On 4/4/20 8:20 AM, Stephen Adolph wrote:
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.
Thank you much.
I have applied this update to a couple 100s, 200, and 8201, with no
problem so far. I haven't done any real testing other than running the
installer and verifying that the CS=#### number (checksum?) on the info
screen changed between before & after.
Along the way I discovered that my current version of dlplus is broken
for normal tpdd usage with ts-dos. Probably the same mystery commands
that have been mentioned recently. I was dinking around with that a
while ago. The bootstrap works and tpdd works with teeny. So I have
something to do for a while now locked up indoors.
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 <[email protected]
<mailto:[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
--
bkw
