Keyboard 2000

0 views

Skip to first unread message

Gaynelle Alnutt

unread,

Aug 3, 2024, 5:03:17 PM8/3/24

to tekomrede

I just got an HP 2,000 (At least I think that is the model name) for Christmas, and I've figured most things out on my own, but I can't seem to find a "backlight" option for the keyboard. I'm typing in the dark and I know I should know the keyboard layout but it is kind of different from Desktops, so it makes it very frustrating when trying to input passwords and such.

Either way none of those methods worked, but thank you. It looks like I'll have to buy one of the two things you mentioned, but I wouldn't even know where to start, can you help me with that as well or should I make a seperate post?

Like other recent Microsoft wireless keyboards and mice, the Microsoft wireless keyboard 2000 comes with a USB wireless receiver that doesn't allow pairing any devices not already paired at the factory, as neither the receiver nor the keyboard have a pairing button.

Hi
Using Audacity 2.4.2
Mac Big Sur 11.2.1
I am trying to record Audio from my Roland RD-2000 stage piano into Audacity, however it is not picking up any input despite setting the audio inputs to the RD-2000. I tried Garage Band which recognises the input but only allows the prerecorded sounds which makes me suspect that the program is only picking up a MIDI rather than an Audio input.
Can anyone help?
Thanks

There are three (3) USB ports on the RD-2000: One USB port is used for updates. There is a USB cap over this port to prevent its accidental use. A second USB port is used for recording to a USB flash drive. You could record your performance to the flash drive, then read it back into your computer, for example. The third USB port is used for both MIDI and audio.

Today I wanted to report on my latest experiment; using a dishwasher to help me clean a Microsoft Comfort Curve Keyboard 2000. There are many posts on the internet about this, and after some research, I decided to give it a try, as I had just inherited my keyboard from work.

First decision was; How much should I dismantle the keyboard? Some people have tried running the whole keyboard through the dishwasher, but this typically seems to be followed by letting it dry for days afterwards, and involves some risk because the electronics get wet. Some suggest stripping the electronics out of the keyboard, and washing all the rest. I decided to prise off the key-tops and dishwash those, but leave the main frame safe and dry.

Before removing any keys, make sure that you take a photo or have access to a reference to be sure you know where to put each key back! On the whoe there are few surpsises, but things like the cursor keys would be a little easier with a reference photo.

I found that the carefully pulling on the top of the keys on this keyboard tended to have the best results in terms of getting the keys to pop off. It was a little bit like playing tiddly-winks. I used a letter-opener to get under the keys as much as possible before prising them up, and on-the-whole this worked fine; it was a little thicker than a typical cutlery knife, but a knife would probably have done the job just fine.

The keyboard base and small metal bits were kept separately, and did not go into the dishwasher. I chose to wash the keys in a porous bag intended for use washing small items in a washing machine, and placed it as spread-out as possible on the top rack. I washed it on the lowest temperature setting, and did use dishwasher soap. A number of sites suggested a normal dishwasher drying cycle might be too aggressive, and fearing that it could melt the transfers on the keys I took it out about half-way-through the drying cycle. I laid the keys out on a drying-towel to air-dry.

Once the keys had dried completely the process of returning them could start. Most keys simply click back into place, though some take a little joggling and reseating to get a key that presses up-and-down cleanly and without sticking.

The Intrinsically Safe Industrial Keyboard with Separate FSR Pointing Device is certified for Class I, II, and III, Division I, Groups C, D, E, F, and G devices to reduce the risk of failure in your hazardous areas. As well as pointing, it incorporates a Force Sensing Resistor. Protected NEMA 4X for extremely rugged applications.

Devices made by iKey are designed to lower the failure rate in hazardous locations. Its stainless steel housing and industrial silicone rubber pad ensure NEMA 4X protection in the most arduous of environments. DT-2000-FSR-IS Industrial Keyboard additional functionality is provided by the inclusion of an FSR pointing device. Class I, II, and III, Division 1, Groups C through G are approved by Factory Mutual. There are optically isolated barriers and bulkhead cables included to ensure total protection in dangerous locations. In addition, it features a full 114-key industrial keyboard and two rows of function keys for quick access to software shortcuts with a single input. DT-2000-FSR-IS is the new part number.

Intrinsically Safe Barrier iKey PS2-IS-BARRIER is approved for use in Class I, II, III, Division 1 hazardous areas.PS2-IS-Barrier isolation is provided between the host PC and the keyboard or pointing device, as well as between the signal and power supply connections on the hazardous location side. Interface connections are made by industry-standard connectors. In particular, the connection from the PC uses a mini-DIN 6 pin socket, while the connection to the keyboard or PS/2 device in the hazardous location uses a mini-DIN 7 pin socket. Shop Now!

Has any recalled getting the On-Screen Keyboard (OSK.exe) v1.0 from WinME (yes it comes with WinME) or Win2000 working in 98SE? I have a friend that has disabilities. Here is a screenshot of it on WinME:

I have tried to port it myself by taking MSSWCH.DLL and MSSWCHX.exe and OSK.EXE/OSK.CHM/OSK.HLP from a Windows ME installation and putting them in the WINDOWS\SYSTEM directory and using KernelEX (Setting compatibility to WinME/Win2000 mode on OSK.EXE and MSSWCH.DLL and MSSWCHX.EXE), and registering MSSWCH.DLL with regsvr32 msswch.dll but it says a corrupt version may be in memory. I tried it with the KernelEX mode to normal and disabled but it still says a corrupt version may be in memory. I ran OSK.exe with normal mode and disabled mode and WinME/Win2000 Mode and it just says the program has performed an illegal operation and will be shut down. KERNEL32.DLL seemed to be causing the problem.

I'm not on Win9x at the moment, but surely you can just test it and see if it runs. If it doesn't, it might just need a small edit to satisfy the version check. There are some folks here ( MDGx I think ) who ported lots of WinME to earlier Win9x.

Because I didn't know about that file I went and located a 3rd party alternative to use on Win98se called On-Screenkeyboardportable.exe by John T. Haller ( link ). You learn something new everyday here.

I'm afraid that this is probably not a version conflict, it looks like they compiled the EXE or that DLL for something specific in the WinME system. I didn't have time to debug it ( in fact I am not even sure I have a debugger on that Win98se machine any longer ), nor did I scan for deeper dependencies that might be tucked away in there. Perhaps another day.

I have actually got it working by copying the explorer.exe and shell32.dll files and placing them in their appropriate location and placing MSSWCH.DLL and MSSWCHx.exe and OSK.exe in SYSTEM then running OSK, but I do NOT recommend doing this. It can totally mess up your system. ALWAYS have a backup of your original explorer.exe and shell32.dll files and get ready to copy them back in MS-DOS mode if you decide to try it. You don't need KernelEx for this trick. Here is a picture:

Go to the Windows Setup tab, click Accessibility, then click Details. Check both Accessibility Options and Accessibility Tools then click OK and then OK once more. If you are prompted for your Windows 98 SE CD insert it. Continue with that and if it says that a file being copied is older than the one already on your system, click Yes.

Unzip the files to a folder of your choice and run INSTALL.BAT. Then click on Start>Programs>Accessories>Accessibility>On-Screen Keyboard. You should have a successful installation of the Windows ME OSK.

Note: If there is a down arrow in the Accessibility folder, click on it. Then it will show the OSK shortcut. The reason why it does that is because WinME/Win2000/WinXP shell sometimes hides unused shortcuts in the Start Menu under a down arrow. After you run the program from that location in the Start Menu once then it will show the shortcut normally and not hidden so you won't have to click the arrow again.

I also figured out the reboot issue! The A1000 keyboard does not have a separate RESET signal wire, it only has 4 wires on the connector. Also the 4-wire reboot code in this sketch can be applied to my previous A2000 code to make it work on 4-wire A2000 keyboards.

Annoyingly, my 4-wire A2000 keyboard (and possibly others), ignore the first keystroke. What happens is the Leonardo waits for the first keystroke to sync with the keyboard, and during that sync phase misses the keypress. However it does get the key release, so I added code there to process it as a press-and-release. Because of that, held-down modifiers (shift, ctrl, alt) are ignored. I did get CTRL+Amiga+Amiga to work as the first keystroke though.