Different HAL loaded than defined in boot.ini

  • Thread starter Thread starter jhcw
  • Start date Start date
J

jhcw

Hi

Im creating the image on T400, which has a dualcore processor. I also want
to use the same Image on T4x computers, mostly T42. I've extracted all hals
from SP3.cab to \system32\drivers and added /hal=halacpi.dll (the HAL that
t42 uses). I've also replaced ntoskrnl.exe and ntkrnlpa.exe in system32 with
proper ones, as T42 is a uniprocessor system. However, even with
/hal=halacpi.dll option it seems to loads halmacpi.dll and ntoskrnl is
something like ntoskrnmpa (can't remember the exact name right now, but the
multiprocessor one). I wouldn't really mind it using this one as it seems to
boot up and run very nicely, but it seems to cause problems with the WLAN
adapter. I get "network controller" in device manager, and it will not accept
drivers that I know are the correct ones for the system.

I've tried kernel parameters in boot ini, renaming hal.dlls, using
updateUPHAL option in sysprep etc, but nothing seems to help really and I'm
running out of ideas. If anybody has an idea what I'm possibly doing wrong,
or how to get around it and load the correct HAL, I would greatly appreciate
it.
 
Hi John,

Thanks for your reply. However I just noticed I've been reading an old
logfile, so the HAL is correct. I suppose the problem (wlan adapter not
working, wont accept correct drivers) is somewhere else. I'll keep looking
for something.

SUppose this proves again that sometimes a break is needed.

-jon
 
Hi John,

Thanks for your reply. However I just noticed I've been reading an old
logfile, so the HAL is correct. I suppose the problem (wlan adapter not
working, wont accept correct drivers) is somewhere else. I'll keep looking
for something.

SUppose this proves again that sometimes a break is needed.

-jon
Click to expand...

There have been some interesting BIOS issues with the T4 and 500's,
and Lenovo isn't budging in spite of customer uproar. Have you looked
into Universal Imaging Utility. They handle all the drivers and HAL
changes across the entire environment and I know they found a way
around the T4 and 500's.
Hope this helps
 
Back
Top