I just realized my pilot link is faster in GUI mode vs terminal mode with the same user. Any ideas why??

I'm using pilot-xfer for both and specified the speed in ~/.bashrc.

what is pilot link ??

Pilot link is a terminal program that the GUI frontends like JPilot need to communicate with your serial or usb handheld device.

The pilot-link suite of tools contains a robust library and a series of conduits for moving information between your desktop or workstation and your Palm handheld device, such as those made by Palm, Sony, Handspring, Handera, and others. It also includes language bindings for languages such as Perl, Python, and Java.


Pilot-Link Homepage

Wow that's a first a gui program that is faster than the shell! Is your shell fast for everything else besides this pilot thing?

Also, when you use the pilot thing, does the shell start spitting out tones of info? A lot of times shell programs are slowed down because it can't write to your screen fast enough. You can try redirecting the output some place else. You could also use a framebuffer. Depending on your video card it will use your hardware accelearation in the shell then that text just flys by. I recommend a framebuffer though.

Framebuffer will only help in the real termianasl tty1, tty2, etc. It wont help with the pty's in X.

If you use the gnome termianl or kde Konsole it just compounds the problem because they use anti alias pretty fonts and sh*t, which takes forever to scroll and output text.

xterm is ugly but much faster at scrolling text. Eterm is also one of my favorites.

Hmm, that framebuffer explanation makes sense. If my framebuffer is having trouble, would error logs be generated in /var/log or somewhere??

Okay so it does output a lot of text then? Question number is are you even have a framebuffer? When you boot your machine do you see a pengiun in the termianl? If not you aren't using a framebuffer. I had to recompile my kernel and use an initrd.img just to get one working.

Also a prelimanary test you could do is trying running your program in xterm. If it is faster, well then you have your answer.

I do have text with no errors on my framebuffer screen and I do have a penguin logo when Slack boots. I just disabled this penguin logo in /etc/lilo.conf by commenting vga =771 and enabling vga = normal. Ran lilo>reboot.

Fonts were bigger and no penguin. Pilot-xfer is still slow in the terminal.

In GUI, pilot-xfer is a lot faster using an x-term window.

I'm thinking about re-compiling my kernel, chbin. I am using kernel 2.4.29. Which kernel did you re-compile to get the framebuffer working?

You know know you problem.

Some framebuffer drivers have options you can set on the to get accelerated scollling. Think mine is setting xyres, mttr, and accel in the kernel boot options. Using video = , , , , , , , ...

Read the Documentation of whatever framebuffer you are using. If you are using the generic one then when you compile your new kernel include the specific one for you video card and get rid of the generic one.

To begin with just use the 2.4.29, work no prob. Have you ever compiled a kernel before. You are going to have to have detailed knowledge about you hardware.

cat /proc/pci
cat /proc/cpuinfo
cat /proc/interrupts

Hell just read a bunch of stuff in /proc and learn exactlly what is in your box, trust me it's knowledge you are going to need when you compile a new kernel.

Just successfully (for the 1st time) compiled the 2.4.29 kernel last week. I am going to work off the same config file I used and do a make xconfig and just look for video cards. I'm not sure what this laptop uses-I'll look through /proc.