New file structure　Old offline version/full version

Versions after 0b180

Compatible startup program and new program

　From 0b180, the file structure has changed from before.

　The executable file up to 0b178 has been replaced by a small program that maintains compatibility, and the main program has been moved to a new file name structure.
　When updating service registration and execution paths using updaters or installers, compatibility with the old environment will be maintained.
　However, updating using a ZIP file is only for core users as it requires some work to match the specifications.
　If you use the updater or installer, you can continue using it without any additional work.

　List of old file names (startup file names for compatibility)

　　thilmera7.exe, thilmera7s.exe　(32bit)
　　thilmera7_64.exe, thilmera7s64.exe　(64bit)
　　thilmera7_64arm.exe, thilmera7s64arm.exe　(64bit-ARM64)


　List of new file names

　　thilmera7-win32.exe　(x86-win32) (32bit)
　　thilmera7-win64.exe　(x86-win64, AMD64) (64bit)
　　thilmera7-arm64.exe　(arm64, AArch64) (64bit)


Changes in ZIP distribution

　Old files will no longer be included in ZIP distributions after 0b180.
　With ZIP distribution, it is not possible to control the files to be extracted, so it is extremely difficult to know which one to run.In order to avoid extracting 9 program files, the ZIP distribution is newly created for each architecture. There are only three files.

　Therefore, overwriting an existing environment from a ZIP distribution is for more advanced users.

Steps to take if you absolutely must update using ZIP distribution

　As an update to the existing environment, simply overwrite the contents of the ZIP and run the old file that was there. Or, if you start it from a service, an unstartable error will occur due to a resource file mismatch.
　In this case, if it is a recent version, you will be asked whether or not to call the updater, but this is not a bug.
　ZIP distribution does not update the old configuration files and old mismatched files remain, so services and program files must be manually deleted. Please understand this before proceeding.
　After overwriting, the executable file with the old configuration cannot be started.

　When using ZIP for updates, once the service is registered, delete it instead of stopping it and overwrite the contents of the ZIP.
　After that, delete the six programs with the old file names above and start the program that matches the environment. Restoring service registration, etc.
　Basically, the file structure is for all architectures, so running thilmera7-win32.exe will launch the one appropriate for the current architecture.

Changes in updater

　The specifications are currently under construction.

　After 0b180, when the updater is run, if there is a program in the old configuration file, the updater will overwrite the compatible program instead.
　If there are no old configuration files in the destination folder, the updater will only extract the new configuration program.

　Also, the updater defaults to the "current architecture", and if it is executed as is, a different architecture (for example, a 32-bit executable file in a 64-bit environment) that does not have an old file will not be expanded.
　If you are installing it for the purpose of copying it to some other environment, you must use the "All architectures" setting.
　If the updater is called from the program itself and a file with an old configuration exists, it will be in "all architectures" mode to maintain compatibility, and different architectures will also be expanded.

　For existing users, updating with the Updater is specifically designed so that this migration does not require any effort, but rolling back to the old file configuration will not process files in the new configuration.

　If you have any problems with this, please report them.

---

Versions up to 0b178

Offline only version - 7n (normal version)

　The offline-only version is based on the old normal version (7n), and when it became completely freeware in 2022, there were cases where existing users had registered the program as the program destination for the service, so it could not be deleted, so it was changed to 「offline」 as a temporary measure. It remains as a special edition.

　After it becomes completely freeware in 2022, it is designed with the assumption that the full-featured version (7s) will be used, so if this offline-only version is not installed in the mode that creates shortcuts with the updater, To start it directly offline, you need to manually create a shortcut.

　The installer always creates shortcuts, so you don't need to create them manually.

　If you run it without passing the offline parameter, it will run by calling7s. (This behavior is currently undesirable, but it is due to the migration of users before and after becoming freeware.)
　However,7sIf the version cannot be checked during execution in an offline environment, 7n will be called after a while and execution will move there.

Full-featured version - 7s(sPherTia version)

　Originally, it was launched with the aim of reducing the high cost of digital signature fees, and was a "campaign benefit version" for those who donated.
　At that time (2011) in Japan, individuals could not receive donations, and even if it was actually a donation, they had to provide some kind of compensation, so they donated. It was positioned as a "formal complimentary version" in which a license key was issued to a person and could only be used with that key.

　However, as many years have passed, the difference between the functions of the normal version and the promotional version, which was just an error, has become larger, and even though it is freeware, it has become like 「If you want to use this function, you have to pay.」 Things that were kept in place were out of line with the purpose and purpose of the development.
　Considering the changes in the situation since 2011, I announced that it would become completely freeware in January 2021, and in January 2022, the standard has changed from 7n to7s. Ta.

　This version is currently used, and all others are exceptions. It is designed as follows.

Q: How can I check whether I am running the full version or the offline version?

If the main window attribute information is valid, THILMERA 7 S will be displayed on the left, and if offline, THILMERA 7 N will be displayed.
If the attribute information is not valid, the offline version always displays thilmera is offline in reverse color.

Q: I want to start the offline version (7n) directly.

If the installer or updater created a shortcut, start from the one with (offline) at the end.
If the shortcut is not generated, thilmera7.exe in a 32-bit environment. AMD thilmera7_64.exe for 64 environment. If you are using an ARM64 environment, create a shortcut to thilmera7_64arm.exe and add offline to the parameters.
The reason these steps are necessary is that when I made it completely freeware in 2022, existing users registered the program as a service and could not delete it, so although I left it as an offline version, it is currently used by7s. This is because it is designed with the premise that it will be used.
Offline mode will be integrated into7sin the future.