Jump to content

Custom Euroscope package


Recommended Posts

This might be on developers especially:

Here at VACC-CZ we would like to make a completely pre-set package for our controllers including .PRF, .ASRs, settings files, .SCT/ESE, etc. We would like to publish a package which could be just downloaded by user and ready to run of the shelf. Would it be possible? We tried something like that with 3.1d, it quite worked but we had some problems and didn't finish the whole mission. Now with 3.2 we would like to finally finish it. I especially like the idea of having a portable version on USB stick ready to be used at any computer without having to install ES first.

 

My questions:

1) does ES write some stuff somewhere else than into his Program Files folder and user docomeents? I mean shall we expect something important in registry, fonts, etc. that needs to be also transferred to the end user computer?

 

2) Can we disable the default stuff which we dont use? Like the Hungary folder, default atis, etc? Whenever we delete those files the ES seems to start installation again trying to repair them. We agreed we see no reason why should our controllers keep some never-to-use ASRs from Hungary over there...

 

Thank you for info,

Pavel

Pavel Brodsky

VACC-CZ

Link to post
Share on other sites
This might be on developers especially:

Here at VACC-CZ we would like to make a completely pre-set package for our controllers including .PRF, .ASRs, settings files, .SCT/ESE, etc. We would like to publish a package which could be just downloaded by user and ready to run of the shelf. Would it be possible? We tried something like that with 3.1d, it quite worked but we had some problems and didn't finish the whole mission. Now with 3.2 we would like to finally finish it. I especially like the idea of having a portable version on USB stick ready to be used at any computer without having to install ES first.

 

My questions:

1) does ES write some stuff somewhere else than into his Program Files folder and user docomeents? I mean shall we expect something important in registry, fonts, etc. that needs to be also transferred to the end user computer?

 

2) Can we disable the default stuff which we dont use? Like the Hungary folder, default atis, etc? Whenever we delete those files the ES seems to start installation again trying to repair them. We agreed we see no reason why should our controllers keep some never-to-use ASRs from Hungary over there...

 

Thank you for info,

Pavel

 

 

Agree about the Hungary default files. They are useless.

logomail.png

Mark-Julius Pikat
Head / ATC Instructor at VACC Estonia
Mail: mark-julius.pikat [at] estvacc.org

Link to post
Share on other sites
  • 4 weeks later...

Hello Pavel,

 

My questions:

1) does ES write some stuff somewhere else than into his Program Files folder and user docomeents? I mean shall we expect something important in registry, fonts, etc. that needs to be also transferred to the end user computer?

 

I think not really. Important are the links in the .prf file to find all relevant settings. That means create a package (includes .sct. ese. prf. ase, atis and more). Furthermore you can create a easy install routine like http://www.thprogs.de/EasySetup/eng/index.htm to simulate a normal installation. Thats it !

 

2) Can we disable the default stuff which we dont use? Like the Hungary folder, default atis, etc? Whenever we delete those files the ES seems to start installation again trying to repair them. We agreed we see no reason why should our controllers keep some never-to-use ASRs from Hungary over there...

 

maybe check the setting in the .prf file.

 

Settings AtisFolder \..\YOUR FOLDER\Atisfiles.txt

 

Hope it helps.

 

Regards

Link to post
Share on other sites
  • 5 years later...
On 10/11/2014 at 5:24 PM, Pavel Brodsky 982568 said:

2) Can we disable the default stuff which we dont use? Like the Hungary folder, default atis, etc? Whenever we delete those files the ES seems to start installation again trying to repair them. We agreed we see no reason why should our controllers keep some never-to-use ASRs from Hungary over there...

As a new EuroScope user, I wanted to remove all the demo config cruft in %home%\Documents\EuroScope to have a clean slate, and stumbled over the same behaviour. The mistake seems that those demo configs are declared being part of the "software installation" when Gergely creates the MSI package, so considered "vital" by the windows MSI installer self-repair functionality.

The EuroScope start menu link is not directly pointing to the .EXE file but to a virtual application registration (that's via registry as far as I found out - not a windows admin/dev), and that makes clicking the start menu EuroScope entry first trigger MSI. That one then detects the "crucial" files having being deleted and starts the prevent-support-calls "auto-repair", restoring the demo configs.

@Gergely Csernak 904331 any chance of fixing that so that %home%\Documents\EuroScope is considered install-only (no auto-repair)?

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...