win32

Win32 APIDOS is a free and useful Win API utility.

TracePlus/Win32 shows you the interaction between your Win32
application and multiple Win32 APIs. Supported
APIs that are displayed in realtime include ODBC, OLE, COM, TAPI,
WININET, registry, DB-Library, and more. Integrated SQL capture window
displays SQL statements generated by the supported database APIs.
Status window displays DLL version information, OutputDebugString() calls, and more.

X-Win32 is a powerful PC X Server that quickly, easily and securely connects your Windows PCs to UNIX and Linux servers. Bringing common ground to the mixed OS environment, X-Win32 provides PC users seamless access to their Solaris, AIX, HP-UX, Redhat, Suse, Mandrake and other UNIX and Linux systems. Key features include OpenGL support for interactive 3D graphic applications, Multiple XDMCP Sessions allowing you to connect to multiple UNIX and Linux servers simultaneously, and LBX Support for increased performance of X applications over a slower connection.

Today s users demand a remote access tool that is easy to configure and operate, acts quickly with powerful performance and continually offers innovative features. X-Win32 provides all of the above in addition to unlimited free technical support and one year of free upgrades, at an affordable price.

MegaPipe Win32 DLL is a reliable and powerful library for handling serial communication, modem operation and file-transfer (XModem Checksum, XModem CRC, XModem 1K, YModem, YModem-G, ZModem and Kermit), multiple ports/lines (up to 8) are supported.

It can be used in a lot of environments like VC++, VB, VB.Net, C#.Net, Access, Delphi and Borland C++.

TracePlus Win description
It shows you the interaction between your Win32 application and multiple Win32 APIs TracePlus/Win32 will provide information on application usage of the Win32, ODBC, RAS, MAPI, TAPI and Win32 Internet APIs.

TracePlus Win32 traces 32 categories of API functions, comprising nearly 1350 API calls.

The API categories are:
· Access Control
· Profile Functions
· Application related (Kernel)
· Registry
· Common Controls
· Remote Access (RAS)
· Date and Time
· Resource Management
· DDEML
· Serial Communications
· Windows NT Event Log
· Service Manager
· File I/O
· Shell
· File System
· Simple MAPI
· Memory Management
· System Related
· Multimedia APIs
· TAPI
· Network (WNetxxx() functions)
· Threads
· ODBC (Full ODBC 3.x support)
· Timers
· OLE (Base)
· Tokens
· OLE (COM)
· Win32 Internet API (Expanded support)
· Pipes and Mailslots
· Windows GUI (Expanded support)
· Processes

Using its unique visual realtime display of Win32 activity, you can spot timing-sensitive API issues, view error codes for failed Win32 functions, reverse engineer other Win32 applications without source code, locate DLLs loaded by an application, and discover what registry keys are used by an application.

TracePlus/Win32 has proprietary technology called Cyclone Plus which detects and hooks API functions both inside and outside of the process being spied upon. Thus Java applications, Active X controls, out of process OLE servers, and child processes will be detected and traced automatically.

TracePlus can prevent an application from detecting that it is being run in a debugger. Some well known applications have code in them that prevent applications such as TracePlus from revealing the way that they operate. Such applications abort immediately after they are launched, or disable certain features of the application when a debugger is detected.

TracePlus is aware of several different methods by which applications can detect whether they are being debugged. Via these same techniques, TracePlus indicates to the application that in fact it is not being debugged. Such applications will then run normally inside of TracePlus.

Here are some key features of "TracePlus Win":

