Re: [M100] REX#/REXCPM release 2.2 is on the wiki

Hi Pawel, I included a note in the instructions. 'x' is a variable: 1,2 or N - depending on your model hope that addresses the concern. Thanks Steve On Sunday, November 5, 2023, Pawel Radomychelski | ExPLIT < exp...@mailbox.org> wrote: > Hello Steve! > > Thank you for the bugfix relese of

Re: [M100] REX#/REXCPM release 2.2 is on the wiki

Hello Steve! Thank you for the bugfix relese of REX# 22 Upde went with one small issue: When i use your Instructions here: Instructions 1. Make sure REX# is in default state, meaning a. REX# Manager is not running (use CNTL-X to remove hooks, or F7 from REXMGR)

Re: [M100] Rex# Crash on an M102

Thanks for the updates! I tried the following: 1. Flash REX# firmware via TPDD, which appeared to work but then exhibited the same behavior of trying to load some ghost image on start and then crashing 2. Flash REX# with the test.do, which I realize would lose the flash images but I've got

Re: [M100] Rex# Crash on an M102

First thing verify the connection to all the pins in the socket. It's a common weak point. No weak/compressed pins, no oxidization, rex# fully seated etc. Otherwise what Steve said, run the install/update tool to reflash the Rex#. -- bkw On 5/25/23 21:27, Charlie Hoey wrote: Hello there! I

Re: [M100] Rex# Crash on an M102

Charlie, Hard to say what's wrong. In an ideal situation, I'd like to get it back and root cause the problem. So, yoo could send it back and I send you a replacement. Short of that, a rebuild would be what is needed. Release 2.1 to do a rebuild are posted on the wiki, along with instructions.

Re: [M100] REX# - RAM Images

On Wed, Feb 22, 2023, 1:54 PM Joseph Colson III wrote: > John - I have been reading up on tback.exe. It would appear that you can > backup a ram state on Virtual-T and load the backup onto a Model 100 ? How > is this done ? > > > If you're asking what file in virtual t... it's just a file on

Re: [M100] REX# - RAM Images

p onto a Model 100 ? How > is this done ? > > > > > > Thanks for your hard work. > > > > Joe > > > > *From:* M100 *On Behalf Of *John R. > Hogerhuis > *Sent:* Wednesday, February 22, 2023 12:53 PM > *To:* m...@bitchin100.com > *Subject:* Re:

Re: [M100] REX# - RAM Images

...@bitchin100.com Subject: Re: [M100] REX# - RAM Images I don't have any handy but RAM images can be useful for saving configurations of multiple files especially with large ML programs that are difficult to load, like TMPC. And even without a REX, because you can use TBACK.EXE to save or load

Re: [M100] REX# - RAM Images

I don't have any handy but RAM images can be useful for saving configurations of multiple files especially with large ML programs that are difficult to load, like TMPC. And even without a REX, because you can use TBACK.EXE to save or load a RAM image. -- John.

Re: [M100] Rex#..TPDD compatibility

Jeff Birt > > > > *From:* bir...@soigeneris.com > *Sent:* Saturday, January 14, 2023 1:30 PM > *To:* 'm...@bitchin100.com' > *Subject:* RE: [M100] Rex#..TPDD compatibility > > > > For the Backpack, when you save a file the Backpack needs to check to see > if the fil

Re: [M100] Rex#..TPDD compatibility

that TS-DOS provides. The user may not wish to overwrite a previous backup, and this will give them a warning that they are about to do so. Jeff Birt From: bir...@soigeneris.com Sent: Saturday, January 14, 2023 1:30 PM To: 'm...@bitchin100.com' Subject: RE: [M100] Rex#..TPDD compatibility

Re: [M100] Rex#..TPDD compatibility

Subject: Re: [M100] Rex#..TPDD compatibility Here is the current status of REX# (and REXCPM) interworking. Better than I thought! Dosbox is set up to run pretty slow, but my set up runs Desklink well on Windows 10, and also runs PDD.EXE, which is great. Backpack works for general

