[M100] My old WP-2 and 200

[Mitch Parker]

Good evening,

I am not getting the use that I want out of these devices, and honestly, I
like the 102 better.

Who wants them for a reasonable price?  They are working, although the 200
needs a new NiCad, and in excellent condition.

Thanks,

Mitch

Re: [M100] Brand new member

[Willard Goosey]

On Sun, 27 Jan 2019 15:51:07 -0500
Stephen Pereira  wrote:

> Hi Willard, and thanks a million for letting me know this!
> 
No problem.

> I’ve been pulling my hair out, trying to figure out what I was
> missing.  Why in the world did it end up this way?  Why would folks
> make an XMODEM program and advertise it as a way to handle .CO files,

I always assumed that the xmodem authors simply didn't have the
documentation about writing .CO files available.  It turns out that
writing .CO files from a .CO is complicated and fragile. (See this list
archive over the last (gaaa!) 2 years, where I had MANY questions about
making that work...)

> but then they don’t?  Too weird for me!  I am so glad to know that I
> am not totally incompetent!
> 
To be fair, it is in the docs for xmodem.ba and xmdpw.ba that they only
support transferring ASCII files.. ;-)

Willard
-- 
Willard Goosey  goo...@sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard

Re: [M100] Selling my M100 collection

[James Zeun]

That's lovely, best of luck selling your collection.

Would absolutely love a manual for my M100. Pdf's are all great, but I
prefer physical books.

-James

On Sun, 27 Jan 2019, 1:57 am Scotty Brown  Hey all,
>
> I've had a great time reconnecting with my M100, and in large that is
> thanks to this community.  Quite a few of you helped me troubleshoot and
> chase things down - so thank you.
>
> Between young kids and life though I am not getting to use the M100 the
> way I thought - so I'd like to hand it on to someone else to enjoy.  Before
> I list it on eBay I thought I would offer the lot up to this group first.
> I don't know what it's worth so I'm open to honest offers.  I am in
> Australia though - and am hoping there is someone on the Gold Coast or in
> Brisbane that is interested.
>
> Once you see the amount of stuff included you'll understand my hesitation
> around postage.  I am also not looking to split just yet.  I will if I have
> to - but would like the whole lot to go in one hit if at all possible.
> Pictures and a desc of what is included is on imgur at the link below.
>
> https://imgur.com/a/S05JKeW
>
> Thanks again,
> Scotty
>
> --
>   Scotty Brown
>   sco...@pennmail.net
>

Re: [M100] Unable to Load TEENY to MT

[Josh Malone]

I have only ever used TS-DOS RAM to load RFx49.co -- I've programmed
over 40 REXes with TS-DOS in RAM and never had an issue. In fact, I
didn't even realize that RFx49.c had its own DOS routines -- I assumed
that it needed DOS in RAM. Not having to load full TS-DOS would save a
bit of time programming REXes.

-Josh

Re: [M100] Brand new member

[John R. Hogerhuis]

On Sun, Jan 27, 2019 at 2:28 PM Stephen Pereira <
stephen.m.pereira...@gmail.com> wrote:

> Oh, crap!  The serial device path…
>
> Starting with Mac OS Mohave (10.14.x) Apple has now built in the driver
> for my Prolific USB-to-serial device.  That means it no longer shows up in
> /DEV as a plug & play device, Mac OS just takes care of it.  All this to
> say that I don’t know what the path to my serial device is any more.
>
>
It's unix it must have a device name path. Sometimes your driver+device
can be configured to always show up as a specific name.

I do that on my Linux machines, but it uses the udev filesystem. Whenever a
usb devices is plugged in, I can run a script that renames the device, and
I can trigger off specific models/serial numbers.

I don't know what you do on OSX, but there is usually a way.


> I also have Parallels, and I can run my Windows XP virtual machine.  Would
> that work?  In Windows XP, my USB-to-serial device shows up as COM4.
>
>
If you're using Windows and don't have Rex you should use Kurt's MComm
program. It will help you inject TEENY and get started quickly.

He shares it in his personal libraries on Club 100.


> What do I need to run your Laddie on Windows XP?
>
>
.NET 3.5 or higher. The original laddiecon supports .NET 2.0 I think, you
could use it if necessary. I don't know what XP came with.

-- John.

Re: [M100] Brand new member

[Stephen Pereira]

Oh, crap!  The serial device path…

Starting with Mac OS Mohave (10.14.x) Apple has now built in the driver for my 
Prolific USB-to-serial device.  That means it no longer shows up in /DEV as a 
plug & play device, Mac OS just takes care of it.  All this to say that I don’t 
know what the path to my serial device is any more.

I also have Parallels, and I can run my Windows XP virtual machine.  Would that 
work?  In Windows XP, my USB-to-serial device shows up as COM4.

What do I need to run your Laddie on Windows XP?

smp
- - -
Stephen Pereira
Bedford, NH  03110
KB1SXE


> On Jan 27, 2019, at 5:23 PM, John R. Hogerhuis  wrote:
> 
> 
> 
> On Sun, Jan 27, 2019 at 2:20 PM Stephen Pereira 
> mailto:stephen.m.pereira...@gmail.com>> 
> wrote:
> Hi John, and thanks very much for your reply!
> 
> With Mono, do I have to build anything, or would I install it and use it to 
> run Laddie?  
> 
> You know, like:  prompt> MONO LADDIE.EXE
> 
> I’ll take a look at the web site and Wili.
> 
> 
> That's pretty much it. You don't have to compile it.
> 
> But you do need to tell it the serial device path. 
> 
> -- John.

Re: [M100] Brand new member

[John R. Hogerhuis]

On Sun, Jan 27, 2019 at 2:20 PM Stephen Pereira <
stephen.m.pereira...@gmail.com> wrote:

> Hi John, and thanks very much for your reply!
>
> With Mono, do I have to build anything, or would I install it and use it
> to run Laddie?
>
> You know, like:  prompt> MONO LADDIE.EXE
>
> I’ll take a look at the web site and Wili.
>
>
That's pretty much it. You don't have to compile it.

But you do need to tell it the serial device path.

-- John.

Re: [M100] Unable to Load TEENY to MT

[John R. Hogerhuis]

On Sun, Jan 27, 2019 at 2:11 PM Stephen Adolph  wrote:

>
>
>>> when himem is not set correctly, ... a .CO program beeps, of course, on
>>> failed start up.
>>>
>>
>> Yes. BTW, why do you document a clear at 55,000 rather than at what TOP
>> is set to a few hundred bytes higher? Do you  use memory before your
>> program?
>>
>>
>
> John, just laziness on my part.
> D800
> 55296
>
>
Or laziness on the user's behalf ;-)

55,000 is certainly easier to remember

-- John.

Re: [M100] Unable to Load TEENY to M1

[Fugu ME100]

Must admit I have never had that happen, all the faults I have seen usually 
allow the RF149.co run to completion.   I have plugged them in backwards a few 
times though :-D Especially when trying to debug crashing programmings.

