Screen Shot

Downloads:
RomVault (2.2.6)

Others:
TorrentZip File Format
7-Zip File Format

Contact Me

Also find me on IRC:
irc.foreverchat.net
#ROMVault

You are Visitor:
url and counting visits
Since: 01/01/2016
 

For a very quick 'How to use RomVault' Scroll down to the very bottom. (Read April 12,2010 post.) or watch This YouTube Video

May 19th, 2016

The Multi threaded checking is now getting to a good stable point so I have put out a new full release V2.2.6.

February 12th, 2016

Finally got around to catching up a little on some other peoples fixes and improvements to RomVault. So here is a test build V2.2.5 it has a few small bug fixes, and the big new changes thanks to edc's input is some multi-threading file hashing, which should give a new speed boost to scanning your files. If this version looks good, I will promote it to the official version in the next few days.

To keep up with all the changes you can head over to the source code on GitHub

January 3rd, 2016

Happy New Year

January 27th, 2015, ROMVault 2.2.1, Linux Compatible Release

So RomVault development had gone quiet for a while, but during this time some good things have happened, the first thing is that for a while now ROMVault has become an open source project. You can now keep up with the latest code at:
GitHub RomVault Repository

And with it now being open source a big thanks goes out to my friend Ack for picking up the code and working on making the needed changes to get ROMVault running on Linux, You need to be running 'mono 3.10+' for it to work. I hope it will not be to long before more good things happen with ROMVault development.

Just so there is no confusion: This is a standard Windows .NET release of ROMVault, compiled to run on your Windows PC just the same as any previouse release. The difference is that this same .exe file will also run on Linux using Mono to run a .NET exe file in a linux OS, There are some code changes in the .exe that detect if you are running Windows or Linux, and then some alternative internal functions are used depending on which OS you are running.

April 22th, 2014, ROMVault 2.1.24

Quick update today, Fixed a couple of bugs in DAT loading, and added a couple of new Meta Data Items for Trurip DATs

March 4th, 2014, ROMVault 2.1.23

Happy Fat Tuesday, and here is a quick bug fix update, fixed a couple of bug that caused the fix engine to crash when fixing files.
Fixed renaming a file if it was needing the case of some characters changed.
Fixed moving files out to ToSort

January 27th, 2014, ROMVault 2.1.22

Update1:
Fixed a couple of Bugs. Corrupt CHD's where missing some fix cases, so these should be handled correctly. Also speeded up rescanning directories that contain a lot of files. (not zips).
Update2:
So it turned out that after fixing the CHD bugs in 2.1.21, I looked a little further into the code and fixed a couple more CHD fixing related issues. So here is the next update.

January 7th, 2014, ROMVault 2.1.20

HAPPY NEW YEAR.
And after much searching and trouble I believe I have finally tracked down 'comparing null ulong?' error.
You had to have:
a) a missing CHD file that did not give a SIZE in the CHD DAT
b) a missing ROM file that was zero length and so no CRC supplied in the DAT
c) have a fix for the CHD
d) have the order of things so that the CHD would be fixed before the ZERO length file.

And then you got the ulong? error message.
Anyway finally tracked that one down, and put the correct checks in place to handle missing Size/CRC information better.
So go grab 2.1.20, and keep on fixing.

December 23th, 2013, ROMVault 2.1.19

A few more bugs have been coming in with the new version, so a new fix release is already here.
Fixes:
Handles Missing DATRoot directory cleanly now.
Added some better error handling to find the ulong null problem
Ignored files being set to incorrect status on Cache Load
Error opening CHD file (): decompression error

Please update asap.

December 20th, 2013, ROMVault 2.1.18

Already fixed one bug caused by not having a ROMRoot directory setup when you try and run RV, and trying to track down another bug.
If you have been getting the error message 'comparing null ulong?' please download and run this version.
I do not understand what logic is leading to the reason this message is being displayed. So this version will send me a more detailed message about it.
If you are at the point where you can reproduce this error repeatedly, please get a hold of me, I would really like to get to the bottom of this one ASAP.

December 19th, 2013, ROMVault 2.1 Release

Merry Christmas

After a lot of work and testing over the last few months I have decided it is time to release 2.1 of ROMVault.
The big new feature of 2.1 is CHD file support. You will need to have chdman.exe in the same directory as RomVault21.exe for the full CHD support to work.
But there have been many more smaller fixes and improvements made, such as continuing to scan passed locked files. (Files locked by other applications accessing them.)
There is also improvements made to the ZIP reading code, that should be compatible with a few more rare zip formats.

What is NOT yet in ROMVault 2.1 is 7Z support, I started adding 7Z support and got a long way into it, but then started running into problems with the way the fixing core was working with 7Z. So for now the 7Z code is not in this release,
I instead worked a lot on trying to get the existing code as stable as I could.

So before I get into another big development cycle to rework the core for 7Z I wanted to get a release out now as I believe it is a lot better than the current 2.0.10 code.
There are a couple of strange crashes I see once in a while, and so this version has some improved error logging so I hope to get these tracked down soon.

A few other notes:
The cache file has changed in this release, so your old cache files will not work!! You will have to re-scan all of your files with this release!!
ROMVault 2.1 will make a new cache file called: RomVault2_7.Cache (This is actually my internal version 7 of this cache file, so that explains the 2_7)

If ROMVault does crash is does send me a log of the crash report, this has helped me track down many bugs in the past, this is also why I ask you to enter your name and email before using ROMVault for the first time.
This way I can contact you back to try and find out more details about crashes I see.


May 23th, 2013, ROMVault 2.1

Been a while since my last update so I thought it is about time I checked in with an update as to what I am working on.

The 2 main things I am focusing on are 7Z and CHD support, and the good news is both are coming along well, and both work to a degree.

It has been interesting developing ROMVault now that I have publicly released it, in that I can many times get a version of RomVault together that works well for my own use and as I know the limits of what it can do and what will break it, it works well for my needs, the thing is taking ROMVault to the next level were it will keep working with everything that anybody else can throw at it is another completely different level of developmental robustness and sometime that part of developing is not much fun and not the rewarding part.

So as this is at the end of the day just a 'fun' personal project of mine, sometimes I need to take a break and just work on it for me and keep it fun, which is kind of where I have been for the last couple of months.

So like I said 7Z and CHD support are kind of working, and I will be spending the next while here getting it as robust and possible more efficient before the next public release of ROMVault.

Here is a screen shot of the latest code, converting zip files to torrent7zip files.


Click on the image for full screen version


February 23th, 2013, ROMVault 2.0.10

Fixed one new bug introduced by the addittion of the <clrmamepro forcepacking="unzip"> code, that was causing an error when trying to fix a zero length file.

February 7th, 2013, ROMVault 2.0.9

Couple more bug fixes.
Bugfixed: Fixed the 'Unknown double check delete status MoveToSort' bug.
Bugfixed: Fixed the negative totals being reported in the ToSort directory.
New: Added support for <clrmamepro forcepacking="unzip">

January 26th, 2013, ROMVault 2.0.8

Just a couple of small bug fixes today.

January 19th, 2013, ROMVault 2.0.7

Lots of things new and improved in this release. Read the what's new to see.
I have now released an Images.zip file that if left in the same directory as RomVault2.exe will be used to supply the images to RV.
This means that if somebody would like to pick these up and work with them and make me a set of Color Blind friendly version of these icons, that would be great.

January 14th, 2013, ROMVault 2.0.5

So in 2.0.3 I fixed the code so you could be offline with RV2, but it looks like there was still a problem if my update server is offline, so 2.0.5 should just keep on going either way, also fixed a bug in the miss-list reporting that was crashing RV.

January 11th, 2013, ROMVault 2.0.4

Woops let a new bad bug slip into 2.0.3, so is fixed now in 2.0.4, you should now not get the "Could not find self" error message while deleting empty directories.

January 10th, 2013, Again, ROMVault 2.0.3 Bug Fix Release

So you may have noticed that ROMVault 2.0 now asks you for your name and email address, (If you did not fill this in please go to Help->Registration and fill it on.)

The reason is that ROMVault 2.0 now automatically sends me a report any time an error message or crash occurs, it also sends a message if there is a problem reading a DAT file. So I have already been getting plenty of good crash reports, and emailing people to find out what there where doing to make them happen, and so thanks go out to all those who are already helping make ROMVault 2.0 Better.

This also explains the reason why so many quick fixes can be made right now.
So here is another update with a few more fixed, check the whats new doc to see what has changed in 2.0.3

January 10th, 2013, ROMVault 2.0.2 Bug Fix Release

Fixed a bug where a zero length file would match a No-Dump file and cause pop-up error messages.
If you have been seeing an error that looks like ", ZipFile , InDatBad , Got from: Error to: Error", then get this update, and re-scan your roms.

January 9th, 2013, ROMVault 2.0.1 Bug Fix Release

As I like to say... Another day another set of bugs, so here is 2.0.1, fixes and add a few things. I am going to try and maintain the whats new doc, but I am not very good at keeping these things up to date.
Also another new feature in RV2 is unicode support.

January 8th, 2013, ROMVault 2.0.0 Officially Released

Hi,
So around August time of 2011, I was working with the code of RomVault 1.7 and was starting to get frustrated with the direction it was heading. The biggest problem was that the core data structured used internally by RV1.7 was based around trying to look like the list of DAT that it scanned in from DATRoot. This sounds correct but I was running into problems like this: where do I store the information about any files I find in a directory that is not in one of the DAT directories. The scanning code was starting to do more and more fixing, so that it could complete a scan, like copying unknown directories and files over to ToSort. Also as I am sure all you RV1.7 users know, there was no clean way in the data structure to store the status of the Tree of DATs as displayed in the UI, so it kept on resetting itself, as it was not really a tree structure at all, just a list of DATs displayed as a tree. This was all heading in the wrong direction fast.

So I realized I had the change the core data structure, as what I am really working with is actually not DATs, I am really processing a structure of Files and Directories. (The DATs are just a way of representing the list of files you want to collect.) So I started to rework the core data structure to be a structure that would hold a tree of Files and Directories, and at that time back in August 2011, I figured a couple of months of work, build the new core structure, put all the old scanning and fixing code back on top of it and RomVault 2.0 would be ready to go.

The new core data structure was made, and then I converted over the DAT loader, and then got the File scanner going, and everything was going along good and then I started working on the Finding Fixes code, and then got into a world of CRC's, SHA1's and MD5's, it was probably around 10 months ago we (that’s me and my great Beta testers) realized that just fixing on CRC’s and file size alone was not going to cut it. So after a couple more month Levels of scanning and fixing where born, and then after a few more months Levels of scanning and fixing where about working, and then the improved DAT loader was developed, and oh yes, the Missing report code was never converted over, and then the idea of supporting filenames greater than 260 characters came along, and fast Zip processing was added………..

You get the idea, the project just kept on snowballing. So here we are today around 16 months later, with what is RomVault 2.0.0, with 40'ish private Beta version being tested, about 300 check-ins to the source control. (So that works out at about one check-in every 1.5 days for over 18 months!!!,You did already click on that Donate button over there of the left, I hope.)

Is RomVault 2.0.0 finished? No, nothing is ever finished, there is a great big list of things still to be added to it, but it is a great big step up from 1.7. So before you ask there are 2 things still at the top of the to-do list, so Sorry, there is still no 7z support, and still no CHD support. But I will put this another way, neither of those 2 features would ever have fitted into the 1.7 data structure, and so also look out for the 2.1 development cycle starting. (As I actually already have a private test version of RomVault that does to a limit degree support 7z.)

So you need now to know a little about scanning levels, and how RV works.
First you need to know what a CRC32 is, and to put this as simply as possible it is a 4 byte, 8 digit (in hex) hash of your file, ZIP uses and stores the CRC32 of your file when you put a file into a ZIP, this way when it extracts your file it rechecks the CRC32 to see that your file did not become corrupt.

And here is an old DAT file game description, showing the crc values of the files needed for this game:

game (
   name 2020bb
   description "2020 Super Baseball"
   romof neogeo
   rom ( name 030-p1.bin size 524288 crc d396c9cb )
   rom ( name 000-lo.lo merge 000-lo.lo size 131072 crc 5a86cff2 )
   rom ( name sp-s2.sp1 merge sp-s2.sp1 size 131072 crc 9036d879 )
   rom ( name sfix.sfix merge sfix.sfix size 131072 crc c2ea0cfd )
   rom ( name 030-s1.bin size 131072 crc 7015b8fc )
   rom ( name 030-m1.bin size 131072 crc 4cf466ec )
   rom ( name 030-v1.bin size 1048576 crc d4ca364e )
   rom ( name 030-v2.bin size 1048576 crc 54994455 )
   rom ( name 030-c1.bin size 1048576 crc 4f5e19bd )
   rom ( name 030-c2.bin size 1048576 crc d6314bf0 )
   rom ( name 030-c3.bin size 1048576 crc 47fddfee )
   rom ( name 030-c4.bin size 1048576 crc 780d1c4e )
)

So this CRC32 numbers become a finger print of your file, and RV1.7 used the CRC32 it found in the zip file header and file size to identify your files, so if you have a file in ToSort RomVault would look at the header of the zip file and read all the CRC’s and Sizes from that zip file and if a DAT requires a file that matches that CRC32 and size, then RomVault would move that file from ToSort to the correct zip file as described by the dat.

This is all super-fast an easy as the CRC32 was right there waiting for me to look at in the zip file information.

But here started the problem, the more files you start to compare this way you realize that CRC32 is really not enough, which brings us right up to date with the very latest TOSEC dat sets:

Commodore C64 - Games - [D64] (TOSEC-v2012-12-22_CM).dat

game (
   name "Elvira - The Arcade Game (1991)(Flair Software)(M3)[cr MHI][t +2 MHI][a]"
   description "Elvira - The Arcade Game (1991)(Flair Software)(M3)[cr MHI][t +2 MHI][a]"
   rom (
     name "Elvira - The Arcade Game (1991)(Flair Software)(M3)[cr MHI][t +2 MHI][a].d64"
     size 174848
     crc 298caa9c
     md5 71700ed3cf36b0724e0dd8e68fe32ed9
     sha1 0dde6ccb17ed13c05f7f3a03ee6d636f5ba56545 )
)


game (
   name "Jimbo (1995)(CP Verlag)[cr FLT][a]"
   description "Jimbo (1995)(CP Verlag)[cr FLT][a]"
   rom (
     name "Jimbo (1995)(CP Verlag)[cr FLT][a].d64"
     size 174848
     crc 298caa9c
     md5 92e4a98d8d9c2234c066124765a5192e
     sha1 ba3eb11347d159951d94d7a34a3d08c40b6d009c )
)

Two files from the Commodore C64 set, and as you can see they both have CRC of 298CAA9C!!!
Our system fails, CRC is not enough, and so bring on SHA1 & MD5 two other hashing methods, and as you can see much bigger longer hash values with an almost infinitely small chance now of the SHA1 checksum failing to be the correct file finger print.

So now back to RomVault 2.0
Level 1 scanning: still just scans the CRC/Size right out of the headers of the ZIP files, this is super fast, and if you just want to fix a mame set as quick as you can and are about to join the next mame torrent which will fixing anything that may be wrong anyway, then this is still probably enough for you.

Level 3 scanning: this then gets the full set of CRC,Size,SHA1 & MD5 of every file it scans which is unfortunately much much much slower that the quick Level 1 scan, as is has to fully extract every file out of every zip file and perform all of the checksums on every file. (RomVault 2.0.0 does do all of this in memory, so it tries to be as fast as it can.) But does of course guaranty all your files are truly correct.

