Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Hi,
To cut a long story short, I had a partition with WinME on & one with XP Pro on (striped RAID array, single logical disk). I added more RAM and XP blue-screened (I think some of the RAM was faulty). Rebuilt XP and it worked fine. Installed Partition Magic V7 (compatible with XP) and tried running it but it fails with error 100 (Partition table bad). Suggested solution: delete partitions and re-create them.I don't mind doing this, all my data is backed up BUT (and it's a big but) I can't use a boot floppy because my system currently won't recognise any floppies! I have tried swapping in a good drive & cable, so I suspect the mobo (an engineer is coming to fix that at least).
Has anyone any ideas how I might fix the bad Partition Table without the use of a boot disk and formatting the entire hard drive?
Any (sensible) suggestions welcome!
Thanks in advance,
Roger.
I have the same problem with my raid setup - Deleting the partitions didnt make a difference. Only way it would work is if I disabled my RAID in the bios - could use PM ok then, then just re-enabled it after. I have an Abit kt7a-raid with 2 13 gig hdds in raid 0. If you get any luck, email me
0 
i had winme + xp pro running with pm7 on a striped raid array(abit bx133 raid), until i accidentaly deleted the bootsec file in the winme partition.after lots of reinstallations of both operating systems pm7 will only work from floppy in dos or in winme. xp pro says "init 100 bad partition table" .tried fixboot and fixmbr in recovery console and lolevel format please someone help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
0
i also use a striped raid (with dawi ide100 controller) under winxppro and got the same problem with pm7. perhaps there's someone out there who can give a solution.
0
Bad news guys, I mailed the PM7 people and they don't support software RAID arrays. I ended up blitzing the disk and reinstalling XP only. I plan to put an additional IDE drive in and put my other OS on that.
Cheers,
Roger.
0
I also have the same problem. Kt7-raid with OS on the RAID. Never had problems before then it popped up. Did a fdisk but still there. Even rebuilt the RAID array.
Weird thing is the error went away after awhile but now its back. Also same thing with Drive Image which is by the same company.
Also I don't run software raid as the onboard RAID chip on my mobo does it.
0
I have a solution!!!
This really only works for kt7-raid users.
I had the RAID bios version 2.0.2019 and my 2x30gig hdd's would show up in device manager as 2 seperate hdd's and not one as it should. Now I upgraded to RAID bios 2.31 and installed the 2.31 drivers (had the default MS ones before) and now device manager sees it as one drive not 2.
Now I load up pm7 and no error :)
Now I'm not sure if it was the 2.31 BIOS or 2.31 driver that fixed it but its best to match the bios and driver versions.
Now some of you may know the latested official kt7-raid bios only comes with RAID bios 2.0.2019 or something liike that. What you need to do is grab the bios on this site http://www.viahardware.com/faq/kt7/faqdownloads.html#BIOS%20releases
The owner of that site has merger the 2.31 bios (which is an official version) into the latest kt7-raid bios.
So go grab the modified bios and the 2.31 driver. Flash the bios first then install the driver when you reboot.
Hope this helps :)
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
