Hehe yeah :D Just that since some people might complain we either break their installs / do not play "fair" with other companies products / etc... I prefer to play safe here :)
-----Message d'origine----- De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Thomas Faber Envoyé : mardi 16 mai 2017 09:48 À : ros-dev@reactos.org Objet : Re: [ros-dev] [ros-diffs] [hbelusca] 74550: [USETUP]: Continue implementing the NT OS installation detector. What remains to be done here, besides cleaning up the code from temporary comments and DPRINTs (and fixing potenti... On 2017-05-15 03:59, hbelu...@svn.reactos.org wrote: > Author: hbelusca > Date: Mon May 15 01:59:28 2017 > New Revision: 74550 > > URL: http://svn.reactos.org/svn/reactos?rev=74550&view=rev > Log: > [USETUP]: Continue implementing the NT OS installation detector. > What remains to be done here, besides cleaning up the code from temporary > comments and DPRINTs (and fixing potential bugs), is to actually parse the > NTOS loader configuration files (freeldr.ini in ROS' case, or boot.ini in > Win2k3's case, etc...) to retrieve the actual installation paths. So far > these are currently hardcoded for testing purposes only. > Note that I try to distinguish between ROS and Windows installations by > checking at the company name vendor of the ntoskrnl.exe & ntdll.dll files, in > order to allow the upgrade of ROS installations only. > Suggestions are always welcome. We should totally allow "upgrading" Windows installations with ROS. We're obviously better ;) _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
