Re: [M100] REX# Version 2 software update.

[Stephen Adolph]

Folks,
A bug was found in REXCPM Version 2, that also affects REX# Version 2.

I have a fix in hand, so I will be posting an update later tonight or
tomorrow.

Summary of the bug:
* when copying a RAM image to system memory from REX#, you cannot start
BASIC or TEXT.
* work around is to press RESET and carry on.

issue resolved in build 13.

Steve

On Thu, Jan 7, 2021 at 9:47 PM Stephen Adolph  wrote:

> Many delays for this, sorry to those who've been waiting for me to get
> this done.
>
> I have posted an update to REX# at the Bitchin100 Wiki.
> Version 2 provides
> * integrated VT100 video driver (for M100/T102)
> * multi-bank (for T200 and NEC)
> * new quick menu key stroke CNTL-A to start REXMGR
> not to mention a major bug fix.
>
> Due to the *major bug* I do suggest people do the upgrade, but also I
> suggest saving off to external storage any important RAM images or other
> data!
>
> Information is posted here:
>
>
> http://bitchin100.com/wiki/index.php?title=REXsharp#Use_with_MVT100_external_Video
>
> http://bitchin100.com/wiki/index.php?title=Integrated_VT100_driver
>
> Thanks to COVID lockdown, I have been able to invest a lot of time in
> development and testing.
> I have really put in some time and I hope that upgrades go smoothly.
>
> I have created new tools that I hope are more user friendly.
>
> For those of you with REX#, just download the REX# upgrade utility, and
> the new software image.  Both are posted at the link above.
>
> My utilities are now are ASCII .DO files, and 7bit, so they can be loaded
> correctly more easily and reliably.  No need to transfer as a .CO, with
> some of the hassle that entails.
>
> I do rely on feedback when things don't work because I really can't
> possibly test everything!  So, thanks in advance for your feedback.
>
> Lastly, I will be posting the similar update for REXCPM.  So Version 2
> REXCPM software with integrated VT100 is on it's way.
>
> thanks,
> Steve
>
>
>

Re: [M100] REXCPM Upgrade to version 2 available

[Stephen Adolph]

early reports of trouble; i must have missed something.
I'll take it down until I have found the problem...

On Fri, Jan 15, 2021 at 6:03 PM Stephen Adolph  wrote:

> The next version of REXCPM is now available for download.
>
> http://bitchin100.com/wiki/index.php?title=REXCPM#Software
>
> Version 2 provides the integrated VT100 driver, and adds in the CNTL-A
> quickmenu shortcut to start RXCMGR.
>
> I have run through the upgrade process on my machines, from Version 1
> build 43 to Version 2 build 10.  Worked for me, and worked in VirtualT.
>
> Please read the instructions carefully, and download the software and
> utilities bundle.
> Delete your old utilities and use the new ones.
> To do a fresh install (as in you have never installed it before) then use
> RXCINI.DO.
> To UPGRADE an existing V1 install, please use RXCUPG.DO.
>
> Let me know if there any problems, and of course bug reports are valuable.
>
> Also, I have updated the BCR hack page with information on how to apply
> the hack to T102.
>
> http://bitchin100.com/wiki/index.php?title=BCR_TTL_SERIAL_HACK#T102
>
> thanks
> Steve
>
>
>

Re: [M100] REXCPM Upgrade to version 2 available

[Stephen Adolph]

Sorry Jim.  Ok I guess something is broken that I didnt see.

I will investigate.

Fyi I attempted the directory structure with rex# so that the same sort
routines would be used!


On Saturday, January 16, 2021, Jim Anderson  wrote:

