Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: zimgr5 on March 27, 2009, 05:10:03 PM
-
Hi,
My problem is I can't install WB 3.1 on my A3000T
It has KS 3.1 bought from vesalia and 16MB FAST ram.
When I had WarpEngine inside A3000T, WB 3.1 and AmigaOS 3.5 worked well.
Now WarpEngine is gone and I don't have it.
Since I removed the WarpEngine I'm getting 8000 0003 guru's while booting from an original 3.1 Workbench disk with kickstart 3.1. I don't know what's wrong, it always worked well with the WarpEngine
Maybe I set some jumpers wrong but I don't think so?
I find it a bit strange that everything worked fine with my Warpengine and without I'm getting these errors :-o
Booting with the 2.04 kickstart and workbench 2.04 supplied with the A3000 works fine though.
I've been testing the A3000 today with kick 3.1. I can only install Workbench from the original WB 2.04 set supplied with the A3000.
And even connection of SCSi HDD with preinstalled WB 3.1 ends with this error.
Any help will be appreciated guys
-
Does WB 3.1 boot with Kick 2.04 ?
Is this WB 3.1 original (write protected and never changed) or did you manipulate it somehow ? Perhaps copied WarpEngine software to it ?
-
What do you have instead of the WarpEngine, the onboard 030 ? Maybe you should change the jumper for the external clock if that's the case.
-
Yep, now I have only onboard 030
WB 3.1 is a copy because my original is unreadable
-
@zimgr5
You might wanna read this thread, the problem your having is with the kikstart rom.
Have you got a copy OS3.9? on the cd is the full release (all versions) of OS3.1.
http://www.amiga.org/forums/showthread.php?t=10847
-
Thanks for the info. Must read it.
I have only original OS 3.5 but don't have any 3.9 versions.
Since I can't install just WB 3.1 I have no use of my SCSi PlexWriter as it's not recognised :(
-
Erol,
I read that thread and partially understand what was said there and have strange feeling that "it is illegal to update roms in A3000T as only developers could make a use of it" ??
Could anyone tell me what should I do to solve this problem in step-by-step plan ?
I thought that setting up an OS won't be a problem with A3000T, but , sadly , it seems to be a real pain :(
I haven't got this problems neither with my earlier A2000 or A3000D ...
-
Make sure you have the correct roms The 3000T and 3000D use different roms.
-
@don27dog:
The A3000T and A3000D use exactly the same roms.
The original poster should verify that the WB3.1 disks do not have anything on them that would be specific to his "previous setup", in terms of cpu libraries and such. If he could try a set of new WB3.1 installation disks, that would be a good initial troubleshooting step.
-
@zingr5
There are a couple of motherboard jumpers that were changed when the WarpEngine (WE) was installed. When you remove the WE you have to put these jumpers back the way they were before. Check the WE and A3000 manuals available on the Amiga Hardware Database (http://amiga.resource.cx/).
-
sandpiper wrote:
@zingr5
There are a couple of motherboard jumpers that were changed when the WarpEngine (WE) was installed. When you remove the WE you have to put these jumpers back the way they were before. Check the WE and A3000 manuals available on the Amiga Hardware Database (http://amiga.resource.cx/).
Thank you. I checked motherboard and next to those jumpers there is 74F08 socketed in U103. Does it change anything ?
-
@zingr5
Not sure. I'm not a hardware expert so I don't know the significance of that.
From the WE manual, Jumper J100 must have pins 3-4 connected; from the A3000 jumper table on BBoAH, J100 should have pins 1-2 jumpered.
Similarly, J102 has pins 1-2 jumpered for the WE, whereas the A3000 manual requires pins 2-3 jumpered.
Note: I am assuming the A3000 jumper settings are the same as the A3000T. I DON'T KNOW if this is the case. Maybe someone can confirm this.
I went through this a couple of weeks ago when I temporarily removed the WE from my A3000D so it is still fresh in my mind. You should confirm the above settings yourself in the WE manual & BBoAH in case I have made some typos.
-
I found this thread http://groups.google.com/group/comp.sys.amiga.hardware/browse_thread/thread/e566c75b4b465951?hl=en
and set jumpers for A3000T with 74F08 configuration.
Doesn't work. :-(
Then tried all 3 other configurations.
None of it is OK , without HDD or floppy A3000T boots with KS 3.,1 but booting from WB 3.1 Install floppy or preinstalled HDD with WB 3.1 results in 8000 0003 error :-(
If anyone could confirm that below settins are correct, it would be great
(http://i43.tinypic.com/2j3i9lj.jpg)
-
@zimgr5:
If you can see the Kickstart 3.1 insert floppy screen, then your jumper config is ok. At this point try and insert a floppy disk of let's say a game or some known to work (a3000 compatible) auto-booting piece of software and that way you will immediately prove or disprove proper functionality of your Amiga, should that game/software load and work ok. A set of fresh WB3.1 installation disks would be ideal.
Have you also tried booting from your WB3.1 Workbench disk?
Have you tried booting from the Workbench disk or the install disk with your hard drive disconnected from the scsi chain?
How much fast ram and how much chip ram does your A3000 have?
Have you tried removing all the fast memory and booting only with chip?
-
Thank for your response!
x56h34 wrote:
If you can see the Kickstart 3.1 insert floppy screen, then your jumper config is ok. At this point try and insert a floppy disk of let's say a game or some known to work (a3000 compatible) auto-booting piece of software and that way you will immediately prove or disprove proper functionality of your Amiga, should that game/software load and work ok.
Floppy games run without problem.
A set of fresh WB3.1 installation disks would be ideal.
I'm in progress of buying original set of OS 3.1, coz today I got a suggestion that my OS 3.1 copy may contain a virus (?). It's kinda unbelievable for me that OS can be virused, but ...who knows ?
Have you also tried booting from your WB3.1 Workbench disk?
Yes. It ends with the same error
SOFTWARE FAILURE
CODE : 8000 0003 0700DEBQ Press left mouse button to continue
Have you tried booting from the Workbench disk or the install disk with your hard drive disconnected from the scsi chain?
Yes of course.
Only SCSI with WB 2.04 from original floppies boots OK.
SCSI with WB 3.1 preinstalled on my another A2000 connected doesn't boot - it shows EXACTLY the same error as floppies with WB 3.1. Strange isn't it ?
How much fast ram and how much chip ram does your A3000 have?
8MB chip & 16MB RAM.
Have you tried removing all the fast memory and booting only with chip?
I wouldn't seek a problem here - memory is OK with WB 2.04 and when A3000T had WarpEngine earlier (previous owner) , everything was smooth. Now I have no WarpEngine and as I mentioned, I tried all combinations of jumpers - with no result. So I assume memory is OK.
-
SOFTWARE FAILURE CODE : 8000 0003 0700DEBQ Press left mouse button to continue
Perhaps your A3000's NVRAM is corrupted and it needs a reset? It is the only "cache-type" memory that will survive a complete shutdown. A3000 has it, unlike other Amigas.
You can use SetBatt to reset it or tweak its settings (search for SetBatt on Aminet). It is specifically used to keep settings for the on-board SCSI controller.
If an Amiga virus could hide somewhere, it would be there or on the floppy disk itself. Also, NVRAM in A3000 is known to get into a state of "amnesia" and needs a reset through SetBatt, so it could be another thing to check.
8MB chip & 16MB RAM.
You can only have up to 2MB of chip ram with any Amiga.
It is possible that your memory is faulty too, and as soon as a particular part of the memory banks gets accessed by data you get an error or a crash.
As a last resort type solution, try and pull all of the fast memory out and see if with only 2MB of chip ram you don't get that error message anymore.
Try inspecting those Workbench disks on another amiga (if possible) and see if they carry any library files or similar, that would load on boot and cause this error/crash. Like I mentioned, they could have some needed files for an expansion that is no longer there (e.g. WarpEngine or a GFX card, etc.)
Also keep in mind that I am giving you some ideas as how to troubleshoot this issue and while I may not necessarily be right with any of my suggestions it's just means of isolating some of many possible causes for this error message that you are getting.
I'll let you know if something else comes to mind.
-
Oh what a terrible mistake - of course 2MB CHIP RAM, not 8 !
Thank very much for this information, now I go to this work!