Re: [M100] BackPack - read data from CLI

[Georg Käter]

Jeff,

 

trying to get data from BackPack after sending a "set" via PRINT#1 from BASIC ends always with a 'T'.

Do you have a sample code to enter CLI mode and get data via PRINT/INPUT sequence from BASIC?

I would like to read 1st "DATE format" set in BackPack for a program to cover all Date format in the

M100 family - YY/MM/DD for NECs, MM/DD/YY or DD/MM/YY pending US or international variant.

 

Thanks for your help

Georg

 
 

Gesendet: Freitag, 03. März 2023 um 01:08 Uhr
Von: bir...@soigeneris.com
An: "'Georg Käter'" 
Betreff: RE: Re: [M100] BackPack - read data from CLI




Georg,

 

My first replay to you was incomplete. When you send four CR (carriage return) to the Backpack it will respond with a symbol followed by CR.

‘C’ CR

‘#’ CR

 

When it times out it sends:

 

‘T’ CR

 

Jeff Birt

 



From: Georg Käter 
Sent: Thursday, March 2, 2023 12:24 AM
To: m...@bitchin100.com
Cc: bir...@soigeneris.com
Subject: Aw: Re: [M100] BackPack - read data from CLI



 



Hi Jeff,



 



I´ve added the following to the listing below to "see" if BPD responds



 



..



42 INPUT#2,K
43 IF K<>"#" GOTO 42



44 PRINT K



..
 




After some seconds I see the #, but program then program stucks.



Any further idea about this behaviour?



 



Thanks for your support



Georg



  



Gesendet: Mittwoch, 01. März 2023 um 14:47 Uhr
Von: bir...@soigeneris.com
An: m...@bitchin100.com
Betreff: Re: [M100] BackPack - read data from CLI





You might be sending the SET command before the BPD has time to wake up and respond. It will return a ‘#’ when it wakes up and switches to CLI mode.

 

Jeff Birt

 



From: M100 <m100-boun...@lists.bitchin100.com> On Behalf Of Georg Käter
Sent: Wednesday, March 1, 2023 12:59 AM
To: m...@bitchin100.com
Subject: [M100] BackPack - read data from CLI



 



Hello together,



 



I tried to read "settings" from a BackPack+ with the following, but w/o success



 



10 REM read settings from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM turn-on CLI mode
41 PRINT#1,STRING$(4,13)
50 REM send "set" command to BackPack/BackPack+
51 PRINT#1,"set";CHR$(13)
60 REM read data from BackPack (set returns 9? values)
61 INPUT#2,A,B,C,D,E,F,G,H,I
70 REM show "settings"
71 PRINT A,B,C,D,E,F,G,H,I
80 REM turn-off CLI mode
81 PRINT#1,"bye"
99 END



 



What is wrong in the above? Any idea?



 



btw this works:




10 REM read data from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM read from BackPack/BackPack+ (Date=A, Time=B, Day=C)
41 PRINT#1,"FF";chr$(7);chr$(13)
42 INPUT#2,A,B,C
50 REM print values
51 PRINT A,B,C
99 END



 



Thanks for your help

Re: [M100] - Backpack

[Fisher]

He’s got the t-shirt. We’ve all got the t-shirt! :D



> On Mar 3, 2023, at 3:07 PM, John R. Hogerhuis  wrote:
> 
> You can hook it but the dinner bell is a non maskable interrupt where I live, 
> no kidding. 
> 
> -- John. 
> 
> On Fri, Mar 3, 2023, 10:30 AM Joshua O'Keefe  > wrote:
> > On Mar 2, 2023, at 3:45 PM, John R. Hogerhuis  > > wrote:
> > The dinner bell interrupts you.
> 
> Is there a vector I can hook a routine to?  I have a ton of code I'd love to 
> run at interrupt if it won't disrupt the dinner timing itself.

Re: [M100] - Backpack

[John R. Hogerhuis]

You can hook it but the dinner bell is a non maskable interrupt where I
live, no kidding.

-- John.

On Fri, Mar 3, 2023, 10:30 AM Joshua O'Keefe 
wrote:

> > On Mar 2, 2023, at 3:45 PM, John R. Hogerhuis  wrote:
> > The dinner bell interrupts you.
>
> Is there a vector I can hook a routine to?  I have a ton of code I'd love
> to run at interrupt if it won't disrupt the dinner timing itself.

Re: [M100] - Backpack

[Joshua O'Keefe]

> On Mar 2, 2023, at 3:45 PM, John R. Hogerhuis  wrote:
> The dinner bell interrupts you.

Is there a vector I can hook a routine to?  I have a ton of code I'd love to 
run at interrupt if it won't disrupt the dinner timing itself.

Re: [M100] - Backpack

[John R. Hogerhuis]

On Fri, Mar 3, 2023 at 4:02 AM Francois Gurin  wrote:

>
>
> On Thu, Mar 2, 2023, 6:45 PM John R. Hogerhuis  wrote:
>
>> Tap the machine 3 times, proclaim "no whammies!," sacrifice a chicken and
>> move on.
>>
>
>
> Does where you tap affect the outcome? What about how hard.
>
>
It's not critical. But feel free to knock 4 or 5 times if the spirit moves.


> My accent is a little thick but I don't expect an issue unless this is a
> sensitive step.
>
>
If the family can hear you well, it's loud enough. It's really about
attracting helpful spirits. If you're not loud enough, they cannot aid you.


> I am most concerned about the chicken -- I only have ready access to live
> pigeons and pre-butchered chicken.  Any experience with more readily
> available substitutions in the city?
>
>
Between you and me, in a pinch, I've been known to toss a piece of deli
meat or unheated hot dog on the floor, business side down.

Go with what you got.

-- John.

Re: [M100] - Backpack ...[The dinner bell interrupt]

[John R. Hogerhuis]

On Fri, Mar 3, 2023, 5:56 AM Fisher  wrote:

>
> The dinner bell interrupt: when you switch-off the memory backup
> power and give it an hour or so (to digest the chicken.)
>

Exactly! The deities need the chicken. But a experience user will throw in
a cold start for good measure.

"Death therapy, Bob. It's a guaranteed cure!"

-- John.

>

Re: [M100] - Backpack ...[The dinner bell interrupt]

[Fisher]

The dinner bell interrupt: when you switch-off the memory backup power 
and give it an hour or so (to digest the chicken.)




> No.. TS-DOS never got away with it, really.
> 
> The dysfunction created is insidious. The immediate thing the user may see is 
> that the file inloaded is corrupted. Oh well, you mess around and try again. 
> Maybe you fix the extension. Maybe you don't. The dinner bell interrupts you.
> 
> You pick it up later. But little do you realize the stage is set for 
> crash/hang/data loss. At this point the RAM in general is corrupted with 
> weird effects and eventually you will have to "cold start" to fully recover.
> 
> The disconnect will result in making up theories of what happened. Sunspots. 
> Some new CO you used the other day. Maybe an errant poke in Joe's program 
> that you were testing for him. Maybe you blame Microsoft.
> 
> So I suspect TS-DOS + Desklink avoided blame because users don't always know 
> when or why exactly things go wrong.
> 
> Or, it got away with it because fundamentally, all said and done, it's truly 
> the user's fault for not following the official naming conventions (which 
> they may or may not understand. Tokenization? Plain text? BASIC ASCII? 
> Tokenized BASIC? Inload? etc).
> 
> Tap the machine 3 times, proclaim "no whammies!," sacrifice a chicken and 
> move on.
> 
> -- John.

Re: [M100] - Backpack

[Francois Gurin]

On Thu, Mar 2, 2023, 6:45 PM John R. Hogerhuis  wrote:

> Tap the machine 3 times, proclaim "no whammies!," sacrifice a chicken and
> move on.
>


Does where you tap affect the outcome? What about how hard.

My accent is a little thick but I don't expect an issue unless this is a
sensitive step.

I am most concerned about the chicken -- I only have ready access to live
pigeons and pre-butchered chicken.  Any experience with more readily
available substitutions in the city?

Couldn't resist
-fg

Re: [M100] - Backpack

[Gary Weber]

John,

You have described the issues and the resulting frustration quite
accurately, and in the most entertaining method I've witnessed to date.
Bravo!

Gary

On Thu, Mar 2, 2023 at 4:45 PM John R. Hogerhuis  wrote:

>
>
> On Thu, Mar 2, 2023 at 3:29 PM  wrote:
>
>> Regarding Jeff’s comment:  “TSDOS does its own thing, like John says, and
>> really makes a mess of it.”:
>>
>>
>>
>> Could it be that TSDOS got away with it due to inherent delays in reading
>> data from a disk?   Reading from an SD card should be much faster and not
>> have those delays.Just speculating…
>>
>>
>>
>
> No.. TS-DOS never got away with it, really.
>
> The dysfunction created is insidious. The immediate thing the user may see
> is that the file inloaded is corrupted. Oh well, you mess around and try
> again. Maybe you fix the extension. Maybe you don't. The dinner bell
> interrupts you.
>
> You pick it up later. But little do you realize the stage is set for
> crash/hang/data loss. At this point the RAM in general is corrupted with
> weird effects and eventually you will have to "cold start" to fully recover.
>
> The disconnect will result in making up theories of what happened.
> Sunspots. Some new CO you used the other day. Maybe an errant poke in Joe's
> program that you were testing for him. Maybe you blame Microsoft.
>
> So I suspect TS-DOS + Desklink avoided blame because users don't always
> know when or why exactly things go wrong.
>
> Or, it got away with it because fundamentally, all said and done, it's
> truly the user's fault for not following the official naming conventions
> (which they may or may not understand. Tokenization? Plain text? BASIC
> ASCII? Tokenized BASIC? Inload? etc).
>
> Tap the machine 3 times, proclaim "no whammies!," sacrifice a chicken and
> move on.
>
> -- John.
>

Re: [M100] - Backpack

[MikeS]

I wondered how you discriminated; clever!
  - Original Message - 
  From: John R. Hogerhuis 
  To: m...@bitchin100.com 
  Sent: Thursday, March 02, 2023 1:20 PM
  Subject: Re: [M100] - Backpack


  "you would only have tokenized files on the M100 itself"


  Or cassette files, tpdd files, xmodem'd BA files tsdos sending to desklink, 
etc. ;-)


  But I think I know what you mean. It is mostly a closed system until you 
start transferring to a foreign host. Then you can stub your toe on this 
problem.


  One question is, could it have been solved on the tsdos side? I guess not.  
IIRC the distinguishing characteristics are at the end of a proper tokenized 
file versus text file since there are nuls (or not). 


  If you're going to detect it and take steps it has to happen on the host. 


  Which is where I addressed it in LaddieAlpha. 


  Even there, there are multiple ways to do it. I fix the presented extension. 
Another way would be to hide the bad file or give an error on open or read. 


  -- John. 

Re: [M100] - Backpack

[John R. Hogerhuis]

On Thu, Mar 2, 2023 at 3:29 PM  wrote:

> Regarding Jeff’s comment:  “TSDOS does its own thing, like John says, and
> really makes a mess of it.”:
>
>
>
> Could it be that TSDOS got away with it due to inherent delays in reading
> data from a disk?   Reading from an SD card should be much faster and not
> have those delays.Just speculating…
>
>
>

No.. TS-DOS never got away with it, really.

The dysfunction created is insidious. The immediate thing the user may see
is that the file inloaded is corrupted. Oh well, you mess around and try
again. Maybe you fix the extension. Maybe you don't. The dinner bell
interrupts you.

You pick it up later. But little do you realize the stage is set for
crash/hang/data loss. At this point the RAM in general is corrupted with
weird effects and eventually you will have to "cold start" to fully recover.

The disconnect will result in making up theories of what happened.
Sunspots. Some new CO you used the other day. Maybe an errant poke in Joe's
program that you were testing for him. Maybe you blame Microsoft.

So I suspect TS-DOS + Desklink avoided blame because users don't always
know when or why exactly things go wrong.

Or, it got away with it because fundamentally, all said and done, it's
truly the user's fault for not following the official naming conventions
(which they may or may not understand. Tokenization? Plain text? BASIC
ASCII? Tokenized BASIC? Inload? etc).

Tap the machine 3 times, proclaim "no whammies!," sacrifice a chicken and
move on.

-- John.

Re: [M100] - Backpack

[lloydelmer]

Regarding Jeff’s comment:  “TSDOS does its own thing, like John says, and 
really makes a mess of it.”:

 

Could it be that TSDOS got away with it due to inherent delays in reading data 
from a disk?   Reading from an SD card should be much faster and not have those 
delays.Just speculating…

 

Lloyd

 

 

From: M100  On Behalf Of Peter Vollan
Sent: Wednesday, March 1, 2023 2:13 PM
To: m...@bitchin100.com
Subject: Re: [M100] - Backpack

 

See, I take the unpopular opinion that that should not be done because it 
teaches bad habits.

 

On Wed, 1 Mar 2023 at 06:20, mailto:bir...@soigeneris.com> > wrote:

I also tried loading a .DO named as .BA through BASIC, i.e. load "com:98n1e" 
and that worked fine. Seems to me that if it were a man ROM issue the same 
problem would happen this way. Also, the TS-DOS disassembly shows that it 
changes it’s behavior based on filetype extension.

 

Jeff Birt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Brian White
Sent: Wednesday, March 1, 2023 6:51 AM
To: m...@bitchin100.com <mailto:m...@bitchin100.com> 
Subject: Re: [M100] - Backpack

 

I don't think it's ts-dos, it's the main rom. The main rom and all the tpdd 
clients basically have to trust the file name. If it's declared as a .ba, then 
the bytes are copied verbatim and then later interpreted according to the rules 
of parsing a .ba. If the contents are not .ba, kablooey.

bkw

 

On Tue, Feb 28, 2023, 8:11 PM mailto:bir...@soigeneris.com> > wrote:

I did some more testing and discovered that John is absolutely correct. 
Previously when I had tried to load a .BA which was really a .DO it made it 
about 3-4 line in and then stopped. This led me to believe it was an issue I 
have seen on other computer; when loading an ASCII file over serial the 
computer will tokenize the line when the CR is encountered. Just like it had 
been typed in on the keyboard. For these systems you have to add a 2 second or 
so delay after each line to allow for tokenization.

TSDOS does its own thing, like John says, and really makes a mess of it. 

 

Jeff Birt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of John R. Hogerhuis
Sent: Saturday, February 25, 2023 7:40 PM
To: m...@bitchin100.com <mailto:m...@bitchin100.com> 
Subject: Re: [M100] - Backpack

 

A side note but the reason files misnamed as BA cause a problem is that tsdos 
will load them into the BASIC program region verbatim and  treat the ASCII 
bytes as parts of binary formatted line numbers and tokens among other 
problems, ultimately causing a corrupted RAM file system. 

 

It was the convention on the old Club100 library  to name them this way but 
it's now a bad practice. 

 

-- John. 

 

 

 

On Sat, Feb 25, 2023, 5:30 PM mailto:bir...@soigeneris.com> > wrote:

Yes, someone already wrote such a program and shared it. If you just got a 
Backpack Drive Plus it is already on the SD card. You can also download it 
from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs 

 

Re: [M100] - Backpack

[MikeS]

Well, I count a cassette or TPDD (or the DVI for that matter) as part of the 
stock 'closed' M100 system, with  TELCOM only able to transfer plaintext files 
in and out; xmodem and DLplus changed that and that's where the trouble started.

Back in the day it was never an issue; everything was ASCII text except for the 
.BA programs running or stored in the M100 system.

When I dug out my M100 many years later, lo and behold there were now lots of 
binary .CO and .BA files out there, but how to load them into the M100? Xmodem 
was one obvious answer, but how to load it in the first place? 

So, many thanks to Ron Wiesen (R.I.P.) and Traveling Software for the 
self-installing TEENY and DeskLink combo; that opened the door to lots of other 
stuff including TS-DOS etc.

A quite different environment these days thanks to all the innovative folks 
who've contributed over the last 40 years...

m


  - Original Message - 
  From: John R. Hogerhuis 
  To: m...@bitchin100.com 
  Sent: Thursday, March 02, 2023 1:20 PM
  Subject: Re: [M100] - Backpack


  "you would only have tokenized files on the M100 itself"


  Or cassette files, tpdd files, xmodem'd BA files tsdos sending to desklink, 
etc. ;-)


  But I think I know what you mean. It is mostly a closed system until you 
start transferring to a foreign host. Then you can stub your toe on this 
problem.


  One question is, could it have been solved on the tsdos side? I guess not.  
IIRC the distinguishing characteristics are at the end of a proper tokenized 
file versus text file since there are nuls (or not). 


  If you're going to detect it and take steps it has to happen on the host. 


  Which is where I addressed it in LaddieAlpha. 


  Even there, there are multiple ways to do it. I fix the presented extension. 
Another way would be to hide the bad file or give an error on open or read. 


  -- John. 

Re: [M100] - Backpack

[John R. Hogerhuis]

"you would only have tokenized files on the M100 itself"

Or cassette files, tpdd files, xmodem'd BA files tsdos sending to desklink,
etc. ;-)

But I think I know what you mean. It is mostly a closed system until you
start transferring to a foreign host. Then you can stub your toe on this
problem.

One question is, could it have been solved on the tsdos side? I guess not.
IIRC the distinguishing characteristics are at the end of a proper
tokenized file versus text file since there are nuls (or not).

If you're going to detect it and take steps it has to happen on the host.

Which is where I addressed it in LaddieAlpha.

Even there, there are multiple ways to do it. I fix the presented
extension. Another way would be to hide the bad file or give an error on
open or read.

-- John.

Re: [M100] - Backpack

[Mike Stein]

Not sure what you mean? What's the bad habit?

The idea of using .BA for plaintext BASIC files and .DO for text documents
made perfect sense in the old days. Keep in mind that a stock M100 can not
transfer binary files such as tokenized BASIC or .CO, so normally all files
transferred would be plain ASCII and you would only have tokenized files on
the M100 itself.

The problem being discussed only arose once various means of transferring
binary files without discriminating between binary and plaintext came along.

m

On Wed, Mar 1, 2023 at 3:29 PM Peter Vollan  wrote:

> See, I take the unpopular opinion that that should not be done because it
> teaches bad habits.
>
> On Wed, 1 Mar 2023 at 06:20,  wrote:
>
>> I also tried loading a .DO named as .BA through BASIC, i.e. load
>> "com:98n1e" and that worked fine. Seems to me that if it were a man ROM
>> issue the same problem would happen this way. Also, the TS-DOS disassembly
>> shows that it changes it’s behavior based on filetype extension.
>>
>>
>>
>> Jeff Birt
>>
>>
>>
>> *From:* M100  *On Behalf Of *Brian
>> White
>> *Sent:* Wednesday, March 1, 2023 6:51 AM
>> *To:* m...@bitchin100.com
>> *Subject:* Re: [M100] - Backpack
>>
>>
>>
>> I don't think it's ts-dos, it's the main rom. The main rom and all the
>> tpdd clients basically have to trust the file name. If it's declared as a
>> .ba, then the bytes are copied verbatim and then later interpreted
>> according to the rules of parsing a .ba. If the contents are not .ba,
>> kablooey.
>>
>> bkw
>>
>>
>>
>> On Tue, Feb 28, 2023, 8:11 PM  wrote:
>>
>> I did some more testing and discovered that John is absolutely correct.
>> Previously when I had tried to load a .BA which was really a .DO it made it
>> about 3-4 line in and then stopped. This led me to believe it was an issue
>> I have seen on other computer; when loading an ASCII file over serial the
>> computer will tokenize the line when the CR is encountered. Just like it
>> had been typed in on the keyboard. For these systems you have to add a 2
>> second or so delay after each line to allow for tokenization.
>>
>> TSDOS does its own thing, like John says, and really makes a mess of it.
>>
>>
>>
>> Jeff Birt
>>
>>
>>
>> *From:* M100  *On Behalf Of *John R.
>> Hogerhuis
>> *Sent:* Saturday, February 25, 2023 7:40 PM
>> *To:* m...@bitchin100.com
>> *Subject:* Re: [M100] - Backpack
>>
>>
>>
>> A side note but the reason files misnamed as BA cause a problem is that
>> tsdos will load them into the BASIC program region verbatim and  treat the
>> ASCII bytes as parts of binary formatted line numbers and tokens among
>> other problems, ultimately causing a corrupted RAM file system.
>>
>>
>>
>> It was the convention on the old Club100 library  to name them this way
>> but it's now a bad practice.
>>
>>
>>
>> -- John.
>>
>>
>>
>>
>>
>>
>>
>> On Sat, Feb 25, 2023, 5:30 PM  wrote:
>>
>> Yes, someone already wrote such a program and shared it. If you just got
>> a Backpack Drive Plus it is already on the SD card. You can also download
>> it from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>>
>>
>>
>>

Re: [M100] BackPack - read data from CLI

[Georg Käter]

Hi Jeff,

 

I´ve added the following to the listing below to "see" if BPD responds

 

..

42 INPUT#2,K
43 IF K<>"#" GOTO 42

44 PRINT K

..
 


After some seconds I see the #, but program then program stucks.

Any further idea about this behaviour?

 

Thanks for your support

Georg

 

Gesendet: Mittwoch, 01. März 2023 um 14:47 Uhr
Von: bir...@soigeneris.com
An: m...@bitchin100.com
Betreff: Re: [M100] BackPack - read data from CLI




You might be sending the SET command before the BPD has time to wake up and respond. It will return a ‘#’ when it wakes up and switches to CLI mode.

 

Jeff Birt

 



From: M100  On Behalf Of Georg Käter
Sent: Wednesday, March 1, 2023 12:59 AM
To: m...@bitchin100.com
Subject: [M100] BackPack - read data from CLI



 



Hello together,



 



I tried to read "settings" from a BackPack+ with the following, but w/o success



 



10 REM read settings from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM turn-on CLI mode
41 PRINT#1,STRING$(4,13)
50 REM send "set" command to BackPack/BackPack+
51 PRINT#1,"set";CHR$(13)
60 REM read data from BackPack (set returns 9? values)
61 INPUT#2,A,B,C,D,E,F,G,H,I
70 REM show "settings"
71 PRINT A,B,C,D,E,F,G,H,I
80 REM turn-off CLI mode
81 PRINT#1,"bye"
99 END



 



What is wrong in the above? Any idea?



 



btw this works:




10 REM read data from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM read from BackPack/BackPack+ (Date=A, Time=B, Day=C)
41 PRINT#1,"FF";chr$(7);chr$(13)
42 INPUT#2,A,B,C
50 REM print values
51 PRINT A,B,C
99 END



 



Thanks for your help

Re: [M100] - Backpack

[Peter Vollan]

See, I take the unpopular opinion that that should not be done because it
teaches bad habits.

On Wed, 1 Mar 2023 at 06:20,  wrote:

> I also tried loading a .DO named as .BA through BASIC, i.e. load
> "com:98n1e" and that worked fine. Seems to me that if it were a man ROM
> issue the same problem would happen this way. Also, the TS-DOS disassembly
> shows that it changes it’s behavior based on filetype extension.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100  *On Behalf Of *Brian
> White
> *Sent:* Wednesday, March 1, 2023 6:51 AM
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] - Backpack
>
>
>
> I don't think it's ts-dos, it's the main rom. The main rom and all the
> tpdd clients basically have to trust the file name. If it's declared as a
> .ba, then the bytes are copied verbatim and then later interpreted
> according to the rules of parsing a .ba. If the contents are not .ba,
> kablooey.
>
> bkw
>
>
>
> On Tue, Feb 28, 2023, 8:11 PM  wrote:
>
> I did some more testing and discovered that John is absolutely correct.
> Previously when I had tried to load a .BA which was really a .DO it made it
> about 3-4 line in and then stopped. This led me to believe it was an issue
> I have seen on other computer; when loading an ASCII file over serial the
> computer will tokenize the line when the CR is encountered. Just like it
> had been typed in on the keyboard. For these systems you have to add a 2
> second or so delay after each line to allow for tokenization.
>
> TSDOS does its own thing, like John says, and really makes a mess of it.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100  *On Behalf Of *John R.
> Hogerhuis
> *Sent:* Saturday, February 25, 2023 7:40 PM
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] - Backpack
>
>
>
> A side note but the reason files misnamed as BA cause a problem is that
> tsdos will load them into the BASIC program region verbatim and  treat the
> ASCII bytes as parts of binary formatted line numbers and tokens among
> other problems, ultimately causing a corrupted RAM file system.
>
>
>
> It was the convention on the old Club100 library  to name them this way
> but it's now a bad practice.
>
>
>
> -- John.
>
>
>
>
>
>
>
> On Sat, Feb 25, 2023, 5:30 PM  wrote:
>
> Yes, someone already wrote such a program and shared it. If you just got a
> Backpack Drive Plus it is already on the SD card. You can also download it
> from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>
>
>
>

Re: [M100] - Backpack

[John R. Hogerhuis]

On Wed, Mar 1, 2023, 6:43 AM Brian K. White  wrote:

> COM: does not see any filename, it only sees the content bytes.
> This is totally unrelated to storing a file in the ram filesystem.
>

It's the tpdd client that creates an inloaded file in the RAM filesystem,
including deciding which section to put it in. The ROM has low level helper
code to make gaps, fix up pointers and such but them logic is mostly in the
tpdd client you use.

Except for the cassette subsystem. It handles inloading based on file type
encoded in the file header.

But in a way cassette are all binary files since they have a binary header.
And they're only ever created by the ROM so it doesn't allow such an
accident. It's a closed system. Until/unless someone creates a cassette
based PC interface with a bug in it...

I suppose someone could craft a evil cassette text file with a BA header
and wreak havoc. But they or at least their file would quickly become
unpopular.

-- John.

>

Re: [M100] BackPack - read data from CLI

[Brian K. White]

The only thing ts-dos is doing differently is it's treating .ba files 
according to the rules of .ba files, as dictated by the main rom. It's 
not a ts-dos thing. teeny and floppy etc have to do the same exact thing.



On 3/1/23 08:47, bir...@soigeneris.com wrote:
You might be sending the SET command before the BPD has time to wake up 
and respond. It will return a ‘#’ when it wakes up and switches to CLI 
mode.


Jeff Birt

*From:* M100  *On Behalf Of *Georg Käter
*Sent:* Wednesday, March 1, 2023 12:59 AM
*To:* m...@bitchin100.com
*Subject:* [M100] BackPack - read data from CLI

Hello together,

I tried to read "settings" from a BackPack+ with the following, but w/o 
success


10 REM read settings from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM turn-on CLI mode
41 PRINT#1,STRING$(4,13)
50 REM send "set" command to BackPack/BackPack+
51 PRINT#1,"set";CHR$(13)
60 REM read data from BackPack (set returns 9? values)
61 INPUT#2,A,B,C,D,E,F,G,H,I
70 REM show "settings"
71 PRINT A,B,C,D,E,F,G,H,I
80 REM turn-off CLI mode
81 PRINT#1,"bye"
99 END

What is wrong in the above? Any idea?

btw this works:


10 REM read data from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM read from BackPack/BackPack+ (Date=A, Time=B, Day=C)
41 PRINT#1,"FF";chr$(7);chr$(13)
42 INPUT#2,A,B,C
50 REM print values
51 PRINT A,B,C
99 END

Thanks for your help



--
bkw

Re: [M100] - Backpack

[grima...@gmail.com]

When you load a file through COM, I don’t think  the file information is
passed at all. The Model 100 expects ASCII and tokenizes it on the fly.

Try sending an actual tokenized program over COM and it will fail I believe.

Could be wrong through

On Wed, Mar 1, 2023 at 9:20 AM  wrote:

> I also tried loading a .DO named as .BA through BASIC, i.e. load
> "com:98n1e" and that worked fine. Seems to me that if it were a man ROM
> issue the same problem would happen this way. Also, the TS-DOS disassembly
> shows that it changes it’s behavior based on filetype extension.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100  *On Behalf Of *Brian
> White
> *Sent:* Wednesday, March 1, 2023 6:51 AM
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] - Backpack
>
>
>
> I don't think it's ts-dos, it's the main rom. The main rom and all the
> tpdd clients basically have to trust the file name. If it's declared as a
> .ba, then the bytes are copied verbatim and then later interpreted
> according to the rules of parsing a .ba. If the contents are not .ba,
> kablooey.
>
> bkw
>
>
>
> On Tue, Feb 28, 2023, 8:11 PM  wrote:
>
> I did some more testing and discovered that John is absolutely correct.
> Previously when I had tried to load a .BA which was really a .DO it made it
> about 3-4 line in and then stopped. This led me to believe it was an issue
> I have seen on other computer; when loading an ASCII file over serial the
> computer will tokenize the line when the CR is encountered. Just like it
> had been typed in on the keyboard. For these systems you have to add a 2
> second or so delay after each line to allow for tokenization.
>
> TSDOS does its own thing, like John says, and really makes a mess of it.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100  *On Behalf Of *John R.
> Hogerhuis
> *Sent:* Saturday, February 25, 2023 7:40 PM
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] - Backpack
>
>
>
> A side note but the reason files misnamed as BA cause a problem is that
> tsdos will load them into the BASIC program region verbatim and  treat the
> ASCII bytes as parts of binary formatted line numbers and tokens among
> other problems, ultimately causing a corrupted RAM file system.
>
>
>
> It was the convention on the old Club100 library  to name them this way
> but it's now a bad practice.
>
>
>
> -- John.
>
>
>
>
>
>
>
> On Sat, Feb 25, 2023, 5:30 PM  wrote:
>
> Yes, someone already wrote such a program and shared it. If you just got a
> Backpack Drive Plus it is already on the SD card. You can also download it
> from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>
>
>
>

Re: [M100] - Backpack

[Brian K. White]

COM: does not see any filename, it only sees the content bytes.
This is totally unrelated to storing a file in the ram filesystem.


On 3/1/23 08:44, bir...@soigeneris.com wrote:
I also tried loading a .DO named as .BA through BASIC, i.e. load 
"com:98n1e" and that worked fine. Seems to me that if it were a man ROM 
issue the same problem would happen this way. Also, the TS-DOS 
disassembly shows that it changes it’s behavior based on filetype extension.


Jeff Birt

*From:* M100  *On Behalf Of *Brian White
*Sent:* Wednesday, March 1, 2023 6:51 AM
*To:* m...@bitchin100.com
*Subject:* Re: [M100] - Backpack

I don't think it's ts-dos, it's the main rom. The main rom and all the 
tpdd clients basically have to trust the file name. If it's declared as 
a .ba, then the bytes are copied verbatim and then later interpreted 
according to the rules of parsing a .ba. If the contents are not .ba, 
kablooey.


bkw

On Tue, Feb 28, 2023, 8:11 PM <mailto:bir...@soigeneris.com>> wrote:


I did some more testing and discovered that John is absolutely
correct. Previously when I had tried to load a .BA which was really
a .DO it made it about 3-4 line in and then stopped. This led me to
believe it was an issue I have seen on other computer; when loading
an ASCII file over serial the computer will tokenize the line when
the CR is encountered. Just like it had been typed in on the
keyboard. For these systems you have to add a 2 second or so delay
after each line to allow for tokenization.

TSDOS does its own thing, like John says, and really makes a mess of
it.

Jeff Birt

*From:* M100 mailto:m100-boun...@lists.bitchin100.com>> *On Behalf Of *John R.
Hogerhuis
*Sent:* Saturday, February 25, 2023 7:40 PM
*To:* m...@bitchin100.com <mailto:m...@bitchin100.com>
*Subject:* Re: [M100] - Backpack

A side note but the reason files misnamed as BA cause a problem is
that tsdos will load them into the BASIC program region verbatim
and  treat the ASCII bytes as parts of binary formatted line numbers
and tokens among other problems, ultimately causing a corrupted RAM
file system.

It was the convention on the old Club100 library  to name them this
way but it's now a bad practice.

-- John.

On Sat, Feb 25, 2023, 5:30 PM mailto:bir...@soigeneris.com>> wrote:

Yes, someone already wrote such a program and shared it. If you
just got a Backpack Drive Plus it is already on the SD card. You
can also download it from:
https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
<https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs>



--
bkw

Re: [M100] BackPack - read data from CLI

[birt_j]

You might be sending the SET command before the BPD has time to wake up and 
respond. It will return a ‘#’ when it wakes up and switches to CLI mode. 

 

Jeff Birt

 

From: M100  On Behalf Of Georg Käter
Sent: Wednesday, March 1, 2023 12:59 AM
To: m...@bitchin100.com
Subject: [M100] BackPack - read data from CLI

 

Hello together,

 

I tried to read "settings" from a BackPack+ with the following, but w/o success

 

10 REM read settings from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM turn-on CLI mode
41 PRINT#1,STRING$(4,13)
50 REM send "set" command to BackPack/BackPack+
51 PRINT#1,"set";CHR$(13)
60 REM read data from BackPack (set returns 9? values)
61 INPUT#2,A,B,C,D,E,F,G,H,I
70 REM show "settings"
71 PRINT A,B,C,D,E,F,G,H,I
80 REM turn-off CLI mode
81 PRINT#1,"bye"
99 END

 

What is wrong in the above? Any idea?

 

btw this works:


10 REM read data from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM read from BackPack/BackPack+ (Date=A, Time=B, Day=C)
41 PRINT#1,"FF";chr$(7);chr$(13)
42 INPUT#2,A,B,C
50 REM print values
51 PRINT A,B,C
99 END

 

Thanks for your help

Re: [M100] - Backpack

[birt_j]

I also tried loading a .DO named as .BA through BASIC, i.e. load "com:98n1e" 
and that worked fine. Seems to me that if it were a man ROM issue the same 
problem would happen this way. Also, the TS-DOS disassembly shows that it 
changes it’s behavior based on filetype extension.

 

Jeff Birt

 

From: M100  On Behalf Of Brian White
Sent: Wednesday, March 1, 2023 6:51 AM
To: m...@bitchin100.com
Subject: Re: [M100] - Backpack

 

I don't think it's ts-dos, it's the main rom. The main rom and all the tpdd 
clients basically have to trust the file name. If it's declared as a .ba, then 
the bytes are copied verbatim and then later interpreted according to the rules 
of parsing a .ba. If the contents are not .ba, kablooey.

bkw

 

On Tue, Feb 28, 2023, 8:11 PM mailto:bir...@soigeneris.com> > wrote:

I did some more testing and discovered that John is absolutely correct. 
Previously when I had tried to load a .BA which was really a .DO it made it 
about 3-4 line in and then stopped. This led me to believe it was an issue I 
have seen on other computer; when loading an ASCII file over serial the 
computer will tokenize the line when the CR is encountered. Just like it had 
been typed in on the keyboard. For these systems you have to add a 2 second or 
so delay after each line to allow for tokenization.

TSDOS does its own thing, like John says, and really makes a mess of it. 

 

Jeff Birt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of John R. Hogerhuis
Sent: Saturday, February 25, 2023 7:40 PM
To: m...@bitchin100.com <mailto:m...@bitchin100.com> 
Subject: Re: [M100] - Backpack

 

A side note but the reason files misnamed as BA cause a problem is that tsdos 
will load them into the BASIC program region verbatim and  treat the ASCII 
bytes as parts of binary formatted line numbers and tokens among other 
problems, ultimately causing a corrupted RAM file system. 

 

It was the convention on the old Club100 library  to name them this way but 
it's now a bad practice. 

 

-- John. 

 

 

 

On Sat, Feb 25, 2023, 5:30 PM mailto:bir...@soigeneris.com> > wrote:

Yes, someone already wrote such a program and shared it. If you just got a 
Backpack Drive Plus it is already on the SD card. You can also download it 
from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs 

 

Re: [M100] - Backpack

[Brian White]

I don't think it's ts-dos, it's the main rom. The main rom and all the tpdd
clients basically have to trust the file name. If it's declared as a .ba,
then the bytes are copied verbatim and then later interpreted according to
the rules of parsing a .ba. If the contents are not .ba, kablooey.

bkw

On Tue, Feb 28, 2023, 8:11 PM  wrote:

> I did some more testing and discovered that John is absolutely correct.
> Previously when I had tried to load a .BA which was really a .DO it made it
> about 3-4 line in and then stopped. This led me to believe it was an issue
> I have seen on other computer; when loading an ASCII file over serial the
> computer will tokenize the line when the CR is encountered. Just like it
> had been typed in on the keyboard. For these systems you have to add a 2
> second or so delay after each line to allow for tokenization.
>
> TSDOS does its own thing, like John says, and really makes a mess of it.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100  *On Behalf Of *John R.
> Hogerhuis
> *Sent:* Saturday, February 25, 2023 7:40 PM
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] - Backpack
>
>
>
> A side note but the reason files misnamed as BA cause a problem is that
> tsdos will load them into the BASIC program region verbatim and  treat the
> ASCII bytes as parts of binary formatted line numbers and tokens among
> other problems, ultimately causing a corrupted RAM file system.
>
>
>
> It was the convention on the old Club100 library  to name them this way
> but it's now a bad practice.
>
>
>
> -- John.
>
>
>
>
>
>
>
> On Sat, Feb 25, 2023, 5:30 PM  wrote:
>
> Yes, someone already wrote such a program and shared it. If you just got a
> Backpack Drive Plus it is already on the SD card. You can also download it
> from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>
>
>
>

[M100] BackPack - read data from CLI

[Georg Käter]

Hello together,

 

I tried to read "settings" from a BackPack+ with the following, but w/o success

 

10 REM read settings from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM turn-on CLI mode
41 PRINT#1,STRING$(4,13)
50 REM send "set" command to BackPack/BackPack+
51 PRINT#1,"set";CHR$(13)
60 REM read data from BackPack (set returns 9? values)
61 INPUT#2,A,B,C,D,E,F,G,H,I
70 REM show "settings"
71 PRINT A,B,C,D,E,F,G,H,I
80 REM turn-off CLI mode
81 PRINT#1,"bye"
99 END

 

What is wrong in the above? Any idea?

 

btw this works:


10 REM read data from BackPack/BackPack+
20 REM set variables
21 MAXFILES=2:DEFSTR A-K
22 CP="COM:98N1ENN"
30 REM open COM: for I/O
31 OPEN CP FOR OUTPUT AS 1
32 OPEN CP FOR INPUT AS 2
40 REM read from BackPack/BackPack+ (Date=A, Time=B, Day=C)
41 PRINT#1,"FF";chr$(7);chr$(13)
42 INPUT#2,A,B,C
50 REM print values
51 PRINT A,B,C
99 END

 

Thanks for your help

Re: [M100] - Backpack

[John R. Hogerhuis]

On Tue, Feb 28, 2023 at 5:09 PM  wrote:

> I did some more testing and discovered that John is absolutely correct.
> Previously when I had tried to load a .BA which was really a .DO it made it
> about 3-4 line in and then stopped. This led me to believe it was an issue
> I have seen on other computer; when loading an ASCII file over serial the
> computer will tokenize the line when the CR is encountered. Just like it
> had been typed in on the keyboard. For these systems you have to add a 2
> second or so delay after each line to allow for tokenization.
>
> TSDOS does its own thing, like John says, and really makes a mess of it.
>
>
>

Yes. Thanks. In retrospect, it is about TS-DOS trusting the filename
extensions on the host system. It's a reasonable assumption on its/the
developers' part... files don't get the wrong extension by anything the
M100 can do when saving/loading files. M100 always names the files
correctly. If the file says .B* it gets inloaded to the BASIC file area.
TS-DOS doesn't even look at the content AFAIK.

The problem originates above the keyboard assembly.

For my part, LaddieAlpha checks the host file content itself and presents
them with the correct extension rather than risk TS-DOS inloading a
non-tokenized BA file and corrupting the system.

-- John.

Re: [M100] - Backpack

[birt_j]

I did some more testing and discovered that John is absolutely correct. 
Previously when I had tried to load a .BA which was really a .DO it made it 
about 3-4 line in and then stopped. This led me to believe it was an issue I 
have seen on other computer; when loading an ASCII file over serial the 
computer will tokenize the line when the CR is encountered. Just like it had 
been typed in on the keyboard. For these systems you have to add a 2 second or 
so delay after each line to allow for tokenization.

TSDOS does its own thing, like John says, and really makes a mess of it. 

 

Jeff Birt

 

From: M100  On Behalf Of John R. Hogerhuis
Sent: Saturday, February 25, 2023 7:40 PM
To: m...@bitchin100.com
Subject: Re: [M100] - Backpack

 

A side note but the reason files misnamed as BA cause a problem is that tsdos 
will load them into the BASIC program region verbatim and  treat the ASCII 
bytes as parts of binary formatted line numbers and tokens among other 
problems, ultimately causing a corrupted RAM file system. 

 

It was the convention on the old Club100 library  to name them this way but 
it's now a bad practice. 

 

-- John. 

 

 

 

On Sat, Feb 25, 2023, 5:30 PM mailto:bir...@soigeneris.com> > wrote:

Yes, someone already wrote such a program and shared it. If you just got a 
Backpack Drive Plus it is already on the SD card. You can also download it 
from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs 

 

Re: [M100] - Backpack

[Mike Stein]

You're right. They're produced in relatively small quantities and sell out
pretty quickly; guess we'll have to wait for Jeff to respond.

m

On Sun, Feb 26, 2023 at 11:57 AM ho collo  wrote:

> Thanks. I’ve tried both of those several times since I got my 100. Has
> been sold out since I’ve been looking.
>
> Sent from my iPhone
>
> On Feb 26, 2023, at 10:21, Mike Stein  wrote:
>
> 
> Sorry; I forgot that it's been upgraded; try this link:
> https://www.soigeneris.com/tandy-tpdd-2-backpack-drive-2
>
>
> On Sun, Feb 26, 2023 at 8:22 AM ho collo  wrote:
>
>> That page has always come back out of stock.
>>
>> Sent from my iPhone
>>
>> On Feb 25, 2023, at 22:12, Mike Stein  wrote:
>>
>> 
>> https://www.soigeneris.com/vintage-computing?pagenumber=3
>>
>> On Sat, Feb 25, 2023 at 9:27 PM ho collo  wrote:
>>
>>> I have been searching for a source to actually purchase a backpack for a
>>> Model 100. Does anyone have a source where I can purchase a unit?
>>>
>>> Google has not been my friend.
>>>
>>> Sent from my iPhone
>>>
>>> On Feb 25, 2023, at 20:21, Gary Weber  wrote:
>>>
>>> 
>>> Hi George,
>>>
>>> Yes you can configure the way the date is represented by your backpack
>>> sending commands to it when it is in regular serial mode:
>>> It's on page 37 of the User Manual, and here's a summary:
>>>
>>> To switch between 24-hour and 12-hour time format:
>>> set time 24
>>> set time ampm
>>>
>>> To switch between date formats:
>>> set date mdy
>>> set date dmy
>>> set date ymd
>>>
>>> Cheers,
>>> Gary
>>>
>>>
>>> On Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com 
>>> wrote:
>>>
>>>> Thank you!
>>>>
>>>> I typed it in from GitHub. what I found is my Backpack is setup to
>>>> reply with dd/mm/.
>>>>
>>>> However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA
>>>> program seems to assume the date will come back in the correct format.
>>>>
>>>> Does the Backpack have a way to configure the output format?
>>>>
>>>> In the meantime i altered the program and it works fine!
>>>>
>>>> Best,
>>>> George
>>>>
>>>> On Sat, Feb 25, 2023 at 8:30 PM  wrote:
>>>>
>>>>> Yes, someone already wrote such a program and shared it. If you just
>>>>> got a Backpack Drive Plus it is already on the SD card. You can also
>>>>> download it from:
>>>>> https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>>>>>
>>>>>
>>>>>
>>>>> There is an MT version and NEC version. Note that while these have a
>>>>> .BA extension they are really text files, a.k.a. .DO files. It has been 
>>>>> the
>>>>> convention to give BASIC programs shared as text files the .BA extension
>>>>> but if you try to load such a file as is BASIC will try to parse it on the
>>>>> fly and it can’t do so fast enough. The file extension needs to be changed
>>>>> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it 
>>>>> loads
>>>>> do: SAVE”FILE.BA” and it is now a tokenized BASIC file.
>>>>>
>>>>> I’ll get these renamed and include the tokenized version in the future
>>>>> to avoid such confusion.
>>>>>
>>>>>
>>>>>
>>>>> Jeff Birt
>>>>>
>>>>>
>>>>>
>>>>> *From:* M100  *On Behalf Of *
>>>>> grima...@gmail.com
>>>>> *Sent:* Saturday, February 25, 2023 7:19 PM
>>>>> *To:* m...@bitchin100.com
>>>>> *Subject:* Re: [M100] - Backpack
>>>>>
>>>>>
>>>>>
>>>>> Random question - Does a BASIC program already exist to interface with
>>>>> the Backpack to set the clock?
>>>>>
>>>>>
>>>>>
>>>>> I find myself having to Cold start the machine often, but this handy
>>>>> Backpack has a real time clock in it.
>>>>>
>>>>>
>>>>>
>>>>> Would be great to run a quick program that interfaces with the
>>>>> Backpack over serial, issues the TIME, DATE and DAY commands, queries the
>>

Re: [M100] - Backpack

[ho collo]

