a Flo + a Blog = a Flog my ブログ

Mac OSx86 10.4.6 on Thinkpad T60

i have previously explained how to install OSx86 aka MacOS X on a T60 thinkpad 200762U, I would like here really sum up everything you need for the post OS install.

After installing the OS you will get a working T60 with no sound, a lousy resolution and no wireless. Let's review one after another.

Sound

1) Delete AppleHDA.kext:

* In Terminal, type: sudo rm -rf /System/Library/Extensions/AppleHDA.kext
* sudo rm -rf /System/Library/Extensions.mkext
* sudo rm -rf /System/Library/Extensions.kext

2) Edit AppleAzaliaAudio.kext:

* In Terminal, type: sudo pico /System/Library/Extensions/AppleAzaliaAudio.kext/Contents/Info.plist
* Search for (use hotkey= ctrl + w):
IOHDAudioCodecVendorID
* change the string to:
0x10ec0882
* Exit pico
* sudo pico /System/Library/Extensions/AppleAzaliaAudio.kext/Contents/PlugIns/AppleAzaliaController.kext/Contents/Info.plist
* Search for (use hotkey= ctrl + w):
IOPCIPrimaryMatch
* change the string to:
0x27d88086
* Exit pico

3) Clean up the system:

* In Terminal, type: sudo kextload /System/Library/Extensions/AppleAzaliaAudio.kext
* kextcache -k /System/Library/Extensions/

4) Then, reboot and enjoy sound out of two channels.

Video

1) Open the file:
/System/Library/Extensions/ATIRadeonX1000.kext/Contents/Info.plist

2) and find the line "IOPCIMatch". Modify the next line to say: "0x71091002 0x71C41002 0x71C01002"

3) Open the file "/Library/Preferences/SystemConfiguration/com.apple.Boot.plist"

4) after the lines:
"Boot Graphics
Yes"

add the lines:"Graphics Mode
1400x1050x32"

Wireless

The 200762U has the ThinkPad 11a/b/g Wireless LAN Mini-PCI Express Adapter (lenovo.com part #: 40Y7026) which is compatible with OSx

1) You must download the Apple 10.4.5 intel upgrade available here

2) You must also download a program called Pacifist available here
3) Install Pacifist and double click on the apple upgrade to mount it.

4) Next, open up pacifist and browse to the file inside the mounted image called "MacOSXUpd10.4.5Intel.pkg".

5) After it opens, click "find" and search for "IO80211Family.kext". Drag that file into the folder: "/System/Library/Extensions/" replacing any pre-existing files.

6) Delete the files "/System/Library/Extensions.kextcache" and "/System/Library/Extensions.mkext"

And reboot! Alternatively you may want to check if your wireless worked before rebooting.

7) open the disk utility (/Application/Utilities/Disk Utility), then repair permissions on your Startup volume (may take a little while)

open up terminal, and switch to root (enter sudo -s, enter your user password)

cd /System/Library/Extensions
chmod -R 755 IO80211family.kext
chown -R root:wheel IO80211family.kext

then list the contents

ls -l

make sure the IO80211Family line looks like this:

drwxr-xr-x   3 root  wheel  102 Feb  2  2006 IO80211Family.kext

check that the permissions propagated to subdirectories:

cd IO80211Family.kext/contents/plugins
ls -l

should look like this:

total 0
drwxr-xr-x   3 root  wheel  102 Feb  2  2006 AirPortAtheros5424.kext
drwxr-xr-x   3 root  wheel  102 Feb  2  2006 AppleAirPortBrcm4311.kext

then test that the extensions works:

kextload AirPortAtheros5424.kext

should give a extension loaded successfully message

then you have to go to System Preferences>Network
a message should pop up telling you you have a new AirPort. from the Show: box, pick AirPort. you can set the options here, i suggest you check the Show airport status in menu bar, make sure you click apply now.

There you have it, fully working native Atheros card!

