In article <4568BB36.54B2@Worldnet.att.net>, "Paul N. Lee" <Paul.N.Lee@Worldnet.att.net> writes:
Richard wrote:
"Paul N. Lee" writes:
I thought it was prior to VC3, something closer to VC1.
Wikipedia states that VC2 was the first 32-bit only environment under the Visual C++ name.
Which is why one has to go back to VC1 (Visual C++ 1.5). I still have the old install of that lying around somewhere in a storage box (got to be at least 13 years old or so).
I got 1.52 off the MSDN subscriber downloads. It turns out you actually need an OS older than Windows 2000 in order to install the development environment :-). I had a VMWare image of a Win98 machine for testing and I've added a snapshot of the development tools on there. It looks like I could get everything to compile 16-bit if I created a new makefile or edited the existing makefiles. Do I need to setup some environment variables for NMAKE to just "do the right thing"? If I manually go into the common folder and do nmake /f common.mak then everything builds except parser.c and parserfp.c, which get lots of errors when comparing/assigning a far function pointer to a non-far function pointer. The struct member is declared far: void (far *f)(void); while the data variables are declared non-far: void (*StkNeg)(void) = dStkNeg; This does seem to be a legitimate problem when you compare or assign .f with StkNeg such as on line 1965: if(o[posp-1].f == StkNeg) { I didn't slug it through any farther than that. Has anyone else compiled the DOS application with Visual C++ 1.52? -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>