ULTRIX-32M V1.0 and microVAX II

[jmdhuse]

Try this in IMG.CFG:

# DEC RX50
[rx50::409600]
cyls = 80
heads = 1
secs = 10
interleave = 2
bps = 512
id = 1
rpm = 300
rate = 250
mode = mfm

Since there are other popular formats with the same size, the 'rx50' prefix requires that you name images in the form "<filename>.rx50.dsk" to avoid confusion. At least one of the conflicting formats is a built-in, which is likely to cause problems unless the tag name is used.

So, if you have an image file called "system_disk.dsk", rename it to "system_disk.rx50.dsk" when running on the Gotek. Then you'll be sure it's the definition above that gets used.

Thanks - I will give this a try.

 

[shirsch]

I believe it works happily, the trick is that with no image and the proper CFG settings it sees the drive "door" as "open".

Interesting. Would you mind sharing the CFG settings you're using? I did battle with the problem for almost a week - to not avail. On my system it just fails the floppy drives and pretends they're not there afterwards.

 

[jmdhuse]

Interesting. Would you mind sharing the CFG settings you're using? I did battle with the problem for almost a week - to not avail. On my system it just fails the floppy drives and pretends they're not there afterwards.

I have not been able to get this to work... The first GOTEK is correctly read when booting the boot1_3 installation disk, but the installation fails due to some error when it trys to access the boot2_3 disk in the second GOTEK.

 

[czunit]

Interesting. Would you mind sharing the CFG settings you're using? I did battle with the problem for almost a week - to not avail. On my system it just fails the floppy drives and pretends they're not there afterwards.

I'd have to put it together to check, but I did do a post on this for the Pro/380 and the RQDX3. Let me know if you can't find it and I'll fire things up this weekend.

 

[shirsch]

I'd have to put it together to check, but I did do a post on this for the Pro/380 and the RQDX3. Let me know if you can't find it and I'll fire things up this weekend.

To be clear, I have the FF Goteks working properly with the Pro/350 and have done installs from floppy images. The nagging problem is that I must have a non-bootable formatted image in the first drive. Unless the firmware sees that at boot it fails the floppy subsystem. Very odd that you are not seeing that. I believe I had the configuration as you described in the post.

 

[jmdhuse]

To be clear, I have the FF Goteks working properly with the Pro/350 and have done installs from floppy images. The nagging problem is that I must have a non-bootable formatted image in the first drive. Unless the firmware sees that at boot it fails the floppy subsystem. Very odd that you are not seeing that. I believe I had the configuration as you described in the post.

I don't know much about the Pro/350... what OS are you trying to boot? I also have a PDP-11/53 and I could try to validate the image you are trying to boot...

 

[shirsch]

This (mis)behavior is almost certainly taking place during the Pro/350 firmware initialization and self-test. Not likely to manifest on other platforms. The fix is to have a non-bootable RX50 image mounted on the first Gotek drive. With a real RX50, things are fine when it's empty. I spent weeks trying to quantify what was different between an empty RX50 drive and a Gotek with no image mounted. Never found the smoking gun.