JRomManager v2.4.0

June 8th, 2020, 21:28 Posted By: wraggster

JRomManager v2.4.0 is released. JRomManager ia a Rom Manager entirely written in Java and released under GPL v3.

Current Features:
* Zip support
* Mame and Logiqx Dat formats
* Import from Mame executable
* Dat parsing caching via Java Serialization
* Optimized to permit scan over shared network
* Dir scan caching via Java Serialization based on FileMDate+FileSize, one cache file per romdir, reusable between different Dat Scans if same dir used
* Split Scan/Fix/Rebuild
* Non-Merged Scan/Fix/Rebuild
* Merged Scan/Fix/Rebuild (with choice in case of name collision)
* Full SHA1 scan or on-need SHA1 scan in case of suspicious CRC32
* Retain SHA1 in cache until zip file change
* CHD support (no separate dir from roms yet)
* Per profile settings (what to fix, how to scan, ...)
* MultiThreading support (at least for archive manipulation and checksum calculation, fast disks required)
* MD5 support (for old dats)
* 7z support via SevenZipJBinding + 7z command line as functional backup
* TorrentZip support via trrntzip command line
* Multiple Source Dir
* Enhanced Gui with Report
* Translated to English and French
* Software List support
* Filtering functionalities (clone, chds, systems list, display mode, cabinet type, driver status, ...)

JRomManager v2.4.0 Changelog:
Added full server mode
Made for an usage over the Internet (but it should be kept legal between users)
Jetty is used instead of NanoHTTPd
Multi-user with access rights, a per user WorkDir, a shared read-only space, and no access to the rest of the entire FileSystem
Totally secured (separate accounts with login/password, HTTPS with TLS 1.3, server certificate handling and auto reload, obfuscated paths, ...)
HTTP2 support (only with TLS 1.2) which permit long polling request usage in place of WebSockets without loosing too much network performance
This mode is still experimental, work still need to be made on disk/thread quotas, and a firewall with IP filtering may be required to get full control on who is attempting to connect
Implemented Long polling Request as alternative of WebSockets for simple server mode
New "Single File" mode, made for single ROM per game sets than can be kept in base directory without creating a sub-directory for each game...
Added support for import/export of settings from one profile to another
More graphical icons for tabs and buttons
Various fixes
This will be the last version supporting Java 8, next one will require at least Java 11

http://www.emucr.com/2020/06/jrommanager-v240.html

There are 0 comments - Join In and Discuss Here