search for: mcopy

...+ b/build/config/x86.cfg @@ -57,7 +57,7 @@ endif mkfs.msdos -v -i $(DOS_VOLUME_ID) -n $(DOS_VOLUME_LABEL) -C $(TEMP_BOOT) $(FLOPPY_SIZE) # syslinux is used to make the image bootable - syslinux $(SYSLINUX_OPTS) $(TEMP_BOOT) + syslinux $(SYSLINUX_OPTS) $(TEMP_BOOT) --directory /boot/syslinux/ mcopy -i$(TEMP_BOOT) $(TEMP_KERNEL) ::linux mcopy -i$(TEMP_BOOT) $(TEMP_INITRD) ::initrd.gz @@ -110,9 +110,19 @@ endif fi if [ "$(SYSLINUX_CFG)" != prompt ]; then \ - mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/vesamenu.c32 ::vesamenu.c32; \ - mcopy -i$(TEMP_BOOT) /usr/lib/sysli...

@Carl, I'll repeat what I said in my prior email: you don't have to keep looking, we already achieved what you want (considering that you are willing to "disregard" the screen problems and similar issues, at least for now, according to your own emails). In short: 1_ Re-read my email from 2018Dec05: www.syslinux.org/archives/2018-December/026247.html where I posted

...eds root to do loopback mounting, but if you have MTOOLS, you can use that instead. This seems to work so far: #!/bin/sh # A minimal replacement for /usr/bin/syslinux; assumes that ldlinux.sys # and ldlinux.bss are available in the current directory. You must # specify locations of mkdosfs and mcopy. You need not be root. The # image will be overwritten if it exists, and an empty boot disk image # will be created. To avoid overwriting existing files, just omit # the two steps marked "Create fresh image" below. # General configuation IMAGE=`pwd`/lnx.img TEMP=bootsector.tmp MKDOSFS...

...tpboot 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.img # this is bootable as is... # make a "tagged" etherboot image from the floppy... # this will only be bootable inside etherboot......

I have been having problems with syslinux not working on one system. The error message was "failed to create ldlinux.sys". I checked and mcopy was installed. But upon further investigation I finally found the problem. I were starting syslinux for python (2.4) and in the python code I made it ignore SIGNCHLD. It turns out that this signal state was inherited by syslinux and it made waitpid() in syslinux.c fail which caused the error messag...

...JCOPY = objcopy -AR = ar -NM = nm -RANLIB = ranlib +LD = $(CROSS_COMPILE)ld +OBJDUMP = $(CROSS_COMPILE)objdump +OBJCOPY = $(CROSS_COMPILE)objcopy +AR = $(CROSS_COMPILE)ar +NM = $(CROSS_COMPILE)nm +RANLIB = $(CROSS_COMPILE)ranlib GZIPPROG = gzip PNGTOPNM = pngtopnm MCOPY = mcopy -------------- next part -------------- A non-text attachment was scrubbed... Name: mconfig.diff Type: application/octet-stream Size: 833 bytes Desc: not available URL: <http://www.zytor.com/pipermail/syslinux/attachments/20100315/7f6872fe/attachment.obj>

...$ make hdt.img I don't know which way is preferred. - Gert Hulselmans $ diff -u ./MCONFIG.old ./MCONFIG --- ./MCONFIG.old 2009-10-03 21:16:38.172614946 +0200 +++ ./MCONFIG 2009-10-03 21:18:26.956615419 +0200 @@ -52,6 +52,8 @@ RANLIB = ranlib GZIPPROG = gzip PNGTOPNM = pngtopnm +MCOPY = mcopy +MFORMAT = mformat com32 = $(topdir)/com32 $ diff -u ./com32/hdt/Makefile.old ./com32/hdt/Makefile --- ./com32/hdt/Makefile.old 2009-09-30 06:32:42.000000000 +0200 +++ ./com32/hdt/Makefile 2009-10-03 23:06:49.356614719 +0200 @@ -27,6 +27,11 @@ OBJS = $(patsubst %....

> > > I think add some lines around here: > > > > > > https://salsa.debian.org/installer-team/debian-installer/blob/master/build/config/x86.cfg#L113-115 > > > > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/vesamenu.c32 > > > ::vesamenu.c32; \ > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libcom32.c32 > > > ::libcom32.c32; \ > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libutil.c32 > > >...

...k append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS floppies with the dd command or anything that works. I've tried pretty much everything that I can think of, but still not success. Here's a list that I tried: mkdiskimage floppy.img mkdossfs floppy.img mcopy a: /mnt/img syslinux dos.img If anyone can provide any suggestion/help, I'd really appreciate. Thanks, Joel

