similar to: memdisk parameters in windows pe.

Hi. I'm working on replacing a PXELINUX/MEMDISK loaded DOS based installation image with a PXELINUX/MEMDISK loaded WinPE ISO image. So far everything seems to work well (appending "bigraw" to memdisk solved booting problems on several machines), but I kind of miss the option of using getargs.com to get/set environment variables from the memdisk command line. Is there any way to

Hallo, versuche mit Pxelinux Windows 98 ?ber das Netz zu laden. Hierzu verwende ich Memdisk und ein Imgage einer funktionierenden Startdiskette (1,44 MB). Memdisk und das Image werden korrekt geladen. Auch startet die Autoexec.bat korrekt. Beim Start von Windows bricht das System allerdings ab. Mein Verdacht ist, dass es an dem noch im Speicher stehenden Memdisk liegt. Gibt es eine M?glichkeit

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

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

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

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"

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

I have added instructions to memdisk.doc for how to disable MEMDISK. However, it's unlikely that this will work if you're running under DOS, since DOS will be very unhappy about drives changing underneath it. Anyway, until the next (pre)release comes out, here are the instructions: --- memdisk.doc 27 Apr 2004 06:49:36 -0000 1.10 +++ memdisk.doc 6 Jul 2004 01:29:03 -0000 @@ -122,5

Greetings, all... Hoping someone can point me in the right direction. I've set up a Linux PXE host with a menu choice to install Windows. This option boots a WinPE image, which then uses \\net use... to mount the appropriate ISO image. Works fine. However, I would like to pass the iso name and directory into WinPE from the menu via append= arguments. Thus, I can set up a separate menu option

> Greetings, all... Hoping someone can point me in the right > direction. I've set up a Linux PXE host with a menu choice to > install Windows. This option boots a WinPE image, which then uses > \\net use... to mount the appropriate ISO image. Works fine. > However, I would like to pass the iso name and directory into > WinPE from the menu via append= arguments. Thus, I can

I've got $SUBJ almost working except for the DOS bit where the CD needs to be read. My pxe config: label Firmware menu label Update IPMI firmware kernel memdisk append keeppxe raw iso initrd=<isofile> The ISO is about 400Mb, and works fine when I boot it from an actual CDROM drive. It also boots fine over PXE, I can see FreeDOS being booted up etc. The problem is - once

Hi guys, We are using syslinux (memdisk) and gpxe already for a while. Also got a working winpe boot method by means of pxe. Which basicly is a dd of an 'recovery partition' where winpe.wim is on. That method isn't really the most efficient way, cause its loaded into memory twice. We are going to do a major windows 7 deployment soon and i'm looking for the most efficient way of

H. Peter, three simple commits here[1] (for_hpa branch). Gert, sample binaries are here[2]. --- mdiskchk: Add --no-sequential mode It might be useful to suppress MDISKCHK.COM's classic behaviour of probing all BIOS drive numbers in search of MEMDISKs. Some BIOSes might not enjoy being probed. --- memdisk: Correct El Torito termination response Two

Just a slight poke regarding the MEMDISK and MDISKCHK.COM possibilities available here[1]. Review by non-hpas is welcome, too. Thanks! - Shao [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ mdiskchk_enh2

Hi all: I create one share named gr?zer but the share can?t be accessed.I looked into the log, and find the share name will be transformed to upper case and then lower case. The ASCII can be transformed in between successfully, but German can?t. It leaded to access failed. I also tried the upper case share gr?zer, and it works successfully. It seems the lower case can?t be transformed back

On 7/6/2014 01:55, Ady wrote: > > I can see 1 branch in Shao's git repo that might be relevant: > > mdiskchk_win > > [quote] > > mdiskchk.exe will be the Windows counterpart for the DOS version > mdiskchk.com. The purpose is to be able to scan low memory for > instances > of Syslinux' MEMDISK and report these instances' parameters to a > user

Thus the rub: The exe seems to have disappeared from winbin as well. It's there, but downloads as a zero-byte file. > Date: Sun, 6 Jul 2014 22:40:21 +0200 > From: herbszt at gmx.de > To: sha0.miller at gmail.com > CC: syslinux at zytor.com; jml9904 at hotmail.com > Subject: Re: [syslinux] mdiskchk and WinPE > > Shao Miller wrote: > > On 7/6/2014 01:55, Ady wrote:

> > Date: Sun, 6 Jul 2014 22:40:21 +0200 > > From: herbszt at gmx.de > > To: sha0.miller at gmail.com > > CC: syslinux at zytor.com; jml9904 at hotmail.com > > Subject: Re: [syslinux] mdiskchk and WinPE > > > > Shao Miller wrote: > > > On 7/6/2014 01:55, Ady wrote: > > > > > > > > I can see 1 branch in Shao's git repo

Hi, I am working on the diskless booting over Infiniband networks. At the moment we have created and implemented architecture which allow diskless booting of Linux nodes on x86, x86_64 and Itanium platforms. The system works by booting first small custom made Linux kernel of the Infiniband adapter ROM. The kernel has enough of infiniband stack to setup TCP/IP networking over infiniband. Then it

Hi Peter, I'm using isolinux and memdisk to create a multiboot rescue cd for personal use as described on Bart's page (www.nu2.nu). One boot item is to boot DOS 7.1 from Win98SE with a lot of other staff for emergencies. This DOS bootimage puts all necessary stuff into it's own ramdisk (XMSDSK). Some progs on the ramdisk needs access to floppy drive A: and unfortunately I've no