Jump to content











Photo
- - - - -

Please Help WinXP & Win7 USB Duel Boot


  • Please log in to reply
3 replies to this topic

#1 Ramkumar

Ramkumar
  • Members
  • 1 posts
  •  
    India

Posted 10 August 2011 - 07:45 PM

i am try to create duel boot usb for install winxp and win7.
win7 working but winxp not working. my syslinux.cfg code is.


default vesamenu.c32
menu title multiboot
MENU WIDTH 72
MENU MARGIN 10
MENU VSHIFT 3
MENU HSHIFT 6
MENU ROWS 5
MENU TABMSGROW 20
MENU TIMEOUTROW 22
menu color title 1;36;44 #66A0FF #00000000 none
menu color hotsel 30;47 #C00000 #DDDDDDDD
menu color sel 30;47 #000000 #FFFFFFFF
menu color border 30;44 #D00000 #00000000 std
menu color scrollbar 30;44 #DDDDDDDD #00000000 none

label Install Windows 7 x86
menu label Windows Vista/7 Installer
COM32 chain.c32
append fs ntldr=/bootmgr

label Install Windows XP
menu label Windows XP
COM32 chain.c32
append fs ntldr=/i386/SETUPLDR.BIN

any one please help me.
Thanks

#2 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1338 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 10 August 2011 - 08:24 PM

While this site tends to use GRUB (rather than syslinux), end result is more important. Go to the RMPrepUSB site and pick your "tutorial"...

#3 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 11 August 2011 - 07:37 AM

label Install Windows 7 x86
menu label Windows Vista/7 Installer
COM32 chain.c32
append fs ntldr=/bootmgr

label Install Windows XP
menu label Windows XP
COM32 chain.c32
append fs ntldr=/i386/SETUPLDR.BIN

any one please help me.
Thanks

Please do not use spaces in LABEL directives; spaces in MENU LABEL are fine.

chain.c32's ntldr= argument must point to a file that's available in the same filesystem as Syslinux booted from. So: Does that filesystem have /i386/setupldr.bin in it?

Also: When working with GRUB4DOS or Syslinux and trying to determine the cause of a problem, it can help to remove the menu system and simply use the boot-loader's CLI, entering your commands manually and observing the results. When you use a menu system, you take the chance that you will not observe the results. Please try "commenting-out" your DEFAULT directive and avoid running the 'vesamenu.c32' COMBOOT32 module, just until you understand the nature of the failure. You should get a "boot:" prompt from which you can try your LABELs.

# Comments begin with #

#default vesamenu.c32

menu title multiboot

...



#4 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15194 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 11 August 2011 - 08:11 AM

While this site tends to use GRUB (rather than syslinux), end result is more important. Go to the RMPrepUSB site and pick your "tutorial"...


Actually this site :w00t: tends to use grub4dos, which is NOT GRUB (Legacy) and is NOT GRUB2.
Why it is so difficult calling things with their names? :dubbio:

:cheers:
Wonko




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users