cl (Miscellaneous)
> > "Visual C++ 4.x bundled this 16-bit version. [Visual C++ 1.52x
> (16-bit)]"
> > (Ebay link)
>
> Thanks a lot for that pointer! I now have a
> combined birthday and father's day present
> on the way. Let's see what I can do with it!
This CDROM has arrived and today I tried it.
The default installation only installed the
Win32 version of cl.exe, so I can't produce
huge memory model programs.
In addition, I carefully read the license
agreement for the version of ml.exe (MASM)
that I normally use, and it requires me to
have Visual Studio 6.0 with SP5 installed
before I'm allowed to use that, so I didn't
install that either.
So I don't even have 32-bit MASM available on
my new computer yet. Not sure what assembler
people were supposed to use back in the
Visual Studio 4.0 days.
I went looking for the separate 16-bit C compiler
so that I could see if Microsoft C produces decent
assembler for pointer manipulation, but the only
thing I could find is a complete installation of
Win32s which can only be done legally if you already
own Windows 16-bit, which I don't.
So I think I need to give up on Microsoft C and
stick with Watcom C until such time as I manage
to find someone willing to update SubC (which is
public domain) to have a huge memory model target.
Unless someone else has a better suggestion on how
to rationalize and secure PDOS?
Thanks. Paul.
Complete thread:
- cl - kerravon, 20.08.2021, 18:31 (Miscellaneous)
- cl - Rugxulo, 21.08.2021, 07:29
- cl - Ringding, 21.08.2021, 09:38