Path: csiph.com!news.swapon.de!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Chris Newman Newsgroups: comp.sys.acorn.hardware Subject: Re: Disc Error ??? Date: Thu, 16 May 2024 22:42:00 +0100 Organization: None Lines: 42 Message-ID: <5b62227ff8mec@npost.uk> References: <5b59662272mec@npost.uk> Injection-Date: Thu, 16 May 2024 23:42:09 +0200 (CEST) Injection-Info: dont-email.me; posting-host="04251c84f3777f6e87f7c727d567462d"; logging-data="1877223"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18OgvWDTOu8gWSLBX6QCvpqoUVthhGgows=" User-Agent: Pluto/3.20 (RISC OS/5.29) NewsHound/v1.54 Cancel-Lock: sha1:4h5nB3CbXzz7ZhJB2H8iOi2g+rA= Xref: csiph.com comp.sys.acorn.hardware:7601 In article <5b59662272mec@npost.uk>, Chris Newman wrote: > Hi, > Every now and again I fire up the Risc PC to use the old scanner or to > run Sibelius. > On Saturday it didn't start up properly. > After an aeon it eventually got the the green screen with the boot > choices and an error box. > Disc error 21 at :4/00 000 000 000 000 6 > The m/c has a Simtec unipod. It should boot from h-4 (Spinning rust). > h-6 is an ssd for backup. > I eventually got to the desktop. Problem solved. By resetting lots of parameters I got it to the stage where it would boot properly from the green screen with the list of startup options by choosing IDEFS drive 4. I took the RiscPC to our local RiscOS group at Southampton where Andrew Conroy went throught it with a fine tooth comb. He surmised (correctly) that because I only used the machine sporadically, it hadn't been on for enough time to recharge the CMOS battery so was losing its settings. Andrew suggested a straight run of 8 hours per week should keep the battery healthy. He then checked for unplugged modules. None were unplugged. That triggered my little grey cells. In the dim and distant past when I set up the Unipod, I remember the Simtec instruction that if you put the CD Rom drive on the unipod instead of the motherboard, you had to unplug softATAPI. Having lost the CMOS settings it had reverted to the default setting of plugged in. ATAPI unplugged, machine back to normal. All now fine. -- Chris