similar to: Memdisk large IMA file

On Wed 5/5/2010 3:28 AM Miller, Shao wrote, ---------------------------------------------- Good day again Matthew, As per (c=80) * (h=2) * (s=48) * (sect_size=512) = 3,932,160 bytes = 7,680 sectors: For Windows, you might enjoy: - "DD for Windows" by John Newbigin and chrysocome[1] - "ImDisk Virtual Disk Driver" and "Zero and Random Device Driver" by Olof

Hi Community - I would like to request that SYSLINUX be extended to install on a filesystem image file on the Windows platform. This feature is available on Linux (option -t); however, on Windows SYSLINUX only installs with a raw device path. This feature would be use by another open source project. As an small incentive, I'll offer a small, token bounty ($50) for the developer that

I'm trying to install IMA (http://linux-ima.sourceforge.net/) on CentOS 5.5, but the shipped kernel does not support it. One solution is to install a 2.6.30 kernel, but I don't really like this idea. Does anybody has tried to install it? Regards, Andreas

Hi, bit of a newbie if I'm honest but was wondering if issue mentioned here: http://syslinux.zytor.com/archives/2006-October/007586.html was ever fixed? basically I have the same issue with the same machine. I have 4 different types of PC's here that i'm trying to boot by USB stick. It works fine on 3 of them, but on the 4th, A HP/Compaq dx2200 MT, memdisk will not boot the .ima

Hi I am trying to clone harddrive eg: centos, freebsd, openbsd..... any ima ge software suggestion for different os Thank you Send instant messages to your online friends http://uk.messenger.yahoo.com

Greetings, On 3/24/11, Akemi Yagi <amyagi at gmail.com> wrote: > I should note, however, that they are not for production use. > > Akemi Thanks Akemi very much for your always relevant and brilliant works. </rant> As an Indian, where "veda" repository of knowledge originated, I have always looked at every member of this list as a repository of knowledge.

Looks like I can't install syslinux's bootloader on an ntfs partition? What I'd like to do is remotely setup a bootloader to wipe the hard drive contents on old assets. I was kind of hoping, that I could install syslinux on a remote workstation, and then throw a dban image and the corresponding menu and syslinux.cfg files on the remote workstation and then reboot it and have the

Once again I feel horrible for asking something I feel is completely off topic for this group but everyone is so extremely helpful :( In my organization, we basically use Windows PE disks, to do our re-images, after some time and a lot of help from this group I was able to get a thumb drive to successfully work as a Windows PE bootloader, as well as some other utilities like wiping the hard

I am having the darnedest of times trying to get my WinPE to work off the syslinux loader. I used to use isolinux, and my isolinux config would just invoke the etfsboot.com file which i had renamed to loader.bin, and everything would work just fine off a cd. But now I'm trying to transfer all of my cd functionality to thumbdrives. With Syslinux, i have my syslinux.cfg file calling loader.bin

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

There is a bug introduced in autofs which breaks maps which are not stored in /etc. There is a patch but no official update yet. A patched version of autofs is available here: http://www.chrysocome.net/downloads/autofs-4.1.3-187.c4.1.i386.rpm See also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201084 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202860 John. -- John

On 3/11/2016 22:32, Phil Garcia via Syslinux wrote: > I would like to request that SYSLINUX be extended to install on a filesystem > image file on the Windows platform. This feature is available on Linux > (option -t); however, on Windows SYSLINUX only installs with a raw device > path. > > This feature would be use by another open source project. As an small > incentive,

I understand this isn't supported, but I was curious will it ever be, and also I use a hard drive wiping utility not dban and when i boot off my usb stick and wipe the hard drive it wipes the usb stick :( Matt

Unless someone already has a snazzy isolinux image that lets you select multiple makes and models to update bios's that's willing to share. I was curious if someone could tell me how to go from my isolinux.cfg into sub menu categories so instead of having one great big menu with multiple makes models and bios revisions, I can drill down into menu's until i get to the bios revisions to

> -----Original Message----- > From: Shao Miller [mailto:sha0.miller at gmail.com] > Sent: Saturday, March 12, 2016 10:39 AM > To: Phil Garcia <phil at thinkedge.com> > Subject: Re: [syslinux] Adding image file support for Windows > > On 3/12/2016 13:16, Phil Garcia wrote: > > On 3/12/2016 12:21, Shao Miller wrote: > > > >> On 3/11/2016 22:32, Phil

Anyone know the correct syntax for specifying a floppy image in the /tftpboot/pxelinux.cfg/default file? I am trying to use: label Dos Bootdisk MENU LABEL Dos bootdisk FDIMAGE discimage.img But when I select it the menu, I get a message saying "Automatic boot in 30 seconds" and nothing happens. I would use: label Dos Bootdisk 2 MENU LABEL Dos bootdisk 2

To make say a BIOS flash tool available over PXE, my impression is that a typical procedure goes like this: modify a generic FreeDOS 1440K disk image to contain the EXE and change the AUTOEXEC.BAT to launch that EXE, then make the 1440K IMG available on the PXE server. But more recent BIOS flash EXE are too large and won't fit on the 1440K, not even 3840K, so now we have to look into

[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

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

Olly Betts writes: > On Mon, Apr 11, 2016 at 09:54:36AM +0200, Jean-Francois Dockes wrote: > > The question which remains for me is if I should run xapian-compact > > after an initial indexing operation. I guess that this depends on the > > amount of expected updates and that there is no easy answer ? > > I think it's not obvious whether it's a good plan