>> 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.)
I've used the ALT-255 trick to create files with "fake spaces" in
them that were virtually impossible to deal with unless you knew
what was being done. The QB files were real spaces though, not
255's.
-- Mike A. Harris - Computer Consultant - Linux advocateLinux software galore: http://freshmeat.net
- 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/