[THIN] Re: Mapping client drive when published application is initializing
- From: "Rick Mack" <Rick.Mack@xxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Sun, 9 Oct 2005 18:11:48 +1000
Hi,
I suspect it's a matter of timing.
The client v: drive mapping printer autocreation etc is initiated via
cmstart.exe and is probably not completed when the published application starts.
What I'd be tempted to try is to disable client drive automapping and have a
manual "net use v: \\client\c$" at the beginning of usrlogon.cmd. Set logon
scripts execution to synchronous and you've got a reasonable chance that v:
drive will be in place before your application starts.
regards,
Rick
Ulrich Mack
Volante Systems
Level 2, 30 Little Cribb Street
Coronation Drive Office Park
Milton Qld 4064
tel: +61 7 32431847
fax: +61 7 32431992
rick.mack@xxxxxxxxxxxxxx
________________________________
From: thin-bounce@xxxxxxxxxxxxx on behalf of Yang Yi
Sent: Sun 9/10/2005 5:43 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Mapping client drive when published application is initializing
Hello All:
I've a published application (an executable file). It's on the MetaFrame XP
server, say "D:\MyApp\app.exe". When this executable is initializing, it must
reference an external file (an Access mdb file), say "..\data.mdb". (the
filepath is hard-coded, and I cannot pass it as parameter to the executable)
However, I have to keep this data.mdb file on the client pc.
I know that client C: Drive is mapping to V: Dirve on server, thus I tried to
change the working directory for the published application. I put the data.mdb
in "C:\" on client pc. And then change the working directory on MetaFrame XP to
"V:\MyApp".
I suppose that, by "..\data.mdb" up one level of "V:\MyApp", it would reference
to "V:\data.mdb" (actually, C:\data.mdb).
Unfortunately, it does not work that way. MetaFrame cannot find that working
directory (saying that it is invalid).
Thanks very much,
Y. Yang
#####################################################################################
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this e-mail has been
sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this e-mail is prohibited. If you have received it in
error please notify the sender immediately by reply e-mail and destroy all
copies of this e-mail and any attachments. All liability for direct and
indirect loss arising from this e-mail and any attachments is hereby disclaimed
to the extent permitted by law.
#####################################################################################
Other related posts:
