Update installation instructions
Modified: branches/xmlbuildsystem/reactos/INSTALL
_____
Modified: branches/xmlbuildsystem/reactos/INSTALL
--- branches/xmlbuildsystem/reactos/INSTALL 2005-05-13 19:17:44 UTC
(rev 15267)
+++ branches/xmlbuildsystem/reactos/INSTALL 2005-05-13 19:47:30 UTC
(rev 15268)
@@ -7,67 +7,72 @@
2. Building ReactOS
-To build from Windows run 'make' (wihout the quotes) from the top
directory.
-To build from unix, edit rules.mak and change the PREFIX variable to
the
-correct value for your cross-compiler. Run 'export HOST=mingw32-linux'
to
-tell the ReactOS build system that it is building ReactOS on a linux
machine.
-Now run 'make'.
+2.1 Building the binaries
+To build ReactOS run 'make' (wihout the quotes) if you are building on
Linux
+or 'mingw32-make' if you are building on Windows (or ReactOS) from the
top
+directory.
+
+2.2 Building a bootable CD image
+
+To build a bootable CD image run 'make bootcd' (wihout the quotes) if
you are
+building on Linux or 'mingw32-make bootcd' if you are building on
Windows (or
+ReactOS) from the top directory. This will create a CD image with a
filename,
+ReactOS.iso, in the top directory.
+
+
3. Installation
-The system can only be installed on the first partition on the first
harddisk.
-The partition must be formatted as FAT16 or FAT32. The system can only
be
-started from DOS and not from a Windows DOS-prompt.
+ReactOS can only be installed on a machine that has a FAT16 or FAT32
partition
+as the active (bootable) partition. The partition on which ReactOS is
to be
+installed (which may or may not be the bootable partition) must also be
+formatted as FAT16 or FAT32. ReactOS Setup can format the partitions if
+needed.
-ReactOS can be installed from the source distribution or from the
binary
+ReactOS can be installed from the source distribution or from the
bootable CD
distribution. The two ways to install ReactOS are explained below.
3.1 Installation from sources
-To install ReactOS after building it, type 'make install'. This will
create
-the directory 'reactos' in the top directory. Copy this directory to
the root
-of your first partition on your first harddisk. This is usually c:\ on
a
-Windows machine.
+If you don't have an existing ReactOS installation you want to upgrade,
then
+build a bootable CD as described above. Burn the CD image, boot from
it, and
+follow the instructions to install ReactOS.
-If you don't want to copy the files manually every time you run a 'make
install',
-you can specify the directory where the files are to be copied to
during
-installation.
+If you have an existing ReactOS installation you want to upgrade, then
to
+install ReactOS after building it, type 'make install' or
+'mingw32-make install'. This will create the directory 'reactos' in the
top
+directory. Copy the contents of this directory over the existing
installation.
-In rules.mak find the variable INSTALL_DIR and change the assigned
value to the
-name of the directory where the files are to be copied to. If you are
using
-Windows this could be:
+If you don't want to copy the files manually every time you run a
+'make install' or 'mingw32-make install', then you can specify the
directory
+where the files are to be copied to during installation.
- INSTALL_DIR = c:\reactos
+Set the ROS_INSTALL environment variable. If you are on Windows this
could be
+done by:
-If you are on linux this could be:
+ set ROS_INSTALL=c:\reactos
- INSTALL_DIR = /mnt/windows/reactos
+If you are on Linux this could be done by:
-Save the changes to rules.mak and run 'make install' to install the
files to
-the new location. If you don't want to change rules.mak, you can
specify the
-installtion directory when invoking make. Run
-'make INSTALL_DIR=c:\reactos install' to install to c:\reactos.
+ export ROS_INSTALL=/mnt/windows/reactos
+Now run 'make install' or 'mingw32-make install' to install the files
to the
+new location.
-3.2 Installation from binany distribution
-To install ReactOS from the binary distribution, extract the archive
contents
-to c:\reactos. Remember to extract the files with full paths.
+3.2 Installation from bootable CD distribution
+To install ReactOS from the bootable CD distribution, extract the
archive
+contents. Then burn the CD image, boot from it, and follow
instructions.
-4. Booting ReactOS
-Startup in DOS mode. 'cd' to c:\reactos and type 'boot' and press
<enter>.
-A simple shell is started where you can use simple commands like 'cd'
and 'dir'.
-
-
5. Help
If you run into problems or have suggestions for making ReactOS better,
please
-surf to the address below and subscribe to one or more of the mailing
lists.
+visit the address below and subscribe to one or more of the mailing
lists.
-http://www.reactos.com/index.php?tab=discussion§ion=lists
+http://www.reactos.com/en/content/view/full/66
ReactOS Development Team
Cleanup template configuration file
Modified: branches/xmlbuildsystem/reactos/config.template.xml
_____
Modified: branches/xmlbuildsystem/reactos/config.template.xml
--- branches/xmlbuildsystem/reactos/config.template.xml 2005-05-13
17:11:16 UTC (rev 15265)
+++ branches/xmlbuildsystem/reactos/config.template.xml 2005-05-13
19:01:46 UTC (rev 15266)
@@ -1,67 +1,39 @@
<!--
- Architecture to build for
+ This file is a template used as a starting point for compile-time
+ configuration of ReactOS. Make a copy of this file and name it
config.xml.
+ Then change the options in config.xml. If you don't have a config.xml
file,
+ then the defaults in this file, config.template.xml, will be used
instead.
- Specify one of: i386
- Possible values in the future: alpha,i386,m68k,mips,powerpc
+ Boolean options can obtain the values 0 (disabled) or 1 (enabled).
String
+ options can obtain any value specified in the comment before it.
-->
-<property name="ARCH" value="i386" />
-
<!--
- Which cpu should reactos optimze for
- example : i486, i586, pentium, pentium2, pentum3, pentium4
- athlon-xp, athlon-mp, k6-2,
-
- see gcc manual for more cpu name and which cpu it can
- be optimze for.
+ Architecture to build for. Specify one of:
+ i386
-->
+<property name="ARCH" value="i386" />
-<property name="OARCH" value="i486" />
<!--
- Whether to compile in the kernel debugger
-<property name="KDBG" value="1" />
--->
+ Which CPU ReactOS should be optimized for. Specify one of:
+ i486, i586, pentium, pentium2, pentum3, pentium4, athlon-xp,
athlon-mp,
+ k6-2
-
-
-<!--
- Whether to compile for debugging
-<property name="DBG" value="1" />
+ See GCC manual for more CPU names and which CPUs GCC can optimize
for.
-->
+<property name="OARCH" value="i486" />
-
<!--
- Whether to compile with optimizations
+ Whether to compile in the integrated kernel debugger.
-->
+<property name="KDBG" value="0" />
-<property name="OPTIMIZED" value="0" />
-
<!--
- Whether to compile a multiprocessor or single processor version
+ Whether to compile for debugging. No compiler optimizations will be
+ performed.
-->
-
-<property name="MP" value="0" />
-
-
-<!--
- Whether to compile for ACPI compliant systems
--->
-
-<property name="ACPI" value="0" />
-
-
-<!--
- whether to use a 3GB User, 1GB Kernel memory map
--->
-
-<property name="_3GB" value="1" />
-
-
-<!--
- Which version of NDIS do we support up to?
-<property name="NDISVERSION" value="NDIS50" />
--->
+<property name="DBG" value="0" />
adjustments for GCC and MinGW
Modified: trunk/reactos/subsys/system/winefile/winefile.c
_____
Modified: trunk/reactos/subsys/system/winefile/winefile.c
--- trunk/reactos/subsys/system/winefile/winefile.c 2005-05-13
15:32:04 UTC (rev 15263)
+++ trunk/reactos/subsys/system/winefile/winefile.c 2005-05-13
15:35:55 UTC (rev 15264)
@@ -2013,28 +2013,32 @@
case ID_CONNECT_NETWORK_DRIVE: {
DWORD ret =
WNetConnectionDialog(hwnd, RESOURCETYPE_DISK);
- if (ret!=NO_ERROR &&
ret!=(DWORD)-1)
+ if (ret!=NO_ERROR &&
ret!=(DWORD)-1) {
if (ret ==
ERROR_EXTENDED_ERROR)
display_network_error(hwnd);
else
display_error(hwnd, ret);
+ }
break;}
case ID_DISCONNECT_NETWORK_DRIVE: {
DWORD ret =
WNetDisconnectDialog(hwnd, RESOURCETYPE_DISK);
- if (ret!=NO_ERROR &&
ret!=(DWORD)-1)
+ if (ret!=NO_ERROR &&
ret!=(DWORD)-1) {
if (ret ==
ERROR_EXTENDED_ERROR)
display_network_error(hwnd);
else
display_error(hwnd, ret);
+ }
break;}
+#ifndef __MINGW32__ /* SHFormatDrive missing in MinGW (as of
13.5.2005) */
case ID_FORMAT_DISK: {
UINT sem_org = SetErrorMode(0);
/* Get the current Error Mode settings. */
SetErrorMode(sem_org &
~SEM_FAILCRITICALERRORS); /* Force O/S to handle */
SHFormatDrive(hwnd, 0 /* A: */,
SHFMT_ID_DEFAULT, 0);
SetErrorMode(sem_org); /* Put it
back the way it was. */
break;}
+#endif
case ID_HELP:
WinHelp(hwnd,
RS(b1,IDS_WINEFILE), HELP_INDEX, 0);