Here it is! This one is all new and has a ton of new features. It's not as "simple" any more though so if you're happy with what you have then don't worry about upgrading

Using this new version will (might?) be a litttle confusing at first, but really it's the same thing only generating lists is a two-step process.
Step 1) Create output format with default criteria. Save.
Step 2) Run it.
Whereas before it was sort of all one big step. You'll see. Just keep in mind that you have to create the "output format" ("report") to specify the fields to output, header, footer, etc. first before you can run it.
This should be considered BETA software! I tested it and it ran fine on my system, but all permiatations haven't been tested and it's likely to mess up somehow.
As with any program, make sure your ROMs are backed up before you do any ROM maintance with it!http://www.bluecamel.org/software/listgen.net/listgen.net_2.0.zipI had to re-work the saved queries implementation. Now it's more of a "report generator", minus all the fancy formatting! You can specify headers and footers so, for example, if you wanted to make a batch file and make sure the folders exist before you co moving ROMs to them, you can add a couple 'mkdir' statements in the header.
There's a "grid" mode now, which will let you see the output in a spreadsheet-like fashion. Also while in this grid mode you can individually select ROMs and perform maintenance on those specific ROMs (delta88, **** my ****

).
Outputting as a DAT file now comes standard. You can make a DAT file of very specific ROMs, if you like (yes, it's a standard SQL statement!).
ListGen.NET 2.0 supports multiple platforms, so when you're importing you have to specify a platform name, like 'mame', 'snes', 'Nintendo 64', whatever. It will be easiest for you though, if you keep it short and simple (like 'snes', 'n64'). Just remember that if you utilize this feature you're probably going to want to specify the 'platform' field in your queries, otherwise you might be getting back more than you intended!
Also, since the multiple platform thing, I'm working on getting the TOSEC information parsed out from the file name. Currently, ListGen.NET uses the same library that comes with TIM (TOSEC's ROM management thingie) but it really needs some work. In addition, most people are using GoodTools-style ROM names, which are pretty much a bastardization of the TOSEC "standard". I'm working on that too, but it's going to be a slow painful process to get that working well.
This TOSEC info can also be output as a standard DAT file, but this isn't all too useful yet until I get the TOSEC parser working better. You can select down to the ROM level though, if you need to.
One of the benefits (that's only going to get more benefit-er) is being able to have 1 DAT file with any platform you'd like on it. Why would you want that? Who knows? You'd still need to have all your ROMs in one folder for it to work in a FE. *shrug*

I feel like there's more that's new but I can't think of them now.
Here is a couple of my TODOs. Feel free to add to them

- Parse and store dipswitch information
- Figure out a better way to specify criteria that will allow grouping.
- Implement the "Import from config text" option for sharing.
Let me know if you have any problems.
And again, all credit for this
timesink GREAT program goes to Buddabing. If it wasn't for his lead, ListGen.NET wouldn't exist!
-sab