This is the official kit, for professional developers. It comes with all sorts of equipment (among others 'the Blue PSX'). The compiler is made by SN Systems, the libraries and documentation are by Sony (I don't need to tell you their URL, do I?). Basically, this is the kit, it allows you to use the psx to the full extent (contrary to the yaroze). It makes things a lot easier (coding wise), but a crappy coder with a (fairly) good compiler is still a crappy coder.

A rip-off, you get a grey psx that's painted black for the occasion, a serial cable, a cd, a dongle memory card, documentation and a compiler (that produces ecoffs) with all the libraries compiled into one, nice, big, clumsy libps.exe. (which eats a lot of memory). The only thing you get for your money is legality. If (when) you use it, you have to convert the ecoff the yaroze compiler generates to 'real' psx-exe's using eco2exe. And combine comes in handy for combining your exe with libps.exe.

First let me remind you that the psx's cpu is not in Intel's ball park (in fact, not even gameday ;-) ), it's a mips cpu (like I said, a modified r3000). Therefore you cannot just use any compiler, you need one that outputs r3000 ecoffs (or some compilers even include the psx as a target). If you have a compiler that produces ecoffs, you need eco2exe to convert the ecoff to a regular psx-exe.

So your best bet is cross compiling a gnu compiler so that it outputs (once again) r3 ecoffs.

Now this is (I think) the only 'easy' legal way, you can still use c (although some weirdo's prefer asm.. ;-) ) and you're in the clear on the legal area: Check the Not Yaroze site (which has a link to the compiler kit targeted win32). And if we're lucky, there will be libraries -- developed independently from Sony -- that offer the same functionallity, only better ;-). But for now, just start cracking ;-)

Note: because psyq uses a proprietary format (not ecoff, it's similar, but not entirely) which hasn't been hacked yet (afaik), you can't use the official libraries with a cross compiled gnu kit.

As you already know.. the cpu in the psx is a modified r3000 (see www.idt.com) and mips asm is simple as fook. You can download a nice reference from ftp.idt.com/docs/3467.pdf. For now, I'm not including a tutorial on programming in asm, as it's easy(see hitmen and napalm sites) and there are lots of examples.. erm I mean exe's to disassemble. I know, it's the hard way, but by doing it a couple of times on simple examples (maybe a c source you compiled yourself with, for example psyq), you learn a lot about C, the psx and how compilers 'optimize'. And as an added bonus, you can use the symbol tables generated by psyq with my disassembler. This makes things quite a bit easier.
It's called AdisasM and you can find it on Hitmen&Napalm.. version 0.3b is the latest, it's just a couple of buxfixes, and I added the -x switch, which enables 'higher level disassembly'.. it's no big deal for now, but I'm thinking about coding something specifically for compiled c code, like re-ordering instructions, maybe even some sort of pseudo language resourcing with simple flow control and memory references... If you have any ideas or if you want to invest some time, thinking and coding in it, please let me know, I just don't have time to implement my ideas.

How to make a PSX cd

StopCallback();
printf("Stopped callback\n");
_96_init();
printf("_96_Init\n");
printf("Loading Exec file\n");
LoadExec("cdrom:\\SLES_012.28;1",0x801ffff0,0);

This is very easy, just use code like the following:

void main()
{
 char c[80]; 
 struct DIRENTRY res;
 strcpy(c, "pcdrv:*.*");
 printf("\n** Loading files...\n");

 // Generate list from dir entrys...
 if (firstfile(c,&res)==0)
 {
  printf("Failed to read directory entry, does directory pcdata exist?\n");
  exit(1);
 }

 processFile(rec.name)
 while (nextfile(&res)!=0)
 {
  processFile(rec.name)
 }
}

void processfile(char *name)
{
 int fd;
 char fullName[80];
 strcat(fullName, name);
 fd = open(fullName, O_RDONLY);
 if (fd==-1)
 {
  printf("Failed to open file %s\n",rec->filename);
  exit(1);
 }

// Load file here...
 numRead = read(fd, (char *)rec->ptr, rec->length);
 if (numRead != rec->length)
 {
  close(fd);
  printf("Failed to read from file %s\n",rec->filename);
  exit(1);
 }

 printf("ok.\n");
 close(fd);
 rec = rec->next;
}

This will read the directory from the PC and load all files into PSX ram,

hope that helps

FuSIONMan

if (*(char *)0xbfc7ff52=='E') // E(urope) --> PAL; A(merica) and J(apan) both use NTSC
 SetVideoMode(1);     // PAL
else
 SetVideoMode(0);     // NTSC

#  Makefile for MyK1ck4zzTro
CC   = CCPSX
ASM  = ASMPSX
LINK = PSYLINK

CCOPTS   = -c -g -comments-c++
ASMOPTS  = /l /o c+,h+,n+
LINKOPTS = /m

OBJS = main.obj data.obj

tro.cpe: $(OBJS)
        del tro
        $(LINK) $(LINKOPTS) /p @tro.lnc,tro,tro.sym,tro.map
        $(LINK) $(LINKOPTS) @tro.lnc,tro.cpe
        ren tro.bin tro
        cpe2x /CE tro.cpe

main.obj : main.c
        $(CC) $(CCOPTS) main.c

data.obj : data.s
        $(ASM) $(ASMOPTS) data,data

You might find these useful:

cpebin adds a binary file to a .cpe file, which is probably THE easiest way
to include a MOD or graphics in your demo. For example, just do

bincpe mydemo.cpe great.mod 80080000

and great.mod has been added to your .cpe! You can then convert the .cpe as
normal to a PSX exe.

pxe2cpe converts a PSX exe to a .cpe file. The two programs combined can
then be used to convert old multifile demos to a single file!

You can grab Win32 versions w/C source right here from 
Napalm,or visit http://hjem.get2net.dk/surfsmurf


SurfSmurf . >(oo)<