Network monitoring system for tracking, billing and recovering licenses

Abstract

A network monitoring system operates on a computer including processor for running a multi-tasking operating system capable of having active and inactive windows. The computer is connected to a server or a service which provides access to a user application subject to a license restriction. When the user application is associated with the active window, the user application is executed by the processor. A license recovering system includes a display coupled to the processor for displaying a user interface of the operating system. A user prompting device, run by the processor, the display and associated with an inactive window, prompts a user when the the inactive window has been inactive for a period greater than a first predetermined period. A closing device closes the user application when the inactive window has been inactive for a period greater than a second predetermined period. The network monitoring system also includes a real-time billing system for billing the computer user for access time to the user application subject to the license restriction to alleviate problems occurring in shared license pools on a network. The network monitoring system also includes a user priority system which defines user priorities for the application shared on the network. The priority system closes a current user accessing the user application if the priority of a new user requesting access is greater than the priority of the current user or if the application of the current user is idle.

Claims

What is claimed is:

1. A network monitoring system comprising:

a computer including processing means for executing a multi-tasking operating system which is capable of running a plurality of user applications each of which being associated with an active or an inactive window, wherein one of said user applications is provided by at least one of a server and a service and is subject to a license restriction,

wherein when said one of said user applications is associated with said active window, said user application is executed by said processing means;

display means, coupled to said processing means, for displaying a user interface of said operating system; and

user prompting means, run by said processing means and said display means and associated with said one of said user applications, for prompting a user when said one of said user applications has been associated with an inactive window for a period greater than a first predetermined period.

2. The network monitoring system of claim 1 wherein said user prompting means includes a first timer.

3. The network monitoring system of claim 1 wherein said user interface is a graphical user interface.

4. The network monitoring system of claim 1 further comprising:

closing means, run by said processing means and associated with said one of said user applications, for closing said one of said user applications when said one of said user applications has been associated with said inactive window for a period greater than a second predetermined period.

5. The network monitoring system of claim 4 wherein said closing means includes a second timer.

6. The network monitoring system of claim 4 further comprising:

check means, associated with said processing means, said user prompting means, and said closing means, for periodically enabling said user prompting means and said closing means based on a third predetermined period shorter than said first and second predetermined periods.

7. The network monitoring system of claim 1 further comprising:

identification (ID) means, associated with said computer, for generating an access request including a computer ID to access said one of said user applications and a termination request to terminate said one of said user applications;

application usage storing means, coupled to said ID means, for storing said computer ID and user startup and termination data based on said access and termination requests for said computer;

billing means, associated with said application usage storing means, for generating billing for said computer for use of said one of said user applications based upon said user startup and termination data.

8. The network monitoring system of claim 1 further comprising:

a plurality of computers each including a processing means for executing a multi-tasking operating system which is capable of running multiple user applications each of which being associated with an active or an inactive window, wherein said plurality of computers are connected to at least one of a server and a service which provides access to said one of said user applications;

network monitor means, coupled to said plurality of computers, for providing a first predetermined number of users access to said one of said user applications;

storing means, associated with said network monitor means, for storing a user identity and a user priority for each of said first predetermined number of users; and

comparing means, associated with said network monitor means and said storing means, for comparing a user priority of a new user requesting access to said one of said user applications to said user priorities stored in said storing means when said first predetermined number of users are currently accessing said one of said user applications.

9. The network monitoring system of claim 8 further comprising:

closing means, coupled to said comparing means, for closing said one of said user applications for one of said first predetermined number of users if said user priority of said new user is higher than the user priority of said one of said first predetermined number of users.

10. The network monitoring system of claim 9 further comprising:

access granting means, coupled to said comparing means, for granting said new user access to said one of said user applications.

11. The network monitoring system of claim 8 further comprising:

closing means, coupled to said comparing means, for closing said one of said user applications for one of said first predetermined number of users if said user priority of said new user is the same as said user priority of said one of said first predetermined number of users and if said one of said user applications of said one of said predetermined number of users is associated with an inactive window.

12. A priority system for granting and denying access to a user application subject to a license restriction comprising:

a plurality of computers each including a processing means for executing a multi-tasking operating system capable of having active and inactive windows, said computer being connected to at least one of a server and a service which provides access to a user application subject to a license restriction,

wherein said user application is associated with one of said active and inactive windows, and

wherein when said user application is associated with said active window, said user application is executed by said processing means;

network monitor means, coupled to said plurality of computers, for providing a first predetermined number of users access to said user application;

storing means, associated with said network monitor means, for storing a user identity and user priority for each of said first predetermined number of users; and

comparing means, associated with said network monitor means and said storing means, for comparing a user priority of a new user requesting access to said user application to said user priorities stored in said storing means when said first predetermined number of users are currently accessing said user application.

13. The priority system of claim 12 further comprising:

closing means, coupled to said comparing means, for closing said user application for one of said first predetermined number of users if said user priority of said new user is higher than said user priority of said one of said first predetermined number of users.

14. The priority system of claim 13 further comprising:

closing means, coupled to said comparing means, for closing said user application for one of said first predetermined number of users if said user priority of said new user is the same as said user priority of said one of said first predetermined number of users and if said user application of said one of said predetermined number of users is associated with an inactive window.

15. The priority system of claim 13 further comprising:

access granting means, coupled to said comparing means, for granting said new user access to said user application.

16. A license monitoring and recovering system comprising:

a computer including processing means for executing a multi-tasking operating system which is capable of running a plurality of user applications each of which being associated with an active or an inactive window, wherein one of said user applications is provided by at least one of a server and a service and is subject to a license restriction, and

wherein when said one of said user applications is associated with said active window, said one of said user applications is executed by said processing means;

display means, coupled to said processing means, for displaying a user interface of said operating system; and

closing means, run by said processing means and associated with said user application, for closing said one of said user application when said one of said user applications has been associated with an inactive window for a period greater than a first predetermined period.

17. The monitoring device of claim 16 further comprising:

user prompting means, associated with said processing means, said display means and said one of said user applications, for prompting a user when said one of said user applications has been associated with said inactive window for a period greater than a second predetermined period, wherein said first predetermined period exceeds said second predetermined period.

18. A method of monitoring and recovering licenses comprising the steps of:

executing a multi-tasking operating system on a computer which is capable of running a plurality of user applications each of which being associated with an active or an inactive window;

providing one of said user applications using at least one of a server and a service, wherein said one of said user applications is subject to a license restriction;

executing said one of said user applications with a processor associated with said computer when said user application is associated with said active window;

displaying a user interface of said operating system; and

prompting a user when said one of user applications has been associated with an inactive window for a period greater than a first predetermined period.

19. The method of claim 18 further comprising the step of:

closing said one of said user applications when said one of said user applications has been associated with said inactive window for a period greater than a second predetermined period.

20. The method of claim 19 further comprising the step of:

periodically enabling said user prompting means and said closing means based on a third predetermined period shorter than said first and second predetermined periods.

21. The method of claim 18 further comprising the step of:

generating an access request including a computer ID to access said one of said user applications and a user termination request to terminate said one of said user applications;

storing said computer ID and user startup and termination time data based on said access and termination requests for said computers;

generating billing for said computer for use of said one of said user applications based upon said startup and termination time.

22. The method of claim 18 further comprising the step of:

providing a first predetermined number of users access to said one of said user applications subject to said license restriction;

storing a user identity and user priority for said first predetermined number of users; and

comparing a user priority of a new user requesting access to said one of said user applications to said user priorities stored in said storing means when said first predetermined number of users are currently accessing said one of said user applications.

23. The method of claim 22 further comprising the step of:

closing said one of said user applications for one of said first predetermined number of users if said user priority of said current user is higher than said user priority of said one of said first predetermined number of users.

24. The method of claim 23 further comprising the step of:

granting said new user access to said one of said user applications.

25. In a computer including a processing means for running a multi-tasking operating system capable of having active and inactive windows, said computer being connected to at least one of a server and a service which provides access to a user application subject to a license restriction, wherein said user application is associated with one of said active and inactive windows, and wherein when said user application is associated with said active window, said user application is executed by said processing means, a method of granting and denying access to said user application based upon user priority comprising the steps of:

providing a first predetermined number of users access to said user application subject to said license restriction;

storing a user identity and a user priority for each of said first predetermined number of users; and

comparing a user priority of a new user requesting access to said user application to said user priorities stored in said storing means when said first predetermined number of users are currently accessing said user application.

26. The method of claim 25 further comprising the steps of:

