Thread View: net.micro.atari8
2 messages
2 total messages
Started by Bill Dippert
Mon, 07 Apr 1986 23:43
256k Upgrades
Author: Bill Dippert
Date: Mon, 07 Apr 1986 23:43
Date: Mon, 07 Apr 1986 23:43
20 lines
1703 bytes
1703 bytes
Does anyone have any answers (or questions) in regards to David Young's comments to me about the RAMBO XL board vs the Newall board? If I had of known that a Newell board would work in an 1200XL I might have gone that way. However, I did not. His comments about it not switching the ANTIC chip worry me, but it seeminly is contracdicted by the instructions which (admittedly prejudiced) say that RAMBO XL is 100% compatible with Atari Writer+, BASIC XE, Paper Clip, Synfile+ and others? What does Young's comments really mean? Also, does anyone feel (as I do) that Young's scheme of using one of the additional 16k banks for his Atariwriter+ 80 col scheme is NOT the way to go? Why use up some of the additional memory when you have 16k available to you at the cartridge slot? (Either use a cartridge or at least use the 16k memory allocated for the cart.) Personally, I put out a magazine using Atarwriter+ as my wordprocessor and believe you me -- I use all of the memory of my 130XE. There is not 16k available for his 80 col. soft- ware/firmware. Does some of the CDY stuff already use the cartridge 16k memory allocated? --Bill--
Re: 256k Upgrades
Author: C. David Young
Date: Tue, 08 Apr 1986 13:03
Date: Tue, 08 Apr 1986 13:03
44 lines
3109 bytes
3109 bytes
Since Bill has expressed curiosity about some of the details of my AtariWriter Plus conversion to 80 columns, I will talk a little bit more about it since it might be of general interest. AW+ uses the extra memory of the 130XE (or compatible) in a kludgy sort of way. (At least it appears to be kludgy; I have not used the word processor enough to speak from experience.) Of the 5 16K banks that map into the $4000-$7FFF range, the first 3 (the main bank and the first 2 extended banks) are used as 3 independent 16K text buffers. The fourth is used as the kill buffer and the fifth is largly unused: only the first 4K is used for miscellaneous routines. That leaves 12K of this bank unused. HMMM. Plenty of room for the 8K 80 column screen if only we could get Antic to look up there. Now Bill was wondering why I do not use the cartridge area for the 80 column screen. The answer is that all that area has already been used by the program. It is true that there is about 1K at the top of memory that is used for the 40 column screen, but that is way too small for the 80 column screen. Back at the original problem, how do we get Antic to look way up into that last extended bank? Pondering this question, I was suddenly struck by ATARI's foresight (and Newell's for following the same convention in his 256KXL) of giving us the control over the Antic to force it to stay with the main memory bank even when the CPU is off looking at other banks. What if I were to rearrange the order in which the banks are used so that the last bank (the one with the free 12K) becomes the main bank? Then I could leave bit 5 of $D301 high, forcing Antic to look at my 80 column screen while the CPU was off merrily flipping banks. That is exactly what I have done. Fortunately, redefining the order of the banks was easy; there are 5 little routines used to select each of the 5 banks. I merely swapped the bank address in the first and last routine. Unfortunately, the rest of the conversion has been very tedious. In my opinion, the program is quite poorly written. The screen output is not at all elegant or structured. It is brute force and spread out in bits and pieces throughout the code. However, the conversion is about 90% complete and I hope to have it finished by June 1st. It will take the form of a binary load file that will be appended to the AP.OBJ file on the AtariWriter Plus disk. David Young -------
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads