»

[KThunder]

helooo did you try plugging in a scsi device
maybe?

[motrucker]

If my memory still works at all, I think the A3000 is unique in that it keeps a few bytes of critical info in RAM somewhere - that can be erased when the battery is replaced. This may cause an apparent failure.
I'll have to dig this data - 'till than, does anyone remember what I am refering to?

[KThunder]

yes motrucker it does have memory called nvram that holds config info it is also discussed on the big book of amiga hardware page right under my above quote. www.amiga-hardware.com
click on amiga models and clones find a3000 scroll about halfway down to just above a pic of a mobo

[KThunder]

btw my 3000 wont boot if there isn't something on the scsi bus :-o man that is scary

[melott]

KThunder wrote:
helooo did you try plugging in a scsi device
maybe?

OK.. I tried with a SCSI HD connected.. same result..

The system isn't getting that far...
Although I've nevew heard that an A3000 won't boot without
a SCSI device connect.
The battery part of this discussion is not correct.
I have been running my other A3000 for about 3 years now
without a battery. The bytes refered to hold the SCSI
prefs and they go to default if the battery isn't installed.

The problem is right after the power is turned on, whatever
the next step is in the power-up sequence isn't happening.

This machine ran before .. it should still run.

[motrucker]

melott wrote:

The battery part of this discussion is not correct.
I have been running my other A3000 for about 3 years now
without a battery. The bytes refered to hold the SCSI
prefs and they go to default if the battery isn't installed.

The problem is right after the power is turned on, whatever
the next step is in the power-up sequence isn't happening.

This machine ran before .. it should still run.


Sorry. My memory isn't what it was, I guess. It was a thought.

[dnelsonfl]

Going back to the ROMs for a moment, some motherboard revisions might have the silkscreen printing for ROM0 and ROM1 reversed. Also while you're in there, try pushing down on all the socketed chips and ram. Double-check the floppy and SCSI cable orientations, too. It doesn't hurt to look again. Does the floppy start clicking when you turn it on? Do any of the HD lights stay on? I tried looking briefly on the 'net for a good site that would list trouble-shooting tips for the 3000. Didn't find one. Although one possible cause of the problem booting was a defective SCSI chip. That fella's A3000 was stuck polling the SCSI interface because the SCSI chip had gone bad. I would have thought the A3000 would have eventually timed out and tried the floppy.

-Edit- Here's some info on the motherboard/daughterboard revisions: Link

-David

[T3000]

any one have any concrete information on the problem at hand concerning these stubborn machines? (first couple of posts on this thread) Looks like a lot of hit and miss sugestions. Currently don't have the time to tinker or spend money on chip replacemnt with my a3000Tower. Any repair guys out there have a better clue? I really miss my a3000Tower.

[melott]

T3000 wrote:
any one have any concrete information on the problem at hand concerning these stubborn machines? (first couple of posts on this thread) Looks like a lot of hit and miss sugestions. Currently don't have the time to tinker or spend money on chip replacemnt with my a3000Tower. Any repair guys out there have a better clue? I really miss my a3000Tower.

I did get this A3000 running :-D
I'm a little embarressed to say that I had the roms
switched.. although the rom tower IS marked wrong.
I had to open my other A3k to check all the setting
and found the roms switched. I installed the roms
correctly and it fired right up.
I don't know if that helps your problem though :-(