Re: [M100] Rex#..TPDD compatibility

added DLPilot to the list: [image: image.png] On Sat, Jan 14, 2023 at 11:09 AM Stephen Adolph wrote: > not yet but that is the plan > > On Sat, Jan 14, 2023 at 10:35 AM Cedric Amand wrote: > >> I wish to add that the patched version you sent me (with enlarged delays) >> worked on my TPDD1 >>

Re: [M100] Rex#..TPDD compatibility

not yet but that is the plan On Sat, Jan 14, 2023 at 10:35 AM Cedric Amand wrote: > I wish to add that the patched version you sent me (with enlarged delays) > worked on my TPDD1 > Was this never merged with the "main" software ? > > > Le 2023-01-14 16:30, Stephen Adolph a écrit : > > Here is

Re: [M100] Rex#..TPDD compatibility

I wish to add that the patched version you sent me (with enlarged delays) worked on my TPDD1 Was this never merged with the "main" software ? Le 2023-01-14 16:30, Stephen Adolph a écrit : > > > Here is the current status of REX# (and REXCPM) interworking. > > Better than I thought! > > > >

Re: [M100] Rex#..TPDD compatibility

Here is the current status of REX# (and REXCPM) interworking. Better than I thought! [image: image.png] Dosbox is set up to run pretty slow, but my set up runs Desklink well on Windows 10, and also runs PDD.EXE, which is great. Backpack works for general use with REX#. Just the REX# utilities

Re: [M100] Rex#..TPDD compatibility

thanks Josh, I think I should be able to test mComm windows. I imagine I need something special to use mComm android. On Thu, Jan 12, 2023 at 10:14 PM Josh O’Keefe wrote: > Those I have used “for real” recently not on your list: > mComm Python > dlplus > > Those I’m aware of off the top of my

Re: [M100] Rex#..TPDD compatibility

On 1/12/23 14:37, Stephen Adolph wrote: Thinking about a maintenance release on REX# to pick up a bunch of fixes and improvements. One of the items is to make the interface to a TPDD client more reliable. Did I get that right Brian? ;) No, since these are servers. ;) The code inside rxcini

Re: [M100] Rex#..TPDD compatibility

Those I have used “for real” recently not on your list: mComm Python dlplus Those I’m aware of off the top of my head not on your list, but can’t comment on further due to platform constraints: mComm Windows mComm Android Sent from my iPhone > On Jan 13, 2023, at 8:38 AM, Stephen Adolph

Re: [M100] REX availability

Great! Would like REXCPM for 102 and REX for 100. Chris On Thu, Dec 8, 2022, 11:20 PM Stephen Adolph wrote: > Yes they are! For rexcpm you need s machine specific adapter. M100 or > t102? > > > > On Thursday, December 8, 2022, Chris Kmiec wrote: > >> I have one in my 102, and just got

Re: [M100] REX availability

Yes they are! For rexcpm you need s machine specific adapter. M100 or t102? On Thursday, December 8, 2022, Chris Kmiec wrote: > I have one in my 102, and just got another 100 and 102. Would like to get > both REX and REXCPM. Are they still available? > > Thanks! >

Re: [M100] REX

Bob, I'd be happy to help you out. Please contact me off list. I believe the email address should be visible. thanks Steve On Sun, Nov 13, 2022 at 1:14 PM Bob Sylvester wrote: > To Whom It May Concern; > > Is the REX still available? > > Regards, > > Bob Sylvester > >

Re: [M100] REX

Chuckle! Anyhow, I recently got a 2MB REXCPM and it works swell! On 11/13/22 1:41 PM, Gregory McGill wrote: Sure is did you look at the rex page? or are you a bing user? https://bitchin100.com/wiki/index.php?title=REX On Sun, Nov 13, 2022, 10:14 AM Bob Sylvester wrote: To Whom It May

