yes that's the most obvious solution for my problem.
--
View this message in context:
http://www.nabble.com/cygwin-copy-problems-usb-2.0-tf2009189.html#a5537963
Sent from the Cygwin Users forum at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
isn't there a possibitly that cygwin provides a quicker cp-implementation?
i mean 4 minutes for a copy of 70MB to a memstick (instead of CopyFile() 20
sec.) is not really good performance.
i guess there is a reason for that...
--
View this message in context:
http://www.nabble.com/cygwin-copy
when running a little program using CopyFile() under cygwin it is about as
quick as totalcommander. so it must be the abstraction layer of cygwin which
makes copying vry slow...
--
View this message in context:
http://www.nabble.com/cygwin-copy-problems-usb-2.0-tf2009189.html#a5528112
Sent
total commander is a clone of norton commander. something like midnight
commander on linux.
i thought the same: choice between usb 1.x and 2.0 is done far lower level
that cygwin can really influence it. but the difference of speed made me
consipicious.
example, copying a single file (.tar.gz) o
hi,
i've got usb 2.0, when i copy through TotalCommander the copy speed is quite
high. when i copy through cygwin shell it seems that it is transmitting data
only with usb 1.x speed.
very spooky, because i thought that cygwin is calling windows drivers/api so
it should be indirectly supporting u
5 matches
Mail list logo