Remove parts from the winsetup.exe

Started by arj0n, Mon 12/09/2011 14:14:00

Previous topic - Next topic

arj0n

Is it possible to modify (remove or hide) parts from the winsetup.exe, like for example the sound options?
(Just to create a more simplified version of the winsetup.exe with only the parts that are really needed for a specific project)

Gilbert

No, and moreover, since winsetup.exe is not the setup programme for AGS games you wouldn't achieve anything by modifying it.

All winsetup.exe does is solely launching "GAMENAME --setup", i.e. the setup programme is actually embedded in the AGS engine executable.

Since the engine is now open sourced, it should be possible to recompile a version of it with some of the options reduced but one needs coding skills to do that.

arj0n

Quote from: Iceboty V7000a on Mon 12/09/2011 14:21:30
No, and moreover, since winsetup.exe is not the setup programme for AGS games you wouldn't achieve anything by modifying it.

All winsetup.exe does is solely launching "GAMENAME --setup", i.e. the setup programme is actually embedded in the AGS engine executable.

Since the engine is now open sourced, it should be possible to recompile a version of it with some of the options reduced but one needs coding skills to do that.
I know it launches the game that way but thanx for your 3rth line and your quick response.

arj0n

#3
Used output.WriteRawLine & output.WriteRawChar within the project in a gui with buttons which each contain a scripted predefined config.
If I'm right this way winsetup.exe is not needed anymore. Or is there a disadvantage doing it this way?

The search is still broken so a question: is there a plugin for this already?

monkey0506

Yes, the drawback to doing it that way is that you have to launch the game to use that method, and then exit and restart it to see the changes.

SSH wrote a module which worked alongside a VB Script to simplify this process I believe. Don't recall what it was called, but you could try Googling "site:adventuregamestudio.co.uk/yabb SSH module config"

arj0n

For me that's not really a drawback, I only use the fullscreen/windowed mode option and the borders on/off option.
The rest of the options is of no use for me in this project.
It will always work both ways (fullscreen or windowed in combi with borders on/off.
But if they like to change the setting for the next time they start up the app,
they now can do that with just 4 simple buttons inside the project instead of the 'more complicated' winsetup.exe.

Thanx for the info guys.

Gilbert

Quote from: monkey_05_06 on Mon 12/09/2011 20:21:01
Yes, the drawback to doing it that way is that you have to launch the game to use that method, and then exit and restart it to see the changes.

Yeah. And the main problem is, if for whatever reasons the user changes the setting to something incompatible with his own system he cannot start the game again anymore.

Snarky

Quote from: └» Arj0n «┘ on Mon 12/09/2011 20:48:48
For me that's not really a drawback, I only use the fullscreen/windowed mode option and the borders on/off option.
The rest of the options is of no use for me in this project.
It will always work both ways (fullscreen or windowed in combi with borders on/off.
But if they like to change the setting for the next time they start up the app,
they now can do that with just 4 simple buttons inside the project instead of the 'more complicated' winsetup.exe.

Thanx for the info guys.

It's important to have the graphics filter options in there, since (depending on the resolution of your game), otherwise it might not play on all computers. And if your game has sound/music, those options might be needed to play audio correctly as well.

There's generally a reason for each configuration option, and just because you don't use it that doesn't mean it's not needed.

arj0n

#8
@ Iceboty & Snarky:
Sound Options:the project has no music/soundfx.
Graphic settings: the project runs in 1024x768 and using a graphic filter is of no use cause mostly users will get get a warning that the graphics mode/adapter is not supported when using a filter.
Language: not used.

So in this specific case I think I only need windowed/full-screen and the side borders on widescreen monitors.
So I only need four predefined settings (gui with 4 buttons):
* full-screen with side borders
* full-screen with no side borders
* windowed with side borders
* windowed with no side borders

It's no problem that the choosen setting will only apply after a restart because it will actually always run.

Am I thinking correct of did I overlooked something?

SMF spam blocked by CleanTalk