· Supported API functions that fail are indicated in the Diagnostics View along with the Win32 error code describing the failure
· Displays API calls originating from ActiveX controls and COM objects instanced by an application
· Displays API and ODBC calls originating from a child process
· Displays ODBC calls originating from the Microsoft Jet Database Engine, and Active Data Objects (ADO)
· Works with most commercial Win32 applications (release versions) with no modifications to the target application
· Compatible with Microsoft Terminal Server and Remote Desktop (Windows NT 4.x, Windows 2000, Windows 2003 Server)
· Supports Win32 .EXE files from all languages and compilers (including Visual C++, Visual Basic, Visual C#, Microsoft Access, MASM, Borland Delphi and C++ Builder, Sybase PowerBuilder)
· Works with most Win32 Services on platforms that support services (Windows NT 4.x, Windows 2000, Windows XP, Windows 2003 Server)
· The Registry View displays accesses made to the Windows registry by one or more processes. Using a unique algorithm, TracePlus determines the full key name as well as displaying the value of the key.
· Registry accesses that fail are indicated in the Registry View along with the Win32 error code describing the failure
· User-definable filters limit what is displayed in the Registry View to the types of Registry accesses that interest you
· The text of SQL statements transmitted via the ODBC API is displayed in the SQL View
· Contents of result columns displayed in the SQL View along with the SQL statement
· Displays the contents of all variables bound to parameters in a SQL Statement. This information is displayed inside the ODBC functions SQLExecute() or SQLExecDirect() in the Diagnostics View.
· Execution time is profiled in the SQL View for each SQL statement
· SQL statements that fail are indicated in the SQL View along with full ODBC error information describing the failure
· File opening, closing, creation, deletion, copying, moving, and renaming by an application are detailed in the File I/O View
· File reads, writes, locks, and unlocks are detailed in the File I/O View
· Manipulation of mapped files (open, create, close, read, write, flush) are detailed in the File I/O View
· The referenced filename is displayed for every file open or create appearing in the File I/O View
· Mapped Views are supported in the File I/O View
· User-definable filters limit what is displayed in the File I/O View to the types of File I/O that interest you
· The status of COM object creation via CoCreateInstance() and CoCreateInstanceEx() is detailed in Status View
· DLL loading and unloading is profiled in the Status View. DLL load events contain version information (if available) for the module being loaded.
· The text of messages sent via OutputDebugString() appears in the Status View
· User definable filter profiles enable separate API configurations for different capture sessions


Requirements:

· Compatible with the WOW64 subsystem on Windows XP x64, Windows 2003 Server x64, and Windows Vista x64
· Pentium 3 or AMD Athlon 1 GHZ or greater
· 192 MB RAM
· 10 MB disk space

Limitations:

· Function details in the Diagnostics View will be fully visible for the first 20 items.
· Certain statistics in all views will be fully visible for the first 20 items

TracePlus/Win32 will provide information on application usage of the Win32, ODBC, RAS, MAPI, TAPI and Win32 Internet APIs.

TracePlus Win32 traces 32 categories of API functions, comprising nearly 1350 API calls.

The API categories are:
· Access Control
· Profile Functions
· Application related (Kernel)
· Registry
· Common Controls
· Remote Access (RAS)
· Date and Time
· Resource Management
· DDEML
· Serial Communications
· Windows NT Event Log
· Service Manager
· File I/O
· Shell
· File System
· Simple MAPI
· Memory Management
· System Related
· Multimedia APIs
· TAPI
· Network (WNetxxx() functions)
· Threads
· ODBC (Full ODBC 3.x support)
· Timers
· OLE (Base)
· Tokens
· OLE (COM)
· Win32 Internet API (Expanded support)
· Pipes and Mailslots
· Windows GUI (Expanded support)
· Processes

Using its unique visual realtime display of Win32 activity, you can spot timing-sensitive API issues, view error codes for failed Win32 functions, reverse engineer other Win32 applications without source code, locate DLLs loaded by an application, and discover what registry keys are used by an application.

TracePlus/Win32 has proprietary technology called Cyclone Plus which detects and hooks API functions both inside and outside of the process being spied upon. Thus Java applications, Active X controls, out of process OLE servers, and child processes will be detected and traced automatically.

TracePlus can prevent an application from detecting that it is being run in a debugger. Some well known applications have code in them that prevent applications such as TracePlus from revealing the way that they operate. Such applications abort immediately after they are launched, or disable certain features of the application when a debugger is detected.

TracePlus is aware of several different methods by which applications can detect whether they are being debugged. Via these same techniques, TracePlus indicates to the application that in fact it is not being debugged. Such applications will then run normally inside of TracePlus.

Here are some key features of "TracePlus Win":

· Supported API functions that fail are indicated in the Diagnostics View along with the Win32 error code describing the failure
· Displays API calls originating from ActiveX controls and COM objects instanced by an application
· Displays API and ODBC calls originating from a child process
· Displays ODBC calls originating from the Microsoft Jet Database Engine, and Active Data Objects (ADO)
· Works with most commercial Win32 applications (release versions) with no modifications to the target application
· Compatible with Microsoft Terminal Server and Remote Desktop (Windows NT 4.x, Windows 2000, Windows 2003 Server)
· Supports Win32 .EXE files from all languages and compilers (including Visual C++, Visual Basic, Visual C#, Microsoft Access, MASM, Borland Delphi and C++ Builder, Sybase PowerBuilder)
· Works with most Win32 Services on platforms that support services (Windows NT 4.x, Windows 2000, Windows XP, Windows 2003 Server)
· The Registry View displays accesses made to the Windows registry by one or more processes. Using a unique algorithm, TracePlus determines the full key name as well as displaying the value of the key.
· Registry accesses that fail are indicated in the Registry View along with the Win32 error code describing the failure
· User-definable filters limit what is displayed in the Registry View to the types of Registry accesses that interest you
· The text of SQL statements transmitted via the ODBC API is displayed in the SQL View
· Contents of result columns displayed in the SQL View along with the SQL statement
· Displays the contents of all variables bound to parameters in a SQL Statement. This information is displayed inside the ODBC functions SQLExecute() or SQLExecDirect() in the Diagnostics View.
· Execution time is profiled in the SQL View for each SQL statement
· SQL statements that fail are indicated in the SQL View along with full ODBC error information describing the failure
· File opening, closing, creation, deletion, copying, moving, and renaming by an application are detailed in the File I/O View
· File reads, writes, locks, and unlocks are detailed in the File I/O View
· Manipulation of mapped files (open, create, close, read, write, flush) are detailed in the File I/O View
· The referenced filename is displayed for every file open or create appearing in the File I/O View
· Mapped Views are supported in the File I/O View
· User-definable filters limit what is displayed in the File I/O View to the types of File I/O that interest you
· The status of COM object creation via CoCreateInstance() and CoCreateInstanceEx() is detailed in Status View
· DLL loading and unloading is profiled in the Status View. DLL load events contain version information (if available) for the module being loaded.
· The text of messages sent via OutputDebugString() appears in the Status View
· User definable filter profiles enable separate API configurations for different capture sessions

X-Win32 will allow you to easily and securely connect your Windows computer to any Solaris, HP/UX, AIX or Linux system.

Whether you are designing an advanced IC, analyzing a string of human DNA, accessing an Oracle database, or configuring your enterprise networking server from home, X-Win32 allows you to quickly, easily and securely connect your Windows computer to any Solaris, HP/UX, AIX or Linux system.

While it is a client/server system, the X Window System has important differences between other client/server software such as mail or HTTP. A first-time user can be confused because X applications (such as xterm and mailtool) are clients, while an X display (such as X-Win32) is a server.

This means that when you start X-Win32 you have just started an X server and are now waiting for clients to connect to you. But how do you start a client on a remote machine?

Window management is the system whereby the user moves, resizes, stacks, and iconifies (minimizes) windows. It also displays titles on windows, and can let the user switch between several virtual screens. On Unix systems running X, windows are managed by a special X application known as a window manager.

Common ones are mwm (Motif), olwm (OpenLook), and dtwm (CDE). X-Win32 gives the user the option of using the Windows 95 window manager (Multiple Window mode) or an X window manager running on the Unix system (Single Window mode ). It is recommended that you use Multiple Window mode when using rsh or rexec, and Single Window mode when using XDMCP.

QuickUPX-Win32 Shell is a free file compression tool that will come in handy.