I have had problems where the +5V has failed and corrupted a REX, not sure how 
that can happen, but reprogramming it usually brings it back to life.   Yes 
sometimes I forget the REX is in there when playing with system bus plugins.

From: M100 
mailto:m100-boun...@lists.bitchin100.com>> 
on behalf of Stephen Adolph mailto:twospru...@gmail.com>>
Reply-To: mailto:m...@bitchin100.com>>
Date: Sunday, January 27, 2019 at 2:07 PM
To: mailto:m...@bitchin100.com>>
Subject: Re: [M100] Unable to Load TEENY to M1

the fact that you say that 
RF149.CO
 hung during burning of a file (in this case the RexManager software) to me 
says that the flash is stalled in the "BUSY" state.   One of 2 things
(1) REX is improperly seated
(2) REX has a hardware defect

In my experience contrary to Fugu (i am very reluctant to differ from him 
ever!) all of my REX software can hang when the Flash gets stuck in BUSY state. 
   This happens when for example the software tries to REWRITE a "1" to an 
address that has already been WRITTEN to "0" value.   This only happens if the 
software is buggy, or somehow there is a hardware defect, like a malfunctioning 
address line connection.

..Steve


On Sun, Jan 27, 2019 at 4:58 PM Greg Swallow 
mailto:gswal...@mchsi.com>> wrote:
I did get farther, even with TS-DOS loaded. Ran 
RF149.CO
 from MENU after the LOADM. It seem to start ok, but then nothing seemed to 
happen when left it half the night loading 0:RF149.BX. Maybe I should have let 
go all night.

God Bless,

GregS <><
- Original Message -
From: John R. Hogerhuis mailto:jho...@pobox.com>>
To: m...@bitchin100.com
Sent: Sun, 27 Jan 2019 05:37:32 -0500 (EST)
Subject: Re: [M100] Unable to Load TEENY to MT

But it gave no error...

I think it loaded. Meaning when you typed loadm it copied it's contents to
55302.

Not sure why the clear address is 55000. The program starts at 55302. Maybe
the program uses the gap as a scratchpad.

I'm guessing the beep is from the program itself. Maybe it's done or maybe
it's giving you an error.

-- John.


On Sun, Jan 27, 2019, 12:24 AM Greg Swallow 
mailto:gswal...@mchsi.com> wrote:

> CLEAR0,55000: 
> LOADM"RF149.CO"
>  gives
>
> Top: 55302
> End: 60148
> Exe: 55302
>
> Hope this helps
>
> GregS <><
>
>
> - Original Message -
> From: "John R. Hogerhuis" mailto:jho...@pobox.com>>
> To: m...@bitchin100.com
> Sent: Sunday, January 27, 2019 12:03:56 AM
> Subject: Re: [M100] Unable to Load TEENY to MT
>
> What did you try to "clear out" ts-dos?
>
> I don't think that beep has anything to do with TS-DOS. When a CO file
> beeps on load, it's because the CLEAR statement is wrong. And if you typed
> the CLEAR statement and it gave no error, then you have sufficient room to
> run the utility.
>
> If it beeps anyway, maybe the program is running but just beeps. Who knows.
>
> Do me a favor, do the CLEAR statement, and 
> LOADM"RF149.CO
> from the BASIC prompt, not from the main menu and tell us what you see.
>
> If it prints out the CO file's header, we can figure out if
>
> a) The clear statement is right
> b) The beep is coming as a BASIC load issue, or for some other reason.
>
> -- John.
>

Re: [M100] Brand new member

[Stephen Pereira]

Hi John, and thanks very much for your reply!

With Mono, do I have to build anything, or would I install it and use it to run 
Laddie?  

You know, like:  prompt> MONO LADDIE.EXE

I’ll take a look at the web site and Wili.

Thanks!

smp
- - -
Stephen Pereira
Bedford, NH  03110
KB1SXE


> On Jan 27, 2019, at 4:40 PM, John R. Hogerhuis  wrote:
> 
> 
> 
> On Sun, Jan 27, 2019 at 11:43 AM Stephen Pereira 
> mailto:stephen.m.pereira...@gmail.com>> 
> wrote:
> 
> I use a Macintosh MacBook Pro laptop as my computer, so on the laptop side, 
> I’ll need a drive emulator that will work on the latest Mac OS X 10.14.3.
> 
> Thanks again for your attention!
> 
> 
> I'll let others respond about Rex.
> 
> For the mac, if you are willing to install Mono, you can use LaddieAlpha. I 
> wrote and support that.
> 
> If you prefer compiling a C program you can use DLPlus. I am more likely to 
> update LaddieAlpha than DLPlus, since LaddieAlpha runs on WIndows, Linux, 
> Mac. 
> 
> All are available via http://bitchin100.com  or the 
> http://bitchin100.com/wiki 
> 
> -- John.

Re: [M100] Unable to Load TEENY to MT

[Stephen Adolph]

>
>> when himem is not set correctly, ... a .CO program beeps, of course, on
>> failed start up.
>>
>
> Yes. BTW, why do you document a clear at 55,000 rather than at what TOP is
> set to a few hundred bytes higher? Do you  use memory before your program?
>
>

John, just laziness on my part.
D800
55296

Re: [M100] Unable to Load TEENY to MT

[Fugu ME100]

Ah interesting.  So perhaps the method should be to perform the DOS-ON/DOS-OFF 
first and then clearmem.  Rather than just clearmem.   That might clear 
everything out properly.

From: M100 
mailto:m100-boun...@lists.bitchin100.com>> 
on behalf of "John R. Hogerhuis" mailto:jho...@pobox.com>>
Reply-To: mailto:m...@bitchin100.com>>
Date: Sunday, January 27, 2019 at 2:08 PM
To: mailto:m...@bitchin100.com>>
Subject: Re: [M100] Unable to Load TEENY to MT



On Sun, Jan 27, 2019 at 1:48 PM Fugu ME100 
mailto:b4me...@hotmail.com>> wrote:

  *Simply clearing a piece of RAM does not undo anything RAM TPDD might of 
done to various hooks, timers or buffers.

True, but that is what the DOS-ON/DOS-OFF command in TS-DOS does. It hooks / 
unhooks the BASIC extensions.

If it does not, it is a bug in TS-DOS. Which of course is possible, it wouldn't 
be the first bug discovered.

-- John.

Re: [M100] Unable to Load TEENY to M1

[Stephen Adolph]

the fact that you say that RF149.CO hung during burning of a file (in this
case the RexManager software) to me says that the flash is stalled in the
"BUSY" state.   One of 2 things
(1) REX is improperly seated
(2) REX has a hardware defect

In my experience contrary to Fugu (i am very reluctant to differ from him
ever!) all of my REX software can hang when the Flash gets stuck in BUSY
state.This happens when for example the software tries to REWRITE a "1"
to an address that has already been WRITTEN to "0" value.   This only
happens if the software is buggy, or somehow there is a hardware defect,
like a malfunctioning address line connection.

