Jump to content


  • Content count

  • Joined

  • Last visited

About Harkoni

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Location
  1. Chain0 file can be found anywhere, it's just a general boot0 file from Mac OS X Leopard. So search for 'download boot0 leopard', something like that. For the detailed preocedure with boot0: follow step 2.2 of my guide good luck with it. Let me know if it worked out. Gtz
  2. What you describe is exactly what I have in 64 bit mode in Snow Leopard. In 32 bit mode in SL I have exact behavior as in Leopard (means works perfectly). And I have to use DSDT.aml in snow leopard (32 bit and 64 bit mode), otherwise won't boot up. BTW: concerning N mode, my speed is always 130 Mbps. When I copy something from network hard disk (Iomega) I get download speed up tot 7 MB/s, so wireless N in network card does his job.
  3. Same here, works flawless in 32 bit but not in 64 bit. I have revision 2. Shame cuz got everything working in 64 bit except for that (and ethernet which I don't use).
  4. SL on Intel DP35DP

    OK, got it almost perfect working (still not working: restart, sleep and mute sound). Don't think it makes much sense to create a complete guide because the ones which exist for Snow Leopard 10A432 10.6 are excellent. Basic guide to follow for Intel DP35DP is: (not sure linking to youtube is allowed?) After you followed all the steps on the youtube guide pay attention for next things: (only kexts necessary from this youtube guide is dsmos.kext) - use DSDTpatcher GUI 1.0 in current working Leopard to create DSDT.aml file in the root of your newly created SL partition. Without that one, starting up SL won't be possible. - when you started SL first time you'll get a KP after 1 or 2 minutes caused by spotlight (could happen when you're still busy filling in the registrtation en setup forms. No panic: just disable all drives for spotlight searching in 'system preferences' under 'private' tab as soon as you enter SL. After that rebuild kext cache (use OSX86tools) and reboot. Now it's safe to add drives to spotlight and let spotlight do his job without any KP. - extra Kexts I installed with Kext utility (the good old osx86tools won't do the job) are; voodoohda.kext (for sound), Intel82566MM.kext (for ethernet), openhaltrestart.kext, nullcpupowermanagement.kext, sleepenabler.kext (take SL version), disabler.kext (for shut down) (of course repair kext persmissions and kext cache after install with same utility) - add right video card using EFI studio. That's it for now. You've got a rock solid snow leopard working, except for sleep , restart and sound mute for the moment. UPDATE: 64 bit will be for later on; wireless network not recognized in 64 bit, known problem. Have 32 bit almost perfect, except for sleep (never use that anyway) , mute button on keyboard and have a light blue mouse pointer (repair kernel extensions permissions and reboot gives normal mouse pointer, but after another reboot, again mouse pointer is blue. (Someone knows a script or something that could repair permissions of kexts just before shut down?) THX Nycpan for giving me your modified DSDT.aml and right kexts! used kexts are: VoodooHDA.kext fakesmc.kext IOAHCIBlockStorageInjector.kext NullCPUPowerManagement.kext OpenHaltRestart.kext PlatformUUID.kext Sleepenabler.kext Intel82566MM.kext
  5. SL on Intel DP35DP

    OK, got SL working now thx to dsdtpatcher GUI by creating the unmodified dsdt.aml from my existing, working leopard to snow leopard installation partition. In 'about my mac' looks very nice; correct RAM, CPU, bus speed, USB, SATA, wireless all out of the box. 3 problems left: - GPU is now recognized as 32MB nvidia -no sound recognized - kernel panic 1-2 minutes after startup. quite annoying, trying to install something but am always to late because have to restart system. Could someone pleaz explain to me what I have to modify to avoid these KP after starting up on my DP35DP MoBo? gtz UPDATE: - quick KP was caused by spotlight, known issue. Excluding all the drives immediately after startup from indexing, and after that rebuilding kext cache, solves it. After restart, drives can be enbaled again for spotlight and spotlight also really works then. No more KP now. - (@ Nycpan) sound works: with voodoohda.kext. But aint perfect, sound is sometimes 'choppy', and audio is not given in 'about this mac', but is given in system preferences, so you can choose channel etc. Also, it's a bit quiet, so guess voodoohda will be improved in future, but is really good start, thx to voodoo team. - booting in -x64 mode simply stops after while, which doesn 't surprise me. doesn 't matter, as long -x32 is ok - initially used chameleon 1. Installed 2 RC1 but boot simply stops now, really strange, so guess stay with chameleon 1 for now. Not so fancy but works. - shut down works after installing Disabler.kext. Restart and sleep still not ok. -ethernet works after installing Intel82566MM.kext
  6. SL on Intel DP35DP

    Hi Nycpan I have almost exactly the same system, also with intel dp35dp, intel CPU, nvidia, SATA HD and DVD etc. (see signature) Could you please give a little more (critical information) on which kexts and files (e.g. uploading your dsdt.aml) you used to install and where to find these? I'll make a complete installation guide then for intel dp35dp after it works. I've been trying a lot until now, especially trying to make a suitable boot132 disc but always KP with ACPI error. So if I could install it with your method, it would help me a lot, also other people when I have the installation method guide ready. thx in advance!
  7. Ok, sorry it didn 't work. Good to know which part didn't succeed, my knowledge grows every day a little more . But as I wrote, that was the 'tricky' part, the part I wasn't sure of, the other steps I do was sure of. But yes, it's part of the game. I reinstalled OS X more than 10 times (6-7 times iDeneb) and couple of times retail. Now everything works flawless except for sleep and shut down, and it 's rock solid. But a reinstall only takes 30 min; I only start installing all the porgrams when I'm completely sure the basic system everything works. Now with snow leopard, it will all start over again . Have to buy a new (my 5th already) hard disk (50€) so my current system isn't destroyed, and trying to install SL on it. Anyway, I suggest to everyone who starts with hackintosh to search first if a retail install isn't possible. Will be much more stable if everything works and you'll be able to do all the updates without worries. Of course with a laptop things get more complicated, so iDeneb could be only solution than... BTW; what you also can try is; just install your ideneb 1.4 on your new disk (nothing more, even not kexts) and try again what I explained with time machine restore. There might be a chance that OS X is recognized and a restore is permitted now when you boot with DVD. What Time Machine does when restoring system, is simply quick erasing current partition (your fresh installed ideneb) and copy completely the system you have on Time machine external USB hard disc. This way you don't have to reinstall all your settings. If it wouldn't work, well, you lost half an hour or so and can start with a clean install again. Of course, when you start with your new system (after the movie of 'welcome') OS X asks if you want to migrate data from existing OS X: you can select Time Machine backup for that. This way, all your music, movies, mails, settings etc are kept, and all you still need to do is install your programs again (guess like adobe CS 4, office for mac etc) gtz
  8. Ok, well, I'm trying to help you out, if it doesn 't work, don't shoot me. Anyway, you won't destroy anything when doing what I'm going to write here down, in worst case everything stays like it was before. Make sure you really have the latest chameleon installed, which is chameleon 2.0 RC2 r640 !!! 1 thing I don't know, and you should to be sure of before beginning: I don't know how XP repair CD works in case things go wrong, so to make your XP partition back active. Before you start, make sure you have a XP disk and know the commands to make XP partition active. But I guess you have XP CD because you installed it recently on your new HD. When I installed OS X and everything, I messed up a lot, but was always able to repair things because I had the Vista repair disk and OS X install DVD to be able to go to DOS and Terminal to repair things... So what you need is: Your iDeneb DVD (so burned on a DVD DL to be able to boot with, guess you have that already?) your most recent Time machine backup on external USB hard disk I don't know how much experience you have with these things, so don't feel offended if I explain it like explaining something to a complete newbie; it's better to explain it clear rather than skipping steps so you get stuck from the beginning. 1. disconnect USB drive, connect your new hard drive and boot in XP, delete your current empty partition in disk management, simply right mouse button and 'erase' partition'. 2. create a compatible partition (FAT32) by applying: go to run-> cmd, and type following commands in DOS: diskpart list disk select disk X (with X number of your disk, I suppose 0) create partition primary size=Y id=af (with Y = size in MB which of course cannot be more than the free space you have on the disk after deleting your free partition just done before) 3. keep your new HD connected en reboot with you iDeneb DVD inserted. Boot from the DVD. 4. go to disk utility, select the partition you just made (and where new Mac OS X will come), select 'MAC OS X Journaled extended', give it the name you want (I wouldn't use spaces in the name, just to be sure, so use underscores instead) and click 'erase'. Shut system down. 5. connect external USB Time machine drive and reboot with still DVD inserted and still new disk connected. 6. Go to utilities and to 'put back system', something like that, the button to restore your system from Time Machine. At this point I'm not exactly sure, but you normally should be able to select Time Machine external USB as 'source' and your new created partition as 'destination'. Let it restore. 7.After this is done you can try to reboot with DVD NOT inserted anymore. It could work but think you'll get the error: "chain booting error" at startup. Use this post I made, and follow the steps in chapter 1 under the category "In case you DO HAVE a newer osx86 dvd installation disk WITH chameleon bootloader-----" After you did the codes in terminal also follow the guide under the code about making the partition (your new OS X partition) active when you have chameleon 2.0 installed. That should be it. Normally, chameleon 2.0 scans the disks and partitions at startup, so also with the new situation he should do that. Your system didn't change so that isn't a problem either (concerning kexts chameleon uses) and you have only 1 SATA disk, so this again should be disk 0, number which is automatically given by BIOS. So good luck with it, let me know if it worked. If not, still have an alternative, using Superduper which can create a bootable OS X clone, so even booable on e.g. a Firewire or USB hard disc or a new hard disc. In case it doesn't work: your new disk won't boot XP anymore, but i guess you have a repair disk for that, for simply putting your XP partition back to active? In my guide I linked before, i explain how to do that for Vista, to be honest, I'm not using XP anymore for several years, so I don't know what XP has as repair/boot up disk so you are able to go to DOS to write down the commands you also find in my little guide. gtz
  9. Hi need some more information about your system: is your mac os x leopard hackintosh (ideneb, kalyway, XxX ect.) or retail installation? in case of retail, do you have a boot132 disc? in case of hackintosh, do you boot up with Chameleon? Is chameleon installed on your os x partition or on a separate small partition? Is your first (small) original disc partitioned in GUID of MBR? If you have a windows on that same disc, it's MBR. In case you don't know, go to disc utility -> single click on the name of your small hard disc, so not on the partition name but the complete disc (for me e.g. the name is "698,6 GB SAMSUNG HD753LJ Media") and look at the bottom of your screen if it displays GUID of MBR. Can you see/access your new drive and its partitions when you're working in MAC OS X? With this information we might be able to help you out. Gtz
  10. Hi Macinized first of all many thanx again for your great noob proof tutorial and and even better noob proof Boot132 disc. Since I reinstalled my OS X (old one was iDeneb 1.3 with Voodoo but unable to update etc) things go much smoother , faster and more reliable (reliable, that's what MAC is 80% about for me). Right now everything works flawless here except for sleep, but I guess everyone has that minor problem? Haven't found an easy fix for that, only a very 'not-noob-proof' hugh terminal command solution... The things I'll tell right now is just some explanation about my experience with it, certainly not critics or a question for repair or so. Just to give you some information. When I do the job with your Macloader 5.2.1 om my separate 700MB Macloader partition and I restart I get some odd things with my normally flawless working OS X retail. (I have to delete the AppleTyMCEDriver.kext first otherwise have a kernel panic when choosing my OS X at Chameleon bootloader). Strange things are (when booting with chameleon from Macloader instead of using the Boot132.iso for DP35DP what I normally do); My 8GB DDR2 800Mhz RAM is now displayed as 8GB DDR2 667Mhz in 'about this MAC' The DVD R/RW machine isn't displayed anymore neither can be used, it's just 'gone' The boot ROM version displayed switches sometimes between a couple versions. With the boot132 it's always correct displayed as DPP3510J.0517.2009 (only my CPU speed is displayed 4Ghz but has to be 2.4GHz (have a Q6600) but I don't worry about a higher CPU speed ) Shut down doesn't work anymore, well, it shuts down, it spins down the HD etc but always ends with the well know grey screen asking to use the power button to shut down or restart. Startup is much slower. UPDATE: I installed the 10.5.8 update by the automatic software update, worked perfect. Of course after the update, had to reinstall the sound and IOnetworkfamily kext, as usual. Took me 1 minute. I tried again your macloader which is integrated with Chameleon 2 r431 bootloader. Some annoying problems mentioned above arge gone now! The number 2. (DVD gone) and number 5. (slow startup) aren't issues anymore. So from now on I use the chameleon bootloader. The only 'real' problem left stays the fact that I get the gray error screen after the shutdown/restart and some fans of the computer keep working (number 4. problem): so a bad shut down. If anyone knows a solution for that restart/ shutdown problem, I'd like to hear it! (If I use the Boot132 CD to start up there's no shutdown problem) UPDATE 2: I saw you created a new Macloader 6.2. Thx for that. I installed it, but when I copy all the kexts from your (original) boot132 kext folder there's 1 double (dsmos.kext), so I overwrote the new one with the old one. Don't know exactly what to do with the kexts already inserted in your new Macloader? Overwrite or keep them? Didn't boot up when I used the newer dsmos.kext so for now I still use the old one which works. Also the boot rom version is stable now and all the infomation (in about this mac) of CPU speed, number of cores, bus speed, total RAM , ROM version, serial number etc etc are correct now. So as summary; compared to my orginal situation with the 5 problems mentioned above it's much better now thanx to 10.5.8 update and the new chameleon bootlader (with the old macloader). Fast startup now, DVD recognized, 800MHz RAM recognized instead of 667MHz and right information in about this mac. So 4 of the 5 problems are gone. Restart works too. Only Shut down and sleep don't work, that's all. So thx MACinized and Chameleon team. With the chameleon installed I changed the 'boot' file as described by Netkas with the one PC EFIv10 to be able to boot Snow Leopard, also replaced dsmos.kext and another one with so called 'Snow leopard proof versions' but until now immediate kernel panic at startup. I installed Snow Leopard 10A380 from my OS X Leopard partition to another partition using the OSXinstall package in the hidden folder of Snow Leopard and install worked perfect, but not does the booting so far... Has anyone already succeeded on an Intel DP35DP with the new chameleon r600 to boot Snow Leopard or even dual boot Leopard and Snow Leopard? Keep up the great work and I silently really hope someone willll be able to make another perfectly working boot132.iso to boot Snow Leopard in the future, maybe something when SL is released? I just don't know enough of it do try it myself, I just have no idea if it's possible to simply change some Kexts from the current bootloader to new ones for Snow Leopard or there's much more needed? Gtz
  11. I already used GParted Live to shrink my existing Leopard retail partition so I could create an extra partition on the same HD to test Snow Leopard and the partitioning worked flawless. Just an idea, because I've been looking some time for a good, reliable and free software to do the job. BTW; still no success with the snow leopard (10A380) installation Had the same problem: For me the problem was caused by the AppleTyMCEDriver.kext. Apparently, this is a new kext in 10.5.7 and does some support for Nehalem processors in new Mac pro. Well, I don't have Nehalem so you can simply delete that kext by this command in Terminal: while sleep 1 ; do rm -rf /System/Library/Extensions/AppleTyMCEDriver.kext ; done After that panics were gone. Thx to Netkas fot the hint and the terminal command line!!
  12. First of all: many thanx to MACinized for this terrific tutorial. Worked flawless for me. Anyway, to help other noobs like out with their Intel DP35DP motherboard these were the 'difficulties' I experienced during the installation; 1. In BIOS my SATA hard disc was configured as IDE. It has to be AHCI mode to avoid the checksum error in the beginning of the booting of the BOOT132.ISO. 2. Didn 't exactly know how to burn the BOOT132 files of your Boot-132 DiscMaker. My PC didn't recognize the CD with these files as a bootable CD. Burned instead the BOOT132.iso from the link to the collection of boot132 iso and that booted perfectly! 3. My newly installed OS X Leopard had some troubles with execution of macloader.command. Got the message of not having the permission to execute that; acces denied. Had to change the permissions of the map with the commander inside. That method is explained here: http://brockwoolf.com/change-file-permissi...nal-in-mac-os-x Last problem was: My linksys wireless N PCI netwerk card is normally recognized as an Airport Extreme which makes it very easy to work with (worked already during the installation process, was connected to my wireless network). After the " macloader.command " I had the beautifull all perfectly working chameleon bootloader, but my linksys network card wasn 't recognized anymore. Got the message: no airport found, something like that. Really strange. Keep up the good work and thanx again!
  13. Which problems exactly do you mean? Those with the bootloader, windows bootloader or chameleon bootloader? My best (and seems most of the people here) have the best experiences with installations (Windows / MAC OS X) on different partitions (Windows in NTFS and OS X in HFS+ extended (journaled)) on 1 and the same hard disk.
  14. All right. Here we go. 1. How much GB are your hard disks? What I would do is: make 2 partitions on the first hard disk, one for vista and one for OS X and keep the second hard disk for data, partitioned in NTFS. Don't worry, Windows (of course) and also MAC OS X van both perfectly handle (read/write) NTFS file system (you need Paragon NTFS for MAC 7.0 for that, get that the same way as you're downloading iAtkos...). Why 2 partitions on 1 disk? I don't know much about it but read a lot of people have problems wih the windows or chameleon bootloader when OS X and Vista are on seperate disks. 2. Because you need to use a seperate partition for your OS X installation, you can simply delete that partition in Windows. After that, you'll need to repair your vista bootloader with the vista recovery disk if you used the chameleon bootloader before. It's piece of cake and fail proof, but always make sure, even at this moment already you have a vista DVD with the recovery console on it. If not, you can download it from here:http://neosmart.net/blog/2008/windows-vist...-disc-download/ and burn it on DVD. It's compatible with all languages and all versions of Vista. Needed this DVD for about 10-15 times by now. So you can always return to your vista when things go wrong. 3. You can check hardware compatibility on the OSX86 wiki project: http://wiki.osx86project.org/wiki/index.php/Main_Page Check your version and hardware under 'Hardware'. You really need to do that first to be sure that it will work on your motherboard (or that another OS X version would work better) and the kexts (= 'drivers') you need to install extra included with the DVD. I think a good version is iAtkos 5.0. Or search for iDeneb 1.3, is also good version with extra kexts included, I use that one. iAtkos 1.0 seems to be a really old version?? 4. Same here: first check all your components on osx86 project. It will really help you to find the right kexts or to choose the right kexts straight from the DVD when installing OS X. The newer the installation version, the more Kexts already included so less work(and troubles) for you after installation... 5. As long as you ALWAYS have the vista recovery disk (or even 2 in case one is unusable because of a scratch or something) burned on a CD/DVD you'll always be able to repair vista bootloader in a few simple steps without any other trouble. But make really sure when applying code in the OS X terminal window that you choose the right disk and partition number of your MAC OS X installation. In my case for OS X installation it's disk 0 (first and only disk) and partition 2 (because I had vista installed already on the HD which is the first partition, so Vista had number 1). For repairing vista bootloader of chameleon bootloader I wrote a little guide. Even when your PC of vista seems completely messed up (I've seen it all) and you're about to throw your computer out of a window, no worries, it can be fixed in a few minutes. Just make sure you read/print the guide in advance and make the preparation like always having the vista recovery disk and the OS X installation DVD with you. A installation guide will be needed too: you can find some on the OSX86 wiki page or use this one: http://inihilist.wordpress.com/2008/04/05/...and-fool-proof/ Good luck with it!
  15. I think the problem is that you used a 'logical partition' instead of a 'primary partition' for your OS X installation. You can create up to 4 primary partitions on 1 hard disk. Problem should be solved normally when installing on a primary partition. Gtz A hint; you don't have to use the 'old skool' FAT32 partiton system for using it with both operating systems. Mac OS X is pretty advanced and can perfectly read and write the newer and better NTFS partitoning. So the best thing is to partition partition 2 in NTFS and install NTFS 3G from http://macntfs-3g.blogspot.com/ in MAC OS X. It enables you to write in NTFS when using MAC OS X. It's free and opensource. A faster (and I think better program) is Paragon NTFS for mac OS X 7.0. Its not free but I sure you'll find some ways to get that program... I would also give MAC OS X a little more space in case you' re intending to use it more and more as your first operating system. And don't forget to install windows XP/vista or whatever first and only after that installation starting the MAC OS X installation. Gtz BTW; http://tgrounds.blogspot.com/2008/10/osx-l...1055-on-pc.html : is a great guide for beginners to make an installation from scratch. Good luck with it. Let me know if you succeeded. I used the same installation DVD iDeneb 1.3 as in the guide. I'm very happy with it as you can read here