Pax broken in leopard?

Before doing a fresh install of Leopard, I backed up my data files using pax. This is referenced at the following URL. http://developer.apple.com/macosx/backuponmacosx.html I had trouble restoring the files. I limited the archive volume size to 2gb because of the DVD file size maximum, and this resulted in 2 files. I restored from the 1st volume and expected pax to prompt me for the 2nd volume, as described in pax(1). "When required, pax will prompt for the pathname of the file or device of the next volume in the archive." Instead, pax exits after giving the following message. "pax: End of archive volume 1 reached". I am currently downloading Xcode so I can build my own pax. Next time I may try a multiple-volume zip archive.

My local build of pax was able to restore my files.
The Leopard pax utility cannot even create multi-volume archives.
$ pax -w -v -f volume.1 -x cpio -B 200k Downloads/About\ Downloads.pdf
Downloads/About Downloads.pdf
pax: User specified archive volume byte limit reached.

Similar Messages

Photoshop: values for type, brush, crop, lasso etc tools broken on Leopard

I posted this in answer to another thread, but decided that it may be helpful to some Photoshop users if it had its own topic:
The following is a technote copied from Adobe's forums, regarding the performance of several menus for key tool settings in Photoshop CS3 running in Leopard:
*Changing values for type, brush, crop, lasso etc tools broken on Leopard*
*Kirsten Harris - 08:58pm Nov 15, 2007 Pacific*
Adobe and Apple are working closely to provide a fix to a known issue running Adobe Photoshop CS3 and Photoshop CS3 Extended on Mac OS X Leopard (v10.5.1). Currently, when you enter values in numerical fields to set sizes for the brush, crop, marquee, lasso, type, and other Photoshop CS3 tools, those values revert to previously entered values when you try to apply them.
# While we have identified workarounds for some of the affected tools, this issue prevents people from working as precisely and intuitively as they expect. Providing a fix to customers is a top priority. Please note the following: The fix will be provided through an update to Mac OS X Leopard. Consequently, it is not part of the Photoshop CS3 (10.0.1) update.
# Apple is collaborating closely with us to get this fix incorporated into a Mac OS X Leopard update. No public schedule is available at this time, but both companies understand the urgency of this fix.
# As soon as the appropriate update to Mac OS X Leopard is available, we will immediately alert our Photoshop users.
Affected Photoshop CS3 tools: Art History tool, Blur tool, Brush tool, Burn tool, Color Replacement tool, Clone tools (all), Crop tool, Dodge tool, Eraser tools (all), Gradient tool, Healing tools (all), History tool, Lasso tools (all), Line tool, Magic Wand tool, Marquee tools (all), Paint Bucket tool, Pencil tool, Polygon tool, Quick Selection tool, Red Eye tool, Rounded Rectangle tool, Sharpen tool, Smudge tool, Sponge tool, Slice tool, Type tool
Workaround for tools with sliders: Instead of typing in a number, use the sliders to change the value.
Workaround for tools with pop-up menus: Enter a value for the size but don’t press Return/Enter to apply the value. Instead, choose it from the top of the Size pop-up menu to commit it.
Workaround for tools which do not have sliders or pop-up menus: For certain tools, such as the Line tool, you may want to set up presets that you can load to set common sizes. Alternatively, you can restart Photoshop CS3 to clear the problem. You will then be able to enter values again. However, the issue typically re-surfaces quickly.
If additional details come to light, our tech doc Values in numerical fields in Photoshop CS3 revert to the previous value in Mac OS X v10.5.1 (Leopard) will be updated.

Well, that's interesting! Here I thought the problem with my CS1 was just that it was too old, running in Rosetta and all, and would be fixed when I get my Xmas treat of CS3. Wonder if that means when the fix comes from Apple it will also fix the same problem in CS1? Of course, by then I'll probably have CS3.... Thanks for posting this, I would have been mighty annoyed to have plonked down my 200 bucks only to discover that I had the same bugs.
Francine
Francine
Schwieder

2 problems! - RAM module broken & Snow Leopard not loading

