similar to: [PATCH] Support WinImage compressed floppies

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

Are their any plans to allow compressed floppy images in later versions of memdisk? Right now Im using isolinux/memdisk on a cd with quite a few floppy images, each image has a different purpose as you can imagine. Many of the floppy imaages are not 'full' and would benifit greatly from compression. Is their a standard(ish) way to compress a floppy image, maybe compress is misleading, Id

Haven't yet had a need for 10MB FDD images. The biggest I had to create was 5MB (5760kb). At that time I had to use WinImage to create the FDD image and it took me a while to figure out the correct settings. My notes state: "I'm getting 'missing FAT' errors in WinImage, and 7-zip complains about 'unexpected end'. The fix is to increasing the FDD Heads from 2 to 4 and

In other words: I'm suggesting to use WinImage as it also allows easy injection of new files *and* updating of already existing files. May I ask which vendor is distributing a DOS FW update that is 20MB? I'd like to see the files. Sometimes you just need the .bin/.rom and the actual FW update EXE and it would fit a 5MB FDD image. On Mon, Jun 18, 2018 at 2:03 PM, R S <rene.shuster at

Howdy to all, We've been using isolinux quite successfully for quite some time now, and I have come across a couple of laptops where isolinux balks at my config file.. Upon booting on this systems, the image background appears corrupted, and at the boot prompt, the following happens automatically. Unknown keyword in config file. Could not find kernel image: 1 boot: Any label input here

>that image under B: or X: or whatever. This will allow us to cross the >size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect >memdisk to mount it, just that set things up so that DOS mounts it there. I'm using a 5MB image which emulates floppydisk. label test kernel data/memdisk append initrd=data2/test.img c=80 h=8 s=18 floppy problems are

some times ago i was playing with coding, shannon theoremes and other stuff, i have tried without success to compress audio wave, and i have notice that simply oversampling audio material enacnhe a lot compression ratio i only take awav file, oversampled it by 20 tiimes and then compressi it using pkzip or rar. i don0't remember if i also do a CONSTANT PREDICTION, iony know that pkzip and

Greetings again, I am experiencing a lockup when ghost casting about 1 out of 5 client machines locks up. I don't recall if I was having this issue when I was using 3com pxe menus or not. I was wondering if the issue I am seeing could be caused by pxelinux since it basically is loading a Linux kernel then booting a MSDos.imz file. I cannot find any errors from the ghostcast side or the

Op 18-6-2018 om 20:19 schreef R S via Syslinux: > In other words: I'm suggesting to use WinImage as it also allows easy > injection of new files *and* updating of already existing files. > May I ask which vendor is distributing a DOS FW update that is 20MB? I'd > like to see the files. Sometimes you just need the .bin/.rom and the actual > FW update EXE and it would fit a

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

some times ago i was playing with coding, shannon theoremes and other stuff, i have tried without success to compress audio wave, and i have notice that simply oversampling audio material enacnhe a lot compression ratio i only take awav file, oversampled it by 20 tiimes and then compressi it using pkzip or rar. i don0't remember if i also do a CONSTANT PREDICTION, iony know that pkzip

Hi community, since more than one week I try now to boot my client via PXE. More informations about my equipment: Client: Board ASUS K8V-X SE Amibios with BIOS Revision 1501 (newest) Intel UNDI, PXE-2.0 (build 082) Server: Tyan Tomcat K7M Board with Eisfair 1.6.1 (www.eisfair.org) With exactly the same hardware unattended boots where working for more than one year perfectly without any

Hello, I encountered some unexpected behavior of unzip when using info-zip's unzip instead of R's internal program. Specifically, unzip("file.zip", list=TRUE, unzip=/usr/bin/unzip) produces incorrect output if the zip archive has filenames with spaces, and results in an error if the zip archive includes an archive comment or file comments. Here is some code to reproduce along

[Redirecting to the syslinux mailing list.] anutma at cmsd.bc.ca wrote: > First of all THANKYOU! > I am a tech at Coast Mountains School District, we have 6 techs and close to > 3000 computers. We have need using Neboot, and have recently switched to grub > using nbgrub. With Memdisk, life has been great (well easier) > What I am trying to do is create a small windows 9x

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

Hi, Apologies in advance if this is rather long winded ... I have a Windows 2000 DHCP/FTP/TFTP server, serving up a linux-based diags package using PXELinux. Everything is working fine, just like I'd expect. I also have some WinImage images of DOS floppy disks that I'd also like to serve via PXE. So I made up some simple menus using menu.c32 to serve both the floppy image and the

Sorry for makeing a new post, but I already erased my old mails. In the following I describe my Server-Situation (Sorry for my bad english) * I have a eisfair server http://www.eisfair.org with version 1.6.1 (newest) * I have a ISC-DHCPD 3 Server running * I have a TFTP Server running http://www.kernel.org/pub/software/network/tftp/ * I have Samba installed and a DNS Server is running My

Hello all, I've been following this project with interest, and have had great fun implementing Isolinux within the FreeDOS cdrom distribution. Since I'm not that an expert at Linux, I would like to know how I can *succesfully* generate a bootable image from a partition. Situation is like this: (640MB RAM on system) 60GB IDE harddisk, primary partition 1 win98 500MB extended partition

My system is hanging up when attempting to boot a floppy disk image. Does the following info tell any story as to what's happening? Loading ghost.imz ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000 0000000000020000 2 e820: 0000000000100000 0000000009ef0000 1 e820: 0000000009ff0000