#'030 Accelerators
11 messages in this thread
I've never been able to track it down, but I get more crashes when I'm
running these GVP 030 boards. I had a 33 Mhz for a while, and it would
bring more crashes, and now I'm running a 28 Mhz one. Still crashes more
than I'd like and certainly more than I get without it. Can anyone point
at any known incompatibilities or flakey bits of software I might be
running? In my startup, let's see, there's FastMemFirst, VD0:,
SetPatch1.32, SETCPU FASTROM NOBURST NOCACHE, addbuffers, setclock load,
bindnames, automount, CED Pro, rexxmast, nazcron, fastfonts, runback
faccII, runback virusX, ConMan, and the Manx 'set' command.
You don't happen to also have the Commodore 2 meg ram card in that
machine, do you? If so, that is probably the culprit. If you don't – well,
it must be something else.
John,
I have had to remove the 3001 board and reseat it on occasion. I
think the contacts do get somewhat corroded over time. This seems to
prevent any crashes. The only time I have had crashes was do to games not
compatible with 020/030 processors.
Just make sure with SETPATCH that you are using R option. This and
BINDDRIVERS should be run before using SETCPU. Other than that I'm not
sure what your problem could be. Norm
I think you've hit the nail on the head. Tracking it down myself, by
commenting out lines in the s-s, I found that SetPatch was doing it.
What's the 'R' option do? I'm sure it would take days to find the docs
around here… I don't run BindDrivers. Meanwhile, I run without SetPatch.
It's gotten much more stable since I removed it.
John,
The 'r' switch to SetPatch allows recoverable ram drives to recover
if you have more than 512k of CHIP RAM.dd
Don
John,
Commodore claimed that the 'R' option was for RAD recoverable ram
drive device. It really patches a bunch of bugs in the opperating system
of the Amiga. It should be run before SETCPU in the startup sequence file.
It is a good idea to make it the first line in the startup sequence. If
you don't have the 1meg Agnus chip it may not be needed. Norm
Great. I do have the 1 meg Agnus, and I threw RAD: as far as I could, once
I read what it was.
Norm,
SetPatch itself fixes a lot of bugs, by adding the 'r' option, an
additional fix is added that prevents the startup code from nuk'ing RAM
(thus invalidating RAD:) if you have more than 512k of CHIP.
In other words, the 'r' option supposedly only adds one more patch
to those already done by SetPatch.
Don
Don, for users of 1.3.2, is Setpatch 1.34 the latest, and is there any
reason to use SETPATCH r if you don't use RAD but do use more then 512k of
chip ram (in our case 2 meg)?
Thanks, and happy holiday!
Ron
Ron,
Yes, as far as I know, SetPatch 1.34 is the latest (it's what I'm
using). And no, there is no reason for the 'r' switch if you're not using
a recoverable ram drive. At least I've not heard of a problem, nor do I
have a problem not using the 'r' switch.
Don