Post a new comment to participate in the discussion on how this
game should be configured, or to add relevant information regarding
the use of these configurations.
Posted by
Retro-Nerd at
2013-09-29 16:39:05 (Updated 2013-09-29 17:44:11):
It was indeed the tmp file.
Posted by
thevoice at
2013-09-29 16:16:24 (Updated 2013-09-29 16:20:04):
im mostly sure the game was started before packing it up in .lha. if so this is quite a bad idea if everybody relies on the same data .
so probally the best bet would be to have 1 person to make an install and make it public at eab. kinda like retroplay does with whdload installs.
Posted by
FrodeSolheim at
2013-09-29 15:05:34 (Updated 2013-09-29 16:17:51):
I have checked thevoice's install vs the one in the database. The installs differ on the following:
The file PE_AR000.TMP is only present in Retro-Nerd's install. This file may have been left by the installer, or perhaps more likely, the game has been started (thus creating the .TMP file) before it was packed.
The script file mag!-hd differs. They are equal except for that Retro-Nerd's version has an initial "setmap d" line which is not present in thevoice's install. Otherwise identical. Perhaps this has to do with the existing keyboard map currently active when installing the game?
c/SetMap differs (also by name though that's not really the problem - c/SetMap vs c/setmap). The binaries are different, presumably because they are copied from Workbench by the installer, thus the resulting install depends on the Workbench used to install it :-/
(Another note; though mag!-hd is included in the install, it isn't really used, as the used startup sequence is given in hdinst_args (basically what mag!-hd contains))
I don't have any great ideas for this issue right now... "HD-installs" or obviously more complicated than WHDLoad installs :-/
Posted by
Retro-Nerd at
2013-09-29 13:48:53 (Updated 2013-09-29 13:54:01):
In theory, yes. Maybe you should upload one of your own preinstalled versions for a file comparison.
Edit: I did the hd-install. But this has nothing to do if you use FS-UAE or WinUAE. Looks like a typical crc checksum problem if your own install isn't detected properly. Something differs then to my install.
Posted by
thevoice at
2013-09-29 13:43:23 (Updated 2013-09-29 13:48:59):
yea i am aware of the pre installed ones at eab. the question is why i get a different install when installing the same game from the same disks inside fs-uae.
in other words if i install it by myself i should get the very same result no?
so the question is what makes my install and the preinstalled version different and prevents the launcher to proper detect it
edit: maybe the person which made those installs can tell if they were made inside fs-uae or inside winuae.
is there any way to create the hdinstalled version out of the box ?
the screenshots indicate it is made from the aga version of the game.
but neither the aga or non aga version gives a result which the launcher accepts as a valid install
source images i used were the tris and dlm release from tosec.
Posted by
TCD at
2013-03-11 19:54:34 (Updated 2013-03-11 20:17:13):
It will be like WHDLoad works now. Just needs a few more options for the startup-sequence. The HD installed games can be extracted from lha archives. At least that's the idea for now... Might take a bit until it becomes reality
It was indeed the tmp file.
im mostly sure the game was started before packing it up in .lha. if so this is quite a bad idea if everybody relies on the same data
.
so probally the best bet would be to have 1 person to make an install and make it public at eab. kinda like retroplay does with whdload installs.
TODO: Follow up on the HDinst issues
I have checked thevoice's install vs the one in the database. The installs differ on the following:
(Another note; though mag!-hd is included in the install, it isn't really used, as the used startup sequence is given in hdinst_args (basically what mag!-hd contains))
I don't have any great ideas for this issue right now... "HD-installs" or obviously more complicated than WHDLoad installs :-/
In theory, yes. Maybe you should upload one of your own preinstalled versions for a file comparison.
Edit: I did the hd-install. But this has nothing to do if you use FS-UAE or WinUAE. Looks like a typical crc checksum problem if your own install isn't detected properly. Something differs then to my install.
yea i am aware of the pre installed ones at eab. the question is why i get a different install when installing the same game from the same disks inside fs-uae. in other words if i install it by myself i should get the very same result no?
so the question is what makes my install and the preinstalled version different and prevents the launcher to proper detect it
edit: maybe the person which made those installs can tell if they were made inside fs-uae or inside winuae.
Why don't you grab my preinstalled Mag! HD version from the EAB FTP? You find it in Commodore_Amiga/Game/CleanHDInstalls/
is there any way to create the hdinstalled version out of the box ? the screenshots indicate it is made from the aga version of the game. but neither the aga or non aga version gives a result which the launcher accepts as a valid install source images i used were the tris and dlm release from tosec.
It will be like WHDLoad works now. Just needs a few more options for the startup-sequence. The HD installed games can be extracted from lha archives. At least that's the idea for now... Might take a bit until it becomes reality
The AGA version will be suported in later FS-UAE updates. As preinstalled game folder. Just like some other games which are HD only.