Re: [M100] REX

Sure is did you look at the rex page? or are you a bing user? https://bitchin100.com/wiki/index.php?title=REX On Sun, Nov 13, 2022, 10:14 AM Bob Sylvester wrote: > To Whom It May Concern; > > Is the REX still available? > > Regards, > > Bob Sylvester > >

Re: [M100] REX# and Option ROMs: Qs from a noob

On Thu, Jul 7, 2022 at 2:58 PM Charles Hudson wrote: > Okay, this is what I was looking for: > http://www.club100.org/library/libdoc.html > Oh, good. I went to the librom page and didn't see it. Guess I should have dug deeper. And apparently the outliner is called THOUGHT not THINK. Memory

Re: [M100] REX# and Option ROMs: Qs from a noob

Okay, this is what I was looking for: http://www.club100.org/library/libdoc.html

Re: [M100] REX# and Option ROMs: Qs from a noob

If I have the pdf files they are buried somewhere on my network. I’ll keep looking. May end up scanning. Here’s a tip buy for getting several rims working (from Club100): Most option ROMs for the Model 100/102, Model 200, and NEC PC-8201A use the same ROM call, since you are telling the OS to

Re: [M100] REX# and Option ROMs: Qs from a noob

Also: https://ia803208.us.archive.org/22/items/Multiplan_for_Tandy_100_1984_Microsoft/Multiplan_for_Tandy_100_1984_Microsoft.pdf

Re: [M100] REX# and Option ROMs: Qs from a noob

Interestingly, found this email archive while nosing around: https://m100.bitchin100.narkive.com/yM6Z1vcJ/spreadsheet-program-for-model-100 Rick Hansons's advice: "Download the files as if they were .txt files to your PC, then move them over to your Model "T" as .do files, load them into BASIC

Re: [M100] REX# and Option ROMs: Qs from a noob

I'll look in my old downloads. I think I might have a set. If not, may be able to create a set between John & I. Jul 7, 2022 2:14:08 PM John R. Hogerhuis : > I have original manuals but I know PDFs are around. And in general SuperROM > installs the usual way, I think CALL 63012,0 or similar.

Re: [M100] REX# and Option ROMs: Qs from a noob

I have original manuals but I know PDFs are around. And in general SuperROM installs the usual way, I think CALL 63012,0 or similar. The keyboard commands are generally guessable at least for THINK. But, documentation would be better. Anyone have links to PDFs? -- John.

Re: [M100] REX# and Option ROMs: Qs from a noob

John or Joshua, Thus far I have only found documentation for the UR2100 ROM, and that only an overall description. Specifics of operation of the TEXT and BASE programs are still a mystery, e.g. how to call up a print menu. Apparently there is one but ... As for the other ROMs I haven't found

Re: [M100] REX# and Option ROMs: Qs from a noob

> > > Try out SuperROM too. "Think" outliner is my #1 favorite model t program after TEXT. -- John. > <#m_7172767600747353736_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >

Re: [M100] REX# and Option ROMs: Qs from a noob

Thanks, Joshua, I found out more about the Intex HEX format and also found the pre-converted ROMS at the end of the REX# Manager documentation. I have successfully installed the UR2100 ROM and created a text document with it; I'm making my way, slowly. Thanks again for your help. -CH-

Re: [M100] REX# and Option ROMs: Qs from a noob

> On Jul 6, 2022, at 5:53 AM, Charles Hudson wrote: > I found the OR files at http://www.club100.org/library/librom.html and > inspected a few. Immediately I was out of my depth, so pardon me for > inquiring: Hi Charles, I'd suggest you might want to start with the binary files at

Re: [M100] REX question

Teeny? On Thursday, July 8, 2021, Tom Wilson wrote: > Right, you don’t need TS-DOS, but you need *something* with the ability > to load files from a TPDD compatible device. If you have an actual TPDD, > you can use the bootstrap function, otherwise you have to find a program > that can be used

