Prev: Western digital 250 gb drive no longer seen in windows, weird boot msg
Next: Acronis TI Home 11 - image corruption ?
From: Franc Zabkar on 17 Aug 2008 17:01
On Sat, 16 Aug 2008 21:05:41 -0700 (PDT), rahejasuresh(a)gmail.com put
finger to keyboard and composed:

>My 250 gb drive has died. Windows no longer sees it at all. During
>boot I hear 3 repeating beeps (long-short-long), prior to boot. It
>delays boot process by about a minute. Smart has been enabled now, but
>it finds nothing. Weirdest thing is that IDE detection no longer shows
>the drive model, but it now identifies the drive with the following
>identification string " WDC ROM MODEL-HAWK 0.2.01C03".
>
>Searched google, other people have seen it but no solution so far.
>Western digital website does not even list it.
>
>Any ideas?
>
>thanks
>
>Suresh

This person's solution was to replace the ROM chip at U12:

http://forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html
http://209.85.141.104/search?q=cache:b3mbxfUOivYJ:forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html+%22WDC+ROM+MODEL-HAWK%22&hl=en&ct=clnk&cd=5&client=opera

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.
From: Franc Zabkar on 17 Aug 2008 22:38
On Mon, 18 Aug 2008 07:01:55 +1000, Franc Zabkar
<fzabkar(a)iinternode.on.net> put finger to keyboard and composed:

>On Sat, 16 Aug 2008 21:05:41 -0700 (PDT), rahejasuresh(a)gmail.com put
>finger to keyboard and composed:
>
>>My 250 gb drive has died. Windows no longer sees it at all. During
>>boot I hear 3 repeating beeps (long-short-long), prior to boot. It
>>delays boot process by about a minute. Smart has been enabled now, but
>>it finds nothing. Weirdest thing is that IDE detection no longer shows
>>the drive model, but it now identifies the drive with the following
>>identification string " WDC ROM MODEL-HAWK 0.2.01C03".
>>
>>Searched google, other people have seen it but no solution so far.
>>Western digital website does not even list it.
>>
>>Any ideas?
>>
>>thanks
>>
>>Suresh
>
>This person's solution was to replace the ROM chip at U12:
>
>http://forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html
>http://209.85.141.104/search?q=cache:b3mbxfUOivYJ:forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html+%22WDC+ROM+MODEL-HAWK%22&hl=en&ct=clnk&cd=5&client=opera
>
>- Franc Zabkar

Looks like I misunderstood the fix. The problem is most likely some
other part, not U12. The site was down last time I looked, but now
that I can see the PCB, it looks like U12, the SDRAM (U3) and possibly
the uP (U5) were the only survivors. The OP obtained a replacement PCB
from a different model in the same series and got it to work by
swapping U12. I suspect that the code in U12 distinguishes the model.
It is probably responsible for the "WDC ROM MODEL-HAWK 0.2.01C03" ID
string.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.
From: Arno Wagner on 18 Aug 2008 11:13
Previously Franc Zabkar <fzabkar(a)iinternode.on.net> wrote:
> On Mon, 18 Aug 2008 07:01:55 +1000, Franc Zabkar
> <fzabkar(a)iinternode.on.net> put finger to keyboard and composed:

>>On Sat, 16 Aug 2008 21:05:41 -0700 (PDT), rahejasuresh(a)gmail.com put
>>finger to keyboard and composed:
>>
>>>My 250 gb drive has died. Windows no longer sees it at all. During
>>>boot I hear 3 repeating beeps (long-short-long), prior to boot. It
>>>delays boot process by about a minute. Smart has been enabled now, but
>>>it finds nothing. Weirdest thing is that IDE detection no longer shows
>>>the drive model, but it now identifies the drive with the following
>>>identification string " WDC ROM MODEL-HAWK 0.2.01C03".
>>>
>>>Searched google, other people have seen it but no solution so far.
>>>Western digital website does not even list it.
>>>
>>>Any ideas?
>>>
>>>thanks
>>>
>>>Suresh
>>
>>This person's solution was to replace the ROM chip at U12:
>>
>>http://forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html
>>http://209.85.141.104/search?q=cache:b3mbxfUOivYJ:forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html+%22WDC+ROM+MODEL-HAWK%22&hl=en&ct=clnk&cd=5&client=opera
>>
>>- Franc Zabkar

> Looks like I misunderstood the fix. The problem is most likely some
> other part, not U12. The site was down last time I looked, but now
> that I can see the PCB, it looks like U12, the SDRAM (U3) and possibly
> the uP (U5) were the only survivors. The OP obtained a replacement PCB
> from a different model in the same series and got it to work by
> swapping U12. I suspect that the code in U12 distinguishes the model.
> It is probably responsible for the "WDC ROM MODEL-HAWK 0.2.01C03" ID
> string.

If U12 is the ROM, then it holds the identity. While swapping
SMD chips is possible, it requires a lot of experience and SMD
soldering tools.

