Jump to content
ErmaC

Clover General discussion

20,637 posts in this topic

Recommended Posts

Advertisement

Hi. I think there's a typo in kext_inject.c:

UINT8   KBESieDebugSearchEXT[]   = { 0xE8, 0x47, 0x00, 0x00, 0x00, 0xE9, 0x09, 0x00, 0x00, 0x00, 0x48, 0x8B, 0x7D, 0xE8, 0xE8, 0xD9 };
UINT8   KBESieDebugReplaceEXT[]  = { 0xE8, 0x47, 0x00, 0x00, 0x00, 0x90, 0x90, 0x00, 0x00, 0x00, 0x48, 0x8B, 0x7D, 0xE8, 0xE8, 0xD9 };

Note that now we don't NOP out the jmpq fully. (E9 09 00 00 00 -> 90 90 00 00 00 , should be 5x NOP actually.)

 

And fixed here... (Also with a minor variable renaming, don't care about that. ;))

 

new_kext_inject.c.zip

Share this post


Link to post
Share on other sites

You all are going to think I'm nuts, but it would be wonderful if when the system boots to the Clover main load screen (the one that lists your drives and systems with icons), it would be great if there was a way to have some kind of screen saver turn on after some minutes.

 

I don't suppose there's any way to do that, but it would be a nice to have feature!

Share this post


Link to post
Share on other sites

You all are going to think I'm nuts, but it would be wonderful if when the system boots to the Clover main load screen (the one that lists your drives and systems with icons), it would be great if there was a way to have some kind of screen saver turn on after some minutes.

 

I don't suppose there's any way to do that, but it would be a nice to have feature!

Just out of curiosity, why in the world would one need such a "nice to have feature", if you don't mind me asking?

Share this post


Link to post
Share on other sites

Prevent monitor burnout, just in case you forget, and don't auto-load the OS, or prefer not to auto-load the OS.   If you load Windows and Mac and even a Linux distro (like we do at work) that screen is a nice stopping point, but if you forget, and leave the computer on that screen, you'll suffer screen burn-out.  A simple screen-off (or have the screen just go black) would be plenty.   Some systems we use we prefer to leave on to save time loading the system.

Share this post


Link to post
Share on other sites

Prevent monitor burnout, just in case you forget, and don't auto-load the OS, or prefer not to auto-load the OS.   If you load Windows and Mac and even a Linux distro (like we do at work) that screen is a nice stopping point, but if you forget, and leave the computer on that screen, you'll suffer screen burn-out.  A simple screen-off (or have the screen just go black) would be plenty.   Some systems we use we prefer to leave on to save time loading the system.

On what kind of system are you using Clover and forget such long time to burnout a monitor?

 

Edit: More elegant solution would be, as original macOS boot loader does (at least when FileVault 2 is active) shutdown the computer after x second timeout.

Share this post


Link to post
Share on other sites

Error of new compilation of clover4034 and above.

 

Clover 4033 is compiled successfully. And if after that I update the clover, 

then everything also ends successfully. But there is a problem when 
I perform a new compilation (not an update) of the clover 4034 and above.
 
iMac-Droplets-2:Clover droplets$ svn up -r 4034
Updating '.':
U    Clover.dsc
U    Patches_for_EDK2/Conf/tools_def.txt
U    buildExtras.sh
U    build_gcc6.sh
U    buildnasm.sh
U    ebuild.sh
Updated to revision 4034.

 

 

Generating BootSectors
[NASM] boot0af.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot0af
[NASM] boot0ss.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot0ss
[NASM] boot0md.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot0md
[NASM] boot1h.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1h
[NASM] boot1h2.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1h2
[NASM] boot1f32.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1f32
[NASM] boot1f32alt.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1f32alt
[NASM] boot1x.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1x
boot1x.s:188: error: short jump is out of range
boot1x.s:193: error: short jump is out of range
boot1x.s:204: error: short jump is out of range
boot1x.s:233: error: short jump is out of range
make: *** [/Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1x] Error 1

 

 

But if I do not update ebuild.sh then the compilation is successful.

Share this post


Link to post
Share on other sites

Zenith432, thank you!

Clover4038 compiles without problems.

iMac-Droplets-2:Clover droplets$ svn up
Updating '.':
U    Patches_for_EDK2/MdePkg/Include/IndustryStandard/Pci22.h
U    buildExtras.sh
C    ebuild.sh
.....
Restored 'CloverPackage/CloverV2/BootSectors'
Restored 'CloverPackage/CloverV2/BootSectors/lzma'
Restored 'CloverPackage/CloverV2/BootSectors/BootSectImage.exe'
Restored 'CloverPackage/CloverV2/BootSectors/usbs32.bin'
Restored 'CloverPackage/CloverV2/BootSectors/cdboot'
Restored 'CloverPackage/CloverV2/BootSectors/makeusb.bat'
Restored 'CloverPackage/CloverV2/BootSectors/GenBootSector.exe'
Updated to revision 4038.

 

 

iMac-Droplets-2:Clover droplets$ ./ebuild.sh -fr
TOOLCHAIN_DIR: /Users/droplets/src/edk2/Clover/../../opt/local
NASM_PREFIX: /Users/droplets/src/edk2/Clover/../../opt/local/bin/
NASM_VER: 2.12.02
Initializing workspace
Loading previous configuration from /Users/droplets/src/edk2/Conf/BuildEnv.sh
WORKSPACE: /Users/droplets/src/edk2
EDK_TOOLS_PATH: /Users/droplets/src/edk2/BaseTools
CONF_PATH: /Users/droplets/src/edk2/Conf

Running edk2 build for CloverX64 using the command:
build  -D USE_LOW_EBDA -p Clover/Clover.dsc  -a X64 -b RELEASE -t XCODE5 -n 9 

Build environment: Darwin-16.5.0-x86_64-i386-64bit
Build start time: 17:46:25, Mar.14 2017

WORKSPACE        = /Users/droplets/src/edk2
ECP_SOURCE       = /Users/droplets/src/edk2/EdkCompatibilityPkg
EDK_SOURCE       = /Users/droplets/src/edk2/EdkCompatibilityPkg
EFI_SOURCE       = /Users/droplets/src/edk2/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /Users/droplets/src/edk2/BaseTools
CONF_PATH        = /Users/droplets/src/edk2/Conf


Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE5

Active Platform          = /Users/droplets/src/edk2/Clover/Clover.dsc
Flash Image Definition   = /Users/droplets/src/edk2/Clover/Clover.fdf

Processing meta-data ....... done!
Building ... /Users/droplets/src/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64]
Building ... /Users/droplets/src/edk2/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [X64]
Building ... /Users/droplets/src/edk2/MdePkg/Library/BaseMemoryLib/BaseMemoryLib.inf [X64]
Building ... /Users/droplets/src/edk2/MdePkg/Library/BaseLib/BaseLib.inf [X64]
[CC] PcdLib
[SLINK] BasePcdLibNull
Building ... /Users/droplets/src/edk2/MdePkg/Library/BasePrintLib/BasePrintLib.inf [X64]
[CC] DebugLib

............
............
  -> Fat-64.efi
Copy Applications:
  -> bdmesg.efi
Done!

Generating BootSectors
[NASM] boot0af.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot0af
[NASM] boot0ss.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot0ss
[NASM] boot0md.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot0md
[NASM] boot1h.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1h
[NASM] boot1h2.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1h2
[NASM] boot1f32.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1f32
[NASM] boot1f32alt.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1f32alt
[NASM] boot1x.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1x
[NASM] boot1xalt.s -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1xalt
Description.txt -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/Description.txt
Installation.txt -> /Users/droplets/src/edk2/Clover/CloverPackage/CloverV2/BootSectors/Installation.txt
Done!

 

 

Share this post


Link to post
Share on other sites

EDIT

This could be SF website problems. Thanks to @philip_petev !

 

Hi. Could someone tell me what's wrong... I could just get nothing in SF.net, when I went to https://sourceforge.net/p/cloverefiboot/code/HEAD and it showed nothing like this.

 

post-1579222-0-15220600-1489496682_thumb.png

 

Have I done anything wrong? But run this in Terminal, everything seemed fine.

Vanillas-MacBook:~ vanilla$ svn info svn://svn.code.sf.net/p/cloverefiboot/code
Path: code
URL: svn://svn.code.sf.net/p/cloverefiboot/code
Relative URL: ^/
Repository Root: svn://svn.code.sf.net/p/cloverefiboot/code
Repository UUID: 52d7a1c0-eba5-4e63-a9d7-e3186cd7c462
Revision: 4038
Node Kind: directory
Last Changed Author: zenith432
Last Changed Rev: 4038
Last Changed Date: 2017-03-14 18:57:46 +0800 (Tue, 14 Mar 2017)

Vanillas-MacBook:~ vanilla$ 

Edited by PMheart

Share this post


Link to post
Share on other sites

When I use Clover 3333 install OS X 10.12.3 (16D32),it stuck at progress bar.

When I use Clover 4305 install OS X 10.12.3 (16D32),it works.

what is the difference between Clover 3333 and Clover 4305 make this happen?

Thank you.

Share this post


Link to post
Share on other sites

When I use Clover 3333 install OS X 10.12.3 (16D32),it stuck at progress bar.

When I use Clover 4305 install OS X 10.12.3 (16D32),it works.

what is the difference between Clover 3333 and Clover 4305 make this happen?

Thank you.

A whole 972 commits of fixes...

Share this post


Link to post
Share on other sites

A whole 972 commits of fixes...

I am asking Slice for explain how his C source code,logic gate,binary change my life,I do not need arabic numerals that misleading Slice C source code.

Share this post


Link to post
Share on other sites

please help us, we are trying to get clover to work on ryzen cpus for some kernel testing using the kernel that worked for other amd sse 4.1 and sse4.2 capable cpus, we are also working with some kernel developers, but we first need to get the boot loader to work, so i ask clover developers to help up us. the erro we are getting now is displayed on that screen, it seems to be a memory allocation error or something related to cpu clock (the same screen may also appear with unstable overlcloks, also consider that the ryzen clock system is very different from the old am3 cpus)

 

if you have problem with the image here is the url:

https://dl.dropboxusercontent.com/s/76t448hafn27shj/post-598519-0-79895300-1489399096.jpg

 

post-598519-0-79895300-1489399096.jpg

Share this post


Link to post
Share on other sites

I am asking Slice for explain how his C source code,logic gate,binary change my life,I do not need arabic numerals that misleading Slice C source code.

Well I don't know any numbering system in another language, especially in mandarin.

Anyway, if you happen to spend 2 seconds for searching, you would have find the expanation you are looking for

Share this post


Link to post
Share on other sites

Hi, I've corrected the mistakes in kernel_patcher.c.  :) The old discussion can be found at here.

 

Please check the attachment.

 

attachicon.gifnew_kernelPm_kernel_patcher.c.zip

I may accept this if someone else confirmed it working.

please help us, we are trying to get clover to work on ryzen cpus for some kernel testing using the kernel that worked for other amd sse 4.1 and sse4.2 capable cpus, we are also working with some kernel developers, but we first need to get the boot loader to work, so i ask clover developers to help up us. the erro we are getting now is displayed on that screen, it seems to be a memory allocation error or something related to cpu clock (the same screen may also appear with unstable overlcloks, also consider that the ryzen clock system is very different from the old am3 cpus)

 

if you have problem with the image here is the url:

https://dl.dropboxusercontent.com/s/76t448hafn27shj/post-598519-0-79895300-1489399096.jpg

 

 

It's a pity I have no test machine to known what is the problem. Some user/coder/hacker with such cpu should inform me what to change in Clover.

Hi. I think there's a typo in kext_inject.c:

UINT8   KBESieDebugSearchEXT[]   = { 0xE8, 0x47, 0x00, 0x00, 0x00, 0xE9, 0x09, 0x00, 0x00, 0x00, 0x48, 0x8B, 0x7D, 0xE8, 0xE8, 0xD9 };
UINT8   KBESieDebugReplaceEXT[]  = { 0xE8, 0x47, 0x00, 0x00, 0x00, 0x90, 0x90, 0x00, 0x00, 0x00, 0x48, 0x8B, 0x7D, 0xE8, 0xE8, 0xD9 };

