soporific

NO i'm pretty sure you won't be able to do that. In your situation, i would probably consider a re-install of the OS but keeping the existing programs already installed (if there's nothing wrong with them) ... the OS will need updating but just run AP. To do this do the following: 1) make a backup of WIN.COM (which is normally in C:\Windows) and then delete this file (or rename it to something else) 2) Use your Installation CD to start Windows setup. Because you have deleted or renamed WIN.COM the setup program will allow you to continue. 3) After the OS has re-installed, you will need to run AP to get your system up to date.

Hey problemkid, don't be down or anything ... i LOVE your avatar!!

Well, is there any more information about your problem that you can share? At the moment, one of the 189 updates contained in AP is causing the problem. If i can't replicate the problem in front of me, i don't have much chance of trying to find a fix for it. These are some of the things you can do: 1) post your log file so i can see what you were trying to run. I've already mentioned this! 2) just tell me which modules you ran, and also which optional updates you ran, or you could just send me your log file, whichever is easiest. 3) inform me what 3rd party apps you have installed that possibly could be causing a conflict See how you go with that

C & P from the first post: Fri June 22, 2007 There is 1 new release: * June 2007 sp2 Upgrade - 19.5 MB - you need version June 2007 or later already installed. - the June 2007 sp2 Full release will be uploaded in the next few days What's new in June 2007 sp2? * Sun Java Environment 5 update 12 has been added to the 3rd party apps module --- this is why this release is so big! * New versions of: Unofficial Cumulative Security Update for Internet Explorer 6 sp1, Unofficial DirectX Media (DXM) 6.0 Update for Internet Explorer 6.x * Windows Media Player 9 now has a new version checking routine. Previously if you uninstalled WMP9, AP would still think it was installed (thanks to Mazabuka who pointed this out) * fixed some documentation errors in Modules.rtf (thanks Mazabuka) * the color scheme function has been removed until i can fix the dos window hang problem * a new option has been added to the Internet Explorer module: you can choose to only install IE6 sp1 and skip installing the updates. * If you don't have Outlook express on your machine, then the two updates for it won;t be installed. Please note: installing IE 6 sp1 installs Outlook Express and it cannot then be uninstalled from the Components dialog, you must manually delete the files. * a new routine has been added to ManiCode.bat which reduces the needed environment space for certain hotfixes including q314941 and q323172.

i will indeed hang in there ... for you i would hang from a mountain cliff top ... wait, let me think about that for a sec .. I'm just about to release the next version and i've fixed everyone else's concerns except yours ... i can't replicate the problem you are experiencing ... are there any questions i haven't answered you need answering? You know what you can do to help us with your wordiness ... please do a summary !! -- this means you'll be able to rave away to your hearts content just as long as you give us the short version at the end !! Cheers man.

OK first remember that Auto-Patcher is an automatic hotfix installer so the problem should lie in one of the updates, not in AP itself. Are you saying that simply installing AP (but not running it) causes this problem, or are you saying after you have patched your system with AP that the problem arises ... which one is it? Assuming it's not a problem simply installing AP, we need to find out which update is causing the fuss. Can you please see if you can narrow down which update it is, and also, when you report any errors in the running of AP, please post your log file and or report file text so i can see which modules you were trying to run. See the recent posts by Nathanson1947 where he doesn't always say much, but he does always attach his log files that tell me lots and lots about what he was doing when the problems occurs. This makes helping him very easy and makes me happy to help ... all you are saying at present is in effect "Auto-Patcher isn't working for some reason" and i need more info to properly help ... cheers.

Everyone who's asked a question, i will respond eventually. But for now: 1) The first post is where you should always look for the latest information. 2) If you install later versions of AP over earlier ones, of course you are going to have some files that are not needed anymore. NUSB30.exe and NUSB31.exe are a good example. If in doubt, just delete the entire folder of the old installation, and then install the new version of AP. Then you won't have any unneeded files will you ... I have spent a bit of time on the new installer and it handles updating the uninstall information quite well i think, so use them with confidence! 3) I will release June 2007 sp2 in the next day or so, everyone please upgrade - these updates will only be a meg in size. EDIT: actually, i can see a way you won't be able to do no. 2. If you haven't got any of the new Full versions, then you are relying on the updates on top of 1.95 PR2 ... OK fair enough sorry for not thinking it through ... the other way to see if a file is needed is to move it to a safe place and then see if AP complains. The error checking should pick it up. Other than that you're just going to have to ask me if you're unsure.

changelog: * fixed all documentation errors (thanks Mazabuka) * the color scheme function has been removed until i can fix the dos window hang problem * a new option has been added to the Internet Explorer module: you can choose to only install IE6 sp1 and skip installing the updates. * If you don't have Outlook express on your machine, then the two updates for it won;t be installed. Please note: installing IE 6 sp1 installs Outlook Express and it cannot then be uninstalled from the Components dialog, you must manually delete the files. * a new routine has been added to ManiCode.bat which reduces the needed environment space for certain hotfixes including q314941 and q323172.

This is all good info. There's a few jobs i have to do for the next release and so i will work on trying to fix all these issues. Thanks for persevering with this, you are definitely greatly helping to improve this project. Good on you ... and you have also mastered the art of posting on MSFN. Now, if only some other people could get a hang of it ...

Has this always happened? Does this always happen? Does this happen if you don't change the color scheme? I think it's a bug in the new color scheme option -- i'll look into it ...EDIT -- do you load ANSI in your system startup? Look in Config.sys and Autoexec.bat and see if there is any reference to ANSI and report back please. That's a good point, others have made it as well, i'll add this to my to do list ... so can i confirm, in your case you have totally removed Outlook Express so the file named MSIMN.EXE is nowhere to be found on your computer?and Jack (nathanson1947), you may want to look into performing a re-install --- it sounds like it might need one in your situation. But then again if your system is working fine then apply the 'if it aint broke don't fix it' rule.

C & P frm the first post: Latest News: Oops: um, there's a couple of reasons i have to release June 2007 sp1 - it won't be big. sorry! Its nothing major, 2 updates aren't the very latest but you should install the upgrade just in case. Available soon ... Sat June 16, 2007 There are 4 new releases: * June 2007 Full - 263 MB * June 2007 Upgrade from 1.95 PR2 (or later) - 64 MB * June 2007 sp1 Upgrade from May 2007 (or later) - 7 MB * June 2007 sp1 Upgrade from June 2007 - 1 MB What's new in June 2007? * code cleanup and some minor bug fixes * a freeware CD burner app added to the 3rd Party module. * Notepad has been added to the \bin directory so the user doesn't have to have this on their machine. * all recent unofficial update releases by MDGx have been updated. None are new titles though. Notes on the 1.95 PR2 Upgrade release: * This will upgrade any version of Auto-Patcher for Windows 98se v1.95 PR2 or later * the installer has been improved from the ones released previously. It is now highly recommended to let the installers do their job as opposed to moving the program directory around manually.

MDGx: You know me, i can always find something that can be improved ... if you were just an average joe, and saw the following entry in the Add/Remove list: " Remove Unofficial USER32.DLL + USER.EXE Fix" would you have any clue at all what it was referring to?? I bet even some regulars to MSFN would probably scratch their heads in a year or so ... "hmmm, that does ring a bell but bugger if i can remember what issue is being fixed" --- its the Q891711 fix for those who were wondering --- i make this point because of AP ... it's getting out to people who have never visited MSFN and they will have no chance of being able to match the updates. I could make this comment about a few of the unofficial fixes floating around (and they're not all yours MDGx) but this one really stands out IMHO. My preference is to come up with as short a descriptive title as possible, keeping the key words or at least the KB number in the title. Eg this is what i've gone with for Q891711: "Unofficial Fix for Newer Cursor & Icon Format Vulnerability (Q891711)" Incidentally, i've kept the old official fix in AP for a good reason, and i've used this for the title: "Official Fix for older Cursor & Icon Format Vulnerability (kb891711)" When seen both together, the user is left in NO doubt about what is being fixed, as they can look up the issue using the Q or KB number. My other gripe is the consistency of the Add/Remove list when a user installs all the unofficial fixes. I feel we are cheating a bit by putting that space at the front to force putting the update at the top of the list. Why are our unofficial updates so important that we upset the alphabetical list ... wouldn't it be good to just put the same word at the start eg "Unofficial" and so they will all be grouped together. I know its a bit late now and i'm not suggesting releasing all the old ones again, but i thought i'd say it all what has been wanting to be said for a while now. Having said that, please keep up the fantastic effort at keeping Windows 98 alive and kicking. You're the greatest!

Thanks for that info MDGx! ... Jack, how'd you go with that file? News: the June 2007 release will be available soon. I have to start getting a system together for releasing Full editions and Update editions -- i'm sure you don't want to download 260 MB each month and i don't want to upload that each month. So, i'll get on this ... in other news, the code has been changed to re-check each module even if there is no reboot. This means some updates that are going to 'loop' will actually loop instead of installing the once (but not installing) and then you only realize if you run AP again. You'll see what i mean when you see the new version. So coming soon: * The full June 2007 release * Update any May 2007 version to June 2007. ie Update May 2007 or May 2007 sp1 to June 2007 * Update 1.95 PR2 to June 2007 (long overdue!) Stay tuned ... Oh yeah, remember how i was saying i was going to build a test system with Norton Anti-Virus ??? Well i did and the test system lasted a day before i overwrote it in a fit of utter frustration. PLEASE, OH PLEASE do not use NORTON SYSTEMWORKS or NORTON ANTI-VIRUS and wonder why your computer is so slow, buggy, unstable, and generally much the worse off. I may even go as far as code a warning into AP ...

IF you don't have msjetoledb40.dll, you will get a message like that. Please do the following: 1) do a search for msjetoledb40.dll to see if it is actually on your system. If it is, please note down the file size, and also see if you can determine the file version (look in its properties) Notes: This file seems to be installed when the OS is first installed, so it should always be there. If your system can't find it or doesn't recognize it, this is a problem. I have tried to find the original file in the OS installation files, but i can't find it as such, but it is already installed on a fresh system. If anyone else has more info, please say something ...

DO us a favour can you and do a search of the program folder for the following file: kb918144.exe and run it. If everything is OK you can back out of the installation, but my guess is you will get to see what the error message is telling you. Please let me know what happens!

I've looked at your log file -- very useful as it goes back quite a few versions, do you have any older ones by any chance? Has it always said it was looping thru for those 2 updates? Did any version of AP work properly ie without looping thru?the most likely scenario is you don't have those updates ... what's happening is AP says it's installing the update, but in the background there's some sort of error message we aren't seeing because all the updates are run silently. This is actually happened to 3 or 4 other hotfixes and i know how to fix the problems. It looks like a service pack 2 is coming soon. Stay tuned ...

Good news: - i've fixed the "CTRL-C doesn't exit the DOS screen automatically" problem --- if you want to fix your version without downloading anything, look inside MainCode.bat and find the following line: echo EXIT>> "%WinDrive%\Run-Mod.bat" and add this line directly BEFORE it: echo CLS>> "%WinDrive%\Run-Mod.bat" otherwise it will be fixed in the next release. Oh, and there will be a freeware CD-Burner (InfraRecorder) added to Optional Components.

