[syslinux] Two Windows 2k8 Server an booting via pxelinux

nevee nevee at supercomputing.pl
Thu Aug 19 03:06:20 PDT 2010


  Hello,
thanks for suggestions, now I try to install both systems on two 
partitions,
manually created in linux parted. It seems to that now Windows will not 
create boot partition,
beacause there is no place to do that.

-nevee
> For what its worth...
> If the windows install has indeed installed the boot manager on a seperate boot (recovery) partition.
> You could move the boot manager to the windows partition.
> Although this isn't that easy. ( you have to edit the bcd etc afaik )
>
> If its possible for you to do a new install of windows and you want it on 1 partition then
> make sure there are 3 primary partitions already (or add them while installing).
> Then the windows installer doesn't make a seperate partition just for the boot manager.
>
> Not sure if the above is helping for your problem though....
>
> -reni
>
>>>> "H. Peter Anvin"<hpa at zytor.com>  17-8-2010 20:52>>>
> On 08/17/2010 07:33 AM, nevee wrote:
>>    Hello list,
>> I have a question concerning the possibility of booting one of two
>> Windows systems installed on two partitions.
>> In case with one Windows system and one Linux system, I can chainload
>> grub or windows loader, and this is OK.
>> But in case with two Windows systems, when I installed second system,
>> the installer added multi boot loader(I think it's called bootmgr),
>> and then I can't choose the proper OS via syslinux config because
>> chainloading(append hd0 1, append hd0 2)
>> is not working (I get the "ntldr is missing" error).
>> When I try boot from mbr (hd0 0), multi boot loader shows up, and then I
>> can choose OS manually,
>> but I really don't know how to choose it automatically(via pxelinux
>> config file).
>>
>> I appreciate your help,
>> -nevee
> I haven't experimented with Win2k8, but if it is like Win7, then the
> boot manager is installed on a separate partition, and if both of your
> installations are using the same boot manager, then there isn't much
> that can be done from Syslinux, for obvious reasons.  This appears to be
> a deliberate decision by Microsoft.
>
> One thing you *can* do with at least older versions of Windwos plus a
> recent enough Syslinux is to copy NTLDR to the Syslinux install medium
> (in your case, the network drive) and boot, for example:
>
> chain.c32 hd0 2 ntldr=ntldr
>
> You may need 4.03-pre1 for this... there are some updates in the beta.
>
> -hpa
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>




More information about the Syslinux mailing list