soporific

OK, this is quite annoying. At least 6 of the 7 updates Windows Update thinks are needed, are NOT needed. In particular, for the official cumulative update for Internet Explorer 6, I tried very hard to get this installed but also keeping Windows Update happy when the unofficial cumulative update is subsequently installed. No luck --- all I managed to do is get the files installed properly so when Windows Update "re-installs" kb916281 all it does is tell *itself* that it has now been installed. Sheesh!! All the updates (except q323172 which I'm investigating further) are in this category -- i.e when Windows Update re-installs these updates, nothing of value is added to your system. If there was a way to stop Windows Update giving these false readings I would definitely employ that way, but it seems not. So I will put a disclaimer somewhere advising that this is the case and not to worry about the results of using Windows Update.

Change log: v1.10 * Improved code in COPYMOVE.reg, Fast_Web.reg, and Perform.inf (thanks to MDGx) * Added new settings to perform.inf * improved pack files layout

Wow, as always. You are a living treasure.

That's a bummer ... oh well, the update is included but only in the manual installs folder. Thanks for hosting it!! Yep, i keep a close watch of your updates thread these days and I saw that. Thanks for pointing it out again tho.

scratch that. I've just revised the C2GBME.INF, COPY2GB.INF, FE.INF & SE.INF files to deal with this problem. I'll send you the updated INF files. the updated KERNEL32.DLL files will now be copied as KERNEL32.NEW to the Windows\System folder and the INF files will make WININIT rename the old kernel file [from kernel32.dll to kernel32.ori] and WININIT will also rename the new kernel file [from kernel32.new to kernel32.dll] - all this according to the revised INF files. this will ensure the old kernel file gets renamed AND the new kernel file gets renamed from kernel32.new extension to kernel32.dll, even when re-installing the Copy2Gb Kernel32.dll fixes This was the exact reason i made an installer for an older version of Copy2Gb --- to account for those trying to re-install it. Well, to be completely honest, to account for ME trying to needlessly re-install it and breaking my boot routine (can't find kernel32.dll) -- I should have made a bigger song and dance about it at the time, you may have been able to use some of my batch code.

It may be useful for you to post the version of SYSTEM.INI you used that caused the hard disk thrashing, and also the specs of the hardware. All info would be useful. And if you have the time, going thru the settings one by one may find the culprit and help improve the tweaks pack. Thanks for this ...

I found some info for the PageOverCommit setting -- but what does it all mean? It seems to be saying that DON'T apply this tweak if you don't have much memory but apart from that I'm stumped. Any info much appreciated ... PageOverCommit=20 - Specifies the multiplier for determining the amount of linear address space the Memory Manager will create for the system. The amount of linear address space that the Memory Manager will create is computed by rounding up the amount of available physical memory to the nearest 4 megabytes and then by multiplying that value to the value specified for this setting. You can specify a value between 1 and 20. Increasing this value increases the amount of available linear address space, causing the size of data structures to increase. This also increases paging activity proportionately and can slow down the system. The Default is 4. And while I'm whining, why does microsoft provide excellent information about SYSTEM.INI settings for Windows 3.1 (!!!) but I can't even find a mention of even one setting for the Windows 98 SYSTEM.INI --- (actually I lie, I can find references to ConservativeSwapfileUsage=1 but that is it !!) the M-Z of the options for Windows 3.1 SYSTEM.INI can be found here: http://support.microsoft.com/kb/83436

Hi there, This thread was inspired by the one started by Problemchyld but I thought it prudent to start another as I plan to maintain the pack and provide regular updates. [see below for the change log] Here is the list of tweaks contained in the attachment: ADV_IE.REG ---- The 'Advanced Internet Options' tweak from Auto-Patcher for Windows 98SE. Adds many more options to the Advanced Internet Options tab. ADV_WE.REG ---- The 'Advanced Windows Explorer Options' tweak from Auto-Patcher. Adds many more options to 'Folder Options' in Windows Explorer. AR_DIS.reg ---- Disable CD autorun AR_ENA.reg ---- Enable CD autorun COPYMOVE.reg -- adds Copy to... and Move to... menus to explorer shell DEL_MSN.reg --- deletes the MSN icon from the desktop after first boot to desktop (useful for unattended boot CDs) DMA_ON.INF ---- The 'Turn on DMA access to hard disks and CD/DVD drives' tweak from Auto-Patcher. It turns on DMA access for hard drives and for all future drive additions. DOSHERE.INF --- adds 'Command Prompt Here' to Right-Click Menu when clicking on a folder EditReg.reg --- changes the default behaviour of registry files from MERGE to EDIT --- useful for coders who open .reg files more often than installing them EnabMenu.INF --- Enables the Boot Menu (you can alternatively use TweakUI) Fast_Web.reg --- increases the number of simultaneous internet connections per server from 2 to 8 FixAttrb.reg --- In a clean install of Windows 98 Second Edition, the Attrib column is lost in Windows Explorer’s “Details” view. Use this tweak to restore it. IconCach.reg --- fixes very common problems of icons not refreshing and displaying properly, by increasing your icons cache size NoSsaver.reg --- Stops screen savers from forcing restarts of interrupted Defrag operations Perform.inf ---- adds high performance tweaks to system.ini (adjust settings to suit your computer!) Rest_New.reg --- Fix for missing "NEW" command in Windows Explorer, or in right-click menu StopLogo.inf --- Disables the Boot Logo (you can alternatively use TweakUI) ThumNail.reg --- fix to restore Windows Explorer’s thumbnail preview capability for a dozen different image types. See info folder for more info. Win2k_scheme.reg -- adds the Windows 2000 style theme to the list of available themes in Windows 98 SE systems Other files inside the pack: InstTwk.bat --- a sample batch file that can be modified to install the INF tweaks Info (Folder) -- all the documents i've come across that may help you tweak your computer Change Log: v1.30 - added 4 new tweaks: ADV_IE.REG, ADV_WE.REG, DMA_ON.INF, Win2k_scheme.reg - added new file "How to increase system resources in Windows 95/98" to info folder. Tweaks120.zip Win98_TweaksPack_1.30.zip

Ok, the version I used to have for Internet Explorer 6 sp1 was the "full" version --- but that was still missing all the language packs -- -all the Full version installs is the auto-language selection thingy ... so it seems the best thing to do is actually include all the language packs and these files will be copied tot he hard disk before installation. This should solve all potential probs. It does however double the size of the package. So if there's no reason to include the language packs I'd like to hear it to save space.

MDGx, regarding your new NUSB24.EXE ... I've got it installing properly ... my code can differentiate between 23e and 24 ... but there's one teeny weeny little problem ... it prompts if the USER wants to reboot even when I use the /Q:A /R:N switches .... so it can't go into auto-patcher yet ... but I want to release v1.8 very soon !!! Can you look into this? Cheers mate. PS - thanks for the info about the Timezone updates --- your notes did say that was the case I was just being a bit paranoid and wanted to be sure.

Actually, this seems to be the best bet ... I can use NSET to search for the line containing 01.04 and if it can't find then the title can be installed, if it is found, I then check the next line to see if its blank or has something there --- I don't even have to do any math because as long as Maximus Decim keeps the same style of reporting which version it is, shouldn't be a prob. So thanks for the tip!! EDIT: I have tested the above method and it works a treat. Hardly any code, and no math calculations. Here's hoping Maximus D keeps the same format for versioning the INF file.

I'm a bit confused by this point... 1) doesn't ScanFrag install the ME versions of scandisk and defrag?? this is what my Updates list tells me: ScanFrag - 2005 Mar 23 - 521kb - dl I - Unoffical update of Defrag and Scandisk to Windows ME versions (highly recommended) 2) this situation is unlike the duplication in the XP mp3 codec and MDGX's WMP replacement pack --- in that situation, both can be installed from AutoPatcher, sorry i mean auto-patcher, but in this case, the user doesn't have the option to install the full Win98 to ME pack --- but if I'm wrong about point 1, then it will be good to offer it as an optional install ... maybe I should do it anyway (make it optional) ... I'll decide after some feedback

4th Jan, 2007: Added to main list: PNGFIX (by Tihiy) A note: just because I don't post a new message, doesn't mean the list isn't being updated. Sometimes I am just too busy ...

MDGX, regarding your latest Timezone hotfixes ... Can I confirm with you that you now only need to install Q928388 and not also Q929120?? My testing revealed that absolutely nothing of value is installed with Q929120 when the latest version of Q928388 has already been done ... but I have been known to smoke a spliff or 6 so I could be hallucinating ... and thanks as always for these unofficial hotfixes, it will soon be the case that auto-patcher has more unofficial hotfixes than the mouldy old official ones ... and better ones too!

I think one of the reasons for insisting the program check to see if an install is needed before installing, is so all my coding work can be seen!!! All the other service packs just do their thing regardless and all the magic is hidden away ... The main way I check to see if all the checking code works is to run auto-patcher twice. It is only when I have nothing installing the second time around that tells me if it works. So, i'd be interested to know the results of running auto-patcher a second time after the first run has finished. Your log file should report that nothing was installed. Can you do this for me and post the result? Or just report that nothing installs if that is the case. Cheers man. I also re-edited the post before yours, re-read it can ya? The broken link to v1.7 --- maybe I should lay off the green stuff ... there were orignally 2 links to the v1.7 update --- so what do I do? I delete the one that works, leaving the link to nowhere as the only place to get v1.7 --- D'OH !! --- and I nearly couldn't find the URL !!!! I found it near the bottom of my history list in firefox .... geez I love my firefox!!

Eck, I'll try out the "IE setup files on the hard disk" thingy and get back to you... is there a quick way to check if this works? What can we do to force the OS to try to refer to the place it thinks the IE cab files are kept? NEW QUESTION: regarding MDGx's latest version of NUSB24.EXE ... I am now including this as a proper install within auto-patcher (instead of a manual install) but to properly code for it I need to create a new routine. I have eliminated virtually all installs that will go out of date but to do this for NUSB24.EXE is a bit tricky. The problem is how to differentiate between NUSB24.EXE and NUSB23e.EXE, but also future-proof the title. A problem will occur if i only check for the file size of USBSTOR.INF --- if a future version is released and someone installs this manually, and then tries to run the existing auto-patcher, the method above would try to re-install the old version. This probably won't matter too much (the old version just wont install anything if the hotfix is compiled properly) but it breaks the philosophy of this project --- nothing should be installed if it isn't needed. And the report function would give false reports about this title, which is a no no. The way I've worked out is to perform 2 checks ---- the main difference between all the releases of NUSB seems to be USBSTOR.INF and so one of the checks will be checking to see if the size in bytes of USBSTOR.INF is exactly 20,387 bytes but in order to future proof it, I should also check the file version of one of the files. So my first question is: ... which of the files included in NUSB24.EXE that we can check the file version of, is MOST LIKELY to be updated in a future version of this title??? Or can people think of another way to solve this problem ... let me re-state it just in case --- the problem is: how can we see if this title has already been installed WITHOUT stopping future versions of this title from being installed? If we can differentiate between NUSB24.EXE and NUSB23e.EXE then the problem should be solved. Its just that it seems that all the files that we can check the file version of --- they are all exactly the same in both NUSB24.EXE and NUSB23e.EXE --- hopefully I'm wrong because this would solve the problem, but it seems not. What's a guy to do? Oh, and the next release of this project i want to be a BETA release --- can anyone see a problem with this? Also, a new dedicated hoster for auto-patcher will be available soon -- as soon as I can get a CD to a guy in Canada, it will be available. And I will also be releasing a combined version of the unattended boot Cd project and auto-patcher. I'm just testing it now, but it is SOOOOO GOOD to be able to set whichever custom version of Windows 98 I want (ie keyboard & regional setting, etc) and then start the install and two hours later have a completely patched and ready to go clean installation of Win98se. No MSN icon on the desktop, Dial-Up Networking 1.4 gets installed automatically (it installs nicely with a RUNONCE command just before the last reboot of the installation process), and AutoPatcher, sorry I mean auto-patcher, starts automatically and runs all the way to the end. Jolly good show it all is. BUT ..... I'm sure this could do with more collaboration. Whoever wants to join forces with me to make a really kick-arse version of the combined UBCD and AP, IS MORE THAN WELCOME!!!! We will completely split the credit.

There is duplication going on here ... I didn't realise the XP mp3 codec was installed along with MDGx's killer replacements pack. But then again, you now have the option of only installing the codec if that is useful for some reason. I can see why you would want this all neat and tidy (ie you know and your system knows where the IE setup files will be) --- my strategy for installing Windows 98 from CAB files already on the hard disk is for this very reason --- so any future updates can be run and the OS knows where to look for the Windows 98 second edition CD. So, it looks like we should do the same when installing IE ... what I will do is create a special directory in the Windows directory to hold the cab files, and install it from there if its needed. But before I do this can people please give feedback on my proposal. Now that MDGx has released another version of NUSB24.EXE I'll have another look into device driver issues.

1) let me get my practical response out of the way first. I have changed all references to AutoPatcher for Windows 98 etc etc, to now read auto-patcher. I have dropped the capitalization of the A, and will put a hyphen between the words "Auto" and "Patcher". Happy now? I couldn't give a flying f**k if you're not. 2) unauthorised? who gave you the authorisation in the first place to reserve the word autopatcher for your own exclusive use? usually its only governments backed up by the power of the state that get away with this sort of sh*t. so i'd like to know, which army, navy and/or airforce are you going to send to who knows where, to enforce these restrictions? 3) The other way to approach this would be to enter into negotiations with me over this question which would have avoided the nastiness of my second point. You indicated on the other forum that you had no idea why I would post something like I did. Gee, maybe telling the world that the auto-patcher for windows 98 se actually existed was a possible reason. Especially when I read the thread where someone was asking where they could download it. I actually posted into that thread advertising the existence of my project but it looks like that was ignored. 4) And so, because of all this &^%$& this project is now worth just one star... not that I was counting or it really matters, but this a******e seems to be trying to get back at me in every way possible.

if you make a backup of your system files before running autopatcher and then compare them after, you'll be able to see the changes --- lines are added depending on which tweak is applied. v1.7 full is available now on ED2K and in a few days on a public server

ed2k://|file|Autopatcher_for_Win98_v1.7_update.rar|32507679|4F018E44BE91794B841AD9D28B6D7B2A| ed2k://|file|Autopatcher_for_Win98se_v1.7_Full.exe|207043044|E727A0593ACC10520AEB3442191DDFA6| Powershared on release

AutoPatcher for Windows 98se v1.7 alpha has been released... see the first post

Yep, I definitely agree with your approach here ... it is definitely an optional install, and can be easily avoided. I was going to include it as a default install but I'll bow to your comments about giving users the option to easily just install the essential OS file updates, and if people want it, they can set it to be installed through the options function. There's 2 main menu pages in autopatcher and I've tried to keep them separate --- page 1 has all the essential hotfix updates, etc, and page 2 has all the optional stuff. So all these extra optional stuff will be tucked away in page 2 which you can just ignore if you don't ever want to visit it.

Sorry, mate, I'm not using it, so I don't need it.But I'm only 1 person, I can't speak for anybody else. Fair enough, its gonna be hard to speak for other people ... i suppose I'm after opinions about its usefulness -- if its a complete waste of coding space, then i definitely won't bother. It sounds like its one of those Apps for Newbies things that most people avoid like the plague ... but having said that, its not very big in size, and there's a hotfix for it as well

That's fine, go ahead -- I'm sure lots will be happy there will be 2 languages available -- if you need some help with understanding what I've done, just ask. I've started work on the essential 3rd party apps module that will contain things like 7-Zip which i consider to be an absolutely essential installation on any Windows OS. The question then is: what else should go in? The size of the app is quite important ... i'd say over 10 mb would disqualify it... And I know its the bloody silly holiday season but no comments on MS Agent? UPDATE: just finished coding 7-zip into autopatcher --- i'm now using LOCATE.COM which finds a file anywhere on the system, so autopatcher should be able to determine if: 1) you have 7-Zip installed anywhere on your system (ie if its not in the default location) and 2) if you have the latest version. This might sound like a no brainer, but trying to do it all in DOS was not that easy. Anyway, i'm quite happy with the functionality !! B) Just thought i'd let you all know...

Thanks for your reply and feedback about autopatcher, its been rather scarce... Please confirm that you have tried the following: 1) run the autopatcher 1.5 file 2) exit out of an error messages you get and exit out of all DOS boxes 3) run the autopatcher 1.6 file - the program should now open and run correctly. version 1.7 will be out very soon and so you can always try that one -- I will release a 1.7 update and also the full file now that I have a hoster so there should be a solution soon! regarding MS Agent 2.0: Should I include this in autopatcher?