Dave-H

Hi Soporific, I have just tried to use the new December 2007 full release of AP, but unfortunately I'm getting the same problem as I had with the previous version. I did manage to use the one before that successfully, but the last two versions won't run! When I run them the DOS box comes up and then immediately closes down. If I run the debug batch file, it runs OK until I press "any key to continue" and the same thing happens, it just closes! No error messages, nothing........... I have tried increasing my environment in config.sys manually from 768 to 4096, and even to 8192, but this makes absolutely no difference. It still won't run if I close down all other running programs. It will however run in Safe Mode, at least the DOS box stays open and will respond to commands, but I haven't tried actually using AP in Safe Mode. Is this OK to do? I would have thought that there would be things that it cannot do properly in Safe Mode, like system analysis. Any idea why it won't run in the first place? I did get the version before last to work OK, and I haven't changed any settings to my knowledge, so why would later ones now not work? Unless AP changed something itself of course which is preventing it from running again! Thanks, Dave.

Amen to that!

Thanks again, I had missed that link to UserAss. Got it now! The Registry Compactor program that I found is here http://www.majorgeeks.com/Registry_Compactor_d3504.html Seems to do the same job I suspect, especially now I've er, enabled it! I also found a program called "Registry Space Profiler" which I found very useful. You can find it here - http://www.tliquest.net/software/rsp/ It shows the sizes of the various sections of the registry, so you can see what's taking up the most space. In my case, the "Interface" section is the biggest, at 2,039,736, followed by the "CLSID" section at 1,926,404. All the other sections are very much smaller, but there's an awful lot of them of course!

dencorso, thank you so much! I have downloaded and deployed all the tools you mention, except UserAss 1.2, which I couldn't find anywhere to download. My searches only kept coming back to http://www.utdallas.edu/~jbs024000/software/index.html which doesn't seem to work any more. Do you know anywhere else I can download it from? I've removed all the UserAssist keys from my registry manually anyway, and I assume that's all it does. Registry Compactor only actually compacts the registry if you pay for it, but even without its full functionality it's worth having to tell you how much empty space there is in the registry. I assume that the Norton Optimisation Wizard, which I have been using for ages, does exactly the same job. My starting point was with system.dat at 12,273MB. I've now got it down to 11,677MB. The biggest drop was when I ran oleclean, when it dropped from 12,273 to 11,801. I couldn't believe how many invalid entries there were! Obviously I'd like to get it down to a bit smaller than that, but that will do for now! Thanks again!

soporific, I'm getting exactly the same problem as Bankis. The October full release installs OK but won't load, exactly as he describes. The DOS window, both in normal and verbose mode, just disappears, with no error messages. I've tried running the August full release again, which I had already run and used successfully a couple of months ago, but it won't run now either! Exactly the same result. It obviously isn't a problem with your program, something has changed, at least on my system (as the August release did work), which is now preventing the batch files from executing. I have tried the Environment Space fix which you suggested, and it did what it said on the tin, but makes no difference to the problem. I am intrigued by its adding of "REM -- please leave this REM line here" to autoexec.bat. What does that do exactly? Great program BTW, I was very impressed indeed with the August release when I did manage to run it!

Well, I'm still at it! Got the system.dat file down to 12.269MB now....... Checked with TonyArts EasyCleaner, which showed all green lights, no spurious entries. I would have been surprised if there had been, as I've always regularly checked the registry with Norton Windoctor, which does the same thing, and removed or corrected any invalid entries. Thought I would go into DOS and try a scanreg /fix routine, just to see if that made any difference. It got to 78% complete, and then told me - "Windows found an error in your system files and was unable to fix the problem. Try deleting some files to free up disk space on your Windows drive. If that doesn't work then you will need to install Windows in a new directory." What a load of rubbish! I certainly hope that nobody has actually reinstalled Windows in a new directory as a result of this nonsense. I assume that it failed because, as was mentioned earlier, scanreg chokes on any registry bigger than 8MB, which as far as I can see makes it completely useless, at least in my scenario! I will backup the files now and see if clearing the MRU and run data helps.........

