"sw" is the store word instruction. It writes a 32-bit word from a register into memory, in this case, general purpose register "v0" (which will be the first argument in your C function for example). "4(s1)" is the memory address to store the data. "s1" contai...

The mouse is interrupt driven so it sounds as if there might be an IRQ conflict

From Will, you're buying the software (BIOS) from NO$CASH which is freeware but you're buying the chip itself and having Will program it which is why it costs money (you're paying for parts and labour). I believe Will should however kindly donate a portion to NO$CASH from the sales of the Xboo softw...

In a nutshell, the HC05 is basically a sort of CD-ROM controller and yes, IC102 is in fact the BIOS.
https://www.willsconsolemodifications.c ... uct_id=111

for some reason, i can't compile your code. https://pp.userapi.com/c840730/v840730379/4f42c/6O24wAeKlA0.jpg I have the exactly same errors. my psyq.ini have [ccpsx] stdlib=libapi.lib libc2.lib libcard.lib libds.lib libpress.lib libgpu.lib libgs.lib libgte.lib libcd.lib libetc.lib libsn.lib libsnd.l...

You can swap the BIOS, but the HC05 will also need to be swapped if you want to boot games and on those older PU-8 boards it typically uses the 80-pin variant which is far less common. To get around swapping the HC05 though, you can just install a modchip.

nocash wrote: ↑September 17th, 2024, 5:48 am The limit is 256x256 (or perhaps something like 255x255 in practice), not 128x128.

Thanks for the correction and clarification

mp3 player for Playstation http://www.geocities.co.jp/Playtown/2004/ bero@geocities.co.jp It is first implementation for test. ‚±‚ê‚̓eƒXƒg‚Ì‚½‚߂̍ŏ‰‚ÌŽÀ‘•‚Å‚·B It is toooooo sloooooooooooow. not optimized for speed yet. use verbose mode,otherwise you will think psx hang up. ‚Þ‚¿‚á‚­‚¿‚á’x‚¢‚Å‚·...

If I'm not mistaken, the PSX can only natively support a texture size of 128 x 128. Larger textures need additional methods.

That horrible colour mod needs to be removed and replaced with a new colour mod.

I wonder how many bytes will get corrupted overtime due to the RAM being mounted on a giant antenna

Nowadays people use the PSNee modchip but otherwise you can't go wrong with a MultiMode 3 (which is also stealth).

I have included an old archive from S1lenT which includes a tutorial as well as old tools to make the STR files. patrickdinh33 has also created a guide which may help make your STRs work with P.I.M.P which I have included below. Note that these tutorials are outdated and are a horrible way to make S...

It's very likely that the memory is being trashed. Check the address size and offsets. When Trimesh was developing and testing the program it was loaded by another method and not a serial uploader.

MercenarioVNZLA wrote: ↑July 4th, 2024, 7:08 pm Please update msRSDExporter

Try sending Orion a private message so the system emails him and when you get a copy, put a mirror up on this topic.

I have a copy on my hard drive somewhere. It was called P.I.M.P which (if I were to guess) would be an abbreviation of PlayStation Interactive Movie Player.

Edit: Here you are https://www.psxdev.net/forum/viewtopic.php?f=75&t=4194

The logic and software is non-existent. I'm talking solely about the hardware. You based your hardware design off of our hardware design. Without our design, you wouldn't have tweaked it to make your new version. I repeat, the only common thing between my cart and the psx blaster is the FT245. You'...

The logic and software is non-existent. I'm talking solely about the hardware. You based your hardware design off of our hardware design. Without our design, you wouldn't have tweaked it to make your new version. We supported you years ago by buying a copy of Yopaz IceStar from your website and adve...

I can confirm that the PSX Blaster design doesn't work. I simulated the logic in a software and it is wrong, RD_USB goes low require AD17 AND !AD17, which is impossible. Also, the logic voltage are mixed up, some logic chip have 5V, some other 3.5V, and the USB chip receive 5V logic on its pin wher...

The heap grows upwards and you can use some basic math to have it dynamically adjusted using the compiler/linker variables. The code below is just an example. Change the variables to your compiler flags as needed. EnterCriticalSection(); InitHeap3(&bss_end, (((int)&sp - stacksize) - (int)&am...