herbalist

Prozactive, I've tried several different combinations of official and unofficial updates with KEX, RP, and SSM installed in different orders. I haven't been able to duplicate the problem or cause any type of error message. Saw your post in the RP9 thread. I suspect that these problems have a common cause, and the first one that comes to mind is a RAM stick going bad. If you haven't already, could you test the RAM? Is there anything else that you've installed recently, possibly printer software?

This appears to be the same version that's contained in the Maximus Decim InternetExplorer 6.0sp1 Component Update 3.4. The copy of BrowseUI.dll on my system is that version. Could you verify the MD5 for that file? The hash for my copy is 63ef369f829e36018180f7c67efc2957

Thanks. Knowing exactly what files you've updated will make it easier to investigate. Just so I can set up a similar system, did you install any of the unofficial service packs? If so, which ones? Trying to come up with a user friendly interface that included all those options was a project in itself. Compared to the pro version of SSM, it's actually quite friendly. The pro version is much more convoluted, especially the registry rules. In some ways its behavior seems backwards in comparison. The interfaces definitely could have been better, but from the beginning it was clear that SSM would target a limited user base and that there was no real way to make it friendly to the more "typical" user (not referring to you). Several of us convinced the developer not to drop 9X support, but even the free version was designed with XP in mind. There was only a couple of us testing it on 98. Being one of the few remaining viable security applications for 98 wasn't planned for. The help file did skip over the options for applications almost completely and is seriously lacking in detail for logging. The short explanation for application options: 1, allow everything. Default permit. If the process or activity isn't specifically blocked, it's allowed. 2, block process creation. Only whitelisted applications (those with allowing rules) can run. Other activities such as DLL injection are not restricted. The default parent and child settings is "allow." 3, Block everything (paranoiac setting). All monitored activites not specifically allowed are intercepted. If the UI (user interface) is connected, you'll be prompted. If it's not connected, the activity is silently blocked. If this setting is chosen and rules for normal system activities aren't finished and the UI is disconnected, SSM can easily lock up the system. Another thing the help file doesn't mention. If you set a password, the "Connect user interface at startup" no longer applies. SSM will automatically start with the UI disconnected. Do not set a password until the rules for all processes involved in startup are complete. I had hoped to have the web pages for SSM and 98 done long ago. I seriously underestimated what it would take to thoroughly address this subject. KEX and to a lesser extent RP9 have made it necessary to modify some of the material. Since these are very necessary to the continued viability of 98, they have to be accounted for and have to get along with SSM and each other. Snowstorms aside, I "should" have more time to finish them this winter. There's a lot I still need to examine and account for, especially in regards to external devices. Building web pages/sites is not something I'm good at. They won't be pretty or fancy. Hopefully they will be useful.

The KEX extensions is disabled for browseui.dll on mine as well. I never checked the KEX settings for that file before. Might be the normal setting for it. The file version might make a difference. That will take a bit longer to check. I've needed a 98-IE6 test unit a few times but have yet to build it. Regarding the file from the update, did you just substitute it for the original in DOS? That setting allows any application to use the file. Unless there's something different with the version you're using, SSM should not restrict it on that setting. By menu, I meant the file menu on explorer windows. It probably applies to the file menu on Internet Explorer as well. Judging by the things you've described, I'm assuming that the SSM setting on the options tab for applications, under program behavior you have "block process creation" selected. If that's not the case, let me know. You mentioned that SSM seems to be working properly with KEX disabled for its components. I'm interested to find out why that should be necessary. I don't think that I'll be able to check thru this today. It looks like I'll be spending the day dealing with winter.

Could you check a couple things? 1, What is the KernelEX compatibility setting for browseui.dll in the system folder? 2, Under SSM application rules, look for the rule for browseui.dll, advanced properties. What is the default action in the drop box? If not "allow injection" is explorer checked as an allowed source? Were you also getting this error when using the menu on explorer?

So far, I'm unable to duplicate the problem with SSM and KEX 4.5RC1 or RC4. Just to rule out one possibility, could you verify that you do have version 2.0.8.583 of SSM and not version 584? Version 584 was released for a short time but had stability issues, some of which were similar to what you're describing.

Just to confirm, you installed SSM free after Kernel EX? The conflict between SSM-free and KEX was fixed with the release of KEX 4.0RC1. On my PC, SSM files are using the default KEX settings, but SSM was installed first. Also SSM can lock up a system if it's not configured properly. If you set a password in SSM, it will automatically start with the UI disconnected and will deny any activity that you don't have rules to allow. If it prevents explorer from performing some tasks, that will lock up a system. I'll have to set up a test unit to confirm it, but I'd suspect that installing SSM after KEX might be the problem. SSM has its hooks into almost everything that happens on a PC. KernelEX could have caused it to incorrectly integrate with the system. Will try to get an answer for you as soon as possible.

