similar to: SYSLINUX 3.05 released

Displaying 20 results from an estimated 700 matches similar to: "SYSLINUX 3.05 released"

2005 Jan 14
5
Trouble with Syslinux 3.07 and USB-key
Hi, I've a usb-key that boot regularly on a PC using syslinux 2.09; well, this PC (a thin-client) at the moment is the only PC that can boot from USB in my office... and it usually booted oretty well, without any hacks... After changed to syslinux 3.07, it stopped booting, showing a simple "BOOT ERROR" message, nothing more... Reverting to syslinux 2.09, it restarted to work...
2004 Dec 22
3
Dummy question on Syslinux and MBR
Hi, I've seen that syslinux does include also a MBR record. But how can I install it on a HD under Windows? And how can I backup the previous MBR? Does syslinux help us on this task also? bye! -- Paolo Salvan _______________________________ X v i s i o n Via Vigonovese 123A 35127 - Padova - Italy +39 049 8709427 tel +39 049 8709426 fax www.xvision.it
2005 Jan 25
4
PXE floppy, PXELINUX and LOCALBOOT
Hi! A friend of mine has tried a PXE floppy (build from the new etherboot 5.3.12) to load PXELINUX.0; a menu voice of the pxelinux.cfg use the LOCALBOOT statement. Selecting this statement, the PC retry to boot from the floppy... is this normal? The user expected that LOCALBOOT would have tried the NEXT boot device (ie CDROM or HD), not the FIRST boot device (the floppy)... (note: this has
2005 Jan 16
3
Can I use....
Hi, Is it possible to create a boot floppy that I can use to start iso's that use say syslinux ? Dave T.
2005 Jan 25
1
Problems with isolinux.cfg
hi! I?m working on a projekt ( unattended.sourceforge.net ) This is using a linuxboot.iso My problem is the following: I opened up the iso with winiso, extrcat the isolinux.cfg, edited it with vi for windows as follows: # isolinux/pxelinux configuration file default unattended label unattended kernel bzImage # Add options (z_user=..., z_path=..., etc.) to this line. append
2005 Feb 01
4
PXE 0.99h stacks... any chance?
Hi I have searched the site, list archives, google etc and have not been able to find an appropriate answer so I am asking it here. Apologies if this has been answered already. I have a kiosk-style pc which I wish to remote boot to keep it quiet. This way I don't need a hard disk at all, keeping it truly silent as it has a passive cpu cooler. Unfortunately, it has no upgrade options. I
2005 Jan 14
1
Changing USB-key geometry from syslinux.exe?
I'm playing with syslinux 3.0x to get PC to boot from USB key... In particular, I'm giving a look at the "ZIP geometry hack" to get some more BIOS boot working with USB... Some question: - if we have a usbkey with a single partition, can we change the geometry without requiring to reformat the partition? Or is a reformat unavoidable? - at the moment we can use the "ZIP
2005 Jan 26
2
Multi-NIC network boot floppy+cd+hd+com with PXE and NBI support: does interest?
Hi! I'm preparing what should be a general "network boot" solution for the ones that needs to do network boot on PC without BIOS support / ROM chips. It supports both PXE (like pxelinux.0) and NBI images. I've prepared a precompiled multi-driver image that can autodetect and handle nearly 30 PCI and ISA NICs. My "remote boot kit" contains the same image in 4
2006 Jan 03
1
(no subject)
Hi all! ...As I'm the author of http://sourceforge.net/project/shownotes.php?release_id=190646 http://sourceforge.net/project/showfiles.php?group_id=80408 (for Steven: these two links are for the SAME file...) ...I'd like to say some comments, to let you understand what the peculiarities of my approch are... My approach is more minimalistic: etherboot have already the capabilities to
2005 Apr 06
1
Announce: Universal network boot floppy/cd/hd 5.4.0 released
Hi all, I've just released a new version of my universal network boot package, built from the just-released Etherboot 5.4.0 Features: - It now supports both pxelinux (and others PXE second stage loaders) and etherboot ".nbi" images. - Available in the following formats: - floppy image - CD ".iso" image - kernel-like image (usable with any kernel loader) for
2004 Oct 27
1
Passing one more file after initrd to the kernel...
Hi! I have a particular need... I'm not sure if this is the right place to ask, but surely here there are people that can say me if it is feasible or not... I'm working for a thin-client distribution (thinstation.sf.net); I want to boot it from various media (netowork, cdrom, hd, usb key...), and at the moment syslinux/isolinux/pxelinux are doing it very well... The problem is that the
2007 Mar 19
1
Delphi applications printing bug
Hi, I'm using Wine 0.9.27 and Ubuntu 6.06. I've problems when printing from Delphi Apps that use QReport (the default reporting engine for most Delphi versions), and after some hacking I've perhaps isolated the trouble: it seems that Delphi printing over a Canvas works only if I show the system PrintDialog or the PrinterSetupDialog befor printing, and I press OK in this dialog:
2004 Oct 25
1
Syslinux and USB support
Hi, I'm writing as I'm an happy user of syslinux/isolinux(pxelinux, as it has kade booting from floppy/hd/cd simple and reliable... (I've looked the tons of workaround developers had to develop to circumvent bugs BIOS bug in isolinux....) I think that next frontier for syslinux should be USB booting: it already works, but here also there are a lot of BIOS problem that a bootloader
2005 Jan 10
0
Re: Problems with loading ramdisk under SYSLINUX 3.05
Petr Vandrovec wrote: > Hello, > one of FreeDOS developers pointed out (in > http://www.vmware.com/community/thread.jspa?threadID=11324&messageID=109507&#109507) > that FreeDOS does not work under VMware when using ISOLINUX 3.0x. After > looking at their ISO image I downloaded syslinux-3.05, and there seems > to be bad bug: > > You have this in kernel.inc:
2005 Jan 10
0
SYSLINUX 3.06 released
Okay, let's hope *fourth* time is a charm... Changes in 3.06: * Fix typo that caused the ramdisk to load in the wrong place. Changes in 3.05: * New API function "shuffle and boot"; allows COM32 modules to load or construct (almost) arbitrarily complex objects, e.g. a kernel and its initrd/initramfs in pieces, and have the API core
2005 Jan 12
0
SYSLINUX 3.07 released
Let's try it again... *fifth* time is a charm? Changes in 3.07: * Fix chainloading (chain.c32). * Fix zlib build problem. Changes in 3.06: * Fix typo that caused the ramdisk to load in the wrong place. Changes in 3.05: * New API function "shuffle and boot"; allows COM32 modules to load or construct (almost) arbitrarily complex
2004 Aug 02
1
version 3.05 users %u change?
Hello I just upgraded my samba from 2.8 to 3.05 and the user profiles started storing in some strange way before it used to store in /var/samba/profiles/username/machine/ now it makes /var/samba/profiles/%u directory under that machine name . it seems like something in smb.conf chnged and %u variable works no more. Can someone help?
2005 Jan 09
3
"so old bootloader ..." with syslinux-3.05 on x86_64
Hi, I'm trying to install Fedora Core 3 on an AMD 64-based machine using PXE (via DHCP and TFTP). I've managed to get the machine to load the kernel over the network and start booting, but instead of loading the root fs from initrd.img (that I appended as a config via pxelinux.cfg), it loads the pre-existing rootfs on my harddisk. At the top of dmesg is the message: "so old
2017 Dec 22
4
codificación
Estimados compañeros me tiene loco un problema de codificación que no logro resolver. Importo un fichero cuyo nombre tiene acento. Pongamos por ejemplo "Adrián.doc". Escribo el siguiente comando: mdoc<-list.files(path = dest,pattern = "*.doc", full.names = TRUE) Entonces mdoc, además del path, se me presenta como: "Adria´n.doc" Aunque le quite la tilde con:
2004 Aug 03
1
Samba 3.05 pdc
I'm trying to connect a Windows 2000 workstation to my samba pdc domain. I have followed all the steps in the documentation to setup samba as a pdc, but I have not been able to connect any workstations to the domain. Does anyone have a example smb.conf file I can compare with mine. I checked the "log.smbd" and I'm getting the following messages when I tried to add a computer