Return to site

Prl Tools Mac Iso Download

broken image


How I Managed to Upgrade My Parallels Desktop from Version 7 to 8 onto OS X Mavericks

So, I deemed it was time to move on from OS X Lion to Mavericks. From a previous inquiry, I found out that my version 7 of Parallels Desktop wouldn't run on Maverick. After waiting for quite a while, last Christmas netted me a deep discount for its iteration number 8. I nailed a full version of Parallels Desktop 8 —which will enable me to run my existing VM on Mavericks— for just a buck after mail-in rebate. Woohoo! I know it's not the latest version, but I really think that the price at that level is very reasonable. When your OS is free, is it really worth for you to get Parallels Desktop for at least 59 bucks? Nu'uh. Not in my dictionary.

Music software for Mac or Windows to create audio with up to 128 audio tracks. Pro Tools includes 60 virtual instruments (thousands of sounds), effects, sound processing, utility plugins, 1 GB of cloud storage and 75 individual plugins. Create, Collaborate. Copy the prl-tools-lin.iso from the Mac /Applications folder into NixOS. //path/to/prl-tools-lin.iso (and the version should be updated too). Copy link Quote reply. @srid My pr downloads prl-tools automatically, but I think it's only been merged into master so far (so you would have to cherry pick it into your own 17.09 fork).

Yesterday, with both Mavericks and Parallels Desktop 8 in hand, I decided to make the plunge. The transition to Mavericks was seamless and a breeze. Unfortunately, this wasn't the case with Parallels' upgrade. To be exact, the upgrade itself was fine. However, after I ran my VM, it detected that my Parallels Tools was out of date, tried to install it and ultimately failed with the error 'There was a problem updating Parallels Tools' shown on a red 'Parallels Tools Installation Agent' window after showing progress of 15% and sometimes 24%.

Prl

I tried everything I could. I followed the instruction on said window to reboot. I rebooted like a gazillion times to no avail. I turned off Windows Security Essential based on a Parallels KB that said antivirus software might halt installation. I turned off Windows system restore on all my disk. I uninstalled Parallels Desktop completely and reinstalled it. Nothing yielded any result.

So, here are the list of actions I've taken that allowed me to install Parallel Tools on my VM.

  1. I found out that Parallel Tools .iso and related files aren't where they're supposed to be. So, several links pointed out that the files 'prl-tools-win.iso' and 'prl-tools-win.tar.gz 'should both be inside the path '/Library/Parallels/Tools'. Problem is, I didn't even see the name of the folder. All I saw in the Parallels folder were 'Downloads', 'Receipts', and 'Uninstaller' folders.
  2. Do a 'Show Package Contents' on the app

    I copied those two files from Parallels Desktop application file with Finder. I opened Applications folder, right-click on Parallels Desktop.app and clicked on Show Package Contents menu item. Then I copied the two files from the application's

    Copy the two files to where they're supposed to be

    'Content/Resources/Tools' folder to '/Library/Parallels/Tools' folder after, I created the 'Tools' folder. This way, all the required files are where they supposed to be when I mount the images in my VM.

  3. I killed the unresponsive 'Parallels Tools Installation Agent' window with Task Manager. At this point, that darned window wouldn't close and won't minimize. It just stared blankly, giving the only option of rebooting the VM. It took me two attempts with Task Manager to kill it.
  4. I uninstalled 'Parallel Tools' from Control Panel's Add/Remove Programs dialog. If the darn thing's giving you trouble by throwing error message 'Error 2738, Could not access VBScript run time for custom action', follow the instructions here. For me, the command on the bottom worked (I had a 64-bit system), but I had to type it precisely since I don't have clipboard sharing enabled —thanks to missing Parallel Tools.
  5. I rebooted my VM. Just to make sure.
  6. I mounted the Parallels Tools .iso onto the VM. Instead of running the autorun script, I browsed the virtual CD. And from then, I ran the 'PTAgent.exe' file as Administrator by right-clicking on it and selecting 'Run as administrator' from the menu. Finally, the installation agent ran smoothly this time.

  1. It is dedicated to help in ISO 9001, ISO 14001 & OHSAS 18001 (or any other H&S management system) management in the most efficient way. Downloads: 0 This Week Last Update: 2016-07-25 See Project From visitors to conference rooms, Envoy redefines how people, places, and technology work together.
  2. This is the vmx file for the VM on which Crypt doesn't working. Crypt vmx file faulty.
  3. The work-around is to copy the Parallels Tools ISO (ApplicationsParallels DesktopShow Package ContentsResourcesToolsprl-tools-mac.iso). Copy the ISO to the desktop of your Catalina VM. You might not be able to see ANY shared folders or be able to drag and drop (because there are no tools installed, duh).

