Game produced in 1991 sells for $91k+ on eBay, gaming device made in 2nd century AD sells for almost $18k on Christies. Should have tried to sell it on eBay first.
You could try an old trick that I used during my tech support days.
You can kill Windows explorer with task manager and then use the File/New Task option to restart explorer with a higher level user. You can then do whatever you need to as that user (e.g. control panel, delete files, add hardware, etc). When you're done, you can just repeat the process and start explorer again as the original users.
I haven't tested 100% in Windows 8 (killing and starting explorer as another user does work), but it should work in Windows 7 and below.
I used this any time right clicking an exe and selecting "run as" wasn't enough
Fn key is switched with Ctrl - this completely breaks my touchtyping. On last Lenovo I used there was no way to make Fn to be Ctrl, don't know if it was possible on T420. But with that little swap I can't call that keyboard decent.
On T530 you can do it from the BIOS settings. I have the weirdest problems with that though. If I touch-type I always use the Fn as Ctrl, but when I read a more complex shortcut and try to apply it by looking at the keyboard (like: Notepad++ XML format = Ctrl+Alt+Shift+B), I always use the "Ctrl" instead of Fn frist.
The Fn key has always been the leftmost key on Thinkpads, so I don’t really care about that. However, even my T410s has the option to swap Fn and Ctrl in the BIOS, so I would assume the T420s to have it, too.
I feel you. I use my desktop 80% of the time, touchtyping on my Das Keyboard. When I switch to my T430s my typing speed definitely drops for that reason.
This is by far craziest I've seen: "Error Message: Your Password Must Be at Least 18770 Characters and Cannot Repeat Any of Your Previous 30689 Passwords" [1]
My $0.02 is on a dull explanation: the max length and #remembered parameters must be configurable and/or depend on the access method, and the printf-like call that creates the message string must have passed erroneous pointers pointing into some DLL. When that DLL changed, or when another DLL changed in size, causing the DLL to move, the pointers pointed to different, but still constant data.
