Winbatch gui tool


















At that point, the "WinBatch Navigator", which is just yet another WinBatch script, pops up giving you a number of handy choices. You can look at the WinBatch Navigator display screen and figure out what version of WinBatch you have managed to install. If you have just downloaded WinBatch, it will, presumably, be the latest version. Assuming that you see the dialog box pop up, then WinBatch is properly installed on the system.

Also note that the entire WinBatch install process is nothing more than a rather complex compiled WinBatch script. Now it is time to write a few simple programs to get started. The first order of business is to find and run "WinBatch Studio". It should have a little blue owl icon next to it. That will launch WinBatch Studio. The very first time you launch it, it may decide is has to update some registry configuration information, and will display a small note to that effect.

If this happens, close WinBatch Studio and start it up again to get the best results. Now you should be looking at the WinBatch Studio screen. Select "File - New" to open a new document window - or hit the first button on the toolbar - which is the same thing. If you hover your mouse over a toolbar button a little "tooltip" should appear telling you what the button does. So let's type in the first program. Enter the following line into the new window you just opened.

Now that we have the line in the window, we have to save it. Hit the "File - Save" menu item - or the third button on the button bar. The file save dialog should pop up. Select or make a new a directory and type in a file name. Follow the file name with a. For example a filename of MyFirstScript. Now that it is saved, you can run it. There are several ways to do this. We'll start with the easiest. Locate the RUN button on the toolbar. The Run icon looks like a stack of papers with a blue down arrow on top.

Click the RUN button and your script should run. One of three things might happen at this point After getting your one line "Hello World" script running, you might try changing it a little and see what happens. In addition, you might try copying and pasting the example scripts shown up above. The default color of WinBatch keywords is blue.

To get help on a keyword, first click it, then right-click it. A popup menu should appear. Select the "Keyword Lookup" from the popup menu. The appropriate page from the correct help file should appear on your screen. The right-click menu in WinBatch Studio has another great feature for new users. There is a "Insert WIL Function" menu item that can insert a function directly into your script, ready for immediate customization.

This can save time digging through the help files. You will note that WinBatch function names start with a function "group", in that the functions that deal with files start with "File", such as FileCopy , FileDelete , FileMove , and functions that deal with directories aka folders start with "Dir", such as DirGet , DirChange , DirMake , and so on.

This is handy for looking functions up in the documentation. The function you are looking for usually clusters together alphabetically with related functions i. Functions of a feather flock together. Speaking of help files, WinBatch has a lot of them. Dozens actually. Two main ones for WinBatch itself, one or sometimes two for each extender, and a few "free-floaters" that contain interesting information but are not tied to any particular function.

It combines multiple. So, as you install some new WinBatch product i. I am a qualified network engineer and systems architect.

What I am NOT is a programmer. I understand syntax and how to read code, but I do not write code. Despite this, I have been able to create some very professional looking applications and implement them for common tasks. While WinBatch itself introduces some overhead in the way of DLLs that need to reside on the machine in order to quickly process scripts if you choose not to compile them , what it gives you is flexibility to quickly and efficiently get tasks done, including scheduled runs, updates especially flat file updates and it will encapsulate VBScript and other languages fine if you know what you are doing.

When you refer to it not looking professional, this may be due to either your programmer not knowing HOW to make it look ANSI standard, or you have the actual product installed as opposed to just making the DLL calls. All in all, I have used KixTart and WinBatch for scripting and both have their strengths, but WinBatch gives you incredible flexibility especially when combined with the compiler to offer solutions for non-programmers to perform automation.

I used Winbatch to update routers automatically with new configs. When ever I wanted a refresh, I put in a new dated file into my update directory, called out to the routers and updated the confg files. It also backed up the existing files, did versioning, and monitored upstates. There is no doubt that C and VBScript allow you to do some nice functions with RegExp and such, but Winbatch gives you those functions through wrappers, and there is little in the way of automation I haven't been able to do.

