Mid-2010 Mac Mini -  black screen after installing boot camp drivers

I successfully installed Windows XP Service Pack 2 on my new Mac Mini. The display worked without issue in XP at this point.
After doing this, I proceeded to install the boot camp drivers. They installed and automatically rebooted the machine.
After reboot, Windows XP no longer has a functioning display. The display is a black screen and eventually the monitor shuts off.
Things I've tried:
- Reset PRAM
- Reset SMC
- Tried both Mini DisplayPort and HDMI connections to connect to the HDMI port on the monitor
- Booting into Safe Mode. Holding down F8 successfully brought up the Safe Mode options, but again the display was blank after choosing the Safe Mode option and attempting to load Windows.
Message was edited by: mullingitover

Update: Other stuff I've now tried--
- Swapping out RAM modules. I've tried it with the stock 2GB sticks in place, also with a single 4GB stick. Same result.
Other interesting/troubling problems:
- Unable to boot into Safe Mode with command line. The text-only interface with safe mode options that is reached by pressing F8 during windows startup is displayed. However, no matter which option I choose, the result is a dead display.
- Unable to boot with Windows XP install CD (?!). After choosing the CD at the boot selection screen, the display blanks and never wakes up.

Similar Messages

  • Black screen after installing Boot camp Win7 on iMac 27 late 2009

    I've run out of ideas as to how to fix this problem. I have a late 2009 iMac quad i5, Mountain Lion, 12GB RAM, 1TB HD (recently exchanged under extended warranty).
    I stopped counting how many times I have tried to get this up and running but I followed a whole bunch of 'how to's' on the net, including the official Appple guide, but I always end up with a black screen. I insytalled it from scratch using both, Apple drivers on CD and SD card and I can confirn that they installed correctly during my last try. That time I first installed Win Vista, then upgraded to Win 7. I took out the install DVD after first restart and left the SD card in its slot (correctly named, as suggested by Apple). the installation finished, the screen went dark for about 5 min, then the computer rebooted, the screen went dark again for another few min and after that the vomputer restarted again but this time all stayed dark and nothing happened for the better part of an hour.
    I also restarted from the Win install disk and tried to remove the ATI drivers using command lines, as suggested in one post.
    I need to run Win in Bootcamp because some application I use are very demanding so I need Win to run natively. In an earlier attempt I managed to boot Win7 from the Bootcamp partition in Parallels and I installed the Apple Drivers in that environment but it still resulted in a black screen. I also tried to remove the ATI drivers from Drivers directory manually in MacOS mode but the System wouldn't let me edit the Syustem folder at all, not even in Root user mode.
    I understand that I'm not the only one with problem and I feel for you, but please refrain from "me too" posts becuase it doesn't really solve my problem. Thank you.

    I presume that you've followed the instructions for sideloading the iMac Windows drivers into your install via USB stick? (wasn't aware the EFI recognized the SD slot as storage on boot. Now i know)
    I always found more success in just slipstreaming the drivers and install.xml file onto a custom Win7 DVD rather than the USB approach when trying with my Late 2009 27" iMac. The Win7 installer needs that enclosed .xml file in the driver package to tell it where to find the drivers so that they be loaded when the Win7 image extracts itself.
    If you're using mountain lion, then you should be receiving the proper Win7 driver set. If you wanted to create a custom image, then you can use an ISO file, the driver package and disk utility to make something you can use. Either that or you learn what edits your install.xml file needs to point the installer properly and check it manually.
    I don't know what links you have so i'll just include everything:
    Installing boot camp on a Late 2009 iMac:
    http://support.apple.com/kb/TS3173
    Direct link to Late 2009 iMac-specific Windows drivers.
    http://support.apple.com/kb/DL995
    I'd try a USB stick and the iMac-specific driver set. It should steer your insolent windows installer correctly.
    Hope this helps.

  • 2010 Mac Pro Boot Camp - Refuses to boot Windows after installing Boot Camp drivers

    Hey all,
    I have a quad 3.2Ghz 2010 Mac Pro with a Radeon 5870 and 8 GB RAM.
    I have 2 10000RPM WD Raptor drives, the first drive is my Lion boot drive. The 4th bay contains the second Raptor which has Windows 7 Ultimate 64 bit installed. Bay 2 has Time Machine, bay 3 has a Windows backup drive.
    I had first installed Windows and the Boot Camp drivers a few months ago and everything was humming along smoothly. Monday I tried to boot into Windows and it crashed immediately after the black Booting Windows screen started to change to the login window. This happened repeatedly. Nothing changed on the system that I am aware of. Whenever I tried to boot windows again, it booted into the repair mode. That did not seem to work because after running the repair it would still not boot.
    So I did what is usually required of Windows, and that was to reinstall. I reformatted the hard drive, ran Boot Camp assistant, and started the install.
    Everything was peachy so far, so I tried to reinstall the Boot Camp drivers (4.0). Did a reboot. Same problem. Doh!
    So I did ANOTHER reinstall, and everything was fine. But this time I tried to install the Boot Camp drivers off the os install disc that came with my Mac (3.1). Still no go!
    So finally I did my third reinstall and after that I did not install Boot Camp drivers. However, I did load up the CD and individually installed drivers for the Apple Mouse, Apple Keyboard, Cinema Display, etc. No problems whatsoever. Everything is actually still humming along fine.
    So it looks like running the full Boot Camp install for some reason no longer works. Which means I am missing the Apple Boot Camp control panel, but that's not really a big deal. Althought it's quite annoying to not have the functionality of the special Mac keyboard keys like volume control, etc.
    Has anyone run into this? I thought it might be a hardware problem but my Mac OS X OS exhibits no problems whatsoever.
    Thanks!

    Thank you to The hatter.
    I have a Mac Pro mid 2010 with a SSD and several internal hard disks. For some time I was trying to install Windows 7 on a fresh boot camp volume on a new WD 7200rpm 1TB hard disk. It was taking hours to install, and then I had a series of failures to reboot that proved permanent. The Window Repair utility would come up and took forever to repair the volume - but failed to actually do so, requiring completion reinstallation of the bootcamp volume. This occurred three times, between 1 day and 2 months after installation. I had already moved the Windows drive in to drive slot 1 of the Mac Pro.
    Eventually I gave up and installed boot camp on a secondary partition of the SSD. This worked fine, however is limited in capacity. So yesterday I thought I would try to install Windows on the hard disk again. The Windows installer took many hours to do its thing, and eventually a message came up that the installation had failed.
    I took your tip about possible hard disk failure, and ran Techtool Pro surface scan. It turns out that there are lots of bad blocks being reported. According to Micromat's documentation, the bad blocks being reported are those that may be in critical areas of the disk that cannot be mapped out. They recommend low level reinitialisation (with zeros) to map out the bad blocks, if possible. I am now running Apple's Disk Utility to do this, and fingers crossed that this reinitialisation succeeds, or I will have to replace the drive.

  • Windows 8 crashes and with the error "kernel_security_check_failure" after installing Boot Camp drivers.

    Hi!
    I've got a new 27" iMac (late 2013), and I was going to install Windows 8.1 (64-bit) to be able to play a few games.
    Everything went smoothly (installed normally via Boot Camp Assistant), and after the Windows setup, the Boot Camp drivers needed to be installed. After this, the computer rebooted, but crashed at a blue screen with the error called "kernel_security_check_failure".
    It rebooted a few times on its own, but after a few times, I got some options, and I chose to "refresh" the Windows 8 install, meaning it would reset the install while keeping my files (even though I didn't have any, as I never got to use it). This took some time, but it worked, and it booted into W8.
    The Boot Camp drivers had been removed though, so I had to reinstall them. After they had reinstalled, the computer rebooted and the same blue screen with the same error hit me.
    Something tells me that some of the BC drivers are messing things up. I can't find any information on this elsewhere.
    Would it be possible to install only selected drivers, to eventually find out which driver is causing the problem?
    All help is greatly appreciated!

    I finally gave up, reloaded everything, this time, using WIn 8.1 Pro, not Enterprise.  After I did the updates, patches, Norton 360, shut computer down and connected the external drives, and booted up...and got the BSOD.  This time, I went to Microsoft and downloaded the Windows Debugger, and think I may have found the problem...NORTON! 
    Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
    Am conrtacting them, but, here's the Debugger output:
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Dump\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0xfffff802`0f87e000 PsLoadedModuleList = 0xfffff802`0fb482d0
    Debug session time: Tue Jun 17 00:48:52.131 2014 (UTC - 6:00)
    System Uptime: 0 days 0:03:09.864
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 139, {3, ffffd0002852d3e0, ffffd0002852d338, 0}
    *** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
    Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
    Followup: MachineOwner
    6: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure.  The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd0002852d3e0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd0002852d338, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    Debugging Details:
    TRAP_FRAME:  ffffd0002852d3e0 -- (.trap 0xffffd0002852d3e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffe00059c129f0 rbx=0000000000000000 rcx=0000000000000003
    rdx=ffffe0005718d2a0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8020f9e8cdb rsp=ffffd0002852d570 rbp=0000000000000000
    r8=0000000000005aa0  r9=00000000000007ff r10=ffffd00066cc8000
    r11=ffffe00059963040 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe cy
    nt! ?? ::FNODOBFM::`string'+0x682b:
    fffff802`0f9e8cdb cd29            int     29h
    Resetting default scope
    EXCEPTION_RECORD:  ffffd0002852d338 -- (.exr 0xffffd0002852d338)
    ExceptionAddress: fffff8020f9e8cdb (nt! ?? ::FNODOBFM::`string'+0x000000000000682b)
       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
      ExceptionFlags: 00000001
    NumberParameters: 1
       Parameter[0]: 0000000000000003
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    BUGCHECK_STR:  0x139
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    EXCEPTION_PARAMETER1:  0000000000000003
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff8020f9ddae9 to fffff8020f9d1fa0
    STACK_TEXT: 
    ffffd000`2852d0b8 fffff802`0f9ddae9 : 00000000`00000139 00000000`00000003 ffffd000`2852d3e0 ffffd000`2852d338 : nt!KeBugCheckEx
    ffffd000`2852d0c0 fffff802`0f9dde10 : ffffe000`59c8cc40 00000000`00000000 ffffe000`54b71040 fffff800`1d6d40b6 : nt!KiBugCheckDispatch+0x69
    ffffd000`2852d200 fffff802`0f9dd034 : 00000000`00000000 00000000`00000000 ffff6d2d`50094127 fffff802`0f81458f : nt!KiFastFailDispatch+0xd0
    ffffd000`2852d3e0 fffff802`0f9e8cdb : ffffc000`061df4e0 ffffc000`061df4e0 ffffc000`061dfbf8 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
    ffffd000`2852d570 fffff800`1d7a0be6 : ffffe000`59e10120 fffff800`1d794388 ffffe000`54dfe9c8 fffff800`1d735f7c : nt! ?? ::FNODOBFM::`string'+0x682b
    ffffd000`2852d5a0 fffff800`1d7a54e2 : ffffc000`061df4e0 ffffc000`061dfbf8 ffffc000`061df550 fffff800`1d7367ea : SYMDS64+0x71be6
    ffffd000`2852d5d0 fffff800`1d737f20 : ffffc000`061df378 ffffc000`061dfbf8 00000000`00000000 ffffc000`05a9bf18 : SYMDS64+0x764e2
    ffffd000`2852d620 fffff800`1d73e171 : ffffc000`051e6a88 ffffc000`05a9bf18 ffffc000`05a9bf18 ffffe000`5988cb00 : SYMDS64+0x8f20
    ffffd000`2852d650 fffff800`1d782027 : ffffc000`061ea018 00000000`00000000 ffffe000`58409008 fffff800`1d794388 : SYMDS64+0xf171
    ffffd000`2852d680 fffff800`1d79af21 : ffffc000`061ea018 ffffd000`2852d8c9 ffffe000`58409008 00000000`10000004 : SYMDS64+0x53027
    ffffd000`2852d6c0 fffff800`1d9a3bb3 : ffffe000`58409078 fffff800`1d98b3e8 ffffe000`58409008 ffffd000`2852d8c9 : SYMDS64+0x6bf21
    ffffd000`2852d6f0 fffff800`1d9a91fa : ffffe000`5840a1a8 ffffe000`58409008 00000000`00000000 ffffe000`00000000 : SYMEFA64+0xe9bb3
    ffffd000`2852d720 fffff800`1d9ae015 : 00000000`00000000 00000000`00000000 ffffd000`2852d8c9 ffffe000`58a10e60 : SYMEFA64+0xef1fa
    ffffd000`2852d760 fffff800`1d9adf4c : 00000000`01820201 ffffe000`58a10e60 ffffe000`58a10e60 ffffe000`58a10be0 : SYMEFA64+0xf4015
    ffffd000`2852d790 fffff800`1d9b294c : ffffe000`59e0a150 ffffe000`58a10e60 ffffe000`5988ca80 ffffe000`58a10e60 : SYMEFA64+0xf3f4c
    ffffd000`2852d7c0 fffff800`1d9a2435 : ffffd000`2852d8a0 ffffe000`599a4010 ffffd000`00000000 ffffe000`59e0a010 : SYMEFA64+0xf894c
    ffffd000`2852d7f0 fffff800`1d6d528a : 00000000`00000000 ffffe000`59e0a070 ffffe000`5604e300 ffffe000`58a10e60 : SYMEFA64+0xe8435
    ffffd000`2852d820 fffff800`1d71bf76 : ffffd000`2852d960 00000000`00000000 ffffe000`5604f900 ffffe000`571dab10 : fltmgr!FltpPerformPreCallbacks+0x31a
    ffffd000`2852d930 fffff800`1d6d413a : ffffe000`57170dd0 ffffe000`571dabd0 ffffe000`59cf18c0 fffff802`0fd411a7 : fltmgr!FltpProcessShutdownRequest+0x122
    ffffd000`2852d9b0 fffff802`0fbf7518 : ffffe000`57170dd0 00000000`00000001 ffffe000`571dabd0 fffff802`0fb54a90 : fltmgr!FltpDispatch+0x13a
    ffffd000`2852da10 fffff802`0fbf7273 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopShutdownBaseFileSystems+0xb8
    ffffd000`2852da90 fffff802`0fbfb722 : fffff802`0fbfb4b0 00000000`00000000 ffffe000`59963040 ffffe000`59963040 : nt!IoShutdownSystem+0x127
    ffffd000`2852db10 fffff802`0f8d1adb : fffff802`0fbfb4b0 ffffd000`2852dbd0 00000000`00000000 ffffe000`59963040 : nt!PopGracefulShutdown+0x272
    ffffd000`2852db50 fffff802`0f94d794 : ffffe000`59965800 ffffe000`59963040 ffffe000`59963040 ffffe000`54b71040 : nt!ExpWorkerThread+0x293
    ffffd000`2852dc00 fffff802`0f9d85c6 : ffffd000`66c40180 ffffe000`59963040 ffffe000`59965800 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`2852dc60 00000000`00000000 : ffffd000`2852e000 ffffd000`28528000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    SYMDS64+71be6
    fffff800`1d7a0be6 33d2            xor     edx,edx
    SYMBOL_STACK_INDEX:  5
    SYMBOL_NAME:  SYMDS64+71be6
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: SYMDS64
    IMAGE_NAME:  SYMDS64.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  51f84c44
    FAILURE_BUCKET_ID:  0x139_3_SYMDS64+71be6
    BUCKET_ID:  0x139_3_SYMDS64+71be6
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x139_3_symds64+71be6
    FAILURE_ID_HASH:  {bf9be68b-5f04-08d4-3152-3d420dc362f6}
    Followup: MachineOwner

  • Windows 7 Freezes at Restart After Installing Boot Camp Drivers

    Hi,
    I have a MacBook Pro and am having troubles installing 32-Bit Windows 7. All seems to be functional until I install the Boot Camp drivers included on the Install Disk. I have tried using the Boot Camp 3.1 update, but the same problem occurs. After the computer freezes on the install page, I can no longer access Windows (even in Safe Mode) and am forced to restart the entire process (that is, repartition the hard drive and reinstall Windows).
    If I don't install the Boot Camp drivers, Windows seems to be functional, so I'm pretty sure it's something in the Boot Camp package causing the trouble.
    Is anyone else having this problem? Any ideas or workarounds?

    I finally got it to work. You need to go to the NVidia website and install their drivers. I think the Apple supplied ones are out of date and are causing Windows to hang. Install Boot Camp from the supplied DVD, install the update that Apple supplies through the newly installed Boot Camp, and then go to the NVidia website to manually download the drivers. I used the GeForce 300M series installer. Make sure you do all of this before letting Windows restart.
    I had a few issues with it hanging a few times, but once I was able to get into Windows it seems to be working. All of the other Apple supplied drivers seem to work.

  • Mid 2010 Mac Pro, Black Screen on start up.  Video works after I turn machine off, let it cool

    My Mac Pro is acting up.
    If I do a reset after its beenruning for a period of time I get a black screen at start up.  I have tried multiple different monitor cables and nothing seems to work.  It does seem to resart and I can here the start up chime but no display.  If I unplug the machine and let cool for 1/2 ~ 1 hour it then turns back on with no problem.
    Processor  3.33 GHz 6-Core Intel Xeon
    Memory  24 GB 1333 MHz DDR3 ECC
    Graphics  ATI Radeon HD 5870 1024 MB
    Software  Mac OS X Lion 10.7.4 (11E53)
    Display is the 27 inch cinema
    Any ideas?  Bad graphics card?

    AC if you used it this once would pay for itself. Same for a good solid UPS - a good one can stop that 1/100,000 surge that takes out a modem (if you filter of course).
    I've known people that never knew you could filter coax cable or dsl and we get enough severe storms it has been, not if it happens, but when.
    Unlike the X1900 which had a air chamber and would cause clogging you really should not need to and be pulling it out to clean dust all that much if at all.
    People have gone through 2 or 3 ATI 5770s and some 5870s due to what are probably design or bad batches especially the first months run.

  • I get a black screen after installing the bootcamp drivers on my newly created windows partition?

    I am attempting to install windows 7 on my mid 2007 core 2 extreme iMac. I open bootcamp and do all of the steps except the usb flash drive drivers from apple because the server always fails to load. After restarting, I install windows 7 to the bootcamp partition, and the screen goes black during the "Completing Installation." I wait about an hour before shutting down and rebooting into my Mac partition. I use paragon ntfs for mac and go to the drivers folder and delete the atikmdag.sys file and restart. Booting into the windows partition, I get the error that says "Windows installation has failed because the system unexpectedly restarted. Click ok to restart and redo installation" or something along those lines. Instead of pressing ok, I press shift+f10 and open regedit. After opening regedit, I go into some registry file for the setup (I don't remember where this is located, although I can find it if needed), and I change a value from 3 to 1. After doing this and restarting, It boots regularly with a super low res screen but it boots without problem. I go to the apple website and download the appropriate bootcamp support software and install on my windows partition. After restarting, the screen is black again. I assume this is another video driver problem again because the black screen seems to always be video driver problems; however, its odd that the bootcamp support software would give me an incorrect video driver as it is directly from apple. Would this be the problem or does anyone know a fix? Any help is appreciated.
    Cheers,
    Adam

    If you bought your RAM at a place that also sells PC RAM you may have gotten mislabelled RAM. PCs can handle different RAM speeds so they’ll often label higher speed RAM as a lower speed rather than make two different speeds of RAM. But Macs are much more picky. They require a RAM stick to be exactly 667mhz not 675mhz or 800mhz. The way to tell is to put one of your old RAM sticks in and it will force the new RAM to run at the correct speed.
    This is from one review of PNY RAM:
    "These modules are actually 800Mhz. PNY no longer makes or sells 667Mhz modules. Not all computers that require 667Mhz are compatible with 2 800Mhz modules. They refuse to down clock properly. This is especially true with a number of Core 2 Duo MacBooks. Spoke to PNY support, they flat out told me that yes, they sell 800Mhz modules in 667Mhz packaging. If you RMA a module that is 667Mhz (or supposed to be 667Mhz) they will replace it with an 800Mhz module as they no longer have any 667Mhz SODIMMs, not even for RMA replacement!"
    These are good online stores for Mac compatible RAM
    OWC http://eshop.macsales.com/shop/memory/MacBook/DDR2/ - They offer Mac tested RAM at very good prices.
    Crucial Memory http://www.crucial.com/ - good place to buy RAM from all over the world. They also have an excellent memory selector that allows you to choose memory based on your computer's model
    Data Memory Systems http://www.datamemorysystems.com/apple-memory.asp - another good, cheap place to buying RAM if you live in the U.S.

  • Install Windows 7 on a Mid 2010 Mac mini using USB or SD media?

    Is is possible to install Windows 7 on a Mid 2010 Mac mini using USB or SD media?  I have not figured this out.  Here's what I have observed:
    I can install OS X Lion using USB or SD media. Both are detected in the boot menu, and will boot.
    An SD card with Windows 7 installation files formatted MBR/FAT32 using diskpart appears (with an SD card icon) in the boot menu but when selected as a boot device, the boot fails and the existing OS X instance on the Macintosh HD starts.  A USB stick formatted as described does not appear in th boot menu at all.
    An SD card or a USB stick formatted as described will boot on a Mid 2011 MacBook Air, and can be used to install Windows 7.
    Is this due to EFI differences between a Mid 2010 Mac mini and a Mid 2011 MacBook Air?
    Thanks.

    The Mac Mini Mid 2010 has a DVD player built in, you can startup and install from a Windows 7 DVD. The Mac Mini Mid 2011 does not have a DVD player built in. I am happy that in new computers I can make use of an USB-stick to install Windows 7. Windows 7 uses MBR and Mac OS X uses EFI and that is why it was not possible on a Mac Mini Mid 2010. I think the EFI on a Mac Mini Mid 2011 is different.
    I should like a firmware update on my Mac Mini Mid 2010 if possible. In that case I could choose between DVD or USB stick if I want to install Windows 7.
    I also have a FireWire CF Card Reader. I think it is not possible to install Windows 7 via FireWire too.
    I do have an external USB HD with 2 partitions: Mac OS X 10.6.8 and Windows 7, but is is not possible to start up Windows 7 from the external HD.  It is possible to start up Mac OS X 10.6.8 from the external HD on a Mac Mini Mid 2010.

  • Help: Install Snow Leopard Server 10.6.0 on Mid-2010 Mac Mini, then update?

    I just purchased a Mid-2010 Mac Mini with Snow Leopard Client 10.6.3 (the new ones just released) with the idea of installing my copy of Snow Leopard Client on it and using it as both a network server and media server.
    I own Snow Leopard Server 10.6.0 (the initial DVD release) and was thinking I could do a fresh install and update to 10.6.4 on the Mini without problem, but that didn't work. I also tried doing a Target Disk Install to the Mini using my MacbookPro, but the installer choked at the Machine Checksum saying MBPs weren't supported to run the installer.
    So, that blows both of my previously known installation options. I was wondering if anyone else with the new Mini and Snow Leopard Server had any suggestions on how to get my current version of Snow Leopard Server (10.6.0) installed on the Mini and then run system updates to get it to boot properly.
    Thanks

    Allan Eckert wrote:
    Hi GrainFocuser;
    Your copy of SL Server version is probably too old to install on the new Mac Mini. It probably doesn't have all of the correct drivers for the newer hardware.
    You might have better success with your alternatives if you post over on the server forum instead of here.
    Allan
    Message was edited by: Allan Eckert
    Allan, thanks.
    It is pretty clear that my installation disk is too old, hence looking for options and suggestions.
    In years past with previous versions of Server, there was a way to install an outdated install disk (a point release or 3 behind) and then run the necessary installation updates...either through target disk mode or on to a separate boot disc.
    So, with my 10.6.0 Server Install disc, I am not able to do so in either scenario because a) My other admin machine is a MB Pro and the installer performs a hardware checksome preventing install...so no Target Disk Mode, and B) Install on other disc from mini, again Hardware checksome since hardware not recognized.
    I am looking at options to enable an install with my disk short of having to physically walk into Apple (a huge trek) and get a new install disk or ask Apple Support to mail one.
    So, again... Any options from OS X Server Admins out there?

  • Airdrop - Mid 2010 Mac Mini - Upgraded to OS X Yosemite

    I upgraded my Mid 2010 Mac Mini to Yosemite yesterday and thought I'd try using Airdrop to send a file to my almost brand new IPad with OS 8. Airdrop is listed in Finder on my Mac Mini but when I open it it doesn't find my iPad but the screen states "Airdrop let's you share instantly with people nearby. To share with someone using a Mac, ask them to go to Airdrop in the Finder".  If alternatively I right click on a document in Finder and select 'share' the Airdrop option is there but greyed out and if I click on Airdrop a message appears stating "To share with someone using a Mac, ask them to go to Airdrop in the Finder" - no mention of what to do if you want to share with an iPad. I have Bluetooth and Wi-Fi switched on on both devices and have the Airdrop status set to Everyone on the iPad.  On the Mac Mini in settings - extensions - share menu, the Airdrop box is white with black tick whereas other tick boxes are blue with a white tick. Does all this mean that my Mac Mini even with Yosemite can't operate Airdrop at all or maybe only with another Mac (maybe it's too old)? Or maybe I'm missing something?

    You need a newer model Mac to use AirDrop between an iOS device (e.g. iPad) and a Mac
    System Requirements
    To see if your Mac works with AirDrop, make sure you’re in the Finder by clicking the desktop (the background area of your screen), or by clicking the Finder icon in the Dock. Then, check to see if AirDrop is listed as an option in the Go menu. If you don't see AirDrop listed, your Mac doesn't support this feature.
    In order to transfer files between a Mac and and an iPhone, iPad or iPod touch
    your iOS device needs to include a lightning connector
    your iOS device needs iOS 7 or later installed
    your Mac needs to be a 2012 or later model with OS X Yosemite installed
    Your Mac and iOS device both need bluetooth and Wi-Fi turned on. You do not have to be connected to a specific Wi-Fi network.
    To transfer files between two Mac computers, you need the Mac models listed below with Wi-Fi turned on and OS X Lion or later installed.
    MacBook Pro (Late 2008 or newer)*
    MacBook Air (Late 2010 or newer)
    MacBook (Late 2008 or newer)*
    iMac (Early 2009 or newer)
    Mac Mini (Mid 2010 or newer)
    Mac Pro (Early 2009 with AirPort Extreme card, or Mid 2010)
    Mac Basics: AirDrop lets you send files from your Mac to nearby Macs and iOS devices - Apple Support

  • Audio issues on Mid-2010 Mac mini upgraded to Lion

    I'm using a Mid-2010 Mac mini that came with Snow Leopard but I recently upgraded it to Lion. Every app works pretty well except for audio playback. Whenever I play a game or play a movie, audio stutters every 8 to 10 seconds for like a sec and it comes back in. Video keeps playing fine. It's pretty annoying since I can't properly play games or watch movies anymore. The rest of my apps are working very well except for Boxer which seems to have taken a performance hit.
    Currently, the hardware hasn't been upgraded in any other way - meaning it still has the original 2 GB RAM memory. It's connected to my HDTV via HDMI. It didn't manifest this issue until the upgrade to Lion.
    I've tried closing every app but it doesn't seem to help. Hope you can help me out. Thanks!!

    You need a newer model Mac to use AirDrop between an iOS device (e.g. iPad) and a Mac
    System Requirements
    To see if your Mac works with AirDrop, make sure you’re in the Finder by clicking the desktop (the background area of your screen), or by clicking the Finder icon in the Dock. Then, check to see if AirDrop is listed as an option in the Go menu. If you don't see AirDrop listed, your Mac doesn't support this feature.
    In order to transfer files between a Mac and and an iPhone, iPad or iPod touch
    your iOS device needs to include a lightning connector
    your iOS device needs iOS 7 or later installed
    your Mac needs to be a 2012 or later model with OS X Yosemite installed
    Your Mac and iOS device both need bluetooth and Wi-Fi turned on. You do not have to be connected to a specific Wi-Fi network.
    To transfer files between two Mac computers, you need the Mac models listed below with Wi-Fi turned on and OS X Lion or later installed.
    MacBook Pro (Late 2008 or newer)*
    MacBook Air (Late 2010 or newer)
    MacBook (Late 2008 or newer)*
    iMac (Early 2009 or newer)
    Mac Mini (Mid 2010 or newer)
    Mac Pro (Early 2009 with AirPort Extreme card, or Mid 2010)
    Mac Basics: AirDrop lets you send files from your Mac to nearby Macs and iOS devices - Apple Support

  • Windows vista 32 Bit Ultimate. Black screen after installing drivers B-Camp

    I installed windows vista Ultimate 32 bit on my 2.26ghz mac mini 2gb ram. after installing vista and setting up my account, i installed the drivers from the apple CD that came with the mac. it installed all the drivers and requested me to reboot, so i did. once i rebooted, i got a black screen with a thin green line through the center of the screen. i hear the bootup sound but that is all i see. Any tips or anything on how to fix this?

    How did you solve this? I am having the same problem.

  • Boot Camp - Black Screen after installing Windows 7

    Hello guys!
    I have tried to install Windows 7 several times and so far no success.
    Everything goes fine until I complete Win7 installation.
    Then when I install Boot camp drivers the computer prompts for reboot.
    After the login screen, I am able to log in, but the screen turns into BLACK!.
    And I cannot do anything but shut it down with the power button. I can still hear that the laptop is on, but screen stays black.
    I have tried removing the ATI and NVIDIA Drivers as recommended in this forum:
    http://forums.macrumors.com/showthread.php?t=840528
    But so far I get the same result over an over.
    Anybody is facing the same issue?
    I have MACBOOK PRO
    MAC OS X 10.6.8
    AMD Radeon HD 6490M (ATI)
    Intel HD Graphics 3000
    Quad Core i7 Chip, 4GB RAM 500GB HD
    Please Help!!

    I did install : Display Driver +  Catalyst Control Center dowloaded from AMD support website:
    http://support.amd.com/us/gpudownload/Pages/bootcamp-win7.aspx
    The result is still the same - BLACK SCREEN
    I rolled back to initial configuration.
    Then I installed the AMD driver.
    In device manager it shows as the AMD  Radeon HD 6490M driver for the display/Graphics card
    Everythig is fine until I install the Boot camp drivers.
    Then after the reboot I face the same issue.
    However the driver for AMD still stays there in the devive manager.
    Any other ideas, suggestions?
    thanks!!

  • Mid-2010 Mac Mini, dead optical drive: Are any slim Firewire DVD burners compatible?

    The optical drive on my Mac Mini seems to have died prematurely, as the OEM drives are known to do. Estimated cost of replacing the internal component: $170. And it would be the exact same model Apple optical drive, not a more robust one.
    Now very reluctantly thinking of adding yet another peripheral. USB ports are pretty well filled but I don't use the Firewire port for anything.
    Trouble is, since Apple discontinued Firewire, the manufacturers of Mac-compatible optical drives aren't making Firewire models any more.
    There are a few recent Firewire DVD burners from PC peripheral manufacturers, such as Acer, Aopen, Dell, Pioneer, Sony (Amazon reviews say it's restricted to burning Sony media) in a small "slim" form factor.
    Anyone have information about their compatibility with Firewire 800 on mid-2010 Mac mini, Mac OS 10.10.1 Yosemite?

    There are some steps involved which may translate to tedium,
    as noted in the repair guide for the Mid 2010 Mini from iFixit.
    •Mac Mini - Mid 2010 Repair Guide - iFixit:
    https://www.ifixit.com/Device/Mac_Mini_Mid_2010
    At about Step 25, of an overall rated Difficult process, you can
    see the Optical Drive, and likely be at a point to install replace-
    ment, then reverse the process; paying heed to advice given.
    •Mac Mini - Model A1347 - Optical Drive Replacement - iFixit:
    https://www.ifixit.com/Guide/Mac+mini+Model+A1347+Optical+Drive+Replacement/3167
    At least you can get into this computer. Be sure to have a spare
    optical drive cable and other possible items that may get broken
    in the process. Oh there also is a PRAM battery in this computer
    that may or may not need replacement while it is open...
    If at one point, if several parts were to be replaced at one time, a
    visit to a service technician becomes very cost effective. Find one
    that will install the parts you may get from third-party sources. If
    you know someone at a college computer lab, they may be able
    to perform the swap, test their work, and be done, in short order.
    Or, chose to use an external inexpensive 'superdrive' equivalent.
    I'd heard the LG brand was among some that work, and can also
    be used to boot the computer from System DVD or utility discs...
    It is a USB drive, can burn DVD/CD media, and is not costly.
    The ability to swap out the defective optical drive, and replace it
    with an SSD or second storage drive, may be a way to go; but
    it also would be at least as tedious as optical drive replacement.
    This may add value to the device, in a resale situation later.
    That would use the 'drive doubler' idea referred to at macsales.
    In the above main guide, is a primer on how to swap out the optical
    drive and replace it with a second hard disk drive or solid state drive.
    Similar to what the OWC site says, but they have a good kit, too.
    Good luck & happy computing!

  • Upgrade a mid 2010 Mac Mini or buy a new one?

    I have a mid 2010 Mac Mini with a 2.4 GHz Intel Core 2 Duo processor, 2 GB SDRAM DDR3, and a 320 GB HDD. I use it primarily as a way to watch movies, TV, and internet videos on my TV. However, lately it has become excruciatingly slow with choppy video playback. I realize upgrading the RAM and/or the HDD to a SSD would offer an improvement. But my question is, would it be better to upgrade a computer that's getting close to 5 years old now, or buy a new Mac Mini, despite the complaints I've heard about the inability to upgrade RAM and/or hard drive.
    Thanks

    For your use going to the max of 8 GB of memory and an SSD will be fine.

Maybe you are looking for