A4000T not working

  • Thread starter Thread starter JHanna
  • Start date Start date
  • Replies Replies 119
  • Views Views 4139
Hold up. Was working with 3.1 ROMs. Put the 3.2 ROMs in and now back to square one.

Curious.
I have observed a strange behavior in the ROMs 3.2.2 at startup everything appears to be fine but after the first flash the computer stays there.

Sometimes if the floppy drive is not connected it could seem that there is some problem and it does not boot from the HD, however connecting the floppy drive works correctly, I have burned several ROMs 3.2.2 and I have seen this on some A4000s and some 1200s without really knowing why it happens. Because then in the end all ROMs worked fine :mad:
 
I have observed a strange behavior in the ROMs 3.2.2 at startup everything appears to be fine but after the first flash the computer stays there.

Sometimes if the floppy drive is not connected it could seem that there is some problem and it does not boot from the HD, however connecting the floppy drive works correctly, I have burned several ROMs 3.2.2 and I have seen this on some A4000s and some 1200s without really knowing why it happens. Because then in the end all ROMs worked fine :mad:

That is very strange. I seem to remember 3.1 has a long delay while it waits for a hard drive to spin up. But the insert disk screen always pops up in the end.

Getting some new 3.2.2 ROMs tomorrow, so will report back then.
 
That is very strange. I seem to remember 3.1 has a long delay while it waits for a hard drive to spin up. But the insert disk screen always pops up in the end.

Getting some new 3.2.2 ROMs tomorrow, so will report back then.
Had issues with the BFG9060 on a A4KD setup. Either worked or didn’t work. Just make sure the BFG is seated correctly. If the 4000T has built in SCSI, then that’s also another issue with BFG9060’s. The BFG card also don’t use autoconfig. Another gotcha I’m afraid. I fixed my problem by getting rid of the BFG and bought a classic accelerator.
As others have pointed out. A4000D 3.2.2 ROMs differ to the A4000T 3.2.2 ROMs. Also make sure you have a good PSU.
 
I know this might sound silly ...

Kickstart ROMS in the right sockets / properly seated?

What would happen if the Hi/Lo ROMs were labelled the wrong way round?

I really don't want to keep installing and removing these things, but the only thing I can think of is they are labelled wrong.
 
You'd get a black screen most likely, as long as you don't plug them upside down they should be ok electrically. The notches on the chips should match the notches on the socket as im sure you know.
 
Had issues with the BFG9060 on a A4KD setup. Either worked or didn’t work. Just make sure the BFG is seated correctly. If the 4000T has built in SCSI, then that’s also another issue with BFG9060’s. The BFG card also don’t use autoconfig. Another gotcha I’m afraid. I fixed my problem by getting rid of the BFG and bought a classic accelerator.
As others have pointed out. A4000D 3.2.2 ROMs differ to the A4000T 3.2.2 ROMs. Also make sure you have a good PSU.

I haven't had any single issue with BFG9060 in my A4000T, using both original 3.1 ROMs and 3.2.2 ROMs (A4000T version ofc).
Booting from SCSI and / or CF-IDE works as expected, with 50 MHz and 100 MHz.
I am also using Z3 RAM expansion but no other Zorro cards.
 
You'd get a black screen most likely, as long as you don't plug them upside down they should be ok electrically. The notches on the chips should match the notches on the socket as im sure you know.
Yeah that's what im getting. Black screen. No early boot menu. But strangely sometimes the cap lock doesn't even light up. Or if it does, it goes out and won't light up again. Sometimes I get a grey screen then a reboot loop.

I might swap them over and see what happens.
 
Yeah that's the image I've been using as reference. There's nothing else online, anywhere.
 
It's possible he mislabelled the Roms but it's more likely they're either bad or he's put the regular A4000 and not A4000T version
 
Yeah that's the image I've been using as reference. There's nothing else online, anywhere.
You might have 4000D ROMs instead of 4000T ROMs. Or the ROMs themselves have not been programmed correctly or have become faulty.
Do you have a TL866 ROM programmer with the adapter for the ROMs? If you did, you could check them.
 
I thought the only difference was the workbench.library being excluded so they could fit the SCSI code in.
 
I thought the only difference was the workbench.library being excluded so they could fit the SCSI code in.
As of 3.1.4 ROMs. Both Workbench.library and icon.library was removed for space constraints. The A4000D has only IDE where as A4000T has SCSI. Therefore the code is different for both systems I believe. Therefore why each ROMs are made separately. For example A1200 even though AGA has its own separate ROMs. When using the Load Modules disk, these have there own Modules for each system.
You can however make 1MB ROMs and have the libraries and extras put onto the ROMs. Such as other device drivers found on the TF cards such as EIDE.device etc..
 
The A4000T has IDE and SCSI. With the 3.2.2 ROMs installed I can't even get to the early boot menu.

Hopefully have another set being shipped tomorrow. Just want this done.
 
Hopefully new roms sort out the issue.

Have you retried the 3.1 ROMs to confirm it works again with them?

How are your jumpers set on your BFG are you overclocking or just running at 50 MHz?

When trying the 3.2.2 roms have you tried with no zorros cards attached?

With 3.1 ROMs have you tried setting the system up on them first and checked it all runs as expected and is stable? The reason I ask this is my A4KT mobo I found was faulty and I only discovered this due to getting my hands on a spare mobo which worked flawlessly.

My original A4KT mobo would only work occasionally and with certain accelerators and got more unstable when adding zorro cards this mobo was professionally recapped which didn't sort the issue and then I had to send it to the Master @hese who discovered faults on the motherboard which he repaired. Hopefully this is not your issue
 
3.1 ROMs work fine.
BFG is running at 100MHz fine.

I've played parts roulette and have determined it's definitely a ROM issue.

This whole thing is such a pain in the arse.
 
Is there any way to test SCSI on an A4000T? Hard drive and CDRW aren't being picked up in HDToolbox and the Install3.2 floppy respectively. Currently using scsi.device and UNIT=2.

Everything should be working.

Urgh.
 
It's probably not scsi.device you're looking for
 
I think it's 2nd.scsi.device you'll need to update the tooltype in HD toolbox
 
Back
Top Bottom