Note that now we don't NOP out the jmpq fully. (E9 09 00 00 00 -> 90 90 00 00 00 , should be 5x NOP actually.)

 

And fixed here... (Also with a minor variable renaming, don't care about that. ;))

 

attachicon.gifnew_kext_inject.c.zip

Thanks, accepted.

@Slice

i made new v3 pkg file. completed all

Thanks, accepted!

Is there anyway to get the log from the part of Clover that does the kext patching? This is the stuff that occurs after the clover boot log and before the kernel boot log.

 

Or is there a way to redirect the console output to the serial port instead of the screen? If the console output could be redirected, then couldn't it be redirected to a memory buffer, maybe the same buffer that holds the boot log or a new buffer for this log? It may be necessary to allocate extra space for this log before writing log information there if it is not possible to make a growing buffer.

Yes, possible. Post#50 Non-Standard Legacy Boot Files

The command to build is

./ebuild.sh -D DEBUG_ON_SERIAL_PORT

I think it works also for UEFI but not sure.

Share this post


Link to post
Share on other sites

referring to new_kernelPm_kernel_patcher.c.zip

I may accept this if someone else confirmed it working.

It does not work on my system.

Darwin 16.4

i5-7600

Z270 chipset

MSR 0xE2 locked in bios so need KernelPM patch.

Current KernelPM patch by RehabMan works.

With new patch I get KP.

Attached is image of KP. Sorry for botched focus.

Had to restore working Clover from Windows.

post-446538-0-42656900-1489779940_thumb.jpg

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By cvad
      View File Bootdisk Utility
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
    • By e97
      HackPro X99 System
      Until Apple blesses us with the MacPro7,1 – this is for those that require tools to do their work.
      An appropriate bicycle for the mind.
       
       

       

       

       
      Specs:
       
      CPU: Intel Xeon E5-2678 v3 (12 core, 2.5 GHz / 3.3 GHz Boost)
      Motherboard: SZMZ X99-8D3
      RAM: 16GB DDR3-14900R 1866Mhz ECC RDIMM modules
      GPU: Radeon RX Vega 64 8GB
      Storage: Phison E12 m.2 NVMe PCI-E 3.0 x4 SSD
      Water blocks: BARROW CPU + GPU
      Radiator: 360mm x 25mm slim
      Pump: DDC
       
      Case dimensions: 431 mm x 342 mm x 177 mm
       
       
       
      XCPM OFF
       

       
      XCPM ON
       

       
      OpenCL
       

       
       
       
      iMacPro1,1
       

       
       

       
      OpenCL
       

       
       
      NVMe
       

       
       
      Win 10 x64 v1809
       
      AIDA64 - Cache & Memory
       

       
       
      Download:  https://github.com/xe97/X99-8D3-Clover
       
       
       
       
       
      Anyone else I forgot
       
       
    • By digivish
      Hi All - quick thing - I have a NUC 8i7BEH with 32GB RAM and 2 x 1TB SSD drives. Each drive has its own OS - Windows 10 and Catalina 10.15.
       
      Clover works well - Catalina Boots, so does Windows.
      Catalina - has sound over HDMI (to my monitor's speakers)
      Windows - no audio device found - It does show Realtek and Intel Display Drivers - but the speaker has a red"x" and in Devices, there is no entry for Microphone Array under Audio Input/Output. It does, however, show Intel display over the HDMI - but actually no sound.
       
      I have tried reinstalling Realtek drivers - now here's the thing...when it installs, it first uninstalls existing Realtek drivers - at this stage (and it's important) the sound starts working - as if uninstalling did the trick. As part of the installing, I have to reboot and upon reboot, it actually reinstalls the Realtek drivers. After that, I'm back to square 1. Unsure if it's the config.plist or boot args in clover. But something with Clover for sure.
       
      I have tested this by removing the Mac Drive with clover and just booting directly to Windows 10 bootloader and everything works as it should, I have sound over HDMI and the audio device shows. Just not when I boot with Clover.
       
      has anyone experienced this and have thoughts or pointers.
       
      Thanks a ton!
    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://olarila.com/forum/viewtopic.php?f=28&t=10578
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
×