Clover General discussion

[Iwanche]

Could you please, post a screenshot or output of diskutil list command?

 

Also, a boot.log or preboot.log might help.

I can, but for some two hours , as I am currently at work .. Thanks for help..

[Iwanche]

Could you please, post a screenshot or output of diskutil list command?

 

Also, a boot.log or preboot.log might help.

What's wrong is that it didn't create an EFI partition upon formatting your hard drive. Or....you removed it accidentally afterwards. Either way, with no EFI partition, there is nothing to mount, so you can't fix your sound (at least not using Clover patching).

Diskutil list:

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *320.1 GB   disk0

   1:                  Apple_HFS OS X                    55.3 GB    disk0s1

   2:       Microsoft Basic Data WINDOWS                 84.0 GB    disk0s2

   3:                  Apple_HFS                         179.8 GB   disk0s3

 

I don't know how to use boot.log.. :/

Here is Darwindumper..

 

DarwinDumper_2.9.8_Clover_X64_3280_Mav_ivaniana.zip

[arsradu]

 

Diskutil list:

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *320.1 GB   disk0

   1:                  Apple_HFS OS X                    55.3 GB    disk0s1

   2:       Microsoft Basic Data WINDOWS                 84.0 GB    disk0s2

   3:                  Apple_HFS                         179.8 GB   disk0s3

 

I don't know how to use boot.log.. :/

Here is Darwindumper..

 

 

To save preboot.log, you need to press F2 when you see Clover GUI (the one where you select your boot drive).

But I'm not sure where or if you're gonna generate a log, if you don't have an EFI partition...

 

You can try though. The log is (usually) saved in Clover/misc.

[polyzargone]

 

Diskutil list:

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *320.1 GB   disk0

   1:                  Apple_HFS OS X                    55.3 GB    disk0s1

   2:       Microsoft Basic Data WINDOWS                 84.0 GB    disk0s2

   3:                  Apple_HFS                         179.8 GB   disk0s3

 

I don't know how to use boot.log.. :/

Here is Darwindumper..

 

 

 

How did you created those partitions ? With OS X installer, Linux, Windows ?

 

Also, install gdisk and run this in  terminal :

 

 

sudo gdisk /dev/disk0

 

And report back here with copy/paste or screenshot.

[Slice]

Disable USB support question.  So CGP compiled without any switches has USB support?  Would you be willing to share that copy of Clover.  I wanted to test it on my system to see if it helps with a USB panic I am getting on boot.  Thanks

My copy of Clover? You laugh? It is me who made Clover release for sf.net.

 

 

I think I've gotten kext injection to work the way I want it to. With some (very hacky and rushed) edits, Clover now loads kexts from the Other folder first (in OEM if present) and then afterwards, the OS-specific version (e.g. 10.11, also in OEM if present). Again, this is very hacky and probably buggy, check before using it. It seems to work from the (very limited) tests I've done.

 

Fixed Diff:

CHAR16*
-GetExtraKextsDir (
+GetOtherKextsDir ();
+
+CHAR16*
+GetOSVersionKextsDir (
   CHAR8 *OSVersion
   );


 EFI_STATUS
+InjectKextsFromDir (
+  EFI_STATUS Status,
+  CHAR16 *SrcDir
+  );
+
+EFI_STATUS
 LoadKexts (
   IN  LOADER_ENTRY *Entry
   );
diff --git a/rEFIt_UEFI/Platform/Settings.c b/rEFIt_UEFI/Platform/Settings.c
index c95f472..507a3ef 100644
--- a/rEFIt_UEFI/Platform/Settings.c
+++ b/rEFIt_UEFI/Platform/Settings.c
@@ -5486,14 +5486,32 @@ SaveSettings ()
   return EFI_SUCCESS;
 }


