Re: Fix for Blue Screen's and other fatal errors

On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" <[email hidden]> wrote: >The author of this website apparently was one of the beta testers for >Windows 98 and he stated that in their rush to get the product to the >market, Microsoft omitted several important vxd files (surprised??). That's an urban legend, so to say. These files are there in every standard Windows installation, they are just packed together in one larger file. Don't have the URL with the details on hand but I'll see if I can find it. But hey, if you *think* it improves things for you, just go ahead. Imagination is quite a strong factor ... :) Jan

I have been experiencing random blue screen's and other fatal errors, usually after running GPL and exiting the program succesfully. One in particular was a vcomm.vxd fatal error, a file that wasn't even on my hard drive. I thought this odd and checked the web and came up with this fix... http://users.megapath.net/~revolution/vxdfix.html The author of this website apparently was one of the beta testers for Windows 98 and he stated that in their rush to get the product to the market, Microsoft omitted several important vxd files (surprised??). He developed a batch file to fix this (it extracts the missing vxd files from your windows cd and loads them on your hard drive). So I tried it (I run Win95) and it works great thus far. I have also noticed my modem connects fastet to the internet and my webpages seem to load faster. So instead of blaming GPL for those fatal errors...it's just might be due to those missing vxd files. KC

Urban legend it is not. The "one large file you speak of is not REALLY a real file at all. It is vmm32.vxd which is a "global device driver" that windows uses in the absence of proper devide drivers. It is not as efficient, nor is it really a file of intent (as far as application goes). Windows likes to use it during install, so that plug 'n pray will operate some devices immediately. In fact... if you have not installed the files manually... you can simply goto Control Panel>System>Display Device> Dub Click Card>Driver Info and look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows it needs vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebce for basic function. You push that vid card, you gonna get instabilities, since Windows is also using that device driver for many other devices at the same time... and that file is not really intended for application, it is for basic function. I highly suggest people install the vxds manually. www.gplonline.com has a similar patch, along with many others for online stability, etc. in the Tech Talk section. Cheers, Schumi "Jan Loebzien" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (18 lines)

> On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > <[email hidden]> wrote: > > > >The author of this website apparently was one of the beta testers for > >Windows 98 and he stated that in their rush to get the product to the > >market, Microsoft omitted several important vxd files (surprised??). > > That's an urban legend, so to say. These files are there in every > standard Windows installation, they are just packed together in > one larger file. Don't have the URL with the details on hand but > I'll see if I can find it. > > But hey, if you *think* it improves things for you, just go ahead. > Imagination is quite a strong factor ... :) > > > Jan

Urban legend it is not. The "one large file you speak of is not REALLY a real file at all. It is vmm32.vxd which is a "global device driver" that windows uses in the absence of proper devide drivers. It is not as efficient, nor is it really a file of intent (as far as application goes). Windows likes to use it during install, so that plug 'n pray will operate some devices immediately. In fact... if you have not installed the files manually... you can simply goto Control Panel>System>Display Device> Dub Click Card>Driver Info and look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows it needs vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebce for basic function. You push that vid card, you gonna get instabilities, since Windows is also using that device driver for many other devices at the same time... and that file is not really intended for application, it is for basic function. I highly suggest people install the vxds manually. www.gplonline.com has a similar patch, along with many others for online stability, etc. in the Tech Talk section. Cheers, Schumi

Quoted text (16 lines)

> On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > >The author of this website apparently was one of the beta testers for > >Windows 98 and he stated that in their rush to get the product to the > >market, Microsoft omitted several important vxd files (surprised??). > That's an urban legend, so to say. These files are there in every > standard Windows installation, they are just packed together in > one larger file. Don't have the URL with the details on hand but > I'll see if I can find it. > But hey, if you *think* it improves things for you, just go ahead. > Imagination is quite a strong factor ... :) > Jan

Jason, do you have that file for the vxds? when I try to download it off the site you listed, I am getting a CGI error Thanks "Jason "Schumi" Murray" <[email hidden]> wrote in message news:[email hidden]... > Urban legend it is not. > > The "one large file you speak of is not REALLY a real file at all. It is > vmm32.vxd which is a "global device driver" that windows uses in theabsence > of proper devide drivers. It is not as efficient, nor is it really a fileof > intent (as far as application goes). Windows likes to use it duringinstall, > so that plug 'n pray will operate some devices immediately. > > In fact... if you have not installed the files manually... you can simply > goto Control Panel>System>Display Device> Dub Click Card>Driver Info and > look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows itneeds > vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebce for basic > function. > > You push that vid card, you gonna get instabilities, since Windows is also > using that device driver for many other devices at the same time... andthat

Quoted text (34 lines)

> file is not really intended for application, it is for basic function. > > I highly suggest people install the vxds manually. > > www.gplonline.com has a similar patch, along with many others for online > stability, etc. in the Tech Talk section. > > Cheers, > > Schumi > > > "Jan Loebzien" <[email hidden]> wrote in message > news:[email hidden]... > > On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > > <[email hidden]> wrote: > > > > > > >The author of this website apparently was one of the beta testers for > > >Windows 98 and he stated that in their rush to get the product to the > > >market, Microsoft omitted several important vxd files (surprised??). > > > > That's an urban legend, so to say. These files are there in every > > standard Windows installation, they are just packed together in > > one larger file. Don't have the URL with the details on hand but > > I'll see if I can find it. > > > > But hey, if you *think* it improves things for you, just go ahead. > > Imagination is quite a strong factor ... :) > > > > > > Jan > >

"Cliff Roman" <[email hidden]> wrote in message news:96ujor$165e$[email hidden]... > Jason, do you have that file for the vxds? when I try to download it offthe > site you listed, I am getting a CGI error same here

**** Post for FREE via your newsreader at post.usenet.com **** Can someone please start this thread from the top, and explain _exactly_ what is being discussed here? It sounds interesting and important. I just can't figure it out because there are sections missing... Thanks :) -Larry "Jason "Schumi" Murray" <[email hidden]> wrote in message news:[email hidden]... > Urban legend it is not. > > The "one large file you speak of is not REALLY a real file at all. It is > vmm32.vxd which is a "global device driver" that windows uses in theabsence > of proper devide drivers. It is not as efficient, nor is it really a fileof > intent (as far as application goes). Windows likes to use it duringinstall, > so that plug 'n pray will operate some devices immediately. > > In fact... if you have not installed the files manually... you can simply > goto Control Panel>System>Display Device> Dub Click Card>Driver Info and > look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows itneeds > vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebce for basic > function. > > You push that vid card, you gonna get instabilities, since Windows is also > using that device driver for many other devices at the same time... andthat

Quoted text (34 lines)

> file is not really intended for application, it is for basic function. > > I highly suggest people install the vxds manually. > > www.gplonline.com has a similar patch, along with many others for online > stability, etc. in the Tech Talk section. > > Cheers, > > Schumi > > > "Jan Loebzien" <[email hidden]> wrote in message > news:[email hidden]... > > On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > > <[email hidden]> wrote: > > > > > > >The author of this website apparently was one of the beta testers for > > >Windows 98 and he stated that in their rush to get the product to the > > >market, Microsoft omitted several important vxd files (surprised??). > > > > That's an urban legend, so to say. These files are there in every > > standard Windows installation, they are just packed together in > > one larger file. Don't have the URL with the details on hand but > > I'll see if I can find it. > > > > But hey, if you *think* it improves things for you, just go ahead. > > Imagination is quite a strong factor ... :) > > > > > > Jan > >

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! *** http://www.usenet.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

On Tue, 20 Feb 2001 11:04:24 -0800, "Jason \"Schumi\" Murray" <[email hidden]> wrote: >Urban legend it is not. > >The "one large file you speak of is not REALLY a real file at all. It is >vmm32.vxd Since when is a .vxd not a file? >which is a "global device driver" that windows uses in the absence >of proper devide drivers. It is not as efficient, nor is it really a file of >intent (as far as application goes). It's like the unified Detonator drivers from Nvidia. They also work for all cards from a TNT1 (or even Riva?) up to a Gefarce2 GTS Ultra. Do you think that makes them any less efficient? >You push that vid card, you gonna get instabilities, since Windows is also >using that device driver for many other devices at the same time... and that >file is not really intended for application, it is for basic function. A driver can (and does) contain many different functions, which are called independently once the driver is loaded into memory. I'm repeating myself here: >>But hey, if you *think* it improves things for you, just go ahead. >>Imagination is quite a strong factor ... :) Jan

