SMS and PFS Explorer

[leidout]

Create the partitions with PFS explorer. The maximum size is 1.5gb (not 1gb, as is popular belief). Multiple partitions are safe, i've used 4 partitions of 1.5gb each for at least 6 months with zero errors.

If your files are still bigger than 1.5gb each, just use a program like virtualdub or something like that to break them down into smaller pieces.

[emcepl]

If you were speaking of a bug/limitation specific to PFS Explorer, then I assume you are correct about it, having used it so much.

I used it a LOT (copied about 80-100GB), ran MANY practical tests (concerning audio/video stream corruption), talked with PPE's programmers and GadgetFreak (he told me that PPE has problems with ~1,5GB partitions; don't know why - didn't ask), and I came to the golden mean (stated above).
BTW. That way it's also easier to properly manage corrupted partitions

A partition size limit exists, due to the use of 32 bit offset indexing, which sets the safe limit to 4GB (2^32). But it is quite likely that some software will have problems with such sizes too, because they may treat indexes as signed values, reducing their effective usage to 2GB (2^31).

I don't see why any software would need to reduce this by another bit to 1 GB (2^30), but if that's something you know about PFS Explorer, I'll take your word for it.

Only one word: BUGS It is not a limitation. Don't know why (I don't have ANY idea about programming), but that's the way it is. Remember that PPE is in early beta stage (unfortunately abandoned ).

[lee99]

Thanks for all the replies, is it safe to have multiple paritions in your hdd or will that wear it out?

I want to try lee99's theory about the expanding, but my files aren't exactly 896 in size.

it does not matter,
most avi's are 700mb or 1400mb if you expand with 896mb fill it with a 700mb there will be like about 196mb left so you expand it again with 896mb.

it just not matter but if you have a 1400mb you have to expand twice with 896mb and not in once!

multiple partitions is ok here
i got like 5 partitions of 20gb and never had any problems.


and dlanor,
if i erase one avi, i replace it with another one.
never had a problem with that, maybe there will be problem like, if i erase more avi's in once.(over 1400mb)

[neiljames]

Man someone needs to pickup where e_gama and souljack left off. The programs' concept is just what's needed to transfer files to and from the PS2 HD.

I use leidout's method and so far no problems. I wish that I could just create 1 big partition using either PFS Explorer or DMS HDD Format Tool 1.1 and transfer as many videos or whatever type of file I wish to put into the partition I created without any problems.

dlanor... do you think you could manage programming PFS explorer? That'd be kick ass if you could and would I wish I knew how to program. Anyway... does anyone know how to get in touch with Gadget Freak?

Best Regards,

neiljames

[emcepl]

Have no fear, GF is working on it

[iamtheodork]

Yeah, that'd be freakin' awesome if someone could update the PFS explorer.

I really hate transferring files via network.

Plus by transferring through IDE cables, it goes in much much faster.

Thanks for all the responses, I plan on making multiple partions because expanding over and over seems a bit tedious.

/edit

I just created multiple partitions using PFS and now I can't access it via DMS to delete the partitions.

Anyway to delete them?

[Serdna]

Thanks for the information everyone!

A partition size limit exists, due to the use of 32 bit offset indexing, which sets the safe limit to 4GB (2^32).

Just to get it right... is the 32 bit offset a file system property or a driver one? I mean, are there 32 bit offset fields stored on the hard drive? (Sorry if this is an stupid question).

Finally, I suppose that any partition used as a sequential device (without deleting anything) won't misbehave even if created big (>4GB) in advance, will it?

[dlanor]

Thanks for the information everyone!
Just to get it right... is the 32 bit offset a file system property or a driver one? I mean, are there 32 bit offset fields stored on the hard drive? (Sorry if this is an stupid question).

That is a very relevant question, whose answer is of great importance to what we can do to change the limitation.

If it is only a driver usage limitation, then it can 'easily' (yeah right ) be fixed just by making new drivers, using 64-bit variables for such offsets. But if 32-bit offsets are part of the filesystem standard itself, as you say 'stored on the hard drive', then there is nothing to be done about it.

Someone really should take a deeper look at this, and report exactly how this limitation works, and what the long-term consequences may be of the workaround for using larger partitions. That would best be done by someone already well informed on the HDD driver internals, such as Gadgetfreak or romz, but if they (or others with similar skill) don't have time for it, then I will eventually do it myself. (No promise as to when though.)

Best regards: dlanor

Finally, I suppose that any partition used as a sequential device (without deleting anything) won't misbehave even if created big (>4GB) in advance, will it?

It appears that way, as many have reported success at such usage.

But if you ever make changes, you should try to 'fill in the holes' precisely, to avoid possibly harmful fragmentation.

Best regards: dlanor

[neiljames]

emcepl,

Has Gadget Freak told you of this?... (continuing the progression of PFS) Damn if it's true I can't wait till he's done with it. Any news on what he plans to do exactly? Will PFS have Winhiip integrated? Damn I hope it's true and he is making good progress

neiljames

[emcepl]

Has Gadget Freak told you of this?... (continuing the progression of PFS)

Yup

Damn if it's true I can't wait till he's done with it. Any news on what he plans to do exactly? Will PFS have Winhiip integrated?

Yup

Damn I hope it's true and he is making good progress

It is true
http://psx-scene.com/forums/showthread.php?t=46012 (WinHIIP 1.7.6)