

InterviewSolution
1. |
Solve : Can't Access BIOS? |
Answer» Not sure where I should post this, so I'm posting it here. Anyway, I have an Intel D945GCNL MOBO, with Intel NL94510J.86A BIOS. The problem is I can't access it. It worked fine a couple of months ago when I was running Windows Vista Home Premium. The stupid computer crashed when I attempted to INSTALL a wireless NIC. I couldn't get it back up and running for the longest time. Well the other day I did get it to work again with Windows Xp, and it runs fine. The problem is like I said, I can't access the BIOS. Hey, even a blind squirrel finds a nut once in a while... Sorry I haven't gotten back lately, been out of state to my brother's wedding. Anyway, I'm using a Mircosoft wireless keyboard. A Mutimedia Keyboard 1.0A to be exact. The POINT is that I used the same one before when I set the computer up with Vista. Somehow this all started when the computer crashed and I tried to install XP on it instead, and it wouldn't detect any DRIVES. I used a boot CD and ran some different diagnostic software, such as ones you would find on Hiren's Boot CD. Anyway, I'd have to check, but one program said it detected my drive. That's when I attempted to reinstall XP, and for some reason it worked. Though now like I mentioned I can't access the BIOS anymore. I can try a different keyboard, though I don't think that's the problem. Though I guess that's why it's called troubleshooting.Yes, get a good old-fashioned keyboard that doesn't depend upon drivers being loaded first, and I bet you'll be able to get to the BIOS. Aegis, you are probably 100% right about the keyboard deal, though I don't have any extra lying around. However, I did solve my problem, and now I FEEL stupid. Apparently my keyboard has a F Lock key on it. So, I pressed it and tried again, and it worked. All that frustration over one little key. Thanks for everybody who helped me with this.No worries -- I have a keyboard with a similar F lock -- it's goten me in trouble in other ways -- I didn't think of the lock, because it's not the keyboard I'm using right now. Thank you for posting your problem resolution -- it always helps to see / learn the fix for a problem. |
|