Why an "*.txt " document is saved as "MSDOS" application?

Hi - a ***.txt document is an MS DOS file, by definition. What is wrong with that?

There's nothing MS-DOS-like in a .txt file. It's just data, totally OS-independent. Although Unix-systems have another way to denote end-of-line than DOS and Windows use.
And, of course, a text file isn't an application, but some kind of data.

The problems seems to be the description for the .txt file somewhere in the registry.

Kees

DOS/Windows, Mac, and *nix all use different line end encodings. For the useless trivia buffs, if memory serves... *nix uses a LF (Line Feed) character, Macs (pre-OS X, which I'm unsure about) use CR (Carriage Return), and DOS/Windows uses CR/LF.

The text itself is standard 8-bit ASCII codes most of the time. So aside from some formatting abnormalities opening a text file made on one platform to another, it should still be usable.

Just figured I'd help Mr. O'Daneil out. It seems he must be too busy to add this useless bit of trivia himself, and what are these forums if not places to help one another?

... or ***.cmd it would no longer be a simple text file as far as the OS is concerned. It would be an executable (although it would not actually execute and a com suffix would get you an error message).

What does your registry show you at HKEY_CLASSES_ROOT\.txt