Backport Configurations Files

Backport Smode Beta configurations to a Stable Smode version

When you finish participating in a Smode Tech Beta program and want to switch to a new Stable release (which includes all validated code fixes and provides long-term support),
you may lose your current Smode Beta configuration settings from the Preferences panel.

This happens because Smode does not allow loading configuration files created with a newer version, and Beta versions are always considered “future” versions of the latest Stable release, even if their features eventually become part of it.

Smode versions are versioned differently for Beta and Stable:

• Beta versions use an internal patch numbering system that increases with every new fix or test.
• Stable versions group multiple validated fixes into a single patch release.

For example:

• If you used Smode R13.100 (Beta) during the Beta phase, it will be followed by a Stable release named R13.4.
• Likewise, in the legacy versioning format like Smode 10.2, the Beta version 10.2.100 was followed by a Stable version 10.2.4.

Because Smode doesn’t load configuration files created with a “newer” version, it sees the Beta version (e.g. R13.100) as more recent than the Stable version (e.g. R13.4), and ignores its configuration files.

To workaround this you have two choices:

1. Discard your beta configuration:
   do nothing or to avoid surprises during next beta testing, delete all file named *_13_100.configuration from the folder
   %AppData%\Roaming\Smode <EditionName>\configurations
   Next Smode R13.4 will automatically port Smode R13.3 configuration files (or previous one if not present) at first boot

2. Keep your Beta configuration in new Stable Smode version:
   Before Smode R13.4 first boot, manually rename all *_13_100.configuration into *_13_4.configuration from the folder
   %AppData%\Roaming\Smode <EditionName>\configurations