OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Utilities => Topic started by: Martin Vieregg on August 25, 2018, 12:31:36 am
-
I have downloaded a new version of my DO.EXE commandline utility:
DO for OS/2 archive file (http://www.hypermake.de/archive/do-os2.zip)
DO for Windows (32 bit) archive file (http://www.hypermake.de/archive/do-win.zip)
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.
-
Meanwhile, I've uploaded the MacOS and Linux version of DO:
DO for Linux 64 bit archive file (http://www.hypermake.de/archive/do-linux.zip)
DO for MacOS X archive file (http://www.hypermake.de/archive/do-macos.zip)
-
{0}[k:\] do
Command only valid in batch file "DO"
Is DO.EXE a wise name for your utility?
-
[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):
/* Number of column headers*/
format=4
'DO format
CALL CharOut '','---------'
END
-
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
-
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.
-
you?
-
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.
-
do is used in REXX and cmd scripts. It's really a bad idea to name a program the same.
-
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?
go delete
go rebuild
go copy
go touch
-
What about GO?
A good, classic process killer! ;)
http://hobbes.nmsu.edu/download/pub/os2/util/process/go_15.zip (http://hobbes.nmsu.edu/download/pub/os2/util/process/go_15.zip)
-
What about GO?
A good, classic process killer! ;)
http://hobbes.nmsu.edu/download/pub/os2/util/process/go_15.zip (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.
-
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 (http://hobbes.nmsu.edu/h-search.php?key=top214&pushbutton=Search)). 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.
-
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. :-)
-
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.
-
Is there really a conflict with the REXX "do" ?
As such not, but you may be one typo or error away from a possible disaster. On top of possible CMD.EXE processing mistakes, where DO is also a keyword: for %a in (*.TXT) do (do sort %a).
I'd suggest a new, unique name indeed, without suggesting a new name. For one because DO.EXE isn't an innocent tool which just prints a blank line.
FORMAT.COM/FORMAT.EXE and Rexx' Format() cannot be compared with DO. Format() is a function, which requires more than one typo or error to format a drive (if we ignore the "ARE YOU SURE?" dialog of the external OS command). DO is a different category, and a new command of your DO may make it worse.
I'm also not 100% sure, without testing, what the expected result of ...
/*TEST.CMD */; DO
... is. A syntax error of Rexx, or your DO explaining how it works.
IIRC I have DO in my path, but the arguments against such a name are valid and are more than trivial and theoretical, and nobody knows which commands may be introduced by you in the future. Despite of the fact that DO is a good name for what it is doing and how it works, you could consider a creative new name. DO is taken by CMD.EXE, and Rexx.
-
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.
I know you are trying to make it simple. Later post indicate this is not so easy to do. How about "makeitso"
makeitso delete
makeitso rebuild
makeitso copy
makeitso touch
-
I know you are trying to make it simple. Later post indicate this is not so easy to do. How about "makeitso"
makeitso delete
makeitso rebuild
makeitso copy
makeitso touch
Or ENGAGE.EXE:
engage delete
engage rebuild
engage copy
engage touch
-
Hi to all! I'm new to os2world... and welcome to myself ;D
After many years finally I have some time for my dream: a workstation with a daily functional os/2.
My first warp pc was version 2.1. Then I bought warp 3 but in that years also starting my actual job such as Graphics Technician.
So my first operating environment is Apple Mac.
I follow this forum from a few months when I contacted Martin Iturbide for some information about DBExpert. But it is another story...
I take this opportunity to propose my opinion about DO.EXE.
I think was possible to name it LDO.EXE, like "Let's DO":
> ldo delete
> ldo copy
Cheers to you all and Happy Warping!
-
LETS.EXE, PLZ.EXE, ... :P
-
I think the conflict only occurs on Unix systems. What about uppercase DO or Do ?
-
I've updated the archive files of DO to 2.00a:
http://www.hypermake.com/english/do.html (http://www.hypermake.com/english/do.html)
german language with a short explanation how to use (the readme.txt is only in english)
http://www.hypermake.de/deutsch/do.html (http://www.hypermake.de/deutsch/do.html)
I have decided to write DO in uppercase letters on Unix systems. This seems to work fine.