I use se plugins pack for DAX custom fw. If you can't find it, let me know and I'll attach it here. You put the se plugins folder in the root of the memstick and then go in recovery to enable them. After that, just hold select and hit L to take a shot or R to capture video (but will slow you down ALOT).
Intel Core 2 Duo E6600 | 2 GB DDR2 RAM | GeForce 7900 GTX
2.5 TB Hard Drive Space | Windows XP Pro SP2
Official betatester of PCSX2 and Co-owner of General Emulation
You can use SCEP plugin too. With it you can take screenshot, shutdown, restart, overclock. Just press select. To take screenshot ingame, I'd prefer Cwcheat. 3.03 OE is your choice for custom XMB theme. It's safe. But, with 3.10 OE, custom XMB more comlicated for me. Just wait for 3.30 OE and see what we can do for custom XMB.
If you're brave, you can change you topmenu and waves since you're running 3.03 OE-C. However, this requires access f0 (NAND) through USB and can be dangerous if you have an accident.
Intel Core 2 Duo E6600 | 2 GB DDR2 RAM | GeForce 7900 GTX
2.5 TB Hard Drive Space | Windows XP Pro SP2
Official betatester of PCSX2 and Co-owner of General Emulation
Not if you back-up the topmenu file then change it. If anything does happen just enter Recovery Mode and replaced the bad topmenu file with the back-up and the psp will be as good as new!!! One of the advantages of Dark_Alex's Custom Firmwares!!!
Most memorable quote on Generalemu: "But when I see the name refraction, I go "Wow, thats a cool f***ing name." -MireTank.
Yeah, I know about recovering from USB through recovery mode, and pretty much if anything in VSH gets deleted/modified, it won't fully brick you, but if you're not careful and you start digging around in the other folders while in the f0, you are really at risk of hurting yourself, which is the only reason I brought it up. Any time there's a chance of bricking, I like to give people a strong warning about it, cause you never know.
Intel Core 2 Duo E6600 | 2 GB DDR2 RAM | GeForce 7900 GTX
2.5 TB Hard Drive Space | Windows XP Pro SP2
Official betatester of PCSX2 and Co-owner of General Emulation
- Copy oeupdmaker and oeupdmaker% to /PSP/GAME if you are in 1.50, or to /PSP/GAME150 if you
are in any SE/OE version. Get the 1.50 and 3.30 Sony updaters (of any region, because all are
currently the same), and copy them in the oeupdmaker directory with the names 150.PBP and 330.PBP.
Execute the program, and it will generate the DATA.DXAR file. Although the program will check its
integrity at the end, you can also check it with the following checksums:
- Copy 330oeflasher and 330oeflasher% to /PSP/GAME if you are in 1.50, or to /PSP/GAME150 if you
are in any SE/OE version. Move the DATA.DXAR to 330oeflasher directory.
You need 75% battery, although you can skip this if you pressed L+triangle while loading the program.
Changelog:
- Updated from psp firmware 3.10 to 3.30
- Fixed a bug that could have caused inestability in 3.10 OE after recovering from sleep mode.
- Patched a protection that prevents the firmware to load higher firmware modules.
popsloader note: it won't work on 3.30 OE due to sony rearranging again the module list of pspbtcnf_pops.
(thanks sony for destroying my backwards compatibility again ¬¬ ).
I'll make a new version one of these days to support all current pops in 3.30 OE, 3.10 OE and
maybe 3.03 OE-C.
A lil late there Shendo. I flashed to it last week when it was released. Damn Sony though. Just a few days after DAX brings this out, they go and release 3.40......
Intel Core 2 Duo E6600 | 2 GB DDR2 RAM | GeForce 7900 GTX
2.5 TB Hard Drive Space | Windows XP Pro SP2
Official betatester of PCSX2 and Co-owner of General Emulation
This post was last modified: 04-19-2007 09:02 PM by General Plot.
Same here plot. I'm on 3.30 OE-A not far from the release time. And then change icons, battery bar, sound bar etc. There are Disc load speed option for popstation. I'm happy
Damn Sony though. Just a few days after DAX brings this out, they go and release 3.40......
