#Amiga help
24 messages in this thread
I'm having a strange problem with my Amiga. First, let me describe my
system:
I'm using an A2000, three drives (two internal, one external–all 3.5"
disks), flicker fixer, Sony multisync, modem (serial), printer (parallel),
2 Megs extra RAM, and the 1 Meg Fatter Agnus Chip.
If I use a file system such as MessyDOS, my computer freezes up if I
attempt any writing to the disk. However, this only occurs if I have
installed MessyDOS on my internal drives. My external drive runs MSH fine.
I also have had some disk problems using an Atari emulator. (Again, using
the internal drives.)
I've tried cleaning the drives, but the problem still persists. I believe
that there may be something wrong with the chip that handles the internal
drives. Could anyone direct me to a software packag (preferably PD), which
I could use to test my Amiga's chips? Or would anyone care to suggest
what the problem could be?
Another quirk that has come up is with VirusX. When I run it, it tells me
the ColdCapture Vector is not set to zero. Would my flicker fixer be using
this vector? What exactly does this vector do?
Thanks, in advance, for the replies.
Chris,
I don't know of any program that tests the chips, but I would
suggest that one of the CIA chips (8520's) in your Amiga is probably a bit
flakey.
They are the source of a lot of strange goings on, and they are
very static sensitive…so they can "break" fairly easily.
No idea on the VirusX thing.
Don
Thanks for the help. Now I have a starting point. How much would you
figure a CIA chip will cost? I guess I can steal one from my Dad's 500,
so that I can test your theory. 🙂
Chris,
CIA chips cost about $20 each. Your Amiga has 2 of them in it.
The best way to test them…is to swap them. If your original problem goes
away (but some oth399
er problem will probably crop up), and then you swap them
back…the original problem returns…you've found the cause.
Don
I appreciate the help…I'm going to open my 2000 up tonight and try it.
Don't worry, it's too old to void the warranty (I've had it for about 6
months, and the guy before me had it for about a year and a half).
Could the CIA chips be affecting my space bar? Sometimes when I tap it, I
get two spaces instead of one. Or does my space bar need cleaning?
Chris,
If it's just on one key…I'd suspect the key itself. But yes, the
keyboard is one of those things that also go thru the CIA chips.
Don
Chris,
BTW…as I mentioned before…those CIA chips are VERY static
sensitive. Make sure you are properly grounded before you touch them.
Don
If you have the SetPatch command enabled in you startup-sequence, VirusX
will deliver the ColdCapture message.
But I used the exact same startup-sequence on my Dad's Amiga 500, and I
did not receive that message. (To tell you the truth, I used my original
copy of Workbench 1.3-with the write-protect on!-to test).
I forgot to mention that I have V1.2 ROMs in the A2000. Could 1.2 be
giving me that message while 1.3 doesn't?
Chris, could be that when Setpatch -r is used on your Dad's 500 it checks
to see if you have less than 1meg of Chip ram, as in the 500, and if so
doesn't install the patch and modify the Cold Capture vector. But on a 3000
it sees the 1 or 2 meg Chip ram and installs the patch. If you read the
VirusX docs you will find there is an option to disable the Cold Capture
error message, something like VirusX -r . By the way, I think the correct
notation for the Setpatch is Setpatch r and not Setpatch -r as I typed
above.
That is quite possible…I do not have a fatter agnus on the A500, but my
A2000 has one. Is there any way that I can run VirusX from WB and stop the
message from appearing?
There may be a way to run VirusX from the WB specifying the -r option, but
I couldn't be sure unless I sit down and read the docs again. Possibly
setting a tool option in the .info file. The easiest way I found to use
VirusX is start it up from the startup-sequence in your s: subdirectory.
That way it is available when you boot up your computer and is always
checking for those nasty Viruses. If you need some help on editing your
startup-sequence, let me know and I'll lead you through it.
John (in beautiful downtown Walla Walla) – via Whap!
I usually don't receive disks from other people's Amigas, so I can't be
bothered to run it all the time. I usually give everything a check once
in a while to see if any nasty critters have clung onto my disks somehow.
I shouldn't have any problem with editing the Startup-Sequence if I do add
it on (actually, I may if I get a hard drive in the near future).
Sorry, can't help anymore. I was just citing the most common cause for
the ColdCapture thang.
No problem…Some other friendly people have stepped in to help. Thanks
for the help you have given me.
VirusX is correctly reporting on the ColdCapture vector. This is a result
of your using the 'R' option with SetPatch, which you should be doing as
far as I know. You can disable the message from VirusX, I believe.
Like I mentioned to someone else, I used the sem startup-sequence on my
Amiga and my Dad's A500, and used the same version of VirusX, but the A500
did not report anything about the ColdCapture Vector. Is there a reason
for that?
Chris,
If your dad's A500 doesn't have the 1 meg AGNUS chip activated with a 1.3
Kickstart ROM, I don't believe that the 'r' option will have any effect.
That could be the reason.
David
David,
1.3 is not necessary to "activate" the 1 Meg AGNUS.
Don
Don,
No, but it is necessary to autoboot from RAD: with a 1 meg AGNUS that has
been activated. The reason that I mentioned the word "activate" is that
it's my understanding that C= has shipped A500's with the new part
installed but without the modifications to activate the extra chip ram. In
those cases, Setpatch R is not required, even though there is a 1 meg AGNUS
chip in the machine. (Sorry if my answer was confusing.)
David
– via Whap!
Chris,
I had one more thought. Try taking the >NIL: redirection out of the
Setpatch command in your startup-sequence. Setpatch will then print some
message lines about what it's doing. Maybe that will help us figure it out.
David
I'll give it a try….At the moment, I'm more concerned with some disk
access problems I've got. When I have some spare time, I'll play around
with VirusX. At least I'm pretty sure that the ColdCapture thing isn't an
unknown virus that my computer has picked up. Thanks, again, for all the
help!
David,
According to the docs the ColdCapture screen does not indicate a virus.
If it was a virus VirusX would tell you. I can neither confirm nor deny
this but it is what was in the docs. What version of VirusX are you using?
I think 4.01 is the version that first allowed the elimination of the
coldcapture message.
Bruce H.
-Via Whap!
I think I'm using version 4.0 of VirusX. I can't quite remember. I should
look for the latest version.