Hello Everyone!

We’ve heard your feedback since the launch of Gunship + Gunship 2000 and we’re actively working on fixes and improvements for these two games.

First and foremost, our main concerns were getting the latest, most complete version of Gunship 2000 and removing the copy protection for Gunship.

To allow you all to see exactly what we’re working on, we’ve added a public testing branch. This has a few major fixes listed below. Feel free to opt in and see what we’re up to!

If you have any feedback or notice something we may have missed, please mention it in this thread!

Testing Branch Password:
rO32QM78vqqp

Testing Branch Changelog:
- Gunship: Fixed crash at mission 3 due to copy protection
- Gunship 2000: Updated to latest version and cleaned up files
- Updated dosbox settings for a better experience

Thanks for making this available.

These notes are from GS2000.

Game runs and the copy-protection value is auto-entered. Sounds works.

However, I cannot get the game to use the joystick.

Running the included DOSBox on its own proves DOSBox picks up my controller, but GS2000 does not.

Selecting the Setup option in the Dosbox game menu doesn't work (its supposed to run Setup.exe, but instead just exits and returns to the windows launcher). I believe this is the correct way to select a joystick - but as I say, it doesn't work to launch Setup, and then in-game via ALT-J within the game does nothing - presumably because there was no setup config created indicating a joystick.

So looks like there's a problem configuring a joystick within GS2000 setup program.

When I manually go through DOSBox to run setup, it reports an "MSCDEX not loaded." error - which looks like its the root of the problem preventing setup from being run to configure the joystick in-game that DOSBox can see.

Assuming setup modifies the SETUP.GS2 file in the install directory : this file is binary, not text so there's no way to meaningfully edit it to force the joystick config outside of using the setup program which won't run.

EDIT: Manually doing a DOSBox imgmount and then running setup will allow me to configure the joystick, which then works within the game.

So looks like the solution is to provide an option for users to run setup - I would suggest changing the gs2000.conf file from the original (right below) to the revised one (which works for me) under the :setup that Option 2 calls:

--- ORIGINAL START ---
:setup
cls
setup
exit
--- ORIGINAL END ---

--- MODIFIED START ---
:setup
imgmount d gs2000.iso -t iso -fs iso
cls
setup
exit
--- MODIFIED END ---

And where is the testing branch available? where should that password be used?

Greetings

Ok. I found it. You need to add a private channel from the beta option under Galaxy

Apparently you consider that Atari has the right to their license-game and that "seller" have the right of their fixing work plus the game itself? Good deal, indeed,

Maybe ethically debatable, or just the easy/lazy way. Indeed.

The matter is if the "work of someone else" is being sold in a legit way (I doubt it) and if Atari, as the current right holder, has the rights to use anything related with their game.

How does one get to the testing branch?

So you go into Manage Installations > Configure within Galaxy, set Beta Channel to the correct item and insert the code they plugged in here earlier.

Yeah so, guys from Atari - it is not ethical to take the modified installers from the seller.

Obviously he has not copyrighted his work but still. Why not simply email him with a heads up?

The actual work involved amounts to 10 minutes but still, do it right!

Hello everyone!

There is a new build available on the Testing Branch, if you are still opted in you should be prompted to update.

If you haven’t and would like to try it out, the password to opt in is still:

rO32QM78vqqp

Take a look and leave any feedback you might have in this thread!

Thank you!