달력

5

« 2025/5 »

  • 1
  • 2
  • 3
2009. 12. 8. 08:01

Setup Geforce 8xxx-9xxx GT Hackintosh/Graphic Card2009. 12. 8. 08:01

You can get your 8600GT including 8XXX-9XXX series video card working using one of following methods in Snow Leopard.
➊ - Patch DSDT with the video
➋ - Add device (EFI) string to com.apple.Boot.plist
➌ - Chameleon's current auto injection of video / network works if your hardware is identified on PCIroot0 (you can check this in IORegistryExplorer). If your hardware is on PCIroot1 then you might have to use Netkas' PC EFI v10.n. Add GraphicsEnabler=Yes to your com.apple.Boot.plist for Chameleon 2.0-rc3 to inject the device properties.

➍.- After upgarding to 10.6.2, it sometimes did not work EFI String.

- remove nVidia kexts then install 10.6.1 nVidia kexts.

- or remove EFI String in com.apple.Boot.plist and Add GraphicsEnabler=Yes to your com.apple.Boot.plist then add your device-id in Geforce.kext, NVD*

- 10.6.1 NVDAResman.kext (6.0.6) and NVDANV50Hal.kext (6.0.6) in here. installing them in the /Extra/Extensions folder, with a properly configured boot cache will solve the issue. There is no need to install the kexts in /System/Library/Extensions, as the /Extra/Extensions folder will work.

- several 9800 Gt 1024 MB or 512 MB works just fine in 10.6.2 with ATY_init.kext enabler.


* Leopard 10.5.6 이상인 경우에는 위 과정 생략하고 아래과정부터 진행하세요.

 

Following is one of them for EFI string to com.apple.Boot.plist


1. Start OSx86 Tools then click Add EFI Strings/Boot Flag

2. Click GFX String


3. Click Choose.

4. Select your Graphic Card




GFX-String

5.


6.



7.


8. Copy and Paste com.boot.Apple.plist file from /Darwin to /Library/Preferences/SystemConfiguration/


, , , , , , , , , , , , ,

'Hackintosh > Graphic Card' 카테고리의 다른 글

A Simple Guide of the 4830/4850/4870/4870x2/4890, Working QE/CI, Resolution Change, etc.  (0) 2009.12.23
Beta Universal 46xx install package  (0) 2009.12.17
GTS 250,260,280 그래픽 카드 잡기 - 이제는 발로 설치한다. 10분만에  (0) 2009.11.18
9800 GT 설정하기  (0) 2009.07.13
EmTek Radeon HD 4870 XENON Live II Extreme D5 1GB TWIN Cool  (0) 2009.07.10
:
Posted by Ritz®™
2009. 12. 6. 19:24

Code injection via DSDT for NVIDIA graphics Hackintosh/DSDT2009. 12. 6. 19:24

Created by Team EvOSX86
In this third guide, board and add to our DSDT code, graphics injection that will enable us to stop using Efi strings or injectors
Nvidia video card.
* Note: We've had success with this technique for some GMA950, ATI X3100 and some of the series X1xxx but not yet in HD.
Tools needed:
Ioregistry explorer
Nvidia graphics card working 100% including video outputs needed (QE and Hardware CI).
Having previously read chapter one and two of the guide
Content:
1. How to recognize where our video card in the registry and its associated devices.
2. Decompilation file and added COFIG DSDT.aml chart.
2a. The loader code.
3. Comparison of our code with Ioreg added Nvcaps, reg and renamed.
4. Basic structure of video devices and the DSDT added to our code.
4a. Example portable.
4b. Example computer tower.
5. Compiling and testing.
APPENDIX: How to clean our DSDT video inputs nonfunctional
1. How to recognize where our video card and registration devices
partners.
After downloading the program Ioregistry explorer, executive, we walk the tree of entries until we find the reference for our
video card, usually tends to be quite clear:
This example is from a laptop with a 256MB Nvidia 8600GT using the latest patches as Nvinject video and injector.
 Pic1

As you will see, is not marked in green line corresponds to the card, but the upper, and has an explanation: in the DSDT code does not find his name, but with
the device that houses it.
Let me explain a bit these devices:
Marked in red is the AGP device @ 1, which depends on PCI @ 0, this device houses a device called a sub-VID @ 0, which is our video card.
In turn, the device VID @ 0 contains other devices that do not see, such as LCD, VGA, etc.
2. Decompilation of the code and added dsdt.aml chart.
Assuming that prior to this guide you have got to have a fixed DSDT and operational (HPET and RTC patched etc ...) you make a backup file and DSDT.aml
We have to work on.
In previous guides we have spoken of the binary called "iasl" found inside the folder "tools" created by the patcher Fassler. I repeat the recommendation that
copieis this file in / usr / bin with this I will always be available when you open the terminal and not have to be Recordade where we have given, or drag it to the terminal
every time we change our archive dst.dsl
That said, having copied the binary to start with where we mentioned decompilation of DSDT.aml:
Open terminal as root logueamos us and agree to the folder where we alamacenado the DSDT (cd "path to the folder")
once inside type in "-d iasl dsdt.aml"
This will create DSDT.dsl, we make a copy for backup and have it move away from the tools folder to avoid overcrowding of.
Now prodeas DSDT.dsl edit using a text editor of our choice (suggested textmate)
For this example we will use a DSDT from a laptop.
Note: The code marked in red is not used.
   The blue outlines the part that we must adapt to our video card.



CODE

Device (PEGP)  

  {

  Name (_ADR, 0x00010000)

  Device (GFX0)

  {

  Name (_ADR, Zero)

  Name (_SUN, One)

  Method (_DSM, 4, NotSerialized)

  {

  Store (Package (0x1A)

  {

  "@0,compatible",

  Buffer (0x0B)

  {

  "NVDA,NVMac"

  },

  "@0,device_type",

  Buffer (0x08)

  {

  "display"

  },

  "@0,name",

  Buffer (0x0F)

  {

  "NVDA,Display-A"

  },

  "@1,compatible",

  Buffer (0x0B)

  {

  "NVDA,NVMac"

  },

  "@1,device_type",

  Buffer (0x08)

  {

  "display"

  },

  "@1,name",

  Buffer (0x0F)

  {

  "NVDA,Display-B"

  },

  "NVCAP",   <----------------   Nuestro NVCAP para salidas múltiples extraído de IOREG.

  Buffer (0x18)

  {

  /* 0000 */   0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00,

  /* 0008 */   0x06, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

  /* 0010 */   0x00, 0x00, 0x00, 0x00

  },

  "NVPM",   <----------------   Nuestro NVPM (gestión de energía), normalmente no hay que cambiarlo, pero es bueno compararlo en IOREG.

  Buffer (0x20)

  {

  /* 0000 */   0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

  /* 0008 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

  /* 0010 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

  /* 0018 */   0x00, 0x00, 0x00, 0x00

  },

  "VRAM,totalsize",

  Buffer (0x04)

  {

     0x00, 0x00, 0x00, 0x20

  },

   "device_type",

  Buffer (0x0D)

  {

  "NVDA,GeForce"

  },

  "model",

     Buffer (0x1F)   <----------------   Dependerá de la longitud del nombre + los espacios + 1.

     {

  "Nvidia GeForce 8600M GS 256 MB"   <----------------   El nombre de nuestra tarjeta y su memoria (a vuestra elección).

  },

   "rom-revision",

  Buffer (0x20)

     {

  "DSDT ROM v.1a #irc.osx86.es (c)"

  },

  "reg",   <----------------   Nuestro REG extraído de IOREG.

   Buffer (0x78)

   {

  /* 0000 */   0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0008 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0010 */   0x00, 0x00, 0x00, 0x00, 0x10, 0x00, 0x01, 0x02,

/* 0018 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0020 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01,

/* 0028 */   0x14, 0x00, 0x01, 0x42, 0x00, 0x00, 0x00, 0x00,

/* 0030 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0038 */   0x00, 0x00, 0x00, 0x10, 0x1C, 0x00, 0x01, 0x02,

/* 0040 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0048 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02,

/* 0050 */   0x24, 0x00, 0x01, 0x01, 0x00, 0x00, 0x00, 0x00,

/* 0058 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0060 */   0x80, 0x00, 0x00, 0x00, 0x30, 0x00, 0x01, 0x02,

/* 0068 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0070 */   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x00

  }

  }, Local0)

  DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

  Return (Local0)

  }

  }

  }

    

Renowned for our card in the code outsider.
                                                     
If you look at the letters in blue is suggested, you will see that marked the buffer and the name of the card, why?, It is simple, you will have to change the name of the card
for yours, and the buffer indicating the number of characters (including spaces) is in the name quoted 1 if you change the name but not the buffer, the
compilation will fail.
How to find the buffer (which is also in hexadecimal).
It is very simple, we need a converter decimal to hexadecimal and vice versa.
A site that you can come very convenient is this:
http://www.parkenet.com/apl/HexDecConverter.html
or this:
http://www.paulschou.com/tools/xlate/
Well, he began:
Sample buffer for the line "Nvidia GeForce 8600M GS 256MB, the number of letters and spaces contained here is 30 (decimal), add 1 to the result (actually it
The problem is that the account number starts from zero), which gives us 31, using the websites listed above, we put 31 in decimal and as a result gives us 1F
hexadecimal, ie, the buffer used.
If we change the name to our card, we use the same approach to calculate the size of the buffer.

2a. The loader code.

We will give an overview of the concept of loader code already discussed in the previous guide.
Our code is not ACPI is a string of information that add to the ACPI code, and if we as-is, our record's not OSX not being charged this compatible
ACPI, so this is loaded, we must use a "shipper" which is nothing more than a bit of code that define our entry code and allow its load by
system.
Where to insert the "shipper"?
This is simple, you must seek with the text editor area code _WAK called, and when the definition of it, fit the loader code.
Charger Code:


 CODE

Method (DTGP, 5, NotSerialized)

{

If (LEqual (Arg0, Buffer (0x10)

{

/* 0000 */ 0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44,

/* 0008 */ 0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B

}))

{

If (LEqual (Arg1, One))

{

If (LEqual (Arg2, Zero))

{

Store (Buffer (One)

{

0x03

}, Arg4)

Return (One)

}

If (LEqual (Arg2, One))

{

Return (One)

}

}

}

Store (Buffer (One)

{

0x00

}, Arg4)

Return (Zero)

}


Cargo Area:
The code in this area will depend on the machine, and basically you have to find the end _WAK code, which ends:

CODE

Return (Package (0x02)

{

Zero,

Zero

})

}
I include below the code loader.
EXAMPLE:
More cargo area shipper:


CODE

Method (_WAK, 1, NotSerialized)

{

P8XH (One, 0xAB)

If (LOr (LEqual (Arg0, 0x03), LEqual (Arg0, 0x04)))

{

If (And (CFGD, 0x01000000))

{

If (LAnd (And (CFGD, 0xF0), LEqual (OSYS, 0x07D1)))

{

TRAP (0x3D)

}

}

}

If (LEqual (RP2D, Zero))

{

Notify (\_SB.PCI0.RP02, Zero)

}

If (LEqual (Arg0, 0x03)) {}

If (LEqual (Arg0, 0x04))

{

\_SB.PCI0.LPCB.EC0.SELE ()

}

P8XH (Zero, 0xCD)

Return (Package (0x02)

{

Zero,

Zero

})

}

Method (DTGP, 5, NotSerialized)

{

If (LEqual (Arg0, Buffer (0x10)

{

/* 0000 */ 0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44,

/* 0008 */ 0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B

}))

{

If (LEqual (Arg1, One))

{

If (LEqual (Arg2, Zero))

{

Store (Buffer (One)

{

0x03

}, Arg4)

Return (One)

}

If (LEqual (Arg2, One))

{

Return (One)

}

}

}

Store (Buffer (One)

{

0x00

}, Arg4)

Return (Zero)

}


Salváis the file and compile to see if there were errors in the code.
Open the terminal, as root logueamos us and tune into the DSDT folder (cd "path to the folder) then type
iasl-f dsdt.dsl

 If errors occur is that you put the wrong charger, if warnings occur, is that it may come before, not do them much attention now.
If no error occurs, delete the file that was generated DSDT.aml and continued work within DSDT.dsl
3. Comparison of our code with Ioreg added Nvcaps, reg and
renamed.
We now proceed to seek the necessary data on our IOREG for insertion into each unit in the code.
NVCAPS or seek first the configuration of the outputs of our video card and NVPM or energy management.
We opened the IOREG and seek our video card, pointing device and look for the entry child NVCAP and NVPM:

Pic2

Once we have NVCAP values and NVPM, amend our code.
Now look at the value of the input REG:

Pic 3

Change value of REG in the graphical code, so you get the real value is in our system.

4. Basic structure of video devices and the DSDT added
of our code.
4a. Example using a laptop.
Let's open the DSDT.dsl and look through the keyword "device" until we get to:


CODE

Device (AGP)
We will find the device tree in this way (different colors for each device):
In short without our code:


CODE

Device (AGP) (Dispositivo madre)

{

Nombre y dirección.

DEVICE VID0 (Dispositivo hijo)

{

   Nombre y dirección de VID0

Inicio del método

{

   Método

   }

   Device (TV)

Device (CRT)

   Device (LCD)

Device (DVI)

}

}
Briefly our code:


CODE

Device (AGP) (Dispositivo madre)

{

Nombre y dirección.

DEVICE VID0 (Dispositivo hijo)

{

   Nombre y dirección de VID0

Inicio del método

{

   Método

   }

   Device (TV)

Device (CRT)

   Device (LCD)

Device (DVI)

Device (GFX) <-------- Nuestro codigo.

}

}

Extended:



CODE

Device (AGP)

{

Name (_ADR, 0x00010000)

Device (VID)

{

Name (_ADR, Zero)

Method (_DOS, 1, NotSerialized)

{

Store (Arg0, MIS4)

SMI (0x9E, MIS4)

}

Method (_DOD, 0, NotSerialized)

{

Store (SMI (0x6D, Zero), Local0)

If (LEqual (Local0, One))

{

Return (Package (0x04)

{

0x00010100,

0x00010200,

0x00010110,

0x00010210

})

}

Else

{

Return (Package (0x04)

{

0x00010100,

0x00010200,

0x00010118,

0x00010120

})

}

}

Device (TV)

{

Method (_ADR, 0, NotSerialized)

{

Return (0x0200)

}

Method (_DCS, 0, NotSerialized)

{

Store (SMI (0x8E, 0x04), Local0)

Return (Local0)

}

Method (_DGS, 0, NotSerialized)

{

Store (SMI (0x99, 0x04), Local0)

Return (Local0)

}

Method (_DSS, 1, NotSerialized)

{

DSS (0x04, Arg0)

}

}

Device (CRT)

{

Method (_ADR, 0, NotSerialized)

{

Return (0x0100)

}

Method (_DCS, 0, NotSerialized)

{

Store (SMI (0x8E, 0x02), Local0)

Return (Local0)

}

Method (_DGS, 0, NotSerialized)

{

Store (SMI (0x99, 0x02), Local0)

Return (Local0)

}

Method (_DSS, 1, NotSerialized)

{

DSS (0x02, Arg0)

}

}

Device (LCD)

{

Method (_ADR, 0, NotSerialized)

{

Store (SMI (0x6D, Zero), Local0)

If (LEqual (Local0, One))

{

Return (0x0110)

}

Else

{

Return (0x0118)

}

}

Method (_DCS, 0, NotSerialized)

{

Store (SMI (0x8E, One), Local0)

Return (Local0)

}

Method (_DGS, 0, NotSerialized)

{

Store (SMI (0x99, One), Local0)

Return (Local0)

}

Method (_DSS, 1, NotSerialized)

{

DSS (One, Arg0)

}

Name (BTVL, 0x64)

Name (DBCL, Package (0x0A) {})

Method (_BCL, 0, NotSerialized)

{

SX10 ()

SX30 (0x19)

SX30 (Zero)

SX11 ()

Store (SX40 (), Index (DBCL, Zero))

Store (SX40 (), Index (DBCL, One))

Store (SX40 (), Index (DBCL, 0x02))

Store (SX40 (), Index (DBCL, 0x03))

Store (SX40 (), Index (DBCL, 0x04))

Store (SX40 (), Index (DBCL, 0x05))

Store (SX40 (), Index (DBCL, 0x06))

Store (SX40 (), Index (DBCL, 0x07))

Store (SX40 (), Index (DBCL, 0x08))

Store (SX40 (), Index (DBCL, 0x09))

SX12 ()

Return (DBCL)

}

Method (_BCM, 1, NotSerialized)

{

SX10 ()

SX30 (0x19)

SX30 (One)

SX30 (Arg0)

Store (Arg0, BTVL)

SX11 ()

SX12 ()

}

Method (_BQC, 0, NotSerialized)

{

SX10 ()

SX30 (0x19)

SX30 (0x02)

SX11 ()

Store (SX40 (), Local0)

Store (Local0, BTVL)

SX12 ()

Return (Local0)

}

}

Device (DVI)

{

Method (_ADR, 0, NotSerialized)

{

Store (SMI (0x6D, Zero), Local0)

If (LEqual (Local0, One))

{

Return (0x0210)

}

Else

{

Return (0x0120)

}

}

Method (_DCS, 0, NotSerialized)

{

Store (SMI (0x8E, 0x08), Local0)

Return (Local0)

}

Method (_DGS, 0, NotSerialized)

{

Store (SMI (0x99, 0x08), Local0)

Return (Local0)

}

Method (_DSS, 1, NotSerialized)

{

DSS (0x08, Arg0)

}

}

Device (GFX0) <------------- Comienzo de nuestro codigo

{

Name (_ADR, Zero)

Name (_SUN, One)

Method (_DSM, 4, NotSerialized)

{

Store (Package (0x1A)

{

"@0,compatible",

Buffer (0x0B)

{

"NVDA,NVMac"

},

"@0,device_type",

Buffer (0x08)

{

"display"

},

"@0,name",

Buffer (0x0F)

{

"NVDA,Display-A"

},

"@1,compatible",

Buffer (0x0B)

{

"NVDA,NVMac"

},

"@1,device_type",

Buffer (0x08)

{

"display"

},

"@1,name",

Buffer (0x0F)

{

"NVDA,Display-B"

},

"NVCAP",

Buffer (0x18)

{

/* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00,

/* 0008 */ 0x06, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0010 */ 0x00, 0x00, 0x00, 0x00

},

"NVPM",

Buffer (0x20)

{

/* 0000 */ 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0018 */ 0x00, 0x00, 0x00, 0x00

},

"VRAM,totalsize",

   Buffer (0x04)

   {

0x00, 0x00, 0x00, 0x20

},

"device_type",

Buffer (0x0D)

{

"NVDA,GeForce"

},

"model",

Buffer (0x1F)

{

"Nvidia GeForce 8600M GS 256 MB"

},

"rom-revision",

Buffer (0x20)

{

"DSDT ROM v.1a #irc.osx86.es (c)"

},

"reg",

   Buffer (0x78)

{

/* 0000 */ 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00,

   /* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

   /* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, 0x01, 0x02,

   /* 0018 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

   /* 0020 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01,

   /* 0028 */ 0x14, 0x00, 0x01, 0x42, 0x00, 0x00, 0x00, 0x00,

   /* 0030 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

   /* 0038 */ 0x00, 0x00, 0x00, 0x10, 0x1C, 0x00, 0x01, 0x02,

   /* 0040 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

   /* 0048 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02,

   /* 0050 */ 0x24, 0x00, 0x01, 0x01, 0x00, 0x00, 0x00, 0x00,

   /* 0058 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

   /* 0060 */ 0x80, 0x00, 0x00, 0x00, 0x30, 0x00, 0x01, 0x02,

   /* 0068 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

   /* 0070 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x00

}

}, Local0)

DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

Return (Local0)

}

   } <------------- Fin de nuestro codigo (No incluir esta reseña en el DSDT)

}

}
4b. Example using a computer tower.
We will seek to explore our IOregistry video card, and here we notice a difference with the code on the laptop, and is as follows:
In the computer tower, we will find the video devices that we saw in the previous example, LCD, CRT etc., except in cases of integrated graphics, we
ioreg to look at the site of our graph, usually it be under some PCI devices such as PC1, P0P1 etc. .. depends
motherboard manufacturer, but sometimes we do not see the device with a clear demarcation in ioreg and appears as PCI2BRIDGE or in this case PCIBRIDGE
add the entry directly into the ICP as all these devices have the device "mother" to the main PCI ..... In plates with integrated graphics
we can find something closer to the example of the laptop, but we must not fall into errors, the code must be added in the code
for the device that is located not on our card and the integrated video board.
Set in the PCI code.



CODE

Device (PCI0)

{

Name (_HID, EisaId ("PNP0A03"))

Name (_ADR, 0x00)

Name (_UID, 0x01)

Name (_BBN, 0x00)

Method (_S3D, 0, NotSerialized)

{

If (LEqual (OSFL, 0x02))

{

Return (0x02)

}

Else

{

Return (0x03)

}

}

   Method (_STA, 0, NotSerialized)

{

Return (0x0F)

}

Method (_CRS, 0, NotSerialized)

{

Name (BUF0, ResourceTemplate ()

{
The code continues much longer, but we will take this as a reference.
Here we would have our code added to the PCI video:



CODE

Device (PCI0)

{

Name (_HID, EisaId ("PNP0A03"))

Name (_ADR, 0x00)

Name (_UID, 0x01)

Name (_BBN, 0x00)

   Device (PEGP)

{

Name (_ADR, 0x00060000)

Device (GFX0)

{

Name (_ADR, Zero)

Name (_SUN, One)

Method (_DSM, 4, NotSerialized)

{

Store (Package (0x1C)

{

   "AAPL,slot-name",

   Buffer (0x0D)

   {

"PCI-E Slot-1"

}, },

"@0,compatible",

Buffer (0x0B)

{

"NVDA,NVMac"

},

"@0,device_type",

Buffer (0x08)

{

"display"

},

"@0,name",

Buffer (0x0F)

{

"NVDA,Display-A"

},

"@1,compatible",

Buffer (0x0B)

{

"NVDA,NVMac"

},

"@1,device_type",

Buffer (0x08)

{

"display"

},

"@1,name",

Buffer (0x0F)

{

"NVDA,Display-B"

},

"NVCAP",

Buffer (0x18)

{

/* 0000 */ 0x04, 0x00, 0x01, 0x00, 0x00, 0x00, 0x03, 0x00,

/* 0008 */ 0x0C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07,

/* 0010 */ 0x00, 0x00, 0x00, 0x00

},

"NVPM",

Buffer (0x20)

{

/* 0000 */ 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0018 */ 0x00, 0x00, 0x00, 0x00

},

"VRAM,totalsize",

Buffer (0x04)

{

0x00, 0x00, 0x00, 0x20

},

"device_type",

Buffer (0x0D)

{

"NVDA,GeForce"

},

"model",

Buffer (0x22)

{

"POV Nvidia GeForce 8800 GT 512 MB"

},

"rom-revision",

Buffer (0x23)

{

"DSDT ROM v.1a by #irc.osx86.es (c)"

},

"reg",

Buffer (0x78)

{

/* 0000 */ 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, 0x01, 0x02,

/* 0018 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0020 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01,

/* 0028 */ 0x14, 0x00, 0x01, 0x42, 0x00, 0x00, 0x00, 0x00,

/* 0030 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0038 */ 0x00, 0x00, 0x00, 0x10, 0x1C, 0x00, 0x01, 0x02,

/* 0040 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0048 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02,

/* 0050 */ 0x24, 0x00, 0x01, 0x01, 0x00, 0x00, 0x00, 0x00,

/* 0058 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0060 */ 0x80, 0x00, 0x00, 0x00, 0x30, 0x00, 0x01, 0x02,

/* 0068 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0070 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x00

}

}, Local0)

DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

Return (Local0)

}

}

}

Method (_S3D, 0, NotSerialized)

{

If (LEqual (OSFL, 0x02))

{

Return (0x02)

}

Else

{

Return (0x03)

}

}

Method (_STA, 0, NotSerialized)

{

Return (0x0F)

}


5. Compiling and testing.

Now we only save the file and compile it to check for syntax errors or not.
Open the terminal, as root logueamos us and tune into the folder where we have our DSDT (cd "path to folder") Keyboards
iasl dsdt.dsl

 If errors occur is that you put the wrong charger, if warnings occur, is that it may come before, not do them much attention now.
If you have them, make certain that brackets have not been orphaned, or deleted.
If not, you can rename the file you have in DSDT.aml the root of the system to "DSDTold.aml" and copy the new (to open created when compiling) to the root of the disk.
We delete the injector that we are using (Nvkush, Nvinject or NVdarwin) or EFI string if we use this method and proceed to reboot. If our site has
been right and proper coding of our graphics should be fully recognized and activated yet.
If you fail the new DSDT.aml (eg freezes the system), you can boot the system using the command DSDTold.aml DSDT = (introducidlo when you see the boot
chameleon by pressing F8 and selecting the installation of Leopard).
We hope that this third guide on the possibilities of DSDT system has been of your liking.
We will be updating the guidelines as new data have ....

ANNEX
In this annex, see how to optimize a laptop, removing the graphic code is not used by OSX, obtaining with this a greater fluidity in the video
because the register is only the code that is functional, our code added.
In the summary view can better see the tree of devices, so we can determine who should stay and who must not be erased to useful code and
prepare for the inclusion of our code of video.
In summary, our code should look like in after deleting unnecessary devices:
BEFORE:



CODE

Device (AGP)

{

Nombre y dirección.

Cabezera de VID0

{

   Nombre y dirección de VID0

Inicio del método

{

   Método

   }

   Device (TV)

Device (CRT)

   Device (LCD)

Device (DVI)

}

}
LATER:



CODE

Device (AGP)

{

Nombre y dirección.

Cabezera de VID0

{

   Nombre y dirección de VID0

Inicio del método

{

   Método

   }

   }

}

}


Extended BEFORE:



CODE

Device (AGP)

{

Name (_ADR, 0x00010000)

Device (VID)

{

Name (_ADR, Zero)

Method (_DOS, 1, NotSerialized)

{

Store (Arg0, MIS4)

SMI (0x9E, MIS4)

}

Method (_DOD, 0, NotSerialized)

{

Store (SMI (0x6D, Zero), Local0)

If (LEqual (Local0, One))

{

Return (Package (0x04)

{

0x00010100,

0x00010200,

0x00010110,

0x00010210

})

}

Else

{

Return (Package (0x04)

{

0x00010100,

0x00010200,

0x00010118,

0x00010120

})

}

}

Device (TV)

{

Method (_ADR, 0, NotSerialized)

{

Return (0x0200)

}

Method (_DCS, 0, NotSerialized)

{

Store (SMI (0x8E, 0x04), Local0)

Return (Local0)

}

Method (_DGS, 0, NotSerialized)

{

Store (SMI (0x99, 0x04), Local0)

Return (Local0)

}

Method (_DSS, 1, NotSerialized)

{

DSS (0x04, Arg0)

}

}

Device (CRT)

{

Method (_ADR, 0, NotSerialized)

{

Return (0x0100)

}

Method (_DCS, 0, NotSerialized)

{

Store (SMI (0x8E, 0x02), Local0)

Return (Local0)

}

Method (_DGS, 0, NotSerialized)

{

Store (SMI (0x99, 0x02), Local0)

Return (Local0)

}

Method (_DSS, 1, NotSerialized)

{

DSS (0x02, Arg0)

}

}

Device (LCD)

{

Method (_ADR, 0, NotSerialized)

{

Store (SMI (0x6D, Zero), Local0)

If (LEqual (Local0, One))

{

Return (0x0110)

}

Else

{

Return (0x0118)

}

} If (LEqual (Local0, One))


Method (_DCS, 0, NotSerialized)

{

Store (SMI (0x8E, One), Local0)

Return (Local0)

}

Method (_DGS, 0, NotSerialized)

{

Store (SMI (0x99, One), Local0)

Return (Local0)

}

Method (_DSS, 1, NotSerialized)

{

DSS (One, Arg0)

}

Name (BTVL, 0x64)

Name (DBCL, Package (0x0A) {})

Method (_BCL, 0, NotSerialized)

{

SX10 ()

SX30 (0x19)

SX30 (Zero)

SX11 ()

Store (SX40 (), Index (DBCL, Zero))

Store (SX40 (), Index (DBCL, One))

Store (SX40 (), Index (DBCL, 0x02))

Store (SX40 (), Index (DBCL, 0x03))

Store (SX40 (), Index (DBCL, 0x04))

Store (SX40 (), Index (DBCL, 0x05))

Store (SX40 (), Index (DBCL, 0x06))

Store (SX40 (), Index (DBCL, 0x07))

Store (SX40 (), Index (DBCL, 0x08))

Store (SX40 (), Index (DBCL, 0x09))

SX12 ()

Return (DBCL)

}

Method (_BCM, 1, NotSerialized)

{

SX10 ()

SX30 (0x19)

SX30 (One)

SX30 (Arg0)

Store (Arg0, BTVL)

SX11 ()

SX12 ()

}

Method (_BQC, 0, NotSerialized)

{

SX10 ()

SX30 (0x19)

SX30 (0x02)

SX11 ()

Store (SX40 (), Local0)

Store (Local0, BTVL)

SX12 ()

Return (Local0)

}

}

Device (DVI)

{

Method (_ADR, 0, NotSerialized)

{

Store (SMI (0x6D, Zero), Local0)

If (LEqual (Local0, One))

{

Return (0x0210)

}

Else

{

Return (0x0120)

}

}

Method (_DCS, 0, NotSerialized)

{

Store (SMI (0x8E, 0x08), Local0)

Return (Local0)

}

Method (_DGS, 0, NotSerialized)

{

Store (SMI (0x99, 0x08), Local0)

Return (Local0)

}

Method (_DSS, 1, NotSerialized)

{

DSS (0x08, Arg0)

}

}

   }

   }
Extended LATER:



CODE

Device (AGP)

{

Name (_ADR, 0x00010000)

Device (VID)

{

Name (_ADR, Zero)

Method (_DOS, 1, NotSerialized)

{

Store (Arg0, MIS4)

SMI (0x9E, MIS4)

}

Method (_DOD, 0, NotSerialized)

{

Store (SMI (0x6D, Zero), Local0)

If (LEqual (Local0, One))

{

Return (Package (0x04)

{

0x00010100,

0x00010200,

0x00010110,

0x00010210

})

}

Else

{

Return (Package (0x04)

{

0x00010100,

0x00010200,

0x00010118,

0x00010120

})

}

}

   }

}
Obviously, if we are to compile after erasing all those devices, we report a number of errors will disappear as many references as well
that we look for the lines marked as errors and remove them as follows:

CODE

Errores generados al compilar cuando eliminamos el device "LCD":

/Users/xxx/Desktop/pruebas dsdt/Tools/DSDToriginal.dsl 721: Notify (\_SB.PCI0.AGP.VID.LCD, 0x86)

Error 4063 - Object does not exist ^ (\_SB.PCI0.AGP.VID.LCD)

/Users/xxx/Desktop/pruebas dsdt/Tools/DSDToriginal.dsl 726: Notify (\_SB.PCI0.AGP.VID.LCD, 0x87)

Error 4063 - Object does not exist ^ (\_SB.PCI0.AGP.VID.LCD)



We move to the line 721 and 726 as shown and we find:

CODE

If (LGreaterEqual (OSID (), 0x20))

{

If (And (Local0, 0x04))

{

Notify (\_SB.PCI0.AGP.VID.LCD, 0x86)

Notify (\_SB.PCI0.VID.LCD, 0x86)

}

If (And (Local0, 0x02))

{

Notify (\_SB.PCI0.AGP.VID.LCD, 0x87)

Notify (\_SB.PCI0.VID.LCD, 0x87)

}

}



If we remove those two entries, and compile again, the errors are gone.

CODE

If (LGreaterEqual (OSID (), 0x20))

{

If (And (Local0, 0x04))

{

Notify (\_SB.PCI0.VID.LCD, 0x86)

}

If (And (Local0, 0x02))

{

Notify (\_SB.PCI0.VID.LCD, 0x87)

}

}


It is recommended to compile every time you delete an entry, so you can gradually correct our code.
Guide by: Roisoft and Pere
, , , , , , , ,

'Hackintosh > DSDT' 카테고리의 다른 글

DSDT 생성  (4) 2010.06.19
8600 GTS 256 MB DSDT  (0) 2010.02.18
Fix'y DSDT for ASUS P5W DH Deluxe and Snow & Leopard  (0) 2009.11.06
Windows용 DSDT 추출 및 Patcher  (0) 2009.10.30
Enabling ACPI, EIST, etc for ASUS P5W DH DELUXE  (0) 2009.10.25
:
Posted by Ritz®™
2009. 12. 6. 15:12

IPHONE SDK용 시스템 Mobile/iPhone2009. 12. 6. 15:12


IPHONE SDK용 시스템

참고
http://developer.apple.com/technology/xcode.html

P4 시스템, 10.5.7 이상 시스템에서도 쓸만합니다.

f0027855_4b1545d68ce88.jpeg

,

'Mobile > iPhone' 카테고리의 다른 글

iPhone용 무료 어플리케이션을 다운로드 받아보자  (0) 2009.12.10
HTC hero, 아이폰과 옴니아를 인가젯에서 비교한 동영상  (0) 2009.12.07
Control your Mercedes mbrace with an iPhone or RIM Blackberry  (0) 2009.12.05
twittpop Event!! iPhone  (0) 2009.11.28
iPhone 잠실실황 생중계  (0) 2009.11.27
:
Posted by Ritz®™
2009. 12. 6. 14:53

DELL M1210 OS X SETUP Hackintosh/NoteBook2009. 12. 6. 14:53

First of all, Thanks joshms83 and others,

Original Posts is in here

This guide references an image of setup files which I have made available here:

DELL M1210 OS X SETUP IMAGE: http://www.mediafire.com/?jmwxxyo1tht (MediaFire)

Note: The following is also provided as a nicely formatted read-me within the DELL M1210.dmg file attached to this post. The DELL M1210.dmg file also contains all of the patches/kexts/apps you need to follow the steps outlined below.

To help any desperate googlers:

Keywords: dell M1210 osx86 Geforce 7400 go External Monitor Dual Monitor Enable QE/QI Bluetooth Sigmatel 9221 Vanilla 9.0.6 10.5.6

rev. March, 2009.

The files included in this image were used to successfully configure a DELL M1210 Laptop using iDeneb v1.4 10.5.6 distribution and Vanilla 9.6.0 kernel. That is not to say however, that all or any of these files won't work for other configurations...

I've provided a summary of installation options used to get OSx86 running on a properly journaled partition, as well as a series of final install/patch steps to follow once you are successfully booted into OS X.

These files and instructions are simply a collection of other people's work organized and consolidated into a package that is (hopefully) easy to use and follow. I've attempted to provide credit to as many of those people as possible, but I may have missed some given this stuff was collected over several weeks of trial-and-error.

References:
http://www.insanelymac.com/forum/index.php?showtopic=41775 (M1210 Dual Boot Guide)
http://www.insanelymac.com/forum/index.php?showtopic=97966 (Dell Post Installer)

DELL M1210:
- Intel Centrino Duo T7200 @ 2Ghz
- 4GB DDR SDram @ 667Mhz
- NVidia Geforce 7400 Go (64Mb/192Mb)
- Sigmatel 9221 Audio
- Dell Bluetooth 355 2.0 +EDR (Broadcom)
- Dell 1390 (Broadcom) Wireless B/G

Resulting Working Feature Set:
This is a list of hardware/features that your system will support at the end of this process.
- Dual Cores (No need for cpus=1)
- GeForce 7400 QE/QI Enabled, Hardware Acceleration, Internal + External (Dual) Display
- Sigmatel 9221 Audio (Not Choppy)
- Internal Microphone
- Full Bluetooth Support
- Full USB Support
- Full Firewire Support
- Full Airport Wireless Support
- Full Laptop/Battery Support
- Full Intel Speedstep Support
- 5-in-1 Card Reader Support
- System will properly Sleep / Wake.
- Support for Apple Software Update

Issues:
- Intel 3945 A/B/G Wireless card is not supported (as of March 3rd 2009). You must replace it with a Dell 1390 card from Ebay (EASY - approx. $12)
- Shutdown command does not fully shutdown the system. I have identified this to be an issue with the Sigmatel 9221 audio patch and nothing else.
- Internal monitor does not properly recover when the system puts the display to sleep as a result of energy preferences (full system sleep works fine).
- Memory bank/DIMM_B is reporting a speed of 0 MHz. The system however, is reporting all 4GB of RAM.
- Logitech Quickcam (PID:0x08c6) is detected as a USB device by the system profiler, but is not yet supported.
Quickcam Drivers under development @ http://webcam-osx.sourceforge.net/cameras/index.php

Untested:
- ExpressCard Slot


OSx86 - iDeneb v1.4 10.5.6:
Vanilla 9.6.0 Kernel (Default)

Patches (Ready)
Chipset
- ICHx Fixed

Network / Ethernet
- AppleBC440x

Fix
- cpus=1 fix (Temporary)
- BatterManager
- Power_Off Fix

Video / NVidia
-NVKush (Temporary)

Apps
- ASU
- BetterZip
- OSx86 Tools
- Transmission

(OPTIONAL) NTFS Read/Write Support:
Note: While this step is listed as optional, if you are installing any of the provided patches directly from an NTFS partition, it is highly advised that you install full Read/Write support for NTFS drives before proceeding. It is also ideal for dual boot scenarios where you would like full control of your xp/vista partition from within OS X.

1. Install MacFUSE 2.0.3 (Mount and install from the .dmg file provided in the root of this setup image)
2. Install NTFS-3G (Mount and install from the .dmg file provided in the root of this setup image)

*Restart*

Patch Sigmatel Audio:
This step is required for OSX to fully support your Sigmatel 9221 audio and microphone.

1. Install AppleHDAPatcher (Copy AppleHDAPatcher v1.12 app provided in the root of his setup image into your Applications folder)
2. Apply Sigmatel9221 HDA Patch (Drag Sigmatel9221.txt provided in the root of this setup image onto the installed AppleHDAPatcher icon. (takes a while to run))

*Restart*

Install Modified NVinjectGO Extension:
The NVinjectGO v0.2.0 extension provided in this setup image has been modified to provide full QE/Hardware Acceleration/Dual Display support for the GeForce7400 Go. Graphics memory will read 512MB in system profiler, but this does not appear to have any adverse effects on system performance.

Note: "Mirror" mode will not work. Also, attempting to use the [Fn] + [F8] key combination (display mode toggle) will halt the system.

1. Delete NVKush.kext (Drag file to Trash - System/Library/Extensions/NVKush.kext )
2. Launch OSx86 Tools (Applications/iDeneb App/OSx86 Tools)
3. (OSx86 Tools) Install NVinjectGO.kext (Provided in this setup image (modified v0.2.0))
4. (OSx86 Tools) Enable Quartz GL
5. (OSx86 Tools) Run System Maintenance (Set Extensions Permissions, Clear Extensions Cache -> Run Tasks)

*Restart*

Enable Support for Both Cores:
This step will allow us to remove the "cpus=1" and "-f " kernel boot flags from apple.com.Boot.plist enabling and synchronizing both cores. Removing "cpus=1" enables both cores. Removing "-f" appears to correct kernel panic upon resume from sleep.

1. Launch OSx86 Tools (Applications/iDeneb App/OSx86 Tools)
2. (OSx86 Tools) Install Kernel ("mach_kernel" provided in this setup image under "/mach_kernel [DELL M1210] [Vanilla 9.6.0] [Dual Core]/mach_kernel")
3. (OSx86 Tools) Run System Maintenance (Repair Permissions, Set Extensions Permissions, Clear Extensions Cache -> Run Tasks)

*Restart*

4. Install pList Edit Pro (Mount and install from the .dmg file located on this setup image)
5. Open com.apple.Boot.plist (Library/Preferences/com.apple.Boot.plist)
6. Remove "cpus=1 -f" from kernel flags (Under <Kernel> change "<string>cpus=1 -f</string>" to "<string></string>")

*Restart*

If you system boots up normal, with no jittery mouse or sound, you are running properly with dual core support. While you shouldn't experience any problems, in the event that do, you can restart again, press any key during the darwin boot countdown and provide "cpus=1 -f" flags to boot back into stable system and undo the changes to your com.apple.Boot.plist file.


Install 5-in-1 Card Reader Support:
This kext installs support for the 5-in-1 card reader. I have used it to successfully mount a 4GB SD Card.

1. Launch OSx86 Tools (Applications/iDeneb App/OSx86Tools)
2. Install IOSDHCIBlockDevice.kext (Located in the 5-in-1 Card Reader directory included with this setup image)
3. Run System Maintenance (Set Extension Permissions, Clear Extensions Cache -> Run Tasks)

*Restart*

(OPTIONAL) Install Apple Software Update Support:
Notes originally provided with this mention needing chameleon 1.0.11 installed or higher prior to installing this feature. I did not try to update without this feature, but I did successfully patch my OS X installation using Apple Software Update after installing it.

1. Launch OSx86 Tools (Applications/iDeneb App/OSx86 Tools)
2. Install AppleDecrypt.kext (Located in the Apple Updater Support directory included with this setup image)
2. Install Disabler.kext (Located in the Apple Updater Support directory included with this setup image)
3. Run System Maintenance (Set Extension Permissions, Clear Extensions Cache -> Run Tasks)

*Restart*


(OPTIONAL) Install Intel Speedstep Extension:
I'm 50% sure that Speedstep is working without this step. Applying this step however, does not have any adverse effect on system performance, and allows you to visually confirm speedstep functionality via the included SpeedStep GUI application.

1. Launch OSx86 Tools (Applications/iDeneb App/OSx86 Tools)
2. Install IntelEnhancedSpeedStep.kext (Located in the SpeedStep Support directory included with this setup image)
3. Run System Maintenance (Set Extension Permissions, Clear Extensions Cache -> Run Tasks)
4. Install SpeedStep Application (Drag the SpeedStep included with this setup image into your Applications folder)

*Restart*

5. Launch SpeedStep Application (Run the installed SpeedStep app from your Applications folder to confirm working SpeedStep)

If you experience any problems (Kernel Panic, etc...) after installing IntelEnhancedSpeedStep.kext, press any key during the darwin boot countdown and provide the boot flag "-x". This will boot you into OS X "Safe Boot" and allow you to uninstall IntelEnhancedSpeedStep.kext from your system/library/extensions folder (by dragging it into the trash).

(OPTIONAL) Install Clamshell Display:
This step installs an extension that will put the system to sleep when you close the lid. It works 100%, but I'm not sure how I feel about it - so I marked it optional.

1. Launch OSx86 Tools (Applications/iDeneb App/OSx86Tools)
2. Install ClamshellDisplay.kext (Located in the Clamshell Display directory included with this setup image)
3. Run System Maintenance (Set Extension Permissions, Clear Extensions Cache -> Run Tasks)

*Restart*

If you decide you don't like this. You can remove it by dragging the ClamshellDisplay.kext file located in your System/Library/Extensions folder into the trash and restarting.


At this point you should have a pretty functional OS X setup.

Dual Boot Preferences/Notes:

- You can assign a more windows like behavior to your [CTRL] and [ALT] keys by swapping their key functions in System Preferences.
(Located under System Preferences -> Keyboard and Mouse -> Keyboard -> Modifier Keys)

- If you are using a bluetooth keyboard and mouse, they can be configured to work in both Vista and OS X without the need to constantly re-pair them:
1. "Connect" (not "Pair") to your device in vista (I use BlueSoleil v6 Bluetooth Stack).
2. In OS X, set up/connect your mouse using the "mouse" option (as you normally would) within bluetooth preferences.
3. In OS X, set up/connect to your keyboard using the "Any Device" option.
4. On the device locater screen, click "Passkey Options" and select "Do not use a passkey"
5. Proceed with the connection... select "use this as a remote control for my computer"
6. Future connection requests from your keyboard should be automatically accepted by OS X.

Note: I performed this with a Logitech MX5000 keyboard and Logitech MX1000 mouse (both bluetooth).


DELL M1210 OS X SETUP IMAGE: http://www.mediafire.com/?jmwxxyo1tht (MediaFire)
, , , , , , ,

'Hackintosh > NoteBook' 카테고리의 다른 글

Samsung Q210-FS02  (0) 2009.12.15
Sony Vaio CR11z, CR21z, CR31z with ATI X2300 and Snow Leopard  (0) 2009.12.07
HP 2133 with OSX?  (0) 2009.11.22
HP CQ40  (0) 2009.11.05
Toshiba Satellite A300-1N8  (0) 2009.10.29
:
Posted by Ritz®™
2009. 12. 3. 16:41

응용프로그램을 클릭한방으로 알아서 Update해보자 - AppFresh macOS/Leopard2009. 12. 3. 16:41

설치된 모든 어플리케이션을 검색하여 Update가 있는 소프트웨어를 그림과 같이 클릭한방으로 업데이트하여 줍니다.

Requirement : Tiger, Leopard, Snow Leopard.
, , , , , , , , , , ,

'macOS > Leopard' 카테고리의 다른 글

Apple 키보드 매핑  (0) 2013.02.25
맥에서 백업하기  (0) 2011.02.13
root 계정 활성화 하기  (0) 2009.12.16
10.5 BootCamp 드라이버  (0) 2009.02.09
:
Posted by Ritz®™
2009. 12. 2. 07:50

맥에서 하는 디스크 조각모음 macOS2009. 12. 2. 07:50

일단 맥은 윈도우즈와 비교하여 파일시스템 관리 구조(GPT+HFS 파티션 포맷) 자체가 다릅니다.

윈도우즈에서 사용하였었던 디스크 조각모음을 할 필요가 없습니다.

고정관념을 버리셔야 합니다.

- 6. Mac OSX 기본 사용법

그만큼 유닉스는 윈도우즈와 비교하여 상대적으로 아주 안정화된 시스템입니다.

하지만, torrent를 이용하여 다운로드를 많이 받으시는 분이나 간혹 굳이 디스크 조각모음을 하여야 겠다고 고집을 피우시는 분들을 위해 다음 그림과 같이 TechTool Pro라는 유틸리티를 소개합니다.




, , , , , ,


'macOS' 카테고리의 다른 글

iTunes 9.0.3, iLife Support 9.0.4, Digital Camera Raw Compatibility 3.0  (0) 2010.02.10
맥에서 커널패닉에 대한 대처  (0) 2009.12.25
Boot Argument  (0) 2009.11.27
Mac OS X 10.6 Snow Leopard: the Ars Technica review  (0) 2009.11.19
해킨토시 하드디스크 구성 가이드  (0) 2009.10.27
:
Posted by Ritz®™
2009. 11. 25. 09:40

iPhoto Update(8.1.1) macOS/Update2009. 11. 25. 09:40
, , , , , , ,

'macOS > Update' 카테고리의 다른 글

Apple to begin Testing Snow Leopard 10.6.3  (0) 2009.12.10
Apple updates Final Cut Server  (0) 2009.11.25
Microsoft Office 2008 12.2.3 Update  (0) 2009.11.11
Security Update 2009-006  (0) 2009.11.10
iMovie 8.0.4 Update  (0) 2009.07.17
:
Posted by Ritz®™
2009. 11. 25. 07:42

DSDT simple editor V1.3.6 (Extended tables support) Hackintosh/Tool2009. 11. 25. 07:42

First of all, Thanks roisoft and Evosx86 team,

Source : http://www.osx86.es/?p=610




Here I leave an application raised from our team to edit DSDT code.

There is an automatic patcher contains tools, fixes and hacks that you may be more comfortable working in the DSDT.

The application contains a contextual help and usage help.

Thanks:

A real software for its magnificent development forum.
A Fassl by extraction code registration Osx DSDT.
In the Linux community for their fixes over the years in the DSDT. (All included in "DSDT fixes").
The OSx86 community for their hacks to make our computers more compatible. (All included in "DSDT hacks).
Evosx86 team for their confidence and tests in this work.

DSE Version 1.0

DSDTSE V1.1 (ES) (version 1.3.0 and is EN / ES)

.

English:

Is a simple editor DSDTSE Aimed to help you solve your problems and add common DSDT hacks to it.

It will not do automatic patching, you have to manually add the fixes or hacks to minimun so skill is needed (regular skill should be ok to begin with).

Thanks to Fassl for the DSDT extraction method under Osx.

Thanks to the Linux community for their DSDT fixes all this years (all the ones included under "dsdt_fixes").

Thanks to the OSx86 community for their DSDT hacks (all the ones included under "dsdt_hacks").

Link to Español version:

DSDTSE V1.2 (version espagnole)

DSDTSE V1.2.1 (EN)

DSDTSE V1.2.3 (EN)

DSDTSE v1.2.4 (EN)

DSDTSE v1.3.0 (EN / ES)

DSDTSE V1.3.1 (EN / ES)

DSDTSE V1.3.3 (EN / ES)

DSDTSE v1.3.4 (EN / ES)

DSDTSE V1.3.5 (EN/ES)

DSDTSE V1.3.6 (EN/ES)

Version information:

Changelog V1.2 (EN).

Changed the routine to load DSDT when dropping files onto the app or double clicking them.

Now the app knows if you are running Leopard or Snow to correctly recognize the EFI partition.

Improved code (faster app).

Improved the routine permission to install the DSDT files.

Changelog V1.2.1 (EN)

Improved Español translation.

Changelog V1.2.3 (EN)

Solved a bug when opening custom code on the editor window (The program crashed).

Added 4 new DSDT hacks (PCI naming hack, hack CST X58, another cosmetic Jmicron Acl889a hack and hack).

Changed Skin.

Changelog v1.2.4 (EN)

Improved search method on code.

Added more devices to search Acpi PopupMenu.

Changelog v1.3.0 (EN / ES)

Added a new shini editor from Alex Restrepo.

Now Undo / Redo behaves as expected. (No more wrong repositioning).

Highlightning Code.

Code enclosed by brackets can be closed.

Line numbering.

Version update under help menu.

Changed placement of DSDT files to / Library / Application support / EvOsoftware instead / Library.

Improved search method.

Editor background color of code can be changed.

Text on code now has colors.

New window layout.

English and Spanish languages (Spanish is unfinished).

Added more DSDT hacks.

Changelog V1.3.1 (EN / ES)

Hopefully solved the bug when the app fails to create it's main working directory.

Changelog V1.3.3 (EN / ES)

Added support for Extended acpi tables on Main pane.

Changelog v1.3.4 (EN / ES)

Finally solved a bug on editor window. (when compilation goes wrong, become transparent buttons on editor after clicking error reporting window). Solved. : D

Changelog v1.3.5 (EN / ES)

Some minor tweaks in code.

Added more DSDT hacks.

Changed Icon.


Changelog V1.3.6 (EN/ES)

Catched a bug when using “Erase DSDT files” menu option.

Added more DSDT hacks.


Join the forum discussion on this post - (8) Posts


1. newhpet is ok ..... it will create a virtual hpet deice if you don't have one.

2. force compile should be used only if you have errors

3. you should use hpet on GA-EP35 and EP45.

* if you have hpet errors with appleintelcpu, use newhept.

'Hackintosh > Tool' 카테고리의 다른 글

TheUnarchiver 2.4  (0) 2010.07.09
Theme Changer  (0) 2010.07.06
Lizard & BootCDMaker in DARWINx86 software  (0) 2009.11.21
Path Finder  (0) 2009.11.10
EvOToolsX V1.1.0 EvOToolsX for Snow Leopard  (0) 2009.11.02
:
Posted by Ritz®™

티스토리툴바