DIFFATONCE STUDIO · 0.1.1 · WINDOWS X64
Software in order. Your data under your control.
Getting started and help for installing, opening and updating Prime and ResinAtOnce with visible decisions.
Versions in this release
On small screens, scroll the table horizontally to see every column.
| Application | Version | Approximate MSI size | Role |
|---|---|---|---|
| DiffAtOnce Studio | 0.1.1 | 61.98 MB | Software manager; does not compute DOSY. |
| DiffAtOnce Prime | 0.15.103 | 1.38 GB | Same preserved scientific package. |
| ResinAtOnce | 0.51.104 | 1.34 GB | Same preserved scientific package. |
1. Read the status, not just the button
Studio checks the catalog at startup and every four hours while it remains open. Check for updates repeats the check. The date and message identify what was verified, not just which cards are displayed.
- Verified signed catalog: signature, expiry and sequence were accepted using the previously distributed public key. MSI files must still pass their own checks before installation.
- Unavailable, offline or rejected catalog: retain the warning. That status does not establish that no newer versions exist, or turn a cached copy into a fresh check.
- A card may represent an MSI application, portable copy, online service or official page. Only available MSI releases offer managed installation; an installer is not invented to fill the catalog.
Limit to retain: Do not accept a key proposed inside the same catalog it is meant to verify. Catalog integrity and signing are neither Authenticode signing nor scientific validation.
2. Install without conflating MSI and portable
Use the official Studio page to download installers. Save open work and retain a copy of your projects before changing versions.
- Install and open Studio. Choose Español or English, find Prime or ResinAtOnce and open Details to inspect version, location and provenance.
- If the local MSI is not found, select it in Open catalog / MSI. Selection does not install: Studio accepts only a package matching an included or authenticated release.
- Select Install and review the confirmation. Product, version, MSI identity, size and SHA256 are checked before Windows Installer runs. The actual installation is checked afterwards; a completed download is insufficient.
- MSI installation uses a fixed per-user directory. A portable copy remains a separate copy: Studio can open it but does not automatically convert it or migrate its identity. The new path may require registration or activation through the normal workflow.
Limit to retain: Keep every file when using a portable distribution, not just its EXE. Do not delete an identity or copy credentials to bypass registration. Windows-copy registration and the online-laboratory account are different mechanisms.
3. Update explicitly
A newer release is shown on the card and in filters. Updating requires confirmation: checking the catalog installs nothing.
- Save projects and close the application you intend to update. Studio does not forcibly terminate it or save a project on your behalf.
- Review current version, new version and notes. Select Update, or Update all for a sequence of available updates. A failure stops the sequence; remaining applications are not presented as updated.
- Wait for download, verification and installation. After a failure or cancellation, inspect the actual installed version and retain the log rather than inferring success from a progress bar.
- To update Studio itself, close the manager and run its verified MSI. This version does not replace the Studio executable while it is in use, and does not automatically downgrade.
Limit to retain: Reboots are not forced. If Windows reports one is needed, save your work and decide when to restart. Four-hour checks run only while Studio is open; no invisible resident service is claimed.
4. Download, installation and Cancel
These are separate stages. Cancelling a download is not the same as interrupting a Windows Installer transaction.
- Before MSI begins, you can cancel a download in Studio. An incomplete file is not used as a verified installer.
- During MSI, Studio’s download-cancel control is disabled. Windows Installer displays its own Cancel button; Studio waits for its terminal result and does not kill the process.
- Do not terminate MSI processes in Task Manager to “speed up” an update. If Windows Installer is already busy with another program, allow that operation to finish; Studio has no authority to remove it.
Limit to retain: The final test observed the Cancel button, but its finite pause completed before a cancellation was recorded: button-driven rollback was not established. That limitation is retained rather than presented as a passed rollback test.
5. What is preserved and what is not migrated
Studio manages software, not research results. The Prime and ResinAtOnce installers contain the same verified scientific files as their current application versions.
- Installing or checking updates does not recalculate DOSY/MwOSY, change TTMS or temperature, or turn an earlier map into a new review.
- Retain project or batch, reviews, sources, calibrations and reports. Before updating, export what you need and verify that your copy can be opened. Another tab or folder does not replace a checked backup.
- Uninstall is offered only for a verified managed MSI installation. It is not an instruction to remove portable copies, projects, results or identities outside the installer. Projects are managed in the scientific application.
Limit to retain: Studio 0.1.1 includes self-contained .NET 10.0.15. Prime and ResinAtOnce retain their historical .NET 8 runtime: support ended on 10 November 2026 and migration requires a separate scientific audit. Migration of the entire suite is not claimed.
6. Integrity is not a Windows signature
The catalog uses RSA-PSS/SHA256, a trusted public key distributed in advance, expiry and an increasing sequence. Each MSI has a specific identity, version, size and SHA256.
- Do not ignore an expired signature, rejected sequence or different hash. Retain the warning and obtain a reviewed official distribution; do not edit the catalog or rename another file to force acceptance.
- Current MSI files have no Windows Authenticode signature. The catalog key is not an Authenticode certificate and does not remove Windows or SmartScreen warnings. No certificate has been purchased and no computer security policy changed.
- The publishing private key is neither distributed with applications nor uploaded to the website. Only its public part is published; Studio does not ask you to enter a publishing password or private key.
Limit to retain: Do not disable Windows protections or accept an unknown key to continue. Package integrity, installation, numerical agreement and experimental validation are different checks.
7. Resolve the specific status
Retain the literal message, product and version, action and failure stage. Operation and installation logs are not scientific results.
- MSI not found: select the official package through Open catalog / MSI. A file without a matching release is not installed merely because it has an .msi extension.
- Application running: save and close that application, then retry. Installer busy: allow the other installation to finish. Catalog unavailable: check connection and official status; do not interpret it as “no newer versions”.
- Installation not confirmed: review Details and the version that actually opens again. Retain Studio and Windows Installer logs. Send Support only the minimum authorised material, without passwords, keys, tokens or confidential results.
Limit to retain: Do not delete standards, identity or projects to fix an installer problem. Studio has no automatic results cleanup at startup or during a calculation.