>What would be involved to restrict some access to Windows '95?
>
>For example, on the user workstation, we would like to avoid a user to install a software, to change the registry, etc.


Michel,

Here's something excerpted from the ActiveX.Com newsletter I got this week that sounds like it might help you.....

Protecting a computer from bonehead users is a primary objective of any
software developer. But what happens when your software is designed to be
run in an information kiosk or on another type of unattended machine?
What happens when your application must absolutely be run on its own,
without meddling users attempting to run other apps or switch tasks on
the computer? DISABLE OCX gives your applications the capability to take
control of a Windows 95 computer by letting you disable key features of
the graphical user interface. The package actually consists of four
controls--Disable, DisableStartMenu, DisableControlPanel, and
DisableMisc. With Disable you can shut down the Taskbar, prevent users
from switching from one application to another, remove access to the
Start button, and prohibit users from getting access to the Windows
desktop. DisableStartMenu lets you prevent users from accessing
individual items on the Windows 95 Start menu, such as the shutdown menu.
DisableControlPanel denies users access to the network control panel, and
DisableMisc removes access from a number of other Windows services,
including network browsing and launching DOS applications. The control is
freeware; the beta currently available features minimal documentation but
contains a number of code examples. Click here to take control:

http://www.activex.com/PC/Result/TitleDetail/0%2C16%2C0-24136-g%2C00.html?axd