Group: Members
Posts: 1496
Joined: 2-March 04
Member No.: 104181
No. They aren't and never have been. Then problem was something else. There was a problem with the code decrypting the eeprom, but I fixed that (hopefully) and will update xboxhdm soon. The official linux locking tool (from xbox-linux) still have this bug.
Group: Members
Posts: 80
Joined: 6-January 04
Member No.: 89387
Xbox Version: v1.1
I've got a question on cloning cause the tutorial doesn't really go into detail. does it support lba48 drives for cloning? Specifically, will it clone a full 120GB to a 200GB? would it be faster then ftp?
Group: Members
Posts: 1088
Joined: 28-May 04
Member No.: 122369
Xbox Version: unk
360 version: unknown
QUOTE (ddkore @ Jul 29 2004, 12:13 PM)
I've got a question on cloning cause the tutorial doesn't really go into detail. does it support lba48 drives for cloning? Specifically, will it clone a full 120GB to a 200GB? would it be faster then ftp?
Group: Members
Posts: 1020
Joined: 8-December 03
Member No.: 80325
QUOTE (adil786 @ Jul 29 2004, 12:38 PM)
i dont see why not.
I don't have a definitive answer on this and would like to know.
Say if the original F: is only 80G but the new one(use to the extend of 137G) is 100G, would that affect the FAT ? If yes, would it be all wrong if I just clone it from old to new ?
Group: Members
Posts: 1496
Joined: 2-March 04
Member No.: 104181
If you just do a simple clone this way the F: on the new drive will also be 80 Gb. The FAT filesystem is transferred also - I guess cloning is a good name
To get access to the rest of the drive you would have to reformat F: (data will be lost) to let it take up the rest of the drive or define a G: partition (F: will be left intact).
This post has been edited by ldots: Jul 29 2004, 12:10 PM
Group: Members
Posts: 1020
Joined: 8-December 03
Member No.: 80325
QUOTE (ldots @ Jul 29 2004, 01:12 PM)
If you just do a simple clone this way the F: on the new drive will also be 80 Gb. The FAT filesystem is transferred also - I guess cloning is a good name
To get access to the rest of the drive you would have to reformat F: (data will be lost) to let it take up the rest of the drive or define a G: partition (F: will be left intact).
thanks.
This would mean the current linux partition table scheme(in the cvs, for supporting G) would be dead wrong. I think I would make some patches to it.
Group: Members
Posts: 1496
Joined: 2-March 04
Member No.: 104181
Come to think of it I believe the current hacked bioses only allow the F+G scheme to let F take up to 137Gb and G the rest or to let F take it all. Dont think you can let F be 80 Gb and G the rest.