search for: mtoolsrc

...g existing files, just omit # the two steps marked "Create fresh image" below. # General configuation IMAGE=`pwd`/lnx.img TEMP=bootsector.tmp MKDOSFS=mkdosfs MCOPY=mcopy DD=dd DISKSIZE=1440 # MTOOLS configuration LETTER=Q CONFIG="drive $LETTER: file=\"$IMAGE\" #TEMP" MTOOLSRC=~/.mtoolsrc grep drive.$LETTER ~/.mtoolsrc >/dev/null 2>&1 || echo $CONFIG >> ~/.mtoolsrc # ### Create fresh image $DD if=/dev/zero of=$IMAGE bs=1k count=$DISKSIZE $MKDOSFS $IMAGE # ### Create fresh image $MCOPY ldlinux.sys $LETTER: # values from syslinux.c (calculated and conve...

...mknbi-1.4.0 # newer seems to have trouble w/ syslinux...? syslinux-3.08 etherboot-5.4.0 make the tagged NBI image: TFTP_ARCHIVE=/tftpboot rm -f /tmp/net-boot.img drivex='drive x: file="/tmp/net-boot.img"' ( grep -v -i "drive.*x:" ~/.mtoolsrc 2>/dev/null ; echo "$drivex" ) > ~/.mtoolsrc.new mv -f ~/.mtoolsrc.new ~/.mtoolsrc mformat -C -t 80 -s 36 -h 2 x: mcopy $TFTP_ARCHIVE/pxelinux.cfg/default x:syslinux.cfg mcopy $TFTP_ARCHIVE/{vmlinuz,miniroot.gz,boot.msg,logo.16} x: syslinux /tmp/net-boot.im...

Hi, I've got a couple of questions, I'm trying to get syslinux 2.10 to work on my Apacer Handy Steno TN202 128MB flash drive, I'm getting... root at will # syslinux /dev/sdb1 Total number of sectors not a multiple of sectors per track! Add mtools_skip_check=1 to your .mtoolsrc file to skip this test ...but if I try the same command on a mandrake box the syslinux command is successful. The syslinux version on my Mandrake 10 box is 1.76. Has anyone come across this problem? is this a known problem? Is this a problem with my Flash drive? what files does syslinux actua...

...nx spotless: clean - rm -f *.lss *.c32 *.com + rm -f *.lss *.c32 *.com hdt.img rm -f *~ \#* install: -include .*.d + +hdt.img: hdt.c32 floppy/hdt.cfg $(topdir)/mtools/syslinux $(MODULES_ALIAS_FILE) $(MODULES_PCIMAP_FILE) $(PCI_IDS_FILE) floppy/mtools.conf + rm -f hdt.img + MTOOLSRC=$(PWD)/floppy/mtools.conf $(MFORMAT) -v HDT -f 2880 -C a: + $(topdir)/mtools/syslinux hdt.img + MTOOLSRC=$(PWD)/floppy/mtools.conf $(MCOPY) hdt.c32 $(MODULES_ALIAS_FILE) $(MODULES_PCIMAP_FILE) $(PCI_IDS_FILE) a: + MTOOLSRC=$(PWD)/floppy/mtools.conf $(MCOPY) floppy/hdt.cfg a:syslinux.cfg +...

...t /dev/sdc1 /mnt/stick c. cp rhas3u2/isolinux/* /mnt/stick where rhas3u2 is the RHES AS 3 update2 CD mount point d. cp /mnt/stick/isolinux.cfg /mnt/stick/syslinux.cfg e. cp /rhas3u2/images/pxeboot/initrd.img /mnt/stick/ f. umount /mnt/stick g. echo "mtools_skip_check=1" >> /root/.mtoolsrc h. syslinux /dev/sdc1 When I took this memory stick to another PC, I can see the hard disk device (OTi6828) at the BIOS level - Boot option. But after selected this in the boot option, save and reboot, the system reports: PXE-E61: media Test failure check cable PXE-M0F: Exiting Intel Boot Agent...

Hi, I'm sorry to bring this up again but I can't quit get this too work. I'm trying to build a 2.88 floppy image so that I can use PXE to load Ghost. I'm useing the following to get a copy of the bootsector: dd if=/dev/fd0 of=bootblock bs=512 count=1 Then I build the image file with: mformat -C -t 160 -s 18 -h 2 -B bootblock x: Then use mcopy to put the required

Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25" and a 3.5" drive, both are plugged in, but in the BIOS, all I see is the 3.5". Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor