kelli217

The markdown code in the PRG is mis-formatted; the list of routines should look like this: $FF4A: CLOSE_ALL – close all files on a device $FF8D: LKUPLA – search tables for given LA $FF8A: LKUPSA – search tables for given SA $FF62: DLCHR - activate a text mode font in the video hardware [not yet implemented] $FF65: PFKEY – program a function key [not yet implemented] $FF74: FETCH – LDA (fetvec),Y from any bank $FF77: STASH – STA (stavec),Y to any bank $FF7A: CMPARE – CMP (cmpvec),Y to any bank $FF7D: PRIMM – print string following the caller’s code The current markdown code lacks two spaces at the end of the line, and so the rendering has them all smashed together, making it look like this: $FF4A: CLOSE_ALL – close all files on a device $FF8D: LKUPLA – search tables for given LA $FF8A: LKUPSA – search tables for given SA $FF62: DLCHR - activate a text mode font in the video hardware [not yet implemented] $FF65: PFKEY – program a function key [not yet implemented] $FF74: FETCH – LDA (fetvec),Y from any bank $FF77: STASH – STA (stavec),Y to any bank $FF7A: CMPARE – CMP (cmpvec),Y to any bank $FF7D: PRIMM – print string following the caller’s code

I purchased several copies of Compute, and Compute's Gazette, but I wasn't what one would call diligent about it, and didn't subscribe. I never managed to get one of the issues that had a version of SpeedScript in it.

It... might have been. I don't know anything about the history of the program, and I've never used the CP/M app by that name. It used commands inserted onto a separate line to do stuff like changing line spacing or margins or justification, sort of like WordStar's dot commands. It had all the hallmarks of a text-screen-oriented word processor that had been ported over to a GUI-based platform.

What @Elektron72 said is correct. Here's a short tutorial for using SYS in BASIC 2.0: The BASIC interpreter will first push the existing contents of the registers onto the stack, then load the A register with the value stored in location 780 ($030C), X with the value stored in location 781 ($030D), Y with the value stored in location 782 ($030E), and the status register with the value stored in location 783 ($030F). Then it will JSR to the address provided as the argument to the SYS command itself. When (or if) the routine executes an RTS to return to BASIC, the reverse happens. The contents of A are stored in 780, etc. Finally, it will pull the previous register contents from before the SYS call back into the registers, and resume BASIC execution at the next instruction.

The KERNAL routine SCREEN is what you are looking for. When you call it, it returns the screen width in the X register and height in the Y register. Calling it from BASIC: 10 SYS $FFED : X = PEEK(781) : Y = PEEK(782)

And you're going to bolt it down to the table it sits on, right?

Well begun is half done! Somewhere around here or on the Facebook group there's a compiled BASIC version someone made. There might also be an assembly version.

Yeah, when I first got GEOS, my printer was a Commodore MPS-803, and you could see the gaps between dots. Later I got a printer that was more or less a clone of an Epson *X (Nakajima AR-30, sold by Sears as an 'SR-2000' brand), but with both IEC and Centronics ports on the back, and that worked much better. I kept that printer when I upgraded to the Amiga. The MPS-803 was what I had back when I was using Bank Street Writer, and the lack of enough pins on the printhead to make a descender in text mode meant that I was always playing with fire when using it for anything scholastic, as the teachers couldn't easily tell whether I'd typed an uppercase or lowercase P — and the rubric was that if they couldn't tell, it was wrong.

When I had my 64, I went from Bank Street Writer, which was short on features but responsive, to geoWrite, which had lots of features but they came at the cost of speed.

I know that tendency to stick with things pretty well. When you find something that works, even if it's a little clunky, it's difficult to switch. WS2K rather forced that switch on their users. When I first found a word processor that was powerful enough, fast enough, and usable enough, I stuck with it for quite a while. Anybody else remember Write from the Gold Disk Amiga Appetizer? Yeah, you weren't going to write a doctoral thesis with it or create a manuscript ready for publishing, but it had all the basic features and could handle fairly large documents.

I've used WordStar. I've used an early PC version that didn't even support subdirectories, and I've also used WordStar 2000, which was what I will diplomatically call 'quite different from the standard WordStar.' I have a version of it. It's an early version, for an obscure MS-DOS machine that isn't an IBM PC clone. I have the machine, a Sanyo MBC-555, but I've booted it maybe twice since I got it in around 1997. The capacitors are probably dead. Anyway, the machine came with all the office productivity software that MicroPro offered at the time. WordStar, CalcStar, DataStar. And I have the original disks and manuals, much like I do for WordPerfect for Amiga.

It ought to be mature, being based on a product that was first released in 1985!

This is just a continuation of the discussion on WordPerfect that started as a tangent to the "Commander X16 Deluxe Keyboard -- SysReq/PrtSc, Scroll Lock and Pause/Break" thread in the X16 General Chat subforum. @Michael Parson, I don't currently have any of my Amigas up and running, and I can't quite lay my hands on the installation floppies. Thanks for your offer of help, though. @EMwhite, it isn't the Windows version. It's the DOS version... but it's 5.1.

We can pick up the WP tangent over on the General Retro Chat subforum.

Please be careful when offering up ideas for design stuff. I did a thing once where all I did was create derivatives of the logos for the P, C, and E models with sports medal coloration for the model designation, and they had to take it down because I had neglected to mention that they had my explicit permission to use it for free in perpetuity, and without that kind of permission, there are lots of potential legal ramifications to using designs from other people.