Then tried a variety of iterations of the dd command similar to your syntax but could not get dd to work.
Errors? Couldn't restore? I'd think dd would work since it is just a bit copy. Curious before I try...
Glad you got it working, the long way
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Deleted file in Windows, will no longer boot.
- Thread starter notredewey
- Start date
- Sort by reaction score
Errors? Couldn't restore? I'd think dd would work since it is just a bit copy. Curious before I try...
Glad you got it working, the long way
Wirelessly posted (NokiaN70-1/2.0539.1.2/SN359380002126483 Series60/2.8 Profile/MIDP-2.0 Configuration/CLDC-1.1)
Hal.Dll is hardware abstraction layer
for me when the boot.Ini file is pointing to the wrong partition i get the error
try using fixboot in the recovery console
Hal.Dll is hardware abstraction layer
for me when the boot.Ini file is pointing to the wrong partition i get the error
try using fixboot in the recovery console
My dd command were very similar to the template you provided. But very few bytes were copied if any. I always got a file name to show up, usually with 0 bytes, when I tried my versions.
I was hoping you would give me something different. But your syntax looked the same.
I also tried the mount names with no luck either.
Be curious if you get it to work, and if you do, what your exact command is when it worked.
It has been years since I was an avid Unix user -- back in the 70's/80's -- so I am a bit rusty and may have missed something.
The long way is better than no way!Glad you got it working, the long way
I am just glad that I got it to work. I was getting tired of re-installing Windows!
I don't remember, but I don't think you can dd with a mounted drive (that could be disatrous)...You have to unmount first and another site I just read mentioned only doing this only in single user mode....
I'll report back once I attempt this. Maybe tomorrow evening or this coming weekend. My fear is the recovery part since I don't want to have to reinstall windows, but at least I have the long way
Since the file missing is hal.dll, you are basically outta luck. HAL stands for Hardware Abstraction Layer, this is probably the lowest level program file besides ntloader. Even if you copy another one, there is no guarantee it will work completely correctly. A reinstall is needed and prudent.
As for backing up the Windows partition, follow Sushi's advice and get the current version of NetRestore from Bombich's site. Also, dig around on the site and find ntfsprogs.pkg, this allows NetRestore to see the Windows partition, even if it is NTFS.
We just had an Apple engineer on campus doing a workshop on imaging and with NetRestore and NetBoot he was able to partition the drive, install Mac OS, name the machine based on the mac address, and install Windows with a couple simple clicks. Now if only I could get our 400 systems to do that too.
As for backing up the Windows partition, follow Sushi's advice and get the current version of NetRestore from Bombich's site. Also, dig around on the site and find ntfsprogs.pkg, this allows NetRestore to see the Windows partition, even if it is NTFS.
We just had an Apple engineer on campus doing a workshop on imaging and with NetRestore and NetBoot he was able to partition the drive, install Mac OS, name the machine based on the mac address, and install Windows with a couple simple clicks. Now if only I could get our 400 systems to do that too.
Sometimes windows says hal.dll is corrupt if your partition table changes.
Im using a pc. It originally came with two partitions
Partition 0=FAT 32 Recovery partition.
Partition 1=NTFS Windows partition.
I formatted the fat32 partition to install linux, which means boot.ini was pointing at partition 1 but windows cant see linux partitions so the NTFS Partition was partition 0.
Recovery Console.
Bootcfg /add
worked for me.
(or manually editing boot.ini)
Im using a pc. It originally came with two partitions
Partition 0=FAT 32 Recovery partition.
Partition 1=NTFS Windows partition.
I formatted the fat32 partition to install linux, which means boot.ini was pointing at partition 1 but windows cant see linux partitions so the NTFS Partition was partition 0.
Recovery Console.
Bootcfg /add
worked for me.
(or manually editing boot.ini)
Thanks!I don't remember, but I don't think you can dd with a mounted drive (that could be disatrous)...You have to unmount first and another site I just read mentioned only doing this only in single user mode....
I'll report back once I attempt this. Maybe tomorrow evening or this coming weekend. My fear is the recovery part since I don't want to have to reinstall windows, but at least I have the long way
Will be looking forward to hearing how it went. Good luck!
Unfortunately, I started a training course at work and require my Windows partition for a little while. I will have to try when I have some time, just in case, it doesn't go as planned.
Completely understand.
Probably a wise choice.
You might want to try what I did first so that you can restore even if it takes a few steps.
That way while you are trying out different methods, you won't have to reinstall Windows like I had to.
Still training...However, I recently had to upgrade a Windows machine HDD, and used a GParted Live CD to clone the drive and that got me to wondering if that might also work. Its nice because of its GUI.
I'll let you know, I promise
Resolving HAL.dll issue within your windows install
Being a Windows guy I know its odd for me to be wandering through the "support" forums. But to be honest I'm waiting on the new version of Mac OSX to come out along with the new cores before I make the switch in June.
First thing is first for the HAL fix, run a "Windows Repair" on the partition that holds your Windows install. When you running through the windows install screens this will be called what is commonly known as the second "R". Simply the Windows Repair install will rip out all system files and reinstall Windows over the old keeping the windows registry intact. By doing this all program installs remain installed and usable (most of the time). Sometimes drivers will need to be reloaded but this step is pretty easy to complete.
Now is this does for some reason not work you could just blow the system away and redo which is easy enough. I wanted to through out a couple commands to use at the first "R" recovery console that might also me nice to know as well. "FIXBOOT" is always a nice help if you have FAT problems, "FIXMBR" will resolve master boot record issues when you rarely have them, "chkdsk /r" will almost always resolve corrupt file issues preventing full booting into Windows but you might want to start this at night and go to sleep it can take awhile.
I apologize if this issue has been explored adnausem I just wanted to toss my two cents in and pretent I'm part of the MAC community just about 4 months early.
Peace Out,
-J
Being a Windows guy I know its odd for me to be wandering through the "support" forums. But to be honest I'm waiting on the new version of Mac OSX to come out along with the new cores before I make the switch in June.
First thing is first for the HAL fix, run a "Windows Repair" on the partition that holds your Windows install. When you running through the windows install screens this will be called what is commonly known as the second "R". Simply the Windows Repair install will rip out all system files and reinstall Windows over the old keeping the windows registry intact. By doing this all program installs remain installed and usable (most of the time). Sometimes drivers will need to be reloaded but this step is pretty easy to complete.
Now is this does for some reason not work you could just blow the system away and redo which is easy enough. I wanted to through out a couple commands to use at the first "R" recovery console that might also me nice to know as well. "FIXBOOT" is always a nice help if you have FAT problems, "FIXMBR" will resolve master boot record issues when you rarely have them, "chkdsk /r" will almost always resolve corrupt file issues preventing full booting into Windows but you might want to start this at night and go to sleep it can take awhile.
I apologize if this issue has been explored adnausem I just wanted to toss my two cents in and pretent I'm part of the MAC community just about 4 months early.
Peace Out,
-J
Being a Windows guy I know its odd for me to be wandering through the "support" forums. But to be honest I'm waiting on the new version of Mac OSX to come out along with the new cores before I make the switch in June.
First thing is first for the HAL fix, run a "Windows Repair" on the partition that holds your Windows install. When you running through the windows install screens this will be called what is commonly known as the second "R". Simply the Windows Repair install will rip out all system files and reinstall Windows over the old keeping the windows registry intact. By doing this all program installs remain installed and usable (most of the time). Sometimes drivers will need to be reloaded but this step is pretty easy to complete.
Now is this does for some reason not work you could just blow the system away and redo which is easy enough. I wanted to through out a couple commands to use at the first "R" recovery console that might also me nice to know as well. "FIXBOOT" is always a nice help if you have FAT problems, "FIXMBR" will resolve master boot record issues when you rarely have them, "chkdsk /r" will almost always resolve corrupt file issues preventing full booting into Windows but you might want to start this at night and go to sleep it can take awhile.
I apologize if this issue has been explored adnausem I just wanted to toss my two cents in and pretent I'm part of the MAC community just about 4 months early.
Peace Out,
-J
Thats what I tried to say earlier, Sorry if it wasnt very understandable,
Try Bootcfg /add
while in the recovery console.
Have you looked here?
Have you looked at this link?
http://support.microsoft.com/kb/314477
This provides instructions from microsoft for this exact scenario.
Have you looked at this link?
http://support.microsoft.com/kb/314477
This provides instructions from microsoft for this exact scenario.
Any word?Still training...However, I recently had to upgrade a Windows machine HDD, and used a GParted Live CD to clone the drive and that got me to wondering if that might also work. Its nice because of its GUI.
I'll let you know, I promise
Still patiently waiting. The long way is tiring!
Any word?
Still patiently waiting. The long way is tiring!
Sorry man...just had a baby daughter, haven't been on the computer much lately. I did see there was a newer version of GParted that came out recently. I tried an older version and it didn't seem to boot.
Wow! Congrats on the baby daughter. Completely understand.
After you have a chance to sleep, then maybe you can give it a try. I figure that I will hear from you in a couple of years!
Again, congrats on your new daughter!
Wow! Congrats on the baby daughter. Completely understand.
After you have a chance to sleep, then maybe you can give it a try. I figure that I will hear from you in a couple of years!
Again, congrats on your new daughter!
I'm currently in the process of trying out the dd method. I was going to evaluate that netrestore program and the dd method. However netrestore trashed my windows partition, came up with an error saying can't find autocheck or something similar and then would blue screen immediately. Luckily i did the dd image first. It is copying back onto the windows partition now. (Not sure how much it will like doing it as i am copying an NTFS image onto a FAT32 partition) Hopefully it works, will let you know when it finishes.
Edit: Straight copy of the .dmg of my previous windows install onto the empty Bootcamp partition did not work. When trying to boot into Windows presented with a black screen with a blinking white dash. I am now using NetRestore to clone the windows.dmg back onto the Bootcamp partition, hopefully this works, it's currently restoring so i will leave this over night and report back in the morning.
Edit: Did some research seems that it is a whole lot more complicated that just straight dding back on to the partition. It will copy back no problem but the bootloader or whatever it is called doesn't know that there is an operating system on there and so will not boot. For instructions on how to do this using the terminal see here. I tried this but for some reason i got a permissions error which even remained after i used the "sudo" command. The DD command took 3 hours both ways on my computer so a very long process, could reinstall everything easily in that time. Anyway the program that i would suggest the most as it is the program that i have managed to delete and restore my bootcamp parition is winclone, take about 30 minutes to backup (less if you choose other options) and about 15 minutes to restore the partition. Very pleased with this application and how it works, highly recommended. Netrestore i have found to be very buggy and actually cause my bootcamp partition to get destroyed.
Sushi...Finally got around to trying. Had to upgrade to a 250GB drive.
dd didn't work, and I also tried a gparted live CD with no luck either. Interesting part is the files definitely copied, but OS X fails to mount it and boot camp bootloader didn't even see it. I could mount the Volume manually, but it didn't really resolve my issue. The one thing I didn't try was dd'ing the little 200mb partition that is created by boot camp. I think this has a role in things.
If I had more time, I know I could figure it out, however, my work obligations require me to get up and running so I am just reinstalling Windows - which is probably the best for me given all the crapware I have installed in the past year.
Thought I would report back, as promised - only 4 months later
dd didn't work, and I also tried a gparted live CD with no luck either. Interesting part is the files definitely copied, but OS X fails to mount it and boot camp bootloader didn't even see it. I could mount the Volume manually, but it didn't really resolve my issue. The one thing I didn't try was dd'ing the little 200mb partition that is created by boot camp. I think this has a role in things.
If I had more time, I know I could figure it out, however, my work obligations require me to get up and running so I am just reinstalling Windows - which is probably the best for me given all the crapware I have installed in the past year.
Thought I would report back, as promised - only 4 months later
Thanks for the update.Sushi...Finally got around to trying. Had to upgrade to a 250GB drive.
dd didn't work, and I also tried a gparted live CD with no luck either. Interesting part is the files definitely copied, but OS X fails to mount it and boot camp bootloader didn't even see it. I could mount the Volume manually, but it didn't really resolve my issue. The one thing I didn't try was dd'ing the little 200mb partition that is created by boot camp. I think this has a role in things.
If I had more time, I know I could figure it out, however, my work obligations require me to get up and running so I am just reinstalling Windows - which is probably the best for me given all the crapware I have installed in the past year.
Thought I would report back, as promised - only 4 months later
Recovery from delete...
Please see the posts from Nitromaster as he has provided the answer.
When you disturb boot.ini in the root window directory, the loader looks for the boot files on the wrong partition, and gives you the "HAL" message.
Any number of ways to recover depending upon what has been deleted.
Of interest, on my MBR bootcamp boot.ini file the lines that tells the loader where to start from is found in this file: (see copy immediately below)
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
The last line is wrapped in my editor.
The key here are the "...partition(3)..." statements.
On the MBP the EFI partition (hidden partition) and the OSX partition are the first two partition, and Bootcamp is third.
While I have not tried to restore bootcamp, I use Acronis to generate an image backup off to an external USB drive. This backup can be mounted as a virtual drive (just click on the image icon) and you can recover one or more files by dragging/dropping.
Neil
Please see the posts from Nitromaster as he has provided the answer.
When you disturb boot.ini in the root window directory, the loader looks for the boot files on the wrong partition, and gives you the "HAL" message.
Any number of ways to recover depending upon what has been deleted.
Of interest, on my MBR bootcamp boot.ini file the lines that tells the loader where to start from is found in this file: (see copy immediately below)
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
The last line is wrapped in my editor.
The key here are the "...partition(3)..." statements.
On the MBP the EFI partition (hidden partition) and the OSX partition are the first two partition, and Bootcamp is third.
While I have not tried to restore bootcamp, I use Acronis to generate an image backup off to an external USB drive. This backup can be mounted as a virtual drive (just click on the image icon) and you can recover one or more files by dragging/dropping.
Neil
There you go; PEBKAC. Never delete stuff you think you don't need. Only delete stuff you KNOW you don't need. I'm surprised you haven't deleted anything important from your Mac OS X partition yet.