Thraxen

They aren't going to let people rip and play their own PSX games. That will never happen.

It worked for me. Try renaming your files to match the names in the CUE I posted. Those long file nmes you are using may be causing an issue for some reason. That's the only difference that I can see between the game working for me and not working for you.

OK, this is the best I could do for Renny Blaster: FILE "Track01.mp3" BINARY TRACK 1 AUDIO INDEX 1 00:00:00 FILE "Track02.iso" BINARY TRACK 2 MODE1/2048 INDEX 1 00:47:71 FILE "Track03.mp3" BINARY TRACK 3 AUDIO INDEX 1 04:16:04 FILE "Track04.mp3" BINARY TRACK 4 AUDIO INDEX 1 06:10:68 FILE "Track05.mp3" BINARY TRACK 5 AUDIO INDEX 1 07:40:12 FILE "Track06.mp3" BINARY TRACK 6 AUDIO INDEX 1 09:14:15 FILE "Track07.mp3" BINARY TRACK 7 AUDIO INDEX 1 10:57:30 FILE "Track08.mp3" BINARY TRACK 8 AUDIO INDEX 1 12:05:21 FILE "Track09.mp3" BINARY TRACK 9 AUDIO INDEX 1 13:07:16 FILE "Track10.mp3" BINARY TRACK 10 AUDIO INDEX 1 15:09:68 FILE "Track11.mp3" BINARY TRACK 11 AUDIO INDEX 1 18:05:18 FILE "Track12.mp3" BINARY TRACK 12 AUDIO INDEX 1 20:15:24 FILE "Track13.mp3" BINARY TRACK 13 AUDIO INDEX 1 22:24:48 FILE "Track14.mp3" BINARY TRACK 14 AUDIO INDEX 1 24:55:47 FILE "Track15.mp3" BINARY TRACK 15 AUDIO INDEX 1 26:59:17 FILE "Track16.mp3" BINARY TRACK 16 AUDIO INDEX 1 31:50:15 FILE "Track17.mp3" BINARY TRACK 17 AUDIO INDEX 1 35:04:37 FILE "Track18.mp3" BINARY TRACK 18 AUDIO INDEX 1 37:00:37 FILE "Track19.mp3" BINARY TRACK 19 AUDIO INDEX 1 38:02:26 FILE "Track20.mp3" BINARY TRACK 20 AUDIO INDEX 1 38:13:29 FILE "Track21.mp3" BINARY TRACK 21 AUDIO INDEX 1 39:57:71 FILE "Track22.mp3" BINARY TRACK 22 AUDIO INDEX 1 43:04:11 FILE "Track23.mp3" BINARY TRACK 23 AUDIO INDEX 1 44:45:63 FILE "Track24.mp3" BINARY TRACK 24 AUDIO INDEX 1 46:09:10 FILE "Track25.mp3" BINARY TRACK 25 AUDIO INDEX 1 48:30:16 FILE "Track26.mp3" BINARY TRACK 26 AUDIO INDEX 1 49:36:52 FILE "Track27.mp3" BINARY TRACK 27 AUDIO INDEX 1 51:25:19 FILE "Track28.mp3" BINARY TRACK 28 AUDIO INDEX 1 53:29:52 FILE "Track29.mp3" BINARY TRACK 29 AUDIO INDEX 1 54:09:26 The game plays and there is music, but I don't hear any sound effects. So either the original game was like that or, more likely, it's a bug with the emulator. Also, some of the cut scenes tend to skip by too fast it seems. But the game is playable (but it's not a very good game ).

Wow... that's a fairly obscure game. Most PC Engine CDs do work, you just have to make a good cue. If I can get my hands on that game or the Downtown game then I can likely make a working cue, but I need the games first.

X3 CE w/ LCD I use XBMC all the time to watch videos so the progress bar on the LCD screen is quite useful. The chip itself is installed with the pin header and 3 wires (LAN, HDD, D0). Super easy to install... I've installed them for several friends as well.

I've got a couple of bugs that I think have been asked about before but I can't remember for sure. Anyway, someone was asking me if it was possible for these 2 bugs to be fixed... First, when you select X-Arcade as your controller type and configure the button the emulator doesn't save the configuration. You apparently have to configure the controller options each time you play. Second, the dip swtiches in Magic Sword (CPS1 game) don't work. Changing the switches through the emulator menu has no effect. If you try to change them by activating the Diagnostic Mode and selecting the Dip Switches option from the -in-game menu you can't actually navigate the screen to change anything... all you can do is look at the settings and exit back out. Also, does FBAXXX have the ability to save hi-scores, or would that have to be accomplished by using save states?

Well, I don't have that game and can't seem to locate it right now either... I'll keep looking though,. Anyway, here is what I did to get Hellfire S working. First I tried Sega Cue Maker, but it failed. SCM doesn't make PC Engine cue files correctly anyway. It puts them in Sega CD format. For example, it always lists the ISO track first when the first PC Engine ISO track is always track 2. Also, if there is more than one ISO track it won't list the second one. I assume this is because Sega CDs must only use one ISO track so it doesn't know how to handle more than one. So I then used CDDISSECT. I burned the ISO to a CD-RW and then used CDDISSECT to make a cue sheet. CDDISSECT is a command line program, but don't let that scare you away, it's easy to use. 1. Burn ISO to a CD 2. Put CD in drive 3. Start -> Run -> cmd (to bring up command prompt) 4. Navigate to where the CDDISSECT executable is located (cd = change directory) 5. Type this in, "cddissect -alt -cue Hellfire" 6. Select drive 7. Done You might not have to use the "-alt" flag, but I did. CDDISSECT won't work with some drive without it. The "-cue" flag just tells the program to only make a CUE sheet and not actually rip any tracks. The only bug with CDDISSECT is that it doesn't report the ISO format correctly on PC Engine games. When you have the cue you need to change the ISO format to say this "MODE1/2048"... CDDISSECT will put this instead "TRACK 2 MODE1/2385" (or something like that). The games will usually play with the wrong format listed, but it's not technically correct so I usually fix it.

Alright, I got HellFire S working. Use this cue: FILE "Track01.mp3" BINARY TRACK 1 AUDIO INDEX 1 00:00:00 FILE "Track02.iso" BINARY TRACK 2 MODE1/2048 INDEX 1 00:47:65 FILE "Track03.mp3" BINARY TRACK 3 AUDIO INDEX 1 01:16:08 FILE "Track04.mp3" BINARY TRACK 4 AUDIO INDEX 1 01:48:70 FILE "Track05.mp3" BINARY TRACK 5 AUDIO INDEX 1 02:33:56 FILE "Track06.mp3" BINARY TRACK 6 AUDIO INDEX 1 05:24:68 FILE "Track07.mp3" BINARY TRACK 7 AUDIO INDEX 1 11:51:72 FILE "Track08.mp3" BINARY TRACK 8 AUDIO INDEX 1 16:14:16 FILE "Track09.mp3" BINARY TRACK 9 AUDIO INDEX 1 16:20:45 FILE "Track10.mp3" BINARY TRACK 10 AUDIO INDEX 1 21:08:16 FILE "Track11.mp3" BINARY TRACK 11 AUDIO INDEX 1 28:28:40 FILE "Track12.mp3" BINARY TRACK 12 AUDIO INDEX 1 33:12:29 FILE "Track13.mp3" BINARY TRACK 13 AUDIO INDEX 1 37:37:35 FILE "Track14.mp3" BINARY TRACK 14 AUDIO INDEX 1 38:05:21 FILE "Track15.mp3" BINARY TRACK 15 AUDIO INDEX 1 38:57:41 FILE "Track16.mp3" BINARY TRACK 16 AUDIO INDEX 1 40:08:18 FILE "Track17.mp3" BINARY TRACK 17 AUDIO INDEX 1 40:22:39 FILE "Track18.mp3" BINARY TRACK 18 AUDIO INDEX 1 41:22:12 FILE "Track19.mp3" BINARY TRACK 19 AUDIO INDEX 1 41:40:06 FILE "Track20.mp3" BINARY TRACK 20 AUDIO INDEX 1 42:13:57 FILE "Track21.mp3" BINARY TRACK 21 AUDIO INDEX 1 46:07:64 FILE "Track22.mp3" BINARY TRACK 22 AUDIO INDEX 1 46:16:08 FILE "Track23.mp3" BINARY TRACK 23 AUDIO INDEX 1 46:31:10 FILE "Track24.iso" BINARY TRACK 24 MODE1/2048 INDEX 1 46:56:66

It's actually fairly easy to change the save location yourself with a hex editor. I actually posted some quick instructions on how to do this over at XBox-Scene just a few days ago: Link It might be easier with dexbe, but I've always just used a hex editor for tasks like this.

You can a list of some working CUE sheets here: Link Star Parodia is in there. Sorry I haven't gotten around to Hellfire yet. I'm pretty sure I had it running at one time but as I said earlier I didn't bother keeping it on my XBox because I could play it on Genesis anyway. But I'll take a look at it tonight. If I get it working I'll post the cue. [edit] Seems I got rid of Hellfire... I can't find it right now. I'll see if I can find it again.

That isn't a concern if you are using an Xecuter BIOS. The Xecuter BIOS' block Live access so you wouldn't be able to connect even if you wanted to. It's a nice feature. They could, but as far as I know it's never been proven that they (MS) have ever done that. Some people who are paranoid of that very thing keep their C: and E: partitions stock. You can boot off the F: partition and leave everything else bone stock. And it doesn't matter what's on F: because the original XBox BIOS has no way to access it.

You have two options. One, rename all your files to match the names used in the CUE file that I linked to... Two, change the names in my CUE files to match the names of you files. Do either of those and then try to launch the game again with the new CUE file.

Rayxanber II seems to work fine for me... I can't remember if I've ever tried Hellfire or not... I think I did but didn't bother keeping it because I could play it on the Genesis emulator. There's a working CUE for Rayxanber on Xport's site here: Link Just make sure your file names match the names in the CUE. When I get a chance I'll try Hellfire later.

I think he plans to update all his own old projects and then maybe throw in a new project or two... but I don't think he plans on touching MAME again. He is going to be busy enough getting all his emus caught up to their PC counterparts.

Well, Magic Plus 2 (kf2k2mp2) is still has the garbled graphics, but Magic Plus (kf2k2mp) is now working fine.

Don't bother. I'm hoping to have a fixed build out soon. However the kf2k3upl problem doesn't look like a driver issue. Thraxen, do you know if it does the same thing in MAME? <{POST_SNAPBACK}> OK, I can now confirm that MAME has that bug seen in kf2k3upl too. I played the game in the latest MAME 0.104 and it did it too. Maybe it's just a bug with the game itself?

All these ROMS with the problems are clones... so, yeah, you could take them out and still play other versions of the same game.

Don't bother. I'm hoping to have a fixed build out soon. However the kf2k3upl problem doesn't look like a driver issue. Thraxen, do you know if it does the same thing in MAME? <{POST_SNAPBACK}> I'm honestly not sure as I haven't tried it yet. I'll try to test it later tonight unless someone else does it first.

I wonder why some sort of modchip hasn't appeared on the scene? The firmware seems like it is full of holes which is why we have the constant battle between Sony and hackers... hackers find exploits and then Sony attemepts to fix them. Given that plus the fact that it's a Sony product you would think there must be some sort of hardware hacks that could be done. Then we could just be done with all this non-sense about firmware exploits, revisions, upgrading, downgrading, UMD emulators, ISO launchers, etc, etc... So what do you guys think? Is the hardware simply harder to crack than the firmware? Or is it more along the lines of not being able to fit a chip inside or it being too difficult to install a chip thus making the potential market to small? IMO, any sort of chip, even if it had to be contained in a small case on the outside of the PSP, would be highly profitable... simply because a chip would likely allow people to no longer have to worry about their firmware version.

Some bugs have been found in this latest build. These games all have scrambled graphics and garbled sound (all appear to be affected by the same issue): kf2k2mp (KoF 2k2 Magic Plus) kf2k2mp2 (KoF 2k2 Magic Plus II) ms4plus (Metal Slug 4 Plus) ms5plus (Metal Slug 5 Plus) Also, when all these games launch the problem affects the Uni-Bios screen too: unibios KoF 2k4 Ultra Plus (kf2k3upl) also appears to have a bug: kf2k3upl This happens when fighting the mid-boss, Kusanagi. When the round starts both character look normal, but at some point during the round they will both look like they are encompassed by fire... and they will stay that way for the rest of the fight. This also happens when fighting the final boss, except the fighters look like they are surrounded by green fire.

Yeah, that's the most complete you can get right now.

Well, you know how inside each ROM zip file there is a collection of several files? Yellow ROMS means that you have all the correct files to make that ROM in your ROM set, but there is still something wrong with that set. Just click on the ROM name in the left hand window where you have your ROM paths defined and then look at the right hand window to see what it says. It will probably be one of two things. First, one of the files inside the zip may simply have the wrong name. In this case it will say next to the file something like, "Bad name, name should be [whatever]". So all you have to do it right click on the ROM and select "Fix game" and Romcenter will rename it for you. The other message you might see is, "Available in another game". That means that a required file is missing from that ROM, but the file that is missing is located in another ROM set (i.e. a different version of the same game). So just right-click on the ROM and select "Fix game" again and Romcenter will copy the missing file from the ROM that has it and put it in the ROM that is missing the file. Yellow ROMS are easy to fix, but you can't ignore them because the emulator won't run them unless you do fix them.

BTW, thanks, iq_132, for all the input you've had with the recent updates. There are a lot of people out there that appreciate the work you guys are doing with Pro.

It appears that kf2k3pcb is wrong in the emulator and/or DAT. It calls for a 271-bios.bin (148dd727) that is 256 KB in size. I have that file with the correct CRC and it's actually 512 KB in size. I was just updating my ROM set so I haven't tried to run it yet... so I don't know if it's just wrong in the DAT or if it's wrong in the emulator too. [edit] Well, nevermind the part about checking the emulator. I tried to run it only to find out it's a non-working game anyway. But the DAT is still wrong about the file size.

I'm not sure that would work. The previews are all pngs while the screenshots are in BMP format. The emulator may be able to use BMPs for previews... but I have not tested that. But another problem would be the names of the images. The previews are all like this: [name of rom].png Screenshots are all like this: [name of rom] [###].bmp (or something like that) The ### is the screenshot number... like 001, 002, 003, etc... IMO, it doesn't seem like it would be worth your time to try and change any of that because it would probably be more trouble that it's worth.