Mabry EncoderX 1.00.011
<
Mabry Softwares Encoder/X ActiveX control and COM object provides an easy and powerful way to handle the data encoding formats used by various Inteet protocols. The four basic encoding types used by protocols such as mail and news are Base64, BinHex 4.0, Quoted Printable, and UU. Encoder/X provides a number of functions to convert back and forth between binary (or text) data and any of these formats.
The Encoder/X control provides unlimited flexibility when it comes to specifying source and destination for the data being encoded or decoded. The following methods fulfill basic requirements: FileToString, FileToFile, StringToFile, and StringToString. In addition, Encoder/X utilizes our new Streams technology to provide a fully extensible way of accessing and storing encoded/decoded data.
Our Streams objects include the following: MemStream, VirtualMemStream, and FileStream. Any of these can be used by Encoder/Xs StreamToStream method. And there are StreamToFile, StreamToString, FileToStream, and StringToStream methods. If, for instance, you have a file containing a huge amount of data, you could create a VirtualMemStream and then use the FileToStream method to decode the data. Using this technique, you can easily access many tens of megabytes of data.
Encoder/X also makes use of the IMStream interface. The Encoder and Decoder objects Implement the IMStream interface, and each of them has an In property to which an IMStream object can be assigned. This makes it easy to perform a number of conversion jobs. For instance, if you need to convert UU encoded data stored in a file to Base64 in memory, you could do that easily by following this procedure:
1. Create a FileStream for the source data to be decoded
2. Assign the source stream to the Decoders In property
3. Set the Decoders EncodingType property to UUencoding
4. Assign the Decoder Out itself to the Encoders In property (this works because both Encoder and Decoder Implement the IMStream interface).
5. Use the Encoders IMStream interfaces Read method to read data from the Encoder.
To explain when you call the Encoders Read method, it calls the Decoders Read method to get some data to encode. The Decoder decodes the data and retus it to the Encoder that encodes the data and retus it to your program.
Of course, there are a number of ways to accomplish this same task using Encoder and Decoder. You will be able to choose the way that works best for you in any given situation.
And for those of you who have _really_ large amounts of data to encode or decode, Encoder and Decoder objects provide background processing on a separate thread! If you set the Blocking property to False and call one of the methods, the method call will retu immediately, and the method itself will begin executing in the background. As data is encoded or decoded, Progress events fire so the programmer can provide a visual indicator to the user. When the method has finished, the Done event fires.
And, last but not least, Encoder/X comes in both Active/X Control and COM Object versions. We strongly recommend using the COM object wherever possible. Its smaller, slightly faster, and doesnt impact form load times.
Mabry Softwares Encoder/X provides the most versatile and powerful Encoder and Decoder objects available.
About Encoding
Encoding Basics
For historical reasons, there are e mail systems on the Inteet that are not able to correctly transmit and/or receive e mail messages containing 8 bit data. Instead, they can process only 7 bit data.
Restricting data to 7 bits was fine when only text messages were being transported. But now we want to transmit everything images, pictures, sound, etc. Such items are transmitted as attachments. Since these attachments require that each bytes 8 bits are transmitted, it is necessary to have a way to convert collections of 8 bit data into 7 bit data to accommodate the 7 bit e mail systems.
Note: in the context of e mail programs, encoding refers to the process of tuing 8 bit data into 7 bit data. Decoding refers to the inverse operation.
Types of Encoding
There are four types of encoding commonly used in email messages: Base64, Bin Hex 4.0, UUencode, and Quoted Printable, all of which are supported by the Mabry Encoder/Decoder objects and controls.
Base64 is the preferred encoding format. Base64 works very well and has none of the problems associated with the other formatting schemes. Unless there is some unusual compelling circumstance, you will want to use Base64 to encode messages. But you must also give users of your program the option to select other encoding types. Some e mail clients have limited capabilities and demand UUencode or one of the other methods.
Bin Hex 4.0 is rarely used since it is really a Macintosh format.
UUencode preceded Base64 and is very similar except that it suffers from multiple almost the same implementations no doubt a result of its origins in multiple almost compatible UNIX systems. But again, you must be prepared to receive UUencoded email. UUencoding also suffers from a deficiency in its encoding scheme in that certain characters it uses may be modified as the email passes through various systems especially those that convert ASCII to EBCDIC. For these reasons, avoid UUencode whenever possible.
Quoted Printable is not suitable for encoding large amounts of data because it uses three 7 bit characters to encode one 8 bit character (Base 64, Bin Hex 4.0, and UUencode use 7 bit characters to encode every three 8 bit characters). However, messages encoded with Quoted Printable are seen from time to time and your program must be prepared to decode them.
About Streams
What Are Streams?
Streams are used to store data. Three standard stream types are provided by Mabry: MemStream, FileStream, and VMemStream. Each type has different characteristics in terms of speed, memory usage, and easy persistence.
Any object that implements the IMStream Interface has access to one of the five IMStream Interface methods: Read, Write, Seek, Clone, and Copy. See the IMStream Interface documentation for more details.
When Should I Use Streams?
The Mail/X Message and Part Objects both expose a BodyStream property. When a new Message or Part is created, the BodyStream property can be used to access a MemStream Object.
If you have a file and you want to send its encoded contents in a given message, you can use the FileToStream method to encode the contents of the file and place the result in the stream. Later, when the message is transmitted, the contents of the stream will be sent.
But what if you have one or more huge attachments? Fifteen megabytes or more are often seen now that high bandwidth connections are becoming the norm. The encoded data is going to total 20 megabytes and, while it is possible to use the default MemStream Object, it is hardly a good idea. In such cases you can create either a VMemStream, which uses virtual memory, or a FileStream. Then you use the Encoders FileToStream method, as before, and assign the stream to the Messages BodyStream property.
Because the encoded data is stored on the disk in a temporary file, very little RAM is used and the programming model hasnt changedt, making it easy to make on the fly choices regarding the type of stream to use in a given situation.
Samples
The samples in this section are intended to demonstrate only the basic uses of the Encoder and Decoder objects. More complicated uses are demonstrated in the sample programs included with the Encoder/X package.
Visual Basic
Encoding A File
This sample demonstrates how to encode a file and place the encoded data into a FileStream object. Note: your VB project must reference the Encoder/Decoder and Stream objects in order to implement this code.
Create objects
Dim Encoder As New Encoder
Dim DstStream As New FileStream
Trap errors!
On Error Resume Next
Encoder.FileToStream "c:\somefile.exe", DstStream
If (Error) Then
MsgBox "Encoder failed "
Encoder.LastErrorMessage
End If
See what our customers have to say about Encoder/X.
View Encoder/Xs release notes.
ActiveX Control (32 bit OCX)
File Name ENCODEX.OCX
Compatibility VB 5.0 and 6.0, VC 5.0 and 6.0,
Access 95 and above, VFP 5.0 and 6.0
Built Using Microsoft Visual C++ v6
Control Elements Controls
DecoderXCtl
EncoderXCtl
BUY Mabry EncoderX 1.00.011 15$
TAGS\: low cost Mabry EncoderX 1.00.011, download Mabry EncoderX 1.00.011, low price Mabry EncoderX 1.00.011
1994/06/29
1994/06/27
Mabry FTPServerX 1.00.054
Mabry FTPServerX 1.00.054
<
FTPServer/X makes it easy for you to put up an FTP server. FTPServer/X comes in both ActiveX Control and COM Object forms to make it easy for you to integrate it into nearly any Windows programming environment. When you use FTPServer/X, you have complete control over user access, directories, file uploads and downloads, deletion, etc.
You can have a fully functional FTP server up and running within minutes of installing FTPServer/X. FTPServer/X acts as a full FTP server by default.
Events notify your program when the user requests to download a file, upload a file, create a directory, delete a directory, etc. Through these events you can thoroughly control the users access and modifications to your server. You can make it wide open or you can simply allow them to download a single file or anywhere in between.
FTPServer/X supports Fast Notifications. Fast Notifications allow your code to receive events far faster than through the normal event scheme. This means that your server will run quickly and with less CPU load.
If you need to provide a complex server to provide user patches and updates, FTPServer/X can do the job for you. Or, if you just need to put up a simple FTP server for inteal use, FTPServer/X will do the job quickly and easily.
BUY Mabry FTPServerX 1.00.054 15$
TAGS\: low price Mabry FTPServerX 1.00.054, oem Mabry FTPServerX 1.00.054, download Mabry FTPServerX 1.00.054
<
FTPServer/X makes it easy for you to put up an FTP server. FTPServer/X comes in both ActiveX Control and COM Object forms to make it easy for you to integrate it into nearly any Windows programming environment. When you use FTPServer/X, you have complete control over user access, directories, file uploads and downloads, deletion, etc.
You can have a fully functional FTP server up and running within minutes of installing FTPServer/X. FTPServer/X acts as a full FTP server by default.
Events notify your program when the user requests to download a file, upload a file, create a directory, delete a directory, etc. Through these events you can thoroughly control the users access and modifications to your server. You can make it wide open or you can simply allow them to download a single file or anywhere in between.
FTPServer/X supports Fast Notifications. Fast Notifications allow your code to receive events far faster than through the normal event scheme. This means that your server will run quickly and with less CPU load.
If you need to provide a complex server to provide user patches and updates, FTPServer/X can do the job for you. Or, if you just need to put up a simple FTP server for inteal use, FTPServer/X will do the job quickly and easily.
BUY Mabry FTPServerX 1.00.054 15$
TAGS\: low price Mabry FTPServerX 1.00.054, oem Mabry FTPServerX 1.00.054, download Mabry FTPServerX 1.00.054
1994/06/24
Mabry FTPX 2.03.051
Mabry FTPX 2.03.051
<
Mabrys FTP/X ActiveX control provides easy, high level access to the complete FTP client protocol (RFC 959). In addition to capturing server directory listings into a string array property, the new FTP/X also makes the results available as an ADO Recordset providing easy access to the various fields that a server retus. The FTP/X also has powerful built in features to support debugging and non standard servers using the Quote method.
The 32 bit FTP/X comes as both an ActiveX control (OCX) and a COM object (DLL), so you can use it in nearly any mode programming environment. As a light ActiveX control/COM Object, FTP/X doesnt require any bulky MFC DLLs to run. Your web based applications (VBScript, ASP, etc.) will download faster, your installation package will be smaller, and youll have no problems with different versions of DLLs on your users systems. And, because its both an ActiveX control and COM Object, FTP/X will run in Visual Basic, Visual FoxPro, Inteet Explorer, Delphi and any other environment that supports either ActiveX controls or COM objects.
A common problem with FTP servers is that there is no official standard when it comes to the format of directory listings. The exact format of the data retued by the server may vary depending upon the system type. The FTP/X control solves this programmers headache by automatically parsing the data and making it available to your application as a familiar ADO Recordset object. If the servers format is not suitable for the controls parser, a new DirItemPatte property can be used to specify how the fields are to be parsed. For those who would rather handle the data themselves, the data is also presented in its original format via a string array property.
Both the FTP/X ActiveX control and COM Object use the normal event driven programming model or Fast Notifications. Fast Notifications allow your program to quickly receive events through simple functions, rather than going through the overhead to fire an event. This reduces the amount of time required to handle an event.
FTP/X supports non blocking (asynchronous) mode as well as pseudo blocking and true blocking modes, to meet most any programming requirement. FTP/X is firewall friendly complying with the Firewall Friendly FTP Specification (RFC 1579). From behind most firewalls, your applications will be able to communicate with exteal FTP servers.
Mabrys FTP/X ActiveX control requires no user input to run. The FTP/X control can run completely in the background under program control. This allows your program to take care of file transfers while the user performs other tasks.
BUY Mabry FTPX 2.03.051 15$
TAGS\: low price Mabry FTPX 2.03.051, oem Mabry FTPX 2.03.051, low cost Mabry FTPX 2.03.051
<
Mabrys FTP/X ActiveX control provides easy, high level access to the complete FTP client protocol (RFC 959). In addition to capturing server directory listings into a string array property, the new FTP/X also makes the results available as an ADO Recordset providing easy access to the various fields that a server retus. The FTP/X also has powerful built in features to support debugging and non standard servers using the Quote method.
The 32 bit FTP/X comes as both an ActiveX control (OCX) and a COM object (DLL), so you can use it in nearly any mode programming environment. As a light ActiveX control/COM Object, FTP/X doesnt require any bulky MFC DLLs to run. Your web based applications (VBScript, ASP, etc.) will download faster, your installation package will be smaller, and youll have no problems with different versions of DLLs on your users systems. And, because its both an ActiveX control and COM Object, FTP/X will run in Visual Basic, Visual FoxPro, Inteet Explorer, Delphi and any other environment that supports either ActiveX controls or COM objects.
A common problem with FTP servers is that there is no official standard when it comes to the format of directory listings. The exact format of the data retued by the server may vary depending upon the system type. The FTP/X control solves this programmers headache by automatically parsing the data and making it available to your application as a familiar ADO Recordset object. If the servers format is not suitable for the controls parser, a new DirItemPatte property can be used to specify how the fields are to be parsed. For those who would rather handle the data themselves, the data is also presented in its original format via a string array property.
Both the FTP/X ActiveX control and COM Object use the normal event driven programming model or Fast Notifications. Fast Notifications allow your program to quickly receive events through simple functions, rather than going through the overhead to fire an event. This reduces the amount of time required to handle an event.
FTP/X supports non blocking (asynchronous) mode as well as pseudo blocking and true blocking modes, to meet most any programming requirement. FTP/X is firewall friendly complying with the Firewall Friendly FTP Specification (RFC 1579). From behind most firewalls, your applications will be able to communicate with exteal FTP servers.
Mabrys FTP/X ActiveX control requires no user input to run. The FTP/X control can run completely in the background under program control. This allows your program to take care of file transfers while the user performs other tasks.
BUY Mabry FTPX 2.03.051 15$
TAGS\: low price Mabry FTPX 2.03.051, oem Mabry FTPX 2.03.051, low cost Mabry FTPX 2.03.051
1994/06/22
Mabry FileViewX 1.01.002
Mabry FileViewX 1.01.002
<
Mabry Softwares FileView/X component provides a file list view identical to that seen in Windows Explorer. Using FileView/X, you can easily present a list of files that the user can choose to display as large icons, small icons, names, or complete details. There is a FilePatte property that you can use to select which files are to be displayed. And, for more demanding filtering requirements, an event is fired for each item before it is displayed, enabling you to determine on the fly which items to display. There is a patte matching method to help you filter names, plus many other useful properties and events. FileView/X can be used in conjunction with Mabry Softwares FolderView/X to create applications that have complete or limited explorer capabilities
ActiveX Control (32 bit OCX)
File Name FILEVIEWX.OCX
Compatibility VB 5.0 and 6.0, VC 5.0 and 6.0,
Access 95 and above, VFP 5.0 and 6.0
Built Using Microsoft Visual C++ v6
Control Elements
Properties Events Methods
BrowseFolder
Enabled
FilePatte
IncludeObjectType
MatchPatte
Objects
ShellFolder
SpecialFolder
Version
ViewFolderFlags
ViewMode BrowseFolderChange
IncludeObject
InvokeMenuCommand
KeyDown
KeyPress
KeyUp
ObjectSelect
ObjectSelected
QueryContextMenu
StateChange About
ModifyFolderFlags
Refresh
UpOneLevel
Objects
FLVFolder
FLVObject
FLVObjects
BUY Mabry FileViewX 1.01.002 15$
TAGS\: discount Mabry FileViewX 1.01.002, order Mabry FileViewX 1.01.002, cheap Mabry FileViewX 1.01.002
<
Mabry Softwares FileView/X component provides a file list view identical to that seen in Windows Explorer. Using FileView/X, you can easily present a list of files that the user can choose to display as large icons, small icons, names, or complete details. There is a FilePatte property that you can use to select which files are to be displayed. And, for more demanding filtering requirements, an event is fired for each item before it is displayed, enabling you to determine on the fly which items to display. There is a patte matching method to help you filter names, plus many other useful properties and events. FileView/X can be used in conjunction with Mabry Softwares FolderView/X to create applications that have complete or limited explorer capabilities
ActiveX Control (32 bit OCX)
File Name FILEVIEWX.OCX
Compatibility VB 5.0 and 6.0, VC 5.0 and 6.0,
Access 95 and above, VFP 5.0 and 6.0
Built Using Microsoft Visual C++ v6
Control Elements
Properties Events Methods
BrowseFolder
Enabled
FilePatte
IncludeObjectType
MatchPatte
Objects
ShellFolder
SpecialFolder
Version
ViewFolderFlags
ViewMode BrowseFolderChange
IncludeObject
InvokeMenuCommand
KeyDown
KeyPress
KeyUp
ObjectSelect
ObjectSelected
QueryContextMenu
StateChange About
ModifyFolderFlags
Refresh
UpOneLevel
Objects
FLVFolder
FLVObject
FLVObjects
BUY Mabry FileViewX 1.01.002 15$
TAGS\: discount Mabry FileViewX 1.01.002, order Mabry FileViewX 1.01.002, cheap Mabry FileViewX 1.01.002
1994/06/19
Mabry FolderViewX 1.02.002
Mabry FolderViewX 1.02.002
<
Mabrys FolderView/X component provides a folder list view which is identical to that seen in Windows Explorer. Using FolderView/X you can easily present a list of folders to users. There are a number of properties which can be used to enable special features such as checkboxes, buttons, and lines between folders. FolderView/X can be used in conjunction with Mabrys FileView/X to create applications which have complete or limited explorer capabilities. Other properties are used to enable/disable context menus, the display of share names, and whether icons are displayed or not to name a few. FolderView/X also provides a complete list of events, giving you total control over what happens as the user selects and clicks on folders. And FolderView/X provides a Folders collection containing Folder objects which provide useful information such as PathName, ShareName, and DisplayName.
BUY Mabry FolderViewX 1.02.002 15$
TAGS\: low price Mabry FolderViewX 1.02.002, low price Mabry FolderViewX 1.02.002, low price Mabry FolderViewX 1.02.002
<
Mabrys FolderView/X component provides a folder list view which is identical to that seen in Windows Explorer. Using FolderView/X you can easily present a list of folders to users. There are a number of properties which can be used to enable special features such as checkboxes, buttons, and lines between folders. FolderView/X can be used in conjunction with Mabrys FileView/X to create applications which have complete or limited explorer capabilities. Other properties are used to enable/disable context menus, the display of share names, and whether icons are displayed or not to name a few. FolderView/X also provides a complete list of events, giving you total control over what happens as the user selects and clicks on folders. And FolderView/X provides a Folders collection containing Folder objects which provide useful information such as PathName, ShareName, and DisplayName.
BUY Mabry FolderViewX 1.02.002 15$
TAGS\: low price Mabry FolderViewX 1.02.002, low price Mabry FolderViewX 1.02.002, low price Mabry FolderViewX 1.02.002
1994/06/17
Mabry HTTPX 2.00.046
Mabry HTTPX 2.00.046
<
Mabry Softwares HTTP/X ActiveX control provides easy, high level access to the complete HTTP client protocol. HTTP/X was designed to be as programmer friendly as possible by providing features such as automatic connect and disconnect for single interactions with HTTP/X servers. And, for more advanced uses, HTTP/X also directly supports the more sophisticated pipelined request mechanisms used by todays servers.
The 32 bit HTTP/X component package includes both an ActiveX control (OCX) and a COM object (DLL), which means you can use HTTP/X in nearly any mode programming environment. As a light ActiveX control/COM Object, HTTP/X requires no bulky MFC DLLs to run. Your web based applications (VBScript, ASP, etc.) will download faster, your installation package will be smaller, and youll have no problems with different versions of DLLs on your users systems. And, because its both an ActiveX control and COM Object, HTTP/X will run in Visual Basic, Visual FoxPro, Inteet Explorer, Delphi and any other environment that supports either ActiveX controls or COM objects.
Both the HTTP/X ActiveX control and COM Object use the normal event driven programming model. They also support Fast Notifications that allow your program to quickly receive events through simple functions rather than going through performance degrading overhead to fire and handle an event.
HTTP/X supports non blocking (asynchronous) mode as well as pseudo blocking and true blocking modes, thereby meeting any programming requirements you may have. HTTP/X also provides direct support for use behind firewalls.
Mabrys HTTP/X ActiveX control requires no user input to run. The HTTP/X control can run completely in the background under program control, allowing your program to take care of file transfers while the user performs other tasks.
BUY Mabry HTTPX 2.00.046 15$
TAGS\: low price Mabry HTTPX 2.00.046, cheap Mabry HTTPX 2.00.046, low price Mabry HTTPX 2.00.046
<
Mabry Softwares HTTP/X ActiveX control provides easy, high level access to the complete HTTP client protocol. HTTP/X was designed to be as programmer friendly as possible by providing features such as automatic connect and disconnect for single interactions with HTTP/X servers. And, for more advanced uses, HTTP/X also directly supports the more sophisticated pipelined request mechanisms used by todays servers.
The 32 bit HTTP/X component package includes both an ActiveX control (OCX) and a COM object (DLL), which means you can use HTTP/X in nearly any mode programming environment. As a light ActiveX control/COM Object, HTTP/X requires no bulky MFC DLLs to run. Your web based applications (VBScript, ASP, etc.) will download faster, your installation package will be smaller, and youll have no problems with different versions of DLLs on your users systems. And, because its both an ActiveX control and COM Object, HTTP/X will run in Visual Basic, Visual FoxPro, Inteet Explorer, Delphi and any other environment that supports either ActiveX controls or COM objects.
Both the HTTP/X ActiveX control and COM Object use the normal event driven programming model. They also support Fast Notifications that allow your program to quickly receive events through simple functions rather than going through performance degrading overhead to fire and handle an event.
HTTP/X supports non blocking (asynchronous) mode as well as pseudo blocking and true blocking modes, thereby meeting any programming requirements you may have. HTTP/X also provides direct support for use behind firewalls.
Mabrys HTTP/X ActiveX control requires no user input to run. The HTTP/X control can run completely in the background under program control, allowing your program to take care of file transfers while the user performs other tasks.
BUY Mabry HTTPX 2.00.046 15$
TAGS\: low price Mabry HTTPX 2.00.046, cheap Mabry HTTPX 2.00.046, low price Mabry HTTPX 2.00.046
1994/06/15
Mabry ListX 1.04.012
Mabry ListX 1.04.012
<
List/X+ is an ActiveX control that sets a new standard for functionality and programmability in ActiveX controls. List/X+ provides multiple sortable columns, multi line headers, captions, and list items, unlimited color options, and more. The Mabry List/X+ control is a 32 bit light ActiveX.
List/X+ also provides a unique owner draw capability using high level COM objects that you create with Visual Basic. This feature provides unlimited flexibility, freeing you from the design limitations built into other controls. Using owner draw objects, you can easily define the exact appearance of any column in any row. With List/X+ you can display bitmaps, change fonts and colors on the fly, and use any of the graphical methods available in Visual Basic or the Windows API.
FUNCTIONALITY
Multiple columns
Multi column sorting individual columns can be sorted as desired
Sorted/unsorted property may be modified at runtime
Multi line list items the individual items can be single line or multi line
Multi line column headings each column can have its own multi line heading
Multi line caption captions are not limited to single lines.
Unique and innovative COM callbacks provide the programmer with the ability to paint any or all listbox items on a per column basis
ItemData is a Variant instead of a Long you are no longer limited to numbers only as the data type. The list items can be associated with numeric values, objects, arrays, boolean values, or any other value that can be held in a Variant.
Simple selection, multiselect, and extended multiselect
Selection type is programmable at run time
Column alignment may be modified at run time
User resizable columns
Minimum and maximum widths for user resizable columns
Properties to determine whether the mouse is over the caption, headings, or list parts of the listbox
Powerful object oriented programming model with Column objects and Columns collection
ColumnIndex property provides the column location of the mouse
List items are assignable at design time using property pages
APPEARANCE
3D effects for list, caption, and headings include Raised, Pop, Drop, Shadow, or Inset
Programmable 3D effect colors
Caption is alignable to left, right, or center
Selected and normal foreground and background colors may be specified for the listbox, columns, and individual items
Appearance and colors are programmable at runtime
Column alignment right, left, or center each column can have its own alignment setting
Column headings alignment right, left or center each column heading can have its own alignment
BUY Mabry ListX 1.04.012 15$
TAGS\: oem Mabry ListX 1.04.012, oem Mabry ListX 1.04.012, low price Mabry ListX 1.04.012
<
List/X+ is an ActiveX control that sets a new standard for functionality and programmability in ActiveX controls. List/X+ provides multiple sortable columns, multi line headers, captions, and list items, unlimited color options, and more. The Mabry List/X+ control is a 32 bit light ActiveX.
List/X+ also provides a unique owner draw capability using high level COM objects that you create with Visual Basic. This feature provides unlimited flexibility, freeing you from the design limitations built into other controls. Using owner draw objects, you can easily define the exact appearance of any column in any row. With List/X+ you can display bitmaps, change fonts and colors on the fly, and use any of the graphical methods available in Visual Basic or the Windows API.
FUNCTIONALITY
Multiple columns
Multi column sorting individual columns can be sorted as desired
Sorted/unsorted property may be modified at runtime
Multi line list items the individual items can be single line or multi line
Multi line column headings each column can have its own multi line heading
Multi line caption captions are not limited to single lines.
Unique and innovative COM callbacks provide the programmer with the ability to paint any or all listbox items on a per column basis
ItemData is a Variant instead of a Long you are no longer limited to numbers only as the data type. The list items can be associated with numeric values, objects, arrays, boolean values, or any other value that can be held in a Variant.
Simple selection, multiselect, and extended multiselect
Selection type is programmable at run time
Column alignment may be modified at run time
User resizable columns
Minimum and maximum widths for user resizable columns
Properties to determine whether the mouse is over the caption, headings, or list parts of the listbox
Powerful object oriented programming model with Column objects and Columns collection
ColumnIndex property provides the column location of the mouse
List items are assignable at design time using property pages
APPEARANCE
3D effects for list, caption, and headings include Raised, Pop, Drop, Shadow, or Inset
Programmable 3D effect colors
Caption is alignable to left, right, or center
Selected and normal foreground and background colors may be specified for the listbox, columns, and individual items
Appearance and colors are programmable at runtime
Column alignment right, left, or center each column can have its own alignment setting
Column headings alignment right, left or center each column heading can have its own alignment
BUY Mabry ListX 1.04.012 15$
TAGS\: oem Mabry ListX 1.04.012, oem Mabry ListX 1.04.012, low price Mabry ListX 1.04.012
1994/06/12
Mabry MIMEX 1.01.029
Mabry MIMEX 1.01.029
<
Mabrys Mime/X COM object is more than just a simple email parser. It is capable of handling nested attachments, of any reasonable quantity or deeply nested. It also includes separate Address, Folder, and Header objects. And it has a handy EMailParser object that provides RFC compliant email address parsing which is much better than that provided by popular email programs such as Outlook.
BUY Mabry MIMEX 1.01.029 15$
TAGS\: oem Mabry MIMEX 1.01.029, oem Mabry MIMEX 1.01.029, download Mabry MIMEX 1.01.029
<
Mabrys Mime/X COM object is more than just a simple email parser. It is capable of handling nested attachments, of any reasonable quantity or deeply nested. It also includes separate Address, Folder, and Header objects. And it has a handy EMailParser object that provides RFC compliant email address parsing which is much better than that provided by popular email programs such as Outlook.
BUY Mabry MIMEX 1.01.029 15$
TAGS\: oem Mabry MIMEX 1.01.029, oem Mabry MIMEX 1.01.029, download Mabry MIMEX 1.01.029
1994/06/10
Mabry PingX 1.00.018
Mabry PingX 1.00.018
<
Mabrys Ping/X ActiveX control provides easy to use inteet ping functionality. Using Ping/X you can test for the existance of machines on the net and you can determine what the latency time is for transfer between the machine doing the ping and that being pinged. In addition to the usual ICMP and RAW type pings Mabrys Ping/X supports TCP and UDP pings. These alteatives are provided because some systems, mostly running UNIX, can be set up so that they dont respond to the normal ping requests.
The 32 bit Ping/X comes as both an ActiveX control (OCX) and a COM object (DLL), so you can use it in nearly any mode programming environment. As a light ActiveX control/COM Object, Ping/X doesnt require any bulky MFC DLLs to run. Your web based applications (VBScript, ASP, etc.) will download faster, your installation package will be smaller, and youll have no problems with different versions of DLLs on your users systems. And, because its both an ActiveX control and COM Object, Ping/X will run in Visual Basic, Visual FoxPro, Inteet Explorer, Delphi and any other environment that supports either ActiveX controls or COM objects.
BUY Mabry PingX 1.00.018 15$
TAGS\: buy Mabry PingX 1.00.018, download Mabry PingX 1.00.018, download Mabry PingX 1.00.018
<
Mabrys Ping/X ActiveX control provides easy to use inteet ping functionality. Using Ping/X you can test for the existance of machines on the net and you can determine what the latency time is for transfer between the machine doing the ping and that being pinged. In addition to the usual ICMP and RAW type pings Mabrys Ping/X supports TCP and UDP pings. These alteatives are provided because some systems, mostly running UNIX, can be set up so that they dont respond to the normal ping requests.
The 32 bit Ping/X comes as both an ActiveX control (OCX) and a COM object (DLL), so you can use it in nearly any mode programming environment. As a light ActiveX control/COM Object, Ping/X doesnt require any bulky MFC DLLs to run. Your web based applications (VBScript, ASP, etc.) will download faster, your installation package will be smaller, and youll have no problems with different versions of DLLs on your users systems. And, because its both an ActiveX control and COM Object, Ping/X will run in Visual Basic, Visual FoxPro, Inteet Explorer, Delphi and any other environment that supports either ActiveX controls or COM objects.
BUY Mabry PingX 1.00.018 15$
TAGS\: buy Mabry PingX 1.00.018, download Mabry PingX 1.00.018, download Mabry PingX 1.00.018
1994/06/07
Mabry RASX 1.01.018
Mabry RASX 1.01.018
<
Mabrys RAS/X ActiveX Control and COM Object provide easy access to Dial Up Networking (DUN). Using RAS/X, you can connect to, and disconnect from, the Inteet all under program control and without operator intervention. This makes RAS/X ideal for use in applications that need to automatically make a connection and carry out a task, such as sending e mail, transferring files and data, order processing, a messaging service, to name only a few possibilities.
In addition to providing easy control over the Inteet connection, RAS/X also makes it simple for you to let your users add, edit, modify, and delete phonebook entries. The controls methods and full complement of properties allow you to determine when and what your users are permitted to do.
And, as with all of Mabry Softwares Inteet controls, RAS/X is built using the latest in ActiveX control development tools and technologies. You can use the COM object version of RAS/X, for minimal size requirements and usability in ASP and similar environments. Or, for Visual Basic and other full featured development environments, you may choose to use the OCX version of RAS/X. You will get the same unbeatable functionality and reliability with either form of the RAS/X tool.
BUY Mabry RASX 1.01.018 15$
TAGS\: low price Mabry RASX 1.01.018, low cost Mabry RASX 1.01.018, cheap Mabry RASX 1.01.018
<
Mabrys RAS/X ActiveX Control and COM Object provide easy access to Dial Up Networking (DUN). Using RAS/X, you can connect to, and disconnect from, the Inteet all under program control and without operator intervention. This makes RAS/X ideal for use in applications that need to automatically make a connection and carry out a task, such as sending e mail, transferring files and data, order processing, a messaging service, to name only a few possibilities.
In addition to providing easy control over the Inteet connection, RAS/X also makes it simple for you to let your users add, edit, modify, and delete phonebook entries. The controls methods and full complement of properties allow you to determine when and what your users are permitted to do.
And, as with all of Mabry Softwares Inteet controls, RAS/X is built using the latest in ActiveX control development tools and technologies. You can use the COM object version of RAS/X, for minimal size requirements and usability in ASP and similar environments. Or, for Visual Basic and other full featured development environments, you may choose to use the OCX version of RAS/X. You will get the same unbeatable functionality and reliability with either form of the RAS/X tool.
BUY Mabry RASX 1.01.018 15$
TAGS\: low price Mabry RASX 1.01.018, low cost Mabry RASX 1.01.018, cheap Mabry RASX 1.01.018
1994/06/05
Mabry TREEX 1.01.013
Mabry TREEX 1.01.013
<
Mabry Softwares Tree/X ActiveX is the ultimate tree control it does everything except change colors in the fall. Written using the latest component authoring tools from Microsoft, Tree/X is efficient both in terms of memory and performance, and it has features never before seen in any control.
Tree/X provides the entire range of capabilities that you would expect to see in a state of the art Tree component. Check boxes, radio buttons, different images for open and closed nodes selectable on a per node basis, sub nodes to the right as well as below the parent node, and many other standard Tree features such as sorting.
At Mabry we like to innovate in significant ways with each new component. As a result, Tree/X has a feature not seen in any other component to date it is a full fledged ActiveX container in and of itself. What that means is that you can place any ActiveX component in any node of the tree. You determine whether or not Tree/X allows the user to resize the component at run time Tree/X automatically resizes and rearranges the tree as necessary. Events from contained components are fired through to your program using the same model as used in VB6 for components added at run time no additional leaing curve required!
And, for the pure at heart, you can also assign window handles to Tree/X nodes. If there are windows common controls, for instance, which you would like to use directly in Tree/X, then you simply create one and assign its window handle to Tree/X the rest is handled automatically. WM_COMMAND messages normally sent to the window are passed into the CommandMessage event where you can perform custom processing.
We continue to try to break new ground. In the meantime, try Tree/X and check out its state of the art features.
BUY Mabry TREEX 1.01.013 15$
TAGS\: low cost Mabry TREEX 1.01.013, low price Mabry TREEX 1.01.013, discount Mabry TREEX 1.01.013
<
Mabry Softwares Tree/X ActiveX is the ultimate tree control it does everything except change colors in the fall. Written using the latest component authoring tools from Microsoft, Tree/X is efficient both in terms of memory and performance, and it has features never before seen in any control.
Tree/X provides the entire range of capabilities that you would expect to see in a state of the art Tree component. Check boxes, radio buttons, different images for open and closed nodes selectable on a per node basis, sub nodes to the right as well as below the parent node, and many other standard Tree features such as sorting.
At Mabry we like to innovate in significant ways with each new component. As a result, Tree/X has a feature not seen in any other component to date it is a full fledged ActiveX container in and of itself. What that means is that you can place any ActiveX component in any node of the tree. You determine whether or not Tree/X allows the user to resize the component at run time Tree/X automatically resizes and rearranges the tree as necessary. Events from contained components are fired through to your program using the same model as used in VB6 for components added at run time no additional leaing curve required!
And, for the pure at heart, you can also assign window handles to Tree/X nodes. If there are windows common controls, for instance, which you would like to use directly in Tree/X, then you simply create one and assign its window handle to Tree/X the rest is handled automatically. WM_COMMAND messages normally sent to the window are passed into the CommandMessage event where you can perform custom processing.
We continue to try to break new ground. In the meantime, try Tree/X and check out its state of the art features.
BUY Mabry TREEX 1.01.013 15$
TAGS\: low cost Mabry TREEX 1.01.013, low price Mabry TREEX 1.01.013, discount Mabry TREEX 1.01.013
1994/06/02
Mabry TelnetX 1.00.010
Mabry TelnetX 1.00.010
<
The Mabry Software Telnet/X COM object and ActiveX control implement several client side protocols that can connect to a remote character based service and carry out various tasks. Supported protocols are: Telnet, RLogin (remote login), RExec (remote execution of one command), RSH (remote shell), and SSH (secured encrypted shell).
Telnet/X has implemented inteal automation so you can make it fully scripted. Using the PromptString property, you can make it wait for a command prompt from the remote host. You can then issue a command, wait for the result of that command, examine the result, and then either issue new commands or just disconnect. And its all fully automated with an easy to use interface.
Or, if you need a manual chat with the remote server using terminal emulation, check out our samples and see how to make simple (or even advanced) applications that chat with remote servers at your request. Telnet/X supports automated logins, automated execution of commands, firing events for all needed situations. Of course, you can disable all of those options if you want raw information about the data that is transferred between your computer and a remote host.
Using SSH 1, you can be sure that your connection cannot be tampered with or examined by a 3rd person and you do it just by changing one property value! For you, its fully transparent use SSH or fallback to RSH if the server doesnt support SSH. Make Telnet/X worry about that for you.
And, if speed is a real conce for you, Telnet/X supports the Fast Notification Interface instead of events, if speed is a real conce for you.
Overview
Telnet/X is a component that is able to connect to console type remote servers. These servers usually run on UNIX based computers. Telnet/X can be used not only as a Telnet client, but also as an RSH (remote shell), REXEC (remote exec), RLogin (remote login) and SSH (secure shell).
Using Telnet/Xs friendly component interface, you can configure Telnet/X for different script like programs. You can easily connect to a server, execute specific code, wait for results, and retu. You can also implement different GUI based applications, such as Terminals and Remote administration programs. You can make Telnet/X work silently and execute several different programs at once, waiting for each one to finish. Using very little VB programming knowledge, you can easily interactively connect to a server, execute commands that you specify, receive the results, etc.
With SSH mode, Telnet/X will make a completely secure, private connection that is useful for different types of network sniffers and analyzers. All that is required on the server side is any type of service running the SSH1 protocol.
Tutorial
We will attempt, in a few steps, to show you how easily you can get to know Telnet/X. Just like other Mabry components, Telnet/X contains a main COM object which actually contains all the of the Telnet/X code, plus you have an OCX wrapper that calls the COM object for you. If you want, you can use the COM object directly, but this requires a bit more work to be done on your application.
Add Telnet/X to Your Program
ActiveX: To use the Telnet/X ActiveX control (OCX) with your applications, you need to add a reference to it in your VB program. This is easy just open the VB application you are currently working on, click on the Project menu, then on the Components submenu. On the newly opened dialog, find the Mabry Inteet Telnet/X Control and click on OK.
COM Object: For advanced VB users, we would suggest using the COM object instead of the OCX wrapper. This requires a little more work, but it will result in a faster response from Telnet/X because one less step is used in communication between your application and Telnet/X. To do this, click on Project, then on References and find the Mabry Telnet/X COM Object.
Add Telnet/X to Your Form
ActiveX: Adding Telnet/X to your form is easy. Just drag it from the component toolbox and drop it on your form. Or, click on Telnet/X in the toolbox and make a bounding rectangle for it on the form. However, Telnet/X is a Windowless component it doesnt show any content graphically. It has no window, so no matter what you select for your window, it will always reduce itself to icon size.
COM Object: If you want to use the COM object, you have to switch to the code view. Then, in the General section, add a line like this.
Dim WithEvents TelnetX As TelnetXCom Also, in Form_Load you need to initialize the COM object, and in Form_Unload you have to release it, like this
Private Sub Form_Load()
Set TelnetX New TelnetXCom End Sub
Private Sub Form_Unload(Cancel As Integer)
Set TelnetX Nothing
End Sub
Setting Properties Prior to Establishing a Connection
Before you actually establish a connection with a server, you need to specify a few required properties for Telnet/X. The most basic properties are the Host and Port for the remote server. Host depends on the remote server that you intend to use, and Port varies from service to service. If youre using a Telnet server, use port 23. For RExec use 512, for RLogin use 513, for RSH use 514. Finally, if you want to use secured SSH, use port 22. Note: these are default values. It is possible that your remote server uses different ports for its services, in which case you need to contact the system administrator of that particular server.
Next, you must choose the Protocol type, as described above. The most common is, of course, the Telnet protocol. You cannot mix different Protocol types with different ports (unless the server is configured that way). However, for various tests, you can always use the Telnet protocol with other server types such as POP3 and SMTP. You cannot actually change Telnet/X to make your application POP3 or SMTP compliant but you can manually implement commands for those protocols, which is very handy as a testing tool.
Automating Logon to a Server
All of the protocols that Telnet/X implements require authentication to the remote server, usually by responding to Useame and Password queries sent by the server. You can easily authenticate with the server using the Send method to supply your credentials.
In addition, Telnet/X can automatically authenticate with the Telnet protocol. Set the AutoLogon property to True and put the proper values in the LogonName and LogonPassword properties. Telnet/X will send these values when the server requests them.
All of the protocols except the Telnet protocol require that authentication is set before you can actually send or receive anything else. For this purpose, when you select the Protocol Type to be RSH RExec, RLogin or SSH, the AutoLogon property is automatically set to True and you will not be able to change it back to False.
Automating Commands Executed On The Server
RExec requires it, others support it! What Im talking about here is the LogonCommand property. If you put anything in this property, then Telnet/X will, upon a connect, immediately issue this command. It will then wait for results to complete, send you a response, and disconnect from the server. This is very handy when you need to execute something like a script. You can prepare a batch file on the server, put a few arguments in the LogonCommand script name, and just let Telnet/X do the entire job for you. Nice!
Connecting to the Server
This is the easy part. Once you set up the basic properties, you then call the Connect method with its optional Host and Port parameters. Telnet/X will attempt to connect to the remote server and will fire the Connected event if successful. If Telnet/X is unable to connect, then the LastError property will hold the error that occurred. The state will be set to StateNotConnected.
Communicating with the Server
To send and receive data from the server, you will use the Send and Receive methods. You can actually try to receive data only when the Received event is fired by Telnet/X, informing you that there is data to be read that has arrived from the server. You can use the Send and Receive methods until the connection is closed either if you closed it with the Disconnect method, or the server closed the connection.
Using The Prompt Event To Decide When To Send The
Next
Using the Prompt Event to Decide When to Send the
Next Command
When there is scripting involved in
communication, there is always a question of
when to send the next command if you have more
than one in a sequence.
For instance, you may want to delete a file on a server. You will need to send the ls command (list files), determine what files reside on the server, and delete rm one of them. If you try to send ls and then wait for some time the question is, how many seconds/minutes of inactivity must occur until you can actually send a new command or examine data. Telnet/X has the answer for you.
If you have noticed, when you connect to a Telnet
server, it replies with a prompt like this:
testacc:~>
or
joe:/home/users/joe> The server has identified you as user joe who is currently in the directory /home/users/joe. This is called the prompt string. Telnet/X has a PromptString property where you will store a string identical to the servers. So, when Telnet/X receives this prompt from the remote side, it will fire the Prompt event thus informing you that most probably the server is ready to accept a new command. With tracking of the Prompt event, you can execute several commands exactly at the right time.
The code below is an example of using the Prompt
event:
Private Sub Form_Load()
DidSendCommand 0
here goes code for authentication
put prompt you expect to be received
TelnetX1.PromptString "test@yourprompt:~"
put telnet hostname
TelnetX1.Connect "test.server", 23
End Sub
Private Sub TelnetX1_Prompt()
Dim a As String
a TelnetX1.Receive(vbString)
Select Case DidSendCommand
Case 0
TelnetX1.Send "ls al" vbCrLf
DidSendCommand 1
Case 1
TelnetX1.Send "exit" vbCrLf
DidSendCommand 2
End Select
End Sub The above code will first execute ls al which
retrieves a directory listing. Then it will send
a command to logout from the server.
Using a Secured Connection
In SSH mode, with Telnet/Xs Protocol property set to SSH1, Telnet/X can establish a secure connection with a remote server running an SSH1 service. You can optionally use the Encryption property to specify what encryption is used. After the connection is established, your data will flow transparently for you whatever you send (in plain text) will be received by the server just as you sent it. But, during transmission, the data will be encrypted and anyone who is spying on your connection will not be able to see what data has been sent, including your password.
One thing to check when a connection is established, the SSHCheckServerKey event will fire and the ServerKey variable will hold the server key. This is a servers public key which should never change. The SSH protocol is based on trust once you trust that the remote side has a valid public key, you should verify that it is the same key on each new connection. So, store this value the first time you connect, and check it on each new connect. If the key has changed, there is a possibility that someone is spying on your connection.
Choosing the Terminal Type
Usually, most console type servers need specific terminal implementation in order that the keyboard and screen are mapped properly. The most common terminal types are ANSI and VT100 but there are many more types. Using terminal types like this, you are able to, for example, clear the screen on a remote console, delete one line, use backspace, delete, etc capabilities which are not enabled if the remote terminal is only in the so called teletype mode.
Telnet/X doesnt implement any specific terminal, but allows you to define any type you need. Telnet/X has a TerminalType property that can hold 3 values None, Manual and Automatic. If you set it to None, then Telnet/X responds to special commands (such as clear screen, for instance) with the reply unable to perform operation of course in the protocols language. This is common behavior. It will happen every time you use the Telnet protocol, because, on primary negotiation, the server always sends a few options. Setting the Telnet/X TerminalType to None will reply with deny on all such options.
If you set the property to Automatic, Telnet/X will implement the few terminal options of which it is capable (without knowing your actual needs). These options include the BS character (backspace), line speed (regular modem connection dont worry if youre faster than that), BELL character, window size (80x25) etc.
If you set it to Manual, Telnet/X will fire the SpecialCode event each time there is some special code sent by the server. Special codes vary depending on the protocol that is used with Telnet/X. In general, these are ASCII codes that are not printable (once more only in general). Your job is to implement those codes as you wish which means that you will implement some sort of Terminal emulation by yourself. Please note that you must know the protocol used to be able to correctly reply to such special codes.
Using Proxy Firewalls
In case you dont have direct access to the Inteet and you are forced to use a proxy, Telnet/X allows you to use several predefined proxies or to implement your own (we leave this up to you). The most common proxies are TelnetProxy, Socks4, Socks5, HTTPProxy, and Pipe.
The TelnetProxy is the one most commonly used for Telnet protocols. When Telnet/X connects to such a proxy, the control sends the Host and Port properties. The proxy then connects to the destination server and passes all traffic between you and the server.
Socks4 and Socks5 are more general. Usually they are listening on port 1080. When Telnet/X connects to Socks4, it specifies some special codes and commands that the server interprets and uses to connect you to your destination server. It then starts relaying data.
The HTTPProxy is the most widespread. When Telnet/X connects to such a proxy, it sends the CONNECT keyword and the proxy tries to connect to the remote side for you. If everything succeeds, you can talk to the remote side. Many HTTP servers also support this you should check one running on your local network.
The PIPE relay does nothing except it connects to that proxy and expects a real telnet server. The purpose of PIPE is that you can easily spy on your own connection and see what is actually transferred for debugging purposes. Download Mabry Softwares Firewall/X and test its PIPE SPY sample to see how this actually works.
Disconnecting From the Server
When the time comes to disconnect from a remote server, you have two options to disconnect in the regular manner, or to disconnect with brute force.
The regular way would be to send the exit or logoff command to the remote server and wait for the server to close the connection. If you do it this way, you will be sure that there are no processes left running on the server and that leaving the command prompt was clean.
If, for whatever reason, you cannot disconnect in a regular manner, then you can use the Disconnect method that will just close the connection. Please note that sometimes the server does not know that you have disconnected and will keep you marked as logged on for quite some time afterwards.
Using and Implementing the Fast Notification Interface
The Fast Notification Interface is a replacement for regular events. Its purpose is to avoid using the regular COM architecture and firing of events. The interface implements a few callback functions that you will have in your code, and Telnet/X will call them just as it would fire an event. As a result, you will get a faster application.
Interface ITelnetXNotify (ITelnetXComNotify for the COM object) is the name of the interface that knows the structure and declaration of the callback functions. If you want to use fast notifications, you need to provide and implement ALL of the methods that are declared in the above interfaces. If you dont want to implement them leave the bodies empty but surely declare them.
So, whats the deal? Instead of having, e.g., the PromptString declared like this in your VB application,
Private Sub TelnetX1_Received(ByVal BytesCount As Long) Dim a As String
a TelnetX1.Receive(vbString)
If DidSendCommand 1 Then
Text1 Text1 + a
End If
End Sub
you will have something like this
Private Sub ITelnetXNotify_Received(ByVal Object
As MabryTelnetXOCXLibCtl.ITelnetX, ByVal
BytesCount As Long)
Dim a As String
a TelnetX1.Receive(vbString)
If DidSendCommand 1 Then
Text1 Text1 + a
End If
End Sub
This is what you need to do, step by step.
First, copy/paste this line into your code:
Implements ITelnetXNotify
If youre using the COM object instead, do this:
Dim TelnetX1 as TelnetXCom
Implements ITelnetXComNotify
Note that we dont use the WithEvents keyword
anymore because we dont use events.
Immediately after adding this line, you will see that a new object is shown in the object list ITelnetXNotify (ITelnetXComNotify). If you look closely, you will see that it has several methods very similar to actual events. You need to click on all of them at least so that their declaration is shown in the code view. If you dont do this, when you run your program you will get an error saying that not all methods are implemented. Be careful here.
There is only one more thing to do you need to let Telnet/X know that you will use the fast notification interface instead of events. You will do it like this:
TelnetX1.NotificationObject Me You can also create new class and implement these notification methods in it, in which case you would put TelnetX1.NotificationObject class1,
BUY Mabry TelnetX 1.00.010 15$
TAGS\: discount Mabry TelnetX 1.00.010, low price Mabry TelnetX 1.00.010, oem Mabry TelnetX 1.00.010
<
The Mabry Software Telnet/X COM object and ActiveX control implement several client side protocols that can connect to a remote character based service and carry out various tasks. Supported protocols are: Telnet, RLogin (remote login), RExec (remote execution of one command), RSH (remote shell), and SSH (secured encrypted shell).
Telnet/X has implemented inteal automation so you can make it fully scripted. Using the PromptString property, you can make it wait for a command prompt from the remote host. You can then issue a command, wait for the result of that command, examine the result, and then either issue new commands or just disconnect. And its all fully automated with an easy to use interface.
Or, if you need a manual chat with the remote server using terminal emulation, check out our samples and see how to make simple (or even advanced) applications that chat with remote servers at your request. Telnet/X supports automated logins, automated execution of commands, firing events for all needed situations. Of course, you can disable all of those options if you want raw information about the data that is transferred between your computer and a remote host.
Using SSH 1, you can be sure that your connection cannot be tampered with or examined by a 3rd person and you do it just by changing one property value! For you, its fully transparent use SSH or fallback to RSH if the server doesnt support SSH. Make Telnet/X worry about that for you.
And, if speed is a real conce for you, Telnet/X supports the Fast Notification Interface instead of events, if speed is a real conce for you.
Overview
Telnet/X is a component that is able to connect to console type remote servers. These servers usually run on UNIX based computers. Telnet/X can be used not only as a Telnet client, but also as an RSH (remote shell), REXEC (remote exec), RLogin (remote login) and SSH (secure shell).
Using Telnet/Xs friendly component interface, you can configure Telnet/X for different script like programs. You can easily connect to a server, execute specific code, wait for results, and retu. You can also implement different GUI based applications, such as Terminals and Remote administration programs. You can make Telnet/X work silently and execute several different programs at once, waiting for each one to finish. Using very little VB programming knowledge, you can easily interactively connect to a server, execute commands that you specify, receive the results, etc.
With SSH mode, Telnet/X will make a completely secure, private connection that is useful for different types of network sniffers and analyzers. All that is required on the server side is any type of service running the SSH1 protocol.
Tutorial
We will attempt, in a few steps, to show you how easily you can get to know Telnet/X. Just like other Mabry components, Telnet/X contains a main COM object which actually contains all the of the Telnet/X code, plus you have an OCX wrapper that calls the COM object for you. If you want, you can use the COM object directly, but this requires a bit more work to be done on your application.
Add Telnet/X to Your Program
ActiveX: To use the Telnet/X ActiveX control (OCX) with your applications, you need to add a reference to it in your VB program. This is easy just open the VB application you are currently working on, click on the Project menu, then on the Components submenu. On the newly opened dialog, find the Mabry Inteet Telnet/X Control and click on OK.
COM Object: For advanced VB users, we would suggest using the COM object instead of the OCX wrapper. This requires a little more work, but it will result in a faster response from Telnet/X because one less step is used in communication between your application and Telnet/X. To do this, click on Project, then on References and find the Mabry Telnet/X COM Object.
Add Telnet/X to Your Form
ActiveX: Adding Telnet/X to your form is easy. Just drag it from the component toolbox and drop it on your form. Or, click on Telnet/X in the toolbox and make a bounding rectangle for it on the form. However, Telnet/X is a Windowless component it doesnt show any content graphically. It has no window, so no matter what you select for your window, it will always reduce itself to icon size.
COM Object: If you want to use the COM object, you have to switch to the code view. Then, in the General section, add a line like this.
Dim WithEvents TelnetX As TelnetXCom Also, in Form_Load you need to initialize the COM object, and in Form_Unload you have to release it, like this
Private Sub Form_Load()
Set TelnetX New TelnetXCom End Sub
Private Sub Form_Unload(Cancel As Integer)
Set TelnetX Nothing
End Sub
Setting Properties Prior to Establishing a Connection
Before you actually establish a connection with a server, you need to specify a few required properties for Telnet/X. The most basic properties are the Host and Port for the remote server. Host depends on the remote server that you intend to use, and Port varies from service to service. If youre using a Telnet server, use port 23. For RExec use 512, for RLogin use 513, for RSH use 514. Finally, if you want to use secured SSH, use port 22. Note: these are default values. It is possible that your remote server uses different ports for its services, in which case you need to contact the system administrator of that particular server.
Next, you must choose the Protocol type, as described above. The most common is, of course, the Telnet protocol. You cannot mix different Protocol types with different ports (unless the server is configured that way). However, for various tests, you can always use the Telnet protocol with other server types such as POP3 and SMTP. You cannot actually change Telnet/X to make your application POP3 or SMTP compliant but you can manually implement commands for those protocols, which is very handy as a testing tool.
Automating Logon to a Server
All of the protocols that Telnet/X implements require authentication to the remote server, usually by responding to Useame and Password queries sent by the server. You can easily authenticate with the server using the Send method to supply your credentials.
In addition, Telnet/X can automatically authenticate with the Telnet protocol. Set the AutoLogon property to True and put the proper values in the LogonName and LogonPassword properties. Telnet/X will send these values when the server requests them.
All of the protocols except the Telnet protocol require that authentication is set before you can actually send or receive anything else. For this purpose, when you select the Protocol Type to be RSH RExec, RLogin or SSH, the AutoLogon property is automatically set to True and you will not be able to change it back to False.
Automating Commands Executed On The Server
RExec requires it, others support it! What Im talking about here is the LogonCommand property. If you put anything in this property, then Telnet/X will, upon a connect, immediately issue this command. It will then wait for results to complete, send you a response, and disconnect from the server. This is very handy when you need to execute something like a script. You can prepare a batch file on the server, put a few arguments in the LogonCommand script name, and just let Telnet/X do the entire job for you. Nice!
Connecting to the Server
This is the easy part. Once you set up the basic properties, you then call the Connect method with its optional Host and Port parameters. Telnet/X will attempt to connect to the remote server and will fire the Connected event if successful. If Telnet/X is unable to connect, then the LastError property will hold the error that occurred. The state will be set to StateNotConnected.
Communicating with the Server
To send and receive data from the server, you will use the Send and Receive methods. You can actually try to receive data only when the Received event is fired by Telnet/X, informing you that there is data to be read that has arrived from the server. You can use the Send and Receive methods until the connection is closed either if you closed it with the Disconnect method, or the server closed the connection.
Using The Prompt Event To Decide When To Send The
Next
Using the Prompt Event to Decide When to Send the
Next Command
When there is scripting involved in
communication, there is always a question of
when to send the next command if you have more
than one in a sequence.
For instance, you may want to delete a file on a server. You will need to send the ls command (list files), determine what files reside on the server, and delete rm one of them. If you try to send ls and then wait for some time the question is, how many seconds/minutes of inactivity must occur until you can actually send a new command or examine data. Telnet/X has the answer for you.
If you have noticed, when you connect to a Telnet
server, it replies with a prompt like this:
testacc:~>
or
joe:/home/users/joe> The server has identified you as user joe who is currently in the directory /home/users/joe. This is called the prompt string. Telnet/X has a PromptString property where you will store a string identical to the servers. So, when Telnet/X receives this prompt from the remote side, it will fire the Prompt event thus informing you that most probably the server is ready to accept a new command. With tracking of the Prompt event, you can execute several commands exactly at the right time.
The code below is an example of using the Prompt
event:
Private Sub Form_Load()
DidSendCommand 0
here goes code for authentication
put prompt you expect to be received
TelnetX1.PromptString "test@yourprompt:~"
put telnet hostname
TelnetX1.Connect "test.server", 23
End Sub
Private Sub TelnetX1_Prompt()
Dim a As String
a TelnetX1.Receive(vbString)
Select Case DidSendCommand
Case 0
TelnetX1.Send "ls al" vbCrLf
DidSendCommand 1
Case 1
TelnetX1.Send "exit" vbCrLf
DidSendCommand 2
End Select
End Sub The above code will first execute ls al which
retrieves a directory listing. Then it will send
a command to logout from the server.
Using a Secured Connection
In SSH mode, with Telnet/Xs Protocol property set to SSH1, Telnet/X can establish a secure connection with a remote server running an SSH1 service. You can optionally use the Encryption property to specify what encryption is used. After the connection is established, your data will flow transparently for you whatever you send (in plain text) will be received by the server just as you sent it. But, during transmission, the data will be encrypted and anyone who is spying on your connection will not be able to see what data has been sent, including your password.
One thing to check when a connection is established, the SSHCheckServerKey event will fire and the ServerKey variable will hold the server key. This is a servers public key which should never change. The SSH protocol is based on trust once you trust that the remote side has a valid public key, you should verify that it is the same key on each new connection. So, store this value the first time you connect, and check it on each new connect. If the key has changed, there is a possibility that someone is spying on your connection.
Choosing the Terminal Type
Usually, most console type servers need specific terminal implementation in order that the keyboard and screen are mapped properly. The most common terminal types are ANSI and VT100 but there are many more types. Using terminal types like this, you are able to, for example, clear the screen on a remote console, delete one line, use backspace, delete, etc capabilities which are not enabled if the remote terminal is only in the so called teletype mode.
Telnet/X doesnt implement any specific terminal, but allows you to define any type you need. Telnet/X has a TerminalType property that can hold 3 values None, Manual and Automatic. If you set it to None, then Telnet/X responds to special commands (such as clear screen, for instance) with the reply unable to perform operation of course in the protocols language. This is common behavior. It will happen every time you use the Telnet protocol, because, on primary negotiation, the server always sends a few options. Setting the Telnet/X TerminalType to None will reply with deny on all such options.
If you set the property to Automatic, Telnet/X will implement the few terminal options of which it is capable (without knowing your actual needs). These options include the BS character (backspace), line speed (regular modem connection dont worry if youre faster than that), BELL character, window size (80x25) etc.
If you set it to Manual, Telnet/X will fire the SpecialCode event each time there is some special code sent by the server. Special codes vary depending on the protocol that is used with Telnet/X. In general, these are ASCII codes that are not printable (once more only in general). Your job is to implement those codes as you wish which means that you will implement some sort of Terminal emulation by yourself. Please note that you must know the protocol used to be able to correctly reply to such special codes.
Using Proxy Firewalls
In case you dont have direct access to the Inteet and you are forced to use a proxy, Telnet/X allows you to use several predefined proxies or to implement your own (we leave this up to you). The most common proxies are TelnetProxy, Socks4, Socks5, HTTPProxy, and Pipe.
The TelnetProxy is the one most commonly used for Telnet protocols. When Telnet/X connects to such a proxy, the control sends the Host and Port properties. The proxy then connects to the destination server and passes all traffic between you and the server.
Socks4 and Socks5 are more general. Usually they are listening on port 1080. When Telnet/X connects to Socks4, it specifies some special codes and commands that the server interprets and uses to connect you to your destination server. It then starts relaying data.
The HTTPProxy is the most widespread. When Telnet/X connects to such a proxy, it sends the CONNECT keyword and the proxy tries to connect to the remote side for you. If everything succeeds, you can talk to the remote side. Many HTTP servers also support this you should check one running on your local network.
The PIPE relay does nothing except it connects to that proxy and expects a real telnet server. The purpose of PIPE is that you can easily spy on your own connection and see what is actually transferred for debugging purposes. Download Mabry Softwares Firewall/X and test its PIPE SPY sample to see how this actually works.
Disconnecting From the Server
When the time comes to disconnect from a remote server, you have two options to disconnect in the regular manner, or to disconnect with brute force.
The regular way would be to send the exit or logoff command to the remote server and wait for the server to close the connection. If you do it this way, you will be sure that there are no processes left running on the server and that leaving the command prompt was clean.
If, for whatever reason, you cannot disconnect in a regular manner, then you can use the Disconnect method that will just close the connection. Please note that sometimes the server does not know that you have disconnected and will keep you marked as logged on for quite some time afterwards.
Using and Implementing the Fast Notification Interface
The Fast Notification Interface is a replacement for regular events. Its purpose is to avoid using the regular COM architecture and firing of events. The interface implements a few callback functions that you will have in your code, and Telnet/X will call them just as it would fire an event. As a result, you will get a faster application.
Interface ITelnetXNotify (ITelnetXComNotify for the COM object) is the name of the interface that knows the structure and declaration of the callback functions. If you want to use fast notifications, you need to provide and implement ALL of the methods that are declared in the above interfaces. If you dont want to implement them leave the bodies empty but surely declare them.
So, whats the deal? Instead of having, e.g., the PromptString declared like this in your VB application,
Private Sub TelnetX1_Received(ByVal BytesCount As Long) Dim a As String
a TelnetX1.Receive(vbString)
If DidSendCommand 1 Then
Text1 Text1 + a
End If
End Sub
you will have something like this
Private Sub ITelnetXNotify_Received(ByVal Object
As MabryTelnetXOCXLibCtl.ITelnetX, ByVal
BytesCount As Long)
Dim a As String
a TelnetX1.Receive(vbString)
If DidSendCommand 1 Then
Text1 Text1 + a
End If
End Sub
This is what you need to do, step by step.
First, copy/paste this line into your code:
Implements ITelnetXNotify
If youre using the COM object instead, do this:
Dim TelnetX1 as TelnetXCom
Implements ITelnetXComNotify
Note that we dont use the WithEvents keyword
anymore because we dont use events.
Immediately after adding this line, you will see that a new object is shown in the object list ITelnetXNotify (ITelnetXComNotify). If you look closely, you will see that it has several methods very similar to actual events. You need to click on all of them at least so that their declaration is shown in the code view. If you dont do this, when you run your program you will get an error saying that not all methods are implemented. Be careful here.
There is only one more thing to do you need to let Telnet/X know that you will use the fast notification interface instead of events. You will do it like this:
TelnetX1.NotificationObject Me You can also create new class and implement these notification methods in it, in which case you would put TelnetX1.NotificationObject class1,
BUY Mabry TelnetX 1.00.010 15$
TAGS\: discount Mabry TelnetX 1.00.010, low price Mabry TelnetX 1.00.010, oem Mabry TelnetX 1.00.010
Subscribe to:
Posts (Atom)