• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I hate windows networking.

N

notfred

Lifer
Windows networking just lost a 4GB file on me. I was transferring it to my laptop, about 75% done, and then the little "network cable unplugged" thing came up in the taskbar, my transfer died, and my 4GB file was now a 10mb file.

I nearly beat the PC to death. Fvcking thing.... I want to kill it. :|
 
Originally posted by: notfred
If only the internet was as fast as a LAN...

Of course, I still find 8 minutes to be too long to wait... I'm so spoiled.
Click to expand...

What, you have something that'll transfer that faster?
 
Originally posted by: Kenazo
come on gigabit... 🙂
Click to expand...
Too much overhead.

Besides, theoretically, you should be able to transfer 1GB in 8 secs on a gigabit conn. However, like I said, overhead + hdd limitation.

Firewire, maybe???
 
and completely unnecessary for most applications. I'm contemplating going gigabit for my home network. 🙂 The cards can be had for $50 cdn a piece, just patch my two computers together and then have a 10/100 nic in one of them if i want to add any other computers (like friends)
 
WTF??? How does Windows Networking "lose" a file? What version of Windows? I've had severed net connections many times when transferring files (we need to reset router to get the print server working...dad does this without asking...) and I've never lost the source file...EVAR. Even if you're doing a 'move' and not a copy...it won't delete the source until after the last packet of the file is sent and verified.
 
Originally posted by: uncJIGGA
WTF??? How does Windows Networking "lose" a file? What version of Windows? I've had severed net connections many times when transferring files (we need to reset router to get the print server working...dad does this without asking...) and I've never lost the source file...EVAR. Even if you're doing a 'move' and not a copy...it won't delete the source until after the last packet of the file is sent and verified.
Click to expand...

Whatever version of windows networking windows 2000 uses. The file was over 4GB when I started, and 10MB after the connection failure.
 
So... the transfer was hosed somehow and you blame windows networking? That little "network cable unplugged" notification is tied in with the hardware; blame your cable/NIC/drivers.
 
Originally posted by: notfred
Originally posted by: uncJIGGA
WTF??? How does Windows Networking "lose" a file? What version of Windows? I've had severed net connections many times when transferring files (we need to reset router to get the print server working...dad does this without asking...) and I've never lost the source file...EVAR. Even if you're doing a 'move' and not a copy...it won't delete the source until after the last packet of the file is sent and verified.
Click to expand...

Whatever version of windows networking windows 2000 uses. The file was over 4GB when I started, and 10MB after the connection failure.
Click to expand...

Were both boxes win2k?
 
Originally posted by: Descartes
So... the transfer was hosed somehow and you blame windows networking? That little "network cable unplugged" notification is tied in with the hardware; blame your cable/NIC/drivers.
Click to expand...

I'm not mad cause my transfer died. I'm mad cause windows lost 4GB of data.


And one bow was a win2k machine, the other was an OS X machine.
 
That sucks. So, you were xferring from Windows to OSX, cable came out of OSX box and file was lost on Windows box?

Anyway, when I transfer a lot of data like that I use copy, verify it's good on other side manually, and then delete from source afterwards. If I use move, I generally don't care if the data goes bah by.
 
And one bow was a win2k machine, the other was an OS X machine.
Click to expand...

I have NEVER had any problem with windows networking after it was properly set up. And furthermore, not once have I ever receieved a message that the network cable was unplugged when it was not unplugged (or the device on the other end of the cable shut down).

Drew
 
Originally posted by: dman
That sucks. So, you were xferring from Windows to OSX, cable came out of OSX box and file was lost on Windows box?

Anyway, when I transfer a lot of data like that I use copy, verify it's good on other side manually, and then delete from source afterwards. If I use move, I generally don't care if the data goes bah by.
Click to expand...

The cable didn't physically come out of anything. I think the network card in the windows box is bad, and that's why I got the message. And I didn't use move, I was copying it. It got lost anyway.
 
Originally posted by: notfred
Originally posted by: dman That sucks. So, you were xferring from Windows to OSX, cable came out of OSX box and file was lost on Windows box? Anyway, when I transfer a lot of data like that I use copy, verify it's good on other side manually, and then delete from source afterwards. If I use move, I generally don't care if the data goes bah by.
Click to expand...
The cable didn't physically come out of anything. I think the network card in the windows box is bad, and that's why I got the message. And I didn't use move, I was copying it. It got lost anyway.
Click to expand...

I have never lost a file transferring from Windows. I routinely transfer 20+ GB of data and never lost a byte.

EDIT: I transfer from Windows XP to Windows Server 2003 Enterprise or Windows 2k AS.
 
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 must log in or register to reply here.

TRENDING THREADS

Back
Top