Eric, I corrupted my file system over and over trying to figure out what was going on when loading in the various ADVx.DO files for the ADVENT adventure game using TS-DOS. Turns out those .DO files had an EOF character at the end. And that ended up in the files because I'd manipulated them on an OS at the time that appended the character to each file.
Once I removed those EOFs, problem was gone. Could you be running into the same situation? On Thu, Feb 7, 2019 at 10:01 PM Eric LK <[email protected]> wrote: > I found yesterday Adrian Ryan's DEBUG program on this page: > http://www.club100.org/cgi-bin/blosxom2011_06.cgi > > That's when things started to go weirdly wrong. > I'm using a Rex with FW 4.9 and the TS-DOS ROM with mComm 2.50. I've > never had any issue with those before but to make it short, loading > "DEBUG.DO" which is a plain ascii file ends up corrupting the > filesystem of the M100. > > I tried again after a cold reset (Ctrl+Pause+reset), and the problem > is really easy to reproduce: > - go to basic and type CALL63012 to open TS-DOS > - Download the DBMAKE.DO text file and press F4 to check its size > after the download (should be 886 bytes as expected) > - Download the DEBUG.DO text file and test again the size of DBMAKE.DO > which should now be 0 > > If I re-download it, I'll be able to generate the debug.co but saving > the file and loading it I get very weird Top/End/Exe values (not > always the same). Also when I check the sizes of existing files I got > totally random filesizes (including a 39000+ bytes file at some point) > > Could a bad character in a DO file compromise the M100 filesystem > after a simple download (weird stuffs starts just after downloading, > without even opening or trying to execute the file). > > The only thing I noticed with DEBUG.CO is that the file includes and > EOF byte at the end of the file (chr$(26)). I think it's ignored as > the transferred file is one byte smaller than the one on the mComm > server but could that be the issue? > > I haven't been using mComm/TS-DOS for very long so I may miss > something obvious here but could someone with more miles behind them > confirm this is a bug or should I look into a fault on my M100? > > Here is a short video where I reproduce the problem (sorry for the > shaking, I was hand holding the camera while trying to type) : > https://youtu.be/RPhuwlKhuAM > > Eric > > PS: I also tried to switch the "Memory Power" switch off to have a > real cold reset but to my surprise, even after removing the AA > batteries, my files were still there when I switched on the M100 > again. > -- Gary Weber [email protected]
