CompuServe Thread

#Summasketch wont work

5 messages in this thread
#82228From: LCS/TelegraphicsFeb 8, 1994 11:54 AM
Patrick: Your bus mouse card may be set for the same IRQ line (#3) as that of COM2's default. It is likely then that the bus mouse driver and the tablet driver are fighting for the same resource and the tablet driver is losing. Another consideration is that no version of 3D Studio, past or current, understands how to set a COM port irq correctly. It behaves as if every one always uses COM1 for their digitizer. Try swapping the modem and tablet COM ports. Good Luck. Daniel Haney
#82460From: Evan Yares [WeirdTM]Feb 9, 1994 12:47 AM
Daniel: I haven't seen you on the forum before. Have you introduced LCS/Telegraphics to the folks here? I'm sure that they'd like to know that your company is the premier developer of digitizer driver software. Evan
#82566From: LCS/TelegraphicsFeb 9, 1994 12:25 PM
Evan: Hush! 🙂 1) I do not seek notoriety for my employer. 2) While LCS/Telegraphics does indeed write a lot of digitizer drivers, the germaine thing is that a message on a forum can eliminate someone's need for an extended customer service call to one of our clients, or by extension, the need of our clients to pass a formal bug report back to us. 3) How do you do, sir. I am Daniel Haney, the author of ALL of the current digitizer ADI drivers that LCS/Telegraphics licenses to OEM's and by God, I'm good at it! (Tongue planted firmly in cheek!) 4) This forum is the fastest possible feedback on any screw-ups, er… mis-features that remain in my, er.. that is , LCS's production code. Hiya, Hawahya, Daniel Haney.
#82575From: David J. MarksFeb 9, 1994 12:58 PM
Have you considered on your own, or for your employer, writing a revised 3DS-only ADI driver for the more-common tablets? (Or would it constitute a conflict of interest with your clients?) Just a thought.
#82632From: LCS/TelegraphicsFeb 9, 1994 4:03 PM
David: The short answer is: It is not my problem. The Multimedia team, given time, resources, and a few good nights sleep should make 3DS3 fully ADI 4.2 compliant so that any OEM- supplied ADI 4.2 digitizer driver will work with it. They are currently consumed with genuinely pressing problems or they would have done so by now. So far, 3DS3 has incomplete but useful support for ADI 4.1 digitizer drivers. This would be enough for drivers that poll (request data from) the digitizer, but it is a problem with interrupt-mode drivers. 3DS3 never sends a TERMINATE command to the driver. This means that if the tablet sends data=generates a hardware interrupt when 3DS is shutting down, you get a protection fault or a cold reboot, if you are lucky. The work-around is to take the tablet puck out of proximity when you exit 3DS. Whining and Flaming, Daniel Haney.