Well, I have uninstalled .NET v2, which seemed to go OK, and removed an awful lot of registry keys. My system.dat file went from 12.689MB (which is right on the edge of allowing the system to boot!) to 12.333MB. Obviously worth having, but not as big a reduction as I had hoped considering that there had been over 1500 keys associated with .NET v2! This has now gone down to about 50 keys which still reference the .NET v2 folder. The registry compacter that I use routinely is part of the optimisation facility that came with Norton Utilities 2002. There do seem to be many others around, are any of them likely to be better than the Norton one? There was no change in the system.dat file size until I ran the optimisation wizard, so presumably the deleted keys just leave empty space until that is done. I do have the TonyArts EasyCleaner (v2.0.6.380) so I will have a go with that. I was disappointed that I only reduced the system.dat size by a few 100 KBs of size be removing .NET v2. I had been hoping for more. What I really want is to reduce it by a couple of MB, but I don't see how i can possibly do that without removing a lot of stuff that I actually still want to be able to use! eidenk said on Nov 11th that he got 6MB out of the registry by manual pruning. I can't imagine that I would ever be able to remove anywhere near that amount of data without crippling the whole system!

Thanks adamt. Sorry for the huge delay in responding, but I wasn't getting e-mail notification of replies as I should have been. Yes, the reference on page 319 of that book does look very familiar, even though it refers to Windows ME. Possibly this "bug", whatever it is, was perpetuated in Windows 2000. Unfortunately, the page which contains most of "solution 2" isn't available in that preview of the book! Anyway, I had already solved the problem by running Windows setup again, which has made the problem go away, at least for the moment.......... Thanks again, Dave.

Thanks all, especially to eidenk and dencorso for all their contributions to this thread. As the thread starter, I'm sorry I haven't contributed to it recently, but I wasn't getting any e-mail notification of replies for some reason. One development, that I have now noticed on my system, is that the boot problem actually seems to appear in two stages. I was always getting the VFAT error BSOD on startup if system.dat got too big, and I've been trying to prune it down as much as possible, both by using automatic compacting programs, and by careful manual editing. If the system.dat file size is below around 12.5MB the system boots fine. If it gets above that, but still below about 12.7MB, the system doesn't blue screen on startup, but just stops on a flashing DOS cursor after the splash screen, and never goes any further. Above about 12.7MB system.dat size, the VFAT error BSOD appears. I don't know if this gives anyone any further clue as to what's actually happening here. I'm still looking at removing all software that writes a lot of registry data, and which I don't use much, to work around the problem, and get the registry size down to a level where I don't have to keep worrying about the system failing to boot all the time! I read that the .NET framework is a big registry data writer, and I have both v1.1 and v2 installed. I still need 1.1 as I know that I have software which I don't want to uninstall which uses it. I am thinking of removing v2 though, as I suspect that alone has written a lot of registry keys. Does anyone know what sort of applications might need .NET v2 as opposed to v1.1? Thanks everyone. Dave.

Thanks dencorso, that's really interesting, and sorry that I've only just seen it! I'm particularly interested in the bit about ".......the SYSTEM hive and the Windows kernel files must fit below 16 MB when Windows starts." That or something similar could well be the case in Windows 98 as well, and could well explain my problem! If this is a fundamental limitation on registry size in Win98, I'm very surprised that it doesn't seem to be more generally known about..............

Thanks for the replies guys! All my ftp sites are listed in the registry under - HKEY_CURRENT_USER\Software\Microsoft\Ftp\Accounts This includes an entry for the site I'm trying to add, which seems to have all the correct information! It just doesn't have an icon in "My Network Places", which is what I'm trying to add. Permissions seem to be OK for this key, with full access for all except restricted users (I'm an Administrator). The ftp site I'm trying to add works fine if I use a shortcut in my Internet Explorer Favorites. It isn't a problem with that specific site, I get the same error message if I try to add any site to "My Network Places" using the "Add Network Place" wizard. It just won't complete the operation, saying "the parameter is incorrect". A typically unhelpful M$ error message. How much more useful would it be if it actually told you which parameter was incorrect?!

Sorry to just bump this, bad I know, but has no-one any ideas on this? I have managed to find one other reference to the same problem, on another forum, but again no answer offered. I just don't understand why my "Add Network Places" wizard, which has always worked for me in the past, should suddenly be refusing to let me add any new entries.........

Already checked that page long ago, several times! Everything stated there as a possible cause of the VFAT loading error has always been correct on my system, but when the error appears I still get that error message BSOD and the system hangs. I do remember doing a logged boot several times when I first had the error, before I isolated it down to being related to the registry size, and I think the boot actually croaked on loading the ndis driver. If I did a step by step boot, and skipped that driver, the boot completed successfully. This is of course the same as disabling the network adapter.................!

Thanks everyone. I'd be interested to see the translated pages too please eidenk. [EDIT] Oh, you've posted tham! BTW, I eventually opened your .7z file with WinRAR. As you say, it's strange that WinZip won't cope with it, but I have found a few other compreesed archive formats which only open with WinZip and not WinRAR, and vice versa...... In reply to Sfor, I don't think that having 1GB of memory is causing the problem. There has been much debate on here and elsewhere as to whether Windows 98 can run happily with that amount of RAM fitted, and whether it can actually use it if it is happy! I think the concensus is that there should be no problem with 1GB of RAM, as long as a few tweaks are done, all of which I have done. I've been running like that for quite a few years now, and everything has been very stable on Windows 98 and runs very well. I don't ever need to have a swap file, it all runs in memory. What I am intrigued with is the possibility that scanreg is the source of the problem. If it really can't cope with optimising a registry larger than 8MB, and it's set to check and compact the registry on bootup, it is very possible that it's actually falling over when the registry gets very much bigger than 8MB. This could well prvent the boot from continuing, although it still doesn't explain why the boot will complete if the network adaptor is disabled! This does seem to be a bit of a major design flaw in scanreg, as the registry on a system with many large pieces of software installed is inevitably going to end up considerably larger than 8MB in size! I have disabled start-up optimisation as suggested, and I'll see how it goes. I can always manually optimise the registry with the Norton Optimisation Wizard, or any of the other programs I've kindly been pointed to. Thanks again, Dave.

Thank you so much for that eidenk, that's really helpful. I will certainly look at all those references closely. I downloaded the file from Rapidshare, but what do I open .7Z files with? I assume it's some sort of compressed archive, but WinZip doesn't want to know it! It does look at first glance as if the Japanese guy's method of compacting the registry relies on exporting the sections as text files and then merging them back in again. The Windows Optimisation Wizard in Norton Utilities works pretty much the same way I think, to remove empty space in the registry files, and that is what I've been using to keep my registry size down to a minimum. You can in fact backup the entire registry as a text file and re-import it, which will do pretty much the same thing I think. I am still very puzzled as to why this is happening on my system though. I really can't believe that Windows 98 has a limitation that will prevent it from starting just because the registry has got too big! There was a key data size limit I believe on Windows 95, which was removed in Windows 98, and I know you can set a maximum registry size on NT based systems, but everything I've read says that there is no limitation on registry size in Windows 98. As I said before, I can only assume that it is a problem with the registry not loading properly into memory on start-up. Does anyone know exactly where in memory the registry loads? Is it always loaded into a specific address range? If so, it is possible that on my system the amount of memory available for the registry isn't as big as it should be for some reason, maybe because something on the motherboard is taking some of it up. Perhaps the network adaptor resources, which would explain why it will boot if I disable it. Any more ideas anyone? Thanks, Dave.

I have an issue with my Windows 98SE system which I'm hoping that one of the many Win98 experts on here may be able to shed some light on. It first came up when I tried to install Office XP on the system. The install went fine, but when I re-started, all I got was the dreaded "VFAT unable to load" BSOD. It would boot in safe mode, and by trial and error, I discovered that if I disabled my network adaptor in Device Manager, it would boot normally. I could then re-enable the adapter, and it worked fine, but the system wouldn't start normally with it enabled. I also started to get all sorts of error messages about the registry being corrupted if I tried to test its integrity with utilities like Norton Windoctor. Eventually I had to fix the problem by using scanreg to restore an earlier version of the registry, but this of course didn't contain the necessary keys for Office XP. To cut a very long and painful story short, I had to abandon Office XP (it is actually a dual boot system with Windows 2000, and I now use Office XP just on Windows 2000, with no problem.) Since then I have had this happen again a few times when I've installed new software, and it seems to happen if anything complex is installed which writes a lot of registry data. What appears to be happening is that the boot fails if the registry gets to above a certain size, and it seems to be specifically if the system.dat file gets to above about 12.5MB in size. I recently proved this (I think!) when it happened again when I tried to upgrade to WMP 9 from WMP 7.1. The VFAT error came back again on the first reboot after an apparently successful install. As an experiment I saved some of the Realplayer registry keys as exported files, and deleted the keys. (Realplayer installation writes huge amounts of data to the registry.) The system then booted fine. I merged the keys back in, and the system wouldn't boot again! The system is just on edge on this, as I have been able to cure the problem occasionally in the past by compacting the registry by using an optimisation program. However I have now uninstalled the Realplayer, which has reduced the registry size considerably, so that I'm not in imminent danger of this happening again if I install something! Realplayer was the obvious thing to remove as it does write a huge amount of stuff to the registry, and I didn't use it much anyway. I'll probably just install RealAlternative now instead. I should say that Realplayer always worked perfectly when it was installed. So, does anyone have any idea as to why this was happening? Everything I've read on this subject, and believe me, I've searched a lot, implies that the size of the Windows 98 regisrty is limited only by disk space and memory. I have a huge amount of both. The symptoms seem to indicate to me that something is happening when the registry files get to a certain size which is preventing them from loading into memory. I have 1GB of RAM, which Windows 98 seems to be recognising and using. My motherboard is a Supermicro dual Zeon server board (Intel chipset), which I gather hasn't been tested with Windows 98, but seems to work fine apart from this issue. Could it be a motherboard issue? Does the Windows 98 registry go into some special place in memory which isn't as big as it should be for some reason? Is disabling the network adaptor somehow releasing space which is allowing the registry to load? If anyone has any clues on this, I would be very grateful to know, because no-one I've asked so far has even ever heard of this happening before! Thanks, Dave.

