HDTenEightyP/NetNews huggingface dataset:
From: me41@sdcc12.ucsd.edu (david j. looney)
Newsgroups: comp.os.os2.programmer
Subject: Re: Where is getch()?!??
Date: 16 Dec 92 17:17:02 GMT
Organization: University of California, San Diego

Speaking of which, for us lowly gnu (golly its not kansas) gcc
folks, is there ANY workaround in character mode to read single
characters from the keyboard ala getch() ? Do more recently updated
libs support this function? Can one call a supplied vio or pm
functions from a window compatible program ?

This is an absolute essential for me, and if there's no way to do it
with gcc then it's going to mean signficant $$$ to buy a complier
that does (any suggestions ?)
Newsgroups: comp.os.os2.programmer
From: mitch@de01.denver.waii.com (Mitch Upton)
Newsgroups: comp.os.os2.programmer
Subject: GPI function and Message Parm's reference?
Date: 15 Dec 92 22:28:26 GMT
Organization: Western Geophysical


     I have been working with the GPI and  Window functions in OS/2 2.0 recently and I noticed that there is very little reference material available.  Specifically, I need reference material on parameter lists for the GPI/Dos/Win functions.  Also, a good comprehensive list of possible application and system messages and their associated message parameters would be helpful.  I have found certain texts that touch on some functions and messages, but nothing dedicated to them.  Any suggestions on where I can 

find said information would be GREATLY appreciated.
From: john.navas@uttsbbs.uucp (John Navas)
Newsgroups: comp.os.os2.programmer
Subject: RE: DOS BOX PROGRAMMING
Date: 20 Dec 92 12:56:00 GMT
Reply-To: john.navas@uttsbbs.uucp (John Navas)
Organization: The Transfer Station BBS, Danville, CA - 510-837-4610/837-5591

kevin@wicat.com (Kevin Vigor) writes:

 > Interestingly enough, I have reveived the PDK since this thread
 > started, and the only information I can find relating to
 > programming the DOS box is about using named pipes to communicate
 > between a DOS session and a OS/2 session. I can find absolutely no
 > mention of time-slicing (though the call I originally mentioned
 > does work), nor anything else of interest. I sincerely hope this
 > information will be documented in a later version (preferably very
 > soon!).

Check out the "Virtual Device Driver Reference" and "DOS and Windows
Environment".

Best regards,
John
From: GG.MPD@forsythe.stanford.edu (Michael Durket)
Newsgroups: comp.os.os2.programmer
Subject: Workframe and MSC 6.00A
Date: 11 Dec 1992 14:59:39 -0800
Organization: Stanford University
NNTP-Posting-Host: morrow.stanford.edu

I'm getting a C1024 error running MSC 6.00A under the Workframe
(the compiler was installed so that it runs under OS/2 not
DOS).

The error is due to the fact that I'm compiling with the /Zi
option and is caused by the compiler running out of files.
(I located an article in the Microsoft Knowledge Base that
indicates that the /Zi option requires a file handle, and
that this may cause nested includes to run out of files thus
causing the C1024 error).

According to the article, the fix is to edit CONFIG.SYS to
increase the FILES= parameter. This is all well and good,
but that applies to DOS programs only, correct? For OS/2
does this have any meaning? If so, how do I adjust it for
running MSC in OS/2 protected mode under the Workframe?

Any assistance is appreciated.
Newsgroups: comp.os.os2.programmer
From: ernst@opal.cs.tu-berlin.de (Ernst Kloecker)
Subject: OS/2 libraries thread-safe ?
Organization: Techn. University of Berlin, Germany
Date: Wed, 16 Dec 1992 22:13:52 GMT

Hi,

what precautions do I have to take when calling C-library functions from
different threads in one process ?

What happens to static variables like 'errno' ?

Can I safely call '...printf()' from different threads ?

Or are the only safe functions the OS-functions in 'bsedos.h' ?

Or are even those functions not completely thread-safe ?


Thanks for any info, Ernst.
--

-----------------------------------------------------------------------------
Ernst Kloecker      phone: ++49-30-6181635      e-mail: ernst@cs.tu-berlin.de
-----------------------------------------------------------------------------
Newsgroups: comp.os.os2.programmer
From: richk@grebyn.com (Richard Krehbiel)
Subject: Re: Monochrome card in OS/2 DOS VDM work okay?
Organization: Grebyn Timesharing
	<1992Dec17.161351.11289@gandalf.UMCS.Maine.EDU>
Distribution: usa
Date: Fri, 18 Dec 1992 03:25:10 GMT

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...
-- 
Richard Krehbiel                                 richk@grebyn.com
OS/2 2.0 will do for me until AmigaDOS for the 386 comes along...
From: sl31+@andrew.cmu.edu (Stephen M. Lacy)
Newsgroups: comp.os.os2.programmer
Subject: Re: New programmer requesting assistance
Date: 12 Dec 92 11:30:03 GMT
Article-I.D.: andrew.kf_ZbPO00iV102v6MB
Organization: Junior, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA

Excerpts from netnews.comp.os.os2.programmer: 11-Dec-92 Re: New
programmer requesti.. by Bruce Kitchin@lf.hp.com 
> Microsoft Press(!!!!).  It appears that they made it 'out-of-print'
> even when there was some demand for it.  Occaisionally one sees a copy
> especially in a used book store.  One might also be able to borrow a copy.

I found this book ~6 months ago in a bookstore, new.  I also saw it
alongside "Client/Server Programming with OS/2 2.0" in a Border's book
store not more than 3 weeks ago.  Granted, in both cases there was only
one copy, and in the first case I was the person to buy the one copy :)
-- along with the Client/Server book, which is also excellent.   I also
recommend "OS/2 Presentation Manager GPI", but with a little hesitation.
 It took me about 3 readings of this thing to figure out what the hell
was going on.  Its sooooo condensed its almost too much.  (Every try
learning C with K&R as your only reference?  Well, its worse than that.)

Steve


"I can't understand what makes a man hate another man, help me
understand." -Depeche Mode
Newsgroups: comp.os.os2.programmer
From: robbar@aplcenmp.apl.jhu.edu (Robert Baruch)
Subject: Multicolumn Listboxes
Organization: Johns Hopkins Continuing Professional Programs
Date: Wed, 16 Dec 1992 13:37:02 GMT

Anyone have any code to perform multicolumn listbox insertions?
This would be a great help to me if someone knew or had the source
to do this!

Thanks,

Rob Baruch
Organization: Sophomore, H&SS general, Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.os.os2.programmer
Date: Tue, 15 Dec 1992 05:26:44 -0500 
From: Matthew Edward Patton <mp52+@andrew.cmu.edu>
Subject: Re: DOS Box Programming

Excerpts from netnews.comp.os.os2.programmer: 14-Dec-92 Re: DOS Box
Programming by Kevin Vigor@wicat.com 
> 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?

Where do I get the info?


Thanks

==================================================================
                     Laws of Computer Programming

1. Any given program, by the time it is up and running is obsolete.
2. Any given program costs more and takes longer than planned and budgeted.
3. Inside every large program is a small program struggling to get out.
4. Program complexity grows until it exceeds the capability of the programmer
   who must maintain it.
5. At the source of every error which is blamed on the computer, you will
   find at least two human errors, including the error of blaming it on the
   computer.

Press F4 to exit menu.
From: francis@vnet.ibm.com (Tim Francis)
Date: Mon, 14 Dec 92 13:43:17 EST
Subject: Workframe and MSC 6.00A
Newsgroups: comp.os.os2.programmer
Reply-To: francis@vnet.ibm.com
Organization: IBM Canada Lab, WorkFrame/2 development
Disclaimer: This posting represents the poster's views, not those of IBM

In article <1gb6grINNcjk@morrow.stanford.edu>,
GG.MPD@forsythe.stanford.edu (Michael Durket) writes:
>
>I'm getting a C1024 error running MSC 6.00A under the Workframe
>(the compiler was installed so that it runs under OS/2 not
>DOS).
>
>The error is due to the fact that I'm compiling with the /Zi
>option and is caused by the compiler running out of files.
>(I located an article in the Microsoft Knowledge Base that
>indicates that the /Zi option requires a file handle, and
>that this may cause nested includes to run out of files thus
>causing the C1024 error).
>
>According to the article, the fix is to edit CONFIG.SYS to
>increase the FILES= parameter. This is all well and good,
>but that applies to DOS programs only, correct? For OS/2
>does this have any meaning? If so, how do I adjust it for
>running MSC in OS/2 protected mode under the Workframe?
>
>Any assistance is appreciated.

WorkFrame uses several file handles itself, to pipe the output of the
compiler into the listbox, etc.  To compensate, the maximum number
of file handles available is dynamically increased, above the FILES=
statement in your config.sys (which does work under OS/2).  Unfortunately,
and as best as we can determine, MSC 6a is hardcoded to only use file
handles less than 20.  Even though the final open succeeds, the compiler
will report a failure, and abort.

To compensate, I've written a small utility that will move all file handles
in use to above 20; the compiler will now run to completion.  The utility
is located on the WorkFrame/2 interface documentation & sample disk,
which can be obtained from any IBM marketing office.  For further
details on how to obtain this disk, contact me off-line.   -tim
Newsgroups: comp.os.os2.programmer
From: caliaro@avalon.physik.unizh.ch (Aurelio Caliaro)
Subject: Re: GNU C/C++ for OS/2
Organization: University of Zurich, Department of Computer Science
X-Newsreader: Tin 1.1 PL4
Date: Tue, 15 Dec 1992 07:41:00 GMT

kevinl@tisdec.tis.tandy.com writes:
: 
: When using GNU C/C++ for OS/2, I am unable to run the programs it
: produces.
: 
: Everything compiles and links OK when just compiling a C program,
: but when I try to run it, OS/2 stops the program and says it
: created a problem and cannot continue.
: 
: When I try to link a C++ program I get unresolved externals that
: look something like __?????__, where ? represents some character--
: some undefined constant I think.

A C++ program? C++ is a portable language -- it says. Well, it isn't! I had
several C programs that do not work on OS/2 without modifications, and mostly
there are exactly those errors of unresolved externals. Maybe you didn't link
all necessary libraries. Maybe GNU C does not support commands your program
has. If you want to port C programs from Unix, you better take EMX/GCC, because
it has been designed for this purpose (of porting from Unix). Otherwise you
must try to replace the unknown commands with others that GCC knows.


: Also, when link386 finishes, it says that the program type is not
: specified "assuming WINDOWCOMPAT."  How do I specify the program type?
: I tried the /PMTYPE option, but it did not help.  This is really
: secondary.  I don't mind the message as long as I can get the programs
: to actually _run_.


If your programs run in an OS/2 window in character mode there is no problem.
Because this is the setting LINK386 supposes. If your application is for PM,
you must define a .def-file. See the documentation with EMX/GCC for the
settings of the definitions file.


           Aurelio Caliaro
Xref: sparky comp.os.os2.programmer:7131 comp.os.os2.apps:9502 comp.os.os2.misc:39928
From: dic5340@hertz.njit.edu (David Charlap)
Newsgroups: comp.os.os2.programmer,comp.os.os2.apps,comp.os.os2.misc
Subject: Re: DLL question
Keywords: DLL library
Date: 18 Dec 92 20:46:37 GMT
Organization: New Jersey Institute of Technology, Newark, N.J.

In article <lj1ktuINNftf@exodus.Eng.Sun.COM> deepakd@ural.Eng.Sun.COM (Deepak Dhamdhere) writes:
>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. 

Are you also using the compiler switches to ensure that DS!=SS and
that DS is always loaded on process entry.  I think these are in the
keyword EXPENTRY.  I believe that any functions you export to a DLL
must be declared with this.

>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.

It sounds like the DLL is (correctly) assuming that DS!=SS, and is
loading it, but the calling program isn't providing the segment.  Be
sure that the code and headers are using the EXPENTRY keyword for all
exported functions.

>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.

In general, I don't like to call C run-time functions from DLL's, but
that's a different story.  Some compilers (like EMX/GCC) have the C
library functions in a DLL, so there's little linkage problems, but
you can't do that with MS-C.



-- 
  |)  David Charlap          | .signature confiscated by FBI due to
 /|_  dic5340@hertz.njit.edu | an ongoing investigation into the
((|,)                        | source of these .signature virusses
 ~|~
Newsgroups: comp.os.os2.programmer
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: Minimizing window with REXX
Keywords: minimize, rexx
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Distribution: usa
Date: Thu, 17 Dec 1992 23:10:20 GMT

In article <burkley.724353692@nosc.mil> burkley@nosc.mil (Joe Burkley) writes:
>I have a little application that has no need to run in an open window, but
>I can't use start /min to run it.  It is a rexx program that calls some
>os2 exe code.  Right now I have the rexx code call itself like this
>Original invocation: "example"
>then the program parses the startup arguments and calls itself with
>start /min example run_me
>where the "run_me" parameter is used to check whether this is the first or
>second invocation of the program.
>This works OK, but isn't very clean.  So back to my question, is there a
>way for a rexx program to cause itself to be minimized?

Is there something in Visual REXX that you might use?  (Visual REXX is
available via anonymous ftp from software.watson.ibm.com.)

>A second question.  The os/2 applicaiton my rexx code starts likes to throw a 
>lot of garbage to the screen.  Currently I redirect the output to a file and
>then delete the file.  Can a redirect it to a null file?

Sure.

Just use:

PROGRAM > NUL

-- 
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: NOVEMBER PDK INFO...
Date: 16 Dec 92 08:41:00 GMT
Reply-To: john.navas@uttsbbs.uucp (John Navas)
Organization: The Transfer Station BBS, Danville, CA - 510-837-4610/837-5591

Scott.Jibben@f115.n282.z1.tdkt.kksys.com (Scott Jibben) writes:

 > I ordered & received an IBM PDK CD.  Is there more than one of
 > these floating around (you noted November PDK)?  I think I received
 > mine before November so I'm wondering if there is a newer version?

There are currently three versions: first release; 10/92; and 11/92.
The most recent version has the C++ compiler.

Best regards,
John
From: jmaynard@oac.hsc.uth.tmc.edu (Jay Maynard)
Newsgroups: comp.os.os2.programmer
Subject: What does CDROM.IFS expect from a driver?
Date: 11 Dec 1992 23:09:56 GMT
Organization: UT Health Science Center Houston


Is the software interface from CDROM.IFS to the driver documented anywhere?
I've poked through the Physical Device Driver reference with no success...
What else talks to the CD-ROM drive (something in MMPM/2, perhaps)?
-- 
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@oac.hsc.uth.tmc.edu      | adequately be explained by stupidity.
  "All [Windows] NT has is a lot of journalists fooled." -- Brian Button
Newsgroups: comp.os.os2.programmer
From: joiner@exa.cs.umn.edu (Jay K. Joiner)
Subject: Re: Online help, API reference
Organization: University of Minnesota
Date: Tue, 15 Dec 1992 16:40:02 GMT

In <1992Dec15.085659.248@vulcan.resmel.bhp.com.au> paulg@a1.resmel.bhp.com.au (Paul Gallagher) writes:

>FINALLY I've got myself setup for OS/2 development. I'm using
>IBM C Set/2 and workframe that came on CD from a developer's
>conference.

>Is a complete API reference available on-line? 

As far as I can tell, there is a complete API reference on the Nov PDK.  
Run the INSTALL script from the root dir of the CD, and select the 
Documentation option.  Pick the option to install all of the documentation
and you will get a folder with icons for everything on the CD.  Very 
little HD is used since all the documents stay on the CD.
From: woan@exeter.austin.ibm.com (Ronald S. Woan)
Subject:  COBOL for OS/2 2.0
Date: Wed, 16 Dec 1992 21:11:19 GMT
Reply-To: woan@cactus.org
Organization: Austin School of Hardknocks

In article <ant.724489686@brolga> ant@brolga.cc.uq.oz.au (Anthony Murdoch) writes:
>I was wondering if there is an IBM cobol out there, and how similar it is
>to VM cobol.  IE how much work would be required to port a major
>application from VM Cobol to OS/2 Cobol.

I think Microfocus COBOL is the most popular out there and it is
apparently very similar to VM COBOL...

-- 
+-----All Views Expressed Are My Own And Are Not Necessarily Shared By------+
+------------------------------My Employer----------------------------------+
+ Ronald S. Woan                       woan@cactus.org or woan@vnet.ibm.com +
+ other email addresses             Prodigy: XTCR74A Compuserve: 73530,2537 +
Newsgroups: comp.os.os2.programmer
From: richk@grebyn.com (Richard Krehbiel)
Subject: Monochrome card in OS/2 DOS VDM work okay?
Organization: Grebyn Timesharing
Distribution: usa
Date: Thu, 17 Dec 1992 04:33:35 GMT

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.
-- 
Richard Krehbiel                                 richk@grebyn.com
OS/2 2.0 will do for me until AmigaDOS for the 386 comes along...
From: halgrim@diku.dk (Maz H. Spork)
Newsgroups: comp.os.os2.programmer
Subject: Re: C++ and Database Manager
Date: 16 Dec 92 14:44:07 GMT
Organization: Department of Computer Science, U of Copenhagen

The problem is the same old one: the embedding is not as close to your
host language as you'd like it to be. Workaround: use dynamically allocated
data or declare automatic locals in the head of your functions.

Alternatively, you can brace the offending locals inside the function in
which case they'll never be constructed. 

Don't expect C++ exception handling to be supported much anywhere, as there
is still much discussion as to its generality and usefulness (though all
clear-minded thinkers know it's a good idea!)

M Spork
halgrim@diku.dk
From: John.Cocula@f347.n109.z1.fidonet.org (John Cocula)
Sender: Uucp@blkcat.UUCP
Newsgroups: comp.os.os2.programmer
Subject: Re: Com Port routines fo
Date: Mon, 14 Dec 1992 11:07:12 -0500

In a message to All <12-13-92 18:26>, William M. Utter writes:

 WM>  Does anyone know of any good Com Port routines for OS/2 2.0..

Sure, DosOpen, DosDevIOCtl, DosRead, DosWrite, and DosClose.  More
info for DosDevIOCtl in on-line programming reference.

John
  
___  
 * PMQWK 1.00b5 *
From: tmg@midget.saar.de (John Tmg)
Newsgroups: comp.os.os2.programmer
Subject: Re: Is OS/2 a good development platform for Windows 3.1?
Date: 10 Dec 92 17:10:25 GMT
Organization: Yoyodyne Posting Systems, Midget HQ

In comp.os.os2.programmer jules@kentek.com writes:

>I've tried very hard to convince the powers-that-be that OS/2 v2 is a
>much better target environment but I've so far been completely
>unsuccessful.  However, I'd still like to do the development under
>OS/2.  Is OS/2 a suitable development and test environment for Windows
>programming or would I be better off just canning OS/2 and working
>with MS-DOS and Windows?

>I've already ftp'd the c7os2.zip package which claims to support OS/2
>hosted development for MSC7 but, since I don't have MSC7, I haven't
>been able to test it.

>jules@kentek.com

This package does work (indeed :-)
But one recommendation: i learned by experience, that the Windows environment
on OS/2 is not as stable as i would wish, but maybe that just depends on
my network setup, too :-)
Get *lots* of RAM. 16 MB minimum. More is even better. I think the most
annoying thing about OS/2 is that it swallows RAM as if it was nothing,
especially when running Windows Apps.
Be aware that the debuggers will _not_ run under OS/2 2.0.
A good setup would be to have a DOS partition with Windows installed,
C7 and the source code on A FAT partition, so you could boot into DOS
to do some debugging.
I do only develop for DOS in the moment, and that works great. Windows
developing would be harder (ie. not as stable), but Windows itself
crashes even more often, i think :-) :-)

hope this helps,
  Tilman

BTW: Windows 3.1 is not fully supported yet, but at least the OLE DLLs
work, so if you do not use any of the really *new* features in Win3.1
developing should be quite possible. The Win 3.1 update for OS/2 2.0
is expected by the end of the year/1st Quarter '93, rumours welcome...
-- 
tmg@midget.saar.de dumb, dumb, dumb, dumb, dumb, dumb, dumb, dudumb, dumb, dumb
Tilman Mueller-Gerbes, Saarbruecken
Xref: sparky comp.os.os2.programmer:6999 comp.os.os2.misc:39322