Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
LABEL 1
MENU LABEL XP Install
#only include the following line if not using DHCP otherwise exclude the "--address" switch
ifconfig --address=<IP here> --server=<IP of nfs server>
root (nd)
chainloader +1
Last edited by Person_1873; 07-09-2009 at 06:44 PM.
Im gona try again, YOU CANT CHAINLOAD WINDOWS USING GRUB UNLESS ITS CHAINLOADED FROM A REAL BIOS DEVICE.
Take a look at how ppl boot windows of iscsi storage with gPXE.
First you boot up gpxe it will then hook the iscsi drive as a fake bios device drop an address to it in memory (IBFT), and the first part of windows can now boot, at some time the network connection with the iscsi drive have to be handed over to windows native drivers.
Thats done by windows initiating the network card, and a program called a iscsi initiator reads the IBFT of memory connect to the iscsi drive and windows has now fully taken over the connection.
Without IBFT and the initiator windows would at that point crash because when the windows kernel is loaded any "FAKE" bios drives will be ignored and the system will no longer know where to conteniue from.
Its like having a linux system with kernel and initrd and no root filesystem it wont boot.
then the only other thing i can think to do is to have the ISO extracted to both a FAT32 and a ext3 partition and somehow on boot after the initial boot has happened tell the XP kernel where to find it's setup files, i'm unfamiliar with kernel32 options so i guess it's off to hit the books for me, i suppose you could modify the boot.ini file for the cd image to specify a different root than the initial boot partition
after further investigation, on the XP CD, there is a file called DOSNET.INF EDIT: (/I386/DOSNET.INF), this appears to specify virtual drives, if we could discover the syntax for this, it may be possible to chainload the ntldr on the XP cd and have ntldr do the work of mounting the network filesystem that it can read and thus make t possible using grub to network boot an XP installation
Last edited by Person_1873; 07-18-2009 at 09:11 PM.
To load a full CD into RAM, nah. Not all Computers tha comes to my workshop has more than 512 MB Ram.
Where you thinking of using "memdisk" on a cd-rom iso?
also remember that not every PC that comes into your workshop is going to have a NIC capable of PXE and thus you will need to install from a disk anyway, i believe that this thread has gone beyond any truly practical usage and is now theoretical speculation
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.