Thanks alot, is there any down side to changing firmwares to rebug 3.55.2
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
Thanks alot, is there any down side to changing firmwares to rebug 3.55.2
Im on rebug 3.55.1 and it worked fine then i updated to 3.55.2 and it kept crashing when i tried to run a game from mm it would say "connect the ps3 controller with a usb cable then press the ps3 button on the remote" then when i do that it will say the system cant run the firmware and that i would have to go to the recovery mode to fix it. so i ended up having to reinstall 3.55.1 and now its working. does anyone have any ideas on this ?
I had missed one crucial fact, but apart from that what you are saying here is mainly a reformulation of what I said earlier.
You say: "MM cache's it to internal"
I said: "For multiMAN itself Dean has implemented a form of NTFS drive access, ONLY for copying of files and folders"
And that is exactly what happens when "MM cache's it to internal". That stuff then gets copied to the internal drive.
What I had missed (and I really had missed this), is only that recent versions of MM apparently have implemented such automatic copying to cache on internal HDD not only for games, as was the first such implementation, but also for media files on NTFS drives. Since I myself have zero interest in that I had missed when this was added. I honestly don't see the point in an NTFS support which requires all the stuff on such a drive to be copied to internal drive before use. And it makes especially little sense for playing media files which should be done better over network without having to move the files from the PC where they usually originate (whether by downloads or by DVD/BD ripping).
I'd rather see Dean develop similar access routines for the SMB network protocol instead, so that we can access network files on computers without having to run any special server on them. That would be truly worthwhile...
I think that is a misunderstanding. As I see it no real NTFS device driver for PS3 exists at all.(I believe NTFS driver is only usable through official Sony SDK in which Showtime doesn't use)
What does exist is a set of NTFS compatible device access routines, but not in the form of a device driver.
If it was a real device driver, then it would be possible for Showtime to use it even though based on a different SDK.
But since it is just a set of access routines implemented as part of the multiMAN source code, those routines (including all dependencies) would have to be ported into the Showtime source code, with adaption for the SDK it uses, in order to make a version of Showtime able to access an NTFS drive in the same way that multiMAN can do it.
That might be a worthwhile implementation for Andreas Öman and his friends to make (the Showtime authors), but I would not want Dean to invest much time on it, apart from sharing the relevant part of his sources.
Best regards: dlanor
I was reading alot about the rebug 3.55.2 and it said to make sure when you upgraded to be in normal mode and not rebug mode. But I thank the best way to do it is to reinstall the ofw 3.55 Than install rebug 3.55.2. But I still will wait alittle longer to find out how well it works. But please let us no if you try again and if it works better this way.
The PFS (NTFS) libraries were provided by anonymous people in precompiled binary format, to be linked during compilation. It means that nothing can be changed in these libraries.
These libraries provide few simple functions: Open, Stat, Seek, Read, Close. The issue for Showtime and these libraries is that it is impossible to compile showtime with psl1ght using libpfsm.a and libpmsd.a, because the second one uses Sony SDK specific calls (cellUsb********).
I see. This means that the situation with these NTFS libs is even worse than I was aware of.
Not only do they not implement a proper device driver (probably impossible under GameOS), like I already knew, but we also lack access to the source code of this access routine lib making reimplementation with modifications impossible. So even if definite bugs and limitations are discovered, there is nothing at all we can do about it.
Best regards: dlanor
There is a sticky for this discussion. http://psx-scene.com/forums/f191/rel...-55-2-a-93020/ (RELEASE - REBUG 3.41.3 and 3.55.2)
Thanks for all this awesome thingy![]()
Check out this thread about MM and rebug 3.55.2 problems. http://psx-scene.com/forums/f191/rel...20/index2.html (RELEASE - REBUG 3.41.3 and 3.55.2)
| « Previous Thread | Next Thread » |
| Tags for this Thread |