• Please review our updated Terms and Rules here

Kaypro 1 File Copy/transfer Issue

Thorbjørn Ravn Andersen said:
I agree. Back in the day we could get around it by making a "BLOCKS.BAD" file which explicitly pointed to the areas on disk that was bad, and then CP/M didn't try to use those (as they already belonged to a file). Could make a diskette last a little longer (they were really expensive in the beginning).
Click to expand...
Is this possible on a kaypro? I'd like to give it a try. EDIT: I assume that I can do this using the FINDBAD.COM file on the kaypro.
 
Last edited:
I'm not aware of any utilities from Kaypro that do that. I did not see any such options in DUTIL.COM. There have been ones over the years, and even recently someone did work on them. But you'd still have to find a way to download that, and since you disk is bad that will be problem.

One idea. Kermit has a "SET INCOMPLETE-FILE KEEP" option which should cause Kermit to keep a failed file. What you'd have to do is keep pressing RETURN at the "Bad Sector" errors until it completed. After that, you rename the downloaded file to something like "BADBLOCK.XXX" and don't erase it. You could possibly do the same thing with PIP.
 
durgadas311 said:
I'm not aware of any utilities from Kaypro that do that. I did not see any such options in DUTIL.COM. There have been ones over the years, and even recently someone did work on them. But you'd still have to find a way to download that, and since you disk is bad that will be problem.

One idea. Kermit has a "SET INCOMPLETE-FILE KEEP" option which should cause Kermit to keep a failed file. What you'd have to do is keep pressing RETURN at the "Bad Sector" errors until it completed. After that, you rename the downloaded file to something like "BADBLOCK.XXX" and don't erase it. You could possibly do the same thing with PIP.
Click to expand...
Thank you, whenever I get the chance, I will give this a try and report back here.
 
OK, I tested the new disks out and yeah they worked. Slight issue though, with files over 16k, it gives me "Unable to receive file." I don't know if this is normal or not supposed to be happening.
 
Are you "uploading" a >16K file (Kaypro to PC)? Or downloading? The C-Kermit side might be hitting some "idle timeout" where it is taking too long for the Kaypro to load up the 8K buffer (if it's using that for uploads). I guess you're not using C-Kermit, though, are you? You have some Win95 version of Kermit?
 
durgadas311 said:
Are you "uploading" a >16K file (Kaypro to PC)? Or downloading? The C-Kermit side might be hitting some "idle timeout" where it is taking too long for the Kaypro to load up the 8K buffer (if it's using that for uploads). I guess you're not using C-Kermit, though, are you? You have some Win95 version of Kermit?
Click to expand...
I'm doing PC to Kaypro using Tera-term to send it over since it has a kermit file transfer function. It worked fine when I transferred SBASIC.COM from my PC to my Kaypro it worked fine, but I need to transfer BASICLIB.REL and it's I assume over 16k and when it reaches 16,389 bytes transferred, KERMIT on the Kaypro gives "Unable to receive file."
 
Unfortunately, Tera Term may implement the kermit protocol differently than C-Kermit, but I'll give this a try using C-Kermit. Are you using the settings I found to work?

Code: 
SET TERMINAL QUIET
SET BUFFER-SIZE 1
 
durgadas311 said:
Unfortunately, Tera Term may implement the kermit protocol differently than C-Kermit, but I'll give this a try using C-Kermit. Are you using the settings I found to work?

Code: 
SET TERMINAL QUIET
SET BUFFER-SIZE 1
Click to expand...
I was not using those settings, I can give it a try tomorrow as I have to go somewhere right now. I can also give C-Kermit a try if needed.
 
durgadas311 said:
Unfortunately, Tera Term may implement the kermit protocol differently than C-Kermit, but I'll give this a try using C-Kermit. Are you using the settings I found to work?
Click to expand...
If you have Linux (or a Mac) available, I've used minicom's Kermit protocol for many years to transfer files between Kaypros and have never had an issue or had to change any of the default Kermit settings with either side.
 
ECNeilson said:
If you have Linux (or a Mac) available, I've used minicom's Kermit protocol for many years to transfer files between Kaypros and have never had an issue or had to change any of the default Kermit settings with either side.
Click to expand...
I unfortunately do not have a Linux or Mac machine available as of now. I will give C-Kermit a try as of now, and if that doesn't work out I'll look around to see if I have a Linux or Mac anywhere.
 
and if you use an rPi, you should be able to mount shares from your Windows machine - so gives you access to the same files/directories without adding another copy operation.
 
durgadas311 said:
and if you use an rPi, you should be able to mount shares from your Windows machine - so gives you access to the same files/directories without adding another copy operation.
Click to expand...
If I can find my old rPi, I will give it a try with minicom.
 
OK, My issue has been fixed. Turns out something is wrong with tera term's implementation of the KERMIT protocol, and when I used Kermit 95 to transfer the file over, it worked. Thank you all for your help.
 
ECNeilson said:
If you have Linux (or a Mac) available, I've used minicom's Kermit protocol for many years to transfer files between Kaypros and have never had an issue or had to change any of the default Kermit settings with either side.
Click to expand...
I believe minicom will just be running C-Kermit in the background which is probably why it works properly - not much point in reimplementing the protocol themselves on unix when C-Kermit is there and free. None of the Windows terminals work this way though as the Windows version of C-Kermit (Kermit 95) used to be closed-source commercial software and was sold as a terminal emulator which would have prevented the other commercial terminal emulators from depending on it even if the cost wouldn't have been a problem for their customers.
 
davidrg said:
I believe minicom will just be running C-Kermit in the background which is probably why it works properly - not much point in reimplementing the protocol themselves on unix when C-Kermit is there and free. None of the Windows terminals work this way though as the Windows version of C-Kermit (Kermit 95) used to be closed-source commercial software and was sold as a terminal emulator which would have prevented the other commercial terminal emulators from depending on it even if the cost wouldn't have been a problem for their customers.
Click to expand...
Now I remember... I had to tell minicom what command to use for kermit. So, minicom on Linux would use C-Kermit. Not sure about Windows, but I'd think it was similar except I don't think there is a C-Kermit for that. But, if all I'm doing is kermit then there's really no reason for the minicom or tera-term, since there's no need to "log in" or whatnot. I ditched minicom as soon as I discovered that, and just ran kermit (server mode) directly on the serial port.
 
durgadas311 said:
Now I remember... I had to tell minicom what command to use for kermit. So, minicom on Linux would use C-Kermit. Not sure about Windows, but I'd think it was similar except I don't think there is a C-Kermit for that. But, if all I'm doing is kermit then there's really no reason for the minicom or tera-term, since there's no need to "log in" or whatnot. I ditched minicom as soon as I discovered that, and just ran kermit (server mode) directly on the serial port.
Click to expand...
I think Windows 95 was just a port of C-Kermit to windows, I think they're mostly the same except ones for a different OS.
 
Kermit 95 is a bit more than just a port of C-Kermit to Windows (and OS/2). Functionality-wise its closer to a superset of Tera Term and C-Kermit, adding:
  • A few dozen terminal emulations (list)
  • Built-in X/Y/Z-modem support
  • On Windows XP SP3 and newer a built-in SSH client (older versions used to support SSH on Windows 9x and NT too)
  • Named Pipe connections, and the OS/2 version supports NetBIOS too
  • LAT and CTERM connections if you've got DEC Pathworks installed
  • REXX scripting as of the current release (the OS/2 version always supported it)
(I'm the current maintainer of Kermit 95)
 
You must log in or register to reply here.
Back
Top