LisaList2

Advanced search  

News:

2022.06.03 added links to LisaList1 and LisaFAQ to the General Category

Pages: [1]   Go Down

Author Topic: BLU and HyperTerminal  (Read 3781 times)

blusnowkitty

  • Sr. Member
  • ****
  • Karma: +72/-0
  • Offline Offline
  • Posts: 248
BLU and HyperTerminal
« on: May 02, 2024, 07:44:58 pm »

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.
Logged
You haven't lived until you've heard the sound of a Sony 400k drive.

sigma7

  • Administrator
  • Sr. Member
  • *****
  • Karma: +132/-1
  • Offline Offline
  • Posts: 338
  • Warning: Memory errors found. Verify comments.
Re: BLU and HyperTerminal
« Reply #1 on: May 02, 2024, 08:59:59 pm »

any luck ... with HyperTerminal?

The BLU manual says:

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

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.

It may be that was before BLU understood CRC, but it seems worth trying.
« Last Edit: May 02, 2024, 09:08:13 pm by sigma7 »
Logged
Warning: Memory errors found. ECC non-functional. Verify comments if accuracy is important to you.

patrick

  • Sr. Member
  • ****
  • Karma: +88/-0
  • Offline Offline
  • Posts: 105
    • Patrick's Hardware Page
Re: BLU and HyperTerminal
« Reply #2 on: May 03, 2024, 02:11:28 am »

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
« Last Edit: May 04, 2024, 02:06:03 am by patrick »
Logged

compu_85

  • Sr. Member
  • ****
  • Karma: +68/-0
  • Offline Offline
  • Posts: 238
Re: BLU and HyperTerminal
« Reply #3 on: May 03, 2024, 08:00:13 pm »

I always use TeraTerm.
Logged

stepleton

  • Sr. Member
  • ****
  • Karma: +117/-0
  • Offline Offline
  • Posts: 396
Re: BLU and HyperTerminal
« Reply #4 on: May 04, 2024, 07:50:37 am »

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.
Logged

sigma7

  • Administrator
  • Sr. Member
  • *****
  • Karma: +132/-1
  • Offline Offline
  • Posts: 338
  • Warning: Memory errors found. Verify comments.
Re: BLU and HyperTerminal
« Reply #5 on: May 04, 2024, 02:55:33 pm »

Linux ... xmodem transfer ... has the annoying habit of dealing with fatal errors not just by quitting but by deleting the file that it was receiving first!

... at the very end of the transfer ... The hard drive image you spent many minutes downloading (all while wondering if the drive itself will survive!) is deleted immediately ... frustrating!

Ouch! Congrats figuring out a work-around!

There is a BLU bug report (from Ray) indicating that he saw some Linux xmodem transfers that didn't terminate properly, but it doesn't seem to be a popular problem, and his report was years after release.

Looking for info, I found this (may or may not be related): https://www.mattkeeter.com/blog/2022-05-31-xmodem/, which mentions an issue with an FTDI USB-to-serial module driver interfering with the xmodem packet timing. Apparently the driver's latency is/was easy to adjust on Windows and Linux, but not MacOS -- his MacOS fix referenced at https://openbci.com/forum/index.php?p=/discussion/comment/17915/#Comment_17915.

Can anyone confirm that the BLU xmodem issue is specifically an issue with compatibility with the Linux implementation or perhaps there are anecdotes with changing serial dongles fixing an xmodem problem?
Logged
Warning: Memory errors found. ECC non-functional. Verify comments if accuracy is important to you.

compu_85

  • Sr. Member
  • ****
  • Karma: +68/-0
  • Offline Offline
  • Posts: 238
Re: BLU and HyperTerminal
« Reply #6 on: May 05, 2024, 05:40:01 pm »

Hmm. I know I had little success with GUI terminal software on my Mac. In trying to use minicom, the installer didn't bring down the zmodem binaries... that took me hours to figure out what was going on.

-J
Logged
Pages: [1]   Go Up