A600 with KS37.300 not being kind with new HDD

[Kronos]

Question No.1 : is this a 2.5" or 3.5" disk ? And if it is the later, are your sure power is o.k. ?

The form-factor may seem to be irrelavant, it also gives a hint on the age of the drive.

Lots of drives from the early 90's had a lousy implementation of the "read layout from disk" feature as x86s of these days didn't use them. 3.5s are more likely to have these probs.

Back in the days I tried a 170MB Connor in my A1200 (3.0), which would work just fine for 5-10 boots, but would then come back as a predifened type with 20MB... ONLY way to fix that was to fdisk it on a PC  :-o Had to go back to the 60mb 2.5"  :-x  :-x

It sounds quite possible that 2.x has even more probs with interpreting such garbled layout-info than 3.1-ROMs.

[Kronos]

Cos my brother allready had a 340MB Seagate (which later ended in my A2000, but must have been sold to someone sometime later) when I sold him the 386-POS that the Connor came from ?

Cos the big problems with Connors only surfaced a year later ? Just like the Deathstar-fiasko surfaced after IBM had been the brand-of-choice for several years ?

Oh, and the 60MB that came with the A1200 was also a Connor ....