• Please review our updated Terms and Rules here

Transferring text files from Kaypro II to Windows machine.

@DavidWien Can you share the disk image you are using to boot CP/M? If you downloaded it somewhere, share the URL. Else if you have an IMD or TD0 for it, find a place to share it? Worst case, I can setup ftp/scp access to my public server so you can put a copy there.
That's a good question. I have a couple of Kaypro CP/M master diskettes, also a .IMD disk which I am pretty sure came from here -- search for "Kaypro 3/83 disks, (also Kaypro II)". The latter I have put on the HXC2001 (A drive). I can run both format and sysgen from there and the B drive (floppies), with identical results, as far as I know.
 
Upon reviewing these photos closer, I notice that your version of CP/M does not "signon" the same as the standard Kaypro distribution. The copy I have signs on with:
Code:
KAYPRO II 64k CP/M vers 2.2

A>
while yours signs on with:
Code:
KAYPRO II
64k CP/M v 2.2

A>
So, there are some differences we may need to figure out.

In addition, when you do the SAVE you should be saving the contents of memory which should start with a copy of PIP.COM followed by the text you typed. But the first bytes of PIP.COM contain a ^Z (1AH) character at location 9 and so if you were to TYPE that you'd only get 9 characters max. The output of the "TYPE KAYPRO.TXT" command should have been:
Code:
CNδIʹʹIʹʹ
and that's all.

So, we need to start looking at what is "non-standard" in your version of CP/M. Or else how your procedure might not actually be saving what we think it is.
I hadnt noticed the two-line sign on. When I reset with the CP/M derived from the Dave's Old Computers image on the HXC2001, it is two lines. But since several of the emulated disks from there just tell you that "you are trying to boot from a master disk", I sysgened them from the floppy drive, Then the sign on is one line only. I will explore this version.
 
It looks like you must have run CONFIG, as the CP/M on the boot tracks does not match the signon message you see. Did you configure other options, and if so what were those?
 
I sysgened from the B drive and now the sign on on A is a one-liner.

I will also get a pip from the B drive and repeat the earlier experiments.
 
Doug, you can get the Kaypro3*83.zip file from here.

The monitor rom is one for Kaypro II/IV (81-232A). Nothing unusual there.
The char ROM (81-234) is like this:

CHAR-ePROM_U43_81-234.png

whereby the first two line, which often have Greek characters, are replaced.

I dont think either factor is involved in this problem. I will explore using pip from the distribution diskette, and sysgen that produces one line and get back to you later.
 
Last edited:
I'd like to get a binary copy of your 81-234 chargen ROM, so I can use it in my simulator. If you have a way to share that, please do.

I'm wondering if the BIOS was favoring the ü character (code 1AH) over ^Z and ignoring it (or converting it). If your "pristine" boot changes things, that may tell us.
 
I compared the PIP.COM from the "kaypro3*83" boot disk (kayii01) and the "standard" distro I have, and they are not the same. Something has been patched into the kayii01 version. I have not analyzed the differences to see what, but this very well may be impacting things.
 
Well, I tried this alternate PIP.COM on my simulator, and it worked (responded to ^Z correctly). So, we may be looking for something else. We probably need to see a fresh run and look at the SAVE 40 B:KAYPRO.TXT file from DUMP. Make certain you don't run any other commands after the RESET (before the SAVE).
 
Doug, Changing pip for the Kaypro Master distribution one made no difference, but I havent tested all the things you suggested, as I had to go out. Thanks for your continued interest and help!

It may be that teraterm is not much use!

David
 
Since the KAYPRO.$$$ file was never closed, it won't have any data in it.

I know that PIP does not write any records to disk until it gets a ^Z (or fills memory), so there is not going to be any data on disk anywhere.

How are you sure it was never closed or that the ^Z wasn't received? (See below...)

I still think a video of what actually happens would be very helpful. It might clear up misunderstandings we have not even identified yet.

Agreed!! Especially the "not even identified" part.

So, we need to start looking at what is "non-standard" in your version of CP/M. Or else how your procedure might not actually be saving what we think it is.

I compared the PIP.COM from the "kaypro3*83" boot disk (kayii01) and the "standard" distro I have, and they are not the same.

Now that we've gone this far, I think it will be easier to explain why I asked the question that didn't get answered from my last post to this thread.

The reason I asked if KAYPRO.$$$ had a file size (i.e. a size greater than zero) was to see if maybe PIP.COM was closing the file but not exiting for some reason. It's possible that the file had data written to it and was closed before the name change step. If PIP.COM failed before KAYPRO.$$$ was renamed to KAYPRO.TXT then the file might have been transferred properly but still appeared to be a temporary file.

The fact that the version of PIP.COM is now known to be "non-standard" means that we should question exactly when the transfer is failing. So I suggest that the initial Teraterm-to-PIP test be tried again and careful attention be paid to the resulting KAYPRO.$$$ file. Likely it will be empty. But the expected likely result has already not occurred. It makes sense to track down all the details that differ from what is expected.

