General Category > LisaList2

BLU and HyperTerminal

(1/2) > >>

blusnowkitty:
Has anyone ever had any luck dumping diskettes and transferring them with HyperTerminal? I replaced my SCC today and while all the replacements I got all now work fine for simply bashing on the keyboard to make text pop out of either end, I cannot either end to see an Xmodem transfer.


For the curious: I suspect my original SCC is one of those infamous faulty chips sold as NOS - there's no evidence of sanding, but the legs were all suspiciously tinned. Oh well, I have a bunch of very pretty ceramic and gold SCCs now, so I'm happy.

sigma7:

--- Quote from: blusnowkitty on May 02, 2024, 07:44:58 pm ---any luck ... with HyperTerminal?

--- End quote ---

The BLU manual says:


--- Quote ---NOTE: HyperTerminal won't work for bootstrapping as it mangles CR/LF combinations!
--- End quote ---

Which seems sufficiently specific that it might do an xmodem transfer ok, but it could also mean it was a non-starter and so wasn't considered worth testing -- sorry I don't recall.

Given no progress in either direction, I'd guess it is a handshaking issue.

In any case, trying an alternative may be informative.

Good luck!

edit:

This post from Ray implies that HyperTerminal could work, but doesn't confirm he tested it.

edit 2:

In a 2007-02-01 email exchange with Ray there is this comment:


--- Quote ---HyperTerminal rejects the data UNLESS you wait until a couple of timeout failures pass; whence it switches from CRC to checksum; if you start sending then it works ok.
--- End quote ---

It may be that was before BLU understood CRC, but it seems worth trying.

patrick:
The version of Hyperterminal that comes with Windows XP works fine with both BLU and UsbWidEx XMODEM transfers. This runs on the lab notebook I'm using with vintage computer hardware

compu_85:
I always use TeraTerm.

stepleton:
I'm a Linux person, and I don't have relevant things to say for Windows. But since we're talking about xmodem transfer, the standard Linux program that does xmodem, ymodem, and zmodem reception ("rx", "rb", and "rz", but deep down it's the same program) has the annoying habit of dealing with fatal errors not just by quitting but by deleting the file that it was receiving first!

While I forget whether this led to trouble with BLU, with UsbWidEx, there's a disagreement between the way rx does xmodem and the way UsbWidEx does it. This disagreement arises at the very end of the transfer, and rx has a tantrum and fatal-errors. The hard drive image you spent many minutes downloading (all while wondering if the drive itself will survive!) is deleted immediately. It's very frustrating!

The quick-and-dirty workaround is to go to another terminal window while the image is being transferred and make a hard link (plain `ln`, not `ln -s`) to the file being downloaded. rx will unlink the original filesystem entry for the image, but your second entry is just as good. The image itself will be fine no matter what rx thinks about it.

Navigation

[0] Message Index

[#] Next page