Thanks. I’ve tried both of those several times since I got my 100. Has been sold out since I’ve been looking. Sent from my iPhoneOn Feb 26, 2023, at 10:21, Mike Stein  wrote:Sorry; I forgot that it's been upgraded; try this link:https://www.soigeneris.com/tandy-tpdd-2-backpack-drive-2On Sun, Feb 26, 2023 at 8:22 AM ho collo <mtlw...@yahoo.com> wrote:That page has always come back out of stock. Sent from my iPhoneOn Feb 25, 2023, at 22:12, Mike Stein <mhs.st...@gmail.com> wrote:https://www.soigeneris.com/vintage-computing?pagenumber=3On Sat, Feb 25, 2023 at 9:27 PM ho collo <mtlw...@yahoo.com> wrote:I have been searching for a source to actually purchase a backpack for a Model 100. Does anyone have a source where I can purchase a unit?Google has not been my friend. Sent from my iPhoneOn Feb 25, 2023, at 20:21, Gary Weber <g...@web8201.com> wrote:Hi George,Yes you can configure the way the date is represented by your backpack sending commands to it when it is in regular serial mode:It's on page 37 of the User Manual, and here's a summary:To switch between 24-hour and 12-hour time format:set time 24set time ampmTo switch between date formats:set date mdyset date dmyset date ymdCheers,GaryOn Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com <grima...@gmail.com> wrote:Thank you!I typed it in from GitHub. what I found is my Backpack is setup to reply with dd/mm/.However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA program seems to assume the date will come back in the correct format.Does the Backpack have a way to configure the output format? In the meantime i altered the program and it works fine!Best,GeorgeOn Sat, Feb 25, 2023 at 8:30 PM <bir...@soigeneris.com> wrote:Yes, someone already wrote such a program and shared it. If you just got a Backpack Drive Plus it is already on the SD card. You can also download it from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs  There is an MT version and NEC version. Note that while these have a .BA extension they are really text files, a.k.a. .DO files. It has been the convention to give BASIC programs shared as text files the .BA extension but if you try to load such a file as is BASIC will try to parse it on the fly and it can’t do so fast enough. The file extension needs to be changed to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads do: SAVE”FILE.BA” and it is now a tokenized BASIC file. I’ll get these renamed and include the tokenized version in the future to avoid such confusion. Jeff Birt From: M100 <m100-boun...@lists.bitchin100.com> On Behalf Of grima...@gmail.comSent: Saturday, February 25, 2023 7:19 PMTo: m...@bitchin100.comSubject: Re: [M100] - Backpack Random question - Does a BASIC program already exist to interface with the Backpack to set the clock? I find myself having to Cold start the machine often, but this handy Backpack has a real time clock in it. Would be great to run a quick program that interfaces with the Backpack over serial, issues the TIME, DATE and DAY commands, queries the current system time and date, calculates the delta and then resets the system clock. I started to write the program in BASIC, but I admit I don’t know much about serial communication. I managed to open the COM buffer for output, send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after that, close the buffer, reopen it for input and then try to get the result. However I only end up with: C#T As if the second PRINT never went through. So rather than continue to rack my brain, I figured I’d ask if it already exists. -George On Fri, Feb 17, 2023 at 4:44 PM Mike Stein <mhs.st...@gmail.com> wrote:It might not be that straightforward; the printer port is partially shared with the keyboard. On Fri, Feb 17, 2023 at 10:58 AM Alex ... <abortretryf...@gmail.com> wrote:Wire a R2R DAC to the printer port and have the M100 play music Covox style.  On Wed, Feb 15, 2023, 14:21 Fisher <nolan...@fisher25.ca> wrote:All it needs in its next version is an 8mm stereo jack, an mp3 player and some jukebox software for the laptop!Too much to wish for? No matter, it’s already a great piece of kit. :-) Sean On Feb 14, 2023, at 8:08 PM, <bir...@soigeneris.com> <bir...@soigeneris.com> wrote: The Backpack was designed by a friend of mine who wishes to remain private. He sent me one and I thought it was great and encouraged him to make more offering my help. My only part of the design was the case.  Jeff Birt From: M100 <m100-boun...@lists.bitchin100.com> On Behalf Of grima...@gmail.comSent: Tuesday, February 14, 2023 1:15 PMTo: Model 100 Discussion <m100@lists.bitchin100.com>Subject: [M100] - Backpack Just received my Backpack from Soigeneris. All I have to say, is that I really like the design of it all. It’s relatively compact, it matches the design of the M100, and it runs on a single AA cell. I immediately plugged it in, and got it

Re: [M100] - Backpack - Time/Date

[Georg Käter]

Following works for me, independent the format of "time format" set in BackPack
 
A=STR$(VAL(A)+(RIGHT$(A,1)="p"AND12))+RIGHT$(A,7):A="0"+RIGHT$(A,LEN(A)-1):TIME$=MID$(A,LEN(A)-8,8)where
 A is read from BackPack
 
Question now: Is there a way to read the "date format" from BackPack as US 
version uses MM/DD/YY, INT version uses DD/MM/YY and NEC uses YY/DD/MM?
 
Kind regards
Georg

== Ihre Nachricht ==

von      : Gary Weber 
gesendet : Sonntag, 26. Februar 2023, 03:20
an       : m...@bitchin100.com
Betreff  : [M100] - Backpack

__ Originalnachricht ___


> Hi George,

> Yes you can configure the way the date is represented by your backpack 
> sending commands to it when it is in regular serial mode:
> It's on page 37 of the User Manual, and here's a summary:
> To switch between 24-hour and 12-hour time format:
> set time 24
> set time ampm

> To switch between date formats:
> set date mdy
> set date dmy
> set date ymd

> Cheers,
> Gary


> On Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com  wrote:

>> Thank you!

>> I typed it in from GitHub. what I found is my Backpack is setup to reply 
>> with dd/mm/.

>> However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA 
>> program seems to assume the date will come back in the correct format.

>> Does the Backpack have a way to configure the output format? 

>> In the meantime i altered the program and it works fine!

>> Best,
>> George
>> On Sat, Feb 25, 2023 at 8:30 PM  wrote:

>>> Yes, someone already wrote such a program and shared it. If you just got a 
>>> Backpack Drive Plus it is already on the SD card. You can also download it 
>>> from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs 
>>>  
>>> There is an MT version and NEC version. Note that while these have a .BA 
>>> extension they are really text files, a.k.a. .DO files. It has been the 
>>> convention to give BASIC programs shared as text files the .BA extension 
>>> but if you try to load such a file as is BASIC will try to parse it on the 
>>> fly and it can’t do so fast enough. The file extension needs to be changed 
>>> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads 
>>> do: SAVE”FILE.BA” and it is now a tokenized BASIC file. 

>>> I’ll get these renamed and include the tokenized version in the future to 
>>> avoid such confusion.
>>>  
>>> Jeff Birt
>>>  
>>> From: M100  On Behalf Of 
>>> grima...@gmail.com
>>> Sent: Saturday, February 25, 2023 7:19 PM
>>> To: m...@bitchin100.com
>>> Subject: Re: [M100] - Backpack
>>>  
>>> Random question - Does a BASIC program already exist to interface with the 
>>> Backpack to set the clock?
>>>  
>>> I find myself having to Cold start the machine often, but this handy 
>>> Backpack has a real time clock in it.
>>>  
>>> Would be great to run a quick program that interfaces with the Backpack 
>>> over serial, issues the TIME, DATE and DAY commands, queries the current 
>>> system time and date, calculates the delta and then resets the system clock.
>>>  
>>> I started to write the program in BASIC, but I admit I don’t know much 
>>> about serial communication. I managed to open the COM buffer for output, 
>>> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after 
>>> that, close the buffer, reopen it for input and then try to get the result.
>>>  
>>> However I only end up with:
>>>  
>>> C
>>> #
>>> T
>>>  
>>> As if the second PRINT never went through.
>>>  
>>> So rather than continue to rack my brain, I figured I’d ask if it already 
>>> exists.
>>>  
>>> -George
>>>  
>>> On Fri, Feb 17, 2023 at 4:44 PM Mike Stein  wrote:
>>>> It might not be that straightforward; the printer port is partially shared 
>>>> with the keyboard.
>>>>  
>>>> On Fri, Feb 17, 2023 at 10:58 AM Alex ...  wrote:
>>>>> Wire a R2R DAC to the printer port and have the M100 play music Covox 
>>>>> style. 
>>>>>  
>>>>> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>>>>>> All it needs in its next version is an 8mm stereo jack, an mp3 player 
>>>>>> and some jukebox software for the laptop!
>>>>>> Too much to wish for? No matter, it’s already a great pie

Re: [M100] - Backpack

[Mike Stein]

Sorry; I forgot that it's been upgraded; try this link:
https://www.soigeneris.com/tandy-tpdd-2-backpack-drive-2


On Sun, Feb 26, 2023 at 8:22 AM ho collo  wrote:

> That page has always come back out of stock.
>
> Sent from my iPhone
>
> On Feb 25, 2023, at 22:12, Mike Stein  wrote:
>
> 
> https://www.soigeneris.com/vintage-computing?pagenumber=3
>
> On Sat, Feb 25, 2023 at 9:27 PM ho collo  wrote:
>
>> I have been searching for a source to actually purchase a backpack for a
>> Model 100. Does anyone have a source where I can purchase a unit?
>>
>> Google has not been my friend.
>>
>> Sent from my iPhone
>>
>> On Feb 25, 2023, at 20:21, Gary Weber  wrote:
>>
>> 
>> Hi George,
>>
>> Yes you can configure the way the date is represented by your backpack
>> sending commands to it when it is in regular serial mode:
>> It's on page 37 of the User Manual, and here's a summary:
>>
>> To switch between 24-hour and 12-hour time format:
>> set time 24
>> set time ampm
>>
>> To switch between date formats:
>> set date mdy
>> set date dmy
>> set date ymd
>>
>> Cheers,
>> Gary
>>
>>
>> On Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com 
>> wrote:
>>
>>> Thank you!
>>>
>>> I typed it in from GitHub. what I found is my Backpack is setup to reply
>>> with dd/mm/.
>>>
>>> However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA
>>> program seems to assume the date will come back in the correct format.
>>>
>>> Does the Backpack have a way to configure the output format?
>>>
>>> In the meantime i altered the program and it works fine!
>>>
>>> Best,
>>> George
>>>
>>> On Sat, Feb 25, 2023 at 8:30 PM  wrote:
>>>
>>>> Yes, someone already wrote such a program and shared it. If you just
>>>> got a Backpack Drive Plus it is already on the SD card. You can also
>>>> download it from:
>>>> https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>>>>
>>>>
>>>>
>>>> There is an MT version and NEC version. Note that while these have a
>>>> .BA extension they are really text files, a.k.a. .DO files. It has been the
>>>> convention to give BASIC programs shared as text files the .BA extension
>>>> but if you try to load such a file as is BASIC will try to parse it on the
>>>> fly and it can’t do so fast enough. The file extension needs to be changed
>>>> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads
>>>> do: SAVE”FILE.BA” and it is now a tokenized BASIC file.
>>>>
>>>> I’ll get these renamed and include the tokenized version in the future
>>>> to avoid such confusion.
>>>>
>>>>
>>>>
>>>> Jeff Birt
>>>>
>>>>
>>>>
>>>> *From:* M100  *On Behalf Of *
>>>> grima...@gmail.com
>>>> *Sent:* Saturday, February 25, 2023 7:19 PM
>>>> *To:* m...@bitchin100.com
>>>> *Subject:* Re: [M100] - Backpack
>>>>
>>>>
>>>>
>>>> Random question - Does a BASIC program already exist to interface with
>>>> the Backpack to set the clock?
>>>>
>>>>
>>>>
>>>> I find myself having to Cold start the machine often, but this handy
>>>> Backpack has a real time clock in it.
>>>>
>>>>
>>>>
>>>> Would be great to run a quick program that interfaces with the Backpack
>>>> over serial, issues the TIME, DATE and DAY commands, queries the current
>>>> system time and date, calculates the delta and then resets the system 
>>>> clock.
>>>>
>>>>
>>>>
>>>> I started to write the program in BASIC, but I admit I don’t know much
>>>> about serial communication. I managed to open the COM buffer for output,
>>>> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
>>>> that, close the buffer, reopen it for input and then try to get the result.
>>>>
>>>>
>>>>
>>>> However I only end up with:
>>>>
>>>>
>>>>
>>>> C
>>>>
>>>> #
>>>>
>>>> T
>>>>
>>>>
>>>>
>>>> As if the second PRINT never went through.
>>>>
>>

Re: [M100] - Backpack

[ho collo]

That page has always come back out of stock. Sent from my iPhoneOn Feb 25, 2023, at 22:12, Mike Stein  wrote:https://www.soigeneris.com/vintage-computing?pagenumber=3On Sat, Feb 25, 2023 at 9:27 PM ho collo <mtlw...@yahoo.com> wrote:I have been searching for a source to actually purchase a backpack for a Model 100. Does anyone have a source where I can purchase a unit?Google has not been my friend. Sent from my iPhoneOn Feb 25, 2023, at 20:21, Gary Weber <g...@web8201.com> wrote:Hi George,Yes you can configure the way the date is represented by your backpack sending commands to it when it is in regular serial mode:It's on page 37 of the User Manual, and here's a summary:To switch between 24-hour and 12-hour time format:set time 24set time ampmTo switch between date formats:set date mdyset date dmyset date ymdCheers,GaryOn Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com <grima...@gmail.com> wrote:Thank you!I typed it in from GitHub. what I found is my Backpack is setup to reply with dd/mm/.However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA program seems to assume the date will come back in the correct format.Does the Backpack have a way to configure the output format? In the meantime i altered the program and it works fine!Best,GeorgeOn Sat, Feb 25, 2023 at 8:30 PM <bir...@soigeneris.com> wrote:Yes, someone already wrote such a program and shared it. If you just got a Backpack Drive Plus it is already on the SD card. You can also download it from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs  There is an MT version and NEC version. Note that while these have a .BA extension they are really text files, a.k.a. .DO files. It has been the convention to give BASIC programs shared as text files the .BA extension but if you try to load such a file as is BASIC will try to parse it on the fly and it can’t do so fast enough. The file extension needs to be changed to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads do: SAVE”FILE.BA” and it is now a tokenized BASIC file. I’ll get these renamed and include the tokenized version in the future to avoid such confusion. Jeff Birt From: M100 <m100-boun...@lists.bitchin100.com> On Behalf Of grima...@gmail.comSent: Saturday, February 25, 2023 7:19 PMTo: m...@bitchin100.comSubject: Re: [M100] - Backpack Random question - Does a BASIC program already exist to interface with the Backpack to set the clock? I find myself having to Cold start the machine often, but this handy Backpack has a real time clock in it. Would be great to run a quick program that interfaces with the Backpack over serial, issues the TIME, DATE and DAY commands, queries the current system time and date, calculates the delta and then resets the system clock. I started to write the program in BASIC, but I admit I don’t know much about serial communication. I managed to open the COM buffer for output, send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after that, close the buffer, reopen it for input and then try to get the result. However I only end up with: C#T As if the second PRINT never went through. So rather than continue to rack my brain, I figured I’d ask if it already exists. -George On Fri, Feb 17, 2023 at 4:44 PM Mike Stein <mhs.st...@gmail.com> wrote:It might not be that straightforward; the printer port is partially shared with the keyboard. On Fri, Feb 17, 2023 at 10:58 AM Alex ... <abortretryf...@gmail.com> wrote:Wire a R2R DAC to the printer port and have the M100 play music Covox style.  On Wed, Feb 15, 2023, 14:21 Fisher <nolan...@fisher25.ca> wrote:All it needs in its next version is an 8mm stereo jack, an mp3 player and some jukebox software for the laptop!Too much to wish for? No matter, it’s already a great piece of kit. :-) Sean On Feb 14, 2023, at 8:08 PM, <bir...@soigeneris.com> <bir...@soigeneris.com> wrote: The Backpack was designed by a friend of mine who wishes to remain private. He sent me one and I thought it was great and encouraged him to make more offering my help. My only part of the design was the case.  Jeff Birt From: M100 <m100-boun...@lists.bitchin100.com> On Behalf Of grima...@gmail.comSent: Tuesday, February 14, 2023 1:15 PMTo: Model 100 Discussion <m100@lists.bitchin100.com>Subject: [M100] - Backpack Just received my Backpack from Soigeneris. All I have to say, is that I really like the design of it all. It’s relatively compact, it matches the design of the M100, and it runs on a single AA cell. I immediately plugged it in, and got it to work. Pretty much zero configuration needed. I’ve already got REX installed so I was able to load up TS-DOS and be off to the races. Shout out to Soigeneris and to whomever designed and built this device! Best,George 

Re: [M100] - Backpack

[Brian White]

oh yeah... looking at the schematic again I forgot the actual function of
the 3 /OE pins is still a question until actually tried.

So it's not quite time yet to claim 200 has this option that 100 and 102
have had for a few years.