I am obviously a proponent of WinBatch, but I am not discouraging the use of other languages. I am just saying don't underestimate its power. I think you are more than likely fighting an inexperienced programmer, not the product. I have been using WinBatch for the last 5 years in our IT shop to do a multitude of automated tasks that would otherwise require manual intervention. Prior to that, all of our scripts were in Windows batch files and VB scripts.

I have converted most of our old scripts over to WinBatch because it easy to expand on the functionality and do more with the script than was ever possible before. We don't use it as a software distribution platform however. It is used as an installation wrapper, to make the installation entirely automated and hidden from the end user. It really helped for the small application I automated yesterday. Your order and shipping department were great!

I am delighted to say that this Upgrade reached me yesterday morning and installed beautifully. It greatly impressed me that it did NOT over write my configuration files, merely loading new versions with a NEW prefix to the filename.

That is highly intelligent program design. I just wanted to thank you for a great product WinBatch and congratulate you with your excellent technical support. The support pages are the best I have found on the net so far, and I have yet to get a problem I haven't found the answer to very quickly by searching the site.

My company is using Winbatch to update our website with news and recordings of our broadcasts, and it's working excellent. You guys are great.

I never expected such a quick response. The script works beautifully now. It could use a little streamlining to account for those machines that don't require the registry hack, but that's about it.

I ran into your site by hazard and I wanted only to congratulate you for the effort and the good work. WinBatch has made me a hero at my company.

Our project required us to manually download thousands of cameras from Kodak's Photonet site. Manually, it would take me 5 minutes to go through the Kodak site to download one camera.

With WinBatch, I can start a script when I leave at and download cameras over night. Just felt like telling you that "you are simply the best". No problems at present, but I really enjoy reading your forum because it's fast, knowledgable and entertaining. Since I mostly post problem reports, I thought I'd mention that I am thoroughly impressed with this product. I've only just begun to use it and already my productivity has increased significantly over what I was using.

Almost every day I find some little feature that works just like it should. The bookmark facility is stupendous. The only thing I would add there is some form of permanent named bookmark like in Word so I could mark section of code and go directly to them by name and which wouldn't get erased by the erase all bookmarks button. The color coding is unbelievable. I've avoided several typos that would have caused program failures that I would have had to debug later.

The only minor thing I'd like is nested comments since Rexx supports that. Search and replace and find are excellent. I cannot praise y'all enough for this wonderful product. I am a Software Engineer at Turner Broadcasting Systems in Atlanta, Ga and was tasked to integrate the installation of several different products and applications i.

This tool paid for itself within DAYS! My team has delivered, in weeks, an installation utility that would have taken months to do in a traditional programming language, perhaps not even delivering the same result.

It took me a matter of days to ramp up on the WIL language, and once there, I was blown away by the level of power and flexibility it provided. Y'all have really delivered the goods. I just recently heard about your WinBatch products from another developer, so I thought I'd better check them out, so I downloaded WinBatch evaluation and a couple of add-ons for testing.

Just a simple plug to tell you how much I like your product. Started testing, things seem to be functioning, as always your tech support is 'Top Drawer' and we appreciate the support! I am a long time user of Winbatch and have as of today joined the ranks of Winbatch Compiler users. I know all to well the issues of providing tech support over the phone. This background BS is just so you know the source. For the past couple of years I've reached Deana a lot when I call for support.

I just want to say that she is the best support person I have ever had the occasion to work with - bar none! Her patience and knowledge is excellent. Please give her several Gold Stars if not a big raise - she deserves it! Your help is always right on target, but your suggestion that the reason I was not getting all of the text in a combo box because the box was not being populated until it was dropped down was stunning. Thank you for your help yesterday. I also wanted to mention that was the best support call I have ever made.

Nice work by you, and the WinBatch people. Feel free to pass this note on to your supervisor, atta boys are always nice. These were the best newsgroups I have ever participated in. You go to their site, and they have an easily navigated and searchable The examples and questions were very good - lots of times I found info their and didn't have to go to the newgroup portion.

But, if I did There was never a newsgroup post that went unanswered. Even if it was him just saying "Clarify more, and here is my guess".

