search for: xmsdsk

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

...i 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 chance to modify this behavior because I've only the Exes. While memdisk use A: the real floppy is assigned to B: and that is my problem. So I've read all docs and searched through the whole mailing li...

Hi, Just FYI: I've create a template disk image + small shell script for creating a multi-disk linux boot floppies for kernels and/or initrd's with a size > 1.44 MB. It's based on FreeDOS Beta 8, the XMSdsk ramdisk and Loadlin: http://www.rocklinux.org/people/clifford/MDLBL/ I primary wrote it for ROCK Linux <www.rocklinux.org> but it might be usefull for everyone who wants to boot larger (2.5) kernels from floppies. yours, - clifford PS: Linux-Kernel and FreeDOS-Dev List members: I'm...

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

Hi list, I've used sys & pxelinux now many times, it's really a useful toy. I found esp. syslinux very helpful as it allows to COMPLETELY boot from multiple disks. However, I could never use a 'vanilla' syslinux for that. I'm doomed to use Distributor patched versions, which I don't really like. Why is that? Read on: Well, I can't manage to boot of a 1.44 MB