Thanks Steve, It will take me some time to try it out. I have never re-flashed the REX before, so I will need to note what files are in each image (the masters are on my PC), then study the re-flash procedure and execute it, then re-load all the files.
Hopefully nothing will break and cause my REX to become a doorstop. I expect that you do not have an SQA (Software Quality Assurance) Test Suite, so hopefully the fix doesn't break anything else. While we are on the "bug fix" topic, I also found another one the other day. I was using the REXMGR to rename a file in RAM. Once the rename was successful, the label menu was not re-displayed. I think this also occurs when killing a file, but I am not sure. Regards, Peter -------------- > > Message: 1 > Date: Sat, 4 Apr 2020 08:20:04 -0400 > From: Stephen Adolph <twospru...@gmail.com> > To: m...@bitchin100.com > Subject: Re: [M100] REX problem with .DO files > Message-ID: > < > camcmnv5abvuwonucxftb+ixcmh_vhjzpm9wxvaqqk0gcwrw...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Peter, thanks for finding this bug. It's been in the code for a long time! > Found the issue. Injection point for a new .DO file was off by 1 byte. > Release 258 should fix this. > > It is posted at the REX wiki. > > Would appreciate people to go and give 258 a try. It should be the same as > 254, which was the prior posted release, with this bug fix added. > > I will say that I have not tested every model with every possible > configuration. So any bug reports would be useful. > > thanks > Steve > > > On Mon, Mar 23, 2020 at 1:33 AM Peter Noeth <petern0...@gmail.com> 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 > > > <snip> > >