And then the better Option:
Level 2 scanning: (USE THIS ONE) Level 2 scans every file just the same as Level3, getting and checking the full set of CRC, SHA1 & MD5, and the first time you run a Level 2 scan it will take a very long time, but it also stores the file time stamp of your zip files, and so the second time you run a scan it checks the file time stamp, and if the file has not changed then it does not recheck it, so the second time around it actually goes super fast again, only slowing down to read any new or changed files.

There is also Level 1,2 & 3 fixing, which sort of works the same as scanning.
Level 1 fixing, only fixes comparing Size and CRC.
Level 2 fixing, compares size,CRC,SHA1 & MD5, but will still copy the raw uncompressed data from one zip to another, for speed if it can.
Level 3 fixing, compares size,CRC,SHA1 & MD5, but will uncompress and recompress every file every time.

So with all that said, use LEVEL 2 Scanning, and LEVEL 2 Fixing, and your future should be good.

That’s enough I am done with the introduction, download it, have fun, and I will probably try and make some new videos before to long.


November 13nd, 2012

It may not feel like much is going on with RomVault these days, but I want to let you all know I have been very hard at work on RomVault 2.0 and it is coming along very well, so stay tuned.
Also please check out our new page over at www.facebook.com/romvault

September 2nd, 2012

I have created a how to use RomVault to join a pleasuredome mame torrent video:

Please email me if you watch these videos and find them usefull

July 19th, 2012

Big THANKS go out to emuDrache for him offering to host www.RomVault.com, These pages should be faster loading and more available now. (Thanks again)

June 8th, 2012

Just updated RomVault to Version 1.7.1, it fixes the bug where the first character of the directory and filenames are being lost in the ToSort Directory if you have set your ToSort Directory to point at a root directory (Like D:\)
Also, I know I have been quiet for a while, but I am still working hard on RomVault 2.0, but still need to find time to get this to a point where I can get a beta version out to some people. (If you want to be a 2.0 beta tester let me know.)

February 7th, 2012

Here is a new release of RomVault (Version 1.7) It adds larger file support. Using Zip64 You can now store files bigger that 4Gb. It also fixes a DAT scanning issue where .DAT files are being release with a .XML extentions. The link for this download is over on the left.

January 21st, 2012

For anybody interested in the inner workings of a Torrentzip file I have written a document explaining the torrentzip standards. You can download it here.

December 3rd, 2011

Had a couple of bugs show up in the last few days, so here is a quick bug fix release. Please update to version 1.6.6 using the link on the left.
Fixed a problem scanning MESSXML DATs and Fixed a problem fixing files if the zip was in a sub directory in ToSort.

December 2nd, 2011

I have created a how to use RomVault Video:


November 11th, 2011

Welcome to 11-11-11, and welcome to TOSEC's newest update. I have updated the TOSEC links on the left with the newest DAT's structured ready to be dropped into your RomVault DatRoot Directory.

May 10, 2011

There was a bug in 1.6.4 that was giving a "Can not create a file when that file already exist" error when moving files out to the ToSort directory.
I have fixed this bug in 1.6.5

April 27, 2011

Turns out there where still some problems with the file copy/move code across drives. So 1.6.4 should now fixed this.
(What does this mean.?)
It means you can now right click on the ToSort directory (in the Dat tree) and set it to a location on a different drive, and things should all keep working.

April 25, 2011

Another day, another update.
Thanks to everybody who has ever sent me crash reports. I do look at them, and here is an update directly as a result of them.
This version 'should' be a lot more stable when fixing roms. I have added a lot of file checking, and handle unexpected results much better now.
Also I fixed the problems of moving unknown directory if the Tosort directory is on a different volume from the RomRoot directory.
So go download 1.6.3 and let me know how it goes.

April 24, 2011

Updated my TOSEC DATS to the current 2011-04-07 sets.

April 23, 2011

Fixed a couple of bugs:
   Was ignoring Character Case's when scanning, So if you had the correct file but the filenames case was wrong like 'fr' instead of 'FR' it would report this as correct.
   Removed extra spaces and the '.' character from the end of rom filenames.
