CompuServe Thread

#QEMM conflict

6 messages in this thread
#21631From: Aug 16, 1992 2:34 PM
help! i just installed qemm 6.0 so i could run 3ds2 and windows without having to reboot my machine. prior to installing qemm i had no problems whatsoever with 3ds2. i have a 486 33 8mb ram and 340 mb hard drive. now when i run qemm in different configurations i cant complete renderings of complex objects problem 1: when i use qemm.sys x=d000-dfff, i am able to render most complex scenes but above a certain level of complexity i get kicked out of 3ds2 with an error saying 386:vm corrupted and my system locks. problem 2:I took out the x=d000-dfff statement reran optimize and when i render even minor scenes i get an error message no ram for rendering mesh object. It appears that i am not able to use the virtual disk problem 3: when i am able to render scenes with the x=d000-dfff statement excluded when i exit 3ds my system locks saying batch file not found. I have played around with a number of configurations and have not found a solution, i was wondering if any of the parameters involved with cfig386 would solve the problem or use different memory exclusions. However i really dont fully understand the cfig386 commands and am totally clueless about changing any other exclusions in memory. thanks sam coor
#21637From: CSA/CAAug 16, 1992 7:01 PM
Sam, I have no problem with sauch setups, so there is likely some other hardware or software conflict going on. Excluding D000-DFFF makes sense for a Targa or other graphic board at that address. I usually also Exclude B000-B7FF for Windows compatibility, and make sure that my Windows INI files exclude the same areas of memory. Except possibly for TSR's, I suspect you may have an incompatible hard disk controller. My guess would be that you have an IDE drive (that's the only time I see these types of errors) and controller. Try swapping out for a controller from a different manufacturer. With IDE, you do not need to reformat the drive – it's just plug & play. Kevin Krell – Computer Support Associates
#21698From: Aug 17, 1992 6:42 PM
thanks, however i tried x=d000-dfff and low and behold i no longer have any problems. by the way i am using a scsi. thanks for your prompt reply sam
#21644From: Yost GroupAug 16, 1992 10:30 PM
Sheesh, what a configuration nightmare! Kevin's suggestions sound like a great place to start working on it. Plus please give us a more-complete list of what's in your system in addition to the hard disk controller. (ie, display cards, ADI drivers, SCSI cards, etc) – G
#21699From: Aug 17, 1992 6:44 PM
since i postes the message i tried one more configuration x=d000-dfff and i no longer have any problems! I got the configuration off ofasoft 1-2 weeks ago for a similar problem someone else was having and just recently found it thanks for your prompt reply sam
#21717From: Yost GroupAug 17, 1992 11:12 PM
I'm glad that your problem is solved, Sam! – G