Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Frank Slootweg <this@ddress.is.invalid>
Newsgroups: alt.comp.os.windows-11,alt.comp.os.windows-10
Subject: Re: what is the fastest command line copy?
Date: 2 Apr 2025 17:36:51 GMT
Organization: NOYB
Lines: 66
Message-ID: <vsk3js.14fo.1@ID-201911.user.individual.net>
References: <vsa1o9$2hf7l$1@dont-email.me> <vsctt2$1c3kf$1@paganini.bofh.team> <050kujpf36f33i4hspur5jg286m5r7fvn3@4ax.com> <vse1av$8pa5$1@dont-email.me> <vse6e0$e3ib$1@dont-email.me> <vsea99$i2o2$1@dont-email.me> <ljsmujdighbuvcltfh5kihbmnqaqqohern@4ax.com> <vsgpfb$36vg6$1@dont-email.me> <nanpujlogu6350309ttemlh3u4u3798698@4ax.com> <vsiro1$1brfi$1@dont-email.me> <vsjiap.e54.1@ID-201911.user.individual.net> <vsjnrh$28nan$1@dont-email.me>
X-Trace: individual.net GWfh9wDXAnx+VWN3tPHebwY/C7pSUH43Nq79qmjn9CHdAKnBj7
X-Orig-Path: not-for-mail
Cancel-Lock: sha1:p8YwaUpV96qhE7RWgAI9pvHYViI= sha256:H480Ajii5do9dXlKtL5LmZmNWLf/ltEbeZNeM9wmf9s=
User-Agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2
Xref: csiph.com alt.comp.os.windows-11:18203 alt.comp.os.windows-10:183188

Paul <nospam@needed.invalid> wrote:
> On Wed, 4/2/2025 8:41 AM, Frank Slootweg wrote:
> > Paul <nospam@needed.invalid> wrote:
> >> On Wed, 4/2/2025 2:50 AM, Steve Hayes wrote:
[...]
> >>> I'm not sure what you're saying here. 
> >>>
> >>> I have four batch files:
> >>>
> >>> dsk2flsh.bat
> >>> flsh2lap.bat
> >>> lap2flsh.bat
> >>> flsh2dsk.bat
> >>>
> >>> I only have to remember the exact syntax when I make the batch files,
> >>> and after that I I have to remember is the name of the batch file. 
> >>
> >> When those .bat files copy things, do you check
> >> the "error number" to see if the copy
> >> was successful ?
> > 
> >   Note that (this part of) the discussion is for .bat files which mainly
> > contain a single 'complicated' command, so the user does not have to
> > remember the complicated command, but just the name of hir .bat file.
> > 
> >   For *such* a .bat file, if the command fails, it will give the same
> > error(s) as if the command was typed manually, so there's no need for
> > checking the error number.
> > 
> >> Scripting is "programming", and the same things I would
> >> have to check when writing a C language program, those
> >> are still issues when running a (so-called OS) copy program.
> > 
> >   Yes, scripting - i.e. also .bat files - is "programming", but for
> > simple .bat files, such are under discussion here, there's no need to
> > make things more complicated than just putting the 'complicated' command
> > in a .bat file.
> > 
> > [...]
> > 
> 
> Well, someone is expressing an interest in scripting, and I don't
> want them picking up any bad habits.

  Fair enough. Just as long we agree that there's nothing wrong with
Steve's method.

> I use a different approach than Steve, for one-liners. I have
> a separate notes file in the backup area, and all the one-liners
> are copy/pasted in there. Copy a line from that file, into a
> separate Notepad, edit the details as required, then paste it raw
> into the Terminal window, and then all the side effects are visible
> on the screen.

  Again, fair enough, different strokes for different folks.

  FWIW, if the task and parameters are static, I use a .bat file instead
of copy and paste.

  And my 'one-liners' are two or more lines, because they start with
'@echo off'! :-)

> It's like code inspection, doing it that way. Anything moving data
> around, deserves extra eyeballs.

  "code inspection"!? *I* wrote it, so it's purrfect!