HDTenEightyP/NetNews huggingface dataset:
From: hsu@leda.TTI.COM (Joe Hsu)
Subject: Device Monitor in 1.3
Keywords: Device Monitor OS/2 1.3 PM
Reply-To: hsu@leda.TTI.COM (Joe Hsu)
Organization: Citicorp+TTI
Date: Tue, 15 Sep 1992 02:30:10 GMT

Does anybody know if the device monitor feature is 
supported under PM in 1.3?

I was able to do DosMonOpen(), DosMonReg(), DosMonRead(),
and DosMonWrite() for KBD$ in OS/2 full screen mode under 1.3.

When I tried to do the same from a PM program, the DosMonReg()
reported that the monitor is not supported.  Why?  I read both
the Duncan book and MS OS/2 Prog. Ref. and nothing was mentioned
this would not work. The diagram in Duncan's book (page 421) 
shows this would work.  

Can somebody help?  Thank you in advance!


Have A Nice Day....
Joe Hsu    Citicorp(+)TTI            Email: hsu@soldev.TTI.COM           
3100 Ocean Park Blvd. Q34            Voice: (310) 450-9111 Ext. 3117 
Santa Monica, California  90405      Fax  : (310) 450-3932           
{philabs,psivax,pyramid,quad1,rdlvax,retix,rutgers}!ttidca!hsu 
Newsgroups: comp.os.os2.programmer
From: oneil@hns.com (Pat O'Neil)
Subject: OS2 Device Driver in C -- Linking Problem
Organization: Hughes Network Systems Inc.
Date: Thu, 3 Sep 1992 22:27:35 GMT

Anyone out there have any experience writing OS/2 drivers in C?

I am writing a 16-bit OS/2 device driver in C/2. I'm having trouble
getting the linker to put the data segment (which contains the
device header) first. The C/2 manual says that the linker
locates segments in the order it encounters them. This seems
true until I start bringing in the C run-time libraries
(which I need for sprintf, strtok, memcpy, etc.). If I link
without the library (and thereby get a zillion unresolveds)
the map at least says that the data segment is first.

Pat O'Neil
Hughes Network Systems
Germantown, Md.
From: merrill@optima.UUCP (Darren Merrill)
Newsgroups: comp.os.os2.programmer
Subject: Re: C Set/2 CSD0014
Date: 15 Sep 92 20:18:41 GMT

From article <19920915.092111.212@almaden.ibm.com>, by ameline@vnet.ibm.com (Ian Ameline):
> Folks, if this fix came from compuserve originally, and you are
> installing it on top of ship level code (not another CSD), *make sure*
> that the package includes ICC.EXE. If it does not, do not replace
> dde4fe.exe, or your compiler will stop working. ICC.EXE didn't make it
> up to compuserve until a few days after the rest of the package.

Yes, this did come from compuserve.  I included the new icc.exe in 
the package when I uploaded it to hobbes.  So, all you need is 
cs0014.zoo to go over ship code.

-darren

--
Darren Merrill                  Internet: merrill@cs.arizona.edu  
Department of Computer Science  Compuserve: 76570,2526
University of Arizona    
Newsgroups: comp.os.os2.programmer
From: rls@tip.wedge.nt.com (Robert L. Smith)
Subject: Re: BASIC on OS/2?
Originator: rls@
Organization: Northern Telecom Inc., RTP, NC
Distribution: na
Date: Tue, 8 Sep 1992 12:13:47 GMT


>>   How do you run BASIC under OS/2 2.0?

    I wish to thank everyone who, via E-mail or otherwise, acquainted
me with the availability of QBASIC.
    Unfortunately, DOS searches on *<anything> don't seem to work.  We
might have avoided this thread if they'd named it "BASICQ".
    Thanks again!

Regards, rLs
Newsgroups: comp.os.os2.programmer
From: cpbaltus@cs.vu.nl (Baltus CPS)
Subject: GNU warning: unknown escapecode "\O"
Organization: Fac. Wiskunde & Informatica, VU, Amsterdam
Date: Fri, 11 Sep 1992 09:44:50 GMT

Hi,
	
	I just downloaded the GCC 2.2 compiler from charon.mit.edu. When
I try to compile (make) the sample3 which is part of the package, i get a lot
of warnings like this:

	C:/GNUOS2-Include/bsedos.h: 1050: warning: unknown escape sequence '\O';

The executable works fine though. What can i do to prevent these messages? 
It is really nasty to search your realy error messages when they're all 
covered up in warnings.

			Stefan.
-- 
-----------------------------------------------------------------------
Department of Mathematics and Computer Science       Vrije Universiteit
				             Amsterdam, The Netherlands
Stefan Baltus.			    	    InterNet: cpbaltus@cs.vu.nl
From: pstevens@Metaphor.COM (Paul Stevens)
Newsgroups: comp.os.os2.programmer
Subject: Re: Help: Kernel Debugger
Date: 9 Sep 92 19:35:33 GMT
Reply-To: pstevens@Metaphor.COM (Paul Stevens)
Organization: m4

In article <1992Sep9.221627.10717@waikato.ac.nz>, hamish@waikato.ac.nz writes:
|> In article <1992Sep8.180216.3718@javelin.sim.es.com>, rpack@javelin.sim.es.com (Rick Pack) writes:
|>>   Just last week, I realized that the debugging kernal is NOT necessary, as
|>> there is a great debugger included in the c-set2 package that runs under
|>> PM and will debug PM programs.  It's called IPMD.  I STILL do not know
|>> what the purpose of the debugging kernal is, as IPMD works just fine 
without
|>> it, and there is none of this async terminal/serial port stuff.
|>>   The install documentation for workset/2 never mentions IPMD, just the 
debug
|>> kernal, which leads you to believe that it is your only option.
|>>
|> 
|> Oh yeah. Use COM2. I could never get my PC booted when trying to use COM1, 
so I
|> moved the mouse from COM2 -> COM1, and moved the debugger to COM2 (The COM1
|> option is only mentioned for the PM debugger part of the kernel debugger, so
|> not really sure if COM1 is workable at all if you have 2 COM ports).
|> 

I can corroborate that.  Even though the docs imply that you can use 
whatever com port you want by use of the /Cn flag, everyone here has
had to use n=2 to get the debugging kernel to run.

+------------------------------------------------------------------------+

   Paul Stevens                        {apple|decwrl}!metaphor!pstevens
   Metaphor Computer Systems           pstevens@metaphor.com
   Mountain View, CA
From: pebly@vnet.ibm.com (Bob Pebly)
Date: Tue, 8 Sep 92 08:47:05 EDT
Newsgroups: comp.os.os2.programmer
Subject: Re: Help: Kernel Debugger
Reply-To: pebly@vnet.ibm.com
Organization: IBM Industrial Sector Division, Boca Raton, FL
News-Software: UReply 3.0

In <1992Sep7.145724.22530@hns.com> Pat O'Neil writes:
>Anyone have any experience with the OS/2/2.0 Debug Kernel?  I have installed
>it and can't get it to respond to an async terminal on COM1.
>(remainder deleted)

Does your system have a second COM port?  COM2 is the default port for
the kernel debugger.  If there is no COM2, the debugger checks for COM1
and then any other COM port address in the ROM data area.

Bob Pebly

Disclaimer: This posting represents the poster's view, not those of IBM.

Newsgroups: comp.os.os2.programmer
Newsgroups: comp.os.os2.programmer
Subject: Is ibm uk still in the st
Date: Tue, 08 Sep 1992 19:14:00 +1000

LIUYU>It may require **intimate** knowledge for YOU to understand Herc hardware!
LIUYU>I programmed for Herc. It's easier than CGA. So don't tell me I don't know
LIUYU>my stuff!

So go ahead and write the goddamn driver!

LIUYU>As I said before, let's drop this subject. I'm getting too tired of
explaining. LIUYU>Some just don't have open minds to read my point. Others will
talk about some LIUYU>thing that has nothing to do with my point. Just too
tired....

Super. The 'let me have the last word and then recommend that the thread be
dropped' gambit. Highly original - NOT!

Let's talk dollars and sense here for  moment, chum, so listen up.

THERE IS NO MONEY IN SUPPORT FOR HERCULES UNDER OS/2 2.0!

Just like there is no money in support for the Professional Graphics Adapter, or
for the Perstor hard disk controller, or for virtual CP/M sessions.

Folk who do not have the $$$ to invest in current technology are also unlikely
to have the $$$ to promote the development of OS/2 by investing in OS/2
application software. ___
 * MR/2 1.1 NR * If this were an actual tagline, it would be funny.

 * Origin: Custom Programming BBS - Node 2 (3:632/341)
From: claude@trc.mew.mei.co.jp (Claude Huss)
Newsgroups: comp.os.os2.programmer,comp.os.os2.misc.comp.os.os2
Subject: OS/2 icons to Windows format
Date: 8 Sep 92 04:05:28 GMT
Distribution: comp
Organization: Matsushita Electric Works Ltd., Tokyo, Japan.


Does anyone know how to convert OS/2 Icons to Windows format?

Thank you in advance,

--
+----------------------+-----------------------------------------------------+
| Claude Huss          | Matsushita Electric Works, Ltd. Tokyo Research Labs.|
| Networking Engineer  | Mita 5-13-2, Minato-Ku, Tokyo 108, JAPAN            |
|                      | Phone: +81-3-3452-4941 Fax: +81-3-3451-0793         |
+----------------------+-----------------------------------------------------+
| Disclaimer:"Any comments for my company > /dev/null"                       |
+----------------------------------------------------------------------------+
             Gaijin Touroku Card: Don't leave home without it!
Xref: sparky comp.os.os2.programmer:4941 comp.os.os2.misc:30022 comp.os.os2.apps:6134
From: dic5340@hertz.njit.edu (David Charlap)
Newsgroups: comp.os.os2.programmer
Subject: Re: gcc 2.1, gcc 2.2.2, emx confusion
Date: 9 Sep 92 13:06:57 GMT
Organization: New Jersey Institute of Technology, Newark, N.J.

In article <18gvm4INNrou@usenet.INS.CWRU.Edu> helmick@ces.cwru.edu (Paul Helmick) writes:
>i am currently trying to setup the 32-bit GNU C++ environment to run under
>OS/2 2.0. i have been looking at the various files at hobbes.nmsu.edu
>and am thoroughly confused. which files do i need to setup emx with the
>ability to compile C++ programs? i downloaded gnudev.zoo but it was
>missing the C++ headers needed to compile C++ programs. should i also
>install gcc 2.1 or gcc 2.2.2? any help in this matter would be GREATLY
>appreciated.

You're getting the two packages confused.  Gcc/2 2.2.2 does not
require EMX.  Just un-zoo the archives from the same place with the
"x" extract option.  It'll create all the directories you need and
place the files in them.  You should wind up with something like this:

/gnu
/gnu/bin
/gnu/gcc-include   ...
/gnu/g++-include   ...
/gnu/os2-include   ...
/gnu/lib
/gnu/doc

Once all the archives are extracted, read all the documentation.
There isn't much.  It'll tell you about four or five environment
variables to set.  Insert them in your config.sys file.  Note the
direction of the slashes, some paths use unix-style forward-slashes
for directory separators.  Others use DOS/OS2-style back-slashes.  I
think these are the necessary variables to set:

LIB=
INCLUDE=
PATH=
C_INCLUDE_PATH=
CPLUS_INCLUDE_PATH=
TEMPDIR=

There may be one or two more.

EMX/GCC is a different package.  I don't know about it, so I can't
give you installation instructions, but I do know that a file called
emx.dll must be in a directory on your LIBPATH in order for it to run.
If you installed any emx-based app (like gnu-emacs), then this dll is
already present.
-- 
   |)  David Charlap           "TELEPHONE, n.  An Invention of the devil which
  /|_  dic5340@hertz.njit.edu   abrogates some of the advantages of making a
 ((|,)                          disagreeable person keep his distance."
  ~|~                              --- Ambrose Bierce, The Devil's Dictionary
Newsgroups: comp.os.os2.programmer,comp.os.os2.advocacy,comp.os.ms-windows.advocacy,comp.os.ms-windows.programmer.win32
From: oleg@watson.ibm.com (Oleg Vishnepolsky)
Subject: Re: OS/2 vs NT features list, Revision 1.8
Date: Mon, 14 Sep 1992 15:33:38 GMT
News-Software: IBM OS/2 PM RN (NR/2) v0.12 by O. Vishnepolsky and R. Rogers
Reply-To: oleg@watson.ibm.com (Oleg Vishnepolsky)
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: IBM T.J. Watson Research Center

In  <1992Sep7.172652.1686@hellgate.utah.edu>  brian%jaguar.cs.utah.edu@cs.utah.edu (Brian Sturgill) writes:
> ...
>
> Features in the pre-beta Windows NT but not in OS/2 2.0 GA
>  ...
>
>         Networking
>                 TCP/IP
>                 Peer-peer file and printer sharing.
>                 Ability to support multiple vendors as transports
>                         w/common admin.
>                 Good network admin facilities.
>                 SNMP
> #               Berkeley sockets (WinSock compliant).
>                 Named pipes.
>                         (Both NT and OS/2 GA have non-networked ones.)
>                 Event logging.
>                         (Both NT and OS/2 GA have this in non-networked form.)
> ...
>
> Corrections of grammar, spelling, etc are welcomed.
>
> Brian

I do not understand why you list TCP/IP, SNMP and sockets not being in
OS/2 2.0 GA. True, these are optional packages that one can buy either
from IBM or third party vendors, but what's the NT's advantage here ?

Oleg
Newsgroups: comp.os.os2.programmer
From: caliaro@avalon.physik.unizh.ch (Aurelio Caliaro)
Subject: Trident VGA-256
Organization: University of Zurich, Department of Computer Science
X-Newsreader: Tin 1.1 PL4
Date: Fri, 11 Sep 1992 09:40:20 GMT


The Trident 640x480x256 colors only works with 1 MB of VGA memory. The README-
File, that was distributed with it, said that Trident is working on it, so
that it can work with 512k. Does someone know if that problem is already
solved and if the new driver was published, or if it is better to buy those
512k to add onto the card?
How much does such a 512k-chip cost?

    caliaro@amiga.physik.unizh.ch
From: dic5340@hertz.njit.edu (David Charlap)
Newsgroups: comp.os.os2.programmer
Subject: Re: gcc/os2 docs
Date: 11 Sep 92 19:21:02 GMT
Organization: New Jersey Institute of Technology, Newark, N.J.

In article <grendel.716224537@cygnus.cis.ksu.edu.cis.ksu.edu> grendel@cis.ksu.edu (Stephen Spencer) writes:
>What format are the gcc docs in for OS/2?  IOW, how can I convert them to 
>ASCII again :)