Re: [M100] REX question

Right, you don’t need TS-DOS, but you need *something* with the ability to load files from a TPDD compatible device. If you have an actual TPDD, you can use the bootstrap function, otherwise you have to find a program that can be used to bootstrap the necessary files. That was the challenge -

Re: [M100] REX question

I've been informed that you don't actually need TS-DOS loaded to flash a REX -- just something to load the flash utility. Teeny will do. On Thu, Jul 8, 2021 at 6:38 PM Tom Wilson wrote: > > Yes, I have flashed a Rex Classic to work on a 200. It’s a PITA, mostly to > get the DOS boot loader on

Re: [M100] REX question

Yes, I have flashed a Rex Classic to work on a 200. It’s a PITA, mostly to get the DOS boot loader on so I can get the TS-DOS ROM loaded. The problem being that with only 24K of RAM per bank, it’s hard to find a BASIC loader small enough to do the job. If you need me to, I can dig through my

Re: [M100] REX question

Thank you Josh and Brian On Thu, Jul 8, 2021 at 2:25 PM Brian Brindle wrote: > Hi Bill, > > Yes, you can use the same REX in a model 100 or 102. > > If they are mod100/102's have the same amount of memory you will have no > issues with stored RAM Images, but if they are different you will get a

Re: [M100] REX question

Hi Bill, Yes, you can use the same REX in a model 100 or 102. If they are mod100/102's have the same amount of memory you will have no issues with stored RAM Images, but if they are different you will get a memory size mismatch when attempting to load them. Easy to fix using the file browse

Re: [M100] REX question

Bill, REX# and it's predecessor REX can be installed in either M100 or T102. Meaning you buy an M100 version, you can use it in T102 also, and move it between the 2 if you want. I don't make REX anymore. I have switched to the new design REX#. If you really want the old version others will make

Re: [M100] REX question

REX classic and REX# come in 2 "flavors": 100/102 and 200 The hardware is physically identical, as is the CPLD program. However, the FLASH load is different, owing to the different memory configurations/maps on the 2 systems. You can "reprogram" a 100/102 into a 200 and vice-versa by following

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

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

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

: Re: [M100] REX# Version 2 software update. Oh forgot one thing. I have updated the option rom .ZIP files posted there, to include Kurt's bug-fix versions of TS-DOS for M100, T200 and NEC.  cheers, and thanks again Kurt. Steve

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

Oh forgot one thing. I have updated the option rom .ZIP files posted there, to include Kurt's bug-fix versions of TS-DOS for M100, T200 and NEC. cheers, and thanks again Kurt. Steve On Thu, Jan 7, 2021 at 9:47 PM Stephen Adolph wrote: > Many delays for this, sorry to those who've been waiting

Re: [M100] REX Classic Message

ickly a person can't read it (even though the operation of REX is correct and not an error). Thanks and regards, Peter > > -- > > Message: 9 > Date: Sun, 3 Jan 2021 07:12:52 -0500 > From: Stephen Adolph > To: m...@bitchin100.com > Subject:

Re: [M100] REX Classic Message

it is a message telling you that the system software hooks changed. This is just informative; Option ROMs often install their own hooks to do certain things, like removal of their software when the ROM is "removed". I think this sequence of events can cause the hooks to change, and display the

Re: [M100] REX update questions (probably only answerable by Stephen)

Sure send the RAM image. I'll check it out in Virtual T (the prototype that I have that supports REX# and REXCPM- hopefully that will get released at some point. As is par for the course with me, I introduced a bug or 2 into the prototype but heck it was my first ever C programming). On Mon,

Re: [M100] REX update questions (probably only answerable by Stephen)

