SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks
ATM vs. Gigabit
An SI Board Since July 1997
Posts SubjectMarks Bans
63 2 0
Emcee:  Michael Foy Type:  Unmoderated
 Previous 25 | Next 25 | View Recent | Post Message
Go to reply# or date (mm/dd/yy):
ReplyMessage PreviewFromRecsPosted
13 Geof, it is true that Gigabit Ethernet has adopted the Fibre Channel physicalSteve Scribe-7/28/1997
12 >>This {Fibre Channel} will provide the economies of scale needed to compGeof Hollingsworth-7/28/1997
11 <<<(FC is replacing SCSI for storage.>> Can you tell them to huEleder2020-7/28/1997
10 I believe that ATM vs Gigabit Ethernet is a false choice. I think that they bSteve Scribe-7/27/1997
9 <<Why in the world do you think those are requirements for GE to take offGeof Hollingsworth-7/23/1997
8 Regis,, Thanks for the lead. FORE becane a good buy today. We should see a breaJohn T. Hardee-7/23/1997
7 Article on Fore & Bay earnings, comments on shift into gigabit. news.com Regis McConnell-7/23/1997
6 Would you include MRVC as a player in the gigabit ethernet business? Mikemountyone-7/23/1997
5 <<IMHO Gigabit ethernet is not going to "take off" in the LAN eSector Investor-7/22/1997
4 I'm interested in why you think MRV/NBase will be an also-ran: they have mDee Jay-7/22/1997
3 IMHO Gigabit ethernet is not going to "take off" in the LAN environmeGeof Hollingsworth-7/22/1997
2 I agree with the premise that ATM will survive in the WAN ... primarily becauseVincent Yaffnarro-7/22/1997
1 1) I believe we have reached the point where gigabit ethernet will the backbonPaul Motter-7/21/1997
 Previous 25 | Next 25 | View Recent | Post Message
Go to reply# or date (mm/dd/yy):