Jump to content











Photo
- - - - -

problems with kon-boot and Easy2boot


  • Please log in to reply
5 replies to this topic

#1 camelx

camelx
  • Members
  • 2 posts
  •  
    United States

Posted 24 February 2014 - 09:00 PM

This is mainly for Steve or anyone else, thanks in advance!

 

I have a 32g usb and have got most of my payloads working just fine with Steve's excellent tutorials and reading around here on this forum, thanks.

 

My problem is I can NOT get kon-boot to work from my usb.

 

I originally worked through other issues where my hiren's stuff would not detect my HDDs at all. That was all fixed with settings in my bios with IDE, legacy and even took out boot from CD/DVD and USB to boot first. I just hit F10 on my intel MOBO and now all my Hiren's utils work, DOS, etc.

 

I went through Steve's tutorial on the RMPrepUSB site to a tee, but kon-boot won't work.

 

What I get after the menu selection is just a black screen that is stuck. I do see the first couple of commands go by, then I'm dead in the water. I originally thought this was due to the USB not seeing all my HDD sata drives, but now I have the other tools seeing them just fine, like the partition tools in the DOS utils.

 

My drive where my Windows 7 install is Loc 0(Chan 0, Target 0, Lun 0), Steve, wondering based on that if I need to modify your example menu list file for that???

 

I've tried with kon-boot USB img and the Kon Floppy img, but no luck. I also tried the example in your tutorial included from this site, but no luck either.

 

Can someone please help me? not that I really have to have that tool working, but it's driving me crazy and now I have to make it work.

 

Thanks!



#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 6629 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 24 February 2014 - 09:22 PM

There are two .mnu files in e2b docs folder - one is for konboot version 2.1 which works for win7/8.

Is your Win7 install non-UEFI?

Is there anything else (other hard disk) in the system?



#3 camelx

camelx
  • Members
  • 2 posts
  •  
    United States

Posted 24 February 2014 - 11:59 PM

Thanks Steve for getting back so quickly.

 

I"m not sure if my Win 7 in UEFI or not, I don't think it is. It's Windows 7 Ultimate, my motherboard is an Intel motherboard D845WN, about 5-6 years old.

 

I did not have a setupact.log file in the c:\windows\panther dir, so could not confirm UEFI.

 

I have 4 hard drives in the system, all sata. 750g, and  3 1tb drives

My windows 7 boots from the 750g.

My DVD is also sata.

There are no IDE drives or cables hooked up.

 

I'm hoping my kon-bootfloppy file is okay. Is there a generice test img that you know works I can download to verify that is not my problem? But my guess is the  one on the Hiren's disk should be good enough.

 

I also have the Hirens DLC ISO and that kon-boot is not working either.

 

oh, btw.......I just double checked your kon 2.1 menu and it did not work for me.

 

Disk Management does not report EFI System for any of the drives.

 

Sorry for the multiple edits, after running MSinfo32, my board is a DQ965GF and I do not see a BIOS mode of UEFI.


Edited by camelx, 25 February 2014 - 12:22 AM.


#4 steve6375

steve6375

    Platinum Member

  • Developer
  • 6629 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 25 February 2014 - 11:38 AM

Not sure what the problem is. If you bought it from Kryptos Logic ($16) then they will support you.

Or try PassPass?



#5 vance003

vance003
  • Members
  • 1 posts
  •  
    United States

Posted 03 April 2015 - 02:37 PM

I realize this thread is more than a year old, but I'll post anyway, in case someone else comes across it after googling for "kon-boot black screen" (as I did).

 

I am using kon-boot 2.4, but I have run across this problem with prior versions as well. On most systems it starts fine, but occasionally I've tried it on one where I just get a black screen from it, without any splash screen. The problem, as best I can tell, arises from a routine that it's using to start drawing the splash screen. The program enters a conditional loop, but the condition is never met, so it ends up in an infinite loop. (Thank you Quaid Analyzer for helping me find this!)

 

For version 2.4 a way to solve it is to patch the image file before burning it. Using a hex editor, search the image file for the hex string:

8A E0 3C 10 75 DC

It should occur only once in the file. When you find it, change the 75 to EB. Save the file, and then commit it to the medium of your choice. When you run kon-boot, the colors on the splash screen will be wonky, but hopefully you should avoid at least this cause of a black screen.


Edited by vance003, 03 April 2015 - 02:47 PM.

  • steve6375 likes this

#6 steve6375

steve6375

    Platinum Member

  • Developer
  • 6629 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 12 April 2017 - 12:06 AM

Here is E2B menu with vance003 patch added.

iftitle [if exist $HOME$/konboot.img] KONBOOT 2.4 (with Patch for black screen issue)\nPress Enter once Kon-Boot starts to run then allow it to boot your system to Windows
errorcheck off
map --mem $HOME$/konboot.img (fd0)
# If current grub4dos root drive (UDF)(stored at 0x8280 in memory) is 0x80 (=hd0), remap (hd0) to (hd1), else do nothing
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
# If current grub4dos root drive (UDF) (stored at 0x8280 in memory) is 0x80 (=hd0), remap (hd1) (=internal hard drive) to (hd0), else do nothing
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
echo patching byte in memory...
cat --locate=\x8A\xE0\x3C\x10\x75\xDC --replace=\x8A\xE0\x3C\x10\xEB\xDC --number=1 (fd0)+0x1000 || echo ERROR: Not patched!
pause --wait=3
chainloader (fd0)+1
rootnoverify (fd0)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users