Thread View: net.micro.atari
3 messages
3 total messages
Started by Bob Burch
Wed, 20 Nov 1985 00:04
256K 800XL Conversion updates
Author: Bob Burch
Date: Wed, 20 Nov 1985 00:04
Date: Wed, 20 Nov 1985 00:04
155 lines
7801 bytes
7801 bytes
About a month ago, I requested information concerning the
"Quarter-Meg Atari 800XL" article appearing in BYTE 9/85. At the
time, I had just ordered the necessary parts and was awaiting delivery.
I have since received those parts and have performed the upgrade.
The hardware apparently works well, however, the RAMdisk software
from BYTEnet has problems. I have not been able to get it to work.
My DOS2.0s has been configured to recognized Drive #3. The ATARIRA2
.ASM file (from BYTEnet) has options Drive 3 single density defined.
The source code was assembled to produce an AUTORUN.SYS. Upon booting,
I get a momentary screen flash of garbage resembling multiple "=" signs
across the entire screen when the AUTORUN boots. This does not seem to
be a problem. Once the DOS menu appears, the RAMdisk (D3:) should be
formatted. This operation causes the machine to hang.
Upon further investigation it appears that the "format" process
operates on banks 5 thru 0, respectively. In the source code, the
initialization code to set-up a given bank is accomplished in routine
SETBNK, while the format code is in routine FORMAT. FORMAT controls
the procedure calling SETBNK via a JSR. It appears that bank 5 formats
properly, switches to bank 4, then hangs on the RTS return from SETBNK
to FORMAT. In fact, all *odd* banks format properly while *even* banks
blow-up. Apparently the return address for the returning RTS has
been damaged in the stack when *even* numbered banks are swapped in.
Since I am not an 6502 assembly language wizard, I do not have a
FIX. I am depending (hopefully) on one of you guys to correct this
situation and release it to the World.
Judging from the responses I've seen on the Net, a number of us
are having similiar problems/interests. Since a 256KXL is of
particular interest and has exciting possibilities, I suggest that
those individuals interested form a Users Group of our own. I will
be willing to act as a clearinghouse for information. It is to our
mutual interests to share whatever associated information/software
that we can obtain. My address is
Bob Burch
6609 Charles Dr.
Mt. Airy, MD 21771
Now, to repond to other articles:
In article <oyster@uwmacc.UUCP (Vicious Oyster) writes:
>
>The local Atari user's group Hardware SIG has two working 256K 800XLs.
>I saw them demo'd at both the SIG and general meetings. They work;
>however, I think they found that the BYTE article wasn't 100% accurate,
>but since they have the hardware knowledge, have done there own modifications,
>and have also modified DOS 2.5 to work properly. The good news is that we
>(the User's Group) have made both the circuit diagrams and the DOS patches
>Public Domain. I'm not sure how you, as a member of the public,
>would go about getting this information, but since I'm here on the net
>and a member of the AUG, I'll take names of interested people and see what
>I can do. (If you ARE a member of some Atari user's group, it might be easier
>to ask your chairman or secretary or whatever to get ahold of my chairman or
>secretary or whatever, and request the info. Here's the address:
>
> Madison Area Atari Users Group (MAAUG)
> Post Office Box 56191
> Madison, WI 53705
>
>Further news: they haven't yet made a 256K 1200XL, but they've opened one
>up and said it can be done........(etc.)
>
> - joel "vo" plutchak
> [allegra,ihnp4,seismo]!uwvax!uwmacc!oyster
Thank you, Joel, we appreciate the help. In fact, about 3 weeks ago my
AUG, Potomac Atari Computer Users (PACU), president Fred Ward wrote to MAAUG
requesting the information. To date, there has been no response. We would
appreciate it if you could query your folks as to the issue. I'm supposed
to demo this thing at the AUG meeting this Saturday!! Further, your
suggestion of sharing info between user groups is good. Our group would
be glad to pass any information you could provide to other groups in
the Washington Metropolitan area (or anywhere).
In article <djk611@uiucuxa.CSO.UIUC.EDU writes:
>yes the mod works... be careful when assembling the code
Please enlighten us!!! Given recent Net articles and what has been
written above, what is it that you did that allows the mod to work?
Are we talking the same "mod"? Did you do anything special? Was the
upgrade completely successful for you? We would appreciate your
insight.
In article <DYOUNG@USC-ISID.ARPA (C. David Young) writes:
>We have been shipping the 256KXL for a couple of weeks and no problems
>have been noted. It makes the 800XL look exactly like a 130XE except that
>bits 5 and 6 of $D301 have been redefined to address twice as much memory.
Who are "we"? Can you please explain the theory of the bit-usage of
PORTB ($D301) and the significance of its use. Also, how can a given
bank be directed to the upper or lower 32K when swapped in?
In article <scp@akgua.UUCP (S.C. Pierson [Stephen]) writes:
>I've currently upgraded a 1200XL to 256K using the article from the
>september issue of Byte.....When we run Ramsgl or RAMdbl and format a
>drive, the screen turns to blue and white horizontal stripes from top
>to bottom. The rest of the computer works fine, it's just when we try to
>access the extra ram for ramdisk that it seems to fail and lock-up.....
> Steve Pierson
> AT&T Network Systems Atlanta Ga.
> 404-447-2142 c 583-2142
Steve,
This is exactly what happens on my 800XL. My stripes come at boot-time
for only a second, while the machine just hangs when trying to format.
Whatever info. I get I'll try to pass along.
In article <DYOUNG@USC-ISID.ARPA (C. David Young) writes:
>...I just finished souping up the ramdisk handlers in OMNIVIEW XL/XE
>to treat the extra RAM in our 256K upgrade for the 800XL....
Also, in a following article C David Young writes:
>That 256K RAM upgrade in BYTE was a real dog. We have got a 256K upgrade
>(256KXL) that will make your 1200 130 compatible. You can buy it without
>RAM for $50 or with for $100. The reason that the BYTE upgrade is such a
>dog is that it ends up including the stack in the bank switch area.
Hurray for Dave!!!!! Can we purchase just the software you've created for
this upgrade? If so, where can we order? Or, can you pass along the
patches necessary to kick-start the BYTE "dog" that us suckers have
fallen for. It is wonderful to know that we are not without
alternatives in this situation.
In article <dsaker@iuvax.UUCP (Daryel Akerlind)
>I too want a copy of the answers. thanks
and artivle <BillHolland.ES@XEROX.ARPA
>Please copy me in all answers, Thanks
Consider yourselves copied. We would appreciate any experiences you've
had in this matter, thank you.
Anyway, this has been long enough. I'm preparing a letter to
Claus Buchholz author of "The Quarter-Meg Atari 800XL". Any replies
I'll post on the net. I would appreciate any other contacts/replies.
Bob Burch
6609 Charles Dr.
Mt. Airy, MD 21771
(301) 831-7690 evenings
:Oh! He had high hopes....just remember that dam.
:OOPS! There goes another Quarter-Meg RAM!!!!
-wocka-wocka-wocka-
Re: 256K 800XL updates (LONG)
Author: Vicious Oyster
Date: Thu, 21 Nov 1985 15:35
Date: Thu, 21 Nov 1985 15:35
143 lines
5879 bytes
5879 bytes
Regarding queries about and problems with the BYTE DOS for 256K, here's
what's in the MAAUG October newsletter:
[Start newsletter excerpt]
...the new Atari 130XE comes with DOS 2.5 which already supports a RAM-disk
as D8:. DOS 2.5 will work with our memory upgrade without modification;
however, since the 130XE only comes with 128K, DOS 2.5 has no way of knowing
about the extra memory that our modification provides.
The following is a description of how to modify DOS 2.5 in order to provide D8:
with a full 720 sectors (instead of the 512 sectors provided); and to add D7:
with 720 sectors. This procedure is included for the benefit of other users
groups... MAAUG members need not read this section since they can get the
patched DOS at the MAUUG meeting. You will need an ASSEMBLER cartridge to
install this patch:
1) Insert your assembler cartridge.
Put DOS 2.5 in drive 1.
Cold start your machine.
2) When the "EDIT" prompt appears, get into debug mode by typing: "BUG".
3) When the "DEBUG" prompt appears, get into the mini-assembler by typing "A".
4) Type the following lines ending each by pressing the RETURN key. The mini-
assembler will respond to each line with one or more lines of assembled object
code. Notice that you MUST type a space after each '<' sign (which denotes the
end of the address and the start of the instruction).
B86< LDX #0
105C< LDA #$64
12DE< LDY $21
< CPY #8
< BCC *+4
< ADC #5
< TAY
< LDA $185B,Y
< JMP $1846
148D< CMP #6
14C4< LDA #$70
< JSR $1846
183A< .BYTE "MEM.SAV ERR",$9B
1846< STA $44
< LDA $D301
< AND #$83
< ORA $44
< STA $D301
< RTS
185B< .BYTE $20,$24,$28,$2C
< .BYTE $40,$44,$48,$4C
< .BYTE $60,$64,$68,$6C
77F< CPX #7
< BCC $78A
B88< CMP #7
< BCS $BD3
105E< CPY #7
< BCS $1076
70A< .BYTE $C3
5) Press the RETURN key to exit the mini-assembler mode.
6) Type "X" followed by RETURN to return to the EDIT mode.
7) Type "DOS" to access the DOS menu.
8) Write the DOS files out to drive 1.
9) Turn off the machine and cold start DOS... when you do a directory of
D8: you should now have 620 sectors free (instead of 499). Use the "I"
command to format D7:. When you do a directory of D7: you should have
707 sectors free. (D8: is automatically formatted by the "RAMDISK.COM"
program if present on the disk when DOS is loaded.)
10) Pat yourself on the back... you now have two full-sized RAM-disks.
Note: this patch will only drive 256K. A single patch to drive either the
256K or 512K will be forthcoming as soon as we have a working 512K memory
upgrade installed.
==========
QUIRKS
==========
Don't erase DOS.DUP or MEM.SAV from D8:
Don't write DOS files to D5: thru D7:
Don't try to copy MEM.SAV
Don't count on the Duplicate disk function always working between RAM-disks
Don't turn off your machine and expect data written only to a RAM-disk to
still be there when you turn it back on.
Don't run any 130XE programs that use extra memory without first saving any
data that you need to keep from your RAM-disks to a real disk. (For example
a sector copier.)
Don't expect all the 130XE software to work since there is one function of
that machine which is not duplicated by this memory upgrade...namely, the
extra memory video chip enable line (PB5) is being used by us as an address
line.
Two DOS error messages were shortened/disfigured in order to make room for
these patches. They are "Type Y to still run DOS" and "ERROR-saving user
memory on disk". The latter now reads: "MEM.SAV ERR" and the former now
is illegible (Asi es la vida).
If the 512K version of the upgrade is installed, then the self-test feature
of the 800XL must be sacrificed.
Disclaimer: The information contained in the articles in the MAUUG Newsletter
are intended for general distribution as the property of the Madison Area ATARI
User's Group. The information is free and may be used in any way which is
generally assumed to be appropriate by any individual or group of individuals
as long as no financial compensation is incurred. Neither the articles nor the
information contained in them is to be sold or distributed in exchange for
money.
ATARI is a copyrighted name and all of its products are protected by
copyright.
[End newsletter excerpt]
Further caveats:
Don't change your original copy of DOS!! Change a copy.
There's a small chance that I confused a "B" with an "8" in the above
instructions, due to the fact that the newsletter is done using a dot-matrix
printer with less than perfect resolution.
Further news:
The MAAUG now has a couple of 512K 800XL's.
They are still having a few problems with the 1200XL upgrade, but they just
started working on it last week, so I'm keeping my fingers crossed.
I'm still trying to keep names of anybody who wants further info.
Personal disclaimer: I'm neither a hardware hacker, an OS wizard, nor an
official representative of the MAAUG. Also, my employer has no connection
with the MAAUG, and doesn't know what I do during my coffee breaks.
- Joel Plutchak
{allegra,ihnp4,seismo}!uwvax!uwmacc!oyster
Re: 256K 800XL Conversion updates
Author: Bill Dippert
Date: Sat, 23 Nov 1985 18:16
Date: Sat, 23 Nov 1985 18:16
91 lines
4111 bytes
4111 bytes
> > Judging from the responses I've seen on the Net, a number of us > are having similiar problems/interests. Since a 256KXL is of > particular interest and has exciting possibilities, I suggest that > those individuals interested form a Users Group of our own. I will > be willing to act as a clearinghouse for information. It is to our > mutual interests to share whatever associated information/software > that we can obtain. My address is > > Bob Burch > 6609 Charles Dr. > Mt. Airy, MD 21771 > > >Further news: they haven't yet made a 256K 1200XL, but they've opened one > >up and said it can be done........(etc.) > > > >yes the mod works... be careful when assembling the code > > Please enlighten us!!! Given recent Net articles and what has been > written above, what is it that you did that allows the mod to work? > Are we talking the same "mod"? Did you do anything special? Was the > upgrade completely successful for you? We would appreciate your > insight. > > >We have been shipping the 256KXL for a couple of weeks and no problems > >have been noted. It makes the 800XL look exactly like a 130XE except that > >bits 5 and 6 of $D301 have been redefined to address twice as much memory. > > Who are "we"? Can you please explain the theory of the bit-usage of > PORTB ($D301) and the significance of its use. Also, how can a given > bank be directed to the upper or lower 32K when swapped in? > > Whatever info. I get I'll try to pass along. > > In article <DYOUNG@USC-ISID.ARPA (C. David Young) writes: > > >...I just finished souping up the ramdisk handlers in OMNIVIEW XL/XE > >to treat the extra RAM in our 256K upgrade for the 800XL.... > > Also, in a following article C David Young writes: > > >That 256K RAM upgrade in BYTE was a real dog. We have got a 256K upgrade > >(256KXL) that will make your 1200 130 compatible. You can buy it without > >RAM for $50 or with for $100. The reason that the BYTE upgrade is such a > >dog is that it ends up including the stack in the bank switch area. > > Hurray for Dave!!!!! Can we purchase just the software you've created for > this upgrade? If so, where can we order? Or, can you pass along the > patches necessary to kick-start the BYTE "dog" that us suckers have > fallen for. It is wonderful to know that we are not without > alternatives in this situation. > > >Please copy me in all answers, Thanks > > Consider yourselves copied. We would appreciate any experiences you've > had in this matter, thank you. > > Anyway, this has been long enough. I'm preparing a letter to > Claus Buchholz author of "The Quarter-Meg Atari 800XL". Any replies > I'll post on the net. I would appreciate any other contacts/replies. > > Bob Burch > 6609 Charles Dr. > Mt. Airy, MD 21771 > (301) 831-7690 evenings > > :Oh! He had high hopes....just remember that dam. > :OOPS! There goes another Quarter-Meg RAM!!!! > -wocka-wocka-wocka- I too am interested in all of the above -- I have deleted over 50% in the interests of brevity. I am interested in converting a 1200XL, 800XL and a 130XE all to 256K. That's correct, since it only has a 90 day warrenty which is almost up, why not upgrade the 130XE to 256K also!!! Please add me to any mailing list. I am: Bill Dippert c/o Tektronix, Inc. D/S C1/775 P.O. Box 3500 Vancouver, WA 98668-3500 or by eMail: tektronix!tekigm2!wrd Thanks, --Bill--
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