Releases: MarkBaggett/srum-dump
SRUM-DUMP 3.2
This is a minor bug fix to address issue #44
SRUM-DUMP 3.1
This is a minor bug release. It addresses the following issue:
SRUM-DUMP 3.0 Release
This is the official release of SRUM-DUMP 3.0.
3.0 BETA#3
This is the third BETA release of SRUM-DUMP.EXE version 3. At the moment I think it has all of the functionality of the latest verion2.
Please check https://github.com/MarkBaggett/srum-dump/issues for known issues and enter new issues as you identify them.
Version 2.6 Bloodier Sport
11-24-2023 Version 2.6 - Bloodier Sport
Happy Thanksgiving
- Added retry on database operations. Unsure of the cause but sometime the libesedb engine raises a traceback when retrieving information from the ese table, but pausing for a second and trying the same query again fixes the issue. Now I retry 5 time with a 0.1 second pause before allowing the error to be raised. (Einstien was wrong. Trying the same thing over and over sometime yields different results.Then again, I can't rule out insanity.)
- Keeping Red color scheme. People seem to like it.
- Tested on Windows 11 22H2 build 19045.3693,22621.2715 and Windows 10.0 Build 10240
- Built with Python 3.12 and pyinstaller 6.2.0
Version 2.5 Bloodsport
4-13-2023 Version 2.5 - Bloodsport
- Several Template enhancements by Yogesh Khatri
- Updated ESE Database engine to latest version
- Change Color Scheme to Red.. aka Bloodsport
- Tested for Windows 22H2 build 22621.1555 and below
2.4 Kayak
This release addresses changes in the Window 11 registry. It is backward compatible with prior releases.
2.3 TanBlue
This is just a rebuild of the previous version of code with an update to underlying modules. The old version would crash with an error about not being able to read the number of records because of an error in one of the underlying modules. Initial testing of this rebuild shows that it does not seem to suffer form the same problem.
Test Build of latest binary
This is a test rebuild. No code changes. Just updated the underlying libraries and rebuilt the exe.
I am hoping this resolves the issue reported by @MRandol and @nurajbihari in issue 27.