Sporadic "Contains an invalid path" on Ctrl+2 off

Sapphireblue · Post by **Sapphireblue** » Mon Mar 14, 2005 2:17 am

I am using TextPad 4.7.3 on Windows to write Java code. I'm a student of Java programming so it's entirely possible I have a problem rooted in Java and not in TextPad and just wouldn't know the difference...

Most of the time the TextPad compile and run functionalities work fine. However, three times today, I've had something ugly happen. I compile and all is well, then I hit Ctrl+2 to run it. There is a pause, a command prompt/Java console comes up and remains blank for a second, and then I *think* some monster string of Java console errors scrolls by and the console closes before I can see any of the text.

At that point, if I try to compile or run the script again I get an error "G:\Project1 contains an invalid path" in TextPad. (G:\ is a USB flash drive.) When I attempt to browse the contents of G: via the Open... command or via Windows explorer it shows no contents on G:\. I have to "Safely Remove Hardware" the flash drive, unplug it, and put it back in before I can see the contents again. One time this happened today, one of the .java subclass files of the app I was trying to run was eaten and replaced by a long string of high-ASCII characters, all of them y with an umlaut or something. Needless to say I'm concerned about my source code being eaten.

I don't think my code is the problem here, as once I've unplugged/replugged the flash drive I can compile and run the same code with no changes in TextPad with no problems. Until it happens again.

Any thoughts at all? I'd hate to have to work off my hard drive, makes my life much easier to be able to just carry my flash drive back and forth between home and school and work so I always have the latest version of everything. Thank you.

talleyrand · Post by **talleyrand** » Mon Mar 14, 2005 4:14 pm

Sounds more like an issue with Windows and the device to me, rather than a TextPad thing since browsing to it with Explorer is failing. Is there any diagnostic you can run on the device itself to make sure it is working as intended? If it is, perhaps try a different computer to see if the USB port on the one machine is flaking out.