Even that "guess" alone, puts confidence that somebody is thinking about my problem. Other people answered posts, but he was the MAN! Imagine the confidence you will have, when you post a message in the morning Or if not the end of the day or if you post your question at the end of the day -- as soon as you get into work -- you fire up the newsgroups and wow!

Those newsgroups were beautiful!!!! I wanted to take a moment to let you know how much I appreciate some of the people you have on your staff.

It had to do with WinBatches locking up during login script processing, and the problem was determined to be with our Virus software, McAfee. But, that simplifies it greatly. Their hard work and cooperation and just plain brain power figured this one out. However, I always win out when they look at my scripts I have created versus the other packages.

Your staff's level of customer support is a HUGE factor in this. Please do! It's a great tool and you should work on reaching the lab crowd. Everyone I've recommended it to in labs, absolutely loves it!!

Here is my most recent application: Since 3 months I have a new job. As an it professional, I want to do things efficiently. The guy I was replacing was very badly organized and in the network, the documents were placed everywhere with no structure! So I created a script that scan's the computer's Hard Drive, looks for all folders that contains up to 10 file extensions and then creates an batch.

Nut it's not all, all the help I received for the guys at this web board is a lot more valuable then the actual price of WinBatch! I give a big thanks to Marty for all the help I received for him. And thanks to all of you guy's!! You make my job a lot easier! Well I use WinBatch anytime I think it will be hard to explain to an average user or when I need something that need to be done 1 00 of times. I also customize "standard" tool s like EDI converter, interfaces there is always a point where you need to act.

I work in the technical development area for a bank. We have NT 4. We are in the process of converting the branches to a WAN. This system delivers program updates to branches and is comprised of 10 programs that interact with each other.

Another major system keeps the data tables used in the branches up to date. There are 5 primary data files downloaded to the servers nearly every night and loaded into MSSQL tables. There are another 65 tables that are updated with programs written in WinBatch. Three years ago we designed a software auditing system in WinBatch. We are lucky in that all of our servers and workstations in the branches run the same set of software. The system scans each server and workstation for specified file types, compares them against a list of programs that should be present and then returns the data to a central location.

Another WinBatch program is used to compile the audit results from each server into seven reports. From those reports we can tell what software is missing, if software has been loaded, etc. Another system designed in WinBatch was a release software update tracking system. Each release is given a unique name.

The system took messages returned from the servers and compiled so that we could instantly tell when a site did not load a release correctly, what sites had loaded a particular release, etc. That system was used for about 2 months until communication problems rendered it useless - the programs worked and compiled the data that was returned but not all of the data was always returned.

A program I recently wrote in WinBatch interfaces to a transmission program called XCOM that allows me to create a series of jobs to send and execute a batch file on an set of desired servers.

Another cute program that we wrote in WinBatch allows us to encoded a password into a series of numbers based on a cute algorithm - the encoded password can then be loaded on remote systems. We use this to change the main system passwords on all servers.

We have written several programs to script the installation of GUI based programs when we did not trust the users to type in information correctly. In addition, a workstation backup and restore system based around the product NovaDisk from NovaStor was scripted using WinBatch so that the user only had to click one button to start the restore. Many of the programs written make use of WinBatch's ability to manipulate the registry.

We just used the Windows NT networking extender to change the sign on account for a service to another account. My favorite commands center around the File handling , list manipulation and string manipulation. There are so many useful things that can be so easily with these commands.

In the past 4 years we have written about different programs to support the branch servers, update data, move files, etc. Out of the program I would venture that of them are in WinBatch. WinBatch is everywhere!!! I have no programming formation, but I developed a commercial application I distribute to health professionals. After unsuccessful attempts to work with contracted programmers, I discovered WinBatch and developed the Windows version myself.

I used it for my installation routine, CD production and so on. I also use it for:. Esp Internet related things, like check that web page is working, check that DNS server is working, check that e-commerce server is working, send email with attachments. In many cases, I've grafted in a perl routine to handle things WBT does poorly.

See my many messages in your wish-list pile.



0コメント

  • 1000 / 1000