http://www.infinisource.com/techfiles/vmm32.html -- Cheers, Robin Lord - Trance DJ & Sim Racer. http://www.oppositelock.co.uk N�rburgring and Grand Prix Legends Jan Loebzien <[email hidden]> wrote in message news:[email hidden]... | On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" | <[email hidden]> wrote: | | | >The author of this website apparently was one of the beta testers for | >Windows 98 and he stated that in their rush to get the product to the | >market, Microsoft omitted several important vxd files (surprised??). | | That's an urban legend, so to say. These files are there in every | standard Windows installation, they are just packed together in | one larger file. Don't have the URL with the details on hand but | I'll see if I can find it. | | But hey, if you *think* it improves things for you, just go ahead. | Imagination is quite a strong factor ... :) | | | Jan

How will that work for WinME? "Jason "Schumi" Murray" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (22 lines)

> Sincere apologies... seems a misconfiguration the file extension in the > webserver caused this. All fixed, and tested. > > Thanks for bringing this my attention. > > Cheers, > > Schumi > > "Cliff Roman" <[email hidden]> wrote in message > news:96ujor$165e$[email hidden]... > > Jason, do you have that file for the vxds? when I try to download it off > the > > site you listed, I am getting a CGI error > > > > Thanks > > > > "Jason "Schumi" Murray" <[email hidden]> wrote in message > > news:[email hidden]... > > > Urban legend it is not. > > > > > > The "one large file you speak of is not REALLY a real file at all. It

is

Quoted text (12 lines)

> > > vmm32.vxd which is a "global device driver" that windows uses in the > > absence > > > of proper devide drivers. It is not as efficient, nor is it really a > file > > of > > > intent (as far as application goes). Windows likes to use it during > > install, > > > so that plug 'n pray will operate some devices immediately. > > > > > > In fact... if you have not installed the files manually... you can > simply > > > goto Control Panel>System>Display Device> Dub Click Card>Driver Info

and

Quoted text (9 lines)

> > > look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows it > > needs > > > vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebce for > basic > > > function. > > > > > > You push that vid card, you gonna get instabilities, since Windows is > also > > > using that device driver for many other devices at the same time...

and > > that > > > file is not really intended for application, it is for basic function. > > > > > > I highly suggest people install the vxds manually. > > > > > > www.gplonline.com has a similar patch, along with many others foronline

Quoted text (14 lines)

> > > stability, etc. in the Tech Talk section. > > > > > > Cheers, > > > > > > Schumi > > > > > > > > > "Jan Loebzien" <[email hidden]> wrote in message > > > news:[email hidden]... > > > > On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > > > > <[email hidden]> wrote: > > > > > > > > > > > > >The author of this website apparently was one of the beta testers

for > > > > >Windows 98 and he stated that in their rush to get the product tothe > > > > >market, Microsoft omitted several important vxd files(surprised??).

Quoted text (17 lines)

> > > > > > > > That's an urban legend, so to say. These files are there in every > > > > standard Windows installation, they are just packed together in > > > > one larger file. Don't have the URL with the details on hand but > > > > I'll see if I can find it. > > > > > > > > But hey, if you *think* it improves things for you, just go ahead. > > > > Imagination is quite a strong factor ... :) > > > > > > > > > > > > Jan > > > > > > > > > > > >

Sincere apologies... seems a misconfiguration the file extension in the webserver caused this. All fixed, and tested. Thanks for bringing this my attention. Cheers, Schumi "Cliff Roman" <[email hidden]> wrote in message news:96ujor$165e$[email hidden]... > Jason, do you have that file for the vxds? when I try to download it offthe

Quoted text (12 lines)

> site you listed, I am getting a CGI error > > Thanks > > "Jason "Schumi" Murray" <[email hidden]> wrote in message > news:[email hidden]... > > Urban legend it is not. > > > > The "one large file you speak of is not REALLY a real file at all. It is > > vmm32.vxd which is a "global device driver" that windows uses in the > absence > > of proper devide drivers. It is not as efficient, nor is it really a

file > of > > intent (as far as application goes). Windows likes to use it during > install, > > so that plug 'n pray will operate some devices immediately. > > > > In fact... if you have not installed the files manually... you cansimply > > goto Control Panel>System>Display Device> Dub Click Card>Driver Info and > > look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows it > needs > > vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebce forbasic > > function. > > > > You push that vid card, you gonna get instabilities, since Windows isalso

Quoted text (38 lines)

