Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ucsd!usc!sdd.hp.com!think.com!paperboy!hsdndev!cmcl2!phri!rna!dan
From: dan@rna.UUCP (Dan Ts'o)
Newsgroups: comp.windows.ms
Subject: Re: Recursive Windows
Message-ID: <1070@rna.UUCP>
Date: 25 Jan 91 18:14:38 GMT
References: <91014.153634YTHPRGDB@MTUS5.BITNET>
Organization: Rockefeller University - Neurobiology
Lines: 19

In article <91014.153634YTHPRGDB@MTUS5.BITNET> YTHPRGDB@MTUS5.BITNET writes:
>Is there any nice way to prevent your users from recursively running windows?
>That is, they exit to DOS (via the DOS icon), do something, and leave.  Later
>in the day they come back and see DOS, so they type WIN and run Windows.  As
>Windows doesn't (can't?) tell if it is already running, it let's you do it.
>But since you're in a Windows DOS Shell, you're really running Windows inside
>of Windows.  The computer runs SO slow it's unbearable.

	You can always do the BAT file, lock file game...

	A lock file, say C:\WINDOWS.LCK
	A BAT file, WIN.BAT in a directory earlier in the PATH than \WINDOWS.

	AUTOEXEC.BAT deletes C:\WINDOWS.LCK
	WIN.BAT tests for C:\WINDOWS.LCK
			if exists, error message
		creates C:\WINDOWS.LCK
		runs WINDOWS
		deletes C:\WINDOWS.LCK