No subject
Wed Jun 30 17:19:42 UTC 2010
g designed.=A0<br><br><div class=3D"gmail_quote">2010/9/5 Eric Kohl <span d=
ir=3D"ltr"><<a href=3D"mailto:eric.kohl at t-online.de">eric.kohl at t-online.=
de</a>></span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><br>
Hi!<br>
<br>
Being cooperative was my intention when I wrote this part of usetup. The ba=
d thing about this approach is that usetup needs to deal with all kinds of =
different situations that developers cannot even think about. The only prop=
er way to fix this situation was: "Don't touch it if you don't=
know how to deal with it!" The result was that usetup could only hand=
le empty harddisks and Windows boot managers correctly. Except for these tw=
o cases there are lots of different situations that a setup application can=
not deal with. That's where the user must fix things. That's why us=
etup enables users to save the bootsector to a floppy disk. =A0This enables=
them to fix the unknown situations themselves. Unfortunately this means th=
at newbies might not be able to install the bootcode properly. But I though=
t it was better not to overwrite a bootsector that to unintentionally damag=
e a system.<br>
<br>
The question how to handle this correctly is a difficult one. Microsoft cho=
se the easy way as they behave like they are the owner of the system and ov=
erwrite everything as they see fit. But implementing this part of the setup=
in a way that fits everyones needs is a very difficult task. Just think ab=
out the different filesystems and different versions of LILO and GRUB and w=
hat about other third-party boot-managers...<br>
<br>
Regards,<br>
Eric<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
<a href=3D"mailto:Ros-dev at reactos.org" target=3D"_blank">Ros-dev at reactos.or=
g</a><br>
<a href=3D"http://www.reactos.org/mailman/listinfo/ros-dev" target=3D"_blan=
k">http://www.reactos.org/mailman/listinfo/ros-dev</a><br>
</blockquote></div><br>
--0022152d6e593e3670048f884569--
More information about the Ros-dev
mailing list