Hi all,
Ok so my new 2.5" 1tb drive has just arrived today to replace the 320gb drive that is currently in.
Rather than go through the process of hex editing, or making an image of the older drive like I did in the past (wouldn't be so bad if it was only a 20gb drive)....I'm just going to copy the 290gb or so from the old drive to an external USB drive (or ftp)...format the new drive in the 360, and then copy it back again bit by bit from USB. At least that should be a bit tidier.
I know nowadays, you can use hdd_compat_partition_fixer_v1 to restore the xbox compatability partition......but what I'm not sure of is, does it also create the cache partition 0?
Want to be sure all 3 partitions will be available before I start the long process of transferring it all....as I have a feeling may end up with only 2 partitions then.
IIRC if you format a regular drive with the 360, it only creates a single partition, and not all 3.....so wouldn't following the usual guides for hdd_compat_partition_fixer_v1 still have the same problem of a missing partition (and potentially more problems as a result)
Ok so my new 2.5" 1tb drive has just arrived today to replace the 320gb drive that is currently in.
Rather than go through the process of hex editing, or making an image of the older drive like I did in the past (wouldn't be so bad if it was only a 20gb drive)....I'm just going to copy the 290gb or so from the old drive to an external USB drive (or ftp)...format the new drive in the 360, and then copy it back again bit by bit from USB. At least that should be a bit tidier.
I know nowadays, you can use hdd_compat_partition_fixer_v1 to restore the xbox compatability partition......but what I'm not sure of is, does it also create the cache partition 0?
Want to be sure all 3 partitions will be available before I start the long process of transferring it all....as I have a feeling may end up with only 2 partitions then.
IIRC if you format a regular drive with the 360, it only creates a single partition, and not all 3.....so wouldn't following the usual guides for hdd_compat_partition_fixer_v1 still have the same problem of a missing partition (and potentially more problems as a result)