I always like feedback, even if its buried within mountains of unnecessary text. I'll repeat, even if its buried within mountains of unnecessary text. Me thinks you still haven't got a hang of trimming your posts... ask if you are unsure or need help I agree. I'll add something else. 1) OK, i've got a valid reason why we need to increase the user's ES if they haven't got much. Using someone's actual AUTOEXEC.BAT file, i was able to determine that even trying to assign just one letter to one variable created environment space (ES) problems. This means ANY process that uses COMMAND.COM and also has to assign a variable isn't going to be able to. I have one hotfix that is in this category and simply won't run on the test system i was using without giving more space overall. So if a user fails my ES test (which isn't very stringent) then they are likely to get into trouble, AP aside even. The fix is as i've gone with for this reason. 2) I have 2 fixes actually. The first one assigns the variable CLASSPATH to Nul if it exists. On my test system, this solved the problem without having to resort to the CONFIG.SYS fix. I did however make it a little bit harder to pass the test just to ensure that people with little space (as opposed to hardly any space) would also be trapped and informed about their low ES. Ah ha !!! We have some answers at last ... if i can just give my experience with Norton AV ... i used it from about 1997 to 2000 and stopped because it was starting to consume so much of a computer's system resources. Any computer that was 'old' would take forever loading up and the whole business of 'maintaining' the product was a chore, with so many compatibility issues to sort thru. Norton AV is probably the reason why there are messages asking you to ensure you don't have your anti-virus 'protection' turned on while you install a particular program. I mean, why this unwanted and time-consuming obstacle? "Can't they design an anti-virus product that DOESN'T require the user to, unbelievably, TURN OFF the so-called protection, just so you can legitimately install a program?" was my thinking about 7 years ago. They probably have fixed this by now but then again here we are talking about how we need to turn off AV protection just to even USE a program! Way to go, Symantec. Now i have another test system to create, one with Norton AV on it ... oh well such is the life of a [insert something suitable] No, if you have that selected in the modules menu, then any missing hotfixes should be reported. Maybe you are talking about the report generated when you choose the option from the MAIN menu (not the module menu) ... anyway, please select the Rare and Obscure hotfixes in the modules menu and run the report again to see if the report still misses them out. It seems fine from my testing. Well, you see, the only reason that START_ME.bat exists is to give Autopach.bat enough space to run. So it defeats the purpose using another file to give the space to START_ME.bat --- my thinking is that if the user can't even run a simple DOS windows without getting into trouble, we need to FIX the cause of the trouble rather than trying to tunnel around it. This is an interesting idea. I could even design it to be reasonably automatic, so all you would have to do is drop a new 'config' text file into the right folder. I'll look into this, thanks heaps for the idea ...

Eureka !! Why i didn't think of that .... i need to take a break !!! Thanks for that ...

