Must admit I have never had that happen, all the faults I have seen usually allow the RF149.co run to completion. I have plugged them in backwards a few times though :-D Especially when trying to debug crashing programmings.
I have had problems where the +5V has failed and corrupted a REX, not sure how that can happen, but reprogramming it usually brings it back to life. Yes sometimes I forget the REX is in there when playing with system bus plugins. From: M100 <m100-boun...@lists.bitchin100.com<mailto:m100-boun...@lists.bitchin100.com>> on behalf of Stephen Adolph <twospru...@gmail.com<mailto:twospru...@gmail.com>> Reply-To: <m...@bitchin100.com<mailto:m...@bitchin100.com>> Date: Sunday, January 27, 2019 at 2:07 PM To: <m...@bitchin100.com<mailto:m...@bitchin100.com>> Subject: Re: [M100] Unable to Load TEENY to M1 the fact that you say that RF149.CO<https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2FRF149.CO&data=02%7C01%7C%7Cc9ecc72a9f5d45dc44fa08d684a3eb41%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636842236886887504&sdata=E4CJLda5LtBoDDi6g6TyMyFFuIeTlm9TJZOqAhhXYWs%3D&reserved=0> hung during burning of a file (in this case the RexManager software) to me says that the flash is stalled in the "BUSY" state. One of 2 things (1) REX is improperly seated (2) REX has a hardware defect In my experience contrary to Fugu (i am very reluctant to differ from him ever!) all of my REX software can hang when the Flash gets stuck in BUSY state. This happens when for example the software tries to REWRITE a "1" to an address that has already been WRITTEN to "0" value. This only happens if the software is buggy, or somehow there is a hardware defect, like a malfunctioning address line connection. ..Steve On Sun, Jan 27, 2019 at 4:58 PM Greg Swallow <gswal...@mchsi.com<mailto:gswal...@mchsi.com>> wrote: I did get farther, even with TS-DOS loaded. Ran RF149.CO<https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2FRF149.CO&data=02%7C01%7C%7Cc9ecc72a9f5d45dc44fa08d684a3eb41%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636842236886897509&sdata=xpWzlxv0z4sqnYyjSLQ3%2BYP2KOqS8R0kZvgDKtUPDtw%3D&reserved=0> from MENU after the LOADM. It seem to start ok, but then nothing seemed to happen when left it half the night loading 0:RF149.BX. Maybe I should have let go all night. God Bless, GregS <>< ----- Original Message ----- From: John R. Hogerhuis <jho...@pobox.com<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 <gswal...@mchsi.com<mailto:gswal...@mchsi.com> wrote: > CLEAR0,55000: > LOADM"RF149.CO<https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2FRF149.CO&data=02%7C01%7C%7Cc9ecc72a9f5d45dc44fa08d684a3eb41%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636842236886907520&sdata=zw8zFc7tWzIb8sTLa7wunAD9K5lXMSCI9xQq0W%2BCG44%3D&reserved=0>" > gives > > Top: 55302 > End: 60148 > Exe: 55302 > > Hope this helps > > GregS <>< > > > ----- Original Message ----- > From: "John R. Hogerhuis" <jho...@pobox.com<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://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2FRF149.CO&data=02%7C01%7C%7Cc9ecc72a9f5d45dc44fa08d684a3eb41%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636842236886917531&sdata=%2FB7v5fBY%2BaCp%2F00srYCtPfPQcASrIbSLFSHh%2FhjEezs%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. >
