Blog

NO! …Not at the very least until such time as I have no pressures and fancy an experiment (everything backed-up of course). On my Jan 2010 MacBook Pro (unibody), most things “ain’t broke” at present, the only issues are that the FW800 port and ExpressCard ports work only in Mac OS, not Windows 7, but I’ve found no explicit mention of these issues having been fixed. Shame, quite a few Windows people are put off Macs for that kind of reason.  On the other hand while some people report no problems, others do report issues (sometimes due to old/unhandled existing nVidia drivers on their systems), as follows.

• nVidia driver problems affecting install, display (and possibly keyboard).
  • Installation may hang or fail or appear to succeed but not completely in practice.
  • Screen may appear at low-resolution (e.g.VGA) or may black-out
  • Sleep (power management) may give a BSOD.

(more…)

No solution noted as of March 2010: http://discussions.info.apple.com/thread.jspa?threadID=1972915&start=15&tstart=0

Here are the steps that worked for me:

• First, boot from Windows 7 installation (DVD).
  • On a MacBook Pro (with BootCamp), power-on with Alt/Option key held down.
    • Initially, only the standard Mac and Windows options appear, but wait a few more seconds and then additional options appear for Windows and EFS methods of booting from the DVD.
    • I selected the Windows option (guesswork).
• Select the System Recovery option http://www.sevenforums.com/tutorials/668-system-recovery-options.html
• Select the STartup Repair option http://www.sevenforums.com/tutorials/681-startup-repair.html

As it happened, this whole process was a distraction.  I was trying to get a BootCamp-W7 Virtual Machine (VM) in Parallels working - it would boot OK in BootCamp but not Parallels.  It was a matter of identifying the problem by excluding other possibilities, as much as hoping for this to be the fix.   However I record the process I went through, here, for posterity.

On MacBook Pro, used Sony Clip Browser (ClipBrowser) to import footage from a Sony XDCAM-EX to Mac OS HFS+.  This machine had MacDrive installed, enabling Windows apps to directly access files on the HFS+ file system.  On same machine, under Boot Camp (BootCamp) and Windows 7, ran Sony Vegas NLE.   Successfully imported and used footage by both of the following methods:

• Sony Vegas’s Device Explorer [View > Device Explorer].
  • This took several minutes to import.
  • Importing resulted in copying the [.mp4] file (and other files) to the NTFS partition.
• Direct use of [.mp4] on the HFS+ partition.
  • No need to import as such, just constructed waveforms etc.
  • This completed in seconds.
  • Only downside is that it ewas unable to save the waveform files etc., due to my config of MacDrive (read-only), so it would have to do this every time I opened the project.
    • Have yet to try the same thing when MacDrive has config for full read/write access.

GRAID mini was initially a single partition formatted HFS+ under GPT partitioning-scheme.

Repartitioned it as MBR partitioning-scheme where the HFS+partition (existing but reduced) was followed by an NTFS partition.  The repartitioning of the disk and the formatting of the NTFS partition was accomplished from Mac OS, using the iPartition application.

When I first connected the resulting disk to a MacBook Pro, the HFS+ partition was seen OK under Mac OS.  However the NTFS partition seen from Boot Camp / Windows 7 caused Windows Explorer to crash, whenever it was selected or right-clicked in that applications left-hand pane.  On the other hand if the thing selected in the left-hand pane was the computer itself then the NTFS partition (among other volumes) was listed in the right-hand pane, and it was possible to right-click that without the application crashing.  Also, no problems were experienced when accessing it from commandline, or when using Windows Explorer to look inside its folders (as opposed to teh top-level).

By right-clicking the NTFS partition in the right-hand pane, selected options to:

• Define it as a mainly-videos drive.  Presumably alters the block size or something.
• Change that volume’s name, from “GRD mini NTFS” to “GRm HTFS.  Not sure if relevant.

Subsequently was accessed OK in both left and right hand panes.

