|
Author |
Thread Statistics | Show CCP posts - 33 post(s) |

Zataaki
GoonFleet GoonSwarm
|
Posted - 2007.12.07 10:22:00 -
[1]
I'm running a windows partition on a mac. When I try to start up windows it gives me the hal.dll error. My cd drive is currently broken and won't read any cd's. What are my options here other than get the cd drive fixed so I can use the windows cd to recover?
|

Zataaki
GoonFleet GoonSwarm
|
Posted - 2007.12.07 10:34:00 -
[2]
Originally by: PsyMan Edited by: PsyMan on 07/12/2007 10:31:37
Originally by: Zataaki I'm running a windows partition on a mac. When I try to start up windows it gives me the hal.dll error. My cd drive is currently broken and won't read any cd's. What are my options here other than get the cd drive fixed so I can use the windows cd to recover?
One option you can try if you have access to another PC or Mac with a firewire port and a firewire cable is to plug a cable between the 2 machines and boot your mac while holding down T, this will start it in target disk mode and your hard drive will show up on the other machine as an external disk, you can then make the repair. Or of course you could boot it to your mac OS and repair it from the mac, I recommend to use textwrangler (free) to create a new boot.ini though as it will produce a nice clean file.
I'm actually getting an error with hal.dll rather than boot.ini. If anything I will have to repair it from mac OS. My roommate has a pc with vista but we dont have firewire.
|

Zataaki
GoonFleet GoonSwarm
|
Posted - 2007.12.07 10:48:00 -
[3]
Edited by: Zataaki on 07/12/2007 10:54:28
Originally by: PsyMan
Originally by: Zataaki
Originally by: PsyMan Edited by: PsyMan on 07/12/2007 10:31:37
Originally by: Zataaki I'm running a windows partition on a mac. When I try to start up windows it gives me the hal.dll error. My cd drive is currently broken and won't read any cd's. What are my options here other than get the cd drive fixed so I can use the windows cd to recover?
One option you can try if you have access to another PC or Mac with a firewire port and a firewire cable is to plug a cable between the 2 machines and boot your mac while holding down T, this will start it in target disk mode and your hard drive will show up on the other machine as an external disk, you can then make the repair. Or of course you could boot it to your mac OS and repair it from the mac, I recommend to use textwrangler (free) to create a new boot.ini though as it will produce a nice clean file.
I'm actually getting an error with hal.dll rather than boot.ini. If anything I will have to repair it from mac OS. My roommate has a pc with vista but we dont have firewire.
I will boot camp my mac and see how the boot.ini file works on a mac partition, I believe the hal.dll problem is a direct result of a missing boot.ini file. In any case it shouldn't take long to do a skeleton install of windows xp and get back
Awesome thanks, it's like 3 AM here and I'm gonna sleep but I'll check this thread again in the morning.
edit: I forgot to mention my Windows partition is NTFS while it's usually FAT32 with bootcamp. I'm also using windows xp home edition service pack 2.
|

Zataaki
GoonFleet GoonSwarm
|
Posted - 2007.12.07 21:53:00 -
[4]
Originally by: PsyMan Edited by: PsyMan on 07/12/2007 12:18:19
Originally by: Zataaki Edited by: Zataaki on 07/12/2007 10:54:28
Originally by: PsyMan
I will boot camp my mac and see how the boot.ini file works on a mac partition, I believe the hal.dll problem is a direct result of a missing boot.ini file. In any case it shouldn't take long to do a skeleton install of windows xp and get back
Awesome thanks, it's like 3 AM here and I'm gonna sleep but I'll check this thread again in the morning.
edit: I forgot to mention my Windows partition is NTFS while it's usually FAT32 with bootcamp. I'm also using windows xp home edition service pack 2.
Sleep well, I can confirm that the hal.dll screen on boot is a direct result of the boot.ini file being removed as I have boot camped my imac and deleted it (backing it up) and the resulting boot gives me exactly the same problem. I also opted for an ntfs partition which makes things a little tricky but not impossible to fix. I am going to now fix it and document it HERE to save you searching this thread and to allow anyone else effected to hopefully repair their mac.
And sound and a Blue Screen happened to me too, it turned out to be faulty realtek onboard HD sound drivers, I updated the drivers from the realtek website and all was good in the world., annoying thing was it would only BS when I turned the armour repairer on.
Oh man you are awesome, thank you! Everything is working perfectly now
|
|
|
|