Also, while I think this is nothing, I noticed from the kaypro.jpg screenshot in post #187 that the disk in drive B (which is the one being written to) has a file named RPIP.COM on it. Since we know the PIP.COM being used isn't the "standard" one, could it be a renamed version of RPIP.COM? Or is RPIP.COM a renamed "standard" PIP.COM (R standing for "Real")? Has a test file transfer with RPIP.COM been tried?
 
Both PIPs handle ^Z properly, so it seems right now that Tera Term (or the Windows PC) is not actually generating a true ^Z. It is less likely that PIP suddenly starts malfunctioning and refuses to exit when seeing ^Z. Since RESET was done, the test file most likely won't have been written and is zero length. The next most logical step is to get a clean SAVE 40 after RESET and analyze that file to see what PIP is receiving.
 
Now that we've gone this far, I think it will be easier to explain why I asked the question that didn't get answered from my last post to this thread.

The reason I asked if KAYPRO.$$$ had a file size (i.e. a size greater than zero) was to see if maybe PIP.COM was closing the file but not exiting for some reason. It's possible that the file had data written to it and was closed before the name change step. If PIP.COM failed before KAYPRO.$$$ was renamed to KAYPRO.TXT then the file might have been transferred properly but still appeared to be a temporary file.
All the *.$$$ files on my Kaypro are of zero length, as expected.
The fact that the version of PIP.COM is now known to be "non-standard" means that we should question exactly when the transfer is failing. So I suggest that the initial Teraterm-to-PIP test be tried again and careful attention be paid to the resulting KAYPRO.$$$ file. Likely it will be empty. But the expected likely result has already not occurred. It makes sense to track down all the details that differ from what is expected.
I removed the HXC2001 emulator and am now using a Tandon 100-1 disk drive with software copied from Kaypro R/O master disks. Pip from this gives the same results as described above.
Also, while I think this is nothing, I noticed from the kaypro.jpg screenshot in post #187 that the disk in drive B (which is the one being written to) has a file named RPIP.COM on it. Since we know the PIP.COM being used isn't the "standard" one, could it be a renamed version of RPIP.COM? Or is RPIP.COM a renamed "standard" PIP.COM (R standing for "Real")? Has a test file transfer with RPIP.COM been tried?
Yes. No difference. RPIP.COM is a lightly modified version of PIP.COM which was distributed in the 1908s by either MicroCornucopia or Plu*Perfect Solutions. It allows changing of diskettes in PIP without the BDOS R/O problem. I used it and other software from these and other companies at that time, with totally satisfactory results.
 
Both PIPs handle ^Z properly, so it seems right now that Tera Term (or the Windows PC) is not actually generating a true ^Z. It is less likely that PIP suddenly starts malfunctioning and refuses to exit when seeing ^Z. Since RESET was done, the test file most likely won't have been written and is zero length. The next most logical step is to get a clean SAVE 40 after RESET and analyze that file to see what PIP is receiving.
The only thing I have been able to do successfully with teraterm.com in Terminal mode on the pc is to send characters that display in term.com on the Kaypro screen, and the same in the other direction. I am unable to control operations of the Kaypro from term.com. I have never found any instructions for using teraterm, and have not proved that it does what I want.

I have also tried pip kaypro.txt=tty:,eof: with no success: pip does not finish operation.

My initial message to this group was two months ago. I have been encouraged by the kindness of those who have taken the trouble to respond, particularly durgadas311 and Larry Kraemer, and thank them in gratitude.

Reviewing that first page, my only need is to transfer ascii files created on the Kaypro to the pc, for further use on pc and subsequent publication. I can do this with ^P and type directly to my printer, and then scan to an ocr program. It was this group that encouraged me to buy a usb to DB25 cable (which was easier said than done!). The rest has been a long rabbit hole which I do not have time to explore further at present. I shall be out of the country during August and have things to do before then. When I return, I may resume this trip!

Generally, and this is not a criticism of anyone who has participated in this thread, I am disappointed that as far as I can tell, the vast majority Kaypro owners are not using them for productive work, which is a pity, because, in my experience, Perfect Writer lives up to its name and has never been bettered by anything on Windows, and Turbo Pascal is not to be sniffed at.

Most people who sell Kaypros do not know whether what they are offering is in a working state, mostly selling computers with inadequate photos, lack of keyboard or keyboard cable and, most importantly, no software. Indeed, access to diskettes, real or virtual, of useful programs is extremely limited. There is an Ebay seller who trades in copies he makes of games, but these do not interest me. In the longer term, I see that critical ICs will be unobtainable; but hopefully by then I shall not need them!

Many thanks to all. When I have time over the next 3 or so weeks, I shall continue to read postings here, but I shall have little time for experiments.

David
 
It is frustrating to not be able to see this work for you. It should not have been this difficult. But, there are always those cases where Murphy's Law dominates for some inexplicable reason.
 
