PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Herbert Graf <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Wed, 29 Mar 2000 07:40:23 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
> Thanks, Peter, for the response.
> I have another question though...
>
> The same two computers connected via crossover cable;
> Computer B is printing to the shared printer which is physically
> connected to computer A...
> Now computer B wants to read the contents of a large file on A...
> Can A send B the data while B is sending the print data
> at the same time?   (Full Duplex)?
> Or will printing be interrupted while B receives the data from A?
> Or will A have to wait for print job to complete?
> The answer will help me to understand my original question about
> full duplex.

     On a network, rarely is something sent continuously such that no other
system will be able to get in a packet, so even if you were only half duplex
the print job would still wedge it's way in. Full duplex of course wouldn't
have to worry. Quite frankly, full duplex is a great idea that has rarely
ever worked well. On a two node system it may help from time to time, but on
a small LAN it is practically useless if there is alot of traffic. You'd get
a much larger increase in speed by going 100BaseT instead of getting full
duplex to cooperate. TTYL

                  Visit our website regularly for FAQs,
               articles, how-to's, tech tips and much more
                  http://nospin.com - http://nospin.org

ATOM RSS1 RSS2