On "discuss_de" we've talked about some problems with the installation process
on windows plattforms:

The affected OSs:
MS Windows 95 A, B, C
MS Windows 98 First, Second
MS Windows ME
MS Windows XP Home
MS Windows NT
MS Windows 2000 Professional
MS Windows XP Professional

Basics:
As you already know, the above plattforms not offering the same architecture
like unix-based plattforms. At least on Windows NT 4.0 Windows OS has become the
feature of an "root" (Administrator) and normal Users, in the discussion we
figured out, that this is also the strategy for Windows 2000 and the Windows XP
Plattform.


A sample situation
The setup proposal for the netinstallation is a good whitepaper in bigger
installations. But a "normal user" (for e.g. "moritz") won't read it, he just
clicks on the setup.exe (without -net) on his Windows OS and install his Version
on the appropriate Path (for e.g. on C:\Programme\OpenOffice.org1.0\) without
knowing, that he should do that only with the root privileges (Administrator user).
Then, later on, another user (in a private enviroment another part of the
family) will log on with a "normal user" (for e.g. "max") and if he also wants
to use OOo, he will just click on the setup.exe (withou -net) and the only
screen he will receive is the "remove option", where he can de-install
openoffice.org.

Background Ideas:
Eric and Andreas talked about an external "batch file", witch will call
"setup.exe -net" if they use it. Personally I don't like the idea to create
external tools, if we have the source code of the installation-set available and
working together on the same project ;-)
I've created this issue to bring the ideas and possible solutions together at
one point, tough that the "installation.openoffice.org"-project is the right
place to talk about this issue.

Some possible Solutions:
- Maybee it's possible to read out the current users privileges, when a user
calls setup.exe. 

- If he's not an administrator (at least at Windows NT or higher plattforms) a
warning msgbox should be displayed. 

- If the user is administrator, the installation should be working without a
warning (even if he has local administrative rights, they should know what they
do with those permissions).

- And if the "Administrator" calls the setup.exe this installation set should
give him the possibility to create/add a "setup.exe -net" shortcut on the
start>programs>menu or "the desktop" for normal users (in addition to the normal
current user shortcuts to the program apps (writer, calc, setup etc...) With
this  enhancement, "normal users" can simply click the shortcut on their
desktop/menu (without knowing that this will call setup.exe -net) and proceed
with the setup procedure.

If you have another idea/solution or understanding of this situation, feel free
to add your comments to this issue.