Could someone point me to where there might be some script/technique for checking that a user has not logged on more than once on the same pc i.e. prevent multi copies of arev running.

I seem to recall seeing discussion somewhere, but I thought it might have been on compuserve.

Running an NT network. Arev logon does not have different user names.

Barry

Suggest that you set up a table with a record for each machine (could be done automatically), and lock the machine record in the Arev startup routines. Subsequent attempts to lock the same record would fail….

Barry

I think most people just check a local text file when logging in. Either check if it exists meaning I am already logged into Arev or check if the content is 1 for example. Then log off process just resets it.

Most also have a manual reset to delete/change file that is still around when it shouldn't be !

Hope this helps, Tony.

I tried this technique. Unfortunately, there are system routines that do an unlock all, so this will not work.

Another method would be to create an Arev file and check it for the workstation id, if it is there already don't allow login, if not there, write a record using the station id as the key and continue. It would mean having to put a shell around the voc off/logoff entries to clear the item when the user logs out.

Problems? Abends and Windows crashes could leave the item in the file with the user out of the system.

Advantages: You could add login/out history, add a MFS and checksumming to prevent unauthorized users from tampering with the log items.

Now if you were running OS/2 as you desktops you could just change the icon property to switch to a current existing session rather than spawn a new one when clicked on, but then Win95 is so much better than OS/2 in every way I shouldn't mention it.

I'm sure there's a way to do it in Windows95. I know little about Windows95, so how can I say this? Because I have built an interface between Arev and a Windows95 graphics program. When I navigate through a browse list in Arev, going from one graphics database entry to another, a graphics viewer is called (PCPERFORMed) with the name of the picture as an argument. The reason I picked the viewer I used was partly because when I called it, it used the existing instance of itself and simply unloaded the old picture and loaded the new one. Using whatever technique was used in that program, one could put a shell around Arev entirely. Surely there's a Window95 guru on the board who can explain how to do this.

Some Windows programs behave that way, some don't. Some behave both ways. It depends on how they are written. Quarterdeck's Zip-it (their version of WinZip) will sometimes open another zip file within itself, sometimes it will spawn a new session of itself. There's no option that I can find in the program itself to control this.

I'm sure it can be done, but to get a DOS session to do it probably involves writing a shell program or assembler/C++ interface that punches the correct WinAPI or DOS/WIN/BIOS interrupt or service.

Nothing simple like just checking an option on the icon properties.

What system routines do this? I've not encountered any, and I have the locking method used at several customer sites, so I'm keen to know

J

Really only exiting the debugger to the best of my knowledge (apart from things you'd expect to like LOGTO and such).

amcauley@sprezzatura.com

Sprezzatura Group

World Leaders in all things RevSoft

You may wish to view this previous thread on the same issue.

The RESET verb in HR-1 systems do an UNLOCK ALL if I'm not mistaken. RESET in HR-1 did quite a few things more than the vanilla RESET in ARev.

View this thread on the forum...