A600 with KS37.300 not being kind with new HDD

[cartmanau]

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

Only after it appears on the desktop.

[cartmanau]

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

Done that. Doesnt appear

- installing the correct filesystem in the RDB

Is this done in HDToolBox?

[Generale]

Hi there.
Here's my 2c worth. Just read this thread and it looks a little different from my less WB savvy perspective.
To me it looks like an electronic fault in the controller/cable. Simplest level, drive doesn't seem to be receiving a signal from the write pin..pin 23 i think. It's probably more complex, like a lightly fried chip, but it's worth checking components associated with R/W operations.

I'm unfamiliar with the internal workings of the amiga disk wrangling utilities, but usually fdisk style utils read the disk contents, work on the RAM copy and then when you are done, splat it to the drive. I'm not sure whether it checks.

Oh, is there corrupt data afterwards or no change?

There are also many other possibilities including databits or addressbits going missing. anyone ever had a disk write garbage, or just become a bit bucket for writes.
Theres all sorts of weird and wonderful combinations for problems.

So just eyeball it. Look for problems, especially corrosion in the connectors. Oh and any unusual heat dissipation.

[Jope]

cartmanau wrote:

- installing the correct filesystem in the RDB

Is this done in HDToolBox?

Yes..

And I said it a bit unclearly before:

Set your dostypes to normal FFS (DOS/1 or 0x444f5301) .. my sentence was a bit backwards.

[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.

[Generale]

@kronos
Why on earth were you using a connor? They are terrible!! I've got a few 'working' ones, which have major compatibility issues with everything, including using anything else on the same controller, use as a slave, autoconfiguration on IBM compatibles etc.
Anyway, I guess circumstance couldn't be helped.

[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 ....

[adonay]

LOL  :lol: sorry miss understod thx for the note .bahh i feel ashamed  :-D
a 40 !!!MB!!! get it sorry all for miss posting



 :lol:-> adonay <- :lol: all laugh :lol:

[cartmanau]

Generale wrote:
Hi there.
Here's my 2c worth. Just read this thread and it looks a little different from my less WB savvy perspective.
To me it looks like an electronic fault in the controller/cable. Simplest level, drive doesn't seem to be receiving a signal from the write pin..pin 23 i think. It's probably more complex, like a lightly fried chip, but it's worth checking components associated with R/W operations.

A less savvy perspective is always refreshing. I have only decided to revisit the world of the A600 after years of trouble free A1200 use. I have never had an Amiga as troublesome as this A600.

It is definantly reading and writing to the HDD, when I put it in the A1200 it is perfect. Just wont auto boot on the A600 (nor automount).

Oh, is there corrupt data afterwards or no change?

Data is perfect.

[cartmanau]

Jope wrote:
Yes..

And I said it a bit unclearly before:

Set your dostypes to normal FFS (DOS/1 or 0x444f5301) .. my sentence was a bit backwards.

I have tried it as a custom with 0x44f5301 as the type. On the next boot it appears in the boot menu, but after that it is gone again.

@Kronos
It is a 2.5" drive

[Doobrey]

cartmanau wrote:
I have tried it as a custom with 0x44f5301 as the type. On the next boot it appears in the boot menu, but after that it is gone again.

 Is that after a warm boot or a cold boot ?

If it`d only doing this on warm boots, and considering it`s an old drive, it might be the reset problem that plagued many Amiga users years ago. Cutting the wire that goes to pin #1 should stop it.

[cartmanau]

Doobrey wrote:

 Is that after a warm boot or a cold boot ?

If it`d only doing this on warm boots, and considering it`s an old drive, it might be the reset problem that plagued many Amiga users years ago. Cutting the wire that goes to pin #1 should stop it.

It will only appear in the boot menu after setting it up in HDToolBox with a warm reset.

[Generale]

So if I understand correctly the drive isn't detected after a cold boot but is after a warm boot?
Could have something to do with the delay time for detection used by the A600 coupled with a drive that is slow at getting its marbles together.
I've noticed that both aging WD and Connor drives can suffer from horrendously long startup times. The WD in this crudbucket PC doesn't always say 'Here!' before the rollcall is done so to speak, and misses out on being detected, until I do a warm reset. Cold reset doesn't always work for it.
Never had the problem with a Seagate or Maxtor though.

[Argus]

@Doobrey

I have a 540mb 2.5" drive from an IBM Thinkpad (DHAA-2540) that just won't work at all with 2.1 of an A600 nor with 3.0 of an A1200.  It will appear under HDToolbox and I can get it to set up partitions.  But then, upon warm reboot, no familiar icons for the partitions.  If I click on the HDSetup program, the icons for the partitions will suddenly appear.  I can then format these and install Workbench on the bootable system partition but after warm reboot nothing again.  Very frustrating indeed.  I've thought about cutting the first wire of the ide cable but never did because the cable cost more ($5.00) than the drive (free).

[Generale]

@Argus
Well, if the drive was free you could have just sn(i/a)pped off pin 1 from the drive connector itself.

[jahc]

You need kickstart 37.350 to use a hard drive on an Amiga 600! 37.000 wont do. The "A600HD" came with the 37.350 rom......

you've been wasting your time with this I think. sorry. :/