With the one pin being connected directly to A15 according to the service
manual, I implemented that pin as active high. But until I actually try it,
who knows? The schematic claims it's an active low /CE by labelling it that
way. Yet... A15.   `\_(oo)_/'


bkw

On Sun, Feb 26, 2023, 4:56 AM Brian White  wrote:

> It still works. I use it. And anyone can build themselves a new one any
> time from my re-spin plans, it just hasn't changed and probably never will
> because I am not up to picking apart the firmware to hack on it nor write a
> new one. It's Steve's last version.
>
> The only advancement is I made adapter boards for model 200 recently like
> I had for 100 & 102 already, where the board includes a copy of a standard
> rom so that it functions just like the original rom, but also provides a
> solderless connection out to rex and back so that you can boot from the rex
> or boot from internal without having to open the case again. And the
> connections are all dupont jumper wires, so installable/removable without
> soldering, and without blocking the original socket preventing having an
> internal main rom.
>
> Some weeks ago when we were talking about the weird 8k chip in the 200, I
> made a board for that. So now 200 also has this option to keep an internal
> rom and still boot from rex. For the main 32k chip in the 200, you just use
> the same one as 102. At the time we all decided based on the data sheets
> that if all you wanted to do was replace that 8k chip, you should be able
> to just use a normal 27C64, but I decided to actually implement the extra
> control pin with a few gates just to be sure.
>
> I have built and programmed that new board so I at least know the
> programing jumper setting works, but have not tried installing it yet.
> github.com/bkw777/aDIPters#flexrom_200_m13
>
> It's kind of wildly impractical. These small eeprom are getting stupid
> expensive. I'm afraid to add up the cost of all the bits to make a rex
> classic and these two rom adapter boards to make a 200 with rex classic and
> still usable internal main rom. I mean I have already got all those bits,
> but I just mean I don't want to find out explicitly just how dumb it is. ;)
>
> But I do love my 100 and 102 with the same option. I switch between stock
> internal main rom with no rex, like when testing that ram+ or pgdesigns
> ram, rex classic software main rom, rexcpm, and back etc any time without
> opening the case any more. I love it.
>
> And it's all just sockets and dupont pin connectors. I could put the
> original stock rom back in any time. I could also ditch the jumper wires to
> rex yet still use the non-original main rom by just installing a jumper on
> the pins on the board in place of the wires. I could also still update the
> rom on the board. That would require opening the case again but no
> soldering.
>
> bkw
>
> On Sun, Feb 26, 2023, 12:46 AM Mike Stein  wrote:
>
>> Yeah, the XR4 would certainly expand the options (pun intended) but I
>> never quite figured out how they selected among the images; I did work out
>> another solution and started building a 16MB RAM expansion but never
>> actually finished or tested any of it. Things like REX, the Backpack and
>> the Dial-a-ROM are a lot easier ;-)
>>
>> The issue is that when TS-DOS is in (the single) ROM space it would get
>> clobbered by loading another ROM image there; I'll have to have another
>> look at it all, including the EME tools, to see how it might work. Am I
>> missing something?
>>
>> BTW, I haven't used my REX in years; AFAIR it's the original version with
>> the System ROM replacement option and I guess there's not much support for
>> that these days?
>>
>> m
>>
>> On Sun, Feb 26, 2023 at 12:14 AM Stephen Adolph 
>> wrote:
>>
>>> Mike, not sure I follow.
>>> You know you can have multiple ram spaces in option locations.  Like xr4.
>>> Could an xr4 do what you want?
>>>
>>> Xr4 was a tidy solution.  Needed a few wires to make it work.
>>>
>>> I guess I don't understand why tsdos is not compatible with option ram?
>>> Seems like it is, just like any other rom program?
>>>
>>>
>>>
>>> On Sunday, February 26, 2023, Mike Stein  wrote:
>>>
 As you may remember, years ago I designed an adapter that let you put
 both the system image and an option ROM image into a single chip that
 replaced the System ROM, both the standard (new) or non-standard (old)
 version; some folks on here may even still have one in their M100, probably
 loaded with TS-DOS.

 In another M100 I replaced the option ROM with RAM and load/save/copy
 etc. various ROM images using the EME extRAM tools, but of course I can't
 have TS-DOS in the same memory area as the option ROMs.

 The Dial-a-ROM and 

Re: [M100] - Backpack

[Brian White]

It still works. I use it. And anyone can build themselves a new one any
time from my re-spin plans, it just hasn't changed and probably never will
because I am not up to picking apart the firmware to hack on it nor write a
new one. It's Steve's last version.

The only advancement is I made adapter boards for model 200 recently like I
had for 100 & 102 already, where the board includes a copy of a standard
rom so that it functions just like the original rom, but also provides a
solderless connection out to rex and back so that you can boot from the rex
or boot from internal without having to open the case again. And the
connections are all dupont jumper wires, so installable/removable without
soldering, and without blocking the original socket preventing having an
internal main rom.

Some weeks ago when we were talking about the weird 8k chip in the 200, I
made a board for that. So now 200 also has this option to keep an internal
rom and still boot from rex. For the main 32k chip in the 200, you just use
the same one as 102. At the time we all decided based on the data sheets
that if all you wanted to do was replace that 8k chip, you should be able
to just use a normal 27C64, but I decided to actually implement the extra
control pin with a few gates just to be sure.

I have built and programmed that new board so I at least know the
programing jumper setting works, but have not tried installing it yet.
github.com/bkw777/aDIPters#flexrom_200_m13

It's kind of wildly impractical. These small eeprom are getting stupid
expensive. I'm afraid to add up the cost of all the bits to make a rex
classic and these two rom adapter boards to make a 200 with rex classic and
still usable internal main rom. I mean I have already got all those bits,
but I just mean I don't want to find out explicitly just how dumb it is. ;)

But I do love my 100 and 102 with the same option. I switch between stock
internal main rom with no rex, like when testing that ram+ or pgdesigns
ram, rex classic software main rom, rexcpm, and back etc any time without
opening the case any more. I love it.

And it's all just sockets and dupont pin connectors. I could put the
original stock rom back in any time. I could also ditch the jumper wires to
rex yet still use the non-original main rom by just installing a jumper on
the pins on the board in place of the wires. I could also still update the
rom on the board. That would require opening the case again but no
soldering.

bkw

On Sun, Feb 26, 2023, 12:46 AM Mike Stein  wrote:

> Yeah, the XR4 would certainly expand the options (pun intended) but I
> never quite figured out how they selected among the images; I did work out
> another solution and started building a 16MB RAM expansion but never
> actually finished or tested any of it. Things like REX, the Backpack and
> the Dial-a-ROM are a lot easier ;-)
>
> The issue is that when TS-DOS is in (the single) ROM space it would get
> clobbered by loading another ROM image there; I'll have to have another
> look at it all, including the EME tools, to see how it might work. Am I
> missing something?
>
> BTW, I haven't used my REX in years; AFAIR it's the original version with
> the System ROM replacement option and I guess there's not much support for
> that these days?
>
> m
>
> On Sun, Feb 26, 2023 at 12:14 AM Stephen Adolph 
> wrote:
>
>> Mike, not sure I follow.
>> You know you can have multiple ram spaces in option locations.  Like xr4.
>> Could an xr4 do what you want?
>>
>> Xr4 was a tidy solution.  Needed a few wires to make it work.
>>
>> I guess I don't understand why tsdos is not compatible with option ram?
>> Seems like it is, just like any other rom program?
>>
>>
>>
>> On Sunday, February 26, 2023, Mike Stein  wrote:
>>
>>> As you may remember, years ago I designed an adapter that let you put
>>> both the system image and an option ROM image into a single chip that
>>> replaced the System ROM, both the standard (new) or non-standard (old)
>>> version; some folks on here may even still have one in their M100, probably
>>> loaded with TS-DOS.
>>>
>>> In another M100 I replaced the option ROM with RAM and load/save/copy
>>> etc. various ROM images using the EME extRAM tools, but of course I can't
>>> have TS-DOS in the same memory area as the option ROMs.
>>>
>>> The Dial-a-ROM and REX are certainly excellent solutions, but I'd still
>>> like to make the Option RAM concept compatible with TS-DOS, even if I have
>>> to add or reuse a physical switch to select between RAM and ROM. Any other
>>> ideas?
>>>
>>> m
>>>
>>>
>>>
>>> On Sat, Feb 25, 2023 at 11:26 PM John R. Hogerhuis 
>>> wrote:
>>>


 On Sat, Feb 25, 2023, 8:18 PM Mike Stein  wrote:

> Yeah, I guess everybody has TS-DOS in ROM one way or another these
> days; I've thought about putting it in the system ROM instead of the
> Scheduler and Address Book, but removing them doesn't really free up much
> space; maybe Teeny would fit...
>
>
 Scheduler 

Re: [M100] - Backpack

[Mike Stein]

Yeah, the XR4 would certainly expand the options (pun intended) but I never
quite figured out how they selected among the images; I did work out
another solution and started building a 16MB RAM expansion but never
actually finished or tested any of it. Things like REX, the Backpack and
the Dial-a-ROM are a lot easier ;-)

The issue is that when TS-DOS is in (the single) ROM space it would get
clobbered by loading another ROM image there; I'll have to have another
look at it all, including the EME tools, to see how it might work. Am I
missing something?

BTW, I haven't used my REX in years; AFAIR it's the original version with
the System ROM replacement option and I guess there's not much support for
that these days?

m

On Sun, Feb 26, 2023 at 12:14 AM Stephen Adolph 
wrote:

> Mike, not sure I follow.
> You know you can have multiple ram spaces in option locations.  Like xr4.
> Could an xr4 do what you want?
>
> Xr4 was a tidy solution.  Needed a few wires to make it work.
>
> I guess I don't understand why tsdos is not compatible with option ram?
> Seems like it is, just like any other rom program?
>
>
>
> On Sunday, February 26, 2023, Mike Stein  wrote:
>
>> As you may remember, years ago I designed an adapter that let you put
>> both the system image and an option ROM image into a single chip that
>> replaced the System ROM, both the standard (new) or non-standard (old)
>> version; some folks on here may even still have one in their M100, probably
>> loaded with TS-DOS.
>>
>> In another M100 I replaced the option ROM with RAM and load/save/copy
>> etc. various ROM images using the EME extRAM tools, but of course I can't
>> have TS-DOS in the same memory area as the option ROMs.
>>
>> The Dial-a-ROM and REX are certainly excellent solutions, but I'd still
>> like to make the Option RAM concept compatible with TS-DOS, even if I have
>> to add or reuse a physical switch to select between RAM and ROM. Any other
>> ideas?
>>
>> m
>>
>>
>>
>> On Sat, Feb 25, 2023 at 11:26 PM John R. Hogerhuis 
>> wrote:
>>
>>>
>>>
>>> On Sat, Feb 25, 2023, 8:18 PM Mike Stein  wrote:
>>>
 Yeah, I guess everybody has TS-DOS in ROM one way or another these
 days; I've thought about putting it in the system ROM instead of the
 Scheduler and Address Book, but removing them doesn't really free up much
 space; maybe Teeny would fit...


>>> Scheduler and address book are a very simple "grep" type utility serving
>>> as a simple database. I feel they are too clever and minimalist a solution
>>> to remove :-) plus there are programs that let you use this search facility
>>> on any text file.
>>>
>>> -- John.
>>>

Re: [M100] - Backpack

[Mike Stein]

Hmm... She's incorporated Teeny, not TS-DOS but that's fine; removing modem
functionality also doesn't trouble me, but she also removed ADDRSS and
SCHEDL, as well as some print functions; those were probably the issues I
found with it when I first looked at it.

But a pretty impressive effort and worth a try for sure.

m

On Sun, Feb 26, 2023 at 12:06 AM Stephen Adolph 
wrote:

> Teeny integrated Main  rom has been done and shared.
>
> I think it was quite a good job and useful.
> http://sarahkmarr.com/retromodel100.html
>
>
>
>
> On Saturday, February 25, 2023, Mike Stein  wrote:
>
>> Point taken; I've never used them but I suppose others find them useful.
>> I don't think they'd free up much space anyway because ISTR that they use
>> TEXT for much of their functionality.
>>
>> On Sat, Feb 25, 2023 at 11:26 PM John R. Hogerhuis 
>> wrote:
>>
>>>
>>>
>>> On Sat, Feb 25, 2023, 8:18 PM Mike Stein  wrote:
>>>
 Yeah, I guess everybody has TS-DOS in ROM one way or another these
 days; I've thought about putting it in the system ROM instead of the
 Scheduler and Address Book, but removing them doesn't really free up much
 space; maybe Teeny would fit...


>>> Scheduler and address book are a very simple "grep" type utility serving
>>> as a simple database. I feel they are too clever and minimalist a solution
>>> to remove :-) plus there are programs that let you use this search facility
>>> on any text file.
>>>
>>> -- John.
>>>

Re: [M100] - Backpack

[Stephen Adolph]

Mike, not sure I follow.
You know you can have multiple ram spaces in option locations.  Like xr4.
Could an xr4 do what you want?

Xr4 was a tidy solution.  Needed a few wires to make it work.

I guess I don't understand why tsdos is not compatible with option ram?
Seems like it is, just like any other rom program?



On Sunday, February 26, 2023, Mike Stein  wrote:

> As you may remember, years ago I designed an adapter that let you put both
> the system image and an option ROM image into a single chip that replaced
> the System ROM, both the standard (new) or non-standard (old) version; some
> folks on here may even still have one in their M100, probably loaded with
> TS-DOS.
>
> In another M100 I replaced the option ROM with RAM and load/save/copy etc.
> various ROM images using the EME extRAM tools, but of course I can't have
> TS-DOS in the same memory area as the option ROMs.
>
> The Dial-a-ROM and REX are certainly excellent solutions, but I'd still
> like to make the Option RAM concept compatible with TS-DOS, even if I have
> to add or reuse a physical switch to select between RAM and ROM. Any other
> ideas?
>
> m
>
>
>
> On Sat, Feb 25, 2023 at 11:26 PM John R. Hogerhuis 
> wrote:
>
>>
>>
>> On Sat, Feb 25, 2023, 8:18 PM Mike Stein  wrote:
>>
>>> Yeah, I guess everybody has TS-DOS in ROM one way or another these days;
>>> I've thought about putting it in the system ROM instead of the Scheduler
>>> and Address Book, but removing them doesn't really free up much space;
>>> maybe Teeny would fit...
>>>
>>>
>> Scheduler and address book are a very simple "grep" type utility serving
>> as a simple database. I feel they are too clever and minimalist a solution
>> to remove :-) plus there are programs that let you use this search facility
>> on any text file.
>>
>> -- John.
>>
>>>
>>>

Re: [M100] - Backpack

[Mike Stein]

Thank you!

Now that you mention it I'd seen that before, probably from a link that you
also supplied.

ISTR that I found a couple of minor issues with it, but it's time to read
that again and burn one.

Tnx again!


On Sun, Feb 26, 2023 at 12:06 AM Stephen Adolph 
wrote:

> Teeny integrated Main  rom has been done and shared.
>
> I think it was quite a good job and useful.
> http://sarahkmarr.com/retromodel100.html
>
>
>
>
> On Saturday, February 25, 2023, Mike Stein  wrote:
>
>> Point taken; I've never used them but I suppose others find them useful.
>> I don't think they'd free up much space anyway because ISTR that they use
>> TEXT for much of their functionality.
>>
>> On Sat, Feb 25, 2023 at 11:26 PM John R. Hogerhuis 
>> wrote:
>>
>>>
>>>
>>> On Sat, Feb 25, 2023, 8:18 PM Mike Stein  wrote:
>>>
 Yeah, I guess everybody has TS-DOS in ROM one way or another these
 days; I've thought about putting it in the system ROM instead of the
 Scheduler and Address Book, but removing them doesn't really free up much
 space; maybe Teeny would fit...


>>> Scheduler and address book are a very simple "grep" type utility serving
>>> as a simple database. I feel they are too clever and minimalist a solution
>>> to remove :-) plus there are programs that let you use this search facility
>>> on any text file.
>>>
>>> -- John.
>>>

[M100] - Backpack

[Stephen Adolph]

Teeny integrated Main  rom has been done and shared.

I think it was quite a good job and useful.
http://sarahkmarr.com/retromodel100.html




On Saturday, February 25, 2023, Mike Stein  wrote:

> Point taken; I've never used them but I suppose others find them useful. I
> don't think they'd free up much space anyway because ISTR that they use
> TEXT for much of their functionality.
>
> On Sat, Feb 25, 2023 at 11:26 PM John R. Hogerhuis 
> wrote:
>
>>
>>
>> On Sat, Feb 25, 2023, 8:18 PM Mike Stein  wrote:
>>
>>> Yeah, I guess everybody has TS-DOS in ROM one way or another these days;
>>> I've thought about putting it in the system ROM instead of the Scheduler
>>> and Address Book, but removing them doesn't really free up much space;
>>> maybe Teeny would fit...
>>>
>>>
>> Scheduler and address book are a very simple "grep" type utility serving
>> as a simple database. I feel they are too clever and minimalist a solution
>> to remove :-) plus there are programs that let you use this search facility
>> on any text file.
>>
>> -- John.
>>
>>>
>>>

Re: [M100] - Backpack

[Mike Stein]

As you may remember, years ago I designed an adapter that let you put both
the system image and an option ROM image into a single chip that replaced
the System ROM, both the standard (new) or non-standard (old) version; some
folks on here may even still have one in their M100, probably loaded with
TS-DOS.

In another M100 I replaced the option ROM with RAM and load/save/copy etc.
various ROM images using the EME extRAM tools, but of course I can't have
TS-DOS in the same memory area as the option ROMs.

The Dial-a-ROM and REX are certainly excellent solutions, but I'd still
like to make the Option RAM concept compatible with TS-DOS, even if I have
to add or reuse a physical switch to select between RAM and ROM. Any other
ideas?

m



On Sat, Feb 25, 2023 at 11:26 PM John R. Hogerhuis  wrote:

>
>
> On Sat, Feb 25, 2023, 8:18 PM Mike Stein  wrote:
>
>> Yeah, I guess everybody has TS-DOS in ROM one way or another these days;
>> I've thought about putting it in the system ROM instead of the Scheduler
>> and Address Book, but removing them doesn't really free up much space;
>> maybe Teeny would fit...
>>
>>
> Scheduler and address book are a very simple "grep" type utility serving
> as a simple database. I feel they are too clever and minimalist a solution
> to remove :-) plus there are programs that let you use this search facility
> on any text file.
>
> -- John.
>
>>
>>

Re: [M100] - Backpack

[Mike Stein]

Point taken; I've never used them but I suppose others find them useful. I
don't think they'd free up much space anyway because ISTR that they use
TEXT for much of their functionality.

On Sat, Feb 25, 2023 at 11:26 PM John R. Hogerhuis  wrote:

>
>
> On Sat, Feb 25, 2023, 8:18 PM Mike Stein  wrote:
>
>> Yeah, I guess everybody has TS-DOS in ROM one way or another these days;
>> I've thought about putting it in the system ROM instead of the Scheduler
>> and Address Book, but removing them doesn't really free up much space;
>> maybe Teeny would fit...
>>
>>
> Scheduler and address book are a very simple "grep" type utility serving
> as a simple database. I feel they are too clever and minimalist a solution
> to remove :-) plus there are programs that let you use this search facility
> on any text file.
>
> -- John.
>
>>
>>

Re: [M100] - Backpack

[Mike Stein]

Probably dates back to the days when files that you downloaded from
Compuserve or another user etc. had to all be plain text ASCII because
TELCOM can't handle binary files; I suppose everyone just knew that .DO
stood for documentation and .BA stood for plaintext BASIC programs that had
to be renamed before loading with BASIC or TEXT.

On Sat, Feb 25, 2023 at 8:41 PM John R. Hogerhuis  wrote:

> A side note but the reason files misnamed as BA cause a problem is that
> tsdos will load them into the BASIC program region verbatim and  treat the
> ASCII bytes as parts of binary formatted line numbers and tokens among
> other problems, ultimately causing a corrupted RAM file system.
>
> It was the convention on the old Club100 library  to name them this way
> but it's now a bad practice.
>
> -- John.
>
>
>
>
> On Sat, Feb 25, 2023, 5:30 PM  wrote:
>
>> Yes, someone already wrote such a program and shared it. If you just got
>> a Backpack Drive Plus it is already on the SD card. You can also download
>> it from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>>
>>
>>
>> There is an MT version and NEC version. Note that while these have a .BA
>> extension they are really text files, a.k.a. .DO files. It has been the
>> convention to give BASIC programs shared as text files the .BA extension
>> but if you try to load such a file as is BASIC will try to parse it on the
>> fly and it can’t do so fast enough. The file extension needs to be changed
>> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads
>> do: SAVE”FILE.BA” and it is now a tokenized BASIC file.
>>
>> I’ll get these renamed and include the tokenized version in the future to
>> avoid such confusion.
>>
>>
>>
>> Jeff Birt
>>
>>
>>
>> *From:* M100  *On Behalf Of *
>> grima...@gmail.com
>> *Sent:* Saturday, February 25, 2023 7:19 PM
>> *To:* m...@bitchin100.com
>> *Subject:* Re: [M100] - Backpack
>>
>>
>>
>> Random question - Does a BASIC program already exist to interface with
>> the Backpack to set the clock?
>>
>>
>>
>> I find myself having to Cold start the machine often, but this handy
>> Backpack has a real time clock in it.
>>
>>
>>
>> Would be great to run a quick program that interfaces with the Backpack
>> over serial, issues the TIME, DATE and DAY commands, queries the current
>> system time and date, calculates the delta and then resets the system clock.
>>
>>
>>
>> I started to write the program in BASIC, but I admit I don’t know much
>> about serial communication. I managed to open the COM buffer for output,
>> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
>> that, close the buffer, reopen it for input and then try to get the result.
>>
>>
>>
>> However I only end up with:
>>
>>
>>
>> C
>>
>> #
>>
>> T
>>
>>
>>
>> As if the second PRINT never went through.
>>
>>
>>
>> So rather than continue to rack my brain, I figured I’d ask if it already
>> exists.
>>
>>
>>
>> -George
>>
>>
>>
>> On Fri, Feb 17, 2023 at 4:44 PM Mike Stein  wrote:
>>
>> It might not be that straightforward; the printer port is partially
>> shared with the keyboard.
>>
>>
>>
>> On Fri, Feb 17, 2023 at 10:58 AM Alex ... 
>> wrote:
>>
>> Wire a R2R DAC to the printer port and have the M100 play music Covox
>> style. 
>>
>>
>>
>> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>>
>> All it needs in its next version is an 8mm stereo jack, an mp3 player and
>> some jukebox software for the laptop!
>>
>> Too much to wish for? No matter, it’s already a great piece of kit. :-)
>>
>>
>>
>> Sean
>>
>>
>>
>>
>>
>> On Feb 14, 2023, at 8:08 PM,  <
>> bir...@soigeneris.com> wrote:
>>
>>
>>
>> The Backpack was designed by a friend of mine who wishes to remain
>> private. He sent me one and I thought it was great and encouraged him to
>> make more offering my help. My only part of the design was the case.
>>
>>
>>
>> Jeff Birt
>>
>>
>>
>> *From:* M100  *On Behalf Of *
>> grima...@gmail.com
>> *Sent:* Tuesday, February 14, 2023 1:15 PM
>> *To:* Model 100 Discussion 
>> *Subject:* [M100] - Backpack
>>
>>
>>
>> Just received my Backpack from Soigeneris. All I have to say, is that I
>> really like the design of it all. It’s relatively compact, it matches the
>> design of the M100, and it runs on a single AA cell.
>>
>>
>>
>> I immediately plugged it in, and got it to work. Pretty much zero
>> configuration needed. I’ve already got REX installed so I was able to load
>> up TS-DOS and be off to the races.
>>
>>
>>
>> Shout out to Soigeneris and to whomever designed and built this device!
>>
>>
>>
>> Best,
>>
>> George
>>
>>
>>
>>

Re: [M100] - Backpack

[John R. Hogerhuis]

On Sat, Feb 25, 2023, 8:18 PM Mike Stein  wrote:

> Yeah, I guess everybody has TS-DOS in ROM one way or another these days;
> I've thought about putting it in the system ROM instead of the Scheduler
> and Address Book, but removing them doesn't really free up much space;
> maybe Teeny would fit...
>
>
Scheduler and address book are a very simple "grep" type utility serving as
a simple database. I feel they are too clever and minimalist a solution to
remove :-) plus there are programs that let you use this search facility on
any text file.

-- John.

>
>

Re: [M100] - Backpack

[Mike Stein]

Yeah, I guess everybody has TS-DOS in ROM one way or another these days;
I've thought about putting it in the system ROM instead of the Scheduler
and Address Book, but removing them doesn't really free up much space;
maybe Teeny would fit...

On Sat, Feb 25, 2023 at 10:02 PM grima...@gmail.com 
wrote:

> Thanks Gary!
>
> Mike - I have TS-DOS in ROM thanks to REX. So after a cold start, I just
> need to activate TS-DOS, copy RTC from Backpack, and run it.
>
> Best,
> George
>
> On Sat, Feb 25, 2023 at 9:21 PM Gary Weber  wrote:
>
>> Hi George,
>>
>> Yes you can configure the way the date is represented by your backpack
>> sending commands to it when it is in regular serial mode:
>> It's on page 37 of the User Manual, and here's a summary:
>>
>> To switch between 24-hour and 12-hour time format:
>> set time 24
>> set time ampm
>>
>> To switch between date formats:
>> set date mdy
>> set date dmy
>> set date ymd
>>
>> Cheers,
>> Gary
>>
>>
>> On Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com 
>> wrote:
>>
>>> Thank you!
>>>
>>> I typed it in from GitHub. what I found is my Backpack is setup to reply
>>> with dd/mm/.
>>>
>>> However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA
>>> program seems to assume the date will come back in the correct format.
>>>
>>> Does the Backpack have a way to configure the output format?
>>>
>>> In the meantime i altered the program and it works fine!
>>>
>>> Best,
>>> George
>>>
>>> On Sat, Feb 25, 2023 at 8:30 PM  wrote:
>>>
>>>> Yes, someone already wrote such a program and shared it. If you just
>>>> got a Backpack Drive Plus it is already on the SD card. You can also
>>>> download it from:
>>>> https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>>>>
>>>>
>>>>
>>>> There is an MT version and NEC version. Note that while these have a
>>>> .BA extension they are really text files, a.k.a. .DO files. It has been the
>>>> convention to give BASIC programs shared as text files the .BA extension
>>>> but if you try to load such a file as is BASIC will try to parse it on the
>>>> fly and it can’t do so fast enough. The file extension needs to be changed
>>>> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads
>>>> do: SAVE”FILE.BA” and it is now a tokenized BASIC file.
>>>>
>>>> I’ll get these renamed and include the tokenized version in the future
>>>> to avoid such confusion.
>>>>
>>>>
>>>>
>>>> Jeff Birt
>>>>
>>>>
>>>>
>>>> *From:* M100  *On Behalf Of *
>>>> grima...@gmail.com
>>>> *Sent:* Saturday, February 25, 2023 7:19 PM
>>>> *To:* m...@bitchin100.com
>>>> *Subject:* Re: [M100] - Backpack
>>>>
>>>>
>>>>
>>>> Random question - Does a BASIC program already exist to interface with
>>>> the Backpack to set the clock?
>>>>
>>>>
>>>>
>>>> I find myself having to Cold start the machine often, but this handy
>>>> Backpack has a real time clock in it.
>>>>
>>>>
>>>>
>>>> Would be great to run a quick program that interfaces with the Backpack
>>>> over serial, issues the TIME, DATE and DAY commands, queries the current
>>>> system time and date, calculates the delta and then resets the system 
>>>> clock.
>>>>
>>>>
>>>>
>>>> I started to write the program in BASIC, but I admit I don’t know much
>>>> about serial communication. I managed to open the COM buffer for output,
>>>> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
>>>> that, close the buffer, reopen it for input and then try to get the result.
>>>>
>>>>
>>>>
>>>> However I only end up with:
>>>>
>>>>
>>>>
>>>> C
>>>>
>>>> #
>>>>
>>>> T
>>>>
>>>>
>>>>
>>>> As if the second PRINT never went through.
>>>>
>>>>
>>>>
>>>> So rather than continue to rack my brain, I figured I’d ask if it
>>>> already exists.
>>>>
>>>>
>>>>
>>>

Re: [M100] - Backpack

[Mike Stein]

https://www.soigeneris.com/vintage-computing?pagenumber=3

On Sat, Feb 25, 2023 at 9:27 PM ho collo  wrote:

> I have been searching for a source to actually purchase a backpack for a
> Model 100. Does anyone have a source where I can purchase a unit?
>
> Google has not been my friend.
>
> Sent from my iPhone
>
> On Feb 25, 2023, at 20:21, Gary Weber  wrote:
>
> 
> Hi George,
>
> Yes you can configure the way the date is represented by your backpack
> sending commands to it when it is in regular serial mode:
> It's on page 37 of the User Manual, and here's a summary:
>
> To switch between 24-hour and 12-hour time format:
> set time 24
> set time ampm
>
> To switch between date formats:
> set date mdy
> set date dmy
> set date ymd
>
> Cheers,
> Gary
>
>
> On Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com 
> wrote:
>
>> Thank you!
>>
>> I typed it in from GitHub. what I found is my Backpack is setup to reply
>> with dd/mm/.
>>
>> However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA
>> program seems to assume the date will come back in the correct format.
>>
>> Does the Backpack have a way to configure the output format?
>>
>> In the meantime i altered the program and it works fine!
>>
>> Best,
>> George
>>
>> On Sat, Feb 25, 2023 at 8:30 PM  wrote:
>>
>>> Yes, someone already wrote such a program and shared it. If you just got
>>> a Backpack Drive Plus it is already on the SD card. You can also download
>>> it from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>>>
>>>
>>>
>>> There is an MT version and NEC version. Note that while these have a .BA
>>> extension they are really text files, a.k.a. .DO files. It has been the
>>> convention to give BASIC programs shared as text files the .BA extension
>>> but if you try to load such a file as is BASIC will try to parse it on the
>>> fly and it can’t do so fast enough. The file extension needs to be changed
>>> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads
>>> do: SAVE”FILE.BA” and it is now a tokenized BASIC file.
>>>
>>> I’ll get these renamed and include the tokenized version in the future
>>> to avoid such confusion.
>>>
>>>
>>>
>>> Jeff Birt
>>>
>>>
>>>
>>> *From:* M100  *On Behalf Of *
>>> grima...@gmail.com
>>> *Sent:* Saturday, February 25, 2023 7:19 PM
>>> *To:* m...@bitchin100.com
>>> *Subject:* Re: [M100] - Backpack
>>>
>>>
>>>
>>> Random question - Does a BASIC program already exist to interface with
>>> the Backpack to set the clock?
>>>
>>>
>>>
>>> I find myself having to Cold start the machine often, but this handy
>>> Backpack has a real time clock in it.
>>>
>>>
>>>
>>> Would be great to run a quick program that interfaces with the Backpack
>>> over serial, issues the TIME, DATE and DAY commands, queries the current
>>> system time and date, calculates the delta and then resets the system clock.
>>>
>>>
>>>
>>> I started to write the program in BASIC, but I admit I don’t know much
>>> about serial communication. I managed to open the COM buffer for output,
>>> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
>>> that, close the buffer, reopen it for input and then try to get the result.
>>>
>>>
>>>
>>> However I only end up with:
>>>
>>>
>>>
>>> C
>>>
>>> #
>>>
>>> T
>>>
>>>
>>>
>>> As if the second PRINT never went through.
>>>
>>>
>>>
>>> So rather than continue to rack my brain, I figured I’d ask if it
>>> already exists.
>>>
>>>
>>>
>>> -George
>>>
>>>
>>>
>>> On Fri, Feb 17, 2023 at 4:44 PM Mike Stein  wrote:
>>>
>>> It might not be that straightforward; the printer port is partially
>>> shared with the keyboard.
>>>
>>>
>>>
>>> On Fri, Feb 17, 2023 at 10:58 AM Alex ... 
>>> wrote:
>>>
>>> Wire a R2R DAC to the printer port and have the M100 play music Covox
>>> style. 
>>>
>>>
>>>
>>> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>>>
>>> All it needs in its next version is an 8mm stereo jack, an 

Re: [M100] - Backpack

[grima...@gmail.com]

Thanks Gary!

Mike - I have TS-DOS in ROM thanks to REX. So after a cold start, I just
need to activate TS-DOS, copy RTC from Backpack, and run it.

Best,
George

On Sat, Feb 25, 2023 at 9:21 PM Gary Weber  wrote:

> Hi George,
>
> Yes you can configure the way the date is represented by your backpack
> sending commands to it when it is in regular serial mode:
> It's on page 37 of the User Manual, and here's a summary:
>
> To switch between 24-hour and 12-hour time format:
> set time 24
> set time ampm
>
> To switch between date formats:
> set date mdy
> set date dmy
> set date ymd
>
> Cheers,
> Gary
>
>
> On Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com 
> wrote:
>
>> Thank you!
>>
>> I typed it in from GitHub. what I found is my Backpack is setup to reply
>> with dd/mm/.
>>
>> However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA
>> program seems to assume the date will come back in the correct format.
>>
>> Does the Backpack have a way to configure the output format?
>>
>> In the meantime i altered the program and it works fine!
>>
>> Best,
>> George
>>
>> On Sat, Feb 25, 2023 at 8:30 PM  wrote:
>>
>>> Yes, someone already wrote such a program and shared it. If you just got
>>> a Backpack Drive Plus it is already on the SD card. You can also download
>>> it from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>>>
>>>
>>>
>>> There is an MT version and NEC version. Note that while these have a .BA
>>> extension they are really text files, a.k.a. .DO files. It has been the
>>> convention to give BASIC programs shared as text files the .BA extension
>>> but if you try to load such a file as is BASIC will try to parse it on the
>>> fly and it can’t do so fast enough. The file extension needs to be changed
>>> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads
>>> do: SAVE”FILE.BA” and it is now a tokenized BASIC file.
>>>
>>> I’ll get these renamed and include the tokenized version in the future
>>> to avoid such confusion.
>>>
>>>
>>>
>>> Jeff Birt
>>>
>>>
>>>
>>> *From:* M100  *On Behalf Of *
>>> grima...@gmail.com
>>> *Sent:* Saturday, February 25, 2023 7:19 PM
>>> *To:* m...@bitchin100.com
>>> *Subject:* Re: [M100] - Backpack
>>>
>>>
>>>
>>> Random question - Does a BASIC program already exist to interface with
>>> the Backpack to set the clock?
>>>
>>>
>>>
>>> I find myself having to Cold start the machine often, but this handy
>>> Backpack has a real time clock in it.
>>>
>>>
>>>
>>> Would be great to run a quick program that interfaces with the Backpack
>>> over serial, issues the TIME, DATE and DAY commands, queries the current
>>> system time and date, calculates the delta and then resets the system clock.
>>>
>>>
>>>
>>> I started to write the program in BASIC, but I admit I don’t know much
>>> about serial communication. I managed to open the COM buffer for output,
>>> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
>>> that, close the buffer, reopen it for input and then try to get the result.
>>>
>>>
>>>
>>> However I only end up with:
>>>
>>>
>>>
>>> C
>>>
>>> #
>>>
>>> T
>>>
>>>
>>>
>>> As if the second PRINT never went through.
>>>
>>>
>>>
>>> So rather than continue to rack my brain, I figured I’d ask if it
>>> already exists.
>>>
>>>
>>>
>>> -George
>>>
>>>
>>>
>>> On Fri, Feb 17, 2023 at 4:44 PM Mike Stein  wrote:
>>>
>>> It might not be that straightforward; the printer port is partially
>>> shared with the keyboard.
>>>
>>>
>>>
>>> On Fri, Feb 17, 2023 at 10:58 AM Alex ... 
>>> wrote:
>>>
>>> Wire a R2R DAC to the printer port and have the M100 play music Covox
>>> style. 
>>>
>>>
>>>
>>> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>>>
>>> All it needs in its next version is an 8mm stereo jack, an mp3 player
>>> and some jukebox software for the laptop!
>>>
>>> Too much to wish for? No matter, it’s already a great piece of kit. :-)
>>>
&

Re: [M100] - Backpack

[ho collo]

I have been searching for a source to actually purchase a backpack for a Model 100. Does anyone have a source where I can purchase a unit?Google has not been my friend. Sent from my iPhoneOn Feb 25, 2023, at 20:21, Gary Weber  wrote:Hi George,Yes you can configure the way the date is represented by your backpack sending commands to it when it is in regular serial mode:It's on page 37 of the User Manual, and here's a summary:To switch between 24-hour and 12-hour time format:set time 24set time ampmTo switch between date formats:set date mdyset date dmyset date ymdCheers,GaryOn Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com <grima...@gmail.com> wrote:Thank you!I typed it in from GitHub. what I found is my Backpack is setup to reply with dd/mm/.However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA program seems to assume the date will come back in the correct format.Does the Backpack have a way to configure the output format? In the meantime i altered the program and it works fine!Best,GeorgeOn Sat, Feb 25, 2023 at 8:30 PM <bir...@soigeneris.com> wrote:Yes, someone already wrote such a program and shared it. If you just got a Backpack Drive Plus it is already on the SD card. You can also download it from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs  There is an MT version and NEC version. Note that while these have a .BA extension they are really text files, a.k.a. .DO files. It has been the convention to give BASIC programs shared as text files the .BA extension but if you try to load such a file as is BASIC will try to parse it on the fly and it can’t do so fast enough. The file extension needs to be changed to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads do: SAVE”FILE.BA” and it is now a tokenized BASIC file. I’ll get these renamed and include the tokenized version in the future to avoid such confusion. Jeff Birt From: M100 <m100-boun...@lists.bitchin100.com> On Behalf Of grima...@gmail.comSent: Saturday, February 25, 2023 7:19 PMTo: m...@bitchin100.comSubject: Re: [M100] - Backpack Random question - Does a BASIC program already exist to interface with the Backpack to set the clock? I find myself having to Cold start the machine often, but this handy Backpack has a real time clock in it. Would be great to run a quick program that interfaces with the Backpack over serial, issues the TIME, DATE and DAY commands, queries the current system time and date, calculates the delta and then resets the system clock. I started to write the program in BASIC, but I admit I don’t know much about serial communication. I managed to open the COM buffer for output, send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after that, close the buffer, reopen it for input and then try to get the result. However I only end up with: C#T As if the second PRINT never went through. So rather than continue to rack my brain, I figured I’d ask if it already exists. -George On Fri, Feb 17, 2023 at 4:44 PM Mike Stein <mhs.st...@gmail.com> wrote:It might not be that straightforward; the printer port is partially shared with the keyboard. On Fri, Feb 17, 2023 at 10:58 AM Alex ... <abortretryf...@gmail.com> wrote:Wire a R2R DAC to the printer port and have the M100 play music Covox style.  On Wed, Feb 15, 2023, 14:21 Fisher <nolan...@fisher25.ca> wrote:All it needs in its next version is an 8mm stereo jack, an mp3 player and some jukebox software for the laptop!Too much to wish for? No matter, it’s already a great piece of kit. :-) Sean On Feb 14, 2023, at 8:08 PM, <bir...@soigeneris.com> <bir...@soigeneris.com> wrote: The Backpack was designed by a friend of mine who wishes to remain private. He sent me one and I thought it was great and encouraged him to make more offering my help. My only part of the design was the case.  Jeff Birt From: M100 <m100-boun...@lists.bitchin100.com> On Behalf Of grima...@gmail.comSent: Tuesday, February 14, 2023 1:15 PMTo: Model 100 Discussion <m100@lists.bitchin100.com>Subject: [M100] - Backpack Just received my Backpack from Soigeneris. All I have to say, is that I really like the design of it all. It’s relatively compact, it matches the design of the M100, and it runs on a single AA cell. I immediately plugged it in, and got it to work. Pretty much zero configuration needed. I’ve already got REX installed so I was able to load up TS-DOS and be off to the races. Shout out to Soigeneris and to whomever designed and built this device! Best,George 

Re: [M100] - Backpack

[Gary Weber]

Hi George,

Yes you can configure the way the date is represented by your backpack
sending commands to it when it is in regular serial mode:
It's on page 37 of the User Manual, and here's a summary:

To switch between 24-hour and 12-hour time format:
set time 24
set time ampm

To switch between date formats:
set date mdy
set date dmy
set date ymd

Cheers,
Gary


On Sat, Feb 25, 2023 at 7:16 PM grima...@gmail.com 
wrote:

> Thank you!
>
> I typed it in from GitHub. what I found is my Backpack is setup to reply
> with dd/mm/.
>
> However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA
> program seems to assume the date will come back in the correct format.
>
> Does the Backpack have a way to configure the output format?
>
> In the meantime i altered the program and it works fine!
>
> Best,
> George
>
> On Sat, Feb 25, 2023 at 8:30 PM  wrote:
>
>> Yes, someone already wrote such a program and shared it. If you just got
>> a Backpack Drive Plus it is already on the SD card. You can also download
>> it from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>>
>>
>>
>> There is an MT version and NEC version. Note that while these have a .BA
>> extension they are really text files, a.k.a. .DO files. It has been the
>> convention to give BASIC programs shared as text files the .BA extension
>> but if you try to load such a file as is BASIC will try to parse it on the
>> fly and it can’t do so fast enough. The file extension needs to be changed
>> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads
>> do: SAVE”FILE.BA” and it is now a tokenized BASIC file.
>>
>> I’ll get these renamed and include the tokenized version in the future to
>> avoid such confusion.
>>
>>
>>
>> Jeff Birt
>>
>>
>>
>> *From:* M100  *On Behalf Of *
>> grima...@gmail.com
>> *Sent:* Saturday, February 25, 2023 7:19 PM
>> *To:* m...@bitchin100.com
>> *Subject:* Re: [M100] - Backpack
>>
>>
>>
>> Random question - Does a BASIC program already exist to interface with
>> the Backpack to set the clock?
>>
>>
>>
>> I find myself having to Cold start the machine often, but this handy
>> Backpack has a real time clock in it.
>>
>>
>>
>> Would be great to run a quick program that interfaces with the Backpack
>> over serial, issues the TIME, DATE and DAY commands, queries the current
>> system time and date, calculates the delta and then resets the system clock.
>>
>>
>>
>> I started to write the program in BASIC, but I admit I don’t know much
>> about serial communication. I managed to open the COM buffer for output,
>> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
>> that, close the buffer, reopen it for input and then try to get the result.
>>
>>
>>
>> However I only end up with:
>>
>>
>>
>> C
>>
>> #
>>
>> T
>>
>>
>>
>> As if the second PRINT never went through.
>>
>>
>>
>> So rather than continue to rack my brain, I figured I’d ask if it already
>> exists.
>>
>>
>>
>> -George
>>
>>
>>
>> On Fri, Feb 17, 2023 at 4:44 PM Mike Stein  wrote:
>>
>> It might not be that straightforward; the printer port is partially
>> shared with the keyboard.
>>
>>
>>
>> On Fri, Feb 17, 2023 at 10:58 AM Alex ... 
>> wrote:
>>
>> Wire a R2R DAC to the printer port and have the M100 play music Covox
>> style. 
>>
>>
>>
>> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>>
>> All it needs in its next version is an 8mm stereo jack, an mp3 player and
>> some jukebox software for the laptop!
>>
>> Too much to wish for? No matter, it’s already a great piece of kit. :-)
>>
>>
>>
>> Sean
>>
>>
>>
>>
>>
>> On Feb 14, 2023, at 8:08 PM,  <
>> bir...@soigeneris.com> wrote:
>>
>>
>>
>> The Backpack was designed by a friend of mine who wishes to remain
>> private. He sent me one and I thought it was great and encouraged him to
>> make more offering my help. My only part of the design was the case.
>>
>>
>>
>> Jeff Birt
>>
>>
>>
>> *From:* M100  *On Behalf Of *
>> grima...@gmail.com
>> *Sent:* Tuesday, February 14, 2023 1:15 PM
>> *To:* Model 100 Discussion 
>> *Subject:* [M100] - Backpack
>>
>>
>>
>> Just received my Backpack from Soigeneris. All I have to say, is that I
>> really like the design of it all. It’s relatively compact, it matches the
>> design of the M100, and it runs on a single AA cell.
>>
>>
>>
>> I immediately plugged it in, and got it to work. Pretty much zero
>> configuration needed. I’ve already got REX installed so I was able to load
>> up TS-DOS and be off to the races.
>>
>>
>>
>> Shout out to Soigeneris and to whomever designed and built this device!
>>
>>
>>
>> Best,
>>
>> George
>>
>>
>>
>>

Re: [M100] - Backpack

[grima...@gmail.com]

Thank you!

I typed it in from GitHub. what I found is my Backpack is setup to reply
with dd/mm/.

However, Tandy BASIC appears to want the date in mm/dd/. The RTC.BA
program seems to assume the date will come back in the correct format.

Does the Backpack have a way to configure the output format?

In the meantime i altered the program and it works fine!

Best,
George

On Sat, Feb 25, 2023 at 8:30 PM  wrote:

> Yes, someone already wrote such a program and shared it. If you just got a
> Backpack Drive Plus it is already on the SD card. You can also download it
> from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>
>
>
> There is an MT version and NEC version. Note that while these have a .BA
> extension they are really text files, a.k.a. .DO files. It has been the
> convention to give BASIC programs shared as text files the .BA extension
> but if you try to load such a file as is BASIC will try to parse it on the
> fly and it can’t do so fast enough. The file extension needs to be changed
> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads
> do: SAVE”FILE.BA” and it is now a tokenized BASIC file.
>
> I’ll get these renamed and include the tokenized version in the future to
> avoid such confusion.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100  *On Behalf Of *
> grima...@gmail.com
> *Sent:* Saturday, February 25, 2023 7:19 PM
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] - Backpack
>
>
>
> Random question - Does a BASIC program already exist to interface with the
> Backpack to set the clock?
>
>
>
> I find myself having to Cold start the machine often, but this handy
> Backpack has a real time clock in it.
>
>
>
> Would be great to run a quick program that interfaces with the Backpack
> over serial, issues the TIME, DATE and DAY commands, queries the current
> system time and date, calculates the delta and then resets the system clock.
>
>
>
> I started to write the program in BASIC, but I admit I don’t know much
> about serial communication. I managed to open the COM buffer for output,
> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
> that, close the buffer, reopen it for input and then try to get the result.
>
>
>
> However I only end up with:
>
>
>
> C
>
> #
>
> T
>
>
>
> As if the second PRINT never went through.
>
>
>
> So rather than continue to rack my brain, I figured I’d ask if it already
> exists.
>
>
>
> -George
>
>
>
> On Fri, Feb 17, 2023 at 4:44 PM Mike Stein  wrote:
>
> It might not be that straightforward; the printer port is partially shared
> with the keyboard.
>
>
>
> On Fri, Feb 17, 2023 at 10:58 AM Alex ... 
> wrote:
>
> Wire a R2R DAC to the printer port and have the M100 play music Covox
> style. 
>
>
>
> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>
> All it needs in its next version is an 8mm stereo jack, an mp3 player and
> some jukebox software for the laptop!
>
> Too much to wish for? No matter, it’s already a great piece of kit. :-)
>
>
>
> Sean
>
>
>
>
>
> On Feb 14, 2023, at 8:08 PM,  <
> bir...@soigeneris.com> wrote:
>
>
>
> The Backpack was designed by a friend of mine who wishes to remain
> private. He sent me one and I thought it was great and encouraged him to
> make more offering my help. My only part of the design was the case.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100  *On Behalf Of *
> grima...@gmail.com
> *Sent:* Tuesday, February 14, 2023 1:15 PM
> *To:* Model 100 Discussion 
> *Subject:* [M100] - Backpack
>
>
>
> Just received my Backpack from Soigeneris. All I have to say, is that I
> really like the design of it all. It’s relatively compact, it matches the
> design of the M100, and it runs on a single AA cell.
>
>
>
> I immediately plugged it in, and got it to work. Pretty much zero
> configuration needed. I’ve already got REX installed so I was able to load
> up TS-DOS and be off to the races.
>
>
>
> Shout out to Soigeneris and to whomever designed and built this device!
>
>
>
> Best,
>
> George
>
>
>
>

Re: [M100] - Backpack

[Mike Stein]

If you just cold started, wouldn't that erase the program?

m

On Sat, Feb 25, 2023 at 8:20 PM grima...@gmail.com 
wrote:

> Random question - Does a BASIC program already exist to interface with the
> Backpack to set the clock?
>
> I find myself having to Cold start the machine often, but this handy
> Backpack has a real time clock in it.
>
> Would be great to run a quick program that interfaces with the Backpack
> over serial, issues the TIME, DATE and DAY commands, queries the current
> system time and date, calculates the delta and then resets the system clock.
>
> I started to write the program in BASIC, but I admit I don’t know much
> about serial communication. I managed to open the COM buffer for output,
> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
> that, close the buffer, reopen it for input and then try to get the result.
>
> However I only end up with:
>
> C
> #
> T
>
> As if the second PRINT never went through.
>
> So rather than continue to rack my brain, I figured I’d ask if it already
> exists.
>
> -George
>
> On Fri, Feb 17, 2023 at 4:44 PM Mike Stein  wrote:
>
>> It might not be that straightforward; the printer port is partially
>> shared with the keyboard.
>>
>> On Fri, Feb 17, 2023 at 10:58 AM Alex ... 
>> wrote:
>>
>>> Wire a R2R DAC to the printer port and have the M100 play music Covox
>>> style. 
>>>
>>> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>>>
>>>> All it needs in its next version is an 8mm stereo jack, an mp3 player
>>>> and some jukebox software for the laptop!
>>>> Too much to wish for? No matter, it’s already a great piece of kit. :-)
>>>>
>>>> Sean
>>>>
>>>>
>>>> On Feb 14, 2023, at 8:08 PM,  <
>>>> bir...@soigeneris.com> wrote:
>>>>
>>>> The Backpack was designed by a friend of mine who wishes to remain
>>>> private. He sent me one and I thought it was great and encouraged him to
>>>> make more offering my help. My only part of the design was the case.
>>>>
>>>> Jeff Birt
>>>>
>>>> *From:* M100  *On Behalf Of *
>>>> grima...@gmail.com
>>>> *Sent:* Tuesday, February 14, 2023 1:15 PM
>>>> *To:* Model 100 Discussion 
>>>> *Subject:* [M100] - Backpack
>>>>
>>>> Just received my Backpack from Soigeneris. All I have to say, is that I
>>>> really like the design of it all. It’s relatively compact, it matches the
>>>> design of the M100, and it runs on a single AA cell.
>>>>
>>>> I immediately plugged it in, and got it to work. Pretty much zero
>>>> configuration needed. I’ve already got REX installed so I was able to load
>>>> up TS-DOS and be off to the races.
>>>>
>>>> Shout out to Soigeneris and to whomever designed and built this device!
>>>>
>>>> Best,
>>>> George
>>>>
>>>>
>>>>

Re: [M100] - Backpack

[John R. Hogerhuis]

A side note but the reason files misnamed as BA cause a problem is that
tsdos will load them into the BASIC program region verbatim and  treat the
ASCII bytes as parts of binary formatted line numbers and tokens among
other problems, ultimately causing a corrupted RAM file system.

It was the convention on the old Club100 library  to name them this way but
it's now a bad practice.

-- John.




On Sat, Feb 25, 2023, 5:30 PM  wrote:

> Yes, someone already wrote such a program and shared it. If you just got a
> Backpack Drive Plus it is already on the SD card. You can also download it
> from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs
>
>
>
> There is an MT version and NEC version. Note that while these have a .BA
> extension they are really text files, a.k.a. .DO files. It has been the
> convention to give BASIC programs shared as text files the .BA extension
> but if you try to load such a file as is BASIC will try to parse it on the
> fly and it can’t do so fast enough. The file extension needs to be changed
> to .DO. Load it into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads
> do: SAVE”FILE.BA” and it is now a tokenized BASIC file.
>
> I’ll get these renamed and include the tokenized version in the future to
> avoid such confusion.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100  *On Behalf Of *
> grima...@gmail.com
> *Sent:* Saturday, February 25, 2023 7:19 PM
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] - Backpack
>
>
>
> Random question - Does a BASIC program already exist to interface with the
> Backpack to set the clock?
>
>
>
> I find myself having to Cold start the machine often, but this handy
> Backpack has a real time clock in it.
>
>
>
> Would be great to run a quick program that interfaces with the Backpack
> over serial, issues the TIME, DATE and DAY commands, queries the current
> system time and date, calculates the delta and then resets the system clock.
>
>
>
> I started to write the program in BASIC, but I admit I don’t know much
> about serial communication. I managed to open the COM buffer for output,
> send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
> that, close the buffer, reopen it for input and then try to get the result.
>
>
>
> However I only end up with:
>
>
>
> C
>
> #
>
> T
>
>
>
> As if the second PRINT never went through.
>
>
>
> So rather than continue to rack my brain, I figured I’d ask if it already
> exists.
>
>
>
> -George
>
>
>
> On Fri, Feb 17, 2023 at 4:44 PM Mike Stein  wrote:
>
> It might not be that straightforward; the printer port is partially shared
> with the keyboard.
>
>
>
> On Fri, Feb 17, 2023 at 10:58 AM Alex ... 
> wrote:
>
> Wire a R2R DAC to the printer port and have the M100 play music Covox
> style. 
>
>
>
> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>
> All it needs in its next version is an 8mm stereo jack, an mp3 player and
> some jukebox software for the laptop!
>
> Too much to wish for? No matter, it’s already a great piece of kit. :-)
>
>
>
> Sean
>
>
>
>
>
> On Feb 14, 2023, at 8:08 PM,  <
> bir...@soigeneris.com> wrote:
>
>
>
> The Backpack was designed by a friend of mine who wishes to remain
> private. He sent me one and I thought it was great and encouraged him to
> make more offering my help. My only part of the design was the case.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100  *On Behalf Of *
> grima...@gmail.com
> *Sent:* Tuesday, February 14, 2023 1:15 PM
> *To:* Model 100 Discussion 
> *Subject:* [M100] - Backpack
>
>
>
> Just received my Backpack from Soigeneris. All I have to say, is that I
> really like the design of it all. It’s relatively compact, it matches the
> design of the M100, and it runs on a single AA cell.
>
>
>
> I immediately plugged it in, and got it to work. Pretty much zero
> configuration needed. I’ve already got REX installed so I was able to load
> up TS-DOS and be off to the races.
>
>
>
> Shout out to Soigeneris and to whomever designed and built this device!
>
>
>
> Best,
>
> George
>
>
>
>

Re: [M100] - Backpack

[birt_j]

Yes, someone already wrote such a program and shared it. If you just got a 
Backpack Drive Plus it is already on the SD card. You can also download it 
from: https://github.com/Jeff-Birt/Backpack/tree/main/User_Programs 

 

There is an MT version and NEC version. Note that while these have a .BA 
extension they are really text files, a.k.a. .DO files. It has been the 
convention to give BASIC programs shared as text files the .BA extension but if 
you try to load such a file as is BASIC will try to parse it on the fly and it 
can’t do so fast enough. The file extension needs to be changed to .DO. Load it 
into RAM, go to BASIC and do: LOAD”FILE.DO”. After it loads do: SAVE”FILE.BA” 
and it is now a tokenized BASIC file. 

I’ll get these renamed and include the tokenized version in the future to avoid 
such confusion.

 

Jeff Birt

 

From: M100  On Behalf Of grima...@gmail.com
Sent: Saturday, February 25, 2023 7:19 PM
To: m...@bitchin100.com
Subject: Re: [M100] - Backpack

 

Random question - Does a BASIC program already exist to interface with the 
Backpack to set the clock?

 

I find myself having to Cold start the machine often, but this handy Backpack 
has a real time clock in it.

 

Would be great to run a quick program that interfaces with the Backpack over 
serial, issues the TIME, DATE and DAY commands, queries the current system time 
and date, calculates the delta and then resets the system clock.

 

I started to write the program in BASIC, but I admit I don’t know much about 
serial communication. I managed to open the COM buffer for output, send the 
four CR to wake it. However, I then PRINT “TIME”+chr$(13) after that, close the 
buffer, reopen it for input and then try to get the result.

 

However I only end up with:

 

C

#

T

 

As if the second PRINT never went through.

 

So rather than continue to rack my brain, I figured I’d ask if it already 
exists.

 

-George

 

On Fri, Feb 17, 2023 at 4:44 PM Mike Stein mailto:mhs.st...@gmail.com> > wrote:

It might not be that straightforward; the printer port is partially shared with 
the keyboard.

 

On Fri, Feb 17, 2023 at 10:58 AM Alex ... mailto:abortretryf...@gmail.com> > wrote:

Wire a R2R DAC to the printer port and have the M100 play music Covox style. 

 

On Wed, Feb 15, 2023, 14:21 Fisher mailto:nolan...@fisher25.ca> > wrote:

All it needs in its next version is an 8mm stereo jack, an mp3 player and some 
jukebox software for the laptop!

Too much to wish for? No matter, it’s already a great piece of kit. :-)

 

Sean

 





On Feb 14, 2023, at 8:08 PM, mailto:bir...@soigeneris.com> > mailto:bir...@soigeneris.com> > wrote:

 

The Backpack was designed by a friend of mine who wishes to remain private. He 
sent me one and I thought it was great and encouraged him to make more offering 
my help. My only part of the design was the case. 

 

Jeff Birt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of grima...@gmail.com 
<mailto:grima...@gmail.com> 
Sent: Tuesday, February 14, 2023 1:15 PM
To: Model 100 Discussion mailto:m100@lists.bitchin100.com> >
Subject: [M100] - Backpack

 

Just received my Backpack from Soigeneris. All I have to say, is that I really 
like the design of it all. It’s relatively compact, it matches the design of 
the M100, and it runs on a single AA cell.

 

I immediately plugged it in, and got it to work. Pretty much zero configuration 
needed. I’ve already got REX installed so I was able to load up TS-DOS and be 
off to the races.

 

Shout out to Soigeneris and to whomever designed and built this device!

 

Best,

George

 

Re: [M100] - Backpack

[grima...@gmail.com]

Random question - Does a BASIC program already exist to interface with the
Backpack to set the clock?

I find myself having to Cold start the machine often, but this handy
Backpack has a real time clock in it.

Would be great to run a quick program that interfaces with the Backpack
over serial, issues the TIME, DATE and DAY commands, queries the current
system time and date, calculates the delta and then resets the system clock.

I started to write the program in BASIC, but I admit I don’t know much
about serial communication. I managed to open the COM buffer for output,
send the four CR to wake it. However, I then PRINT “TIME”+chr$(13) after
that, close the buffer, reopen it for input and then try to get the result.

However I only end up with:

C
#
T

As if the second PRINT never went through.

So rather than continue to rack my brain, I figured I’d ask if it already
exists.

-George

On Fri, Feb 17, 2023 at 4:44 PM Mike Stein  wrote:

> It might not be that straightforward; the printer port is partially shared
> with the keyboard.
>
> On Fri, Feb 17, 2023 at 10:58 AM Alex ... 
> wrote:
>
>> Wire a R2R DAC to the printer port and have the M100 play music Covox
>> style. 
>>
>> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>>
>>> All it needs in its next version is an 8mm stereo jack, an mp3 player
>>> and some jukebox software for the laptop!
>>> Too much to wish for? No matter, it’s already a great piece of kit. :-)
>>>
>>> Sean
>>>
>>>
>>> On Feb 14, 2023, at 8:08 PM,  <
>>> bir...@soigeneris.com> wrote:
>>>
>>> The Backpack was designed by a friend of mine who wishes to remain
>>> private. He sent me one and I thought it was great and encouraged him to
>>> make more offering my help. My only part of the design was the case.
>>>
>>> Jeff Birt
>>>
>>> *From:* M100  *On Behalf Of *
>>> grima...@gmail.com
>>> *Sent:* Tuesday, February 14, 2023 1:15 PM
>>> *To:* Model 100 Discussion 
>>> *Subject:* [M100] - Backpack
>>>
>>> Just received my Backpack from Soigeneris. All I have to say, is that I
>>> really like the design of it all. It’s relatively compact, it matches the
>>> design of the M100, and it runs on a single AA cell.
>>>
>>> I immediately plugged it in, and got it to work. Pretty much zero
>>> configuration needed. I’ve already got REX installed so I was able to load
>>> up TS-DOS and be off to the races.
>>>
>>> Shout out to Soigeneris and to whomever designed and built this device!
>>>
>>> Best,
>>> George
>>>
>>>
>>>

Re: [M100] - Backpack

[Mike Stein]

It might not be that straightforward; the printer port is partially shared
with the keyboard.

On Fri, Feb 17, 2023 at 10:58 AM Alex ...  wrote:

> Wire a R2R DAC to the printer port and have the M100 play music Covox
> style. 
>
> On Wed, Feb 15, 2023, 14:21 Fisher  wrote:
>
>> All it needs in its next version is an 8mm stereo jack, an mp3 player and
>> some jukebox software for the laptop!
>> Too much to wish for? No matter, it’s already a great piece of kit. :-)
>>
>> Sean
>>
>>
>> On Feb 14, 2023, at 8:08 PM,  <
>> bir...@soigeneris.com> wrote:
>>
>> The Backpack was designed by a friend of mine who wishes to remain
>> private. He sent me one and I thought it was great and encouraged him to
>> make more offering my help. My only part of the design was the case.
>>
>> Jeff Birt
>>
>> *From:* M100  *On Behalf Of *
>> grima...@gmail.com
>> *Sent:* Tuesday, February 14, 2023 1:15 PM
>> *To:* Model 100 Discussion 
>> *Subject:* [M100] - Backpack
>>
>> Just received my Backpack from Soigeneris. All I have to say, is that I
>> really like the design of it all. It’s relatively compact, it matches the
>> design of the M100, and it runs on a single AA cell.
>>
>> I immediately plugged it in, and got it to work. Pretty much zero
>> configuration needed. I’ve already got REX installed so I was able to load
>> up TS-DOS and be off to the races.
>>
>> Shout out to Soigeneris and to whomever designed and built this device!
>>
>> Best,
>> George
>>
>>
>>

Re: [M100] - Backpack

[Alex ...]

Wire a R2R DAC to the printer port and have the M100 play music Covox
style. 

On Wed, Feb 15, 2023, 14:21 Fisher  wrote:

> All it needs in its next version is an 8mm stereo jack, an mp3 player and
> some jukebox software for the laptop!
> Too much to wish for? No matter, it’s already a great piece of kit. :-)
>
> Sean
>
>
> On Feb 14, 2023, at 8:08 PM,  <
> bir...@soigeneris.com> wrote:
>
> The Backpack was designed by a friend of mine who wishes to remain
> private. He sent me one and I thought it was great and encouraged him to
> make more offering my help. My only part of the design was the case.
>
> Jeff Birt
>
> *From:* M100  *On Behalf Of *
> grima...@gmail.com
> *Sent:* Tuesday, February 14, 2023 1:15 PM
> *To:* Model 100 Discussion 
> *Subject:* [M100] - Backpack
>
> Just received my Backpack from Soigeneris. All I have to say, is that I
> really like the design of it all. It’s relatively compact, it matches the
> design of the M100, and it runs on a single AA cell.
>
> I immediately plugged it in, and got it to work. Pretty much zero
> configuration needed. I’ve already got REX installed so I was able to load
> up TS-DOS and be off to the races.
>
> Shout out to Soigeneris and to whomever designed and built this device!
>
> Best,
> George
>
>
>

Re: [M100] - Backpack

[Fisher]

All it needs in its next version is an 8mm stereo jack, an mp3 player and some 
jukebox software for the laptop!
Too much to wish for? No matter, it’s already a great piece of kit. :-)

Sean


> On Feb 14, 2023, at 8:08 PM,   
> wrote:
> 
> The Backpack was designed by a friend of mine who wishes to remain private. 
> He sent me one and I thought it was great and encouraged him to make more 
> offering my help. My only part of the design was the case. 
>  
> Jeff Birt
>  
> From: M100  On Behalf Of grima...@gmail.com
> Sent: Tuesday, February 14, 2023 1:15 PM
> To: Model 100 Discussion 
> Subject: [M100] - Backpack
>  
> Just received my Backpack from Soigeneris. All I have to say, is that I 
> really like the design of it all. It’s relatively compact, it matches the 
> design of the M100, and it runs on a single AA cell.
>  
> I immediately plugged it in, and got it to work. Pretty much zero 
> configuration needed. I’ve already got REX installed so I was able to load up 
> TS-DOS and be off to the races.
>  
> Shout out to Soigeneris and to whomever designed and built this device!
>  
> Best,
> George

Re: [M100] - Backpack

[birt_j]

The Backpack was designed by a friend of mine who wishes to remain private. He 
sent me one and I thought it was great and encouraged him to make more offering 
my help. My only part of the design was the case. 

 

Jeff Birt

 

From: M100  On Behalf Of grima...@gmail.com
Sent: Tuesday, February 14, 2023 1:15 PM
To: Model 100 Discussion 
Subject: [M100] - Backpack

 

Just received my Backpack from Soigeneris. All I have to say, is that I really 
like the design of it all. It’s relatively compact, it matches the design of 
the M100, and it runs on a single AA cell.

 

I immediately plugged it in, and got it to work. Pretty much zero configuration 
needed. I’ve already got REX installed so I was able to load up TS-DOS and be 
off to the races.

 

Shout out to Soigeneris and to whomever designed and built this device!

 

Best,

George

[M100] - Backpack

[grima...@gmail.com]

Just received my Backpack from Soigeneris. All I have to say, is that I
really like the design of it all. It’s relatively compact, it matches the
design of the M100, and it runs on a single AA cell.

I immediately plugged it in, and got it to work. Pretty much zero
configuration needed. I’ve already got REX installed so I was able to load
up TS-DOS and be off to the races.

Shout out to Soigeneris and to whomever designed and built this device!

Best,
George

Re: [M100] Backpack-Plus with REXCPM help

[Philippe Van Lieu]

Making sure my numbers are correct...

According to the M100 Service manual, R91, R94 and R99 were 5.6K Ohms. 
If I wanted to add in a resistor in parallel to bring it down to about 
330 Ohms, it appears that I would need to use a 350 Ohm resistor, based 
on the parallel resistor equation:


* 1/Rfinal = (1/Ra) + (1/Rb) + ...
* 1/330 = (1/5600) + (1/350)
* 1/330 = (350/196) + (5600/196)
* 1/330 = 5950/196
* 1/330 ~= 1/329.411764

Again, this is assuming the service manual is correct: 
https://archive.org/details/m100service/page/n73/mode/2up?q=R91


Personally, I'll just replace R91/94/99 resistors outright... but in 
case someone else reading this would rather add a resistor in parallel, 
then this should work right. Of course if you have no 350 Ohm resistor 
handy, you can just connect different ones in serial until it adds up to 
350 Ohms (like 150 + 150 + 50). And ABSOLUTELY make sure your own 
numbers are correct, like maybe your R91/94/99 resistors are something 
other than 5.6k Ohms; don't just take my word on it!


— Philippe


On 1/15/2023 1:03 PM, m100-requ...@lists.bitchin100.com wrote:
Yes, that would work too. If I am recalling correctly when I was 
experimenting with this problem, before getting hold of the tech 
bulletin I put something like a 10K in parallel and it was enough to 
make it ?just? work.


If I fitted a resistor in parallel instead of pulling the original and 
replacing it outright it would gnawl at until the end of my days. Yes, 
I have done such hacks when out in the field but it bugs me ?



Jeff Birt

Re: [M100] Backpack-Plus with REXCPM help

[Philippe Van Lieu]

Wow! I guess this also means we got some early editions of the M100, huh?

I appreciate you letting me know about the repair bulletin; fortunately 
I'm handy with a soldering iron so I should have no problem getting them 
swapped out. I'll also try setting the lookback switches away form the 
dot in the meantime. Heck, I'll even record the process; I've been 
looking for an excuse to make some M100-related videos! :D


Thanks again!

--- Philippe


On 1/13/2023 1:31 PM, m100-requ...@lists.bitchin100.com wrote:
Some of the original M100s have the wrong resistors in part of the 
RS232 handshake circuit. The voltage drop is so high that with the 
signal looped back it is just barely sufficient. The Backpack 
eavesdrops to know when to power itself back up and this minuscule 
additional load is too much. The symptom is that the Backpack responds 
once and then stops.


I have tried to attach a tech bulletin that Tandy put out back in the 
day that describes the fix. The alternative is to set both lookback 
switches away from the dot. The Backpack does not eavesdrop in this 
configuration so it can't wake itself up. You can adjust the timeout 
to compensate.


This is only the third M100 I've com across with this issue. I have 
one of them too ? At some point in the future I'll do a video on the 
fix per the Tandy tech bulletin.


Jeff Birt

Re: [M100] Backpack-Plus with REXCPM help

[birt_j]

Yes, that would work too. If I am recalling correctly when I was experimenting 
with this problem, before getting hold of the tech bulletin I put something 
like a 10K in parallel and it was enough to make it ‘just’ work. 

If I fitted a resistor in parallel instead of pulling the original and 
replacing it outright it would gnawl at until the end of my days. Yes, I have 
done such hacks when out in the field but it bugs me 

 

Jeff Birt

 

From: M100  On Behalf Of Stephen Adolph
Sent: Friday, January 13, 2023 6:29 PM
To: m...@bitchin100.com
Subject: Re: [M100] Backpack-Plus with REXCPM help

 

Or just solder on in parallel right? The result would be pretty much the same.

 

 

On Friday, January 13, 2023, mailto:bir...@soigeneris.com> > wrote:

No, it is a simple fix. Just a few resistors to swap out.

 

 

 

Jeff Birt

 

 

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Peter Vollan

Sent: Friday, January 13, 2023 5:13 PM

To: m...@bitchin100.com <mailto:m...@bitchin100.com> 

Subject: Re: [M100] Backpack-Plus with REXCPM help

 

 

 

I see that my Model 100 is one of the ones so afflicted. Is there any reason to 
not do the repair?

 

 

 

On Fri, 13 Jan 2023 at 14:14, Stephen Adolph mailto:twospru...@gmail.com> > wrote:

 

 

 

Hmm. 3 of my 10 M100 have this defect.

 

Good to know!! 

 

 

 

On Friday, January 13, 2023, mailto:bir...@soigeneris.com> > wrote:

 

 

 

Some of the original M100s have the wrong resistors in part of the RS232 
handshake circuit. The voltage drop is so high that with the signal looped back 
it is just barely sufficient. The Backpack eavesdrops to know when to power 
itself back up and this minuscule additional load is too much. The symptom is 
that the Backpack responds once and then stops.

 

 

 

I have tried to attach a tech bulletin that Tandy put out back in the day that 
describes the fix but it was too large. I zipped it up with the M200 andM600 
tech bulletins here: 
https://1drv.ms/u/s!AtH4vpaZnzX7lq9GsKp0I4qvY59yCw?e=yAcrwQ The alternative is 
to set both lookback switches away from the dot. The Backpack does not 
eavesdrop in this configuration so it can't wake itself up. You can adjust the 
timeout to compensate.

 

 

 

This is only the third M100 I've com across with this issue. I have one of them 
too  At some point in the future I'll do a video on the fix per the Tandy tech 
bulletin.

 

 

 

Jeff Birt

 

 

 

-Original Message-

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Philippe Van Lieu

 

Sent: Friday, January 13, 2023 2:02 PM

 

To: m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com> 

 

Subject: [M100] Backpack-Plus with REXCPM help

 

 

 

Hello everyone! I recently bought the Backpack-Plus for the M100, and I LOVE 
the thing. I want to thank you Jeff Birt/soigeneris for making this wonderful 
device to help keep these classic machines alive!

 

 

 

That said, I'm having an issue getting it to work properly on my REXCPM-powered 
M100. Fortunately the Backpack works fine on my normal

 

M100 so I figure the Backpack isn't the issue, but every time I try to run it 
on TS-DOS on my REXCPM'd M100, I get a "device not ready" error albeit after 
working only once beforehand.

 

 

 

I read the instructions and tried to adjust the timeout/sleep settings to 
something like 5 minutes via the CLI, but that didn't affect it. I also read 
the "Use with CP/M-100 and REXCPM", but that's just the initial installation 
instructions. I also saw the suggestion of using TS-DOS v4 or higher, but that 
also didn't have a positive effect.

 

Finally, a saw the paragraph on page 45 about making sure that the LOOP switch 
is set to LOOP in order to ensure TS-DOS keeps the Backpack-Plus awake, but 
neither that nor power cycling the Backpack-Plus woke it up.

 

 

 

So I'm at a loss on what I can do to get it working. I went through the

 

M100 mailing list archive, and it sounds like other REXCPM users haven't had 
any issues using the Backpack... so I suspect that maybe I'm doing something 
wrong. I'm open to any suggestions, and I thank you ahead of time for your help!

 

 

 

--- Philippe

 

 

 

 

 

 

 

 

 

 

 

 

 

Re: [M100] Backpack-Plus with REXCPM help

[John R. Hogerhuis]

Makes sense, thanks for the detail.

-- John.

Re: [M100] Backpack-Plus with REXCPM help

[Stephen Adolph]

Or just solder on in parallel right? The result would be pretty much the
same.


On Friday, January 13, 2023,  wrote:
No, it is a simple fix. Just a few resistors to swap out.



Jeff Birt



From: M100  On Behalf Of Peter Vollan
Sent: Friday, January 13, 2023 5:13 PM
To: m...@bitchin100.com
Subject: Re: [M100] Backpack-Plus with REXCPM help



I see that my Model 100 is one of the ones so afflicted. Is there any
reason to not do the repair?



On Fri, 13 Jan 2023 at 14:14, Stephen Adolph  wrote:



Hmm. 3 of my 10 M100 have this defect.

Good to know!!



On Friday, January 13, 2023,  wrote:



Some of the original M100s have the wrong resistors in part of the RS232
handshake circuit. The voltage drop is so high that with the signal looped
back it is just barely sufficient. The Backpack eavesdrops to know when to
power itself back up and this minuscule additional load is too much. The
symptom is that the Backpack responds once and then stops.



I have tried to attach a tech bulletin that Tandy put out back in the day
that describes the fix but it was too large. I zipped it up with the M200
andM600 tech bulletins here:
https://1drv.ms/u/s!AtH4vpaZnzX7lq9GsKp0I4qvY59yCw?e=yAcrwQ The alternative
is to set both lookback switches away from the dot. The Backpack does not
eavesdrop in this configuration so it can't wake itself up. You can adjust
the timeout to compensate.



This is only the third M100 I've com across with this issue. I have one of
them too  At some point in the future I'll do a video on the fix per the
Tandy tech bulletin.



Jeff Birt



-Original Message-

From: M100  On Behalf Of Philippe Van
Lieu

Sent: Friday, January 13, 2023 2:02 PM

To: m100@lists.bitchin100.com

Subject: [M100] Backpack-Plus with REXCPM help



Hello everyone! I recently bought the Backpack-Plus for the M100, and I
LOVE the thing. I want to thank you Jeff Birt/soigeneris for making this
wonderful device to help keep these classic machines alive!



That said, I'm having an issue getting it to work properly on my
REXCPM-powered M100. Fortunately the Backpack works fine on my normal

M100 so I figure the Backpack isn't the issue, but every time I try to run
it on TS-DOS on my REXCPM'd M100, I get a "device not ready" error albeit
after working only once beforehand.



I read the instructions and tried to adjust the timeout/sleep settings to
something like 5 minutes via the CLI, but that didn't affect it. I also
read the "Use with CP/M-100 and REXCPM", but that's just the initial
installation instructions. I also saw the suggestion of using TS-DOS v4 or
higher, but that also didn't have a positive effect.

Finally, a saw the paragraph on page 45 about making sure that the LOOP
switch is set to LOOP in order to ensure TS-DOS keeps the Backpack-Plus
awake, but neither that nor power cycling the Backpack-Plus woke it up.



So I'm at a loss on what I can do to get it working. I went through the

M100 mailing list archive, and it sounds like other REXCPM users haven't
had any issues using the Backpack... so I suspect that maybe I'm doing
something wrong. I'm open to any suggestions, and I thank you ahead of time
for your help!



--- Philippe

Re: [M100] Backpack-Plus with REXCPM help

[birt_j]

The Backpack has two modes of operation: CLI and TSDOS Server. Since it is 
powered by a single AA battery in order to conserve power it spends most of its 
time sleeping unless it is asked to do something.

 

In CLI mode it communicates with a terminal program on the host computer. This 
makes it easy to set time/date, mode of operation, or even transfer files via 
XModem. If it goes to sleep you can wake it up with 4 carriage returns in a row.

In TSDOS server mode it has to be a little smarter. TSDOS asserts DTR and 
expects to then find DSR set. To save power, so the Backpack does not need to 
stay powered on to provide the DSR signal you can set it to loop back the DTR 
signal from the computer, i.e. DTR to DSR. The Backpack is fast enough to wake 
up and handle requests from the TSDOS client on the computer by monitoring this 
looped back signal. It can remain in peaceful slumber using very little power 
until TSDOS wakes it up.

On the M100 there is a large resistor in the DTR output path AND a large 
resistor in the DSR input path. If you loop DRT to DSR the signal seen at the 
level shifting chip in the M100 is just over 1V (from my memory.) If the 
Backpack is also eavesdropping on this looped back signal the voltage goes 
below 1V and the M100 no longer sees the DSR signal.  According to the tech 
bulletin this was also a problem when trying to use the M100 with a few of 
Tandy’s own products at the time.

If you turn off the loopback switch for DSR/DTR the Backpack will have to 
generate DSR thus it needs to stay powered up. A work around is to turn the 
lookback off and then increase the sleep time to 2-5 minutes. Replacing the 
resistors is not difficult but it is a task that some folks don’t wish to do 
themselves, so the workaround is a good option.

I know of someone who has an NEC 8201A with this same issue though I have not 
dug into it in detail to see if they had updated this section of the circuitry.

 

Jeff Birt

 

From: M100  On Behalf Of John R. Hogerhuis
Sent: Friday, January 13, 2023 4:04 PM
To: m...@bitchin100.com
Subject: Re: [M100] Backpack-Plus with REXCPM help

 

Interesting. RS232 has always been marginal on the Model 100 but it's news to 
me that there was a needed repair.

 

I'm also interested to understand more about what's going on with the backpack.


You said it had to do with handshaking signalling and loopback, and what sounds 
like a powersave mode in the backpack reacting to the low signal.

 

What is "loop" feature on Backpack? Why is it necessary? Does Backpack not 
connect or assert DSR?

 

-- John.

Re: [M100] Backpack-Plus with REXCPM help

[birt_j]

No, it is a simple fix. Just a few resistors to swap out.

 

Jeff Birt

 

From: M100  On Behalf Of Peter Vollan
Sent: Friday, January 13, 2023 5:13 PM
To: m...@bitchin100.com
Subject: Re: [M100] Backpack-Plus with REXCPM help

 

I see that my Model 100 is one of the ones so afflicted. Is there any reason to 
not do the repair?

 

On Fri, 13 Jan 2023 at 14:14, Stephen Adolph mailto:twospru...@gmail.com> > wrote:

 

Hmm.  3 of my 10 M100 have this defect.

Good to know!! 

 

On Friday, January 13, 2023, mailto:bir...@soigeneris.com> > wrote:

 

Some of the original M100s have the wrong resistors in part of the RS232 
handshake circuit. The voltage drop is so high that with the signal looped back 
it is just barely sufficient. The Backpack eavesdrops to know when to power 
itself back up and this minuscule additional load is too much. The symptom is 
that the Backpack responds once and then stops.

 

I have tried to attach a tech bulletin that Tandy put out back in the day that 
describes the fix but it was too large. I zipped it up with the M200 andM600 
tech bulletins here: 
https://1drv.ms/u/s!AtH4vpaZnzX7lq9GsKp0I4qvY59yCw?e=yAcrwQ The alternative is 
to set both lookback switches away from the dot. The Backpack does not 
eavesdrop in this configuration so it can't wake itself up. You can adjust the 
timeout to compensate.

 

This is only the third M100 I've com across with this issue. I have one of them 
too  At some point in the future I'll do a video on the fix per the Tandy tech 
bulletin.

 

Jeff Birt

 

-Original Message-

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Philippe Van Lieu

Sent: Friday, January 13, 2023 2:02 PM

To: m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com> 

Subject: [M100] Backpack-Plus with REXCPM help

 

Hello everyone! I recently bought the Backpack-Plus for the M100, and I LOVE 
the thing. I want to thank you Jeff Birt/soigeneris for making this wonderful 
device to help keep these classic machines alive!

 

That said, I'm having an issue getting it to work properly on my REXCPM-powered 
M100. Fortunately the Backpack works fine on my normal

M100 so I figure the Backpack isn't the issue, but every time I try to run it 
on TS-DOS on my REXCPM'd M100, I get a "device not ready" error albeit after 
working only once beforehand.

 

I read the instructions and tried to adjust the timeout/sleep settings to 
something like 5 minutes via the CLI, but that didn't affect it. I also read 
the "Use with CP/M-100 and REXCPM", but that's just the initial installation 
instructions. I also saw the suggestion of using TS-DOS v4 or higher, but that 
also didn't have a positive effect.

Finally, a saw the paragraph on page 45 about making sure that the LOOP switch 
is set to LOOP in order to ensure TS-DOS keeps the Backpack-Plus awake, but 
neither that nor power cycling the Backpack-Plus woke it up.

 

So I'm at a loss on what I can do to get it working. I went through the

M100 mailing list archive, and it sounds like other REXCPM users haven't had 
any issues using the Backpack... so I suspect that maybe I'm doing something 
wrong. I'm open to any suggestions, and I thank you ahead of time for your help!

 

--- Philippe

 

 

 

 

 

Re: [M100] Backpack-Plus with REXCPM help

[Peter Vollan]

I see that my Model 100 is one of the ones so afflicted. Is there any
reason to not do the repair?

On Fri, 13 Jan 2023 at 14:14, Stephen Adolph  wrote:

>
>> Hmm.  3 of my 10 M100 have this defect.
> Good to know!!
>
>>
>> On Friday, January 13, 2023,  wrote:
>
>
>> Some of the original M100s have the wrong resistors in part of the RS232
>> handshake circuit. The voltage drop is so high that with the signal looped
>> back it is just barely sufficient. The Backpack eavesdrops to know when to
>> power itself back up and this minuscule additional load is too much. The
>> symptom is that the Backpack responds once and then stops.
>
>
>> I have tried to attach a tech bulletin that Tandy put out back in the day
>> that describes the fix but it was too large. I zipped it up with the M200
>> andM600 tech bulletins here:
>> https://1drv.ms/u/s!AtH4vpaZnzX7lq9GsKp0I4qvY59yCw?e=yAcrwQ The
>> alternative is to set both lookback switches away from the dot. The
>> Backpack does not eavesdrop in this configuration so it can't wake itself
>> up. You can adjust the timeout to compensate.
>
>
>> This is only the third M100 I've com across with this issue. I have one
>> of them too  At some point in the future I'll do a video on the fix per
>> the Tandy tech bulletin.
>
>
>> Jeff Birt
>
>
>> -Original Message-----
>
> From: M100  On Behalf Of Philippe Van
>> Lieu
>
> Sent: Friday, January 13, 2023 2:02 PM
>
> To: m100@lists.bitchin100.com
>
> Subject: [M100] Backpack-Plus with REXCPM help
>
>
>> Hello everyone! I recently bought the Backpack-Plus for the M100, and I
>> LOVE the thing. I want to thank you Jeff Birt/soigeneris for making this
>> wonderful device to help keep these classic machines alive!
>
>
>> That said, I'm having an issue getting it to work properly on my
>> REXCPM-powered M100. Fortunately the Backpack works fine on my normal
>
> M100 so I figure the Backpack isn't the issue, but every time I try to run
>> it on TS-DOS on my REXCPM'd M100, I get a "device not ready" error albeit
>> after working only once beforehand.
>
>
>> I read the instructions and tried to adjust the timeout/sleep settings to
>> something like 5 minutes via the CLI, but that didn't affect it. I also
>> read the "Use with CP/M-100 and REXCPM", but that's just the initial
>> installation instructions. I also saw the suggestion of using TS-DOS v4 or
>> higher, but that also didn't have a positive effect.
>
> Finally, a saw the paragraph on page 45 about making sure that the LOOP
>> switch is set to LOOP in order to ensure TS-DOS keeps the Backpack-Plus
>> awake, but neither that nor power cycling the Backpack-Plus woke it up.
>
>
>> So I'm at a loss on what I can do to get it working. I went through the
>
> M100 mailing list archive, and it sounds like other REXCPM users haven't
>> had any issues using the Backpack... so I suspect that maybe I'm doing
>> something wrong. I'm open to any suggestions, and I thank you ahead of time
>> for your help!
>
>
>> --- Philippe
>
>
>>
>>
>>
>>
>>

Re: [M100] Backpack-Plus with REXCPM help

[Stephen Adolph]

>
>
> Hmm.  3 of my 10 M100 have this defect.
Good to know!!

>
> On Friday, January 13, 2023,  wrote:


> Some of the original M100s have the wrong resistors in part of the RS232
> handshake circuit. The voltage drop is so high that with the signal looped
> back it is just barely sufficient. The Backpack eavesdrops to know when to
> power itself back up and this minuscule additional load is too much. The
> symptom is that the Backpack responds once and then stops.


> I have tried to attach a tech bulletin that Tandy put out back in the day
> that describes the fix but it was too large. I zipped it up with the M200
> andM600 tech bulletins here:
> https://1drv.ms/u/s!AtH4vpaZnzX7lq9GsKp0I4qvY59yCw?e=yAcrwQ The
> alternative is to set both lookback switches away from the dot. The
> Backpack does not eavesdrop in this configuration so it can't wake itself
> up. You can adjust the timeout to compensate.


> This is only the third M100 I've com across with this issue. I have one of
> them too  At some point in the future I'll do a video on the fix per the
> Tandy tech bulletin.


> Jeff Birt


> -Original Message-

From: M100  On Behalf Of Philippe Van
> Lieu

Sent: Friday, January 13, 2023 2:02 PM

To: m100@lists.bitchin100.com

Subject: [M100] Backpack-Plus with REXCPM help


> Hello everyone! I recently bought the Backpack-Plus for the M100, and I
> LOVE the thing. I want to thank you Jeff Birt/soigeneris for making this
> wonderful device to help keep these classic machines alive!


> That said, I'm having an issue getting it to work properly on my
> REXCPM-powered M100. Fortunately the Backpack works fine on my normal

M100 so I figure the Backpack isn't the issue, but every time I try to run
> it on TS-DOS on my REXCPM'd M100, I get a "device not ready" error albeit
> after working only once beforehand.


> I read the instructions and tried to adjust the timeout/sleep settings to
> something like 5 minutes via the CLI, but that didn't affect it. I also
> read the "Use with CP/M-100 and REXCPM", but that's just the initial
> installation instructions. I also saw the suggestion of using TS-DOS v4 or
> higher, but that also didn't have a positive effect.

Finally, a saw the paragraph on page 45 about making sure that the LOOP
> switch is set to LOOP in order to ensure TS-DOS keeps the Backpack-Plus
> awake, but neither that nor power cycling the Backpack-Plus woke it up.


> So I'm at a loss on what I can do to get it working. I went through the

M100 mailing list archive, and it sounds like other REXCPM users haven't
> had any issues using the Backpack... so I suspect that maybe I'm doing
> something wrong. I'm open to any suggestions, and I thank you ahead of time
> for your help!


> --- Philippe


>
>
>
>
>

Re: [M100] Backpack-Plus with REXCPM help

[John R. Hogerhuis]

Interesting. RS232 has always been marginal on the Model 100 but it's news
to me that there was a needed repair.

I'm also interested to understand more about what's going on with the
backpack.

You said it had to do with handshaking signalling and loopback, and what
sounds like a powersave mode in the backpack reacting to the low signal.

What is "loop" feature on Backpack? Why is it necessary? Does Backpack not
connect or assert DSR?

-- John.

On Fri, Jan 13, 2023 at 1:44 PM  wrote:

> Some of the original M100s have the wrong resistors in part of the RS232
> handshake circuit. The voltage drop is so high that with the signal looped
> back it is just barely sufficient. The Backpack eavesdrops to know when to
> power itself back up and this minuscule additional load is too much. The
> symptom is that the Backpack responds once and then stops.
>
> I have tried to attach a tech bulletin that Tandy put out back in the day
> that describes the fix. The alternative is to set both lookback switches
> away from the dot. The Backpack does not eavesdrop in this configuration so
> it can't wake itself up. You can adjust the timeout to compensate.
>
> This is only the third M100 I've com across with this issue. I have one of
> them too  At some point in the future I'll do a video on the fix per the
> Tandy tech bulletin.
>
> Jeff Birt
>
> -Original Message-
> From: M100  On Behalf Of Philippe Van
> Lieu
> Sent: Friday, January 13, 2023 2:02 PM
> To: m100@lists.bitchin100.com
> Subject: [M100] Backpack-Plus with REXCPM help
>
> Hello everyone! I recently bought the Backpack-Plus for the M100, and I
> LOVE the thing. I want to thank you Jeff Birt/soigeneris for making this
> wonderful device to help keep these classic machines alive!
>
> That said, I'm having an issue getting it to work properly on my
> REXCPM-powered M100. Fortunately the Backpack works fine on my normal
> M100 so I figure the Backpack isn't the issue, but every time I try to run
> it on TS-DOS on my REXCPM'd M100, I get a "device not ready" error albeit
> after working only once beforehand.
>
> I read the instructions and tried to adjust the timeout/sleep settings to
> something like 5 minutes via the CLI, but that didn't affect it. I also
> read the "Use with CP/M-100 and REXCPM", but that's just the initial
> installation instructions. I also saw the suggestion of using TS-DOS v4 or
> higher, but that also didn't have a positive effect.
> Finally, a saw the paragraph on page 45 about making sure that the LOOP
> switch is set to LOOP in order to ensure TS-DOS keeps the Backpack-Plus
> awake, but neither that nor power cycling the Backpack-Plus woke it up.
>
> So I'm at a loss on what I can do to get it working. I went through the
> M100 mailing list archive, and it sounds like other REXCPM users haven't
> had any issues using the Backpack... so I suspect that maybe I'm doing
> something wrong. I'm open to any suggestions, and I thank you ahead of time
> for your help!
>
> --- Philippe
>
>

Re: [M100] Backpack-Plus with REXCPM help

[birt_j]

Some of the original M100s have the wrong resistors in part of the RS232 
handshake circuit. The voltage drop is so high that with the signal looped back 
it is just barely sufficient. The Backpack eavesdrops to know when to power 
itself back up and this minuscule additional load is too much. The symptom is 
that the Backpack responds once and then stops.

I have tried to attach a tech bulletin that Tandy put out back in the day that 
describes the fix but it was too large. I zipped it up with the M200 andM600 
tech bulletins here: 
https://1drv.ms/u/s!AtH4vpaZnzX7lq9GsKp0I4qvY59yCw?e=yAcrwQ  The alternative is 
to set both lookback switches away from the dot. The Backpack does not 
eavesdrop in this configuration so it can't wake itself up. You can adjust the 
timeout to compensate.

This is only the third M100 I've com across with this issue. I have one of them 
too  At some point in the future I'll do a video on the fix per the Tandy tech 
bulletin.

Jeff Birt

-Original Message-
From: M100  On Behalf Of Philippe Van Lieu
Sent: Friday, January 13, 2023 2:02 PM
To: m100@lists.bitchin100.com
Subject: [M100] Backpack-Plus with REXCPM help

Hello everyone! I recently bought the Backpack-Plus for the M100, and I LOVE 
the thing. I want to thank you Jeff Birt/soigeneris for making this wonderful 
device to help keep these classic machines alive!

That said, I'm having an issue getting it to work properly on my REXCPM-powered 
M100. Fortunately the Backpack works fine on my normal
M100 so I figure the Backpack isn't the issue, but every time I try to run it 
on TS-DOS on my REXCPM'd M100, I get a "device not ready" error albeit after 
working only once beforehand.

I read the instructions and tried to adjust the timeout/sleep settings to 
something like 5 minutes via the CLI, but that didn't affect it. I also read 
the "Use with CP/M-100 and REXCPM", but that's just the initial installation 
instructions. I also saw the suggestion of using TS-DOS v4 or higher, but that 
also didn't have a positive effect. 
Finally, a saw the paragraph on page 45 about making sure that the LOOP switch 
is set to LOOP in order to ensure TS-DOS keeps the Backpack-Plus awake, but 
neither that nor power cycling the Backpack-Plus woke it up.

So I'm at a loss on what I can do to get it working. I went through the
M100 mailing list archive, and it sounds like other REXCPM users haven't had 
any issues using the Backpack... so I suspect that maybe I'm doing something 
wrong. I'm open to any suggestions, and I thank you ahead of time for your help!

--- Philippe

[M100] Backpack-Plus with REXCPM help

[Philippe Van Lieu]

Hello everyone! I recently bought the Backpack-Plus for the M100, and I 
LOVE the thing. I want to thank you Jeff Birt/soigeneris for making this 
wonderful device to help keep these classic machines alive!


That said, I'm having an issue getting it to work properly on my 
REXCPM-powered M100. Fortunately the Backpack works fine on my normal 
M100 so I figure the Backpack isn't the issue, but every time I try to 
run it on TS-DOS on my REXCPM'd M100, I get a "device not ready" error 
albeit after working only once beforehand.


I read the instructions and tried to adjust the timeout/sleep settings 
to something like 5 minutes via the CLI, but that didn't affect it. I 
also read the "Use with CP/M-100 and REXCPM", but that's just the 
initial installation instructions. I also saw the suggestion of using 
TS-DOS v4 or higher, but that also didn't have a positive effect. 
Finally, a saw the paragraph on page 45 about making sure that the LOOP 
switch is set to LOOP in order to ensure TS-DOS keeps the Backpack-Plus 
awake, but neither that nor power cycling the Backpack-Plus woke it up.


So I'm at a loss on what I can do to get it working. I went through the 
M100 mailing list archive, and it sounds like other REXCPM users haven't 
had any issues using the Backpack... so I suspect that maybe I'm doing 
something wrong. I'm open to any suggestions, and I thank you ahead of 
time for your help!


--- Philippe

Re: [M100] Backpack drives

[Philippe Van Lieu]

Awesome! Thanks for enabling the "notify when back in stock" button as well.

I also imagine it's tough to work out how many to make too, especially when 
there's also a bunch of silent fans like me who just like to lurk and know a 
good deal when we see it... so it's all the more appreciated that you're able 
to keep up with demand. Thank you very much! :D



On 12/22/2022 1:04 PM, m100-requ...@lists.bitchin100.com wrote:
I'm working on finishing up some more now. It was rather hard to guess 
at how many of which adapters folks might want but we are building 
more of the ones low in stock. I'm setting up each of the options as 
separate stock items so you can tell if the option you selected is in 
stock or not. (For example, I won't have more extra CR1025 batteries 
until next week.) I also just enabled the 'Notify when back in stock' 
button.

Jeff Birt

Re: [M100] Backpack drives

[birt_j]

I'm working on finishing up some more now. It was rather hard to guess at how 
many of which adapters folks might want but we are building more of the ones 
low in stock. I'm setting up each of the options as separate stock items so you 
can tell if the option you selected is in stock or not. (For example, I won't 
have more extra CR1025 batteries until next week.)  I also just enabled the 
'Notify when back in stock' button. 

Jeff Birt

-Original Message-
From: M100  On Behalf Of Philippe Van Lieu
Sent: Thursday, December 22, 2022 10:21 AM
To: m...@bitchin100.com
Subject: Re: [M100] Backpack drives

Any plans for a restock on the Backpacks? I was in the process of ordering one 
yesterday but I forgot to finish the process. So I thought to myself this 
morning "eh, it can't be THAT popular, I'll just finish the order now" and... 
nope, 'Out of Stock'. Ooof I deserve that!

If no restock is immediately planned, that's OK, I'll just do a better job of 
jumping on them whenever next time happens! Thanks!

Re: [M100] Backpack drives

[Philippe Van Lieu]

Any plans for a restock on the Backpacks? I was in the process of 
ordering one yesterday but I forgot to finish the process. So I thought 
to myself this morning "eh, it can't be THAT popular, I'll just finish 
the order now" and... nope, 'Out of Stock'. Ooof I deserve that!


If no restock is immediately planned, that's OK, I'll just do a better 
job of jumping on them whenever next time happens! Thanks!

Re: [M100] Backpack drives

[birt_j]

The thanks go to my friend who developed it. I’m happy to help make them 
available to folks. 

 

Jeff Birt

 

From: M100  On Behalf Of Louis Lipp
Sent: Wednesday, December 21, 2022 8:44 AM
To: m100@lists.bitchin100.com
Subject: [M100] Backpack drives

 

Thanks so much for letting us know they were back! These things disappeared in 
record time after the Z88 crew discovered that there was finally a solution out 
there for them! In fact I had just checked again the day before yesterday but 
there was nothing there yet.

I have been looking forward to a solution like this for so many years now..! 

Take care, Louis 

[M100] Backpack drives

[Louis Lipp]

Thanks so much for letting us know they were back! These things disappeared
in record time after the Z88 crew discovered that there was finally a
solution out there for them! In fact I had just checked again the day
before yesterday but there was nothing there yet.
I have been looking forward to a solution like this for so many years
now..!
Take care, Louis

Re: [M100] Backpack drives are back!

[Alastair Wiggins]

Many thanks Birt - very much appreciated! Just need to get my HX-20 working
now..

Alastair


>
> -- Forwarded message --
> From: 
> To: 
> Cc:
> Bcc:
> Date: Tue, 20 Dec 2022 07:22:03 -0600
> Subject: Re: [M100] Backpack drives are back!
>
> There is a Epson firmware for the original Backpack.  Grab the Epson zip
> file from:
>
>
>
> https://github.com/Jeff-Birt/Backpack/tree/main/BPD%20Files/SD_Card
>
>
>
> You need to put the entire directory structure inside the ZIP file on the
> root of your SD card. The .BIN file is the firmware. The firmware update is
> done by the CLI as shown in the Backpack manual.
>
>
>
> You will need to build an adapter from the odd serial ports Epson used to
> a standard DB25 or I do have a few adapters that my friend made but you
> will need mini-din cables for the adapter to plug into the Epson.
>
> The documentation for the Epson firmware is there too:
> https://github.com/Jeff-Birt/Backpack/tree/main/BPD%20Files/Documentation
>
>
>
> Jeff
>
>

Re: [M100] Backpack drives are back!

[birt_j]

There is a Epson firmware for the original Backpack.  Grab the Epson zip file 
from:

 

https://github.com/Jeff-Birt/Backpack/tree/main/BPD%20Files/SD_Card 

 

You need to put the entire directory structure inside the ZIP file on the root 
of your SD card. The .BIN file is the firmware. The firmware update is done by 
the CLI as shown in the Backpack manual. 

 

You will need to build an adapter from the odd serial ports Epson used to a 
standard DB25 or I do have a few adapters that my friend made but you will need 
mini-din cables for the adapter to plug into the Epson. 

The documentation for the Epson firmware is there too:
https://github.com/Jeff-Birt/Backpack/tree/main/BPD%20Files/Documentation 

 

Jeff



 

From: M100  On Behalf Of Alastair Wiggins
Sent: Monday, December 19, 2022 4:48 PM
To: m100@lists.bitchin100.com
Subject: Re: [M100] Backpack drives are back!

 

Hi Birt,

 

I purchased one of the older Backpack variants. Will it be possible to get this 
working with the HX-20 too? I already own an NEC-PC8210A and Tandy WP-2 (both 
supported), but have just received an HX-20 for refurbishment.

 

Many thanks,

 

Alastair

 

 

On Tue, 20 Dec 2022 at 08:07, mailto:m100-requ...@lists.bitchin100.com> > wrote:

Send M100 mailing list submissions to
m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com> 

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.com
or, via email, send a message with subject or body 'help' to
m100-requ...@lists.bitchin100.com 
<mailto:m100-requ...@lists.bitchin100.com> 

You can reach the person managing the list at
m100-ow...@lists.bitchin100.com 
<mailto:m100-ow...@lists.bitchin100.com> 

When replying, please edit your Subject line so it is more specific
than "Re: Contents of M100 digest..."
Today's Topics:

   1. Re: TS-DOS Option ROM (Peter Vollan)
   2. Re: Pinenut Wifi / BLE (Joseph Colson III)
   3. TS-DOS Option ROM (Joseph Colson III)
   4. Re: TS-DOS Option ROM (Wayne Lorentz)
   5. Re: TS-DOS Option ROM (Stephen Adolph)
   6. Re: TS-DOS Option ROM (Will Senn)
   7. Re: TS-DOS Option ROM (MikeS)
   8. Re: TS-DOS Option ROM (John R. Hogerhuis)
   9. Backpack drives are back! (bir...@soigeneris.com 
<mailto:bir...@soigeneris.com> )



-- Forwarded message --
From: Peter Vollan mailto:dprogra...@gmail.com> >
To: m...@bitchin100.com <mailto:m...@bitchin100.com> 
Cc: 
Bcc: 
Date: Sun, 18 Dec 2022 13:30:59 -0800
Subject: Re: [M100] TS-DOS Option ROM

Brian is right but I might have a TS DOS ROM for you. Are you in Seattle?

 

On Sun, 18 Dec 2022 at 07:27, Brian White mailto:b.kenyo...@gmail.com> > wrote:

I'd suggest get a REX#, which comes with ts-dos pre-loaded.

http://www.bitchin100.com/wiki/index.php?title=REX

 

You could build a plain rom with only ts-dos,

http://tandy.wiki/Teeprom

but it ends up costing almost the same as a REX# anyway plus more work.

--  

bkw

 

On Sun, Dec 18, 2022, 8:46 AM Wayne Lorentz mailto:wa...@lorentz.me> > wrote:

Does anyone know if TS-DOS option ROMS are still being sold anywhere?  I'd like 
to use one with TPDD Backpack.  

All the online searches point to the Bitchin' 100 web site, which doesn't 
appear to have been updated in 15 years.




-- Forwarded message --
From: Joseph Colson III mailto:joecols...@outlook.com> 
>
To: "m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com> " 
mailto:m100@lists.bitchin100.com> >
Cc: Joseph Colson III mailto:joecols...@outlook.com> >
Bcc: 
Date: Sun, 18 Dec 2022 21:54:14 +
Subject: Re: [M100] Pinenut Wifi / BLE

Hiraghm < <http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.com> 
hiraghm at hotmail.com> wrote:

> I came across this tiny little board on the Pine64 site, and I wonder...

 

 

I started using the WiRSa device sold here. (  
<https://www.ebay.com/itm/175299622202?var=474519028969> 
https://www.ebay.com/itm/175299622202?var=474519028969 )

I have had it for a month and after reading your post hooked it up and it works 
well, admittedly I have only used it a short time, but I was able to connect to 
a BBS using Telnet.   It allows you to use 300 baud.   It’s powered via 5volt 
USB type adapter.   It’s a bit large but will see if it can be shrunk down 
more.   I know there is room in the model 102 for this device as the lower half 
of the unit is open.   

 

Joe

KC5HRT 

 




-- Forwarded message --
From: Joseph Colson III mailto:joecols...@outlook.com> 
>
To: "m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com> " 
mailto:m100@lists.bitchin100.com> >
Cc: Joseph Colson III mailto:joecols...@outlook.com> >
Bcc: 
Date: Sun, 18 Dec 2022 22:20:28 +
Subject: [M100] TS-DOS Option ROM

I would agree that the REX# is the best option but there 

Re: [M100] Backpack drives are back!

[Alastair Wiggins]

 Original Message -
> *From:* Wayne Lorentz 
> *To:* m...@bitchin100.com
> *Sent:* Sunday, December 18, 2022 5:43 PM
> *Subject:* Re: [M100] TS-DOS Option ROM
>
> I thought about the REX#, but it looks discontinued.  There aren't any
> links on that page to order anything, and no contact information.   Not
> even a name.  Super sketchy.
>
> If I was going to get a REX, I'd get the CP/M version, as I'm a CP/M
> enthusiast. But $100 is more than I can do this close to Christmas. That's
> why I thought if I could find a TS-DOS chip, it might be cheap enough to
> tide me over.
>
> I recently bought one of those Backpack SD card storage devices. The
> TS-DOS option ROM will work with that, right?
>
> —
> iPhoneから送信
>
> On Dec 18, 2022, at 9:27 AM, Brian White  wrote:
>
> 
> I'd suggest get a REX#, which comes with ts-dos pre-loaded.
> http://www.bitchin100.com/wiki/index.php?title=REX
>
> You could build a plain rom with only ts-dos,
> http://tandy.wiki/Teeprom
> but it ends up costing almost the same as a REX# anyway plus more work.
>
> --
> bkw
>
>
>
>
> ------ Forwarded message --
> From: "John R. Hogerhuis" 
> To: m...@bitchin100.com
> Cc:
> Bcc:
> Date: Sun, 18 Dec 2022 16:21:31 -0800
> Subject: Re: [M100] TS-DOS Option ROM
>
>
> On Sun, Dec 18, 2022, 2:43 PM Wayne Lorentz  wrote:
>
>> I thought about the REX#, but it looks discontinued.  There aren't any
>> links on that page to order anything, and no contact information.   Not
>> even a name.  Super sketchy.
>>
>
> There's a ordering link on the Rex page
>
> https://bitchin100.com/wiki/index.php?title=REX
>
>
> https://bitchin100.com/wiki/index.php?title=Ordering_Information
>
> Steve's email is on that page but he encoded it so he doesn't get spam.
> Point is you can send him emails through that or he is also on this list.
>
> https://bitchin100.com/wiki/index.php?title=Ordering_Information
>
>
> FYI I run bitchin100 site and the bitchin100 wiki. Steve posts his product
> support documentation and contact info there. There is also the legacy
> Club100 site that Ken Pettit keeps going. The only content that changes
> much is the personal libraries. Most of the content is kept going as a
> information resource and a tribute to Rick Hanson, the original proprietor
> of Club100 who passed away.
>
> -- John.
>
>>
>
>
> -- Forwarded message --
> From: 
> To: 
> Cc:
> Bcc:
> Date: Mon, 19 Dec 2022 09:17:01 -0600
> Subject: [M100] Backpack drives are back!
>
> Hi all,
>
>
>
> A lot of folks have been asking when more Backpack drives will be
> available. As you know the chip shortage has made some parts impossible to
> obtain, including the microcontroller used in the original Backpack. My
> friend that designed the original Backpack found a newly released AVR
> processor that was actually available and designed the Backpack Drive Plus,
> or BPD+ if you prefer. It looks the same and works the same with a slightly
> lower current draw from the battery. He also made a number of adapters to
> use the Backpack with computers like the WP2, Sinclair Z88, Epson HX-20,
> Epson PX-8. The Epson’s have a separate firmware to simulate the original
> Epson disk drives.
>
>
>
> We had a waiting list of folks who had asked for one and have worked
> through that list so now ordering is open to the public. We are still 3D
> printing cases and finishing the units up. If the stock level shows zero,
> try again in a few days. When we run out, I will note that on the webpage.
>
>
>
> https://www.soigeneris.com/tandy-tpdd-2-backpack-drive-2
>
>
>
> Jeff Birt
> ___
> M100 mailing list
> M100@lists.bitchin100.com
> http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.com
>

[M100] Backpack drives are back!

[birt_j]

Hi all,

 

A lot of folks have been asking when more Backpack drives will be available.
As you know the chip shortage has made some parts impossible to obtain,
including the microcontroller used in the original Backpack. My friend that
designed the original Backpack found a newly released AVR processor that was
actually available and designed the Backpack Drive Plus, or BPD+ if you
prefer. It looks the same and works the same with a slightly lower current
draw from the battery. He also made a number of adapters to use the Backpack
with computers like the WP2, Sinclair Z88, Epson HX-20, Epson PX-8. The
Epson's have a separate firmware to simulate the original Epson disk drives.

 

We had a waiting list of folks who had asked for one and have worked through
that list so now ordering is open to the public. We are still 3D printing
cases and finishing the units up. If the stock level shows zero, try again
in a few days. When we run out, I will note that on the webpage.

 

https://www.soigeneris.com/tandy-tpdd-2-backpack-drive-2

 

Jeff Birt

Re: [M100] Backpack drive?!?1

[birt_j]

I will let you know when we get more…

 

Jeff

 

From: M100  On Behalf Of ~Art
Sent: Friday, January 28, 2022 4:05 PM
To: m...@bitchin100.com
Subject: Re: [M100] Backpack drive?!?1

 

Well that figures.   Story of my life, always a day late and a dollar short.  

 

The NADSBox works great, so I guess I will survive.

 

Do you have a wait list I can put my name on?

 

~Art

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of bir...@soigeneris.com 
<mailto:bir...@soigeneris.com> 
Sent: Friday, January 28, 2022 1:47 PM
To: m...@bitchin100.com <mailto:m...@bitchin100.com> 
Subject: Re: [M100] Backpack drive?!?1

 

I ran out of them yesterday ☹

 

We want to get more built, but the chip shortage has made things like 
microcontrollers very hard to obtain and very expensive. When we can get the 
parts and get them at more ‘normal’ prices we’ll get more built.

 

Jeff Birt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Joshua O'Keefe
Sent: Friday, January 28, 2022 11:54 AM
To: m...@bitchin100.com <mailto:m...@bitchin100.com> 
Subject: Re: [M100] Backpack drive?!?1

 

On Jan 28, 2022, at 9:20 AM, ~Art mailto:m...@randombits.net> > wrote:

Are these still available?  Who would I contact?

 

Hi Art!  I got mine from:

  https://www.soigeneris.com/tandy-tpdd-2-backpack-drive

 

Looks like he still has a few on hand, too!

Re: [M100] Backpack drive?!?1

[Brian K. White]

I just checked and you can still get all the parts to build a PDDuino.

The parts are an off-the-shelf microcontroller board and a short bom for 
an adapter board.


You have a choice of at least 4 different microcontroller boards all in 
stock from a few different places currently, and the only special part 
on the adapter board is a max3232 clone chip that has a few different 
equivalent substitutions so if one is out of stock there are other 
suppliers and other versions.


Currently, everything is in stock all from one place from digikey 
(probably mouser, farnell, jameco etc too).


But this is quite a different proposition, building the MounT board 
yourself and compiling and loading the firmware yourself.


In more detail, it goes like this:

Altogether this is made of 4 main parts

1 - The MounT board, which is a small pcb that serves as serial cable, 
rs232 level shifter, and physical mount to hold the arduino board.

https://github.com/bkw777/MounT

The BOM shows the max3232 clone chip out of stock, but digikey 
automatically offers a substitution that's in stock, and it's a good 
substitution, so go ahead and use it.


Bizarrely the 2-pin jumper horizontal pin header is out of stock but 
that is trivial. Its just a plain 2.54mm 90 degree pin header. They have 
countless others. You could get a bag of 40-pin sticks of the same thing 
on ebay etc and just snap 2 pins of one stick, or just bridge the two 
pins directly on the pcb since 99% of the time you just want a jumper on 
the pins anyway.



2 - the off-the-shelf arduino-compatible board (2 adafruit feather 
models, 2 teensy models) which has the microcontroller and sd card 
reader, and in the case of the feather boards also a lipo battery charger.

https://www.adafruit.com/product/2795

This is also available from digikey so you can just add it to the same 
order as the MounT parts.

https://www.digikey.com/short/qfr0hr4p


3 - USB version of BCR_Breakout for power, or for the feather boards 
they can use either the BCR port or a lipo cell for power. The lipo cell 
is small and fits right in between the two pcbs and doesn't even make 
the combined unit any larger. It recharges from the usb port and is 
connected by a JST plug so it's removable/replaceable.

https://github.com/bkw777/BCR_Breakout

The usb cable unfortunately just has to come from the alieexpress links 
in the readme. You can use any ordinary microusb cable that you already 
have, but if you want one of those neat little short cables with 90 
degree plugs in just the right directions, they aren't so common.


and/or the lipo cell
https://www.adafruit.com/product/1570
Also available from digikey so also can be added right to the same order 
https://www.digikey.com/short/9nj4hh3p


To be clear, the battery is totally optional. It runs fine off the BCR 
port. You just may not want that extra cable and plug hanging off your 
machine sometimes.


When using the battery, it fits right in between the two pcb's, and the 
wire can be stuffed in there too so the whole thing is neat and compact.



4 - PDDuino firmware
https://github.com/bkw777/PDDuino


You don't have to solder the microcontroller board to the MounT board. 
You can, but the MounT board has staggered pin holes so that they form a 
friction fit with the pins on the microcontroller board. You order the 
PCB with ENIG finish which means the copper is gold plated, so those pin 
holes effectively become a socket for the microcontroller board. You can 
plug it in and use it, then unplug it and use it for something else.


Of the 4 supported boards (5 if you count the grossly overkill Teensy 
4.1), I recommend the 32u4 feather board for several reasons even though 
it's the oldest and slowest cpu of the lot.


Between the teensys and the feathers in general, the feather boards have 
lipo battery managers built-in, so they can charge a lipo cell from the 
usb port and run off of that battery, and it acts as a UPS, switching 
itself automatically between running from usb or running from battery or 
charging the battery as needed. You can connect/disconnect either the 
usb or the battery any time without worrying or interrupting anything. 
And the battery is connected by a standard JST connector, so it's 
removable/replaceable.


Oh plus the feather boards have the sd card detect switch in the card 
slot wired up to a pin, which is also assignable to a hardware 
interrupt, while the teensy boards do not have the switch physically 
connected to anything. (the card slot does have a switch though, and I 
*think* it's possible to make a pretty easy hardware mod to connect it 
up and read it from software) So the feather boards can detect when the 
card is ejected/inserted, and automatically trigger the card-init and 
bootstrap functions just by ejecting the card. It means 2 things, 1 - 
when you eject and re-insert the card, the pdduino code knows it 
happened and re-scans the card to get the new file listing, and 2 - you 
can 

Re: [M100] Backpack drive?!?1

[~Art]

Well that figures.   Story of my life, always a day late and a dollar short.  

 

The NADSBox works great, so I guess I will survive.

 

Do you have a wait list I can put my name on?

 

~Art

 

From: M100  On Behalf Of 
bir...@soigeneris.com
Sent: Friday, January 28, 2022 1:47 PM
To: m...@bitchin100.com
Subject: Re: [M100] Backpack drive?!?1

 

I ran out of them yesterday ☹

 

We want to get more built, but the chip shortage has made things like 
microcontrollers very hard to obtain and very expensive. When we can get the 
parts and get them at more ‘normal’ prices we’ll get more built.

 

Jeff Birt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Joshua O'Keefe
Sent: Friday, January 28, 2022 11:54 AM
To: m...@bitchin100.com <mailto:m...@bitchin100.com> 
Subject: Re: [M100] Backpack drive?!?1

 

On Jan 28, 2022, at 9:20 AM, ~Art mailto:m...@randombits.net> > wrote:

Are these still available?  Who would I contact?

 

Hi Art!  I got mine from:

  https://www.soigeneris.com/tandy-tpdd-2-backpack-drive

 

Looks like he still has a few on hand, too!

Re: [M100] Backpack drive?!?1

[Mark J. Blair]

I didn't know about the Backpack drive, either! It looks very much like a 
concept I CADed up and shared on Twitter for a 1x AA powered TPDD emulator 
quite a while back. But I ran out of gumption before making much progress. I'm 
very happy to see that somebody actually made such a beast. That also means 
that I can cross that project off my list of projects I'll never get around to 
finishing! LOL

It looks lovely. I like how they designed the case. I think I'll order one, 
even though I already have a perfectly good NADS box.

-- 
Mark J. Blair 
Blog:https://www.nf6x.net
Git: https://gitlab.com/users/NF6X/groups
HECnet:  DOGPAK::MBLAIR
Twitter: @nf6x

Re: [M100] Backpack drive?!?1

[Carlos Nunez]

The website is showing out of stock for me, so the last few must have been 
snapped up. I left a message on the website’s contact form.

Does anyone know if they get new stock on a regular basis, or is it released on 
demand?

> On Jan 28, 2022, at 10:28 AM, Ben Wiley Sittler  wrote:
> 
> 
> Yeah I bought some in the last few months and they work great. In conjunction 
> with REX# or REXCPM it is really perfect - especially REXCPM as you can fully 
> bootstrap and restore the device even when your M100 battery previously ran 
> dry, provided you backed up full memory images to the backpack drive first. 
> The backpack drive fills the same role with REXCPM that onboard flash fills 
> with REX# in this case
> 
> Only thing you might need to do is substitute flat-headed screws if you're 
> plugging one into something like KC-85 or PC-8300 where the RS-232 connector 
> has projecting mounting hardware for securing a cable, but flat-headed screws 
> are very cheap
> 
> Be aware that the provided bootstrap and TPDD client don't yet work on some 
> of the less-common models (M10, for instance, unless you replaced the ROM 
> with the T102-derived one) but regular TELCOM downloads are still fine there. 
> Adding support for more models is likely "just a matter of software" too, 
> since the first-stage bootstrap is just a BASIC program you can edit or 
> replace very easily
> 
> All in all: this device makes the machine far more usable and doesn't even 
> "dangle". Also Jeff Birt/soigeneris customer support is excellent, questions 
> were answered and a single minor issue were resolved quickly and with a true 
> minimum of hassle
> 
> 
>> On Fri, Jan 28, 2022, 09:53 Joshua O'Keefe  wrote:
>>> On Jan 28, 2022, at 9:20 AM, ~Art  wrote:
>>> Are these still available?  Who would I contact?
>> 
>> Hi Art!  I got mine from:
>>   https://www.soigeneris.com/tandy-tpdd-2-backpack-drive
>> 
>> Looks like he still has a few on hand, too!

Re: [M100] Backpack drive?!?1

[birt_j]

I ran out of them yesterday ☹

 

We want to get more built, but the chip shortage has made things like 
microcontrollers very hard to obtain and very expensive. When we can get the 
parts and get them at more ‘normal’ prices we’ll get more built.

 

Jeff Birt

 

From: M100  On Behalf Of Joshua O'Keefe
Sent: Friday, January 28, 2022 11:54 AM
To: m...@bitchin100.com
Subject: Re: [M100] Backpack drive?!?1

 

On Jan 28, 2022, at 9:20 AM, ~Art mailto:m...@randombits.net> > wrote:

Are these still available?  Who would I contact?

 

Hi Art!  I got mine from:

  https://www.soigeneris.com/tandy-tpdd-2-backpack-drive

 

Looks like he still has a few on hand, too!

Re: [M100] Backpack drive?!?1

[Ben Wiley Sittler]

Yeah I bought some in the last few months and they work great. In
conjunction with REX# or REXCPM it is really perfect - especially REXCPM as
you can fully bootstrap and restore the device even when your M100 battery
previously ran dry, provided you backed up full memory images to the
backpack drive first. The backpack drive fills the same role with REXCPM
that onboard flash fills with REX# in this case

Only thing you might need to do is substitute flat-headed screws if you're
plugging one into something like KC-85 or PC-8300 where the RS-232
connector has projecting mounting hardware for securing a cable, but
flat-headed screws are very cheap

Be aware that the provided bootstrap and TPDD client don't yet work on some
of the less-common models (M10, for instance, unless you replaced the ROM
with the T102-derived one) but regular TELCOM downloads are still fine
there. Adding support for more models is likely "just a matter of software"
too, since the first-stage bootstrap is just a BASIC program you can edit
or replace very easily

All in all: this device makes the machine far more usable and doesn't even
"dangle". Also Jeff Birt/soigeneris customer support is excellent,
questions were answered and a single minor issue were resolved quickly and
with a true minimum of hassle


On Fri, Jan 28, 2022, 09:53 Joshua O'Keefe  wrote:

> On Jan 28, 2022, at 9:20 AM, ~Art  wrote:
>
> Are these still available?  Who would I contact?
>
>
> Hi Art!  I got mine from:
>   https://www.soigeneris.com/tandy-tpdd-2-backpack-drive
>
> Looks like he still has a few on hand, too!
>

Re: [M100] Backpack drive?!?1

[Joshua O'Keefe]

On Jan 28, 2022, at 9:20 AM, ~Art  wrote:
> Are these still available?  Who would I contact?

Hi Art!  I got mine from:
  https://www.soigeneris.com/tandy-tpdd-2-backpack-drive

Looks like he still has a few on hand, too!

[M100] Backpack drive?!?1

[~Art]

Hello all,

 

How did I miss the BackPack?  I have an NADSBox that I purchased way back
when I got my first 102. It still works great, but now I have multiple
'M100' devices (NECs mostly) and it would be great to have another external
storage device.  All the devices have some version of REX, (a 'must have'
IMHO) so it's manageable, but it would really be much more convenient with
two.  Are these still available?  Who would I contact?

 

 

Much thanks,

~Art

 

 

 

 

Re: [M100] Backpack drive quick start

[Russell Flowers]

I started watching this video while getting ready for work this morning.
You do a good job! Will watch the remainder later.

As for the device, it is something I would like to have, but I'm not sure
if I do enough work on the 100 to make it worthwhile.

-- Russ

On Thu, Jul 8, 2021 at 8:11 AM Jeffrey Birt  wrote:

> Hi all,
>
>
>
> Here is the promised Quick Start video for the Backpack drive. They have
> all been spoken for at this point but if you are interested in one let me
> know so we can get an idea of how many to have made up on the production
> line.
>
>
>
> This video is intended as a ‘quick start’ of sorts, to get you up and
> running quickly. More videos will be coming where we will dig into advanced
> features.
>
>
>
> https://youtu.be/3es0NLJmd2c
>
>
>
> Jeff Birt (Hey Birt!)
>

Re: [M100] Backpack drive quick start

[Jeff Gonzales]

Righteous!

On Thu, Jul 8, 2021 at 9:11 AM Jeffrey Birt  wrote:

> Hi all,
>
>
>
> Here is the promised Quick Start video for the Backpack drive. They have
> all been spoken for at this point but if you are interested in one let me
> know so we can get an idea of how many to have made up on the production
> line.
>
>
>
> This video is intended as a ‘quick start’ of sorts, to get you up and
> running quickly. More videos will be coming where we will dig into advanced
> features.
>
>
>
> https://youtu.be/3es0NLJmd2c
>
>
>
> Jeff Birt (Hey Birt!)
>

[M100] Backpack drive quick start

[Jeffrey Birt]

Hi all,

 

Here is the promised Quick Start video for the Backpack drive. They have all
been spoken for at this point but if you are interested in one let me know
so we can get an idea of how many to have made up on the production line.

 

This video is intended as a 'quick start' of sorts, to get you up and
running quickly. More videos will be coming where we will dig into advanced
features.

 

https://youtu.be/3es0NLJmd2c

 

Jeff Birt (Hey Birt!)