[thelist] asp: FileSystemObject
Tab Alleman
Tab.Alleman at RealMetros.com
Tue Aug 14 13:24:34 CDT 2001
Hmmm... Ok, I tested the same script as a .vbs and ran it from the
command prompt and it worked.. it created the FSO object.. so why won't
it do it in an .asp script?
-----Original Message-----
From: Anthony Baratta [mailto:Anthony at Baratta.com]
Sent: Tuesday, August 14, 2001 11:11 AM
To: thelist at lists.evolt.org
Subject: RE: [thelist] asp: FileSystemObject
At 07:16 AM 8/14/2001, you wrote:
>Ummm, ok I'm not big on Sysadmin stuff, or maybe it's that I've never
>used a Win2K server before, but...what's a windows host script and how
>do I verify if it's installed? : )
You might want to test your script as a VBS script and see if it you can
create the FSO object outside of the IIS Service. On Win2K I don't see a
way to "uninstall" WSH. On WinNT its configurable via Control Panel,
Add/Remove Software.
I stole this from the Win2K Help File....
Windows Script Host overview
Windows Script Host enables scripts to be run directly in Windows 2000
by
clicking a script file on the Windows desktop, or by typing the name of
a
script file at the command prompt. Just like Microsoft Internet
Explorer,
Windows Script Host serves as a controller of ActiveX scripting engines.
Unlike Internet Explorer, however, Windows Script Host has very low
memory
requirements and is ideal for both interactive and non-interactive
scripting needs such as logon scripting and administrative scripting.
Windows Script Host supports scripts written in Visual Basic Scripting
Edition (VBScript) or JScript. When a script is started from the Windows
desktop or from the command prompt, the script host reads and passes the
specified script file contents to the registered script engine. The
scripting engine uses file extensions (.vbs for VBScript; .js for
JScript)
to identify the script instead of using the SCRIPT tag (used in HTML).
This
way, the script writer doesn't have to be familiar with the exact
programmatic ID (ProgID) of various script engines. The script host
itself
maintains a mapping of script extensions to ProgIDs and uses the Windows
association model to launch the appropriate engine for a given script.
There are two versions of the Windows Script Host: a windows-based
version
(wscript.exe) that provides a windows-based property sheet for setting
script properties, and a command prompt-based version (cscript.exe) that
provides command line switches for setting script properties. You can
run
either of these by typing wscript.exe or cscript.exe at the command
prompt.
Previously, the only native scripting language supported by the Windows
operating system was the MS-DOS command language. Although MS-DOS is
fast
and small, it has limited features compared to VBScript and JScript.
Today,
ActiveX scripting architecture allows users to take advantage of these
powerful scripting languages while support is still provided for MS-DOS
command scripts.
For more information, see the Windows Script Technologies Web site at
the
Microsoft Web site (http://www.microsoft.com/scripting).
----
Anthony Baratta
President
Keyboard Jockeys
"Conformity is the refuge of the unimaginative."
---------------------------------------
For unsubscribe and other options, including
the Tip Harvester and archive of TheList go to:
http://lists.evolt.org Workers of the Web, evolt !
More information about the thelist
mailing list