To: Thean who wrote (4652 ) 10/26/1998 7:36:00 PM From: Alski Respond to of 14427
Thean, OT - Memory. I agree, some software you're running isn't freeing up memory when it's done. Internet Explorer 2 was notorious at that. I haven't had the problem with either IE4 or Netscape 4 though. Keep in mind I'm not experienced with Win98 but 128M should be more than enough memory. I'm not familiar with your BMC monitoring software either but I'd be willing to bet it's referring to the 640K conventional base memory as physical memory. That's where the stacks and DOS stuff still reside. Windows is very good and managing high memory and even uses spare disk space as virtual memory. Your problem has to be something eating up that base memory. Unfortunately you could add 10G of high memory and you'll still crash if something eats up all your base memory or overflows a stack. Unfortunately trying to find out what's eating up your base memory can be a bit tricky. I wonder if the tech support forks for your BMC monitor software would be willing to help? The best way I know is to turn everything off you can and start as clean as possible. Get rid of everything in your startup folder, re-boot, and then use ctrl-alt-delete to get rid of everything else, except the basic Windows stuff. Then start your browser and monitor. If you're still loosing memory try reloading your browser from scratch, or try the other one. I've had bad luck with some of the Netscape plugins. If you're using Netscape you might try uninstalling all the your plugins to see if one of them is the culprit. Or, try IE. You're really getting down into the mud with that DOS game. If you check the properties of a DOS program (right click on the .exe), you'll find several different memory usage options you might try though. Oh, and if you have a config.sys or autoexec.bat in your root directory (C:), try renaming them config.sav and autoexec.sav and rebooting. Windows doesn't need them but will try to use them if they're there, usually with less than optimum results. Also, isn't one of the troubleshooting wizards in Win98 a memory troubleshooter? Sorry if that wasn't much help but I've probably chewed up too much public bandwidth already. PM me if you want more. Alski