CompuServe Messages

Tom, I'm one of the people who are using QEMM's QDPMI.SYS with ANI Pro. It seems that success with these various memory managers is highly dependent upon the different types of system BIOS and adapter boards in the computer. IOW what works for you works for you and may not work for anyone else. That said, I'll explain how my system is set up… I am using QEMM 7.01 with Stealth mapping mode and QDPMI enabled. I also have Stacker 3.01 installed and ANI Pro writes its temporary files to the stacked drive. I never had a problem with QDPMI and have not changed the parameters that QEMM installed for the QDPMI driver: DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=QDPMI.SWP SWAPSIZE=1024 After looking through the manual (Chapter 10, pg. 108) I would suggest that you check your CONFIG.SYS file. If there is a parameter on the QDPMI line such as EXTCHOFF or NOXCHK, then the QDPMI driver will refuse to relinquish control to the Pharlap extender in ANI Pro. The default setup does not use those parameters and allows QDPMI to step out of the way when a Pharlap program is executed. You could also insert the parameter XCHK into the QDPMI line to force it out of the way. After saying all of that, it appears that QDPMI is not needed to run really important programs such as 3DS and ANI Pro <G>, so if its easier to just not load QDPMI then don't load it. Also, for those of you interested, I had stated in a previous thread that ANI Pro did not seem to like running with the QEMM STEALTH mode. I finally went through the STEALTH.TEC trouble shooting procedures and discovered that ANI Pro wants to directly access system ROM in the range of FC00 to FFFF. After excluding that portion, STEALTH and ANI Pro work together just fine. Now for the weasel words: The above information represents my findings on my machine only. Your actual results and mileage may vary. Steven