A complication with the cube computer arose in that the LapLink software it uses forces 2400,n,8,1 with parity when it remote installs. Something about that bothered a part of my mind that has been dormant since…well, DOS.

Using parity under some DOS's copy command is sometimes flaky. Using no parity on the DOS side will enable it to get the bootstrap file properly but the actual transfer utility (Some freakily named COM file that is sent over) will insist on parity and the process pukes.

You could do it manually but…

c:\mode com1:2400,n,8,1
c:\copy com1: somefile.exe

Doesn't work because it's binary. So..binary switch?
c:\mode com1:2400,n,8,1
c:\copy /b com1: somefile.exe

Nope. Doesn't work because there's no way for copy command to know when the end of file is transmitted. This is why a special COM file to do the transfer is sent across. I haven't looked but I suspect it ends with a EOF and is crafted in such a way that one does NOT appear in the middle of the binary itself. Which is kind of clever.

So, I have to send a floppy down with the LapLink software too. He assures me his floppy drive still works. We're going to find out soon.

Edit: I can't format for crap and I inexplicable substituted ctty for mode. I think I need a nap.

2016-10-06T04:17:35Z