Database Search
TechHome
 | |
|
- 10130 BoxesUP Invalid Rect String
- 16 versus 32 bit EXEs
- 3088 or 1591 - FileRead - Attempt to Read Past EOF
- All Compiled Exes Start to Crash
- Code Sign Error
- Compile Error 1125 FileTimeGet File Not Found
- Compiled EXE Size Compared to WBT
- Compiled vs Studio and Includes with UDFs
- Compiler 1126 BinaryAlloc Error
- Compiler Error 1337 Dialog Box Creation Error
- Compiler Explained
- Compiler Hangs
- Compiler Not Remembering Previous Settings
- Compiler Removes Remarks
- Compiler Runtime Error - EXE File Open Failed
- Compiler Source File Limit
- Compiler Splash Screen Explained
- Compiler Version Information Field Limit
- Compiler Versions with Compression
- Decompile a Compiled WB EXE
- Determine Version of Compiler Used to Compile an EXE
- Distinguish between WBTs and WBCs
- Does it Run Faster or Use More Resources
- Encode Error - Input File Too Big
- Encode for Calls from EXE files
- Encryped Encoded Verification Failed
- Encrypted Encoded Error
- Exe Crack Protection
- EXE Wont Launch on other PCs
- Extenders not Showing up in Compiler List
- Extract Files on Removeable Drive
- Extract WIL DLL To Specified Directory
- ExtractAttachedFile only Newer Files
- Firefox Problem Downloading Compiler ZIP
- How to Embed Source Code
- Icon Formatting Tools
- Icons and Compiler 2002
- Icons and the Compiler (old versions)
- Icons
- Include Shortcut as Other File in Compile
- Include Statements - How They Work
- Large versus Small EXE Model
- Missing msfvw32 dll
- Newer WBCs called from Older EXE
- Other Files Check Before Overwrite
- Other Files Explained
- Output File Open Failed
- Saved Compiler Settings
- Using WBC Files
- WB EXE is in Use by Another Program Error
- What Encryption is Used
- Win32 Network Extenders and Compiler
- Work Buffer Error when Compiling
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Compiler Splash Screen Explained
For many years where were a few features of the compiler that required you to stop and push a button. One way or another.
It was quite obvious that the compiler could just keep on running and do its job and exit, but there was always some little button you had to press each time someplace.
Turns out it was to force recognition of the product and require you to know it was there.
But it was a nuisance.
With the current scheme, with the big blue background window, it make it more obvious the program is running, and has allowed us to drop some of the peskier required button pushes, as the background window now serves this purpose.
If an option were installed to bypass the background window, I would imagine that some of the required button pushes would come back.
Depends. It a new thing and of course subject to modification as long as the lawyers are happy enough. They like the old way of doing it, primitie though it was, and have bought off on this new way. So it's not realy a techinical problem, but more of a copyright issue.
Article ID: W16911
File Created: 2007:07:03:14:26:58
Last Updated: 2007:07:03:14:26:58