Ophcrack Live Cd Windows 10
Basilio Jarvis
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.
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)
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?
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. :)
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.
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:
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.
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).
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.
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.
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 ??
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
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.
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!
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.)
d3342ee215