10 Aug
2015
10 Aug
'15
12:54 a.m.
Well, Chuck, thanks a bunch, this is very useful and quite difficult code to
write from scratch. How does one compile for DOS by the way (I have to admit
I am too young to have ever tried), and get a copy of MSC 8.00C. Is the DOS
compiler buried in some part of Visual Studio? I have some old versions
dating back from Windows 95 time, when it was called Visual Studio 97...
Marc
From: Chuck Guzis <cclist at sydex.com>
Subject: SCSI Tape to TAP utility
A couple of weeks ago, I offered to share the source and executable for
a SCSI tape-to-SIMH .TAP file utility for MSDOS.
To run it, you'll need an ASPI driver for your SCSI adapter.
It was compiled using MSC 8.00C.
Find it here:
https://www.dropbox.com/s/x6qiudlpyitgxom/STP2T02.ZIP?dl=0
Enjoy,
Chuck
10 Aug
10 Aug
1:21 a.m.
On 08/09/2015 09:54 PM, Marc Verdiell wrote:
Well, Chuck, thanks a bunch, this is very useful and
quite difficult
code to write from scratch. How does one compile for DOS by the way
(I have to admit I am too young to have ever tried), and get a copy
of MSC 8.00C. Is the DOS compiler buried in some part of Visual
Studio? I have some old versions dating back from Windows 95 time,
when it was called Visual Studio 97... Marc
I believe it was tossed into Visual Studio 97 as a separate CD (not part
of the usual packet of Visual Basic, 32-bit C++, Visual J++, etc.) So
you probably already have it. I don't install the MS-specitic stuff
(e.g. COM), just the compiler binaries and basic libraries and include
files. It does require some DOS extender support (e.g. run it on Win9x
or install HXDOS which will also work). I'd be surprised if there
weren't a free version wandering around the web; sort of like MASM 6.x.
With a little tweaking, almost any C that can compile to real mode (e.g.
Borland C) should be able to handle it. The model that I compiled for
is the "Compact" one (>64K data, <64K code).
It should not be very difficult to alter for Windows 32-bit cli use
making use of WNASPI32--I just haven't had a need for it. Linux sg
might also be an option--SCSI CDBs don't change.
--Chuck
--Chuck
14 Aug
14 Aug
3 p.m.
On 8/9/15 10:21 PM, Chuck Guzis wrote:
On 08/09/2015 09:54 PM, Marc Verdiell wrote:
last 16 bit compiler is visual C++ 1.52c
also ran across MASM 8
https://www.microsoft.com/en-us/download/details.aspx?id=12654
if you need it
Well, Chuck, thanks a bunch, this is very useful
and quite difficult
code to write from scratch. How does one compile for DOS by the way
(I have to admit I am too young to have ever tried), and get a copy
of MSC 8.00C. Is the DOS compiler buried in some part of Visual
Studio? I have some old versions dating back from Windows 95 time,
when it was called Visual Studio 97... Marc
I believe it was tossed into Visual Studio 97 as a separate CD (not part of the usual
packet of Visual Basic, 32-bit C++, Visual J++, etc.) So you probably already have it.
4:30 p.m.
On 08/14/2015 12:00 PM, Al Kossow wrote:
last 16 bit compiler is visual C++ 1.52c
also ran across MASM 8
https://www.microsoft.com/en-us/download/details.aspx?id=12654
if you need it
Schizophrenic MS labeling. The C++ suite is 1.52c, but the compiler
identifies itself as 8.00c. Crazy.
--Chuck
9:08 p.m.
On 8/14/15 1:30 PM, Chuck Guzis wrote:
Schizophrenic MS labeling. The C++ suite is 1.52c,
but the compiler
identifies itself as 8.00c. Crazy.
yea.. There is a page on it on Wikipedia. Visual C++ came out after
MS C 7.0 which was Windows 3.1 time frame.
Just staring at all this because I'm scanning a redundant win 3.1 /c++
7.0 dev kit doc set we have right now.
If someone has a spare win 3.1 driver dev kit doc set, I'd like to do
that as well, but we only have one of them and I'm not going to do it
a page at a time.
10:28 p.m.
On 08/14/2015 06:08 PM, Al Kossow wrote:
> yea.. There is a page on it on Wikipedia. Visual C++ came out after
> MS C 7.0 which was Windows 3.1 time frame.
> Just staring at all this because I'm
scanning a redundant win 3.1
> /c++ 7.0 dev kit doc set we have right now.
> If someone has a spare win 3.1 driver dev
kit doc set, I'd like to
> do that as well, but we only have one of them and I'm not going to do
> it a page at a time.
I've got the Windows 3.1 DDK in big box/piles of floppies version. But
isn't the documentation (and the rest) part of the MSDN collection?
Seems to me that it is. Do you want me to check my old MSDN CDs?
--Chuck
3265
days inactive
3270
days old
6 comments
3 participants
participants (3)
-
aek＠bitsavers.org -
cclist＠sydex.com -
marc.verdiell＠gmail.com