AMOS 3D: Software Failure: 80000004

[zosodk69]

I'm trying to get AMOS set up to run some of the old programs I created in my youth.  The problem is, when I created these programs, my machine had a slightly different configuration.  I'm running an A3000D 030/16.  Back in the day I had kickstart roms v2.04.  Today I've got the same machine with v3.1 kickstart roms and a Cyberstorm PPC 233/060/60.

It seems AMOS is otherwise working fine, it's just the 3D extension that's giving me fits.  Whenever the interpreter encounters TD prefixed command it bombs with said error.  This happens in both AMOS 1.36 and AMOS Professional 2.0.  Any in site would be great.

[rednova]

Dear Friend:

http://amos.condor.serverpro3.com

this is the amos factory, the amos online group.
I am sure someone there can help you. I use amos too,
but I don't have experience with the 3d extension.
Cheers!!!

rednova
-mobilis in mobile-

[bloodline]

zosodk69 wrote:
I'm trying to get AMOS set up to run some of the old programs I created in my youth.  The problem is, when I created these programs, my machine had a slightly different configuration.  I'm running an A3000D 030/16.  Back in the day I had kickstart roms v2.04.  Today I've got the same machine with v3.1 kickstart roms and a Cyberstorm PPC 233/060/60.

It seems AMOS is otherwise working fine, it's just the 3D extension that's giving me fits.  Whenever the interpreter encounters TD prefixed command it bombs with said error.  This happens in both AMOS 1.36 and AMOS Professional 2.0.  Any in site would be great.

I think you have your error code wrong...

look here:

http://www.amigahistory.co.uk/guruguide.html

[zosodk69]

bloodline wrote:
I think you have your error code wrong...

From the URL you just linked to:

If the first digit of the subsystem ID is greater than 3, there is no way to recover from the error. In these cases, subtract 8 from the first digit to get the subsystem ID number.

[Spellcoder]

80000004 means AMOS 3D somehow tried to run a 'Illegal instruction'. Maybe AMOS 3D uses selfmodifying code, in which cause disabling the CPU caches would help. (in the 'Early startup control' while booting or with some shell command of which I forgot the name)

[SamuraiCrow]

The shell command that does it is "cpu nocache".

[Lonewolf10]

Which version of the 3D extension are you using?

Are all appropraite libraries in the correct place?


You should have "AMOSPro_3d.lib" (or "3d.lib" if you are using the original extension) and "c3d.lib" in the "APSystem" folder.
I don't know what would happen if the "c3d.lib" was missing.

Also, are all 3D files ".3DT", ".3DO" etc. where they should be?


EDIT: Forgot this... I did get AMOS to crash before when loading in files into Banks which were too small. So loading in a 100 byte file into bank 6, which was only 80 bytes long , caused the remaining 20 bytes to overwrite into the bank following it. I think I got a different error code though, but it might be worth checking just incase.


Regards,
Lonewolf10

[zosodk69]

I've traced this problem back to ppclibemu.  When I comment ppclibemu_install out of my startup-sequence, the AMOS 3D extension starts working great.  I don't know if there is a solution to this other then said workaround.