Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Windows 98 Driver bug solution - possible Add-on for Unofficial Servic

- - - - -

  • Please log in to reply
28 replies to this topic

#26
PROBLEMCHYLD

PROBLEMCHYLD

    The Resurrector for old Windows OS

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,528 posts
  • OS:98SE
  • Country: Country Flag
I would assume the vmm32 folder right?

Believe God is the Alpha and Omega.
Believe Jesus Christ died for our sins.
Repent for your sins now or there will be
BLOOD

The Path to God


U98SESP3 03-11-2013



How to remove advertisement from MSFN

#27
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 808 posts
  • OS:98SE
  • Country: Country Flag

Donator

I would assume the vmm32 folder right?


Yes, for the files listed. It depends completely on the file. Some VXD's still go in \SYSTEM (including NDIS.VXD) or SYSTEM\IOSUBSYS (including CDFS.VXD) rather than SYSTEM\VMM32. The HotFixes should place them in the proper locations.

If in doubt, you can always examine COPY.INF inside your target 9x CAB files. Find the file in question and it will have an entry, for example:

CDFS.VXD=12
NDIS.VXD=11
UDF.VXD=22

The numbers after the file are "LDID's" - Logical Directory Identifaction Numbers (I think that's the right term).

These LDID's are explained in this section common to HotFixes:

[DestinationDirs]
; 10=Windows, 11=SYSTEM, 12=IOSUBSYS, 13=COMMAND, 14=Control Panel, 15=Printers, 16=Workgroup
; 17=INF, 18=Help, 19=Administration, 20=Fonts, 21=Viewers, 22=VMM32, 23=Color, 25=Shared
; 26=Winboot, 27=Machine, 28=Host Winboot, 30=Boot drv root, 31=Root of Boot drv Host
; 00=Null (new) LDID, 01=Source drv:\path, 02=Temp Setup, 03=Uninstall, 04=Backup


Some VXD's are compressed into VMM32.VXD when Windows 9x is installed. This does not mean that 9x is using a "generic driver" as described above. It simply means that all of those individual files such as NTKERN.VXD, UDF.VXD, VFAT.VXD, etc etc have all been combined into a single executable driver. Think of VMM32.VXD as a "ZIP archive" of VXD's. All of the original code exists, just no longer as individual files.

When applying HotFixes that place a newer version of a file such as NTKERN.VXD, the new file is added to the \VMM32 folder, where it will automatically override the older version that was packed into VMM32.VXD.

This is why it is preferable to slipstream files or add them to the \WIN9x SETUP folder prior to installation, so that the newer files will be picked up and be packed into VMM32.VXD during SETUP rather than the older versions. This saves space by eliminating the older unused code and preventing the need for a newer HotFix file to exist separately. It also can make the system perform faster if the VXD's are packed into VMM32.VXD rather than loaded individually (this was Microsoft's original intent).


Note that VMM.VXD is an exception to all the rules above. VMM.VXD does not exist as an independent file on a 9x system unless it has been added by a HotFix. VMM.VXD is already packed into VMM32.VXD inside the original CABs and the newer HotFix VMM.VXD's cannot be packed into VMM32.VXD. If VMM.VXD is present during the original VMM32.VXD compression, the compression will fail.

Edited by LoneCrusader, 06 August 2013 - 09:30 PM.


#28
Zoinkity

Zoinkity

    Junior

  • Member
  • Pip
  • 63 posts

Wasn't there a simple method to force a rebuild of VMM32.vxd? 



#29
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 808 posts
  • OS:98SE
  • Country: Country Flag

Donator

Wasn't there a simple method to force a rebuild of VMM32.vxd?


Not that I am aware of, but that doesn't mean that it doesn't exist.

VMM32.VXD usually contains many of the same VXD's, but it can still be unique to each machine. WININIT.INI is used to build it during SETUP, but this INI file is used for more things on the second round of SETUP, and only ONE backup version is maintained. Each time a new INI is generated, the oldest backup is lost. So theoretically you could lose the original INI that built VMM32 on the second boot to Desktop unless you physically make a backup copy of it and rename it to something that will not be overwritten.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN