billygoat

Thanks! Whoops, I never noticed the Unofficial VB updates! Guess I just used my earlier (default) choices for that module without noticing the 'Unofficial' part. First time I've seen it, and just with these two.

billygoat, msxml4.dll versions higher than 4.20.9841.0 (kb927978) have problems in Windows 9x. Remove msxml4 from Add/Remove Programs, then delete msxml4.dll from \WINDOWS\SYSTEM and run Auto-Patcher again. The official Visual Basic 6 files are older than the unofficial update so do not worry about that one. Thanks, RetroOS. Interesting about the msxml4.dll. I was thinking that AP ought to handle it, in that case. (Since I'm assuming the newer one came from AP August Full.) Likewise, if there's a benefit (or no worry) to the newer msvbvm60.dll, why did it appear in the August AP but seems to have been removed in AP October Full? (I haven't actually checked the packages for these versions, so I might be wrong about the origin. But I've been keeping backups of each update stage and that's what it looks like at first glance.)

I have a couple of interesting lines in my I_Result.log after updating with the AP October Full release. (This was installed after fully uninstalling the August Full release - I never tried the September update.) -------------------------------------------------------------------- 14:42:56 ++ the Internet Explorer module was started -------------------------------------------------------------------- 14:43:03 -- update installed: HTMLHelp - Unofficial HTML Help Update 14:43:05 -- was not installed: Unofficial MSXML 3.0 SP7 Update (kb924191) 14:43:06 -- superceeded: -- kb925672 (MSXML 4.0 SP2 Update) File: C:\WINDOWS\system\msxml4.dll Current: 4.20.9848.0 Attempted: 4.20.9839.0 AFAICS, the 4.20.9848.0 version was installed by the August AutoPatcher, so I'm wondering why October Full is trying to install 4.20.9839.0. (Thinking perhaps the later version was removed from October Full for some reason.) Same question for this: -------------------------------------------------------------------- 14:51:58 ++ the Visual Basic Runtimes module was started -------------------------------------------------------------------- 14:51:58 -- set to by-pass -- VBRUN100 - Visual Basic 1.0 Runtimes 14:51:58 -- set to by-pass -- VBRUN200 - Visual Basic 2.0 Runtimes 14:51:59 -- set to by-pass -- VBRUN300 - Visual Basic 3.0 Runtimes 14:51:59 -- set to by-pass -- VBRUN400 - Visual Basic 4.0 Runtimes (16 & 32 bit) 14:52:00 -- set to by-pass -- VBRUN500 - Visual Basic 5.0 sp3 Runtime Files 14:52:01 -- superceeded: -- VBRUN600 (Official Visual Basic 6.0 sp6 Runtime Files) File: C:\WINDOWS\system\msvbvm60.dll Current: 6.0.97.98 Attempted: 6.0.97.82 Again, the later version seems to have been installed by AP August Full.

I've finally had time to try the latest AP for the first time since 1.95 PR2, and also to read all the posts since April. I downloaded and installed the August FULL archive and set up choices to be similar to my 1.95 PR2 choices. Thanks for the System.ini tweaks info! This is what I wanted to see, although I just used the recommended automatic values based on my RAM config. The procedure seemed to go fine. I still have trouble with my 'choices.sav' file disappearing periodically, but I've learned to back it up. (Every so often AP doesn't load any settings when I choose 'M', and I investigate and sure enough, 'choices.sav' has gone missing!) I was a bit concerned about whether changes to AP or to some of the fixes would update correctly over 1.95 PR2, and a bit confused about the Win982ME changes, but in the end I thought I had it figured out and felt fairly confident. (I enabled both Q891711 and Explor98, sounds like that's what I should want.) I also suffered the "OLEDLG.DLL is missing" problem, and found that OLEDLG00.DLL was already the same file in the update, though I can only see 'version 1.0' and I'm not sure where the 'real' version numbers are to be found. Anyway, I just renamed it and I think all is well. Much more interesting is that two updates are reported as having been set to 'bypass' even though there's no option to do so! From my I_Result.Log: 14:53:27 ++ the Critical & Recommended System Updates module was started -------------------------------------------------------------------- 14:53:30 -- update installed: RootsUpd - Root Certificate Update August 2007 (13.0.2195.0) 14:53:33 -- update installed: TOOLS9X - Tihiy's Unofficial Improved Replacement Tools 14:53:36 -- update installed: OleLibUp - OLE Automation Libraries Update (OLEPRO32.DLL 5.0.4530.0) 14:53:39 -- set to by-pass -- 48BitLB2 - Unofficial Update for Drives over 137gb (for IBM portables) 14:53:39 -- set to by-pass -- NativUSB - Maximus Decim Native USB Drivers v3.1 14:53:40 -- set to by-pass -- 98KrnlUp - Unofficial Update for KRNL386.EXE (4.10.0.1999) 14:53:41 -- set to by-pass -- kb933360 - Unofficial 2007 Updates to Time Zone Daylight Saving Time Settings 14:53:43 .. the computer was set to reboot. 14:55:00 .. the computer finished rebooting and started Auto-Patcher. -------------------------------------------------------------------- I'm referring to 98KrnlUp and kb933360. I don't see any relevant options for this module. Running a report doesn't find them missing, but it doesn't report them installed, either. Should I install these manually? I haven't tried yet. If so, I'm not sure if I should use the INF files to install or just run the 98KrnlUp.exe and kb933360.exe. Thanks again. I'm amazed and encouraged to see this updated with so much enthusiasm!

Darn, I've tried it again with WM Encoder choice (for other reasons, having restored again) and *didn't* have it happen. As I said, my original sense was that it may have been random, so hard to test. WM Encoder seems unlikely to be causing it anyway, since WMP 9, codecs, and patches occur afterward. I've been toying with additionally installing a few apparently remaining codecs from wmp6cdcs.exe. GSpot reports three additional codecs installed after running wmp6cdcs.exe, and also wmp6cdcs.exe reports three to install after the AP module is run. Maybe they only work with MP 6.4 or are obsolete, but I actually use 6.4 rather than MP9 for wmv when possible. Any thoughts on wmp6cdcs.exe? What is actually in the Legacy pack?

The message you are getting happens when AP has lost control of the OS during a patch session [...] at least one update is rebooting after its finished when its not supposed to. If you can narrow down which ones are doing this and post the result, that would be helpful. It looks like the WM Encoder is doing it. First time I had choices 1 and 2 set to install. (Legacy and Encoder.) This time I left it at default (Legacy only) and it went as expected.

I had this happen after the MP9 module today, but I also had this happen once before with an earlier version of AP (different module, I think) without being able to replicate it, so I didn't report it, thinking it was peculiar to my system or a random occurrence.

Okay, I got the release version and tried again with that same restored clean install C: - same result on the Win98-to-ME module installed by itself. (If I had time, I'd go ahead and try MDGx's original, but there's other priorities.) I installed the same options as before, everything seems fine. Still to do: Tweaks, WMP and Other. Oh, BTW, guess I've missed info on the System.ini stuff. Followup on changes to the UPnP vulnerability Fix: If I understand you correctly, the repackaging you've done now allows the install even when UPnP isn't installed. (The original package would abort.) And further, I'm guessing, if I elect to install the XP Networking tool in the future (no desire right now) it would be wise to only use AutoPatcher to do that, so as to insure the fix is still in place. Thanks again!

I just finally got a chance to try the new code, but haven't looked at the release link yet. The AutoPatcher 1.95 installer I used was still putting kb931836 - Unofficial 2007 Updates to Time Zone Daylight Saving Time - in Manual Updates, but the Critical and Recommended Updates module now expects kb931836.exe in Hotfixes folder. AutoPatcher complained about this during install and notes the missing update file in the log. (I also see this wasn't the same executable used in 1.92.) I've not had a chance to test some of the modules yet, either, but hopefully others have done so. I guess Tweaks is good to go now, but I didn't use it. I've only (so far) used: Stability Hotfixes Windows Installer Internet Explorer DirectX 9 Critical Security Hotfixes Critical & Recommended System Updates ASPI Layer Win98 to Me (The worst thing about 'Win98 to Me' failing on my system was it was the last update, FWIW...) I see the wait time has been reduced. Reminds me, I noticed after the DirectX installation there was still lots of hard drive activity when the timer ran out, even when it was set to 20 seconds previously. Log looks correct now though. :-) (No more 'set to bypass' anomalies...)

This indicates that since in the installation of AP's "Optional Components - Windows Networking Tool (from Windows XP)" that UPnP was indeed also installed, hence the application of the patch. Hi, thanks for the link. Interesting. However, I have the Optional Components bypassed completely right now, and it's all just the same as it was with 1.92. (I don't find anything like UPnP in Add/Remove even after the patch, FWIW.) I only let the W98 machine access a couple of partitions on an NAS unit right now. W98 isn't sharing anything because I use the NAS for shared files. Yes, I ran a report just now and it reports all installed.

It *should* show those installed updates as 'installed', though, not 'set to bypass'. If you look at the same item, before the previous boot it shows 'installed', then in the current module session shows 'set to by-pass'. But apparently there's something fishy about any reports of 'set to by-pass', if I understood correctly. Thanks for clarifying. My semi-clean 98SE install was previously saved, so I don't remember what options I may have disabled in Setup, but UPnP doesn't even ring a bell. (There *is* a 'PnP OS' option in my BIOS, but is irrelevant, I guess.) Anyway, the behavior of AutoPatcher was different from 1.92 to 1.95 because I reverted to the same system before starting clean again with 1.95, partly just for kicks. Thanks for your comments. I'll have a look.

I've tried 1.95 (no Tweaks) with the same options I used for 1.92. First, I wonder if 1.92 erroneously skipped the update 'q314941 - Hotfix for Vulnerability in Universal Plug 'n' Play'. 1.95 apparently installs it, even though 1.92 skipped it, claiming I didn't have Universal PnP installed. (At the time, I imagined this might be because I had disabled it in the BIOS at one time, but no, that's no longer true.) I guess now I would suppose W98 has Universal PnP by default, and the update is installed, so I'm good. More interesting is the IReport.Log shows some weird results. Updates just installed are reported as 'set to by-pass' after the next boot. Maybe this is related to your discussion of reporting bugs. Critical and Recommended is where the trouble starts: -------------------------------------------------------------------- 10:40:20 ++ the Critical & Recommended System Updates module was started -------------------------------------------------------------------- 10:40:33 -- was installed: 98TShoot - Unofficial Windows 98se HTML Help Troubleshooting Fix 10:40:36 -- was installed: ScanFrag - Update of Defrag & Scandisk to Windows ME versions 10:40:40 -- was installed: RichEd9x - Unofficial Rich Text Controls Update (RICHED20.DLL 5.40.11.2220) 10:40:42 -- was installed: UCopy2GB - Unofficial Fix for Bug When Copying Files Over 2gb in Explorer 10:40:45 .. the computer was set to reboot. 10:41:57 .. the computer finished rebooting and started Auto-Patcher. -------------------------------------------------------------------- 10:42:18 ++ the Critical & Recommended System Updates module was started -------------------------------------------------------------------- 10:42:22 -- set to by-pass -- ScanFrag - Update of Defrag & Scandisk to Windows ME versions 10:42:28 -- was installed: UShell98 - Unofficial Fix for Bug with Windows Explorer and numerous large files 10:42:30 -- was installed: V_Studio - Unofficial Visual Studio 6.0 SP6 Components Update 10:42:33 -- was installed: NPUpdW98 - Unofficial Update for Windows Notepad 10:42:35 -- was installed: UsbmteUp - USB, 1394 & Mass Storage Device Drivers (q242975 Update) 10:42:36 -- was installed: FdskFrmt - Unofficial Fix for Windows 98 SE Display Errors with FORMAT & FDISK 10:42:38 -- was installed: 48BITLBA - Unofficial Update for Drives over 137gb (not for IBM portables) 10:42:40 -- set to by-pass -- 48BITLB2 - Unofficial Update for Drives over 137gb (for IBM portables) 10:42:42 .. the computer was set to reboot. 12:18:45 .. the computer finished rebooting and started Auto-Patcher. -------------------------------------------------------------------- 12:19:06 ++ the Critical & Recommended System Updates module was started -------------------------------------------------------------------- 12:19:07 -- set to by-pass -- ScanFrag - Update of Defrag & Scandisk to Windows ME versions 12:19:09 -- set to by-pass -- UShell98 - Unofficial Fix for Bug with Windows Explorer and numerous large files 12:19:14 -- set to by-pass -- 48BITLBA - Unofficial Update for Drives over 137gb (not for IBM portables) 12:19:14 -- set to by-pass -- NativUSB - Maximus Decim Native USB Drivers v3.1 12:19:26 -- was installed: kb925672 - MSXML 4.0 SP2 Update 12:19:27 -- was installed: SERVIC9X - Unofficial Windows 98se SERVICES Update 12:19:28 -- was installed: ADDREMOV - Unofficial Add/Remove Programs Utility Update 12:19:31 .. the computer was set to reboot. 12:21:54 .. the computer finished rebooting and started Auto-Patcher. -------------------------------------------------------------------- 12:22:16 ++ the Critical & Recommended System Updates module was started -------------------------------------------------------------------- 12:22:17 -- set to by-pass -- ScanFrag - Update of Defrag & Scandisk to Windows ME versions 12:22:17 -- set to by-pass -- UShell98 - Unofficial Fix for Bug with Windows Explorer and numerous large files 12:22:18 -- set to by-pass -- 48BITLBA - Unofficial Update for Drives over 137gb (not for IBM portables) 12:22:21 -- set to by-pass -- ADDREMOV - Unofficial Add/Remove Programs Utility Update 12:22:21 ++ All titles have finished installing. -------------------------------------------------------------------- -------------------------------------------------------------------- I think all the 'set to bypass' items actually reported as 'installed' on the command line. Haven't checked to verify any of the components. Maybe this is exactly what you're referring to already, though.

Sounds good. Yes, I'm covered. I might have a look at MDGx's original package to see if it does the same thing. I can't imagine why it bails out before copying the files, though, but I have almost zero knowledge. I would say, though, that the failure was amazingly catastrophic on my system, but I guess it goes without saying that everyone using such a package should make sure they have a reliable backup. Looks good! Thanks again for everything. Looking forward to AP 1.95!

No, silently it creates C:\Windows\wininit.ini containing text "Y". Good to know, thanks. heh, heh... mostly over my head, but good. I'll have a another look. Did I miss the instructions on enabling debug/verbose mode? Excellent, glad to know how you're thinking! Good, thanks. This probably touches on the main docs issue. I've not been actively searching out unofficial tweaks or updates, so haven't been aware of the community efforts. A few links like that in the readme would help people catch up. Without inclusion in the Auto-Patcher, I wouldn't know about it, but optional status makes me immediately want to do some research. Without a direct link or included comments it's frustrating. So this is good, thanks. Hah, nuff said! :-) All good to know. After peeking at your code, I tried my hand at a few GOTO lines to skip individual updates, and by trial and error eliminated the other possibilities for the 10-second delay. I could see I could always comment out the relevant block, too, or just snip it. Generally I wouldn't want to take out things without a good reason, because I don't *want* to have to understand all of these fixes! But it's good it isn't a monolithic executable without possibility of editing for those who wish to do so. I *have* been concerned about the whole issue of some updates requiring others, but as you say, that seems to be pretty bullet-proof in Auto-Patcher. Yes, well even poking into it and running it several times I've begun to see it very differently than the first time. Thanks, Max. :-) Well, now I've had a look at your 'complete list of updates' page, and yes, that's a large part of what I would be looking for, though in the end the MS info pages can cause more trouble it seems! But for ease of use it would be nice to have links directly in the 'features' readme or at least have an html file for the links which has them organized in the same order. But also the unofficial updates and tweaks don't seem to be there, if I'm not missing stuff, so links to threads covering those would be even more important. But I may not be very clear about what got me going on this. The very fact of having optional modules and optional features in the modules makes the user want more info if they don't already have an opinion. Depends on the type of user it's intended for. When I see you have some things set to bypass by default, I'm reluctant to set them to 'install' without more info, so I'm curious about benefits and consequences. The note you make about one of the updates eliminating the possibility to alter shortcut icons is perfect. It gives me a very clear idea of why you made it optional and why it's set to bypass by default, and made it easy to decide I want to install it anyway. Anyway, for the most part I'm one who would install *all* the critical security stuff without question (my main purpose) and nearly all of the critical updates based on your recommendation. Everything else I start to be at least a bit curious about, so including links to discussion threads on any of that stuff would be very convenient. (Not so much for me personally now - I think I'm getting there, and I'll just pester you here for anything still unclear - but to make it as clear as possible for others in the future.)

A quick note about my earlier report on the Win98-2-ME module: I mumbled something about not seeing changes in the registry - didn't realize those Keys are *deleted* so never mind. Also, I thought my failure to remove my SCSI Zip drive from the system might have caused the trouble, but another try without it produced the same failure. Oh well. Onward... I'm wondering if there's anything alarming about the message "Locate error - user variable not found" during the installation of q301540 - 'Unofficial fix for bug in Installable File System Manager' - in the Critical System Hotfixes Pack. I've run Auto-Patcher a number of times and wanted to give some further feedback per your request. In general, I think the level of information during the Auto-Patcher execution is about right, but the log could alternatively be more informative if there's more info to be provided. I still would like to find some citation for some of the unofficial fixes - some of the descriptions are pretty vague. The option 'Tweaks for Fast Computers' leaves me wondering what is considered 'fast', though I particularly doubt my 933 MHz PIII is one. ;-) At least those tweaks can be investigated, but I don't see any place a user can evaluate benefits or advisability. Also I'm curious about the 48BitLBA patch as this has been a thorny problem for 98, and a fix might need some thorough testing to be safe. (With another solution I've tried, the drive still must have partitions smaller than 137GB.) So, regarding the official patches, I'm just slightly concerned about the advisability of installing everything regardless of symptoms or relevant hardware, but I'm only an obsessive user, no real understanding of this stuff. The update for LS120 drives, for instance. MS says on a lot of these updates not to install unless the system exhibits the particular problem mentioned, but maybe that's just boilerplate language. I don't have an LS120 drive, for this example. Similarly, I wonder about q323455 - 'Directory Services Client Update for Windows 98' - in the Critical System Hotfixes Pack. *That's* the update which seems to be the reason for the ten-second delay after login, and the information page lists a lot of symptoms cured by various components, but I don't see any pertinent to me. Anyway, I'm just asking. I know you primarily intend this as a click-and-forget installer, but even for someone who wants to understand everything that's going on, this is a really nice package to have it all in one place. (I finally decided I wanted to defer some of this, like the WMP stuff, and just have the 'critical' stuff nailed down, hence my interest in installing some modules later.) If appropriate (I don't know) it might be nice to have a few more toggle options for some of the modules (though it's not hard to skip certain updates by editing the .bat files.) Thanks again for all your work. Maybe the documentation I'm hoping for is asking too much, but perhaps other users can chime in with comments for a FAQ.

Quite right. I still can't get over how many updates are packed into this thing! As you say, it may be cumulative, so no wonder. I once spent many weeks trying to assimilate the best advice on Win95 updates from places like Walbeehm's System Updates page, and it was only about a tenth of what is involved here. Thanks again for all your efforts.

I started again, selecting only the W98-to-ME module this time. Same result. The original files Explorer.exe User32.dll and User.exe are all renamed with a '.w98' extension. Not sure if the registry information gets updated - couldn't see anything changed in RegEdit even after doing it by hand. (I also then copied the three files from the Win98-2-ME folder. There was no obvious reason the files could not be copied by the script.) Somehow, I didn't find the I_Result.Log when I first ran this, but anyway it ends like this after the failure: -------------------------------------------------------------------- 00:58:00 ++ the Win98-to-Me module was started -------------------------------------------------------------------- 00:58:04 -- was installed: Win982Me - The core of Win98-to-Me by MDGx 00:58:08 .. the computer was set to reboot. So anyway, then I ran Auto-Patcher pretty much with defaults, with Win98-to-ME on 'Install' to check. It seemed happy, and the other updates seemed to install fine. Generated a report afterward which seems as expected. I think another user may have also noticed this, but I have a long delay after login after booting - about 10 seconds. I'd be happy to help test the Win98-to-ME issues on this system, but for now it looks like it's solved for me. I still want to try to learn more about some of the updates and options, and I'm curious about some of your reasons for the default install/bypass setup.

Hmmm... more on this later, but currently the partition is *not* hidden. I can't remember how I set this up, seemed to be a bit of a trick, IIRC. I have a vague memory of trying to hide the alt PriDOS and messing things up - couldn't get it back. (It shows up as one of the last drive letters, before or after a Secondary Master physical drive I try to hide in BIOS, but which Windows finds after boot anyway.) Great! That's what I thought. Yes, however once into the Auto-Patcher I suddenly realize there are several modules I know nothing about, and want to go ahead with the obvious ones. Which reminds me - I know there's a lot of info about what Auto-Patcher does, and I've skimmed it, but some people (like me) could use a quick summary of some of the modules. I don't own XP, so I have only the vaguest idea of some of the post-98SE features. I'm sure I'll find what I need to know eventually, though, so don't waste any effort - just if it's already in front of me but I can't find it. Good, thanks. I'll give it a shot.

I had restored C: back to a point where only hardware drivers had been installed, just prior to my first installation of the SESP2. (In case I'm an id***, I have to say that I have a second primary DOS partition which I switch to 'Active' and boot into, in order to 'backup' by copying my 'real' system partition. AFAICS this doesn't cause problems, but it's unusual, so I'd better mention it.) (Hmmm.. the system seems very sensitive - should I say 'fool' instead? Surprising...) Well, it does remind me of the grief I had trying to install DirectX 9.0c in earlier installations. Protection bits set by default (and re-set on every boot IIRC!) caused the MS installer to fail without any details. I only found the answer from other users. There is nothing installed other than hardware drivers at this point. I'm planning to restore to that state again and look at User.exe properties, then either install *only* the Win98-to-ME module or else install Auto-Patcher defaults *without* the Win98-to-ME module. Then I could try installing Win98-to-ME on its own and see if that works, then go back and try it again with Auto-Patcher. But if you think my unorthodox backup routine is questionable, it doesn't give you any reliable info. Also, I'm wondering still about effects of omitting some updates and opting to re-run Auto-Patcher to pick them up later, if the order makes a difference or if that's fairly bullet-proof in the checking routines. There's a lot of stuff I'm not aware of or sure if I want/need - MSDA/JetEngine, .Net Framework, etc. - and I'd be inclined to only install the critical updates first but wanted to pretty much follow the Auto-Patcher defaults the first time. (But I didn't strictly...) I'm guessing you would have mentioned any logs or markers to look at, so I'll probably not save anything from this first try. Any other ideas on best procedure (no w98-ME, w98-ME first, etc.) would be welcome, but I may have a go before you're on again. FWIW, the error Windows spits out seems broken, too: "Windows could not upgrade the file [blank, several lines] from [blank, more lines] : " I was suprised that a missing User.exe causes the system to shut down - I still haven't managed to catch the last bit of the error message! Thank goodness for the alternate Pri DOS partition.

First, thanks for this effort! An amazing amount of work! I've finally gotten around to having a try installing the 1.8 package with 1.92 updates. (It took me a long time to realize that the 1.8 exe file was really an unpacker, not the real installer!) I restored my 98SE system back to just after most hardware drivers were installed, so basically clean. I changed very few of the module options, but will be wanting to get more details on some of the modules at some point. (Still amazed at how much is in here!) Anyway, on my system the Auto-Patcher fails during the Win98-to-ME module. I get a "Windows could not upgrade the file" message, then a prompt to press any key to continue. Briefly, I see "Error loading User.exe" (and a bit more, I think) before the system shuts down. Looks like System\User.exe is renamed to 'User.w98' and the module doesn't proceed past that point. I haven't found any pertinent log files on that module, but I've left the system partition and the 'autopach' directory alone for now, so let me know if there's something to look for. Additionally, though you may have already addressed this, I'm not sure if it's recommended to go back and install optional modules later, in no particular order. My next step, of course, will be to install without the Win98-to-ME module. Thanks again for this very interesting project! I had followed the Unofficial SESP after stumbling on it, and found the Auto-Patcher thread while checking for updates after SP2.1a.