Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About realityiswhere

  • Rank
    Insanely Unreal

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Outskirts of insanity
  1. realityiswhere

    IRC Page?

    the network is 'irc.moofspeak.net', standard irc port 6667 works fine, port 6697 is for SSL (secure), but you need to have 'allow self-signed certificates' enabled for that. the channel is #osx86 the irc is *NOT*, i repeat, *NOT* run by insanelymac anymore, it is completely separate, and if someone misbehaves, the mods are at their own discretion to remove you, and complaining about it on the forum will not have any effect. the rules are listed on the same server as the bot, spotlight.
  2. myhack does nothing to firmware. boot to the snow leopard disc using either 'c' or 'option' held down on the keyboard. in one of the menus there'll be a 'startup disk', use it to boot to the installed OS on the hard drive, from within the installed OS re-bless the hard drive like normal. sudo bless --folder=/Volumes/[yourhddname] --file=/Volumes/[yourhddname]/System/Library/boot.efi --setBoot these GUI tools like myhack are idiotic, just FYI.
  3. realityiswhere

    Migrated from Linux - Only One (Big) Problem

    1. using a static ip address has nothing to do with the router. you can just assign yourself a static IP from within the OS. if you can't get at the router then you're lucky it even worked in the first place, the only thing I can think of is assign static IPs on both your ubuntu and macbook installs, but make sure you're assigning the static one on the macbook as what the Ubuntu one used to be, and then change the port on the ubuntu install in the transmission client, and use that port only on the macbook. you can only move the torrent that you downloaded from the torrent directory and keep sharing it if you right click the torrent in the transmission window, there should be a "move data file" or something similar, that way both the torrent client and the OS know it was moved, otherwise if you just cut/paste it then the transmission client has no data to upload cause it's not looking in the right place.
  4. realityiswhere

    Migrated from Linux - Only One (Big) Problem

    1. ROFL [Explanation, basic networking]: the port is an incoming port, not an outgoing port. So your router is forwarding the port from the internet to your Ubuntu laptop, forwarding to the Ubuntu laptop's specific internal IP address on your LAN. So you *NEED* to use another port on your Macbook that's different from the one your Ubuntu laptop is working because your router can only forward that port to one specific internal LAN IP at any given moment. What you think makes no sense makes perfect sense because the router can only forward a specific port to one IP at a time 2. In order to continue seeding you should be keeping the .torrent file with the actual torrent (in case you move computers/change filesystems/back it up and intend on seeding later, any number of reasons), if you ever intend on seeding that particular torrent again you should always keep the original .torrent file.
  5. realityiswhere

    Migrated from Linux - Only One (Big) Problem

    [The below comments are my own and should be taken as such, not affiliated with InsanelyMac as I no longer approve of the way this site is run) It sounds like you just to add the .torrent files back into the Transmission client again. Let me further clarify: Torrents are organized in several ways, always by special servers called trackers which contact torrent clients (Transmission) for ratio reporting and the like. When a torrent is created, the person imports the file/files to be uploaded and a special ".torrent" (notice the dot) file is created. This .torrent file is very small, and represents the file you're downloading. Basically you're downloading a file (the .torrent), so that file gets imported into the Transmission client, which downloads the "real" torrent, ie: the files you want. So if you were to download say a Ubuntu livecd, you would download the .torrent file, which would then be downloaded by your web browser, which you would import into your Transmission client for the real Ubuntu .iso to be downloaded. So, to clarify, it sounds like you just had the .torrents being opened directly with Transmission when you downloaded them, in order to re-import the Torrents into your new Transmission client on OS X, you would just need to re-add the original .torrent files to Transmission so it can recognize the material as being previously downloaded, it'll compare hashes, verify the integrity of the download to confirm you've indeed gotten all of it, and allow you to upload again. On the matter of not uploading: It looks like you have a ratio of 0.06 on the file you downloaded, meaning out of 100% of the file you have listed, so far you've re-uploaded 0.06% of that, so upload is technically working, it could just be a not well wanted Torrent, or you could have closed ports (which is an entirely different topic). Hopefully that makes some sense, and you have the original .torrent files of the torrents you're trying to re-add to your client.
  6. realityiswhere

    Asus Rampage II Gene Hackintosh

    I have a friend with this board, I set up Snow for him and can confirm it absolutely rocks. this bootcd (which I just uploaded) can be used to boot it so you don't need to do the long leopard installation process, it'll boot snow leopard directly.
  7. realityiswhere

    Diablo II on the Dell Mini 10v

    Try asking Blizzard to re-compile the binary as Intel.. Diablo II was only ever released on the Mac as a PPC binary. The game is being used through an emulation layer for PPC - Intel code called Rosetta.. it's not a native Intel game. That's why it's slow.
  8. realityiswhere

    What the hell..

    Look at the TLD (Top-Level Domain) of the website in question, it's owned by Do1. They're the ones responsible for the.. err.. 'improvements' to the IM interface. Fubra hosts, Do1 designs. It's their test site which hasn't been locked down properly, and was used to give admins/mods a preview of the changes before they went into effect.
  9. The Moofspeak IRC is not related to InsanelyMac. InsanelyMac links to moofspeak (where #osx86 is located), nothing more.
  10. realityiswhere

    Video Converstion

    Handbrake - Free, awesome movie conversion software. Can rip dvds directly to .avi. If you can find it, VisualHub does a good job too. (Out of development and since renamed to TranscoderRedux, but VisualHub itself still works well if you can find it).
  11. realityiswhere

    What about new releases? OSx86 dieing?

    The com.apple.Boot.plist I posted is from my Macbook, which is why it doesn't look like yours.. You don't add it to the boot-132 cd, you add it to the one in /Library/Preferences/SystemConfiguration/ (that you posted above) after you install, just add it after the last but before the . 74c20456e67696e65205b4546495d</string> <key>boot-uuid</key> <string>611CA259-411B-3D1F-BAB5-AEA4F8551297</string> </dict> </plist>
  12. realityiswhere

    What about new releases? OSx86 dieing?

    The one from en0 (00:1F:C6:4E:D0:2E) goes into the UUID kext, in the string under the UUID-key line of the Info.plist (ie replace exactly what you highlighted above in the top right textedit window, with 001FC64ED02E ) The UUID line from Disk Utility goes into the com.apple.Boot.plist Kernel mach_kernel Kernel Flags boot-uuid 611CA259-411B-3D1F-BAB5-AEA4F8551297
  13. realityiswhere

    Where did my thread go!?

    1. reeg, not all OSx86 dvds have that software update utility you were asking about. it's an ancient, and out of date utility that no one uses anymore since the Voodoo kernel was released. This is easily findable information, yes, on these forums. 2. You posted it in the wrong section. You put it in the "New Releases and Updates" (it's neither), just like you posted this one, which I moved to the "Forum Information and Feedback" section (posts are better responded to when in the section they should be in). 3. You bumped it after 2 hours, this is extremely bad forum etiquette, and if the first two reasons weren't enough to merit the deletion of the thread, this one certainly is. (for 'rest assured son') "Mods" (as in moderators) cannot do anything like this, it's an Admin only capability. Send a PM to Ed or ComplexMind.
  14. realityiswhere

    What about new releases? OSx86 dieing?

    DSDT Patching: Most computers have BIOS's. Exceptions to this would be Macs which use EFI. This Differentiated System Descriptor Table contains the Differentiated Definition Block, which supplies the information and configuration information about the base system. It is always inserted into the ACPI Namespace by the OS at boot time. Hardware vendors can include support for different OS's (even different versions of the same OS, like Windows). When you patch your DSDT, you are not editing the BIOS itself, but it's the same effect as if you were, you are fixing errors/settings that are not optimal for your OS, and OS X can even have 'drivers' set in the DSDT so you don't need a kext/dev-prop strings. Device Property Strings: Sometimes falsely called EFI strings, or GFX strings, they are used to inject information into the IORegistry of OS X, just like kext-based injectors. They are less flexible, and less easily edited than kexts. Injector Kexts: The OS is run by the kernel, the software equivalent of a processor, every single instruction the OS receives or gives is sent through and by the kernel. In Linux, and in OS X, Kernel EXTensions (kexts, and kernel modules in Linux) provide extra device driver support for things that aren't built into the kernel by default. They provide extra functionality, usually always for a hardware piece, but sometimes just for software. Correct. Plists are property lists, they store serialized objects, mostly user settings, and they're not just for kexts, you can find them inside apps as well. They're found inside of the .kext itself. You can use the GUI to get there. Right click the .kext, click "Show Package Contents". Double click the Contents folder (not all of them have this folder), and the Info.plist is there. To edit it, you have to be root, so use the terminal (I always use nano) and type: sudo nano /System/Library/Extensions/Example.kext/Contents/Info.plist . Alternatively, you can open Text Edit as root. sudo open -a textedit /System/Library/Extensions/Example.kext/Contents/Info.plist (offhand I can't remember if textedit is one word or too, I'm in Linux atm, not OS X. If it is two words, then it's text\ edit ) UUID: You already have a UUID, it's on the partition. It's just a matter of getting the OS to see it in all the places it needs to. Right click UUID.kext > show package contents Edit info plist and change 0016174EE065 to your MAC address (without colons) under: IOKitPersonalities Generic CFBundleIdentifier com.free.driver.UUID IOClass UUID IOMatchCategory UUID IOProviderClass IOPlatformExpertDevice IOResourceMatch SMBIOS UUID-key 00000000-0000-1000-8000-0016174EE065 find your MAC address by typing ifconfig -a . it's a series of 6 sections of 2 numbers/letters, (00:00:00:00:00:00) representing the hardware identifier of your network card. Save and load the kext, after repairing permissions properly (not with disk utility). sudo chown -R root:wheel /Extra/Extensions/UUID.kext && sudo chmod -R 755 /Extra/Extensions/UUID.kext && sudo kextload -t /Extra/Extensions/UUID.kext Replace /Extra/Extensions with /System/Library/Extensions if you choose to use that directory instead. You can also use a dev-prop string in your com.apple.Boot.plist to assist this process. To determine your UUID open Disk Utility select your OS X disk and click on info, or right click>info, and look for Universal Unique Identifier. Copy this number and paste it into a boot-uuid=string in your boot.plist i.e. Code: <key>boot-uuid</key> <string>PasteHere</string> ----------------------------------------- Learning is good, the graphical version of slimbuild/uinstaller do not support learning.
  15. realityiswhere

    What about new releases? OSx86 dieing?

    All it takes is a little searching. There's a premade boot-132 .iso for your motherboard, on this page, specifically the link to it is here. For the EP45-UD3R. It's excellent that you want to learn however, the main two boot-132 threads are the one I linked to above (for .iso's) and this one for general info.