SKEPTiCK
Member
Ok, so I am having issues with very specific parts of the ps3tools collection and I don't know why becuase everything was working good until I made some (slightly accidental) changes to the registry... and yes, I have had this problem in the past on my Windows 10 laptop which made me assume that it was just a W10 issue but now that my laptop is dead and I'm stuck on Windows 7, well, it can happen on Win7 too.
So, here is the initial process of everything I did before screwing up the registry / certain apps
1. Installed ps3tools collection 4.8.1.exe to:
2. Copied "MSVBVM50.DLL" into these 3 directories:
5. Added PKG_ContentID & BruteForceSaveData to DEP in Adv. System Settings > Performance
After that, everything launched fine (mmTM GUI, PKG_ContentID, Scetool GUI, etc.)
The only thing I had left to get working was PKG Tools for the right-click context menu.
6. Installed "remove_ps3tools_file_associations.reg" to the Windows Registry
Finally, AFTER ALL THAT, the PKG Tools in right-click context showed up and worked!
But alas, it is not working now & there were 2 other issues prior to the context menu breaking.
So then I thought that maybe the registry breaks had something to do with it. What I mean is how:
and yes I'm aware of commands that come after such as "%1" which is the only one that is barely still working now. The only 2 options that work for me from right-click PKG Tools are:
I had basically tried for 12 hours straight, at this point, I want to make my own right-click context menu.
Initially, I was just trying to make an icons pack + more sorted folder system for the tools collection but that "tools" folder is too heavy to tackle & can cause alot of issues if you drag folders out of it. I also made folders for "pkg tools", "resigners" that were in the same directory as "tools" but now I have to do this again.
The lesson basically is that having PKG Tools work from the right-click context menu is somewhat of a one-chance opportunity it seems, one chance as in... If you do get it working, you better pray on your registry that it stays that way. Because if that application called "PKG File" stops working then you will have a very hard time getting to the root of how & where it runs from when it is not there if you look in your system's applications... and even if you completely uninstall ps3tools, purge it from the registry or rewind your PC to an earlier time you will find out that it is still probably broken when you bring it back.
I am not able to factory reset at this time and as for manually trying to fix it, I give up.
So, here is the initial process of everything I did before screwing up the registry / certain apps
1. Installed ps3tools collection 4.8.1.exe to:
- C:\Program Files\PST00LKIT\ps3tools
2. Copied "MSVBVM50.DLL" into these 3 directories:
- "C:\Program Files\PST00LKIT\ps3tools"
- "C:\Program Files\PST00LKIT\ps3tools\tools"
- "C:\Program Files\PST00LKIT\ps3tools\tools\BruteForceSaveData"
- "C:\Program Files\PST00LKIT\ps3tools\tools\scetool"
5. Added PKG_ContentID & BruteForceSaveData to DEP in Adv. System Settings > Performance
After that, everything launched fine (mmTM GUI, PKG_ContentID, Scetool GUI, etc.)
The only thing I had left to get working was PKG Tools for the right-click context menu.
6. Installed "remove_ps3tools_file_associations.reg" to the Windows Registry
Finally, AFTER ALL THAT, the PKG Tools in right-click context showed up and worked!
But alas, it is not working now & there were 2 other issues prior to the context menu breaking.
- when I opened a .pkg with 7zip, it overwrote itself as the default handler through whole registry
- also, CCleaner flags ".PKG" as unused file extension, had chance to keep but opted to delete
- Later, when growing frustrated, tried fully removing .PKG from associated filetypes in regedit
So then I thought that maybe the registry breaks had something to do with it. What I mean is how:
- RegEdit will shorten "C:\Program Files" to "C:\PROGRA~1" in command folders
- RegEdit will shorten "C:\Program Files (x86)" to "C:\PROGRA~2" in command folders
- So, what I had was "C:\PROGRA~1\PST00L~1\" etc. through the whole registry
- I manually went through registry & replaced every single instance of these breaks
- I've even re-installed the tools 3x to C:\Users\DELL\6CHARS to shorten paths more.
- Also tried restoring system/registry to 3 days ago before doing any of this.
- I set commands for the right-click PKG tools in regedit, but they only work for 1 use
and yes I'm aware of commands that come after such as "%1" which is the only one that is barely still working now. The only 2 options that work for me from right-click PKG Tools are:
- "Extract to current path..." and "Split PKG"
- PS3 Splitter crashes when trying to do anything
- PS3 Games Datatabase crashes shortly after boot
- PS3 Game Updates won't open, a very fast message with lock flashes for less than 1 second
- When using PKG_ContentID to check a PKG, it crashes saying "PKG File (has stopped working"
I had basically tried for 12 hours straight, at this point, I want to make my own right-click context menu.
Initially, I was just trying to make an icons pack + more sorted folder system for the tools collection but that "tools" folder is too heavy to tackle & can cause alot of issues if you drag folders out of it. I also made folders for "pkg tools", "resigners" that were in the same directory as "tools" but now I have to do this again.
The lesson basically is that having PKG Tools work from the right-click context menu is somewhat of a one-chance opportunity it seems, one chance as in... If you do get it working, you better pray on your registry that it stays that way. Because if that application called "PKG File" stops working then you will have a very hard time getting to the root of how & where it runs from when it is not there if you look in your system's applications... and even if you completely uninstall ps3tools, purge it from the registry or rewind your PC to an earlier time you will find out that it is still probably broken when you bring it back.
I am not able to factory reset at this time and as for manually trying to fix it, I give up.
Last edited: