I have a 1gH DP G4 with Panther 10.3.2 running on it. I have installed
VPC 6.1.1 with Windows XP. I get it up and running, but about every
other day I receive an error when booting the VPC HD stating NTLDR:
Fatal error 32769 reading BOOT.INI. Anyone know why I keep getting
this error. Any way around it? It is VERY frustrating to have to
rebuild the hard drive every other day!
Any help would be greatly appreciated.
I hear your pain. We've had our vpc set up for several months. I've
got very important info and programs on there for work and when we
called MS for help- they told us we have to reinstall VPC and all of
our Windows programs. It's a nightmare. Please let us know if you've
found a way to solve this problem.
I'm the one who had the same problem as you. I guess I could tell you
a little more about our setup to see if there are any similarities:
-We have a G4 Powerbook 1.33 ghz, 17"
-We added 512 mb ram for a total of 1 gb (512 dedicated to VPC)
-We run QuickBooks Pro, MS Office, Visio on VPC and I set up a network
with other PC's through my ethernet connection on VPC
-This is the first time this has happened to me and I've been using
VPC for about 6 months. I was using QuickBooks Pro and MS Word on
VPC, I went to lunch. When I came back my screen was totally black
and there was only a cursor which responded to movement but I couldn't
access the menu or anything. We did a manual restart of the Mac.
When I restarted it and tried to get back into VPC, I go the same
message... NTLDR: Fatal Error 32768 reading BOOT.INI
Hope this helps us both out in finding the cause or solution to our
problem!
Thanks,
Eden
Daryl Boman - 27 Jul 2004 16:23 GMT
Sounds like XP NTLDR can not find the BOOT.INI file.
The BOOT.INI contains the information for the operating systems available to
boot.
Especially helpful to edit when you need to dual boot, but I digress.
Have you tried booting from the XP cd and doing a repair?
Did you make a repair diskette. I think that those files are on there.
Try making a new VPC HD and booting from it and making the other drive the
D: drive and look to see which files are missing. They can be copied from
the bootable drive to the D: drive.
Good luck.
> I'm the one who had the same problem as you. I guess I could tell you
> a little more about our setup to see if there are any similarities:
[quoted text clipped - 16 lines]
> Thanks,
> Eden