+CHAR16
+*GetOtherKextsDir ()
+{
+  CHAR16 *SrcDir         = NULL;
+
+  SrcDir     = PoolPrint (L"%s\\kexts\\Other", OEMPath);
+  if (!FileExists (SelfVolume->RootDir, SrcDir)) {
+    FreePool (SrcDir);
+    SrcDir = PoolPrint (L"\\EFI\\CLOVER\\kexts\\Other");
+    if (!FileExists (SelfVolume->RootDir, SrcDir)) {
+      FreePool (SrcDir);
+      SrcDir = NULL;
+    }
+  }
+
+  return SrcDir;
+}
+
 //dmazar
 CHAR16
-*GetExtraKextsDir (
+*GetOSVersionKextsDir (
   CHAR8 *OSVersion
   )
 {
   CHAR16 *SrcDir         = NULL;
-  CHAR8  FixedVersion[6] = "Other";
+  CHAR8  FixedVersion[6];
   CHAR8  *DotPtr;


   if (OSVersion != NULL) {
@@ -5516,25 +5534,10 @@ CHAR16
   SrcDir     = PoolPrint (L"%s\\kexts\\%a", OEMPath, FixedVersion);
   if (!FileExists (SelfVolume->RootDir, SrcDir)) {
     FreePool (SrcDir);
-    SrcDir   = PoolPrint (L"%s\\kexts\\Other", OEMPath);
-
-    if (!FileExists (SelfVolume->RootDir, SrcDir)) {
-      FreePool (SrcDir);
-      SrcDir = NULL;
-    }
-  }
-
-  if (SrcDir == NULL) {
-    // if not found, check EFI\CLOVER\kexts\...
     SrcDir = PoolPrint (L"\\EFI\\CLOVER\\kexts\\%a", FixedVersion);
     if (!FileExists (SelfVolume->RootDir, SrcDir)) {
       FreePool (SrcDir);
- //     SrcDir = PoolPrint (L"\\EFI\\CLOVER\\kexts\\Other", gSettings.OEMProduct);
-      SrcDir   = PoolPrint (L"\\EFI\\CLOVER\\kexts\\Other");
-      if (!FileExists (SelfVolume->RootDir, SrcDir)) {
-        FreePool (SrcDir);
-        SrcDir = NULL;
-      }
+      SrcDir = NULL;
     }
   }
   
@@ -5542,6 +5545,24 @@ CHAR16
 }


 EFI_STATUS
+InjectKextsFromDir (
+  EFI_STATUS Status,
+  CHAR16 *SrcDir
+  )
+{
+  if (SrcDir != NULL) {
+    MsgLog ("Injecting kexts from %s\n", SrcDir);
+  }
+
+  if (EFI_ERROR (Status)) {
+    MsgLog (" - ERROR: Kext injection failed!\n");
+    return EFI_NOT_STARTED;
+  }
+
+  return Status;
+}
+
+EFI_STATUS
 SetFSInjection (
   IN LOADER_ENTRY *Entry
   )
@@ -5555,7 +5576,7 @@ SetFSInjection (
   FSI_STRING_LIST      *Blacklist      = 0;
   FSI_STRING_LIST      *ForceLoadKexts;


-  MsgLog ("FSInjection: ");
+  MsgLog ("Beginning FSInjection\n");
     
   Volume = Entry->Volume;
     
@@ -5574,18 +5595,18 @@ SetFSInjection (
   Status = gBS->LocateProtocol(&gFSInjectProtocolGuid, NULL, (void **)&FSInject);
   if (EFI_ERROR (Status)) {
     //Print (L"- No FSINJECTION_PROTOCOL, Status = %r\n", Status);
-    MsgLog ("not started - gFSInjectProtocolGuid not found\n");
+    MsgLog (" - ERROR: gFSInjectProtocolGuid not found!\n");
     return EFI_NOT_STARTED;
   }


   // check if blocking of caches is needed
   if (OSFLAG_ISSET(Entry->Flags, OSFLAG_NOCACHES)) {
-    MsgLog ("blocking caches");
+    MsgLog ("Blocking kext caches\n");
 //  BlockCaches = TRUE;
     // add caches to blacklist
     Blacklist = FSInject->CreateStringList ();
     if (Blacklist == NULL) {
-      MsgLog (": Error not enough memory!\n");
+      MsgLog (" - ERROR: Not enough memory!\n");
       return EFI_NOT_STARTED;
     }


@@ -5599,55 +5620,45 @@ SetFSInjection (
     if (gSettings.BlockKexts[0] != L'\0') {
       FSInject->AddStringToList(Blacklist, PoolPrint (L"\\System\\Library\\Extensions\\%s", gSettings.BlockKexts));
     }
-
-    MsgLog (", ");
   }
     
   // check if kext injection is needed
   // (will be done only if caches are blocked or if boot.efi refuses to load kernelcache)
   SrcDir = NULL;
   if (OSFLAG_ISSET(Entry->Flags, OSFLAG_WITHKEXTS)) {
-    SrcDir = GetExtraKextsDir(Entry->OSVersion);
-    if (SrcDir != NULL) {
-      // we have found it - injection will be done
-      MsgLog ("using kexts path: '%s'", SrcDir);
-//    InjectionNeeded = TRUE;
-    } else {
-      MsgLog ("skipping kext injection (kexts folder not found)");
-    }
-  } else {
-    MsgLog ("skipping kext injection (not requested)");
-  }
-    
-  // prepare list of kext that will be forced to load
-  ForceLoadKexts = FSInject->CreateStringList ();
-  if (ForceLoadKexts == NULL) {
-    MsgLog (" - Error: not enough memory!\n");
-    return EFI_NOT_STARTED;
-  }
-
-  KextPatcherRegisterKexts (FSInject, ForceLoadKexts, Entry);
+    Status = FSInject->Install (
+                       Volume->DeviceHandle,
+                       L"\\System\\Library\\Extensions",
+                       SelfVolume->DeviceHandle,
+                       GetOtherKextsDir (),
+                       Blacklist,
+                       ForceLoadKexts
+                       );
+    InjectKextsFromDir(Status, GetOtherKextsDir());


-  Status = FSInject->Install (
+    Status = FSInject->Install (
                        Volume->DeviceHandle,
                        L"\\System\\Library\\Extensions",
                        SelfVolume->DeviceHandle,
-                       SrcDir,
+                       GetOSVersionKextsDir (Entry->OSVersion),
                        Blacklist,
                        ForceLoadKexts
                        );
-    
-  if (SrcDir != NULL) {
-    FreePool (SrcDir);
+    InjectKextsFromDir(Status, GetOSVersionKextsDir(Entry->OSVersion));
+  } else {
+    MsgLog ("skipping kext injection (not requested)\n");
   }
     
-  if (EFI_ERROR (Status)) {
-    MsgLog (" - Error: could not install injection!\n");
+  // prepare list of kext that will be forced to load
+  ForceLoadKexts = FSInject->CreateStringList ();
+  if (ForceLoadKexts == NULL) {
+    MsgLog (" - Error: not enough memory!\n");
     return EFI_NOT_STARTED;
   }
-    
+
+  KextPatcherRegisterKexts (FSInject, ForceLoadKexts, Entry);
+   
   // reinit Volume->RootDir? it seems it's not needed.
     
-  MsgLog ("\n");
   return Status;
 }
diff --git a/rEFIt_UEFI/Platform/kext_inject.c b/rEFIt_UEFI/Platform/kext_inject.c
index 53b71b9..d73e73d 100644
--- a/rEFIt_UEFI/Platform/kext_inject.c
+++ b/rEFIt_UEFI/Platform/kext_inject.c
@@ -303,7 +303,26 @@ EFI_STATUS LoadKexts(IN LOADER_ENTRY *Entry)
    }


   // Volume = Entry->Volume;
- SrcDir = GetExtraKextsDir(Entry->OSVersion);
+ SrcDir = GetOtherKextsDir();
+ if (SrcDir != NULL) {
+ MsgLog("Preparing kexts injection for arch=%s from %s\n", (archCpuType==CPU_TYPE_X86_64)?L"x86_64":(archCpuType==CPU_TYPE_I386)?L"i386":L"", SrcDir);
+ // look through contents of the directory
+ DirIterOpen(SelfVolume->RootDir, SrcDir, &KextIter);
+ while (DirIterNext(&KextIter, 1, L"*.kext", &KextFile)) {
+ if (KextFile->FileName[0] == '.' || StrStr(KextFile->FileName, L".kext") == NULL)
+ continue;   // skip this
+
+ UnicodeSPrint(FileName, 512, L"%s\\%s", SrcDir, KextFile->FileName);
+ MsgLog("  Extra kext: %s\n", FileName);
+ AddKext(Entry, SelfVolume->RootDir, FileName, archCpuType);
+      
+ UnicodeSPrint(PlugIns, 512, L"%s\\%s", FileName, L"Contents\\PlugIns");
+         LoadPlugInKexts(Entry, SelfVolume->RootDir, PlugIns, archCpuType, FALSE);
+ }
+ DirIterClose(&KextIter);
+ }
+
+ SrcDir = GetOSVersionKextsDir(Entry->OSVersion);
  if (SrcDir != NULL) {
  MsgLog("Preparing kexts injection for arch=%s from %s\n", (archCpuType==CPU_TYPE_X86_64)?L"x86_64":(archCpuType==CPU_TYPE_I386)?L"i386":L"", SrcDir);
  // look through contents of the directory

Thank you for the proposition! I need a time to understand what is it. Then I'll commit the modification.

Anyone test this?

[TheRacerMaster]

Thank you for the proposition! I need a time to understand what is it. Then I'll commit the modification.

Anyone test this?

 

Check the post again, there are some more (minor) edits to the patch. I also attached a package if anyone wants to test.

[Iwanche]

How did you created those partitions ? With OS X installer, Linux, Windows ?

 

Also, install gdisk and run this in  terminal :

sudo gdisk /dev/disk0

And report back here with copy/paste or screenshot.

I created with os x installer..

Here is termialn with gdisk:

GPT fdisk (gdisk) version 1.0.0

 

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

  MBR: protective

  BSD: not present

  APM: not present

  GPT: present

 

Found valid GPT with protective MBR; using GPT.

 

Command (? for help): 

[Slice]

I created with os x installer..

Here is termialn with gdisk:

GPT fdisk (gdisk) version 1.0.0

 

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

  MBR: protective

  BSD: not present

  APM: not present

  GPT: present

 

Found valid GPT with protective MBR; using GPT.

 

Command (? for help): 

Then type "?" 

[Iwanche]

Then type "?" 

And than?

b back up GPT data to a file

c change a partition's name

d delete a partition

i show detailed information on a partition

l list known partition types

n add a new partition

o create a new empty GUID partition table (GPT)

p print the partition table

q quit without saving changes

r recovery and transformation options (experts only)

s sort partitions

t change a partition's type code

v verify disk

w write table to disk and exit

x extra functionality (experts only)

? print this menu

[Ramalama]

Slice?

 

I have 2 SSD's, 

 

1st - EFI (200MB) / MacOSX10.11 (117GB) / RecoveryHD (650MB) / DATA (10GB)

2nd - Microsoft Reserved (135MB) / Windows10 (127GB) / Windows Recovery (824MB)

 

okay, let me explain,

On the 1st Partition (EFI 200MB), i have this Folders:

-> WINDOWS - (Windows Bootloader)

-> APPLE - (OS X Bootloader)

-> CLOVER - (Clover v3280)

-> BOOT - (Clover .efi linked files)

 

So you see there, the windows Bootloader and Clover is on the same partition,

but the Windows Partition itself, is on the other SSD...

 

So if you run Startvolume app on OS X, the app see only the Windows Partition, but not the Bootloader files on the EFI partition...

And set/store the UUID of the Windows Partition... not the Bootloader entry...

 

If you reboot, clover can't find anything and can't do anything with the UUID...

 

I don't know why windows install always this way on my Laptop...

 

 

Its possible to link start volume (UUID or anything else) to a Custom Entry via config.plist? or anything like that?

Can you maybe look into that if you can write some code for this?

 

Cheers :-)

[oSxFr33k]

@slice,

 

Sorry for my confusion.  I know your the developer of Clover etc.  I read that you are not using CGP and do the compiling manually or via another method of compiling Clover.  I was interested in the binary installer you had compiled wihtout USB support to troubleshoot some USB panic problems and to see what would happen if I were to use that Clover version.

[Slice]

And than?

b back up GPT data to a file

c change a partition's name

d delete a partition

i show detailed information on a partition

l list known partition types

n add a new partition

o create a new empty GUID partition table (GPT)

p print the partition table

q quit without saving changes

r recovery and transformation options (experts only)

s sort partitions

t change a partition's type code

v verify disk

w write table to disk and exit

x extra functionality (experts only)

? print this menu

Type "p"

 

@Ramalama

I understand nothing.

Startvolume app??? May be you mean Startup Disk.prefPane? Yes, it can't work with Windows. Ask Apple for this issue.

Custom entry by UUID? Yes, it is designed for this. What is the problem?

@slice,

 

Sorry for my confusion.  I know your the developer of Clover etc.  I read that you are not using CGP and do the compiling manually or via another method of compiling Clover.  I was interested in the binary you had compiled wihtout USB support to troubleshoot some USB panic problems and to see what would happen if I were to use that Clover version.

This version is in official release. 

The option named "Clover BiosBlockIO". Yes, I always used DISABLE_USB_SUPPORT for this variant because it means legacy USB used.

[Iwanche]

When i put ''p'', i got this:

Disk /dev/disk0: 625140335 sectors, 298.1 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): BA99156E-78A4-43DD-ACF0-C88FA038F154

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 625140301

Partitions will be aligned on 8-sector boundaries

Total free space is 524884 sectors (256.3 MiB)

 

Number  Start (sector)    End (sector)  Size       Code  Name

   1              40       107936887   51.5 GiB    AF00  OS X

   2       108199032       273635327   78.9 GiB    AF00  OS X 2

   3       273897472       625139711   167.5 GiB   AF00  Razno

[Ramalama]

Type "p"

 

@Ramalama

I understand nothing.

Startvolume app??? May be you mean Startup Disk.prefPane? Yes, it can't work with Windows. Ask Apple for this issue.

Custom entry by UUID? Yes, it is designed for this. What is the problem?

This version is in official release. 

The option named "Clover BiosBlockIO". Yes, I always used DISABLE_USB_SUPPORT for this variant because it means legacy USB used.

 Exactly i mean Startup Disk... (its called start volume in german OS X)

 

What i mean is, Statup Disk write UUID into Nvram for boot device ...

But this UUID Corresponds to Windows Partition, not the Windows Bootloader files, which are on the same partition as Clover...

 

So if clover reads the UUID (Bootdevice) from nvram, clover can't find with the UUID any bootloader... Because the Windows boot files are on the Clover partition, not the windows partition...

 

So i meant anything like if i add a property to Custom Entry, like: "Match" = 1239834-1234234235-234234-2344 (UUID)

 

You get what i mean? So if Clover read NVram and get any uuid from there for boot device, it can match any custom entry...

 

Cheers :-)

[Slice]

When i put ''p'', i got this:

Disk /dev/disk0: 625140335 sectors, 298.1 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): BA99156E-78A4-43DD-ACF0-C88FA038F154

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 625140301

Partitions will be aligned on 8-sector boundaries

Total free space is 524884 sectors (256.3 MiB)

 

Number  Start (sector)    End (sector)  Size       Code  Name

   1              40       107936887   51.5 GiB    AF00  OS X

   2       108199032       273635327   78.9 GiB    AF00  OS X 2

   3       273897472       625139711   167.5 GiB   AF00  Razno

Hey, there is another info here   #8510  

Anyway yes, you have no EFI partition because your drive is wrong formatted. Sorry. Begin from zero.

 

 

 Exactly i mean Startup Disk... (its called start volume in german OS X)

 

What i mean is, Statup Disk write UUID into Nvram for boot device ...

But this UUID Corresponds to Windows Partition, not the Windows Bootloader files, which are on the same partition as Clover...

 

So if clover reads the UUID (Bootdevice) from nvram, clover can't find with the UUID any bootloader... Because the Windows boot files are on the Clover partition, not the windows partition...

 

So i meant anything like if i add a property to Custom Entry, like: "Match" = 1239834-1234234235-234234-2344 (UUID)

 

You get what i mean? So if Clover read NVram and get any uuid from there for boot device, it can match any custom entry...

 

Cheers :-)

 

Not so simple.

Open temrinal and make "sudo -s". Type your root password. Keep the terminal window open it prevents from restart.

Open Startup Disk panel choose Window (as I understand you can do this!). Press "Restart".

It will say that Terminal don't allow to restart so you may cancel it.

then type in terminal "nvram -p".

It will list all variables written into nvram including your choosed Windows partition. Show me the setting..... if it happens....

If you do the same procedure with OSX chosen you will successfully see what is happen.

[Ramalama]

Sry Slice, I've got it,

If i run Startup Disk, select Windows, it write into nvram:

efi-boot-device	<array><dict><key>MemoryType</key><integer size="64">0xb</integer><key>StartingAddress</key><integer size="64">0xffe00000</integer><key>IOEFIDevicePathType</key><string>HardwareMemoryMapped</string><key>EndingAddress</key><integer size="64">0xffefffff</integer></dict><dict><key>IOEFIDevicePathType</key><string>MediaFirmwareVolumeFilePath</string><key>Guid</key><string>2B0585EB-D8B8-49A9-8B8C-E21B01AEF2B7</string></dict><dict><key>IOEFIBootOption</key><string>HD</string></dict></array>

1. 2B0585EB-D8B8-49A9-8B8C-E21B01AEF2B7  (I don't have any volumes with this UUID, Or what means GUID???)

2. So Clover can't do anything with this entry...

 

 

 

 

 

If i start Startup Dist, select OS X, or come from a clean reboot:

efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>DA30A57C-75B3-45A1-85BF-C377F43CF205</string></dict></dict><key>BLLastBSDName</key><string>disk0s2</string></dict></array>

1. DA30A57C-75B3-45A1-85BF-C377F43CF205 (UUID from OS X Partition) everything boots perfect...

 

 

 

 

So seems like the problem is deeper as i thinked...

 

Cheers :-)

Hey, there is another info here   #8510  

Anyway yes, you have no EFI partition because your drive is wrong formatted. Sorry. Begin from zero.

 

 

 

Not so simple.

Open temrinal and make "sudo -s". Type your root password. Keep the terminal window open it prevents from restart.

Open Startup Disk panel choose Window (as I understand you can do this!). Press "Restart".

It will say that Terminal don't allow to restart so you may cancel it.

then type in terminal "nvram -p".

It will list all variables written into nvram including your choosed Windows partition. Show me the setting..... if it happens....

If you do the same procedure with OSX chosen you will successfully see what is happen.

Ive got the same idea above :-) Lol

