Forums

Application/Game : Activision's Star Trek: Armada
Wine version : 1.1.32
Distribution : OpenSUSE
Distribution Version : 11.1 (32 bit)
Graphics card : Nvidia GeForce 7600 GT
Graphics card driver version : 190.42

Game Icon:

Edité par JimBo

1) Heading should look different
2) Use select_prefix
3) quote paths
4) do
cd "$TEMP"
echo "[HKEY_CURRENT_USER\\Software\\Wine\\Direct3D]" > armada.reg
5) In German there is Programme and in Spanish there is Archivo de programma and not Program Files so your script doesn't work for everyone
6) use POL_SetupWindow_wait_next_signal and POL_SetupWindow_detect_exit at installing patch

1) Should I use the heading from your 'Winamp' install script as an example? If so, can I add extra lines (ie. the Note)
2) I started this script with the 'Script Creator' plugin...and it used 'select_prefixe'. I'll fix it.
3) Not sure what you mean...all the paths in my script are quoted. (" ") Can you give me an example?
4) Will do.
5) Is that why you use this code in your Winamp install script:
PROGRAMFILES=`wine cmd /c echo "%ProgramFiles%"`
PROGRAMFILES=${PROGRAMFILES:3}
6) Like this?...
patch_armada()
{
cd $HOME
POL_SetupWindow_browse "Please select the patch file" "Patch selection" ""
POL_SetupWindow_wait_next_signal "Patch installation in progress..." "Patch"
wine "$APP_ANSWER"
POL_SetupWindow_detect_exit
}

1) Yes of course
2) Script Creator is bit outdated and prefixe is from French AFAIK French words in functions shouldn't be used anymore in scripts
3) cd $CDROM
if it would be quoted then
cd $CDROM
5) Yes
6) Yes

you could also look for icon for that game (in ~/.local/share/icons) and copy it to "~/.PlayOnLinux/icones/32" with the name of the script (without any extensions)

Ok...how does this look?

Use
instead


Why do you do ?
sleep 5

If the POL_SetupWindow_wait_next_signal don't work as it should then do it as in this script

Did the "sleep 5" as a delay in the script to allow time for the patch program to complete. The "POL_SetupWindow_wait_next_signal / POL_SetupWindow_detect_exit" command nest did not work for the "setup.exe" program from the CD, so I assumed the same thing would happen with the patch program.

Made some more modifications...here is the updated and fully tested code:

If POL_SetupWindow_wait_next_signal don't work, don't use it at all. Do it as I made it in script I gave you above. Sleep command is not a way to do this, it only delays.

BTW. Don't set UseGLSL, RenderTargetLockMode, Multisampling because they have default values the same as you set them.

Edité par NSLW

Wasn't sure if the 'POL_SetupWindow_Wait...' thing didn't work only on my distro. Left it in just in case it works for someone else. The 'Sleep 10' is to give time for the 'setup.exe' to kick off and hide the window as to not confuse people in thinking the install took less then a second. I don't really see the harm in leaving both in.

On my machine the UseGLSL registry entry is blank by default...besides I'm not a big fan of relying on 'defaults' to stay true for the duration. One thing I've learned with OpenSource, is things keep evolving, and changing. If it's all the same to you, I feel more comfortable leaving stuff in the script that I know works for the game.

Wasn't sure if the 'POL_SetupWindow_Wait...' thing didn't work only on my distro. Left it in just in case it works for someone else. The 'Sleep 10' is to give time for the 'setup.exe' to kick off and hide the window as to not confuse people in thinking the install took less then a second. I don't really see the harm in leaving both in.

I do see harm. It doesn't work so why should be in script? Next thing is that script goes forward and does things that should be done after successful installation.

On my machine the UseGLSL registry entry is blank by default...besides I'm not a big fan of relying on 'defaults' to stay true for the duration. One thing I've learned with OpenSource, is things keep evolving, and changing. If it's all the same to you, I feel more comfortable leaving stuff in the script that I know works for the game.

Then you should set 150 values because their defaults may change in future. That's sinless, you should set value only if it's needed.

Ok...I've been able to sort out the first issue. Turns out the 'setup.exe' at the root of the CDROM was simply calling a 'setup.exe' in the setup folder. So I changed the script to call that one...now everything behaves properly.

I also trimmed down the registry entires to only include the ones that are noted as being required in order for the game to run properly. I've also tested it with the latest version of wine. Cool?

The new code is as follows:

Forgot to ask: should I be editing/updating my original message/code, or keep posting it the way that I have been?

And how do you guys get the game icon in your post?

Edité par JimBo

I also trimmed down the registry entires to only include the ones that are noted as being required in order for the game to run properly. I've also tested it with the latest version of wine. Cool?

This
echo "\\"UseGLSL\\"=\\"enabled\\"" >> armada.reg
is default setting since I don't even remember when.

Forgot to ask: should I be editing/updating my original message/code, or keep posting it the way that I have been?

Just edit first post.

And how do you guys get the game icon in your post?

If you upload to imageshack.us then you'll get special link for it then you only need to paste it to Message window you normally write here on the forum.

This
echo "\\"UseGLSL\\"=\\"enabled\\"" >> armada.reg
is default setting since I don't even remember when.

Is the Set_GLSL "On" command the same as that registry entry?

Just edit first post.

If you upload to imageshack.us then you'll get special link for it then you only need to paste it to Message window you normally write here on the forum.

Will do!

Is the Set_GLSL "On" command the same as that registry entry?

Yes but it isn't needed because it's default setting.

Yes but it isn't needed because it's default setting.

Ok...edited the first post, and was able to included the Game Icon...thanks for the ImageShack link. I removed the "Set_GLSL On" command...but kept the registry entry. On my machine the GLSL entry on Wine always defaults to an empty value. Not sure if that means enabled or disabled. I have noticed that if it's not 'enabled' the game has some serious video issues.

Now to try Star Trek: Armada II! :D

Thanks for your guidance!

Use
instead of

Do
instead of

Use

?

1	"$HOME/.local/share/icons/*_armada.xpm"

instead of

?

1	"$HOME/.local/share/icons/c9ab_armada.xpm"

The CP command with a wild card in a bash script doesn't work all that well...it produces a "cp: cannot stat" error. The following script line works nicely though:


Aside from that one, I made the other change you suggested, and a couple of my own:

1. There was a minor syntax error on lines 74 and 76 in the if...elif statement. (Aside: running PlayOnLinux from the command line really helps with debugging scripts.) :)

2. I changed the name from "Star Trek: Armada" to "Star Trek - Armada". I figured the colon in the filename may cause problems for some file systems.

Are there any plans to include an 'uninstall' section in these scripts? I noticed when removing an application stuff is left behind...like Wine icons and application references. Makes things a confusing and requires a manual clean-up process many may not know how to accomplish properly.

Cheers!

J.

Edité par JimBo

Are there any plans to include an 'uninstall' section in these scripts? I noticed when removing an application stuff is left behind...like Wine icons and application references. Makes things a confusing and requires a manual clean-up process many may not know how to accomplish properly.

You can use remove option. It makes no sense to uninstall application when it has its own wineprefix.

You can use remove option. It makes no sense to uninstall application when it has its own wineprefix.

Yes...but the remove option does not delete the stuff that gets created in the ".local/share" directories for Wine. They need to be deleted manually.