similar to: xen-unstable dom0 boot "Floppy drive(s): fd0 is 1.44M" 17apr05

Thanks for your response, and how would you suggest that one would fix that? It hangs in the boot process! woody ==================== From: Christopher Clark <christopher.w.clark@gmail.com> [Add to Address Book] [View Source] To: "tarawa1943@comcast.net" <tarawa1943@comcast.net> Cc: xen-devel@lists.xensource.com Subject: Re: [Xen-devel] xen-unstable dom0 boot "Floppy

Hi - daft one for Friday morning coffee break: I have been trying to mount floppies on a couple of CentOS5 servers - the usual "mount /dev/fd0 /mnt/floppy" (yes, /mnt/floppy exists!). On both servers, the mount command just doesn't come back and I have to hit CTRL-C. I have tried different media and also changed the floppy drive on one server, /dev/fd0 is seen as present on both

Trying to be not long, on x86 I have 3 floppies images boot, root-1, root-2 Booting from boot image with no problem, I try reading root-1 and root-2 image in raw format. Reading root-1 and root-2 is made from boot init script, using klibc-1.5.9 or klibc-1.5.10 with debian insmod patch, and a vanilia linux-2.6.24.7 root-1 and 2 images are smaller than 1440 kB and are made the same way with cd

It is now possible to build a bootable floppy image which contains HDT, with my patch applied to Erwans HDT branch: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871 Unpack the Syslinux archive and build whole Syslinux first, then cd to ./com32/hdt/ and make hdt.img $ make $ cd ./com32/hdt/ $ make hdt.img Now you have a 2.88 MB floppy image which

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 still trying to get kick-start centos in my vmware5 because pxe cannot find the pxe server. I do not control the dhcp or pxe server. I have both my kickstart file and my iso image for centos6.5 on my vmware datastore, but am trying to run my kickstart file from VMware guest. Can I tell the command line to run from the datastore in VMWare? Or must I convert my kickstart file to a

Hi, all I can't boot from local drive on some machines(thinkpad x200 and thinkpad x1 carbon) using syslinux 3.05 or syslinux 4.05. And i change localboot 0xffff to localboot 0x80, boot from local drive is available. I find "0x80 is the primary hard drive. The special value -1(0xffff) causes ISOLINUX to report failure to the BIOS, which, on recent BIOSes, should mean that the next

I have been trying to find the information by searching through the archives and google, so I am sorry if this question has been asked before I just have not been able to find an answer. I have a syslinux boot floppy which loads to the boot prompt, I wish to load a .gz image which is on my hd0 0 by using memdisk as the kernel. I have tried to kernel memdisk append root=/dev/hd0 0 (also just

After formatting a floppy to MSDOS format and using syslinux /dev/fd0, I successfully installed ldlinux.sys to the root directory of the floppy. Then I created a syslinux.cfg under the root directtory of this floppy to load the linux kernel in my first hard disk, 3rd partition, boot folder. The file system of this partition is ext3. The floppy has a FAT file system. This config file is listed

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a

Hi All, I am trying to attach floppy virtual image to Windows domU. Either it is not attaching or domU is not showing floppy drive? domU config: 1. disk = [ ''file:/root/xenwin.img,hda,w'', ''file:/opt/Windows-Xp.iso,hdc:cdrom,r'', ''file:/root/win-boot.img,fd:floppy,r'' ] boot = "cda" In above format the window domU is booting but

I am trying to install the binary version of xen 3.1. When I boot, after some console output, I get the following: :: Loading Initramfs scsi_mod: no version for "struct_module" found: kernel tainted. SCSI subsystem intialized :: Running Hook [udev] :: Loading udev...input: AT Translated Set 2 keyboard as /class/inpt/input0 done. :: Running Hook [keymap] :: Loading keymap...Cannot find

I have tried "LOCALBOOT -1" , it still didn't work. ? 2014?02?25? 12:44, Gene Cumm ??: > On Mon, Feb 24, 2014 at 10:27 PM, ?? <lei.xia at cs2c.com.cn> wrote: >> Hi, all >> >> I can't boot from local drive on some machines(thinkpad x200 and >> thinkpad x1 carbon) using >> syslinux 3.05 or syslinux 4.05. >> >> And i change

Hi, I suspect this bug has already been reported, but here it is just in case: the bootable floppies I produced with syslinux 2.10 (just by running 'syslinux /dev/fd0') are not able to 'remember' the parameters I pass at the boot prompt. Namely, to boot a USB pen from one of my floppies I pass something like boot: MoviX MEDIA=usb (where MoviX is the boot label) but the usb boot

I am trying to get a programmable database working, and what I see as the only solution is a prog like access via wine. The problem is my computer that I wish to install it on has no floppy drive, and this copy (the first version?) comes with about 10 floppies. -- John R. Sowden AMERICAN SENTRY SYSTEMS, INC. Residential & Commercial Alarm Service UL Listed Central Station Serving the San

On bootup, it seems CentOS automatically mounts the floppy drive to /media/floppy. Is there a way to stop this from happening, short of removing the floppy drive from the system (as I don't use it)? Thanks, Ash Christopher -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, i think this message should be removed ;) paradigm:~# umount /mnt2 paradigm:~# mkdosfs /dev/fd0 mkdosfs 2.5 (07 Jan 2000) paradigm:~# /tmp/syslinux /dev/fd0 paradigm:~# sync paradigm:~# mount /dev/fd0 /mnt2 VFS: Can't find an ext3 filesystem on dev fd(2,0). Flo -- Florian Lohoff flo@rfc822.org +49-5201-669912 Why is it called "common sense"

I have the same problem. I can not boot a floppy disk. Once I did it but no longer I can do this. I think there is some problem in the new versions of PXELinux. -----Original Message----- From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On Behalf Of Quinn Plattel Sent: Thursday, September 28, 2006 7:04 PM To: syslinux at zytor.com Subject: Re: [syslinux] problem booting

Hello, when testing FreeBSD-7.1-BETA i discovered that the floppy disk controller doesn't work correctly. Trying to format a floppy (perhaps with bad blocks) i get: Processing fdformat: ioctl(FD_FORM): Device not configured instead of the normal E letter. I then checked the same problem is present on FreeBSD-6.3 and it has been reported by Beech Rintoul (*) in 2006! Of course the floppy disk

Hi all, I try to boot an msdos system using pxelinux and memdisk on my PC engines Wrap-2.c card and I have problems with it This is what I see: PXELINUX 3.11 Debian-2006-03-16 Copyright (C) 1994-2005 H. Peter A boot: msdos Loading memdisk.... Loading images/msdos/msd622bd.dosim......................... Ready. dp83815: Setting full-duplex based on negotiated link capability. MEMDISK 3.11