copy size?

"CJT" wrote in message
...
*selah* wrote:

"CJT" wrote in message
...

The obvious question is, "What's the error message?"



"Cannot copy file - file system error (1026)"


Does any of this apply? :

http://support.microsoft.com/kb/q208082/


I had already seen this file - in the section that is of interest,
all
it says is:

Network Security or Traffic
Check with your Network Administrator to verify that there are no
network security or network traffic issues on the network.


Does the error occur regardless of how you try to copy the file (e.g.
by drag-and-drop vs copy/paste vs ftp)? Have you tried copying
between
the machines that are involved and others on the network to determine
whether the problem is particular to this source and/or target?

When you monitor the status lights on your NIC and/or switch/hub, do
you
see anything unexpected (e.g. drop of connectivity, long lags, high
collision rates)?

I'm not sure how to do this. The nic on the dell is on the back of the
computer. The one on the laptop is visible and has 3 lights, but I don't
know what they indicate.

"*selah*" wrote in message
...
I'm not sure how to do this. The nic on the dell is on the back of the
computer. The one on the laptop is visible and has 3 lights, but I
don't
know what they indicate.


The fd/col and 10/100 lights are steady green, the link/act blinks green
rapidly (on the laptop).

"*selah*" wrote in message
...
I'm not sure how to do this. The nic on the dell is on the back of the
computer. The one on the laptop is visible and has 3 lights, but I
don't
know what they indicate.


The fd/col and 10/100 lights are steady green, the link/act blinks green
rapidly (on the laptop).

*selah* wrote:
"*selah*" wrote in message
...

I'm not sure how to do this. The nic on the dell is on the back of the
computer. The one on the laptop is visible and has 3 lights, but I

don't

know what they indicate.



The fd/col and 10/100 lights are steady green, the link/act blinks green
rapidly (on the laptop).

That's as it should be. I'm curious what happens as a copy fails --
e.g. does the link light go off? At the same time the disk light comes
on? How long from when the lights stop flashing until the error is
signaled on the screen? etc.

I suspect your transfer is proceeding fine until the receive buffers
fill, then (as it's necessary to dump the data to disk on the receiving
end in order to proceed), the sending machine times out. Unfortunately,
there are MANY reasons that might happen, from faulty software/drivers
to misconfiguration. No chain is stronger than its weakest link.

I detect from your response that you might be using a crossover cable.

FWIW, I've found use of such cables (i.e. no switch/hub) to be more
troublesome than a "normal" connection. Switches can be had for under
10 bucks; that would be a cheap thing to try in order to eliminate one
possible source of difficulty. A store-and-forward switch will help
manage the protocol and perhaps get you past this problem.

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form .

*selah* wrote:
"*selah*" wrote in message
...

I'm not sure how to do this. The nic on the dell is on the back of the
computer. The one on the laptop is visible and has 3 lights, but I

don't

know what they indicate.



The fd/col and 10/100 lights are steady green, the link/act blinks green
rapidly (on the laptop).

That's as it should be. I'm curious what happens as a copy fails --
e.g. does the link light go off? At the same time the disk light comes
on? How long from when the lights stop flashing until the error is
signaled on the screen? etc.

I suspect your transfer is proceeding fine until the receive buffers
fill, then (as it's necessary to dump the data to disk on the receiving
end in order to proceed), the sending machine times out. Unfortunately,
there are MANY reasons that might happen, from faulty software/drivers
to misconfiguration. No chain is stronger than its weakest link.

I detect from your response that you might be using a crossover cable.

FWIW, I've found use of such cables (i.e. no switch/hub) to be more
troublesome than a "normal" connection. Switches can be had for under
10 bucks; that would be a cheap thing to try in order to eliminate one
possible source of difficulty. A store-and-forward switch will help
manage the protocol and perhaps get you past this problem.

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form .

CJT wrote:

*selah* wrote:

"*selah*" wrote in message
...

I'm not sure how to do this. The nic on the dell is on the back of the
computer. The one on the laptop is visible and has 3 lights, but I


don't

know what they indicate.



The fd/col and 10/100 lights are steady green, the link/act blinks green
rapidly (on the laptop).

That's as it should be. I'm curious what happens as a copy fails --
e.g. does the link light go off? At the same time the disk light comes
on? How long from when the lights stop flashing until the error is
signaled on the screen? etc.

I suspect your transfer is proceeding fine until the receive buffers
fill, then (as it's necessary to dump the data to disk on the receiving
end in order to proceed), the sending machine times out. Unfortunately,
there are MANY reasons that might happen, from faulty software/drivers
to misconfiguration. No chain is stronger than its weakest link.

I detect from your response that you might be using a crossover cable.

FWIW, I've found use of such cables (i.e. no switch/hub) to be more
troublesome than a "normal" connection. Switches can be had for under
10 bucks; that would be a cheap thing to try in order to eliminate one
possible source of difficulty. A store-and-forward switch will help
manage the protocol and perhaps get you past this problem.

Re-reading this, I realize I didn't notice before that you say the
"fd/col" light is steady green. You might want to read the
documentation for your laptop and see if that's normal. It might
be indicating near-constant collisions.

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form .

CJT wrote:

*selah* wrote:

"*selah*" wrote in message
...

I'm not sure how to do this. The nic on the dell is on the back of the
computer. The one on the laptop is visible and has 3 lights, but I


don't

know what they indicate.



The fd/col and 10/100 lights are steady green, the link/act blinks green
rapidly (on the laptop).

That's as it should be. I'm curious what happens as a copy fails --
e.g. does the link light go off? At the same time the disk light comes
on? How long from when the lights stop flashing until the error is
signaled on the screen? etc.

I suspect your transfer is proceeding fine until the receive buffers
fill, then (as it's necessary to dump the data to disk on the receiving
end in order to proceed), the sending machine times out. Unfortunately,
there are MANY reasons that might happen, from faulty software/drivers
to misconfiguration. No chain is stronger than its weakest link.

I detect from your response that you might be using a crossover cable.

FWIW, I've found use of such cables (i.e. no switch/hub) to be more
troublesome than a "normal" connection. Switches can be had for under
10 bucks; that would be a cheap thing to try in order to eliminate one
possible source of difficulty. A store-and-forward switch will help
manage the protocol and perhaps get you past this problem.

Re-reading this, I realize I didn't notice before that you say the
"fd/col" light is steady green. You might want to read the
documentation for your laptop and see if that's normal. It might
be indicating near-constant collisions.

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form .

I tried mapping the network drive as F: and copying the files from dos
and they all copied with no problems.

Seems the problem is with windows somewhere.

I tried mapping the network drive as F: and copying the files from dos
and they all copied with no problems.

Seems the problem is with windows somewhere.

*selah* wrote:

I tried mapping the network drive as F: and copying the files from dos
and they all copied with no problems.

Seems the problem is with windows somewhere.

Sure sounds like it. Is copying them that way an option? Or do you
still need to find a solution?

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form .