To do now is to get the BlueTooth working...

Redirect docs and settings somewhere else

One of your IT problems is ensuring that it has enough free space on its system partition to be happy. Microsoft is no help since its default installation places directories such as Documents and Settings, Program Files, and Inetpub on the monolithic C: volume. Presumably they do this to make things simpler for users. A single volume is the most efficient allocation of disk, but when your disk does fill up, the consequences are much more serious. This page provides instructions on how to move non-OS directories to other volumes so that you can more easily avoid filling up your system partition.

Windows throws a fit when its system partition nears capacity; it's prudent to use a separate partition for application installations and user data. Here's how I move these directories under Windows manually.

This technique makes use of NTFS junctions, which are a bit like cross-linked files you may have encountered back in the day with DOS... only junctions are cross-linked on purpose! This is also similar to UNIX soft links in that you are creating a second access path to a single directory. Because Windows takes locks on some files in the Program Files and user profile directory trees, we need to use safe mode and two different administrative accounts to pull this off. Safe mode lets us work with Program Files. The logged-on-user can't manipulate its own files, but you can use two different admin accounts to copy the whole user profiles directory in two passes.

You may also want to check what Microsoft recommends for this matter. You could even go user based.
You could just do a search and replace in the registry to avoid the junctions and also create a GPO but I'd come back with that later on as we'll need to create .adm file for this purpose, but this is less error-prone and frees you from worrying about whether an installer will insist on going to your C: drive.

1. Install the linkd utility from the Windows 2000 Pro Resource Kit (It isn't available with the no-cost download of W2K resource kit tools, but I'll bet the linkd provided with the no-cost download Windows Server 2003 Resource Kit Tools is the same thing anyway). Alternatively, try Junction from Sysinternals.
2. Make sure you have at least two local users with membership in the local Administrators group. You will need to be able to login as both of these users. For clarity, I'll call these admin1 and admin2, but you can pick whatever names you like.
3. Make sure that you've logged in at least once as each of these users. This will ensure that Windows has created a profile for them. Determine the path to each administrator's profile. You need to know the directory names under C:\Documents and Settings\ that correspond to each account. If you fail to create a profile before you continue with this procedure, Windows will create the profile while you're in command-prompt-only-safemode. In that case, it does something a little different and the result will be that it will create a new profile for the user if you try to login after this procedure. That wouldn't be a disaster, but you would probably want to clean up the abandoned profile and the new/permanent profile would have a funny name like "numbertwo.copland" if your computer is named copland. I'll assume that these directories are called C:\Documents and Settings\admin1 and C:\Documents and Settings\admin2 so that I can refer to them easily later.
4. Boot into safe mode, command prompt only. Login with an administrative account (admin1).
5. C:\>xcopy /s /e /h /r /k /o /x "Program Files" "D:\Program Files"
6. C:\>xcopy /s /e /h /r /k /o /x "Documents and Settings" "D:\Documents and Settings" �? this will result in an error message about file sharing or locking or so.
7. ctrl-alt-del to access the security menu and log out.
8. login as the other administrator (admin2)
9. C:\>xcopy /s /e /h /r /k /o /x /c /y "Documents and Settings" "D:\Documents and Settings"
10. C:\>rd /s "Program Files"
11. C:\>"D:\Program Files\Resource Pro Kit\linkd.exe" "Program Files" "D:\Program Files"
12. C:\>rd /s "Documents and Settings" �? this will produce an error about file sharing or locking or so.
13. C:\>cd "Documents and Settings"
14. C:\Documents and Settings>linkd "admin1" "D:\Documents and Settings\admin1"
15. ctrl-alt-del to access the security menu and logout
16. login as admin1
17. C:\>rd /s "Documents and Settings"
18. C:\>linkd "Documents and Settings" "D:\Documents and Settings"
19. ctrl-alt-del to access the security menu and restart into Windows.