[syslinux] USB bootable (using syslinux)

[Geert Stappers]

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