Prican25 Posted March 18, 2005 Share Posted March 18, 2005 his post has been changed and let that be a forewarning to all who have joined that theres no rom requests allowed, plz read the rules before doing any such request/post you can request a patch for a rom\s but plz do that in the patches topic i made as i like to leave this topic for updates and troubleshooting for ppl that run into probs running certain game\s Link to comment Share on other sites More sharing options...
GLiTcH Posted March 18, 2005 Share Posted March 18, 2005 UPDATE: - Fixed scrambled graphics in cthd2003. - Fixed graphics in samsh5bl. (I don't have the romset to test this but it should be fixed now) - Some ROM updates. - Added list of all supported ROMsets to package.more rom updates, damn, i'll check it out later thoughthanks Link to comment Share on other sites More sharing options...
+ T + Posted March 18, 2005 Author Share Posted March 18, 2005 There was a little issue with the DATs in the last release not detecting progear clones correctly. I've now updated the package with fixed versions for those who were having this problem. Link to comment Share on other sites More sharing options...
famitsu1 Posted March 21, 2005 Share Posted March 21, 2005 (edited) Hi,sorry to appear completely ignorant:Basically I keep all my roms in my MameOX folder and just direct all my other emus via their ini folders towards these rom folders.From what I can work out Pro doesn't seem to generate it's own ini file and so will only reconise roms which are psyhically in its own rom folder.Is there a way of directing Pro to reconise roms stored on other emus like MameOX?I have tried making an ini folder and placing it in Pro and actually copying my fbaxxx ini file over to it but with no joy.Any help greatly appreciated.Cheers famitsu1 Edited March 21, 2005 by famitsu1 Link to comment Share on other sites More sharing options...
+ T + Posted March 22, 2005 Author Share Posted March 22, 2005 ...(DATs, ini, etc. are now created in E:\TDATA\ffff0504 rather than the root directory) Link to comment Share on other sites More sharing options...
famitsu1 Posted March 22, 2005 Share Posted March 22, 2005 Hi T,ohhhh I see,thanks so much for the prompt reply and info,its greatly appreciated.Thank god for this forum and it's friendly&helpful members,if I tried posting a question like this on the french fbaxxx board I would have been met by a wall of silence,is it just me but that board is really hostile to people who don't already have some grasp of coding ect.Anyway thanks again.Ta famitsu1 Link to comment Share on other sites More sharing options...
MiG Posted March 22, 2005 Share Posted March 22, 2005 Thanks for the fixes.. CThd2003 is working perfectly now... unfortunatly Samurai showdown bootleg is still broken, the graphics still break up in vertical bars. I re-cecked the roms and deleted all the ini files but it doesnt work, If you need s screenshot pm me and i can show you what is up.. Thanks again. Link to comment Share on other sites More sharing options...
+ T + Posted March 22, 2005 Author Share Posted March 22, 2005 (edited) Thanks for the info. I know what the problem is with samsh5bl now. It's just a question of whether I can fix it or not. Edited March 22, 2005 by + T + Link to comment Share on other sites More sharing options...
+ T + Posted March 24, 2005 Author Share Posted March 24, 2005 (edited) UPDATE: - Updated ROM names across all systems. All supported ROMs are now 100% cross-compatible with MAMEdOX (assuming you're using the version that supports the Pro NG sets). Edited March 24, 2005 by + T + Link to comment Share on other sites More sharing options...
MiG Posted March 26, 2005 Share Posted March 26, 2005 Hi T, Just noticed something weird, but since you updated the kof2003b rom with a 128k s rom all the text (such as 'insert coin' and the play instructions) has become messed up.. It was working fine with the 512k s rom. It is still playable, and i checked it with the old 512k rom again but it is not working with that anymore either. I had to patch the s rom several times to get the correct crc could that have anything to do with it? anyway, thanks again.. Link to comment Share on other sites More sharing options...
+ T + Posted March 27, 2005 Author Share Posted March 27, 2005 I don't have any problems with kof2003b. Make sure you're using the latest version of both the emu and DATs and ensure your S ROM has a CRC of 482c48a5. Link to comment Share on other sites More sharing options...
Recommended Posts