Ir al contenido principal

Cómo usar el PSP con 3.52 M33 (y demás custom firmware 3.x)

Hasta la fecha, el firmware 3.52 M33-3 es el firmware más completo, siendo relativamente fácil de instalar.

El 3.71 es mucho más complicado y creo que no tiene ninguna ventaja tangible.

Primero consulta esta guía completa para instalar el firmware 3.52: http://forums.qj.net/f-guides-hacks-homebrew-and-emulators-43/t-guide-installing-351-custom-firmware-get-help-here-114299.html#post1673294

Pero lo que nadie te dice es cómo usar este custom firmware. He aquí sus características principales:

  • Kernel 1.5 - Hay que instalar los programas (ya sea 1.5 o 1.0) en el directorio /PSP/GAME150/ no en ../GAME
  • ISO auto-loader - Solo coloca las imágenes de tipo .iso o .cso en /ISO/ y cada una aparecerá con un icono en el menú de "Game-Memory Stick" del PSP.
  • Se puede seguir utilizando el truco de __SCE__Nombre y %__SCE__Nombre para los programas 1.5 (en vez de Nombre y Nombre%) - de esa forma no aparecen los iconos de "Corrupted Data".
  • Menú VHS (importante) - Al estar en el XMB, da clic en el botón Home del PSP. Lo más importante en el menú es modificar cómo lee UMDs el PSP.
  • Emulación de UMD (importante) - Si cambiamos la lectura de UMD de normal a UMD emulation, ¡no se necesita ningún UMD físico cargado en el PSP para correr imágenes en /ISO/!
  • Modo "Recovery": Para empezar, antes de poder acceder a este modo, hay que apagar en duro el PSP (manteniendo hacia abajo unos 10 segundos el apagador o quitando la pila). Al prender de nuevo el PSP hay que mantener el botón R (como de "Recovery") presionado y voilá.
Espero no haber olvidado nada importante.

Felicidades a Dark Alex = M33
-Jorge Orpinel


Powered by ScribeFire.

Comentarios

Entradas populares de este blog

sqlalchemy ProgrammingError can't adapt type numpy.float64 - Python troubleshooting

Are you getting a

sqlalchemy.exc.ProgrammingError: (ProgrammingError) can't adapt type 'numpy.float64'
???

It's because psycopg (psycopg2) - which is used inherently by SQL Alchemy but if you're just dealing directly with alchemy you might not know this - has no idea how to make the numpy.core.numerictypes.float64 (complete type path: another thing they don't tell you) a string for SQL querying.

Simple solution, add:

# solution by Jorge Orpinel found at rehalcon.blogspotcom
import numpy
from psycopg2.extensions import register_adapter, AsIs
def addapt_numpy_float64(numpy_float64):
return AsIs(numpy_float64)
register_adapter(numpy.float64, addapt_numpy_float64)
somewhere in the program.

For a more complete reference of the problem see http://initd.org/psycopg/docs/advanced.html#adapting-new-python-types-to-sql-syntax

I don't git it.

A lot of people praise git. I liked it at first, now I don't geet it.

Some weird stuff I've found in git, in no particular order:

You can pretend to be anyone. Just change your [user] name and email in .git/config and commit away. As long as when you push you use valid credentials, the commits will be recorded as from someone else. (At least this is possible on GitHub, I know git doesn't implement any specific user access control.)
* I guess you could try to enforce signing commits but as anything besides the basics, that gets pretty complicated on git.Steep learning curve that keeps getting steeper. Ok: git init, git add, git rm -r, git commit -am, git remote add, git fetch, git merge -ff, git push and pull -u of course, git checkout -b, git reset --mixed, git revert HEAD ... Those are just some of the basics... Ever tried to incorporate git subtree pull -P prefix --squash > into your workflow? I have, it's not fun (keep reading).Its super complicated to collaborate…

Dockerize your Django App (for local development on macOS)

I'm writing this guide on how to containerize an existing (simple) Python Django App into Docker for local development since this is how I learned to to develop with Docker, seeing that the existing django images and guides seem to focus on new projects.

For more complete (production-level) stack guides you can refer to Real Python's Django Development with Docker Compose and Machine or transposedmessenger's Deploying Cookiecutter-Django with Docker-Compose.

Pre-requisitesAn existing Django app which you can run locally (directly or in Virtualenv). We will run the local dev server with manage.py runserver.A requirements.txt file with the app dependencies, as is standard for Python projects; including MySQL-python.Working local MySQL server and existing database. (This guide could easily be adapted for other SQL engines such as Postgres.)Install Docker. You can see Docker as a virtual machine running Linux on top of your OS ("the host"), which in turn can run con…