search for: lanworks

...ve.org/web/20040806022202/http://linux.tu-varna.acad.bg/~lig/romdsk/ On 15 January 2016 at 13:43, Sergii Kolisnyk <kolkmail at gmail.com> wrote: > As for BIOS, there are single-sector base memory (real mode) memdisk > implementations, which should be ROM-compatible. I do remember > Lanworks one. It's possible to make a compile option for syslinux > memdisk resident code to work with base memory. > > On 15 January 2016 at 00:50, H. Peter Anvin via Syslinux > <syslinux at zytor.com> wrote: >> On 01/13/16 00:13, Tal Lubko via Syslinux wrote: >>> >&...

...1.76, but the result is always the same. I'm quite sure that the problem is in my configuration somewhere, thanx in advance emir ------------------------------------------------------------------------------------------ Output on client: Managed PC Boot Agent (MBA) v 4.30 (C) Copyright 2000 Lanworks Technologies Corporation a subsidiary of 3Com Corporation Node 000475F7DB60 DHCP ............... TFTP ............... ------------------------------------------------------------------------------------------ Part of dhcpd.conf: allow booting; allow bootp; deny unknown-clients; not authoritativ...

On 01/13/16 00:13, Tal Lubko via Syslinux wrote: > > OK. I'll try that. > Any thoughts regarding the requirement to store the bootloader inside the BIOS chip? > That is fundamentally up to your BIOS. The best is to expose the bootloader in the BIOS as a (readonly) disk drive using standard BIOS or EFI interfaces. -hpa

As for BIOS, there are single-sector base memory (real mode) memdisk implementations, which should be ROM-compatible. I do remember Lanworks one. It's possible to make a compile option for syslinux memdisk resident code to work with base memory. On 15 January 2016 at 00:50, H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > On 01/13/16 00:13, Tal Lubko via Syslinux wrote: >> >> OK. I'll try that....

...e chosen upon CPU architecture right after the one named after assigned IP number. I mean it now attempts to load e.g. i686-smp (naming algorithm is described in commentary section) right after 409EDEE3 and before proceeding to 409EDEE. The code was tested under Managed PC Boot Agent (MBA) v4.30 by Lanworks/3Com, Intel Boot Agent 1.0.15 (Gigabit desktop adapter), 3.0.5 and 4.0.13 (100Mbit built-in adapters), all PXE 2.x implementations, and with Intel MP Spec 1.1 and 1.4 compliant ASUS motherboards. In case you wonder DHCP service is provided by ISC dhcpd 2.0. Cheers. Andy. -------------- next part -...

> -----Original Message----- > From: Sergii Kolisnyk [mailto:kolkmail at gmail.com] > Sent: Tuesday, January 19, 2016 2:35 PM > To: Syslinux > Cc: Tal Lubko > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > Hi, Tal, > > could you answer to 2 questions: > - what is amount of ROM you're intending to use? > (actually 8

Hello I have an application running on top of the ORK (Open Ravenscar Kernel). The file format of the executable is elf: $ file /var/tftp/hello.vmic7750 /var/tftp/hello.vmic7750: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, not stripped I wonder if I can use pxelinux for booting the kernel via network on the target machine. The target machine support PXE. I

Hi I am using PXELinux to boot BartPE and some other application and it works fine. There are some other Boot application which I am using 3COM MBAUTIL PXE.mnu and floppy images. I have problem chaining from pxelinux.0 to 3com pxe.0 (pxe.mnu). Consider: BIOS->(DHCP-TFTP)->pxelinux.0 works fine. BIOS->(DHCP-TFTP)->3COM pxe.mnu works fine, the menu appears and I can choose a floppy