search for: winboot

...lace the disk, a 000001C0 6E 64 20 74 68 65 6E 20 70 72 65 73 73 20 61 6E nd then press an 000001D0 79 20 6B 65 79 0D 0A 00 49 4F 20 20 20 20 20 20 y key...IO 000001E0 53 59 53 4D 53 44 4F 53 20 20 20 53 59 53 80 01 SYSMSDOS SYS€. 000001F0 00 57 49 4E 42 4F 4F 54 20 53 59 53 00 00 55 AA .WINBOOT SYS..Uª 00000200 F8 FF FF FF FF FF 04 00 FF FF 06 00 FF FF 08 00 øÿÿÿÿÿ..ÿÿ..ÿÿ.. So if that is where guestfish is looking for the partition table... I searched for other references. Found this one and it agreed with this 0x1BE value. http://www.win.tue.nl/~aeb/partitions/partition_types-2.html...

Lu Wei, For the DOS portion make sure you have a working FAT-32 DOS Bootable Drive first. Back up it's boot sector into a file. This file will probably be 512 Bytes and if you were to open it with a Hex editor it would start with ".X.MSWIN4.1" and end with "SYS~..WINBOOT SYS..U" This would of course be looking at the ASCII view. Assuming you put the file in the DOS directory and that your file is named PBR.BS Your entry would look something like this LABEL MSDOS710 MENU LABEL Boot MS-DOS 7.10 from USB Partition COM32 chain.c32 APPEND fs file=/DOS/PBR.BS nos...

...iso-linux: A function very much like lilos 'single-key' directive, Which only allows 1 character labels (but there should be plenty of them too ;o) Config-file: DEFAULT l PROMPT 1 TIMEOUT 50 SINGLEKEY LABEL l KERNEL vmlinux APPEND initrd=initrd.img LABEL w KERNEL MEMDISK APPENG initrd=winboot.img So when pressing w you get a windows boot-disk. Yours. -- Morten B?geskov (email: morten at bogeskov.dk) PS. Your software has helped me a great deal in making a rescue-cd that can boot from scsi cdrom drives (initrds has an ugly way of growing when you need scsi-support).

...t; 000001C0 6E 64 20 74 68 65 6E 20 70 72 65 73 73 20 61 6E nd then press an > 000001D0 79 20 6B 65 79 0D 0A 00 49 4F 20 20 20 20 20 20 y key...IO > 000001E0 53 59 53 4D 53 44 4F 53 20 20 20 53 59 53 80 01 SYSMSDOS SYS€. > 000001F0 00 57 49 4E 42 4F 4F 54 20 53 59 53 00 00 55 AA .WINBOOT SYS..Uª > 00000200 F8 FF FF FF FF FF 04 00 FF FF 06 00 FF FF 08 00 øÿÿÿÿÿ..ÿÿ..ÿÿ.. This doesn't look like any partition table I've seen before. It's possible that the disk is not partitioned, ie. that what you've got here is a straight filesystem. You could see if libguestf...

Greetings, I encounter a problem that should be basic, but I can't get a clue. I have 8G USB disk formatted as FAT32. I run (syslinux -i -s -r -m H:) to make it bootable, and write syslinux.cfg according to the documents, but it will not boot some items. Syslinux is 6.03, bios files used. The whole syslinux.cfg file:

...kte/677/Ritter_Rost_Geisterjagd_Wasserpost.html) When starting the game, I receive a message that some drivers are being installed. (That's okay, I receive the same message when running the game for the first time on Windows.) The next message asks me to reboot the systems. I am selecting "winboot" from the Gnome menu. After starting the game again, I receive the message that there are pending installation issues and I have to reboot the system. Finally, after actually rebooting Linux, I receive the original message, back to start. Any ideas what I might do? Thanks, Jochen -- I hav...

> > The appliance kernel couldn't find any partitions at all on the disk. > > Is it a raw format disk image, or some other format that qemu can > reasonably be expected to read? I used the "Advanced Options" of Macrium Reflect (on Windows 7) to do a raw byte copy. If it is, then yes I'd say the image is corrupted. However you'd > probably want to hexdump

...gt; > For the DOS portion make sure you have a working FAT-32 DOS Bootable > Drive first. Back up it's boot sector into a file. This file will > probably be 512 Bytes and if you were to open it with a Hex editor it > would start with ".X.MSWIN4.1" and end with "SYS~..WINBOOT SYS..U" > This would of course be looking at the ASCII view. Assuming you put > the file in the DOS directory and that your file is named PBR.BS > > Your entry would look something like this > > LABEL MSDOS710 > MENU LABEL Boot MS-DOS 7.10 from USB Partition > COM32 ch...

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