SCOUG-HELP Mailing List Archives

<< Previous Message <<

Date:	Fri, 8 Oct 2004 22:16:53 PDT7
From:	Martin Rosenfeld <rosenfeldmj@comcast.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Problem with CMD file

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven,

If I use the Program Template and make a file object that basically has
as its path and file name, as soon as I try to
run it, without apparent disk activity, I get the following blue and
gray error box:

=========================================================
BAK-MOZ

Cannot start V:\BAK-MOZ\BAK-MOZ.CMD

This could be caused by one or more of the
following reasons:

1. The oath for the program is incorrect/
2. The file is not an eCS, OS/2, DOS or Windows Program
3. Not enough memory available to run the program.
4. The file is locked by another process.
5. A component DLL is missing.

Do you wish to modify the properties for the object?

PROPERTIES CANCEL HELP
=========================================================

But, this program object does run:
File name and path: V:\BAK-MOZ\DSYNC.EXE
Parameters: -v -i

I don't understand why I can't run a CMD file from a program object. Did
I use the wrong template? Is there a template that allows a CMD to run?

Martin Rosenfeld

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

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
"rollin@scoug.com".

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

Return to [ 08 | October | 2004 ]

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.