Hi,
I have 2 problems:
I got Mac Mini (late 2009 model, 2,26ghz, 2gb) upgraded from 2GB to 4GB from this Apple Premium Reseller (http://www.stormfront.co.uk/). When I got it back and switched it on and immediately got 3 beeps which indicated bad ram or logic board. The y took it back and said they sent it to their workshop in Exeter and fixed it. When I switched it on I still got 3 beeps. Took it back to the shop they said don't what to do and get the workshop to ring me back on Monday. At this point I'm fuming!!! So I decided to take apart the Mac MIni myself. Upon discovery that one of the memory modules is broken, I bent the bit metal back and it seems to ok after hardware tests and is working now. What can I do about this? I honestly did not break this and know it was the shop but how I van prove this? What would be done about a replacement as I have no longer sold, would I get a discount on brand new mac mini?
As mentioned above that I took it apart I cant load up Snow Leopard, I just get the Apple logo plus the spinning wheel I can hear some hard drive activity but does nothing ( I left it for 20 mins). I then booted from the SNow Leopard and ran disk verify it came up with errors and said to format and restore, which I have done via Time Machine. But I still get the Apple plus spinning wheel. I know the hard rive ok now because I can boot into Windows via bootcamp. So what I should do?
Any help would be appreciated.

it seems that it's not emptying trash for you. only emptying trash will actually free up space on the drive. what exactly happens when you empty trash? does it seem to empty?
click on the trash in the dock. is there anything inside?

IMovie 08 Broken in Leopard, but old version works

2.0 Core Duo Macbook Pro. Upgraded to Leopard, then upgraded iLife. iLife mostly works.
I movie is broken. I can start iMovie 08, but the things like NEW PROJECT, NEW FOLDER, are grey and unselectable. Other menu items are not grey however. I can't open old projects with it. If i drag an old project onto the imovie desktop icon, it just ignores it.
iMovieHD works fine.

I'm having the same issues with iMovie I imported 4 hrs of video over Christmas and the new year and edited it into 3.5hrs and then broke the edited version up into manageable smaller sizes for export to several DVD'S using iDVD but when I l ran imovie to do this,the next time i had time available to do this stage, I found the same issues as you ... I hope all this work has not been for nothing . . .
to check the problem was not with the old files I created a very small new project using the built in camera of only a few second and it has the same issues. . .
Maybe it's me but i can't find any references to this in Apples online support . . .
I the past i have used a commercial video editing and burning program on another machine but both need upgrading badly so i opted for a new Mac and the built in software . . . thinking this would be a better long term investment
At least I now know I'm not the only one with this problem . . . I just wish Apple would fix this issue . . . SOON
If I wanted unstable beta ware software i would have gone windoze . . .

Dual monitor setup broken in Leopard

There are numerous problems running an external Cinema Display from a MacBook Pro using Leopard. I've tried with 2 MacBook Pros (one 15", one 17") and 2 different Cinema Displays (24" and 30"). Not to mention everything was fine under Tiger. Both Leopard installations were "clean installs".
1. Closing the lid of the MBP doesn’t remove the screen from Leopard (Or Spaces).
2. When the MBP sleeps with a Display attached it never comes back onto the Display, only the MBP’s LCD.
3. Periodically the MBP refuses to wake when it’s connected to the display.
4. I can no longer use the power button on the Display to sleep/shutdown the MBP.
5. Simply plugging the Display sometimes causes it to wake (while the MBP is closed). In Tiger, I had to have the Power Adapter connected to wake my Sleeping MBP with the lid closed (as stated in the documentation).
Wonder if all this will be fixed in 10.5.1 (hoping)?

Firefox doesn't always play well with a multiple monitor setup and hardware acceleration.
Try to disable hardware acceleration.
*Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
*https://support.mozilla.org/kb/how-do-i-upgrade-my-graphics-drivers

Lightroom Is Still Broken in Leopard

Well here we are, Nov. 10th.
Lightroom Still isnt working in Leopard.
How close are we Adobe?

For 64 bit Carbon?
http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/6
Yeah, I know that for Adobe (and for Microsoft) it's a big deal. Because of the huge code bases and extensive support and code base that dates to pre-OS X days. Basically no "free" 64 bit support as many parts of the UI layer just ain't going 64 bit. Also given the "Hey when is Photoshop going to be 64 bit?" questions it's not something that isn't being considered :-)
These types of problems though really affect software products that have been around for a long, long time way more than they do other apps. Because none of these SDKs were available in System 6. Well if Photoshop were developed from the start on NextStep maybe it would have been easier but it's a fine line balancing the needs of what's good for the platform in the future and the needs of your existing user base (and the apps they must rely on).
I mean, you get apps like this that come out of nowhere:
http://www.naked.la/light/
Which largely rely on the OS foundations to do the work. Core Image is something that's really cool (modulo performance issues and hardware requirements) that can substantially reduce development time here. But if you're doing cross-platform and there's no Win32 equivalent then they aren't any help.
Anyway, regarding API choices and legacy compatibility and the like -- I'm glad I don't have to make those decisions :-)

How to maintain default folder view (broken when leopard clients connect)?

hi there,
we run 10.4 tiger server and have the problem that if 10.5 leopard clients connect to the share their changes to the folder view become the new default for everyone connecting after them. with 10.4 clients the default folder view is looked to the settings of the admin.
is there a way to bring back this feature with 10.5 clients connecting? lock the default folder view of shares?
this question was asked before by andy lowe (http://discussions.apple.com/thread.jspa?threadID=1571877&tstart=45) but never answered.

It's "show view options" in English. Also obtained by typing CMD+J
Those only apply to the top-level folder. Each folder you open uses whatever you've elected to use as the defaults. Select a folder, CMD+J, set the view as you desire, click on Use as Default button. That setting will be used for all windows that you open in the future that have never been opened previously. All other windows that you opened will retain whatever view you previously selected for them.
If you want to reset everything to one view, close all open Finder windows, launch the Terminal app (/Applications/Utilities/), copy & paste this command into the window that pops up,
find ./ -name ".DS_Store" -depth -exec rm {} \;
hit the return key, quit the Terminal app, restart, open a Finder window, CMD+J, set up the view options as desired, click the Use as Defaults button, and close the view options window. Now, every Finder window you open will have this view.
Once you sort this out, see:
Switching from Windows to Mac OS X,
Basic Tutorials on using a Mac,
Mac 101: Mac Essentials,
Mac OS X keyboard shortcuts,
Anatomy of a Mac,
MacTips, and
Switching to the Mac: The Missing Manual, Snow Leopard Edition.
Additionally, *Texas Mac Man* recommends:
Quick Assist,
Welcome to the Switch To A Mac Guides,
Take Control E-books, and
A guide for switching to a Mac.

X11 fullscreen mode broken in Leopard - fix available / planned?

Hello,
in Leopard, X11 fullscreen mode doesn´t work.
Is there already a fix available?
if not is a fix of this problem planned?
As we can see here: http://aaroniba.net/articles/x11-leopard.html it is possible to install Tigers X11, but I´d prefer a fix of the version, which comes with Leopard.
Martin

There is a fake way.
To fake fullscreen support with Xephyr:
$ Xephyr -ac -fullscreen :9 &
$ DISPLAY=:9 twm&
$ DISPLAY=:9 xterm &
It works ok on mine.
Good source http://homepage.mac.com/sao1/X11/index.html

Folder icon broken in leopard?

just upgraded to Leopard and noticed that when i'm in thumbnail view and change the icon of the folder to an image stored in 'clipboard' - it renders that folder unclickable? what's going on? worked great in tiger! ****....

The problem is the size of the picture you are using. I forget about this sometimes and still occasionally get the "unclickable" icon problem. Don't remember what the size limit is, but if you go beyond it you get the problem. You can either open the source image in Preview and resize it, then do copy and paste (and remember NOT to save the changes!), or else use something--an Automator workflow, CocoThumbX or an Applescript--to create a thumbnail for the image, then do GetInfo on the image file and copy the thumb and paste that. You shouldn't notice pixelation problems unless you are using CoverFlow view. In CoverFlow if the view is more than 128 pixels you will notice a degraded view, since normal thumbs created by any of the options are 128x128.
Francine
Francine
Schwieder

IPhoto broken in Leopard

i have installed Leopard on both a MacBook and a G4 12-inch Powerbook, and in both cases iPhoto fails to open. the version loaded seems to be 2.0.1, which seems very old. in both machines i did an erase-install, so any old versions would have been wiped out.
any ideas?

Ed:
Welcome to the Apple Discussions. iPhoto 2 is not supported by Leopard. Therefore, in order to recover your library as a working entity you'll have to purchase iLife 08. If you don't want to purchase iLife you'll have to move all of the full sized image files out of the iPhoto 2 library folder and put them is another folder. If you have duplicate file names that will be a difficult prospect. However, I think you can follow the procedure in Tutorial #1 to write the keywords to the actual files and then use iView to Batch Rename each file to it's Capture Date choosing whatever date format you'd like. I recommend you use YYYY-MM-DD-001.jpg format.
After renaming you can easily find the large files in the library folder and subfolder with a search criteria like Size greater than 100 KB. This will exclude the thumbnail files and you can move the files to a new folder and use a different image management application on them.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Lightroom Is Broken in Leopard

Yes I know this is being discussed in other threads but I wanted to just add to the critical mass in these forums so Adobe will step up the fix.
Not only can I not make a pdf of my contacts because of the module switch problem, I also cant import from a CF card like I normally can.
Come on Adobe.
It's not like this release of Leopard was a surprise. It's been in development for years.
It's out now and we cant use Lightroom in the way I need to.
Please fix it.

"Just to be accurate, members of ADC were notified only Friday that the final GM release version was available for download for developers. Contrast that with MSFT making Vista GM available to developers in Nov 06 with the consumer release in Jan 07 and you might see the differences between being an Apple developer and a MSFT developer. Apple has been known to make last minute changes (it happened with Tiger) that software developers where not told about and had profound impact to developers.
Wake up and realize that any major OS upgrade is gonna whack a lot of developers and you only REALLY know what gets whacked until the final release gets into the wild.
If a user is foolish enough to jump without looking (or taking any precautions) then I would be inclined to say you deserve what you get"
Jeff,
Most everyone knows you have a much closer relationship with Adobe than the average person. How about using that though for a little protection and advise for the average consumer rather than holding Adobe faultless ..
It is perhaps unfair to put all the blame on Adobe here, but they can't be held blameless either. Wacom seemed to have enough time to get something up, and while LR may be 100x the product if not more (from a SW coding perspective), they got it done. Major modules like print not working, or importing from a CF card are pretty basic test functions, and despite what may be a very late code drop from Apple, and unless those functions broke on Friday morning, Adobe still has some basic role to play in alerting its customer base (back to Web Page alert). This is not solely on the consumer. Not everyone is as connected as you, or as smart as a lot of folks on this forum. That doesn't mean that they got what they deserved.. just a little harsh perhaps?
Jay S.

Secure IMAP broken in Leopard

Major troubles with secure IMAP and Leopard.
It won't allow me to access an IMAP account thru port 993 (despite selecting the proper port # and security check box.)
Each time it tries, it gives an error "Cannot connect" error, and takes the account offline. The connection doctor is unhelpful, telling me to check network connections, etc.
It has no trouble connecting insecurely/via port 143.
The cert on the server is valid, and Thunderbird has no such problems on the same machine.
Anyone have any clue? This seems like a legit bug in Leopard, and a frustrating one at that!

I'm using a Macbook connected via DVI-HDMI to a Samsung LE40M86. As mentioned I am unable to choose 1920x1080p, it only displays 1080i.
Though my Macbook detects the display as a Samsung so I guess that thing works.
Regarding the 1080p/i disfunctionality I did find a temporary fix on google but I cant find it any more. The guy clearly stated that it was working though not just displaying 1080p as an option.
Follow these steps and you shall be able to use 1080p via DVI-HDMI:
1. Enable the Display "button" in the menu bar (top right) under Settings (or some').
2. In Main(!) Resolution window set res to 1920x1080 (interlaced).
3. When done, switch to a lower res (a random one).
4. Change back to 1920x1080 (interlaced).
5. Check the Display "button" in menubar and you will see two 1920x1080 (If not jump to step 7), one of them is interlaced the other progressive.
6. Try them out, one should work.
7. If you're not seeing two 1920x1080, change "max no's of previous resolutions used" somewhere under Settings.
This worked for me, I think. Though I'd like a real Apple-ish fix.
Good Luck!
A sum up of my problem,
Leopard is not displaying 1920x1080 (progressive) as an option.

++ Type, brush, crop, lasso etc tools broken on Leopard ++

Apple released OS 10.5.2, which resolves the known issue that numeric values to set sizes for the brush, crop, marquee, lasso, type, and other Photoshop CS3 tools, revert to previously entered values when you try to apply them.
Go to
Apple's knowledgebase doc.

I know they are acknowledging it and working on a fix with Apple, I said that myself in my previous post.
Adobe's Leopard compatibility FAQ http://www.adobe.com/support/products/pdfs/leopardsupport.pdf was published when the final version of Leopard was released. It was presumably intended to help users decide when to upgrade. It does not list any issues with Photoshop CS3 and Leopard. If they hadn't finished testing they should have waited to publish compatibility information. At the very least the FAQ should have been updated when they became aware of the issue. Leopard shipped over a month ago and this problem still isn't mentioned.
I installed Leopard after reading that there were no issues, and I was a bit disappointed to find that was not the case. I ran into this problem immediately. I don't mind dealing with some minor issues though, and I'm still able to get my work done. Overall I'd say CS3 is running better on Leopard for me... I don't get random beachballing all the time like I did in Tiger. (That was really frustrating, much worse than this bug. Especially since I just bought a new 2.8GHz machine with 4GB RAM!) Leopard also has a ton of other improvements that have made my work easier, and even fixed a lot of bugs. I'd rather have some new bugs to complain about than deal with the same ones that have been there for months or even years!
Cheers.

Is ssh broken with Leopard ?

Hi !
Since I've upgraded to Leopard, I cannot do sftp (using Transmit.app) nor scp. Got no message, no stderror ou stdout, nothing in /var/log: the file are simply not copied. Any idea ?

So I've used SSH and the terminal for some time starting with Jaguar, but I don't have extensive command line experience. I've been SSHing into my iMac G5 (running Leopard) for some time now with this MBP (10.5.2). Recently, I wasn't able to connected. I've edited the known_hosts file and removed the old keys. I just did ssh -v to find out what was going on, and I'm not sure what to do. I can get to the password inputs, it asks for a password 3 times no matter what I put in, and then it asks for the password of the target computer (that I'm attempting to SSH into) and it tells me it's an incorrect password the 3 times that it asks, even if I put in the correct password three times. Here's the output and thanks for any help you can give me.
wvcl155:~ username$ ssh -v username@<ip address>
OpenSSH_4.5p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to <ip address> (openbracket)<IP address>] port 22.
debug1: Connection established.
debug1: identity file /Users/username/.ssh/identity type -1
debug1: identity file /Users/username/.ssh/id_rsa type -1
debug1: identity file /Users/username/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_4.7
debug1: match: OpenSSH_4.7 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.5
debug1: SSH2MSGKEXINIT sent
debug1: SSH2MSGKEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2MSG_KEX_DH_GEXREQUEST(1024<1024<8192) sent
debug1: expecting SSH2MSG_KEX_DH_GEXGROUP
debug1: SSH2MSG_KEX_DH_GEXINIT sent
debug1: expecting SSH2MSG_KEX_DH_GEXREPLY
debug1: Host '<IP address>' is known and matches the RSA host key.
debug1: Found key in /Users/username/.ssh/known_hosts:2
debug1: sshrsaverify: signature correct
debug1: SSH2MSGNEWKEYS sent
debug1: expecting SSH2MSGNEWKEYS
debug1: SSH2MSGNEWKEYS received
debug1: SSH2MSG_SERVICEREQUEST sent
debug1: SSH2MSG_SERVICEACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/username/.ssh/identity
debug1: Trying private key: /Users/username/.ssh/id_rsa
debug1: Trying private key: /Users/username/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
username@<IP address>'s password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Permission denied, please try again.
username@<IP address>'s password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Permission denied, please try again.
username@<IP address>'s password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: No more authentication methods to try.
Permission denied (publickey,password,keyboard-interactive).
I have also realized I can't FTP, SFTP, or screenshare with the iMac G5. I have checked all network and sharing settings of the iMac G5 (via Phone) and made sure all necessary ports are open (firewall was even off on both Router and iMac for testing).
Thanks again.

Mac Pros extra two internal sata ports broken since Leopard 10.5??

I have a Mac Pro and according to xlr8yourmac.com and the newertech website, there are four sata ports for your hard drives PLUS an additional two more sata ports directly on the motherboard. Through a complicated and difficult disassembly, it is possible to dissect your mac pro and install their cable which they sell for about $30, and get at the rear of your mac pro housing connectors for these two internal sata ports. In short, it's nothing more than an extension cable that fits into a neat housing at the back of the mac pro. You can then plug up to two esata drives into those jacks and they are basically hooked into the macpro motherboard. I ordered this cable and it worked splendidly since 10.4.8 and for 10.4.9 without any issue (that I could tell). I was even able to raid them together etc etc. (edit to be clear I mean I had two Lacie 500Gb drives with esata, firewire 800, 400 and USB 2 on them).
When I installed 10.5 it was all broken!! What a disaster. I can't use these drives on the firewire bus (which by the way they work fine on) because I am already tieing up that with other devices and drives. I need these extra two buses, plus they were **** fast before- I guess it's the same bus as the internal drives get.
I have contacted Lacie - no luck - and also newertech, and did so again today, but so far no luck, and apple, no luck and even submitted a feedback request back when we were on 10.5.1 (just released at that time), and no luck. I hoped 10.5.2 would restore this functionality.
I was told Apple do not normally go out of their way to kill unintended functionality but could this be the case on this occasion?

www.xlr8yourmac.com its over my head but...
A Copy of the April 23rd, 2007 news page post is below (in reply to eSATA Extender cables (w/PCI slot bracket) from Newer Tech for use with the 2 unused ports on the Mac Pro motherboard.)
" this may be of some interest for your readers.
From the Intel 631xESB/632xESB I/O Controller Hub data sheet:
"Hot-Plug Operation
Dynamic Hot-Plug (for example, surprise removal) is not supported by the SATA host controller. However, using the PCS register configuration bits and power management flows, a device can be powered down by software, and the port can then be powered off, allowing removal and insertion of a new device. "
(I asked if he knew of any way to do that in OS X.)
the SATA controller does support AHCI mode, which enables hot plugging (same as with the raid southbridges ICH6R - ICH8R which support hot plugging with raid drivers from Intel without Intel assuring this).
But it does not support AHCI if the PATA port is used as in the Mac Pro. And without AHCI there is no way to do hot plugging.
Using a SATA DVD drive may not mean AHCI is used automatically. The controller has to be switched from IDE to AHCI mode. Maybe the Mac Pro does it on startup or some EFI specialist can finds out how to do that.
BTW Tiger can handle an ICH8R in AHCI mode on all SATA ports without a problem.
Kind regards,
Martin S. "
Info/Tips on using Spare SATA Ports with Windows: (from Jan 15th, 2008 news page) This may have come up in the past and I'd forgotten it (don't own a Mac Pro yet) but in reply to a post yesterday (1/15/2008) on the Pioneer SATA Blu-Ray reader/Superdrive combo drive, a reader mentioned the spare SATA ports are not usable in Windows XP at least with the standard drivers with Bootcamp. (Most readers have used the ports in OS X although I've not searched drive db reports for anyone that mentioned using Bootcamp/Windows also. BTW - The spare ports are bootable for OS X use, as noted in this article - although drives are not shown/usable when booted from Windows with standard drivers.)
(Update) Here's a reader mail w/tips on using the spare ports with Windows via a replacement chipset driver install and grub bootloader edit:
" after finding this thread in the onmac forums I finally was able to get my pioneer sata drive to work under bootcamp. Basically you have to do the following:
- Install Win XP and ubuntu linux with a pata dvd drive in XP, change the ide 2680 driver to the intel ahci driver found here (downloadcenter.intel.com) S5000 Based Server AHCI SATA Storage Driver for Windows.
- Boot into ubuntu and change the stage1 file of the grub bootloader to this:
http://www.olofsson.info/grub/stage1
This keeps the mac pro in ahci mode when booting a foreign OS
Now you can boot windows using the linux partition, this will start grub and keep the mac pro in the correct mode
I also installed Refit to make things a little easier but as far as i know using Alt key when booting should work too.
if anyone tries this and has any questions feel free to ask
-Forrest"

Pax broken in leopard?

Similar Messages

Maybe you are looking for