There you go. I got my Parallels Desktop 8 working on OS X Mavericks. Hopefuly you'll get yours working too.

-6.271645106.803089

Howto: Mac mini multi-boot without GRUB2/rEFIt woes

In trying to set up a triple-boot OS X/Karmic/XP setup on my 2009 mac mini, I encountered some (but not all) of the problems in this thread and many others. I found that if you don't take special precautions, Karmic will easily render both your Ubuntu installation and your Windows installation (if you have one) unbootable.
The problem here is essentially that every piece of software in the installation chain is broken in some way or lacks some piece of critical functionality. There are many holes and if you step in one, you'll have to go back to start. War thunder aimbot download. It may be possible to get installed in the normal fashion if you have enough days to spare, but I spent many hours following the steps in that thread and others only to replace my original problem with others, then restore the original. I wanted to have Linux installed before February so I chose to avoid, rather than fix, the broken bits.
This post contains few troubleshooting phases (‘run this command and see if it fixes the problem') but does require you do do a few things that will seem insane. I'll try to explain why, without getting too tangential. I'm not entirely sure that I'll manage, so forgive me if I ramble too much.
The Rogues Gallery
Each of these pieces of software is culpable in some way. Whenever you use one of these programs, keep the bugs in mind and simply don't use whatever is broken. One of the other pieces of software will pick up the slack.

  • OS X Disk Utility
  • rEFIt (http://refit.sourceforge.net)
  • GRUB (specifically version 1.97 beta, IIRC)
  • Ubuntu Installer/GParted
  • Windows XP Installer


GRUB and GParted are most broken here. Be extra careful when dealing with them. GRUB2, in particular, is horrendously broken. It will hose your disk, and it's up to you to decide if you are up to the task of searching the forums and fixing it.
Partition notes
Only the first three partitions you see in Disk Utility will be part of the MBR disk. MBR supports four primary partitions, but there is a tiny partition at the beginning of the disk which Disk Utility is hiding from you. So you only have three.
On an EFI disk, you cannot create extended partitions, but you can create more than four primary partitions. Windows won't be able to see partitions after the fourth one, but Ubuntu can see them all. Put your Ubuntu root (or /boot if you like it that way) on partition 3 and if you need more, you can add them at the end. Dozens of howtos on the internet say that if you are installing Windows, install it on partition 4. Remember, in Disk Utility this will look like 2 and 3.
The EFI Dance
Just get used to doing this series of steps every time you make a change to a partition, format something, or install an operating system. Keep in mind that the Ubuntu LiveCD won't be able to reboot.
1. Shutdown.
2. Start up.
3. In rEFIt, select the partition tool. If asked to synchronize the disks, say 'y.' Be on the lookout for 'Unknown' appearing in the MBR. If it does, you did something wrong and will need to fix it/start over.
4. Boot into OS X. A rEFIt script in the startup does some magic to 'bless' the disk.
5. Shutdown.
6. Start up.
Installation steps
The main thing to do here is avoid GRUB2. After reading that, if you are upgrading, Ubuntu will not replace the original GRUB with GRUB2, I realized that the way to get Karmic installed is to start with Jaunty. Jaunty (9.04) is the latest version of the installer than uses the original GRUB, and you will need that if you want an easy mac install.
1. In OS X Disk Utility, shrink the OS X partition and create partitions for Ubuntu and/or Windows. These new partitions should be ms-dos (FAT32).
Notes

In my experience, any of the following will cause rEFIt to be unable to properly sync the disk. One of the partitions showed up as 'Unknown' if I did one of these: Creating a partition with Ubuntu installer/GParted, formatting a partition as FAT32 in GParted, formatting a partition AS NTFS in GParted. The only solution when this happens is to delete the partition and start over with Disk Utility.
rEFIt can only sync very clean, well-behaved data. When hit with the output of GParted (which I suspect is invalid but am not qualified to say for sure), it can't deal with it and chokes. But Disk Utility is fine. It can reliably create and resize partitions that rEFIt will be happy with. I never had any problems with it. Always create your partitions with Disk Utility.

Prl Tools Mac Iso Download 64-bit

On the other hand, Disk Utility can only create or format HFS+ and FAT32 partitions. It also wastes ~128MB of space after each HFS+ partition (but not after FAT32 partitions), so always create FAT32 partitions.
Disk Utility cannot reliably delete NTFS or ext3 partitions, or partitions that show up as Unknown in rEFIt. Sometimes it refuses to look at the disk, sometimes it errors out but will work if you retry, and sometimes it completely crashes. I found it safer to delete, but not create, partitions with the Ubuntu LiveCD.
FAT32 partitions created are not bootable after a Windows install, so you must get the Windows installer to format the partition.

2. Do the EFI Dance.
3. Boot the Ubuntu live CD and format the partitions you want for linux. According to various forums, rEFIt doesn't support ext4, so it is probably safest to stick with ext3. Your call.
Notes

When installing Windows, there will be only one FAT32 partition to choose, which makes it impossible to miss. When installing Ubuntu, all you will need to do is select your already-formatted ext3 partitions.
GParted can format partitions as ext3 (I can't confirm swap; with 4GB of RAM, I don't need it; might eventually have a small swap file). It also doesn't have problems with deleting partitions.

4. EFI Dance.
(Windows XP steps, not needed if you don't triple boot).
5. (Optional, depending on installer version) Fill up the FAT32 partition with files. Leave as few megs as possible.
Notes

XP cannot create partitions on a GPT/MBR disk, and it will not install on an existing partition formatted as NTFS (by GParted, at least). If you install on a FAT32 partition created by Disk Utility, it won't boot, so you must get XP to format.

Prl-tools-mac.iso Download

Depending on the specific type of XP you are installing (apparently), it might not give you the option to format. But if leave so little free space on the drive that Windows will be forced to format it, then you'll get the option to format.

6. Put the XP CD in and restart. Hold down 'C' when restarting. When XP says to press any key too boot from CD, press a key.
7. Select the FAT32 partition. You will be asked to reformat it. Do so.
8. When it reboots, hold down 'C' when restarting. When XP says to press any key too boot from CD, DON'T. Just wait.
9. After this phase of install it will reboot again. Hold down 'C' when restarting. When XP says to press any key too boot from CD, DON'T. Just wait.
10. When XP starts up, remove the XP disk and put in the OS X DVD. Install the Apple hardware drivers.
11. EFI Dance. After the dance, you should be able to boot XP through rEFIt and by holding down Alt when booting. It worked for me three times, and once I did the dance, everything was OK. You'll want to verify windows with Microsoft.
(End Windows XP steps)
12. Boot Ubuntu Jaunty (9.04) with either the alternate installer iso or the mini iso.
Notes

The Karmic installer installed GRUB2 against my wishes and hosed my disk. It wasn't an optional choice. It wasn't the default choice. It was the only choice. Totally irresponsible. Installing GRUB2 will most likely be the last thing you do before deleting all your MBR partitions and starting over.
Also, rEFIt hasn't been updated since March of 2009, so it won't recognize GRUB2 either. It will just be a 'legacy disk.'
Jaunty won't install GRUB2, not having it. The theory with a minimal installation is that it means less stuff that can break on upgrade. Personally, I used the mini ISO and unetbootin.

13. When you get to the partitioning stage, select your existing partitions, which you formatted in step 3, select the proper type of disk and mount them. At minimum, mount / and /swap (if you're using it).
14. When you get to GRUB, install it to either the MBR or to the Ubuntu partition. Personally, I chose to install to /sda, so that is the only method I can personally confirm. There is a down side to this: after you do this, you will get the grub menu on both the Linux and Windows menu entries in rEFIt.
I can't confirm that it works with /sda3, but most of the howtos on the net recommend it.
Notes

Prl Tools Mac Iso Download
The only minus to installing GRUB on the MBR is cosmetic. You have two menus that do the same thing. It also takes several seconds longer to boot into Windows.
But this works for me. It works even when you skip rEFIt entirely, by holding down Alt when starting up. There is no Linux option here, but if you select Windows, you still get to boot Linux. You might even be able to get rid of rEFIT entirely, should you choose.

15. Do the EFI dance. I *think* this is the last time.
At this point, I was able to boot into Ubuntu. I had my functional triple boot system. I only got as far as step 15 once, but I don't see much in steps 12-15 that could go wrong. Perhaps where you install GRUB, but everything did exactly what I expected it to do.
16.

17. Reboot. Now you are in Karmic Koala.
18.

Prl Tools Mac Iso Download Windows 7

There is no reason why kubuntu-desktop or xubuntu-desktop wouldn't work just as well.
19. Reboot. Now you are in a normal Ubuntu login.
20. You will still be able to connect to the internet, but won't be able to edit the connection settings for this setting in gnome or kde network managers. This seems to be caused by the upgrade. It's a very old bug that still hasn't been fixed.

Tools

I tried everything I could. I followed the instruction on said window to reboot. I rebooted like a gazillion times to no avail. I turned off Windows Security Essential based on a Parallels KB that said antivirus software might halt installation. I turned off Windows system restore on all my disk. I uninstalled Parallels Desktop completely and reinstalled it. Nothing yielded any result.

So, here are the list of actions I've taken that allowed me to install Parallel Tools on my VM.

  1. I found out that Parallel Tools .iso and related files aren't where they're supposed to be. So, several links pointed out that the files 'prl-tools-win.iso' and 'prl-tools-win.tar.gz 'should both be inside the path '/Library/Parallels/Tools'. Problem is, I didn't even see the name of the folder. All I saw in the Parallels folder were 'Downloads', 'Receipts', and 'Uninstaller' folders.
  2. Do a 'Show Package Contents' on the app

    I copied those two files from Parallels Desktop application file with Finder. I opened Applications folder, right-click on Parallels Desktop.app and clicked on Show Package Contents menu item. Then I copied the two files from the application's

    Copy the two files to where they're supposed to be

    'Content/Resources/Tools' folder to '/Library/Parallels/Tools' folder after, I created the 'Tools' folder. This way, all the required files are where they supposed to be when I mount the images in my VM.

  3. I killed the unresponsive 'Parallels Tools Installation Agent' window with Task Manager. At this point, that darned window wouldn't close and won't minimize. It just stared blankly, giving the only option of rebooting the VM. It took me two attempts with Task Manager to kill it.
  4. I uninstalled 'Parallel Tools' from Control Panel's Add/Remove Programs dialog. If the darn thing's giving you trouble by throwing error message 'Error 2738, Could not access VBScript run time for custom action', follow the instructions here. For me, the command on the bottom worked (I had a 64-bit system), but I had to type it precisely since I don't have clipboard sharing enabled —thanks to missing Parallel Tools.
  5. I rebooted my VM. Just to make sure.
  6. I mounted the Parallels Tools .iso onto the VM. Instead of running the autorun script, I browsed the virtual CD. And from then, I ran the 'PTAgent.exe' file as Administrator by right-clicking on it and selecting 'Run as administrator' from the menu. Finally, the installation agent ran smoothly this time.

  1. It is dedicated to help in ISO 9001, ISO 14001 & OHSAS 18001 (or any other H&S management system) management in the most efficient way. Downloads: 0 This Week Last Update: 2016-07-25 See Project From visitors to conference rooms, Envoy redefines how people, places, and technology work together.
  2. This is the vmx file for the VM on which Crypt doesn't working. Crypt vmx file faulty.
  3. The work-around is to copy the Parallels Tools ISO (ApplicationsParallels DesktopShow Package ContentsResourcesToolsprl-tools-mac.iso). Copy the ISO to the desktop of your Catalina VM. You might not be able to see ANY shared folders or be able to drag and drop (because there are no tools installed, duh).

There you go. I got my Parallels Desktop 8 working on OS X Mavericks. Hopefuly you'll get yours working too.

-6.271645106.803089

Howto: Mac mini multi-boot without GRUB2/rEFIt woes

In trying to set up a triple-boot OS X/Karmic/XP setup on my 2009 mac mini, I encountered some (but not all) of the problems in this thread and many others. I found that if you don't take special precautions, Karmic will easily render both your Ubuntu installation and your Windows installation (if you have one) unbootable.
The problem here is essentially that every piece of software in the installation chain is broken in some way or lacks some piece of critical functionality. There are many holes and if you step in one, you'll have to go back to start. War thunder aimbot download. It may be possible to get installed in the normal fashion if you have enough days to spare, but I spent many hours following the steps in that thread and others only to replace my original problem with others, then restore the original. I wanted to have Linux installed before February so I chose to avoid, rather than fix, the broken bits.
This post contains few troubleshooting phases (‘run this command and see if it fixes the problem') but does require you do do a few things that will seem insane. I'll try to explain why, without getting too tangential. I'm not entirely sure that I'll manage, so forgive me if I ramble too much.
The Rogues Gallery
Each of these pieces of software is culpable in some way. Whenever you use one of these programs, keep the bugs in mind and simply don't use whatever is broken. One of the other pieces of software will pick up the slack.

  • OS X Disk Utility
  • rEFIt (http://refit.sourceforge.net)
  • GRUB (specifically version 1.97 beta, IIRC)
  • Ubuntu Installer/GParted
  • Windows XP Installer


GRUB and GParted are most broken here. Be extra careful when dealing with them. GRUB2, in particular, is horrendously broken. It will hose your disk, and it's up to you to decide if you are up to the task of searching the forums and fixing it.
Partition notes
Only the first three partitions you see in Disk Utility will be part of the MBR disk. MBR supports four primary partitions, but there is a tiny partition at the beginning of the disk which Disk Utility is hiding from you. So you only have three.
On an EFI disk, you cannot create extended partitions, but you can create more than four primary partitions. Windows won't be able to see partitions after the fourth one, but Ubuntu can see them all. Put your Ubuntu root (or /boot if you like it that way) on partition 3 and if you need more, you can add them at the end. Dozens of howtos on the internet say that if you are installing Windows, install it on partition 4. Remember, in Disk Utility this will look like 2 and 3.
The EFI Dance
Just get used to doing this series of steps every time you make a change to a partition, format something, or install an operating system. Keep in mind that the Ubuntu LiveCD won't be able to reboot.
1. Shutdown.
2. Start up.
3. In rEFIt, select the partition tool. If asked to synchronize the disks, say 'y.' Be on the lookout for 'Unknown' appearing in the MBR. If it does, you did something wrong and will need to fix it/start over.
4. Boot into OS X. A rEFIt script in the startup does some magic to 'bless' the disk.
5. Shutdown.
6. Start up.
Installation steps
The main thing to do here is avoid GRUB2. After reading that, if you are upgrading, Ubuntu will not replace the original GRUB with GRUB2, I realized that the way to get Karmic installed is to start with Jaunty. Jaunty (9.04) is the latest version of the installer than uses the original GRUB, and you will need that if you want an easy mac install.
1. In OS X Disk Utility, shrink the OS X partition and create partitions for Ubuntu and/or Windows. These new partitions should be ms-dos (FAT32).
Notes

In my experience, any of the following will cause rEFIt to be unable to properly sync the disk. One of the partitions showed up as 'Unknown' if I did one of these: Creating a partition with Ubuntu installer/GParted, formatting a partition as FAT32 in GParted, formatting a partition AS NTFS in GParted. The only solution when this happens is to delete the partition and start over with Disk Utility.
rEFIt can only sync very clean, well-behaved data. When hit with the output of GParted (which I suspect is invalid but am not qualified to say for sure), it can't deal with it and chokes. But Disk Utility is fine. It can reliably create and resize partitions that rEFIt will be happy with. I never had any problems with it. Always create your partitions with Disk Utility.

Prl Tools Mac Iso Download 64-bit

On the other hand, Disk Utility can only create or format HFS+ and FAT32 partitions. It also wastes ~128MB of space after each HFS+ partition (but not after FAT32 partitions), so always create FAT32 partitions.
Disk Utility cannot reliably delete NTFS or ext3 partitions, or partitions that show up as Unknown in rEFIt. Sometimes it refuses to look at the disk, sometimes it errors out but will work if you retry, and sometimes it completely crashes. I found it safer to delete, but not create, partitions with the Ubuntu LiveCD.
FAT32 partitions created are not bootable after a Windows install, so you must get the Windows installer to format the partition.

2. Do the EFI Dance.
3. Boot the Ubuntu live CD and format the partitions you want for linux. According to various forums, rEFIt doesn't support ext4, so it is probably safest to stick with ext3. Your call.
Notes

When installing Windows, there will be only one FAT32 partition to choose, which makes it impossible to miss. When installing Ubuntu, all you will need to do is select your already-formatted ext3 partitions.
GParted can format partitions as ext3 (I can't confirm swap; with 4GB of RAM, I don't need it; might eventually have a small swap file). It also doesn't have problems with deleting partitions.

4. EFI Dance.
(Windows XP steps, not needed if you don't triple boot).
5. (Optional, depending on installer version) Fill up the FAT32 partition with files. Leave as few megs as possible.
Notes

XP cannot create partitions on a GPT/MBR disk, and it will not install on an existing partition formatted as NTFS (by GParted, at least). If you install on a FAT32 partition created by Disk Utility, it won't boot, so you must get XP to format.

Prl-tools-mac.iso Download

Depending on the specific type of XP you are installing (apparently), it might not give you the option to format. But if leave so little free space on the drive that Windows will be forced to format it, then you'll get the option to format.

6. Put the XP CD in and restart. Hold down 'C' when restarting. When XP says to press any key too boot from CD, press a key.
7. Select the FAT32 partition. You will be asked to reformat it. Do so.
8. When it reboots, hold down 'C' when restarting. When XP says to press any key too boot from CD, DON'T. Just wait.
9. After this phase of install it will reboot again. Hold down 'C' when restarting. When XP says to press any key too boot from CD, DON'T. Just wait.
10. When XP starts up, remove the XP disk and put in the OS X DVD. Install the Apple hardware drivers.
11. EFI Dance. After the dance, you should be able to boot XP through rEFIt and by holding down Alt when booting. It worked for me three times, and once I did the dance, everything was OK. You'll want to verify windows with Microsoft.
(End Windows XP steps)
12. Boot Ubuntu Jaunty (9.04) with either the alternate installer iso or the mini iso.
Notes

The Karmic installer installed GRUB2 against my wishes and hosed my disk. It wasn't an optional choice. It wasn't the default choice. It was the only choice. Totally irresponsible. Installing GRUB2 will most likely be the last thing you do before deleting all your MBR partitions and starting over.
Also, rEFIt hasn't been updated since March of 2009, so it won't recognize GRUB2 either. It will just be a 'legacy disk.'
Jaunty won't install GRUB2, not having it. The theory with a minimal installation is that it means less stuff that can break on upgrade. Personally, I used the mini ISO and unetbootin.

13. When you get to the partitioning stage, select your existing partitions, which you formatted in step 3, select the proper type of disk and mount them. At minimum, mount / and /swap (if you're using it).
14. When you get to GRUB, install it to either the MBR or to the Ubuntu partition. Personally, I chose to install to /sda, so that is the only method I can personally confirm. There is a down side to this: after you do this, you will get the grub menu on both the Linux and Windows menu entries in rEFIt.
I can't confirm that it works with /sda3, but most of the howtos on the net recommend it.
Notes

The only minus to installing GRUB on the MBR is cosmetic. You have two menus that do the same thing. It also takes several seconds longer to boot into Windows.
But this works for me. It works even when you skip rEFIt entirely, by holding down Alt when starting up. There is no Linux option here, but if you select Windows, you still get to boot Linux. You might even be able to get rid of rEFIT entirely, should you choose.

15. Do the EFI dance. I *think* this is the last time.
At this point, I was able to boot into Ubuntu. I had my functional triple boot system. I only got as far as step 15 once, but I don't see much in steps 12-15 that could go wrong. Perhaps where you install GRUB, but everything did exactly what I expected it to do.
16.

17. Reboot. Now you are in Karmic Koala.
18.

Prl Tools Mac Iso Download Windows 7

There is no reason why kubuntu-desktop or xubuntu-desktop wouldn't work just as well.
19. Reboot. Now you are in a normal Ubuntu login.
20. You will still be able to connect to the internet, but won't be able to edit the connection settings for this setting in gnome or kde network managers. This seems to be caused by the upgrade. It's a very old bug that still hasn't been fixed.

Prl Tools Mac Iso Download Windows 10

Under 'auto eth0' will be a line starting with iface. Comment it out or delete it, save, and reboot. Then delete the auto eth0 connection in gnome network manager.
21. Find your device under CategoryMac and finish any extra hardware steps. For the Mac Mini 3.1, I have one thing to add. If you add reboot=pci to your boot options, I can confirm that rebooting will work.
Summary
Ubuntu on the mac mini is like Satan's own jan-ken-pon game. Fixing problems caused by other developers has been my job for a decade, so I was sort of used to it, but it was still painful. Ubuntu made XP unbootable twice, forcing me to start over, but it seems to be functional now and running nicely.





broken image