amiga 3000 won't boot from scsi

I recently resurrected my A3000 from storage. It initially would not boot the hard disk (100 meg original quantum drive) but would boot from floppy.

Then one day voila it started to boot from the hard disk. I was so happy. My external DAT drive also worked although I only had it connected once.

So there I was happy for a few days while I could use my A3000.

Then a few days ago, it went back to not booting. For the life of me I cannot get it to boot again.

When I hold down the mouse buttons, it does not see the hard disk as a boot device. It sees nothing.

I've tried different hard disks etc; it doesn't see them.

I have kickstart 3.1 roms, 8 megs fast, 2 megs chip.

I looked the board over and did see that the oscillator in u111 is kinda loose, but does that have anything to do with the SCSI controller? I swapped the CIA chips around but nothing changed. My battery on the board was changed to a modern lithium 3V one with diode to prevent charging. There is no corrosion. The machine holds the time just fine when off for a few days.

What could cause this flaky situation with my SCSI controller?

J

[alexh]

Broken SCSI cable?

Batmem settings?

Over clocking?

Thanks Alexh.

I have tried a new scsi cable and my machine is not overclocked.

What is batmem? I googled it and it came up as both 'battery memory' and a program. Please elaborate.

[alexh]

Several SCSI settings are stored in battery backed up memory. Remove or replace the battery and it looses it's settings.

The default settings should work but might be worth looking at.

How can I modify the default settings?

[alexh]

You will need to get one of the several different battmem programs onto a bootable floppy disk or use a serial cable and AmigaExplorer

Google Aminet and Battmem.

In the meantime have you tried a different SCSI ID on your HDD?

[LTAC]

Does your KS3.1 ROMs were recently installed?

LTAC: I recently did change to kickstart 3.1 roms. Why is that significant? It was flaky under the 2.0 roms I had as well.

Alexh: I will try another SCSI id. Thanks for the tip.

[Unknown_K]

Could also be termination issues with the drive. Plug in a terminator (or an external CDROM drive with terminator) and see if the issue goes away.

Could be you only had it working with the external DAT because of termination.

[LTAC]

Originally Posted by curiousottman

LTAC: I recently did change to kickstart 3.1 roms. Why is that significant? It was flaky under the 2.0 roms I had as well.

Alexh: I will try another SCSI id. Thanks for the tip.

My experience: some years ago I've bought a KS3.1 ROM (A3000) on Evilbay and I have the most difficulty to boot on SCSI HDD! I never had this problem with the original ROM 3.1 that I bought some years ago (over 20 years).
I suppose that the latest KS3.1 that I'm using is a bad (illegal?) copy!

I bought my roms from amigakit.com and they look legit.

I really need to find a batmem program.

J

[tomse]

are the KS3.1 for the A3000 or are they for A1200/A4000D/A4000T ?

since each machine is alittle different from the other there are some minor differences.. i.e. the A1200 has pcmcia/ide, A3000/A4000T has scsi controller etc.

I take it if you chose the correct ones on amikits shop, you'd have the A3000 roms.. but worth looking into.

I can't say if there are better tools to see what's in kickstart, but I'd use Remus or rather ROMsplit for this: http://www.doobreynet.co.uk/beta/index.html

you should see the scsi.device (A3000)

I have the correct a3000 roms from amikits.

J