Hello Mr. Roth:

        Yes, I'm interested.  Please let me know what you have in mind.  Also,
regarding my perplexing problem, I think I may have found out what the real
problem is.  It seems that when a user logs on, the use of the Runh.exe program
adds a couple of seconds to the time it takes the logon script to run.

        Since the OS doesn't wait for logon scripts to finish executing before giving
the user a shell, the drive-mappings created by the logon script are not
"in-place" when the user's startup program begins (and this startup program
relies on a particular drive mapping).

        So, the solution I will be trying tomorrow is to use PolEdit to set the
"Default Computer->System->Logon->Run logon scripts synchronously" check box
(this setting also appears under "Windows NT System->Logon").  What this
(supposedly) does is to wait for the logon scripts to complete before starting
the user's shell.

        In any event, I would still appreciate any tips/tricks regarding the Perl
console.  Thanks.


Dean Theophilou
Genisar


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 09, 2002 8:42 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: Perplexed


Alternatively there are some tricks you can use to minimize and even hide
the normal perl.exe console. They require the use of Win32::API. Let me know
if you are interested.

-----Original Message-----
From: Jenda Krynicky [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 09, 2002 8:10 AM
To: Perl_beginner EE-mail"; Perl-Win32-Admin@ActiveState. com
Subject: Re: Perplexed


"Dean Theophilou" <[EMAIL PROTECTED]> wrote
>       I created a Perl logon script for use on an NT TSE machine which
sets
> environment variables and maps drives.  It runs as expected when it's
> run from the path specified in User Manager for
> Domains->Profile->Logon Script Name. Since I don't want the user to be
> able to see it when he logs on, I use runh.exe with the script.
>
>       Unfortunately, when I use runh.exe, the user's program, which
> launches at startup, can't find the drive that the logon script is
> supposed to map.  I've also noticed this kind of behavior when calling
> the logon script from Usrlogon.cmd.

Try to run the script with c:\perl\bin\wPerl.exe
That one should not create the console, but otherwise it's just the
normal perl interpreter.

Jenda


=========== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ========== There
is a reason for living. There must be. I've seen it somewhere. It's just
that in the mess on my table ... and in my brain. I can't find it.
                                        --- me
_______________________________________________
Perl-Win32-Admin mailing list [EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin

--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to