You don't have to go back that far - a lot of the early P4 machines supported Windows 98SE too. They typically shipped with XP on them, but since during that time frame a lot of business users were still using 98 they still had support (and drivers) for it.

More problematic, depending on the ...

It shouldn't be a problem - I've written lots of stuff with the source split over multiple files.

You could try compiling it manually to see if it's a problem with the build system - just use a command like

ccpsx -g -Xo$80010000 file1.c file2.c filex.c -otarget.cpe
cpe2x target.cpe

Someone was ...

The short answer is that on a PU-18 the modchip shouldn't interfere with reading the disc.

On the older boards (PU-7, PU-8, PU-18, PU-20) the output data from the modchip is connected directly to the mechacon MCU as a digital signal and no connection is made to the analog side of the circuit. The ...

No, that's not normal - from the look of it, the chip has already been programmed with something - and since the 12C508 is an OTP device that means it's basically useless.

This approach seems great so far. About that CPU speed: I really don't know much about ROM reading yet but I assumed that OE pin was there to signal that data is ready. Shouldn't this enable us to deliver the data at the speed we want?


The signal you want is conventionally called WAIT - but in ...

It is the wrong install diagram - that's for the "Stealth 2.x" series of chips. On the PU-8, the MM3 does not support full stealth and is normally installed in 4-wire mode with only pins 1, 5, 6 and 8 connected - all of which go to the same places as the corresponding pin numbers on the stealth 2.x ...

I think these are involved in IC706. But this custom chip, datasheet is only in general terms.
There is a lot of information on the components of PU-18 with datasheets. There are also descriptions of the pin assignments of the microcircuits.
http://wiki.psxdev.ru/index.php/PU-18


Yeah, the ...

Ah yeah, I wrote what I remembered. So the C is for center..

Anyway, we know that the wobble on pressed disks creates a pattern that some kind of tracking error circuit converts to the 1's and 0's that form the SCEX string.
That error detect circuit is part of any CD DSP, but Sony added another ...

Yes, it's entirely reasonable what SCEE did. That's why I find it so odd. As I understand it, the LibCrypt option wasn't available until later, but I may be wrong on that.

At the time the anti-modchip code came out, libcrypt was something that SCEE had in development in their Cambridge research ...

Maybe I'm jaded but such a pro consumer decision just sounds odd to me.

It is possible though, of course. One other development of the time:
The anti region lock modchip.
It was much more complicated to pull of, but it replaced just the last letter of the SCEX string, allowing games of all ...

If you search this forum (and maybe Assemblergames, I forgot), you will find this most likely explanation:
SCEE simply did not want this code to lock out games from other regions.
My addition to it: Maybe they didn't fully understand what this code would block and management simply banned the idea ...

OK, that looks like an original Datel PCB for sure - I don't think I've ever seen a gameshark with an AMD flash chip in it, though. See if you can find one of the chips that were used in the Datel carts - my original Datel carts have Atmel AT29C010 chips in them, and they definitely work .

If it really is a V1.x Gameshark then it has the old style Datel communications port - these were not compatible with parallel ports and connected only to a special "comms link card". These are (somewhat amazingly) still available from certain sources (like EMS in Hong Kong), but you most likely don ...

The check was probably always intended. It appeared in the Japanese boot code almost immediately after the initial batch of consoles. EU and NTSC-U consoles probably have the code for it, but disabled. I don't know this though, it's just speculation.


The check was always in the Japanese ...

You may also want to remove the modchip connection for dumping. It may interfere.

I have no modchip in my net yaroze.


I will dig out my Arduino and see if I can find out what the problem is - my guess is that serial.print() is blocking long enough to miss the start bits coming out of the ...

I will dig out my Arduino and see if I can find out what the problem is - my guess is that serial.print() is blocking long enough to miss the start bits coming out of the PSX and the code needs some buffers.

Apropos. Any news on dumping more retail psx cdrom firmwares? I had hoped that dozens of people would their firmwares... like people implementing it as "my first serial data transfer project" using an arduino or the like... but now it's more than three years and only 3-4 people managed to dump ...

I have disable the ntsc fix, and now the psone works fine.
So in my case i don't need the A18 and D2 point on the bios chip?

I like my installs to be as clean as possible, i can make this on all psx version and post it, at least on pall versions.


You will only need those points connected if ...

Hello from Portugal
I have installed a arduino pro mini 8Mhz on a PU-18 if the last version of PSNee, and everything works ok tank you rama3 for the code.
But on a PSONE i did not have any luck, again if a arduino pro mini 8Mhz, when the psone is loading the screen appears like is out off sync ...

Yeah, that's a serious limitation.
Definitely rules out using a hacked original software this way.

Do you think the RAM is enough to establish 2 way communication with an external MCU?
It would also have to read and control each of the used I/O.


Maybe, but you would need some pretty fast IO to ...