Arno

> - Franc Zabkar
> --
> Please remove one 'i' from my address when replying by email.
From: Squeeze on 18 Aug 2008 10:15
Franc Zabkar wrote in news:svnha41kb6e230iqo3bvjan4q9a98v4hkq(a)4ax.com
> On Mon, 18 Aug 2008 07:01:55 +1000, Franc Zabkar
> <fzabkar(a)iinternode.on.net> put finger to keyboard and composed:
>
> > On Sat, 16 Aug 2008 21:05:41 -0700 (PDT), rahejasuresh(a)gmail.com put
> > finger to keyboard and composed:
> >
> > > My 250 gb drive has died. Windows no longer sees it at all. During
> > > boot I hear 3 repeating beeps (long-short-long), prior to boot. It
> > > delays boot process by about a minute. Smart has been enabled now, but
> > > it finds nothing. Weirdest thing is that IDE detection no longer shows
> > > the drive model, but it now identifies the drive with the following
> > > identification string " WDC ROM MODEL-HAWK 0.2.01C03".
> > >
> > > Searched google, other people have seen it but no solution so far.
> > > Western digital website does not even list it.
> > >
> > > Any ideas?
> > >
> > > thanks
> > >
> > > Suresh
> >
> > This person's solution was to replace the ROM chip at U12:
> >
> > http://forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html
> >
http://209.85.141.104/search?q=cache:b3mbxfUOivYJ:forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html+%22WDC+ROM+MODEL-HAWK%22&hl=en&ct=clnk&cd=5&client=opera
> >
> > - Franc Zabkar

> Looks like I misunderstood the fix.

Yes Franc, that can happen when you are aspiring to become the new Babblebot.

> The problem is most likely some
> other part, not U12. The site was down last time I looked, but now
> that I can see the PCB, it looks like U12, the SDRAM (U3) and possibly
> the uP (U5) were the only survivors. The OP obtained a replacement PCB
> from a different model in the same series and got it to work by
> swapping U12.

> *I suspect* that the code in U12 distinguishes the model.

> *It is probably* responsible for the "WDC ROM MODEL-HAWK 0.2.01C03" ID
> string.

In other words, you don't have the nearest clue, have you, Franc.

>
> - Franc Zabkar

From: Squeeze on 18 Aug 2008 15:57
Arno Wagner wrote in news:6gthscFhco4gU1(a)mid.individual.net
> Previously Franc Zabkar <fzabkar(a)iinternode.on.net> wrote:
> > On Mon, 18 Aug 2008 07:01:55 +1000, Franc Zabkar
> > <fzabkar(a)iinternode.on.net> put finger to keyboard and composed:
>
> > > On Sat, 16 Aug 2008 21:05:41 -0700 (PDT), rahejasuresh(a)gmail.com put
> > > finger to keyboard and composed:
> > >
> > > > My 250 gb drive has died. Windows no longer sees it at all. During
> > > > boot I hear 3 repeating beeps (long-short-long), prior to boot. It
> > > > delays boot process by about a minute. Smart has been enabled now, but
> > > > it finds nothing. Weirdest thing is that IDE detection no longer shows
> > > > the drive model, but it now identifies the drive with the following
> > > > identification string " WDC ROM MODEL-HAWK 0.2.01C03".
> > > >
> > > > Searched google, other people have seen it but no solution so far.
> > > > Western digital website does not even list it.
> > > >
> > > > Any ideas?
> > > >
> > > > thanks
> > > >
> > > > Suresh
> > >
> > > This person's solution was to replace the ROM chip at U12:
> > >
> > >
http://forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html
> > >
http://209.85.141.104/search?q=cache:b3mbxfUOivYJ:forum.hddguru.com/hard-disk-drives-repair-and-data-recovery-f1/ready-to-recover-data-wd1600js-photo-of-damage-t9234.html+%22WDC+ROM+MODEL-HAWK%22&hl=en&ct=clnk&cd=5&client=opera
> > >
> > > - Franc Zabkar
>
> > Looks like I misunderstood the fix. The problem is most likely some
> > other part, not U12. The site was down last time I looked, but now
> > that I can see the PCB, it looks like U12, the SDRAM (U3) and possibly
> > the uP (U5) were the only survivors. The OP obtained a replacement PCB
> > from a different model in the same series and got it to work by
> > swapping U12. I suspect that the code in U12 distinguishes the model.
> > It is probably responsible for the "WDC ROM MODEL-HAWK 0.2.01C03" ID
> > string.
>

> *If *

Another freakin' expert.

> U12 is the ROM, then it holds the identity.

And if not, Babblebot?

> While swapping
> SMD chips is possible, it requires a lot of experience and SMD
> soldering tools.
>
> Arno
>
> > - Franc Zabkar
> > --
> > Please remove one 'i' from my address when replying by email.

 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Western digital 250 gb drive no longer seen in windows, weird boot msg
Next: Acronis TI Home 11 - image corruption ?