3D game Testament..... file is not executable?

[A4000_Mad]

Hi,



Due to not quite having enough memory for it to run properly after booting into OS3.9, I'm trying to start the 3D game Testament by switching on with both mouse buttons held down and choosing to 'Boot With No Startup-Sequence'.

(the problems I'm getting are a yellow alert "Memory allocation error !", failure of the game to start at all, or missing sound effects in the game)

After booting without startup-sequence I'm typing:-

cd Work:Games2/Testament
Testament

But this just gives the report "testament: file is not executable"

I believe that the big and colourful Testament icon activates the file 'Testament.exe' as this also starts the game from inside Workbench. But if I type Testament.exe instead of Testament, I get the request "Please insert volume ENV in any drive" with the choices to Retry or Cancel. Clicking Retry does nothing and clicking Cancel gives the report:-

testament.exe
Program failed (error #80000004).
Suspend              Reboot



Can anyone be of help please?

[A4000_Mad]

Thanks JJ but could you be more specific please as it has made no difference to type:-

ASSIGN Env: Ram:

as well as my others:-

cd Work:Games2/Testament
Testament

OR

cd Work:Games2/Testament
Testament.exe

[A4000_Mad]

Thanks FaLLeNOnE

For 'iconx testament' i got the report "iconx is used from Workbench only".

And for 'Ed Testament' i just got a window titled Ed 2.00 with the word "testament.exe" inside of it.


If I click on the Icon tab of the Testament screengrab above it shows that the default tool is indeed iconx. However, there is no problem to start Nigel Mansell racing after choosing 'Boot Without Startup-Sequence'. Nigel Mansell racing also has the default tool of iconx, but I just need to type:-

cd Work:Mansell
Mansell

and away it goes. Vrooom!

[A4000_Mad]

Yes there are ticks on Read, Write, Delete and Execute

[A4000_Mad]

Pass! To be honest I'm not sure exactly what happens when you boot without startup-sequence. Is a setpatch used and are the drawers ENV, T and Clipboards even put into RAM?

Anyway, it's an AMIGA A1200 Desktop with Blizzard 030 Mk IV running OS3.9

Oh.... the game runs from the 3 floppy fisks fine, but we don't want to keep using those when we have a hard drive of course.

[A4000_Mad]

Thanks Matt

ASSIGN ENV: RAM:

followed by 'Execute Work:Games2/Testament/Testament' gave two lines:-

testament.exe: Unknown command
testament.exe failed returncode 10

Will have a look at the startup-sequence on the floppy disk etc next.....

[A4000_Mad]

Matt_H wrote:
entering the Early Startup Menu before the 3.9 updates are kicked in.

I wasn't sure what you meant by that Matt, but it looks like FaLLeNOnE has just explained it.


The floppy disk startup-sequence is:-

setpatch quiet
assign env: ram:
testament.exe

So I tried typing:-

setpatch quiet
assign env: ram:
Work:Games2/Testament/Testament.exe :oops:

The HDD light flashed for about 1 second then the screen went dark followed by nothing else happening.

There is no WHDLoad installer, probably because there is a hard drive installer on disk 1.


@ FaLLeNOnE

Will give that a shot next thanks :-)

[A4000_Mad]

@ FaLLeNOnE and Matt H

Well those 'setpatch noromupdate' and 'stack x' command have made all the difference so far thanks :pint:

However, I'm still getting yellow reports of "Memory allocation error !" at the beginning and during the game, plus variable missing sound problems. The stack was 4096. We've got 30 meg of fast memory so I don't know why I'm getting the yellow memory alert and sound faults?


@ rkauer

Thanks mate :-)

[A4000_Mad]

Just to say thanks again and all is working fine now :-)

I'm pleased to know how to get this game to work after booting without startup-sequence and to use 'setpatch noromupdate' and 'stack' commands.

As suggested I switched on the A1200 while keeping both mouse buttons held down.

Then I typed:-

Assign Env: Ram:
setpatch noromupdate
cd Work:Games2/Testament
stack 4096
Testament.exe


:cheers:

[A4000_Mad]

Yeah it sure makes you happy if you can remember something to help someone out. It makes the years of trial, error and frustration seem much more worthwhile  :violin:  :lol:

Oh.... Your instructions got the game started ok, but a fresh install of Testament was needed to fix the sound problems and stop the yellow "Memory allocation error !" reports  8-)