Dave, you can change the HAL with the standard (free) version of TBOSDT.
WinXP contains "all" the HALs. It is just a matter of installing the multi-processor one.
eg from this line..
copy 0:\WINDOWS\servicepackfiles\i386\halmacpi.dll 0:\windows\system32\hal.dll
( 0: is the mounted WinXP partition)
If the WinXP partition doesn't contain halmacpi.dll then it can be copied from the TBOSDT flash drive.
Thanks Brian, if it's just a matter of copying and renaming the file then that can be done from windows 7.
I thought maybe it kept the halmacpi.dll intact and changed all the registry entries.
fraiser-
You said that you did a clean install of XP on the new system as a test,
How did you get around the SATA/AHCI problem?
Did you slipstream the drivers into the install disk, use a floppy driver disk, or change the BIOS setting to ATA mode?
DaveH wrote:if it's just a matter of copying and renaming the file then that can be done from windows 7.
I'll be interested to hear if it works. It may not. I just converted the HAL to halmacpi.dll in my old P4 computer. It no longer boots. Freezes at the end of the black and white loading bars. Using a WinPE CD I copied halacpi.dll into Windows\System32. In that folder both hal.dll and halacpi were present. WinXP still doesn't boot.
I booted to a WinPE CD. hal.dll was 132 kb and halacpi.dll was 80 kb. I deleted halacpi.dll. Then booted to a TBOSDT CD containing halacpi.dll. Used this...
copy halacpi.dll 0:\windows\system32\hal.dll
WinXP now boots. In Windows\System32 hal.dll is now 80 kb. The 132 kb hal.dll has been change to a 80 kb hal.dll.
halmacpi.dll is a 132 kb file
halacpi is a 80 kb file
So TBOSDT does something that WinPE copy/paste can't do. Weird.
Brian_K wrote:
I'll be interested to hear if it works. It may not. I just converted the HAL to halmacpi.dll in my old P4 computer. It no longer boots. Freezes at the end of the black and white loading bars. Using a WinPE CD I copied halacpi.dll into Windows\System32. In that folder both hal.dll and halacpi were present. WinXP still doesn't boot.
I booted to a WinPE CD. hal.dll was 132 kb and halacpi.dll was 80 kb. I deleted halacpi.dll. Then booted to a TBOSDT CD containing halacpi.dll. Used this...
copy halacpi.dll 0:\windows\system32\hal.dll
WinXP now boots. In Windows\System32 hal.dll is now 80 kb. The 132 kb hal.dll has been change to a 80 kb hal.dll.
halmacpi.dll is a 132 kb file
halacpi is a 80 kb file
So TBOSDT does something that WinPE copy/paste can't do. Weird.
When you copied halacpi.dll into the system32 folder did you rename it to hal.dll?
actually rename hall.dll to something like hal.old and then rename halacpi.dll to hal.dll?
DaveH wrote:
When you copied halacpi.dll into the system32 folder did you rename it to hal.dll?
actually rename hall.dll to something like hal.old and then rename halacpi.dll to hal.dll?
Good idea. Yes, that works. Very easy to do too.
Good, because I'm having problems trying to use tbos and the manual is rather big.
Maybe thats what windows does and the specific file in use is always renamed to hal.dll
You never see anyone get the error "can't find halacpi.dll"?
I agree thats the easy part, the hal can be replaced from windows 7. Then if the BIOS has a ATA or comapatibility setting the system could be booted into XP and the chipset and SATA or AHCI drivers could be installed.
TBOSDT isn't easy. The boot disk boots to > (a command interpreter prompt)
Type tbosdt and press Enter. Now you will see @A:\> (tbosdt prompt)
To see what is on HD0 use
list hd 0 (and press Enter)
Amongst all the info, write down the partition ID you require. Let's say WinXP is ID 02 then you can mount the partition with a numerical drive letter, 0 to 9. Let's use 0: for example.
mount 0: 0 0x02 (and press Enter. 0 0x02 is HD0, partition 2)
To see what's in WinXP type
dir 0: (and press Enter)
Like DOS you can change the prompt to @0:\> by typing 0:
You can CD to a folder, etc
To view a text file use type eg
type boot.ini
Just a short introduction.
I guess I should RTFM.
I didn't know I had to type tbosdt first. LOL
I was stuck at the > prompt and tried ?, help, copy, list, everything I could think of.
The HD2 is from the Disk Management. It would be easier for me to start Windows XP from scratch. The Windows XP disc is retail and Windows 7 is OEM. The old emachine PC is still working.
I'm trying to get the hard drive (with Windows XP) from the old computer working on the new one. The other drives have been disabled while testing this. When booting from the drive the blue screen error appears and reboots straight away. Do I have to change a setting in the BIOS so IDE drives work with SATA motherboards?
You need to change the hal, and you need to also install the SATA drivers.
You have a few options here, you can decide what may be easier for you.
Option 1
If the Bios has a setting under SATA to change it to ATA mode or compatability mode. Then all you should need to do is change the hal and the system should boot in ATA mode. Then in windows you can install the chipset and SATA drivers.
See my post here about using the Ghost recovery disk to manually switch the hal from a single core to multicore CPU.
Option 2
Perform a repair install on XP. You have the retail disk to do this. Only problem is you need the install disk at the same service pack level as the installed version of XP. If your installed version is SP3, and your retail disk is not, you will need to use nLite to slipstream the service pack into it. While your at it you can also slipstream the SATA driver.
Option 3
Since your old system still works, you may be able to force the SATA driver to install onto the secondary IDE chain that you are not using. A different hal can also be loaded from the boot.ini file so another entry could be added to boot with the multicore hal.
Once you get XP booting on the new system you can add that into the dual boot with windows 7.
Dave
What type of chipset do I install and do I slipstream this with XP? The Windows disc only has a Repair using the Recovery Console. Can I repair the installation from there?
I slipstreamed the sata drivers and SP3 but can not repair the Windows because my CD does not have this function. I've also changed the hal for use with the multicore CPU and copied the standard sata drivers to the system32 folder. After doing this, when the computer boots it's restarting without showing the BSOD. The mode on the BIOS has always been set to ATA. The comnputer still does not read IDE drives.
I'm not going to spend any more time working on this since the dual boot does work although the Windows XP is installed from scratch.
So thanks for all the help.