humm.... QuickWin Programming Compiling a DOS program with the /Mq option makes it a QuickWin program with a limited Windows interface. In Windows terminology, the style of a QuickWin program's interface is known as Multiple Document Interface (MDI), wherein the user sees a work area containing one or more child windows. Each of these child windows can be individually reduced to icons (minimized) or made to fit the entire work area (maximized). The work area normally contains one window with the title Stdin/Stdout/Stderr, which displays output meant for the predefined C streams stdout and stderr, and enables you to read input that you normally read from stdin. The best way to see how a QuickWin program works is to look at a simple example.

1

//--------------------------------------------------------------- // File: hello.c // // A QuickWin program that displays "Hello, World!" in // the Stdout window. // // Compile and link with the /Mq option. //---------------------------------------------------------------- #include <stdio.h> void main(void) { printf("Hello, World!\n"); } A simple QuickWin program such as the one in Listing 1 provides the following properties: - Includes a minimal Windows interface with a standard menu bar and a console window with the title Stdin/Stdout/Stderr. - Allows copying of text between the Windows clipboard and the application's window. -Takes advantage of Windows memory management capabilities, thus overriding the 640K memory limit under DOS. Enhanced QuickWin Programs The term enhanced QuickWin program refers to QuickWin programs that call one of the 14 functions described in this file to impart several additional user interface elements to the application. Of course, once you use the functions from this file in your code, your program becomes dependent on the QuickWin library and cannot be compiled and run under DOS. An enhanced QuickWin application can: Have multiple child windows. Include a specific message in the About box. Control window sizing and placement. Control the size of text buffer associated with a window. Make a specific window active (the active window gets the keypress). However, even with these enhancements a QuickWin Program is no substitute for a true Window application because a QuickWin program cannot display any graphics in a window nor can it detect and respond to mouse clicks in a window. Also, you cannot call any Microsoft Windows functions in a QuickWin application. Table 1. Alphabetic listing of QuickWin functions. Function Description _fwopen Opens a new QuickWin window as a stream. _wabout Sets the string that appears in the About dialog box of the QuickWin application. _wclose Closes the file handle associated with a QuickWin window. _wgetexit Returns an integer constant that indicates what happens to the QuickWin window if the exit is called anywhere in a program. _wgetfocus Returns the handle of the QuickWin window that has the focus. _wgetscreenbuf Returns the size of the text buffer associated with a QuickWin window. _wgetsize Provides information about the position and the size of a window. _wmenuclick Simulates selection of certain menu items by the user. _wopen Opens a QuickWin window. _wsetexit Sets the exit behavior of a QuickWin window. _wsetfocus Makes a specified window the active window. _wsetscreenbuf Sets the size of the text buffer associated with an open QuickWin window. _wsetsize Sets the position and size of a specified QuickWin window. _wyield Yields control to Windows to allow other Windows applications to run. Basic QuickWin Tasks Table 1 lists the console and port I/O functions alphabetically and gives you a quick overview of these functions. Table 2 organizes these functions by the tasks they perform. Some of these tasks are illustrated by a short sample program in the following sections. For more information about a function, consult the reference entry for that function in the reference section that follows. Table 2. Basic QuickWin tasks. Task Functions Opening and closing windows _fwopen, _wclose, _wopen Getting and setting window attributes _wgetexit, _wgetfocus, _wgetscreenbuf, _wgetsize, _wsetexit, _wsetfocus, _wsetscreenbuf, _wsetsize, _wsetexit Simulating certain menu selections _wmenuclick Yield to other Windows applications _wyield Displaying the Contents of a Text File Listing 2 shows the program dispfile.c, which illustrates how to open a child window and use it as a scrollable text display. As you can see from the listing, when you open the window with the _fwopen function, you can treat the returned FILE pointer just like any other stream. Despite its simplicity, dispfile.c is somewhat useful - you can load a text file into a child window and browse through the file using the scroll bars attached to the child window.

1

if your windows task is simple a dos program might work a dos app can be made to control a windows app there is a freeware program that enables dos (running in a win3x dos box) to execute windows programs and dos apps can be made to work with windows tasks such as the clipboard depends on what you are trying to do

1

Wow Man, thanks a lot, i will see this options and implement it in my job. Those thing are new to me, useful utilities. Thanks again XD.

0

on the contrary thank you there is still the sdk to locate

1

somthing interesting... Of these the following include their own Windows libraries, and do not require you to purchase a Windows SDK (although you will need to buy the SDK documentation, which is available separately; in the following list, only those marked with * include full documentation on the Windows API). - Borland C++ - Turbo Pascal for Windows * - Microsoft Cobol - Visual Basic - QuickC for Windows * - Watcom C/386 * - Turbo C++ - Zortech C++ 3.0 * - Microsoft C/C++ 7.0 *

0

Microsoft's upgrade to C/C++ 7.0 includes online documents only. Visual Basic Professional Toolkit includes basic API manuals. Borland C++ 3.1/Application Frameworks includes basic API manuals. Of these, Microsoft C/C++ 7.0 and Borland C++ 3.1 include the updated Windows 3.1 SDK. Windows 3.0 SDKs still work, but won't be able to take advantage of many of the Windows 3.1 features. The following also include the Microsoft QuickWin libraries (or the Borland equivalent, EasyWin), allowing rapid conversion of DOS character applications into the Windows environment: - Microsoft C/C++ 7.0 - Microsoft Cobol - Microsoft Fortran - QuickC for Windows - Turbo Pascal for Windows - Turbo C++ for Windows - Borland C++ 3.0 - Watcom Fortran - Watcom Fortran/386 - Zortech C++ 3.0

0

Thanks Watler, Yes, the Borland products have the documentation of Win APIs (Im using now), and some tools are in some products, very useful. Thanks again.

0

Hi ishenly If you have the MSDN 16 bit platform archive disks then it can be found on the disk whose title is 16Bit SDKs and Tools, Windows NT 3.51, Service Pack 5 (Danish) The path would be something like like: M:\WIN31\SDKS\US\ in this folder run the install.exe program. In my case M is the cd/dvdrom drive letter. Also in the 16 bit platform archive is the full documentation for SDK and DDK which I think you would find very helpful. Hope that helps Jhangeir Akhtar

0