[wgjhstt247]

For the life of me, I can't figure out how to get syslinux to boot UBCD4WIN from my 16GB (Fat32) flash drive. I've installed syslinux, it boots the menu. When I select the Ultimate boot cd for windows the screen goes black with a blinking cursor in the upper left part of the screen. Nothing happens after that. I've tried to chainload the bootsect file with no avail. ubcd4win.bss that's included with the build is for a fat16 flash drive, but there is none for a fat32 flash drive. I've used UBUSB and it works (except for the PreLogon error that's common to Vista builds). However, I do not want the grub4dos bootloader. Can someone help me figure this out? I've been searching on the forums for a couple of days now and nothing seems to work. There is no documentation anywhere on how to change the ubcd4win.bss from Fat16 to Fat32. Please help. Thank you!

[cdob]

Use a current syslinux project.
Chainload the file setupldr.bin.

LABEL UBCD4Win
  MENU LABEL Launch "The Ultimate Boot CD for Windows"
  COM32 chain.c32
  APPEND ntldr=/minint/SETUPLDR.BIN 
  TEXT HELP
  Runs a pre-installed Windows environment, loaded with diagnostic tools.
  ENDTEXT

[wgjhstt247]

With the most current UBCD4Win the winint folder doesn't exist, but the i386 does. I've tried chainloading the setupldr.bin in the i386 folder with no luck. Thanks for the reply though.
Here's what the command returns to the console:

Booting...
CHAINLOAD Failed!
boot:

Here's what I did to create the bootable USB drive:
1) Format using HP Format Tool - Full Format; Fat32
2) Copied all the built files over from the "BartPE" folder to the UFD using Windows Explorer
3) Ran the command: syslinux -ma f:
4) Copied the most recent chain.c32 from the syslinux folder to the UFD/syslinux folder
5) Changed the syslinux.cfg to result in booting UBCD4WIN (Fails every time to boot UBCD4WIN)

This post has been edited by wgjhstt247: 07 November 2009 - 09:26 AM

[cdob]

wgjhstt247, on 07 November 2009 - 09:12 AM, said:

I've tried chainloading the setupldr.bin in the i386 folder with no luck.

Well, I386 won't work at a USB drive.
Minint does work. Rename I386 and copy ntdetect.com to root directory.

Try a old syslinux 3.75

LABEL UBCD4Win
  MENU LABEL Launch "The Ultimate Boot CD for Windows - chain.c32"
  KERNEL chain.c32 
  APPEND hd0 1 ntldr=/minint/SETUPLDR.BIN
  TEXT HELP
  Runs a pre-installed Windows environment, loaded with diagnostic tools.
  ENDTEXT

[wgjhstt247]

cdob, on 07 November 2009 - 10:54 AM, said:

wgjhstt247, on 07 November 2009 - 09:12 AM, said:

I've tried chainloading the setupldr.bin in the i386 folder with no luck.

Well, I386 won't work at a USB drive.
Minint does work. Rename I386 and copy ntdetect.com to root directory.

Try a old syslinux 3.75

LABEL UBCD4Win
  MENU LABEL Launch "The Ultimate Boot CD for Windows - chain.c32"
  KERNEL chain.c32 
  APPEND hd0 1 ntldr=/minint/SETUPLDR.BIN
  TEXT HELP
  Runs a pre-installed Windows environment, loaded with diagnostic tools.
  ENDTEXT

So here's what I did. I let UBUSB.exe copy the files to the UFD, and it made the changes you suggested automatically. I installed the older version of syslinux using "syslinux -ma -d syslinux f:" Then I booted the UFD to the syslinux menu and it states that it "cannot read the Master Boot record" when booted with "chain.c32 ntldr=/minint/SETUPLDR.BIN." Using the command you mentioned above, it just resets back to the main syslinux menu by booting, "chain.c32 hd0 1 ntldr=/minint/SETUPLDR.BIN" Thank you so much for helping me in advance. I appreciate all the help you've given me so far.

This is my first time ever working with the bootsector and mbr in a low-level way. I don't necessarily understand how it works, but I'd like to learn more. I'd like to learn how to hex edit the bootsector and mbr, but there is nowhere (that I've found so far) that will show me how to do this. All I can see are the hex numbers and ASCII text in my hex editor.

[wgjhstt247]

So I almost gave up... Then I discovered the solution. Here's how I got it to work:

1) Build UBCD4WIN on Windows XP. If you build in Vista, you need to get a copy of "EMPTYREGDB.DAT" and put it in the i386 folder.

2) Format UFD using the HP Format Tool.

2) Copied files over to UFD from "BartPE" folder using UBUSB (Copy files and format MBR, no need for anything else)
a) you can do this manually by copying in Windows Explorer. Change "i386" folder to "minint". Copy "setupldr.bin" to the root of the UFD, rename it to "ntldr". Copy "ntdetect.com" to the root of the UFD.

3) Download Syslinux. Important!! -> Copy cat.c32, chain.c32, menu.c32, reboot.c32, and vesamenu.c32 from the syslinux you downloaded to the UFD's "syslinux" folder. Run "syslinux -d syslinux x:" or "syslinux -ma -d syslinux x:" where "x" is the drive letter of your UFD.

4) Edit "syslinux.cfg" in the syslinux folder on the UFD. Edit the Ultimate boot cd entry to this:

LABEL UBCD4Win
  MENU LABEL Launch "The Ultimate Boot CD for Windows"
  COM32 chain.c32 
  APPEND hd0 1 ntldr=/ntldr
  TEXT HELP
  Runs a pre-installed Windows environment, loaded with diagnostic tools.
  ENDTEXT

5) Test it using USUSB's "Test USB" button.

Thanks again for all your help!!!

This post has been edited by wgjhstt247: 08 November 2009 - 01:45 AM

[cdob]

Thanks for report.

A renamed setupldr.bin is not the best solution.
Can you try 'chain.c32 ntldr=/minint/SETUPLDR.BIN' too?

[wgjhstt247]

cdob, on 08 November 2009 - 02:42 AM, said:

Thanks for report.

A renamed setupldr.bin is not the best solution.
Can you try 'chain.c32 ntldr=/minint/SETUPLDR.BIN' too?

Yes, that works too now. But I have to put in the hd0 1 to make it work with my version of syslinux. So the full command looks like this: "chain.c32 hd0 1 ntldr=/minint/setupldr.bin" So is this suppose to make it more compatible? Or why is it not the best solution to rename to ntldr and put it in the root?

[wgjhstt247]

cdob, on 08 November 2009 - 02:42 AM, said:

Thanks for report.

A renamed setupldr.bin is not the best solution.
Can you try 'chain.c32 ntldr=/minint/SETUPLDR.BIN' too?

I renamed ntldr, and gtldr in the root directory. It works without them just as you said. However, now I'm having issues loading the recovery console portion of UBCD4WIN. The command I use is this: "chain.c32 hd0 1 ntldr=/CMDCONS/SETUPLDR.BIN" and it loads the normal UBCD4WIN just as "chain.c32 hd0 1 ntldr=/minint/setupldr.bin" does. Also, How do I get rid of the multiple menu entries (It has the same menu about 5 or more times)?

[hilander999]

Quote

Also, How do I get rid of the multiple menu entries (It has the same menu about 5 or more times)?

You must check the "Build ISO" box in the builders main window since that is where all the post processing is done. You can disable "[Autobuild] - Build ISO" if you do not need the ISO file.

[cdob]

wgjhstt247, on 08 November 2009 - 12:07 PM, said:

I renamed ntldr, and gtldr in the root directory. It works without them just as you said.

That's nice.

Quote

However, now I'm having issues loading the recovery console portion of UBCD4WIN.

Setupldr.bin user internal default directories: I386, minint and cmdcons.
To break the defaults, change different files setupldr.bin.

Hexedit setupldr.bin, rename cmdcons to cmdcOFF and minint to minOFF.

[wgjhstt247]

cdob, on 08 November 2009 - 04:49 PM, said:

Hexedit setupldr.bin, rename cmdcons to cmdcOFF and minint to minOFF.

Do you mean hexedit the ASCI text in the file (ie. find where cmdcons in the file is at and rename it in the file)? Or do you mean something completely different? If so, please guide me through it. Thanks!

[cdob]

wgjhstt247, on 08 November 2009 - 11:09 PM, said:

Do you mean hexedit the ASCI text in the file

Yes.

[wgjhstt247]

cdob, on 08 November 2009 - 11:48 PM, said:

wgjhstt247, on 08 November 2009 - 11:09 PM, said:

Do you mean hexedit the ASCI text in the file

Yes.

It didn't work. The QEMU emulator crashed when I tried to load it. What else would you suggest?

[cdob]

How did you changed the file cmdcons\setupldr.bin?