I've been playing with ZuluScsi on my old Arc machines and when my old cdrom on a RiscPC died I thought I'd go all scsi on that machine. Using real discs has proved to be a nightmare on a Cumana SCSI-2 16/32bit card. The only spare scsi drives I have are scsi-3 ultra 160/320 and the Cumana is not happy with them though the discs checkout fine on a PC.
Anyway, to the point of my post.
With an unconfigured machine and just a single IDE drive connected (but IDEDiscs 0) it takes 15 seconds before the screen displays the initial RISC OS and RAM messages and beeps. A further second or two into the desktop. The 15 seconds to beep seems a lot to me, but it gets worse.
Disconnect the IDE disc completely and it's 45 seconds to display initial message and beep. Into the desktop a second later. What's the machine looking for? IDEDiscs is 0.
Add a correctly configured Cumana podule and its 49 seconds from boot until the Cumana displays it's messages and a further 63 seconds before the RISC OS/RAM messages. Desktop is then entered after a further second.
Leaving the Cumana connected and reconnecting the IDE drive (still unconfigured) brings the delay back to 15 seconds or so before the Cumana messages appear and the RISC OS/RAM messages follow immediately.
I don't remember these kind of delays but I've never had zero IDE devices attached before.
Any thoughts? Why does disconnecting the IDE disc cause such delays?
Anyway, to the point of my post.
With an unconfigured machine and just a single IDE drive connected (but IDEDiscs 0) it takes 15 seconds before the screen displays the initial RISC OS and RAM messages and beeps. A further second or two into the desktop. The 15 seconds to beep seems a lot to me, but it gets worse.
Disconnect the IDE disc completely and it's 45 seconds to display initial message and beep. Into the desktop a second later. What's the machine looking for? IDEDiscs is 0.
Add a correctly configured Cumana podule and its 49 seconds from boot until the Cumana displays it's messages and a further 63 seconds before the RISC OS/RAM messages. Desktop is then entered after a further second.
Leaving the Cumana connected and reconnecting the IDE drive (still unconfigured) brings the delay back to 15 seconds or so before the Cumana messages appear and the RISC OS/RAM messages follow immediately.
I don't remember these kind of delays but I've never had zero IDE devices attached before.
Any thoughts? Why does disconnecting the IDE disc cause such delays?
Statistics: Posted by Sniffer — Sun Dec 22, 2024 1:12 pm