Nobody is perfect! 🙂
darry wrote on 2025-04-14, 01:11:
Lacking that, even software like AutoCAD release 10 for DOS from 1988, which needs a coprocessor (contrary to what the WIKIpedia article says) will not run. I know this from memory, and reference material from the era corroborates this.
EDIT: AutoCAD release 9 was the first release that required a coprocessor for the DOS version . [..]
Hi, thanks for the info, darry!
That would explain why my dad never said a word about newer AutoCAD releases.
The version I had was R5, I think, and R9/R10 wouldn't have run on a humble 286 PC of mine.
Well, not without an 80287 upgrade or an 8087 emulator (emul87), I suppose (80186/80286 and higher can catch FPU exceptions).
AutoSketch 2 was different here, I think.
Our retail version of AutoSketch had included two diskettes, one 8086 version and an 8087 version.
So it was up to the user to make the decision at installation time.
But AutoSketch was using a different code base, after all.
The GUI is much more modern, shares similarity with AutoShade utility.
AutoSketch 2 also was being bundled with drawing boards and mice, I think.
Version 3 added EMS support, which was very useful (I ran out of memory in v2 a lot of time).
Edit: There also were two notable Windows 3 versions of AutoSketch.
As far as I know, version 2 was the last good one, with the macro language.
Later versions share similarily mainly in by the name.
PS: To those without an FPU, Franke387 used to be a very good, very quick x87 emulator, which is now free.
http://icfs.de/english/franke387.html
Windows has its own FPU emulator/virtualizer, win87em.
On Windows 2.x it is win87em.exe.
On Windows 3.x it's renamed win87em.dll, but it's still an exe really.
It can be loaded in memory permanently, by manually adding it as exe to wini.ini:
"Keep WIN87EM.DLL always loaded in memory.
To have Program Manager (PROGMAN) or another Windows shell keep this in memory,
rename WIN87EM.DLL to be WIN87EM.EXE and place WIN87EM.EXE on the LOAD= line of the WIN.INI file."
https://www.betaarchive.com/wiki/index.php/Mi … _Archive/120182
Edited.
Edit: This is also interesting, and partially on-topic.
AutoCAD R11 and R12 had the title "AutoCAD 386", which implies 386 support.
So is it true that they can't run on a 286 anymore? That's a bummer.
My dad had a hot-rod 286 in 1989, with 4MB of RAM and Hercules.
Enough for running stuff such as Xenix, Minix, AutoCAD 2.x and R9/R10 which apparently had XMS support?!
Microsoft mentions the AutoCAD 386 name in another Knowledge Base article, too.
"AutoCAD 386 release 11 and 12 do not run with Windows NT because AutoCAD 386 requires DPMI version 1.0 and Windows NT supports version 0.9.
When you try to run AutoCAD 386 in a virtual machine, you receive the following Pharlap error 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."
https://www.betaarchive.com/wiki/index.php?ti … _Archive/101813
For OS/2, there's a workaround, though.
It uses NEWDX to update the Phar Lap 386|DOS-Extender in AutoCAD 386.
After being updated to version 2.6, the DOS-Extender, in addition to providing other features, allows AutoCAD 386 to use the XMS memory managed by Himem.sys.
"In order to upgrade the AutoCAD dos extender to work with DOSBOX, OS2 and other extended memory managers
(HIMEM.SYS, EMM386.EXE, QEMM.SYS), you need to install the NEWDX patch that can be found
in the OS2PCH.ZIP which can be downloaded from http://cd.textfiles.com/ems/emspro17/disk3/CADUTIL/
Extract the NEWDX.EXE, put it in the directory where ACAD.EXE is and run the command: NEWDX ACAD.EXE"
More info here.
On other hand, this means that the early R11 port to Windows 3.0 might have been using an 386 Protected-Mode Extender, too.
Something akin to Watcom's Win386 extender.
The prior OS/2 port of R10 likely was Protected-Mode ready already, I assume, but OS/2 1.x was still 16-Bit (except for a few parts, such as HPFS386 driver).
There's also a Xenix 386 port of R10, I think, but I can't find any screenshots.
That might have been 32-Bit already
"Another well known application which used Win386 was Autodesk’s AutoCAD R12 for Windows and the first release of AutoCAD LT (1993)."
Source: https://www.os2museum.com/wp/watcom-win386/
Exit: My apologies for the long post. It's night where I live and I got carried away!
But to be fair, this topic is somewhat fascinating!
Early AutoCAD on 386/486 systems has something to it, I think! It's that workstation feel, so exciting!
Similarily to how people in art/game development had used desktop Amigas as little workstations for running DPaint.
Windows 3.0 was essentially an cheap alternative to running the Unix version of AutoCAD on a minicomputer/unix workstation.
Edit: There was this Sun 80386 workstation from 1988, btw.
It had a full MS-DOS emulation environment with VGA graphics, it's being mentioned here
https://en.m.wikipedia.org/wiki/Sun386i
Especially the upcoming Windows 3.1 was great upgrade because it had support by the early, accelerated ISA Super VGA cards:
The GUI accelerators/Windows accelerators/GDI accelerators.
There was an early Xenix 386 port of AutoCAD R10, but R11/R12/13 surely was also on IRIX in early 90s.
R13 was from '94, the pre-Windows 95 days in which Unix graphics workstations were at their peak.
Btw, did you know that IRIX 5.2/5.3 had a NetMeeting type of program (SGI InPerson)?
You could video chat via ISDN and a comparably quick network connection! So cool!
Here's a YouTube video about it: https://www.youtube.com/watch?v=0u8Fb8l9Xr4