3 Replies Latest reply: Feb 16, 2012 11:35 PM by Cattus Thraex
vickyj Level 1 (10 points)

Hello all,


I have a Late 2009 Mac Mini Server (Macmini 3,1) with OS X Lion.

I have created a Bootcamp Windows Partition on one the 500GB Disk using Bootcamp 4.0.

After the partition is created, I have tried installing Windows 7 using the Bootable USB method as well as using the CD Drive from the attached SuperDrive.


But all I encounter is either the blinking cursor or after the "Starting Windows" logo, a BSOD.


Any tips/help on how to proceed?


Thanks in advance.

Mac mini, Mac OS X (10.7.1)
  • Cattus Thraex Level 4 (1,715 points)

    If in Lion, use BC to create:

    - a USB Windows boot flash

    - download additional Apple software for windows, to be used after installation

    - made partition

    - install Windows, it will surely work

    Do not forget to format BC partition with Windows utility before installation proper. Or format it as NTFS while still in Mac OS by using a utility like NTFS-3g.

    As I see, that mac does not need any firmware update, so go for it.

  • vickyj Level 1 (10 points)



    Thanks for the reply.


    I did use BC to create the USB stick. I also tried to create the USB on a WIndows Machine (just in case). But still can't boot from USB. What's the WIndows Utility you mentioned?


    Also, according to the this LINK, The firmware for Macmini 3,1 should be MM31.0081.B06 (EFI 1.2).

    However, the BOOT ROM info on my mac mini says MM31.00AD.B00 and I can't seem to update the EFI Firmware. I get a message "This computer does not need this update" when I try to run the MacminiEFIupdate.pkg

  • Cattus Thraex Level 4 (1,715 points)

    BC stands for Boot Camp, NTFS-3g is a utility for Mac OS X allowing to format external disk as NTFS; also NTFSmounter, a tiny similar app.

    Hm, if a certain EFI is needed, then yes; according to Matracker, your generation does not need any firmware update, perhaps your description is not accurate. Anyway, if a firmware update is needed, it should be detected by software update (initially, these updates were not detected, users had to pay attention to newcomers).

    If the boot flash was created with BC and using a valid Windows disc or iso image, I do not see why it should not boot. Did you test the original? Is it indeed a boot Windows disk? BAsed on what you say, this seems the reasonable explanation.