#Tablet woes
5 messages in this thread
I'm having a strange problem with 3DSr3 and my Summa II 1201 tablet.
I'm using the latest DGPADI driver DL'ed from Summa's BBS(I just prefer it over
the internal one). Anyway, when I run 3DS, my cursor is stuck in about
mid-screen. I do a "* T" via keyboard. Wait a few seconds until the program
comes back with "Can't find Device". Answer OK, then define the Area with the
tablet cursor. Answer OK again and all is well. I save this info as part of my
3ds.prj. Now here's the problem, when I rerun #3DS or load any other .prj file
saved with the same input device config. info. I have to go through the same
routine again to get the tablet to work. What gives, any ideas?
I used a DGPADI with r2 with no problem, so I tried that version of the driver
and the same happens under r3… I also use the tablet under DOS, I disable it
(/off switch) before running 3DS and back on again upon exit, with no problem.
I also have tried deleting and updating 3DSADI.cfg with the same negative
result.
I've also come upon a quick fix for the "polling driver/hanging cursor"
problem when using a 4.1/4.2 ADI driver. I just bounce the tablet (off/on) and
the cursor comes right back until the next time…
I just thought you'd like to know about this because I've seen others having
the same problem.
Thanks for reading,
Paul
Paul, Have you tried just using mouse emulation with your summa. (Tablet.com)
That's what we use on our system and it works great. Although you don't get the
option of picking the tablet area… which would be a problem for AutoCAD it's
fine (IMHO) for 3DS.
Dave Mennenoh
David,
Yes I have, but I've been using a tablet for so long… I really don't like
using the tablet cursor as a mouse and all my other software uses the tablet as
a tablet so it's very uncomfortable for me to use 3DS otherwise.
I'd just like to be able to get rid of the extra keystokes every time I startup
or load a .prj.
Thanks for sharing your idea,
Paul
>> I'm using the latest DGPADI driver DL'ed from Summa's BBS
I may be a bit late with this response as I was away all last week. I hope it
will still shed a little light on the problem.
Following is a thread I saved that describes the problem. (I think it was sent
to you once already, back in March). The key is to find a 4.1 ADI driver, not
4.2.
———————————————
10-Mar-94 01:26:36 Sb: #90233-Help w/ 3DSr3 install Fm: Gus J Grubba
70673,1605 To: Paul Minni 71053,3516
Yep, the RCPADI -> RDPADI was a typo. Good catch. The minute I saw your
config.sys and autoexec.bat files I knew it would be easy to solve your
problems (the user part of the problem was out of the picture! <g>).
Regarding the Summagraphics stuff, here is a message left by Summagraphics
explaining the thing…
————————————————————————— Sb:
#69191-Summagraphics Tablet Fm: Steven M. McGuinness 73144,2412 To: Pierre Jean
72230,3046
SUMMA1.RES:
Topic: SummaSketch Compatibility with 3D Studio, Release 3 By: Steve
McGuinness, Product Marketing, Summagraphics Corporation Date: 11/23/93
After completing SummaSketch compatibility testing and speaking with
representatives from Autodesk, we at Summagraphics have uncovered both a
documentation error and programming bug in 3D Studio R3 ADI tablet driver
interface. Both problems have been reported to a representative in Autodesk
Multimedia Development. They have verbally concurred with us on these problems.
The documentation error notes that the ADI tablet driver should be documented
as an ADI 4.1 compatible driver. It is currently documented to be compatible
with ADI 4.2 drivers. This is why our ADI 4.2 drivers do not work. To get a
copy of our latest 4.1 Protected mode ADI drivers, dial our BBS at (203)
881-5305 and download 011.ZIP. We have dual 14.4 KB modems and are up 24 hours
a day, 7 days a week. Feel free to distribute the drivers to owners of
SummaSketch tablets; however, please note that it is illegal to upload them
onto another BBS.
The programming error notes that, assuming the ADI input driver is 4.1
compatible, the ADI interface does not properly clean up upon program
termination. In English, this means that your system will hang when quitting
the program. Our work around is to move your cursor off of the tablet before
quitting. You should then be able to start another 3DS session without error.
If for some reason you cannot start another 3DS session, restart your tablet
while rebooting your PC.
If you continue to have problems using our ADI 4.1 protected mode drivers with
3D Studio, do not hesitate to call our Customer Service Department at
1-800-728-7866. We are open Monday through Friday, 8:30-5:00 Est. At this point
in time, we do not offer support via CompuServe.
David,
<<< The key is to find a 4.1 ADI driver, not 4.2. >>>
Yea, I've tried both, same result…
-P.M.