Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It faulted out again. So I will take your advise and try again.
I can't help but think it falls on how Apple's firmware and boot sector in GPT are setup (non standard for GPT used by any other developer).

I'll be up, and keep checking back. So let me know how it goes. :)

I've given this proceedure to other members, who got it to work successfully. Yours is a little different, as you're adding it to an array. But that's just the added step of creating the array in the RR2642 firmware, and loading an additional set of drivers during the Windows install. The array's already set up, isn't it?

So you should only need to proceed with the installation and add both sets of drivers. ;)

Not complicated at all, so good luck. :)
 
I can't help but think it falls on how Apple's firmware and boot sector in GPT are setup (non standard for GPT used by any other developer).

I'll be up, and keep checking back. So let me know how it goes. :)

I've given this proceedure to other members, who got it to work successfully. Yours is a little different, as you're adding it to an array. But that's just the added step of creating the array in the RR2642 firmware, and loading an additional set of drivers during the Windows install. The array's already set up, isn't it?

So you should only need to proceed with the installation and add both sets of drivers. ;)

Not complicated at all, so good luck. :)

I have now prepared a clean new USB stick, deleted the array and build it again. Then started Install DVD and loaded only RR2642 driver. Windows could not install on unformated RAW space. Partioned it from the Install program using "NEW" and it was accepted for installation. Files being expanded now once again. See how this goes......

Edit: failed again

I'm deleting the array again and will do something different with COA input.
 
I have now prepared a clean new USB stick, deleted the array and build it again. Then started Install DVD and loaded only RR2642 driver. Windows could not install on unformated RAW space. Partioned it from the Install program using "NEW" and it was accepted for installation. Files being expanded now once again. See how this goes......

Edit: failed again

I'm deleting the array again and will do something different with COA input.
It will need to be formatted. I figured it was, as it's not a true hardware controller. Simple fix. :)
 
Actually it was kind of over formatted. It used to be a Bart PE and was partitioned as an active partition. I just formatted it and the acvtive partition wasn't erased. I reralized it when I checked what went wrong this time.

Now I have partitioned and formatted it and I will be inputting the COA from the start because I may have an issue there as well.

Usually my 2006 maschine takes no anytime upgrade DVDs because they have multiple images which the 32bit EFI can't handle. Because of this I have nLited my original install DVD to get it down to one image. I may have done something with the COA input as well. So far I have skipped over the COA input but now I will put it in every time. So touch wood I may have eliminated another trip wire. :rolleyes:

I hope its not the effing disk.....

Edit1:

Arrrrggghhhh... next I try using the replicated disk. The RR2642 BIOS may be capable to boot it.

Edit2:

not working. I'm cleaning my install disk. if that will not work I will go 32-bit.

Edit3:

gave up on 64-bit

now files expanding with 32-bit replicated disk

Edit 4: nothing is working. I have gone to OS X and done a PRAM reset. The Monitor setting changed. I also checked the system disk and found ok. I checked the system privileges and tons of warnings. I'm now making a backup to another HDD and will then make an install with archive and repair. It will take some time. Hopefully the screen corruptions will be gone then and the failure to operate the Bios utility. So far I had an installed HDD of Vista in the system and have made all changes to the Win Utility of the RAID controller. There must be a serious problem with my OS X system because EFI does not interact correctly with the RR2642 BIOS.

EDIT5: I have completely set up my OS X from scratch and used 32-bit replicated original DVD. Still the same fault code. Googel tells me that I'm not alone with that fault. Apparently it happens when Windows looses the contact to the DVD drive during install. I have an original Sony/Apple DVD drive and it looks like it is not good. Perhaps I can use my LG SATA BR with an IDE Adapter. At least I can give it a try.

I have:

1. Made a new install of OS X
2. Put the controller in another slot
3. Flashed the RR Bios once again
4. Re-installed the Management software

From earlier trials it appears that Windows wants the drive partitioned and acvtivated in MBR, formatted in NTFS and non aktive. If someone thinks that is wron please shout at me.
 
