CompuServe Thread

#3D Studio & Win3.1

6 messages in this thread
#18307From: jeffJul 2, 1992 8:53 AM
Is there a way to get 3DS to run under Win3.1 and DOS5.0 with the latest HIMEM, EMM386 and SMARTDRV? Whether or not this is slow, is better than never using it. I've heard that this combination is now VCPI compliant and should run. I would settle for atleast running directly from DOS with my same config settings. I prefer not to have to purchase QEMM. When starting up 3DS (without WIN3.1 running) with my current config settings I get the following Message: "The 386 chip is currently executing in virtual 8086 mode under the control of another program. You must turn off this other program in order to use 386|DOS-Extender to run in protected mode." My config file is: DEVICE =C:\UTILITY\WINDOWS\HIMEM.SYS DEVICE =C:\UTILITY\WINDOWS\EMM386.EXE noems x=c000-c7FF DEVICEhigh=C:\UTILITY\WINDOWS\setver.exe SHELL =C:\UTILITY\WINDOWS\command.com /P /E:750 BUFFERS =5 FILES =80 BREAK =off STACKS =0,0 LASTDRIVE =e DOS =umb,high My autoexec.bat file is: VERIFY off PROMPT $P$G SET COMSPEC=c:\utility\windows\COMMAND.COM SET TEMP=d:\temp PATH C:\utility\windows LOADHIGH C:\utility\windows\share.exe LOADHIGH C:\utility\mouse\lmouse.com C:\UTILITY\WINDOWS\SMARTDRV.EXE 5120 5120 rem call C:\UTILITY\NETWORK\PROGRAMS\NET.BAT win/3 I'm running a 486/33 with 20Mb of RAM, a Video7 VRAMII w/1Mb. I appreciate your response and suggestions for a .PIF file. Thanks in advance, Jeff
#18313From: Yost GroupJul 2, 1992 9:30 AM
Jeff, 3DS is not DPMI-compliant. Since it uses the VCPI method of memory management, Windows is incompatible in enhanced mode. You should be able to use the latest version of HIMEM.SYS when running 3DS from DOS, however. – G
#18326From: jeffJul 2, 1992 12:37 PM
I am using the latest HIMEM.SYS that came with Win3.1. I am still unable to run 3DS from Dos 5.0. I had read that Win3.1 and associated memory management software was compatible with VCPI applications. I am running 3DS version 1.0. Are there later updates previous to Rev 2.0? I also read about a patch that updates the PharLap extender for AutoCAD making it compatible with MS memory management. Could there have been a similar patch for 3DS. I bought 3DS from a local vendor in October 91. Thanks for your help. Jeff
#18362From: Yost GroupJul 2, 1992 9:33 PM
Ah ha… you didn't tell me that you were running 3DS 1.0. If you insist on using HIMEM.SYS with it, you're going to have to update the version of Phar Lap inside of it using NEWDX.EXE (available as NEWDX.ZIP somewhere on this forum). That will convert ver 2.2 to 2.6. 3DSr2 ships with 2.6, so that's not necessary. Why are you using 3DSr1? The thought of using r1 for anything right now is a nightmare. – G
#18424From: james hydeJul 3, 1992 4:22 PM
Jeff, Get rid of EMM386.SYS thats whats causing the conflict, If you absolutly have to have EMS memory use QEMM. James
#18527From: MARTIN G FOSTERJul 5, 1992 11:02 PM
Jeff, the "noems" causes that message – or at least it does with QEMM. Martin