similar to: Last call before syslinux 2.08

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

Hi, I want to use PXELINUX to load a DOS disk image which I currently use for Win2K/XP unattended installs. I want to move away from reliance on specific NDIS2 drivers and use the 3Com UNDIS3C driver instead. I have used this successfully to start the MSClient, but the problem is that the UNDI and PXE layer take about 90K of base memory, which means that WINNT.EXE has insufficent memory to run

>that image under B: or X: or whatever. This will allow us to cross the >size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect >memdisk to mount it, just that set things up so that DOS mounts it there. I'm using a 5MB image which emulates floppydisk. label test kernel data/memdisk append initrd=data2/test.img c=80 h=8 s=18 floppy problems are

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

perhaps the boot-from-cdrom code in Smart Boot Manager? Bernd >>> No, since booting from CD-ROM requires that the El Torito part of the BIOS is activated, which it won't be if it didn't boot from CD-ROM in the first place. ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing:

Hi I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy disk image 8440kB size. I've put FreeDOS kernel and bootsector into the floppy. Boot process goes fine with this command: isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy The problems begin when I try to run FreeDOS memory manager emm386 from the floppy image. my config.sys: ...

I'm trying to use this universal DOS TCP/IP boot disk available here: http://members.iinet.net.au/~bdriver/bootdisk/ It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

Hi there, I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... what is the problem can anybody tell me.. Regards, Yogesh

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

Hello list. I have configured a Linux box for booting from a Compact Flash instead of a Hard Disk, this is an IDE CF, Syslinux is on the MBR because it loads, when I put the the kernel file named as linux as it expects i load it but when I rename it expecting it to load the SYSLINUX.CFG it does not load the menu as I would like, I will put two images on that Compact flash in order to boot from

>The way the El Torito CD-ROM is going to look like to the program, is >that it looks like an additional hard disk which a very high drive >number (typically 9Fh or so); MS-DOS will normally ignore this since it >asks the BIOS how many drives there are and ignores the rest. >Does the error message come from UDMA2.SYS or...? > -hpa yes, it comes from UDMA2.SYS, it does a

This is a resubmission of my patch sent Jun 18, 2011 since it does not seem it was accepted. Please let me know if I am doing something wrong in how I am submitting this patch. Thank you. The below patch will swap order of sectors/track with bytes/sector to match diskette parameter table order (as pointed to by INT 1Eh). References: (additional ones available if necessary) 'System BIOS for

Hi: Thank you very much for creating this very useful program. I downloaded the DOS version because there was a suggestion in th isolinux website. I was not able to detect the cd-rom on my pentium II computer with Award BIOS 4.51 v 1.10. I tried to set the IDE i/o address but I am not sure where to get the i/o address information. I used the i/o address in the Win98 device manager IDE

Hello! I'm trying to boot with a remastered Knoppix 3.4 CD. I burned it with debugging and I get the following output: isolinux: Starting up, DL = 9F isolinux: Loaded spec packet OK, drive = 9F isolinux: Loading main image from LBA = DEADBEF0 isolinux: Sectors to load = D5B7 isolinux: Disk error BE, AX = 42F0, drive 9F A don't understand everything in it and I can't find enough

I'm considering the suggestion which was raised before about turning the debugging messages on by default in isolinux, or specifically, not building the non-debugging-messages version in the standard distribution. What do people think (especially distro maintainers?) -hpa

Hi James. Tanks for reply. It's been a hvile - I have no knowledge of this and lost interest in the matter. Now using Ubuntu 10.04 and allways latest Wine, but does not work. For others : Problem 1. IRDA protocoll must be working. First install in Ubuntu, so in Wine - I've heard ? The miniCD PolarIRDA (SigmaTel) contains Linux drivers, but I do not know howto..... On Mac it has to be on

isolinux: Extremely broken BIOS detected Yoper 2.1 --------- ISOLINUX 2.11 2004-08-16 isolinux: Loading spec packet failed, trying to wing it... isolinux: Extremely broken BIOS detected, last ditch attempt with drive = 9F isolinux: Disk error 01, AX = 4209, drive 9F Boot failed: press a key to retry... Helix 1.5 --------- ISOLINUX 2.04 (Debian, 2003-06-06) isolinux: Loading spec packet failed,

I've got $SUBJ almost working except for the DOS bit where the CD needs to be read. My pxe config: label Firmware menu label Update IPMI firmware kernel memdisk append keeppxe raw iso initrd=<isofile> The ISO is about 400Mb, and works fine when I boot it from an actual CDROM drive. It also boots fine over PXE, I can see FreeDOS being booted up etc. The problem is - once

Hi, I''m trying to run kernel compilations on a VM and my times are better than on the host machine. I''m using the time command, so I''m assuming its bugged. I try to use hwclock, and it spits out nothing. Is there an easy way to determine REAL time in a virtual machine? Thanks, David _______________________________________________ Xen-users mailing list