Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: matt3k on January 07, 2017, 03:59:30 AM
-
I have an Amiga 3000 with a mediator 3000Di and cyberstorm mk iii with boing bag 2 (currently was bb4).
Every time it boots it gives 80000003 errors on any command in the user-startup like 'If' or 'Path'. If I disable the user-startup it will boot up and run ok. My 3000D has a bad on board 030 so I can't run it without the CS. The 3000D also has a Radeon PCI card, Prisma Megamix, Xsurf 100. If I disable cache on boot it will boot up sometimes.
It was running fine for a long time, except that is would crash when I selected backup prefs for Abackup and when I ran SMBFS it effected screen refresh speeds. So I decided to go back to BB2, thinking it was the problem.
Here is what I tried:
1. Scanned for viruses - None found.
2. Tried different powersupply.
3. Tried different memory on the Cyberstorm.
4. Tried different 3.1 roms.
5. Tried different CIA's
6. Tried different Buster 11
7. Tried different Ramsey 7
8. Tried different Agnus
9. Cleaned motherboard and mediator 3000Di
10. Tried differnt 060 libs.
11. Tried Oxypather and cyberpatcher.
12. Ran whichamiga and it sees the full mc68060 with the mmu active.
Could it be a bad CS MK III? Any other ideas?
-
Does the machine have the INT2 mod? Is Ramsey 7 paired with a DMAC 4?
Looks like there are a lot of variables to account for, both with added cards and software. What happens if you drop back to stock 3.1 + 060 libs? What's your hard drive situation (filesystem, onboard/CS SCSI, real drive/CF/SD converter)?
-
Not to mention, what version of SetPatch and 68040.library (which is required if you use SetPatch from 3.1, the "dummy" 68040.library that loads the 68060.library).
8000 0003 can also be results of overclocking the 060 to a point where the FPU stops functioning.
-
Does the machine have the INT2 mod? Is Ramsey 7 paired with a DMAC 4?
Looks like there are a lot of variables to account for, both with added cards and software. What happens if you drop back to stock 3.1 + 060 libs? What's your hard drive situation (filesystem, onboard/CS SCSI, real drive/CF/SD converter)?
Hi Matt,
Yes, it has the INT2 mod, and the Ramsey 07 is paired with a DMAC 04.
I can try going to 3.1 and see and let you know...
The hard disk is a OWC SSD Sata on a Acard 2000 SUP 68pin scsi to sata. With PFS3.
-
Not to mention, what version of SetPatch and 68040.library (which is required if you use SetPatch from 3.1, the "dummy" 68040.library that loads the 68060.library).
8000 0003 can also be results of overclocking the 060 to a point where the FPU stops functioning.
Using the standard P5 libs with the dummy in 3.9, can try with 3.1.
The 060 has ran fine at the stock 50MHz for years and which Amiga states a FPU present...
-
It is maybe not related, but which monitor do you use?
I have a A4000 recapped and Mediator board V3. Everytime I connect my Amiga 1438S monitor, I Always get the same Guru error and my whoe Amiga crashes.
I use CPU cards 3630 and 3640 with 060 adapter. I also tried using Kickstart 3.1 and a patched version of Kickstart 3.9.
-
It is maybe not related, but which monitor do you use?
I have a A4000 recapped and Mediator board V3. Everytime I connect my Amiga 438S monitor, I Always get the same Gurro error and my whoe Amiga crashes.
I use CPU cards 3630 and 3640 with 060 adapter. I also tried using Kickstat 3.1 and a patched version of Kickstart 3.9.
I use an lg ips led 27ea63, it has vga and dvi in which I use for the radeon and the standard Amiga.
-
Could this be a cap issue? I have never had this system recapped, but it has been up and running most of its life answering the phone. It never had battery damage.
Do notice the Amiga video does a little dance for 30 seconds until it warms up then the picture is perfect.
-
Could be caps but I doubt it on an A3000. I havent seen one yet that NEEDED new caps, but have done plenty of them because I was asked to do it anyway. My 3000 acted strange too when I had it and used a Mediator with it. I would have to let it warm up the same way.
-
Think I finally figured it out!!!
Thanks to all for the help.
It turns out whenever the 060 libs (Phase 5) installed and I tamper with adding to the user-startup and startup sequence it goes running to 80000003 land.
So my vote if for the 060 itself, I'm ordering one now...
Do you still need the libs with a Rev 6 68060? Assume the latest Rev 6 is the way to go...
-
It turns out whenever the 060 libs (Phase 5) installed and I tamper with adding to the user-startup and startup sequence it goes running to 80000003 land.
Have you tried replacing the Phase 5 libs with THoR's?
-
@Mike
Yes, they were worse.
Maybe it is the entire Cyberstorm Card and not the 060. That seems more likely to me, but an 060 is easier to try.
-
Hmmm... malware?
I mention it as it seems very suspicious to me that the machine only crashes when you try to mess with the startup-sequence etc, or typing commands directly into a CLI or Shell.
That smells fishy, to me anyway.
1. Scanned for viruses - None found.
Which one, with which database? I doubt it would find anything on a file scan, but you might notice some of the system files aren't the ones that you think are being used.
It turns out whenever the 060 libs (Phase 5) installed and I tamper with adding to the user-startup and startup sequence it goes running to 80000003 land.
OK, you already isolated it to the library or the chip, and you are changing the chip anyway, as changing the library had no effect. That makes sense.
-
@Mike
Yes, they were worse.
Maybe it is the entire Cyberstorm Card and not the 060. That seems more likely to me, but an 060 is easier to try.
Did you try OS3.1 alone? Simplest thing to do would be a Workbench 3 boot floppy with the 060 lib(s) on. Work with a copy obviously, and of course you'll likely have to delete some files to make a bit of room first. Then run software from your hard drive (let's assume your software is virus free). Bare in mind your scsi.device version though and your partition setup etc...I can't be held responsible for any data loss if you directly or indirectly write to your hard drive! I'll assume you already have all of that in mind though as I know you're a clever chap. :)
For novices, perhaps that 911 boot disk would be of help here? I know literally nothing about it except for its existance, but it's likely got all this stuff on.
Unless you cold boot from another device (like floppy) then you really can't rule out Virus infection nor just corruption of some of your system files. But yes, that 060 would need the 060 lib(s) to fully test. In my gallery there's a VirusZ entry which lists all the files needed to fully check your system. It's worth it as I had a link virus infection called 'Ebola' a few years ago on one of my Amigas... VirusZ fixed it.
Out of curiosity, what is wrong with your onboard 030? Does it exhibit the same behaviour you are now seeing on your 060?
-
I kinda miss an answer to my question about what versions of the following you have installed:
Version full file C:SetPatch
Version full file LIBS:68040.libray
Version full file LIBS:68060.libray
-
I'm using virusz with the latest xvs.library. No viruses found...
I looked at virusz and found what you would expect for nonstandard dos.library and a few other items I would suspect.
I would hope that virusz would turn up the ebola and other viruses... Maybe a new virus has entered the Amiga community, that would explain a great deal frankly...
It does seem really odd. I just has to be the CS card or the 060. I'm going to swap out the 060 and if that doesn't fix it send it for repair...
Hmmm... malware?
I mention it as it seems very suspicious to me that the machine only crashes when you try to mess with the startup-sequence etc, or typing commands directly into a CLI or Shell.
That smells fishy, to me anyway.
Which one, with which database? I doubt it would find anything on a file scan, but you might notice some of the system files aren't the ones that you think are being used.
OK, you already isolated it to the library or the chip, and you are changing the chip anyway, as changing the library had no effect. That makes sense.
-
Did you try OS3.1 alone? Simplest thing to do would be a Workbench 3 boot floppy with the 060 lib(s) on. Work with a copy obviously, and of course you'll likely have to delete some files to make a bit of room first. Then run software from your hard drive (let's assume your software is virus free). Bare in mind your scsi.device version though and your partition setup etc...I can't be held responsible for any data loss if you directly or indirectly write to your hard drive! I'll assume you already have all of that in mind though as I know you're a clever chap. :)
For novices, perhaps that 911 boot disk would be of help here? I know literally nothing about it except for its existance, but it's likely got all this stuff on.
Unless you cold boot from another device (like floppy) then you really can't rule out Virus infection nor just corruption of some of your system files. But yes, that 060 would need the 060 lib(s) to fully test. In my gallery there's a VirusZ entry which lists all the files needed to fully check your system. It's worth it as I had a link virus infection called 'Ebola' a few years ago on one of my Amigas... VirusZ fixed it.
Out of curiosity, what is wrong with your onboard 030? Does it exhibit the same behaviour you are now seeing on your 060?
I did boot from 3.1 floppy, but I didn't do much testing off the floppy. It was used to boot for install 3.1.
I tried scanning with virusz with the latest xvs.library, but I did it from booting from the hard disk. Will that not provide proper functinality? It didn't report any viruses.
The SSD is on the Cyberscsi.device so no worries.
The 030 goes to a flashing yellow screen, so i believe it is defective...
-
I did boot from 3.1 floppy, but I didn't do much testing off the floppy. It was used to boot for install 3.1.
I tried scanning with virusz with the latest xvs.library, but I did it from booting from the hard disk. Will that not provide proper functinality? It didn't report any viruses.
The SSD is on the Cyberscsi.device so no worries.
The 030 goes to a flashing yellow screen, so i believe it is defective...
There are further settings in VirusZ to enable scanning of compressed archives etc. but the standard file check of SYS: with default settings would show up any infection if it existed.
It'd be nice to replace that 030... I wish it was socketed for you.
-
Matt, I could replace that 030 if you had another and wanted to risk it, but I would see if you can get another CPU card on loan from someone.
You are in the US? I may be willing to send you an 040 card to test and see how things run. I really suspect that BGA soldered POS socket Phase5 came up with for these cards. They are a major failure point. Replacing them is a pain too, but can be done. I did it once, and dont know if I would want to ever again. It takes soldering one pin at a time and building up a new socket row by row.
-
My .02 cents... I hate building a "house of cards" on a shaky foundation. Get that '030 replaced and see what other issues the motherboard may have before pointing fingers at one component or another. Try rebuilding the system piece-by-piece, from the ground up, and see when the issue occurs.
Of course, if you can just swap in another CPU or processor card and the issue disappears, then you're golden. :)
Also, here's a link to that Amiga911 disk Paul mentioned, earlier: http://amiga911maker.site11.com/index-1280.htm Might have something helpful on it?
-
From what I recall, yellow screen means that the CPU is ok, but that it detects something else is wrong. Faulty CPU is just a black screen, iirc.
EDIT: Ah, here it is
http://wiki.classicamiga.com/Amiga_boot_error_code_colours
-
Btw - on A3000, isn't there a jumper on the mobo that you need to swap when acc card is used (or not)? I have two A3000 myself, so I ought to know :p
-
Btw - on A3000, isn't there a jumper on the mobo that you need to swap when acc card is used (or not)? I have two A3000 myself, so I ought to know :p
Lucky guy :).
Yes, the jumpers are required to use the CS.
-
From what I recall, yellow screen means that the CPU is ok, but that it detects something else is wrong. Faulty CPU is just a black screen, iirc.
EDIT: Ah, here it is
http://wiki.classicamiga.com/Amiga_boot_error_code_colours
Pretty sure it is the FPU that isn't working... Thanks for the correction.
-
My .02 cents... I hate building a "house of cards" on a shaky foundation. Get that '030 replaced and see what other issues the motherboard may have before pointing fingers at one component or another. Try rebuilding the system piece-by-piece, from the ground up, and see when the issue occurs.
Of course, if you can just swap in another CPU or processor card and the issue disappears, then you're golden. :)
Also, here's a link to that Amiga911 disk Paul mentioned, earlier: http://amiga911maker.site11.com/index-1280.htm Might have something helpful on it?
Yes, I agree fully Mike. Pretty sure it's the FPU, so I suppose I could find someone to fix the board...
I have a warp engine, but the dang mediator isn't compatible with it... Suppose I could use the warp engine without the mediator... since I know the mediator isn't the issue... Will give that a go. Thanks Mike.
I built a 3.1 disk with the libs on it to install 3.9, I can try working off the floppy later and see what happens...
-
Yes, I agree fully Mike. Pretty sure it's the FPU, so I suppose I could find someone to fix the board...
I have a warp engine, but the dang mediator isn't compatible with it... Suppose I could use the warp engine without the mediator... since I know the mediator isn't the issue... Will give that a go. Thanks Mike.
I built a 3.1 disk with the libs on it to install 3.9, I can try working off the floppy later and see what happens...
The Warp Engine works with the Mediator on the A4000.