Robert
Thu Sep 04 15:26:25 CDT 2003
Richard, thanks for the discussion -- this helps greatly. I am, in fact,
using a mapped drive extensively, which I'll reconsider.
"Richard Mueller [MVP]" <rlmueller@ameritech.net> wrote in message
news:OCUBor0bDHA.3248@tk2msftngp13.phx.gbl...
> Hi,
>
> When a bat logon script runs on Win9x clients, drive z: is temporarily
> mapped to the NetLogon share. When the bat file calls a VBScript logon
> script (such as NetLogon.vbs), it can happen that the temporary drive
> mapping is deleted before the vbs runs, and the user gets an error message
> that z:\NetLogon.vbs not found. However, this does not happen on NT
clients,
> because they use UNC rather than a temporary drive to run logon scripts.
> Still, it sounds like your bat file can't find the vbs, or the vbs can't
> find the exe file. How does netlogon.bat call SFLogin.bat or SFLogin.vbs?
> How does the vbs launch the exe? Do you use a full UNC path?
>
> All of the programs run on the client, even if the files are on the
server.
> During logon, perhaps the "current" directory would be the NetLogon share.
I
> would expect the working directory to be the directory where the bat file
is
> located. However, I would never depend on this. I would always specify the
> full path to any file, in UNC format.
>
> When a bat file launches a vbs, the batch file first loads either
> cscript.exe or wscript.exe into memory. Then, cscript or wscript loads the
> vbs and runs it in the cscript or wscript process. When the vbs launches
an
> exe, the exe runs in it's own process, so they could run simultaneously.
If
> the bat file uses cscript, it will wait for the vbs to run before
> continuing. If it uses wscript, it will not (I believe). Whether the
> programs run simultaneously depends exactly on how they are launched.
>
> --
> Richard
> Microsoft MVP Scripting and ADSI
> HilltopLab web site -
http://www.rlmueller.net
> --
>
> "Robert Solorzano" <rsolorzano@NOSPAMyahoo.com> wrote in message
> news:%cN3b.691$tw6.73@newsread4.news.pas.earthlink.net...
> > SFLogin.vbs runs from an NT4 server at user login (netlogon.bat serves
as
> a
> > stub loader that calls SFLogin.bat).
> >
> > When SFLogin.bat attempts to run an .exe, sometimes NT4 Workstation
hosts
> > get this error:
> >
> > "Rundll32.exe - Invalid Current Directory. The process cannot switch to
> the
> > startup directory to c:\winnt. Select OK to set current directory to
> > c:\winnt, or select cancel to exit."
> >
> > Would anybody have a general explanation as to why this is happening?
> That
> > is: does this have something to do with a "working directory?" What is
a
> > working directory? What is a current directory? When netlogon.bat
calls
> > SFLogin.vbs, what's going on? What's happening when SFLogin.vbs calls
> > another .exe? Do these processes run on the server, or on the client?
> >
> > Hopefully a general explanation will help me figure out instances of
this
> > error.
> >
> > Thanks,
> > Robert
> >
> >
>
>