[Iwanche]

What should I do? I deleted the partition, and when i go to reinstall, i can't create a new partition, in fact, a new partitions. I got error: file system resize support required such as hfs+ with journaling enabled.

Do I have to delete the entire HDD, and create a guid partition? If I have to, where to do,from windows installation or os x installation?

Can you explain to me, what should I do and how? Thanks a lot.

[arsradu]

What should I do? I deleted the partition, and when i go to reinstall, i can't create a new partition, in fact, a new partitions. I got error: file system resize support required such as hfs+ with journaling enabled.

Do I have to delete the entire HDD, and create a guid partition? If I have to, where to do,from windows installation or os x installation?

Can you explain to me, what should I do and how? Thanks a lot.

 

Although recreating the EFI partition is not impossible, it's risky. So I would recommend formatting the drive. If you don't do it right, you might end up having to do it anyway.

 

So, you have to remember two main things:

 

1. HDD/SSD formatted as GUID.

 

You can boot from your USB drive, go to Disk Utility, select the HDD on the left (not the partition), go to Erase, give it a Name (anything you want), a Format (Mac OS Extended (journaled) ) and a Scheme (GUID Partition Map).

Yes, this will erase the entire HDD/SSD. So make a backup of your important files on another drive, if you want to save anything.

 

2. Partitions formatted as Mac OS Extended (journaled). This is the default format anyway. So you don't have to worry about it. Just keep in mind for the future.

