Windows Scripting Post: 302143143

Sponsored Content

Special Forums Windows & DOS: Issues & Discussions Windows Scripting Post 302143143 by Perderabo on Tuesday 30th of October 2007 06:41:46 PM

10-30-2007

Administrator Emeritus

VBscript has a reputation for being insecure, but I don't think it is fairly deserved, it is simply a powerful language. The problem was a variety of applications that allowed the outside world to run VBscript routines. Disabling VBscript was a bandaid for other problems. If you let anyone on Earth run any Perl or Ksh scripts they want, then those languages would be just as "insecure". That said, Microsoft is moving away from VBscript so I would not now recommend learning it.

.bat files have been around forever and will probably never go away. It is an odd language, but it is more powerful than most folks realize. If you don't know .bat files, you might start there. Powershell is Microsoft's latest experiment. It might last or they may drop it as fast as VBscript. Powershell has been made available for XP so I have been thinking of downloading it and giving it a try. But so far, I have no experience with it.

Perderabo

View Public Profile for Perderabo

Find all posts by Perderabo

5 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

windows scripting for a batch job

I have been doing unix scripting for quite awhile and there seems to be a wealth of information on it. Now I am working on migrating an intel based application to a new server. I need to modify some existing scripts, but am having trouble finding information on windows scripting, a forum similar...

2. UNIX for Dummies Questions & Answers

Need help configuring Active Perl on Windows Vista.: Perl Scripting on Windows

Hi All, Need help configuring Active Perl on Windows Vista. I am trying to install Active Perl on Windows Vista. The version of Active Perl i am trying to install is : ActivePerl 5.10.1 Build 1006 After installing it through cmd, When i try to run perl -v to check the version, i get the...

3. Shell Programming and Scripting

Shell scripting on Windows platform

Is there a free unix platform that will allow me to write a shell script on my Windows OS? I have my files on my C: drive and i need to write a script that reads from those files and does some manipulation. Its pretty straightforward in unix commands hence i don't want to write a Java/C++ program...

4. Windows & DOS: Issues & Discussions

Need Help in Windows scripting

Dear Expert, Below code is for to take the backup of database by daily time stamp. I need vital help to make my script automatic sending me email if it sucess or fail. Code: echo on @REM Seamonkey’s quick date batch (MMDDYYYY format) @REM Setups %date variable @REM First parses...

5. Shell Programming and Scripting

C Shell Scripting on SUA windows 7

hi, Even $eType is BSD_8GB echo $eType switch ( $eType ) case BSD_8GB: case BSD_12GB: echo "excuted BSD_8GB & BSD_12GB" breaksw default: echo "default" exit 0 endsw Result always default case printing. Please help....

LEARN ABOUT SUSE

platform::shell

platform::shell(n)					       Tcl Bundled Packages						platform::shell(n)

__________________________________________________________________________________________________________________________________________________

NAME

       platform::shell - System identification support code and utilities

SYNOPSIS

       package require platform::shell ?1.1.4?

       platform::shell::generic shell
       platform::shell::identify shell
       platform::shell::platform shell
_________________________________________________________________

DESCRIPTION

       The platform::shell package provides several utility commands useful for the identification of the architecture of a specific Tcl shell.

       This  package  allows the identification of the architecture of a specific Tcl shell different from the shell running the package. The only
       requirement is that the other shell (identified by its path), is actually executable on the current machine.

       While for most platform this means that the architecture of the interrogated shell is identical to the architecture of  the  running  shell
       this  is  not generally true. A counter example are all platforms which have 32 and 64 bit variants and where a 64bit system is able to run
       32bit code. For these running and interrogated shell may have different 32/64 bit settings and thus different identifiers.

       For applications like a code repository it is important to identify the architecture of the shell which will  actually  run  the  installed
       packages, versus the architecture of the shell running the repository software.

COMMANDS

       platform::shell::identify shell
	      This command does the same identification as platform::identify, for the specified Tcl shell, in contrast to the running shell.

       platform::shell::generic shell
	      This command does the same identification as platform::generic, for the specified Tcl shell, in contrast to the running shell.

       platform::shell::platform shell
	      This command returns the contents of tcl_platform(platform) for the specified Tcl shell.

KEYWORDS

       operating system, cpu architecture, platform, architecture

platform::shell 						       1.1.4							platform::shell(n)