this is more to share an experience, then to solve a problem, but it's a bit unique, so i'll put it out there and hopefully save someone else some grief.
ended up having to reformat my hd, so i changed the boot sequence in cmos to cd first, then hd. but my system would freeze up, bypass the cd boot and go to the hd, where it would just hang until a hard reboot. tried formatting on another system but some compatibility issues. was going to order new hd and just go that route, when i noticed that my keyboard lights would come on, but i was unable to numlok or f-lock during the boot process. changed to old keyboard i had laying around, and it solved the problem. i was able to get to the cd boot, reformatted and now working through all the re-installs.
the problem keyboard is a saitek, that evidently waits for certain drivers, before fully functioning; some of the functions light up, but not all. using the saitek now w/o problems, but it's something i'll remember, if i ever go that route again. sometimes its the simple things.
ended up having to reformat my hd, so i changed the boot sequence in cmos to cd first, then hd. but my system would freeze up, bypass the cd boot and go to the hd, where it would just hang until a hard reboot. tried formatting on another system but some compatibility issues. was going to order new hd and just go that route, when i noticed that my keyboard lights would come on, but i was unable to numlok or f-lock during the boot process. changed to old keyboard i had laying around, and it solved the problem. i was able to get to the cd boot, reformatted and now working through all the re-installs.
the problem keyboard is a saitek, that evidently waits for certain drivers, before fully functioning; some of the functions light up, but not all. using the saitek now w/o problems, but it's something i'll remember, if i ever go that route again. sometimes its the simple things.
Facebook
Twitter