jnp@calmasd.UUCP (06/06/86)
I'm running a TRS-80 Mod 4, and TRSDOS 6.2.1
We all know that Tandy has all but scrapped the Mod 4 but I
have a bunch of software that is still quite functional.
To protect this investment I would like to get the source
code for TRSDOS 6.2.x. I've heard that Logical Systems
(the producer of TRSDOS) no longer sells the source, but that
another company still does. Anyone know who these people are?
Please e-mail. If there is any interest I'll post the results. Thanks.
--
These opinions are solely mine and in no way reflect those of my employer.
...{ucbvax|decvax}!sdcsvax!calmasd!jnp John M. Pantone @ GE/Calma San Diegouhclem@trsvax.UUCP (06/11/86)
<The Knights who say 'Letni' demand.....A SEGMENT REGISTER!!!....> EATEATEATE The SOURCE is no longer available from Logical Systems. The sales of that publication has been turned over to MISOSYS. The head guy at LSI says you get all three editions (System, Libraries and Utilities) for $99 total from Misosys. Formally the price was $249 for the set of three. MISOSYS order number is 1-800-MISOSYS, or 1-703-450-4181. In all other respects, LSI plans to continue to be the support-house for %%%DOS 6.x series operating systems. ---- "Then, when you have found another segment register, we can set it next to this one and do string moves. Then... you must execute the following instructions with interrupts enabled: ES: REP MOVSW" "We'll do no such thing! Do a string move with a segment override and survive an interrupt? It can't be done!" <This information is provided by an individual and is not nor should be construed as being provided by Radio Shack or Tandy Corp. Radio Shack/Tandy Corp has no obligation to support the information provided in any way, and might seize up if they did. They would rather you buy some "Science Fair" coloring books anyway.> "Thank you, Uh Clem." Frank Durda IV @ <trsvax!uhclem> Letni is a registered trademark of TtLG
res@ihlpl.UUCP (Rich Strebendt @ AT&T Information Systems - Indian Hill West; formerly) (06/15/86)
An addition to the following request: > I'm running a TRS-80 Mod 4, and TRSDOS 6.2.1 > > We all know that Tandy has all but scrapped the Mod 4 but I > have a bunch of software that is still quite functional. > To protect this investment I would like to get the source > code for TRSDOS 6.2.x. I have been running a TRS-80 Model II for several years now and have been fairly well pleased with it. As the gentle reader is undoubtedly aware, the Model II was canned by Tandy several aeons ago. (You know that you are using a dead-end machine when $200 software packages are put on sale for $29.95 to clear the store shelves for the DESIRABLE products!) I, also, would like to get a copy of the source code for the Model II TRSDOS 2.1 along with supporting documentation on such matters as how the command processor overlay technique works. Perhaps someone at Tandy can respond to this request or provide a pointer to the proper person within Tandy to whom such a request should be sent. Rich Strebendt ...!ihnp4!iwsl6!res
gene@cooper.UUCP (06/19/86)
> An addition to the following request: > Speaking of which, does anyone know how the TRSDOS system calls (on disk, NOT the ROM calls) work? I've been going freaky trying to get my program to simply copy from one file to another, later to become a few filter routines. I've gotten as far as opening both files (specified in the command line), checking the syntax, reporting any errors that might occur, etc, but I have _not_ been able to even get a physical record into RAM. Since the TRSDOS 1.3 manual doesn't have any sample programs that are of any help, I decided to try to find the source code and figure it out for myself. Do any AL wizzes know how to do it? For my purposes, I am dealing with physical records from the disk (not logical records), with the LRL (logical record length) being 256 bytes (a disk sector). Everything assembles just fine, with a clean exit to the DOS, except that the newly-created file has nothing written out! A "hunch" tells me that somehow the $POSN routine has to be called after/before every $READ and/or $WRITE. Any clues??? By the way, if I get the basic filters working, I'd be glad to share them on the net. As an enticement, think about using Scripsit or SuperScripsit (ASCII file output) to edit a BASIC file, EDTASM file, etc. Using BASIC to filter out a long file takes just about years for a substantial file. I found out that's the only way to mask out eighth_bits, entab/detab, and so on. Doing it in AL will kill that time to practically nothing. Like I said, just ask, and ye shall receive. For now, I guess I have to do the asking... Usenet (UUCP) Address: harvard!cmcl2\ {ihnp4 | seismo}!allegra>!phri!cooper!gene columbia/ philabs/