Jump to content

Search the Community: Showing results for tags 'resolution'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 35 results

  1. VMQemuVGA display adapter driver for OSx86 running as a VirtualBox guest. The binary should work on all OSs from Snow Leopard up to Yosemite 10.10. It allows to set different screen resolutions in VirtualBox from System Preferences. The changes I've made to the fork have been minimal. GitHub project page Binary and source releases Special thanks: PureDarwin probonopd rafirafi Zenith432 VMware, Inc
  2. Hello everyone I have a problem setting the virtual OS X to display the screen's native resolution(1600x900). When the machine first boots up, it displays the right resolution then after the logging in by a few moments the screen displays a wrong resolution(800x450 HIPDI) which is a quarter of the resolution. I have macOS High Sierra (10.13.1) on VMware Workstation 14 Pro version: 14.0.0 build-6661328. My laptop has i5-4310U CPU with HD graphics 4400 which has 128mb dedicated video memory and a 1600x900 screen. I have installed VMware tools that was created on 14 September 2017 and VMware unlocker version 2.1.1 made by DrDonk. When logging in the background isn't the blurred wallpaper and the dock isn't transparent as it should be, or at least from what I saw on the internet. Here is what I have tried up until now: 1) Changing the resolution from the system preferences. 2) Using sudo /Library/Application\ Support/VMware\ Tools/vmware-resolutionSet 1600 900 Which displayed this output: Requested resolution: 1600x900 Effective resolution: 1600x900 Without any result. 3) I tried setting the screen's native resolution in the Display settings of VMware, still nothing. 4) I also tried to change virtualHW.version from 14 to 10 but it also did not do anything noticeable. The only thing that changed is that the blurred wallpaper was in the background when logging in. One thing to note is that it runs correctly up until 1366x768. I think the problem may be that the OS tries to load kexts after the logging in that interferes with the VMware tools, but I am not sure or that there is a hardware limitation, but I do not know a way to test it. Does anyone know how to fix that?
  3. Hello guys! I successfully installed MAC OS X El Capitan in my system, ethernet and audio drivers, but im having a really sad graphic performance, problem with resolution and flickering pixels on screen, specially in animations. I tried to fix with this, but no success: http://www.insanelymac.com/forum/files/file/63-intel-hd-2000-full-resolution-enabler-kexts/ Im still noob in this subject, but i was looking for DSDT, is there a way to me make a DSDT using AIDA64 in Windows about Intel HD Graphics 2000 and then patch in MAC OS X? Thanks adv.
  4. Hi everyone. I'm new to this forum and hackintoshes. Just recently I was able to successfully install OS X 10.9 on my HP G62-470CA (specs here: http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_ba847bafb2a2d782fcbb0710b053ce01=wsrp-navigationalState%3DdocId%253Demr_na-c02674415-2%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.tpst=ba847bafb2a2d782fcbb0710b053ce01&ac.admitted=1408231975655.876444892.199480143). Although I am super excited about using OS X I'm not quite happy yet. I am getting 1024x768 on a laptop that should be getting a higher resolution (and should be able to output a higher resolution). The icons look weird, there if flickering when browsing the web and other misc activities, and animations are a complete eye sore. Suffice to say I need help. The laptop works off of integrated graphics, the Intel HD 4000. How can I remedy the problems I am having. (Bonus: Is there a way I can also re-enable my VGA and HDMI, I usually output to an external monitor at 1920x1080). I'm sorry if this isn't satisfactory information for you to help me with my problems, please ask and I will try and get back to you with the information asap, I'm really new to this and am not completely sure what information I should provide. Thanks for your time, hopefully we can solve this problem.
  5. Hello , I've learned how to change manually your resolution when u don't have a supported graphic card on your Hackintosh. Lets start!!! My card is a SiS 671/771. Go to /Extra/org.chameleon.Boot.plist Add the following strings: <key>GraphicsEnabler</key> <string>No</string> <key>Graphics Mode</key> <string>WIDTHxHEIGHTx32</string> Where u gonna change the number of resolution u want, gonna be something like that, thats my one look: <string>1280x768x32</string> Now save the file and lets move to: Go to /Extra/Themes/Default/theme.plist Now u gonna edit the part <key>screen_width</key> <string>WIDTH</string> AND <key>screen_height</key> <string>768</string> Put the same width and height that u added to org.chameleon.boot.plist and save the file. Now u gonna reboot and your resolution will be changed!!!! To check what resolutions your Graphic Card support, boot into Chameleon screen and press down arrow, then go to Video Info, it gonna show a huge list of resolutions that your graphic support!!! Any questions ask me here!Ive been looking for a solution to change my resolution that was 1024x768 and edited org.chameleon.boot, apple.boot.plist, edited the Monitor Pref Panel and nothing worked, only that has changed my resolution!!!
  6. Hi, please advise with the following, I've never installed a MacOS before, also I don't have any Apple devices. I've installed VMware Workstation Player 12.1.1 build-3770994 on Windows 10, applied a patch Unlocker 2.0.8, created a 80GB VM with HW ver.12 and specified a smc.version = "0" by applying to a vmx file, Installed vanilla 10.11.1 from a bootable ISO without specifying an Apple ID, installed VMware tools under it, then I've downloaded and applied an update to 10.11.5 through App Store. I would like to proceed with Clover EFI bootloader installation for a couple of reasons. The problem is that installed MacOS is almost unusable for me in spite of auto detecting the host display settings in VMware and "Default for display" resolution under MacOS system preferences: every objects are too small! The height of upper menu is almost half of my mouse cursor. I think it is caused by a host system which have 13.5 inch display with 267 dpi (3000 x 2000), as far as I know this called a HiDPI (Retina) displays, Windows 10 default display settings size of objects are 200% on my system. Please suggest if there are some suitable and "right" solutions because I couldn't easily find any. Also I'm interested, if it's possible to pass a real DPI parameter to a guest system because anyone can decide to connect any additional display with a different DPI and while VMware window can be resized anytime, I think it should pass the DPI of current host display to guest system.
  7. I have only JUST managed to get OSX86 installed on my laptop, and that was by installing Tiger. However, after all this, there is one last problem. The resolution... It is stuck at 1024x768 and wont let me make it larger OR smaller for that matter. My computer screens resolution SHOULD be at 1280x800. It also says this so im unsure what i should be doing >.< ive googled around for a kext but nothings coming up :'( I also tried to edit the com.apple.boot.plist but thats dont nothing also What SHOULD i do XD
  8. Hi! I just want to share with you my "solution" for my boot screen. I think many of us having the bootscreen like this: with that two bold black area on both side My display native resolution is 1920x1080 but I couldn't get that resolution for boot screen. So I simply found out what resolution I have by checking it in my monitor/display osd menu while osx was on the boot screen (for me it is: 1600x1200). When I found out what resolution I have on the boot screen, I did this: I went to /Extra/Themes/Default/ folder, and opened the theme.plist file. Changed boot_height and screen_height to 1200 Changed boot_width and screen_width to 1600 Saved the changes to the theme.plist file. Then I made an 1600x1200 size image in photoshop (you can use gimp or something else), filled it with black, and put a nice apple logo to the middle, then saved1 it as boot.png. Backed up /Extra/Themes/Default/boot.png file. Replaced /Extra/Themes/Default/boot.png with my 1600x1200 size boot.png file. Rebooted. (Green is your horizontal, Blue is your vertical resolution on the boot screen.) 1: Try to make the png as small (filesize) as you can (for better loading speed). I used multiple online png crush/compress tools to achieve this (google for "online png crush" or "online png compress"). Now I have a nice iOS-like boot screen: I'm using this since I'm using a hackintosh (1,5years). Notes: - make sure you don't have "Legacy Logo=Yes" in boot.plist. - with the big boot.png, you can't see the spinning wheel (like in iOS)
  9. bob321654984

    4k / UHD with Yosemite

    I have a Samsung 4k monitor hooked up to an Nvidia Geforce 760 in my Hackintosh via DisplayPort. If I leave the settings on 'Best for display', for some reason it goes into 1080p mode. If I put it in 3840x2160 resolution manually (which, for some reason I can only do using the screenresx third party app, the resolution isn't listed in the normal display settings), everything is absolutely tiny (buttons, menus etc). I had thought (and have seen screenshots) that there would be the ability to change the scaling of all the items within Yosemite, but the only way I can make everything readable (and even clickable without pico-adjustments of the mouse!) is by downgrading the resolution, which seems a bit pointless. Has anyone got 4k working as I was expecting, or have any suggestions that I could try to get this functionality somehow?
  10. UPDATE Hm sorry I forgot to update this topic. This tutorial works only in 10.8 here on my hackintosh. I have read that some people made it work in 10.9, but only with Intel's intergrated GPU. Cheers -------------------------- Hi. Excuse me for my English. I'm trying to make it simple. 1, Prepare SwitchResX, PlistEdit Pro and IORegExplorer. SwitchResX is not a must but I recommend it. 2, Enable HiDPI if you haven't done it sudo defaults write /Library/Preferences/com.apple.windowserver DisplayResolutionEnabled -bool YES; sudo defaults delete /Library/Preferences/com.apple.windowserver DisplayResolutionDisabled; Log out and log back in if you'd like to be sure. Also works if you have Quartz Debug. 3, Extract EDID in SwitchResX. Or from IOReg as in Picture A. 4, In Terminal, run ioreg -l Use Edit - Find to get your DisplayProductID and DisplayVendorID. In my case, I got DisplayVendorID = 14499 DisplayProductID = 26609 You also need to find IODisplayPrefsKey but it would must easier to get that in IOReg, as shown in Picture A. In my case I got this IODisplayPrefsKey = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPCI2PCIBridge/PEGP@0/ATY,Ipomoea@0/ATIFramebufferNI/display0/AppleDisplay-38a3-67f1 Hence the value: AppleDisplay-38a3-67f1 5, Create a folder on the desktop and name it DisplayVendorID-****. In my case it was DisplayVendorID-38a3 And then create a blank text file named DisplayProductID-***. In my case it was DisplayProductID-67f1 Use the Get Info panel to make sure this text file HAS NO EXTENSION. 6, Edit this DisplayProductID-*** file in PlistEdit Pro. Add the following children and edit their values with your own DisplayProductID DisplayVendorID and EDID data. <key>DisplayProductID</key> <integer>****</integer> <key>DisplayVendorID</key> <integer>****</integer> <key>IODisplayEDID</key> <data> **** </data> In my case, it was like <key>DisplayProductID</key> <integer>26609</integer> <key>DisplayVendorID</key> <integer>14499</integer> <key>IODisplayEDID</key> <data> AP///////wA4o/FnAQEBAQYWAQOAMBt4KpLFollVnicOUFS/7wCBQIGAlQCzANHAAQEB AQEBAjqAGHE4LUBYLEUA3QwRAAAeAAAA/QA4Sx5QEQAKICAgICAgAAAA/ABWRTIyMDFY RwogICAgAAAA/wAyMjExMTUzME5DCiAgAFM= </data> 7, To add your custom resolution, create a new child like this <key>scale-resolutions</key> <array> </array> And add a new sibling <data></data> 8, Convert your custom resolution with a Hexadecimal Converter/Decimal Converter My GPU supports 2560 x 1600 max. My display supports 1920 x 1080 max. So I will need 2560 x 1440 for retina. 00000A00 000005A0 00000001 00000A00 = 2560 000005A0 = 1440 00000001 This one doesn't really matter. I also added 1366 x 768 because I could not stand 1360 x 768 provided by OS X. 00000556 00000300 00000001 Someone with 780 SLI or 7990 Cross-Fire may set 3840 x 2160 for 1920 x 1080 HiDPI. lol Therefore, in your PlistEdit Pro it should look similar to mine: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>DisplayProductID</key> <integer>26609</integer> <key>DisplayVendorID</key> <integer>14499</integer> <key>IODisplayEDID</key> <data> AP///////wA4o/FnAQEBAQYWAQOAMBt4KpLFollVnicOUFS/7wCBQIGAlQCzANHAAQEB AQEBAjqAGHE4LUBYLEUA3QwRAAAeAAAA/QA4Sx5QEQAKICAgICAgAAAA/ABWRTIyMDFY RwogICAgAAAA/wAyMjExMTUzME5DCiAgAFM= </data> <key>scale-resolutions</key> <array> <data> AAAKAAAABaAAAAAB </data> <data> AAAFVgAAAwAAAAAB </data> </array> </dict> </plist> 9, Copy your DisplayVendorID folder to /System/Library/Displays/Overrides Now you can take a look in SwitchResX. Your custom resolutions should show up as "scaled" and "system-inactive". If you don't have SwitchResX it doesn't matter either. Restart and voila! Picture B Picture C Do NOT try to choose 2560 x 1440, though. You will get a white screen or worse. Choose 1280 x 720 HiDPI instead. Note: A. Some other tutorial shows how to add custom resolutions with Switchres and Quartz Debug. It seems for laptops only. I was unable to add resolutions on my Hackintosh. Instead I got irrelevant DisplayVendorID folders in /System/Library/Displays/Overrides . Make sure you delete these folders before applying this tutorial. B. I have not tested it with multiple displays, laptops or even TV. It is possible to be the same and, following this tutorial, you can add multiple EDID profiles to /System/Library/Displays/Overrides C. Known issues: Lag a tiny bit when switching spaces. Also white screen for less than a second after logging in but before your retina desktop shows up. But it works fine on my Hackintosh now. D. Do tell me if it would burn your GPU when you play games. lol A lot of thanks to Apple, Steve, Hackintosh hackers, this forum, and especially authors of these two posts http://www.insanelymac.com/forum/topic/208410-fixing-scrambledstretched-or-wrong-resolution-laptop-display-problems/ Fixing Scrambled,Stretched, or Wrong Resolution Laptop Display Problems http://www.insanelymac.com/forum/topic/281412-how-to-advanced-edid-injection/ HOW TO: Advanced EDID Injection Ciao Henry Pentium G840 Gigabyte H61M-DS2 rev.2.2 F8 Samsung DDR3 1600 4G MSI R6670-MD2GD3v2 Hitachi 320 GB (WIN 7 X86 SP1) Seagate 500 GB (10.8.4) NEC VE2201XG Display 1280x720 HiDPI
  11. Luiz Carlos Belem

    what ktext for nvidia gforce 7050 (64mb onborad) ?

    Hello! My motherboard have onboard video (Nvidia 7050 64mb), exist any driver for this ? I can change my resolution to 1024 from 1280 ? tanks for help!
  12. hello just iATKOS v7 and everything's working fine . Usb , wireless , all are OK except Screen resolution Currently in Mac OS X the screen resolution is 1024 x 768 The Below Screen Shot Displays the Present Display Hardware Settings The Below Screen Shot Displays My Monitor's Specification Details. Please Help Me Guyz.
  13. How to Enable Resolution on Intel HD Graphics (0046:8086 and 0042:8086) Background Info: It has been said since the dawn of time: “Ye who build a Hackintosh must select a Graphics Card that ye can find in a real Mac to ensure 100% compatibility.” However, it appears a very rare exception is ye…I mean the infamous Intel HD Graphics. These first-gen integrated Graphics Cards found on Core iXXX processors are the first to use the new I/O design, integrating the Northbridge into the CPU itself. The Intel HD Graphics chips have been used in real Macs before, like the Mid-2010 MacBook Pro. The problem: Every Mac that has the integrated Graphics chip also has a dedicated Graphics Card, like the NVIDIA GeForce GT 330M on the same MacBook Pro model. Therefore, it’s not that Apple didn’t write drivers for the Intel HD Graphics, but their drivers are, well, buggy on PCs, resulting in either a frozen or blank screen once the framebuffer Kext loads. People have worked out a way to enable partial Quartz Extreme in Snow Leopard 10.6.7, but even that is very buggy. Try to launch anything Full Screen, get greeted with a surprise Kernel Panic. There was no hope as to how to get full resolution…until now! Manor had thought he had found a way to enable full resolution on Intel HD Graphics, but what he didn’t realize was that his VESA mode tables in his Video BIOS supported his resolution. Everyone that his “fix” worked for them also had it supported in their Video BIOS. Everyone else likely had the maximum of 1024x768 in their mode tables, and therefore couldn’t work. Since then, people had suggested patching the Video BIOS on the fly with the Resolution module… a module based off of the 915resolution Linux hack that also patches NVIDIA and some ATI cards. However, by itself, it doesn’t do a thing. Yet, a recent patch to the module enables support for the Intel HD Graphics! This isn’t a simple one-for-all compile, however. Why? The patch is full of hacks, and it requires you to insert your DTD, an 18-byte sequence extracted from your EDID, into the source code directly. You need a little bit of programming knowledge, but it’s so trivial that just about anyone with little to no programming knowledge (like me) could patch. So, what do you need to get this patch to work? Requirements: Access to Mountain Lion with XCode installed and network access (to compile Chameleon) Access to Windows Extracted EDID of the computer in question UPDATE: If you want, you can try RemC's module in this post; it should be universal and not require any source code patching on your part. Look at the second post: http://www.insanelym...6/#entry1877529 A flash drive (optional, even an old 256MB flash drive would do) You’ll also need to download these tools: DTD Calculator – http://www.clevertec...roductsfree.htm Attached Resolution source code IMPORTANT UPDATE (4/4/2013): If you plan on enabling QE/CI (see below), don't bother with any form of the resolution module. The patched framebuffer will allow custom resolution without the resolution module. The Resolution module is only needed if you want custom resolution on your boot screen. Otherwise, don't mess with it as it may cause distortions. The guide is below is kept for legacy purposes/for those who want to create their own Resolution Module. How to Extract your EDID: This is pretty self-explanatory in another thread: http://www.insanelym...s/#entry1392033 Go to Solution B. I prefer using the Windows way, but the link to the utility there is dead. Go here: http://www.eldim.fr/...lite-free-tools and click the link that reads “EDID Viewer utility”. Please note, though, and I cannot stress this enough: THIS NEEDS TO BE RUN ON THE COMPUTER WITH INTEL HD GRAPHICS INSIDE. THIS WILL EXTRACT THE EDID VALUE FROM YOUR MONITOR, SO YOU NEED TO RUN IT ON THAT COMPUTER ONLY! (Sorry for shouting, but EDID varies from monitor to monitor, even LCD monitors from the same laptop model with the same max resolution. Using someone else’s EDID is like using someone else’s DSDT.aml file. Thus, run only on your computer with Intel HD Graphics on it.) Save your EDID raw data somewhere, or copy your EDID to your clipboard if you’re using the same computer. Now that you’ve got that saved, you’re ready to go to step 1. Step 1 – “Convert” EDID to DTD: I put the word convert in quotation marks because we really aren’t converting it. All we’re doing is extracting specific 18 bytes from the EDID raw data. Launch DTD Calculator and a text editor. For our purposes, Notepad will do. When you copy the raw data from ELDIM, it’ll look something like this: 0x00 00 FF FF FF FF FF FF 00 30 E4 AC 02 00 00 00 00 0x10 00 14 01 03 80 22 13 78 0A C1 25 9D 5F 5B 9B 27 0x20 19 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 0x30 01 01 01 01 01 01 12 1B 56 78 50 00 0E 30 20 20 0x40 24 00 58 C2 10 00 00 19 00 00 00 00 00 00 00 00 0x50 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 00 4C 0x60 47 20 44 69 73 70 6C 61 79 0A 20 20 00 00 00 FE 0x70 00 4C 50 31 35 36 57 48 32 2D 54 4C 51 42 00 C1 You need to have the raw hex data in a single line with only a space to separate them. Using mine, it then should read like this: 00 FF FF FF FF FF FF 00 30 E4 AC 02 00 00 00 00 00 14 01 03 80 22 13 78 0A C1 25 9D 5F 5B 9B 27 19 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 12 1B 56 78 50 00 0E 30 20 20 24 00 58 C2 10 00 00 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 00 4C 47 20 44 69 73 70 6C 61 79 0A 20 20 00 00 00 FE 00 4C 50 31 35 36 57 48 32 2D 54 4C 51 42 00 C1 In DTD calculator, click the Interpret EDID tab, and paste the resulting string in there. And then click Interpret EDID. It should say the DTD on the bottom right. Double click it. You may get a warning that reads “Entered DTD and Generated DTD don’t match”. Ignore it. To make sure you’ve got it right, or if there is more than one, the right should have a value under H Active Pixels and V Active Lines. These values should be your resolution. Now click the Calculation tab. On the bottom you’ll see the calculated DTD. Click in the text box. Press Ctrl+A to select the text and Ctrl+C to copy it to the clipboard. This is the DTD. Here is my DTD as an example: 12 1B 56 78 50 00 0E 30 20 20 24 00 58 C2 10 00 00 18 Paste it into a notepad window and save it as a text document. Make sure you’ll be able to access this on the machine where you’ll be compiling Chameleon. Speaking of which, we now need to move onto the next step, which happens to be compiling Chameleon. Step 2: Compile Chameleon with Modified Resolution Code Just like its mother, 915resolution, the Resolution module will modify our VBIOS on the fly to allow us to select a different resolution from the VESA tables. Therefore, before we compile, we need to modify the code. Thankfully (with many thanks to InsanelyMac User and Chameleon developer orlian, as well as Chameleon developer dmazar), we can patch use already modified code. However, we still need to replace the present DTD with ours. Remember, as this is from EDID, it will vary from monitor to monitor. But first, we need to download and clean up Chameleon’s source code. To do so, download XCode on Mountain Lion, and install command line tools. You can use an already existing hackintosh with internet, a real Mac, or, like me, use a VMware virtual machine. Once you have XCode installed, open a terminal window (don’t freak out if you’ve never used command line before; these commands are safe) and type the following commands: mkdir chameleon-imod cd chameleon-imod svn co http://forge.voodooprojects.org/svn/chameleon/trunk/ cd trunk make clean If all goes well, there should be a folder called “chameleon-imod” in your home folder. In there, should be only one folder called trunk. Inside that folder should be all sorts of file, including an XCode project called Chameleon. Navigate further into i386 > modules. This contains the source code for the individual Chameleon modules. Delete the folder called Resolution and empty the trash. Then, replace it with the attached Resolution source code. Resolution.zip Now, in the Resolution folder, open the file called 915resolution.c. This will open an XCode Window and navigate to line 32. The code should be: map = open_vbios(CT_UNKNOWN); // if(map) { unlock_vbios(map); char* bytes = (char *)VBIOS_START; int patchlocation = 0x0254; verbose("Addr: %X Before patch: %x - ", patchlocation, bytes[patchlocation] ); bytes[patchlocation] = 0x8A; verbose("after patch: %x \n", bytes[patchlocation++] ); bytes[patchlocation++] = 0x25; bytes[patchlocation++] = 0xA0; bytes[patchlocation++] = 0x20; bytes[patchlocation++] = 0x51; bytes[patchlocation++] = 0x84; bytes[patchlocation++] = 0x1A; bytes[patchlocation++] = 0x30; bytes[patchlocation++] = 0x30; bytes[patchlocation++] = 0x40; bytes[patchlocation++] = 0x36; bytes[patchlocation++] = 0x00; bytes[patchlocation++] = 0x30; bytes[patchlocation++] = 0xBE; bytes[patchlocation++] = 0x10; bytes[patchlocation++] = 0x00; bytes[patchlocation++] = 0x00; bytes[patchlocation++] = 0x1E; This is the portion we need to modify to match our DTD. Every byte XX in our DTD is read by the source code as bytes[patchlocation++] = 0xXX; Therefore, in my DTD code, 0x8A becomes 0x12, 0x25 becomes 0x1B, 0xA0 becomes 0x56, etc. Once that’s modified, save it and exit XCode. We’re now ready to compile Chameleon. Navigate back to the terminal window and type: make I know it’s a pain we have to compile all of Chameleon when we only need to compile the resolution module, but we can’t just type make in the directory of the resolution module source code; I’ve tried it and it doesn’t do anything. Once that’s taken care of, navigate back up to the trunk directory, and in the sym folder, should be the i386 folder of Chameleon binaries. If you’re going to do step three, copy this back to a Windows computer. I recommend compressing it into a zip file first if you do that. If not, go straight to step 4. Why am I suggesting you don’t have to do step 3? Step 3: Install Chameleon to a test flash drive (optional) This is not required, but I do recommend you do this. Why? There isn’t any reason to believe you can’t simply copy the resulting Resolution.dylib to /Extra/modules/ folder. However, if something went wrong and the computer can’t boot due to wrong resolution/poor timings, the resolution module is only present on the Flash Drive and you can simply reboot off of the hard drive without issues and try compiling again. If you skip step 3, though, you’re stuck until you boot without the module. Therefore, I recommend you install Chameleon to the flash drive for testing purposes. Once you go into Windows, I’ll be showing you a somewhat new way to install Chameleon using Clover’s Win32 tools. Download the package called Win_USBTools-Fat32_Clover_v2_rL954.zip from here: http://www.osx86.net..._efi_tools.html Extract the archive inside there called USBTools-Boot1f32.zip. Be sure to back up everything on your flash drive that you need. We’re going to format it with the tool HPUSBFW.EXE. Run it as administrator, select your flash drive, and tick quick format. Make sure it’s set to format it to FAT32. Click start. Confirm you want to continue and let it do its thing. Once that’s done, and this is important, unplug it (don’t use safely remove hardware), and plug it back in. Next, open a command prompt in the extracted directory as administrator, and type: BootUSB.bat X: Where X is the drive letter of your flash drive. If it completes without errors, do the same replug method as before. Finally, extract our compiled binaries. Copy the file “boot” to the root directory of the flash drive and create an Extra folder. If you need to copy any contents from your own Extra folder (especially true if FakeSMC.kext is inside /Extra/Extensions and not /System/Library/Extensions), do so now. However, be sure to run create a modules folder inside the Extra folder and copy “Resolution.dylib” in that modules folder. Step 3a: Testing Once that’s done, reboot off of the flash drive. If there was a theme inside your Extra folder, the VBIOS patch should be noticeable from the GUI. If there isn’t a theme installed, or the resolution still appears form the GUI as 1024x768, type at the boot prompt “?video” (without quotes) to make sure that the resolution is listed in the VBIOS. If it isn’t listed there, something went wrong. It should patch an already present resolution. In my case, it was 800x600. If your resolution is listed, try typing “Graphics Mode”=”XxYx32” (WITH Quotes, where X and Y are your resolution values, i.e. 1366x768x32) with any other boot flags you need to successfully boot OS X. If all goes well, you should see full resolution. If something looks funny, but the resolution is correct, then the timings are wrong. Make sure that the DTD was copied correctly in step 2 and try compiling again. If, however, it isn’t listed, boot using the flags “-v Wait=Yes” (without quotes), and before it loads OS X, you’ll see a screen with all startup logs by Chameleon. Scroll down (With theme/GUI, use arrow keys, without theme, space bar to go to next page, p to go to previous page) to where it says “Resolution.dylib by Unknown loaded”. This is the log of Chameleon loading the resolution module. If it shows any errors, take a screenshot of the log and feel free to upload an image here. If you’ve got your full resolution within Mac OS X, you’re ready to install the Resolution module to your Chameleon installation. Step 4: Install the Resolution Module to your existing Chameleon/OS X installation Copy the file Resolution.dylib from your flash drive (or your compiled binary extracted from the zip folder) to /Extra/modules. If there isn’t a “modules” folder in the /Extra folder, create it. Also, be sure to modify org.chameleon.Boot.plist to have these lines in: <key>Graphics Mode</key> <string>1366x768x32</string> Of course, be sure to change the resolution to match your own if it’s different. Once that’s done, reboot and you’ll have your resolution in OS X. If something goes wrong, use the same steps in step 3a to debug the error. Step 5: Enabling Acceleration in Mac OS X Mountain Lion TBD. UPDATE (2/5/2013): Mountain Lion now is capable of enabling Core Image on our Graphics Card. Still no Quartz Extreme, but if you try it out, check out Part 2 in this post: http://www.insanelym...s/#entry1885544 Thanks goes to GhostRaider for the guide, and Mehdymehdy for his discovery! MAJOR UPDATE (3/10/2013): We have made history: a patch for the Mountain Lion Framebuffer was made, and it works now on our machine. Look at this thread: http://www.insanelym...-fixed-sl-1068/ and this post: http://www.insanelym...20#entry1895588 Special thanks to verteks and warraisraw for their discoveries!! However, if you don’t have a problem using an older version of OS X, follow these guides to enable partial QE/CI in Snow Leopard: http://www.insanelym...0/#entry1504066 http://www.insanelym...d/#entry1827443 And that’s it! I hope this guide has been of use to you, and that you’ll be able to use your Intel HD Graphics once and for all! Special Thanks To: orlian dmazar slice and last, but certianly not least, everyone who helped contribute to this VoodooLabs thread: http://forum.voodoop...4.msg13045.html
  14. Hi everybody. I can't install my graphics card on my Hackintosh. I've tried several methods and no one of them work, when I go to the tab "About this Mac" it says on Display that I have a 3MB screen and I don't have 1920x1080 resolution.I'm a beginner here in the Hackintosh world so please be patient with me. Hope you can help me. Thank you. Also I'm uploading my Clover folder. CLOVER.zip
  15. ManIkWeet

    The Intel HD3000 problem.

    Hi After a short time of usage, I get horrible graphical glitches on my screen. See screenshots: I can temporarily remove the glitches by changing resolution to scaled and then back. I have a single resolution available: 1600x900 Graphics kexts are stock Apple. I am on OS X 10.9 (13A598). My bootloader is Clover, but I am willing to switch to Chameleon if needed. OS X recognizes same EDID as Windows, though said EDID does not seem complete. HDMI Connector does seem to work properly, though graphic glitches do appear on external monitor. I can not change VRAM in BIOS. On verbose boot, I get the infamous "Buffer pool allocate failed" message. Connectors: Internal LCD VGA HDMI Hardware specifications: Intel i5 2410m, 2.3GHz Intel HD3000 with device id = 0x01198086 4GB 1333MHz DDR3 RAM Intel Mobile HM65 chipset Laptop/Notebook model: Asus K73E-TY071V
  16. nomadtrsh

    Sapphire HD5770 second monitor resolution

    Hi guys:-) I am here from 2008,and i make a Hackintosh these years which works 'till now...nowadays things are changed and i am started as a total NOOB:-) Now i completed new (old) maschine with Sapphire Radeon 5770 which has DVI, HDMI and Display port out.... Basically everything works fine because i find right DSDT file, i have ML 10.8.5 installed but....and the goddess of fortune was with me at this moment:-) and of course one friend from Zagreb who help me a lot with some advices:-) THX to him a lot:-) When i boot normally i have a fine correct scaled resolution on main monitor (1920x1200) and it is fine but on Toshiba TV 50" (second monitor) connected on HDMI output in HDMI splitter i have a max resolution of 720p or a little bit more 1360x768...and it is recognized as TOSHIBA TV On this HDMI splitter i have a 2 Toshiba TV in two rooms...on PC installation everything works fine... When i start with AtiConfig=Vervet i have a lot more resolutions higher than 1920x1080 on second monitor but it is recognised as VGA monitor and of cource card cannot start in this resolution and allow me to set max 1280x720....when i try to set 1920x1080 or higher it always returns me on first resolution.... If i start with AtiConfig=Baboon i see only a small part of second screen on both monitors:-) and i cannot do nothing.... Mobo: Gigabyte GAX38 DQ6, Sapphire Radeon 5770, 8 GB DDR2 Any suggestion for this problem maybe? THX in advance....
  17. Hi, I hope I'm posting this in the right forum. (I'm a noob when it comes to things like this) I'm a bit new when it comes to Hackintosh, but I'm really stumped about this. I recently got Kalyway 10.5.2 to run on my old Asus M6800n notebook as that was the only version of Leopard I could get working. The setup didn't include the right kexts for my graphics card (ATI Mobility Radeon 9600) so I left them uncheck. Rest of the setup went fine, just had to install some missing Network and Sound kexts. When that was all done I edited the com.Boot.Apple.plist so that it wouldn't be stuck in 1024x768, which worked. But now I'm having this problem. The screen that is actuall on the notebook shows everything fine. However, the external Acer VGA monitor I have hooked up to the notebook has it's edges cut off. You can see these in the pictures attached. This is the screen of the Asus M6800n. As you can see every thing is on screen. This is the Acer VGA Monitor. As you can see the top and sides are cut off and not visible. I've looked through many forum posts, done tons of searches and all of the methods I found don't seem to work. One that involves modifying a Callisto kext seemed like it might work, and I would have tried it but it seems that the Callisto website is dead. I'd really like to use this monitor as the hinges on the notebook screen are partially broken. So, in short the apple menu bar and sides of the screen are being cut off on my external monitor but not my notebook's screen. If anyone knows why this is happening or what I can do to fix it please let me know. Thanks
  18. Hi, I have a 30" Apple Cinema Display, a DL-DVI to HDMI adaptor and a 2013 MacBook Pro. That's all well and good, but the resolution of the Cinema Display is topping out at 1280x800. If anybody could give me some ideas - as I'm stumped - that would be great, and your help would be most appreciated. Thanks in advance.
  19. I have a Mac Mini 2006 (upgraded) with Intel GMA950 graphics, running MLPostFactor 10.8.5. It is connected to an ASUS VS197 LCD panel using DVI-D. This is natively a 1366x768 panel that is recognized and works fine. However, the other choices for resolution are 4:3 800x600 and 1024x768, and then the oddballs 832x624 and 1360x768. None of these are useful as a low-resolution widescreen for gaming or watching DVD content. Specifically I want to get access to 848x480 or 854x480, and also 1024x576. SwitchResX makes these choices available, but it doesn't work with a "full screen" game, presumably because the game directly queries OSX Display to get a list of valid resolutions and SwitchResX is bypassing that system instead. So the solution is obvious: buy a new computer pull the monitor's EDID data, hack it to enable new resolutions, and then tell OSX to use this custom EDID instead of the one retrieved from the monitor. Following the steps of the EDID injection guide, here is where I am: * Retrieve EDID, DisplayVendorID etc from ioreg. 00 FF FF FF FF FF FF 00 04 69 F2 19 24 94 00 00 31 16 01 03 80 29 17 78 EA F5 45 A4 55 50 9E 27 0F 50 54 BD EE 00 81 C0 01 01 01 01 01 01 01 01 01 01 01 01 01 01 66 21 56 AA 51 00 1E 30 46 8F 33 00 9A E6 10 00 00 1E 00 00 00 FD 00 32 4B 18 53 11 00 0A 20 20 20 20 20 20 00 00 00 FC 00 41 53 55 53 20 56 53 31 39 37 0A 20 20 00 00 00 FF 00 43 43 4C 4D 54 46 30 33 37 39 32 34 0A 00 F1 * Use an EDID editor to enable new 848x477 and 1024x576 resolutions. (Verify with an online EDID tool, and compare to the previous version) 00 FF FF FF FF FF FF 00 04 69 F2 19 24 94 00 00 31 16 01 03 80 29 17 78 EA F5 45 A4 55 50 9E 27 0F 50 54 BD EE 00 81 C0 4B C0 4B CA 4B CF 61 C0 61 CA 61 CF 01 01 66 21 56 AA 51 00 1E 30 46 8F 33 00 9A E6 10 00 00 1E 00 00 00 FD 00 32 4B 18 53 11 00 0A 20 20 20 20 20 20 00 00 00 FC 00 41 53 55 53 20 56 53 31 39 37 0A 20 20 00 00 00 FF 00 43 43 4C 4D 54 46 30 33 37 39 32 34 0A 00 47 * Create a new subfolder and plist within /System/Library/Overrides/Display/ containing the new EDID string and monitor name. * Reboot. Now the problems begin. Even though the plist file is being read (which I know because the Monitor Name has changed in Displays), the custom EDID is not being used. When I dig into IORegExplorer I am able to come up with AAPL00,EDID string and it is the unmodified one read from the monitor. I even tried a plug-and-unplug while OSX is running, and also tried to reset the SMC and NVRAM, but no dice. Do I need to start digging into DSDT hacking? Is the Intel driver pulling down EDID during boot and I need to override it somewhere else? What am I missing here?
  20. Hello to all! Yesterday I finished installing OS X Mavericks onto my PC and all is working fine apart from one problem. I cannot change the resolution to anything that isn't 4:3, and I can't boot without the flag nv_disable=1 (which I believe is why I can't change the resolution). I have set up my org.chameleon.Boot.plist correctly as well in case any one asks. Anyways when I boot without that flag I get stuck with AppleIntelCPUPowerManagement.kext timing out (see image). I have been trying to solve this for literally 12 hours and I have tried everything from installing the patched AppleIntelCPUPowerManagement, to installing the NullCPUPowerManegmenmt.kext. I even installed the AppleACPIPlatform Rollback to see if that would fix it and nothing I have done at all has fixed it. As mentioned before I can boot as long as I use the nv_disable=1 flag but it would be nice to use this at a nicer resolution. Also I do have drivers for my GPU (GTX 750ti) installed and it is detected correctly by the system. I am completely stuck and I have no idea what else to try so any help would be much appreciated! Image of where I get stuck: https://drive.google.com/file/d/0B4ZVlmeZ7NFnUnlRMHloNURPSGs/view?usp=sharing Thanks in advance!!
  21. thedubiousdubber

    Boot Screen Issues

    So I'm new to clover. I've used Chameleon in the past, but switched over by doing a clean install of Yosemite on my z77-ds3h. I have everything working so far (as far as I can tell), but the boot screen shows up in a super low resolution. I have my monitor connected to my GTX 760 and set for 1080p. I set graphics to display 1920x1080, which it does, but it does not do so until the login screen. I am using the Yosemite theme from the wiki which supports higher resolutions, but for some reason mine is showing up in something terrible like 800x600 maybe? Not sure, but it looks awful and hoping for some help on how to fix. I tried searching but haven't come up with any relevant information.
  22. UPDATE: Read my second post as I figured this out, but will leave this post here in case others are searching the same issues later... Hey guys and Gals, Firstly, thanks for all your insight, time and hard work. Im new here as a member, but have been reading for about a year off and on. I asked this question in another post, but it is an older thread that mostly deals with Metal Installs as opposed to Virtual VMWare etc. I am hoping someone can give me a definitive YES?NO can/can't be done answer or even better, a solution. So, here is my question Now, weird issue. I have Host Toshiba Ultrabook U840W 21:9 1792 x 768 resolution (yes, thats correct res) running Windows 8.1 pro x64, Dual Core, 6gb Ram (host) VMWare WS 11+Tools and Un-locker 2.0.4 (should be titled enabler I think, the name suggests hacked when really, it just enables VMWare to load OSX into preset menu) I have two guest VM's; Mavericks 10.9.5 and Yosemite 10.10 PROBLEM -Yosemite OOB VMDK install worked great, full screen resolution at 1792 x 768 with no tinkering required at all. Slow and unreliable when updated security patches are installed. Beamoff Tool solves most of the lag and speed issues. (BUT NO other available options available in display options-weird), -Mavericks 10.9 VMDK install, Un-locker 2.0.4, VM Tools gets maximum 1366 x 768 as a pre-installed option in Display prefs. So, I love Yosemite's look and feel, BUT the mavericks install leaves Yosemite wanting; In speed, Video, Ram Usage etc. The Mavericks install is fantastically fast, stable and only has this one annoying screen limitation issue. Hence, until I get a faster Laptop, Mavericks will be my choice of VM [ for now ] ATTEMPTED FIXES: -SwitchResX: Continual "Not Installed' error and 'Need Reboot' etc that everyone gets attempting to create custom display settings. -Contacted Stephane at SwitchResX (Basically told the issue is not with SwitchResX, but rather my Operating System, despite making numerous mistakes about what order I was running the VM environment in. I.E kept stating that Mac OS X as a host is not supported by VMWare and other such silly statements. [ Reminder: I'm on Windows host anyway and they do support VMWare in mac. I.E Fusion ] -I have read NOTEBOOK Forum and relevant guides (there are non on Toshiba u840W though)as well as a postings over at TonyMacX regarding creating Plist EDID fixes in PListPro and Xcode etc. -Uninstall_Re-install of all softwares -Third Party SVGA Driver (Not recommended unless from a very trusted source as many online versions crashed a number of my installs, Thanks goodness for VM software!) I used this guide to confirm EDID on Yosemite/Mavericks and BOTH VM's use the same Plist details as listed below. They show up as the generic: DisplayProductID" = 1815 DisplayVendorID" = 1970170734 IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/display@F/VMwareGfx/VMwareFramebuffer/display0/AppleDisplay-756e6b6e-717 So my confusion is this, why does Resolution in Yosemite work perfectly at 1792 x 768 OOB, with the same VMWare+Tools+Unlocker preferences and settings, yet Mavericks 10.9 is stuck at 1366 x 768 despite Plist being the same in both VM Op's? I think I have a case of working on something too long, and forgetting what i have tried and not tried etc. Maybe someone has a simple solution for this, but i know that with my 21:9 1792 x 768 resolution, its a challenge, BUT Yosemite knew straight away to use the Host settings? Thanks ahead of time people, and just so you know, I am a helper too and contribute to posts (Toshiba) etc, so i will pay it forward. Cheers from Australia.... Shane
  23. I managed to install OS X after some problems, but the maximum resolution I can set is 1024 x 768, and, in "About This Mac" it says I only have 3 MB display graphics memory. I actually have 2 Sapphire R9 290s, which each have 4 GB memory, so what's the problem here, and how can I fix it? Thanks,
  24. Hi, I'm trying to install Snow Leopard on my PC (I have an AMD CPU so can't install Lion) but my resolution is stuck at 1024x768 which is a long way off my monitor at 1920x1200. I have a 560ti which I have read is not compatible with Snow Leopard and needs Lion but this is out of the option due to the lack of AMD kernel. Is it possible to either get my 560ti working in Snow Leopard or at least increase the resolution to 1920x1200? I have tried setting "GraphicsMode"=1920x1200x32 at the bootloader but when I get into OSX, the resolution has decreased to 1600x1200. Any help would be greatly appreciated
  25. Hey, I got my hackintosh (almost) completely running, it just freezes when I put a USB Stick/external HDD in my front USB 3 ports and I got a problem with my resolution. So my monitors resolution is 1680x1050, but in system preferences I can only change it to 1280x1024 (or some lower resolutions). The weird thing: Running my system with 1280x1024 looks just fine, as the resolution was the right one, the only situations I realize the resolution is wrong is when watching videos or streams in full screen or playing games. I tried to use SwitchResX to change it to 1680x1050, but then my monitor would turn black and show an error that the resolution is wrong, but it's the same resolution as it should be. Also, when booting with GraphicsMode=1680x1050 or GraphicsMode=1680x1050x32 nothing changes. My Graphics card is also perfectly recognized by my hackintosh (as seen in the screenshot, I'm sorry my system is running in german). I am currently running 10.9.1. My monitor is connected to my dvi port at the PC, since my monitor only has a VGA cable I use a VGA to DVI adapter. When I plug my monitor into the VGA port I can only use my onboard Intel HD 4000, and have to change my BIOS to Onboard Graphics instead of PCI Express E.
×