The Orangeware drivers are distributed with a lot of USB devices and are available on many vendor websites but are not generally referred to by the "orangeware" name. For me, version 2.3 has worked the best. YMMV The driver package contains the following files: ousb2hub.sys ousbehci.sys ousb2.inf The only problem I've had with USB was accessing parts of my external hard drive in pure DOS. It turned out that the problem wasn't USB related at all, but was due to the way GParted partitioned the drive. Another member helped me straighten that out. I can't comment on how it works with USB drives > 137GB as mine is an old 80GB. The USB card also worked well when I installed it for a short time in a Compaq P866/815E . The Compaqs built in USB worked very poorly with my external and flash drives, constant errors. By using the USB card, I was able to install and update directly from the external drive. Depending on the USB card and the requirements of the external drive, you might run into problems with a card that doesn't deliver sufficient power. A USB hub with its own power supply will fix that. I added one just so the USB ports would be in easy reach. NUSB identified it easily and whatever I plug into it works fine. The only problem it creates is with the Acronis rescue CD, which won't recognize devices plugged into it. The Orangeware drivers themselves shouldn't cause problems. Even so, if you make a full system backup first, there's no risk in working with both sets of drivers. At a minimum, make a registry backup first. Another app that helps with the issues caused by modifying and updating is Inctrl5. It's an install monitor that takes system snapshots of the registry and file system before and after the install or test, then shows all the changes in your choice of formats, which can be saved. If a full list of the drive contents is created when the system is built and Inctrl5 is used for every install and update afterwards, it enables you to account for every file on your system and where it came from.

USB cards with the NEC chipset do work on both 98FE and SE. I've had one in my old HP for years. Unless your USB hardware came with drivers for 98, you will need NUSB, which is available for both 98FE and 98SE. On my PC, I also had to install the Orangeware drivers after NUSB in order to get 2.0 speeds from the card. They also work on both FE and SE. On FE, the drivers had to be installed manually as the CD claimed that they weren't compatible. So far, every USB device I've plugged into it has worked properly on both 98 systems. The 2 built in USB ports also work but are limited to 1.1 speed. I've never tried a combo card so I can't comment on whether one will work with 98 or not.

I trust my 98 unit to stand up to anything they can do from the web along with the older Smoothwall unit in front of it. The DSL modem is what I'm not trusting. I'd like to think its failing at that moment was a coincidence but I wouldn't bet on it. Somehow, it locked up. The interface would only half load. It took 2 factory resets to get it to the point I could redo its settings. It's the ISPs modem but I have full access and had disabled remote access, telnet, and UPnP. If it's not a coincidence, I'd be interested to find out just what was done to it. The link you posted earlier is still working. Going to find that torrent as soon as I can. I was wondering when the takeover of the net was going to happen. Never thought it would start with Wikileaks.

Thanks for the link. I was trying to find a way there this morning. Interesting that my DSL modem picked that moment to corrupt its settings.

On the right. Thanks for taking the time to make that image. That explains why I didn't notice the change. I've been so used to the way Windows sorts that I automatically number files 01, 02,....10, instead of using single digits. I'll be interested to see what it does with some of my numbering systems. Thanks for another good update.

What exactly is natural shell file name sorting?

First page login link isn't working for me either. Using SeaMonkey on both 98 and XP. Clearing the cache and cookies hasn't helped.

It appears to be an OEM file. I missed it in the file listing.

I'm not sure if this is any help or if it confuses the situation even more. On my old 98FE unit, my copy of secur32.dll does not say export version or USA and Canada on the version tab. Just says Microsoft Win32 Security Services. The MD5 for the file is 677273be08256ea12afdfc8da91ac54a if it's of any help. So far, I'm unable to determine just where I got this file. It does have DUN1.4 installed. Rick

TestRun isn't a registry backup program per se, though it can be used as one. The first batch file creates a full duplicate of your registry and other system files. When you want to test install something or do some other experimenting or modifying that involves the registry, you run the 2nd batch file which replaces the original files with the duplicate files. The original registry files are kept out of harms way. The test files can be used as long as you want. The change survives reboots. When you're done with whatever you're trying, you can either accept the test files as your new permanent registry or you can revert back to the ones you started with. If something you do makes Windows unbootable, you can switch registries in DOS. The TestRun batch files dupliacte and swap these system files: Autoexec.bat Config.sys Msdos.sys system.dat user.dat win.ini system.ini protocol.ini If you're 98 unit is set up with user profiles, you might want to modify the batch files to include the user.dat files stored in each users profile. The batch files cover the system.dat and user.dat from the windows folder only, the normal setup on single user systems. If you're primarily interested in registry backup and protection, check out the 2nd link in my signature. It's based on TestRun but is modified to include user autostart folders and runs automatically at bootup.