> -Original Message- > > Active block is always first, does seem to fit what is happening? I just > checked on my end and it seems to be working.  Active block first, then > sorted by date/time. Yes, it shows the active block first as always, it's the rest of the entries which aren't

Re: [M100] REX update questions (probably only answerable by Stephen)

Active block is always first, does seem to fit what is happening? I just checked on my end and it seems to be working. Active block first, then sorted by date/time. Sorry about the rebuild. Every time I think I have a robust working solution On Sun, Dec 20, 2020 at 4:39 PM Jim Anderson

Re: [M100] REX update questions (probably only answerable by Stephen)

> -Original Message- > > I see you understand "S" not "O".  I've checked it out on my end and it > was working.  If the date/time stamps are the same, sort order won't > change. The sort order does change with each press of S (reverse and forwards), it's just that the sort order is

Re: [M100] REX update questions (probably only answerable by Stephen)

> -Original Message- > > Re REXclassic: sounds like your directory is corrupted at first > glance.  I would do a full rebuild, not just the software. > Let me know if you cannot find the tools you need. Argh... OK, yeah, hard lesson about backup-before-trying-something-new learned

Re: [M100] REX update questions (probably only answerable by Stephen)

I see you understand "S" not "O". I've checked it out on my end and it was working. If the date/time stamps are the same, sort order won't change. Anyhow, I will check it again. steve On Sun, Dec 20, 2020 at 4:25 PM Stephen Adolph wrote: > re REXCPM - S changes the sort order! > > Re

Re: [M100] REX update questions (probably only answerable by Stephen)

re REXCPM - S changes the sort order! Re REXclassic: sounds like your directory is corrupted at first glance. I would do a full rebuild, not just the software. Let me know if you cannot find the tools you need. cheers, steve On Sun, Dec 20, 2020 at 3:05 PM Jim Anderson wrote: > I recently

Re: [M100] REX update questions (probably only answerable by Stephen)

A couple of additional notes: > update, of course). Press O to change sort order only reverses the OCD self-nitpick: I meant S, not O. :) > and cats... my T102 locked up solid and the Reset button wouldn't Amendment: I noticed a couple of additional things. - Although the Reset button won't

Re: [M100] REX# erratic behavior and data corruption

David, I'll send you the test program to run so you can confirm if your REX# has a hardware issue. ..Steve On Tue, Nov 10, 2020 at 8:01 AM David Kinzler wrote: > I'd like to first acknowledge that I'm a new Model 100 user, and I suspect > user error is a large component of my woes. > >

Re: [M100] REX Classic

> > > > *From: *Gregory McGill > *Sent: *Thursday, May 21, 2020 2:44 PM > *To: *m...@bitchin100.com > *Subject: *Re: [M100] REX Classic > > > > usually this is a contact issue.. > > > > > > On Thu, May 21, 2020 at 10:52 AM Stephen Adolph

Re: [M100] REX Classic

. Thanks for the heads up on that issue. Framer Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Gregory McGill<mailto:arcadeshop...@gmail.com> Sent: Thursday, May 21, 2020 2:44 PM To: m...@bitchin100.com<mailto:m...@bitchin100.com> Subject: Re:

Re: [M100] REX Classic

