VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Accessories (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=3)
-- Stowaway Graffiti Problems (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=10396)

I just got the Targus Stowaway for Christmas and love it. I have the latest driver from Think Outside, but I am having a problem with Graffiti after I use my keyboard.

It seems I can write letters but can't do punctuation or shifting after I use my keyboard. The only way is to either go into the Keyboard application and uncheck and then check the checkbox next to "Enable Keyboard". Or do a reset. Both of which I don't want to do.

Has anyone else had this problem. I haven't found any mention of it so far.

Thanks in advance for any suggestions!

Dave.

I have also had this problem with my Visor Deluxe, though I have no way to fix it. I understand that the Stowaway developer kit has a beta of the 1.5 drivers for the keyboard, perhaps they have a fix for it.

__________________
Matt Nichols
[email protected]

I too have the same problem on my Visor Deluxe. My Deluxe is filled with so many programs I figured it was some conflict with another program.

However, the problem doesn't exist on my Prism.

David

Hmmm. I've had different problems, but not that. I find the driver hangs my HVD on reset and causes apphack to freak out. (which is the same thing that happened on my old Pilot 5000 with another keyboard).

I noticed the same thing with my new stowaway.

I upgraded to v1.2 of their driver without even giving the included drivers a shot. Anyone know if this problem exists with the original version as well?

All I did to fix it was uncheck the 'enable keyboard' box while not hooked up. That is something of a hassle, though.

quote:

---

Originally posted by PeloGrande
I noticed the same thing with my new stowaway.

I upgraded to v1.2 of their driver without even giving the included drivers a shot. Anyone know if this problem exists with the original version as well?

All I did to fix it was uncheck the 'enable keyboard' box while not hooked up. That is something of a hassle, though.

---