Partitions disappeared

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

I am runing Windows 98 on a 200 Gig HD. There are 3 partitions on the HD.
One is about 10 gigs and holds the operating system. Yesterday the other
two partitions disappered while windows was running. So far I have rebooted
a couple of times (before i realized what was going on) and attempted to fix
the mbr with "FDISK /MBR" which did not fix the problem. I have run
FindPart and will include the ouput from that below. But after this point I
am out of my league. Is the output from FindPart enough to restore the
partitions? I am not concerned with the data on the OS partition. I am
fine with having to reinstall the OS. It's the data on the other 2 drives
that I am interested in. Can someone please guide me through this?

Thank you very much.

FindPart Output....................

Findpart, version 4.42.
Copyright Svend Olaf Mikkelsen, 1999-2004.

OS: DOS 7.10

Disk: 1 Cylinders: 24792 Heads: 255 Sectors: 63 MB: 194474

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 - 0C 63 19534977 9538 0 1 1 1215 254 63 B OK
8511 1 0B 63261554202127712 8511 1 1 24791 254 63 OK OK

------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
0 1 33 9530 8 2 9530 0 0 0 05-03-07 454
8511 1 33 31921 32 2 31921 0 0 0 05-02-21 75808
13317 0 33 Second FAT not found.

Partitions according to partition tables on first harddisk:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK OK
0 2 0F 19535040378748440184935 1216 0 1 24791 254 63 OK

No signature CHS: 1216 0 1

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Annika K" <none@none.com> wrote in message
newspGdndxdBKruwK_fRVn-vQ@comcast.com...
> I am runing Windows 98 on a 200 Gig HD. There are 3 partitions on the HD.
> One is about 10 gigs and holds the operating system. Yesterday the other
> two partitions disappered while windows was running. So far I have
rebooted
> a couple of times (before i realized what was going on) and attempted to
fix
> the mbr with "FDISK /MBR" which did not fix the problem. I have run
> FindPart and will include the ouput from that below. But after this point
I
> am out of my league. Is the output from FindPart enough to restore the
> partitions? I am not concerned with the data on the OS partition. I am
> fine with having to reinstall the OS. It's the data on the other 2 drives
> that I am interested in. Can someone please guide me through this?
>
> Thank you very much.
>
> FindPart Output....................
>
> Findpart, version 4.42.
> Copyright Svend Olaf Mikkelsen, 1999-2004.
>
> OS: DOS 7.10
>
> Disk: 1 Cylinders: 24792 Heads: 255 Sectors: 63 MB: 194474
>
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 0 - 0C 63 19534977 9538 0 1 1 1215 254 63 B OK
> 8511 1 0B 63261554202127712 8511 1 1 24791 254 63 OK OK
>
> ------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
> 0 1 33 9530 8 2 9530 0 0 0 05-03-07 454
> 8511 1 33 31921 32 2 31921 0 0 0 05-02-21 75808
> 13317 0 33 Second FAT not found.
>
> Partitions according to partition tables on first harddisk:
>
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK OK
> 0 2 0F 19535040378748440184935 1216 0 1 24791 254 63 OK
>
> No signature CHS: 1216 0 1
>
>

You did not indicate the size of the missing 2 partitions. Your mistake was
running fdisk /mbr as win98's fdisk only "understands" up to 64GB size
partitions. After that, you get cylinder wrap. An updated version of fdisk
from MS does up to 128GB.

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Lil' Dave" <spamyourself@virus.net> wrote in message
news:AbyYd.1583$qW.938@newsread3.news.atl.earthlink.net...
>
> You did not indicate the size of the missing 2 partitions. Your mistake was
> running fdisk /mbr as win98's fdisk only "understands" up to 64GB size
> partitions. After that, you get cylinder wrap. An updated version of fdisk
> from MS does up to 128GB.
>
Fdisk /mbr never fixes such problems. The original version works, it just
reports the wrong drive size.

If the OP has an older machine, the BIOS does not support over 135GB. You will
certainly get corruption with a 200GB disk and Win98.

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

Is it too late to use the updated fdisk?

"Lil' Dave" <spamyourself@virus.net> wrote in message
news:AbyYd.1583$qW.938@newsread3.news.atl.earthlink.net...
> "Annika K" <none@none.com> wrote in message
> newspGdndxdBKruwK_fRVn-vQ@comcast.com...
>> I am runing Windows 98 on a 200 Gig HD. There are 3 partitions on the
>> HD.
>> One is about 10 gigs and holds the operating system. Yesterday the other
>> two partitions disappered while windows was running. So far I have
> rebooted
>> a couple of times (before i realized what was going on) and attempted to
> fix
>> the mbr with "FDISK /MBR" which did not fix the problem. I have run
>> FindPart and will include the ouput from that below. But after this
>> point
> I
>> am out of my league. Is the output from FindPart enough to restore the
>> partitions? I am not concerned with the data on the OS partition. I am
>> fine with having to reinstall the OS. It's the data on the other 2
>> drives
>> that I am interested in. Can someone please guide me through this?
>>
>> Thank you very much.
>>
>> FindPart Output....................
>>
>> Findpart, version 4.42.
>> Copyright Svend Olaf Mikkelsen, 1999-2004.
>>
>> OS: DOS 7.10
>>
>> Disk: 1 Cylinders: 24792 Heads: 255 Sectors: 63 MB: 194474
>>
>> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
>> 0 - 0C 63 19534977 9538 0 1 1 1215 254 63 B OK
>> 8511 1 0B 63261554202127712 8511 1 1 24791 254 63 OK OK
>>
>> ------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
>> 0 1 33 9530 8 2 9530 0 0 0 05-03-07 454
>> 8511 1 33 31921 32 2 31921 0 0 0 05-02-21 75808
>> 13317 0 33 Second FAT not found.
>>
>> Partitions according to partition tables on first harddisk:
>>
>> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
>> 0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK OK
>> 0 2 0F 19535040378748440184935 1216 0 1 24791 254 63 OK
>>
>> No signature CHS: 1216 0 1
>>
>>
>
> You did not indicate the size of the missing 2 partitions. Your mistake
> was
> running fdisk /mbr as win98's fdisk only "understands" up to 64GB size
> partitions. After that, you get cylinder wrap. An updated version of
> fdisk
> from MS does up to 128GB.
>
>

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

