CompuServe Thread

#qemm386 conflict

4 messages in this thread
#72133From: tony galloriniDec 17, 1993 11:49 AM
Hello, my name is Tony Gallorini. I am an Animator Pro and 3D-Studio Rel 3 user. I run a 486dx2-66 IBM clone with QEMM386 ver 6.02 and DOS 6.0. All was well until i upgraded to qemm386 ver 7.0 with tis upgade animator pro lockes my system i tried evrything but was forced to remove ver 7.0 and go back to 6.02. any known problems with ver of qemm386 help woud be appreciated. thanks T.G.
#72198From: John TissavaryDec 17, 1993 4:25 PM
Qemm 7 is a LOT more aggressive about allocating memory, so you have to be on top of all conflicts like a wombat. You'll need to exclude EVERY SINGLE PIECE OF HARDWARE that uses upper memory to map ROM from your QEMM386.sys line by adding a statment similar to this: x=c000-cfff. That was just an example. You'll have to find out where your hardware lives and replace the numbers appropriately, and add seperat x=xxxx-xxxx lines for each block exclusion. Then get rid of stealth if you're using it, it'll slow you down and may screw up the dos extender. And get rid of that silly VCPI line. If you need further help, please post info about your hardware and your autoexec and config files. If you study the manual closely, it outlines an effective procedure for analyzing your memory and hardware setup, and will help you find exclusions and conflicts if you run it properly and carefully. Good luck, John Tissavary (La Luna cie)
#72649From: Joe MacRaeDec 20, 1993 9:53 AM
Tony, In additon to what John just told you, QEMM386 is up to version 7.03 as the initial releases had some problems with DOS6.0
#72670From: David RhotenDec 20, 1993 10:49 AM
I think you'll find the problem is probably the DPMI driver that is automatically installed unless you request otherwise — just remove the DEVICE=DPMI.SYS (or whatever) line, and you'll probably be ok. Dave PS – GO QUARTERDECK for upgrade patches to 7.03!