HDTenEightyP/NetNews huggingface dataset:
From: lansche@torolab6.VNET.IBM.COM (Martin Lansche)
Date: Thu, 17 Dec 92 15:06:15 EST
Newsgroups: comp.os.os2.programmer
Subject: Re: Yet another novice on PM programming
Disclaimer: This posting represents the poster's views, not those of IBM
News-Software: UReply 3.0

In <1992Dec17.171822.1978@iplmail.orl.mmc.com> Dave Mckinny writes:
>Hello,
>I have a book on PM programming by Dror and somebody else I don't have it
>with me but ....
>My problem is that of the three sample programs I've tried only the first
>worked. I'm using EMX/GCC. The first program just sends a beep on the speaker.
>It worked no problem. The second program is supposed to put a slider on the
>screen. It compiles and links ok, but when I try to execute it nothing happens.
>
David,  I don't know if this helps, but I have managed to get most (all
but one that I tried) of the examples from the book to work.  I suspect
that your problem is your linker options.  Which linker are you using?
LINK386.EXE?  You need to specify these options to LINK386.EXE:
   /NOL /NOE /PM:PM
and you must give the correct name to the prompt for .DEF file.
  If you get "incompatible types" messages at link time, you may need to
add some casts.  Also, you should change the 2nd parameter for all
instances of ClientWinProc from "USHORT" to "ULONG".  I didn't do this
until late in the book (i.e. USHORT will work sort of), so I am sure that
your problem is that when you link you are creating a PM app.
  I hope this helps.
Martin Lansche, IBM Lab, Toronto Canada
  ________________________________________________________________________
   Ilu Iluvatar en kare eldain a firimoin ar antarota mannar valion :
   numessier.  Toi aina, mana, meldielto -- enga morion : talantie.
   ----------------------------------------------------------------------
   The father made the world for elves and mortals and he gave it into
   the hands of the Lords in the West.  They are blessed, holy and loved,
   except the black one.  He has fallen.  (J.R.R. Tolkien).
  ________________________________________________________________________
From: jawetzel@athena.mit.edu (The Rottweiler)
Subject: 32-bit programming using MASM 6.00b
Organization: Massachusetts Institute of Technology
Date: Mon, 14 Dec 1992 13:18:17 GMT

Is there anyone out there who has experience assembling 32-bit OS/2 v2.0
programs using Microsoft's MASM 6.00b.  I thought that I could use the 
flat memory model but LINK386 chokes on the object code.  LINK386 does not
complain if I use the normal segmented model but the EXE created generates
a 000E trap. 

Any pointers would be greatly appreciated.

						Jake

------------- hello.asm ------------------------

		title	filecomp.asm

		.386

INCLUDE 	hello.inc

cr		equ	0dh
lf		equ	0ah

stdin		equ	0
stdout		equ	1
stderr		equ	2

DGROUP 	 	group	 _DATA

_DATA		 segment dword public use32 'DATA'

testmess	db	cr,lf,'Hello World',cr,lf
testmess_len	equ	$-testmess

wlen		dw	?

_DATA		ends

_TEXT		segment dword public use32 'CODE'

main		proc	near

		push	stdout
		push	ds
		pushd	offset DGROUP:testmess
		push	testmess_len
		push	ds
		pushd	offset DGROUP:wlen
		call	DosWrite

		or	eax,eax
		jnz	error

		push	1
		push	0
		call	DosExit

error:		push	1
		push	1
		call	DosExit

main		endp

_TEXT		ends

		end	main


------------- hello.inc ------------------------------------

externdef	DosWrite:near
externdef	DosExit:near


------------- hello.def ------------------------------------

NAME	HELLO WINDOWCOMPAT
DESCRIPTION "OS/2 2.0 Test Program"
PROTMODE
STACKSIZE 4096


------------- assemble commands --------------------------

ml /c /Zi /W3 hello.asm
link386 /NOE /NOD /ALIGN:16 /M /DE hello,,,c:\os2\doscalls,hello;


Newsgroups: comp.os.os2.programmer
From: jurlwin@gandalf.UMCS.Maine.EDU (Jeff Urlwin)
Subject: Re: Monochrome card in OS/2 DOS VDM work okay?
Organization: University of Maine, Department of Computer Science
Distribution: usa
Date: Fri, 18 Dec 1992 18:15:35 GMT

In article <1992Dec18.032510.29705@grebyn.com> richk@grebyn.com (Richard Krehbiel) writes:
>In article <1992Dec17.161351.11289@gandalf.UMCS.Maine.EDU> jurlwin@gandalf.UMCS.Maine.EDU (Jeff Urlwin) writes:
>
>>   In article <1992Dec17.043335.9041@grebyn.com> richk@grebyn.com (Richard Krehbiel) writes:
>>   >I'd like to get a monochrome (text) card and monitor, and use it for
>>   >two-screen DOS program debugging.  I think this should work okay, but
>>   >I thought I'd ask first.
>>
>>   I have no problems with this for small enough programs.  When debugging
>>   larger ones, I need to run TD386, which won't run in VDM.  When the app
>>   is small enough, all is OK.  If you have any further questions, let
>>   me know.
>
>Hmmm... OS/2 wouldn't boot for me when I had the monochrome card in.
>Maybe I had it set wrong.  I'll have to try it again...

Well, I can think of at least two things that may go wrong.  Try the 
selective install program and add support for the secondary monitor
(I did this during the normal install...).  Second:  Make sure the card
doesn't have an interrupt conflict with anything else.  Most of these cards
come with a parallel port adapter which is usually set up as IRQ5 and IRQ7.
(My bus mouse is setup as IRQ5 and that's the default for a secondary
printer port...If I had both of these at IRQ5, I would imagine OS/2 would
have trouble initializing the mouse...who knows what happens if it got
into a loop testing for something and gets responses from both cards...)

DOS doesn't use the IRQs for printers and doesn't care, but I'd be careful 
under OS/2 and other more sophisticated, multitasking OSs (Unix, NT, for 
example).

There should be an option on the card to disable the extra stuff.  I'd 
start from there.  It may not be an option, though, if you can't find
the documentation for it.  

Good luck,

Jeff

-- 
--------------------------------------
jurlwin@gandalf.umcs.maine.edu

Newsgroups: comp.os.os2.programmer
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: ovember PDK Info...
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Fri, 11 Dec 1992 23:24:15 GMT

In article <1992Dec10.230819.16814@cs.brown.edu> wcn@cs.brown.edu (Wen-Chun Ni) writes:
>In article <168B9EBBE.BOB@ysub.ysu.edu> BOB@ysub.ysu.edu (Bob Quigley) writes:
>>I just ordered the PDK and was wondering what parts of TCP/IP are included?
>>Does it include the programmers toolkit and/or the source kit? I have some
>>TCP/IP applications I need to port and I may have to resort to buying the
>>programmers toolkit for the socket support ($325!)
>Yes, all included. Enjoy it!

By the way, 32-bit DLLs have now been released (they should be
available shortly via anonymous ftp from ftp-os2.nmsu.edu) which allow
easier programming to the main TCP/IP DLL.

I know lots of people have been waiting for these.

-- 
Timothy F. Sipples      | Read the OS/2 FAQ List 2.0h, available from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/info
Dept. of Econ., Univ.   | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
of Chicago, 60637       | [Read the List, THEN post to ONE OS/2 newsgroup.]
From: sjb5@ns1.cc.lehigh.edu (STACY JOHN BEHRENS)
Newsgroups: comp.os.os2.programmer
Subject: OS/2 PDK Reminder
Date: 14 Dec 92 20:46:29 GMT
Organization: Lehigh University

Just a reminder:

The code license for the first PDK expires tomarrow (Dec. 15)  You should
order the new November PDK which extends the license to something like march.

