|I am currently working on a raid volume that is presenting with the hal.dll file missing error. Nothing I've done has worked to fix this error (hitman kickstart, kaspersky restore, etc). I decided to clone the drive and see if I could play with it externally outside of the raid volume constraints.|
After cloning the disc, when viewing where the boot.ini file was pointed, I noticed it was point to the WINNT file as this machine is an XP upgrade from ME. This is where my problem arises.
I can see the entire winnt folder, including my "missing files", from my win7 machine I use for diagnosis and bench testing, but when I try to insert the master raid drive back into the original volume and repair it using either kaspersky restore or another linux program pre-boot, neither program's file manager is registering ANYTHING inside the winnt folder. 0.00 Mbs, 0 files....
I've never seen this before and am at a complete loss as to whether this is corrupted or what