- #OPEN PS2 LOADER OPTION FOR VAMPIRE DARKSTALKERS COLLECTION UPDATE#
- #OPEN PS2 LOADER OPTION FOR VAMPIRE DARKSTALKERS COLLECTION FULL#
If we implement the actual PADEMU (the system that actively replaces PADMAN) instead of native support for the BT controller, then it will require resident code.
#OPEN PS2 LOADER OPTION FOR VAMPIRE DARKSTALKERS COLLECTION FULL#
Unfortunately, that would only work in FMCB and not in other software, since each software will have full control over the PlayStation 2. It might be because I am trying hard to rush through all these projects and their many silly problems, but I have been making a lot of silly mistakes lately. So the lesson here, is as some old advice goes - there is a risk involved when we comment out code while debugging. so libcdvd was (silently) failing because its semaphores were deleted by the EE kernel, but it couldn't be initialized because it thinks it already was initialized.
So while trying to get it to work, I commented out the code that deinitializes the RPC services. This shall become the new release, which will hopefully be the last one.Īs for how the glitch came about: I changed the DVD Player selection code for v1.96. So there is now probably some confusion over the version number.
#OPEN PS2 LOADER OPTION FOR VAMPIRE DARKSTALKERS COLLECTION UPDATE#
Fixed play history being updated twice, when a DVD Video disc is played.Īlso because I must have accidentally hit the "keep both files button", the previous update did not get overwritten.Added a call to deinitialize libpad to the FMCB Configurator, for stability after exiting.Fixed inability to boot DVDs from the browser, by re-addeding the accidentally deleted cleanup code.You do not have to download the new package, if you had no problems installing FMCB.įMCB + FHDB + installer project page (downloads at bottom): Hence there is less reason to keep the official workaround for supporting both CEX and DEX consoles, in favour of the simpler workaround of getting secrman_special itself to adapt to the DEX. I have no wish to deal with such randomly-occuring problems. At that point, it does seem like some part of the installer has entered an undefined state, since it is impossible to make another installation after that. Such a vague message is printed when an unrecognized error code is encountered. While I am all for keeping the modules free of unofficial code, it appears that rebooting the IOP between the signing of each file increases the odds of an "Installation failed" happening. Reverted change from v0.98 - the IOP will no longer be reboot between the signing of each file.