..Steve


On Sun, Jan 27, 2019 at 4:58 PM Greg Swallow  wrote:

> I did get farther, even with TS-DOS loaded. Ran RF149.CO from MENU after
> the LOADM. It seem to start ok, but then nothing seemed to happen when left
> it half the night loading 0:RF149.BX. Maybe I should have let go all night.
>
> God Bless,
>
> GregS <><
> - Original Message -
> From: John R. Hogerhuis 
> To: m...@bitchin100.com
> Sent: Sun, 27 Jan 2019 05:37:32 -0500 (EST)
> Subject: Re: [M100] Unable to Load TEENY to MT
>
> But it gave no error...
>
> I think it loaded. Meaning when you typed loadm it copied it's contents to
> 55302.
>
> Not sure why the clear address is 55000. The program starts at 55302. Maybe
> the program uses the gap as a scratchpad.
>
> I'm guessing the beep is from the program itself. Maybe it's done or maybe
> it's giving you an error.
>
> -- John.
>
>
> On Sun, Jan 27, 2019, 12:24 AM Greg Swallow 
> > CLEAR0,55000: LOADM"RF149.CO" gives
> >
> > Top: 55302
> > End: 60148
> > Exe: 55302
> >
> > Hope this helps
> >
> > GregS <><
> >
> >
> > - Original Message -
> > From: "John R. Hogerhuis" 
> > To: m...@bitchin100.com
> > Sent: Sunday, January 27, 2019 12:03:56 AM
> > Subject: Re: [M100] Unable to Load TEENY to MT
> >
> > What did you try to "clear out" ts-dos?
> >
> > I don't think that beep has anything to do with TS-DOS. When a CO file
> > beeps on load, it's because the CLEAR statement is wrong. And if you
> typed
> > the CLEAR statement and it gave no error, then you have sufficient room
> to
> > run the utility.
> >
> > If it beeps anyway, maybe the program is running but just beeps. Who
> knows.
> >
> > Do me a favor, do the CLEAR statement, and LOADM"RF149.CO
> > from the BASIC prompt, not from the main menu and tell us what you see.
> >
> > If it prints out the CO file's header, we can figure out if
> >
> > a) The clear statement is right
> > b) The beep is coming as a BASIC load issue, or for some other reason.
> >
> > -- John.
> >
>
>

Re: [M100] Unable to Load TEENY to MT

[John R. Hogerhuis]

On Sun, Jan 27, 2019 at 1:48 PM Fugu ME100  wrote:

>
>-  Simply clearing a piece of RAM does not undo anything RAM TPDD
>might of done to various hooks, timers or buffers.
>
>
True, but that is what the DOS-ON/DOS-OFF command in TS-DOS does. It hooks
/ unhooks the BASIC extensions.

If it does not, it is a bug in TS-DOS. Which of course is possible, it
wouldn't be the first bug discovered.

-- John.

>

Re: [M100] Unable to Load TEENY to MT

[John R. Hogerhuis]

On Sun, Jan 27, 2019 at 1:46 PM Stephen Adolph  wrote:

> John, all I meant by conflict is if TSDOS in RAM (16k ish?) + my code(8k
> ish?) cause the M100 to run out of memory.
>

Ah. Well, TS-DOS didn't complain which is why it seems like there is enough
room.


> TSDOS is a lot of program to merely load one .CO.  But I really don't know
> specifically if everything can reside in RAM at the same time with a low
> CLEAR at 55000.
>

Totally true, but I think he would find out while running TS-DOS, and
trying to inload the CO. It should error out then because not enough space
to add to the file system.

If the file system grew so much that a low clear wouldn't work, there is a
question of whether BASIC would refuse the CLEAR command.

But the solution would be, delete TS-DOS after loading the CO into RAM file
system, but before doing the CLEAR.


> when himem is not set correctly, ... a .CO program beeps, of course, on
> failed start up.
>

Yes. BTW, why do you document a clear at 55,000 rather than at what TOP is
set to a few hundred bytes higher? Do you  use memory before your program?


>   I don't recall but I don't think that any of my routines beep.  they
> might.  I really don't remember ;)
>

 OK.

-- John

Re: [M100] Unable to Load TEENY to M1

[Greg Swallow]

I did get farther, even with TS-DOS loaded. Ran RF149.CO from MENU after the 
LOADM. It seem to start ok, but then nothing seemed to happen when left it half 
the night loading 0:RF149.BX. Maybe I should have let go all night.

God Bless,

GregS <><
- Original Message -
From: John R. Hogerhuis 
To: m...@bitchin100.com
Sent: Sun, 27 Jan 2019 05:37:32 -0500 (EST)
Subject: Re: [M100] Unable to Load TEENY to MT

But it gave no error...

I think it loaded. Meaning when you typed loadm it copied it's contents to
55302.

Not sure why the clear address is 55000. The program starts at 55302. Maybe
the program uses the gap as a scratchpad.

I'm guessing the beep is from the program itself. Maybe it's done or maybe
it's giving you an error.

-- John.


On Sun, Jan 27, 2019, 12:24 AM Greg Swallow  CLEAR0,55000: LOADM"RF149.CO" gives
>
> Top: 55302
> End: 60148
> Exe: 55302
>
> Hope this helps
>
> GregS <><
>
>
> - Original Message -
> From: "John R. Hogerhuis" 
> To: m...@bitchin100.com
> Sent: Sunday, January 27, 2019 12:03:56 AM
> Subject: Re: [M100] Unable to Load TEENY to MT
>
> What did you try to "clear out" ts-dos?
>
> I don't think that beep has anything to do with TS-DOS. When a CO file
> beeps on load, it's because the CLEAR statement is wrong. And if you typed
> the CLEAR statement and it gave no error, then you have sufficient room to
> run the utility.
>
> If it beeps anyway, maybe the program is running but just beeps. Who knows.
>
> Do me a favor, do the CLEAR statement, and LOADM"RF149.CO
> from the BASIC prompt, not from the main menu and tell us what you see.
>
> If it prints out the CO file's header, we can figure out if
>
> a) The clear statement is right
> b) The beep is coming as a BASIC load issue, or for some other reason.
>
> -- John.
>

Re: [M100] Unable to Load TEENY to MT

[Fugu ME100]

Just a couple of observations from programming a few REXs :)

  *   Even if the REX were dead RF149.co always seems to run to completion. I 
have run it with a few faulty REXs.  It will complete and be quite happy. Then 
when you try to perform the BASIC CALL it fails.  If the REX has failed then 
what happens is either the erasing part runs in a few seconds rather than 30s 
and the programming part will run quite quickly.  It will still download both 
ROM image files from the TPDD drive.  In fact it looks like it completes 
programming – but it does not.  Locking up trying to download the ROM images 
would indicate to me that it is having a problem loading the ROM images from 
the TPDD drive.  The RF149.co runs regardless of the state of the REX.  The 
only time this is not the case is if the REX is inserted backwards, but then 
the Model T locks up :)
  *   The fact RAM TPDD has been loaded and, I believe, inserts hooks in 
