I want to access BIOS on my ThinkPad x120e. I have tried to do it several ways like pressing F1 button for couple times, but it doesn't access the BIOS anyway.
How can I access the BIOS on ThinkPad x120e?
NOTE: I'm using Windows 7
Thanks.
As soon as you power on your computer, there should be a message that says "Press F1 to enter setup" or it might say "Press ESC to interrupt normal boot process". At this point, you should be prompted to enter the BIOS.
Needless to say that it doesn't matter what OS you have, bacause this process is OS indipendent. When you access BIOS, your OS is not even loaded yet.
Related
In my laptop Toshiba satellite L640, there are 2 issues
1] when I press on Power button it does not start OS I have to press any keys to start the OS.
2] When the battery is inserted in its slot and charger is connected, the battery does not charge in fact the status doesn not even change to Plugged in. But, when I remove the battery and turn the laptop on it works fine.
Can anyone please help me in these issues ?
the first issue,you can fix in the BIOS, you can set your PC to turn on by pressing any key on the keyboard, you have to remove this configuration and you're done, and the second problem, do not really understand, but i suppouse is a protection system.
I have been trying to get windows 8.1 to force into a blue screen, but all of my attempts have failed. I don't really want to go into driver code or anything to do it, but just crash it using some sort of silly loop hole.
I tried creating the CrashOnCtrlScroll registry and it doesn't seem to work, even after restarting my computer. I also tried ending csrss, but microsoft has decided to let the user have no control and denies access at all costs (even after an informative prompt window).
I looked online for a while, but can't find anything on blue screening 8.1. It seems that everything out there is for 8 and below.
Notmyfault , a portable tool created by Microsoft's Mark Russinovich for the Windows Internals book will help you get a BSOD with more than a couple of ways (i.e High IRQ fault, hang IRP, stack trash, deadlock, etc)
Which registry key have you tried? There is different key location for PS2 and USB Keyboard.
USB Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid
Add DWORD32, name= CrashOnCtrlScroll, value =0x1
PS2 Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt
Add DWORD32, name= CrashOnCtrlScroll, value =0x1
Restart. Hold the RIGHT CTRL key and press SCROLL LOCK twice quicky.
I'm doing some driver development on my Windows machine and I've been wondering why pressing the PrtSc (print screen) button to take a screen capture seems to hang my machine. There are some forums that suggest this happens when the DEBUG boot option is set in Windows and that this is a panic/bug-check in the Windows kernel.
Is this a Windows bug? Or is this actually useful in some way, like in Linux where PrtSc/SysRq is actually a kernel interrupt key?
UPDATE #1: I'm using Windows 7 x64 Professional Build 7601.
https://msdn.microsoft.com/en-us/library/windows/hardware/ff541727(v=vs.85).aspx
You can disable the SYSRQ key by editing the registry. In the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters registry key, create a value named BreakOnSysRq and set it equal to DWORD 0x0. Then, restart the computer. After you have restarted the computer, you can press the SYSRQ key on the target computer's keyboard and it will not break into the kernel debugger.
Obviously, you're likely using a usb keyboard, so make sure to add the BreakOnSysRq = 0 value data pair to kbdhid\Parameters (and for good measure hidusb and kbdclass, not i8042prt. This will prevent the PrntScr key from being interpreted as SysRq.
After erasing the hard drive of my MacBook Pro 2011, I realized that I must've done something wrong, because whenever I boot, the computer will ask for the hard drive password. Might this have to do with the fact that I chose Journaled, Encrypted?
I ran into this too. If you go to the "Security" preference pane, you should see a message that says "File Vault is turned on for the disk . Some users are not able to unlock the disk." Click the padlock in the lower left of the preference pane to authenticate, then click "Enable Users" and select which users you want to allow. They'll then be able to unlock the disk when logging in, instead of at boot time.
Had the same issue after doing an erase/encrypt of the disk followed by a re-install of OS/X. I just put in the password I used to encrypt the drive and it allowed me to log in and then continue the install.
Since I updated to OSX Lion I got a strange issue.
I am used to never shut down my Mac, I simply put it in hibernate / sleep mode.
But since the update to Lion the mac just starts up at random times.
Day and Night I can hear the CD-Drive sound when it wakes up.
The screen does not even go on, it stays black but the as soon as you hit any key the monitor just turns on.
This is really annoying as it sometimes wakes you up at night when you MAC is booting up.
I could not find a similar issue reported yet.
Thanks
Sebastian
Given the RTC (Alarm) wake reason, ensure Wake for network activity is turned off. See the last comment in the thread at https://discussions.apple.com/thread/3247367?start=0&tstart=0
Also ensure you have not scheduled wake. See http://osxdaily.com/2010/07/17/why-mac-wakes-from-sleep/
Launch the Terminal and type the following at the command line:
syslog |grep -i "Wake reason"
OHC: stands for Open Host Controller, is usually USB or Firewire. If you see OHC1 or OHC2 it is almost certainly an external USB keyboard or mouse that has woken up the machine.
EHC: standing for Enhanced Host Controller, is another USB interface, but can also be wireless devices and bluetooth since they are also on the USB bus of a Mac.
USB: a USB device woke the machine up
LID0: this is literally the lid of your MacBook or MacBook Pro, when you open the lid the machine wakes up from sleep.
PWRB: PWRB stands for Power Button, which is the physical power button on your Mac
RTC: Real Time Clock Alarm, is generally from wake-on-demand services like when you schedule sleep and wake on a Mac via the Energy Saver control panel. It can also be from launchd setting, user applications, backups, and other scheduled events.
Hope this fixes your problem.