Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

pilsator

Members
  • Content count

    195
  • Joined

  • Last visited

  1. Three times yes. Booting Leopard as well as Snow Leopard is possible because of the nice chameleon feature to have different folders with different kexts for different system versions. I will copy the content of the boot partition (I created a separate partition just for the bootloader) of the eSATA hd to the boot partition of the internal hd, install chameleon on it and unplug the internal hd. That should be more safe than the bank of suisse. The lesson of this for me is that I wouldn't recommend the opensuse dvd for hybrid gpt/MBR disks. The installer promised not to touch the MBR but it did - maybe because hybrid gpt/MBR is pretty special. blackosx, now I remember an article about what happens when a computer boots that I once read. As much as I remember it performs a selftest and then accesses a certain sector on the hd where it expects code to execute. If it doesn't find anything - game over. In my case one part of this code was obviously missing. Both of my hds boot with chameleon. On the external hd I first installed windows, then chameleon, then linux with grub on the linux root partition. On the internal hd I started with chameleon 1 as much as I remember, then updated the boot-file, used asere bln's booter for some time, then installed chameleon 2. It might be a wild mixture of different components.
  2. Sorry but I don't know what code is or should be there. Is this a question for experts only or could you ask in a way that a typical apple user understands? Can I find out with gdisk? If so: which options should I choose in the main menu and the submenu? Just installed boot0hfs with the dd-command and now the machine boots again from the eSATA hd!! Thanks a lot, dmazar. Without your help hours of stupid work would have waited for me.
  3. This is the output of the new DarwinDumper version. I could try to plug the eSATA hd into a laptop running 10.7.1 and then run the package installer or install boot0hfs from the latest chameleon binaries manually. After reading your post now I will try what you suggested. This boot CD is the only one I found (well someone else found it) that works for my old ASRock G945-DVI board. I tried different boot CDs including HackBoot, nothing ever worked. I thought I could forget Snow Leopard for this board before someone on insanelymac found this CD that was made for another board. I installed some systems with it. DarwinDumper_2.1.4_Chameleon_2.0_LEO_ottokatz.zip
  4. When I boot from CD the display shows a custom boot logo, the circle of lines is rotating, then the machine seems to be stuck in a loop. The mouse pointer disappears and comes back, there is some hd and CD activity. This repeats periodically while the activity symbol stopped spinning. When I boot from CD with -v x text is displayed, dsmos arrives, then the screen turns black with a little white block in the upper left corner and it seems to be stuck in the same loop as before. The system is almost vanilla except a driver for a USB audio interface, LAN-driver and a patched AppleAzalia.kext (if I didn't forget anything). I could boot windows 7 with the boot CD without problems. Just downloaded the new DarwinDumper 2.1.4. Will run it on the desktop machine tomorrow, blackosx.
  5. On the internal disk it's Leopard. I think the latest version of 10.5. Bootloader is chameleon, I think an older version, maybe any version 1. If you want to know exactly I can check tomorrow, I'm using another computer right now (we have little heatwave and it's damn hot in my room). What I could try is to boot 10.6.8 on the eSATA hd with a boot CD and then run the package installer.
  6. I got this error message: ______________________________________________________ otto-katzs-mac-pro:boot0hfs Installation ottokatz$ sudo ./fdisk440 -f boot0 -u -y /dev/rdisk0 Password: dyld: lazy symbol binding failed: Symbol not found: ___bzero Referenced from: /Users/ottokatz/Desktop/boot0hfs Installation/./fdisk440 Expected in: /usr/lib/libSystem.B.dylib dyld: Symbol not found: ___bzero Referenced from: /Users/ottokatz/Desktop/boot0hfs Installation/./fdisk440 Expected in: /usr/lib/libSystem.B.dylib Trace/BPT trap ________________________________________________________ Maybe it has to do with the errors that occurred when I tried to extract fdisk440 and boot0 with pacifist. Now I downloaded the Chameleon 2.1svn Official Binaries. I hope I can combine the boot0hfs file from these binaries with the other chameleon files that should be already installed on the eSATA hd. No idea why there is no boot0hfs file in the .pkg-installer.
  7. I use Chameleon-2.0-r1394 because it's called "golden master", always worked for me (except the installer package problem now) and I thought I don't need the latest chameleon version for 10.6.8. As I don't have the binaries I wanted to extract the boot0hfs file and fdisk440 with pacifist. But there was no boot0hfs file, just a boot0 file but that should do the job too according to iFIRE. Both files were extracted although there was an error message. So the plan is to start terminal, navigate to the folder with boot0 and fdisk440, paste "fdisk440 -f" type space drag boot0 on the terminal window paste " -u -y /dev/rdiskX" ("X = number of the eSATA hd) hit enter enter admin password Will try tomorrow.
  8. I attached the DarwinDumper output, dmazar. The gdisk operation looks complicated, maybe dangerous. I need cold blood for that and will first fool around a little with gdisk on a laptop. Thanks for the help and patience. DarwinDumper_2.1.3_Chameleon_2.0_LEO_ottokatz.zip
  9. This is what gdisk reported for the external disk: _________________________________ Partition table scan MBR: hybrid BSD: not present APM: not present GPT: present Found valid GPT with hybrid MBR; using GPT __________________________________ When I type "v" for "verify disk" it puts out: No problems found.
  10. Thanks for responding. I forgot to mention that I already reinstalled Chameleon - with a .pkg-installer, this simple method always worked for me. That didn't change anything. Yes, I can see all mac partitions when I boot from the internal hd. Now I will google for Rod Smith's gdisk.
  11. I used this system for maybe two years without issues. The whole thing is on an eSATA hd, hybrid gpt/MBR format, 11 partitions, Chameleon on a separate partition along with the extra folder, OSX for everyday use, another OSX for emergency cases, Linux with separate home-partition and Windows 7 64 Bit. I wanted to install a new Linux, chose open suse 12.1 64 Bit and downloaded the dvd. I knew I would have to fix the fake MBR-partition table with gptsync afterwards to get windows back. After choosing several install options the installer reported that he was going to format the 2 linux partitions that he found as ext4, use one as root partition, the other one as home partition, use the existing swap partition and that he had detected a gpt hd, so he would install grub to the linux root partition and leave the MBR untouched. That sounded good for me, so I hit enter. Installation was finished, but after reboot I just saw a blinking cursor. That made me think that the wrong partition might be marked as active. So I first fixed the faked MBR partition-table with gptsync and then marked the chameleon partition as active. Again the blinking cursor after reboot. Marked the OSX partition that was part of the faked MBR as active. Blinking cursor after reboot, then: "Error. No operating system found." Maybe i should have unplugged the internal hd before reinstalling linux? Too late. (OSX on the internal hd still boots, so does windows 7 via chameleon if I choose to boot from the internal hd.) There might be just one or two bits in the wrong place. Do I really have to reinstall everything from scratch?
  12. I suppose before running the ./finalize-command you have to navigate to a certain directory in the terminal. Right? I didn't try because I didn't buy the board yet. Could you be so kind to describe the process for someone who is not really comfortable with the terminal but made it to create the install stick. Percybut, John Cashs Guide has already been upped by WTSNZ (with some modifications for this board): http://dl.dropbox.co...758/install.zip
  13. I copied the 'install'-folder and the InstallESD.dmg to the desktop. When i paste 'install/mkboot /Volumes/-volumetoinstallML' into terminal, terminal responds: -bash: install/mkboot: No such file or directory. That can be fixed by dragging the 'mkboot'-script on the terminal-window, hitting space and pasting '/Volumes/-volumetoinstallML' in the same line. Now terminal seems to find the 'mkboot'-script but not the InstallESD.dmg. It responds: InstallESD.dmg: No such file Usage: mkboot ‹Target volume› I tried this under 10.7.4, booted from a USB 3.0 hd. The terminal and me, a sad story. Edit: found this in lofen's thread (http://www.insanelym...howtopic=280420): It looks like the error is caused by being in the wrong directory. Make sure you copied the "install" folder and "InstallESD.dmg" file to the desktop, or at least put them in the same directory. Then in terminal, you want to go to where you put them. Assuming the files are in your Desktop directory, in Terminal I did the following: ~$ cd Desktop/ ~/Desktop$ ls InstallESD.dmg My Boot Camp install ~/Desktop$ sudo install/mkboot /Volumes/USB ....................................................................... He named the install stick USB instead of ML. He said that firewire works out of the box. Looks a little bit frightening but I will try tomorrow. edit2: worked for me, install stick done.
  14. Very useful guide, thanks. One question: does firewire work out of the box? Or, if not: is there a driver to make it work? I'm in doubt whether to choose this board or the cheaper DS3H plus firewire card with Texas Instruments chipset. I don't need a highend overclocker board but if you consider the price for the card and the better build quality and better cooling of the UD5H it might be the better choice.
  15. Virus eingefangen?

    Ich hatte den gleichen Verdacht und wie gesagt deshalb von einer USB-Platte gebootet, die daraufhin auf einmal auch schwer gezickt hat, was sie vorher nie gemacht hatte. Die Standardplatte ist via eSata angeschlossen, da gibt es nicht selten Kabelprobleme, hat es auch schon gegeben, aber das habe ich mit Smart Tools geprüft und mit der Hardware einschliesslich Kabel und fest sitzenden und nicht wackelnden Steckern scheint alles in Ordnung zu sein. Ich kann mir demnächst die desinfect DVD ausleihen, vielleicht finde ich die auch im Netz. Keine Ahnung ob damit auch OSX Viren aufzuspüren sind, aber versuchen kann ich es ja mal.
×