Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Functions
- !! Performance Monitoring and WinBatch !!
- AddExtender function - freeing the DLL
- Advantages of While over Goto
- AppExist AppWaitClose Fail
- AppExist Fails
- AppExist Not Working on NT
- AppWaitClose for Terminalserver
- Ask Function Will Not Display
- AskDirectory Flags Not Working
- AskDirectory Questions
- AskFileName Bug
- AskFileName Limit
- AskFileName Window Location and Size
- AskItemList and Switch Statement
- AskYesNo with Custom Button Names
- AskYesNo with Default NO
- AskYesNo without Cancel Button
- BinaryHashRec Examples
- BinaryReadEx
- BoxShut and WBT icon
- Buttonnames function
- Call Versus Include
- Call vs CallExt
- Command Line Limitation
- Concatenate using StrCat to Cat info Together
- Converting files with LF Endings
- Debug window and Longest Line Displayable
- Decipher Debugtrace output
- Dirchange versus LogDisk
- DirExist Failing
- DirHome vs DirGet
- DirRemove Not Removing Directory
- DirSize Function Anomalies
- DirSize Slow
- DiskFree Function
- Diskscan Function
- DiskSize and DiskFree returning incorrect values
- DiskSize and Network Shares
- DiskSize limit
- Display Function and More than 256 Chars
- Display Using Fractional Timeout
- Drop Function
- DropWild Function
- ERRORMODE Suppressing Errors Important Info
- Execute Function
- Explanation of Negative Value in Display Function
- FileAppend is Leaving an End of File Marker
- FileClose Greater than 5 Files Error
- FileCompare - FileSize - FileTimeCode
- FileCopy Eats CPU
- FileCopy Fails going to SMB or UNIX Servers
- FileCopy Failure with McAfee Virus Files
- FileCopy Failure
- FileCopy to a Null Device
- FileDelete Error 1016 when File Doesnt Exist
- FileDelete Returns True but File Shows up in Explorer
- FileExist Check In Use
- FileExist Returns Sharing Violation
- FileExist Unable to Locate an EXE
- FileExtension Example
- FileGet and Unicode
- FileInfoToArray Total File Size Problem
- FileItemize File Mask IntControl 91
- FileMove Function
- FileOpen and Determing if File is Open
- FileOpen on File Opened by Another Process
- FileRead Examples
- FileRename Function General Info
- FileSize Returns Zero
- FileSizeEx and Integer Math
- FileSizeEX Returns Zero for Pagefile
- FileTimeCode Example
- FileVerinfo and Language Keys
- FileWrite Adds CRLF
- FileWrite and CRLF Character
- FileWrite FilePut Benchmark
- Floor Function question
- Fonts in Message Boxes
- Get extension from AskFileName is user did not supply one
- GetTickCount Explained
- IconReplace - IntControl 37 - Not Working
- Icons, IconGroups, and IconImages Explained
- IniReadPvt returns default using Citrix WinFrame
- InstallFile Function and Return Codes
- IntControl 1005 - A Treatise
- Intcontrol 1005 and Shutdown
- IntControl 1005
- Intcontrol 1006
- Intcontrol 1007 and 1008
- IntControl 28 Fixed Pitch Font
- IntControl 30 Allow Protected Renames
- Intcontrol 30 and Shared Mapped Drives
- IntControl 30 Failing to Move File
- IntControl 31...
- IntControl 38 and 73 and WbErrorHandler
- Intcontrol 39-40 and Share Violations
- Intcontrol 50 and Specifying your own URL
- Intcontrol 61 Usage
- Intcontrol 65 and FileRead
- IntControl 67 and Windows 95 Hangs on Shutdown
- IntControl 67 and Windows 98 Blue Screen
- IntControl 67 and Windows NT logs user out rather than rebooting
- IntControl 67 and Windows XP
- IntControl 68 will reboot instead of shut down
- IntControl 76 Explained
- IntControl 92 and the Performance Monitor
- IsInt with Trailing Spaces
- IsLicensed Function
- IsMenuChecked - MenuChange - IsMenuEnabled
- IsNumber Problem
- ItemInsert and the Lists Problem
- ItemSort and Hyphens
- ItemSort and Other Sorting Functions
- ItemSort Reverse Sort Order
- KeyToggleGet and Problem Detecting Key Toggle
- Max Length of an Item in AskItemList
- Message Function and Strings Greater than 261 Chars
- Mod - Modulo - Function
- MouseClickBtn and Sending Ampersands
- NetInfo API Info
- Netware wntRunAsUser and RunwithLogon Problem
- Orphaned Functions
- ParseData Function
- ParseData Removes Quotes
- Performance Counters Disabled
- Persistent Verses Global Variables
- Place AskColor Dialog
- Random() Function
- Run Function Crash
- Run on Win95 Finished but Icon Persists
- Run or Runwait and Second Parameter 125 or more Chars
- RunExit in Win95 WinNT
- RunHide Command Info
- RunShell with Parameters longer than 100 Char
- RunWait - AppWaitClose Failing and Loader Programs
- RunWait 16 bit script doesnt wait for 32 bit apps
- RunWait Not Working with Word Perfect 60
- RunWithLogon Ignores the Display Mode Flag
- RunwithLogon with no password
- RunWithLogon wntRunAsUser LocalSystem Account
- SendMenusTo Not Working
- ShellExecute With Wait
- StrClean Function
- StrFixLeft Issue
- String Comparisons in a Switch Statement
- Switch Statement - Multiple Values Under One Case
- Switch with a Variable Name
- SysParamInfo
- Terminate Function
- TimeDelay and Millisecond Intervals
- TimeDelay Discussion
- WaitforKey and CPU Usage
- WaitForKey Issues
- WildCards with FileExist
- WinActivate Erratic Behavior
- WinActivate with Remote Desktop
- WinActiveChild Failing
- Winbatch hangs on TimeDelay
- Winclose Failure with McAfee Virus
- WinCloseNot Doesnt Work
- WinExeName Returning a Null String on Some Systems
- WinExist Failing
- Winhelp Function
- WinItemizeEx
- WinItemNameId and IP address
- WinItemNameId and WinItemizeEx
- WinMetrics and Screen Resolution
- Winplace and Child Windows
- WinPlaceSet of a Winbatch Dialog
- WinShow Maximizes Window
- WinState Waits up to 8 Seconds
- WinWaitClose( ) with Minimized Windows
- Yield versus TimeDelay
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Message Function and Strings Greater than 261 Characters
Keywords: Message 261 262 strings
Question:
I'm using the Intcontrol(1006 function. I've got an unparsed command line that's more than 261 chars long.With the following code:
unparsed=IntControl(10006,0,0,0,0) Message(StrLen(unparsed), unparsed)In Windows 95/98 the variable contents come in OK (it displays more than the 261 chars.)
In Windows NT 4.0, the message statements only displays up to 261 chars. I don't get any error message, but it won't display past that length.
Do you have any idea why the differences between the two operating systems?
Answer:
It's there. Maybe save it to a file and look at it.It is limitation of the windows message box function. It was not designed for real long strings.
Article ID: W14233
Filename: Message Function and Strings Greater than 261 Chars.txt
File Created: 1999:10:26:11:22:40
Last Updated: 1999:10:26:11:22:40