Msi Wind Forums • View topic – 100% Working Snow Leopard Retail install
This solution seems to work. Here are the exact steps I followed
1) Image your Snow Leopard CD
2) Restore the image on your USB stick
3) Run NetbookMaker (the instructions mention running Netbookinstaller which is an error)
4) Boot the USB stick
5) Format the drive as 1 partition, make sure in options you select GUID partitions. (This is in Utilities/Disk Utility if you’re not used to this)
7) Boot and install the Realtek drivers ( http://files.binaryfactory.ca/windtools/Realtek_RTL8187SE_MacOS10.5_Driver_073_UI_1.6.2.zip )
8) Reboot. At this point, video works, Wifi works, sound doesn’t, and I haven’t tested everything else.
9) Enable Filevault. The whole point of Netbooks is to bring them to places where you’ll forget them isn’t it?
9.5) Enable Time Machine (See point 9)
10) Install 10.6.1 as I had forgotten to slipstream it to my USB stick. I didn’t install the combo. I’m such a rebel.
More to come tomorrow or Friday !
I recently got a Lacie D2 network drive. It has been working pretty well, I’m using it for SMB share, AFP share, time machine and to share movies and music to my ps3.
I own a copy of Office that is the download-able version. It is basically a selft-extracting exe that then runs a setup.
I had it stored in a SMB share on the Lacie drive. I ran it. The setup crashed. Then, AFP crashed on my NAS. Rebooting it made things worse. AFP wouldn’t start. Bonjour wouldn’t start. Not long after, SMB wouldn’t start.
Logfiles seemed to indicate that the system’s drive was full. I presume the system is stored on Flash storage in the NAS itself.
I contacted Lacie support. They could only instruct me to reset the unit to factory settings. At least, no data was lost.
I then asked if it could be related in any way to me running a setup file directly from the share, expecting them to tell me there is a known issue when reading a file and writing a lot at the same time or something similar..
Instead, I got this reply:
Tech Support dude.
Makes no sense
Posted: September 3, 2009 @ 7:23 AM
It was related to running the .exe file on the drive. The file is proprietary to an OS such as XP, Vista, or Mac OS X. Running the file on a non-conforming OS is going to create severe havoc and other issues. I am glad the reset resolved the issue.
Tech support dude