A600 with KS37.300 not being kind with new HDD

[cartmanau]

I just put the 40 Mb (Seagate ST9051A) out of my dead A1200 in my A600. I loaded the computer using Install 2.1 and was surprised to not see the icons for the drive on workbench.

I opened HDTool, deleted the partitions, created new ones, saved to disk and restarted. Still no Hard disk.

I loaded HDTool and exited. The hard disk icons appeared on the desktop. I fomatted them and installed Workbench (or so I thought). At the end I pulled out the floppy - and restarted. It did nothing.

I then turned it off and back on, holding down both mouse buttons (for the boot menu). No sign of DH0 or DH1 there. I then pulled the HD out, put it in my other A1200 and partitioned it. Put it back in the A600, nothing.

I also borrowed a mate's WB 2.05, removed the RDB and partitioned and formatted. Still no go in the A600. It can see it after HDTool has touched it but it just will not auto mount :pissed:

The HDD will boot the A1200 but not the A600. WTF am I doing wrong?

[Daedalus]

I'm a little bit rusty at WB2.05 installs, but are you sure you have a filesystem that the 2.05 ROMs can understand installed on the drive? If you install it on an A1200 you'll get the 3.0 version of FFs installed, and it won't boot on the 600... Make absolutely sure you've got hte 2.05 version of FFS in L: on your boot floppy before you install it with HDToolbox...

Failing that (and I don't want to insult your intelligence here), but you did check the automount option in HDToolbox? It may or may not be stored differently between the WB2 and WB3 versions of HDToolbox, so checking it on the 1200 might not necessarily mean it'll automount under WB2...

[adonay]

What kind of ide controller have you got in the 600 and what ide software (scsi emulation modes etc ) and i dont think 2.1 supports 4Gb-> drives ..try wb 3.1 witch will need 3.1 rom (this dont count for 1200 witch can run 3.1 from 3.0 roms) if you dont have 3.1 rom in the 600 i think u have a problem whith large disks..


adonay :-)

[Trooper]

adonay wrote:
What kind of ide controller have you got in the 600 and what ide software (scsi emulation modes etc ) and i dont think 2.1 supports 4Gb-> drives ..try wb 3.1 witch will need 3.1 rom (this dont count for 1200 witch can run 3.1 from 3.0 roms) if you dont have 3.1 rom in the 600 i think u have a problem whith large disks..


adonay :-)

Sorry to be an ass, But if you re-read his post, He said he has a 40mb drive. Which i think is within the boundaries of the 4 gig barrier, But only just. :-D

Trooper

[Piru]

@Daedalus

I'm a little bit rusty at WB2.05 installs, but are you sure you have a filesystem that the 2.05 ROMs can understand installed on the drive? If you install it on an A1200 you'll get the 3.0 version of FFs installed, and it won't boot on the 600...

Actually, the only incompatible new feature in 3.0/3.1 is DirectoryCache (DC). Using 37.300 ROM FFS should be fine, assuming no DC is used.

Also to my knowlege all amiga fastfilesystems provided on disk (at least upto 3.0/3.1) are compiled for 68000 and KS V37++, except for one bug in the code: If requester would pop up, the filesystem crash on 2.x (iirc aminet has a patch for this particular bug).

Failing that (and I don't want to insult your intelligence here), but you did check the automount option in HDToolbox? It may or may not be stored differently between the WB2 and WB3 versions of HDToolbox

It's not. The automount has always been stored in the PART RDB block the same way.

@adonay

What kind of ide controller have you got in the 600

A600 has the built-in IDE controller, similar to A1200 one. It's quite likely he uses it.

and what ide software (scsi emulation modes etc )

It's the scsi.device in Kickstart ROM. SCSI emulations are irrelevant here, as the disk is only 40MB.

and i dont think 2.1 supports 4Gb-> drives

40MB < 4GB.

..try wb 3.1 witch will need 3.1 rom (this dont count for 1200 witch can run 3.1 from 3.0 roms) if you dont have 3.1 rom in the 600 i think u have a problem whith large disks..

2.05 (37.300) scsi.device indeed had some issues with large HDDs, however it should be fine upto 40MB.

It could be that KS 37.350 would still fix the problem (as it has some scsi.device fixes)... or maybe not. From this info it's pretty hard to speculate what the problem really is.

Kickstart 2.0x / Workbench 2.05 info

[Daedalus]

@Piru

Actually, the only incompatible new feature in 3.0/3.1 is DirectoryCache (DC). Using 37.300 ROM FFS should be fine, assuming no DC is used.

Wasn't even thinking on levels of Directory Cache since I've never used it on a HD, but what I mean is that if the drive was prepped with the 3.0 version of FFS that was on the 1200, but the filesystem wasn't actually installed in the RDB then the filesystem in 2.05 wouldn't recognise it. I've had problems along that line before, and my A600 has 37.350 ROMs. Choosing to update the version of FFS in HDToolbox should rectify this problem if that's the case, assuming he has the file system available on disk at all...

It's not. The automount has always been stored in the PART RDB block the same way.

Good to know, thanks :-)

I know I have a different version of the ROM in mine, but I had no problem installing and formatting a 1.4GB HD in my 600 using the WB2.05 floppies and RDBPrep (I think)...

[Piru]

@Daedalus

but what I mean is that if the drive was prepped with the 3.0 version of FFS that was on the 1200, but the filesystem wasn't actually installed in the RDB then the filesystem in 2.05 wouldn't recognise it.

IMO this shouldn't happen, KS 2.x ROM FFS should read the filesystem just fine. At least that is my experience.

However, putting the latest FFS (for the particular OS) to the HDD's RDB can't hurt...

[cartmanau]

Daedalus wrote:
I'm a little bit rusty at WB2.05 installs, but are you sure you have a filesystem that the 2.05 ROMs can understand installed on the drive? If you install it on an A1200 you'll get the 3.0 version of FFs installed, and it won't boot on the 600... Make absolutely sure you've got hte 2.05 version of FFS in L: on your boot floppy before you install it with HDToolbox...

I am using the disks on the A600 to set it up (2.05 and 2.1).

Failing that (and I don't want to insult your intelligence here), but you did check the automount option in HDToolbox? It may or may not be stored differently between the WB2 and WB3 versions of HDToolbox, so checking it on the 1200 might not necessarily mean it'll automount under WB2...

I have done this in the HDToolBox on WB2.

[cartmanau]

adonay wrote:
What kind of ide controller have you got in the 600 and what ide software (scsi emulation modes etc ) and i dont think 2.1 supports 4Gb-> drives ..try wb 3.1 witch will need 3.1 rom (this dont count for 1200 witch can run 3.1 from 3.0 roms) if you dont have 3.1 rom in the 600 i think u have a problem whith large disks..


adonay :-)

Standard A600 IDE, 40 MB drive.

[cartmanau]

IMO this shouldn't happen, KS 2.x ROM FFS should read the filesystem just fine. At least that is my experience.

However, putting the latest FFS (for the particular OS) to the HDD's RDB can't hurt...

How does one do that?

[orange]

Did that A600 ever work with any HDD?
I'd try PFS and different versions of HDToolbox(other programs). Maybe somethings wrong with its KS..  :inquisitive:

[whabang]

Type 'info' in the shell, and see if it appears there...

[Jope]

Also be sure to check by rebooting with both mouse buttons down that the partitions are visible in the early startup menu..

If not, then it can't be an automount bug either.

I remember having the same kind of problems with a 3.0 A4000 at some point in time, but I think those were solved by

- installing the correct filesystem in the RDB
- checking that the dostype of the partitions correspond to a findable filesystem

I was running PFS3 on the drive and it so happened that I had it in the RDB of my first drive, but not the second drive.. -> remove first drive, second one mysteriously broke

So also look to see that the dostype isn't plain vanilla FFS.

[cartmanau]

orange wrote:
Did that A600 ever work with any HDD?
I'd try PFS and different versions of HDToolbox(other programs). Maybe somethings wrong with its KS..  :inquisitive:

Never had a HDD the whole time I have had it, so I wouldnt know.

What is PFS? I have tried HDToolbox 1.3, 2.05, 2.1 and 3.1. 1.3 wont detect it, the rest do. I have tried a paritioner from Aminet (HDInst or something like that) as well as the 2.05 HDInstall script.

Frankly I am at a loss as to why it doesnt work.

[cartmanau]

whabang wrote:
Type 'info' in the shell, and see if it appears there...

Only after it appears on the desktop.