Amiga 3000 / Error 8000000B

[Kernel]

I've done some searches on Google as well as here but the reasons for this error seem to range across a few things.

I'm seeing this when I try to use the latest Scalos (beta) V41.7 - it pops up on Scalos_Async_Backfilll and I've also seen it when messing around with Zeus BBS.  the system seems stable otherwise.

030 @ 25, 2 Chip 16 Fast, 4GB SCSCI Drive... no other problems per se at this point.  It's a pretty vanilla 3.1 install with a few commodities running and of course MUI, VisualPrefs, and MagicWB.

Any insight would be helpful.

Also note, I've ran all the AIBB tests and it doesn't crash.

[Kernel]

I downgraded to the older 1.2d version of Scalos and it runs exceot when I try to run the Scalos Prefs utility, I get an 80000004 error.  The other prefs programs within Scalos work fine.

[don27dog]

I was having problems with error 80000004 errors and http://aminet.net/search?query=dtack helped get rid of them.

[Kernel]

Worth a try I suppose

Thanks!

[Kernel]

I was having problems with error 80000004 errors and http://aminet.net/search?query=dtack helped get rid of them.

Well, that did not do the trick.  And I now know there is something going on at a basic level in the A3K.

For the most part, it's stable.  But with certain programs I can *always* duplicate crashing.

A specific example: I boot from a 3.1 floppy Workbench disk and run the icon in the MUI drawer that looks like a smiley face - if anyone doesn't recall, this pops up a windows with an small animated demo from the MUI author - and when it exits, my A3K locks up.

I can run all AIBB benchmarks with 0 issues.  I would think that is stressing the machine so I'm at a loss as to what is happening.

[Leffmann]

You will get the 8000 000B if a program uses FPU machine instructions and you have neither FPU nor software emulation for it installed. For an otherwise illegal or unsupported instruction you'll usually get 8000 0004, sometimes 8000 000A.

If you're sure none of your programs require an FPU, and that the files are not broken, then I have no idea why you get these errors.

[Ral-Clan]

This probably isn't much help, but Amidock in AmigaOS3.9 would always cause this crash when I was using an Amiga 3000.

I really only ever saw this type of crash on my Amiga 3000 for some reason.

[Kernel]

You will get the 8000 000B if a program uses FPU machine instructions and you have neither FPU nor software emulation for it installed. For an otherwise illegal or unsupported instruction you'll usually get 8000 0004, sometimes 8000 000A.

If you're sure none of your programs require an FPU, and that the files are not broken, then I have no idea why you get these errors.

then something perhaps with the 68882 in my machine?

[Kernel]

Well, I do have a 68882 in this so I think that covers the FPU doesn't it?

I've traced the MUI crash past that anim program to the MUI/Docs/Registration program.  It's weird... click it and the system just freezes with the mouse pointer flashing/flickering.  Hard to describe.

[Ral-Clan]

You haven't mentioned what version of Amiga OS you are using (or I didn't see it).

If you are running OS3.9 have you tried disabling the patches for OS3.9 in your startup sequence?  It's a setpatch command thingy....I forget exactly, but I'm sure it's easily found through Google.

[matthey]

Well, I do have a 68882 in this so I think that covers the FPU doesn't it?

It's a line F trap/guru. I can think of 3 possibilities:

1) buggy program or library (may be a MUI add-on library)
2) an fpu program or library for the 68040 or 68060 was accidentally installed and it's trying to use the FSOP or FDOP instructions
3) a program or library for the 68040 or 68060 was accidentally installed and it's trying to use the MMU or MOVE16 instructions

If it only happens when running MUI then it may be an MUI add-on library. You can either try installing new versions that may fix it or reinstall MUI and then the add-ons one by one to see if the problem returns.

[Kernel]

Well, one issue solved.

I booted up AmiKit and tried the registration program there and it ran fine; I copied it over the A3000 and it ran fine; I then opened it up from the install folder I had created from the archive and it too opened fine.

So it appears that something corrupted it during install.

One issue out of the way...

[Kernel]

Also found one of the programs that is causing an 8000000B has an issue as well.. tried the previous version and it runs fine.

[Kernel]

It's a line F trap/guru. I can think of 3 possibilities:

1) buggy program or library (may be a MUI add-on library)
2) an fpu program or library for the 68040 or 68060 was accidentally installed and it's trying to use the FSOP or FDOP instructions
3) a program or library for the 68040 or 68060 was accidentally installed and it's trying to use the MMU or MOVE16 instructions

If it only happens when running MUI then it may be an MUI add-on library. You can either try installing new versions that may fix it or reinstall MUI and then the add-ons one by one to see if the problem returns.

Interesting, I do see a 68040.library in libs that came from the 3.1 install but other than that, nothing jumps out.

[matthey]

Interesting, I do see a 68040.library in libs that came from the 3.1 install but other than that, nothing jumps out.

The 68040.library won't be used with a 68030. SetPatch detects the CPU on boot and uses it only if a 68040 is detected. It shouldn't be a problem at all. It's a lot more rare to install a 68040 or 68060 program or library than for someone without an FPU to install a program or library that uses the FPU. Almost all non-FPU 68040 or 68060 libraries and programs will work on the 68030. Some that use the FPU will also work depending on which compiler is used.

It's more likely that you have some other corrupted files for some reason. If you have one then you could have others. The big question is what would be causing the corruption.