Some hard drives attached with FireWire may perform slowly with Windows 7 on a MacBook Pro (15-inch, Mid 2010).  Not aware of any such problem on my system, but found this in passing, worth keeping a note of…[http://support.apple.com/kb/TS3188]

• MacBook Pro (15-inch, Mid 2010): FireWire drives perform slowly with Windows 7
  • Last Modified: April 14, 2010
  • Article: TS3188
• Issue:
  • Some hard drives attached with FireWire may perform slowly with Windows 7 on a MacBook Pro (15-inch, Mid 2010).
• Products Affected
  • Boot Camp, MacBook Pro (15-inch, Mid 2010), Windows 7
• Resolution
  • This situation may occur because of an issue in the 1394ohci.sys driver in Windows 7.
  • Microsoft has posted a “hot fix” for this issue.  See the Microsoft website for more information.

On a MacBook Pro, official SxS card in ExpressCard slot is seen OK by Mac OS. However on same machine running Boot Camp Windows 7, it is not seen.SxS drivers have been installed in both cases (OS X & W7). For W7 I tried a couple of versions, including the one from SXS Drivers, stated as “Updated for Windows 7″. The webpage also says “This OS must be factory-installed”, so I wonder what special things they do at the factory!I see at an apple forum some comments (at [http://discussions.apple.com/thread.jspa?threadID=2306364&tstart=0]) that “there is still no ExpressCard support in release 3.1 (of Boot Camp)” and “At the moment I’m aware of exactly zero Firewire ExpressCards that work in Windows 7 on Boot Camp”. Not familiar with this territory - maybe implies that the Sony drivers are not sufficient?Posted my problem at DvInfo: [http://www.dvinfo.net/forum/sony-xdcam-ex-cinealta/477958-mbp-boot-camp-w7-cant-see-sxs-osx-can.html].  Response confirms Apple not only do not support ExpressCard (EC) under Boot Camp on a MacBook Pro, they may never do so, given that the new model lacks any EC slot.

Steps:

1. Use iPartition, reduce existing HFS+ partition to half-size.
2. Don’t create the other partition yet.
3. Change Partition-Scheme (from GPT) to MBR
   • Otherwise the partition won’t be visible to windows.
4. Now create the other partition, e.g. NTFS.
   • That option only became available once the partition scheme had been changed.
   • Result: [ MBR | HFS+ | NTFS ]

Problem:

• MacBook Pro, when in Boot Camp Windows 7, gets uncomfortably hot (in its heatsink areas, the bar above keyboard and also the chassis underside).  In comparison, it runs pretty cool (temperature) under Mac OS.

Reason:

• No fan control when in Boot Camp Windows mode.

Popular Solution (does not imply any recommendation):

• When in Boot Camp windows, use Lubbo’s Fan Control [http://sourceforge.net/projects/lubbofancontrol]

Some good links (as of 2010-03-27):

• http://www.almico.com/sfdownload.php
• http://sourceforge.net/projects/lubbofancontrol
• http://www.sevenforums.com/general-discussion/17177-fan-control-macbook-pro-15-inch-under-windows-7-a.html
• http://www.lokiman.com/blog/2009/12/13/fan-control-for-macbook-pro-under-snow-leopard-or-windows-7-and-more

Experiences:

• Just copied the contents of the zip file to  [C:\Program Files (x86)\Lubbo’s Fan Control] and ran it from there.  It has files [inpout32.dll] and [inpoutx64.dll].
• Ran it but it gave error messages:
  • (The) Following process(es) is/are using SMC:
    • kbdmgr
  • It’s not an error, but Lubbo’s Fan Control cannot share apple SMC access.
  • Do you want to kill it/them?
  • NO = the system may freeze.  Try only if you are running BootCamp 3.1
  • YES = the incompatible process(es) will bekilled and the program will start.
    • But I have read elsewhere that this means function keys won’t then work (for that session).
    • Didn’t work - it said “It was not possible to load IO driver.  Retry?” and “(May be better to press CANCEL and reopen the program)”
  • CANCEL = this program will exit
• Someone else had the same problem but found a solution that appeared to work for them:
  • “…upon updating to .NET 4 and running with “administrator control” or whatever, it appears to be working. [http://sourceforge.net/projects/lubbofancontrol/forums/forum/970570/topic/3507393]
  • Further confirmation that (for Windows 7),  .NET v4 is needed [http://sourceforge.net/projects/lubbofancontrol/forums/forum/970570/topic/3444415]
    • “…I have the same problem with the error about the IO drivers. When I try to install .NET framework 3.5 using the setup file, the screen just flashes and nothing happens. I have a feeling win7 did not install it.  This is in win7 64 bit professional”
    • “The problem was fixed after I installed .NET framework 4.0 Beta for windows “
• So it seems that to get Lubbo’s utility working I have to:
  • Kill a system process
  • Install a version of .NET that is not yet officially supported.
    • I’ll write a separate blog post about .NET
• Life on the edge, huh?

Recap:

1. Backed-up via Time Machine to a low-cost (£60) USB-powered 0.5TB hard drive that will be carried around with the laptop (can that drive be backed-up itself?)
   • Turned off Time Machine (auto-backups) afterwards.
2. Updated everything
   • Several system restarts required, and re-ran the Update function until no more updates available.
3. Backed-up again viaTime Machine.

Continue:

1. Ran Boot Camp Assistant
   • It prompted me to print its instructions.  I decided to accept this.
     • I connected my printer.  System prompted for printer-driver download - I accepted.
     • I selected the print option to format the instructions specifically for my (make of) printer.
     • From Preview, the instructions occupy 14 pages.  Thinking green (and clutter-avoidance) I elected instead to save it as PDF to a memory stick that I can view elsewhere.
2. Read thru the Boot Camp instructions
   • It seems I have done it right so far (update everything & backup)
3. Boot Camp Assistant: Actions
   • Click Continue (onwards from the printing stage).
   • Partitioning:
     • Select Divide Equally
       • (Don’t know what sizes I need, presumably can alter proportions later if needed using e.g. via iPartition).
     • Click Partition
       • (Is very fast)
   • Windows Installation
     • Insert Windows disk.
       • There are two options (disks): 32-bit and 64-bit.  Let’s go for 64-bit.  In case of any residual doubt:
         • “The short answer is that you should go with Windows 7 64-bit unless you’re running a system well into its antiquity where driver support is going to become an issue. ” [http://www.techspot.com/guides/177-windows-install-32bit-64bit]
     • Click Start Installation
       • (Even though Boot Camp Assistant (BCA) does not mention Windows 7 as an option, onlyXP & Vista.)
     • Locale info:
       • Language: English; Units: UK; Keyboard: UK
         • (What is “UK Extended” ?)
       • Next
     • Install Now
       • (Accept License)
     • Installation option: Upgrade or Custom(BCA instructions don’t mention this choice)
       • Default is Upgrade but this is a fresh installso choose Custom
         • Warning (from instructions): “It’s important to select the correct partition when installing Windows so that you don’toverwrite Mac OS X on your computer.”
       •  Selected the Boot Camp partition (Disk 0 Partition 3), but…
         • “Windows caannot be installed to Disk 0 Partition 3″
         • …because it has not yet been formatted as NTFS (did I miss that stage?)
       • Clicked Drive Options, and, with Partition 3 selected, clicked Format.
         • There were no format options e.g. NTFS or other, it just did it, taking only a few seconds.
       • Clicked Install, now it worked.
       • Looking thru the BCA instructions, that formatting step is indeed mentioned, all is well.
         • “The Windows partition is formatted using the NTFS file system”
       • (installation automated processes took half an hour or so)
       • Enter names for user (account) and computer (to distinguish it on a network)
       • Enter a password
       • Enter Product Key and accept default option to automatically activate when on-line.
       • Select Use Recommended Settings (e.g. for updates policy)
       • Accept TimeZone as UTC
       • JoinWireless Network
         • Enter key, accept Automatically Connect policy
         • Selectit as Home Network (trusted)
       • (Windows now began its update processes)
         • First it downloaded a manifest- list of available updates
         • After this it prompted to “click here for available updates”.  Did so.
         • It offered “11 important updates” and “2 optional updates”.  I accepted them all.
           • An update clash (my term) occurred - it said “Some updates were not installed” and “…try again in a few minutes”
           • Waited several minutes and tried again - it worked: 10 updates successfullyinstalled, then required restart (did it).
   • First proper login to Windows.
     • Note there had been no prompts for drivers etc.
   • Mac Hardware Drivers for Windows
     • Insert the Mac OS install-disk … after ejecting the Windows install-disk.
       • But the”Eject Disk” button has no effect (presumably due to no driver yet)
       • Workaround: Windows Explorer > DVD Drive > Eject
     • Autoplay (yes/no): Windows Support > setup.exe.  YES.
     • Security: Allow it (Boot Camp) to make changes to computer.  YES.
     • Boot Camp: Accept license, allow “Apple software update for windows”
       • (It took some significant time)
     • Restart
       • Doh - I left the Mac OS install-disk inserted; as a result I feared the machine would boot from that disk.  However in practice it was Windows that came up.
         • The default OS can be changed via the Boot Camp icon in system tray.
       • Unable to log in - keyboard doesn’t work.
         • (Yes, this is familiar Windows behaviour…)
     • Restart again.
       • Now it works fully.  Keyboard and disk-eject too.
   • Settling-in to Windows
     • Config the system tray to always show all icons.
     • Got warned that there is no antivirus as yet.
     • Purchase Parallels 5, which Kapersky AntiVirus comes bundled with, and I want Parallels anyway.  Cost around £60.
   • x
4. Install Parallels
   • Purchase & download Parallels 5 desktop for mac.  Is a “.dmg” file of size 222 MB.
   • Restart machine in Mac mode.
   • Backup (Time Machine)
   • Run installer.  It says the installation will occupy around 450MB of disk.
   • Backup (Time Machine)
   • Run Parallels.  Prompts for activation (license key/code).  Did so.
     • (Parallels then did a “prepare for first start”)
   • x
   • Create new Virtual Machine onto the Boot Camp Windows 7 system.
     • New Windows Installation
     • Boot Camp Partition
     • Windows 7, “Let other Mac users access this virtual machine”, sharing “Home folder only”.  Create.
     • Done.
   • Now I have two new desktop items, for Parallels Virtual Machines (VMs): “My Boot Camp” and “Windows 7″.
     • How come I’ve got two items, not just one?  What are each of them for?
     • Others are similarly confused, e.g. http://forums.macrumors.com/showthread.php?t=829128
     • Looks like the answer is at http://download.parallels.com/desktop/v5/docs/en/Parallels_Desktop_Users_Guide/23414.htm,”If you install Parallels Desktop on a Mac computer with a Boot Camp Windows partition, and Parallels Desktop detects that there are no virtual machines on the computer, it automatically creates a new virtual machine for this Boot Camp partition and places it to the following location: <Username>/Documents/Parallels/My Boot Camp“
     • So I need not have created one explicitly.  I guess “Windows 7″ is the one I (explicitly) created, “My BootCamp” is the one that Parallels (implicitly) created.  In that case all I need to do is delete the “Windows 7″ one.   Did so.
   • Ran the “My Boot Camp” virtual machine for the first time.  It said “Setting up forthe first time - may take some time”.  In that case I regard this as part of the installation process.
     • Got to the login prompt (for Windows 7) and, reasonably enough, required me to log in before it could act further.  Dod do.
       • (It said “Please wait while the virtual machine is being upgraded”, then after several minutes “…was successfully upgraded”)
     • Now I had a Windows login prompt again.  Logged in.
       • The VM runs in Coherence mode by default.
       • (It said “The Windows application folder is being added to the dock” and “To remove the folder, edit the Shared Applications settings in the virtual machine config)
     • Installed Parallels Internet Security (Kapersky AntiVirus etc.)  - it is not installed by default - you have to take action, did so as follows.
       • Select the Parallels VM Launcher (window).  In the Mac (top-screen) menu (when that window is selected), click:
         • Virtual Machine > Install Parallels Internet Security
       • (Took maybe 30 minutes to download)
       • Began installing itself.  As part of this, Windows Firewall was disabled (as indicated by a Windows security message), so I unplugged my router, just in case.
       • At the end of installation, the VM restarted itself (successfully).
       • Following restart, I plugged my router back in and told Kapersky to update.
       • Following Kapersky update, a VM restart was required.  Did so.
       • Did another Kapersky update.  Status: Up-to-date.
     • Ran a full system scan.  Takes quite some time (started 18:08, finished ????).  No issues detected.
     • Windows security messages about “No firewall” and “Parallels Internet Security is on but reporting its status to Windows Security Centre in a format that is no longer supported”.
       • The “no longer supported” message: someone said “I had to uninstall Kaspersky as well as Parallels Tools, and then reinstall Parallels Tools, to fix this problem. That seems to have worked.”  http://forum.parallels.com/showthread.php?t=96492&highlight=longer+supported
       • I tried simply the VM Launcher option “Reinstall Parallels Tools”, because being simple, it was worth a try.  It restarted the VM.
         • No effect - didn’t fix it.
       • Try following another person’s advice “If Tools are already isntall, you can remove them from (Control Panel > Add/Remove Programs>) Programs & Features list, restart Windows and load them from Virtual Machine menu. “.  Did so.  VM Restart.
     • Configure: Do not backup with Time Machine.  This is very important!
   • x
5. x