Welcome, Guest. Please login or register.

Author Topic: Unusual AmigaDOS error  (Read 1883 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline KarlosTopic starter

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16882
  • Country: gb
  • Thanked: 6 times
    • Show all replies
Unusual AmigaDOS error
« on: April 05, 2009, 03:33:47 PM »
I finally decided to boot one of the old 68K amiga systems I have lying around my place.

This one is a towered 1200 with Apollo 68040, Mediator1200 with Voodoo3000 PCI, 32MB RAM and a 20GB hard disk running OS3.9.

It hasn't been used in a long time. It booted fine, but I discovered that the last partition on the disk is allegedly validating. I say allegedly, since there's no observable disk activity.

Anyway, I changed the backdrop image to a plain colour and the machine spat out an error claiming an "Error 45" occurred with ENVARC:sys/wbpattern.prefs.

I went on to discover that pretty much any operation other than reading files from the hard disk results in the same error message.

I've never seen this one before. I thought most of the AmigaDOS error return codes were 2xx. Any ideas?
int p; // A
 

Offline KarlosTopic starter

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16882
  • Country: gb
  • Thanked: 6 times
    • Show all replies
Re: Unusual AmigaDOS error
« Reply #1 on: April 05, 2009, 11:00:19 PM »
I spotted this thread on another forum.

I wonder if it's scsi.device giving the error?

Quote
#define HFERR_BadStatus 45 /* status and/or sense error */


If so, it would be somewhat unusual since the machine used to work fine, it just hasn't been booted in a fairly long time.
int p; // A
 

Offline KarlosTopic starter

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16882
  • Country: gb
  • Thanked: 6 times
    • Show all replies
Re: Unusual AmigaDOS error
« Reply #2 on: April 06, 2009, 09:41:10 AM »
Well, initially only the topmost partition was invalidated. Now, all but the lowest are.

SYS: is currently on DH1 (DH0 has a lower boot priority atm), which is well under the 4G limit. According to info, it's Read/Write, but all partitions return Error 45 when attempting anything that would modify the contents.

There's not a lot of data on the drive. I think I might shove it into my old PC and recover the data with UAE and repartition it.
int p; // A