Text 61567, 84 rader
Skriven 2010-07-27 20:28:00 av ED VANCE (1:123/140)
     Kommentar till en text av PAUL QUINN
Ärende: Long Filename Troubles.
===============================
PQ> EV> As much as I thought I had learned about these computing machines and
PQ> EV> knowing that they have "Inside Information" so they can Win All the
PQ> EV> time, I never would had thought a simple DOS Style 8.3 filename would
PQ> EV> get changed into a Long File Name.

PQ> EV> PC = 1      Ed = 0   this time.    ;-)

PQ>:-(  Not good, Ed.  I always get 'my way' here, one way or t'other.  That's
PQ>partly why I switched to linux, where a filename is just that: a filename.
PQ>Like you, I still sometimes get frustrated with file & directory naming with
PQ>the DOS batch scripting that I do but persistence usually pays off.

Paul,

I found out why XP gave me a long filename for my .TXT file.

When I saved it in Notepad I saved it as ROUND2IT.TXT.

I forgot that XP would append another .TXT to the end of the filename I
typed.

The other day I trimmed off the extra .TXT and made it a regular 8.3
file/

PQ> EV> P.S. I have no idea what the Tagline will do.
PQ> EV>      I certainly will NOT try running it in DEBUG.

PQ> EV>  * SLMR 2.1a #T348 * It's scary when you see B8 00 4C CD 21 and
PQ> EV> understand

PQ>Mmm... I had some trouble with this because I've only got a text capture of
PQ>first 127 ASCII codes.  As far as I could figure it's roughly:
PQ>"[char][null]L[char]!", sans the quotes.  Using the table and the Windows
PQ>calculator to convert between hex & decimal, all I could decipher was two of
PQ>the characters.  :(  With only a string of four chars and an exclamation poi
PQ>and none of them likely to be a vowel because of the -null- char, it can't b
PQ>terribly important.[smirk]

PQ>OTOH, if it is a binary sequence it probably won't execute in Windows'
PQ>protected mode IAC.  =:)

I wouldn't know if it wouldn't or not.

I grabbed that tagline many years ago, probably even before Windows 95.

Somewhere around here I have a book with a chart of what those codes
mean but I can't figure out where I stashed it.    ;-)

I tried playing around with DEBUG.COM a bit to find a empty space in the
computers memory so I could type it in and then Unassemble it to see
what the assembly language code was, but I am NOT RUNNING IT to see what
would happen.

PQ>On a similar note, one of the most interesting life's experience I've had wa
PQ>when I worked at an Army headquarters where there was a signals unit providi
PQ>communications via teletype machines.  I was just one of their 'customers',
PQ>mind you, and would use their facility as I would with any other 'black box'
PQ>operation.  You know, I draft up a message and hand it over to them for
PQ>transmission.

I was a U.S. Navy Radioman.

PQ>Anyhow, the crux of the message: some of the signals operators would wander
PQ>around with lengths of punched tape draped over their shoulders, and I once
PQ>to talking with one of them who said that sometimes they'd do that until one
PQ>the machines was free in order to run the tape through.  I was somewhat agha
PQ>at the idea that they would take such a lackadaisical attitude with somethin
PQ>like not decoding them ASAP, but, the feller said that he'd already read it
PQ>knew that it wasn't important.  I mean the guy said that he had already
PQ>translated the hole punches into ASCII in his head!

When I was in the Service we used the 5-level BAUDOT Code from our
TeleType Machines I couldn't read the hole code, but I could read the
Alphanumeric Characters printed on the edge of the punched tape.

IIRC ASCII Code tapes have 8 holes per character instead of the 5 holes
per character that the Baudot code used, but they probably Print the
characters on the edge of the tape also to make it easier for someone
like me to read them.


 * SLMR 2.1a #T348 * Conclusion: The place where you got tired of thinking.
--- Platinum Xpress/Win/WINServer v3.0pr5
 * Origin: Doc's Place BBS Fido Since 1991 docsplace.tzo.com (1:123/140)