similar to: Syslinux modification to not use mount, but write the file directly

@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

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

I tend to use the same tool-chain across various hosts so I made this very simple patch that allows you to pass the cross-compiler name to make ( e.g. make CROSS_COMPILE=i686-nptl-linux-gnu-). I'm not sure if patches should be attached or just pasted inline so I did both this time. BTW, it's relative to syslinux 4 but the same changes work with syslinux 3 although the patch won't

Hello list, My set up is almost complete in booting DOS through PXELinux, but I need to create a DOS boot image from (2 )DOS floppies. I've search the archives and google but didn't find any relavant info... My current set up now works with the standard setup (with one DOS floppy): kernel: memdisk append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS

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

I am trying to build a distribution without having to be root. The SYSLINUX installer typically needs 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

Please consider adding the following to the next R release (I understand that it's too late for R-2.1.0). It adds the menu item `Search R Site' in the `Help' menu in Rgui (which calls RSiteSearch() 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 @@

On Sat, Nov 17, 2018 at 1:54 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > Here are some comments and questions for you. > > > > > > > Thanks. > > > > I've have my scripts to a better state, including

On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > Here are some comments and questions for you. > Thanks. I've have my scripts to a better state, including installing/using qemu to uefi and legacy boot the usb stick for testing. It mostly works for me, but the "wget a tarball of binaries" step isn't going to sit well with

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

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

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

Hello All: I've recently had to provision some RHEL and CentOS VMWare instances. There was no network connectivity so I had to use a kickstart floppy and DVD iso rather than installing from our repository. To create the floppy I used the following: As root: dd if=/dev/zero of=floppy.flp bs=1k count=360 mkfs.vfat floppy.flp mount -o loop floppy.flp /mnt/floppy cp base_kickstart.ks

Just a quick question, in case I'm doing something really boneheaded that could be easily sorted out. I'm attempting to save() datasets on Linux (R 1.1.1) and load() them on Win2K (rw1011, fetched from CRAN today). I get the "restore file corrupted" message every time. I've tried saving with ascii=TRUE and FALSE, and the ASCII versions look OK (it's my impression

A non-text attachment was scrubbed... Name: not available Type: text Size: 5982 bytes Desc: not available Url : https://stat.ethz.ch/pipermail/r-help/attachments/19980216/81b069c2/attachment.pl

Hi, I am currently running Icecast 2.4.4 on Debian stretch and am using the info from the status-json.xsl to display some stats on my radio webpage. This works well. On the same website, I have also managed to display listener stats. I looks like this https://systrum.net/listeners.png To get this data, my developer created a php script containing the icecast admin credentials so that I can

On Thu, Dec 13, 2018 at 10:57 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @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).

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

Hi, I am working on a project where I have to move some parts files from an old Unix server. I have tared the files to floppy disc, but I can't mount them. After doing some reasearch I have found that the SCO Unix ver 3.2 uses a System V filesystem I think. From the article that I have read I need to add this filesystem to my kernel to be able to mount and read the floppy discs. Can