On 98 units without IE6, the handles for toolbars don't reappear after locking and unlocking the taskbar. They can be made movable again by closing the toolbars, then reopening them. I never lock the taskbar or move the toolbars, but I like the handles which look like dividers between them. Regarding the registry and testing new updates and apps, there's an easier way than using the built in 98 registry backups. TestRun is a group of batch files that creates copies of the registry and system configuration files and switches them in DOS. It enables the user to load a duplicate file set for testing while keeping your original registry out of harms way. You then have the option of keeping the new registry or restoring to your original. It's more flexible and user friendly than the 98 registry backup utility as it will switch to DOS for you. The installer makes no real changes to your system. It just unzips the files to a folder and makes shortcuts for you. I've used it for years. For those who aren't that experienced with DOS and batch files, these are good examples of just how powerful and flexible DOS can be for a 98 user. The original TestRun site is long gone but the Wayback machine still has the site, but not the installer. I've uploaded a copy of it here for those who can use it.

Dell support does have drivers for the 8200 for WinME. Many if not most of them should work with 98SE. On this page. According to their manual, the 8200 uses the 850 or 850E chipset. Intel has 98 drivers for these here. There's a good chance that Intel will also have display drivers if you're not using a separate card. If you make a full system backup first, there's no risk in trying the WinME drivers. The manual for that PC is available on the Dell site. It should identify the individual components. Once you know the make and model of the components, look for the drivers on the component vendors site. You'll probably find most everything you need. I'll be starting a similar project very soon. Just obtained a Dell dimension E310 with a 3.06 Pentium 4 and 2GB RAM. Going to try to put 98lite on it.

Which model of Dell Optiplex do you have? I'm dual booting 98SE and XP on an Optiplex GX260. It's a Pentium 4, 2.4GHZ with 1GB RAM and a 160GB hard drive, split into several partitions. It's also very quiet. 98 drivers for this model are available from Dell with several more available thru Intel support, including the chipset, audio, display, and the built in network. The Dell Optiplex is proving to be a very stable platform for 98SE. Everything works as it should. My only complaint regarding the Optiplex is that it doesn't have room for more than one hard drive, not that big of an issue as my external hard drive works well with it. If yours is the same model, you might want to look over this thread, in which I received some very good help getting this PC built.

Regedit.exe works in batch files. Syntax here.

I manually copied NPSWF32.DLL from the macromed\flash folder on my XP install to the same folder on 98 after renaming the old copy from the 10.0.12.36 install. The xpt files for both versions are the same. The Adobe website now says I have version 10,1,53,64 installed. So far, all the sites I've tried are working properly. If you go this route, go back thru the flash player settings. There's options there that weren't present with version 9.

The installer format was changed sometime after version 10.0.12.36. This version I can extract with 7zip. The next version I have, 10,1,53,64 can't be extracted by 7zip. None of the 10.1 versions will install on 98 here. The installers don't seem to do anything.

Farmville seemed to load properly here although I didn't try to play it. It's a friends farm and there's way too much there for me to want to sort out. I keep up fish wrangler for her when she's away to keep her log-in streak going. Using KernelEX, RP9, and Flash 10.0.12.36 on SeaMonkey 1.1.18. Had to bypass Proxomitron in order to get it to load. That game is a processor hog. Took almost 2 minutes to fully load, very cluttered farm. Even after it loaded, processor load was consistently between 85 and 90% with a 2.4 GHZ Pentium. SeaMonkey crashed when I tried to go full screen. Edited to correct version number.

If I remember right, some of his winsockfix were OS specific. I haven't seen this type of malware in several years. "NewDotNet" was one of them. There were others. As long as the malware file that replaced the winsock was present, the PC had normal internet access, as did the adware/malware that installed it. A lot of the malware then was quite different than what we have now. A lot of it was very "in your face", literally daring you to try to remove it. This was before the days of HIPS and other process controlling security apps. I remember a couple of them that used several processes, each protecting and restarting the others. If you didn't kill the entire group of processes in one shot, you couldn't delete any of them. If I'm remembering right, the old versions of Kazaa would add this and a lot more to your system. Today, malware hides very well. Often there's no visible indications that your system is infected. If your AV missed it, you could remain infected for a long time and never know it.