Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Prmetime on December 22, 2003, 07:14:58 PM
-
Please Help!!!!
:-?:-?
I have just upgraded both of my A3000s with new batteries and the int2 mod. One of the machines boots right up. The other had problems acknowledging the HD. Sometimes it does fine, other times it has constant software errors and will not boot. However if I put a OS3.1 in the floppy drive, it will boot but does not say there is a HD there. Does this sound like a SCSI controller or CIA chip problem? Could it be anything else? It is frustrating beyond belief and ANY help would be appreciated.
P.S. I have been having goofy things happening with this machine for a long time but I didn't suspect anything until recently. Now I guess I have my suspicions confirmed. Both HDs I'm testing in this machine worked fine on the other A3000 so it isn't the Hard Drives.
-
What I've done when I had similiar problems was pull chips from one A3000 and put 'em in the other one at a time to find the culprit. Start with the SCSI chip and then do the rest.
-
It could be that you need the program SetBatt-1.2 from aminet as amiga 3000,s store imformation for the scusi drives which is lost if the battery goes flat or is removed. :-)
I have not used this myself the a3000 i have is working fine.
-
why not try an alternative - IDE? A buddha card can boot from the hd, and is usually more reliable (and cheaper drives) than SCSI on A3000D's in my experience....
the speed difference between IDE and SCSI, unless you were using a Toaster/Flyer where you had to have absolutely the fastest drives possible, shouldn't be significant for daily usage...
kevin orme
amiga university
www.amigau.com
-
@amigau:
One very nifty thing about using the builtin A3000 scsi-controller is that it does DMA-transfers, so the cpu is neglectible loaded when doing transfers to/from the harddrive.
/Patrik
-
A3000 SCSI is really nice. It may require some tweaking in order to get it to work (SetBatt utility from Aminet usually does the job), but once you set it, it works great.
-
MagicM,
I hadn't really though about that but I REALLY didn't want to have to do something like that. I guess I shall have to though. Any other thoughts before I start pulling chips?
-
:-) I don't know what happened but I don't really care. I was playing with the idea of replacing chips one by one with the machine that does work. I took the ROM tower off and decided not to play with it. After resetting the ROM tower the computer started recognizing the Hard Drive. OS3.1 is running solid as a rock. I don't know why that would make a difference but my A3000 is running again and that is all that really matters. :-D
-
I have not used this myself the a3000 i have is working fine.
You should. There are some settings there that can get more speed out of your hd's transfers.
-
try what the others have said first since its easier... because I know its a pain in the butt to take a A3000 apart and put back together..lol.
-
Removing and reseating all socketed ICs is something you should definately do anyway, as those sockets have a bad habit of going intermittent over time.
It's probably nothing in the SCSI controller's settings (stored in the RTC which is battery backed up) as you said it works sometimes. Software does not really go intermittent :-P
You should use "SetBatt A" to clear the amnesia bit in the RTC memory anyway.
Pay attention to SCSI termination, this can cause transfer errors if not done correctly. Motherboard termination is enabled by fitting 3 resistor networks into provided sockets. Drive termination is usually a jumper or fitting resistor networks.
Also replace the 50 way SCSI ribbon cable. Those IDC connectors go intermittent when you least expect it. :-(