On Sun, Jan 27, 2019 at 12:55 PM Fugu ME100 <[email protected]> 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 =-
