Yes. For a while, every software publisher for the PC followed a similar packaging format with their software, that of a hardback, looseleaf manual that fits in a shell.
I don't think IBM mandated this in any way, it was just follow-the-leader. So if you saw a picture of a bunch of similar manuals, then they had to have bought all of them save the few that came with the machine. The only time I can think of more software being bundled was back around the MS-DOS 1.25 days, when some of the OEMs would include a full copy of MASM with the machine. I used that version clear up into the 90s because it didn't require all the useless definitions later assemblers did, and it would still produce a single-segment .COM program if your code was small enough and didn't need to leap outside the current segment.
Hate to change the subject, but I've been using TASM/TLINK lately to "practice." It's the first one I've used, I like it so far. Would you say trash TASM for MASM?
Wanted to write something to utilize my Tandy 1000 SL or TL's Mode E video mode, 640x200x16. There's no BIOS routine to set up this video mode, so all of the video registers have to be set up manually. Made a A-Z font set in PC-PAINT in uncompressed TIFF format, I found TIFF format makes it easy to rasterize the image. All I've got so far is setting the video mode and displaying either the entire font set or just one character of it. Next thing I'm going to try is smooth bouncing ball animation utilizing both 64k pages of this video mode and switching back and forth between the two.
The last time I assembled for an x86 device was 1993. I have no experience with Turbo Assembler, so I can't really guide you. I know the version of Microsoft Assembler I was using probably didn't understand anything past 8086 instructions, so I would say don't use that one.
But I doubt you could, seeing as how it had to be lifted from an 8" floppy...The only thing I can say is TASM is probably a good period-correct choice for your machine. They all produce executable code, so it's whatever your comfortable with. I just preferred the old MASM because you didn't have to define memory models and segment definitions, it by default only produced single-segment code.
Thanks for the advice. First live person to ever mention these things to me. Didn't realize you're probably 20 years older than I am until today... I haven't even reached double-digit age by 1993!
(post is archived)