Ophcrack and Kon-Boot Multipass problems.

[Ekoh]

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! -EOT" and then an error stating I do not have enough physical memory to load Windows Boot Manager. I've tried downloading another floppy image, but no luck.

Issues with Ophcrack: This issue only appears on one of the three machines, so I assume it is a BIOS configuration error on my part or some sort of video card incompatibility. On this box Ophcrack loads to the "Configure X" screen right before the Slitaz login, but instead of offering numerous resolutions it offers: "xterm 800x600x16" "xorg Installer Xorg" and "quit Quitter". Obviously none of these have worked. I have tried serveral different LiveCD isos from different mirrors on their site but none have worked on the machine thus far.

I appreciate any ideas the Hak5 community has to offer :D.

Current menu.lst:

color green/black

title BackTrack 3 FINAL
root (hd0,0)
kernel /bootbt3/vmlinuz vga=0x317 ramdisk_size=6666 root=/dev/ram0 rw quiet
initrd=/bootbt3/initrd.gz
boot

title Ophcrack Live 2.3.1
kernel /boot/boot.ophcrack/bzImage rw root=/dev/null vga=normal lang=C kmap=us 
screen=1024x768x16 autologin
initrd /boot/boot.ophcrack/rootfs.gz

title Kon-Boot
map --mem /FD0-konboot-v1.1-2in1.img (fd0)
map --hook
chainloader (fd0)+1
map (hd1) (hd0)
map --hook
rootnoverify (fd0)

title Memtest86+
kernel /memdisk
initrd /memtestp.bin

title Hirens 9.9
kernel /Hirens_root/memdisk
initrd /hirens_root/boot.gz

title Trinity Rescue Kit 3.3 (default)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 vollabel=EKOHBOOT
initrd /initrd.trk

[Netshroud]

Try remove the second "map --hook" in the Kon-Boot entry.

[H@L0_F00]

Try remove the second "map --hook" in the Kon-Boot entry.

No, that's not it. It should look something similar to this (although that might not even be what's wrong with it):

title Kon-Boot
map --mem /FD0-konboot-v1.1-2in1.img (fd0)
map (hd1) (hd0)
map (hd0) (hd1)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

[Netshroud]

The hard drive mappings dont need to be hooked, and you dont need to double-map them.

[Ingo]

Just my two cents but, Ekoh you did download the floppy image of the Kon-boot, right? And it doesn't have to be extracted to your USB -device, you can just copy whole *.img to your USB's root (or where ever you want it to run from)

[H@L0_F00]

The hard drive mappings dont need to be hooked, and you dont need to double-map them.

Since when do you not need to hook them? If they aren't then the changes aren't made and the devices still show up as what they originally were.

Just my two cents but, Ekoh you did download the floppy image of the Kon-boot, right? And it doesn't have to be extracted to your USB -device, you can just copy whole *.img to your USB's root (or where ever you want it to run from)

That is what is being attempted.

[Netshroud]

Since when do you not need to hook them? If they aren't then the changes aren't made and the devices still show up as what they originally were.

"Map --hook" makes mapping changes, so that the changed (such as mounting an ISO) can be accessed from Grub, instead of only after the OS is told to boot.

[H@L0_F00]

Yeah, my mistake.

[Ekoh]

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". To remedy the problem I have been just manually mounting /sda2 and having to navigate to my tables once ophcrack loads (semi-pain). Is there anyway to change the launch.sh or some other file in order for /sda2 to mount on startup so I dont have to spend 4 minutes loading up my tables?

[AtomikNoize]

If you but the small MEMDISK file from syslinux package into the /boot folder on your usb drive, you can use this following code in your menu.lst to boot KonBoot and any other floppy disk image , no chainloading or root commands needed. :)

title KonBoot

kernel /boot/memdisk

initrd /boot/konboot.img

just be sure to put the floppy disk image in the /boot folder as well , it should work , just tested on three diff pc's.

You can find syslinux package using google or from a linux distro with memdisk in the boot folder.

[Ekoh]

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 /FD0-konboot-v1.1-2in1.img
map (hd0) (hd1)
map (hd1) (hd0)
map --hook

[AtomikNoize]

Glad My post possibly helped a little bit, but it seems strange your still having so many issues.

As Far as I am aware, after the KonBoot splash screen , and after it loads it should in fact loop back to the

Grub boot menu, this is how you then tell it to boot off the Actual Hard drive (windows) on the PC,

To boot Windows after loading Konboot, you\'ll need a second Menu entry such as

title Boot Windows off First Hard Disk after Konboot 
root (hd1,0) 
chainloader (hd1,0)+1
boot

If you Boot konBoot , then when your returned to grub , boot Windows it should work.

I just tryed again and it still works. (on my system anyway, and on Halo\'s VM )

Hope this helps.

This is what my whole menu.lst looks like , all entries work on my setup.

color green/black red/blue

timeout 120

title ---===KonBoot (Inject Konboot into Ram)===---

kernel /boot/memdisk

initrd /boot/konboot.img

title ---===Boot from HardDisk after KonBoot===---

root (hd1,0)

chainloader (hd1,0)+1

boot

[Netshroud]

Or you could just map the drives first.

[Ekoh]

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

I'm assuming the "map (hd0) (hd1)" is unnecessary since I don't really need to map the flash drive at this point...nevertheless this was successful on the restarting problem machine. On the pausing machine..it again just pauses at "Filesystem is NTFS partition" and refuses to boot into Windows.

Psychosis I'm assuming by mapping the drives first you mean something like this:

title Kon-Boot (GPC Success)
map (hd0) (hd1)
map (hd1) (hd0)
map --hook
kernel /memdisk
initrd /FD0-konboot-v1.1-2in1.img

This did not work (said something like "refuse to hook int13 becuase of empty drive map table", however mapping the drives at the end did work, on one machine (the machine that is not pausing to be specific).

[AtomikNoize]

After Reading your last post Ekoh, I decided to go and try mine on a couple different pc's , a few at my friends house and my G/F's laptop. Now im stumped as well because the three new machines i tested this on all failed to work. it did work in Halo's VM , and both my Desktop, and Laptop. My G/F's laptop was afflicted with the same "Filesystem is NTFS" than hangs. The other two at my friends house are both dell boxes, both restarted right after the Windows bootloader executed. Not a clue why .. Its only so strange because i Had it work on Two other computers and on the VM.

Maybe this has to do with certain hardware configurations , or some sort of limitations of certain BIOS's.

Hope somebody can figure this out, three days of messing around and i just realized it only works on my machines. I'm to get frustrated lol :)

[Ekoh]

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 hitting Kon-boot first. If people from the forums could throw out some other ideas on code that would boot hdd partitions, no matter how crazy/silly they are, one may work.

[AtomikNoize]

I will definitely try that on my friends dell boxes. But i was thinking mabe its a problem with KonBoot its self and the way it injects its self into the RAM , because if the system boots without Konboot, well then i would assume KonBoot is the culprit in this situation , but either way im really confused, it would be nice if there were a little more documentation on using konboot, as well as using it conjunction with grub/grub4dos. Anyone got ne links ??

Either way I ain't gonna give up until i figure this out lol..

[Netshroud]

The first thing to try is seeing if it works from a floppy or a CD. If that works, it should work from your USB.

Remember, Kon-Boot does not support 64-bit operating systems.

[H@L0_F00]

I found that Kon-Boot didn't work on a Compaq desktop. I forget the code that was given, but I think it was because it's got that "Restore Partition" or whatever they like to call it. This "Restore Partition" was actually the first partition of the hard drive and formatted as NTFS so I'm guessing that Kon-Boot tries booting the "Restore Partition," resulting in failure. I haven't tried it on any other systems except my VM and my Dell D620 which both worked fine. I'll see if I can test it on a school computer or two this week ;P

[Ekoh]

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.

[Netshroud]

You need to chainload (hd0) after mapping, not (hd0,0) or (hd0,1)

[Ekoh]

You need to chainload (hd0) after mapping, not (hd0,0) or (hd0,1)

Made no difference, still freezes up.

[nvrmnd]

I found that Kon-Boot didn't work on a Compaq desktop. I forget the code that was given, but I think it was because it's got that "Restore Partition" or whatever they like to call it. This "Restore Partition" was actually the first partition of the hard drive and formatted as NTFS so I'm guessing that Kon-Boot tries booting the "Restore Partition," resulting in failure. I haven't tried it on any other systems except my VM and my Dell D620 which both worked fine. I'll see if I can test it on a school computer or two this week ;P

I've had kon-boot not working on several branded computers. Either just hangs before the splash-screen or while detecting dummy bios. And then working on several others so, but when it works it works. Too bad you can't change the password while using it!

Some times only Kon-boot seems to work, and not like winkey pro, pc login now etc.

[~Muushi~]

Hey im very new to this~

So uhh i was just mucking around and i might know y ur kon boot isnt working properly~

well as a guess from me is that ur gldr file isnt really correct.

i had the same problem as u with the kon boot on my laptop.

and uhh all i needed to do was change it. im not so exact but i found this other

folder then got its gldr and changed it~

or maybe how you installed ur grub4dos.

like i said i really dont knnow but its a might :3

Hope i somehow helped.

[Bread870]

Hey I finally got the ophcrack to work...its so simple its silly.

Its not the cleanest/smallest setup but it works.

First, setup your usb with grub4dos (look up how to do this)

Second, copy the whole iso to the USB

Third, burn a cd/mount the iso image which is still on your computer, extract the "TABLES" folder and "md5sum" to the root of your USB (these have to be in the root in order for the program to find the tables.)

The menu.lst code is as follows:

title OphCrack 2.3.1

map (hd0,0)/ophcrack-vista-livecd.iso (hd32) <----or whatever the iso is named

map --hook

chainloader (hd32)

This mounts the image, boots the disk, and then the program searches the root for the Tables file (this gets rid of that annoying "no tables found" error on startup.

I'm trying to set it up without the iso and im sure i can...im just a little lazy...so for all you other lazy people that just want oph on you usb and are sick of trying...well...try this setup.