PLS: need SDK from Windows 3.1, do you have?

Microsoft / Windows 3.1
September 10, 2009 at 21:05:43
Specs: Windows XP, Celeron 3Ghz - 512 ram
Hi manes
I am doing a job in the old Windows 3.1 (16 bits) and using C++ language (especifycally Microsoft C++ 7); but, I need the Software Development Kit (SDK) for Windows 3.1, because is neccesary for Microsoft C works.

Please, anybody retro fan or developer, this SDK (in english please) is hard to find.

Helpme helpme T.T

BYe


See More: PLS: need SDK from Windows 3.1, do you have?

Report •

#1
September 23, 2009 at 17:23:33
boooooooooooooo T_T

Report •

#2
September 24, 2009 at 13:51:28
humm...
thought 7 could already make win16 apps...

could you give any more details
what are the files needed?
header files,compiler updates,etc...?

if watcom is to large
why not use quickc for windows?


Report •

#3
September 28, 2009 at 19:23:52
Thanks, the files thaht need are: "windows.h" and its (unknowns) relatives; too need utilities like: ImageEditor, DialogEditor, FontEditor; one "winstub.exe".

In esence, documentation from Microsoft C++, about programming Windows 16 bit, say: need SDK. Is a collection of "necesaries".

XD


Report •

Related Solutions

#4
September 30, 2009 at 15:47:59
if you are collecting
some places do claim to have it
http://www.emsps.com/oldtools/msc.h...

heh now if your programming thats a different matter
http://groups.yahoo.com/group/watle...
winstub.exe
msvc++1.5, bp7, POW!,bc3.1 and ,bc4 all have a file with that name

quickC delphi and open watcom dont seem to need it

have you checked to see if what your aiming on doing has already been done yet?
http://win31.no-ip.org/freeware/

let me know whats up


Report •

#5
October 6, 2009 at 23:27:42
Hi Watler, your info is very usseful, Im processing now...

Thanks a lot, I'm working... XD


Report •

#6
October 10, 2009 at 17:10:17

QuickWin Functions

QuickWin is a set of 14 functions, introduced in Microsoft C/C++ 7.0, that
enable you to write simple text-oriented programs that can run under
Microsoft Windows. Essentially, the QuickWin library provides a window
that emulates the standard input/output (I/O) streams. A window
representing the predefined
streams stdin, stdout, and stderr is automatically
created by the library. This window appears as a console window to a
QuickWin program. For a simple text-oriented C progra


Report •

#7
October 10, 2009 at 17:23:28
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.


Report •

#8
October 10, 2009 at 17:39:39
//---------------------------------------------------------------
// 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.


Report •

#9
October 10, 2009 at 17:58:03
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


Report •

#10
October 13, 2009 at 19:02:03
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.


Report •

#11
October 14, 2009 at 15:24:34
on the contrary thank you


there is still the sdk to locate


Report •

#12
November 3, 2009 at 06:03:40
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 *


Report •

#13
November 3, 2009 at 06:08:00
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


Report •

#14
November 12, 2009 at 12:56:01
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.


Report •

#15
November 18, 2009 at 15:34:03
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


Report •

#16
November 22, 2009 at 15:36:27
Thanks Jhangeir,

But, I don't have this disk, thanks for apport... If tou know where get this MSDN, please, tell me

Thanks


Report •

#17
January 6, 2010 at 08:10:39

Report •

#18
January 6, 2010 at 14:38:52
Hi ishenly

Regarding the disk labled "16Bit SDKs and Tools, Windows NT 3.51, Service Pack 5 (Danish)" which includes the SDK for windows 3.1, the best people to get in touch with are Microsoft Developers Network MSDN. When I subscribed to them many years I had the Universal subscription but I specifically had to ask for the 16 bit platforms archive. They had a phone number for the Ireland call centre, If i find it during my next tidy up I will post it here.


I don't know now what the procedure is for getting MSDN, if somebody who has a more recent experience of subscription with them would be better informed than me.

Also another thing I should mention

Installing the SDK with Microsfot C/C++ 7 has do be done from MS-DOS.

If you use the CDROM then you have to configure MSDOS with cdrom support and run the SDK's intall.exe from MSDOS. When I tried from within Windows 3.1 it did'nt work.


The SDK installation program will ask lots of questions so, be relaxed and have patiance.


Hope that helps


Report •

#19
January 7, 2010 at 16:16:44
found a windows source code generator
for Microsoft C 6/7

http://win31.no-ip.org/freeware/pro...


Report •

#20
January 18, 2010 at 02:10:36
Thanks for all, very very Thanks.
Your info is very interesting. I got interest too for old computer magazines, so good.

Report •

#21
January 29, 2010 at 17:46:19
ImageEditor and DialogEditor are in the
bin/tools folder of the xblite install

xblite compiles win32s programs


Report •

#22
January 30, 2010 at 07:12:12
Yes Watler, in XBLite exists this resources editors, but, for use, need Win32s, and my objetive is use 16 bits (strict). Anyway, I can use the editors in another machine and pass the resources creates.

Very thanks XD.


Report •

#23
January 31, 2010 at 17:17:26
the M$ ImageEditor and DialogEditor programs
included with xblite are 16bit


Report •

#24
February 1, 2010 at 17:00:36
sorry my mistake

in xblite the
ImageEditor and DialogEditor helpfiles
and the DialogEditor program are all 16bit

but the imageeditor program is win32


Report •

Ask Question