UBCD4Win Forums: Syslinux Usb Multiboot - UBCD4Win Forums

Jump to content

  • (4 Pages)
  • +
  • 1
  • 2
  • 3
  • 4
  • You cannot start a new topic
  • This topic is locked

Syslinux Usb Multiboot Using Syslinux to boot UBCD4Win

#16 User is offline   feelunion Icon

  • Newbie
  • Pip
    • Group: Members
    • Posts: 15
    • Joined: 05-November 09
    • Gender:Male

    Posted 09 November 2009 - 10:58 AM

    View Postwgjhstt247, on 08 November 2009 - 08:34 AM, said:

    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!!!


    Thank u for sharing ur thoughts, I did exactly what you said but I got message "NTDETECT failed"

    Posted Image

    I'm using UFD Kingstone 4GB with FAT32.
    Any help would be appreciated.
    0

    #17 User is offline   wgjhstt247 Icon

    • Member
    • PipPip
      • Group: Members
      • Posts: 27
      • Joined: 07-November 09
      • Gender:Male
      • Location:Chicago, IL USA

      Posted 09 November 2009 - 11:17 AM

      View Postcdob, on 09 November 2009 - 07:47 AM, said:

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


      I used my hex editor's Find and replace function. I changed everywhere "cmdcons" was written to "cmdOFF." I also searched for "minint" but none were found." Then I saved it as "setupldr2.bin" and chainloaded it in syslinux.
      0

      #18 User is offline   wgjhstt247 Icon

      • Member
      • PipPip
        • Group: Members
        • Posts: 27
        • Joined: 07-November 09
        • Gender:Male
        • Location:Chicago, IL USA

        Posted 09 November 2009 - 11:22 AM

        View Postfeelunion, on 09 November 2009 - 09:58 AM, said:

        Thank u for sharing ur thoughts, I did exactly what you said but I got message "NTDETECT failed"

        Posted Image

        I'm using UFD Kingstone 4GB with FAT32.
        Any help would be appreciated.


        The fact that you even got "Setup is inspecting your computer's hardware configuration..." means that the boot part of it is working. So you copied ntdetect.com from the i386 or minint folder to the root of the UFD? There should still be a copy of it in the i386 or minint folder as well. If it still isn't working right, use UBUSB (run as administrator) and just copy the files over (Don't do anything else). UBUSB will do all the necessary arrangements for you automatically. =)
        0

        #19 User is offline   feelunion Icon

        • Newbie
        • Pip
          • Group: Members
          • Posts: 15
          • Joined: 05-November 09
          • Gender:Male

          Posted 09 November 2009 - 12:02 PM

          View Postwgjhstt247, on 09 November 2009 - 06:22 PM, said:

          View Postfeelunion, on 09 November 2009 - 09:58 AM, said:

          Thank u for sharing ur thoughts, I did exactly what you said but I got message "NTDETECT failed"

          Posted Image

          I'm using UFD Kingstone 4GB with FAT32.
          Any help would be appreciated.


          The fact that you even got "Setup is inspecting your computer's hardware configuration..." means that the boot part of it is working. So you copied ntdetect.com from the i386 or minint folder to the root of the UFD? There should still be a copy of it in the i386 or minint folder as well. If it still isn't working right, use UBUSB (run as administrator) and just copy the files over (Don't do anything else). UBUSB will do all the necessary arrangements for you automatically. =)


          Thank u for reply, Now I got error "Access Path"
          I'll try again, But this time with video recording.
          Hope it will help.
          Thank u again.
          0

          #20 User is offline   wgjhstt247 Icon

          • Member
          • PipPip
            • Group: Members
            • Posts: 27
            • Joined: 07-November 09
            • Gender:Male
            • Location:Chicago, IL USA

            Posted 09 November 2009 - 01:26 PM

            View Postfeelunion, on 09 November 2009 - 11:02 AM, said:

            Thank u for reply, Now I got error "Access Path"
            I'll try again, But this time with video recording.
            Hope it will help.
            Thank u again.


            What version of Windows XP did you build UBCD4WIN on?
            What version of syslinux are you using?
            Which version of UBUSB.exe?

            The root of your UFD should have these files:
            bootsect.bin, ntdetect.com, win51ip, win51ip.sp2 or win51ip.sp1 (depending on the service pack you built with), and winbom.ini.

            minint folder should have these files (not including folders):
            biosinfo.inf, BOOTFIX.BIN, EMPTYREGDB.DAT, explorer.exe, iexplore.exe, ntdetect.com, regedit.exe, setupldr.bin, spcmdcon.sys, system.ini, txtsetup.sif, win.ini, WindowsShell.Manifest, and winhlp32.exe

            syslinux.cfg should look like this:
            LABEL UBCD4Win
              MENU LABEL Ultimate Boot CD for Windows
              COM32 chain.c32 
              APPEND hd0 1 ntldr=/minint/setupldr.bin
              TEXT HELP
              Runs a pre-installed Windows environment, loaded with diagnostic tools.
              ENDTEXT
            

            This post has been edited by wgjhstt247: 09 November 2009 - 01:34 PM

            0

            #21 User is offline   pcuser Icon

            • Project Programmer
            • PipPipPipPipPipPipPip
              • Group: Moderator & Development
              • Posts: 3,822
              • Joined: 20-November 04
              • Gender:Male
              • Location:Kneebrasskee

              Posted 09 November 2009 - 01:58 PM

              Quote

              ubcd4win.bss that's included with the build is for a fat16 flash drive, but there is none for a fat32 flash drive.

              Yes, there is a fat16 ubcd4win.bss included in UBCD4Win but UBUSB doesn't use it. UBUSB creates a new file dynamically depending on the filesystem being used.
              If you're afraid of taking any chances then the chances are great that you will never learn anything

              Multiboot Plugins - UBUSB (Ultimate Boot USB) - EzPcFix - RootKitty - Network Configuration Utility - UnIsoFS - A Small Linux Distro - SELogger - HashME - WSock - My Paypal
              0

              #22 User is offline   feelunion Icon

              • Newbie
              • Pip
                • Group: Members
                • Posts: 15
                • Joined: 05-November 09
                • Gender:Male

                Posted 09 November 2009 - 02:04 PM

                View Postwgjhstt247, on 09 November 2009 - 08:26 PM, said:

                View Postfeelunion, on 09 November 2009 - 11:02 AM, said:

                Thank u for reply, Now I got error "Access Path"
                I'll try again, But this time with video recording.
                Hope it will help.
                Thank u again.


                What version of Windows XP did you build UBCD4WIN on?
                What version of syslinux are you using?
                Which version of UBUSB.exe?

                The root of your UFD should have these files:
                bootsect.bin, ntdetect.com, win51ip, win51ip.sp2 or win51ip.sp1 (depending on the service pack you built with), and winbom.ini.

                minint folder should have these files (not including folders):
                biosinfo.inf, BOOTFIX.BIN, EMPTYREGDB.DAT, explorer.exe, iexplore.exe, ntdetect.com, regedit.exe, setupldr.bin, spcmdcon.sys, system.ini, txtsetup.sif, win.ini, WindowsShell.Manifest, and winhlp32.exe

                syslinux.cfg should look like this:
                LABEL UBCD4Win
                  MENU LABEL Ultimate Boot CD for Windows
                  COM32 chain.c32 
                  APPEND hd0 1 ntldr=/minint/setupldr.bin
                  TEXT HELP
                  Runs a pre-installed Windows environment, loaded with diagnostic tools.
                  ENDTEXT
                


                Thank u again wgjhstt247

                This is the answers:

                Quote

                What version of Windows XP did you build UBCD4WIN on?

                Windows XP SP3 on Vmware machine.

                Quote

                What version of syslinux are you using?

                syslinux-3.83

                Quote

                Which version of UBUSB.exe?

                The one that include with UBCD4WIN

                root of UFD
                Posted Image

                minint folder
                Posted Image

                syslinux.cfg
                Posted Image

                I'm so lost. :(

                PS: When I build UBCD4WIN I used Windows server 2003 files.

                This post has been edited by feelunion: 09 November 2009 - 02:06 PM

                0

                #23 User is offline   cdob Icon

                • Special Guest
                • PipPipPipPipPipPip
                  • Group: Moderator & Development
                  • Posts: 1,387
                  • Joined: 19-October 05

                  Posted 09 November 2009 - 02:15 PM

                  @wgjhstt247

                  New game:
                  Revovery Console with grub4dos, called by syslinux
                  Copy grub.exe to \syslinux

                  Do you have a \cmdc or \cmdcons directory? Rename \cmdc to \cmdcons

                  Use a default file setupldr.bin.

                  LABEL cmdc
                    MENU LABEL Windows(tm) Recovery Console - grub4dos
                    KERNEL grub.exe
                    APPEND --config-file="ls /cmdcons/setupldr.bin || find --set-root /cmdcons/setupldr.bin;chainloader /cmdcons/setupldr.bin;write 0x7C03 0x63646D63;write 0x7C07 0x00736E6F"
                    # write string "cmdcons" to memory 0000:7C03
                    TEXT HELP
                    Windows(tm) Recovery Console
                    ENDTEXT


                  Check or create file \cmdcons\winnt.sif
                  [data]
                  CmdCons="1"

                  0

                  #24 User is offline   wgjhstt247 Icon

                  • Member
                  • PipPip
                    • Group: Members
                    • Posts: 27
                    • Joined: 07-November 09
                    • Gender:Male
                    • Location:Chicago, IL USA

                    Posted 09 November 2009 - 02:21 PM

                    View Postfeelunion, on 09 November 2009 - 01:04 PM, said:

                    I'm so lost. :(

                    PS: When I build UBCD4WIN I used Windows server 2003 files.


                    I know how lost feels. I was there once. Just hang in there and we'll figure this out.

                    1)You should build UBCD4WIN with Windows XP SP2 or SP1 files. No need to use the Windows Server 2003 files. Building on Vmware is fine. I built mine on Virtual PC 2007.

                    2) Run UBUSB.exe as Administrator (get the latest version - 1.0.46). Leave everything unchecked, make sure the directory for your built files is correct (it will remove everything from your UFD). Hit Go.

                    3) Downgrade syslinux to 3.75. That's the version I'm currently using. Run syslinux.exe -ma -d syslinux x: where x is the drive letter of your UFD. Copy over the chain.c32, vesamenu.c32, reboot.c32, etc. from the 3.75 version of syslinux. This is important because these are effected by the syslinux code in the bootloader.

                    4) Modify syslinux.cfg file to this:
                    LABEL UBCD4Win
                      MENU LABEL Ultimate Boot CD for Windows
                      COM32 chain.c32 
                      APPEND hd0 1 ntldr=/minint/setupldr.bin
                      TEXT HELP
                      Runs a pre-installed Windows environment, loaded with diagnostic tools.
                      ENDTEXT
                    

                    0

                    #25 User is offline   feelunion Icon

                    • Newbie
                    • Pip
                      • Group: Members
                      • Posts: 15
                      • Joined: 05-November 09
                      • Gender:Male

                      Posted 09 November 2009 - 02:30 PM

                      View Postwgjhstt247, on 09 November 2009 - 09:21 PM, said:

                      View Postfeelunion, on 09 November 2009 - 01:04 PM, said:

                      I'm so lost. :(

                      PS: When I build UBCD4WIN I used Windows server 2003 files.


                      I know how lost feels. I was there once. Just hang in there and we'll figure this out.

                      1)You should build UBCD4WIN with Windows XP SP2 or SP1 files. No need to use the Windows Server 2003 files. Building on Vmware is fine. I built mine on Virtual PC 2007.

                      2) Run UBUSB.exe as Administrator (get the latest version - 1.0.46). Leave everything unchecked, make sure the directory for your built files is correct (it will remove everything from your UFD). Hit Go.

                      3) Downgrade syslinux to 3.75. That's the version I'm currently using. Run syslinux.exe -ma -d syslinux x: where x is the drive letter of your UFD. Copy over the chain.c32, vesamenu.c32, reboot.c32, etc. from the 3.75 version of syslinux. This is important because these are effected by the syslinux code in the bootloader.

                      4) Modify syslinux.cfg file to this:
                      LABEL UBCD4Win
                        MENU LABEL Ultimate Boot CD for Windows
                        COM32 chain.c32 
                        APPEND hd0 1 ntldr=/minint/setupldr.bin
                        TEXT HELP
                        Runs a pre-installed Windows environment, loaded with diagnostic tools.
                        ENDTEXT
                      


                      I'm going to do this now, and I'll tell u the results later. ^_^
                      0

                      #26 User is offline   feelunion Icon

                      • Newbie
                      • Pip
                        • Group: Members
                        • Posts: 15
                        • Joined: 05-November 09
                        • Gender:Male

                        Posted 09 November 2009 - 03:30 PM

                        @wgjhstt247

                        I just have two questions before using UBUSB

                        Quote

                        2) Run UBUSB.exe as Administrator (get the latest version - 1.0.46). Leave everything unchecked, make sure the directory for your built files is correct (it will remove everything from your UFD). Hit Go.


                        Is this right!
                        Posted Image

                        And how about Boot Loader, should I leave it as Grub4dos or what!

                        Quote

                        Run syslinux.exe -ma -d syslinux x: where x is the drive letter of your UFD.


                        This is what I did before

                        downloaded syslinux-3.75 and put it in the "C" drive
                        Posted Image

                        Went to Start then Run
                        Posted Image

                        And then I typed this to get the path of syslinux.exe
                        Posted Image

                        After that I hit Enter and got as u c in the next pic
                        Posted Image

                        Is that right!
                        0

                        #27 User is offline   pcuser Icon

                        • Project Programmer
                        • PipPipPipPipPipPipPip
                          • Group: Moderator & Development
                          • Posts: 3,822
                          • Joined: 20-November 04
                          • Gender:Male
                          • Location:Kneebrasskee

                          Posted 09 November 2009 - 03:41 PM

                          Quote

                          And how about Boot Loader, should I leave it as Grub4dos or what!

                          Aren't you wanting syslinux instead? I'm curious to know why you both don't just use UBUSB to install syslinux? Why are you installing it from the commandline?
                          If you're afraid of taking any chances then the chances are great that you will never learn anything

                          Multiboot Plugins - UBUSB (Ultimate Boot USB) - EzPcFix - RootKitty - Network Configuration Utility - UnIsoFS - A Small Linux Distro - SELogger - HashME - WSock - My Paypal
                          0

                          #28 User is offline   wgjhstt247 Icon

                          • Member
                          • PipPip
                            • Group: Members
                            • Posts: 27
                            • Joined: 07-November 09
                            • Gender:Male
                            • Location:Chicago, IL USA

                            Posted 09 November 2009 - 03:45 PM

                            @feelunion

                            You can leave the grub4dos bootloader on in UBUSB (We change the bootloader when launching syslinux.exe). The path to your built files is correct as well. You ran syslinux.exe correctly. It won't give you any messages saying you did it right, but it will take a moment to finish and then prompt.

                            After you run syslinux, make sure you copy the chain.c32, reboot.c32, vesamenu.c32, and menu.c32 from the downloaded syslinux folder (C:\syslinux\com32\ and C:\syslinux\menu\) to the syslinux folder on the UFD. If you get a menu when you boot your UFD, you installed syslinux correctly.
                            0

                            #29 User is offline   feelunion Icon

                            • Newbie
                            • Pip
                              • Group: Members
                              • Posts: 15
                              • Joined: 05-November 09
                              • Gender:Male

                              Posted 09 November 2009 - 03:46 PM

                              View Postpcuser, on 09 November 2009 - 10:41 PM, said:

                              Quote

                              And how about Boot Loader, should I leave it as Grub4dos or what!

                              Aren't you wanting syslinux instead? I'm curious to know why you both don't just use UBUSB to install syslinux? Why are you installing it from the commandline?


                              Thx for reply
                              Do u mean there is no need for commandline if we used syslinux in boot loader?
                              0

                              #30 User is offline   feelunion Icon

                              • Newbie
                              • Pip
                                • Group: Members
                                • Posts: 15
                                • Joined: 05-November 09
                                • Gender:Male

                                Posted 09 November 2009 - 03:51 PM

                                View Postwgjhstt247, on 09 November 2009 - 10:45 PM, said:

                                @feelunion

                                You can leave the grub4dos bootloader on in UBUSB (We change the bootloader when launching syslinux.exe). The path to your built files is correct as well. You ran syslinux.exe correctly. It won't give you any messages saying you did it right, but it will take a moment to finish and then prompt.

                                After you run syslinux, make sure you copy the chain.c32, reboot.c32, vesamenu.c32, and menu.c32 from the downloaded syslinux folder (C:\syslinux\com32\ and C:\syslinux\menu\) to the syslinux folder on the UFD. If you get a menu when you boot your UFD, you installed syslinux correctly.


                                Ok, I'm going to do it now. ^_^
                                0

                                • (4 Pages)
                                • +
                                • 1
                                • 2
                                • 3
                                • 4
                                • You cannot start a new topic
                                • This topic is locked

                                1 User(s) are reading this topic
                                0 members, 1 guests, 0 anonymous users