The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Arthur Krewat <krewat@kilonet.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Floppy to modern files for Usenet maps
Date: Sun, 23 Jun 2019 20:50:47 -0400	[thread overview]
Message-ID: <061daf0b-e01c-075f-2b01-ef0db7bbf2b6@kilonet.net> (raw)
In-Reply-To: <bb6f6575-0497-a78d-61af-dbb4321a944b@spamtrap.tnetconsulting.net>

Another thing to think about, and that's only because I'm a 
dumpster-diver, is what's in the unallocated sectors? ;)


On 6/23/2019 8:02 PM, Grant Taylor via TUHS wrote:
> On 6/23/19 5:52 PM, Arthur Krewat wrote:
>> Does the AT&T have a serial port?
>>
>> Kermit would be the way I'd go, but since you say you have nothing 
>> with serial ports, that could be a problem. A cheap usb-to-serial 
>> port might be in order. Then you can run Kermit 95 on a Windows 7 or 
>> earlier machine. (might work on later OS's too, but it's not supported)
>>
>> The flip side is how to get Kermit onto the DOS machine.
>
> Does Kermit have an option like INTERLNK & INTERSVR have where you can 
> run a "copy COM1 INTERxxx.EXE" to push the software across the serial 
> port?

Not that I'm aware of. Things like NULs, and ^S can really ruin your 
day. Not to mention ^Z which a DOS copy might interpret as EOF. I only 
ever wrote programs to access the UART directly, but I remember my 
attempts at COPY or other DOS-specific ways of dealing with serial ports 
were never very successful. But that might have had more to do with 
buffer overruns (or in the case of the 8250 in the XT, a lack of a FIFO 
ala-16550 in the first place). Redirecting LPT1 to COM1 using MODE, I 
used to print to an LA100 using hardware handshaking.

>> I used a floppy recovery service a while back to read my old 
>> Commodore 64/PET disks - he was relatively inexpensive, and very 
>> responsive.
>>
>> http://retrofloppy.com/
>
> If the machine is able to read the files without error, then a 
> recovery service might not be necessary.  IMHO it's a question of 
> getting one or more copies onto something else so that the existing 
> floppy isn't the only copy.

Of course, but in some cases, a few $'s thrown at the problem is easier 
than messing around with something you don't want to mess around with ;)

I would be happy to contribute.


  parent reply	other threads:[~2019-06-24  0:58 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23 23:10 Mary Ann Horton Gmail
2019-06-23 23:52 ` Arthur Krewat
2019-06-24  0:02   ` Grant Taylor via TUHS
2019-06-24  0:35     ` Mary Ann Horton Gmail
2019-06-24  0:53       ` Arthur Krewat
2019-06-24  0:56         ` Larry McVoy
2019-06-24  1:12           ` Arthur Krewat
2019-06-24  1:31             ` William Pechter
2019-06-24  1:51               ` Arthur Krewat
2019-06-24  1:40         ` Bakul Shah
2019-06-24  3:20           ` Grant Taylor via TUHS
2019-06-24  0:50     ` Arthur Krewat [this message]
2019-06-24 21:07     ` Michael Kjörling
2019-06-24 21:30       ` Steve Nickolas
2019-06-24 21:59         ` Gregg Levine
2019-06-23 23:57 ` Grant Taylor via TUHS
2019-06-24  0:40   ` Mary Ann Horton Gmail
2019-06-24  1:37     ` William Pechter
2019-06-24  3:17     ` Jason Stevens
2019-06-24  1:57   ` Steve Nickolas
2019-06-24  2:09     ` pechter
2019-06-24  0:03 ` Theodore Ts'o
2019-06-24  0:19 ` Seth Morabito
2019-06-24  0:33 ` Larry McVoy
2019-06-24  1:58   ` Steve Nickolas
2019-06-25  3:54 ` Jonathan Gevaryahu
2019-06-25 11:21   ` ckeck
2019-07-09 16:28 ` Mary Ann Horton Gmail
2019-07-09 16:53   ` KatolaZ
2019-07-09 17:12   ` Henry Bent
2019-07-09 17:25     ` Seth Morabito
2019-07-09 17:34       ` Henry Bent
2019-07-09 19:19         ` Henry Bent
2019-07-09 19:41           ` Richard Salz
2019-07-09 20:09           ` Grant Taylor via TUHS
2019-07-09 20:58             ` Henry Bent
2019-07-09 20:54           ` Mary Ann Horton Gmail
2019-07-09 21:30             ` Grant Taylor via TUHS
2019-07-09 21:35               ` Grant Taylor via TUHS
2019-07-09 21:37             ` Grant Taylor via TUHS
2019-07-09 21:46               ` Henry Bent
2019-07-09 22:02                 ` Henry Bent
2019-07-09 23:23                   ` Mary Ann Horton Gmail
2019-07-10  0:06                     ` Dan Cross
2019-07-10  0:26                       ` Grant Taylor via TUHS
2019-07-10  0:38                         ` Dan Cross
2019-07-10  0:49                           ` Larry McVoy
2019-07-10  0:57                             ` Clem Cole
2019-07-10  1:26                               ` [TUHS] V0 B Compiler Warren Toomey
2019-07-10  1:29                                 ` Clem Cole
2019-07-10  1:32                                   ` [TUHS] Plot 10 Sources Clem Cole
2019-07-10  2:51                                     ` Charles Anthony
2019-07-10  3:00                                       ` Charles Anthony
2019-07-10  3:01                                       ` Clem Cole
2019-07-10 12:51                                     ` Nelson H. F. Beebe
2019-07-10 14:34                                       ` Clem cole
2019-07-10  1:02                             ` [TUHS] Floppy to modern files for Usenet maps Arthur Krewat
2019-07-10  1:19                               ` Larry McVoy
2019-07-10  1:34                                 ` Dave Horsfall
2019-07-10  0:28                       ` Mary Ann Horton Gmail
2019-07-09 22:01               ` Mary Ann Horton Gmail
2019-07-09 22:44                 ` Grant Taylor via TUHS
2019-07-09 23:14                   ` Mary Ann Horton Gmail
2019-07-10  0:24                     ` Grant Taylor via TUHS
2019-07-10  1:13                       ` Mary Ann Horton Gmail
2019-07-09 17:33     ` Clem Cole
2019-07-15  3:21   ` [TUHS] Historical " Mary Ann Horton Gmail

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=061daf0b-e01c-075f-2b01-ef0db7bbf2b6@kilonet.net \
    --to=krewat@kilonet.net \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).