> I tried upgrading to this new release (using RXCUPG), and encountered
> issues when restoring a RAM image back from backup.  The same thing happens
> sometimes when switching from one RAM image to another, but every time when
> restoring from an image (either through Ctrl-R or through RXCMGR).  The
> progress bar indicates data is being copied to RAM, but then the M100 locks
> up, sometimes showing a screen like the photo below, and sometimes just a
> frozen screen.  Sometimes Reset or a power-cycle will recover the machine,
> sometimes it needs a cold reset.
>
>
>
> I also tried using RXCINI (the new one from REXCPMV2_b11.ZIP) to create a
> new directory and load REX from scratch, and the same issue is present.  In
> addition, there are more strange behaviours – when starting from an empty
> directory I can create a new RAM backup, but if I try to create another RAM
> backup or switch to a RAM image I’ve loaded back from TPDD, RXCMGR just
> creates a new RAM image with the same name as the current one.  If I try to
> delete the non-active image I get a message which I thought I had committed
> firmly to memory (sorry) – it said something about ‘error: flash not
> available’ or not ready or something to that effect.
>
>
>
> On the upside, my RAM image was actually being sorted correctly by date
> and time.  :)  I’ve restored my backup and running v1 build 43 again as it
> was essentially unusable the way things were.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> jim
>
>
>
> *From:* M100 [mailto:m100-boun...@lists.bitchin100.com] *On Behalf Of *Stephen
> Adolph
> *Sent:* Friday, January 15, 2021 17:02
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] REXCPM Upgrade to version 2 available
>
>
>
> *CAUTION External Sender:* Do not click links or open attachments unless
> you recognize the sender and know the content is safe.
>
>
>
> I found a minor issue just now;
>
> When switching from M100 to CP/M, it is possible that the M100 leaves the
> SCREEN in the scroll lock state.
>
>
>
> Here is a simple basic program that de-scroll locks the screen and starts
> CPM.
>
> It assumes RXCMGR is installed.
>
>
>
>
>
> CPM.BA
> 
>
>
>
> 10 screen0:cls:print"Enabling scroll..."
>
> 20 screen2:printchr$(27);"W";
>
> 30 screen0:print"starting CP/M."
>
> 40 call32804,3
>
>
>
>
>
> it is  a work around until i drop a new load with a fix.
>
> cheers
>
> Steve
>
>
>
>
>
>
>
> On Fri, Jan 15, 2021 at 6:03 PM Stephen Adolph 
> wrote:
>
> The next version of REXCPM is now available for download.
>
>
>
> http://bitchin100.com/wiki/index.php?title=REXCPM#Software
> 
>
>
>
> Version 2 provides the integrated VT100 driver, and adds in the CNTL-A
> quickmenu shortcut to start RXCMGR.
>
>
>
> I have run through the upgrade process on my machines, from Version 1
> build 43 to Version 2 build 10.  Worked for me, and worked in VirtualT.
>
>
>
> Please read the instructions carefully, and download the software and
> utilities bundle.
>
> Delete your old utilities and use the new ones.
>
> To do a fresh install (as in you have never installed it before) then use
> RXCINI.DO.
>
> To UPGRADE an existing V1 install, please use RXCUPG.DO.
>
>
>
> Let me know if there any problems, and of course bug reports are valuable.
>
>
>
> Also, I have updated the BCR hack page with information on how to apply
> the hack to T102.
>
>
>
> http://bitchin100.com/wiki/index.php?title=BCR_TTL_SERIAL_HACK#T102
> 
>
>
>
> thanks
>
> Steve
>
>
>
>
>
>

Re: [M100] REXCPM Upgrade to version 2 available

[Jim Anderson]

I tried upgrading to this new release (using RXCUPG), and encountered issues 
when restoring a RAM image back from backup.  The same thing happens sometimes 
when switching from one RAM image to another, but every time when restoring 
from an image (either through Ctrl-R or through RXCMGR).  The progress bar 
indicates data is being copied to RAM, but then the M100 locks up, sometimes 
showing a screen like the photo below, and sometimes just a frozen screen.  
Sometimes Reset or a power-cycle will recover the machine, sometimes it needs a 
cold reset.

I also tried using RXCINI (the new one from REXCPMV2_b11.ZIP) to create a new 
directory and load REX from scratch, and the same issue is present.  In 
addition, there are more strange behaviours - when starting from an empty 
directory I can create a new RAM backup, but if I try to create another RAM 
backup or switch to a RAM image I've loaded back from TPDD, RXCMGR just creates 
a new RAM image with the same name as the current one.  If I try to delete the 
non-active image I get a message which I thought I had committed firmly to 
memory (sorry) - it said something about 'error: flash not available' or not 
ready or something to that effect.

On the upside, my RAM image was actually being sorted correctly by date and 
time.  :)  I've restored my backup and running v1 build 43 again as it was 
essentially unusable the way things were.

[cid:image001.jpg@01D6EBA8.70354260]







jim

From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Stephen 
Adolph
Sent: Friday, January 15, 2021 17:02
To: m...@bitchin100.com
Subject: Re: [M100] REXCPM Upgrade to version 2 available

CAUTION External Sender: Do not click links or open attachments unless you 
recognize the sender and know the content is safe.

I found a minor issue just now;
When switching from M100 to CP/M, it is possible that the M100 leaves the 
SCREEN in the scroll lock state.

Here is a simple basic program that de-scroll locks the screen and starts CPM.
It assumes RXCMGR is installed.


CPM.BA

10 screen0:cls:print"Enabling scroll..."
20 screen2:printchr$(27);"W";
30 screen0:print"starting CP/M."
40 call32804,3


it is  a work around until i drop a new load with a fix.
cheers
Steve



On Fri, Jan 15, 2021 at 6:03 PM Stephen Adolph 
mailto:twospru...@gmail.com>> wrote:
The next version of REXCPM is now available for download.

http://bitchin100.com/wiki/index.php?title=REXCPM#Software

Version 2 provides the integrated VT100 driver, and adds in the CNTL-A 
quickmenu shortcut to start RXCMGR.

I have run through the upgrade process on my machines, from Version 1 build 43 
to Version 2 build 10.  Worked for me, and worked in VirtualT.

Please read the instructions carefully, and download the software and utilities 
bundle.
Delete your old utilities and use the new ones.
To do a fresh install (as in you have never installed it before) then use 
RXCINI.DO.
To UPGRADE an existing V1 install, please use RXCUPG.DO.

Let me know if there any problems, and of course bug reports are valuable.

Also, I have updated the BCR hack page with information on how to apply the 
hack to T102.

http://bitchin100.com/wiki/index.php?title=BCR_TTL_SERIAL_HACK#T102

thanks
Steve