Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Understanding COPY /J parameter

10 views
Skip to first unread message

JJ

unread,
Jun 17, 2012, 3:49:29 PM6/17/12
to
What does COPY /J parameter actually do?
I can't seem to figure it out the difference between normal COPY.

I thought it's actually a "resumable" copy incase the copy fails at the
middle of process. I tried copying a large ISO file using COPY /G /J so
that it took long enough for me to break it with CTRL-C. It stopped at the
middle at hasn't reach 50% yet. But when I repeat the command, it start at
0%.

Sjouke Burry

unread,
Jun 17, 2012, 10:48:59 PM6/17/12
to
JJ <jaejunks_at@_googlemail_dot._com> wrote in
news:XnsA0761CD6D3BE9ja...@0.0.0.54:
Did you mean copy /Y?
That tells the computer to not ask for Yes/No dialog, but to assume
Yes on all opreations, so it will overwrite files without asking.

Laurent Jumet

unread,
Jun 18, 2012, 1:26:48 AM6/18/12
to

Hello Sjouke !

Sjouke Burry <s@b> wrote:

>> What does COPY /J parameter actually do?
>> I can't seem to figure it out the difference between normal COPY.

In some cases, if you are copying a directory and it fails, you can resume at the already copied last file. I don't think you can resume inside a file.

--
Laurent Jumet - Point de Chat, Liège, BELGIUM
KeyID: 0xCFAF704C
[Restore address to laurent.jumet for e-mail reply.]

Klaus Meinhard

unread,
Jun 18, 2012, 3:23:36 AM6/18/12
to
>>> What does COPY /J parameter actually do?
>>> I can't seem to figure it out the difference between normal COPY.
>
> In some cases, if you are copying a directory and it fails, you
> can resume at the already copied last file. I don't think you can
> resume inside a file.

That's not what it says in HELP:

/J Copy the file in restartable mode. The copy
progress is tracked in the destination file in
case the copy fails. The copy can be restarted
by specifying the same source and destination
file names.

This may or may not be a bug or a badly formulated help entry. I
suggest you bring this up in the official support forum at
www.jpsoft.com


--
Best regards,

* Klaus Meinhard *
<www.4dos.info>





CRNG

unread,
Jun 18, 2012, 4:49:44 AM6/18/12
to
On Mon, 18 Jun 2012 09:23:36 +0200, "Klaus Meinhard"
<K_Mei...@gmx.de> wrote Re Re: Understanding COPY /J parameter:
They aren't much help there if you aren't useing the latest version
(v25678.1 ??). They just tell you to upgrade to the current version
of the month.

Klaus Meinhard

unread,
Jun 18, 2012, 5:05:11 AM6/18/12
to
"CRNG" <Sp...@uce.gov> schrieb im Newsbeitrag
news:smqtt7h74ru7giflq...@4ax.com...

>>This may or may not be a bug or a badly formulated help entry. I
>>suggest you bring this up in the official support forum at
>>www.jpsoft.com

> They aren't much help there if you aren't useing the latest version
> (v25678.1 ??). They just tell you to upgrade to the current version
> of the month.

I cannot confirm this. If you tell them the version you are actually
using, they may tell you to update the the latest build of that
version, because that's where the bug may have been fixed. There are
quite a few very knowledgeable users there that will try to help
regardless of your version.

JJ

unread,
Jun 18, 2012, 6:55:23 AM6/18/12
to
"Laurent Jumet" <1st_NAME...@skynet.be> wrote in
news:GED4FDEBC95@1st_NAME.Lst_NAME.skynet.be:

> In some cases, if you are copying a directory and it fails, you
> can resume at the already copied last file. I don't think you can
> resume inside a file.

I even just tried that. I copied the numeruous C:\WINDOWS\SYSTEM32\*.DLL
files so I have time to break it. Stopped it at D*.DLL. Repeated the
command, but it starts from A*.DLL again.

However, After I break a COPY comand, then typed: echo %?
It returns zero. Could it be that CTRL-C/BREAK doesn't affect /J
parameter?

JJ

unread,
Jun 18, 2012, 7:04:51 AM6/18/12
to
"Klaus Meinhard" <K_Mei...@gmx.de> wrote in news:a48b9cF350U1
@mid.individual.net:

> I cannot confirm this. If you tell them the version you are actually
> using, they may tell you to update the the latest build of that
> version, because that's where the bug may have been fixed. There are
> quite a few very knowledgeable users there that will try to help
> regardless of your version.

If it was a bug, how can it fails at the main part of that parameter
purpose?

I kind of think that the parameter help description is not explained
correctly.

What do you think of that parameter purpose when you read its help
description?

E. S. Fabian

unread,
Jun 18, 2012, 7:33:56 AM6/18/12
to
JJ:

| If it was a bug, how can it fails at the main part of that parameter
| purpose?
|
| I kind of think that the parameter help description is not explained
| correctly.
|
| What do you think of that parameter purpose when you read its help
| description?

Notice two points:
1/ HELP says "file", not "set of files". You can always use the /U option to
prevent copying a file more than once when you repeat a command.
2/ Intentionally breaking the copying process does not cause it to "fail".
If you copy from or to a removable disk, and it is removed in the middle of
the action, or you have a power failure, or - most common - if you're
copying across a communication link which fails, the /J is applicable.
--
Steve


Bruce Morgen

unread,
Jun 18, 2012, 1:02:38 PM6/18/12
to
As Steve Fabian explained,
using that parameter means
you can resume the copy
after hardware, power, or
network failures, but not
after deliberately aborting
a copy /j operation (e.g.
from the keyboard or by
prematurely exiting the 4NT
window).
0 new messages