The docs are in TexInfo format.  I believe you can download them in
ASCII format as well.  Here's what you do with them:

1) You can print them.  Using a TeX formatting package (like emTeX for
   OS/2) and the Texinfo header file, you can convert these to a
   device-independant (.dvi) file.  This can then be converted into a
   PostScript (.PS) document or some other printer-specific format.

2) You can make a hypertext document from them.  Using Gnu-Emacs (and
   the texinfo-format-buffer command) or the MakeInfo utility (has
   this been ported to OS/2?), you can produce .info files that the
   Gnu-Emacs info system can use.

I did method 2, as I prefer on-line help to using lots of my printer
paper. 

-- 
   |)  David Charlap           "LECTURER, n.  One with his hand in your pocket,
  /|_  dic5340@hertz.njit.edu   his tongue in your ear, and his faith in your
 ((|,)                          patience."
  ~|~                              --- Ambrose Bierce, The Devil's Dictionary
Newsgroups: comp.os.os2.programmer,comp.os.os2.misc,comp.os.os2.advocacy
From: orville%weyrich@tnet.com (Orville R. Weyrich)
Subject: Re: Missing documentation - KBD, MOU and VIO
Reply-To: tnet.com!weyrich!orville
Organization: Weyrich Computer Consulting
Date: Thu, 10 Sep 92 08:01:11 GMT

In article <9209080106.AA19548@ucbvax.Berkeley.EDU> KENKAHN@PKSMRVM.VNET.IBM.COM ("Kenneth A. Kahn") writes:
>Organization: Staff of IBM Fellow - IBM Personal/370
>Disclaimer: This posting represents the poster's views, not those of IBM
>News-Software: UReply 3.0
>X-X-From: KENKAHN@PKSMRVM.VNET.IBM.COM (Ken Kahn)
>References: <715895337snx@sugs.tware.com>
>
>In <715895337snx@sugs.tware.com> Hale Landis writes:
>>Has anyone found the (missing) documentation for the KBD, MOU and
>>VIO functions in the OS/2 2.0 manuals?
>>
>
>These APIs are not documented in any 2.0 technical manual because they are
>not supported in 32-bit mode.  They are supported in 16-bit mode which is
>what thunking is all about.  This is mentioned in one or two of the ToolKit
>Manuals for 2.0 but I forget which right now.  The actual description and
>syntax for these APis however must be looked up in the 1.x technical manuals.

That may be fine for long-time OS/2 developers, but what do new-comers to
OS/2 do? Are the 1.x manuals still in print? If so, what is the relevant
ordering information? Or we just SOL?

orville

--------------------------------------       **********************************
Orville R. Weyrich, Jr.                          Weyrich Computer Consulting
Certified Data Processor                       POB 5782, Scottsdale, AZ 85261
Certified Systems Professional                      Voice: (602) 391-0821
Certified Computer Programmer                Internet: orville%weyrich@tnet.com
--------------------------------------       **********************************
From: rjo@panix.com (Robert Olivier)
Newsgroups: comp.os.os2.programmer
Subject: Re: Help: Kernel Debugger
Date: 9 Sep 92 01:34:35 GMT
Organization: PANIX Public Access Unix, NYC

In <1992Sep8.180216.3718@javelin.sim.es.com> rpack@javelin.sim.es.com (Rick Pack) writes:

>oneil@hns.com (Pat O'Neil) writes:

>>Anyone have any experience with the OS/2/2.0 Debug Kernel?  I have installed
>>it and can't get it to respond to an async terminal on COM1.  I've
>>read the directions pretty carefully and done everything they say, including:
>>
>>...... stuff deleted
>>
>>I would greatly appreciate any help.
>>
>>Pat O'Neil
>>Hughes Network Systems
>>Germantown, Md.

>  Pat,
>  I had terrible trouble with the debug kernel when I first tried to get
>it to work.  My system would crash after about 30 seconds of use.  Just
>getting it to boot was iffy.  I then started debugging with just printf
>statements, using the original kernal, figuring that the debugging kernal
>was buggy.
>  Just last week, I realized that the debugging kernal is NOT necessary, as
>there is a great debugger included in the c-set2 package that runs under
>PM and will debug PM programs.  It's called IPMD.  I STILL do not know
>what the purpose of the debugging kernal is, as IPMD works just fine without
>it, and there is none of this async terminal/serial port stuff.
>  The install documentation for workset/2 never mentions IPMD, just the debug
>kernal, which leads you to believe that it is your only option.

The debug kernel is needed for debugging device drivers or applications
that somehow cause a GP or page fault while the kernel is executing.

The PM debugger can only debug code that is running in ring 3.

-- 
Robert J. Olivier

rjo@panix.com
From: bjaspan@athena.mit.edu (Barry Jaspan)
Newsgroups: comp.os.os2.programmer
Subject: Re: OS/2 TCP/IP socket programming library for GNU/2
Date: 9 Sep 92 16:28:44 GMT
Organization: Massachusetts Institute of Technology

In article <pclank01.715981011@starbase.spd.louisville.edu>, pclank01@rigel.spd.louisville.edu (Pat C. Lankswert) writes:
|> What is the status of the programming library for TCP/IP sockets
|> with the IBM TCP/IP package?

I haven't been able to work on it recently.

When I last touched it, I had the basic socket functions (socket, connect,
bind, accept, listen, recv, recvfrom, send, sendto, close) and a few netdb
functions (gethostby{name,addr}) working.  In this case, "working" means I
could compile a program with gcc and link it with my tcp32.dll and everything
would work.

I also began integrating my socket library into gcc/2's C library, so that
read(), write(), and close() will work on stream sockets.  This also seemed to
work, but certainly wasn't complete.

I do not guarantee that the approach I am using will work in all cases; my
simple test program works but that doesn't really prove anything.

I will try to get some kind of release together soon.  I realize that a lot of
people want this thing and that I've been promising it for a while.  I think I
have just about used up my excuse of personal problems.. :-)

-- 
Barry Jaspan, bjaspan@mit.edu
Newsgroups: comp.os.os2.programmer
From: bbs.dennis@tsoft.sf-bay.org (Dennis Yelle)
Subject: Does kbhit() work for anyone else?
Organization: The TSoft BBS and Public Access Unix, +1 415 969 8238
Date: Thu, 10 Sep 1992 02:28:13 GMT

I can't get kbhit() to return anything but a 0.
No matter how many keys I type.
 
Also, if I do a getch() and then type a Ctrl-C, the
process hangs.

Has anyone gotten either of these two functions to
work properly under OS/2 2.0?

Does anyone have any other suggestions about how to deal
with the keyboard successfully in C under OS/2 2.0?

--
Dennis Yelle (bbs.dennis@tsoft.sf-bay.org)
Newsgroups: comp.os.os2.programmer
From: tcf9033@venus.tamu.edu (FREY, TONY C)
Subject: C Developers Workset/2 for sale - help
News-Software: VAX/VMS VNEWS 1.41    
Organization: Texas A&M University, Academic Computing Services
Date: Sun, 13 Sep 1992 19:30:00 GMT


 I'm in dire need of cash for this fall semester and can't afford the
C Developers Workset/2 I bought last month. I'll pay shipping (UPS) and
I'd like to get $250. Reply by e-mail TCF9033@venus.tamu.edu or call me
at 409-696-5701. Thanks.
From: fred@labtech.com (Fred Putnam)
Newsgroups: comp.os.os2.programmer
Subject: Multimedia developer's information or kit?
Keywords: OS/2 multimedia
Date: 14 Sep 92 19:53:04 GMT
Distribution: comp

dissapointed, because this is a tool for end users, and has nothing
at all for developers.  What do I have to order to get the developer's
kit for multimedia?

Fred Putnam, fred@labtech.com, 9/14/92

Xref: sparky comp.os.os2.programmer:4815 alt.bbs:5779 comp.bbs.misc:902
Newsgroups: comp.os.os2.programmer,alt.bbs,comp.bbs.misc
Subject: Passing control of COMM from OS/2 to DOS window.
From: mgjones@miavx1.acs.muohio.edu (Mike 'Felix' Jones)
Date: 8 Sep 92 17:47:21 -0500
Organization: Miami Computer Users Group

I heard this mentioned in a previous post in one of the BBS
newsgroups, but I didn't see any followups.  (it was also one of the
things I was looking for in an OS/2 bbs).

Is it possible for an OS/2 program (for example, a BBS) to pass
control of the COMM port to a DOS program (for example, a DOS door
game) without interuption of service?

If so, has it been done with a BBS yet?
or, how can it be done so I could write my own door driver?

---
Mike "Felix" Jones ---[ President of Miami Computer Users' Group ]---
{} School: mgjones@apsvax.aps.muohio.edu <--- Preferred            {}
{} Work  : mjones@sba-laws.sba.muohio.edu                          {}
{} Home  : mgjones@sacder.nshore.org (UUCP - slower response time) {}
Newsgroups: comp.os.os2.programmer,comp.os.os2.advocacy,comp.os.ms-windows.advocacy,comp.os.ms-windows.programmer.win32
From: landis@sugs.tware.com (Hale Landis)
Newsgroups: comp.os.os2.programmer
Subject: Missing documentation - KBD, MOU and VIO
Date: 8 Sep 92 00:02:17 GMT
Organization: SUGS

Has anyone found the (missing) documentation for the KBD, MOU and
VIO functions in the OS/2 2.0 manuals?

Hello IBMer's: Do any of you know what became of this documentation?

It is plainly clear that OS/2 2.0 supports these functions and it
supports them for both 1.x and 2.0 applications.  Based on what I
have read, something called 'thunking' is used to convert 16:32
addresses (aka flat memory model) to 16:16 addresses (1.x
addresses) so that 2.0 applications can use existing 1.x DLL's.

So where is this really documented?  I read about it in one of
those after-market books about OS/2 2.0 you find in the
bookstores.

Again, IBMer's: what gives here?

If you have the IBM C compiler and the example programs, look at
the WORMS program.  It demostrates how a 2.0 program calls the
VIO, MOU, etc, functions.

Now for the real reason for this posting:  I notice that a number
of people are posting questions about this and no one seems to
have the definitive answer:  an IBM manual to refer to!

IBMer's:  You really didn't overlook these important functions
when creating the OS/2 2.0 manuals, did you?

--------------------------------------------
Hale Landis                  Ph 408-423-4017
tware!sugs!landis -or- landis@sugs.tware.com
--------------------------------------------
Newsgroups: comp.os.os2.programmer
From: rmy@pyuxf.uucp (Robert Yaeger)
Subject: winos2, toolhelp stacktrace problem.
Organization: bcr.
Date: Tue, 15 Sep 92 14:35:16 GMT

Hi,


I'm having a problem with toolhelp.dll StackTrace routines under OS/2.
The STACKENTRY segment field isn't being filled in correctly.  The code
runs fine under windows. The segment field is used to lookup the symbol
name owning that stack frame in the sym file.  As we are moving our
development to run under OS/2 it'd be nice if our debugging stuff still
worked!

-Bob