Installing Boot Camp drivers on Win XP

Hi and welcome to Discussions,

do you have any external devices connected to your Mac during the driver installation ?
(external harddisks, printer, scanner, etc.)

If so, disconnect all external devices leaving only (if needed) mouse, keyboard and display connected and try the driver installation again.

Hope it helps

Stefan

Ok, so much for that...

Is that a retail or OEM/SystemBuilder version of XP you installed ?

Or is there a chance that it is a manufacturer-bundled version, that originally was sold with another computer ?
Such versions are known to cause problems on Macs.

Stefan

Hi,

the mentioned error message with 'HAL' made me thought about that.

"Originally implemented with Windows NT, but still used with later Windows versions like XP, Vista and even Windows 7 the Hardware Abstraction Layer (HAL) refers to a layer of software that deals directly with your computer hardware. Because the HAL operates at a level between the hardware and the Windows NT executive services, applications and device drivers need not be aware of any hardware-specific information. The HAL provides routines that enable a single device driver to support a device on different hardware platforms, making device driver development much easier. It hides hardware dependent details such as I/O interfaces, interrupt controllers, and multiprocessor communication mechanisms. Applications and device drivers are no longer allowed to deal with hardware directly and must make calls to HAL routines to determine hardware specific information. Thus, through the filter provided by the HAL, different hardware configurations can be accessed in the same manner."

(Quoted from the Windows NT Ressource Guide)

Due to the fact that some manufacturer can 'cripple' the Windows versions they sell with their computers to nearly their own likings, it might really be that the Windows CD you used for your BootCamp install is in essence not 'compatible' with your Mac.

My own experiences with such Windows versions is limited to a old Toshiba Laptop that included a Windows XP Home version and I never tried to install that version on another computer.
So I really can't say if there is a remedy for this.

Regards

Stefan

I have been trying to install XP on my new MacBook Pro using Boot Camp, and I have had exactly the same problem as @massiverisingson. Mac HAL won't start, and I may not have enough permissions, etc. The result is also similar, no keyboard or trackpad functionality.

Coincidentally, the XP version I have been using also turns out to be OEM, though completely new and unused - I was given it by a retailer some time ago. I have come to the conclusion that @Fortuny/Stefan is right, and that OEM versions of XP are probably the problem.

I see little alternative but to invest in a retail version of XP and hope for the best.

Hi hzviewmax and welcome to Discussions,

non-bundled OEM versions of XP SP2 or later should work without problems with BootCamp.
Fact is I use one myself.

Have you ruled out the obvious, like the mentioned disconnecting unneeded external devices plus that you are logged in as Administrator in Windows ?
And using the OSX DVD that came with your newe MBP and not an older one.

Stefan

Hi,

looking at the other posters problems with a non-bundled OEM version of XP but also on a new MBP might lead to a general problem with BootCamp XP and the new MBPs.

Could both of you please post the results from using the System Profiler in OSX like this:

Modellname: Mac Pro
Modell-Identifizierung: MacPro1,1
Prozessortyp: Dual-Core Intel Xeon
Prozessorgeschwindigkeit: 2.66 GHz
Anzahl der Prozessoren: 2
Gesamtzahl der Kerne: 4
L2-Cache (pro Prozessor): 4 MB
Speicher: 8 GB
Busgeschwindigkeit: 1.33 GHz
Boot-ROM-Version: MP11.005C.B04
SMC Version: 1.7f8

(leave out the Serial Number) !

Maybe we can find similarities and/or a pattern.

Stefan

Let's see what hzviewmax comes up with.

Like said maybe we can find a pattern.

...might be enjoying his weekender... 😉

Did some more googling about the MacHal error but could only find this mentioned in conjunction with either Vista 64-bit or Windows 7 64-bit plus two hits which seemed to indicate a not-being Administrator issue.

No mentioning of a 'simple' 32-bit Windows XP SP2 (3) with this error.

While the 'pure' "missing or corrupt hal.dll" error surfaces quite a lot of times, the MacHal one seems really rare.

Stefan

You have also to consider the language of your Windows. I have more than 4 occasions where a similar problem occurred due to the Greek Windows.