[NTLUG:Discuss] error 18 correct, but this is a head scratcher

[Daniel Hauck]

(2009年10月04日 12:51), Allen Meyers さんは書きました:
> Daniel said
>
> Some time ago, there was a practice of having a boot partition followed
>   
>> by several other partitions. This practice was partly to overcome the
>> problem you are experiencing now.
>>
>> The answer? Install Linux first, then Windows. Then when Windows is done
>> installing, "fix" the boot problem by reinstating grub using a Linux repair
>>     
> Sounds like a plan that I am more then willing to give it a shot.
> However please elaborate someone specifically how to reinstall grub
> using Linux repair. Just a challenged old man trying to get it right
>
> Thanks for helping
>   

http://www.geocities.com/epark/linux/grub-w2k-HOWTO.html

This guide goes into some pretty useful details. I have little more to
offer for two reasons -- 1. I don't do dual boot. 2. The last time I did
any dual boot, it was at least 3 maybe 4 years ago and I don't recall
much more than "why."

But I will say this. The typical process for setting up a dual boot
machine is "Windows first" and then "Linux second." The reason is that
Windows always installs its own boot loader and cares nothing for any
other. Bootloaders used by Linux are considerably more respectful. But
there are times when the size of any given partition might cause problems.

Another, slightly easier procedure to follow that might work without
getting into command lines and other such details might be to start the
install of your Linux of choice and create the partition layout where it
would be ordered like:

1. /boot
2. Windows
3. Linux
...

Then leave the installation incomplete. Either that or using a live CD
you can create the partitioning layout in advance. Then you can install
Windows to the target partition, then installing Linux to its target
partitions. The Linux partitions (other than /boot) may be outside of
the 1024 cylinder range, but the /boot partition will have the linux
kernel and initrd in it which will load and in turn contain the Linux
drivers for disk access which will not have the limitations presented by
the BIOS.