Jump to content


  • Content count

  • Joined

  • Last visited

About anomaly256

  • Rank
    InsanelyMac Protégé
  1. nmap for iphone

    Unfortunately my hosting provider reset my VPS and this tarball was lost. Since I built this package a newer version of nmap has been released aswell. Today or tomorrow I'll rebuild the latest and put it back on my site, aswell as contributing it to the Cydia repo and possibly Apptapp if I cbf'd figuring out Apptapp's packaging method. I'll also provide the Makefile used and such as requested by a few people so that others can maintain this if they choose to.
  2. nmap for iphone

    I got bored and so decided to get the unofficial sdk up and running. And then having done that I commenced trying to find apps to port. I looked around and didn't find nmap in any of the main repos so thought I'd tar it up and post it here. Tested on 1.1.2. Let me know if you have problems on other versions or on the ipods and I'll see if I can get them going. Also, if you cbf'd, feel free to put it into an installer.app repo. I cbf'd. It includes the python bindings but I haven't played with them. It does not include nmapfe. It untar's to opt/iphone/ Enjoy. 1.6mb (but the forum still complains when I try to attach it, claiming it's too large)
  3. i think i saw earlier in the thread someone mentioned it's a passworded dmg and details are in the accompanying txt file? Edit: or perhaps it was in another thread.. but yer..
  4. just FYI's, All finals are 'internal candidates' before being finals. Or at least, they should be. In a proper commercial dev environment, nothing should change between an RC being approved to be final and final release apart from the printing on the box, or you risk breaking something on release which makes you look very very foolish.
  5. Personally I think it's stupid the way Parallels have their product testing for bootability from native partitions and only serves as a warning that they don't really know what they're doing in this regard, and to not expect anything significant from this in the near future. I mean, I've been coding for a long time now, many years, but I would think the parallels devs know more than I. However, even I can understand this really simple premise: OSX can read the partition, bootcamp or not, mbr or guid or not. Therefore it can read the boot record. Therefore ANY vm software of ANY kind can and should boot ANY x86 os from it just by using the OSX /dev/disk* devices. PERIOD. If the Parallels coders can't make this really simple logical connection that anyone with half a clue would realize is the appropriate path to take, then I have exactly 0 faith in them ever getting it to work. The fact that they are relying on the bootcamp assistant to ascertain bootability is just retarded, and needlessly limiting. ie: you'll never be able to boot linux from a native partition in this manner. And the part that REALLY gets me is, the current stupid path they've chosen, is the harder of the 2! WHYYYYYYYYYYYY It makes no sense. So, I give up. Parallels ftg. NB: Meanwhile, XEN is chugging along quite nicely And starting OSX as a domU can't be far away. (I'm sure hackintosh versions of OSX are already bootable in this manner!)
  6. Well, it turns out I had xen working all along! The issue I was having is something related to how the combination of grub, acpi, and xen bring the core duo's second core online in the macbook pro. Hitting enter at the grub boot menu causes the second core not to wake up and xen's dom0 kernel to panic. However, hitting the right arrow to select the boot option works and boots without issue! I now have a dom0 and domU kernel booted. Just need to set up the usbhid stuff to get the keyboard working in it and I'll try XP. Also, as I stated in my previous post, refit, bootcamp, and grub ARE NOT replacements for eachother. In fact they are COMPLEMENTARY in many ways. The amount of people saying 'bootcamp is better than grub and refit' is really alarming since grub RELIES on bootcamp, and rEFIt makes using bootcamp EVEN BETTER than bootcamp alone. Please, if you don't understand the place of these utilities, don't make comments like that. They can be very misleading to people trying to find factual information. So, just follow the XEN documentation as usual, except apply the proper macbook/macbook pro patches to the xen linux kernel source (to enable kb, etc), then hit RIGHT instead of ENTER at the boot menu and all should be good. Happy XENing!
  7. I have a GUID partitioned drive, repartitioned with bootcamp, and it's still greyed out If anyone has a .pvs from a working 'bootcamp' parallels vm, I'd like to see what the entries are for the 'Disk 0:0' section on the odd chance it's possible to force it to try loading a given partition
  8. I got the xen hypervisor kernel running ok, but the dom0 kernel has an issue and forces a reboot. However, this all occurs waaay too fast to be able to read what the problem is, and since there's no serial ports on a macbook pro I have no way of trapping this output. Any suggestions on how i could capture it? Tried cameras but all my digicams are crappy 15fps, far too slow. When I'm around broadband next I'll grab netbsd and try it for the dom0. Don't know how this will go with hardware support for the mbp though Pretty sure I read somewhere that netbsd could be used for the dom0...
  9. Well, macbook PROs have 100~120gb at least. Mbootpack will let you combine multiple kernels into a single image specifically for achieving the likes of booting xen with lilo and other non-multiboot compatible bootloaders. Going to give it a go today anyway for at least xp and linux. OSX itself might be a different story? (ps: my current setup is refit -> bootcamp -> grub/lilo for anything linux anyway (to enable the mmapped ati vbios image), so I don't see how bootcamp or refit can be considered replacements for the bootloader or for eachother)
  10. -Archive- Macefix86 2006 -Archive-

    I'm on macspeak now. Which chan?
  11. -Archive- Macefix86 2006 -Archive-

    Hi, I've written a little python script (thank you intel/tiano for the python port!) that searches the output of dh -v for ImageBase/ImageSize and then outputs a .nsh that uses dmem to dump the entries to disk, then converts the canonical hex output to binary grabbing the names from PdbFileName. So far I've come across 106 .efi files in my macbook pro's EFI env. Of most note are probably these: abomination:~/src/efirip/out anomaly$ ls *Legacy* AppleLegacyStartup.efi Legacy8259.efi LegacyBootFS.efi LegacyMetronome.efi However a couple others look like they may be pertinant to the osx86 project. (Is it possible the CSM consists solely of these files or would portions of it still reside elsewhere? I've dumped the 'bios' and 'vbios' from inside bootcamp but can't find anything matching them in either the dumped .efi's or a complete firmware image dump. Also bootcamp appears to set the first 'boot option' entry to point to the start of the firmware with the filename of '?', for example using bcfg to list boot options has "01. MemMap(11:FFE00000-FFF9FFFF)/? "Mac OS X" OPT" (yes, it says osx in there when booting xp, swaps the memmap reference for a partition reference when booting osx), how does this tell EFI to init the CSM?) I'll attach a full bootcamp'd dh listing aswell as a file listing of the dumped efis. Let me know if anyone wants these files to look at, or the script itself (real messy and jury rigged right now but I'll clean it up if people want it). Also, does anyone know how to start these up manually? AppleLegacyStartup appears to be a driver but looks for a LegacyBoot handle that doesn't appear to exist on any devices... can you force this protocol to appear bound to a device even when it's not? list1.txt dh.txt
  12. macbook pro trackpad under X11/linux

    Heh, I'll take the lack of response as a 'no' :pirate2:
  13. -Archive- Macefix86 2006 -Archive-

    As manchmod said, I'm using rEFIt to run the efi shell (aswell as other things). I've been pretty busy at work lately, a deadline for our current project is getting close so I haven't had much free time to play around with efi. However I have some free time coming up soon and will gladly devote my time to trying to pull this stuff apart I'll post anything I find here. One thing in particular I would like to pull out of the firmware is the ATI 'vbios' driver that bootcamp uses so I can preload it for enabling 3d acceleration when booting using elilo instead of having to boot standard lilo through bootcamp and losing the framebuffer support
  14. -Archive- Macefix86 2006 -Archive-

    I've managed to dump the output from the drivers command using the efi shell on my macbook pro 15", however, for some reason it truncates the output to an 80 column width, despite having run 'mode 180 47' before hand. output as follows, let me know if you need anything else. more than happy to experiment. EDIT: Output attached to post as DriversDump.rtf In order to get the -full- guid image names, here's the output from 'dh' for the device handles. these map to the start of the image names from the previous 'drivers' output: EDIT: Output attached to post as HandlesDump.rtf DriverDump.txt HandlesDump.txt
  15. macbook pro trackpad under X11/linux

    Hi, After some playing around I've managed to get working tripple boot happening without chainloading from ntldr. Hardware acceleration works perfectly under both xp and gentoo linux. However, I seem to be hitting a snag trying to get the trackpad working under X11/Linux. X11 seems to detect it and loads a driver, however it's all... wonky.. moving up and down on the trackpad makes the cursor go sideways, and clicking makes it move up, and moving my finger sideways makes it select and deselect while scrolling... Anyone else managed a workaround for this? I tried searching these forums for an answer but regardless of how simplistic my search was the forums claimed 0 search results. Thanks in advance