the fact that you say that RF149.CO hung during burning of a file (in this case the RexManager software) to me says that the flash is stalled in the "BUSY" state. One of 2 things (1) REX is improperly seated (2) REX has a hardware defect
In my experience contrary to Fugu (i am very reluctant to differ from him ever!) all of my REX software can hang when the Flash gets stuck in BUSY state. This happens when for example the software tries to REWRITE a "1" to an address that has already been WRITTEN to "0" value. This only happens if the software is buggy, or somehow there is a hardware defect, like a malfunctioning address line connection. ..Steve On Sun, Jan 27, 2019 at 4:58 PM Greg Swallow <[email protected]> wrote: > I did get farther, even with TS-DOS loaded. Ran RF149.CO from MENU after > the LOADM. It seem to start ok, but then nothing seemed to happen when left > it half the night loading 0:RF149.BX. Maybe I should have let go all night. > > God Bless, > > GregS <>< > ----- Original Message ----- > From: John R. Hogerhuis <[email protected]> > To: [email protected] > 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 <[email protected] wrote: > > > CLEAR0,55000: LOADM"RF149.CO" gives > > > > Top: 55302 > > End: 60148 > > Exe: 55302 > > > > Hope this helps > > > > GregS <>< > > > > > > ----- Original Message ----- > > From: "John R. Hogerhuis" <[email protected]> > > To: [email protected] > > 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. > > > >