-- 
Stacy John Behrens
*===)-------------
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The only justification for our concepts and systems of concepts is that they
serve to represent the complex of our experiences; beyond this they have not
legitimacy.                                  [Albert Einstein]
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Newsgroups: comp.os.os2.programmer
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: BSR 6800 CDROM driver
Followup-To: comp.os.os2.misc
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Thu, 17 Dec 1992 23:07:10 GMT

In article <Uf_m3bW00WCQ8=pkRI@andrew.cmu.edu> mp52+@andrew.cmu.edu (Matthew Edward Patton) writes:
>A friend of mine asked me to ask around for the availability of a driver
>for the BSR 6800 from DAK.  He can't seem to get anything to work.  CAN
>someone direct me to a site or provide hints to a workaround?

The only way, at present, is to use a specific DOS session.  See
Appendix E of your Installation Guide and/or the online Command
Reference under VMDISK for further instructions.

-- 
Timothy F. Sipples      | Read the OS/2 FAQ List 2.0h, available from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/info
Dept. of Econ., Univ.   | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
of Chicago, 60637       | [Read the List, THEN post to ONE OS/2 newsgroup.]
From: john.navas@uttsbbs.uucp (John Navas)
Newsgroups: comp.os.os2.programmer
Subject: RE: DOS BOX PROGRAMMING
Date: 16 Dec 92 08:46:00 GMT
Reply-To: john.navas@uttsbbs.uucp (John Navas)
Organization: The Transfer Station BBS, Danville, CA - 510-837-4610/837-5591

Matthew Edward Patton <mp52+@andrew.cmu.edu> writes:

 >> Call interrupt 2F (hex) with AX set to 1680 (hex). The call
 >> returns with AL set to zero on sucess and 80 on failure. N.B.:
 >> this same call works in a Windows 3.x DOS box and under DPMI.

 > Although this information is not what I am interested in (I am not
 > the one who requested it) my interest lies in where you found the
 > information about the interrupt/call information.  Is there
 > programmer documentation for the mdos/os2 kernel I don't know
 > about?

There's a great deal of inportant information in a couple of the "red
books":  "OS/2 2.0 Technical Library, Virtual Device Driver Reference"
and "OS/2 Version 2.0, Volume 2: DOS and Windows Environment".

 > Where do I get the info?

You can buy the red books direct from IBM, or you can order a copy of
the Professional Developers Kit (PDK) CD-ROM, which contains these
documents as well as a *wealth* of other information.  ( Best excuse
for a CD-ROM drive I know! :)

Best regards,
John
    
Xref: sparky comp.os.os2.programmer:7104 comp.os.os2.apps:9444 comp.os.os2.misc:39782
From: deepakd@ural.Eng.Sun.COM (Deepak Dhamdhere)
Newsgroups: comp.os.os2.programmer,comp.os.os2.apps,comp.os.os2.misc
Subject: DLL question
Date: 17 Dec 1992 19:23:42 GMT
Organization: Sun Microsystems Inc., Mountain View, CA
NNTP-Posting-Host: ural
Keywords: DLL library

I am posting this question for a friend, hope that the DLL experts can
help him out.

Deepak Dhamdhere

************
I have an application that calls functions from ABC.DLL,
those functions call routines from XYZ.DLL and those, in turn,
call routines from the C library. This application starts a child process
using DosExecPgm, which in turn, does the same thing. I have used 
llibcdll.lib to link all these programs and libraries. 

Very frequently, it generates a segementation violation. When I checked
with Codeview, I found that the malloc() call fails because it tries to
load a non-existent segment into DS.

Any clues to why is this happening ? I would like to know the correct
way of compiling and linking ABC.DLL, XYZ.DLL and the applications.

Your immediate help will be appreciated very much.
************
Newsgroups: comp.os.os2.programmer
From: mark@snark.itc.gu.edu.au (Mark Hessling)
Subject: Re: Online help, API reference
Organization: ITC, Griffith University, Brisbane, Australia
Date: 17 Dec 92 02:46:30 GMT

