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 <[email protected]<mailto:[email protected]>> on behalf of "John R. Hogerhuis" <[email protected]<mailto:[email protected]>> Reply-To: <[email protected]<mailto:[email protected]>> Date: Sunday, January 27, 2019 at 1:25 PM To: <[email protected]<mailto:[email protected]>> Subject: Re: [M100] Unable to Load TEENY to MT On Sun, Jan 27, 2019 at 12:55 PM Fugu ME100 <[email protected]<mailto:[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<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2FRF149.CO&data=02%7C01%7C%7C493abc44724140a7c47308d6849dd981%7C84df9e7fe9f640afb435aaaaaaaaaaaa%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%7C84df9e7fe9f640afb435aaaaaaaaaaaa%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 =-
