SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Wed, 22 Mar 2006 11:24:04 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

I tried:
1. Deleted .ini file information via Unimaint.
2. Deleted directory structure via WPS.
3. Deleted Warpin database entry.
4. Ran Checkini .
5. Rebooted.
6. Re-installed PMView Pro from pmview324os2fullenu.exe (6,145,596
bytes). The install via Warpin ran "successfully" according to Warpin.
7. Running PMView crashes just as before.
8. All other items in the PMView Pro folder work as expected.

Is there any way to trace what is happening? I have never done this
before, so it would be a "learning experience" for me! :-)

Thanks!

Tom Brown wrote:
> 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".

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

Return to [ 22 | March | 2006 ]

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.