| |
coolkidswriteviruses
Posts: 2
Score: 0
Joined: 8/23/2003
From: USA
Status: offline
|
I've been having the worst time with Visual Basic Script and Windows XP Professional SP1 (+hotfixes)
It appears that Microsoft has definately stripped VBScript down to a minimal scripting language worse than BATCH. You can't do ANYTHING with it. I can't get FileSystemObject to work at all, none of the commands ever complete successfully, yet there are no errors. I'm not really worried about that right now, but what I am worried about is getting the wscript.shell to work.
Example Code:
dim k
set k = createobject("wscript.shell")
k.run "cmd" (or "command")
set k = nothing
or even
dim k
set k = createobject("wscript.shell")
k.run "C:\windows\system32\cmd.exe"
set k = nothing
Neither of these work...
This doesnt work either
dim f
set f = createobject("scripting.filesystemobject")
f.createtextfile("C:\test.txt")
set f = nothing
What's the deal here? Is there some special magical setting that allows XP to run VBScript?
I'm accessing all of these from either .hta files, .vbs files, or .wsf files from the desktop, so there shouldn't be any security issues as far as the way I'm accessing it.
Killing Cancer -- One Stick at a Time
|
|
Printable Version
Windows XP and wscript.shell - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread