Welcome, Guest. Please login or register.

Author Topic: A600 with KS37.300 not being kind with new HDD  (Read 5192 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Generale

  • Full Member
  • ***
  • Join Date: Feb 2005
  • Posts: 233
    • Show all replies
    • http://members.dodo.com.au/~izabellion
Re: A600 with KS37.300 not being kind with new HDD
« on: February 22, 2005, 10:10:39 AM »
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.
A500 (salvo): 1Mb RAM (512k chip, 512k SlowFast)
1x880k Floppy Disk, 1xIBM 540Mb 3.5\\"HDD KS1.3, WB1.3
1084S monitor. AT Keyboard!
A500 (Whitey): 512k RAM, 1x880k Floppy Disk, KS1.2, WB1.3
 

Offline Generale

  • Full Member
  • ***
  • Join Date: Feb 2005
  • Posts: 233
    • Show all replies
    • http://members.dodo.com.au/~izabellion
Re: A600 with KS37.300 not being kind with new HDD
« Reply #1 on: February 22, 2005, 10:57:34 AM »
@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.
A500 (salvo): 1Mb RAM (512k chip, 512k SlowFast)
1x880k Floppy Disk, 1xIBM 540Mb 3.5\\"HDD KS1.3, WB1.3
1084S monitor. AT Keyboard!
A500 (Whitey): 512k RAM, 1x880k Floppy Disk, KS1.2, WB1.3
 

Offline Generale

  • Full Member
  • ***
  • Join Date: Feb 2005
  • Posts: 233
    • Show all replies
    • http://members.dodo.com.au/~izabellion
Re: A600 with KS37.300 not being kind with new HDD
« Reply #2 on: February 23, 2005, 01:23:40 AM »
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.
A500 (salvo): 1Mb RAM (512k chip, 512k SlowFast)
1x880k Floppy Disk, 1xIBM 540Mb 3.5\\"HDD KS1.3, WB1.3
1084S monitor. AT Keyboard!
A500 (Whitey): 512k RAM, 1x880k Floppy Disk, KS1.2, WB1.3
 

Offline Generale

  • Full Member
  • ***
  • Join Date: Feb 2005
  • Posts: 233
    • Show all replies
    • http://members.dodo.com.au/~izabellion
Re: A600 with KS37.300 not being kind with new HDD
« Reply #3 on: February 23, 2005, 03:46:34 AM »
@Argus
Well, if the drive was free you could have just sn(i/a)pped off pin 1 from the drive connector itself.
A500 (salvo): 1Mb RAM (512k chip, 512k SlowFast)
1x880k Floppy Disk, 1xIBM 540Mb 3.5\\"HDD KS1.3, WB1.3
1084S monitor. AT Keyboard!
A500 (Whitey): 512k RAM, 1x880k Floppy Disk, KS1.2, WB1.3