What a MESS! :(

Couple of questions:
1. Your original disks consist of multiple .iso 's? (both OS X & Windows)?
2. Have you been able to make all the settings on the RR2642, given the screen issue?
(If not, or not sure, do you have access to another system, to stuff it in, and run the BIOS utility)?
 
What a MESS! :(

Couple of questions:
1. Your original disks consist of multiple .iso 's? (both OS X & Windows)?
2. Have you been able to make all the settings on the RR2642, given the screen issue?
(If not, or not sure, do you have access to another system, to stuff it in, and run the BIOS utility)?

1. We have a distro channel in Europe/Germany which is called system builder edition. I dunno if that applies in US as well. It is basically a retail minus the free service in the first couple of months. I believe it is an adaptation to EU law where MS was sentenced to unbundle HW and SW. Those licenses are technically like retail but cost 30% of what you pay in a shop if you grab them at Ebay used. All my licenses over the year were used SBEs.

One of the features here of 64-bit Retail and SBE is upgradebility. If you buy home premium you can upgrade to Ultimate. You basically load a particular image out of several which are on the DVD depending of your COA. So Business COA triggers loading Business, Ultimate COA triggers Ultimate. All images are allready on the disk.

Technically there is a parameter which invokes different images and the boot loader is supposed to cope with it. Until the 2008 models all apple bootloaders could not cope with this type of disk. But for the 2008 Mac Pro Model and for Unibody Apple fixed it. So all EFI64 Mac Pros can cope with multiple images and 2006/2007 m/cs can't.

2. I can run the management utility in Vista 64 from HDD. Bios utility is dead as a door nail. It works in automatic mode, i.e. it repairs the array when things go wrong, but from the first minute I cannot apply any setting at all. It simply doesn't react to any input. I have to go to Win off another HD to change things which is really shytti. I have a Shuttle which has PCIe graphics but no other slot. Perhaps I can run it with chipset graphics and get the 2642 alive in the PCIe slot. But what will accomplish that?
 
1. We have a distro channel in Europe/Germany which is called system builder edition. I dunno if that applies in US as well. It is basically a retail minus the free service in the first couple of months. I believe it is an adaptation to EU law where MS was sentenced to unbundle HW and SW. Those licenses are technically like retail but cost 30% of what you pay in a shop if you grab them at Ebay used. All my licenses over the year were used SBEs.

One of the features here of 64-bit Retail and SBE is upgradebility. If you buy home premium you can upgrade to Ultimate. You basically load a particular image out of several which are on the DVD depending of your COA. So Business COA triggers loading Business, Ultimate COA triggers Ultimate. All images are allready on the disk.

Technically there is a parameter which invokes different images and the boot loader is supposed to cope with it. Until the 2008 models all apple bootloaders could not cope with this type of disk. But for the 2008 Mac Pro Model and for Unibody Apple fixed it. So all EFI64 Mac Pros can cope with multiple images and 2006/2007 m/cs can't.

2. I can run the management utility in Vista 64 from HDD. Bios utility is dead as a door nail. It works in automatic mode, i.e. it repairs the array when things go wrong, but from the first minute I cannot apply any setting at all. It simply doesn't react to any input. I have to go to Win off another HD to change things which is really shytti. I have a Shuttle which has PCIe graphics but no other slot. Perhaps I can run it with chipset graphics and get the 2642 alive in the PCIe slot. But what will accomplish that?
1. Got it.

Here it's a little different, though similar in a sense. It's a single disk, and appears as a single .iso install to the system. But then Product Key tells the installer which parts to install.

2. Do you have access to a PC?
It's a PITA, but you could install the card and the drives, and change the BIOS settings as needed, and make any adjustments to the array as you see fit (i.e. stripe size). The settings would hold when transfered back the MP. :) Assuming this is possible, of course.

Perhaps I'm mistaken, but I'm getting the severe impression the EFI32 on your machine is the source of the issues. A real difficult situation. :( My limited experience with a MP, was a 10 day stint with an '08, which was EFI64.

Perhaps Tesselator could be persuaded to contribute (PM works, we've communicated this way before), as he is using a '06 MP. So perhaps he has some insight that would be useful. ;)
 
I just don't get it that they sell this piece of junk specifically for Mac Pros. They have an own page for this. Are we supposed to use the OS X, Windows and Linux drivers only separately? One at a time???? That doesn't mak any sense. If you sell this thing for a Mac Pro the buyer can expect that it works with EFI/Windows and not only with Bios/Windows. I even had to input my model to download drivers. After that kind of hassle you would expect they do it to accomodate your technical requirements. Are they just after marketing data?
 
I just don't get it that they sell this piece of junk specifically for Mac Pros. They have an own page for this. Are we supposed to use the OS X, Windows and Linux drivers only separately? One at a time???? That doesn't mak any sense. If you sell this thing for a Mac Pro the buyer can expect that it works with EFI/Windows and not only with Bios/Windows. I even had to input my model to download drivers. After that kind of hassle you would expect they do it to accomodate your technical requirements. Are they just after marketing data?
Are you referring to the RR2642? :confused: (I assume this is the case).

It was meant to be able to boot BIOS, so that means Windows and Linux. But they also expected it to be installed in PC's, not Macs (% wise anyway).

So the only OS X operation would be via drivers. But from a driver perspective, it shouldn't be restricted to one set of driver operation (just one OS at a time, obviously). It's not a full hardware card though, and I've not messed with FakeRAID controllers in some time. So I'm a little unfamiliar with the most recent models, though the methodology shouldn't have changed since I last had access to them. Seriously, as they haven't changed in their fundamental operation.

Unfortunately, I've never had a '06 - '07 MP, and have never had the oportunity to experience anythihng but an '08MP, which is EFI64. And I only had that for 10 days or so, as I discovered it wasn't right for me, and had to send it back in time. :rolleyes: (External enclosures were too expensive, and "ate" the savings the MP offered. With interest :p).

I've never been a big fan of Highpoint, particularly of my experience with their FakeRAID controllers (last time I used one, it was a disaster). Since then, I've wised up, and realized my needs/wants were worth switching to a proper hardware controller, but they aren't cheap. WAY more money than the RR2642. But given the specs, I'd have thought it up to the task as well. I actually still do, but it looks like a PC might be needed to make any changes to the firmware on the card.

And I'm still not 100% certain the EFI32 isn't still going to be an issue. Friggin' Apple, not willing to write EFI64 for their older machines. :mad:
 
Thx, a thousand times nano for your support. I think I will give it a try with the shuttle. there is not much else what is left to do. What exactly do yyou think is needed in terms of setup on the shuttle? Do I have to load a Windows system or would it de enough to partition it? Can you give me some more hints, please. A windows installation in a shuttle with dual Athlons will probly not work inas Mac Pro at all.
 
Status is now that I have connected everything on the Shuttle. I can for the first time address the BIOS management of the controller. There is no screen problem as with EFI. I have set up the array again although it was allready set up (via the Windows GUI). I have now installed XP32 drivers because the Shuttle runs with XP32 or XP64. What can I accomplish from there?
 
Thx, a thousand times nano for your support. I think I will give it a try with the shuttle. there is not much else what is left to do. What exactly do yyou think is needed in terms of setup on the shuttle? Do I have to load a Windows system or would it de enough to partition it? Can you give me some more hints, please. A windows installation in a shuttle with dual Athlons will probly not work inas Mac Pro at all.
:cool: NP. :)

Can you give me some details on the Shuttle?
You mentioned PCI slot in the PM, but is it rather a PCIe type (needed)?

All I was interested in the Shuttle for, was to install both the card and drives. Startup the system, and get into the firmware on the RR2642 to make any settings/adjustments as needed. You could also delete the stripe, and start over (recreate it). Just remember, you have to delete the existing set first.

This is just to make sure the card and array are set up correctly, given you've been having graphics issues and unable to view the information correctly (that's what I've understood at any rate). ;)
 
As I have posted above I have PCIe in the Shuttle. I can operate the BIOS interface, delete and set up array. I actually did this.

The question is how to get a MP bootable Vista64 on this array?
 
As I have posted above I have PCIe in the Shuttle. I can operate the BIOS interface, delete and set up array. I actually did this.

The question is how to get a MP bootable Vista64 on this array?

I can actually manipulate the arry with PartitionMagic. I'm getting really excited now!!
 
As I have posted above I have PCIe in the Shuttle. I can operate the BIOS interface, delete and set up array. I actually did this.

The question is how to get a MP bootable Vista64 on this array?

I can actually manipulate the arry with PartitionMagic. I'm getting really excited now!!
I'd read Tessellator's post, that BC 3.0 could be had NOW from non Apple sources. ;) Nevermind, saw the later posts. :p

Have you gone through any other setting in the firmware and set according to needs/desire?
I'd make sure, before doing anything else, while the access is easy and no OS has been installed. :)

Now you can go one of two routes:
1. Install the Windows OS while the array's in the Shuttle, then transfer. I'm not sure if this would work, but might be worth a shot (concerned about bootloader giving the option of OS X or Windows install). You may have more insight into this, as I've not had much time with OS X.

2. Go ahead and transfer the array to the MP, and begin the Windows install, following the previous proceedures (both AHCI & RR2642 drivers, REFRESH, select array). Finish, then run BC windows drivers.

Let me know which way you want to go, or if you have any questions on the firmware (RR2642) settings before moving the card out of the Shuttle. :)
 
