I hate windows networking.

[notfred]

Originally posted by: FracturedSoul
If you think the NIC is bad then replace it, they ain't that expensive. It ain't windows fault your damned NIC went bad, don't blame the OS 'cause your card dies.

You don't seem to understand my problem. The functionality of the network card does not effect the contents of the hard drive.

 

[isekii]

boo hoo

lets blame microsoft for all the wars in this world...

geez it seems like a bad connector or something, why blame windows for it ?

 

[GeekDrew]

Originally posted by: notfred

Originally posted by: FracturedSoul If you think the NIC is bad then replace it, they ain't that expensive. It ain't windows fault your damned NIC went bad, don't blame the OS 'cause your card dies.

You don't seem to understand my problem. The functionality of the network card does not effect the contents of the hard drive.

Some other action has caused that file to be deleted, not the copy over the network... windows DOES NOT delete anything until after it is verified to have been received... so it would not have been deleted if it was being moved... and it DEFINITELY would not have been deleted if you were just copying the file. Something else is at fault.

 

[Windogg]

My home RAID5 array has moved around 100TB (Yes Terabytes) of data in the last few years and everything has been 100% so far. A few servers at the last company I worked for would 6TB a month of transfer and no one has ever complained about losing data.

For those looking for a nice gigabit switch. I have my eye on the Linksys EG008W for around $165 shipped. Eight 10/100/1000 ports.

Windogg

 

[kt]

It's like falling to the pavement and get a nasty scar then blaming the pavement for being there. You didn't get hurt because of the pavement, you got hurt because you are damn clumpsy!

I don't know how you lost your file.. but I have done transfer over the network many many times without losing anything. Even had a computer crash on me while doing a transfer.

 

[dighn]

hater

 

[DaiShan]

You have ntfs on the laptop hard drive? If not it won't be able to store it....

 

[DaiShan]

Originally posted by: Bootprint
Go wireless and wait for it to finish transfering.. and waiting and waiting...

Haha that is the truth, I don't bother transferring anything at all over my wifi, just used to share internet and printer.

 

[DaiShan]

Originally posted by: notfred

Originally posted by: FracturedSoul
If you think the NIC is bad then replace it, they ain't that expensive. It ain't windows fault your damned NIC went bad, don't blame the OS 'cause your card dies.

You don't seem to understand my problem. The functionality of the network card does not effect the contents of the hard drive.

Just get a file restore program, problem solved

 

[spidey07]

A little help here...

1) don't crimp your own cables, they suck when you do
2) buy patch cables
3) get gigabit when you want higher speeds - the "overhead" is exaclty the same as 10/100 Meg ethernet

Hope that helps. Tons of misinformation in this thread.

Please just trust me on this...been doing it for 14 years.

-edit- if you got a "cable unplugged" error then you have a physical layer (cable) problem or nic/driver problem.

 

[GeekDrew]

Originally posted by: spidey07
A little help here... 1) don't crimp your own cables, they suck when you do 2) buy patch cables 3) get gigabit when you want higher speeds - the "overhead" is exaclty the same as 10/100 Meg ethernet Hope that helps. Tons of misinformation in this thread. Please just trust me on this...been doing it for 14 years. -edit- if you got a "cable unplugged" error then you have a physical layer (cable) problem or nic/driver problem.

Ahem, your edit is exactly what they had been saying... and only a couple of clueless ppl posted contrary to your 3 points

 

[spidey07]

Originally posted by: GeekDrew

Originally posted by: spidey07
A little help here... 1) don't crimp your own cables, they suck when you do 2) buy patch cables 3) get gigabit when you want higher speeds - the "overhead" is exaclty the same as 10/100 Meg ethernet Hope that helps. Tons of misinformation in this thread. Please just trust me on this...been doing it for 14 years. -edit- if you got a "cable unplugged" error then you have a physical layer (cable) problem or nic/driver problem.

Ahem, your edit is exactly what they had been saying... and only a couple of clueless ppl posted contrary to your 3 points

heh, yeah it was the comment "gigabit ethernet has more overhead" that got my eyes rolling.

Seen it a million times - why does my network suck? "did you make your own cables?" yep "that's why".

 

[McMadman]

I would think that gigabit network would be almost as fast for a copy as if it were hd/hd, (the drives being the major bottleneck of course)

That source file should not have been lost though unless it was simply too big anyways for the file system.

 

[notfred]

You guys can't read. The filesystem on the laptop has noting to do with whether or not the file remains on the source machine.

I did not accidentally delete the file after my transfer failed. If I had, the file would have been compoletely gone, not shrunken to 10mb.

I'm not mad cause my file transfer failed, I'm mad because a formerly 4GB file was reduced in size to 10MB after this network problem.

I don't care if it never happened to you before. It happened to me. I once broke my arm. Just because you never broke your arm does not mean it couldn't happen to ME.

 

[GeekDrew]

Originally posted by: notfred
You guys can't read. The filesystem on the laptop has noting to do with whether or not the file remains on the source machine. I did not accidentally delete the file after my transfer failed. If I had, the file would have been compoletely gone, not shrunken to 10mb. I'm not mad cause my file transfer failed, I'm mad because a formerly 4GB file was reduced in size to 10MB after this network problem. I don't care if it never happened to you before. It happened to me. I once broke my arm. Just because you never broke your arm does not mean it couldn't happen to ME.

We can read just perfectly. We just refuse to agree. I fully believe that you did not accidently delete the file. I believe that some operating system process on ONE of the ends caused the file to be corrupted. Which machine was source and which was destination (OS)?

 

[notfred]

I had this 4GB file on a Windows 2000 machine. I had an OS X machine on the same network. I connected to the macintosh share from the windows machine. I then copied the file from a Windows Exploer window, and pasted it into the open window showing the macintosh share. The file transfer started. About 75% of the way through the transfer, the "cable disconnected" message appeared. At that point the transfer stopped, and the file size was now 10MB on the windows machine, where it had resided the entire time.

Is that a detailed enough description?

 

[GeekDrew]

Originally posted by: notfred
I had this 4GB file on a Windows 2000 machine. I had an OS X machine on the same network. I connected to the macintosh share from the windows machine. I then copied the file from a Windows Exploer window, and pasted it into the open window showing the macintosh share. The file transfer started. About 75% of the way through the transfer, the "cable disconnected" message appeared. At that point the transfer stopped, and the file size was now 10MB on the windows machine, where it had resided the entire time. Is that a detailed enough description?

Yes. Sorry for trying to figure out what happened.

And what did happen was probably that windows didn't know that the file transfer failed - I'm not 100% sure on how it works, but it most likely does not verify that the file transfer was successful under foreign operating systems. And yes, while SMB should have governed it (I believe), there was a failure somewhere. Most likely a hardware fault.

Drew

 

[McMadman]

That really is an odd fluke, since basic "copying" shouldn't ever do anything other than read the source file.

Of course, I have no experience in dealing with large files, I'm limited to FAT32 due to the desire to keep a dualboot system, most things will start to act "odd" when working with a single file that approaches 2gb for me.

 

[Zugzwang152]

at work we're installing cat. 7 cabling. it's supposed to be scaleable up to 10 Gbs :Q:Q:Q:Q

 

[dabuddha]

Next time copy the file properly. You did something wrong. Not sure what though. If you simply copied the file, then it doesn't effect the source file. Perhaps you had another application running which had the file open? Or maybe even some sort of virus, who knows. Either way, you can redownload your dvd iso

 

[XZeroII]

Definatly not Windows fault. Windows will always transfer the file, then once it's done it will delete the original.

 

[WannaFly]

I'd bet on the fact that it wasnt windows networking's fault, you were probably MOVING the file instead of COPYING. That will do that to the file. You've learned your lesson!

 

[JackBurton]

I'd bet on the fact that it wasnt windows networking's fault, you were probably MOVING the file instead of COPYING. That will do that to the file. You've learned your lesson!

Exactly.

 

[notfred]

Originally posted by: JackBurton

I'd bet on the fact that it wasnt windows networking's fault, you were probably MOVING the file instead of COPYING. That will do that to the file. You've learned your lesson!

Exactly.

You guys can argue with XzeroII about it. I know what I was doing.

 

[amdskip]

Originally posted by: McMadman
That really is an odd fluke, since basic "copying" shouldn't ever do anything other than read the source file.

Must be a user problem