Click on my logo to go to my homepage.
Click on my logo to go to my homepage. |
Computer Solutions...Partition Magic version 8.01Error Code 100 issue - 10/25/06 |
10/25/06 - When I initially built my current computer, I installed a 30 gigabyte (GB) hard drive (HDD). Before installing Windows XP (WinXP), I partitioned off a second drive (drive "D") , to use for off loading downloaded updated, programs, temporary storage, and misc stuff I didn't want on my primary data drive. However, now three years later, and a year after I installed a larger drive for data storage, as well as an external drive for file backup, I found my "C" drive slowly filling to capacity, and the "D" drive sitting empty. I wanted to combine the two drives, but didn't want to reformat the drive, and reinstall my OS and all the programs.
(I actually find it rather amazing that after three years have gone by since I installed a brand new Operating System (OS) (installed in October 2003 when WinXP first hit the shelves) I'd still be running it from the initial install. Quite a difference from Windows 95 and 98 huh?).
Anyway; I purchased a copy of Partition Magic 8.0 (PM8), and installed it, as well as the update to version 8.01, and with great anticipation, cranked it up to resize my drive! After working through some troubling messages (that kept telling me my actions would render my drive "unbootable"), I finally worked up enough nerve to execute the necessary steps to resize the drive.
After working through the steps, and rebooting my computer, WinXP started, as did PM8 to execute the instructions I gave before rebooting. It immediately brought up an error! (I like to have snapshots of problems, but since WinXP wasn't fully booted, I couldn't use my snapshot program (Snagit), and didn't think quick enough to take a picture with my digital camera, until it was too late (DOLT!!). But I did write down the error message line for line. The error read:
Partiton Magic (xmnt2002.exe
PowerQuest Partition Magic is preparing to apply changes...
Press any key to abort.
* * * * *
Error Initializing the Program,
Return Code = 100
Error 100 while executing Batch.
Error 100 Partition Table is bad.
Press any key to continue...
PowerQuest for Partition Magic Complete.
In order to resolve the issue, I decided to check out a few online computer forums. One of my favorites, The Elder Geek (www.theeldergeek.com) had a few posts on partitioning but nothing that I could find on the error. So I decided to post a message, to see if anyone else had had the same issue.
I got a few suggestions:
1. Try "Merging" the partitions rather than deleting and resizing (Thanks Phil!). Unfortunately, that didn't help (that would have been too easy!).
2. Try running CHKDSK /F on both drives, then try again, or try deleting D, and resizing C (Thanks Allan!). Nope, didn't help, still get same error (also would have been too easy!).
Next I decided to check out the support pages on Symantec's website (they now own PM8). I found a list of codes, even a page specific to Error 100. But it said they've received feedback on the error, but were'nt able to recreate it themselves to find the problem (and the page wasn't updated for over a year).
OK, now it time to do some "GOOGLEing"! After wading through tons of responses to my query (Partition Magic + Error 100), I found a small post on a website where someone made a comment that someone told them, that some HP printers with flash media reader slots, kick back this code. The solution sounded WAY too simple ---disconnect the printer! But hey, at this point, I'm ready to try just about anything. And this one would't cost me my grandchildren...
So, I pulled the USB cable off my printer, started up PM8, setup the delete and resize commands and rebooted. PM8 came up during the boot, and completed the changes, allowing WinXP to finish booting. It went off without a hitch!!
My HP printer is a "Photosmart 1315", with two flash media card reader slots (a Smart Media, and a Compact Flash). These "slots" show up as "drives" in MY COMPUTER, but not in Partition Magic. And apparently, the way they are formatted or registered in Windows, doesn't agree with Partition Magic (maybe a "DriveMapper" issue), so when it tries to execute the commands on reboot, and looks at all the "registered" drives, it kicks out the code, because something doesn't look right (or some such reason).
I tried to passed the infomation along to Symantec, but after taking the time to complete the info, and writhing the message (ok, I noticed the misspell -writhing-, but like the ironly of what came out - so I left it), the page went nowhere (kicked back a message that stated - and this is REALLY what it said!: "Incident will not create in Right Now". So much for lending a helping hand...
Copywright 2006
Created by:
JEB's Digital Impressions