1. What Windows platforms is WinBatch supported on?
WinBatch is currently supported on the following Windows platforms:
- Windows 2000 Client
- Windows 2000 Server
- Windows XP x86 Client
- Windows XP x64 Client
- Windows 2003 x86 Server
- Windows 2003 x64 Server
- Windows 2003 x86 R2 Server
- Windows 2003 x64 R2 Server
- Windows Vista x86 Client
- Windows Vista x64 Client
- Windows 2008 x86 Server
- Windows 2008 x64 Server
- Windows 2008 x86 R2 Server
- Windows 2008 x64 R2 Server
- Windows 7 x86 Client
- Windows 7 x64 Client
- Windows 8 x86 Client
- Windows 8 x64 Client
- Windows 2012 x64 Server
2. How is WinBatch used most?
WinBatch is used to write custom system automation
Busy system administrators and power users need
rapid solutions to Windows problems. WinBatch
provides results when time is short. Here's why.
It is simple to learn and maintain. It includes
over 500 functions for scripting and rapid access
to Windows APIs. It adds 26 extender libraries
that feature networking, data connectivity, and
Internet automation. Over 2,500 practical examples
and case studies fill a Web database.
3. What is included in WinBatch?
WinBatch is a scripting "environment". It has
a complete scripting language. It includes an
intelligent code editor, a code debugger, a GUI dialog editor,
a window manipulator (RoboScripter), and over 26 special purpose extended
function libraries. It also includes phone, email,
and online technical support.
4. What is WinBatch?
A simple, structured, scripting language called
WIL (Windows Interface Language.) All scripts
are processed by an interpreter--even those made
into executables with the WinBatch Compiler.
5. What is WinBatch best used
IT administration. Among WinBatch strengths is
the ability to automate Windows and Novell networking.
Together with all the other capabilities in Windows,
this leverages Windows to save time in managing
6. Why use WinBatch instead of
VB and Perl?
The different tools have different uses. WinBatch
is optimized for PC automation. VB is built to
develop database applications. VBScript is designed
for Web page scripting. Perl is designed for text
processing. While all these options share capabilities,
they work more quickly and dependably when applied
as originally intended.
are WIL "extenders"?
Extenders are special purpose libraries of functions
designed to simplify network administration, PC
management, the control of peripheral hardware,
and rapid Internet use. Currently there are over
8. What is the difference between
WinBatch and the Compiler?
WinBatch is a scripting environment designed
to automate standalone PCs. It includes desktop
menu utilities for adding features to the Windows
File Explorer and Start menu. A RoboScripter
utility, is included to streamline software
The Compiler encapsulates scripts together with
the executable code to make executable runtimes.
These run from servers or workstations. Licensing
includes rights to distribute or sell compiled
scripts without limitation. (Users of compiled
scripts do not have use of the desktop utilities
included in the single PC version of WinBatch.)
9. Can WinBatch automate third-party applications?
The ability to control and assist the movement of data between applications
is one of the key strengths of WIL. There many ways to share data between applications:
using the Clipboard, Dynamic data exchange (DDE), Control Manager Functions,
SendKey functions and COM ( Component Object Model ).
10. How does WinBatch work with COM objects?
WinBatch includes OLE automation. WinBatch variables
can hold variants and collections. VB syntax in
a WinBatch script is like it is in VB. WinBatch
offers a unique blend of structured programming
along with the ability to work with COM objects.
WinBatch can be used in applications requiring
ADO, ODBC, DDE, and WMI.
11. How does WinBatch work with dotNet Classes?
WinBatch supports access to the Microsoft dotNet Framework. WinBatch makes
this possible by hosting the common language runtime (CLR) and exposing
functionality for creating and accessing the members of classes, structures
and enumerations of managed code assemblies (DLLs) that are part of or based
on the Framework.
12. Why use WinBatch instead of VB, VBA or VBScript?
WinBatch is less complex. It is has the advantage
of being optimized to batch process sequences
of operations. WinBatch is glue that links all
this: software applications, multiplatform networking,
Internet access, and peripheral devices.
13. I don't want to program.
How do I locate a WinBatch programer for hire?
The WindowWare Web site, www.winbatch.com, has
a "Links" link on
the home page. It goes to a page with references
experts. Also, you can search for "resume"
together with "WinBatch" in your favorite search