[Iwanche]

Although recreating the EFI partition is not impossible, it's risky. So I would recommend formatting the drive. If you don't do it right, you might end up having to do it anyway.

 

So, you have to remember two main things:

 

1. HDD/SSD formatted as GUID.

 

You can boot from your USB drive, go to Disk Utility, select the HDD on the left (not the partition), go to Erase, give it a Name (anything you want), a Format (Mac OS Extended (journaled) ) and a Scheme (GUID Partition Map).

Yes, this will erase the entire HDD/SSD. So make a backup of your important files on another drive, if you want to save anything.

 

2. Partitions formatted as Mac OS Extended (journaled). This is the default format anyway. So you don't have to worry about it. Just keep in mind for the future.

Okay, thank you very much. I just forgot to mention that I want to have the windows and os x.

The procedure remains the same?

[arsradu]

Okay, thank you very much. I just forgot to mention that I want to have the windows and os x.

The procedure remains the same?

 

The procedure describes how to format your HDD in order to automatically create that EFI partition that you need. It does not describe what you put on it after that.

 

I would strongly suggest you to use different HDDs for Windows and Mac OS X. Although installing them side by side, on the same HDD, might not be impossible, especially for new users, it might be best if you were using two separate HDD for this.

 

Also, I'm not sure Windows 7 can run off a GPT formatted drive... Never tried it before. I think Windows 8 can (and probably newer versions too). But I'm not sure about older versions. Sorry, can't help you there.

