Autocad R12 Dos Download For Windows
Jhinton wrote: I am attempting to run ACAD r12 from Windows XP. I am trying to use the same PIF I have used sucessfully with Windows 98 SE ad Windows 95. WinXP is built on the NT/2000 model, not the 'graphical shell' upon DOS called Win95/98/ME. Can't use -REALBREAK under this version of DPMI Can't get any memory. It never worked on NT, 2000 and it sure ain't gonna start working now.
What can I do to make this work? I have tried various solutions (modifying my system.ini file, etc.). Any assistance would be greatly appreciated. The best solution is two machines. An old DOS machine to run this old DOS software.
If you insist on running it on this machine, you will need to reformat the drive. Boot to DOS, create a 2gb partition, and install DOS and R12DOS. Reformat the remainder of the drive and reinstall WinXP. Better do a lot of reading at Microsoft.com before you start to confirm this. Of course if Autodesk did the right thing you would be able to upgrade for say $1695. Then again, there's always ICAD.;-) Terry. Jhinton, i had a similar problem with running 3d studio r4 dos from windows xp (i had an identical error message) i discovered a workaround which worked for 3ds4, that i think may also work with autocad 12 dos.
Firstly, i upgraded the rainbow drivers for my hardware lock at from www.rainbow.com (ssd5.39.2.zip) i installed these. Secondly, from the command prompt ( 'start' 'run' type 'command') i entered the directory of the executable (ie 'cd ' to get the c: prompt, then 'cd 3ds' - substitute wherever your autocad is located for 3ds ie: 'cd r12' once in the autocad directory where the executable is located, i inputted 'cfig386.exe 3ds.exe -realbreak 0' again, i would imagine substituting acad.exe for 3ds.exe I hope this works, if not, it should help anyone searching for a 3d studio dos workaround 'jhinton' wrote in message news:f0a2dc7.-1@WebX.maYIadrTaRb. I am attempting to run ACAD r12 from Windows XP. I am trying to use the same PIF I have used sucessfully with Windows 98 SE ad Windows 95. However, I am recieving the following error message: Phal Lap err 74 Can't use -REALBREAK under this version of DPMI What can I do to make this work?
AutoCAD R12 for DOS. AutoCAD R12 for DOS AutoCAD R12 for Windows AutoCAD R13 AutoCAD R14. Downloads: Size: Bc12dos.exe: 744. CAD Studio - files and utilitiesapplications, files, patches, utilities, macros, libraries, viewers. File Download: click on the disc icon to download the file.
I have tried various solutions (modifying my system.ini file, etc.). Any assistance would be greatly appreciated. Here are 3 common Phar Lap error messages that occur when trying to run old Extended DOS programs in Win 2000 or XP accompanied by possible solutions: (You'll want to check the last one, err 74) No DOSX.EXE loaded (Microsoft DPMI host): Error TNT.20035: 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 TNT DOS-Extender to run in protected mode.
Solution: Load DOSX.EXE in an Autoexec.NT file such as AUTOEXEC.NT or a program specific Autoexec.NT you create and set in the Program Shortcut/Program/Advanced/Custom MS-DOS initialization files/Autoexec filename: - REM Install DPMI support lh%SystemRoot% system32 dosx This is the standard line in AUTOEXEC.NT. In your program shortcut's Memory tab, set EMS to None. PADS Perform DOS with built-in 386 DOS-Extender v5.1 sometimes does not delete swap file when it terminates abnormally and then cannot, or refuses to, start a new one (overwriting the one left): Phar Lap err 58: Can't create VM swap file of size 0 in directory C: PPERFORM.SWP Solution: Start the program with a batch file and add 'del C: PPERFORM.SWP' before the line that starts PADS Perform For a different program, substitute the appropriate path and swap file name. No DPMI v1.0 host with Map Conventional Memory in Memory Block function (INT31h AX=0509h), required by any program which uses -REALBREAK: Phar Lap err 74: Can't use -REALBREAK under this version of DPMI Error TNT.20074: Can't use -REALBREAK under this version of DPMI The purpose of the -REALBREAK switch is to request that some of the code and data be placed in conventional memory. There appears to be 2 reasons to use -REALBREAK to load some of the application in conventional memory: 1. Having some of the application in conventional memory can apparently improve the performance for some programs. Mixing Real-mode and Protected-mode code. Zeiss ikon contarex bullseye.
Apparently Real-mode code can be mixed with Protected-mode code if the Real-mode code and data are 64K or less and they are loaded in conventional memory (linked to be positioned at the beginning of the executable file). If program is all Protected-mode code, apply -REALBREAK 0 - 'CFIG386.EXE Program.EXE -realbreak 0' if DOS-Extender is bound to the Program (one.EXE), 'TNT.EXE -REALBREAK 0 Program.EXE' if using a separate DOS-Extender loader This says load 0KB in conventional memory, effectively eliminating the need for -REALBREAK support and allowing a DPMI v0.9 host to suffice. Microsoft's EMM386.EXE and DOSX.EXE DPMI hosts provide DPMI v0.9 support.
The performance will decrease, but the program should run. If program is mixed Real-mode and Protected-mode code, you're screwed. This is because Real-mode code and data MUST be loaded in conventional memory, thus requiring support for INT31h Function AX=0509h, which in turn requires a DPMI v1.0 host. In this case, with -REALBREAK set to 0, the DOS-Extender will load. But when the program starts to load, it quickly displays an error such as the following: Panic!!!! Cannot reach real mode vector EAX.
Ms-dos Download For Windows 7
0000250F EBX. 00000000 ECX. 00008DC0 EDX.
Autocad R12 C4 Download
002D0008 Exiting. Since the Real-mode code isn't being loaded in conventional memory. Reverse engineer the program and add the realcopy function shown in DOX-Extender's MDRAW sample program and eliminate the need for -REALBREAK. Then the program should work in the NT series.
Or, for a more practical solution, try a Virtual Machine or Emulator such as DOSBox, Virtual PC, or VMware Workstation. Virtual PC can run PADS Perform DOS in Windows XP SP2, but only at 640x480 because of limited video support. DOSBox can even run PADS Perform DOS at 1024x768 in Windows XP SP2. DOSBox and Virtual PC are free. So, even if ACAD R12 DOS uses mixed code like PADS Perform, you can still run it in Win 2000 or XP.
But you'll have to use a virtual machine or emulator such as Virtual PC or DOSBox. On an Athlon XP 3200 with 2GB of memory, performance was acceptable for PADS.
Ms-dos Download For Windows 7 64-bit
Try both to see which has the best performance and video support for ACAD. And get the fastest computer possible if your drawings are very large. If interested, see: 'ort.mspx' Community, Virtual PC newsgroup Search for: Virtual PC 2004 or 2007 Video Card Support for DOS programs See the 2 posts on. VMware Workstation 5.5 or 6.0 Video Card Support for DOS programs '595889' See post of. (CFIG386.EXE is a utility from Phar Lap that allows configuring the DOS-Extender when it's bound into the main program's.EXE). (PHARLAP.386 is a VxD, virtual driver, only for the Win 9x series. It will not load or work in the NT series).
(PADS Perform DOS is an Electronic CAD program that uses mixed code, the Phar Lap 386 DOS-Extender, and the -REALBREAK switch). No DOSX.EXE loaded (Microsoft DPMI host): Error TNT.20035: 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 TNT DOS-Extender to run in protected mode. Solution: Load DOSX.EXE in an Autoexec.NT file such as AUTOEXEC.NT or a program specific Autoexec.NT you create and set in the Program Shortcut/Program/Advanced/Custom MS-DOS initialization files/Autoexec filename: - REM Install DPMI support lh%SystemRoot% system32 dosx This is the standard line in AUTOEXEC.NT. In your program shortcut's Memory tab, set EMS to None. Obviously you know what you are talking about and I am grateful for this. I am trying to configure a Dos based version of ArcInfo 3.5.1 (1997) and I am receiving the same error message.
I have tried many variations and attempts with my NT files (both autoexec.nt and config.nt). I have followed the exact rules you specify yet still receive the error message. I am at a loss what to do.