.
Jonathan
jonathan.y...@mykopat.slu.se
Från: M100 [m100-boun...@lists.bitchin100.com] för Tom Hoppe [tjho...@gmail.com]
Skickat: den 2 december 2020 23:07
Till: m...@bitchin100.com
Ämne: Re: [M100] REXCPM update
I figured it out, to a point. I was using mComm to
Also, just a comment, for the sake of those on the list,
If you ran RXCTST, your REXCPM is now completely blank. I hope that comes
as no surprise!\No Directory, no ROMs, no REXMGR. So, you really have
to re-run RXCINI.DO to re install RXCMGR from scratch, and then re-install
TS-DOS.
cheers
S
remember, the reason for the upgrade is the fairly damaging bug discovered
with REXCPM, which corrupts the file system. So, not surprising things
could be messed up. A cold restart WITH A POWER CYCLE is necessary to make
sure REXCPM starts up in default state and has freshly cleaned out RAM.
I've
Tom ,please contact me off list to debug. It will get too involved to have
on list, ok? thanks.
On Wed, Dec 2, 2020 at 5:07 PM Tom Hoppe wrote:
> I figured it out, to a point. I was using mComm to inject TS-DOS via
> RUN"COM:98N1E" but after it loads I can no longer CLEAR 1000,62000 (even if
I figured it out, to a point. I was using mComm to inject TS-DOS via
RUN"COM:98N1E" but after it loads I can no longer CLEAR 1000,62000 (even if
I delete TS-DOS.BA). However, I *now* know that the CLEAR command works
fine from a clean M100 (as it should), and I determined that loading it via
TEENY
Makes no sense. I would cold boot.
The ram file system gets damaged by the current version of RXCMGR. So it
makes sense to clean house anyways.
On Monday, November 30, 2020, Tom Hoppe wrote:
> Hmm. Getting this error when I try to run RXCUTL.BA for the update on an
> clean/empty M100:
>
> ?F
Hmm. Getting this error when I try to run RXCUTL.BA for the update on an
clean/empty M100:
?FC Error in 10
Ok
If I run CLEAR 1000,62000 manually by itself I get the same error. I can
omit this CLEAR statement in line 10 and it seems to install fine but then
I have instability issues later.
Tom
Thanks Steve!
rcs
On Sun, Nov 29, 2020 at 9:33 AM Stephen Adolph wrote:
> http://bitchin100.com/wiki/index.php?title=REXCPM#Backup_and_Restore
>
> Update RXCMGR ROM build 43 and utilities V2 are posted at the above link,
> with minor updates to the page.
>
> Build 43 includes
> * bug fix: M100
s?
>
> David
>
> Sent from Mail[https://go.microsoft.com/fwlink/?LinkId=550986] for Windows 10
>
> From: Greg Swallow[gswal...@mchsi.com]
> Sent: Sunday, November 29, 2020 10:51 AM
> To: m...@bitchin100.com
> Subject: Re: [M100] REXCPM update
>
> Steve,
>
&g
, November 29, 2020 10:51 AM
To: m...@bitchin100.com
Subject: Re: [M100] REXCPM update
Steve,
Very cool. Thanks.
One question. When I first loaded/configured REXCPM, I did so using an ol’
Windows 7 HP computer. I have since gone all macOS; Catalina. I have gotten
mComm working,— though I seem to
Steve,
Very cool. Thanks.
One question. When I first loaded/configured REXCPM, I did so using an ol’
Windows 7 HP computer. I have since gone all macOS; Catalina. I have gotten
mComm working,— though I seem to have lost the command line to start it up, I
wonder what ASCII terminal program thos
http://bitchin100.com/wiki/index.php?title=REXCPM#Backup_and_Restore
Update RXCMGR ROM build 43 and utilities V2 are posted at the above link,
with minor updates to the page.
Build 43 includes
* bug fix: M100 directory corruption occurs on exit from CP/M. This is
repaired now.
* Date/Time/Sort
> -Original Message-
>
> Tonight I'll try it the way you specify in the note, and also (if I'm
> feeling brave) try a wipe and restore.
CTRL-X followed by power cycle works.
Wipe and restore of both the REXCPM area and the CPM area works like a charm
(eventually :) ).
jim
> -Original Message-
>
> Jim, did you get this working? ..Steve
> [...]
> Here is the exact note:
>
> "Make sure REXCPM is in default state, meaning RXCMGR is not running
> (use CNTL-X to remove hooks) and power cycle once."
Sorry, I missed the power-cycle part of the instructions. I wa
Jim, did you get this working? ..Steve
On Wed, Jun 24, 2020 at 8:05 PM Stephen Adolph wrote:
> Here is the exact note:
>
>
> "Make sure REXCPM is in default state, meaning RXCMGR is not running (use
> CNTL-X to remove hooks) and power cycle once."
>
>
> On Wed, Jun 24, 2020 at 7:57 PM Jim Ander
Here is the exact note:
"Make sure REXCPM is in default state, meaning RXCMGR is not running
(use CNTL-X to remove hooks) and power cycle once."
On Wed, Jun 24, 2020 at 7:57 PM Jim Anderson wrote:
> > -Original Message-
> >
> > Comments:
> > 1) to run the backup utility, RXCMGR must b
> -Original Message-
>
> Comments:
> 1) to run the backup utility, RXCMGR must be disabled. CNTL-X. think I
> stated this at the wiki?
I tried again after removing the hooks and get the same results.
Do I need to be in an empty memory image (ie. with RXCUTL.DO being the only
file in t
I did not have that note in the wiki! I will add it now. cheers-
On Wed, Jun 24, 2020 at 7:21 PM Stephen Adolph wrote:
> Great to hear!
>
> Comments:
> 1) to run the backup utility, RXCMGR must be disabled. CNTL-X. think I
> stated this at the wiki?
>
>
Great to hear!
Comments:
1) to run the backup utility, RXCMGR must be disabled. CNTL-X. think I
stated this at the wiki?
2) And yes, I've dropped some features that either added little value or
added greatly to the testing burden. Date and sort were on the chopping
block. bad call?
Steve
On
Got mine today! Loaded in some OPTROMS and one of my old RAM backup images
from my REX Classic, and they work great! (Not sure if you want to test that
yourself before updating the wiki, Stephen.) Only hitch (mostly cosmetic) is
that there is still a REXMGR entry on the menu screen left over
Thanks Steve, looking forward to getting mine. :-)
Cheers,Bert
On 6/16/20 9:11 PM, Stephen Adolph wrote:
> I am well into the 2nd build of REXCPM. All of the REXCPM modules are
> built, untested, but I still need to build the adapters.
> So good progress. I'm aiming to ship the next tranch
👍🏻👍🏻
David, WA7ZYQ
C’est la vie, c’est la guerre, viva la salade de pommes de terre.
> On Jun 16, 2020, at 7:11 PM, Stephen Adolph wrote:
>
> I am well into the 2nd build of REXCPM. All of the REXCPM modules are built,
> untested, but I still need to build the adapters.
> So good progress.
I am well into the 2nd build of REXCPM. All of the REXCPM modules are
built, untested, but I still need to build the adapters.
So good progress. I'm aiming to ship the next tranch in 2 weeks or sooner.
Steve
SIC or ML in native M100 mode.
>
> - Original Message -
> *From:* Mike Stein
> *To:* m...@bitchin100.com
> *Sent:* Saturday, June 13, 2020 10:33 PM
> *Subject:* Re: [M100] REXCPM update
>
> Is the 2/4MB RAM accessible to the M100, perhaps as individually
> address
Is the 2/4MB RAM accessible to the M100, perhaps as individually addressable 32
KB pages in the OptROM address space?
m
- Original Message -
From: Stephen Adolph
To: m...@bitchin100.com
Sent: Wednesday, June 10, 2020 10:27 PM
Subject: Re: [M100] REXCPM update
Looks like
Well, I don't yet have installation instructions posted for T102, but may
as well go ahead. I'll post photos shortly.
On Wed, Jun 10, 2020 at 10:30 PM wrote:
> Steve,
>
> I didn't think from your first post the REXCPM would work with the 102. If
> it just takes a single wire, please put me down
Steve,
I didn't think from your first post the REXCPM would work with the 102. If
it just takes a single wire, please put me down for one unit.
Thank you
Keith
On Wed, Jun 10, 2020 at 8:49 PM Stephen Adolph wrote:
> Thank you everyone for the interest!
>
> I have indications for about 2x what
Looks like a new FAQ item!
You literally get an M100 with REX and a separate CP/M system to use.
You can switch between the 2.
..steve
On Wednesday, June 10, 2020, Josh Malone wrote:
> On Wed, Jun 10, 2020 at 8:49 PM Stephen Adolph
> wrote:
>
>> Thank you everyone for the interest!
>
>
> Th
On Wed, Jun 10, 2020 at 8:49 PM Stephen Adolph wrote:
> Thank you everyone for the interest!
Thank you and others on the project for making this amazing advance in
Model-T technology!
> I have indications for about 2x what I have on hand, but I have parts here
> to build to meet the need. No
HI Steve,
Absolutely wonderful - Thanks for making these, they really help the
community
Kindest regards,
Doug Jackson
em: d...@doughq.com
ph: 0414 986878
Check out my awesome clocks at www.dougswordclocks.com
Follow my amateur radio adventures at vk1zdj.net
--
Thank you everyone for the interest!
I have indications for about 2x what I have on hand, but I have parts here
to build to meet the need. Nothing to order and wait for...
For now I am putting down my Z80 conversion toy, and putting down my coding
projects to focus on shipping and building for a
Sent: Thursday, November 23, 2017 16:47
To: m...@bitchin100.com
Subject: Re: [M100] REXCPM update.
sorry... I checked the layout. TSSOP! doh.just goes to prove... need to
state package.
On Thu, Nov 23, 2017 at 7:38 PM, Stephen Adolph
mailto:twospru...@gmail.com>> wrote:
https://www.e
Silly question: what's the difference?
- Original Message -
From: Stephen Adolph
To: m...@bitchin100.com
Sent: Thursday, November 23, 2017 7:46 PM
Subject: Re: [M100] REXCPM update.
sorry... I checked the layout. TSSOP! doh.just goes to prove... need to
sorry... I checked the layout. TSSOP! doh.just goes to prove... need
to state package.
On Thu, Nov 23, 2017 at 7:38 PM, Stephen Adolph
wrote:
> https://www.ebay.ca/itm/5-pcs-New-SN74LVC4245APWR-LJ245A-
> SSOP-24-IC-Chip/232528836254?hash=item3623cc769e:g:ioMAAOSwtYxZggSv
>
> SSOP ... this
https://www.ebay.ca/itm/5-pcs-New-SN74LVC4245APWR-LJ245A-SSOP-24-IC-Chip/232528836254?hash=item3623cc769e:g:ioMAAOSwtYxZggSv
SSOP ... this is the part here.
On Thu, Nov 23, 2017 at 7:36 PM, Stephen Adolph
wrote:
> the 4245 is an SOP or SOIC. you are correct I need to specify that. not
> super
the 4245 is an SOP or SOIC. you are correct I need to specify that. not
super tiny but just tiny.
the CPLD is the same, but with different firmware.
I will post a verified BOM including packages
On Thu, Nov 23, 2017 at 7:13 PM, Jim Anderson wrote:
> > -Original Message-
> >
> >
> -Original Message-
>
> BOM:
Question about the SN74LVC4245 - is that an SSOP or TSSOP package?
Also, is the CPLD the same chip as used on the original REX a bunch of us have
been building, or is this one different?
jim
https://www.ebay.com/itm/CY62167DV30LL-55ZXI-16Mbit-1Mx16-Static-RAM-55ns-TSOP48/271833602209?hash=item3f4a8b98a1:g:I3QAAOSwEyhZ3e6x
interestingly here is a fairly affordable 2MB SRAM - CY62167 - that I would
think is compatible with this design.
7$+ shipping.
On Thu, Nov 23, 2017 at 7:50 AM, St
BOM:
XCR3064XL-10VQ44
TC55VBM416AFTN
(2) SN74LVC4245
LP2980-3.3
TPS78233
BAV70
(2) 10k 0805
(2) 1uF 0805
[image: Inline image 2][image: Inline image 1]
On Thu, Nov 23, 2017 at 7:44 AM, Stephen Adolph
wrote:
> Mike, I have not really thought about it. I just submitted a V2 board
> that cleans
Mike, I have not really thought about it. I just submitted a V2 board that
cleans up the barnacles needed on V1, and once that is confirmed good in
about 3 weeks, I was thinking just to post all the info so it can be built
by anyone, like REX.
The BOM cost is quite a bit higher. The CPLD is 5$ a
Sounds great!
Any rough idea of a price point?
m
- Original Message -
From: Stephen Adolph
To: m...@bitchin100.com
Sent: Wednesday, November 22, 2017 4:48 PM
Subject: Re: [M100] REXCPM update.
for fun I tested it with the EME systems software called COMROM - for loading
On Wed, Nov 22, 2017 at 5:48 PM Philip Avery wrote:
> Thanks John, I got it working. I just check for EOF (3F) from Return
> Command. I imported Zork1.dat, that's 83KB. Zork1 boots up - yay.
>
>
> Philip
>
Ok. I’m pretty sure file enumeration also can have larger than 16 bit file
sizes. I just
Thanks John, I got it working. I just check for EOF (3F) from Return
Command. I imported Zork1.dat, that's 83KB. Zork1 boots up - yay.
Philip
On 23/11/2017 1:22 PM, John R. Hogerhuis wrote:
You can put two more bytes somewhere else in the packet, is my
recollection.
You could take a look at
You can put two more bytes somewhere else in the packet, is my
recollection.
You could take a look at LaddieAlpha source.
— John.
On Wed, Nov 22, 2017 at 4:20 PM Philip Avery wrote:
> Well, the doc
> http://bitchin100.com/wiki/index.php?title=TPDD_Base_Protocol says so
> and the Directory size
Well, the doc
http://bitchin100.com/wiki/index.php?title=TPDD_Base_Protocol says so
and the Directory size field is 2-bytes, but... I think you're right as
I've read past 64KB to an apparent end of file. I've just got to study
the Return Command details more closely. Working on it.
Philip
On
I don’t think there’s a 64k file size limit.
— John.
Marvellous. Will make a great Christmas present for me :-)
I'm still at it on the CP/M software front, currently overcoming TPDD's
64KB file size...
Philip
On 23/11/2017 10:00 AM, Stephen Adolph wrote:
Just a short note to say I have finished verification of my REXCPM
board. It provides up
for fun I tested it with the EME systems software called COMROM - for
loading binary images into EXTRAM. Worked perfectly, I was able to load
and run TS-DOS into bank 0.
In many ways REXCPM based on SRAM is better than REX based on flash. It
does everything REX does, but it can also support file
#include
On Wed, Nov 22, 2017 at 4:11 PM, Lee Kelley wrote:
> Very exciting.
>
> On Wed, Nov 22, 2017 at 3:09 PM, Tom Hoppe wrote:
>>
>> This is very cool!
>>
>> On Wed, Nov 22, 2017 at 1:00 PM, Stephen Adolph
>> wrote:
>>>
>>> Just a short note to say I have finished verification of my REXCPM
Very exciting.
On Wed, Nov 22, 2017 at 3:09 PM, Tom Hoppe wrote:
> This is very cool!
>
> On Wed, Nov 22, 2017 at 1:00 PM, Stephen Adolph
> wrote:
>
>> Just a short note to say I have finished verification of my REXCPM
>> board. It provides up to 2MB of battery backed up SRAM in the OPTROM
>>
This is very cool!
On Wed, Nov 22, 2017 at 1:00 PM, Stephen Adolph
wrote:
> Just a short note to say I have finished verification of my REXCPM board.
> It provides up to 2MB of battery backed up SRAM in the OPTROM socket, and
> it is good for providing the needed full 64KB of SRAM for CP/M opera
Just a short note to say I have finished verification of my REXCPM board.
It provides up to 2MB of battery backed up SRAM in the OPTROM socket, and
it is good for providing the needed full 64KB of SRAM for CP/M operation,
plus provides ample space for RAM based disks.
It needs only 2 wires - one co
52 matches
Mail list logo