[jaclaz]

Maybe this is useful for tweaking/modifying VMM32.VXD:
http://www.tbcnet.co...inp.html#VXDLIB

Quote

VXDLIB.ZIP -- VxDLib is a utility that I have written that works with the new compressed W4 file format used by VMM32.VXD to archive multiple VxDs for Windows '95: you can dump out the contents of VMM32.VXD, decompress it, recompress it (more tightly than Microsoft), and extract individual VxD's from it. Multiple VxD's can be extracted using wildcards. VXDLIB.ZIP includes VXDLIB.EXE and VXDLIB.DOC.

jaclaz

[Ninho]

LLXX, on Nov 1 2006, 10:08 AM, said:

Interesting point. Would it be possible to rebuild it with only the needed VXDs (and put the other VXDs that normally aren't in it) and decrease bootup time even further?

It is indeed possible, but generally not worth doing unless, maybe, your system has undergone many changes since it was first build. Working instructions (by Pietrek or Russinovich or? some guru of the kind) are available on the web should you want to play, Google is your friend...

[Edited : The guru in question was Clive Turvey indeed, as referenced by Jacklaz while I was writing this...]
Basically, vmm.vxd is a composite of :

- "the" VMM.VXD itself,
- an "W4" archive of other VxDs, similar to a zip, built at system installation time from the individual VxDs.

Because the VxDs are compressed and also since it is only one file to open instead of several, the load time is indeed decreased. Notice that this was already done in Windows 3.11 for Workgroups, the Win386.exe was also an archive, albeit uncompressed (the "W3" type).

HTH

--
Ninho

This post has been edited by Ninho: 08 November 2006 - 02:55 PM

[Offler]

I have made another reinstallation of win98se for testing purposes. Bios was set to manual mode - each irq has been set manually and it was forbidden to use PNP in many cases.

Then i listed device manager and only one device was using vmm32.vxd. In previous installation it was used by many devices (at least by three). Thats strange. When the PNP and IRQ selection was automatic many of drivers used it, but the system was unstable resulting in "Blue screen of death", and guess in which module happened this Exception Error. (yes, in vmm32.vxd)

but it is still hard to say if it causes trouble, maybe the same error could happen in other module (such as ntkern.vxd), but in fact i havent seen "BSOD" after i put these files in system folder.

(btw i realized one thing. ntkern.vxd has been installed in vmm32 directory, but it has not been installed in system directory. some other files has been installed in both directories during installation proces. i have no idea why...)

This post has been edited by Offler: 12 November 2006 - 04:37 PM