Mem Stick problem - PSP3D.com - Sony PlayStation Portable News, Homebrew, Hacks, Reviews, Videos, Mods, Forums

jonnyp777 · #1 (**permalink**) 07-19-2006, 06:14 PM

Haven't noticed before, but when I put the firmware (dh) folder from devhook on my stick, it says the folder is only 18mb, but on disk properties it says it has 26mb used. i think it adds a little on my savedata folder too. what's going on here? i don't wanna be losing any room. can keep switching isos all the time mess up the stick?
and another ?: on the daxter iso, can i delete all the foreign language intro pmfs or do i have to replace and rename with a small or blank one? and what about the credits, animatic, and concept art pmfs as well? thanks.

Kyubi_Naruto · #2 (**permalink**) 07-19-2006, 06:17 PM

huuuhhh... remove everything from the memstick and see how much space is used pls... DONT FORMAT IT...

jonnyp777 · #3 (**permalink**) 07-19-2006, 06:23 PM

i already formated it (after putting everything on my computer) and it say it had 956mb free space out of 956mb. then i put everything back on (not including any isos) and it still has 10mb unaccounted for.

Kyubi_Naruto · #4 (**permalink**) 07-19-2006, 06:25 PM

hum... it is strange... maybe hidden files and folders or something like that...

chriscooke109 · #5 (**permalink**) 07-19-2006, 06:45 PM

There isn't anything wrong, it is probably savedata I have about 20MB of it.

Off Topic: jonnyp777 why have you still got "v2.6=I'm a fucking idiot" in your sig? You should be happy you did have a 1.5 now because of it, and you also have a usebar with it 2.6 owner aswell.

SLYgUy2098 · #6 (**permalink**) 07-19-2006, 06:53 PM

hidden files?

Kyubi_Naruto · #7 (**permalink**) 07-19-2006, 07:09 PM

who the hell s this tribalbase? hey, how do you think you are to come here and talk like that to others?

jcoolkatzerg · #8 (**permalink**) 07-19-2006, 07:32 PM

Quote:

Originally Posted by Kyubi_Naruto

hum... it is strange... maybe hidden files and folders or something like that...

No, it's not hidden folders. It's how drive manufactures rip you off. Seriously. Lets work though the math:
The manufactures say they are giving you 1 gb, right? Look on the box, and somewhere it will (or, it should by US law) say that 1 gb = 1,000,000,000 bytes. This is all fine and dandy, except when a computer (i.e., psp) calculates the drive size. Computers work in base 2 (0 and 1), not base 10 (0, 1, 2, 3,...., 8, 9). For them, 1 gig is equal to 1,073,741,824 bytes (2^30 bytes). So, if we convert the manufacture's 1,000,000,000 bytes to megs, we get 953 megabytes (roughly, this can vary a little due to some estimation on the manufacture's part), and that is your problem. And no, there is no way around it, and the manufactures aren't going to change anytime soon. So the problem is not with your memory stick, your psp, or you. It's with the damn manufactures.

Oh, and if you don't trust my math, just google it.

As for the topic starter, your problem has something to do with what is called allocation. This is where the computer "sections" it's hardrive into indiviual sectors because it can't possibly address every single possible byte. Useing the example above, in order for your psp to find every single byte on the memorystick, it would need to proccess an address that is 30 bits long (0x000000000000000000000000000000, would be the address for the first byte on a one gig stick). Remember, a byte is only 8 bits long (00000000). So to find one byte, it would take 4 bytes in a file table. As you can see, this is very unpractical from the computer's point of veiw. So it "allocates" or sections the drive into smaller pieces, the default for a one gig stick is 4 kilobytes. When a file is saved, it is put into a block of sections, and is rounded up to the nearest 4 kb.
An example of this in action: create a blank txt file in your memory stick. Then click on it's file properties. You'll see that it's real size is 0 bytes, but it's size-on-disk is 4 kilobytes (or whatever the alocation size is). So whenever you save a file, it can waste up to 4 kb because of alocation. The only way around this is to not have so many files, which is impossible with dev hook because the dumped firmware needs all of those files to run.

jonnyp777 · #9 (**permalink**) 07-19-2006, 07:37 PM

thanks for all the help. and i just haven't gotten around to changing my sig yet, i'll do that right now. and i did figure out the daxter thing too. i was able to compress it down to 466mb by relinking some at3 and pmf files using umdgen. and what was with that random comment by tribalbase? whatever man. thanks again.

Michael M. · #10 (**permalink**) 07-19-2006, 07:39 PM

Actually, jcoolkatzerg, that's not correct.

FAT-formatted disks are set up so that a file must take up at least one disk allocation unit. Depending on the size of the unit, this could mean that a one-byte file takes up 4KB on disk. Files also cannot share allocation units. So if you have a bunch of one-byte files on a disk with 4KB units, they'll each take up 4KB. This could mean that 100 bytes' worth of data takes up 400KB on disk.

"Size on disk" is the total size of all the allocation units used by the data for which you're getting the properties.

And yes, there's a way around it: Format your disk with a smaller allocation unit size. However, the smaller the allocation unit, the more each file will take up, so the longer it'll take to read/write the disk.