DeadDude, on Jan 15 2007, 03:19 PM, said:
The patching goes through without a hitch... my problem is I need to know what updates increases the Windows version number to what values?
Or, if there is a way to force Windows to report a particular version number, I think this by itself may allow me to use all the updates without HPJOBBER having issues.
The updates work great, the problem is HPJOBBER doesn't want to work properly for some reason when 98 is fully patched.
Thank you for pointing out the list at the beginning, but I need to find out how those updates change the version reported.
Eck nailed it. "No Microsoft Windows Updates change the version number of Windows with the exception of the long discontinued Microsoft Security Updates Cd. " So your only excuse is a corrupted registry since this version info is just a simple value in the registry here?
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion]
"VersionNumber"="4.10.2222"
"SubVersionNumber"="B"
And this is the same text displayed by pressing Winkey and Pause. It is NOT used for much version testing and it doesn't alter the DOS ver report at all. Your HPJOBBER may be one of the very rare ones that actually does look at (/alter?) this key's value. 98 Gold gets an 'A' for a SubversionNumber after running the Security CD, just to add confusion to the issue I believe, unless anybody else really does know why? Before the Security CD is run, there is no SubVersionNumber entry or value at all.
------------------
soporific
Your trials at WinUP site are due to the erasing of the below key's value by the reinstallation of IE. I really don't know why they do it that way but the iewizard does it every time it fires up. This is the text one sees when clicking on Help/About in IE but with the title 'Update Versions:' instead of the key's name of 'MinorVersion'.
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"MinorVersion"=";SP2;Q890923;Q837009;q313829;Q891781;Q832894;Q823353;Q903235;"
This entry is from my 98se IE 5.50 SP2 machine, your mileage will vary of course. Most of the more recent updates used a custom update engine which directly writes the update's ID number to this key thus providing a record of it for the V4 WinUP scan. If the WinUp scan can't find the number in this key, then you get bugged to reinstall the update even when file version protection inherent in inf files has prevented your higher versioned files from being overwritten during the IE reinstall in the first place and your really don't need the f@#$n update at ALL. To WinUP's credit though, there is also a version test done on the critical update's files themselves so one should not be able to 'fake' their way out of a legitimate WinUP scan of their system by cheating in the registry by manually setting it with values similar to those shown above. But that's one way you can avoid the nag at WinUP site given the proper files are in place, even MS recommended doing just that in one or two cases very early in the V4 WinUP site's life.
The other way is to use the custom update engine with the proper inf file 'strings' section as per each update and let the original engine write the key as it is supposed to. You can spot these updates with Resource Hacker in the RCData section under RunProgram - "OEUPDATE.EXE" Q837009 for example, means that OEUPDATE.EXE is the install engine and a batch file can launch it just fine, I would extend the quotes past the Inf file number Q837009 in this case and also include the full drive and path in the quotes for good measure. This 'Original' method would then also pass the QFE test (maybe?) - which is, go to the Windows folder and double click on QFECheck.exe. Read it's report to find all manner of missing/wrong versioned files. Running updates can be a headache at times as even done fully and properly, QFECheck will show some bad files when they are OK. This was a recent reg 'fix file' posted in Computing.net forum, and it works good. MS needs better logic/script to scan with at WinUP site and they need to write these updates correctly in the first place, as this stuff below attests to, original update data is just plain wrong.
REGEDIT4
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Updates\W98\UPD908519]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Updates\W98\UPD908519]
@="Windows 98 KB908519 Update"
"C:\\WINDOWS\\SYSTEM\\t2embed.dll"="5.0.2195.7073"
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Updates\W98\UPD918547]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Updates\W98\UPD918547]
@="Windows 98 KB918547 Update"
"C:\\WINDOWS\\SYSTEM\\KB918547\\KB918547.EXE"="4.10.0.2224"
"C:\\WINDOWS\\SYSTEM\\KB918547\\Q918547.dll"="4.10.0.2224"
Keep up the good work!
Lee
Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
Help
I'm sure you gave soporific food for thought. 
Believe it or not, I had no idea so many things can be done in a batch file - I never got around playing with them. But I learn fast... sometimes (and it looks very similar to BASIC, which I used to know pretty well back in the Z80 days). 
Back to top
-- seriously, v1.6 is 2 versions before the one that I thought was accurate enough to release to the public. C'mon, v1.8 is on a reasonable server, go get it!
