thanks, I'll look into this. I think it probably relates to the use of the buffers by REX, but I don't know for sure.
On Mon, Mar 23, 2020 at 3:15 AM Tom Wilson <[email protected]> wrote: > I reproduced it on the 200. > > 1. Cold booted (I turned the 200's memory switch off before I put it > away.) > 2. Started Rex with CALL 61167,2 > 3. Create a text file TEST.DO > - This is a test > - This is line 2 > - This is line 3 > 4. Created a new backup called "TEST" > 5. loaded a previous backup "BAK1" > 6. Launched REXMGR and copied TEST.DO > 7. exited REXMGR and opened TEST.DO > 8. The file contents appeared correct. > 9. F7, selected line 2, F5 (copy) > 10. The word "Test" appeared in place of the highlight. When I pressed > Paste, the program locked up. > 11. I used the reset button to restart the computer. The file now says > "This is a←" > > It seems to behave differently with TS-DOS and with Cleauseau/ROM2 > installed, but the end result is the same - using the clipboard on that > file leads to the file getting mangled. > I also tried this with a BASIC file, and it did not have this problem. I > did the same thing, but before step 9, I typed Edit and then followed the > same procedure. No lockups. > So either the BASIC open/save process fixes whatever file pointers are > bugged, or the problem only happens with DO files. > > > > > On Sun, Mar 22, 2020 at 10:33 PM Peter Noeth <[email protected]> wrote: > >> Currently discovered this. Firstly I have a T102, 32K and a REX, Software >> 4.9 (CS=5E09)/Firmware 6(1). >> >> I copied a small .DO file (47 bytes) to RAM from another REX image. I >> then ran TEXT on the file and found that highlighting a section with F7 and >> pressing F5 to copy it to the paste buffer, caused the computer to lock up >> and had to be cold booted. This behavior occurs whether the REX hook is >> active or disabled after the file has been copied. >> >> I tried this with several .DO files, just to see if it was repeatable, >> which it was. The file content was correct when viewed in the TEXT editor. >> Maybe something in the FCB (file control block) in the directory is not >> correct? >> >> Any ideas Steve? Maybe you could look into this since you are doing >> current development to REXCPM. >> >> Regards, >> >> Peter >> >
