Do you have the mainboard where the SCPH-5000 bios chip came from, too? The board name & mechacon chip part number would be interesting for adding it to this list: viewtopic.php?f=70&t=1065

I am not familar with PS2. What is a DECKARD? Another odd things was that when the INTerrupt value in 0x1F801803.Index1 would change from 0 to the actual value (on polling), sometimes it would first become one value and only on the second read does it turn to the expected INT value. You mean like tr...

Not really. Your description about ambient/music/sound is leaving it rather unclear which sound sources you are talking about. Is it SPU sound working, and XA-ADPCM sound streamed from CDROM to SPU not working? That could happen technically - if there's some sort of broken connection between CD and ...

Thanks for the scarlet sample! With the multiple source code files it looks good for testing some more complicated cases. Having a PSXSDK sample from somebody would be also nice! I assume that it does have debug info stored in ELF files (?) which would be even easier to implement because the no$gba-...

You have made it a 512K file, didn't you? The secret unlock commands were added with no$psx v1.9, you could download the older versions and try if they work. Even the older versions are writing to debug info stuff to unused I/O ports. Theoretically, some/many/all other emulators should just ignore t...

Caetla with the parallel port. I like using that due to the speed and it keeping the SIO port free If you want it for speed, you could also give it a try with the kernel clone & upload function in no$psx: http://www.psxdev.net/forum/viewtopic.php?f=76&t=1319 It should be 3x faster than the original...

What's that RA=80020070h from? Is that something in your uploaded EXE code (or is it an address from the caetla rom)? If it's from the EXE, disassemble the code at 80020070h and up, and the function being called at 8002006xh, either there it must have crashed. Or if it's from the ROM, try to disasse...

The linked repo is not the original code so the lines won't be 1:1 for the files I attached : - ). Good to know, then I don't have to worry about the mismatching line numbers. Even without matching source code, the the huge 1.5Mbyte .SYM file from tomb5 is very useful to make sure that the debugger...

I've reverse-engineered most of the .SYM file chunks. The five chunk numbers from the ASM68K version do match for PSX version, too (but with slightly different parameter values). But there are a lot more than five chunks... lameguy's sample uses 12 different chunks, and the tomb5.zip package contain...

This is not a myth but reality. 90's are in the past and modern compilers really evolved pretty good. Yeah, possible, maybe compilers are getting better over time. Or, to be pessimistic, maybe they will require more and more resources, ending up with code that is "faster" than from some recent era,...

SYM Files Different versions sounds nasty, good that you mention that! Having some small homebrew sample for the "current/newest" version would be also great. That Samples Addon CD might be also useful (if it's for the newest version?) (I don't know where to get that CD though). There isn't any spe...

Hmmmm, I think those modern C/C++ compiler optimizations are a myth originated somewhere in the 1990's. I've haven't yet spotted any such optimized code when disassembling software for PSX/GBA/NDS/DSi consoles, from my experiences, compiler code tends to be at least 10x slower than ASM code, and I w...

Yes, settings are stored in one of the unused memory card sectors. Storing them in bios/expansion memory would be a bit more difficult: Won't work with chips aren't stored in the chip ID list, won't work with PROMs or UV-EPROMS, and I haven't researched what kind of erase-sector-sizes the different ...

Memory Cards: Yes, I've tried the other options as well. The problem immediately starts at 1.0 (fast). tested: Tomb Raider 5, Chrono Cross, Tomb Raider 2, PSX-XBOO itself (tried to copy a savegame > Card I/O Error) Hmmmm, how could that happen? Looks as if I didn't test things too well. Or maybe it...

Ow this sounds cool. Also the general kernel replacement. Should this be supported by all ps1 hardware or on wich did you test this? The kernel and vcd player should work anywhere from early psx to late psone. In japan/asia, one would need a modchip as extra hardware for the vcd player. Wow, that's...

Installer EXE Oops, yes, there's a stupid mistake: I forgot to zeropad the EXE to next 800h-byte boundary (the installed stub is 2800h bytes, but the size of the appended ROM-image isn't properly aligned). Theoretically it should have worked in a single step, as so: 1) Create nocash expansion rom i...

New no$psx version should work with the DeathBall - but only with one joypad (which makes the game rather unplayable; no$psx has some support for up to 12 joypads when emulating 12 consoles at once, but it still lacks support for more than joypad per console). Btw. looks as if the loading problem wa...

Yes, I could try to add support for those .sym files. I've never used any psx SDK's, and until today I haven't even known that they can store debug info in .sym files (though I've wondered if they might have some such feature). Do you have any specs for that .sym file format? Having some sample pack...

Hiya, the new version of my kernel clone is now also working as Expansion ROM (ie. it can be used with regular Xplorer & Datel cheat devices). The binaries can be found in no$psx v2.0 (debug version) --> Utility --> Remote Access menu. There are several options for installing the file: - You can ext...

Just released no$psx v2.0 (psx emulator/debugger), and also updated the SPXSPX playstation specs: http://problemkaputt.de/psx.htm There are a bunch of new things here and there. A lot of new stuff related to peripherals. And alongsides, two new features for the kernel clone: * It's now working as Ex...