closing said user application for one of said first predetermined number of users if said user priority of said new user is higher than said user priority of one of said first predetermined number of users.

27. The method of claim 26 further comprising the steps of:

granting said new user access to said user application.

28. A method of monitoring and recovering licenses comprising the steps of:

executing a multi-tasking operating system on a computer which is capable of running a plurality of user applications each of which being associated with an active or an inactive window;

providing one of said user applications using at least one of a server and a service, wherein said one of said user applications is subject to a license restriction;

executing said one of said user applications with a processor associated with said computer when said user application is associated with said active window;

displaying a user interface of said operating system; and

closing said one of said user applications when said one of said user applications has been associated with an inactive window for a period greater than a first predetermined period.

29. The method of claim 28 further comprising the steps of:

prompting a user when said one of said user applications has been associated with said inactive window for a period greater than a second predetermined period shorter than said first predetermined period.

Description

BACKGROUND OF THE INVENTION

1. Technical Field

This invention relates to computers, and more particularly, to a network monitoring system for tracking, billing and recovering licenses for computers connected to a network and running multi-tasking operating systems.

2. Background of the Invention

As a result of intense competition and innovation, personal computers (PCs) have become more versatile by evolving from a single-tasking, stand-alone device to a single-tasking network device to a multi-tasking network device. As a stand-alone device, PCs run an operating system, such as DOS.RTM., which is capable of executing only one application at a time ("single-tasking"). Every application that the user intends to run has to be installed on the stand-alone PC. The stand-alone PC runs one application at a time and starts and stops each application in succession. Therefore, stand-alone PCs have a 1:1 ratio of PCs to licenses. For example, if the PC user desires five applications, such as word processing, terminal emulation, a spreadsheet, graphics, and a database, the user requires five licenses, in other words, a license copy for each application installed on the stand-alone PC.

Local area networks (LANs) allow the interconnection of multiple PCs. Each PC shares disk space, files, printers, and other I/O devices with a network server. However, the PCs still run a single-tasking operating system and, therefore, still run only one license application at a time. Using the network server, however, the applications are shared by the multiple PCs ("shared license pool"). Not every PC needs to have each application installed locally at the same time nor is a license copy required for each PC.

Because the PCs are still single-tasking, not every PC needs to access every application all of the time. The applications are available on the network server when they are needed. Therefore, depending on the statistical demand, a single copy of an infrequently used application is shared among many users. Even the most popular application does not require a license for every user. The benefits of the shared use of the applications on the server allow the ratio of PCs to licenses to increase significantly, for some applications a ratio 15:1 (fifteen PCs accessing the server to one license available on the network server) are typical. This shared use of applications resulted in a cost saving because license cost is typically based upon the number of concurrent users.

When multi-tasking operating systems, such as Windows.RTM., were introduced, the prior cost savings of sharing applications on the network server were reduced. A PC running a multi-tasking operating system is capable of running multiple applications at a time. Therefore, a single PC user can tie up multiple licenses. Network PCs running a multi-tasking operating system can still access the shared license pool on the network server. However, theoretically, every PC can access every application at the same time. Therefore, a single user could tie up multiple applications on the server and reduce access to these by other users.

The effect of multi-tasking operating systems on shared license pools caused the industry to move backwards from the higher ratios towards the 1:1 ratio of PCs to licenses which was the case for stand-alone single-tasking PCs. In other words, multi-tasking operating systems increase license requirements and costs in a network having a shared license pool.

Therefore, a network monitoring system which reduces license cost for a network of computers running multi-tasking operating systems is desirable. Further, a network monitoring system which optimizes use of licenses in a shared license pool is desirable.

In a network having a shared license pool, a fixed number of licenses are available at one time. Problems occur when a large number of users tend to desire access to an application at a common or prime time. For example, a shared license pool may have one license for every five machines for a word processing application. A large number of users may desire access to the word processor at the same time, for example at the end of the month to prepare monthly reports. Because only a fixed number of licenses are available, some users will be unable to access the desired application during the prime time. Even a manager who may need access to the wordprocessing application more than some of his employees is denied access if the fixed number of licenses in the shared license pool are being used. The only way to alleviate this problem is to purchase additional license copies which increases costs. Therefore, a network monitoring system which addresses these problems is also desirable.

As the trend of having a large number of users on a network increases, processing power of a service provider providing access to user applications on the network will become more scarce. Typically the service provider providing access to the user application performs the processing and the user operates in a terminal mode. In essence, the user's processor only executes terminal processing related to input and output of already-processed data from the service provider. Competing uses of the service provider such as sharing large common files, sharing meterfiles, and running more complex applications are also competing for processing time/power.

As the number of users increases, the processing demand will likewise increase and the service provider will require more and more processing power. Therefore it is desirable to decrease demands on the service provider's processor to allow the service provider to focus on processing data or user applications which cannot be performed by the user.

SUMMARY OF THE INVENTION

A network monitoring system according to the invention includes a computer with a processor for running a multi-tasking operating system capable of having both active and inactive windows. The computer is connected to at least one of a server and a service which provides said computer access to a user application subject to a license restriction. The user application is associated with one of said active and inactive windows. When said user application is associated with one of said active windows, said user application is executed by said processor. A display, coupled to said processor, displays a user interface of said operating system. A user prompting device, associated with said processor, said display and said user application, prompt a user when said one of said active and inactive windows associated with said user application has been inactive for a period greater than a first predetermined period.

According to another feature of the invention, a closing device, associated with said processor and said user application, closes said user application when said one of said active or inactive windows associated with said user application has been inactive greater than a second predetermined period.

According to still another feature, a check device, associated with said processor, said user prompting device, and said closing device, periodically enables said user prompting device and said closing device based on a third predetermined period shorter than said first and second predetermined periods.

According to still another feature of the invention, an identification (ID) device, associated with said computer, generates an access request including a computer ID to access said user application and a termination request to terminate said user application. An application usage storing device, coupled to said ID device, stores said computer ID and user startup and termination data based on said access and termination requests for said computer. A billing device, associated with said application usage storing device, generates billing for said computer for use of said user application based upon said user startup and termination data.

According to still another feature of the invention, a plurality of computers each include a processor for executing a multi-tasking operating system capable of having active and inactive windows. The plurality of computers are connected to at least one of a server and a service which provides access to said user application. A network monitor, coupled to said plurality of computers, for provides a first predetermined number of users access to said user application. A storing device, associated with said network monitor, for stores a user identity and a user priority for each of said first predetermined number of users. A comparing device, associated with said network monitor and said storing device, compares a user priority of a new user requesting access to said user application to said user priorities stored in said storing device when said first predetermined number of users are currently accessing said user application.

According to still another feature, a closing device, coupled to said comparing device, closes said user application for one of said first predetermined number of users if said user priority of said new user is higher than the user priority of said one of said first predetermined number of users.

According to another feature, a closing device, coupled to said comparing device, for closing said user application for one of said first predetermined number of users if said user priority of said new user is the same as said user priority of said one of said first predetermined number of users and if said user application of said one of said predetermined number of users is associated with an inactive window.

According to another feature, an access granting device, coupled to said comparing device, grants said new user access to said user application.

Other objects, features and advantages will be readily apparent from the specification, drawings and accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The various advantages of the present invention will become apparent to those skilled in the art after studying the following specification and by reference to the drawings in which:

FIG. 1 is a diagram illustrating a stand-alone personal computer (PC) according to the prior art;

FIG. 2 is an electrical schematic illustrating different interconnections of PCs, servers, and a service provider via local area networks and wide area networks according to the prior art;

FIG. 3 is an electrical schematic of a personal computer for executing procedures associated with the network monitoring system;

FIG. 4 is a block diagram illustrating a license recovering procedure for the network monitoring system according to the present invention which can be run on the PC, server or service provider of FIG. 3;

FIG. 5 is a flow chart depicting the license recovering system of FIG. 4 and its associated data structure;

FIG. 6 is a flow chart depicting a real-time license billing procedure for the network and its associated data structure; and

FIG. 7 is a flow chart of a license priority procedure and its associated data structure.

DETAILED DESCRIPTION OF THE INVENTION

I. Background and Hardware System Description

A. Stand-Alone PC.

In FIG. 1, a PC 10 running a single-tasking operating system according to the prior art is illustrated. PC 10 is a stand-alone computer which is not connected to a network. PC 10 includes a microprocessor, memory, a display, and an input/output (I/O) interface (not shown in FIG. 1). PC 10 runs the single-tasking operating system, such as DOS.RTM., which is capable of executing only one application at a time. Every application which the user desires must be installed in internal or external memory of PC 10. PC 10 runs only one application at a time, each starting and stopping in succession. Therefore, PC 10 requires one license for every application which it runs.

2. PC Running A Single-Tasking Operating System

With reference to FIG. 2, PC 10' can be connected to a local area network (LAN) 14 via a network bus 16 in a conventional manner. PC 10' can share disk space, files, printers, applications, or other devices, with a network server 20. Because PC 10' runs a single-tasking operating system, such as DOS.RTM., PC 10' can still only run one application at a time. However, PC 10' can be connected to network server 20 and share applications with server 20. PC 10' no longer needs to have every application installed locally as with the stand-alone PC 10 in FIG. 1.

3. PC Running A Multi-Tasking Operating System

Other PCs 22 coupled to LAN 14 in a conventional manner run a multi-tasking operating system, such as Windows.RTM.. Each of these PCs 22 is capable of running more than one application at a time, unlike PC 10' which must run only one application at a time. Typically the multi-tasking operating system allows one or more active windows (or application) which is/are currently being executed and multiple inactive windows which are idle. As can be appreciated, PC 22 can more readily exhaust the shared license pool of the server 20 because the user can open multiple licensed application at once. Each PC 20 requires a license copy for each application whether the application is associated with the active or inactive windows.

Server 20 can, in turn, be coupled to a wide area network (WAN) 30, such as the Internet, which can provide additional applications to the PCs 10 and 20. Alternately, a PC 34 running a single- or multi-tasking operating system can be coupled directly to WAN 30 which provides access to a service provider 36 and other LANs 38. Still other configurations will be apparent to skilled artisans.

In FIG. 3, PC 22 which runs a multi-tasking operating system is illustrated in further detail. PC 22 includes a microprocessor 40, internal memory 44, and an input/output (I/O) interface 46. PC 22 includes a keyboard 50, a display 52, external memory 54, such as a hard drive, tape drive, CD-ROM, etc. and other input/output (I/O) devices 56 such as a mouse. PC 22 is connectable to a local server 20 via LAN 14 and to a service provider 36 via WAN 30 in a conventional manner.

II. License Recovering Procedure

In FIG. 4, a functional diagram of a license recovering procedure 100 for the network monitoring system is illustrated. License recovering procedure 100 is preferably implemented as software stored in memory 44 (and/or memory 54) and executed by microprocessor 40 which runs a multi-tasking operating system such as Windows.RTM.. As can be appreciated, other multi-tasking operating systems can be employed. Alternately, license monitoring procedure 100 can be implemented in an electronic circuit using discrete components, stored in firmware, etc. License recovering procedure 100 includes a main program control 104, queryunload module 106, Timer1 module 108 and Timer2 module 110.

Queryunload module 106 checks the unload mode of an application. In other words, when the application is being exited, queryunload module 106 checks the propriety of the method of exiting the application. The license recovering procedure 100 allows the user to unload (or quit) if the user employs the built-in procedures of the application and/or if the multi-tasking operating system is being closed. Otherwise, queryunload event 106 displays a message using the user interface to close the running application first. Timer1 module 108 checks the instance of a current active window every chktime seconds. If the current active window is not "our" window (in other words, the application being monitored is inactive), a timer is incremented. If the timer exceeds idletime, an idlemessage is displayed and the timer is reset. If the current window is "our" window (in other words, the application is active), the time is reset. Timer2 module 110 checks the instance of the current active window every chktime seconds. If the current active window is not "our" window, a timer is incremented. If the timer exceeds closintime, license recovering procedure 100 closes the application. If the current window is "our" window, the timer is reset.

As can be appreciated, one or more applications can be monitored. Each application to be monitored would be associated with a running copy of the license recovering procedure 100.

In FIG. 5, a flow diagram illustrates operation of Timer1 and Timer2 modules 106 and 108 of license recovering procedure 100 using a flow diagram 150 and an associated data structure 160. Skilled artisans can appreciate that Timer1 and Timer2 modules 106 and 108 can be event driven instead of flow driven. However, the operation will be analogous. Data structure 160 includes a chktime variable, a Timer1 variable, a Timer2 variable, an idletime variable, a closintime variable, and an idlemessage variable.

License recovering procedure 100 begins at step 164 where control determines whether "our" application is open. If not, control loops until "our" application is open. If "our" is open, control proceeds to step 166 where Timer1 and Timer2 are reset. At step 168, control waits a predetermined period set by chktime variable. At step 170, control determines if "our" application is idle. If not, control returns to step 164. If "our" application is idle, control continues with step 174 where the Timer1 and Timer2 variables are started. Skilled artisans can appreciate that a single timer can be employed if desired.

Control continues with step 176 where the Timer1 variable is compared to the idletime variable. If the Timer1 variable exceeds the idletime variable, control displays an idlemessage such as "Be considerate to others and close this idle application", at step 180. As can be appreciated, the system operator can provide other messages as desired. If the Timer1 variable does not exceed the idletime variable, control proceeds with step 184 where control determines whether the Timer2 variable is greater than or equal to closintime. If the Timer2 variable exceeds the closintime variable, control closes "our" application at step 186. If not, control returns.

The following sections detail a specific implementation of the present invention for PCs operating with Windows.RTM.:

    ______________________________________
    I.  License Monitoring and Recovering Code Structure
    ______________________________________
    A.    Declarations
    declare Windows .RTM. API functions
    declare Windows .RTM. API Constants
    declare program global variables
    B.    Functions
    Functions are specifically called in.
    Function IsSucces
            check program return code after trying to connect to
            a network drive and return status
    Function DisSuccess
            check program return code after trying to disconnect
            from a network drive and true status
    Function Drive.sub.-- in.sub.-- use
            check the active task list for any program using
            this drive and return true or false
    C.    Events
          Events can happen at any time
    1.      QueryUnload
            check unload mode
            if attempting to unload from the main program, ok
            if attempting to unload because windows is exiting, ok
            if attempting to unload from anywhere else, display
            message to close the running application first.
    2.      Timer1
            every chktime seconds, get the instance of the current
            active window
            if current active window is not `our` window
              increment timer interval
              check to see if the elapsed time is grater than
              idletime
                if so, display idlemessage and set the dialog
                to modal if ismodal is true
                reset the timer interval and continue
            if current window is `our` window, reset the timer
            interval and continue
    3.      Timer2
            every chktime seconds, get the instance of the current
            active window
            if current active window is not `our` window
              increment timer interval
              check to see if the elapsed time is greater than
              closintime
              if so, send message to the application to close
              reset the timer interval and continue
            if current window is `our` window, reset the timer
            interval and continue
    D.    Main
    disable timer events; Timer1 and Timer2
    initialize local variables
    find this program window and hide it from the windows
    task list
    set up the initialization file string based on the program
    path
    verify that the initialization file is a valid file
    process the command line, checking for errors
    parse the command line string for the application name and
    optional program startup parameters
    check for the special command line word "ABOUT"
            if "ABOUT", open the diagnostic dialog box
            wait to close dialog and then end program
    open the initialization file
    read the service variables;
    drive       the drive letter to map the serve (share)
    service     the service (share) to attach to
    program     the program to run
    dummy1      username
    dummy2      password
    ismodal     characteristic of idle message dialog box
    build the program string from program and drive
    build username and password string from dummy1 and
    dummy2 if specified
    check to see if we are already connected to the service
    read the program setup variables;
    setupgpgm     the setup program to run to install the
                  application
    appnstlfile   the file to check for to indicate if the
                  application is installed
    appnstldisk   the disk to install the application on
    appnstlspace  the required disk space to install this
                  application
    check to see if the application is installed by checking for
    appnsrlfile
            in not installed
              if so,
                check for the setup program setuppgm and
                set the main program to be the setup program
                verify enough free space on drive appnstldisk
                by checking against size appnstlspace
              if not end the program
    if installed, read the miscellaneous variables
    meterfile      the file used to log the connect,
                   disconnect, terminate and idle times
    sound1         the sound played when a drive is
                   connected to the service
    sound2         the sound played when an application
                   terminates
    sound3         the sound played when the drive is dis-
                   connected from the service
    spawnandend    a parameter to indicate that the application
                   will launch another program and
                   immediately terminate
    altworkingdir  the path of an alternate working directory
                   for the application
    idletime       the allowed application idle time
    chktime        the frequency of the events; Timer1 and
                   Timer2
    idlemessage    the message displayed when the application
                   has been idle longer than idletime
    closintime     the allowed maximum idletime before the
                   application is automatically closed
    maxusers       the maximum number of users licensed to
                   run the application
    whofile        the name of the license file that will
                   keep track of who and how many users are
                   using the application
    alwhodrive     the drive letter of an alternate who file
    alwhofile      the file name of an alternate license file
    alwhoservice   the name of the service containing the
                   alternate license file
    close the initialization file
    read the DOS environment variable NODE
    check for the license file whofile
            see if the file whofile exists
              if not, create the file and write the sections;
              application name and maxusers
              if so, check to see if this application name is
              registered
                if this application name is not registered,
                register it
                if it is registered, update maxusers
              read the application name section, get maxusers
              and the number of current users
              see if this NODE is registered
              if the current users equals maxusers, check for an
              alternate license file altwhofile
              if an alternate is specified
              connect the alternate license server to
              altwhoservice
                verify the connection by calling function
                IsSuccess
                if successful continue
                if not,
                  display message indicating no available
                  licenses
                  write entry in the meterfile
                  end program
            read the altwhofile to check if current users is less than
            maxusers
              if so, continue
              if not
                display message indicating no available
                licenses
                write entry in the meterfile
                attempt to disconnect the drive
                verify disconnection by calling DisSuccess
                end program
            otherwise update the whofile or altwhofile and
            continue
    if we are not connected, try to connect to the service
            verify the connection by calling function IsSuccess
            if successful continue
            if not
              display message indicating connection failure
              write entry in the meterfile
              end program
    if we connect,
            play sound1
            write entry in meterfile indicating NODE, application
            name, status and time
    change default drive and directory to altworkingdir if
    specified
    enable timer events; Timer1 and Timer2
    try to run the application
            if not
              generate message
              disconnect drive
              end program
    shell the application and keep track of it's instance
    wait for the application program to exit
    if the program has exited, check for spawnandend
            if spawnandend, get the spawned windows instance
            and keep track of it
    disable timer events; Timer1 and Timer2
    play sound2
    call function Drive.sub.-- in.sub.-- use to see if any other program is
    using this drive
    if the drive is in use by any other program
    if no other copies of this application are still running, up-
    date the whofile or altwhofile
    update the meterfile
    end program
    if no other application is using the drive, attempt to dis-
    connect it
    call function DisSuccess to verify disconnection
    play sound3
    update the whofile or altwhofile
    update the meterfile
    end the program
    ______________________________________

    ______________________________________
    A.      INI FILE EXAMPLE
            ›MSInfo!
            Drive=j:
            service=.backslash..backslash.cwsrv1.backslash.word60a
            dummy1=testuser
            dummy2=testme
            dummy3=test
            program=.backslash.msapps.backslash.msinfo.backslash.msifo.exe
            Appnstlfile=c:.backslash.joesch.moe
            SetupPgm=.backslash.winwword.backslash.setup.exe
            Appnstlspace=1000
            Sound1=c:.backslash.windows.backslash.tada.wav
            Sound2=c:.backslash.windows.backslash.chord.wav
            Sound3=c:.backslash.windows.backslash.chimes.wav
            MeterFile=zapplictn.mtr
            IsMsgModal=false
            chktime=60
            idletime=1800
            idlemessage="Please be considerate of others."
            SpawnandEnd=YES
            MaxUsers=10
            WhoFile=z:.backslash.whofile.who
            AltWhoDrive=0:
            AltWhoService=.backslash..backslash.fesrv2.backslash.wingrp
            AltWhoFile=.backslash.altfile.who
            ›Word!
            Drive=j:
            service=.backslash..backslash.cwsrv1.backslash.word60a
            . . . etc . . .
            {Excel!
            . . . etc . . .
            ›PowerPoint!
            . . . etc . . .
    ______________________________________

• Inventors
  Wiggins, Christopher;
• Published
  Feb-10-1998
• Current US Classes:
  705/412
  709/229
  713/201
• Application #
  450618
• International Classes
  G06F 007/00
• Field of Search
  364/514 380/4 380/30 380/49 395/187.01 395/200.11 395/326 395/340 395/680 395/682 395/838
• Examiner
  Trammell; James P.
• Agent
  Wiggins; Michael D.
• US Patent References:
  4924378
  5023907
  5386369