At first I thought it was related to the larger size of RXCMGR, but then I saw
I was having issues in images where there were several kb available, and then I
did the exercise where it ate like 13+kb of memory in an empty filesystem...
jim
From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Stephen
Adolph
Sent: Tuesday, January 26, 2021 04:14
To: m...@bitchin100.com
Subject: Re: [M100] updates to REX# Version 2, REXCPM Version 2
CAUTION External Sender: Do not click links or open attachments unless you
recognize the sender and know the content is safe.
RXCMGR is now >1kb
I'll look into it, but, the VT100 driver exists in RAM now. Is that the
problem?
I could not find a way to place the VT100 driver in option ROM. too
challenging to understand how to make it work.
On Tue, Jan 26, 2021 at 4:54 AM Jim Anderson
<jim.ander...@kpu.ca<mailto:jim.ander...@kpu.ca>> wrote:
> -----Original Message-----
> From: M100
> [mailto:m100-boun...@lists.bitchin100.com<mailto:m100-boun...@lists.bitchin100.com>]
> On Behalf Of
> Stephen Adolph
> Sent: Sunday, January 24, 2021 18:49
> To: m...@bitchin100.com<mailto:m...@bitchin100.com>
> Subject: Re: [M100] updates to REX# Version 2, REXCPM Version 2
>
> CAUTION External Sender: Do not click links or open attachments unless
> you recognize the sender and know the content is safe.
>
> Glad to hear Jim. Thanks! And thanks for your patience.
There is one thing. Since the upgrade I've been having some weirdness with
Ultimate Rom II not behaving itself (refusing to open T-Base files, etc).
I thought it might have been some residual RAM image corruption left over from
before that was fixed (I keep thinking I had checked or re-created all my RAM
images since then, but always have a nagging feeling that I haven't...)
The most easily checked misbehaviour is that if I try to launch UR-2 where
there are only a few kb of space left, I can't exit with F8 - it beeps and
briefly flashes the word "Can't". Have to use Reset to get out of it.
I won't bore you with all the things I tried, except the last: I thought I will
re-create this RAM image from scratch where I have T-Base files with my gas
receipts and my video collection. Cold reset, check that I can run UR-2, then
fire up TS-DOS to copy the T-Base files into RAM. I run out of space. This
all fit before...
Cold reset again, check the free space, it's normal. Fire up UR-2, exit. Free
space has suddenly been cut by nearly half, it's now only 16350 bytes. The
only things created in the RAM filesystem are CONFIG.DO which is the usual size
and the UR-2 file to launch the ROM. If I kill those, free space goes up a
little bit but not back to normal.
I could make a backup, re-init my REXCPM back to v1 build 43 and try this to
verify if you want, but I'm pretty sure it didn't do this before (although I
can't swear to it, I just don't remember having problems with UR-2 before). As
a check I cold reset another machine with REX Classic and went into UR-2 and as
expected, the free space has only gone down by the size of CONFIG.DO plus a few
bytes for the UR-2 launch file.
jim
