Jump to content

Ekoh

Active Members
  • Content Count

    10
  • Joined

  • Last visited

About Ekoh

  • Rank
    Hackling

Recent Profile Visitors

2,475 profile views
  1. As far as TRK goes the only successful way I've been able to boot it on one partition (while I'm sure there are others) is by having the TRK iso contents on the root of your drive and not in a separate folder (in your case /Trinity). My menu entry looks like this and works well: title Trinity Rescue Kit 3.3 (default) kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 vollabel=MULTIPASS initrd /initrd.trk
  2. Ekoh

    SARDU

    Is there anyway to use SARDU in combination with other iso's? Creating a SARDU iso and booting from grub does not seem to work, but using SARDU's "Create Bootable USB" utility makes everything work fine. However, I would still like to be able to use BT3, Ophcrack and Kon-boot that are currently working on my legacy grub multipass and installing SARDU would remove everything that is currently on the drive. Would it be possible to load SARDU on another partition, say (hd0,2) and have a grub menu entry like title Boot Second Partition rootnoverify (hd0,2) chainloader +1 to boot? If not
  3. Does anyone have a working Kav Rescue Disk or Avira Rescue Disk on their multipass? I've tried using both on separate machines and both fail to work once booted up. Kav I get past the initial load screen fine, but it never makes it to the GUI. When it goes to mount my hdds it cannot find any and says something to the extent of "Please specify ROOT drive": and entering in /dev/sda1 or /dev/hda1 does not work. Avira is a similar issue. It gets into the GUI but stops at Loading Modules- 98% for about 5 minutes and then pauses at Mounting (fd0). When I open the commandline and run fdisk -l , it
  4. Good point H@L0, I forgot that one machine had a recovery partition. However, that machine did successfully boot up to the windows partition from the multipass when I did not use it with kon-boot beforehand, so I don't think thats the issue.
  5. Yeah I'm a little stumped myself. Machines that restart on the boot command seem to work well for me with title ---===Boot from HardDisk after KonBoot===--- map (hd0) (hd1) map (hd1) (hd0) map --hook root (hd0,1) chainloader (hd0,1)+1 boot I would be curious to see if it works for your friend's Dell boxes too. As for the other with "Ntfs partition" and hang..I'm really not sure what to do with that one. Surprisingly, the code did work when it was used not in conjunction with Konboot on the hanging machines ie. booting from the multipass and just hitting boot from HardDisk instead of hitt
  6. Atomik I tested your method on the two actual windows boxes. Both work fine on looping back to the grubloader but on the title Boot Windows off First Hard Disk after Konboot root (hd1,0) chainloader (hd1,0)+1 boot one of the machines pauses at "Filesystem is NTFS partition", while the other restarts instead of booting straight into Windows..which messes up Konboot. The restart issue I was able to figure out by mapping the drives instead using: title ---===Boot from HardDisk after KonBoot===--- map (hd0) (hd1) map (hd1) (hd0) map --hook root (hd0,1) chainloader (hd0,1)+1 boot
  7. Atomik thanks for the idea, unfortunately it just looped me back to the main grub page. Using a little bit of Atomik's idea and some of your others I came up with a few lines that were successful on one machine. However Hal0's VM gave me an error when I tried to use it, and the other comp just hung at "Booting UP! - EOT" like usual. Ideally I would like Kon-boot to consistently work all the comps so hopefully you all can find a flaw/fix in my partially successful code to make it successful with the other computers and VMs. Successful on 1/3 machines: title KonBoot kernel /memdisk initrd
  8. I tried all of your suggestions for kon-boot, so far no luck. The most improvement I saw was by removing the second "map --hook" line which just looped me back to the main grubloader page (if you call that improvement) all the others just gave the same result as before. And yes Ingo I am using the floppy .img and not the .iso. Quick Ophcrack side note, one of my machines that is working when I use Ophcrack is split /dev/sda1, /dev/sda2 and /dev/sda3 however on boot only /dev/sda3 mounts and not being windows partition launch.sh then gives the error, "no windows partitions with hashes found".
  9. Been having some weird issues with Kon-boot and Ophcrack on the multipass. My multipass is using grub legacy on a 16GB Patriot usb flash drive (not that the drive would make any difference). I have tested the multipass on 3 separate machines which include HAL0_F00's VM and two other windows boxes. Issues with Kon-Boot: The issues all begin when I get to the Kon-boot splash screen. Either I will get "BIOS seems to be OK." "Booting Up! - EOT" and it will just hang, or on one windows box I get something to the extent of "Dummy BIOS Seems to be in place, fixing SMAP BIOS entries" "Booting up! -E
×
×
  • Create New...