fantasymor.blogg.se - Mac or windows for bootcamp

#Mac or windows for bootcamp drivers
#Mac or windows for bootcamp update
#Mac or windows for bootcamp driver
#Mac or windows for bootcamp windows 10
#Mac or windows for bootcamp windows 7

#Mac or windows for bootcamp update

now that Win7 is activated, I could update (via the assistive tip) to Win10 Pro (this time, Activated).

gpu-switch doesn’t at all work under Win7 – even after installing VC2013 x86 + 64, it complains about a missing entry point in the system KERNE元2.DLL.

#Mac or windows for bootcamp driver

Also after auto-installing the driver it deemed the right. Enabling it, of course, results in a black-screen boot. the iGPU (when spoofed, obviously) is listed with the same „ the device isn’t using any resources because it has a problem” problem.That is, the only case it boots in when I restart from MacOS without previously executing automate-eGPU.sh that is, when the eGPU is completely hidden by design. with the eGPU connected to the MBP, when booting after executing the script (without -a) or NOT from MacOS, freezes right on the boot loader selector screen, be it either rEFInd or the standard, stock (Alt) one.I’ve removed Win10 + Bootcamp and installed a brand new copy of Windows 7. That is, it behaved in exactly the same way as with a connected monitor.

#Mac or windows for bootcamp windows 7

(I can reinstall & update it from Windows 7 so that it’s activated – I have legal licenses for Win7 but not directly for Win10.)īy the way, as some people reported success on booting into Windows with a, from the (connected) eGPU disconnected monitor, I re-tested the spoofed Bootcamp with my monitor disconnected.ġ, cold boot (after powering up) right into Windows: boots eGPU is invisible in Device Manager (HD4000 is visible, obviously - as we're spoofed)Ģ, warm reboot from Windows into Windows: freezes right at boot loader selector (rEFInd in this case)ģ, warm reboot from MacOS into Windows, without running automate-eGPU-master: boots eGPU is invisible in Device Manager (HD4000 is visible, obviously - as we're spoofed)Ĥ, warm reboot from MacOS into Windows, with running automate-eGPU-master: freezes right at boot loader selector (rEFInd in this case)

#Mac or windows for bootcamp windows 10

May be the problem caused by Windows 10 not being activated? I installed it about a week ago so it still hasn’t run out of 30 days. With no-admin execution, I get:Įrror message was: Not all privileges or groups referenced are assigned to the caller.

What's the Windows 10 build? Type "ver" in cmd. As you now did, the must be some missing Win10 package. It should say: "Administrator: Command Prompt". Your screenshot shows that you are not running in the administrator mode.

no spoofing, Safe mode, installed HD 4000 driversĪlso note that the Resources tab of the HD4000 shows „ the device isn’t using any resources because it has a problem” in both Safe and normal mode (with spoofing and installed HD 4000 drivers).

#Mac or windows for bootcamp drivers

spoofing, Safe mode, installed HD 4000 drivers.spoofing, normal mode, installed HD 4000 drivers.

no spoofing, normal mode, not installed HD 4000 drivers (that is, the default).

Did you try that in Windows 10 (Boot Camp)?”Įrror messages for both batch files in all these cases: After that, you can run apple_set_os.efi. „In order to activate the iGPU, you must first configure the gmux device to use integrated mode with the gpu-switch. Your MBP10,1 has an older firmware which doesn’t support Windows Boot Camp UEFI installation. No definitive answer here other than a necessary UEFI Windows installation was difficult because, as goalque wrote: Nando4> Below is a concatenated discussion between goalque and Menneisyys on applying apple_set_os.efi to his GT650M 15" Macbook Pro. If I make it work, I understand that I have then to create startup.nsh (in EFI/boot) with all the above refi shell commands that will be be automatically executed at boot time Where boot圆4.efi is the renamed Shell_Full.efi file from /Edk/Other/Maintained/Application/UefiShell/bin/圆4/folderĦ) Plug the USB stick into the USB-C to USB adapter, and connect it to your Mac (TB3 port closest to the esc key)Ĩ) Turn on your Mac and hold the Option key downġ0) Change file system to USB “fs2:” => on my configuration it is fs4:, working fine up to hereġ2) Change file system to Windows partition “fs0:” => I am stuck here, I have no access to the Windows partition, fs0 (apple EFI), fs1 (macintosh HD), fs2 (recovery disk), fs3 (unreadable, windows?), fs4 (usb).ġ3) cd EFI\Boot => BTW, there is no EFI folder on my BOOTCAMP partition Have tried the EFI shell commands you recommended:ģ) Format an USB stick in OS X Disk Utility (Choose Erase, Format: MS-DOS (FAT), Scheme: Master Boot Record)Ĥ) Copy apple_set_os.efi to the root directoryĥ) Create a folder structure in Finder as follows: EFI/Boot/boot圆4.efi