That's the point - they SATA problems requiring vaious hacks means that Apple doen't give you the means to run it. Duh.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac Pro and Windows XP - Running from IDE
- Thread starter brockbr
- Start date
- Sort by reaction score
Yeah, seems pretty obvious to me that Apple should fix this. I mean, sure, it's a beta, they aren't obliged to fix it, but it would at least put the Mac Pro at parity to the standards they have set for the Windows experience on all of the other Macs.
I know that this is going to sound elementry, but how did you guys get this to work? I have a 120gb PATA drive connected as my master, DVD as slave. Disk shows up fine in Finder. When I run Boot Camp Assistant it only shows my "Mac HD" and wants to partition it. My PATA drive never shows up. DO I have to clone the image from my SATA to a PATA?
Thanks!!
Thanks!!
stealiesubee said:
I don't have my MP yet, but if I recall from other threads, I *think* you should just be able to put in your WinXP install disc and it will recognize the drive. From there you can use the XP installer to format the IDE drive. All bootcamp is good for is partitioning a drive (not needed with a separate drive) and collecting needed drivers. You don't really need it to install XP.
But then again... I'm talking completely out of my azz since I don't have my MP yet
someone please correct me if I'm wrong!!
some good news:
http://www.anandtech.com/weblog/default.aspx#287
Anand Lal Shimpi's Weblog
August 25, 2006
Mac Pro Update (sort of) - Friday, Aug 25, 2006 3:36 PM
Blank
Blank I wish I had better news for you all with this, but I've been trying to track down the cause of the Mac Pro PIO mode issues and so far I've come up empty handed. I've tried all avenues, the least successful of which has been going directly to Apple. The best I've gotten out of Apple is they are aware of the problem and are currently investigating a solution. No word on the cause or anything beyond confirmation of the problem.
I've upgraded the 2.0GHz Mac Pro I used in our review to 3.0GHz with a simple processor swap, it works just as expected and the only problems I ran into were just gaining access to the CPU sockets without gutting my hand. As user friendly as most of the case is, Apple doesn't seem to want you easily replacing CPUs. Luckily it can be done and you can buy these things from Newegg, so my recommendation is to go with slowest CPUs you can deal with today and wait for the prices on the faster ones to drop before upgrading.
Regular FB-DIMMs do work in the Mac Pro, and during normal usage you won't run into any problems. However, if you run a memory stress test (or I'm guessing if you are running a combination of applications that is very memory intensive) non-Apple modules will begin to overheat. I know Crucial is working on a revised heatsink design for their FB-DIMMs that will keep the modules cool enough in the Mac Pro, and I've been told to expect availability of those by the end of this month. I'll let you know how they turn out as soon as I get some samples in my hands. There are some other vendors that are currently shipping similar memory with the large heatsinks that seem to work fine as well, but I would stay away from any standard FB-DIMMs without more robust cooling.
Living with Rosetta on a regular basis has been fine, although I did need to upgrade the version of Dreamweaver I was using. For some reason, with Derek's X1950 XTX article Dreamweaver MX 2004 would crash if I clicked away to a different application and then switched back to Dreamweaver and tried to type in a table (without first clicking on the table cell my cursor was already in). Moving to Dreamweaver 8 fixed the problem, but be warned that Rosetta may not always play nice with your applications. Photoshop CS2 under Rosetta works just fine, but the application is clearly slower than other native applications. The easiest way to tell is to try quitting a bunch of applications in a row; all of the universal binaries quit almost instantaneously, the Rosetta apps take another second or two which ends up being quite visible. The performance impact also exists whenever you're interacting with the application and as I wrote in our Mac Pro review: it feels as if you're running 2 - 3x slower than you should be. By no means is Rosetta a deal breaker, but it's something that I want to have out of my hair as soon as possible.
http://www.anandtech.com/weblog/default.aspx#287
Anand Lal Shimpi's Weblog
August 25, 2006
Mac Pro Update (sort of) - Friday, Aug 25, 2006 3:36 PM
Blank
Blank I wish I had better news for you all with this, but I've been trying to track down the cause of the Mac Pro PIO mode issues and so far I've come up empty handed. I've tried all avenues, the least successful of which has been going directly to Apple. The best I've gotten out of Apple is they are aware of the problem and are currently investigating a solution. No word on the cause or anything beyond confirmation of the problem.
I've upgraded the 2.0GHz Mac Pro I used in our review to 3.0GHz with a simple processor swap, it works just as expected and the only problems I ran into were just gaining access to the CPU sockets without gutting my hand. As user friendly as most of the case is, Apple doesn't seem to want you easily replacing CPUs. Luckily it can be done and you can buy these things from Newegg, so my recommendation is to go with slowest CPUs you can deal with today and wait for the prices on the faster ones to drop before upgrading.
Regular FB-DIMMs do work in the Mac Pro, and during normal usage you won't run into any problems. However, if you run a memory stress test (or I'm guessing if you are running a combination of applications that is very memory intensive) non-Apple modules will begin to overheat. I know Crucial is working on a revised heatsink design for their FB-DIMMs that will keep the modules cool enough in the Mac Pro, and I've been told to expect availability of those by the end of this month. I'll let you know how they turn out as soon as I get some samples in my hands. There are some other vendors that are currently shipping similar memory with the large heatsinks that seem to work fine as well, but I would stay away from any standard FB-DIMMs without more robust cooling.
Living with Rosetta on a regular basis has been fine, although I did need to upgrade the version of Dreamweaver I was using. For some reason, with Derek's X1950 XTX article Dreamweaver MX 2004 would crash if I clicked away to a different application and then switched back to Dreamweaver and tried to type in a table (without first clicking on the table cell my cursor was already in). Moving to Dreamweaver 8 fixed the problem, but be warned that Rosetta may not always play nice with your applications. Photoshop CS2 under Rosetta works just fine, but the application is clearly slower than other native applications. The easiest way to tell is to try quitting a bunch of applications in a row; all of the universal binaries quit almost instantaneously, the Rosetta apps take another second or two which ends up being quite visible. The performance impact also exists whenever you're interacting with the application and as I wrote in our Mac Pro review: it feels as if you're running 2 - 3x slower than you should be. By no means is Rosetta a deal breaker, but it's something that I want to have out of my hair as soon as possible.
A possible solution can be found here:
http://web.mac.com/terrabit/iWeb/macpro/xp.html
I don't have my Mac Pro (yet) to try it out, though.
http://web.mac.com/terrabit/iWeb/macpro/xp.html
I don't have my Mac Pro (yet) to try it out, though.
brockbr said:
After doing this, wouldn't you just install the SATA drivers in XP and then clone the ATA drive to an SATA drive?
timswim78 said:
No, because it will still need to use the underperforming SATA drivers to communicate with the hard drive. The speed would be just as poor as if you'd installed on SATA directly.
A bit strange ....
What is the difference between :
"installing new S-ATA drivers and reboot"
and
"installing new S-ATA drivers in the install process of windows and finally reboot"
I wonder ....
What is the difference between :
"installing new S-ATA drivers and reboot"
and
"installing new S-ATA drivers in the install process of windows and finally reboot"
I wonder ....
Has it worked for anybody yet?chrismmx said:it dosen't work.
Well, it's at least awesome news that Apple has acknowledged it.
Yeah it works a treat, you have to reinstall i tried it both ways and the only way is intergrating the driver into the install the bonus is you can extract the boot camp drivers and add those so its a fully operational machine on boot 8) except firewire isight doesnt work damn it
GOOD WORK TERRABIT
GOOD WORK TERRABITUpdated Website Address
Due to bandwidth restrictions on the Dot Mac account, I have purchased a new webserver. The new address for the website is:
http://www.macprojournal.com/
or:
http://71.18.168.229 (if the above DNS entries haven't updated yet).
Terrabit!
aiongiant said:**CONFIRMED***
It WORKS!! Internal SATA2 going at a good 60MB/s
yayyyy
now time to buy another SATA2 drive for XP hehe
Due to bandwidth restrictions on the Dot Mac account, I have purchased a new webserver. The new address for the website is:
http://www.macprojournal.com/
or:
http://71.18.168.229 (if the above DNS entries haven't updated yet).
Terrabit!
I'm interested in re-cycling a '10Gb' IDE hard drive, in the spare optical-drive bay of my Mac Pro, for occasional Windows XP use (couple of games/couple of windows only apps).
Some ?'s though:
1) It seems I can hold the 'option' to boot to another drive, particularly to pick the Windows install CD for initial install etc - in which case would I even need to use Bootcamp?
2) If I don't need Bootcamp, I assume I could get away with a Windows SP1 installation disk and update from there? (where as Bootcamp required SP2)
Some ?'s though:
1) It seems I can hold the 'option' to boot to another drive, particularly to pick the Windows install CD for initial install etc - in which case would I even need to use Bootcamp?
2) If I don't need Bootcamp, I assume I could get away with a Windows SP1 installation disk and update from there? (where as Bootcamp required SP2)
so today I tried to do this but I ran into a couple problems. First of all, after I connected the IDE and extra power cable to my IDE hard drive and rebooted, neither the drive nor the superdrive showed up and in the case of the superdrive it didn't even mount at all. So I disconnected the IDE HD and restarted and the dvd drive worked fine. I would still like to be able to use the drive but I can not seem to figure out how to change the master slave settings-can someone tell me how to?
The Hard drive and DVD drive should have the settings for master / slave on the label, if not, you can find the info on the manufacturers website.
Cheers,