various places to me implies that it could conflict with the RF149.co internal 
DOS program, whereas TEENY I believe is quite clean in that respect.  I only 
know from bitter experience that when I was attempting to program a REX 
originally using RAM TPDD it would cause problems – including the beep.  
Whereas using TEENY caused no problems.  I can only conclude that RAM TPDD 
somehow conflicted with the REX programming using RF149.co.  Simply clearing a 
piece of RAM does not undo anything RAM TPDD might of done to various hooks, 
timers or buffers.

I think a cold boot followed by installing TEENY then downloading RF149.co will 
work.  Whether the REX is dead or not RF149.co will run to completion.  Only 
when you do the BASIC CALL do you find out if it is successful :-D  If it takes 
<2mins to program,  the REX is probably faulty, if it takes approx 5mins it is 
probably good.

From: M100 
mailto:m100-boun...@lists.bitchin100.com>> 
on behalf of "John R. Hogerhuis" mailto:jho...@pobox.com>>
Reply-To: mailto:m...@bitchin100.com>>
Date: Sunday, January 27, 2019 at 1:25 PM
To: mailto:m...@bitchin100.com>>
Subject: Re: [M100] Unable to Load TEENY to MT



On Sun, Jan 27, 2019 at 12:55 PM Fugu ME100 
mailto:b4me...@hotmail.com>> wrote:
The RAM TPDD is most likely conflicting with the the REX program.  The best 
method is to use TEENY to download the 
RF149.CO
 file.  I have never used the RAM TPPD to program a REX

Well.

TEENY is fine, and Steve says that's what he tested with, so I agree that's the 
best way to go.

But let me do my small part to prevent cargo cult misunderstandings though...

Saying TSDOS "conflicts" with 
rf149.co
 doesn't make any sense to me.

RAM based DOSes that aren't running don't conflict with other CO programs. If 
they did, there wouldn't be much point to them, because part of the point of a 
DOS is to be able to inload CO files, and then run them.

When a DOS inloads a CO program, it inloads it into the file system portion of 
RAM. If you don't have enough RAM to add the file to the RAM file system, the 
DOS will give you an error.

But that didn't happen... it loaded the CO into the file system. Note that the 
inload just places it in the file system. It doesn't run it. It doesn't copy 
the program to the place it needs to run. If it did, it might overwrite itself!

But it doesn't, because that's not how it works.

Then you exit the DOS, you enter a CLEAR statement if the file needs to run 
lower than whatever HIMEM is currently set to, likely because of a previous 
clear for other programs you run (like the DOS).

The program then launches and runs.

The one area you might say this is not true is that TS-DOS can be "hooked" into 
BASIC to add some extensions. Those extensions must be copied and run from 
somewhere, so it's possible they could conflict.

The most likely thing IMO is his REX is not making contact or it is faulty in 
some other way.

As you say the burn should complete in 5 minutes.

Steve does your program ever beep for any reason?

:-)

-- John.

-= Model T's Forever =-

Re: [M100] Unable to Load TEENY to MT

[Stephen Adolph]

John, all I meant by conflict is if TSDOS in RAM (16k ish?) + my code(8k
ish?) cause the M100 to run out of memory.  TSDOS is a lot of program to
merely load one .CO.  But I really don't know specifically if everything
can reside in RAM at the same time with a low CLEAR at 55000.

when himem is not set correctly, ... a .CO program beeps, of course, on
failed start up.  I don't recall but I don't think that any of my routines
beep.  they might.  I really don't remember ;)


On Sun, Jan 27, 2019 at 4:24 PM John R. Hogerhuis  wrote:

>
>
> On Sun, Jan 27, 2019 at 12:55 PM Fugu ME100  wrote:
>
>> The RAM TPDD is most likely conflicting with the the REX program.  The
>> best method is to use TEENY to download the RF149.CO file.  I have never
>> used the RAM TPPD to program a REX
>>
>
> Well.
>
> TEENY is fine, and Steve says that's what he tested with, so I agree
> that's the best way to go.
>
> But let me do my small part to prevent cargo cult misunderstandings
> though...
>
> Saying TSDOS "conflicts" with rf149.co doesn't make any sense to me.
>
> RAM based DOSes that aren't running don't conflict with other CO programs.
> If they did, there wouldn't be much point to them, because part of the
> point of a DOS is to be able to inload CO files, and then run them.
>
> When a DOS inloads a CO program, it inloads it into the file system
> portion of RAM. If you don't have enough RAM to add the file to the RAM
> file system, the DOS will give you an error.
>
> But that didn't happen... it loaded the CO into the file system. Note that
> the inload just places it in the file system. It doesn't run it. It doesn't
> copy the program to the place it needs to run. If it did, it might
> overwrite itself!
>
> But it doesn't, because that's not how it works.
>
> Then you exit the DOS, you enter a CLEAR statement if the file needs to
> run lower than whatever HIMEM is currently set to, likely because of a
> previous clear for other programs you run (like the DOS).
>
> The program then launches and runs.
>
> The one area you might say this is not true is that TS-DOS can be "hooked"
> into BASIC to add some extensions. Those extensions must be copied and run
> from somewhere, so it's possible they could conflict.
>
> The most likely thing IMO is his REX is not making contact or it is faulty
> in some other way.
>
> As you say the burn should complete in 5 minutes.
>
> Steve does your program ever beep for any reason?
>
> :-)
>
> -- John.
>
> -= Model T's Forever =-
>

Re: [M100] Unable to Load TEENY to MT

[Fugu ME100]

The RAM TPDD is most likely conflicting with the the REX program.  The best 
method is to use TEENY to download the RF149.CO file.  I have never used the 
RAM TPPD to program a REX.

Running the REX programmer to completion should only take around 5mins.  The 
erasing part takes about 20-30s then downloading the RF149.BR file takes a few 
minutes.  It will then load the tsd100.bx file – which takes a few more 
minutes.  A progress bar will show as they are downloaded.  Both of these files 
need to be on the TPDD drive.  The REX programmer will automatically load in 
the two ROM files.  RF149.co is fully self contained and does not require 
anything else to be loaded.

On Sun, Jan 27, 2019 at 3:06 PM Greg Swallow 
mailto:gswal...@mchsi.com>> wrote:
I thought that might be the case and tried running after the LOADM. it seemed 
to be working. It wiped the bank(s) and started loading 0:RF149.BX -- I think 
it was, but didn't indicate any progress after a few hours I stop it. Maybe I 
should've let it keep going. I'll be off work again Tuesday and give it a try, 
if I don't get a chance today. Spending time with in-laws today.

God Bless,

GregS <><

- Original Message -
From: John R. Hogerhuis mailto:jho...@pobox.com>>
To: m...@bitchin100.com
Sent: Sun, 27 Jan 2019 05:37:32 -0500 (EST)
Subject: Re: [M100] Unable to Load TEENY to MT

But it gave no error...

I think it loaded. Meaning when you typed loadm it copied it's contents to
55302.

Not sure why the clear address is 55000. The program starts at 55302. Maybe
the program uses the gap as a scratchpad.

I'm guessing the beep is from the program itself. Maybe it's done or maybe
it's giving you an error.

-- John.


On Sun, Jan 27, 2019, 12:24 AM Greg Swallow 
mailto:gswal...@mchsi.com> wrote:

> CLEAR0,55000: 
> LOADM"RF149.CO"
>  gives
>
> Top: 55302
> End: 60148
> Exe: 55302
>
> Hope this helps
>
> GregS <><
>
>
> - Original Message -
> From: "John R. Hogerhuis" mailto:jho...@pobox.com>>
> To: m...@bitchin100.com
> Sent: Sunday, January 27, 2019 12:03:56 AM
> Subject: Re: [M100] Unable to Load TEENY to MT
>
> What did you try to "clear out" ts-dos?
>
> I don't think that beep has anything to do with TS-DOS. When a CO file
> beeps on load, it's because the CLEAR statement is wrong. And if you typed
> the CLEAR statement and it gave no error, then you have sufficient room to
> run the utility.
>
> If it beeps anyway, maybe the program is running but just beeps. Who knows.
>
> Do me a favor, do the CLEAR statement, and 
> LOADM"RF149.CO
> from the BASIC prompt, not from the main menu and tell us what you see.
>
> If it prints out the CO file's header, we can figure out if
>
> a) The clear statement is right
> b) The beep is coming as a BASIC load issue, or for some other reason.
>
> -- John.
>

Re: [M100] Unable to Load TEENY to MT

[Stephen Adolph]

I really only ever use the following
* serial transfer of TEENY into the M100, to make teeny.co
* use Teeny.co to load RF149.co

..then run rf149.co

Are you getting the software from the bitchin100 website?

I have never used TS-DOS in RAM to load up and run RF149.CO.  I can't say
if there is any gotcha.

On Sun, Jan 27, 2019 at 3:06 PM Greg Swallow  wrote:

> I thought that might be the case and tried running after the LOADM. it
> seemed to be working. It wiped the bank(s) and started loading 0:RF149.BX
> -- I think it was, but didn't indicate any progress after a few hours I
> stop it. Maybe I should've let it keep going. I'll be off work again
> Tuesday and give it a try, if I don't get a chance today. Spending time
> with in-laws today.
>
> God Bless,
>
> GregS <><
>
> - Original Message -
> From: John R. Hogerhuis 
> To: m...@bitchin100.com
> Sent: Sun, 27 Jan 2019 05:37:32 -0500 (EST)
> Subject: Re: [M100] Unable to Load TEENY to MT
>
> But it gave no error...
>
> I think it loaded. Meaning when you typed loadm it copied it's contents to
> 55302.
>
> Not sure why the clear address is 55000. The program starts at 55302. Maybe
> the program uses the gap as a scratchpad.
>
> I'm guessing the beep is from the program itself. Maybe it's done or maybe
> it's giving you an error.
>
> -- John.
>
>
> On Sun, Jan 27, 2019, 12:24 AM Greg Swallow 
> > CLEAR0,55000: LOADM"RF149.CO" gives
> >
> > Top: 55302
> > End: 60148
> > Exe: 55302
> >
> > Hope this helps
> >
> > GregS <><
> >
> >
> > - Original Message -
> > From: "John R. Hogerhuis" 
> > To: m...@bitchin100.com
> > Sent: Sunday, January 27, 2019 12:03:56 AM
> > Subject: Re: [M100] Unable to Load TEENY to MT
> >
> > What did you try to "clear out" ts-dos?
> >
> > I don't think that beep has anything to do with TS-DOS. When a CO file
> > beeps on load, it's because the CLEAR statement is wrong. And if you
> typed
> > the CLEAR statement and it gave no error, then you have sufficient room
> to
> > run the utility.
> >
> > If it beeps anyway, maybe the program is running but just beeps. Who
> knows.
> >
> > Do me a favor, do the CLEAR statement, and LOADM"RF149.CO
> > from the BASIC prompt, not from the main menu and tell us what you see.
> >
> > If it prints out the CO file's header, we can figure out if
> >
> > a) The clear statement is right
> > b) The beep is coming as a BASIC load issue, or for some other reason.
> >
> > -- John.
> >
>
>

Re: [M100] Unable to Load TEENY to MT

[Greg Swallow]

I thought that might be the case and tried running after the LOADM. it seemed 
to be working. It wiped the bank(s) and started loading 0:RF149.BX -- I think 
it was, but didn't indicate any progress after a few hours I stop it. Maybe I 
should've let it keep going. I'll be off work again Tuesday and give it a try, 
if I don't get a chance today. Spending time with in-laws today.

God Bless,

GregS <><

- Original Message -
From: John R. Hogerhuis 
To: m...@bitchin100.com
Sent: Sun, 27 Jan 2019 05:37:32 -0500 (EST)
Subject: Re: [M100] Unable to Load TEENY to MT

But it gave no error...

I think it loaded. Meaning when you typed loadm it copied it's contents to
55302.

Not sure why the clear address is 55000. The program starts at 55302. Maybe
the program uses the gap as a scratchpad.

I'm guessing the beep is from the program itself. Maybe it's done or maybe
it's giving you an error.

-- John.


On Sun, Jan 27, 2019, 12:24 AM Greg Swallow  CLEAR0,55000: LOADM"RF149.CO" gives
>
> Top: 55302
> End: 60148
> Exe: 55302
>
> Hope this helps
>
> GregS <><
>
>
> - Original Message -
> From: "John R. Hogerhuis" 
> To: m...@bitchin100.com
> Sent: Sunday, January 27, 2019 12:03:56 AM
> Subject: Re: [M100] Unable to Load TEENY to MT
>
> What did you try to "clear out" ts-dos?
>
> I don't think that beep has anything to do with TS-DOS. When a CO file
> beeps on load, it's because the CLEAR statement is wrong. And if you typed
> the CLEAR statement and it gave no error, then you have sufficient room to
> run the utility.
>
> If it beeps anyway, maybe the program is running but just beeps. Who knows.
>
> Do me a favor, do the CLEAR statement, and LOADM"RF149.CO
> from the BASIC prompt, not from the main menu and tell us what you see.
>
> If it prints out the CO file's header, we can figure out if
>
> a) The clear statement is right
> b) The beep is coming as a BASIC load issue, or for some other reason.
>
> -- John.
>

Re: [M100] Brand new member

[Stephen Adolph]

hi, I'll contact you off list.  I have a REX I can ship. Steve


On Sun, Jan 27, 2019 at 3:01 PM Stephen Pereira <
stephen.m.pereira...@gmail.com> wrote:

> Hi Stephen,
>
> Thanks a million for your reply!
>
> Please put me on your list for the next time you make up some REX devices.
>
> Are you also the person who indicated there might be a CP/M REX coming out
> sometime?  If so, could you please briefly describe what it would entail?
> Should I wait for that instead of going for the “original”?
>
> Thanks very much for any information you can provide.  Also, any
> no-strings-attached estimate of waiting time would be appreciated.
>
> smp
> - - -
> Stephen Pereira
> Bedford, NH  03110
> KB1SXE
>
>
> On Jan 27, 2019, at 2:53 PM, Stephen Adolph  wrote:
>
> I still make them from time to time.  there are other options as well.
>
>
> On Sun, Jan 27, 2019 at 2:43 PM Stephen Pereira <
> stephen.m.pereira...@gmail.com> wrote:
>
>> Hi John, and thanks very much for the welcome.
>>
>> I get it:  “If possible, acquire a REX.”
>>
>> How do I go about that?  Does anyone on the list make them anymore, or
>> does anyone on the list have a stash of them, that they might like to sell
>> one?
>>
>> Please let me know ASAP!  I’m ready to purchase!
>>
>> I use a Macintosh MacBook Pro laptop as my computer, so on the laptop
>> side, I’ll need a drive emulator that will work on the latest Mac OS X
>> 10.14.3.
>>
>> Thanks again for your attention!
>>
>> smp
>> - - -
>> Stephen Pereira
>> Bedford, NH  03110
>> KB1SXE
>>
>>
>

Re: [M100] Brand new member

[Stephen Adolph]

I still make them from time to time.  there are other options as well.


On Sun, Jan 27, 2019 at 2:43 PM Stephen Pereira <
stephen.m.pereira...@gmail.com> wrote:

> Hi John, and thanks very much for the welcome.
>
> I get it:  “If possible, acquire a REX.”
>
> How do I go about that?  Does anyone on the list make them anymore, or
> does anyone on the list have a stash of them, that they might like to sell
> one?
>
> Please let me know ASAP!  I’m ready to purchase!
>
> I use a Macintosh MacBook Pro laptop as my computer, so on the laptop
> side, I’ll need a drive emulator that will work on the latest Mac OS X
> 10.14.3.
>
> Thanks again for your attention!
>
> smp
> - - -
> Stephen Pereira
> Bedford, NH  03110
> KB1SXE
>
>
> On Jan 27, 2019, at 1:40 PM, John R. Hogerhuis  wrote:
>
> Welcome Stephen!
>
> If possible acquire a REX. It will come with the best DOS, TSDOS in ROM.
>
> There is really only one type of rex available right now for 100/102.
>
> What kind of computer do you have? That will dictate the tpdd service to
> use.
>
> -- John.
>
>
> On Sun, Jan 27, 2019, 8:58 AM Stephen Pereira <
> stephen.m.pereira...@gmail.com wrote:
>
>> Hello folks,
>>
>> This past week, I became the proud owner of a Tandy Model 102 in
>> excellent shape - 32K RAM, and Multiplan in the Option Socket.
>>
>> For the past few days, I’ve been familiarizing myself with it.  I can
>> attach to a terminal emulator on my laptop, and I’ve been able to transfer
>> ASCII .BA files into the M102 as .DO files, load them into BASIC, and see
>> them go.  I am aware of both the Club 100 site and the Bitchin 100 site,
>> and I am trying my best to learn about what options might still be
>> available for extending my machine.
>>
>> Recently, while lurking here on the list, I saw the mention of something
>> called CPM REX that may actually be coming out soon?  Please tell me more!
>>
>> I am quite confused about the things I see, like Rex, Remem, Sardine,
>> NADS, and so many DOSs!
>>
>> Much of the information I’m seeing seems to be made for folks who already
>> know what’s going on, so It’s been difficult for me to tell what way I may
>> want to go - and of course if that device is actually still available any
>> more.
>>
>> So here’s my first call for help:  Can anyone point me to a concise
>> description of what system extensions are actually still available, and
>> what they do?  Also, if it may be best to wait a bit and simply go with
>> that CPM REX?  Thanks in advance.
>>
>> In the back of my mind, I wanted to try out machine language… I found
>> that one can transfer .CO files using XMODEM.  Yesterday, I spent time
>> pulling in a couple of the XMODEM.BA  programs from
>> the Club 100 Telecom Library, and got them each to go.  I then attached to
>> my terminal emulator that has XMODEM transfer capability and I thought that
>> I’d be all set, but no.  The first thing I tried was to transfer
>> XMODEM.CO  back up to my laptop, but when I gave the
>> file name to XMODEM, it abruptly cancelled the upload.  The same thing with
>> both of the XMODEM programs that I tried.  I was able to transfer ASCII
>> files using one of the other encodings, so I know that I had a good setup.
>> I’m not doing something right, but I cannot figure out what it might be.
>>
>> FYI, the two programs I pulled from the Club 100 Library were:  XMODEM.BA
>>  and XMDPW5.BA .  I was able to
>> transfer each of them into my system, and then run the .BA program to
>> create the .CO program.  then running the .CO program was wht gave me the
>> problem in both cases.
>>
>> Thanks in advance for any advice or pointers that you may have to offer!
>>
>> smp
>> - - -
>> Stephen Pereira
>> Bedford, NH  03110
>> KB1SXE
>>
>>
>>
>

Re: [M100] Brand new member

[Stephen Pereira]

Hi John, and thanks very much for the welcome.

I get it:  “If possible, acquire a REX.”  

How do I go about that?  Does anyone on the list make them anymore, or does 
anyone on the list have a stash of them, that they might like to sell one?

Please let me know ASAP!  I’m ready to purchase!

I use a Macintosh MacBook Pro laptop as my computer, so on the laptop side, 
I’ll need a drive emulator that will work on the latest Mac OS X 10.14.3.

Thanks again for your attention!

smp
- - -
Stephen Pereira
Bedford, NH  03110
KB1SXE


