similar to: Trouble with Superfloppy format

Mattias Schlenker <ms at mattiasschlenker.de> wrote: > Is ifcpu.c32 or ifcpu64.c32 sufficient for your task? No. I need to detect a given machine by something unique. E.g. the MAC-address of the Ethernet Interface CPU-id or such, because I have custom kernels for all the machines. Sven -- If you can spend five minutes on the Internet and do not run Linux, you're a genius. (Dirk

Ich werde au?er Haus sein von 18-06-99 Bis 28-06-99. Ich werde Ihre Nachrichten nach meiner R?ckkehr beantworten. Bitte wenden Sie sich in dringenden F?llen an: Frank R?seler, Tel: MON 3855 Uwe Spiess, Tel: MON 3743 Guido Zimmermann, Tel: MON 3962 Ferdinand Gro?, Tel: MON 2368 lieber Gru? Axel Hellmig

Hello, on a somewhat recent machine (Dell T1600) I'm unable to use my usual setup (pxelinux as a boatloader also for local OS - typically windows). The BIOS is capable of using UEFI, but this is turned off. Unfortunately all I get is a message telling me that pxelinux is unable to boot from local disk. The config entry looks like this: LABEL local MENU LABEL OS installed on local disk

Hello, up to now I have been using plain pxelinux with symbolic links (IP or MAC-Address) to the machine dependent defaults. This has been working fine with minimal differences in the configuration files: --default-lenny-- DEFAULT lenny INCLUDE pxelinux.cfg/include-options INCLUDE pxelinux.cfg/include-kernels ----------------- --default-squeeze-- DEFAULT squeeze INCLUDE

Hello, setting up Meetme was very easy. I jut added the MeetMe Application to an internal extension to be reachable by SIP and to an external extension to be reachable by ISDN. What I don't understand however is how to call somebody and drop him to the conference? I'm using Asterisk 1.4 from Debian lenny Sven -- "In the land of the brave and the free, we defend our freedom with

I try two ways to use syslinux for USB key (2GB USB key), and one approach can boot from machine, another approach can not. Could you review the following steps and tell me why #2 can not boot? Thanks very much! approach #1 steps: mkfs.vfat -F 16 -n USB /dev/sdb -I (pay attention, it uses "-I" here) syslinux /dev/sdb (pay attention, it is "sdb", not "sdb1" here)

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

On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao Miller, Kenneth Davis, wrote: > [...] Thank you all for your responses. You helped me solve my problem. For anyone else that runs into similar trouble and finds this thread, here follow summaries of what I've learned. To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy images booted via MEMDISK.

Hello, after upgrading from Samba 3.5.6 to 3.6.5 I encounter some strange NT_STATUS_ACCESS_DENIED trouble when trying to access group readable directories from Windows 7 or Windows 2008 Terminal Server. Very strange stuff is that it works fine using smbclient from a Linux machine using the same userid and Kerberos authentication. The Server is fully integrated into active directory and uses

On 07/08/2014 05:55 PM, H. Peter Anvin wrote: > On 07/08/2014 03:05 PM, Alexander Perlis wrote: >> >> Question: what's special about the transition from 8203KiB to 8204KiB? >> Both have CHS=8/64/32 and both involve a fractional end cylinder. > > Fractional cylinders with floppy disks is almost certainly a very bad thing. > Agreed, but that doesn't appear to

I used syslinux 4.03 for my brand new usb-stick (16GB FAT32, no Partition Table). It works, but on some computers i get "boot error". My investigation reveals three bugs in the boot code. Int 13 function 8 destroys the contents of register ES. Ah, now it is corrected in version 4.04 pre 5. Well done. I am happy now. But there are still other bugs. Look on version 4.04 pre 5,

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

Hi, I'm not sure if this issue is due to a samba behaviour, but I try to post this question... I've joined my (virtualbox) ubuntu in my AD windows domain, following Ubuntu instruction . So it seem almost everithing is ok, my login authentication seem doing fine, I perform it with 'MYDOMAIN\myuser" without problem. When I browsing my network and clikking on my server share

Hi, this is a forward from the debian bug tracking system, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595170: "syslinux for Windows provides the options -m (write an MBR) and -a (make partition active). These options make it easy to provide instructions for Windows users to make a bootable USB drive: just run "syslinux -m -a" on the drive, then drop some files on the drive

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

Hello, CONFIGURATION Syslinux "old": 3.36 Syslinux "new": 5.01 (B)LFS i686-pc-linux-gnu 3.8.0 Machine #1: ASUS P5E-VM HDMI. Latest BIOS. circa 3 years ago. Machine #2: ASUS P8H77-I. Latest BIOS. This year. USB Flash stick: Kingston "Data Traveler" 4GB. Clean (blank) STRANGE (UNEXPLAINED) syslinux BEHAVIOR DIFFERENCE Steps: 1. Set up KNOPPIX 7.05

> > I am still interested in improving the isohybrid wiki > and will watch for pointers to descriptions of the FAT > production process (with GRUB/GRUB2 if not with SYSLINUX). > > If no such descriptions appear within the next weeks, > then i plan to state in > http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI > > "The SYSLINUX project cannot yet provide

Greetings one and all. I'm a unix newbe....so deal with me here. I have a .iso copy of syslinux 1.67 (which actually might be ISOlinux??) that I boot from CD (ramdisk version...no HD needed)... but my version doesnt have the mkdosfs utility on it. I was looking for an executable that would work with this version... can someone point me toward such an animal??? :Pat

Hi there, I try to boot from an USB Pen-Drive. This works fine on my Laptop, but when I try to change to the target machine it almost takes five minutes until the initrd (fairly big, 18MB) has been loaded. Any hints on how I could try to increase speed? The Bios has already been updatet to the most recent Version. Sven -- "Das ist halt der Unterschied: Unix ist ein Betriebssystem mit

Do you have an example on how I use this? My goal is to boot into DOS so I have access to my dos apps Den 22. dec. 2017 kl. 14.24 skrev Ady Ady via Syslinux <syslinux at zytor.com>: >> How can I boot into dos with different kinds of dos command with PXELinux? >> >> My menu is working fine, but I'm not sure what I should add to run into dos. >> >> My