SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 22 | March | 2006 ]

>> Next Message >>


Date: Wed, 22 Mar 2006 09:40:55 PST8
From: Tom Brown <thombrown@san.rr.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: PMView crash

Content Type: text/plain

Steven Levine wrote:
> In <4420EF2B.4040707@san.rr.com>, on 03/21/06
> at 10:30 PM, Tom Brown said:
>
>
>>03-21-2006 15:59:13 SYS2070 PID 0072 TID 0001 Slot 00a8
>>E:\TOOLS\PMVIEW\PMVIEW.EXE
>>PMVIEW
>>193
>
>
> If this is all you get, this is typically a DLL mismatch. You might try
> pmdll and see what it says. Use the Test Load DLLs option and see what
> shows up red. The latest beta is at
>
> <http://home.earthlink.net/~steve53/betas>

OK, ran it in the pmview directory with Test Load option. I get pmview
at the upper left with it's directory tree underneath, all grayed out.
Nothing in red.

Peter says:

***************
PMView doesn't need any own DLLs to start (PMV30HTK is only needed for hot
key screen capturing. That's the only time it will be loaded). I'm
talking about missing OS/2 DLLs (or wrong versions) that generate the
SYS2070. But it's difficult to say... It could be something completely
different.

It's totally weird that v3.12 works and v3.24 doesn't. It's the EXACT same
compiler & code. (Now if v3.05 worked and v3.10 didn't, it would be
another story, as a compiler switch was made in v3.10)

Try:

pmview /ini=temp.ini /log=pmview.log
***************

Tried that. Same story, same entry in popuplog.os2, no files created.

One other thing alluded to above, pmview v. 3.12 on another drive works
fine, .ini and .log files created as expected.

I'm going to play with re-installing. Will keep you posted.

Thanks!

--
Tom Brown, Catherder
thombrown at san dot rr dot com
Member SCOUG, V.O.I.C.E. & SDAA

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


>> Next Message >>

Return to [ 22 | March | 2006 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.