search for: floppyb

...r. Not a problem, as the issue is that the bootsector needs to be in the root of the CD. Well if I do that then how do I spec that location properly in isolinux.cfg for the label tag? For example- this works for the floppy images / . ..../isolinux | floppya.img floppyb.img isolinux.cfg is like so. label 1 kernel memdisk append initrd=cdrom.img _________________________________________ The no workie part looks like this- So the i386 and .bin are in the cdroot and the imgs are under /isolinux /(cdroot) |.I386 |.ntboot.bin |..../isolinux |...

This is a minor tweak on 3.11-pre2. If nothing new comes up, I will release this as 3.11 probably early next week. -hpa

With windows, if your "virtual" floppy is drive B:, then windows will treat it specially. It will basically copy the contents into memory from real mode using int13h, knowing that it will not be able to access the device after it switches to protected mode. I asked a few days ago about support for making a memdisk image behave as drive B:, but got no answer. :-( We have our

...bde59907bba tools/examples/bochsrc --- a/tools/examples/bochsrc Thu Jun 30 18:41:11 2005 +++ /dev/null Thu Jun 30 18:59:08 2005 @@ -1,20 +0,0 @@ -#megs: 32 -#romimage: file=$BXSHARE/BIOS-bochs-latest, address=0xf0000 -#vgaromimage: $BXSHARE/VGABIOS-lgpl-latest -floppya: 1_44=a.img, status=inserted -floppyb: 1_44=b.img, status=inserted -# if you don''t use absolute paths below, bochs looks under the cwd of xend, -# which is usually "/" -#ata0-master: type=disk, path=/var/images/min-el3-i386.img, cylinders=800, heads=4, spt=32 -i440fxsupport: enabled=1 -ne2k: ioaddr=0x300, irq=9, mac...

hello, i have this problem : [y.moya@yves y.moya]$ cd /mnt/cdrom [y.moya@yves cdrom]$ ls 3Dfx SETUP.EXE _setup.dll autorun.pak hlinst.dll setup.bmp DATA.TAG SETUP.INI _sys1.cab data1.cab lang.dat setup.ins DIRECTX Worldcraft _user1.cab dsetup.dll layout.bin setup.lid Localize.cab _INST32I.EX_ autorun.exe dsetup16.dll os.dat sierra.inf