Re: Booting problem with XP / DOS
Ixcoatl Perez <[email protected]>
| Newsgroups | gmane.network.etherboot.user |
|---|---|
| Message-ID | <[email protected]> |
Regarding the image configuration, I followed the instructions in the page. fdisk -lu gives me the following info: You must set cylinders. You can do this from the extra functions menu. Disk winXPimg: 0 MB, 0 bytes 128 heads, 63 sectors/track, 0 cylinders, total 0 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0xee54ee54 Device Boot Start End Blocks Id System winXPimg1 * 63 6128639 3064288+ b W95 FAT32 I guess the image has a mbr beacuse it boots from QEMU. It would be nice to have a small image with some OS at the etherboot page to test the network configuration before trying something bigger. The blue screen of dead you describe would be a big progress right now =D. I'll try to install xp in a real disk at the client machine now. Thank you ________________________________ De: "Miller, Shao" <[email protected]> Para: Ixcoatl Perez <[email protected]> CC: [email protected] Enviado: domingo, 30 de agosto, 2009 11:24:50 Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS Good day Ixcoatl Perez, Concerning your process for SAN-booting Windows XP: You should be installing Windows XP on the actual target hardware that will be SAN-booting. QEmu has different hardware (including different NIC) than your real hardware, so three things could potentially prevent the OS from fully booting: HAL, kernel, NIC. The symptom of this would be a "Blue Screen of Death" with number 0x0000007B. You would be better off installing to the actual target hardware. If you have multiple model types, you will be better off installing to each one and having an "image" for each model-type. HOWEVER, it doesn't appear that you have gotten that far. Your initial SAN-boot seems to fail. Some things to think about: Does the SAN have an MBR (with boot-code and partition table and an active partition)? Did you copy the whole disk (correct) or just the partition (incorrect)? Are you able to attach to this SAN from some other running OS on the same network and take a look at the disk? DOS certainly does not require a driver. INT 0x13 is hooked. A guess would be that you copied the partition, instead of the disk, or that QEmu disk geometry is somehow messing things up. Good luck! - Shao Miller ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Etherboot-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/etherboot-discuss Encuentra las mejores recetas en Yahoo! Cocina. http://mx.mujer.yahoo.com/cocina/ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Etherboot-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/etherboot-discuss