[PROBLEMCHYLD]

CharlesF, on 07 December 2011 - 05:08 PM, said:

You need to run the EXE file with the /X switch to extract the files.
For some patches it has to be done on a Win2k/XP/2k3 machine.

HTH

I got the files extracted but there is no inf file inside the package.

[PROBLEMCHYLD]

CharlotteTheHarlot, on 29 December 2010 - 06:33 AM, said:

I would suggest installing it on an imaged (roll-back-able) 9x test machine with a registry dump and filelist, BEFORE and AFTER.

Can someone be so kind to do this, if not point me to the tools so I can give it a shot?

[loblo]

InstallWatch is the best before/after utility IMO so I would suggest you use it. It does monitor both files and registry and will keep all the before and after registry values in its database from which you can export anything as regedit 4 files, allowing you to precisely know (and eventually revert) all the installer has done.

http://www.brotherso...watch-9407.html

As suggested you may want to back up your root dir files and windows dir (or even entire C drive) before doing it if you fear to bork it all.

[CharlotteTheHarlot]

PROBLEMCHYLD, on 23 January 2012 - 03:30 PM, said:

CharlotteTheHarlot, on 29 December 2010 - 06:33 AM, said:

I would suggest installing it on an imaged (roll-back-able) 9x test machine with a registry dump and filelist, BEFORE and AFTER.

Can someone be so kind to do this, if not point me to the tools so I can give it a shot?

I have a time constraint presently, else I would do it (err, maybe not, because I am not sure if any of my remaining Win9x systems even require the WMI9x.exe changes).

But what you could do is this (presume you have a spare HDD kicking around) ...

* Do a fresh install of Win9x onto another drive (be safe, disconnect your useable Win9x boot drive) *or* just clone your existing one.

* Save a registry export and also a filelist of the drive (DIR C:\*.* /A /S).

* Run the WMI9x.exe.

* Repeat: Save a registry export and also a filelist of the drive (DIR C:\*.* /A /S).

* Put back your normal Win9x drive and slave the other one as a D: or E: or F: ...

* WinDiff the snapshots you made.

* Collect the needed files from the slaved HDD and gather up the added registry settings from the export. NB: Besides added files and registry keys, there are other things to watch for. For example, there may be edits made to INI files (SYSTEM.INI...etc). These will show up in the WinDiff as modifications to said files in the 2nd filelist. You would then need to further WinDiff your original SYSTEM.INI (from the original drive) with the modified one on the auxillary HDD. Such changes can happen to other files as well. This is why you step carefully through the WinDiff of the filelists.

This is why it is very handy to keep a collection of Hard Drives around. You can really do almost any experiment that suits your fancy

[CharlotteTheHarlot]

EDIT: Oops, sorry guys. The thing said 'Error Occurred'. Hit it again and it duplicated. Weird!

This post has been edited by CharlotteTheHarlot: 25 January 2012 - 03:02 AM

[PROBLEMCHYLD]

I finally created an inf so it can be added to the Service Pack. We are so close to the end.
Heres a link so you guys can see what WMI/WBEM is all about.
http://www.wtcs.org/snmp4tpc/wmi.htm