ross@isis.UUCP (Ross McConnell) (11/06/87)
I have a couple of commercial software packages (civil engineering oriented) that currently run on PC's and AT's, and are written in MSC. I am fighting the 640K barrier, and am considering porting the packages to a 386 to take advantage of the 4G 'small' model. It seems to me that there are several possibilities : 1) Use Xenix 386 from SCO or Microport 2) Use the Phar Lap and Metaware sort of compiler/Run386 environment 3) Wait for OS/2 (will it allow 4G addressing ? ) Has anyone had any experience in this area? Would it make sense to fiddle with extended/expanded memory on a PC or AT? Should I give up and move to a 68020 machine? Any comments would be appreciated.
garon@pedro.UUCP (Garon C. Yoakum) (11/11/87)
In article <2032@isis.UUCP>, ross@isis.UUCP (Ross McConnell) writes: > I have a couple of commercial software packages (civil engineering > oriented) that currently run on PC's and AT's, and are written in MSC. > I am fighting the 640K barrier, and am considering porting the packages > to a 386 to take advantage of the 4G 'small' model. It seems to me that there > are several possibilities : > 1) Use Xenix 386 from SCO or Microport > 2) Use the Phar Lap and Metaware sort of compiler/Run386 environment > 3) Wait for OS/2 (will it allow 4G addressing ? ) Currently, I am running MicroPort V.3/386 with the green-hills 'c' compiler. The 4G 'small' address space works wonderfull and required zero program modifications. OS/2 will not allow 4G addressing and only support's the 286 addressing. Personally, I think it's a waste of time messing with a screwed up processor and operating system. Take my advice, go true 386 or bag it and go for the 68000 series processors.