Date: Thursday, April 10th, 2003, 00:00
Here is my workaround for the problems with Virtual PC and the 17″ PowerBook’s built-in AirPort Extreme card. This work around allows you to configure Virtual Switch networking properly so you can run servers in your Virtual PC session. Users of Shared Networking need not do this since Shared Networking “works”. Click Read More for the whole story…
Here is my workaround for the problems with Virtual PC and the 17″ PowerBook’s built-in AirPort Extreme card. This work around allows you to configure Virtual Switch networking properly so you can run servers in your Virtual PC session. Users of Shared Networking need not do this since Shared Networking works.
I was able to perform this process with the help of my friend Jason from Shekinah Studios who pointed me in the right direction by telling me about the extensions directory and what it was for. Thanks Jason!
A few words of caution:
First please read this whole thing before proceeding. At the end I talk about some of the caveats and issue with this workaround. It would be smart to review all of this before proceeding.
You will be working as root and this procedure could potentially damage your operating system if done improperly. the files in the extensions directory are VITAL to the operation of OS X. If you delete them you may render your system UNUSABLE requiring a reinstall of OS X. Be smart and take your time. Don’t delete files, just move them, and keep multiple backups (as my procedure does).
Also when you operate as root (superuser) you can do ANYTHING. This is a very dangerous mode to work in and you can damage your operating system to the point of non-functionality. If you feel uneasy about this DON’T DO IT!
Please be safe! Backing up your whole system might seem extreme when moving just three files, but if you roast your operating system, you will be glad you did.
I take NO responsibility for the results of this process. If you perform this procedure, the results are on YOUR head. If OS X chokes and dies, VPC decides not to work, or your cat/dog/boyfriend/girlfriend runs away, YOU HAVE BEEN WARNED.
Step 1) Go to the directory /System/Library/Extensions/
Step 2) Create a folder on you desktop to backup these files.
Step 3) Copy these three files FROM the extensions folder TO the backup directory:
Step 4) Start up a terminal session.
Step 5) Go to the directory in terminal:
% cd /System/Library/Extensions
Step 6) Change to superuser mode or prefix each command with sudo (superuser do). The su command will prompt you for your root password.
Warning this sets you as root, and you can DO ANYTHING BE CAREFUL
Step 7) Create a backup directory to store the three files:
% mkdir backup
Step 8) Move the three files to this backup directory:
% mv AppleAirPort.kext backup
% mv AppleAirPortFW.kext backup
% mv AppleAirPort2.kext backup
Step 9) Exit you terminal session
Step 10) Now reboot your system
This process could also be done entirely from Finder, but I’m more comfortable doing this in a terminal session. You would have to change the permissions of the files before doing the move. I found the method more complicated, but if you know how to do it all from Finder go ahead. Just be careful. Working as a root user and fiddling with permissions can have disastrous consequences to the functionality of your operating environment.
This ELIMINATES your Airport Extreme. It will no longer be visible to OS X. It in effect removes it from the operating system’s consciousness. If you need the AirPort, this workaround won’t help you. If you need to restore the AirPort, copy the files back into the extensions directory and reboot.
After performing this procedure I also had to install a new copy of Windows 2000 since the old instance was totally broken. I don’t know if this was because of the changes resulting from this workaround or was due to the messing around I was doing trying to get the thing working. Don’t be surprised if you have to re-install Windows 2000 or whatever it is you are using.