> On Jan 27, 2019, at 1:40 PM, John R. Hogerhuis  wrote:
> 
> Welcome Stephen!
> 
> If possible acquire a REX. It will come with the best DOS, TSDOS in ROM. 
> 
> There is really only one type of rex available right now for 100/102. 
> 
> What kind of computer do you have? That will dictate the tpdd service to use. 
> 
> -- John. 
> 
> 
> On Sun, Jan 27, 2019, 8:58 AM Stephen Pereira   wrote:
> Hello folks,
> 
> This past week, I became the proud owner of a Tandy Model 102 in excellent 
> shape - 32K RAM, and Multiplan in the Option Socket.
> 
> For the past few days, I’ve been familiarizing myself with it.  I can attach 
> to a terminal emulator on my laptop, and I’ve been able to transfer ASCII .BA 
> files into the M102 as .DO files, load them into BASIC, and see them go.  I 
> am aware of both the Club 100 site and the Bitchin 100 site, and I am trying 
> my best to learn about what options might still be available for extending my 
> machine.
> 
> Recently, while lurking here on the list, I saw the mention of something 
> called CPM REX that may actually be coming out soon?  Please tell me more!
> 
> I am quite confused about the things I see, like Rex, Remem, Sardine, NADS, 
> and so many DOSs!
> 
> Much of the information I’m seeing seems to be made for folks who already 
> know what’s going on, so It’s been difficult for me to tell what way I may 
> want to go - and of course if that device is actually still available any 
> more.
> 
> So here’s my first call for help:  Can anyone point me to a concise 
> description of what system extensions are actually still available, and what 
> they do?  Also, if it may be best to wait a bit and simply go with that CPM 
> REX?  Thanks in advance.
> 
> In the back of my mind, I wanted to try out machine language… I found that 
> one can transfer .CO files using XMODEM.  Yesterday, I spent time pulling in 
> a couple of the XMODEM.BA  programs from the Club 100 
> Telecom Library, and got them each to go.  I then attached to my terminal 
> emulator that has XMODEM transfer capability and I thought that I’d be all 
> set, but no.  The first thing I tried was to transfer XMODEM.CO 
>  back up to my laptop, but when I gave the file name to 
> XMODEM, it abruptly cancelled the upload.  The same thing with both of the 
> XMODEM programs that I tried.  I was able to transfer ASCII files using one 
> of the other encodings, so I know that I had a good setup.  I’m not doing 
> something right, but I cannot figure out what it might be.
> 
> FYI, the two programs I pulled from the Club 100 Library were:  XMODEM.BA 
>  and XMDPW5.BA .  I was able to 
> transfer each of them into my system, and then run the .BA program to create 
> the .CO program.  then running the .CO program was wht gave me the problem in 
> both cases.
> 
> Thanks in advance for any advice or pointers that you may have to offer!
> 
> smp
> - - -
> Stephen Pereira
> Bedford, NH  03110
> KB1SXE
> 
> 

Re: [M100] Need a m102/200 please

[Lee Kelley]

And I have a m200 I could part with.

On Sun, Jan 27, 2019 at 1:21 PM Anthony Coghlan  wrote:

> Kevin, is that Bern, PA, or Switzerland (beautiful place, but quite a bit
> farther from Northern Virginia)?
>
> Welcome to the group.  You’ll find guidance and answers to just about
> everything Mxxx related here.
>
> I have a Model 100 with 24KB, in great condition.  You’d have to clean the
> sides of the keys a little - literally, just about the only thing I can
> find.  The backup battery and capacitors inside look great also - common
> problems with these machines after time.  The backup battery definitely
> works and has no corrosion leakage.  I need to reduce my collection (have
> working M100, 102, 200, PC-2, Model 4 and CoCo 3).  I’d toss in a “parts”
> M100 also.  Perhaps you can get the parts machine working as well or just
> scavenge parts from it as needed for projects.
>
> Send me a note to my personal mail (coghl...@gmail.com) if interested.
> Price negotiable but certainly reasonable.  You’d be doing me a favor and
> I’d be happy to see an excellent machine go to a good home.  Otherwise I
> may list on Craigslist or eBay also, to see it out the door.
>
> Best wishes,
> Anthony
>
>
>
> On Sunday, January 27, 2019, Kevin Lee  wrote:
>
>> I used to have a m102 when I was a kid.
>> Sorely miss it. Current Im rebuilding a model 3/4 and a coco 3.
>>
>> However I would be appreciative if someone who had a surplus 102/200
>> In good working order to sell me one.
>>
>> I’ve looked all over and yeah flea bay
>> Came to mind. However I feel it’s better getting it from the crowd that
>> loves it the most.
>>
>> I have a small and growing retro collection. And the m102/200 would come
>> in very handy for my travels and daily life
>>
>> Cheers everyone
>> Kevin in Bern
>>
>> Ps. More then happy to pay courier postage from anywhere.
>>
>>
>>

-- 
*"I will never in my lifetime make a film that cannot be seen by the whole
family"*  Arther P. Jacobs

Re: [M100] Need a m102/200 please

[Anthony Coghlan]

Kevin, is that Bern, PA, or Switzerland (beautiful place, but quite a bit
farther from Northern Virginia)?

Welcome to the group.  You’ll find guidance and answers to just about
everything Mxxx related here.

I have a Model 100 with 24KB, in great condition.  You’d have to clean the
sides of the keys a little - literally, just about the only thing I can
find.  The backup battery and capacitors inside look great also - common
problems with these machines after time.  The backup battery definitely
works and has no corrosion leakage.  I need to reduce my collection (have
working M100, 102, 200, PC-2, Model 4 and CoCo 3).  I’d toss in a “parts”
M100 also.  Perhaps you can get the parts machine working as well or just
scavenge parts from it as needed for projects.

Send me a note to my personal mail (coghl...@gmail.com) if interested.
Price negotiable but certainly reasonable.  You’d be doing me a favor and
I’d be happy to see an excellent machine go to a good home.  Otherwise I
may list on Craigslist or eBay also, to see it out the door.

Best wishes,
Anthony



On Sunday, January 27, 2019, Kevin Lee  wrote:

> I used to have a m102 when I was a kid.
> Sorely miss it. Current Im rebuilding a model 3/4 and a coco 3.
>
> However I would be appreciative if someone who had a surplus 102/200
> In good working order to sell me one.
>
> I’ve looked all over and yeah flea bay
> Came to mind. However I feel it’s better getting it from the crowd that
> loves it the most.
>
> I have a small and growing retro collection. And the m102/200 would come
> in very handy for my travels and daily life
>
> Cheers everyone
> Kevin in Bern
>
> Ps. More then happy to pay courier postage from anywhere.
>
>
>

Re: [M100] Brand new member

[John R. Hogerhuis]

Welcome Stephen!

If possible acquire a REX. It will come with the best DOS, TSDOS in ROM.

There is really only one type of rex available right now for 100/102.

What kind of computer do you have? That will dictate the tpdd service to
use.

-- John.


On Sun, Jan 27, 2019, 8:58 AM Stephen Pereira <
stephen.m.pereira...@gmail.com wrote:

> Hello folks,
>
> This past week, I became the proud owner of a Tandy Model 102 in excellent
> shape - 32K RAM, and Multiplan in the Option Socket.
>
> For the past few days, I’ve been familiarizing myself with it.  I can
> attach to a terminal emulator on my laptop, and I’ve been able to transfer
> ASCII .BA files into the M102 as .DO files, load them into BASIC, and see
> them go.  I am aware of both the Club 100 site and the Bitchin 100 site,
> and I am trying my best to learn about what options might still be
> available for extending my machine.
>
> Recently, while lurking here on the list, I saw the mention of something
> called CPM REX that may actually be coming out soon?  Please tell me more!
>
> I am quite confused about the things I see, like Rex, Remem, Sardine,
> NADS, and so many DOSs!
>
> Much of the information I’m seeing seems to be made for folks who already
> know what’s going on, so It’s been difficult for me to tell what way I may
> want to go - and of course if that device is actually still available any
> more.
>
> So here’s my first call for help:  Can anyone point me to a concise
> description of what system extensions are actually still available, and
> what they do?  Also, if it may be best to wait a bit and simply go with
> that CPM REX?  Thanks in advance.
>
> In the back of my mind, I wanted to try out machine language… I found that
> one can transfer .CO files using XMODEM.  Yesterday, I spent time pulling
> in a couple of the XMODEM.BA programs from the Club 100 Telecom Library,
> and got them each to go.  I then attached to my terminal emulator that has
> XMODEM transfer capability and I thought that I’d be all set, but no.  The
> first thing I tried was to transfer XMODEM.CO back up to my laptop, but
> when I gave the file name to XMODEM, it abruptly cancelled the upload.  The
> same thing with both of the XMODEM programs that I tried.  I was able to
> transfer ASCII files using one of the other encodings, so I know that I had
> a good setup.  I’m not doing something right, but I cannot figure out what
> it might be.
>
> FYI, the two programs I pulled from the Club 100 Library were:  XMODEM.BA
> and XMDPW5.BA.  I was able to transfer each of them into my system, and
> then run the .BA program to create the .CO program.  then running the .CO
> program was wht gave me the problem in both cases.
>
> Thanks in advance for any advice or pointers that you may have to offer!
>
> smp
> - - -
> Stephen Pereira
> Bedford, NH  03110
> KB1SXE
>
>
>

[M100] Need a m102/200 please

[Kevin Lee]

I used to have a m102 when I was a kid. 
Sorely miss it. Current Im rebuilding a model 3/4 and a coco 3.  

However I would be appreciative if someone who had a surplus 102/200
In good working order to sell me one. 

I’ve looked all over and yeah flea bay
Came to mind. However I feel it’s better getting it from the crowd that loves 
it the most.  

I have a small and growing retro collection. And the m102/200 would come in 
very handy for my travels and daily life 

Cheers everyone 
Kevin in Bern 

Ps. More then happy to pay courier postage from anywhere. 

Re: [M100] REX in a sub-standard machine

[Stephen Adolph]

Classic REX does not have any RAM on it, and it is plug and play meaning
there is no hardware /WR signal which is needed for RAM to work.

So, yes, a REX enabled machine with limited RAM is still a machine with
limited RAM.  No shortcoming of REX there.
In fact adding REX to any machine brings all the same benefits.  Adding RAM
to the full extent provides those benefits.  They are independent.

That was partly my motivation for QUAD, but that is a separate story.

All it means is - you need to upgrade your RAM, to enjoy the benefits of
more RAM.

There is a soon to be released all RAM REX - called REXCPM.
The purpose here is to obviously run CPM on M100/T102, but it has a side
benefit of doing a full RAM upgrade.
(another reason to not stress so much about QUAD).

REXCPM has 2MB of SRAM.  It is based on bank switching like REX, but it
also replaces the internal SRAM.  So,  you can map any 32k block of SRAM
into the optrom space, and you can switch any 16k block into each of the
two upper ram 16k blocks.
This arrangement can be used to implement all the functions of REX but it
also delivers the key thing needed for CP/M, that being the ability to use
RAM blocks as a RAM DISK.

In M100, REXCPM is plug and play, using the system bus connector and the
Optrom socket.
In T102, REXCPM needs a small hardware change, and uses the 4th memory chip
socket and the Optrom socket.





On Fri, Jan 25, 2019 at 4:56 PM Jan Vanden Bossche 
wrote:

> Yes, I think so.
>
> But that also means I had the concept wrong. I thought that the
> RAM-switching was done ON the REX, and that the live RAM was on the REX. If
> I understand it now - sorry I'm slow - the RAM-image is copied into the
> live RAM of the machine.
>
> But, that also mean that, in order to be able to take full advantage of
> REX, you do need a 32KB machine, or upgrade to it.
>
> Sad if you happen to find an 8KB Model 100, or a 24 KB Model 102... :-/
>
> Greetings from the TyRannoSaurus
> Jan-80
>
>

Re: [M100] Unable to Load TEENY to MT

[John R. Hogerhuis]

But it gave no error...

I think it loaded. Meaning when you typed loadm it copied it's contents to
55302.

Not sure why the clear address is 55000. The program starts at 55302. Maybe
the program uses the gap as a scratchpad.

I'm guessing the beep is from the program itself. Maybe it's done or maybe
it's giving you an error.

-- John.


On Sun, Jan 27, 2019, 12:24 AM Greg Swallow  CLEAR0,55000: LOADM"RF149.CO" gives
>
> Top: 55302
> End: 60148
> Exe: 55302
>
> Hope this helps
>
> GregS <><
>
>
> - Original Message -
> From: "John R. Hogerhuis" 
> To: m...@bitchin100.com
> Sent: Sunday, January 27, 2019 12:03:56 AM
> Subject: Re: [M100] Unable to Load TEENY to MT
>
> What did you try to "clear out" ts-dos?
>
> I don't think that beep has anything to do with TS-DOS. When a CO file
> beeps on load, it's because the CLEAR statement is wrong. And if you typed
> the CLEAR statement and it gave no error, then you have sufficient room to
> run the utility.
>
> If it beeps anyway, maybe the program is running but just beeps. Who knows.
>
> Do me a favor, do the CLEAR statement, and LOADM"RF149.CO
> from the BASIC prompt, not from the main menu and tell us what you see.
>
> If it prints out the CO file's header, we can figure out if
>
> a) The clear statement is right
> b) The beep is coming as a BASIC load issue, or for some other reason.
>
> -- John.
>

Re: [M100] Unable to Load TEENY to MT

[Greg Swallow]

CLEAR0,55000: LOADM"RF149.CO" gives

Top: 55302
End: 60148
Exe: 55302

Hope this helps

GregS <><


- Original Message -
From: "John R. Hogerhuis" 
To: m...@bitchin100.com
Sent: Sunday, January 27, 2019 12:03:56 AM
Subject: Re: [M100] Unable to Load TEENY to MT

What did you try to "clear out" ts-dos?

I don't think that beep has anything to do with TS-DOS. When a CO file
beeps on load, it's because the CLEAR statement is wrong. And if you typed
the CLEAR statement and it gave no error, then you have sufficient room to
run the utility.

If it beeps anyway, maybe the program is running but just beeps. Who knows.

Do me a favor, do the CLEAR statement, and LOADM"RF149.CO
from the BASIC prompt, not from the main menu and tell us what you see.

If it prints out the CO file's header, we can figure out if

a) The clear statement is right
b) The beep is coming as a BASIC load issue, or for some other reason.

-- John.