cnadler@vnet.ibm.com (Cliff Nadler) writes:

>In <1992Dec15.085659.248@vulcan.resmel.bhp.com.au> paulg@a1.resmel.bhp.com.au (Paul Gallagher) writes:
>>Hi,
>>
>>I've spent some time exploring the online books, INF files etc,
>>and I've set EPM up for online help, but (forgive me if there's
>>an obvious answer to this question)... where the hell do you
>>"go" to get comprehensive online API help? 
>>
>>Is a complete API reference available on-line? If not, what are
>>some good alternative sources? (Am I missing something because
>>IBM only gave me the CDs and not the printed docs?)
>>

>The on-line documents should be complete. What do you think is missing?


How about the Vio,Mou and Kbd function calls. They exist but there is no
documentation on them anywhere.
I have asked our local DAP people for a response and they promptly sent
me a copy of the reply to a discussion on the OS2FNS FORUM. I will quote
that reply:
--------------------- start of quote
THE VIO/KBD/MOU calls are inherently 16-bit, byte swap oriented. They
don't port well to other architectures so I would expect them to not
be available on a portable versiob of OS/2, if one is ever produced.
However, I would expect them to remain in an Intel based OS/2 product
for compatability with 16-bit apps. If you believe your customer
base would want to use your product on OS/2 on a different machine
architecture, don't use VIO/KBD/MOU calls, make a PM application.
------------------- end of quote

So what if you want to remain on an Intel platform with OS/2 or even
wanted to run without the WPS ? How do you write full-screen window
applications for that situation without using the Vio,Mou and Kbd functions?

I am the maintainer of a public domain curses library for DOS and OS/2
and trying to guess the usage of these taboo functions is a real pain.

Discouraging the use of these functions also discourages the porting of
character-based applications from other platforms. I suppose with the
wealth of OS/2 applications available, IBM can afford to ignore these
insignificant applications. :-)

>Cliff Nadler
>IBM Federal Systems Company

>Note: This post represents the views of the poster, not those of IBM or the
>      IBM Federal Systems Company
------------------------------------------------------------------------
Mark Hessling                         Email: mark@snark.itc.gu.edu.au
DBA,ITS                               Phone: +617 875 7691
Griffith University                   Fax:   +617 875 7877
Nathan, Brisbane QLD 4111 Australia   *** PDCurses Maintainer ***
------------------------------------------------------------------------
Newsgroups: comp.os.os2.programmer
From: jurlwin@gandalf.UMCS.Maine.EDU (Jeff Urlwin)
Subject: Re: AT&T enhancements for the DAP CD-ROM disk for $10. Worth it?
Keywords: OS/2, DAP, AT&T, enhancements, C++
Organization: University of Maine, Department of Computer Science
Date: Mon, 14 Dec 1992 23:43:10 GMT

In article <Bz7L6w.3r8@cs.uiuc.edu> joshi@cs.uiuc.edu (Anil Joshi) writes:
>
>I called the 1-800-3-ibm-os2 the other day to order the DAP CD-ROM. The person
>at the other end asked whether I would like to order the AT&T enhancements
>floppy too for an extra $10. Does somebody know what it contains? Any help
>would be greatly appreciated.

If you plan to use classes and functions normally in iostream.h, fstream.h and
stream.h, you'll want these.  A good example of use of the iostream is 
the cout stream along with the operators: << and >>.

I think it's worth it, but if you only use printf, etc...maybe you can get
by without them.

jeff

-- 
--------------------------------------
jurlwin@gandalf.umcs.maine.edu

Newsgroups: comp.os.os2.programmer
From: boh@fraser.sfu.ca (Changhao Boh)
Subject: DOS Box Programming
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Mon, 14 Dec 1992 08:14:35 GMT

Hi, I am wondering about programming a serial communication programme in DOS
but would like to make it "OS/2 aware".  Thus I have the following questions.

   1.  Is there a way to detect if a programme is operation in OS/2 2.0's
       dos box ?

   2.  Is there a way a programme, running in OS/2 2.0's DOS box, can release
       clock cycles to OS/2 ?

   3.  What happens when a programme hooks onto the serial communication
       inturrupt as provided by DOS INT 21h ? Will a interrupt driven
       serial communication driver written this way be efficient in the
       DOS box of OS/2 ?

The reason why I want to write an OS/2 aware programme in DOS mode is that
I cannot afford an OS/2 based compiler just yet, and I really don't want to
be forced into using C/C++ which is provided by the free GCC compiler.

Good Health.

Changhao.
boh@sfu.ca
From: pr@umiacs.umd.edu (Jesus M. Rodriguez)
Newsgroups: comp.os.os2.programmer
Subject: Re: Zortech C++
Date: 12 Dec 92 05:26:51 GMT
Distribution: na
Organization: University of Maryland Institute for Advanced Computer Studies


Well in response to the question about Zortech C++ for OS/2, there is one
they sent me an offer to get Zortech C++ for OS/2 2.0 for $249.  It is
a 32-bit compiler.  They also have one that does cross-platform compiling
it will do Windoze, DOS, NT, OS/2 all for $699.

Jesus
pr@umiacs.umd.edu
Newsgroups: comp.os.os2.programmer
From: menaf00@DMI.USherb.CA (FRANCOIS MENARD)
Subject: OS/2 MIDI programming ...
Organization: Universite de Sherbrooke -- Dept. d'Informatique
Date: Tue, 15 Dec 1992 07:53:15 GMT

Hi !

I am about to start a new project (Ambitious ???) during Christmas holidays.

It is a General MIDI compatible standard midi file player for OS/2 PM.

To get this program going, I beleive I need either the following :

1st configuration :  MPUDD103.ZIP (OS/2 device driver for an mpu401)

2nd configuration :  MASM 6.0 to write myself a device driver

3rd configuration :  OS/2 MMPM

4th configuration :  C SET/2 with inline assembly allowed

  So far, I do not have the choice to use the MPU401 driver, but the 
documentation is hard to understand, and I have no source to get me going.

Of course, I should use OS/2 mmpm, but it is a commercial product $$$ and, if
I make use of it, I would be shooting myself in the foot, since nobody uses
the thing (unless IBM give it with a future release of OS/2).
 
My *original* C SET/2 will not do inline assembly, so there is no way to
incorporate direct mpu support into my exe file.

So what is your suggestion, does somebody would be willing to help me acquire
a copy of OS/2 mmpm, I know that you can get the developer CDROM, but, 
unfortunately, I do not have a CD-ROM and IBM wont ship beta to Canada (it 
sucks badly <g?> )...

So I either NEED C Set/2 with inline assembly
                 MASM 6.0b to create my device driver
                 OS/2 MMPM

Hope somebody have same interests... <MAJOR GRIN>...

-=Francois=-	
-- 
                 Francois D. Menard -- Menaf00@DMI.USherb.CA
Les opinions refletes dans ce message ne sont pas redevables aupres de FMMO
---------------------------------------------------------------------------
        Francois Menard, Groupe des Utilisateurs OS/2 de Sherbrooke
Newsgroups: comp.os.os2.programmer,comp.os.os2.misc
From: mike@ulinf0.unil.ch (Michael Bloch)
Subject: Database manager programming from Pascal
Organization: HEC, University of Lausanne, Switzerland
Date: Tue, 15 Dec 1992 14:45:36 GMT

With OS/2 v1.3, we were able to do Embedded SQL programming from
IBM Pascal/2 using IBM Database Manager and its precompiler.

Pascal support seems to have disappeared from OS/2 v2.0 + ES

Is this really true ?
Any suggestion or work-around ?

Thanks, Michael
-- 
Michael Bloch, Research Assistant               Internet : mike@ulinf0.unil.ch
University of Lausanne, Switzerland		BIX ID   : astolfi

If I have seen farther, it is by standing on the shoulders of giants - I. Newton
From: rommel@jonas.gold.sub.org (Kai Uwe Rommel)
Newsgroups: comp.os.os2.programmer
Subject: Re: 32-bit programming using MASM 6.00b
Distribution: world
Date: Wed, 16 Dec 92 23:37:57 MET
Organization: Private

In article <1992Dec14.131817.14808@athena.mit.edu> jawetzel@athena.mit.edu (The Rottweiler) writes:
>Is there anyone out there who has experience assembling 32-bit OS/2 v2.0
>programs using Microsoft's MASM 6.00b.  I thought that I could use the 
>flat memory model but LINK386 chokes on the object code.  LINK386 does not
>complain if I use the normal segmented model but the EXE created generates
>a 000E trap. 

What probably happens is, that you call the *16-bit* DOS calls in your
program. The 32-bit ones are prefixed with Dos32 instead of Dos, i.e.
Dos32Write and so on. Working example:

----------------------------------------------------
.386
.model	flat
.stack	04000H

includelib doscalls.lib

.data

message	byte	13, 10, "Hello, world.", 13, 10

.data?

count   dword	?

.code

extern	DOS32WRITE:proc
extern	DOS32EXIT:proc

start   proc

	push	offset count
	push    lengthof message
	push    offset message
	push    1
        call    DOS32WRITE

        push	27
        push	1
	call	DOS32EXIT

start	endp
	
	end	start
----------------------------------------------------

Kai Uwe Rommel

--
/* Kai Uwe Rommel                                      Muenchen, Germany *
 * rommel@jonas.gold.sub.org                       Phone +49 89 723 4101 *
 * rommel@informatik.tu-muenchen.de                  Fax +49 89 723 7889 */

DOS ... is still a real mode only non-reentrant interrupt
handler, and always will be.                -Russell Williams
Newsgroups: comp.os.os2.programmer
From: sthiagar@bronze.ucs.indiana.edu (sivasailam thiagarajan)
Subject: Anyone using Zortech C++ for OS/2 2.0?
Organization: Indiana University
Distribution: na
Date: Tue, 15 Dec 1992 19:23:20 GMT

I just got a brochure from Symantec. It loudly screams "C++ COMPILER
FOR WINDOWS FOR $129!!" but mentions in smaller type that you can also
get their 32-bit OS/2 2.0 compiler for $149. Anybody using Zortech
(Symantec) C++ for OS/2 2.0? How is it? Is it worth $149?

Raja Thiagarajan
(sthiagar@bronze.ucs.indiana.edu)
From: parry@yoyo.cc.monash.edu.au (Tom J Parry)
Subject: Re: X-Windows like mouse/focus behavior (here's how)
Originator: parry@yoyo.cc.monash.edu.au
Organization: Monash University, Melb., Australia.
Date: Sun, 20 Dec 1992 00:49:02 GMT

Larry Salomon Jr. (os2man@panix.com) wrote:
> For those interested, I've seen quite a few requests for this behavior.
> Although I haven't tried the below, it should work; no guarantees, however.

> The strategy here is to install a system-wide HK_INPUT hook which follows
> the WM_MOUSEMOVE messages.  You can easily call WinWindowFromPoint() to
> obtain the window handle under the mouse, follow the parent chain until
> you reach the top-level window, and call WinSetFocus() to give it the focus.

You don't need to follow the parent chain, you can do
WinWindowFromPoint(HWND_DESKTOP, &ptl, FALSE). The FALSE means don't look
at children windows so the window returned will be a child of HWND_DESKTOP.
If you do decide to trace backwards for some reason be careful not to
compare anything to HWND_DESKTOP. HWND_DESKTOP is a constant (0 or 1)
whereas a window function will return the handle of the desktop window
(0x201383 or something similar on mine).

-- 
Tom J Parry.
Your reality is a figment of my imagination.
Newsgroups: comp.os.os2.programmer,comp.os.os2.apps,comp.os.os2.misc