Posted by jack in scaesar.com
I have an Athlon 1700 with lots of memory, WIN98, AVG Free antivirus, and a recurring conflict between filt95.vxd and the mouse driver (msmouse.vxd). Outpost is still v 2.5.370 on this PC as I had too many probs with later version and WIN98 and went back to it (V3 is fine on my XP machines - Family license).
When I start W98 it reports 'serial mouse not found' and freezes unless I do a step by step startup and say NO to filt95.vxd startup - then it starts normally (msmouse.vxd is the next startup item). Once it does, Outpost appears to be running - certainly the try icon is there and the program comes up when you click it.
I once had one good registry copy which would start W98 with Outpost, and I had to run Scanreg /restore every boot-up to start this PC - all other copies of the Registry wouldn't work. Then somehow I fixed it by uninstalling and reinstalling mouse drivers, but the problem always recurs after a while, and now I've run out of good copies of the Registry that will start it - I suspect Outpost is modifying them and producing this problem. I'm wondering whether the problem is that filt95.vxd is still running its start up as the mouse driver tries to start up, and if moving the mouse startup to before filt95.vxd would fix it. If so, how do I do that, and any other ideas please? Please don't just recommend upgrading to V3.0 - I'll be changing this PC to XP soon, but past experience was that Outlook upgrades past 2.5 were trouble with WIN98.
Thanks,
Max
PS - If I disable Filt95.vxd on startup then shut down the Outpost interface once WIN98 is running then restart outpost.exe, there's no problem, so it looks like the startup routine or order is the culprit?
PS - If I disable Filt95.vxd on startup then shut down the Outpost interface once WIN98 is running then restart outpost.exe, there's no problem, so it looks like the startup routine or order is the culprit?Hello Maxr,
Welcome to the forums. It is certainly possible that there is a run time issue between them. Since you used to have a registry that appeared to work and no longer have one I would say the issue is probably something corrupted the registry in a non-fatal way. You might try switching to mouse to USB rather than PS/2 if that is possible.
I would suggest uninstalling the mouse and firewall with reboots between. Then reinstall the mouse drivers, reboot and reinstall the firewall. Personally I would use 2.5.375 rather than 370.
When I start W98 it reports 'serial mouse not found' and freezes unless I do a step by step startup and say NO to filt95.vxd startup - then it starts normally (msmouse.vxd is the next startup item). Once it does, Outpost appears to be running - certainly the try icon is there and the program comes up when you click it.
I once had one good registry copy which would start W98 with Outpost, and I had to run Scanreg /restore every boot-up to start this PC - all other copies of the Registry wouldn't work. Then somehow I fixed it by uninstalling and reinstalling mouse drivers, but the problem always recurs after a while, and now I've run out of good copies of the Registry that will start it - I suspect Outpost is modifying them and producing this problem. I'm wondering whether the problem is that filt95.vxd is still running its start up as the mouse driver tries to start up, and if moving the mouse startup to before filt95.vxd would fix it. If so, how do I do that, and any other ideas please? Please don't just recommend upgrading to V3.0 - I'll be changing this PC to XP soon, but past experience was that Outlook upgrades past 2.5 were trouble with WIN98.
Thanks,
Max
Welcome to the forums. It is certainly possible that there is a run time issue between them. Since you used to have a registry that appeared to work and no longer have one I would say the issue is probably something corrupted the registry in a non-fatal way. You might try switching to mouse to USB rather than PS/2 if that is possible.
I would suggest uninstalling the mouse and firewall with reboots between. Then reinstall the mouse drivers, reboot and reinstall the firewall. Personally I would use 2.5.375 rather than 370.
#If you have any other info about this subject , Please add it free.# |