usually this is a contact issue.. On Thu, May 21, 2020 at 10:52 AM Stephen Adolph wrote: > Hi, hard to say. what design is it? Is it from me or other? (sorry if I > don't recall) > Steve > > On Thu, May 21, 2020 at 1:43 PM William McKay wrote: > >> I have two Model 100 USA model numbers

Re: [M100] REX Classic

Hi, hard to say. what design is it? Is it from me or other? (sorry if I don't recall) Steve On Thu, May 21, 2020 at 1:43 PM William McKay wrote: > I have two Model 100 USA model numbers and the same. REX works perfect in > one and hang when the call 63012 is issued and need a cold boot.

Re: [M100] REX 260 Updating

t; > > -- >> >> Message: 3 >> Date: Thu, 9 Apr 2020 23:21:47 -0700 >> From: Tom Wilson >> To: M100 Mailing List >> Subject: Re: [M100] REX 260 Updating >> Message-ID: >> < >> calt8mqtrp6-ywlj+ij0k-

Re: [M100] REX 260 Updating

with the new system. Maybe not, but a clean start can't hurt. Also a good time to do some file organization in the images. Peter -- > > Message: 3 > Date: Thu, 9 Apr 2020 23:21:47 -0700 > From: Tom Wilson > To: M100 Mailing List > Subject: Re: [M100

Re: [M100] REX 260 Updating

To prove it to yourself, in REXMGR, on any screen, press "i". 4.9-260 for 100/102 is CS=DF79 Here's the last few builds for all 3 platforms: REX versions REXMGR info screen (press i) 4.9 build 254 100 CS=DD90 200 CS=0FEC NEC CS=3CEC 4.9 build 258 100 CS=E16C 200 CS=1B0D NEC

Re: [M100] REX 260 Updating

So here's what I did... I started by extracting the ZIP file to the ROM100 directory under my LaddieAlpha Root. (in my case, that's C:\Model 100\root\rom100) So I have RF149.CO TSD100.BX RF149.BR Then I started LaddieAlpha. On my T102, I started RexMgr and activated TS-DOS. F4 (DISK) Select the

Re: [M100] REX 260 Updating

If you're using LaddieAlpha, this is a TPDD device. So you just need to back up all of your banks to your PC (through LaddieAlpha) then activate the TSDOS ROM and use that to copy RFx49.CO to your T102. I'm about to perform exactly the same process with my 102, so I'll try it and get back to you

Re: [M100] REX problem with .DO files

thanks for the excellent bug report. I have replicated it. I'll get it fixed. It is a common bug across REX Classic, REX# and REXCPM. Steve On Sun, Apr 5, 2020 at 10:52 PM Peter Noeth wrote: > Yes Stephen, I should have been more specific, but I didn't have my T102 > in front of me: > > 1)

Re: [M100] REX problem with .DO files

pr 2020 08:01:32 -0400 > From: Stephen Adolph > To: m...@bitchin100.com > Subject: Re: [M100] REX problem with .DO files > Message-ID: > vcrcikwnw_acfjybozx0_tcc3mtvmpcygtwru...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > tha

Re: [M100] REX problem with .DO files

I will never use the system ROM option, but I sure would like those extra ace slots, especially on my T-200, which throws away 16K on every slot. On Sun, Apr 5, 2020 at 7:16 AM Stephen Adolph wrote: > good question. Had not considered that to be honest. > If you have a working REX today.. not

Re: [M100] REX problem with .DO files

yes, TS-DOS is in the same default place, same block # On Sun, Apr 5, 2020 at 2:49 PM Ken Pettit wrote: > Hey Steve, > > I downloaded it from the Wiki, but I have a question. Is the starting > directory image the same as 4.8, or has that changed also? VirutalT writes > both the REX software

Re: [M100] REX problem with .DO files

Hey Steve, I downloaded it from the Wiki, but I have a question. Is the starting directory image the same as 4.8, or has that changed also? VirutalT writes both the REX software as well as the starting directory image. Ken On 4/5/20 10:51 AM, Stephen Adolph wrote: sure that would be

Re: [M100] REX problem with .DO files

sure that would be great. Do you need an image? or did you grab it from the wiki? use the "full" image 32k that includes directories. thx Steve On Sun, Apr 5, 2020 at 1:23 PM Ken Pettit wrote: > Steve, > > Since I am workingon a VirtualT 1.8 release, should I pull in REX release > 258 as the

Re: [M100] REX problem with .DO files

Steve, Since I am workingon a VirtualT 1.8 release, should I pull in REX release 258 as the FW loaded for "Create Default Flash" button when choosing REX memory emulation? Ken On 4/4/20 12:14 PM, Stephen Adolph wrote: Yes. That's what is available now. I can post an upgrade version later

