I'm not trying to fool the OS. It is already fooled the way I understand the problem. The scanner created files with "/" in the name.
On Jul 22, 2013, at 10:32 AM, Mark Wieder wrote: > Dar- > > Monday, July 22, 2013, 8:05:15 AM, you wrote: > >> That is what I was suggesting, with the fix above. But, now I >> have less faith in that. It might be that that character is not >> really there but is displayed by Windows Explorer. > > I'd be very wary of trying to fool the operating system with things it > isn't expecting. At one point I managed to create a file with a name > that ended with ".txt " (note the trailing space). I could see it by > displaying the directory, but the file was inaccessible to either the > file system or any utility I threw at it. That file stayed right where > it was until the hard drive finally died. > > -- > -Mark Wieder > mwie...@ahsoftware.net > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
