soporific

re: Paint error stuff: sorry, that's most likely my fault ... i put it together pretty quickly and its really something i should leave to MDGx. i will post him what i have and ask him very nicely to fix up my mess. re: Revolutions Pack 7 in the manual installs folder: its a silent install package that cleans up the installation files after its all done. IF you need access to them, just extract the contents of the package as opposed to running the installer. You may need to install WinRAR to be able to extract the files.

The $win_nt$.~ls directory is used by setup as the location of the source for all install files. It doesn't 'become' i386, it is deleted after setup has finished using it. But i'm commenting on an unattended method i'm not familiar with. Sorry i can't help further.

I dunno if this helps, but i get a very similar message when i forget to include the root directory files from the Windows source. Ie, when trying to make unattended CD for Windows XP Pro SP2, if you don't include "win51ip.sp2" in the root directory, setup asks for the CD. Have you included all the files in the root directory of your source CD in your project?

yes but in those cases, surely it would be up to the user to notch the value down. I wonder if there is a command line tool that would tell us how much video memory is being assigned. Then we could overcome even this. Here's my new table: reasoning: * why are there no settings for 64 MB RAM and under? MS recommended 64 as the RAM to use for optimal usage at the time the OS was designed/released. I trust they know what's best for these RAM sizes. If anyone has documentation that says the opposite, please post a link. * No MinFileCache setting: i agree that there isn't any good reason behind setting a minimum MinFileCache value ... well, no reason i know of. * the 1 gig settings: I think that if MS knew about the 1 gig limit and assumed that a user may have this, then i would think it safe to allow the maximum MaxFileCache setting possible as opposed to an 'optimal' setting. I find the arguments of people who have tested extensively with 1 gig compelling to use. * The Chunk File settings: - as i understand how chunk file settings work, i don't agree with leaving this at 512 for the higher RAM values. I must admit to not having tested this idea out in practice but you can't just create any old test to prove whether this will improve performance, i'm yet to be convinced of whats been said so far. Theoretically, if you have lots and lots of RAM, using larger chunks is more efficient when moving large amounts around. Whether or not you get much of a % increase in completion time is what i would be interested in. and UBCD 4.6.2 will be setting MaxPhysPage lower than 39000 because users with more than 1280 will not get thru the install process. I have just tested with 20000 then and it works, 39000 didn't work and this was without any AGP aperture setting of note.

seriously, you can set your watch by MDGx ... just not this month for the first time in ages. It just goes to show ... human beings need holidays! It's about time he took a break We've got things covered till you get back MDGx!

thanks to everyone for their replies and stay tuned for my new table! I may even make Dencorso happy with this one

i remember very clearly my transformation from a local Windows 98 updater (you know: friends, family, the guy down the street, etc) to the guy that puts out Auto-Patcher and UBCD for a wide international audience and it was DEFINITELY because of this forum. I was sick and tired spending hours and hours on re-installs of Windows 98 and i was sure there was a way to 'automate' it. I searched and searched and the web pages that always seemed to come up were from this place called MSFN. So I lurked for about 2 weeks, got all the info that i needed, and went to work. When the first version of UBCD was working and it did the job, i was SOOOOO over-joyed that i had created this enormous time-saver that i immediately stopped lurking and basically posted the instructions of how to do your own UBCD. That was version 1 way back in 2005 and hasn't it come a long way!?! The first UBCD had 33 hotfixes which was all that Windows Update said i needed. Boy did i have no idea how worthless what Windows Update reported was !! LOL. Anyway, if this forum wasn't filled with the sort of passionate DIY computer engineers like i am, i wouldn't have hung around. And Eck, "greatest thing since sliced bread"? Oh shucks dude, how does a guy kept a semblance of modesty when people talk about his projects like that? Still, thanks anyway. But like you said, the real credit goes to the team working together by providing feedback to each other using this forum. Yay!

Thanks for the replies. I've just confirmed that using another method, i've got WU to report that i need the updates i previously reported i didn't. I did this is by leaving off every update from the slipstream except IE7 and WMP11 and checking in with WU. All the updates that you said should be there, were there. Curious, very curious.

Yes there is. Those flashing network icons are part of Tihiy's Unofficial Improved Replacement Tools, so open up Control Panel, open "Add/Remove programs" and look for "Unofficial Improved Replacement Tools". Choose to uninstall, reboot and it will all be gone. You can always re-install via Auto-Patcher if you want it back. Thanks for the feedback.

Hey there ... thanks for all the work on the list, i've been using it extensively for the last few hours trying to get my unattended CD up-to-date, and now i've got some questions ... 1) KB890859: how critical is this ... i've left it off my test CD and Windows Update doesn't complain. It's also not listed in RyanVM's Windows XP Post-SP2 Update Pack which was last updated June 2007. But it IS in the last AutopatcherXP. What's the best way of determining if this has or has not been replaced by a newer update? 2) as well as kb890859 above, this is the list of updates i left off the CD and which Windows Update doesn't complain about being missing: * kb890859 * kb891781 * kb899587 * kb899589 * kb900725 * kb902400 (missing from MSFN list, but listed in AP) * kb904706 * kb914389 * kb917537 * kb917953 * kb918118 (i'm adding to it as i go) 3) I'm also using the last ever official release of AutoPatcher XP (August 2007) as a guide and i was wondering why the big differences between the 3 lists i'm using that i've mentioned (ie this one, RyanVM's, and Autopatcher). I want to know which list to best rely on! 4) kb891122: should have been listed as a 'removed' hotfix when wmp11 was added. Please correct me if i'm wrong. 5) i'll probably have more questions soon! Thanks in advance for any help on these questions!

Yes to all your questions. Seriously, i consider very carefully the question of user friendliness and i think the installation and usage of Auto-Patcher for Windows 98se is very user friendly.

This is the settings table i'm working from to set the values in the AutoSYSTEMini project i'm working on: as you can see there's two values i'm not sure what to put for ... if anyone has ever used over 1 gig, what did you use for the MaxPhysPage value? Did you use it? If anyone has any comments about the table, please type now or forever hold your peace!

Java 5.0 Update 13 made it in, but the latest 98MP10 hasn't as yet. See details below. Latest News: Oct 15: The final September 2007 UPGRADE is now available: September 2007 UPGRADE - 31.2 MB MD5: BBF60F778688E7DB98FA36D08C163A97 Please Note: There are a few changes to the final September Upgrade release which will make your Auto-Patcher slightly newer than the FULL release. Changes from the UPGRADE version and the FULL (beta) version are listed below. Change log: September 2007 Final new: Backup4all 1.3.0 (file & directory backup) (optional) update: AutoSYSTEMini Tweaks Installer version 1.5 (the original version was 1.0) update: Sun Java 2 Runtime Environment 5 update 13 (optional) Change log: September 2007 beta new: TriEdit - Cumulative TriEdit & DHTML Edit Control Vulnerability Fixes new: kb932590 - Unofficial TZ Environment Variable Errors Fix new: MSPaint - Unofficial MSPaint Update and Graphic Filters Pack (optional) new: Contrl98 - Unofficial Control Panel Applets Lockups Fix new: Revolutions Pack 7 by Tihiy (manual updates folder) update: 98KrnlUp - Unofficial Update for KRNL386.EXE (4.10.0.2000) update: RichEd9x - Unofficial Rich Text Controls Update (Sept 2007) update: Q891711 - Unofficial Fix for Newer Cursor & Icon Format Vulnerability (updated INF code) bug fix: the q329048 hotfix wasn't installing due to wrong file number check value bug fix: the PNGFIX in the Manual Installs folder was broken.

Philco I've tried Spybot with various different RAM sizes and least amount of system resources i could get was 17% with 64 MB of RAM. The average i got overall was about 40% free. So on my test system (with hardly any programs installed), it works fine. How much RAM have you got installed, and what figure do you normally get for system free resources when Spybot isn't running?

um, i think this is a better place to ask this question: http://forums.spybot.info/

For those who were excited by the new v1.5 of Spybot - Search & Destroy but only to be disappointed by less than sterling performance... get the new beta version from here: http://forums.spybot.info/showthread.php?t=18788 - the very long start time is no more - other slowness problems seem to have disappeared. Thanks to SubMix8c who put me onto this. EDIT: for those who want to include this on their UBCD, here is the new silent installer: - it installs the new beta release of v1.5 (as above) - it installs the latest updates as of Oct 10. - NOTE: this is a SILENT installer. Once it starts, that's it, let it run. - also note: it sets Tea Timer active which is a system settings change notifier. If you don't want this active, you can turn it off in the settings. link: http://soporific.dsleague.com/downloads/SpyBotSnD_1.51.exe

OK, i've been on the receiving end of some USER.EXE, USER32.DLL and EXPLORER.EXE muckups quite a few times and it really is the simplest thing to fix if you know what's going on when this happens. Yes it p***es me off no end when it happens, but, again, it is the easiest thing to fix. For me. But what about others? I think its high time the "keep Windows 98 alive" crew, which is most of us regular posters in the "Unofficial Win98 SE Service Pack" section of MSFN, create an automatic hotfix solution to fix all those caught up in the maelstrom of our system patching activities. I'm specifically talking about the USER*.* issues. Not everyone who takes a punt by installing these updates knows what to do when it all stops working, especially the problem that stops the OS from even loading. If this is your only connection to the internet, its highly inconvenient to get a fix for the problem by the usual way of asking for help online. I know the REAL solution would be to create hotfixes that don't muck a system up, but the real world shows us its still possible. And when the solution is so easy i think its high time we provided one for the community. So who wants the kudos for getting this fix together? I have some ideas if someone wants to help out...

You need the DOS RAR module which is available from their website. I've also sent you a PM. I wonder what it could be?

Have you got MaxPhysPage set to anything in SYSTEM.INI with bugs appearing when MaxFileCache is set to 131072?

dencorso good call, i hadn't followed the links! I'm wondering why you put 4096 as the minfilecache for all RAM variations? What's your reasoning? I was playing around with huge RAM sizes in Virtual PC and the most i could get reported by the OS was 1158 MB. This was what the OS reported, when there was actually 1500 available. To get 1158 MB I set MaxPhysPage to 48899 and this was the last possible setting before windows wouldn't load. Thanks for those kb article links I had heard that there was a usable limit of 1 gig of RAM for Window 98se but i never knew why. That the answer is that Win98se or even WinME weren't designed for that much RAM is just so typical. So, actually, my fix of setting MaxPhysPage to 39999 is actually a very sound thing to do. Use the left over ram for the RAM drive as has been suggested. So the file that was released inside UBCD v4.6.0 called "MaxPhysP.exe" is fine to use after all. yay.

here's a link that explains all:http://soporific.dsleague.com/downloads/copyfile.htm i got it from the INF guide that MDGx keeps a copy of at this location: http://www.mdgx.com/INF_web/INF_WEB.ZIP

OK, so does someone want to suggest the best/ideal SYSTEM.INI settings for RAM sizes starting from 512 MB and going up? Heck, why not start at 32 MB ? Here's what i have so far, please feel free to suggest changes: RAM ... MinFileCache ... MaxFileCache ... ChunkSize 32 ...... 4096 ....... 8192 ...... 512 64 ...... 8192 ....... 16384 ...... 512 128 .... 16384 ..... 32768 ...... 1024 256 .... 32768 ..... 65536 ...... 1024 512 .... 65536 ..... 131072 ...... 1024 1024 ... 131072 ... 262144 ..... 2048 1536 ... 131072 ... 262144 ..... 2048 2048 ... 131072 ... 262144 ..... 2048 4096 ... 131072 ... 262144 ..... 2048 my plan is to create an AutoFileCache hotfix for the UBCD project that will add the best settings during setup.

joe tweaker: i've found the exact page where you get confused about which version to go with: my guess is try the v31.40h files and if it all seems to work, then as this is the latest package by far (3 years difference) the only thing is whether they are telling the truth about the drivers also supporting Win98se. The clincher for me is the way the whole web page is laid out, each heading has the name of just one version of Windows. This makes these headings unreliable in terms of meaning and so i would go with what it says it supports, so the v31.40h files are definitely the best bet to thoroughly test and then go with if it tests out. please let me know which drivers you are going to go with and i will add them to the packs. here's the latest list: Index for the Driver Packs for Windows 98se v1.01 __________________________________ DP_w98_1.01.exe 7.65 MB extracts to 27.0 MB DP_w98_2.01.exe 10.4 MB extracts to 51.1 MB DP_w98_3.exe 13.9 MB extracts to 48.4 MB DP_w98_4.01.exe 1.41 MB extracts to 3.71 MB DP_w98_5.01.exe 9.23 MB extracts to 41.5 MB total: 42.2 MB extracting to 171.71 MB uncompressed __________________________________ ** Driver Packs 1 ** ATI Radeon 9800 series ATI Radeon 9700 series ATI Radeon 9600 series ATI Radeon 9500 series ATI Radeon 9200 series ATI Radeon 9100 series ATI Radeon 9000 series ATI Radeon 8500 series ATI Radeon 7500 series ATI Radeon 7200 series ATI Radeon 7000 series ATI Radeon Xpress 200 series ** and all "All-In-Wonder" variants of the every ATI Radeon series family above. SiS 315 SiS 530 SiS 6326 SiS 635 SiS 645 SiS 733 SiS 735 Trident Blade XP-T64 S3 ProSavageDDR Realtek 10/100/1000/ NIC Family (network) ADMtek AN983B (network) Realtek RTL8139 (network) LanKom LB-1200U (network) VIA VT8233 (network) Winbond W89C840 (network) __________________________________ ** Driver Packs 2 ** SiS 650 VIA-S3 UniChrome VIA VT8361 VIA VT8601 VIA VT850 ATi Rage 128 ATi Rage 128 Pro Voodoo1 Voodoo2 Voodoo3 Voodoo4 Voodoo5 Voodoo Banshee __________________________________ ** Driver Packs 3 ** NVIDIA GeForce2 Integrated GPU NVIDIA GeForce2 MX 100/200 NVIDIA GeForce2 MX/MX 400 NVIDIA GeForce2 GTS/GeForce2 Pro NVIDIA GeForce2 Ti NVIDIA GeForce2 Ultra NVIDIA GeForce3 NVIDIA GeForce3 Ti 200 NVIDIA GeForce3 Ti 500 NVIDIA GeForce4 MX 4000 NVIDIA GeForce4 MX 420 NVIDIA GeForce4 MX 420 with AGP8X NVIDIA GeForce4 MX 440 NVIDIA GeForce4 MX 440 with AGP8X NVIDIA GeForce4 MX 440SE NVIDIA GeForce4 MX 440SE with AGP8X NVIDIA GeForce4 MX 460 NVIDIA GeForce4 MX Integrated GPU NVIDIA GeForce4 Ti 4200 NVIDIA GeForce4 Ti 4200 with AGP8X NVIDIA GeForce4 Ti 4400 NVIDIA GeForce4 Ti 4600 NVIDIA GeForce4 Ti 4800 NVIDIA GeForce4 Ti 4800 SE NVIDIA GeForce FX 5100 NVIDIA GeForce FX 5200 NVIDIA GeForce FX 5200 Ultra NVIDIA GeForce FX 5200LE NVIDIA GeForce FX 5500 NVIDIA GeForce FX 5600 NVIDIA GeForce FX 5600 Ultra NVIDIA GeForce FX 5600XT NVIDIA GeForce FX 5700 NVIDIA GeForce FX 5700 Ultra NVIDIA GeForce FX 5700LE NVIDIA GeForce FX 5700VE NVIDIA GeForce FX 5800 NVIDIA GeForce FX 5800 Ultra NVIDIA GeForce FX 5900 NVIDIA GeForce FX 5900 Ultra NVIDIA GeForce FX 5900XT NVIDIA GeForce FX 5900ZT NVIDIA GeForce FX 5950 Ultra NVIDIA GeForce PCX 5300 NVIDIA GeForce PCX 5750 NVIDIA GeForce PCX 5900 NVIDIA GeForce 6100 NVIDIA GeForce 6100 nForce 400 NVIDIA GeForce 6100 nForce 405 NVIDIA GeForce 6100 nForce 420 NVIDIA GeForce 6100 nForce 430 NVIDIA GeForce 6150 NVIDIA GeForce 6150 LE NVIDIA GeForce 6200 NVIDIA GeForce 6200 A-LE NVIDIA GeForce 6200 LE NVIDIA GeForce 6200 TurboCache(tm) NVIDIA GeForce 6200SE TurboCache(tm) NVIDIA GeForce 6500 NVIDIA GeForce 6600 NVIDIA GeForce 6600 GT NVIDIA GeForce 6600 LE NVIDIA GeForce 6600 VE NVIDIA GeForce 6610 XL NVIDIA GeForce 6700 XL NVIDIA GeForce 6800 NVIDIA GeForce 6800 GS NVIDIA GeForce 6800 GS/XT NVIDIA GeForce 6800 GT NVIDIA GeForce 6800 LE NVIDIA GeForce 6800 Series GPU NVIDIA GeForce 6800 Ultra NVIDIA GeForce 6800 XE NVIDIA GeForce 6800 XT NVIDIA GeForce 7025 NVIDIA GeForce 7050 PV NVIDIA GeForce 7100 GS NVIDIA GeForce 7300 GS NVIDIA GeForce 7300 GT NVIDIA GeForce 7300 LE NVIDIA GeForce 7300 SE NVIDIA GeForce 7500 LE NVIDIA GeForce 7600 GS NVIDIA GeForce 7600 GT NVIDIA GeForce 7600 LE NVIDIA GeForce 7650 GS NVIDIA GeForce 7800 GS NVIDIA GeForce 7800 GT NVIDIA GeForce 7800 GTX NVIDIA GeForce 7800 GTX v2 NVIDIA GeForce 7900 GS NVIDIA GeForce 7900 GT/GTO NVIDIA GeForce 7900 GTX NVIDIA GeForce 7950 GT NVIDIA GeForce 7950 GT AGP NVIDIA GeForce 7950 GX2 NVIDIA GeForce 7950 GX2 v2 NVIDIA GeForce 8300 GS NVIDIA GeForce 8400 GS NVIDIA GeForce 8500 GT NVIDIA GeForce 8600 GT NVIDIA GeForce 8600 GTS NVIDIA GeForce 8800 GTS NVIDIA GeForce 8800 GTX NVIDIA GeForce 8800 Ultra NVIDIA Quadro2 MXR/EX NVIDIA Quadro2 Pro NVIDIA Quadro4 380 XGL NVIDIA Quadro4 550 XGL NVIDIA Quadro4 580 XGL NVIDIA Quadro4 700 XGL NVIDIA Quadro4 750 XGL NVIDIA Quadro4 780 XGL NVIDIA Quadro4 900 XGL NVIDIA Quadro4 980 XGL NVIDIA Quadro DCC NVIDIA Quadro FX 1000 NVIDIA Quadro FX 1100 NVIDIA Quadro FX 1300 NVIDIA Quadro FX 1400 NVIDIA Quadro FX 1500 NVIDIA Quadro FX 2000 NVIDIA Quadro FX 3000 NVIDIA Quadro FX 3400/4400 NVIDIA Quadro FX 3450/4000 SDI NVIDIA Quadro FX 350 NVIDIA Quadro FX 3500 NVIDIA Quadro FX 4000 NVIDIA Quadro FX 4500 NVIDIA Quadro FX 4500 X2 NVIDIA Quadro FX 500/FX 600 NVIDIA Quadro FX 540 NVIDIA Quadro FX 550 NVIDIA Quadro FX 4600 NVIDIA Quadro FX 5500 NVIDIA Quadro FX 5600 NVIDIA Quadro FX 560 NVIDIA Quadro FX 700 NVIDIA Quadro NVS NVIDIA Quadro NVS 210S NVIDIA Quadro NVS 285 NVIDIA Quadro NVS 440 NVIDIA Quadro NVS 50 PCI NVIDIA Quadro NVS 55/280 PCI NVIDIA Quadro NVS with AGP8X NVIDIA Quadro PCI-E Series __________________________________ ** Driver Packs 4 ** ALi1621 nForce2 (chipset) nForce3 (chipset) nForce4 (chipset) VIA USB 2.0 (usb) VIA HyperionPro 5.12 (chipset) __________________________________ ** Driver Packs 5 ** Realtek AC97 WDM Driver (v4.01) - (audio drivers)

The guy releases a fix to a real problem, one that had me stuck for a solution, and you reply that its not much of a fix. Well, from where i'm sitting, it's a great fix and only changing 20 bytes twice means it's a very efficient patch! He didn't say it was going to save the world, he said if would fix certain things and it does. Xeno86, don't worry, he can be a bit tactless sometimes

good suggestion but it has prompted the plea for more help, see first post for details The voodoo files are all basically identically named and it is getting increasingly harder to work around the limitations of the method i'm using. Any help is so much appreciated if there was a world record for the amount of appreciation ever given i'm a shoe in for second place on this issue. I reckon i hold first place as well! That's a story for another time, its a good one though. I should write a book ...