Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: bbond007 on May 31, 2010, 08:31:05 PM
-
Hi
I'm trying to get the remaining bugs worked out of my new A1200.
I have installed ClassicWB ADV on my 4gb CF card.
Most applications are working fine, however Ibrowse and DirOpus4 seem to both crash with GURU #8000000D
I have a Typhoon MK2 030/40 with FPU & 32mb RAM.
I have a subway USB adapter, but the errors occur even when the software for that is not loaded.
I tried increasing the stack.
Any Ideas?
Thanks!
-nate
-
"Coprocessor Protocol Violation" error (GURU 8000000D).
I also get the same error with DirOpus4 if I boot of my Workbench floppy.
Also, the machine freezes with SysSpeed when I run the CPU/FPU test.
I have no idea what to do :(
-
Try to change the Maxtransfer rate to 00x1fe00 with HDToolbox. This will get rid of your problem.
-
Try to change the Maxtransfer rate to 00x1fe00 with HDToolbox. This will get rid of your problem.
I checked my MaxTransfer and its set to 0x1fe00 on all partitions.
Any other ideas?
Thanks,
-nate
-
What happend when you copy this program to your RAM disk and run the program?
-
What happend when you copy this program to your RAM disk and run the program?
if I copy DirOpus4 to RAM: I still get error #8000000D when I run it.
Thanks,
Nate
-
What happend when you copy this program to your RAM disk and run the program?
Actually,
I can run SysSpeed (cpu/fpu test) and DirOpus4 after the computer has been off and don't get #8000000B(for a while), but once I get it I continue to get it.
I can boot off of my original Workbench floppy, try and run DirOpus4 and still get it - until I let the computer cool off again.
Most stuff runs really reliably however long the machine has been on. Just not the stuff that causes #8000000D...
-
Don't know about DOpus, but which CPU option did you choose when installing IBrowse? Sounds like you maybe have the wrong build installed.
-
Don't know about DOpus, but which CPU option did you choose when installing IBrowse? Sounds like you maybe have the wrong build installed.
I doubt I installed the wrong version :) but you gave me an idea.
I reinstalled and just picked the 020 without FPU and it actually seems to work. I'll try the FPU version and see if I encounter the error again.
I'm thinking I have a bad FPU chip.
-
I reinstalled and just picked the 020 without FPU and it actually seems to work. I'll try the FPU version and see if I encounter the error again.
Update:
the 020 version works well, the 020+FPU version brings my old nemesis #8000000D.