It's not an older machine..at least I don’t think so. The BIOS recognized
the hard drive correctly. How old is older? At any rate, is there any hope
for me or is all lost since I ran FDISK /mbr? If there is hope can someone
walk me through this or point to a site that tells me precisely how to
recover the partitions? I'm in over my head on this one.

Thanks very much

"Eric Gisin" <ericgisin@hotmail.com> wrote in message
news:d0v6rl1o99@enews1.newsguy.com...
> "Lil' Dave" <spamyourself@virus.net> wrote in message
> news:AbyYd.1583$qW.938@newsread3.news.atl.earthlink.net...
>>
>> You did not indicate the size of the missing 2 partitions. Your mistake
>> was
>> running fdisk /mbr as win98's fdisk only "understands" up to 64GB size
>> partitions. After that, you get cylinder wrap. An updated version of
>> fdisk
>> from MS does up to 128GB.
>>
> Fdisk /mbr never fixes such problems. The original version works, it just
> reports the wrong drive size.
>
> If the OP has an older machine, the BIOS does not support over 135GB. You
> will
> certainly get corruption with a 200GB disk and Win98.
>

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Lil' Dave" <spamyourself@virus.net> wrote in message news:AbyYd.1583$qW.938@newsread3.news.atl.earthlink.net
> "Annika K" <none@none.com> wrote in message
> newspGdndxdBKruwK_fRVn-vQ@comcast.com...
> > I am runing Windows 98 on a 200 Gig HD. There are 3 partitions on the HD.
> > One is about 10 gigs and holds the operating system. Yesterday the other
> > two partitions disappered while windows was running. So far I have rebooted
> > a couple of times (before i realized what was going on) and attempted to fix
> > the mbr with "FDISK /MBR" which did not fix the problem. I have run
> > FindPart and will include the ouput from that below. But after this point I
> > am out of my league. Is the output from FindPart enough to restore the
> > partitions? I am not concerned with the data on the OS partition. I am
> > fine with having to reinstall the OS. It's the data on the other 2 drives
> > that I am interested in. Can someone please guide me through this?
> >
> > Thank you very much.
> >
> > FindPart Output....................
> >
> > Findpart, version 4.42.
> > Copyright Svend Olaf Mikkelsen, 1999-2004.
> >
> > OS: DOS 7.10
> >
> > Disk: 1 Cylinders: 24792 Heads: 255 Sectors: 63 MB: 194474
> >
> > --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> > 0 - 0C 63 19534977 9538 0 1 1 1215 254 63 B OK
> > 8511 1 0B 63261554202127712 8511 1 1 24791 254 63 OK OK
> >
> > ------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
> > 0 1 33 9530 8 2 9530 0 0 0 05-03-07 454
> > 8511 1 33 31921 32 2 31921 0 0 0 05-02-21 75808
> > 13317 0 33 Second FAT not found.
> >
> > Partitions according to partition tables on first harddisk:
> >
> > --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> > 0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK OK
> > 0 2 0F 19535040378748440184935 1216 0 1 24791 254 63 OK
> >
> > No signature CHS: 1216 0 1
> >
> >
>
> You did not indicate the size of the missing 2 partitions. Your mistake was
> running fdisk /mbr as win98's fdisk only "understands" up to 64GB size
> partitions. After that, you get cylinder wrap. An updated version of fdisk
> from MS does up to 128GB.

Wotanidiot.

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Annika K" <none@none.com> wrote in message newspGdndxdBKruwK_fRVn-vQ@comcast.com
> I am runing Windows 98 on a 200 Gig HD. There are 3 partitions on the HD.
> One is about 10 gigs and holds the operating system. Yesterday the other
> two partitions disappered while windows was running. So far I have rebooted
> a couple of times (before i realized what was going on) and attempted to fix
> the mbr with "FDISK /MBR" which did not fix the problem.

That only fixes (very limited) bootproblems.

> I have run FindPart and will include the ouput from that below.
> But after this point I am out of my league.

> Is the output from FindPart enough to restore the partitions?

It can usually be used to serve as input to a partition table editor.

> I am not concerned with the data on the OS partition. I am
> fine with having to reinstall the OS. It's the data on the other 2 drives
> that I am interested in. Can someone please guide me through this?
>
> Thank you very much.
>
> FindPart Output....................
>
> Findpart, version 4.42.
> Copyright Svend Olaf Mikkelsen, 1999-2004.
>
> OS: DOS 7.10
>
> Disk: 1 Cylinders: 24792 Heads: 255 Sectors: 63 MB: 194474
>
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS

> 0 - 0C 63 19534977 9538 0 1 1 1215 254 63 B OK

The bootrecord of the primary partition, drive C:

> 8511 1 0B 63 261554202 127712 8511 1 1 24791 254 63 OK OK

The bootrecord of the second logical, drive E:
The bootrecord of the first logical, (drive D at cyl. 1216 is missing

>
> ------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
> 0 1 33 9530 8 2 9530 0 0 0 05-03-07 454

FAT of the primary partition, drive C:

> 8511 1 33 31921 32 2 31921 0 0 0 05-02-21 75808

FATs of 2nd logical again.
The FATs of 1st logical at cyl 1216 are missing.

> 13317 0 33 Second FAT not found.
>
> Partitions according to partition tables on first harddisk:
>
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS

> 0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK OK

MBR, primary partition, drive C:

> 0 2 0F 19535040 378748440 184935 1216 0 1 24791 254 63 OK

Extended partition, holder of logicals D: and E:
The EMBR at cyl. 1216 that the Extended partition points to and it's Logical
and the pointer to the second EMBR at cyl. 8511 and its logical are missing.

The EMBR at cyl. 8511 itself may be OK.

>
> No signature (at) CHS: 1216 0 1

May be the reason why the 1st EMBR isn't listed.
Inconclusive since there is no such comment on the second EMBR and it isn't
listed either.

Recreating the first EMBR may return access to drive E:
Drive D: is lost.

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

Thank you, Folkert. Do I use ptedit to recreate the EMBR? I read
instructions on this page
http://www.warpdoctor.org/walter/articles/2000/aa061400a.html
that say to change the type column from 0F to 05. Is this what i need to
do?

"Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message
news:39hl1fF62hpi8U1@individual.net...

> Recreating the first EMBR may return access to drive E:
> Drive D: is lost.

 

[joeP]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Annika K" <none@none.com> wrote in message
newspGdndxdBKruwK_fRVn-vQ@comcast.com...
> I am runing Windows 98 on a 200 Gig HD. There are 3 partitions on the HD.
> One is about 10 gigs and holds the operating system. Yesterday the other
> two partitions disappered while windows was running. So far I have
rebooted
> a couple of times (before i realized what was going on) and attempted to
fix
> the mbr with "FDISK /MBR" which did not fix the problem. I have run
> FindPart and will include the ouput from that below. But after this point
I
> am out of my league. Is the output from FindPart enough to restore the
> partitions? I am not concerned with the data on the OS partition. I am
> fine with having to reinstall the OS. It's the data on the other 2 drives
> that I am interested in. Can someone please guide me through this?
>

Hi,

If Svend doesn't reply you may want to try DiskPatch from
www.diydatarecovery.nl

--
Joep

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Annika K" <none@none.com> wrote in message news:SpidnQdszJJyOa7fRVn-hA@comcast.com
> "Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message news:39hl1fF62hpi8U1@individual.net...
>
> > Recreating the first EMBR may return access to drive E:
> > Drive D: is lost.

> Thank you, Folkert. Do I use ptedit to recreate the EMBR?

That is what I prefer.

> I read instructions on this page
> http://www.warpdoctor.org/walter/articles/2000/aa061400a.html
> that say to change the type column from 0F to 05.

> Is this what i need to do?

Possibly. I have no idea what that is about without further examination.

Lines copied from other post, for reference:

Disk: 1 Cylinders: 24792 Heads: 255 Sectors: 63 MB: 194474

Partitions according to partition bootrecords on first harddisk:
--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 - 0C 63 19534977 9538 0 1 1 1215 254 63 B OK
8511 1 0B 63 261554202 127712 8511 1 1 24791 254 63 OK OK

Partitions according to partition tables on first harddisk:
--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK OK
0 2 0F 19535040 378748440 184935 1216 0 1 24791 254 63 OK

Punch the EMBR (extended partition MBR) button in the opening screen and
put most of the info of this line:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
8511 1 0B 63 261554202 127712 8511 1 1 24791 254 63 OK OK

into line 2 of the new tables presented, like so:

type: 0F starting*: 8511 0 1, ending*: 24791 254 63, sectors before: xxxxxxxxx, sectors: 261554202,
where xxxxxxxxx = (8510+1)*(254+1)*63 = 136729215 (Cylinders and heads are 0-based)
* Starting and ending CHS will not be accepted for cylinders over 1023, you can fill
in the maximum CHS that is allowed for them: 1023 254 63, i.e. large drive placeholders.

If all is well then ptedit should now let you go to the next EMBR for the just defined
(2nd) extended partition and show you the logical (E in it, as represented by:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
8511 1 0B 63 261554202 127712 8511 1 1 24791 254 63 OK OK

and you should be able to open the bootrecord.

Next:
You can combine the info of these 2 lines to recreate the *first* line
(for the logical (D drive in this first Extended partition ):

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 2 0F 19535040 378748440 184935 1216 0 1 24791 254 63 OK
8511 1 0B 63 261554202 127712 8511 1 1 24791 254 63 OK OK

like so:
type: 0B, starting*: 1216 1 1, ending*: 8510 254 63, sectors before: 63, sectors: xxxxxxxxx,
where xxxxxxxxx = ((8511-1216)*255*63)-63 = 117194112
And with the same proviso for starting and ending CHS as before.

This will now be the D: logical but the bootrecord is likely toast.

If you can recreate your partition with same size on an other drive
and format it you could copy the bootrecord parameters from there
and input them here and see what gives. It could be that that may
give other apps like WinHEX enough to recognize directories and
such (if still there) and perhaps let you copy files and/or directories.


Another side note (to help better understand what we are doing above):

With microsoft there are usually 2 partitions: 1 primary, one extended.
You can see an extended partition as an description of "the rest".
Each extended can have another primary and another extended, which in
turn has .... and so on and so on. The last extended only has the last primary.
The primaries in the extendeds we call logicals.

The description of the extended partition serves as a link and the "sectors
before" are referenced against the start of the physical drive (sector 0).
"Sectors" are the remaining sectors on the physical drive.
Primaries are referenced logically against the start of the extended
partition (the EMBR), usually a track distance so usually 63 sectors.
"Sectors" here is the size of the logical drive.

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

Here is my plan of attack...Please look it over and correct any
misunderstandings that I may have...

First of all, here is the First PTEdit screen before I make any changes....

Starting Ending Sectors
Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
------------------------------------------------------------------
0C 80 0 1 1 191 254 63 63 19534977
0F 00 192 0 1 215 254 63 19535040 378748440

Then, after I click Goto EPBR the screen looks like this (before
modification)...

Starting Ending Sectors
Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
------------------------------------------------------------------
FF 10 414 171 13 4 12 30 2565263962 1872013011
0D BC 737 20 54 586 155 24 715414953 2356450195
C1 9F 473 187 57 97 150 29 2960922799 89931260
51 33 158 72 17 302 240 1 886023102 2723627765

At this stage, I am supposed to change the second line so that the screen
looks like this...

Starting Ending Sectors
Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
--------------------------------------------------------------------
FF 10 414 171 13 4 12 30 2565263962 1872013011
0F BC 1023 254 63 1023 254 63 19535040 261554202
C1 9F 473 187 57 97 150 29 2960922799 89931260
51 33 158 72 17 302 240 1 886023102 2723627765

....using CHS 1023,245,63 instead of the actual values because the cylinder
is over 1023 (is that correct? I'm unsure on this) and following Joep's
suggestions to use Type: 0F and "Sectors Before":19535040 (What about the
boot field? do I leave that BC?)

Then I click "Save Changes"
Then I click "Goto EPBR" for the 2nd line (the one i just modified)
Then I change the first line of the resulting screen to look like this

Starting Ending Sectors
Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
--------------------------------------------------------------------
0B ?? 1023 254 63 1023 254 63 63 117194112

Again using CHS 1023,254,63 (What about the boot field here?)

Then I click Save changes and exit the program
Then i try booting the machine? I'm afraid

Thanks very much for your time in this matter.

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

Hi... If you had installed Windows 98 on this HD you should be able to
see 2 files SUHODLOG.DAT and SUHODLOG.BAK in rott of C:\ these are
hidden system files. Send me these two files and I will send you your
original Partition table along with a restoration utility developed by
me.

Best regards
Tanmoy Banerjee

Annika K wrote:
> I am runing Windows 98 on a 200 Gig HD. There are 3 partitions on
the HD.
> One is about 10 gigs and holds the operating system. Yesterday the
other
> two partitions disappered while windows was running. So far I have
rebooted
> a couple of times (before i realized what was going on) and attempted
to fix
> the mbr with "FDISK /MBR" which did not fix the problem. I have run
> FindPart and will include the ouput from that below. But after this
point I
> am out of my league. Is the output from FindPart enough to restore
the
> partitions? I am not concerned with the data on the OS partition. I
am
> fine with having to reinstall the OS. It's the data on the other 2
drives
> that I am interested in. Can someone please guide me through this?
>
> Thank you very much.
>
> FindPart Output....................
>
> Findpart, version 4.42.
> Copyright Svend Olaf Mikkelsen, 1999-2004.
>
> OS: DOS 7.10
>
> Disk: 1 Cylinders: 24792 Heads: 255 Sectors: 63 MB: 194474
>
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 0 - 0C 63 19534977 9538 0 1 1 1215 254 63 B OK
> 8511 1 0B 63261554202127712 8511 1 1 24791 254 63 OK OK
>
> ------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
> 0 1 33 9530 8 2 9530 0 0 0 05-03-07 454
> 8511 1 33 31921 32 2 31921 0 0 0 05-02-21 75808
> 13317 0 33 Second FAT not found.
>
> Partitions according to partition tables on first harddisk:
>
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK OK
> 0 2 0F 19535040378748440184935 1216 0 1 24791 254 63 OK
>
> No signature CHS: 1216 0 1

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Annika K" <none@none.com> wrote in message news:cKednaSILMz1RKnfRVn-tQ@comcast.com
> Here is my plan of attack...Please look it over and correct any misunderstandings
> that I may have...
>
> First of all, here is the First PTEdit screen before I make any changes....
>
> Starting Ending Sectors
> Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
> ------------------------------------------------------------------
> 0C 80 0 1 1 191 254 63 63 19,534,977
> 0F 00 192 0 1 215 254 63 19535040 378,748,440

Hmm.

" > 0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK OK "
" > 0 2 0F 19535040 378748440 184935 1216 0 1 24791 254 63 OK "

Findpart seems to have a mind of it's own. Svend should look into that.

>
> Then, after I click Goto EPBR the screen looks like this (before modification)...
>
> Starting Ending Sectors
> Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
> ------------------------------------------------------------------
> FF 10 414 171 13 4 12 30 2565263962 1872013011
> 0D BC 737 20 54 586 155 24 715414953 2356450195
> C1 9F 473 187 57 97 150 29 2960922799 89931260
> 51 33 158 72 17 302 240 1 886023102 2723627765
>
> At this stage, I am supposed to change the second line so that the screen
> looks like this...
>
> Starting Ending Sectors
> Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
> --------------------------------------------------------------------
> FF 10 414 171 13 4 12 0 2565263962 1872013011
> 0F BC 1023 254 63 1023 254 63 19535040 261554202
> C1 9F 473 187 57 97 150 29 2960922799 89931260
> 51 33 158 72 17 302 240 1 886023102 2723627765

You can clear lines 3 and 4 if you want.

>
> ...using CHS 1023,245,63 instead of the actual values because the cylinder
> is over 1023

> (is that correct? I'm unsure on this)

Yes, that is correct. The "actual" values aren't really actual, they are con-
verted/recalculated (but invalid) CHS representations of the LBA values.
They don't actually exist and can't be actually used in bios or driver
routines because CHS doesn't exist beyond 8GB (1024*256*63*512).

> and following Joep's suggestions to use Type: 0F and "Sectors Before":19535040

No, it should be my original value (136729215) but minus that 19535040 of the
first original primary which makes 117194175.

> (What about the boot field? do I leave that BC?)

You may clear that.

>
> Then I click "Save Changes"
> Then I click "Goto EPBR" for the 2nd line (the one i just modified)

You don't have to, you just check that you can and then you return, or you can leave it.
And you don't have to position the cursor, Goto EPBR just goes to the next
EPBR in the chain, like Goto Parent will return you to the previous one.

> Then I change the first line of the resulting screen to look like this

No, you return (Goto Parent) if you *did* go to the next EPBR to check if it's working.
As I said, the 3rd logical should be OK so you are not going to change anything there.
We will change the first line in the same screen where we changed that second line.

>
> Starting Ending Sectors
> Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
> --------------------------------------------------------------------
> 0B ?? 1023 254 63 1023 254 63 63 117194112
>
> Again using CHS 1023,254,63 (What about the boot field here?)

You may clear it.
You may also clear any unused lines that have rubbish in them.

>
> Then I click Save changes and exit the program
> Then i try booting the machine? I'm afraid
>
> Thanks very much for your time in this matter.

And it is taking more time than I expected it would. I must try and remember
how tricky it is and how easy you can make a mistake if you can't dry run it.
It's probably easier if you draw the screens on paper and check the
columns against each other than to try keeping it all in ones head.
Your constant removal of previous quotation doesn't make the process any
snappier either.

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

Time for another "oops".

"Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message news:39jl2lF61mflsU1@individual.net
> "Annika K" <none@none.com> wrote in message news:SpidnQdszJJyOa7fRVn-hA@comcast.com
> > "Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message news:39hl1fF62hpi8U1@individual.net...
> >
> > > Recreating the first EMBR may return access to drive E:
> > > Drive D: is lost.
>
> > Thank you, Folkert. Do I use ptedit to recreate the EPBR?
>
> That is what I prefer.
>
> > I read instructions on this page
> > http://www.warpdoctor.org/walter/articles/2000/aa061400a.html
> > that say to change the type column from 0F to 05.
>
> > Is this what i need to do?
>
> Possibly. I have no idea what that is about without further examination.
>
> Lines copied from other post, for reference:
>
> Disk: 1 Cylinders: 24792 Heads: 255 Sectors: 63 MB: 194474
>
> Partitions according to partition bootrecords on first harddisk:
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 0 - 0C 63 19534977 9538 0 1 1 1215 254 63 B OK
> 8511 1 0B 63 261554202 127712 8511 1 1 24791 254 63 OK OK
>
> Partitions according to partition tables on first harddisk:
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK OK
> 0 2 0F 19535040 378748440 184935 1216 0 1 24791 254 63 OK
>
> Punch the EPBR (Extended Partition mBR) button in the opening screen and
> put most of the info of this line:
>
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 8511 1 0B 63 261554202 127712 8511 1 1 24791 254 63 OK OK
>
> into line 2 of the new tables presented, like so:
>
> type: 0F starting*: 8511 0 1, ending*: 24791 254 63, sectors before: xxxxxxxxx, sectors: 261554202,

> where xxxxxxxxx = (8510+1)*(254+1)*63 = 136729215 (Cylinders and heads are 0-based)

So with the correction below in mind we have to correct for the space taken up by the primary partition:
136729215-19535040 = 117194175

> * Starting and ending CHS will not be accepted for cylinders over 1023, you can fill
> in the maximum CHS that is allowed for them: 1023 254 63, i.e. large drive placeholders.
>
> If all is well then ptedit should now let you go to the next EPBR for the just defined
> (2nd) extended partition and show you the logical (E in it, as represented by:
>
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 8511 1 0B 63 261554202 127712 8511 1 1 24791 254 63 OK OK
>
> and you should be able to open the bootrecord.
>
> Next:
> You can combine the info of these 2 lines to recreate the *first* line
> (for the logical (D drive in this first Extended partition ):
>
> --PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 0 2 0F 19535040 378748440 184935 1216 0 1 24791 254 63 OK
> 8511 1 0B 63 261554202 127712 8511 1 1 24791 254 63 OK OK
>
> like so:
> type: 0B, starting*: 1216 1 1, ending*: 8510 254 63, sectors before: 63, sectors: xxxxxxxxx,
> where xxxxxxxxx = ((8511-1216)*255*63)-63 = 117194112
> And with the same proviso for starting and ending CHS as before.
>
> This will now be the D: logical but the bootrecord is likely toast.
>
> If you can recreate your partition with same size on an other drive
> and format it you could copy the bootrecord parameters from there
> and input them here and see what gives. It could be that that may
> give other apps like WinHEX enough to recognize directories and
> such (if still there) and perhaps let you copy files and/or directories.
>
>
> Another side note (to help better understand what we are doing above):
>
> With microsoft there are usually 2 partitions: 1 primary, one extended.
> You can see an extended partition as a description of "the rest".
> Each extended can have another primary and another extended, which in
> turn has .... and so on and so on. The last extended only has the last primary.
> The primaries in the extendeds we call logicals.
>
> The description of the extended partition serves as a link and the "sectors
> before" are referenced against the start of the physical drive (sector 0).

Oops, that's wrong, It's relative to a single point, but it is not sector 0.
It's relative to the start of the original extended partition, the disk address
of the first EPBR.

> "Sectors" are the remaining sectors on the physical drive.

> Primaries are referenced logically against the start of the extended
> partition (the EPBR), usually a track distance so usually 63 sectors.
> "Sectors" here is the size of the logical drive.

 

[joeP]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message
news:39kq20F61udc5U2@individual.net...
>
> And it is taking more time than I expected it would. I must try and
remember
> how tricky it is and how easy you can make a mistake if you can't dry run
it.
> It's probably easier if you draw the screens on paper and check the
> columns against each other than to try keeping it all in ones head.
> Your constant removal of previous quotation doesn't make the process any
> snappier either.

Not trying to be a smart-ass (it's hard) I'd like to make one suggestion:

Re-type your instructions from scratch so there's one nicely formatted email
with only correct values.

--
Joepie

 

[joeP]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Tanmoy" <datarecovery@hotpop.com> wrote in message
news:1110811350.377546.165830@o13g2000cwo.googlegroups.com...
> Hi... If you had installed Windows 98 on this HD you should be able to
> see 2 files SUHODLOG.DAT and SUHODLOG.BAK in rott of C:\

Ah! in the rott! Splendid! And isn't that SUHDLOG.DAT?

> these are
> hidden system files. Send me these two files and I will send you your
> original Partition table

Partition locations are already known. Read the rest of the thread.

--
Joepie

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

I suggest you use partition table doctor.It provides very useful
functions: Backup partition table, Restore partition table, Rebuild
partition table, undelete partition,Fixboot.
use rebuild partition table function,it can automatic find out harddisk
partition!
see more:http://www.ptdd.com

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Joep" <available@request.nl> wrote in message news:d5938$42358b61$3eddca68$5823@nf1.news-service.com
> "Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message news:39kq20F61udc5U2@individual.net...
> >
> > And it is taking more time than I expected it would. I must try and remember
> > how tricky it is and how easy you can make a mistake if you can't dry run it.
> > It's probably easier if you draw the screens on paper and check the
> > columns against each other than to try keeping it all in ones head.
> > Your constant removal of previous quotation doesn't make the process any
> > snappier either.
>
> Not trying to be a smart-ass (it's hard)

And failing.

> I'd like to make one suggestion:
>
> Re-type your instructions from scratch so there's one nicely formatted email
> with only correct values.

Well, what holds you back to do that yourself and take the credit?

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

That was a typographical mistake. I guess everyone could make out its
not rott but root. Regarding the issue of Partition locations, agreed
its known but how does a layman restore it? assuming he/she does not
know how to edit physical sectors manually. Moreover the structrure of
Boot Record is not known, so I asked for the SUHDLOG.DAT file.

Joep wrote:
> "Tanmoy" <datarecovery@hotpop.com> wrote in message
> news:1110811350.377546.165830@o13g2000cwo.googlegroups.com...
> > Hi... If you had installed Windows 98 on this HD you should be able
to
> > see 2 files SUHODLOG.DAT and SUHODLOG.BAK in rott of C:\
>
> Ah! in the rott! Splendid! And isn't that SUHDLOG.DAT?

that was a typographical mistake. I guess everyone could make out its
not rott but root.
>
> > these are
> > hidden system files. Send me these two files and I will send you
your
> > original Partition table
>
> Partition locations are already known. Read the rest of the thread.

Regarding the issue of Partition location, agreed its known but how
does a layman restore it? assuming he/she does not know how to edit
physical sectors manually. Moreover the structrure of Boot Record is
not known, so I asked for the SUHDLOG.DAT file

> --
> Joepie

 

[joeP]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message
news:39ms0vF6291kuU1@individual.net...
> "Joep" <available@request.nl> wrote in message
news:d5938$42358b61$3eddca68$5823@nf1.news-service.com
> > "Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message
news:39kq20F61udc5U2@individual.net...
> > >
> > > And it is taking more time than I expected it would. I must try and
remember
> > > how tricky it is and how easy you can make a mistake if you can't dry
run it.
> > > It's probably easier if you draw the screens on paper and check the
> > > columns against each other than to try keeping it all in ones head.
> > > Your constant removal of previous quotation doesn't make the process
any
> > > snappier either.
> >
> > Not trying to be a smart-ass (it's hard)
>
> And failing.

lol. dumb-ass!

>
> > I'd like to make one suggestion:
> >
> > Re-type your instructions from scratch so there's one nicely formatted
email
> > with only correct values.
>
> Well, what holds you back to do that yourself and take the credit?

Hahaha! do it yourself Volkert!

--
Joepie

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Tanmoy" <datarecovery@hotpop.com> wrote in message news:1110878033.904879.271150@f14g2000cwb.googlegroups.com
> That was a typographical mistake.

No, that were several. One would be an unfortunate mistake but
several gives insight in how much you can be trusted with ones data
if you can't even be bothered to check your posts before sending.

> I guess everyone could make out its not rott but root.
> Regarding the issue of Partition locations, agreed
> its known but how does a layman restore it? assuming he/she does not
> know how to edit physical sectors manually.

Not only can you barely write, you don't read very well either, don't
you, "Tanmoy". Who said anything about editing "physical sectors".

> Moreover the structrure of Boot Record is not known, so I asked
> for the SUHDLOG.DAT file.

Oh, and my SUHDLOG.DAT is 3 years old. I have had several HDs
since then and I'm 100% certain that my current one (36GB) is par-
titioned differently from when I originally installed on a 4 GB one.
I would most certainly destroy my system if I followed your advice.

>
> Joep wrote:
> > "Tanmoy" datarecovery@hotpop.com> wrote in message news:1110811350.377546.165830@o13g2000cwo.googlegroups.com...
> > > Hi... If you had installed Windows 98 on this HD you should be able to
> > > see 2 files SUHODLOG.DAT and SUHODLOG.BAK in rott of C:\
> >
> > Ah! in the rott! Splendid! And isn't that SUHDLOG.DAT?
>
> that was a typographical mistake. I guess everyone could make out its
> not rott but root.
> >
> > > these are
> > > hidden system files. Send me these two files and I will send you your
> > > original Partition table
> >
> > Partition locations are already known. Read the rest of the thread.
>
> Regarding the issue of Partition location, agreed its known but how
> does a layman restore it? assuming he/she does not know how to edit
> physical sectors manually. Moreover the structrure of Boot Record is
> not known, so I asked for the SUHDLOG.DAT file
>
> > --
> > Joepie

 

[joeP]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

"Tanmoy" <datarecovery@hotpop.com> wrote in message
news:1110878033.904879.271150@f14g2000cwb.googlegroups.com...
> That was a typographical mistake. I guess everyone could make out its
> not rott but root. Regarding the issue of Partition locations, agreed
> its known but how does a layman restore it? assuming he/she does not
> know how to edit physical sectors manually. Moreover the structrure of
> Boot Record is not known, so I asked for the SUHDLOG.DAT file.
>

Hi.

Yes, you are right, it's just, we see here (this thread) a living example of
what could happen if you're not exact and to the point with the instructions
you give. And in that light, not even getting a simple thing as a filename
right doesn't add to the confidence. Yes indeed the bootrecord appears to be
lost, and I very much doubt if that's the only component that's damaged; the
partition table EPBR was trashed, the boot sector as well, no FAT was found
so part of the first FAT at least is damaged as well. And because of that I
doubt if knowing what the boot sector looked like will do much good. If this
were up to me, I'd try the recover the last logical and recover data from
the first logical partition using a file recovery tool. You could even
redefine the partition to make it a little easier on the tool of your
choice.

As far as I understand the files you refer to are created during setup. If
the partitioning changed since that there's not too much use for those
files. In fact data has been lost more than once because of those files and
the restoration of partition tables and boot sectors from those files.
Because of that I'd never rely on them. IMO it's better to scan a disk,
analyse the results of the scan, and plan and perform interventions based on
at analysis.

Does one know how to use the information as it is presented by Findpart?
Yes, that's the question. Either you know, or you don't. The latter seems to
be the case more frequently, and in those cases 99 out of 100 times Svend
has to come to the rescue. Svend recently indicated that he's slowing down a
bit, or has to slow down a bit, because there's so many requests for help
that he fears he may not be able to maintain the high quality of his
support. Svend has a reputation to keep up ;-). It is also because of this
reputation, so it seems, that people trust him blindly to resolve an issue,
or at least that he knows where and when to stop so it doesn't turn into a
bigger mess. I know what Svend is capable of (as anyone that visits this
group on a regular basis probably). If Svend created a batch file to fix my
disk I'd not have too much trouble running that. No offense intended, but
you I don't know, so that's a bit more difficult. F'Nut (alias Folkert) I do
know and I'd never let him touch my disk, before you know it, you have 'free
space partitions' (don't ask me, only he knows) all over the place.

Anyway ... There are tools available that are able to resolve many of the
issues that can be resolved with the help of Findpart and Svend in a safe
manner. Tools that allow about ordinary users to solve issues even when they
don't know how to edit a disk and without indepth knowledge on partition
table and boot sector structures. Tools that only require the user to select
the correct disk and the partitions that need repair.

If people do not want to use those (often commercial) tools then they either
need to be patient or take some risks. I suggest they first clone the victim
disk or practice on a dummy disk.

--
Joep
http://www.diydatarecovery.nl

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

Thank you very much for your help. Using my "modified" plan of attack I was
able to restore the E: drive (and this is the one that was of most
importance to me). When I try to select the D: drive I get an error message
which reads "D:\ is not accessible. A device attached to the system is not
functioning." At this stage, do I give up on the data on that partition?
What other options are still available to me?

For those who are interested, here is what my PTEdit screen looked like in
the end...(I didn't bother removing the 3rd and 4th lines as that seemed
optional)

Starting Ending Sectors
Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
------------------------------------------------------------------
0B 1023 254 63 1023 254 63 63 117194112
05 1023 254 63 1023 254 63 117194175 261554202
C1 9F 473 187 57 97 150 29 2960922799 89931260
51 33 158 72 17 302 240 1 886023102 2723627765



"Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message
news:39kq20F61udc5U2@individual.net...
> "Annika K" <none@none.com> wrote in message
> news:cKednaSILMz1RKnfRVn-tQ@comcast.com
>> Here is my plan of attack...Please look it over and correct any
>> misunderstandings
>> that I may have...
>>
>> First of all, here is the First PTEdit screen before I make any
>> changes....
>>
>> Starting Ending Sectors
>> Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
>> ------------------------------------------------------------------
>> 0C 80 0 1 1 191 254 63 63
>> 19,534,977
>> 0F 00 192 0 1 215 254 63 19535040
>> 378,748,440
>
> Hmm.
>
> " > 0 1*0C 63 19534977 9538 0 1 1 1215 254 63 OK
> OK "
> " > 0 2 0F 19535040 378748440 184935 1216 0 1 24791 254 63
> OK "
>
> Findpart seems to have a mind of it's own. Svend should look into that.
>
>>
>> Then, after I click Goto EPBR the screen looks like this (before
>> modification)...
>>
>> Starting Ending Sectors
>> Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
>> ------------------------------------------------------------------
>> FF 10 414 171 13 4 12 30 2565263962
>> 1872013011
>> 0D BC 737 20 54 586 155 24 715414953
>> 2356450195
>> C1 9F 473 187 57 97 150 29 2960922799
>> 89931260
>> 51 33 158 72 17 302 240 1 886023102
>> 2723627765
>>
>> At this stage, I am supposed to change the second line so that the screen
>> looks like this...
>>
>> Starting Ending Sectors
>> Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
>> --------------------------------------------------------------------
>> FF 10 414 171 13 4 12 0 2565263962
>> 1872013011
>> 0F BC 1023 254 63 1023 254 63 19535040
>> 261554202
>> C1 9F 473 187 57 97 150 29 2960922799
>> 89931260
>> 51 33 158 72 17 302 240 1 886023102
>> 2723627765
>
> You can clear lines 3 and 4 if you want.
>
>>
>> ...using CHS 1023,245,63 instead of the actual values because the
>> cylinder
>> is over 1023
>
>> (is that correct? I'm unsure on this)
>
> Yes, that is correct. The "actual" values aren't really actual, they are
> con-
> verted/recalculated (but invalid) CHS representations of the LBA values.
> They don't actually exist and can't be actually used in bios or driver
> routines because CHS doesn't exist beyond 8GB (1024*256*63*512).
>
>> and following Joep's suggestions to use Type: 0F and "Sectors
>> Before":19535040
>
> No, it should be my original value (136729215) but minus that 19535040 of
> the
> first original primary which makes 117194175.
>
>> (What about the boot field? do I leave that BC?)
>
> You may clear that.
>
>>
>> Then I click "Save Changes"
>> Then I click "Goto EPBR" for the 2nd line (the one i just modified)
>
> You don't have to, you just check that you can and then you return, or you
> can leave it.
> And you don't have to position the cursor, Goto EPBR just goes to the next
> EPBR in the chain, like Goto Parent will return you to the previous one.
>
>> Then I change the first line of the resulting screen to look like this
>
> No, you return (Goto Parent) if you *did* go to the next EPBR to check if
> it's working.
> As I said, the 3rd logical should be OK so you are not going to change
> anything there.
> We will change the first line in the same screen where we changed that
> second line.
>
>>
>> Starting Ending Sectors
>> Type Boot Cyl Head Sector Cyl Head Sector Before Sectors
>> --------------------------------------------------------------------
>> 0B ?? 1023 254 63 1023 254 63 63
>> 117194112
>>
>> Again using CHS 1023,254,63 (What about the boot field here?)
>
> You may clear it.
> You may also clear any unused lines that have rubbish in them.
>
>>
>> Then I click Save changes and exit the program
>> Then i try booting the machine? I'm afraid
>>
>> Thanks very much for your time in this matter.
>
> And it is taking more time than I expected it would. I must try and
> remember
> how tricky it is and how easy you can make a mistake if you can't dry run
> it.
> It's probably easier if you draw the screens on paper and check the
> columns against each other than to try keeping it all in ones head.
> Your constant removal of previous quotation doesn't make the process any
> snappier either.

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

Folkert Rienstra wrote:
> "Tanmoy" <datarecovery@hotpop.com> wrote in message
news:1110878033.904879.271150@f14g2000cwb.googlegroups.com
> > That was a typographical mistake.
>
> No, that were several. One would be an unfortunate mistake but
> several gives insight in how much you can be trusted with ones data
> if you can't even be bothered to check your posts before sending.
>
> > I guess everyone could make out its not rott but root.
> > Regarding the issue of Partition locations, agreed
> > its known but how does a layman restore it? assuming he/she does
not
> > know how to edit physical sectors manually.
>
> Not only can you barely write, you don't read very well either, don't

> you, "Tanmoy". Who said anything about editing "physical sectors".
>
> > Moreover the structrure of Boot Record is not known, so I asked
> > for the SUHDLOG.DAT file.
>
> Oh, and my SUHDLOG.DAT is 3 years old. I have had several HDs
> since then and I'm 100% certain that my current one (36GB) is par-
> titioned differently from when I originally installed on a 4 GB one.
> I would most certainly destroy my system if I followed your advice.

I guess its time you learn to read well too ! in my earlier post I said

if you had installed Windows 98 on this HD (and not cloned from another
drive OK). It doesnt matter if its 3 yrs old installation as long as
you did not change the partition structure.

I hope you would agree that what findpart or any other utility reports
is the present partition structure, and many virus do alter the
structure of the partition table. Till date I havent come across any
that alters SUHDLOG.DAT. (let me know if there is one whic alters
SUHDLOG.DAT)

If there is no partition alteration after installation of WIN98 and you
know to extract the partition and Boot Record out of SUHDLOG.DAT, I
doubt if there is any other better utilty to recreate the original
ones.

>
> >
> > Joep wrote:
> > > "Tanmoy" datarecovery@hotpop.com> wrote in message
news:1110811350.377546.165830@o13g2000cwo.googlegroups.com...
> > > > Hi... If you had installed Windows 98 on this HD you should be
able to
> > > > see 2 files SUHODLOG.DAT and SUHODLOG.BAK in rott of C:\
> > >
> > > Ah! in the rott! Splendid! And isn't that SUHDLOG.DAT?
> >
> > that was a typographical mistake. I guess everyone could make out
its
> > not rott but root.
> > >
> > > > these are
> > > > hidden system files. Send me these two files and I will send
you your
> > > > original Partition table
> > >
> > > Partition locations are already known. Read the rest of the
thread.
> >
> > Regarding the issue of Partition location, agreed its known but how
> > does a layman restore it? assuming he/she does not know how to edit
> > physical sectors manually. Moreover the structrure of Boot Record
is
> > not known, so I asked for the SUHDLOG.DAT file
> >
> > > --
> > > Joepie

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

I suggest you use partition table doctor.It provides very useful
functions: Backup partition table, Restore partition table, Rebuild
partition table, undelete partition,Fixboot.
see more:http://www.ptdd.com/recoverylostpartition.htm