It is frustrating to not be able to see this work for you. It should not have been this difficult. But, there are always those cases where Murphy's Law dominates for some inexplicable reason.
Indeed, I am very familiar with the ins and outs of Murphy's Law! Maybe after a rest we can solve the problem. In the meantime, a search for a substitute for Tera Term, which actually has a user manual, might help at the PC end. I dont understand why pip doesnt work, though I have never tried to used it in this way before. There must also be somebody who can make SSDD Kaypro-formatted diskettes with some utilities on them, including those that can be used instead of pip. This would be a help. (I thought I glimpsed a site with the µCornucopia disk images the other day; but it may have been a mirage.)

I have restored the HXC2001 = Disk A: and Tandon TM100-1 = disk B: configuration for the time being.
 
All the *.$$$ files on my Kaypro are of zero length, as expected.

Thanks for answering the question. That fills in the details and means the software doesn't seem to be the problem. But Kaypros are tricky things when it comes to software. When you bought the computer new, all the software was guaranteed to match the machine. (If there was a mismatch your dealer could fix that.) Purchasing the computer now, one can't be so sure, and there is no dealer to fix things.

Yes. No difference. RPIP.COM is a lightly modified version of PIP.COM which was distributed in the 1908s by either MicroCornucopia or Plu*Perfect Solutions. It allows changing of diskettes in PIP without the BDOS R/O problem. I used it and other software from these and other companies at that time, with totally satisfactory results.

Good. Since you were purchasing the computer and trying to match up disks (or disk images) with it, I just wanted to be sure we knew what programs were being used.

My initial message to this group was two months ago. I have been encouraged by the kindness of those who have taken the trouble to respond, particularly durgadas311 and Larry Kraemer, and thank them in gratitude.

@durgadas311 and @ldkraemer are the two most responsive and knowledgeable members we have regarding Kaypros. There are a number of times when I'd normally reply to a thread about these computers, but they've beaten me to it and with well thought out and informative responses. You are right to single them out with your gratitude. (Realizing that you also include all who've tried to help out, of course.)

Generally, and this is not a criticism of anyone who has participated in this thread, I am disappointed that as far as I can tell, the vast majority Kaypro owners are not using them for productive work, which is a pity,

No offense taken. Just to clarify: while it may appear that members' Kaypros are being used just for a hobby, that is not necessarily the case. There are many ways for a Kaypro to interact with more modern computers besides the serial port. If you have more than one computer from previous decades, you have more options. For example, there are several programs that can read Kaypro disks in IBM PCs that have 5.25" drives. This makes it easy to swap disks from machine-to-machine and directly access the 5.25" disk over a LAN to your present day workhorse.

The HXC2001 allows you to transfer data by SD card. The Kaypro files are stored in a disk image, but can be extracted on the newer computer. You can also make Kaypro disk images on the PC and read them directly on the Kaypro. There is a little extra effort this way, but it does work in both directions.

Most people who sell Kaypros do not know whether what they are offering is in a working state, mostly selling computers with inadequate photos, lack of keyboard or keyboard cable and, most importantly, no software. Indeed, access to diskettes, real or virtual, of useful programs is extremely limited.

Form what I've seen, most people selling Kaypros have found them in an attic or basement and know nothing about them, having never used them before themselves. They probably only offer them on Ebay, etc. because they found out people will pay a lot for them. Otherwise, they probably would have thrown out the "useless machine" as soon as they found it. These people wouldn't be able to know how to determine which disks are the right ones from the pile in the box beside the computer or even what makes an adequate photo set to show you which Kaypro they are trying to sell.

In regards to the software, though, this can be an especially difficult part of the problem, because Kaypro corp. was constantly changing the insides of the computer while leaving the outside practically unchanged. CP/M isn't like later OSs such as Windows, Linux, or even DOS where a newer version will easily replace the older. I've seen instances where the wrong version of CP/M 2.2 appeared to work properly on a Kaypro, only to crash later on for no apparent reason. If you think "I've got Kaypro CP/M so it will work with my Kaypro" you can easily be wrong. There were several Kaypro CP/M 2.2 versions, 2.2F, 2.2G, and 2.2U, (to name three) that were intended only for specific Kaypro models.

This may be a reason why durgadas311 can get the version of PIP.COM to work for him and you can't get it to work for you. It's also possible that your serial port has something wrong with it.

Many thanks to all. When I have time over the next 3 or so weeks, I shall continue to read postings here, but I shall have little time for experiments.

Like durgadas311 said, it's too bad you are having so much trouble getting this to work. It really shouldn't be this hard. But, such is life sometimes with all computers.
 
I have a PC81-240A motherboard and Monitor ROM labelled 81-232A. This ROM can be used with single or double-sided drives to make a Kaypro II or IV. In either case, the version of CP/M should be 2.2f. How do I check that this is what I have installed?
 
Back
Top