search for: imz

...nu.txt F3 hdtest.txt F7 FAQ.txt label linresc kernel linresc/rescue.lnx append initrd=/isolinux/linresc/initrd.gz root=/dev/ram0 label A: localboot 0x00 label a: localboot 0x00 label o localboot -1 label 0 localboot 0x80 label 1 kernel winpe.bin label 2 kernel memdisk append initrd=dosde.imz label 4 kernel memdisk append initrd=dosde2.imz label 3 kernel /i386/linux/vmlinuz-2.4.25 append initrd=/i386/linux/initrd acpi=off root=/dev/ram0 init=/linuxrc setkmap=us vga=788 label P kernel /isolinux/ntpasswd/vmlinuz append rw vga=1 init=/linuxrc initrd=/isolinux/ntpasswd/initrd.gz root=...

...ncing 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 ghost error file. Here is the pxelinux menu item I am choosing which I created. # MS-DOS Loader for GHOST Cast Server LABEL GHOST MENU DEFAULT MENU LABEL ^1. T12 Group 1 Session 1 KERNEL MEMDISK append initrd=imz/t12/T12-G1-1.imz stac...

...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 to have a separate imz file. Is it possible to do something like: label winstall kernel unattended/memdisk append initrd=unattended/winstall.imz /dell/2850/base.gho And then retrieve the /dell/2850/base.gho at a later time as a DOS...

...y dhcpd.conf looks like the following: PXE relevant things: DHCPD_PXE_3_NAME = test DHCPD_PXE_3_ACTIVE = yes DHCPD_PXE_3_KERNEL = unattended/memdisk DHCPD_PXE_3_INITRD = DHCPD_PXE_3_ROOT = DHCPD_PXE_3_APPEND = initrd=unattended/undis3c.imz The file "Default" (I think it is the syslinux.cfg file) looks like the following: # # Do not edit this file, edit /etc/config.d/dhcpd # Creation date: Fri Jul 31 21:24:53 CEST 2009 DEFAULT test PROMPT 1 TIMEOUT 150 DISPLAY pxelinux.cfg/boot.msg F1 pxelinux.cfg/boot.msg LABEL test...

I have been using memdisk (version 3.82) with no problem. I use it to boot my x86 computer with a compressed image I created/modified from an original DOS floppy bootable diskette. The original size of the image is 2.44 MB. I tried memdisk (version 3.83) and the bootable image gets uncompressed, bu the computer locks up and the las two lines in my screen are: Loading Boot Sector... Booting...

...F regarding PXE: START_TFTPD = yes TFTPD_ADD_ARGS = DHCPD.CONF (only PXE part) DHCPD_PXE_N = 1 DHCPD_PXE_1_NAME = test DHCPD_PXE_1_ACTIVE = yes DHCPD_PXE_1_KERNEL = unattended/memdisk DHCPD_PXE_1_INITRD = DHCPD_PXE_1_ROOT = DHCPD_PXE_1_APPEND = initrd=unattended/fetnd.imz I also tried the options "raw" and "bigraw" at the end of the append line, without success. fetnd.imz is the correct .imz file that works with my client. I tried this out with a floppy disk and everything was working. Generated (by my dhcp server) default file: # # Do n...

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 learned that WinImage does understand compressed floppies, and it does use a ".imz" suffix for them, but they are not the same as t...

...n be reproduced with the following: - Dell OptiPlex GX280, BIOS version A08 (the latest/last). - pxelinux.0 version 3.62 (or later). - Menu.c32 (I can use menu.c32 from 3.62 with pxelinux.0 from 3.61). Menu example: KERNEL memdisk APPEND keeppxe initrd=images/install/w98_aterm_xp_current.IMZ I haven't seen this problem on any other machine model (3.62 or later versions). We're stuck with a bunch of old GX280's for the rest of the year, after that they will be replaced. As long as we do not experience problems with any of our other PC models (17 at the moment), version 3.6...

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 0000000000008000 3 e820: 0000000009ff8000 0000000000008000 4 e8...

Hi, I'm trying to get the above working, without success so far: UNDIS.DOS refuses to load with an invalid NDIS stack message (from memory). keeppxe has some effect: it reduces the available conventional memory by 140 kbytes or so... still, the packet driver doesn't seem to find the interface. Does anybody have a working setup I could look at? -- Thanks, Feri.

