DO.EXE new version commandline utility 1.99

[Martin Vieregg]

I have downloaded a new version of my DO.EXE commandline utility:

DO for OS/2 archive file
DO for Windows (32 bit) archive file

DO.EXE is a swiss army knife command line enhancement. Since the last published version 1.46, I have added a handful new functions.

- DO SHOWCLONE, KILLCLONE: find and delete clone files
- DO EVERY: time-related executing of batch files, .e.g. every 3 days
- DO RENAME

and, most important:

- DO COPY
in variants. DO COPY shows the copied file names, DO PCOPY shows a progress bar. (With copy or xcopy, you won't get feedback for a long time when copying big files to slow drives like USB sticks.)
It is faster than XCOPY, because it can handle several file exensions simulateously. It collects all files before beginning with copying.
DO COPY can handle files larger than 4 GB on FAT32 drives. (There really seems to be no program which fits the problem.)

Please report bugs. 1.99 is a beta version, but it seems to work fine.
Please read the docu. DO.EXE can cause harm with only few input. By default, DO.EXE includes subdirectories.

A Linux and Macintosh version will follow. DO.EXE ist written with WDsibyl, and the other platforms with Freepascal-Lazarus.

[Martin Vieregg]

Meanwhile, I've uploaded the MacOS and Linux version of DO:

DO for Linux 64 bit archive file
DO for MacOS X archive file

[Neil Waldhauer]

Code: [Select]

{0}[k:\] do
Command only valid in batch file "DO"

Is DO.EXE a wise name for your utility?

[xynixme]

[quoteIs DO.EXE a wise name for your utility?[/quote]
Possibly not in an environment with an embedded Classis Rexx interpreter or CMD.EXE's FOR, to answer that question.

The user may be one typo anway from formatting a drive (virtual sample):

Code: [Select]

/* Number of column headers*/
format=4

'DO format
    CALL CharOut '','---------'
END

[Dave Yeo]

The readme does touch on this and suggests renaming it and on Linux and OSX suggests renaming to doo, which sounds like what the dog leaves on the lawn
Perhaps doit.exe would be a better name

[Martin Vieregg]

good to hear that doo has already another meaning...

doit is not so useful, because the parameters are verbs

do delete
do rebuild
do copy
do touch

Perhaps, anyone else has got a good idea.

[Ian B Manners]

you?

[Martin Vieregg]

Now I've found a quite simple solution:

DO in capital letters, because Unix is case-sensitive. On OS/2 and Windows, you can countinue typing "do" in lowercase letters.

[Andi B.]

do is used in REXX and cmd scripts. It's really a bad idea to name a program the same.

[RickCHodgin]

Now I've found a quite simple solution:

DO in capital letters, because Unix is case-sensitive. On OS/2 and Windows, you can countinue typing "do" in lowercase letters.

What about GO?

Code: [Select]

go delete
go rebuild
go copy
go touch

[xynixme]

What about GO?

A good, classic process killer!

http://hobbes.nmsu.edu/download/pub/os2/util/process/go_15.zip

[RickCHodgin]

What about GO?

A good, classic process killer!

http://hobbes.nmsu.edu/download/pub/os2/util/process/go_15.zip

Nice utility.  But, an odd name for it.  I would've called it TASKMAN.EXE or something.

BTW, I could've used that utility the other day. :-)  During development I had an unresponsive process I couldn't kill.

[xynixme]

BTW, I could've used that utility the other day. :-)  During development I had an unresponsive process I couldn't kill.

Nowadays TOP is perhaps a weapon of choice installed by default since eCS 2.x (and available as an informal update for eCS 1.x). An installed GO.EXE may be as old as dial-up internet, to download something and to disconnect A.S.A.P. by killing the dialer. Nevertheless GO.EXE is an existing name of an OS/2 utility.

[RickCHodgin]

An installed GO.EXE may be as old as dial-up internet, to download something and to disconnect A.S.A.P. by killing the dialer. Nevertheless GO.EXE is an existing name of an OS/2 utility.

Given as it's so old, probably nobody would mind renaming the 1995 GO.EXE to TASKMAN.EXE and allowing Martin Vieregg to use GO.EXE for his new app.  He could also call it UGO.EXE for Utility-GO. :-)  Or, go all out and call it YUGO.EXE. :-)

[Martin Vieregg]

I also use GO.EXE. A really nice utility.

Is there really a conflict with the REXX "do" ? Because in Rexx scripts, you have to write normal commandline commands in quotation marks and DO is part of the language (not in quotation marks). I have got DO.EXE in the path statement for years and all Rexx scripts work fine.