![]() | |||||||||||||
Messages in this thread |
Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > open "blah hi" as binary #1 (or something like this) > print #1, "jkfsdjlkfsdjkl" > close #1 > > Then you can open "blah hi" with the QBASIC program again. > > The system never reported it as an error or anything, and it would show up as > a valid file when you did a DIR. In fact, when you got a directory listing, > it would show it with the space. I think you will find that the space probably became chr$(255) if I remember correctly. I believe some of the OS/2 rule breaking files are also char 255. (Maybe it was 128... I cant even remember what space is off hand, but I do remember that these tended to be something NOT space.) To check it out go to a DOS/windows/etc box and try to edit that file... you know how to get all the blah hi stuff.. for the space do ALT+255 (255 must be done on the numpad). Anyway, this is how I remember it. I used to hide things in files that way as well. Trever - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:44 [from the cache] ©2003-2008 | |||||||||||||