Re: [M100] R2.2 update for REX# and REXCPM

2023-02-04 Thread Stephen Adolph
hello, just an FYI, I have RAM Write Protect implemented now in REX# 2.2. Seems to work well, will be testing it out. * in RAM tab in REXMGR, "W" toggles the write protect status of a RAM image * write protect ON is indicated by "!" ex. "RAMIMG !" would indicate this image is write protect * any

Re: [M100] R2.2 update for REX# and REXCPM

2023-01-31 Thread MikeS
already gotten used to the DATE$ format. m - Original Message - From: To: Sent: Tuesday, January 31, 2023 10:35 AM Subject: Re: [M100] R2.2 update for REX# and REXCPM I agree with Brian, consistency with the system that can't be changed is probably the best. At least

Re: [M100] R2.2 update for REX# and REXCPM

2023-01-31 Thread jonathan.y...@telia.com
gt;To : m100@lists.bitchin100.com >Subject : Re: [M100] R2.2 update for REX# and REXCPM > >Cosistency with the rest of the system which can't be changed is >definitely a legit point. Thanks for clarifying. > >-- >bkw > >On 1/31/23 03:03, Cedric Amand wrote: >> As I'm

Re: [M100] R2.2 update for REX# and REXCPM

2023-01-31 Thread Brian K. White
Cosistency with the rest of the system which can't be changed is definitely a legit point. Thanks for clarifying. -- bkw On 1/31/23 03:03, Cedric Amand wrote: As I'm the one who started the date debate :) let me clarify what my feedback to Steve was In the context of my M200, there are

Re: [M100] R2.2 update for REX# and REXCPM

2023-01-31 Thread Cedric Amand
As I'm the one who started the date debate :) let me clarify what my feedback to Steve was In the context of my M200, there are multiple things that are confusing with dates, First of I consider that the system time, the one reported by print DATE$ , should define the date format, otherwise you

Re: [M100] R2.2 update for REX# and REXCPM

2023-01-30 Thread jonathan.y...@telia.com
: 2023-01-31 - 02:26 (CEST) >To : m100@lists.bitchin100.com >Subject : Re: [M100] R2.2 update for REX# and REXCPM > >That is a great set of updates. >Personally I prefer year-first dates so don't assume the illogical way >was was a universal preference ;) > >But it's a sm

Re: [M100] R2.2 update for REX# and REXCPM

2023-01-30 Thread Stephen Adolph
> > > Yah, that is the issue. I did that recently too! Well the change now is that you have to choose to refresh the backup. If > not, you skip the write into the active ram , before you select and load up > a different image. There was no way directly to load up a saved ram image that was not

Re: [M100] R2.2 update for REX# and REXCPM

2023-01-30 Thread Josh Malone
On Mon, Jan 30, 2023 at 9:03 PM Stephen Adolph wrote: > Brian, > Great suggestion on read only. That's a cool idea. > This feature would make me throw out all my Classics immediately and replace them with #s. I can't tell how many times I've booted a blank M100, gone to restore a RAM image,

Re: [M100] R2.2 update for REX# and REXCPM

2023-01-30 Thread Stephen Adolph
> > > Brian, Great suggestion on read only. That's a cool idea. I'm actually daydreaming about something a step further, too. Thinking about a way to be able to save files directly into an image. Getting away from the ram image concept would allow that. To keep a ram image intact, it is

Re: [M100] R2.2 update for REX# and REXCPM

2023-01-30 Thread Brian K. White
That is a great set of updates. Personally I prefer year-first dates so don't assume the illogical way was was a universal preference ;) But it's a small thing that I also don't think it's worth making configurable. I would have told anyone who cared enough to ask for it to be changed, to

[M100] R2.2 update for REX# and REXCPM

2023-01-30 Thread Stephen Adolph
I'm most of the way through testing a bug fix release for REX# and REXCPM. Current load is R2.1 build 19. New load is R2.2. Here's the list of changes (see below). I'll post the upgrade files to the wiki when I am happy it is all looking good! cheers Steve Bugs Rel 2.1: All: Fix the date