Try manually setting DEBUG=Y inside START_ME.BAT ... the only difference between START_ME.Bat and START_DEBUG.bat is that. That could only be because the system can't find NOTEPAD.EXE in any of the locations set by the PATH statement. Have you done something with notepad? The reason i asked that is because Windows 98se is notorious for needing re-building, especially for systems that have seen lots of installing and uninstalling. When i see a system like that, that gives errors and such when trying to run stuff normally, i dont't waste one second trying to solve the problem, the first thing i do is prepare the computer for re-building. The only choice i make is whether to try to simply re-install the OS (for systems that don't seem too bad or old) or do a clean freash re-install (for systems that crash regularly). Now, the reason i do this is because THIS FIXES THE PROBLEMS! The time it takes to do either of the above is sometimes a lot quicker than trying to solve these problems. No, its going to help track down what is wrong. What you could do: set up a VM and install Win98 on it. Then install all the programs you have on your current machine, on the test system and try to set it up exactly the same. You will then be able to see if you can replicate the problems on both systems. This project simply WOULD NOT EXIST if i didn't have access to VM software. Please try the following: * please set AP to only search through individual modules, one at a time. ie set AP to search thru the Stability hotfixes module only, and then set it to search thru the tweaks module, etc. Please report what happens. You say that the program is crashing when it gets to HPSecure (the critical security hotfixes module), so unless there is more information for me, AP should get thru the individual modules and report what it finds? Why do you think the code gets executed in a different sequence? Some things may not execute, but it is ALWAYS in the same order. Please explain how it can be otherwise ... The fact that DOS 7.1 doesn't have things like FOR loops is actually one of its strengths, the command set is tiny. In my experience, the only thing that can go 'Out of bounds' is the environment space which gives a very similar message to array errors ('Out of environment space'). When each module is invoked, the following variables are passed to it: %WINDRIVE% %WINDODIR% %LOC8% %MARKER% (this is actually %TRACK% from ModMenu.bat)

thanks for the info .... i never noticed that you could have more than one COMMAND.COM on your system. I knew about the one in the Windows directory but it never occurred to me it could be in two locations. So, it looks like i can just use like you pointed out. The way i've gone with is to add a REM line to AUTOEXEC.BAT which is totally harmless to do which also fixes the problem. But i will probably change it if we get to the bottom of this saga!I'm still interested in hearing more on this subject though. Anyone?

This is all just from the first post: Latest News: Wed June 6, 2007 there is a possible problem with the May 2007 release and so a service pack is being prepared. Yes, that's right i've completely bought into the MS 'service pack' terminology. The problem is with the Environment Space fix (see this post for more info. I've worked out a way to avoid all the problems (even though i don't know what is causing them) and so please upgrade ASAP. The other change is that when you exit the program using CTRL-C the program doesn't exit out. This is now fixed. Grab it here: upgrade May 2007 to May 2007 sp1 file size 277 kb - MD5: EEBCBE32542D307BAE67192431B19506 you will need May 2007 already installed. the May 2007 release is finally out! Grab it from here: May 2007 (v2.0) file size: 259 MB - MD5: 1B14F7B790627C17522A64C88E3FD074 Notes: * the installer is much improved: - If you choose to install the new version over the old one, all old registry uninstall information is now deleted (it wasn't before meaning you had the program listed twice in the Add/Remove programs list - when you uninstall the program, the shortcut folder is now deleted, and so are the desktop icons (they weren't before) - option available to delete entire install folder when uninstalling which deletes any module save files and other logs and reports. * an update from 1.95 PR2 to May 2007 will be available soon ...

Ok here's the line i added to the first post: Also, not every single update is on this list. Updates for Internet Explorer 5.5 are NOT included, neither are any unofficial upgrade packs. So that clears a few more from your list. I will eventually get around to going thru the rest so please stay tuned ... I have already made quite a few changes. EDIT: do i have to add EVERY single old "Cumulative Security Update for Internet Explorer" to the obsolete list? eg. IE834707 - OLD Unofficial MS IE 6.0 Patch --- actually this for IE 6 and not IE6 sp1 --- i'm in two minds about whether to add this to the obsolete list because it isn't obsolete for those who haven't upgraded to IE 6 sp1. Comments?

OK, what's going on here: 1) something about my fix for a lack of environment space is causing a major bug that is sooo weird it should be the new definition for weirdness. All the fix does is add the following line to CONFIG.SYS SHELL=COMMAND.COM /E:4096 /P 2) if i install this fix on a totally clean newly installed OS it works fine with no problems. When i run AP on it to fully patch it, there are still no problems afterwards (which is how i was testing). 3) if i install this fix on a totally patched system i get the following error: Can't find COMMAND.COM 4) a fix for this problem is simply adding SET PATH=%PATH% to AUTOEXEC.bat and the problem goes away. Even just adding a REM statement to AUTOEXEC.bat fixes this problem !!!! I have been testing exactly what 'fixes' this problem and it seems that if the size of the AUTOEXEC.BAT file is zero the problem is there, but if AUTOEXEC.BAT is even 1 byte in size or over then the problem is NOT there. All i did was add a space to AUTOEXEC.BAT and the problem is fixed. The problem also goes away if i change the line added to CONFIG.SYS to SHELL=C:\WINDOWS\COMMAND.COM /E:4096 /P But this means that if the user has COMMAND.COM in a different directory its not going to work. And i can't use: SHELL=%windir%\COMMAND.COM /E:4096 /P which would avoid the different directory issue. You can't use environment variables in CONFIG.SYS WHAT IS GOING ON ???????????? .... far out this AP project is giving me gray hairs before my time !!! Thanks in advance for any comments or help.

OK, this is getting a bit serious ... 1) AP works perfectly fine on a newly installed OS. 2) AP works perfectly fine on systems with large PATH statements 3) AP gives general protection faults on your machine. That tells me that there is something particular to your system that is causing all these problems ... it may or may not be something in the code and that is what i want to determine. It is also possible that your system is a bit screwed and is giving you these messages as a result. ie this problem is either something to do with AP or something to do with your system. can you please tell me more about the system you are trying to use AP on ... things i want to know: 1) how old is your OS installation? ie how long ago did you install the operating system and do you re-install the OS regularly? 2) please post the contents of your configuration files (PM me) - use SYSEDIT to bring them up and just copy and paste into a text file. the files i want are: CONFIG.SYS AUTOEXEC.BAT SYSTEM.INI WIN.INI Please try the following: 1) manually add the following line to your CONFIG.SYS file: SHELL=COMMAND.COM /E:4096 /P and then try the program again. If you get a message saying the system can't find COMMAND.COM then add this to your AUTOEXEC.BAT file: SET PATH=%PATH%;%windir% (why the above is needed is beyond me) 2) consider learning how to use a virtual machine program (MS Virtual PC 2007 is decent enough) and try the program out on a test system. You should be able to see AP working perfectly well on a new system. See how you go with all that.