Re: [M100] REX problem with .DO files

good question. Had not considered that to be honest. If you have a working REX today.. not sure you need REX#? On Sun, Apr 5, 2020 at 10:10 AM Tom Wilson wrote: > Will we be able to run Rex# on current hardware, or will that require a > new board? > > On Sun, Apr 5, 2020 at 5:01 AM Stephen

Re: [M100] REX problem with .DO files

Will we be able to run Rex# on current hardware, or will that require a new board? On Sun, Apr 5, 2020 at 5:01 AM Stephen Adolph wrote: > thanks Peter, I'll try to replicate your bug. I think you are saying that > after renaming a file, the function key name tags were not visible? > > You are

Re: [M100] REX problem with .DO files

thanks Peter, I'll try to replicate your bug. I think you are saying that after renaming a file, the function key name tags were not visible? You are correct that software testing is a challenge. The biggest challenges are (1) Support for multiple models, especially mult-bank support. This was

Re: [M100] REX problem with .DO files

the rename was successful, the label menu was not re-displayed. I think this also occurs when killing a file, but I am not sure. Regards, Peter -- > > Message: 1 > Date: Sat, 4 Apr 2020 08:20:04 -0400 > From: Stephen Adolph > To: m...@bitchin100.com > Subject: Re: [M100

Re: [M100] REX problem with .DO files

great! cheers. I think calling 258 a beta is a little funny. But as we have seen there are always bugs to fix. On Sat, Apr 4, 2020 at 7:58 PM Josh Malone wrote: > Seems to work perfectly! Upgraded my 4.9 REX on 102 to the latest version. > Was able to cold-start, load REXMGR, and restore a

Re: [M100] REX problem with .DO files

Seems to work perfectly! Upgraded my 4.9 REX on 102 to the latest version. Was able to cold-start, load REXMGR, and restore a saved RAM image. Starblaze still runs after the memory restore so I'd say all is in order. Checksum E16C -Josh On Sat, Apr 4, 2020 at 7:43 PM Stephen Adolph wrote: >

Re: [M100] REX problem with .DO files

Hi, I posted upgrade only. Hopefully they work without an issue. Josh, maybe give this a whirl and let me know? thx Steve On Sat, Apr 4, 2020 at 1:12 PM Josh Malone wrote: > So, this is also a "wipe and re-load completely" upgrade? Is that > necessary? Seems like the bug is only in REXMGR

Re: [M100] REX problem with .DO files

On 4/4/20 6:20 PM, John R. Hogerhuis wrote: On Sat, Apr 4, 2020 at 2:56 PM Brian K. White > wrote: 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

Re: [M100] REX problem with .DO files

On 4/4/20 3:20 PM, John R. Hogerhuis wrote: I have been working with Ken. If you're using NEWDOS 5.05, there are significant issues. In other words, it's probably not DLPlus. NEWDOS is broken. Yep, and that's what *I* am working on while locked indoors. :) Ken

Re: [M100] REX problem with .DO files

On Sat, Apr 4, 2020 at 2:56 PM Brian K. White wrote: > > 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

Re: [M100] REX problem with .DO files

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

Re: [M100] REX problem with .DO files

Yes. That's what is available now. I can post an upgrade version later so long as you are on 254 now. A lot of people have not upgraded to rhe new directory format hence I force it with a wipe. On Saturday, April 4, 2020, Josh Malone wrote: > So, this is also a "wipe and re-load completely"

Re: [M100] REX problem with .DO files

So, this is also a "wipe and re-load completely" upgrade? Is that necessary? Seems like the bug is only in REXMGR which is just block 0, right? Or are the stored RAM images also corrupt and not usable on 258? -Josh On Sat, Apr 4, 2020 at 8:20 AM Stephen Adolph wrote: > Peter, thanks for

Re: [M100] REX problem with .DO files

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

Re: [M100] Rex(CP/M) documentation?

On 3/23/20 10:00 PM, Tom Wilson wrote: On Mon, Mar 23, 2020 at 6:30 PM Brian K. White > wrote: There is also a fairly good cheat sheet built right in to REXMGR. There are still a mystery or two though. For instance, what is the OS tab? "OS" sounds like

Re: [M100] Rex(CP/M) documentation?

Sounds great. On 3/23/20 9:39 PM, Stephen Adolph wrote: OS is a useless function, in the end. It was intended to differentiate between option roms and things like CP/M. In the end, it's just complexity for no point. I've deleted it from REX#, which I just now got the first hardware working

Re: [M100] Rex(CP/M) documentation?

On Mon, Mar 23, 2020 at 6:30 PM Brian K. White wrote: > There is also a fairly good cheat sheet built right in to REXMGR. > > There are still a mystery or two though. For instance, what is the OS > tab? "OS" sounds like it must be the main rom feature, and the screen > even looks like it, but

Re: [M100] Rex(CP/M) documentation?

OS is a useless function, in the end. It was intended to differentiate between option roms and things like CP/M. In the end, it's just complexity for no point. I've deleted it from REX#, which I just now got the first hardware working for. REX# ("REX Sharp") is a redesign of REX, with simpler,

Re: [M100] Rex(CP/M) documentation?

There is also a fairly good cheat sheet built right in to REXMGR. There are still a mystery or two though. For instance, what is the OS tab? "OS" sounds like it must be the main rom feature, and the screen even looks like it, but the main rom images are managed in the SYS tab. -- bkw On

Re: [M100] Rex(CP/M) documentation?

From an end user standpoint, the documentation needed is pretty simple: pick the thing you want and press enter on it. Try function keys to see if they do anything cool. Some of them do. It was not totally obvious to me until I picked up on the "Enter probably does what you want to the thing

Re: [M100] Rex(CP/M) documentation?

Here's the official home for Rex documentation. http://bitchin100.com/wiki/index.php?title=Rex -- John.

Re: [M100] REX problem with .DO files

Seems like the file table or the memory file region pointers not being updated. Or maybe an unterminated file. > -- John.

Re: [M100] REX problem with .DO files

thanks, I'll look into this. I think it probably relates to the use of the buffers by REX, but I don't know for sure. On Mon, Mar 23, 2020 at 3:15 AM Tom Wilson wrote: > I reproduced it on the 200. > >1. Cold booted (I turned the 200's memory switch off before I put it >away.) >2.

Re: [M100] REX problem with .DO files

I reproduced it on the 200. 1. Cold booted (I turned the 200's memory switch off before I put it away.) 2. Started Rex with CALL 61167,2 3. Create a text file TEST.DO - This is a test - This is line 2 - This is line 3 4. Created a new backup called "TEST" 5.

Re: [M100] REX on M200

REX hardware and CPLD load is the same between 100 and 200 but the flash load is different. Flash load can be changed in the 200 in-situ -- just follow the REX flash upgrade procedure. On Wed, Mar 11, 2020, 4:05 PM Tom Wilson wrote: > So I may have just stored a M200 on EBay... for super cheap.

Re: [M100] REX on M200

Yes just needs to be re-flashed and it should be fine. It is probably the easiest way to get TS-DOS onto the machine. There are a few options to build an EEPROM board eg http://tandy.wiki/Teeprom but if you already have a REX then I would just go that route. From: M100 on behalf of Tom

Re: [M100] REX + Ultrascreen100

REX heavily uses ALTLCD.. that memory space is almost surely being clobbered by Ultrascreen. I didn't design REX with the though that Ultrascreen would need to be usable with it, in the same way DVI does not work with REX. Sorry! In my new project REX#, I may be able to address that.Also

  1   2   3   4   5   >