[Iwanche]

The procedure describes how to format your HDD in order to automatically create that EFI partition that you need. It does not describe what you put on it after that.

 

I would strongly suggest you to use different HDDs for Windows and Mac OS X. Although installing them side by side, on the same HDD, might not be impossible, especially for new users, it might be best if you were using two separate HDD for this.

 

Also, I'm not sure Windows 7 can run off a GPT formatted drive... Never tried it before. I think Windows 8 can (and probably newer versions too). But I'm not sure about older versions. Sorry, can't help you there.

Okay, thank you anyway. I've already had on the same HDD, windows and os x. 

But never mind, it is my means to format Mac OS Extended (journaled) ) and a Scheme (GUID Partition Map).

[arsradu]

Okay, thank you anyway. I've already had on the same HDD, windows and os x. 

But never mind, it is my means to format Mac OS Extended (journaled) ) and a Scheme (GUID Partition Map).

 

Yes, you did have them both on the same HDD. But you also had a missing EFI partition. That was the starting point of this whole thing. And the main reason why you're  formatting your drive for GUID now, right?

 

Anyway, if you know how to do it, if you know it will work, then by all means, try it. And if you have a bit of time, come back and tell us if it worked.

 

Good luck!

But never mind, it is my means to format Mac OS Extended (journaled) ) and a Scheme (GUID Partition Map).

 

Yes.

[Iwanche]

Yes, you did have them both on the same HDD. But you also had a missing EFI partition. That was the starting point of this whole thing. And the main reason why you're  formatting your drive for GUID now, right?

 

Anyway, if you know how to do it, if you know it will work, then by all means, try it. And if you have a bit of time, come back and tell us if it worked.

 

Good luck!

 

Yes.

Nooo, i didn't have missing EFI partition earlier. 

When i re-installed os x, and when I did the install, I dropped windows system, and that was a mistake, since then I have no EFI partition, only the EFI folder.

[arsradu]

Nooo, i didn't have missing EFI partition earlier.

When i re-installed os x, and when I did the install, I dropped windows system, and that was a mistake, since then I have no EFI partition, only the EFI folder.

Ok, then why do you want to install Windows again if that caused you this issue in the first place?

By the way, you know that Macs can run OSX and Windows by default, right?

[Iwanche]

Ok, then why do you want to install Windows again if that caused you this issue in the first place?

By the way, you know that Macs can run OSX and Windows by default, right?

You're right, I will not install windows, but will over Macs to run windows.

Will I be able to install the El Capitan? Try to have to install it, come to a white screen and colorful cursor.