THE UNIVERSE BIOS ( MVS / AES, and now also for CD )
www.universebios.com. Also on facebook, please like http://www.facebook.com/UniverseBios.
Last edited by aku; 11-22-2016 at 04:10 PM.
Last edited by Razoola; 11-22-2016 at 04:11 PM.
THE UNIVERSE BIOS ( MVS / AES, and now also for CD )
www.universebios.com. Also on facebook, please like http://www.facebook.com/UniverseBios.
THE UNIVERSE BIOS ( MVS / AES, and now also for CD )
www.universebios.com. Also on facebook, please like http://www.facebook.com/UniverseBios.
The version you had that generated bad roms with the wrong runtime installed, was a really old version, actual version should not create bad roms.
Anyways, we will fix it tomorrow and we will add the option to check if roms are good or bad, this will solve any issue.
Thanks !
Yes it might be the case with newer version but I just don't know, the runtime was required for a critical part of the neo creation with some sets and there was no error message if the runtime was not present before. It would be great if it was no longer needed. The crc check of the final .neo will be a good adition but maybe also a check for the 32bit runtime (if its required still) and a popup error when the ui is launched if its not followed by exit. That would be the best thing.
THE UNIVERSE BIOS ( MVS / AES, and now also for CD )
www.universebios.com. Also on facebook, please like http://www.facebook.com/UniverseBios.
This should be them all hopefully:
http://pastebin.com/raw/6C6KfK39
Its just in case the conversion process has an issue processing a directory that contains the full MAME romsets.
You could use the above batch file to grab the neo geo files out of there.
I would probably make a copy anyway just in case there was an issue processing the original files.
Great job with the NeoBuilder tool!
So far, it's working great for me. I got some "Internal error" / "Bad Roms" issues and some romsets are skipped since they seem to need a different required name (maybe due to my old MAME romset), nothing that can't be solved re-downloading such romsets from different sources or renaming the pre-existing ones. Finally, I am almost done with the full 259 NeoSD 'official' romset.
But here is a simple question: In this NeoBuilderUI version we have been provided, whenever the program generates a .neo file, can it be assumed to be a correct, working one?
Next, I'll continue using the command line program to try to convert some homebrew Neo-Geo games.
Thank you very much and keep up the good work!
OK OK... I can confirm that there are 259 (plus 4 extras that were included.)... There maybe more homebrews ONLY... but thats as complete as it gets for now..
Someone sent me this:
http://imgur.com/a/KawAp
I can also confirm that I do have a full set of stuffs available to me...
xROTx
PS. The CHAT Room here is FLASH based... just FYI there lads...
EDIT: This post is meant for people who are having "Difficulties"... in certain matters... and if I am in chat (I live in GMT land..)... i will be available to discuss your problems...
I'm just wondering if the neosd builder could support other file formats other than zip? My sets are in 7z format and other may use rar, not sure just a thought. I am having to unzip then re pack in zip format.
Hello,
We are just working now on a tool to verify created roms, we have already fixed yesterday reported issues.
Both things, among a readme explaining how to install/use the tool, will be avaliable today.
We are working as fast as possible to get this shorted.
Thanks !!
Thank you for the new verification tool, neosd!
Finally, I managed to obtain the 259 'canonical' .neo files. In addition, in the "order.txt" file there seem to be 3 additional filenames which yet are not recognized by NeoBuilder in your ROM directory: 'kof10th' (KOF 10th Anniversary), 'kf2k3pcb' (KOF2003 JAMMA PCB) and 'samsho3k' (I guess, Samurai Shodown III Korean Release, aka Fighters Swords, already included and recognized as 'fswords'). Only the latter can be converted manually using the command line, whereas the other two give an 'Invalid romfile structure' error. However, it doesn't matter, as they are repeated game versions and we already have two more 'hacked' versions of KOF 10th which are recognized (KOF 10th Extra Plus / 2005 Unique).
I also used the command line program to yield some .neo files from all my homebrew NG collection, and I can say that almost all seem to be successfully converted, the exception being BIOS-like ROMs (including those of Neo Print), thus raising a total amount of 277 .neo files so far. Let's see if they can be verified with the new tool... ;-)
I've just tried to convert a ROM set I had but I have almost as many games with errors as games that worked. Anyone got any ideas?
http://i.imgur.com/py2FwEA.jpg
probably not the correct sets to start with.
THE UNIVERSE BIOS ( MVS / AES, and now also for CD )
www.universebios.com. Also on facebook, please like http://www.facebook.com/UniverseBios.
This should help you freakin n00bz....
Latest Set as of 28 July 2017... COMPLETE... Includes da' Muzak now... over 13gb on extraction...
xROTx
PS... Copy Paste the individual HTML links into a web browser...
Download... Extract...
Hello everyone,
Neobuilder 1.02 is up.
http://www.neosdstore.com/news/index...loads-section/
Thanks
Good job NeoSD, works great. And good idea for the validator.
Thanks neosd!
The validation tool works great. As expected, my 259 recognized 'official' .neo files are correct, whereas the remaining 18 'handmade' .neo files appear in the Errors column. No missing known neo files! :-)
Time to copy them to the microSD card... ;-)
The readme file is also detailed and well explained. Congrats again!
There are currently 1 users browsing this thread. (0 members and 1 guests)