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 98 Not Remembering Previous Settings
Keywords: compiler 98 CMP files
Question:
When I upgraded from 96 to WinBatch 98, I recompiled all my scripts and put the new DLL out on the servers. My problem is this:With all previous versions of WinBatch, when I went to compile interactively, it would remember the last .wbt that was compiled, what kind of compile, and the destination. If I changed the source to a different file, it would bring up the settings for the last time I compiled that .wbt.
That was very useful when working with 30 or 40 different Winbatches at a time, I didn't have to keep digging down through subdirectories everytime I change the program I compile. 98 isn't holding this info - if I change source, it resets the destination to the same directory as source, NOT the last place I compiled it to. Don't know if it's a bug, or something I did. Any suggestions???
Answer:
- The information is saved in the CMP file with the same name as the WBT file in the same directory as the
WBT file. Make sure you are not deleting those files if you want to use the previous settings.
The CMP files are new. They are really just INI files. You can examine them. They retain all settings.
- If the WBT directories are read-only maybe the information cannot be saved.
Article ID: W12776
Filename: Compiler Not Remembering Previous Settings.txt
File Created: 1999:04:15:16:49:34
Last Updated: 1999:04:15:16:49:34