similar to: syslinux 440D error

Hi. I'm trying to install the latest version of syslinux on a FAT12 partition on a 16M Flash disk. However, despire reformatting, repartioning, and running both lock c: and fdisk /mbr, I keep receiving an "ERROR 440D: Unable to lock drive for exclusive access" message. Do you have any suggestions on how to bypass this problem? Please respond ASAP. Thanks, Mario Di Giacomo

Hello HPA, I think on harddisks, Syslinux is going to lose somehow from other bootloaders like LILO, Grub and others. However, SYSLINUX is still VERY usefull for removable media like diskettes, Zipdisks, USB Flash keys, etc.. I don't know if the fact that Syslinux is now installed using blockmapping is really breaking the usefullness for harddisks. You already mentioned system attribute

I've recently returned to working on FreeDOS again after quite some time, and read about an unmerged MEMDISK branch that allows to boot DOS-based ISOs. This seemed quite usefull to me as it allows for faster modifications to my code/scripts/disklayout. The general idea was to install Syslinux 3.83 to harddisk, then add the modified Memdisk from that boot-land forum, as well as my ISO. In

Can someone tell me if syslinux will work on a harddisk ? I have a 4mb flash device that plugs into the IDE connector on the motherboard, and i'm trying to get syslinux to work with it, so I can load a Linux kernel and an initrd. I'm not having any luck with it. Then it dawned on me that the boot loader in syslinux might be expecting a floppy drive rather than an atapi hard disk. Any

Hello, I'm trying to create and boot a Win98SE-DOS OS through Hard Disk emulation. My src files are from a Win98SE 1440K floppy image file, with a x86 boot sector (dl'd from the net - I have no floppy drive and a slow net link 3.2KB). I don't know what to put into the partition boot record of my image and how to load dos.bss properly (the docs explain for floppy images not for HD

I'm running into some issues with regard to isolinux and memdisk, and am not sure where to ask/look in the best way possible. These are DOS-related issues. So here goes: * Can MEMDISK map a imagefile (compressed? harddisk?) to more than (and/or beyond) 4GB of memory? Say you'd have 8/16GBGB and want 4GB available to the user so might as well use the other 4/12GB for MEMDISK. Or max

(Sorry, Outlook webmail prohibits me from proper replying/quoting) >it has the nice effect that you can load the El Torito >CD-ROM driver. Which seems logical if you boot a kernel (like Linux, or Memdisk with an imagefile), but not when doing a local boot (diskette/harddisk) In other words: boot from cdrom, and if you then load a disk-image, eltorito.sys should load. If not loading a

As far as I know the only thing close to that, is to boot DOS from a floppy image (stored on the CD). The floppy image will contain the CD drivers and hence you can use DOS to access the contents of the CD. The floppy image is usually stored in the "boot sector" of the CD, or if you are using utilities like ISOLINUX, then they can be stored on the CD, and ISOLINUX/memdisk can boot

>information a bit closer; it'd find that it's marked accordingly. UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?). also something about EDD v1.1 and v3.0 specifications and setting bits to 1. Anyway, the driver works now on: BIOS -> cdrom ->

Sorry, I originally send this message to H. Peter only... -----Original Message----- Hi! Strangely enough, I have again the same Fujitsu-Siemens machine which (still) has the same darn PXE bug. This time I have tested it with Pxelinux 2.02 . Just to suite it to my specific needs, I have recompiled it, changed only this line: (2036) ;cfgprefix db 'pxelinux.cfg/' ; No final null!

Hello, I'm trying to boot a dos floppy stored on a disk image which is initially loaded over pxe using memdisk. I've created the disk image as follows: dd if=/dev/zero of=$IMGLOCATION/$IMGNAME bs=$(( 1024 * 1024 )) count=20 LOOPDEV=$(losetup --show -f $IMGLOCATION/$IMGNAME) MAJOR_MINOR=$(ls -l $LOOPDEV|awk '{print $5$6}'|sed 's/,/:/') DMSIZE=$(( $(ls -l

Hi, I have a mailgw running Centos where trendmicro(IMSS) is installed. it works perfectly. Now, the problem is it is running out of Harddisk. pls see below and pay attention to / file system (/dev/sda6), where only 1.3 gb is available. these are not Logical volums (LVM) [root at gateway 17141]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda6 9.7G 7.9G 1.3G

Yes, it is in the docs... All i need to do is load the memdisk image with the 'keeppxe' option. so, the default file should look like this: -------------------------------------------------------------------- default linux label linux kernel memdisk append initrd=client.ima keeppxe -------------------------------------------------------------------- That is all! Again, thanks for

Thanks for responses. I use GRUB as my bootloader in my hard disk now. I have a Windows in sda1, Ubuntu in sda3. If I want to install extlinux to boot Ubuntu, should I follow the steps below? 1. in Ubuntu, go to extlinux folder, run command ./extlinux --install /boot 2. create an extlinux.conf in/boot 3. cd ../mbr 4. cat mbr.bin > /dev/sda (or use dd if=mbr.bin of=/dev/sda bs=404 count=1)

Hi All, I am still having troubling with PXE. Thanks for replying Shao.I did follow ur suggestions and my results have improved a bit.From Ethereal and TCPdump, I can see that the client sucessfully dowloads the file pxelinux.0 from the server but stops at this point. here is the output of tcpdump tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:05:41.966864 IP

Hi all, I found a strange behavior in memdisk: I build an image of Windows 2000 (Fat32) with geometric of C=115 H=255 S=63. I testet it as a real harddisk and it works. I boot it to ram with memdisk initrd=w2000.img from my first harddrive, as discribed to boot with syslinux. It crashs with reboot, the time is to short to recognice the appearing letters before reboot. (Can I stop the screen?)

When I use syslinux version 1.75 to boot from floppy I get "Boot failed". The system specs are as follows: Manufacture : IBM Model : 4695-324 Bios: SurePath BIOS version GV3.030US Bios Date: 08/21/2000 Processor : AMD K6 II 300mhz RAM : 64MB This is an IBM Point of Sale terminal. I can get IBM DOS 5.0 and MS DOS 6.22 to boot from floppy with no problems. I have also booted a linux

On Thu, Feb 2, 2017 at 1:26 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Hi all, > > > > I have observed a problem where, under legacy BIOS booting mode on the > > DL360g9, memdisk fails to execute. The same mechanism works fine on the > > DL360g8. The system displays the below on the console and ceases to > > respond and must be

I've been attempting to create a bootable image thats double the size of the 2880 floppy disk. I can do the following to create a image that will boot with memdisk but i cant seam to get it to work with a larger size. What works... dd if=/dev/zero of=floppy288.img bs=1024 count=2880 mkdosfs floppy288.img ms-sys -1 -f floppy288.img mount -o loop floppy288.img /mnt

hi: i try to make some images for pxelinux+memdisk. the version i try is 2.0.6 and 2.0.7pre5 for 2.88M floppy image, first i make a 1.44M boot floopy, then use "winimage" to load the disk and transfer it to 2.88M format, then save the image. it seems a easy way to make a 2.88M boot image. for harddisk image, i use vmware to build a virtual machine with 20M harddisk, make it boot