Just thought I'd post my findings. I'm testing the Vtablet driver 7.11 on a
new Win 7 Pro 64 bit system. (Dell T7500)
CPU Intel X5680 6 core
Graphics Nvidia FX-5800 4 GB
Memory 24 GB
Moinitor: Dell 30" 3008WFP
Hard Drive 450 GB SAS
Tablet: Calcomp DrawingBoard III 12x12
Software: AutoCAD MEP 2011
The initial install of the Vtablet 7.11 driver went fine.Configuring
AutoCAD..no problems. All was good until I closed and re-opened some files.
My AutoCAD display area was reduced to only about 24" of the 30" screen. the
only way to fix it was to exit and re-enter AutoCAD. I was using the nVidia
3D display driver. After switching to the Autodesk driver the problem has
not reappeared (so far ).
Also, after "Publishing" to a multi-sheet dwf file, all tablet buttons and
mapping were lost. I had to exit and re-enter AutoCAD. I was using the
"Publish in background" option. After disabling this option and allowing
each drawing in the set to open, the tablet worked fine. Not good, but I can
live with that.
The next day, upon system boot, the Vtablet driver failed to load saying my
serial port is being used by another device (huh?...no changes were made to
system from the previous day). A dialogue box suggested reloading the
Vtablet software which I did and so far so good.
In my opinion the Calcomp crosshairs seem to have a slightly slower reponse
time than the 7.46 drivers on an older system. This may just be because I'm
not yet used to such a large display. (I was using a 20" flat screen).
I'm almost ready to start using this system for production work. Another day
or two of testing should do it. I'll keep my finger crossed ;-)
"Jim" wrote in message ...
>Just thought I'd post my findings. I'm testing the Vtablet driver 7.11 on a
>new Win 7 Pro 64 bit system. (Dell T7500)
Thanks for sharing. I have v7.02 version running at work on a Dell T7400 in
XP Pro 64-bit driving my Calcomp DBIII 12x12. I haven't tried the updated
7.03 yet, much less the beta you're running.
>The next day, upon system boot, the Vtablet driver failed to load saying my
>serial port is being used by another device (huh?...no changes were made to
>system from the previous day). A dialogue box suggested reloading the
>Vtablet software which I did and so far so good.
I've gotten this from time to time and on the previous v 6 release. In fact
I got it this morning. Not sure what it is but a re-boot along with turning
off the tablet and turning it back on usually clears it up. My tablet
usually stays on permanently whether the machine is on or off. I also have
a Blackberry, and the Desktop Manager and USB driver creates a virtual
serial port through the USB. Maybe something gets crossed up with the real
serial port every once in a while. It happened maybe 2 or 3 times in the 2
years I've been using the Vtablet driver. I wouldn't worry about until it
gets to such a point that a re-boot or reinstall simply fails to fix to it,
or if it starts doing that all the time.
>In my opinion the Calcomp crosshairs seem to have a slightly slower reponse
>time than the 7.46 drivers on an older system. This may just be because I'm
>not yet used to such a large display. (I was using a 20" flat screen).
No. It's a difference in the driver. I noticed the difference too, and I'm
using the same monitor that I used on the old XP 32-bit system with the
Calcomp 7.46 driver. I also noticed the jumpiness in the crosshair movement
on my home machine when I tested the older Vtablet drivers a few years ago.
Still running XP Pro 32-bit at home (with a Calcomp DBII 12x12 there), I'd
try out a new Vtablet release to see if they smoothed out the crosshair
movement, find that it was still stuttering, unload it and reload the 7.46
I will say that the home machine booted up much faster with the Vtablet
driver installed than it does with the Tabletworks 7.46 driver. But the
much, much smoother crosshair movement is a deal maker for me. It's why I'm
sticking with the Tabletworks at home until I move to 64-bit (at which point
I'll have to buy the VTablet driver for myself).
Thanks for the info. If I need to reboot a few times a year to initialize
the driver, that will be OK....as long as it doesn't get any worse.
Reinstalling it however WILL be a problem.
So I'm not imagining that crosshair movement is not up to snuff. It is
usable however. Again, this is the beta driver I'm testing, so I'm hoping
the final release is a little better.
Well, the crosshair movement has always been like that. Not sure why since
Mr. Schumer wrote the original wintab 1.1 driver used in Tabletworks up to
version 7.46. Unless Calcomp modified if further after he was... well, no