It's really best to partition the disk from the Terminal when booted from the OS X install CD/DVD, I outlined how to do that.
if there are scenarios (other than user error) where the mini-CD can cause that a mini refuses to boot from a tiger CD we need to fix that on another level.
aand for now i assume a user error or something with USB - because why would a mac not boot from a volume only because some other volume on aanother drive isnt right?
Myself (occasionally being the involuntary practitioner of user error)…
have just discovered that using Drive Setup 2.1 on the “mini-mod” v.8 install disk, and then two-partitioning the drive before installing the “mini-mod” v.8 software… the mini then allows the C-boot install of Tiger 10.4 (from single DVD)
AND even Tiger 10.4.6 (also from single DVD)…
whereas before, I invoked the Open Firmware method to boot from the Tiger install DVDs (when I had used Drive Setup 1.9.2 previously, which
would not allow the Tiger C-boot).
Yet another reason to use Drive Setup 2.1 when installing the “mini-mod” v. whichever number?
In other, related news…
Last night I went ahead and ran the comparison between the two Drive Setups on a 1.25 GHz mini with a (probable) 4200 RPM Seagate 80GB HD to check which Driver version was installed and it checked out… 3.25 vs. 3.3 (as expected). Quickbench results weren’t as dramatic as with the 1.5GHz with Zheino, but there were improvements. Suppose that with a slower drive, one can’t expect that much drama.
Re-initialized a 1.25 GHz mini with Drive Setup 1.9.2 from the v.8 install CD and it installs HD Driver
3.2.5 …whereas Drive Setup 2.1 installs HD Driver version
3.3. QuickBench comparisons for both (below) show a slight increase in performance with the 80GB Seagate standard HD. Not nearly as dramatic as the Zheino results in the 1.5 GHz mini… but still, a little boost in some areas as the XFer sizes increase.
Did not check cold boot times but I did discover that my earlier report of 50 seconds on the 1.5GHz mini was
incorrect. Had timed that with the 1.92 Drive Setup on the 1.5GHz with the 3.25 HD driver in place. After that discovery, re-initialized the 1.5GHz with Drive Setup 2.1 and clocked that cold-boot @ 38 secs. A mere 4 seconds more (without any pruning) than my previous 34 second, best…
So, there is no 16 second increase in boot time when using 2.1.
(The increased cold boot time came with 1.9.2.)
My apologies. Erreur de l'utilisateur!
FireWire and frozen mouse noise, later.