> > using that device driver for many other devices at the same time... and > that > > file is not really intended for application, it is for basic function. > > > > I highly suggest people install the vxds manually. > > > > www.gplonline.com has a similar patch, along with many others for online > > stability, etc. in the Tech Talk section. > > > > Cheers, > > > > Schumi > > > > > > "Jan Loebzien" <[email hidden]> wrote in message > > news:[email hidden]... > > > On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > > > <[email hidden]> wrote: > > > > > > > > > >The author of this website apparently was one of the beta testers for > > > >Windows 98 and he stated that in their rush to get the product to the > > > >market, Microsoft omitted several important vxd files (surprised??). > > > > > > That's an urban legend, so to say. These files are there in every > > > standard Windows installation, they are just packed together in > > > one larger file. Don't have the URL with the details on hand but > > > I'll see if I can find it. > > > > > > But hey, if you *think* it improves things for you, just go ahead. > > > Imagination is quite a strong factor ... :) > > > > > > > > > Jan > > > > > >

Sincere apologies... seems a misconfiguration the file extension in the webserver caused this. All fixed, and tested. Thanks for bringing this my attention. Cheers, Schumi > Jason, do you have that file for the vxds? when I try to download it off the

Quoted text (13 lines)

> site you listed, I am getting a CGI error > Thanks > > Urban legend it is not. > > The "one large file you speak of is not REALLY a real file at all. It is > > vmm32.vxd which is a "global device driver" that windows uses in the > absence > > of proper devide drivers. It is not as efficient, nor is it really a

file > of > > intent (as far as application goes). Windows likes to use it during > install, > > so that plug 'n pray will operate some devices immediately. > > In fact... if you have not installed the files manually... you can simply > > goto Control Panel>System>Display Device> Dub Click Card>Driver Info and > > look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows it > needs > > vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebce for basic > > function. > > You push that vid card, you gonna get instabilities, since Windows is also

Quoted text (32 lines)

> > using that device driver for many other devices at the same time... and > that > > file is not really intended for application, it is for basic function. > > I highly suggest people install the vxds manually. > > www.gplonline.com has a similar patch, along with many others for online > > stability, etc. in the Tech Talk section. > > Cheers, > > Schumi > > > On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > > > >The author of this website apparently was one of the beta testers for > > > >Windows 98 and he stated that in their rush to get the product to the > > > >market, Microsoft omitted several important vxd files (surprised??). > > > That's an urban legend, so to say. These files are there in every > > > standard Windows installation, they are just packed together in > > > one larger file. Don't have the URL with the details on hand but > > > I'll see if I can find it. > > > But hey, if you *think* it improves things for you, just go ahead. > > > Imagination is quite a strong factor ... :) > > > Jan

Not advisable that you use that patch for ME. Although... I did not test it to see the results, since I found too many other bugs in ME that forced me to drop it completely. ME spent all of 48 hours on one of my boxes... then out tha door. The best thing to do is again check your device drivers section in System. Check the vidcard, and any network cards you may have. Look for the brackets. If there are none... you won't need a patch. In short, don't know if this problem exists in ME to begin with... so don't use that patch on it (those are win98 vxds included in that patch). Cheers, Schumi "Cliff Roman" <[email hidden]> wrote in message news:96v1j5$prk$[email hidden]...

Quoted text (17 lines)

> How will that work for WinME? > > > "Jason "Schumi" Murray" <[email hidden]> wrote in message > news:[email hidden]... > > Sincere apologies... seems a misconfiguration the file extension in the > > webserver caused this. All fixed, and tested. > > > > Thanks for bringing this my attention. > > > > Cheers, > > > > Schumi > > > > "Cliff Roman" <[email hidden]> wrote in message > > news:96ujor$165e$[email hidden]... > > > Jason, do you have that file for the vxds? when I try to download it

off > > the > > > site you listed, I am getting a CGI error > > > > > > Thanks > > > > > > "Jason "Schumi" Murray" <[email hidden]> wrote inmessage > > > news:[email hidden]... > > > > Urban legend it is not. > > > > > > > > The "one large file you speak of is not REALLY a real file at all.It

Quoted text (15 lines)

> is > > > > vmm32.vxd which is a "global device driver" that windows uses in the > > > absence > > > > of proper devide drivers. It is not as efficient, nor is it really a > > file > > > of > > > > intent (as far as application goes). Windows likes to use it during > > > install, > > > > so that plug 'n pray will operate some devices immediately. > > > > > > > > In fact... if you have not installed the files manually... you can > > simply > > > > goto Control Panel>System>Display Device> Dub Click Card>Driver Info > and > > > > look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows

