🚀 go-pugleaf

In article <mtvCzKAC3O$3Ewbu@dbqa.demon.co.uk>, Tom Bird
<hamster@nospam.demon.co.uk> writes
>More of a Hamster.  I did test it, I set two to full duplex and
>disconnected the rest.  It just went like last time.  Not to worry, I
>think you would need a switch for full duplex.

Not according to 3com the hub just has to support it as well.

I'm not sure whether mine does.
In order to get duplex I have to manually switch all the cards. Then I
get the following same results doing a simple restore of a compressed
partition (basically a copy of files, but compressed originally which
explains the slower rate) using netbeui (only) using Ghost. Ghost gives
me the fastest rates. Machine ghosted *from* has been manually set to
100baseT & switched to either full or half, network optimization: 
Note:                  ^^^^^^^^^^^^^^^^^^
normal.
(after things have settled down)
Packets received 44547*
Packets sent    133155 
Single collisions 1-3 
Multiple collisions 0
280 Mbytes of Data
Time taken 3.18 mins
Done a few times just to make sure
I would have thought this ought to be faster with duplex in view of *,
but it's the same!
What _does_ slow the operation down is switching to 'maximized network
performance' when the received data rate doubles. What this really seems
to mean is more reliable? *not* faster performance.

All 3com cards btw; all working fine, now, thanks 3com!

The hub is a big old dual speed thing (fan cooled!)
-- 
John Chapple