bstronga Wrote:pspbtknf.bin - m33 no umd driver
pspbtlnf.bin - sony no umd driver
Ok so let me get this striate, I use the sony no umd driver so do I just replace pspbtlnf, or do I replace both pspbtknf.bin and pspbtlnf.bin?
Im sorry if this is a noobish question lol, I just want to make sure.
To ZiNgA BuRgA :p...
I write my tool... But for the "path" position is declare on 2 bytes...
For example "0D01" and in Hex Workshop the Value is 269... but I don't made a function (in Visual Basic) for convert the position to the good value...
If you would help me ?
Thanks in Advance !
this is a beauty mate thanks bro man you guys are incredible
Ac_K Wrote:S***...
ZiNgA BuRgA I need your help in VB !
If you ready contact me by MP please !
I don't do made that I want !
What's MP?
Ac_K Wrote:To ZiNgA BuRgA :p...
I write my tool... But for the "path" position is declare on 2 bytes...
For example "0D01" and in Hex Workshop the Value is 269... but I don't made a function (in Visual Basic) for convert the position to the good value...
If you would help me ?
Thanks in Advance !
Sorry, do you mean how VB (ghey-ly) is always off by one? You can always just add one to the address.
For example, if you want to change byte 0x50, you'll need to seek at &H51
Argh Update 3.51 M33-7 have changed the two new bin files (pspbtknf.bin & pspbtlnf.bin). So the vsh.prx bug is there again....
Undertaxx I'm using the ones posted here on the m33-7 update and it seem to work ok,until Bstronga updates 'em
(If it's needed)
Where posted here ? Anyway the new files are 5kb diffrent in size so i don't think it's a good idea to flash the one's from 3.51 M33-6 back (11kb).
yes I'm using the files from here (for m33-6)and no problems yet.
have tried everything in xmb,browser,homebrew,iso,umd all work.
have modded vsh.prx, paf.prx ,vshctrl.prx and .rco's (even your cool osk.rco).
No conflicts so far.
they just removed unnessary listings...
Thanks for the update Bstronga, Your quick with the quickness:yes: