SCOUG-HELP Mailing List Archives

<< Previous Message <<

Date:	Sun, 13 Jul 2003 23:32:44 PDT7
From:	jack.huffman@worldnet.att.net
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: Need help with XCOMP

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

In <3F11B7E5.370F51E8@pacbell.net>, on 07/13/2003
at 11:48 AM, "J. R. Fox" said:

>>Jack Huffman wrote:

>> Thanks for the encouraging comment about Roman Stangl.
>>
>> I am surprised that no one thought, when XCopy was written, to require it
>> to stop on error/problem or create an error log.

>Actually, I've sometimes had a problem where encountering an error causes
>XCOMP to stop dead in its tracks, most often when that session is not the
>one that has focus.

Jordan,

I used the /log switch on the command line. You saw what that file
contained:

XCOMP118: Error SYS3 returned by DosFindFirst() at Line 1130

XCOMP005: 1 directory(ies) could not be opened. This may be caused by non
accessible directories due to ACLs (e.g. on HPFS386), an
incorrect/outdated file system driver (e.g CD-ROM) or file system
corruption. XCOMP007: 0 file(s) compared successfully, 0 file(s) compared
totally.

Apparently XComp performed 1129 operations (probably reads of the drive
being copied c:) successfully but stopped on the next one.

Would the log file created by your batch file list these 1130 operations?
I don't know how that is possible but then many things happen that I do
not expect. If it will list them, please send me a copy.

Jack

I usually run XCOMP from a batch file, the command
>for which redirects the output to a designated logfile. Roman already
>has improved the program, up to the present version, but I feel the major
>remaining area for further improvement (assuming the strictly command
>line interface is retained) has to be in error handling / reporting.
>There are probably also some things it runs into that could optionally be
>ignored. I hope he will have the opportunity to continue developing it,
>as it is already a fine tool.

>Jordan

>=====================================================

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

>=====================================================

--
-----------------------------------------------------------
jack.huffman@worldnet.att.net
-----------------------------------------------------------

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

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 [ 13 | July | 2003 ]

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.