Yes, Windows 9x does not function correctly with Universal Extractor. Beginning with v1.6, UniExtract will no longer work at all under 9x due to a combination of changes in AutoIt and the continued difficulties involved in trying to make it work under the older and unsupported OS. If you need to use it under 9x, please look through the last few pages of this thread. I exchanged posts with another 9x user, and he did some testing of various UniExtract versions to see which worked best. You may want to give that a try. I was that user! Rather belatedly, I can pass on that version 1.3.1 was the most successful under Windows 98SE on my system. I hope this helps. Cheers, Dave.

My "Add Network Place" wizard seems to have stopped working (Windows 2000 SP4). The wizard runs OK, and I can enter all the information, but when I click to add the network place, I always just get an error message which says "unable to connect, the parameter is incorrect". I already have several network places installed, all of which still work correctly. I dare not delete any of them in case I can't now put them back! They all point to FTP sites, as does the one I'm trying to add. I can browse this FTP site OK in Internet Explorer, so I know that the parameters I'm putting into the wizard are correct! Also, I have read that going to an FTP site in IE should auomatically add it to the "My Network Places" folder, but this isn't happening. Anyone any ideas on this? Thanks.

Hi again Nitro. Thanks for the download page of previous versions! I have tried almost all versions with my Windows 98SE setup, and reached the conclusion that 1.3.1 seems to work the best. I am using the installed version. Even that occasionally throws up an error message, and doesn't support as many file types as the later versions of course, but most of the time it does work under Windows 98. Maybe that's the latest version that you should recommend to Windows 98 users, as I had no luck at all with any of the versions of 1.4, or 1.5. I will install 1.5 on the Windows 2000 side of my machine. Looking forward to 1.6! Thanks again. Cheers, Dave.

Thanks again. I managed to find and download a copy of version 1.4.2, which produced exactly the same error message as 1.5! I tried the exe installer version and the rar archive version, with the same result. I can't find a copy of 1.3.1 anywhere to download. Could you point me to somewhere I can get it? What is the "other" version of 1.5? Do you mean the non exe installer version? Cheers, Dave.

Thanks for the reply nitro322. I thought that it looked like something pretty fundamental that was causing the error message! I understand the Windows 98 compatibility problem. The only thing I would ask is whether there is an earlier version of Universal Extractor that does work under Windows 98 still available anywhere? I could then install both versions on my dual boot machine. Cheers, Dave.

I've just installed version 1.5 of Universal Extractor on my dual boot Windows 2000 SP4 / Windows 98SE machine. Works OK on Windows 2000, but on Windows 98SE I'm getting an error and the program won't work. Searching this thread it looks as if some others have seen this too, on earlier versions going back a year! Is the there any fix as yet? The program is supposed to work under Windows 98...........

Thanks miko, Very interesting...........

One of the main reasons I wouldn't use XP over 98 or 2000! Thanks for the tip about avoiding the file locking, I will try that. I have a customised .htt with movie preview for the shared "My Documents" folder which is used on 98 and 2000 (dual boot). It does lock the files and prevent renaming etc. on 98, but not on 2000. Good to know that this is probably avoidable!

Be aware that if you do enable movie previews in Windows Explorer under Windows 98, you will have problems with files getting locked by the process. If you click on an avi file say, and the WMP preview pops up, you will not then be able to rename or delete that file, as the OS will report it as being in use. This limitation does not happen in Windows 2000 or XP.