Long time since I've used VectorLinux. Two of my computers "burned out" on the same night, both the VectorLinux and CentOS ones (GX270s). Have no idea what happened, the one computer wasn't even turned on. Both power supplies out and the motherboard out on the VectorLinux computer. Nothing else in the house was touched. I replaced the power supply on the CentOS machine. My "big" hard drive (160 Gig) was in my even older GX240, which had openSUSE 11 and hasn't been used regularly for a couple years. So, after procrastinating for almost six months, I finally backed up what I wanted to keep from openSUSE computer, stole and wiped its hard drive and built VectorLinux Deluxe on it. My son gets the GX240 now (which has been my plan for at least a year and a half). I'm a champion procrastinator.
At any rate I'm back to VectorLinux and loving it. I left some free space to dual-boot CentOS on this computer because I'm still studying "Red Hat." (Some day it might come in handy.)
But anyhow, the question...
My brother gave me a QuickPad keyboard for writing (www.quickpad.com
). The only way to use what you've written is to upload the file (via the keyboard port) to an application on a PC or a Mac. I think it's a great idea -- text flows into your word processor just as if you were typing. No problems with file compatibilty, so (in theory) any OS or any application should work.
It does work without a hitch in Windows and, I assume, it would work fine on a Mac (it has an Apple mode), but in a Linux Xwindows application I run into one of two problems, depending on which mode I'm using (PC or Apple). In Apple mode the text transfers, but it's garbled -- some words are fine, most are not. Characters drop out, but it's not random -- it's always the same characters in the same file. I haven't been able to figure out the pattern yet. In PC mode, the first word will transfer, but then the keyboard "whacks out" and the only way to recover is to reboot Linux. So neither mode works in an Xwindows application.
However... if I open a virtual terminal (ALT+CTRL+F2) and transfer the text into jstar (or, I assume, any text editor) it works flawlessly. I can save the file and read it into OpenOfficeOrg Write without issue. (Except, there are carriage returns behind each line so the text doesn't "flow," but that's easily cleared up using Find & Replace.)
So, finally, to the question. What does Xwindows do differently with keyboard input than does a non-Xwindows session? I'm guessing there is a driver between the keyboard and Xwindows, but I have no idea why it's there or how to bypass it for the QuickPad. It's not that important as I can use the QuickPad in the "round-about" way, but I am curious if something like this would be fixable.
Sorry for rambling. I've got a blog (probably a temporary one) for the QuickPad at "quickpadwriting.blogspot.com" if anyone is interested in reading more about it. (I'm long winded there, too.)
Anyhow, it's great to be back. I think this newer hard drive is even faster than the VectorLinux was on the old, much smaller drive.