Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-03 Thread Ralph
Howdy, On Tue, 2008-09-02 at 09:22 -0700, Peter wrote: Make sure there is a break at precisely 131,072 MB, and place at least one bootable partition below the 131,072 MB line. The new properties (it is NOT a hack) remain active until a reset- nvram O.F. command is executed. It seems

Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-03 Thread Kris Tilford
On Sep 3, 2008, at 2:04 AM, Ralph wrote: It seems as though the break does not need to be precisely there. It just needs to be under the 128 GB barrier, as long as that is the only partition you would need to access in a pinch. I think you are wrong about this. I think it needs to be at the

Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-03 Thread Peter
On Sep 2, 2008, at 10:35 AM, insightinmind wrote: The new properties (it is NOT a hack) remain active until a reset- nvram O.F. command is executed. Out of curiosity ... is that something that can be re-done at each Startup? Set the disk size through Open Firmware at Boot Time?

Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-03 Thread billycar_G3-5
You say it is not a hack, and you may well be right. It appears that it is only a property that is negotiated between the firmware and the drive. A property between the firmware and the Apple ATA drive controller, not the HD itself. Actually. I don''t think always doing this at

Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-03 Thread Doug McNutt
If you want to avoid a no-man's land in a partition, the break should be at precisely 131,072 MB. A most interesting thread. I'm not about to use the patch but I do have a question and it's about the meaning of MB and GB in this context. It's not clear, especially with disk drives, whether

Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-03 Thread Charles Davis
To give you a very 'unsatisfying', but truthful' answer; It's all up to MARKETING. They use the terms as they wish, to make the drives seem as large as possible, with little regard for providing useful information for the consumer. Sorry!!! Chuck D. On Sep 3, 2008, at 7:51 PM, Doug

Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-03 Thread Peter
On Sep 3, 2008, at 4:51 PM, Doug McNutt wrote: If you want to avoid a no-man's land in a partition, the break should be at precisely 131,072 MB. A most interesting thread. I'm not about to use the patch but I do have a question and it's about the meaning of MB and GB in this context.

Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-02 Thread insightinmind
On Sep 2, 2008, at 9:24 AM, Michael B. in Cincinnati wrote: Folks, after Kris Tilford's kind suggestions, I pursued hacking my G4 DA to support large drives. I found a good deal on a 250 GB PATA drive at my local computer emporium (cheaper than a 160!), and replaced the dying 120 GB second

Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-02 Thread Peter
On Sep 2, 2008, at 6:24 AM, Michael B. in Cincinnati wrote: http://nanchatte.wordpress.com/2008/04/27/128gb-large-hdd-lba48- support-on-the-g4-cube-with -leopard/ It's an Open Firmware hack that essentially does the same thing through a different path. It's a little unnerving; when one

Re: Follow Up to G4 Large Drive Question - the Hack Works!

2008-09-02 Thread insightinmind
The new properties (it is NOT a hack) remain active until a reset- nvram O.F. command is executed. Out of curiosity ... is that something that can be re-done at each Startup? Set the disk size through Open Firmware at Boot Time? Realizing it should be effective until resetting nvram? do