similar to: Could not find kernel image: memdisk error

Hallo, I try to boot the windows 98 bootdisk via memdisk. It doesn't work completely. Booting a freedos FD image works, booting the windows 98 image works too. But the windows 98 boot disk then should extract the file "ebd.cab" with the file "extract.com", and that step fails. Is that a syslinux problem or a windows problem? Viele Gruesse! Helmut

Hi! Sorry to bother you, but I don't know where else to ask about memdisk. I'm trying to use memdisk + pxelinux with a DOS boot image, is this possible? It works great with redhat and debian install floppy images, but my freedos, and win98 boot disk just won't boot! Is there some special way to prepare a dos image other than doing a sys a: or format a: /s in DOS, and then dd-ing it

On Thu, Jun 6, 2013 at 11:58 AM, upen <upendra.gandhi at gmail.com> wrote: >> This is sounding like dropped/intercepted packets. Could we get some >> details on the client (make/model of computer/motherboard, same for >> NIC, PXE OROM details)? Is it connected to the same physical switch >> as the DHCP/TFTP server? Any chance that the physical switch that the

On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote: > I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks this > step resolved the earlier error. Next I get failed to load com32 file > vesamenu.c32 while that file exists in /tftplinux/linux-install. Is vesamenu.c32 from 5.10? -- -Gene

Just a trivial question... Do the hosts allow and hosts deny clauses (i.e. within smb.conf) support the use of IPv4 CIDR notation (e.g. A.B.C.D/maskbits) ? The specific documentation page I was looking at, i.e.: https://www.samba.org/samba/docs/using_samba/ch06.html was rather entirely ambiguous on this one small point. When describing the interfaces clause, it says explicitly that CIDRs

> On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao > Miller, Kenneth Davis, wrote: > > [...] > > Thank you all for your responses. You helped me solve my problem. For > anyone else that runs into similar trouble and finds this thread, here > follow summaries of what I've learned. > > To recap, our PXE server holds Dell BIOS updates in

On Jun 5, 2013 6:13 PM, "upen" <upendra.gandhi at gmail.com> wrote: > > Thanks hpa. It looks like it's not able to find lpxelinux.0 files which > actually resides under /tftpboot/linux-install directory where the > pxelinux.0 existed before. > > ls -al /tftpboot/linux-install/lpxelinux.0 > -rwxr-xr-x 1 root root 81240 Jun 5 15:15 >

Hi, Where can i find up to date samba4 related smb.conf settings? Is this for samba4 too: http://www.samba.org/samba/docs/using_samba/ch06.html Thanks, Robert

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

2018-06-26 2:10 GMT+08:00 H. Peter Anvin via Syslinux <syslinux at zytor.com>: > On 06/18/18 13:06, R S via Syslinux wrote: >> The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. >> >> If you are interested I could provide a 5MB FDD image template based on >> FreeDOS 2041 kernel (the latest available at that time in 2014) where you >>

The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. If you are interested I could provide a 5MB FDD image template based on FreeDOS 2041 kernel (the latest available at that time in 2014) where you would just inject your ROM and EXE (and possibly adjust autoexec.bat to autostart/apply the FW update). It's a minimal FreeDOS FDD image that defaults to a clean boot with

On Wed, Jun 5, 2013 at 7:49 PM, upen <upendra.gandhi at gmail.com> wrote: > On Wed, Jun 5, 2013 at 5:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Jun 5, 2013 6:13 PM, "upen" <upendra.gandhi at gmail.com> wrote: >> > >> > Thanks hpa. It looks like it's not able to find lpxelinux.0 files which >> > actually resides under

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

I am using FreeDOS kernel 2.0.34 with FAT32 support (ke2034_32), together with PXELINUX and memdisk from SYSLINUX 2.0.9-pre15. I am experiencing this problem on multiple test systems (Dell Precision 450 and IBM T22 so far). My pxelinux.cfg/default has these lines: label test kernel memdisk append initrd=test.img keeppxe ...which let me boot my 1.44M "test.img"

Hi I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy disk image 8440kB size. I've put FreeDOS kernel and bootsector into the floppy. Boot process goes fine with this command: isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy The problems begin when I try to run FreeDOS memory manager emm386 from the floppy image. my config.sys: ...

On Wed, Jun 5, 2013 at 7:34 PM, upen <upendra.gandhi at gmail.com> wrote: > > > > On Wed, Jun 5, 2013 at 7:25 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> On Wed, Jun 5, 2013 at 7:49 PM, upen <upendra.gandhi at gmail.com> wrote: >> > On Wed, Jun 5, 2013 at 5:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Jun 5,

Helle, I'm facing a strange issue with memdisk The context : syslinux 3.75 gpxelinux.0 the gpxe stript called from a menu executed through menu.c32 : #!gpxe kernel /modules/memdisk initrd=/freedos initrd /freedos The output before the freeze : /boot.gpxe. ok /modules/memdisk. ok /freedos...... ok MEMDISK 3.75 3.75 Copyright 2001-2009 H. Peter Anvin et al e820: 0000000000000000

I've been recompiling syslinux 2.09 and with my gcc 3.3.2, I must use the -O1 option instead of -Os. After compiling with -Os, the linker says "undefined reference to `memcmp'" My gcc specialist told me that this error was due to a too long inline of memcmp(). I've tryied my memdisk compiled in O1, the size is really quite the same and it works fine. So I will keep memdisk

Haven't yet had a need for 10MB FDD images. The biggest I had to create was 5MB (5760kb). At that time I had to use WinImage to create the FDD image and it took me a while to figure out the correct settings. My notes state: "I'm getting 'missing FAT' errors in WinImage, and 7-zip complains about 'unexpected end'. The fix is to increasing the FDD Heads from 2 to 4 and

On 06/18/18 13:06, R S via Syslinux wrote: > The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. > > If you are interested I could provide a 5MB FDD image template based on > FreeDOS 2041 kernel (the latest available at that time in 2014) where you > would just inject your ROM and EXE (and possibly adjust autoexec.bat to > autostart/apply the FW update).