I'd read Tessellator's post, that BC 3.0 could be had NOW from non Apple sources. ;) Nevermind, saw the later posts. :p

Have you gone through any other setting in the firmware and set according to needs/desire?
I'd make sure, before doing anything else, while the access is easy and no OS has been installed. :)

I have set everything as you said. Except cache. It gives me cache policy N/A when I create the array.

I can also hook up my Vista SATA disk via eSATA and I have done that. Perhaps I can clone this disk on the array. But that would almost too much to wish for.
 
I have set everything as you said. Except cache. It gives me cache policy N/A when I create the array.

I can also hook up my Vista SATA disk via eSATA and I have done that. Perhaps I can clone this disk on the array. But that would almost too much to wish for.
Yeah, it appears they only let you set cache for RAID5 then.

The clone might be worth a shot though. :) As mentioned earlier, I'm not sure how that's going to affect the MP's bootloader though. I'd think it OK if it's off the MP's copy, as the boot loader is already set (still sees the array as a single logical disk). The question is maybe the pointer would need to be changed (if the clone's disk is different than the array, it points to a non existant installation). Can this be set manually from OS X?
 
Yeah, it appears they only let you set cache for RAID5 then.

The clone might be worth a shot though. :) As mentioned earlier, I'm not sure how that's going to affect the MP's bootloader though. I'd think it OK if it's off the MP's copy, as the boot loader is already set (still sees the array as a single logical disk). The question is maybe the pointer would need to be changed (if the clone's disk is different than the array, it points to a non existant installation). Can this be set manually from OS X?

Is the lack of cache setting going to hurt me?

Actually you are right with ther pointer. It would fail to boot because the disk structure is completely different physically. I hate MS effing copy protection. You never get anything done easy. I bought the bloody OS for this machine and just want to run it from a different disk for christ's sake. OS X is so much better in this regard.
 
Is the lack of cache setting going to hurt me?

Actually you are right with ther pointer. It would fail to boot because the disk structure is completely different physically. I hate MS effing copy protection. You never get anything done easy. I bought the bloody OS for this machine and just want to run it from a different disk for christ's sake. OS X is so much better in this regard.
No, not really. RAID0 is really simple, but cache can help speed it up a bit, particularly on high end RAID cards. Unfortunately, too expensive to make it worthwhile, and there's no need to worry.

It looks like it's time to go ahead and physically transfer the card and drives back to the MP, and begin the Windows installation.
 
I have installed the RR Gui in XP and it tells me Cache is actually enabled for write and read.

I have connected the Vista64 drive to eSATA and selected legacy in the RR GUI. Now I can see the VISTA64 drive and read and copy everything from it although I guess it will not help me much.

I'm now expanding files during the Vista64 installation procedure. Hopefully it will at least make a full install on the Shuttle and give me a chance to Winclone later with the MP.
 
I have installed the RR Gui in XP and it tells me Cache is actually enabled for write and read.

I have connected the Vista64 drive to eSATA and selected legacy in the RR GUI. Now I can see the VISTA64 drive and read and copy everything from it although I guess it will not help me much.

I'm now expanding files during the Vista64 installation procedure. Hopefully it will at least make a full install on the Shuttle and give me a chance to Winclone later with the MP.
Odd with the GUI. It may be giving erroneous information, as it should match the firmware settings. If anything, you'd get additional settings in the firmware, though there's not much to that card.

Why bother with XP? Testing/diagnostics?

You're still going to try a Winclone installation method?
 
Christ, I'm getting the same fault again as with the Mac Pro.

I'm suspecting something if wrong with the driver of the card. This is outrageous.
When I boot again, I see that the array is actually disabled. I have to build it again. I must look for an updated driver.

Found a version 1.3 on HPT web site. The CD comes with version 1.0. Please let it be a buggy driver that they have fixed now.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.