I've finally got a new build compiled. Hopefully, this fixes the problems with importing INI values. Now we are hardcoding them in a separate source that will also create an INI file. The next phase will be making sure that all defined constants from this file are working properly. This will include URL's for websites, runtimes, and wiki; as well as icons, emulator and filetype descriptions. The custom install screen still doesn't show up yet. The new [CODE] section can get beta-tested for functionality and further development. There have been so many changes under the hood of the entire installer design, too many to list. This is why EmuPack is being brought into the modern age via version 2.0
I've finally gotten a build to compile and I'm assuming there are many bugs in it. Mostly with how variables and constants are declared as well as probable issues with importing INI information. As such. this is something more important to test out for those who are willing to provide feedback.
The worst bug I've found so far is that INI information is not being pulled into the installer during compilation so the dialog with file associations appears somewhat blank. I know I went through this the last time I was upgrading the code and still have to figure out a solution.
I am still trying to correct code while implementing new code. Seems to be going ok for such a major overhaul. There have been a lot of changes in the emulators and their runtimes, so some things are being removed while others are being added. There are still a lot of emulators that I'm looking for updates to, but not all of them can support legacy systems. Not sure how the system registry is going to be affected. I'm getting the setup to pull information from an INI file instead of being hardcoded because condensing things that may change makes sense. I'm getting closer to being able to compile a beta build. There are still lots of things that need double-checking for updates. Hopefully, make sure the new version will properly handle legacy runtimes. The next version should be capable of downloading and updating runtimes and sideloading offline redists (as long as the location and naming are as specified).
Also worth mentioning is that the EmuPack Lite version is going to be the public release version. It should be able to download anything that is not already supplied in order to bring down the download size. A 'Full' version would have redists available sideloaded in runtime folders outside the main setup. This option would not guarantee up-to-date runtime files, however, Windows Update will generally take care of that.
I am still trying to correct code while implementing new code. Seems to be going ok for such a major overhaul. There have been a lot of changes in the emulators and their runtimes, so some things are being removed while others are being added. There are still a lot of emulators that I'm looking for updates to, but not all of them can support legacy systems. Not sure how the system registry is going to be affected. I'm getting the setup to pull information from an INI file instead of being hardcoded because condensing things that may change makes sense. I'm getting closer to being able to compile a beta build. There are still lots of things that need double-checking for updates. Hopefully, make sure the new version will properly handle legacy runtimes. The next version should be capable of downloading and updating runtimes and sideloading offline redists (as long as the location and naming are as specified).
Also worth mentioning is that the EmuPack Lite version is going to be the public release version. It should be able to download anything that is not already supplied in order to bring down the download size. A 'Full' version would have redists available sideloaded in runtime folders outside the main setup. This option would not guarantee up-to-date runtime files.
Trying to understand PASCAL has been strangely challenging. It was easier to adapt Java to LUA.
It's not going to compile correctly, but I'm asking for help.