It appears that the 3.74 completely broke the "keeppxe" directive -- not due to the command-line parser, but due to mishandling of the flag later. I consider this to be severe enough to do a short-cycle 3.75. As a result, I would like help with: a) are there any other bugs that snuck through? b) once I have a 3.75-pre1, I would really appreciate help testing it. The goal is to have

Hi, there now i am booting pxelinux menu32 with 2 boot images 1. DOS boot image 2. Thinstaion pxelinux and my directory structure is like this (Pxelinux with menu32) /tftpdroot/pxelinux.0 /tftpdroot/pxelinux.cfg/default /tftpdroot/dos.imz (DOS bootimage) /tftpdroot/memdisk (memdisk package) (Thinstation Pxelinux) /tftpdrooot/pxe/pxelinux.0 /tftpdroot/pxe/initrd /tftpdroot/pxe/vmlinuz /tftpdroot/pxe/otherconfiles /tftpdroot/pxe/pxelinux.cfg/default now the config from /tftpdroot/pxelinux.cfg/default is DEFAULT menu PROMPT 0 NOE...

...are on the server I have also tried uploading files to a ram-disk (using ramfs) but it didn't change anything but the download speed. TCPdump files -------------------------- I only exported a litte piece of the transfer. If there's something missing let me know. http://www.ludd.ltu.se/~imz/upload.txt http://www.ludd.ltu.se/~imz/download.txt

...ied -| uploading files to a ram-disk (using ramfs) but it didn't change -| anything but the download speed. -| -| TCPdump files -| -------------------------- -| I only exported a litte piece of the transfer. If there's something -| missing let me know. -| http://www.ludd.ltu.se/~imz/upload.txt -| http://www.ludd.ltu.se/~imz/download.txt -| -| -- -| To unsubscribe from this list go to the following URL and read the -| instructions: http://lists.samba.org/mailman/listinfo/samba -|

...s a leftover of PXELINUX. Even though the second run of XMSDSK succeeds, the cabinet extraction does not fully succeed. I decided to rule out PXELINUX, so instead I put GRUB4DOS 0.4.4 on the local HDD. I booted to the HDD and ran GRUB4DOS. From its CLI, I did: kernel /memdisk initrd /dellgx280.imz and encountered the same failures as the PXELINUX case. The "raw," "bigraw," "int," and "safeint" (default) modes all produce the same failure. Then I tested using GRUB4DOS' non-memory drive mapping technique, which also failed. To do this, I used an...

I have a USB flash drive that I'd like to image, and then load that image via pxelinux and memdisk. The flash drive was formatted under Windows 98 SE as FAT, and boots just fine on its own. The PXE boot process gets as far as loading the image via memdisk, but then when the boot process switches over to the RAM disk, it fails: [...PXE diagnostic information...] Loading boot

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

...isappears: MEMDISK 3.08 2005-05-19 Copyright 2001-2005 H. Peter Anvin E820: E820: E820: E820: Here are lots of Hex numbers E820: E820: E820: E820: E820: Ramdisk at 0x1fe73000, length 0x00168000 Command line: initrd=unattended/b44.imz BOOT_IMAGE=unattended/memdisk Disk is floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1977 bytes, allocating 2K Old dos memory at 0x9f800 (map says 0x9fc00), loading at 0x9f000 1588: 0xffff 15E801: 0x3c00 0x1ee7 INT 13 08: Success, count = 1, BPT = f000:79f9 Old: int13 = f00030e4 int1...

...> This CD works all right on some machines, but not on one of > the machines > > I have. > > Here is the complete MEMDISK output from the failing > machine. This is a > > Toshiba Satellite Pro 4600 laptop. > > > > Loading memdisk.... > > Loading e100b.imz.......... > > Ready. > > MEMDISK 2.07 2.07-pre5 Copyright 2001-2003 H. Peter Anvin > > E820: 0000000000000000 000000000009fc00 1 > > E820: 000000000009fc00 0000000000000400 2 > > E820: 00000000000e0000 000000000000e800 2 > > E820: 00000000000ee800 00000000000006...

Hi, I was wondering what's the best standard file extension for zipped DOS disk images and ramdisks. I've been using the following standard: .zi kernels, memtest86, memdisk .igz .img.gz zipped floppy images and ramdisks I'd rather have a different extension for ramdisks, maybe .zim zipped floppy images .zrd zipped ramdisks Any ideas ? It would also be nice if syslinux