...ou in this context? Debian? D-I? The Syslinux > > > Project? Other? > > > > Debian. > > > > I think add some lines around here: > > > > https://salsa.debian.org/installer-team/debian-installer/blob/master/build/config/x86.cfg#L113-115 > > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/vesamenu.c32 > > ::vesamenu.c32; \ > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libcom32.c32 > > ::libcom32.c32; \ > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libutil.c32 > > ::libutil.c32 ; \ > &g...

On 07/15/2014 06:57 PM, Ady wrote: > > Finally, when using MEMDISK to boot floppy images, these images > should not use partial "cylinders". In other words, use exact CHS > values for floppy images, instead of building the images by means of > the desired megabytes size. Then use the selected CHS values as > parameters for MEMDISK. > If you have a proper set

...earch() on the input string). Best, Andy --- R-beta/src/gnuwin32/rui.c 2005-03-06 09:41:40.000000000 -0500 +++ R-beta-new/src/gnuwin32/rui.c 2005-04-12 08:21:55.001824500 -0400 @@ -65,7 +65,8 @@ static menuitem msource, mdisplay, mload, msave, mloadhistory, msavehistory, mpaste, mpastecmds, mcopy, mcopypaste, mlazy, mconfig, mls, mrm, msearch, mhelp, mmanintro, mmanref, mmandata, - mmanext, mmanlang, mmanadmin, mman0, mapropos, mhelpstart, mhelpsearch, + mmanext, mmanlang, mmanadmin, mman0, mapropos, mhelpstart, mhelpsearch, + msearchRsite, mFAQ, mrwFAQ, mpkgl, mpkgm, mp...

...e ldlinux.e64 from the tarbal or package? > > What is "upstream" to you in this context? Debian? D-I? The Syslinux > Project? Other? Debian. I think add some lines around here: https://salsa.debian.org/installer-team/debian-installer/blob/master/build/config/x86.cfg#L113-115 mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/vesamenu.c32 ::vesamenu.c32; \ mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libcom32.c32 ::libcom32.c32; \ mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libutil.c32 ::libutil.c32 ; \ > > > > > > I'm trying to follow t...

...oo 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 files into the image. I mount the image on the loop back device and everything looks ok, but when I try to boot a machine from this it just moans "invalid system disk". The disk I am useing for the bootsector and to copy the files from is a working Windows 98 startup...

...t; > What is "upstream" to you in this context? Debian? D-I? The Syslinux > > Project? Other? > > Debian. > > I think add some lines around here: > > https://salsa.debian.org/installer-team/debian-installer/blob/master/build/config/x86.cfg#L113-115 > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/vesamenu.c32 > ::vesamenu.c32; \ > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libcom32.c32 > ::libcom32.c32; \ > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libutil.c32 > ::libutil.c32 ; \ I'm confused. Why exactl...

I want to eufi boot this image: http://cdn-fastly.deb.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz there is a bug against it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913523 I'd like to fix the resulting usb stick for my use, and also fix it in a way that can be used to fix the upstream bug. I'm trying to follow the guids

If there a way to may samba "handle" files like ftp does during ascii transfers. Changing the ^m to unix end of line markers

R 1.4.0 is now sinking into feature freeze, and we'd like some help testing it under Windows. Duncan Murdoch and Uwe Ligges have already volunteered. I've put a copy of SetupR140.exe at http://www.stats.ox.ac.uk/pub/bdr/RWin Also in that directory is a file TESTING suggesting some tests, not all of which have been run on this build. As the graphics internals have been changed a lot

I reimplemented the syslinux.c such that it writes the file directly to the disk or disk image. Would you be interested in taking it into syslinux? I have to ask because if you'd accept it, I need to make sure my employer has no objection. They have no interest in the program, but I have to go through the procedure anyway.

...tupid) option */ @@ -240,7 +241,7 @@ int main(int argc, char *argv[]) } /* This command may fail legitimately */ - system("mattrib -h -r -s s:/ldlinux.sys 2>/dev/null"); + ret = system("mattrib -h -r -s s:/ldlinux.sys 2>/dev/null"); mtp = popen("mcopy -D o -D O -o - s:/ldlinux.sys", "w"); if (!mtp || (fwrite(syslinux_ldlinux, 1, syslinux_ldlinux_len, mtp) @@ -313,7 +314,7 @@ int main(int argc, char *argv[]) /* This command may fail legitimately */ sprintf(command, "mattrib -h -r -s %s 2>/dev/null&quot...