Go grab 1.6.1 from the link on the left.

March 29, 2011

Just passing this job opening along. (Job is located in Davenport, IA, USA.) C# Rhino Programmer needed.

Feb 25, 2011

So here is a big update. Version 1.6 now supports TorrentZip files. What this means, is that every Zip file that RomVault makes will already be TorrentZipped.
There are some other options added if you are not needing TorrentZip support. Click on Settings and you will see a new dropdown:

1) TorrentZip all files (Default): This will make all new files TorrentZip'ed.
2) Fastest: When moving a file from one Zip to another, it just copies the compressed raw data, which is very fast, but if you source zip is not compressed the destination file will also not be compressed.
3) Highest: This re-compresses every file that is moved using slightly different compression from torrentzip which in many cases compresses just a little higher.



The other little icon to know about is the TZ ZIP icon in the Game List, This lets you know if your Zip file is TorrentZip File.
You can click on 'TorrentZip ROMs' in the top menu, this will TorrentZip all ROM's in the selected DATs.
(You should Scan your roms first, so that RomVault knows which ROMs need to be TorrentZip'ed)

There are still a number of other features I could add, such as just TorrentZipping any selected Directory (to fully replace trrntzip.exe)
Please do send me your feedback, comments and ideas. Contact Me and of coarse that Donate button is still sitting there over on the left of your screen. (Thanks)

Feb 17, 2011

Fixed a bug today that was making corrupt ZIP files if the rom filenames had characters greater than ASCII 127.
So everybody should update to 1.5.5 as soon as possible. Also it is possible for me to recover the files out of these corrupt ZIPs, so please contact me if you need help with this.
(I will probably put up a link here soon with some fixed zip files.)

Jan 28, 2011

There was still a bug in reading HEX values from DAT files, I was chopping off one to many characters, so I was converting 0x2000 to 000 instead of 2000, which made the size values come back as 0 instead of 8192
Anyway it should be fixed now. So go get 1.5.4.

Jan 23, 2011

Bug Fixed: "Index was out of range" Please download version 1.5.3

A bug has surfaced with the latest RomVault 1.5.2. The error message contains the text "Index was out of range".
I am testing a fix right now, and should have 1.5.3 released before the end of the day.

Jan 22, 2011

A new TOSEC set was just released (Jan 19th 2011), I have uploaded the TOSEC DATs set for this release, setup in the required directory structure.
There will be 3 sets I will be posting here:

1) TOSEC the main dat sets
2) TOSEC-ISO the CD ISO images
3) TOSEC-PIX the magazine dats

Jan 17, 2011

Just put together build 1.5.2, it fixes a small bug in the MESS xml loader so that HEX numbers can be used.
This fixes c64_cart.xml. (Thanks go out to Philippe for pointing out this bug.)

Sept 12, 2010

I updated my Tosec-iso set to match the current tosec iso sets.

July 8, 2010

Just added a quick bugfix update (1.5.1):
Corrupt zips are now correctly moved out to the ToSort/Corrupt directory.
The zip scanning code now cleanly handels zip files that are open by another application and just marks them as unknown status.
Fixed the MESS XML Dat reader to load the latest NES dat (size no longer needs to be suppied if the status="nodump").

June 28, 2010

So I added another update to RomVault (1.5), the main changes are:
Fixed an error on the MESS XML Dat reader. (loadflag="continue" is working in the aes.xml dat)
It now deletes zips out of ToSort as soon as it has finished with them. (Saves a lot of HD space while fixing.)

June 24, 2010

Updated the Tosec-ISO set to include the latest Dreamcast updated.

June 04, 2010

Just to let you all know, I have not disappeared completely, I am working hard on adding Non-Zipped directory support, this turned out to be a bigger deal than I had at first imagined, but it is all good I have really been working on separating out the file handling from the ROM Database Sorting Code, so that the Sorting Codes does not have to know the difference between a ZIP and a Directory. It is developing into an interesting exercise in writing the ROM Sorting Class, and a File/Zip Handling Class, and really separating these 2 classes correctly. Along the way I have found and fixed a couple of bug, and probably will introduce a couple more before this is all done. So more work to be done, but it should be a nice update when it is all done.

