Amos Setup

DrkStarr · 30 January 2023, 07:25

Can anybody help me with setting up AMOS.

I'm trying to get Set Interpreter to work, but fooling around with it hasn't solved anything.

I'm using a GitHub version of AMOS, and everything has worked well, but I can't get into the Set Interpreter without loading some files from the original disks and that's still not helping.

Dan · 30 January 2023, 16:25

If i remember right, the "set Interpreter" file on github is a compiled version, while AmosPro is searching for the not compiled version.

Just copy the "Interpreter_config.amos" in to the amos Pro folder, and it should work ok.

DrkStarr · 30 January 2023, 22:15

Moving over the original Interpreter_Config.AMOS works. But you do need the AMOSPro_Interpreter_Config in DH0:S to edit it.

I was also using the version from AOZ-Studio. This version will not apply the what I was trying to edit (Variable Name Buffer Size) but it will change it.

So in the end I have to use the marc365 version. I thing I noticed about that version is the Text Buffer size for the program jumps up. It goes from 137388 to 327680. o.O

Is this cool? It seems like a big jump. I have the chip ram to program it, it's under emulation, so I can bump it up to 1 million, but is this going to cause any problems?

Thanks for all the help

DrkStarr · 31 January 2023, 06:24

So I looked at the two programs some more. The difference I'm seeing is with the Default Text Buffer Size under Set Interpreter. In marc365 it's set to 320k, in AOZ I think it's set to 32k.

I also noticed some different changes in the marc365 compiler default config which cause the AMOS program to not run at all after compiling, but after setting the marc compiler up like the AOZ, it all works fine.

This program is very flexible. Thanks for helping out.

30 January 2023, 07:25	#1
DrkStarr Registered User Join Date: Aug 2022 Location: Detroit / USA Posts: 37	Amos Setup Can anybody help me with setting up AMOS. I'm trying to get Set Interpreter to work, but fooling around with it hasn't solved anything. I'm using a GitHub version of AMOS, and everything has worked well, but I can't get into the Set Interpreter without loading some files from the original disks and that's still not helping.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Wip] Amos Professional X : Bring AGA to Amos Pro!	freddix	Coders. AMOS	53	22 July 2023 09:53
AMOS Files from Writing RPG's in AMOS	supercruiser	request.Other	0	21 April 2020 13:03
How to use AMOS 3D with AMOS PRO?	viddi	Coders. AMOS	6	25 October 2012 23:11
f/s Amiga Amos Programming books / Disks / Easy Amos & other Books mega collection!	fitzsteve	MarketPlace	4	23 May 2012 04:35
Where's the amos.library on the 3-disk AMOS set?	andreas	support.Apps	0	15 November 2001 16:04

30 January 2023, 16:25	#2
Dan Registered User Join Date: Nov 2004 Location: Germany Posts: 629	If i remember right, the "set Interpreter" file on github is a compiled version, while AmosPro is searching for the not compiled version. Just copy the "Interpreter_config.amos" in to the amos Pro folder, and it should work ok.

30 January 2023, 22:15	#3
DrkStarr Registered User Join Date: Aug 2022 Location: Detroit / USA Posts: 37	Moving over the original Interpreter_Config.AMOS works. But you do need the AMOSPro_Interpreter_Config in DH0:S to edit it. I was also using the version from AOZ-Studio. This version will not apply the what I was trying to edit (Variable Name Buffer Size) but it will change it. So in the end I have to use the marc365 version. I thing I noticed about that version is the Text Buffer size for the program jumps up. It goes from 137388 to 327680. o.O Is this cool? It seems like a big jump. I have the chip ram to program it, it's under emulation, so I can bump it up to 1 million, but is this going to cause any problems? Thanks for all the help

31 January 2023, 06:24	#4
DrkStarr Registered User Join Date: Aug 2022 Location: Detroit / USA Posts: 37	So I looked at the two programs some more. The difference I'm seeing is with the Default Text Buffer Size under Set Interpreter. In marc365 it's set to 320k, in AOZ I think it's set to 32k. I also noticed some different changes in the marc365 compiler default config which cause the AMOS program to not run at all after compiling, but after setting the marc compiler up like the AOZ, it all works fine. This program is very flexible. Thanks for helping out.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)