From: "Robert Armstrong" <bob at jfcl.com>
> The hobbyist DECnet is actually working - we have now five distinct
> locations connected and six or seven machines online 24x7 with a couple
> dozen more that are turned on occasionally. Here's a SHOW NETWORK -
Actually, there are probably around 15 machines that are on 24x7. (Maybe
more.)
> You can see a full list of the nodes and descriptions here
>
> http://www.jfcl.com/Computers/dcn.pdf
And as I pointed out to Bob in another mail, that list is not a full
list of nodes... :-)
> We've been using Johnny's HECnet mailing list to communicate
>
> http://www.update.uu.se/~bqt/hecnet.html
>
> If you'd like to hook up we'd love to have more nodes!
Feel free.
As of now, we can connect new nodes and areas either with my bridge
program, or Bob can route DECnet over IP with Multiware.
Each as its points.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at update.uu.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
>
>Subject: RE: Archiving Software
> From: "Cini, Richard" <Richard.Cini at wachovia.com>
> Date: Fri, 16 Dec 2005 08:34:02 -0500
> To: "'General Discussion: On-Topic and Off-Topic Posts'" <cctalk at classiccmp.org>
>
>The method (using PIP and a COM port) works well for physical machines. We
>wrote these utilities for the Altair32 to talk directly to the host
>hardware.
>
>Point being that someone could write a generic CP/M utility which can dump a
>disk image over a COM port instead of only a file. I like ADT because it has
>the nifty ability to download the transfer program to the Apple using
>console redirection...ADT basically stuffs a monitor script into the Apple
>over the serial connection. CP/M probably has the same ability...I don't
>know.
How about MDM7? I've used that inside Dave's Horizon Sim with good success.
The MDM7 I used was allready setup for a NS* IO and the Sim maps NS* IO
to COM ports.
There are two different issues here:
* Transfering CP/M files and MDM7 (XMDM, Kermit ...) do that well.
The Sim side issues vary depening on how IO is simulated.
For example MyZ80 transfering CP/M files is trivial as there
is a utility inside the emulated CPM for reading and writing
outside to DOS filesystem. Others are not as flexible.
* booting a system that has a unique NON-PC compatable format.
This varies all over the map depending on target system.
Allison
>
>-----Original Message-----
>From: cctalk-bounces at classiccmp.org [mailto:cctalk-bounces at classiccmp.org]
>On Behalf Of Allison
>Sent: Friday, December 16, 2005 8:25 AM
>To: cctalk at classiccmp.org
>Subject: RE: Archiving Software
>
>>
>>Subject: RE: Archiving Software
>> From: "Cini, Richard" <Richard.Cini at wachovia.com>
>> Date: Fri, 16 Dec 2005 08:16:24 -0500
>> To: "'General Discussion: On-Topic and Off-Topic Posts'"
><cctalk at classiccmp.org>
>>
>>
>>For archiving MSDOS disks I use ZIP files unless the disk is bootable, in
>>which case I use readimg/writimg (Microsoft utilities).
>>
>>For cross-platform archiving, the only thing I've done so far is on the
>>Apple, using ADT.
>>
>>However, ADT brings-up an idea. In my Altair emulator, we have a CP/M
>>utility on one of the disk images which allows you to transfer files from
>>the host to the emulator space and back (read.com and write.com I think).
>>The program uses an invalid opcode trap to communicate with the host file
>>system. You would use a program to convert a CP/M COM program on the host
>to
>>an Intel HEX file which is then read into the CP/M environment through the
>>trap mechanism. The reverse would happen except that the "write" does not
>>convert it to Intel HEX -- it deposits it as a CP/M COM file.
>
>There are programs for CP/M to handel hexfiles:
>
>LOAD creates a com file from hex (CP/M standard tool)
>DDT/SID/ZSID can do the same.
>
>Unload is a PD program (small) that can create an intel hexfile from
>a .com file (the reverse of load).
>
>Those two with PIP file.foo=CON: [or rdr:] can move files in or out
>on a serial port.
>
>There are many ways of doing this.
>
>Allison
>
>>The source is on one of the disk images. There's no reason why it couldn't
>>be enhanced to move entire disk images instead of just files, and since
>it's
>>a CP/M utility it should work on any CP/M system. Unfortunately I don't
>have
>>enough experience in programming for CP/M, nor the time right now, to do
>it.
>>
>>Rich
>>
>>-----Original Message-----
>>From: cctalk-bounces at classiccmp.org [mailto:cctalk-bounces at classiccmp.org]
>>On Behalf Of Jules Richardson
>>Sent: Friday, December 16, 2005 7:02 AM
>>To: On-Topic and Off-Topic Posts
>>Subject: Re: Archiving Software
>>
>>M H Stein wrote:
>>> Aside from bootable system disks, for which Dave Dunfield's imaging
>>program
>>> seems to be a much better solution than Teledisk, what's the best way to
>>> archive software in a way that makes it as universally useable as
>possible
>>and
>>> downloadable/emailable?
>>
>>ImageDisk seems like a definite step in the right direction - it's
>certainly
>>
>>done a brilliant job when I've tried it.
>>
>>What it now needs IMHO is multi-platform support so that you don't *have*
>to
>>
>>use DOS and so that it can be used by more people. (Whether a Windows
>>version
>>is viable I don't know; certainly Linux seems to give you all sorts of ways
>>to
>>reach the bare hardware though - presumably *BSD would be the same)
>>
>>Other than that it seems a viable tool to use - the file format has a
>>comment
>>field of unlimited length for any useful metadata, and is able to record
>>where
>>bad spots were on the original disk.
>>
>>> For example, I have original distribution diskettes for CP/M Wordstar,
>>> Supercalc, etc. on 8" disks. Obviously images wouldn't be very useful for
>
>>> someone with only 5" drives or no 8" drive on the PC; on the other hand,
>>> a DOS ZIP file of the files on that disk would have to be
>copied/converted
>>
>>> back to a CP/M format disk somehow.
>>
>>Well the ImageDisk file format's public - I suppose there's nothing to stop
>
>>someone writing utilities to pull data out of an image at the file level,
>>then
>>spitting them across a serial link with a terminal app to the original
>>hardware. Or converting them back into a 5.25" image file, say.
>>
>>Getting the data off (and knowing you've captured it all) and onto modern
>>media is probably more important than what tools someone may use in the
>>future
>>to interpret the data. Providing it's all captured of course!
>>
>>> So, how are the rest of you dealing with this?
>>
>>Burying heads in sand I suspect :) I've finally got a PC that'll handle FM
>>data (I think it was the 7th one I tried!), so I can start imaging my own
>>collection. Luckily I just have soft-sectored MFM/FM disks here; no
>>hard-sectored stuff, GCR encoded media etc.
>>
>>I need to make the host machine dual-boot DOS/Linux so I can just use DOS
>to
>>
>>the actual reading/writing, then Linux for everything else (archival, any
>>processing of the files, taking advantage of being able to use longer
>>filenames etc.).
>>
>>I'll give DOSEMU a try under Linux to see if it'll run ImageDisk, but I
>>suspect it won't allow the necessary direct access to the hardware... but
>>I'm
>>happy to dedicate a box to disk imaging, so it doesn't really matter if the
>
>>Linux floppy subsystem gets clobbered in the process. I suspect that
>>ImageDisk
>>won't even run under DOSEMU though.
>>
>>
>>cheers
>>
>>Jules
>
>Subject: RE: Archiving Software
> From: "Cini, Richard" <Richard.Cini at wachovia.com>
> Date: Fri, 16 Dec 2005 08:16:24 -0500
> To: "'General Discussion: On-Topic and Off-Topic Posts'" <cctalk at classiccmp.org>
>
>
>For archiving MSDOS disks I use ZIP files unless the disk is bootable, in
>which case I use readimg/writimg (Microsoft utilities).
>
>For cross-platform archiving, the only thing I've done so far is on the
>Apple, using ADT.
>
>However, ADT brings-up an idea. In my Altair emulator, we have a CP/M
>utility on one of the disk images which allows you to transfer files from
>the host to the emulator space and back (read.com and write.com I think).
>The program uses an invalid opcode trap to communicate with the host file
>system. You would use a program to convert a CP/M COM program on the host to
>an Intel HEX file which is then read into the CP/M environment through the
>trap mechanism. The reverse would happen except that the "write" does not
>convert it to Intel HEX -- it deposits it as a CP/M COM file.
There are programs for CP/M to handel hexfiles:
LOAD creates a com file from hex (CP/M standard tool)
DDT/SID/ZSID can do the same.
Unload is a PD program (small) that can create an intel hexfile from
a .com file (the reverse of load).
Those two with PIP file.foo=CON: [or rdr:] can move files in or out
on a serial port.
There are many ways of doing this.
Allison
>The source is on one of the disk images. There's no reason why it couldn't
>be enhanced to move entire disk images instead of just files, and since it's
>a CP/M utility it should work on any CP/M system. Unfortunately I don't have
>enough experience in programming for CP/M, nor the time right now, to do it.
>
>Rich
>
>-----Original Message-----
>From: cctalk-bounces at classiccmp.org [mailto:cctalk-bounces at classiccmp.org]
>On Behalf Of Jules Richardson
>Sent: Friday, December 16, 2005 7:02 AM
>To: On-Topic and Off-Topic Posts
>Subject: Re: Archiving Software
>
>M H Stein wrote:
>> Aside from bootable system disks, for which Dave Dunfield's imaging
>program
>> seems to be a much better solution than Teledisk, what's the best way to
>> archive software in a way that makes it as universally useable as possible
>and
>> downloadable/emailable?
>
>ImageDisk seems like a definite step in the right direction - it's certainly
>
>done a brilliant job when I've tried it.
>
>What it now needs IMHO is multi-platform support so that you don't *have* to
>
>use DOS and so that it can be used by more people. (Whether a Windows
>version
>is viable I don't know; certainly Linux seems to give you all sorts of ways
>to
>reach the bare hardware though - presumably *BSD would be the same)
>
>Other than that it seems a viable tool to use - the file format has a
>comment
>field of unlimited length for any useful metadata, and is able to record
>where
>bad spots were on the original disk.
>
>> For example, I have original distribution diskettes for CP/M Wordstar,
>> Supercalc, etc. on 8" disks. Obviously images wouldn't be very useful for
>> someone with only 5" drives or no 8" drive on the PC; on the other hand,
>> a DOS ZIP file of the files on that disk would have to be copied/converted
>
>> back to a CP/M format disk somehow.
>
>Well the ImageDisk file format's public - I suppose there's nothing to stop
>someone writing utilities to pull data out of an image at the file level,
>then
>spitting them across a serial link with a terminal app to the original
>hardware. Or converting them back into a 5.25" image file, say.
>
>Getting the data off (and knowing you've captured it all) and onto modern
>media is probably more important than what tools someone may use in the
>future
>to interpret the data. Providing it's all captured of course!
>
>> So, how are the rest of you dealing with this?
>
>Burying heads in sand I suspect :) I've finally got a PC that'll handle FM
>data (I think it was the 7th one I tried!), so I can start imaging my own
>collection. Luckily I just have soft-sectored MFM/FM disks here; no
>hard-sectored stuff, GCR encoded media etc.
>
>I need to make the host machine dual-boot DOS/Linux so I can just use DOS to
>
>the actual reading/writing, then Linux for everything else (archival, any
>processing of the files, taking advantage of being able to use longer
>filenames etc.).
>
>I'll give DOSEMU a try under Linux to see if it'll run ImageDisk, but I
>suspect it won't allow the necessary direct access to the hardware... but
>I'm
>happy to dedicate a box to disk imaging, so it doesn't really matter if the
>Linux floppy subsystem gets clobbered in the process. I suspect that
>ImageDisk
>won't even run under DOSEMU though.
>
>
>cheers
>
>Jules
For archiving MSDOS disks I use ZIP files unless the disk is bootable, in
which case I use readimg/writimg (Microsoft utilities).
For cross-platform archiving, the only thing I've done so far is on the
Apple, using ADT.
However, ADT brings-up an idea. In my Altair emulator, we have a CP/M
utility on one of the disk images which allows you to transfer files from
the host to the emulator space and back (read.com and write.com I think).
The program uses an invalid opcode trap to communicate with the host file
system. You would use a program to convert a CP/M COM program on the host to
an Intel HEX file which is then read into the CP/M environment through the
trap mechanism. The reverse would happen except that the "write" does not
convert it to Intel HEX -- it deposits it as a CP/M COM file.
The source is on one of the disk images. There's no reason why it couldn't
be enhanced to move entire disk images instead of just files, and since it's
a CP/M utility it should work on any CP/M system. Unfortunately I don't have
enough experience in programming for CP/M, nor the time right now, to do it.
Rich
-----Original Message-----
From: cctalk-bounces at classiccmp.org [mailto:cctalk-bounces at classiccmp.org]
On Behalf Of Jules Richardson
Sent: Friday, December 16, 2005 7:02 AM
To: On-Topic and Off-Topic Posts
Subject: Re: Archiving Software
M H Stein wrote:
> Aside from bootable system disks, for which Dave Dunfield's imaging
program
> seems to be a much better solution than Teledisk, what's the best way to
> archive software in a way that makes it as universally useable as possible
and
> downloadable/emailable?
ImageDisk seems like a definite step in the right direction - it's certainly
done a brilliant job when I've tried it.
What it now needs IMHO is multi-platform support so that you don't *have* to
use DOS and so that it can be used by more people. (Whether a Windows
version
is viable I don't know; certainly Linux seems to give you all sorts of ways
to
reach the bare hardware though - presumably *BSD would be the same)
Other than that it seems a viable tool to use - the file format has a
comment
field of unlimited length for any useful metadata, and is able to record
where
bad spots were on the original disk.
> For example, I have original distribution diskettes for CP/M Wordstar,
> Supercalc, etc. on 8" disks. Obviously images wouldn't be very useful for
> someone with only 5" drives or no 8" drive on the PC; on the other hand,
> a DOS ZIP file of the files on that disk would have to be copied/converted
> back to a CP/M format disk somehow.
Well the ImageDisk file format's public - I suppose there's nothing to stop
someone writing utilities to pull data out of an image at the file level,
then
spitting them across a serial link with a terminal app to the original
hardware. Or converting them back into a 5.25" image file, say.
Getting the data off (and knowing you've captured it all) and onto modern
media is probably more important than what tools someone may use in the
future
to interpret the data. Providing it's all captured of course!
> So, how are the rest of you dealing with this?
Burying heads in sand I suspect :) I've finally got a PC that'll handle FM
data (I think it was the 7th one I tried!), so I can start imaging my own
collection. Luckily I just have soft-sectored MFM/FM disks here; no
hard-sectored stuff, GCR encoded media etc.
I need to make the host machine dual-boot DOS/Linux so I can just use DOS to
the actual reading/writing, then Linux for everything else (archival, any
processing of the files, taking advantage of being able to use longer
filenames etc.).
I'll give DOSEMU a try under Linux to see if it'll run ImageDisk, but I
suspect it won't allow the necessary direct access to the hardware... but
I'm
happy to dedicate a box to disk imaging, so it doesn't really matter if the
Linux floppy subsystem gets clobbered in the process. I suspect that
ImageDisk
won't even run under DOSEMU though.
cheers
Jules
>
>Subject: Re: Archiving Software
> From: Jules Richardson <julesrichardsonuk at yahoo.co.uk>
> Date: Fri, 16 Dec 2005 12:01:51 +0000
> To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org>
>
>M H Stein wrote:
>> Aside from bootable system disks, for which Dave Dunfield's imaging program
>> seems to be a much better solution than Teledisk, what's the best way to
>> archive software in a way that makes it as universally useable as possible and
>> downloadable/emailable?
>
>ImageDisk seems like a definite step in the right direction - it's certainly
>done a brilliant job when I've tried it.
>
>What it now needs IMHO is multi-platform support so that you don't *have* to
>use DOS and so that it can be used by more people. (Whether a Windows version
>is viable I don't know; certainly Linux seems to give you all sorts of ways to
>reach the bare hardware though - presumably *BSD would be the same)
>
>Other than that it seems a viable tool to use - the file format has a comment
>field of unlimited length for any useful metadata, and is able to record where
>bad spots were on the original disk.
My solution for CP/M disk so I can work at the file level is to use one of
David's emulators and serial down/up load the content using xmodem to either
a copy of Procom running on the same box or to a real CP/M crate. The SIM
to Procom thing has caveats (I had to fire up a win98se box) as NT is to fussy
about touching the metal. However, once i had the w98se engine going I had to
loop com1 to com2 (real wire!) worked well using the Horizon Sim. The first
case was Sim to real CP/M machine and that neatly sidesteps the old two systems
common OS incompatable media.
>> For example, I have original distribution diskettes for CP/M Wordstar,
>> Supercalc, etc. on 8" disks. Obviously images wouldn't be very useful for
>> someone with only 5" drives or no 8" drive on the PC; on the other hand,
>> a DOS ZIP file of the files on that disk would have to be copied/converted
>> back to a CP/M format disk somehow.
>
>Well the ImageDisk file format's public - I suppose there's nothing to stop
>someone writing utilities to pull data out of an image at the file level, then
>spitting them across a serial link with a terminal app to the original
>hardware. Or converting them back into a 5.25" image file, say.
If you want to get/put files on CP/M disks the problem is one level more
complex. To do image manipulation of CP/M disks the utility must understand
CP/M filesystem AND know the know the internal format of the media imaged.
For example the internal format of a single density NS* CP/M disk is layed
out different from a Compupro CP/M image internally. Reason for that is CP/M
applies allocation blocks of differing granularity that is disk size dependent
and also sector skewing. So to read or write the internal file you need to run
the equivilent of a CP/M BDOS and disk portion of the BIOS. Not that difficult
but certainly more effort. The ugly part is getting the CP/M disk parameter
table and sector skew data into the tool for each imaged cp/m disk.
>Getting the data off (and knowing you've captured it all) and onto modern
>media is probably more important than what tools someone may use in the future
>to interpret the data. Providing it's all captured of course!
Without a doubt.
>> So, how are the rest of you dealing with this?
>
>Burying heads in sand I suspect :) I've finally got a PC that'll handle FM
>data (I think it was the 7th one I tried!), so I can start imaging my own
>collection. Luckily I just have soft-sectored MFM/FM disks here; no
>hard-sectored stuff, GCR encoded media etc.
For NS* hard sector a real NS* and the Sim work fine. For others I have
real systems and serial ports.
>I need to make the host machine dual-boot DOS/Linux so I can just use DOS to
>the actual reading/writing, then Linux for everything else (archival, any
>processing of the files, taking advantage of being able to use longer
>filenames etc.).
>
>I'll give DOSEMU a try under Linux to see if it'll run ImageDisk, but I
>suspect it won't allow the necessary direct access to the hardware... but I'm
>happy to dedicate a box to disk imaging, so it doesn't really matter if the
>Linux floppy subsystem gets clobbered in the process. I suspect that ImageDisk
>won't even run under DOSEMU though.
Dos is not as bothersome as full out winders. though I've found my W9x boxes
do this well enough and as demonstrated I can run sim to procom so sim to sim
may be possible on one box and with two boxes no question.
Allison
Hi Jim,
I read your message on the control of a Tek2712 via GPIB.
I have a Tek2712 myself with no serial interface, however I do have a GPIB.
I also have a Ethernet to GPIB interface and are able to control my HP 53131
counter via GPIB, so I know it all works fine. I am struggling to find
appropriate drivers or basic control s/w that allows me to connect the
Tek2712 to the GPIB I/F.
My aim is to simply print, however any additional features would help.
Are you able to provide more detail of how you went about controlling your
Tek2712 via GPIB?
Regards
Gerald Molenkamp
Melbourne Australia
The method (using PIP and a COM port) works well for physical machines. We
wrote these utilities for the Altair32 to talk directly to the host
hardware.
Point being that someone could write a generic CP/M utility which can dump a
disk image over a COM port instead of only a file. I like ADT because it has
the nifty ability to download the transfer program to the Apple using
console redirection...ADT basically stuffs a monitor script into the Apple
over the serial connection. CP/M probably has the same ability...I don't
know.
-----Original Message-----
From: cctalk-bounces at classiccmp.org [mailto:cctalk-bounces at classiccmp.org]
On Behalf Of Allison
Sent: Friday, December 16, 2005 8:25 AM
To: cctalk at classiccmp.org
Subject: RE: Archiving Software
>
>Subject: RE: Archiving Software
> From: "Cini, Richard" <Richard.Cini at wachovia.com>
> Date: Fri, 16 Dec 2005 08:16:24 -0500
> To: "'General Discussion: On-Topic and Off-Topic Posts'"
<cctalk at classiccmp.org>
>
>
>For archiving MSDOS disks I use ZIP files unless the disk is bootable, in
>which case I use readimg/writimg (Microsoft utilities).
>
>For cross-platform archiving, the only thing I've done so far is on the
>Apple, using ADT.
>
>However, ADT brings-up an idea. In my Altair emulator, we have a CP/M
>utility on one of the disk images which allows you to transfer files from
>the host to the emulator space and back (read.com and write.com I think).
>The program uses an invalid opcode trap to communicate with the host file
>system. You would use a program to convert a CP/M COM program on the host
to
>an Intel HEX file which is then read into the CP/M environment through the
>trap mechanism. The reverse would happen except that the "write" does not
>convert it to Intel HEX -- it deposits it as a CP/M COM file.
There are programs for CP/M to handel hexfiles:
LOAD creates a com file from hex (CP/M standard tool)
DDT/SID/ZSID can do the same.
Unload is a PD program (small) that can create an intel hexfile from
a .com file (the reverse of load).
Those two with PIP file.foo=CON: [or rdr:] can move files in or out
on a serial port.
There are many ways of doing this.
Allison
>The source is on one of the disk images. There's no reason why it couldn't
>be enhanced to move entire disk images instead of just files, and since
it's
>a CP/M utility it should work on any CP/M system. Unfortunately I don't
have
>enough experience in programming for CP/M, nor the time right now, to do
it.
>
>Rich
>
>-----Original Message-----
>From: cctalk-bounces at classiccmp.org [mailto:cctalk-bounces at classiccmp.org]
>On Behalf Of Jules Richardson
>Sent: Friday, December 16, 2005 7:02 AM
>To: On-Topic and Off-Topic Posts
>Subject: Re: Archiving Software
>
>M H Stein wrote:
>> Aside from bootable system disks, for which Dave Dunfield's imaging
>program
>> seems to be a much better solution than Teledisk, what's the best way to
>> archive software in a way that makes it as universally useable as
possible
>and
>> downloadable/emailable?
>
>ImageDisk seems like a definite step in the right direction - it's
certainly
>
>done a brilliant job when I've tried it.
>
>What it now needs IMHO is multi-platform support so that you don't *have*
to
>
>use DOS and so that it can be used by more people. (Whether a Windows
>version
>is viable I don't know; certainly Linux seems to give you all sorts of ways
>to
>reach the bare hardware though - presumably *BSD would be the same)
>
>Other than that it seems a viable tool to use - the file format has a
>comment
>field of unlimited length for any useful metadata, and is able to record
>where
>bad spots were on the original disk.
>
>> For example, I have original distribution diskettes for CP/M Wordstar,
>> Supercalc, etc. on 8" disks. Obviously images wouldn't be very useful for
>> someone with only 5" drives or no 8" drive on the PC; on the other hand,
>> a DOS ZIP file of the files on that disk would have to be
copied/converted
>
>> back to a CP/M format disk somehow.
>
>Well the ImageDisk file format's public - I suppose there's nothing to stop
>someone writing utilities to pull data out of an image at the file level,
>then
>spitting them across a serial link with a terminal app to the original
>hardware. Or converting them back into a 5.25" image file, say.
>
>Getting the data off (and knowing you've captured it all) and onto modern
>media is probably more important than what tools someone may use in the
>future
>to interpret the data. Providing it's all captured of course!
>
>> So, how are the rest of you dealing with this?
>
>Burying heads in sand I suspect :) I've finally got a PC that'll handle FM
>data (I think it was the 7th one I tried!), so I can start imaging my own
>collection. Luckily I just have soft-sectored MFM/FM disks here; no
>hard-sectored stuff, GCR encoded media etc.
>
>I need to make the host machine dual-boot DOS/Linux so I can just use DOS
to
>
>the actual reading/writing, then Linux for everything else (archival, any
>processing of the files, taking advantage of being able to use longer
>filenames etc.).
>
>I'll give DOSEMU a try under Linux to see if it'll run ImageDisk, but I
>suspect it won't allow the necessary direct access to the hardware... but
>I'm
>happy to dedicate a box to disk imaging, so it doesn't really matter if the
>Linux floppy subsystem gets clobbered in the process. I suspect that
>ImageDisk
>won't even run under DOSEMU though.
>
>
>cheers
>
>Jules
I was an authorized reseller/distributor of the entire SoftCraft line of
font products, including Fancy Font and Fancy Word. Yes, I've used it (it's
been a very long time), and in fact I still have all of it, both the
programs and a very large selection of fonts (probably over 1,000, counting
different point sizes as different fonts). In fact, although it's an
anachronism and I probably have not used it in almost 20 years, I have all
of that material right here on the hard drive of this computer (along with
Microsoft Word .... FOR MS-DOS). [I also have the original distribution
copies, in the complete retail packaging, with documentation.]
:)
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
