[M100] Unable to Load TEENY to MT
All, Got a Rex from arcadeshopper. Need to flash it and am trying to load TEENY. Not working. Attached MT to a Portege running Win7. Plugged into USB/COM4 and using TEENY /4 /BS /S. MT gets initial code, but has an SN error on line 0. From what I can tell a variable is missing. Anyone have other source for TEENY or other idea? GregS <><
Re: [M100] Unable to Load TEENY to MT
Since you are using Windows 7, mComm for Windows has the ability to push TEENY or TS-DOS to a Model-T. On Tue, Jan 22, 2019, at 3:03 PM, Greg Swallow wrote: > All, > > Got a Rex from arcadeshopper. Need to flash it and am trying to load > TEENY. Not working. Attached MT to a Portege running Win7. Plugged > into USB/COM4 and using TEENY /4 /BS /S. MT gets initial code, but has > an SN error on line 0. From what I can tell a variable is missing. > Anyone have other source for TEENY or other idea?> > GregS <><
Re: [M100] Unable to Load TEENY to MT
Trying to flash it? Not clear on your steps. I assume Rex was flashed before delivery but maybe I'm missing something. Programming opt ROM sectors or backing up / restore images over tpdd protocol is done with REXMGR. -- John. On Tue, Jan 22, 2019, 3:03 PM Greg Swallow All, > > Got a Rex from arcadeshopper. Need to flash it and am trying to load > TEENY. Not working. Attached MT to a Portege running Win7. Plugged into > USB/COM4 and using TEENY /4 /BS /S. MT gets initial code, but has an SN > error on line 0. From what I can tell a variable is missing. Anyone have > other source for TEENY or other idea? > > GregS <>< >
Re: [M100] Unable to Load TEENY to MT
Flash it is right. Something happened and it's not booting. After a cold start (Ctrl-Break-Reset/Power) I install the Rex, startup, go to BASIC and execute CALL 63012. And, get nothing. Unless I wait a few minutes then some random black blocks are dumped on the screen. Emailed Greg at arcadeshopper.com and figured the flash became corrupt. So am trying to go through a rebuild using the latest 4.9 from bitchin100.com. Otherwise I would be using REXMGR, yes. Thanks, Greg - Original Message - From: "John R. Hogerhuis" To: m...@bitchin100.com Sent: Tuesday, January 22, 2019 4:48:31 PM Subject: Re: [M100] Unable to Load TEENY to MT Trying to flash it? Not clear on your steps. I assume Rex was flashed before delivery but maybe I'm missing something. Programming opt ROM sectors or backing up / restore images over tpdd protocol is done with REXMGR.
Re: [M100] Unable to Load TEENY to MT
The most likely issue in a new Rex install is that the pins of the optrom are not all making good contact. If the firmware is corrupted (unlikely) teeny isn't going to help. -- John.
Re: [M100] Unable to Load TEENY to MT
Figured that when I first experienced the stall. Examined the plating on the Rex and it all looks good. Don't think it would be the socket as I re-installed the SR and it continues to function fine. Tiny is an attempt to get TPDD support loaded so I can load the rf149.co file and rebuild the Rex. Thank you, Greg - Original Message - From: "John R. Hogerhuis" To: m...@bitchin100.com Sent: Tuesday, January 22, 2019 6:11:01 PM Subject: Re: [M100] Unable to Load TEENY to MT The most likely issue in a new Rex install is that the pins of the optrom are not all making good contact. If the firmware is corrupted (unlikely) teeny isn't going to help. -- John.
Re: [M100] Unable to Load TEENY to MT
You need the full TS-DOS in RAM to re-flash a REX. mComm can inject TS-DOS easily. http://www.club100.org/memfiles/index.php?PHPSESSID=og35ki7qmru99qqn00eal5ijm2&direction=1&order=mod&directory=Kurt%20McCullum On Tue, Jan 22, 2019 at 8:20 PM Greg Swallow wrote: > > Figured that when I first experienced the stall. Examined the plating on the > Rex and it all looks good. Don't think it would be the socket as I > re-installed the SR and it continues to function fine. Tiny is an attempt to > get TPDD support loaded so I can load the rf149.co file and rebuild the Rex. > > Thank you, > > Greg > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Tuesday, January 22, 2019 6:11:01 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > The most likely issue in a new Rex install is that the pins of the optrom > are not all making good contact. > > If the firmware is corrupted (unlikely) teeny isn't going to help. > > -- John.
Re: [M100] Unable to Load TEENY to MT
In my experience it's an issue of good contact pressure between all pins and the socket, and the proper spacer between rex and the socket bottom. -- John. On Tue, Jan 22, 2019, 5:20 PM Greg Swallow Figured that when I first experienced the stall. Examined the plating on > the Rex and it all looks good. Don't think it would be the socket as I > re-installed the SR and it continues to function fine. Tiny is an attempt > to get TPDD support loaded so I can load the rf149.co file and rebuild > the Rex. > > Thank you, > > Greg > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Tuesday, January 22, 2019 6:11:01 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > The most likely issue in a new Rex install is that the pins of the optrom > are not all making good contact. > > If the firmware is corrupted (unlikely) teeny isn't going to help. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
>From what I can tell the spacing et al of the Rex is the same as the SR. The >PCB of the Rex is thinner material than the SR, but the top surface of both is >level/even when the two are set next to each other. I have made some adjusting >attempts with near same result. Even installed the Rex in one of my other MT >and had the same issue there. I was trying to load TS-DOS injected via mComm 2.5, but that is giving me an OD, Out of Data, error in line 5. It's my hope that the rf149.co might have enough "diagnosis" that it can tell if the Rex is in/programmed/whatever to further figure out what is wrong. Sill looking for a way to load TS-DOS, anyone have a suggestion? God Bless, Greg - Original Message - From: "John R. Hogerhuis" To: m...@bitchin100.com Sent: Tuesday, January 22, 2019 7:10:41 PM Subject: Re: [M100] Unable to Load TEENY to MT In my experience it's an issue of good contact pressure between all pins and the socket, and the proper spacer between rex and the socket bottom. -- John.
Re: [M100] Unable to Load TEENY to MT
Hi Greg TS-DOS is not needed to re-flash the REX. Teeny should be good enough to get the RF149.co across to the model T. The flash program has its own built in DOS which should them pull in the two other ROM files from the ŒmComm Drive¹. Make sure tsd100.bx and RXF149.BR are at the top level of the virtual drive, these are the TS-DOS and REXMGR ROMs respectively. That should be all you need :) There are no diagnostics with RF149.co it will just wipe and reprogram the REX. The only times I have seen the REX lose its mind is when there are power issues with the model T like a sudden glitch. It is quite sensitive to power problems. If you get really stuck please contact me offline and I am quite happy to re-flash it for you. On 22/1/19, 7:23 PM, "M100 on behalf of Greg Swallow" wrote: >From what I can tell the spacing et al of the Rex is the same as the SR. >The PCB of the Rex is thinner material than the SR, but the top surface >of both is level/even when the two are set next to each other. I have >made some adjusting attempts with near same result. Even installed the >Rex in one of my other MT and had the same issue there. > >I was trying to load TS-DOS injected via mComm 2.5, but that is giving me >an OD, Out of Data, error in line 5. It's my hope that the rf149.co might >have enough "diagnosis" that it can tell if the Rex is >in/programmed/whatever to further figure out what is wrong. Sill looking >for a way to load TS-DOS, anyone have a suggestion? > >God Bless, > >Greg
Re: [M100] Unable to Load TEENY to MT
Teeny can also be injected from mComm. It's quite a bit smaller too so it loads faster. I'm not sure why that error would be coming up with TS-DOS. Did you use the command "RUN COM:98N1E" from Basic? The dos injector uses xon/xoff so the flow control lines don't matter when loading. On Tue, Jan 22, 2019, at 7:23 PM, Greg Swallow wrote: > From what I can tell the spacing et al of the Rex is the same as the > SR. The PCB of the Rex is thinner material than the SR, but the top > surface of both is level/even when the two are set next to each other. > I have made some adjusting attempts with near same result. Even > installed the Rex in one of my other MT and had the same issue there.> > I was trying to load TS-DOS injected via mComm 2.5, but that is giving > me an OD, Out of Data, error in line 5. It's my hope that the rf149.co > might have enough "diagnosis" that it can tell if the Rex is > in/programmed/whatever to further figure out what is wrong. Sill > looking for a way to load TS-DOS, anyone have a suggestion?> > God Bless, > > Greg > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Tuesday, January 22, 2019 7:10:41 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > In my experience it's an issue of good contact pressure between > all pins> and the socket, and the proper spacer between rex and the > socket bottom.> > -- John.
Re: [M100] Unable to Load TEENY to MT
Yeup, using RUN"COM:98N1E" alright. Have tried to inject TEENY, but it stalls. I RESET, go to BASIC, and RUN and gives a Checksum error. Am beginning to wonder about my RS-232 port. - Original Message - >From: "Kurt McCullum" >To: m100@lists.bitchin100.com >Sent: Tuesday, January 22, 2019 9:31:51 PM >Subject: Re: [M100] Unable to Load TEENY to MT > >Teeny can also be injected from mComm. It's quite a bit smaller too >so it loads faster. I'm not sure why that error would be coming up >with TS-DOS. Did you use the command "RUN COM:98N1E" from Basic? The >dos injector uses xon/xoff so the flow control lines don't matter >when loading.
Re: [M100] Unable to Load TEENY to MT
Might be the port but one more thing to try. Instead of going to basic and typing the run command do the following.1) Open TEXT with a filename of TEENY.DO 2) Press F2 and type COM:98N1E 3) Press the button on mComm to start the inject process. This will at least let you see what is making it to your machine. Kurt On Wed, Jan 23, 2019, at 5:41 AM, Greg Swallow wrote: > Yeup, using RUN"COM:98N1E" alright. Have tried to inject TEENY, but it > stalls. I RESET, go to BASIC, and RUN and gives a Checksum error. Am > beginning to wonder about my RS-232 port.> > > > - Original Message - >> From: "Kurt McCullum" >> To: m100@lists.bitchin100.com >> Sent: Tuesday, January 22, 2019 9:31:51 PM >> Subject: Re: [M100] Unable to Load TEENY to MT >> >> Teeny can also be injected from mComm. It's quite a bit smaller too >> so it loads faster. I'm not sure why that error would be coming up >> with TS-DOS. Did you use the command "RUN COM:98N1E" from Basic? The>> dos >> injector uses xon/xoff so the flow control lines don't matter >> when loading. >
Re: [M100] Unable to Load TEENY to MT
The same thing happens with other MT's so I am figuring something is amiss in my Windows 7; fain surprise. Anyway, am going to try on the wife's Macbook Air, but need to find mComm for OSX. Anyone have the link? I can not seem to Google it up. Thanks, GregS <>< - Original Message - From: "Kurt McCullum" To: m100@lists.bitchin100.com Sent: Wednesday, January 23, 2019 8:07:38 AM Subject: Re: [M100] Unable to Load TEENY to MT Might be the port but one more thing to try. Instead of going to basic and typing the run command do the following.1) Open TEXT with a filename of TEENY.DO 2) Press F2 and type COM:98N1E 3) Press the button on mComm to start the inject process. This will at least let you see what is making it to your machine. Kurt
Re: [M100] Unable to Load TEENY to MT
Sorry, no such thing as mComm for OSX. On Wed, Jan 23, 2019, at 9:17 AM, Greg Swallow wrote: > The same thing happens with other MT's so I am figuring something is > amiss in my Windows 7; fain surprise.> Anyway, am going to try on the wife's > Macbook Air, but need to find > mComm for OSX. Anyone have the link? I can not seem to Google it up.> > Thanks, > > GregS <>< > > - Original Message - > From: "Kurt McCullum" > To: m100@lists.bitchin100.com > Sent: Wednesday, January 23, 2019 8:07:38 AM > Subject: Re: [M100] Unable to Load TEENY to MT > > Might be the port but one more thing to try. Instead of going to basic> and > typing the run command do the following.1) Open TEXT with a > filename of TEENY.DO> 2) Press F2 and type COM:98N1E > 3) Press the button on mComm to start the inject process. > > This will at least let you see what is making it to your machine. > > Kurt >
Re: [M100] Unable to Load TEENY to MT
Thought I saw something about it as part of Posix/Linux. Is it Windows and Android only? - Original Message - From: "Kurt McCullum" To: m100@lists.bitchin100.com Sent: Wednesday, January 23, 2019 10:19:07 AM Subject: Re: [M100] Unable to Load TEENY to MT Sorry, no such thing as mComm for OSX.
Re: [M100] Unable to Load TEENY to MT
Yes. But there is also LaddieAlpha. That may work for you. When you opened the file in TEXT, what ended up being sent to the machine? It should have given you some data even if it was garbage. Kurt On Wed, Jan 23, 2019, at 9:21 AM, Greg Swallow wrote: > Thought I saw something about it as part of Posix/Linux. Is it Windows > and Android only?> > - Original Message - > From: "Kurt McCullum" > To: m100@lists.bitchin100.com > Sent: Wednesday, January 23, 2019 10:19:07 AM > Subject: Re: [M100] Unable to Load TEENY to MT > > Sorry, no such thing as mComm for OSX. >
Re: [M100] Unable to Load TEENY to MT
When I used TEXT to capture I got what looked ok, until I checked the lines that errors mentioned. There I could see something was missing. The latest was the OD error in TS-DOS. Did some switching around and used my Portege with mComm, in hopes it was a Win7 64-bit issue. Same errors there, but injecting TS-DOS did get farther and actually ran after the injection before it got the OD error. I will try capturing in text next. I did also check my cables between two MT and got full/half duplex in TERMINAL, so cable should be ok. That doesn't eliminate the USB-RS232 adapter though. I am beginning to think there may be the problem. I'll let y'all know what happens. God Bless, GregS <>< - Original Message - From: "Kurt McCullum" To: m100@lists.bitchin100.com Sent: Wednesday, January 23, 2019 10:41:09 AM Subject: Re: [M100] Unable to Load TEENY to MT Yes. But there is also LaddieAlpha. That may work for you. When you opened the file in TEXT, what ended up being sent to the machine? It should have given you some data even if it was garbage. Kurt
Re: [M100] Unable to Load TEENY to MT
are you transferring at 300baud? I would try that. sounds like you are dropping bytes due to no flow control possibly. On Wed, Jan 23, 2019 at 1:21 PM Greg Swallow wrote: > When I used TEXT to capture I got what looked ok, until I checked the > lines that errors mentioned. There I could see something was missing. The > latest was the OD error in TS-DOS. > > Did some switching around and used my Portege with mComm, in hopes it was > a Win7 64-bit issue. Same errors there, but injecting TS-DOS did get > farther and actually ran after the injection before it got the OD error. I > will try capturing in text next. I did also check my cables between two MT > and got full/half duplex in TERMINAL, so cable should be ok. That doesn't > eliminate the USB-RS232 adapter though. I am beginning to think there may > be the problem. I'll let y'all know what happens. > > God Bless, > > GregS <>< > > - Original Message - > From: "Kurt McCullum" > To: m100@lists.bitchin100.com > Sent: Wednesday, January 23, 2019 10:41:09 AM > Subject: Re: [M100] Unable to Load TEENY to MT > > Yes. But there is also LaddieAlpha. That may work for you. > > When you opened the file in TEXT, what ended up being sent to the > machine? It should have given you some data even if it was garbage. > Kurt > >
Re: [M100] Unable to Load TEENY to MT
Thought about that too Steve, but haven't been able to find anything about how to mod mComm command line or internal options for the port. It always comes up saying to use RUN"COM:98N1E." If I mod the port in Win7 Device Manager to match 19200 (98N1E), 9600 (88N1E), or 300 (3N1E), the problem persist. - Original Message - From: "Stephen Adolph" To: m...@bitchin100.com Sent: Wednesday, January 23, 2019 11:27:55 AM Subject: Re: [M100] Unable to Load TEENY to MT are you transferring at 300baud? I would try that. sounds like you are dropping bytes due to no flow control possibly.
Re: [M100] Unable to Load TEENY to MT
You could try mcomm under wine. There are lots of ways to inject teeny.do Any terminal program can do it. Laptop.exe. TBACK.EXE. LaddieAlpha won't help you in this case because it has no injector. Once you have your REX working, LaddieAlpha or dlplus is the way to go on osx. And it works on all other platforms. I guess I should add an injector. -- John. On Wed, Jan 23, 2019, 9:17 AM Greg Swallow The same thing happens with other MT's so I am figuring something is amiss > in my Windows 7; fain surprise. > Anyway, am going to try on the wife's Macbook Air, but need to find mComm > for OSX. Anyone have the link? I can not seem to Google it up. > > Thanks, > > GregS <>< > > >
Re: [M100] Unable to Load TEENY to MT
Before my REX I would transfer teeny.do via a terminal program and then justbused dlplus on OS X. > On Jan 23, 2019, at 1:55 PM, John R. Hogerhuis wrote: > > You could try mcomm under wine. > > There are lots of ways to inject teeny.do > > Any terminal program can do it. Laptop.exe. TBACK.EXE. > > LaddieAlpha won't help you in this case because it has no injector. > > Once you have your REX working, LaddieAlpha or dlplus is the way to go on > osx. And it works on all other platforms. > > I guess I should add an injector. > > -- John. > >> On Wed, Jan 23, 2019, 9:17 AM Greg Swallow > The same thing happens with other MT's so I am figuring something is amiss >> in my Windows 7; fain surprise. >> Anyway, am going to try on the wife's Macbook Air, but need to find mComm >> for OSX. Anyone have the link? I can not seem to Google it up. >> >> Thanks, >> >> GregS <>< >> >>
Re: [M100] Unable to Load TEENY to MT
" Thought about that too Steve, but haven't been able to find anything about how to mod mComm command line or internal options for the port. It always comes up saying to use RUN"COM:98N1E." If I mod the port in Win7 Device Manager to match 19200 (98N1E), 9600 (88N1E), or 300 (3N1E), the problem persist." I'm sure Kurt sets the port speed in his code. You would need him to give you a way to change the baud rate. Or, just use a terminal program (hyperterm, realterm, etc) to transfer the TEENY.DO, that's all that Mcomm is doing. You need to turn on hardware handshaking, and turn the port speed way down. Do you have TEENY.DO as a stand-alone file? -- John.
Re: [M100] Unable to Load TEENY to MT
I do TEE100.DO, which I think in TEENY.DO for the MT. I have TEENY.EXE, but it is for WIN32. My problem at this point in finding a good, terminal program since HTERM is gone. God Bless, GregS <>< - Original Message - From: "John R. Hogerhuis" To: m...@bitchin100.com Sent: Wednesday, January 23, 2019 3:48:44 PM Subject: Re: [M100] Unable to Load TEENY to MT I'm sure Kurt sets the port speed in his code. You would need him to give you a way to change the baud rate. Or, just use a terminal program (hyperterm, realterm, etc) to transfer the TEENY.DO, that's all that Mcomm is doing. You need to turn on hardware handshaking, and turn the port speed way down. Do you have TEENY.DO as a stand-alone file? -- John.
Re: [M100] Unable to Load TEENY to MT
Kurt McCullum wrote: > Teeny can also be injected from mComm. It's quite a bit smaller too > so it loads faster. I'm not sure why that error would be coming up > with TS-DOS. Did you use the command "RUN COM:98N1E" from Basic? The > dos injector uses xon/xoff so the flow control lines don't matter > when loading. Kurt, I didn't asked about it yet because my M100 is having a lot of other issues and I didn't want to flood the list with too many different topics but if I did manage to get mComm 2.5 running, the "inject TS-DOS" feature never worked for me (and yes, I have eventually tested every single pin of my DB9 to DB25 adapter and it is totally matching the cable described in mComm documentation). I'm pretty sure the issue is my dodgy cheap USB to RS232 interface having issues with xon/xoff, but here is how I managed to get TS-DOS on the M100: - I opened the file dos100.do from the mComm directory in a text editor and copied it in the clipboard - I opened a 1200 bauds serial connection with even parity and xon/xoff using Putty on the PC - I typed LOAD "com:58e1e in the basic prompt - I pasted the clipboard content into putty - I pressed CTRL+Z in putty (that sends the EOF to the M100) - After one eternity (3-4 minutes) the loading completed, I typed RUN and it did the trick Note that using TS-DOS, I can transfer files at at full speed and I got no error so far so the problem only occurs at the initial step. Also to be transparent I had to try 3 times before getting TS-DOS transferred without any corrupted content so perhaps you may try an even slower speed (it usually works fine at 1200 bauds but I've never transferred a file that big before). Note that if you're using 600 bauds you'll have to wait for 6-8 minutes to get the file. Perhaps in the next revision of mComm you could add an option to reduce the speed for TS-DOS injection? (and if possible some kind of progress indicator because it's a little nerve breaking to look at the M100 for 3+ minutes while nothing changes at all :o) ) Greg Swallow wrote: > Yeup, using RUN"COM:98N1E" alright. Have tried to inject TEENY, but it stalls. > I RESET, go to BASIC, and RUN and gives a Checksum error. Am beginning to > wonder about my RS-232 port. Is it one of those $4 USB to RS232C interfaces from eBay? That's what I'm using and I'm pretty sure that's where the problem comes from... Eric
Re: [M100] Unable to Load TEENY to MT
As Erik says, you can use Putty. I like Realterm, but it has A LOT of extra knobs. And he gives instructions for loading DOS100.DO, so that could get you over the hump. -- John.
Re: [M100] Unable to Load TEENY to MT
Thank you Erik and John. I got RealTerm to work at 300bd (DTR/DSR) and dropped TD-DOS.DO into TEXT with a Load from: COM:39E1E. Took a while, I watched the news.TS-DOS is load and functioning. Yeah! Got RF149.CO loaded into RAM with TS_DOS and mComm. Ok, now I get a beep when I try to run RF149.CO from the Menu. I saw something about what to do if this happened, but I can not -- for the life of me, figure out where/what is was. Any hints? God Bless, GregS <>< - Original Message - From: "John R. Hogerhuis" To: m...@bitchin100.com Sent: Wednesday, January 23, 2019 4:46:12 PM Subject: Re: [M100] Unable to Load TEENY to MT As Erik says, you can use Putty. I like Realterm, but it has A LOT of extra knobs. And he gives instructions for loading DOS100.DO, so that could get you over the hump. -- John.
Re: [M100] Unable to Load TEENY to MT
You need to run a clear command. Did the CO come with documentation? Probably you can follow the usual steps. http://bitchin100.com/wiki/index.php?title=Loading_a_typical_CO_file -- John. On Wed, Jan 23, 2019, 5:59 PM Greg Swallow Thank you Erik and John. I got RealTerm to work at 300bd (DTR/DSR) and > dropped TD-DOS.DO into TEXT with a Load from: COM:39E1E. Took a while, I > watched the news.TS-DOS is load and functioning. Yeah! > > Got RF149.CO loaded into RAM with TS_DOS and mComm. Ok, now I get a beep > when I try to run RF149.CO from the Menu. I saw something about what to > do if this happened, but I can not -- for the life of me, figure out > where/what is was. Any hints? > > God Bless, > > GregS <>< > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Wednesday, January 23, 2019 4:46:12 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > As Erik says, you can use Putty. I like Realterm, but it has A LOT of extra > knobs. > > And he gives instructions for loading DOS100.DO, so that could get you over > the hump. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
Greg, That's interesting that you had to drop the speed down to 300. I suspect the USB to serial adapter was not responding to the XON/XOFF messages from the MT before it over-ran the buffer on the MT. I have not run into this problem with the Windows version of mComm. The Android version had this problem in the past and I had to write my own routines to handle XON/XOFF when in TELCOM/TELNET mode or when pushing TS-DOS. I may end up having to do the same thing with the Windows version. Glad to hear you have it working now. Kurt On Wed, Jan 23, 2019, at 5:59 PM, Greg Swallow wrote: > Thank you Erik and John. I got RealTerm to work at 300bd (DTR/DSR) and > dropped TD-DOS.DO into TEXT with a Load from: COM:39E1E. Took a while, > I watched the news.TS-DOS is load and functioning. Yeah!> > Got RF149.CO loaded into RAM with TS_DOS and mComm. Ok, now I get a > beep when I try to run RF149.CO from the Menu. I saw something about > what to do if this happened, but I can not -- for the life of me, > figure out where/what is was. Any hints?> > God Bless, > > GregS <>< > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Wednesday, January 23, 2019 4:46:12 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > As Erik says, you can use Putty. I like Realterm, but it has A LOT > of extra> knobs. > > And he gives instructions for loading DOS100.DO, so that could get > you over> the hump. > > -- John.
Re: [M100] Unable to Load TEENY to MT
On Thu, Jan 24, 2019 at 12:12 PM Kurt McCullum wrote: > Greg, > > That's interesting that you had to drop the speed down to 300. I suspect > the USB to serial adapter was not responding to the XON/XOFF messages from > the MT before it over-ran the buffer on the MT. I have not run into this > problem with the Windows version of mComm. The Android version had this > problem in the past and I had to write my own routines to handle XON/XOFF > when in TELCOM/TELNET mode or when pushing TS-DOS. I may end up having to > do the same thing with the Windows version. Glad to hear you have it > working now. > > Kurt > > As far as I know the USB serial driver isn't involved in software flow control. Seems Windows level. But maybe. Just curious... do you do most of your testing on M100? If the NEC really has a larger queue... -- John.
Re: [M100] Unable to Load TEENY to MT
Most testing done with a 102 and then I double check things with a 200 and then the NEC. I don't have a functional 100. On Thu, Jan 24, 2019, at 1:54 PM, John R. Hogerhuis wrote: > > > On Thu, Jan 24, 2019 at 12:12 PM Kurt McCullum > wrote:>> __ >> Greg, >> >> That's interesting that you had to drop the speed down to 300. I >> suspect the USB to serial adapter was not responding to the XON/XOFF >> messages from the MT before it over-ran the buffer on the MT. I have >> not run into this problem with the Windows version of mComm. The >> Android version had this problem in the past and I had to write my >> own routines to handle XON/XOFF when in TELCOM/TELNET mode or when >> pushing TS-DOS. I may end up having to do the same thing with the >> Windows version. Glad to hear you have it working now.>> >> Kurt >> > > As far as I know the USB serial driver isn't involved in software flow > control. Seems Windows level. But maybe.> > Just curious... do you do most of your testing on M100? > > If the NEC really has a larger queue... > > -- John.
Re: [M100] Unable to Load TEENY to MT
On Thu, Jan 24, 2019 at 2:24 PM Kurt McCullum wrote: > Most testing done with a 102 and then I double check things with a 200 and > then the NEC. I don't have a functional 100. > > Oh well. So much for theories. Bottom line is XON/XOFF on Model T's is really hard to not overrun :-) -- John.
Re: [M100] Unable to Load TEENY to MT
clear0,55000 should do the trick. not sure you will have enough ram, when TS-DOS is also in there. May have to delete TS-DOS after you load RF149.CO. may also want to try RT149.CO. ..Steve On Wed, Jan 23, 2019 at 8:59 PM Greg Swallow wrote: > Thank you Erik and John. I got RealTerm to work at 300bd (DTR/DSR) and > dropped TD-DOS.DO into TEXT with a Load from: COM:39E1E. Took a while, I > watched the news.TS-DOS is load and functioning. Yeah! > > Got RF149.CO loaded into RAM with TS_DOS and mComm. Ok, now I get a beep > when I try to run RF149.CO from the Menu. I saw something about what to > do if this happened, but I can not -- for the life of me, figure out > where/what is was. Any hints? > > God Bless, > > GregS <>< > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Wednesday, January 23, 2019 4:46:12 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > As Erik says, you can use Putty. I like Realterm, but it has A LOT of extra > knobs. > > And he gives instructions for loading DOS100.DO, so that could get you over > the hump. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
In Steve's REX Wiki http://bitchin100.com/wiki/index.php?title=REX_Release_4.9 chapter "Rebuild REX" is the description how to proceed. For me it sounds you missed the CLEAR0,55000 before you run RF149.CO. X the Fingers that it works. Reverse Georg from Germany Am Do., 24. Jan. 2019, 02:59 hat Greg Swallow geschrieben: > Thank you Erik and John. I got RealTerm to work at 300bd (DTR/DSR) and > dropped TD-DOS.DO into TEXT with a Load from: COM:39E1E. Took a while, I > watched the news.TS-DOS is load and functioning. Yeah! > > Got RF149.CO loaded into RAM with TS_DOS and mComm. Ok, now I get a beep > when I try to run RF149.CO from the Menu. I saw something about what to > do if this happened, but I can not -- for the life of me, figure out > where/what is was. Any hints? > > God Bless, > > GregS <>< > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Wednesday, January 23, 2019 4:46:12 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > As Erik says, you can use Putty. I like Realterm, but it has A LOT of extra > knobs. > > And he gives instructions for loading DOS100.DO, so that could get you over > the hump. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
are you out of ram? :) On Wed, Jan 23, 2019 at 5:59 PM Greg Swallow wrote: > Thank you Erik and John. I got RealTerm to work at 300bd (DTR/DSR) and > dropped TD-DOS.DO into TEXT with a Load from: COM:39E1E. Took a while, I > watched the news.TS-DOS is load and functioning. Yeah! > > Got RF149.CO loaded into RAM with TS_DOS and mComm. Ok, now I get a beep > when I try to run RF149.CO from the Menu. I saw something about what to > do if this happened, but I can not -- for the life of me, figure out > where/what is was. Any hints? > > God Bless, > > GregS <>< > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Wednesday, January 23, 2019 4:46:12 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > As Erik says, you can use Putty. I like Realterm, but it has A LOT of extra > knobs. > > And he gives instructions for loading DOS100.DO, so that could get you over > the hump. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
Go into basic and type clear 0,55000 Then load rfx100.co On Wed, Jan 23, 2019, 8:59 PM Greg Swallow Thank you Erik and John. I got RealTerm to work at 300bd (DTR/DSR) and > dropped TD-DOS.DO into TEXT with a Load from: COM:39E1E. Took a while, I > watched the news.TS-DOS is load and functioning. Yeah! > > Got RF149.CO loaded into RAM with TS_DOS and mComm. Ok, now I get a beep > when I try to run RF149.CO from the Menu. I saw something about what to > do if this happened, but I can not -- for the life of me, figure out > where/what is was. Any hints? > > God Bless, > > GregS <>< > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Wednesday, January 23, 2019 4:46:12 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > As Erik says, you can use Putty. I like Realterm, but it has A LOT of extra > knobs. > > And he gives instructions for loading DOS100.DO, so that could get you over > the hump. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
Ok, have a day off from work so checking in. I did the CLEAR0,55000 and steps that are in the Wiki. I am sure, as others, that it is because I have TS-DOS (RAM) loaded. I did try clearing TS-DOS out before running RF149.CO, but the the best I could find, are instructions to clear TS-DOS Disk; http://www.club100.org/library/doc/tsdos.html. The instructions there seem to be aimed at TS-DOS may not work with the RAM version. I did turn the resident portion off using [F5] as it says to before following the instructions to clear. Then CLEAR0,55000 before running RF149.CO and still get a single BEEP. Maybe I should try dropping TEENY.DO through PuTTY. It might be small enough to allow RF149.CO to run. Thanks all, GregS <>< - Original Message - From: "Josh Malone" To: m...@bitchin100.com Sent: Wednesday, January 23, 2019 7:52:06 PM Subject: Re: [M100] Unable to Load TEENY to MT Go into basic and type clear 0,55000 Then load rfx100.co
Re: [M100] Unable to Load TEENY to MT
On Sat, Jan 26, 2019 at 10:48 PM Greg Swallow wrote: > > Ok, have a day off from work so checking in. > > I did the CLEAR0,55000 and steps that are in the Wiki. I am sure, as > others, that it is because I have TS-DOS (RAM) loaded. I did try clearing > TS-DOS out before running RF149.CO, but the the best I could find, are > instructions to clear TS-DOS Disk; > http://www.club100.org/library/doc/tsdos.html. The instructions there > seem to be aimed at TS-DOS may not work with the RAM version. I did turn > the resident portion off using [F5] as it says to before following the > instructions to clear. Then CLEAR0,55000 before running RF149.CO and > still get a single BEEP. > > Maybe I should try dropping TEENY.DO through PuTTY. It might be small > enough to allow RF149.CO to run. > > Thanks all, > > GregS <>< > > What did you try to "clear out" ts-dos? I don't think that beep has anything to do with TS-DOS. When a CO file beeps on load, it's because the CLEAR statement is wrong. And if you typed the CLEAR statement and it gave no error, then you have sufficient room to run the utility. If it beeps anyway, maybe the program is running but just beeps. Who knows. Do me a favor, do the CLEAR statement, and LOADM"RF149.CO from the BASIC prompt, not from the main menu and tell us what you see. If it prints out the CO file's header, we can figure out if a) The clear statement is right b) The beep is coming as a BASIC load issue, or for some other reason. -- John.
Re: [M100] Unable to Load TEENY to MT
Best way for me getting TEENY on my M100/102 or T200 via Windows-PC (Win XP/7/8.1/10) is running TEENY.EXE from DOSBox. Makes no difference If using a native RS232 port or a USB-serial adapter. Also for data transfer with TSDOS and DeskLink I prefer this solution. Regards Georg from Germany Am So., 27. Jan. 2019, 07:47 hat Greg Swallow geschrieben: > > Ok, have a day off from work so checking in. > > I did the CLEAR0,55000 and steps that are in the Wiki. I am sure, as > others, that it is because I have TS-DOS (RAM) loaded. I did try clearing > TS-DOS out before running RF149.CO, but the the best I could find, are > instructions to clear TS-DOS Disk; > http://www.club100.org/library/doc/tsdos.html. The instructions there > seem to be aimed at TS-DOS may not work with the RAM version. I did turn > the resident portion off using [F5] as it says to before following the > instructions to clear. Then CLEAR0,55000 before running RF149.CO and > still get a single BEEP. > > Maybe I should try dropping TEENY.DO through PuTTY. It might be small > enough to allow RF149.CO to run. > > Thanks all, > > GregS <>< > > > > - Original Message - > From: "Josh Malone" > To: m...@bitchin100.com > Sent: Wednesday, January 23, 2019 7:52:06 PM > Subject: Re: [M100] Unable to Load TEENY to MT > > Go into basic and type > > clear 0,55000 > > Then load rfx100.co > >
Re: [M100] Unable to Load TEENY to MT
CLEAR0,55000: LOADM"RF149.CO" gives Top: 55302 End: 60148 Exe: 55302 Hope this helps GregS <>< - Original Message - From: "John R. Hogerhuis" To: m...@bitchin100.com Sent: Sunday, January 27, 2019 12:03:56 AM Subject: Re: [M100] Unable to Load TEENY to MT What did you try to "clear out" ts-dos? I don't think that beep has anything to do with TS-DOS. When a CO file beeps on load, it's because the CLEAR statement is wrong. And if you typed the CLEAR statement and it gave no error, then you have sufficient room to run the utility. If it beeps anyway, maybe the program is running but just beeps. Who knows. Do me a favor, do the CLEAR statement, and LOADM"RF149.CO from the BASIC prompt, not from the main menu and tell us what you see. If it prints out the CO file's header, we can figure out if a) The clear statement is right b) The beep is coming as a BASIC load issue, or for some other reason. -- John.
Re: [M100] Unable to Load TEENY to MT
But it gave no error... I think it loaded. Meaning when you typed loadm it copied it's contents to 55302. Not sure why the clear address is 55000. The program starts at 55302. Maybe the program uses the gap as a scratchpad. I'm guessing the beep is from the program itself. Maybe it's done or maybe it's giving you an error. -- John. On Sun, Jan 27, 2019, 12:24 AM Greg Swallow CLEAR0,55000: LOADM"RF149.CO" gives > > Top: 55302 > End: 60148 > Exe: 55302 > > Hope this helps > > GregS <>< > > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Sunday, January 27, 2019 12:03:56 AM > Subject: Re: [M100] Unable to Load TEENY to MT > > What did you try to "clear out" ts-dos? > > I don't think that beep has anything to do with TS-DOS. When a CO file > beeps on load, it's because the CLEAR statement is wrong. And if you typed > the CLEAR statement and it gave no error, then you have sufficient room to > run the utility. > > If it beeps anyway, maybe the program is running but just beeps. Who knows. > > Do me a favor, do the CLEAR statement, and LOADM"RF149.CO > from the BASIC prompt, not from the main menu and tell us what you see. > > If it prints out the CO file's header, we can figure out if > > a) The clear statement is right > b) The beep is coming as a BASIC load issue, or for some other reason. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
I thought that might be the case and tried running after the LOADM. it seemed to be working. It wiped the bank(s) and started loading 0:RF149.BX -- I think it was, but didn't indicate any progress after a few hours I stop it. Maybe I should've let it keep going. I'll be off work again Tuesday and give it a try, if I don't get a chance today. Spending time with in-laws today. God Bless, GregS <>< - Original Message - From: John R. Hogerhuis To: m...@bitchin100.com Sent: Sun, 27 Jan 2019 05:37:32 -0500 (EST) Subject: Re: [M100] Unable to Load TEENY to MT But it gave no error... I think it loaded. Meaning when you typed loadm it copied it's contents to 55302. Not sure why the clear address is 55000. The program starts at 55302. Maybe the program uses the gap as a scratchpad. I'm guessing the beep is from the program itself. Maybe it's done or maybe it's giving you an error. -- John. On Sun, Jan 27, 2019, 12:24 AM Greg Swallow CLEAR0,55000: LOADM"RF149.CO" gives > > Top: 55302 > End: 60148 > Exe: 55302 > > Hope this helps > > GregS <>< > > > - Original Message - > From: "John R. Hogerhuis" > To: m...@bitchin100.com > Sent: Sunday, January 27, 2019 12:03:56 AM > Subject: Re: [M100] Unable to Load TEENY to MT > > What did you try to "clear out" ts-dos? > > I don't think that beep has anything to do with TS-DOS. When a CO file > beeps on load, it's because the CLEAR statement is wrong. And if you typed > the CLEAR statement and it gave no error, then you have sufficient room to > run the utility. > > If it beeps anyway, maybe the program is running but just beeps. Who knows. > > Do me a favor, do the CLEAR statement, and LOADM"RF149.CO > from the BASIC prompt, not from the main menu and tell us what you see. > > If it prints out the CO file's header, we can figure out if > > a) The clear statement is right > b) The beep is coming as a BASIC load issue, or for some other reason. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
I really only ever use the following * serial transfer of TEENY into the M100, to make teeny.co * use Teeny.co to load RF149.co ..then run rf149.co Are you getting the software from the bitchin100 website? I have never used TS-DOS in RAM to load up and run RF149.CO. I can't say if there is any gotcha. On Sun, Jan 27, 2019 at 3:06 PM Greg Swallow wrote: > I thought that might be the case and tried running after the LOADM. it > seemed to be working. It wiped the bank(s) and started loading 0:RF149.BX > -- I think it was, but didn't indicate any progress after a few hours I > stop it. Maybe I should've let it keep going. I'll be off work again > Tuesday and give it a try, if I don't get a chance today. Spending time > with in-laws today. > > God Bless, > > GregS <>< > > - Original Message - > From: John R. Hogerhuis > To: m...@bitchin100.com > Sent: Sun, 27 Jan 2019 05:37:32 -0500 (EST) > Subject: Re: [M100] Unable to Load TEENY to MT > > But it gave no error... > > I think it loaded. Meaning when you typed loadm it copied it's contents to > 55302. > > Not sure why the clear address is 55000. The program starts at 55302. Maybe > the program uses the gap as a scratchpad. > > I'm guessing the beep is from the program itself. Maybe it's done or maybe > it's giving you an error. > > -- John. > > > On Sun, Jan 27, 2019, 12:24 AM Greg Swallow > > CLEAR0,55000: LOADM"RF149.CO" gives > > > > Top: 55302 > > End: 60148 > > Exe: 55302 > > > > Hope this helps > > > > GregS <>< > > > > > > - Original Message - > > From: "John R. Hogerhuis" > > To: m...@bitchin100.com > > Sent: Sunday, January 27, 2019 12:03:56 AM > > Subject: Re: [M100] Unable to Load TEENY to MT > > > > What did you try to "clear out" ts-dos? > > > > I don't think that beep has anything to do with TS-DOS. When a CO file > > beeps on load, it's because the CLEAR statement is wrong. And if you > typed > > the CLEAR statement and it gave no error, then you have sufficient room > to > > run the utility. > > > > If it beeps anyway, maybe the program is running but just beeps. Who > knows. > > > > Do me a favor, do the CLEAR statement, and LOADM"RF149.CO > > from the BASIC prompt, not from the main menu and tell us what you see. > > > > If it prints out the CO file's header, we can figure out if > > > > a) The clear statement is right > > b) The beep is coming as a BASIC load issue, or for some other reason. > > > > -- John. > > > >
Re: [M100] Unable to Load TEENY to MT
The RAM TPDD is most likely conflicting with the the REX program. The best method is to use TEENY to download the RF149.CO file. I have never used the RAM TPPD to program a REX. Running the REX programmer to completion should only take around 5mins. The erasing part takes about 20-30s then downloading the RF149.BR file takes a few minutes. It will then load the tsd100.bx file – which takes a few more minutes. A progress bar will show as they are downloaded. Both of these files need to be on the TPDD drive. The REX programmer will automatically load in the two ROM files. RF149.co is fully self contained and does not require anything else to be loaded. On Sun, Jan 27, 2019 at 3:06 PM Greg Swallow mailto:gswal...@mchsi.com>> wrote: I thought that might be the case and tried running after the LOADM. it seemed to be working. It wiped the bank(s) and started loading 0:RF149.BX -- I think it was, but didn't indicate any progress after a few hours I stop it. Maybe I should've let it keep going. I'll be off work again Tuesday and give it a try, if I don't get a chance today. Spending time with in-laws today. God Bless, GregS <>< - Original Message - From: John R. Hogerhuis mailto:jho...@pobox.com>> To: m...@bitchin100.com<mailto:m...@bitchin100.com> Sent: Sun, 27 Jan 2019 05:37:32 -0500 (EST) Subject: Re: [M100] Unable to Load TEENY to MT But it gave no error... I think it loaded. Meaning when you typed loadm it copied it's contents to 55302. Not sure why the clear address is 55000. The program starts at 55302. Maybe the program uses the gap as a scratchpad. I'm guessing the beep is from the program itself. Maybe it's done or maybe it's giving you an error. -- John. On Sun, Jan 27, 2019, 12:24 AM Greg Swallow mailto:gswal...@mchsi.com> wrote: > CLEAR0,55000: > LOADM"RF149.CO<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2FRF149.CO&data=02%7C01%7C%7Ccb89d0d30570435057c008d68493bd2b%7C84df9e7fe9f640afb435%7C1%7C0%7C636842167395782308&sdata=63lXSY9%2Fxo012LiMOGjl7u3UHa%2Bwa%2FnA3xIOFhfexzU%3D&reserved=0>" > gives > > Top: 55302 > End: 60148 > Exe: 55302 > > Hope this helps > > GregS <>< > > > - Original Message - > From: "John R. Hogerhuis" mailto:jho...@pobox.com>> > To: m...@bitchin100.com<mailto:m...@bitchin100.com> > Sent: Sunday, January 27, 2019 12:03:56 AM > Subject: Re: [M100] Unable to Load TEENY to MT > > What did you try to "clear out" ts-dos? > > I don't think that beep has anything to do with TS-DOS. When a CO file > beeps on load, it's because the CLEAR statement is wrong. And if you typed > the CLEAR statement and it gave no error, then you have sufficient room to > run the utility. > > If it beeps anyway, maybe the program is running but just beeps. Who knows. > > Do me a favor, do the CLEAR statement, and > LOADM"RF149.CO<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2FRF149.CO&data=02%7C01%7C%7Ccb89d0d30570435057c008d68493bd2b%7C84df9e7fe9f640afb435%7C1%7C0%7C636842167395792325&sdata=kKzcdFJJf%2FWMybgXDP%2BRItnDCKP%2BqLoOyIk8IDa1JmM%3D&reserved=0> > from the BASIC prompt, not from the main menu and tell us what you see. > > If it prints out the CO file's header, we can figure out if > > a) The clear statement is right > b) The beep is coming as a BASIC load issue, or for some other reason. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
On Sun, Jan 27, 2019 at 12:55 PM Fugu ME100 wrote: > The RAM TPDD is most likely conflicting with the the REX program. The > best method is to use TEENY to download the RF149.CO file. I have never > used the RAM TPPD to program a REX > Well. TEENY is fine, and Steve says that's what he tested with, so I agree that's the best way to go. But let me do my small part to prevent cargo cult misunderstandings though... Saying TSDOS "conflicts" with rf149.co doesn't make any sense to me. RAM based DOSes that aren't running don't conflict with other CO programs. If they did, there wouldn't be much point to them, because part of the point of a DOS is to be able to inload CO files, and then run them. When a DOS inloads a CO program, it inloads it into the file system portion of RAM. If you don't have enough RAM to add the file to the RAM file system, the DOS will give you an error. But that didn't happen... it loaded the CO into the file system. Note that the inload just places it in the file system. It doesn't run it. It doesn't copy the program to the place it needs to run. If it did, it might overwrite itself! But it doesn't, because that's not how it works. Then you exit the DOS, you enter a CLEAR statement if the file needs to run lower than whatever HIMEM is currently set to, likely because of a previous clear for other programs you run (like the DOS). The program then launches and runs. The one area you might say this is not true is that TS-DOS can be "hooked" into BASIC to add some extensions. Those extensions must be copied and run from somewhere, so it's possible they could conflict. The most likely thing IMO is his REX is not making contact or it is faulty in some other way. As you say the burn should complete in 5 minutes. Steve does your program ever beep for any reason? :-) -- John. -= Model T's Forever =-
Re: [M100] Unable to Load TEENY to MT
John, all I meant by conflict is if TSDOS in RAM (16k ish?) + my code(8k ish?) cause the M100 to run out of memory. TSDOS is a lot of program to merely load one .CO. But I really don't know specifically if everything can reside in RAM at the same time with a low CLEAR at 55000. when himem is not set correctly, ... a .CO program beeps, of course, on failed start up. I don't recall but I don't think that any of my routines beep. they might. I really don't remember ;) On Sun, Jan 27, 2019 at 4:24 PM John R. Hogerhuis wrote: > > > On Sun, Jan 27, 2019 at 12:55 PM Fugu ME100 wrote: > >> The RAM TPDD is most likely conflicting with the the REX program. The >> best method is to use TEENY to download the RF149.CO file. I have never >> used the RAM TPPD to program a REX >> > > Well. > > TEENY is fine, and Steve says that's what he tested with, so I agree > that's the best way to go. > > But let me do my small part to prevent cargo cult misunderstandings > though... > > Saying TSDOS "conflicts" with rf149.co doesn't make any sense to me. > > RAM based DOSes that aren't running don't conflict with other CO programs. > If they did, there wouldn't be much point to them, because part of the > point of a DOS is to be able to inload CO files, and then run them. > > When a DOS inloads a CO program, it inloads it into the file system > portion of RAM. If you don't have enough RAM to add the file to the RAM > file system, the DOS will give you an error. > > But that didn't happen... it loaded the CO into the file system. Note that > the inload just places it in the file system. It doesn't run it. It doesn't > copy the program to the place it needs to run. If it did, it might > overwrite itself! > > But it doesn't, because that's not how it works. > > Then you exit the DOS, you enter a CLEAR statement if the file needs to > run lower than whatever HIMEM is currently set to, likely because of a > previous clear for other programs you run (like the DOS). > > The program then launches and runs. > > The one area you might say this is not true is that TS-DOS can be "hooked" > into BASIC to add some extensions. Those extensions must be copied and run > from somewhere, so it's possible they could conflict. > > The most likely thing IMO is his REX is not making contact or it is faulty > in some other way. > > As you say the burn should complete in 5 minutes. > > Steve does your program ever beep for any reason? > > :-) > > -- John. > > -= Model T's Forever =- >
Re: [M100] Unable to Load TEENY to MT
Just a couple of observations from programming a few REXs :) * Even if the REX were dead RF149.co always seems to run to completion. I have run it with a few faulty REXs. It will complete and be quite happy. Then when you try to perform the BASIC CALL it fails. If the REX has failed then what happens is either the erasing part runs in a few seconds rather than 30s and the programming part will run quite quickly. It will still download both ROM image files from the TPDD drive. In fact it looks like it completes programming – but it does not. Locking up trying to download the ROM images would indicate to me that it is having a problem loading the ROM images from the TPDD drive. The RF149.co runs regardless of the state of the REX. The only time this is not the case is if the REX is inserted backwards, but then the Model T locks up :) * The fact RAM TPDD has been loaded and, I believe, inserts hooks in various places to me implies that it could conflict with the RF149.co internal DOS program, whereas TEENY I believe is quite clean in that respect. I only know from bitter experience that when I was attempting to program a REX originally using RAM TPDD it would cause problems – including the beep. Whereas using TEENY caused no problems. I can only conclude that RAM TPDD somehow conflicted with the REX programming using RF149.co. Simply clearing a piece of RAM does not undo anything RAM TPDD might of done to various hooks, timers or buffers. I think a cold boot followed by installing TEENY then downloading RF149.co will work. Whether the REX is dead or not RF149.co will run to completion. Only when you do the BASIC CALL do you find out if it is successful :-D If it takes <2mins to program, the REX is probably faulty, if it takes approx 5mins it is probably good. From: M100 mailto:m100-boun...@lists.bitchin100.com>> on behalf of "John R. Hogerhuis" mailto:jho...@pobox.com>> Reply-To: mailto:m...@bitchin100.com>> Date: Sunday, January 27, 2019 at 1:25 PM To: mailto:m...@bitchin100.com>> Subject: Re: [M100] Unable to Load TEENY to MT On Sun, Jan 27, 2019 at 12:55 PM Fugu ME100 mailto:b4me...@hotmail.com>> wrote: The RAM TPDD is most likely conflicting with the the REX program. The best method is to use TEENY to download the RF149.CO<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2FRF149.CO&data=02%7C01%7C%7C493abc44724140a7c47308d6849dd981%7C84df9e7fe9f640afb435%7C1%7C0%7C636842210819854880&sdata=2MeQKbFM1wovZpHCFW8IAIksrgnyH5sFeGDlmQWJr30%3D&reserved=0> file. I have never used the RAM TPPD to program a REX Well. TEENY is fine, and Steve says that's what he tested with, so I agree that's the best way to go. But let me do my small part to prevent cargo cult misunderstandings though... Saying TSDOS "conflicts" with rf149.co<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frf149.co&data=02%7C01%7C%7C493abc44724140a7c47308d6849dd981%7C84df9e7fe9f640afb435%7C1%7C0%7C636842210819864879&sdata=bSYsn0piPZ4QQtSOoqz3wkmI549OZgOc7kF46BfMivM%3D&reserved=0> doesn't make any sense to me. RAM based DOSes that aren't running don't conflict with other CO programs. If they did, there wouldn't be much point to them, because part of the point of a DOS is to be able to inload CO files, and then run them. When a DOS inloads a CO program, it inloads it into the file system portion of RAM. If you don't have enough RAM to add the file to the RAM file system, the DOS will give you an error. But that didn't happen... it loaded the CO into the file system. Note that the inload just places it in the file system. It doesn't run it. It doesn't copy the program to the place it needs to run. If it did, it might overwrite itself! But it doesn't, because that's not how it works. Then you exit the DOS, you enter a CLEAR statement if the file needs to run lower than whatever HIMEM is currently set to, likely because of a previous clear for other programs you run (like the DOS). The program then launches and runs. The one area you might say this is not true is that TS-DOS can be "hooked" into BASIC to add some extensions. Those extensions must be copied and run from somewhere, so it's possible they could conflict. The most likely thing IMO is his REX is not making contact or it is faulty in some other way. As you say the burn should complete in 5 minutes. Steve does your program ever beep for any reason? :-) -- John. -= Model T's Forever =-
Re: [M100] Unable to Load TEENY to MT
On Sun, Jan 27, 2019 at 1:46 PM Stephen Adolph wrote: > John, all I meant by conflict is if TSDOS in RAM (16k ish?) + my code(8k > ish?) cause the M100 to run out of memory. > Ah. Well, TS-DOS didn't complain which is why it seems like there is enough room. > TSDOS is a lot of program to merely load one .CO. But I really don't know > specifically if everything can reside in RAM at the same time with a low > CLEAR at 55000. > Totally true, but I think he would find out while running TS-DOS, and trying to inload the CO. It should error out then because not enough space to add to the file system. If the file system grew so much that a low clear wouldn't work, there is a question of whether BASIC would refuse the CLEAR command. But the solution would be, delete TS-DOS after loading the CO into RAM file system, but before doing the CLEAR. > when himem is not set correctly, ... a .CO program beeps, of course, on > failed start up. > Yes. BTW, why do you document a clear at 55,000 rather than at what TOP is set to a few hundred bytes higher? Do you use memory before your program? > I don't recall but I don't think that any of my routines beep. they > might. I really don't remember ;) > OK. -- John
Re: [M100] Unable to Load TEENY to MT
On Sun, Jan 27, 2019 at 1:48 PM Fugu ME100 wrote: > >- Simply clearing a piece of RAM does not undo anything RAM TPDD >might of done to various hooks, timers or buffers. > > True, but that is what the DOS-ON/DOS-OFF command in TS-DOS does. It hooks / unhooks the BASIC extensions. If it does not, it is a bug in TS-DOS. Which of course is possible, it wouldn't be the first bug discovered. -- John. >
Re: [M100] Unable to Load TEENY to MT
Ah interesting. So perhaps the method should be to perform the DOS-ON/DOS-OFF first and then clearmem. Rather than just clearmem. That might clear everything out properly. From: M100 mailto:m100-boun...@lists.bitchin100.com>> on behalf of "John R. Hogerhuis" mailto:jho...@pobox.com>> Reply-To: mailto:m...@bitchin100.com>> Date: Sunday, January 27, 2019 at 2:08 PM To: mailto:m...@bitchin100.com>> Subject: Re: [M100] Unable to Load TEENY to MT On Sun, Jan 27, 2019 at 1:48 PM Fugu ME100 mailto:b4me...@hotmail.com>> wrote: *Simply clearing a piece of RAM does not undo anything RAM TPDD might of done to various hooks, timers or buffers. True, but that is what the DOS-ON/DOS-OFF command in TS-DOS does. It hooks / unhooks the BASIC extensions. If it does not, it is a bug in TS-DOS. Which of course is possible, it wouldn't be the first bug discovered. -- John.
Re: [M100] Unable to Load TEENY to MT
> >> when himem is not set correctly, ... a .CO program beeps, of course, on >> failed start up. >> > > Yes. BTW, why do you document a clear at 55,000 rather than at what TOP is > set to a few hundred bytes higher? Do you use memory before your program? > > John, just laziness on my part. D800 55296
Re: [M100] Unable to Load TEENY to MT
On Sun, Jan 27, 2019 at 2:11 PM Stephen Adolph wrote: > > >>> when himem is not set correctly, ... a .CO program beeps, of course, on >>> failed start up. >>> >> >> Yes. BTW, why do you document a clear at 55,000 rather than at what TOP >> is set to a few hundred bytes higher? Do you use memory before your >> program? >> >> > > John, just laziness on my part. > D800 > 55296 > > Or laziness on the user's behalf ;-) 55,000 is certainly easier to remember -- John.
Re: [M100] Unable to Load TEENY to MT
I have only ever used TS-DOS RAM to load RFx49.co -- I've programmed over 40 REXes with TS-DOS in RAM and never had an issue. In fact, I didn't even realize that RFx49.c had its own DOS routines -- I assumed that it needed DOS in RAM. Not having to load full TS-DOS would save a bit of time programming REXes. -Josh
Re: [M100] Unable to Load TEENY to MT
Josh: I can appreciate the success you and so many have had. I just wish I could also share in that success and enjoy the benefits of a fully functioning Rex. For my latest attempt I used my daily driver MT. TS-DOS went in nicely using TEXT to capture the .DO file from RealTerm. RF149.CO seemed to run as expected -- indicating progression of loading the BX files. Unfortunately, after a hard-reset and CALL63012 no REXMGR. Not quite sure what else to try. God bless, GregS <>< - Original Message - From: "Josh Malone" To: m...@bitchin100.com Sent: Sunday, January 27, 2019 5:23:51 PM Subject: Re: [M100] Unable to Load TEENY to MT I have only ever used TS-DOS RAM to load RFx49.co -- I've programmed over 40 REXes with TS-DOS in RAM and never had an issue. In fact, I didn't even realize that RFx49.c had its own DOS routines -- I assumed that it needed DOS in RAM. Not having to load full TS-DOS would save a bit of time programming REXes. -Josh
Re: [M100] Unable to Load TEENY to MT
On Tue, Jan 29, 2019 at 12:21 PM Greg Swallow wrote: > Josh: > > I can appreciate the success you and so many have had. I just wish I could > also share in that success and enjoy the benefits of a fully functioning > Rex. > > For my latest attempt I used my daily driver MT. TS-DOS went in nicely > using TEXT to capture the .DO file from RealTerm. RF149.CO seemed to run > as expected -- indicating progression of loading the BX files. > Unfortunately, after a hard-reset and CALL63012 no REXMGR. Not quite sure > what else to try. > > God bless, > > Seems like it's either a contact issue between your Rex and laptop, or there is a hardware issue with your Rex board. Either way, seems like a hardware issue. I recommend you should work directly with the seller. He may want to swap your unit or assist you with getting the Rex to make good contact. -- John.
Re: [M100] Unable to Load TEENY to MT
Has the ram in the M100 been really verified? -- bkw On Tue, Jan 29, 2019 at 3:31 PM John R. Hogerhuis wrote: > > > On Tue, Jan 29, 2019 at 12:21 PM Greg Swallow wrote: > >> Josh: >> >> I can appreciate the success you and so many have had. I just wish I >> could also share in that success and enjoy the benefits of a fully >> functioning Rex. >> >> For my latest attempt I used my daily driver MT. TS-DOS went in nicely >> using TEXT to capture the .DO file from RealTerm. RF149.CO seemed to run >> as expected -- indicating progression of loading the BX files. >> Unfortunately, after a hard-reset and CALL63012 no REXMGR. Not quite sure >> what else to try. >> >> God bless, >> >> > Seems like it's either a contact issue between your Rex and laptop, > or there is a hardware issue with your Rex board. > > Either way, seems like a hardware issue. > > I recommend you should work directly with the seller. He may want to swap > your unit or assist you with getting the Rex to make good contact. > > -- John. > -- bkw
Re: [M100] Unable to Load TEENY to MT
I haven't run a RAMTST on the first two MT I tried, but I have on this latest. I've been using it with the SuperROM for some time. I hadn't intended to use the Rex with this one, but I am getting farther in the process. Am figuring more along the connection is the problem some how. If I can't get it functioning today or Wednesday, I'll see what I can do with Greg over at ArcadeShopper.com. God Bless, GregS <>< - Original Message - From: "Brian White" To: m...@bitchin100.com Sent: Tuesday, January 29, 2019 1:33:49 PM Subject: Re: [M100] Unable to Load TEENY to MT Has the ram in the M100 been really verified? -- bkw
Re: [M100] Unable to Load TEENY to MT
Agreed - sounds like a hardware problem. If you can't get the seller to assist you, contact me off-list and we can arrange something. I can test your REX and repair it if necessary. Have you ever used an option ROM or REX in the machines you're testing with now? On Tue, Jan 29, 2019, 3:31 PM John R. Hogerhuis > > On Tue, Jan 29, 2019 at 12:21 PM Greg Swallow wrote: > >> Josh: >> >> I can appreciate the success you and so many have had. I just wish I >> could also share in that success and enjoy the benefits of a fully >> functioning Rex. >> >> For my latest attempt I used my daily driver MT. TS-DOS went in nicely >> using TEXT to capture the .DO file from RealTerm. RF149.CO seemed to run >> as expected -- indicating progression of loading the BX files. >> Unfortunately, after a hard-reset and CALL63012 no REXMGR. Not quite sure >> what else to try. >> >> God bless, >> >> > Seems like it's either a contact issue between your Rex and laptop, > or there is a hardware issue with your Rex board. > > Either way, seems like a hardware issue. > > I recommend you should work directly with the seller. He may want to swap > your unit or assist you with getting the Rex to make good contact. > > -- John. >
Re: [M100] Unable to Load TEENY to MT
Josh, I would appreciate any help. As for option ROMs, yes. Two of the three MTs have the SuperROM in them. Used that in trying to figure contact issues. the top surfaces of the PCB for both packages are at the same level, but the Rex has a thinner board thickness. Other than that I am afraid -- even with my shop magnifier, I just can't tell if an individual pin is actually setting properly or not. Thanks, GregS <>< - Original Message - From: "Josh Malone" To: m...@bitchin100.com Sent: Tuesday, January 29, 2019 1:51:52 PM Subject: Re: [M100] Unable to Load TEENY to MT Agreed - sounds like a hardware problem. If you can't get the seller to assist you, contact me off-list and we can arrange something. I can test your REX and repair it if necessary. Have you ever used an option ROM or REX in the machines you're testing with now? On Tue, Jan 29, 2019, 3:31 PM John R. Hogerhuis
Re: [M100] Unable to Load TEENY to MT
The REX board needs to be seated all the way down. It should feel firmly inserted into the socket, it might not be making good contact all the way round. The REX programmer will run to completion even if the board is not properly inserted. After running CALL63012 does the machine lock up or return straight to the MENU screen? If if returns to the menu immediately then in general the REX is not being seen, a bad REX will usually cause the MT to lock up when trying to start the REXMGR - if the onboard FLASH is corrupted. On 29/1/19, 12:51 PM, "M100 on behalf of Greg Swallow" wrote: >I haven't run a RAMTST on the first two MT I tried, but I have on this >latest. I've been using it with the SuperROM for some time. I hadn't >intended to use the Rex with this one, but I am getting farther in the >process. Am figuring more along the connection is the problem some how. >If I can't get it functioning today or Wednesday, I'll see what I can do >with Greg over at ArcadeShopper.com. > >God Bless, > >GregS <><
Re: [M100] Unable to Load TEENY to MT
On Tue, Jan 29, 2019 at 4:11 PM Greg Swallow wrote: > > Josh, > > I would appreciate any help. As for option ROMs, yes. Two of the three MTs > have the SuperROM in them. Used that in trying to figure contact issues. the > top surfaces of the PCB for both packages are at the same level, but the Rex > has a thinner board thickness. Other than that I am afraid -- even with my > shop magnifier, I just can't tell if an individual pin is actually setting > properly or not. > > Thanks, > > GregS <>< Can you send a high quality picture of the installed REX? You did install the spacer board and ribbon, right? -Josh
Re: [M100] Unable to Load TEENY to MT
Josh, Yep. Greg/ArcadeShopper delivers it all nicely together using some micro-thin double stick. It looks like it should pop right in like other Option OMS (SR). I have removed it and added multiple thinner layers in an attempt to match the bottom level of the PCB and hope for a better connection, but that did not work out either. I should probably just give Greg a call and see what can be done. Thanks, GregS <>< - Original Message - From: "Josh Malone" To: m...@bitchin100.com Sent: Tuesday, January 29, 2019 2:50:30 PM Subject: Re: [M100] Unable to Load TEENY to MT Can you send a high quality picture of the installed REX? You did install the spacer board and ribbon, right? -Josh
