[resolved] BootThink 2.3.18 win uninstall error

[sugarfixx]

Hi guys guess what?? I built I HackIntosh here the other day.

Clean Installed XP on a NTFS partition after deviding a 1TB disk in 3. Left the 2 unused partitions unformatted.

Got XP working and Installed Boot Think 2.3.18 and rebooted.

BootThink launched but since I did not exactly understand how to deal with this GUI i got a Boot132 CD up and running and went back to XP to be able to research the topic further. I am not that good in Chinese but I saw recomandations somewhere that I should have installed OS X before BootThink so I went through the Unistall process as described in the Boot Think manual.

 

At reboot I got the following error

boot0 : testing

boot0 : testing

boot0 : error

 

I launched the Xp recovery console and did a FIXMBR

at relauch the famous ISERT SYSTEM DISK appeared so I launched the Xp recoveryconsole again and tried the FIXBOOT only to find that this pointed me to a drive named drive F

Win is on drive C as far as I know unless the letter F is an character used by those clever MS guys (F***ing ROOT DSK lol).

 

Anyway at the time I installed BootThink my disks visible in XP was

C win XP

D DVD Drive

E unformatted RAW

F unformated RAW

G Virtual Clone Drive

 

However I aborted the FIXBOOT and booted the machine from iATKOS V7 installed 10.5.7 rebooted back via the BOOT132 CD and watched the Movie and apart from sound everything seemed to work there.

I booted again into XP to see if I could figure ut this boot thing but now the disks listed by XP looks like this.

C win XP

D DVD Drive

E unformated RAW

G Virtual Clone Drive

 

So it strikes me that FIXBOOT might try to fix something on F that in my basic understanding of this problem is the partition with my OS X

 

SO finally here is what I'm wondering about.

Do I fix this easiest by fixing the original WIN XP boot?

Or is it no problem at all if I setup another bootloader?

As of today the BOOT132 gives me access to both os so not a huge problem apart from me tired of having a CD in the drive all the time.

 

GA G31M-ES2L

E7400

2gB RAM

WD 1TB SATA

EN9400GT

PATA DVD

[sugarfixx]

OK a little update.

This far I have tried to resolve this in XP revoery console.

Ran Chkdsk /r and everything was clear

tried FIXBOOT with same result that it wants to do this on drive F

did the old chdir C:\dir

and it listed all the usual files (NTLDR, NTDETECT.COM etc)

 

BUT also a file called BTLDR was there.

 

The BootThink uninstall guideasks you to remove a file called BTLDR but THAT file is suposed to be located on the root of XP's C drive and I did remove a BTLDR from this.

 

I am thinking hmm could there be 2 BRLDR files 1 original for Xp and a BootThink modified one?

My guess is NO but anywaysince everything but the boot is smooth I will walk carefully to sort this one out. I will welcome all input from you on this issue.

 

However I did rename btldr t xbtldr

Fixmbr again

Fixboot C:

Still no luck!

 

SO a new question in addition to the previous is;

Do any one of you reading this have a file called BTLDR at this location?

the original BTLDR I deleted earlier was wisible from the C drive in XP.

This new one is to me this far only detected if you do the following. (as even CMD will not show this)

 

Boot from WIN XP install CD

type R at setup

type at the C:\WINDOWS>

Chdir C:\

the promt will now be C:\>

Type

dir

 

Please is somone of you do NOT have this BTLDR showing up here in XP let me know.

Please also if someone know how to change the FIXBOOT to drive C also let me know.

[sugarfixx]

Ok here is how this problem was resolved.

After doing all the above without any luck I felt so stupid. So I posted a question on a XP tech forum!

From the answer given me there that fixed my problem I realized that what BootThink is doing on installation is to change active boot partition.

The unintaller in BootThink 2.3.18 does not revert bootpartition changes!

The fix was simply to change active partition under storage in Computer Management

 

Well I feel a little stupid not even checking this, but it just did not ring any bells that this would be the case, I was more prepared for a HUGE fix to sort this out.

 

Well lesson learned: the biggest problems are the easiest to solve.

Cheers