Hi, I am the maintainer of uranos (http://uranos.sf.net) and want to implement the unattended setup of ReactOS into uranos. I read that you have implemented a answer file into ReactOS. Because of uranos does all the parts which is done by the txtinstaller from ReactOS (partition disk, write mbr, copy files and so on) from a linux boot environment - I want to know if it is possible to place the unattended.inf into the filesystem so the ReactOS is read the file in the first GUI boot.
Thank you! Cheers mario
Mario Gzuk wrote:
Because of uranos does all the parts which is done by the txtinstaller from ReactOS (partition disk, write mbr, copy files and so on)
Can it create registry hives?
I want to know if it is possible to place the unattended.inf into the filesystem so the ReactOS is read the file in the first GUI boot.
See http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/syssetup/wizard.c?revision=53485&view=markup#l_2185. ReactOS searches unattend.inf on installation CD on the first GUI boot.
Hi.
Am 30.08.2011 15:02, schrieb Dmitry Gorbachev:
Mario Gzuk wrote:
Because of uranos does all the parts which is done by the txtinstaller from ReactOS (partition disk, write mbr, copy files and so on)
Can it create registry hives?
There is also the offline registry editor in the boot env (http://pogostick.net/~pnh/ntpasswd/ ) so it should be possible if it is needed. (is it?)
I want to know if it is possible to place the unattended.inf into the filesystem so the ReactOS is read the file in the first GUI boot.
Seehttp://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/syssetup/wizard.c?revision=53485&view=markup#l_2185. ReactOS searches unattend.inf on installation CD on the first GUI boot.
But at this time there is no CD in the drive... In the M$ Windows (XP/2003) installation the installer is searching for the winnt.sif answer file (for the GUI mode) in $win_nt$.~bt on the hard drive. For automated installation it would be helpful to have a possibility to place the answer file directly into the InstallDIR (e.g. ReactOS\ or ReactOS\system32). What do you think?
Thank you for the fast answer.
Cheers
please, again, dont use "M$"
On Tue, Aug 30, 2011 at 3:12 PM, Mario Gzuk mariogzuk@technikz.de wrote:
Hi.
Am 30.08.2011 15:02, schrieb Dmitry Gorbachev:
Mario Gzuk wrote:
Because of uranos does all the parts which is done by the txtinstaller from ReactOS (partition disk, write mbr, copy files and so on)
Can it create registry hives?
There is also the offline registry editor in the boot env ( http://pogostick.net/~pnh/**ntpasswd/http://pogostick.net/~pnh/ntpasswd/) so it should be possible if it is needed. (is it?)
I want to know if it is possible to place the
unattended.inf into the filesystem so the ReactOS is read the file in the first GUI boot.
See<http://svn.reactos.org/**svn/reactos/trunk/reactos/dll/** win32/syssetup/wizard.c?**revision=53485&view=markup#l_**2185http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/syssetup/wizard.c?revision=53485&view=markup#l_2185
.
ReactOS searches unattend.inf on installation CD on the first GUI boot.
But at this time there is no CD in the drive... In the M$ Windows (XP/2003) installation the installer is searching for the winnt.sif answer file (for the GUI mode) in $win_nt$.~bt on the hard drive. For automated installation it would be helpful to have a possibility to place the answer file directly into the InstallDIR (e.g. ReactOS\ or ReactOS\system32). What do you think?
Thank you for the fast answer.
Cheers
______________________________**_________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/**mailman/listinfo/ros-devhttp://www.reactos.org/mailman/listinfo/ros-dev
There is also the offline registry editor in the boot env (http://pogostick.net/~pnh/ntpasswd/ ) so it should be possible if it is needed. (is it?)
Yes. See usetup sources (base/setup/usetup).
For automated installation it would be helpful to have a possibility to place the answer file directly into the InstallDIR (e.g. ReactOS\ or ReactOS\system32). What do you think?
Then you should modify the installer (syssetup).