it > > > needs > > > > vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebce for > > basic > > > > function. > > > > > > > > You push that vid card, you gonna get instabilities, since Windowsis > > also > > > > using that device driver for many other devices at the same time... > and > > > that > > > > file is not really intended for application, it is for basicfunction.

Quoted text (43 lines)

> > > > > > > > I highly suggest people install the vxds manually. > > > > > > > > www.gplonline.com has a similar patch, along with many others for > online > > > > stability, etc. in the Tech Talk section. > > > > > > > > Cheers, > > > > > > > > Schumi > > > > > > > > > > > > "Jan Loebzien" <[email hidden]> wrote in message > > > > news:[email hidden]... > > > > > On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > > > > > <[email hidden]> wrote: > > > > > > > > > > > > > > > >The author of this website apparently was one of the beta testers > for > > > > > >Windows 98 and he stated that in their rush to get the product to > the > > > > > >market, Microsoft omitted several important vxd files > (surprised??). > > > > > > > > > > That's an urban legend, so to say. These files are there in every > > > > > standard Windows installation, they are just packed together in > > > > > one larger file. Don't have the URL with the details on hand but > > > > > I'll see if I can find it. > > > > > > > > > > But hey, if you *think* it improves things for you, just go ahead. > > > > > Imagination is quite a strong factor ... :) > > > > > > > > > > > > > > > Jan > > > > > > > > > > > > > > > > > > > >

Not advisable that you use that patch for ME. Although... I did not test it to see the results, since I found too many other bugs in ME that forced me to drop it completely. ME spent all of 48 hours on one of my boxes... then out tha door. The best thing to do is again check your device drivers section in System. Check the vidcard, and any network cards you may have. Look for the brackets. If there are none... you won't need a patch. In short, don't know if this problem exists in ME to begin with... so don't use that patch on it (those are win98 vxds included in that patch). Cheers, Schumi

Quoted text (18 lines)

> How will that work for WinME? > > Sincere apologies... seems a misconfiguration the file extension in the > > webserver caused this. All fixed, and tested. > > Thanks for bringing this my attention. > > Cheers, > > Schumi > > > Jason, do you have that file for the vxds? when I try to download it

off > > the > > > site you listed, I am getting a CGI error > > > Thanks message > > > > Urban legend it is not. > > > > The "one large file you speak of is not REALLY a real file at all. It

Quoted text (15 lines)

> is > > > > vmm32.vxd which is a "global device driver" that windows uses in the > > > absence > > > > of proper devide drivers. It is not as efficient, nor is it really a > > file > > > of > > > > intent (as far as application goes). Windows likes to use it during > > > install, > > > > so that plug 'n pray will operate some devices immediately. > > > > In fact... if you have not installed the files manually... you can > > simply > > > > goto Control Panel>System>Display Device> Dub Click Card>Driver Info > and > > > > look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows

it > > > needs > > > > vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebce for > > basic > > > > function. > > > > You push that vid card, you gonna get instabilities, since Windows is > > also > > > > using that device driver for many other devices at the same time... > and > > > that > > > > file is not really intended for application, it is for basic function.

Quoted text (32 lines)

> > > > I highly suggest people install the vxds manually. > > > > www.gplonline.com has a similar patch, along with many others for > online > > > > stability, etc. in the Tech Talk section. > > > > Cheers, > > > > Schumi > > > > > On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > > > > > >The author of this website apparently was one of the beta testers > for > > > > > >Windows 98 and he stated that in their rush to get the product to > the > > > > > >market, Microsoft omitted several important vxd files > (surprised??). > > > > > That's an urban legend, so to say. These files are there in every > > > > > standard Windows installation, they are just packed together in > > > > > one larger file. Don't have the URL with the details on hand but > > > > > I'll see if I can find it. > > > > > But hey, if you *think* it improves things for you, just go ahead. > > > > > Imagination is quite a strong factor ... :) > > > > > Jan

It does exist.. so I guess I can just manually extract those files out of the WinME cabs "Jason "Schumi" Murray" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (11 lines)

> Not advisable that you use that patch for ME. > > Although... I did not test it to see the results, since I found too many > other bugs in ME that forced me to drop it completely. ME spent all of 48 > hours on one of my boxes... then out tha door. > > The best thing to do is again check your device drivers section in System. > Check the vidcard, and any network cards you may have. Look for the > brackets. If there are none... you won't need a patch. > > In short, don't know if this problem exists in ME to begin with... so

don't

Quoted text (15 lines)

> use that patch on it (those are win98 vxds included in that patch). > > Cheers, > > Schumi > > > "Cliff Roman" <[email hidden]> wrote in message > news:96v1j5$prk$[email hidden]... > > How will that work for WinME? > > > > > > "Jason "Schumi" Murray" <[email hidden]> wrote in message > > news:[email hidden]... > > > Sincere apologies... seems a misconfiguration the file extension in

the

Quoted text (26 lines)

> > > webserver caused this. All fixed, and tested. > > > > > > Thanks for bringing this my attention. > > > > > > Cheers, > > > > > > Schumi > > > > > > "Cliff Roman" <[email hidden]> wrote in message > > > news:96ujor$165e$[email hidden]... > > > > Jason, do you have that file for the vxds? when I try to download it > off > > > the > > > > site you listed, I am getting a CGI error > > > > > > > > Thanks > > > > > > > > "Jason "Schumi" Murray" <[email hidden]> wrote in > message > > > > news:[email hidden]... > > > > > Urban legend it is not. > > > > > > > > > > The "one large file you speak of is not REALLY a real file at all. > It > > is > > > > > vmm32.vxd which is a "global device driver" that windows uses in

the > > > > absence > > > > > of proper devide drivers. It is not as efficient, nor is it reallya > > > file > > > > of > > > > > intent (as far as application goes). Windows likes to use itduring > > > > install, > > > > > so that plug 'n pray will operate some devices immediately. > > > > > > > > > > In fact... if you have not installed the files manually... you can > > > simply > > > > > goto Control Panel>System>Display Device> Dub Click Card>DriverInfo > > and > > > > > look at the vmm32.vxd and the "vdd.vxd" in brackets. Windows knows > it > > > > needs > > > > > vdd.vxd, but cannot find it, so it uses vmm32.vxd in its absebcefor

Quoted text (7 lines)

> > > basic > > > > > function. > > > > > > > > > > You push that vid card, you gonna get instabilities, since Windows > is > > > also > > > > > using that device driver for many other devices at the same

time...

Quoted text (23 lines)

> > and > > > > that > > > > > file is not really intended for application, it is for basic > function. > > > > > > > > > > I highly suggest people install the vxds manually. > > > > > > > > > > www.gplonline.com has a similar patch, along with many others for > > online > > > > > stability, etc. in the Tech Talk section. > > > > > > > > > > Cheers, > > > > > > > > > > Schumi > > > > > > > > > > > > > > > "Jan Loebzien" <[email hidden]> wrote in message > > > > > news:[email hidden]... > > > > > > On Mon, 19 Feb 2001 22:45:54 -0500, "{USER_FIRSTNAME} Crocco" > > > > > > <[email hidden]> wrote: > > > > > > > > > > > > > > > > > > >The author of this website apparently was one of the beta

testers > > for > > > > > > >Windows 98 and he stated that in their rush to get the productto > > the > > > > > > >market, Microsoft omitted several important vxd files > > (surprised??). > > > > > > > > > > > > That's an urban legend, so to say. These files are there inevery > > > > > > standard Windows installation, they are just packed together in > > > > > > one larger file. Don't have the URL with the details on hand but > > > > > > I'll see if I can find it. > > > > > > > > > > > > But hey, if you *think* it improves things for you, just goahead.

Quoted text (14 lines)

> > > > > > Imagination is quite a strong factor ... :) > > > > > > > > > > > > > > > > > > Jan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >

"Cliff Roman" <[email hidden]> wrote in message news:96v49d$141u$[email hidden]... > It does exist.. so I guess I can just manually extract those files out of > the WinME cabs > You people are mad. The reason a lot of vxd's are bundles into the large vmm32.vxd is to reduce the boot-up time. By extracting these *SAME* files onto your hard disk you will a) increase your boot-up time (not by much though) and b) reduce memory available as the vmm32.vxd will still be loaded (again not by much though). However, if doing this makes you feel better and give you some sort of sense of power over your OS then go right ahead. Don't take my word for it or the word of a single web page... go and do some research first.

On Tue, 20 Feb 2001 23:24:16 -0000, "Robin Lord" <[email hidden]> wrote: >http://www.infinisource.com/techfiles/vmm32.html Thanks! I head it from a different site but it does say the same. Jan