Login: Difference between revisions
(Created page with "==Description== Login is a program wich provides multiple desktops to your WPS. Every user defined desktop can be protected by a password. It doesn't protect any files, so be ...") |
No edit summary |
||
(7 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
== | {{Software | ||
Login is a program | |Picture=NA.png | ||
|Version=0.4 (Mar 1994) | |||
|Author=[[Jens Glathe]] | |||
|License=GNU GPL V3 | |||
|Download=[https://hobbes.nmsu.edu/download/pub/os2/util/wps/Login_0-4.zip Login_0-4.zip] | |||
}} | |||
Login is a program which provides multiple desktops for WPS. Every user defined desktop can be protected by a password. It doesn't offer any security. | |||
The program uses the emx.dll and emxlibc.dll. | |||
Example: | |||
login.exe c:\utils\login\userdata.login c:\os2\pmshell.exe | |||
==Installation== | |||
To install it correctly, you must do some changes to your config.sys. The modifications are: | To install it correctly, you must do some changes to your config.sys. The modifications are: | ||
* FIRST: ADD A CALL=CMD.EXE STATEMENT!! It saves a lot of trouble in the case that something goes wrong. | * FIRST: ADD A CALL=CMD.EXE STATEMENT!! It saves a lot of trouble in the case that something goes wrong. | ||
* SECOND: Create a backup of your .ini files! Login doesn't modify them, but the WPS does. | * SECOND: Create a backup of your .ini files! Login doesn't modify them, but the WPS does. | ||
* Replace the PROTSHELL statement with login.exe and the needed parameters. Example: | |||
* Replace the PROTSHELL statement with login.exe and the needed | |||
PROTSHELL=C:\UTILS\LOGIN.EXE c:\utils\login\userdata.login c:\os2\pmshell.exe | PROTSHELL=C:\UTILS\LOGIN.EXE c:\utils\login\userdata.login c:\os2\pmshell.exe | ||
* Add following setting: | * Add following setting: | ||
SET WORKPLACE_PROCESS=YES | SET WORKPLACE_PROCESS=YES | ||
If you forget it, pmshell won't open your folders or programs or whatever you start automatically. | If you forget it, pmshell won't open your folders or programs or whatever you start automatically. | ||
* REMOVE the following setting:<tt>SET RUNWORKPLACE=<anyprogram></tt> | |||
* REMOVE the following setting: | |||
If you forget it, the RUNWORKPLACE will start before you're logged in. | If you forget it, the RUNWORKPLACE will start before you're logged in. | ||
Line 47: | Line 34: | ||
* password | * password | ||
* full path and name of the user ini file. | * full path and name of the user ini file. | ||
It's a good idea to add the initial.ini desktop as a service entry. | It's a good idea to add the initial.ini desktop as a service entry. | ||
;How to create a new desktop: | |||
* Use the makeini utility to create a new user .ini file. | * Use the makeini utility to create a new user .ini file. | ||
* Add an entry associated with the new user file to the user data file. | * Add an entry associated with the new user file to the user data file. | ||
Line 56: | Line 42: | ||
* The WPS should start with the well-known default desktop for beginners. This is the new one. Now you can change it til it fits to your needs. | * The WPS should start with the well-known default desktop for beginners. This is the new one. Now you can change it til it fits to your needs. | ||
=== | ==Problems== | ||
* If a new USER_INI file is set, the desktop background color and the system settings (like window animation) will not be changed. Therefore you should configure this with the initial.ini desktop for your needs. | * If a new USER_INI file is set, the desktop background color and the system settings (like window animation) will not be changed. Therefore you should configure this with the initial.ini desktop for your needs. | ||
* To have printing capability from every desktop, you MUST install the printer drivers for EVERY desktop separately. This makes sense, because every printer object has its own queue. | * To have printing capability from every desktop, you MUST install the printer drivers for EVERY desktop separately. This makes sense, because every printer object has its own queue. | ||
* To get more save operation of the WPS with multiple desktops, every desktop directory tree should be located in its own subdirectory. Example: | * To get more save operation of the WPS with multiple desktops, every desktop directory tree should be located in its own subdirectory. Example: | ||
User 1: c:\user_1\Desktop | User 1: c:\user_1\Desktop - there is the Desktop subdirectory tree for user 1, located normally in c:\desktop or "c:\os/2 2.0 Desktop". Move it with the WPS to this location (important!), but ONLY if it is the active desktop! | ||
User 2: c:\user_2\Desktop | User 2: c:\user_2\Desktop - the Desktop tree for user 2. Same procedure as above. | ||
This is my own experience with desktop directories. | This is my own experience with desktop directories. | ||
== | ==Links== | ||
* [https://github.com/OS2World/UTIL-WPS-Login GitHub Repository] | |||
* [ | |||
[[Category:Software]] | [[Category:Open Source Software]] | ||
[[Category:Security]] |
Revision as of 16:34, 22 November 2020
Login | |
---|---|
Version | 0.4 (Mar 1994) |
Vendor | |
Author | Jens Glathe |
License | GNU GPL V3 |
Download | Login_0-4.zip |
Website |
Login is a program which provides multiple desktops for WPS. Every user defined desktop can be protected by a password. It doesn't offer any security.
The program uses the emx.dll and emxlibc.dll.
Example:
login.exe c:\utils\login\userdata.login c:\os2\pmshell.exe
Installation
To install it correctly, you must do some changes to your config.sys. The modifications are:
- FIRST: ADD A CALL=CMD.EXE STATEMENT!! It saves a lot of trouble in the case that something goes wrong.
- SECOND: Create a backup of your .ini files! Login doesn't modify them, but the WPS does.
- Replace the PROTSHELL statement with login.exe and the needed parameters. Example:
PROTSHELL=C:\UTILS\LOGIN.EXE c:\utils\login\userdata.login c:\os2\pmshell.exe
- Add following setting:
SET WORKPLACE_PROCESS=YES
If you forget it, pmshell won't open your folders or programs or whatever you start automatically.
- REMOVE the following setting:SET RUNWORKPLACE=<anyprogram>
If you forget it, the RUNWORKPLACE will start before you're logged in.
You should create a new user .ini file with "makeini initial.ini ini.rc", which you set as the default USER_INI file. That's why... you'll see.
- Create the user data file. Use the userdata.log file as a template. The format is:
First line: The magic cookie for the program. Do not change this line! After this line, every three lines are one user entry. The order is:
- user name
- password
- full path and name of the user ini file.
It's a good idea to add the initial.ini desktop as a service entry.
- How to create a new desktop
- Use the makeini utility to create a new user .ini file.
- Add an entry associated with the new user file to the user data file.
- Reboot and log in with the new name.
- The WPS should start with the well-known default desktop for beginners. This is the new one. Now you can change it til it fits to your needs.
Problems
- If a new USER_INI file is set, the desktop background color and the system settings (like window animation) will not be changed. Therefore you should configure this with the initial.ini desktop for your needs.
- To have printing capability from every desktop, you MUST install the printer drivers for EVERY desktop separately. This makes sense, because every printer object has its own queue.
- To get more save operation of the WPS with multiple desktops, every desktop directory tree should be located in its own subdirectory. Example:
User 1: c:\user_1\Desktop - there is the Desktop subdirectory tree for user 1, located normally in c:\desktop or "c:\os/2 2.0 Desktop". Move it with the WPS to this location (important!), but ONLY if it is the active desktop!
User 2: c:\user_2\Desktop - the Desktop tree for user 2. Same procedure as above.
This is my own experience with desktop directories.