Hey Esther, actually none of this was done through BootCamp, so I'm
not sure that is the deal. I just opened finder and went to my
Windows volume, opened boot.ini in TextEdit and the rest is herstory!
It seems Bootcamp actually renumbered itself correctly but nobody
told Windows to do the same! lol!
In other words, when I created the second OSX partition, the BC
partition was reset to 4 instead of 3, but the boot.ini file wasn't
updated, as it couldn't be.
As for the error they mention, I did see that, but the error I got
was different.
So I'm not sure it's the same sitch. <smile>
Anyway, as I said, I'm really glad you'd found that resource, as
I'd been searching and really didn't find a thing that was as
informative so bigtime kudos to you! -You rock!…
Smiles,
cara :)
On Dec 14, 2008, at 4:17 PM, Esther wrote:
HI Cara,
Glad this all worked. I think, at a guess, that the relevant part
of that wiki was:
"Also, for some reason BootCamp expects the Windows "C:" drive to be
the last partition present on the drive. If it isn't, Windows setup
will crash with a "cannot find hall.dll" error after the first
reboot."
When you created new partitions, their numbered partitions got added
in. BootCamp was left pointing to whatever partition number it was
assigned at the time you created it, even though it was still the
last partition on the drive.
Anyway, congratualations on having deciphered all of this!
Cheers,
Esther
P.S. I'm not sure that Wiki is the most up-to-date source of
information now, as that effort to get Windows XP working on a Mac
was started before there was full support for VM systems -- they
only referenced Parallels in their earlier Wiki because VMWare
Fusion wasn't available at the time. There's a forum that may be
more up to date.
On Dec 14, 2008, at 2:05 PM, Cara Quinn wrote:
Esther, well, thanks very much for that site!
It turns out though, that I didn't even need it, thankfully so, as
it was soooo complicated it made my head spin! lol!
This was the simplest fix in the world, and I didn't see it written
anywhere on the web. I simply looked in boot.ini and changed the
two references to the disk partition from 3 to 4. Now, I have no
idea why this should have changed, but apparently the Bootcamp
partition got renumbered. So I tried this on a lark, as I was
thinking I'd need to erase the partition and start again. So I'm
sooo glad it worked! woohoo!
It's interesting that I didn't find this fix anywhere as it seems
so simple and easy. In fact, everything I'd read basically
suggested gloom and doom, in the sense that once one screws up a
Bootcamp partition, by resizing or anything, that it's just useless
and one should just scratch everything and start again.
As I said though, thank you so much for that site though. Though
it's complicated I plan to revisit it as I'd learned a lot in the
short time reading it.
Have a great day and talk witcha soon!…
Smiles,
Cara :)
On Dec 14, 2008, at 11:43 AM, Esther wrote:
Hi Cara,
This is outside of my area of knowledge, but I think the problem
it that Windows (and BootCamp) requires the MBR (Master Boot
Record) to be in a specific location when there are multiple
partitions on a hard drive. This is one of the reasons why a lot
of problems arise from decisions to repartition a disk after the
initial BootCamp installation has been done, and a lot of early
guides basically said, think carefully about the sizes and
parameters you want to set up at the beginning.
Try looking at this web page: "Triple Boot via BootCamp" from the
OnMac.net Wiki and see whether it at least helps answers some of
your questions. You may still end up having to reinstall.
http://wiki.onmac.net/index.php/Triple_Boot_via_BootCamp
HTH
Cheers,
Esther
On Dec 14, 2008, at 6:13 AM, Cara Quinn wrote:
Ben, no prob. It's a Windows error that is basically just as
cryptic and non-explicative as I'd suggested. I'll try to get
you the actual text when I can, (need sighted help for that) but
for now, from memory, it said only that Windows had encountered
an error and couldn't load.
This was when booting into the BC partition. It was a form of
blue screen.
Now, as I'd already said, in the 'little information' I gave,
this only occurred after I'd resized a completely unrelated
partition and left the BC one alone.
I suspect this has to do with OSX rewriting the partition table
after Bootcamp had done so but am not sure. If this is the case,
I'd think there'd be a way to repair this from the Windows
install app or some such. -But that might be too logical /
optimistic of me?… lol!
Unfortunately, there just isn't any other info to give you, so my
apologies but it's as nebulous as it seems. lol! Even disc util
that warned me about the possible boot trouble didn't explain
itself. Nor did BootCamp. I'm also Googling this and as well,
have only run into more vague allusions to non-related Bootcamp
use so really, I'm still in the clouds here on this one.
Thanks though for taking time to respond.
Have a great day!…
Smiles,
Cara :)
On Dec 14, 2008, at 7:47 AM, ben mustill-rose wrote:
I'd have to agree with the previous 2 replies based on what little
information you gave.
What does the error actually say and is it a bootcamp or windows
one?
On 14/12/2008, David Poehlman <[email protected]
> wrote:
To restore windows on your partition, first, erace it through
bootcamp.
then, install it again.
--
Kind regards, BEN.
email: [email protected]
msn: [email protected]
web: http://www.bmr.me.uk (under construction)
---
View my Online Portfolio at:
http://www.onemodelplace.com/CaraQuinn
---
View my Online Portfolio at:
http://www.onemodelplace.com/CaraQuinn
---
View my Online Portfolio at:
http://www.onemodelplace.com/CaraQuinn
