A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Major partition problem



 
 
Thread Tools Display Modes
  #1  
Old April 23rd 06, 04:53 PM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem

Hello, All!

I used Partition Magic 8.02 to create a new 1GB partition (J, taking the
space from E:. At the end of operation, I received an error that
"...cross-linked files were found." There was no option other than to
continue. PM then called DriverMapper and it seemed to go smoothly.

On reboot, Windows Explorer shows E: and J: with no labels. When I click on
the drives, I get an error that says, "E:\ is not accessible. A device
attached to the system is not functioning."

In Device Manager on the Performance tab, it says "Drive E is using an
MS-DOS compatibility mode file system."

In DOS, ScanDisk says, "...cannot examine drive E:" I did not try J:

Also in DOS, FDisk shows E:'s size as it should (10000MB), but shows System
"Unknown" (-- it should be FAT32 --) with an 18% Usage -- which is about
right. FDisk does not show J: at all.

Partition Magic shows E: as it should -- FAT32; (new) Size: 10,001.4MB;
Used: 1150.5, set as Logical. Drive J: does not appear at all. What does
show is 1004.1MB of Unallocated space after E:; this was supposed to be the
new J: partition.

Can anybody please help? I really can't afford to lose my files on E:.
....and, of course, it's one of the partitions that I haven't backed up in
years. Don't ya sometimes just wish you never got out of bed?!!!!

Thank you in advance...
~~
Hoppy.
E-mail:


  #2  
Old April 23rd 06, 05:57 PM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem

"Hoppy" wrote in message ...
Hello, All!

I used Partition Magic 8.02 to create a new 1GB partition (J, taking the
space from E:. At the end of operation, I received an error that
"...cross-linked files were found." There was no option other than to
continue. PM then called DriverMapper and it seemed to go smoothly.

On reboot, Windows Explorer shows E: and J: with no labels. When I click on
the drives, I get an error that says, "E:\ is not accessible. A device
attached to the system is not functioning."

In Device Manager on the Performance tab, it says "Drive E is using an
MS-DOS compatibility mode file system."

In DOS, ScanDisk says, "...cannot examine drive E:" I did not try J:

Also in DOS, FDisk shows E:'s size as it should (10000MB), but shows System
"Unknown" (-- it should be FAT32 --) with an 18% Usage -- which is about
right. FDisk does not show J: at all.

Partition Magic shows E: as it should -- FAT32; (new) Size: 10,001.4MB;
Used: 1150.5, set as Logical. Drive J: does not appear at all. What does
show is 1004.1MB of Unallocated space after E:; this was supposed to be the
new J: partition.


Look in the Partition Magic directory tree for partinfo.exe. Open a DOS prompt,
CD to that dir, and run
partinfo partinfo.txt

Open partinfo.txt in notepad and Copy/Paste/Post to this thread.

Don't try to fix E: (or J until you find out what the problem is.



  #3  
Old April 23rd 06, 06:56 PM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem

On Sun, Apr 23, 2006 12:57:55, Bill wrote:

"Hoppy" wrote in message
...
Hello, All!

I used Partition Magic 8.02 to create a new 1GB partition (J, taking the
space from E:. At the end of operation, I received an error that
"...cross-linked files were found." There was no option other than to
continue. PM then called DriverMapper and it seemed to go smoothly.

On reboot, Windows Explorer shows E: and J: with no labels. When I click
on the drives, I get an error that says, "E:\ is not accessible. A device
attached to the system is not functioning."

In Device Manager on the Performance tab, it says "Drive E is using an
MS-DOS compatibility mode file system."

In DOS, ScanDisk says, "...cannot examine drive E:" I did not try J:

Also in DOS, FDisk shows E:'s size as it should (10000MB), but shows
System "Unknown" (-- it should be FAT32 --) with an 18% Usage -- which is
about right. FDisk does not show J: at all.

Partition Magic shows E: as it should -- FAT32; (new) Size: 10,001.4MB;
Used: 1150.5, set as Logical. Drive J: does not appear at all. What does
show is 1004.1MB of Unallocated space after E:; this was supposed to be
the new J: partition.


Look in the Partition Magic directory tree for partinfo.exe. Open a DOS
prompt, CD to that dir, and run
partinfo partinfo.txt

Open partinfo.txt in notepad and Copy/Paste/Post to this thread.

Don't try to fix E: (or J until you find out what the problem is.
---
Hi Bill --

I'm getting too old for this. Here's the file. I'll try to attach it to my
post as well; I hope that's not breaking any rules.

-----------------------------
Partition Information Program
Sep 16 2002 - DOS32 Version
Copyright (c) 1994-2002, PowerQuest Corporation
Permission is granted for this utility to be freely copied so long
as it is not modified in any way. All other rights are reserved.

PowerQuest, makers of PartitionMagic(r), Drive Image(tm) and DriveCopy(tm),
can be reached at
Voice: 801-226-6834 Web site: http://www.powerquest.com/support/
Fax: 801-226-8941 Email:
BiosExtensions: 0x100 Subsets (0x00000003): Access Lock/Eject
EGeo 0x0001 16383 16 63 120103200 0 512

================================================== ==========================
Disk 0: 7476 Cylinders, 255 Heads, 63 Sectors/Track.
BiosExtensions: 0x100 Subsets (0x00000003): Access Lock/Eject
The BIOS supports INT 13h extensions for this drive.
============================ Partition Tables ==============================
Partition -----Begin---- ------End----- Start Num
Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects
---------- - ---- ---- ---- ---- -- ---- ---- ---- ---------- ----------
0 0 80 0 1 1 0B 305 254 63 63 4915827
0 1 00 [ 306 0 1] 0F [ 307 254 63] 4915890 115186050
[Large Drive Placeholders]
306 0 1 7475 254 63
Actual Values
4915890 0 00 306 1 1 0B 777 254 63 4915953 7582617
4915890 1 00 778 0 1 05 [1023 254 63] 12498570 20482875
[Large Drive Placeholders]
778 0 1 2052 254 63
Actual Values
12498570 0 00 778 1 1 0B [1023 254 63] 12498633 20482812
[Large Drive Placeholders]
778 1 1 2052 254 63
Actual Values
12498570 1 00 [ 133 0 1] 05 [ 307 254 63] 35037765 85064175
[Large Drive Placeholders]
2181 0 1 7475 254 63
Actual Values
35037765 0 00 [ 133 1 1] 0B [ 735 254 63] 35037828 9687132
[Large Drive Placeholders]
2181 1 1 2783 254 63
Actual Values
35037765 1 00 [ 736 0 1] 05 [ 307 254 63] 44724960 75376980
[Large Drive Placeholders]
2784 0 1 7475 254 63
Actual Values
44724960 0 00 [ 736 1 1] 0B [ 752 254 63] 44725023 16723602
[Large Drive Placeholders]
2784 1 1 3824 254 63
Actual Values
44724960 1 00 [ 753 0 1] 05 [ 307 254 63] 61448625 58653315
[Large Drive Placeholders]
3825 0 1 7475 254 63
Actual Values
61448625 0 00 [ 753 1 1] 0B [ 302 254 63] 61448688 25671807
[Large Drive Placeholders]
3825 1 1 5422 254 63
Actual Values
61448625 1 00 [ 303 0 1] 05 [ 307 254 63] 87120495 32981445
[Large Drive Placeholders]
5423 0 1 7475 254 63
Actual Values
87120495 0 00 [ 303 1 1] 0B [ 307 254 63] 87120558 32981382
[Large Drive Placeholders]
5423 1 1 7475 254 63
Actual Values

Disk[0], Part[44724960]: Warning #113: EPBR partition starting at 44724960
overlaps previous EPBR partition.

Disk[0], Part[61448625]: Warning #113: EPBR partition starting at 61448625
overlaps previous EPBR partition.

Disk[0], Part[87120495]: Warning #113: EPBR partition starting at 87120495
overlaps previous EPBR partition.


================================================== ==========================
======
Disk 0: 58643.5 Megabytes
============================= Partition Information
==============================
Volume Partition Partition Start
Total
Letter:Label Type Status Size MB Sector # Sector
Sectors
------------- --------------- -------- -------- ---------- - ---------- ----
------
C:WIN98SE FAT32 Pri,Boot 2400.3 0 0 63
4915827
ExtendedX Pri 56243.2 0 1 4915890
115186050
EPBR Log 3702.5 None - 4915890
7582680
D:PROGRAMS FAT32 Log 3702.4 4915890 0 4915953
7582617
EPBR Log 10001.4 4915890 1 12498570
20482875
J:STORAGE FAT32 Log 10001.4 12498570 0 12498633
20482812
Unallocated Log 1004.1 None - 32981445
2056320
EPBR Log 41535.2 12498570 1 35037765
85064175
F:TEMP FAT32 Log 4730.0 35037765 0 35037828
9687132
EPBR Log 36805.2 35037765 1 44724960
75376980
G:MISC FAT32 Log 8165.8 44724960 0 44725023
16723602
EPBR Log 28639.3 44724960 1 61448625
58653315
H:IMAGES FAT32 Log 12535.1 61448625 0 61448688
25671807
EPBR Log 16104.2 61448625 1 87120495
32981445
I:GRAFIX FAT32 Log 16104.2 87120495 0 87120558
32981382



================================================== ======================
Boot Sector 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: 8
5. Reserved Sectors: 32
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: 4915827 (0x4B0273)
15. Big Sectors Per FAT: 4792
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 0
20. Backup Boot Sector: 6
21. Reserved: 0x00 00 00 00 00 00 00 00 00 00 00 00
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x00000DAA
26. Volume Name: WIN98SE
27. File System Type: FAT32
28. Boot Signatu 0xAA55


================================================== ======================
Boot Sector for drive D: Drive 1, Starting Sector: 4915953, Type: FAT32
================================================== ======================
1. Jump: EB FE 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 32
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: 7582617 (0x73B399)
15. Big Sectors Per FAT: 7391
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 0
20. Backup Boot Sector: 6
21. Reserved: 0x00 00 00 00 00 00 00 00 00 00 00 00
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x00000EDB
26. Volume Name: PROGRAMS
27. File System Type: FAT32
28. Boot Signatu 0xAA55


================================================== ======================
Boot Sector for drive J: Drive 1, Starting Sector: 12498633, Type: FAT32
================================================== ======================
1. Jump: 52 52 61
2. OEM Name: ASWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 16
5. Reserved Sectors: 32
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: 12498633 (0xBEB6C9)
14. Big Total Sectors: 20482812 (0x1388AFC)
15. Big Sectors Per FAT: 9995
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 127 (0x7F)
19. FS Info Sector: 0
20. Backup Boot Sector: 6
21. Reserved: 0x00 00 00 00 00 00 00 00 00 00 00 00
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x00000F06
26. Volume Name: STORAGE
27. File System Type: FAT32
28. Boot Signatu 0xAA55


================================================== ======================
Boot Sector for drive F: Drive 1, Starting Sector: 35037828, Type: FAT32
================================================== ======================
1. Jump: EB FE 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 32
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: 9687132 (0x93D05C)
15. Big Sectors Per FAT: 9442
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 0
20. Backup Boot Sector: 6
21. Reserved: 0x00 00 00 00 00 00 00 00 00 00 00 00
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x00000EE8
26. Volume Name: TEMP
27. File System Type: FAT32
28. Boot Signatu 0xAA55


================================================== ======================
Boot Sector for drive G: Drive 1, Starting Sector: 44725023, Type: FAT32
================================================== ======================
1. Jump: EB FE 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 32
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: 16723602 (0xFF2E92)
15. Big Sectors Per FAT: 16300
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 0
20. Backup Boot Sector: 6
21. Reserved: 0x00 00 00 00 00 00 00 00 00 00 00 00
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x00000ECE
26. Volume Name: MISC
27. File System Type: FAT32
28. Boot Signatu 0xAA55


================================================== ======================
Boot Sector for drive H: Drive 1, Starting Sector: 61448688, Type: FAT32
================================================== ======================
1. Jump: EB FE 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 16
5. Reserved Sectors: 32
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: 25671807 (0x187B87F)
15. Big Sectors Per FAT: 12523
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 0
20. Backup Boot Sector: 6
21. Reserved: 0x00 00 00 00 00 00 00 00 00 00 00 00
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x00000F07
26. Volume Name: IMAGES
27. File System Type: FAT32
28. Boot Signatu 0xAA55


================================================== ======================
Boot Sector for drive I: Drive 1, Starting Sector: 87120558, Type: FAT32
================================================== ======================
1. Jump: EB FE 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 16
5. Reserved Sectors: 32
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: 32981382 (0x1F74186)
15. Big Sectors Per FAT: 16089
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 0
20. Backup Boot Sector: 6
21. Reserved: 0x00 00 00 00 00 00 00 00 00 00 00 00
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x00000F04
26. Volume Name: GRAFIX
27. File System Type: FAT32
28. Boot Signatu 0xAA55
--------------------------------------

--
Hoppy
~~




Attached Files
File Type: txt partinfo.txt (14.3 KB, 642 views)
  #4  
Old April 24th 06, 01:45 PM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem

"Hoppy" wrote in message ...
On Sun, Apr 23, 2006 12:57:55, Bill wrote:

"Hoppy" wrote in message
...
Hello, All!

I used Partition Magic 8.02 to create a new 1GB partition (J, taking the
space from E:. At the end of operation, I received an error that
"...cross-linked files were found." There was no option other than to
continue. PM then called DriverMapper and it seemed to go smoothly.

On reboot, Windows Explorer shows E: and J: with no labels. When I click
on the drives, I get an error that says, "E:\ is not accessible. A device
attached to the system is not functioning."

In Device Manager on the Performance tab, it says "Drive E is using an
MS-DOS compatibility mode file system."

In DOS, ScanDisk says, "...cannot examine drive E:" I did not try J:

Also in DOS, FDisk shows E:'s size as it should (10000MB), but shows
System "Unknown" (-- it should be FAT32 --) with an 18% Usage -- which is
about right. FDisk does not show J: at all.

Partition Magic shows E: as it should -- FAT32; (new) Size: 10,001.4MB;
Used: 1150.5, set as Logical. Drive J: does not appear at all. What does
show is 1004.1MB of Unallocated space after E:; this was supposed to be
the new J: partition.


Look in the Partition Magic directory tree for partinfo.exe. Open a DOS
prompt, CD to that dir, and run
partinfo partinfo.txt

Open partinfo.txt in notepad and Copy/Paste/Post to this thread.

Don't try to fix E: (or J until you find out what the problem is.


I'm getting too old for this. Here's the file. I'll try to attach it to my
post as well; I hope that's not breaking any rules.


No, that's fine. Actually better as attached.

The extended partition chain has a corrupt link in the chain for one.

Assuming all the start sectors LBA values are correct.

The first EMBR/second table entry contains an incorrect value for LBA "Num sectors"
(total sectors remaining in the extended partition).

The second EMBR/first table entry contains an incorrect value for LBA "Num sectors"
(total in "this" logical drive).

Again, that's assuming the start sector numbers are correct. If math corrected
the E: logical drive still may not show. The "E:" boot sector doesn't show, so may
also be corrupt, start elsewhere, or DOS/Windows has a problem with those
incorrect values.

You could try to correct the values yourself, and see what that does, or probably
safer use something like DiskPatch or MBRWork to scan the disk for the missing
partitions. I'd use DiskPatch first, as freeware MBRWork is a "do or die" operation.
The demo version of DiskPatch is read-only, so won't do any damage.
http://www.diydatarecovery.nl/DiskPatch.htm

Your existing partitions probably aren't at too much risk, but you never know. Back
up all important data before fixing anything.




================================================== ==========================
Disk 0: 7476 Cylinders, 255 Heads, 63 Sectors/Track.
BiosExtensions: 0x100 Subsets (0x00000003): Access Lock/Eject
The BIOS supports INT 13h extensions for this drive.
============================ Partition Tables ==============================
Partition -----Begin---- ------End----- Start Num
Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects
---------- - ---- ---- ---- ---- -- ---- ---- ---- ---------- ----------
0 0 80 0 1 1 0B 305 254 63 63 4915827
0 1 00 [ 306 0 1] 0F [ 307 254 63] 4915890 115186050
[Large Drive Placeholders]
306 0 1 7475 254 63
Actual Values
4915890 0 00 306 1 1 0B 777 254 63 4915953 7582617
4915890 1 00 778 0 1 05 [1023 254 63] 12498570 20482875
[Large Drive Placeholders]
778 0 1 2052 254 63
Actual Values
12498570 0 00 778 1 1 0B [1023 254 63] 12498633 20482812
[Large Drive Placeholders]
778 1 1 2052 254 63
Actual Values
12498570 1 00 [ 133 0 1] 05 [ 307 254 63] 35037765 85064175
[Large Drive Placeholders]
2181 0 1 7475 254 63
Actual Values
35037765 0 00 [ 133 1 1] 0B [ 735 254 63] 35037828 9687132
[Large Drive Placeholders]
2181 1 1 2783 254 63
Actual Values
35037765 1 00 [ 736 0 1] 05 [ 307 254 63] 44724960 75376980
[Large Drive Placeholders]
2784 0 1 7475 254 63
Actual Values
44724960 0 00 [ 736 1 1] 0B [ 752 254 63] 44725023 16723602
[Large Drive Placeholders]
2784 1 1 3824 254 63
Actual Values
44724960 1 00 [ 753 0 1] 05 [ 307 254 63] 61448625 58653315
[Large Drive Placeholders]
3825 0 1 7475 254 63
Actual Values
61448625 0 00 [ 753 1 1] 0B [ 302 254 63] 61448688 25671807
[Large Drive Placeholders]
3825 1 1 5422 254 63
Actual Values
61448625 1 00 [ 303 0 1] 05 [ 307 254 63] 87120495 32981445
[Large Drive Placeholders]
5423 0 1 7475 254 63
Actual Values
87120495 0 00 [ 303 1 1] 0B [ 307 254 63] 87120558 32981382
[Large Drive Placeholders]
5423 1 1 7475 254 63
Actual Values

Disk[0], Part[44724960]: Warning #113: EPBR partition starting at 44724960
overlaps previous EPBR partition.

Disk[0], Part[61448625]: Warning #113: EPBR partition starting at 61448625
overlaps previous EPBR partition.

Disk[0], Part[87120495]: Warning #113: EPBR partition starting at 87120495
overlaps previous EPBR partition.



  #5  
Old April 24th 06, 09:48 PM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem

| I'd use DiskPatch first, as freeware MBRWork is a "do or die"
operation.

I was going to ask why?, but I think I figured it out. MBRWork's Option
1 isn't sufficient to backup the current locations of logical drives
within Extended Partitions, is it? That's because the logical drive
chain is outside track one? It doesn't really sound like MBRWork will
even try to recover logical drives, but only the Extended Partition
itself.

http://www.terabyteunlimited.com/utilities.html MBRWork
Free MBR utility. Below is it's Readme. A good try may be...

(a) Option 7 - Work with multiple hard drives.
Get to HDD in question, the bad one.
(I'm not really sure how it looks/works).
(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 are 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.
(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 (by passing
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 Extened
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

"Bill Blanton" wrote in message
...
| "Hoppy" wrote in message
...
| On Sun, Apr 23, 2006 12:57:55, Bill wrote:
|
| "Hoppy" wrote in message
| ...
| Hello, All!
|
| I used Partition Magic 8.02 to create a new 1GB partition (J,
taking the
| space from E:. At the end of operation, I received an error that
| "...cross-linked files were found." There was no option other than
to
| continue. PM then called DriverMapper and it seemed to go
smoothly.
|
| On reboot, Windows Explorer shows E: and J: with no labels. When I
click
| on the drives, I get an error that says, "E:\ is not accessible. A
device
| attached to the system is not functioning."
|
| In Device Manager on the Performance tab, it says "Drive E is using
an
| MS-DOS compatibility mode file system."
|
| In DOS, ScanDisk says, "...cannot examine drive E:" I did not try
J:
|
| Also in DOS, FDisk shows E:'s size as it should (10000MB), but
shows
| System "Unknown" (-- it should be FAT32 --) with an 18% Usage --
which is
| about right. FDisk does not show J: at all.
|
| Partition Magic shows E: as it should -- FAT32; (new) Size:
10,001.4MB;
| Used: 1150.5, set as Logical. Drive J: does not appear at all.
What does
| show is 1004.1MB of Unallocated space after E:; this was supposed
to be
| the new J: partition.
|
| Look in the Partition Magic directory tree for partinfo.exe. Open a
DOS
| prompt, CD to that dir, and run
| partinfo partinfo.txt
|
| Open partinfo.txt in notepad and Copy/Paste/Post to this thread.
|
| Don't try to fix E: (or J until you find out what the problem is.
|
| I'm getting too old for this. Here's the file. I'll try to attach
it to my
| post as well; I hope that's not breaking any rules.
|
| No, that's fine. Actually better as attached.
|
| The extended partition chain has a corrupt link in the chain for one.
|
| Assuming all the start sectors LBA values are correct.
|
| The first EMBR/second table entry contains an incorrect value for LBA
"Num sectors"
| (total sectors remaining in the extended partition).
|
| The second EMBR/first table entry contains an incorrect value for LBA
"Num sectors"
| (total in "this" logical drive).
|
| Again, that's assuming the start sector numbers are correct. If math
corrected
| the E: logical drive still may not show. The "E:" boot sector doesn't
show, so may
| also be corrupt, start elsewhere, or DOS/Windows has a problem with
those
| incorrect values.
|
| You could try to correct the values yourself, and see what that does,
or probably
| safer use something like DiskPatch or MBRWork to scan the disk for the
missing
| partitions. I'd use DiskPatch first, as freeware MBRWork is a "do or
die" operation.
| The demo version of DiskPatch is read-only, so won't do any damage.
|
http://www.diydatarecovery.nl/DiskPatch.htm
|
| Your existing partitions probably aren't at too much risk, but you
never know. Back
| up all important data before fixing anything.
|
|
|
|
|
================================================== ======================
====
| Disk 0: 7476 Cylinders, 255 Heads, 63 Sectors/Track.
| BiosExtensions: 0x100 Subsets (0x00000003): Access Lock/Eject
| The BIOS supports INT 13h extensions for this drive.
| ============================ Partition Tables
==============================
| Partition -----Begin---- ------End----- Start
Num
| Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect
Sects
|
---------- - ---- ---- ---- ---- -- ---- ---- ---- ---------- ----

------
| 0 0 80 0 1 1 0B 305 254 63 63
4915827
| 0 1 00 [ 306 0 1] 0F [ 307 254 63] 4915890
115186050
| [Large Drive Placeholders]
| 306 0 1 7475 254 63
| Actual Values
| 4915890 0 00 306 1 1 0B 777 254 63 4915953
7582617
| 4915890 1 00 778 0 1 05 [1023 254 63] 12498570
20482875
| [Large Drive Placeholders]
| 778 0 1 2052 254 63
| Actual Values
| 12498570 0 00 778 1 1 0B [1023 254 63] 12498633
20482812
| [Large Drive Placeholders]
| 778 1 1 2052 254 63
| Actual Values
| 12498570 1 00 [ 133 0 1] 05 [ 307 254 63] 35037765
85064175
| [Large Drive Placeholders]
| 2181 0 1 7475 254 63
| Actual Values
| 35037765 0 00 [ 133 1 1] 0B [ 735 254 63] 35037828
9687132
| [Large Drive Placeholders]
| 2181 1 1 2783 254 63
| Actual Values
| 35037765 1 00 [ 736 0 1] 05 [ 307 254 63] 44724960
75376980
| [Large Drive Placeholders]
| 2784 0 1 7475 254 63
| Actual Values
| 44724960 0 00 [ 736 1 1] 0B [ 752 254 63] 44725023
16723602
| [Large Drive Placeholders]
| 2784 1 1 3824 254 63
| Actual Values
| 44724960 1 00 [ 753 0 1] 05 [ 307 254 63] 61448625
58653315
| [Large Drive Placeholders]
| 3825 0 1 7475 254 63
| Actual Values
| 61448625 0 00 [ 753 1 1] 0B [ 302 254 63] 61448688
25671807
| [Large Drive Placeholders]
| 3825 1 1 5422 254 63
| Actual Values
| 61448625 1 00 [ 303 0 1] 05 [ 307 254 63] 87120495
32981445
| [Large Drive Placeholders]
| 5423 0 1 7475 254 63
| Actual Values
| 87120495 0 00 [ 303 1 1] 0B [ 307 254 63] 87120558
32981382
| [Large Drive Placeholders]
| 5423 1 1 7475 254 63
| Actual Values
|
| Disk[0], Part[44724960]: Warning #113: EPBR partition starting at
44724960
| overlaps previous EPBR partition.
|
| Disk[0], Part[61448625]: Warning #113: EPBR partition starting at
61448625
| overlaps previous EPBR partition.
|
| Disk[0], Part[87120495]: Warning #113: EPBR partition starting at
87120495
| overlaps previous EPBR partition.
|
|


  #6  
Old April 25th 06, 04:01 AM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem

Hey hey.. quotes are back..

"PCR" wrote in message ...
| I'd use DiskPatch first, as freeware MBRWork is a "do or die"
operation.

I was going to ask why?, but I think I figured it out. MBRWork's Option
1 isn't sufficient to backup the current locations of logical drives
within Extended Partitions, is it? That's because the logical drive
chain is outside track one?


Right. The logical drive tables "sit on top" of the logical drive they
define, with a pointer to the next in the chain.

It doesn't really sound like MBRWork will
even try to recover logical drives, but only the Extended Partition
itself.


I'm not sure on that, but I would think it would. You could ask
David F. Either way (in this case), if it didn't, it wouldn't help. If it did, it
would be a "no return" operation. Not easily anyway.



  #7  
Old April 25th 06, 11:14 PM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem

"Bill Blanton" wrote in message
...
| Hey hey.. quotes are back..

I've decided to toggle QP as needed. Don't ask me for Registry keys,
unless you're prepared to lose your indents!

| "PCR" wrote in message
...
| | I'd use DiskPatch first, as freeware MBRWork is a "do or die"
| operation.
|
| I was going to ask why?, but I think I figured it out. MBRWork's
Option
| 1 isn't sufficient to backup the current locations of logical drives
| within Extended Partitions, is it? That's because the logical drive
| chain is outside track one?
|
| Right. The logical drive tables "sit on top" of the logical drive they
| define, with a pointer to the next in the chain.

Yea. I think it was cquirke maybe you first explained it to me... the
Extended Partition in full is described in the MBR as one of the four
partitions. But the logical partitions within the Extended Partition are
described in a chain in front of each drive's data area.

| It doesn't really sound like MBRWork will
| even try to recover logical drives, but only the Extended Partition
| itself.
|
| I'm not sure on that, but I would think it would. You could ask
| David F. Either way (in this case), if it didn't, it wouldn't help. If
it did, it
| would be a "no return" operation. Not easily anyway.

I don't know. But I think MBRWork probably will not touch the logical
partitions. It will attempt to recover the Extended Partition only-- &
the rest will have to be good or not. In that case, MBRWork will do
nothing that isn't recoverable by Option 2, provided Option 1 was done
first before fiddling. BUT, I think I'd better ask or look it up now.

........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 (by passing
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 Extened
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 .............


  #8  
Old April 26th 06, 01:39 AM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem

On Mon, Apr 24, 2006 08:45:51, Bill wrote:

"Hoppy" wrote in message ...
On Sun, Apr 23, 2006 12:57:55, Bill wrote:

"Hoppy" wrote in message ...
Hello, All!

I used Partition Magic 8.02 to create a new 1GB partition (J, taking
the space from E:. At the end of operation, I received an error
that "...cross-linked files were found." There was no option other than
to continue. PM then called DriverMapper and it seemed to go smoothly.

On reboot, Windows Explorer shows E: and J: with no labels. When I click
on the drives, I get an error that says, "E:\ is not accessible. A device
attached to the system is not functioning."

In Device Manager on the Performance tab, it says "Drive E is using an
MS-DOS compatibility mode file system."

In DOS, ScanDisk says, "...cannot examine drive E:" I did not try J:

Also in DOS, FDisk shows E:'s size as it should (10000MB), but shows
System "Unknown" (-- it should be FAT32 --) with an 18% Usage -- which is
about right. FDisk does not show J: at all.

Partition Magic shows E: as it should -- FAT32; (new) Size: 10,001.4MB;
Used: 1150.5, set as Logical. Drive J: does not appear at all. What

does
show is 1004.1MB of Unallocated space after E:; this was supposed to be
the new J: partition.


Look in the Partition Magic directory tree for partinfo.exe. Open a DOS
prompt, CD to that dir, and run
partinfo partinfo.txt

Open partinfo.txt in notepad and Copy/Paste/Post to this thread.

Don't try to fix E: (or J until you find out what the problem is.


I'm getting too old for this. Here's the file. I'll try to attach it to
my post as well; I hope that's not breaking any rules.


No, that's fine. Actually better as attached.

The extended partition chain has a corrupt link in the chain for one.

Assuming all the start sectors LBA values are correct.

The first EMBR/second table entry contains an incorrect value for LBA "Num
sectors" (total sectors remaining in the extended partition).

The second EMBR/first table entry contains an incorrect value for LBA "Num
sectors" (total in "this" logical drive).

Again, that's assuming the start sector numbers are correct. If math
corrected the E: logical drive still may not show. The "E:" boot sector
doesn't show, so may also be corrupt, start elsewhere, or DOS/Windows has a
problem with those incorrect values.

You could try to correct the values yourself, and see what that does, or
probably safer use something like DiskPatch or MBRWork to scan the disk for
the missing partitions. I'd use DiskPatch first, as freeware MBRWork is a
"do or die" operation. The demo version of DiskPatch is read-only, so won't
do any damage. http://www.diydatarecovery.nl/DiskPatch.htm

Your existing partitions probably aren't at too much risk, but you never
know. Back up all important data before fixing anything.

================================================== ========================
Disk 0: 7476 Cylinders, 255 Heads, 63 Sectors/Track.
BiosExtensions: 0x100 Subsets (0x00000003): Access Lock/Eject
The BIOS supports INT 13h extensions for this drive.
========================== Partition Tables ==============================
Partition -----Begin---- ------End----- Start Num
Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects
---------- - ---- ---- ---- ---- -- ---- ---- ---- ----------
---------- 0 0 80 0 1 1 0B 305 254 63 63
4915827 0 1 00 [ 306 0 1] 0F [ 307 254 63] 4915890
115186050 [Large Drive Placeholders] 306 0 1
7475 254 63 Actual Values 4915890 0 00 306 1 1 0B 777
254 63 4915953 7582617 4915890 1 00 778 0 1 05 [1023
254 63] 12498570 20482875 [Large Drive Placeholders]
778 0 1 2052 254 63 Actual Values 12498570 0 00 778 1
1 0B [1023 254 63] 12498633 20482812 [Large Drive Placeholders]
778 1 1 2052 254 63 Actual Values 12498570 1 00 [ 133 0
1] 05 [ 307 254 63] 35037765 85064175 [Large Drive Placeholders]
2181 0 1 7475 254 63 Actual Values 35037765 0 00 [ 133
1 1] 0B [ 735 254 63] 35037828 9687132 [Large Drive
Placeholders] 2181 1 1 2783 254 63 Actual
Values 35037765 1 00 [ 736 0 1] 05 [ 307 254 63] 44724960
75376980 [Large Drive Placeholders] 2784 0 1
7475 254 63 Actual Values 44724960 0 00 [ 736 1 1] 0B [ 752
254 63] 44725023 16723602 [Large Drive Placeholders]
2784 1 1 3824 254 63 Actual Values 44724960 1 00 [ 753
0 1] 05 [ 307 254 63] 61448625 58653315 [Large Drive
Placeholders] 3825 0 1 7475 254 63 Actual
Values 61448625 0 00 [ 753 1 1] 0B [ 302 254 63] 61448688
25671807 [Large Drive Placeholders] 3825 1 1
5422 254 63 Actual Values 61448625 1 00 [ 303 0 1] 05 [ 307
254 63] 87120495 32981445 [Large Drive Placeholders]
5423 0 1 7475 254 63 Actual Values 87120495 0 00 [ 303
1 1] 0B [ 307 254 63] 87120558 32981382 [Large Drive
Placeholders] 5423 1 1 7475 254 63 Actual
Values

Disk[0], Part[44724960]: Warning #113: EPBR partition starting at 44724960
overlaps previous EPBR partition.

Disk[0], Part[61448625]: Warning #113: EPBR partition starting at 61448625
overlaps previous EPBR partition.

Disk[0], Part[87120495]: Warning #113: EPBR partition starting at 87120495
overlaps previous EPBR partition.


Thank you very much for responding, Bill (and PCR). I'm sorry for not
responding sooner, but your discussion with PCR has me reeling a bit. I
will probably take your suggestion about the trial version of DiskPatch --
especially since it read-only. At this point I am not willing to lose any
files on this HDD, and I'm not ready to commit to any procedure until I'm
1000% sure of its outcome. There used to be a second HDD in this machine,
and I've spent many hours hacking the registry to correct its addresses.
This box was destined for disassembly until I had a problem with my XP
machine. I'm wondering if the removal of the drive had something to do with
the misbehaviour of Partition Magic.

I will probably start working on this mess during the upcoming weekend.
Hopefully I can image and burn my drives to CD just in case I trash the HDD
while trying to fix it. Last night I remembered that I imaged these drives
and burned them to DVD on my XP machine -- which is currently down due a yet
undiagnosed hardware issue.

In the meantime, I'm hoping there may be a PowerQuest veteran at Symantec
who may be able to help. I've only used PQ tech support once before (with
Drive Image) and once I was sure they understood my problem, they quickly
solved it. Hopefully this time around, I can be so lucky.

It sounds like you have experience with PM, Bill. Do you think there's any
chance that reallocating the space on the J: drive might solve the problem?

Also, I'm thinking of snipping PartInfo from this post. Will that cause any
problem with future responses?

BTW, whatever you guys are doing with your quotes has made subsequent posts
pretty unreadable -- tons of breaks.
--
Hoppy
~~


  #9  
Old April 26th 06, 11:49 PM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem

"Hoppy" wrote in message
...
| On Mon, Apr 24, 2006 08:45:51, Bill wrote:
|
| "Hoppy" wrote in message
...
| On Sun, Apr 23, 2006 12:57:55, Bill wrote:
|
| "Hoppy" wrote in message
...
| Hello, All!
|
| I used Partition Magic 8.02 to create a new 1GB partition (J,
taking
| the space from E:. At the end of operation, I received an error
| that "...cross-linked files were found." There was no option other
than
| to continue. PM then called DriverMapper and it seemed to go
smoothly.
|
| On reboot, Windows Explorer shows E: and J: with no labels. When I
click
| on the drives, I get an error that says, "E:\ is not accessible. A
device
| attached to the system is not functioning."
|
| In Device Manager on the Performance tab, it says "Drive E is using
an
| MS-DOS compatibility mode file system."
|
| In DOS, ScanDisk says, "...cannot examine drive E:" I did not try
J:
|
| Also in DOS, FDisk shows E:'s size as it should (10000MB), but
shows
| System "Unknown" (-- it should be FAT32 --) with an 18% Usage --
which is
| about right. FDisk does not show J: at all.
|
| Partition Magic shows E: as it should -- FAT32; (new) Size:
10,001.4MB;
| Used: 1150.5, set as Logical. Drive J: does not appear at all.
What
| does
| show is 1004.1MB of Unallocated space after E:; this was supposed
to be
| the new J: partition.
|
| Look in the Partition Magic directory tree for partinfo.exe. Open a
DOS
| prompt, CD to that dir, and run
| partinfo partinfo.txt
|
| Open partinfo.txt in notepad and Copy/Paste/Post to this thread.
|
| Don't try to fix E: (or J until you find out what the problem is.
|
| I'm getting too old for this. Here's the file. I'll try to attach
it to
| my post as well; I hope that's not breaking any rules.
|
| No, that's fine. Actually better as attached.
|
| The extended partition chain has a corrupt link in the chain for one.
|
| Assuming all the start sectors LBA values are correct.
|
| The first EMBR/second table entry contains an incorrect value for LBA
"Num
| sectors" (total sectors remaining in the extended partition).
|
| The second EMBR/first table entry contains an incorrect value for LBA
"Num
| sectors" (total in "this" logical drive).
|
| Again, that's assuming the start sector numbers are correct. If math
| corrected the E: logical drive still may not show. The "E:" boot
sector
| doesn't show, so may also be corrupt, start elsewhere, or DOS/Windows
has a
| problem with those incorrect values.
|
| You could try to correct the values yourself, and see what that does,
or
| probably safer use something like DiskPatch or MBRWork to scan the
disk for
| the missing partitions. I'd use DiskPatch first, as freeware MBRWork
is a
| "do or die" operation. The demo version of DiskPatch is read-only, so
won't
| do any damage. http://www.diydatarecovery.nl/DiskPatch.htm
|
| Your existing partitions probably aren't at too much risk, but you
never
| know. Back up all important data before fixing anything.
|
|
================================================== ======================
==
| Disk 0: 7476 Cylinders, 255 Heads, 63 Sectors/Track.
| BiosExtensions: 0x100 Subsets (0x00000003): Access Lock/Eject
| The BIOS supports INT 13h extensions for this drive.
| ========================== Partition Tables
==============================
| Partition -----Begin---- ------End----- Start
Num
| Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect
Sects
| ---------- - ---- ---- ---- ---- -- ---- ---- ---- ----------
| ---------- 0 0 80 0 1 1 0B 305 254 63
63
| 4915827 0 1 00 [ 306 0 1] 0F [ 307 254 63]
4915890
| 115186050 [Large Drive Placeholders] 306 0 1
| 7475 254 63 Actual Values 4915890 0 00 306 1 1 0B
777
| 254 63 4915953 7582617 4915890 1 00 778 0 1 05
[1023
| 254 63] 12498570 20482875 [Large Drive Placeholders]
| 778 0 1 2052 254 63 Actual Values 12498570 0 00
778 1
| 1 0B [1023 254 63] 12498633 20482812 [Large Drive
Placeholders]
| 778 1 1 2052 254 63 Actual Values 12498570 1 00 [
133 0
| 1] 05 [ 307 254 63] 35037765 85064175 [Large Drive
Placeholders]
| 2181 0 1 7475 254 63 Actual Values 35037765 0 00 [
133
| 1 1] 0B [ 735 254 63] 35037828 9687132 [Large Drive
| Placeholders] 2181 1 1 2783 254 63
Actual
| Values 35037765 1 00 [ 736 0 1] 05 [ 307 254 63]
44724960
| 75376980 [Large Drive Placeholders] 2784 0 1
| 7475 254 63 Actual Values 44724960 0 00 [ 736 1 1] 0B [
752
| 254 63] 44725023 16723602 [Large Drive Placeholders]
| 2784 1 1 3824 254 63 Actual Values 44724960 1 00 [
753
| 0 1] 05 [ 307 254 63] 61448625 58653315 [Large Drive
| Placeholders] 3825 0 1 7475 254 63
Actual
| Values 61448625 0 00 [ 753 1 1] 0B [ 302 254 63]
61448688
| 25671807 [Large Drive Placeholders] 3825 1 1
| 5422 254 63 Actual Values 61448625 1 00 [ 303 0 1] 05 [
307
| 254 63] 87120495 32981445 [Large Drive Placeholders]
| 5423 0 1 7475 254 63 Actual Values 87120495 0 00 [
303
| 1 1] 0B [ 307 254 63] 87120558 32981382 [Large Drive
| Placeholders] 5423 1 1 7475 254 63
Actual
| Values
|
| Disk[0], Part[44724960]: Warning #113: EPBR partition starting at
44724960
| overlaps previous EPBR partition.
|
| Disk[0], Part[61448625]: Warning #113: EPBR partition starting at
61448625
| overlaps previous EPBR partition.
|
| Disk[0], Part[87120495]: Warning #113: EPBR partition starting at
87120495
| overlaps previous EPBR partition.
|
| Thank you very much for responding, Bill (and PCR).

You are welcome.

| I'm sorry for not
| responding sooner, but your discussion with PCR has me reeling a bit.
I
| will probably take your suggestion about the trial version of
DiskPatch --
| especially since it read-only.

That is sensible. I Googled "MBRWork logical drive", but could not
easily find what I wanted-- whether it tries to recover logical drives
or just the container Extended Partition(s) itself along with the
Primary Partition(s). My guess is still... it won't! The chain that
defines the logicals must be intact. It only works on the four actual
partitions that are in an MBR-- which normally is up to 3 Primary & 1
Extended. If you wanted to create a J:, you must have had 7 partitions
before-- meaning there are logical partitions involved. I don't think
MBRWork can handle it-- UNLESS PM did everything it should except to
adjust the MBR.

BUT, I will post your problem to... "public.apps.bootitng" of
"terabyteunlimited.com", just to see for sure. They wrote the thing!

| At this point I am not willing to lose any
| files on this HDD, and I'm not ready to commit to any procedure until
I'm
| 1000% sure of its outcome.

Be very cautious, then. You know I can't be sued? (But Blanton has no
disclaimer.)

| There used to be a second HDD in this machine,
| and I've spent many hours hacking the registry to correct its
addresses.
| This box was destined for disassembly until I had a problem with my XP
| machine. I'm wondering if the removal of the drive had something to
do with
| the misbehaviour of Partition Magic.

I don't know. Maybe, because the Registry is always busy.

| I will probably start working on this mess during the upcoming
weekend.
| Hopefully I can image and burn my drives to CD just in case I trash
the HDD
| while trying to fix it.

That is very sensible. I only hope it CAN be done in the present
circumstance.

| Last night I remembered that I imaged these drives
| and burned them to DVD on my XP machine -- which is currently down due
a yet
| undiagnosed hardware issue.

Would be best, if those are good. Your whole problem goes away then!

| In the meantime, I'm hoping there may be a PowerQuest veteran at
Symantec
| who may be able to help. I've only used PQ tech support once before
(with
| Drive Image) and once I was sure they understood my problem, they
quickly
| solved it. Hopefully this time around, I can be so lucky.

Give them a try. I'll post it to "public.apps.bootitng".

| It sounds like you have experience with PM, Bill. Do you think
there's any
| chance that reallocating the space on the J: drive might solve the
problem?

Don't call me Bill! There are too many, already! Just ask Colorado! Best
would be that the Images you did to DVD are good.

| Also, I'm thinking of snipping PartInfo from this post. Will that
cause any
| problem with future responses?

No. But anyone new looking in will have to do a bunch more clicking.

| BTW, whatever you guys are doing with your quotes has made subsequent
posts
| pretty unreadable -- tons of breaks.

That has to be all Blanton's fault now! I'm sending UUEncode!

| --
| Hoppy
| ~~
|
|


  #10  
Old April 27th 06, 04:12 AM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Major partition problem


"Hoppy" wrote in message ...

Thank you very much for responding, Bill (and PCR). I'm sorry for not
responding sooner, but your discussion with PCR has me reeling a bit. I
will probably take your suggestion about the trial version of DiskPatch --
especially since it read-only. At this point I am not willing to lose any
files on this HDD, and I'm not ready to commit to any procedure until I'm
1000% sure of its outcome.


Look into iRecover on the same site as Diskpatch. Run that first to attempt file recovery.


There used to be a second HDD in this machine,
and I've spent many hours hacking the registry to correct its addresses.
This box was destined for disassembly until I had a problem with my XP
machine. I'm wondering if the removal of the drive had something to do with
the misbehaviour of Partition Magic.


I very much doubt it.


I will probably start working on this mess during the upcoming weekend.
Hopefully I can image and burn my drives to CD just in case I trash the HDD
while trying to fix it. Last night I remembered that I imaged these drives
and burned them to DVD on my XP machine -- which is currently down due a yet
undiagnosed hardware issue.

In the meantime, I'm hoping there may be a PowerQuest veteran at Symantec
who may be able to help. I've only used PQ tech support once before (with
Drive Image) and once I was sure they understood my problem, they quickly
solved it. Hopefully this time around, I can be so lucky.




It sounds like you have experience with PM, Bill. Do you think there's any
chance that reallocating the space on the J: drive might solve the problem?


No, you definetly don't want to do any partition work on the drive until it's straightened out. You'll likely make things worse.


Also, I'm thinking of snipping PartInfo from this post. Will that cause any
problem with future responses?


No problem. If someone wants to see it, they can find it.




 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Network Login and Connection Problem William B. \(Beau\) Sanders General 1 July 9th 05 09:06 PM
MS05-002 on 9x and ME Jerry Bryant [MSFT] General 204 April 11th 05 06:57 AM
problem with IE and not able to download [email protected] General 3 February 11th 05 08:41 AM
Keyboard problem Nevans General 8 January 26th 05 03:17 AM
Continued problem with Slow System bgaard General 9 January 14th 05 12:08 AM


All times are GMT +1. The time now is 11:58 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.