currentworkingdirectory after uncompress on XP

Forums

My Profile

Inbox

Address Book

My Subscription

My Forums

currentworkingdirectory after uncompress on XP

Logged in as: Guest

arrSession:exec spGetSession 2,2,998

	Active Users: There are 0 members and 0 guests.
	Users viewing this topic: none

Printable Version

All Forums >> [Scripting] >> WSH & Client Side VBScript >> currentworkingdirectory after uncompress on XP
Do you like VisualBasicScript.com? Link to us and help spread the word about our forum. Thanks!

Page: [1]

Message

<< Older Topic Newer Topic >>

currentworkingdirectory after uncompress on XP - 4/5/2004 2:27:11 AM

nikhilb

Posts: 1
Score: 0
Joined: 4/5/2004
From:
Status: offline

Folks...

have a strange wsh (vbscript) problem.

basically i am trying to run a wsf file , which is in zip format. on XP , i use the XP's built in uncompress mechanism and it opens the zip file and displays its contents...(the files). And when I click on the wsf file to execute it, it executes fine...until a point where its looking to copy a file from the same unzipped file into windows directory. thats where it bails out...giving file not found exception.

from what i hear when you run a wsf file, the windows scripting host runs from the same directory where the file is and hence you can do currentWorkgingdirectory and get the path of other files in the same folder as the wsf file. But in the case which is just described above, on XP, after being uncompressed, i cannot determine what the directory from where i am running the wsf file.

any pointers will be appreciated.

tia,
nik