Of course, they DID have an input device -- the remote computer on the GPIB port. It was a design mistake not to have that port be able to control all of the device, including the underlying OS, or to have the OS not NEED a local input. That IS what the GPIB is for, after all.
I agree, I think its not wise to blame everything on the manufacturer. The customer has to be also careful about these things and know what are the specifications and the configurations they need for their specific task.
Leave it to microsopht to include something that will paralize a system because of something that you should be able to ignore. And I am amazed that it was that hard to operate a mouse with verbal commands. Of course the best substitute for the mouse would have been one of those "pre mouse" knob boxes. Back in the days prior to windows infecting computer systems with the " syndrom. Microsopht critics know what I mean.
"Co-workers tried to help me navigate the mouse without being able to see the screen, but we didn't have much luck, so we contacted the manufacturer. The only response we received was: "Well, we didn't think of that. Sorry.""
Noor, very funny answer. Some time, the responses from customer supporting peoples are very funny; which can cause you laugh and sadness at same moment.
TJ, I think they would have had the same problem hooking up the keyboard as they had with the mouse. Of course, a USB port on the front panel would have allowed either and made this a non-problem. The customer, knowing that they were rack mounting the units should have anticipated this situation, however.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.