| PLEX86 | ||
The System360 Model 20 Wasn't As Bad As All That 3864The System360 Model 20 Wasn't As Bad As All That 3866 This is on a Windows 98 box? MS didn't invest much in DOS after 6.2. Since... Well, it's like this: xx0.txt .. xx9.txt are what my Nortons file recovery program named the fragments. Norton did not return the thing as a single file because ??? whatever it does, it didn't recognize the pieces to fit together. So I don't right now (yet) know if they have extraneous trailing ^Zs. The returned files are pieces of a yenc encoded file. the xx0.txt file contains the yenc header =yenc ... and the last file (I called it) xx9.txt for posting contains the =yend ... text. Since it was a yenc encoded file, that had been downloaded off of a newsgroup, it was 8bit text with lines terminated by CRLFs. but should not contain any control characters. I look at the pieces in Vim which can work with binary. ie. Vim doesn't mung file content like Word or other text editors. After cleaning the xx files up as best I can, I concatenated the pieces and tried to decode the beast. yenc32 said that the file was corrupted. Well the comments about a trailing ^Z alerted me to, just something else, to check trying to clean the mess up. Thanks for your interest. Ps. I have looked for cmd.exe retrofitted to W98, and in the process learned some interesting details. Everybody discusses the 'for' command but not any other enhancements to any other utilities. -- Rostyk The System360 Model 20 Wasn't As Bad As All That 3865 Rostyslaw J. Lewyckyj As pointed out elsewhere, they are in the cmd.exe on Win 2000-XP, not command.com. That's irrelevant...
|
||||
The System360 Model 20 Wasn't As Bad As All That 3865 Alt Folklore Computers from Newsgroups The #1 Usenet Provider on the Internet
|
||||