Database Search
TechHome
 |
- 1028 Error using Go rather than Run Button
- Add Separator to the WinBatch Studio Toolbar
- Adding File Types to Studio
- Background Check
- Bitness of WinBatch Studio
- Block comment and uncomment code
- Change File Save-Open Default
- Change Studio Default File Open Path
- CLR Files for Other Extensions
- Code to Convert Hex to Decimal in Studio
- Custom Syntax Colorization
- DirGet returning Winbatch System Subdir
- Disable Studio Keyboard Shortcut
- Extended ASCII Cursor Placement Issue
- F12 in WinBatch Studio
- Foreign Language Search
- Hitting n Key Causes Strange Behavior
- Interactive Debug Mode and GoSub
- Keyboard Shortcuts
- Keyword Lookup not Working
- Manipulate open file or highlighted lines in WinBatch Studio
- Null characters found
- Pass Params in Winbatch Studio
- Pass Parms to WBT while in WB Studio
- Problem wRight wLeft and wGetChar
- Recreate WinBatch Studio Environment
- Regular Expression searches in WinBatch Studio
- Save As Dialog in WB Studio
- Shift-F1 stopped working
- Turn off WinBatch Tips
- Unable to Run WIL Extension
- Using Debug to See Contents of Array in Studio
- WinBatch Studio Choppy and Slow
- WinBatch Studio Window Missing
- Wrap lines to a specific length
- WSHELP.DLL - WSHELP.INI question
- WSINIT.DLL Process Stays When Studio Opens
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Null characters found
Keywords: WinBatch studio null chars
Question:
Hello,I noticed that after upgrading to Winbatch 2001k, I keep getting the following popup window when stepping through many of my scripts in Winbatch Studio:
Null characters found in file. Replace with ASCII value 255? Yes or No
If I answer No, I get the following Winbatch error:
Nulls encountered in file. Use another editor to edit this file.
If I answer Yes, my script is replaced with weird characters. Ether way, I can't use Studio to debug my scripts anymore.
I always use Notepad as my script editor. I don't ever remember having this problem with version 2000.
I've really come to depend on Studio and now I am unbale to use it. Can anyone help?
Answer:
What is happening is you are debugging a script that places calls to a .wbc file (complied called script) or other executable that is compiled. The replaced characters that are weird are the text versions of the files that are being called. If you are 'calling' a called script, try replacing all of the ".wbc" entries with ".wbt" and see if you get the scripts that you wrote, before they were compiled.User reply:
You are right...I changed my Call statement from a .wbc to a .wbt and it is working just fine. Thanks..Article ID: W15777
File Created: 2003:05:13:11:30:02
Last Updated: 2003:05:13:11:30:02