similar to: unloading memdisk

Hi SysLinux, i'm using pxelinux.0 and memdisk to successfully boot dos on my PXE capable workstation. But aber the DOS boot I need to get access to Drive A: again. My DOS bootimage is putting all necessary stuff into it's own RAMdisk. How can I disable memdisk, so that it releases drive A: (does not necessarily free the allocated memory for it's RAMdisk ..) with kind regards / mit

Does SYSLINUX have any idea which DOS driveletter would be assigned to the disk it is booting from? At www.veder.com someone is trying to build a USB flash drive. However, FreeDOS does not seem to boot correctly from it (bootsector trouble maybe, or kernel itself is confusing drives), thus we're thinking of using Syslinux + Memdisk + bootimage, but somehow we want to be able to also access the

Hello Peter, is it possible to boot a CD-Image of a bootable CD (no disk emu) via pxe. I've build up the infrastructure to boot normal floppy images via PXE (under W2K and/or Netware). I have a ISO image of the bootable CD (1 tack TAO eltorinto with an a single boot sect -> bootimage is 2kB, ISO image about 600 MB) I suspect that a combination of MEMDISK and PXELINUX with activated UNDI

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

I am using PXELINUX, ISOLINUX, and memdisk in my project (http://unattended.sourceforge.net/). When memdisk gained support for compressed images, I started using it because it is cool. I used gzip to compress floppy.img to create floppy.imz, and all was good. But now my users are complaining that they cannot use WinImage (a Windows floppy image editing tool) to edit my floppy.imz files. I have

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

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

I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks

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

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:

I'm running into some issues with regard to isolinux and memdisk, and am not sure where to ask/look in the best way possible. These are DOS-related issues. So here goes: * Can MEMDISK map a imagefile (compressed? harddisk?) to more than (and/or beyond) 4GB of memory? Say you'd have 8/16GBGB and want 4GB available to the user so might as well use the other 4/12GB for MEMDISK. Or max

I will really hate myself if this has already been solved, i searched the archives but didn't really find anything pertaining to it. I have a 2.88mb dos boot floppy image, with ghost.exe, dos nic drivers, and dos system files. It works fine when burnt to a cd. As for the thumbdrive when trying to configure this hpghost.ima file to run from my syslinux.cfg menu, it works and boots up fine but

hi everyone. i have a small tftp/pxe server i use to install different OS's without having to burn countless cd's (not all the machines i work on support usb boot). until recently, these were mostly linux/bsd-based systems (plus freedos). recently i've been trying to deploy a network-based windows installation, by booting windows pe (3.1, the one based on win7) with memdisk and from

Hi! I have problem with MEMDISK, because when I load modules in NW Client32 using NIOS.EXE commands, computer is restarted :-( Not everytime, but manytimes. The problem is with MSDOS 5.0, 6.22 and FreeDOS too. But when I create in DOS another RAMDISK and copy all data from MEMDISK to new RAMDISK and change settings and PATH to new ramdisk, all work fine. Directly from floppy or from

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

Hi all, I am new to Syslinux and Memdisk. I setup a PXE boot server that services an image file via memdisk. This works very well. However, I am trying to figure out as to where memdisk the image puts in memory? On the wiki page it says: "MEMDISK simulates a disk by claiming a chunk of high memory for the disk and a (very small - 2K typical) chunk of low (DOS) memory for the driver itself,

So I have a few questions. I have already made the base part of making a windows TFTPD running with memedisk. So that part works, but what I was wondering, if there is a way to some how add an option to the config file. What I have is something like this: label winstall kernel unattended/memdisk append initrd=unattended/winstall.imz That all works great, However, for each image, I have

Hello, I am a *nix newbie I am trying to boot a DOS boot disk using PXE (to Ghost on windows images). We have an existing PXE server which successfully serves out PXElinux and Fedora builds based on that but my floppy disk image with memdisk isn't working I have tried a few different floppy images which people have posted as ones that work for them but I doubt the disk is the problem

Hi, I've got the same Problem. Not with WinMe but Win 98SE. But what I figured out is, that it doesn't realy apply to the Command.com rather to the Way the BootImage was created. It took me a long time to get my Hands on a Image with 2.8MB that's working. Since creating one my self, was allways failling. I downloaded the Bootutils 4.3 from 3com and used the Imageedit tools. With these

Good day again Daniel, So the first thing I did was to remove the >NUL for your XMSDSK line and put a PAUSE after it in AUTOEXEC.BAT. That way, I could see the error message: *** XMS RAMdisk v1.9I (FU - 08/98): XMS get free mem error. Then I noticed that if you run AUTOEXEC.BAT manually from the DOS CLI, XMSDSK actually succeeds! So that led to a new test: Duplicate the XMSDSK line. ...