May 25, 2010

Thanks to the feedback from emuLOAD on the RomVault Pleasuredome forum, it was pointed out that I missed a couple of things with the new MESS XML Dats, so they are fixed now, and here is 1.4.1.

May 22, 2010

Two new features have been added to V1.4, First RomVault now supports the MESS XML Dat lists. And then secondly I now permit more than one DAT file to exists in the same DATRoot sub-directory, so now (for example) you can just put all of the MESS XML files into one directory and it will create all of the sub directories needed. (using the 'Name' value from the DAT file.)
Because of the changes to support the different dats the Cache store has changed so if you are upgrading you will have to fully rescan your DAT's and ROM's.

May 13, 2010

Turns out there was a bug in 1.2 that meant it would not fix files if they are in a sub directories in the tosort directory.
So here is 1.3

May 12, 2010

Here is version 1.2.

I fixed the tree view to work a little better
And worked a little more on trapping too long filenames

I want to start working on Non-Zipped files and maybe supporting some of No-Intro files that have HeaderBlocks, so it may be a while before my next update, but it should be a good one when it arrives.

April 25, 2010

I have put together version 1.1 with the following fixes:

Added WildCards to the Exclude File List.
Replaced the TreeView control, so that I can add Disabled DATs (if the filenames get to long.)
Added Yes, No options to the unknown File and Directory moving code.
Fixed a couple of crashed.

Download it from the link of the left. (I have changed the cache file format a little. so you will have to rescan all of your DATs and ROMs with this new version)


April 15, 2010

Thanks to my good friends over at Pleasuredome, RomVault now has its very own forum.
RomVault Forum
Please go and visit and leave any comment, bug reports, suggestions.

April 12, 2010

I have decided it is about time I went public with a release!! Please download Romvault from the link on the left.

Here is a very quick get going instructions for RomVault.
Download from the link on the left (RomVault Full DIR's), Make a directory called RomVault and extract the zip into it.
You should now have:

DatRoot This is where you DAT structure will live, I have supplied a few DATs just to get you going, I will update these as time goes by.
RomRoot This is where your ROMS will start collecting.
ToSort you should put ROM zip files in here that you want to sort out.

RomVault.exe Now run this.

To use RomVault you will just click down the big Icons on the Left hand side.

Update DATs Click this first this will read the DAT files in your DATRoot directory, next to try everything out put some test roms into the ToSort directory and then click on:

Scan ROMs This will scan the ROM zips in the ROMRoot directories to see what you have. It also scans the ToSort directory.

Find Fixes Looks at all the ROM Zips you have to find out what need moved where.

Fix ROMs will then make the changes found by the Find Fixes Button.

I have included on the left DAT Zips for the TOSEC sets, you should extract these files into your DATRoot directory, and then click the 'Update DATs' Button, so that RomVault finds them. Then click on down the buttons to scan and fix all of your TOSEC sets.

The rest is up to you.

Please contact me I am very much looking for feedback, I do have a TODO list so please check this out but I also very much want your feedback to make this program as useful to people as possible.

I started working on an early version of this program probably 4 or 5 years ago, trying to fill my own personal need for a program that could handle many DAT files at the same time.

About 2 years ago I started over making a version that I would plan to release at some point, I guess that point has just arrived.

A Final note:
If you find this program useful please use it and have fun. If you would like to help me make it better please contact me with suggestions. If you don't like this program then that is fine keep using your other favorite Rom Management program.

If you find this program really useful then please donate, I have already spent many 100's of hours writing this code, and will probably spend 100's more.
But life is a balance between Family and Work and RomVault Programming time.
And knowing there is a little support coming in for RomVault will enable me to justify spending a lot more time developing it into the future.

Thanks

GordonJ.