VSHARE.VXD Missing?
Vern Moore
I had one system hanging during the load of Windows '95 and did a reboot
with the logging on to help issolate the problem. During the process, I
did a find on all load failures and came up with the load of VSHARE
failing one one system. According to the Registry, this is associated
with VMM32 but I am unable to find this module on either system. It is
being loaded on one and not on the other [according to the logs from
each]. I have had some sharing problems on the system that fails the
load! Where is it coming from on the system that says it is loading it
and how might I restore/install it?
Any information will be appreciated,
Vern
--
Travels, Safaris & Wildlife | ("-''-/").___..--''"`-._
http://www.inficad.com/~vmoore | `6_ 6 ) `-. ( ).`-.__.`)
Stop for a visit & say hello! | (_Y_.)' ._ ) `._ `. ``-..-'
Many Photos, Articles & more. | _..`--'_..-_/ /--'_.' ,'
EMail: vmo...@inficad.com | (il),-'' (li),' ((!.-'
Bob Lewis
Check and see if VSHARE is loaded sucessfully prior to the failure. It
is normal for VSHARE to try and load twice - You get a failure the
second time.
Vern Moore
Bob Lewis wrote:
>
> Vern Moore wrote:
> >
> > I had one system hanging during the load of Windows '95 and did a reboot
> > with the logging on to help issolate the problem. During the process, I
> > did a find on all load failures and came up with the load of VSHARE
> > failing one one system. According to the Registry, this is associated
> > with VMM32 but I am unable to find this module on either system. It is
> > being loaded on one and not on the other [according to the logs from
> > each]. I have had some sharing problems on the system that fails the
> > load! Where is it coming from on the system that says it is loading it
> > and how might I restore/install it?
> >
> > Any information will be appreciated,
> >
> > Vern
>
> is normal for VSHARE to try and load twice - You get a failure the
> second time.
You are correct and I appreciate the feedback. I am still a bit curious
as to where it is loaded from as I couldn't located it. Possibly within
one of the CABs?
Thanks
Kestutis Sipavicius
It is loaded from VMM32.VXD, together with other 44 VXDs.
The 45 VXD's were copied from your CAB's during Win95 Setup and bundled
into VMM32.VXD.
If you are still curious, search for "VMM32Files" (w/o quotes) in
regedit.exe.
--
Aloha from Sao Paulo Brazil Lithuania is Beautiful
Backup your Registry weekly and before making any changes to it
Vern Moore <vmo...@inficad.com> wrote in article
<3372106A...@inficad.com>...
Kestutis Sipavicius
Load Failures Listed in the Bootlog.txt File
Article ID: Q127970
Creation Date: 22-MAR-1995
Revision Date: 10-FEB-1997
The information in this article applies to:
筆icrosoft Windows 95
SYMPTOMS
When you review the Bootlog.txt file in the root folder on your hard
disk, you may see the following lines even though your computer seems
to function properly:
畢oadFailed = dsound.vxd 畢oadFailed = ebios 畢oadFailed = ndis2sup.vxd
畢oadFailed = vpowerd 畢oadFailed = vserver.vxd 畢oadFailed = vshare
肘nitCompleteFailed = SDVXD
CAUSE
These load failures do not necessarily mean that there is a problem. It
is common for some, if not all, of these to fail, depending on your
system configuration.
DSOUND
Many sound drivers are DirectSound enabled. DirectSound is part of
Microsoft DirectX, a set of libraries used by most newer Windows-based
games. When a DirectSound-enabled sound driver is loaded, it attempts
to register with the DirectSound library so that games can use it. If
no DirectX-based games are installed on your computer, the DirectSound
library fails to load. This is normal.
EBIOS
The extended BIOS driver did not find an extended BIOS, so it does not
load.
Ndis2sup.vxd
The NDIS 2 support driver did not find any NDIS 2 drivers to support,
so it does not load.
VPOWERD
The Advanced Power Management (APM) driver determined that your
computer does not support APM, so it does not load, or APM support may
be disabled. To determine if you have inadvertently disabled APM in
Device Manager, follow these steps:
1.In Control Panel, double-click System. 2.Click the Device Manager
tab. 3.Double-click the System Devices branch to expand it.
4.Double-click the Advanced Power Management Support branch. (If this
branch does not exist, your computer does not support APM.) 5.Click the
Settings tab. 6.Verify that the Enable Power Management Support check
box is selected.
Vserver.vxd
Vserver.vxd does not load statically so that it can save memory by
loading later in the boot process only if it is needed. For example,
Vserver.vxd might not be needed when you start a laptop computer while
it is out of its docking station.
VSHARE
If you examine the Bootlog.txt file, you will notice that VSHARE loaded
successfully earlier in the boot process. The second copy of VSHARE
detects that VSHARE is already loaded and does not load.
Font Failures
After the first boot of Windows 95, the Bootlog.txt file may list many
font load failures. This is a normal occurrence. When Font Manager
searches the hard disk for fonts, it may find them in several folders.
After it finds them, it records the information so that future attempts
to locate a font proceed more quickly.
--
Aloha from Sao Paulo Brazil Lithuania is Beautiful
Backup your Registry weekly and before making any changes to it
Steven Ross Kurth <ste...@crosslink.net> wrote in article
<01bc5cca$509ac240$f441...@stevek.crosslink.net>...
> > Check and see if VSHARE is loaded sucessfully prior to the failure.
It
> > is normal for VSHARE to try and load twice - You get a failure the
> > second time.
> >
> I have this problem, too. How do i stop the second load attempt? Also
> havinhg load of NDIS2SUP.VXD fail after NDIS.VXD loads successfully.