RISC OS Open: Forum: Disc error 21 after rom upgrade

Nov 26, 2013 9:30pm

Bob (2194) 6 posts

Hello,
I wonder if anyone else has had this problem after installing the 5.20 ROMS on a RISC PC 600. The machine was working fine before the upgrade but afterwards I couldn’t access the drive and get the above error on startup.
The machine has a Cumana CD ROM connected via an interface card, which also worked prior to the upgrade – could this be the cause of the problem?

Thanks for any pointers.

Regards
Bob

Nov 26, 2013 10:33pm

Dave Higton (1515) 3534 posts

If you’ve installed physical ROMs, the usual problem is that the drive cable is not back correctly.

Nov 27, 2013 7:17am

Bob (2194) 6 posts

Thanks Dave, the cable is OK though.

Nov 27, 2013 8:15am

Dave Higton (1515) 3534 posts

You’re absolutely sure that one or the other end hasn’t been inserted 180 degrees from the correct orientation?

Nov 27, 2013 9:39am

Ronald May (387) 407 posts

I think the special interface card might have had a driver, if that is the case, it might not be 32bit and might not work anyway.
Somebody will know for sure, I only used one for a short time before going to true IDE CDDrive.

Nov 27, 2013 12:37pm

Bob (2194) 6 posts

Thanks to everyone who responded, I’ve solved the problem now – amazing what a good nights sleep can do!

If anyone is interested these were the steps that I took:-

1. Remove Cumana disc drive and interface board – I’m pretty sure now that this was the cause of the error.
2. Put new CDROM into the machine and make it a Slave on the IDE cable. I’m currently using a SeagateST34311A (4.3GB) which is set as the Master on the IDE cable.
3. Replace the 3.5 ROMs with the 5.20 ones.
4. Power up and the machine comes up in CLI mode reporting and error (apologies forgot to write it down).
5. Type Desktop at the prompt and note that the CDROM is now available.
6. Use !HForm to format the drive and note that the defaults all match the values that I read off the hard disc label.
7. Run !IOMD520 and wait for everything to be copied.
8. Reboot and it now works perfectly!

Next job is to get the DDE tools onto the machine and have some fun!

Thanks again
Regards
Bob

Nov 27, 2013 7:03pm

Steve Pampling (1551) 8172 posts

1. Remove Cumana disc drive and interface board – I’m pretty sure now that this was the cause of the error.
2. Put new CDROM into the machine and make it a Slave on the IDE cable. I’m currently using a SeagateST34311A (4.3GB) which is set as the Master on the IDE cable.

Hmmm, casting my memory back to pre-StrongARM days and the change to SA, then RO4.02, that sounds like the hardware change required for one bit of that sequence¹. If it is that then you could have broken things in the same fashion without RO5.xx

¹ I think it was 3.50 to 3.70

Disc error 21 after rom upgrade

Reply

Search forums

Social

ROOL Store

Donate! Why?

RISC OS IPR

Description

Voices

Options

Nov 26, 2013 9:30pm Bob (2194) 6 posts	Hello, I wonder if anyone else has had this problem after installing the 5.20 ROMS on a RISC PC 600. The machine was working fine before the upgrade but afterwards I couldn’t access the drive and get the above error on startup. The machine has a Cumana CD ROM connected via an interface card, which also worked prior to the upgrade – could this be the cause of the problem? Thanks for any pointers. Regards Bob

Nov 26, 2013 10:33pm Dave Higton (1515) 3534 posts	If you’ve installed physical ROMs, the usual problem is that the drive cable is not back correctly.

Nov 27, 2013 7:17am Bob (2194) 6 posts	Thanks Dave, the cable is OK though.

Nov 27, 2013 8:15am Dave Higton (1515) 3534 posts	You’re absolutely sure that one or the other end hasn’t been inserted 180 degrees from the correct orientation?

Nov 27, 2013 9:39am Ronald May (387) 407 posts	I think the special interface card might have had a driver, if that is the case, it might not be 32bit and might not work anyway. Somebody will know for sure, I only used one for a short time before going to true IDE CDDrive.

Nov 27, 2013 12:37pm Bob (2194) 6 posts	Thanks to everyone who responded, I’ve solved the problem now – amazing what a good nights sleep can do! If anyone is interested these were the steps that I took:- 1. Remove Cumana disc drive and interface board – I’m pretty sure now that this was the cause of the error. 2. Put new CDROM into the machine and make it a Slave on the IDE cable. I’m currently using a SeagateST34311A (4.3GB) which is set as the Master on the IDE cable. 3. Replace the 3.5 ROMs with the 5.20 ones. 4. Power up and the machine comes up in CLI mode reporting and error (apologies forgot to write it down). 5. Type Desktop at the prompt and note that the CDROM is now available. 6. Use !HForm to format the drive and note that the defaults all match the values that I read off the hard disc label. 7. Run !IOMD520 and wait for everything to be copied. 8. Reboot and it now works perfectly! Next job is to get the DDE tools onto the machine and have some fun! Thanks again Regards Bob

Nov 27, 2013 7:03pm Steve Pampling (1551) 8172 posts	1. Remove Cumana disc drive and interface board – I’m pretty sure now that this was the cause of the error. 2. Put new CDROM into the machine and make it a Slave on the IDE cable. I’m currently using a SeagateST34311A (4.3GB) which is set as the Master on the IDE cable. Hmmm, casting my memory back to pre-StrongARM days and the change to SA, then RO4.02, that sounds like the hardware change required for one bit of that sequence¹. If it is that then you could have broken things in the same fashion without RO5.xx ¹ I think it was 3.50 to 3.70