similar to: Booting a no-emulation image

Look into the original XP cd and see where NTLDR is located, then place it on your cd in the same directory and it 'should' work. I have created some 2000 XP boot cd's with integrated recent service pack's and they still boot. But I do that with cdrecord+original boot sector, not with any isolinux stuff... But I hope this help! -----Original Message----- From: G. Murali

Hello all, I plan to make an (emergency) multi OS bootable CD which contain: - Win98 boot floppy (create from Win 98 control panel, add remove program) - WinME boot floppy (create from Win 98 control panel, add remove program) - Linux boot disk - Win NT boot disk - Win 2000 recovery console - Win XP recovery console - Winternal Administrative Pak (ERD Commander etc) I am new to Linux and feel

I am using PXELINUX, ISOLINUX, and memdisk in my project (http://unattended.sourceforge.net/). When memdisk gained support for compressed images, I started using it because it is cool. I used gzip to compress floppy.img to create floppy.imz, and all was good. But now my users are complaining that they cannot use WinImage (a Windows floppy image editing tool) to edit my floppy.imz files. I have

Comments inline > -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Posted At: Thursday, November 14, 2002 1:40 AM > Posted To: Syslinux > Conversation: [syslinux] MSDOS not working: problem Solved > Subject: Re: [syslinux] MSDOS not working: problem Solved > > > G. Murali Krishnan wrote: > > > > In short: Is it possible to

This isn't strictly speaking a SYSLINUX release, it's a change to MEMDISK and mkdiskimage to allow the creation of hard disk images with DOSEMU headers. This should make it easier to create bootable DOS hard disk images under DOSEMU. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hello Where can I get example in assembly, using COM32 API ? I'm trying to make simple "Hello World" using COM32, but this code does not works 8-( org 0x101000 ; this number I get from comboot.doc _start: mov ecx,msge-msg mov ebx,msg mov ah,0x02 .L: mov dl, byte [ebx] inc ebx int 0x21 loop .L .Z: jmp .Z ; \infty loop msg: db "Hello World !" msge:

This message is from Luis F. Correia, who unfortunately could not post it himself to the list.... ---------------------------------------------------------------------------- -- Hi! I would like to thank you, H. Peter Anvin for creating this wonderful set of tools. The only thing that bothers me is the lack of proper examples in the docs. Syslinux and affiliates would certainly improve

Okay.. I'm pulling out my hair, not having much luck trying to get ISOLinux (syslinux) running on my IBM x345 Server... I want to put my boot (syslinux) and root files (lib etc for modules) on the CDROM and just boot off of it to use PartImage... Not having much luck though.. For testing purposes I'm using the boot floopy I created using "The Linux Bootdisk HOWTO" and it

Can someone address the boot once option. Is it to hard for syslinux to write a flag file to file system or the blank space after the mbr? .conf bootonce Lable /boot/flagfile or .conf bootonce Lable1 /boot/flagfileLable1 bootonce Lable2 /boot/flagFileLable2 bootonce Lable2 /boot/flagFileLable2 skip the default option if the flag file is 0 size. Write something to the

Since lot of people want this thing, I will try to take a stab at it. For now, I will hard code the menu in the code, and then somebody else can remove that restriction. May be we can add some kind of keyword to the config file which syslinux ignores and the comboot menu does something with it. I have one question about comboot: If I write a DOS program using C (compiled using watcom -3 -mt -osx

Is it possible to have a isolinux based boot CD, where one of the options is to boot off the network. This would mean, 1. The kernel that one boots into is on the network and not on the CD. So easy to make changes. 2. One does not need a 'PXE enabled' network card. - Murali

HPA, I believe that support to boot windows CD bootsectors was broken in 3.05. I have tested 2.13, 3.00, 3.02, 3.05, 3.06, 3.08, 3.11, and 3.20pre6. All versions >= 3.05 are broken. All versions <= 3.02 work fine with the same config. The error message I get is: ================================================================ IOSLINUX 3.20 3.20-pre6 Copyright (C) 1994-2005 H. Peter Anvin

Working on fixing lower-priority bugs that I didn't want to risk destabilizing the 2.07 release for: Changes in 2.08: * Add "timeoutcmd" to allow timeout to have a different action than just pressing Enter. * Fix bugs in the COMBOOT/COM32 command-line parsing. APPEND now works with COMBOOT/COM32 images.

Hello all, First off, thanks for the great work. I have recently added "more submenus" to a functioning advanced menu that only had one "submenu off of the main menu before" The addition of the new submenus has caused the main menu to not function correctly and I have been pouring over the code for several weeks and I just cannot see the error that I have introduced. This

Hi, Thanks a lot for your exceptional work.... I guess many people dealing with bootable CD's just could'nt do anything without isolinux... However I've got a small problem. In fact the problem is maybe due to my BIOS (Phoenix on an HP Vectra VL800), and maybe due to isolinux / memdisk, I don't know. Generally speaking, take any floppy, format it under Win2K, copy from your hard

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a project that uses syslinux to load the kernels from the CD to create disk and/or partition images. The process works great, but as I have been building newer kernel images with new disk and nic drivers, I have had users run into problems. Example: one users machine would fail at hotplug detection, creating a kernel with this feature off

This version contains a fix to mbr.asm, plus a version of Murali's menu system, but ported to gcc. Although gcc produces much bigger 16-bit code (since it's really 32-bit code with prefixes) I figured it would be much easier for people to deal with since it requires the configuration to be compiled in. That being said, it's a *very* powerful menu system, partially *because*

I guess this really isnt the right place to be posting this it's probably the best place for me to find the answer. I would like to know if any of you are doing windows 2000/2003 installs over PXE and if so how you had it setup. I've done some searching on google and mostly found info about somthing called RIS or RAS or whatever.... it required a windows box and thats not a option.. I

On the SysLinux page, there is a screenshot of "COMBOOT Menu System for SYSLINUX developed by Murali Krishnan Ganapathy" (Advanced Menu System). I was wondering where I might be able to download this menu system in full to work with? If you dont want to share, I understand, but I am really intrigued by this and want to learn more, and maybe make my own design if I can figure it out.

Does the COMBOOT stuff with 2.04 work correctly with function calls? or does one need to write it as one huge function? If memory serves me correctly, there was some problem if hello.c was modified to include additional functions, in an earlier version. - Murali