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 [ 17 | February | 2006 ]

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


Date: Fri, 17 Feb 2006 11:42:20 PST8
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: How list required DLLs ?

Content Type: text/plain

Steven Levine wrote:
>
> In <43F2D602.1B6E@peterskye.com>, on 02/14/06
> at 11:19 PM, Peter Skye said:
>
> >What is the utility which lists an exe's dll requirements? I can't get
> >ffst.exe to run -- it starts and immediately ends with no message,
>
> Did you check popuplog.os2?

Yes. No entries.

> >and in
> >the past I've seen this happen with a missing DLL.
>
> Since you are a command line guy, I am assuming you tried to start if from
> the command line. If so, a missing DLL will always generate a message.
> If you try to start it from a Program object, you will get the setting
> notebook, which can be misleading. Ask Tom.

Good info, thanks. I tried it both ways and got no message or setting
notebook so I guess my DLLs are fine.

> >Or
> >am I "looking in the wrong spot" and do I have to delete a possibly
> >corrupted probe file somewhere?
>
> That's the more likely cause. It might be sufficient to run syslogpm and
> clear the logs. Worst case you might need to run ffstconf. You should
> have Desktop objects for both of these.

There's my mistake. I didn't run syslog.exe. Thank you.

- Peter

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

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

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


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

Return to [ 17 | February | 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.