The first (CodeAudio) is an E program, and it seems it fail to catch the version number once we open it to check the version, Daniel say:
So the same binary works fine under AmigaOS 3.x but fails to check the command VERSION under AmigaOS 4.xI think C:Version looks for a .cdata chunk in the file but since this
is an Amiga-E program there are no chunks and then C:Version will only
search a number bytes at the beginning of the program. But CodeAudio is
to big and the version string is too far away so it is not found. Nothing
I can do about it. It works on OS3 though since OS3 C:Version will scan
the entire file until it finds the version.
The other program i tested is AmiArcadia, this is what James discovered during our port from 68k to OS4
More info at: http://amigan.1emu.net/releases/ami-code.txtVersion:
(a) Version strings which are not prepended by a NUL ($00) byte are not
(b) Multiple version strings in one file confuse the parser.
(c) "If I create a file with nothing but the OS3 executable identifier
($000003F3) at the beginning followed by a valid version string, the
Version command won't find the version. If the executable identifier
is replaced with anything else (binary or alphanumeric) then the
Version command works. My suspicion is that if the Version command
finds an OS3 executable identifier at the beginning of a file, it only
looks for a version string in a particular type of Amiga OS hunk. If
that's not the case then it is a complete mystery to me. Regardless,
the Version command should get fixed for the next OS4 release."
So would be cool if VERSION command can be fixed on OS4 almost to support any AmigaOS 3.x behaviours