Just wondering if anyone had a 1571 proggers ref guide and was
willing to part with info on the 1571 burst modes. Just wondering
if the 64 bus could be tricked into running a 1571 in burst mode.
-Maybe if only between two 1571's
IE: Fast hack'em dual 1541 copier that lets you power down the 64 and
just copies between the two drives! --> Should work for 1571's in chain!
Oh well, if anyone has info it's much appreciated!
Later:
-Joe C
1581's User's Manual has quite a nice appendix describing the burst
commands.
>Just wondering
>if the 64 bus could be tricked into running a 1571 in burst mode.
Yes. The most important burst command being the Burst Load routine
(see ftp.funet.fi:/pub/cbm/c64/diskutil/BurstLoader64.lzh). You need
to add two wires to your c64 though.
>-Joe C
-Pasi
--
"I need your clothes, your boots and your motorcycle."
-- Terminator in "Terminator 2 - the Judgement Day"
It looks like in Australia it's hard to get hold of 1581's!
I have NEVER seen one: HOWEVER! I just got the address of my local
CMD distrib. so things might change :)
Just BTW:
I got a CRAZY idea last night. I have had a simple static RAM disk (rs232)
idea for AGES on the drawing board with a driver which piggy-backed on the
BASIC roms. (Just switch it in/out) but last night I got the idea of using
the address/data bus to control the RAMdisk. MAYBE-
If you select one address pin of the eprom, you could use less eprom space
(yes, waste it!) and install a toggle which would also go into the RAM
data lines and when you brought the address line high it would check three
bytes, 1. data-direction/hi-hi 7bits for out, 2.lo byte 3.hi-byte
and send/rcv the fourth. Sounds possible?
why all this crap? So you can use a cart like ARiv or PowerCart or Trilogic
AND have a big RAM disk!
Ideas?
> I have built such an interface, but of course you need some additional
> software. I use this to read PC Disks on the 1571 with my C64.
Interface? All you need is 2 wires. Anything more is redundant. I only
added these 2 wires and nothing more and it works like a charm since
years.
> You can find a description in the german magazin 64er, issue 6/89 I think.
> (unfortunately the on/off switch in this shematics is wrong (never put +5V
Of course it's wrong, it's the 64'er magazine. :-)
Without reading the "Fehlerteufelchen" nothing works.
> to CA2 on the userport!), but I think you will figure it out (sorry, this
> bad shematics was my fault...))
There's no CA2 pin on the C64 Userport or CIA 6526, CA2 is a pin related
to the VIA 6522. Probably you meant PA2.
> Actually you just have to connect DATA on the serial Bus with the
> CIA SR pin on the Userport and CLK (or SRQIN???) to the shift register
> clock of the CIA.
Right.
> Then you have to switch the direction if the drivers.
> ThatÂs what I use CA2 (was it this line?) for.
What drivers and what direction? Drivers aren't necessary and so you
haven't switch the direction, it's all done with bit #6 of $dc0e.
> You can find Software ("bdos+" to read PC Disks on the C64 or the C128
> with a 1571) on the net: http://ix.urz.uni-heidelberg.de/~fs1 on the
> World Wide Web (WWW).
The 64'er magazine also published a disk speeder using this enhancement.
It should be in the big archive on funet.
MfG Andreas
Can you program it just like a 128 (for BURST protocoll)?
: There's no CA2 pin on the C64 Userport or CIA 6526, CA2 is a pin related
: to the VIA 6522. Probably you meant PA2.
: > Actually you just have to connect DATA on the serial Bus with the
: > CIA SR pin on the Userport and CLK (or SRQIN???) to the shift register
: > clock of the CIA.
: Right.
What about a 128 in 64 mode? Is there any way to do burst in 64 mode
on a 128 without additional hardware?
> : Interface? All you need is 2 wires. Anything more is redundant. I only
> : added these 2 wires and nothing more and it works like a charm since
> : years.
>
> Can you program it just like a 128 (for BURST protocoll)?
Yes, it's absolutely the same, except there is no need to switch the
direction in the MMU too, bit#6 of $dc0e is enough.
> What about a 128 in 64 mode? Is there any way to do burst in 64 mode
> on a 128 without additional hardware?
No way!
The CIA's shift register isn't directly connected to the serial port. Each
of both lines is split up into both directions. The transmitting lines are
connected through a 7407 amplifier and the receiving lines take use of a
74LS14 schmitt-trigger. Also there are 4 gates (74LS03) switching the
lines separately on and off. The transmitting lines are only controlled by
-FSDIR, so we can send in C64 mode, but unfortunately the receiving lines
are controlled by -FSDIR and 128/64. 128/64 is a line generated by the MMU
and there is no way to switch the C128 into 100% C64 mode without changing
this line to C64 status.
So if you want to take advantage of burst routines on your C128 in C64
mode, you have to do a hardware patch - the same that works on the C64.
CNT1 on the userport has to be connected to SRQIN (pin 1) on the serial
port and SP1 has to be connected to DATA (pin 5).
MfG Andreas
So would the code in, say, the 1581 drive manual work (if I leave out
the MMU access) on one of these modified 64s?
: So if you want to take advantage of burst routines on your C128 in C64
: mode, you have to do a hardware patch - the same that works on the C64.
: CNT1 on the userport has to be connected to SRQIN (pin 1) on the serial
: port and SP1 has to be connected to DATA (pin 5).
Thanx very much for all the info!
: So if you want to take advantage of burst routines on your C128 in C64
: mode, you have to do a hardware patch - the same that works on the C64.
: CNT1 on the userport has to be connected to SRQIN (pin 1) on the serial
: port and SP1 has to be connected to DATA (pin 5).
Actually, I found I had to use CIA2 on a 128, or it caused a number of problems
with 128 mode. (Namely, no serial access at all with the connection made.
Even installing a switch on the lines caused errors in burst saves.)
Now if only there were a way to use the fast serial in commercial games,
but most insist on changing the ILOAD vector to their own routine. And my
efforts with a number of games (lately, SSI's AD&D series.. where slow
disk access makes the games almost painful..) have had no results. Even going
so far as loading their fastload code, but NOPing out the routine that changed
ILOAD failed.
: MfG Andreas
--
And still the bridge collapsed the space between, Gyrfalcon
replaced the gap inside with silent screams, Jason Gorst
raked across the coals--what are you telling me? fal...@fullfeed.com
before you disappear, let me see. --Murder, Inc. "Mania"
I think you should better go the way to patch the kernel to achieve
fastload. This will work as long as the original routines are being used
(what I assume, when the disk access is slow).
I patched my kernel to use an IEEE488 interface as well as the serial
bus, depending on the device number this way and it works quite well for
nearly everything without an own fastloader.
Andre
--
Andre Fachat mail me! fac...@galileo.rhein-neckar.de
For some it is MS-Windows, for others it's the longest batch file on earth...
: Now if only there were a way to use the fast serial in commercial games,
: but most insist on changing the ILOAD vector to their own routine. And my
: efforts with a number of games (lately, SSI's AD&D series.. where slow
: disk access makes the games almost painful..) have had no results.
: Even going so far as loading their fastload code, but NOPing out the
: routine that changed ILOAD failed.
What AD&D games did you try to "fast-load"? I have successfully installed
a number of RPG's by Strategic Simulations on my RAMLink! They include
Champions/Death Knights of Krynn, Countdown to Doomsday, Gateway to the
Savage Frontier, and Secret of the Silver Blades.
We could be crossing wires here, but I just thought I would add my two
cents' worth and say that operating those four- and six-disk SSI games
from a single RAMLink partition is a pure joy. (Just SWAP the RL to
Device 8, and select "yes" when you are asked to disable the built-in
fastloader.)
Nhat-Viet Phi, alias "Toto"
nhat...@nucleus.com
Calgary, Alberta, Canada