forums.ps2dev.org

Anyone know if there is a solution yet to getting a DS3 controller working on Vista x64?

I can help you.

1) Buy a license to develop on the PSP from SCE

2) Log onto scedev with your supplied user/pass and download the SDK libraries for use with Codewarrior.

You're welcome.

nice work!

:)

If you'd like, I can test it under 1.5. Chances are it'd work.. everything that was on a previous firmware is generally available on the next. The official games that required 1.0 still work on 2.8 and so on.. of course, you didn't use the official SDK so that might not be the case.. worth a try tho...

in the new SE-C SDK you can set the version number by doing
That would change the version number to 2.81 for example. However, the problem with SOCOM 2 is not firmware version, it checks something else.

I would like to know this aswell (don't have a PS3). I tried a few PS3-only websites with changing my user agent to the same as the PS3 browser and they worked.

Maybe it would work with the store also.

nice one TyRaNiD :-)

Hello guys, what is an easy way of reading a directory in on the mem stick so I can get the list of files to load into my program?

cheers,
zshadow

Very nice work.

Erm.. DATA.PSP is just an ELF file.

DATA.PSAR contains all the firmware modules which is extracted when you run a fw update.. what use would it be to make your own? Anyway they probably have some Sony internal soft for building them.

data.psp can be decrypted using prxdecrypt sample in PSPSDK - although, if the data.psp is encrypted with a fw 2.6/2.7 key you may have to edit the source and run it on a 2.6 unit.

moonlight wrote:Awesome.

Kernel mode on 2.6. The keys will be with us soon :)

Congratulations.

indeed :)

nice work hitchhikr

0okm0000 and all others I know I asked this in the old now locked thread, but the answer I got was not to my satisfaction... About using bigger RAM, I found out that the development unit has 64 mb for main memory, I don't know if that suggest only flash or both RAM and flash. My guess would be that...

add to end of file:

I ran it for a few hours..

received quite a few false positives, but heres one that may be real (someone feel free to test) -

1579a159 = sceUtilityLoadNetModule

Fanjita wrote: Any idea if loadexec.prx or similar modules look like they've changed? This would help to confirm / refute the rumour that the syscall mechanism has been modified.

2.7 loadexec.prx is about ~5KB larger than the 2.6 module. So it seems quite a bit was added / changed.

some new modules I noticed in 2.7: amctrl.prx avcodec.prx game_install_plugin.prx iofilemgr_dnas.prx irda.prx mm_flash.prx psheet.prx usbacc.prx usbcam.prx usbgps.prx usbgps_serial.prx usbmic.prx usbpspcm.prx video_main_plugin.prx seems camera support is there now (although I don't think the actual ...

thanks for the update PspPet :)

you could try replacing the prx files in the data.psp, although if it relies on new 2.7 syscalls it most likely won't boot still. You cannot actually decrypt a prx unless you can run kernel mode code, and as far as I am aware, the 1.00/1.50 firmwares do not possess the required keys to decrypt this...

The LocoRoco demo appears to be a simple signed EBOOT. Editing the PARAM.SFO will allow you to launch it on lower firmwares than 2.7, but it doesn't really start before producing an error popup of 80020001 - the only meaning we have for that is "Error". Possibly it's an unresolved NID for...

neat stuff :)

0okm0000 are you able to read the NAND flash of fw 2.6? If so it would be very usefull since we could then get the decryption keys for 2.6 PRX modules

nice program, works great:)

ah, thanks for the info TyRaNiD, guess I should leave that to the hardware devs ;)

Mathieulh wrote: I think that hardware hacks will be required to decrypt the newer IPLs from now on. that's a shame tough :/

most likely :(

yes there is no 1.0 update, if you have a 1.0 update eboot it is the debug firmware which will brick your psp

You need the 3rd part called iplplayload The best would be to set psardumper to extract the files without the use of the ipl decryption routine to get the encrypted ipl as psp_ipl.bin Then use another app using the ipl decryption routine (you can get it either from psardumper or from Nem's infos) a...

In fact I don't think that the decryption keys changed either (I might be wrong tough) , at least I can decrypt my prx modules from my 2.60 games using the 2.00 key.... Otherwise if the key indeed changed you can get it form the mesg_led.prx file (that's probably how psppet retrived the other keys)...

Mathieulh very nice info, i was able to get the modules :)

i think i will look up on scePSAR_Driver, but yes you are probably right about not much changing between 2.5 -> 2.6 other than the decryption keys

I doubt so because the scenand API is only "officially" used durring an update and the scenand API is called by the iplupdater module (located in the updater's data.psp) and that module doesn't seem to change from 1.50 to 2.60 updater. Beside I don't know how the updater would be able to ...

I tried it.. but the EBOOT won't load, gives me "The game could not be started" error 80010002. :/ btw, I thought sceKernelLoadExec() reboots the kernel so would the CPU change stay in effect? heres my code: #include <pspkernel.h> #include <pspdebug.h> #include <psppower.h> #define printf ...

Theres a program that I would like to run @ 333MHz

would it be possible to start up an eboot from vsh, have it set the cpu speed, then load the desired program?

if someone could give me sample code that I could build off of or compile itd be greatly appreicated :)