Repository navigation
MineMaster 1.4.9
MineMaster 1.4.9
- Update SRBMiner-MULTI from 3.6.7 to 3.7.0 on Windows and Linux x64, with verified archive and runtime-file hashes. Upstream changes include Quantus compatibility/performance work, Pearl improvements and Intel Arc Quantus support. Actual gains depend on hardware and drivers; no performance benchmark is claimed.
- Nanominer 3.10.0 and XMRig 6.26.0 remain the latest official stable releases as checked September 29, 2026.
- Package only current, verified miner runtime files and supplied notices. Exclude obsolete cached versions, optional drivers and unrelated files. Verify the packaged Windows/Linux file lists and hashes before publication.
- Check official latest stable miner releases before publishing a client release. Fail clearly if pins are outdated or upstream assets cannot be verified; do not automatically change binaries.
- Correct Nanominer pool endpoint and reconnect reporting, retaining original observation times.
- Include up to two recent failed managed-file/archive paths in explicit Windows history checks, and show the exact checked paths in admin/client diagnostics. Checks remain read-only and never change protection settings.
- Preserve file inspection failure details through launch preparation and identify config/log/directory write failures separately from executable launch failures.
- Derive admin/client SRBMiner version labels from the shared catalog.
- Correct AMD integrated-GPU inventory and reject placeholder PCI addresses as stable hardware identities.
- Detect parent-process exit before output-handle closure; block duplicate starts, repairs and updater handoff while descendant/process closure remains uncertain.
- Show automatic-install behavior and paused-install errors in the admin/client. A newer Stop cancels update preparation.
Supported clients on 1.4.9 automatically install verified downloads, safely stop mining, restart and resume previously running enabled processes. Failed/canceled attempts require an explicit retry. Older clients require one installation request to adopt this behavior. No forced fleet update, mining action, repair, profile change or antivirus modification is part of this release. Custom executable paths remain operator-managed.