search for: kolisnyk

Google search freedos rom found two source-available implementations: https://web.archive.org/web/20050104085311/http://rayer.wz.cz/romos/romose.htm https://web.archive.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...

Hey Guys, Below is a patch for the com32/rosh/rosh.c from tonights syslinx git. The patch does the following: 1) changes the rosh_issp to use an if instead of a case for this simple test. 2) changes the rosh_dir_arg function to move the readdir() to inside the while test. This will let me go through my APUE book. Let me know if you have any questions. Keith --- rosh.orig 2009-03-05

Need some assistance, I have a firewall I am trying to reinstall the os, on, and I have no idea how to do it, they sent me syslinux, but I have no idea what kernel to use, or really how to install it using syslinux. Please, any help will be appreciated. Scott Latta Network Administrator Techsupport Supervisor Nexity Bank A+, NET+, MCP 205-298-6482

...w Windows partition needs activation. Is it necessary to turn an ext2/ext3 partition to active, too? If it is, how? Best regards, Hu Jia Yi Ext: 20430 Tel: 65-67510430 -----Original Message----- ------------------------------ Message: 5 Date: Thu, 21 Aug 2008 13:03:00 +0300 From: "Sergii Kolisnyk" <kolkmail at gmail.com> Subject: Re: [syslinux] failed when boot the kernel image on the hard disk from syslinux on a floppy To: "For discussion of SYSLINUX and tftp-hpa" <syslinux at zytor.com> Message-ID: <1783038b0808210303j3c69e310pb6892b5f681b5190 at mail.gmail...

I am now convinced the problem is really trivial to solve. The problem is that ldlinux.c32 is too big, but we already know that stripping the modules gets them down to a reasonable size: 430318 ldlinux.c32 114376 ldlinux.c32 It would also be nice to support LZO or gzip compressed modules: 66798 ldlinux.c32.lzo 61513 ldlinux.c32.gzip ... which would really take care of the problem. But

Hi, As I have not seen any confirmation yet on the list, I just wanted to let you know that sdi.c32 works fine here, at least as fine as my initial syslinux-2.11 asm patch. I only use XPe SDI images with the following structure (of course PART blob size can vary): Type Offset Size Base Address Attr ---- ------------------- -------------------

After formatting a floppy to MSDOS format and using syslinux /dev/fd0, I successfully installed ldlinux.sys to the root directory of the floppy. Then I created a syslinux.cfg under the root directtory of this floppy to load the linux kernel in my first hard disk, 3rd partition, boot folder. The file system of this partition is ext3. The floppy has a FAT file system. This config file is listed

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

> -----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...

> -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Sent: Friday, January 15, 2016 8:41 PM > To: Tal Lubko; 'Celelibi' > Cc: 'For discussion of Syslinux and tftp-hpa' > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On 01/14/2016 02:50 PM, H. Peter Anvin via Syslinux wrote: > > On

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:

Hi! I'm sorry for misposting. Could you actually post the output of tar tzf (list of content) here? It's small enough (for just a firewall), it contains no your information and no someone's trade secrets. Then I and others could figure out instructions for installing genuine OS. Tar for Windows is here: http://gnuwin32.sourceforge.net/downlinks/tar-bin.php Best regards, Sergii On

http://comments.gmane.org/gmane.network.ipxe.devel/2872 On 24 April 2014 01:37, Romine, Bryan <Bryan.Romine at amd.com> wrote: > Is it possible to boot a Windows image file (.wim) directly from Syslinux 6.xx EFI? If not, is this a feature that will ever be added? This may be related to bug #17: http://bugzilla.syslinux.org/show_bug.cgi?id=17 > > > Bryan Romine [Description:

Hi, Tal, could you answer to 2 questions: - what is amount of ROM you're intending to use? (actually 8 MB SPI or parallel NOR flash chip can contain some minimalist Linux distribution) - which chip do you plan to flash to, motherboard BIOS or option ROM? Also, ROMOS comes without a license, so you'll have to contact the author for commercial usage. On other hand, ROMDSK is GPLed, and you