Hi, Am Freitag, 19. November 2004 21:55 schrieb Christopher A. Williams: > in my 10-local.rules file. I use a palm Tungsten T. It worked fine for a > while, but lately it has stopped working. I get a null pointer exception > in what appears to be visor.c but I'm not sure. When I repeat the > hotsync attempt, I noticed that it tries each time to use a different > virtual USB port (ttyUSB1, then ttyUSB2 on the next try, ttyUSB3, > etc...). If I reboot, we start over with ttyUSB0. All I know is it now > doesn't work with uncanny consistency... I noticed the same thing here. I might be wrong, but it seems to happen when the connection gets lost, but the syncing application (pilot-xfer, kpilot, etc) is still active and doesn't release the port. Does this also happen when you close or kill the application and restart it? Stephan
