javaMan
Premium,MVM
join:2002-07-15
San Luis Obispo, CA
| hal.dll error and new DVD drive
Does anyone have any idea why I would get a hal.dll error on boot after changing out a DVD drive? I guess the real question is what will it take to get XP to accept the new drive. If I put the old one back in, the system boots fine.
--
Woe unto them that call evil good, and good evil; that put darkness for light, and light for darkness. . . Isa. 5:20 |
|
javaMan
Premium,MVM
join:2002-07-15
San Luis Obispo, CA
| All I can figure out is that it must have been specific to the Pioneer drive I was installing because I exchanged it for an LG and it worked just fine. As I recall I had the same problem with the Pioneer I was replacing but after a little fiddling around I was able to get Windows to load. Oh well, I guess I'll steer away from Pioneer in the future.
--
Woe unto them that call evil good, and good evil; that put darkness for light, and light for darkness. . . Isa. 5:20 |
|
wingnut
Go Wings
Premium
join:2001-02-06
Sterling Heights, MI | reply to javaMan
Hello...Is this the only dvd drive? If so then by default the jumper is set to slave. Did you move it to master or cable select(CS)? If not then try that. Hope this helps.
regards
--
jimmy |
|
ChiTang
Premium,MVM
join:2002-08-23
Alhambra, CA
| reply to javaMan
I got a feeling that it may be a bad firmware in the Pioneer DVD. The way I see it is that, when a new device is detected, OS pulls the vendor ID and add it to registry. What if the vendor ID string is invalid or have invalid character in it? I'll bet you can't even use the Pioneer DVD in a new install as well. I have many bad hardware that causes BSOD during of "installing driver informatation data base" of a new install.
--
I used to be indecisive, now I am not sure. |
|
