PlayStation Development Network

Hi there,

Wasn't too sure where to post this. I thought this was probably the most appropriate forum.

I'm sure homebrew authors are testing their work via emulators as they build different pieces of their projects. How are you testing the final product on the actual hardware?

Are most burning CDs to be placed in your PlayStation or is sending the game through a NetYaroze communication cable the general practice?

Burning CDs can get time consuming and costly when you find little things that act okay in an emulator but don't act quite right on the real hardware. And with the communication cable; you're limited to what can fit in RAM, right?

I know the PSIO is coming but what do you use now for real hardware testing? Also, how do you confirm your NTSC/PAL conversions work on real hardware? Do you have PAL and NTSC machines to test with before you release?

Hi. I use an Xplorer with a parallel cable to do communication with my PSX and PC.
The firmware on the Xplorer is CAETLA 0.34, while my parallel port is in SPP mode.

same i do.

in EUROPE we have PAL. if i have a NTSC game it is scaled in Black/white.
to patch, i read some screen "fix Values" from the original NTSC ps1 exe and put it in my main.C --> source.

later i activate it in the "PSX.EXE while pressing "O" on Gamepad ---> now it is correctly displayed and in full colour, but mostly i'll let detect the videosystem automatically .
that's it.


fast codings i test with a pc emu: ePSXe.exe

In the library I made, I use data loading over the parallel port cable, so I have 2 mode of testing, one is debugging from PC and loading data from my PC, and the other is from CD when doing a release.
So I'm not limited to the psx memory
I explained it in my playstation coding tutorial:
http://onorisoft.free.fr/psx/tutorial/tuto.htm

To write edit end use codeblock.
psyq use to compile.
epsx use emulator to run. and cd-rom
I have 2 and 3 ps1 ps2
I'll try to run homebrew via emulator (psxps2)