Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Me? I picked up a CD called Blackhawk for Windows 95, way back in Nov 1996 and it was one of the shareware programs on it. Printed out the manual (2 or 3 inches thick) and starting going at. Never looked back. How about you?
Once the dream come true I thought of automizing 3270 app with it and etc. etc. I am still with it in 2003 and I widespread Winbatch everywhere.
I asked Google, an it gives me a list of Batch related products out there.
I tried one, looking simple, and it was really simple and it's behaviour under stress was ugly. After a few days I deleted that bad app. So I've tried WinBatch and quickly I had the impression, that this company knows about how making things simple, but keeping it effective and intelligent.
That was the love starts.
Since they I've managed to get at least 4 other companies that I've worked for to by the Compiler.
I couldn't do without now.
I asked a programming friend for advice and he said it sounded like I would need to either write new software myself (not in my job description, and probably a life long project) or find a way to control it with another program. For a few weeks I hacked around with other software to send keystrokes, monitor ports, etc... but they didn't work.
Then my friend called and said he'd been joking about my plan with a networking colleague who suggested I try winbatch. I downloaded an evaluation, whipped up a few quick tests over the weekend, wowed the group with the minor improvements made in 2 days and convinced them to buy me a copy. They did and by the end of the next week I had a rough script that did everything they had asked for. Then I found the WebBoard and in after a few hints from Marty I had the script perfected. From there I apply WinBatch wherever I can.
WinHide(WinGetActive())That alone - and the ability to unhide such windows - is worth the purchase price of Winbatch.
In 1996 I was starting a project to automate the distribution and update of sofware packages on campus. The deadline meant there was no time to implement it in C++ or a similar language. Another group on-campus had used WinBatch to automate some tasks and spoke very highly of it. What sealed the deal for me was the Tech Database which was (still is) an incredible repository of tips, tricks, and useful snippets.
2 weeks later, was walking past a cow-orkers desk, and saw a WB box, (complete w/manuals & CD) sitting on his shelf. Asked if he used it, he said it was left by the previous occupant, he'd never used it, and had no idea what it was for. (this was someone working in the AUTOMATION department of our company!) I borrowed the copy, got a new menu working for my group in no time and was hooked.
No one bought into the menu system I wrote (they preferred the old Novell menus that were impossible to maintain), and it died. 2 years later, I was transferred to the automation group and found WB everywhere.
Have now convinced my second employer to purchase WB, and am happily saving myself hours a day of tedious hand running applications!
Of course, the wonderful support from this board is integral to its abilities.
The program used some strange scripting thing called "WIL" to do stuff behind the scenes. I decided to try and figure out how this "WIL" thing worked.
It took a few years, but I finally convinced my colleagues at work to look at WinBatch for writing automation routines and utilities. Now we wouldn't dream of not having it around.
I also have a friend who has never been able to make the leap from the old 8-bit programming environments (Apples, Commodores, etc) to Windows programming. I tried, C, Java, VB... He just could not make the transition. WinBatch is the first language that he has been able to grasp and use successfully since BASIC - a testament to WinBatch's objective to make Windows programming simpler to do (though he still complains about the demise of the old CLI style screens for I/O).
Article ID: W15441
File Created: 2017:07:28:13:00:02
Last Updated: 2003:05:13:10:27:52