Re: Second Drive Not Recognized in Win98

[MEB[_2_]]

Hi Mike,

If you post this issue in microsoft.public.win98.gen_discussion you will
find more help. Let's see if a cross-post goes through, you'll need to pick
up that group if you aren't already pulling it [monitoring]

--
MEB
http://peoplescounsel.org
a Peoples' counsel
_ _
~~
"mikesmith" > wrote in message
...
|
|
| "philo" wrote:
|
| >
| > "Peggy A" > wrote in message
| > ...
| > > I am trying to help a friend get her data from an old hard drive after
her
| > > motherboard died. This drive is from a 6-7 year old Gateway PC and it
has
| > the
| > > older parallel connector, so I tried to add it as a second drive in an
| > older
| > > Dell Dimension XPS Pro PC running Windows 98 SE. I attached the second
| > drive
| > > as a slave and the BIOS recognizes it, but I cannot see it in Windows.
| > I've
| > > read other posts about needing to format the drive, but since this
drive
| > has
| > > data on it, I cannot reformat it. I also tried attaching it as the
| > primary
| > > and only drive, but the system wouldn't boot. I even applied an update
to
| > the
| > > BIOS thinking it may be a drive capacity issue since the second one is
a
| > 40
| > > GB drive. That didn't have any impact either.
| > >
| > > Is there a way to get Windows 98 to recognize this drive so I can copy
the
| > > data off of it for her? Any suggestions on the best way to get the
data
| > off
| > > her drive would be appreciated.
| > >
| > > Thanks.
| > >
| > >
| >
| > If the drive came from another win98 machine...it should be visible
| >
| > however if it came from a Win2k machine or an XP machine...the drive may
| > very well be formatted as NTFS
| > and not visible from win98 which cannot recognize NTFS
| >
| > http://en.wikipedia.org/wiki/NTFS
| >
| >
| > Im having sort of the same problem as philo
| My Operating System is Windows 98SE..
| Ok here goes...
| my computer motherboard *WAS*an ABIT KT7-RAID it died...
| when the computer was running i had 2 hard drives installed on it..
| 1 MASTER (Operating System 98SE* And Programs ONLY*)..
| 1 SLAVE (for Data Backup And Storage Only)
| both hard drives were on the *same IDE Cable*
| their pins were set on MASTER and SlAVE
| *Not* on cable select....
|
| the Master hard drive was a
| IBM DeskStar Hard Drive
| Model: DPTA-371360 (ATA)
| 13.6 GB 7200 RPM
| P/N 31L9151
|
| the Slave hard drive was a
| Quantum Fireball Hard Drive
| Quantum Fireball lct20
| Model ID: QML20000LD-A
| 20.4 GB 4500 RPM
| P/N 204531-001
|
| heres what happened
| well my motherboard died so i got another motherboard that would work with
| my parts off my old system..
| a friend gave me a striped Compaq computer (MotherBoard and Case Only)
| a *Compaq 5000US*
| besides no over clocking in the Bios on the Compaq like My KT-7 had it
works
| pretty good..
| i installed my processor (AMD Athlon 1200 - A1200AMS3B)
| and my Memory sticks...
| i installed My Windows 98SE Operating system On the IBM hard drive..
| *just like on My old system*
| Got it All running good...
| im using it right now typing this...
| its all running GREAT..
| HERES THE PROBLEM..
| then When i went to Put in My Quantum disk Drive with ALL my data on it
| on the same IDE cable as The IBM with my OS
| *just like i had set up in my old system*
| REMEMBER i have the Quantum Slaved ALL READY..i Didn't Change Anything
| Started up my System...
| i Got a ERROR...
| NO DISK FOUND
| my system wouldent boot up..
| i restarted and checked in my BIOS..
| both Hard Drives were listed in the Bios As they should be..right Size and
| all..
| restarted it again...nothing..same Error
| shut it all down...pulled out the Quantum Hard drive...
| it stared up fine..booted fine no problems..system running good
| so i thought id try putting the Quantum On the Second IDE cable...
| the system booted up then...BUT NO D: DRIVE was showing...just the C:
drive
| was showing up...
| pulled out the Quantum Again..put the Pin on the Quantum to Master..
| same thing the drive was NOT showing...only the C: drive showing
| restarted the computer again..
| looked in my Bios Again..there it was Again..but showing as a Master on
the
| Second IDE now...like it should..since i changed it to that...
| restarted my system...
| NO D: drive showing up..
| pulled out the Quantum...
| put back My DVD burner and DVD ROM back on to the Second IDE...
| they were working fine...so i know the Second IDE works
| PUT the Quantium back in...then *checked it in Fdisk*..
| it was showing up There...**BUT** the FAT wasent showing..it was showing
as
| UNKNOWN....Not FAT32 like it should be..the IBM was showing FAT32
| i thought what the hecks going on i didnt change anything on it...
| just pluged it in on my new system...
| then i tried checking it with the Quantium Disk tool in DOS..
| (Maxator Max Blaster 4.0 Partition tool)..
| it was showing up as FAT32 in the Quantum disk tool...like it should..
| i thought whats going on..one DOS tools showing it...ones not..
| what the hecks going on....im worried im going to loose all my data i
thought
| was safe due to being on a seperate hard drive disk..
| i didnt change anything on it just pluged it on to another Windows 98
system
| it should be working fine..
| i have done this before with other peoples system..pulled a hard drive
from
| one Windows 98 system..Slaved the Hard drive pin..
| Put it on to another windows 98 system and had it always showed and was
| always able to get data from them...
| whats up with this one???
| i am SOOO lost..
| why isen't the FAT32 showing in Fdisk now
| and *WHY IS IT*showing in the Quantium Disk tool for that type of hard
| drive...
| it was working fine before...
| all i did was take a SLAVED Hard drive DATA Disk that was working fine..
| and put it onto another system..
| why isen't it working now??
|
|
|
|
|
|
|
|
|

[Jeff Richards]

If you were using some disk management software for the Quantum drive when
it was a slave in the old machine, then that software is not running now and
the partitioning will not be recognised by Windows. That would produce the
symptoms you are seeing - the drive is recognised in BIOS and some
information can be accessed but it is inconsistent and not sufficient to
allow Windows (or DOS) to recognise it as properly partitioned or formatted.

This would be the case if the old BIOS was not capable of recognising the
full capacity of that drive and you had to use management software to make
it compatible, or if you originally configured the drive using the drive
manufacturer's configuration utility (whether it was really needed or not).

You can get a similar result if the logical block mapping is different
between the two BIOSes. Sometimes, manually configuring the BIOS settings
for the new machine can get you back to a compatible setting.

It's also possible that when the motherboard died it took the drive with it.
Run the manufacturer's diagnostics to confirm that the drive really is
working OK.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"MEB" <meb@not > wrote in message
...
> Hi Mike,
>
> If you post this issue in microsoft.public.win98.gen_discussion you will
> find more help. Let's see if a cross-post goes through, you'll need to
> pick
> up that group if you aren't already pulling it [monitoring]
>
> "mikesmith" > wrote in message
> ...
> |
> | snip | <
> | >
> | > Im having sort of the same problem as philo
> | My Operating System is Windows 98SE..
> | Ok here goes...
> | my computer motherboard *WAS*an ABIT KT7-RAID it died...
> | when the computer was running i had 2 hard drives installed on it..
> | 1 MASTER (Operating System 98SE* And Programs ONLY*)..
> | 1 SLAVE (for Data Backup And Storage Only)
> | both hard drives were on the *same IDE Cable*
> | their pins were set on MASTER and SlAVE
> | *Not* on cable select....
> |
> | the Master hard drive was a
> | IBM DeskStar Hard Drive
> | Model: DPTA-371360 (ATA)
> | 13.6 GB 7200 RPM
> | P/N 31L9151
> |
> | the Slave hard drive was a
> | Quantum Fireball Hard Drive
> | Quantum Fireball lct20
> | Model ID: QML20000LD-A
> | 20.4 GB 4500 RPM
> | P/N 204531-001
> |
> | heres what happened
> | well my motherboard died so i got another motherboard that would work
> with
> | my parts off my old system..
> | a friend gave me a striped Compaq computer (MotherBoard and Case Only)
> | a *Compaq 5000US*
> | besides no over clocking in the Bios on the Compaq like My KT-7 had it
> works
> | pretty good..
> | i installed my processor (AMD Athlon 1200 - A1200AMS3B)
> | and my Memory sticks...
> | i installed My Windows 98SE Operating system On the IBM hard drive..
> | *just like on My old system*
> | Got it All running good...
> | im using it right now typing this...
> | its all running GREAT..
> | HERES THE PROBLEM..
> | then When i went to Put in My Quantum disk Drive with ALL my data on it
> | on the same IDE cable as The IBM with my OS
> | *just like i had set up in my old system*
> | REMEMBER i have the Quantum Slaved ALL READY..i Didn't Change Anything
> | Started up my System...
> | i Got a ERROR...
> | NO DISK FOUND
> | my system wouldent boot up..
> | i restarted and checked in my BIOS..
> | both Hard Drives were listed in the Bios As they should be..right Size
> and
> | all..
> | restarted it again...nothing..same Error
> | shut it all down...pulled out the Quantum Hard drive...
> | it stared up fine..booted fine no problems..system running good
> | so i thought id try putting the Quantum On the Second IDE cable...
> | the system booted up then...BUT NO D: DRIVE was showing...just the C:
> drive
> | was showing up...
> | pulled out the Quantum Again..put the Pin on the Quantum to Master..
> | same thing the drive was NOT showing...only the C: drive showing
> | restarted the computer again..
> | looked in my Bios Again..there it was Again..but showing as a Master on
> the
> | Second IDE now...like it should..since i changed it to that...
> | restarted my system...
> | NO D: drive showing up..
> | pulled out the Quantum...
> | put back My DVD burner and DVD ROM back on to the Second IDE...
> | they were working fine...so i know the Second IDE works
> | PUT the Quantium back in...then *checked it in Fdisk*..
> | it was showing up There...**BUT** the FAT wasent showing..it was showing
> as
> | UNKNOWN....Not FAT32 like it should be..the IBM was showing FAT32
> | i thought what the hecks going on i didnt change anything on it...
> | just pluged it in on my new system...
> | then i tried checking it with the Quantium Disk tool in DOS..
> | (Maxator Max Blaster 4.0 Partition tool)..
> | it was showing up as FAT32 in the Quantum disk tool...like it should..
> | i thought whats going on..one DOS tools showing it...ones not..
> | what the hecks going on....im worried im going to loose all my data i
> thought
> | was safe due to being on a seperate hard drive disk..
> | i didnt change anything on it just pluged it on to another Windows 98
> system
> | it should be working fine..
> | i have done this before with other peoples system..pulled a hard drive
> from
> | one Windows 98 system..Slaved the Hard drive pin..
> | Put it on to another windows 98 system and had it always showed and was
> | always able to get data from them...
> | whats up with this one???
> | i am SOOO lost..
> | why isen't the FAT32 showing in Fdisk now
> | and *WHY IS IT*showing in the Quantium Disk tool for that type of hard
> | drive...
> | it was working fine before...
> | all i did was take a SLAVED Hard drive DATA Disk that was working fine..
> | and put it onto another system..
> | why isen't it working now??
> |

[mikesmith]

"Jeff Richards" wrote:
If you were using some disk management software for the Quantum drive when
it was a slave in the old machine, then that software is not running now and
the partitioning will not be recognised by Windows. That would produce the
symptoms you are seeing - the drive is recognised in BIOS and some
information can be accessed but it is inconsistent and not sufficient to
allow Windows (or DOS) to recognise it as properly partitioned or formatted.
This would be the case if the old BIOS was not capable of recognising the
full capacity of that drive and you had to use management software to make
it compatible, or if you originally configured the drive using the drive
manufacturer's configuration utility (whether it was really needed or not).

You can get a similar result if the logical block mapping is different
between the two BIOSes. Sometimes, manually configuring the BIOS settings
for the new machine can get you back to a compatible setting.

It's also possible that when the motherboard died it took the drive with it.
Run the manufacturer's diagnostics to confirm that the drive really is
working OK.

Jeff Richards
MS MVP (Windows - Shell/User)
"MEB" <meb@not > wrote in message
...

***
Hey jeff
thanks for answering my post
i don't know everything about computers..
but i may know a little bit more then some people...
please keep this in mind..

you wrote:
*If you were using some disk management software*

i wasent using any disk management software..
i dont think that is it...

you wrote:
*or if you originally configured the drive using the drive
manufacturer's configuration utility (whether it was really needed or not).*

this might be it Jeff..
not 100% really sure..
heres where things get a lil foggy..
(Due to building my old system about 5-6 years ago..)
i have never had to reinstall the operating system ever (98SE)..
it worked great from day 1 of me building it..
no problems ever..
can you believe that...
never having to re-install Windows

Anyways...
when i first built it ..
heres what i think i did when i went to install my second hard drive

*FIRST* i Low level formated the Hard drive with the Quantium tool (MAXTOR)
I KNOW FOR SURE I DID THAT...
then..
heres where the foggy part is, that im not really sure about..
i SWEAR this is what happened...
BUT NOT! 100% sure though..
(like i said this was 6 years ago...)

THEN i put in Fdisk and
partition the Hard Drive and formated it ..I KNOW I DID THIS

BUT!! then..i think..not 100% sure
then when i went to reboot my computer..
Windows didnt see the D: drive..
i was like what the hecks going on here!!...
so i put back in the Quantum tool..
and as soon as i did...it may have done something
and said something like..
not compatable with your current system you need to *SOMETHING*
i forget..
i think i just clicked OK..
and it did something..
then i rebooted..
and there was my D: drive..
all i remember was being happy..
because it was BIGGEST Hard Drive i EVER had and it was working..lol...
(ha ha 20 Gigs BIG!!... 6 years look how far we've come..anyways)
yeah in not really sure...
but im kinda thinking maybe thats what happened..

and now im worring that your going to say..
im going to loose all that data..
just because i may have
originally configured the drive using the drive manufacturer's configuration
utility

how can i check and see if i did do that???...can i?

then you wrote..
*You can get a similar result if the logical block mapping is different
between the two BIOSes. Sometimes, manually configuring the BIOS settings
for the new machine can get you back to a compatible setting.

im lost here..
i do know
that my bios in my Abit KT7 had WAY MORE options..
like i could set the paramaters manualy for the Hard drives..
cylinders..blocks...and stuff like that

and the new Compaq motherboard dosen't have nothing much in it..
only stuff like Enable Dissable UMDA...a few other things..
it doesen't even show much about the hard drives info..
just the name and size of the Hard drives that about it..
yeah the Compaq Bios is nothing compared to the Abits Bios..
the Compaq Bios is for pre-schoolers..
so i think that might not be a option to change much there..

so Jeff buddy what do you think?
what if i did do the configuration thing with the Quantum tool..
any thing?..
i still have the Quantum tool..
and there is some options in it..
but im not sure of what some of Options even do...
i dont want to do anything to loose this data..
like pick a option in the tool and have it make things worse then they are..
any more ideas or thoughts?
if not thanks so much for the information you gave me so far..
and if not..
yeah thanks so much for trying to help me..
yeah Jeff..thanks so much for your time buddy..
yeah thanks alout buddy
yeah your wicked cool for trying to even help..
thanks alot!!

[Jeff Richards]

It sure sounds like the drive was set up to be managed by the Quantum
software. At this stage, that's a better assumption than some difference in
the LBA (which is what could have happened as a result of needing to make
special settings in the original BIOS).

If you can find the Quantum software then have a good look through the
documentation to get an idea of what's needed to access that disk. The
process will involve installing the drive management software to the boot
disk (C in your case) WITHOUT going through the drive setup procedure for
the drive that is going to be managed - that is, without doing the
equivalent of FDISK on the second drive. You might even be able to do the
setup without having that drive connected to the machine, just to be safe.
It will probably complain about no having any drives that need to be
managed, but should still install. Once the software is running it only
interferes with those drives that require it. When you then reconnect the
old drive, it should then be recognised as a managed drive and should become
accessible.

So the important thing to keep in mind is that the software has two parts.
The disk preparation part for the drive to be managed, which has already
been done and you definitely do not want to repeat, and the management
software installation part (to the boot drive) which you do want to repeat.
The documentation for the software should cover that option.

It may be possible to use the Quantum software to prepare a boot floppy that
will give you DOS access to that drive. That will at least prove what the
problem is, and you could, if necessary, retrieve your data through DOS.

In the meantime, be very careful that you don't do anything that might write
to that old disk. In its current state it looks usable in some
circumstances, but if data gets written to the disk then it may be written
using different partitioning parameters to those it is actually set up with,
and the file system will be corrupted. Be particularly careful of anything
that wants to try and 'repair' the disk (as distinct from simply examining,
displaying or copying off the contents) as the repair could destroy all the
data.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"mikesmith" > wrote in message
...
>
> "Jeff Richards" wrote:
> If you were using some disk management software for the Quantum drive when
> it was a slave in the old machine, then that software is not running now
> and
> the partitioning will not be recognised by Windows. That would produce the
> symptoms you are seeing - the drive is recognised in BIOS and some
> information can be accessed but it is inconsistent and not sufficient to
> allow Windows (or DOS) to recognise it as properly partitioned or
> formatted.
> This would be the case if the old BIOS was not capable of recognising the
> full capacity of that drive and you had to use management software to make
> it compatible, or if you originally configured the drive using the drive
> manufacturer's configuration utility (whether it was really needed or
> not).
>
> You can get a similar result if the logical block mapping is different
> between the two BIOSes. Sometimes, manually configuring the BIOS settings
> for the new machine can get you back to a compatible setting.
>
> It's also possible that when the motherboard died it took the drive with
> it.
> Run the manufacturer's diagnostics to confirm that the drive really is
> working OK.
>
> Jeff Richards
> MS MVP (Windows - Shell/User)
> "MEB" <meb@not > wrote in message
> ...
>
> ***
> Hey jeff
> thanks for answering my post
> i don't know everything about computers..
> but i may know a little bit more then some people...
> please keep this in mind..
>
> you wrote:
> *If you were using some disk management software*
>
> i wasent using any disk management software..
> i dont think that is it...
>
> you wrote:
> *or if you originally configured the drive using the drive
> manufacturer's configuration utility (whether it was really needed or
> not).*
>
> this might be it Jeff..
> not 100% really sure..
> heres where things get a lil foggy..
> (Due to building my old system about 5-6 years ago..)
> i have never had to reinstall the operating system ever (98SE)..
> it worked great from day 1 of me building it..
> no problems ever..
> can you believe that...
> never having to re-install Windows
>
> Anyways...
> when i first built it ..
> heres what i think i did when i went to install my second hard drive
>
> *FIRST* i Low level formated the Hard drive with the Quantium tool
> (MAXTOR)
> I KNOW FOR SURE I DID THAT...
> then..
> heres where the foggy part is, that im not really sure about..
> i SWEAR this is what happened...
> BUT NOT! 100% sure though..
> (like i said this was 6 years ago...)
>
> THEN i put in Fdisk and
> partition the Hard Drive and formated it ..I KNOW I DID THIS
>
> BUT!! then..i think..not 100% sure
> then when i went to reboot my computer..
> Windows didnt see the D: drive..
> i was like what the hecks going on here!!...
> so i put back in the Quantum tool..
> and as soon as i did...it may have done something
> and said something like..
> not compatable with your current system you need to *SOMETHING*
> i forget..
> i think i just clicked OK..
> and it did something..
> then i rebooted..
> and there was my D: drive..
> all i remember was being happy..
> because it was BIGGEST Hard Drive i EVER had and it was working..lol...
> (ha ha 20 Gigs BIG!!... 6 years look how far we've come..anyways)
> yeah in not really sure...
> but im kinda thinking maybe thats what happened..
>
> and now im worring that your going to say..
> im going to loose all that data..
> just because i may have
> originally configured the drive using the drive manufacturer's
> configuration
> utility
>
> how can i check and see if i did do that???...can i?
>
> then you wrote..
> *You can get a similar result if the logical block mapping is different
> between the two BIOSes. Sometimes, manually configuring the BIOS settings
> for the new machine can get you back to a compatible setting.
>
> im lost here..
> i do know
> that my bios in my Abit KT7 had WAY MORE options..
> like i could set the paramaters manualy for the Hard drives..
> cylinders..blocks...and stuff like that
>
> and the new Compaq motherboard dosen't have nothing much in it..
> only stuff like Enable Dissable UMDA...a few other things..
> it doesen't even show much about the hard drives info..
> just the name and size of the Hard drives that about it..
> yeah the Compaq Bios is nothing compared to the Abits Bios..
> the Compaq Bios is for pre-schoolers..
> so i think that might not be a option to change much there..
>
> so Jeff buddy what do you think?
> what if i did do the configuration thing with the Quantum tool..
> any thing?..
> i still have the Quantum tool..
> and there is some options in it..
> but im not sure of what some of Options even do...
> i dont want to do anything to loose this data..
> like pick a option in the tool and have it make things worse then they
> are..
> any more ideas or thoughts?
> if not thanks so much for the information you gave me so far..
> and if not..
> yeah thanks so much for trying to help me..
> yeah Jeff..thanks so much for your time buddy..
> yeah thanks alout buddy
> yeah your wicked cool for trying to even help..
> thanks alot!!
>
>
>
>

[PCR]

Jeff Richards wrote:
| It sure sounds like the drive was set up to be managed by the Quantum
| software. At this stage, that's a better assumption than some
| difference in the LBA (which is what could have happened as a result
| of needing to make special settings in the original BIOS).
|
| If you can find the Quantum software then have a good look through the
| documentation to get an idea of what's needed to access that disk.
| The process will involve installing the drive management software to
| the boot disk (C in your case) WITHOUT going through the drive setup
| procedure for the drive that is going to be managed - that is,
| without doing the equivalent of FDISK on the second drive. You
| might even be able to do the setup without having that drive
| connected to the machine, just to be safe. It will probably complain
| about no having any drives that need to be managed, but should still
| install. Once the software is running it only interferes with those
| drives that require it. When you then reconnect the old drive, it
| should then be recognised as a managed drive and should become
| accessible.
|
| So the important thing to keep in mind is that the software has two
| parts. The disk preparation part for the drive to be managed, which
| has already been done and you definitely do not want to repeat, and
| the management software installation part (to the boot drive) which
| you do want to repeat. The documentation for the software should
| cover that option.
|
| It may be possible to use the Quantum software to prepare a boot
| floppy that will give you DOS access to that drive. That will at
| least prove what the problem is, and you could, if necessary,
| retrieve your data through DOS.
|
| In the meantime, be very careful that you don't do anything that
| might write to that old disk. In its current state it looks usable
| in some circumstances, but if data gets written to the disk then it
| may be written using different partitioning parameters to those it is
| actually set up with, and the file system will be corrupted. Be
| particularly careful of anything that wants to try and 'repair' the
| disk (as distinct from simply examining, displaying or copying off
| the contents) as the repair could destroy all the data.

Since mikesmith's new Compaq 5000US motherboard/BIOS sees the full 20
GBs of the Maxblast drive (as he reports & I've seen it in a NET ad),
isn't it worth a try to uninstall Maxbast? And I wonder whether MBRWork
could do that with its Option 8. If Option 8 doesn't show up, I wonder
whether this would do it...?...

http://www.terabyteunlimited.com/utilities.html MBRWork
Free MBR utility.

(a) Option 7 - Work with multiple hard drives.
Get to drive 1, the bad one.
(b) Option 1-- Backup the first track on a hard drive.
Makes a backup of the current MBR & EMBR.
Then, Option 2 can undo all of the following...
(c) Option 3 - Reset the EMBR area to all zeros.
A generally unused area between the MBR & end of first track,
but it can hold a drive overlay or 3rd party boot manager.
(d) Option 4 - Reset the MBR area to all zeros.
This wipes the MBR table holding the dimensions of all partitions
on that drive, if more than one. But it leaves all other drives
intact.
(e) Select option A to recover partition(s).
This generates partition dimensions into the MBR,
getting them somehow from the partition data area itself.
Sounds like it ONLY will work, IF the MBR has been mussed,
& everything else is fine.
(f) Option 5 - Install standard MBR Code
This will put boot code into the MBR.

........Quote MBRWork Readme .......
MBRWork - Freeware utility to perform some common and uncommon MBR
and disk functions. Provided As-Is.

It can perform the following:

1 - Backup the first track on a hard drive.
2 - Restore the backup file.
3 - Reset the EMBR area to all zeros.
4 - Reset the MBR are to all zeros.
5 - Install standard MBR Code
6 - Set a partition active (avail on the command line too)
7 - Work with multiple hard drives.
8 - Remove EZ-Drive (You must boot directly to a diskette [bypassing
ez-drive] for this option to show)
9 - Edit MBR partition entry values.
A - If no partitions exist in the MBR and no EMBR exists then this
option will allow you to recover lost FAT, HPFS, NTFS, and
Extended partitions.
C - Capture up to 64 disk sectors to a file.
R - Restore up to 64 disk sectors from a file. This feature should only
be used by those who completely understand what they are doing!
T - Transfer/Copy sectors from disk to disk. This feature should only
be used by those who completely understand what they are doing!
P - Compare sectors.
......EOQ... MBRWork Readme .............

| --
| Jeff Richards
| MS MVP (Windows - Shell/User)
| "mikesmith" > wrote in message
| ...
|>
|> "Jeff Richards" wrote:
|> If you were using some disk management software for the Quantum
|> drive when it was a slave in the old machine, then that software is
|> not running now and
|> the partitioning will not be recognised by Windows. That would
|> produce the symptoms you are seeing - the drive is recognised in
|> BIOS and some information can be accessed but it is inconsistent and
|> not sufficient to allow Windows (or DOS) to recognise it as properly
|> partitioned or formatted.
|> This would be the case if the old BIOS was not capable of
|> recognising the full capacity of that drive and you had to use
|> management software to make it compatible, or if you originally
|> configured the drive using the drive manufacturer's configuration
|> utility (whether it was really needed or not).
|>
|> You can get a similar result if the logical block mapping is
|> different between the two BIOSes. Sometimes, manually configuring
|> the BIOS settings for the new machine can get you back to a
|> compatible setting.
|>
|> It's also possible that when the motherboard died it took the drive
|> with it.
|> Run the manufacturer's diagnostics to confirm that the drive really
|> is working OK.
|>
|> Jeff Richards
|> MS MVP (Windows - Shell/User)
|> "MEB" <meb@not > wrote in message
|> ...
|>
|> ***
|> Hey jeff
|> thanks for answering my post
|> i don't know everything about computers..
|> but i may know a little bit more then some people...
|> please keep this in mind..
|>
|> you wrote:
|> *If you were using some disk management software*
|>
|> i wasent using any disk management software..
|> i dont think that is it...
|>
|> you wrote:
|> *or if you originally configured the drive using the drive
|> manufacturer's configuration utility (whether it was really needed or
|> not).*
|>
|> this might be it Jeff..
|> not 100% really sure..
|> heres where things get a lil foggy..
|> (Due to building my old system about 5-6 years ago..)
|> i have never had to reinstall the operating system ever (98SE)..
|> it worked great from day 1 of me building it..
|> no problems ever..
|> can you believe that...
|> never having to re-install Windows
|>
|> Anyways...
|> when i first built it ..
|> heres what i think i did when i went to install my second hard drive
|>
|> *FIRST* i Low level formated the Hard drive with the Quantium tool
|> (MAXTOR)
|> I KNOW FOR SURE I DID THAT...
|> then..
|> heres where the foggy part is, that im not really sure about..
|> i SWEAR this is what happened...
|> BUT NOT! 100% sure though..
|> (like i said this was 6 years ago...)
|>
|> THEN i put in Fdisk and
|> partition the Hard Drive and formated it ..I KNOW I DID THIS
|>
|> BUT!! then..i think..not 100% sure
|> then when i went to reboot my computer..
|> Windows didnt see the D: drive..
|> i was like what the hecks going on here!!...
|> so i put back in the Quantum tool..
|> and as soon as i did...it may have done something
|> and said something like..
|> not compatable with your current system you need to *SOMETHING*
|> i forget..
|> i think i just clicked OK..
|> and it did something..
|> then i rebooted..
|> and there was my D: drive..
|> all i remember was being happy..
|> because it was BIGGEST Hard Drive i EVER had and it was
|> working..lol... (ha ha 20 Gigs BIG!!... 6 years look how far we've
|> come..anyways)
|> yeah in not really sure...
|> but im kinda thinking maybe thats what happened..
|>
|> and now im worring that your going to say..
|> im going to loose all that data..
|> just because i may have
|> originally configured the drive using the drive manufacturer's
|> configuration
|> utility
|>
|> how can i check and see if i did do that???...can i?
|>
|> then you wrote..
|> *You can get a similar result if the logical block mapping is
|> different between the two BIOSes. Sometimes, manually configuring
|> the BIOS settings for the new machine can get you back to a
|> compatible setting.
|>
|> im lost here..
|> i do know
|> that my bios in my Abit KT7 had WAY MORE options..
|> like i could set the paramaters manualy for the Hard drives..
|> cylinders..blocks...and stuff like that
|>
|> and the new Compaq motherboard dosen't have nothing much in it..
|> only stuff like Enable Dissable UMDA...a few other things..
|> it doesen't even show much about the hard drives info..
|> just the name and size of the Hard drives that about it..
|> yeah the Compaq Bios is nothing compared to the Abits Bios..
|> the Compaq Bios is for pre-schoolers..
|> so i think that might not be a option to change much there..
|>
|> so Jeff buddy what do you think?
|> what if i did do the configuration thing with the Quantum tool..
|> any thing?..
|> i still have the Quantum tool..
|> and there is some options in it..
|> but im not sure of what some of Options even do...
|> i dont want to do anything to loose this data..
|> like pick a option in the tool and have it make things worse then
|> they are..
|> any more ideas or thoughts?
|> if not thanks so much for the information you gave me so far..
|> and if not..
|> yeah thanks so much for trying to help me..
|> yeah Jeff..thanks so much for your time buddy..
|> yeah thanks alout buddy
|> yeah your wicked cool for trying to even help..
|> thanks alot!!

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

[Jeff Richards]

I have not used the process you describe, but I think it is unlikely to
work. The point of the Quantum software is to map the disk sectors to
hardware parameters that the BIOS can understand. Simply rewriting the MBR
without that particular mapping in place could write the MBR to the 'wrong'
physical location, possibly overwriting data such as FAT. Then again, it may
not, as the MBR location is often the same between the mapped and unmapped
states. That may be why the drive appears to be partially accessible (and
why I was careful to warn against allowing anything to write to it). But
when it's accessed by the OS, if the correct mapping is not happening then
the FAT will not make sense (even if it hasn't been corrupted) as the
logical sector numbers used in the FAT will map to different physical
locations (and also presumably won't match the partition information).

The Quantum software might have a facility for undoing the mapping - that
is, physically re-arranging the data in the sectors to match the default
hardware characteristics - but in my experience it is easier to copy off the
data and rebuild the drive from scratch. Note that I was careful not to call
this 'uninstalling' - the management software is not currently installed,
and my guess is that's the problem. What we are trying to achieve is to
undo the special sector numbering arrangement of that drive. It's not just
terminology - it's an important distinction because there is a significant
amount of complex data shuffling needed.

Also, we have to first confirm that this is actually the problem.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"PCR" > wrote in message
...
> Jeff Richards wrote:
> | It sure sounds like the drive was set up to be managed by the Quantum
> | software. At this stage, that's a better assumption than some
> | difference in the LBA (which is what could have happened as a result
> | of needing to make special settings in the original BIOS).
> |
> | If you can find the Quantum software then have a good look through the
> | documentation to get an idea of what's needed to access that disk.
> | The process will involve installing the drive management software to
> | the boot disk (C in your case) WITHOUT going through the drive setup
> | procedure for the drive that is going to be managed - that is,
> | without doing the equivalent of FDISK on the second drive. You
> | might even be able to do the setup without having that drive
> | connected to the machine, just to be safe. It will probably complain
> | about no having any drives that need to be managed, but should still
> | install. Once the software is running it only interferes with those
> | drives that require it. When you then reconnect the old drive, it
> | should then be recognised as a managed drive and should become
> | accessible.
> |
> | So the important thing to keep in mind is that the software has two
> | parts. The disk preparation part for the drive to be managed, which
> | has already been done and you definitely do not want to repeat, and
> | the management software installation part (to the boot drive) which
> | you do want to repeat. The documentation for the software should
> | cover that option.
> |
> | It may be possible to use the Quantum software to prepare a boot
> | floppy that will give you DOS access to that drive. That will at
> | least prove what the problem is, and you could, if necessary,
> | retrieve your data through DOS.
> |
> | In the meantime, be very careful that you don't do anything that
> | might write to that old disk. In its current state it looks usable
> | in some circumstances, but if data gets written to the disk then it
> | may be written using different partitioning parameters to those it is
> | actually set up with, and the file system will be corrupted. Be
> | particularly careful of anything that wants to try and 'repair' the
> | disk (as distinct from simply examining, displaying or copying off
> | the contents) as the repair could destroy all the data.
>
> Since mikesmith's new Compaq 5000US motherboard/BIOS sees the full 20
> GBs of the Maxblast drive (as he reports & I've seen it in a NET ad),
> isn't it worth a try to uninstall Maxbast? And I wonder whether MBRWork
> could do that with its Option 8. If Option 8 doesn't show up, I wonder
> whether this would do it...?...
>
> http://www.terabyteunlimited.com/utilities.html MBRWork
> Free MBR utility.
>
> (a) Option 7 - Work with multiple hard drives.
> Get to drive 1, the bad one.
> (b) Option 1-- Backup the first track on a hard drive.
> Makes a backup of the current MBR & EMBR.
> Then, Option 2 can undo all of the following...
> (c) Option 3 - Reset the EMBR area to all zeros.
> A generally unused area between the MBR & end of first track,
> but it can hold a drive overlay or 3rd party boot manager.
> (d) Option 4 - Reset the MBR area to all zeros.
> This wipes the MBR table holding the dimensions of all partitions
> on that drive, if more than one. But it leaves all other drives
> intact.
> (e) Select option A to recover partition(s).
> This generates partition dimensions into the MBR,
> getting them somehow from the partition data area itself.
> Sounds like it ONLY will work, IF the MBR has been mussed,
> & everything else is fine.
> (f) Option 5 - Install standard MBR Code
> This will put boot code into the MBR.
>
> .......Quote MBRWork Readme .......
> MBRWork - Freeware utility to perform some common and uncommon MBR
> and disk functions. Provided As-Is.
>
> It can perform the following:
>
> 1 - Backup the first track on a hard drive.
> 2 - Restore the backup file.
> 3 - Reset the EMBR area to all zeros.
> 4 - Reset the MBR are to all zeros.
> 5 - Install standard MBR Code
> 6 - Set a partition active (avail on the command line too)
> 7 - Work with multiple hard drives.
> 8 - Remove EZ-Drive (You must boot directly to a diskette [bypassing
> ez-drive] for this option to show)
> 9 - Edit MBR partition entry values.
> A - If no partitions exist in the MBR and no EMBR exists then this
> option will allow you to recover lost FAT, HPFS, NTFS, and
> Extended partitions.
> C - Capture up to 64 disk sectors to a file.
> R - Restore up to 64 disk sectors from a file. This feature should only
> be used by those who completely understand what they are doing!
> T - Transfer/Copy sectors from disk to disk. This feature should only
> be used by those who completely understand what they are doing!
> P - Compare sectors.
> .....EOQ... MBRWork Readme .............
>

[PCR]

Jeff Richards wrote:
| I have not used the process you describe, but I think it is unlikely
| to work.

Yea, I haven't used it either. And I haven't yet found an instance of
anyone having used it for this purpose (but I'm sure some must exist
somewhere). And I'd hate to see mikesmith waste his Quantum Fireball.

BUT Terabyte has deemed it possible to put an Option 8 into MBRWork (a
little 26KB program), & Terabyte usually is quite good. Therefore, it
must be possible to do it-- but what really needs to be done?

Is it as you fear that something unusal has been done to the structure
of the partition (maybe the FAT tables)? Or can it be all is well with
that-- & only the MBR has been altered? Then, into the MBR boot code was
inserted a call to the Quantum DDO that kind of supplements BIOS to
understand LBA. The MBR table (& the FAT tables) could be a normal one
that includes LBA information. However, looks like the partition type(s)
is altered, maybe to...

http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
Partition types
..........Quote.....................
55 EZ-Drive

EZ-Drive is another disk manager (by MicroHouse, 1992). Linux kernel
versions older than 1.3.29 do not coexist with EZD. (On 990323
MicroHouse International was acquired by EarthWeb; MicroHouse Solutions
split off and changed its name into StorageSoft. MicroHouse Development
split off and changed its name into ImageCast. It is StorageSoft that
now markets EZDrive and DrivePro.)
..........EOQ.......................

Can it really only be necessary to change that "55" to a normal FAT
code? Here is what MBRWork shows to me for my slave drive, run from a
Windows DOS box. "c" is a primary FAT32 partition, & "f" is an extended
partition...

----------------------------------------------------------------------
MBR Partition Information (HD1):
----------------------------------------------------------------------
¦ 0: ¦ 0 ¦ 1 1 0 ¦ c ¦ 239 63 1021 ¦ 63 ¦
16374897 ¦
¦ 1: ¦ 0 ¦ 239 63 1021 ¦ f ¦ 239 63 1021 ¦ 16374960 ¦ 61795440 ¦
¦ 2: ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 0 0 ¦ 0
¦ 0 ¦
¦ 3: ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 0 0 ¦ 0
¦ 0 ¦
----------------------------------------------------------------------

Here is what that URL says about them. Obviously, it was written before
the advent of Win98, though...

0c WIN95 OSR2 FAT32, LBA-mapped
Extended-INT13 equivalent of 0b.

0f WIN95: Extended partition, LBA-mapped
Windows 95 uses 0e and 0f as the extended-INT13 equivalents of 06 and
05. For the problems this causes, see Possible data loss with LBA and
INT13 extensions. (Especially when going back and forth between MSDOS
and Windows 95, strange things may happen with a type 0e or 0f
partition.) Windows NT does not recognize the four W95 types 0b, 0c, 0e,
0f ( Win95 Partition Types Not Recognized by Windows NT). DRDOS 7.03
does not support this type (but DRDOS 7.04 does).


| The point of the Quantum software is to map the disk
| sectors to hardware parameters that the BIOS can understand. Simply
| rewriting the MBR without that particular mapping in place could
| write the MBR to the 'wrong' physical location, possibly overwriting
| data such as FAT. Then again, it may not, as the MBR location is
| often the same between the mapped and unmapped states. That may be
| why the drive appears to be partially accessible (and why I was
| careful to warn against allowing anything to write to it). But when
| it's accessed by the OS, if the correct mapping is not happening then
| the FAT will not make sense (even if it hasn't been corrupted) as the
| logical sector numbers used in the FAT will map to different physical
| locations (and also presumably won't match the partition
| information).
|
| The Quantum software might have a facility for undoing the mapping -
| that is, physically re-arranging the data in the sectors to match the
| default hardware characteristics - but in my experience it is easier
| to copy off the data and rebuild the drive from scratch. Note that I
| was careful not to call this 'uninstalling' - the management software
| is not currently installed, and my guess is that's the problem. What
| we are trying to achieve is to undo the special sector numbering
| arrangement of that drive. It's not just terminology - it's an
| important distinction because there is a significant amount of
| complex data shuffling needed.
|
| Also, we have to first confirm that this is actually the problem.
| --
| Jeff Richards
| MS MVP (Windows - Shell/User)
| "PCR" > wrote in message
| ...
|> Jeff Richards wrote:
|> | It sure sounds like the drive was set up to be managed by the
|> | Quantum software. At this stage, that's a better assumption than
|> | some difference in the LBA (which is what could have happened as a
|> | result of needing to make special settings in the original BIOS).
|> |
|> | If you can find the Quantum software then have a good look through
|> | the documentation to get an idea of what's needed to access that
|> | disk. The process will involve installing the drive management
|> | software to the boot disk (C in your case) WITHOUT going through
|> | the drive setup procedure for the drive that is going to be
|> | managed - that is, without doing the equivalent of FDISK on the
|> | second drive. You might even be able to do the setup without
|> | having that drive connected to the machine, just to be safe. It
|> | will probably complain about no having any drives that need to be
|> | managed, but should still install. Once the software is running
|> | it only interferes with those drives that require it. When you
|> | then reconnect the old drive, it should then be recognised as a
|> | managed drive and should become accessible.
|> |
|> | So the important thing to keep in mind is that the software has two
|> | parts. The disk preparation part for the drive to be managed, which
|> | has already been done and you definitely do not want to repeat, and
|> | the management software installation part (to the boot drive) which
|> | you do want to repeat. The documentation for the software should
|> | cover that option.
|> |
|> | It may be possible to use the Quantum software to prepare a boot
|> | floppy that will give you DOS access to that drive. That will at
|> | least prove what the problem is, and you could, if necessary,
|> | retrieve your data through DOS.
|> |
|> | In the meantime, be very careful that you don't do anything that
|> | might write to that old disk. In its current state it looks usable
|> | in some circumstances, but if data gets written to the disk then it
|> | may be written using different partitioning parameters to those it
|> | is actually set up with, and the file system will be corrupted. Be
|> | particularly careful of anything that wants to try and 'repair' the
|> | disk (as distinct from simply examining, displaying or copying off
|> | the contents) as the repair could destroy all the data.
|>
|> Since mikesmith's new Compaq 5000US motherboard/BIOS sees the full 20
|> GBs of the Maxblast drive (as he reports & I've seen it in a NET ad),
|> isn't it worth a try to uninstall Maxbast? And I wonder whether
|> MBRWork could do that with its Option 8. If Option 8 doesn't show
|> up, I wonder whether this would do it...?...
|>
|> http://www.terabyteunlimited.com/utilities.html MBRWork
|> Free MBR utility.
|>
|> (a) Option 7 - Work with multiple hard drives.
|> Get to drive 1, the bad one.
|> (b) Option 1-- Backup the first track on a hard drive.
|> Makes a backup of the current MBR & EMBR.
|> Then, Option 2 can undo all of the following...
|> (c) Option 3 - Reset the EMBR area to all zeros.
|> A generally unused area between the MBR & end of first track,
|> but it can hold a drive overlay or 3rd party boot manager.
|> (d) Option 4 - Reset the MBR area to all zeros.
|> This wipes the MBR table holding the dimensions of all partitions
|> on that drive, if more than one. But it leaves all other drives
|> intact.
|> (e) Select option A to recover partition(s).
|> This generates partition dimensions into the MBR,
|> getting them somehow from the partition data area itself.
|> Sounds like it ONLY will work, IF the MBR has been mussed,
|> & everything else is fine.
|> (f) Option 5 - Install standard MBR Code
|> This will put boot code into the MBR.
|>
|> .......Quote MBRWork Readme .......
|> MBRWork - Freeware utility to perform some common and uncommon MBR
|> and disk functions. Provided As-Is.
|>
|> It can perform the following:
|>
|> 1 - Backup the first track on a hard drive.
|> 2 - Restore the backup file.
|> 3 - Reset the EMBR area to all zeros.
|> 4 - Reset the MBR are to all zeros.
|> 5 - Install standard MBR Code
|> 6 - Set a partition active (avail on the command line too)
|> 7 - Work with multiple hard drives.
|> 8 - Remove EZ-Drive (You must boot directly to a diskette [bypassing
|> ez-drive] for this option to show)
|> 9 - Edit MBR partition entry values.
|> A - If no partitions exist in the MBR and no EMBR exists then this
|> option will allow you to recover lost FAT, HPFS, NTFS, and
|> Extended partitions.
|> C - Capture up to 64 disk sectors to a file.
|> R - Restore up to 64 disk sectors from a file. This feature should
|> only be used by those who completely understand what they are
|> doing!
|> T - Transfer/Copy sectors from disk to disk. This feature should
|> only be used by those who completely understand what they are
|> doing!
|> P - Compare sectors.
|> .....EOQ... MBRWork Readme .............

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

[mikesmith]

hey jeff sorry i havent got to you in a while..i had some personal family
matters to tend to
i glanced over what you wrote to me..
and i'll try and read it in more detail as soon as i can..
yeah its kind of hard making sense of some of it..
and it may take me a while to try and figure it out...
if i can...
just want you to know im going to respond to it..
and let you know the out come..
and im not just going to dissaper...
just have to take care of other things..
thanks for all your trying to do..
i should respond in a few days..
plus a day or two to try figure what you wrote..
yeah thanks for even trying to help here..
yeah thanks a million buddy..
talk to you soon as possible

"PCR" wrote:

> Jeff Richards wrote:
> | I have not used the process you describe, but I think it is unlikely
> | to work.
>
> Yea, I haven't used it either. And I haven't yet found an instance of
> anyone having used it for this purpose (but I'm sure some must exist
> somewhere). And I'd hate to see mikesmith waste his Quantum Fireball.
>
> BUT Terabyte has deemed it possible to put an Option 8 into MBRWork (a
> little 26KB program), & Terabyte usually is quite good. Therefore, it
> must be possible to do it-- but what really needs to be done?
>
> Is it as you fear that something unusal has been done to the structure
> of the partition (maybe the FAT tables)? Or can it be all is well with
> that-- & only the MBR has been altered? Then, into the MBR boot code was
> inserted a call to the Quantum DDO that kind of supplements BIOS to
> understand LBA. The MBR table (& the FAT tables) could be a normal one
> that includes LBA information. However, looks like the partition type(s)
> is altered, maybe to...
>
> http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
> Partition types
> ..........Quote.....................
> 55 EZ-Drive
>
> EZ-Drive is another disk manager (by MicroHouse, 1992). Linux kernel
> versions older than 1.3.29 do not coexist with EZD. (On 990323
> MicroHouse International was acquired by EarthWeb; MicroHouse Solutions
> split off and changed its name into StorageSoft. MicroHouse Development
> split off and changed its name into ImageCast. It is StorageSoft that
> now markets EZDrive and DrivePro.)
> ..........EOQ.......................
>
> Can it really only be necessary to change that "55" to a normal FAT
> code? Here is what MBRWork shows to me for my slave drive, run from a
> Windows DOS box. "c" is a primary FAT32 partition, & "f" is an extended
> partition...
>
> ----------------------------------------------------------------------
> MBR Partition Information (HD1):
> ----------------------------------------------------------------------
> ¦ 0: ¦ 0 ¦ 1 1 0 ¦ c ¦ 239 63 1021 ¦ 63 ¦
> 16374897 ¦
> ¦ 1: ¦ 0 ¦ 239 63 1021 ¦ f ¦ 239 63 1021 ¦ 16374960 ¦ 61795440 ¦
> ¦ 2: ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 0 0 ¦ 0
> ¦ 0 ¦
> ¦ 3: ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 0 0 ¦ 0
> ¦ 0 ¦
> ----------------------------------------------------------------------
>
> Here is what that URL says about them. Obviously, it was written before
> the advent of Win98, though...
>
> 0c WIN95 OSR2 FAT32, LBA-mapped
> Extended-INT13 equivalent of 0b.
>
> 0f WIN95: Extended partition, LBA-mapped
> Windows 95 uses 0e and 0f as the extended-INT13 equivalents of 06 and
> 05. For the problems this causes, see Possible data loss with LBA and
> INT13 extensions. (Especially when going back and forth between MSDOS
> and Windows 95, strange things may happen with a type 0e or 0f
> partition.) Windows NT does not recognize the four W95 types 0b, 0c, 0e,
> 0f ( Win95 Partition Types Not Recognized by Windows NT). DRDOS 7.03
> does not support this type (but DRDOS 7.04 does).
>
>
> | The point of the Quantum software is to map the disk
> | sectors to hardware parameters that the BIOS can understand. Simply
> | rewriting the MBR without that particular mapping in place could
> | write the MBR to the 'wrong' physical location, possibly overwriting
> | data such as FAT. Then again, it may not, as the MBR location is
> | often the same between the mapped and unmapped states. That may be
> | why the drive appears to be partially accessible (and why I was
> | careful to warn against allowing anything to write to it). But when
> | it's accessed by the OS, if the correct mapping is not happening then
> | the FAT will not make sense (even if it hasn't been corrupted) as the
> | logical sector numbers used in the FAT will map to different physical
> | locations (and also presumably won't match the partition
> | information).
> |
> | The Quantum software might have a facility for undoing the mapping -
> | that is, physically re-arranging the data in the sectors to match the
> | default hardware characteristics - but in my experience it is easier
> | to copy off the data and rebuild the drive from scratch. Note that I
> | was careful not to call this 'uninstalling' - the management software
> | is not currently installed, and my guess is that's the problem. What
> | we are trying to achieve is to undo the special sector numbering
> | arrangement of that drive. It's not just terminology - it's an
> | important distinction because there is a significant amount of
> | complex data shuffling needed.
> |
> | Also, we have to first confirm that this is actually the problem.
> | --
> | Jeff Richards
> | MS MVP (Windows - Shell/User)
> | "PCR" > wrote in message
> | ...
> |> Jeff Richards wrote:
> |> | It sure sounds like the drive was set up to be managed by the
> |> | Quantum software. At this stage, that's a better assumption than
> |> | some difference in the LBA (which is what could have happened as a
> |> | result of needing to make special settings in the original BIOS).
> |> |
> |> | If you can find the Quantum software then have a good look through
> |> | the documentation to get an idea of what's needed to access that
> |> | disk. The process will involve installing the drive management
> |> | software to the boot disk (C in your case) WITHOUT going through
> |> | the drive setup procedure for the drive that is going to be
> |> | managed - that is, without doing the equivalent of FDISK on the
> |> | second drive. You might even be able to do the setup without
> |> | having that drive connected to the machine, just to be safe. It
> |> | will probably complain about no having any drives that need to be
> |> | managed, but should still install. Once the software is running
> |> | it only interferes with those drives that require it. When you
> |> | then reconnect the old drive, it should then be recognised as a
> |> | managed drive and should become accessible.
> |> |
> |> | So the important thing to keep in mind is that the software has two
> |> | parts. The disk preparation part for the drive to be managed, which
> |> | has already been done and you definitely do not want to repeat, and
> |> | the management software installation part (to the boot drive) which
> |> | you do want to repeat. The documentation for the software should
> |> | cover that option.
> |> |
> |> | It may be possible to use the Quantum software to prepare a boot
> |> | floppy that will give you DOS access to that drive. That will at
> |> | least prove what the problem is, and you could, if necessary,
> |> | retrieve your data through DOS.
> |> |
> |> | In the meantime, be very careful that you don't do anything that
> |> | might write to that old disk. In its current state it looks usable
> |> | in some circumstances, but if data gets written to the disk then it
> |> | may be written using different partitioning parameters to those it
> |> | is actually set up with, and the file system will be corrupted. Be
> |> | particularly careful of anything that wants to try and 'repair' the
> |> | disk (as distinct from simply examining, displaying or copying off
> |> | the contents) as the repair could destroy all the data.
> |>
> |> Since mikesmith's new Compaq 5000US motherboard/BIOS sees the full 20
> |> GBs of the Maxblast drive (as he reports & I've seen it in a NET ad),
> |> isn't it worth a try to uninstall Maxbast? And I wonder whether
> |> MBRWork could do that with its Option 8. If Option 8 doesn't show
> |> up, I wonder whether this would do it...?...
> |>
> |> http://www.terabyteunlimited.com/utilities.html MBRWork
> |> Free MBR utility.
> |>
> |> (a) Option 7 - Work with multiple hard drives.
> |> Get to drive 1, the bad one.
> |> (b) Option 1-- Backup the first track on a hard drive.
> |> Makes a backup of the current MBR & EMBR.
> |> Then, Option 2 can undo all of the following...
> |> (c) Option 3 - Reset the EMBR area to all zeros.
> |> A generally unused area between the MBR & end of first track,
> |> but it can hold a drive overlay or 3rd party boot manager.
> |> (d) Option 4 - Reset the MBR area to all zeros.
> |> This wipes the MBR table holding the dimensions of all partitions
> |> on that drive, if more than one. But it leaves all other drives
> |> intact.
> |> (e) Select option A to recover partition(s).
> |> This generates partition dimensions into the MBR,
> |> getting them somehow from the partition data area itself.
> |> Sounds like it ONLY will work, IF the MBR has been mussed,
> |> & everything else is fine.
> |> (f) Option 5 - Install standard MBR Code
> |> This will put boot code into the MBR.
> |>
> |> .......Quote MBRWork Readme .......
> |> MBRWork - Freeware utility to perform some common and uncommon MBR
> |> and disk functions. Provided As-Is.
> |>
> |> It can perform the following:
> |>
> |> 1 - Backup the first track on a hard drive.
> |> 2 - Restore the backup file.
> |> 3 - Reset the EMBR area to all zeros.
> |> 4 - Reset the MBR are to all zeros.
> |> 5 - Install standard MBR Code
> |> 6 - Set a partition active (avail on the command line too)
> |> 7 - Work with multiple hard drives.
> |> 8 - Remove EZ-Drive (You must boot directly to a diskette [bypassing
> |> ez-drive] for this option to show)
> |> 9 - Edit MBR partition entry values.
> |> A - If no partitions exist in the MBR and no EMBR exists then this
> |> option will allow you to recover lost FAT, HPFS, NTFS, and
> |> Extended partitions.
> |> C - Capture up to 64 disk sectors to a file.
> |> R - Restore up to 64 disk sectors from a file. This feature should
> |> only be used by those who completely understand what they are
> |> doing!
> |> T - Transfer/Copy sectors from disk to disk. This feature should
> |> only be used by those who completely understand what they are
> |> doing!
> |> P - Compare sectors.
> |> .....EOQ... MBRWork Readme .............
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> Should things get worse after this,
> PCR
>
>
>
>

[PCR]

mikesmith wrote:
| hey jeff sorry i havent got to you in a while..i had some personal
| family matters to tend to
| i glanced over what you wrote to me..
| and i'll try and read it in more detail as soon as i can..
| yeah its kind of hard making sense of some of it..
| and it may take me a while to try and figure it out...
| if i can...
| just want you to know im going to respond to it..
| and let you know the out come..
| and im not just going to dissaper...
| just have to take care of other things..
| thanks for all your trying to do..
| i should respond in a few days..
| plus a day or two to try figure what you wrote..
| yeah thanks for even trying to help here..
| yeah thanks a million buddy..
| talk to you soon as possible

All right, keep him/us informed.

| "PCR" wrote:
|
|> Jeff Richards wrote:
|> | I have not used the process you describe, but I think it is
|> | unlikely to work.
|>
|> Yea, I haven't used it either. And I haven't yet found an instance of
|> anyone having used it for this purpose (but I'm sure some must exist
|> somewhere). And I'd hate to see mikesmith waste his Quantum Fireball.
|>
|> BUT Terabyte has deemed it possible to put an Option 8 into MBRWork
|> (a
|> little 26KB program), & Terabyte usually is quite good. Therefore, it
|> must be possible to do it-- but what really needs to be done?
|>
|> Is it as you fear that something unusal has been done to the
|> structure
|> of the partition (maybe the FAT tables)? Or can it be all is well
|> with
|> that-- & only the MBR has been altered? Then, into the MBR boot code
|> was inserted a call to the Quantum DDO that kind of supplements BIOS
|> to
|> understand LBA. The MBR table (& the FAT tables) could be a normal
|> one
|> that includes LBA information. However, looks like the partition
|> type(s)
|> is altered, maybe to...
|>
|> http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
|> Partition types
|> ..........Quote.....................
|> 55 EZ-Drive
|>
|> EZ-Drive is another disk manager (by MicroHouse, 1992). Linux kernel
|> versions older than 1.3.29 do not coexist with EZD. (On 990323
|> MicroHouse International was acquired by EarthWeb; MicroHouse
|> Solutions
|> split off and changed its name into StorageSoft. MicroHouse
|> Development
|> split off and changed its name into ImageCast. It is StorageSoft that
|> now markets EZDrive and DrivePro.)
|> ..........EOQ.......................
|>
|> Can it really only be necessary to change that "55" to a normal FAT
|> code? Here is what MBRWork shows to me for my slave drive, run from a
|> Windows DOS box. "c" is a primary FAT32 partition, & "f" is an
|> extended partition...
|>
|> ---------------------------------------------------------------------
-
|> MBR Partition Information (HD1):
|> ---------------------------------------------------------------------
-
|> ¦ 0: ¦ 0 ¦ 1 1 0 ¦ c ¦ 239 63 1021 ¦
|> 63 ¦ 16374897 ¦
|> ¦ 1: ¦ 0 ¦ 239 63 1021 ¦ f ¦ 239 63 1021 ¦ 16374960 ¦
|> 61795440 ¦ ¦ 2: ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 0
|> 0 ¦ 0 ¦ 0 ¦
|> ¦ 3: ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 0 0 ¦
|> 0 ¦ 0 ¦
|> ---------------------------------------------------------------------
-
|>
|> Here is what that URL says about them. Obviously, it was written
|> before
|> the advent of Win98, though...
|>
|> 0c WIN95 OSR2 FAT32, LBA-mapped
|> Extended-INT13 equivalent of 0b.
|>
|> 0f WIN95: Extended partition, LBA-mapped
|> Windows 95 uses 0e and 0f as the extended-INT13 equivalents of 06 and
|> 05. For the problems this causes, see Possible data loss with LBA and
|> INT13 extensions. (Especially when going back and forth between MSDOS
|> and Windows 95, strange things may happen with a type 0e or 0f
|> partition.) Windows NT does not recognize the four W95 types 0b, 0c,
|> 0e, 0f ( Win95 Partition Types Not Recognized by Windows NT). DRDOS
|> 7.03
|> does not support this type (but DRDOS 7.04 does).
|>
|>
|> | The point of the Quantum software is to map the disk
|> | sectors to hardware parameters that the BIOS can understand. Simply
|> | rewriting the MBR without that particular mapping in place could
|> | write the MBR to the 'wrong' physical location, possibly
|> | overwriting data such as FAT. Then again, it may not, as the MBR
|> | location is often the same between the mapped and unmapped states.
|> | That may be why the drive appears to be partially accessible (and
|> | why I was careful to warn against allowing anything to write to
|> | it). But when it's accessed by the OS, if the correct mapping is
|> | not happening then the FAT will not make sense (even if it hasn't
|> | been corrupted) as the logical sector numbers used in the FAT will
|> | map to different physical locations (and also presumably won't
|> | match the partition information).
|> |
|> | The Quantum software might have a facility for undoing the mapping
|> | - that is, physically re-arranging the data in the sectors to
|> | match the default hardware characteristics - but in my experience
|> | it is easier to copy off the data and rebuild the drive from
|> | scratch. Note that I was careful not to call this 'uninstalling' -
|> | the management software is not currently installed, and my guess
|> | is that's the problem. What we are trying to achieve is to undo
|> | the special sector numbering arrangement of that drive. It's not
|> | just terminology - it's an important distinction because there is
|> | a significant amount of complex data shuffling needed.
|> |
|> | Also, we have to first confirm that this is actually the problem.
|> | --
|> | Jeff Richards
|> | MS MVP (Windows - Shell/User)
|> | "PCR" > wrote in message
|> | ...
|> |> Jeff Richards wrote:
|> |> | It sure sounds like the drive was set up to be managed by the
|> |> | Quantum software. At this stage, that's a better assumption than
|> |> | some difference in the LBA (which is what could have happened
|> |> | as a result of needing to make special settings in the original
|> |> | BIOS).
|> |> |
|> |> | If you can find the Quantum software then have a good look
|> |> | through the documentation to get an idea of what's needed to
|> |> | access that disk. The process will involve installing the drive
|> |> | management software to the boot disk (C in your case) WITHOUT
|> |> | going through the drive setup procedure for the drive that is
|> |> | going to be managed - that is, without doing the equivalent of
|> |> | FDISK on the second drive. You might even be able to do the
|> |> | setup without having that drive connected to the machine, just
|> |> | to be safe. It will probably complain about no having any
|> |> | drives that need to be managed, but should still install. Once
|> |> | the software is running it only interferes with those drives
|> |> | that require it. When you then reconnect the old drive, it
|> |> | should then be recognised as a managed drive and should become
|> |> | accessible.
|> |> |
|> |> | So the important thing to keep in mind is that the software has
|> |> | two parts. The disk preparation part for the drive to be
|> |> | managed, which has already been done and you definitely do not
|> |> | want to repeat, and the management software installation part
|> |> | (to the boot drive) which you do want to repeat. The
|> |> | documentation for the software should cover that option.
|> |> |
|> |> | It may be possible to use the Quantum software to prepare a boot
|> |> | floppy that will give you DOS access to that drive. That will
|> |> | at least prove what the problem is, and you could, if necessary,
|> |> | retrieve your data through DOS.
|> |> |
|> |> | In the meantime, be very careful that you don't do anything that
|> |> | might write to that old disk. In its current state it looks
|> |> | usable in some circumstances, but if data gets written to the
|> |> | disk then it may be written using different partitioning
|> |> | parameters to those it is actually set up with, and the file
|> |> | system will be corrupted. Be particularly careful of anything
|> |> | that wants to try and 'repair' the disk (as distinct from
|> |> | simply examining, displaying or copying off the contents) as
|> |> | the repair could destroy all the data.
|> |>
|> |> Since mikesmith's new Compaq 5000US motherboard/BIOS sees the
|> |> full 20 GBs of the Maxblast drive (as he reports & I've seen it
|> |> in a NET ad), isn't it worth a try to uninstall Maxbast? And I
|> |> wonder whether MBRWork could do that with its Option 8. If Option
|> |> 8 doesn't show up, I wonder whether this would do it...?...
|> |>
|> |> http://www.terabyteunlimited.com/utilities.html MBRWork
|> |> Free MBR utility.
|> |>
|> |> (a) Option 7 - Work with multiple hard drives.
|> |> Get to drive 1, the bad one.
|> |> (b) Option 1-- Backup the first track on a hard drive.
|> |> Makes a backup of the current MBR & EMBR.
|> |> Then, Option 2 can undo all of the following...
|> |> (c) Option 3 - Reset the EMBR area to all zeros.
|> |> A generally unused area between the MBR & end of first track,
|> |> but it can hold a drive overlay or 3rd party boot manager.
|> |> (d) Option 4 - Reset the MBR area to all zeros.
|> |> This wipes the MBR table holding the dimensions of all
|> |> partitions on that drive, if more than one. But it leaves all
|> |> other drives intact.
|> |> (e) Select option A to recover partition(s).
|> |> This generates partition dimensions into the MBR,
|> |> getting them somehow from the partition data area itself.
|> |> Sounds like it ONLY will work, IF the MBR has been mussed,
|> |> & everything else is fine.
|> |> (f) Option 5 - Install standard MBR Code
|> |> This will put boot code into the MBR.
|> |>
|> |> .......Quote MBRWork Readme .......
|> |> MBRWork - Freeware utility to perform some common and uncommon MBR

|> |> and disk functions. Provided As-Is.
|> |>
|> |> It can perform the following:
|> |>
|> |> 1 - Backup the first track on a hard drive.
|> |> 2 - Restore the backup file.
|> |> 3 - Reset the EMBR area to all zeros.
|> |> 4 - Reset the MBR are to all zeros.
|> |> 5 - Install standard MBR Code
|> |> 6 - Set a partition active (avail on the command line too)
|> |> 7 - Work with multiple hard drives.
|> |> 8 - Remove EZ-Drive (You must boot directly to a diskette
|> |> [bypassing ez-drive] for this option to show)
|> |> 9 - Edit MBR partition entry values.
|> |> A - If no partitions exist in the MBR and no EMBR exists then this
|> |> option will allow you to recover lost FAT, HPFS, NTFS, and
|> |> Extended partitions.
|> |> C - Capture up to 64 disk sectors to a file.
|> |> R - Restore up to 64 disk sectors from a file. This feature
|> |> should only be used by those who completely understand what
|> |> they are
|> |> doing!
|> |> T - Transfer/Copy sectors from disk to disk. This feature should
|> |> only be used by those who completely understand what they are
|> |> doing!
|> |> P - Compare sectors.
|> |> .....EOQ... MBRWork Readme .............
|>
|> --
|> Thanks or Good Luck,
|> There may be humor in this post, and,
|> Naturally, you will not sue,
|> Should things get worse after this,
|> PCR
|>

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

[Jeff Richards]

That's OK - I'm watching.

Don't forget that we haven't proved that we know what the problem is.
Although a missing disk manager seems most likely to me, it's still possible
that the problem has an entirely different cause.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"mikesmith" > wrote in message
...
> hey jeff sorry i havent got to you in a while..i had some personal family
> matters to tend to
> i glanced over what you wrote to me..
> and i'll try and read it in more detail as soon as i can..
> yeah its kind of hard making sense of some of it..
> and it may take me a while to try and figure it out...
> if i can...
> just want you to know im going to respond to it..
> and let you know the out come..
> and im not just going to dissaper...
> just have to take care of other things..
> thanks for all your trying to do..
> i should respond in a few days..
> plus a day or two to try figure what you wrote..
> yeah thanks for even trying to help here..
> yeah thanks a million buddy..
> talk to you soon as possible
>

[mikesmith]

hey jeff remember me..lol..

jeff if you ever work on computers
you should read this..

im going to go off on a little tangent point here..
but it is kinda the fault that made all of this problem..
and why i moved my hard drive to another computer in the first place..

remember what started it all was..
when my Abit KT7-raid mother board died..
and i put my salve Quantum (data only) drive into a Compaq 5000 US

well heres what my KT7 computer was doing...
it keep locking up..
freezing..
it would freeze up on the windows 98 logo screen..
it wouldent get past that..
and sometimes it wouldent even make it to that..
one day it was fine..
the next day it was dead..
i couldent get into windows 98..

i read fourm after fourm..
and tried everything all of them said..
to try and fix my computer...

replace the memory..
replace your power supply..
replace your video card..
replace your processor..
sound card....
cables..

this that..this that
BLAH BLAH BLAH BLAH...

reinstall windows..

yeah thats the fix everyone recomends...
when nothing they recomend works...
re-install windows...

none of what i did worked!..
short of re-installing windows

well guess what jeff..i figured it out..
and fixed my Kt7 motherboard..
and im thinking this might be a big problem with more peoples computers
then most people know about...

it has to do with a manufacturing defect with MILLION AND MILLIONS
of capacitors that were put in almost every mother board made
Abits..Msi..Giga-bytes...ALL OF THEM..

i found this web site..http://www.badcaps.net

and i read this page.....http://www.badcaps.net/pages.php?vid=4
**this is the page that explains how it all happened**

and i read their fourm...http://www.badcaps.net/forum/
to find out how to fix it..

well i re-capped my motherboard..
and soldered all new Nichicon caps in my board

and replaced all my **bluging TP-cons**..i replaced them all..all the caps
on the board..
there is picture apon picture of these bluging defective capacitors in their
fourm
from peoples post's in it...
i wonder how many people have this problem and don't even know..
and i wonder how many boards have been thrown out because of it..

well now my mother board runs better then it did brand new..
it runs like superman on steroids..lol..

i wish i would have read those articles years ago because all the problems
i ever encountered were probably all related to this problem..
till one day...it got so bad..
it wouldent work no more..
and my mother board died

plus!!!
i had 2 power supplys i bought over the years that died..
a 350 watt one..
and a 400 watt one..
guess what..
i replaced 6 caps in one..for like 4 dollars
and 5 caps in the other for 3 dollars..
they work now!!!!
i wish i would have knew..
i would have not had to buy third power supply for 65 bucks..

i have a 32 inch TV i bought a few years back..
the top and bottom of the picture
got big black lines in them..top and bottom..like 3 inches wide..

so i bought a new TV for like 400 bucks..
because my old one went bad with those big black lines..
well guess what...
i replaced 1 cap..for 65 cents..
and now my TV works again...

lol..im going Cap replace crazy..lol...

i wish i would have read that web page years ago...
i would have saved alot of money..
anyways..

maybe alot of problems people think are caused by this or that
really might just be bad caps...
im going to check those first thing from now on !!!!!

back to my hard drive...
well..
i put that hard drive back in my RECAPED Kt7...and its seeing it..
nothing was wrong with the hard drive to start...
it was the stupid Compaq system..

BUT!!!
BUT
but i did some things to the Hard drive using TESTDISK..
that the developer of TESTDISK had me do..
like changing things on the master boot thing i think...

and now the files arent acessable...
i see funny looking files and folders
they all have funny symbols..
insted of the names..
and...i dont know...
i think i messed stuff up doing what he said to do..
...anyways...i'll look into that..
and try to find out what things i did..
so i can tell you what i did..
its hard talking to that guy..
i dont think he speeks english.....im guessing..

i'll do that in my next post to you..

but yeah it was that gay AZZ Compaq...nothing was wrong with the hard drive
in the first place...
it was something in that stupid compaq set up..
im going to have to ask that TESTDISK guy what i did and how to reverse it
if i can...

yeah thanks for trying to help me Jeff..
talk to you soon buddy....
THANKS FOR YOUR HELP!!!


"Jeff Richards" wrote:

> That's OK - I'm watching.

[Buffalo]

mikesmith wrote:
[snip]
> it has to do with a manufacturing defect with MILLION AND MILLIONS
> of capacitors that were put in almost every mother board made
> Abits..Msi..Giga-bytes...ALL OF THEM..
>
> i found this web site..http://www.badcaps.net
>
> and i read this page.....http://www.badcaps.net/pages.php?vid=4
> **this is the page that explains how it all happened**
>
> and i read their fourm...http://www.badcaps.net/forum/
> to find out how to fix it..
>
> well i re-capped my motherboard..
> and soldered all new Nichicon caps in my board
>
> and replaced all my **bluging TP-cons**..i replaced them all..all the
> caps on the board..
> there is picture apon picture of these bluging defective capacitors
> in their fourm
> from peoples post's in it...
> i wonder how many people have this problem and don't even know..
> and i wonder how many boards have been thrown out because of it..
>
> well now my mother board runs better then it did brand new..
> it runs like superman on steroids..lol..
[snip]

My roommate's Abit K-7 mb also had problems and I found one bulging cap and
replaced it. I thouht it was very difficult to replace. It is still working
like a charm.
This was several years ago. Yes, the bad caps were on many MBs and all
because some cap mfg was using a stolen chemical component formula that had
the wrong chemicals in it, or so I heard. :)
How did you replace all those caps? What method did you use and what
equipment did you need?
Don't go cap crazy, and remember, the ones in a TV set, etc have a lot of
high voltage in them and could cause serious injury, even death.

Sorry I can't help you on the HDD problem either, but hopefully someone here
can.
Buffalo

[PCR]

mikesmith wrote:
| hey jeff remember me..lol..
|
| jeff if you ever work on computers
| you should read this..
|
| im going to go off on a little tangent point here..
| but it is kinda the fault that made all of this problem..
| and why i moved my hard drive to another computer in the first place..
|
| remember what started it all was..
| when my Abit KT7-raid mother board died..
| and i put my salve Quantum (data only) drive into a Compaq 5000 US
|
| well heres what my KT7 computer was doing...
| it keep locking up..
| freezing..
| it would freeze up on the windows 98 logo screen..
| it wouldent get past that..
| and sometimes it wouldent even make it to that..
| one day it was fine..
| the next day it was dead..
| i couldent get into windows 98..
|
| i read fourm after fourm..
| and tried everything all of them said..
| to try and fix my computer...
|
| replace the memory..
| replace your power supply..
| replace your video card..
| replace your processor..
| sound card....
| cables..
|
| this that..this that
| BLAH BLAH BLAH BLAH...
|
| reinstall windows..
|
| yeah thats the fix everyone recomends...
| when nothing they recomend works...
| re-install windows...
|
| none of what i did worked!..
| short of re-installing windows
|
| well guess what jeff..i figured it out..
| and fixed my Kt7 motherboard..
| and im thinking this might be a big problem with more peoples
| computers then most people know about...
|
| it has to do with a manufacturing defect with MILLION AND MILLIONS
| of capacitors that were put in almost every mother board made
| Abits..Msi..Giga-bytes...ALL OF THEM..
|
| i found this web site..http://www.badcaps.net
|
| and i read this page.....http://www.badcaps.net/pages.php?vid=4
| **this is the page that explains how it all happened**
|
| and i read their fourm...http://www.badcaps.net/forum/
| to find out how to fix it..
|
| well i re-capped my motherboard..
| and soldered all new Nichicon caps in my board
|
| and replaced all my **bluging TP-cons**..i replaced them all..all the
| caps on the board..
| there is picture apon picture of these bluging defective capacitors
| in their fourm
| from peoples post's in it...
| i wonder how many people have this problem and don't even know..
| and i wonder how many boards have been thrown out because of it..
|
| well now my mother board runs better then it did brand new..
| it runs like superman on steroids..lol..
|
| i wish i would have read those articles years ago because all the
| problems i ever encountered were probably all related to this
| problem..
| till one day...it got so bad..
| it wouldent work no more..
| and my mother board died
|
| plus!!!
| i had 2 power supplys i bought over the years that died..
| a 350 watt one..
| and a 400 watt one..
| guess what..
| i replaced 6 caps in one..for like 4 dollars
| and 5 caps in the other for 3 dollars..
| they work now!!!!
| i wish i would have knew..
| i would have not had to buy third power supply for 65 bucks..
|
| i have a 32 inch TV i bought a few years back..
| the top and bottom of the picture
| got big black lines in them..top and bottom..like 3 inches wide..
|
| so i bought a new TV for like 400 bucks..
| because my old one went bad with those big black lines..
| well guess what...
| i replaced 1 cap..for 65 cents..
| and now my TV works again...
|
| lol..im going Cap replace crazy..lol...
|
| i wish i would have read that web page years ago...
| i would have saved alot of money..
| anyways..
|
| maybe alot of problems people think are caused by this or that
| really might just be bad caps...
| im going to check those first thing from now on !!!!!
|
| back to my hard drive...
| well..
| i put that hard drive back in my RECAPED Kt7...and its seeing it..
| nothing was wrong with the hard drive to start...
| it was the stupid Compaq system..
|
| BUT!!!
| BUT
| but i did some things to the Hard drive using TESTDISK..
| that the developer of TESTDISK had me do..
| like changing things on the master boot thing i think...
|
| and now the files arent acessable...
| i see funny looking files and folders
| they all have funny symbols..
| insted of the names..
| and...i dont know...
| i think i messed stuff up doing what he said to do..
| ..anyways...i'll look into that..
| and try to find out what things i did..
| so i can tell you what i did..
| its hard talking to that guy..
| i dont think he speeks english.....im guessing..
|
| i'll do that in my next post to you..
|
| but yeah it was that gay AZZ Compaq...nothing was wrong with the hard
| drive in the first place...
| it was something in that stupid compaq set up..
| im going to have to ask that TESTDISK guy what i did and how to
| reverse it if i can...
|
| yeah thanks for trying to help me Jeff..
| talk to you soon buddy....
| THANKS FOR YOUR HELP!!!

I'm sure Jeff remembers & is still watching. Few of us can recall he has
gone senile yet & he is wearing triple-thick trifocal glasses! I'm no
expert on caps, & the site you posted won't come up for me; so, answer
Buffalo's questions when you get a chance too. You should hesitate to
recommend a thing that could electrocute us. We get our electro-shock
brain therapy & restarted hearts on an as-needed basis here! Keep us all
informed.

I don't want to step on the toes of your TESTDISK guy, but, yea, try to
recall what he said & what has been done. Was it determined that the
Quantum Fireball Hard Drive had MaxBlast unnecessarily installed? Is the
TESTDISK guy trying to uninstall it or to reinstall it? Maybe post what
MBRWork shows for the MBR on the Fireball. What partition type does it
show?

| "Jeff Richards" wrote:
|
|> That's OK - I'm watching.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

[Jeff Richards]

The capacitor issue is widely known, although the machines in which it
occurs are that much older now and repair people are not running into it
that often, so it's very easy to overlook. Also, that particular problem was
associated with particular models of motherboard so a lot of people won't
come across it at all.

But those capacitors don't age well, and the problem has existed in other
equipment for many years. I'm sure I can remember an article way back from
the 70's where a technician had to decide whether or not the effort in
replacing all the suspect caps in a TV was going to cost more than replacing
it. So you are certainly not the first, and probably not the last, to be
bitten. I have just thrown out a massive 12v power supply with an array of
huge electrolytic capacitors that would have made a terrific power supply
for a large model car or train layout, but I was too scared to turn it on
for fear that the ancient capacitors would explode as they charged up, and
that would have been a real mess!

If my guess about the disk drive was correct then any changes you have made
to that disk could be the cause of the problem, and might not be reversible.
I did warn about not letting anything be written to that drive :-{ If
something in the boot or MBR area has been changed, then the garbled data
such as you are seeing is confirming my guess. I agree that your best option
is to try and undo what was done. Another option is to prepare a boot floppy
with the drive management software installed, boot to it, and see if the
disk is recognised when the drive management software is running. If all
that fails, standard disk data recovery tools might be able to put some of
the disk back together - at least fragments of files could be recovered, and
depending on how important they are, you may be able to reconstruct them.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"mikesmith" > wrote in message
...
> hey jeff remember me..lol..
>
> jeff if you ever work on computers
> you should read this..
>
> im going to go off on a little tangent point here..
> but it is kinda the fault that made all of this problem..
> and why i moved my hard drive to another computer in the first place..
>
> remember what started it all was..
> when my Abit KT7-raid mother board died..
> and i put my salve Quantum (data only) drive into a Compaq 5000 US
>
> well heres what my KT7 computer was doing...
> it keep locking up..
> freezing..
> it would freeze up on the windows 98 logo screen..
> it wouldent get past that..
> and sometimes it wouldent even make it to that..
> one day it was fine..
> the next day it was dead..
> i couldent get into windows 98..
>
> i read fourm after fourm..
> and tried everything all of them said..
> to try and fix my computer...
>
> replace the memory..
> replace your power supply..
> replace your video card..
> replace your processor..
> sound card....
> cables..
>
> this that..this that
> BLAH BLAH BLAH BLAH...
>
> reinstall windows..
>
> yeah thats the fix everyone recomends...
> when nothing they recomend works...
> re-install windows...
>
> none of what i did worked!..
> short of re-installing windows
>
> well guess what jeff..i figured it out..
> and fixed my Kt7 motherboard..
> and im thinking this might be a big problem with more peoples computers
> then most people know about...
>
> it has to do with a manufacturing defect with MILLION AND MILLIONS
> of capacitors that were put in almost every mother board made
> Abits..Msi..Giga-bytes...ALL OF THEM..
>
> i found this web site..http://www.badcaps.net
>
> and i read this page.....http://www.badcaps.net/pages.php?vid=4
> **this is the page that explains how it all happened**
>
> and i read their fourm...http://www.badcaps.net/forum/
> to find out how to fix it..
>
> well i re-capped my motherboard..
> and soldered all new Nichicon caps in my board
>
> and replaced all my **bluging TP-cons**..i replaced them all..all the caps
> on the board..
> there is picture apon picture of these bluging defective capacitors in
> their
> fourm
> from peoples post's in it...
> i wonder how many people have this problem and don't even know..
> and i wonder how many boards have been thrown out because of it..
>
> well now my mother board runs better then it did brand new..
> it runs like superman on steroids..lol..
>
> i wish i would have read those articles years ago because all the problems
> i ever encountered were probably all related to this problem..
> till one day...it got so bad..
> it wouldent work no more..
> and my mother board died
>
> plus!!!
> i had 2 power supplys i bought over the years that died..
> a 350 watt one..
> and a 400 watt one..
> guess what..
> i replaced 6 caps in one..for like 4 dollars
> and 5 caps in the other for 3 dollars..
> they work now!!!!
> i wish i would have knew..
> i would have not had to buy third power supply for 65 bucks..
>
> i have a 32 inch TV i bought a few years back..
> the top and bottom of the picture
> got big black lines in them..top and bottom..like 3 inches wide..
>
> so i bought a new TV for like 400 bucks..
> because my old one went bad with those big black lines..
> well guess what...
> i replaced 1 cap..for 65 cents..
> and now my TV works again...
>
> lol..im going Cap replace crazy..lol...
>
> i wish i would have read that web page years ago...
> i would have saved alot of money..
> anyways..
>
> maybe alot of problems people think are caused by this or that
> really might just be bad caps...
> im going to check those first thing from now on !!!!!
>
> back to my hard drive...
> well..
> i put that hard drive back in my RECAPED Kt7...and its seeing it..
> nothing was wrong with the hard drive to start...
> it was the stupid Compaq system..
>
> BUT!!!
> BUT
> but i did some things to the Hard drive using TESTDISK..
> that the developer of TESTDISK had me do..
> like changing things on the master boot thing i think...
>
> and now the files arent acessable...
> i see funny looking files and folders
> they all have funny symbols..
> insted of the names..
> and...i dont know...
> i think i messed stuff up doing what he said to do..
> ..anyways...i'll look into that..
> and try to find out what things i did..
> so i can tell you what i did..
> its hard talking to that guy..
> i dont think he speeks english.....im guessing..
>
> i'll do that in my next post to you..
>
> but yeah it was that gay AZZ Compaq...nothing was wrong with the hard
> drive
> in the first place...
> it was something in that stupid compaq set up..
> im going to have to ask that TESTDISK guy what i did and how to reverse it
> if i can...
>
> yeah thanks for trying to help me Jeff..
> talk to you soon buddy....
> THANKS FOR YOUR HELP!!!
>
>
> "Jeff Richards" wrote:
>
>> That's OK - I'm watching.
>

[mikesmith]

hey bufflo..lol...i wana talk to jeff!! or PC..lol..
about my hard drive...

but to answer your question about what i did...
i replaced all the caps...
about 40 or so of them..

you gota get the right kinds of caps to replace them..
not just the right ""microfarad..and the volts...and the heat range""
they gota be the same CLASS TYPES..""OR BETTER""
like THE RIPPLE CURRENT..rating..higher is better
theres a special class type of caps for computers...

ha ha...what type of tools did i use...

i just used a NEW ""30 watt "" radio shack soldering iron..
you gota tin the tip...and keep it clean...
a lil sponge to clean the tip..
you ever solder anything before?..

and a roll of radio shack 60/40 .032 thick solder..
and my big magnafying glass stand that has a light on it..
a lil pair of wire snips..
and the all important NEEDLE..sewing needle...
the needles to poke the hole threw after removing that caps...

first i'd put a real little extra drop of solder on both ends of the cap..
just a lil bit..real little
it makes it easier to heat..adding a lil extra bit of solder to remove them..
then i heated one end..gave it a lil easy pull..pulling it out a lil..
then the other end..
back and forth..
lil heat pull easy..lil heat lil easy pull...back and forth..
like rocking it out...
it takes like 2 times...maybe 3 per side of the cap..
not pulling it hard..nice easy
cause if you pull it and force it..you can pull up the copper foil on the PC
board...
nice and easy...back and forth..one side then the other...

then after i had the cap out...
there would still be solder still in the whole...
so..
i'd put the needle in the whole on one side of the board..
then heat the other side of the hole on the other side of the board..
while i'd push the needle threw...
((might even put a lil bit of solder on it again so it would heat easy))

push threw the lil bit of solder left behind with the needle..
the solder doesnt really stick to the stainless steel of a needle..
and there you go...you'd have a nice clean hole...

(i put the needle into a lil square peice of plastic like a knob)..
the plastic knob on the end..to have something i could push on

like make a lil tool..
your lil needle tool..lol...

then after having a nice lil clean hole..
put your new cap in the right way...
gota make sure its in the right way...
negative...positive...

then solder it up...
real little bit of solder...takes like 2-3 seconds
have a nice lil shiney solder joint..
then clip off the extra bit of the new caps leads..
making sure its not to tall sticking out the back of the board..
so it dont touch the case like ground on the case..

yeah i had electronics in high school..
i've solder stuff before..
just a lil pratice anyone could do it .
anyone with a steady hand...

yeah i replaced them all about 40 or so caps....

yeah i know about CAPS holding a charge..
and they can even re-charge just sitting on a shelf..
CRT's are the worst..lol...
you know what a CRT is??..

anyways...yeah no need for a 100 dollar soldering station..

hey Bufflo...you ever resolder a SMD?..
i made this cool ass hot air soldering gun..
with a Radio shack DE-soldering iron..and a fish tank lil air pump..and a
POT..
lol...yeah i like tinkering..i wana be able to fix everything..lol..

anyways...i wana fix my hard drive that Comapq messed up..
yeah my hard drive was fine..it was that stupid mother board..
nothing was wrong with it in the first palce..
when i thought there was...
it had something to do with the mother board not seeing it right threw
Windows 98
i dont know why the Compaq didnt see it in windows 98..

anyways...hey jeff..or PC...where you cool dudes at...lol..im lost..
i've fallen and i cant get up...lol..

[mikesmith]

hey bufflo..lol...i wana talk to jeff!! or PC..lol..
about my hard drive...

but to answer your question about what i did...
i replaced all the caps...
about 40 or so of them..

you gota get the right kinds of caps to replace them..
not just the right ""microfarad..and the volts...and the heat range""
they gota be the same CLASS TYPES..""OR BETTER""
like THE RIPPLE CURRENT..rating..higher is better
theres a special class type of caps for computers...

ha ha...what type of tools did i use...

i just used a NEW ""30 watt "" radio shack soldering iron..
you gota tin the tip...and keep it clean...
a lil sponge to clean the tip..
you ever solder anything before?..

and a roll of radio shack 60/40 .032 thick solder..
and my big magnafying glass stand that has a light on it..
a lil pair of wire snips..
and the all important NEEDLE..sewing needle...
the needles to poke the hole threw after removing that caps...

first i'd put a real little extra drop of solder on both ends of the cap..
just a lil bit..real little
it makes it easier to heat..adding a lil extra bit of solder to remove them..
then i heated one end..gave it a lil easy pull..pulling it out a lil..
then the other end..
back and forth..
lil heat pull easy..lil heat lil easy pull...back and forth..
like rocking it out...
it takes like 2 times...maybe 3 per side of the cap..
not pulling it hard..nice easy
cause if you pull it and force it..you can pull up the copper foil on the PC
board...
nice and easy...back and forth..one side then the other...

then after i had the cap out...
there would still be solder still in the whole...
so..
i'd put the needle in the whole on one side of the board..
then heat the other side of the hole on the other side of the board..
while i'd push the needle threw...
((might even put a lil bit of solder on it again so it would heat easy))

push threw the lil bit of solder left behind with the needle..
the solder doesnt really stick to the stainless steel of a needle..
and there you go...you'd have a nice clean hole...

(i put the needle into a lil square peice of plastic like a knob)..
the plastic knob on the end..to have something i could push on

like make a lil tool..
your lil needle tool..lol...

then after having a nice lil clean hole..
put your new cap in the right way...
gota make sure its in the right way...
negative...positive...

then solder it up...
real little bit of solder...takes like 2-3 seconds
have a nice lil shiney solder joint..
then clip off the extra bit of the new caps leads..
making sure its not to tall sticking out the back of the board..
so it dont touch the case like ground on the case..

yeah i had electronics in high school..
i've solder stuff before..
just a lil pratice anyone could do it .
anyone with a steady hand...

yeah i replaced them all about 40 or so caps....

yeah i know about CAPS holding a charge..
and they can even re-charge just sitting on a shelf..
CRT's are the worst..lol...
you know what a CRT is??..

anyways...yeah no need for a 100 dollar soldering station..

hey Bufflo...you ever resolder a SMD?..
i made this cool ass hot air soldering gun..
with a Radio shack DE-soldering iron..and a fish tank lil air pump..and a
POT..
lol...yeah i like tinkering..i wana be able to fix everything..lol..

anyways...i wana fix my hard drive that Comapq messed up..
yeah my hard drive was fine..it was that stupid mother board..
nothing was wrong with it in the first palce..
when i thought there was...
it had something to do with the mother board not seeing it right threw
Windows 98
i dont know why the Compaq didnt see it in windows 98..

anyways...hey jeff..or PC...where you cool dudes at...lol..im lost..
i've fallen and i cant get up...lol..

[mikesmith]

HEY JEFF!!!..
HEY PC!!!!

omg..im not use to using this fourm...
i didn't see the blue MORE THING down at the bottom of the page...

i posted a reply to bufflos thing..
and didnt see my post i was like what the heck!!..
wheres my post...

and i messed up and posted it 2 times....
lol..i almost posted it 3 times..lol..

yeah i didn't see your guys replys either..

i didnt know there was another page..
and had to click the lil blue MORE thing in the lower right hand corner...
im use to seeing numbers..

i didnt see it cause i didnt scroll over...
i kinda look silly posting the same thing 2 times....
sorry...

yeah i have ADD...and am hyper active...

lol..im like all happy you guys are still here..

OMG!!..i didnt see your post and thought you guys left me cause i type long
post...

lol..one time this guy..CLSID...for mega codec pack
his fourm..
said i gave him a head ache..lol..

and he said he couldent read all my babble...
and told me to just throw away my computer..
and find something else to do with my free time..lol..

im sorry i dont type like a major geek...
and say stuff like...

yeah my OS is not doing a DL right..i think my TCP/ICP..isent connecting to
my ISP right...and i have changed my INF...and switched DLL's..

you know how hard it is reading stuff like that..
when you have no idea what thier talking about..

yeah im not a geek and dont know everything..
yeah im dyslexic...ha ha i googled that..
its hard typing..

thats why i type paragraphs and make spaces between them..
because i get lost if i don't....

reading is hard too..
im happy you guys..JEFF...AND PC..
are still here..im gona try and figure what i did with
testdisk..
that guy who owns testdisk...the developer guy..
im not sure he talks good english..

cause i'd write alot...and he'd just say stuff like..

Go in Advanced, choose Boot, RebuildBS, List, Quit
and send me the new log file..

i have the e-mails...and the log files..
should i post them?..
any of you two ever use TESTDISK..
i used it in DOS.....
it is used as a boot type thing..
you know..it runs in DOS..

anyways..lol..im like all happy your both still here..
i didn't know there was the MORE thing in the lower right corner..

yeah should i post all the e-mails and logs?..
or like personally e-mail and foward them to both you?...

like copy and paste them all..i think theres like 4-5-6 of them..

my eyes are hurting typing so much..
i'll talk to you guys tomarrow...

thanks so much jeff and pc..you guys are wicked cool...lol..
ha ha even if we dont fix this..it is cool you guys just trying to help..
thanks guys

[Buffalo]

mikesmith wrote:
> hey bufflo..lol...i wana talk to jeff!! or PC..lol..
> about my hard drive...
>
> but to answer your question about what i did...
> i replaced all the caps...
> about 40 or so of them..
>
> you gota get the right kinds of caps to replace them..
> not just the right ""microfarad..and the volts...and the heat range""
> they gota be the same CLASS TYPES..""OR BETTER""
> like THE RIPPLE CURRENT..rating..higher is better
> theres a special class type of caps for computers...

[snip]

Thanks for the tip on the stainless steel needle and the steps needed.
I've done some soldering and I do know what a CRT is. :)
Thanks again.
If you don't get the solution here, try VirtualDr.com. All you have to do
is Register (free) and they are an excellent help group.
I am sure you will be pleased with their knowledge and personalities.
The help is usually very accurate and polite and free.
Buffalo

[mikesmith]

hey jeff!!..
how you doing buddy..
i really dont know how to use this fourm..
i kinda got lost not knowing there was a MORE thing.
i wrote a lil about that to you and PC..
im hoping i hear from you again..
yeah im not really use to this forum..i didnt see your guys replys...
i wrote a little about that Test disk guy..
anyways..i hope you can read my bable..
i thought maybe i should reply to this message you wrote..
and see if your still gona try and help me out here..
i have e-mails from that Test disk developer guy..
and the log things when i ran it..
i wrote a lil bit about it in a post here..
anyways..
i putting this post to see if your still here and wanting to try and help me
out here..
im gona reply to one of PC's post too..
talk to you later buddy...

[mikesmith]

hey PC whats up buddy..
im not use to using this fourm..
and i didnt know there was a more button..
to see the rest of the post..
i wrote a lil bit about that in another post..
anways i don't wana type alot and keep babbling..
hope to hear from you so i can know your still gona try and help me out
here...
yeah im not use to this fourm at all...
talk to you later buddy...

[PCR]

mikesmith wrote:
| hey PC whats up buddy..
| im not use to using this fourm..
| and i didnt know there was a more button..
| to see the rest of the post..
| i wrote a lil bit about that in another post..
| anways i don't wana type alot and keep babbling..
| hope to hear from you so i can know your still gona try and help me
| out here...
| yeah im not use to this fourm at all...
| talk to you later buddy...

Yea, we're here... click that MORE button! Though it's possibly best to
stick with Richards, post everything you recall the TESTDISK guy said to
do. Post the results you've accumulated. Also...

(1) Was it determined that the Qantum Fireball Hard Drive had
MaxBlast unnecessarily installed?
(2) Is the TESTDISK guy trying to uninstall it or to reinstall it?
What is the plan he came up with?
(3) Maybe post what MBRWork shows for the MBR on the Fireball.
What partition type does it show-- 55...?...

http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
Partition types
..........Quote.....................
55 EZ-Drive

EZ-Drive is another disk manager (by MicroHouse, 1992). Linux kernel
versions older than 1.3.29 do not coexist with EZD. (On 990323
MicroHouse International was acquired by EarthWeb; MicroHouse Solutions
split off and changed its name into StorageSoft. MicroHouse Development
split off and changed its name into ImageCast. It is StorageSoft that
now markets EZDrive and DrivePro.)
..........EOQ.......................

http://www.terabyteunlimited.com/utilities.html MBRWork
Free MBR utility.

Here is what MBRWork shows for my slave drive, run from a Windows DOS
box.
"c" is a primary FAT32 partition, & "f" is an extended partition...

-----------------------------------------------------------
MBR Partition Information (HD1):
-----------------------------------------------------------
¦ 0: ¦ 0 ¦ 1 1 0 ¦ c ¦ 239 63 1021 ¦ 63 ¦ 16374897 ¦
¦ 1: ¦ 0 ¦ 239 63 1021 ¦ f ¦ 239 63 1021 ¦ 16374960 ¦ 61795440 ¦
¦ 2: ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 ¦
¦ 3: ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 0 0 ¦ 0 ¦ 0 ¦
----------------------------------------------------------------------

Here is what that URL says about them. Obviously, it was written before
the advent of Win98, though...

0c WIN95 OSR2 FAT32, LBA-mapped
Extended-INT13 equivalent of 0b.

0f WIN95: Extended partition, LBA-mapped
Windows 95 uses 0e and 0f as the extended-INT13 equivalents of 06 and
05. For the problems this causes, see Possible data loss with LBA and
INT13 extensions. (Especially when going back and forth between MSDOS
and Windows 95, strange things may happen with a type 0e or 0f
partition.) Windows NT does not recognize the four W95 types 0b, 0c, 0e,
0f ( Win95 Partition Types Not Recognized by Windows NT). DRDOS 7.03
does not support this type (but DRDOS 7.04 does).

To show yours...

(1) Download & unzip MBRWork into...
C:\WINDOWS\COMMAND
(It's meant to run from DOS.)
(2) "START button, Programs, MS-DOS Prompt"
(3) Enter... MBRWork
(4) Enter... 7 (Change active hard drive)
(5) Enter... 1
(This presumes the Fireball is either a slave or a secondary
master & it is the only hard drive other than the primary master.)
(6) Use the DOS box's MARK & COPY buttons to get highlighted
text into the Clipboard. Highlight what you need with the mouse.
(7) Enter... E (Exit MBRWork).
(8) Post the text to us. The 4th column will hold the partition type
identifier.


........Quote... MBRWork Readme .......
MBRWork - Freeware utility to perform some common and uncommon MBR
and disk functions. Provided As-Is.

It can perform the following:

1 - Backup the first track on a hard drive.
2 - Restore the backup file.
3 - Reset the EMBR area to all zeros.
4 - Reset the MBR are to all zeros.
5 - Install standard MBR Code
6 - Set a partition active (avail on the command line too)
7 - Work with multiple hard drives.
8 - Remove EZ-Drive (You must boot directly to a diskette [bypassing
ez-drive] for this option to show)
9 - Edit MBR partition entry values.
A - If no partitions exist in the MBR and no EMBR exists then this
option will allow you to recover lost FAT, HPFS, NTFS, and
Extended partitions.
C - Capture up to 64 disk sectors to a file.
R - Restore up to 64 disk sectors from a file. This feature should only
be used by those who completely understand what they are doing!
T - Transfer/Copy sectors from disk to disk. This feature should only
be used by those who completely understand what they are doing!
P - Compare sectors.
......EOQ... MBRWork Readme .............

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

[mikesmith]

PART 1 OF 3


HEY PC
whats up buddy..
man this is making me crazy..
i just want to get my data off this HD..
god this would be so much easier if i could just talk to someone..
insted of typing a book here..
im so sorry about having to type so much for you to read..

and i have no idea if any of this will make any sense..
or let you know anything you might need to know..

i think i messed up having the Developer of the program TESTDISK help me..
i kinda really think this guy does not speek good english..
and is greman or something...
and he might have made things worse then they really were...
he doesnt seem to give all the steps nessary..
like...
i run his program in DOS..
and do what he says to..
but i get to a point where he didnt say anything about the choices i should
pick or choose...or the things i should type in..
you'll see later...

i dont know if you remember what started this all..
i'll give a short history here..

i took a hard drive that was a Slaved hard drive (Data only)..
took it out of one windows 98 system..
and put it in another Win 98 system..
i had done this before alot..
and there never was any problems ever doing this..

i have done this alot with this same hard drive..
in many different other systems..
and there never was any problems ever...

im thinking now that this problem was caused ONLY by the Compaq motherbaord
and the hard drive was fine in the first place!!!!...
and there was nothing ever wrong with this HD..
it was that stupid Compaq motherboard..
because
i fixied the orginal Abit motherboard..
and now the HD is being seen in Windows 98 now..
BUT now all the things the testdisk guy had me do..
i think has made the data unreadable...

i have a hard time talking to this guy..
he dosent really say much..
and he gives me directions to do...
and i get to steps that he dose not say anything about what to do..
like he leaves out steps...
i told him before i even started doing this i knew NOTHING about this program

i'll tell you now PC or who ever..
IM NOT A HARD DRIVE EXPERT..
i have no idea about anything about hard drives..NOTHING..
LBA's..Cylinders..Clusters..
i have NO IDEA what any of these things mean..
its like speeking GREEK to me..
please keep that in mind...

well anyways...
the guy that Developed TESTDISK..
was having me do things i have no idea what i was doing..
im going to put up the e-mails..
and the program log files..
the log files are LONG!!!..
sorry about that..
i dont know if you need to see them or not..

heres my first e-mail...and his responce to it..
at the bottom..
theres like 7-8 e-mails..
and a few log files...


*****FIRST E-MAIL***********
-------------------------------------------------------------------------------

On Tue, 30 Sep 2008, Mike Smith wrote:

> will try to make short as possible please let me know any information you may need to try and help me....thank you so much
>
> old mother board Died(Abit kt7-raid *2 Hard drives on it*)Windows 98SE OS
>
> built a new system using motherboard a friend gave me off a COMPAQ 5000US
> installed Windows 98se on it...working fine..typing this letter to you using it now..
>
> after i installed my OS on my new build.
> i went to put my second hard drive back in
> (2nd hard drive was ALWAYS for data only storage *SLAVED*)
> system would not boot then...
> pulled second hard drive back out..
> system started up fine...
> tried putting the slaved hard drive back in onto the second IDE cable
> system booted up fine..*BUT* NO D: drive being seen in windows..
>
> i didn't do anything to this hard drive..i only pulled it from one working Windows 98SE system and put it into another working system

****HERES HIS RESPONCE....******

Go in Advanced, choose Boot, RebuildBS, List, Quit
and send me the new log file

Christophe

-------------------------------------------------------------------

HERES THE first LOG FILE....

------------------------------------------------------------------
Tue Sep 30 10:09:30 2008
Command line: TestDisk

TestDisk 6.10, Data Recovery Utility, July 2008
Christophe GRENIER >
http://www.cgsecurity.org
OS: DOS
Compiler: djgpp 2.3 - Jul 17 2008 15:48:02
ext2fs lib: 1.41.0, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: none
Disk 80 - 7911 MB / 7545 MiB - CHS 1022 240 63
Disk 80 Enhanced BIOS 2.1 / EDD-1.1 - R/W/I - Identify
Computes C from number of sectors
LBA 26712000, computed 26711370 (CHS=28265,14,63)
hd_identify_enh_bios
Disk 80 - 13 GB / 12 GiB - CHS 28266 15 63
LBA size=26712000
Disk 81 - 7786 MB / 7425 MiB - CHS 1022 240 62
Disk 81 Enhanced BIOS 2.1 / EDD-1.1 - R/W/I - Identify
Computes C from number of sectors
LBA 39876480, computed 39875610 (CHS=42876,14,62)
hd_identify_enh_bios
Disk 81 - 20 GB / 19 GiB - CHS 42877 15 62
LBA size=39876480
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
Hard disk list
Disk 80 - 13 GB / 12 GiB - CHS 1766 240 63, sector size=512
Disk 81 - 20 GB / 19 GiB - CHS 2679 240 62, sector size=512

Partition table type (auto): Intel
Disk 81 - 20 GB / 19 GiB
Partition table type: Intel

Analyse Disk 81 - 20 GB / 19 GiB - CHS 2679 240 62
Geometry from i386 MBR: head=127 sector=63
BAD_RS LBA=62 61


test_FAT()
1 * FAT32 LBA 0 1 1 2679 158 12 39873266
sector_size 0
cluster_size 0
reserved 0
fats 0
dir_entries 0
sectors 0
media 00
fat_length 0
secs_track 0
heads 0
hidden 0
total_sect 0
check_part_i386 failed for partition type 0C
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=1
Current partition structure:
Invalid FAT boot sector
1 * FAT32 LBA 0 1 1 2679 158 12 39873266
1 * FAT32 LBA 0 1 1 2679 158 12 39873266

Warning: Bad starting sector (CHS and LBA don't match)
Ask the user for vista mode
Allow partial last cylinder : No
search_vista_part: 0

search_part()
Disk 81 - 20 GB / 19 GiB - CHS 2679 240 62
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk

Results

interface_write()

No partition found or selected for recovery

search_part()
Disk 81 - 20 GB / 19 GiB - CHS 2679 240 62
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk

Results

interface_write()

No partition found or selected for recovery
simulate write!

write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition

TestDisk exited normally.


------------------------------------------------------------------
------------------------------------------------------------------

********HERS MY Second E-Mail TO Him***********

----------------------------------------------

On Thu, 2 Oct 2008, Mike Smith wrote:

> hey Christophe
> i did what you said to do below
> but God i hope i didnt do anything wrong...
> heres what i did..
>
> i went to
> Advanced, then choose Boot, then RebuildBS,
>
> *But when i went to choose where it said LIST*..
> *there was no option* to choose LIST from..
>
> So i just hit Quit Quit Quit untill i exited TestDisk..
> then i copied that Log file and renamed it to (Testdisk.log number 1)
> and saved it..
>
> I thought i Did something Wrong since there was no list option.

*****HERES HIS RESPONCE***********

The first log file shows you have choose List after RebuildBS.
The second log shows the partition table has been corrupted since.

Run TestDisk, Geometry, set 255 heads, Analyse, Quick Search,
there should be a FAT32 LBA starting at 0 1 1 and using the whole disk
if you don't see it, use 'a' to manually add it,be carefull, the
partition start at 0 1 1, not 0 0 1.
Set the partition as *(bootable).
On next screen, choose Write, confirm, quit and send me the new log
file.

Christophe

------------------------------------------------------------------
-----------------------------------------------------------------

[mikesmith]

PART 2 of 3

*********** HERES THE LOG FILES ****************

Thu Oct 2 05:27:27 2008
Command line: TestDisk

TestDisk 6.10, Data Recovery Utility, July 2008
Christophe GRENIER >
http://www.cgsecurity.org
OS: DOS
Compiler: djgpp 2.3 - Jul 17 2008 15:48:02
ext2fs lib: 1.41.0, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: none
Disk 80 - 7911 MB / 7545 MiB - CHS 1022 240 63
Disk 80 Enhanced BIOS 2.1 / EDD-1.1 - R/W/I - Identify
Computes C from number of sectors
LBA 26712000, computed 26711370 (CHS=28265,14,63)
hd_identify_enh_bios
Disk 80 - 13 GB / 12 GiB - CHS 28266 15 63
LBA size=26712000
Disk 81 - 7911 MB / 7545 MiB - CHS 1022 240 63
Disk 81 Enhanced BIOS 2.1 / EDD-1.1 - R/W/I - Identify
Computes C from number of sectors
LBA 39876480, computed 39876165 (CHS=42196,14,63)
hd_identify_enh_bios
Disk 81 - 20 GB / 19 GiB - CHS 42197 15 63
LBA size=39876480
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
Hard disk list
Disk 80 - 13 GB / 12 GiB - CHS 1766 240 63, sector size=512
Disk 81 - 20 GB / 19 GiB - CHS 2637 240 63, sector size=512

Partition table type (auto): Intel
Disk 81 - 20 GB / 19 GiB
Partition table type: Intel
disk_read_aux: Don't read after the end of the disk

Interface Advanced
Geometry from i386 MBR: head=255 sector=63
FAT32 at 0/1/1
Info: size boot_sector 39873267, partition 39873267
FAT1 : 32-9761
FAT2 : 9762-19491
start_rootdir : 19492 root cluster : 2
Data : 19492-39873251
sectors : 39873267
cluster_size : 32
no_of_cluster : 1245430 (2 - 1245431)
fat_length 9730 calculated 9730
heads/cylinder 255 (FAT) != 240 (HD)
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=2
1 * FAT32 LBA 0 1 1 2637 29 63 39873267 [DSK1_VOL1]
FAT32, 20 GB / 19 GiB

fat32_boot_sector
1 * FAT32 LBA 0 1 1 2637 29 63 39873267 [DSK1_VOL1]
FAT32, 20 GB / 19 GiB
FAT32 at 0/1/1
Info: size boot_sector 39873267, partition 39873267
FAT1 : 32-9761
FAT2 : 9762-19491
start_rootdir : 19492 root cluster : 2
Data : 19492-39873251
sectors : 39873267
cluster_size : 32
no_of_cluster : 1245430 (2 - 1245431)
fat_length 9730 calculated 9730
FAT differs, FAT sectors=304-312/9730
heads/cylinder 255 (FAT) != 240 (HD)
FAT32 at 0/1/1
Info: size boot_sector 39873267, partition 39873267
FAT1 : 32-9761
FAT2 : 9762-19491
start_rootdir : 19492 root cluster : 2
Data : 19492-39873251
sectors : 39873267
cluster_size : 32
no_of_cluster : 1245430 (2 - 1245431)
fat_length 9730 calculated 9730
FAT differs, FAT sectors=304-312/9730
heads/cylinder 255 (FAT) != 240 (HD)
Boot sector
Warning: Incorrect number of heads/cylinder 255 (FAT) != 240 (HD)
OK

Backup boot sector
Warning: Incorrect number of heads/cylinder 255 (FAT) != 240 (HD)
OK

Sectors are identical.

A valid FAT Boot sector must be present in order to access
any data; even if the partition is not bootable.

1 * FAT32 LBA 0 1 1 2637 29 63 39873267 [DSK1_VOL1]
FAT32, 20 GB / 19 GiB
rebuild_FAT_BS p_fat12 0, p_fat16 0, p_fat32 1
fat_find_type(max_offset=311573, p_fat12=0, p_fat16=0, p_fat32=1, debug=1,
dump_ind=0)
FAT32 at 32(0/1/33), nbr=2169
FAT32 at 688(0/11/59), nbr=1
FAT32 at 689(0/11/60), nbr=1
FAT32 at 690(0/11/61), nbr=1
FAT32 at 691(0/11/62), nbr=1
FAT32 at 692(0/11/63), nbr=1
FAT32 at 693(0/12/1), nbr=1
FAT32 at 694(0/12/2), nbr=1
FAT32 at 695(0/12/3), nbr=1
FAT32 at 696(0/12/4), nbr=1
FAT32 at 697(0/12/5), nbr=1
FAT32 at 698(0/12/6), nbr=1
FAT32 at 699(0/12/7), nbr=1
FAT32 at 700(0/12/8), nbr=1
FAT32 at 701(0/12/9), nbr=1
FAT32 at 702(0/12/10), nbr=1
FAT32 at 703(0/12/11), nbr=1
FAT32 at 704(0/12/12), nbr=1
FAT32 at 705(0/12/13), nbr=1
FAT32 at 706(0/12/14), nbr=1
FAT32 at 707(0/12/15), nbr=1
FAT32 at 708(0/12/16), nbr=1
FAT32 at 709(0/12/17), nbr=1
FAT32 at 710(0/12/18), nbr=1
FAT32 at 711(0/12/19), nbr=1
FAT32 at 712(0/12/20), nbr=1
FAT32 at 713(0/12/21), nbr=1
FAT32 at 714(0/12/22), nbr=1
FAT32 at 715(0/12/23), nbr=1
FAT32 at 716(0/12/24), nbr=1
FAT32 at 807(0/13/52), nbr=1
FAT32 at 808(0/13/53), nbr=1
FAT32 at 809(0/13/54), nbr=1
FAT32 at 810(0/13/55), nbr=1
FAT32 at 811(0/13/56), nbr=1
FAT32 at 812(0/13/57), nbr=1
FAT32 at 813(0/13/58), nbr=1
FAT32 at 814(0/13/59), nbr=1
FAT32 at 855(0/14/37), nbr=1
FAT32 at 856(0/14/38), nbr=1
FAT32 at 857(0/14/39), nbr=1
FAT32 at 858(0/14/40), nbr=1
FAT32 at 859(0/14/41), nbr=1
FAT32 at 860(0/14/42), nbr=1
FAT32 at 861(0/14/43), nbr=1
FAT32 at 862(0/14/44), nbr=1
FAT32 at 863(0/14/45), nbr=1
FAT32 at 864(0/14/46), nbr=1
FAT32 at 865(0/14/47), nbr=1
FAT32 at 866(0/14/48), nbr=1
FAT32 at 867(0/14/49), nbr=1
FAT32 at 868(0/14/50), nbr=1
FAT32 at 869(0/14/51), nbr=1
FAT32 at 870(0/14/52), nbr=1
FAT32 at 871(0/14/53), nbr=1
FAT32 at 872(0/14/54), nbr=1
FAT32 at 873(0/14/55), nbr=1
FAT32 at 874(0/14/56), nbr=1
FAT32 at 875(0/14/57), nbr=1
FAT32 at 876(0/14/58), nbr=1
FAT32 at 877(0/14/59), nbr=1
FAT32 at 878(0/14/60), nbr=1
FAT32 at 879(0/14/61), nbr=1
FAT32 at 880(0/14/62), nbr=1
FAT32 at 881(0/14/63), nbr=1
FAT32 at 882(0/15/1), nbr=1
FAT32 at 883(0/15/2), nbr=1
FAT32 at 884(0/15/3), nbr=1
FAT32 at 885(0/15/4), nbr=1
FAT32 at 886(0/15/5), nbr=1
FAT32 at 887(0/15/6), nbr=1
FAT32 at 888(0/15/7), nbr=1
FAT32 at 889(0/15/8), nbr=1
FAT32 at 890(0/15/9), nbr=1
FAT32 at 891(0/15/10), nbr=1
FAT32 at 892(0/15/11), nbr=1
FAT32 at 893(0/15/12), nbr=1
FAT32 at 544(0/9/41), nbr=1673
FAT32 at 800(0/13/45), nbr=62
FAT32 at 31(0/1/32), nbr=104
FAT32 at 288(0/5/37), nbr=40
FAT32 at 543(0/9/40), nbr=76
FAT32 at 799(0/13/44), nbr=2
FAT32 at 287(0/5/36), nbr=1
FAT32 at 9762(0/155/61), nbr=1692
FAT32 at 10018(0/160/2), nbr=44
FAT32 at 9761(0/155/60), nbr=50
FAT32 at 10274(0/164/6), nbr=1811
FAT32 at 10530(0/168/10), nbr=68
FAT32 at 10273(0/164/5), nbr=72
FAT32 at 10529(0/168/9), nbr=3
FAT32 at 10017(0/160/1), nbr=5
FAT32 at 10311(0/164/43), nbr=1
FAT32 at 188690(12/116/6), nbr=1
FAT32 at 193032(12/185/1), nbr=1
FAT32 at 193033(12/185/2), nbr=1
FAT32 at 193034(12/185/3), nbr=1
FAT32 at 193035(12/185/4), nbr=1
FAT32 at 193036(12/185/5), nbr=1
FAT32 at 193038(12/185/7), nbr=1
FAT32 at 193048(12/185/17), nbr=1
FAT32 at 193050(12/185/19), nbr=1
FAT32 at 193056(12/185/25), nbr=1
FAT32 at 193057(12/185/26), nbr=1
FAT32 at 193059(12/185/28), nbr=1
FAT32 at 193060(12/185/29), nbr=1
FAT32 at 193061(12/185/30), nbr=1
FAT32 at 193062(12/185/31), nbr=1
FAT32 at 193063(12/185/32), nbr=1
FAT32 at 193065(12/185/34), nbr=1
FAT32 at 193066(12/185/35), nbr=1
FAT32 at 193067(12/185/36), nbr=1
FAT32 at 193068(12/185/37), nbr=1
FAT32 at 193074(12/185/43), nbr=1
FAT32 at 193082(12/185/51), nbr=1
FAT32 at 193098(12/186/4), nbr=1
FAT32 at 193100(12/186/6), nbr=1
FAT32 at 193107(12/186/13), nbr=1
FAT32 at 193109(12/186/15), nbr=1
FAT32 at 193110(12/186/16), nbr=1
FAT32 at 277905(18/92/13), nbr=1
FAT32 at 277906(18/92/14), nbr=1
FAT32 at 277907(18/92/15), nbr=1
FAT32 at 280240(18/129/17), nbr=1
FAT32 at 287088(18/237/61), nbr=1
FAT32 at 287102(18/238/12), nbr=1
FAT32 at 287103(18/238/13), nbr=1
FAT32 at 287104(18/238/14), nbr=1
FAT32 at 287105(18/238/15), nbr=1
FAT32 at 287106(18/238/16), nbr=1
FAT32 at 287393(19/2/51), nbr=1
FAT32 at 288223(19/15/62), nbr=1
FAT32 at 288237(19/16/13), nbr=1
FAT32 at 288298(19/17/11), nbr=1
FAT32 at 288710(19/23/45), nbr=1
FAT32 at 288730(19/24/2), nbr=1
FAT32 at 288898(19/26/44), nbr=1
FAT32 at 289235(19/32/3), nbr=1
FAT32 at 289339(19/33/44), nbr=1
FAT32 at 289714(19/39/41), nbr=1
FAT32 at 289808(19/41/9), nbr=1
FAT32 at 289810(19/41/11), nbr=1
FAT32 at 289897(19/42/35), nbr=1
FAT32 at 289904(19/42/42), nbr=1
FAT32 at 289905(19/42/43), nbr=1
FAT32 at 289918(19/42/56), nbr=1
FAT32 at 289919(19/42/57), nbr=1
FAT32 at 289920(19/42/58), nbr=1
FAT32 at 289921(19/42/59), nbr=1
FAT32 at 289922(19/42/60), nbr=1
FAT32 at 289928(19/43/3), nbr=1
FAT32 at 289929(19/43/4), nbr=1
FAT32 at 289930(19/43/5), nbr=1
FAT32 at 289931(19/43/6), nbr=1
FAT32 at 289932(19/43/7), nbr=1
FAT32 at 290022(19/44/34), nbr=1
FAT32 at 290023(19/44/35), nbr=1
FAT32 at 290024(19/44/36), nbr=1
FAT32 at 290025(19/44/37), nbr=1
FAT32 at 290031(19/44/43), nbr=1
FAT32 at 290032(19/44/44), nbr=1
FAT32 at 290033(19/44/45), nbr=1
FAT32 at 290034(19/44/46), nbr=1
FAT32 at 290035(19/44/47), nbr=1
FAT32 at 290036(19/44/48), nbr=1
FAT32 at 290037(19/44/49), nbr=1
FAT32 at 290038(19/44/50), nbr=1
FAT32 at 290039(19/44/51), nbr=1
FAT32 at 290040(19/44/52), nbr=1
FAT32 at 290041(19/44/53), nbr=1
FAT32 at 290042(19/44/54), nbr=1
FAT32 at 290043(19/44/55), nbr=1
FAT32 at 290044(19/44/56), nbr=1
FAT32 at 290045(19/44/57), nbr=1
FAT32 at 290046(19/44/58), nbr=1
FAT32 at 290047(19/44/59), nbr=1
FAT32 at 290048(19/44/60), nbr=1
FAT32 at 290049(19/44/61), nbr=1
FAT32 at 290050(19/44/62), nbr=1
FAT32 at 290051(19/44/63), nbr=1
FAT32 at 290052(19/45/1), nbr=1
FAT32 at 290053(19/45/2), nbr=1
FAT32 at 290054(19/45/3), nbr=1
FAT32 at 290055(19/45/4), nbr=1
FAT32 at 290056(19/45/5), nbr=1
FAT32 at 290057(19/45/6), nbr=1
FAT32 at 290058(19/45/7), nbr=1
FAT32 at 290059(19/45/8), nbr=1
FAT32 at 290060(19/45/9), nbr=1
FAT32 at 290061(19/45/10), nbr=1
FAT32 at 290062(19/45/11), nbr=1
FAT32 at 290063(19/45/12), nbr=1
FAT32 at 290064(19/45/13), nbr=1
FAT32 at 290065(19/45/14), nbr=1
FAT32 at 290066(19/45/15), nbr=1
FAT32 at 290067(19/45/16), nbr=1
FAT32 at 290068(19/45/17), nbr=1
FAT32 at 290069(19/45/18), nbr=1
FAT32 at 290070(19/45/19), nbr=1
FAT32 at 290071(19/45/20), nbr=1
FAT32 at 290072(19/45/21), nbr=1
FAT32 at 290073(19/45/22), nbr=1
FAT32 at 290074(19/45/23), nbr=1
FAT32 at 290075(19/45/24), nbr=1
FAT32 at 290076(19/45/25), nbr=1
FAT32 at 290077(19/45/26), nbr=1
FAT32 at 290078(19/45/27), nbr=1
FAT32 at 290079(19/45/28), nbr=1
FAT32 at 290080(19/45/29), nbr=1
FAT32 at 290081(19/45/30), nbr=1
FAT32 at 290082(19/45/31), nbr=1
FAT32 at 290083(19/45/32), nbr=1
FAT32 at 290084(19/45/33), nbr=1
FAT32 at 290085(19/45/34), nbr=1
FAT32 at 290086(19/45/35), nbr=1
FAT32 at 290087(19/45/36), nbr=1
FAT32 at 290088(19/45/37), nbr=1
FAT32 at 290089(19/45/38), nbr=1
FAT32 at 290090(19/45/39), nbr=1
FAT32 at 290091(19/45/40), nbr=1
FAT32 at 290092(19/45/41), nbr=1
FAT32 at 290093(19/45/42), nbr=1
FAT32 at 290094(19/45/43), nbr=1
FAT32 at 290095(19/45/44), nbr=1
FAT32 at 290096(19/45/45), nbr=1
FAT32 at 290097(19/45/46), nbr=1
FAT32 at 290098(19/45/47), nbr=1
FAT32 at 290099(19/45/48), nbr=1
FAT32 at 290100(19/45/49), nbr=1
FAT32 at 290101(19/45/50), nbr=1
FAT32 at 290102(19/45/51), nbr=1
FAT32 at 290103(19/45/52), nbr=1
FAT32 at 290104(19/45/53), nbr=1
FAT32 at 290105(19/45/54), nbr=1
FAT32 at 290106(19/45/55), nbr=1
FAT32 at 290107(19/45/56), nbr=1
FAT32 at 290108(19/45/57), nbr=1
FAT32 at 290109(19/45/58), nbr=1
FAT32 at 290110(19/45/59), nbr=1
FAT32 at 290111(19/45/60), nbr=1
FAT32 at 290112(19/45/61), nbr=1
FAT32 at 290113(19/45/62), nbr=1
FAT32 at 290114(19/45/63), nbr=1
FAT32 at 290115(19/46/1), nbr=1
FAT32 at 290116(19/46/2), nbr=1
FAT32 at 290117(19/46/3), nbr=1
FAT32 at 290118(19/46/4), nbr=1
FAT32 at 290119(19/46/5), nbr=1
FAT32 at 290120(19/46/6), nbr=1
FAT32 at 290121(19/46/7), nbr=1
FAT32 at 290122(19/46/8), nbr=1
FAT32 at 290123(19/46/9), nbr=1
FAT32 at 290124(19/46/10), nbr=1
FAT32 at 290125(19/46/11), nbr=1
FAT32 at 290126(19/46/12), nbr=1
FAT32 at 290127(19/46/13), nbr=1
FAT32 at 290128(19/46/14), nbr=1
FAT32 at 290129(19/46/15), nbr=1
FAT32 at 290130(19/46/16), nbr=1
FAT32 at 290131(19/46/17), nbr=1
FAT32 at 290132(19/46/18), nbr=1
FAT32 at 290133(19/46/19), nbr=1
FAT32 at 290134(19/46/20), nbr=1
FAT32 at 290135(19/46/21), nbr=1
FAT32 at 290136(19/46/22), nbr=1
FAT32 at 290137(19/46/23), nbr=1
FAT32 at 290138(19/46/24), nbr=1
FAT32 at 290139(19/46/25), nbr=1
FAT32 at 290140(19/46/26), nbr=1
FAT32 at 290141(19/46/27), nbr=1
FAT32 at 290142(19/46/28), nbr=1
FAT32 at 290143(19/46/29), nbr=1
FAT32 at 290144(19/46/30), nbr=1
FAT32 at 290145(19/46/31), nbr=1
FAT32 at 290146(19/46/32), nbr=1
FAT32 at 290147(19/46/33), nbr=1
FAT32 at 290148(19/46/34), nbr=1
FAT32 at 290149(19/46/35), nbr=1
FAT32 at 290150(19/46/36), nbr=1
FAT32 at 290151(19/46/37), nbr=1
FAT32 at 290152(19/46/38), nbr=1
FAT32 at 290153(19/46/39), nbr=1
FAT32 at 290154(19/46/40), nbr=1
FAT32 at 290155(19/46/41), nbr=1
FAT32 at 290156(19/46/42), nbr=1
FAT32 at 290157(19/46/43), nbr=1
FAT32 at 290158(19/46/44), nbr=1
FAT32 at 290159(19/46/45), nbr=1
FAT32 at 290160(19/46/46), nbr=1
FAT32 at 290161(19/46/47), nbr=1
FAT32 at 290162(19/46/48), nbr=1
FAT32 at 290163(19/46/49), nbr=1
FAT32 at 290164(19/46/50), nbr=1
FAT32 at 290165(19/46/51), nbr=1
FAT32 at 290166(19/46/52), nbr=1
FAT32 at 290167(19/46/53), nbr=1
FAT32 at 290168(19/46/54), nbr=1
FAT32 at 290169(19/46/55), nbr=1
FAT32 at 290170(19/46/56), nbr=1
FAT32 at 290171(19/46/57), nbr=1
FAT32 at 290172(19/46/58), nbr=1
FAT32 at 290173(19/46/59), nbr=1
FAT32 at 290174(19/46/60), nbr=1
FAT32 at 290175(19/46/61), nbr=1
FAT32 at 290176(19/46/62), nbr=1
FAT32 at 290177(19/46/63), nbr=1
FAT32 at 290178(19/47/1), nbr=1
FAT32 at 290179(19/47/2), nbr=1
FAT32 at 290180(19/47/3), nbr=1
FAT32 at 290181(19/47/4), nbr=1
FAT32 at 290182(19/47/5), nbr=1
FAT32 at 290183(19/47/6), nbr=1
FAT32 at 290184(19/47/7), nbr=1
FAT32 at 290185(19/47/8), nbr=1
FAT32 at 290186(19/47/9), nbr=1
FAT32 at 290187(19/47/10), nbr=1
FAT32 at 290188(19/47/11), nbr=1
FAT32 at 290189(19/47/12), nbr=1
FAT32 at 290190(19/47/13), nbr=1
FAT32 at 290191(19/47/14), nbr=1
FAT32 at 290192(19/47/15), nbr=1
FAT32 at 290193(19/47/16), nbr=1
FAT32 at 290194(19/47/17), nbr=1
FAT32 at 290195(19/47/18), nbr=1
FAT32 at 290196(19/47/19), nbr=1
FAT32 at 290197(19/47/20), nbr=1
FAT32 at 290198(19/47/21), nbr=1
FAT32 at 290199(19/47/22), nbr=1
FAT32 at 290200(19/47/23), nbr=1
FAT32 at 290201(19/47/24), nbr=1
FAT32 at 290202(19/47/25), nbr=1
FAT32 at 290203(19/47/26), nbr=1
FAT32 at 290204(19/47/27), nbr=1
FAT32 at 290205(19/47/28), nbr=1
FAT32 at 290206(19/47/29), nbr=1
FAT32 at 290207(19/47/30), nbr=1
FAT32 at 290208(19/47/31), nbr=1
FAT32 at 290209(19/47/32), nbr=1
FAT32 at 290210(19/47/33), nbr=1
FAT32 at 290211(19/47/34), nbr=1
FAT32 at 290212(19/47/35), nbr=1
FAT32 at 290213(19/47/36), nbr=1
FAT32 at 290214(19/47/37), nbr=1
FAT32 at 290215(19/47/38), nbr=1
FAT32 at 290216(19/47/39), nbr=1
FAT32 at 290217(19/47/40), nbr=1
FAT32 at 290218(19/47/41), nbr=1
FAT32 at 290219(19/47/42), nbr=1
FAT32 at 290220(19/47/43), nbr=1
FAT32 at 290221(19/47/44), nbr=1
FAT32 at 290222(19/47/45), nbr=1
FAT32 at 290223(19/47/46), nbr=1
FAT32 at 290224(19/47/47), nbr=1
FAT32 at 290225(19/47/48), nbr=1
FAT32 at 290226(19/47/49), nbr=1
FAT32 at 290227(19/47/50), nbr=1
FAT32 at 290228(19/47/51), nbr=1
FAT32 at 290229(19/47/52), nbr=1
FAT32 at 290230(19/47/53), nbr=1
FAT32 at 290231(19/47/54), nbr=1
FAT32 at 290232(19/47/55), nbr=1
FAT32 at 290233(19/47/56), nbr=1
FAT32 at 290234(19/47/57), nbr=1
FAT32 at 290235(19/47/58), nbr=1
FAT32 at 290236(19/47/59), nbr=1
FAT32 at 290237(19/47/60), nbr=1
FAT32 at 290238(19/47/61), nbr=1
FAT32 at 290239(19/47/62), nbr=1
FAT32 at 290240(19/47/63), nbr=1
FAT32 at 290241(19/48/1), nbr=1
FAT32 at 290242(19/48/2), nbr=1
FAT32 at 290243(19/48/3), nbr=1
FAT32 at 290244(19/48/4), nbr=1
FAT32 at 290245(19/48/5), nbr=1
FAT32 at 290246(19/48/6), nbr=1
FAT32 at 290247(19/48/7), nbr=1
FAT32 at 290248(19/48/8), nbr=1
FAT32 at 290249(19/48/9), nbr=1
FAT32 at 290250(19/48/10), nbr=1
FAT32 at 290251(19/48/11), nbr=1
FAT32 at 290252(19/48/12), nbr=1
FAT32 at 290253(19/48/13), nbr=1
FAT32 at 290254(19/48/14), nbr=1
FAT32 at 290255(19/48/15), nbr=1
FAT32 at 290256(19/48/16), nbr=1
FAT32 at 290257(19/48/17), nbr=1
FAT32 at 290258(19/48/18), nbr=1
FAT32 at 290259(19/48/19), nbr=1
FAT32 at 290260(19/48/20), nbr=1
FAT32 at 290261(19/48/21), nbr=1
FAT32 at 290262(19/48/22), nbr=1
FAT32 at 290263(19/48/23), nbr=1
FAT32 at 290264(19/48/24), nbr=1
FAT32 at 290265(19/48/25), nbr=1
FAT32 at 290266(19/48/26), nbr=1
FAT32 at 290267(19/48/27), nbr=1
FAT32 at 290268(19/48/28), nbr=1
FAT32 at 290269(19/48/29), nbr=1
FAT32 at 290270(19/48/30), nbr=1
FAT32 at 290271(19/48/31), nbr=1
FAT32 at 290272(19/48/32), nbr=1
FAT32 at 290273(19/48/33), nbr=1
FAT32 at 290274(19/48/34), nbr=1
FAT32 at 290275(19/48/35), nbr=1
FAT32 at 290276(19/48/36), nbr=1
FAT32 at 290277(19/48/37), nbr=1
FAT32 at 290278(19/48/38), nbr=1
FAT32 at 290279(19/48/39), nbr=1
FAT32 at 290280(19/48/40), nbr=1
FAT32 at 290281(19/48/41), nbr=1
FAT32 at 290282(19/48/42), nbr=1
FAT32 at 290283(19/48/43), nbr=1
FAT32 at 290284(19/48/44), nbr=1
FAT32 at 290285(19/48/45), nbr=1
FAT32 at 290286(19/48/46), nbr=1
FAT32 at 290287(19/48/47), nbr=1
FAT32 at 290288(19/48/48), nbr=1
FAT32 at 290289(19/48/49), nbr=1
FAT32 at 290290(19/48/50), nbr=1
FAT32 at 290291(19/48/51), nbr=1
FAT32 at 290292(19/48/52), nbr=1
FAT32 at 290293(19/48/53), nbr=1
FAT32 at 290294(19/48/54), nbr=1
FAT32 at 290295(19/48/55), nbr=1
FAT32 at 290296(19/48/56), nbr=1
FAT32 at 290297(19/48/57), nbr=1
FAT32 at 290298(19/48/58), nbr=1
FAT32 at 290299(19/48/59), nbr=1
FAT32 at 290300(19/48/60), nbr=1
FAT32 at 290301(19/48/61), nbr=1
FAT32 at 290302(19/48/62), nbr=1
FAT32 at 290303(19/48/63), nbr=1
FAT32 at 290304(19/49/1), nbr=1
FAT32 at 290305(19/49/2), nbr=1
FAT32 at 290306(19/49/3), nbr=1
FAT32 at 290307(19/49/4), nbr=1
FAT32 at 294002(19/107/45), nbr=1
FAT32 at 294026(19/108/6), nbr=1
FAT32 at 294036(19/108/16), nbr=1
FAT32 at 294042(19/108/22), nbr=1
FAT32 at 294043(19/108/23), nbr=1
FAT32 at 294047(19/108/27), nbr=1
FAT32 at 294054(19/108/34), nbr=1
FAT32 at 294055(19/108/35), nbr=1
FAT32 at 294058(19/108/38), nbr=1
FAT32 at 294062(19/108/42), nbr=1
FAT32 at 294063(19/108/43), nbr=1
FAT32 at 294064(19/108/44), nbr=1
FAT32 at 294067(19/108/47), nbr=1
FAT32 at 294068(19/108/48), nbr=1
FAT32 at 294069(19/108/49), nbr=1
FAT32 at 303710(20/21/51), nbr=1
FAT32 at 303711(20/21/52), nbr=1
FAT32 at 303712(20/21/53), nbr=1
FAT32 at 304466(20/33/51), nbr=1
FAT32 at 304487(20/34/9), nbr=1
FAT32 at 304505(20/34/27), nbr=1
FAT32 at 304509(20/34/31), nbr=1
FAT32 at 304525(20/34/47), nbr=1
FAT32 at 304526(20/34/48), nbr=1
FAT32 at 304527(20/34/49), nbr=1
FAT32 at 304529(20/34/51), nbr=1
FAT32 at 304531(20/34/53), nbr=1
first_fat 32, second_fat 544
FAT : 32, reserved=32, fat_length=512
sectors_per_cluster 1024
Can't get cluster size

fat32_boot_sector
1 * FAT32 LBA 0 1 1 2637 29 63 39873267 [DSK1_VOL1]
FAT32, 20 GB / 19 GiB
FAT32 at 0/1/1
Info: size boot_sector 39873267, partition 39873267
FAT1 : 32-9761
FAT2 : 9762-19491
start_rootdir : 19492 root cluster : 2
Data : 19492-39873251
sectors : 39873267
cluster_size : 32
no_of_cluster : 1245430 (2 - 1245431)
fat_length 9730 calculated 9730
FAT differs, FAT sectors=80-88/9730
heads/cylinder 255 (FAT) != 240 (HD)
FAT32 at 0/1/1
Info: size boot_sector 39873267, partition 39873267
FAT1 : 32-9761
FAT2 : 9762-19491
start_rootdir : 19492 root cluster : 2
Data : 19492-39873251
sectors : 39873267
cluster_size : 32
no_of_cluster : 1245430 (2 - 1245431)
fat_length 9730 calculated 9730
FAT differs, FAT sectors=80-88/9730
heads/cylinder 255 (FAT) != 240 (HD)
Boot sector
Warning: Incorrect number of heads/cylinder 255 (FAT) != 240 (HD)
OK

Backup boot sector
Warning: Incorrect number of heads/cylinder 255 (FAT) != 240 (HD)
OK

Sectors are identical.

A valid FAT Boot sector must be present in order to access
any data; even if the partition is not bootable.

FAT: cluster=2(0x2), pos=19555
1 * FAT32 LBA 0 1 1 2637 29 63 39873267 [DSK1_VOL1]
FAT32, 20 GB / 19 GiB
Directory /
5352 drwxr-xr-x 0 0 0 19-Mar-2006 03:47 RECYCLED
5376 drwxr-xr-x 0 0 0 24-Mar-2006 16:22 movie clips
X 5288 drwxr-xr-x 0 0 0 13-Sep-2008 15:53 MASTER
Reinstall for KT7
65342 dr-xr-xr-x 0 0 0 14-May-2006 21:05 a2
20185 -rwxr-xr-x 0 0 64 25-Feb-2008 05:06 Capture.fcb
7861 drwxr-xr-x 0 0 0 21-Apr-2006 22:43 1a
X 5288 drwxr-xr-x 0 0 0 13-Sep-2008 15:53 Reinstall for KT7
53480 dr-xr-xr-x 0 0 0 16-May-2006 10:33 z logos
X 578913 -rwxr-xr-x 0 0 104600000 13-Sep-2008 19:27
Amat-GF02.part1.rar
211658 -r-xr-xr-x 0 0 79188480 22-Jul-2006 22:01 c.avi
65245 drwxr-xr-x 0 0 0 23-May-2006 03:29 barf
65244 drwxr-xr-x 0 0 0 23-May-2006 03:40 mfc42u.dll
7885 drwxr-xr-x 0 0 0 21-Jul-2007 15:01 dont lose my vids
X1213999 -rwxr-xr-x 0 0 109002300 28-Dec-2007 02:44 Amat-GF02.wmv
144486 -rwxr-xr-x 0 0 43391488 2-Sep-2005 00:01 stacy.avi
65233 -rwxr-xr-x 0 0 42 29-Mar-2006 21:59 connection
speed.txt
X 8362 -rwxr-xr-x 0 0 1679538 23-Feb-2006 04:56 white.wmv
65236 drwxr-xr-x 0 0 0 28-May-2006 19:08 WUTemp
743606 -rwxr-xr-x 0 0 47788412 21-Mar-2007 11:03 MAN.mpg
65021 drwxr-xr-x 0 0 0 18-Jun-2006 20:27 sad
499725 -rwxr-xr-x 0 0 427258104 2-Aug-2007 07:13 rain.mpg
65231 drwxr-xr-x 0 0 0 26-May-2006 23:48 install KT7
5290 drwxr-xr-x 0 0 0 24-May-2008 03:46 1
X 276342 dr-xr-xr-x 0 0 0 18-Feb-2007 22:15 rain swim 15
X 44584 -rwxr-xr-x 0 0 471150 26-Jun-2006 11:07 rain p 3.wmv
648380 -rwxr-xr-x 0 0 82121834 24-Jul-2006 21:09 c baby mpg4.avi
76181 drwxr-xr-x 0 0 0 11-Sep-2006 11:00 papport data
166 mhz
20186 drwxr-xr-x 0 0 0 1-Jul-2007 18:31 my recordings
main
77060 -rwxr-xr-x 0 0 2272872 1-Aug-2007 21:32 rain b day 1.mpg
190041 -rwxr-xr-x 0 0 2316328 20-Jul-2007 22:35 5 always.MP3
X 30930 drwxr-xr-x 0 0 0 22-Jun-2008 08:37 u torrent
29178 drwxr-xr-x 0 0 0 11-Feb-2008 11:07 low level tool
X1203595 drwxr-xr-x 0 0 0 11-Sep-2008 23:31 avg7qt.dat

TestDisk exited normally.

-----------------------------------------------------------------------------------
---------------------------------------------------------------------------------

[mikesmith]

PART 3 OF 3

*******HERES THE SECOND LOG FILE he was talking about*****

__________________________________________________ _____________


Thu Oct 2 06:54:08 2008
Command line: TestDisk

TestDisk 6.10, Data Recovery Utility, July 2008
Christophe GRENIER >
http://www.cgsecurity.org
OS: DOS
Compiler: djgpp 2.3 - Jul 17 2008 15:48:02
ext2fs lib: 1.41.0, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: none
Disk 80 - 7911 MB / 7545 MiB - CHS 1022 240 63
Disk 80 Enhanced BIOS 2.1 / EDD-1.1 - R/W/I - Identify
Computes C from number of sectors
LBA 26712000, computed 26711370 (CHS=28265,14,63)
hd_identify_enh_bios
Disk 80 - 13 GB / 12 GiB - CHS 28266 15 63
LBA size=26712000
Disk 81 - 7911 MB / 7545 MiB - CHS 1022 240 63
Disk 81 Enhanced BIOS 2.1 / EDD-1.1 - R/W/I - Identify
Computes C from number of sectors
LBA 39876480, computed 39876165 (CHS=42196,14,63)
hd_identify_enh_bios
Disk 81 - 20 GB / 19 GiB - CHS 42197 15 63
LBA size=39876480
disk_read_aux: Don't read after the end of the disk
disk_read_aux: Don't read after the end of the disk
Hard disk list
Disk 80 - 13 GB / 12 GiB - CHS 1766 240 63, sector size=512
Disk 81 - 20 GB / 19 GiB - CHS 2637 240 63, sector size=512

Partition table type (auto): Intel
Disk 81 - 20 GB / 19 GiB
Partition table type: Intel

Interface Advanced
Geometry from i386 MBR: head=127 sector=63


test_FAT()
1 * FAT32 LBA 0 0 63 2637 29 61 39873266
sector_size 0
cluster_size 0
reserved 0
fats 0
dir_entries 0
sectors 0
media 00
fat_length 0
secs_track 0
heads 0
hidden 0
total_sect 0
check_part_i386 failed for partition type 0C
1 * FAT32 LBA 0 0 63 2637 29 61 39873266

fat32_boot_sector
1 * FAT32 LBA 0 0 63 2637 29 61 39873266
Boot sector
Bad

Backup boot sector
Bad

Sectors are identical.

A valid FAT Boot sector must be present in order to access
any data; even if the partition is not bootable.

1 * FAT32 LBA 0 0 63 2637 29 61 39873266
rebuild_FAT_BS p_fat12 0, p_fat16 0, p_fat32 1
fat_find_type(max_offset=311573, p_fat12=0, p_fat16=0, p_fat32=1, debug=1,
dump_ind=0)
FAT32 at 33(0/1/33), nbr=599
FAT32 at 289(0/5/37), nbr=470
FAT32 at 545(0/9/41), nbr=701
FAT32 at 801(0/13/45), nbr=493
FAT32 at 800(0/13/44), nbr=53
FAT32 at 1057(0/17/49), nbr=28
FAT32 at 32(0/1/32), nbr=16
FAT32 at 288(0/5/36), nbr=35
FAT32 at 544(0/9/40), nbr=14
FAT32 at 9763(0/155/61), nbr=573
FAT32 at 10019(0/160/2), nbr=493
FAT32 at 9762(0/155/60), nbr=44
FAT32 at 10275(0/164/6), nbr=688
FAT32 at 10274(0/164/5), nbr=75
FAT32 at 10531(0/168/10), nbr=578
FAT32 at 10787(0/172/14), nbr=26
FAT32 at 10530(0/168/9), nbr=22
FAT32 at 10312(0/164/43), nbr=1
FAT32 at 10568(0/168/47), nbr=1
FAT32 at 65569(4/81/49), nbr=415
FAT32 at 65825(4/85/53), nbr=350
FAT32 at 66081(4/89/57), nbr=714
FAT32 at 66337(4/93/61), nbr=487
FAT32 at 66593(4/98/2), nbr=16
FAT32 at 66336(4/93/60), nbr=44
FAT32 at 65568(4/81/48), nbr=48
FAT32 at 65824(4/85/52), nbr=48
FAT32 at 66592(4/98/1), nbr=2
FAT32 at 66080(4/89/56), nbr=16
FAT32 at 75299(4/236/14), nbr=459
FAT32 at 75555(5/0/18), nbr=354
FAT32 at 75298(4/236/13), nbr=53
FAT32 at 75811(5/4/22), nbr=598
FAT32 at 76067(5/8/26), nbr=541
FAT32 at 76323(5/12/30), nbr=23
FAT32 at 75554(5/0/17), nbr=33
FAT32 at 75810(5/4/21), nbr=44
FAT32 at 76066(5/8/25), nbr=2
FAT32 at 75848(5/4/59), nbr=1
FAT32 at 76104(5/8/63), nbr=1
FAT32 at 193033(12/185/1), nbr=1
FAT32 at 193034(12/185/2), nbr=1
FAT32 at 193035(12/185/3), nbr=1
FAT32 at 193036(12/185/4), nbr=1
FAT32 at 193037(12/185/5), nbr=1
FAT32 at 193039(12/185/7), nbr=1
FAT32 at 193049(12/185/17), nbr=1
FAT32 at 193051(12/185/19), nbr=1
FAT32 at 193057(12/185/25), nbr=1
FAT32 at 193058(12/185/26), nbr=1
FAT32 at 193060(12/185/28), nbr=1
FAT32 at 193061(12/185/29), nbr=1
FAT32 at 193062(12/185/30), nbr=1
FAT32 at 193063(12/185/31), nbr=1
FAT32 at 193064(12/185/32), nbr=1
FAT32 at 193066(12/185/34), nbr=1
FAT32 at 193067(12/185/35), nbr=1
FAT32 at 193068(12/185/36), nbr=1
FAT32 at 193069(12/185/37), nbr=1
FAT32 at 193075(12/185/43), nbr=1
FAT32 at 193083(12/185/51), nbr=1
FAT32 at 193099(12/186/4), nbr=1
FAT32 at 193101(12/186/6), nbr=1
FAT32 at 193108(12/186/13), nbr=1
FAT32 at 193110(12/186/15), nbr=1
FAT32 at 193111(12/186/16), nbr=1
FAT32 at 193289(12/189/5), nbr=1
FAT32 at 193290(12/189/6), nbr=1
FAT32 at 193291(12/189/7), nbr=1
FAT32 at 193292(12/189/8), nbr=1
FAT32 at 193293(12/189/9), nbr=1
FAT32 at 193295(12/189/11), nbr=1
FAT32 at 193305(12/189/21), nbr=1
FAT32 at 193307(12/189/23), nbr=1
FAT32 at 193313(12/189/29), nbr=1
FAT32 at 193314(12/189/30), nbr=1
FAT32 at 193316(12/189/32), nbr=1
FAT32 at 193317(12/189/33), nbr=1
FAT32 at 193318(12/189/34), nbr=1
FAT32 at 193319(12/189/35), nbr=1
FAT32 at 193320(12/189/36), nbr=1
FAT32 at 193322(12/189/38), nbr=1
FAT32 at 193323(12/189/39), nbr=1
FAT32 at 193324(12/189/40), nbr=1
FAT32 at 193325(12/189/41), nbr=1
FAT32 at 193331(12/189/47), nbr=1
FAT32 at 193339(12/189/55), nbr=1
FAT32 at 193355(12/190/8), nbr=1
FAT32 at 193357(12/190/10), nbr=1
FAT32 at 193364(12/190/17), nbr=1
FAT32 at 193366(12/190/19), nbr=1
FAT32 at 193367(12/190/20), nbr=1
FAT32 at 277906(18/92/13), nbr=1
FAT32 at 277907(18/92/14), nbr=1
FAT32 at 277908(18/92/15), nbr=1
FAT32 at 280241(18/129/17), nbr=1
FAT32 at 287089(18/237/61), nbr=1
FAT32 at 287103(18/238/12), nbr=1
FAT32 at 287104(18/238/13), nbr=1
FAT32 at 287105(18/238/14), nbr=1
FAT32 at 287106(18/238/15), nbr=1
FAT32 at 287394(19/2/51), nbr=1
FAT32 at 288224(19/15/62), nbr=1
FAT32 at 288238(19/16/13), nbr=1
FAT32 at 288299(19/17/11), nbr=1
FAT32 at 288711(19/23/45), nbr=1
FAT32 at 288730(19/24/1), nbr=1
FAT32 at 288899(19/26/44), nbr=1
FAT32 at 289236(19/32/3), nbr=1
FAT32 at 289340(19/33/44), nbr=1
FAT32 at 289715(19/39/41), nbr=1
FAT32 at 289809(19/41/9), nbr=1
FAT32 at 289811(19/41/11), nbr=1
FAT32 at 289898(19/42/35), nbr=1
FAT32 at 289905(19/42/42), nbr=1
FAT32 at 289906(19/42/43), nbr=1
FAT32 at 289919(19/42/56), nbr=1
FAT32 at 289920(19/42/57), nbr=1
FAT32 at 289921(19/42/58), nbr=1
FAT32 at 289922(19/42/59), nbr=1
FAT32 at 289923(19/42/60), nbr=1
FAT32 at 289929(19/43/3), nbr=1
FAT32 at 289930(19/43/4), nbr=1
FAT32 at 289931(19/43/5), nbr=1
FAT32 at 289932(19/43/6), nbr=1
FAT32 at 289933(19/43/7), nbr=1
FAT32 at 290023(19/44/34), nbr=1
FAT32 at 290024(19/44/35), nbr=1
FAT32 at 290025(19/44/36), nbr=1
FAT32 at 290026(19/44/37), nbr=1
FAT32 at 290032(19/44/43), nbr=1
FAT32 at 290033(19/44/44), nbr=1
FAT32 at 290034(19/44/45), nbr=1
FAT32 at 290035(19/44/46), nbr=1
FAT32 at 290036(19/44/47), nbr=1
FAT32 at 290037(19/44/48), nbr=1
FAT32 at 290038(19/44/49), nbr=1
FAT32 at 290039(19/44/50), nbr=1
FAT32 at 290040(19/44/51), nbr=1
FAT32 at 290041(19/44/52), nbr=1
FAT32 at 290042(19/44/53), nbr=1
FAT32 at 290043(19/44/54), nbr=1
FAT32 at 290044(19/44/55), nbr=1
FAT32 at 290045(19/44/56), nbr=1
FAT32 at 290046(19/44/57), nbr=1
FAT32 at 290047(19/44/58), nbr=1
FAT32 at 290048(19/44/59), nbr=1
FAT32 at 290049(19/44/60), nbr=1
FAT32 at 290050(19/44/61), nbr=1
FAT32 at 290051(19/44/62), nbr=1
FAT32 at 290052(19/44/63), nbr=1
FAT32 at 290053(19/45/1), nbr=1
FAT32 at 290054(19/45/2), nbr=1
FAT32 at 290055(19/45/3), nbr=1
FAT32 at 290056(19/45/4), nbr=1
FAT32 at 290057(19/45/5), nbr=1
FAT32 at 290058(19/45/6), nbr=1
FAT32 at 290059(19/45/7), nbr=1
FAT32 at 290060(19/45/8), nbr=1
FAT32 at 290061(19/45/9), nbr=1
FAT32 at 290062(19/45/10), nbr=1
FAT32 at 290063(19/45/11), nbr=1
FAT32 at 290064(19/45/12), nbr=1
FAT32 at 290065(19/45/13), nbr=1
FAT32 at 290066(19/45/14), nbr=1
FAT32 at 290067(19/45/15), nbr=1
FAT32 at 290068(19/45/16), nbr=1
FAT32 at 290069(19/45/17), nbr=1
FAT32 at 290070(19/45/18), nbr=1
FAT32 at 290071(19/45/19), nbr=1
FAT32 at 290072(19/45/20), nbr=1
FAT32 at 290073(19/45/21), nbr=1
FAT32 at 290074(19/45/22), nbr=1
FAT32 at 290075(19/45/23), nbr=1
FAT32 at 290076(19/45/24), nbr=1
FAT32 at 290077(19/45/25), nbr=1
FAT32 at 290078(19/45/26), nbr=1
FAT32 at 290079(19/45/27), nbr=1
FAT32 at 290080(19/45/28), nbr=1
FAT32 at 290081(19/45/29), nbr=1
FAT32 at 290082(19/45/30), nbr=1
FAT32 at 290083(19/45/31), nbr=1
FAT32 at 290084(19/45/32), nbr=1
FAT32 at 290085(19/45/33), nbr=1
FAT32 at 290086(19/45/34), nbr=1
FAT32 at 290087(19/45/35), nbr=1
FAT32 at 290088(19/45/36), nbr=1
FAT32 at 290089(19/45/37), nbr=1
FAT32 at 290090(19/45/38), nbr=1
FAT32 at 290091(19/45/39), nbr=1
FAT32 at 290092(19/45/40), nbr=1
FAT32 at 290093(19/45/41), nbr=1
FAT32 at 290094(19/45/42), nbr=1
FAT32 at 290095(19/45/43), nbr=1
FAT32 at 290096(19/45/44), nbr=1
FAT32 at 290097(19/45/45), nbr=1
FAT32 at 290098(19/45/46), nbr=1
FAT32 at 290099(19/45/47), nbr=1
FAT32 at 290100(19/45/48), nbr=1
FAT32 at 290101(19/45/49), nbr=1
FAT32 at 290102(19/45/50), nbr=1
FAT32 at 290103(19/45/51), nbr=1
FAT32 at 290104(19/45/52), nbr=1
FAT32 at 290105(19/45/53), nbr=1
FAT32 at 290106(19/45/54), nbr=1
FAT32 at 290107(19/45/55), nbr=1
FAT32 at 290108(19/45/56), nbr=1
FAT32 at 290109(19/45/57), nbr=1
FAT32 at 290110(19/45/58), nbr=1
FAT32 at 290111(19/45/59), nbr=1
FAT32 at 290112(19/45/60), nbr=1
FAT32 at 290113(19/45/61), nbr=1
FAT32 at 290114(19/45/62), nbr=1
FAT32 at 290115(19/45/63), nbr=1
FAT32 at 290116(19/46/1), nbr=1
FAT32 at 290117(19/46/2), nbr=1
FAT32 at 290118(19/46/3), nbr=1
FAT32 at 290119(19/46/4), nbr=1
FAT32 at 290120(19/46/5), nbr=1
FAT32 at 290121(19/46/6), nbr=1
FAT32 at 290122(19/46/7), nbr=1
FAT32 at 290123(19/46/8), nbr=1
FAT32 at 290124(19/46/9), nbr=1
FAT32 at 290125(19/46/10), nbr=1
FAT32 at 290126(19/46/11), nbr=1
FAT32 at 290127(19/46/12), nbr=1
FAT32 at 290128(19/46/13), nbr=1
FAT32 at 290129(19/46/14), nbr=1
FAT32 at 290130(19/46/15), nbr=1
FAT32 at 290131(19/46/16), nbr=1
FAT32 at 290132(19/46/17), nbr=1
FAT32 at 290133(19/46/18), nbr=1
FAT32 at 290134(19/46/19), nbr=1
FAT32 at 290135(19/46/20), nbr=1
FAT32 at 290136(19/46/21), nbr=1
FAT32 at 290137(19/46/22), nbr=1
FAT32 at 290138(19/46/23), nbr=1
FAT32 at 290139(19/46/24), nbr=1
FAT32 at 290140(19/46/25), nbr=1
FAT32 at 290141(19/46/26), nbr=1
FAT32 at 290142(19/46/27), nbr=1
FAT32 at 290143(19/46/28), nbr=1
FAT32 at 290144(19/46/29), nbr=1
FAT32 at 290145(19/46/30), nbr=1
FAT32 at 290146(19/46/31), nbr=1
FAT32 at 290147(19/46/32), nbr=1
FAT32 at 290148(19/46/33), nbr=1
FAT32 at 290149(19/46/34), nbr=1
FAT32 at 290150(19/46/35), nbr=1
FAT32 at 290151(19/46/36), nbr=1
FAT32 at 290152(19/46/37), nbr=1
FAT32 at 290153(19/46/38), nbr=1
FAT32 at 290154(19/46/39), nbr=1
FAT32 at 290155(19/46/40), nbr=1
FAT32 at 290156(19/46/41), nbr=1
FAT32 at 290157(19/46/42), nbr=1
FAT32 at 290158(19/46/43), nbr=1
FAT32 at 290159(19/46/44), nbr=1
FAT32 at 290160(19/46/45), nbr=1
FAT32 at 290161(19/46/46), nbr=1
FAT32 at 290162(19/46/47), nbr=1
FAT32 at 290163(19/46/48), nbr=1
FAT32 at 290164(19/46/49), nbr=1
FAT32 at 290165(19/46/50), nbr=1
FAT32 at 290166(19/46/51), nbr=1
FAT32 at 290167(19/46/52), nbr=1
FAT32 at 290168(19/46/53), nbr=1
FAT32 at 290169(19/46/54), nbr=1
FAT32 at 290170(19/46/55), nbr=1
FAT32 at 290171(19/46/56), nbr=1
FAT32 at 290172(19/46/57), nbr=1
FAT32 at 290173(19/46/58), nbr=1
FAT32 at 290174(19/46/59), nbr=1
FAT32 at 290175(19/46/60), nbr=1
FAT32 at 290176(19/46/61), nbr=1
FAT32 at 290177(19/46/62), nbr=1
FAT32 at 290178(19/46/63), nbr=1
FAT32 at 290179(19/47/1), nbr=1
FAT32 at 290180(19/47/2), nbr=1
FAT32 at 290181(19/47/3), nbr=1
FAT32 at 290182(19/47/4), nbr=1
FAT32 at 290183(19/47/5), nbr=1
FAT32 at 290184(19/47/6), nbr=1
FAT32 at 290185(19/47/7), nbr=1
FAT32 at 290186(19/47/8), nbr=1
FAT32 at 290187(19/47/9), nbr=1
FAT32 at 290188(19/47/10), nbr=1
FAT32 at 290189(19/47/11), nbr=1
FAT32 at 290190(19/47/12), nbr=1
FAT32 at 290191(19/47/13), nbr=1
FAT32 at 290192(19/47/14), nbr=1
FAT32 at 290193(19/47/15), nbr=1
FAT32 at 290194(19/47/16), nbr=1
FAT32 at 290195(19/47/17), nbr=1
FAT32 at 290196(19/47/18), nbr=1
FAT32 at 290197(19/47/19), nbr=1
FAT32 at 290198(19/47/20), nbr=1
FAT32 at 290199(19/47/21), nbr=1
FAT32 at 290200(19/47/22), nbr=1
FAT32 at 290201(19/47/23), nbr=1
FAT32 at 290202(19/47/24), nbr=1
FAT32 at 290203(19/47/25), nbr=1
FAT32 at 290204(19/47/26), nbr=1
FAT32 at 290205(19/47/27), nbr=1
FAT32 at 290206(19/47/28), nbr=1
FAT32 at 290207(19/47/29), nbr=1
FAT32 at 290208(19/47/30), nbr=1
FAT32 at 290209(19/47/31), nbr=1
FAT32 at 290210(19/47/32), nbr=1
FAT32 at 290211(19/47/33), nbr=1
FAT32 at 290212(19/47/34), nbr=1
FAT32 at 290213(19/47/35), nbr=1
FAT32 at 290214(19/47/36), nbr=1
FAT32 at 290215(19/47/37), nbr=1
FAT32 at 290216(19/47/38), nbr=1
FAT32 at 290217(19/47/39), nbr=1
FAT32 at 290218(19/47/40), nbr=1
FAT32 at 290219(19/47/41), nbr=1
FAT32 at 290220(19/47/42), nbr=1
FAT32 at 290221(19/47/43), nbr=1
FAT32 at 290222(19/47/44), nbr=1
FAT32 at 290223(19/47/45), nbr=1
FAT32 at 290224(19/47/46), nbr=1
FAT32 at 290225(19/47/47), nbr=1
FAT32 at 290226(19/47/48), nbr=1
FAT32 at 290227(19/47/49), nbr=1
FAT32 at 290228(19/47/50), nbr=1
FAT32 at 290229(19/47/51), nbr=1
FAT32 at 290230(19/47/52), nbr=1
FAT32 at 290231(19/47/53), nbr=1
FAT32 at 290232(19/47/54), nbr=1
FAT32 at 290233(19/47/55), nbr=1
FAT32 at 290234(19/47/56), nbr=1
FAT32 at 290235(19/47/57), nbr=1
FAT32 at 290236(19/47/58), nbr=1
FAT32 at 290237(19/47/59), nbr=1
FAT32 at 290238(19/47/60), nbr=1
FAT32 at 290239(19/47/61), nbr=1
FAT32 at 290240(19/47/62), nbr=1
FAT32 at 290241(19/47/63), nbr=1
FAT32 at 290242(19/48/1), nbr=1
FAT32 at 290243(19/48/2), nbr=1
FAT32 at 290244(19/48/3), nbr=1
FAT32 at 290245(19/48/4), nbr=1
FAT32 at 290246(19/48/5), nbr=1
FAT32 at 290247(19/48/6), nbr=1
FAT32 at 290248(19/48/7), nbr=1
FAT32 at 290249(19/48/8), nbr=1
FAT32 at 290250(19/48/9), nbr=1
FAT32 at 290251(19/48/10), nbr=1
FAT32 at 290252(19/48/11), nbr=1
FAT32 at 290253(19/48/12), nbr=1
FAT32 at 290254(19/48/13), nbr=1
FAT32 at 290255(19/48/14), nbr=1
FAT32 at 290256(19/48/15), nbr=1
FAT32 at 290257(19/48/16), nbr=1
FAT32 at 290258(19/48/17), nbr=1
FAT32 at 290259(19/48/18), nbr=1
FAT32 at 290260(19/48/19), nbr=1
FAT32 at 290261(19/48/20), nbr=1
FAT32 at 290262(19/48/21), nbr=1
FAT32 at 290263(19/48/22), nbr=1
FAT32 at 290264(19/48/23), nbr=1
FAT32 at 290265(19/48/24), nbr=1
FAT32 at 290266(19/48/25), nbr=1
FAT32 at 290267(19/48/26), nbr=1
FAT32 at 290268(19/48/27), nbr=1
FAT32 at 290269(19/48/28), nbr=1
FAT32 at 290270(19/48/29), nbr=1
FAT32 at 290271(19/48/30), nbr=1
FAT32 at 290272(19/48/31), nbr=1
FAT32 at 290273(19/48/32), nbr=1
FAT32 at 290274(19/48/33), nbr=1
FAT32 at 290275(19/48/34), nbr=1
FAT32 at 290276(19/48/35), nbr=1
FAT32 at 290277(19/48/36), nbr=1
FAT32 at 290278(19/48/37), nbr=1
FAT32 at 290279(19/48/38), nbr=1
FAT32 at 290280(19/48/39), nbr=1
FAT32 at 290281(19/48/40), nbr=1
FAT32 at 290282(19/48/41), nbr=1
FAT32 at 290283(19/48/42), nbr=1
FAT32 at 290284(19/48/43), nbr=1
FAT32 at 290285(19/48/44), nbr=1
FAT32 at 290286(19/48/45), nbr=1
FAT32 at 290287(19/48/46), nbr=1
FAT32 at 290288(19/48/47), nbr=1
FAT32 at 290289(19/48/48), nbr=1
FAT32 at 290290(19/48/49), nbr=1
FAT32 at 290291(19/48/50), nbr=1
FAT32 at 290292(19/48/51), nbr=1
FAT32 at 290293(19/48/52), nbr=1
FAT32 at 290294(19/48/53), nbr=1
FAT32 at 290295(19/48/54), nbr=1
FAT32 at 290296(19/48/55), nbr=1
FAT32 at 290297(19/48/56), nbr=1
FAT32 at 290298(19/48/57), nbr=1
FAT32 at 290299(19/48/58), nbr=1
FAT32 at 290300(19/48/59), nbr=1
FAT32 at 290301(19/48/60), nbr=1
FAT32 at 290302(19/48/61), nbr=1
FAT32 at 290303(19/48/62), nbr=1
FAT32 at 290304(19/48/63), nbr=1
FAT32 at 290305(19/49/1), nbr=1
FAT32 at 290306(19/49/2), nbr=1
FAT32 at 290307(19/49/3), nbr=1
FAT32 at 290308(19/49/4), nbr=1
FAT32 at 294003(19/107/45), nbr=1
FAT32 at 294027(19/108/6), nbr=1
FAT32 at 294037(19/108/16), nbr=1
FAT32 at 294043(19/108/22), nbr=1
FAT32 at 294044(19/108/23), nbr=1
FAT32 at 294048(19/108/27), nbr=1
FAT32 at 294055(19/108/34), nbr=1
FAT32 at 294056(19/108/35), nbr=1
FAT32 at 294059(19/108/38), nbr=1
FAT32 at 294063(19/108/42), nbr=1
FAT32 at 294064(19/108/43), nbr=1
FAT32 at 294067(19/108/46), nbr=1
FAT32 at 294068(19/108/47), nbr=1
FAT32 at 294069(19/108/48), nbr=1
FAT32 at 303712(20/21/52), nbr=1
FAT32 at 303713(20/21/53), nbr=1
FAT32 at 304467(20/33/51), nbr=1
FAT32 at 304488(20/34/9), nbr=1
FAT32 at 304507(20/34/28), nbr=1
FAT32 at 304511(20/34/32), nbr=1
FAT32 at 304526(20/34/47), nbr=1
FAT32 at 304527(20/34/48), nbr=1
FAT32 at 304528(20/34/49), nbr=1
FAT32 at 304530(20/34/51), nbr=1
FAT32 at 304532(20/34/53), nbr=1
first_fat 33, second_fat 289
FAT : 32, reserved=33, fat_length=256
sectors_per_cluster 2048
Can't get cluster size

fat32_boot_sector
1 * FAT32 LBA 0 0 63 2637 29 61 39873266
Boot sector
Bad

Backup boot sector
Bad

Sectors are identical.

A valid FAT Boot sector must be present in order to access
any data; even if the partition is not bootable.

TestDisk exited normally.

__________________________________________________ _______________
__________________________________________________ ______________

******HERES THE 3RD E_MAIL***********

On Sun, 5 Oct 2008, Mike Smith wrote:

> Hey
> Christophe
>
> thanks so much for trying to help me here..
> hey buddy don't forget im NOT familiar with TESDISK at all...
> and know very little about Hard drive Specifications..

*******HIS REPLY***************
You have followed the steps correctly ;-)
Now run TestDisk, Advanced, Boot, RebuildBS, List,
If you see your files, choose Write, confirm, Quit
and reboot.
Send me the testdisk.log file if you have any problem.

__________________________________________________ _____________
__________________________________________________ _________

*****4TH E-MAIL

____________________________________________

On Tue, 7 Oct 2008, Mike Smith wrote:

> hey
> Christophe
> yeah just want to say it again..thanks so much for trying to help me
>
> yeah Christophe im Officially lost now :))
> with what were doing here ..

Looks like it won't be easy to recover your data...

> yeah this is way out of my leauge buddy..
> thank god theres people in the world like you buddy..
> yeah just kinda really wondering to my self..
> how you arrived at this point knowing the things you do about computers..
> yeah thanks so much Christophe for trying to help me..
>
> whelp heres that log..
> i got to the point RebuildBS
> after running that it said *cant get cluster*..
> and something about Boot Sector Bad
> and Back up Boot Sector Bad
> Sectors are the same..
> anyways..
> heres the log..

Now run TestDisk, Options, enable the expert mode,
Advanced, Boot, RebuildBS, for FAT1 and FAT2,
enter 33, use the default value otherwise.
List and send me the testdisk.log file

Christophe

__________________________________________________ _____
__________________________________________________ ____

********** 5TH E-MAIL **********

___________________________________

On Fri, 10 Oct 2008, Mike Smith wrote:

> hey Christophe
>
> heres that log file ..
> i ended up running Testdisk( 5 )times..
> before i finally got this log file..
> *but at the end..it said* ..
> LOG FILE CORRUPT!
> wondering if that matters or not..

*****HIS REPLY ******
Enable the expert mode, RebuildBS, choose
FAT1: 33
FAT2: 9763
Send me the new log file.

__________________________________________________ ____
__________________________________________________ ___

*********** 6TH E-MAIL **********

_______________________________________________

On Sun, 23 Nov 2008, Mike Smith wrote:

> Hey christophe..
> ...
> and if we should maybe want to try and put the HD BACK TO THE WAY IT WAS when we first started and see what happens or if that is even possible...
>
> Since it is now being seen in Windows 98 on the Abit motherboard but is not accessable the way we have the HD settings set now...
>
> like i said when we first started Christophe im not a computer wizzard..
> and hope you understand what i just wrote you..
>
> and what you might think i should try and do now to either get this HD working again..or what i should try to do to recover some of my data on this HD...
> please let me know what you think i should do now..


************** HIS RESPONCE ***************
My previous recommandation is still valid:

>> Enable the expert mode, RebuildBS, choose
>> FAT1: 33
>> FAT2: 9763
>> Send me the new log file.

__________________________________________________ ________
__________________________________________________ ______

************ 7TH E-MAIL **************

_______________________________________

On Sun, 23 Nov 2008, Mike Smith wrote:

> hey Christophe
>
> i dont know if i did this right i did this to get to where i think you wanted me to get..
>
> Advanced
> enable the expert mode...
> Advanced
> RebuildBS
> Boot
>
> then it said something like...
>
> potential FATS and it listed 2 different things..
> one of them was..
> fat1 32
> fat2 9762..
>
> i just clicked proceed..
>
> then the next thing poped up..
> and the first one was blinking 32...i changed it to 33
> and then fat2 poped up saying 9762...and i changed it to 9763
>
> i changed them to 33 and 9763 like you said to
>
> then it said this...
>
> Number of FATS (Usually 2) (1-2) :2
> and i just clicked... ok..and left the 2
>
> and i guess it started searching subdirectory ..
> and stoped at this numbers.. 190464 / 39873267 4
>
> and now down at the bottom it says
>
> STOP
> cluster size (0-128) :32
>
> and line is flashing under the 3 like i need to pick cluster size...
>
> what am i suposed to pick under the cluster size?..
> or am i just suposed to click stop now...
> and not change that 32 number

********** HIS RESPONCE ***************
Validate the other values

Christophe

__________________________________________________ _____
__________________________________________________ _____

***************** 8TH E_MAIL *************

__________________________________________________ ____

hey Christophe

im lost here...
i don't know what you mean Validate!!..
plus...
theres things you didn't say what to do after..
i changed the FAT 33 and FAT2 9763

like the last letter i wrote i've had my computer running for 4 days in Dos
just sitting running..
wating on what to type on the CLUSTER thing..

i asked you what i should type in there..
when it was flashing on the 3 in 32..
***i just clicked ENTER...and left it at 32***

then it went to another page..
that looks like im going to show you below..
you didnt say what i should pick on this page either...

like i keep telling you christophe..
im am NOT a computer wizzard..
and have no idea what im doing here..

and when theres things you do not say anything about i get lost..
and have no idea which things to pick..
hoping im not messing anything up picking things
that you didn't say i would have to pick from...

like this next page...
you didn't say anything about the cluster page
or this page that was after it..

and what thing i should pick on this next page either..
heres what the page looks like...


TestDisk 6.10 Data Recovery Utility,July2008
Christophe >
http://www.cysecurity.org

1*FAT32LBA 0 1 1 2481 254 63 39873267 [DSK1_VOL1]
Cluster 2, Directory/found?
Answer Y(yes), N(o) or A(bort interactive mode).N or A if not sure.

drwxr-xr-x 0 0 0 19-Mar-2006 03:47 RECYCLED
drwxr-xr-x 0 0 0 24-Mar-2006 16:22 movie clips
dr-xr-xr-x 0 0 0 14-May-2006 21:05 a2
-rwxr-xr-x 0 0 64 25-Feb-2008 05:06 Capture.fcb
drwxr-xr-x 0 0 0 21-Apr-2006 22:43 1a

***and theres alot more on the list...***
i don't think typing the whole page matters..

you did not say what to pick from here..
like if i should pick....(yes / no or abort)

i just picked Abort because i didn't know...
you didn't say anything about what to pick on that page either..

and when i picked Abort it took me to another page

and now it searched
**Search root Cluster**

and when it was done..
it asked me to..

**create a new root cluster with 16 first-level directories (expert only)
(y/n)**

i picked **NO** because i didnt know what to pick either on this page..
you didn't say anything about this page either...

after picking NO

then it poped to a page that wants me to pick
** root cluster (2-1245431) :0 **

and is flashing on :0 zero

what do i type in there?

you didn't say anything about choosing from this either...

i have no idea what i have picked for these last 3 pages becasue you didnt
say anything about the choices i had to pick from them...

what do i choose for this page now thats asking me

root cluster (2-1245431) :0

yeah Christophe im lost i have no idea because you didnt say i'd have all
these choices after doing what you said to do below..

and heres all you said...
you didn't say anything about the numbers or choices i'd have to pick...
you do know im running the DOS program right?..
and not the one from Windows?..
heres all you said below..
what about the rest?

**My previous recommandation is still valid:**

>> Enable the expert mode, RebuildBS, choose
>> FAT1: 33
>> FAT2: 9763
>> Send me the new log file.

___________________________
__________________________________________________ ___

yeah PC that was a few days ago..i havent heard from him yet...

i had my computer blinking on the root cluster thing for like a few days now..
i have no idea what i should type in the Root cluster thing..

it says....root cluster (2-1245431) :0...

and is blinking on the :0 zero...
i have no idea what to type in there....

and my computer is sitting in DOS running for days now..
i dont think it will be good to just re-start it with out typing something
in there..
i don't think just shutting off my computer without typing anything in there..

yeah i dont know what to do now..
kinda wish i never put this hard drive in that stupid Compaq system..
because i know it was something to do with the Compaq and the hard drive was
fine to start with...
and now i probally messed it up changing what the testdisk guy had me change.

anyways...
sorry this is so long

[Jeff Richards]

There's not much point in more than one person getting involved at this
stage of things. It seems he is attempting to rebuild the FAT. This may or
may not work, depending on the original cause of the problem. It won't work
if the problem is what I have guessed, because the LBA is different. This
means that the current relationship between a logical block of data (the
number that the operating system uses to address the disk sectors) and the
actual physical location on the disk where the data for that logical block
number is stored (the CHS value) is different than that which applied when
the data was originally written to disk. So even if you can reconstruct the
FAT, the numbers in the FAT will point to a physical location on the disk
that does not correspond to the data for that file. This means (for
instance) when the system attempts to read a directory to find where you
other files are, it will be reading some correct data and some wrong data,
and won't be able to make much sense of it.

I see some evidence that my theory might be right, but I don't understand
enough about that program to be able to confirm it, so it's still possible
that the searching and rebuilding you are doing might get that data back.
You can't do much more than stick with the procedure you have started.

Have you told him that someone else you have spoken with thinks that the
disk may originally have had a disk manager installed? That could be
something useful for him to know.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"mikesmith" > wrote in message
...
> PART 3 OF 3
>
> snip <

[PCR]

I think I saw some good in the logs you posted, especially when it
started showing directory names...

| FAT: cluster=2(0x2), pos=19555
| 1 * FAT32 LBA 0 1 1 2637 29 63 39873267
| [DSK1_VOL1] FAT32, 20 GB / 19 GiB
| Directory /
| 5352 drwxr-xr-x 0 0 0 19-Mar-2006 03:47 RECYCLED
| 5376 drwxr-xr-x 0 0 0 24-Mar-2006 16:22 movie clips
| X 5288 drwxr-xr-x 0 0 0 13-Sep-2008 15:53 MASTER
| Reinstall for KT7

It looks to me a recovery is possible. Either Richards or the TESTDISK
guy should be able to do it. Has the latter gotten back to you yet? (I
hope so.) More below.

mikesmith wrote:
....snip

| ************** HIS RESPONCE ***************
| My previous recommandation is still valid:
|
|>> Enable the expert mode, RebuildBS, choose
|>> FAT1: 33
|>> FAT2: 9763
|>> Send me the new log file.
|
| __________________________________________________ ________
| __________________________________________________ ______
|
| ************ 7TH E-MAIL **************
|
| _______________________________________
|
| On Sun, 23 Nov 2008, Mike Smith wrote:
|
|> hey Christophe
|>
|> i dont know if i did this right i did this to get to where i think
|> you wanted me to get..
|>
|> Advanced
|> enable the expert mode...
|> Advanced
|> RebuildBS
|> Boot
|>
|> then it said something like...
|>
|> potential FATS and it listed 2 different things..
|> one of them was..
|> fat1 32
|> fat2 9762..
|>
|> i just clicked proceed..

I suppose you couldn't change them right there. OK, then-- if that's all
you could do.

|> then the next thing poped up..
|> and the first one was blinking 32...i changed it to 33
|> and then fat2 poped up saying 9762...and i changed it to 9763
|>
|> i changed them to 33 and 9763 like you said to

Fine! (But would be nice to know why he chose those values. But I guess
he knows!)

|> then it said this...
|>
|> Number of FATS (Usually 2) (1-2) :2
|> and i just clicked... ok..and left the 2

Looks right to me.

|> and i guess it started searching subdirectory ..
|> and stoped at this numbers.. 190464 / 39873267 4
|>
|> and now down at the bottom it says
|>
|> STOP
|> cluster size (0-128) :32
|>
|> and line is flashing under the 3 like i need to pick cluster size...
|>
|> what am i suposed to pick under the cluster size?..
|> or am i just suposed to click stop now...
|> and not change that 32 number
|
| ********** HIS RESPONCE ***************
| Validate the other values

Yea, I'm not sure, either, what he means by that-- but it could mean to
accept them. Let's see (as glee once posted)...

http://support.microsoft.com/kb/q192322/
Description of Default Cluster Sizes for FAT32 File System
.......Quote.........
Partition size Cluster size
------------------------------ --------------
512 MB to 8,191 MB 4 KB
8,192 MB to 16,383 MB 8 KB
16,384 MB to 32,767 MB 16 KB
Larger than 32,768 MB 32 KB
......EOQ.............

Yikes, it looks to me the default for a 20 GB partition is 16! But I'm
not sure what size your partition actuall is. The TESTDISK log shows two
possibilities...

| Disk 81 - 7911 MB / 7545 MiB - CHS 1022 240 63

That's about 8 GB, which would have a cluster size (by default) of 4 KB.

| Disk 81 - 20 GB / 19 GiB - CHS 42197 15 63
| LBA size=39876480

That's where it says 20 GB. But this too wouldn't have a default cluster
size of 32 KB. Of course, it could be your particular partition is not
using a default size for some reason. Because the log went on to show
valid directory names-- maybe stick with 32 for the cluster size. (I
can't really say.)

| Christophe
|
| __________________________________________________ _____
| __________________________________________________ _____
|
| ***************** 8TH E_MAIL *************
|
| __________________________________________________ ____
|
| hey Christophe
|
| im lost here...
| i don't know what you mean Validate!!..

I'm hoping he's gotten back to you with an answer for that & the rest of
what you ask.

| plus...
| theres things you didn't say what to do after..
| i changed the FAT 33 and FAT2 9763
|
| like the last letter i wrote i've had my computer running for 4 days
| in Dos just sitting running..
| wating on what to type on the CLUSTER thing..
|
| i asked you what i should type in there..
| when it was flashing on the 3 in 32..
| ***i just clicked ENTER...and left it at 32***

Ask him what is the actual size of the partition getting rebuilt, & show
him that table of default cluster sizes.

| then it went to another page..
| that looks like im going to show you below..
| you didnt say what i should pick on this page either...
|
| like i keep telling you christophe..
| im am NOT a computer wizzard..
| and have no idea what im doing here..
|
| and when theres things you do not say anything about i get lost..
| and have no idea which things to pick..
| hoping im not messing anything up picking things
| that you didn't say i would have to pick from...
|
| like this next page...
| you didn't say anything about the cluster page
| or this page that was after it..
|
| and what thing i should pick on this next page either..
| heres what the page looks like...

You are asking the right questions. Try not to sound accusatory at this
stage, though.

| TestDisk 6.10 Data Recovery Utility,July2008
| Christophe >
| http://www.cysecurity.org
|
| 1*FAT32LBA 0 1 1 2481 254 63 39873267 [DSK1_VOL1]
| Cluster 2, Directory/found?
| Answer Y(yes), N(o) or A(bort interactive mode).N or A if not sure.
|
| drwxr-xr-x 0 0 0 19-Mar-2006 03:47 RECYCLED
| drwxr-xr-x 0 0 0 24-Mar-2006 16:22 movie clips
| dr-xr-xr-x 0 0 0 14-May-2006 21:05 a2
| -rwxr-xr-x 0 0 64 25-Feb-2008 05:06 Capture.fcb
| drwxr-xr-x 0 0 0 21-Apr-2006 22:43 1a

It looks like you are certainly getting at least some directory names
correctly shown. But do you have a directory named "a2" & "1a"? Let us
see what he says about those.

| ***and theres alot more on the list...***
| i don't think typing the whole page matters..
|
| you did not say what to pick from here..
| like if i should pick....(yes / no or abort)

I hope he has given you the answer. I'd say to choose "abort", if you
are unsatisfied with the names being shown.

| i just picked Abort because i didn't know...
| you didn't say anything about what to pick on that page either..
|
| and when i picked Abort it took me to another page

Possibly -- since you chose to abort -- it is going to retry to get you
a better list of directory names.

| and now it searched
| **Search root Cluster**
|
| and when it was done..
| it asked me to..
|
| **create a new root cluster with 16 first-level directories (expert
| only) (y/n)**
|
| i picked **NO** because i didnt know what to pick either on this
| page..
| you didn't say anything about this page either...

You did well to choose "no", under the circumstances. This is a good
post of yours-- he can respond to it with finalized answers!

| after picking NO
|
| then it poped to a page that wants me to pick
| ** root cluster (2-1245431) :0 **
|
| and is flashing on :0 zero
|
| what do i type in there?
|
| you didn't say anything about choosing from this either...
|
| i have no idea what i have picked for these last 3 pages becasue you
| didnt say anything about the choices i had to pick from them...
|
| what do i choose for this page now thats asking me
|
| root cluster (2-1245431) :0
|
| yeah Christophe im lost i have no idea because you didnt say i'd have
| all these choices after doing what you said to do below..

All right, all right, you have done well to show him all the questions.
Just stop sounding accusatory, is all! You have done well not to answer
the questions on your own, but to show every single one of them to him.

| and heres all you said...
| you didn't say anything about the numbers or choices i'd have to
| pick...
| you do know im running the DOS program right?..
| and not the one from Windows?..
| heres all you said below..
| what about the rest?
|
| **My previous recommandation is still valid:**
|
|>> Enable the expert mode, RebuildBS, choose
|>> FAT1: 33
|>> FAT2: 9763
|>> Send me the new log file.
|
| ___________________________
| __________________________________________________ ___
|
| yeah PC that was a few days ago..i havent heard from him yet...

When you are certain he will never answer, I'm sure Richards will help
you guess-- if not, then I will!

| i had my computer blinking on the root cluster thing for like a few
| days now.. i have no idea what i should type in the Root cluster
| thing..
|
| it says....root cluster (2-1245431) :0...
|
| and is blinking on the :0 zero...
| i have no idea what to type in there....
|
| and my computer is sitting in DOS running for days now..
| i dont think it will be good to just re-start it with out typing
| something
| in there..
| i don't think just shutting off my computer without typing anything
| in there..
|
| yeah i dont know what to do now..
| kinda wish i never put this hard drive in that stupid Compaq system..
| because i know it was something to do with the Compaq and the hard
| drive was fine to start with...
| and now i probally messed it up changing what the testdisk guy had me
| change.
|
| anyways...
| sorry this is so long

It was long, but full of the proper questions. Has that guy answered
them yet?


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR