• Please review our updated Terms and Rules here

Problems with VirtualKaypro hard disk image

The Mad Turk

Member
Joined
Apr 5, 2022
Messages
10
Location
Seattle
Hi, I was very pleased to discover the Virtual Kaypro website and spent last evening merrily mounting disk images and exploring. Unfortunately, the WD1002-0.U.cpm3 image with the kaypro10e and kaypro10.cpnet config files seems to get caught in a boot loop --over and over, it displays "*KAYPRO 10 v1.9E* while alternately flashing the "10MB Ready" and "floppy" lights. I've mounted other hard drive images without difficulty under both MacOS Monterey and Windows 10, and I've tried a fresh download of the image. I'm very interested in trying the CP/Net features. Is this a known problem, or something with a work-around? Thanks!
 
The problem is the difference between the original Kaypro 10 (ROM, HDD format) and the later "universal mainboard" systems (different HDD format). The HDD image "WD1002-0.U.cpm3" is for the Universal system, and the "kaypro10e" config file is for the original Kaypro 10. Try using the "kaypro10eu*" config files with the HDD image you have.
 
Were you able to get this working? Using the combination of WD1002-0.U.cpm3 disk image and kaypro10eu.cpnet config file I was able to make it work. Also note, you need to edit the property "wd1002_disk1" in the config file to match the disk image (and path to it) that you want to use.
 
Hi, Do
Were you able to get this working? Using the combination of WD1002-0.U.cpm3 disk image and kaypro10eu.cpnet config file I was able to make it work. Also note, you need to edit the property "wd1002_disk1" in the config file to match the disk image (and path to it) that you want to use.
Hi, Doug.

My posts are still being moderated, and my response to your first reply hasn't been released yet. I went through my virtual Kaypro folder and cleared everything out, recopied the disk image and config files, renamed the disk, put the new disk name in the config (including the full path, though it's in the same folder as the jar file), and got the same result: a screen showing "Kaypro Corporation Version 2.01" with all lights on the front panel except the CP/Net-08 lit up.
 
All I can think of is that the disk image is not getting downloaded correctly. The size should be 10653824 bytes. I'm not sure what crc/checksum programs Windows has, so it probably doesn't make sense to provide a checksum from Linux. One thing I'm wondering is if Windows is getting concerned about the size and binary nature of the disk image, and instead of downloading a "pure" copy of it there is some filtering/modification/virus-protection going on.
 
All I can think of is that the disk image is not getting downloaded correctly. The size should be 10653824 bytes. I'm not sure what crc/checksum programs Windows has, so it probably doesn't make sense to provide a checksum from Linux. One thing I'm wondering is if Windows is getting concerned about the size and binary nature of the disk image, and instead of downloading a "pure" copy of it there is some filtering/modification/virus-protection going on.
I'm actually downloading on a Mac, not Windows (though I've tried running the emulator on both Mac and Windows, with the same results). I have access to all the same crc/checksum utilities you do, so it probably wouldn't hurt to get a SHA value or something. Though, as I said, all the other hard drive images work just fine, and I did re-download the disk (which of course makes the issues I'm having even weirder). If the checksums match, this might just be a lost cause.
 
Here's the various sums:

Code:
$ sum WD1002-0.U.cpm3
27525 10405
$ md5sum WD1002-0.U.cpm3
8a6751c38292bd404312dd50727ebd7e  WD1002-0.U.cpm3
$ sha1sum WD1002-0.U.cpm3
c91081222d44702b15699dbc24d5fab57c1c7dd2  WD1002-0.U.cpm3
$

I can't imagine why it's not working. Maybe post your config file (the actual contents), and I'll see if I can find something.
 
Here's the various sums:

Code:
$ sum WD1002-0.U.cpm3
27525 10405
$ md5sum WD1002-0.U.cpm3
8a6751c38292bd404312dd50727ebd7e  WD1002-0.U.cpm3
$ sha1sum WD1002-0.U.cpm3
c91081222d44702b15699dbc24d5fab57c1c7dd2  WD1002-0.U.cpm3
$

I can't imagine why it's not working. Maybe post your config file (the actual contents), and I'll see if I can find something.
Hi, Doug.

The sums all matched perfectly. Here is the content of my config file (which I'v also attached, adding a .txt extension to allow the upload):

kaypro_model = 10E
monitor_rom = 81-478a.rom

wd1002_drive1 = ST412
wd1002_disk1 = ~/Retro/kaypro/WD1002-1
floppy_drive1 = FDD_5_25_DS_ST

cpnetdevice_clientid=8
cpnetdevice_server00 = HostFileBdos

I'm confused about this, though. You say on the quickstart page I need to rename whatever disk image I'm using to "WD-1002-1", which I've done...but the sample files use the original disk image name. Which name is supposed to be in the config file, and do I need to put in the full path, though the disk is in the same folder as the config file and the emulator? I think a concrete example of what a working config file looks like might help. Sorry if I'm being obtuse.
 

Attachments

  • kaypro10e.cpnet.txt
    202 bytes · Views: 2
Doug, I found the problem. There was a typo in my HostFileBdos folder name! Talk about blind...it works now. Sorry for the drama!
 
Good news! Although, I'm concerned that a HostFileBdos typo would prevent the HDD from working. As a next step, I was going to ask to see the messages printed in the terminal window when you run the java command. Not sure if this problem would have been caught there or not.

Regarding the HDD image name, I think what I was targeting (at least originally) in the quick-start was to run without using a config file - in which case the HDD image needs to match the default. If you are using a config file - and customizing it - you can use whatever path and filename you want. Probably time to go back and re-read all that, and make improvements.
 
The typo wasn't so much in the path name as it was I missed creating the "a" folder beneath it.

That being said, I have some suggestions on your documentation, if you're open to them. And a few other questions about using top level folders...we can take them to email if you'd like (or leave them here or in a new forum post).
 
Back
Top