Partition Recovery with Drive Geometry Problem
Karl Korsch
is detected in BIOS but not in Windows (no drive letter). I ran Norton Disk
Doctor and it reported: "Disk 2 14676 187/C 255h 63s appears to have
partitions created using a different drive geometry (1h 58s)...". When it
then tried to fix it the drive it ran out of disk space and said the
partition needed to be backed up before trying to reconstruct the partition.
Unfortunately I get errors whenever I try to image or copy the partition.
Easy Recovery Pro found no physical errors on the drive, just a messed up
partition. I managed to recover a few files using raw recovery mode, but
file names and lots of critical files that weren't in contiguous file blocks
can't be recovered in this mode.
Is there a way to safely restore this partition data, FAT or whatever has
been damaged? (below are the results of Partition Magic's PartitionInfo):
==========================================
PowerQuest PartitionInfo 7.0 -- Windows NT/2000 Version
Date Generated: 08/27/02 16:35:38
General System Information:
Total Physical Memory (bytes): 200,761,344
Used Physical Memory: (bytes): 146,718,720
Maximum Page File Size: (bytes): 502,816,768
Current Page File Size: (bytes): 192,987,136
============================================================================
===============================
Disk Geometry Information for Disk 1: 7476 Cylinders, 255 Heads, 63
Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect
StartSect NumSects
============================================================================
===============================
0 0 80 0 1 1 0C 1023 254 63
63 120,085,812
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 80 0 1 1 0C 7474 254 63 63 120085812
============================================================================
===============================
Disk Geometry Information for Disk 2: 1871 Cylinders, 255 Heads, 63
Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect
StartSect NumSects
============================================================================
===============================
0 0 1C 415 0 49 1C 415 0
502,675,114,0122,677,932,060
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 1C 166518 37 12 1C 65862 91 1326751140122677932060
Warning: Partition boot flag expected to be 0x00 or 0x80,
not 0x1C. This should not be a problem.
Error #107: Partition begins after end of disk.
ucBeginCylinder (166518) must be less than 1871.
Error #105: Partition didn't begin on head boundary.
ucBeginHead expected to be 0 or 1, not 37.
Error #106: Partition didn't begin on head boundary.
ucBeginSector expected to be 1, not 12.
Error #109: Partition ends after end of disk.
ucEndCylinder (65862) must be less than 1871.
Error #108: Partition didn't end on cylinder boundary.
ucEndHead expected to be 254, not 91.
Error #108: Partition didn't end on cylinder boundary.
ucEndSector expected to be 63, not 13.
0 1 1C 415 0 53 1C 415 0
542,675,638,3002,678,390,812
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 1C 166550 199 14 1C 65923 140 126756383002678390812
Warning: Partition boot flag expected to be 0x00 or 0x80,
not 0x1C. This should not be a problem.
Error #107: Partition begins after end of disk.
ucBeginCylinder (166550) must be less than 1871.
Error #105: Partition didn't begin on head boundary.
ucBeginHead expected to be 0 or 1, not 199.
Error #106: Partition didn't begin on head boundary.
ucBeginSector expected to be 1, not 14.
Error #109: Partition ends after end of disk.
ucEndCylinder (65923) must be less than 1871.
Error #108: Partition didn't end on cylinder boundary.
ucEndHead expected to be 254, not 140.
Error #108: Partition didn't end on cylinder boundary.
ucEndSector expected to be 63, not 1.
0 2 1C 415 0 57 1C 415 0
582,692,546,5882,675,703,836
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 2 1C 167603 69 47 1C 66808 200 826925465882675703836
Warning: Partition boot flag expected to be 0x00 or 0x80,
not 0x1C. This should not be a problem.
Error #107: Partition begins after end of disk.
ucBeginCylinder (167603) must be less than 1871.
Error #105: Partition didn't begin on head boundary.
ucBeginHead expected to be 0 or 1, not 69.
Error #106: Partition didn't begin on head boundary.
ucBeginSector expected to be 1, not 47.
Error #109: Partition ends after end of disk.
ucEndCylinder (66808) must be less than 1871.
Error #108: Partition didn't end on cylinder boundary.
ucEndHead expected to be 254, not 200.
Error #108: Partition didn't end on cylinder boundary.
ucEndSector expected to be 63, not 8.
0 3 1C 415 0 61 1C 415 0
622,675,900,4442,675,965,980
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 3 1C 166567 25 15 1C 65788 236 4026759004442675965980
Warning: Partition boot flag expected to be 0x00 or 0x80,
not 0x1C. This should not be a problem.
Error #107: Partition begins after end of disk.
ucBeginCylinder (166567) must be less than 1871.
Error #105: Partition didn't begin on head boundary.
ucBeginHead expected to be 0 or 1, not 25.
Error #106: Partition didn't begin on head boundary.
ucBeginSector expected to be 1, not 15.
Error #109: Partition ends after end of disk.
ucEndCylinder (65788) must be less than 1871.
Error #108: Partition didn't end on cylinder boundary.
ucEndHead expected to be 254, not 236.
Error #108: Partition didn't end on cylinder boundary.
ucEndSector expected to be 63, not 40.
============================================================================
===============================
Partition Information for Disk 1: 58,643.5 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects UsedSects FreeSects
============================================================================
===============================
C: FAT32X Pri,Boot 58,635.7 0 0 63
120,085,812 120,085,812 0
Unallocated Pri 7.8 None -- 120,085,875
16,065 0 16,065
============================================================================
===============================
Partition Information for Disk 2: 14,676.6 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects UsedSects FreeSects
============================================================================
===============================
Unallocated Pri 14,676.5 None -- 63
30,057,552 0 30,057,552
Unallocated Pri 1,291,531.4 None --
30,057,6152,645,056,397 02,645,056,397
Unallocated Pri 798,653.3
None --1,056,900,2851,635,641,910 01,635,641,910
Unallocated Pri 789,812.8
None --1,058,089,0951,617,536,655 01,617,536,655
Unallocated Pri 789,467.7
None --1,059,069,0601,616,829,795 01,616,829,795
Hid.FAT32X Pri,Boot 1,307,584.0 0
02,675,114,0122,677,932,0602,677,932,060 0
Hid.FAT32X Pri,Boot 1,307,808.0 0
12,675,638,3002,678,390,8122,678,390,812 0
Hid.FAT32X Pri,Boot 1,306,624.0 0
32,675,900,4442,675,965,9802,675,965,980 0
Hid.FAT32X Pri,Boot 1,306,496.0 0
22,692,546,5882,675,703,836 02,675,703,836
============================================================================
===============================
Boot Record for drive C: (Drive: 1, Starting sector: 63, Type: FAT32)
============================================================================
===============================
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes per Sector: 512
4. Sectors per Cluster: 64
5. Reserved Sectors: 38
6. Number of FAT's: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Big Total Sectors: 120085812 (0x7285D34)
15. Big Sectors per FAT: 14657
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x3CDF1C5B
26. Volume Name:
27. File System Type: FAT32
28. Boot Signature: 0xAA55
============================================================================
===============================
Boot Record for drive *: (Drive: 2, Starting sector: 2,675,114,012, Type:
FAT32)
============================================================================
===============================
Radish
partition information re-appears. For instance, change LBA to Large, or
vice versa.
If the recovery routines you tried actually wrote to the drive when the
geometry was wrong then there isn't much chance of getting useful data off
the drive (assuming wrong geometry really is the problem).
Is it possible that this drive had a drive manager (such as EZ BIOS)
installed? That's another reason for different geometry being applied.
"Karl Korsch" <k.ko...@softhome.net> wrote in message
news:3d6c6...@corp-news.newsgroups.com...
Svend Olaf Mikkelsen
<k.ko...@softhome.net> wrote:
>I've lost access to a hard drive with a Win98SE FAT32 partition. The drive
>is detected in BIOS but not in Windows (no drive letter). I ran Norton Disk
>Doctor and it reported: "Disk 2 14676 187/C 255h 63s appears to have
>partitions created using a different drive geometry (1h 58s)...". When it
>then tried to fix it the drive it ran out of disk space and said the
>partition needed to be backed up before trying to reconstruct the partition.
>Unfortunately I get errors whenever I try to image or copy the partition.
>
>Easy Recovery Pro found no physical errors on the drive, just a messed up
>partition. I managed to recover a few files using raw recovery mode, but
>file names and lots of critical files that weren't in contiguous file blocks
>can't be recovered in this mode.
>
>Is there a way to safely restore this partition data, FAT or whatever has
>been damaged? (below are the results of Partition Magic's PartitionInfo):
For an alternative view, you can download Findpart at
http://inet.uni2.dk/~svolaf/utilities.htm
do:
findpart all fp.txt
and insert (not attach) the output.
There are too many "1C" in the MBR, meaning that the MBR is more than
usual corrupted. From the Partinfo output it is not known if the
errors are limited to the MBR. Hardware problems is a possible
explanation, but also some software error.
--
Svend Olaf
Karl Korsch
Findpart, version 4.23 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 2002.
Searches for partitions type 01, 04, 06, 07, 0B, 0C, 0E, 82, 83,
plus Fdisk F6 and Lilo sectors. Information based on bootsectors
is marked B. If the disk is larger than supported by BIOS, the
supported part of the disk is examined. Disks are numbered from 1.
OS: Windows 5.1 All
Disk: 1 Cylinders: 7476 Heads: 255 Sectors: 63 MB: 58644
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63120085812 58635 0 1 1 7474 254 63 B OK
-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
93 1 35 Second FAT not found.
2203 0 33 Second FAT not found.
3377 0 35 Second FAT not found.
3592 0 2 Second FAT not found.
5283 1 2 Second FAT not found.
5306 1 33 Second FAT not found.
6096 0 33 Second FAT not found.
6272 0 2 Second FAT not found.
6278 1 33 Second FAT not found.
6281 1 33 Second FAT not found.
6771 1 33 Second FAT not found.
6801 1 46 Second FAT not found.
6805 1 2 Second FAT not found.
6979 0 2 Second FAT not found.
7322 0 33 Second FAT not found.
7322 1 33 Second FAT not found.
----- FAT CHS ----- LBA Confidence Distance Type Sig
0 1 39 101 13883 32 OK
0 234 17 14758 13883 14657 32 OK
Partitions according to partition tables on first harddisk:
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0C 63120085812 58635 0 1 1 7474*254 63 OK OK
Disk: 2 Cylinders: 1871 Heads: 255 Sectors: 63 MB: 14677
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63 30057552 14676 0 1 1 1870 254 63 B OK
-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 14663 8 2 14661 0 1 1 000513 14552
Partitions according to partition tables on second harddisk:
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1?1C --- --- --- 415 0 49 415 0 50 NR NB
0 2?1C --- --- --- 415 0 53 415 0 54 NR NB
0 3?1C --- --- --- 415 0 57 415 0 58 NR NB
0 4?1C --- --- --- 415 0 61 415 0 62 NR NB
Disk: 3 Cylinders: 9729 Heads: 255 Sectors: 63 MB: 76317
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63156296322 76316 0 1 1 9728 254 63 B OK
-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 19076 32 2 19076 0 0 0 020321 75416
Partitions according to partition tables on third harddisk:
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1 0C 63156296322 76316 0 1 1 9728*254 63 OK OK
Disk: 4 Cylinders: 4866 Heads: 255 Sectors: 63 MB: 38170
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63 78172227 38170 0 1 1 4865 254 63 B OK
No FATs found.
Partitions according to partition tables on fourth harddisk:
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1 0C 63 78172227 38170 0 1 1 4865*254 63 OK OK
"Svend Olaf Mikkelsen" <svo...@inet.uni2.dk> wrote in message
news:3d6c79a...@News.CIS.DFN.DE...
Zvi Netiv
> <k.ko...@softhome.net> wrote:
>
> >I've lost access to a hard drive with a Win98SE FAT32 partition. The drive
> >is detected in BIOS but not in Windows (no drive letter). I ran Norton Disk
> >Doctor and it reported: "Disk 2 14676 187/C 255h 63s appears to have
> >partitions created using a different drive geometry (1h 58s)...". When it
> >then tried to fix it the drive it ran out of disk space and said the
> >partition needed to be backed up before trying to reconstruct the partition.
> >Unfortunately I get errors whenever I try to image or copy the partition.
Hope that Norton Disk Doctor didn't make irreversible changes. NDD is fine for
fixing minor problems, of the sort that ScanDisk can fix too, but never let it
do that sort of fix!
> >Easy Recovery Pro found no physical errors on the drive, just a messed up
> >partition. I managed to recover a few files using raw recovery mode, but
> >file names and lots of critical files that weren't in contiguous file blocks
> >can't be recovered in this mode.
Unless you tried in "ignore FAT" mode, the failing of EasyRecovery to see all
files could indicate that the FAT and/or root directory were severely corrupted,
or that the current BIOS settings for the drive are different than those used
when initially partitioned. If this is the case, then you should "thank" NDD
for causing the mess, and blame your judgement for using it.
> >Is there a way to safely restore this partition data, FAT or whatever has
> >been damaged? (below are the results of Partition Magic's PartitionInfo):
If only the partition table got corrupted, then here is how to fix it:
Download RESQ from http://resq.co.il/resq.php and make a RESQ work floppy as in
the instructions. Assuming that the drive with the problem is drive 2, run
RESQDISK /KILL /2 to zero the corrupted partition table. Reboot the computer
and let the BIOS redetect drive 2, with correct BIOS settings. Boot from the
RESQ floppy, and from the A: prompt, run RESQDISK /REBUILD /FAT32 /2 (force a
FAT-32 MBR, on hard drive 2).
The above procedure operates on the MBR uniquely, and will cause no other
changes. You have nothing to lose in trying, since your MBR is a total mess
anyway.
Regards, Zvi
--
NetZ Computing Ltd. ISRAEL http://invircible.com sup...@resq.co.il
InVircible Anti-Virus Software, ResQdisk and Data Recovery Utilities
E-mail sent in reply to this post will not be considered private and
may be answered in the newsgroup.
Svend Olaf Mikkelsen
<k.ko...@softhome.net> wrote:
>Findpart, version 4.23 - for Windows 95/98/ME/NT/2000/XP.
>Copyright Svend Olaf Mikkelsen, 2002.
>OS: Windows 5.1 All
>
>Disk: 1 Cylinders: 7476 Heads: 255 Sectors: 63 MB: 58644
>
>-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
> 0 - 0C 63120085812 58635 0 1 1 7474 254 63 B OK
>
>-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
> 93 1 35 Second FAT not found.
(more like that cut, means nothing).
The partition on disk 2 seems basically OK. Two FAT sectors do not
match between first and second FAT copy. From the Findpart output I
cannot see if it is the first or the second FAT copy that is correct.
On disk 4 I do not understand why no FAT was located. If a FAT in the
beginning of the disk is not at a standard location, it should be
found anyway as on disk 1.
I suggest that the partition on disk 2 is not made visible by editing
the partition table until the FAT issues are solved.
One way to examine further is (karl1.bat):
findpart chsdir 2 0 1 33 14663 8 2 fat1 summary fp2-1a.txt
findpart chsdir 2 0 1 33 14663 8 2 fat2 summary fp2-1b.txt
The batch file is in:
http://inet.uni2.dk/~svolaf/karl1.zip
Can you see the 38170 MB partition on disk 4?
Do you have other operating systems than Windows XP installed? A 32 GB
problem in Windows 98/ME could be an explanation.
If you need some files now, you may be able to copy them in pure DOS
(without long file names) using my fp.sys device driver. Or files can
be copyied using Cyldir, which is included in Findpart for Windows.
For usage type "findpart cyldir".
--
Svend Olaf
Karl Korsch
KARL1.BAT produced what looks like the directory structure of my lost
partition. I don't think it saved the directory structure to file but I can
probably do without it. I tried using cyldir to record the directory
structure using these parameters (following the readme file):
cyldir 2 0 1 33 14663 8 2 cdir.txt
but it said disk not found. Oh well, I'm off to try your fp.sys driver to
recover some files. I'll let you know what happens. Your set of utilities
are truly fantastic.
The output of the two text files generated by KARL1.BAT are below in case
they provide further information. I'm crossing my fingers that I can at
least recover a few crucial documents, if not the entire partition.
====================================
(fp2-1a.txt:)
Chsdir, version FP 4.23.
Disk 2 CHS: 1871/255/63 FAT Location: 0/1/33
NBEXE
Total clusters: 1876862 Cluster KB: 8
Last used cluster: 1876763 Reserved: 32
FAT sectors: 14663 Root cluster: 2
FAT used clusters: 1825032 FAT entries: 31534
Used clusters: 1813674 Entries: 31540
Directories: 1891 Directories MB: 16
Files: 29649 Files MB: 13805
Partition MB: 14663 Free MB: 404
Exe count: 1112
Exe match: 1111
Used clusters do not match the FAT.
FAT copy 1 used.
NB files: 10
(fp2-1b.txt:)
Chsdir, version FP 4.23.
Disk 2 CHS: 1871/255/63 FAT Location: 0/1/33
NBEXE
Total clusters: 1876862 Cluster KB: 8
Last used cluster: 1876763 Reserved: 32
FAT sectors: 14663 Root cluster: 2
FAT used clusters: 1825029 FAT entries: 31540
Used clusters: 1825029 Entries: 31540
Directories: 1891 Directories MB: 16
Files: 29649 Files MB: 14105
Partition MB: 14663 Free MB: 404
Exe count: 1112
Exe match: 1111
FAT copy 2 used.
"Svend Olaf Mikkelsen" <svo...@inet.uni2.dk> wrote in message
news:3d7090d5...@News.CIS.DFN.DE...
Karl Korsch
First, Disk 4 is a new 40 gig hard drive which at the moment just has a few
files on it, including DOS system. I was hoping to use this for any file
recovery or partition copying from the damaged Disk 1. And yes, I can see
Disk 4 within DOS and Windows -- it gets a drive letter and it seems to work
so far.
Second, as far as other operating systems are concerned, the problem Disk 2
has Win98SE on it and was the boot disk in another system. When this drive
crashed I removed it and added it as Disk 2 to another system which uses
WinXP on its boot drive. Other than that, I suppose I have the DOS system
files installed on the 40gig Disk 4 that you were asking about.
By the way, I just got "findpart cyldir 2 0 1 33 14663 8 2 >cdir.txt" to
save the lost directory structure to file. I think it worked. Now to try
some recovering....
Please let me know if you have any ideas on how to fix the FAT and/or MBR
after some selective recovery.
Karl
Svend Olaf Mikkelsen
<k.ko...@softhome.net> wrote:
>Sorry, I forgot to answer a couple of questions.
>
>First, Disk 4 is a new 40 gig hard drive which at the moment just has a few
>files on it, including DOS system. I was hoping to use this for any file
>recovery or partition copying from the damaged Disk 1. And yes, I can see
>Disk 4 within DOS and Windows -- it gets a drive letter and it seems to work
>so far.
>
>Second, as far as other operating systems are concerned, the problem Disk 2
>has Win98SE on it and was the boot disk in another system. When this drive
>crashed I removed it and added it as Disk 2 to another system which uses
>WinXP on its boot drive. Other than that, I suppose I have the DOS system
>files installed on the 40gig Disk 4 that you were asking about.
>
>By the way, I just got "findpart cyldir 2 0 1 33 14663 8 2 >cdir.txt" to
>save the lost directory structure to file. I think it worked. Now to try
>some recovering....
>
>Please let me know if you have any ideas on how to fix the FAT and/or MBR
>after some selective recovery.
>
>Karl
You may be able to copy cdir.txt and findpart.exe to the root of the
empty partition, open a command prompt in that directory, do:
findpart cyldir 2 tree
and wait while files are copied. The Windows XP version of Cyldir
however is new, so I am not certain.
Also a DOS boot floppy with fp.sys, and the line in config.sys:
device=fp.sys 2
may provide access to the problem partition without long file names.
(It also works in Windows 95/98 with long file names, but that should
not be used now).
From the Chsdir output it is known that the second FAT copy is OK. The
partition can be repaired by copying FAT copy 2 to FAT copy 1, and
editing the partition table.
It has become too late today for me to make at batch file for that,
and also it always is nice to copy files before a repair is done.
In theory it would be enough to edit the partition table and run
Scandisk/Chkdsk, but I would not recommend that.
--
Svend Olaf
Karl Korsch
I managed to restore most all of the files by running "findpart cyldir 2
tree" under WinXP. I had to perform this within a subdirectory because when
I tried it from the root directory it said something like "directory not
found" or "problem reading directory", in case that information is of any
interest.
You've done so much for me already, though if you can find time to give some
direction in copying FAT copy 2 to FAT copy 1, or at least tell me which
utility can do this, I would really appreciate it.
"Svend Olaf Mikkelsen" <svo...@inet.uni2.dk> wrote in message
news:3d71515d...@News.CIS.DFN.DE...
Svend Olaf Mikkelsen
<k.ko...@softhome.net> wrote:
>Thank you again!
>
>I managed to restore most all of the files by running "findpart cyldir 2
>tree" under WinXP. I had to perform this within a subdirectory because when
>I tried it from the root directory it said something like "directory not
>found" or "problem reading directory", in case that information is of any
>interest.
>
>You've done so much for me already, though if you can find time to give some
>direction in copying FAT copy 2 to FAT copy 1, or at least tell me which
>utility can do this, I would really appreciate it.
Nice so far.
The Findpart commands to copy FAT copy 2 to FAT copy 1 would be
(karl2.bat):
set findpart=edit
findpart findfat 2 0 1 33 14663 fat2to1 1871
set findpart=
findpart 2 fp2-2.txt
The batch file is in
http://inet.uni2.dk/~svolaf/karl2.zip
The last parameter is the number of cylinders on the disk (for check).
I would prefer to copy the FAT, and check the result, before the
partition table is edited.
--
Svend Olaf
Karl Korsch
Findpart, version 4.23 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 2002.
Searches for partitions type 01, 04, 06, 07, 0B, 0C, 0E, 82, 83,
plus Fdisk F6 and Lilo sectors. Information based on bootsectors
is marked B. If the disk is larger than supported by BIOS, the
supported part of the disk is examined. Disks are numbered from 1.
OS: Windows 5.1
Disk: 2 Cylinders: 1871 Heads: 255 Sectors: 63 MB: 14677
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63 30057552 14676 0 1 1 1870 254 63 B OK
-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 14663 8 2 14663 0 0 0 000513 14552
Partitions according to partition tables on second harddisk:
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1?1C --- --- --- 415 0 49 415 0 50 NR NB
0 2?1C --- --- --- 415 0 53 415 0 54 NR NB
0 3?1C --- --- --- 415 0 57 415 0 58 NR NB
0 4?1C --- --- --- 415 0 61 415 0 62 NR NB
"Svend Olaf Mikkelsen" <svo...@inet.uni2.dk> wrote in message
news:3d6dafb...@News.CIS.DFN.DE...
Svend Olaf Mikkelsen
<k.ko...@softhome.net> wrote:
>Thank you again!
Since I have prepared the partition table editing, it comes here.
To make the partition visible, you can get karl3.bat in
http://inet.uni2.dk/~svolaf/karl3.zip
Copy karl3.bat to the same directory as findpart.exe, and run
karl3.bat, which contains:
set findpart=edit
findpart 2 0 1 * 0C 0 1 1 1870 254 63 0 1871 255 63 26 zero loop
set findpart=
findpart 2 table fp2-3.txt
After partition tables have been edited, Disk Management should not be
entered until after reboot.
You have the option to post the content from fp2-3.txt for
confirmation before reboot, but it should not be necessary in this
case.
--
Svend Olaf
Karl Korsch
haven't needed to. I'll feel more reassured if you think things look okay.
Findpart, version 4.23 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 2002.
OS: Windows 5.1
Disk: 2 Cylinders: 1871 Heads: 255 Sectors: 63 MB: 14677
Partitions according to partition tables on second harddisk:
-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0C 63 30057552 14676 0 1 1 1870*254 63 OK OK
"Svend Olaf Mikkelsen" <svo...@inet.uni2.dk> wrote in message
news:3d6debf...@News.CIS.DFN.DE...
Svend Olaf Mikkelsen
<k.ko...@softhome.net> wrote:
>Thanks again. Below is the output of FP2-3.TXT. I haven't rebooted yet and
>haven't needed to. I'll feel more reassured if you think things look okay.
>
>Findpart, version 4.23 - for Windows 95/98/ME/NT/2000/XP.
>Copyright Svend Olaf Mikkelsen, 2002.
>
>OS: Windows 5.1
>
>Disk: 2 Cylinders: 1871 Heads: 255 Sectors: 63 MB: 14677
>
>Partitions according to partition tables on second harddisk:
>
>-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
> 0 1*0C 63 30057552 14676 0 1 1 1870*254 63 OK OK
You can reboot and look at the result.
--
Svend Olaf
Unknown
<k.ko...@softhome.net> wrote:
>> If you need some files now, you may be able to copy them in pure DOS
>> (without long file names) using my fp.sys device driver.
There are at least three sets of tools that alllow LFNs to be used
from within DOS mode. Two are TSRs, one of which fails to create
unique 8.3 names (buggy, avoid) and the third is a set of L*
replacements for usual file commands (e.g. there are LCopy, LDir, LCD,
LDel, LRen etc.)
I must look up and get FP.SYS :-)
>--------------- ----- ---- --- -- - - -
Error Messages Are Your Friends
>--------------- ----- ---- --- -- - - -
Unknown
<k.ko...@softhome.net> wrote:
>You've done so much for me already, though if you can find time to give some
>direction in copying FAT copy 2 to FAT copy 1, or at least tell me which
>utility can do this, I would really appreciate it.
Unless you know FAT2 is good (e.g. post CIH strike, in which case
rather use Gibson's free Fix-CIH from www.grc.com) you should rather
do a hands-on FAT repair (or at least back up FAT1 first).
To do a FAT repair, I set DiskEdit to show each FAT in a separate
pane, and then compare windows. It's often obvious what has to be
sector-pasted to what between the two; when ambiguous, backup both FAT
copies first and swing both ways.
Karl Korsch
It looks like my partition has been fully restored. I can't thank you
enough!
"Svend Olaf Mikkelsen" <svo...@inet.uni2.dk> wrote in message
news:3d6e5a11...@News.CIS.DFN.DE...
Svend Olaf Mikkelsen
<k.ko...@softhome.net> wrote:
>Unbelievable!
>
>It looks like my partition has been fully restored. I can't thank you
>enough!
Nice.
Note that before the disk can be used as a boot disk, the command
"fdisk /mbr" should be run while the disk is first disk.
--
Svend Olaf
Karl Korsch
"Svend Olaf Mikkelsen" <svo...@inet.uni2.dk> wrote in message
news:3d6f126e...@News.CIS.DFN.DE...