[syslinux] USB bootable (using syslinux)
Agostinho Carvalho
agostinho.df.carvalho at hotmail.com
Sun Jul 19 05:02:31 PDT 2009
> Date: Sun, 19 Jul 2009 08:58:00 +0200
> From: stappers at stappers.nl
> To: syslinux at zytor.com
> Subject: Re: [syslinux] USB bootable (using syslinux)
>
> Op 20090719 om 02:23 schreef Agostinho Carvalho:
> > Date: Tue, 14 Jul 2009 21:29:37 +0000
> > From: kimmik999999 at yahoo.co.uk
> > > From: Agostinho Carvalho <agostinho.df.carvalho at hotmail.com>
> > > Sent: Tuesday, 14 July, 2009 21:19:55
> > >>
> > >> Hello!
> > >>
> > >> Yes I have unmounted the pendrive (so there is no unsaved data in
> > >> any buffer memory area). And besides (normally) I don't remove
> > >> the pendrive from the USB port unless the PC is off.
> > >>
> > >> I also haven't touched the floppy image data (no files added,
> > >> modified, etc...)
> > >>
> > >> Any more suggestions?
> > >> I'll keep trying to...
> > >>
> > >> Thank you
> > >>
> > >
> > > Part of /doc/memdisk.txt of the syslinux archive:
> > >
> > > d) MEMDISK normally uses the BIOS "INT 15h mover" API to access high
> > > memory. This is well-behaved with extended memory managers which load
> > > later. Unfortunately it appears that the "DOS boot disk" from
> > > WinME/XP *deliberately* crash the system when this API is invoked.
> > > The following command-line options tells MEMDISK to enter protected
> > > mode directly, whenever possible:
> > >
> > > raw Use raw access to protected mode memory.
> > >
> > > bigraw Use raw access to protected mode memory, and leave the
> > > CPU in "big real" mode afterwards.
> > >
> > > int Use plain INT 15h access to protected memory. This assumes
> > > that anything which hooks INT 15h knows what it is doing.
> > >
> > > safeint Use INT 15h access to protected memory, but invoke
> > > INT 15h the way it was *before* MEMDISK was loaded.
> > > This is the default since version 3.73.
> > >
> > >
> > > So try adding one of the previous parameters to memdisk:
> > >
> > > LABEL DOS
> > > MENU LABEL Boot into DOS
> > > KERNEL /boot/memdisk
> > > APPEND initrd=/boot/images/winme.img raw
> > > TEXT HELP
> > >
> > >
> >
> > Hello!
> >
> > I have tried 'raw' and 'bigraw'.
> > Unfortunately it didn't help.
> >
> > I also changed to a Win98 image floppy (without RAMDrive support).
> > It just won't work.
> >
> > What are the other boot alternatives to MEMDISK?
> > Maybe a .bss file??
>
> The hardware, how does it see the USB device? ( As a floppy ? )
> Any partitions involved?
>
>
>
> Cheers
> Geert Stappers
>
> _______________________________________________
Hello Geert
When the system reboots I use F12 key (show Boot Menu) and I select "Cone 256MB USB Flash Disk".
To make the pendrive I used:
mkdiskimage -4 /dev/sdb 0 64 32
Then:
syslinux -s -d /boot/syslinux /dev/sdb4
Then I copy the necessary files:
boot directory contents:
drwxr-xr-x 2 ADFC root 4096 2009-07-13 00:41 images
drwxr-xr-x 2 ADFC root 4096 2009-07-13 00:43 syslinux
-rwxr-xr-x 1 ADFC root 2643405 2009-04-13 11:43 initrd.gz
-rwxr-xr-x 1 ADFC root 19584 2009-06-09 18:20 memdisk
-rwxr-xr-x 1 ADFC root 408760 2009-06-14 19:33 splash.png
-rwxr-xr-x 1 ADFC root 140580 2009-04-13 11:43 vesamenu.c32
boot/images directory contents:
-rwxr-xr-x 1 ADFC root 1474560 2004-03-25 12:04 622c.img
boot/syslinux directory contents:
-rwxr-xr-x 1 ADFC root 14918 2009-06-20 20:45 ldlinux.sys
-rwxr-xr-x 1 ADFC root 1884 2009-07-13 00:43 syslinux.cfg
Then I modify the syslinux.cfg file:
PROMPT 0
TIMEOUT 30
DEFAULT /boot/vesamenu.c32
MENU BACKGROUND /boot/splash.png
#
#
#
# #Some color definitions are placed here
#
#
#
LABEL DOS
MENU LABEL Boot into DOS
KERNEL /boot/memdisk
APPEND initrd=/boot/images/622c.img
TEXT HELP
Help:
Loads MS-DOS.
ENDTEXT
What am I doing wrong?
Thank you all
Agostinho C.
_________________________________________________________________
With Windows Live, you can organize, edit, and share your photos.
http://www.microsoft.com/middleeast/windows/windowslive/products/photo-gallery-edit.aspx
More information about the Syslinux
mailing list