DOCS/DESKTOP0000755000000000000000000000000011761422163007531 5ustar DOCS/DESKTOP/45double.gif0000755000000000000000000001647311656741062011745 0ustar GIF87a/,-#!#+)+313;9;! !WUW|z|xvxQPQPOP~}~mlm]\]²;9<557EEGrrullo[[]001++,CCD}}~uuvdde\\]Ҽ?@Ckloacgiko}~сy|QSUY[]cdeghiqtv¹9;VY"fWV\.$R1C+Q^$ԇuRDGwVƹ JH-!č*aTD r@yrFZr i **Ч.ڨ(Q*Ц04$Le1rY X]Y1/q#Gu곭%ATpIƔhY2@@"ȭ|"C¶c /UdQx \‡%8*Н.c)P!DCB $8b yd.(+lPa[D /#RD|Lx5*j+I0}nWW[%B 6/E)F kĽ)+. P+rFJ3 $*Bq֞tfB,Tˀ eF$$g牟\x*'؋ P+XJq 0xs"ۇg.f ~ Sd6>l~W(|)ǎ1 B|+҇,AW: #}[H h,e0X` kH/Y0# e >L A &lcH/eAa7^\P  w"IHb!x qVz#33 >b$[[ > Er8.vxĐr pыhP'1e B5$ub@P#CS@vD萲DvEӑ J$~uɒdɢDƝ,S ʠc8MdMJ/RZ gU8Ib%BxDqј,: rS:(LS , ȆDYO4}z̭_wK5؛<_#:HQiz|@ݔx4sָiDQISTFe@^/{(15a V$u$wE~}(52_B^p#08R$"hS`'Is( QrY@'H$gS9uL,؂[ X5f1qR1}]>v_RY25ExTBM``!ICpvQh:S*%& 9#2tr1qh9e0g4H̀ }"X5KsW! >[ׇb_cpնYYqurbu ]@xţ PFwe+7hg"d}U'.H>W`RSS ҃=V-#ŵq&,#^>l`TZTzxcQYsDo"1sfqu5 a]_bEx Ў%S0'*x~ e2&_p@ZT@36>^$RU5*@2]S!Ñ{ ԅh#l]"g@gxu a7_WT*' 5` fW"d7]ҵ&,u$>lI@Aql#Ty1Xy"/$VXXnVzH.^`;) djSaA[CoXRJ ;q  <9sbeJ̃j1 @P<" d"֙.H Y9$N3J(O(,I0U3Fv RZyoxfqSzIdVb)#x,E<eOc~ȝDCx".A=;X3 [ lY&|?cM!aChسwH[5C>Q&S,WNFoDi*sgAt(ЕMa 0P.f>Ygehd @_`gAO抅"ӏf)p2)gRLP">630BvaB79g`hF`o6.0D>:}GH ֏Y]9DOD YI1#h a N({8LlByhYb*0 jrak^ )iEKԬ JDZEs*E:klUEa42T]4kfZt:Dln$pTU·'DWzFߪԫ"qmdLzׯc*i0<c pۖKqG畱́V}@ !K$ &p pLQF.+kEVo" >|@"mB+F AE ױ SGEWP #Qo[ {Fڲ񲇝|@j<ã"+%:1zxqq!n&rKb*`w (SǸy!v/cĹk|Blt\dC۸FrYdC9q6˻H7@*rŻ5r4.%h o|Ut+ h(!=e&{`w mHGPWwDi$f~aGdzDr";L1f!k|Wv^f,fB!xqL8\C;D!DԺWVb0 {a j[qXOA !QLq{.MqR5U^ ESo>1q6|0A+꾦ƵK*N7S2&ȉ\q} TzH4\>Ǜuٴcw}xPG{dWQNME[!izX*@&eN"WZ:sc6et}Lw~*C} %9Npm@. nPhLQ\z])sHv8't9<, 9+wf( 4#M! v ,2ҺHf vגi0*} $43"=C5h>l2=/Se)Yk@)44N$ak[ P ADMo fSK&JNERB]IBP6jJ}ש_NP1lwʪ91ViSp-|' #H5V]č펚RIaI5*<ڭiX]~bq! DP탇%JJEi˭Yb>C-݈I,G#zTl܎L30$=gIMٍuBR -3߷( %@|<e:R4 % rkҽ4i.2p2 ,"w"6.sKٜ mߏA)(8/Őh^&.W3UN{/QAi`0`SFF03ӳ}=8+;*;3MP3RQ A]WP4Mcy0!8sVfcSn4B~8 ;3xâa | 5a,31sY萾_S0J֙A;4-9{x5tWdE6/~nk&M\!A-22Z2#3VqpV]YK >0돋dq٤.&g"[A!x C4y~>Cx)Iڅ(,qJUJRl 꾅߈yuf.-#MQ Cd]ӕa`ߦI/V pr^7Q 5;z&5p~tH`߂n9ʨٕwi#uD`0@6U,`*9Ci1 ]?*,lW]7 67C1ͤ?4rO#5 *D`ѵ:F &@H P(QPD zZcP<~ B 1-=9S(T3{l9+T+BRh PEj0UTUr1jWK<5,K~}֢ʔm9 i%fZȲ'Fw{ u_4L3P+SHP>sL FE2HbH a%1ע,4 ;f9T @j"M-AUXU $ lB=(]Ws/v ; [Xd]YODKД5>X$[mB`[GH`\<\)LWX@J*ʹ#gͫW6-P&ۣ*޶Px&$>V8g*^$d?&=Iٱ !JYYW,Vfy#pZ>ʦ9%\ :h dC̪JaxA /bS\6>e2m寱t{%k*oX$ \.jFv #_b ÒqsݻYs=/5HL`"DXzo!*y zj {Yyu@&$XWc ˧|aɖ@L"4N ! YJT']9K2+e.fKR/K`W LiLfZ ɚ9ML!,9f6/%4f815 lSb;DOCS/DESKTOP/KCCA.gif0000755000000000000000000007240511656741516011024 0ustar GIF89a3(! ,3(ڋ޼H扦ʶ L ĢJL* JԪjܮ 2N' HHXhx)9IYiy7h):JZjz +;K[k{ػ ,N^n~ͷO_o?>/~<0… xÉcI1ƍ;z|tQP$Kf i2ʕ,[RN̗4ki3Ν<{L5NP &io(ҥL:}Si #V8eue5Ѭd-B*°غBnB&ה]ػ&2s1I(T2anIIPt ~xښJ|xhhV }x=ۜ?;qr΄{xobaO5:sqt}jW㺉9E(q]!yە_!gշ7 { ؘ NJ`Yd& Ga ?%bh3HD#G#5Ђ$>>dDIڷxU^qHݔvxP15yNz)c1hFff%aRқrv֝[*H^ J%6N Jyv[^i$*Ihzj%*v)k!>(tm˜޳u1+F,{תzQ[ [gLj*l6arxvf8mzbΛiofOnꙋn {n2ps!S[:XIw8vkHcL7K4chCr _p ( 5ψG\l)ɠ"i}*' Qwo_e`7 *x-~HcvDn53X%Bwl>[=EiV:L\͕{>3f7Xݐ|A9/'0׳w|dwF+ l|;1J} &}Fed>'viRϽVTs^>Rbk[w=dXoQ1(4 Mr |,($CZ_Eek)|3 %~j62R u-v8eqF ) F0S$:fLZ|XA,0k4ġ,CQ0׷ƿv3ZX1^}|ت 1bXD䠑2[<Q3 6[$rngx\PafBD "e⧺qe+XEIp(RQΎw\c);8Leld$y. :}JWnZFBU:ӓn\5_v4M=׿f+ܺx(nbuq;wVzTt$Tl+o^_M#o-qd%=jlR2O+h%u G L[vk~4`ᔝoc1Ւ-,귑̀0_}fc&`G=߹{+Vf;,Rn`t%ξt8ƹ lWbYy;?P9AT`N=hO de^ɥu{[Y^ ?˹>NGe}۷w9ѐ9y歗}GowsDʭ;Օn䓞Sd M[}}6}r^ԁbBkRakOk.K EcƕjaxtgfpdU`#Mwvd~ usF8bWCrw[vǀpӗ-CGtuvCD3zЖ^vI%wǀk%M}t'jgkNTpDD7SURvN}*{rqr~Psr&?9I_vV[t`Gi-vE#FWxAd6xXZU,^r8FhK-xjIS@*})htm5n Ո:~:uxv(l3'|K(QBRG. |5Xvu-bg90\q'}⊁"KHy aEX08{1VrasVdF-C[]Ha(#HiHXȅ[ 9m W/kWx{6`Nvr8hOhWvy4ǒI|冔J8bjȃo(j6OXhWw~W#d8EI9/Z@icAi)1$كK)vkU7("wsԅ$xĕu) 'ROR[EnYjlEVh.ʸG|V7lWԘAIɈ4َGG!6I@n)pٖwtymcxٌWUJUO(pIjsX3g sɛo/739Ȗəwm9wמډ!GJ}XlIٜgՂY? 艚~ަ-C8!TOaع(ƔJٛd4z٠I~JYYHw|_ yQ4k !~,z#f^ĂPb=yz:bQfhueʁX,*x`LZ?؀k V&aBi*è/z嘝`q:\r *QZ{Ĵfڨҩ*ɩJQQ&mʪ (ڪ**ڨJxZlšĊ:Aʬ٬ *zՊ٪Dq**J 窮ʮ ک J*jʫʯꯀKkѭ[ ˰ s*kK+y+%k';i$-֚/l,+5k7kH4=k?&<+Ek}G{=DMOL+UkW[T]d_\+ek;gdm&o+uk/wt}v|+ks[lx+kK2[+k 뺫K;k˻pKျ ˼  K[ۻ˽࠽+Kk黼嫾ھ W{5K싿i[L|k  ,\c[ l"L% ({+. 1 4lö;7<:䛺= @,ĞC,FĖ[I2LčORLfUs|v6[y|' {Lȅ{Ȋ Ȉȑl2Ʌ\ɗۑɄɝ,wɂʣOQ|ʩH~ʓz"kS{_uÚljN^vY׬-Iz_lgEz<)\eq;ǎ>S}B I̙VU J҉ٛ?mXݍhSǖ]]]-s%qA-٧{F-Jc]!IVjǼjr:ڿ7a7{)]Z< Z3 ǣV=ԛDHיI [)gMr왂#tyAb,.צy`nݙ mx ބ(wt-tn9 {ȑVR#Ckd&.W~]薀&}}Pkm_?~ݑ<P3쭓0OTmX. #Jxӧg(܌\m)n(Я} X}6^QP[T:,K&Gt1lep5z]xiڒ{䉮=]AXd%X^Lwn=Cf>gD]ӣ^Q= uh:n㦾pGonm9*]^;^Y@Y.bޚv^KPx1~}~l .M&~]i~N?欻@|E gzh.$ Otn~mNUx¡B--hx;ޙ~ QLe:zRz^~,l+_+'^&e6 x.v^8 #F_=!_r/kx_\^Ž'<nCl?IdnITM՜?/b/9ďmMٱd/dH/_Nd_o4w}$US19il]1KN]L#_ݜy^Qn >gQU9&LYe֜.)*{ҞE7YF_-+n/p /1J( PRSQ2o13Qf#RoӲmt3vvkIUS7:ZzZkD{q; ӖVUXyy~n&.0CB=Q[g,:8aCդxղxeJ`μ4<3/pt3Cb+)5ؤ&ē,,*ȝ@tDM+EjNk*Ŭ0S;m$/a{ò,N=UvU?TqMHRƪM0͘]"KR|)i>ooL+PAWd m>ZV VCŗ8r#M};w\S8k}6G3X!vKeW]߄w˂& ] C@;NWCwndkvXMM`E0V\⢍F_cCyE>Z؆g&Xk^GG>M'~z%\ns6#?H|n_KQj_hKD1إm[hQ~;!C_" үcCH'2] 5XBY--6|YrHò=q |\ UD6Xʵ'LscDqk=Ĉ /EdZ͑>y#{@zjla%.{*CE?y:JbdT!#=eMb-F㒰c!I<8N[yXJ rrd{h@+ ,Ԅΰrgd*3 ǃ, ]8>̔/ݧ2; GeVtǒ%4Dq"c z5N03pFft!3ɩ"v=G8=1NB1ɆCMMgD5O Ai'GQ~Uiۜ'ҡGWz/đʢ)rjsq#JoXSyASOԤ$MN%TUJPNT[TaXZV~+):JT\ZW,Z ֓)ykL[XkZWݭu[QY ;Y^l> X0Ӡ N7;ʖUjY͟⑃Hyڋֶny[z_i+BߖUr2_mH\Zv+W঱7.k;^#tFRս|k%~_0&;` k`8 ` _ 9M!I\b8'VqyUbج)qYt%I_Xƕ7/zUHu_fu?{_^ MگvqW￦{Yw| W9o|YJy|9w??.}z_{_i>ø׽o{}?L|z?7)7NO=Ϝ~*l) yۺ͠6i I :E 딘/|ԯ0y=@IiVDt&4Є<Юg fr-ۯ)o/nPقbP_$/]Nͤ%x0|jhpw6^@_2J|H jK pX ] p{iiМL/ 3Ѕ"ˁpHipp F IP fII걀foJU"i:H1Pti@1I\.1rWJ*0vq p/jtx 7f~PZ>'hx#HGk)y1 yQ+c qf$S{GTT5JqX&`=b&h AߏƦ w Q1_' BUC3D/D6w,=%%172IHz4 2vI/CLSf^>;3#ݏFsNF7HIpK=B1AWL"*-4IJ)#7PeSJ4<44AK,Q2O]2}PyDAWD$GH U;UQK(KF\ KU=;35HoD&/5II7534qt0E5 aMn/fjb`PU sj$t/y@!M$IPsUHYh5M6+t^KY4!=KwQ}ktIC_?kZ1QZ 5$5N/Ib4NN,T]˕\bO5W1J3]XV}t]{QOvLU.3IQP>OAAb+%!6CC+ NjbshoZ\@<{sa_!<'^q-gUQ$kcgk*uShluj#.sv#6NbewjS?0nJkMPp7d,-r]N0aX?UcvfuliWreXVRLFe#q e `p3=TqQh^ɩ摛A*wur rr7PyMHA5`$I5=3ws 'r Nwywcz WoY{7=VDv_{h.wm{&aTzuS6ư[&vճ#7zn!El.kL$7}wJaR4WkܷW`\4vqS}Kyk˴oVtu]ۗ[)p9y5M[ V I'rk|R 8Jw6GAwV^m%vqoeuCcw#7 m-6C5XYYSȇ?v"srX8x{9--mm)YuCDV wUKkŶc(c~[5;]oÝ]TojjS4Ӗڛ|-vO!#!g>>x=S%W~0 oy_lqk^͇AEg?ܜ\-韞fU9V׃[Kz̓VQFw=?G]uްԋ^כ|lnXA~ M}NIv/~ܿLlGㅟ -{zi3e#Y'z!)۞?x㚾_[ E= 4c`p9KJ)fX `^c]6&.s]NխWS_\aKޡP"#ݣW`E%Nd G(h[$d'I&)!X*^p'! `rnt+4r 357r#7.ysxɺby<{},}{mw@V6) i+4ZL}~ٲ$!G~$Fp-[´#fe6tU=g?szAd͈@2biC43A ԫZUdVaf,x(Z&Wؼ1/`vi.l0ĊT;噌mUo,ofey>G.]zԪWn횱)lj>sME{!i:ٷg[ /n8ʗ3o|fYC>})u|g~oω/o<׳o_.:`O$z2vrw~ 8 x ~Dwf}  :6g&!!8"%"e_dS"pc(#=#AㅦM5N(>HFOؤUZy%Yj`] 5zwc6%%wQR[&q9'a^(u\ifme)Iy(*(g/8凟ZgR>xV\v(:*yu0)ԍ ,zZ*+zhj?A*(,J;m7,hӵjje.R{.骻nEm[:,r;I/J./ (Jp˯ ;0ZR0k1ZN1Ȋa2%|zX#21l3۬73=CTAE}4e4o44QK [[S[MYku@sZ`=67{]D6mcyR7ullwk=}sp.4߃~8 ΅38k0;^9kn9o~埋>:Nv^͡:_&;NϞ;'< 凌z>ώ?SΟ?ിs42BBR{ r 4 Ұ 4-C} ?K4$2 ?(R6i4,rO034`l#k9zt4(qɣI> c,$" ID鐌|$ I9r,$/@j̤''WP,%VFU𔬜'_)Kr8%.!Y\J#ev s1ɒeb/)M!s&6XlVM)SNn2mHjEq3@*ɐyqg?TϠg:g0 PA7ǀBiCyAEP!tX'U0~ hiC /5\G_v^ۢGKge:*9]Hy*ShtpuS{Ԫ7Qi6\KQWԬ>CE152xGYŰb4ɶ W]%m2bk(WV*ja3׾u\eZAqm U"SZJ\ wE*LCڃ-Cd2^k *'Sn_ݸ:s2^) unl @ [ z7-D]1%)RSVp]GB7^_~ `j6'WZ+1DL\N$Goo{ c8Bű x6r= 4 (֚K-/u e])L#Ry}y08ynm`4{M7'u^ȅg'AT ×N܌Z9F ԐB$4tRj'uiX ^íLΌ]kcFĔNb[w vT_0ܻ27/>=Vun-&q=.颭 4SKmyv\f|˦3{k1%nwv݋pλ,a{+85M6 |;LQ9?σ4=4Zs7'oJ  FlM[œR]3݉׼_7} FBWg̼[x[{FJ-Z4/Ҋ:/ NJܞR],>cǻ;U}t:1OdC>̟^=sO8+%QNm~<~#7W7*JENv1@~1&wTDtOݶqvgq JP\Q _`~AE,ZQEAU WeVy`E v9XS\ 6퉖u yY6 \Z-I=DGل8r-Z1!)  q~ ʈn-u`Jada .Q ΂i&K,"#m n%b/a%fb z8 H"'R-# "wb/? #1&#c"2>c?19#4VsaBQ5nr`Ai#7cqx#>8Bu*#:iHc;Σc#=#~'>#%&#@ $#A.$Tc=)$CF$L89AD^-"1Z$Fvd!drGd$I$$J$K4$L$u3ҤMdi0$Oed2P/%R622SNc)e.J%Uf%ĤV~ep#z%X(e+Ye,Z-b%[:%E\%R%7ե] %^f^%O%6%`")f`E?Z=faN&QVfʩUf8ș_jdRiZ TŭbYhNy_in%:_lB]hWm_!n6%qV&ĩSrr":'x[:` Jqљ\WgyvKnKxA' Ny&5YR &[D&}(J#5ihYjƧP^'fCiJIIghg&$}0`Z`ń^" >ht Y.SYߍrfꐅh(ui5hp:ړJb$ng,)'TF(yn~ˇ iJizF="ۙ҅]S}i6*y*lqݡa&[`Ɯҝ_=T)wӤ7#)v@jniX**t]fz|*jԪ)E' d~P6+ :N~jV+jku+Sc(ސٲ^*℩Zjh\ضbgv+ i$$,r,j)fC^R]+!` f̚BAǃlTkRfFA(.lĖOn ͂]"bu~I*Ӛe>ҩ򝮖,vݽ~jOmyq,ؾӚm6Ϫwj0f!_2+-0ʢW:)҂鮚*vܹbij>=mFwR. }k&d,Ψ>l^.d2.n.vϞk5,2/ Mn6lf/~]1\Jogᖾhm>!і.vovSͫb_,/_#oݮ/>^'ojP;p`Bpk{0{ʭgZ/6`n-]ݒn˦-pC1 $(RpqQV_p*i=.R ֫H9,,܎lҲS1n~1nNqu^&jYqߊo٫ q$! (+Xaخɞc]o$^ƒ( 5y1*۞*O+⽲4Ų,-? .":ID0+KT1J.3/s8oN1cGi/5#,2 b-lCaZAs8"?jm Ҝ97'8#."4sڬ@#$pAرRsts+_>c8WU3?f=U2W_f-10o3muCá}6#YtC˴ mt;ծf7Ftmo^t1/ผ-1GbjP2 .ƛ5Mߛc`}mWFIVJOUwdut\G X3uUJ5RZ%q!LXx\-ձm+5Us0^ 5Y/vU'V׵lyv5vc{mgurvܳ16t^NXAr1oh#?0c1 W;4nTWB7n{fJ-r*xjrf's©q-r*CI O&8-t(mfiVn N&wHoI>|pc8u- 8imL#w 7 xYŸ#jltZpnߵ[/9 CzRy_ަZlDʂG/uhUvwx9 9Ǹc_ygZC8.79uRVtQl9Vy/c5O飋1۰ʸ;7'y.8}kuKsSHgzz*rى[9' g6w1x1E c{/r;yZ;ks^;Lޱ>|߻;Wp¦};|{{M9˺C/ãG9j:+{1ﰯ|'^V#KzG<4O<ȓ| |Лϯ [{|WCw<Ş}oHReN=2/|Igz=ۛ+֗rT׼':=+K-:;ΓÒ>s~W<ލ|7Ťu3l׺[lW{tf@pL$ vQMD q}!Yfc՟kǁ1_P)x!.WsV[6>{J ox\>>4<@CDE¬A1Ʃ*73$ǖʐH͇P5HRM'3QAְB$S^ԥHU߶NW H=1\cZb&emOo[вPWEuŻwvzr:{~yҙFW8 kgq3FE\*|D4(Wf:RHrɄ8,c 86UDi&fHŏTQ"W.JSQ;)TY WptY)}cc.˲ZۂL08voҮdfw`VutnӾr&Xgʛ\ Qªi .Z,I6_e [lܹ.7i:-`=9&"/ 6"ݽ?7{M8@D~s:c-.SPJC#P' 8ӄ;Ӱ9 )\ L@WKğKq9K̹b(+ٛBʐ>CN!=|$qJB.wsFr`$L2+͓#*KEBmJ;Q pPPP+^{Yuɴ.:S y|~W;|DZ&}tuFYitP5#u+g#&2u]S}[mnwkm^8vc=3{hOG]tT~GüXs_EõECYAɞc$+:T6M\&h%I,TP<[VB=auwɁ ,1qy3΄X>iKQ,+"Q#,yEkLTF,@ xF+rgRlAfz!'y"v<ٌkvʫ'IiskaDVfsg@́V2C'4C'Ny'%t_ ,oAܶo]k܋=q\ *8id᭤9ͳ=rD;y}sv0DʷrnKMx) @Ω~ug]Z]ZI|J#:v]s^u?wwB]i"';.g|?[{wJ_lWs.v}Mzԟ9۳ z-Gw譪wFO{{_]}'\tʾ7p1IV۱5M ~z_~R8S9S Լիi?Ͼ%Q j]#< + 9z? @ s5}V 2TA ,A<CA $A[4@aA72U.B <d@D;Oc!@d"Ypy7! LBA"ߣJ'z۰ .Xٯ4+1Ŀ[Cm):72|)3|A?ZB*7dәC:S-v?ăDD@MD`@sb=/A\pGħ2ŭDVE4D3=ݐSUEHE9[\7`$V>T3;f._d4r0dBmTkTCqĴ"33j|clqtno p4sG[Gv;GYxFwlGzĻGGG{G4Gl,>R+hƊK 0l<2tO;ɕCh,Ek0,+]HKəb$F-JC;~@ʋIēʹJ]TʆdJ+J5P#dP̬@{wzKpL:{+#K?K,,̒%KT6<- L; =ˀiELGvJ;Âb?+o8+V43 S>{=2'R|KcM$*CCdcKԱDŽ D;6T+ETJ:|M$C>6$:zʥM#MT#<]H->$b)#?k`c CNϡJMOOP6* =S--O + et7:# :Z41lTL(2J=D$?zP?5ʉ+#% ŧ+!B}!:‚t%-"Wfxlfٌ̚Bj&G/k&D]ut4ybS>NdRG zMU kV, ^fŖgdÑgz[iiPp1|cl2TIEAh~.J.M_]՚5jD++L(MԒ"^F=W^e=c4E`M߮EYkZjh .g)lR8-F5ukr5GhZ=SıGЖ1PRH8o ,~Q!=`.U`a eKcmTlV'zҥ%+s˅&w3vWIlɐulÆ;"w&׽QU5_s'c_%?uv S?xoq_lφ9x$:$=&oUs&NX[Ւgtv1P#q-e kziw7NuF~F ).}p||z+}|(ݟ׭ vKxJӥ#2k/g_H~~'ؐw-G N^0v։2R 'f+ߟ*l!pH,"-l:ШtJZج6ންxL.Pzn8'_' :0%>x{}z<.6@3$#2<=J| _r[vYjf`TZFy~+;NJ0=ʿԘ?A{⽶dU]8$c!lƷ-L YDxM5IyP[G!˗a Mv oɓ )?-XcNjDC*-Ȍ-tJŇFe{jǪ!{z *ٳ@sZ2Zʝ{l! רL^M%ԦEw2kWq"N|xstfy3[V;.Ө ̊q\ᣯ;1Ueȏ'.q˶S?1y)EN]lس/o-}Zj7n kshw>{}—x^ڥ[`'`] h5 y1؛oic fNE3סW_|rԡ׽}(,b'@4\95 (axm9WE\1PF)TVIm6&[%H]9"e{zYe a::aXZix{隖b 砀TؚN \N`% ٗt禜v駠6fj(FЄVbAdI>(ºTn颟+kl*(csI4*FRmvk覫FՓ& *> >ݸؕ 7ÿk/rGzeB(i,C0,s./;9o+A(  a0`92d03ݘ* B́b!ЉVL@PZ>qy%I" 1F0L$bdEI1b8dSOגyȱ#i}0q% j:aZB9 Nt)!,E{$mŠ2433~T1y_NLY;U22k,)_IY\f4 Nȧ080.tB̝yM7Lt&'Dn3S'?eyb.ܧHiPj!\6 r2(EgZBQr'`8Q2)F[ Ŵn ze$'2y!n=iGҎX#jG2pk\N,kN:DIsD^ߊw)u.Il1x즖@c-kZMLp@sўt?aoUYpŸt)O)0šF*op\9| t!cbR!X7L>; X:rP_, znCFݤ-pXWeHw[a"<Ȇ9fkx7!_+[^8tmTehry 01S,UDse%SD sjukCdkĩEkeVMϗ uZk7#cpnWUMov ^㤥rC0|ˈ{]hy2quyc^~V;vňlS^~5v˭oL[߶Ys<}tMo|_[ z7hvf:"= M@Oġs~2\zh}d.8לV8W½t?vh;~tr<9ftAMt})w˾xI&_]Iq0oxћ/ɷ;=oyJ}dL;Lߝѱ=_Ӷi>/7n;_#`O^ίbݚ~o"}-o_ ~]^R/}yl.cv巽-g^_hCfD9qǗ|4oö`~ (y1I&~gGS}k^^g~(HWlg6fUv#FUҦ._x 5Gux}wF?G:J|{c2|w4H=gpe^Phwgvѧh(}[y\{|뷂a7{6+^v Wt!T ׃wH8tC҅(R|Kx҄{ah[b.tCVv7Uuch}xHs1776Gƕkw'vd膚-xxALƘtqD h83BM:t/X_؊vxXAX~֊oȂ,!h(rHgv7z`k]oXhoXʘ+،57C#x؍gSS3xم>GHWpz+7wt%h$uH'Y@f$ YEw؎Dґ#=/"9>7Xl{8[y_h8]vJ)WB@ٗ7؎1hxI>fAȨ}TzRfYdERWJ^I|hgbe&q{8x'Wo)8Ir=WDŘQys`4Bj/IGi!Bƍ);k)p`y%ugB}XqWSU};h()D(:6ķUUYSZ,i+yh!{y)w֚y%םՙhُЉ$Ce"Rl}gpW}Ni8fi!ZsyPQJ,mw8d4~؋4[ƘrIɖuefɖg|o$k[ZuoD0iYu`o\b*w2)7yMCU6G:,Ijj:{>|I IZWhtjP٩%9sVPt"yw2=PgXgzjbԇZhyƪcxիȟe{y,= *,ŢR4$\H6Jqm)ia&`WFfqG ze_j3*YϚ}w[DFE K<ȥvchaSZ`|pȱqc~9Y 0kK+[nr]e zYcffNtyg׷n-׆}L9}z c- ֈٞs {]ڒ=Rumi=Wٟ=۴TM5,bѦڏqf8)X]8?K Jm|]kUm]NHlҿy D߮M׍mj|,޽]6*M =~|;ښ|fN[5ZߗVN]*v%ҊH"HͱȪ@-u+bndɬVB\N„="<ܺ'{㕌b\k]~xL pε.9Go>/쩸锾9_zư5kƂY^;w mNpQǦ,%Z^뷴᛺mلIdh> ƞʎD~~~Ş4S">~"HN^~~/L?OE^ Wr O/?6^ o$>(ZȾ.*`2_+6/Q-jO1uaV{q֛wPxѓWG}{ߙN!w# LPlpAKS?;f 1 ʐ 9X QLQEJLJ.g C N^n~ͷO_o?>/~<0… xÉcI1ƍ;z|tQP$Kf i2ʕ,[RN̗4ki3Ν<{L5NP &o(ҥL:}Si#V8_ue֬d7M4vNZuDuVI܀V-K]TXWBG j_`vp\Z -c斒PAcр7k6G/˸<3u!ؼ2a-6 ݫ]7}4\ܩ_F9>*9'}k^]ۂ;'^_P[bwz wMw Z3z#`3YZz7Bܦ!$45 S}F!ϭ hb~#Ra=8\AƳdyv#cO%MRތxh~ab,9]YJŴI˖ǭ٣Ltxg/"|xf~BCWWt M 塎`RYijji§fբPβ?کjiJ&(먰 ʂB *mbݨBf$4Frn*'ƺ證)T m-Z!o-N%;5j u"o;k8.,jlWWX6ogrٲ6+ _賮3"̱ nH{=1`WRQ˩:aWk.1 qmN᝷94Lywd[*W o[$KMbgݛilD[s.]:cgt(:ů}/nCyq^@kXk.O}nNVۺlIiȂ;lk;VgH_0!>DS,=ku3Ru^/JC޺@eQ:^T J2\R2C9r"N8qy \yUpFDBS$5=}i$b W]x.4`tH9.u^kE/ee4#B26P+G-Q}["`qnb!9,fQ#El]pH%uWk KAH$#'AT@v1}!Lq+.69$1Oh>&Tdi7@krkeTGuqi0Lrsk;c2U x_"#;IWIxRs2:j)ۤʬ: 4̦&' 4RE0.:PCKRS*P2uEs^ °S)yz!&.4v˩\ؠ_8zV(`:^,`}@S0JbfAoft;3DzԒl- F) -U}_)9jP),ڶGs#s+20ūKUDv$RcK ̦ں&od籽]؍p{>0} %kvri޴L icFJWknxd̼ͯsY5s[UU*}{0^l/ti܀6鲙S6:KgLkmB6\/ aEm_k mLgU.w*@Vץ8^cp r 쁟:Ҋrჳ.3?^ \O)K0oAYet}-=ӎw0Pe)y9fX-bj`*Y7 v њ *_ 5-1'y=sf9?StmQ"77Kj9ܮS֕t;n>ٜޯŶK\ᯁkȽ6Olڿs/}ye˨ãb\">nB}cMAoyK!7Nf-R|n.hy¿u%9 -"S Qjs QO6AOX*)O"]C'}҉6w^}C+FZ3iFjWl`gm-洮gV{\YS"&MR[b:,n"3t)^OrȨE¡.58R]_S?k+좗:qo/?w,ǘ7]dž; r-W'?ϸebfTG5zېTAg. {5e}G}շ|osklEN(ķe W`vWtmkK~T3Wb2Eyu.kqSvg~X-ws)7hzCfqtʫ fȱ| dHrRʠpaa;˴<^D9g*; V<@e$lS֛O|)}K(xRٌq\Qsͧ˕*l'=zu9i[\,}v5|Ҳ:LYk8r=WN=9r&I1ڛ)R*GuV}Mod(m6IM% ~ՉC1tpV:% [gm;9}j/yPqMԔї}HXDž^*xjn^ U"8ۚZ~zӦr9ޣ}cyw/5ϽfhyWz̢{fA V,7;MlB{]l YF9?%eVqGcTz)nfyһm_], >W ]vMoM n)]sʎݠ~uM@myWn:M[BdLӊtnWrcedވjr zl3p|x4)\,ÓEE ~R};J&=j^ܿhjݩC݋}fIG"V(4'Vc|}`9OxRWi}'ԋx 8׎n ^˫;٪̨x.^lXyN!0Wu?RPGV]v^.ɞ!r9m] [^nи56w .ܶׄm mInBiW?{[_Gg?DU?{3"myy$v:bf%,Մ}U7odOݬf!TUL<?p߄]}oώ>v#Lrk\ ^#?PO޾b~ri=3A7)WXy F ɶ{k:Y9a}<Ɉ KUHUn]b<ƽ*;\UŬ4k Opei͏ /nlQjNn.23uPԫ3dQTW-4Vxٱ6o֖zwVq3t05/DǺJ||h^\79fl~!6;$(gb%hjUq!E#I4Y$62~[ɨeX4cGz6S:H&"!yHs;~А}jQ4g֘%3_QR|aSVU5j]2]Cwm{Nx vUV}'rnMq;|.y9M82L\*zlNΤ-'̮7*qK34_HӪYv"޲!ztƆ|(k̙Te_D{6(!Do<~IhDTo’ -Jr/KM7z" lTmϞ˳:ЎZtQjPhG4A.W?IIm0^! 2!E:..I'$^CS$3a|oG2L,1;˂ >s@3&]`RK>l00DR4{L-L󌲸pS!q9v"TsPNJ+/VY +˴4CDgeշx<6=y]Y$=CMyu6[8lq_|(qvW̕@lC\gq[=r,_]akXekUAQwނ 9Rƺ]TmaؿvO$uox /oLwB}缙( ғLl았"VYUBDzhk/= 5RhMS2x;19Ψ\ByFw/,- IW EDWJSӒhJ HR6ϡh97tu iS鴞8LYş~o4)D)}5(eMqZ>͘KO[V~6L_ԀQm:X%[({3ϺsEk퍲dCG^{-1 Yi'oQ) L-g HR~,a'+|Kr+̒R(e*Ҩzc/ 2'r&S2 g|b(`ʫsT𧳘#Q1a#D$ h#3P3G5J,,cNr5[0yKJ8yiR627k<;v %1ٖ:Ci6U+4r> /s726ӅȆ %*@2'@5Pq^tiah?kJ5-KdǼ3{T-=r6tE@=-qΑLA3% 3@-T9%OtѴOo[/(tOtÊ3MP4DH5+S1:s'4|DLUUG3, vVuQT7UQUES=(ϒH1ҭQ0UZ B5 Eh4A)3CjWRlt P+|R{]) TOYMSNc'Z{5IC&iuQu[et7RM &J\@?(L4"1;o 9|TO1 *sZZO3X1#16-uuQmT)R)BfVgl5iP/UO(2C`jVZbWX L&lԈ&6X3}vˣ"QqJpqU$t-.vٔ4ߋX0s6Fth9ekε#Ofkr,i=Q_x4[m8X6wwp7\?75=r]h mc6JE1e@uY[kzEPCGQOx7yz0Ur͊g+ySH ѷ2_㖜foC䞯A#)ɅuE~e)3|iV,9Ix]kl3ׯ&sPQxK}X{ "׸L9cAQ.xE+6bY{)s8lwYT؅p)=T1rX#w7M"<蠡^ZsbVXgO{͉a!9UdjՋ5XFGUEDCw0!uLNDU]k?Ct?* /m^ryyb1QXJdU},aXy TZOU_؂t{DK$`92}4i~%Λ5Z7m6)gy~pmo U+4B4'sդG%Sg:+ڄZu]9j9a3:gsvE) F uo9{:{_zw9"%>XX򙆳sL0+&}DN:Z=:U<ٙA珨oTXdي7yv>d/ؗVz ;Js3#qCXySR" VzIM?5#G5ֶk[,z]5⛍;v;y''EgP}[+&:kp1ĆKrSyW'U/;e[r99uE\Er{;1ܒMV4vIizo/\UxDhTu؁—Kć \7q?ڻ![غ9 b=&E)|;}|Hey'L.K5mOexڵn>F*h"@,ǵ{e ;Yr2ŃU}'`noQpiW:|uғV+̝H)]lz=iOGX (g|+{> ]45sؗ+c[{(Aχu]r$ۑ#eݷ=W̯n,%^Ͳ:]ڛk{X^}~>47kE}$OC}u/Fkӣ~Ҽap͞b?{>Fv~W1<9<aW}n wJĶmN w)#_{Z_ҼcpsO [!y,vv\tR_igj]hpwa7C: e=_>m[۷Y> >.?rj/z?#Y'+ۺ/3]:Czd'Dҙ E/U6r/8,3:^nk35U=WνQ{~HG^ԟDa#d$e%f&ggɠcBai"j쪭!g/p0q12q/! ,s@42Fuض5BwVx9z:{;*O3P}vvx轋! „ 2l!D̛-~ti8L".FU$ʔ*WlS l٤OD䂾W(ҤJ2m4f?82۟(lBsNNk}k,ڴjײU iW콻vW[V߀3I}0Ċ3kg ~Wd7ӕxhE7.m4Ԫr2_2( [b亡W7‡i}sƗJҧSn}Ǔ/4;+D=U>?VŃß * !XO Zx!/Q ~zX߇!8"HmM)q-"eb5f#9#/:#$Eyd*"IL:$O8d;X%Yjiޔ[z a9]g&f٦i9'uFEʙ'}Y긧z(&" #:(2Ry\/6Z)jꙒx:L!*`:kZ椷+_ ;왾K_*,2^J;jG|b-%:wڂ;.~[.u⢻..q;/[o/oj<0[pc#0j0b C<1Y^żI1Cn^2%3̍2-Em35s+͜3=7%4E 4M׀-5Uo\X[m[{dZ6K]}6 6JfvPýs}wk͐{V8.#x&C>yȏS^k>Gܹo^::^۞췏3_<_?+o?]ѫNңh==7={?>_7_?ҟ5@ r T#;O  =X0D!K 0)\! aE6|T 1?9{(lpJ0J|xA'B֑h-F ""1oeЏC( @Kbq#9QC%)SS|8X?W²Ő%hi]%/8P2o!iuT';xⳟzM'ρVƝ(A J }hIBQah$)jэJ˴'GCLR"="%zh3XhnS1/#:I,:3*hfFT4,UMMRqH򧴋*|vz gT6Y?zNzɬE-u'nM\W)YB}*{]1SֽUb*_VF6lC]=2d>d)R2V l ;-VZY[l֦'zf[!f;!(w WA:Du[[$of %p%n.XVNvZvo`y֞L`_ڷos5&vo [ŅـZ6/=zX88)\AK\(w+._vzLV8ǐ!sa{d9@(#0Cٞ)Ԛ{ZKͮ 7[k3?hfVrӬ+8#M=d۾UV,UMz>|XֻƵm])tWo^5 IfL[FknuUKr<=P=Oavi7#*W?}eOe7 ˫2oyG| Vxk}v6u}q/³pXwzoFokb|moܴ3ߴQx%#ųO==uGNċ~cUJzkgۍ̝W9ח]鄓uŽʅkyۅ5sw1^v)ۺ[?9B&ZQ'{f8dw;^-ξم}>؇>ǟô<ع ZI^W\|UAYXm_&ȅ[IU_K^ Bޥ)`yT-͚ _ޙa`R ` r]) y} !] Va]GzeM ѡn!z` *a!:a ba b ݵ0R䕠!Jbb$vb"Y"z"(\ʡTC`ӝ_x!]( r'nb!֚(@N&Z'"š.`- ٟb4>_.z)6 2b>*4*"ޢ"<#1<"F!4"*- ё-#"]̙"]#C&*BCc31z#E"2FBFQ V&mc:?}#Cv^RDb~`3TG$Jc)vJ%Q`( KR ,A_$5U&:֚ #P"aUH}>ҢU^XndDd_8R.9F 0cye%{\8 %av3LEN#D:# )&Pe]ePɢjZm &0M^qW>YjYi&~T`[O.bT&>ڥEmdL^ejJZ^$d% d-T :fUޣCf?#e.fzet"/-&y>Hѩj&foFZ_m]&zhDF ]_QrF(g}FJgcf\ u&翝^bF}'.x'|VOhVm蹥NʧGb(8rj~*d[&hҧs):Ee">4E~$HvhZg'Z(caAbQ)tg_UcvTf&{(gg#ʤV聞((R>h#F&iM!ʨ瑪^$neX q_'mi0)"ێBjjNi"_W:GuIz'Xhu!x#r*d>d5*rj5' %>]&Nkhb"llΧ_MO b2k*B)~ =\Fj~n&bdvZ轔SjhzEX&gkǛQ~ݽ%yzE*c2e#nƕZ[bkyjrkajޏljlk+ski{k&?)jx+!:iƬ̂jS`jgqvl&&6)I M>, &mYܱ;.!!iLR,Ɏ%ێ*l+]_>rj`iV-֡)in&$B`R")A(m^"Gm"ZNy"$ժB*nBFWb)lZ.VGĆF(-Bn)Zkݺc6hާR+vZ,.-2/f;Ω.n^4>+Ă^nV)J*qj,r&+2gö-BUTr:b#D+rbRgVhNdYkI 0 8l'i$Rk>pC٢*ъ0tzoru0;cXLҩgvfUp *2~׾!*pj.Y,($B5.O7^1so W0cޚKξ1i^oV:p91om+qe( /m1k5.9j*H ,nvﵲ :2V,$R/ 'rJ֤{린n9+1޻'}7 \;n6sq0'{'/;ZqŒ2\w>얬2I)f/5'/PN֪q"2>C72q[?FFS4 'c1ߪ5go4&hmG^eN.1,CsEu-^󅲝EfJ_TReun& \OuasYtM*[SOh..F4e:KBV&K*gKFhm#l7^uA2oퟖe]e5bRn%om^uAq4=S)u)vquqkY\\kFr7z3{nGd3w=_iUT7iR1_a0ZRdW6r8_N%|\f@w6fF+X f/s~sٰ.^6vmu8+x,1gv87ype17QvDwZ|.'D*;LEyLo8 o#XvSW7^3 tLh4`ysyᗿ.Mqt*y, yYy@y-J6ԙsC'ys\+x%P{zӣ' 'y{/Ӷ]vug1doar>wpMy \ϫԅVj^Vz\N}/;לp<3#83uour䶫Ag&wOkL_GR9k6h 6~ky 2OXpP.'%; <ȓ-5X{9C|_B_czR;ؼLɇ3 3qAwN;^q{=CC~s{>\szჾx'W8i:56 ?Om|G{77;c/:t+3|~ӓv;}LbNDYms{Y;{Fk@|L]n^0G4/8K_xz8dj"Hx*IQ >o$'l:+pXhgtZfox\>w|^⿍**/+D2ÇB,B-"HI&EG̡E©L OOP>VWXYZ[\]^Ւ@KaT bRdeA+,lcmHtvwxyzul#ggn8H?Y?jP"7qթG!E$YI:X 1` j&…^2Bl0ΜCSSQNZǦ.UkX*Щ2(4ZzCVak.nmn!Xu;'/G)+paȑ%}*8Z,˶2ܷ3U? 8kPY uЧ][{yn}ҋ* 7]#3.u«:sV鈧JZ';{o׋z+|6=7\* @4d?OB @ 0pC5/(E A SDp-Fy`G.D!smG>t +%mH5H,,-DE'ˎ1wSK' -s94N< 2.=7ӣ2lfOPTtե3 QL3Q碴2%}Sԓ>4)8͐=eEU)U,T\ٌ>wISu[uaaMvDWo PbM)isbiO [$[MY5HXmH]]zUs=l )vg;>; a2d0G1u0-\EJHDp :iǛ?(l|[\`Ý8> xS(j&mx9xh7Qw4\,C&y} 6~U"W= E=\39DHN}e8'D/n;( v.α]W -!IM22b#g:ĔPR~2s8ƴ$M%KG>lp&GrD8G]BT; ?:Н&6YH[">2~*T gO!PBRjQ 5HCej;yG!VUx@ժZҮzV=g0QfɘzUѼeRטUbu [@dMitDZzTBV %b{6jeA;zX rղI}gY5<Wd5˲Nzie*lv-OwCe=a-ng;YIg5LϞn*~Q|\>vHխ~KּMV2\ohdYdhTC*"a~®WÌ N6*0{7޻~uC6Or1K/7kݪ7~bwy`m`(g( a%/_qiYB @[+PU\840['M*_s 60r@rG0~s#daC@et`pMz Ӽyƫ^:qN=96kꙇujnl5M]gc։oeۚ]t;g렘fCkXCu~3j1n,iv_E#EfiHx7fo%_n(̍!8=OxߌoIs8/c}t,׊]){f*}Sϯ*kVõ6y}b)=>>3.!^ฝxqNjcַJ(lQ/g=xɻ;-H 7\Y+|T tuiiGzo҉f+s7M@U9ۯ.T\69,ky鹵uϫ}[ָ܈Ǎm{l <%]{UJ"T}^}$ky_ w /ocw,]O_t a"==;C+P8;6[ús?;. 飼%ұ l T|@>̳dSCNk㾎k4{A{@@HAƫr+0Y@@ L@P:}ʺ`> BC * \k>6?nk"5̘.0A\=#!h@#D d$#{?cC39+#-2n)D1qB*D/kBکOB>´A6 Y8[﫶R?ӡ$EX{:ϢKTt#Kҟ]4F$<:Ĵ[f =#q"ECS\>;i3CW+!ěmD)T]bۻC28>=`* {,Ơӂ"CsDss.L]Dp$;Ó/QHeaR-^48}\?Ǣ;H[:Zȕl508l(Tt@#mڟADud;&ēI(I+6*<ƞ,ZEs% 8K4ɠ TBCKoș ƴB%LF*"A|tJD0 )˹*nr5C,ň39&-)4JE ڳ/GLr)I/#DB֌ƻ3Mh)7L" KXY{w$NKмFdJ۝\ LH|tNTL樰c%S: ;g6L.=TSAbl6FmLx1ITLTMT4=Ue4TdЯl0ZT9qUYUZUB"$G!Z NΚYUTemVg}VhJ=F*VuH,$#mRPXV)$%WtMWu:4Xm_}_[:S]Uߛћ(=^_`ȅVX7>-` ` ]GEim-ܡ ^anmY.$X Uv^_-^va b!A\-1թCG'v`T˹Ub+!>=Vb]+t2V*4 >9 =pYc:c, -H`%ʩDzUbcjiVREFG&JF֋I>VU co}M1vMm=am7Tˌ3<֓MdXd4"Y&[d<_q5[^V3lM5fT5\>dd %^c6Wffj CS8G iҀ|gFe9kOy'{gh\|Vv\=n_g= ~hMh6hxοWlh;hM!g‚d~UnU^8_AExлiNFihigihNRS{(Xjh6\jRj6Jvi[IꞶjfj#iFΙF%~SvY=0i揈:ױf8dܽkd`U峗S%BxdTm&]|7EQ=jʁf.}xmVB>Tsu 5ehFmвfl~n,0&KgF uUn d)4ܖmVR6E1BԾ! z DSBfG@cκo'pS~=(=bp Yed-E , z1]-~l~b[lZI,M/_me[O=:GQoն@a B>f4] i1~a*OBkMcEkrydjmOptT-=r!Չ\B[ eZ7R1^~yL"wUem^W:ts_nrva!Vc\q=mFht<&apfdĞ3+7ȨRѨlM0۔}`Tdc=%-h xW:Dpo& HN) k8-\5)i2U!td$C~PPFGѣQӧPJ!%kzxB99`_eyMSZrelݘz+͒}j{YNqخxlo^S3k̹j9YYxOK찫BVkdć64^)͛a+GڷZlvb@{ZһD'sy^Ͼ}:㗚vc#~vXǘ@WD2XonEXIHʆڍTDgBY(!D'vXw)ہP0bAyhsx#e.)V7%Pv)+:n&덻tJW*e}YjmԚZ. u+z9Lk,ozU&{Į’ɵI\ ;LbŃVn೙e* : F GH~&}Tx υ gH8! 1}Pv'HL"e;hw2i)ˋڞ)~yd D.6GNd6ݛxvR5ny.;- .j)-X4񑐌$' B'R~<;Ő: 7ExJL-U#ֲx>GR̥.wY9Kk PU:exۥ͐Dj[<ynz/S8̃MoEJFZqNTY'2 @JPGRf#mog'怃홲dFOhNQ? JҒ(SLyIhQg)83(DyHMRyP(5QP,ZXuJz՗եWT!uhMZךĦ% %B$։Rg}dh&ӺajVJ~nlMbC_sW~*;ؿNէ;]6 U!MjWۮⳬlH(XVo{h!jѯOwVM\k궐g,;- V_i]F\ H= s]vvL̷֢]%=m5-yK+5/jywܫxY8,93 FGL|pg;_6?-W ׌x1\z&rb ֿΧmYjc1xd`sʈKEHPzzSN,VN`eE_1π&Af*]_oG.a 6_s7NrЁ֜Ϝ΍jtL?*,O kzָuJAmBLt;y]-ҭ*ƼN؜t6Mjw0Zu&Q$:n_Z٢mF~JU֎Flg٦Q1JqٺJN?%g2mܘܸ:oK;#n8!Kf=L^LNβY}{Gkb9|@ƹַu鼺 ʥ=Xu\ĎQ#]BEtkW_ֻ=)_ -+ek9,az&+Bjz[.>ϼ M{׼GO $U_ֻ/QpzH=9/f׽uއيwcO`As[[e9}cwu{?OO~wꏿ G?ʕ7XWl$ k׀V}8VXF8I؁5 8$DX$$(,hB'؂084sW&(8QxZa\H\_b?^HI g(PY8l؆P8ih(jnxxxNTixkHC8eHՇr}؈hz7ȇtvXxXXX8*z8PpXbD8bV((bV؆x`TX`TǘH~(xب?8xHcqmX"Y[t  wDϘ'x+wxhc1[DEh.f3HGrv45xHX񸐎JyæOvp Cwa's]ONG#nᦑo y(ybWA.eNd#tFRtVvhDLnf"섓TAFydfpn&t6?Lń%5[U| bnґM!sަm%g]n 6gB#Fn@8|ـejfp1n`Sg{[oL}9XGs)_YzmP5g{ hs7je gjjfjǚLgolj[8擱s)[Y0(Dh6)iy<_kŹHֹ·uyڝs)\bpZRc&{ZxJY,fPrRJ*j'MIJʣmmclW]ez᪛֩S h3:3-'Zo)Ț{(L^:TgnQqt?:תr *ʮ#vcU9vI]hWj모(w9,5O::tNIWl)kx]9jD9^$37u#"J:w<wb[pt{IJӲnʱ6/)ASJU@7[8FILGORU{X;[۵G^ a;ʪd+gi jGŶgp[%%dKvu|+zK+9믆cĸa븐[`/&^K鷢+={GCۺ$] ;[+zicX[^Vƛɻ%WK᪺Cқ7@Býx⛾DC-d˻lӣw  Z5ɿJI=lZ(ƾ˼۬Ĭewތ`,\Ҭ y,i<}yjxZ-'NU[3\`Xτ^< d͘|X,Mm0#"]L/Zѯ&m>2sLӽ;ӌҊ,>=BKF F T ʤ(b/rʺ|ԟ/,C,ܬncqO7i |Ǹ5aS8Fø9܎L:8O=8<=-Uzͩ.Mpm V~.Lm̓`N!.Lݘ*,ސ='/~8>ߖ?>>#GۜƄO$~V~Kr`b>d^f~hjlnpr>t^v~xz|~>^~舞芞>>^~阞难>p~ꨞꪾ>^~븞뺾>^~Ȟʾ>^~؞ھ>^~>^~?_ H?_ "?$_&(*,.02?4_68:<_;DOCS/DESKTOP/ad_100d.htm0000755000000000000000000000731711656577042011457 0ustar Supported Adapters - Desktop Pro/100

Supported Intel® PRO/100 Desktop Adapters

This driver and software are designed to operate with the following Intel® PRO/100 desktop adapters:

Product Name Board ID #† Controller
Intel® 82552 10/100 Network Connection n/a 82552V
Intel® PRO/100+ Management Adapter 721383-xxx
701738-xxx
691334-xxx		 82558, 82559
Intel® PRO/100 M Desktop Adapter A80897-xxx 82551
Intel® PRO/100 S Desktop Adapter 751767-xxx 82550, 82550C
Intel® PRO/100 VE Desktop Adapter A19716-xxx 82562
Intel® PRO/100 VM Network Connection n/a 82562

†Board ID # = A 6-digit code with a 3-digit extension; printed on barcode sticker on the front of the card.

Also see the Adapter & Driver ID Guide: http://support.intel.com/support/go/network/adapter/home.htm

NOTES:

  • A "Network Connection" or "LAN Connect" is a networking feature built in to the motherboard, as opposed to a plugged-in adapter.

  • The Intel® 82562V 10/100 Network Connection, Intel® 82562GT 10/100 Network Connection, Intel(R) 82562V-2 10/100 Gigabit Network Connection, Intel(R) 82562G-2 10/100 Gigabit Network Connection, and the Intel(R) 82562GT-2 10/100 Gigabit Network Connection are supported by the PRO/1000 drivers.

Compatibility Notes

The following devices are not supported by Microsoft* Windows Server* 2008

  • Intel® PRO/100+ Management Adapter
  • Intel® PRO/100 VE Desktop Adapter
  • Intel® 82552 10/100 Network Connection

Last modified on 12/30/09 3:31p Revision

DOCS/DESKTOP/adpins01.gif0000755000000000000000000002127411656741062011734 0ustar GIF89a!!!)))111999BBBJJJRRRZZZccckkksss{{{,H*\ȰÇPHŋ3j 2tIɓ(n @ RʜI&J >LxA͟@ 5(C <_ʴSȐ*̧XjE U_R]١><@ӪUg=iCȰbw\L8)ܾs9a xJe8.@AV _7 HHa@[$ >L6V tb```,(@C Tj9֢kn``S6ANA &")/sW* pC DlxRN@p PGZD]yY p !A4dxJ-u d<]SR=aPP`q$`ꅒA(YWuKA[PQ vސE H0eA7dIU%Ad݌1@ PjfB`^=Y@AH f#cѥ" ( !@ &P1A $=䋗b 40gALڙI$Hxg@Tl*ܸ ,i=0,DK%W D8@vd|4 ]A7A01Pa`)F Ytn*I.ċJL1 UŽj<.iTŬz d (mP@L<|UC'`sHpF)d\*xH`KV'd) A3LtwnA$p)]F~AO UG (kIPʋ@ d񀬈 .(z1X>w'HA~qhQ[;4bm9l$ dvs0B$$|T](BhOyΗJVi;+JU@)OŒlQxrSd yK2hTJ׀~@[E9|/b$bY*k^P!NRu$EZQr.ȑ(>KOv`ŋ O>joekM)kWb>jmC^`%*"ejcʖmIkR$> Ye{X|m2zζҝn50MU$*%p @ 7.Omnl6o 7ۂx@D)3%RT@R"s{X. !Ӊ,&fBpmbk۶%ƭbzdrY}h¦9 o)4p} ]O @qqf p#U*햦W:j¤݇jX,`ȁs 1^S]{pS^޶Vl\|d(qp8x:_{2mwRǬ0_o%S@\%׀zHVU$Jc@Y2_z+{78eh(2ϧLCU `Ox6te{GmdBvRax>&5^Z'|1q'UERG O DKUhSQ6y%{ "ci&Ds$w5WG49%KF}p}f 0 0vr'aQgae3C]u_\5-Q`hXBp,iw{hsv)O.d|L=BgV4-ԂSxPNBh\soWkWm&QemD^qclj!LJTi%)Tyu/]Zc* 0rpS 7'Wt[cVw;gnjU|(EqSkW,]kv3S!_,2q{6;(pN@uՇL[Yj`n,q<51l>qbkˆ؎$FӅ !)$y)7jrhy 7Eфe48B5c|=qr[F&@tу1fgUHj:C8]PirAD~c24)N8iiI7]UgӸ0 @d2H[UkVo;x4x[|Z֐zX`gd]0Qw!$0HV A8”~FN3l8hC9IDa ӝ޹0p6y ?d"s0@7/̂z){$?)!ewDBG{xԞ KpPXhzq?[wOFD֘zQ75}>LN>d 񞡁6/щVi"3BݦoiН}81JK EpQf$ az| )H'6v%kM 3P/ze4Z;EqjI)<\lD*`Qa&)OGH pi:v#"voi ;xmfz!!jzs!bftPwksm'd"YtrS8 eom@ $@R{%a1AY9xY1pUPGxgp0-<'ڭ:gAhjVjHP{噷igOZ[{yw;׶ȱp[ŬKyG{[x&X4դngHKX3vGӘ*yv$b[ۦqxXtGv4:<'vG YQu6Kʺg8{j#Z1++azQ18kWp嶰jIj'LHIr{Q0*E@)a+ji 2xˆ&7bt@U:o\krb|s;"*L$$WPP 99l*!xIt/c!7i1vhf]|b o²k8A$gxKy[T0s;fS9Y4(ћfXEr 6t/+ 2vU0^p!n^\"@K;ӻEI w/Wx9`62+,C$wi,`R gyr֥`{/f<7ؖz!ŌǡƠ쁬rӸmҲ\|d\#PpJ8][Ѐ`]Ŝ]3hyh@PmbmU} Jhv5X5yB,v02Bpj'̥;-6Jy,}#1]t-ԑ7hM7ie3Lr[Šk1ÿ<-v}UQ7֗ 6PvX +kWÑ)N~A >μg #0@IujdmͭS pJB~2<@~Fv} y = ;;DBmUV[#-"HطkN]~RU aԤk<'NNx17 탼gy mI@ .1hj uSh?5kٟ.?ѱxzsn p 4 P=hB`6<,<2ƒwG/7 _E|^MBW=co@[@2m8!+o8 F$79Ѵ:$A@P{GoI X\%3lmPU0mNnsa?I^IqIIposkW H_[?/wǭܝq"` 'ߓھ&[{1[Qā߸%`ꌿ#~kxܼoP-[ɧҲ7/9p ގh TPA0t`؁%NX bG X`ȡdC 1@PT0H8@@OA (Q 9.ŐAC \@ Oj퐁Mp aևծX Ӝ,$xmC \P`6s/VܘOǑ5\ 2ǧ  PaQneHA^1 @2\9D+ ̴0G5( -gn b"=*$ IG| =Lp3gc\ @3`r,p jR@ )ʀ`-A2 (`h39k jHIj"* "Ў,X`BMG  &Џf,pL))*?Z:3 ( `/b25ZRJ HĹؠMLETʃqң2@pЎ2q 3`Ih$@)jS*A2 ML^tAa4+tQ6X  *l=X H)5w 6p mN Vk X"h4kG6'Rċql|$ V/̣ =`*hՉKKZuqɧY hN3􃄼5yO >HOg' XGpdٲ a.":2Ie.NjɁ(oh0w>(rK[SO0v[߂t @ӽ~lӟXG-Ԭz4Ib+ 9fQl^18qP-|6icR, \SK- _,5s~/N)&q .@.JE׾4A/zjBnS Y`HD 4IuX 8(~3OB Ф[v!Ug%/]#]p+g62 Dq;C!h8*#{LEu4,81$#WՒ}sˊ0.o$=^TD6rJݫ8d2(`$TrJP/@Xf`d~ e"v3,΃ D6<3GBGz 66:[[&%iZ l4 N`ubpԖa5,pHW皳 60k*]yu @π('vy%P;k6%9ZvvAB.>^=m7K۪uŭmw _og8xhx7\7r=qxw=~lm2!}MvY%O2?5}C <0  g_p;?9==h`ށp| 8@p9Y$[oC~[V{xҀQQZ|` }@^wzT ~ P.?j xkz H3@ ;i.֡@Ha>)< aC= x~z>}(vMOe#| (u<% %[˓;X >{+멎༹VҾś _&0z` |{:{PЦ :k:4ۀ`<<2\1s rI 3`8uA\/4,i}28)CC.53lC9ԸI9CC>䫞-CA 0DD\7LKDGDӱG.DLBܴL÷Q3DO Q,ESN76oovoz贔TI%)$IJUpu+J.U׿Z贔TI%)$IJU1?1!mĸԭ_Krq-}ֹ֒-s}*}/$G?$n6BOW?׿ZΞZzm#>h,ol>vo,* zՏ %?TI%)$IJYpofE,k\5ꩯMUmoi)6lFٿґ繍'ILmTz--peW0?ucݶ6U~S5ٳoC7~鿙"װmngB?Ig/6oٽoWwӝ?C$TI%)$IJ^s3Y0Ǡ8d?_o0KK^=S5^s+iD>K~[oYWS}G3ͣg/?/^r;փN~_ֽ+/@h.}i=_/$TI%)$IJXd8~5NȲhk,{IcUC޶j92l>Z3=rϳ#v07MjYj*ɰ1{Zm{XZǹw7kgK/{ETI%)$IJU]Oj%NZ{=&}=;J] x0p GrJkM8QXls2D_1OYN^G6G_gӿ Yf19ǐGo()8BIMKPuKPuKPuMbNmGOm_SPu6SPu6SPu6TAܖ/RmP+wwP+ڪP+ڪP+ڪQ:6Q:6Q:6OAKOAKOAKNffMUUL68BIM XICC_PROFILE HLinomntrRGB XYZ  1acspMSFTIEC sRGB-HP cprtP3desclwtptbkptrXYZgXYZ,bXYZ@dmndTpdmddvuedLview$lumimeas $tech0 rTRC< gTRC< bTRC< textCopyright (c) 1998 Hewlett-Packard CompanydescsRGB IEC61966-2.1sRGB IEC61966-2.1XYZ QXYZ XYZ o8XYZ bXYZ $descIEC http://www.iec.chIEC http://www.iec.chdesc.IEC 61966-2.1 Default RGB colour space - sRGB.IEC 61966-2.1 Default RGB colour space - sRGBdesc,Reference Viewing Condition in IEC61966-2.1,Reference Viewing Condition in IEC61966-2.1view_. \XYZ L VPWmeassig CRT curv #(-27;@EJOTY^chmrw| %+28>ELRY`gnu| &/8AKT]gqz !-8COZfr~ -;HUcq~ +:IXgw'7HYj{+=Oat 2FZn  % : O d y  ' = T j " 9 Q i  * C \ u & @ Z t .Id %A^z &Ca~1Om&Ed#Cc'Ij4Vx&IlAe@e Ek*Qw;c*R{Gp@j>i  A l !!H!u!!!"'"U"""# #8#f###$$M$|$$% %8%h%%%&'&W&&&''I'z''( (?(q(())8)k))**5*h**++6+i++,,9,n,,- -A-v--..L.../$/Z///050l0011J1112*2c223 3F3334+4e4455M555676r667$7`7788P8899B999:6:t::;-;k;;<' >`>>?!?a??@#@d@@A)AjAAB0BrBBC:C}CDDGDDEEUEEF"FgFFG5G{GHHKHHIIcIIJ7J}JK KSKKL*LrLMMJMMN%NnNOOIOOP'PqPQQPQQR1R|RSS_SSTBTTU(UuUVV\VVWDWWX/X}XYYiYZZVZZ[E[[\5\\]']x]^^l^__a_``W``aOaabIbbcCccd@dde=eef=ffg=ggh?hhiCiijHjjkOkklWlmm`mnnknooxop+ppq:qqrKrss]sttptu(uuv>vvwVwxxnxy*yyzFz{{c{|!||}A}~~b~#G k͂0WGrׇ;iΉ3dʋ0cʍ1fΏ6n֑?zM _ɖ4 uL$h՛BdҞ@iءG&vVǥ8nRĩ7u\ЭD-u`ֲK³8%yhYѹJº;.! zpg_XQKFAǿ=ȼ:ɹ8ʷ6˶5̵5͵6ζ7ϸ9к<Ѿ?DINU\dlvۀ܊ݖޢ)߯6DScs 2F[p(@Xr4Pm8Ww)Km&File written by Adobe Photoshop 5.2Adobed@     u!"1A2# QBa$3Rqb%C&4r 5'S6DTsEF7Gc(UVWdte)8fu*9:HIJXYZghijvwxyzm!1"AQ2aqB#Rb3 $Cr4%ScD&5T6Ed' sFtUeuV7)(GWf8vgwHXhx9IYiy*:JZjz ?ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^+Hyuר3.}b#g6Y3TTPfoŷ&k"JS 6^/uZ82o=,}|TT:ٱzڝӎck ϓPmLIEN^C;KgWخT9ݝYƚ ven|N'bt$y R%}Cߺ@Nb{۪Lg^T[ Ovz ɹDi?evu|nգ y馬* _uW|;} FH_'7?O~{ߺ_ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^vYޒjnN'EFcwIMՔ3xh*6~X`pK[ߺPv^2Y:$J<,KIQe,OSp$."}u7ߺEi\=Wuߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺUП>][3/1nϧL?aH1ΎRQE "{^V=q{svvSaC1Z:HcE,n;3fbOJ~{ߺ^}sU{ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkɌ'{K{{^׺uӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkɌ'{K{{^׺uӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkɌ'{K{{^׺uӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺHK__Ut+#ۻ?،)ޙ홖~?5bquy)H皦8؆i u/~b<|)woUv3:/֥uungCV?;A)Tː#W{[.cۏwn̏i溪g֮>OܹV57*>̫o(ޓ-Q4U3GM=׺?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺZ4o)]uZu&/odq3m\%Fou]!_GwOz^ߏ!jOToՇSC`r\ LZ{lmI/hWAOZ|Ì`ϒ?#~Fm~;zkx{?(wGm12}79"`ţ^OU|}o_*߿${-w?.],vDws#wxd((0{]WLdLD2u{_xݡ,5F}w}nWeٹ? K]nʩ}{L@Ԇ5Ћ4. ߺ_ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+/q^^/' &o:\t=)O)*$Se6vUm2sEc+&uUsYo7acv;l}= LmR1Tߑ}r #@LeT[ߺGߺEi\=Wuߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEG%eHjk騩TFsMQ)ift<ʨg`~J˷19+2+CK@QQO@Qnӑg|}|'.=ݝ[bki:AWI' 6ڔ]>2z>3|Mko1K_/Wlx9)rFmDY[69˂ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺU3W}O|;')C%T2 !T2IUݸf*y*ց'u?l;m&.׵7I{{U->EES5br8-lq$r՞{^׺uӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺUsω} "Wc_]O`|QKy }&9ꯓ㜦(d֋=dk!PTaI̋ tdϖvnZ4'|UeՔ["'gn;k&^6y.Ee7Zl$Tԏ-3R2jE[9[Bve׺9om ڟ{^go~C/wrvgt]Qt[g'{p̞ݡd谕!P& RIГi\=Wuߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺZ6ߐO߉&փndz1 7} fOk3RѮ{bkkњ UT!P5Oun1>Vv_h?3=H+q{w ) stW127~{ߺ[v!_wGɏksڞ׺D9˂ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺZ8 ~,pxp;- >? gI)%AXD //^-||b-NmM)6x8u>}w%a|6r nByS{{{^n(]&ߧ'l ^4. ߺ_ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺZv)̪?~wr쪣G@׺RMͻ#+dߒ}3gT~wlGP F MC%VCici皦MPQ ׺޾SܟK{05ۓ}us?>輾i%qvT|v"M]I ( [{usU{ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺUZ"US|mY׿%~Ro({Sۙ>Mwܡ⒁$3U4jc5I;8SM'~C~t^oEN;lg*iV>&D r*udEx5?ߺ^JT_]#^t_`lMݴUx}ݱ6 ymXJ*|ХnNr|$U;#xXruWӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺU vKۛnQ3XK{}e2O#N)1xj܎Tz/%1ퟷ2jlmpd)AEf2t41Vk%iL Tu-yZ7׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺT~juO{'dlύT=kLƟ]GVʋug"{3is;ŔFtZ@̳G迒;߿zvg6K;p]e7Yˡ7?7Wrq`{KEn ׷28)F*{nq4wkvYAwGF_ :ڱủ6l|f;Ledt׺ UE]Vk&c1tT +O]EQI5LXx#4. ߺ_ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺTؙ-S=6_olP.6&׫ܘzLU-<XR#Պ|svmn^Pdi먲e$ڴ7fN3h.Z(+rp["0ҏ{g_u.S}Ic(S1˙"B:Ѹq͒ QOM, uhǬ.n:NYܮ]GOkVs#e}[ BiqR 4J~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺD<7h|K&W>7ew>Zd}|];FkqebubG&h5-7F`=s{fnJSYܛw!K_sIMPSꨫ $ =5DO#^/x׾r]{C:w.: w'O씏cE;lv6M#giR"SBOt [tyʜjt-߻s׾ﯧ{u&'OGAOMfZz*h("#^}矧=#E; ܓ;fduNiv뢂zqkRT粔(Cd#^o  _S_cH_s~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^CAC쟛Ԙ:l}#$ԴPGMLƏ9lwH+KkW;uu{s 4-& jݯ%Lo iݤhhh.NDU{tquߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^|.ϏkwEW`ힿﺏ;*:s`Tm]ϓZ|c'%G9 İUS/C;?&CF>돿uo?YHEfc 6׺O-m'/]/{/[=es}{\&V-vqW 5*ih{tquߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^׽uՇ퇿uao~w{{^ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^׽uDOCS/DESKTOP/attnew.gif0000755000000000000000000001740511656741062011620 0ustar GIF89a#dXVWsqrpnoUTUNMNzyzvuvpopnmnlkljijihifef_^_[Z[YXYWVWǮQQR||}yyzsstllmhhiddebbc^^_]]^YYZWWXUUVÿhikdeglmosuwoqs`abҟһƺ755DBBB@@PNNMKK][[ZXXvttsqqiggSRR~~}|||{{yxxutttssrqqqppnmmmllihhfeedcccbba```__]\\\[[YXXVUUrrroooZZZVVVSSSOOO,#dH/].\ȰÇ#JHŋ3jQ$FIBԱɓ(S\ɒ(H@͛8sq@̟6xIѣH1^g]H&JU~4mDկ`Êe(f(cP]˶-K8ʽ!ԭݻx7f+i#y <,_J!̸1[#GAsDZSF|ÌB̠C49BE^r҉M[b!_O\hr G#U{1\xFR'޸PÕC;cEرOdX?UCAݾ cT߁:'`~$ ߂7Its./d("F\!7A,N'>H%-Ћ0t@cd8 x$dBZŔB*A =b \*E(0ULnOY9{0r'JA{zgfQN'e'N$S>N蠝Vʖy梥FfwzI\ީ%VgBA0j# d¨p -aR1\چJd*x{ץ"zjX.Oij~꼘$)l$ itG!pK1R04|1^Feqg֐0;y|2?11-m2y16a ͹/QŸy /B ^CE#xK@Јp D '@8AI; @QBHA WhD \b SXZ'D!FIL@BT`P4 ְAyІ@.0Jb ^U8DQ@p ^D)+HH~h"^^x) e1t#hAΉa$Pc'\=5R3ֲ$ FQ(ԑfI[R'JAt#id~2Dx@ T 2(BZN(RKԏt1̪*9I) )>Xcʛ2l{6ĉ~G<=FF> X` +B}UJ@R)h2)8gd7YJQWZkuZ bwF@Վ\? nB:;`!Ax` ljUّ23,f\"FQ"'j:)M[fA@J x U#%ZZ]fX$-t!ns#ݧP6RD V@ۂ85vpa"]%D15.^Žֺ֝#XH(B/|cHI;@3"5L1z,;>/}\*_Jx!:Fm)'fOY(f)la6S9 c49ޭ^EYD )" ]cr=bE =e7tx8ƫ5\l܈? WH"6mА%Xljܲ(`; dOː2ڙRHxgO&6*8!Q@[Ce!\d];!E6GYmp. PqE^]Z:k@7E.4H%IY2oq F^YD`I;ցuݐ=8ڢaxOF!⑫>S=RW̝S2\b7YCAWQp"I0eۖZ6ضBj4BuO>a tźMX,da֔nQmup e'?Wz? Ev-1\,8'AgshHY}!Bv"6y3a:A=ԽI DbwAp*6s"|C W/H ̓6Е.8A‰);r~?) Ծ?ːKؽ" Swr5 s}@ =aȗ^yS7dB`l])Q^i&WS'·IfcX^7E Br sGg {"h_Cv d;тQt^RwkO(^,yx=_g6`0 pxzs[suvPFWu#@0Զ`ЀVlEJe# dAqܔ+8<{oU0! h eDhKTu0oBlfDLwgIP_ljEMS:\ *DDq6} }Aqv@R|iNxue4 anXwC5Qt#&N VB5悇x0hr \r6;q $%qxoOhw p|R8} D2A}wHNW_Hy ~PtpX;tsH!(Ȃ )* {,.=In3b+ 4 4~PQ(Wt6&E9|MFX}DLx7EwSА+yF9%#זq{0UC:{Pⴇ\^8hh+?.FDfeAT?2C{]6b95PE0) oH4@QIgPy9E)~w>5A}kqjHyp)y ؒi_$HK@$cAuC$q dA8jbqai 9`on@dd6i*WR7Gi^ #aY }F*YqfY6a6}E1IyR+AȵwF\a ax 3) UFYXy  zyjH4|ʣWPO7r::&^YV a 韗zVț-}zjPj >K C{z&q9ҒZL9IW0I}٪P$NqY! 3t(D#vt h>f6]YraQtɤNW"V[HUƃXA*NYD0aoG!d{qvWWGd'ʫ&gVV1f ;pI!d@1C#+C`z^\ӧ5XPNPKA~PA4疵ozNW@U/fbqWpc&:W~ [5av~atQ+VAYHl]5cHFQX))˺)&_Q[VC  aU69Q0n+JDQgXu`;) r;)re[IZ+ꋩۛdҋ{L}  KjIZBa\ (fCڷIz [EgT\> t'"TU*I*B~PD4+r+Q7Qo֨5U?Ȫn; KJL쵩 B&*o?I|37MܰkʽSfU+6s\Ekǃ|w.`a~<]<)69zRه1 [kz,qmc)|+!@~9*\ mEll[L >-lp t`ke,ޞ~JWpܵ^?r!j?* =~m r w1یT.n3T^n$X. ֞lavt>"gE>Q+{b9WSnU{Hk])VmVOCF)($0/~ e)|tC.Y_fl])DY_Gq}-rKax${B}s=SRN}R-k,zsȾB1PN:kBHpw)BJ su@|cx! \ dbBQp}v obAء[Apyl!Oے(/0ܿO7o kTZ |!B:$XA .dP;޹ӰąkXG!-IPI0YÈ+zPMAH%J(gch̞DU ŏV WF!X`r3+Ck)ōyQۗZa%(޼|Z Ɲy5R܀Tg\U8[i_U%pn]Loi̚fO*)MN(󂘟^ަVHGm&Gw_$*njn#kB#㸓C"O!렋3LHFD`400K,NDL)$lq"cȓ,&Th[#?(dQB,D!E\8+I" @@"ŏRKb2#TDL8R7Գ9CO>́Ђ<> sqPD+,$]F#Im'J+=n5AK $GPI M5!T;21+=+]I1$WjU[$O$"B+Z8_1T"E3"$q\r ]|}eUXږoB^9UZ%;w!I]YupᅧT ;, +E| vFhhI#B9eD{e59f?a):P+27v_= @>.K>6E,Ys&gCDى"H+¹^}y($) "l[OOv9b.;K.Ksc}`2(oY$}]csvc)(3([QhUCM(w5؝{cA:KvD*Gz&Â}O# }ᡫhm#Qr2[F*!S ᲮzުWE4ӓ ,#$.-+,lBPᑡWhCP(?焸"&J=`#OZm2E*f̊ b''v}_tS<2g|VAF6ʍc8QwH'>ΌZ GHoD8?6K4$8&PCd%i1j'{!)x:b'MYE$'_<1]" ]y= hU_J rD96sq~)/Q2Rh6ϦMH)~|8b3c몠Ϊ+$a%<%ϩ\bL>"esWJ. SA+PA t( њ*N@(Hzz~N%r T NSiX4:RhMuST4DDORt :B7j8 )tdIP5I TUXyGJ.raER ҡL?S@\3fBH14_STo $c< [ XFV!Xx@5G,-VAj$"e 4׼rK޺V empu[<ָBn57}tI]Y׶=pur5-xD^Ps[nN'AD Ą/qoZ"LښPڄ`rLu0 ELQw'J)DŻJ[bg -s<;DOCS/DESKTOP/box.gif0000755000000000000000000000074711651733270011104 0ustar GIF89aM3!,MI8ͻ`(dihlp,tmx|pH,$J8ШtJZجvz zn|NnB. LJ+^̸ǐ#KL˘3k̹ϠC;DOCS/DESKTOP/cable.htm0000755000000000000000000000752611656741062011412 0ustar Attach the RJ45 Network Cable

Attach the RJ45 Network Cable

Insert the twisted pair, RJ45 network cable as shown.

Use one of the following types of network cabling, depending on your adapter and the intended use: 

  • For 1000 Mbps operation (1000BaseT), use Category 5 or better (must be 4-pair wiring). Make sure you use Category 5 cable that complies with the TIA-568 wiring specification. For more information on this specification, see the Telecommunications Industry Association's website: www.tiaonline.org.

Note: To insure compliance with CISPR 24 and the EUs EN55024, devices based on the 82576 controller should be used only with CAT 5E shielded cables that are properly terminated according to the recommendations in EN50174-2.

  • For 100 Mbps operation (100BaseTX), use Category 5 wiring or better. 

  • For 10 Mbps operation (10BaseT), use Category 3 wiring or better. 

Caution: If using less than 4-pair cabling, you must manually configure the speed and duplex setting of the adapter  and the link partner. In addition, with 2- and 3-pair cabling the adapter can only achieve speeds of up to 100Mbps.

  • If you are using this adapter in a residential environment (at any speed), use Category 5 or better wiring. If the cable runs between rooms or through walls and/or ceilings, it should be plenum-rated for fire safety.

In all cases:

  • Segment length is limited to 100 meters.

  • The adapter must be connected to a compatible link partner, and may be set to auto-negotiate speed and duplex.

  • Intel® Gigabit Network Adapters using copper connections automatically accommodate either MDI or MDI-X connections. The auto-MDI-X feature of Intel Gigabit Network adapters allows you to directly connect two adapters without using a cross-over cable. 


Single-port models


Dual-port models

 

Last modified on 6/24/08 9:27a Revision

DOCS/DESKTOP/caut2.gif0000755000000000000000000000065011651733270011323 0ustar GIF89aՈ|ɂvpjc]xtWkhQ_\KSPDFD>:88FDDSQQ_]]xvvkjj͵!",pHH.Ĥ83`ѐqH@dg"9J8CYxA['!0!`> BH"F$D\N4yB$;DOCS/DESKTOP/ce.gif0000755000000000000000000000203311656741516010700 0ustar GIF87a6/,6/H@\`B >ć^QF?Qȅ&1 d.#„r&6oz1N0WL)P&{<:RLB 9hҧ6qVXU~(*SEɎU6fYmiYrFś[ujJwؽ|sE ذە|>|W0NR]\fV1 Yh˝=7Z5CMei۟QW햽y;˙VrɉN]W}\?N )/! Sɟ?zs9h,b YMYgJ+9)*N(ݨ@^2 xH{[õ+!y%]ޘ-'Rë§,(:g ꍹ(i*Lǂ6 (2,' *&$n*/|h 6ア,CY?n/(=.-T*F‰нŒ_(1=}(w%'DdFR)6ަX7q0*H^}R~m.{&dohlI:Al8t~߉"]z{W[*<-G+4]앞kgIC9˪mf.Cu(UZS@^ަbПE;HAJIjV÷ Bsޯw-J&dD*cɭa-ZHͫi&͉*w1] P(!XKT=!`JԱ4- Umgrдy;\Jt,8qnr' u xPU!ĸ#{իAHҒ=W{4)Fæ'CQ^ҫ.J (t润lHzcuG,"͌∋b3S+8DOF*GN3A~|%&4Gfh*UåWBMj WI&EJѶvh.J:i*+ث@E%|9 iqS $'Ar _ӄ36q^TZYَN^i&#&v\PmUKESі,:53Rc1$Vʇ%۟xLpJFDW $iQzDN]1W3&mF($ S% LwRx.&]3 6r8Y9e;$KLq:"!U4^Ԯz\Z%gf*VչT vb٠QjqԜl1^p@T\./58T~j%4m.C- ALylD~b_r`[K~ U( E)ȘF^[-RDZhmtTM *avsɂPا P ___X저 T2Z$@Rׇh/m_u -1Uy&VJKa.s*@B Ű&m8PVњwЬ"M{_2qՊ!?=Re8번V1H<هr "9L@* q_anOk-8/<L.q!UcJ|2zьN *b2ȷ١ڍDIxN$v q{oa^-mwKɦ"g;/ؾI-$'(GsN[H3{Qzq[g3IŽreֵTEd hnHXvɵDt(<@_/CtKѨ$scʵjͨst#i:|o!ľt"u"ܑvNC1R_fՑtO}K_m澷{k_4wLm1;ZSw 0*~AvJsV=/rcv I}G5ё$T;5ZGYVͿ^咅=SeDsF^ͩ{鋩F-b>)/mookDTy3i}ߩf>.Gw^t 鴖k#wTb7|wSǀxv"aLgsyMtwl'es+r|"QHkBX[Wzu+' v(~8~Hy~7{ٗ'v4{'tG9Ck$&$vb2yVT0fL9ӆyd|:9 !R)#G2m(k~7FDh%zUCUbs;0R7w$Sx~vj5j9hy_H;v QiΔxl؉…脌k(q1:]È$Gy'9h{S>G7y"(agxBe&yWoh!\8NgyH 2y $Ibhh"K$vEXR8y'ySd2A]asHoX[ʼnmg.ȏot 2{=.؁GtY)vo)ϸN\a6H1'WBvyD#h_CRsi)<9? ɅxDhԏsX4ؐSȶ|q}ntT~IMm#ux&+U|SsI~~3~Ib-DٝwYX&s)W"r&:4z8:yo,>@wW:r2Dl+BڤNPZml7dpJZmJY"tH:Jduǚ:JxZ$Dg奅1呤e rCN%L*nB8FW*V1Ü:y:vR7|ih4'<3k\w~2y{bwv$i;Hx1LhD8Z7;]ʩYڝ)~= Yz)Oi JY~Y{J$Ӝȩ5ׂi)vy(ʖOw&ZwڍT7})|ITwzʃyg'WฅԒVemAI.HBڦ{X8=Tٓ:)2×hvc-,ɰ>j>}Io9Hd 9v*DT/!T:ɃXX2uʗaDR]K&)HgXh׮"ٰڟIZi{ֆjOLhhv |VMӮg|ι{Wpki‰_i|cu՚|)ɛ>#@_4;  ?z}ڭ٘h7KCȐk/6á@t-CX&K9ڌ~JCړ C.sdXkP6Nf@_YnD-UdUcBKOnF45ZDd")t〮&Y2 d04>'PU+32- ݳ=2Wn=-O q/qT,[QAy#QAIE&&ڲH Uf7(TmKiE迥"gN5S9>nG2^n5x!u%6 KIRע?,R 2iEO}V'XeHHNO;} >~NS!}>1<|$KmFr2&X'.3*5&yF')/璅Z]_N3T8NO$iaLUK=D/.v(5PFYl;idkAFT-$$!*E4l2^)NhEU=/O>4FNx1s./eLBແ,QN^.=+u.iZj55kxSwQt+P:\LݧXa76i$Okr䄥B9q"G2"rZUNiK`%t|_3fcf>?dFl\ڿT~M@jS=l?SJ'F9RH 4rDRJ-]SL5męSN=}yȊSPbʂ.Qx|BU+L("ǣ(SAH2Ӄ LE!BbNJ"ܨ&r X KǴ!QX:*V֛dʕ-_ƜYfΝgF6Al) YmRhC)S)X.Ƨ=ap"a&p6,uuWMoZWB!~ըix|=G^}fݿz(߬%jd.>kϵ<$1B)1D=<+CF, >OlBWdE_1FgFo1ǔTԱCxG!$E֎D2I%dI'2J)J+2K-(.K0$L3D"Y& T5ٜΚcO N;M@BE4QE#FOGJ/TIܔ +8 3N3Q983TytՕ6,U+"eUT?_C5a`6pKaMҨ Bm'I4y51ncIb!oFƖk 9U38leR=ˮ#%LOWe'b[c)ی]AiT.ӝ)RNDN [.թO2cRT5WEI3n)ikX:VլWYպ-u%כ82HJR _oƺ2V}*"y,dU/+lؘd'vL^|FU@Mݍ!<PJھ*B0E|Zҟ@WْoQ @maZJqralKwe3G9TŽ4@UV˺Wl݁C+<wד^ oثV4! GX TtY1"\9{EW34b]Hoͤe޷J ΚFG+ScnVs)ZJDZѬOQVBTUvi˛@3QYt9-^;_HjŻ<|OXvx|XXxPg!Ybܼ"&Nʋ?1B7Ɵ}UR(M\˼Z<|8ӄdYg(cKXezbM9ypsKX]Kˇ}r`pUL^rT5MzAPȺs X܎d\0Fnjd3Fjvܡ̆+òil@O$yؙw8D4SfS mLɈTRq)FKE G, 3iW`L##yh||ɵEl8Ln22:݌(רL8,CдJ+Ǿ%=鳍 Q-%"MBtM5XNL< $QެIXk |ʈ[8L9. 5 ƙ,S(fQjAS\LGtPd үdЏ J*N`*T'RO\\R8 I|sHJ;3S]NKpM*l,Q/UǔdF"`_EA^EO(Iѡ c8CdM`EK) ר69SBEۑ`+ (T&=$HJ.]~3d\z-6Gq#iB4b3V*>66 Ə=? ҖV`)S5^ZCO ¬a1Sqzcܭ3Fi`MKn۪kb{ ?ޤ'>2eNJ`Ҽ"Tru讪]ط흽s)HP #cYv*L;츕sq#CB5 ;ѕ_ڊrȅ,q}ʀ-hΈHNXjMZj5[ Z瑓-|EJ"bNKY0NO{ 1h）S¤ y钴kCZYjm-^A =Qri =\ i kf>ki7qӜџȞQrjXR.df[N$3Չ K&]!˻,qPA&AK H̖:jk.ˈUl&l}[jݫ }}s-.@^@bFվ4Ѧ؝h@,;v6猹1 {sn sF?;ts>/+=CsBsDGHIOt)8tJǒ NtP'R7rh`[Eq\îuUCXе.XDl*Yuavrq$ f?Q̃YZv?5&/O}ZVA_svoVrOJ[PRXw~v0,CQ_3β),O( o{}78$x"WC'yS=.թbL;,Uިˑ7 SHҿτD>ݑcTb).Q !)jF`CC;B(4Lxב:3J뎘y'k3CNyJwoX>ÿaWRVQaIJ$H|82Pӎʯ+c{ѣw2o)ON x)S]C:A^=22j:yy*!)mϦXӻA9҅#0 "ǐ I7pW- /c๷bAqR tG-DR?Z)O PŃVtT~j <\#L(bҬi&Μ:g<G6IcФ&LEjHƢH=t<)ТXФśmM"$Yr jPؖd]f*׼l:#ŨL6ʕrxERX+V~! Vz>Z{ܞMe1o1_[X0ۭOaWkBs.T;dβ`D6Ktes-+9զ.9$oեGYhbA`g)mV!V=dJ VfQQKEDheB%t|& fq臊sW]fT'.hW[=apIxDPb$RNnSmz$M$E;:B5dIuD`a'@u^X\wyzDo1r}ej"%dVS}g FGMJU#ta0!pY[lI=Xot)G*!}聘%Jƒ1I Fm5 2BvN 1F(`((nl)Aށd++q;WS)N{|w][yᾧTcN8*& Q w؍tַ%VRI{5Q]6Zb1Krd8j1EQrۍ4ҼZHMuΦM6:JvVc1է*%QDC=˥f+"pmѴV#[FU\Hو|"80Z] deU16\T0-ٲB/ifd{aiMaB]Q.!\AyhM/k!{VM"m85vFVd=o7䧫7\利6pڧw0ɜပ//BEi_@R&0Cp7$4d.+i )ߤ4֛U %I2y*nZ3n~JAMyȃሀ(vOF &e$/CL:Dp45[i>D1Ec\zaM+v a rNwƙ*p!X*!;4 ŷ%!~H9*dIĈ*DB  cULPi[Ŗc=6gCS#jk٘)lO\IqvMDģ;YЁ^{RF.wDVb8ŦA$LlxK릷1t2"k1LBF DeY[&/}DuE) uXҼg51e".~k0zZpH(ƒhhcHY+}DR7/<=׈$~n:ܻ*( _6yW KFJ}D u| T&U\%Q2a78MRB"NvR #:H`^$?QITb*ut%(qnc!@N~2OV2e ]&qȊZ Hj~[& .SA)yBiqg[wvpT-[WqF/#BXZ2'HJ)e#4C-Q:6cTbV+u)CB ?F]׾.آ<2L*R`%$R;H.(fGX䯳mg8vvP!: bb MPjܾ̀7apØ DYr+G~4O:"piTX-Sŷ9KT;KG6ֹ&@`Xsӗ98c.s`o9Bsn^C^ss窥*ʒ\̓6׉}Bm`slKW5q \Ԣ43fWyg*!EQl窨kD~nq:YݭP#e( #I~-ZMp^?'??H?Os- =}_?q `_q!_m1]9`BJ BVRtYNp]ϝRh)*-CZMƨ&Am~M]E v} ՛9]>=AԐN`V|hW}I P͟4I|ANE[N>PXjpԟ ЎVQ P4ӣq ͌қp">㍔Ku5N P6Lm`[жXjGwbyӲyd!: Ǫ=uU!ڕX~iY,: V|ΒmA^%Qh!̌! aGK#8 ˻P~Hk m!TbRiNkˆ;Pq".b&φSD`M49 A[%ݓC NrcH81\ dᅫI^AMaZALuXE-*D@܆LP!]mܕʍԣeeuRFlNr\Q#$iIMW."s"VuF!}GpdJtY ԻFR IÈ/zQpv?/1Ūl&P섈CqFdBɾ԰®pIMiUi_ܯy^u-ؔVDnWPB=^I`)i ڣp(&P)>n ,hmHc UfKeeUJ`_uU] Ňj8h^HԖE&eXh`D{fƣea>qøKxfNU?ҞIi‡rHkffUn؆ urbڝ-ݦT&噎9!7W Z-1Ys7ٝH柡γ0B.l!ob mQ A4Bf&C?qyA4EWI4 1q23:3@kE4b4IJ;JS@^ *^)^G:Os^Kc`QԭhJ@[ Zc=ҮGXfU^Py /5̓- ͬn, 3JUueZtHUoM_)*PJ΀&(^-&&L5cW] vEnzPq(SbiȄ2~m^tfcv=6;-X-#]c q$Ei-MKiԟͮ !_'bvt nCfJZB7whAF QgZn̈bHB%8Ǥt7}^W~ bQ Ą+2 >RLd݊PZs}G 7mUBZkęoFxc"JiZ]wAh&)iWfDҬQ7:/NLg$(_cz n/҅ea/ڇ449 (>34-+iqeHk+y)G9Z@Yyߟ瘠yAߢOP:gV{5Y::zr[as:G=k`ϺS7:++Z;1K8?{}7BC;zg{i_Qi36w𷏻U;A;[WX{E主?4ļA{;_t; <'/<7?>X@;DOCS/DESKTOP/d100.js0000755000000000000000000013666411701554270010634 0ustar /********************************************************************** ** ** ** I N T E L P R O P R I E T A R Y ** ** ** ** COPYRIGHT (c) 2005-2012 BY INTEL CORPORATION. ALL ** ** RIGHTS RESERVED. NO PART OF THIS PROGRAM OR PUBLICATION MAY ** ** BE REPRODUCED, TRANSMITTED, TRANSCRIBED, STORED IN A ** ** RETRIEVAL SYSTEM, OR TRANSLATED INTO ANY LANGUAGE OR COMPUTER ** ** LANGUAGE IN ANY FORM OR BY ANY MEANS, ELECTRONIC, MECHANICAL, ** ** MAGNETIC, OPTICAL, CHEMICAL, MANUAL, OR OTHERWISE, WITHOUT ** ** THE PRIOR WRITTEN PERMISSION OF : ** ** ** ** INTEL CORPORATION ** ** ** ** 2200 MISSION COLLEGE BOULEVARD ** ** ** ** SANTA CLARA, CALIFORNIA 95052-8119 ** ** ** **********************************************************************/ var Results = new Array(); var URLTarget = "_blank"; var Document = document; var PathDiv = "\\"; var SearchList = new Array(); var ExcludeList = new Array(); var CurEntries = new Array(); function Search() { if (arguments.length == 0) return; if (typeof Array.prototype.splice == "undefined") Array.prototype.splice = Splice_Fcn; if (typeof navigator.userAgent != "undefined") { var browser = navigator.userAgent.toLowerCase(); if ((browser.indexOf("netscape") == -1) && (browser.indexOf("firefox") == -1) && (browser.indexOf("gecko") == -1)) URLTarget="_self"; } if (typeof window.location.pathname != "undefined") { var nIdx = window.location.pathname.indexOf('/'); if (nIdx != -1) PathDiv = "/"; } ClearArrays(); var Exclude_Warning = ""; var FrameCnt = top.frames.length; if (FrameCnt != 0) Document = top.frames[FrameCnt-1].document; for (i=0; i < arguments.length; i++) { if (arguments[i].toString().indexOf(" ") == -1) AddToSearchArray(arguments[i].toString()); else { var arg_array = arguments[i].toString().split(" "); for (j=0; j < arg_array.length; j++) { var current = arg_array[j]; if (current == "") continue; if ((current == "+") || (current == "-")) { var next = arg_array[++j]; while ((next == "") && (j < arg_array.length+1)) next = arg_array[++j]; current = current + next; } AddToSearchArray(current); } } } Document.clear(); Document.write(""); Document.write(""); Document.write(""); Document.write(""); Document.write(""); Document.write(""); Document.title = "Search Results"; Document.write("

Search Results

"); Document.write("
"); Document.write("
"); if (ExcludeList.length != 0) { for (j=0; j < Entries.length; j++) { var ExcCount = 0; for (i=0; i < ExcludeList.length; i++) { ExcCount += GetEntryCount(Entries[j], ExcludeList[i]); if (ExcCount != 0) break; } if (ExcCount == 0) CurEntries[CurEntries.length] = Entries[j]; } } else CurEntries = Entries; for (i=0; i < SearchList.length; i++) { if (Exclude.indexOf(SearchList[i]) != -1) { if (Exclude_Warning != "") Exclude_Warning += ", "; Exclude_Warning += SearchList[i]; } else { FindString(SearchList[i]); } } if ((SearchList.length == 0) && (ExcludeList.length != 0)) FindString("*"); if (Exclude_Warning != "") { Document.write("

" + Exclude_Warning + ""); if (Exclude_Warning.indexOf(",") != -1) Document.write(" are common words and were ignored.
"); else Document.write(" is a common word and was ignored.
"); } for (i=0; i < Results.length; i++) { Document.write("
"); WriteResult(Results[i][1], Results[i][0], Results[i][2]); } if (Results.length == 0) { var OutStr = ""; for (i=0; i < arguments.length; i++) OutStr += " " + arguments[i]; Document.write("
"); Document.write("Your search - " + OutStr + " - did not match any documents."); Document.write("

Suggestions:
- Make sure all words are spelled correctly.
- Try different keywords
- Try more general keywords
"); } Document.write(""); Document.write(""); Document.close(); ClearArrays(); } function AddToSearchArray(str) { if (str.indexOf("+") != -1) { var len = SearchList.length; if (len != 0) { len--; SearchList[len] = SearchList[len] + str; } else SearchList[0] = str; } else if (str.indexOf("-") == 0) { str = str.substring(1, str.length); ExcludeList[ExcludeList.length] = str; } else SearchList[SearchList.length] = str; } function WriteResult(page_name, page_url, description) { if (arguments.length != 3) { return null; } if (description == "") description = "No description available"; if ((PathDiv == "/") && (page_url.indexOf("\\") != -1)) page_url = page_url.replace("\\", "/"); Document.write("
"+page_name+""); Document.write("
" + description); } function FindString(str) { for (j=0; j < CurEntries.length; j++) { var Count = 0; if (str == "*") Count += 1; Count += GetEntryCount(CurEntries[j], str); if (Count != 0) AddToResults(CurEntries[j][0], CurEntries[j][1], CurEntries[j][2], Count); } } function GetEntryCount(theEntry, str) { if (theEntry.length != 5) return 0; str = str.toLowerCase(); var Count = 0; if (str.indexOf("+") != -1) { var str_array = str.split("+"); var c1 = GetEntryCount(theEntry, str_array[0]) var c2 = GetEntryCount(theEntry, str.replace(str_array[0] + "+", "")); if ((c1 != 0) && (c2 != 0)) Count = c1 + c2; } if (theEntry[1].toLowerCase().indexOf(str) != -1) Count += 8; if (theEntry[2].toLowerCase().indexOf(str) != -1) Count += 5; if (theEntry[3].indexOf(str) != -1) Count += 10; if (theEntry[4].indexOf(str) != -1) Count += 1; return Count; } function AddToResults(url, name, desc, count) { for (k=0; k < Results.length; k++) { if (Results[k][0] == url) { count = Results[k][3] + count; Results.splice(k, 1); break; } } var NewIdx = Results.length; for (l=0; l < Results.length; l++) { if (Results[l][3] <= count) { NewIdx = l; break; } } var NewEntry = new Array(4); NewEntry[0] = url; NewEntry[1] = name; NewEntry[2] = desc; NewEntry[3] = count; Results.splice(NewIdx, 0, NewEntry); } function Splice_Fcn() { if (arguments.length < 2) return; var InsertIdx = arguments[0]; var Count = arguments[1]; var tmp = new Array(); var ModArray = new Array(); var i = 0; for (i = 0; i < InsertIdx; i++) tmp[tmp.length] = this[i]; for (i = 2; i < arguments.length; i++) tmp[tmp.length] = arguments[i]; for (i = InsertIdx + Count; i < this.length; i++) tmp[tmp.length] = this[i]; for (i = 0; i < tmp.length; i++) this[this.length] = tmp[i]; return ModArray; } function ClearArrays() { Results = new Array(); SearchList = new Array(); ExcludeList = new Array(); CurEntries = new Array(); } var Exclude = "a add all also an and and/or are as at be but by can did do for from has have how id if in into is it no non not of on once one only onto or so some than that the this to too try two use want well what when where which why will with within yes you your"; var Entries = new Array(); Entries[0] = new Array(4); Entries[0][0] = "ad_100d.htm"; Entries[0][1] = "Supported Adapters Desktop Pro/100"; Entries[0][2] = "Supported Intel PRO/100 Desktop This driver and software are designed to operate with the following Intel PRO/100 desktop adapters Product Name Board ID # &dagger ..."; Entries[0][3] = "adapters connections support"; Entries[0][4] = "a19716 a80897 adapter barcode board built card code connect controller dagger designed desktop devices digit driver extension feature following front gigabit guide intel lan last management microsoft modified motherboard n/a name network notes operate opposed plugged printed pro/100 pro/1000 product revision see server software sticker supported ve vm windows xxx"; Entries[1] = new Array(4); Entries[1][0] = "cable.htm"; Entries[1][1] = "Attach the RJ45 Network Cable"; Entries[1][2] = "How to attach an RJ45 network cable to your adapter."; Entries[1][3] = "cable port rj45"; Entries[1][4] = "accommodate according achieve adapter addition allows any association's attach auto automatically based better between cable cases cat category caution ceilings cispr compatible compliance complies configure connect controller copper cross depending devices directly dual duplex either en50174 en55024 environment eus feature fire following gigabit industry information insert insure intel intended last length less limited link make manually may mbps mdi meters models modified more must negotiate network note operation over pair partner plenum port properly rated recommendations residential revision rj45 rooms runs safety see segment set shielded should shown single specification speed sure telecommunications terminated through tia twisted types up walls website wiring without"; Entries[2] = new Array(4); Entries[2][0] = "drivers.htm"; Entries[2][1] = "Install the Drivers"; Entries[2][2] = "Installing Microsoft Windows drivers for your adapter."; Entries[2][3] = "drivers install"; Entries[2][4] = "acceptable adapter add/remove after already any apply attempts automatically autorun before below cable cancel cannot cd click computer confirmation connections control dialog discovers displayed displays double download driver extracted files find follow found hardware insert install instructions intel intervention last located microsoft modified network new notes ok operating package panel plug procedure product programs r2 recommended regardless release revision runs screen select server software start support system them these transfer uninstall update user versions vista website whether window without wizard xp"; Entries[3] = new Array(4); Entries[3][0] = "support.htm"; Entries[3][1] = "Intel Customer Support"; Entries[3][2] = "Customer Support Intel support is available on the web or by phone. Support offers the most up to date information about Intel products, including installation ..."; Entries[3][3] = ""; Entries[3][4] = "about available corporate customer date general including information installation instructions intel internet last modified most network offers phone product revision site support tips troubleshooting up web"; Entries[4] = new Array(4); Entries[4][0] = "dupwindm.htm"; Entries[4][1] = "Configuring Speed and Duplex in Windows"; Entries[4][2] = "How to configure an adapter's speed and duplex under Microsoft Windows."; Entries[4][3] = "duplex link speed"; Entries[4][4] = "adapter administrators advertises allow always appropriate attach attempt auto available based been best cannot capable caution change choose click configure connections considerations copper default determine device differently direct disabled does down duplex either enabled establish experienced fiber force full gbps gigabit half identical ieee intel last like link manager manually match may mbps menu microsoft mode modified modules multi must native navigate need negotiate network ok older open operate option packets partner pass per performance performs present pro/100 properties pull receive requires revision runs same select send set sfp should specific speed suffer support switch tab their time up using windows would"; Entries[5] = new Array(4); Entries[5][0] = "hyperv.htm"; Entries[5][1] = "Creating Virtual NICs in Hyper V"; Entries[5][2] = "Creating Virtual NICs in Microsoft Hyper V."; Entries[5][3] = "hyper hyper-v nics v virtual"; Entries[5][4] = "aaaaaaaa able adapter added address advanced alb allow any appear applies article automatically available balancing based bbbb between bind bound box bridging bypasses cannot capable cases cause cccc center change channel check click cluster com/technology/advanced comm/virtualization command communication configuration configuring connectivity considerations consolidate control core correct cpu create createteam data dcb dddddddddddddddd desire details device different directly disable documentation does driver each enable environment error etc ethernet even example faster fcoe fibre file filter follow frees general get give guest gui guid hardware higher host however htm http hyper i/o ignoring impact increases information installation instructions intel interface iov issue laa last lets line linked load lose loss lower mac machine makes management manager manger manually may memory microsoft mode modified more move ms must necessary need netbios network nic note number nvspbind offloading ok open operating operation order oses over overview packet panel parent part partition path perform performance physical please port possible present prevent primary property proset prosetcl protocol queue r2 receive reduces remote require resolve resources result revision root routes rsquo run same secondary see separate server set several share sheet simultaneously since single sits software sr standard step such support switch system tab takes tasks tcpip team team1 technet their then these they throughput together tool transmit true tttttttt unbind uncheck under underlying unique up usage utility utilization uuuu validation virtual virtualization virtualized vlan vmq vnic was windows work www wwww xxxxxxxxxxxxxxxx"; Entries[6] = new Array(4); Entries[6][0] = "insert.htm"; Entries[6][1] = "Insert the Adapter"; Entries[6][2] = "Step by step instructions on how to install a PCI or PCI X adapter into a system."; Entries[6][3] = "hot install pci plug"; Entries[6][4] = "adapter additional anything before bit bracket bus case cause caution compatible computer configuration connected connector contacts contents cord could cover damage determine documentation down each edge electrical enabled end endanger error exposed failure firmly function get hot insert install instructions it's last later make master may modified off operating pci plug power problem push remove repeat replace required revision running screw seated secure see select shut slot special start steps still supports sure system table then through touch troubleshooting turn unplug until would"; Entries[7] = new Array(4); Entries[7][0] = "ipsecoff.htm"; Entries[7][1] = "IP Security Offloading"; Entries[7][2] = "Internet Protocol IP Security IPSec is a set of protocols used to help secure the exchange of IP data. IP Security offloading is the assignment ..."; Entries[7][3] = "ip ipsec offloading security"; Entries[7][4] = "algorithm assignment automatically compatible computations configure confining contents cpu data decreases devices disabled enabled enabling exchange features generally hardware help increases information intel internet ip ipsec issue large last left lso may mitigate modified more network note offload pane performance place port proset protocol reduce revision secure security select send set software support table takes those through traffic used utilization window"; Entries[8] = new Array(4); Entries[8][0] = "lbracket.htm"; Entries[8][1] = "Attach the Low Profile Bracket"; Entries[8][2] = "How to attach the low profile bracket for use in systems with low profile slots."; Entries[8][3] = "bracket install low profile"; Entries[8][4] = "adapter any attach away back before bracket carefully charge come dissipate follow future ground handling install instructions last low may models modified necessary need over package product profile re remove revision screws seated securing side sized slide slot small standard static step these they tighten until used using yourself"; Entries[9] = new Array(4); Entries[9][0] = "legaldis.htm"; Entries[9][1] = "Legal Information"; Entries[9][2] = "Copyright and Legal Disclaimers Copyright 2002 2012 Intel Corporation. All rights reserved. Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124 6497 USA Intel ..."; Entries[9][3] = ""; Entries[9][4] = "any assumes brands claimed commitment contained copyright corporation countries disclaimers document does elam errors herein hillsboro information intel itanium last legal make may modified names nor omissions other parkway pentium property reserved responsibility revision rights trademarks update usa young"; Entries[10] = new Array(4); Entries[10][0] = "license.htm"; Entries[10][1] = "Software License"; Entries[10][2] = "INTEL SOFTWARE LICENSE AGREEMENT IMPORTANT READ BEFORE COPYING, INSTALLING OR USING . Do not copy, install, or use this software and any associated materials collectively, ..."; Entries[10][3] = ""; Entries[10][4] = "about above accompanied accompanying accuracy acknowledge adapt addition additional administrator advised affiliates after against agree alleges alpha alternate any appear applicable application apply arise assign assignable associated assume attempt attorney author authorized back been before below beta bound break business california capable carefully cause changes claim code collectively commercial compatible completeness component computer condition conflict conjunction consent consequential constitutes contain context contractor contracts control convenience convention copy copyright corporation correct costs could countries create creator customers damages data days death decompile defect delivered delivery derivatives design destroy developed development device dfars directly disassemble disclaims disclosure distribute documentation does done duplication emulated enclosed end engineer english entirety equipment errors estoppel et even event except excluding exclusion exclusive existing expense export express extent failure far fees final fitness following form forth found free fully function future goods governed government granted grants graphics guest harmless here herein hereunder hold i ii iii image immediately implication implied important inability incidental include incorporated indemnify indirectly inducement information injury install integral intel intellectual intended international interruption introduce items its iv jurisdiction kind labeled language larger last laws ldquo lease legal liability liable license life limitation limited links loss lost machine maintenance make manager manufacture manufacturer mask material may media medical merchantability minimum modify nations necessary negligent neither network ninety noninfringement nor normal note notice number obligated obligation occur oem offered officers operate organization original other otherwise out own ownership part particular party patent perform period personal physical please portions possibility pre prevent principles private problems product profits prohibit promised properly property proprietary protected provided provision purpose pursuant rdquo read reasonable recipient redistributables referenced regard regulates regulations related release remains remove rent replacement represent representative reproduce research resolve respect responsibility restricted restrictions retain return reverse revision right risk rsquo running safeguard sale sample saving seal secret section select sell separate seq set shall signed single site situation software sold source specifically standalone state subject sublicense subsidiaries successor such supersede suppliers support sustaining system tamper term terminate text then therein thereof these they third those time title trade trademark transfer translate treaty type unauthorized under understand unintended united unless until up update upon usage user vary version vi vii violate virtual warrant warranty was were whatsoever whole without work writing written"; Entries[11] = new Array(4); Entries[11][0] = "warranty.htm"; Entries[11][1] = "Limited Lifetime Hardware Warranty"; Entries[11][2] = "Limited Lifetime Hardware Warranty Intel warrants to the original owner that the adapter product delivered in this package will be free from defects in material ..."; Entries[11][3] = ""; Entries[11][4] = "above abuse accept accident adapter advance against agreement agrees air allow along alteration america any anyone applicable applications apply arise assume authorization authorizes back becomes before below business calling cannot care charge claims completely consequential contact container contract control costs cover critical current customer damage days dealer defective defects defend deficiency deliver department described details direct disaster disclaims discontinued distributors does either element energy entirely equivalent essential event example exceed except exclusion explanation express fitness foregoing forth found free full generation goodwill ground group guarantee hardware harmless health hereunder higher hold implied improper incidental including indemnify indirect infringement installation installed intel intellectual interruptions irrespective issue last level liability license licensee lieu lifetime limitation limited limiting locations loss material may measurable merchantability misuse modified money must neglect negligence neither new ninety noninfringement nor north notice notwithstanding nuclear number objectively obtain option original other out owner package paid part particular pay place policy possibility potential price process product profits proof property proposal provided purchase purpose received reconditioned refund registered remedies repair replace reprocurement resellers reserves respectively return revision right risk rma safety same sample satisfied see set shall ship software sole special specifically specification speculative states statutory sublicensees such support systems testing their thereof these they time tort total traffic transit under user's verifies wants warrants warranty were whether whom without workmanship"; Entries[12] = new Array(4); Entries[12][0] = "lights.htm"; Entries[12][1] = "Indicator Lights"; Entries[12][2] = "The Intel PRO/100+, PRO/100 S, PRO/100 M, PRO/100 VE, and VM Desktop Adapters and Network Connections have the following indicator lights Label Indication Meaning ACT/LNK ..."; Entries[12][3] = "connections indicator lights"; Entries[12][4] = "act/lnk adapter amount between cable configuration connection data desktop driver flashes flashing following frequency good indication indicator intel label last lights mbps meaning modified network off operating power pro/100 problem receiving revision sending switch traffic varies ve vm"; Entries[13] = new Array(4); Entries[13][0] = "mang_win.htm"; Entries[13][1] = "Power Management"; Entries[13][2] = "Setting up Power Saver options and Wake on LAN on Microsoft Windows operating systems."; Entries[13][3] = "management power remote wake wol"; Entries[13][4] = "ability acbs access accessible acpi active activity adapter advanced after allow amount any anyway apm appear auto automatically available battery between bios both bursts cable called capability capable complex computer configured connect consumption content control converged data dependant detect development device directed disabled disarms disconnected display down dual duplex during eee effect efficient enable ends energy engine enter et2 ethernet even evolved example explicitly expressmodule f4 feature few following forced full fully function functionality gigabit hibernate higher however i340 i350 idle important included includes including incorporated indicate installed intel interacting introduce keeps lan last latency led limited link lit low lowest lp magic manageability management manager may microsoft mode modified mt must needs negotiate network nic note off operating option other over override packet partner period pf port possible power previously pro/1000 proset pt quad r2 readily ready reconnected reduce remote removed replaces requests rest restored resume revision s3 s4 s5 saved saver server set several shutdown shutting simple sleep small speed standard standby state status stay support system t1 t2 t4 tab then there these they timeout traffic transition transmitted turns type under up using variety versions vista vt wake were windows wol x520 x540 xp years"; Entries[14] = new Array(4); Entries[14][0] = "manage.htm"; Entries[14][1] = "Remote Wake Up"; Entries[14][2] = "Remote Wake up and Wake on LAN basics."; Entries[14][3] = "lan remote wake wake-up"; Entries[14][4] = "ability about accept acpi activates adapter address administrators advanced allow amps any apm area around arp assigned attached awaken aware backwards based below bios board both bracket bus cable came capability capable check choosing circuitry clock compatibility complaint completely complex compliant components computer concept configure connection connector consecutive contact containing contains contents control converged corresponds could cpu current d815epea2 data defined description designed desktop details determine development device different directed disk documentation does done down draw drive driver due each early either enable equipped ethernet event every evolved example extends feature few field find first fit following format fully function generally gigabit had header hibernate hours however ibautil implementation important include information initiated installed intel interacting interface intermediate ip keyed label lan last least leds level limited list locations look low mac magic maintenance management manufacturer many may memory milliamps mode model modified more most motherboard mt multiple must named necessary need network newer note numbers off older operating operating system operational operations os out over own packet partial particular patterns pci per perform pila8460bn pila8460f pila8461 pila8900 pin plugged pme port power pro/100 pro/1000 proset protocol provide pwla8390t pwla8490xt quad querying ram rating received receives reduces referred refers refreshed reloaded remains remote removed repeated repetitions represents request require resolution response revision routed s0 s1 s2 s3 s4 s5 section see selectable selectively sending sent server set should shutdown signal similar simple sleep slot specific standby started state still stopped such supply support suspend swapped system t1 t2 technician then there these they through times titled true turning type typically under up upon user usually utility value variety various verify versions volt vt wake was were whereas without wol work x520 x540 xt years"; Entries[15] = new Array(4); Entries[15][0] = "overview.htm"; Entries[15][1] = "Overview"; Entries[15][2] = "Welcome to the User's Guide for the Intel PRO/100 family of desktop adapters. This guide covers hardware and software installation, setup procedures, and troubleshooting tips ..."; Entries[15][3] = "64 hardware ia-32 installation setup software troubleshooting"; Entries[15][4] = "adapter additional advanced any architecture available based basic click column compatible computer configuration contents covers desktop driver family features follow further guide hardware ia-32 information install intel itanium last latest left link list make modified necessary network note operating overview platforms pro/100 problems procedure process refers review revision see select set setup software start step supported sure system table these tips topic troubleshooting up upgrading user's varies welcome windows"; Entries[16] = new Array(4); Entries[16][0] = "prosetdm.htm"; Entries[16][1] = "Using PROSet"; Entries[16][2] = "Installing, using, and removing Intel PROSet for Windows Device Manager."; Entries[16][3] = "device install manager proset"; Entries[16][4] = "add/remove added additional administrator advanced automatically cd change cl command compatibility connection control core device dialog directory dmix drivers extension file following gigabit help install intel last line located manager modified must network note options panel please process product program proset prosetcl refer removing revision rights same select server services settings software support tabs under uninstall utility windows"; Entries[17] = new Array(4); Entries[17][0] = "reqd.htm"; Entries[17][1] = "System Requirements"; Entries[17][2] = "System requirements for Intel PRO/100 desktop adapters."; Entries[17][3] = "32-bit 64-bit compatibility install pci pci-x requirements"; Entries[17][4] = "adapter advanced advantage architecture basic before bios bit bus check compatibility computer configuration dos drivers either following hardware hat higher hyper installed installing intel kernel last latest linux master met microsoft minimum mode modified must network open operating order pack pci platform pro/100 red requirements revision run server service slot software supplies supported supports suse system takes v2 vista windows xp"; Entries[18] = new Array(4); Entries[18][0] = "trbl_dm.htm"; Entries[18][1] = "Configuration and Troubleshooting"; Entries[18][2] = "Configuration and Troubleshooting Common Problems and Solutions There are many simple, easy to fix problems related to network problems. Review each one of these before ..."; Entries[18][3] = ""; Entries[18][4] = "ability accommodates active activity adapter addresses adjusting advanced affected after agent already among another any apparent applicable appropriate apps asked assumes attached attaining auto auxiliary available base basic been before behavior best better between bios boot bootagnt both bus cable cannot capabilities capacity card carrier category cause change check choose common communicate compatible compliant components computer configure conflicting conflicts connect connectivity connectors consider consistent contact cooling copper correct creating current customer damaged data default described desktop/management detect device diagnostic different disable discussion disrupted documented does down driver duplex each easy edge efficiency either enable enhanced environment established etc even exact examples exceed execution expected express fail familiar family fan feature find fix following forced frame frequently functioning further gigabit going hangs hardware here hub ibautil idle ieee implementation impose inability incompatible indicator information insert install instructions intel intended interrupt irq isn't issues jumbo kinked knowledge known lack lan last latency latest layer led length level light limited limits link list loaded look loose make manually many master match maximizing maximum may mbps memory mode modified monitor more multi multiple multiprocessor must necessarily need negotiate network newer note off offloading often operating operation opposed options os other over overdraw pair parameters partner pass pci pcie peak perform performance physical play plug points port possible power pre presence prevents problem process processor programs proper provide pxe quality questions rate re readme reboot receive recent recognized recommended related release reload replace reports represents require reserve responder resulting results review revision run rx same seat section securely see select send server service set several shared sharing shorter signal simple size slave slot slowest slowing software solution specific speed standard start stops such sufficient supply support sure switch system table teaming technically test them then there these threading time timer traffic transmission triggering trouble troubleshooting tx type unable under unload unpredictable unusual up upgrade utility v1 v2 vary verify version vlans wake while without wol wording work"; Entries[19] = new Array(4); Entries[19][0] = "pushinst.htm"; Entries[19][1] = "Microsoft Windows Push Install Instructions"; Entries[19][2] = "Microsoft Windows Push Install Instructions A Push, or unattended, installation provides a means for network administrators to easily install the drivers on systems that have ..."; Entries[19][3] = "driver install installation push unattended"; Entries[19][4] = "adapters administrators applies apps basic bit cd directory document download drivers easily equipment file following includes install instructions intel last means microsoft modified network operating product provides push push32 pushx64 r2 revision see server setup similar systems unattended vista win32 windows winx64 x64 xp"; Entries[20] = new Array(4); Entries[20][0] = "qos.htm"; Entries[20][1] = "Quality of Service QoS"; Entries[20][2] = "A brief discussion of Quality of Service QoS)."; Entries[20][3] = "balance load qos quality service tagging team"; Entries[20][4] = "adapter advanced allow bandwidth base before configured connected deal disabled does efficient enabled events first frame generation gigabit help high ieee implement include information intel knowledge last levels lower make microsoft modified more most must network note operating order packet prioritization priority priority/vlan pro/1000 processed programs proset pwla qos quality r2 real receive revision see send server service setting specify support switch system tab tagged tagging time under utility vista vlan windows xp"; Entries[21] = new Array(4); Entries[21][0] = "reg100d.htm"; Entries[21][1] = "Regulatory Information"; Entries[21][2] = "Regulatory Information Intel PRO/100 M Desktop Adapter Intel PRO/100 S Desktop Adapter Safety Compliance UL 60950 1 Second Edition CAN/CSA C22.2 No 60950 1 07 ..."; Entries[21][3] = ""; Entries[21][4] = "a1 a11 a2 about accept accordance adapter against antenna any as/nzs australia/new australian authority back based been below between bsmi c22 can/csa canada canadian cause caution ce certification changed china circuit cispr class classe cns13438 communications community compatibility compliance comply conditions conducted conformance conformity connect consult contact control corporation correct council country dealer declaration declares described designed desktop determined device different digital directive distributor disturbance document does edition efup elam electromagnetic emc emi emissions ems en en55022 en55024 encouraged end energy equipment eu european experienced fcc following found frequency general generates guarantee harmful help her hillsboro his home however ices iec immunity including increase industry information installation installed instructions intel interference international japan jf3 kcc korea last life limits listed low lvd mailstop manufacturer mark may measures modified more must ne nmb note notice occur off office operate outlet parkway part particular party people's permission phone pro/100 product protection provide pursuant radiate radio radio/tv reasonable received receiver receiving reception recognition recycling regulatory relocate reorient republic required requirements residential responsible retailer revision rf rohs rules safety second separation standards statement subject systems taiwan take technician technology television tested there these tick turning ul undesired union upon usa user vary vcci void voltage without young zealand"; Entries[22] = new Array(4); Entries[22][0] = "save_dm.htm"; Entries[22][1] = "Save and Restore"; Entries[22][2] = "Saving and restoring an adapter's configuration on systems running Microsoft Windows operating systems."; Entries[22][3] = "function intel proset restore save"; Entries[22][4] = "adapter administration allows any assumed backup been changed command configuration contained copy cscript current default directory disk diskette dmix drive driver error event example failure file filename floppy following former generally hard include intel just last line located may measure modified most multiple must navigate network notes open operation options os performed privileges program prompt receive reinstate requires restore result revision run same save savresdx script settings specified standalone such syntax system team these times tool type unstable using vbscript vlans was windows wmiconf"; Entries[23] = new Array(4); Entries[23][0] = "setbd_dm.htm"; Entries[23][1] = "Unattended Installation"; Entries[23][2] = "Installing the base drivers and Intel PROSet via the command line."; Entries[23][3] = "base driver install proset setupbd"; Entries[23][4] = "able above acceleration actions adapters add/remove advanced after agent already any application apply appropriate apps associated assume available base bd been between bios capable case cd change channel characters chinese chipset codes com/en command commonly complete components components/features configure core corresponds created current dcb default definition describes description deselect detects device different directory disable displays dmix does driver during dxsetup error ethernet even example exist fatal fcoe feature fibre file filename first flexibility folder following force full function get gui hide http i i/o i/oat ignored image include information instability install install/upgrade instructions intel invalid iscsi itanium known language last launches layouts level line list local log makes manager messages method microsoft modify more most msdn msi msiexec mst must necessarily need network note operating option other over package passed path preferred prior productcode programs properly property proset prosetcl prosetdx prounstl provided provides public reboot recommends reduced refer reinstall remove repair result return revision running same searches section see select selected/displayed sensitive server set setup setupbd should silent snmp space specific specify start status strings support switch syntax system system32 takes technology tested them then transform translates typical unattend under uninst uninstall updates uppercase us/library utility valid via warnings website white win32 win64 windows winnt without x64 xp"; Entries[24] = new Array(4); Entries[24][0] = "snmpwin.htm"; Entries[24][1] = "Simple Network Management Protocol SNMP"; Entries[24][2] = "Installing SNMP on Microsoft Windows operating systems."; Entries[24][3] = "agent management network protocol simple snmp"; Entries[24][4] = "about adapter additional administrators advanced agent alerts allow application autorun base before cd changes click communicate compile compliant computer configuration consoles database devices directory documentation download drivers employed event experienced features first follow information install instructions intel last manage menu mib microsoft modified more must network notices operating prior product protocol provides recognize revision screen see send should simple snmp software software/services specified start stations such support system tcp/ip teaming them translates updates utility vlans windows"; Entries[25] = new Array(4); Entries[25][0] = "team_dm.htm"; Entries[25][1] = "Teaming"; Entries[25][2] = "Description of ANS teaming modes."; Entries[25][3] = "advanced aft alb ans services sft static team teaming"; Entries[25][4] = "able according across act active adapter adaptive additional address adopted advanced advantage affected affects aft aggregation aggregator alb allow alternatively although among analyzes another any appear appropriately associated assure attention auto automatic availability available avoid back backup balance bandwidth base because becomes becoming been before begin behavior belong benefit best between beyond both bound bridging button cable cannot capability capable case cause cd center change channel check choose cisco click clients column combination common compatibility compatible component computer conditions configure connect connectivity consider contain contents continue control copper create critical currently data default delay denominator dependencies dependent design designated destination detect developed device different disable disconnect displayed documentation does don't download driver duplex during duties dynamic each effect eight either enable engine ensure etherchannel ethernet/data event example exceed experience failback failed failover fails failure fallback fast fault fcoe/dcb feature fec fiber fibre first five following force formed frame full fully functionality gbps gec gets gigabit go good grouping handles hardware highest hot however hub hyper ieee implement important inactive include increase information initial instability install integrated intel interface ip ipx issues jumbo last later latest least left lets like link list load located loms long lose loss lost lowest machine maintain make management manager manually manufacturers match maximum may member microsoft might mixed mode model modify monitored monitoring more multi multicast multiple must mvt needed negotiate netbeui network never new nic nlb/wlbs normal notes occur offload open operate options order original other over package packet pairing pane part particular pay per performance performing plug port possible preferred prevent primary primary/secondary prior priority pro/100 property proset protocol provide qos r2 rate receive reception recognize recommended recommends reconfigures redundancy regains rejoin releases reliability reload remains removed removing renamed replaces require respective restart restored restricted returned revision rlb routable routed rss run rx safety same schema second secondary see select send separate server service set several sft sheet should similar simultaneous single sla software spanning specific specify speed standard standby start static status still stp subnet such support sure switch system tab table tagging take tcp tcp/ip team technology temporary them then there these they third three throughput toe together tolerance traffic transfer transmission transmit tree tx type under until up updated various vary vendor verify version virtual vlan vmlb waiting waits way we window wizard works would"; Entries[26] = new Array(4); Entries[26][0] = "test_dm.htm"; Entries[26][1] = "Test the Adapter"; Entries[26][2] = "Testing the adapter in Windows and other operating systems."; Entries[26][3] = "diagnostics test"; Entries[26][4] = "about access adapter address allows availability below cable capabilities click communicate connection connects dependent determines device diagnostic displays does duplex each functioning hardware including information intel ip its last link lower manager maximum microsoft modified network operating optimum partner performed ping properly properties proset provide reason reports revision run select settings several speed system tab test these type whether window"; Entries[27] = new Array(4); Entries[27][0] = "trbl_win.htm"; Entries[27][1] = "Troubleshooting"; Entries[27][2] = "Troubleshooting PCI and PCI X adapters."; Entries[27][3] = "bus pci pci-x performance troubleshooting"; Entries[27][4] = "adapter after allow any appear attached automatically available been bios cannot cause clear code computer deleted device disable driver enable error event file full functionality functioning gigabit gives information install intel issues known last latest longer make manager may message microsoft modified need older open operating os play plug present problem process proset re rebooting reinstall replacing reviewed revision server session set ship should simultaneous software solution specific start support sure system table terminal then there these time trouble update upgrading versions viewer windows xp"; Entries[28] = new Array(4); Entries[28][0] = "vlwin.htm"; Entries[28][1] = "Join a Virtual LAN under Windows OS"; Entries[28][2] = "How to configure VLANs on adapters installed in systems running Microsoft Windows."; Entries[28][3] = "lans virtual vlan"; Entries[28][4] = "ability across adapter adds administration advanced any area attached based before between both broadcast building campus capability caution change child clients co collection communicate computers configure connecting connections connects considerations considered consist contents cross defined department desktop devices different dispersed each ease enterprise environments exist first functional geographically group hardware hyper ieee improve including information intel joint lan last least left limit local locations logical management match maximum membership microsoft minimize modified more most moves multiple must network note other pane parent partition per performance physical port pro/100 problems project proset protocol refers restricted revision running same security segments select servers set simplify software storms support switch tab table tagged tagging task team term them then they those together typically under untagged up updates users ve virtual vlan vm were window workers workgroups working"; Entries[29] = new Array(4); Entries[29][0] = "wminicdm.htm"; Entries[29][1] = "WMI NIC Provider"; Entries[29][2] = "Intel Network Adapters WMI Provider The Intel Network Adapters Windows Management Instrumentation WMI Provider enables WMI based management applications such as Intel PROSet for Windows ..."; Entries[29][3] = "provider wmi"; Entries[29][4] = "about access adapter allows any application apps assumptions available based between called cannot cim classes collected common configure consumer contains could data describes detailed device distribution dmi docs driver elevate embed enables enterprise external file format gigabit guide i independent information install instances instrumentation intel intelncs2 interfaces jointly kernel last layer level list local located makes manage manager manifest measurement microsoft middleware missing mode modified monitor more must namespace ncs2 network operate order page paper part pci pipeline platform please pro/100 proset provided provider refer reference registers related remote requirements revision root section see services set setup snmp software specification standards status such supported supports system technical technology then through type typical under user view vista wbem web windows wmi"; DOCS/DESKTOP/drivers.htm0000755000000000000000000000613111710273344012003 0ustar Install the Drivers

Intel Network Drivers for Microsoft* Windows* Operating Systems

Install the Drivers in Microsoft Windows

NOTE: This will update the drivers for all supported Intel® network adapters in your system.

Before installing or updating the drivers, insert your adapter(s) in the computer and plug in the network cable. When Windows discovers the new adapter, it attempts to find an acceptable Windows driver already installed with the operating system. 

If found, the driver is installed without any user intervention. If Windows cannot find the driver, the Found New Hardware Wizard window is displayed.

Regardless of whether or not Windows finds the driver, it is recommended that you follow the procedure below to install the driver. Drivers for all Intel adapters supported by this software release are installed.

  1. If you are installing drivers from the Product CD, insert the CD. If you do not have the Product CD, download drivers from the support website and transfer them to the system.

  2. If the Found New Hardware Wizard screen is displayed, click Cancel.

  3. Start the autorun located on the CD. If you downloaded the software package from the support website, the autorun automatically runs after you have extracted the files.

  4. Click Install Drivers and Software.

  5. Follow the instructions in the install wizard.

Uninstalling the Driver

These instructions uninstall the drivers for all Intel network adapters in a system.

  1. From the Control Panel, double-click Add/Remove Programs. 

  2. Select Intel(R) Network Connections Drivers.

  3. Click Add/Remove. 

  4. When the confirmation dialog displays, click OK. 

Last modified on 6/05/09 11:38a Revision

DOCS/DESKTOP/dupwindm.htm0000755000000000000000000001103211656741062012156 0ustar Configuring Speed and Duplex in Windows*

Set Up Speed and Duplex

In the default mode, an Intel® Network Adapter using copper connections will attempt to auto-negotiate with its link partner to determine the best setting. If the adapter cannot establish link with the link partner using auto-negotiation, you may need to manually configure the adapter and link partner to identical settings to establish link and pass packets. This should only be needed when attempting to link with an older switch that does not support auto-negotiation or one that has been forced to a specific speed or duplex mode.

CAUTION: Only experienced network administrators should force speed and duplex manually. The settings at the switch must always match the adapter settings. Adapter performance may suffer or your adapter may not operate if you configure the adapter differently from your switch.

Your link partner must match the setting you choose.

Fiber-based adapters operate only in full duplex, and only at their native speed.

Configuring Speed and Duplex in Microsoft* Windows*

By default, auto-negotiation is enabled. Change this setting only to match your link partner.

  1. Navigate to the Device Manager.
  2. Open Properties on the adapter you would like to configure.
  3. Click the Link Speed tab.
  4. Select the appropriate speed and duplex from the Speed and Duplex pull down menu.
  5. Click OK.

Intel® Gigabit Network Adapter Considerations

Per the IEEE specification, gigabit speed is available only in full-duplex.

The settings available when auto-negotiation is disabled are:

  • 10 Mbps or 100 Mbps Full duplex (requires a full duplex capable link partner set to full duplex). The adapter can send and receive packets at the same time. You must set this mode manually.

  • 10 Mbps or 100 Mbps Half duplex (requires a link partner set to half duplex). The adapter performs one operation at a time; it either sends or receives. You must set this mode manually.

  • Auto-Negotiation 1000 Mbps. The adapter only advertises gigabit speed at full duplex.

Intel® 10 Gigabit Network Adapter Considerations

Intel® 10 Gigabit adapters that support 1 gigabit speed allow you to configure the Speed setting. If this option is not present, your adapter only runs at its native speed.

If the adapter cannot establish link with the gigabit link partner using auto-negotiation, set the adapter to 1 Gbps Full duplex.

Intel 10 gigabit fiber-based adapters and SFP direct-attach devices operate only in full duplex, and only at their native speed. Multi-speed 10 gigabit SFP+ fiber modules support full duplex at 10 Gbps and 1 Gbps.

Intel® PRO/100 Network Adapter Considerations

The settings available when auto-negotiation is disabled are:

  • 10 Mbps or 100 Mbps Full duplex (requires a full duplex capable link partner set to full duplex). The adapter can send and receive packets at the same time. You must set this mode manually.

  • 10 Mbps or 100 Mbps Half duplex (requires a link partner set to half duplex). The adapter performs one operation at a time; it either sends or receives. You must set this mode manually.

Last modified on 12/30/09 3:51p Revision DOCS/DESKTOP/hotwin.htm0000755000000000000000000000352311656574604011653 0ustar PCI Hot Plug Support for Microsoft Windows

PCI Hot Plug Support for Microsoft* Windows* Operating Systems

Intel® network adapters are enabled for use in selected servers equipped with PCI Hot Plug support and running Microsoft* Windows* operating systems. For more information on setting up and using PCI Hot Plug support in your server, see your hardware and/or Hot Plug support documentation for details. PCI Hot Plug only works when you hot plug an identical Intel network adapter.

 

NOTES:
  • The MAC address and driver from the removed adapter will be used by the replacement adapter unless you remove the adapter from the team and add it back in. If you do not remove and restore the replacement adapter from the team, and the original adapter is used elsewhere on your network, a MAC address conflict will occur.
  • For SLA teams, ensure that the replacement NIC is a member of the team before connecting it to the switch.

 

Last modified on 9/03/07 4:49p Revision

DOCS/DESKTOP/hyperv.htm0000755000000000000000000002101311735070120011630 0ustar Creating Virtual NICs in Hyper-V

Microsoft* Hyper-V* Overview

Microsoft* Hyper-V* makes it possible for one or more operating systems to run simultaneously on the same physical system as virtual machines. This allows you to consolidate several servers onto one system, even if they are running different operating systems. Intel® Network Adapters work with, and within, Microsoft Hyper-V virtual machines with their standard drivers and software.

See http://www.intel.com/technology/advanced_comm/virtualization.htm for more information on using Intel Network Adapters in virtualized environments.

Using Intel® Network Adapters in a Hyper-V Environment

When a Hyper-V Virtual NIC (VNIC) interface is created in the parent partition, the VNIC takes on the MAC address of the underlying physical NIC. The same is true when a VNIC is created on a team or VLAN. Since the VNIC uses the MAC address of the underlying interface, any operation that changes the MAC address of the interface (for example, setting LAA on the interface, changing the primary adapter on a team, etc.), will cause the VNIC to lose connectivity. In order to prevent this loss of connectivity, Intel® PROSet will not allow you to change settings that change the MAC address.

Notes:

  • If Fibre Channel over Ethernet (FCoE)/Data Center Bridging (DCB) is present on the port, configuring the device in Virtual Machine Queue (VMQ) + DCB mode reduces the number of VMQs available for guest OSes.

The Virtual Machine Switch

The virtual machine switch is part of the network I/O data path. It sits between the physical NIC and the virtual machine NICs and routes packets to the correct MAC address. Enabling Virtual Machine Queue (VMQ) offloading in Intel(R) ProSet will automatically enable VMQ in the virtual machine switch. For driver-only installations, you must manually enable VMQ in the virtual machine switch.

Using ANS VLANs

If you create ANS VLANs in the parent partition, and you then create a Hyper-V Virtual NIC interface on an ANS VLAN, then the Virtual NIC interface *must* have the same VLAN ID as the ANS VLAN. Using a different VLAN ID or not setting a VLAN ID on the Virtual NIC interface will result in loss of communication on that interface.

Virtual Switches bound to an ANS VLAN will have the same MAC address as the VLAN, which will have the same address as the underlying NIC or team. If you have several VLANs bound to a team and bind a virtual switch to each VLAN, all of the virtual switches will have the same MAC address. Clustering the virtual switches together will cause a network error in Microsoft’s cluster validation tool. In some cases, ignoring this error will not impact the performance of the cluster. However, such a cluster is not supported by Microsoft. Using Device Manger to give each of the virtual switches a unique address will resolve the issue. See the Microsoft Technet article Configure MAC Address Spoofing for Virtual Network Adapters for more information.

Virtual Machine Queues (VMQ) cannot be enabled on a Hyper-V Virtual NIC interface bound to an ANS VLAN.

Using an ANS Team or VLAN as a Virtual NIC

If you want to use a team or VLAN as a virtual NIC you must follow these steps:

Note: This applies only to virtual NICs created on a team or VLAN. Virtual NICs created on a physical adapter do not require these steps.
  1. Use Intel® PROSet to create the team or VLAN.
  2. Open the Network Control Panel.
  3. Open the team or VLAN.
  4. On the General Tab, uncheck all of the protocol bindings and click OK.
  5. Create the virtual NIC. (If you check the "Allow management operating system to share the network adapter." box you can do the following step in the parent partition.)
  6. Open the Network Control Panel for the Virtual NIC.
  7. On the General Tab, check the protocol bindings that you desire.
    Note: This step is not required for the team. When the Virtual NIC is created, its protocols are correctly bound.

Command Line for Microsoft Windows Server* Core

Microsoft Windows Server* Core does not have a GUI interface. If you want to use an ANS Team or VLAN as a Virtual NIC, you must use the prosetcl.exe utility, and may need the nvspbind.exe utility, to set up the configuration. Use the prosetcl.exe utility to create the team or VLAN. See the prosetcl.txt file for installation and usage details. Use the nvspbind.exe utility to unbind the protocols on the team or VLAN. The following is an example of the steps necessary to set up the configuration.

Note: The nvspbind.exe utility is not needed in Windows Server 2008 R2.

  1. Use prosetcl.exe to create a team.
      prosetcl.exe Team_CreateTeam 1,2,3 ALB Team1
  2. Use nvspbind to get the team�s GUID
      nvspbind.exe -n
  3. Use nvspbind to disable the team�s bindings
      nvspbind.exe -d aaaaaaaa-bbbb-cccc-dddddddddddddddd *
  4. Create the virtual NIC by running a remote Hyper-V manager on a different machine. Please see Microsoft's documentation for instructions on how to do this.
  5. Use nvspbind to get the Virtual NIC�s GUID.
  6. Use nvspbind to enable protocol bindings on the Virtual NIC.
      nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_netbios
      nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_tcpip
      nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_server
     

Virtual Machine Queue Offloading

Enabling VMQ offloading increases receive and transmit performance, as the adapter hardware is able to perform these tasks faster than the operating system. Offloading also frees up CPU resources. Filtering is based on MAC and/or VLAN filters.

Teaming Considerations

  • If VMQ is not enabled for all adapters in a team, VMQ will be disabled for the team.
  • If an adapter that does not support VMQ is added to a team, VMQ will be disabled for the team.
  • Virtual NICs cannot be created on a team with Receive Load Balancing enabled. Receive Load Balancing is automatically disabled if you create a virtual NIC on a team.
  • If a team is bound to a Hyper-V virtual NIC, you cannot change the Primary or Secondary adapter.

 

Last modified on 6/01/11 2:12p Revision

DOCS/DESKTOP/index.htm0000755000000000000000000000102211656577042011441 0ustar Intel® PRO/100 Desktop Network Adapters /html> DOCS/DESKTOP/insert.htm0000755000000000000000000000534011656741062011640 0ustar Insert the Adapter

Insert the PCI Adapter in the Computer

  1. If your computer supports PCI Hot Plug, see your computer documentation for special installation instructions.

  2. Shut down the operating system (if it's running).

  3. Turn off and unplug your computer. Then remove the cover.

    		4.

    CAUTION: Turn off and unplug the power before removing the computer's cover. Failure to do so could endanger you and may damage the adapter or computer.

  4. Remove the cover bracket from a 32-bit or 64-bit PCI (2.2 or later) bus master slot. If you have configuration problems, see your computer's documentation to determine if the PCI slots are bus master-enabled. 

  5. Insert the adapter in a compatible PCI slot. If you install a 64-bit adapter in a 32-bit slot, the adapter will still function, but the end of the edge connector will be exposed and not connected. If this is the case, make sure the exposed contacts do not touch anything that would cause an electrical problem. Push the adapter into the slot until the adapter is firmly seated. 

  6. Secure the adapter bracket with a screw, if required.

  7. Repeat steps 4 through 6 for each additional adapter to be installed.

  8. Replace the computer cover and plug in the power cord.

  9. Turn the power on and start your operating system. 
    If you get a PCI or PCI-X configuration error, select Troubleshooting in the Table of Contents.

Last modified on 4/06/06 3:42p Revision

DOCS/DESKTOP/insscrew.gif0000755000000000000000000001616411656741062012154 0ustar GIF89a%JHIfdeXVWsqrpnoUTUSRSNMNJIJFEF~}~zyzyxyvuvpopnmnlkljijihifefede_^_[Z[YXYDzkkmffhQQR||}yyzsstddebbcaab]]^YYZWWXVVWUUVÿuvyhikdegpqslmoȚz|~suwoqs`abҟһƺ755DBBB@@PNNOMMMKK][[ZXXvttsqqiggSRRONN~~}|||{{{zzyxxutttssrqqqpponnnmmmllihhhgggfffeedcccbbbaaa```__]\\\[[VUUrrroooZZZVVVSSSOOO,%H>{x\ȰÇ#JHŋzU CIdPmĈq#(ɗ0cʜ0ʛAɳϟy y=*]ʔd3Dشի mF&`*lC Ū]kiٲFQ%eKnEo˞qʮ߿ +v,OZĐ]+Rs#kf*3q@fnN?7,qϼv;H^ތ3U赻q̽Z, 5]~!0I|u S'!y g+D|Bt=a~gB{"`&uǐq/y\7({"?Ca,S],ą4BÁH/p[B25?Z1|4M 4'(^["+Dt2pBHƗ " S^AuixHZ䮐 3+xОE|:O⩃12dL܅) r?D*`<){!-v/:OA Kd$M>̗Xd%tfbn* 0b%& |3xL2 ,`9IM>'PE+~8A4.D1d#NID@ ܚJXBJ!?3x㙤L)bb&2"m+5&B1+&ZH}-LuLͦ &D,4U*ExjPՁš~jdD*%tF/*kV b!E0q-Zf \e*LnR&DA +e :*ģW2e"6?r!x+#d(f("N|Ib!RBzX'/>6V 4W[Bndy_ *%v1V80Q&&L^2*0Èi,C'*)"8;djE R ֱ턯Y" a>dtJ(ٞbŔD2`LA2Uhm\gSZ w(X@dO HC$pV㥰/"'X F,&7??*Pg x e; e ͐ӞNRHH=TRlZmI^xX)Wjq8MFN4x 0#LA1H2 [!_ -]sDDQ P! c"2na_2 A& *˽A *:eE0M-j wJڨiih`J Q{}f]+*AB9ʊ"`]؄݊0yjhK2D؉= jib2纊(ip D@j Sp=Q : /iAz\6` <^@ٜP {аi'K'^K7 c;fiۄ^@`;1;{ iKhY2 F{y ZSL9Z(rh[zo n`ڀLrUW2A"t~|hkKhWWc[ yy @hiiq&A*A5YqF:!U.,pqD"Pʜ,|^:å_Tl ű!PƐS[ry!F =|g%qv' ܦmgݹG1P]M!F?OBѪM#*WT]hCGeޑ,ؠw$a>й߼ Zu5qXmn1Z3 n6\7 |0@*7)j"(S1؂M()M3>2=K ],;$۾M-e/AtNNLgNs.3ϡ>>1WM旮n|饾~3>B>N.㺾 *q&`8vzm.`?\>2mp"7VEE~^z~B^cֈަҎƕ@vHBF@ o.n+4(/mFkݦnp]@R"wЩ^CN*bTW#-SH)yE"HRFa]Q wZW;U^Xa Uw'X/^wqc6{QE^[嵠(ovX@5mܩ}U[ 04/jI l-N@&pg$" ǭR'-鯠r^#a  1D."'# ] d=ѣ2QhWq"o \%CE5W$a a$XAuBC%$ƢEFyɹѣE^k"5Qb(8#)@I1zzJM9 Q;)?v VHGZ4Q%̤kUzNԄP9`iš":EX,[IzY,o،[d;OK4g08uP-Wdw ܹa㋜cjֳ嗔5ٵAMOkP +d@uG$܋CGIFsxD^H:4=xMɋQwPGzh0o^"xi͠ϵ,(X;0 BA>A>;B$J Z [dϸAŃ`i !9`.)L9B O<ܑ>⅗H"Rp jC+PR=lhKlo0)E8P-NM8CI!qdԬl8) MrЁPz;҄Z~@FR*O+ẑ3e̴0OP#BWM8]4JT֨4``I氡\57t`H%0$*P^:Џt۲$Rؤ6P6Fn5ꀶP|s fRC;PY$T Z#we(2OC`T`!Ses>3syMH;`08VHLE|aTP0 9I[Vgz`$e$2Lk$ ?:L.YV= @A Tf7~2m^*ChI.%y?13mL6M<܇i0P!z"gdfRIlFb}m/>hH8VH6ݥFj򇭢"VO{gFvH6?& ?dTI翩A}E2PO&,ա@ҏxOJ:A F\2YA NisM?6":a Q8T aqa %C X6aCC|HE`nDd@Vc-RD lb "<ЊDɳV;DOCS/DESKTOP/ipsecoff.htm0000755000000000000000000000345111656574604012141 0ustar IP Security Offloading

IP Security Offloading

Internet Protocol (IP) Security (IPSec) is a set of protocols used to help secure the exchange of IP data. IP Security offloading is the assignment of algorithm computations from software to hardware. Generally, CPU utilization decreases and network performance increases when offloading takes place.

On Intel devices that support IPSec offloading features, you can configure those features through Intel® PROSet. For more information, select Intel PROSet in the Table of Contents (left pane) of this window.

NOTE:  Large Send Offload (LSO) and IPSec Offload are not compatible. LSO is automatically disabled when IPSec Offload is enabled. This may reduce the performance of non-IPSec traffic. Confining all of your IPSec traffic to one port and enabling IPSec Offload only on that port may mitigate this issue.

 

Last modified on 8/28/08 3:57p Revision

DOCS/DESKTOP/jumbo_dm.htm0000755000000000000000000001363011656574604012137 0ustar Jumbo Frames

Jumbo Frames

Jumbo frames are Ethernet frames that are larger than 1518 bytes. You can use Jumbo Frames to reduce server CPU utilization and increase throughput. However, additional latency may be introduced. 

NOTES:

  • Jumbo Frames are supported at 1000 Mbps and 10Gbps. Using Jumbo Frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.

  • End-to-end network hardware must support this capability; otherwise, packets will be dropped.

Jumbo Frames can be implemented simultaneously with VLANs and teaming.

To configure Jumbo Frames at the switch, consult your network administrator or switch user's guide.

Restrictions:

  • Jumbo frames are not supported in multi-vendor team configurations.

  • Supported protocols are limited to IP (TCP, UDP).

  • Jumbo frames require compatible switch connections that forward Jumbo Frames. Contact your switch vendor for more information.

  • When standard sized Ethernet frames (64 to 1518 bytes) are used, there is no benefit to configuring Jumbo Frames.

  • The Jumbo Frames setting on the switch must be set to at least 8 bytes larger than the adapter setting for Microsoft* Windows* operating systems, and at least 22 bytes larger for all other operating systems.

  • The Intel® PRO/1000 PL Network Connection supports jumbo frames in Microsoft* Windows* operating systems only when Intel® PROSet for Windows Device Manager is installed.

  • The following devices do not support jumbo frames larger than 4096 bytes:

    • Intel® 82577LM Gigabit Network Connection

    • Intel® 82578DM Gigabit Network Connection.

  • The following devices do not support jumbo frames:

    • Intel® 82567V-4 Gigabit Network Connection
    • Intel® 82578DC Gigabit Network Connection
    • Intel® 82577LC Gigabit Network Connection
    • Intel® 82567LF-3 Gigabit Network Connection
    • Intel® 82567V-2 Gigabit Network Connection
    • Intel® 82567LF-2 Gigabit Network Connection
    • Intel® 82567V Gigabit Network Connection
    • Intel® 82567LF Gigabit Network Connection
    • Intel® PRO/1000 Gigabit Server Adapter
    • Intel® PRO/1000 PM Network Connection
    • Intel® PRO/1000 PM Network Connection
    • Intel® 82562V 10/100 Network Connection
    • Intel® 82562GT 10/100 Network Connection
    • Intel® 82566DM Gigabit Network Connection
    • Intel® 82566DC Gigabit Network Connection
    • Intel® 82566DC-2 Gigabit Network Connection
    • Intel® 82562V-2 10/100 Gigabit Network Connection
    • Intel® 82562G-2 10/100 Gigabit Network Connection
    • Intel® 82562GT-2 10/100 Gigabit Network Connection
    • Intel® 82552 10/100 Network Connection

Setting Up Jumbo Frames in Microsoft* Windows*

NOTE: Jumbo frames are not supported in multi-vendor team configurations.

  1. Open Microsoft* Windows* Device Manager.

  2. Open Properties on your adapter.

  3. Click the Advanced tab.

  4. Select Jumbo Frames from the list of advanced features.

  5. Set your desired packet size (based on network capability).

  6. Click OK to apply the changes. 

All equipment on the network must also support the larger frame size. When setting up Jumbo Frames on other network devices, be aware that different network devices calculate Jumbo Frame size differently. Some devices include the header information in the frame size while others do not. Intel adapters do not include header information in the frame size. When configuring Jumbo Frames on a switch, set the frame size four bytes higher for CRC, plus four bytes if you are using VLANs or QoS packet tagging.

Last modified on 8/01/11 3:59p Revision

DOCS/DESKTOP/lbracket.htm0000755000000000000000000000424111656741062012122 0ustar Attach the Low-Profile Bracket

Attaching the Low Profile Bracket (Optional)

Some adapter models come with a small bracket in the product package, to be used in a low profile slot. If you need to install the adapter in a low-profile slot, follow these instructions. 

  1. Before handling the adapter, ground yourself to dissipate any static charge.

  2. Remove the two screws securing the standard bracket to the back side of the adapter.

  1. Slide the bracket away from the adapter.

  1. Slide the low profile bracket onto the adapter.

  1. Attach the low profile bracket to the adapter using the screws you removed in step 2.

  1. Carefully tighten the screws until they are seated. Do not over tighten.

You may re-attach the standard sized bracket in the future if necessary. 

Last modified on 8/31/05 3:41p Revision

DOCS/DESKTOP/legaldis.htm0000755000000000000000000000205611701323454012111 0ustar Legal Information

Copyright and Legal Disclaimers

Copyright © 2002 - 2012 Intel Corporation. All rights reserved.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein.

Intel, Itanium, and Pentium are trademarks of Intel Corporation in the U.S. and other countries.

*Other names and brands may be claimed as the property of others.

Warranty Information

Software License

 

Last modified on 1/25/11 10:21p Revision DOCS/DESKTOP/license.htm0000755000000000000000000003527311654245266011771 0ustar Software License

INTEL SOFTWARE LICENSE AGREEMENT

IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.

Do not copy, install, or use this software and any associated materials (collectively, the “Software”) provided under this license agreement (“Agreement”) until you have carefully read the following terms and conditions.

By copying, installing, or otherwise using the Software, you agree to be bound by the terms of this Agreement. If you do not agree to the terms of this Agreement, do not copy, install, or use the Software.

LICENSES:

Please Note:

  • If you are a network or system administrator, the “Site License” below shall apply to you.
  • If you are an end user, the “Single User License” shall apply to you.
  • If you are an original equipment manufacturer (OEM), the “OEM License” shall apply to you.

SITE LICENSE: You may copy the Software onto your organization’s computers for your organization’s use, and you may make a reasonable number of back-up copies of the Software, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual ("emulated") devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

SINGLE USER LICENSE: You may copy the Software onto a single computer for your personal use, and you may make one back-up copy of the Software, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual (“emulated”) devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

OEM LICENSE: You may reproduce and distribute the Software only as an integral part of or incorporated in your product, as a standalone Software maintenance update for existing end users of your products, excluding any other standalone products, or as a component of a larger Software distribution, including but not limited to the distribution of an installation image or a Guest Virtual Machine image, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual (“emulated”) devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. You may only distribute the Software to your customers pursuant to a written license agreement. Such license agreement may be a "break-the-seal" license agreement. At a minimum such license shall safeguard Intel's ownership rights to the Software.
  6. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

LICENSE RESTRICTIONS. You may NOT: (i) use or copy the Materials except as provided in this Agreement; (ii) rent or lease the Materials to any third party; (iii) assign this Agreement or transfer the Materials without the express written consent of Intel; (iv) modify, adapt, or translate the Materials in whole or in part except as provided in this Agreement; (v) reverse engineer, decompile, or disassemble the Materials; (vi) attempt to modify or tamper with the normal function of a license manager that regulates usage of the Materials; (vii) distribute, sublicense or transfer the Source Code form of any components of the Materials, Redistributables and Sample Source and derivatives thereof to any third party except as provided in this Agreement.

NO OTHER RIGHTS. No rights or licenses are granted by Intel to you, expressly or by implication, with respect to any proprietary information or patent, copyright, mask work, trademark, trade secret, or other intellectual property right owned or controlled by Intel, except as expressly provided in this Agreement. Except as expressly provided herein, no license or right is granted to you directly or by implication, inducement, estoppel, or otherwise. Specifically, Intel grants no express or implied right to you under Intel patents, copyrights, trademarks, or other intellectual property rights.

OWNERSHIP OF SOFTWARE AND COPYRIGHTS. The Software is licensed, not sold. Title to all copies of the Software remains with Intel. The Software is copyrighted and protected by the laws of the United States and other countries and international treaty provisions. You may not remove any copyright notices from the Software. You agree to prevent any unauthorized copying of the Software. Intel may make changes to the Software, or to items referenced therein, at any time without notice, but is not obligated to support or update the Software. You may transfer the Software only if the recipient agrees to be fully bound by these terms and if you retain no copies of the Software.

ADDITIONAL TERMS FOR PRE-RELEASE SOFTWARE. If the Software you are installing or using under this Agreement is pre-commercial release or is labeled or otherwise represented as “alpha-“ or “beta-“ versions of the Software ("pre-release Software"), then the following terms apply.

To the extent that any provision in this Section conflicts with any other term(s) or condition(s) in this Agreement with respect to pre-release Software, this Section shall supersede the other term(s) or condition(s), but only to the extent necessary to resolve the conflict.
You understand and acknowledge that the Software is pre-release Software, does not represent the final Software from Intel, and may contain errors and other problems that could cause data loss, system failures, or other errors. The pre-release Software is provided to you "as-is" and Intel disclaims any warranty or liability to you for any damages that arise out of the use of the pre-release Software.
You acknowledge that Intel has not promised that pre-release Software will be released in the future, that Intel has no express or implied obligation to you to release the pre-release Software and that Intel may not introduce Software that is compatible with the pre-release Software. You acknowledge that the entirety of any research or development you perform that is related to the pre-release Software or to any product making use of or associated with the pre-release Software is done at your own risk.
If Intel has provided you with pre-release Software pursuant to a separate written agreement, your use of the pre-release Software is also governed by such agreement.

LIMITED MEDIA WARRANTY. If the Software has been delivered by Intel on physical media, Intel warrants the media to be free from material physical defects for a period of ninety days after delivery by Intel. If such a defect is found, return the media to Intel for replacement or alternate delivery of the Software as Intel may select.

EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE, THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for the accuracy or completeness of any information, text, graphics, links, or other items contained within the Software.

LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION. In the event that you use the Software in conjunction with a virtual (“emulated”) device designed to appear as an Intel component product, you acknowledge that Intel is neither the author nor the creator of the virtual (“emulated”) device. You understand and acknowledge that Intel makes no representations about the correct operation of the Software when used with a virtual (“emulated”) device, that Intel did not design the Software to operate in conjunction with the virtual (“emulated”) device, and that the Software may not be capable of correct operation in conjunction with the virtual (“emulated”) device. You agree to assume the risk that the Software may not operate properly in conjunction with the virtual (“emulated”) device. You agree to indemnify and hold Intel and its officers, subsidiaries and affiliates harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of product liability, personal injury or death associated with the use of the Software in conjunction with the virtual (“emulated”) device, even if such claim alleges that Intel was negligent regarding the design or manufacture of the Software.

UNAUTHORIZED USE. THE SOFTWARE IS NOT DESIGNED, INTENDED, OR AUTHORIZED FOR USE IN ANY TYPE OF SYSTEM OR APPLICATION IN WHICH THE FAILURE OF THE SOFTWARE COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR (E.G MEDICAL SYSTEMS, LIFE SUSTAINING OR LIFE SAVING SYSTEMS). If you use the Software for any such unintended or unauthorized use, you shall indemnify and hold Intel and its officers, subsidiaries and affiliates harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of product liability, personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Intel was negligent regarding the design or manufacture of the part.

TERMINATION OF THIS AGREEMENT. Intel may terminate this Agreement at any time if you violate its terms. Upon termination, you will immediately destroy the Software or return all copies of the Software to Intel.

APPLICABLE LAWS. Claims arising under this Agreement shall be governed by the laws of the State of California, without regard to principles of conflict of laws. You agree that the terms of the United Nations Convention on Contracts for the Sale of Goods do not apply to this Agreement. You may not export the Software in violation of applicable export laws and regulations. Intel is not obligated under any other agreements unless they are in writing and signed by an authorized representative of Intel.

GOVERNMENT RESTRICTED RIGHTS. The enclosed Software and documentation were developed at private expense, and are provided with “RESTRICTED RIGHTS.” Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR 52.227-14 and DFARS 252.227-7013 et seq. or its successor. The use of this product by the Government constitutes acknowledgement of Intel’s proprietary rights in the Software. Contractor or Manufacturer is Intel.

LANGUAGE; TRANSLATIONS. In the event that the English language version of this Agreement is accompanied by any other version translated into any other language, such translated version is provided for convenience purposes only and the English language version shall control.

Last modified on 5/15/11 10:56p Revision

DOCS/DESKTOP/lights.htm0000755000000000000000000000407011656577042011632 0ustar Indicator Lights

Indicator Lights

The Intel® PRO/100+, PRO/100 S, PRO/100 M, PRO/100 VE, and VM Desktop Adapters and Network Connections have the following indicator lights:

Label

Indication

 Meaning
 ACT/LNK On The adapter and switch are receiving power; the cable connection between the switch and adapter is good.
  Off The adapter and switch are not receiving power, or you have a driver configuration problem.
  Flashing The adapter is sending or receiving network data. The frequency of the flashes varies with the amount of network traffic.
 100TX On Operating at 100 Mbps.
  Off Operating at 10 Mbps.

Last modified on 9/08/05 7:02a Revision

DOCS/DESKTOP/manage.htm0000755000000000000000000002521311734015456011563 0ustar Remote Wake-Up

Remote Wake-Up and Wake on LAN*

About Remote Wake-Up

The ability to remotely wake computers is an important development in computer management. This feature has evolved over the last few years from a simple remote power-on capability to a complex system interacting with a variety of device and operating system (OS) power states.

NOTES:
  • Not all systems support every wake setting. There may be BIOS or Operating System settings that need to be enabled for your system to wake up. In particular, this is true for Wake from S5 (also referred to as Wake from power off).

 The following adapters do not support Wake on LAN* (WoL) operations

  • Intel® PRO/1000 MT Quad Port Server adapter
  • Intel® Gigabit VT Quad Port Server Adapter
  • Intel® Ethernet Server Adapter X520-2
  • Intel® Ethernet Server Adapter X520-1
  • Intel® Ethernet Server Adapter X540-T1
  • Intel® Ethernet Converged Network Adapter X540-T2
  • Intel® Ethernet Converged Network Adapter X540-T1

Wake on Magic Packet

In early implementations of Remote Wake-up, the computer could be started from a power-off state by sending a Magic Packet. A Magic Packet is an Ethernet packet that contains an adapters MAC address repeated 16 times in the data field. When an adapter receives a Magic Packet containing its own MAC address, it activates the computers power. This enables network administrators to perform off-hours maintenance at remote locations without sending a technician out.

This early implementation did not require an OS that was aware of remote wake-up. However, it did require a computer that was equipped with a standby power supply and had the necessary circuitry to allow the remote power control. These computers were typically equipped with a feature named Advanced Power Management (APM). APM provided BIOS-based power control.

Advanced Configuration and Power Interface

Newer computers feature Advanced Configuration and Power Interface (ACPI), which extends the APM concept to enable the OS to selectively control power. ACPI supports a variety of power states. Each state represents a different level of power, from fully powered up to completely powered down, with partial levels of power in each intermediate state. Power states include:
Power State  Description
S0 On and fully operational
S1 System is in low power mode (sleep mode). The CPU clock is stopped, but RAM is powered on and being refreshed.
S2 Similar to S1, but power is removed from the CPU.
S3 Suspend to RAM (standby mode). Most components are shutdown. RAM remains operational.
S4 Suspend to disk (hibernate mode). The memory contents are swapped to the disk drive and then reloaded into RAM when the system is awakened.
S5 Power off

Not all systems support being awakened from a powered-off state.

Remote wake-up can be initiated by a variety of user selectable packet types and is not limited to the Magic Packet format. For more information about supported packet types, see the operating system settings section.

Wake Up Address Patterns

The wake up capability of Intel gigabit adapters is based on patterns that are sent by the OS. You may configure the driver to the following settings using Intel® PROSet:

  • OS Controlled - Accept all the patterns sent to the OS.

  • Directed Packets - Accepts only patterns containing the Adapter's Ethernet address in the Ethernet Header or containing the IP address, assigned to the adapter, in the IP header.

  • Magic Packets - Accept only patterns containing 16 consecutive repetitions of the adapter's MAC address.

  • Directed & Magic - Accepts the patterns of both directed packets and magic packets.

Choosing "Directed Packets" will also accept patterns of the Address Resolution Protocol (ARP) querying the IP address assigned to the adapter. Upon configuring multiple IP addresses to one adapter, the OS may request to wake up on ARP patterns to all of the configured addresses. The adapter will only awaken in response to ARP packets querying the first IP address in the list.

Physical Installation Issues

Wake on LAN Cable

For computers with a PCI 2.1 compliant bus

A Wake on LAN cable is required on all remote wake-up capable adapters when used in older WoL-capable computers. These computers are generally equipped with a PCI 2.1 complaint bus and the BIOS is typically designed for APM compliant power management.
NOTE:  Remote Wake-Up from power-off (S5) is not supported on the following adapters in computers using the PCI 2.1 bus. To use Remote Wake-Up on any of the adapters listed below, the computer must have a PCI 2.2 compliant bus.
  • Intel PRO/100+ PCI adapter (PILA8460BN)
  • Intel PRO/100 M Desktop adapter (PILA8460F)
  • Intel PRO/1000 T Desktop adapter (PWLA8390T)
  • Intel PRO/1000 XT Server adapter (PWLA8490XT)

For computers with a PCI 2.2 compliant bus

The Wake on LAN cable is not usually required for computers equipped with a PCI 2.2 compliant bus, as the wake up signal is routed through the PCI bus. This is done through the PCI connector pin defined as PME (Power Management Event).

Many of the newer ACPI computers also have a connector for the 3-pin Wake on LAN cable for backwards compatibility with older WOL capable adapters. In this type of computer, the WOL cable is still required for older 82558-based Intel® PRO/100+ Management adapter model numbers PILA8900 and PILA8461.

Slot

Some motherboards only support remote wake-up (or remote wake-up from S5 state) in a particular slot. For example, the Intel® Desktop Board D815EPEA2 only supports remote wake-up from a powered off (S5) state if the adapter is plugged into PCI slot 2. It does, however, support remote wake-up from standby from any slot. See the documentation that came with your system or motherboard for details on remote wake-up support.

Power

Early versions of the Intel PRO/100+ Management adapter are +5 volt only. These models must have the 3-pin cable attached for the remote wake-up function to work. These adapters are equipped with 3 LEDs on the adapter bracket, whereas the PCI 2.2 compliant PRO/100 models have 2 LEDs on the adapter bracket. The older +5 volt model adapters are not compliant to the PCI 2.2 specification and do not fit in a 3-volt only PCI slot due to the slot being keyed differently.

Newer Intel network adapters are 3.3 volt, but work in a 5-volt slot also. They are keyed to fit either type of slot.

If your computer requires the 3-pin cable, the +5 volt standby power supply must supply at least 0.2 amps at +5 volts for each adapter installed. For older PCI 2.1 compliant management adapters, the power supply must supply at least .6 amps. This value is usually listed on the power supply label as +5SB, +5VSB or +5AUX. 

If your remote wake-up enabled computer is compliant to PCI specification 2.2, it does not require the 3-pin cable for remote wake-up. In these computers, the 3.3 volt standby power supply must provide at least 0.2 amps for each adapter installed. You may need to contact your computer manufacturer to verify the standby current rating. Turning off the remote wake up capability on the adapter by using the IBAUTIL utility reduces the power draw to around 50 milliamps (.05 amps) per adapter.

BIOS Settings

You may need to configure various settings in the computer BIOS so that remote wake-up will work.

Many ACPI computers can be configured to work in APM mode. Check your BIOS settings to determine which mode you are operating in.

In both APM and ACPI computers, you may find settings for Wake on LAN under the Power Control area and titled "Wake on LAN" and/or Wake on PME". Wake on LAN setting refers to wake up events received through the 3-pin header cable. Wake on PME refers to wake up events received through the PCI bus. To enable remote wake-up, you should enable the setting that corresponds to your adapter connection. For example, set Wake on LAN to enable if you are using the WOL cable.

In ACPI computers operating in ACPI mode and using an ACPI aware OS, look for an ACPI specific setting. If you want to power up the system from a power off state, set an ACPI specific setting such as "Wake on LAN from S5" to enable.

Last modified on 7/12/11 11:31p Revision DOCS/DESKTOP/mang_win.htm0000755000000000000000000001754011734015456012136 0ustar Power Management

Power Management

The Intel® PROSet Power Management tab replaces the standard Microsoft* Windows* Power Management tab in Device Manager. It includes the Power Saver and Wake on LAN* (WoL*) options that were previously included on the Advanced tab. The standard Windows power management functionality is incorporated on the Intel PROSet tab.

NOTES:
  • The options available on the Power Management tab are adapter and system dependant. Not all adapters will display all options.
  • The following adapters support WoL only on Port A:
    • Intel® Ethernet Server Adapter I350-T2
    • Intel® Ethernet Server Adapter I350-T4
    • Intel® Ethernet Server Adapter I340-T2
    • Intel® Ethernet Server Adapter I340-T4
    • Intel® Ethernet Server Adapter I340-F4
    • Intel® Gigabit ET2 Quad Port Server Adapter
    • Intel® PRO/1000 PF Quad Port Server Adapter
    • Intel® PRO/1000 PT Quad Port LP Server Adapter
    • Intel® PRO/1000 PT Quad Port Server Adapter
    • Intel® PRO/1000 PT Dual Port Network Connection
    • Intel® PRO/1000 PT Dual Port Server Connection
    • Intel® PRO/1000 PT Dual Port Server Adapter
    • Intel® PRO/1000 PF Dual Port Server Adapter
    • Intel® Gigabit PT Quad Port Server ExpressModule
  • The following adapters do not support WoL:
    • Intel® PRO/1000 MT Quad Port Server adapter
    • Intel® Gigabit VT Quad Port Server Adapter
    • Intel® Ethernet Server Adapter X520-2
    • Intel® Ethernet Server Adapter X520-1
    • Intel® Ethernet Server Adapter X540-T1
    • Intel® Ethernet Converged Network Adapter X540-T2
    • Intel® Ethernet Converged Network Adapter X540-T1

NOTE: If your system has a Manageability Engine, the Link LED may stay lit even if WoL is disabled.

Power Options

The Intel PROSet Power Management tab includes several settings that control the adapter's power consumption. For example, you can set the adapter to reduce its power consumption if the cable is disconnected.

If Reduce speed during standby is enabled,  then Wake on Magic Packet and/or Wake on directed packet must be enabled. If both of these options are disabled, power is removed from the adapter during standby. Wake on Magic Packet from power off state has no effect on this option.

Energy Efficient Ethernet

The Energy Efficient Ethernet (EEE) feature allows a capable device to enter Low Power Idle between bursts of network traffic. Both ends of a link must have EEE enabled for any power to be saved. Both ends of the link will resume full power when data needs to be transmitted. This transition may introduce a small amount of network latency.

NOTES:

  • Both ends of the EEE link must automatically negotiate link speed.
  • EEE is not supported at 10Mbps.

 

Intel® Auto Connect Battery Saver

The Intel® Auto Connect Battery Saver (ACBS) feature turns off the adapter when link is down or the network cable is disconnected. After a timeout period, the adapter will power off. When the network cable is reconnected and link is restored, the NIC powers up and functionality is fully restored.

ACBS only functions when the system is on battery power. If the power cable is connected, ACBS will be automatically disabled. If ACBS is active, the adapter will appear to be powered off. If you have Intel® PROSet installed, on the Link Speed tab, the Link Status will indicate Speed: Not connected. Power off.

NOTE: ACBS will not function on an adapter if the adapter has forced speed or duplex settings. ACBS will only function if the adapter is set to auto-detect or auto-negotiate.

Intel® System Idle Power Saver

The Intel® System Idle Power Saver feature sets the adapter to negotiate the lowest possible speed setting when the system and network are idle. When the system activity is detected, the link will be negotiated to a higher speed.

To support this feature, the adapter must be

  • configured to Auto Detect speed and
  • connected to a link partner that can auto-negotiate speed

Remote Wake-Up and Wake on LAN*

The ability to remotely wake computers is an important development in computer management. This feature has evolved over the last few years from a simple remote power-on capability to a complex system interacting with a variety of device and operating system power states. More details are available here.

Microsoft Windows XP, Windows Vista*, Windows 7, Windows Server* 2003, Windows Server 2008, and Windows Server 2008 R2 are ACPI-capable. These operating systems do not support wake from a power-off (S5) state, only from standby (S3) or hibernate (S4). When shutting down the system, they shutdown ACPI devices, including Intel adapters. This disarms the adapters remote wake up capability. However, in some ACPI-capable computers, the BIOS may have a setting that allows you to override the operating system and wake from an S5 state anyway. If there is no support for wake from S5 state in your BIOS settings, you are limited to Wake From Standby when using these operating systems in ACPI computers.

For some adapters, the Power Management tab in Intel PROSet includes a setting called Wake on Magic Packet from power off state. Enable this setting to explicitly allow wake up with a Magic Packet* from shutdown under APM power management mode.

In ACPI-capable versions of Windows, the Intel PROSet Power Management tab includes Wake on Magic Packet and Wake on directed packet settings. These controls the type of packets that wake up the system from standby.

Wake on Intel® Ready Access

Intel® Ready Access keeps your network connection active when the rest of your system is in sleep or standby mode, so that content on your system is readily accessible. Requests from other computers will wake up your computer.

Last modified on 7/12/11 11:49p Revision

DOCS/DESKTOP/note.gif0000755000000000000000000000073211651733270011253 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/DESKTOP/overview.htm0000755000000000000000000000545511656577042012216 0ustar Overview

Overview

Welcome to the User's Guide for the Intel® PRO/100 family of desktop adapters. This guide covers hardware and software installation, setup procedures, and troubleshooting tips for these adapters.

NOTE: This guide refers only to drivers and features available on IA-32-based computer platforms and platforms based on the Intel® 64 Architecture. These drivers are not compatible with Itanium®-based computers. For further information, see the additional user guides.

To select a topic, click a link in the table of contents column to the left.

Installing the Network Adapter

If you are installing a network adapter, follow this procedure. 
If you are upgrading the driver software, start with step 5.

  1. Make sure that you are installing the latest driver software for the adapter you are installing. For a list of supported adapters, click here.

  2. Review system requirements.

  3. Insert the adapter(s) in the computer.

  4. Attach the network cable(s).

  5. Install the drivers.

  6. For Windows systems, install the Intel® PROSet software.

If you have any problems with basic installation, see Troubleshooting.

You can set up advanced features, if necessary. The available features and the configuration process varies with the adapter and your operating system.

Last modified on 11/22/10 3:56p Revision

DOCS/DESKTOP/pro1000c.gif0000755000000000000000000001342111656741062011554 0ustar GIF87a.+,@>?202:8:  }{y{wuwPOPONO}|}:8;DDFkknZZ\**+rrtBBC||}ttuccd[[\ѻ>?Bjkn`bfhjn|}x{PRTXZ\bcdfghpsu8:;HJKȿ "# 422VSSB@@#""wttfdddbbb``^\\/..wuuussKJJDCClkkhgg[ZZù!,@H*\ȰCŋ3jȱǏy#ȣ!Al(\ɲ˗/c@N Lh 6 J >SK!hMXjh҇RBJ:6Fl*r]˶mKI tQxu`Ia]r/kfA *"-)F N8i<^ͺ55&7g۾ K o*@Q0;!9P/ŹT@ݼ#fpΛ@4{V ֬5׏ M=$Mvf+ag߁Ѱ߂ @`-a$hT o hRwWIաAIJ A`,'#fI@PH&Q@8 ~>VY"fWց\dZ'Q^ uRFwVƹ ? ᥒ%Í*ԈaTD ]r@y rFZryi *%Ч.ڨ(Q*Цm h%\fzVWX`A `,QlY5"Zr JQ(]HP H Kba'X,l1gyF!/_ ڐn5GX![Bp↳ZkZ-$#KyiIdg,bڮ(doAsm{L#Քpg\Z!ӢX'j\^V9ZDYâ)iI, qW}&u drq`2=ٰD)IKˆ(}˛aYkŽ ^h6Y/y6D:28k!7NLB|`g-6QPuCF eHYt޺iB⧬UM%ba<  JMZ34']zY6Yv(XᘏZxi9cdi7[;籐bZ4adž'a]Ó5s!"CsC嘒,g%~0%nnaq7)_y[ = !]I]3T?iVڵUDlfa7] ["10-SOR9QJ\^" 7of(SeR,=A<&8i>y.qʳ% 2E_ WF10C 8*m 9 YeFY+aDBp)vBC8Aya Alɜ@PB@ҹt6-#xjӉ[#ahL}&Abႜ&.3by~(^#1f ? h(@v. s RNF{6DAheFbF$ bifA&jcZ]d) %Q(bEP jz`3gqV/Hf5Zk'ң?ʋ[9`-"k,Ԥa *jpjbCƉ7>DVa0C[9^ZM ;:XK6V0jzu`#D&q_c5y6<6h(¨L 3 jxޢcBE@zڢjm.(|Q!^j bJʫVVSecjs %݃jՊbtUEVi4uwʢaL7vU*B}80L? vWE,2F6 zA Anoz*Cl %V.Ɖ6b.][?~*jR`XLpu(p|:ƥ"voo+ +p|G.gczoN[@%@u{Waf a 'I'I+lik~AFrnqZkrp)H[_Mksg'DEfHR'FwדppJyG0wMQ3?19H${-79 k?~U@:\ sPz tamֆs:'VrKf&`Nq:c!q'?uMĶ L79ۻ; O`}|f֛=̼FXxtq %X;$+?cM@S1A2A hKɕ\̓1-Ck!\P&x9YPXA%CJλ[7NqrA^EH 3ON1ޗQ/1llXdN jN0(̂="0|rD{8ݬB10/Ox1EQrfzP26QP3Hu7i(n,V@CWQ!l GhVY,W(mSN}",p#sQP "@|R5} :R/5Zw{2T$KA J\mptN#K1-F/!P<" ?%2ڜ 2P;=EMYW 'BCMPSx4NP4SMuhCm`4x8pU-Aܰ.Zxf cm0*}X*U@ކyS pU8wjeEm}16 (l~+z{^0.`J&B>dߤf}^' JKIѱq( s`!l췾8S9~q̎-ɛ>ՂhnJ=ḧ>qn y_/~n5WQ;;DOCS/DESKTOP/prosetdm.htm0000755000000000000000000000472411714034554012172 0ustar Using PROSet

Intel® PROSet for Windows* Device Manager

Intel® PROSet for Windows* Device Manager is an extension to the Windows Device Manager. When you install the Intel PROSet software, additional tabs are automatically added to Device Manager.

NOTE:  You must have administrator rights to install or use Intel PROSet for Windows Device Manager.

Installing Intel PROSet for Windows Device Manager

Intel PROSet for Windows Device Manager is installed from the Product CD with the same process used to install drivers. You can select Intel PROSet for Windows Device Manager and Advanced Network Services from the Install Options dialog.

Removing Intel PROSet for Windows Device Manager

Use Add/Remove programs from the Control Panel to uninstall Intel PROSet for Windows Device Manager.

Changing Intel PROSet Settings Under Windows Server Core

You can use the command line utility prosetcl.exe to change most Intel PROSet settings under Windows Server Core. Please refer to the help file prosetcl.txt located in the \Program Files\Intel\DMIX\CL directory. For iSCSI Crash Dump cofiguration, use the CrashDmp.exe utility and refer to the CrashDmp.txt help file.

Compatibility Notes

The following devices do not support Intel PROSet for Windows Device Manager

  • Intel® 82552 10/100 Network Connection
  • Intel® 82567V-3 Gigabit Network Connection

Last modified on 8/04/10 8:12p Revision DOCS/DESKTOP/pushinst.htm0000755000000000000000000000354711735070116012211 0ustar Microsoft* Windows* Push Install Instructions

Microsoft* Windows* Push Install Instructions

A "Push," or unattended, installation provides a means for network administrators to easily install the drivers on systems that have similar equipment. The following document provides instructions for a basic unattended installation of Microsoft* Windows* that includes the installation of drivers for Intel® Network Adapters.

For 32-bit Microsoft Windows operating systems, see the Push32.txt file in the Apps\Setup\Push\Win32 directory on the Product CD or in the download directory. This file applies to the following operating systems:

  • Microsoft Windows* 7
  • Microsoft Windows Vista*
  • Microsoft Windows* XP
  • Microsoft Windows Server* 2008
  • Microsoft Windows Server* 2003

 

For x64 Microsoft Windows operating systems, see the Pushx64.txt file in the APPS\SETUP\PUSH\WINX64 directory on the Product CD or in the download directory. This file applies to the following operating systems:

  • Microsoft Windows Server* 2008 R2
  • Microsoft Windows Server* 2008 x64
  • Microsoft Windows* 7 x64
  • Microsoft Windows Vista* x64
  • Microsoft Windows* XP x64
  • Microsoft Windows Server* 2003 x64

Last modified on 2/22/10 4:47p Revision

DOCS/DESKTOP/qos.htm0000755000000000000000000000422711735070116011132 0ustar Quality of Service (QoS)

Quality of Service

Quality of Service (QoS) allows the adapter to send and receive IEEE 802.3ac tagged frames. 802.3ac tagged frames include 802.1p priority-tagged frames and 802.1Q VLAN-tagged frames. In order to implement QoS, the adapter must be connected to a switch that supports and is configured for QoS. Priority-tagged frames allow programs that deal with real-time events to make the most efficient use of network bandwidth. High priority packets are processed before lower priority packets.

Under Windows XP and Windows Server 2003, tagging is enabled and disabled using the "QoS Packet Tagging" setting in the Advanced tab in Intel® PROSet. Under Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2, tagging is enabled using the "Priority/VLAN Tagging" setting on the Advanced tab.

Once QoS is enabled in Intel PROSet, you can specify levels of priority based on IEEE 802.1p/802.1Q frame tagging.

The supported operating systems have a utility for 802.1p packet prioritization. For more information, see the Windows system help and Microsoft's knowledge base.

NOTE: The first generation Intel® PRO/1000 Gigabit Server Adapter (PWLA 8490) does not support QoS frame tagging.

 

Last modified on 4/22/09 10:46p Revision

DOCS/DESKTOP/reg100d.htm0000755000000000000000000001375511656741516011513 0ustar Regulatory Information

Regulatory Information

  • Intel® PRO/100 M Desktop Adapter
  • Intel® PRO/100 S Desktop Adapter

Safety Compliance

  • UL 60950-1 Second Edition
  • CAN/CSA-C22.2 No 60950-1-07 Second Edition
  • EN 60950-1:2006 +A11:2009 (European Union)
  • IEC 60950-1:2005 Second Edition (International)
  • EU LVD Directive 2006/95/EC

EMC Compliance

  • FCC (Class B) Radiated & Conducted Emissions (USA)
  • ICES-003 (Class B)/NMB-003 (Class B) Radiated & Conducted Emissions (Canada)
  • CISPR 22 (Class B) Radiated & Conducted Emissions (International)
  • EN55022:2006 Radiated & Conducted Emissions (European Union)
  • EN55024:1998 +A1:2001 +A2:2003 Immunity (European Union)
  • EU EMC Directive 2004/108/EC
  • VCCI (Class B) Radiated & Conducted Emissions (Japan)
  • CNS13438 (Class B) Radiated & Conducted Emissions (Taiwan)
  • AS/NZS CISPR 22 (Class B) Radiated & Conducted Emissions (Australia/New Zealand)
  • KCC notice 1997-4, EMI and KCC notice 1997-42 EMS (Korea)

Regulatory Compliance Markings

When required these products are provided with the following Product Certification Markings:

  • UL Recognition Mark for USA and Canada
  • CE Mark
  • FCC Class B markings (Declaration of Conformity)
  • VCCI Class B Marking
  • Australian C-Tick Mark
  • Korea KCC markings
  • Taiwan BSMI Class B markings
  • People's Republic of China "EFUP" mark

Electromagnetic Compatibility Notices

FCC Declaration of Conformity Statement

These adapters have been tested to comply with FCC Standards for Home or Office Use.

Intel Corporation
5200 N.E. Elam Young Parkway
Hillsboro, OR 97124-6497
Phone 1-800-628-8686

This equipment has been tested and found to comply with the limits for a Class B digital device pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation.

If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

  • Reorient or relocate the receiving antenna.
  • Increase the separation between the equipment and receiver.
  • Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
  • Consult the dealer or an experienced radio/TV technician for help.
CAUTION: If the device is changed or modified without permission from Intel, the user may void his or her authority to operate the equipment.
NOTE: This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

Canadian Compliance (Industry Canada)

CANADA ICES-003 CLASS B / CANADA NMB-003 CLASSE B

Manufacturer Declaration
European Community

Intel Corporation declares that the equipment described in this document is in conformance with the requirements of the European Council Directive listed below:

Low Voltage Directive 2006/95/EC
EMC Directive 2004/108/EC

This declaration is based upon compliance of the product to the following standards:

EN 55022:2006 +A1:2007 (CISPR 22 Class B) RF Emissions Control.
EN 55024:1998 +A1:2001 +A2:2003 (CISPR 24) Immunity to Electromagnetic Disturbance.
EN 60950-1:2006 +A11:2009 Information Technology Equipment- Safety-Part 1: General Requirements.

Responsible party:

Intel Corporation, Mailstop JF3-446
5200 NE Elam Young Parkway
Hillsboro, OR 97124-6497

 

VCCI Class B Statement

China RoHS Declaration

KCC Notice (Republic of Korea Only)

End-of-Life / Product Recycling

Product recycling and end-of-life take-back systems and requirements vary by country.

Contact the retailer or distributor of this product for information about product recycling and/or take-back.

Last modified on 11/02/10 3:03p Revision

DOCS/DESKTOP/remscrew.gif0000755000000000000000000001752011656741062012143 0ustar GIF89akfdeXVWsqrpnoUTU~}~zyzyxyvuvpoplkljijihifefede_^_^]^[Z[YXYXWXWVWdzkkmQQR||}yyzsstllmffgddebbcaab]]^[[\YYZWWXVVWUUVïuvyhikdegpqslmoȊz|~suwoqs`abҟһƺ755DBBB@@PNNOMMMKK][[ZXXvttsqqiggSRRNMMDCC~~}|||{{yxxutttssrqqqpponnnmmmllihhgfffeedcccbba```__]\\VUUrrroooZZZVVVOOO,kH*\ȰÇ#eHMH3jȱǏ[qJC! S\ɲ`lH4fɳόIDp)9*]ʴȒt4F VMjIH wʉٳMa#7k+KWS+d߿+ĩs4'+^<0XĻ>ּi(s[*WeM1fz8 '-u띎Mj׸Cn^yتr xx]{;_06N\Eɼ@_bLݺlONgwёZ.([O*ZU3|5$7W$pp!Ywq݂L釘ygArJr$QHXVo!RTY.8r$@G.g&I6Oc!D!б"Pq5KpGo6Uב=b\>),yb gԣBQ GRdd@^" 'TR'`5$)`IWY @%(Օ$OVɆ A@fR.l %o|[x:ӠqL)(p,H6"d)$eI.5('zdrSMTIcu! dԋrvZQ]^h/S@k2, (K:4Eeghњ\Wڛ_AW.73BBGp UbGaSsdq"ˇ+L5<f#YHQovVBf &ey\}7WT&8/(ΐArчϕMrUc+VsZ2o+ф/AIwۨk5(Ja.D32T-jD#UnjO"?nL0$s2DSINf<^djSLdS@fjA^$LY2-/YHa~nwWԐJʙ'As(2O/"@$b s:js$ ' \< 8%ҔD ;9S:qf$ZqO%iJ*PxU1dL<%(jJ-$锨 /b\r*K)V!-KZ=U"l*Y:U?2*V!7)pz7+KΪdl]G0 0]Xc@1Y+ $Eaa&iv%7Vp |m? 6hH0b)0@4xbڬ-b{R}u´@Ւ\xuv<)yͫQ:*]i0?[R/ֽE} rj!Hy#a4H0Y0|$ l!F"G挽Z@$+'ge 6 "dH=lJ!G&s) ȲMWʰKPpMI >b Fų4n(g`ɘ jݾU›p`h0]MAIE脀 F< JNm^21 N4S4WszsV)#Zz`QF4\_3ѐ BViR7e#pB_Jl eg.g!bSu)C۔#Hk0XPYd[Y%7&a|{V[pYAvnjsAj5B߬kSq?<%5˵=$<^urQzF!~qDtVb1p(C㢑sA|Sz7vc'sDJ=3tZ Y%?h\?l]`,ήb7O By{?wwz7:/=ȕ.x&OxArt|A{#d%yY9 pt닞(1Rh|Zy;?cn%Ry9sjA>G\8|wrZ7{~W%{[q8v?fm/;F Vn{l̀"0FG u? 0[8oZ y G~ ) %CeH6k|P Rzd }"o8`Gcjr"lz48Hҁ!~Yi@;kpb"ffs[!vig/! ?2 4{gQowh1 b=Z(XxE`[Z!f%%/ :AW8HlT $fPh^}h(ċE}ZQèep%4 (c0X@(u[ vF_Xxmڈb5y@%Hh >vHNBxkߵM9 ؐe*QL1Q a g !dO HqI TN8&.FG>f@;0&C CՒ 1  RBRgH^`qC_)q&0H!5eՖ U OpO@N9[qO2 ,@y pYoF?0\ \PB6ew/Y \# Pf =IRe] ¤%_i芠@M 1syHi C?GKfI銆D`u%wvfuiNDbSf IVnSuꊇ1p 61zR 4pC`q WPҙ.(nF Wp8zɣ6apHz\L riHV6zY7j[řMJBjIT-`5Pe jF2iv% G*PQu\{z&4C `zN 3 vg\ڤ` pT`zjYa:JiYr%) WsڪwZ頳ja Zʫ ʧ3`GjIꫜ@JjHGpʫYhڤut*ʬʟMq:bt+pXۭY *j ۰iЪ{0Pl +7 ,"۰F |j+02y(h ۋz*~ PAMB;[ /˫G@Q'pZa گ#S x LO۲Rk5P `q O & {P L*op> ˊKʇ" ! ܚ\۴'s `yӪd`˱La jz*0 ۊ}z|۷ @ P#۬з~ۋ۽?۽ћwM ˺a۾Ԁī౻[.k*5J>S0J)Ma;ZKr h&zy|F@ Y i&zm R0B+SK,]k˾L-Y9tK 'ȸM {K uK)N(yKV"aY* xG?1)q}@:~kILqI%? \q=!X{Pd:] O'ƞ A%xǦ<0q cVb4pȖԦ pZv|R܉E3˸̫jtWd,%]SqzG_ L4qp2ཙkˌ̲,L"q*'pbTlޓ&zY@ {|e܉ MbBK@:-z=!JW(0W@{k>֊ }>1 >DkлRv;F@ R^mܰ[[K-_<1< f}늴 }[wᩖn-pmً-NN*~9{B |[nJB'>K Ր @~VK{ mT7chܔE˭GP+ yuk%V&b֙6/L$J.U]~ ͈alab r& tix9Z}T2Ri@^z}_yF|$2=i;q%_YZ"Yb딙 &9 .1) ޣl?1䷙ٛ]YBLX/ɹuιMq.ߏnٹp@o[OzƎ9IމNvW[k .Yx驱$!M)(  o ޡf TO?ґ@S/ $XA .dVҤeE5nq*NCĉSVU0dhK1e 0P5?:H*[%ZHl @iǏ#GM8UX9ISjjYia:bXcLU{V] st.Ot[`J1p^‡%mk rh1*b:_FBƪLۢ.㉨ZCY揱 ADlrQNF+[٨${KmE텂8 Ux/EEё!0=e#VlBzRݻ'j^'j,Km%5Ras%o`LN+5p5lDـI%k)"PK_)~}rLg_sìb'=|\Wm~vi2P}+3 8b-¼{q`^0 iPZ8\QrSB )nnQ38] (r8P-RaאhBHgH-29BS;U")@ڥ%b ⍌Ȇ D_T] 7@!⍬ #6еa bEl< ^Z"RiL6Pԭ'E It׼.a#ʊ!UAf{hn5xuif! a•U!Bg0ĎK] ŵ/ACwE.s&$ŘK^Uo|_~ȿ 0x<nHvOe;a qp`J"AsDb8h3Ta_+ e?(džp!W\5{Vo \iE_hVVjB4d˖,'1S}Msy};DOCS/DESKTOP/reqd.htm0000755000000000000000000000544411656741062011274 0ustar System Requirements

System Requirements

Before installing the network adapter, check your system for the following minimum configuration requirements for Intel® PRO/100 server adapters.

Hardware Compatibility

  • The latest BIOS for your computer
  • One open PCI or PCI-X bus master slot, 32-bit or 64-bit, operating at 33MHz or higher

Supported 32-bit Operating Systems

Basic software and drivers are supported on the following operating systems:

  • DOS

Advanced software and drivers are supported on the following operating systems:

  • Microsoft Windows XP, with latest service pack installed
  • Microsoft Windows Vista*, with latest service pack installed
  • Microsoft Windows Server* 2003, with latest service pack installed
  • Microsoft Windows Server 2008, with latest service pack installed
  • Linux*, v2.4 kernel or higher

Intel® 64 Architecture Platform Requirements

Intel supplies 64-bit drivers for the following operating systems:

  • Microsoft Windows Server 2008, with latest service pack installed
  • Microsoft Windows Server 2008 Hyper-V*, with latest service pack installed
  • Microsoft Hyper-V Server 2008, with latest service pack installed
  • Microsoft Windows Server 2003, with latest service pack installed
  • Microsoft Windows XP, with latest service pack installed
  • Microsoft Windows Vista, with latest service pack installed
  • Red Hat Linux
  • SUSE Linux

A platform that supports the Intel® 64 Architecture will run in either 64-bit mode or 32-bit compatibility mode. In order for it to run in 64-bit mode, the following requirements must be met:

  • The system must have a 64-bit BIOS that takes advantage of the Intel 64 Architecture
  • One of the supported 64-bit operating systems must be installed

Last modified on 11/22/10 4:16p Revision

DOCS/DESKTOP/run.gif0000755000000000000000000000014111654247274011113 0ustar GIF89aE Save and Restore

Saving and Restoring an Adapter's Configuration Settings

The Save and Restore Command Line Tool is a VBScript (SavResDX.vbs) that allows you to copy the current adapter and team settings into a standalone file (such as on a floppy disk) as a backup measure. In the event of a hard drive failure, you can reinstate most of your former settings.

The system on which you restore network configuration settings must have the same configuration as the one on which the save was performed.

NOTES:
  • You must have Administration privileges to run scripts. If you do not have Administration privileges, you will not receive an error, the script just will not run.
  • Only adapter settings are saved (these include ANS teaming and VLANs). The adapter's driver is not saved.
  • Restore using the script only once. Restoring multiple times may result in unstable configuration.
  • The Restore operation requires the same OS as when the configuration was Saved.

Command Line Syntax

cscript SavResDX.vbs save|restore [filename]

SavResDX.vbs has the following command line options:

save Saves adapter and team settings that have been changed from the default settings.  When you restore with the resulting file, any settings not contained in the file are assumed to be the default.
restore Restores the settings.
filename The file to save settings to or restore settings from.  If no filename is specified, the script default to WmiConf.txt.

Examples

Save Example

To save the adapter settings to a file on a floppy diskette, do the following.

  1. Open a Windows Command Prompt.
  2. Navigate to the directory where SavResDX.vbs is located (generally c:\Program Files\Intel\DMIX).
  3. Type the following:

    4. cscript SavResDX.vbs save a:\settings.txt

Restore Example

To restore the adapter settings from a file on a floppy diskette, do the following:

  1. Open a Windows Command Prompt.
  2. Navigate to the directory where SavResDX.vbs is located (generally c:\Program Files\Intel\DMIX).
  3. Type the following:

    4. cscript SavResDX.vbs restore a:\settings.txt

Last modified on 2/10/10 3:18p Revision

DOCS/DESKTOP/setbd_dm.htm0000755000000000000000000006127511656741062012126 0ustar Unattended Installation

Installing the Base Driver and Intel® PROSet via the Command Line

Installation Methods

Installing with DxSetup.exe

Command Line Options for msiexec.exe

Using SetupBD.exe to Install Base Drivers on Windows Server* Core Operating Systems

Uninstalling Drivers and Intel PROSet

Installation Methods

DxSetup.exe is the preferred installation method. You can use it to install the base Windows base drivers and Intel® PROSet for Windows* Device Manager.

NOTES: 
  • Windows XP x64 and Windows Server 2003 x64 do not support unattended driver installation.
  • Intel® 10GbE Network Adapters do not support unattended driver installation.
  • Intel PROSet can be installed with DxSetup.exe or msiexec.exe. Intel recommends using DxSetup.exe. DxSetup.exe detects the system's language, searches for the appropriate transform file, and applies it to MSI package. The transform file translates the installation instructions to the language associated with your operating system.

You can use the base driver install utility (SetupBD.exe) to install Microsoft Windows base drivers from a command line. If you use SetupBD.exe to install base drivers, you will not be able to use the advanced features in Intel PROSet.

Installing with DxSetup.exe

This section describes how to use DxSetup.exe to install the base drivers and Intel PROSet for Windows Device Manager from the command line.

NOTE: Intel PROSet can be installed with DxSetup.exe or msiexec.exe. Intel recommends using DxSetup.exe. DxSetup.exe detects the system's language, searches for the appropriate transform file, and applies it to MSI package. The transform file translates the installation instructions to the language associated with your operating system.

DxSetup.exe is a setup utility used for installing Intel PROSet. It detects the system language, searches for the appropriate transform file in the same folder, and then launches PROSETDX.msi in the language specific to the operating system. The transform file translates the installation instructions to the language associated with your operating system.

DxSetup.exe also takes the install options from the command line and applies them to the PROSETDX.msi command line installation.

DxSetup.exe command line switches:

Switch Description
/q[r|n] silent install options.

r Reduced GUI Install
n Silent install
/l[i|w|e|a] log file option.
i log status messages.
w log non-fatal warnings.
e log error messages.
a log the start of all actions.

DxSetup.exe Public Properties

Property Definition
BD "0", do not install base drivers.

"1", install the base drivers (default).

NOTE: BD should only be set to 0 if the Base Drivers have already been installed prior to running DxSetup.exe
ANS "0", do not install ANS.

"1", select ANS (default).
DMIX "0", do not install Intel PROSet.

"1", install Intel PROSet (default).
FCOE "0", do not install Fibre Channel Over Ethernet (FCoE) using DCB (default).

"1", install FCoE.

ISCSI "0", do not install iSCSI using DCB (default).

"1", install iSCSI using DCB.

SNMP "0", do not install the SNMP Agent (default).

"1", install the SNMP Agent.

 

NOTES:
  • If you specify a path for the log file, the path must exist. If you do not specify a complete path, the install log will be created in the current directory.
  • The ANS property should only be set to ANS=1 if DMIX=1 is set. If DMIX=0 and ANS=1, the ANS=1 is ignored and only the base driver will be installed.
  • Even if FCOE=1 is passed, FCoE will not be installed if the operating system and installed adapters do not support FCoE.
  • Even if ISCSI=1 is passed, iSCSI using DCB will not be installed if the operating system and installed adapters do not support it.
  • Public properties are case sensitive. All characters are uppercase with no white space between characters. For example:

DxSetup.exe /qn ANS=1

Any white space in "ANS=1" makes the setting invalid. "ans=1" is not a valid setting.

Command line examples

You can modify the paths for different operating systems and CD layouts and apply the command line examples.

  1. The following launches a typical install silently:

    DxSetup.exe /qn /liew install.log

    NOTE: BD, ANS and DMIX are selected by default.

  2. How to install components but deselect ANS. Set the ANS=0 in the command line:

    DxSetup.exe /qn ANS=0 /liew install.log

msiexec.exe command line options

Refer to Microsoft's website for the most current information on msiexec.exe command line options: http://msdn.microsoft.com/en-us/Library

NOTES:

  • Not all command line options Microsoft provides with msiexec.exe have been tested or are necessarily supported for Intel PROSet installation.

  • Msiexec.exe also sets an error level on return that corresponds to system error codes: http://msdn.microsoft.com/en-us/Library

  • Intel PROSet can be installed with DxSetup.exe or msiexec.exe. Intel recommends using DxSetup.exe. DxSetup.exe detects the system's language, searches for the appropriate transform file, and applies it to MSI package. The transform file translates the installation instructions to the language associated with your operating system.

Command Line Switches

This section describes how to install Intel PROSet using PROSETDX.msi and msiexec.exe from the command line.

C:\WINNT\System32\msiexec.exe /i PROSETDX.msi /qn /liew install.log

Most commonly used msiexec.exe command line options:

Switch Description
/i install
/x uninstall
/q[r|n] silent install options.

 

r Reduced GUI Install
n Silent install
 
/l[i|w|e|a] log file option.
i log status messages.
w log non-fatal warnings.
e log error messages.
a log the start of all actions.
Transforms A property used to apply transforms (a .mst file) to an MSI package. The following example applies a Chinese language transform to MSI package, so the installer displays Chinese strings during installation:
 
TRANSFORMS=2052.mst

Silent install/upgrade command line syntax

The following launches a typical installation of PROSETDX.msi.

<Full path to msiexec.exe> /i <Full path to PROSETDX.msi> /qn /liew install.log

Silent uninstall command line syntax

The following uninstalls all the Intel PROSet components. It can be used when the path to PROSETDX.msi is available.

<path to msiexec.exe> /x <path to PROSETDX.msi> /qn /liew uninstall.log

The following uninstalls all the Intel PROSet components. It can be used when the path to PROSETDX.msi is not available but the ProductCode of MSI package is known.

<path to msiexec.exe> /x <ProductCode of PROSETDX.msi> /qn /liew uninstall.log

Command line options supported by PROSETDX.msi

PROSETDX.msi provides public properties that can be used to change Intel PROSet install selections from the command line.

By setting the properties in the command line, you can disable and hide some features in PROSETDX.msi, or force some feature to be selected/displayed. This provides the flexibility to install different components/features in Intel PROSet.

Following is the list of public properties provided by PROSETDX.msi:

Property Definition
BD "0", do not install base drivers.

"1", install the base drivers (default).

NOTE: BD should only be set to 0 if the Base Drivers have already been installed prior to running DxSetup.exe
ANS "0", do not install ANS.

"1", select ANS (default).
DMIX "0", do not install Intel PROSet.

"1", install Intel PROSet (default).
FCOE "0", do not install Fibre Channel Over Ethernet (FCoE) using DCB (default).

"1", install FCoE.

ISCSI "0", do not install iSCSI using DCB (default).

"1", install iSCSI using DCB.

SNMP "0", do not install the SNMP Agent (default).

"1", install the SNMP Agent.

 

NOTES:
  • If you specify a path for the log file, the path must exist. If you do not specify a complete path, the install log will be created in the current directory.
  • The ANS property should only be set to ANS=1 if DMIX=1 is set. If DMIX=0 and ANS=1, only the base driver will be installed.
  • Even if FCOE=1 is passed, FCoE using DCB will not be installed if the operating system and installed adapters do not support it.
  • Even if ISCSI=1 is passed, iSCSI using DCB will not be installed if the operating system and installed adapters do not support it.
  • Public properties are case sensitive. All characters are uppercase with no white space between characters. For example:

msiexec.exe /i PROSETDX.msi /qn ANS=1

Any white space in "ANS=1" makes the setting invalid. "ans=1" is not a valid setting.

Command line install examples

Assume that C:\WINNT\System32 is the system32 folder and PROSETDX.msi is under the D:\Apps\PROSETDX\Win32 folder. You can modify the paths for different operating systems and CD layouts and apply the command line examples.

1.      How to install Intel PROSet silently on Windows XP:

C:\WINNT\System32\msiexec.exe /i D:\Apps\PROSETDX\Win32\PROSETDX.msi /qn /liew install.log

2.      How to install Intel PROSet silently on Windows Server 2003 for Itanium®-based systems:

C:\WINNT\System32\msiexec.exe /i D:\Apps\PROSETDX\Win64\PROSETDX.msi /qn /liew install.log

3.      How to install components but deselect ANS:

Set the ANS=0 in the command line, for example:

C:\WINNT\System32\msiexec.exe /i D:\Apps\PROSETDX\Win32\PROSETDX.msi /qn ANS=0 /liew install.log

4.      How to apply a transform file to MSI using msiexec.exe:

Set the TRANSFORMS=filename.mst in the command line. For example:

C:\WINNT\System32\msiexec.exe /i D:\Apps\PROSETDX\Win32\PROSETDX.msi /qn TRANSFORMS=2052.mst /liew install.log

NOTE: Intel recommends using DxSetup.exe to install Intel PROSet. DxSetup.exe detects the system's language, searches for the appropriate transform file, and applies it to MSI package.

Command line uninstall example

NOTE: Do not use the "ANS" option when uninstalling Intel PROSet from a command line.

First get the path of PROSETDX.msi in the local system or any other image path when you installed Intel PROSet, then use msiexec.exe to uninstall Intel PROSet.

For example, assume that C:\Windows\System is the System folder and PROSETDX.msi is in d:\unattend, then the command line will be:

C:\Windows\System\msiexec.exe /x d:\unattend\ PROSETDX.msi /qn /liew uninst.log

Command line reinstall / repair

If you need to repair an Intel PROSet installation, uninstall the application and then reinstall it. See the uninstall and install examples above for more information.

Using SetupBD.exe to Install Base Drivers on Windows Server* Core Operating Systems

NOTE: If you want to use prosetcl.exe to configure your adapters, you must use DxSetup.exe to install drivers and Intel PROSet. SetupBD.exe only installs the base drivers.

Command Line Options

SetupBD.exe supports the following command line switches. 

NOTE: You must include a space between switches.
Switch Description
/s silent install with no reboot
/r force reboot (must be used with the /s switch)
/nr no reboot (must be used with the /s switch. This switch is ignored if it is included with the /r switch)

Examples:

Option Description
SetupBD

Installs and/or updates the driver(s) and displays the GUI.
SetupBD /s Installs and/or updates the driver(s) silently.
SetupBD /s /r Installs and/or updates the driver(s) silently and forces a reboot.
SetupBD /s /r /nr Installs and/or updates the driver(s) silently and forces a reboot (/nr is ignored).

Other information

NOTES:
  • If you install drivers on a system based on a server chipset and BIOS that are Intel I/OAT capable, the /s switch (silent install) forces a reboot without the /r switch. If you do not want the system to reboot, use the /nr switch.
  • For Intel® I/O Acceleration Technology to function properly, you must reboot after driver installation.

You can use the /r and /nr switches only with a silent install (i.e. with the "/s" option).

Uninstalling Drivers and Intel PROSet

Intel recommends you use Add/Remove Programs to uninstall Intel PROSet and the base drivers. If your operating system does not have a GUI installed, you can use msiexec.exe to uninstall the base drivers and Intel PROSet.

If you only installed base drivers, you can use the PROUnstl.exe utility to remove them.

NOTE: PROUnstl.exe only removes the base drivers. Do not use this utility if Intel PROSet is installed on your system. Removing the base drivers without removing Intel PROSet will result in system instability.

PROUnstl.exe supports the following command line switch:

Switch Description
/nogui silent uninstall.

Last modified on 3/07/11 11:02p Revision

DOCS/DESKTOP/slideoff.gif0000755000000000000000000002046211656741062012106 0ustar GIF89a#kfdeXVWsqrpnoUTUTSTNMNJIJzyzvuvpoplkljijihifef_^_[Z[YXYWVWdzQQR||}yyzsstllmhhidde^^_]]^YYZWWXUUVïhikdeglmosuwoqs`abҟһƺ755DBBB@@PNNOMMMKK][[ZXXvttsqqSRRLKK~~}|||{{yxxutttssrqqqppnmmmllihhgfffeedcccbb`__]\\VUUrrroooZZZVVVSSSOOO,#kH*\ȰÇ#JH"DK[lcǏ CI$EAT↣ɗ0cʜI3)+*rK5 JHKnTRCЎ#Jՙtd砥TIJٳ otsgᝤaǢKnM9<Ԋ^ U;JQ1K5̹פS3N5KH!ٳkDž,*{t,Y#JWrMٽI#wIt9&6KO407B1,DG֫B#(B 5 OB[sGXR{D#<½L]n Y$QD'at3I Ҳ)dhDU` Vn}Eh!("4<(iݡWcHV3?f>) a8&G$i}n ad$" P P>;&Tl`9у``숖=drˡCT;dy%A#b{yH'p”l9m zǨdcd>$1Z+@0Q*@,%((6xX+!CH% yp8~d% y<!l1'LDnIKij9 5͊Xb@y.+K(4pS3!W:p+a H,H@;TAQB2D2r%fD2Qa ɕњAD#:ϒ~m-R(2g*NyM~$+ci U;8C(Jv-AHOg˧JH%DQY͎t"_Rhz $J֣HA*G)AFD! WU&.wPu~FZ1qdE V^Y5=0W"Kjk֠l5` "6%nۚbe(`Y 'MjrOJ>ujt=@ap.{!+;haRȎWlX {[)np`˸hSKeagU*X#h'.:'v2!Cb o"؜=o2+?lf8 Θ(>:8Dv0%!P2` ]&進_z@2WtB0#Kb p$T3!rCL ό"^F ʤ"l 멡+XF4ȡYON9(g RsQ،ʰ՘ggĞj Hk"J*AZe6 }QxCqs'[li$~̰$>}齿Cf*D~ } <~x1S_)WTAGszG[D!Gj g)azRU$g_!+%GhGcsXδ# ,R:'X5FzU|~!}$j&W.,؃s` w02Hv5(IZуR%?xE8~ηw ~bfSȂ3+n˗/ R;X=nHGG8'ssot{8Wh(OPMF48V`l}X`?Qs,(j(HT6cŃT036sw#h'XaeIU+øІTՌ68t7׸jrH?(H+@XCHmwkAT͸vx>Tw 811yXHQ+HIЏ(+X+9@mmJP +` (a S9#}' 9E&yd(HؒFvE}9DN1PnIHØkh0PbmVs0D0`nU{`tkxz0SNɏJ@? oȂؕ\IM}`6.np*iBG@i! W {,F q8YB0lYrR`vrE7O合 .RV`?Q+YP{[H )y@z ԟDv9OH Y%Ata8ٖ@YPr+ܸn+*8/@i*ZH7ZF0|'B(F.@QBC[A:DZB"Z\ ^:DYTF" ТD1:&zCZdE/psdNZ/ qZs @0&`Z:DqWb*Uj?{ 9zjDa*ꖅzLkکC٦1*FBcZ@dʪMCej ca 0 *,ʤJR= 5j->'y ʡj?ǦМ*rk7: ! RVdp"zRz[`dJʰo{YAS[hvzy5:=x9y5kZb C!jJ^ zA[vت\6jjGs E`2!ꮒZ+ʴA*6=/vd5 @ jHA=0ĩn}d+KzF( ~.궧 vgqK`z/CQrz h^+ p B1D[:JiڰgQgY w'UkyC< j-4 7ŵqދ覥xK) >|{w6q ƘPzۖ.BfS̺|VH;.Y_p+h pC0 @l| @ۿ`1ZDpq{wc)5q!j>#Ŀvxm)t+0K<7a‚?xpoUx:׷TlH4!$< qR&Iuv[41{ 'UF@B>ȸ`z|<4y&1;b;p$\dp4u7 :'s! 3! mv3q lƊCS B.!=3 K?>A]^66 @.`>^bpI$S#CG jla>SP}m}߅ 1`tx?Xkx~GqlZAP Iݶw+/$U0hm>–湽)m!#X*+ w^1q(r>QrN<O,^4wgm*q]mᮬC XlŎ]޼CXѺ#S0襖-@T:Fr\c?mFy((pcusA8=,;0PS{WEpN\`B{=N3?7A 7ak 0+yhyyWHi djC@YOEXȒ5ropo7( H#0n^ָ53o2geYa=s+An>",Qd$ )8ˎ|*xB(fT? Y $X,dCS)X!-xh17E$Y)Xt,aeSJ.$ʔ3L^O#PYrMIRTTD%-9HNnx9Mji˔*BK- lC$N |<kl k4Έ,4NG2Ԍ:dht3X4ъFd,C@Ƥ;x$dž $:Cd,9E7r .K1=D/K< K93-OId 2)QK<+=&" 2KÑD) ҿ\N[%L6} MWd(/RSՏ(uPVZmHM6^O+aVBvk-*P+55i[tzn%L6]\$eUx Vx}UѨ"̏$aE }WLl`QjHS`>Y/b|$NQY,EDЀx,2]=l =;>4gk+eWE/H$Ah3zʔt8x 5T48:c~99A9N"U57ڭ=lAt QчlFOzSRGhqӡ $ S&/S*UqAbZS^;*Wj6A*YjV#m=MYUǮwi^Wk`׺հ'E[؅4Vl:%{TV֘La5kHų=ch3JZ+Em UֶlJ[ֶ^3[pKv,HEnpmt[1׺|3cN.;6>EoË2t%ao|5V׾S/z_͗$0lSLpi+Z6؋>`sY^m5PJ !9XC`5Y.;,5Vncr ħjKx8rPbKA@E9J 7y FbIZ>`\g2Dc&?!5asfXuYFIlgb$ȚU,@N_Kb*4O[GN!9w۴]x;w3+4}יa`yyD;85y&vg{ݣ)d'_C˳^pi(eo)YAS(m,8B=@iǷ;DOCS/DESKTOP/snmp.htm0000755000000000000000000000361211656574604011317 0ustar Simple Network Management Protocol (SNMP)

Simple Network Management Protocol

The Simple Network Management Protocol (SNMP) is a network protocol used to manage TCP/IP networks. SNMP-compliant devices (agents) communicate with management applications (consoles) to send alerts and updates and allow configuration changes.

The Intel® SNMP Agent translates event notices from the adapter and sends them to specified SNMP management stations. The SNMP agent provides information on Intel® network adapters as well as information about advanced features, such as teaming and VLANs.

Using the Intel SNMP Agent

  • Before you install the Intel SNMP Agent on a computer, you must install SNMP on the computer. See your operating system documentation for more information.

  • To use the Intel SNMP Agent with an SNMP management application, you must first compile the Intel MIB (Management Information Base) into the management application's database. This allows the management application to recognize and support the adapter.

Look in the Table of Contents for information on installing the SNMP agent on your operating system.

Last modified on 9/03/07 4:49p Revision

DOCS/DESKTOP/snmpwin.htm0000755000000000000000000000441211656574604012034 0ustar Simple Network Management Protocol (SNMP)

Simple Network Management Protocol

The Simple Network Management Protocol (SNMP) is a network protocol used to manage TCP/IP networks. SNMP-compliant devices (agents) communicate with management applications (consoles) to send alerts and updates and allow configuration changes.

The Intel® SNMP Agent translates event notices from the adapter and sends them to specified SNMP management stations. The SNMP agent provides information on Intel® network adapters as well as information about advanced features, such as teaming and VLANs.

Using the Intel SNMP Agent

  • Before you install the Intel SNMP Agent on a computer, you must install SNMP on the computer. See your operating system documentation for more information.

  • To use the Intel SNMP Agent with an SNMP management application, you must first compile the Intel MIB (Management Information Base) into the management application's database. This allows the management application to recognize and support the adapter.

Installing the SNMP Agent on Microsoft* Windows* Operating Systems

This utility should only be employed by experienced network administrators. Additional software/services must be installed on your network prior to installing the Intel® SNMP Agent.

To install the SNMP Agent, start the autorun menu from the Product CD or download directory and click Install Drivers and Software. Follow the instructions on the screen.

Last modified on 9/03/07 4:49p Revision

DOCS/DESKTOP/style.css0000755000000000000000000000450511651733270011473 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/DESKTOP/support.gif0000755000000000000000000003157611651733270012034 0ustar GIF89a]h!"9)$9J,Z B R)j)R% X& e)(s!4k#2x1 k1&X1JMwuC6~9;f37j.\8%׶}$).fdӫ_m: ҅qըqaI[1ĖlpG uQW!Qd9ކvEt #81TL37Hae1`)(IroP"YBT!υT"qI}(TVOiH"3McΙᆋ¶]2833h&cv!b r$1%<3 $nxY'eqFRZ)餔VF<3Hc9|ƘllLؗ1fl3_v9z>L*c1KBxdi6lP.Ęrnaa9}y+T0b .z91IvgGU C!zJK4H"ta / w4RSx8-(Q98 3Ċ;>#hAe0H8#nA 7 .;#OH>[ҸUDBHUa-?%Agdx HJ T-pxcG#(#Aژ"btАQ]]E IH"8$@3džhLh!;Z<A01pƸx 㨑8UI˼Qxm(1 2 R&7)ǒ@Wb&H\!"yxȥ8!orH-,8 '$"X21zEcb$ -9F[Ӝ,dQ =z扅z^WpB 8Els IN3lB*:TF5a?BbG;T?@A ^TJqkt#P:uh!p!2|wѻ eHMOAO8(6a5zB`!` +)́l HH9z (3"01Jͫ^iFBK5!AT3ƍi@ʉdyq9Y`C+H8e{MjibH8Wqts Ad@("C;p+QqF `_p`` ؀ؐȉِ Jv/(ِ2P܀[8 TDE7yq P Ҩ `bu0vxqp % e |73Yxhȉ(+h  yѐ 2   ^]0}!-HLX @ bi0] `m@}FP#V `0&g (v0q\gs  p! e +A6p1\@ȏ P*9  *` *p **\) 0%لM8 Q:P[PHG R$PGP yPfsv^h'~XuG} 1H Op.-=0 ` p؉ Xz`  򀙹\KnlQ$Ii0xw E<@lp@ 0l09I8 xS&v(@qōۘi)DEpV $ gj` ЏzI_vZ  yTw+׈ x;50Awb Ds mPXx'&ʁF\˵qyv5GUGEBV'WtEpIi0'ŰxYmڦP}YsJuJ}^ K(Jp`p7fC7 P iBH^jJ&ʆ`*W` `Y|H QZ/fphpӯ PP gq1p *Jvtژ i]!]0iMyIr,°BFɑѭW[9 Y\Kf9 T@Q |{-隡p1:@'ߡC~1^Ph5i&=ڰ ԉ.q* P `@g_ eлfr`qq@p#[/o46{*iK0!YHp D盾]*J! L @Z++^k]wZ) < )`o; ,+jI*'p9pbp% l020po` p^P[&ć uXK!Q|C @Tt _g9|kAX̠&V)Ipʂ|aL`pk+AHQ2K㰿 Ȍȑ! 09;P  L+PH|Ѱ ]Q*P2p3 2I0PgpdEQL,$li|ibƅ:|_л[ Ǜ 0j Q؄oJ)xz,PzpȐ2aɊʈl7`ɞi;p{** Cl-\,؛ -m <iȘ]r,$ғ^@Ƭ̺b.Ps0ZhE9 i}Pt& K, <[  1 GQ9RS epq\okk*+q ݊NHа9lVIK M ҋEʩ} \{|ÜQL1MV0TKL!9];Gƭ2ZJLJR}+΀m5:aE Ac1 0 0 %N(paPP9\gz H_ wglўfjh,ċ݊IΩKɽ-9$i:] Y={l4^( ˾'"WXa5>ioj0#A kD$^bTp  \9(\\46m wvؤ Yg2_Puջg0'rp;dm' mℙꙹٳ O]3a+K`f&ik,:NjʎZN|0j)IpZ2m" t$ sP}҂0 zV>R3~r0 :wǻo`rot tl"WŚМ] ۮ"L4Na*  )hG4HOG/d;̠i2@Jx?Uk-7vI(tķAp8ˆ[)y_tr(%{T f,xȁ!CbF +"W;q}|-p}1HhJ1V]nP2\`nBcK31BU \*qRЁXA,A Јxp׻?ftWD')91kht2!ǘ2V-pp3!B1A2F dpMr/a XplcŔ ipE8,ssc(bÆ[ސ'!Wh%CcgZ7 3$(X3x̸41|׼0}p4!pӸ| cgx,@`l|c[; FQxiKo$pɸ? {ZzmuHޅS4_^4':!FE.<O7Ip9:\5)V@׮j4| d  #U<;%S3܀5Qp 73uG3#HM>LSo=^W`z5w{ hO1!C}Dp tXȺ [> 䳇哇OS tzx (=; zXp rC;B 7s`2g`6hM9),zch%@# a r xhyv6> =L  @cx'O+I$ 1c"t@A8pp M893bz/tM9]tT18; );Jkės8hVxh ck?p?50 E, 3?+%MgHx9/?8512 gZHЅJ49-Xm<R=RUxՅMIeԑnX7&$I KRTsHpWY=SuR؇T^V%<̺Ľ % ЙP>Xo4nxӱy K{>eU&jmhy+L6@L!-""X3!@ȧ}9@6`1hE-!rӱ#X- AN]T&?}XxHA -1J\ H\NAsG},թ\{\C }=Y\ܣ٨Ľ- pBwQR JsK+їr)^H7-!E̲[q!W|[+"83CXChOש}^b=!85\ \Mm\:j܅A)TlCӗ``a%#QXٟ]NXYTF`~tU0EUPϜE8Yħm^9^%VJF گ="%[M[%*^"8!ai:?7 7,}X_:Sԭ:mؑITxܘXO=T TVm\څ,X1:G7T]ʥa%G&T Ƈ B|Ty&dZ|b͈EK- RU!+cI`Cޱ+,k56o5HȋB5(x/˂/}:@X3t,c=~vYGgo\`@d}4:(:ۅ%Go}w]U:uȈPf`$LhQH0ɬsIiLIEϖi"蟞Bc%;!>yvcbyNjfzDg]xF/ #l^b-Ɓ 6X9]H*ȁG.C5"f7,M} 癨p:bޤĆ#$M*t xl] <p8{`Nlfj ATClˉav^,x04iHfjv%W-pXBq.O)32xcEFljj m#򮐛"X˦my,=fՌCގM;V~@bf? H.6i1-yx@ތ=mq&)8nӡ"vw0555KVfh.pRqk ߴ 610 Ca('H4#H4K÷r/O>1䕾Z" s%SQ3&ssqCЍ&`.I =M6)q7I/tLDF^f^FJc=8QSg%[G#AdiWcJkM?vd>V!f^n2bfw0Tߟ˔hn]dt*\\vISDMvye!N8뱺-(7Eb`'xWxbHׅC-pE @`#B+dy@^óSzy/AFV7x->35 G??. ЀH+}dryz,yJym!p&5Wj]8>upB8zݔ4fgZz{zE,"b~3rs9?cxf̲?{ȟF5x3$8J̸{?pz,v[goqvT/@{/yHI(5`Uͤw6v~W,_'| >1t^Ǐ;F9AxJxIc45 Y,h „ 2l!Ĉ'RH^={7jc= a$Ɣ3ڋ'0u=4(1E*ib)l\ =ŬZ꒰K.ZQEjײm-ܸrureǒOQ]ѣČÆMlhC&ĦJ {ңIXͥ"aٱ M6ܺw[};I)%x2@>$ǐ!7(MpUXӂuCӯo>~=N2U 7.8=ƆQ4\$ ZJV<0 L,"@]4NSV'.E4 HtAxD#œKKYŕWx->fbXR@"'(j\ Yc"fl}oJ5qQ<2ua]CC(p)\p#`*).D H^AѨM=`1c4("Lϐ90K,K*cd80qriK A-Z{c*2Pr^sjf{/guJ,bD/@FD1DFxZ0sN` K8*vmKU}6ib?b$4]>L 0@ZK9oPrl3t|j1ߵԬԉ|]"@<'Fd2ġCu#hu(zuCcU4*"Nc(:NٌX {8EHfBǕ(څLlGRt&ArN 6L}*T*թRV*Vխr^*X*ֱf=+X/qMLuЄTrQ Vjj_:Vj]JվO(d#+Y)qI,[TrOeٵ-jSڸL)!.Z;DOCS/DESKTOP/support.htm0000755000000000000000000000206611651733270012047 0ustar Intel Customer Support

Customer Support

Intel support is available on the web or by phone. Support offers the most up-to-date information about Intel products, including installation instructions, troubleshooting tips, and general product information.

Web and Internet Sites

Support: http://www.intel.com/support

Corporate Site for Network Products: http://www.intel.com/products/ethernet/overview.htm

 

Last modified on 5/12/10 3:26p Revision

DOCS/DESKTOP/team_dm.htm0000755000000000000000000005600611735070120011733 0ustar Teaming

Advanced Network Services Teaming

Advanced Network Services (ANS) Teaming, a feature of the Advanced Network Services component, lets you take advantage of multiple adapters in a system by grouping them together. ANS teaming can use features like fault tolerance and load balancing to increase throughput and reliability.

Supported Adapters

Teaming options are supported on Intel® PRO/100, Intel® Gigabit, and Intel® 10GbE adapters. Selected adapters from other manufacturers are also supported.
 

NOTES:

  • Not all team types are available on all operating systems or with all adapters.
  • Be sure to use the latest available drivers on all adapters.
  • If you are using an Intel® 10GbE Server Adapter and an Intel Gigabit adapter in the same machine, the driver for the Gigabit adapter must be updated with the version on the Intel 10GbE CD or respective download package.
  • If a team is bound to a Hyper-V virtual NIC, you cannot change the Primary or Secondary adapter.
  • Intel 10GbE Network Adapters may not be teamed with Intel PRO/100 adapters. Devices based on the Intel® 82597EX controller only support AFT, ALB, and SFT team types.
  • Intel adapters that do not support Intel PROSet may still be included in a team. However, they are restricted in the same way non-Intel adapters are. See Multi-Vendor Teaming for more information.
  • To assure a common feature set, some advanced features, including hardware offloading, are automatically disabled when an adapter that does not support Intel PROSet is added to a team.
  • Hot Plug operations in a Multi-Vendor Team may cause system instability. We recommended that you restart the system or reload the team after performing Hot Plug operations with a Multi-Vendor Team.
  • TOE (TCP Offload Engine) enabled devices can not be added to an ANS team and will not appear in the list of available adapters.
  • Spanning tree protocol (STP) should be disabled on switch ports connected to teamed adapters in order to prevent data loss when the primary adapter is returned to service (failback). Alternatively, an activation delay may be configured on the adapters to prevent data loss when spanning tree is used. Set the Activation Delay on the advanced tab of team properties.
  • Fibre Channel over Ethernet/Data Center Bridging will be automatically disabled when an adapter is added to a team with non-FCoE/DCB capable adapters.
  • If Intel® Active Management Technology (Intel® AMT) has been enabled on a device, then you cannot add the device to a team.

ANS Teaming Types

  • Adapter Fault Tolerance (AFT) - provides automatic redundancy for a server's network connection. If the primary adapter fails, the secondary adapter takes over. Adapter Fault Tolerance supports two to eight adapters per team. This teaming type works with any hub or switch. All team members must be connected to the same subnet.
  • Switch Fault Tolerance (SFT) - provides failover between two adapters connected to separate switches. Switch Fault Tolerance supports two adapters per team. Spanning Tree Protocol (STP) must be enabled on the switch when you create a SFT team.  When SFT teams are created, the Activation Delay is automatically set to 60 seconds.  This teaming type works with any switch or hub. All team members must be connected to the same subnet.
  • Adaptive Load Balancing (ALB) - provides load balancing of transmit traffic and adapter fault tolerance. In Microsoft* Windows* operating systems, you can also enable or disable receive load balancing (RLB) in ALB teams (by default, RLB is enabled).
  • Virtual Machine Load Balancing (VMLB) - provides transmit and receive traffic load balancing across Virtual Machines bound to the team interface, as well as fault tolerance in the event of switch port, cable, or adapter failure. This teaming type works with any switch.
  • Static Link Aggregation (SLA) - provides increased transmission and reception throughput in a team of two to eight adapters. This team type replaces the following team types from prior software releases: Fast EtherChannel*/Link Aggregation (FEC) and Gigabit EtherChannel*/Link Aggregation (GEC). This type also includes adapter fault tolerance and load balancing (only routed protocols). This teaming type requires a switch with Intel Link Aggregation, Cisco* FEC or GEC, or IEEE 802.3ad Static Link Aggregation capability.

    All adapters in a Link Aggregation team running in static mode must run at the same speed and must be connected to a Static Link Aggregation capable switch. If the speed capability of adapters in a Static Link Aggregation team are different, the speed of the team is dependent on the lowest common denominator.

  • IEEE 802.3ad Dynamic Link Aggregation - creates one or more teams using Dynamic Link Aggregation with mixed-speed adapters. Like the Static Link Aggregation teams, Dynamic 802.3ad teams increase transmission and reception throughput and provide fault tolerance. This teaming type requires a switch that fully supports the IEEE 802.3ad standard. 
  • Multi-Vendor Teaming (MVT) - adds the capability to include adapters from selected other vendors in a team. If you are using a Windows-based computer, you can team adapters that appear in the Intel PROSet teaming wizard.
IMPORTANT:
  • Be sure to use the latest available drivers on all adapters.
  • Before creating a team, adding or removing team members, or changing advanced settings of a team member, make sure each team member has been configured similarly. Settings to check include VLANs and QoS Packet Tagging, Jumbo Frames, and the various offloads. These settings are available in Intel PROSet's Advanced tab. Pay particular attention when using different adapter models or adapter versions, as adapter capabilities vary.
  • If team members implement Advanced features differently, failover and team functionality will be affected. To avoid team implementation issues:
    • Create teams that use similar adapter types and models.
    • Reload the team after adding an adapter or changing any Advanced features. One way to reload the team is to select a new preferred primary adapter. Although there will be a temporary loss of network connectivity as the team reconfigures, the team will maintain its network addressing schema.

NOTES:

  • Hot Plug operations for an adapter that is part of a team are only available in Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.
  • The FEC (Fast EtherChannel) and GEC (Gigabit EtherChannel) team types have been renamed to Static Link Aggregation.
  • For SLA teams, all team members must be connected to the same switch. For AFT, ALB, and RLB teams, all team members must belong to the same subnet. The members of an SFT team must be connected to a different switch.
  • Teaming only one adapter port is possible, but provides no benefit.

Primary and Secondary Adapters

If the primary adapter fails, another adapter will take over its duties. If you are using more than two adapters, and you want a specific adapter to take over if the primary fails, you must specify a secondary adapter.

There are two types of primary and secondary adapters:

  • Default primary adapter: If you do not specify a preferred primary adapter, the software will choose an adapter of the highest capability (model and speed) to act as the default primary. If a failover occurs, another adapter becomes the primary. The adapter will, however, rejoin the team as a non-primary.
  • Preferred Primary/Secondary adapters: You can specify a preferred adapter in Intel PROSet. Under normal conditions, the Primary adapter handles all non-TCP/IP traffic. The Secondary adapter will receive fallback traffic if the primary fails. If the Preferred Primary adapter fails, but is later restored to an active status, control is automatically switched back to the Preferred Primary adapter.

To specify a preferred primary or secondary adapter

  1. From Device Manager, open the properties of a team.

  2. Click the Settings tab.

  3. Click the Modify Team button.

  4. Select the adapter you want to be the primary adapter and click the Set Primary button.

The adapter's preferred setting appears in the Priority column.

Failover and Failback

When a link fails, either because of port or cable failure, team types that provide fault tolerance will continue to send and receive traffic. Failover is the initial transfer of traffic from the failed link to a good link. Failback occurs when the original adapter regains link. You can use the Activation Delay setting (located on the Advanced tab of the team's properties in Device Manager) to specify a how long the failover adapter waits before becoming active. If you don't want your team to failback when the original adapter gets link back, you can set the Allow Failback setting to disabled (located on the Advanced tab of the team's properties in Device Manager).

Adapter Fault Tolerance

Adapter Fault Tolerance (AFT) provides the safety of an additional backup link between the server and switch. In the case of switch port, cable, or adapter failure, network connectivity is maintained.

Adapter Fault Tolerance is implemented with a primary adapter and one or more backup, or secondary adapters. During normal operation, the backup adapters are in standby. If the link to the primary adapter fails, the link to the secondary adapter automatically takes over. For more information, see Primary and Secondary Adapters.

To use Adapter Fault Tolerance all adapters must be connected to the same subnet.

Switch Fault Tolerance

Switch Fault Tolerance (SFT) teaming allows you to connect each of two teamed adapters to a separate switch.

Switch Fault Tolerance can detect failures when they occur:

  • on either teamed adapter
  • on either cable connecting the teamed adapter to its switch
  • on switch ports connected to the adapters, if link is lost

In SFT teams, one adapter is the primary adapter and one adapter is the secondary adapter. During normal operation, the secondary adapter is in standby. In standby, the adapter is inactive and waiting for failover to occur. It does not transmit or receive other network traffic. If the primary adapter loses connectivity, the secondary adapter automatically takes over.

In SFT teams, each adapter in the team can operate at a different speed than the other.

Configuration Monitoring

You can set up monitoring between an SFT team and up to five IP addresses. This allows you to detect link failure beyond the switch. You can ensure connection availability for several clients that you consider critical. If the connection between the primary adapter and all of the monitored IP addresses is lost, the team will failover to the secondary adapter.

Adaptive Load Balancing

Adaptive Load Balancing (ALB) uses software to balance routable traffic among a team of two to eight adapters or LOMs (the team must include at least one server adapter) connected to the same subnet. The software analyzes the send and transmit loading on each adapter and balances the rate across the adapters based on destination address. Adapter teams configured for ALB also provide the benefits of fault tolerance.

NOTES:
  • ALB does not load balance non-routed protocols such as NetBEUI and some IPX* traffic.
  • You can create an ALB team with mixed speed adapters. The load is balanced according to the lowest common denominator of adapter capabilities and the bandwidth of the channel.
  • On Windows systems, Receive Load Balancing is enabled by default.
  • Receive Load Balancing is not supported on Microsoft Hyper-V*.

Virtual Machine Load Balancing

Virtual Machine Load Balancing (VMLB) provides transmit and receive traffic load balancing across Virtual Machines bound to the team interface, as well as fault tolerance in the event of switch port, cable, or adapter failure.

The driver analyzes the transmit and receive load on each member adapter and balances the traffic across member adapters. In a VMLB team, each Virtual Machine is associated with one team member for its TX and RX traffic.

If only one virtual NIC is bound to the team, or if Hyper-V is removed, then the VMLB team will act like an AFT team.

NOTES:
  • VMLB does not load balance non-routed protocols such as NetBEUI and some IPX* traffic.
  • VMLB supports from two to eight adapter ports per team.
  • You can create an VMLB team with mixed speed adapters. The load is balanced according to the lowest common denominator of adapter capabilities and the bandwidth of the channel.

Static Link Aggregation

Static Link Aggregation (SLA) is a performance technology developed by Cisco to increase throughput between switches. This team type works with:

  • Cisco EtherChannel-capable switches with channeling mode set to 'ON'
  • Intel switches capable of Link Aggregation
  • Other switches capable of static 802.3ad

The transmission speed will never exceed the adapter base speed to any single address (per specification). Teams can contain two to eight adapters, but must match the capability of the switch. Adapter teams configured for Static Link Aggregation also provide the benefits of fault tolerance and load balancing.

NOTES: 
  • The FEC (Fast EtherChannel) and GEC (Gigabit EtherChannel) team types have been renamed to Static Link Aggregation.

IEEE 802.3ad Dynamic Link Aggregation

802.3ad is an adopted IEEE standard. Teams can contain two to eight adapters, and you can have a maximum of two IEEE 802.3ad dynamic teams per server. You must use 802.3ad switches (in dynamic mode, aggregation can go across switches). Adapter teams configured for IEEE 802.3ad also provide the benefits of fault tolerance and load balancing. Under 802.3ad, all protocols can be load balanced.

Dynamic mode supports multiple aggregators. Aggregators are formed by port speed connected to a switch. For example, a team can contain adapters running at 1 Gbps and 10 Gbps, but two aggregators will be formed, one for each speed. Also, if a team contains 1 Gbps ports connected to one switch, and a combination of 1Gbps and 10Gbps ports connected to a second switch, three aggregators would be formed. One containing all the ports connected to the first switch, one containing the 1Gbps ports connected to the second switch, and the third containing the 10Gbps ports connected to the second switch.

NOTES:
  • Once you choose an aggregator, it remains in force until all adapters in that aggregator lose link.
  • In some switches, copper and fiber adapters cannot belong to the same aggregator in an IEEE 802.3ad configuration. If there are copper and fiber adapters installed in a system, the switch might configure the copper adapters in one aggregator and the fiber-based adapters in another. If you experience this behavior, for best performance you should use either copper or fiber-based adapters in a system.
  • If multiple switches are used, all team members connected to the same switch must operate at the same speed.

Before you begin

  • Verify that the switch fully supports the IEEE 802.3ad standard.
  • Check your switch documentation for port dependencies. Some switches require pairing to start on a primary port.
  • Check your speed and duplex settings to ensure the adapter and switch are running at full duplex, either forced or set to auto-negotiate. Both the adapter and the switch must have the same speed and duplex configuration. The full duplex requirement is part of the IEEE 802.3ad specification: http://standards.ieee.org/.

    If needed, change your speed or duplex setting before you link the adapter to the switch. Although you can change speed and duplex settings after the team is created, Intel recommends you disconnect the cables until settings are in effect. In some cases, switches or servers might not appropriately recognize modified speed or duplex settings if settings are changed when there is an active link to the network.

  • If you are configuring a VLAN, check your switch documentation for VLAN compatibility notes. Not all switches support simultaneous dynamic 802.3ad teams and VLANs. If you choose to set up VLANs, configure teaming and VLAN settings on the adapter before you link the adapter to the switch. Setting up VLANs after the switch has created an active aggregator affects VLAN functionality.

Multi-Vendor Teaming

MVT allows teaming with a combination of Intel adapters that support Intel PROSet, Intel adapters that do not support Intel PROSet, and non-Intel adapters. This feature is currently available under Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2. All adapters that appear in the Intel PROSet teaming wizard can be included in a team.

MVT Design Considerations

  • In order to activate MVT, you must have at least one Intel adapter or integrated connection that supports Intel PROSet in the team. That adapter or connection must be designated as the primary adapter. 
  • A multi-vendor team can be created for any team type. 
  • All members in a MVT must operate on a common feature set (lowest common denominator). 
  • Manually verify that the frame setting for all adapters in the team is the same.
  • Verify that the RSS settings for all adapters in the team are the same.

Setting Up Adapter Teaming in Microsoft* Windows*

Before you can set up ANS teaming in Microsoft Windows, you must install Intel® PROSet software. For more information, select Intel PROSet in the Table of Contents (left pane) of this window.

NOTES:
  • ANS Teaming is compatible with Microsoft Network Load Balancing (NLB/WLBS) running on Microsoft Windows Server* 2003, Microsoft Windows Server 2008, and Microsoft Windows Server 2008 R2, when in multicast mode only. To use Microsoft Network Load Balancing in an Adaptive Load Balancing (ALB) team type, Receive load balance must be disabled.
  • If Intel® Active Management Technology is enabled on an adapter, you will not be able to add it to a team. When you create or modify a team, the adapter will not be displayed in the list of available adapters. The adapter will not have a Teaming tab on its Device Manager property sheet.
  • Teaming only one adapter port is possible, but provides no benefit.

Last modified on 3/07/11 10:18p Revision

DOCS/DESKTOP/test_dm.htm0000755000000000000000000000343011656741062011771 0ustar Test the Adapter

Test the Adapter from Microsoft Windows*

Intel® PROSet allows you to run several diagnostic tests, including:

  • Connection Test: Tests the adapter's connection to the network. If the adapter connects below its maximum speed, the connection test reports the reason for this lower speed. If the adapter has link but does not have an IP address, the test reports whether the adapter can communicate with the link partner. If the adapter has link and has an IP address, ping tests are performed.

  • Link Test: Tests the link speed and duplex capabilities of the link partner and reports the optimum settings.

  • Cable Tests: Provide information about cable properties.

  • Hardware Tests: Determines if the adapter is functioning properly.

To access these tests, select the adapter in Windows* Device Manager, click the Link Speed tab, and click Diagnostics. A Diagnostics window displays tabs for each type of test. Click the tab and run the test.

The availability of these tests is dependent on the adapter and operating system.

Last modified on 4/20/06 3:48p Revision

DOCS/DESKTOP/toc_dm.htm0000755000000000000000000001134711701323424011572 0ustar
Search this guide
  

Overview

System Requirements

Supported Adapters

Hardware Installation

Insert the Adapter

Attaching a Low-Profile Bracket

Attach the Network Cable

Microsoft* Windows* Setup

Install the Drivers

Intel® PROSet

Setup Speed & Duplex

Command Line Install for Base Drivers and Intel PROSet

Windows Unattended Installs & Updates

Microsoft Windows Advanced Features

Teaming

VLANs

Power Management

Simple Network Management Protocol (SNMP)

Quality of Service (QoS)

Save & Restore

Windows Management Instrumentation (WMI)

IP Security Offloading

Setting up Microsoft Hyper-V* virtual NICs on teams and VLANs

Linux Setup

Install the Drivers 

Installing DOS Drivers

Intel Boot Agent

Troubleshooting & Support

Configuration and Troubleshooting

Other Windows Issues

Windows-Based Testing

Linux-Based Testing

DOS Based Testing

DOS Related Issues

Indicator Lights

User Guide for Linux Users

Customer Support

Get Latest Drivers

Warranty, License, Regulatory

Limited Warranty

Software License

Regulatory Information

Copyright © 2002-2012 Intel Corporation.
Legal Information

Last modified on 1/25/11 10:10p Revision

DOCS/DESKTOP/top_d.htm0000755000000000000000000000055011656577042011444 0ustar

Intel® PRO/100 Desktop Adapter Guide

User Guides Home

DOCS/DESKTOP/top_dit.htm0000755000000000000000000000056211656577042012004 0ustar

Intel® PRO/100 Itanium Desktop Adapter Guide

User Guides Home

DOCS/DESKTOP/trbl_dm.htm0000755000000000000000000003446611656741062011772 0ustar Configuration and Troubleshooting

Configuration and Troubleshooting

Common Problems and Solutions

There are many simple, easy-to-fix problems related to network problems. Review each one of these before going further.

  • Check the cable. Use the best available cabling for the intended data rate.

    • Check that the cable is securely attached at both points.

    • For copper connections, make sure the cable is a 4-pair Category-5 or better.

    • Make sure the cable length does not exceed specifications.

    • Perform a cable test.

    • Replace the cable.

  • Check the link partner (switch, hub, etc.).

    • Make sure the link partner is active and can send and receive traffic.

    • Make sure the adapter and link partner settings match one another, or are set to auto-negotiate.

    • Make sure the port is enabled.

    • Re-connect to another available port or another link partner.

  • Look for adapter hardware problems.

    • Re-seat the adapter.

    • Insert the adapter in another slot.

    • Check for conflicting or incompatible hardware devices and settings.

    • Replace the adapter.

  • Check the driver software.

    • Make sure you are using the latest appropriate drivers for your adapter from the Intel support website.

    • Disable (or unload), then re-enable (reload) the driver or adapter.

    • Check for conflicting settings. Disable advanced settings such as teaming or VLANs to see if it corrects the problem.

    • Re-install the drivers.

  • Check for recent changes to hardware, software or the network, that may have disrupted communications.

  • Check the adapter release notes (readme.txt).

    • The Known Issues section may have specific troubleshooting information for your configuration.

  • Check the Intel support website for possible documented issues.

    • Select your adapter from the adapter family list.

    • Check the Frequently Asked questions section.

    • Check the Knowledge Base.

  • Check your process monitor and other system monitors.

    • Check to see that there is sufficient processor and memory capacity to perform networking activity.

    • Look for any unusual activity (or lack of activity).

    • Use network testing programs to check for basic connectivity.

  • Check your BIOS version and settings.

    • Use the latest appropriate BIOS for your computer.

    • Make sure the settings are appropriate for your computer.

  • Reboot the computer.

The following troubleshooting table assumes that you have already reviewed the common problems and solutions.
 
Problem Solution

Your computer cannot find the adapter

Make sure your adapter slots are compatible for the type of adapter you are using:

  • PCI Express v1.0 (or newer)

  • PCI-X v2.0

  • PCI slots are v2.2 

Diagnostics pass but the connection fails

Make sure the cable is securely attached, is the proper type and does not exceed the recommended lengths. 

Try running the Sender-Responder diagnostic Test.

Make sure the duplex mode and speed setting on the adapter matches the setting on the switch.

Another adapter stops working after you installed the Intel® Network Adapter

Make sure your PCI BIOS is current. See PCI / PCI-X / PCI Express Configuration.

Check for interrupt conflicts and sharing problems. Make sure the other adapter supports shared interrupts. Also, make sure your operating system supports shared interrupts.

Unload all PCI device drivers, then reload all drivers.
Adapter unable to connect to switch at correct speed. Gigabit adapter connects at 100 Mbps and 10 gigabit adapter connects at 1000 Mbps.

This is applicable only to copper-based connections.

Make sure the adapter and the link partner are set to auto-negotiate.  

Verify that you are running the latest operating system revision for your switch and that the switch is compliant with the proper IEEE standard:

  • IEEE 802.3ad-compliant (gigabit over copper) 

  • IEEE 802.3an-compliant (10 gigabit over copper)

The adapter stops working without apparent cause

Run the adapter and network tests described under "Test the Adapter".

The Link indicator light is off

Run the adapter and network tests described under "Test the Adapter".

Make sure the proper (and latest) driver is loaded.

Make sure that the link partner is configured to auto-negotiate (or forced to match adapter)

Verify that the switch is IEEE 802.3ad-compliant.
The link light is on, but communications are not properly established

Make sure the proper (and latest) driver is loaded. 

Both the adapter and its link partner must be set to either auto-detect or manually set to the same speed and duplex settings.  

NOTE: The adapter's link indicator light may be on even if communications between the adapter and its link partner have not been properly established. Technically, the link indicator light represents the presence of a carrier signal but not necessarily the ability to properly communicate with a link partner.  This is expected behavior and is consistent with IEEE's specification for physical layer operation.
RX or TX light is off

Network may be idle; try creating traffic while monitoring the lights.

The diagnostic utility reports the adapter is "Not enabled by BIOS"

The PCI BIOS isn't configuring the adapter correctly. See PCI / PCI-X / PCI Express Configuration.
The computer hangs when the drivers are loaded

Try changing the PCI BIOS interrupt settings. See PCI / PCI-X / PCI Express Configuration.

The Fan Fail LED of the 10 Gigabit AT Server Adapter is on (red) The fan cooling solution is not functioning properly. Contact customer support for further instructions.

Multiple Adapters

When configuring a multi-adapter environment, you must upgrade all Intel adapters in the computer to the latest software.

If the computer has trouble detecting all adapters, consider the following:

  • If you enable Wake on LAN* (WoL) on more than two adapters, the Wake on LAN feature may overdraw your systems auxiliary power supply, resulting in the inability to boot the system and other unpredictable problems. For multiple desktop/management adapters, it is recommended that you install one adapter at a time and use the IBAUtil utility (ibautil.exe in \APPS\BOOTAGNT) to disable the WoL feature on adapters that do not require WoL capabilities. On server adapters, the WoL feature is disabled by default.

  • Adapters with Intel Boot Agent enabled will require a portion of the limited start up memory for each adapter enabled. Disable the service on adapters that do not need to boot Pre-Boot Execution Environment (PXE).

PCI / PCI-X / PCI Express Configuration

If the adapter is not recognized by your OS or if it does not work you may need to change some BIOS settings. Try the following only if you are having problems with the adapter and are familiar with BIOS settings. 

  • Check to see that the "Plug-and-Play" setting is compatible with the operating system you are using.

  • Make sure the slot is enabled.

  • Install the adapter in a bus-master slot.

  • Configure interrupts for level-triggering, as opposed to edge-triggering.

  • Reserve interrupts and/or memory addresses. This prevents multiple buses or bus slots from using the same interrupts. Check the BIOS for IRQ options for PCI / PCI-X / PCIe.

Here are some examples of BIOS parameters:

PCI / PCI-X / PCIe slot #: Slot where the adapter is installed
Master: ENABLED
Slave: ENABLED
Latency timer: 40 - 80
Interrupt: Choose any one of several that the BIOS provides.
Edge-level: Level

The exact wording of the parameters varies with different computers.

Other Performance Issues

Attaining the best speed requires that many components are operating at peak efficiency. Among them are the following:

  • Cable quality and length - Do not exceed the maximum recommended length for your cable type. Shorter lengths often provide better results. Check for loose or damaged connectors. Check the cable for kinked or damaged sections. 

  • Bus speed and traffic - The PCI bus speed accommodates the slowest PCI card installed. Check to see if you have a card that is slowing down your system.

  • Processor and Memory - Check your performance monitoring programs to see if traffic is being affected by your processor speed, available memory or other processes.

  • Transmission frame size - Your network performance may be enhanced by adjusting or maximizing the transmission frame size. Operating systems, switches and adapters will impose varying limits on maximum frame size. See the discussion on Jumbo Frames for your OS.

  • Operating System - Networking feature implementation will vary by operating system version, such as offloading and multiprocessor threading.

Last modified on 8/21/08 11:09a Revision DOCS/DESKTOP/trbl_win.htm0000755000000000000000000000543411656741062012160 0ustar Troubleshooting

Microsoft* Windows*-Specific Issues

Use the information in this table after you have reviewed common problems and solutions.
 
Problem Solution
Event viewer message: A device attached to the system is not functioning If there is a BIOS setting for "Plug and Play OS", it should be set to "NO" for all versions of Microsoft* Windows*. 
Microsoft Windows XP or Microsoft Windows Server* 2003 gives an error "Device cannot start (CODE 10)" when you install or update drivers for your gigabit adapter. 

Microsoft Windows XP and Microsoft Windows Server 2003 ship with some older plug-and-play drivers for gigabit adapters present. Windows XP has been known to have trouble replacing a driver file automatically. Updating these drivers with Intel's latest drivers may cause this error message to appear. Rebooting your computer will clear the error and allow you to use the full functionality of your adapter. 

Disable, then re-enable the adapter in Windows Device Manager.
After upgrading operating systems, Intel® PROSet is no longer available

If you are upgrading a Microsoft Windows operating system and you have Intel PROSet software installed, it will be deleted in the process. You will need to reinstall Intel PROSet.

Terminal Server support

When using Terminal Server, make sure only one session of Intel PROSet is open at any one time. Simultaneous sessions are not supported in Intel PROSet.

 

Last modified on 4/01/09 4:16p Revision DOCS/DESKTOP/vcci-a.gif0000755000000000000000000007771111656741516011472 0ustar GIF89aD(((@@@UUUgggyyy! ,D#dihlp,tmx|pH,Ȥrl:ШtJZجvzxL.zn|N~ H*\ȰÇ#JHŋ3jȱǏ CIɓ(S\ɲ˗0cʜI͛8sɳϟ@ JѣH*]ʴӧPJJիXjʵׯ`ÊKٳhӪ]˶۷pʝKݻx˷߿ LÈ+^̸ǐ#KL˘3k̹ϠC@Ө~:װsfD۸sͻ Nȓ+_μУKNسkνËOӫ_Ͼ{˟OϿ(h&k4m Fhb4"f a"#h(S!+0b!3h8>S ;@c CiHRK&PfdSFiXX!Yv嗊T`iehSypiAYx/9j(Ƒ行6o@褔^)iV@f*jQꨨjg꫰j[j7JcKذ` k楬6+fmdrշZ+>e.Dk4Ѐ 0ڵ p@10C `oĞ,|{*(pFK00g$_,4ˢ3/@ R$"/s_C0mPP'+51";lp.s;@  n T0G`Ns(PmmҺKvAH*؟@ `)(1s&HPχ2^ {fW0[C>>jiRA#쏄H;\ @U|OMcQ Rg25`MɺRUJNS?XgY,ijWMB|@`+*"zЄ޲w<`u6 ], 0YζTvEPWRM 2].B+.7|k{sŁQ+Tմ&p*˂Vy` 00vS.X3l׬@Ԋe]+<;ȫ|W-1k7nEc!Z6;l a3!MrV^2V+N%M5Ol@6>ŠGT3`/7y `3փox$Oʉ8A=3? _t3ɻKWIpы .؄02;ҥ65q1Z`mpWaSc^5Ŭp ecr?0u{ *࢑#i6z+gڼ^lRKbؚkt! G:8zQp16,}(B,3gNU!"=@}n_Rt\|- =/Ad,NŝXS[},NjN.K(E_mh_K@Ygԃg(b%`,[(w]>*tG 4[CWW|gbm0"0U715{w+faaV1k=I<5mFz3C YB2AUi;}e i\ N2p}FyPliHimFc; 01r8ut'"i vvDiR^3Nзt_(+0uy@m|u+fc?f7w~`ȉ6: T0=DVct<01HIT|%/A LtANf:stV$0#I)@ҁ4)329cӐ x blYYc7" &P<+ 5ȅ39:TBdN:SJLiw4wQ@TiWlB($ch`ل" @Shij?ؙ "`iYݥӜ~'LyD@yKV5XVyU DYE-:+s ZԚ1}D96P&@^M븛ū)&]FTJyu˹}I7 jov~10 SY6:%hpbY vS*韼Y:mLYzaDq 'G-XX(ܴo7N k*v[_iN.of#Е dX`HՉw1xIGQǘh9:+TvX^Ʌ^zTZxXSXW:ӑ3J V41,2-d~/2:JlgvAk@ԍGXLN?R&86 *+2{생Hb.9i< =Eh0tq2KTYC絶9giT:fNn\8k{@j(,zo|~L E;}Qc܊Wƨ0yeyAC:suKy*0++.VOCQ@E2be/6uu0|DSh#vkZsڵ{KRXEtMhL$W) /@vEq⻠^P*uG|TI[F-̪xz h[c;f߻-gAU4UEk6 5Hӣ (AA [s]\6wK Uk(0|EH6k/kcvs0P)3Ifutcm̔*d7kE9.$*? |\\&_ ēAh$p>:eg'0=Z ]x^XPNA8n;^=6 8|EP ^;[R&hŹ:hLQLݜ%lp=X? ԻFK0tu-ci~-ߍ; fP>SS^VӦ(YNWܰ>f{ߜ<"P S$hܬ/0ebhY#w^ǚ<e')+-'-i6}FmS<9>!ꭢklM|lb"ո^Cm/ ifNPh~.2u~wJo:NVHS7~A+_i?3TE%,d/4Π3*n޵5Xb˖&?_4% œ?1^zȾL5_KoADyCLvK3C";+0x5`/|iNӽfuGf*?9ss;˒a HlB p"s FRT,[V҃4MFoI;m~ J =D^8 ع f!8)8) -A-M=z-q e:E:4 Xfa:!=,9∬$$@$.IRZO9qz0"48n5=Xj%W 4U θcZ3 6Z,xub?uQ؀'k q"XsEGz|2̓nr~-i0l.V|TB"Z~1FW}8K )20G=* 裈M,ˤz|E TeJv z@ (cuh{Kt8z2@!O_*,a7P`2Ze7p](\a`kK*8Ɣalhr'/+Xa@ţDzWHZy]|&<'񤾜(-N\d@MֽTE\ ßuRY3)DVM{Бu#p?Qv{(pSO}V {N m8EFXXʋ%߈0 gЅu8g"V|T)IU8QM㰮5/!J]}=ru+Zs0ٽ *hU b ,Cj v({1@P8saҏ"59x`V<7 :Dby`` l3úR1/tzAbP$`v 7DD4$"P"-EUS` ieùwmwF \rt )zMbKXC>Ps%6<6O %kh1/ÉLw=Z IiK:t @!Pw{`ub .@t? K9֌P <ݘ*z8l9d/FSG)@1[$//2'LS\,dBpۘ`b})j6q<$s Q!0b&^W!嗪UnX {E>p#cWΘ?2q&J9.RaOj#cN/>[?*Ϊ-u "=sM- ]!ദ %4;66HXA/PSMY5 ͥzP馍Ơ{riFV/dpyabgݜE70(:Yi`5ChD~?<+׬4`R,~wQ[li,R>8p lFqr" TؗF2KI83]_=ϠEVN`@he-H j3 Υ xTYۤ&;ziZj!ͅqn!2#K{fdY&`\Xo2LSbǞH~&9Xwfk:%mKkJ\ 4X 6.4m9Xܶjo,fW_p[E,bdnr co\Gcvq:/(x/.;kmF~__y0$l`$ خ namhYCXӘ10edvy1X_{ewP|IXԦc71vwYd zTdSceri]֒|F~] 5\61 |Y*HP)`{K#aT] usהF=#`)+M؝UU)ZgSF wB=_4(;(BI.ep%XhH@ך۪n7̼[5'ir lx&_oBmf!j39r0?*,\}V񛦁#s7hmP  Դo? m;s@Mi=BCm i)sH@L@ @4<[Ad6M^T%ܧ45ΡA}OЅ_L]!_(d0L\iyCe _DI)IQCډܘXQٍ m]VA]yĎ,XDk700ҬB0E-Pux^ =!}4[> ^09Xo"_[IlF~)=sS4_Ae_ CRIxA!>#_HU\P=\TSΝC)_8}Mf)$C7z0h J +ـ|-y6V?5և.J;QA-Cʐ-jZU DM C3Z@-@X؟H=˕#iAr昡V!1㈰apܠw;J9Q7bǘ6JS1P dBoUMi7Ui`*:Q<pzf R/@&0M$ef@4oFaJI&FDA=Ru E A\f&ah̵fGgm&e'fSBe@@od80_\PM>0c^c@2l$@,Ѥ%('yAF4ِqE`@m88$Fc"+ Р _LmgL+.@4ߤP+ʹπ&l=0h餺ZoM}ҚpR qg=Q@sւC |rvu&Xvq'0y( Kx_Cz)ݵ'v|~|Ì~\g5dhn)TinR UdЀX 2QWF ~~'7:h J*ci8$. _tP\^i$]VI*@<=ND)^i6WʐHi}vNKie5E08]^<%DYYg)BNj5 2J c)Y&ᘺǘRQd"s)zƚj4⍝Dn:2؀h~<a̢~àĄ,H,n,gVUCw0'8] Dl)!u60ı T~*%C eDJk8(x׋d]%%mM< #Z"$:@ۅRX΄͚;TI:z )ˊU$̎AP2RR-*mjIjmZ'-m8ZLȐ/:`9s{p|v"(ۗ _<]nM{΍IW0 ֋̞ ["(Sws[7 RnȰkQ:݁tVХꌴ58w]U )@{S|y+KCMg8|Oʠ;ESnTUzCƜ \QO+sS v&o oNbi(n!KeG `H ,U\eR<7<Ïë!_{DPYnx)<!j0AR(BM(0iSƛr.o;NW_4k4R3-C&H0$ Db8)TX74@gR@9GBb'"w,<<:X0r`y"]%dT#EH+Ϣ$zQI[@VȌZyMjML@PS"]G1  g G4.T: ʈѣIɴӨ'%KVo xp61%] @K"CH3`@I_79r j=;1W^p[ Xqt)wswP&J`@̳ܔ#bC2_@9g(]g@~SZ  P@kb0`(ћ,~rvbWv E1SUzQޘU|@Y" ؀o8%v~35*i X*c>+5z  %a)sRHzDۄhl<@5V~4Mֱr(sHk?aGԧ:'nՄm1Yz}auZ%p@ `a ^QU,PM^bc+89&¼.:#TQc6<5I%|*iq9yHE*`iÖ]JeVAf%ްjmBuw8{#|F䉍 2:58P)m˶/ktADtC <u1ˀ['j-΅Z( 4"3^m_/NX*m:  W/CQ9HO(d+qvKຨ*IkHU8a -@rm`BŽ`lp4̑Op*%Ԋ #P~ړ C=e "5p4G\5pr3|_1"}3 !>!3>Brh,J\z<Q ‡Hah! 1ٍS}0iAuàBb aQwBM RGb NvX S@.02S Fͩb%S7FtJVWv'8"a'pօj"^+d"o;R8DOSg=ЕYU"?BU%|j[^ď%߸`ry~biGFQ @~ 'C}Y]F1)$jsSMЊ.l9V^9t ķP A؀QF`Oֿ?l;؂WD/l?$F R!*C ,' J}`)OipL;uBqVݭolj1@r+c'Ј$"9PVP.t4R~H~AE7eY$]'"3I!XE nR"6̗ľ0]mVB('PP"OVE,2Bo]ꄞdlZ&`F% ?*WK_U2a})$c 1Dg V Šrf$j:Uq^8nh)Fv Tй7 A9Q0' f7l4}!GLUndtS6eTZ&v.o> q:PXpϴ:T+m|KXԊ3*o}$X8Aa*|A 4h}6ǙA{]k޹ԕ0=xޮwT$ok3%nY]" L -ʷd{F$CAS)HfU[?8"t1& >94 `O[K>8TyK'#Tq7109ˉԦ6`X۰ֺ\)7M;G %d+A@0%;sUa[况-*;ڛk+pv+_7% 󟏝4̓skw0@; 熥?=vj:?·fPaͯWt'2l:61+gPwLp* ( :0Ls0Y)-(4R95r 7Nc9y7'ǃҁAH@*YrQ!r€sEh,,<_!#xk%K=dZsF335i;{(HhxȈ_؇nHhȉ᠈(PGȊ芯(HhXxȋ苿(HdDxŨȌ(ȈȃH٨ȍ(爎騎ȎH^樂hȏH(Ii Ik  )Iiɑ !ɉ $)')+ɒ-[&~03I5i7))c9? A)C=)uFIIKɔM错NOIUiWY)؈S_ a)cInvekɖm8 ɕoIuiwJy )ؗy8ɘX!)Iiyə陟 |/iY8 )[IɛV7ؚ)IYIiɜIiy;ډ ȝi牞y)婞 )ȞRɟ*Jsr ʠ j jJj֑ʡԹ#J%j$'ʢ-ꢒp/J5j?7ʣ=W4?JEj5GʤMꤋ=OJUjnz3Wʥ]UD^ǃ.͘mHu`p6@J.Cv{q.`YئI}ꂱ Qz80ȕv +gЂdU"+Kp1sm3~v/꫉C\wA,neBf:ө-6`ҬraaJp}b+̺0>zNӪ[JךJҭkQMȆ:WJPCeq[qC֯i KBbk' ˰3gCOd*CByv"Hs99;nU2WT{tVk1;˺KJ%;LF  @R !]@IWkq3^`,[N@rwG@ { Pvߢh,@SK.m8) _pnl7ʳev^GN,"Vп3P9uD P$ LBQZ@  p1gBP1=&{3ga<,rta#UG0k}jk$t02SlÔU չ a;Ir:v5v3pm˰rsF0suyEaXR}N1H i,1@!tt#%}ߙFG6݄op JoSQ]C h)7@6"4}$+)>3ѿr 6àymr@e|ȄZ3|ҿzhG~A  TCu`ػEs1>}Q9{}w' ).GP[=ܷl(:]حzݭPƆE,4 `Dᡆ~u0hޗ]xlűSY+ʯ-( F$4)O Nֳ^N.+fEr =D b%N;4Ysq{nnېP,Ւ >;+QȊHܪ<XrC$`ޫJY;pV0ۆݩDŽT96U9M|CpD%mhĊv.H忽Y. L L>8 (w<#RP+Ю.82xU-P']VS`Dؖv"FQ}) ,Oˈ@R.'O( Ba3' 4mC-pZ5!oRrC$dJmsHo=\ .9%&ȊL'S@N~z p4Z~)}\^ʒ EQZLcV };T@|#o}F\dagTo%K '0Bo0~{000F#2hC "`˜R"Q(zY)1آ6i X, @ a`J#SLAQhh]O b C[B(M@`,X`VQaNraCtIvζCCϙ  .cK.Z@K؎͠Y`t9P#ƙ/#C`I9Ud N݈8B0Mف_ 3Ɖ?@BwbA_ l1@7ʓ^尅gEy$(Hi1`'B zEC_80  [64ev$_W[a6O3}iCJFw8lA*VɌH( [12CN > ,^耏Be\Kᝈ(YhF-@lXzZ(C0vp\:jBn ۔!gK>Pi`v%0֓h 3 ҂ȀhIJ; Ƹ1,ݾFe>emuՁ`IPOEՎCf&& ;!+]*6#`X $O=Ä\A hK tDv3Iŀ)]6*AxhR=k7 ͥ^LBS4oܔոDQ#Soa*6SVeLV [u`kR:Ǹ),Վ,] kW[V-lKMtSlW Y"0q84[-΂ e(V q\ju>9S"T>6:nO[8Jk½a\)c- s\4HWyu|2Anp&-\~ 0Ì}$J){V. 383%0t5Գ51,C4˝Cb?K%RDͣ(k@g,q1a{@^h`)@_|'< S "2N2FA)k_&0Ys0XܔݠYM5'؝^ =U 4!TGEFM@ %E`d^pDhȆ^ 0ŞQ[1_ `}O9(IQ`!@Ŧp_.z<͌aFǩ45N(JL$%a_ >`W#"F!FcShzNTI fa SӮ pDTtQm:bp<$Ԕg0"9ՙY@JhuHX |)AIޓ1$Q(zHۭh#$8bQN%!td,<k$|\[v@3R!2,.G@L6dCG)@EYe3UЇOH`\L$PXX^VjS;R;JKQ#_(K6Lz$ (^n8F;CH34̍x(Th0T=ɹ&^ HK!A1$]B gm:ݙXARu$#b;pWh3dWRBNvp>N2H 8\d%ӡ\>fB-!Ų\rBlZNbcNghԄ""zAh D}5`DM%T5,B'`'T("m l!IUCZ.gՠ2]%]7uwmC '`ψۼg4qJq$"iX[R.tF#70|PC]Kknhu2@^ڮd)!Kr4Q' ʗgj@$Cs^.@su'uZm'Cv';4x:j^d"!lv.@{b$ƧI\ɠ}VB~~%I)u(8@9O)Efj]0hٲjrfhU\h|cfDqhJ˄h͌hU((_g4CGzSՅ %2"h,4)X<)^ތ Z)Ry +ɀqY68`A|,]x7)VXq5Xj j.I $Ϣ6DJGRjnm ~6nTQT6ޤbKPV*AtOg2l?؜ (<M,+>RMbLXP,$ `MN3zvP:("(OYѸzPC z[욾(VVZ-g .aZ auk(-UnV&&An %/!qj_i-a(ݖ#BTy[HAQæٞ+ςCYj ¬!mоQJ**f ܚgm֭^ mm.Ȇ+N. Yo.nC 7LN.B^ndn#nnRMJZnyn嬮nԉo[ .!3j6$d>@2q lFoLo^:/elRl%qJ7xšm &"ARW z/@R+*ɝ,pΏB(ZOl\rx'.oK ץKuʺ~c, [Jױ0T(8;%h.6CJdnB~DŽ->r-ʣ! d(KA`95昶C d{:q5W@: # ?*$syӨR+dvJovƩ+0t,or~2O?M7Ǎ XZ X*raNVUzD K^=ƞR#ajL' rf,tDWML;k; ` 4" 8tCud7RsEEehtG' ʪ{tUfڑL CF4Pn&;,OC]PcQQcȷ*50L0jrCq%M5&ղ)c5h#tc2=ڒ+3Ԟ;@*nBB)<; %+PjG?'4 sN Y+@;`ɢb =J,XvI}Uhl9`@Ej-$Ғ30 @*+J'`Ica g:Ja405 4 ꮤ;c13(N%ĐYBl3$K@㬌~rZ)&!"gswwMP58ktaQ)IBȓJeB!C;ȟ"Md[+aa`Z$J6Ũe%$`z PCa/Lp2C("B(C'@c3Ds>!1(6P'9*:Xʰ/@$#Jȹ4gIm,79~RGqhG)0Ȳu;Ct:R{tZ 6tGO`@"U:j 0EnVP6t 9̑4yB)` xY6XՂϽO@AFDv^{W nO9k`@(EJpYh+Yp(ԷTWAʃQz&,KIډS7D쮖\R E,I0 3-iJ+9.'$fqh#"JChIӐKmG@"B00K8fIJZfR-@C!JeL٘˴:(GZVaص<,6#Z㜔UF\mt6f<0|=l]L p;+ X[oc@١M 4)&HVe55 T@2 e*ɼM9\>U0IqYP#~K[z !aď-EM{tV:㬉{$8MA@l]Z,W!Q0ChS%q;BYzmݘp ت !T'9ki-6PJl9 yP N. `0cyathNc%ԒUl`02x2?嶥Zlo/\9U>ܜCO=c9hN- Ho!Μ2Sz^g`.@~D=_]j5B%C˂`d43i\zԈ`y_uXCA֜5\.ZlZ {3LS|lSz:ٲ6ɳ]me}r_u~*9bۛjl ql-U'n7I\xqw^8h>`{q("@rqrsf(*G_rrsCsC&BlW9\sMҀ+C7&wWJtePp[2KAj01X'f#4u-ZawkBddjG)(&trG@:eaYxk!XmUg,:90J 5y`qø-AЃeqϓD(6hqc5(Ƈw eWW8Y[J@th0]mÆ|b%tYvC@Hz[9v=.M(+|gjҎ0PrP[ U(N7%~S|A &"#9D8֋J=Hr浌PЌvF`64~{R\-}귑wSm\V@&&A9E88hfx&cۆ"0I~"4'^Gjѐ(imIrWN6 Ň1 eCW*Y+b`($o3fOPCjN( |+0`pOmV2 h *W."S nbF#Zh Y Lfq_Y+Kova(8 շy1 ~Z49Ancr_h 0p-Օ r]t`5Hg_8y Ѩ R"KbP t] !xU@p<(24P I_r}9 EmyiJMڛS|5 `WӖ$׆`~S p故&3 ]R_uii^Ъ?Ku</)ҊQ2tR}Gp|q6m3H$ r9|ɠaa@KQZ!׆/Z prU 9m,zIx1 :J#F1:JN>Q?j~A[B|J:SKʤdbQS`X*=Zmӥ_w5io PʦmZ 1=:IvZo4Fڴ5[%?pBj`Bd}1PLpbhoyЩB6;pZn{媰ZyZb@m ԫ=:Gj(amU9]#jQ rPպ YC²V@KRsPdVKk19:[+0@mQ"h n &U/$I~ً8mT (BM0|eL,f p q;x"*`orOnF,֭T#j(t?[>p(a;m!۬ PEB;B] V31Y⻮A6*;}7x&.rm} O;T홺kj,G;&0e i`Zk`4tƆ,HM( jR6%zȖFyDk;\Bi d%6,¸9gGRѴ6(lH8&yRn`\e% B1b_f{_,.Wܦplä8L|Xv̻$Lf\0:5+%fdS]4Jm,`=%Ǵ[*El~ ulCȵ, )| ȏ?#(@м|Af>jjl\sʿ #I|0790KۉF|k|h ˂ ܭ )f 5$u@#txO ])}l"\ETy[[i C ]|фDVt}yz6~׀m(jv،WȠC܀؎ݞgq_-2R,X( *G=mcR ͑-چ<ר9;ڈװ=۴͂~A P2WUmI}W=ܙ=ǭ qMMYнklC׬m=]} ޏM}>^v] >^᳝ ">$^}&,.02>4*(^:<>@B7E>HJLNPG~SV~XZ\^ ^>d^f~hj9bpr>t^vo.y~|~肎{nɅ>舞芾莾)mއ^~阞q>k>n➎^ꪾr^~븞N޲>>^~^ʾξɎt^~ӞtNe>N>^>ނ~_>H_ ?n 8"?$_ln*,Ď.?4_6?2O<>c"@_FHMINP;LVX>]Z`b_\^?hj,ppr?\tz*ll|?yea4?#o?O)_/?/e ݻ_/V=}`@̆Fi!ğUUv(`31@ҟotΑȻ+bg/ y±<ӵ}㹾!h<"%|B)j.,*Qpс@| fv00őEi,,(5AFJNRVZ^bfjnrvz~Z~  29 Qh5<& 8 $j, "8ٞ~g"4!ė$ 13^ *t(Q˕R69%Ч@i L0D96u!El!5$S4| 6|ha@A\Ff{Ur[@jF؇g?-z4ҦOuZ 6"VQ7ubƙճxx-qybvkR@n0&J7+x ٌe XVf+ 2ؠB(jlȖm~l қ>!P%r 6;DGԹudPZuEjjM1o=~C1 g tg$PL[mIxp i0 A,$`9%9"Z"`f30WzX k!э"P0dGKФ6E9BXDl1*d:ybɀrl vFg{' ʨ[碻2iy8P¥s*ætU  *'DTj 17UkՋ]Q-G#Z&S'qJ+A 3+P3rGpl!G#K3]0ǰ6Gq x2~:ؖ7o#LS@*VC&FM> .4LxZ,@";`~CQs6K1aM^駣:D7l{6 \ 4 dܧb~2?m>A(wt@9 wWa@0a8GMĹGe䓷kqȹ t^Tg"0 \X' vjnZzǃj\<(HXiAwxN mn0XTD>1`ѝ G!"-`F |#h+b1ZZYS>ep,]XH0-@Ѓ-p?>l=|4!250d|z"[)o[%)KiSKūe`2 kAapq\3u;B7p%/rb~| c\5<|QրpxD>C$*2'=q& BC$jVȥ8e+U'0m@lJHɭ&5cM .杼 Nd Dv)Mkjӛvj|>O:XHD艮@p]B!H+Vs'O6D:l8@ h |oE2?+;yt0?q׿65: GuvcvV*ܨ1ZV!]'V`*lA1M)Ž-`p)F]M৷Uo:3$b@Dftҝ.u^ag3jًQF!Cz2a e"h(:;k*m=aZ8V;h흰qaPiKY4F029ȝ3aa(m$b P{ie:}8pC</w58l1@m Fq?}M-ds!3- cmw~}4c&I|vb`%3iKL~,A&C=0Q*f:C6@ET0P?k[9Z>i."|k~NܠE'/5ҷ::w}T1mM!-v@{xx o0Y: p 'Y @ 3'DMC^!C?5CxnY7=6Mҷ83@=!zN0{;W6ɹW ے^9K49BQ\Y_]`iF$)4d65h@-\ %E[R4y¡`:BUVK   @/ x]'$ /ߪ!0V, `Dɠ\Wd!I 1&` ` tM 5a:#BbuM!}X!E!lP``l'a ḭWp}Zʟ, 8P,|pNÛ,F22c32@/|-&N!J&`݉!*ڜ0t!"` 2il _2}# m҅MeJ[ OX3RdEZ$<1 dT4  d"x!#.}& l ^:D ;*If]3) 2ABCC@DEjVrd1ՠHH^?d& $?L]-ɘ,@@ZR[xSp 6 Slc&qUP'!XP]$K@Eā8vhfi~Lm Z STJp'Cw9:ŸVe %K`rFdڋ `UƼPwd*i'yĚhPiPY&`VNǗ '|f؂ZҶLǿA~) H*\ȰÇ#JHŋ3jȱǏ CIɓ(S\O<,cʜI͛8sɳϟ@ Jѣ4]Ґ箩ӧPJJ 3Vʵׯ`jm)YhӪ]˶FgݻxHsaKÈ{# #KLed̹ϠCOʜñ ȢS^ͺ,q.۸sڼ N7fnУCnCҳkν.5KOC˟O~3÷Ͽ &`PF(5ƒff v($؇-h,W(4hĸŒ8@ <iH&Iʐ)PF)!LXfjTf\)dZ WlYÙ%t&$i| %#砄"^i袌6Z"褔VJӀ 0 4@ 08zIpj&j *)5*Rºb$,Jli(:*ꪭZફ뺞/4@,F>[F*p-nP ݸYAT³ 0j,T+y m ڌ@@ 0 0 38`3ͮ.L]@ c2/d+0؊kC?3ɜP44ܚ@xsɹZr<` 13y<@"Qa*"г7me k&r-DJXoRø $W֨Z@/>xZܦMb?s쳢V[|; ?`#wz ,] `05 M~R5`\`jiVx,-~_j8u2W x%4"㬠4!ā >y`4 n ",Aș8މzxpA&h;k |Af+z7TUk!Q@>.o-%M܏p۟׫-_'⮈4h`Bp2Y$, Q4'¿`ۢ#Uf dH-dR޼ ԙ5{$fD$lJ')mw(N Ujiqћ_|8JdКhTF6>i;6@(}Dzt G(U& @T= Ir[!SGDRax3j 9n=TbTuDzj]$ئ Ͽ) } P 9cB&ȩ@VJ Ub\Q`cdH8Ū9<Pg>=`b+ȹY U(kZӎSRmYҊiӣL5pu$rg[_}&U U@vcd\^VGp Ҕgg%?κY2vR@4ДEdy >=tDRYTxS+zÊ FBwcթxV5/c+fՒulmƾ<}U"Ho["@`n(- PkΊ¤-/'ڱ }ml9ڒe-zO fvM-yE uխ/LVW-Ax9iWZ"g~KM(WA/}PS5ցa1<ufي 0Q.llYGB#Xg;,FJ]B|#z͝.jlH, # 囚@%r?<285ehy$kw Ln4Þg\5 fH3И=hVlQ+0,▹e@ļPk ]sVR97``D,9LvݎcTS7G+QuHw-&:~a)ZzW|)uRJ>ZP #Io@/ďO [SOx~>V|& { ƭ9Y*Q``풫f|-'{5@1Hn:p&pzge{v6~'܉U>$O@cf3_ pwG*j+4]^s2${SW"p37y3]|W6}Ϸ8,#hW}8Z-D]? GpK h4Ϣ{S/҄3PzA0l/PlE{b{{2{{]* |1P|SHEZK856$W8"n}0}j}}>WWGw?56@27gL8wqK8x+&aXx=yjĀI1Xu(-8c;cf;DϘW2XZ~҇Ya?J1w*0hs&g*F(ЄT8RxFQZSyw'}ׅ"҆fbdUhX,jx5Ŕs(DuHCuyXYŇV+6+Gᄈ `ȈxocUe 5d%Չ,5y>FXu֊iu5Dleb-` T3Sotf $D;H?T@5sbb`y)9^.$~u#y] ~2'UI2'#*O%MPQ/c-<bGtSY+#uc9v`HvG-SZ4.J~9;8*kx.? CF49cf(Ztc-vHO"00B^Ob9R ck8JZW,RtslVdgy^S-Cg^W=Cc *tG/Q|Zw&Ja c* [(I7`_u)١My'&9/+pfRCb磚,Sznz)c{di*|ś5Dv:I6JUǙG6n{']#sY5GVt[q99]~yS\JT22YXUH4`(ß>柊2Lj(h E kj=/oS:J:k:Շx/(,P5H5&CGYnb^)C:TbHj=J::[JKYeiʮ\Jokcfh:|cng`u1:C}6+;m@@.`h:ZOn~;穵)VFoRxätVgzzU@cr@xς*!:KڣuצKYӭ,Y0p7L~qȥTSKUO,42r]j:Ls:)pGXrb"7gKRF2;pd'PE"P/ @_M)Z(O$9-P^c-u9V"rٹ)5J)?)D?GRh~60uwu6mzCY6!S6CSBgDe2[6ժLxNCl;^{q607PYRz`bd[ˆvDDx%| w ]etʲM|qIb_'_9 GRބ ^(dADi[C'~WSkTA$-O1:HU5Do ]YV_E 5\⚨UMPX싢 yt Tp5a*R%mKeid**y |NZ$Q9=)&[v[KJWoǩW8li:L\ =*|YιxLZX5z\z*3"M2Gg$sXLv30Y Pn1,<\G?\g50z7f罋 {G2>K j[xBQ+MsELƃ6Aw kGƐM4Ǐ,l&LL\'WQ EE.}N)3'z*y͇ƓΜLpFW0Ģmi ʴz*Rn \I4]N QIv/djM ֟;uvo1qXVmmӊ7.y5z00> 6lp=A76+|;ӊ_A 0\ޙ7$2[ms7pb'>Rx^MPg@~R43Ϝkӏ2nMJH%O]+0\x觉GCEL.W筟~Cn_M@Mp\؉}*~AW2ϯj >EEES1`\(42A2&XgK~Banw|7Pt6:o(5=P+p@h34%}X,|ItcNۛY6oa8ܘn `/L2E+i4.4Jx5%/ϕ4_+C>3WsEN`fAW ꒂf_p/rkQ%:FuG$`.nVj'-CF '{O&JE/S'֓6fdĻwoWFc/QPOc m^Bל?yPtXEO2;9ꎃt;Rd0E"Q#_7"(! |@q< ͍n%`Md HIy)0AvAH)4b© ]@%h754e?`Ε53J ϸWT@X:]B8NRУ,Yj 8h #Ę0+^$n^*|\4f`(: ǁR:5).h11Q,;ETrHdˎ1ՔU@Pӎ@5eFu!ZҘ#q] s U4?>do{9(1+ )* Tn)w@Əmz:%33t5EC!K^TiwO+(%W*)}A\N[Sf3ИMN57x] 5N;3#(pOO?3  @P+ B& pw''gxd4D-Ea1LB؄W} 5XP7pI-JSܨTT$#YUlK5Y# ek8[(tՂxX^W%(!Cy؞ZQ:q^XYZf+ugL 0jK1l*呹o3&R\L̹ᜭBC x]Fx:\Ԉe4 Z.Y,6E qL K &tǾ؛@iXQ+og1+x#idya Rf'3N $B >j 5SC`X 8 FλBmB`: *eia#Ec`0r|eͅ@o94;]{S&5QPd~Bj0@, 6JIi] g7p6\*]#G38m@v̆ڌpqQxHa@nw,LІ!avc)mKyA-"KWښoIol`N+0 aZ (fi e;-@$C6ֻe&zb:.N4|Q8as 4SAՆӶn\#6>wA>!ۛxW7l p'Ⓒ-.p Sآ]$yzsׄ u*c[~T땻+w xbCr8%+D*+DxQT#XJXp](@'"`C5fDc|1 tg)@ :؂kFSUDC5%n l\jy@$3ܲ1g#Y@<#֌" s0O0t©Q}+A 4j~D&G* kC9%T~aЪTd,CJNwLF`STmQX|G`QrQS djkͤ7R&_c #)a)l Q$cU.-`N|wT+jcAO9,H@$DFv H(4J'IF MFhA@M8E5bdZKatie?Ս! /efRNx!( d^9d dOSP_@*+HyK0,VA3Z^U'ָ:աD ϶s!hm @b6XQEx]3Cm>(i@ A-FwXmc}Y/Lo&R}yCZYX(LrVKd>bRԙ 0JĄ.q]+WC-Mj\"DJYẑȮF]MxncSC26ra-M|7ejݗ1[8N.?a` *Px fsia!~Ro$A;8PRaY.'c)qEtf[\@JYH[d"߻[ZsXs.dr@:]^ᨍ Qg4`-p` 6%.6j/@)zHQWdx9ti3ܐolR0dU%}W Ԍ ̈́"7 r 9 =GX04KYK* J& G3]Oz6Ig/#u1 D5A7w:6NRWޞlPi^XEY`a(bYPAX ~\eS4ucYT/"͡RpË]Քb#@P fT,!V< s| ԝF΅߅n@DABLpLEWJ2xƬ!pcl=W]A9bN6]ҧx~AmAYR6Q " %6%FKTBV6 px =Yj[ZrW%e),.J^ee i^fp1 bc&-J [ЭHm-C[**Hn0n ;NVP„ƀ#JR_.G7B9Dp9-BaAF@Kױlj%kW5"UfLT%/N p!EeB <8\(چyT1,qG?E2Itf`1#+=);(êhz1)!'Z}ݣ6BI'aC>.f'H`i*u N沧p~L1:s?0]!bLvI}g1;ʇMAgBAb1ȱ-]`GSngqM "7/E\#$ .j2C:B&+)''CpY1,R&NfBqr5&/uH,u*ܥ0p1wM;tVuh 7@~s0Ƀ9JA3•<=C3_\[?2@{@_t^I.4pD5(p[DHX`tDGGmIwIJJKhPl%RG5+G2|ǾX.%nE>3ݝ!fȉY5DԜ'6i@E}!292J ӉtFa US!mBoI670$C| h$K eRxU/\#fʚF~PsIHEe*OAUjT0!#@Ӧ7aew9@^U#ģ^Շ~;#ؓ+ Cc{_s/`&k d|ǛEe3Ӂsz3`P_bہ& ye'SRȦȟ ș ^xF&(`40y_̈́+!{'h94:R8MRxL5"1$fκ:&ӮX2GX;(.nwJ|LP*܂܏{DZ QBO`Ｔ큮p:rN9W F3-,X5?lNqX|Ur?@oj)/g=`:7А흸s,vw w(l׵Ҩ:,C0軮*,/ɰAױob߃c:>Jw+rML;7b{Qg4òGμ-ן;_rj/&3CoA|HoR<\*Й utXGv @x gW'8! Xac)o.m5 Fr`Mj{hfCp#@E $pĨ( #hŸn!RG?r-6+V XTj̓2Q @\B zi͍_۱xpAK̅S(SBhAD?Dlt PmuK !>94&,$r m$kK43f =Pb.Ky/ s$ ,?*[/f8 un݌^4/';}Q mU{\C⭲JhW}H'ȸf@)8D}"p}\z 2_'.ȗߏ[&@N.AC^*{3A8& RՀMΫS8 .p+ٶG |)TjF;y~a qDwqLl(JqT,jq\Dk|d,ψ4qll8q(uTUӢ&ZŪW ְ՞Q5PWNJִulYMնut]|_ +{ a*Ve` Jv} KjveΊv--Z?ZӪvmmOQ+UvEakVv;qX w-0wms׈\)ԭu&qw ^iW-yϋ^M{ :ɕ}nկ w N a. /Nؗΰ? bnؙOb%N_ w1ozx bC"C}A"3%^< p%h" >.2cr!`]2á:c` %JFEJPg`A{!Bh58Go!d#r#'(oVVaR ho`* 8qi?w>+6:TZ03 ,PTAZ A@o LP_0#`C&,xs,q8DBf~ l3E߬eyڗ3ʖ >4}Q㞍@cSVKZ뮊OԁI} &pG yX=]m HiWa߁3ⱓe~tKT{\!ua hV#eIрI<=ΓZ9~u>8Ge7%gGr}qv"b};0ww't>Szgs>x# gxLxߠxvx1yGSyryyLyXyz(t p@~W}Hgz gq0{,R{-w2#fÂ÷.ŧ!&#Ḑ> X}ԗקؠ}=H.Q}/ᗀBuHDSotPEhg||k77:ACxX -h6p9$s !؂0a{82$@)bZ)n` |$g&4"سhj 7Z p|np23 ` ñP 1d203'{&C2dE {'`,8tLRsszQ81<1'axRW:#XG׍>S4o  @aeN5SX ,i֖ oQ a8BTp1 ' <{3 5(#艽Q( tz҆Q"Šx1J c{4 Fvƈ԰f4Sט b(h|30#!HhzID(f8q7(hHz$ل$ɄI6iɁ )}@ i^$Nӑ[\ P (+)(hW 6cU;WG~f;\} <8Q70VxL8ٝ s`xgZ0xoX5?F)'QW8Skв6"^ wIG7<eP 'zQ=\QB2s  )!Qp^ Zp;( 7xsBS,.A '&  &њҍ*:}9D ݠE -/ @WѣoTX0G0 1"iFa X Bࣸ !j~^&ipig)S+eF5"]++06(ٷl隦!*K{lG`|6pNkoǚh7sӧIxC 0`8a8S ҡ(觽cdZ 0G~B~ 0RG(Bi|`9f_J4^аiuH5:(d@ H:Z-Ԙl`ꯝgƗ f0`=lSx0wK ZP@ p=ǜ/3jG1M{ {g(w]J`jkf+hǙh;pnȫ @#/|ԛ17˒€; #1( =KpGwXq0iȮ,7p! i7L8{ /lZo|{Ќ|透I& Ȅ e-P<|Ƥ"`\ +!83ZP(Zį|e0ſ'p7ȀY#J!ZpQw^ƓǨ"2bIy<{,{}\ A SÇ+87\}:#:-x';LՒ2 hʡ,V C|\3Ij˲˺׼ ?}P1<+s܁ *eҼ ،Liaݼ|"cyj+k$Gϥ;Vϡ]\mec8xТ@*EX@lq*RwCWf (Is& ܁J!FS/I} P;'Ud5v ?!-R Ih3!E8[ٟv"K@1- Yuܥ 0qss VjmB%DB7q6+XE΋ \;S` ^4@;ߟЗKz!F~Hm1}J!䑰J>mRa- ]_f#pΐܷo}0TC1e^i렞˼:kZÎ.Ɏ~:Vwe#ݞo~q_^ IZiTь .*߹AC~fX_z ES(Oo20#_z%'),O-mSB:O2<7 @p'Z/3@I˜ &w| F`W`0\^A:T87^Wl5 cik0YIL Y]a]#VA# J&@eH$ҋBLg*QLLlNT 5vvvv76SL/ꀮaU/|rUC^'B-q. ^kP%ʴCԞ tݧP4.T]5 ת_I8`\FhZ{  \`Li4̐Q*@ .B\1["r$[#FOPk h!NN_}0`96 '%2.@ɮ YP)a!Ya! F _&MARDH!4 $r96^%"ꈡS_|AD4M@I]A!LEVdxb'@$Xb h`p-n^` `, ۑF W ͂Ex|! a-G(r4 Ca 0eY^ev-@U\#Fse&|"Tnz5$R( N`d" `DLMoXNa"#eq"z-u fP?,fa}'; %"H@neK!ƣ=^vҀo>fGZY5eFlB!BdΈe mj\&=€TAb΄hFc(2d%nfZpg~f::.iXjj&JrN lfږmBnNYorApv*h JrZ=t*^P~JАCz.k}+t4.bJ1(0.20x$+fX颉:Q\n纮سb 힌zZ rH2Z, H<8K%mu_!w $%1=;솁D+Pt@rt @:KY-vͣ1?Y^"{4 4D{xgѤ026Dr ϭ-EPHsij@PZrN-6,+7̰Lsnr\f3nGks8g9:%,D33s3T^ς 4N4SBqw=OMKAUtTrBF+p.dxt\ˢIJXMtqǴ&MMlNsN7WOSj>\P'PQ;)+(S1H2[af7t|~u58מu/j5+QVq55,_{ `3+;rXP~e7LSq xF{Ga _WíaPMi0]x-[)[tOMHІ:>πQ"NȎ~"R̓A 82WRu56A!W9wIa`ѯĮ#\)ZXpbj S=(p:1>sOlpp0ϏӜ gKJe,eB8qqks_% ~'JE[11\*90S;B]E&*HA |ޝȏqM'="g{sEA3ԠJUhb0lTH@af#xZ۴6uL=94/6kahi j46N% Z u/1` *"U9@HZ/N96Z9H*jC=4_7̓Ό*&)G6L6"cZ9Q4$/Zg*@zqֲ 'g80X[8"$#>ΈIG/mzQTpF fQB`MLa$cP4hTqc-*9N35*Y-3FŢ}J,ٜ:Ș@MGaoAܵr0W`,UapёPH*%`c@_w@Qj3 j.D+!110pyY4YUɕpMm ]Nu)9un-?Xwc8ab@"^3 #=p^`@S4T6(Ǔ|}N8U]RN; `"كmN@dgVA kl0< P()EFY鈠lؑ4`4 G4j76$[ RX-$U?5TҙUHC!m_(ƩhWo=\zBf`y>P !Ic}RсB%Cf;I&nUZe$7j @FE n `"opt\2r@J°4x'GD7ޮ)w( kw' pލW{>_ه33JrZFAػd1dM43@M<"d4=$wL"ILg. 0$J\`ۢB.Ze=nSxYTrDAC@="g2֥;Ӏ03, Q뙂87\w5 ܩB Ʊ% &Bpu2XP޴ y!Y¤L], x*hYax/i;$j@QFU1*F8;SŹgE;<Ӏ?9<@4-ۑWukl=Q=|\(pD'r*4Y7v=y &%$IVa%iΆ:lh.ѯ\k+юz ̐nB"cH% ދ+LgZq RQ(#JӞ*=(.)S\M-RԦp%I69uG)(QծӦ[éSt zhMZֶp\J׺Ŭ! xj׾ `KMAG *d'KZaց hGKҚMj-Yxx ]lgKͭnw[=6 pKM-&ʍtKZ=-t\&6 xK .2{|KW`o klXB'/;0% | @ΰ7{Fc?L(NqxC< *gL8,I@la1&;Pˀd%GXβ)^沘L2yžW6p6[8xγ/;yπMh.F;Z.AMJ[ҘJI0L{Ӡ7NԨNLjSհ}ָε5\k5N[zЎ f7ζZ{Mr; v,.Mzeޫ~[M\; 'NC;]7ոGNCW VgNKw/ֹχNc< iA좄~pY(>N =QuAFdA=KKgfeQr>O0L,]$!pi%u?%FImNf˕R pDk =eA!cRH@O9`b:+LAX!X"3dB" =O#GP fc |!U՚q1 W`-~w0k3P Yoqs  bG(.x)*qt@aR 5RQ$`+@=a[qsxJ~:z&HG/uG)*@$p:Nw *d$"Ѫc3aptz҅f2SQwVH19J#7߀*&KS v|ʕcEj 'Y7$ 7 pG7J굹p[)xY{LCH KjKe!b *z8c ) @ 1Ж㹐tCwr$(L) C9ۦR{ENpA4wqp'XPDuMd)J6(4IRk){;|}=E4dETp jZA NX$-H[IЊDuҤG(IgR, Ie ̹"7قȻS;v̋ Ӌ, ؋weؽH(DH` ꫩnԾ zʠ7TE{ ˣ|Syw ls:ưRp\$&(lŒ<.nC@$= >!i8iy&11EઘJOk X0]yGҀaLT"b0V/EWkp1xlq|lAɔrۋ{'<[# }ǖd\pI<ɊQpٙDɠ|}셉dʒ˾2=s$$V &+̈:vmNu-z 4[0"v> R3hĊ S}9  17}[ly] ɭԐ~JP]Ĉ-)*+c XQƯBv*}SjܽM~QNj\Q}'}hl ֭% W]}]P 4ݐg!jQoNuY&'cکKĂ C}BG|Is+v7*y Ҍp#ݍ%GeIlIE39 "cm*1~-b`$+gA)P^%U WZ[`^Јn7]>%< Kslwy>"⮌5O9o"׳$0.. ( iS2r19*ɠ#n海ѮRv+w% A,JPfNž/W7 24t ?%bnN@иTkzK؂* 'pM6?G_[yFLox\V?0P1D34* 8|0'3h^Ü_zP"P )O\HLQqٕq z#'h,g#{ϳ NQMWM+TߏV߬Z); SÜЧDBmJoO!?*Dx/к}_! Eߠ5/hog>==g咠%/˲]pЗl$&\_W 8ykJ{$z,@#ʅk|B US8#ZÆ=9{@ ĴPa400@@$p@Lf?X]q>裓^Φn 8GҖh׶ cq!8~;3.oty܍aWp_@Csf(*.s*@b@}ʅB@;s} a{8+ $%R`+OK}*h b0ܠ Z׊աhABH{|pǃPw16jؑpXkU@'IP&=[ 0S} . y џ?@S̢FTC!%!<9ٓ*׈@51 N9g{(Td9F/ 'pG%d #GB2 +@x҂S0SBPԮ1%FjㆨԆ<23talEW`%O>8E=ኴТ=/t>Qŝ5j`+8ʱv:1V2Di 8EJ2'?QPr&a OOL9%) t@H 14#*E!SX( :z*iWOʉޒhprxIQq#1рQy)O37s`-10Ku @B?n_8oɩ$jْe!geNM ~y,%$Z8x7id 6ֶ>Tk+c9Z{W qLr!&$\ ;o5DVp 0iU 0o&*4yZ@7a[_T8QfK8"@6!7W:֛̃0aB4Ql6g9ȝWCz'[tqǛNcAҔujM:]f\6Ul]t;w#i][VşwSa]n~?R²c<q&8y(\* q JBGkn<<Y=B:ыngj ~C=R:ի.uĺջ=b~?d_;=V1;Юv=z;&c< o#^tWC>ׅw@>=K={ߞ=o#_C?Uc?>U\?o~+???o_?G`!`:B)0`Zb`JKj` ?qx` Z^- ` jP  `. ` !.%a*2a RJRaTZrab zaƗavaޚa b!& "2b#"":$Rb%N$6$Z&rb'&n'(ہbib)*^ݵb,,+"-b.^Aa/c0- c11F19UZv|Ey3 s5Mۣ!*#4AA8XZ(Y O$@A,<5vaXZ-54" P) w]5B8r% 6a7n7d;D9n::5<;ģ==C>R?2? @@ EZv(0#9N@D6"E:c켙8Z6Qψg8UPtͩ!U %ޤ "Ueel%Z兰؂e%u\\RB]h[^TxfAXHab6c$aid'8gY&`lAv&~T{bfhxALD?<W^@礼[\oAEAfT@$}XD%gUO.8G;F>'%&hN[5}SdƌRS(!p'hYN'!U̇NBSҐAּ[()C(G(Gpe@DI7(!@ tL"ܖpe|n\W" 4/Hi))-(NiP7¡Ā=d€$'$}E**\Ԑ-)6iU<~¡TJ!Xpia (i"cAԛ)J& 0i* Ej/jE%,,* O!q+h p*JPjc.i~*eJ}~Z-Pƪ *U*8=-ǿ׬ԓMqF_Irhϸ}49;3I\D =OlTXWNMQ8X *,yAA+t1@P@qifhV>fA|$Y}Wfv\+(.~x,/XOHe8FlNTT,uEn+xrR%eɦɾP,TI˺,4jZZ"\qՎ\ES 0CHBT m]hB5$b rLKF^a&˂` WZbBP YN\$b``kGEsaHHh߅𰮉Z배6p O԰Tp i+JM1.1}f2-8 Olnnbd˨AklB#XM+q,2@++ (!2e(C0I82$[$C{W@b(A, 29[ 뢬^Ln;.( @,5⅂%/l. 3S.<35 DoC,Ц*Ò0D` ܅BE {|@@QB,#xX6*BC?NnTVOlL|MZh4P-.4L̲j&u oiVCHRP-*GAǓB4쪘>åЇPXi4Yvb$9@SQofo;v6Jh߀{eCA"`oa;abrJ(d7dWvNf{r6Kp܎jl?ojjMks~lUmmjn#5Nqw7 <$r m{BJ7 Puc8 w{RxAy 527w@oA8}wwS\nsbp~J>0yB8zBAuڪoobNx/KOIsx^gadIvAD<מ1ۂ"E9 ڦJU@l$fsz0/ HA]9 ֭:dfm9S (HACe2(Ým[잫g++66d·)7w:@£]:o5;OO_5$۩G(K h}zͺB¯@gzgod>3{/w<;*v3C@FtCb 0f)eJ\Ae-d#'P{0+,P'=Zl}b9h-<;Zon/ ,t+OgnPuD4};uy|/jZû|5Rv!9}=S< }}*.*;Wi/,D!]iRN* g+9=sLQ;-=W3hZ[ocԌsLejxt #œYb$Cjp L ĢL*& PgruaŢpb0M DvP  =2//6@fF5cՒ p(GWF% C@`EBGBPfUpp6 uIEٲ剆*E| gs xvR:jR #y@w@ `En "CmMJhg=Xfj\#ѤHʕ,[| 3̙4kڴRTn0I $IL,:B4T(s+nz@ܢQi% @ce) `EMR%-Mȿ;"ch7`zxy$X(E$p؆ ]`+hX9;4\_QR C!\.`QJjZ8GڵklSU}?ۿ$9z<'=@k6L $eD%^ T`U Ue"V%6$k 8 hlxsx]'`Q^KsV`6`b7dZhj7`f́h;ޑjvBk'lDqK&o{vpɵ@XpFh_ <I%HG9NhWwb &A^]z4^iniW8wie}%dX _$p&Ǚ` BlqTtRb!r]&P$,h4g? %Isvw:;ٰS`4#Ƙ"(  2% bOp8TuhCeUVS! _"b`FmԠO$`:(PBJg lQ{D[aS cP<ՐXDCtI|Z2ZZobo D&b}9C kxhP> 2I]JG^TgKSFPѰDVT\lZzFqE!$` f D:(XAz3oGdFIVl9 Ԗ|y42 (s}(8%8Ô/ 2q}JLy.ń^]8]|J@2nwa<1!G.5 l&/P۟@eʑWCG`Fb3m M+]# 7"k%;B3,PSB4y# |W{x>[( bn؆J1'MtqFA W UfSS C:h 9#!Ag{~7S X%/*]r@ׁ;-x `$;>~{,4H{k6 | 0X|^#I߸RЈqz^@K`m\j^`{eq>t)|~nzj~F@ ԎOŋipzZnNz}[9!FXI] ;o#o$~}Ҽx (T92gF@]W}4v]-jcg;0L&z#A!t 15?KR+C8UXP#7 Xp> {}4_3o'!q6FX>I" NAa1s@y7CrGEv.OQsX(.e@IЃYB L1F4~@Pm68e3s& wy.0:P|؇4='cH$ ֆ>az+pzvAb'%^8zGw|Pn. "QnWD0.sX8>Ԁ;Sw',+t2Dn@ EQr@TL#V3t(FWf\AEpoAav@3]lC{(I8-p>1[ fbHVH H<)RŁ ُA{q"qg5zfvHf('Fv=c5Hhv$&Ԩl֨؈H1 B (iJɔȌY&@o؏ٔ"{,92YIHy y yll  I VCY b@ ih( $x Sfh@%gY) ps:7_u <\28 d D^7wi*S @xJ ۨpvG4ɍ@WS^t`/TP 0~ ϩ5 "@3DF&_Kb>.z j >i)R 9i)`@V)Y).yC" 5BvY6i,)'+$sEV`΁Igқ;,џqH!Y-kEƜ^e9fo YhI]0?R5X`y-%KFa9Lukhf* P)ꨏJZiIQPu 1EC- Yu:P.+ R9Pk2Qu =Zid;J+ o72uJ:8z^Uz !J5.GB`bk_ Kf_z E1XvT6eZ +!3@OPڔj Pzy:*Wƫ<>0 P銬67:ӚoqU9S}0jEzw- *1 Z" Tx4/2gi FeP l q Pe ez8[ƐXպCvG4A E5%BE0Y.@!{ԭo>'B[pLl;t$Yᦞ%7?;X[e>{"p8J 2 ǻ𑽗&@v Zӛ pVHk P{P[8iȿLZ.p[  ,7rh{'!%l')+H$\#1,3L5l7Ll?.=? A,CIKME|N,SLUlW7GWQYT H]FnH^ugPi^4[w}l x}vq0S`^bnz@׺懎^0 +vͱ fL^ÜNG鶭@6PjuCFG.[0Ug^ڜ饛}{8>^w79.H;|uNPEU^Wxe)>LVt 8cqh_!`ne.1JIP0߮))^NoO'@@~qCܢ8K|0n/y\g!V ?4 j' sJР1JO[4%6!82  ?Y? F/1.ռcO8!/OTV)l@:qe{z n\R?=n.rtoou/Gp)  G۳/~U>8^x羅Ko;N2oNy/YWW?!C.(Q_r_Cءo\58;{ȕ"9JI? #+ۺ.1[nN2̮X#k0!' IB&;3:^7<.;>?` aA@OZCLTQCCRhi[ث-n.o/p0q1"#Zddefg((0H눫o۬Vmr;|<}=~ x@&2hR$ǀGjF4rx.,i$ʔ*Wl%L4dX#QA*DT v1:&v1Rj*֬Zrj\N5bp*9N 8qR#rHgg@3/) 8!Q^'Sl2̚7s5fl`5G5fЈoMӮ@ܺ@PLNv.n8ʗ3o>Lca_knڷÓddo= xM? 8 W >! J8!Zx!< b!!8"%fpK'"18#5"+ࡍ=#A 9$+6X$M:$QJّ\$YÒSj%]z%Tŕ/d&i&m9epuy'y!P{ :(z(e}>' "(J:)(F^Z)z)҂-z*Ꝧ :+zk+ ;*,:;6 Z{-C j-;n/ܺ-骻.an ;/.,{/o/|0‘  ;0p1k1{1!<2%|2)2-21<35|393=3A =4E}4I+4M; 2K=5UʫYk5Qb5a=v_}6iݟk6qgֶu}7*ѝ7}1{>83+8o8K>y~[~939{>x⟋>:^:ꩫ.!;DOCS/DESKTOP/vlan.gif0000755000000000000000000001066311656574604011263 0ustar GIF89a*?*?*_*_U*_*_**U****U****U****U*ߪ***U**UUUUUUUUUUU?U?UU?U?U_U_UU_U_UUUUUUUUUUUUUUUUUUUߪUUUUUUUU??U??__U__UUUUߪUUU??U??__U__UUUUߪUUU??U??__U__UԟԟUԟԟԿԿUԿԿUߪUUU??U??__U__UUUUߪU3fUUUUߪU**U****U***?*?U𠠤, H*\ȰÇ#JHŋ3jȱǏ CIѐ3raʕZL!6q@C0=J`O$*]^Z %(^ V/kU,ٰP|ziE)@ 1Ĵ߿ hd jqW1 hbƐ% `\ 8XӅO &#i^˞M`TWDVpdg|[\bAZ ]:"Wl]N6_}5bKOy]^}6ހ_!Uyu ]IulE(H$`yTW1 &y=҃NaS Ձ r+$7cH`0 S|)fe-$W#m _Qs pUyB$h浟Ox+"˦2~_^ۖ "<0ho `é{kllNgJ2CJFQfPa )UxO\ʰa t%:d]`0S֭d]HxD @]ԡM¯'4ROu5لA >dp(6PɵBAt6Ʈm k6Xgh{ᵭ!GWf^gu^ieWYN,暧˂}ItIؠ͞lrמ6Jm'|r><$WogO:Ο }R/r/ /#o_|s_'0TKwv # Ab@*C`>Mp# 23%A"-ta(C pG50?Pȑ~s`> 0Lh(ZPQDaEOըOрod#58C8)>2gxHB DT&$C:R##Iɿ<$%LyS 8kq_d񢧔E-rW@y'U2I1^N+@ /i%L@e%B+Kd.Eiiq{ .vhc g.EI%Xh\^ЩNA4Ж@h+\sx"sZCRxG lq<%jXeD%QH8W:ֱYJG?{.Q>HZѩCЇ$C>Q&cai]F^JT:ҡD\fy*ŸMMMm,Y~zQi4?jXֱhfmb/í-Hǣf\Nİ gV(&cؿNIcS.%ϡ2( l" \V!K2،M‚5y-B QWďnၘP7V֭n79c-ɴ.PY;nKIIeJQtHBcנO?561I%[H0 ί@` ωrxR;9Kʦօ+d҂*7I:6O*u<ϥʕ!묒lxŷT" bgaqUc&T:2R|XdϬy׸6Ao!6&9\]"xnW> td7zd0˸ 9%R7&5 LPK6 iK;8J z61푫 D,<dRm좗b qi[a#x.q P~/>xxכ=u]KȖKhNtڔ^4dN.xE6k9p崰YV )fׄD;ڮwg]{w*ؒkNu棧ܲES7͙/lP:8yd;1A},}D xWvl]T.ZG|)nwDaұjm[P*_о,[ⰖyOLÊI ;Oֶ; ]ѷL8NPPAy3w^,UJj 1PMQdX.% g :m7h\(cH*ߓL4M$M啈.Zx(WbZ%_Q2`O"bgz}(IbRQfR"R\vK|]6QARJeTңSaU6mW{7r%V9ar(QqfhVHz׀k=@9^rvxKw ;b/&(8؊9ItD.XȊ3Z j=SՑlQUV,Hc< IA"I$:>sePFsĈ,=|w;"WOE3dN]ZE=7GRr L铻 QxLX,fmmO֙\J%N)$NK\\P][fxX8[OH#X:1C4% Wo AS]ahQ:6yN8y8xRؗqj!qY-+7pS:5$bD\pQed%E?VW5rCeΈK=Z!sLet<4MGtU?Cfux)6:|:_HOk&$g*xBZ刡{JjfLX'b"kfg(d#ZAY'vi&9(OuV!کLQF9)^w)tfK6uPj]ezw[ӧbg@[x3av{[{};DOCS/DESKTOP/vlwin.htm0000755000000000000000000001140111711606312011454 0ustar Join a Virtual LAN under Windows OS

Virtual LANs

The term VLAN (Virtual Local Area Network) refers to a collection of devices that communicate as if they were on the same physical LAN. Any set of ports (including all ports on the switch) can be considered a VLAN. LAN segments are not restricted by the hardware that physically connects them.

VLANs offer the ability to group computers together into logical workgroups. This can simplify network administration when connecting clients to servers that are geographically dispersed across the building, campus, or enterprise network.

Typically, VLANs consist of co-workers within the same department but in different locations, groups of users running the same network protocol, or a cross-functional team working on a joint project. 

 

By using VLANs on your network, you can:

  • Improve network performance

  • Limit broadcast storms

  • Improve LAN configuration updates (adds, moves, and changes)

  • Minimize security problems

  • Ease your management task

Other Considerations

  • To set up IEEE VLAN membership (multiple VLANs), the adapter must be attached to a switch with IEEE 802.1Q VLAN capability.

  • A maximum of 64 VLANs per network port or team are supported by Intel software.

  • VLANs can co-exist with teaming (if the adapter supports both). If you do this, the team must be defined first, then you can set up your VLAN.

  • The Intel PRO/100 VE and VM Desktop Adapters and Network Connections can be used in a switch based VLAN but do not support IEEE Tagging.

  • You can set up only one untagged VLAN per adapter or team. You must have at least one tagged VLAN before you can set up an untagged VLAN.

CAUTION: When using IEEE 802 VLANs, settings must match between the switch and those adapters using the VLANs.

Microsoft* Load Balancing and Failover (LBFO) teams

Intel ANS VLANs are not compatible with Microsoft's LBFO teams. Intel® PROSet will block a member of an LBFO team from being added to an Intel ANS VLAN. You should not add a port that is already part of an Intel ANS VLAN to an LBFO team, as this may cause system instability.

 

Configuring VLANs in Microsoft* Windows*

In Microsoft* Windows*, you must use Intel® PROSet to set up and configure VLANs. For more information, select Intel PROSet in the Table of Contents (left pane) of this window.

Note: If you change a setting under the Advanced tab for one VLAN, it changes the settings for all VLANS using that port.

In most environments, a maximum of 64 VLANs per network port or team are supported by Intel PROSet.

Configuration notes for Microsoft Hyper-V*

If you want to have VLANs on the parent partition and on any child partitions, each child partition's VLAN must have the same VLAN ID as a VLAN on the parent partition.

Last modified on 6/17/09 9:47p Revision

DOCS/DESKTOP/warranty.htm0000755000000000000000000001324011651733270012176 0ustar Limited Lifetime Hardware Warranty

Limited Lifetime Hardware Warranty

Intel warrants to the original owner that the adapter product delivered in this package will be free from defects in material and workmanship. This warranty does not cover the adapter product if it is damaged in the process of being installed or improperly used.

THE ABOVE WARRANTY IS IN LIEU OF ANY OTHER WARRANTY, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF NONINFRINGEMENT OF INTELLECTUAL PROPERTY, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE.

This warranty does not cover replacement of adapter products damaged by abuse, accident, misuse, neglect, alteration, repair, disaster, improper installation, or improper testing. If the adapter product is found to be defective, Intel, at its option, will replace or repair the hardware product at no charge except as set forth below, or refund your purchase price provided that you deliver the adapter product along with a Return Material Authorization (RMA) number (see below), along with proof of purchase (if not registered), either to the dealer from whom you purchased it or to Intel with an explanation of any deficiency. If you ship the adapter product, you must assume the risk of damage or loss in transit. You must use the original container (or the equivalent) and pay the shipping charge.

Intel may replace or repair the adapter product with either new or reconditioned parts, and any adapter product, or part thereof replaced by Intel becomes Intel's property. Repaired or replaced adapter products will be returned to you at the same revision level as received or higher, at Intel's option. Intel reserves the right to replace discontinued adapter products with an equivalent current generation adapter product.

Returning a defective product

From North America:

Before returning any adapter product, contact Intel Customer Support and obtain a Return Material Authorization (RMA) number by calling +1 916-377-7000.

If the Customer Support Group verifies that the adapter product is defective, they will have the RMA department issue you an RMA number to place on the outer package of the adapter product. Intel cannot accept any product without an RMA number on the package.

All other locations:

Return the adapter product to the place of purchase for a refund or replacement.

Intel Adapter Money-back Guarantee (North America Only)

Intel wants you to be completely satisfied with the Intel adapter product that you have purchased. Any time within ninety (90) days of purchase, you may return your Intel adapter to the original place of purchase for a full refund of the purchase price from your dealer. Resellers and distributors, respectively, accepting returns and refunding money back to their customers may return Intel adapters to their original place of purchase. Intel guarantees that it will accept returns under this policy and refund the original purchase price to customers purchasing directly from Intel.

Limitation of Liability and Remedies

INTEL'S SOLE LIABILITY HEREUNDER SHALL BE LIMITED TO DIRECT, OBJECTIVELY MEASURABLE DAMAGES. IN NO EVENT SHALL INTEL HAVE ANY LIABILITY FOR ANY INDIRECT OR SPECULATIVE DAMAGES (INCLUDING, WITHOUT LIMITING THE FOREGOING, CONSEQUENTIAL, INCIDENTAL, AND SPECIAL DAMAGES) INCLUDING, BUT NOT LIMITED TO, INFRINGEMENT OF INTELLECTUAL PROPERTY, REPROCUREMENT COSTS, LOSS OF USE, BUSINESS INTERRUPTIONS, LOSS OF GOODWILL, AND LOSS OF PROFITS, WHETHER ANY SUCH DAMAGES ARISE OUT OF CONTRACT NEGLIGENCE, TORT, OR UNDER ANY WARRANTY, IRRESPECTIVE OF WHETHER INTEL HAS ADVANCE NOTICE OF THE POSSIBILITY OF ANY SUCH DAMAGES. NOTWITHSTANDING THE FOREGOING, INTEL'S TOTAL LIABILITY FOR ALL CLAIMS UNDER THIS AGREEMENT SHALL NOT EXCEED THE PRICE PAID FOR THE PRODUCT. THESE LIMITATIONS ON POTENTIAL LIABILITIES WERE AN ESSENTIAL ELEMENT IN SETTING THE PRODUCT PRICE. INTEL NEITHER ASSUMES NOR AUTHORIZES ANYONE TO ASSUME FOR IT ANY OTHER LIABILITIES.

Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations may not apply to you.

Critical Control Applications: Intel specifically disclaims liability for use of the adapter product in critical control applications (including, for example only, safety or health care control systems, nuclear energy control systems, or air or ground traffic control systems) by Licensee or Sublicensees, and such use is entirely at the user's risk. Licensee agrees to defend, indemnify, and hold Intel harmless from and against any and all claims arising out of use of the adapter product in such applications by Licensee or Sublicensees.

Software: Software provided with the adapter product is not covered under the hardware warranty described above. See the applicable software license agreement which shipped with the adapter product for details on any software warranty.

Last modified on 7/23/02 10:42a Revision

DOCS/DESKTOP/wminicdm.htm0000755000000000000000000000763511656574604012162 0ustar WMI NIC Provider

Intel® Network Adapters WMI Provider

Overview

The Intel® Network Adapters Windows Management Instrumentation (WMI) Provider enables WMI-based management applications such as Intel® PROSet for Windows Device Manager to monitor and configure the status of PCI network adapters. Intel Network Adapters WMI Provider uses WMI, a user-level instrumentation technology for the Microsoft Windows* platform.

WMI is a middleware layer that allows measurement and instrumentation information to be collected from kernel mode data providers. This information can then be provided to local or remote user-mode data consumers through the use of a common set of interfaces (Web-based Enterprise Management called WBEM). WMI is a data-independent pipeline between the data consumer and the data provider that makes no assumptions about the format of the data.

A guide is available on this distribution, which contains detailed information on the Intel Network Adapters WMI Provider, also referred to as Network Configuration Services (NCS2) WMI Providers. This guide is located in \APPS\WMI\DOCS. The technical reference paper describes the external view of NCS2 WMI providers so WMI-based management applications could use it to manage the network configuration for the Intel adapters.

System Requirements

  • Any Intel® PRO/100, Intel® Gigabit Network Adapter, or Intel® 10GbE Network Adapter

  • related driver software

  • a supported Microsoft* Windows* operating system. Please refer to the System Requirements page for a list of supported operating systems.

The Intel Network Adapters WMI Provider supports all Intel PRO/100, Gigabit, and 10GbE network adapters.

Installation

The Intel Network Adapters WMI Provider are installed as part of Intel® PROSet for Windows Device Manager software installation. See the Installing Intel PROSet for Windows Device Manager section for more information on how to install Intel PROSet for Windows Device Manager.

Intel PROSet for Windows Device Manager Typical Setup Type registers the Intel Network Adapters WMI Provider into the root\IntelNCS2 namespace.

Supported Standards

The Intel Network Adapters WMI Provider supports the standards based CIM 2.6 specification.

Known Issues

DMI-SNMP Instrumentation

This Intel Network Adapters WMI Provider cannot jointly operate with the Intel® DMI-SNMP instrumentation.

Missing Instances under Microsoft Windows Vista*

You must elevate (i.e., embed a manifest file) in your application in order to access all of the Intel WMI classes.

Last modified on 6/05/09 11:26a Revision DOCS/DOS-ODI0000755000000000000000000000000011761422163007456 5ustar DOCS/DOS-ODI/dostrb.htm0000755000000000000000000000206310307752542011552 0ustar DOS Troubleshooting

DOS Troubleshooting

  • Make sure youre using the correct and most recent drivers for this adapter.

  • If youre replacing an existing adapter, make sure the LINK statement in your NET.CFG is correct for the new adapter.

  • Verify that the frame type in your NET.CFG file matches your network.

  • Test the adapter by running the DIAGS.EXE diagnostics program. Additional testing is
    available by using a responder.

Last modified on 9/08/05 7:08a Revision 5

DOCS/DOS-ODI/driv_dos.htm0000755000000000000000000005653710741632766012114 0ustar Installing Intel Network Drivers for DOS

Intel Network Drivers for DOS

DOS Driver

The NDIS2 (DOS) driver is provided solely for the purpose of loading other operating systems -- for example, during RIS or unattended installations. It is not intended as a high-performance driver.

You can find adapter drivers, PROTOCOL.INI files, and NET.CFG files in the PRO100\DOS or PRO1000\DOS directory on the Product CD or download folder. For additional unattended install information, see the text files in the operating system subdirectories under the APPS\SETUP\PUSH directory.

Automatic or Explicit Configuration of a Single NIC or Multiple NICs

When the driver finds that only one adapter is installed in the system, it will use that adapter regardless of whether or not parameters in PROTOCOL.INI are present or correct. If the parameters do not match the actual configuration, the driver will display warning messages indicating that the parameter was not used.

One instance of the driver must be loaded for each adapter that is activated. When multiple adapters are installed, the SLOT parameter becomes advisable but not required.

The determination as to which adapter each driver will control should be made by the user based on the protocol stack(s) bound to each driver, and based on the network that is connected to each adapter. The BINDINGS list in each protocol stacks PROTOCOL.INI section establishes the relationship between protocol stacks and drivers. The SLOT parameter in the drivers PROTOCOL.INI section establishes the relationship between drivers and adapters, and a value can be provided for each driver loaded. If a SLOT parameter is not specified, the first driver instance will load on the first NIC/Port found in the scanning list, the second driver instance will load on the second NIC/Port found in the scanning list, etc. When the driver detects multiple NICs/Ports it will report all of the possible slots. The only way for the driver to know which driver instance is being loaded is to use the DRIVERNAME parameter instance number. Therefore, it is essential that the DRIVERNAME parameter instance syntax defined below be used correctly.

The adapters are automatically configured by the PCI system BIOS when the system boots. The driver queries the PCI BIOS and obtains all of the adapters configuration information. BIOS scanning using mechanisms 1 and 2, as defined in the PCI BIOS specification, are supported. The SLOT number is actually the encoded value of the PCI adapters device location, which is defined as shown below. The SLOT value reported by the driver and entered by the user is the value of bits 0 through 15. In versions of the driver prior to 2.01, the SLOT value reported by the driver and entered by the user was shifted right by 3 bits (divided by 8) so that SLOT 0x0088 was actually entered into PROTOCOL.INI as 0x0011. This doesnt allow for multi-function devices to be specified with this SLOT parameter. So starting with v2.01, the driver does not shift the input parameter by 3 bits and SLOT 0x0088 would be entered as 0x0088. This also allows for specifying slot 0x0081 = Bus 0 Device 16 Function 1. If the driver finds that the entered SLOT number is not found in its slot list table, it may be because the SLOT uses the older convention (shifted right). The driver then tries to match this old style slot parameter to a slot in the slot list and loads on that slot if it finds a match. This is done for backward compatibility. 

Configuring with the PROTOCOL.INI File

The configuration parameters listed below are supported through the PROTOCOL.INI file. When the machine has a single adapter, all the parameters (except DRIVERNAME) are optional; when the machine has multiple adapters, some of the parameters are required.

DRIVERNAME

This is the only parameter required for all configurations. This parameter is essentially an "instance ID". Each instance of the driver must create a unique instance name, both to satisfy DOS driver requirements, and to make it possible to find the parameters for the instance in the PROTOCOL.INI file.

When the driver initializes, it tries to find previously loaded instances of itself. If none are found, the driver calls itself "E1000$", and looks for that name in the PROTOCOL.INI file to find its parameters. If one or more instances are found, the driver calls itself "E100x$", where 'x' is one more than the value used by the most recently loaded instance. So, in this scenario, the second driver calls itself "E1002$", the third calls itself "E1003$", and so on; there is no driver called "E1001$". Up to 10 drivers can be loaded in a single system in this way. 

Syntax:

DRIVERNAME = [E1000$ | E1002$ | etc.]

Example:

DRIVERNAME = E1000$

Default:

None, this is a required parameter.

Normal Behavior:

The driver finds its section in PROTOCOL.INI by matching its instance ID to the value for this parameter.

Possible Errors:

The device driver uses a DOS function to display the name of the driver it is expecting. This function cannot display a '$' character. For this reason, the user may see a message referring to this value without the '$'; the user must remember to enter the '$' character as part of the parameter's value.

SPEEDDUPLEX

The parameter disables Auto-Speed-Detect and causes the adapter to function at the speed indicated. Do not include this parameter if you want your Gigabit adapter to connect at 1000Mbps.

Syntax:

SPEEDDUPLEX = [0 | 1 | 2 | 3]

Example:

SPEEDDUPLEX = 2

Default:

Parameter not included in PROTOCOL.INI

Normal Behavior:

0 = 10Mbps half duplex
1 = 10Mbps full duplex
2 = 100Mbps half duplex
3 = 100Mbps full duplex

Possible Errors:

If the SPEEDDUPLEX parameter is set to an invalid value:

  • The parameter is ignored and the default (Auto-Speed-Detect) is used
  • A message indicates a "Parameter value out of range" error

SLOT

This parameter makes it possible for the driver to uniquely identify which of the adapters is to be controlled by the driver. The parameter can be entered in hexadecimal or decimal.

Syntax:

 SLOT = [0x0..0x1FFF]

SLOT = [0..8191]

Examples:

SLOT = 0x1C

SLOT = 28

Default:

The driver will Auto-Configure if possible.

Normal Behavior:

The driver uses the value of the parameter to decide which adapter to control.

Possible Errors:

If only one adapter is installed, and the value does not correctly indicate the adapter slot:

  • A message indicates that the value does not match the actual configuration
  • The driver finds the adapter and uses it

If more than one adapter is installed, and the value does not correctly indicate an adapter slot:

  • A message indicates possible slots to use
  • The driver loads on the next available slot

NODE

This parameter sets the Individual Address of the adapter, overriding the value read from the EEPROM.

Syntax:

NODE = "12 hexadecimal digits"

The value must be exactly 12 hexadecimal digits, enclosed in double quotes. 

The value can not be all zeros.

The value can not have the Multicast bit set (LSB of 2nd digit = 1).

Example:

NODE = 00AA00123456

Default:

Value from EEPROM installed on adapter

Normal Behavior:

The Current Station Address in the NDIS MAC Service-Specific Characteristics (MSSC) table is assigned the value of this parameter. The adapter hardware is programmed to receive frames with the destination address equal to the Current Station Address in the MSSC table. The Permanent Station Address in the MSSC table will be set to reflect the node address read from the adapter's EEPROM.

Possible Errors:

If any of the rules described above are violated, the driver treats this as a fatal error and an error message occurs, indicating the correct rules for forming a proper address.

ADVERTISE

This parameter can be used to restrict the speeds and duplexes advertised to a link partner during auto-negotiation. If AutoNeg = 1, this value is used to determine what speed and duplex combinations are advertised to the link partner. This field is treated as a bit mask.

Syntax:

ADVERTISE = [ 1 | 2 | 4 | 8 | 0x20 | 0x2F]:

0x01 = 10 Half, 0x02 = 10 Full, 0x04 = 100 Half, 0x08 = 100 Full, 0x20 = 1000 Full, 0x2F = all rates

Example:

ADVERTISE = 1

Default:

0x2F (all rates are supported)

Normal Behavior:

By default all speed/duplex combinations are advertised.

Possible Errors:

An error message is displayed if the value given is out of range.

FLOWCONTROL

This parameter, which refers to IEEE 802.3x flow control, helps prevent packets from being dropped and can improve overall network performance. Specifically, the parameter determines what flow control capabilities the adapter advertises to its link partner when auto negotiation occurs. This setting does NOT force flow control to be used. It only affects the advertised capabilities.

NOTES:

  • Due to errata in the 82542 silicon, the chip is not able to receive PAUSE frames if the ReportTxEarly parameter is set to 1. Thus, if ReportTxEarly =1 and the driver is running on an adapter using this silicon (such as the PWLA8490), the driver will modify the FlowControl parameter to disable the ability to receive PAUSE frames.

  • If half-duplex is forced or auto-negotiated, the driver will completely disable flow control.

Syntax:

FLOWCONTROL = [ 0 | 1 | 2 | 3 |0xFF]

Example:

FLOWCONTROL = 1

Default:

3

Normal Behavior:

0 = Disabled (No flow control capability)

1 = Receive Pause Frames (can receive and respond to PAUSE frames)

2 = Transmit Pause Frames (can send PAUSE frames)

3 = Both Enabled (can send and receive PAUSE frames)

0xFF = Hardware Default.

Possible Errors:

An error message is displayed if the value given is out of range.

USELASTSLOT

This parameter causes the driver to load on the device in the last slot found in the slot scan. The default behavior of the driver is to load on the first adapter found in the slot scan. This parameter forces the driver to load on the last one found instead.

Syntax:

UseLastSlot = [ 0 | any other value ]

Example:

USELASTSLOT = 1

Default:

0

Normal Behavior:

0 = Disabled, any other value = Enabled

Possible Errors:

None

TXLOOPCOUNT

This parameter controls the number of times the transmit routine loops while waiting for a free transmit buffer. This parameter can affect Transmit performance. 

Syntax:

TXLOOPCOUNT = <32-bit value>

Example:

TXLOOPCOUNT = 10000

Default:

1000

Normal Behavior:

Default

Possible Errors:

None

DOS ODI Client Driver

This driver is provided solely for the purpose of loading an OS. It is not intended as a high-performance driver. Please limit use to 1-2 frame types.

Location of Drivers: 
 10/100 Mbit: \PRO100\DOS\E100BODI.COM 
 Gigabit: \PRO1000\DOS\E1000ODI.COM (This directory also contains the PROTOCOL.INI file and NET.CFG file for gigabit adapters.)

NOTES:

  • If the connection fails, set the Spanning Tree Protocol (STP) option on the switch to "off".

  • Novell no longer supports NETX.EXE or the VLM client software. However, as a convenience to Intel customers, a copy of NETX.EXE is provided on the Intel Configuration and Drivers CD. Intel recommends that you use the latest Novell Client32 software.

  • With dual-port adapters, the first port must be used before the second port.

NETX General Installation 

  1. Copy the following files from the PRO100\DOS or PRO1000\DOS directory of the Intel media to the NWCLIENT directory on the hard drive:

    • LSL.COM

    • E100BODI.COM (10/100 Mbit) or E1000ODI.COM (gigabit)

    • IPXODI.COM

    • NETX.EXE

  2. Configure AUTOEXEC.BAT and NET.CFG based on the sample files below. NET.CFG should be in the same directory as the driver.

  3. Reboot and the client should connect to the server.

VLM Installation

This version of E100BODI.COM requires latest version of the VLM client (version 1.21 or greater).

Refer to the Novell NetWare documentation for complete installation instructions.

TIPS (DOS ODI)

NETX

  • In CONFIG.SYS add LASTDRIVE=E.

  • In NET.CFG add FIRST NETWORK DRIVE F (or some drive letter after the range of physical devices you've installed) under the NetWare DOS REQUESTER section (indented).

VLM

  • In CONFIG.SYS add LASTDRIVE=Z.

  • In NET.CFG, add FIRST NETWORK DRIVE F under the NetWare DOS REQUESTER section (indented). If F is already assigned, select a drive letter after the range of physical devices you have installed.

  • Promiscuous mode support is not supported since ASM does not include a receive monitor stack. If needed, load RXMONSTK.COM (from the VLM client kit) after LSL.COM and before E100BODI.COM or E1000ODI.COM.

  • This version of E100BODI.COM or E1000ODI.COM requires VLM client version 1.21 or higher. Attempting to use an older version of the VLM client may cause connection problems, slow response or computer system lock-ups.

10/100 Mbit Sample Files

AUTOEXEC.BAT: 

CD\NWCLIENT
LSL
E100BODI
IPXODI
NETX (or VLM optional for NetWare 3.12 or higher)

NET.CFG: 

Link Support
Buffers 8 1514
MemPool 8192
Max Boards 4
Max Stacks 4

Link Driver e100bodi
slot A01
; int 5
frame ethernet_ii
frame ethernet_802.2
protocol IPX 8137 ethernet_ii
protocol IPX e0 ethernet_802.2

Netware Dos Requester
First Network Drive=f
NETWARE PROTOCOL BIND NDS
file cache level=0
; preferred server=190.21.20.62
; preferred server= noestb3-6450

Protocol TCPIP
IP_ADDRESS 190.20.20.201
IP_NETMASK 255.255.0.0
IP_ROUTER 0.0.0.0
tcp_window 598
tcp_sockets 32
BIND e1000odi

Protocol IPX
IPX SOCKETS 60
bind 2

Gigabit Sample Files

AUTOEXEC.BAT: 

CD\NWCLIENT
LSL
E1000ODI
IPXODI
NETX (or VLM optional for NetWare 3.12 or higher)

NET.CFG: 

Link Support
Buffers 8 1514
MemPool 8192
Max Boards 4
Max Stacks 4

Link Driver e1000odi
slot A01
; int 5
frame ethernet_ii
frame ethernet_802.2
protocol IPX 8137 ethernet_ii
protocol IPX e0 ethernet_802.2

Netware Dos Requester
First Network Drive=f
NETWARE PROTOCOL BIND NDS
file cache level=0
; preferred server=190.21.20.62
; preferred server= noestb3-6450

Protocol TCPIP
IP_ADDRESS 190.20.20.201
IP_NETMASK 255.255.0.0
IP_ROUTER 0.0.0.0
tcp_window 598
tcp_sockets 32
BIND e1000odi

Protocol IPX
IPX SOCKETS 60
bind 2
NOTE:  SPEEDDUPLEX parameter: 0=10Mbps half-duplex; 1=10Mbps full-duplex; 2=100Mbps half-duplex; 3=100Mbps full-duplex. The SPEEDDUPLEX keyword is only needed when you are forcing the card to a lower speed and duplex.The link partner must also be forced to the same setting. Do not use the SPEEDDUPLEX keyword if you want to use 1000Mbps.

Last modified on 1/11/08 10:25a Revision 10

DOCS/DOS-ODI/note.gif0000755000000000000000000000073207732316600011177 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/DOS-ODI/style.css0000755000000000000000000000431710415221214011404 0ustar BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/LINUX0000755000000000000000000000000011761422163007317 5ustar DOCS/LINUX/box.gif0000755000000000000000000000074711651733270010672 0ustar GIF89aM3!,MI8ͻ`(dihlp,tmx|pH,$J8ШtJZجvz zn|NnB. LJ+^̸ǐ#KL˘3k̹ϠC;DOCS/LINUX/caution.gif0000755000000000000000000000130411651733270011532 0ustar GIF89a)!19)!k91J9RZBRBJcRJB{fJcsZRRckJRfZJJ{{{{{s{{ksss{sJfffZZZRRRJJJJJ9BBB333)))!!!!,(,,00 -( 40 4(0 6($99 'A/ COO; 74 ͣB0  @7.C)!5.=ҏ# %"p8JB@1xJdbT`$cG(0c R`pP#B@̜=T`#IAT@!Nm; (QƄ:J05 (;98FCG fC >xA['!0!`> BH"F$D\N4yB$;DOCS/LINUX/e1000.htm0000755000000000000000000042655211736252616010664 0ustar Linux Driver for Intel® Gigabit Network Connections

Linux* Base Drivers for Intel Ethernet Network Connection

NOTE: This release includes four Linux* Base Drivers for Intel® Ethernet Network Connection. These drivers are named igb,  e1000, e1000e and igbvf.
  • igb driver supports all 82575, 82576 and 82580-based gigabit network connections.
  • The igbvf driver supports 82576-based virtual function devices that can only be activated on kernels that support SR-IOV. SR-IOV requires the correct platform and OS support.
  • e1000 driver supports all PCI and PCI-X gigabit network connections.
  • e1000e driver supports all PCI Express gigabit network connections, except those that are 82580, 82575 and 82576-based.

NOTE: The Intel(R) PRO/1000 P Dual Port Server Adapter is supported by the e1000 driver, not the e1000e due to the 82546 part being used behind a PCI Express bridge.

First identify your adapter.  Then follow the appropriate steps for building, installing, and configuring the driver.

UPGRADING: If you currently have the e1000 driver installed and need to install e1000e, perform the following:

  • If your version of e1000 is 7.6.15.5 or less, upgrade to e1000 version 8.x, using the instructions in the e1000 section.
  • Install the e1000e driver using the instructions in the e1000e section.
  • Modify /etc/modprobe.conf to point your PCIe devices to use the new e1000e driver using alias ethX e1000e, or use your distribution's specific method for configuring network adapters like RedHat's setup/system-config-network
    or SuSE's yast2.

Identifying Your Adapter

First identify your adapter.  Then select the name of the specified base driver: igb, e1000 or e1000e.

For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at:

http://support.intel.com/support/go/network/adapter/idguide.htm

For the latest Intel network drivers for Linux, refer to the following website. Select the link for your adapter.  

http://support.intel.com/support/go/network/adapter/home.htm

Using the igb Base Driver

Overview

Building and Installation

Command Line Parameters

Additional Configurations

Known Issues

Overview

The Linux base drivers support the 2.4.x and 2.6.x kernels. These drivers includes support for Itanium® 2-based systems.

These drivers are only supported as a loadable module. Intel is not supplying patches against the kernel source to allow for static linking of the drivers. For questions related to hardware requirements, refer to the documentation supplied with your Intel Gigabit adapter. All hardware requirements listed apply to use with Linux.

The following features are now available in supported kernels:

  • Native VLANs

  • Channel Bonding (teaming)

  • SNMP

Channel Bonding documentation can be found in the Linux kernel source: /documentation/networking/bonding.txt

The igb driver supports IEEE 1588 time stamping for kernels 2.6.30 and above.

The driver information previously displayed in the /proc file system is not supported in this release. Alternatively, you can use ethtool (version 1.6 or later), lspci, and ifconfig to obtain the same information. Instructions on updating ethtool can be found in the section Additional Configurations later in this document.

Building and Installation

To build a binary RPM* package of this driver, run 'rpmbuild -tb igb.tar.gz'.

NOTES:

  • For the build to work properly, the currently running kernel MUST match the version and configuration of the installed kernel sources. If you have just recompiled the kernel reboot the system now.

  • RPM functionality has only been tested in Red Hat distributions.

  1. Move the base driver tar file to the directory of your choice. For example, use '/home/username/igb' or '/usr/local/src/igb'.

  2. Untar/unzip the archive, where <x.x.x> is the version number for the driver tar file:

    tar zxf igb-<x.x.x>.tar.gz

  3. Change to the driver src directory, where <x.x.x> is the version number for the driver tar:

    cd igb-<x.x.x>/src/

  4. Compile the driver module:

    # make install

    The binary will be installed as:

    /lib/modules/<KERNEL VERSION>/kernel/drivers/net/igb/igb.[k]o

    The install location listed above is the default location. This may differ for various Linux distributions.

  5. Load the module using either the insmod or modprobe command:

    modprobe igb

    insmod igb

    Note that for 2.6 kernels the insmod command can be used if the full path to the driver module is specified. For example:

        insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/igb/igb.ko

    With 2.6 based kernels also make sure that older igb drivers are removed from the kernel, before loading the new module:

    rmmod igb; modprobe igb

  6. Assign an IP address to the interface by entering the following, where <x> is the interface number:

    ifconfig eth<x> <IP_address>

  7. Verify that the interface works. Enter the following, where <IP_address> is the IP address for another machine on the same subnet as the interface that is being tested:

    ping <IP_address>

TROUBLESHOOTING: Some systems have trouble supporting MSI and/or MSI-X interrupts. If you believe your system needs to disable this style of interrupt, the driver can be built and installed with the command:

# make CFLAGS_EXTRA=-DDISABLE_PCI_MSI install

Normally the driver will generate an interrupt every two seconds, so if you can see that you're no longer getting interrupts in cat /proc/interrupts for the ethX igb device, then this workaround may be necessary.

To build igb driver with DCA:

If your kernel supports DCA, the driver will build by default with DCA enabled.

Command Line Parameters

If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:

modprobe igb [<option>=<VAL1>,<VAL2>,...]

For example, with two Gigabit PCI adapters, entering:

modprobe igb TxDescriptors=80,128

loads the igb driver with 80 TX descriptors for the first adapter and 128 TX descriptors for the second adapter.

The default value for each parameter is generally the recommended setting, unless otherwise noted.

NOTES:

  • For more information about the AutoNeg, Duplex, and Speed parameters, see the Speed and Duplex Configuration section in this document.

  • For more information about the InterruptThrottleRate, RxIntDelay, TxIntDelay, RxAbsIntDelay, and TxAbsIntDelay parameters, see the application note at: http://www.intel.com/design/network/applnots/ap450.htm.

  • A descriptor describes a data buffer and attributes related to the data buffer. This information is accessed by the hardware.

Parameter Name Valid Range/Settings Default Description
InterruptThrottleRate
Valid Range: 0,1,3,100-100000 (0=off, 1=dynamic, 3=dynamic conservative)
 		 3 The driver can limit the amount of interrupts per second that the adapter will generate for incoming packets. It does this by writing a value to the adapter that is based on the maximum amount of interrupts that the adapter will generate per second.

Setting InterruptThrottleRate to a value greater or equal to 100 will program the adapter to send out a maximum of that many interrupts per second, even if more packets have come in. This reduces interrupt load on the system and can lower CPU utilization under heavy load, but will increase latency as packets are not processed as quickly.

The default behaviour of the driver previously assumed a static InterruptThrottleRate value of 8000, providing a good fallback value for all traffic types, but lacking in small packet performance and latency. The hardware can handle many more small packets per second however, and for this reason an adaptive interrupt moderation algorithm was implemented.

The driver has two adaptive modes (setting 1 or 3) in which it dynamically adjusts the InterruptThrottleRate value based on the traffic that it receives. After determining the type of incoming traffic in the last timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that traffic.

The algorithm classifies the incoming traffic every interval into classes. Once the class is determined, the InterruptThrottleRate value is adjusted to suit that traffic type the best. There are three classes defined: "Bulk traffic", for large amounts of packets of normal size; "Low latency", for small amounts of traffic and/or a significant percentage of small packets; and "Lowest latency", for almost completely small packets or minimal traffic.

In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low latency" or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This default mode is suitable for most applications.

For situations where low latency is vital such as cluster or grid computing, the algorithm can reduce latency even more when InterruptThrottleRate is set to mode 1. In this mode, which operates the same as mode 3, the InterruptThrottleRate will be increased stepwise to 70000 for traffic in class "Lowest latency".

Setting InterruptThrottleRate to 0 turns off any interrupt moderation and may improve small packet latency, but is generally not suitable for bulk throughput traffic

NOTE: InterruptThrottleRate takes precedence over the TxAbsIntDelay and RxAbsIntDelay parameters. In other words, minimizing the receive and/or transmit absolute delays does not force the controller to generate more interrupts than what the Interrupt Throttle Rate allows.
LLIPort 0-65535
 		 0 (disabled) LLI (Low Latency Interrupts): LLI allows for immediate generation of an interrupt upon processing receive packets that match certain criteria as set by the parameters described below. LLI parameters are not enabled when Legacy interrupts are used. You must be using MSI or MSI-X (see cat /proc/interrupts) to successfully use LLI.

LLI is configured with the LLIPort command-line parameter, which specifies which TCP port should generate Low Latency Interrupts.

For example, using LLIPort=80 would cause the board to generate an immediate interrupt upon receipt of any packet sent to TCP port 80 on the local machine.

CAUTION: Enabling LLI can result in an excessive number of interrupts/second that may cause problems with the system and in some cases may cause a kernel panic.

LLIPush 0-1
 		 0 (disabled)
 		 LLIPush can be set to be enabled or disabled (default). It is most effective in an environment with many small transactions.
NOTE: Enabling LLIPush may allow a denial of service attack.
LLISize 0-1500 0 (disabled) LLISize causes an immediate interrupt if the board receives a packet smaller than the specified size.
 
IntMode
 		 0-2 (0 = Legacy Int, 1 = MSI and 2 = MSI-X) 2 IntMode controls allow load time control over the type of interrupt registered for by the driver. MSI-X is required for multiple queue support, and some kernels and combinations of kernel .config options will force a lower level of interrupt support. 'cat /proc/interrupts' will show different values for each type of interrupt.
RSS 0-8 1 0 - Assign up to whichever is less, number of CPUS or number of queues
X - Assign X queues where X is less than the maximum number of queues

NOTE: for 82575-based adapters the maximum number of queues is 4; for  82576-based and newer adapters it is 8.

This parameter is also affected by the VMDq parameter in that it will limit the queues more.

VMDQ
Model 0 1 2 3+
82575 4 4 3 1
82576 8 2 2 2
82580 8 1 1 1
VMDQ 0 - 4 on 82575-based adapters; and 0 - 8 for 82576/82580-based adapters.

0 = disabled
1 = sets the netdev as pool 0
2+ = add additional queues but they currently are not used.		 0 Supports enabling VMDq pools as this is needed to support SR-IOV.

This parameter is forced to 1 or more if the max_vfs module parameter is used.  In addition the number of queues available for RSS is limited if this is set to 1 or greater.
max_vfs 0-7

If the value is greater than 0 it will also force the VMDq parameter to be 1 or more.		 0

This parameter adds support for SR-IOV. It causes the driver to spawn up to max_vfs worth of virtual function.
QueuePairs 0-1 1 (TX and RX will be paired onto one interrupt vector) If set to 0, when MSI-X is enabled, the TX and RX will attempt to occupy separate vectors.

This option can be overridden to 1 if there are not sufficient interrupts available. This can occur if any combination of RSS, VMDQ, and max_vfs  results in more than 4 queues being used.
Node 0-n

0 - n: where n is the number of the NUMA node that should be used to allocate memory for this adapter port.

-1: uses the driver default of allocating memory on whichever processor is running insmod/modprobe.

-1 (off) The Node parameter will allow you to pick which NUMA node you want to have   the adapter allocate memory from.  All driver structures, in-memory queues, and receive buffers will be allocated on the node specified.  This parameter is only useful when interrupt affinity is specified, otherwise some portion of the time the interrupt could run on a different core than the memory is allocated on, causing slower memory access and impacting throughput, CPU, or both. 
EEE 0-1 1 (enabled)

A link between two EEE-compliant devices will result in periodic bursts of data followed by periods where the link is in an idle state. This Low Power Idle (LPI) state is supported in both 1Gbps and 100Mbps link speeds.

NOTE: EEE support requires autonegotiation.
DMAC 0, 250, 500, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000. 0 (disabled)

Enables or disables DMA Coalescing feature. Values are in usecs and increase the internal DMA Coalescing features internal timer. DMA (Direct Memory Access) allows the network device to move packet data directly to the system's memory, reducing CPU utilization. However, the frequency and random intervals at which packets arrive do not allow the system to enter a lower power state. DMA Coalescing allows the adapter to collect packets before it initiates a DMA event. This may increase network latency but also increases the chances that the system will enter a lower power state.

Turning on DMA Coalescing may save energy with kernel 2.6.32 and later. This will impart the greatest chance for your system to consume less power. DMA Coalescing is effective in helping potentially saving the platform power only when it is enabled across all active ports.

InterruptThrottleRate (ITR) should be set to dynamic. When ITR=0, DMA Coalescing is automatically disabled.

A whitepaper containing information on how to best configure your platform is available on the Intel website.
MDD (Malicious Driver Detection) Valid Range: 0, 1; 0 = Disable, 1 = Enable Default Value: 1 This parameter is only relevant for I350 devices operating in SR-IOV mode. When this parameter is set, the driver detects malicious VF driver and disables its TX/RX queues until a VF driver reset occurs.

Additional Configurations

Configuring the Driver on Different Distributions

Configuring a network driver to load properly when the system is started is distribution dependent. Typically, the configuration process involves adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other system startup scripts and/or configuration files. Many popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, refer to your distribution documentation. If during this process you are asked for the driver or module name, the name for the Linux Base Driver for the Gigabit family of adapters is e1000.

As an example, if you install the igb driver for two Gigabit adapters (eth0 and eth1) and want to set the interrupt mode to MSI-X and MSI respectively, add the following to modules.conf or /etc/modprobe.conf:

alias eth0 igb
alias eth1 igb
options igb IntMode=2,1

Viewing Link Messages

Link messages will not be displayed to the console if the distribution is restricting system messages. In order to see network driver link messages on your console, set dmesg to eight by entering the following:

dmesg -n 8
NOTE: This setting is not saved across reboots.

Jumbo Frames

Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU) to a value larger than the default value of 1500. Use the ifconfig command to increase the MTU size. For example:

ifconfig eth<x> mtu 9000 up

This setting is not saved across reboots. The setting change can be made permanent by adding MTU=9000 to the file: /etc/sysconfig/network-scripts/ifcfg-eth<x> (Red Hat distributions). Other distributions may store this setting in a different location.

NOTES:

  • To enable Jumbo Frames, increase the MTU size on the interface beyond 1500.

  • The maximum MTU setting for Jumbo Frames is 9216. This value coincides with the maximum Jumbo Frames size of 9234.

  • Using Jumbo frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.

ethtool

The driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information. ethtool version 3 or later is required for this functionality, although we strongly recommend downloading the latest version at:

http://ftp.kernel.org/pub/software/network/ethtool/.

Speed and Duplex Configuration

Speed and Duplex are configured through the ethtool* utility. ethtool is included with all versions of Red Hat after Red Hat 7.2. For other Linux distributions, download and install ethtool from the following website: http://ftp.kernel.org/pub/software/network/ethtool/.

Enabling Wake on LAN* (WoL)

WoL is configured through the ethtool* utility. ethtool is included with all versions of Red Hat after Red Hat 7.2. For other Linux distributions, download and install ethtool from the following website: http://ftp.kernel.org/pub/software/network/ethtool/.

For instructions on enabling WoL with ethtool, refer to the website listed above.

WoL will be enabled on the system during the next shut down or reboot. For this driver version, in order to enable WoL, the e1000 driver must be loaded prior to shutting down or suspending the system.

NOTES: Wake On LAN is only supported on port A of multi-port devices.

Wake On LAN is not supported for the Intel® Gigabit VT Quad Port Server Adapter.

Multiqueue

In this mode, a separate MSI-X vector is allocated for each queue and one for "other" interrupts such as link status change and errors. All interrupts are throttled via interrupt moderation. Interrupt moderation must be used to avoid interrupt storms while the driver is processing one interrupt. The moderation value should be at least as large as the expected time for the driver to process an interrupt. Multiqueue is off by default.

Requirements: MSI-X support is required for Multiqueue. If MSI-X is not found, the system will fallback to MSI or to Legacy interrupts. This driver supports multiqueue in kernel versions 2.6.24 and greater. This driver supports receive multiqueue on all kernels that support MSI-X.

NOTES: Do not use MSI-X with the 2.6.19 or 2.6.20 kernels.

On some kernels a reboot is required to switch between a single queue mode and multiqueue modes, or vice-versa.

LRO

Large Receive Offload (LRO) is a technique for increasing inbound throughput of high-bandwidth network connections by reducing CPU overhead. It works by aggregating multiple incoming packets from a single stream into a larger buffer before they are passed higher up the networking stack, thus reducing the number of packets that have to be processed. LRO combines multiple Ethernet frames into a single receive in the stack, thereby potentially decreasing CPU utilization for receives.

NOTE: LRO requires 2.4.22 or later kernel version.

IGB_LRO is a compile time flag. The user can enable it at compile time to add support for LRO from the driver. The flag is used by adding CFLAGS_EXTRA="-DIGB_LRO" to the make file when it's being compiled.

    # make CFLAGS_EXTRA="-DIGB_LRO" install

You can verify that the driver is using LRO by looking at these counters in ethtool:

lro_aggregated - count of total packets that were combined
lro_flushed - counts the number of packets flushed out of LRO
lro_recycled - reflects the number of buffers returned to the ring from recycling

NOTE: IPv6 and UDP are not supported by LRO.

MAC and VLAN anti-spoofing feature

When a malicious driver attempts to send a spoofed packet, it is dropped by the hardware and not transmitted. An interrupt is sent to the PF driver notifying it of the spoof attempt.
When a spoofed packet is detected the PF driver will send the following message to the system log (displayed by the "dmesg" command):

Spoof event(s) detected on VF(n)

Where n=the VF that attempted to do the spoofing.

Setting MAC Address, VLAN and Rate Limit Using IProute2 Tool

You can set a MAC address of a Virtual Function (VF), a default VLAN and the rate limit using the IProute2 tool. Download the latest version of the iproute2 tool from Sourceforge if your version does not have all the features you require.

Known Issues

NOTE: After installing the driver, if your Intel Ethernet Network Connection is not working, verify that you have installed the correct driver.

Using the igb driver on 2.4 or older 2.6 based kernels

Due to limited support for PCI-Express in 2.4 kernels and older 2.6 kernels, the igb driver may run into interrupt related problems on some systems, such as no link or hang when bringing up the device.

We recommend the newer 2.6 based kernels, as these kernels correctly configure the PCI-Express configuration space of the adapter and all intervening bridges. If you are required to use a 2.4 kernel, use a 2.4 kernel newer than 2.4.30. For 2.6 kernels we recommend using the 2.6.21 kernel or newer.

Alternatively, on 2.6 kernels you may disable MSI support in the kernel by booting with the "pci=nomsi" option or permanently disable MSI support in your kernel by configuring your kernel with CONFIG_PCI_MSI unset.

Intel® Active Management Technology 2.0, 2.1, 2.5 not supported in conjunction with Linux driver

Detected Tx Unit Hang in Quad Port Adapters

In some cases ports 3 and 4 don't pass traffic and report 'Detected Tx Unit Hang' followed by 'NETDEV WATCHDOG: ethX: transmit timed out' errors. Ports 1 and 2 don't show any errors and will pass traffic.

This issue MAY be resolved by updating to the latest kernel and BIOS. The user is encouraged to run an OS that fully supports MSI interrupts. You can check your system's BIOS by downloading the Linux Firmware Developer Kit that can be obtained at http://www.linuxfirmwarekit.org/

Compiling the Driver

When trying to compile the driver by running make install, the following error may occur:  "Linux kernel source not configured - missing version.h"

To solve this issue, create the version.h file by going to the Linux source tree and entering:

# make include/linux/version.h

Performance Degradation with Jumbo Frames

Degradation in throughput performance may be observed in some Jumbo frames environments. If this is observed, increasing the application's socket buffer size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help. See the specific application manual and /usr/src/linux*/Documentation/networking/ip-sysctl.txt for more details.

Jumbo frames on Foundry BigIron 8000 switch

There is a known issue using Jumbo frames when connected to a Foundry BigIron 8000 switch. This is a 3rd party limitation. If you experience loss of packets, lower the MTU size.

Multiple Interfaces on Same Ethernet Broadcast Network

Due to the default ARP behavior on Linux, it is not possible to have one system on two IP networks in the same Ethernet broadcast domain (non-partitioned switch) behave as expected. All Ethernet interfaces will respond to IP traffic for any IP address assigned to the system. This results in unbalanced receive traffic.

If you have multiple interfaces in a server, either turn on ARP filtering by entering:

        echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter

(this only works if your kernel's version is higher than 2.4.5)

NOTE: This setting is not saved across reboots. The configuration change can be made permanent by adding the line:

net.ipv4.conf.all.arp_filter = 1

to the file /etc/sysctl.conf

   or,

install the interfaces in separate broadcast domains (either in different switches or in a switch partitioned to VLANs).

Disable rx flow control with ethtool

In order to disable receive flow control using ethtool, you must turn off auto-negotiation on the same command line.

For example:

     ethtool -A eth? autoneg off rx off

Unplugging network cable while ethtool -p is running

In kernel versions 2.5.50 and later (including 2.6 kernel), unplugging the network cable while ethtool -p is running will cause the system to become unresponsive to keyboard commands, except for control-alt-delete. Restarting the system appears to be the only remedy.

Trouble passing traffic with on ports 1 and 2 using RHEL3

There is a known hardware compatibility issue on some systems with RHEL3 kernels. Traffic on ports 1 and 2 may be slower than expected and ping times higher than expected.

This issue MAY be resolved by updating to the latest kernel and BIOS. You can check your system's BIOS by downloading the Linux Firmware Developer Kit that can be obtained at http://www.linuxfirmwarekit.org/

Do Not Use LRO When Routing Packets

Due to a known general compatibilty issue with LRO and routing, do not use LRO when routing packets.

Build error with Asianux 3.0 - redefinition of typedef 'irq_handler_t'

Some systems may experience build issues due to redefinition of irq_handler_t. To resolve this issue build the driver (step 4 above) using the command:

# make CFLAGS_EXTRA=-DAX_RELEASE_CODE=1 install

MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)

Kernel panics and instability may be observed on any MSI-X hardware if you use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.

Rx Page Allocation Errors

Page allocation failure. order:0 errors may occur under stress with kernels 2.6.25 and above. This is caused by the way the Linux kernel reports this stressed condition.

Under Redhat 5.4-GA - System May Crash when Closing Guest OS Window after Loading/Unloading Physical Function (PF) Driver

Do not remove the igb driver from Dom0 while Virtual Functions (VFs) are assigned to guests. VFs must first use the xm "pci-detach" command to hot-plug the VF device out of the VM it is assigned to or else shut down the
VM.

SLES10 SP3 random system panic when reloading driver

This is a known SLES-10 SP3 issue. After requesting interrupts for MSI-X vectors, system may panic.

Currently the only known workaround is to build the drivers with CFLAGS_EXTRA=-DDISABLE_PCI_MSI if the driver need to be loaded/unloaded. Otherwise the driver can be loaded once and will be safe, but unloading it will lead to the issue.

Enabling SR-IOV in a 32-bit Microsoft* Windows* Server 2008 Guest OS using Intel® 82576-based GbE or Intel® 82599-based 10GbE controller under KVM

KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM. This includes traditional PCIe devices, as well as SR-IOV-capable devices using Intel 82576-based and 82599-based controllers.

While direct assignment of a PCIe device or an SR-IOV Virtual Function (VF) to a Linux-based VM running 2.6.32 or later kernel works fine, there is a known issue with Microsoft Windows Server 2008 VM that results in a "yellow bang" error. This problem is within the KVM VMM itself, not the Intel driver, or the SR-IOV logic of the VMM, but rather that KVM emulates an older CPU model for the guests, and this older CPU model does not support MSI-X interrupts, which is a requirement for Intel SR-IOV.

If you wish to use the Intel 82576 or 82599-based controllers in SR-IOV mode with KVM and a Microsoft Windows Server 2008 guest try the following workaround. The workaround is to tell KVM to emulate a different model of CPU when using qemu to create the KVM guest:

"-cpu qemu64,model=13"

Host May Reboot after Removing PF when VF is Active in Guest

Using kernel versions earlier than 3.2, do not unload the PF driver with active VFs. Doing this will cause your VFs to stop working until you reload the PF driver and may cause a spontaneous reboot of your system.

Using the e1000 Base Driver

Overview

Building and Installation

Command Line Parameters

Speed and Duplex Configuration

Additional Configurations

Known Issues

Overview

The Linux Base Drivers support the 2.4.x and 2.6.x kernels. These drivers includes support for Itanium® 2-based systems.

These drivers are only supported as a loadable module. Intel is not supplying patches against the kernel source to allow for static linking of the drivers. For questions related to hardware requirements, refer to the documentation supplied with your Intel Gigabit adapter. All hardware requirements listed apply to use with Linux.

The following features are now available in supported kernels:

  • Native VLANs

  • Channel Bonding (teaming)

  • SNMP

Channel Bonding documentation can be found in the Linux kernel source: /documentation/networking/bonding.txt

The driver information previously displayed in the /proc file system is not supported in this release. Alternatively, you can use ethtool (version 1.6 or later), lspci, and ifconfig to obtain the same information. Instructions on updating ethtool can be found in the section Additional Configurations later in this document.

NOTE: The Intel® 82562v 10/100 Network Connection only provides 10/100 support.

Building and Installation

To build a binary RPM* package of this driver, run 'rpmbuild -tb e1000.tar.gz'.

NOTES:

  • For the build to work properly, the currently running kernel MUST match the version and configuration of the installed kernel sources. If you have just recompiled the kernel reboot the system now.

  • RPM functionality has only been tested in Red Hat distributions.

  1. Move the base driver tar file to the directory of your choice. For example, use '/home/username/e1000' or '/usr/local/src/e1000'.

  2. Untar/unzip the archive, where <x.x.x> is the version number for the driver tar file:

    tar zxf e1000-<x.x.x>.tar.gz

  3. Change to the driver src directory, where <x.x.x> is the version number for the driver tar:

    cd e1000-<x.x.x>/src/

  4. Compile the driver module:

    # make install

    The binary will be installed as:

    /lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000/e1000.[k]o

    The install location listed above is the default location. This may differ for various Linux distributions.

  5. Load the module using either the insmod or modprobe command:

    modprobe e1000

    insmod e1000

    Note that for 2.6 kernels the insmod command can be used if the full path to the driver module is specified. For example:

        insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000/e1000.ko

    With 2.6 based kernels also make sure that older e1000 drivers are removed from the kernel, before loading the new module:

    rmmod e1000; modprobe e1000

  6. Assign an IP address to the interface by entering the following, where <x> is the interface number:

    ifconfig eth<x> <IP_address>

  7. Verify that the interface works. Enter the following, where <IP_address> is the IP address for another machine on the same subnet as the interface that is being tested:

    ping <IP_address>

Command Line Parameters

If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:

modprobe e1000 [<option>=<VAL1>,<VAL2>,...]

For example, with two Gigabit PCI adapters, entering:

modprobe e1000 TxDescriptors=80,128

loads the e1000 driver with 80 TX descriptors for the first adapter and 128 TX descriptors for the second adapter.

The default value for each parameter is generally the recommended setting, unless otherwise noted.

NOTES:

  • For more information about the AutoNeg, Duplex, and Speed parameters, see the Speed and Duplex Configuration section in this document.

  • For more information about the InterruptThrottleRate, RxIntDelay, TxIntDelay, RxAbsIntDelay, and TxAbsIntDelay parameters, see the application note at: http://www.intel.com/design/network/applnots/ap450.htm.

  • A descriptor describes a data buffer and attributes related to the data buffer. This information is accessed by the hardware.

Parameter Name Valid Range/Settings Default Description
AutoNeg 0x01-0x0F, 0x20-0x2F 0x2F This parameter is a bit mask that specifies which speed and duplex settings the board advertises. When this parameter is used, the Speed and Duplex parameters must not be specified.

This parameter is supported only on adapters using copper connections.

NOTE: Refer to the Speed and Duplex section of this readme for more information on the AutoNeg parameter.
Duplex 0-2 (0=auto-negotiate, 1=half, 2=full) 0 Defines the direction in which data is allowed to flow. Can be either one or two-directional. If both Duplex and the link partner are set to auto-negotiate, the board auto-detects the correct duplex. If the link partner is forced (either full or half), Duplex defaults to half-duplex.

This parameter is supported only on adapters using copper connections.
FlowControl 0-3 (0=none, 1=Rx only, 2=Tx only, 3=Rx&Tx) Read flow control settings from the EEPROM This parameter controls the automatic generation(Tx) and response(Rx) to Ethernet PAUSE frames.
InterruptThrottleRate (not supported on Intel(R) 82542, 82543 or 82544-based adapters)
Valid Range: 0,1,3,4, 100-100000 (0=off, 1=dynamic, 3=dynamic conservative, 4=simplified balancing)
 		 3 The driver can limit the amount of interrupts per second that the adapter will generate for incoming packets. It does this by writing a value to the adapter that is based on the maximum amount of interrupts that the adapter will generate per second.

Setting InterruptThrottleRate to a value greater or equal to 100 will program the adapter to send out a maximum of that many interrupts per second, even if more packets have come in. This reduces interrupt load on the system and can lower CPU utilization under heavy load, but will increase latency as packets are not processed as quickly.

The default behaviour of the driver previously assumed a static InterruptThrottleRate value of 8000, providing a good fallback value for all traffic types, but lacking in small packet performance and latency. The hardware can handle many more small packets per second however, and for this reason an adaptive interrupt moderation algorithm was implemented.

Since 7.3.x, the driver has two adaptive modes (setting 1 or 3) in which it dynamically adjusts the InterruptThrottleRate value based on the traffic that it receives. After determining the type of incoming traffic in the last timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that traffic.

The algorithm classifies the incoming traffic every interval into classes. Once the class is determined, the InterruptThrottleRate value is adjusted to suit that traffic type the best. There are three classes defined: "Bulk traffic", for large amounts of packets of normal size; "Low latency", for small amounts of traffic and/or a significant percentage of small packets; and "Lowest latency", for almost completely small packets or minimal traffic.

In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low latency" or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This default mode is suitable for most applications.

For situations where low latency is vital such as cluster or grid computing, the algorithm can reduce latency even more when InterruptThrottleRate is set to mode 1. In this mode, which operates the same as mode 3, the InterruptThrottleRate will be increased stepwise to 70000 for traffic in class "Lowest latency".

In simplified mode the interrupt rate is based on the ratio of tx and rx traffic. If the bytes per second rate is approximately equal, the interrupt rate will drop as low as 2000 interrupts per second. If the traffic is mostly transmit or mostly receive, the interrupt rate could
be as high as 8000.

Setting InterruptThrottleRate to 0 turns off any interrupt moderation and may improve small packet latency, but is generally not suitable for bulk throughput traffic

NOTE: InterruptThrottleRate takes precedence over the TxAbsIntDelay and RxAbsIntDelay parameters. In other words, minimizing the receive and/or transmit absolute delays does not force the controller to generate more interrupts than what the Interrupt Throttle Rate allows.

CAUTION: If you are using the Intel(R) PRO/1000 CT Network Connection (controller 82547), setting InterruptThrottleRate to a value greater than 75,000, may hang (stop transmitting) adapters under certain network conditions. If this occurs a NETDEV WATCHDOG message is logged in the system event log. In addition, the controller is automatically reset, restoring the network connection. To eliminate the potential for the hang, ensure that InterruptThrottleRate is set no greater than 75,000 and is not set to 0.

NOTE: When e1000 is loaded with default settings and multiple adapters are in use simultaneously, the CPU utilization may increase non-linearly. In order to limit the CPU utilization without impacting the overall throughput, we recommend that you load the driver as follows:

modprobe e1000 InterruptThrottleRate=3000,3000,3000

This sets the InterruptThrottleRate to 3000 interrupts/sec for the first, second, and third instances of the driver. The range of 2000 to 3000 interrupts per second works on a majority of systems and is a good starting point, but the optimal value will be platform-specific. If CPU utilization is not a concern, use RX_POLLING (NAPI) and default driver settings.
RxDescriptors 80-4096 256
This value specifies the number of receive buffer descriptors allocated by the driver. Increasing this value allows the driver to buffer more incoming packets, at the expense of increased system memory utilization.

Each descriptor is 16 bytes. A receive buffer is also allocated for each descriptor and can be either 2048, 4096, 8192, or 16384 bytes, depending on the MTU setting. The maximum MTU size is 16110.

NOTE: MTU designates the frame size. It only needs to be set for Jumbo Frames. Depending on the available system resources, the request for a higher number of receive descriptors may be denied. In this case, use a lower number.
RxIntDelay 0-65535 (0=off) 0 This value delays the generation of receive interrupts in units of 1.024 microseconds. Receive interrupt reduction can improve CPU efficiency if properly tuned for specific network traffic. Increasing this value adds extra latency to frame reception and can end up decreasing the throughput of TCP traffic. If the system is reporting dropped receives, this value may be set too high, causing the driver to run out of available receive descriptors.

CAUTION: When setting RxIntDelay to a value other than 0, adapters may hang (stop transmitting) under certain network conditions. If this occurs a NETDEV WATCHDOG message is logged in the system event log. In addition, the controller is automatically reset, restoring the network connection. To eliminate the potential for the hang ensure that RxIntDelay is set to zero.

RxAbsIntDelay 0-65535 (0=off) 8 This value, in units of 1.024 microseconds, limits the delay in which a receive interrupt is generated. Useful only if RxIntDelay is non-zero, this value ensures that an interrupt is generated after the initial packet is received within the set amount of time. Proper tuning, along with RxIntDelay, may improve traffic throughput in specific network conditions.

This parameter is supported only on 82540, 82545 and later adapters.

Speed 0, 10, 100, 1000 0 Speed forces the line speed to the specified value in megabits per second (Mbps). If this parameter is not specified or is set to 0 and the link partner is set to auto-negotiate, the board will auto-detect the correct speed. Duplex must also be set when Speed is set to either 10 or 100.

This parameter is supported only on adapters using copper connections.
TxDescriptors 80-4096 256 This value is the number of transmit descriptors allocated by the driver. Increasing this value allows the driver to queue more transmits. Each descriptor is 16 bytes.
TxDescriptorStep 1 (use every Tx Descriptor)
4 (use every 4th Tx Descriptor)		 1 (use every Tx Descriptor) On certain non-Intel architectures, it has been observed that intense TX traffic bursts of short packets may result in an improper descriptor writeback. If this occurs, the driver will report a "TX Timeout" and reset the adapter, after which the transmit flow will restart, though data may have stalled for as much as 10 seconds before it resumes.

The improper writeback does not occur on the first descriptor in a system memory cache-line, which is typically 32 bytes, or 4 descriptors long.

Setting TxDescriptorStep to a value of 4 will ensure that all TX descriptors are aligned to the start of a system memory cache line, and so this problem will not occur.

NOTES: Setting TxDescriptorStep to 4 effectively reduces the number of TxDescriptors available for transmits to 1/4 of the normal allocation. This has a possible negative performance impact, which may be compensated for by allocating more descriptors using the TxDescriptors module parameter.

There are other conditions which may result in "TX Timeout", which will not be resolved by the use of the TxDescriptorStep parameter. As the issue addressed by this parameter has never been observed on Intel Architecture platforms, it should not be used on Intel platforms.
TxIntDelay 0-65535 (0=off) 8 This value delays the generation of transmit interrupts in units of 1.024 microseconds. Transmit interrupt reduction can improve CPU efficiency if properly tuned for specific network traffic. If the system is reporting dropped transmits, this value may be set too high causing the driver to run out of available transmit descriptors.
TxAbsIntDelay 0-65535 (0=off) 32 This value, in units of 1.024 microseconds, limits the delay in which a transmit interrupt is generated. Useful only if TxIntDelay is non-zero, this value ensures that an interrupt is generated after the initial packet is sent on the wire within the set amount of time. Proper tuning, along with TxIntDelay, may improve traffic throughput in specific network conditions.

This parameter is supported only on 82540, 82545 and later adapters.
XsumRX 0-1 1 A value of '1' indicates that the driver should enable IP checksum offload for received packets (both UDP and TCP) to the adapter hardware.

This parameter is not supported on the 82542-based adapter.
Copybreak 0-xxxxxxx (0=off) 256 Usage: insmod e1000.ko copybreak=128

Driver copies all packets below or equaling this size to a fresh rx buffer before handing it up the stack.

This parameter is different than other parameters, in that it is a single (not 1,1,1 etc.) parameter applied to all driver instances and it is also available during runtime at /sys/module/e1000/parameters/copybreak
SmartPowerDownEnable 0-1
 		 0 (disabled) Allows Phy to turn off in lower power states. The user can turn off this parameter in supported chipsets.
KumeranLockLoss 0-1 1 (enabled) This workaround skips resetting the Phy at shutdown for the initial silicon releases of ICH8 systems.
TxDescPower

 		 6-12 12 This value represents the size-order of each transmit descriptor. The valid size for descriptors would be 2^6 (64) to 2^12 (4096) bytes each. As this value decreases one may want to consider increasing the TxDescriptors value to maintain the same amount of frame memory.

Speed and Duplex Configuration

Three keywords are used to control the speed and duplex configuration. These keywords are Speed, Duplex, and AutoNeg.

If the board uses a fiber interface, these keywords are ignored, and the fiber interface board only links at 1000 Mbps full-duplex.

For copper-based boards, the keywords interact as follows:

The default operation is auto-negotiate. The board advertises all supported speed and duplex combinations, and it links at the highest common speed and duplex mode IF the link partner is set to auto-negotiate.

If Speed = 1000, limited auto-negotiation is enabled and only 1000 Mbps is advertised (The 1000BaseT spec requires auto-negotiation.)

If Speed = 10 or 100, then both Speed and Duplex should  be set. Auto-negotiation is disabled, and the AutoNeg parameter is ignored. Partner SHOULD also be forced.

The AutoNeg parameter is used when more control is required over the auto-negotiation process. It should be used when you wish to control which speed and duplex combinations are advertised during the auto-negotiation process. The parameter may be specified as either a decimal or hexadecimal value as determined by the bitmap below.

Bit Position 7 6 5 4 3 2 1 0
Decimal Value 128 64 32 16 8 4 2 1
Hex Value 80 40 20 10 8  4 2 1
Speed (Mbps): N/A N/A 1000 N/A 100 100 10 10
Duplex:     Full   Full Half Full Half

Some examples of using AutoNeg:

     modprobe e1000 AutoNeg=0x01 (Restricts autonegotiation to 10 Half)
     modprobe e1000 AutoNeg=1 (Same as above)
     modprobe e1000 AutoNeg=0x02 (Restricts autonegotiation to 10 Full)
     modprobe e1000 AutoNeg=0x03 (Restricts autonegotiation to 10 Half or 10 Full)
     modprobe e1000 AutoNeg=0x04 (Restricts autonegotiation to 100 Half)
     modprobe e1000 AutoNeg=0x05 (Restricts autonegotiation to 10 Half or 100 Half)
     modprobe e1000 AutoNeg=0x020 (Restricts autonegotiation to 1000 Full)
     modprobe e1000 AutoNeg=32 (Same as above)

Note that when this parameter is used, Speed and Duplex must not be specified.

If the link partner is forced to a specific speed and duplex, then this parameter should not be used. Instead, use the Speed and Duplex parameters previously mentioned to force the adapter to the same speed and duplex.

Additional Configurations

Configuring the Driver on Different Distributions

Configuring a network driver to load properly when the system is started is distribution dependent. Typically, the configuration process involves adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other system startup scripts and/or configuration files. Many popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, refer to your distribution documentation. If during this process you are asked for the driver or module name, the name for the Linux Base Driver for the Gigabit family of adapters is e1000.

As an example, if you install the e1000 driver for two Gigabit adapters (eth0 and eth1) and set the speed and duplex to 10full and 100half, add the following to modules.conf or /etc/modprobe.conf:

alias eth0 e1000
alias eth1 e1000
options e1000 Speed=10,100 Duplex=2,1

Viewing Link Messages

Link messages will not be displayed to the console if the distribution is restricting system messages. In order to see network driver link messages on your console, set dmesg to eight by entering the following:

dmesg -n 8
NOTE: This setting is not saved across reboots.

Jumbo Frames

Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU) to a value larger than the default value of 1500. Use the ifconfig command to increase the MTU size. For example:

ifconfig eth<x> mtu 9000 up

This setting is not saved across reboots. The setting change can be made permanent by adding MTU=9000 to the file: /etc/sysconfig/network-scripts/ifcfg-eth<x> (Red Hat distributions). Other distributions may store this setting in a different location.

NOTES:

  • To enable Jumbo Frames, increase the MTU size on the interface beyond 1500.

  • The maximum MTU setting for Jumbo Frames is 16110. This value coincides with the maximum Jumbo Frames size of 16128.

  • Some Intel gigabit adapters that support Jumbo Frames have a frame size limit of 9238 bytes, with a corresponding MTU size limit of 9216 bytes. The adapters with this limitation are based on the Intel® 82571EB, 82572EI, 82573L, 82566, 82562, 82575, and 80003ES2LAN controllers. These correspond to the following product names:
    Intel® PRO/1000 PT Server Adapter
    Intel® PRO/1000 PT Desktop Adapter
    Intel® PRO/1000 PT Network Connection
    Intel® PRO/1000 PT Dual Port Server Adapter
    Intel® PRO/1000 PT Dual Port Network Connection
    Intel® PRO/1000 PF Server Adapter
    Intel® PRO/1000 PF Network Connection
    Intel® PRO/1000 PF Dual Port Server Adapter
    Intel® PRO/1000 PB Server Connection
    Intel® PRO/1000 PL Network Connection
    Intel® PRO/1000 EB Network Connection with I/O Acceleration
    Intel® PRO/1000 EB Backplane Connection with I/O Acceleration
    Intel® PRO/1000 PT Quad Port Server Adapter
    Intel® PRO/1000 PF Quad Port Server Adapter
    Intel® 82566DM-2 Gigabit Network Connection
    Intel® Gigabit PT Quad Port Server ExpressModule

  • Using Jumbo frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.

  • The following adapters do not support Jumbo Frames:
    Intel® PRO/1000 Gigabit Server Adapter
    Intel® PRO/1000 PM Network Connection
    Intel® 82562V 10/100 Network Connection
    Intel® 82566DM Gigabit Network Connection
    Intel® 82566DC Gigabit Network Connection
    Intel® 82566MM Gigabit Network Connection
    Intel® 82566MC Gigabit Network Connection
    Intel® 82562GT 10/100 Network Connection
    Intel 82562G 10/100 Network Connection
    Intel 82566DC-2 Gigabit Network Connection
    Intel 82562V-2 10/100 Network Connection
    Intel 82562G-2 10/100 Network Connection
    Intel 82562GT-2 10/100 Network Connection

ethtool

The driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information. ethtool version 3 or later is required for this functionality, although we strongly recommend downloading the latest version at:

http://ftp.kernel.org/pub/software/network/ethtool/.

Enabling Wake on LAN* (WoL)

WoL is configured through the ethtool* utility. ethtool is included with all versions of Red Hat after Red Hat 7.2. For other Linux distributions, download and install ethtool from the following website: http://ftp.kernel.org/pub/software/network/ethtool/.

For instructions on enabling WoL with ethtool, refer to the website listed above.

WoL will be enabled on the system during the next shut down or reboot. For this driver version, in order to enable WoL, the e1000 driver must be loaded prior to shutting down or suspending the system.

NOTES: Wake On LAN is only supported on port A for the following devices:
  • Intel® PRO/1000 PT Dual Port Network Connection
  • Intel® PRO/1000 PT Dual Port Server Connection
  • Intel® PRO/1000 PT Dual Port Server Adapter
  • Intel® PRO/1000 PF Dual Port Server Adapter
  • Intel PRO/1000 PT Quad Port Server Adapter
  • Intel® Gigabit PT Quad Port Server ExpressModule

NAPI

NAPI (Rx polling mode) is supported in the e1000 driver. NAPI is enabled or disabled based on the configuration of the kernel. To override the default, use the following compile-time flags.

To enable NAPI, compile the driver module, passing in a configuration option:

# make CFLAGS_EXTRA=-DE1000_NAPI install

To disable NAPI, compile the driver module, passing in a configuration option:

# make CFLAGS_EXTRA=-DE1000_NO_NAPI install

See ftp://robur.slu.se/pub/Linux/net-development/NAPI/usenix-paper.tgz for more information on NAPI.

Known Issues

NOTE: After installing the driver, if your Intel Ethernet Network Connection is not working, verify that you have installed the correct driver.

Intel® Active Management Technology 2.0, 2.1, 2.5 not supported in conjunction with Linux driver

Detected Tx Unit Hang in Quad Port Adapters

In some cases ports 3 and 4 don't pass traffic and report 'Detected Tx Unit Hang' followed by 'NETDEV WATCHDOG: ethX: transmit timed out' errors. Ports 1 and 2 don't show any errors and will pass traffic.

This issue MAY be resolved by updating to the latest kernel and BIOS. The user is encouraged to run an OS that fully supports MSI interrupts. You can check your system's BIOS by downloading the Linux Firmware Developer Kit that can be obtained at http://www.linuxfirmwarekit.org/

82573(V/L/E) TX Unit Hang Messages

Several adapters with the 82573 chipset display "TX unit hang" messages during normal operation with the e1000 driver. The issue appears both with TSO enabled and disabled, and is caused by a power management function that is enabled in the EEPROM. Early releases of the chipsets to vendors had the EEPROM bit that enabled the feature. After the issue was discovered newer adapters were released with the feature disabled in the EEPROM.

If you encounter the problem in an adapter, and the chipset is an 82573-based one, you can verify that your adapter needs the fix by using ethtool: 

 # ethtool -e eth0
 Offset          Values
 ------          ------
 0x0000          00 12 34 56 fe dc 30 0d 46 f7 f4 00 ff ff ff ff
 0x0010          ff ff ff ff 6b 02 8c 10 d9 15 8c 10 86 80 de 83
                                                           ^^

The value at offset 0x001e (de) has bit 0 unset. This enables the problematic power saving feature. In this case, the EEPROM needs to read "df" at offset 0x001e.

A one-time EEPROM fix is available as a shell script. This script will verify that the adapter is applicable to the fix and if the fix is needed or not. If the fix is required, it applies the change to the EEPROM and updates the checksum. The user must reboot the system after applying the fix if changes were made to the EEPROM.

Example output of the script: 

 # bash fixeep-82573-dspd.sh eth0
 eth0: is a "82573E Gigabit Ethernet Controller"
 This fixup is applicable to your hardware
 executing command: ethtool -E eth0 magic 0x109a8086 offset 0x1e value 0xdf
 Change made. You *MUST* reboot your machine before changes take effect!

The script can be downloaded at http://e1000.sourceforge.net/files/fixeep-82573-dspd.sh

Dropped Receive Packets on Half-duplex 10/100 Networks

If you have an Intel PCI Express adapter running at 10mbps or 100mbps, half-duplex, you may observe occasional dropped receive packets. There are no workarounds for this problem in this network configuration. The network must be updated to operate in full-duplex, and/or 1000mbps only.

Compiling the Driver

When trying to compile the driver by running make install, the following error may occur:  "Linux kernel source not configured - missing version.h"

To solve this issue, create the version.h file by going to the Linux source tree and entering:

# make include/linux/version.h

Performance Degradation with Jumbo Frames

Degradation in throughput performance may be observed in some Jumbo frames environments. If this is observed, increasing the application's socket buffer size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help. See the specific application manual and /usr/src/linux*/Documentation/networking/ip-sysctl.txt for more details.

Jumbo frames on Foundry BigIron 8000 switch

There is a known issue using Jumbo frames when connected to a Foundry BigIron 8000 switch. This is a 3rd party limitation. If you experience loss of packets, lower the MTU size.

Allocating Rx Buffers when Using Jumbo Frames

Allocating Rx buffers when using Jumbo Frames on 2.6.x kernels may fail if the available memory is heavily fragmented. This issue may be seen with PCI-X adapters or with packet split disabled. This can be reduced or eliminated by changing the amount of available memory for receive buffer allocation, by increasing /proc/sys/vm/min_free_kbytes.

Multiple Interfaces on Same Ethernet Broadcast Network

Due to the default ARP behavior on Linux, it is not possible to have one system on two IP networks in the same Ethernet broadcast domain (non-partitioned switch) behave as expected. All Ethernet interfaces will respond to IP traffic for any IP address assigned to the system. This results in unbalanced receive traffic.

If you have multiple interfaces in a server, either turn on ARP filtering by entering:

        echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter

(this only works if your kernel's version is higher than 2.4.5)

NOTE: This setting is not saved across reboots. The configuration change can be made permanent by adding the line:

net.ipv4.conf.all.arp_filter = 1

to the file /etc/sysctl.conf

   or,

install the interfaces in separate broadcast domains (either in different switches or in a switch partitioned to VLANs).

82541/82547 can't link or is slow to link with some link partners

There is a known compatibility issue with 82541/82547 and some low-end switches where the link will not be established, or will be slow to establish. In particular, these switches are known to be incompatible with 82541/82547:

     Planex FXG-08TE
     I-O Data ETG-SH8

To workaround this issue, the driver can be compiled with an override of the PHY's master/slave setting. Forcing master or forcing slave mode will improve time-to-link.

     # make CFLAGS_EXTRA=-DE1000_MASTER_SLAVE=<n>

Where <n> is:

        0 = Hardware default
        1 = Master mode
        2 = Slave mode
        3 = Auto master/slave

Disable rx flow control with ethtool

In order to disable receive flow control using ethtool, you must turn off auto-negotiation on the same command line.

For example:

     ethtool -A eth? autoneg off rx off

Unplugging network cable while ethtool -p is running

In kernel versions 2.5.50 and later (including 2.6 kernel), unplugging the network cable while ethtool -p is running will cause the system to
become unresponsive to keyboard commands, except for control-alt-delete. Restarting the system appears to be the only remedy.

Using the e1000e Base Driver

Overview

Building and Installation

Command Line Parameters

Speed and Duplex Configuration

Additional Configurations

Known Issues

Overview

The Linux Base Drivers support the 2.4.x and 2.6.x kernels. These drivers includes support for Itanium® 2-based systems.

These drivers are only supported as a loadable module. Intel is not supplying patches against the kernel source to allow for static linking of the drivers. For questions related to hardware requirements, refer to the documentation supplied with your Intel Gigabit adapter. All hardware requirements listed apply to use with Linux.

The following features are now available in supported kernels:

  • Native VLANs

  • Channel Bonding (teaming)

  • SNMP

Channel Bonding documentation can be found in the Linux kernel source: /documentation/networking/bonding.txt

The driver information previously displayed in the /proc file system is not supported in this release. Alternatively, you can use ethtool (version 1.6 or later), lspci, and ifconfig to obtain the same information. Instructions on updating ethtool can be found in the section Additional Configurations later in this document.

NOTE: The Intel® 82562v 10/100 Network Connection only provides 10/100 support.

Building and Installation

To build a binary RPM* package of this driver, run 'rpmbuild -tb e1000e.tar.gz'.

NOTES:

  • For the build to work properly, the currently running kernel MUST match the version and configuration of the installed kernel sources. If you have just recompiled the kernel reboot the system now.

  • RPM functionality has only been tested in Red Hat distributions.

  1. Move the base driver tar file to the directory of your choice. For example, use '/home/username/e1000e' or '/usr/local/src/e1000e'.

  2. Untar/unzip the archive, where <x.x.x> is the version number for the driver tar file:

    tar zxf e1000e-<x.x.x>.tar.gz

  3. Change to the driver src directory, where <x.x.x> is the version number for the driver tar:

    cd e1000e-<x.x.x>/src/

  4. Compile the driver module:

    # make install

    The binary will be installed as:

    /lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000e/e1000e.[k]o

    The install location listed above is the default location. This may differ for various Linux distributions.

  5. Load the module using either the insmod or modprobe command:

    modprobe e1000e

    insmod e1000e

    Note that for 2.6 kernels the insmod command can be used if the full path to the driver module is specified. For example:

        insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000e/e1000e.ko

    With 2.6 based kernels also make sure that older e1000e drivers are removed from the kernel, before loading the new module:

    rmmod e1000e; modprobe e1000e

  6. Assign an IP address to the interface by entering the following, where <x> is the interface number:

    ifconfig eth<x> <IP_address>

  7. Verify that the interface works. Enter the following, where <IP_address> is the IP address for another machine on the same subnet as the interface that is being tested:

    ping <IP_address>

TROUBLESHOOTING: Some systems have trouble supporting MSI and/or MSI-X interrupts. If you believe your system needs to disable this style of interrupt, the driver can be built and installed with the command:

# make CFLAGS_EXTRA=-DDISABLE_PCI_MSI install

Normally the driver will generate an interrupt every two seconds, so if you can see that you're no longer getting interrupts in cat /proc/interrupts for the ethX e1000e device, then this workaround may be necessary.

Command Line Parameters

If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:

modprobe e1000e [<option>=<VAL1>,<VAL2>,...]

The default value for each parameter is generally the recommended setting, unless otherwise noted.

NOTES:

  • For more information about the InterruptThrottleRate, RxIntDelay, TxIntDelay, RxAbsIntDelay, and TxAbsIntDelay parameters, see the application note at: http://www.intel.com/design/network/applnots/ap450.htm.

  • A descriptor describes a data buffer and attributes related to the data buffer. This information is accessed by the hardware.

Parameter Name Valid Range/Settings Default Description
InterruptThrottleRate
0,1,3,4, 100-100000 (0=off, 1=dynamic, 3=dynamic conservative, 4-simplified balancing)
 		 3 The driver can limit the amount of interrupts per second that the adapter will generate for incoming packets. It does this by writing a value to the adapter that is based on the maximum amount of interrupts that the adapter will generate per second.

Setting InterruptThrottleRate to a value greater or equal to 100 will program the adapter to send out a maximum of that many interrupts per second, even if more packets have come in. This reduces interrupt load on the system and can lower CPU utilization under heavy load, but will increase latency as packets are not processed as quickly.

The default behavior of the driver previously assumed a static InterruptThrottleRate value of 8000, providing a good fallback value for all traffic types, but lacking in small packet performance and latency.

The driver has two adaptive modes (setting 1 or 3) in which it dynamically adjusts the InterruptThrottleRate value based on the traffic that it receives. After determining the type of incoming traffic in the last timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that traffic.

The algorithm classifies the incoming traffic every interval into classes. Once the class is determined, the InterruptThrottleRate value is adjusted to suit that traffic type the best. There are three classes defined: "Bulk traffic", for large amounts of packets of normal size; "Low latency", for small amounts of traffic and/or a significant percentage of small packets; and "Lowest latency", for almost completely small packets or minimal traffic.

In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low latency" or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This default mode is suitable for most applications.

For situations where low latency is vital such as cluster or grid computing, the algorithm can reduce latency even more when InterruptThrottleRate is set to mode 1. In this mode, which operates the same as mode 3, the InterruptThrottleRate will be increased stepwise to 70000 for traffic in class "Lowest latency".

In simplified mode the interrupt rate is based on the ratio of tx and rx traffic. If the bytes per second rate is approximately equal, the interrupt rate will drop as low as 2000 interrupts per second. If the traffic is mostly transmit or mostly receive, the interrupt rate could be as high as 8000.

Setting InterruptThrottleRate to 0 turns off any interrupt moderation and may improve small packet latency, but is generally not suitable for bulk throughput traffic

NOTE: InterruptThrottleRate takes precedence over the TxAbsIntDelay and RxAbsIntDelay parameters. In other words, minimizing the receive and/or transmit absolute delays does not force the controller to generate more interrupts than what the Interrupt Throttle Rate allows.

NOTE: When e1000e is loaded with default settings and multiple adapters are in use simultaneously, the CPU utilization may increase non-linearly. In order to limit the CPU utilization without impacting the overall throughput, we recommend that you load the driver as follows:

modprobe e1000e InterruptThrottleRate=3000,3000,3000

This sets the InterruptThrottleRate to 3000 interrupts/sec for the first, second, and third instances of the driver. The range of 2000 to 3000 interrupts per second works on a majority of systems and is a good starting point, but the optimal value will be platform-specific. If CPU utilization is not a concern, use RX_POLLING (NAPI) and default driver settings.
RxIntDelay 0-65535 (0=off) 0 This value delays the generation of receive interrupts in units of 1.024 microseconds. Receive interrupt reduction can improve CPU efficiency if properly tuned for specific network traffic. Increasing this value adds extra latency to frame reception and can end up decreasing the throughput of TCP traffic. If the system is reporting dropped receives, this value may be set too high, causing the driver to run out of available receive descriptors.

CAUTION: When setting RxIntDelay to a value other than 0, adapters may hang (stop transmitting) under certain network conditions. If this occurs a NETDEV WATCHDOG message is logged in the system event log. In addition, the controller is automatically reset, restoring the network connection. To eliminate the potential for the hang ensure that RxIntDelay is set to zero.

RxAbsIntDelay 0-65535 (0=off) 8 This value, in units of 1.024 microseconds, limits the delay in which a receive interrupt is generated. Useful only if RxIntDelay is non-zero, this value ensures that an interrupt is generated after the initial packet is received within the set amount of time. Proper tuning, along with RxIntDelay, may improve traffic throughput in specific network conditions.
TxIntDelay 0-65535 (0=off) 8 This value delays the generation of transmit interrupts in units of 1.024 microseconds. Transmit interrupt reduction can improve CPU efficiency if properly tuned for specific network traffic. If the system is reporting dropped transmits, this value may be set too high causing the driver to run out of available transmit descriptors.
TxAbsIntDelay 0-65535 (0=off) 32 This value, in units of 1.024 microseconds, limits the delay in which a transmit interrupt is generated. Useful only if TxIntDelay is non-zero, this value ensures that an interrupt is generated after the initial packet is sent on the wire within the set amount of time. Proper tuning, along with TxIntDelay, may improve traffic throughput in specific network conditions.
copybreak 0-xxxxxxx (0=off) 256 Usage: insmod e1000e.ko copybreak=128

Driver copies all packets below or equaling this size to a fresh rx buffer before handing it up the stack.

This parameter is different than other parameters, in that it is a single (not 1,1,1 etc.) parameter applied to all driver instances and it is also available during runtime at /sys/module/e1000e/parameters/copybreak
SmartPowerDownEnable 0-1
 		 0 (disabled) Allows Phy to turn off in lower power states. The user can turn off this parameter in supported chipsets.
KumeranLockLoss 0-1 1 (enabled) This workaround skips resetting the Phy at shutdown for the initial silicon releases of ICH8 systems.
IntMode 0-2

(0=legacy, 1=MSI, 2=MSI-X)

2 (MSI-X)

 

 Allows changing the interrupt mode at module load time, without requiring a recompile. If the driver load fails to enable a specific interrupt mode, the driver will try other interrupt modes, from least to most compatible. The interrupt order is MSI-X, MSI, Legacy. If specifying MSI (IntMode=1) interrupts, only MSI and Legacy will be attempted.
CrcStripping 0-1 1 (enabled) Strip the CRC from received packets before sending up the network stack. If you have a machine with a BMC enabled but cannot receive IPMI traffic after loading or enabling the driver, try disabling this feature.
EEE 0-1 1 (enabled for parts supporting EEE) This option allows for the ability of IEEE802.3az (a.k.a. Energy Efficient Ethernet or EEE) to be advertised to the link partner on parts supporting EEE.  EEE saves energy by putting the device into a low-power state when the link is idle, but only when the link partner also supports EEE and after the feature has been enabled during link negotiation.  It is not necessary to disable the advertisement of EEE when connected with a link partner that does not support EEE.
Node 0-n

0 - n: where n is the number of the NUMA node that should be used to allocate memory for this adapter port.

-1: uses the driver default of allocating memory on whichever processor is running insmod/modprobe.

-1 (off) The Node parameter will allow you to pick which NUMA node you want to have   the adapter allocate memory from.  All driver structures, in-memory queues, and receive buffers will be allocated on the node specified.  This parameter is only useful when interrupt affinity is specified, otherwise some portion of the time the interrupt could run on a different core than the memory is allocated on, causing slower memory access and impacting throughput, CPU, or both. 

Additional Configurations

Configuring the Driver on Different Distributions

Configuring a network driver to load properly when the system is started is distribution dependent. Typically, the configuration process involves adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other system startup scripts and/or configuration files. Many popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, refer to your distribution documentation. If during this process you are asked for the driver or module name, the name for the Linux Base Driver for the Gigabit family of adapters is e1000e.

As an example, if you install the e1000e driver for two Gigabit adapters (eth0 and eth1) and want to set the interrupt mode to MSI-X and MSI respectively, add the following to modules.conf or /etc/modprobe.conf:
alias eth0 e1000e
alias eth1 e1000e
options e1000e IntMode=2,1

Viewing Link Messages

Link messages will not be displayed to the console if the distribution is restricting system messages. In order to see network driver link messages on your console, set dmesg to eight by entering the following:

dmesg -n 8
NOTE: This setting is not saved across reboots.

Jumbo Frames

Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU) to a value larger than the default value of 1500. Use the ifconfig command to increase the MTU size. For example:

ifconfig eth<x> mtu 9000 up

This setting is not saved across reboots. The setting change can be made permanent by adding MTU=9000 to the file: /etc/sysconfig/network-scripts/ifcfg-eth<x> (Red Hat distributions). Other distributions may store this setting in a different location.

NOTES:

  • To enable Jumbo Frames, increase the MTU size on the interface beyond 1500.

  • The maximum MTU setting for Jumbo Frames is 9216. This value coincides with the maximum Jumbo Frames size of 9234 bytes.

  • Using Jumbo frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.

  • The following adapters limit Jumbo Frames sized packets to a maximum of 4088 bytes:
    Intel® 82578DM Gigabit Network Connection
    Intel® 82577LM Gigabit Network Connection

  • The following adapters do not support Jumbo Frames:
    Intel® PRO/1000 Gigabit Server Adapter
    Intel® PRO/1000 PM Network Connection
    Intel® 82562V 10/100 Network Connection
    Intel® 82566DM Gigabit Network Connection
    Intel® 82566DC Gigabit Network Connection
    Intel® 82566MM Gigabit Network Connection
    Intel® 82566MC Gigabit Network Connection
    Intel® 82562GT 10/100 Network Connection
    Intel 82562G 10/100 Network Connection
    Intel® 82566DC-2 Gigabit Network Connection
    Intel 82562V-2 10/100 Network Connection
    Intel 82562G-2 10/100 Network Connection
    Intel 82562GT-2 10/100 Network Connection
    Intel® 82578DC Gigabit Network Connection
    Intel® 82577LC Gigabit Network Connection
    Intel® 82567V-3 Gigabit Network Connection

  • Jumbo Frames cannot be configured on an 82579-based Network device, if MACSec is enabled on the system.

ethtool

The driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information. ethtool version 3 or later is required for this functionality, although we strongly recommend downloading the latest version at:

http://ftp.kernel.org/pub/software/network/ethtool/.

NOTE: When validating enable/disable tests on some parts (82578, for example) you need to add a few seconds between tests when working with ethtool.

Speed and Duplex Configuration

Speed and Duplex are configured through the ethtool* utility. ethtool is included with all versions of Red Hat after Red Hat 7.2. For other Linux distributions, download and install ethtool from the following website: http://ftp.kernel.org/pub/software/network/ethtool/.

Enabling Wake on LAN* (WoL)

WoL is configured through the ethtool* utility. ethtool is included with all versions of Red Hat after Red Hat 7.2. For other Linux distributions, download and install ethtool from the following website: http://ftp.kernel.org/pub/software/network/ethtool/.

For instructions on enabling WoL with ethtool, refer to the website listed above.

WoL will be enabled on the system during the next shut down or reboot. For this driver version, in order to enable WoL, the e1000e driver must be loaded prior to shutting down or suspending the system.

NOTES: Wake On LAN is only supported on port A for the following devices:
  • Intel® PRO/1000 PT Dual Port Network Connection
  • Intel® PRO/1000 PT Dual Port Server Connection
  • Intel® PRO/1000 PT Dual Port Server Adapter
  • Intel® PRO/1000 PF Dual Port Server Adapter
  • Intel PRO/1000 PT Quad Port Server Adapter
  • Intel® Gigabit PT Quad Port Server ExpressModule

NAPI

NAPI (Rx polling mode) is supported in the e1000e driver. NAPI is enabled by default.

To disable NAPI, compile the driver module, passing in a configuration option:

# make CFLAGS_EXTRA=-DE1000E_NO_NAPI install

See ftp://robur.slu.se/pub/Linux/net-development/NAPI/usenix-paper.tgz for more information on NAPI.

Known Issues

NOTE: After installing the driver, if your Intel Network Connection is not working, verify that you have installed the correct driver.

Intel® Active Management Technology 2.0, 2.1, 2.5 not supported in conjunction with Linux driver

Detected Tx Unit Hang in Quad Port Adapters

In some cases ports 3 and 4 don't pass traffic and report 'Detected Tx Unit Hang' followed by 'NETDEV WATCHDOG: ethX: transmit timed out' errors. Ports 1 and 2 don't show any errors and will pass traffic.

This issue MAY be resolved by updating to the latest kernel and BIOS. The user is encouraged to run an OS that fully supports MSI interrupts. You can check your system's BIOS by downloading the Linux Firmware Developer Kit that can be obtained at http://www.linuxfirmwarekit.org/

Adapters with 4 ports behind a PCIe bridge

Adapters that have 4 ports behind a PCIe bridge may be incompatible with some systems. The user should run the Linux firmware kit from
http://www.linuxfirmwarekit.org/ to test their BIOS, if they have interrupt or "missing interface" problems, especially with older kernels.

82573(V/L/E) TX Unit Hang Messages

Several adapters with the 82573 chipset display "TX unit hang" messages during normal operation with the e1000e driver. The issue appears both with TSO enabled and disabled, and is caused by a power management function that is enabled in the EEPROM. Early releases of the chipsets to vendors had the EEPROM bit that enabled the feature. After the issue was discovered newer adapters were released with the feature disabled in the EEPROM.

If you encounter the problem in an adapter, and the chipset is an 82573-based one, you can verify that your adapter needs the fix by using ethtool: 

 # ethtool -e eth0
 Offset          Values
 ------          ------
 0x0000          00 12 34 56 fe dc 30 0d 46 f7 f4 00 ff ff ff ff
 0x0010          ff ff ff ff 6b 02 8c 10 d9 15 8c 10 86 80 de 83
                                                           ^^

The value at offset 0x001e (de) has bit 0 unset. This enables the problematic power saving feature. In this case, the EEPROM needs to read "df" at offset 0x001e.

A one-time EEPROM fix is available as a shell script. This script will verify that the adapter is applicable to the fix and if the fix is needed or not. If the fix is required, it applies the change to the EEPROM and updates the checksum. The user must reboot the system after applying the fix if changes were made to the EEPROM.

Example output of the script: 

 # bash fixeep-82573-dspd.sh eth0
 eth0: is a "82573E Gigabit Ethernet Controller"
 This fixup is applicable to your hardware
 executing command: ethtool -E eth0 magic 0x109a8086 offset 0x1e value 0xdf
 Change made. You *MUST* reboot your machine before changes take effect!

The script can be downloaded at http://e1000.sourceforge.net/files/fixeep-82573-dspd.sh

Dropped Receive Packets on Half-duplex 10/100 Networks

If you have an Intel PCI Express adapter running at 10mbps or 100mbps, half-duplex, you may observe occasional dropped receive packets. There are no workarounds for this problem in this network configuration. The network must be updated to operate in full-duplex, and/or 1000mbps only.

Compiling the Driver

When trying to compile the driver by running make install, the following error may occur:  "Linux kernel source not configured - missing version.h"

To solve this issue, create the version.h file by going to the Linux source tree and entering:

# make include/linux/version.h

Performance Degradation with Jumbo Frames

Degradation in throughput performance may be observed in some Jumbo frames environments. If this is observed, increasing the application's socket buffer size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help. See the specific application manual and /usr/src/linux*/Documentation/networking/ip-sysctl.txt for more details.

Jumbo frames on Foundry BigIron 8000 switch

There is a known issue using Jumbo frames when connected to a Foundry BigIron 8000 switch. This is a 3rd party limitation. If you experience loss of packets, lower the MTU size.

Allocating Rx Buffers when Using Jumbo Frames

Allocating Rx buffers when using Jumbo Frames on 2.6.x kernels may fail if the available memory is heavily fragmented. This issue may be seen with PCI-X
adapters or with packet split disabled. This can be reduced or eliminated by changing the amount of available memory for receive buffer allocation, by increasing /proc/sys/vm/min_free_kbytes.

Multiple Interfaces on Same Ethernet Broadcast Network

Due to the default ARP behavior on Linux, it is not possible to have one system on two IP networks in the same Ethernet broadcast domain (non-partitioned switch) behave as expected. All Ethernet interfaces will respond to IP traffic for any IP address assigned to the system. This results in unbalanced receive traffic.

If you have multiple interfaces in a server, either turn on ARP filtering by entering:

        echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter

(this only works if your kernel's version is higher than 2.4.5)

NOTE: This setting is not saved across reboots. The configuration change can be made permanent by adding the line:

net.ipv4.conf.all.arp_filter = 1

to the file /etc/sysctl.conf

   or,

install the interfaces in separate broadcast domains (either in different switches or in a switch partitioned to VLANs).

Disable rx flow control with ethtool

In order to disable receive flow control using ethtool, you must turn off auto-negotiation on the same command line.

For example:

     ethtool -A eth? autoneg off rx off

Unplugging network cable while ethtool -p is running

In kernel versions 2.5.50 and later (including 2.6 kernel), unplugging the network cable while ethtool -p is running will cause the system to
become unresponsive to keyboard commands, except for control-alt-delete. Restarting the system appears to be the only remedy.

MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)

Kernel panics and instability may be observed on any MSI-X hardware if you use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.

Rx Page Allocation Errors

Page allocation failure. order:0 errors may occur under stress with kernels 2.6.25 and above. This is caused by the way the Linux kernel reports this stressed condition.

Network throughput degradation observed with Onboard video versus add-in Video Card on 82579LM Gigabit Network Connection when used with some older kernels.

This issue can be worked around by specifying "pci=nommconf" in the kernel boot parameter or by using another kernel boot parameter "memmap=128M$0x100000000" which marks 128 MB region at 4GB as reserved and therefore OS won't use these RAM pages.

This issue is fixed in kernel version 2.6.21, where the kernel tries to dynamically find out the mmconfig size by looking at the number of buses that the mmconfig segment maps to.

This issue won't be seen on 32bit version of EL5, as in that case, the kernel sees that RAM is located around the 256MB window and avoids using the mmconfig space.

Activity LED blinks unexpectedly

If a system based on the 82577, 82578, or 82579 controller is connected to a hub, the Activity LED will blink for all network traffic present on the hub. Connecting the system to a switch or router will filter out most traffic not addressed to the local port.

Link may take longer than expected

With some Phy and switch combinations, link can take longer than expected. This can be an issue on Linux distributions that timeout when checking for link prior to acquiring a DHCP address; however there is usually a way to work around this (e.g. set LINKDELAY in the interface configuration on RHEL).

Tx flow control is disabled by default on 82577 and 82578-based adapters

Possible performance degradation on certain 82566 and 82577 devices

Internal stress testing with jumbo frames shows the reliability on some 82566 and 82567 devices is improved in certain corner cases by disabling the Early Receive feature. Doing so can impact Tx performance. To reduce the impact, the packet buffer sizes and relevant flow control settings are modified accordingly.

Using the igbvf Base Driver

Overview

Building and Installation

Command Line Parameters

Additional Configurations

Known Issues

Overview

This driver supports upstream kernel versions 2.6.30 (or higher) x86_64.

Supported Operating Systems: SLES 11 SP1 x86_64, RHEL 5.3/5.4 x86_64.

The igbvf driver supports 82576-based virtual function devices that can only be activated on kernels that support SR-IOV. SR-IOV requires the correct platform and OS support.

The igbvf driver requires the igb driver, version 2.0 or later. The igbvf driver supports virtual functions generated by the igb driver with a max_vfs value of 1 or greater. For more information on the max_vfs parameter refer to the section on the the igb driver.

The guest OS loading the igbvf driver must support MSI-X interrupts.

This driver is only supported as a loadable module at this time. Intel is not supplying patches against the kernel source to allow for static linking of the driver. For questions related to hardware requirements, refer to the documentation supplied with your Intel Gigabit adapter. All hardware requirements listed apply to use with Linux.

Instructions on updating ethtool can be found in the section Additional Configurations later in this document.

VLANs: There is a limit of a total of 32 shared VLANs to 1 or more VFs.

Building and Installation

To build a binary RPM* package of this driver, run 'rpmbuild -tb <filename.tar.gz>'. Replace <filename.tar.gz> with the specific filename of the driver.

NOTE: For the build to work properly, the currently running kernel MUST match the version and configuration of the installed kernel sources. If you have just recompiled the kernel reboot the system now.

RPM functionality has only been tested in Red Hat distributions.

  1. Move the base driver tar file to the directory of your choice. For example, use ' /home/username/igbvf or /usr/local/src/igbvf.'.

  2. Untar/unzip the archive:

    tar zxf igbvf-x.x.x.tar.gz

  3. Change to the driver src directory:

    cd igbvf-<x.x.x>/src/

  4. Compile the driver module:

    # make install

    The binary will be installed as:

    /lib/modules/<KERNEL VERSION>/kernel/drivers/net/igbvf/igbvf.[k]o

    The install location listed above is the default location. This may differ for various Linux distributions.

  5. Load the module using either the insmod or modprobe command:

    modprobe igbvf

    insmod igbvf

    Note that for 2.6 kernels the insmod command can be used if the full path to the driver module is specified. For example:

        insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/igbvf/igbvf.ko

    With 2.6 based kernels also make sure that older e1000e drivers are removed from the kernel, before loading the new module:

    rmmod igbvf; modprobe igbvf

  6. Assign an IP address to the interface by entering the following, where <x> is the interface number:

    ifconfig eth<x> <IP_address>

  7. Verify that the interface works. Enter the following, where <IP_address> is the IP address for another machine on the same subnet as the interface that is being tested:

    ping <IP_address>

Troubleshooting: Some systems have trouble supporting MSI and/or MSI-X interrupts. If you believe your system needs to disable this style of interrupt, the driver can be built and installed with the command:

make CFLAGS_EXTRA=-DDISABLE_PCI_MSI install

Normally the driver will generate an interrupt every two seconds, so if you can see that you're no longer getting interrupts in cat /proc/interrupts for the ethX igbvf device, then this workaround may be necessary.

Command Line Parameters

If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:

modprobe igbvf [<option>=<VAL1>,<VAL2>,...]

For example:

modprobe igbvf InterruptThrottleRate=16000,16000

The default value for each parameter is generally the recommended setting, unless otherwise noted.

NOTES:

  • For more information about the InterruptThrottleRate parameter, see the application note at: http://www.intel.com/design/network/applnots/ap450.htm.

  • A descriptor describes a data buffer and attributes related to the data buffer. This information is accessed by the hardware.

Parameter Name Valid Range/Settings Default Description
InterruptThrottleRate
0,1,3,100-100000 (0=off, 1=dynamic, 3=dynamic conservative)
 		 3 The driver can limit the amount of interrupts per second that the adapter will generate for incoming packets. It does this by writing a value to the adapter that is based on the maximum amount of interrupts that the adapter will generate per second.

Setting InterruptThrottleRate to a value greater or equal to 100 will program the adapter to send out a maximum of that many interrupts per second, even if more packets have come in. This reduces interrupt load on the system and can lower CPU utilization under heavy load, but will increase latency as packets are not processed as quickly.

The default behaviour of the driver previously assumed a static InterruptThrottleRate value of 8000, providing a good fallback value for all traffic types, but lacking in small packet performance and latency. The hardware can handle many more small packets per second however, and for this reason an adaptive interrupt moderation algorithm was implemented.

The driver has two adaptive modes (setting 1 or 3) in which it dynamically adjusts the InterruptThrottleRate value based on the traffic that it receives. After determining the type of incoming traffic in the last timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that traffic.

The algorithm classifies the incoming traffic every interval into classes. Once the class is determined, the InterruptThrottleRate value is adjusted to suit that traffic type the best. There are three classes defined: "Bulk traffic", for large amounts of packets of normal size; "Low latency", for small amounts of traffic and/or a significant percentage of small packets; and "Lowest latency", for almost completely small packets or minimal traffic.

In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low latency" or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This default mode is suitable for most applications.

For situations where low latency is vital such as cluster or grid computing, the algorithm can reduce latency even more when InterruptThrottleRate is set to mode 1. In this mode, which operates the same as mode 3, the InterruptThrottleRate will be increased stepwise to 70000 for traffic in class "Lowest latency".

Setting InterruptThrottleRate to 0 turns off any interrupt moderation and may improve small packet latency, but is generally not suitable for bulk throughput traffic

NOTE: Dynamic interrupt throttling is only applicable to adapters operating in MSI or Legacy interrupt mode, using a single receive queue.

NOTE: When igbvf is loaded with default settings and multiple adapters are in use simultaneously, the CPU utilization may increase non-linearly. In order to limit the CPU utilization without impacting the overall throughput, we recommend that you load the driver as follows:

modprobe igbvf InterruptThrottleRate=3000,3000,3000

This sets the InterruptThrottleRate to 3000 interrupts/sec for the first, second, and third instances of the driver. The range of 2000 to 3000 interrupts per second works on a majority of systems and is a good starting point, but the optimal value will be platform-specific. If CPU utilization is not a concern, use default driver settings.

Additional Configurations

Configuring the Driver on Different Distributions

Configuring a network driver to load properly when the system is started is distribution dependent. Typically, the configuration process involves adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other system startup scripts and/or configuration files. Many popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, refer to your distribution documentation. If during this process you are asked for the driver or module name, the name for the Linux Base Driver for the Gigabit Family of Adapters is igbvf.

As an example, if you install the igbvf driver for two Gigabit adapters (eth0 and eth1) and want to set the interrupt mode to MSI-X and MSI respectively, add the following to modules.conf or /etc/modprobe.conf:

alias eth0 igbvf
alias eth1 igbvf
options igbvf InterruptThrottleRate=3,1

Viewing Link Messages

Link messages will not be displayed to the console if the distribution is restricting system messages. In order to see network driver link messages on your console, set dmesg to eight by entering the following:

dmesg -n 8

NOTE: This setting is not saved across reboots.

Jumbo Frames

Jumbo Frames support is enabled by changing the MTU to a value larger than the default of 1500. Use the ifconfig command to increase the MTU size.

For example:

ifconfig eth<x> mtu 9000 up

This setting is not saved across reboots. It can be made permanent if you add:

MTU=9000

to the file /etc/sysconfig/network-scripts/ifcfg-eth<x>. This example applies to the Red Hat distributions; other distributions may store this setting in a different location.

NOTES:

  • To enable Jumbo Frames, increase the MTU size on the interface beyond 1500.

  • The maximum MTU setting for Jumbo Frames is 9216. This value coincides with the maximum Jumbo Frames size of 9234 bytes.

  • Using Jumbo frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.

ethtool

The driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information. ethtool version 3.0 or later is required for this functionality, although we strongly recommend downloading the latest version at:

http://ftp.kernel.org/pub/software/network/ethtool/.

Known Issues/Troubleshooting

NOTE: After installing the driver, if your Intel Network Connection is not working, verify that you have installed the correct driver.

Driver Compilation

When trying to compile the driver by running make install, the following error may occur:

"Linux kernel source not configured - missing version.h"

To solve this issue, create the version.h file by going to the Linux source tree and entering:

make include/linux/version.h.

Multiple Interfaces on Same Ethernet Broadcast Network

Due to the default ARP behavior on Linux, it is not possible to have one system on two IP networks in the same Ethernet broadcast domain (non-partitioned switch) behave as expected. All Ethernet interfaces will respond to IP traffic for any IP address assigned to the system. This results in unbalanced receive traffic.

If you have multiple interfaces in a server, either turn on ARP filtering by entering:

echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
(this only works if your kernel's version is higher than 2.4.5),

NOTE: This setting is not saved across reboots. The configuration change can be made permanent by adding the line:

net.ipv4.conf.all.arp_filter = 1

to the file /etc/sysctl.conf

or,

install the interfaces in separate broadcast domains (either in
different switches or in a switch partitioned to VLANs).

Do Not Use LRO When Routing Packets

Due to a known general compatibility issue with LRO and routing, do not use LRO when routing packets.

Build error with Asianux 3.0 - redefinition of typedef 'irq_handler_t'

Some systems may experience build issues due to redefinition of irq_handler_t. To resolve this issue build the driver (step 4 above) using the command:

make CFLAGS_EXTRA=-DAX_RELEASE_CODE=1 install

MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)

Kernel panics and instability may be observed on any MSI-X hardware if you use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are
encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.

Rx Page Allocation Errors

Page allocation failure. order:0 errors may occur under stress with kernels 2.6.25 and above. This is caused by the way the Linux kernel reports this stressed condition.

Under Redhat 5.4 - System May Crash when Closing Guest OS Window after Loading/Unloading Physical Function (PF) Driver

Do not remove the igbvf driver from Dom0 while Virtual Functions (VFs) are assigned to guests. VFs must first use the xm "pci-detach" command to hot-plug the VF device out of the VM it is assigned to or else shut down the VM.

Unloading Physical Function (PF) Driver Causes System Reboots When VM is Running and VF is Loaded on the VM

Do not unload the PF driver (igb) while VFs are assigned to guests.

Host May Reboot after Removing PF when VF is Active in Guest

Using kernel versions earlier than 3.2, do not unload the PF driver with active VFs. Doing this will cause your VFs to stop working until you reload the PF driver and may cause a spontaneous reboot of your system.

 

Last modified on 11/03/11 4:12p Revision

DOCS/LINUX/index.htm0000755000000000000000000000106311662465060011225 0ustar Intel® Linux Base Driver for Intel Ethernet Adapters /html> DOCS/LINUX/ixgb.htm0000755000000000000000000022676511730102574011063 0ustar Linux Driver for Intel 10GbE Network Connections

Linux* Base Driver for 10 Gigabit Intel® Ethernet Network Connection

NOTES:  This release includes the ixgbe and ixgbevf Linux* Base Drivers for the Intel Ethernet 10 Gigabit Family of Adapters.
 
  • All 82599, X540 and 82598-based 10 Gigabit network connections require the ixgbe driver.
  • The ixgbevf driver supports 82599 and X540-based virtual function devices that can only be activated on kernels that support SR-IOV. SR-IOV requires the correct platform and OS support.

Using the ixgbe base driver

Important Note

Overview

Building and Installation

Command Line Parameters

Additional Configurations

Performance Tuning

Known Issues/Troubleshooting 

Important Note

Warning: The ixgbe driver compiles by default with the LRO (Large Receive Offload) feature enabled. This option offers the lowest CPU utilization for receives, but is completely incompatible with *routing/ip forwarding* and *bridging*. If enabling ip forwarding or bridging is a requirement, it is necessary to disable LRO using compile time options as noted in the LRO section later in this document. The result of not disabling LRO when combined with ip forwarding or bridging can be low throughput or even a kernel panic.

Overview

The Linux* base driver supports the 2.6.x and 3.x kernels, and includes support for any Linux supported system, including Itanium(R)2, x86_64, i686, and PPC.

These drivers are only supported as a loadable module at this time. Intel is not supplying patches against the kernel source to allow for static linking of the driver. A version of the driver may already be included by your distribution and/or the kernel.org kernel. For questions related to hardware requirements, refer to the documentation supplied with your Intel adapter. All hardware requirements listed apply to use with Linux.

The following features are now available in supported kernels:

  • Native VLANs

  • Channel Bonding (teaming)

  • SNMP

  • Generic Receive Offload

  • Data Center Bridging

Channel Bonding documentation can be found in the Linux kernel source: /Documentation/networking/bonding.txt

The driver information previously displayed in the /proc file system is not supported in this release.  Alternatively, you can use ethtool (version 1.6 or later), lspci, and ifconfig to obtain the same information.  Instructions on updating ethtool can be found in the section Additional Configurations later in this document.

The driver in this release is compatible with 82598, 82599 and X540-based Intel Ethernet Network Connections.

For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at:

http://support.intel.com/support/go/network/adapter/proidguide.htm

For the latest Intel network drivers for Linux, refer to the following website. Select the link for your adapter.

http://support.intel.com/support/go/network/adapter/home.htm

SFP+ Devices with Pluggable Optics

82599-BASED ADAPTERS

NOTES:
  • If your 82599-based Intel® Network Adapter came with Intel optics or is an Intel® Ethernet Server Adapter X520-2, then it only supports Intel optics and/or the direct attach cables listed below.
  • When 82599-based SFP+ devices are connected back to back, they should be set to the same Speed setting via ethtool. Results may vary if you mix speed settings.

Supplier            Type                                                     Part Numbers
SR Modules                 
Intel              DUAL RATE 1G/10G SFP+ SR (bailed) AFBR-703SDZ-IN2
Intel              DUAL RATE 1G/10G SFP+ SR (bailed) FTLX8571D3BCV-IT
Intel DUAL RATE 1G/10G SFP+ SR (bailed) AFBR-703SDDZ-IN1
LR Modules                
Intel               DUAL RATE 1G/10G SFP+ LR (bailed) FTLX1471D3BCV-IT
Intel               DUAL RATE 1G/10G SFP+ LR (bailed) AFCT-701SDZ-IN2
Intel DUAL RATE 1G/10G SFP+ LR (bailed) AFCT-701SDDZ-IN1

The following is a list of 3rd party SFP+ modules and direct attach cables that have received some testing. Not all modules are applicable to all devices.

Supplier            Type                                                     Part Numbers
Finisar SFP+ SR bailed, 10g single rate FTLX8571D3BCL
Avago SFP+ SR bailed, 10g single rate AFBR-700SDZ
Finisar SFP+ LR bailed, 10g single rate FTLX1471D3BCL
     
Finisar DUAL RATE 1G/10G SFP+ SR (No Bail) FTLX8571D3QCV-IT
Avago DUAL RATE 1G/10G SFP+ SR (No Bail) AFBR-703SDZ-IN1
Finisar DUAL RATE 1G/10G SFP+ LR (No Bail) FTLX1471D3QCV-IT
Avago DUAL RATE 1G/10G SFP+ LR (No Bail) AFCT-701SDZ-IN1
Finisar 1000BASE-T SFP FCLF8522P2BTL
Avago 1000BASE-T SFP ABCU-5710RZ

82599-based adapters support all passive and active limiting direct attach cables that comply with SFF-8431 v4.1 and SFF-8472 v10.4 specifications.

Laser turns off for SFP+ when ifconfig ethX down

"ifconfig ethX down" turns off the laser for 82599-based SFP+ fiber adapters. "ifconfig ethX up" turns on the laser.

82598-BASED ADAPTERS

NOTES:
  • Intel Ethernet Network Adapters that support removable optical modules only support their original module type (i.e., the Intel 10 Gigabit SR Dual Port Express Module only supports SR optical modules). If you plug in a different type of module, the driver will not load.
  • Hot Swapping/hot plugging optical modules is not supported.
  • Only single speed, 10 gigabit modules are supported.
  • LAN on Motherboard (LOMs) may support DA, SR, or LR modules. Other module types are not supported. Please see your system documentation for details.

The following is a list of SFP+ modules and direct attach cables that have received some testing. Not all modules are applicable to all devices.

Supplier            Type                                                     Part Numbers
Finisar              SFP+ SR bailed, 10g single rate   FTLX8571D3BCL
Avago              SFP+ SR bailed, 10g single rate   AFBR-700SDZ
Finisar              SFP+ LR bailed, 10g single rate FTLX1471D3BCL

82598-based adapters support all passive direct attach cables that comply with SFF-8431 v4.1 and SFF-8472 v10.4 specifications. Active direct attach cables are not supported.

THIRD PARTY OPTIC MODULES AND CABLES REFERRED TO ABOVE ARE LISTED ONLY FOR THE PURPOSE OF HIGHLIGHTING THIRD PARTY SPECIFICATIONS AND POTENTIAL COMPATIBILITY, AND ARE NOT RECOMMENDATIONS OR ENDORSEMENT OR SPONSORSHIP OF ANY THIRD PARTYS PRODUCT BY INTEL. INTEL IS NOT ENDORSING OR PROMOTING PRODUCTS MADE BY ANY THIRD PARTY AND THE THIRD PARTY REFERENCE IS PROVIDED ONLY TO SHARE INFORMATION REGARDING CERTAIN OPTIC MODULES AND CABLES WITH THE ABOVE SPECIFICATIONS. THERE MAY BE OTHER MANUFACTURERS OR SUPPLIERS, PRODUCING OR SUPPLYING OPTIC MODULES AND CABLES WITH SIMILAR OR MATCHING DESCRIPTIONS. CUSTOMERS MUST USE THEIR OWN DISCRETION AND DILIGENCE TO PURCHASE OPTIC MODULES AND CABLES FROM ANY THIRD PARTY OF THEIR CHOICE. CUSTOMERS ARE SOLELY RESPONSIBLE FOR ASSESSING THE SUITABILITY OF THE PRODUCT AND/OR DEVICES AND FOR THE SELECTION OF THE VENDOR FOR PURCHASING ANY PRODUCT. THE OPTIC MODULES AND CABLES REFERRED TO ABOVE ARE NOT WARRANTED OR SUPPORTED BY INTEL. INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF SUCH THIRD PARTY PRODUCTS OR SELECTION OF VENDOR BY CUSTOMERS.

Building and Installation

To build a binary RPM* package of this driver, run 'rpmbuild -tb ixgbe.tar.gz'.

NOTE: For the build to work properly, the currently running kernel MUST match the version and configuration of the installed kernel sources. If you have just recompiled the kernel, reboot the system before building.

RPM functionality has only been tested in Red Hat distributions.

To manually build this driver:

  1. Move the base driver tar file to the directory of your choice. For example, use '/home/username/ixgbe' or '/usr/local/src/ixgbe'.

  2. Untar/unzip the archive:

    tar zxf ixgbe-x.x.x.tar.gz

  3. Change to the driver src directory:

    cd ixgbe-x.x.x/src/

  4. Compile the driver module:

    make install

    The binary will be installed as:

    /lib/modules/[KERNEL_VERSION]/kernel/drivers/net/ixgbe/ixgbe.[k]o

    The install location listed above is the default location. This may differ for various Linux distributions.

  5. Load the module:

    For kernel 2.6.x, use the modprobe command -

          modprobe ixgbe <parameter>=<value>

    Note that for 2.6 kernels the insmod command can be used if the full path to the driver module is specified. For example:

         insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/ixgbe/ixgbe.ko

    With 2.6 based kernels also make sure that older ixgbe drivers are removed from the kernel, before loading the new module:

    rmmod ixgbe; modprobe ixgbe

  6. Assign an IP address to the interface by entering the following, where x is the interface number:

    ifconfig ethX <IP_address> netmask <netmask>

  7. Verify that the interface works. Enter the following, where <IP_address> is the IP address of another machine on the same subnet as the interface that is being tested:

    ping <IP_address>

To build ixgbe driver with DCA

If your kernel supports DCA, the driver will build by default with DCA enabled.

Command Line Parameters

If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:

modprobe ixgbe [<option>=<VAL1>,<VAL2>,...]

For example:

modprobe ixgbe InterruptThrottleRate=16000,16000

The default value for each parameter is generally the recommended setting, unless otherwise noted.

Parameter Name Valid Range/Settings Default Description
RSS - Receive Side Scaling (or multiple queues for receives) 0 - 16

 

 1 0 = disables RSS
1 = enables RSS and sets the descriptor queue count to 16 or the number of
online cpus, whichever is less.
2-16 = enables RSS, with 2-16 queues

RSS also effects the number of transmit queues allocated on 2.6.23 and
newer kernels with CONFIG_NETDEVICES_MULTIQUEUE set in the kernel .config file. CONFIG_NETDEVICES_MULTIQUEUE only exists from 2.6.23 to 2.6.26. Other options enable multiqueue in 2.6.27 and newer kernels.
MQ - Multi Queue 0, 1 1 0 = Disables Multiple Queue support
1 = Enables Multiple Queue support (a prerequisite for RSS)
DCA - Direct Cache Access 0, 1

 

 1 (when IXGBE_DCA is enabled) 0 = Disables DCA support in the driver
1 = Enables DCA support in the driver

See the above instructions for enabling DCA. If the driver is enabled for
DCA this parameter allows load-time control of the feature.
IntMode 0-2 (0 = Legacy Int, 1 = MSI and 2 = MSIX) 2 IntMode controls allow load time control over the type of interrupt registered for by the driver. MSI-X is required for multiple queue support, and some kernels and combinations of kernel .config options will force a lower level of interrupt support. 'cat /proc/interrupts' will show different values for each type of interrupt.
InterruptThrottleRate 956-488281 (0=off, 1=dynamic) 1 Interrupt Throttle Rate (interrupts/sec). The ITR parameter controls how many interrupts each interrupt vector can generate per second. Increasing ITR lowers latency at the cost of increased CPU utilization, though it may help throughput in some circumstances.

1 = Dynamic mode attempts to moderate interrupts per vector while maintaining very low latency. This can sometimes cause extra CPU utilization. If planning on deploying ixgbe in a latency sensitive environment please consider this parameter.

0 = Setting InterruptThrottleRate to 0 turns off any interrupt moderation and may improve small packet latency, but is generally not suitable for bulk throughput traffic due to the increased cpu utilization of the higher interrupt rate. Please note that on 82599 and X540-based adapters, disabling InterruptThrottleRate will also result in the driver disabling HW RSC. On 82598-based adapters, disabling InterruptThrottleRate will also result in disabling LRO (Large Receive Offloads).
LLI (Low Latency Interrupts)

 		     LLI allows for immediate generation of an interrupt upon processing receive
packets that match certain criteria as set by the parameters described below.
LLI parameters are not enabled when Legacy interrupts are used. You must be
using MSI or MSI-X (see cat /proc/interrupts) to successfully use LLI.
LLIPort 0 - 65535 0 (disabled) LLI is configured with the LLIPort command-line parameter, which specifies
which TCP port should generate Low Latency Interrupts.

For example, using LLIPort=80 would cause the hardware to generate an
immediate interrupt upon receipt of any packet sent to TCP port 80 on the
local machine.
CAUTION: Enabling LLI can result in an excessive number of interrupts/second that may cause problems with the system and in some cases may cause a kernel panic.
    LLIPush       0-1 0 (disabled) LLIPush can be set to be enabled or disabled (default). It is most effective in an environment with many small transactions.
NOTE: Enabling LLIPush may allow a denial of service attack.
    LLISize       0-1500 0 (disabled) LLISize causes an immediate interrupt if the board receives a packet smaller than the specified size.
LLIEType 0-x8fff 0 (disabled) Low Latency Interrupt Ethernet Protocol Type.
LLIVLANP 0-7 0 (disabled) Low Latency Interrupt on VLAN priority threshold.
Flow Control    

Ethernet Flow Control (IEEE 802.3x) can be configured with ethtool to enable receiving and transmitting pause frames for ixgbe. When tx is enabled, PAUSE frames are generated when the receive packet buffer crosses a predefined threshold. When rx is enabled, the transmit unit will halt for the time delay specified when a PAUSE frame is received.

Flow Control is enabled by default. If you want to disable a flow control capable link partner, use ethtool:

          ethtool -A eth? autoneg off rx off tx off

NOTE: For 82598 backplane cards entering 1 gig mode, flow control default behavior is changed to off.  Flow control in 1 gig mode on these devices can lead to Tx hangs.
Intel® Ethernet Flow Director    
NOTE: Flow director parameters are only supported on kernel versions 2.6.30 or later.

Supports advanced filters that direct receive packets by their flows to
different queues. Enables tight control on routing a flow in the platform. Matches flows and CPU cores for flow affinity. Supports multiple parameters for flexible flow classification and load balancing.

Flow director is enabled only if the kernel is multiple TX queue capable.

An included script (set_irq_affinity.sh) automates setting the IRQ to CPU affinity.

You can verify that the driver is using Flow Director by looking at the counter in ethtool: fdir_miss and fdir_match.

Other ethtool Commands:

To enable Flow Director

ethtool -K ethX ntuple on

To add a filter

Use -U switch. e.g., ethtool -U ethX flow-type tcp4 src-ip 0x178000a action 1

To see the list of filters currently present:

ethtool -u ethX

Perfect Filter: Perfect filter is an interface to load the filter table that funnels all flow
into queue_0 unless an alternative queue is specified using "action". In that
case, any flow that matches the filter criteria will be directed to the
appropriate queue.

Support for Virtual Function (VF) is via the user-data field. You must update
to the version of ethtool built for the 2.6.40 kernel. Perfect Filter is
supported on all kernels 2.6.30 and later. Rules may be deleted from the table
itself. This is done via "ethtool -U ethX delete N" where N is the rule number
to be deleted.

NOTE: Flow Director Perfect Filters can run in single queue mode, when SR-IOV is enabled, or when DCB is enabled.

If the queue is defined as -1, filter will drop matching packets.

To account for filter matches and misses, there are two stats in ethtool: fdir_match and fdir_miss. In addition, rx_queue_N_packets shows the number of packets processed by the Nth queue.

NOTE: Receive Packet Steering (RPS) and Receive Flow Steering (RFS) are not compatible with Flow Director. IF Flow Director is enabled, these will be disabled.
NOTE: For VLAN Masks only 4 masks are supported.
NOTE: Once a rule is defined, you must supply the same fields and masks (if masks are specified).

Support for UDP RSS
This feature adds an ON/OFF switch for hashing over certain flow types. You
can't turn on anything other than UDP. The default setting is disabled. We only support enabling/disabling hashing on ports for UDP over IPv4 (udp4) or IPv6 (udp6).

NOTE: Fragmented packets may arrive out of order when RSS UDP support is configured.

Supported Ethtool Commands and Options:

-n --show-nfc
Retrieves the receive network flow classification configurations.

rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6
Retrieves the hash options for the specified network traffic type.

-N --config-nfc
Configures the receive network flow classification.

rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6
m|v|t|s|d|f|n|r...
Configures the hash options for the specified network traffic type.

udp4 UDP over IPv4
udp6 UDP over IPv6

f Hash on bytes 0 and 1 of the Layer 4 header of the rx packet.
n Hash on bytes 2 and 3 of the Layer 4 header of the rx packet.

The following is an example using udp4 (UDP over IPv4):

To include UDP port numbers in RSS hashing run:
ethtool -N ethX rx-flow-hash udp4 sdfn

To exclude UDP port numbers from RSS hashing run:
ethtool -N ethX rx-flow-hash udp4 sd

To display UDP hashing current configuration run:
ethtool -n ethX rx-flow-hash udp4

The results of running that call will be the following, if UDP hashing is
enabled:
UDP over IPV4 flows use these fields for computing Hash flow key:
IP SA
IP DA
L4 bytes 0 & 1 [TCP/UDP src port]
L4 bytes 2 & 3 [TCP/UDP dst port]

The results if UDP hashing is disabled would be:
UDP over IPV4 flows use these fields for computing Hash flow key:
IP SA
IP DA

The following three parameters impact Flow Director:
FdirMode 0-2 (0=off, 1=ATR, 2=Perfect filter mode) 1 (ATR) Flow Director filtering modes.
FdirPballoc 0-2 (0=64k, 1=128k, 2=256k) 0 (64k) Flow Director allocated packet buffer size.
AtrSampleRate 1-100 20 Software ATR Tx packet sample rate. For example, when set to 20, every 20th packet, looks to see if the packet will create a new flow.
max_vfs 1-63 0 If the value is greater than 0 it will also force the VMDq parameter to be 1 or more.

This parameter adds support for SR-IOV. It causes the driver to spawn up to max_vfs worth of virtual function.

The parameters for the driver are referenced by position. So, if you have a dual port 82599 or X540-based adapter and you want N virtual functions per port, you must specify a number for each port with each parameter separated by a comma.

For example:
insmod ixgbe max_vfs=63,63

NOTE: If both 82598 and 82599 or X540-based adapters are installed on the same machine, you must be careful in loading the driver with the parameters. Depending on system configuration, number of slots, etc. its impossible to predict in all cases where the positions would be on the command line and the user will have to specify zero in those positions occupied by an 82598 port.
L2LBen 0 = disable, 1 = enable (default) 1 (enable)

This parameter controls the internal switch (L2 loopback between pf and vf). By default the switch is enabled.
LRO 0(off), 1(on) 1 (on) Enable/disable Large Receive Offload.

Additional Configurations

Configuring the Driver on Different Distributions

Configuring a network driver to load properly when the system is started is distribution dependent. Typically, the configuration process involves adding an alias line to /etc/modules.conf or etc/modprobe.conf, as well as editing other system startup scripts and/or configuration files. Many popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, refer to your distribution documentation. If during this process you are asked for the driver or module name, the name for the Linux Base Driver for the 10 Gigabit Family of Adapters is ixgbe.

Viewing Link Messages

Link messages will not be displayed to the console if the distribution is restricting system messages. In order to see network driver link messages on your console, set dmesg to eight by entering the following:

     dmesg -n 8

NOTE: This setting is not saved across reboots.

Jumbo Frames

The driver supports Jumbo Frames for all adapters. Jumbo Frames support is enabled by changing the MTU to a value larger than the default of 1500. The maximum value for the MTU is 16110. Use the ifconfig command to increase the MTU size. For example, enter the following where <x> is the interface number:

ifconfig ethX mtu 9000 up

The maximum MTU setting for Jumbo Frames is 16110. This value coincides with the maximum Jumbo Frames size of 16128. This driver will attempt to
use multiple page sized buffers to receive each jumbo packet. This should help to avoid buffer starvation issues when allocating receive packets.

ethtool

The driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information.  The latest ethtool version is required for this functionality.

The latest release of ethtool can be found at: http://ftp.kernel.org/pub/software/network/ethtool/.

NAPI

NAPI (Rx polling mode) is supported in the ixgbe driver. NAPI is enabled or disabled based on the configuration of the kernel. To override the default, use the following compile-time flags.

You can tell if NAPI is enabled in the driver by looking at the version number of the driver. It will contain the string -NAPI if NAPI is enabled.

To enable NAPI, compile the driver module, passing in a configuration option:

     make CFLAGS_EXTRA=-DIXGBE_NAPI install

NOTE: This will not do anything if NAPI is disabled in the kernel.

To disable NAPI, compile the driver module, passing in a configuration option:

     make CFLAGS_EXTRA=-DIXGBE_NO_NAPI install

See ftp://robur.slu.se/pub/Linux/net-development/NAPI/usenix-paper.tgz for more information on NAPI.

LRO

Large Receive Offload (LRO) is a technique for increasing inbound throughput of high-bandwidth network connections by reducing CPU overhead. It works by aggregating multiple incoming packets from a single stream into a larger buffer before they are passed higher up the networking stack, thus reducing the number of packets that have to be processed. LRO combines multiple Ethernet frames into a single receive in the stack, thereby potentially decreasing CPU utilization for receives.

IXGBE_NO_LRO is a compile time flag. The user can enable it at compile time to remove support for LRO from the driver. The flag is used by adding
CFLAGS_EXTRA="-DIXGBE_NO_LRO" to the make file when it's being compiled.

make CFLAGS_EXTRA="-DIXGBE_NO_LRO" install

You can verify that the driver is using LRO by looking at these counters in ethtool:

lro_flushed - the total number of receives using LRO.

lro_aggregated - counts the total number of Ethernet packets that were combined.

NOTE: IPv6 and UDP are not supported by LRO.

HW RSC

82599 and X540-based adapters support HW based receive side coalescing (RSC) which can merge multiple frames from the same IPv4 TCP/IP flow into a single structure that can span one or more descriptors. It works similarly to SW Large receive offload technique. By default HW RSC is enabled and SW LRO can not be used for 82599 and X540-based adapters unless HW RSC is disabled.

IXGBE_NO_HW_RSC is a compile time flag. The user can enable it at compile time to remove support for HW RSC from the driver. The flag is used by adding CFLAGS_EXTRA="-DIXGBE_NO_HW_RSC" to the make file when it's being compiled.

      make CFLAGS_EXTRA="-DIXGBE_NO_HW_RSC" install

You can verify that the driver is using HW RSC by looking at the counter in ethtool:

      hw_rsc_count - counts the total number of Ethernet packets that were being combined.

rx_dropped_backlog

When in a non-Napi (or Interrupt) mode, this counter indicates that the stack is dropping packets. There is an adjustable parameter in the stack that allows you to adjust the amount of backlog. We recommend increasing the netdev_max_backlog if the counter goes up.

# sysctl -a |grep netdev_max_backlog

net.core.netdev_max_backlog = 1000

# sysctl -e net.core.netdev_max_backlog=10000

net.core.netdev_max_backlog = 10000

Flow Control

Flow control is enabled by default. If you want to disable a flow control capable link partner, use ethtool:

    ethtool -A eth? autoneg off rx off tx off

MAC and VLAN anti-spoofing feature

When a malicious driver attempts to send a spoofed packet, it is dropped by the hardware and not transmitted. An interrupt is sent to the PF driver notifying it of the spoof attempt.
When a spoofed packet is detected the PF driver will send the following message to the system log (displayed by the "dmesg" command):

ixgbe ethX: ixgbe_spoof_check: n spoofed packets detected

Where x=the PF interface#   n=the VF that attempted to do the spoofing.

Setting MAC Address, VLAN and Rate Limit Using IProute2 Tool

You can set a MAC address of a Virtual Function (VF), a default VLAN and the rate limit using the IProute2 tool. Download the latest version of the iproute2 tool from Sourceforge if your version does not have all the features you require.

(WoL) Wake on LAN Support

Some adapters do not support Wake on LAN. To determine if your adapter supports Wake on LAN, run

ethtool ethX

Performance Tuning

An excellent article on performance tuning can be found at:

http://www.redhat.com/promo/summit/2008/downloads/pdf/Thursday/Mark_Wagner.pdf

Known Issues/Troubleshooting

NOTE: After installing the driver, if your Intel Ethernet Network Connection is not working, verify that you have installed the correct driver.

MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)

Kernel panics and instability may be observed on any MSI-X hardware if you use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.

Driver Compilation

When trying to compile the driver by running make install, the following error may occur:  "Linux kernel source not configured - missing version.h"

To solve this issue, create the version.h file by going to the Linux source tree and entering:

make include/linux/version.h

Do Not Use LRO When Routing or Bridging Packets

Due to a known general compatibility issue with LRO and routing, do not use LRO when routing or bridging packets.

LRO and iSCSI Incompatibility

LRO is incompatible with iSCSI target or initiator traffic. A panic may occur when iSCSI traffic is received through the ixgbe driver with LRO enabled. To workaround this, the driver should be built and installed with:

# make CFLAGS_EXTRA=-DIXGBE_NO_LRO install

Performance Degradation with Jumbo Frames

Degradation in throughput performance may be observed in some Jumbo frames environments. If this is observed, increasing the application's socket buffer size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help. See the specific application manual and /usr/src/linux*/Documentation/networking/ip-sysctl.txt for more details.

Multiple Interfaces on Same Ethernet Broadcast Network

Due to the ARP behavior on Linux, it is not possible to have one system on two IP networks in the same Ethernet broadcast domain (non-partitioned switch) behave as expected. All Ethernet interfaces will respond to IP traffic for any IP address assigned to the system. This results in unbalanced receive traffic.

If you have multiple interfaces in a server, either turn on ARP filtering by entering:

     echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter

(this only works if your kernel's version is higher than 2.4.5), or install the interfaces in separate broadcast domains (either in different switches or in a switch partitioned to VLANs).

UDP Stress Test Dropped Packet Issue

Under small packets UDP stress test with 10GbE driver, the Linux system may drop UDP packets due to the fullness of socket buffers. You may want to change the driver's Flow Control variables to the minimum value for controlling packet reception.

Or you can increase the kernel's default buffer sizes for UDP by changing the values in

/proc/sys/net/core/rmem_default and rmem_max

Unplugging network cable while ethtool -p is running

In kernel versions 2.5.50 and later (including 2.6 kernel), unplugging the network cable while ethtool -p is running will cause the system to become unresponsive to keyboard commands, except for control-alt-delete. Restarting the system appears to be the only remedy.

Cisco Catalyst 4948-10GE port resets may cause switch to shut down ports

82598-based hardware can re-establish link quickly and when connected to some switches, rapid resets within the driver may cause the switch port to become
isolated due to "link flap". This is typically indicated by a yellow instead of a green link light. Several operations may cause this problem, such as repeatedly running ethtool commands that cause a reset.

A potential workaround is to use the Cisco IOS command "no errdisable detect cause all" from the Global Configuration prompt which enables the switch to keep the interfaces up, regardless of errors.

Installing Red Hat Enterprise Linux 4.7, 5.1, or 5.2 with an Intel(R) 10 Gigabit AT Server Adapter may cause kernel panic

A known issue may cause a kernel panic or hang after installing an 82598AT-based Intel(R) 10 Gigabit AT Server Adapter in a Red Hat Enterprise Linux 4.7, 5.1, or 5.2 system. The ixgbe driver for both the install kernel and the runtime kernel can create this panic if the 82598AT adapter is installed. Red Hat may release a security update that contains a fix for the panic that you can download using RHN (Red Hat Network) or Intel recommends that you install the ixgbe-1.3.31.5 driver or newer BEFORE installing the hardware.

Rx Page Allocation Errors

Page allocation failure. order:0 errors may occur under stress with kernels 2.6.25 and above. This is caused by the way the Linux kernel reports this stressed condition.

DCB: Generic segmentation offload on causes bandwidth allocation issues

In order for DCB to work correctly, GSO (Generic Segmentation Offload aka software TSO) must be disabled using ethtool. By default since the hardware supports TSO (hardware offload of segmentation) GSO will not be running. The GSO state can be queried with ethtool using ethtool -k ethX.

When using 82598-based network connections, ixgbe driver only supports 16 queues on a platform with more than 16 cores

Due to known hardware limitations, RSS can only filter in a maximum of 16 receive queues.

82599 and X540-based network connections support up to 64 queues.

Disable GRO when routing/bridging

Due to a known kernel issue, GRO must be turned off when routing/bridging. GRO can be turned off via ethtool.

     ethtool -K ethX gro off

     where ethX is the ethernet interface you're trying to modify.

Lower than expected performance on dual port and quad port 10GbE devices

Some PCI-E x8 slots are actually configured as x4 slots. These slots have insufficient bandwidth for full 10Gbe line rate with dual port and quad port 10GbE devices. The driver can detect this situation and will write the following message in the system log: PCI-Express bandwidth available for this card is not sufficient for optimal performance. For optimal performance a x8 PCI-Express slot is required.

If this error occurs, moving your adapter to a true x8 slot will resolve the issue.

ethtool may incorrectly display SFP+ fiber module as Direct Attached cable

Due to kernel limitations, port type can only be correctly displayed on kernel 2.6.33 or greater.

Under Redhat 5.4 - System May Crash when Closing Guest OS Window after Loading/Unloading Physical Function (PF) Driver

Do not remove the ixgbe driver from Dom0 while Virtual Functions (VFs) are assigned to guests. VFs must first use the xm "pci-detach" command to hot-plug the VF device out of the VM it is assigned to or else shut down the VM.

Unloading Physical Function (PF) Driver Causes System Reboots When VM is Running and VF is Loaded on the VM

Do not unload the PF driver (ixgbe) while VFs are assigned to guests.

Running ethtool -t ethX command causes break between PF and test client

When there are active VFs, "ethtool -t" will only run the link test. The driver will also log in syslog that VFs should be shut down to run a full diags test.

SLES10 SP3 random system panic when reloading driver

This is a known SLES-10 SP3 issue. After requesting interrupts for MSI-X vectors, system may panic.

Currently the only known workaround is to build the drivers with CFLAGS_EXTRA=-DDISABLE_PCI_MSI if the driver need to be loaded/unloaded. Otherwise the driver can be loaded once and will be safe, but unloading it will lead to the issue.

Enabling SR-IOV in a 32-bit or 64-bit Microsoft* Windows* Server 2008/R2 Guest OS using Intel® 82576-based GbE, Intel® 82599 or X540-based 10GbE controller under KVM

KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM. This includes traditional PCIe devices, as well as SR-IOV-capable devices using Intel 82576-based and 82599 or X540-based controllers.

While direct assignment of a PCIe device or an SR-IOV Virtual Function (VF) to a Linux-based VM running 2.6.32 or later kernel works fine, there is a known issue with Microsoft Windows Server 2008/R2 VM that results in a "yellow bang" error. This problem is within the KVM VMM itself, not the Intel driver, or the SR-IOV logic of the VMM, but rather that KVM emulates an older CPU model for the guests, and this older CPU model does not support MSI-X interrupts, which is a requirement for Intel SR-IOV.

If you wish to use the Intel 82576, 82599 or X540-based controllers in SR-IOV mode with KVM and a Microsoft Windows Server 2008/R2 guest try the following workaround. The workaround is to tell KVM to emulate a different model of CPU when using qemu to create the KVM guest:

"-cpu qemu64,model=13"

Loading ixgbe driver in 3.2.x and above kernels displays kernel tainted message

Due to recent kernel changes, loading an out of tree driver will cause the kernel to be tainted.

Unable to obtain DHCP lease on boot with RedHat

For configurations where the auto-negotiation process takes more than 5 seconds, the boot script may fail with the following message:

ethX: failed. No link present. Check cable?

If this error appears even though the presence of a link can be confirmed using ethtool ethX, try setting

LINKDELAY=5 in /etc/sysconfig/network-scripts/ifcfg-ethX.

NOTE: Link time can take up to 30 seconds. Adjust LINKDELAY value accordingly.

Host may Reboot after Removing PF when VF is Active in Guest

Using kernel versions earlier than 3.2, do not unload the PF driver with active VFs. Doing this will cause your VFs to stop working until you reload the PF driver and may cause a spontaneous reboot of your system.

Support

For general information, go to the Intel support website at:

    www.intel.com/support/

If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information related to the issue to linux.nics@intel.com.

Using the ixgbevf Base Driver

Overview

Building and Installation

Command Line Parameters

Additional Configurations

Known Issues

Overview

This driver supports upstream kernel versions 2.6.30 (or higher) x86_64.

Supported Operating Systems: SLES 11 SP1 x86_64, RHEL 5.3/5.4 x86_64.

The ixgbevf driver supports 82599 and X540-based virtual function devices that can only be activated on kernels that support SR-IOV. SR-IOV requires the correct platform and OS support.

The ixgbevf driver requires the ixgbe driver, version 2.0 or later. The ixgbevf driver supports virtual functions generated by the ixgbe driver with a max_vfs value of 1 or greater. For more information on the max_vfs parameter refer to the section on the the ixgbe driver.

The guest OS loading the ixgbevf driver must support MSI-X interrupts.

This driver is only supported as a loadable module at this time. Intel is not supplying patches against the kernel source to allow for static linking of the driver. For questions related to hardware requirements, refer to the documentation supplied with your Intel Gigabit adapter. All hardware requirements listed apply to use with Linux.

Instructions on updating ethtool can be found in the section Additional Configurations later in this document.

VLANs: There is a limit of a total of 64 shared VLANs to 1 or more VFs.

Building and Installation

To build a binary RPM* package of this driver, run 'rpmbuild -tb <filename.tar.gz>'. Replace <filename.tar.gz> with the specific filename of the driver.

NOTE: For the build to work properly, the currently running kernel MUST match the version and configuration of the installed kernel sources. If you have just recompiled the kernel reboot the system now.

RPM functionality has only been tested in Red Hat distributions.

  1. Move the base driver tar file to the directory of your choice. For example, use ' /home/username/ ixgbevf or /usr/local/src/ ixgbevf.'.

  2. Untar/unzip the archive:

    tar zxf ixgbevf-x.x.x.tar.gz

  3. Change to the driver src directory:

    cd   ixgbevf-<x.x.x>/src/

  4. Compile the driver module:

    # make install

    The binary will be installed as:

    /lib/modules/<KERNEL VERSION>/kernel/drivers/net/ixgbevf/ixgbevf.[k]o

    The install location listed above is the default location. This may differ for various Linux distributions.

  5. Load the module using either the insmod or modprobe command:

    modprobe ixgbevf

    insmod ixgbevf

    Note that for 2.6 kernels the insmod command can be used if the full path to the driver module is specified. For example:

        insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/ixgbevf/ixgbevf.ko

    With 2.6 based kernels also make sure that older e1000e drivers are removed from the kernel, before loading the new module:

    rmmod ixgbevf; modprobe ixgbevf

  6. Assign an IP address to the interface by entering the following, where <x> is the interface number:

    ifconfig eth<x> <IP_address>

  7. Verify that the interface works. Enter the following, where <IP_address> is the IP address for another machine on the same subnet as the interface that is being tested:

    ping <IP_address>

Command Line Parameters

If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:

modprobe ixgbevf [<option>=<VAL1>,<VAL2>,...]

For example:

modprobe ixgbevf InterruptThrottleRate=16000,16000

The default value for each parameter is generally the recommended setting, unless otherwise noted.

NOTES:

  • For more information about the InterruptThrottleRate parameter, see the application note at: http://www.intel.com/design/network/applnots/ap450.htm.

  • A descriptor describes a data buffer and attributes related to the data buffer. This information is accessed by the hardware.

Parameter Name Valid Range/Settings Default Description
InterruptThrottleRate
0,1,956-488281 (0=off, 1=dynamic)
 		 8000 The driver can limit the amount of interrupts per second that the adapter will generate for incoming packets. It does this by writing a value to the adapter that is based on the maximum amount of interrupts that the adapter will generate per second.

Setting InterruptThrottleRate to a value greater or equal to 100 will program the adapter to send out a maximum of that many interrupts per second, even if more packets have come in. This reduces interrupt load on the system and can lower CPU utilization under heavy load, but will increase latency as packets are not processed as quickly.

The default behaviour of the driver previously assumed a static InterruptThrottleRate value of 8000, providing a good fallback value for all traffic types, but lacking in small packet performance and latency. The hardware can handle many more small packets per second however, and for this reason an adaptive interrupt moderation algorithm was implemented.

The driver has one adaptive mode (setting 1) in which it dynamically adjusts the InterruptThrottleRate value based on the traffic that it receives. After determining the type of incoming traffic in the last timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that traffic.

The algorithm classifies the incoming traffic every interval into classes. Once the class is determined, the InterruptThrottleRate value is adjusted to suit that traffic type the best. There are three classes defined: "Bulk traffic", for large amounts of packets of normal size; "Low latency", for small amounts of traffic and/or a significant percentage of small packets; and "Lowest latency", for almost completely small packets or minimal traffic.

In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low latency" or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This default mode is suitable for most applications.

For situations where low latency is vital such as cluster or grid computing, the algorithm can reduce latency even more when InterruptThrottleRate is set to mode 1. In this mode, the InterruptThrottleRate will be increased stepwise to 70000 for traffic in class "Lowest latency".

Setting InterruptThrottleRate to 0 turns off any interrupt moderation and may improve small packet latency, but is generally not suitable for bulk throughput traffic

NOTE: Dynamic interrupt throttling is only applicable to adapters operating in MSI or Legacy interrupt mode, using a single receive queue.

NOTE: When ixgbevf is loaded with default settings and multiple adapters are in use simultaneously, the CPU utilization may increase non-linearly. In order to limit the CPU utilization without impacting the overall throughput, we recommend that you load the driver as follows:

modprobe ixgbevf InterruptThrottleRate=3000,3000,3000

This sets the InterruptThrottleRate to 3000 interrupts/sec for the first, second, and third instances of the driver. The range of 2000 to 3000 interrupts per second works on a majority of systems and is a good starting point, but the optimal value will be platform-specific. If CPU utilization is not a concern, use default driver settings.

Additional Configurations

Configuring the Driver on Different Distributions

Configuring a network driver to load properly when the system is started is distribution dependent. Typically, the configuration process involves adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other system startup scripts and/or configuration files. Many popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, refer to your distribution documentation. If during this process you are asked for the driver or module name, the name for the Linux Base Driver for the Gigabit Family of Adapters is ixgbevf.

As an example, if you install the ixgbevf driver for two Gigabit adapters (eth0 and ethX) and want to set the interrupt mode to MSI-X and MSI respectively, add the following to modules.conf or /etc/modprobe.conf:

alias eth0 ixgbevf
alias eth1 ixgbevf
options ixgbevf InterruptThrottleRate=3,1

Viewing Link Messages

Link messages will not be displayed to the console if the distribution is restricting system messages. In order to see network driver link messages on your console, set dmesg to eight by entering the following:

dmesg -n 8

NOTE: This setting is not saved across reboots.

ethtool

The driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information. ethtool version 3.0 or later is required for this functionality, although we strongly recommend downloading the latest version at:

http://ftp.kernel.org/pub/software/network/ethtool/

MACVLAN

ixgbevf supports MACVLAN on those kernels that have the feature included. Kernel support for MACVLAN can be tested by checking if the MACVLAN driver is loaded. The user can run 'lsmod | grep macvlan' to see if the MACVLAN driver is loaded or run 'modprobe macvlan' to try to load the MACVLAN driver.

It may be necessary to update to a recent release of the iproute2 package to get support of MACVLAN via the 'ip' command.

Known Issues/Troubleshooting

NOTE: After installing the driver, if your Intel Network Connection is not working, verify that you have installed the correct driver.

Driver Compilation

When trying to compile the driver by running make install, the following error may occur:

"Linux kernel source not configured - missing version.h"

To solve this issue, create the version.h file by going to the Linux source tree and entering:

make include/linux/version.h.

Multiple Interfaces on Same Ethernet Broadcast Network

Due to the default ARP behavior on Linux, it is not possible to have one system on two IP networks in the same Ethernet broadcast domain (non-partitioned switch) behave as expected. All Ethernet interfaces will respond to IP traffic for any IP address assigned to the system. This results in unbalanced receive traffic.

If you have multiple interfaces in a server, either turn on ARP filtering by entering:

echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter

(this only works if your kernel's version is higher than 2.4.5)

NOTE: This setting is not saved across reboots. The configuration change can be made permanent by adding the line:

net.ipv4.conf.all.arp_filter = 1

to the file /etc/sysctl.conf

or,

install the interfaces in separate broadcast domains (either in different switches or in a switch partitioned to VLANs).

Build error with Asianux 3.0 - redefinition of typedef 'irq_handler_t'

Some systems may experience build issues due to redefinition of irq_handler_t. To resolve this issue build the driver (step 4 above) using the command:

make CFLAGS_EXTRA=-DAX_RELEASE_CODE=1 install

MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)

Kernel panics and instability may be observed on any MSI-X hardware if you use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.

Rx Page Allocation Errors

Page allocation failure. order:0 errors may occur under stress with kernels 2.6.25 and above. This is caused by the way the Linux kernel reports this stressed condition.

Host may Reboot after Removing PF when VF is Active in Guest

Using kernel versions earlier than 3.2, do not unload the PF driver with active VFs. Doing this will cause your VFs to stop working until you reload the PF driver and may cause a spontaneous reboot of your system.

Support

For general information, go to the Intel support website at:

    www.intel.com/support/

If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information related to the issue to linux.nics@intel.com.

Last modified on 11/10/11 2:04p 10/22/04 9:45a

DOCS/LINUX/legaldis.htm0000755000000000000000000000205611701323454011677 0ustar Legal Information

Copyright and Legal Disclaimers

Copyright © 2002 - 2012 Intel Corporation. All rights reserved.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein.

Intel, Itanium, and Pentium are trademarks of Intel Corporation in the U.S. and other countries.

*Other names and brands may be claimed as the property of others.

Warranty Information

Software License

 

Last modified on 1/25/11 10:21p Revision DOCS/LINUX/license.htm0000755000000000000000000003527311654245266011557 0ustar Software License

INTEL SOFTWARE LICENSE AGREEMENT

IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.

Do not copy, install, or use this software and any associated materials (collectively, the “Software”) provided under this license agreement (“Agreement”) until you have carefully read the following terms and conditions.

By copying, installing, or otherwise using the Software, you agree to be bound by the terms of this Agreement. If you do not agree to the terms of this Agreement, do not copy, install, or use the Software.

LICENSES:

Please Note:

  • If you are a network or system administrator, the “Site License” below shall apply to you.
  • If you are an end user, the “Single User License” shall apply to you.
  • If you are an original equipment manufacturer (OEM), the “OEM License” shall apply to you.

SITE LICENSE: You may copy the Software onto your organization’s computers for your organization’s use, and you may make a reasonable number of back-up copies of the Software, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual ("emulated") devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

SINGLE USER LICENSE: You may copy the Software onto a single computer for your personal use, and you may make one back-up copy of the Software, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual (“emulated”) devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

OEM LICENSE: You may reproduce and distribute the Software only as an integral part of or incorporated in your product, as a standalone Software maintenance update for existing end users of your products, excluding any other standalone products, or as a component of a larger Software distribution, including but not limited to the distribution of an installation image or a Guest Virtual Machine image, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual (“emulated”) devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. You may only distribute the Software to your customers pursuant to a written license agreement. Such license agreement may be a "break-the-seal" license agreement. At a minimum such license shall safeguard Intel's ownership rights to the Software.
  6. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

LICENSE RESTRICTIONS. You may NOT: (i) use or copy the Materials except as provided in this Agreement; (ii) rent or lease the Materials to any third party; (iii) assign this Agreement or transfer the Materials without the express written consent of Intel; (iv) modify, adapt, or translate the Materials in whole or in part except as provided in this Agreement; (v) reverse engineer, decompile, or disassemble the Materials; (vi) attempt to modify or tamper with the normal function of a license manager that regulates usage of the Materials; (vii) distribute, sublicense or transfer the Source Code form of any components of the Materials, Redistributables and Sample Source and derivatives thereof to any third party except as provided in this Agreement.

NO OTHER RIGHTS. No rights or licenses are granted by Intel to you, expressly or by implication, with respect to any proprietary information or patent, copyright, mask work, trademark, trade secret, or other intellectual property right owned or controlled by Intel, except as expressly provided in this Agreement. Except as expressly provided herein, no license or right is granted to you directly or by implication, inducement, estoppel, or otherwise. Specifically, Intel grants no express or implied right to you under Intel patents, copyrights, trademarks, or other intellectual property rights.

OWNERSHIP OF SOFTWARE AND COPYRIGHTS. The Software is licensed, not sold. Title to all copies of the Software remains with Intel. The Software is copyrighted and protected by the laws of the United States and other countries and international treaty provisions. You may not remove any copyright notices from the Software. You agree to prevent any unauthorized copying of the Software. Intel may make changes to the Software, or to items referenced therein, at any time without notice, but is not obligated to support or update the Software. You may transfer the Software only if the recipient agrees to be fully bound by these terms and if you retain no copies of the Software.

ADDITIONAL TERMS FOR PRE-RELEASE SOFTWARE. If the Software you are installing or using under this Agreement is pre-commercial release or is labeled or otherwise represented as “alpha-“ or “beta-“ versions of the Software ("pre-release Software"), then the following terms apply.

To the extent that any provision in this Section conflicts with any other term(s) or condition(s) in this Agreement with respect to pre-release Software, this Section shall supersede the other term(s) or condition(s), but only to the extent necessary to resolve the conflict.
You understand and acknowledge that the Software is pre-release Software, does not represent the final Software from Intel, and may contain errors and other problems that could cause data loss, system failures, or other errors. The pre-release Software is provided to you "as-is" and Intel disclaims any warranty or liability to you for any damages that arise out of the use of the pre-release Software.
You acknowledge that Intel has not promised that pre-release Software will be released in the future, that Intel has no express or implied obligation to you to release the pre-release Software and that Intel may not introduce Software that is compatible with the pre-release Software. You acknowledge that the entirety of any research or development you perform that is related to the pre-release Software or to any product making use of or associated with the pre-release Software is done at your own risk.
If Intel has provided you with pre-release Software pursuant to a separate written agreement, your use of the pre-release Software is also governed by such agreement.

LIMITED MEDIA WARRANTY. If the Software has been delivered by Intel on physical media, Intel warrants the media to be free from material physical defects for a period of ninety days after delivery by Intel. If such a defect is found, return the media to Intel for replacement or alternate delivery of the Software as Intel may select.

EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE, THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for the accuracy or completeness of any information, text, graphics, links, or other items contained within the Software.

LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION. In the event that you use the Software in conjunction with a virtual (“emulated”) device designed to appear as an Intel component product, you acknowledge that Intel is neither the author nor the creator of the virtual (“emulated”) device. You understand and acknowledge that Intel makes no representations about the correct operation of the Software when used with a virtual (“emulated”) device, that Intel did not design the Software to operate in conjunction with the virtual (“emulated”) device, and that the Software may not be capable of correct operation in conjunction with the virtual (“emulated”) device. You agree to assume the risk that the Software may not operate properly in conjunction with the virtual (“emulated”) device. You agree to indemnify and hold Intel and its officers, subsidiaries and affiliates harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of product liability, personal injury or death associated with the use of the Software in conjunction with the virtual (“emulated”) device, even if such claim alleges that Intel was negligent regarding the design or manufacture of the Software.

UNAUTHORIZED USE. THE SOFTWARE IS NOT DESIGNED, INTENDED, OR AUTHORIZED FOR USE IN ANY TYPE OF SYSTEM OR APPLICATION IN WHICH THE FAILURE OF THE SOFTWARE COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR (E.G MEDICAL SYSTEMS, LIFE SUSTAINING OR LIFE SAVING SYSTEMS). If you use the Software for any such unintended or unauthorized use, you shall indemnify and hold Intel and its officers, subsidiaries and affiliates harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of product liability, personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Intel was negligent regarding the design or manufacture of the part.

TERMINATION OF THIS AGREEMENT. Intel may terminate this Agreement at any time if you violate its terms. Upon termination, you will immediately destroy the Software or return all copies of the Software to Intel.

APPLICABLE LAWS. Claims arising under this Agreement shall be governed by the laws of the State of California, without regard to principles of conflict of laws. You agree that the terms of the United Nations Convention on Contracts for the Sale of Goods do not apply to this Agreement. You may not export the Software in violation of applicable export laws and regulations. Intel is not obligated under any other agreements unless they are in writing and signed by an authorized representative of Intel.

GOVERNMENT RESTRICTED RIGHTS. The enclosed Software and documentation were developed at private expense, and are provided with “RESTRICTED RIGHTS.” Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR 52.227-14 and DFARS 252.227-7013 et seq. or its successor. The use of this product by the Government constitutes acknowledgement of Intel’s proprietary rights in the Software. Contractor or Manufacturer is Intel.

LANGUAGE; TRANSLATIONS. In the event that the English language version of this Agreement is accompanied by any other version translated into any other language, such translated version is provided for convenience purposes only and the English language version shall control.

Last modified on 5/15/11 10:56p Revision

DOCS/LINUX/note.gif0000755000000000000000000000073211651733270011041 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/LINUX/overview.htm0000755000000000000000000000330211660711056011757 0ustar Installing Intel Network Drivers for Linux

Installing Intel® Ethernet Network Drivers for Linux*

Intel provides the following packages for managing 100, Gigabit and 10 Gigabit Families of Adapters for Linux* operating systems.

Base Drivers
For base driver features,  installation, configuration, and command line parameter information, refer to:

For Gigabit adapters:  e1000.htm
For 10 Gigabit adapters: ixgbe.htm
For 100 adapters:  Driver updates for 100 adapters can be found at http://www.sourceforge.net/projects/e1000

Intel Support for Linux

For general information and support, see the Support page.

If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information related to the issue to linux.nics@intel.com.

Last modified on 4/20/11 3:22p Revision

DOCS/LINUX/run.gif0000755000000000000000000000014111654247274010701 0ustar GIF89aE ֲ:e [K]-}lX}?g]V6T=F1]}{G;e4 .h|Ktߛ:}Q뱂ݵA@)ȧ>Sp.호y7YIie_iskm2ȶ:s:1-Ҭ6lVzj~ ?`4@hIw'q?$]F^N>+ګm45Cz?Ͷ*6>w]ΣoVQƢ{s}WTّKnֵI$1&R5TƗ )w\vk{l@kn76QS=;PK]n8M-u ~5Yl-" BoM]K1;e,qn~=nVXAڷ,gJֶ[X:XocY1gve[OưHkk}4IT陇3"5 ;C+i)UZEL,qs`.y}ۥYPkxwINGKn{f3wlgm,o#t *w Z=UVv=Vh[ [5^~OfΝ^+T{A1並voҫWMpxj,o` =F<1?\~Oa'ߦ?554{;)({4BId;oնXicǴPiڒuݿʬ7y͏h-kճk= gXӮSʵY~fYXwPk X\"kOJbEo+#Ͷ\ɇ o2w+Ů`Y~3rp6;'_&r5}7c h$ ,n3}6t-: rK upAPymdRđ }.ߜaඪ׷n:#<_*Xv]Tq]umm o@òJy:~tMncC_Pӳrw4slAt?gm]>'ѳ6\'s 'c79+Uu]E,e&Md4m9VPKa25s̙w}BgOhk7X湀 N{ͿJLk;K.wvuܦ?HXvU;3zz1cH`Τ6A\!I!fߨ}=v`qZ/odGFgd6?jL| ^+`X浍i$S X{SǵX hxog7\絣'Nk^vo%kTAH:TEU4m: '%50ƹ{Af3˛; \mW>6fE8Ix7{|1k<:V;.kvsoCןIޕ0ޡxluBs ?]c w[ԭ6YcL4<ˀ{F40[NwChsw NO9)!:n\NVCFC_l'},WkLwۙPqlw`ϟJUWSvݠO'8sS?][e5!/f{w}s\ K?hd<^6-1_]Mm/6Mg_I$TI%)$IJU6[H\#vzJy3G.?јqwRfeԺ3un0e$C r+ɧ5ڌ#OuWSXw~o{VIHҭuy{̸$JRI$8BIM XICC_PROFILE HLinomntrRGB XYZ  1acspMSFTIEC sRGB-HP cprtP3desclwtptbkptrXYZgXYZ,bXYZ@dmndTpdmddvuedLview$lumimeas $tech0 rTRC< gTRC< bTRC< textCopyright (c) 1998 Hewlett-Packard CompanydescsRGB IEC61966-2.1sRGB IEC61966-2.1XYZ QXYZ XYZ o8XYZ bXYZ $descIEC http://www.iec.chIEC http://www.iec.chdesc.IEC 61966-2.1 Default RGB colour space - sRGB.IEC 61966-2.1 Default RGB colour space - sRGBdesc,Reference Viewing Condition in IEC61966-2.1,Reference Viewing Condition in IEC61966-2.1view_. \XYZ L VPWmeassig CRT curv #(-27;@EJOTY^chmrw| %+28>ELRY`gnu| &/8AKT]gqz !-8COZfr~ -;HUcq~ +:IXgw'7HYj{+=Oat 2FZn  % : O d y  ' = T j " 9 Q i  * C \ u & @ Z t .Id %A^z &Ca~1Om&Ed#Cc'Ij4Vx&IlAe@e Ek*Qw;c*R{Gp@j>i  A l !!H!u!!!"'"U"""# #8#f###$$M$|$$% %8%h%%%&'&W&&&''I'z''( (?(q(())8)k))**5*h**++6+i++,,9,n,,- -A-v--..L.../$/Z///050l0011J1112*2c223 3F3334+4e4455M555676r667$7`7788P8899B999:6:t::;-;k;;<' >`>>?!?a??@#@d@@A)AjAAB0BrBBC:C}CDDGDDEEUEEF"FgFFG5G{GHHKHHIIcIIJ7J}JK KSKKL*LrLMMJMMN%NnNOOIOOP'PqPQQPQQR1R|RSS_SSTBTTU(UuUVV\VVWDWWX/X}XYYiYZZVZZ[E[[\5\\]']x]^^l^__a_``W``aOaabIbbcCccd@dde=eef=ffg=ggh?hhiCiijHjjkOkklWlmm`mnnknooxop+ppq:qqrKrss]sttptu(uuv>vvwVwxxnxy*yyzFz{{c{|!||}A}~~b~#G k͂0WGrׇ;iΉ3dʋ0cʍ1fΏ6n֑?zM _ɖ4 uL$h՛BdҞ@iءG&vVǥ8nRĩ7u\ЭD-u`ֲK³8%yhYѹJº;.! zpg_XQKFAǿ=ȼ:ɹ8ʷ6˶5̵5͵6ζ7ϸ9к<Ѿ?DINU\dlvۀ܊ݖޢ)߯6DScs 2F[p(@Xr4Pm8Ww)KmAdobed         w/  s!1AQa"q2B#R3b$r%C4Scs5D'6Tdt& EFVU(eufv7GWgw8HXhx)9IYiy*:JZjzm!1AQa"q2#BRbr3$4CS%cs5DT &6E'dtU7()󄔤euFVfvGWgw8HXhx9IYiy*:JZjz ?N*UثWb]v*UثWb]v*UثWb]\U]v*UثWWuqWb]v*Uث1Wb]v*UثN*UثWb]xé~l>Mokp&;-HG+w`Hy ?vb+~n6>E!5=T'Zarb,W*UzP[JLPkᤀ F$Qyb<94CUMZL[Wz:QUO#yt-zQAVtw(<ث<;wS],Hom8YHP 1TΚ-315oF;wQ@܂4mJQ*tXFJicR孯kgV~r^UVRiEIfkuKŏ񸤈?m49%RCO~A<W9q犲k<\l-'ETajQ~U1iS Zî0M_Ux\tw5?kD^a4+m5IL:}O +Qc^Z̒}VMЯe94%km8㨙UQG|-WjsE*Ob4ߛ?Z]Om:;}E]dkRCo'ت6I"n(5b-=A3hc ^bc|2Ub5ԫ6QV Ȏ\{W̺Ƃ"'QIc*, K+_]=IVC@Uk̭L8yy4q^fz@_*7R`K+DܑхUت+v*UثWbN*UثWb]x??1흦5*rT=Ǚ$ uIiv_D~SXO<,Y^W^gkruv󏙑ppLU!M?w+&H]/O/jERyx^:It Xx,QqUO$ZqN}K}#V_~׷&,䷭zޟ?I_TWUlU[~]לSƗ,i-#}ivѬh~9O1->VZv{}>=FN!.!GD`ӏ8>|x*4ȋ]3VWm63p-nA%^q?.%YO/+jat%̷߬쌉+3Ugލ.G{!4#JTV4x;|8>\>l.qM9:taOJ朜 6?6Tv*UثWb]v*UثWb]v*UثWb]v*U,5c GУoXҤ~9J~?a!Y>y퍵`bIdP¿~EQWb]N*UK癴yu1Y_Nl%#ӊ_FFU~ 7Ê4[0K ^WiZuz6)wczUN ?mx.,uv6b{; ym$C/RPL.( kXeOԵKy幊ԑl?C@=/-V3Y /x_R/\[~氂G ~&U^n'*i/+rf)ҙ%`gOͧ)^(~7 \v*UثWb]v*UثWb]v*UثWb]v*ꚏոğ>'Uq1jHǠ'>?a^w/1M:eFzv>^oF4KM1Wb]N*UتU-etm8^}]^K[XFU&KˈjLRo9Mu}qYMX}FGJYa&Rxg#FIGiku E̱ƅHdX-% i43p;y|U2;ɯ07 sKݖ"5?zOTF*5|u2¬~ j]j>j3'V#44= O7ÓC^7UVb]v*UثWb]v*UثWb]v*UثWbXw#궲<`zV-$Q, U*﨓GWW{),6H;RK+m_&*+1\)*UثWbN*UتSo.YKmZHC+[}6n27-?O3@0=m$1H~E+zn'=}bFPN_RB#nuϊ\Uث -]nkabp&)5=Iǐ 65v(IӮZ>}jGgݘ@h]Uk4;bB.]v*UثWb]v*UثWb]v*UثWb]3lo?x72.*Mz&&RGyP(K&K* -J)Xfʅ 3|ͫݬ {XD j/I|Q8Wb]N*UثWb]a/ y ڑ9:ZJ#}K+;IRlH R5:Niʟg_p_1o:4]>H!v Xب%jT8 nR ZHW1->=S}w1 )v*UثWb]v*UثWb]v*UثWb]Y4C+5/#@EI$b:s,qU2l&Wx}4NmImJܥ%&=Dgݝ=\"}_ްNBkZ}c2Jx.I#m;|JFa,f O AO/5_Bm6~bwWi9_ݓ0!ثWb_N*UثWb]9YaV[dFI[n8[_MH1U &9E4 QA )生,fɵb]< ibUq5YIv()O5dWחڴ.-#mTkOR*jFeɦF)]ڵiS9`PVzoY #LSܣ[1G b(<̐0=:0z05iţ9E+ޯo)A[C2B?YR<*"/.mMvEi<>\5#E I ^퇅-{EӜ\rT0,ѯ'H4h]GKMBHC䐒 WfY3c¼-'E$jzdl)ߟZ'gwVޙ&d(^c˃cb,Xv*UثWN*Uثt [JkWC,rYέᵻtXu+At (o"tRSEƩ> [{O}cҚN~wGt^VՄڜƨ,DOԒC>%{TӍ}W^V_]:]ZPm.]^WQP)q6. oEYgϕo&{kX#ĒjX& ClTJMYs[@[6q^_ % *(Uf,A,ԹZُ/ğ񴒦Vdr}>#+Tɕ@߾V<* ,ך42X(ĬDopB?YA$H?VSM5ny|-IJ%gn=2_ŌJ51r&HeUӏ䬿儔İFH5fYߏs"HL#~ xqqF$(&jPU5nEi4ۗ.KdvG棤LnDU,2 (de%-GͿ(o&2[e+H㱚5IEإثWb_N*Uت[ˤvb3dxU B+M*+=%u*5> k;FKyAV$crKU4wkTaw-yXkSONw͛_%Ro5ɚ** GNI$JtV^x6Ԃ9=6:QYd*o7h/-j:*\ V[BߵÒr\Yŋj-?Jڻ1ߑEDy+](MV.!xb2o2n8:!r";_c,Yq6?5o4ŜҪ䧨Qx]J|8s趚y!2\U;U~6ř#RA(_(mFړqn(Hdqa2TdV% _\Kg}:]Fث)F4Wp_IX_O,6vZؒKo+%FI&vIr)s+7̗mBtI-oFmUFiӯ#)_󋺜[יm5F0I"J@n/&vq卤+3ihhIGoTW%y4,=l'Z3?`?@BqRJ)jx<9qqfЮ^U)#XńAڡ~Jr;cliX5@sWb{r,|fvQK;Kjs(A$"X iF"v*UثWbwP/1MVEv*~Vw28/ IXTTy+qlU/>](DALՁny tٷ¸Ѭi}g@Ke?ޙ]Iz`^>~ތh) VNz^m|ʒӉq&L1Wb]v*U,ռš RԒq;VF`JqdGޜqI#|([F7U?bTc+%PVŤ ?R'1U0_fuɽ:KMAET/)/fjη0[J?c~\L4*ujQ =ej/C\s*Wa+N-1OmmgX$]v*UثWb]N*UB ʁ2Ѱc@ܰ튼~G.om\Y@e6Mn1fin?Ow3*Y组[}Vyb F-%.gwXc-bx$[~4xIa4M#J|1hb(Nw5WW ֮融:i]%WCt{K]Vi"OkۄKal8 k}4j~_׼ . KkoH K=[f#2\ZsaӸ}^v*UثV;{(n&ث"]v*UتUc@[3N>3d8ʌY_Kڍ[{Z6::,wJcu-pTx5Zt<âm:i}FֽEH>vfi7~mk.$:m7fD9׏44Ÿ*bN/S/eI 2`q_K>eԝ6če6XL4_$$cUyk_޹2ZOX+p$ *2[?IhS='ZKiHzȂܤ5wT3ro,U4]v*Uث]bv*UثWb]v*N*Uث@u]LUP]v*U^&*ȱWb]v*UتOy4_ޢ_\ֺta缙W-aY.&XԆ(EiFXg;XYuGmf%dѭ_Xc>5sq_%Tn?/\V+o 5hTxJڜ3zXk~3@_-XIi7FXr259H%yx{y>ǮeYM^EvaXΠx$t RḧXWb]v*U_ծVIv*UثWb]N*UثWb]v*UثWbXWbobv*UثTV4Uھlw{'F-ķ3pRzPvتjoR,5ӕ >:sBG6R?Vkޣ1HNG z?wm/?L.h"J>m)HP/6)b*UتSyWwɨĞ:^I( dCɪ'T]:EDkpA}3WSwQ,7JcIMB8y~኷/5m85-H!U~Lh>ܾroB7a t8?v*UثV7 kk?VY&*UثWb]v*UN*UثWb]v*]\Uںc_dX1TΞ[x][7qib^F *~%>-O:jNZ-ŵIR{`z}Zb`jpkEb'_ȯbRX0Ӡ#ŬU;+NFO4#j Tf*UثWb]v*jY1K; -^@xN3E"WrF$mFܱT˞`M+]{0~ MY>cP r 3]Kw+Fb-gKM/ZdXKgwgISm+ǦCu5u n,&JRU劦X1V7 kk?VY%F*U81Wb]v*UN*UثWb]Qq#cot_&*]Y[i9~ҭ0=RӫlҢ@~`> QǓH/VcALVn zAYZ@ڛ7C CR~~e ~+m (Ap%Yi Da[[Bu!X\QxӯM`goz{4_O_ȦL7NI%ȚX<0tH [{X8EU#¼W5Ƃ8U'N-PW@)J71rt,KW?v H&,`r&eT_'V#~TUcTt Z5Eu,KESEL~*UثWb]v*_8yci:dc1HY\)vJiLb jWP$@:KaRD\??0CN6iQĊȿizwcІkm=ݙ]U--V.\ۗ *o$"!mmmC"DF9HFfPZGgo&! h%~mi WjD!4̭2Kh.mJ59*ܿjn_ʫ +BEͣttP;ek+`3 űe?NÒ$^Ja䷸W>`+9jKZmfMKQcoe~Т~{=/Y |ףF^: nykOM$[4Z=T;K_s?;/KD$a,s2hϏ-/` KC:SC|B듵Wӑ2`!W߉vh>t@4Qdig!S_' PWhC+9G.>ܕ6 *JU~RKGE-8(,aV{ʞ?i) dbV -*UJJƋEj|sG܊7\8"VOun(UVc Gɿh9^rJ,AS1SY#/%ZNAtoxHW-S쾵ʿJCWMnC0S蛃^tt˶FMex RUثWb]|˻kRT-AܪkWX@ yJI)1VZB..! lދuuYh*\__gJix8Z5h{q =6C+.oD!"$)j MĜɾ/[_ sn-Y=%>*xޛmOێ"o'8qi i8E. I !ԡ*$nK{˛76eqIT̋'TQ?j?<..&UᕣVSqz|#@w5~L]pWs=ש,3ҵVO n]v*UN*UJxiOR5+EQRh7XHmүtthc<R}Zi95vTԼE7]sp\BG}Y`;nت],Kyp@|Z>\3#gኮ&R"G snSd eQ(׏<니࿆I6nZ>lv߼'MTƗs1oqw7P25nX ?__o}xAUri:S{5z8^"'8)l!*4ZN؎+h ɭeJZ^ܙV>O/><6I\_UZ˭\Yj0^-M,s9=;oз^&Zog䮧1Cv֒KF+B@,K2Lσ.6SPB2Jm .oOʦ6C?_ #._c.^ l\ IJ4~&~8b]v*UثWbC_>Cڦ b[,Sm}mCN4|5+?)$j~4_Qc GyG^.֚ǗtqK+Yf+T%.qalOdRIM'}}ww?ʮACH__OiIoP}TGo"ߢ%ޕwb-_x*#- N?Z * A\cGQ{}cIQLn%F &x$Ŀ}\x٦(v*UثWbN*UceV*H4aJj*S5.hXӌ-W+=EѴez~,/e'dY$V^_ m$8b3]cmt[5YX<V12'qHJ4RIX_b|c.k,Z]- Asl#{/ _7/RT.nmRVef-]\H]v.՞N\Ỿ^*_Y*UثWSu1Wb*k>^5MB sR\B2FhNQ*MyL"]'Q)QNKG@?w{RE\Ewq dG j 7$s[sR/wrb)RWS۵eA:bU4'UŸ,i!1zEɨGu"713'm^GDo)c"U7տ3Cwj鷢ޓq4a)$0deiHSwMZ]ikE?~_J'H.xCb;7 93/FC{eV6'/O?{m441Frӈ_`7iii_l) ~_c7z׿pKa!+7XzݭwSGokn-H'wv!UEY&-]{Rm#SqȠ1B3(pS UWb]v*UثWb]N*UثWb]v*UثWb]v*Uث??I,}eocJV{1 7R huZVg% >Z/9,х0"vG'H(#XI=@o&=6&{79LѱajD4qIb 4j8QQycƓaˮL>n4n]iI@)~~ǀ mztF! -U[y=d4| ^/ a⅓ZJmۗL[х8@m䍶. G]|USb|Kcahn-jWbXOI3M"S¶N%&iq$k$i?$t?Ku-~h^jo'jQ鯩z᪅F_i6TK5)'&>Ŋ~O}.y#S{2-4r׉8*82]<[^'I-9٬/^^YKZ]5/۝Q$kAb3_a.*qWb]v*UثWb]N*UثWb]v*UثWb]v*Uث厁[.V'GΈ O0%ZSU =DmeCWĒJqixPߗ~ei}5sq7/O@r(81ZgȖlTYRIk::H#V'14qi6__E4h)ҜQZJ_˖D~ZqZx\x.!Wȯf%Nܱv/۶$PzPx1\?"?-E?| JR0-/oqK@,{# +4b;ߗVދ]v*UثWb]v*UثWb_N*UثWb]v*UثWb]v*UثWb]v*UثWb]v*UثWb]v*UثWb]N*UثWb]v*UثWb]v*UثWb]v*UثWb]v*UثWb]v*UثWb]DOCS/LINUX/style.css0000755000000000000000000000450511651733270011261 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/LINUX/support.gif0000755000000000000000000003157611651733270011622 0ustar GIF89a]h!"9)$9J,Z B R)j)R% X& e)(s!4k#2x1 k1&X1JMwuC6~9;f37j.\8%׶}$).fdӫ_m: ҅qըqaI[1ĖlpG uQW!Qd9ކvEt #81TL37Hae1`)(IroP"YBT!υT"qI}(TVOiH"3McΙᆋ¶]2833h&cv!b r$1%<3 $nxY'eqFRZ)餔VF<3Hc9|ƘllLؗ1fl3_v9z>L*c1KBxdi6lP.Ęrnaa9}y+T0b .z91IvgGU C!zJK4H"ta / w4RSx8-(Q98 3Ċ;>#hAe0H8#nA 7 .;#OH>[ҸUDBHUa-?%Agdx HJ T-pxcG#(#Aژ"btАQ]]E IH"8$@3džhLh!;Z<A01pƸx 㨑8UI˼Qxm(1 2 R&7)ǒ@Wb&H\!"yxȥ8!orH-,8 '$"X21zEcb$ -9F[Ӝ,dQ =z扅z^WpB 8Els IN3lB*:TF5a?BbG;T?@A ^TJqkt#P:uh!p!2|wѻ eHMOAO8(6a5zB`!` +)́l HH9z (3"01Jͫ^iFBK5!AT3ƍi@ʉdyq9Y`C+H8e{MjibH8Wqts Ad@("C;p+QqF `_p`` ؀ؐȉِ Jv/(ِ2P܀[8 TDE7yq P Ҩ `bu0vxqp % e |73Yxhȉ(+h  yѐ 2   ^]0}!-HLX @ bi0] `m@}FP#V `0&g (v0q\gs  p! e +A6p1\@ȏ P*9  *` *p **\) 0%لM8 Q:P[PHG R$PGP yPfsv^h'~XuG} 1H Op.-=0 ` p؉ Xz`  򀙹\KnlQ$Ii0xw E<@lp@ 0l09I8 xS&v(@qōۘi)DEpV $ gj` ЏzI_vZ  yTw+׈ x;50Awb Ds mPXx'&ʁF\˵qyv5GUGEBV'WtEpIi0'ŰxYmڦP}YsJuJ}^ K(Jp`p7fC7 P iBH^jJ&ʆ`*W` `Y|H QZ/fphpӯ PP gq1p *Jvtژ i]!]0iMyIr,°BFɑѭW[9 Y\Kf9 T@Q |{-隡p1:@'ߡC~1^Ph5i&=ڰ ԉ.q* P `@g_ eлfr`qq@p#[/o46{*iK0!YHp D盾]*J! L @Z++^k]wZ) < )`o; ,+jI*'p9pbp% l020po` p^P[&ć uXK!Q|C @Tt _g9|kAX̠&V)Ipʂ|aL`pk+AHQ2K㰿 Ȍȑ! 09;P  L+PH|Ѱ ]Q*P2p3 2I0PgpdEQL,$li|ibƅ:|_л[ Ǜ 0j Q؄oJ)xz,PzpȐ2aɊʈl7`ɞi;p{** Cl-\,؛ -m <iȘ]r,$ғ^@Ƭ̺b.Ps0ZhE9 i}Pt& K, <[  1 GQ9RS epq\okk*+q ݊NHа9lVIK M ҋEʩ} \{|ÜQL1MV0TKL!9];Gƭ2ZJLJR}+΀m5:aE Ac1 0 0 %N(paPP9\gz H_ wglўfjh,ċ݊IΩKɽ-9$i:] Y={l4^( ˾'"WXa5>ioj0#A kD$^bTp  \9(\\46m wvؤ Yg2_Puջg0'rp;dm' mℙꙹٳ O]3a+K`f&ik,:NjʎZN|0j)IpZ2m" t$ sP}҂0 zV>R3~r0 :wǻo`rot tl"WŚМ] ۮ"L4Na*  )hG4HOG/d;̠i2@Jx?Uk-7vI(tķAp8ˆ[)y_tr(%{T f,xȁ!CbF +"W;q}|-p}1HhJ1V]nP2\`nBcK31BU \*qRЁXA,A Јxp׻?ftWD')91kht2!ǘ2V-pp3!B1A2F dpMr/a XplcŔ ipE8,ssc(bÆ[ސ'!Wh%CcgZ7 3$(X3x̸41|׼0}p4!pӸ| cgx,@`l|c[; FQxiKo$pɸ? {ZzmuHޅS4_^4':!FE.<O7Ip9:\5)V@׮j4| d  #U<;%S3܀5Qp 73uG3#HM>LSo=^W`z5w{ hO1!C}Dp tXȺ [> 䳇哇OS tzx (=; zXp rC;B 7s`2g`6hM9),zch%@# a r xhyv6> =L  @cx'O+I$ 1c"t@A8pp M893bz/tM9]tT18; );Jkės8hVxh ck?p?50 E, 3?+%MgHx9/?8512 gZHЅJ49-Xm<R=RUxՅMIeԑnX7&$I KRTsHpWY=SuR؇T^V%<̺Ľ % ЙP>Xo4nxӱy K{>eU&jmhy+L6@L!-""X3!@ȧ}9@6`1hE-!rӱ#X- AN]T&?}XxHA -1J\ H\NAsG},թ\{\C }=Y\ܣ٨Ľ- pBwQR JsK+їr)^H7-!E̲[q!W|[+"83CXChOש}^b=!85\ \Mm\:j܅A)TlCӗ``a%#QXٟ]NXYTF`~tU0EUPϜE8Yħm^9^%VJF گ="%[M[%*^"8!ai:?7 7,}X_:Sԭ:mؑITxܘXO=T TVm\څ,X1:G7T]ʥa%G&T Ƈ B|Ty&dZ|b͈EK- RU!+cI`Cޱ+,k56o5HȋB5(x/˂/}:@X3t,c=~vYGgo\`@d}4:(:ۅ%Go}w]U:uȈPf`$LhQH0ɬsIiLIEϖi"蟞Bc%;!>yvcbyNjfzDg]xF/ #l^b-Ɓ 6X9]H*ȁG.C5"f7,M} 癨p:bޤĆ#$M*t xl] <p8{`Nlfj ATClˉav^,x04iHfjv%W-pXBq.O)32xcEFljj m#򮐛"X˦my,=fՌCގM;V~@bf? H.6i1-yx@ތ=mq&)8nӡ"vw0555KVfh.pRqk ߴ 610 Ca('H4#H4K÷r/O>1䕾Z" s%SQ3&ssqCЍ&`.I =M6)q7I/tLDF^f^FJc=8QSg%[G#AdiWcJkM?vd>V!f^n2bfw0Tߟ˔hn]dt*\\vISDMvye!N8뱺-(7Eb`'xWxbHׅC-pE @`#B+dy@^óSzy/AFV7x->35 G??. ЀH+}dryz,yJym!p&5Wj]8>upB8zݔ4fgZz{zE,"b~3rs9?cxf̲?{ȟF5x3$8J̸{?pz,v[goqvT/@{/yHI(5`Uͤw6v~W,_'| >1t^Ǐ;F9AxJxIc45 Y,h „ 2l!Ĉ'RH^={7jc= a$Ɣ3ڋ'0u=4(1E*ib)l\ =ŬZ꒰K.ZQEjײm-ܸrureǒOQ]ѣČÆMlhC&ĦJ {ңIXͥ"aٱ M6ܺw[};I)%x2@>$ǐ!7(MpUXӂuCӯo>~=N2U 7.8=ƆQ4\$ ZJV<0 L,"@]4NSV'.E4 HtAxD#œKKYŕWx->fbXR@"'(j\ Yc"fl}oJ5qQ<2ua]CC(p)\p#`*).D H^AѨM=`1c4("Lϐ90K,K*cd80qriK A-Z{c*2Pr^sjf{/guJ,bD/@FD1DFxZ0sN` K8*vmKU}6ib?b$4]>L 0@ZK9oPrl3t|j1ߵԬԉ|]"@<'Fd2ġCu#hu(zuCcU4*"Nc(:NٌX {8EHfBǕ(څLlGRt&ArN 6L}*T*թRV*Vխr^*X*ֱf=+X/qMLuЄTrQ Vjj_:Vj]JվO(d#+Y)qI,[TrOeٵ-jSڸL)!.Z;DOCS/LINUX/support.htm0000755000000000000000000000206611651733270011635 0ustar Intel Customer Support

Customer Support

Intel support is available on the web or by phone. Support offers the most up-to-date information about Intel products, including installation instructions, troubleshooting tips, and general product information.

Web and Internet Sites

Support: http://www.intel.com/support

Corporate Site for Network Products: http://www.intel.com/products/ethernet/overview.htm

 

Last modified on 5/12/10 3:26p Revision

DOCS/LINUX/test_ln.htm0000755000000000000000000001057311660711056011571 0ustar Test the Adapter

Adapter Testing Using Ethtool

Intel adapters have built-in self-test diagnostics, such as I/O conflicts, memory faults, EEPROM operability, and basic transmit/receive operation. This can help determine if there is a hardware fault due to the adapter or cable connectivity. This testing capability is built into the adapter and is accessed via the driver. Ethtool (version 1.6 or later) is used as the interface for the diagnostic tests and results.

Ethtool is an open-source program that can be used as an interface to provide driver configuration and diagnostics, as well as displaying statistical information.

Ethtool is available at: http://sourceforge.net/projects/gkernel. See the ethtool man page for complete information on usage.

To invoke diagnostics from ethtool, enter this command:

ethtool -t <EthX>

where <EthX> is the name of the Ethernet device under test (e.g., "eth0").

Here is a sample of the diagnostics output:

The test result is PASS
Register test  (offline).......... Passed
EEPROM test    (offline).......... Passed
Interrupt test (offline).......... Passed
Loopback test  (offline).......... Passed
Link test   (on/offline).......... Passed

By default, the more comprehensive "offline" test set is invoked. This will momentarily disrupt any active traffic on the device under test. The set of available diagnostic tests is determined internally by the NIC. The tests that are run are determined by the ethtool command line parameters.

The following tests are common to many Intel adapters:

Test Name Description Test Results
Register Test Test patterns are written, read and verified through the adapter's device registers to ensure proper functionality. Test failure may indicate a faulty adapter.
FIFO Test This utility will write test bit patterns to the adapter's FIFO buffers, to make sure the FIFOs are working properly. Not all adapters have FIFO buffers, so it may not appear in your test results. Test failure may indicate a faulty adapter.
EEPROM Test This test is run if the adapter is equipped with this type of memory. It tests both the readability of the EEPROM and the integrity of the data via checksum. Test failure may indicate a faulty adapter.
Interrupt Test This tests the adapter's ability to generate an interrupt. This test sets the interrupt cause register and reads the interrupt set register, verifying the adapter correctly registered an internal interrupt. Test failure may indicate a faulty adapter.
Loopback Test There are two internal loopback tests: MAC (media access controller) Loopback and PHY (LAN controller) Loopback. Neither test requires an external loopback connection or responder. These tests set the adapter in the appropriate loopback mode and send packets back through the adapter's receive circuitry and logic. Test failure may indicate a faulty adapter.
Link Test This checks to see whether or not the adapter has established link with its link partner. If this test fails, check the cable connection and the status of the link partner.

Last modified on 12/20/06 8:55a Revision

DOCS/LINUX/toc.htm0000755000000000000000000000222411660711056010700 0ustar
Basic Setup & Features

Overview

Gigabit - e1000 Driver

10 Gigabit - ixgbe Driver


Technical Information & Support

Adapter Testing and Diagnostics

Testing the Adapter

Customer Support


Copyright © 2002-2011 Intel Corporation.
Legal Information

Last modified on 11/04/11 11:38a Revision

DOCS/LINUX/top_lnx.htm0000755000000000000000000000056611662465060011610 0ustar

Intel Linux* Base Driver for Intel Ethernet Adapters

User Guides Home

DOCS/LINUX/trbl_dm.htm0000755000000000000000000003446611656741062011560 0ustar Configuration and Troubleshooting

Configuration and Troubleshooting

Common Problems and Solutions

There are many simple, easy-to-fix problems related to network problems. Review each one of these before going further.

  • Check the cable. Use the best available cabling for the intended data rate.

    • Check that the cable is securely attached at both points.

    • For copper connections, make sure the cable is a 4-pair Category-5 or better.

    • Make sure the cable length does not exceed specifications.

    • Perform a cable test.

    • Replace the cable.

  • Check the link partner (switch, hub, etc.).

    • Make sure the link partner is active and can send and receive traffic.

    • Make sure the adapter and link partner settings match one another, or are set to auto-negotiate.

    • Make sure the port is enabled.

    • Re-connect to another available port or another link partner.

  • Look for adapter hardware problems.

    • Re-seat the adapter.

    • Insert the adapter in another slot.

    • Check for conflicting or incompatible hardware devices and settings.

    • Replace the adapter.

  • Check the driver software.

    • Make sure you are using the latest appropriate drivers for your adapter from the Intel support website.

    • Disable (or unload), then re-enable (reload) the driver or adapter.

    • Check for conflicting settings. Disable advanced settings such as teaming or VLANs to see if it corrects the problem.

    • Re-install the drivers.

  • Check for recent changes to hardware, software or the network, that may have disrupted communications.

  • Check the adapter release notes (readme.txt).

    • The Known Issues section may have specific troubleshooting information for your configuration.

  • Check the Intel support website for possible documented issues.

    • Select your adapter from the adapter family list.

    • Check the Frequently Asked questions section.

    • Check the Knowledge Base.

  • Check your process monitor and other system monitors.

    • Check to see that there is sufficient processor and memory capacity to perform networking activity.

    • Look for any unusual activity (or lack of activity).

    • Use network testing programs to check for basic connectivity.

  • Check your BIOS version and settings.

    • Use the latest appropriate BIOS for your computer.

    • Make sure the settings are appropriate for your computer.

  • Reboot the computer.

The following troubleshooting table assumes that you have already reviewed the common problems and solutions.
 
Problem Solution

Your computer cannot find the adapter

Make sure your adapter slots are compatible for the type of adapter you are using:

  • PCI Express v1.0 (or newer)

  • PCI-X v2.0

  • PCI slots are v2.2 

Diagnostics pass but the connection fails

Make sure the cable is securely attached, is the proper type and does not exceed the recommended lengths. 

Try running the Sender-Responder diagnostic Test.

Make sure the duplex mode and speed setting on the adapter matches the setting on the switch.

Another adapter stops working after you installed the Intel® Network Adapter

Make sure your PCI BIOS is current. See PCI / PCI-X / PCI Express Configuration.

Check for interrupt conflicts and sharing problems. Make sure the other adapter supports shared interrupts. Also, make sure your operating system supports shared interrupts.

Unload all PCI device drivers, then reload all drivers.
Adapter unable to connect to switch at correct speed. Gigabit adapter connects at 100 Mbps and 10 gigabit adapter connects at 1000 Mbps.

This is applicable only to copper-based connections.

Make sure the adapter and the link partner are set to auto-negotiate.  

Verify that you are running the latest operating system revision for your switch and that the switch is compliant with the proper IEEE standard:

  • IEEE 802.3ad-compliant (gigabit over copper) 

  • IEEE 802.3an-compliant (10 gigabit over copper)

The adapter stops working without apparent cause

Run the adapter and network tests described under "Test the Adapter".

The Link indicator light is off

Run the adapter and network tests described under "Test the Adapter".

Make sure the proper (and latest) driver is loaded.

Make sure that the link partner is configured to auto-negotiate (or forced to match adapter)

Verify that the switch is IEEE 802.3ad-compliant.
The link light is on, but communications are not properly established

Make sure the proper (and latest) driver is loaded. 

Both the adapter and its link partner must be set to either auto-detect or manually set to the same speed and duplex settings.  

NOTE: The adapter's link indicator light may be on even if communications between the adapter and its link partner have not been properly established. Technically, the link indicator light represents the presence of a carrier signal but not necessarily the ability to properly communicate with a link partner.  This is expected behavior and is consistent with IEEE's specification for physical layer operation.
RX or TX light is off

Network may be idle; try creating traffic while monitoring the lights.

The diagnostic utility reports the adapter is "Not enabled by BIOS"

The PCI BIOS isn't configuring the adapter correctly. See PCI / PCI-X / PCI Express Configuration.
The computer hangs when the drivers are loaded

Try changing the PCI BIOS interrupt settings. See PCI / PCI-X / PCI Express Configuration.

The Fan Fail LED of the 10 Gigabit AT Server Adapter is on (red) The fan cooling solution is not functioning properly. Contact customer support for further instructions.

Multiple Adapters

When configuring a multi-adapter environment, you must upgrade all Intel adapters in the computer to the latest software.

If the computer has trouble detecting all adapters, consider the following:

  • If you enable Wake on LAN* (WoL) on more than two adapters, the Wake on LAN feature may overdraw your systems auxiliary power supply, resulting in the inability to boot the system and other unpredictable problems. For multiple desktop/management adapters, it is recommended that you install one adapter at a time and use the IBAUtil utility (ibautil.exe in \APPS\BOOTAGNT) to disable the WoL feature on adapters that do not require WoL capabilities. On server adapters, the WoL feature is disabled by default.

  • Adapters with Intel Boot Agent enabled will require a portion of the limited start up memory for each adapter enabled. Disable the service on adapters that do not need to boot Pre-Boot Execution Environment (PXE).

PCI / PCI-X / PCI Express Configuration

If the adapter is not recognized by your OS or if it does not work you may need to change some BIOS settings. Try the following only if you are having problems with the adapter and are familiar with BIOS settings. 

  • Check to see that the "Plug-and-Play" setting is compatible with the operating system you are using.

  • Make sure the slot is enabled.

  • Install the adapter in a bus-master slot.

  • Configure interrupts for level-triggering, as opposed to edge-triggering.

  • Reserve interrupts and/or memory addresses. This prevents multiple buses or bus slots from using the same interrupts. Check the BIOS for IRQ options for PCI / PCI-X / PCIe.

Here are some examples of BIOS parameters:

PCI / PCI-X / PCIe slot #: Slot where the adapter is installed
Master: ENABLED
Slave: ENABLED
Latency timer: 40 - 80
Interrupt: Choose any one of several that the BIOS provides.
Edge-level: Level

The exact wording of the parameters varies with different computers.

Other Performance Issues

Attaining the best speed requires that many components are operating at peak efficiency. Among them are the following:

  • Cable quality and length - Do not exceed the maximum recommended length for your cable type. Shorter lengths often provide better results. Check for loose or damaged connectors. Check the cable for kinked or damaged sections. 

  • Bus speed and traffic - The PCI bus speed accommodates the slowest PCI card installed. Check to see if you have a card that is slowing down your system.

  • Processor and Memory - Check your performance monitoring programs to see if traffic is being affected by your processor speed, available memory or other processes.

  • Transmission frame size - Your network performance may be enhanced by adjusting or maximizing the transmission frame size. Operating systems, switches and adapters will impose varying limits on maximum frame size. See the discussion on Jumbo Frames for your OS.

  • Operating System - Networking feature implementation will vary by operating system version, such as offloading and multiprocessor threading.

Last modified on 8/21/08 11:09a Revision DOCS/LINUX/warning.gif0000755000000000000000000000076411651733270011546 0ustar GIF89aﭭ便{{sskkccZZRRJJBB9911))!!))!!!!!!!!!!,@pH$rlx$r ҬRp.Zir@*8BH)Y8]2"F"l }"s!Pa% Ia# ' r$$R]R'"" XL  JNo E^NۀE@ YPې  2]`eC @ lB::V@ "jHD0eR҄^H 3N@;DOCS/LINUX/warranty.htm0000755000000000000000000001324011651733270011764 0ustar Limited Lifetime Hardware Warranty

Limited Lifetime Hardware Warranty

Intel warrants to the original owner that the adapter product delivered in this package will be free from defects in material and workmanship. This warranty does not cover the adapter product if it is damaged in the process of being installed or improperly used.

THE ABOVE WARRANTY IS IN LIEU OF ANY OTHER WARRANTY, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF NONINFRINGEMENT OF INTELLECTUAL PROPERTY, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE.

This warranty does not cover replacement of adapter products damaged by abuse, accident, misuse, neglect, alteration, repair, disaster, improper installation, or improper testing. If the adapter product is found to be defective, Intel, at its option, will replace or repair the hardware product at no charge except as set forth below, or refund your purchase price provided that you deliver the adapter product along with a Return Material Authorization (RMA) number (see below), along with proof of purchase (if not registered), either to the dealer from whom you purchased it or to Intel with an explanation of any deficiency. If you ship the adapter product, you must assume the risk of damage or loss in transit. You must use the original container (or the equivalent) and pay the shipping charge.

Intel may replace or repair the adapter product with either new or reconditioned parts, and any adapter product, or part thereof replaced by Intel becomes Intel's property. Repaired or replaced adapter products will be returned to you at the same revision level as received or higher, at Intel's option. Intel reserves the right to replace discontinued adapter products with an equivalent current generation adapter product.

Returning a defective product

From North America:

Before returning any adapter product, contact Intel Customer Support and obtain a Return Material Authorization (RMA) number by calling +1 916-377-7000.

If the Customer Support Group verifies that the adapter product is defective, they will have the RMA department issue you an RMA number to place on the outer package of the adapter product. Intel cannot accept any product without an RMA number on the package.

All other locations:

Return the adapter product to the place of purchase for a refund or replacement.

Intel Adapter Money-back Guarantee (North America Only)

Intel wants you to be completely satisfied with the Intel adapter product that you have purchased. Any time within ninety (90) days of purchase, you may return your Intel adapter to the original place of purchase for a full refund of the purchase price from your dealer. Resellers and distributors, respectively, accepting returns and refunding money back to their customers may return Intel adapters to their original place of purchase. Intel guarantees that it will accept returns under this policy and refund the original purchase price to customers purchasing directly from Intel.

Limitation of Liability and Remedies

INTEL'S SOLE LIABILITY HEREUNDER SHALL BE LIMITED TO DIRECT, OBJECTIVELY MEASURABLE DAMAGES. IN NO EVENT SHALL INTEL HAVE ANY LIABILITY FOR ANY INDIRECT OR SPECULATIVE DAMAGES (INCLUDING, WITHOUT LIMITING THE FOREGOING, CONSEQUENTIAL, INCIDENTAL, AND SPECIAL DAMAGES) INCLUDING, BUT NOT LIMITED TO, INFRINGEMENT OF INTELLECTUAL PROPERTY, REPROCUREMENT COSTS, LOSS OF USE, BUSINESS INTERRUPTIONS, LOSS OF GOODWILL, AND LOSS OF PROFITS, WHETHER ANY SUCH DAMAGES ARISE OUT OF CONTRACT NEGLIGENCE, TORT, OR UNDER ANY WARRANTY, IRRESPECTIVE OF WHETHER INTEL HAS ADVANCE NOTICE OF THE POSSIBILITY OF ANY SUCH DAMAGES. NOTWITHSTANDING THE FOREGOING, INTEL'S TOTAL LIABILITY FOR ALL CLAIMS UNDER THIS AGREEMENT SHALL NOT EXCEED THE PRICE PAID FOR THE PRODUCT. THESE LIMITATIONS ON POTENTIAL LIABILITIES WERE AN ESSENTIAL ELEMENT IN SETTING THE PRODUCT PRICE. INTEL NEITHER ASSUMES NOR AUTHORIZES ANYONE TO ASSUME FOR IT ANY OTHER LIABILITIES.

Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations may not apply to you.

Critical Control Applications: Intel specifically disclaims liability for use of the adapter product in critical control applications (including, for example only, safety or health care control systems, nuclear energy control systems, or air or ground traffic control systems) by Licensee or Sublicensees, and such use is entirely at the user's risk. Licensee agrees to defend, indemnify, and hold Intel harmless from and against any and all claims arising out of use of the adapter product in such applications by Licensee or Sublicensees.

Software: Software provided with the adapter product is not covered under the hardware warranty described above. See the applicable software license agreement which shipped with the adapter product for details on any software warranty.

Last modified on 7/23/02 10:42a Revision

DOCS/QUICK0000755000000000000000000000000011761422164007275 5ustar DOCS/QUICK/CHS0000755000000000000000000000000011761422163007711 5ustar DOCS/QUICK/CHS/legaldis.htm0000755000000000000000000000153211730046352012270 0ustar

Ȩͷ

Ȩ® 2002 - 2012 ꣬Ӣض˾Ȩ

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Ӣض˾ԱĵеĴ©ΡӢض˾Ը±ĵеϢκγŵ

ӢضںͱӢض˾ң̱ꡣ

*漰Ƽ̱ڸʲ

Ϣ

֤

 

޶ڣ 2011125 10:21 ޶汾 DOCS/QUICK/CHS/license.htm0000755000000000000000000002216611730046352012134 0ustar ֤

ӢضЭ

Ҫ - ڸơװʹǰĶЭ

ڸơװʹմ֤Э飨“Э”ṩıκιϣܳΪ“”֮ǰϸĶ¸

һơװʹñܱͬЭиԼͬⱾЭеκơװʹñ

֤

ע⣺

  • ϵͳԱ“վ֤”
  • û“һû֤”
  • ԭʼ豸̣OEM“OEM ֤”

վ֤ ԽƵ֯ļԹ֯ʹãҲĿıݣǣ

  1. ¶ʹãaӢضƷͣbеļľӲϵͳʾΪӢضƷ⣨“ģ”豸Աκʹ÷ӢضƷһʹãڴ˴ɡ
  2. ݱЭӢض˾“Ӣض”ǶռҲתõ׼ʹñϵİȨɡ
  3. Э涨֮⣬øơ޸ġ⡢ַۡתñκβֹ֣ͬδȨ
  4. 򹤳̡򷴻౾
  5. ܰݴ˴֮ṩIJ֣ЩӦ֤

û֤: ԽƵ̨ϹʹãҲһݣǣ

  1. ¶ʹãaӢضƷͣbеļľӲϵͳʾΪӢضƷ⣨“ģ”豸Աκʹ÷ӢضƷһʹãڴ˴ɡ
  2. ݱЭӢض˾“Ӣض”ǶռҲתõ׼ʹñϵİȨɡ
  3. Э涨֮⣬øơ޸ġ⡢ַۡתñκβֹ֣ͬδȨ
  4. 򹤳̡򷴻౾
  5. ܰݴ˴֮ṩIJ֣ЩӦ֤

OEM ֤ ԸƺͷǣIJƷɷָһֻϵIJƷеһ֡вƷûṩĶάԸʱųκƷһϴһڰװӳķӳ񣬲ƣ

  1. ¶ʹãaӢضƷͣbеļľӲϵͳʾΪӢضƷ⣨“ģ”豸Աκʹ÷ӢضƷһʹãڴ˴ɡ
  2. ݱЭӢض˾“Ӣض”ǶռҲתõ׼ʹñϵİȨɡ
  3. Э涨֮⣬øơ޸ġ⡢ַۡתñκβֹ֣ͬδȨ
  4. 򹤳̡򷴻౾
  5. ڷ֤Э½ĿͻЭ“⼴”Э顣޶ȣ֤Ӧñ֤ӢضӵȨ
  6. ܰݴ˴֮ṩIJ֣ЩӦ֤

Ȩơ ã (i) Ա“Э”δ涨ķʽʹûƱ“”(ii) “”κε(iii) δӢضȷͬ£öɱ“Э”ת“”(iv) Ա“Э”δ涨ķʽ򲿷޸ġֲת“”(v) “”ִз򹤳̡򷴻ࣻ(vi) ͼ޸Ļ۸ڿ“”÷֤ܣ (vii) Ա“Э”δ涨ķʽ“”“·ַ”Լ“ʾԴ”ƷκԴʽתڻתøκε

Ȩ ڴЭȷṩɣӢضȷʾķʽṩκйӢضӵлƵרϢרȨ̱ꡢҵܣ֪ʶȨȨ֤Ǵ˳ȷûκɻȨֱӷʽͨʾյֹԻʽ˵ӢضӢضרȨ̱֪ʶȨκȷȨ

ȨͰȨ “”ֻʹɣdzۡӢضԱиӵȨȨУҺ͵ķԼʹԼıôӱɾκΰȨֹͬԱδȨĸơӢضʱĴе֪ͨûֻ֧´ֻ÷ͬȫܱԼҲκθʱſתñ

ԤĶ ݴЭаװʹõԤҵл߱ΪʽʾΪ“alpha-”“beta-”棨Ԥá

ڱйԤκ뱾Эκͻ£̶ֽȽܽ˳ͻΪޡ
˽ⲢϱԤӢض汾ҿܰһЩ⣬˻ᵼݶʧϵͳϻ󡣱Ԥ“ԭ”ṩӢضʹñԤɵʧṩκεеκΡ
ӢضδδдԤı֤ӢضûȷʾʾᷢбԤӢضܲƳ뱾ԤݵԱԤκʹû뱾ԤصIJƷеȫκо򿪷еȫա
ӢضһǩЭṩԤԸԤʹͬʱܸЭԼ

ý嵣 ӢضʵýʽṩӢض֤ýӢضṩʮʱڲʵϵ覴áҵȱݣ뽫ý巵صӢضиӢضѡƷн

ų ֤֮⣬“ԭ”ṩκκȷ֤ҵԡȨضĿĵı֤ Ӣض˾ԱаκϢ֡ͼΡӻĿ׼ȷԻԲҲеΡ

ơ Ӣض乩Ӧ̾ʹû޷ʹñκ𺦣ʧҵжϻʧϢΣʹӢض֪Щ𺦵ĿԡijЩϽֹųĵȻżȻ𺦣ƿܻܲϽȨ һʾΪӢضƷ⣨ģ⣩豸ͱʹãӢضǸ⣨ģ⣩豸߻򴴽ߡⲢӢض֤ʹһ⣨ģ⣩豸ʱȷУӢضδƱ⣨ģ⣩豸Эͬϱ⣨ģ⣩豸Эͬʱ޷ȷͬԱ޷⣨ģ⣩豸ȷķճеȫΡͬ뱾⣨ģ⣩豸ʹصκβƷΡֱӻ⣨ʹӢضƻ챾ڹʧ⡢֧𺦡üʦѣӢض߼ְԱ֧߲ȷ䲻ʧ

δȨʹá ּڣȨκڱʱܻᵼ¸˺κϵͳӦóҽϵͳάϵͳϵͳȣκЩԻδȨ;ʹñͬԻδȨ;йصIJƷΡֱӻ⣨ʹӢضڲƻ췽ڹʧ⡢֧𺦡üʦѣ뱣ӢضְԱ֧߲ȷ䲻ʧ

Эֹ ΥЭӢضκʱֹЭ顣Эֹٱ򽫱иƷ黹Ӣض

÷ɣ ɴЭӦܼݷɹƣǷɵִԭͬ⣬ϹʻۺͬԼµôЭ顣Υõijڷɼ³ڱӢضκЭ鸺ΣӢضȨĴǩд

Ȩ ĵʹ˽˷ÿֻṩ“Ȩ”ʹáƻ򹫿 FAR 52.227-14 DFARS 252.227-7013 et seq. ơԱƷʹӦΪӢضԱȨԼ˻ΪӢض

ԣ룺 Э֮Ӣİ汾κ֮汾෭汾֮ĿĽΪṩӢİ汾Լ

޶ 201151510:56 ޶汾

DOCS/QUICK/CHS/note.gif0000755000000000000000000000073211651733270011433 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/CHS/qi_chs.htm0000755000000000000000000001052311656445636011771 0ustar Ӣض(R) ٰװָ

Ӣض® װ

װӢض PCIPCI-X PCI Express*

  1. ػγԴߡ
  2. ж¼ǣжIJ۵IJ۸ǡ
  3. Եι̲ۣʹ֮ȫλ̶֧ܹڻ䡣
  4. װػǡԴߡ

ע ЩӢǧλ̨ʽʹ PCI Express ߡʹһͷIJ۶κ⣬DzҪͼװһ PCI Express ͷ̵IJС

Ӣض® PRO/100 ǧλͭ » 10 Mbps 磬ʹ 3 ࡢ4 5 ˫̫TPE¡ 100 1000 Mbps κլ磬ʹ 5 ࣨ4 ԣ¡

SC Ӣض® ǧλ ж²ǡ 1000Base-SX ˫ SC ͹֧ϵ TX/RX ˿ڡ

LC Ӣض® ǧλ ж²ǡ LC 䲼Ӧ䣨1000BASE-SX 1000BASE-LXĹѧ䣬ƣʹ硡SCת¡

װָʾ

װ

Windows ϵͳ

ע⣺ԲϵͳйȨ޷ܰװ

  1. ⵽ʱWindows ߰װһ Windows פӲ 򵼡
  2. Ӳȡť
  3. Ӣض CDӢضӡ ԶгԶװ ť

Linux*

ҪĶ RPM* rpmbuild -tb <ļ.tar.gz>øľļ <ļ.tar.gz>

ע

  • Ҫʹ汾ȷУǰеں˵İ汾ñ밲װںԴ±ںˣӦϵͳ

  • RPM ܽ Red Hat ϲԹ

  • Ӣض PRO100 e100

  1. tar ļѡĿ¼磬ʹ '/home/username/e1000' '/usr/local/src/e1000'

  2. ѹõļ <x.x.x> ѹļİ汾ţ
    tar zxf e1000-<x.x.x>.tar.gz
  3. л src Ŀ¼£ <x.x.x> ѹļİ汾ţ
    cd e1000-<x.x.x>/src/
  4. ģ飺
    make install
    ļװΪ
    /lib/modules/<ں_汾>/kernel/drivers/net/e1000.o

    гİװλΪĬλáǶijЩ Linux ˵һȷ

  5. װģ飺
    insmod e1000 <>=<ֵ>
  6. ָ IP ַӿڿУ<x> ǽӿڿţ
    ifconfig eth<x> <IP ַ>
  7. ֤ӿУ<IP ַ>뱻ӿλͬһһ̨ IP ַ
    ping <IP ַ>

ϵͳ

Ҫװ򣬲μλϵûָ Ӣضͻ֧վ http://www.intel.com/p/zh_CN/support/

*Ϣ

޶ڣ 10/11/07 3:48p ޶汾14

DOCS/QUICK/CHS/style.css0000755000000000000000000000450511651733270011653 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/CHS/warranty.htm0000755000000000000000000000674611700566202012365 0ustar Ӳ

Ӳ

Ӣضԭʼӵ֤߱汾˰װƷڲϺ͹շȱݡ˵ڰװлʹò𻵵IJƷ

ϵκȷ򷨶ڲַ֪ʶȨҵԡضĿĻκν顢Ʒκε

˵ǸáżȻ¹ʡá졢ѡװԶ𻵵ƷֱƷȱݣӢضѸӲƷ߼Ʒͻľ̻ͻӢضṩ˻׼RMAţģ֤δעᣩӢض˻úַӢض⡣Ʒе𻵻ʧķաʹԭʼװͬ֧˷ѡ

ӢضʹµĻµIJƷ˻صƷ䲿ΪӢضIJƲƷ˻ظ汾ڻյIJƷúְ汾ӢضӢض൱ĵǰƷͣƷȨ

˻ȱݲƷ

ӱޣ

˻κƷ֮ǰӢضͻ֧ϵԻ˻׼RMAţ绰룺+1 916-377-7000

ͻ֧֤ӲƷȱݣǻ RMA Ϊ䷢ RMA ţ뽫ӲƷװϡӢضܽܰװû RMA ŵκβƷ

ص㣺

Ʒ˻عԻ˿

Ӣض˿֤ڱޣ

ӢضϣԹӢضȫ⡣ڹƷʮ90ڽӢضصԭַԻȡӹӦ̴ʱȫ˿˻ͷ˿ķ̺ʹ̿ɽӢض˻ԭ򴦡Ӣض֤߽˻˻ֱӢضĿͻ

κ⳥

ӢضĶνֱӵĿɿ͹۲ʧκ£κμԻͶʧǰġԡżȻԺʧַ֪ʶȨعɱʹʧҵжϡʧʧʧںͬȨĻǸκεҲӢضǷȱ֪ͨʧĿԣӢضŲ𡣾ˣӢضڱЭ涨ܽӦԲƷ֧ļ۸ЩڿεDzƷ۵ҪءӢضеҲδȨκ˳еκΡ

ijЩݲųżȻԻʧƿܲ

ؼԿӦã Ӣضر֤߻ְ֤ڹؼԿӦУΪȫ򽡿ϵͳԭܿϵͳ߿л潻ͨϵͳʹñƷӢضŲķȫûе֤ͬ⣬ά⳥֧Ӣض֤߻¼֤ڴӦʹñƷκҪ

뱾һṩӲ֮Сйκ飬ıƷ֤Э顣

޶ 2002 7 23 10:42 ޶汾6

DOCS/QUICK/CHT0000755000000000000000000000000011761422164007713 5ustar DOCS/QUICK/CHT/legaldis.htm0000755000000000000000000000156311730046352012275 0ustar k߸T

ۧ@vMkn

ۧ@v © 2002 - 2012 Intel CorporationCOd@vQC

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Intel q糧󤤪~βtdCIntel 礣惡B]tTsӿաC

IntelBItanium P Pentium Intel qbHΨLaӼСC

* 䥦W٩M~Pi~gŧiLҦ̤]C

OTT

nv

 

W׭q 2011/1/25AU 10:21 ׭q DOCS/QUICK/CHT/license.htm0000755000000000000000000002304611730046352012133 0ustar nv

INTEL nvX

n - ƻsBw˩ΨϥΫeХ\ŪC

ԲӾ\ŪHUکM󤧫eAФŽƻsBwˡBΨϥΥvX (²١uXѡv) ҤUѪonM (`١unv)C

unƻsBw˩ΨϥΦunvANܱzPNuuXѡvڡCpGzPNuXvڡAФnƻsBwˡBΨϥΦunvC

vѡG

Ъ`NG

  •  pGzOΨtκ޲zAHUu{vѡvAΩzC
  •  pGzO@ϥΪ̡AHUu@ϥΪ̱vѡvAΩzC
  •  pGzOl]ƻsyt (OEM)AHUuOEM vѡvAΩzC

{vG ziHNunvƻszqqHKbqϥΡA]iHƻsXzƥتunv ƥƥAOݨUC󭭨G

  1. unvvȭX֨ϥΩ (a) Intel 󲣫~BH (b) ("") ˸mAoظ˸m]pb檺uXȡv@~tΥݥH Intel 󲣫~e{CunvLϥΤ覡A]A () D Intel 󲣫~Abvd򤺡C
  2. buXѡvҦڤαWdUAIntel Corporation (² "Intel") ¤zDMݡBiuơvϥεۧ@vC
  3. FuXvX~AziH惡unv󳡥iƻsBקBXBPBteBζǿAåBAz]PNnwunvgvƻspo͡C
  4. ziHϦVu{BѽsBΩѦunvC
  5. unvi]Aڤ]w󦹪ADZڳ]ߦbHdzѪvѤC

@ϥΪ̱v G ziHNunvƻs@qWAzӤHγ~AåBiHs@@unvƥƥAݭnUC󪺭G

  1. unvvȭX֨ϥΩ (a) Intel 󲣫~BH (b) ("") ˸mAoظ˸m]pb檺uXȡv@~tΥݥH Intel 󲣫~e{CunvLϥΤ覡A]A () D Intel 󲣫~Abvd򤺡C
  2. buXѡvҦڤαWdUAIntel Corporation (² "Intel") ¤zDMݡBiuơvϥεۧ@vC
  3. FuXvX~AziH惡unv󳡥iƻsBקBXBPBteBζǿAåBAz]PNnwunvgvƻspo͡C
  4. ziHϦVu{BѽsBΩѦunvC
  5. unvi]Aڤ]w󦹪ADZڳ]ߦbHdzѪvѤC

OEM vG zȯHz~@ξXBz~{@ϥΪ̰Wߦunv@s (䥦Wߦ~~)BΥHjunvǻ (]AAAǻw˼vγXȵv) ӹ惡unviƻsMǻAݿuoDZWwG

  1. unvvȭX֨ϥΩ (a) Intel 󲣫~BH (b) ("") ˸mAoظ˸m]pb檺uXȡv@~tΥݥH Intel 󲣫~e{CunvLϥΤ覡A]A () D Intel 󲣫~Abvd򤺡C
  2. buXѡvҦڤαWdUAIntel Corporation (² "Intel") ¤zDMݡBiuơvϥεۧ@vC
  3. FuXvX~AziH惡unv󳡥iƻsBקBXBPBteBζǿAåBAz]PNnwunvgvƻspo͡C
  4. ziHϦVu{BѽsBΩѦunvC
  5. zȯھڮѭvXNunvtezȤCvXiରu (break-the-seal)vvXCvܤO@ Intel 惡unvҦvC
  6. unvi]Aڤ]w󦹪ADZڳ]ߦbHdzѪvѤC

vC ziHG (i) FuXvѻ~AziHϥΩνƻsuơvF(ii) Nuơv~ĤTF(iii) g Intel TѭPNAiHouijѡvuơvF(iv) Fuijѡvѻ~AiHγקBsBĶuơvF(v) iHϦVu{BѽsBΩѦuơvF(vi) խקܰʳWduơvγ~vgz`\F(vii) FuXѡvѻ~ANuơvBuiAǻơvBMudҨӷXvHέlͤe󤸥󪺡uӷXvǻBAvBĤTC

LLvQC DuXvҴѪTvQA_hLשܩηtܡAIntel ¤z Intel ֦α]vTαMQBۧ@vBn@~BӼСBӷ~KΨLz]vvQαvCBTzH~ASvv|γzLqܡB޻BT½ѩΨL覡¤zCSOOAb Intel qBۧ@vBӼСBΨ䥦z]vWdUAIntel ¤zܩηtܪvQC

nҦvMۧ@vC unvOvϥΡAO_CunvҦƥҦv IntelCunvMLaۧ@vMkߡAHΰڱҫO@CziHunvۧ@v`NƶCzPNwLH惡unvi楼gvƻsCIntel i|HɦbtqpUA惡unvΦBΪضiASunvi䴩ΧsqȡCߦb̧PNuoDZڳWwAåBzSOdunvƥpUAz~iHNunvLHC

wn骺䥦ڡC pGھڥuXѡvWdUw˩ΨϥΪunvOwӷ~μХܬunvuեΪv("wn")AHUڴNAΩzC

wunvApGuϬqvһPuXѡvکαĬAuϬqveWV䥦کα󪺮ĤOAĤOȭѨMĬ𪺥ndC
zFѨû{unvOwunvAäN Intel Ѫ̲סunvA䤤i]t~M䥦iyƿ򥢡BtάG١BΨ䥦~DCwunvHuˡvѡA]ϥιwunvҤް_l`AIntel bŧGKOTγdC
z{ Intel |ӿեӱN|XwunvAåB Intel zSܩηtܪqȭnXwunvBӥB Intel iण|XPwunvۮeunvCz{Az檺sζ}oYPwunvBΪ̨ϥλPwunv~isζ}oӬsIѱzۦӾC
pG Intel ̷ӥt~@ѭXѪeѱzwunvAz惡wunvϥΤ]ݭn즹XѪWdC

COTC pGunvO Intel HC鴣ѡAIntel OҦCb Intel eXEQѤ|ƤW岫CpGo{岫AбNCeٵ Intel HK Intel ܭnsΥH䥦keunvzC

LOTKC DpHWҴѡAunv̡u{pvѦӤtܩηtܤOA]AAʡBI`LHvqBξAXYإγ~OC Intel Oҥ礣Ӿᦹunvҥ]tTBrBϤBsΨLؤTΧʡC

dC b󱡪pUAINTEL Ψӳ]ϥΥ~εLkϥΥ~Ҳͪl`A (]AAȭAQlB~_BθT) tdAY INTEL wgDl`iʥOpC]YǥqkҰϤ\tܫOToηN~ladKέAҥHAHWiणAΩzCHzҦbҰϦөwAzi٦䥦kvQC X֨ϥΡunvM (“”) ˸m (]pتOnH Intel 󲣫~e{) ɡAzT{ Intel JO (“”) ˸m@̡A]Oгy̡CzFѨû{Aft ("") ˸mϥήɡAunvTϥ Intel ܡBIntel ]punvNOnX (“”) ˸mϥΡBåBApGX (“”) ˸mϥΡAunviLk`ާ@CX (“") ˸mϥήɡAzPNӾunviLk`@~ICzPNO٩M@ Intel Ψ䰪¾BlqBΪݤq|]unvX (") ˸mϥγy󪽱ζ~dBӤHˮ`BΦ`vӤް_ҦߡBOΡBl`B}PBHΫ߮vOӨˮ`AYϦv Intel bunv]pλsyWҲOpC

vϥΡC n骺]pBNϡBαvγ~OϥΩnGٴNiyӤH˩Φ` (ҦpAtΡBͨtΡBαϥͨt) tΩθ˸mCzYѩWzDwwΫDvγ~ӨϥΡunvAzO٨ëO Intel ΨDƪ̡BlqΪݾcAݩӾ]DwwΫDvγ~Ҭ󲣫~dBHˮ`Φ`nAӪζͤҦvQDiBBl`BXAHΦXz߮vOΡAYϳonź Intel b]pλsy Client ɦҲPC

XѲפC pGzHϨڳWwAIntel HɥiHפuXvCXפAzߨPunvαNҦunvƥ IntelC

AΪkߡC תk߽ĬhA̷ӦuXvWdް_vץѥ[{kߺ޲zCzPNupXꤽvufP⫴vAΩ󦹡uXѡvCziHHϾAΪ~PkMWw~PunvCDgv Intel NHѭܨñWA_hA׮ھڥXAIntel SdθqȡC

FvQC WunvMOpHX}oAHuvQvѨϥΡCuFvϥΡBƻsBo FAR52.227-14 M DFAR252.227-7013 ΨWwCuFvϥΦ~Ncӻ{ Intel 惡unvMvCӥ]өλsytӬO IntelC

yF½ĶC pGuXv^媩H䥦y½ĶA½ĶȥHKϥάتѡA@ӥH^媩DC

W׭q 2011/5/15AU 10:56 ׭q

DOCS/QUICK/CHT/note.gif0000755000000000000000000000073211651733270011434 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/CHT/qi_cht.htm0000755000000000000000000001101411546611560011754 0ustar Intel® dֳtw˫n

Intel® dw

w Intel PCIBPCI-XB PCI Express* d

  1. qéޤUquC
  2. q~ߡAñqŦXdѲdKC
  3. íTaNdtYJ PCI ѡA짹JCN[TwcC
  4. Nq~߸˦^CJquC

`NG Intel Gigabit AMWd|ϥ PCI t׬yơCziHϥΤ񤶭ds٭nѡAoˤ|yˮ`AOФnէפj󴡼Ѫ PCI tsw˨촡ѤC

Wlu

Intel® PRO/100 P Gigabit ɽudG b 10 Mbp ϥO 3B4 5 "A (TPE) lu"AñNlus줶dCb 100 1000 Mbps Maκϥ O 5lu (4 )C

t SC Y Intel® Gigabit ֤dG Uçsֳs~ߡCNH 1000 ¦ SX SC ֱYJtdج[W TX/RX s𤺡C

t LC Y Intel® Gigabit ֤dG Uçsֳs~ߡCNAΩztdTlu LC YJtd]1000BASE-SX 1000BASE-LX)CpGluWPtd۲ (]A׳W)AhiѦұNlu䥦Y (Ҧp SC)C

ҰʹqÿӥHUXʵ{w˻C

wXʵ{

Windows @~t

Ъ`NAz@wn@~tΪ޲zv~wXʵ{C

  1. 줶dAWindows |w Windows `nXʵ{αҰuMsWwv FC
  2. pGuMsWwvFҰʮɡAЫuvsC
  3. J Intel CDCIntel su۰ʰ{|۰ʱҰʡC@UuwXʵ{Mnv sC

Linux*

nإ߳oXʵ{Gi RPM* ʥ]Aа 'rpmbuild -tb <filename.tar.gz>'CXʵ{SwɮצW٨N <filename.tar.gz>C

`NG

  • nϫإ߾A@~Aثe檺֤߻Pw˪֤ߨӷβպA@wn۲šCpGz譫ssĶ֤ߡAаWsҰʨtΡC

  • RPM \ʶȦb Red Hat ǻչLC

  • YO Intel PRO/100 dAШϥ e100 Xʵ{W١C

  1. N¦Xʵ{ tar ɮײzܪؿCҦpAϥ '/home/username/e1000' '/usr/local/src/e1000'C

  2. tar/YӰOɡAB <x.x.x> OXʵ{ tar ɮתXG
    tar zxf e1000-<x.x.x>.tar.gz
  3. ܧXʵ{ src ؿA䤤 <x.x.x> OXʵ{ tar XG
    cd e1000-<x.x.x>/src/
  4. sĶXʵ{ҲաG
    make install
    GiɮױNQwˬG
    /lib/modules/<kernel_version>/kernel/drivers/net/e1000.o

    WCw˦mOw]mCǦmYǯSw Linux ǻӻiणTC

  5. w˼ҲաG
    insmod e1000 <parameter>=<value>
  6. JHUOӫ IP }A䤤 <x> OXG
    ifconfig eth<x> <IP_address>
  7. TwiHA@~CJHUOA䤤 <IP_address> OgLիAbP@lBnWt~@q IP }G
    ping <IP_address>

䥦@~t

Ynw˨䥦Xʵ{AаѾ\mϥΪ̫nn n󤶭d CD AΪ̱ziY{Ȥ䴩G http://www.intel.com/p/zh_TW/support/C

*k߸T

W׭q 2007/10/11 3:48p ׭q 14

DOCS/QUICK/CHT/style.css0000755000000000000000000000450511651733270011654 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/CHT/warranty.htm0000755000000000000000000000724011700574640012361 0ustar ɶwOT

ɶwOT

Intel VҦ̫OҡAboӥ]ˤd~A|ƩMuW岫CpGӤd~bw˴lΨϥΤAKboOT[d򤺡C

WzOTiHN䥦ެOܡBtܩΪkwOTA]A]ȭ^z]DIǩʡBSγ~APʡBAΩʫOTBΦ]ijBWνdΪOTC

oOT[\]ݥΡBN~B~ΡBBB״_BaBw˩Τըld~󴫡CpGo{d~岫AIntel |ۦܧKO󴫩έ״_w鲣~AOHU]ߪp~AΪ̬OApGzѸӤd~Mh٧Ʊv (RMA) X (аѦҥHU) HʶRҩ (pG|U) zʶR~sө IntelAôѷ岫A]iHhٱzʶRBCpGzBeӤd~Ah]lο򥢪ICz@wnϥέӪe]ά۵^äIBeOΡC

Intel i|ΥsνվLsӧ󴫩έ״_Ӥd~AåBA Intel b󴫪d~Ϊ̬Os󳣦 Intel ]C״_Χ󴫪d~A| Intel ܥHɪۦPΧ󰪪eٵzCIntel OdΥثe۵d~󴫤򲣤d~vQC

hٷ岫~

_aϡG

h٥󤶭d~eAХqܨ +1 916-377-7000 sIntel Ȥ䴩èoh٧Ʊv]RMA^XC

pGȤ䴩sաTwӤd~岫AL̷| RMA o@ RMA XzKbd~]˥~C]ˤWS RMA XAIntel N౵󲣫~C

䥦aIG

Nd~zʶRBHohکΧ󴫫~C

Intel dhګOҡ]ȭ_aϡ^

Intel ƱzzʶR Intel d~NCqʶR_EQ]90^ѤɭԡAziHNz Intel dʶRBAqsӳBoʶRBBhڡCӧOhfðhڵӧOȤ᪺APөMtPӥiN Intel dhٵL̪ʶRBCIntel OұNھڦFhfñNʶRBhٵV Intel ʶRȤC

dMvk

INTEL bߤ@d󪽱B[iqalCb󱡪pUAINTEL Ҥ󶡱βqʪl`td]]AoʡBN~BMSl`^]AAȭAIǴz]vBAʶROΡBLkϥΡBӷ~_BhABHQlo]BHϡBήھڥOTް_alAY INTEL ƥwo즹aliʳqOpC׫eO_פΡAھڦXAINTEL ߪ`dNWLӲ~ICoǼbdO~]wnCINTEL qwαvHӾ䥦dC

YǦ{\ưέN~olaA]AWziणAΩzC

nε{G Intel SOn v̡ Av̡ bnε{ (]AAȭ|ҨϥΡAwʩΰdUtΡB֯౱tΡBΪŤΦaqt) ϥΦd~tdAϥΪ̥惡إγ~Ӿ᧹ICv̡ PNO@BO١Bä Intel ] v̡ Av̡ HΤ覡ϥΤd~Ӥް_MҦ߶ˮ`C Av̡C

nG Hd~Ѫn餣bWzwOT[\dCаѦHd~ѪAγnvXѥHnOTԲӸơC

W׭q 2002 ~ 7 23 W 10:42 6

DOCS/QUICK/DEU0000755000000000000000000000000011761422164007712 5ustar DOCS/QUICK/DEU/legaldis.htm0000755000000000000000000000207011730046352012266 0ustar Rechtliche Hinweise

Copyright und rechtliche Beschrnkungen

Copyright © 2002 2012 Intel Corporation. Alle Rechte vorbehalten.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Intel Corporation bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesem Dokument. Auerdem macht Intel keinerlei Zusagen, dessen Inhalt zu aktualisieren.

Intel, Itanium und Pentium sind Marken der Intel Corporation in den USA und anderen Lndern.

*Andere Marken oder Produktnamen sind Eigentum der jeweiligen Inhaber.

Garantie-Informationen

Software-Lizenz

 

Stand: 25.01.2011 22:21 Revision DOCS/QUICK/DEU/license.htm0000755000000000000000000004165611730046352012141 0ustar Software-Lizenz

INTEL SOFTWARE-LIZENZVEREINBARUNG

WICHTIG BITTE LESEN SIE DIESE VEREINBARUNG VOR DEM KOPIEREN, INSTALLIEREN ODER VERWENDEN DER SOFTWARE.

Lesen Sie die folgenden Nutzungsbedingungen, bevor Sie diese Software oder zugehrige Ressourcen (gemeinsam als Software“ bezeichnet), die unter dieser Lizenzvereinbarung (Vereinbarung“) bereitgestellt werden, kopieren, installieren oder verwenden.

Durch Kopieren, Installieren oder anderweitigen Einsatz der Software erklren Sie sich mit den Bestimmungen dieser Vereinbarung einverstanden. Wenn Sie die Bedingungen dieser Vereinbarung nicht akzeptieren, drfen Sie die Software nicht kopieren, installieren oder einsetzen.

LIZENZEN:

Bitte beachten Sie:

  • Wenn Sie Netzwerk- oder Systemadministrator sind, trifft die unten stehende Standortlizenz auf Sie zu.
  • Wenn Sie Endbenutzer sind, trifft die Einzelbenutzerlizenz auf Sie zu.
  • Wenn Sie ein Originalgertehersteller oder OEM sind, gilt die OEM-Lizenz“.

STANDORTLIZENZ: Sie drfen die Software auf Computer Ihrer Organisation zum firmeninternen Gebrauch kopieren und von der Software unter folgenden Bedingungen eine angemessene Anzahl an Sicherungskopien erstellen:

  1. Diese Software ist nur lizenziert fr den Gebrauch mit (a) physischen Intel Komponenten und (b) virtuellen (emulierten“) Gerten, die dafr konzipiert sind, dass sie von einem auf einer virtuellen Maschine ausgefhrten Gastbetriebssystem als Intel Komponente erkannt werden. Jeder anderweitige Gebrauch der Software, einschlielich Gebrauch mit nicht von Intel hergestellten Komponenten, fllt nicht unter diese Lizenzvereinbarung
  2. Vorbehaltlich aller Bedingungen dieses Vertrags erteilt Ihnen die Intel Corporation (Intel“) eine einfache, nicht bertragbare Lizenz unter Einhaltung der Urheberrechte von Intel fr den Einsatz des Materials.
  3. Kein Teil der Software darf auer wie in dieser Vereinbarung festgelegt kopiert, modifiziert, vermietet, verkauft, verteilt oder bertragen werden, und Sie erklren sich damit einverstanden, ein unberechtigtes Kopieren dieser Software zu verhindern.
  4. Sie drfen die Software nicht nachbauen, dekompilieren oder disassemblieren.
  5. Die Software kann Teile umfassen, die zustzlichen Bedingungen zu den hier ausgefhrten unterliegen und in einer eigenen Lizenz ausgefhrt sind, die diesen Teilen beiliegt.

EINZELBENUTZERLIZENZ: Sie drfen die Software auf einen einzelnen Computer fr Ihren persnlichen Gebrauch kopieren und von der Software unter folgenden Bedingungen eine Sicherungskopie erstellen:

  1. Diese Software ist nur lizenziert fr den Gebrauch mit (a) physischen Intel Komponenten und (b) virtuellen (emulierten“) Gerten, die dafr konzipiert sind, dass sie von einem auf einer virtuellen Maschine ausgefhrten Gastbetriebssystem als Intel Komponente erkannt werden. Jeder anderweitige Gebrauch der Software, einschlielich Gebrauch mit nicht von Intel hergestellten Komponenten, fllt nicht unter diese Lizenzvereinbarung
  2. Vorbehaltlich aller Bedingungen dieses Vertrags erteilt Ihnen die Intel Corporation (Intel“) eine einfache, nicht bertragbare Lizenz unter Einhaltung der Urheberrechte von Intel fr den Einsatz des Materials.
  3. Kein Teil der Software darf auer wie in dieser Vereinbarung festgelegt kopiert, modifiziert, vermietet, verkauft, verteilt oder bertragen werden, und Sie erklren sich damit einverstanden, ein unberechtigtes Kopieren dieser Software zu verhindern.
  4. Sie drfen die Software nicht nachbauen, dekompilieren oder disassemblieren.
  5. Die Software kann Teile umfassen, die zustzlichen Bedingungen zu den hier ausgefhrten unterliegen und in einer eigenen Lizenz ausgefhrt sind, die diesen Teilen beiliegt.

OEM-LIZENZ: Die Software darf nur als wichtiger Bestandteil Ihres Produkts bzw. integriert in Ihr Produkt oder als Standalone-Softwareaktualisierung zur Wartung fr bestehende Endanwender Ihrer Produkte unter Ausschluss aller anderen Standalone-Produkte, oder als Komponente einer greren Softwareverteilung, einschlielich der Verteilung eines Installations-Images oder eines Gast-VM-Images, reproduziert und verteilt werden, und zwar unter Vorbehalt folgender Bedingungen:

  1. Diese Software ist nur lizenziert fr den Gebrauch mit (a) physischen Intel Komponenten und (b) virtuellen (emulierten“) Gerten, die dafr konzipiert sind, dass sie von einem auf einer virtuellen Maschine ausgefhrten Gastbetriebssystem als Intel Komponente erkannt werden. Jeder anderweitige Gebrauch der Software, einschlielich Gebrauch mit nicht von Intel hergestellten Komponenten, fllt nicht unter diese Lizenzvereinbarung
  2. Vorbehaltlich aller Bedingungen dieses Vertrags erteilt Ihnen die Intel Corporation (Intel“) eine einfache, nicht bertragbare Lizenz unter Einhaltung der Urheberrechte von Intel fr den Einsatz des Materials.
  3. Kein Teil der Software darf auer wie in dieser Vereinbarung festgelegt kopiert, modifiziert, vermietet, verkauft, verteilt oder bertragen werden, und Sie erklren sich damit einverstanden, ein unberechtigtes Kopieren dieser Software zu verhindern.
  4. Sie drfen die Software nicht nachbauen, dekompilieren oder disassemblieren.
  5. Sie drfen die Software nur in bereinstimmung mit einer schriftlichen Lizenzvereinbarung an Ihre Kunden vertreiben. Bei einer derartigen Lizenzvereinbarung kann es sich um eine Break the seal“ Lizenzvereinbarung handeln, d.h. um eine Lizenz, die mit ffnen der Verpackung oder CD-Hlle in Kraft tritt. Als Mindestvoraussetzung muss die Lizenz Intels Eigentumsrechte an der Software wahren.
  6. Die Software kann Teile umfassen, die zustzlichen Bedingungen zu den hier ausgefhrten unterliegen und in einer eigenen Lizenz ausgefhrt sind, die diesen Teilen beiliegt.

LIZENZEINSCHRNKUNGEN. Sie drfen NICHT: (i) das Material auf andere Weise als in diesem Vertrag vereinbart einsetzen oder kopieren; (ii) das Material an eine beliebige Drittpartei vermieten oder verpachten; (iii) diesen Vertrag oder das Material ohne ausdrckliche schriftliche Genehmigung von Intel bertragen; (iv) das Material in seiner Gnze oder Teile davon verndern, bearbeiten oder bersetzen, auer wie in diesem Vertrag vorgesehen; (v) das Material zurckentwickeln, dekompilieren oder disassemblieren; (vi) versuchen, die normale Funktion eines Lizenzmanagers, der den Einsatz des Materials steuert, abzundern oder zu manipulieren; (vii) das Quellcode-Format irgendwelcher Komponenten des Materials, der neu verteilbaren Dateien und der Beispielsquelle und alle Ableitungen davon auer wie in diesem Vertrag vorgesehen an eine Drittpartei verbreiten, in Unterlizenz vergeben oder bertragen.

KEINE ANDEREN RECHTE. Es werden Ihnen von Intel keine anderen Rechte oder Lizenzen, sei es ausdrcklich oder konkludent, in Bezug auf die proprietren Informationen oder Patente, Urheberrechte, Topographien, Marken, Betriebsgeheimnisse oder andere Rechte an geistigem Eigentum erteilt, die Intel gehren oder von Intel kontrolliert werden, sofern dies nicht ausdrcklich in dieser Vereinbarung erwhnt ist. Soweit nicht ausdrcklich hier angegeben, werden Ihnen weder ausdrcklich noch konkludent Lizenzen oder Rechte gewhrt bzw. eingerumt. Intel gewhrt Ihnen keine ausdrcklichen oder konkludenten Rechte an Patenten, Urheberrechten und Marken von Intel oder andere Rechte an geistigem Eigentum.

EIGENTUM AN SOFTWARE UND URHEBERRECHTEN. Fr die Software wird eine Lizenz gewhrt; sie wird nicht verkauft. Das Eigentum aller Kopien der Software verbleibt bei Intel. Die Software ist urheberrechtlich und durch die Gesetze der Vereinigten Staaten von Amerika und anderer Lnder sowie durch internationale Abkommen geschtzt. Urheberrechtshinweise drfen nicht aus der Software entfernt werden. Sie erklren hiermit Ihr Einverstndnis, das unerlaubte Kopieren der Software zu verhindern. Intel kann die Software oder darin erwhnte Elemente jederzeit und ohne Vorankndigung ndern. Intel ist jedoch nicht dazu verpflichtet, die Software zu untersttzen oder zu aktualisieren. Sie drfen die Software nur bertragen, wenn sich der Empfnger uneingeschrnkt mit diesen Bedingungen einverstanden erklrt, und Sie keine Kopien der Software behalten.

ZUSTZLICHE BEDINGUNGEN FR PRE-RELEASE-SOFTWARE. Wenn die Software, die Sie unter dieser Vereinbarung installieren oder verwenden, eine nicht kommerziell vertriebene Pre-Release-Version ist oder als Alpha“- oder Beta“-Version der Software (Pre-Release-Software“) gekennzeichnet ist, gelten folgende Bedingungen.

Sollte eine Bedingung in diesem Abschnitt in Bezug auf Pre-Release-Software in Widerspruch zu anderen Bedingungen dieser Vereinbarung stehen, so ersetzt dieser Abschnitt die anderen Bedingungen, aber nur in dem Ausma, wie es zur Vermeidung des Widerspruchs erforderlich ist.
Sie verstehen und erkennen an, dass es sich bei dieser Software um Pre-Release-Software und nicht die endgltige Software von Intel handelt. Sie kann Fehler und andere Probleme aufweisen, die zu Datenverlust, Systemausfall oder anderen Fehlern fhren knnen. Die Pre-Release-Software wird wie besehen“ bereitgestellt und Intel schliet jegliche Garantie oder Haftung fr Schden, die aus dem Gebrauch der Pre-Release-Software entstehen knnen, aus.
Sie erkennen an, dass Intel keine Zusage gemacht hat, in Zukunft Pre-Release-Software zu verffentlichen und dass Intel Ihnen gegenber keine ausdrckliche oder konkludente Verpflichtung zur Verffentlichung der Pre-Release-Software hat und dass Intel mglicherweise keine Software verffentlicht, die mit der Pre-Release-Software kompatibel ist. Sie stimmen zu, dass die Gesamtheit aller Forschungs- und Entwicklungsarbeiten, die Sie in Zusammenhang mit der Pre-Release-Software oder einem Produkt, das die Pre-Release-Software nutzt oder damit verknpft ist, durchfhren, auf Ihr eigenes Risiko erfolgt.
Wenn Intel Ihnen entsprechend einer eigenen schriftlichen Vereinbarung Pre-Release-Software zur Verfgung gestellt hat, unterliegt Ihr Gebrauch der Pre-Release-Software ebenfalls dieser Vereinbarung.

BESCHRNKTE GARANTIE FR DATENTRGER. Wenn die Software von Intel auf einem Datentrger geliefert wurde, garantiert Intel fr einen Zeitraum von neunzig Tagen nach der Lieferung durch Intel, dass der Datentrger frei von Materialschden ist. Falls der Datentrger beschdigt ist, knnen Sie ihn an Intel zurckgeben. Intel entscheidet in diesem Fall, ob der Datentrger ersetzt oder ob die Software auf einem anderen Weg an Sie ausgeliefert wird.

AUSSCHLUSS ANDERER GARANTIEN. MIT AUSNAHME DER OBEN GENANNTEN GARANTIE WIRD DIE SOFTWARE IM VORLIEGENDEN ZUSTAND UND OHNE AUSDRCKLICHE ODER STILLSCHWEIGENDE GARANTIEN JEDER ART, EINSCHLIESSLICH FR DEN HANDELSWERT, DIE EINHALTUNG DER RECHTE VON DRITTEN ODER DIE EIGNUNG FR EINEN BESTIMMTEN ZWECK, GELIEFERT. Intel bernimmt keine Garantie oder Verantwortung fr die Richtigkeit oder Vollstndigkeit der Informationen, des Texts, der Grafiken, Verknpfungen oder anderer Elemente, die in der Software enthalten sind.

HAFTUNGSBESCHRNKUNG. UNTER KEINEN UMSTNDEN HAFTEN INTEL ODER DRITTHERSTELLER FR IRGENDWELCHE SCHDEN (EINSCHLIESSLICH UND UNEINGESCHRNKT ALLE GEWINNVERLUSTE, BETRIEBSUNTERBRECHUNGEN ODER INFORMATIONSVERLUSTE), DIE DURCH DIE VERWENDUNG ODER DIE NICHTVERWENDBARKEIT DER SOFTWARE AUFTRETEN; DIES GILT AUCH FR FLLE, IN DENEN INTEL AUF DIE MGLICHKEIT SOLCHER SCHDEN HINGEWIESEN WURDE. IN EINIGEN GERICHTSBARKEITEN IST DER AUSSCHLUSS ODER DIE EINSCHRNKUNG DER HAFTUNG FR STILLSCHWEIGENDE GEWHRLEISTUNGEN ODER FR MITTELBARE BZW. BEILUFIG ENTSTANDENE SCHDEN NICHT ZULSSIG, SO DASS DIE OBEN AUFGEFHRTE EINSCHRNKUNG MGLICHERWEISE AUF SIE NICHT ZUTRIFFT. SIE HABEN UNTER UMSTNDEN NOCH ANDERE RECHTE, DIE JE NACH GERICHTSBARKEIT VARIIEREN KNNEN. Fr den Fall, dass Sie die Software in Verbindung mit einem virtuellen (emulierten“) Gert verwenden, das so konzipiert ist, dass es als Intel Komponente erkannt wird, erkennen Sie an, dass Intel weder der Urheber noch der Hersteller des virtuellen (emulierten“) Gerts ist. Sie verstehen und erkennen an, dass Intel keine Zusicherungen ber den korrekten Betrieb der Software macht, wenn diese mit einem virtuellen (emulierten“) Gert verwendet wird, dass Intel die Software nicht fr den Betrieb mit einem virtuellen (emulierten“) Gert entwickelt hat und dass die Software mglicherweise in Verbindung mit einem virtuellen (emulierten“) Gert nicht korrekt funktioniert. Sie stimmen zu, das Risiko zu bernehmen, dass die Software mglicherweise in Verbindung mit einem virtuellen (emulierten“) Gert nicht korrekt funktioniert. Sie stimmen zu, dass Sie Intel und seine Geschftsfhrer, Niederlassungen und verbundenen Unternehmen von allen Ansprchen, Kosten, Schden, Auslagen sowie Anwaltskosten freistellen, die sich direkt oder indirekt aus einem Anspruch auf Produkthaftung, Krperverletzung oder Tod ergeben und im Zusammenhang mit dem Gebrauch der Software in Verbindung mit einem virtuellen (emulierten“) Gert stehen, selbst dann, wenn im Anspruch vorgebracht wird, dass Intel im Design oder der Herstellung der Software fahrlssig handelte.

UNBEFUGTER GEBRAUCH. DIE SOFTWARE WURDE NICHT FR DEN EINSATZ IN SYSTEMEN ODER ANWENDUNGEN KONZIPIERT, IN DENEN DER AUSFALL DER SOFTWARE ZU PERSONENVERLETZUNG ODER LEBENSBEDROHLICHEN SITUATIONEN FHREN KNNTE (Z. B. IN MEDIZINISCHEN SYSTEMEN ODER LEBENSRETTUNGS- ODER LEBENSERHALTUNGSSYSTEMEN). Sollten Sie die Software fr solche nicht vorgesehenen oder nicht genehmigten Zwecke einsetzen, stellen Sie Intel und seine Geschftsfhrer, Niederlassungen und verbundenen Unternehmen von allen Ansprchen, Kosten, Schden, Auslagen sowie Anwaltskosten frei, die sich direkt oder indirekt aus einem Anspruch auf Produkthaftung, Krperverletzung oder Tod ergeben und in Verbindung mit dem nicht vorgesehenen oder nicht genehmigten Einsatz stehen, selbst dann, wenn im Anspruch vorgebracht wird, dass Intel im Design oder der Herstellung dieses Teils fahrlssig handelte.

BEENDIGUNG DIESER VEREINBARUNG. Diese Vereinbarung kann von Intel jederzeit beendet werden, wenn Sie die genannten Bestimmungen nicht einhalten. Wird die Vereinbarung beendet, sind Sie dazu verpflichtet, die Software entweder umgehend zu lschen oder alle Kopien der Software an Intel zurckzugeben.

ANWENDBARES RECHT. Ansprche, die im Rahmen dieser Vereinbarung erhoben werden, unterliegen dem Recht des US-Bundesstaats Kalifornien, ungeachtet der Prinzipien zur Gesetzeskollision. Sie erklren sich damit einverstanden, dass das bereinkommen der Vereinten Nationen ber Vertrge ber den internationalen Warenkauf in Bezug auf diesen Vertrag nicht zutrifft. Sie drfen die Software nicht exportieren, wenn der Export gegen geltende Exportgesetze und -bestimmungen verstt. Intel ist an keine anderen Vereinbarungen gebunden, es sei denn, sie liegen in schriftlicher Form vor und wurden von einem autorisierten Reprsentanten von Intel unterzeichnet.

EINGESCHRNKTE RECHTE DER US-REGIERUNG. Die im Lieferumfang enthaltene Software und Dokumentation wurden mit privaten finanziellen Mitteln entwickelt und werden mit EINGESCHRNKTEN RECHTEN“ bereitgestellt. Die Verwendung, Vervielfltigung oder Verffentlichung durch Regierungsbehrden unterliegt den Bestimmungen, die in FAR 52.227-14 und DFARS 252.227-7013 ff. oder einer entsprechenden Aktualisierung aufgefhrt sind. Die Verwendung dieses Produkts durch US-Regierungsbehrden erfolgt unter Anerkennung der diesbezglichen Eigentumsrechte von Intel. Auftraggeber oder Hersteller ist Intel.

SPRACHE; BERSETZUNGEN. Sollte die englische Version dieses Vertrags zusammen mit einer in eine andere Sprache bersetzten Version ausgeliefert werden, dient diese bersetzte Version ausschlielich zu Informationszwecken; die englische Version ist die einzige rechtsgltige Version.

Zuletzt berarbeitet 15.05.2011 22:56 Revision

DOCS/QUICK/DEU/note.gif0000755000000000000000000000073211651733270011433 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/DEU/qi_deu.htm0000755000000000000000000001462111546611560011761 0ustar Schnellinstallationsanleitung fr Intel(R) Netzwerkadapter

Installation von Intel® Netzwerkadaptern

Installation des Intel PCI, PCI-X oder PCI-Express* Adapters

  1. Schalten Sie den Computer aus und ziehen Sie den Netzstecker aus der Steckdose.
  2. Entfernen Sie die Computerabdeckung und die Blende des Adaptersteckplatzes, der fr Ihren Adapter passt.
  3. Drcken Sie die Kontaktseite des Adapters fest in den Steckplatz hinein, bis sie vollstndig eingerastet ist. Sichern Sie die Halteklammern am Gehuse.
  4. Bringen Sie die Computerabdeckung wieder an. Stecken Sie die Netzverbindung ein.

HINWEIS: Einige der Intel Gigabit Server und Desktop-Adapter verwenden den PCI-Express-Bus. Sie knnen ohne negative Folgen einen Steckplatz benutzen, der lnger ist als der Anschluss Ihres Adapters; versuchen Sie jedoch nicht, den Adapter in einem Steckplatz zu installieren, der krzer ist als der PCI-Express-Anschluss.

Schlieen Sie das Netzwerkkabel an

Intel® PRO/100 und Gigabit Kupferadapter: Verbinden Sie das oder die Netzwerkkabel mit dem Adapter. Verwenden Sie verdrillte Ethernet- (TPE) Netzwerkkabel der Kategorie 3, 4 oder 5 fr Netzwerke mit 10 Mbit/s. Verwenden Sie ein Kategorie-5-Kabel (4 Leitungspaare) fr 100/1000-Mbit/s-Netzwerke sowie fr Netzwerke in Privathaushalten.

Intel® Gigabit Glasfaseradapter mit SC-Steckverbinder: Entfernen Sie die Abdeckung des Glasfaseranschlusses und bewahren Sie sie gut auf. Stecken Sie den Duplex-SC-Steckverbinder eines 1000 Base-SX-Glasfaserkabels in die TX/RX-Anschlsse der Adapterklammer.

Intel® Gigabit Glasfaseradapter mit LC-Steckverbinder: Entfernen Sie die Abdeckung des Glasfaseranschlusses und bewahren Sie sie gut auf. Befestigen Sie am Adapter eine LC-Steckverbindung mit den korrekten Kabeln fr Ihren Adaptertyp (1000BASE-SX oder 1000BASE-LX). Sie knnen Kabel anderer Verbindungstypen (wie SC) verwenden, wenn die Kabel den optischen Spezifikationen des Adapters, einschlielich der Lngenbegrenzung, entsprechen.

Starten Sie den Computer und folgen Sie nachfolgenden Anweisungen zur Treiberinstallation.

Treiber installieren

Windows-Betriebssysteme

Beachten Sie, dass Sie Administratorrechte fr das Betriebssystem besitzen mssen, um Treiber installieren zu drfen.

  1. Der Adapter wird erkannt, und Windows installiert entweder einen in Windows residenten Treiber oder startet den Assistent fr das Suchen neuer Hardware .
  2. Klicken Sie bei Start des Assistenten fr das Suchen neuer Hardware auf die Schaltflche "Abbrechen".
  3. Legen Sie die Intel CD ein. Das Programm Intel Netzwerkanschlsse startet automatisch. Klicken Sie auf die Schaltflche Treiber und Software installieren .

Linux*

Um ein binres RPM*-Paket dieses Treibers zu erstellen, fhren Sie 'rpmbuild -tb <dateiname.tar.gz>' aus. Ersetzen Sie <dateiname.tar.gz> mit dem Dateinamen des Treibers.

HINWEISE:

  • Damit das erstellte Paket ordnungsgem funktioniert, MUSS der gegenwrtig ausgefhrte Kernel mit der Version und der Konfiguration der installierten Kernelquellen bereinstimmen. Wenn Sie den Kernel gerade neu kompiliert haben, fhren Sie jetzt einen Systemneustart aus.

  • Die RPM-Funktionalitt wurde bisher nur in Red Hat-Verteilungen getestet.

  • Verwenden Sie bei Intel PRO/100 Adaptern e100 als Treibernamen.

  1. Verschieben Sie die Basistreiber-Tardatei in ein Verzeichnis Ihrer Wahl. Verwenden Sie beispielsweise '/home/username/e1000' oder '/usr/local/src/e1000'.

  2. Dekomprimieren Sie das Archiv, wobei <x.x.x> die Versionsnummer fr die Treibertardatei ist:
    tar zxf e1000-<x.x.x>.tar.gz
  3. Wechseln Sie durch folgende Eingabe zum src-Verzeichnis des Treibers ber, wobei <x.x.x> die Versionsnummer des Treibertars ist:
    cd e1000-<x.x.x>/src/
  4. Kompilieren Sie das Treibermodul:
    make install
    Die Binrdatei wird installiert als:
    /lib/modules/<kernel_version>/kernel/drivers/net/e1000.o

    Die oben aufgefhrten Installationsverzeichnisse sind die Standardverzeichnisse. Sie sind mglicherweise fr bestimmte Linux-Distributionen nicht richtig.

  5. Installieren Sie das Modul:
    insmod e1000 <parameter>=<value>
  6. Weisen Sie der Schnittstelle durch folgende Eingabe eine IP-Adresse zu, wobei <x> fr die Schnittstellennummer steht:
    ifconfig eth<x> <IP_address>
  7. Prfen Sie, ob die Schnittstelle funktioniert. Geben Sie Folgendes ein, wobei <IP-Adresse> die IP-Adresse eines anderen Gertes auf demselben Subnet wie die Schnittstelle, die getestet wird, ist:
    ping <IP-Adresse>

Andere Betriebssysteme

Informationen zur Installation anderer Treiber finden Sie im Benutzerhandbuch auf der Adapter-CD oder auf Ihrer Kundensupport-Website: http://www.intel.com/p/de_DE/support/.

*Rechtliche Hinweise

Zuletzt berarbeitet am 11.10.07 15:48 Revision 14

DOCS/QUICK/DEU/style.css0000755000000000000000000000450511651733270011653 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/DEU/warranty.htm0000755000000000000000000001466011546611560012365 0ustar Beschrnkte lebenslange Hardwaregarantie

Beschrnkte lebenslange Hardwaregarantie

Intel garantiert dem ursprnglichen Eigentmer, dass das in diesem Paket gelieferte Adapterprodukt frei von Material- und Herstellungsfehlern ist. Das Adapterprodukt fllt nicht unter diese Garantie, wenn es whrend der Installation beschdigt oder unsachgem verwendet wurde.

DIE OBIGE GARANTIE ERSETZT ALLE ANDEREN AUSDRCKLICHEN, STILLSCHWEIGENDEN ODER GESETZLICHEN GARANTIEN, EINSCHLIESSLICH, ABER NICHT BESCHRNKT AUF IRGENDWELCHE GARANTIEN DER EINHALTUNG DER RECHTE DRITTER AN GEISTIGEM EIGENTUM, DER MARKTGNGIGEN QUALITT, DER EIGNUNG FR EINEN BESTIMMTEN ZWECK, DIE SICH AUS EINEM VORSCHLAG, EINER SPEZIFIKATION ODER EINEM BEISPIEL BZW. EINER PROBE ERGEBEN.

Diese Garantie gilt nicht fr den Austausch von Adapterprodukten, die durch Mutwilligkeit, Unfall, Zweckentfremdung, Nachlssigkeit, Reparaturen, Katastrophen, unsachgeme Installation oder unsachgemes Testen beschdigt wurden. Wird das Adapterprodukt als defekt eingestuft, wird Intel nach eigenem Ermessen das Hardwareprodukt wie unten erlutert kostenfrei ersetzen oder reparieren oder Ihnen den Kaufpreis zurckerstatten, vorausgesetzt, dass Sie das Adapterprodukt zusammen mit einer Return-Material-Authorization-(RMA-)Nummer (siehe unten) und einem Kaufnachweis (falls nicht registriert) an den Hndler, wo Sie es erworben haben, oder an Intel mit einer Beschreibung jeglichen Defekts zurckgeben. Wenn Sie das Adapterprodukt einschicken, bernehmen Sie das Risiko fr Schden am Produkt oder Verlust des Produkts whrend des Transports. Sie mssen die Originalverpackung (oder eine gleichwertige Verpackung) verwenden und das Porto bezahlen.

Intel kann das Adapterprodukt durch neue oder aufbereitete Teile ersetzen oder reparieren. Jedes von Intel ersetzte Adapterprodukt oder Teile davon gehen in das Eigentum von Intel ber. Reparierte oder ersetzte Adapterprodukte werden nach dem Ermessen von Intel mit derselben Revisionsstufe wie empfangen oder hher an Sie zurckgegeben. Intel behlt sich das Recht vor, eingestellte Adapterprodukte durch ein gleichwertiges Adapterprodukt der aktuellen Generation zu ersetzen.

Rckgabe eines defekten Produkts

Aus Nordamerika:

Wenden Sie sich vor der Rckgabe eines Adapterprodukts unter +1 916-377-7000 an den Kundensupport von Intel, um eine Return-Material-Authorization-(RMA-)Nummer anzufordern.

Wenn die Kundensupportgruppe den Defekt des Adapterprodukts besttigt, wird die RMA-Abteilung Ihnen eine RMA-Nummer ausstellen, die Sie an der Auenverpackung des Adapterprodukts anbringen. Intel akzeptiert nur Produkte mit einer RMA-Nummer auf der Verpackung.

Alle anderen Orte:

Geben Sie das Adapterprodukt fr eine Rckerstattung des Kaufpreises oder Ersatz an den Verkaufsort zurck.

Geldrckgabegarantie fr Intel Adapter (nur Nordamerika)

Intel mchte, dass Sie mit dem gekauften Intel Adapterprodukt rundum zufrieden sind. Sie knnen in einem Zeitraum von neunzig (90) Tagen ab Kaufdatum Ihren Intel Adapter fr eine volle Rckerstattung des Kaufpreises durch den Hndler an den ursprnglichen Verkaufsort zurckgeben. Fachhndler und Distributoren, die Retouren akzeptieren und ihren Kunden Geld zurckerstatten, knnen Intel Adapter an den ursprnglichen Verkaufsort zurckgeben. Intel garantiert die Annahme von Retouren unter dieser Richtlinie und die Rckerstattung des ursprnglichen Kaufpreises an Kunden, die direkt von Intel kaufen.

Haftungsbeschrnkungen und Rechtsmittel

DIE EINZIGE HAFTUNG VON INTEL UNTER DIESER VEREINBARUNG IST BESCHRNKT AUF DIREKTE, OBJEKTIV MESSBARE SCHDEN. UNTER KEINEN UMSTNDEN HAFTET INTEL FR JEGLICHE INDIREKTEN ODER SPEKULATIVEN SCHDEN (EINSCHLIESSLICH, ABER OHNE EINSCHRNKUNG DES VORHERGEHENDEN, FOLGESCHDEN, NEBENSCHDEN ODER SONDERSCHDEN), EINSCHLIESSLICH, ABER NICHT BESCHRNKT AUF DIE EINHALTUNG DER RECHTE DRITTER AN GEISTIGEM EIGENTUM, KOSTEN DER NEUBESCHAFFUNG, UNBRAUCHBARKEIT, GESCHFTSAUSFLLEN, VERLUST DES GESCHFTSWERTS UND GEWINNVERLUSTEN, EGAL OB SICH SOLCHE SCHDEN AUS VERTRAGLICHER FAHRLSSIGKEIT, UNERLAUBTEM HANDELN ODER UNTER JEGLICHER GARANTIE ERGEBEN, UNGEACHTET DESSEN, OB INTEL VON DER MGLICHKEIT SOLCHER SCHDEN IM VORAUS KENNTNIS HATTE. UNGEACHTET DES VORHERGEHENDEN BERSTEIGT DIE GESAMTHAFTUNG VON INTEL FR ALLE ANSPRCHE UNTER DIESER VEREINBARUNG NICHT DEN FR DAS PRODUKT BEZAHLTEN PREIS. DIESE BESCHRNKUNGEN POTENZIELLER HAFTUNGSANSPRCHE TRUGEN WESENTLICH ZUR BESTIMMUNG DES PRODUKTPREISES BEI. INTEL BERNIMMT KEINE WEITEREN HAFTUNGEN UND AUTORISIERT NIEMANDEN, AN SEINER STELLE JEGLICHE WEITEREN HAFTUNGEN ZU BERNEHMEN.

In einigen Gerichtsbarkeiten ist der Ausschluss oder die Beschrnkung von Neben- oder Folgeschden nicht zulssig, sodass die oben ausgefhrten Beschrnkungen mglicherweise auf Sie nicht zutreffen.

Kritische Steuerungsanwendungen: Intel lehnt insbesondere die Haftung fr die Verwendung des Adapterprodukts in kritischen Steuerungsanwendungen (einschlielich, nur als Beispiel, Sicherheits- oder medizinische Steuerungssysteme, Kernenergie-Steuerungssysteme oder Luft- und Bodenverkehrs-Steuerungssysteme) durch den Lizenznehmer oder Unterlizenznehmer ab. Eine solche Verwendung geschieht einzig auf Risiko des Benutzers. Der Lizenznehmer willigt ein, Intel vor allen Ansprchen, die sich aus der Verwendung des Adapterprodukts in solchen Anwendungen durch den Lizenznehmer oder Unterlizenznehmer ergeben, zu schtzen, freizuhalten und schadlos zu halten.

Software: Die mit dem Adapterprodukt gelieferte Software fllt nicht unter die oben ausgefhrte Hardwaregarantie. Einzelheiten zu eventuellen Softwaregarantien finden Sie in der zutreffenden Softwarelizenzvereinbarung im Lieferumfang des Adapterprodukts.

Zuletzt berarbeitet 23.7.02 10.42 Revision 6

DOCS/QUICK/ENU0000755000000000000000000000000011761422164007724 5ustar DOCS/QUICK/ENU/legaldis.htm0000755000000000000000000000205611701323454012303 0ustar Legal Information

Copyright and Legal Disclaimers

Copyright © 2002 - 2012 Intel Corporation. All rights reserved.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein.

Intel, Itanium, and Pentium are trademarks of Intel Corporation in the U.S. and other countries.

*Other names and brands may be claimed as the property of others.

Warranty Information

Software License

 

Last modified on 1/25/11 10:21p Revision DOCS/QUICK/ENU/license.htm0000755000000000000000000003527311654245266012163 0ustar Software License

INTEL SOFTWARE LICENSE AGREEMENT

IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.

Do not copy, install, or use this software and any associated materials (collectively, the “Software”) provided under this license agreement (“Agreement”) until you have carefully read the following terms and conditions.

By copying, installing, or otherwise using the Software, you agree to be bound by the terms of this Agreement. If you do not agree to the terms of this Agreement, do not copy, install, or use the Software.

LICENSES:

Please Note:

  • If you are a network or system administrator, the “Site License” below shall apply to you.
  • If you are an end user, the “Single User License” shall apply to you.
  • If you are an original equipment manufacturer (OEM), the “OEM License” shall apply to you.

SITE LICENSE: You may copy the Software onto your organization’s computers for your organization’s use, and you may make a reasonable number of back-up copies of the Software, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual ("emulated") devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

SINGLE USER LICENSE: You may copy the Software onto a single computer for your personal use, and you may make one back-up copy of the Software, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual (“emulated”) devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

OEM LICENSE: You may reproduce and distribute the Software only as an integral part of or incorporated in your product, as a standalone Software maintenance update for existing end users of your products, excluding any other standalone products, or as a component of a larger Software distribution, including but not limited to the distribution of an installation image or a Guest Virtual Machine image, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual (“emulated”) devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. You may only distribute the Software to your customers pursuant to a written license agreement. Such license agreement may be a "break-the-seal" license agreement. At a minimum such license shall safeguard Intel's ownership rights to the Software.
  6. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

LICENSE RESTRICTIONS. You may NOT: (i) use or copy the Materials except as provided in this Agreement; (ii) rent or lease the Materials to any third party; (iii) assign this Agreement or transfer the Materials without the express written consent of Intel; (iv) modify, adapt, or translate the Materials in whole or in part except as provided in this Agreement; (v) reverse engineer, decompile, or disassemble the Materials; (vi) attempt to modify or tamper with the normal function of a license manager that regulates usage of the Materials; (vii) distribute, sublicense or transfer the Source Code form of any components of the Materials, Redistributables and Sample Source and derivatives thereof to any third party except as provided in this Agreement.

NO OTHER RIGHTS. No rights or licenses are granted by Intel to you, expressly or by implication, with respect to any proprietary information or patent, copyright, mask work, trademark, trade secret, or other intellectual property right owned or controlled by Intel, except as expressly provided in this Agreement. Except as expressly provided herein, no license or right is granted to you directly or by implication, inducement, estoppel, or otherwise. Specifically, Intel grants no express or implied right to you under Intel patents, copyrights, trademarks, or other intellectual property rights.

OWNERSHIP OF SOFTWARE AND COPYRIGHTS. The Software is licensed, not sold. Title to all copies of the Software remains with Intel. The Software is copyrighted and protected by the laws of the United States and other countries and international treaty provisions. You may not remove any copyright notices from the Software. You agree to prevent any unauthorized copying of the Software. Intel may make changes to the Software, or to items referenced therein, at any time without notice, but is not obligated to support or update the Software. You may transfer the Software only if the recipient agrees to be fully bound by these terms and if you retain no copies of the Software.

ADDITIONAL TERMS FOR PRE-RELEASE SOFTWARE. If the Software you are installing or using under this Agreement is pre-commercial release or is labeled or otherwise represented as “alpha-“ or “beta-“ versions of the Software ("pre-release Software"), then the following terms apply.

To the extent that any provision in this Section conflicts with any other term(s) or condition(s) in this Agreement with respect to pre-release Software, this Section shall supersede the other term(s) or condition(s), but only to the extent necessary to resolve the conflict.
You understand and acknowledge that the Software is pre-release Software, does not represent the final Software from Intel, and may contain errors and other problems that could cause data loss, system failures, or other errors. The pre-release Software is provided to you "as-is" and Intel disclaims any warranty or liability to you for any damages that arise out of the use of the pre-release Software.
You acknowledge that Intel has not promised that pre-release Software will be released in the future, that Intel has no express or implied obligation to you to release the pre-release Software and that Intel may not introduce Software that is compatible with the pre-release Software. You acknowledge that the entirety of any research or development you perform that is related to the pre-release Software or to any product making use of or associated with the pre-release Software is done at your own risk.
If Intel has provided you with pre-release Software pursuant to a separate written agreement, your use of the pre-release Software is also governed by such agreement.

LIMITED MEDIA WARRANTY. If the Software has been delivered by Intel on physical media, Intel warrants the media to be free from material physical defects for a period of ninety days after delivery by Intel. If such a defect is found, return the media to Intel for replacement or alternate delivery of the Software as Intel may select.

EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE, THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for the accuracy or completeness of any information, text, graphics, links, or other items contained within the Software.

LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION. In the event that you use the Software in conjunction with a virtual (“emulated”) device designed to appear as an Intel component product, you acknowledge that Intel is neither the author nor the creator of the virtual (“emulated”) device. You understand and acknowledge that Intel makes no representations about the correct operation of the Software when used with a virtual (“emulated”) device, that Intel did not design the Software to operate in conjunction with the virtual (“emulated”) device, and that the Software may not be capable of correct operation in conjunction with the virtual (“emulated”) device. You agree to assume the risk that the Software may not operate properly in conjunction with the virtual (“emulated”) device. You agree to indemnify and hold Intel and its officers, subsidiaries and affiliates harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of product liability, personal injury or death associated with the use of the Software in conjunction with the virtual (“emulated”) device, even if such claim alleges that Intel was negligent regarding the design or manufacture of the Software.

UNAUTHORIZED USE. THE SOFTWARE IS NOT DESIGNED, INTENDED, OR AUTHORIZED FOR USE IN ANY TYPE OF SYSTEM OR APPLICATION IN WHICH THE FAILURE OF THE SOFTWARE COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR (E.G MEDICAL SYSTEMS, LIFE SUSTAINING OR LIFE SAVING SYSTEMS). If you use the Software for any such unintended or unauthorized use, you shall indemnify and hold Intel and its officers, subsidiaries and affiliates harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of product liability, personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Intel was negligent regarding the design or manufacture of the part.

TERMINATION OF THIS AGREEMENT. Intel may terminate this Agreement at any time if you violate its terms. Upon termination, you will immediately destroy the Software or return all copies of the Software to Intel.

APPLICABLE LAWS. Claims arising under this Agreement shall be governed by the laws of the State of California, without regard to principles of conflict of laws. You agree that the terms of the United Nations Convention on Contracts for the Sale of Goods do not apply to this Agreement. You may not export the Software in violation of applicable export laws and regulations. Intel is not obligated under any other agreements unless they are in writing and signed by an authorized representative of Intel.

GOVERNMENT RESTRICTED RIGHTS. The enclosed Software and documentation were developed at private expense, and are provided with “RESTRICTED RIGHTS.” Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR 52.227-14 and DFARS 252.227-7013 et seq. or its successor. The use of this product by the Government constitutes acknowledgement of Intel’s proprietary rights in the Software. Contractor or Manufacturer is Intel.

LANGUAGE; TRANSLATIONS. In the event that the English language version of this Agreement is accompanied by any other version translated into any other language, such translated version is provided for convenience purposes only and the English language version shall control.

Last modified on 5/15/11 10:56p Revision

DOCS/QUICK/ENU/note.gif0000755000000000000000000000073211651733270011445 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/ENU/qi_enu.htm0000755000000000000000000001324711644566662012023 0ustar Intel(R) Network Adapters Quick Installation Guide

Intel® Network Adapter Installation

Install the Intel PCI, PCI-X, or PCI Express* Adapter

  1. Turn off the computer and unplug the power cord.
  2. Remove the computer cover and the adapter slot cover from the slot that matches your adapter.
  3. Firmly place the adapter edge connector into the slot until it is fully inserted. Secure the bracket to the chassis.
  4. Replace the computer cover. Plug in the power cord.

NOTE: Some Intel Gigabit server and desktop adapters utilize the PCI Express bus. You may utilize a slot that is longer than your adapter’s connector with no harm, but do not attempt to install in a slot that is shorter than the PCI Express connector.

Attach the Network Cable

Intel® PRO/100 and Gigabit copper adapters: Connect the network cable or cables to the adapter using Category 3, 4, or 5 Twisted Pair Ethernet (TPE) network cable for 10 Mbps networks. Use Category 5 (4 pair) cable for 100 or 1000 Mbps networks and for any residential networks.

Intel® Gigabit fiber adapters with SC connector: Remove and save the fiber optic connector cover. Insert a 1000Base-SX duplex type SC fiber optic connector into the TX/RX ports on the adapter bracket.

Intel® Gigabit fiber adapters with LC connector: Remove and save the fiber optic connector cover. Insert an LC connector into the adapter, with correct cabling for your adapter type (1000BASE-SX or 1000BASE-LX). Conversion cables to other connector types (such as SC) may be used if the cabling matches the optical specifications of the adapter, including length limitations.

Start your computer and follow the driver installation instructions below.

Install the Drivers

Windows Operating Systems

Note that you must have administrative rights to the operating system to install the drivers.

  1. The adapter is detected and Windows either installs a Windows resident driver or starts the Found New Hardware wizard.
  2. If the Found New Hardware wizard starts, press the Cancel button.
  3. Insert the Intel CD. The Intel Network Connections autorun program automatically starts. Click the Install Drivers and Software button.

Linux*

To build a binary RPM* package of this driver, run 'rpmbuild -tb <filename.tar.gz>'. Replace <filename.tar.gz> with the specific file name of the driver.

NOTES:

  • For the build to work properly, the currently running kernel MUST match the version and configuration of the installed kernel sources. If you have just recompiled the kernel reboot the system now.

  • RPM functionality has been tested only in Red Hat distributions.

  • For Intel PRO/100 adapters, use e100 as driver name.

  1. Move the base driver tar file to the directory of your choice. For example, use '/home/username/e1000' or '/usr/local/src/e1000'.

  2. Untar/unzip the archive, where <x.x.x> is the version number for the driver tar file:
    tar zxf e1000-<x.x.x>.tar.gz
  3. Change to the driver src directory, where <x.x.x> is the version number for the driver tar:
    cd e1000-<x.x.x>/src/
  4. Compile the driver module:
    make install
    The binary will be installed as:
    /lib/modules/<kernel_version>/kernel/drivers/net/e1000.o

    The install locations listed above are the default locations. They might not be correct for certain Linux distributions.

  5. Install the module:
    insmod e1000 <parameter>=<value>
  6. Assign an IP address to the interface by entering the following, where <x> is the interface number:
    ifconfig eth<x> <IP_address>
  7. Verify that the interface works. Enter the following, where <IP_address> is the IP address for another machine on the same subnet as the interface that is being tested:
    ping <IP_address>

Other Operating Systems

To install other drivers, see the User's Guide on the adapter CD or visit your customer support web site: http://support.intel.com.

*Legal Information

Last modified on 10/11/07 3:48p Revision

DOCS/QUICK/ENU/style.css0000755000000000000000000000450511651733270011665 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/ENU/warranty.htm0000755000000000000000000001324011651733270012370 0ustar Limited Lifetime Hardware Warranty

Limited Lifetime Hardware Warranty

Intel warrants to the original owner that the adapter product delivered in this package will be free from defects in material and workmanship. This warranty does not cover the adapter product if it is damaged in the process of being installed or improperly used.

THE ABOVE WARRANTY IS IN LIEU OF ANY OTHER WARRANTY, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF NONINFRINGEMENT OF INTELLECTUAL PROPERTY, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE.

This warranty does not cover replacement of adapter products damaged by abuse, accident, misuse, neglect, alteration, repair, disaster, improper installation, or improper testing. If the adapter product is found to be defective, Intel, at its option, will replace or repair the hardware product at no charge except as set forth below, or refund your purchase price provided that you deliver the adapter product along with a Return Material Authorization (RMA) number (see below), along with proof of purchase (if not registered), either to the dealer from whom you purchased it or to Intel with an explanation of any deficiency. If you ship the adapter product, you must assume the risk of damage or loss in transit. You must use the original container (or the equivalent) and pay the shipping charge.

Intel may replace or repair the adapter product with either new or reconditioned parts, and any adapter product, or part thereof replaced by Intel becomes Intel's property. Repaired or replaced adapter products will be returned to you at the same revision level as received or higher, at Intel's option. Intel reserves the right to replace discontinued adapter products with an equivalent current generation adapter product.

Returning a defective product

From North America:

Before returning any adapter product, contact Intel Customer Support and obtain a Return Material Authorization (RMA) number by calling +1 916-377-7000.

If the Customer Support Group verifies that the adapter product is defective, they will have the RMA department issue you an RMA number to place on the outer package of the adapter product. Intel cannot accept any product without an RMA number on the package.

All other locations:

Return the adapter product to the place of purchase for a refund or replacement.

Intel Adapter Money-back Guarantee (North America Only)

Intel wants you to be completely satisfied with the Intel adapter product that you have purchased. Any time within ninety (90) days of purchase, you may return your Intel adapter to the original place of purchase for a full refund of the purchase price from your dealer. Resellers and distributors, respectively, accepting returns and refunding money back to their customers may return Intel adapters to their original place of purchase. Intel guarantees that it will accept returns under this policy and refund the original purchase price to customers purchasing directly from Intel.

Limitation of Liability and Remedies

INTEL'S SOLE LIABILITY HEREUNDER SHALL BE LIMITED TO DIRECT, OBJECTIVELY MEASURABLE DAMAGES. IN NO EVENT SHALL INTEL HAVE ANY LIABILITY FOR ANY INDIRECT OR SPECULATIVE DAMAGES (INCLUDING, WITHOUT LIMITING THE FOREGOING, CONSEQUENTIAL, INCIDENTAL, AND SPECIAL DAMAGES) INCLUDING, BUT NOT LIMITED TO, INFRINGEMENT OF INTELLECTUAL PROPERTY, REPROCUREMENT COSTS, LOSS OF USE, BUSINESS INTERRUPTIONS, LOSS OF GOODWILL, AND LOSS OF PROFITS, WHETHER ANY SUCH DAMAGES ARISE OUT OF CONTRACT NEGLIGENCE, TORT, OR UNDER ANY WARRANTY, IRRESPECTIVE OF WHETHER INTEL HAS ADVANCE NOTICE OF THE POSSIBILITY OF ANY SUCH DAMAGES. NOTWITHSTANDING THE FOREGOING, INTEL'S TOTAL LIABILITY FOR ALL CLAIMS UNDER THIS AGREEMENT SHALL NOT EXCEED THE PRICE PAID FOR THE PRODUCT. THESE LIMITATIONS ON POTENTIAL LIABILITIES WERE AN ESSENTIAL ELEMENT IN SETTING THE PRODUCT PRICE. INTEL NEITHER ASSUMES NOR AUTHORIZES ANYONE TO ASSUME FOR IT ANY OTHER LIABILITIES.

Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations may not apply to you.

Critical Control Applications: Intel specifically disclaims liability for use of the adapter product in critical control applications (including, for example only, safety or health care control systems, nuclear energy control systems, or air or ground traffic control systems) by Licensee or Sublicensees, and such use is entirely at the user's risk. Licensee agrees to defend, indemnify, and hold Intel harmless from and against any and all claims arising out of use of the adapter product in such applications by Licensee or Sublicensees.

Software: Software provided with the adapter product is not covered under the hardware warranty described above. See the applicable software license agreement which shipped with the adapter product for details on any software warranty.

Last modified on 7/23/02 10:42a Revision

DOCS/QUICK/ESN0000755000000000000000000000000011761422164007722 5ustar DOCS/QUICK/ESN/legaldis.htm0000755000000000000000000000222311730046352012276 0ustar Informacin legal

Copyright y renuncia de responsabilidades

Copyright © 2002 - 2012 Intel Corporation. Reservados todos los derechos.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 EE.UU.

Intel Corporation no asume ninguna responsabilidad por los errores y omisiones en esta gua. Del mismo modo, Intel no se compromete de ninguna forma a actualizar la informacin aqu contenida.

Intel, Itanium y Pentium son marcas comerciales de Intel Corporation en los EE.UU. y en otros pases.

* Otros nombres y marcas pueden ser reclamados como propiedad de terceras partes.

Informacin de garanta

Licencia del software

 

ltima modificacin a fecha de 25-1-11 22:21 Revisin 26 DOCS/QUICK/ESN/license.htm0000755000000000000000000004016711730046352012145 0ustar Licencia del software

CONTRATO DE LICENCIA DE SOFTWARE DE INTEL

IMPORTANTE: LASE ANTES DE COPIAR, INSTALAR O UTILIZAR.

No copie, instale ni utilice este software y cualquier material asociado (colectivamente, el “Software”) proporcionado con este contrato de licencia (“Contrato”) hasta que haya ledo atentamente los siguientes trminos y condiciones.

Al copiar, instalar o utilizar el Software de otro modo, acepta que estar sujeto por los trminos de este Contrato. Si no est de acuerdo con los trminos de este Contrato, no copie, instale ni utilice el Software.

LICENCIAS:

Tenga en cuenta que:

  • Si es usted un administrador de redes o de sistema, le corresponde la seccin “Licencia de sitio”.
  • Si es un usuario final, le corresponde la seccin "Licencia de usuario individual".
  • Si es usted un fabricante de equipo original (OEM), le corresponde la seccin "Licencia de OEM".

LICENCIA DE SITIO: Puede copiar el Software en los sistemas de su organizacin para el uso de sta, y podr efectuar un nmero prudente de copias de seguridad del Software, sujeto a las siguientes condiciones:

  1. La licencia de este Software sirve para su uso solo junto con (a) productos de componentes de Intel fsicos, y (b) dispositivos virtuales ("emulados") diseados para aparecer como productos de componentes de Intel en un sistema operativo invitado que funcione en el contexto de una mquina virtual. Cualquier otro uso del Software, incluido su uso con productos de componentes no de Intel, aunque sin limitarse a l, no est cubierto por esta licencia.
  2. Intel Corporation ("Intel") le concede, con sujecin a todos los trminos y condiciones de este Contrato, una licencia de copyright no exclusiva y no asignable de uso de los Materiales
  3. No puede copiar, modificar, alquilar, vender, distribuir ni transferir parte alguna del Software, excepto segn se especifique en este Contrato, y se aviene a impedir la copia no autorizada del Software.
  4. No puede aplicar tcnicas de ingeniera inversa, descompilar ni desensamblar el Software.
  5. El software podr incluir porciones que se ofrecen en trminos agregados a los estipulados en el presente contrato, segn se expresan en la licencia que acompaa a esas porciones.

LICENCIA DE USUARIO NICO: Puede copiar el Software en un nico sistema para su uso personal, no comercial, y realizar una copia de seguridad del Software con estas condiciones:

  1. La licencia de este Software sirve para su uso solo junto con (a) productos de componentes de Intel fsicos, y (b) dispositivos virtuales (“emulados”) diseados para aparecer como productos de componentes de Intel en un sistema operativo invitado que funcione en el contexto de una mquina virtual. Cualquier otro uso del Software, incluido su uso con productos de componentes no de Intel, aunque sin limitarse a l, no est cubierto por esta licencia.
  2. Intel Corporation ("Intel") le concede, con sujecin a todos los trminos y condiciones de este Contrato, una licencia de copyright no exclusiva y no asignable de uso de los Materiales
  3. No puede copiar, modificar, alquilar, vender, distribuir ni transferir parte alguna del Software, excepto segn se especifique en este Contrato, y se aviene a impedir la copia no autorizada del Software.
  4. No puede aplicar tcnicas de ingeniera inversa, descompilar ni desensamblar el Software.
  5. El software podr incluir porciones que se ofrecen en trminos agregados a los estipulados en el presente contrato, segn se expresan en la licencia que acompaa a esas porciones.

LICENCIA DE OEM: Solo puede reproducir y distribuir el Software como parte integral de, o incorporado en su producto, como actualizacin independiente de mantenimiento del Software para usuarios finales existentes de sus productos, excluidos otros productos independientes, o como componente de una distribucin de Software mayor, incluyendo, aunque sin limitarse a ella, la distribucin de una imagen de instalacin o una imagen de mquina virtual invitada, con estas condiciones:

  1. La licencia de este Software sirve para su uso solo junto con (a) productos de componentes de Intel fsicos, y (b) dispositivos virtuales (“emulados”) diseados para aparecer como productos de componentes de Intel en un sistema operativo invitado que funcione en el contexto de una mquina virtual. Cualquier otro uso del Software, incluido su uso con productos de componentes no de Intel, aunque sin limitarse a l, no est cubierto por esta licencia.
  2. Intel Corporation ("Intel") le concede, con sujecin a todos los trminos y condiciones de este Contrato, una licencia de copyright no exclusiva y no asignable de uso de los Materiales
  3. No puede copiar, modificar, alquilar, vender, distribuir ni transferir parte alguna del Software, excepto segn se especifique en este Contrato, y se aviene a impedir la copia no autorizada del Software.
  4. No puede aplicar tcnicas de ingeniera inversa, descompilar ni desensamblar el Software.
  5. Solamente podr distribuir el Software a sus clientes, conforme a un contrato de licencia por escrito. Ese contrato de licencia puede tener el carcter de contrato de licencia por "ruptura del sello". Al menos, esa licencia va a salvaguardar los derechos de propiedad sobre el Software de Intel.
  6. El software podr incluir porciones que se ofrecen en trminos agregados a los estipulados en el presente contrato, segn se expresan en la licencia que acompaa a esas porciones.

RESTRICCIONES DE LA LICENCIA. Usted NO podr: (i) utilizar o copiar los Materiales excepto como se indica en este Contrato; (ii) alquilar o proporcionar en "leasing" los Materiales a terceros; (iii) asignar este Contrato o transferir los Materiales sin el consentimiento expreso por escrito de Intel; (iv) modificar, adaptar o traducir los Materiales en su totalidad o en parte, excepto segn lo previsto en este Contrato; (v) aplicar ingeniera inversa, descompilar o desensamblar los Materiales; (vi) intentar modificar o alterar el funcionamiento normal de un gestor de licencias que regule el uso de los Materiales; (vii) distribuir, sublicenciar o transferir el formato de Cdigo fuente de cualquier componente de los Materiales, Redistribuibles y Cdigo fuente de ejemplo y sus derivados a terceros excepto segn lo previsto en este Contrato.

NO EXISTEN OTROS DERECHOS. Intel no le concede otros derechos o licencias, de manera expresa o implcita, con respecto a cualquier informacin de titularidad o patente, copyright, topografa de circuito integrado, marca comercial, secretos comerciales, u otros derechos de titularidad de propiedad intelectual o controlados por Intel, a excepcin de lo que se establece expresamente en este Contrato. Salvo lo previsto expresamente en este documento, no se le concede ninguna licencia o derecho, de manera directa o implcita, incentivo, impedimento legal o de otra manera. Especficamente, Intel no le concede ningn derecho expreso o implcito bajo patentes, copyrights, marcas comerciales u otros derechos de propiedad intelectual de Intel.

PROPIEDAD DEL MATERIAL Y LOS "COPYRIGHTS". El Software se otorga con licencia, no se vende. Intel mantiene el ttulo de propiedad de todas las copias del Software. El Software dispone de sus correspondientes derechos de autor, y est amparado por la legislacin estadounidense y de otros pases, as como por disposiciones de tratados internacionales. No est permitido eliminar del Software ninguna nota sobre los derechos de autor. Acepta evitar cualquier copia no autorizada del Software. Intel puede introducir modificaciones en el Software, o en elementos a los que se hace referencia en el mismo, en cualquier momento y sin previo aviso, sin tener obligacin de prestar asistencia tcnica o actualizar el Software. Slo podr transferir el Software si el receptor acepta por completo estos trminos y usted no retiene copia alguna del mismo.

TRMINOS ADICIONALES PARA SOFTWARE PREVIO A LA VERSIN. Si el Software que est instalando o utilizando bajo este Contrato es una versin previa a la comercializacin, o est etiquetada o representada de otra manera como versiones “alfa“ o “beta“ del Software ("Software previo a la versin"), se aplican los trminos siguientes.

Hasta el extremo que cualquier disposicin de esta Seccin est en conflicto con otro(s) trmino(s) o condicin(es) de este Contrato respecto al Software previo a la versin, esta Seccin prevalecer sobre otro(s) trmino(s) o condicin(es), pero slo hasta el extremo necesario para resolver el conflicto.
Entiende y reconoce que el Software es Software previo a la versin, no representa el Software final de Intel, y puede contener errores y otros problemas que podran causar la prdida de datos, fallos del sistema u otros errores. El Software previo a la versin se proporciona "como est" e Intel rechaza toda garanta o responsabilidad hacia usted por cualquier dao causado por el uso del Software previo a la versin.
Reconoce que Intel no ha prometido que el Software previo a la versin se comercializar en el futuro, que Intel no tiene ninguna obligacin expresa o implcita hacia usted de comercializar el Software previo a la versin y que Intel puede presentar Software que no sea compatible con el Software previo a la versin. Reconoce que la totalidad de cualquier investigacin o desarrollo relacionado con el Software previo a la versin o con cualquier producto que utilice o est asociado con el Software previo a la versin se realizar por su cuenta y riesgo.
Si Intel le ha proporcionado Software previo a la versin segn los trminos de un contrato escrito por separado, su uso del Software previo a la versin tambin est regido por dicho contrato.

GARANTA LIMITADA DEL MEDIO. Si Intel ha entregado el software en soporte fsico, garantiza que dicho soporte est libre de defectos fsicos de material durante un perodo de noventa das tras la entrega. Si encuentra algn defecto semejante, devuelva el soporte a Intel para reemplazarlo o para que Intel le entregue el Software de otro modo, a discrecin de Intel.

EXCLUSIN DE OTRAS GARANTAS. EXCEPTO LO YA DISPUESTO, SE PROPORCIONA EL SOFTWARE EN EL ESTADO QUE SE ENCUENTRA Y SIN GARANTAS EXPRESAS O IMPLCITAS DE NINGN TIPO, ENTRE OTRAS, GARANTAS DE COMERCIABILIDAD, AUSENCIA DE VIOLACIONES O IDONEIDAD PARA UN FIN DETERMINADO. Intel no garantiza ni asume responsabilidad en cuanto a la exactitud o integridad de cualquier informacin, texto, grficos, enlaces u otros elementos contenidos en el Software.

LIMITACIN DE RESPONSABILIDAD. INTEL Y SUS PROVEEDORES NO SERN RESPONSABLES EN NINGN CASO DE NINGUNA CLASE DE DAO (INCLUYENDO, PERO SIN LIMITARSE A ELLO, LA PRDIDA DE BENEFICIOS, LA INTERRUPCIN DE LA ACTIVIDAD COMERCIAL O LA PRDIDA DE INFORMACIN) DERIVADO DE LA UTILIZACIN O DE LA IMPOSIBILIDAD DE UTILIZAR EL SOFTWARE, INCLUSO EN EL CASO DE QUE INTEL HAYA TENIDO CONOCIMIENTO DE LA POSIBILIDAD DE DICHO DAO. EN CIERTAS JURISDICCIONES SE PROHBE LA EXCLUSIN O LIMITACIN DE RESPONSABILIDAD RESPECTO A GARANTAS IMPLCITAS O DAOS INDIRECTOS O CASUALES, POR LO QUE LAS LIMITACIONES MENCIONADAS PUEDEN NO SER APLICABLES EN SU CASO. ASIMISMO, ES POSIBLE QUE TENGA OTROS DERECHOS LEGALES QUE VAREN DE UNA JURISDICCIN A OTRA. En caso de que utilice el Software junto con un dispositivo virtual (“emulado”) diseado para aparecer como un producto de componente de Intel, reconoce que Intel no es el autor ni el creador del dispositivo virtual (“emulado”). Entiende y reconoce que Intel no hace ninguna declaracin sobre el funcionamiento correcto del Software cuando se utiliza con un dispositivo virtual (“emulado”), que Intel no dise el Software para que funcione conjuntamente con el dispositivo virtual (“emulado”) y que el Software puede no ser capaz de corregir el funcionamiento conjuntamente con el dispositivo virtual (“emulado”). Acepta asumir el riesgo de que el Software no funcione de forma correcta conjuntamente con el dispositivo virtual (“emulado”). Acepta indemnizar y mantener a Intel, sus directores, subsidiarias y afiliados libres de toda responsabilidad contra cualquier demanda, costo, dao y gasto y honorarios razonables de abogados que surjan de, directa o indirectamente, cualquier reclamo por productos defectuosos, daos personales o muerte relacionadas con el uso no previsto o no autorizado del Software conjuntamente con el dispositivo virtual (“emulado”), incluso si dicha accin se basa en que Intel fue negligente con respecto al diseo o fabricacin del Software.

USO NO AUTORIZADO. EL SOFTWARE NO EST DISEADO, PREVISTO O AUTORIZADO PARA SU USO EN CUALQUIER TIPO DE SISTEMA O APLICACIN EN LA QUE UN FALLO DE SOFTWARE PODRA CREAR UNA SITUACIN DONDE SE PRODUJERAN LESIONES PERSONALES O LA MUERTE (POR EJEMPLO, SISTEMAS MDICOS, DE SOPORTE VITAL O PARA SALVAR VIDAS). Si utiliza el Software para cualquier uso no previsto o no autorizado, deber indemnizar y considerar sin responsabilidad a Intel y sus directores, subsidiarias y afiliados contra cualquier demanda, costo, dao y gasto y honorarios razonables de abogados que surjan de, directa o indirectamente, cualquier reclamo por productos defectuosos, daos personales o muerte relacionadas con dicho uso no previsto o no autorizado, incluso si dicha accin se basa en que Intel fue negligente con respecto al diseo o fabricacin del componente.

RESCISIN DE ESTE CONTRATO. Si infringe los trminos de este Contrato, Intel puede rescindirlo en cualquier momento. Tras la rescisin, usted deber destruir inmediatamente el Software o devolver a Intel todas las copias del mismo.

LEGISLACIN APLICABLE. Las reclamaciones que surjan bajo este Contrato estarn regidas por las leyes del estado de California, independientemente de los principios de conflicto de leyes. Acepta que los trminos de la Convencin sobre contratos para la venta internacional de bienes de las Naciones Unidas no se aplican a este Contrato. Se prohbe exportar el Software si dicho acto violara cualquier ley o reglamento aplicable sobre exportaciones. Intel no est obligada por ningn otro contrato, a menos que ste se haya realizado por escrito y est firmado por un representante autorizado de Intel.

DERECHOS RESTRINGIDOS DEL ESTADO. El Software y la documentacin incluidos se desarrollaron a cargo de una iniciativa privada y se proporcionan con “DERECHOS LIMITADOS”. Su uso, reproduccin o divulgacin por el Gobierno est sujeto a las restricciones establecidas en FAR 52.227-14 y DFAR 252.227-7013 y siguientes o sus sucesoras. El uso de este producto por parte del Gobierno constituye el reconocimiento de los derechos de titularidad de Intel sobre el mismo. El contratista o fabricante es Intel.

IDIOMA; TRADUCCIONES. En el caso de que la versin en ingls de este Contrato est acompaada por cualquier otra versin traducida a otro idioma, dicha versin traducida slo se ofrece a ttulo informativo y prevalecer la versin en ingls.

ltima actualizacin 15/05/11 10:56p Revisin

DOCS/QUICK/ESN/note.gif0000755000000000000000000000073211651733270011443 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/ESN/qi_esn.htm0000755000000000000000000001423711550614566012010 0ustar Gua rpida de instalacin de adaptadores de red Intel(R)

Instalacin de adaptadores de red Intel®

Instalacin del adaptador Intel PCI, PCI-X o PCI Express*

  1. Apague su PC y desconecte el cable de energa.
  2. Quite la cubierta del sistema y la cubierta de la ranura del adaptador en la ranura que corresponde al adaptador.
  3. Coloque firmemente el conector del borde del adaptador en la ranura hasta que se haya insertado completamente. Asegure el soporte al chasis.
  4. Vuelva a colocar la cubierta de su PC. Conecte el cable de energa.

NOTA: Algunos adaptadores de servidor y escritorio Intel Gigabit utilizan el bus PCI Express. Puede utilizar una ranura ms larga que el conector del adaptador sin problemas, pero no intente realizar la instalacin en una ranura ms corta que el conector PCI Express.

Conexin del cable de red

Adaptadores Intel® PRO/100 y Gigabit de cobre: Conecte el cable o los cables de red al adaptador utilizando un cable de red Ethernet par trenzado (TPE) de Categora 3, 4 o 5 para redes de 10 Mbps. Utilice un cable de Categora 5 (de 4 pares) para redes de 100 o 1000 Mbps y para las redes residenciales.

Adaptadores Intel® Gigabit de fibra con conector SC: Retire y guarde la cubierta del conector de fibra ptica. Introduzca un conector de fibra ptica tipo SC 1000Base-SX dplex en los puertos TX/RX del soporte del adaptador.

Adaptadores Intel® Gigabit de fibra con conector LC: Retire y guarde la cubierta del conector de fibra ptica. Inserte un conector LC en el adaptador, con el cableado correcto para el tipo del adaptador (1000BASE-SX o 1000BASE-LX). Puede utilizar cables de conversin a otros tipos de conector (como SC) si el cableado se ajusta a las especificaciones pticas del adaptador, incluyendo las limitaciones de longitud.

Inicie su PC y siga las instrucciones de instalacin de los controladores que se ofrecen a continuacin.

Instalacin de los controladores

Sistemas operativos Windows

Para poder instalar los controladores, debe tener derechos de administrador en el sistema operativo.

  1. El adaptador se detecta automticamente, y Windows instala un controlador residente del sistema operativo o inicia el asistente Nuevo hardware encontrado .
  2. Si se inicia el asistente Se encontr nuevo hardware, pulse el botn Cancelar.
  3. Inserte el CD de Intel. Se inicia automticamente el programa de ejecucin automtica Conexiones de red Intel . Haga clic en el botn Instalar los controladores y el software .

Linux*

Para compilar un paquete RPM* binario de este controlador, ejecute 'rpmbuild -tb <nombre_de_archivo.tar.gz>'. Sustituya <nombrearchivo.tar.gz> por el nombre de archivo especfico del controlador.

NOTAS:

  • Para que la creacin funcione correctamente, el kernel en ejecucin DEBE coincidir con la versin y configuracin de las fuentes instaladas del kernel. Si acaba de recompilar el kernel, reinicie el sistema.

  • El funcionamiento de RPM slo se ha probado con las distribuciones Red Hat.

  • Para los adaptadores Intel PRO/100, utilice e100 como nombre de controlador.

  1. Mueva el archivo con la extensin tar del controlador base al directorio que seleccione. Por ejemplo, utilice '/home/username/e1000' o '/usr/local/src/e1000'.

  2. Descomprima el archivo tar o unzip, donde <x.x.x> es el nmero de versin del archivo tar del controlador:
    tar zxf e1000-<x.x.x>.tar.gz
  3. Vaya al directorio src del controlador. donde <x.x.x> es el nmero de versin del archivo tar del controlador:
    cd e1000-<x.x.x>/src/
  4. Compile el mdulo del controlador:
    make install
    El binario se instalar como:
    /lib/modules/<versin_kernel>/kernel/drivers/net/e1000.o

    Las ubicaciones de instalacin descritas anteriormente son las predeterminadas, y es posible que no sean correctas para determinadas distribuciones de Linux.

  5. Instale el mdulo:
    insmod e1000 <parmetro>=<valor>
  6. Asigne una direccin IP a la interfaz. Para ello, escriba lo siguiente, donde <x> es el nmero de interfaz:
    ifconfig eth<x> <direccin_IP>
  7. Compruebe que funcione la interfaz. Escriba lo siguiente, donde <direccin_IP> es la direccin IP de otra mquina en la misma subred donde se encuentra la interfaz que se est probando:
    ping <direccin_IP>

Otros sistemas operativos

Para instalar otros controladores, consulte la Gua del usuario en el CD del adaptador o visite el sitio web de soporte de clientes: http://www.intel.com/p/es_XL/support/.

*Informacin legal

ltima modificacin: 11-10-07 15:48 Revisin 14

DOCS/QUICK/ESN/style.css0000755000000000000000000000450511651733270011663 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/ESN/warranty.htm0000755000000000000000000001523611550614566012401 0ustar Garanta limitada de duracin de hardware

Garanta limitada de duracin de hardware

Intel garantiza al propietario original que el producto de adaptador proporcionado en este paquete no tendr defectos en el material o en la manufactura. Esta garanta no cubre el producto de adaptador si ste se daa durante el proceso de instalacin o si se utiliza de forma indebida.

LA GARANTA ANTERIOR TOMA EL LUGAR DE CUALQUIER OTRA GARANTA, YA SEA EXPLCITA, IMPLCITA O ESTABLECIDA POR LA LEY, INCLUSO SIN LIMITACIN CUALQUIER GARANTA DE FALTA DE CUMPLIMIENTO DE PROPIEDAD INTELECTUAL, COMERCIABILIDAD O IDONEIDAD PARA UN PROPSITO PARTICULAR QUE SURGIESE DE CUALQUIER PROPUESTA, ESPECIFICACIN O MUESTRA.

Esta garanta no cubre el reemplazo de productos de adaptador daados por abuso, accidente, uso indebido, negligencia, alteracin, reparacin, desastre, instalacin incorrecta o prueba inapropiada. Si se determina que el producto de adaptador est defectuoso, Intel, a su propia discrecin, reemplazar o reparar el producto de hardware sin ningn cargo con excepcin de lo estipulado ms adelante, o bien, reembolsar el precio de compra siempre y cuando usted entregue el producto de adaptador junto con un nmero de Autorizacin de devolucin de material (RMA) (vase ms adelante) y junto con la prueba de compra (si no se ha registrado), ya sea al distribuidor a travs del cual lo adquiri o a Intel, con una explicacin de cualquier deficiencia. Si enva el producto de adaptador, usted asume el riesgo de dao o prdida durante el transporte. Usted debe utilizar el contenedor original (o su equivalente) y pagar por el cargo de transporte.

Intel puede reemplazar o reparar el producto de adaptador ya sea con piezas nuevas o reacondicionadas, y cualquier producto de adaptador o pieza del mismo que Intel reemplace se convierte en propiedad de Intel. Los productos de adaptador reparados o reemplazados se devolvern a usted con el mismo nivel de revisin que se recibi o uno ms alto, a la discrecin de Intel. Intel se reserva el derecho de reemplazar los productos de adaptador descontinuados con un producto de adaptador de una generacin actual equivalente

Devolucin de productos defectuosos

En Amrica del Norte:

Antes de devolver cualquier producto de adaptador, comunquese con la Asistencia al cliente Intel y obtenga un nmero de Autorizacin de devolucin de material (RMA). Para ello, llame al +1 916-377-7000.

Si el grupo de asistencia al cliente verifica que el producto de adaptador est defectuoso, harn que el departamento de RMA emita un nmero RMA, el cual debe colocarse en la parte externa del paquete del producto de adaptador. Intel no aceptar ningn producto que no contenga un nmero RMA en el paquete.

Todas las dems ubicaciones:

Devuelva el producto de adaptador al punto de venta para obtener un reembolso o reemplazo.

Garanta de devolucin de dinero para adaptadores Intel (solamente en Amrica del Norte)

Intel desea su total satisfaccin con el producto de adaptador Intel que ha comprado. En cualquier momento dentro de los noventa (90) das a partir de la compra, usted puede devolver el adaptador Intel al punto de venta original para obtener el reembolso total del precio de compra a travs del distribuidor. Los vendedores y distribuidores, respectivamente, que acepten devoluciones y reembolsen dinero a sus clientes pueden devolver los adaptadores Intel a sus puntos de venta originales. Intel garantiza que aceptar las devoluciones bajo esta poltica y que reembolsar el precio de compra original a los clientes que compren directamente a travs de Intel.

Limitacin de responsabilidad y remedio

LA NICA RESPONSABILIDAD DE INTEL ESTIPULADA EN ESTE DOCUMENTO SE LIMITAR A LOS DAOS DIRECTOS QUE PUEDAN MEDIRSE DE FORMA OBJETIVA. BAJO NINGUNA CIRCUNSTANCIA INTEL TENDR NINGUNA RESPONSABILIDAD POR CUALQUIER DAO INDIRECTO O ESPECULATIVO (INCLUSO SIN LIMITACIN LOS DAOS PRECEDENTES, CONSIGUIENTES, FORTUITOS Y ESPECIALES) LO CUAL INCLUYE, SIN LIMITACIN, EL INCUMPLIMIENTO DE PROPIEDAD INTELECTUAL, LOS COSTOS DE READQUISICIN, LA PRDIDA DE USO, LAS INTERRUPCIONES COMERCIALES, LA PRDIDA DE REPUTACIN Y LA PRDIDA DE GANANCIAS, YA SEA QUE CUALQUIERA DE ESOS DAOS SURJAN POR NEGLIGENCIA CONTRACTUAL, RESPONSABILIDAD EXTRACONTRACTUAL O BAJO CUALQUIER GARANTA, INDEPENDIENTEMENTE DE SI INTEL RECIBE UN AVISO POR ANTICIPADO DE LA POSIBILIDAD DE CUALQUIERA DE ESTOS DAOS. A PESAR DE LO ANTERIORMENTE MENCIONADO, LA RESPONSABILIDAD TOTAL DE INTEL PARA CUALQUIER RECLAMO QUE SURJA BAJO ESTE CONTRATO NO EXCEDER EL PRECIO PAGADO POR EL PRODUCTO. ESTAS LIMITACIONES DE RESPONSABILIDADES POSIBLES CONSTITUYERON UN ELEMENTO ESENCIAL EN LA FIJACIN DEL PRECIO DEL PRODUCTO. INTEL NO ASUME NI AUTORIZA QUE NADIE ASUMA NINGUNA OTRA RESPONSABILIDAD EN SU NOMBRE.

Algunos estados no permiten la exclusin o limitacin de daos fortuitos o consiguientes, de modo que las limitaciones anteriores podran no aplicarse en su caso.

Aplicaciones de control crtico: Intel de forma especfica niega cualquier responsabilidad por el uso del producto de adaptador en aplicaciones de control crtico (incluso, solamente como ejemplo, los sistemas de control de atencin mdica, los sistemas de control de energa nuclear o los sistemas de control de trfico areo o terrestre) por los Titulares de licencia o los Titulares de sublicencia, y dicho uso se realiza bajo el riesgo total del usuario. El Titular de licencia acuerda defender, indemnizar y asumir responsabilidad ante Intel por cualquier reclamo que surgiese del uso del producto de adaptador en dichas aplicaciones del Titular de licencia o Titulares de sublicencia.

Software: El software proporcionado con el producto de adaptador no est cubierto bajo la garanta de hardware descrita anteriormente. Consulte el contrato de licencia de software correspondiente, el cual acompaa al producto del adaptador, para obtener detalles sobre la garanta de software.

ltima modificacin: 23-7-02 10:42 Revisin 6

DOCS/QUICK/FRA0000755000000000000000000000000011761422164007705 5ustar DOCS/QUICK/FRA/legaldis.htm0000755000000000000000000000226111730046352012263 0ustar Avertissement

Copyright et exclusions de responsabilit

Copyright © 2002 - 2012 Intel Corporation. Tous droits rservs.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OREGON 97124-6497 tats-Unis

Intel Corporation dcline toute responsabilit pour toute erreur ou omission dans ce document. Intel ne s'engage aucunement mettre jour les informations contenues dans ce document.

Intel, Itanium et Pentium sont des marques de commerce d'Intel Corporation aux tats-Unis et dans d'autres pays.

* Les autres marques et noms de produits sont des marques commerciales appartenant leurs propritaires respectifs.

Informations concernant la garantie

Licence du logiciel

 

Dernire modification le 25/01/11 22h21 Rvision DOCS/QUICK/FRA/license.htm0000755000000000000000000004053611730046352012130 0ustar Licence du logiciel

CONTRAT DE LICENCE DU LOGICIEL INTEL

IMPORTANT - LIRE AVANT TOUTE TENTATIVE DE COPIE, D'INSTALLATION OU D'UTILISATION :

Ne copiez pas, n'installez pas et n'utilisez pas ce logiciel ni tout lment associ (appels collectivement le  Logiciel ) fournis dans le cadre de ce contrat de licence ( Contrat ) tant que vous n'avez pas lu attentivement les conditions gnrales suivantes.

En copiant, installant ou autrement utilisant le Logiciel, vous acceptez d'tre li aux modalits de ce Contrat. Si vous n'acceptez pas les modalits de ce Contrat, ne copiez pas, n'installez pas et n'utilisez pas le Logiciel.

CONTRATS DE LICENCE.

Veuillez noter :

  • Si vous tes un administrateur rseau, reportez-vous la  Licence de site  ci-dessous.
  • Si vous tes un utilisateur final, reportez-vous la Licence utilisateur unique ci-dessous.
  • Si vous tes un fabricant OEM, reportez-vous la Licence OEM .

LICENCE DE SITE. Vous pouvez copier le Logiciel sur les ordinateurs de votre organisation afin qu'il soit utilis dans le cadre des activits de l'organisation et vous pouvez sauvegarder un nombre raisonnable de copies du Logiciel, conformment ces conditions :

  1. Ce Logiciel est accord sous licence pour une utilisation exclusive avec (a) des composants physiques Intel et (b) des priphriques virtuels ( mul ) conus pour apparatre comme des composants Intel dans un systme d'exploitation Invit excut dans le contexte d'un ordinateur virtuel. Toute autre utilisation du Logiciel, y compris, sans s'y limiter, toute utilisation avec des composants non Intel, n'est pas couverte par la licence ci-aprs.
  2. Sous rserve des modalits de ce Contrat, Intel Corporation ( Intel ) vous accorde une licence non exclusive, non transfrable, d'utiliser les lments.
  3. Vous n’tes pas autoris copier, modifier, louer, vendre, distribuer, ni transfrer une partie quelconque du Logiciel, sauf dans la mesure prvue par le prsent Contrat, et vous vous engagez empcher toute copie non autorise du Logiciel.
  4. Vous n'tes pas autoris reconstituer la logique du Logiciel, le dcompiler ou le dsassembler.
  5. Le Logiciel peut inclure des portions sujettes des modalits complmentaires aux prsentes, dfinies dans une licence accompagnant ces portions.

LICENCE UTILISATEUR UNIQUE. Vous pouvez copier le Logiciel sur un seul ordinateur pour une utilisation personnelle, et vous pouvez effectuer une copie de sauvegarde du Logiciel, conformment ces conditions :

  1. Ce Logiciel est accord sous licence pour une utilisation exclusive avec (a) des composants physiques Intel et (b) des priphriques virtuels ( mul ) conus pour apparatre comme des composants Intel dans un systme d'exploitation Invit excut dans le contexte d'un ordinateur virtuel. Toute autre utilisation du Logiciel, y compris, sans s'y limiter, toute utilisation avec des composants non Intel, n'est pas couverte par la licence ci-aprs.
  2. Sous rserve des modalits de ce Contrat, Intel Corporation ( Intel ) vous accorde une licence non exclusive, non transfrable, d'utiliser les lments.
  3. Vous n’tes pas autoris copier, modifier, louer, vendre, distribuer, ni transfrer une partie quelconque du Logiciel, sauf dans la mesure prvue par le prsent Contrat, et vous vous engagez empcher toute copie non autorise du Logiciel.
  4. Vous n'tes pas autoris reconstituer la logique du Logiciel, le dcompiler ou le dsassembler.
  5. Le Logiciel peut inclure des portions sujettes des modalits complmentaires aux prsentes, dfinies dans une licence accompagnant ces portions.

LICENCE OEM. Vous pouvez reproduire et distribuer le Logiciel uniquement s'il fait partie intgrante ou est incorpor votre produit, comme une mise jour de maintenance de Logiciel autonome pour les utilisateurs existants de vos produits, l'exclusion de tout autre produit autonome, ou en tant que composant d'une distribution plus tendue du Logiciel, y compris, mais sans s'y limiter, la distribution d'une image d'installation ou d'une image d'Ordinateur Virtuel Invit, sous rserve de ces conditions :

  1. Ce Logiciel est accord sous licence pour une utilisation exclusive avec (a) des composants physiques Intel et (b) des priphriques virtuels ( mul ) conus pour apparatre comme des composants Intel dans un systme d'exploitation Invit excut dans le contexte d'un ordinateur virtuel. Toute autre utilisation du Logiciel, y compris, sans s'y limiter, toute utilisation avec des composants non Intel, n'est pas couverte par la licence ci-aprs.
  2. Sous rserve des modalits de ce Contrat, Intel Corporation ( Intel ) vous accorde une licence non exclusive, non transfrable, d'utiliser les lments.
  3. Vous n’tes pas autoris copier, modifier, louer, vendre, distribuer, ni transfrer une partie quelconque du Logiciel, sauf dans la mesure prvue par le prsent Contrat, et vous vous engagez empcher toute copie non autorise du Logiciel.
  4. Vous n'tes pas autoris reconstituer la logique du Logiciel, le dcompiler ou le dsassembler.
  5. Vous tes autoris distribuer le Logiciel vos clients conformment un contrat de licence crit. L'ouverture de l'emballage scell entrane l'acceptation implicite des modalits du contrat de licence. Cette licence doit au minimum protger les droits de proprit du Logiciel d'Intel.
  6. Le Logiciel peut inclure des portions sujettes des modalits complmentaires aux prsentes, dfinies dans une licence accompagnant ces portions.

RESTRICTIONS DE LA LICENCE. Vous ne pouvez PAS : (i) utiliser ou copier les lments sauf comme stipul dans ce Contrat ; (ii) louer ou offrir en location-bail les lments un tiers ; (iii) affecter ce Contrat ou transfrer les lments sans autorisation crite expresse d'Intel ; (iv) modifier, adapter ou traduire tout ou partie des lments sauf comme stipul dans ce Contrat ; (v) reconstituer la logique, dcompiler ou dsassembler les lments ; (vi) tenter de modifier ou d'altrer la fonction normale du gestionnaire de licence qui rgit l'utilisation des lments ; (vii) distribuer, offrir des sous-licences ou transfrer le Code source de tout composant des lments, des Redistribuables et de la source d'exemple et de produits drivs un tiers sauf comme stipul dans ce Contrat.

EXCLUSION DES AUTRES DROITS. Aucun droit ou licence ne vous est accord par Intel, de manire explicite ou implicite, en ce qui concerne toute information ou tout brevet propritaire, droit d'auteur, moyen de masquage, marque commerciale, secret industriel ou tout autre droit de proprit intellectuelle contrl par Intel, sauf stipulation contraire dcrite dans ce Contrat. Sauf comme stipul dans la prsente, aucune licence et aucun droit ne vous est accord, directement ou implicitement, de faon induite, par prclusion, ou autre. Spcifiquement, Intel ne vous accorde aucun droit expresse ou induit concernant les brevets, droits d'auteur, marques de commerce ou droits de proprit intellectuelle d'Intel.

PROPRIT DU LOGICIEL ET COPYRIGHT (DROITS D'AUTEUR). Le Logiciel est offert sous licence, il n'est pas vendu. Intel demeure propritaire de toutes les copies du Logiciel. Le logiciel est protg par les lois sur les droits d'auteur, les lois en vigueur aux tats-Unis et dans d'autres pays, ainsi que par les dispositions de traits internationaux. Vous n'tes pas autoris retirer la mention de copyright du Logiciel. Vous acceptez de prvenir toute copie non autorise du Logiciel. Intel peut modifier le Logiciel ou des lments rfrencs dans ce document, tout moment et sans pravis, mais n'est pas dans l'obligation de mettre jour le Logiciel ni d'offrir une assistance. Vous pouvez transfrer le Logiciel uniquement si le bnficiaire accepte d'tre li par ces modalits et si vous ne conservez aucune copie du Logiciel.

MODALITS COMPLMENTAIRES CONCERNANT LA VERSION PRLIMINAIRE DU LOGICIEL. Si le Logiciel que vous installez ou utilisez dans le cadre de ce Contrat est une version de prcommercialisation ou s'il est tiquet ou autrement reprsent comme une version  alpha  ou  bta  du Logiciel ( Logiciel prliminaire ), les modalits suivantes sont applicables.

Dans l'ventualit ou des clauses de cette Section entreraient en conflit avec d'autres modalits de ce Contrat concernant le Logiciel prliminaire, cette Section remplacerait les autres modalits, mais uniquement dans la mesure ncessaire la rsolution du conflit.
Vous comprenez et reconnaissez que le Logiciel est un Logiciel prliminaire, qu'il ne reprsente pas la version finale du Logiciel d'Intel, et qu'il peut contenir des erreurs et d'autres problmes pouvant entraner des pertes de donnes, des pannes de systme et d'autres erreurs. Le Logiciel prliminaire vous est fourni  en l'tat  et Intel n'met aucune garantie et rejette toute responsabilit votre gard concernant les dommages issus de l'utilisation du Logiciel prliminaire.
Vous reconnaissez qu'Intel n'a pas promis que le Logiciel prliminaire serait commercialis l'avenir, qu'Intel n'a aucune obligation expresse ou induite envers vous concernant la commercialisation du Logiciel prliminaire et qu'il est possible qu'Intel n'introduise pas de Logiciel compatible avec le Logiciel prliminaire. Vous reconnaissez que les efforts de recherche et de dveloppement que vous consentez concernant le Logiciel prliminaire ou tout produit utilisant ou associ au Logiciel prliminaire le sont vos propres risques.
Si Intel vous a fourni un Logiciel prliminaire dans le cadre d'un accord crit spar, votre utilisation du Logiciel prliminaire est galement rgie par l'accord en question.

GARANTIE LIMITE DU SUPPORT. Si le logiciel a t remis par Intel sur un support physique, Intel garantit que celui-ci est exempt de dfauts matriels pendant une priode de quatre-vingt-dix jours compter de la date de livraison par Intel. Si un tel dfaut est dtect, renvoyez le support Intel qui pourra choisir de le remplacer ou d'employer une autre mthode de livraison.

EXCLUSION DE TOUTE AUTRE GARANTIE. L'EXCEPTION DES CAS CI-DESSUS, LE LOGICIEL EST FOURNI EN L'TAT , SANS GARANTIE EXPRESSE OU IMPLICITE D'AUCUNE SORTE, NOTAMMENT TOUTE GARANTIE DE QUALIT MARCHANDE, D'ABSENCE DE CONTREFAON OU D'ADQUATION UN USAGE PARTICULIER. Intel ne garantit pas la prcision ni l'exhaustivit des informations, des textes, des graphiques, des liens ou d'autres lments contenus dans le Logiciel et ne peut en tre tenu responsable.

LIMITATION DE RESPONSABILIT. EN AUCUN CAS INTEL OU SES FOURNISSEURS NE POURRONT TRE TENUS POUR RESPONSABLES DE TOUT DOMMAGE, DE QUELQUE NATURE QUE CE SOIT (Y COMPRIS, MAIS DE MANIRE NON LIMITATIVE, TOUTE PERTE DE BNFICES, INTERRUPTION D'ACTIVIT OU PERTE D'INFORMATIONS), RSULTANT DE L'UTILISATION OU DE L'IMPOSSIBILIT D'UTILISER LE LOGICIEL, ET CE MME SI INTEL A T PRVENU DE L'VENTUALIT DE TELS DOMMAGES. CERTAINES JURIDICTIONS N'AUTORISENT PAS L'EXCLUSION OU LA LIMITATION DE RESPONSABILIT POUR LES GARANTIES IMPLICITES OU LES DOMMAGES INDIRECTS OU ACCESSOIRES, DE SORTE QUE LA LIMITATION CI-DESSUS PEUT NE PAS VOUS TRE APPLICABLE. VOUS POUVEZ GALEMENT DISPOSER D'AUTRES DROITS QUI VARIENT DE JURIDICTION EN JURIDICTION. Dans l'ventualit o vous utilisez le Logiciel conjointement avec un priphrique virtuel ( mul ) conu pour apparatre comme un composant Intel, vous reconnaissez qu'Intel n'est ni l'auteur ni le crateur du priphrique virtuel ( mul ). Vous comprenez et reconnaissez qu'Intel ne fait aucune reprsentation concernant le fonctionnement correct du Logiciel lorsqu'il est utilis avec un priphrique virtuel ( mul ), qu'Intel n'a pas conu le Logiciel pour qu'il fonctionne conjointement avec le priphrique virtuel ( mul ), et qu'il est possible que le Logiciel ne soit pas capable de fonctionner correctement conjointement avec le priphrique virtuel ( mul ). Vous acceptez d'assumer le risque que le Logiciel ne fonctionne pas correctement conjointement avec le priphrique virtuel ( mul ). Vous acceptez d'indemniser Intel et ses responsables et filiales et de les protger contre les plaintes, cots, dommages, dpenses et honoraires d'avocat ventuels issus, directement ou indirectement de toute plainte concernant la responsabilit du produit, des blessures ou la mort associes l'utilisation du Logiciel conjointement avec le priphrique virtuel ( mul ), mme si cette plainte prtend qu'Intel a t ngligent concernant la conception ou la fabrication du Logiciel.

UTILISATION NON AUTORISE. LE LOGICIEL N'EST PAS CONU, PRVU OU AUTORIS POUR UNE UTILISATION AVEC TOUT TYPE DE SYSTME OU D'APPLICATION DONT UNE DFAILLANCE LOGICIELLE POURRAIT ENTRANER DES BLESSURES OU LA MORT (PAR EX., SYSTMES MDICAUX, SYSTMES DE MAINTIEN DE LA VIE OU DE SURVIE). Si vous utilisez le Logiciel dans un cadre non prvu ou non autoris, vous acceptez d'indemniser Intel et ses responsables et filiales et de les protger contre les plaintes, cots, dommages, dpenses et honoraires d'avocat ventuels issus, directement ou indirectement de toute plainte concernant la responsabilit du produit, des blessures ou la mort associes l'utilisation du Logiciel dans un cadre non prvu ou non autoris, mme si cette plainte prtend qu'Intel a t ngligent concernant la conception ou la fabrication de la pice.

RSILIATION DE CE CONTRAT. Intel peut rsilier ce contrat tout moment si vous n'en respectez pas les termes. Dans ce cas, vous devez immdiatement dtruire le Logiciel et retourner toutes les copies dudit Logiciel Intel.

LOIS APPLICABLES. Les plaintes dposes dans le cadre de ce Contrat seront rgies par les lois de l'tat de Californie, sans considration pour les principes de conflit de lois. Vous acceptez que les termes de la Convention des Nations Unies sur les contrats de vente internationale de marchandises ne s'appliquent pas ce Contrat. Vous n'tes pas autoris exporter le Logiciel en infraction des lois et des rgulations d'exportation applicables. Intel n'est contraint par aucun autre contrat moins que celui-ci ne soit tabli par crit et sign par un reprsentant autoris d'Intel.

LIMITATION DES DROITS DU GOUVERNEMENT. Le Logiciel et la documentation inclus ont t dvelopps avec des fonds privs, et sont fournis avec des  DROITS RESTREINTS . L'utilisation, la duplication ou la diffusion par le gouvernement est soumise des restrictions comme indiqu dans les clauses FAR.52.227-14 et DFAR.252.227-7013 et suivantes ou leurs successeurs. L'utilisation de ce produit par le Gouvernement constitue une reconnaissance des droits de proprit d'Intel sur le Logiciel. Le sous-traitant ou le fabricant est Intel.

LANGUE ; TRADUCTIONS. Au cas o la version en langue anglaise de cet Accord est accompagne d’une autre version traduite dans une autre langue, la version traduite est fournie uniquement pour des raisons de commodit et seule la version anglaise fait foi.

Dernire mise jour le 15/05/11 22h56 Rvision

DOCS/QUICK/FRA/note.gif0000755000000000000000000000073211651733270011426 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/FRA/qi_fra.htm0000755000000000000000000001451111546611560011745 0ustar Guide d'installation rapide des cartes rseau Intel(R)

Installation des cartes rseau Intel®

Installer une carte Intel PCI, PCI-X ou PCI-Express*

  1. Mettez l'ordinateur hors tension et dbranchez le cordon d'alimentation.
  2. Retirez le panneau de l'ordinateur et le panneau du connecteur de carte correspondant votre carte.
  3. Insrez fermement le connecteur au bord de la carte dans le connecteur, jusqu' ce qu'il soit compltement log. Fixez solidement le support sur le chssis.
  4. Remettez le panneau de l'ordinateur en place. Branchez le cordon d'alimentation.

REMARQUE : certaines cartes Intel Gigabit pour serveurs et PC de bureau utilisent le bus PCI Express. Vous pouvez utiliser sans inconvnient un emplacement plus long que le connecteur de la carte, mais n'essayez pas d'installer la carte dans un emplacement plus court que le connecteur PCI Express.

Brancher le cble rseau

Cartes Intel® PRO/100 et Gigabit cuivre : Branchez le(s) cble(s) rseau sur la carte en utilisant une paire torsade Ethernet de catgorie 3, 4 ou 5 pour les rseaux 10 Mbit/s. Utilisez un cble de catgorie 5 (4 paires) pour les rseaux 100 Mbit/s ou 1000 Mbit/s, ainsi que pour tout rseau rsidentiel.

Cartes Intel® Gigabit fibre avec connecteur SC : retirez le panneau du connecteur fibre optique et mettez-le de ct. Insrez un connecteur SC fibre optique de type 1000Base-SX duplex dans les ports TX/RX du support de la carte.

Cartes Intel® Gigabit fibre avec connecteur LC : retirez le panneau du connecteur fibre optique et mettez-le de ct. Insrez un connecteur LC dans la carte en utilisant un cblage appropri pour le type de carte (1000BASE-SX ou 1000BASE-LX). Les cbles de conversion pour d'autres types de connecteur (p. ex., un connecteur SC) peuvent tre utiliss si le cblage est conforme aux spcifications optiques de la carte, y compris les limites de longueur.

Dmarrez votre ordinateur et suivez les instructions d'installation des pilotes ci-dessous.

Installer les pilotes

Systmes d'exploitation Windows

Notez que vous devez possder des droits d'administrateur sur le systme d'exploitation pour installer les pilotes.

  1. La carte est dtecte et Windows installe un pilote rsidant sous Windows ou dmarre l'Assistant Nouveau matriel dtect .
  2. Si l'assistant Nouveau matriel dtect dmarre, appuyez sur le bouton Annuler.
  3. Insrez le CD Intel. Le programme d'excution automatique Connexions rseau Intel® dmarre automatiquement. Cliquez sur le bouton Installer les pilotes et logiciels .

Linux*

Pour crer un paquage RPM* binaire de ce pilote, excutez "rpmbuild -tb <nom_de_fichier.tar.gz>". Remplacez <filename.tar.gz> par le nom de fichier spcifique du pilote.

REMARQUES :

  • pour que la compilation fonctionne correctement, le noyau en cours d'excution DOIT correspondre la version et la configuration des sources de noyau installes. Si vous venez de recompiler le noyau, redmarrez l'ordinateur maintenant.

  • La fonctionnalit RPM a t teste uniquement sur les distributions Red Hat.

  • Pour les cartes Intel PRO/100, utilisez e100 comme nom de pilote.

  1. Placez le fichier tar du pilote de base dans le rpertoire de votre choix. Par exemple, utilisez '/home/utilisateur/e1000' ou '/usr/local/src/e1000'.

  2. Dcompressez l'archive, o <x.x.x> est le numro de version du fichier tar du pilote :
    tar zxf e1000-<x.x.x>.tar.gz
  3. Passez au rpertoire src du pilote en entrant la commande suivante, o <x.x.x> correspond au numro de version du paquetage du pilote :
    cd e1000-<x.x.x>/src/
  4. Compilez le module du pilote :
    make install
    Les instructions binaires sont installes comme suit :
    /lib/modules/<version_noyau>/kernel/drivers/net/e1000.o

    Les emplacements d'installation rpertoris ci-dessus sont les emplacements par dfaut. Il se peut qu'ils ne soient pas corrects sur certaines distributions Linux.

  5. Installez le module :
    insmod e1000 <paramtre>=<valeur>
  6. Affectez une adresse IP l'interface en entrant la commande suivante, o <x> correspond au numro d'interface :
    ifconfig eth<x> <adresse_IP>
  7. Vrifiez que l'interface fonctionne. Entrez la commande suivante, o <adresse_IP> correspond l'adresse IP d'un autre ordinateur du mme sous-rseau que celui sur lequel l'interface est teste :
    ping <adresse_IP>

Autres systmes d'exploitation

Pour installer d'autres pilotes, voir le Guide de l'utilisateur sur le CD de la carte ou visitez le site Web de l'assistance la clientle : http://www.intel.com/p/fr_FR/support/.

*Avertissement

Dernire mise jour le 11.10.07 15h48 Rvision 14

DOCS/QUICK/FRA/style.css0000755000000000000000000000450511651733270011646 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/FRA/warranty.htm0000755000000000000000000001414311546611560012354 0ustar Garantie vie limite sur le matriel

Garantie vie limite sur le matriel

Intel garantit au propritaire original que la carte livre dans ce coffret est dpourvue de tout dfaut de matriel ou de fabrication. Cette garantie ne couvre pas la carte si elle a t endommage au cours de l'installation ou utilise de faon incorrecte.

LA GARANTIE CI-DESSUS REMPLACE TOUTE AUTRE GARANTIE, EXPLICITE, IMPLICITE OU RGLEMENTAIRE, Y COMPRIS MAIS SANS S'Y LIMITER, LES GARANTIES DE QUALIT MARCHANDE, DE RESPECT DES DROITS DE PROPRIT INTELLECTUELLE OU DADAPTATION UN USAGE PARTICULIER QUI DCOULERAIT DUNE PROPOSITION, DUNE SPCIFICATION OU BIEN DUN CHANTILLON

Cette garantie ne couvre pas le remplacement des cartes endommages suite une utilisation non conforme aux instructions, un usage inappropri, la ngligence, un accident, un abus, une altration, une rparation, un dsastre, une installation incorrecte ou un test incorrect. Si la carte est dfectueuse, Intel pourra, sa discrtion, remplacer ou rparer gratuitement le matriel sauf dans les cas dcrits ci-dessous, ou rembourser le prix d'achat condition que vous retourniez la carte avec un numro d'autorisation de retour (RMA) [voir ci-dessous], une preuve d'achat (si votre produit n'a pas t enregistr), soit au fournisseur chez qui vous avez achet la carte, soit Intel, en incluant une description du problme. Les risques de dommage ou de perte associs l'envoi du produit sont votre responsabilit. Vous devez utiliser l'emballage original (ou un emballage similaire) et payer les frais d'envoi.

Intel peut remplacer ou rparer la carte en utilisant des pices nouvelles ou remises neuf, et toute carte ou pice de carte remplace par Intel deviendra la proprit d'Intel. Les cartes rpares ou remplaces vous seront retournes au mme niveau de rvision reu ou un niveau suprieur, la discrtion d'Intel. Intel se rserve le droit de remplacer les cartes abandonnes par une carte quivalente de la gnration actuelle.

Retourner un produit dfectueux

Depuis l'Amrique du Nord :

Avant de retourner une carte, contactez le support client d'Intel et obtenez un numro d'autorisation de retour (RMA) en appelant le +1 (916) 377-7000.

Aprs vrification par le groupe de support client que le produit est dfectueux, le groupe demandera au service RMA d'mettre un numro RMA que vous devrez apposer sur le carton d'envoi de la carte. Intel n'acceptera aucun produit sans numro RMA appos sur le colis.

Tous les autres pays :

retournez la carte au lieu d'achat pour obtenir un remboursement ou une carte de remplacement.

Remboursement garanti sur les cartes Intel (Amrique du Nord uniquement)

Votre entire satisfaction des cartes Intel que vous avez achetes est trs importante pour Intel. Pour une priode de quatre-vingt dix (90) jours compter de la date d'achat, vous pouvez retourner la carte Intel au lieu d'achat original pour obtenir un remboursement total. Les revendeurs et les distributeurs acceptant les retours et remboursant leurs clients, respectivement, peuvent retourner les cartes Intel au lieu d'achat original. En vertu de la prsente, Intel garantit que les retours seront accepts et que le prix d'achat original sera rembours aux clients qui ont achets leur produit directement auprs d'Intel.

Limitation de responsabilit et recours

SELON CETTE GARANTIE, LA RESPONSABILIT D'INTEL SERA LIMITE AUX DOMMAGES DIRECTS ET MESURABLES OBJECTIVEMENT. INTEL NE SERA EN AUCUN CAS RESPONSABLE DES DOMMAGES INDIRECTS OU SPCULATIFS (Y COMPRIS ET SANS LIMITATION, LES DOMMAGES CONSCUTIFS, ACCIDENTELS ET SPCIAUX), Y COMPRIS, MAIS SANS S'Y LIMITER, LE RESPECT DE LA PROPRIT INTELLECTUELLE, LES COTS DE RAPPROVISIONNEMENT, LA PERTE D'UTILISATION, LES INTERRUPTIONS DACTIVITS ET LA PERTE DE BNFICES, QUE CES DOMMAGES DCOULENT D'UNE NGLIGENCE CONTRACTUELLE, D'UNE FAUTE, OU DE TOUTE GARANTIE, MME SI INTEL A T NOTIFI DE LA POSSIBILIT DE TELS DOMMAGES. NONOBSTANT CE QUI PRCDE, LA RESPONSABILIT TOTALE D'INTEL EN CAS DE RECOURS LI AU PRSENT CONTRAT NE POURRA DPASSER LE PRIX D'ACHAT PAY POUR LE PRODUIT. CES LIMITATIONS DES RESPONSABILITS POTENTIELLES CONSTITUAIENT UN LMENT ESSENTIEL POUR LA DTERMINATION DU PRIX DU PRODUIT. INTEL N'ASSUME NI N'AUTORISE QUICONQUE ASSUMER TOUTES AUTRES RESPONSABILITS.

Certains pays n'autorisent pas l'exclusion ou la limitation des dommages accidentels ou conscutifs, auquel cas les limitations susmentionnes peuvent ne pas vous tre applicables.

Applications de contrle critiques : Intel dcline toute responsabilit en cas d'utilisation de la carte dans des applications de contrle critiques (comme par exemple, les systmes de contrle mdicaux, de la scurit, de l'nergie nuclaire ou du trafic arien) par le dtenteur de la licence ou les sous-licencis. Ceux-ci assument tous les risques lis une telle utilisation. Le dtenteur de la licence accepte de dfendre, d'indemniser et de protger Intel contre les rclamations dcoulant de l'utilisation de la carte dans de telles applications par le dtenteur de la licence ou les sous-licencis.

Logiciel : Le logiciel fourni avec la carte n'est pas couvert par la garantie sur le matriel dcrite ci-dessus. Reportez-vous au contrat de licence logicielle appropri livr avec la carte pour plus d'informations sur les garanties logicielles.

Dernire mise jour le 23 juillet 2002 10h42 Rvision 6

DOCS/QUICK/ITA0000755000000000000000000000000011761422164007712 5ustar DOCS/QUICK/ITA/legaldis.htm0000755000000000000000000000217311730046352012272 0ustar Informazioni legali

Copyright e declinazioni di responsabilit legali

Copyright © 2002 - 2012 Intel Corporation. Tutti i diritti riservati.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Intel Corporation non si assume alcuna responsabilit per eventuali errori o omissioni presenti in questo documento. Inoltre, Intel non si assume alcun impegno di aggiornare le informazioni ivi contenute.

Intel, Itanium e Pentium sono marchi registrati di Intel Corporation negli Stati Uniti e in altri paesi.

*Gli altri marchi e nomi potrebbero essere propriet di terzi.

Informazioni sulla garanzia

Licenza software

 

Ultima modifica: 25/1/11 22:21 Revisione DOCS/QUICK/ITA/license.htm0000755000000000000000000004027011730046352012130 0ustar Licenza software

CONTRATTO DI LICENZA DEL SOFTWARE INTEL

IMPORTANTE - LEGGERE PRIMA DI COPIARE, INSTALLARE O UTILIZZARE.

Non copiare, installare o usare questo software e l’eventuale materiale ad esso associato (definiti collettivamente con il termine “Software”) che sono forniti in base al presente Contratto di licenza (“Contratto”) senza avere prima letto attentamente i termini e le condizioni che seguono.

Copiando, installando o altrimenti utilizzando il Software, si accetta di essere vincolati dai termini di questo Contratto. Se non si accettano i termini di questo Contratto, non copiare, installare o usare il Software.

LICENZE:

Notare:

  • La "Licenza di sito" seguente si applica agli amministratori di rete o dei sistemi.
  • La "Licenza per utente singolo" si applica agli utenti finali.
  • La sezione “Licenza OEM” si applica ai produttori originali del computer (OEM).

LICENZA DI SITO: possibile copiare il Software sui computer di una azienda per un utilizzo interno all'azienda stessa ed possibile effettuare un numero ragionevole di copie di backup del Software, vincolate da queste condizioni:

  1. Il presente Software viene concesso in licenza solo congiuntamente (a) ai componenti Intel e (b) ai dispositivi virtuali ("emulati") destinati ad apparire come componenti Intel a un sistema operativo guest che viene eseguito nel contesto di una macchina virtuale. La licenza esclude qualsiasi altro utilizzo del Software compreso, ma non limitato a, l'uso con componenti non Intel.
  2. In base ai termini e alle condizioni del presente Contratto, Intel Corporation ("Intel") concede al Licenziatario una licenza non esclusiva, non trasferibile, nell'ambito dei copyright Intel, per utilizzare i Materiali.
  3. Non possibile copiare, modificare, affittare, vendere, distribuire o trasferire alcuna parte del Software tranne quanto previsto nel presente Contratto e il Licenziatario concorda nell'impedire copie non autorizzate del Software.
  4. Non permesso decodificare, decompilare o disassemblare il Software.
  5. Il Software pu comprendere componenti soggetti a termini diversi da quelli qui definiti, che sono specificati nei contratti di licenza ad essi relativi.

LICENZA PER UTENTE SINGOLO: possibile copiare il Software su un singolo computer per uso personale ed possibile effettuare una copia di backup del Software, vincolata da queste condizioni:

  1. Il presente Software viene concesso in licenza solo congiuntamente (a) ai componenti Intel e (b) ai dispositivi virtuali (“emulati”) destinati ad apparire come componenti Intel a un sistema operativo guest che viene eseguito nel contesto di una macchina virtuale. La licenza esclude qualsiasi altro utilizzo del Software compreso, ma non limitato a, l'uso con componenti non Intel.
  2. In base ai termini e alle condizioni del presente Contratto, Intel Corporation ("Intel") concede al Licenziatario una licenza non esclusiva, non trasferibile, nell'ambito dei copyright Intel, per utilizzare i Materiali.
  3. Non possibile copiare, modificare, affittare, vendere, distribuire o trasferire alcuna parte del Software tranne quanto previsto nel presente Contratto e il Licenziatario concorda nell'impedire copie non autorizzate del Software.
  4. Non permesso decodificare, decompilare o disassemblare il Software.
  5. Il Software pu comprendere componenti soggetti a termini diversi da quelli qui definiti, che sono specificati nei contratti di licenza ad essi relativi.

LICENZA OEM: possibile riprodurre e distribuire il Software solo come parte integrante e incorporata del prodotto dell'OEM oppure come aggiornamento autonomo di manutenzione del Software per gli utenti esistenti dell'OEM, con l'esclusione degli altri prodotti autonomi o come componente di una distribuzione del Software pi ampia, compresa, ma non limitata a, la distribuzione di un'immagine di installazione o di una macchina virtuale guest, e rispettando queste condizioni:

  1. Il presente Software viene concesso in licenza solo congiuntamente (a) ai componenti Intel e (b) ai dispositivi virtuali (“emulati”) destinati ad apparire come componenti Intel a un sistema operativo guest che viene eseguito nel contesto di una macchina virtuale. La licenza esclude qualsiasi altro utilizzo del Software compreso, ma non limitato a, l'uso con componenti non Intel.
  2. In base ai termini e alle condizioni del presente Contratto, Intel Corporation ("Intel") concede al Licenziatario una licenza non esclusiva, non trasferibile, nell'ambito dei copyright Intel, per utilizzare i Materiali.
  3. vietato copiare, modificare, noleggiare, vendere, distribuire o trasferire qualsiasi parte del Software, a eccezione di quanto specificato nel presente accordo, e l’utente acconsente a impedire di effettuare copie non autorizzate del Software.
  4. Non permesso decodificare, decompilare o disassemblare il Software.
  5. Il Software pu solo essere distribuito ai clienti conformemente a un contratto di licenza scritto. Tale contratto di licenza pu risultare un contratto “break-the-seal”. Per lo meno tale licenza deve salvaguardare i diritti di propriet di Intel sul Software.
  6. Il Software pu comprendere componenti soggetti a termini diversi da quelli qui definiti, che sono specificati nei contratti di licenza ad essi relativi.

LIMITAZIONI DELLA LICENZA. Il Licenziatario NON potr: (i) utilizzare o copiare i Materiali tranne per quanto previsto da questo Contratto; (ii) affittare o noleggiare i Materiali a terze parti; (iii) assegnare questo Contratto o trasferire i Materiali senza espresso consenso scritto da parte di Intel; (iv) modificare, adattare o tradurre i Materiali in tutto o in parte tranne per quanto previsto dal presente Contratto; (v) decodificare, decompilare o disassemblare i Materiali; (vi) cercare di modificare o manomettere la normale funzione di un gestore delle licenze che regola l'utilizzo dei Materiali; (vii) distribuire, concedere in sottolicenza o trasferire il Codice sorgente di alcun componente dei Materiali, dei Ridistribuibili e del Sorgente di esempio e loro derivati a terze parti tranne quanto previsto dal presente Contratto.

NESSUN ALTRO DIRITTO. Intel non concede al Licenziatario altri diritti o licenze, sia in modo esplicito che implicito, in riferimento alle informazioni proprietarie o di brevetto, ai copyright, ai mask work, ai marchi di fabbrica, ai segreti commerciali e ad altri diritti di propriet intellettuale che sono di propriet o controllati da Intel, eccetto nei casi espressamente previsti dal presente Contratto. Fatto salvo per quanto esplicitamente previsto nel presente documento, al Licenziatario non sono concesse altre licenze o diritti diretti, impliciti, indotti, derivanti da dichiarazioni verbali non corrette o di altra natura. In particolare, Intel non garantisce alcun diritto esplicito o implicito su brevetti, copyright, marchi di fabbrica o altri diritti relativi alla propriet intellettuale.

PROPRIET DEL SOFTWARE E COPYRIGHT. Il Software viene concesso in licenza e non venduto. La titolarit di tutte le copie del Software appartiene a Intel. Il Software protetto da copyright, dalle leggi degli Stati Uniti e di altre nazioni oltre che dalle disposizioni previste dai trattati internazionali. Il Licenziatario non pu rimuovere alcun avviso di copyright dal Software. Il Licenziatario accetta di impedire qualsiasi copia non autorizzata del Software. Intel pu apportare modifiche al Software, o agli elementi che a esso fanno riferimento, in qualsiasi momento e senza preavviso, ma non obbligata a supportare o aggiornare il Software. Il Licenziatario pu trasferire il Software soltanto se il destinatario dichiara di accettare di essere vincolato dai termini di questo Contratto e se il Licenziatario non conserva alcuna copia del Software.

TERMINI AGGIUNTIVI PER IL SOFTWARE DI PRE-RELEASE. Se il Software che si sta installando o utilizzando in base a questo Contratto una release preliminare o etichettato o altrimenti denominato versione “alfa“ o “beta“ del Software ("Software di pre-release"), si applicano i seguenti termini.

Nel caso in cui una disposizione di questa Sezione sia in conflitto con altri termini o condizioni di questo Contratto in relazione al Software di pre-release, questa Sezione avr la priorit su tali termini e condizioni, ma solo nei limiti necessari per risolvere il conflitto.
Il Licenziatario riconosce e accetta che il Software un Software di pre-release, non rappresenta il Software finale di Intel e potrebbe contenere errori e altri problemi che potrebbero causare la perdita di dati, il malfunzionamento del sistema o altri errori. Il Software di pre-release fornito "come tale" e Intel declina qualsiasi garanzia o responsabilit nei confronti del Licenziatario per gli eventuali danni causati dall'uso del Software di pre-release.
Il Licenziatario riconosce che Intel non ha promesso il futuro rilascio del Software di pre-release, non ha alcun obbligo espresso o implicito di rilasciare al Licenziatario il Software di pre-release e che Intel potrebbe introdurre un Software non compatibile con il Software di pre-release. Il Licenziatario riconosce che tutte le attivit di ricerca o sviluppo che esegue, relative al Software di pre-release o a qualsiasi prodotto che fa uso o associato con il Software pre-release, sono eseguite a proprio rischio.
Se Intel ha fornito al Licenziatario il Software di pre-release conformemente a un contratto scritto separato, l'uso del Software di pre-release regolamentato anche da tale contratto.

GARANZIA LIMITATA SUI SUPPORTI. Se il Software stato fornito da Intel su un supporto fisico, Intel garantisce che il supporto privo di difetti intrinseci e dei materiali per un periodo di novanta giorni dalla sua consegna da parte di Intel. Nel caso in cui siano rilevati difetti, restituire il supporto a Intel per ottenerne la sostituzione o per ricevere il Software in altro modo stabilito a discrezione di Intel.

ESCLUSIONE DI ALTRE GARANZIE. AD ECCEZIONE DI QUANTO PREVISTO IN PRECEDENZA, IL SOFTWARE CONCESSO IN LICENZA VIENE FORNITO 'COS COME ', SENZA ALCUNA GARANZIA ESPLICITA O IMPLICITA, COMPRESE LE GARANZIE DI COMMERCIABILIT, DI CONFORMIT ALLE NORME O IDONEIT A UN FINE PARTICOLARE. Intel non garantisce n si assume alcuna responsabilit riguardo l'accuratezza o la completezza delle informazioni, del testo, delle immagini, dei collegamenti o di altri elementi contenuti nel Software.

LIMITAZIONI DI RESPONSABILIT. INTEL O I SUOI FORNITORI NON SARANNO IN ALCUN CASO RESPONSABILI PER EVENTUALI DANNI DI QUALSIASI NATURA (COMPRESI, SENZA LIMITAZIONE, LE PERDITE DI PROFITTO, L'INTERRUZIONE DELL'ATTIVIT COMMERCIALE O LA PERDITA DI DATI) DERIVANTI DALL'USO O DALL'IMPOSSIBILIT DI USARE IL SOFTWARE, ANCHE NEL CASO IN CUI INTEL SIA STATA INFORMATA DELLA POSSIBILIT DI TALI DANNI. ALCUNE GIURISDIZIONI PROIBISCONO L'ESCLUSIONE O LA LIMITAZIONE DELLA RESPONSABILIT RELATIVAMENTE ALLE GARANZIE IMPLICITE O AI DANNI CONSEQUENZIALI E ACCIDENTALI; DI CONSEGUENZA, LA SUDDETTA LIMITAZIONE POTREBBE NON ESSERE APPLICABILE A TUTTI I CASI. POTREBBERO INOLTRE ESSERE PREVISTI ALTRI DIRITTI LEGALI CHE VARIANO DA GIURISDIZIONE A GIURISDIZIONE. Nel caso in cui il Licenziatario usi il Software con un dispositivo virtuale (“emulato”) destinato ad apparire come un componente Intel, il Licenziatario riconosce che Intel non n l'autore n il creatore del dispositivo virtuale (“emulato”). Il Licenziatario riconosce e accetta che Intel non fornisce alcuna garanzia relativamente alla correttezza del funzionamento del Software quando usato con un dispositivo virtuale (“emulato”), che Intel non ha progettato il Software per il funzionamento con il dispositivo virtuale (“emulato”) e che il Software potrebbe non funzionare correttamente con il dispositivo virtuale (“emulato”). Il Licenziatario accetta di assumersi il rischio che il Software potrebbe non funzionare correttamente con il dispositivo virtuale (“emulato”). Il Licenziatario accetta di rimborsare e manlevare Intel e i suoi funzionari, le sue societ collegate o controllate, di qualsiasi rivendicazione, costo, danno, spesa, spesa legale derivanti, direttamente o indirettamente, da qualsiasi rivendicazione di responsabilit del prodotto, lesione personale o decesso associati all'uso del Software con il dispositivo virtuale (“emulato”), anche se tale rivendicazione sostiene che Intel abbia agito in modo negligente nella progettazione o costruzione del Software.

USO NON AUTORIZZATO. IL SOFTWARE NON PROGETTATO, PREVISTO O AUTORIZZATO PER ESSERE UTILIZZATO IN QUALSIASI SISTEMA O APPLICAZIONE IN CUI IL FALLIMENTO DEL SOFTWARE POTREBBE CREARE UNA SITUAZIONE DI LESIONE PERSONALE O DECESSO (AD ESEMPIO, SISTEMI MEDICALI, SALVAVITA O DI SOPRAVVIVENZA). Se il Licenziatario utilizza il Software per qualsiasi uso non previsto o non autorizzato, il Licenziatario dovr rimborsare e manlevare Intel e i suoi funzionari, dipendenti, direttori, filiali, rappresentanti, affiliate e agenti nei confronti di qualsiasi rivendicazione, costo, danno, spesa, spesa legale e spese di vario tipo derivanti, direttamente o indirettamente, da qualsiasi rivendicazione di responsabilit del prodotto, lesione personale o decesso associati a tale uso non previsto o non autorizzato, anche se tale rivendicazione ritiene Intel negligente per quanto riguarda la progettazione o la costruzione della parte.

RESCISSIONE DI QUESTO CONTRATTO. Intel pu rescindere il presente Contratto in qualsiasi momento, nel caso l'utente ne violi i termini. In seguito alla rescissione del contratto, il Licenziatario deve immediatamente distruggere tutte le copie del Software o restituirle a Intel.

LEGGI APPLICABILI. Le rivendicazioni derivanti dal, o relative al, presente Contratto saranno regolamentate dalle leggi vigenti nello Stato della California, senza considerazione dei principi di conflitto della legge. Il Licenziatario accetta che la Convenzione delle Nazioni Unite sui Contratti per la vendita di beni non si applica al presente Contratto. Il Licenziatario non pu esportare il Software trasgredendo le leggi e i regolamenti sulle esportazioni attualmente in vigore. Intel non vincolata da alcun altro contratto che non sia per iscritto e firmato da un rappresentante autorizzato di Intel.

DIRITTI LIMITATI DEL GOVERNO. Il Software e la documentazione forniti sono stati sviluppati privatamente e hanno “DIRITTI LIMITATI”. L'uso, la duplicazione o la divulgazione da parte del Governo sono soggetti alle limitazioni delle norme FAR 52.227-14 e DFAR 252.227-7013 et seq. o successive. L’uso di questo prodotto da parte del Governo equivale a riconoscere i diritti di propriet di Intel sul Software. Il contraente o il produttore Intel.

LINGUA; TRADUZIONI. Qualora la versione in lingua inglese del presente Contratto venisse fornita insieme a una versione tradotta in un'altra lingua, a titolo di riferimento, far fede unicamente la versione in lingua inglese.

Ultima modifica 15/5/11 22:56 Revisione

DOCS/QUICK/ITA/note.gif0000755000000000000000000000073211651733270011433 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/ITA/qi_ita.htm0000755000000000000000000001413411546611560011760 0ustar Guida rapida di installazione delle schede di rete Intel(R)

Installazione della scheda di rete Intel®

Installazione della scheda di rete Intel PCI, PCI-X o PCI Express*

  1. Spegnere il computer e disinserire il cavo di alimentazione.
  2. Rimuovere il coperchio del computer e la protezione dello slot della scheda.
  3. Posizionare saldamente il connettore della scheda nello slot fino a quando non inserito completamente. Fissare la staffa di supporto allo chassis.
  4. Chiudere il coperchio del computer. Inserire il cavo di alimentazione.

NOTA: alcune schede di rete Intel Gigabit per server e per sistemi desktop usano il bus PCI Express. Si pu utilizzare uno slot pi lungo del connettore della scheda di rete senza che questo provochi alcun danno, mentre non bisogna tentare di installarla in uno slot pi corto del connettore PCI Express.

Collegare il cavo di rete

Schede di rete Intel® PRO/100 e schede di rete Gigabit in rame: collegare il cavo o i cavi di rete alla scheda utilizzando un cavo di rete Ethernet a doppini intrecciati (TPE) di categoria 3, 4 o 5 per reti a 10 Mbps. Per le reti a 100 o 1000 Mbps e per le reti private utilizzare un cavo di categoria 5 (4 doppini).

Schede di rete Intel® Gigabit in fibra con connettore SC: Rimuovere e riporre la copertura del connettore a fibre ottiche. Inserire un connettore a fibre ottiche di tipo SC duplex 1000Base-SX nelle porte TX/RX della staffa di supporto della scheda di rete.

Schede di rete Intel® Gigabit in fibra con connettore LC: Rimuovere e riporre la copertura del connettore a fibre ottiche. Inserire un connettore LC nella scheda di rete, con il cavo corretto per il tipo di scheda (1000BASE-SX o 1000BASE-LX). possibile usare cavi per convertire altri tipi di connettori (come SC) se tali cavi soddisfano le specifiche ottiche della scheda, lunghezza inclusa.

Avviare il computer e seguire le istruzioni per l'installazione del driver riportate di seguito.

Installazione dei driver

Sistemi operativi Windows

Si noti che necessario disporre dei diritti di amministratore per poter installare i driver.

  1. La scheda viene rilevata e Windows installa un driver residente di Windows o avvia Installazione guidata nuovo hardware .
  2. Se si avvia Installazione guidata nuovo hardware, selezionare Annulla.
  3. Inserire il CD di Intel. Il programma ad esecuzione automatica Connessioni di rete Intel si avvia. Fare clic sul pulsante Installa i driver e il software .

Linux*.

Per generare un package binario RPM* di questo driver, eseguire 'rpmbuild -tb <nomefile.tar.gz>'. Sostituire <nomefile.tar.gz> con il nome file specifico del driver.

NOTE:

  • Affinch il processo di build funzioni correttamente, il kernel al momento in esecuzione DEVE corrispondere alla versione dei sorgenti del kernel installati. Se stato appena ricompilato il kernel riavviare il sistema.

  • Le funzionalit RPM sono state testate soltanto con le distribuzioni Red Hat.

  • Per le schede di rete Intel PRO/100, usare e100 come nome del driver.

  1. Spostare il file tar del driver di base in una directory di propria scelta. Ad esempio, usare '/home/nomeutente/e1000' o '/usr/local/src/e1000'.

  2. Scompattare l'archivio, in cui <x.x.x> il numero di versione del file tar del driver:
    tar zxf e1000-<x.x.x>.tar.gz
  3. Passare alla directory src del driver, dove <x.x.x> il numero di versione del file tar del driver:
    cd e1000-<x.x.x>/src/
  4. Compilare il modulo del driver:
    make install
    Il file binario verr installato come:
    /lib/modules/<versione_kernel>/kernel/drivers/net/e1000.o

    Le posizioni di installazione elencate pi indietro sono le posizioni predefinite. Potrebbero non essere corrette per alcune distribuzioni di Linux.

  5. Installare il modulo:
    insmod e1000 <parametro>=<valore>
  6. Assegnare un indirizzo IP all'interfaccia inserendo l'istruzione seguente, dove <x> il numero di interfaccia:
    ifconfig eth<x> <indirizzo_IP>
  7. Verificare che l'interfaccia funzioni. Immettere l'istruzione seguente, dove <indirizzo_IP> l'indirizzo IP di un altro computer nella stessa sottorete in cui si trova l'interfaccia che si sta sottoponendo a test:
    ping <indirizzo_IP>

Altri sistemi operativi

Per installare altri driver, vedere la Guida dell'utente inclusa nel CD della scheda o visitare il sito Web del supporto: http://www.intel.com/p/it_IT/support/.

*Informazioni legali

Ultima modifica: 10/11/07 3:48p Revisione 14

DOCS/QUICK/ITA/style.css0000755000000000000000000000450511651733270011653 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/ITA/warranty.htm0000755000000000000000000001471011546611560012361 0ustar Garanzia hardware limitata

Garanzia hardware limitata

Intel garantisce al proprietario originario che la scheda di rete contenuta nella confezione non contiene difetti n dei materiali n di lavorazione. La presente garanzia non copre i danni del prodotto causati dall'installazione del prodotto stesso.

LA SUDDETTA GARANZIA SOSTITUISCE QUALSIASI ALTRA GARANZIA, ESPRESSA, IMPLICITA O OBBLIGATORIA, COMPRESA, MA NON LIMITATA A, QUALSIASI GARANZIA DI RISPETTO DELLA PROPRIET INTELLETTUALE, DI COMMERCIABILIT, DI IDONEIT AD UNO SCOPO PARTICOLARE, O QUALSIASI GARANZIA DERIVATA DA PROPOSTE, SPECIFICHE, CAMPIONI.

La presente garanzia non copre la sostituzione di schede di rete danneggiate in caso di abuso, incidente, uso improprio, negligenza, alterazione, riparazione, calamit, installazione errata o collaudo errato. Se la scheda di rete viene trovata altrimenti difettosa, Intel, a propria discrezione, la sostituir o riparer gratuitamente, eccetto che nei casi illustrati di seguito, purch la scheda di rete sia consegnata unitamente al codice di autorizzazione per la restituzione del materiale (RMA) (vedere pi avanti) all'azienda presso cui la si acquistata o a Intel, con copia della ricevuta di acquisto (se la scheda non stata registrata) e una descrizione del difetto riscontrato. In caso di spedizione del prodotto, l'utente si assume il rischio di danneggiamento o perdita durante il trasporto. Occorre usare il contenitore originale (o uno equivalente) e pagare le spese di spedizione.

Intel pu sostituire o riparare la scheda di rete con un prodotto o parti nuove o rigenerate, nel qual caso la scheda di rete o le parti restituite diventano propriet di Intel. Le schede di rete riparate o sostituite saranno restituite, a discrezione di Intel, con un livello di revisione pari o superiore al prodotto originale. Intel si riserva il diritto di sostituire la scheda di rete difettosa con un altro modello equivalente.

Restituzione di un prodotto difettoso

Dall'America del Nord

Prima di restituire una scheda di rete, necessario contattare il Servizio di assistenza clienti al numero +1 916-377-7000 e richiedere un codice di restituzione prodotto (RMA).

Se il Servizio di assistenza clienti determina che la scheda di rete effettivamente difettosa, chieder al reparto responsabile della restituzione dei prodotti di emettere un codice RMA da apporre sulla confezione del prodotto da restituire. La Intel non accetter prodotti sprovvisti del codice RMA sulla confezione.

Dagli altri paesi

Restituire la scheda di rete al rivenditore presso il quale stata acquistata per richiedere il rimborso o la sostituzione.

Garanzia di rimborso del prezzo pagato per la scheda di rete (valida solo per i clienti del Nord America)

Intel desidera che i suoi clienti siano pienamente soddisfatti della scheda di rete Intel che hanno acquistato. Pertanto, permette loro di restituire la scheda acquistata presso il rivenditore e di richiedere il rimborso dell'intero prezzo pagato entro novanta (90) giorni dalla data di acquisto. I rivenditori e i distributori che accettano i prodotti restituiti e rimborsano i clienti possono a loro volta restituire le schede di rete Intel al fornitore dal quale le hanno acquistate. Intel garantisce la possibilit di restituire il prodotto e di richiedere il rimborso dell'intero prezzo pagato anche ai clienti che hanno acquistato le loro schede direttamente dalla Intel.

Limitazione della responsabilit e rimedi

L'UNICA RESPONSABILIT DI INTEL DEFINITA DALLA PRESENTE GARANZIA LIMITATA AI DANNI DIRETTI E MISURABILI IN MODO OGGETTIVO. IN NESSUN CASO INTEL SAR CONSIDERATA RESPONSABILE PER DANNI INDIRETTI O IPOTETICI (INCLUSI, MA NON LIMITATI A, I DANNI PRECEDENTI, DERIVATI, INCIDENTALI E SPECIALI) INCLUSI, MA NON LIMITATI A, LA VIOLAZIONE DI PROPRIET INTELLETTUALE, I COSTI DI RIACQUISTO, LA PERDITA D'USO, L'INTERRUZIONE DELLE ATTIVIT COMMERCIALI, LA PERDITA DI AVVIAMENTO, LA PERDITA DI PROFITTI, INDIPENDENTEMENTE DAL FATTO CHE TALI DANNI SI VERIFICHINO SOTTO CONTRATTO, DA NEGLIGENZA, PER TORTO O SIANO COPERTI DA GARANZIA, E INDIPENDENTEMENTE DA EVENTUALI NOTIFICHE FATTE PERVENIRE ANTICIPATAMENTE A INTEL RELATIVAMENTE ALLA POSSIBILIT DEL VERIFICARSI DI TALI DANNI. NONOSTANTE QUANTO SOPRA RIPORTATO, LA RESPONSABILIT TOTALE DI INTEL PER TUTTI I RECLAMI REGOLATI IN BASE AL PRESENTE CONTRATTO NON PU SUPERARE IL PREZZO PAGATO PER IL PRODOTTO. TALI LIMITAZIONI DELLE RESPONSABILIT POTENZIALI HANNO RAPPRESENTATO UN ELEMENTO ESSENZIALE PER STABILIRE IL PREZZO DEL PRODOTTO. LA INTEL NON SI ASSUME N AUTORIZZA ALCUNO AD ASSUMERSI IN SUA VECE QUALUNQUE ALTRA RESPONSABILIT.

Alcuni stati non consentono l'esclusione o la limitazione dei danni incidentali o consequenziali, pertanto le suddette limitazioni potrebbero non essere applicabili all'utente.

Applicazioni di controllo critiche: la Intel disconosce specificamente la responsabilit per l'uso del prodotto hardware con applicazioni di comando fondamentali (compresi, solo a titolo di esempio, sistemi di comando per l'assistenza sanitaria, sistemi di comando per energia nucleare, o sistemi di comando per il traffico aereo o terrestre) da parte del Licenziatario o dei Sublicenziatari, e tale utilizzo totalmente a rischio e pericolo dell'utente. Il licenziatario concorda di sostenere, risarcire e ritenere Intel non responsabile di qualsivoglia reclamo derivato dall'uso del prodotto hardware in tali applicazioni da parte del Licenziatario o dei Sublicenziatari.

Software: il software fornito con la scheda di rete non coperto dalla garanzia hardware descritta in precedenza. Per informazioni sulle eventuali garanzie software, consultare il Contratto di licenza del software fornito con la scheda di rete.

Ultima modifica: 07/23/02 10:42a Revisione 6

DOCS/QUICK/JPN0000755000000000000000000000000011761422164007724 5ustar DOCS/QUICK/JPN/legaldis.htm0000755000000000000000000000200411725606054012302 0ustar @

쌠і@

Copyright (C) 2002 - 2012 Intel Corporation.All rights reserved.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Intel Corporation ͖{ɋLڂĂě܂͋LژRɂ‚āAؐӔC𕉂܂B܂A{̋LړeXV`ؕ܂B

IntelAItanium PentiuḿAčт̑̍ɂ Intel Corporation ̏WłB

* ̑̐i܂̓uh͊eL҂ɋAĂꍇ܂B

ۏ؂̏

\tgEFAECZX

 

ŏIXV 2011N125 10:21pm ԍ DOCS/QUICK/JPN/license.htm0000755000000000000000000003402011730046352012136 0ustar \tgEFAECZX

Ce \tgEFAgp_

dv - Rs[ACXg[A܂͎gp̑Oɂǂ݂B

ȉ̏𒍈Ӑ[ǂ݂ɂȂ܂ŁA{gp_ (u_v) ̉ɒ񋟂{\tgEFAъ֘A (ȉÂ u\tgEFAv Ƃ܂) Rs[ACXg[A܂͎gpȂłB

\tgEFARs[ACXg[A܂͎gpƁAql͖{_̏ɍS邱ƂɓӂꂽƂɂȂ܂B{_̏ɓӂȂꍇ́A\tgEFARs[ACXg[܂͎gpȂłB

gp_F

ӎF

  • lbg[N܂̓VXeǗ҂ɂ́Aȉ uTCggp_v Y܂B
  • Gh[U[ɂ́AuVO[U[gp_v Y܂B
  • OEM (Original Equipment Manufacturer) ɂ́AuOEM gp_vY܂B

TCggp_F qĺA\tgEFAql̑gDgp邽߂ɂ̑gD̃Rs[^[Ƀ\tgEFARs[邱ƂłA\tgEFÃobNAbvƂđÓȐ̃Rs[쐬邱Ƃł܂BAȉ̏ɏ]ƂƂ܂B

  1. ̃\tgEFÁA(a) IȃCẽR|[lgi (b) z}ṼReLXgŎsĂQXgEIy[eBOEVXeɃCẽR|[lgiƂČ悤ɐ݌vꂽz (uG~[gꂽv) foCXƂ̑gݍ킹ɂgpɂ̂݁Agp܂B\tgEFȂ̂gp,CeȊÕR|[lgił̎gp܂݂Ɍ肳ꂸA̎gp_̉ɃCZXĂ܂B
  2. {_񏑂ׂ̂Ă̏Ə̉ɁAIntel Corporation (uCev) ͂qlɖ{igp邽߂̔rIAn֎~̒쌠CZX‚܂B
  3. {_񏑂œɋK肷ꍇA\tgEFÂȂ镔AAύXAݗ^ApAzzAn邱Ƃ͋ւĂ܂B܂AqĺA\tgEFA̖fh~邱Ƃɍӂ̂Ƃ܂B
  4. \tgEFAo[X GWjAAtRpCAtAZu邱Ƃւ܂B
  5. \tgEFÁAɋLڂȊȌŒ񋟂镔܂ޏꍇȀꍇ͂̕ɕt̎gp_񂪓Kp܂B

VO[U[gp_F qĺA\tgEFA 1 ̃Rs[^[ɂqľlgpړIŃRs[邱ƂłA\tgEFÃobNAbvE Rs[ 1 쐬ł܂B̍ہAȉ̏Kp܂B

  1. ̃\tgEFÁA(a) IȃCẽR|[lgi (b) z}ṼReLXgŎsĂQXgEIy[eBOEVXeɃCẽR|[lgiƂČ悤ɐ݌vꂽz (uG~[gꂽv) foCXƂ̑gݍ킹ɂgpɂ̂݁Agp܂B\tgEFȂ̂gp,CeȊÕR|[lgił̎gp܂݂Ɍ肳ꂸA̎gp_̉ɃCZXĂ܂B
  2. {_񏑂ׂ̂Ă̏Ə̉ɁAIntel Corporation (uCev) ͂qlɖ{igp邽߂̔rIAn֎~̒쌠CZX‚܂B
  3. {_񏑂œɋK肷ꍇA\tgEFÂȂ镔AAύXAݗ^ApAzzAn邱Ƃ͋ւĂ܂B܂AqĺA\tgEFA̖fh~邱Ƃɍӂ̂Ƃ܂B
  4. \tgEFAo[X GWjAAtRpCAtAZu邱Ƃւ܂B
  5. \tgEFÁAɋLڂȊȌŒ񋟂镔܂ޏꍇȀꍇ͂̕ɕt̎gp_񂪓Kp܂B

OEM gp_F qĺAql̐iɓꂽA܂͑gݍ܂ꂽƂāA邢͂ql̐i̊̃Gh[U[ɑ΂X^hÃ\tgEFAEeiXEAbvf[g (ȊÔׂẴX^hAi͏O) A܂̓CXg[EC[W܂̓QXgz}ṼC[W̔zz܂ނɌ肳Ȃ傫ȃ\tgEFA̔zz 1 ‚̃R|[lgƂĂ̂݁A\tgEFA𕡐єzz邱Ƃł܂BAȉ̏ɏ]̂Ƃ܂B

  1. ̃\tgEFÁA(a) IȃCẽR|[lgi (b) z}ṼReLXgŎsĂQXgEIy[eBOEVXeɃCẽR|[lgiƂČ悤ɐ݌vꂽz (uG~[gꂽv) foCXƂ̑gݍ킹ɂgpɂ̂݁Agp܂B\tgEFȂ̂gp,CeȊÕR|[lgił̎gp܂݂Ɍ肳ꂸA̎gp_̉ɃCZXĂ܂B
  2. {_񏑂ׂ̂Ă̏Ə̉ɁAIntel Corporation (uCev) ͂qlɖ{igp邽߂̔rIAn֎~̒쌠CZX‚܂B
  3. {_񏑂œɋK肷ꍇA\tgEFÂȂ镔AAύXAݗ^ApAzzAn邱Ƃ͋ւĂ܂B܂AqĺA\tgEFA̖fh~邱Ƃɍӂ̂Ƃ܂B
  4. \tgEFAo[X GWjAAtRpCAtAZu邱Ƃւ܂B
  5. \tgEFAqľڋqɔzzۂɂ́Aʂɂ郉CZXgp_񏑂ɏ]̂Ƃ܂B̂悤Ȏgp_́AJ_ _񂪐A"break-the-seal" `̎gp_łꍇ܂BŒÂ悤ȃCZX́A\tgEFAɑ΂CȅLی삵܂B
  6. \tgEFÁAɋLڂȊȌŒ񋟂镔܂ޏꍇȀꍇ͂̕ɕt̎gp_񂪓Kp܂B

CZX̐B ȉ̂Ƃ͍s܂B(i) {_Œ񋟂ꂽꍇA{i̎gp܂͕B (ii) ȂO҂ɖ{iݗ^܂̓[X邱Ƃ͂ł܂B (iii) ʂɂCe̖Iȋ‚Ȃɖ{_񏑂蓖Ă{in邱Ƃ͂ł܂B (iv) {_ŋ‚ꂽꍇA{ȋŜ܂͈ꕔύXAA܂͂ق₭邱Ƃ͂ł܂B (v) {ĩo[XGWjAAtRpCAtAZu邱Ƃ͂ł܂B (vi) {i̎gpK郉CZXE}l[W[̐@\̕ύX܂͉݂邱Ƃ͂ł܂B (vii) {_ŋ‚ĂꍇA{îȂR|[lg̃\[XR[h`AĔzz”\ȃ\[XAуTv\[Xт̔hȂO҂ɔzzATuCZXA܂͏n邱Ƃ͂ł܂B

ׂ̑̂Ă̌̏OB {_񏑂ɖIɋK肳Ă̂ACeЂ͂qlɑ΂ACeЂLуRg[铖ГƎ̏A쌠A}XN [NAWAƖ̋@Ȃ̒mILɊւAIAÎI킸AȂ錠⃉CZXt^̂ł͂܂B{_񏑂ɖĂꍇAځAَIAUIA֔Ȃ킸ACZX܂͌n邱Ƃ͈؂܂BɁACéACe̓A쌠AWȂ̒mILɊւAI܂َ͖IȌ؏n邱Ƃ͂܂B

\tgEFȀLђ쌠B {\tgEFA̓CZXĂApꂽ̂ł͂܂B\tgEFAтׂ̂ẴRs[Ɋւ؂̏ĹACeɋA܂B\tgEFA͒쌠o^ĂAčƏO̖@Aэۏɂĕی삳Ă܂B\tgtgEFA̒쌠̍m𖕏邱Ƃ͂ł܂BqĺA\tgEFA̖fh~邱Ƃɍӂ̂Ƃ܂BCeł́Aʒm邱ƂȂ‚ł\tgEFA܂͂ɋLڂĂ鍀ڂɕύX邱ƂłA\tgEFAT|[g܂̓Abvf[g`𕉂܂B󂯎l{_̊ɊSɏ邱ƂɓӂA󂯓nl\tgEFÃRs[ێȂꍇɂ̂݃\tgEFAn邱Ƃł܂B

v[XŃ\tgEFAp̒ljB {_̉ɃCXg[܂͎gp\tgEFAƃ[XÕv[XłłꍇA܂̓\tgEFÁuAt@v܂́ux[^vłƂĕ\ꂽꍇɂ́ȀKp܂B

v[XŃ\tgEFAɊւāÃZNV̂Ȃ{_̑̂܂͏ƖꍇɂẮÃZNV̏܂͏D悳܂ÂɕKvȔ͈݂͂̂Ɍ܂B
qĺA\tgEFAv[Xł̃\tgEFAłACe̍ŏI\tgEFAł͂ȂAf[^̑AVXeQA܂͑̃G[N”\̂G[ё̖܂މ”\邱Ƃ𗝉ďF܂Bv[XŃ\tgEFÁû܂܁v񋟂ACéAv[XŃ\tgEFA̎gp琶邢Ȃ鑹Qɑ΂āAqlւ̕ۏ؂؍s킸AӔCؕ܂B
qĺACev[XŃ\tgEFAナ[X񑩂ACéAql΂āAv[XŃ\tgEFA[X閾I܂َ͖Iȋ`ǂ킸ACe̓v[XŃ\tgEFAƌ݊̂\tgEFA𓱓Ȃ”\邱ƂF܂BqĺAv[XŃ\tgEFA܂̓v[XŃ\tgEFAgpA܂͊֘A邢Ȃ鐻iɊւĂqlsȂ郊T[`܂͊Jׂ͂Ăql̐ӔCɂčsƂF܂B
Ceʓȑʂɂ鍇ӂɏ]ĂqlɃv[Xł̃\tgEFA񋟂ꍇAqlɂv[Xł̃\tgEFA̎gṕA̍ӏɂĂǗ܂B

}̂̌ۏ؁B \tgEFACeɂ蕨IȔ}̏ŔzzꂽꍇACeł͔zB 90 ԁA}̂ɍގエѕIȕsȂƂۏ؂܂B̂悤Ȍׂ‚ꍇA̔}̂CeɕԑĂB}̂̌܂̓CeI@Ń\tgEFA͂܂B

̑̕ۏ؂̏OB qɋK肷ۏ؂A\tgEFÁû܂܁v񋟂܂Bi̕ۏ؁A쌠̐NQȂƁAړIK̕ۏ؂܂߁Ȃ؂̕ۏ؂ɂ͖Eَ킸܂B Ceł́A\tgEFAɊ܂܂AeLXgAOtBbNANȂ̍ڂɂ‚āA̐m⊮Sɂ‚Ĉؕۏ؂AӔC𕉂܂B

ƐӎB ǂ̂悤ȏꍇɂĂACe܂͂̔[Ǝ҂́AQ̉”\wEʍOɂƂĂA\tgEFA̎gp܂͂ꂪgpłȂƂɂĐȂ鑹Q (⎸vɋN鑹QAƖ̒fȂ܂ނɌ̂ł͂Ȃ) ɑ΂ĂAؐӔC𕉂܂B܂͒nɂẮAَ̕ۏ؁AʓI܂͋IȑQ̏O܂͐ւĂꍇ܂B̏ꍇAL͓̐Kp܂B܂͒nɂ肨ql̖͑@IȌLꍇ܂B CẽR|[lgiƂČ悤ɐ݌vꂽz (uG~[gꂽv) foCXƂ̑gݍ킹ɂ\tgEFAgpꍇAqĺACez (uG~[gꂽv) foCX̍҂܂͍쐬҂̂łȂƂF܂BqĺA\tgEFAz (uG~[gꂽv) foCXƂ̑gݍ킹ɂgpƂɂ́ACe̓\tgEFA̐ɂ‚ĐACe̓\tgEFAz (uG~[gꂽv) foCXƂ̑gݍ킹ɂ葀삷邽߂ɐ݌vĂ炸Az (uG~[gꂽv) foCXƂ̑gݍ킹ŎgpƂɂ̓\tgEFA@\Ȃ”\邱Ƃ𗝉AF܂BqĺAz (uG~[gꂽv) foCXƂ̑gݍ킹ŎgpꍇA\tgEFA@\Ȃ”\댯邱Ƃz肷邱Ƃɓӂ܂BqĺAz (uG~[gꂽv) foCXƂ̑gݍ킹Ń\tgEFAgpꍇɂāAgpɊ֘Ai̐ӔCAlgQASɊւ锅ɂāAƂCeɐ݌v܂͐ɂߎƎ咣ꍇłAɒړI܂͊ԐړIɋN锅AAQAp̈؁AёÓȊzٌ̕mp⏞ACeƂ̖AqЁA֘AЂɉ瑹Q^ȂƂɓӂ̂Ƃ܂B

F‚ȂgpB {\tgEFÁA\tgEFA̕sl̂ւ̕܂͎SN”\̂邢Ȃ^CṽVXeAvP[V(Ƃ΁AÃVXeAێuA~uȂ) ɂĂ̎gp̂߂ɐ݌vAӐ}A܂͔F‚Ă܂Bql̓\tgEFAȂӐ}Ȃ܂͋‚ȂprɎgpꍇAgpɊ֘Ai̐ӔCAlgQASɊւ锅ɂāAƂCeɐ݌v܂͐ɂߎƎ咣ꍇłAɒړI܂͊ԐړIɋN锅AAQAp̈؁AёÓȊzٌ̕mp⏞ACeƂ̖AqЁA֘AЂɉ瑹Q^ȂƂɓӂ̂Ƃ܂B

\'96\'7b_̏IB ql{_̏ɈᔽꍇACe͒ɖ{_񂷂邱Ƃł܂B{_񂪏IꍇAql͒Ƀ\tgEFA邩AׂẴRs[Ceɕԋp̂Ƃ܂B

@B {_񂩂琶鐿ɂ́AڐG@̌ɔ邩ǂɊ֌WȂAAJÕJtHjAB̖@Kp܂BqĺA{_ɂ͍ەi_Ɋւ鍑Ȁ͓KpȂƂɓӂ܂BqĺAYAoɊւ@yыKɔă\tgEFAAo邱Ƃ͂ł܂BCéACě̂\҂̏̂鏑ʂɂȂ΁Ȃ̌_̋`𕉂܂B

{̌̐B ꂽ\tgEFAƃhLg͎ɂJAu̐vt܂B {ɂgpAAJɂ‚ẮAFAR52.227-14ADFAR252.227-7013 et seq. ܂͂̌pKɋK肳Ă鐧܂B{ɂ{i̎gṕA\tgEFAɂCȅL̏FƂȂ܂B_҂܂͐҂̓CełB

A|F ̎gp_̉płɁAւ̖|łtĂꍇA̖|ł͂ql̕֋X}Ē񋟂Ă邾̂̂łApł@I͂D悳܂B

ŏIXV | 2011N515 10:56pm | ԍ

DOCS/QUICK/JPN/note.gif0000755000000000000000000000073211651733270011445 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/JPN/qi_jpn.htm0000755000000000000000000001401611623463200011773 0ustar Ce(R) lbg[NEA_v^[ NCbNECXg[EKCh

Ce® lbg[NEA_v^[̃CXg[

Ce PCIAPCI-XA܂ PCI Express* A_v^[̃CXg[

  1. Rs[^[̓d؂AdR[hRZg甲܂B
  2. Rs[^[̃Jo[OAA_v^[ɊYXbgA_v^[EXbgJo[O܂B
  3. A_v^[̃GbW RlN^[AXbgɊSɂ͂܂܂ō݂܂BuPbgV[VɂƎt܂B
  4. Rs[^[̃Jo[t܂BdR[hRZgɍ݂܂B

F Ce MKrbgET[o[уfXNgbvEA_v^[̂‚́A PCI Express oXgp܂BA_v^[̃RlN^[XbggpĂ܂܂񂪁APCI Express RlN^[ZXbgɂ͎tȂłB

lbg[NEP[u̐ڑ

Ce® PRO/100 A_v^[уMKrbgA_v^[F 10 Mbps lbg[Nł́AJeS[ 3A4A܂ 5 ̃cCXgEyAEC[Tlbg (TPE) P[ugpāAlbg[NEP[u܂̓P[uA_v^[ɐڑ܂B100 ܂1000 Mbps lbg[Nуz[ lbg[Nɂ́AJeS[5 (4 yA) P[ugp܂B

Ce® MKrbgEt@Co[EA_v^[ (SC RlN^[ڑ)F t@Co RlN^[̃Jo[Oĕۊǂ܂B1000Base-SX dʐM^ SC t@Co[ RlN^[ A_v^[ uPbg TX/RX |[gɍ݂܂B

Ce® MKrbgEt@Co[EA_v^[ (LC RlN^[ڑ)F t@Co[ RlN^[̃Jo[Oĕۊǂ܂BA_v^[̃^Cv (1000BASE-SX ܂ 1000BASE-LX) ɍP[ugpāALC RlN^[A_v^[ɍ݂܂B̐܂߁At@Co[̎dlɃP[uꍇ́ASC ̂ق̃^CṽRlN^[ɕϊP[ugp邱Ƃł܂B

Rs[^[NAhCo[ECXg[菇ɏ]܂B

hCo[̃CXg[

Windows Iy[eBOEVXe

hCo[CXg[ɂ́AIy[eBOEVXeɑ΂ǗҌKvłB

  1. A_v^[oAWindows ɂ Windows 풓hCo[CXg[邩AVn[hEFǍo EBU[hN܂B
  2. Vn[hEFǍoEBU[hJnꂽꍇ́A[LZ] {^܂B
  3. Ce CD }܂BIntel Network Connections I[g vOIɊJn܂B[hCo[ƃ\tgEFÃCXg[ ] {^NbN܂B

Linux*

̃hCo[̃oCi[ RPM* pbP[W쐬ɂ́Aurpmbuild -tb <filename.tar.gz>vs܂ B<filename.tar.gz> ́̕AhCo[̃t@Cɒu܂ B

F

  • rh@\ɂ́Aݎs̃J[l̃o[WƃCXg[ꂽJ[l \[X̐ݒ肪vKv܂BJ[lăRpC΂̏ꍇ́AVXeċNĂB

  • RPM @\ Red Hat ł̂݃eXgĂ܂B

  • Ce PRO/100 A_v^[ł́AhCo[Ɂue100vgp܂B

  1. Cӂ̃fBNg[Ƀx[X hCo[ tar t@Cړ܂BƂ΁A'/home/username/e1000' ܂ '/usr/local/src/e1000' Ȃǂgpł܂B

  2. ̃R}hgpāAA[JC𓀂܂B<x.x.x> ̕ɂ̓hCu tar t@C̃o[Wԍ܂B
    tar zxf e1000-<x.x.x>.tar.gz
  3. hCo src fBNg[ɕύX܂Bi<x.x.x> ́AhCo[ tar ̃o[WԍłBj
    cd e1000-<x.x.x>/src/
  4. hCo[ W[RpC܂B
    make install
    oCi[͎̂悤ɃCXg[܂B
    /lib/modules/<J[l o[W>/kernel/drivers/net/e1000.o

    Ɏ̂́AftHg̃CXg[ꏊłBgpĂ Linux ɂẮÃCXg[ꏊgpȂꍇ܂B

  5. W[CXg[܂B
    insmod e1000 <p[^>=<l>
  6. ȉ̂悤ɓ͂ăC^[tFCX IP AhX蓖Ă܂Bi<x> ̓C^[tFCXԍłBj
    ifconfig eth<x> <IP AhX>
  7. C^[tFCX@\邱ƂmF܂Bȉ̂悤ɓ͂܂Bi<IP AhX> ̓eXgC^[tFCXƓ̃Tulbgɂʂ̃Rs[^[ IP AhXłBj
    ping <IP AhX>

̑̃Iy[eBOEVXe

̃hCo[CXg[ɂ́AA_v^[ CD ɂ[U[YKChQƂ邩A JX^}[T|[g Web TCgF http://www.intel.com/p/ja_JP/support/ QƂĂB

*@

ŏIύX 2007N1011 3:48p ԍ 14

DOCS/QUICK/JPN/style.css0000755000000000000000000000450511651733270011665 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/JPN/warranty.htm0000755000000000000000000001217011600400030012344 0ustar n[hEFAۏ

n[hEFAۏ

CéÃpbP[WŔzzA_v^-iɂ‚āAގѐׂ̌ɑ΂ۏ؂𐻕ȉ㏊L҂ɒ񋟂܂BA_v^ĩCXg[̑܂͕sȎgpɂ鑹ɑ΂ẮA̕ۏ؂͓Kp܂B

q̕ۏ؂́ÂׂĂ̕ۏ؏i̕ۏ؁AAَA܂͖@킸AmIY̐NQȂƁAiAāAdlA܂̓Tv琶ړIK̕ۏ؂܂߁Ȃ؂̕ۏ؂ɑēKp܂B

̕ۏ؂́ApAߎApAsӁAACAЊQAsK؂ȃCXg[A܂͕sK؂ȃeXgɂ鑹Q́A{ۏ؂̑ΏۂƂȂ܂BA_v^[iɌׂ‚ꍇ́ACe͈ȉɎw肵ꍇAqlׂ̐ Return Material Authorization (RMA) [ԕi] ̔ԍ (ȉQ)Aэw̏ؖ (o^ς݂łȂꍇ) ƂƂɍw̃fB[[܂̓CeɒoꍇɂāACӂɂn[hEFAǐ܂͏C𖳏Œ񋟂邩AA_v^[i̍wiԋ܂BqlA_v^[i𑗕tꍇ́AȂQ܂͕̊댯z肹˂΂Ȃ܂Bql͐iɕt̔ (܂͂Ɠ̂) gpA𕥂Kv܂B

CéAA_v^[ǐA܂͐VKi܂͍ĐigpCsAA_v^[i܂̓CeɂꂽíACȅLƂȂ܂BCς݂܂͌ꂽA_v^íACeɂCӂɂA󂯎̂ƓrW x܂͂ȍ~łqlɖ߂܂BCéA~ɂȂA_v^[i̓̃A_v^[iƌ錠ۗL܂B

אi̕ԕi

kĂŕԕiꍇF

A_v^[iԕiOɁACẽJX^}[ T|[g 1 916-377-7000 ɓdbāAReturn Material Authorization (RMAAԕi) ԍ擾ĂB

JX^}[ T|[g O[vɂAA_v^[iɌׂ邱Ƃ؂ꂽꍇ́ARMA ɂA_v^[i̊Oɕt RMA ԍs܂BCéApbP[W RMA ԍ̂Ȃi͈؎󂯕t܂B

kĈȊÔׂĂ̏ꏊŕԕiꍇF

A_v^[i̕ԋ܂͌󂯂ɂ́AA_v^[iwꏊɕԕiĂB

Ce A_v^[ԋۏ (kĂ̂)

CéAqlwȂCẽA_v^[iɊSɖĂƎvĂ܂Bw 90 ȓ̊Ԃɂ́Aql̓CẽA_v^[wɕԕiAfB[[wiSz̕ԋ󂯂邱Ƃł܂Bԕi󂯕tAqlɕԋ郊Z[уfBXgr[^[͂ꂼACẽA_v^[̍wꏊɖ߂Ƃł܂BCéÃ|V[̉ɁACe璼ڍwql̕ԕi󂯕tA̍wiqlɕԋ邱Ƃۏ؂܂B

Ɛӂы~

̋Lڂɏ]ăCȇӖ́AځAqϓIɑ”\ȑ݂̂Ɍ肳܂BCéAmIY̐NQȂƁAĒB̔pAgp̑AƖ̒fAcƌ̑Aїv̑܂ނɌ肳ȂAȂԐړI܂͐_IȑQɑ΂A؂̐ӔC𕉂܂B܂Â悤ȑQ_̑ӖAs@sׁA܂͑̕ۏ؂̉ɐۂɂ炸ACȇQ̉”\ɂ‚ĎOʒm󂯂ĂۂȂ̂Ƃ܂BOqɂ炸A{_̉ɂׂĂ̔ɑ΂CȇS–́A{iɎxi𒴂邱Ƃ͂܂BݓIȐӔCɑ΂邱̐́AỉiݒɂĕKvȗvfłBCéAȂ҂̂ӔCz肷邱ƁAѐӔC̑zF邱Ƃ͂܂B

BɂẮAtI܂͌ʂƂĐ鑹Q̏O܂͐‚Ȃ߁AL̐qlɓKpȂꍇ܂B

NeBJERg[EAvP[VF Ce͓ɁA{A_v^[iCZV[܂̓TuCZV[NeBJERg[EAvP[V (ƂĂ̂݋S܂̓wXPAERg[EVXeAq̓Rg[EVXeA܂͍q@邢͒ňʃRg[EVXe܂) Ŏgpꍇɂ͈ؐӔC𕉂킸Â悤Ȏgp͊SɃ[U̐ӔCƂȂ܂BCZV[́ACZV[܂̓TuCZV[ɂ邻̂悤ȃAvP[Vɂ{A_v^[i̎gp琶邷ׂĂ̗vCeٌ삵AۏႵی삷邱Ƃɓ ̂Ƃ܂B

\tgEFAF A_v^[iƂƂɒ񋟂\tgEFAɂ́AL̃n[hEFAۏ؂͓Kp܂B\tgEFA̕ۏ؂̏ڍׂɂ‚ẮA{A_v^[iɓĂY\tgEFAgp_񏑂QƂĂB

ŏIύX2002N723 10:42a ԍ 6

DOCS/QUICK/KOR0000755000000000000000000000000011761422164007730 5ustar DOCS/QUICK/KOR/legaldis.htm0000755000000000000000000000170111730046352012304 0ustar

۱

Copyright © 2002 - 2012 Intel Corporation. All rights reserved.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

ڻ å ʽϴ. ⿡ ϵ ƮѴٴ ʽϴ.

, ״Ͼ Ƽ ̱ Ÿ ڻ ǥԴϴ.

*ٸ ̸ 귣 ٸ ȸ ֽϴ.

Ʈ ̼

 

: 11/01/25 10:21p DOCS/QUICK/KOR/license.htm0000755000000000000000000003012711730046352012146 0ustar Ʈ ̼

Ʈ ̼

߿ - Ʈ , ġ Ǵ ϱ ݵ оñ ٶϴ.

Ʒ о ̼ ("") Ͽ Ǵ Ʈ ڷ("Ʈ") , ġ Ǵ Ͻʽÿ.

Ʈ , ġ Ǵ ϸ ޴´ٴ ϴ Դϴ. 뿡 Ʈ , ġ Ǵ ʽÿ.

̼:

:

  • Ʈũ Ǵ ý ڿԴ Ʒ "Ʈ ̼" ˴ϴ.
  • ڿԴ " ̼" ˴ϴ.
  • OEM(Original Equipment Manufacturer)Դ “OEM ̼” ˴ϴ.

Ʈ ̼: , ϴ ڽ ǻͿ Ʈ ϰ Ʈ ֽϴ.

  1. Ʈ (a) ǰ, (b) ý ȯ濡 Ǵ ԽƮ  ü ǰ νĵǵ (“ķ̼ǵ”) ġ ϵ ̼ οǾϴ. ǰ Բ ϴ Ͽ(̿ ѵ ) ٸ 뵵 Ʈ ϴ ̼ ο ʽϴ.
  2. ڻ("") ڷḦ ִ 絵 Ҵ Ÿ ۱ ̼ οմϴ.
  3. ༭ ϴ 찡 ƴϸ Ʈ  κе , , 뿩, Ǹ, Ǵ 絵 , ڴ Ʈ Ϳ ؾ մϴ.
  4. Ʈ Ͼ, Ǵ 𽺾 ϴ.
  5. Ʈ ̼ ༭ ƴ϶ ٸ ̼ ֽϴ.

̼: ؼ , ϴ 뵵 ǻ 뿡 Ʈ ϰ Ʈ ֽϴ.

  1. Ʈ (a) ǰ, (b) ý ȯ濡 Ǵ ԽƮ  ü ǰ νĵǵ (“ķ̼ǵ”) ġ ϵ ̼ οǾϴ. ǰ Բ ϴ Ͽ(̿ ѵ ) ٸ 뵵 Ʈ ϴ ̼ ο ʽϴ.
  2. ڻ("") ڷḦ ִ 絵 Ҵ Ÿ ۱ ̼ οմϴ.
  3. ༭ ϴ 찡 ƴϸ Ʈ  κе , , 뿩, Ǹ, Ǵ 絵 , ڴ Ʈ Ϳ ؾ մϴ.
  4. Ʈ Ͼ, Ǵ 𽺾 ϴ.
  5. Ʈ ̼ ༭ ƴ϶ ٸ ̼ ֽϴ.

OEM ̼: ϴ ǿ ǰ յ ·, ǰ ڸ Ʈ Ʈ · Ǵ Ը Ʈ ·θ Ʈ ֽϴ. ⿡ ġ ̹ Ǵ ԽƮ ǻ ̹ ԵǸ ̿ ѵ ʽϴ.

  1. Ʈ (a) ǰ, (b) ý ȯ濡 Ǵ ԽƮ  ü ǰ νĵǵ (“ķ̼ǵ”) ġ ϵ ̼ οǾϴ. ǰ Բ ϴ Ͽ(̿ ѵ ) ٸ 뵵 Ʈ ϴ ̼ ο ʽϴ.
  2. ڻ("") ڷḦ ִ 絵 Ҵ Ÿ ۱ ̼ οմϴ.
  3. ༭ ϴ 찡 ƴϸ Ʈ  κе , , 뿩, Ǹ, Ǵ 絵 , ڴ Ʈ Ϳ ؾ մϴ.
  4. Ʈ Ͼ, Ǵ 𽺾 ϴ.
  5. ༭ ǰؼ Ʈ ֽϴ. ̷ ̼ ༭ "BTS(Break-The-Seal)" ̼ ༭ ֽϴ. ּ ׷ ̼ Ʈ ȣؾ մϴ.
  6. Ʈ ̼ ༭ ƴ϶ ٸ ̼ ֽϴ.

̼ . ϴ (i) ༭ 츦 ϰ ڷ Ǵ , (ii) 3ڿ ڷ 뿩 Ǵ Ӵ; (iii) Ȯ 絵 Ǵ ڷ ; (iv) ࿡ 츦 ϰ ڷ Ϻ Ǵ ü , Ǵ ȯ, (v) ڷ Ͼ, Ǵ 𽺾, (vi) ڷ ϴ ̼ ϰų Ϸ õ, (vii) ༭ 츦 ϰ ڷ, Ű ҽ Ļ ҽ ڵ Ҹ 3ڿ , ̼ ο Ǵ ϴ ˴ϴ.

ٸ Ǹ . ༭ ϴ 츦 ϰ ϰų ϴ , Ư, ۱, ũ ũ, ǥ, Ǵ Ÿ ǿ  Ǵ Ǹ ̼ ο ʽϴ. ̰ 츦 ϰ Ǵ Ͻ, , ݹݾ ̼ Ǵ Ǹ ο ʽϴ. Ư ڿ Ư, ۱, ǥ Ǵ Ÿ ǿ Ǵ Ǹ ο ʽϴ.

Ʈ ۱. Ʈ ̼ οǴ , ǸŵǴ ƴմϴ. Ʈ 纻 մϴ. Ʈ ۱ ϸ Ʈ ̱, ѹα Ÿ ۱ǹ ȣ ޽ϴ. Ʈ ۱ κ ϸ ȵ˴ϴ. ϴ Ʈ 縦 ̶ մϴ. Ʈ Ʈ ϴ ׸ , Ʈ ̳ Ʈ ǹ ʽϴ. 絵 Ʈ 纻 ϰ ̼ ༭ ؼϰڴٰ 쿡 Ʈ 絵 ֽϴ.

Ʈ ߰ . ࿡ ġ Ǵ ϴ Ʈ ̰ų Ʈ "" Ǵ "Ÿ" (" Ʈ")̶ ǥõ , ˴ϴ.

Ʈ Ͽ ༭ ٸ 浹ϴ ٸ 켱 , ̴ 浹 ذῡ ʿ κп մϴ.
ϴ Ʈ Ʈ ƴ϶ Ʈ, Ÿ ս, ý Ǵ ٸ ų ִ ԵǾ ִٴ ϰ մϴ. Ʈ "ִ ״" Ǹ Ʈ ߻ϴ ؿ ̳ å մϴ.
ϴ Ʈ ȴٵ簡 Ʈ ̶ Ǵ ǹ ƴϸ Ʈ ȣȯǴ Ʈ ̶ մϴ. ϴ Ʈ ؼ ų Ʈ ǰ Ǵ Ʈ Ͽ ϴ Ǵ ߿ δ Ͽ ִٴ մϴ.
ڿ ࿡ Ʈ 쿡 ش ൵ Ʈ 뿡 ˴ϴ.

̵ . ڿ ̵ · Ʈ , Ϸκ 90 ̵ ῡ մϴ. ̷ ߰ߵǸ ڿ ̵ ݼϿ ̵ ȯϰų ٸ ش Ʈ ޹ ֽϴ.

Ÿ . 츦 ϰ Ʈ ǰ, ħ Ǵ Ư ռ Ͽ  Ǵ "ִ ״" ˴ϴ. , ؽƮ, ׷, ũ Ǵ Ʈ Ե Ÿ ׸ Ȯ̳ Ϻ Ͽ  ̳ åӵ մϴ.

å . Ǵ ش ڴ Ʈ Ǵ ( ս, ߴ Ǵ ս ϵ ̿ ѵ ) Ͽ  쿡 å , ̴ ׿ ɼ ˰ ־ ϴ Դϴ. Ϻ // ̳ Ļ Ǵ μ ؿ å ϰų ϴ Ƿ, ڿ ֽϴ. ϴ // ٸ Ǹ ֽϴ. ǰ Ÿ ("ķ̼ǵ") ġ Բ Ʈ , ϴ ("ķ̼ǵ") ġ Ǵ ڰ ƴ϶ մϴ. ϴ ("ķ̼ǵ") ġ Բ Ʈ ùٸ ۵Ѵٴ ǥ ("ķ̼ǵ") ġ ۵ϵ Ʈ ʾ Ʈ ("ķ̼ǵ") ġ ùٸ ۵ ִٴ ϰ մϴ. ϴ Ʈ ("ķ̼ǵ") ġ ùٸ ۵ ɼ Ѵٴ մϴ. ϴ ("ķ̼ǵ") ġ Ʈ ǰ å, λ Ǵ û , ߻ϴ Ҽ, , , մ ȣ ڰ ӿ, ȸ 迭翡 ϰ ̵ ظ ʵ ̶ մϴ. ̴ ׷ û Ʈ Ǵ Ͽ ¸߾ٴ Ÿ ϴ 쿡 Դϴ.

. Ʈ Ʈ λ̳ ߻ ִ ý̳ о(: Ƿ ý, Ǵ ý) ϵ Ǵ ȵǾų ش ʾҽϴ. ׷ ǵ ų Ʈ , ϴ ǵ ų ǰ å, λ Ǵ û , ߻ϴ Ҽ, , , մ ȣ ڰ ӿ, ȸ 迭翡 ϰ ̵ ظ ʵ ̶ մϴ.

. ֽϴ. Ǹ ڴ ٷ Ʈ ıϰų Ʈ 纻 ڷ ݼؾ մϴ.

. ࿡ ߻ϴ û 浹 ĶϾ ˴ϴ. ϴ ǰ Ÿſ UN ࿡ ʴ´ٴ մϴ. ؼ Ʈ ϸ ȵ˴ϴ. ǥ ٸ ࿡ Ͽ  ǹ ʽϴ.

ѵ Ǹ. Ʈ ߵ ̸ “ѵ Ǹ" ˴ϴ. , Ǵ FAR 52.227-14 DFARS 252.227-7013 et seq. Ǵ ļ ϴ. Ʈ Ѵٴ Ͽ ǰ մϴ. Ǵ ڴ Դϴ.

; . ٸ ༭ , Ǹ θ Ǵ ⺻ ˴ϴ.

: 11/5/15 10:56p

DOCS/QUICK/KOR/note.gif0000755000000000000000000000073211651733270011451 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/KOR/qi_kor.htm0000755000000000000000000001233311546611560012013 0ustar (R) Ʈũ ġ ȳ

® Ʈũ ġ

PCI, PCI-X Ǵ PCI ͽ* ġ

  1. ǻ͸ ڵ带 ̽ϴ.
  2. ǻ ش Ϳ ġϴ Կ մϴ.
  3. 𼭸 Ŀ͸ о Կ 귡Ŷ ÿ ŵϴ.
  4. ǻ ٽ ڵ带 մϴ.

: Ϻ ⰡƮ ũž ʹ PCI ͽ Ȱմϴ. Ŀͺ ϴ , PCI ͽ÷ Ŀͺ ª Կ ġ ʽÿ.

Ʈũ ̺

® PRO/100 ⰡƮ : 10Mbps Ʈũ īװ 3, 4 Ǵ 5 ƮƮ ̴(TPE) Ʈũ ̺ Ͽ Ʈũ ̺ Ϳ Ͻʽÿ. 100 Ǵ 1000 Mbps Ʈũ ְ Ʈũ īװ 5(4 ) ̺ Ͻʽÿ.

SC ĿͰ ִ ® ⰡƮ : Ŀ иϿ Ͻʽÿ. 1000Base-SX ÷ SC Ŀ͸ 귡Ŷ TX/RX Ʈ ʽÿ.

LC ĿͰ ִ ® ⰡƮ : Ŀ иϿ Ͻʽÿ. ˸ ̺ Ͽ LC Ŀ͸ Ϳ ϴ(1000BASE-SX Ǵ 1000BASE-LX). ̺ ´ 쿡 SC ٸ Ŀ ϴ ȯ ̺ ֽϴ.

ǻ͸ ϰ Ʒ ̹ ġ ȳ ʽÿ.

̹ ġ

Windows  ü

̹ ġϷ  ü ־ մϴ.

  1. Ͱ ǰ Windows Windows ̹ ġϰų ϵ ߰ 縦 մϴ.
  2. ϵ ߰ 簡 ۵Ǹ ߸ ϴ.
  3. CD ֽϴ. Ʈũ ڵ α׷ ڵ ۵˴ϴ. ̹ Ʈ ġ ߸ Ŭմϴ.

Linux*

̹ ̳ʸ RPM* Ű Ϸ 'rpmbuild -tb <filename.tar.gz>' մϴ. ⼭ ̸ <filename.tar.gz> ̹ ش ̸ ٲٽʽÿ.

:

  • 尡 ùٸ ۵Ϸ Ŀΰ ġ Ŀ ҽ ġؾ մϴ. Ŀ ٽ 쿡 ý ٽ մϴ.

  • RPM Red Hat ׽ƮǾϴ.

  • PRO/100 Ϳ ؼ ̹ ̸ e100 Ͻʽÿ.

  1. 丮 ̹ tar ̵մϴ. , '/home/username/e1000' Ǵ '/usr/local/src/e1000' ֽϴ.

  2. DZϴ. ⼭ <x.x.x> ̹ tar ȣԴϴ.
    tar zxf e1000-<x.x.x>.tar.gz
  3. ̹ src 丮 ̵մϴ. ⼭ <x.x.x> ̹ tar ȣԴϴ.
    cd e1000-<x.x.x>/src/
  4. ̹ մϴ.
    make install
    ̳ʸ ġ˴ϴ.
    /lib/modules/<kernel_version>/kernel/drivers/net/e1000.o

    ġ ġ ⺻ ġԴϴ. Ϻ Linux ǿ ̷ ġ ٸ ֽϴ.

  5. ġմϴ.
    insmod e1000 <parameter>=<value>
  6. Ͽ ̽ IP ּҸ մϴ. ⼭ <x> ̽ ȣԴϴ.
    ifconfig eth<x> <IP_ּ>
  7. ̽ ۵ϴ Ȯմϴ. մϴ. ⼭ <IP_ּ> ׽Ʈ ̽ ݿ ִ ٸ ǻ IP ּԴϴ.
    ping <IP_ּ>

Ÿ  ü

ٸ ̹ ġϷ CD ִ ȳ ϰų Ʈ http://www.intel.com/p/ko_KR/support/ 湮Ͻʽÿ.

*

: 2007 10 11 3:48p : 14

DOCS/QUICK/KOR/style.css0000755000000000000000000000450511651733270011671 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/KOR/warranty.htm0000755000000000000000000001141511546611560012376 0ustar ѵ ϵ

ѵ ϵ

ڿ Ű Ե ǰ ᳪ ۻ ڰ մϴ. ġ ջǾų ջ 쿡 ǰ ʽϴ.

, Ǵ ÷κ ߻ϴ ħ, , Ư ռ Ͽ(̿ ѵ ) , Ǵ ο ٸ üմϴ.

, , , , , , 糭, ġ Ǵ ׽Ʈ ջ ǰ ü 쿡 ʽϴ. ǰ ڰ ִ ǺǸ Ʒ ϰ ܵ ǴϿ ϵ ǰ ü Ǵ ϰų RMA(Return Material Authorization) ȣ(Ʒ ) ( ) Բ ڿ Ͽ ǰ 븮̳ ڿ ǰ ǰ Ű ȯ 帳ϴ. ǰ ߻ϴ ļ̳ нǿ å Ͽ ֽϴ. ǰ Ǵ ׿ 縦 ϰ ۺ ҷ ֽʽÿ.

ǰ ǰ̳ ǰ üϰų ǰ ֽϴ. ڿ ü ǰ̳ ǰ ڿ ˴ϴ. ϰų ü ǰ Ǵܿ ÿ ϰų ǰ˴ϴ. ܵ ǰ ǰ ׿ ϴ ǰ ü Ǹ մϴ.

ִ ǰ ǰ

Ϲ :

ǰ ǰϱ +1 916-377-7000 Ͽ RMA(Return Material Authorization) ȣ ʽÿ.

ΰ Ϳ ڰ Ȯϸ RMA μ RMA ȣ ߱Ͽ ǰ Ѹ鿡 ϵ ûմϴ. RMA ȣ ϵ ǰ ʽϴ.

ٸ :

ǰ ó ǰϸ ȯ Ǵ ü ֽϴ.

ȯ (Ϲ )

ڿ е Ͻ ǰ Ͻñ⸦ մϴ. 90 ̳ ͸ ó ǰϽø Ű ȯ ֽϴ. ǰ ޾Ƽ ǰ ȯ 븮 ش ͸ ó ֽϴ. ڿ å ǰ ϸ ڷκ Ű ȯ 帳ϴ.

å å

࿡ å ̰ Ȯ ջθ ѵ˴ϴ.  쿡 ħ, , ս, ߴ, ս Ǵ ս Ͽ(̿ ѵ ) ׷ ջ ̵ ҹ Ÿ ؼ ߻ ο ϰ Ǵ ߷ ջ(, Ư ջ ϵ ̿ ѵ ) å ʽϴ. ڿ ׷ ջ ɼ ˰ ־ 쿡 ˴ϴ. 뿡 ұϰ, ࿡ Ŭӿ å ѵ ǰ ԰ ʰ ʽϴ. åӿ ̷ ǰ ϴ ʼ Ǵ Դϴ. ٸ Ÿ å ʽϴ.

Ϻ Ǵ ջ ܳ Ƿ Ͽ ֽϴ.

߿ о: ڿ ̼ Ǵ ̼ ڰ Ǵ ǰ ý, ý, Ǵ ý ߿ о߿ ǰ ׿ å , ׷ 뿡 δ ڰ մϴ. ̼ ڴ ڽ Ǵ ̼ ڰ ׷ о߿ ǰ ߻ϴ Ŭκ ظ ʵ ȣϰ ؾ մϴ.

Ʈ: ǰ Բ Ʈ ϵ ʽϴ. Ʈ ǰ Բ ش Ʈ ̼ ༭ Ͻʽÿ.

: 2002 7 23 10:42a : 6

DOCS/QUICK/PTB0000755000000000000000000000000011761422164007722 5ustar DOCS/QUICK/PTB/legaldis.htm0000755000000000000000000000217011730046352012277 0ustar Assuntos legais

Copyright e iseno de responsabilidades legais

Copyright © 2002 - 2012 Intel Corporation. Todos os direitos reservados.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

A Intel Corporation no assume nenhuma responsabilidade por erros ou omisses neste documento. A Intel tambm no assume nenhum compromisso de atualizar as informaes aqui contidas.

Intel, Itanium e Pentium so marcas comerciais da Intel Corporation nos Estados Unidos e em outros pases.

* Outras marcas e nomes podem ser propriedade de outras empresas.

Informaes sobre garantia

Software License

 

ltima modificao: 25 de janeiro de 2011 s 22:21 Reviso DOCS/QUICK/PTB/license.htm0000755000000000000000000003645011730046352012145 0ustar Software License

CONTRATO DE LICENA DE SOFTWARE INTEL

IMPORTANTE LEIA ANTES DE COPIAR, INSTALAR OU USAR.

No copie, no instale nem use este software ou qualquer material associado (coletivamente o “Software”) fornecido sob este contrato de licena (“Contrato”) antes de ler cuidadosamente os termos e condies a seguir.

Ao copiar, instalar ou usar o Software, voc indica que concorda em se submeter aos termos deste Contrato. Se no concordar com os termos deste Contrato, no copie, no instale nem use o Software.

LICENAS:

Note o seguinte:

  • A “Licena de Site” a seguir aplica-se aos administradores de rede ou de sistema.
  • A “Licena para usurio nico” se aplica aos usurios finais.
  • A "Licena para fabricantes de equipamentos originais (OEM)" se aplica a tais fabricantes.

LICENA DE SITE. Voc poder copiar o Software nos computadores da sua empresa, para uso na sua empresa, e poder fazer um nmero razovel de cpias de backup do Software, de acordo com as seguintes condies:

  1. Este Software licenciado para uso apenas em conjunto com (a) componentes fsicos Intel e (b) dispositivos virtuais (“emulados”) que aparecem como produtos Intel para sistemas operacionais Guests (convidados) que rodam em mquinas virtuais. Nenhum outro uso do Software, inclusive, mas sem se limitar a, o uso com produtos no Intel, licenciado sob este contrato.
  2. Em conformidade com todos os termos e condies deste Contrato, a Intel Corporation ("Intel") concede a voc uma licena no exclusive e no transfervel de copyright para usar os Materiais.
  3. Voc no pode copiar, modificar, alugar, vender, distribuir ou transferir qualquer parte do Software, exceto na forma expressa neste Contrato, e voc concorda em impedir a cpia no autorizada do Software.
  4. Voc no pode fazer engenharia reversa, descompilao ou desmontagem do Software.
  5. O Software pode ter partes oferecidas sob termos adicionais aos aqui contidos, descritos em um contrato de licena que acompanha estas partes.

LICENA PARA USURIO NICO. Voc poder fazer uma cpia do Software em um nico computador para o seu uso pessoal, e poder criar uma cpia de backup do Software, de acordo com as seguintes condies:

  1. Este Software licenciado para uso apenas em conjunto com (a) componentes fsicos Intel e (b) dispositivos virtuais (“emulados”) que aparecem como produtos Intel para sistemas operacionais Guests (convidados) que rodam em mquinas virtuais. Nenhum outro uso do Software, inclusive, mas sem se limitar a, o uso com produtos no Intel, licenciado sob este contrato.
  2. Em conformidade com todos os termos e condies deste Contrato, a Intel Corporation ("Intel") concede a voc uma licena no exclusive e no transfervel de copyright para usar os Materiais.
  3. Voc no pode copiar, modificar, alugar, vender, distribuir ou transferir qualquer parte do Software, exceto na forma expressa neste Contrato, e voc concorda em impedir a cpia no autorizada do Software.
  4. Voc no pode fazer engenharia reversa, descompilao ou desmontagem do Software.
  5. O Software pode ter partes oferecidas sob termos adicionais aos aqui contidos, descritos em um contrato de licena que acompanha estas partes.

LICENA PARA FABRICANTES DE EQUIPAMENTOS ORIGINAIS (OEM): Voc pode reproduzir e distribuir o Software apenas como parte integrante ou na forma incorporada ao seu produto, como atualizao de manuteno do Software para usurios existentes dos seus produtos, excluindo-se quaisquer outros produtos individuais, ou como uma distribuio maior do Software, incluindo, mas no se limitando a, a distribuio de uma imagem de instalao ou uma imagem de mquina virtual convidada (Guest), com estas condies:

  1. Este Software licenciado para uso apenas em conjunto com (a) componentes fsicos Intel e (b) dispositivos virtuais (“emulados”) que aparecem como produtos Intel para sistemas operacionais Guests (convidados) que rodam em mquinas virtuais. Nenhum outro uso do Software, inclusive, mas sem se limitar a, o uso com produtos no Intel, licenciado sob este contrato.
  2. Em conformidade com todos os termos e condies deste Contrato, a Intel Corporation ("Intel") concede a voc uma licena no exclusive e no transfervel de copyright para usar os Materiais.
  3. Voc no pode copiar, modificar, alugar, vender, distribuir ou transferir qualquer parte do Software, exceto na forma expressa neste Contrato, e voc concorda em impedir a cpia no autorizada do Software.
  4. Voc no pode fazer engenharia reversa, descompilao ou desmontagem do Software.
  5. A distribuio do Software aos seus clientes s pode ser feita com um contrato de licena em forma escrita. Este contrato de licena pode ser do tipo "violao de lacre". No mnimo, tal contrato deve salvaguardar os direitos de propriedade da Intel sobre o Software.
  6. O Software pode ter partes oferecidas sob termos adicionais aos aqui contidos, descritos em um contrato de licena que acompanha estas partes.

RESTRIES DA LICENA. Voc NO pode: (i) usar ou copiar os Materiais exceto nas formas estabelecidas neste Contrato; (ii) alugar ou fazer lease dos Materiais a terceiros; (iii) ceder este Contrato ou transferir os Materiais sem o consentimento expresso e por escrito da Intel; (iv) modificar, adaptar ou traduzir os Materiais, no todo ou em parte, exceto nas formas estabelecidas neste Contrato; (v) fazer engenharia reversa, descompilar ou desmontar os Materiais; (vi) tentar modificar ou adulterar o funcionamento normal do gerenciador de licenas que regulamenta o uso dos Materiais; (vii) distribuir, sublicenciar ou transferir o cdigo fonte de qualquer componente dos Materiais, dos Redistribuveis e das Fontes de Amostras e seus derivados para terceiros, exceto nas formas estabelecidas neste Contrato.

NENHUM OUTRO DIREITO. A Intel no outorga a voc direitos nem licenas, implcitos ou explcitos, em relao a informaes de propriedade ou patentes, direitos autorais, trabalho de mscara, segredo comercial ou outro direito de propriedade intelectual de propriedade ou de controle da Intel, exceto nas formas expressamente estabelecidas neste Contrato. Exceto nas formas expressamente estabelecidas neste Contrato, no concedida a voc nenhuma licena ou direito, direto ou implcito, por induo, embargo ou outra forma. Especificamente, a Intel no concede nenhum direito expresso ou implcito a voc em relao a patentes, direitos autorais, marcas comerciais ou outros direitos de propriedade intelectual da Intel.

PROPRIEDADE DO SOFTWARE E DIREITOS AUTORAIS. O Software licenciado, no vendido. O ttulo de todas as cpias do Software permanece com a Intel. O Software contm direitos autorais e est protegido por leis dos Estados Unidos e de outros pases e por provises de tratados internacionais. Voc no pode remover nenhum aviso de direitos autorais do Software. Voc concorda em impedir qualquer cpia no autorizada do Software. A Intel pode fazer alteraes ao Software ou aos itens aqui citados a qualquer momento sem aviso prvio, mas no est obrigada a oferecer suporte ou a atualizar o Software. O Software s poder ser transferido se o destinatrio concordar totalmente com estes termos e se voc no retiver nenhuma cpia do Software.

TERMOS ADICIONAIS PARA SOFTWARE DE PR LANAMENTO. Se o Software que voc est instalando ou usando sob os termos deste Contrato for uma verso de pr lanamento comercial, ou for uma verso “alfa“ ou “beta“ do Software ("Software de pr lanamento"), ento os termos a seguir se aplicaro.

Se alguma clusula desta Seo entrar em conflito com qualquer termo ou condio deste Contrato em relao a Software de pr lanamento, esta Seo ter precedncia sobre o(s) outro(s) termo(s) e condio(es), mas apenas at o ponto necessrio para resolver o conflito.
Voc entende e reconhece que o Software um Software de pr lanamento, no representa o Software final da Intel e pode conter erros e outros problemas que podem causar perda de dados, falhas de sistema ou outras falhas. O Software de pr lanamento fornecido a voc "no estado em que se encontra" e a Intel se exime de fornecer garantias e no se responsabiliza por danos que possam ocorrer como consequncia do uso deste Software de pr lanamento.
Voc reconhece que a Intel no prometeu que o Software de pr lanamento ser lanado no futuro, que a Intel no tem obrigao explcita ou implcita de lanar o Software de pr lanamento e que a Intel pode no lanar nenhum Software que seja compatvel com o Software de pr lanamento. Voc reconhece que a totalidade da pesquisa e desenvolvimento que voc fizer e que for relacionada ao Software de pr lanamento ou a qualquer produto que use ou que esteja associado ao Software de pr lanamento feita por sua conta e risco.
Se a Intel forneceu a voc o Software de pr lanamento sob um contrato escrito separado, o uso que voc fizer deste Software de pr lanamento regido tambm por tal contrato.

GARANTIA LIMITADA DA MDIA. Se o Software tiver sido entregue pela Intel em mdia fsica, a Intel garante esta mdia contra defeitos fsicos de material por um perodo de noventa (90) dias a partir da data de entrega. Se for detectado algum defeito fsico, devolva a mdia Intel para substituio ou remessa alternativa do Software, a critrio da Intel.

EXCLUSO DE OUTRAS GARANTIAS. EXCETO PELO DESCRITO ACIMA, O SOFTWARE FORNECIDO "NO ESTADO EM QUE SE ENCONTRA", SEM QUALQUER GARANTIA EXPRESSA OU IMPLCITA DE QUALQUER TIPO, INCLUINDO AS GARANTIAS DE ADEQUAO AO MERCADO, AUSNCIA DE INFRAO OU ADEQUAO A UMA FINALIDADE PARTICULAR. A Intel no oferece garantia nem assume responsabilidade pela exatido ou pela integridade de quaisquer informaes, textos, grficos, links ou outros itens contidos no Software.

LIMITAO DE RESPONSABILIDADE. SOB NENHUMA CIRCUNSTNCIA A INTEL OU SEUS FORNECEDORES SE RESPONSABILIZARO POR QUALQUER DANO (INCLUINDO, MAS NO SE LIMITANDO A, PERDA DE LUCROS, INTERRUPO DE NEGCIOS OU PERDA DE INFORMAES) RESULTANTE DO USO OU INCAPACIDADE DE USO DO SOFTWARE, MESMO QUANDO A INTEL TIVER SIDO AVISADA DA POSSIBILIDADE DE OCORRNCIA DE TAIS DANOS. ALGUMAS JURISDIES PROBEM A EXCLUSO OU LIMITAO DA RESPONSABILIDADE PARA GARANTIAS IMPLCITAS OU PARA DANOS CONSEQENCIAIS OU INCIDENTAIS; PORTANTO, A LIMITAO ACIMA PODE NO SE APLICAR A VOC. VOC PODE TAMBM TER OUTROS DIREITOS LEGAIS QUE VARIAM DE JURISDIO PARA JURISDIO. Se voc usar o Software em conjunto com um dispositivo virtual (“emulado”) e destinado a aparecer como um produto Intel, voc reconhece que a Intel no a autora nem a criadora do dispositivo virtual (“emulado”). Voc entende e reconhece que a Intel no faz nenhuma afirmao sobre a correta operao do Software quando ele usado em um dispositivo virtual (“emulado”), que a Intel no projetou o Software para operar com o dispositivo virtual (“emulado”), e que o Software pode no ser capaz de funcionar corretamente com o dispositivo virtual (“emulado”). Voc concorda em assumir o risco de que o Software possa no funcionar corretamente em conjunto com o dispositivo virtual (“emulado”). Voc concorda em indenizar a Intel e manter a Intel e seus funcionrios, suas subsidirias e suas afiliadas isentos de responsabilidade contra todos os processos judiciais, custos, danos e despesas, alm de custos advocatcios razoveis, resultantes, direta ou indiretamente, de qualquer reclamao de obrigaes do produto, leses corporais ou morte associadas ao uso do Software em conjunto com o dispositivo virtual (“emulado”), mesmo sob a alegao de que a Intel foi negligente em relao ao design ou fabricao do Software.

USO NO AUTORIZADO. O SOFTWARE NO FOI PROJETADO NEM DESTINADO OU AUTORIZADO PARA USO EM QUALQUER TIPO DE SISTEMA OU APLICAO EM QUE A FALHA DO SOFTWARE PODE CAUSAR LESES CORPORAIS OU MORTE (POR EXEMPLO, SISTEMAS MDICOS, SISTEMAS DE SALVAMENTO OU DE MANUTENO DA VIDA). Se usar o Software em qualquer destas aplicaes no autorizadas, voc ir indenizar a Intel e manter a Intel e seus funcionrios, suas subsidirias e suas afiliadas isentos de responsabilidade contra todos os processos judiciais, custos, danos e despesas, alm de custos advocatcios razoveis, resultantes, direta ou indiretamente, de qualquer reclamao de obrigaes do produto, leses corporais ou morte associadas a tal uso no autorizado, mesmo sob a alegao de que a Intel foi negligente em relao ao design ou fabricao do Software.

RESCISO DESSE CONTRATO. A Intel pode rescindir este Contrato a qualquer momento no caso de violao dos seus termos. Com a resciso, voc destruir imediatamente o Software ou devolver todas as suas cpias Intel.

LEIS QUE SE APLICAM. As aes judiciais oriundas deste Contrato sero governadas pelas leis do Estado da Califrnia, EUA, sem considerar conflitos com outras leis. Voc concorda que os termos da Conveno das Naes Unidas sobre Contratos de Venda de Bens no se aplica a este Contrato. Voc no poder exportar o Software em violao s leis e regulamentos aplicveis exportao. A Intel no est obrigada ao cumprimento de quaisquer outros contratos, a menos que se apresentem por escrito e estejam assinados por um representante autorizado da Intel.

DIREITOS RESTRITOS DO GOVERNO. Este Software e esta documentao foram desenvolvidos com capital privado e so fornecidos com “DIREITOS RESTRITOS”. O uso, a duplicao ou a divulgao pelo Governo esto sujeitos s restries estabelecidas em FAR 52,227-14 and DFARS 252,227-7013 et seq. ou s suas clusulas substitutas ou s leis sucessoras. O uso deste produto pelo governo indica o reconhecimento dos direitos de propriedade da Intel sobre o Software. A Intel o fabricante ou o contratante.

IDIOMA; TRADUES. Se a verso no idioma ingls deste Contrato for acompanhada por qualquer outra verso traduzida para qualquer outro idioma, essa verso traduzida ser fornecida somente a ttulo de convenincia e a verso gerada no idioma ingls ter prioridade de controle legal.

Modificado em 15/5/11 22:56 Reviso

DOCS/QUICK/PTB/note.gif0000755000000000000000000000073211651733270011443 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/QUICK/PTB/qi_ptb.htm0000755000000000000000000001340211546611560011775 0ustar Guia de instalao rpida dos adaptadores de rede Intel(R)

Instalao do adaptador de rede Intel®

Instalar o adaptador Intel PCI, PCI-X ou PCI-Express*

  1. Desligue o computador e desconecte o cabo de alimentao.
  2. Remova a tampa do computador e a tampa do slot correspondente ao seu adaptador.
  3. Empurre firmemente a borda do adaptador no slot PCI at que ele esteja completamente inserido. Prenda a braadeira ao chassi.
  4. Recoloque a tampa do computador. Ligue o fio de eletricidade.

NOTA: Alguns adaptadores Intel Gigabit de servidor e de desktop usam o barramento PCI Express. Voc pode usar um slot mais comprido que o conector de seu adaptador, mas no tente instalar o adaptador em um slot mais curto que o conector PCI Express.

Conectar o cabo de rede

Adaptadores Intel® PRO/100 e Gigabit de cobre: Conecte os cabos de rede ao adaptador usando cabos de par tranado Ethernet (TPE) Categoria 3, 4 ou 5 para redes de 10 Mbps. Use cabos categoria 5 (4 pares) para as redes de 100 ou 1000 Mbps e para as redes residenciais.

Adaptadores de fibra Intel® Gigabit com conector SC: Remova e guarde a tampa do conector de fibra tica. Insira um conector de fibra tica SC do tipo 1000Base-SX duplex nas portas TX/RX da braadeira do adaptador.

Adaptadores de fibra Intel® Gigabit com conector LC: Remova e guarde a tampa do conector de fibra tica. Insira um conector LC no adaptador com o cabeamento correto para o seu tipo de adaptador (1000BASE-SX ou 1000BASE-LX). Podem ser usados cabos de converso para outros tipos de conectores (como, por exemplo, SC) se o cabeamento corresponder s especificaes ticas do adaptador, inclusive as limitaes de comprimento.

Ligue o computador e siga as instrues de instalao do driver conforme abaixo.

Instale os drivers

Sistemas operacionais Windows

Voc precisa ter direitos administrativos no sistema operacional para instalar os drivers.

  1. O adaptador detectado e o Windows instala um driver residente ou inicia o assistente Novo hardware encontrado .
  2. Se o assistente Novo hardware encontrado for inicializado, pressione o boto Cancelar.
  3. Insira o CD da Intel. O programa de execuo automtica Conexes de rede Intel inicia automaticamente. Clique no boto Instalar drivers e software .

Linux*

Para criar um pacote binrio RPM* desse driver, execute 'rpmbuild -tb <filename.tar.gz>'. Substitua <filename.tar.gz> com o nome do arquivo especfico do driver.

NOTAS:

  • Para o build funcionar corretamente, o kernel em execuo PRECISA corresponder verso e configurao da origem de kernel instalada. Se voc tiver recompilado o kernel, reinicialize agora o sistema.

  • A funcionalidade RPM s foi testada nas distribuies Red Hat.

  • Para os adaptadores Intel PRO/100, use e100 como o nome do driver.

  1. Mova o arquivo tar do driver bsico para o diretrio de sua escolha. Por exemplo, use '/home/username/e1000' ou '/usr/local/src/e1000'.

  2. Extraia/deszipe o arquivo, onde <x.x.x> o nmero de verso para o arquivo tar do driver:
    tar zxf e1000-<x.x.x>.tar.gz
  3. Mude para o diretrio src, onde <x.x.x> representa o nmero da verso para o tar do driver:
    cd e1000-<x.x.x>/src/
  4. Compile o mdulo do driver:
    make install
    O binrio ser instalado como:
    /lib/modules/<kernel_version>/kernel/drivers/net/e1000.o

    Os locais da instalao listados acima so os locais padro. Eles no podem corrigir certas distribuies de Linux.

  5. Instale o mdulo:
    insmod e1000 <parameter>=<value>
  6. Atribua um endereo IP interface, digitando a seguinte informao, onde <x> representa o nmero da interface:
    ifconfig eth<x> <IP_address>
  7. Verifique se a interface funciona. Digite a seguinte informao, observando que <endereo_IP> refere-se ao endereo IP de outro computador na mesma sub-rede da interface que est sendo testada:
    ping <IP_address>

Outros sistemas operacionais

Para instalar outros drivers, consulte o Guia do Usurio no CD do adaptador ou visite o site de suporte em: http://www.intel.com/p/pt_BR/support/.

*Assuntos legais

ltima modificao em 11/10/07 15:48 14

DOCS/QUICK/PTB/style.css0000755000000000000000000000450511651733270011663 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/QUICK/PTB/warranty.htm0000755000000000000000000001434511546611560012375 0ustar Garantia Vitalcia Limitada do Hardware

Garantia Vitalcia Limitada do Hardware

A Intel garante ao propriedade original que o produto adaptador entregue neste pacote no contm defeitos fsicos nem de fabricao. Esta garantia no cobre o produto adaptador, se ele for danificado no processo de instalao ou por uso inadequado.

A GARANTIA ACIMA SUBSTITUI QUALQUER OUTRA GARANTIA, QUER SEJA EXPRESSA, IMPLCITA OU ESTATUTRIA, INCLUSIVE, MAS NO LIMITADA A, QUALQUER GARANTIA DE NO-VIOLAO DE PROPRIEDADE INTELECTUAL, COMERCIALIZAO, ADEQUAO A UM PROPSITO ESPECFICO DECORRENTE DE QUALQUER PROPOSTA, ESPECIFICAO OU AMOSTRA.

Esta garantia no cobre a substituio de produtos ADAPTADOR danificados por uso indevido, acidente, uso incorreto, negligncia, alterao, reparo, desastre, instalao incorreta ou teste inadequado. Se o produto ADAPTADOR for considerado defeituoso, a Intel, se assim decidir, substituir ou consertar o produto de hardware gratuitamente, exceto conforme especificado a seguir, ou reembolsar o valor de aquisio, desde que o produto ADAPTADOR seja entregue com um nmero RMA (Return Material Authorization Autorizao de Material Devolvido ver abaixo), juntamente com um comprovante de compra (se no estiver registrado), ao negociante onde o produto foi comprado ou Intel, com uma explicao do problema em questo. Se voc enviar o produto ADAPTADOR, assumir o risco de dados ou perda durante o transporte. Use a embalagem original (ou equivalente) e pague o frete.

A Intel pode substituir ou consertar o produto ADAPTADOR com peas novas ou recondicionadas, e o produto ADAPTADOR ou a parte substituda pela Intel se tornar propriedade da Intel. Os produtos ADAPTADOR consertados ou substitudos sero devolvidos a voc, com o mesmo nvel de reviso recebido ou nvel superior, a critrio da Intel. A Intel se reserva o direito de substituir os produtos ADAPTADOR fora de linha por um produto ADAPTADOR de gerao atual equivalente.

Devoluo de um produto com defeito

Da Amrica do Norte:

Antes de devolver qualquer produto ADAPTADOR, entre em contato com o Suporte ao Cliente Intel e obtenha um Nmero RMA (Return Material Authorization Autorizao de Material Devolvido), ligando para +1 916-377-7000.

Se o Grupo do Suporte ao Cliente confirmar que o produto ADAPTADOR est com defeito, o departamento de RMA emitir um Nmero RMA para ser colocado na embalagem externa do produto ADAPTADOR. A Intel no pode aceitar qualquer produto sem um Nmero RMA na embalagem.

Todos os outros locais:

Devolva o produto adaptador ao local de compra para obter um reembolso ou uma troca.

Garantia de Devoluo do Dinheiro Pago pelo Adaptador Intel (somente na Amrica do Norte)

A Intel quer v-lo totalmente satisfeito com o adaptador Intel que voc comprou. A qualquer momento dentro do prazo de noventa (90) dias a partir da data de compra, voc pode devolver o adaptador Intel ao local original de compra, para obter de seu fornecedor o reembolso do valor de aquisio. Os integradores e distribuidores, respectivamente, que aceitarem devolues e reembolsarem seus clientes, podem devolver os adaptadores Intel ao local original de compra. A Intel garante que aceitar as devolues coberta por esta diretiva, e reembolsar o valor de aquisio inicial aos clientes que comprarem diretamente na Intel.

Limitao de Responsabilidade e Correes

A UNICA RESPONSABILIDADE DA INTEL AQUI PREVISTA ESTAR LIMITADA AOS DANOS DIRETA E OBJETIVAMENTE AVALIVEIS. EM HIPTESE ALGUMA, A INTEL SE RESPONSABILIZAR POR QUAISQUER DANOS INDIRETOS OU ESPECULATIVOS (INCLUINDO, MAS NO LIMITADO A, OS DANOS CITADOS ANTERIORMENTE, CONSEQENTES, INCIDENTAIS E ESPECIAIS) INCLUSIVE, MAS NO LIMITADO A, VIOLAO DA PROPRIEDADE INTELECTUAL, CUSTOS DE REABASTECIMENTO, IMPOSSIBILIDADE DE USO, INTERRUPES DE NEGCIOS, PERDA DE REPUTAO E LUCROS CESSANTES, QUER ESSES DANOS SURJAM POR NEGLIGNCIA CONTRATUAL, RETALIAO OU SOB QUALQUER GARANTIA, A DESPEITO DE A INTEL TER SIDO AVISADA ANTECIPADAMENTE SOBRE A POSSIBILIDADE DESSES DANOS. INDEPENDENTEMENTE DO DISPOSTO ANTERIORMENTE, A RESPONSABILIDADE TOTAL DA INTEL POR TODAS AS REIVINDICAES PREVISTAS NESTE CONTRATO NO DEVER ULTRAPASSAR O PREO PAGO PELO PRODUTO. ESSAS LIMITAES SOBRE AS POSSVEIS RESPONSABILIDADE FORAM UM COMPONENTE FUNDAMENTAL AO ESTIPULAR O PREO DO PRODUTO. A INTEL NO ASSUME NEM AUTORIZA QUALQUER PESSOA A ASSUMIR QUAISQUER OUTRAS RESPONSABILIDADES EM SEU NOME.

Alguns estados no permitem a excluso ou limitao de danos incidental ou conseqentes, de modo que as limitaes citadas anteriormente podem no ser aplicveis ao seu caso.

Aplicaes de controle crtico: A Intel se isenta especificamente da responsabilidade pelo uso do produto ADAPTADOR em aplicaes de controle crtico (incluindo, apenas para fins de exemplo, os sistemas de controle de segurana ou tratamento de sade, sistemas de controle de energia nuclear ou os sistemas de controle do trfego areo ou terrestre) por Licenciado ou Sublicenciados, e tal uso ser um risco total do usurio. O Licenciado concorda em defender, indenizar e isentar a Intel de e contra quaisquer e todas as reivindicaes decorrentes do uso do produto adaptador em tais aplicaes pelos Licenciado ou Sublicenciados.

Software: O software fornecido com o produto ADAPTADOR no est coberto pela garantia de hardware descrita anteriormente. Consulte o contrato de licena do software aplicvel, que acompanha o produto ADAPTADOR, para obter detalhes sobre a garantia do software.

ltima modificao em 23.07.02 10:42 6

DOCS/QUICK/chs.gif0000755000000000000000000000040711644566662010640 0ustar GIF89aK̙333,KI8`(dihJ p l2 "O%|\$O셊NuL r/SUUmӴU[MYXYm^r]ywFpfXStbCP({'W`Bx&5\%QzVa~C[sOo8#7Ɲ;DOCS/QUICK/cht.gif0000755000000000000000000000042711644566662010643 0ustar GIF89aK̙333,K@I8`(i%H,zo* |<ܧGbƙC21uWz9" #cӴ }^IPQBa_@z!vjj*+$iYu?q5ftr:~JVTn;-|Xo7XplW՚_8;DOCS/QUICK/deu.gif0000755000000000000000000000033311644566662010636 0ustar GIF89aK̙333!,K@0 I8덁'8$ tms||i*VF"9 oykͬR;߰zkBnn|NǥӬ8*XiexU\66`bH&E'aZcd^,_#C5~4j ;DOCS/QUICK/esn.gif0000755000000000000000000000036111644566662010647 0ustar GIF89aK̙333,K@I8`( AꪚiȖg |߹pH>–ւ-'XZy5;)}ߗFL0]|N~El=<,]D1cfB;::nhL/?6i\j~>M/3%3P.eo" 8;DOCS/QUICK/fra.gif0000755000000000000000000000032711644566662010634 0ustar GIF89aK̙333!,K@0 I8)v!btms||^C$JQ9~()ZkT^:*5#wj.`n|N_6oaMWd;g}f6aE`"$_[+>I=5^\&$4,1 ;DOCS/QUICK/ita.gif0000755000000000000000000000035311644566662010640 0ustar GIF89aK̙333,K@I8`(#f&jd- |oH,sFL k12LZjea}Z#_ѧA|N~GIm`~Ek%O#Cc$ ?!N^-\iF>cijD+3RLe78;DOCS/QUICK/jpn.gif0000755000000000000000000000036211644566662010652 0ustar GIF89aK̙333,K@I8`(#A' +)7xwp{",X#y\)w̦v dJk2Iu_m9mhw쒅8@r]2i@kv;pXjO90\(h\r1`N~l?0io7[a>e+jcgfH6jQX.c ^i'I.k2 ;DOCS/QUICK/quick.htm0000755000000000000000000000604111644566662011222 0ustar Install Instructions

Localized Quick Installation Instructions

These condensed instructions are intended for experienced users and cover basic hardware and software installation only.  English

  Traditional Chinese   German
  French   Japanese
  Italian   Portuguese
  Korean   Spanish
  Simplified Chinese  

 

Last modified on 12/06/07 2:58p Revision

DOCS/QUICK/style.css0000755000000000000000000000450511651733270011236 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/SERVER0000755000000000000000000000000011761422164007427 5ustar DOCS/SERVER/45double.gif0000755000000000000000000001647311656741062011642 0ustar GIF87a/,-#!#+)+313;9;! !WUW|z|xvxQPQPOP~}~mlm]\]²;9<557EEGrrullo[[]001++,CCD}}~uuvdde\\]Ҽ?@Ckloacgiko}~сy|QSUY[]cdeghiqtv¹9;VY"fWV\.$R1C+Q^$ԇuRDGwVƹ JH-!č*aTD r@yrFZr i **Ч.ڨ(Q*Ц04$Le1rY X]Y1/q#Gu곭%ATpIƔhY2@@"ȭ|"C¶c /UdQx \‡%8*Н.c)P!DCB $8b yd.(+lPa[D /#RD|Lx5*j+I0}nWW[%B 6/E)F kĽ)+. P+rFJ3 $*Bq֞tfB,Tˀ eF$$g牟\x*'؋ P+XJq 0xs"ۇg.f ~ Sd6>l~W(|)ǎ1 B|+҇,AW: #}[H h,e0X` kH/Y0# e >L A &lcH/eAa7^\P  w"IHb!x qVz#33 >b$[[ > Er8.vxĐr pыhP'1e B5$ub@P#CS@vD萲DvEӑ J$~uɒdɢDƝ,S ʠc8MdMJ/RZ gU8Ib%BxDqј,: rS:(LS , ȆDYO4}z̭_wK5؛<_#:HQiz|@ݔx4sָiDQISTFe@^/{(15a V$u$wE~}(52_B^p#08R$"hS`'Is( QrY@'H$gS9uL,؂[ X5f1qR1}]>v_RY25ExTBM``!ICpvQh:S*%& 9#2tr1qh9e0g4H̀ }"X5KsW! >[ׇb_cpնYYqurbu ]@xţ PFwe+7hg"d}U'.H>W`RSS ҃=V-#ŵq&,#^>l`TZTzxcQYsDo"1sfqu5 a]_bEx Ў%S0'*x~ e2&_p@ZT@36>^$RU5*@2]S!Ñ{ ԅh#l]"g@gxu a7_WT*' 5` fW"d7]ҵ&,u$>lI@Aql#Ty1Xy"/$VXXnVzH.^`;) djSaA[CoXRJ ;q  <9sbeJ̃j1 @P<" d"֙.H Y9$N3J(O(,I0U3Fv RZyoxfqSzIdVb)#x,E<eOc~ȝDCx".A=;X3 [ lY&|?cM!aChسwH[5C>Q&S,WNFoDi*sgAt(ЕMa 0P.f>Ygehd @_`gAO抅"ӏf)p2)gRLP">630BvaB79g`hF`o6.0D>:}GH ֏Y]9DOD YI1#h a N({8LlByhYb*0 jrak^ )iEKԬ JDZEs*E:klUEa42T]4kfZt:Dln$pTU·'DWzFߪԫ"qmdLzׯc*i0<c pۖKqG畱́V}@ !K$ &p pLQF.+kEVo" >|@"mB+F AE ױ SGEWP #Qo[ {Fڲ񲇝|@j<ã"+%:1zxqq!n&rKb*`w (SǸy!v/cĹk|Blt\dC۸FrYdC9q6˻H7@*rŻ5r4.%h o|Ut+ h(!=e&{`w mHGPWwDi$f~aGdzDr";L1f!k|Wv^f,fB!xqL8\C;D!DԺWVb0 {a j[qXOA !QLq{.MqR5U^ ESo>1q6|0A+꾦ƵK*N7S2&ȉ\q} TzH4\>Ǜuٴcw}xPG{dWQNME[!izX*@&eN"WZ:sc6et}Lw~*C} %9Npm@. nPhLQ\z])sHv8't9<, 9+wf( 4#M! v ,2ҺHf vגi0*} $43"=C5h>l2=/Se)Yk@)44N$ak[ P ADMo fSK&JNERB]IBP6jJ}ש_NP1lwʪ91ViSp-|' #H5V]č펚RIaI5*<ڭiX]~bq! DP탇%JJEi˭Yb>C-݈I,G#zTl܎L30$=gIMٍuBR -3߷( %@|<e:R4 % rkҽ4i.2p2 ,"w"6.sKٜ mߏA)(8/Őh^&.W3UN{/QAi`0`SFF03ӳ}=8+;*;3MP3RQ A]WP4Mcy0!8sVfcSn4B~8 ;3xâa | 5a,31sY萾_S0J֙A;4-9{x5tWdE6/~nk&M\!A-22Z2#3VqpV]YK >0돋dq٤.&g"[A!x C4y~>Cx)Iڅ(,qJUJRl 꾅߈yuf.-#MQ Cd]ӕa`ߦI/V pr^7Q 5;z&5p~tH`߂n9ʨٕwi#uD`0@6U,`*9Ci1 ]?*,lW]7 67C1ͤ?4rO#5 *D`ѵ:F &@H P(QPD zZcP<~ B 1-=9S(T3{l9+T+BRh PEj0UTUr1jWK<5,K~}֢ʔm9 i%fZȲ'Fw{ u_4L3P+SHP>sL FE2HbH a%1ע,4 ;f9T @j"M-AUXU $ lB=(]Ws/v ; [Xd]YODKД5>X$[mB`[GH`\<\)LWX@J*ʹ#gͫW6-P&ۣ*޶Px&$>V8g*^$d?&=Iٱ !JYYW,Vfy#pZ>ʦ9%\ :h dC̪JaxA /bS\6>e2m寱t{%k*oX$ \.jFv #_b ÒqsݻYs=/5HL`"DXzo!*y zj {Yyu@&$XWc ˧|aɖ@L"4N ! YJT']9K2+e.fKR/K`W LiLfZ ɚ9ML!,9f6/%4f815 lSb;DOCS/SERVER/KCCA.gif0000755000000000000000000007240511656741516010721 0ustar GIF89a3(! ,3(ڋ޼H扦ʶ L ĢJL* JԪjܮ 2N' HHXhx)9IYiy7h):JZjz +;K[k{ػ ,N^n~ͷO_o?>/~<0… xÉcI1ƍ;z|tQP$Kf i2ʕ,[RN̗4ki3Ν<{L5NP &io(ҥL:}Si #V8eue5Ѭd-B*°غBnB&ה]ػ&2s1I(T2anIIPt ~xښJ|xhhV }x=ۜ?;qr΄{xobaO5:sqt}jW㺉9E(q]!yە_!gշ7 { ؘ NJ`Yd& Ga ?%bh3HD#G#5Ђ$>>dDIڷxU^qHݔvxP15yNz)c1hFff%aRқrv֝[*H^ J%6N Jyv[^i$*Ihzj%*v)k!>(tm˜޳u1+F,{תzQ[ [gLj*l6arxvf8mzbΛiofOnꙋn {n2ps!S[:XIw8vkHcL7K4chCr _p ( 5ψG\l)ɠ"i}*' Qwo_e`7 *x-~HcvDn53X%Bwl>[=EiV:L\͕{>3f7Xݐ|A9/'0׳w|dwF+ l|;1J} &}Fed>'viRϽVTs^>Rbk[w=dXoQ1(4 Mr |,($CZ_Eek)|3 %~j62R u-v8eqF ) F0S$:fLZ|XA,0k4ġ,CQ0׷ƿv3ZX1^}|ت 1bXD䠑2[<Q3 6[$rngx\PafBD "e⧺qe+XEIp(RQΎw\c);8Leld$y. :}JWnZFBU:ӓn\5_v4M=׿f+ܺx(nbuq;wVzTt$Tl+o^_M#o-qd%=jlR2O+h%u G L[vk~4`ᔝoc1Ւ-,귑̀0_}fc&`G=߹{+Vf;,Rn`t%ξt8ƹ lWbYy;?P9AT`N=hO de^ɥu{[Y^ ?˹>NGe}۷w9ѐ9y歗}GowsDʭ;Օn䓞Sd M[}}6}r^ԁbBkRakOk.K EcƕjaxtgfpdU`#Mwvd~ usF8bWCrw[vǀpӗ-CGtuvCD3zЖ^vI%wǀk%M}t'jgkNTpDD7SURvN}*{rqr~Psr&?9I_vV[t`Gi-vE#FWxAd6xXZU,^r8FhK-xjIS@*})htm5n Ո:~:uxv(l3'|K(QBRG. |5Xvu-bg90\q'}⊁"KHy aEX08{1VrasVdF-C[]Ha(#HiHXȅ[ 9m W/kWx{6`Nvr8hOhWvy4ǒI|冔J8bjȃo(j6OXhWw~W#d8EI9/Z@icAi)1$كK)vkU7("wsԅ$xĕu) 'ROR[EnYjlEVh.ʸG|V7lWԘAIɈ4َGG!6I@n)pٖwtymcxٌWUJUO(pIjsX3g sɛo/739Ȗəwm9wמډ!GJ}XlIٜgՂY? 艚~ަ-C8!TOaع(ƔJٛd4z٠I~JYYHw|_ yQ4k !~,z#f^ĂPb=yz:bQfhueʁX,*x`LZ?؀k V&aBi*è/z嘝`q:\r *QZ{Ĵfڨҩ*ɩJQQ&mʪ (ڪ**ڨJxZlšĊ:Aʬ٬ *zՊ٪Dq**J 窮ʮ ک J*jʫʯꯀKkѭ[ ˰ s*kK+y+%k';i$-֚/l,+5k7kH4=k?&<+Ek}G{=DMOL+UkW[T]d_\+ek;gdm&o+uk/wt}v|+ks[lx+kK2[+k 뺫K;k˻pKျ ˼  K[ۻ˽࠽+Kk黼嫾ھ W{5K싿i[L|k  ,\c[ l"L% ({+. 1 4lö;7<:䛺= @,ĞC,FĖ[I2LčORLfUs|v6[y|' {Lȅ{Ȋ Ȉȑl2Ʌ\ɗۑɄɝ,wɂʣOQ|ʩH~ʓz"kS{_uÚljN^vY׬-Iz_lgEz<)\eq;ǎ>S}B I̙VU J҉ٛ?mXݍhSǖ]]]-s%qA-٧{F-Jc]!IVjǼjr:ڿ7a7{)]Z< Z3 ǣV=ԛDHיI [)gMr왂#tyAb,.צy`nݙ mx ބ(wt-tn9 {ȑVR#Ckd&.W~]薀&}}Pkm_?~ݑ<P3쭓0OTmX. #Jxӧg(܌\m)n(Я} X}6^QP[T:,K&Gt1lep5z]xiڒ{䉮=]AXd%X^Lwn=Cf>gD]ӣ^Q= uh:n㦾pGonm9*]^;^Y@Y.bޚv^KPx1~}~l .M&~]i~N?欻@|E gzh.$ Otn~mNUx¡B--hx;ޙ~ QLe:zRz^~,l+_+'^&e6 x.v^8 #F_=!_r/kx_\^Ž'<nCl?IdnITM՜?/b/9ďmMٱd/dH/_Nd_o4w}$US19il]1KN]L#_ݜy^Qn >gQU9&LYe֜.)*{ҞE7YF_-+n/p /1J( PRSQ2o13Qf#RoӲmt3vvkIUS7:ZzZkD{q; ӖVUXyy~n&.0CB=Q[g,:8aCդxղxeJ`μ4<3/pt3Cb+)5ؤ&ē,,*ȝ@tDM+EjNk*Ŭ0S;m$/a{ò,N=UvU?TqMHRƪM0͘]"KR|)i>ooL+PAWd m>ZV VCŗ8r#M};w\S8k}6G3X!vKeW]߄w˂& ] C@;NWCwndkvXMM`E0V\⢍F_cCyE>Z؆g&Xk^GG>M'~z%\ns6#?H|n_KQj_hKD1إm[hQ~;!C_" үcCH'2] 5XBY--6|YrHò=q |\ UD6Xʵ'LscDqk=Ĉ /EdZ͑>y#{@zjla%.{*CE?y:JbdT!#=eMb-F㒰c!I<8N[yXJ rrd{h@+ ,Ԅΰrgd*3 ǃ, ]8>̔/ݧ2; GeVtǒ%4Dq"c z5N03pFft!3ɩ"v=G8=1NB1ɆCMMgD5O Ai'GQ~Uiۜ'ҡGWz/đʢ)rjsq#JoXSyASOԤ$MN%TUJPNT[TaXZV~+):JT\ZW,Z ֓)ykL[XkZWݭu[QY ;Y^l> X0Ӡ N7;ʖUjY͟⑃Hyڋֶny[z_i+BߖUr2_mH\Zv+W঱7.k;^#tFRս|k%~_0&;` k`8 ` _ 9M!I\b8'VqyUbج)qYt%I_Xƕ7/zUHu_fu?{_^ MگvqW￦{Yw| W9o|YJy|9w??.}z_{_i>ø׽o{}?L|z?7)7NO=Ϝ~*l) yۺ͠6i I :E 딘/|ԯ0y=@IiVDt&4Є<Юg fr-ۯ)o/nPقbP_$/]Nͤ%x0|jhpw6^@_2J|H jK pX ] p{iiМL/ 3Ѕ"ˁpHipp F IP fII걀foJU"i:H1Pti@1I\.1rWJ*0vq p/jtx 7f~PZ>'hx#HGk)y1 yQ+c qf$S{GTT5JqX&`=b&h AߏƦ w Q1_' BUC3D/D6w,=%%172IHz4 2vI/CLSf^>;3#ݏFsNF7HIpK=B1AWL"*-4IJ)#7PeSJ4<44AK,Q2O]2}PyDAWD$GH U;UQK(KF\ KU=;35HoD&/5II7534qt0E5 aMn/fjb`PU sj$t/y@!M$IPsUHYh5M6+t^KY4!=KwQ}ktIC_?kZ1QZ 5$5N/Ib4NN,T]˕\bO5W1J3]XV}t]{QOvLU.3IQP>OAAb+%!6CC+ NjbshoZ\@<{sa_!<'^q-gUQ$kcgk*uShluj#.sv#6NbewjS?0nJkMPp7d,-r]N0aX?UcvfuliWreXVRLFe#q e `p3=TqQh^ɩ摛A*wur rr7PyMHA5`$I5=3ws 'r Nwywcz WoY{7=VDv_{h.wm{&aTzuS6ư[&vճ#7zn!El.kL$7}wJaR4WkܷW`\4vqS}Kyk˴oVtu]ۗ[)p9y5M[ V I'rk|R 8Jw6GAwV^m%vqoeuCcw#7 m-6C5XYYSȇ?v"srX8x{9--mm)YuCDV wUKkŶc(c~[5;]oÝ]TojjS4Ӗڛ|-vO!#!g>>x=S%W~0 oy_lqk^͇AEg?ܜ\-韞fU9V׃[Kz̓VQFw=?G]uްԋ^כ|lnXA~ M}NIv/~ܿLlGㅟ -{zi3e#Y'z!)۞?x㚾_[ E= 4c`p9KJ)fX `^c]6&.s]NխWS_\aKޡP"#ݣW`E%Nd G(h[$d'I&)!X*^p'! `rnt+4r 357r#7.ysxɺby<{},}{mw@V6) i+4ZL}~ٲ$!G~$Fp-[´#fe6tU=g?szAd͈@2biC43A ԫZUdVaf,x(Z&Wؼ1/`vi.l0ĊT;噌mUo,ofey>G.]zԪWn횱)lj>sME{!i:ٷg[ /n8ʗ3o|fYC>})u|g~oω/o<׳o_.:`O$z2vrw~ 8 x ~Dwf}  :6g&!!8"%"e_dS"pc(#=#AㅦM5N(>HFOؤUZy%Yj`] 5zwc6%%wQR[&q9'a^(u\ifme)Iy(*(g/8凟ZgR>xV\v(:*yu0)ԍ ,zZ*+zhj?A*(,J;m7,hӵjje.R{.骻nEm[:,r;I/J./ (Jp˯ ;0ZR0k1ZN1Ȋa2%|zX#21l3۬73=CTAE}4e4o44QK [[S[MYku@sZ`=67{]D6mcyR7ullwk=}sp.4߃~8 ΅38k0;^9kn9o~埋>:Nv^͡:_&;NϞ;'< 凌z>ώ?SΟ?ിs42BBR{ r 4 Ұ 4-C} ?K4$2 ?(R6i4,rO034`l#k9zt4(qɣI> c,$" ID鐌|$ I9r,$/@j̤''WP,%VFU𔬜'_)Kr8%.!Y\J#ev s1ɒeb/)M!s&6XlVM)SNn2mHjEq3@*ɐyqg?TϠg:g0 PA7ǀBiCyAEP!tX'U0~ hiC /5\G_v^ۢGKge:*9]Hy*ShtpuS{Ԫ7Qi6\KQWԬ>CE152xGYŰb4ɶ W]%m2bk(WV*ja3׾u\eZAqm U"SZJ\ wE*LCڃ-Cd2^k *'Sn_ݸ:s2^) unl @ [ z7-D]1%)RSVp]GB7^_~ `j6'WZ+1DL\N$Goo{ c8Bű x6r= 4 (֚K-/u e])L#Ry}y08ynm`4{M7'u^ȅg'AT ×N܌Z9F ԐB$4tRj'uiX ^íLΌ]kcFĔNb[w vT_0ܻ27/>=Vun-&q=.颭 4SKmyv\f|˦3{k1%nwv݋pλ,a{+85M6 |;LQ9?σ4=4Zs7'oJ  FlM[œR]3݉׼_7} FBWg̼[x[{FJ-Z4/Ҋ:/ NJܞR],>cǻ;U}t:1OdC>̟^=sO8+%QNm~<~#7W7*JENv1@~1&wTDtOݶqvgq JP\Q _`~AE,ZQEAU WeVy`E v9XS\ 6퉖u yY6 \Z-I=DGل8r-Z1!)  q~ ʈn-u`Jada .Q ΂i&K,"#m n%b/a%fb z8 H"'R-# "wb/? #1&#c"2>c?19#4VsaBQ5nr`Ai#7cqx#>8Bu*#:iHc;Σc#=#~'>#%&#@ $#A.$Tc=)$CF$L89AD^-"1Z$Fvd!drGd$I$$J$K4$L$u3ҤMdi0$Oed2P/%R622SNc)e.J%Uf%ĤV~ep#z%X(e+Ye,Z-b%[:%E\%R%7ե] %^f^%O%6%`")f`E?Z=faN&QVfʩUf8ș_jdRiZ TŭbYhNy_in%:_lB]hWm_!n6%qV&ĩSrr":'x[:` Jqљ\WgyvKnKxA' Ny&5YR &[D&}(J#5ihYjƧP^'fCiJIIghg&$}0`Z`ń^" >ht Y.SYߍrfꐅh(ui5hp:ړJb$ng,)'TF(yn~ˇ iJizF="ۙ҅]S}i6*y*lqݡa&[`Ɯҝ_=T)wӤ7#)v@jniX**t]fz|*jԪ)E' d~P6+ :N~jV+jku+Sc(ސٲ^*℩Zjh\ضbgv+ i$$,r,j)fC^R]+!` f̚BAǃlTkRfFA(.lĖOn ͂]"bu~I*Ӛe>ҩ򝮖,vݽ~jOmyq,ؾӚm6Ϫwj0f!_2+-0ʢW:)҂鮚*vܹbij>=mFwR. }k&d,Ψ>l^.d2.n.vϞk5,2/ Mn6lf/~]1\Jogᖾhm>!і.vovSͫb_,/_#oݮ/>^'ojP;p`Bpk{0{ʭgZ/6`n-]ݒn˦-pC1 $(RpqQV_p*i=.R ֫H9,,܎lҲS1n~1nNqu^&jYqߊo٫ q$! (+Xaخɞc]o$^ƒ( 5y1*۞*O+⽲4Ų,-? .":ID0+KT1J.3/s8oN1cGi/5#,2 b-lCaZAs8"?jm Ҝ97'8#."4sڬ@#$pAرRsts+_>c8WU3?f=U2W_f-10o3muCá}6#YtC˴ mt;ծf7Ftmo^t1/ผ-1GbjP2 .ƛ5Mߛc`}mWFIVJOUwdut\G X3uUJ5RZ%q!LXx\-ձm+5Us0^ 5Y/vU'V׵lyv5vc{mgurvܳ16t^NXAr1oh#?0c1 W;4nTWB7n{fJ-r*xjrf's©q-r*CI O&8-t(mfiVn N&wHoI>|pc8u- 8imL#w 7 xYŸ#jltZpnߵ[/9 CzRy_ަZlDʂG/uhUvwx9 9Ǹc_ygZC8.79uRVtQl9Vy/c5O飋1۰ʸ;7'y.8}kuKsSHgzz*rى[9' g6w1x1E c{/r;yZ;ks^;Lޱ>|߻;Wp¦};|{{M9˺C/ãG9j:+{1ﰯ|'^V#KzG<4O<ȓ| |Лϯ [{|WCw<Ş}oHReN=2/|Igz=ۛ+֗rT׼':=+K-:;ΓÒ>s~W<ލ|7Ťu3l׺[lW{tf@pL$ vQMD q}!Yfc՟kǁ1_P)x!.WsV[6>{J ox\>>4<@CDE¬A1Ʃ*73$ǖʐH͇P5HRM'3QAְB$S^ԥHU߶NW H=1\cZb&emOo[вPWEuŻwvzr:{~yҙFW8 kgq3FE\*|D4(Wf:RHrɄ8,c 86UDi&fHŏTQ"W.JSQ;)TY WptY)}cc.˲ZۂL08voҮdfw`VutnӾr&Xgʛ\ Qªi .Z,I6_e [lܹ.7i:-`=9&"/ 6"ݽ?7{M8@D~s:c-.SPJC#P' 8ӄ;Ӱ9 )\ L@WKğKq9K̹b(+ٛBʐ>CN!=|$qJB.wsFr`$L2+͓#*KEBmJ;Q pPPP+^{Yuɴ.:S y|~W;|DZ&}tuFYitP5#u+g#&2u]S}[mnwkm^8vc=3{hOG]tT~GüXs_EõECYAɞc$+:T6M\&h%I,TP<[VB=auwɁ ,1qy3΄X>iKQ,+"Q#,yEkLTF,@ xF+rgRlAfz!'y"v<ٌkvʫ'IiskaDVfsg@́V2C'4C'Ny'%t_ ,oAܶo]k܋=q\ *8id᭤9ͳ=rD;y}sv0DʷrnKMx) @Ω~ug]Z]ZI|J#:v]s^u?wwB]i"';.g|?[{wJ_lWs.v}Mzԟ9۳ z-Gw譪wFO{{_]}'\tʾ7p1IV۱5M ~z_~R8S9S Լիi?Ͼ%Q j]#< + 9z? @ s5}V 2TA ,A<CA $A[4@aA72U.B <d@D;Oc!@d"Ypy7! LBA"ߣJ'z۰ .Xٯ4+1Ŀ[Cm):72|)3|A?ZB*7dәC:S-v?ăDD@MD`@sb=/A\pGħ2ŭDVE4D3=ݐSUEHE9[\7`$V>T3;f._d4r0dBmTkTCqĴ"33j|clqtno p4sG[Gv;GYxFwlGzĻGGG{G4Gl,>R+hƊK 0l<2tO;ɕCh,Ek0,+]HKəb$F-JC;~@ʋIēʹJ]TʆdJ+J5P#dP̬@{wzKpL:{+#K?K,,̒%KT6<- L; =ˀiELGvJ;Âb?+o8+V43 S>{=2'R|KcM$*CCdcKԱDŽ D;6T+ETJ:|M$C>6$:zʥM#MT#<]H->$b)#?k`c CNϡJMOOP6* =S--O + et7:# :Z41lTL(2J=D$?zP?5ʉ+#% ŧ+!B}!:‚t%-"Wfxlfٌ̚Bj&G/k&D]ut4ybS>NdRG zMU kV, ^fŖgdÑgz[iiPp1|cl2TIEAh~.J.M_]՚5jD++L(MԒ"^F=W^e=c4E`M߮EYkZjh .g)lR8-F5ukr5GhZ=SıGЖ1PRH8o ,~Q!=`.U`a eKcmTlV'zҥ%+s˅&w3vWIlɐulÆ;"w&׽QU5_s'c_%?uv S?xoq_lφ9x$:$=&oUs&NX[Ւgtv1P#q-e kziw7NuF~F ).}p||z+}|(ݟ׭ vKxJӥ#2k/g_H~~'ؐw-G N^0v։2R 'f+ߟ*l!pH,"-l:ШtJZج6ންxL.Pzn8'_' :0%>x{}z<.6@3$#2<=J| _r[vYjf`TZFy~+;NJ0=ʿԘ?A{⽶dU]8$c!lƷ-L YDxM5IyP[G!˗a Mv oɓ )?-XcNjDC*-Ȍ-tJŇFe{jǪ!{z *ٳ@sZ2Zʝ{l! רL^M%ԦEw2kWq"N|xstfy3[V;.Ө ̊q\ᣯ;1Ueȏ'.q˶S?1y)EN]lس/o-}Zj7n kshw>{}—x^ڥ[`'`] h5 y1؛oic fNE3סW_|rԡ׽}(,b'@4\95 (axm9WE\1PF)TVIm6&[%H]9"e{zYe a::aXZix{隖b 砀TؚN \N`% ٗt禜v駠6fj(FЄVbAdI>(ºTn颟+kl*(csI4*FRmvk覫FՓ& *> >ݸؕ 7ÿk/rGzeB(i,C0,s./;9o+A(  a0`92d03ݘ* B́b!ЉVL@PZ>qy%I" 1F0L$bdEI1b8dSOגyȱ#i}0q% j:aZB9 Nt)!,E{$mŠ2433~T1y_NLY;U22k,)_IY\f4 Nȧ080.tB̝yM7Lt&'Dn3S'?eyb.ܧHiPj!\6 r2(EgZBQr'`8Q2)F[ Ŵn ze$'2y!n=iGҎX#jG2pk\N,kN:DIsD^ߊw)u.Il1x즖@c-kZMLp@sўt?aoUYpŸt)O)0šF*op\9| t!cbR!X7L>; X:rP_, znCFݤ-pXWeHw[a"<Ȇ9fkx7!_+[^8tmTehry 01S,UDse%SD sjukCdkĩEkeVMϗ uZk7#cpnWUMov ^㤥rC0|ˈ{]hy2quyc^~V;vňlS^~5v˭oL[߶Ys<}tMo|_[ z7hvf:"= M@Oġs~2\zh}d.8לV8W½t?vh;~tr<9ftAMt})w˾xI&_]Iq0oxћ/ɷ;=oyJ}dL;Lߝѱ=_Ӷi>/7n;_#`O^ίbݚ~o"}-o_ ~]^R/}yl.cv巽-g^_hCfD9qǗ|4oö`~ (y1I&~gGS}k^^g~(HWlg6fUv#FUҦ._x 5Gux}wF?G:J|{c2|w4H=gpe^Phwgvѧh(}[y\{|뷂a7{6+^v Wt!T ׃wH8tC҅(R|Kx҄{ah[b.tCVv7Uuch}xHs1776Gƕkw'vd膚-xxALƘtqD h83BM:t/X_؊vxXAX~֊oȂ,!h(rHgv7z`k]oXhoXʘ+،57C#x؍gSS3xم>GHWpz+7wt%h$uH'Y@f$ YEw؎Dґ#=/"9>7Xl{8[y_h8]vJ)WB@ٗ7؎1hxI>fAȨ}TzRfYdERWJ^I|hgbe&q{8x'Wo)8Ir=WDŘQys`4Bj/IGi!Bƍ);k)p`y%ugB}XqWSU};h()D(:6ķUUYSZ,i+yh!{y)w֚y%םՙhُЉ$Ce"Rl}gpW}Ni8fi!ZsyPQJ,mw8d4~؋4[ƘrIɖuefɖg|o$k[ZuoD0iYu`o\b*w2)7yMCU6G:,Ijj:{>|I IZWhtjP٩%9sVPt"yw2=PgXgzjbԇZhyƪcxիȟe{y,= *,ŢR4$\H6Jqm)ia&`WFfqG ze_j3*YϚ}w[DFE K<ȥvchaSZ`|pȱqc~9Y 0kK+[nr]e zYcffNtyg׷n-׆}L9}z c- ֈٞs {]ڒ=Rumi=Wٟ=۴TM5,bѦڏqf8)X]8?K Jm|]kUm]NHlҿy D߮M׍mj|,޽]6*M =~|;ښ|fN[5ZߗVN]*v%ҊH"HͱȪ@-u+bndɬVB\N„="<ܺ'{㕌b\k]~xL pε.9Go>/쩸锾9_zư5kƂY^;w mNpQǦ,%Z^뷴᛺mلIdh> ƞʎD~~~Ş4S">~"HN^~~/L?OE^ Wr O/?6^ o$>(ZȾ.*`2_+6/Q-jO1uaV{q֛wPxѓWG}{ߙN!w# LPlpAKS?;f 1 ʐ 9X QLQEJLJ.g C N^n~ͷO_o?>/~<0… xÉcI1ƍ;z|tQP$Kf i2ʕ,[RN̗4ki3Ν<{L5NP &o(ҥL:}Si#V8_ue֬d7M4vNZuDuVI܀V-K]TXWBG j_`vp\Z -c斒PAcр7k6G/˸<3u!ؼ2a-6 ݫ]7}4\ܩ_F9>*9'}k^]ۂ;'^_P[bwz wMw Z3z#`3YZz7Bܦ!$45 S}F!ϭ hb~#Ra=8\AƳdyv#cO%MRތxh~ab,9]YJŴI˖ǭ٣Ltxg/"|xf~BCWWt M 塎`RYijji§fբPβ?کjiJ&(먰 ʂB *mbݨBf$4Frn*'ƺ證)T m-Z!o-N%;5j u"o;k8.,jlWWX6ogrٲ6+ _賮3"̱ nH{=1`WRQ˩:aWk.1 qmN᝷94Lywd[*W o[$KMbgݛilD[s.]:cgt(:ů}/nCyq^@kXk.O}nNVۺlIiȂ;lk;VgH_0!>DS,=ku3Ru^/JC޺@eQ:^T J2\R2C9r"N8qy \yUpFDBS$5=}i$b W]x.4`tH9.u^kE/ee4#B26P+G-Q}["`qnb!9,fQ#El]pH%uWk KAH$#'AT@v1}!Lq+.69$1Oh>&Tdi7@krkeTGuqi0Lrsk;c2U x_"#;IWIxRs2:j)ۤʬ: 4̦&' 4RE0.:PCKRS*P2uEs^ °S)yz!&.4v˩\ؠ_8zV(`:^,`}@S0JbfAoft;3DzԒl- F) -U}_)9jP),ڶGs#s+20ūKUDv$RcK ̦ں&od籽]؍p{>0} %kvri޴L icFJWknxd̼ͯsY5s[UU*}{0^l/ti܀6鲙S6:KgLkmB6\/ aEm_k mLgU.w*@Vץ8^cp r 쁟:Ҋrჳ.3?^ \O)K0oAYet}-=ӎw0Pe)y9fX-bj`*Y7 v њ *_ 5-1'y=sf9?StmQ"77Kj9ܮS֕t;n>ٜޯŶK\ᯁkȽ6Olڿs/}ye˨ãb\">nB}cMAoyK!7Nf-R|n.hy¿u%9 -"S Qjs QO6AOX*)O"]C'}҉6w^}C+FZ3iFjWl`gm-洮gV{\YS"&MR[b:,n"3t)^OrȨE¡.58R]_S?k+좗:qo/?w,ǘ7]dž; r-W'?ϸebfTG5zېTAg. {5e}G}շ|osklEN(ķe W`vWtmkK~T3Wb2Eyu.kqSvg~X-ws)7hzCfqtʫ fȱ| dHrRʠpaa;˴<^D9g*; V<@e$lS֛O|)}K(xRٌq\Qsͧ˕*l'=zu9i[\,}v5|Ҳ:LYk8r=WN=9r&I1ڛ)R*GuV}Mod(m6IM% ~ՉC1tpV:% [gm;9}j/yPqMԔї}HXDž^*xjn^ U"8ۚZ~zӦr9ޣ}cyw/5ϽfhyWz̢{fA V,7;MlB{]l YF9?%eVqGcTz)nfyһm_], >W ]vMoM n)]sʎݠ~uM@myWn:M[BdLӊtnWrcedވjr zl3p|x4)\,ÓEE ~R};J&=j^ܿhjݩC݋}fIG"V(4'Vc|}`9OxRWi}'ԋx 8׎n ^˫;٪̨x.^lXyN!0Wu?RPGV]v^.ɞ!r9m] [^nи56w .ܶׄm mInBiW?{[_Gg?DU?{3"myy$v:bf%,Մ}U7odOݬf!TUL<?p߄]}oώ>v#Lrk\ ^#?PO޾b~ri=3A7)WXy F ɶ{k:Y9a}<Ɉ KUHUn]b<ƽ*;\UŬ4k Opei͏ /nlQjNn.23uPԫ3dQTW-4Vxٱ6o֖zwVq3t05/DǺJ||h^\79fl~!6;$(gb%hjUq!E#I4Y$62~[ɨeX4cGz6S:H&"!yHs;~А}jQ4g֘%3_QR|aSVU5j]2]Cwm{Nx vUV}'rnMq;|.y9M82L\*zlNΤ-'̮7*qK34_HӪYv"޲!ztƆ|(k̙Te_D{6(!Do<~IhDTo’ -Jr/KM7z" lTmϞ˳:ЎZtQjPhG4A.W?IIm0^! 2!E:..I'$^CS$3a|oG2L,1;˂ >s@3&]`RK>l00DR4{L-L󌲸pS!q9v"TsPNJ+/VY +˴4CDgeշx<6=y]Y$=CMyu6[8lq_|(qvW̕@lC\gq[=r,_]akXekUAQwނ 9Rƺ]TmaؿvO$uox /oLwB}缙( ғLl았"VYUBDzhk/= 5RhMS2x;19Ψ\ByFw/,- IW EDWJSӒhJ HR6ϡh97tu iS鴞8LYş~o4)D)}5(eMqZ>͘KO[V~6L_ԀQm:X%[({3ϺsEk퍲dCG^{-1 Yi'oQ) L-g HR~,a'+|Kr+̒R(e*Ҩzc/ 2'r&S2 g|b(`ʫsT𧳘#Q1a#D$ h#3P3G5J,,cNr5[0yKJ8yiR627k<;v %1ٖ:Ci6U+4r> /s726ӅȆ %*@2'@5Pq^tiah?kJ5-KdǼ3{T-=r6tE@=-qΑLA3% 3@-T9%OtѴOo[/(tOtÊ3MP4DH5+S1:s'4|DLUUG3, vVuQT7UQUES=(ϒH1ҭQ0UZ B5 Eh4A)3CjWRlt P+|R{]) TOYMSNc'Z{5IC&iuQu[et7RM &J\@?(L4"1;o 9|TO1 *sZZO3X1#16-uuQmT)R)BfVgl5iP/UO(2C`jVZbWX L&lԈ&6X3}vˣ"QqJpqU$t-.vٔ4ߋX0s6Fth9ekε#Ofkr,i=Q_x4[m8X6wwp7\?75=r]h mc6JE1e@uY[kzEPCGQOx7yz0Ur͊g+ySH ѷ2_㖜foC䞯A#)ɅuE~e)3|iV,9Ix]kl3ׯ&sPQxK}X{ "׸L9cAQ.xE+6bY{)s8lwYT؅p)=T1rX#w7M"<蠡^ZsbVXgO{͉a!9UdjՋ5XFGUEDCw0!uLNDU]k?Ct?* /m^ryyb1QXJdU},aXy TZOU_؂t{DK$`92}4i~%Λ5Z7m6)gy~pmo U+4B4'sդG%Sg:+ڄZu]9j9a3:gsvE) F uo9{:{_zw9"%>XX򙆳sL0+&}DN:Z=:U<ٙA珨oTXdي7yv>d/ؗVz ;Js3#qCXySR" VzIM?5#G5ֶk[,z]5⛍;v;y''EgP}[+&:kp1ĆKrSyW'U/;e[r99uE\Er{;1ܒMV4vIizo/\UxDhTu؁—Kć \7q?ڻ![غ9 b=&E)|;}|Hey'L.K5mOexڵn>F*h"@,ǵ{e ;Yr2ŃU}'`noQpiW:|uғV+̝H)]lz=iOGX (g|+{> ]45sؗ+c[{(Aχu]r$ۑ#eݷ=W̯n,%^Ͳ:]ڛk{X^}~>47kE}$OC}u/Fkӣ~Ҽap͞b?{>Fv~W1<9<aW}n wJĶmN w)#_{Z_ҼcpsO [!y,vv\tR_igj]hpwa7C: e=_>m[۷Y> >.?rj/z?#Y'+ۺ/3]:Czd'Dҙ E/U6r/8,3:^nk35U=WνQ{~HG^ԟDa#d$e%f&ggɠcBai"j쪭!g/p0q12q/! ,s@42Fuض5BwVx9z:{;*O3P}vvx轋! „ 2l!D̛-~ti8L".FU$ʔ*WlS l٤OD䂾W(ҤJ2m4f?82۟(lBsNNk}k,ڴjײU iW콻vW[V߀3I}0Ċ3kg ~Wd7ӕxhE7.m4Ԫr2_2( [b亡W7‡i}sƗJҧSn}Ǔ/4;+D=U>?VŃß * !XO Zx!/Q ~zX߇!8"HmM)q-"eb5f#9#/:#$Eyd*"IL:$O8d;X%Yjiޔ[z a9]g&f٦i9'uFEʙ'}Y긧z(&" #:(2Ry\/6Z)jꙒx:L!*`:kZ椷+_ ;왾K_*,2^J;jG|b-%:wڂ;.~[.u⢻..q;/[o/oj<0[pc#0j0b C<1Y^żI1Cn^2%3̍2-Em35s+͜3=7%4E 4M׀-5Uo\X[m[{dZ6K]}6 6JfvPýs}wk͐{V8.#x&C>yȏS^k>Gܹo^::^۞췏3_<_?+o?]ѫNңh==7={?>_7_?ҟ5@ r T#;O  =X0D!K 0)\! aE6|T 1?9{(lpJ0J|xA'B֑h-F ""1oeЏC( @Kbq#9QC%)SS|8X?W²Ő%hi]%/8P2o!iuT';xⳟzM'ρVƝ(A J }hIBQah$)jэJ˴'GCLR"="%zh3XhnS1/#:I,:3*hfFT4,UMMRqH򧴋*|vz gT6Y?zNzɬE-u'nM\W)YB}*{]1SֽUb*_VF6lC]=2d>d)R2V l ;-VZY[l֦'zf[!f;!(w WA:Du[[$of %p%n.XVNvZvo`y֞L`_ڷos5&vo [ŅـZ6/=zX88)\AK\(w+._vzLV8ǐ!sa{d9@(#0Cٞ)Ԛ{ZKͮ 7[k3?hfVrӬ+8#M=d۾UV,UMz>|XֻƵm])tWo^5 IfL[FknuUKr<=P=Oavi7#*W?}eOe7 ˫2oyG| Vxk}v6u}q/³pXwzoFokb|moܴ3ߴQx%#ųO==uGNċ~cUJzkgۍ̝W9ח]鄓uŽʅkyۅ5sw1^v)ۺ[?9B&ZQ'{f8dw;^-ξم}>؇>ǟô<ع ZI^W\|UAYXm_&ȅ[IU_K^ Bޥ)`yT-͚ _ޙa`R ` r]) y} !] Va]GzeM ѡn!z` *a!:a ba b ݵ0R䕠!Jbb$vb"Y"z"(\ʡTC`ӝ_x!]( r'nb!֚(@N&Z'"š.`- ٟb4>_.z)6 2b>*4*"ޢ"<#1<"F!4"*- ё-#"]̙"]#C&*BCc31z#E"2FBFQ V&mc:?}#Cv^RDb~`3TG$Jc)vJ%Q`( KR ,A_$5U&:֚ #P"aUH}>ҢU^XndDd_8R.9F 0cye%{\8 %av3LEN#D:# )&Pe]ePɢjZm &0M^qW>YjYi&~T`[O.bT&>ڥEmdL^ejJZ^$d% d-T :fUޣCf?#e.fzet"/-&y>Hѩj&foFZ_m]&zhDF ]_QrF(g}FJgcf\ u&翝^bF}'.x'|VOhVm蹥NʧGb(8rj~*d[&hҧs):Ee">4E~$HvhZg'Z(caAbQ)tg_UcvTf&{(gg#ʤV聞((R>h#F&iM!ʨ瑪^$neX q_'mi0)"ێBjjNi"_W:GuIz'Xhu!x#r*d>d5*rj5' %>]&Nkhb"llΧ_MO b2k*B)~ =\Fj~n&bdvZ轔SjhzEX&gkǛQ~ݽ%yzE*c2e#nƕZ[bkyjrkajޏljlk+ski{k&?)jx+!:iƬ̂jS`jgqvl&&6)I M>, &mYܱ;.!!iLR,Ɏ%ێ*l+]_>rj`iV-֡)in&$B`R")A(m^"Gm"ZNy"$ժB*nBFWb)lZ.VGĆF(-Bn)Zkݺc6hާR+vZ,.-2/f;Ω.n^4>+Ă^nV)J*qj,r&+2gö-BUTr:b#D+rbRgVhNdYkI 0 8l'i$Rk>pC٢*ъ0tzoru0;cXLҩgvfUp *2~׾!*pj.Y,($B5.O7^1so W0cޚKξ1i^oV:p91om+qe( /m1k5.9j*H ,nvﵲ :2V,$R/ 'rJ֤{린n9+1޻'}7 \;n6sq0'{'/;ZqŒ2\w>얬2I)f/5'/PN֪q"2>C72q[?FFS4 'c1ߪ5go4&hmG^eN.1,CsEu-^󅲝EfJ_TReun& \OuasYtM*[SOh..F4e:KBV&K*gKFhm#l7^uA2oퟖe]e5bRn%om^uAq4=S)u)vquqkY\\kFr7z3{nGd3w=_iUT7iR1_a0ZRdW6r8_N%|\f@w6fF+X f/s~sٰ.^6vmu8+x,1gv87ype17QvDwZ|.'D*;LEyLo8 o#XvSW7^3 tLh4`ysyᗿ.Mqt*y, yYy@y-J6ԙsC'ys\+x%P{zӣ' 'y{/Ӷ]vug1doar>wpMy \ϫԅVj^Vz\N}/;לp<3#83uour䶫Ag&wOkL_GR9k6h 6~ky 2OXpP.'%; <ȓ-5X{9C|_B_czR;ؼLɇ3 3qAwN;^q{=CC~s{>\szჾx'W8i:56 ?Om|G{77;c/:t+3|~ӓv;}LbNDYms{Y;{Fk@|L]n^0G4/8K_xz8dj"Hx*IQ >o$'l:+pXhgtZfox\>w|^⿍**/+D2ÇB,B-"HI&EG̡E©L OOP>VWXYZ[\]^Ւ@KaT bRdeA+,lcmHtvwxyzul#ggn8H?Y?jP"7qթG!E$YI:X 1` j&…^2Bl0ΜCSSQNZǦ.UkX*Щ2(4ZzCVak.nmn!Xu;'/G)+paȑ%}*8Z,˶2ܷ3U? 8kPY uЧ][{yn}ҋ* 7]#3.u«:sV鈧JZ';{o׋z+|6=7\* @4d?OB @ 0pC5/(E A SDp-Fy`G.D!smG>t +%mH5H,,-DE'ˎ1wSK' -s94N< 2.=7ӣ2lfOPTtե3 QL3Q碴2%}Sԓ>4)8͐=eEU)U,T\ٌ>wISu[uaaMvDWo PbM)isbiO [$[MY5HXmH]]zUs=l )vg;>; a2d0G1u0-\EJHDp :iǛ?(l|[\`Ý8> xS(j&mx9xh7Qw4\,C&y} 6~U"W= E=\39DHN}e8'D/n;( v.α]W -!IM22b#g:ĔPR~2s8ƴ$M%KG>lp&GrD8G]BT; ?:Н&6YH[">2~*T gO!PBRjQ 5HCej;yG!VUx@ժZҮzV=g0QfɘzUѼeRטUbu [@dMitDZzTBV %b{6jeA;zX rղI}gY5<Wd5˲Nzie*lv-OwCe=a-ng;YIg5LϞn*~Q|\>vHխ~KּMV2\ohdYdhTC*"a~®WÌ N6*0{7޻~uC6Or1K/7kݪ7~bwy`m`(g( a%/_qiYB @[+PU\840['M*_s 60r@rG0~s#daC@et`pMz Ӽyƫ^:qN=96kꙇujnl5M]gc։oeۚ]t;g렘fCkXCu~3j1n,iv_E#EfiHx7fo%_n(̍!8=OxߌoIs8/c}t,׊]){f*}Sϯ*kVõ6y}b)=>>3.!^ฝxqNjcַJ(lQ/g=xɻ;-H 7\Y+|T tuiiGzo҉f+s7M@U9ۯ.T\69,ky鹵uϫ}[ָ܈Ǎm{l <%]{UJ"T}^}$ky_ w /ocw,]O_t a"==;C+P8;6[ús?;. 飼%ұ l T|@>̳dSCNk㾎k4{A{@@HAƫr+0Y@@ L@P:}ʺ`> BC * \k>6?nk"5̘.0A\=#!h@#D d$#{?cC39+#-2n)D1qB*D/kBکOB>´A6 Y8[﫶R?ӡ$EX{:ϢKTt#Kҟ]4F$<:Ĵ[f =#q"ECS\>;i3CW+!ěmD)T]bۻC28>=`* {,Ơӂ"CsDss.L]Dp$;Ó/QHeaR-^48}\?Ǣ;H[:Zȕl508l(Tt@#mڟADud;&ēI(I+6*<ƞ,ZEs% 8K4ɠ TBCKoș ƴB%LF*"A|tJD0 )˹*nr5C,ň39&-)4JE ڳ/GLr)I/#DB֌ƻ3Mh)7L" KXY{w$NKмFdJ۝\ LH|tNTL樰c%S: ;g6L.=TSAbl6FmLx1ITLTMT4=Ue4TdЯl0ZT9qUYUZUB"$G!Z NΚYUTemVg}VhJ=F*VuH,$#mRPXV)$%WtMWu:4Xm_}_[:S]Uߛћ(=^_`ȅVX7>-` ` ]GEim-ܡ ^anmY.$X Uv^_-^va b!A\-1թCG'v`T˹Ub+!>=Vb]+t2V*4 >9 =pYc:c, -H`%ʩDzUbcjiVREFG&JF֋I>VU co}M1vMm=am7Tˌ3<֓MdXd4"Y&[d<_q5[^V3lM5fT5\>dd %^c6Wffj CS8G iҀ|gFe9kOy'{gh\|Vv\=n_g= ~hMh6hxοWlh;hM!g‚d~UnU^8_AExлiNFihigihNRS{(Xjh6\jRj6Jvi[IꞶjfj#iFΙF%~SvY=0i揈:ױf8dܽkd`U峗S%BxdTm&]|7EQ=jʁf.}xmVB>Tsu 5ehFmвfl~n,0&KgF uUn d)4ܖmVR6E1BԾ! z DSBfG@cκo'pS~=(=bp Yed-E , z1]-~l~b[lZI,M/_me[O=:GQoն@a B>f4] i1~a*OBkMcEkrydjmOptT-=r!Չ\B[ eZ7R1^~yL"wUem^W:ts_nrva!Vc\q=mFht<&apfdĞ3+7ȨRѨlM0۔}`Tdc=%-h xW:Dpo& HN) k8-\5)i2U!td$C~PPFGѣQӧPJ!%kzxB99`_eyMSZrelݘz+͒}j{YNqخxlo^S3k̹j9YYxOK찫BVkdć64^)͛a+GڷZlvb@{ZһD'sy^Ͼ}:㗚vc#~vXǘ@WD2XonEXIHʆڍTDgBY(!D'vXw)ہP0bAyhsx#e.)V7%Pv)+:n&덻tJW*e}YjmԚZ. u+z9Lk,ozU&{Į’ɵI\ ;LbŃVn೙e* : F GH~&}Tx υ gH8! 1}Pv'HL"e;hw2i)ˋڞ)~yd D.6GNd6ݛxvR5ny.;- .j)-X4񑐌$' B'R~<;Ő: 7ExJL-U#ֲx>GR̥.wY9Kk PU:exۥ͐Dj[<ynz/S8̃MoEJFZqNTY'2 @JPGRf#mog'怃홲dFOhNQ? JҒ(SLyIhQg)83(DyHMRyP(5QP,ZXuJz՗եWT!uhMZךĦ% %B$։Rg}dh&ӺajVJ~nlMbC_sW~*;ؿNէ;]6 U!MjWۮⳬlH(XVo{h!jѯOwVM\k궐g,;- V_i]F\ H= s]vvL̷֢]%=m5-yK+5/jywܫxY8,93 FGL|pg;_6?-W ׌x1\z&rb ֿΧmYjc1xd`sʈKEHPzzSN,VN`eE_1π&Af*]_oG.a 6_s7NrЁ֜Ϝ΍jtL?*,O kzָuJAmBLt;y]-ҭ*ƼN؜t6Mjw0Zu&Q$:n_Z٢mF~JU֎Flg٦Q1JqٺJN?%g2mܘܸ:oK;#n8!Kf=L^LNβY}{Gkb9|@ƹַu鼺 ʥ=Xu\ĎQ#]BEtkW_ֻ=)_ -+ek9,az&+Bjz[.>ϼ M{׼GO $U_ֻ/QpzH=9/f׽uއيwcO`As[[e9}cwu{?OO~wꏿ G?ʕ7XWl$ k׀V}8VXF8I؁5 8$DX$$(,hB'؂084sW&(8QxZa\H\_b?^HI g(PY8l؆P8ih(jnxxxNTixkHC8eHՇr}؈hz7ȇtvXxXXX8*z8PpXbD8bV((bV؆x`TX`TǘH~(xب?8xHcqmX"Y[t  wDϘ'x+wxhc1[DEh.f3HGrv45xHX񸐎JyæOvp Cwa's]ONG#nᦑo y(ybWA.eNd#tFRtVvhDLnf"섓TAFydfpn&t6?Lń%5[U| bnґM!sަm%g]n 6gB#Fn@8|ـejfp1n`Sg{[oL}9XGs)_YzmP5g{ hs7je gjjfjǚLgolj[8擱s)[Y0(Dh6)iy<_kŹHֹ·uyڝs)\bpZRc&{ZxJY,fPrRJ*j'MIJʣmmclW]ez᪛֩S h3:3-'Zo)Ț{(L^:TgnQqt?:תr *ʮ#vcU9vI]hWj모(w9,5O::tNIWl)kx]9jD9^$37u#"J:w<wb[pt{IJӲnʱ6/)ASJU@7[8FILGORU{X;[۵G^ a;ʪd+gi jGŶgp[%%dKvu|+zK+9믆cĸa븐[`/&^K鷢+={GCۺ$] ;[+zicX[^Vƛɻ%WK᪺Cқ7@Býx⛾DC-d˻lӣw  Z5ɿJI=lZ(ƾ˼۬Ĭewތ`,\Ҭ y,i<}yjxZ-'NU[3\`Xτ^< d͘|X,Mm0#"]L/Zѯ&m>2sLӽ;ӌҊ,>=BKF F T ʤ(b/rʺ|ԟ/,C,ܬncqO7i |Ǹ5aS8Fø9܎L:8O=8<=-Uzͩ.Mpm V~.Lm̓`N!.Lݘ*,ސ='/~8>ߖ?>>#GۜƄO$~V~Kr`b>d^f~hjlnpr>t^v~xz|~>^~舞芞>>^~阞难>p~ꨞꪾ>^~븞뺾>^~Ȟʾ>^~؞ھ>^~>^~?_ H?_ "?$_&(*,.02?4_68:<_;DOCS/SERVER/ad_100s.htm0000755000000000000000000000456611656577060011376 0ustar Supported Adapters - Server Pro/100

Supported Intel® PRO/100 Server Adapters

This driver and software are designed to operate with the following Intel® PRO/100 server adapters:

Product Name Board ID #† Controller
Intel® PRO/100+ Server Adapter 729757-xxx
710550-xxx		 82558, 82559
Intel® PRO/100 S Server Adapter 748565-xxx
748568-xxx
752438-xxx		 82550, 82550C, 82559C
Intel® PRO/100 S Dual Port Server Adapter A56831-xxx 82550

†Board ID # = A 6-digit code with a 3-digit extension; printed on barcode sticker on the front of the card.

Also see the Adapter & Driver ID Guide: http://support.intel.com/support/go/network/adapter/home.htm

Compatibility Notes

The following devices are not supported by Microsoft* Windows Vista*

  • Intel(R) PRO/100+ Dual Port Server Adapter

The following devices are not supported by Microsoft Windows Server* 2008

  • Intel® PRO/100+ Dual Port Server Adapter
  • Intel® PRO/100 S Server Adapter

Last modified on 12/30/09 3:31p Revision

DOCS/SERVER/adpins01.gif0000755000000000000000000002127411656741062011631 0ustar GIF89a!!!)))111999BBBJJJRRRZZZccckkksss{{{,H*\ȰÇPHŋ3j 2tIɓ(n @ RʜI&J >LxA͟@ 5(C <_ʴSȐ*̧XjE U_R]١><@ӪUg=iCȰbw\L8)ܾs9a xJe8.@AV _7 HHa@[$ >L6V tb```,(@C Tj9֢kn``S6ANA &")/sW* pC DlxRN@p PGZD]yY p !A4dxJ-u d<]SR=aPP`q$`ꅒA(YWuKA[PQ vސE H0eA7dIU%Ad݌1@ PjfB`^=Y@AH f#cѥ" ( !@ &P1A $=䋗b 40gALڙI$Hxg@Tl*ܸ ,i=0,DK%W D8@vd|4 ]A7A01Pa`)F Ytn*I.ċJL1 UŽj<.iTŬz d (mP@L<|UC'`sHpF)d\*xH`KV'd) A3LtwnA$p)]F~AO UG (kIPʋ@ d񀬈 .(z1X>w'HA~qhQ[;4bm9l$ dvs0B$$|T](BhOyΗJVi;+JU@)OŒlQxrSd yK2hTJ׀~@[E9|/b$bY*k^P!NRu$EZQr.ȑ(>KOv`ŋ O>joekM)kWb>jmC^`%*"ejcʖmIkR$> Ye{X|m2zζҝn50MU$*%p @ 7.Omnl6o 7ۂx@D)3%RT@R"s{X. !Ӊ,&fBpmbk۶%ƭbzdrY}h¦9 o)4p} ]O @qqf p#U*햦W:j¤݇jX,`ȁs 1^S]{pS^޶Vl\|d(qp8x:_{2mwRǬ0_o%S@\%׀zHVU$Jc@Y2_z+{78eh(2ϧLCU `Ox6te{GmdBvRax>&5^Z'|1q'UERG O DKUhSQ6y%{ "ci&Ds$w5WG49%KF}p}f 0 0vr'aQgae3C]u_\5-Q`hXBp,iw{hsv)O.d|L=BgV4-ԂSxPNBh\soWkWm&QemD^qclj!LJTi%)Tyu/]Zc* 0rpS 7'Wt[cVw;gnjU|(EqSkW,]kv3S!_,2q{6;(pN@uՇL[Yj`n,q<51l>qbkˆ؎$FӅ !)$y)7jrhy 7Eфe48B5c|=qr[F&@tу1fgUHj:C8]PirAD~c24)N8iiI7]UgӸ0 @d2H[UkVo;x4x[|Z֐zX`gd]0Qw!$0HV A8”~FN3l8hC9IDa ӝ޹0p6y ?d"s0@7/̂z){$?)!ewDBG{xԞ KpPXhzq?[wOFD֘zQ75}>LN>d 񞡁6/щVi"3BݦoiН}81JK EpQf$ az| )H'6v%kM 3P/ze4Z;EqjI)<\lD*`Qa&)OGH pi:v#"voi ;xmfz!!jzs!bftPwksm'd"YtrS8 eom@ $@R{%a1AY9xY1pUPGxgp0-<'ڭ:gAhjVjHP{噷igOZ[{yw;׶ȱp[ŬKyG{[x&X4դngHKX3vGӘ*yv$b[ۦqxXtGv4:<'vG YQu6Kʺg8{j#Z1++azQ18kWp嶰jIj'LHIr{Q0*E@)a+ji 2xˆ&7bt@U:o\krb|s;"*L$$WPP 99l*!xIt/c!7i1vhf]|b o²k8A$gxKy[T0s;fS9Y4(ћfXEr 6t/+ 2vU0^p!n^\"@K;ӻEI w/Wx9`62+,C$wi,`R gyr֥`{/f<7ؖz!ŌǡƠ쁬rӸmҲ\|d\#PpJ8][Ѐ`]Ŝ]3hyh@PmbmU} Jhv5X5yB,v02Bpj'̥;-6Jy,}#1]t-ԑ7hM7ie3Lr[Šk1ÿ<-v}UQ7֗ 6PvX +kWÑ)N~A >μg #0@IujdmͭS pJB~2<@~Fv} y = ;;DBmUV[#-"HطkN]~RU aԤk<'NNx17 탼gy mI@ .1hj uSh?5kٟ.?ѱxzsn p 4 P=hB`6<,<2ƒwG/7 _E|^MBW=co@[@2m8!+o8 F$79Ѵ:$A@P{GoI X\%3lmPU0mNnsa?I^IqIIposkW H_[?/wǭܝq"` 'ߓھ&[{1[Qā߸%`ꌿ#~kxܼoP-[ɧҲ7/9p ގh TPA0t`؁%NX bG X`ȡdC 1@PT0H8@@OA (Q 9.ŐAC \@ Oj퐁Mp aևծX Ӝ,$xmC \P`6s/VܘOǑ5\ 2ǧ  PaQneHA^1 @2\9D+ ̴0G5( -gn b"=*$ IG| =Lp3gc\ @3`r,p jR@ )ʀ`-A2 (`h39k jHIj"* "Ў,X`BMG  &Џf,pL))*?Z:3 ( `/b25ZRJ HĹؠMLETʃqң2@pЎ2q 3`Ih$@)jS*A2 ML^tAa4+tQ6X  *l=X H)5w 6p mN Vk X"h4kG6'Rċql|$ V/̣ =`*hՉKKZuqɧY hN3􃄼5yO >HOg' XGpdٲ a.":2Ie.NjɁ(oh0w>(rK[SO0v[߂t @ӽ~lӟXG-Ԭz4Ib+ 9fQl^18qP-|6icR, \SK- _,5s~/N)&q .@.JE׾4A/zjBnS Y`HD 4IuX 8(~3OB Ф[v!Ug%/]#]p+g62 Dq;C!h8*#{LEu4,81$#WՒ}sˊ0.o$=^TD6rJݫ8d2(`$TrJP/@Xf`d~ e"v3,΃ D6<3GBGz 66:[[&%iZ l4 N`ubpԖa5,pHW皳 60k*]yu @π('vy%P;k6%9ZvvAB.>^=m7K۪uŭmw _og8xhx7\7r=qxw=~lm2!}MvY%O2?5}C <0  g_p;?9==h`ށp| 8@p9Y$[oC~[V{xҀQQZ|` }@^wzT ~ P.?j xkz H3@ ;i.֡@Ha>)< aC= x~z>}(vMOe#| (u<% %[˓;X >{+멎༹VҾś _&0z` |{:{PЦ :k:4ۀ`<<2\1s rI 3`8uA\/4,i}28)CC.53lC9ԸI9CC>䫞-CA 0DD\7LKDGDӱG.DLBܴL÷Q3DO Q,ES>>===<<<;;;:::999888777666555444333222111000///...---,,,+++***)))((('''&&&%%%$$$###"""!!!  ,H*\ȰÇ#JHŋȱǏTɓ(/8e&2)c( @>@'W @'dJ( ؃'>ON(N" =-cOշ)K2{6iC7,!Hթ] R#;THg1 $& SW }Yt B imGݼx!ztDj\&fH?K%Mp-DK/O"3׳L dAM B H COPq  B _Bb"%k  }0!O9F=tQyE,`L'`'M0`C=~ t"Bh"'`~KBl'q ' 34=8H`cC6$Ag"(fhŒ3w8Q0~E (0|AiD1 pB33T87DN. MjP(f81!P`@BJ _pp5=`؅k GX %xЁ=$(3(btNJF-†'](1 r8 21e |Lh0,4l\Qk "PBH) SCNx8lAS0ctA ҄ @|LI`?kM C -`(L M0B5h)``> g X`A \U<Ā=;" P`7 Az]=I@ U,Yv<\@@qqF MVܽcT= P LWFE0F D H 1bWG/dgb( | T2c G'֐%0@!&bG`ASAFpmS vP0 ;@ A0  {  i0'!0*0 \@ 90 X@Pug w @ >P Fp 0 H bƀ-4PS@c*b=0 my$ ،(f | y s@ kF s ~@@ B >`pq 0/N` 'lcP'0G`p y *C ! e cPQހ . pb А`kPWr/30{ddpY0DYFy`-D2DO4 u <&+s/ s3*fpC9z|ٗ|-Дp4И 0YY~C`w1E٘Eٚ#Ɇ&}:I=P"Y1 ٜIΙ yy9НN0Y IIiM yp / DK`Ή޹ 3pg P ڜz  ҉ T: ":ѡz .)*3Z-Z 4ʣ=z8A*EpYaә٠ ۠B"S 12@PХD 13 _Qqʣ^Ztwzz}*vZ{*:9@y` Zsp =Л'zTJ٘颢٘Zmsʪv::1ڨYHPz؊Pp L  @ z蚮꺮P 42[z]{! kQ P v^@ %g  ?i8H{2P k  `# u dh 2`S b`\ a@n@pEp=P "`0 Ks.0`a    0RW#4.P(P@,g-v71 B{[|jrjҕR{++c@f3,p pu1piAf!n $]@rr`6P P=_ sapHJLNĖn\G%=1S0P P0L8,j \p ـK@ $`X`\Ȇ|ȈȊȋD P<0)l@ G iP } r@ l `;   r ReFI+ Mf p0 AqS +0'?` 5@OcoBb_`W6`940Ou&d^CG8m@rP<:{p*Is`}oW >@L`-l+ ]ӛu c sk g+:PY2O^|+,+P/@0|Ӧ]P-0 pQapo0 @ ?eu<^7@O7C @:@tl02P>ȆJb Qv^#9 3p` 0gP 42@Fo^@!'`G.,`q`Ub0 b  j0p5PT0M piGP[gg<4P9M΀ j @ ;P S0[yPQ Q@#3R#7#;cpai%@`sPo0F@x: A d;y- [- ߀ 0~- `-S@U ckm{$'\ j@s0` `>{cp`e!m~Ƞ `\ ~` p- *(!PH`gt` *PZF*mr j  )Ppu /@ _U] ڂ-ibߠ{ aհE5 x0?`,&8ї1  pE 2 /@ Е\7 VR 5 V %p u!P ?m b px=M 6S  P E N6Q pi\ n!4P{ qG}bc]0^0B GR$p=`=0[]1Q!0 LzOk?\.@!WiN @10АM;YЕ@0ا7!HT+1b  % / H`%pIV$\$C 1@zP.d HC%NXE0iChQ"7OF\x¢ hqc Kl0䨀7yvD!8'j Ā V!DtQS␂,$\ebhXV (dR" (@ཅK԰⟵& ?xA z d4@4@/ 2TY!MB(" F@$,(Gt "  8PJX9Aa]hg9ȩFF &YE$Y" o\Hn0S,&xOP"v4#Y*Y!EZ"c L$"fC,Ku!걆#i|P؊tO8AG&aKV@1gK8bN<f0a XB=@ iB-B syg{y %lKA-(XuqdOz^(IŊ4v"q q9(-{!!{owa8+ C;H;a 1Rnd4y#+~0eڎbj}l}w{ｄ G ד7މA?saz>{*ar fe`~ž/O_ jOcE> Zx-?/i`<9`=`=qAZ)` PHa =P<jQ:l!} BDd`I H`)29 @E ZQ9"a'DŨ!q 'X+ʱtØG=y F|4!1C$!6IN2~%IM 5)q$%xJTCl'*$&WAZ v K`GU* L_39_FS|b5A0hq@  @hd69NaR*p*xGw&˔Џ>1Q FgYL2X@,BhG=QXQ 3@K5pXT3iM! (u_\pstCj7zT&UBF:򱲓(IfU[jW/(R5VƬ `(DN .h&3ՁkeH S>AA@DbJV%BdPDUR07LcO'%v \`PZ8TcOB !mUgokP5 ?Y妔A>vt`hA{'0qH }> [Ȃ H↽2!8!,"T \$ m/t "'Ѓ=paûI0$AF&c q/Fqwd4YPvLX:5Ʋye*{XL,h61f(2p^-Cg#9.xSfsDD0$Z,X]h@ tC,]*̐HO#@ě/|R+dkNuNMVz̭V% %duC JP bJ{-WDL"P" 1iSH-u)QDnv>H"#(ڶ}K "+moODn|c PT_@$А5`O$`E @;u9cD^P(F` B0!`F׼Cy;5o 0PLod@#"K4o^:<.@)BN([ '2JȽ(WXn  }{D& G[>Cy<" 5o?o(V8=%  mB 9B0 !d`'~񍿁 =CrF(Bӧ~ 4ػ @}x'~NW3p3 ,=!;zhi}vh/qlbX@d`>GpOh/@fx8b9"KHW-X@`d*`@`h` o( Wp P/p: MH9ȅ 0ac+ЀUckv_ȃ 1H 8fXCh,0_(EX%xfB˄樊-<I0 A1b0 3-M@w9Oh;hhp(N76oovoz贔TI%)$IJUpu+J.U׿Z贔TI%)$IJU1?1!mĸԭ_Krq-}ֹ֒-s}*}/$G?$n6BOW?׿ZΞZzm#>h,ol>vo,* zՏ %?TI%)$IJYpofE,k\5ꩯMUmoi)6lFٿґ繍'ILmTz--peW0?ucݶ6U~S5ٳoC7~鿙"װmngB?Ig/6oٽoWwӝ?C$TI%)$IJ^s3Y0Ǡ8d?_o0KK^=S5^s+iD>K~[oYWS}G3ͣg/?/^r;փN~_ֽ+/@h.}i=_/$TI%)$IJXd8~5NȲhk,{IcUC޶j92l>Z3=rϳ#v07MjYj*ɰ1{Zm{XZǹw7kgK/{ETI%)$IJU]Oj%NZ{=&}=;J] x0p GrJkM8QXls2D_1OYN^G6G_gӿ Yf19ǐGo()8BIMKPuKPuKPuMbNmGOm_SPu6SPu6SPu6TAܖ/RmP+wwP+ڪP+ڪP+ڪQ:6Q:6Q:6OAKOAKOAKNffMUUL68BIM XICC_PROFILE HLinomntrRGB XYZ  1acspMSFTIEC sRGB-HP cprtP3desclwtptbkptrXYZgXYZ,bXYZ@dmndTpdmddvuedLview$lumimeas $tech0 rTRC< gTRC< bTRC< textCopyright (c) 1998 Hewlett-Packard CompanydescsRGB IEC61966-2.1sRGB IEC61966-2.1XYZ QXYZ XYZ o8XYZ bXYZ $descIEC http://www.iec.chIEC http://www.iec.chdesc.IEC 61966-2.1 Default RGB colour space - sRGB.IEC 61966-2.1 Default RGB colour space - sRGBdesc,Reference Viewing Condition in IEC61966-2.1,Reference Viewing Condition in IEC61966-2.1view_. \XYZ L VPWmeassig CRT curv #(-27;@EJOTY^chmrw| %+28>ELRY`gnu| &/8AKT]gqz !-8COZfr~ -;HUcq~ +:IXgw'7HYj{+=Oat 2FZn  % : O d y  ' = T j " 9 Q i  * C \ u & @ Z t .Id %A^z &Ca~1Om&Ed#Cc'Ij4Vx&IlAe@e Ek*Qw;c*R{Gp@j>i  A l !!H!u!!!"'"U"""# #8#f###$$M$|$$% %8%h%%%&'&W&&&''I'z''( (?(q(())8)k))**5*h**++6+i++,,9,n,,- -A-v--..L.../$/Z///050l0011J1112*2c223 3F3334+4e4455M555676r667$7`7788P8899B999:6:t::;-;k;;<' >`>>?!?a??@#@d@@A)AjAAB0BrBBC:C}CDDGDDEEUEEF"FgFFG5G{GHHKHHIIcIIJ7J}JK KSKKL*LrLMMJMMN%NnNOOIOOP'PqPQQPQQR1R|RSS_SSTBTTU(UuUVV\VVWDWWX/X}XYYiYZZVZZ[E[[\5\\]']x]^^l^__a_``W``aOaabIbbcCccd@dde=eef=ffg=ggh?hhiCiijHjjkOkklWlmm`mnnknooxop+ppq:qqrKrss]sttptu(uuv>vvwVwxxnxy*yyzFz{{c{|!||}A}~~b~#G k͂0WGrׇ;iΉ3dʋ0cʍ1fΏ6n֑?zM _ɖ4 uL$h՛BdҞ@iءG&vVǥ8nRĩ7u\ЭD-u`ֲK³8%yhYѹJº;.! zpg_XQKFAǿ=ȼ:ɹ8ʷ6˶5̵5͵6ζ7ϸ9к<Ѿ?DINU\dlvۀ܊ݖޢ)߯6DScs 2F[p(@Xr4Pm8Ww)Km&File written by Adobe Photoshop 5.2Adobed@     u!"1A2# QBa$3Rqb%C&4r 5'S6DTsEF7Gc(UVWdte)8fu*9:HIJXYZghijvwxyzm!1"AQ2aqB#Rb3 $Cr4%ScD&5T6Ed' sFtUeuV7)(GWf8vgwHXhx9IYiy*:JZjz ?ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^+Hyuר3.}b#g6Y3TTPfoŷ&k"JS 6^/uZ82o=,}|TT:ٱzڝӎck ϓPmLIEN^C;KgWخT9ݝYƚ ven|N'bt$y R%}Cߺ@Nb{۪Lg^T[ Ovz ɹDi?evu|nգ y馬* _uW|;} FH_'7?O~{ߺ_ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^vYޒjnN'EFcwIMՔ3xh*6~X`pK[ߺPv^2Y:$J<,KIQe,OSp$."}u7ߺEi\=Wuߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺUП>][3/1nϧL?aH1ΎRQE "{^V=q{svvSaC1Z:HcE,n;3fbOJ~{ߺ^}sU{ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkɌ'{K{{^׺uӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkɌ'{K{{^׺uӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkɌ'{K{{^׺uӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺHK__Ut+#ۻ?،)ޙ홖~?5bquy)H皦8؆i u/~b<|)woUv3:/֥uungCV?;A)Tː#W{[.cۏwn̏i溪g֮>OܹV57*>̫o(ޓ-Q4U3GM=׺?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺZ4o)]uZu&/odq3m\%Fou]!_GwOz^ߏ!jOToՇSC`r\ LZ{lmI/hWAOZ|Ì`ϒ?#~Fm~;zkx{?(wGm12}79"`ţ^OU|}o_*߿${-w?.],vDws#wxd((0{]WLdLD2u{_xݡ,5F}w}nWeٹ? K]nʩ}{L@Ԇ5Ћ4. ߺ_ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+/q^^/' &o:\t=)O)*$Se6vUm2sEc+&uUsYo7acv;l}= LmR1Tߑ}r #@LeT[ߺGߺEi\=Wuߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEG%eHjk騩TFsMQ)ift<ʨg`~J˷19+2+CK@QQO@Qnӑg|}|'.=ݝ[bki:AWI' 6ڔ]>2z>3|Mko1K_/Wlx9)rFmDY[69˂ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺU3W}O|;')C%T2 !T2IUݸf*y*ց'u?l;m&.׵7I{{U->EES5br8-lq$r՞{^׺uӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺUsω} "Wc_]O`|QKy }&9ꯓ㜦(d֋=dk!PTaI̋ tdϖvnZ4'|UeՔ["'gn;k&^6y.Ee7Zl$Tԏ-3R2jE[9[Bve׺9om ڟ{^go~C/wrvgt]Qt[g'{p̞ݡd谕!P& RIГi\=Wuߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺZ6ߐO߉&փndz1 7} fOk3RѮ{bkkњ UT!P5Oun1>Vv_h?3=H+q{w ) stW127~{ߺ[v!_wGɏksڞ׺D9˂ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺZ8 ~,pxp;- >? gI)%AXD //^-||b-NmM)6x8u>}w%a|6r nByS{{{^n(]&ߧ'l ^4. ߺ_ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺZv)̪?~wr쪣G@׺RMͻ#+dߒ}3gT~wlGP F MC%VCici皦MPQ ׺޾SܟK{05ۓ}us?>輾i%qvT|v"M]I ( [{usU{ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺUZ"US|mY׿%~Ro({Sۙ>Mwܡ⒁$3U4jc5I;8SM'~C~t^oEN;lg*iV>&D r*udEx5?ߺ^JT_]#^t_`lMݴUx}ݱ6 ymXJ*|ХnNr|$U;#xXruWӟ/z~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺU vKۛnQ3XK{}e2O#N)1xj܎Tz/%1ퟷ2jlmpd)AEf2t41Vk%iL Tu-yZ7׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺT~juO{'dlύT=kLƟ]GVʋug"{3is;ŔFtZ@̳G迒;߿zvg6K;p]e7Yˡ7?7Wrq`{KEn ׷28)F*{nq4wkvYAwGF_ :ڱủ6l|f;Ledt׺ UE]Vk&c1tT +O]EQI5LXx#4. ߺ_ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺEkzN+){ߺFߺ^׽u~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺTؙ-S=6_olP.6&׫ܘzLU-<XR#Պ|svmn^Pdi먲e$ڴ7fN3h.Z(+rp["0ҏ{g_u.S}Ic(S1˙"B:Ѹq͒ QOM, uhǬ.n:NYܮ]GOkVs#e}[ BiqR 4J~?p_^׺ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺD<7h|K&W>7ew>Zd}|];FkqebubG&h5-7F`=s{fnJSYܛw!K_sIMPSꨫ $ =5DO#^/x׾r]{C:w.: w'O씏cE;lv6M#giR"SBOt [tyʜjt-߻s׾ﯧ{u&'OGAOMfZz*h("#^}矧=#E; ܓ;fduNiv뢂zqkRT粔(Cd#^o  _S_cH_s~ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^CAC쟛Ԙ:l}#$ԴPGMLƏ9lwH+KkW;uu{s 4-& jݯ%Lo iݤhhh.NDU{tquߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^|.ϏkwEW`ힿﺏ;*:s`Tm]ϓZ|c'%G9 İUS/C;?&CF>돿uo?YHEfc 6׺O-m'/]/{/[=es}{\&V-vqW 5*ih{tquߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^׽uՇ퇿uao~w{{^ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^׽u~{ߺ^׽uDOCS/SERVER/adptro05.jpg0000755000000000000000000004747111656741062011672 0ustar JFIFHH VPhotoshop 3.08BIMHH8BIM x8BIM8BIM 8BIM' 8BIMH/fflff/ff2Z5-8BIMp8BIM8BIM8BIM@@8BIM8BIM 5pFJFIFHHAdobed            p5"?   3!1AQa"q2B#$Rb34rC%Scs5&DTdE£t6UeuF'Vfv7GWgw5!1AQaq"2B#R3$brCScs4%&5DTdEU6teuFVfv'7GWgw ?Wk14zD˃Li,z3$L푷mqc}_'4,Bx!ٓA{eOo^Kǹ#⫋/3uI)I$JRI$_K;RUBamx·aUHkjq3]}7Ң̛}[)ȩcO+S/3uJ$/p Em%)$IJI$S|s .g^icuoZޛ{m`oNߵMd 񳲟^o0?XwX{,~K\#o;=Mu9Mŷ+/2Y]Ѫ{kw#钝On.ޠwgqt3p\=n Ue}_9[^}gȲ mw6~?RRI$I%?DfNgOӱ=3Kw3.wTƧ^`e﬚`qk*y,6E80u+h:m5_U:WQ~63k"gksIOg6S`nH|_YXZbuXʡ3MMZh}kL_i }=?TnOY/v66]Pumokm_[C3 _e~X÷2e~==Ofw[u^p0zMg_u^){n4Xx{k[zng %&GZ7}[ٷ>og$ٟi7랞I)=_tvCclA;*5;oqpf}aOkv܆іgwOLrqu ۰We;Sxߵ(Z8VbO蠟z/&klYXLoD"[LNqb虹wcْU>2-!\ >4)) w 1 KWcl=}=w&?&ʱ>~;I{_}G"X~jx!=ԻݽzY?Cu C=R+v%&ӳ; l}/3DW?ߵR#ݳ~TSl3gڲ1ekO6~qYUMYZѼ[uTWUg68[rrYH3k֐Z+c]O3^ ͨ=ή/`};>1%4>8d2zX.c}d7k\_yg{ZIJI$RI$|36磌жƽw6}M{?#1h tbH7VWzl=6V9h[2*-:czo_zY_u|Z˺;^Տc657?ާLsK VNlk7coj:YYKC[öv+))I$JRI$8BIM XICC_PROFILE HLinomntrRGB XYZ  1acspMSFTIEC sRGB-HP cprtP3desclwtptbkptrXYZgXYZ,bXYZ@dmndTpdmddvuedLview$lumimeas $tech0 rTRC< gTRC< bTRC< textCopyright (c) 1998 Hewlett-Packard CompanydescsRGB IEC61966-2.1sRGB IEC61966-2.1XYZ QXYZ XYZ o8XYZ bXYZ $descIEC http://www.iec.chIEC http://www.iec.chdesc.IEC 61966-2.1 Default RGB colour space - sRGB.IEC 61966-2.1 Default RGB colour space - sRGBdesc,Reference Viewing Condition in IEC61966-2.1,Reference Viewing Condition in IEC61966-2.1view_. \XYZ L VPWmeassig CRT curv #(-27;@EJOTY^chmrw| %+28>ELRY`gnu| &/8AKT]gqz !-8COZfr~ -;HUcq~ +:IXgw'7HYj{+=Oat 2FZn  % : O d y  ' = T j " 9 Q i  * C \ u & @ Z t .Id %A^z &Ca~1Om&Ed#Cc'Ij4Vx&IlAe@e Ek*Qw;c*R{Gp@j>i  A l !!H!u!!!"'"U"""# #8#f###$$M$|$$% %8%h%%%&'&W&&&''I'z''( (?(q(())8)k))**5*h**++6+i++,,9,n,,- -A-v--..L.../$/Z///050l0011J1112*2c223 3F3334+4e4455M555676r667$7`7788P8899B999:6:t::;-;k;;<' >`>>?!?a??@#@d@@A)AjAAB0BrBBC:C}CDDGDDEEUEEF"FgFFG5G{GHHKHHIIcIIJ7J}JK KSKKL*LrLMMJMMN%NnNOOIOOP'PqPQQPQQR1R|RSS_SSTBTTU(UuUVV\VVWDWWX/X}XYYiYZZVZZ[E[[\5\\]']x]^^l^__a_``W``aOaabIbbcCccd@dde=eef=ffg=ggh?hhiCiijHjjkOkklWlmm`mnnknooxop+ppq:qqrKrss]sttptu(uuv>vvwVwxxnxy*yyzFz{{c{|!||}A}~~b~#G k͂0WGrׇ;iΉ3dʋ0cʍ1fΏ6n֑?zM _ɖ4 uL$h՛BdҞ@iءG&vVǥ8nRĩ7u\ЭD-u`ֲK³8%yhYѹJº;.! zpg_XQKFAǿ=ȼ:ɹ8ʷ6˶5̵5͵6ζ7ϸ9к<Ѿ?DINU\dlvۀ܊ݖޢ)߯6DScs 2F[p(@Xr4Pm8Ww)KmAdobed@     u!"1A2# QBa$3Rqb%C&4r 5'S6DTsEF7Gc(UVWdte)8fu*9:HIJXYZghijvwxyzm!1"AQ2aqB#Rb3 $Cr4%ScD&5T6Ed' sFtUeuV7)(GWf8vgwHXhx9IYiy*:JZjz ?ߺX'hiD$\2f\Ou}{>ݘmwvRMK`dg%:zxD׺6y헊`W'al[$i0O&'My$B{u!];GoEϴ3=6ꭧ誣;vNPPʴm9$Ouݝڿ&w}m=!sGqڻnc6Ō>=G2f;QVCܵTk'H=׺?~{ߺ^׽u~{ߺ^׽u~{ߺ^ߺDWbs\[19FNfWcr4U)%5f>ghVHRGu{[m]W?!]$#{?u G6P7EoVmߎHh8zze)]^z=Un덇r'#&_f!ҢG.Olf,<~3Ut_LV/j`TwV]]&6`OFBe- 4CX$^+21?6Un׺5^׺u{{^׺u{{^׺u{[G7q6V?kcۯj֦3ra= x*EKnJda4Lڀ׺e!W;߸>Qvgp]=w.djr&3RAnU-`fJuY"Goߺ^׽tU~ǧOM?)gߺFߺ^׽u~{ߺ^׽u~{ߺ^׽u{wS{ߺGkߺ^׽u~_#wO ~Ѫ׽u~{ߺ^׽u~{ߺ^׽u~{wS{ߺGkߺ^׽u~_#wO ~Ѫ׽u~{ߺ^׽u~{ߺ^׽u~{wS{ߺGkߺ^׽u~_#wO ~Ѫ׽u~{ߺ^׽u~{ߺ^׽u~{wS{ߺGkߺ^׽u~_#wO ~Ѫ׽u~{ߺ^׽u~{ߺ^׽u~{wS{ߺGkߺ^׽u~_#wO ~Ѫ׽u~{ߺ^׽u~{ߺ^׽u~{wS{ߺGkߺZ6.9])|c a7nݧ+>gf[r7ݸ>?CcU!Gn '?iϡ3 >ERvޠ-6>5mv/XZZfmco-ڔKhUX1NGuK#_ :c?{>}|s.f^6 Y{;2UUXKxψ4r{~S,^϶nYn}TUPTˋ>ZؠJJ/ Ȓī(`Gu7u{{^׺u{{^׺u{{^{wS{ߺGkߺ]bTH.I'%w(gXtde.=ntߍ_{ 5KQE ]*!4OuUe0_AmٿOQzs3sۘH)]SQ{%~?%(]{wS}tju~{ߺ^׽u~{ߺ^׽u~{ߺ_{wS{ߺGkߺZ:o_+7̧ݝ{FcIG..m̏zCG"%$ո>T''ʿG#_|۽oEmݓgʹñr}rqY 6ʭ_σ`Wϓ#U&`V#K̮8=~N:؋UH$cQ6>{Ϙ)/-jh([wO+q_/zbM2'g T{ld $r"R'{׽u~{ߺ^׽u~{ߺ^׽u~{wS{ߺGkߺZ7oU'x2nmA?VȼE>?32ԩQ-nlOұꖦ$>k>vEWv龲)y;qu5{W-K4oTTz-,V>84 S2R{ty1?ϖz_gOSе{Cۻk|^ݥ.jE흣dWvFHҊml){{^׺u{{^׺u{{^׺zl)>%wBvmWcQlӁOQjˋ pm:|naFQM=׺$ %aX8ޔ/Br)Y' &Z5SE4buKzˮ7P݋]dt9LcSC_G8 قRjy%DG_u$?#_ ׺`=}NV#=9eiU;5D ?6"v_׹Ȟ%./ :εn*2G9biX!8f{+21?7|T~~{ߺ^׽u~{ߺ^׽u~{ߺ^{wS{ߺU/m򻮺7>ϲ@e}SX~S˼Hw^l_B"3'5ȫ>U#s=odT_ {V:oz̹ڭAIH0"VUUKhe߯'=Ǯ~zzsljmv)YjO\M62 PVBuxrlue&*'ÍՏI/{'QUӿb>EWw!o՟:@Qɕ@I(~ ]T /[;{^׺u{{^׺u{{^׺u{wS{ߺDWu_}}o~3uV{۸˻cO]'1{nqޭߵyꊚ4LJ5Dȋ G{oS+#7tu*͗cVS񄂤}ACHԟ0Oa65w}}=tns5%vQjXlam_;OYc i|n6 fY )GI^G?$5]oϤ2{/U|&;h|7Fȝ[L!i8ẙd#* {u^׺u{{^׺u{{^׺u{{wS{ߺZ‘t?c' u׽u';o~nmwwp U}O~PGY{*~.Z<~Z$٘b,M$K-ϝc/eXGy&_]/UyZZ=-oپcQ *г)e>l[f}ۿ[bld{>>vNw;üq?ޠdҳTCAG ,1{t??jU{^?~-3uWuoT9Tۇ~6d0da;f'-[J#I|Rc25h꣆B{ ['>.썫]a5n^ݴ}%޻#v.,*i$[y<~"Ӻ3~;p--iU?+;?j^ΓY(7^rmjG=.cR^?+& ٮ|g+Xw^GxM|t^vf EGale=Sұ_uW_;lߔ>Y8Ý }5Ҷ*y:GeZu.G;auf3݋7sb w[ivE[idnok:F5a]GOu׺{wS{ߺZ‘t_c' }u׽tp}omU,Kj.E#5tJmE-R(qgdS^I& 2##_Q3#;7VYؖfbnI7>׺~{ߺ^׽u~{ߺ^׽u~{ߺ^{wS{ߺZŽڿνdQA?ʾ]z/lw Vߺ^դ(o>X|l?*~=G;qO^m|npfs>JFBE s)X~m[{)_ V&G Tb/A-AUSM"YGEta{}u~{ߺ^4쯟_:wb7E|s|vnzoWb15qC T>陋$h׺q_wܛ_d.xu݉[g-Vl[rV- #]U ]XƘ?ܛj|^xޚCLCذ:Ӯhhjrչu  f6:mFB=׺_;qdr!/UiSK);aTRAyHj%fog T_ߺD{:1֙^ˊM:cn:7gp/F`RBs¯tj\$kO[@{Y|`4m:}lr㲶&@cwv{G5 U=DžHQMQ E<4R7F ߺ_{wS{ߺZ;J~vwHLtߓ;ױ+7#6TounCzzwmjܾjE4VX%hؿVYWv*U%NoO 7Ϗ_=]}&́ʗ  g^c܇ϏJnYx)bz䩨xi;& Zdi$G$h8U{nc}׺#=wu[O?Dɇݻso lkܹ85yצS׺ HnV:vܞ2;?yM>dgvmܞѧHIh4n[O:;{wFWw>am~Btawf'!w]!!#THy}׺E嵷ό_*>L.N5T{w|5[~Fe))sYd1|W$" ѕ=~OWʾW:f=Pݩ<7ca-*-ĘLLBʭ{A%?V߳gTe;`?=Z֟"Nn:)w{aƛ@")՞|F7ݗn>ݫ[N;oZ&a[bn\?8t|M/i=׺5׺{wS{ߺTȿ nv7^;s-LNPbqg ,%f2+1T>S{ؿ ?2?=u /~dd{^~52_CCOYtn'?6G-|ێpe^%6|WWWT҉)ZsR(ϭW{;d|"Ŏu|WmYp=:g{7j*&閙Dl4ȍ{=u~{ߺ^5nܾosl~{sa+r4}+s1nWU5O$DJ^ӑ dcž6|ysRȱql+e03`cZRF߯JοeQu4t[2L9,. [VORnEdrMGd[o2)Yg1)q?XhߺE|{.Wwb56N͍r:Zs/IsyJ7yu}>ՆŒlTQTT?j'˫z?\z؇-}{Y}?:{6n.9^#oCg>׺A*k߳>43{G.vN뼟Pm|ZyM]b V/yjG_34Jouɗ'wNAGpvwkm/ꚲ. [ɱW<D{ .I۳SOQA{CawOc]nu;#z3&wlˍW7o%d!hKe%=׺)UO{:]/}H67]~\7Vvswfﭷߘꍉ[d=sqU/I^{wS{ߺZŒX;L}cߺ^֥4~x׽ueKuҾ׺/~{ߺ^׽u~{ߺ^׽u~{ߺ^{wS{ߺZŒX;L}cߺ^'whwc|^w'S.cvNN=%|qyHrY Hp5lfꩨ#* $l{6onw^Ź]C{3#S2:"Z\8ʪ̌ɪq M20V li/w<_ K$.ڑ лG,2exE*@*Ͽu^0]u?F뿿us<>z1)^Y uAVq&Nj!:QY ׺-~ǤrC230ۘw\lݕSWRkVy]ɚmyoS aY4Vyi*9۽;[$e鎟WQu߽ mMXo )){{K|W!w[?r dufɱs;l}1ocg65'82e*k(E {,7߿:zMY D[~.<SM1=TЮ2j#ʇ{޿crm~xC&ެNdyl8~-dkmMɑSM՛:rT9,vCE=MtiS{wS{ߺTgпʯbQF,73|˾{ugٙU]oyr9o!~-( Q˿_) =u޿RѾ${^~1|!'mΪX;7Obݻ|woM_ghq'2ck6-'hQČ!qҟ\u~@p18yp.ݿ{ 9;knaԐӰ Cyu;=MOBtEMLTOջY*'yK4ҹgf%$^-KENuGS?{.6?fQO VEV{L^`{} vA{|;Yo?t\Y5޹|&*>r|Yt*j@ߺCǿ'{og2=`av'nvFTX\v7fvޛpnbi1Tdb5,Fߺ_{wS{ߺU?'?v'/JtgDzE}_P+vg^<7q`TRoz.51K9(i+Z!0>AF5۟7+jc>K./>+uY; eqtۓ>#xced1KS\_N~`ֻS^'EF 1_Քab}k*O|><]9Sجio! PXdGQȾ׺u{{^׺u{{^׺u{{wS{ߺGkߺD_z~`zߵbw6`+(q[z1EGGY[NRj #L|`6:g̞~3[2up}~>an˸ }nu Co'O _+soN۝IL'_T믆߳/IBf2 ޡ܉Sq g{=o}|߼6nC޿}qiTФZi$x !7[6^׺u{{^׺u{{^׺u۫/q~;q=}7s)zoEqٞ:x$4,@>6||O}cdb1U벾3Nx:^rnLVVf2tdž(i0=׺:n"Hૣee<e`C?ߺ^КMlFD,U Z }3MNȱXCXB<*l"eP ׺*3":9"_5|RRxQe">4,H_Ѯ׽u~{ߺ^׽u~{ߺ^׽u~kĕ? ;S7dh6n*8j*i}Q'r~4 &o᫤ YRC_U4Y mlI=4<WUaѶ׽u~_#wO ~Ѫ׽u~{ߺ^׽u~{ߺ^׽u~{wS{ߺGkߺ@Gto,>'N GCX tM$U &x](FRߺEV{]g?qlo'[='Gש??4JyC{t;Nyl^};v 1&][f6ȩZVc<#]I#wO ~Ѫ׽u~{ߺ^׽u~{ߺ^׽u~[Nc>@tw/w&*87.8a$qP׺"{|]k8cwtwÜ#7R&tDef|n0Ǽzv:%aD4P׺S^׺u{{^׺u{{^׺uߺA_za򻇤WX|>.!er{K/E;:wwy6vʡݵ twÕ'0{1AGHV ھHG@=ܝߕ`>5ｇlpξu`;/?ڿ0}!wVﳽ2[vc;ǂt^ڶ-ht~Wg@|_^~F`;n^mlzLb>.|W!Z'F'Le?iي1#ldupNaۮ$۩V/W{{^׺u{{^׺u{{^׺DOCS/SERVER/attnew.gif0000755000000000000000000001740511656741062011515 0ustar GIF89a#dXVWsqrpnoUTUNMNzyzvuvpopnmnlkljijihifef_^_[Z[YXYWVWǮQQR||}yyzsstllmhhiddebbc^^_]]^YYZWWXUUVÿhikdeglmosuwoqs`abҟһƺ755DBBB@@PNNMKK][[ZXXvttsqqiggSRR~~}|||{{yxxutttssrqqqppnmmmllihhfeedcccbba```__]\\\[[YXXVUUrrroooZZZVVVSSSOOO,#dH/].\ȰÇ#JHŋ3jQ$FIBԱɓ(S\ɒ(H@͛8sq@̟6xIѣH1^g]H&JU~4mDկ`Êe(f(cP]˶-K8ʽ!ԭݻx7f+i#y <,_J!̸1[#GAsDZSF|ÌB̠C49BE^r҉M[b!_O\hr G#U{1\xFR'޸PÕC;cEرOdX?UCAݾ cT߁:'`~$ ߂7Its./d("F\!7A,N'>H%-Ћ0t@cd8 x$dBZŔB*A =b \*E(0ULnOY9{0r'JA{zgfQN'e'N$S>N蠝Vʖy梥FfwzI\ީ%VgBA0j# d¨p -aR1\چJd*x{ץ"zjX.Oij~꼘$)l$ itG!pK1R04|1^Feqg֐0;y|2?11-m2y16a ͹/QŸy /B ^CE#xK@Јp D '@8AI; @QBHA WhD \b SXZ'D!FIL@BT`P4 ְAyІ@.0Jb ^U8DQ@p ^D)+HH~h"^^x) e1t#hAΉa$Pc'\=5R3ֲ$ FQ(ԑfI[R'JAt#id~2Dx@ T 2(BZN(RKԏt1̪*9I) )>Xcʛ2l{6ĉ~G<=FF> X` +B}UJ@R)h2)8gd7YJQWZkuZ bwF@Վ\? nB:;`!Ax` ljUّ23,f\"FQ"'j:)M[fA@J x U#%ZZ]fX$-t!ns#ݧP6RD V@ۂ85vpa"]%D15.^Žֺ֝#XH(B/|cHI;@3"5L1z,;>/}\*_Jx!:Fm)'fOY(f)la6S9 c49ޭ^EYD )" ]cr=bE =e7tx8ƫ5\l܈? WH"6mА%Xljܲ(`; dOː2ڙRHxgO&6*8!Q@[Ce!\d];!E6GYmp. PqE^]Z:k@7E.4H%IY2oq F^YD`I;ցuݐ=8ڢaxOF!⑫>S=RW̝S2\b7YCAWQp"I0eۖZ6ضBj4BuO>a tźMX,da֔nQmup e'?Wz? Ev-1\,8'AgshHY}!Bv"6y3a:A=ԽI DbwAp*6s"|C W/H ̓6Е.8A‰);r~?) Ծ?ːKؽ" Swr5 s}@ =aȗ^yS7dB`l])Q^i&WS'·IfcX^7E Br sGg {"h_Cv d;тQt^RwkO(^,yx=_g6`0 pxzs[suvPFWu#@0Զ`ЀVlEJe# dAqܔ+8<{oU0! h eDhKTu0oBlfDLwgIP_ljEMS:\ *DDq6} }Aqv@R|iNxue4 anXwC5Qt#&N VB5悇x0hr \r6;q $%qxoOhw p|R8} D2A}wHNW_Hy ~PtpX;tsH!(Ȃ )* {,.=In3b+ 4 4~PQ(Wt6&E9|MFX}DLx7EwSА+yF9%#זq{0UC:{Pⴇ\^8hh+?.FDfeAT?2C{]6b95PE0) oH4@QIgPy9E)~w>5A}kqjHyp)y ؒi_$HK@$cAuC$q dA8jbqai 9`on@dd6i*WR7Gi^ #aY }F*YqfY6a6}E1IyR+AȵwF\a ax 3) UFYXy  zyjH4|ʣWPO7r::&^YV a 韗zVț-}zjPj >K C{z&q9ҒZL9IW0I}٪P$NqY! 3t(D#vt h>f6]YraQtɤNW"V[HUƃXA*NYD0aoG!d{qvWWGd'ʫ&gVV1f ;pI!d@1C#+C`z^\ӧ5XPNPKA~PA4疵ozNW@U/fbqWpc&:W~ [5av~atQ+VAYHl]5cHFQX))˺)&_Q[VC  aU69Q0n+JDQgXu`;) r;)re[IZ+ꋩۛdҋ{L}  KjIZBa\ (fCڷIz [EgT\> t'"TU*I*B~PD4+r+Q7Qo֨5U?Ȫn; KJL쵩 B&*o?I|37MܰkʽSfU+6s\Ekǃ|w.`a~<]<)69zRه1 [kz,qmc)|+!@~9*\ mEll[L >-lp t`ke,ޞ~JWpܵ^?r!j?* =~m r w1یT.n3T^n$X. ֞lavt>"gE>Q+{b9WSnU{Hk])VmVOCF)($0/~ e)|tC.Y_fl])DY_Gq}-rKax${B}s=SRN}R-k,zsȾB1PN:kBHpw)BJ su@|cx! \ dbBQp}v obAء[Apyl!Oے(/0ܿO7o kTZ |!B:$XA .dP;޹ӰąkXG!-IPI0YÈ+zPMAH%J(gch̞DU ŏV WF!X`r3+Ck)ōyQۗZa%(޼|Z Ɲy5R܀Tg\U8[i_U%pn]Loi̚fO*)MN(󂘟^ަVHGm&Gw_$*njn#kB#㸓C"O!렋3LHFD`400K,NDL)$lq"cȓ,&Th[#?(dQB,D!E\8+I" @@"ŏRKb2#TDL8R7Գ9CO>́Ђ<> sqPD+,$]F#Im'J+=n5AK $GPI M5!T;21+=+]I1$WjU[$O$"B+Z8_1T"E3"$q\r ]|}eUXږoB^9UZ%;w!I]YupᅧT ;, +E| vFhhI#B9eD{e59f?a):P+27v_= @>.K>6E,Ys&gCDى"H+¹^}y($) "l[OOv9b.;K.Ksc}`2(oY$}]csvc)(3([QhUCM(w5؝{cA:KvD*Gz&Â}O# }ᡫhm#Qr2[F*!S ᲮzުWE4ӓ ,#$.-+,lBPᑡWhCP(?焸"&J=`#OZm2E*f̊ b''v}_tS<2g|VAF6ʍc8QwH'>ΌZ GHoD8?6K4$8&PCd%i1j'{!)x:b'MYE$'_<1]" ]y= hU_J rD96sq~)/Q2Rh6ϦMH)~|8b3c몠Ϊ+$a%<%ϩ\bL>"esWJ. SA+PA t( њ*N@(Hzz~N%r T NSiX4:RhMuST4DDORt :B7j8 )tdIP5I TUXyGJ.raER ҡL?S@\3fBH14_STo $c< [ XFV!Xx@5G,-VAj$"e 4׼rK޺V empu[<ָBn57}tI]Y׶=pur5-xD^Ps[nN'AD Ą/qoZ"LښPڄ`rLu0 ELQw'J)DŻJ[bg -s<;DOCS/SERVER/box.gif0000755000000000000000000000074711651733270011001 0ustar GIF89aM3!,MI8ͻ`(dihlp,tmx|pH,$J8ШtJZجvz zn|NnB. LJ+^̸ǐ#KL˘3k̹ϠC;DOCS/SERVER/cable.htm0000755000000000000000000000752611656741062011307 0ustar Attach the RJ45 Network Cable

Attach the RJ45 Network Cable

Insert the twisted pair, RJ45 network cable as shown.

Use one of the following types of network cabling, depending on your adapter and the intended use: 

  • For 1000 Mbps operation (1000BaseT), use Category 5 or better (must be 4-pair wiring). Make sure you use Category 5 cable that complies with the TIA-568 wiring specification. For more information on this specification, see the Telecommunications Industry Association's website: www.tiaonline.org.

Note: To insure compliance with CISPR 24 and the EUs EN55024, devices based on the 82576 controller should be used only with CAT 5E shielded cables that are properly terminated according to the recommendations in EN50174-2.

  • For 100 Mbps operation (100BaseTX), use Category 5 wiring or better. 

  • For 10 Mbps operation (10BaseT), use Category 3 wiring or better. 

Caution: If using less than 4-pair cabling, you must manually configure the speed and duplex setting of the adapter  and the link partner. In addition, with 2- and 3-pair cabling the adapter can only achieve speeds of up to 100Mbps.

  • If you are using this adapter in a residential environment (at any speed), use Category 5 or better wiring. If the cable runs between rooms or through walls and/or ceilings, it should be plenum-rated for fire safety.

In all cases:

  • Segment length is limited to 100 meters.

  • The adapter must be connected to a compatible link partner, and may be set to auto-negotiate speed and duplex.

  • Intel® Gigabit Network Adapters using copper connections automatically accommodate either MDI or MDI-X connections. The auto-MDI-X feature of Intel Gigabit Network adapters allows you to directly connect two adapters without using a cross-over cable. 


Single-port models


Dual-port models

 

Last modified on 6/24/08 9:27a Revision

DOCS/SERVER/caut2.gif0000755000000000000000000000065011651733270011220 0ustar GIF89aՈ|ɂvpjc]xtWkhQ_\KSPDFD>:88FDDSQQ_]]xvvkjj͵!",pHH.Ĥ83`ѐqH@dg"9J8CYxA['!0!`> BH"F$D\N4yB$;DOCS/SERVER/ce.gif0000755000000000000000000000203311656741516010575 0ustar GIF87a6/,6/H@\`B >ć^QF?Qȅ&1 d.#„r&6oz1N0WL)P&{<:RLB 9hҧ6qVXU~(*SEɎU6fYmiYrFś[ujJwؽ|sE ذە|>|W0NR]\fV1 Yh˝=7Z5CMei۟QW햽y;˙VrɉN]W}\?N )/! Sɟ?zs9h,b YMYgJ+9)*N(ݨ@^2 xH{[õ+!y%]ޘ-'Rë§,(:g ꍹ(i*Lǂ6 (2,' *&$n*/|h 6ア,CY?n/(=.-T*F‰нŒ_(1=}(w%'DdFR)6ަX7q0*H^}R~m.{&dohlI:Al8t~߉"]z{W[*<-G+4]앞kgIC9˪mf.Cu(UZS@^ަbПE;HAJIjV÷ Bsޯw-J&dD*cɭa-ZHͫi&͉*w1] P(!XKT=!`JԱ4- Umgrдy;\Jt,8qnr' u xPU!ĸ#{իAHҒ=W{4)Fæ'CQ^ҫ.J (t润lHzcuG,"͌∋b3S+8DOF*GN3A~|%&4Gfh*UåWBMj WI&EJѶvh.J:i*+ث@E%|9 iqS $'Ar _ӄ36q^TZYَN^i&#&v\PmUKESі,:53Rc1$Vʇ%۟xLpJFDW $iQzDN]1W3&mF($ S% LwRx.&]3 6r8Y9e;$KLq:"!U4^Ԯz\Z%gf*VչT vb٠QjqԜl1^p@T\./58T~j%4m.C- ALylD~b_r`[K~ U( E)ȘF^[-RDZhmtTM *avsɂPا P ___X저 T2Z$@Rׇh/m_u -1Uy&VJKa.s*@B Ű&m8PVњwЬ"M{_2qՊ!?=Re8번V1H<هr "9L@* q_anOk-8/<L.q!UcJ|2zьN *b2ȷ١ڍDIxN$v q{oa^-mwKɦ"g;/ؾI-$'(GsN[H3{Qzq[g3IŽreֵTEd hnHXvɵDt(<@_/CtKѨ$scʵjͨst#i:|o!ľt"u"ܑvNC1R_fՑtO}K_m澷{k_4wLm1;ZSw 0*~AvJsV=/rcv I}G5ё$T;5ZGYVͿ^咅=SeDsF^ͩ{鋩F-b>)/mookDTy3i}ߩf>.Gw^t 鴖k#wTb7|wSǀxv"aLgsyMtwl'es+r|"QHkBX[Wzu+' v(~8~Hy~7{ٗ'v4{'tG9Ck$&$vb2yVT0fL9ӆyd|:9 !R)#G2m(k~7FDh%zUCUbs;0R7w$Sx~vj5j9hy_H;v QiΔxl؉…脌k(q1:]È$Gy'9h{S>G7y"(agxBe&yWoh!\8NgyH 2y $Ibhh"K$vEXR8y'ySd2A]asHoX[ʼnmg.ȏot 2{=.؁GtY)vo)ϸN\a6H1'WBvyD#h_CRsi)<9? ɅxDhԏsX4ؐSȶ|q}ntT~IMm#ux&+U|SsI~~3~Ib-DٝwYX&s)W"r&:4z8:yo,>@wW:r2Dl+BڤNPZml7dpJZmJY"tH:Jduǚ:JxZ$Dg奅1呤e rCN%L*nB8FW*V1Ü:y:vR7|ih4'<3k\w~2y{bwv$i;Hx1LhD8Z7;]ʩYڝ)~= Yz)Oi JY~Y{J$Ӝȩ5ׂi)vy(ʖOw&ZwڍT7})|ITwzʃyg'WฅԒVemAI.HBڦ{X8=Tٓ:)2×hvc-,ɰ>j>}Io9Hd 9v*DT/!T:ɃXX2uʗaDR]K&)HgXh׮"ٰڟIZi{ֆjOLhhv |VMӮg|ι{Wpki‰_i|cu՚|)ɛ>#@_4;  ?z}ڭ٘h7KCȐk/6á@t-CX&K9ڌ~JCړ C.sdXkP6Nf@_YnD-UdUcBKOnF45ZDd")t〮&Y2 d04>'PU+32- ݳ=2Wn=-O q/qT,[QAy#QAIE&&ڲH Uf7(TmKiE迥"gN5S9>nG2^n5x!u%6 KIRע?,R 2iEO}V'XeHHNO;} >~NS!}>1<|$KmFr2&X'.3*5&yF')/璅Z]_N3T8NO$iaLUK=D/.v(5PFYl;idkAFT-$$!*E4l2^)NhEU=/O>4FNx1s./eLBແ,QN^.=+u.iZj55kxSwQt+P:\LݧXa76i$Okr䄥B9q"G2"rZUNiK`%t|_3fcf>?dFl\ڿT~M@jS=l?SJ'F9RH 4rDRJ-]SL5męSN=}yȊSPbʂ.Qx|BU+L("ǣ(SAH2Ӄ LE!BbNJ"ܨ&r X KǴ!QX:*V֛dʕ-_ƜYfΝgF6Al) YmRhC)S)X.Ƨ=ap"a&p6,uuWMoZWB!~ըix|=G^}fݿz(߬%jd.>kϵ<$1B)1D=<+CF, >OlBWdE_1FgFo1ǔTԱCxG!$E֎D2I%dI'2J)J+2K-(.K0$L3D"Y& T5ٜΚcO N;M@BE4QE#FOGJ/TIܔ +8 3N3Q983TytՕ6,U+"eUT?_C5a`6pKaMҨ Bm'I4y51ncIb!oFƖk 9U38leR=ˮ#%LOWe'b[c)ی]AiT.ӝ)RNDN [.թO2cRT5WEI3n)ikX:VլWYպ-u%כ82HJR _oƺ2V}*"y,dU/+lؘd'vL^|FU@Mݍ!<PJھ*B0E|Zҟ@WْoQ @maZJqralKwe3G9TŽ4@UV˺Wl݁C+<wד^ oثV4! GX TtY1"\9{EW34b]Hoͤe޷J ΚFG+ScnVs)ZJDZѬOQVBTUvi˛@3QYt9-^;_HjŻ<|OXvx|XXxPg!Ybܼ"&Nʋ?1B7Ɵ}UR(M\˼Z<|8ӄdYg(cKXezbM9ypsKX]Kˇ}r`pUL^rT5MzAPȺs X܎d\0Fnjd3Fjvܡ̆+òil@O$yؙw8D4SfS mLɈTRq)FKE G, 3iW`L##yh||ɵEl8Ln22:݌(רL8,CдJ+Ǿ%=鳍 Q-%"MBtM5XNL< $QެIXk |ʈ[8L9. 5 ƙ,S(fQjAS\LGtPd үdЏ J*N`*T'RO\\R8 I|sHJ;3S]NKpM*l,Q/UǔdF"`_EA^EO(Iѡ c8CdM`EK) ר69SBEۑ`+ (T&=$HJ.]~3d\z-6Gq#iB4b3V*>66 Ə=? ҖV`)S5^ZCO ¬a1Sqzcܭ3Fi`MKn۪kb{ ?ޤ'>2eNJ`Ҽ"Tru讪]ط흽s)HP #cYv*L;츕sq#CB5 ;ѕ_ڊrȅ,q}ʀ-hΈHNXjMZj5[ Z瑓-|EJ"bNKY0NO{ 1h）S¤ y钴kCZYjm-^A =Qri =\ i kf>ki7qӜџȞQrjXR.df[N$3Չ K&]!˻,qPA&AK H̖:jk.ˈUl&l}[jݫ }}s-.@^@bFվ4Ѧ؝h@,;v6猹1 {sn sF?;ts>/+=CsBsDGHIOt)8tJǒ NtP'R7rh`[Eq\îuUCXе.XDl*Yuavrq$ f?Q̃YZv?5&/O}ZVA_svoVrOJ[PRXw~v0,CQ_3β),O( o{}78$x"WC'yS=.թbL;,Uިˑ7 SHҿτD>ݑcTb).Q !)jF`CC;B(4Lxב:3J뎘y'k3CNyJwoX>ÿaWRVQaIJ$H|82Pӎʯ+c{ѣw2o)ON x)S]C:A^=22j:yy*!)mϦXӻA9҅#0 "ǐ I7pW- /c๷bAqR tG-DR?Z)O PŃVtT~j <\#L(bҬi&Μ:g<G6IcФ&LEjHƢH=t<)ТXФśmM"$Yr jPؖd]f*׼l:#ŨL6ʕrxERX+V~! Vz>Z{ܞMe1o1_[X0ۭOaWkBs.T;dβ`D6Ktes-+9զ.9$oեGYhbA`g)mV!V=dJ VfQQKEDheB%t|& fq臊sW]fT'.hW[=apIxDPb$RNnSmz$M$E;:B5dIuD`a'@u^X\wyzDo1r}ej"%dVS}g FGMJU#ta0!pY[lI=Xot)G*!}聘%Jƒ1I Fm5 2BvN 1F(`((nl)Aށd++q;WS)N{|w][yᾧTcN8*& Q w؍tַ%VRI{5Q]6Zb1Krd8j1EQrۍ4ҼZHMuΦM6:JvVc1է*%QDC=˥f+"pmѴV#[FU\Hو|"80Z] deU16\T0-ٲB/ifd{aiMaB]Q.!\AyhM/k!{VM"m85vFVd=o7䧫7\利6pڧw0ɜပ//BEi_@R&0Cp7$4d.+i )ߤ4֛U %I2y*nZ3n~JAMyȃሀ(vOF &e$/CL:Dp45[i>D1Ec\zaM+v a rNwƙ*p!X*!;4 ŷ%!~H9*dIĈ*DB  cULPi[Ŗc=6gCS#jk٘)lO\IqvMDģ;YЁ^{RF.wDVb8ŦA$LlxK릷1t2"k1LBF DeY[&/}DuE) uXҼg51e".~k0zZpH(ƒhhcHY+}DR7/<=׈$~n:ܻ*( _6yW KFJ}D u| T&U\%Q2a78MRB"NvR #:H`^$?QITb*ut%(qnc!@N~2OV2e ]&qȊZ Hj~[& .SA)yBiqg[wvpT-[WqF/#BXZ2'HJ)e#4C-Q:6cTbV+u)CB ?F]׾.آ<2L*R`%$R;H.(fGX䯳mg8vvP!: bb MPjܾ̀7apØ DYr+G~4O:"piTX-Sŷ9KT;KG6ֹ&@`Xsӗ98c.s`o9Bsn^C^ss窥*ʒ\̓6׉}Bm`slKW5q \Ԣ43fWyg*!EQl窨kD~nq:YݭP#e( #I~-ZMp^?'??H?Os- =}_?q `_q!_m1]9`BJ BVRtYNp]ϝRh)*-CZMƨ&Am~M]E v} ՛9]>=AԐN`V|hW}I P͟4I|ANE[N>PXjpԟ ЎVQ P4ӣq ͌қp">㍔Ku5N P6Lm`[жXjGwbyӲyd!: Ǫ=uU!ڕX~iY,: V|ΒmA^%Qh!̌! aGK#8 ˻P~Hk m!TbRiNkˆ;Pq".b&φSD`M49 A[%ݓC NrcH81\ dᅫI^AMaZALuXE-*D@܆LP!]mܕʍԣeeuRFlNr\Q#$iIMW."s"VuF!}GpdJtY ԻFR IÈ/zQpv?/1Ūl&P섈CqFdBɾ԰®pIMiUi_ܯy^u-ؔVDnWPB=^I`)i ڣp(&P)>n ,hmHc UfKeeUJ`_uU] Ňj8h^HԖE&eXh`D{fƣea>qøKxfNU?ҞIi‡rHkffUn؆ urbڝ-ݦT&噎9!7W Z-1Ys7ٝH柡γ0B.l!ob mQ A4Bf&C?qyA4EWI4 1q23:3@kE4b4IJ;JS@^ *^)^G:Os^Kc`QԭhJ@[ Zc=ҮGXfU^Py /5̓- ͬn, 3JUueZtHUoM_)*PJ΀&(^-&&L5cW] vEnzPq(SbiȄ2~m^tfcv=6;-X-#]c q$Ei-MKiԟͮ !_'bvt nCfJZB7whAF QgZn̈bHB%8Ǥt7}^W~ bQ Ą+2 >RLd݊PZs}G 7mUBZkęoFxc"JiZ]wAh&)iWfDҬQ7:/NLg$(_cz n/҅ea/ڇ449 (>34-+iqeHk+y)G9Z@Yyߟ瘠yAߢOP:gV{5Y::zr[as:G=k`ϺS7:++Z;1K8?{}7BC;zg{i_Qi36w𷏻U;A;[WX{E主?4ļA{;_t; <'/<7?>X@;DOCS/SERVER/drivers.htm0000755000000000000000000000613111710273344011700 0ustar Install the Drivers

Intel Network Drivers for Microsoft* Windows* Operating Systems

Install the Drivers in Microsoft Windows

NOTE: This will update the drivers for all supported Intel® network adapters in your system.

Before installing or updating the drivers, insert your adapter(s) in the computer and plug in the network cable. When Windows discovers the new adapter, it attempts to find an acceptable Windows driver already installed with the operating system. 

If found, the driver is installed without any user intervention. If Windows cannot find the driver, the Found New Hardware Wizard window is displayed.

Regardless of whether or not Windows finds the driver, it is recommended that you follow the procedure below to install the driver. Drivers for all Intel adapters supported by this software release are installed.

  1. If you are installing drivers from the Product CD, insert the CD. If you do not have the Product CD, download drivers from the support website and transfer them to the system.

  2. If the Found New Hardware Wizard screen is displayed, click Cancel.

  3. Start the autorun located on the CD. If you downloaded the software package from the support website, the autorun automatically runs after you have extracted the files.

  4. Click Install Drivers and Software.

  5. Follow the instructions in the install wizard.

Uninstalling the Driver

These instructions uninstall the drivers for all Intel network adapters in a system.

  1. From the Control Panel, double-click Add/Remove Programs. 

  2. Select Intel(R) Network Connections Drivers.

  3. Click Add/Remove. 

  4. When the confirmation dialog displays, click OK. 

Last modified on 6/05/09 11:38a Revision

DOCS/SERVER/dupwindm.htm0000755000000000000000000001103211656741062012053 0ustar Configuring Speed and Duplex in Windows*

Set Up Speed and Duplex

In the default mode, an Intel® Network Adapter using copper connections will attempt to auto-negotiate with its link partner to determine the best setting. If the adapter cannot establish link with the link partner using auto-negotiation, you may need to manually configure the adapter and link partner to identical settings to establish link and pass packets. This should only be needed when attempting to link with an older switch that does not support auto-negotiation or one that has been forced to a specific speed or duplex mode.

CAUTION: Only experienced network administrators should force speed and duplex manually. The settings at the switch must always match the adapter settings. Adapter performance may suffer or your adapter may not operate if you configure the adapter differently from your switch.

Your link partner must match the setting you choose.

Fiber-based adapters operate only in full duplex, and only at their native speed.

Configuring Speed and Duplex in Microsoft* Windows*

By default, auto-negotiation is enabled. Change this setting only to match your link partner.

  1. Navigate to the Device Manager.
  2. Open Properties on the adapter you would like to configure.
  3. Click the Link Speed tab.
  4. Select the appropriate speed and duplex from the Speed and Duplex pull down menu.
  5. Click OK.

Intel® Gigabit Network Adapter Considerations

Per the IEEE specification, gigabit speed is available only in full-duplex.

The settings available when auto-negotiation is disabled are:

  • 10 Mbps or 100 Mbps Full duplex (requires a full duplex capable link partner set to full duplex). The adapter can send and receive packets at the same time. You must set this mode manually.

  • 10 Mbps or 100 Mbps Half duplex (requires a link partner set to half duplex). The adapter performs one operation at a time; it either sends or receives. You must set this mode manually.

  • Auto-Negotiation 1000 Mbps. The adapter only advertises gigabit speed at full duplex.

Intel® 10 Gigabit Network Adapter Considerations

Intel® 10 Gigabit adapters that support 1 gigabit speed allow you to configure the Speed setting. If this option is not present, your adapter only runs at its native speed.

If the adapter cannot establish link with the gigabit link partner using auto-negotiation, set the adapter to 1 Gbps Full duplex.

Intel 10 gigabit fiber-based adapters and SFP direct-attach devices operate only in full duplex, and only at their native speed. Multi-speed 10 gigabit SFP+ fiber modules support full duplex at 10 Gbps and 1 Gbps.

Intel® PRO/100 Network Adapter Considerations

The settings available when auto-negotiation is disabled are:

  • 10 Mbps or 100 Mbps Full duplex (requires a full duplex capable link partner set to full duplex). The adapter can send and receive packets at the same time. You must set this mode manually.

  • 10 Mbps or 100 Mbps Half duplex (requires a link partner set to half duplex). The adapter performs one operation at a time; it either sends or receives. You must set this mode manually.

Last modified on 12/30/09 3:51p Revision DOCS/SERVER/hot100.htm0000755000000000000000000000347011656577060011253 0ustar PCI Hot Plug Support

PCI Hot Plug Support

Intel® PRO/100 Server Adapters are enabled for use in selected servers equipped with Hot Plug support.

If you replace an adapter in a Hot Plug slot, do not place the removed adapter back into the same network until the server has rebooted (unless you return it to the same slot and same team as before). This prevents a conflict in having two of the same Ethernet addresses on the same network.

The system will require a reboot if you

  • Change the primary adapter designator.

  • Add a new adapter to an existing team and make the new adapter the primary adapter.

  • Remove the primary adapter from the system and replace it with a different type of adapter.

NOTE: To replace an existing SLA-teamed adapter in a Hot Plug slot, first unplug the adapter cable. When the adapter is replaced, reconnect the cable.

Last modified on 9/08/05 7:02a Revision

DOCS/SERVER/hotwin.htm0000755000000000000000000000352311656574604011550 0ustar PCI Hot Plug Support for Microsoft Windows

PCI Hot Plug Support for Microsoft* Windows* Operating Systems

Intel® network adapters are enabled for use in selected servers equipped with PCI Hot Plug support and running Microsoft* Windows* operating systems. For more information on setting up and using PCI Hot Plug support in your server, see your hardware and/or Hot Plug support documentation for details. PCI Hot Plug only works when you hot plug an identical Intel network adapter.

 

NOTES:
  • The MAC address and driver from the removed adapter will be used by the replacement adapter unless you remove the adapter from the team and add it back in. If you do not remove and restore the replacement adapter from the team, and the original adapter is used elsewhere on your network, a MAC address conflict will occur.
  • For SLA teams, ensure that the replacement NIC is a member of the team before connecting it to the switch.

 

Last modified on 9/03/07 4:49p Revision

DOCS/SERVER/hyperv.htm0000755000000000000000000002101311735070120011525 0ustar Creating Virtual NICs in Hyper-V

Microsoft* Hyper-V* Overview

Microsoft* Hyper-V* makes it possible for one or more operating systems to run simultaneously on the same physical system as virtual machines. This allows you to consolidate several servers onto one system, even if they are running different operating systems. Intel® Network Adapters work with, and within, Microsoft Hyper-V virtual machines with their standard drivers and software.

See http://www.intel.com/technology/advanced_comm/virtualization.htm for more information on using Intel Network Adapters in virtualized environments.

Using Intel® Network Adapters in a Hyper-V Environment

When a Hyper-V Virtual NIC (VNIC) interface is created in the parent partition, the VNIC takes on the MAC address of the underlying physical NIC. The same is true when a VNIC is created on a team or VLAN. Since the VNIC uses the MAC address of the underlying interface, any operation that changes the MAC address of the interface (for example, setting LAA on the interface, changing the primary adapter on a team, etc.), will cause the VNIC to lose connectivity. In order to prevent this loss of connectivity, Intel® PROSet will not allow you to change settings that change the MAC address.

Notes:

  • If Fibre Channel over Ethernet (FCoE)/Data Center Bridging (DCB) is present on the port, configuring the device in Virtual Machine Queue (VMQ) + DCB mode reduces the number of VMQs available for guest OSes.

The Virtual Machine Switch

The virtual machine switch is part of the network I/O data path. It sits between the physical NIC and the virtual machine NICs and routes packets to the correct MAC address. Enabling Virtual Machine Queue (VMQ) offloading in Intel(R) ProSet will automatically enable VMQ in the virtual machine switch. For driver-only installations, you must manually enable VMQ in the virtual machine switch.

Using ANS VLANs

If you create ANS VLANs in the parent partition, and you then create a Hyper-V Virtual NIC interface on an ANS VLAN, then the Virtual NIC interface *must* have the same VLAN ID as the ANS VLAN. Using a different VLAN ID or not setting a VLAN ID on the Virtual NIC interface will result in loss of communication on that interface.

Virtual Switches bound to an ANS VLAN will have the same MAC address as the VLAN, which will have the same address as the underlying NIC or team. If you have several VLANs bound to a team and bind a virtual switch to each VLAN, all of the virtual switches will have the same MAC address. Clustering the virtual switches together will cause a network error in Microsoft’s cluster validation tool. In some cases, ignoring this error will not impact the performance of the cluster. However, such a cluster is not supported by Microsoft. Using Device Manger to give each of the virtual switches a unique address will resolve the issue. See the Microsoft Technet article Configure MAC Address Spoofing for Virtual Network Adapters for more information.

Virtual Machine Queues (VMQ) cannot be enabled on a Hyper-V Virtual NIC interface bound to an ANS VLAN.

Using an ANS Team or VLAN as a Virtual NIC

If you want to use a team or VLAN as a virtual NIC you must follow these steps:

Note: This applies only to virtual NICs created on a team or VLAN. Virtual NICs created on a physical adapter do not require these steps.
  1. Use Intel® PROSet to create the team or VLAN.
  2. Open the Network Control Panel.
  3. Open the team or VLAN.
  4. On the General Tab, uncheck all of the protocol bindings and click OK.
  5. Create the virtual NIC. (If you check the "Allow management operating system to share the network adapter." box you can do the following step in the parent partition.)
  6. Open the Network Control Panel for the Virtual NIC.
  7. On the General Tab, check the protocol bindings that you desire.
    Note: This step is not required for the team. When the Virtual NIC is created, its protocols are correctly bound.

Command Line for Microsoft Windows Server* Core

Microsoft Windows Server* Core does not have a GUI interface. If you want to use an ANS Team or VLAN as a Virtual NIC, you must use the prosetcl.exe utility, and may need the nvspbind.exe utility, to set up the configuration. Use the prosetcl.exe utility to create the team or VLAN. See the prosetcl.txt file for installation and usage details. Use the nvspbind.exe utility to unbind the protocols on the team or VLAN. The following is an example of the steps necessary to set up the configuration.

Note: The nvspbind.exe utility is not needed in Windows Server 2008 R2.

  1. Use prosetcl.exe to create a team.
      prosetcl.exe Team_CreateTeam 1,2,3 ALB Team1
  2. Use nvspbind to get the team�s GUID
      nvspbind.exe -n
  3. Use nvspbind to disable the team�s bindings
      nvspbind.exe -d aaaaaaaa-bbbb-cccc-dddddddddddddddd *
  4. Create the virtual NIC by running a remote Hyper-V manager on a different machine. Please see Microsoft's documentation for instructions on how to do this.
  5. Use nvspbind to get the Virtual NIC�s GUID.
  6. Use nvspbind to enable protocol bindings on the Virtual NIC.
      nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_netbios
      nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_tcpip
      nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_server
     

Virtual Machine Queue Offloading

Enabling VMQ offloading increases receive and transmit performance, as the adapter hardware is able to perform these tasks faster than the operating system. Offloading also frees up CPU resources. Filtering is based on MAC and/or VLAN filters.

Teaming Considerations

  • If VMQ is not enabled for all adapters in a team, VMQ will be disabled for the team.
  • If an adapter that does not support VMQ is added to a team, VMQ will be disabled for the team.
  • Virtual NICs cannot be created on a team with Receive Load Balancing enabled. Receive Load Balancing is automatically disabled if you create a virtual NIC on a team.
  • If a team is bound to a Hyper-V virtual NIC, you cannot change the Primary or Secondary adapter.

 

Last modified on 6/01/11 2:12p Revision

DOCS/SERVER/index.htm0000755000000000000000000000102111656577060011335 0ustar Intel® PRO/100 Server Network Adapters /html> DOCS/SERVER/index_it.htm0000755000000000000000000000103511656577060012036 0ustar Intel® PRO/100 Itanium Server Network Adapters /html> DOCS/SERVER/insert.htm0000755000000000000000000000534011656741062011535 0ustar Insert the Adapter

Insert the PCI Adapter in the Computer

  1. If your computer supports PCI Hot Plug, see your computer documentation for special installation instructions.

  2. Shut down the operating system (if it's running).

  3. Turn off and unplug your computer. Then remove the cover.

    		4.

    CAUTION: Turn off and unplug the power before removing the computer's cover. Failure to do so could endanger you and may damage the adapter or computer.

  4. Remove the cover bracket from a 32-bit or 64-bit PCI (2.2 or later) bus master slot. If you have configuration problems, see your computer's documentation to determine if the PCI slots are bus master-enabled. 

  5. Insert the adapter in a compatible PCI slot. If you install a 64-bit adapter in a 32-bit slot, the adapter will still function, but the end of the edge connector will be exposed and not connected. If this is the case, make sure the exposed contacts do not touch anything that would cause an electrical problem. Push the adapter into the slot until the adapter is firmly seated. 

  6. Secure the adapter bracket with a screw, if required.

  7. Repeat steps 4 through 6 for each additional adapter to be installed.

  8. Replace the computer cover and plug in the power cord.

  9. Turn the power on and start your operating system. 
    If you get a PCI or PCI-X configuration error, select Troubleshooting in the Table of Contents.

Last modified on 4/06/06 3:42p Revision

DOCS/SERVER/insscrew.gif0000755000000000000000000001616411656741062012051 0ustar GIF89a%JHIfdeXVWsqrpnoUTUSRSNMNJIJFEF~}~zyzyxyvuvpopnmnlkljijihifefede_^_[Z[YXYDzkkmffhQQR||}yyzsstddebbcaab]]^YYZWWXVVWUUVÿuvyhikdegpqslmoȚz|~suwoqs`abҟһƺ755DBBB@@PNNOMMMKK][[ZXXvttsqqiggSRRONN~~}|||{{{zzyxxutttssrqqqpponnnmmmllihhhgggfffeedcccbbbaaa```__]\\\[[VUUrrroooZZZVVVSSSOOO,%H>{x\ȰÇ#JHŋzU CIdPmĈq#(ɗ0cʜ0ʛAɳϟy y=*]ʔd3Dشի mF&`*lC Ū]kiٲFQ%eKnEo˞qʮ߿ +v,OZĐ]+Rs#kf*3q@fnN?7,qϼv;H^ތ3U赻q̽Z, 5]~!0I|u S'!y g+D|Bt=a~gB{"`&uǐq/y\7({"?Ca,S],ą4BÁH/p[B25?Z1|4M 4'(^["+Dt2pBHƗ " S^AuixHZ䮐 3+xОE|:O⩃12dL܅) r?D*`<){!-v/:OA Kd$M>̗Xd%tfbn* 0b%& |3xL2 ,`9IM>'PE+~8A4.D1d#NID@ ܚJXBJ!?3x㙤L)bb&2"m+5&B1+&ZH}-LuLͦ &D,4U*ExjPՁš~jdD*%tF/*kV b!E0q-Zf \e*LnR&DA +e :*ģW2e"6?r!x+#d(f("N|Ib!RBzX'/>6V 4W[Bndy_ *%v1V80Q&&L^2*0Èi,C'*)"8;djE R ֱ턯Y" a>dtJ(ٞbŔD2`LA2Uhm\gSZ w(X@dO HC$pV㥰/"'X F,&7??*Pg x e; e ͐ӞNRHH=TRlZmI^xX)Wjq8MFN4x 0#LA1H2 [!_ -]sDDQ P! c"2na_2 A& *˽A *:eE0M-j wJڨiih`J Q{}f]+*AB9ʊ"`]؄݊0yjhK2D؉= jib2纊(ip D@j Sp=Q : /iAz\6` <^@ٜP {аi'K'^K7 c;fiۄ^@`;1;{ iKhY2 F{y ZSL9Z(rh[zo n`ڀLrUW2A"t~|hkKhWWc[ yy @hiiq&A*A5YqF:!U.,pqD"Pʜ,|^:å_Tl ű!PƐS[ry!F =|g%qv' ܦmgݹG1P]M!F?OBѪM#*WT]hCGeޑ,ؠw$a>й߼ Zu5qXmn1Z3 n6\7 |0@*7)j"(S1؂M()M3>2=K ],;$۾M-e/AtNNLgNs.3ϡ>>1WM旮n|饾~3>B>N.㺾 *q&`8vzm.`?\>2mp"7VEE~^z~B^cֈަҎƕ@vHBF@ o.n+4(/mFkݦnp]@R"wЩ^CN*bTW#-SH)yE"HRFa]Q wZW;U^Xa Uw'X/^wqc6{QE^[嵠(ovX@5mܩ}U[ 04/jI l-N@&pg$" ǭR'-鯠r^#a  1D."'# ] d=ѣ2QhWq"o \%CE5W$a a$XAuBC%$ƢEFyɹѣE^k"5Qb(8#)@I1zzJM9 Q;)?v VHGZ4Q%̤kUzNԄP9`iš":EX,[IzY,o،[d;OK4g08uP-Wdw ܹa㋜cjֳ嗔5ٵAMOkP +d@uG$܋CGIFsxD^H:4=xMɋQwPGzh0o^"xi͠ϵ,(X;0 BA>A>;B$J Z [dϸAŃ`i !9`.)L9B O<ܑ>⅗H"Rp jC+PR=lhKlo0)E8P-NM8CI!qdԬl8) MrЁPz;҄Z~@FR*O+ẑ3e̴0OP#BWM8]4JT֨4``I氡\57t`H%0$*P^:Џt۲$Rؤ6P6Fn5ꀶP|s fRC;PY$T Z#we(2OC`T`!Ses>3syMH;`08VHLE|aTP0 9I[Vgz`$e$2Lk$ ?:L.YV= @A Tf7~2m^*ChI.%y?13mL6M<܇i0P!z"gdfRIlFb}m/>hH8VH6ݥFj򇭢"VO{gFvH6?& ?dTI翩A}E2PO&,ա@ҏxOJ:A F\2YA NisM?6":a Q8T aqa %C X6aCC|HE`nDd@Vc-RD lb "<ЊDɳV;DOCS/SERVER/ipmi.htm0000755000000000000000000000377611656574604011210 0ustar IPMI Manageability

IPMI Manageability

Overview

The Intelligent Platform Management Interface (IPMI) allows you to monitor server physical health characteristics, such as temperature, voltage, fans, power supplies, and chassis intrusion. These monitoring capabilities provide information that enables system management, recovery and asset tracking.

IPMI and Adapter Teaming

If an adapter is TCO-enabled and connected to a Baseboard Management Controller (BMC), you can add it to any type of iANS team. However, if you add it to a Static Link Aggregation (SLA) or an IEEE 802.3ad Dynamic Link Aggregation Team the system management capabilities will be non-functional. This is due to load balancing requirements within a team and the fact that manageability traffic is restricted to a single port on a specific adapter. Also, if the adapter is connected to a BMC device that does not use a dedicated MAC address, Receive Load balancing and Adaptive Load Balancing teams will lose manageability traffic like SLA and Dynamic Link Aggregation Teams mentioned above.

IPMI and VLANs

If you are using an 82541 or 82547-based network connection and plan to configure a VLAN dedicated to IPMI manageability traffic, you must configure the IPMI-enabled port of the system and the BMC to use the same VLAN ID. If the port will pass only non-manageability traffic, you do not need to configure a VLAN on the BMC.

Last modified on 8/31/05 4:21p Revision

DOCS/SERVER/ipsecoff.htm0000755000000000000000000000345111656574604012036 0ustar IP Security Offloading

IP Security Offloading

Internet Protocol (IP) Security (IPSec) is a set of protocols used to help secure the exchange of IP data. IP Security offloading is the assignment of algorithm computations from software to hardware. Generally, CPU utilization decreases and network performance increases when offloading takes place.

On Intel devices that support IPSec offloading features, you can configure those features through Intel® PROSet. For more information, select Intel PROSet in the Table of Contents (left pane) of this window.

NOTE:  Large Send Offload (LSO) and IPSec Offload are not compatible. LSO is automatically disabled when IPSec Offload is enabled. This may reduce the performance of non-IPSec traffic. Confining all of your IPSec traffic to one port and enabling IPSec Offload only on that port may mitigate this issue.

 

Last modified on 8/28/08 3:57p Revision

DOCS/SERVER/jumbo_dm.htm0000755000000000000000000001363011656574604012034 0ustar Jumbo Frames

Jumbo Frames

Jumbo frames are Ethernet frames that are larger than 1518 bytes. You can use Jumbo Frames to reduce server CPU utilization and increase throughput. However, additional latency may be introduced. 

NOTES:

  • Jumbo Frames are supported at 1000 Mbps and 10Gbps. Using Jumbo Frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.

  • End-to-end network hardware must support this capability; otherwise, packets will be dropped.

Jumbo Frames can be implemented simultaneously with VLANs and teaming.

To configure Jumbo Frames at the switch, consult your network administrator or switch user's guide.

Restrictions:

  • Jumbo frames are not supported in multi-vendor team configurations.

  • Supported protocols are limited to IP (TCP, UDP).

  • Jumbo frames require compatible switch connections that forward Jumbo Frames. Contact your switch vendor for more information.

  • When standard sized Ethernet frames (64 to 1518 bytes) are used, there is no benefit to configuring Jumbo Frames.

  • The Jumbo Frames setting on the switch must be set to at least 8 bytes larger than the adapter setting for Microsoft* Windows* operating systems, and at least 22 bytes larger for all other operating systems.

  • The Intel® PRO/1000 PL Network Connection supports jumbo frames in Microsoft* Windows* operating systems only when Intel® PROSet for Windows Device Manager is installed.

  • The following devices do not support jumbo frames larger than 4096 bytes:

    • Intel® 82577LM Gigabit Network Connection

    • Intel® 82578DM Gigabit Network Connection.

  • The following devices do not support jumbo frames:

    • Intel® 82567V-4 Gigabit Network Connection
    • Intel® 82578DC Gigabit Network Connection
    • Intel® 82577LC Gigabit Network Connection
    • Intel® 82567LF-3 Gigabit Network Connection
    • Intel® 82567V-2 Gigabit Network Connection
    • Intel® 82567LF-2 Gigabit Network Connection
    • Intel® 82567V Gigabit Network Connection
    • Intel® 82567LF Gigabit Network Connection
    • Intel® PRO/1000 Gigabit Server Adapter
    • Intel® PRO/1000 PM Network Connection
    • Intel® PRO/1000 PM Network Connection
    • Intel® 82562V 10/100 Network Connection
    • Intel® 82562GT 10/100 Network Connection
    • Intel® 82566DM Gigabit Network Connection
    • Intel® 82566DC Gigabit Network Connection
    • Intel® 82566DC-2 Gigabit Network Connection
    • Intel® 82562V-2 10/100 Gigabit Network Connection
    • Intel® 82562G-2 10/100 Gigabit Network Connection
    • Intel® 82562GT-2 10/100 Gigabit Network Connection
    • Intel® 82552 10/100 Network Connection

Setting Up Jumbo Frames in Microsoft* Windows*

NOTE: Jumbo frames are not supported in multi-vendor team configurations.

  1. Open Microsoft* Windows* Device Manager.

  2. Open Properties on your adapter.

  3. Click the Advanced tab.

  4. Select Jumbo Frames from the list of advanced features.

  5. Set your desired packet size (based on network capability).

  6. Click OK to apply the changes. 

All equipment on the network must also support the larger frame size. When setting up Jumbo Frames on other network devices, be aware that different network devices calculate Jumbo Frame size differently. Some devices include the header information in the frame size while others do not. Intel adapters do not include header information in the frame size. When configuring Jumbo Frames on a switch, set the frame size four bytes higher for CRC, plus four bytes if you are using VLANs or QoS packet tagging.

Last modified on 8/01/11 3:59p Revision

DOCS/SERVER/lbracket.htm0000755000000000000000000000424111656741062012017 0ustar Attach the Low-Profile Bracket

Attaching the Low Profile Bracket (Optional)

Some adapter models come with a small bracket in the product package, to be used in a low profile slot. If you need to install the adapter in a low-profile slot, follow these instructions. 

  1. Before handling the adapter, ground yourself to dissipate any static charge.

  2. Remove the two screws securing the standard bracket to the back side of the adapter.

  1. Slide the bracket away from the adapter.

  1. Slide the low profile bracket onto the adapter.

  1. Attach the low profile bracket to the adapter using the screws you removed in step 2.

  1. Carefully tighten the screws until they are seated. Do not over tighten.

You may re-attach the standard sized bracket in the future if necessary. 

Last modified on 8/31/05 3:41p Revision

DOCS/SERVER/legaldis.htm0000755000000000000000000000205611701323454012006 0ustar Legal Information

Copyright and Legal Disclaimers

Copyright © 2002 - 2012 Intel Corporation. All rights reserved.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein.

Intel, Itanium, and Pentium are trademarks of Intel Corporation in the U.S. and other countries.

*Other names and brands may be claimed as the property of others.

Warranty Information

Software License

 

Last modified on 1/25/11 10:21p Revision DOCS/SERVER/license.htm0000755000000000000000000003527311654245266011666 0ustar Software License

INTEL SOFTWARE LICENSE AGREEMENT

IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.

Do not copy, install, or use this software and any associated materials (collectively, the “Software”) provided under this license agreement (“Agreement”) until you have carefully read the following terms and conditions.

By copying, installing, or otherwise using the Software, you agree to be bound by the terms of this Agreement. If you do not agree to the terms of this Agreement, do not copy, install, or use the Software.

LICENSES:

Please Note:

  • If you are a network or system administrator, the “Site License” below shall apply to you.
  • If you are an end user, the “Single User License” shall apply to you.
  • If you are an original equipment manufacturer (OEM), the “OEM License” shall apply to you.

SITE LICENSE: You may copy the Software onto your organization’s computers for your organization’s use, and you may make a reasonable number of back-up copies of the Software, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual ("emulated") devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

SINGLE USER LICENSE: You may copy the Software onto a single computer for your personal use, and you may make one back-up copy of the Software, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual (“emulated”) devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

OEM LICENSE: You may reproduce and distribute the Software only as an integral part of or incorporated in your product, as a standalone Software maintenance update for existing end users of your products, excluding any other standalone products, or as a component of a larger Software distribution, including but not limited to the distribution of an installation image or a Guest Virtual Machine image, subject to these conditions:

  1. This Software is licensed for use only in conjunction with (a) physical Intel component products, and (b) virtual (“emulated”) devices designed to appear as Intel component products to a Guest operating system running within the context of a virtual machine. Any other use of the Software, including but not limited to use with non-Intel component products, is not licensed hereunder.
  2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Materials.
  3. You may not copy, modify, rent, sell, distribute or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
  4. You may not reverse engineer, decompile, or disassemble the Software.
  5. You may only distribute the Software to your customers pursuant to a written license agreement. Such license agreement may be a "break-the-seal" license agreement. At a minimum such license shall safeguard Intel's ownership rights to the Software.
  6. The Software may include portions offered on terms in addition to those set out here, as set out in a license accompanying those portions.

LICENSE RESTRICTIONS. You may NOT: (i) use or copy the Materials except as provided in this Agreement; (ii) rent or lease the Materials to any third party; (iii) assign this Agreement or transfer the Materials without the express written consent of Intel; (iv) modify, adapt, or translate the Materials in whole or in part except as provided in this Agreement; (v) reverse engineer, decompile, or disassemble the Materials; (vi) attempt to modify or tamper with the normal function of a license manager that regulates usage of the Materials; (vii) distribute, sublicense or transfer the Source Code form of any components of the Materials, Redistributables and Sample Source and derivatives thereof to any third party except as provided in this Agreement.

NO OTHER RIGHTS. No rights or licenses are granted by Intel to you, expressly or by implication, with respect to any proprietary information or patent, copyright, mask work, trademark, trade secret, or other intellectual property right owned or controlled by Intel, except as expressly provided in this Agreement. Except as expressly provided herein, no license or right is granted to you directly or by implication, inducement, estoppel, or otherwise. Specifically, Intel grants no express or implied right to you under Intel patents, copyrights, trademarks, or other intellectual property rights.

OWNERSHIP OF SOFTWARE AND COPYRIGHTS. The Software is licensed, not sold. Title to all copies of the Software remains with Intel. The Software is copyrighted and protected by the laws of the United States and other countries and international treaty provisions. You may not remove any copyright notices from the Software. You agree to prevent any unauthorized copying of the Software. Intel may make changes to the Software, or to items referenced therein, at any time without notice, but is not obligated to support or update the Software. You may transfer the Software only if the recipient agrees to be fully bound by these terms and if you retain no copies of the Software.

ADDITIONAL TERMS FOR PRE-RELEASE SOFTWARE. If the Software you are installing or using under this Agreement is pre-commercial release or is labeled or otherwise represented as “alpha-“ or “beta-“ versions of the Software ("pre-release Software"), then the following terms apply.

To the extent that any provision in this Section conflicts with any other term(s) or condition(s) in this Agreement with respect to pre-release Software, this Section shall supersede the other term(s) or condition(s), but only to the extent necessary to resolve the conflict.
You understand and acknowledge that the Software is pre-release Software, does not represent the final Software from Intel, and may contain errors and other problems that could cause data loss, system failures, or other errors. The pre-release Software is provided to you "as-is" and Intel disclaims any warranty or liability to you for any damages that arise out of the use of the pre-release Software.
You acknowledge that Intel has not promised that pre-release Software will be released in the future, that Intel has no express or implied obligation to you to release the pre-release Software and that Intel may not introduce Software that is compatible with the pre-release Software. You acknowledge that the entirety of any research or development you perform that is related to the pre-release Software or to any product making use of or associated with the pre-release Software is done at your own risk.
If Intel has provided you with pre-release Software pursuant to a separate written agreement, your use of the pre-release Software is also governed by such agreement.

LIMITED MEDIA WARRANTY. If the Software has been delivered by Intel on physical media, Intel warrants the media to be free from material physical defects for a period of ninety days after delivery by Intel. If such a defect is found, return the media to Intel for replacement or alternate delivery of the Software as Intel may select.

EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE, THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for the accuracy or completeness of any information, text, graphics, links, or other items contained within the Software.

LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION. In the event that you use the Software in conjunction with a virtual (“emulated”) device designed to appear as an Intel component product, you acknowledge that Intel is neither the author nor the creator of the virtual (“emulated”) device. You understand and acknowledge that Intel makes no representations about the correct operation of the Software when used with a virtual (“emulated”) device, that Intel did not design the Software to operate in conjunction with the virtual (“emulated”) device, and that the Software may not be capable of correct operation in conjunction with the virtual (“emulated”) device. You agree to assume the risk that the Software may not operate properly in conjunction with the virtual (“emulated”) device. You agree to indemnify and hold Intel and its officers, subsidiaries and affiliates harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of product liability, personal injury or death associated with the use of the Software in conjunction with the virtual (“emulated”) device, even if such claim alleges that Intel was negligent regarding the design or manufacture of the Software.

UNAUTHORIZED USE. THE SOFTWARE IS NOT DESIGNED, INTENDED, OR AUTHORIZED FOR USE IN ANY TYPE OF SYSTEM OR APPLICATION IN WHICH THE FAILURE OF THE SOFTWARE COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR (E.G MEDICAL SYSTEMS, LIFE SUSTAINING OR LIFE SAVING SYSTEMS). If you use the Software for any such unintended or unauthorized use, you shall indemnify and hold Intel and its officers, subsidiaries and affiliates harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of product liability, personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Intel was negligent regarding the design or manufacture of the part.

TERMINATION OF THIS AGREEMENT. Intel may terminate this Agreement at any time if you violate its terms. Upon termination, you will immediately destroy the Software or return all copies of the Software to Intel.

APPLICABLE LAWS. Claims arising under this Agreement shall be governed by the laws of the State of California, without regard to principles of conflict of laws. You agree that the terms of the United Nations Convention on Contracts for the Sale of Goods do not apply to this Agreement. You may not export the Software in violation of applicable export laws and regulations. Intel is not obligated under any other agreements unless they are in writing and signed by an authorized representative of Intel.

GOVERNMENT RESTRICTED RIGHTS. The enclosed Software and documentation were developed at private expense, and are provided with “RESTRICTED RIGHTS.” Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR 52.227-14 and DFARS 252.227-7013 et seq. or its successor. The use of this product by the Government constitutes acknowledgement of Intel’s proprietary rights in the Software. Contractor or Manufacturer is Intel.

LANGUAGE; TRANSLATIONS. In the event that the English language version of this Agreement is accompanied by any other version translated into any other language, such translated version is provided for convenience purposes only and the English language version shall control.

Last modified on 5/15/11 10:56p Revision

DOCS/SERVER/lights.htm0000755000000000000000000001257111656577060011534 0ustar Indicator Lights

Indicator Lights

The Intel® PRO/100+ adapter, PRO/100 S adapter, and PRO/100 VE and VM Desktop Adapters and Network Connections have the following indicator lights:

 Label

Indication

 Meaning
 ACT/LNK On The adapter and switch are receiving power; the cable connection between the switch and adapter is good.
  Off The adapter and switch are not receiving power, or you have a driver configuration problem.
  Flashing The adapter is sending or receiving network data. The frequency of the flashes varies with the amount of network traffic.
 100TX On Operating at 100 Mbps.
  Off Operating at 10 Mbps.

The PRO/100+ Dual Port Server adapter (with three LEDs per port) has the following indicator lights:

 Label Indication Meaning
 LNK On The adapter and switch are receiving power; the cable connection between the switch and adapter is good.
Off The adapter and switch are not receiving power; the cable connection between the switch and adapter is faulty; or you have a driver configuration problem.
 ACT On or flashing The adapter is sending or receiving network data. The frequency of the flashes varies with the amount of network traffic.
  Off The adapter is not sending or receiving network data.
 100 On Operating at 100 Mbps.
  Off Operating at 10 Mbps.

The Intel® PRO/100 S Dual Port Server adapter (with 64 bit PCI Connector) has the following indicator lights:

 Label Indication Meaning
 ACT/LNK On The adapter and switch are receiving power; the cable connection between the switch and adapter is good.

NOTE: if only one port appears to be operating, go into the Network control panel (Windows) or a configuration file for other operating system, and check the status of the second port.

Off The adapter and switch are not receiving power, or you have a driver configuration problem.
  Flashing The adapter is sending or receiving network data. The frequency of the flashes varies with the amount of network traffic.
 100TX On Operating at 100 Mbps.
  Off Operating at 10 Mbps.

Last modified on 10/12/09 9:04p Revision

DOCS/SERVER/manage.htm0000755000000000000000000002521311734015456011460 0ustar Remote Wake-Up

Remote Wake-Up and Wake on LAN*

About Remote Wake-Up

The ability to remotely wake computers is an important development in computer management. This feature has evolved over the last few years from a simple remote power-on capability to a complex system interacting with a variety of device and operating system (OS) power states.

NOTES:
  • Not all systems support every wake setting. There may be BIOS or Operating System settings that need to be enabled for your system to wake up. In particular, this is true for Wake from S5 (also referred to as Wake from power off).

 The following adapters do not support Wake on LAN* (WoL) operations

  • Intel® PRO/1000 MT Quad Port Server adapter
  • Intel® Gigabit VT Quad Port Server Adapter
  • Intel® Ethernet Server Adapter X520-2
  • Intel® Ethernet Server Adapter X520-1
  • Intel® Ethernet Server Adapter X540-T1
  • Intel® Ethernet Converged Network Adapter X540-T2
  • Intel® Ethernet Converged Network Adapter X540-T1

Wake on Magic Packet

In early implementations of Remote Wake-up, the computer could be started from a power-off state by sending a Magic Packet. A Magic Packet is an Ethernet packet that contains an adapters MAC address repeated 16 times in the data field. When an adapter receives a Magic Packet containing its own MAC address, it activates the computers power. This enables network administrators to perform off-hours maintenance at remote locations without sending a technician out.

This early implementation did not require an OS that was aware of remote wake-up. However, it did require a computer that was equipped with a standby power supply and had the necessary circuitry to allow the remote power control. These computers were typically equipped with a feature named Advanced Power Management (APM). APM provided BIOS-based power control.

Advanced Configuration and Power Interface

Newer computers feature Advanced Configuration and Power Interface (ACPI), which extends the APM concept to enable the OS to selectively control power. ACPI supports a variety of power states. Each state represents a different level of power, from fully powered up to completely powered down, with partial levels of power in each intermediate state. Power states include:
Power State  Description
S0 On and fully operational
S1 System is in low power mode (sleep mode). The CPU clock is stopped, but RAM is powered on and being refreshed.
S2 Similar to S1, but power is removed from the CPU.
S3 Suspend to RAM (standby mode). Most components are shutdown. RAM remains operational.
S4 Suspend to disk (hibernate mode). The memory contents are swapped to the disk drive and then reloaded into RAM when the system is awakened.
S5 Power off

Not all systems support being awakened from a powered-off state.

Remote wake-up can be initiated by a variety of user selectable packet types and is not limited to the Magic Packet format. For more information about supported packet types, see the operating system settings section.

Wake Up Address Patterns

The wake up capability of Intel gigabit adapters is based on patterns that are sent by the OS. You may configure the driver to the following settings using Intel® PROSet:

  • OS Controlled - Accept all the patterns sent to the OS.

  • Directed Packets - Accepts only patterns containing the Adapter's Ethernet address in the Ethernet Header or containing the IP address, assigned to the adapter, in the IP header.

  • Magic Packets - Accept only patterns containing 16 consecutive repetitions of the adapter's MAC address.

  • Directed & Magic - Accepts the patterns of both directed packets and magic packets.

Choosing "Directed Packets" will also accept patterns of the Address Resolution Protocol (ARP) querying the IP address assigned to the adapter. Upon configuring multiple IP addresses to one adapter, the OS may request to wake up on ARP patterns to all of the configured addresses. The adapter will only awaken in response to ARP packets querying the first IP address in the list.

Physical Installation Issues

Wake on LAN Cable

For computers with a PCI 2.1 compliant bus

A Wake on LAN cable is required on all remote wake-up capable adapters when used in older WoL-capable computers. These computers are generally equipped with a PCI 2.1 complaint bus and the BIOS is typically designed for APM compliant power management.
NOTE:  Remote Wake-Up from power-off (S5) is not supported on the following adapters in computers using the PCI 2.1 bus. To use Remote Wake-Up on any of the adapters listed below, the computer must have a PCI 2.2 compliant bus.
  • Intel PRO/100+ PCI adapter (PILA8460BN)
  • Intel PRO/100 M Desktop adapter (PILA8460F)
  • Intel PRO/1000 T Desktop adapter (PWLA8390T)
  • Intel PRO/1000 XT Server adapter (PWLA8490XT)

For computers with a PCI 2.2 compliant bus

The Wake on LAN cable is not usually required for computers equipped with a PCI 2.2 compliant bus, as the wake up signal is routed through the PCI bus. This is done through the PCI connector pin defined as PME (Power Management Event).

Many of the newer ACPI computers also have a connector for the 3-pin Wake on LAN cable for backwards compatibility with older WOL capable adapters. In this type of computer, the WOL cable is still required for older 82558-based Intel® PRO/100+ Management adapter model numbers PILA8900 and PILA8461.

Slot

Some motherboards only support remote wake-up (or remote wake-up from S5 state) in a particular slot. For example, the Intel® Desktop Board D815EPEA2 only supports remote wake-up from a powered off (S5) state if the adapter is plugged into PCI slot 2. It does, however, support remote wake-up from standby from any slot. See the documentation that came with your system or motherboard for details on remote wake-up support.

Power

Early versions of the Intel PRO/100+ Management adapter are +5 volt only. These models must have the 3-pin cable attached for the remote wake-up function to work. These adapters are equipped with 3 LEDs on the adapter bracket, whereas the PCI 2.2 compliant PRO/100 models have 2 LEDs on the adapter bracket. The older +5 volt model adapters are not compliant to the PCI 2.2 specification and do not fit in a 3-volt only PCI slot due to the slot being keyed differently.

Newer Intel network adapters are 3.3 volt, but work in a 5-volt slot also. They are keyed to fit either type of slot.

If your computer requires the 3-pin cable, the +5 volt standby power supply must supply at least 0.2 amps at +5 volts for each adapter installed. For older PCI 2.1 compliant management adapters, the power supply must supply at least .6 amps. This value is usually listed on the power supply label as +5SB, +5VSB or +5AUX. 

If your remote wake-up enabled computer is compliant to PCI specification 2.2, it does not require the 3-pin cable for remote wake-up. In these computers, the 3.3 volt standby power supply must provide at least 0.2 amps for each adapter installed. You may need to contact your computer manufacturer to verify the standby current rating. Turning off the remote wake up capability on the adapter by using the IBAUTIL utility reduces the power draw to around 50 milliamps (.05 amps) per adapter.

BIOS Settings

You may need to configure various settings in the computer BIOS so that remote wake-up will work.

Many ACPI computers can be configured to work in APM mode. Check your BIOS settings to determine which mode you are operating in.

In both APM and ACPI computers, you may find settings for Wake on LAN under the Power Control area and titled "Wake on LAN" and/or Wake on PME". Wake on LAN setting refers to wake up events received through the 3-pin header cable. Wake on PME refers to wake up events received through the PCI bus. To enable remote wake-up, you should enable the setting that corresponds to your adapter connection. For example, set Wake on LAN to enable if you are using the WOL cable.

In ACPI computers operating in ACPI mode and using an ACPI aware OS, look for an ACPI specific setting. If you want to power up the system from a power off state, set an ACPI specific setting such as "Wake on LAN from S5" to enable.

Last modified on 7/12/11 11:31p Revision DOCS/SERVER/mang_win.htm0000755000000000000000000001754011734015456012033 0ustar Power Management

Power Management

The Intel® PROSet Power Management tab replaces the standard Microsoft* Windows* Power Management tab in Device Manager. It includes the Power Saver and Wake on LAN* (WoL*) options that were previously included on the Advanced tab. The standard Windows power management functionality is incorporated on the Intel PROSet tab.

NOTES:
  • The options available on the Power Management tab are adapter and system dependant. Not all adapters will display all options.
  • The following adapters support WoL only on Port A:
    • Intel® Ethernet Server Adapter I350-T2
    • Intel® Ethernet Server Adapter I350-T4
    • Intel® Ethernet Server Adapter I340-T2
    • Intel® Ethernet Server Adapter I340-T4
    • Intel® Ethernet Server Adapter I340-F4
    • Intel® Gigabit ET2 Quad Port Server Adapter
    • Intel® PRO/1000 PF Quad Port Server Adapter
    • Intel® PRO/1000 PT Quad Port LP Server Adapter
    • Intel® PRO/1000 PT Quad Port Server Adapter
    • Intel® PRO/1000 PT Dual Port Network Connection
    • Intel® PRO/1000 PT Dual Port Server Connection
    • Intel® PRO/1000 PT Dual Port Server Adapter
    • Intel® PRO/1000 PF Dual Port Server Adapter
    • Intel® Gigabit PT Quad Port Server ExpressModule
  • The following adapters do not support WoL:
    • Intel® PRO/1000 MT Quad Port Server adapter
    • Intel® Gigabit VT Quad Port Server Adapter
    • Intel® Ethernet Server Adapter X520-2
    • Intel® Ethernet Server Adapter X520-1
    • Intel® Ethernet Server Adapter X540-T1
    • Intel® Ethernet Converged Network Adapter X540-T2
    • Intel® Ethernet Converged Network Adapter X540-T1

NOTE: If your system has a Manageability Engine, the Link LED may stay lit even if WoL is disabled.

Power Options

The Intel PROSet Power Management tab includes several settings that control the adapter's power consumption. For example, you can set the adapter to reduce its power consumption if the cable is disconnected.

If Reduce speed during standby is enabled,  then Wake on Magic Packet and/or Wake on directed packet must be enabled. If both of these options are disabled, power is removed from the adapter during standby. Wake on Magic Packet from power off state has no effect on this option.

Energy Efficient Ethernet

The Energy Efficient Ethernet (EEE) feature allows a capable device to enter Low Power Idle between bursts of network traffic. Both ends of a link must have EEE enabled for any power to be saved. Both ends of the link will resume full power when data needs to be transmitted. This transition may introduce a small amount of network latency.

NOTES:

  • Both ends of the EEE link must automatically negotiate link speed.
  • EEE is not supported at 10Mbps.

 

Intel® Auto Connect Battery Saver

The Intel® Auto Connect Battery Saver (ACBS) feature turns off the adapter when link is down or the network cable is disconnected. After a timeout period, the adapter will power off. When the network cable is reconnected and link is restored, the NIC powers up and functionality is fully restored.

ACBS only functions when the system is on battery power. If the power cable is connected, ACBS will be automatically disabled. If ACBS is active, the adapter will appear to be powered off. If you have Intel® PROSet installed, on the Link Speed tab, the Link Status will indicate Speed: Not connected. Power off.

NOTE: ACBS will not function on an adapter if the adapter has forced speed or duplex settings. ACBS will only function if the adapter is set to auto-detect or auto-negotiate.

Intel® System Idle Power Saver

The Intel® System Idle Power Saver feature sets the adapter to negotiate the lowest possible speed setting when the system and network are idle. When the system activity is detected, the link will be negotiated to a higher speed.

To support this feature, the adapter must be

  • configured to Auto Detect speed and
  • connected to a link partner that can auto-negotiate speed

Remote Wake-Up and Wake on LAN*

The ability to remotely wake computers is an important development in computer management. This feature has evolved over the last few years from a simple remote power-on capability to a complex system interacting with a variety of device and operating system power states. More details are available here.

Microsoft Windows XP, Windows Vista*, Windows 7, Windows Server* 2003, Windows Server 2008, and Windows Server 2008 R2 are ACPI-capable. These operating systems do not support wake from a power-off (S5) state, only from standby (S3) or hibernate (S4). When shutting down the system, they shutdown ACPI devices, including Intel adapters. This disarms the adapters remote wake up capability. However, in some ACPI-capable computers, the BIOS may have a setting that allows you to override the operating system and wake from an S5 state anyway. If there is no support for wake from S5 state in your BIOS settings, you are limited to Wake From Standby when using these operating systems in ACPI computers.

For some adapters, the Power Management tab in Intel PROSet includes a setting called Wake on Magic Packet from power off state. Enable this setting to explicitly allow wake up with a Magic Packet* from shutdown under APM power management mode.

In ACPI-capable versions of Windows, the Intel PROSet Power Management tab includes Wake on Magic Packet and Wake on directed packet settings. These controls the type of packets that wake up the system from standby.

Wake on Intel® Ready Access

Intel® Ready Access keeps your network connection active when the rest of your system is in sleep or standby mode, so that content on your system is readily accessible. Requests from other computers will wake up your computer.

Last modified on 7/12/11 11:49p Revision

DOCS/SERVER/note.gif0000755000000000000000000000073211651733270011150 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/SERVER/overview.htm0000755000000000000000000000575411656577060012115 0ustar Overview

Overview

Welcome to the User's Guide for the Intel® PRO/100 family of server adapters. This guide covers hardware and software installation, setup procedures, and troubleshooting tips for these adapters.

NOTE: This guide refers only to drivers and features available on IA-32-based computer platforms and platforms based on the Intel® 64 Architecture. These drivers are not compatible with Itanium®-based computers.

For further information, see the other user guides.

To select a topic, click a link in the table of contents column to the left.

Installing the Network Adapter

If you are installing a network adapter, follow this procedure. 
If you are upgrading the driver software, start with step 5.

  1. Make sure that you are installing the latest driver software for the adapter you are installing. Here is a list of supported adapters.

  2. Review system requirements.

  3. Insert the adapter(s) in the computer.

  4. Attach the network cable(s).

  5. Install the network driver.

  6. For Windows systems, install the Intel® PROSet software.

If you have any problems with basic installation, see Troubleshooting.

You can now set up advanced features, if necessary. The available features and the configuration process varies with the adapter and your operating system.

Intel Network Encryption Co-Processor

The Intel PRO/100 S Family of network adapters includes an Intel® 82594ED IPSec Encryption Co-processor. If Windows* XP is enabled for IPSec encryption, it automatically offloads the intensive encryption and authentication functions to the adapter, increasing throughput and decreasing CPU utilization. Tunnel mode processing is off-loaded to the encryption co-processor.

Last modified on 11/22/10 3:58p Revision

DOCS/SERVER/overvwit.htm0000755000000000000000000000611511656577060012124 0ustar Overview - PRO100 Server for Itanium

Overview

Welcome to the User's Guide for Intel PRO/100 Server Adapters installed in Itanium®-based computers. This guide covers hardware and software installation, setup procedures, and troubleshooting tips for Intel network adapters. 

NOTE: This guide refers only to drivers and features available on Itanium-based computers. The drivers are not compatible in IA-32-based platforms or those based on the Intel® 64 Architecture.

For further information, see the other user guides.

To select a topic, click a link in the table of contents column to the left.

Installing the Network Adapter

If you are installing a network adapter, follow this procedure. 
If you are upgrading the driver software, start with step 5.

  1. Make sure that you are installing the latest driver software for the adapter you are installing. For a list of supported adapters, click here.

  2. Review system requirements.

  3. Insert the adapter(s) in the computer.

  4. Attach the network cable(s).

  5. Install the driver.

  6. For Windows systems, install the Intel® PROSet software.

If you have any problems with basic installation, see Troubleshooting.

You can now set up advanced features, if necessary. The available features and the configuration process varies with the adapter and your operating system. 

Intel Network Encryption Co-Processor

The Intel PRO/100 S Family of network adapters includes an Intel® 82594ED IPSec Encryption Co-processor. If Microsoft* Windows* XP is enabled for IPSec encryption, it automatically offloads the intensive encryption and authentication functions to the adapter, increasing throughput and decreasing CPU utilization. Tunnel mode processing is off-loaded to the encryption co-processor.

Last modified on 11/22/10 3:59p Revision

DOCS/SERVER/pro1000c.gif0000755000000000000000000001342111656741062011451 0ustar GIF87a.+,@>?202:8:  }{y{wuwPOPONO}|}:8;DDFkknZZ\**+rrtBBC||}ttuccd[[\ѻ>?Bjkn`bfhjn|}x{PRTXZ\bcdfghpsu8:;HJKȿ "# 422VSSB@@#""wttfdddbbb``^\\/..wuuussKJJDCClkkhgg[ZZù!,@H*\ȰCŋ3jȱǏy#ȣ!Al(\ɲ˗/c@N Lh 6 J >SK!hMXjh҇RBJ:6Fl*r]˶mKI tQxu`Ia]r/kfA *"-)F N8i<^ͺ55&7g۾ K o*@Q0;!9P/ŹT@ݼ#fpΛ@4{V ֬5׏ M=$Mvf+ag߁Ѱ߂ @`-a$hT o hRwWIաAIJ A`,'#fI@PH&Q@8 ~>VY"fWց\dZ'Q^ uRFwVƹ ? ᥒ%Í*ԈaTD ]r@y rFZryi *%Ч.ڨ(Q*Цm h%\fzVWX`A `,QlY5"Zr JQ(]HP H Kba'X,l1gyF!/_ ڐn5GX![Bp↳ZkZ-$#KyiIdg,bڮ(doAsm{L#Քpg\Z!ӢX'j\^V9ZDYâ)iI, qW}&u drq`2=ٰD)IKˆ(}˛aYkŽ ^h6Y/y6D:28k!7NLB|`g-6QPuCF eHYt޺iB⧬UM%ba<  JMZ34']zY6Yv(XᘏZxi9cdi7[;籐bZ4adž'a]Ó5s!"CsC嘒,g%~0%nnaq7)_y[ = !]I]3T?iVڵUDlfa7] ["10-SOR9QJ\^" 7of(SeR,=A<&8i>y.qʳ% 2E_ WF10C 8*m 9 YeFY+aDBp)vBC8Aya Alɜ@PB@ҹt6-#xjӉ[#ahL}&Abႜ&.3by~(^#1f ? h(@v. s RNF{6DAheFbF$ bifA&jcZ]d) %Q(bEP jz`3gqV/Hf5Zk'ң?ʋ[9`-"k,Ԥa *jpjbCƉ7>DVa0C[9^ZM ;:XK6V0jzu`#D&q_c5y6<6h(¨L 3 jxޢcBE@zڢjm.(|Q!^j bJʫVVSecjs %݃jՊbtUEVi4uwʢaL7vU*B}80L? vWE,2F6 zA Anoz*Cl %V.Ɖ6b.][?~*jR`XLpu(p|:ƥ"voo+ +p|G.gczoN[@%@u{Waf a 'I'I+lik~AFrnqZkrp)H[_Mksg'DEfHR'FwדppJyG0wMQ3?19H${-79 k?~U@:\ sPz tamֆs:'VrKf&`Nq:c!q'?uMĶ L79ۻ; O`}|f֛=̼FXxtq %X;$+?cM@S1A2A hKɕ\̓1-Ck!\P&x9YPXA%CJλ[7NqrA^EH 3ON1ޗQ/1llXdN jN0(̂="0|rD{8ݬB10/Ox1EQrfzP26QP3Hu7i(n,V@CWQ!l GhVY,W(mSN}",p#sQP "@|R5} :R/5Zw{2T$KA J\mptN#K1-F/!P<" ?%2ڜ 2P;=EMYW 'BCMPSx4NP4SMuhCm`4x8pU-Aܰ.Zxf cm0*}X*U@ކyS pU8wjeEm}16 (l~+z{^0.`J&B>dߤf}^' JKIѱq( s`!l췾8S9~q̎-ɛ>ՂhnJ=ḧ>qn y_/~n5WQ;;DOCS/SERVER/prosetdm.htm0000755000000000000000000000472411714034554012067 0ustar Using PROSet

Intel® PROSet for Windows* Device Manager

Intel® PROSet for Windows* Device Manager is an extension to the Windows Device Manager. When you install the Intel PROSet software, additional tabs are automatically added to Device Manager.

NOTE:  You must have administrator rights to install or use Intel PROSet for Windows Device Manager.

Installing Intel PROSet for Windows Device Manager

Intel PROSet for Windows Device Manager is installed from the Product CD with the same process used to install drivers. You can select Intel PROSet for Windows Device Manager and Advanced Network Services from the Install Options dialog.

Removing Intel PROSet for Windows Device Manager

Use Add/Remove programs from the Control Panel to uninstall Intel PROSet for Windows Device Manager.

Changing Intel PROSet Settings Under Windows Server Core

You can use the command line utility prosetcl.exe to change most Intel PROSet settings under Windows Server Core. Please refer to the help file prosetcl.txt located in the \Program Files\Intel\DMIX\CL directory. For iSCSI Crash Dump cofiguration, use the CrashDmp.exe utility and refer to the CrashDmp.txt help file.

Compatibility Notes

The following devices do not support Intel PROSet for Windows Device Manager

  • Intel® 82552 10/100 Network Connection
  • Intel® 82567V-3 Gigabit Network Connection

Last modified on 8/04/10 8:12p Revision DOCS/SERVER/pushinst.htm0000755000000000000000000000354711735070116012106 0ustar Microsoft* Windows* Push Install Instructions

Microsoft* Windows* Push Install Instructions

A "Push," or unattended, installation provides a means for network administrators to easily install the drivers on systems that have similar equipment. The following document provides instructions for a basic unattended installation of Microsoft* Windows* that includes the installation of drivers for Intel® Network Adapters.

For 32-bit Microsoft Windows operating systems, see the Push32.txt file in the Apps\Setup\Push\Win32 directory on the Product CD or in the download directory. This file applies to the following operating systems:

  • Microsoft Windows* 7
  • Microsoft Windows Vista*
  • Microsoft Windows* XP
  • Microsoft Windows Server* 2008
  • Microsoft Windows Server* 2003

 

For x64 Microsoft Windows operating systems, see the Pushx64.txt file in the APPS\SETUP\PUSH\WINX64 directory on the Product CD or in the download directory. This file applies to the following operating systems:

  • Microsoft Windows Server* 2008 R2
  • Microsoft Windows Server* 2008 x64
  • Microsoft Windows* 7 x64
  • Microsoft Windows Vista* x64
  • Microsoft Windows* XP x64
  • Microsoft Windows Server* 2003 x64

Last modified on 2/22/10 4:47p Revision

DOCS/SERVER/qos.htm0000755000000000000000000000422711735070116011027 0ustar Quality of Service (QoS)

Quality of Service

Quality of Service (QoS) allows the adapter to send and receive IEEE 802.3ac tagged frames. 802.3ac tagged frames include 802.1p priority-tagged frames and 802.1Q VLAN-tagged frames. In order to implement QoS, the adapter must be connected to a switch that supports and is configured for QoS. Priority-tagged frames allow programs that deal with real-time events to make the most efficient use of network bandwidth. High priority packets are processed before lower priority packets.

Under Windows XP and Windows Server 2003, tagging is enabled and disabled using the "QoS Packet Tagging" setting in the Advanced tab in Intel® PROSet. Under Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2, tagging is enabled using the "Priority/VLAN Tagging" setting on the Advanced tab.

Once QoS is enabled in Intel PROSet, you can specify levels of priority based on IEEE 802.1p/802.1Q frame tagging.

The supported operating systems have a utility for 802.1p packet prioritization. For more information, see the Windows system help and Microsoft's knowledge base.

NOTE: The first generation Intel® PRO/1000 Gigabit Server Adapter (PWLA 8490) does not support QoS frame tagging.

 

Last modified on 4/22/09 10:46p Revision

DOCS/SERVER/reg100s.htm0000755000000000000000000001377711656741516011433 0ustar Regulatory Information

Regulatory Information

  • Intel® PRO/100 S Server Adapter
  • Intel® PRO/100 S Dual Port Server Adapter

Safety Compliance

  • UL 60950-1 Second Edition
  • CAN/CSA-C22.2 No 60950-1-07 Second Edition
  • EN 60950-1:2006 +A11:2009 (European Union)
  • IEC 60950-1:2005 Second Edition (International)
  • EU LVD Directive 2006/95/EC

EMC Compliance

  • FCC (Class B) Radiated & Conducted Emissions (USA)
  • ICES-003 (Class B)/NMB-003 (Class B) Radiated & Conducted Emissions (Canada)
  • CISPR 22 (Class B) Radiated & Conducted Emissions (International)
  • EN55022:2006 Radiated & Conducted Emissions (European Union)
  • EN55024:1998 +A1:2001 +A2:2003 Immunity (European Union)
  • EU EMC Directive 2004/108/EC
  • VCCI (Class B) Radiated & Conducted Emissions (Japan)
  • CNS13438 (Class B) Radiated & Conducted Emissions (Taiwan)
  • AS/NZS CISPR 22 (Class B) Radiated & Conducted Emissions (Australia/New Zealand)
  • KCC notice 1997-4, EMI and KCC notice 1997-42 EMS (Korea)

Regulatory Compliance Markings

When required these products are provided with the following Product Certification Markings:

  • UL Recognition Mark for USA and Canada
  • CE Mark
  • FCC Class B markings (Declaration of Conformity)
  • VCCI Class B Marking
  • Australian C-Tick Mark
  • Korea KCC markings
  • Taiwan BSMI Class B markings
  • People's Republic of China "EFUP" mark

Electromagnetic Compatibility Notices

FCC Declaration of Conformity Statement

These adapters have been tested to comply with FCC Standards for Home or Office Use.

Intel Corporation
5200 N.E. Elam Young Parkway
Hillsboro, OR 97124-6497
Phone 1-800-628-8686

This equipment has been tested and found to comply with the limits for a Class B digital device pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation.

If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

  • Reorient or relocate the receiving antenna.
  • Increase the separation between the equipment and receiver.
  • Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
  • Consult the dealer or an experienced radio/TV technician for help.
CAUTION: If the device is changed or modified without permission from Intel, the user may void his or her authority to operate the equipment.
NOTE: This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

Canadian Compliance (Industry Canada)

CANADA ICES-003 CLASS B / CANADA NMB-003 CLASSE B

Manufacturer Declaration
European Community

Intel Corporation declares that the equipment described in this document is in conformance with the requirements of the European Council Directive listed below:

Low Voltage Directive 2006/95/EC
EMC Directive 2004/108/EC

This declaration is based upon compliance of the product to the following standards:

EN 55022:2006 +A1:2007 (CISPR 22 Class B) RF Emissions Control.
EN 55024:1998 +A1:2001 +A2:2003 (CISPR 24) Immunity to Electromagnetic Disturbance.
EN 60950-1:2006 +A11:2009 Information Technology Equipment- Safety-Part 1: General Requirements.

Responsible party:

Intel Corporation, Mailstop JF3-446
5200 NE Elam Young Parkway
Hillsboro, OR 97124-6497

 

VCCI Class B Statement

China RoHS Declaration

KCC Notice (Republic of Korea Only)

 

End-of-Life / Product Recycling

Product recycling and end-of-life take-back systems and requirements vary by country.

Contact the retailer or distributor of this product for information about product recycling and/or take-back.

Last modified on 11/02/10 3:03p Revision

DOCS/SERVER/remscrew.gif0000755000000000000000000001752011656741062012040 0ustar GIF89akfdeXVWsqrpnoUTU~}~zyzyxyvuvpoplkljijihifefede_^_^]^[Z[YXYXWXWVWdzkkmQQR||}yyzsstllmffgddebbcaab]]^[[\YYZWWXVVWUUVïuvyhikdegpqslmoȊz|~suwoqs`abҟһƺ755DBBB@@PNNOMMMKK][[ZXXvttsqqiggSRRNMMDCC~~}|||{{yxxutttssrqqqpponnnmmmllihhgfffeedcccbba```__]\\VUUrrroooZZZVVVOOO,kH*\ȰÇ#eHMH3jȱǏ[qJC! S\ɲ`lH4fɳόIDp)9*]ʴȒt4F VMjIH wʉٳMa#7k+KWS+d߿+ĩs4'+^<0XĻ>ּi(s[*WeM1fz8 '-u띎Mj׸Cn^yتr xx]{;_06N\Eɼ@_bLݺlONgwёZ.([O*ZU3|5$7W$pp!Ywq݂L釘ygArJr$QHXVo!RTY.8r$@G.g&I6Oc!D!б"Pq5KpGo6Uב=b\>),yb gԣBQ GRdd@^" 'TR'`5$)`IWY @%(Օ$OVɆ A@fR.l %o|[x:ӠqL)(p,H6"d)$eI.5('zdrSMTIcu! dԋrvZQ]^h/S@k2, (K:4Eeghњ\Wڛ_AW.73BBGp UbGaSsdq"ˇ+L5<f#YHQovVBf &ey\}7WT&8/(ΐArчϕMrUc+VsZ2o+ф/AIwۨk5(Ja.D32T-jD#UnjO"?nL0$s2DSINf<^djSLdS@fjA^$LY2-/YHa~nwWԐJʙ'As(2O/"@$b s:js$ ' \< 8%ҔD ;9S:qf$ZqO%iJ*PxU1dL<%(jJ-$锨 /b\r*K)V!-KZ=U"l*Y:U?2*V!7)pz7+KΪdl]G0 0]Xc@1Y+ $Eaa&iv%7Vp |m? 6hH0b)0@4xbڬ-b{R}u´@Ւ\xuv<)yͫQ:*]i0?[R/ֽE} rj!Hy#a4H0Y0|$ l!F"G挽Z@$+'ge 6 "dH=lJ!G&s) ȲMWʰKPpMI >b Fų4n(g`ɘ jݾU›p`h0]MAIE脀 F< JNm^21 N4S4WszsV)#Zz`QF4\_3ѐ BViR7e#pB_Jl eg.g!bSu)C۔#Hk0XPYd[Y%7&a|{V[pYAvnjsAj5B߬kSq?<%5˵=$<^urQzF!~qDtVb1p(C㢑sA|Sz7vc'sDJ=3tZ Y%?h\?l]`,ήb7O By{?wwz7:/=ȕ.x&OxArt|A{#d%yY9 pt닞(1Rh|Zy;?cn%Ry9sjA>G\8|wrZ7{~W%{[q8v?fm/;F Vn{l̀"0FG u? 0[8oZ y G~ ) %CeH6k|P Rzd }"o8`Gcjr"lz48Hҁ!~Yi@;kpb"ffs[!vig/! ?2 4{gQowh1 b=Z(XxE`[Z!f%%/ :AW8HlT $fPh^}h(ċE}ZQèep%4 (c0X@(u[ vF_Xxmڈb5y@%Hh >vHNBxkߵM9 ؐe*QL1Q a g !dO HqI TN8&.FG>f@;0&C CՒ 1  RBRgH^`qC_)q&0H!5eՖ U OpO@N9[qO2 ,@y pYoF?0\ \PB6ew/Y \# Pf =IRe] ¤%_i芠@M 1syHi C?GKfI銆D`u%wvfuiNDbSf IVnSuꊇ1p 61zR 4pC`q WPҙ.(nF Wp8zɣ6apHz\L riHV6zY7j[řMJBjIT-`5Pe jF2iv% G*PQu\{z&4C `zN 3 vg\ڤ` pT`zjYa:JiYr%) WsڪwZ頳ja Zʫ ʧ3`GjIꫜ@JjHGpʫYhڤut*ʬʟMq:bt+pXۭY *j ۰iЪ{0Pl +7 ,"۰F |j+02y(h ۋz*~ PAMB;[ /˫G@Q'pZa گ#S x LO۲Rk5P `q O & {P L*op> ˊKʇ" ! ܚ\۴'s `yӪd`˱La jz*0 ۊ}z|۷ @ P#۬з~ۋ۽?۽ћwM ˺a۾Ԁī౻[.k*5J>S0J)Ma;ZKr h&zy|F@ Y i&zm R0B+SK,]k˾L-Y9tK 'ȸM {K uK)N(yKV"aY* xG?1)q}@:~kILqI%? \q=!X{Pd:] O'ƞ A%xǦ<0q cVb4pȖԦ pZv|R܉E3˸̫jtWd,%]SqzG_ L4qp2ཙkˌ̲,L"q*'pbTlޓ&zY@ {|e܉ MbBK@:-z=!JW(0W@{k>֊ }>1 >DkлRv;F@ R^mܰ[[K-_<1< f}늴 }[wᩖn-pmً-NN*~9{B |[nJB'>K Ր @~VK{ mT7chܔE˭GP+ yuk%V&b֙6/L$J.U]~ ͈alab r& tix9Z}T2Ri@^z}_yF|$2=i;q%_YZ"Yb딙 &9 .1) ޣl?1䷙ٛ]YBLX/ɹuιMq.ߏnٹp@o[OzƎ9IމNvW[k .Yx驱$!M)(  o ޡf TO?ґ@S/ $XA .dVҤeE5nq*NCĉSVU0dhK1e 0P5?:H*[%ZHl @iǏ#GM8UX9ISjjYia:bXcLU{V] st.Ot[`J1p^‡%mk rh1*b:_FBƪLۢ.㉨ZCY揱 ADlrQNF+[٨${KmE텂8 Ux/EEё!0=e#VlBzRݻ'j^'j,Km%5Ras%o`LN+5p5lDـI%k)"PK_)~}rLg_sìb'=|\Wm~vi2P}+3 8b-¼{q`^0 iPZ8\QrSB )nnQ38] (r8P-RaאhBHgH-29BS;U")@ڥ%b ⍌Ȇ D_T] 7@!⍬ #6еa bEl< ^Z"RiL6Pԭ'E It׼.a#ʊ!UAf{hn5xuif! a•U!Bg0ĎK] ŵ/ACwE.s&$ŘK^Uo|_~ȿ 0x<nHvOe;a qp`J"AsDb8h3Ta_+ e?(džp!W\5{Vo \iE_hVVjB4d˖,'1S}Msy};DOCS/SERVER/reqs.htm0000755000000000000000000000571411656741062011210 0ustar System Requirements

System Requirements

Before installing the network adapter, check your system for the following minimum configuration requirements for Intel® PRO/100 server adapters.

Hardware Compatibility

  • The latest BIOS for your computer
  • One open PCI or PCI-X bus master slot, 32-bit or 64-bit, operating at 33MHz or higher

Supported 32-bit Operating Systems

Basic software and drivers are supported on the following operating systems:

  • DOS
  • SunSoft* Solaris* (drivers and support are provided by the operating system vendor)

Advanced software and drivers are supported on the following operating systems:

  • Microsoft Windows Server* 2008, with latest service pack installed
  • Microsoft Windows Vista*, with latest service pack installed
  • Microsoft Windows Server 2003, with latest service pack installed
  • Microsoft Windows* XP, with latest service pack installed
  • Linux*, v2.4 kernel or higher
  • FreeBSD*, 6.0 kernel or higher

Intel® 64 Architecture Platform Requirements

Intel supplies 64-bit drivers for the following operating systems:

  • Microsoft Windows Server 2008, with latest service pack installed
  • Microsoft Windows Server 2008 Hyper-V*, with latest service pack installed
  • Microsoft Hyper-V Server 2008, with latest service pack installed
  • Microsoft Windows Vista, with latest service pack installed
  • Microsoft Windows Server 2003, with latest service pack installed
  • Microsoft Windows XP, with latest service pack installed
  • Red Hat Linux
  • SUSE Linux
  • FreeBSD

A platform that supports the Intel® 64 Architecture will run in either 64-bit mode or 32-bit compatibility mode. In order for it to run in 64-bit mode, the following requirements must be met:

  • The system must have a 64-bit BIOS that takes advantage of the Intel 64 Architecture
  • One of the supported 64-bit operating systems must be installed

Last modified on 11/22/10 4:16p Revision

DOCS/SERVER/reqs_ita.htm0000755000000000000000000000314611656741062012042 0ustar Intel PRO/100 Itanium Requirements

System Requirements

Before installing the network adapter, check your system for the following minimum configuration requirements for adapters in Itanium®-based architectures.

Hardware Compatibility

  • The latest BIOS/EFI for your computer
  • One open PCI or PCI-X bus master slot, 32-bit or 64-bit, operating at 33MHz or higher

Supported Operating Systems

The Intel drivers for Itanium-based systems operate with the following operating systems:

  • Microsoft Windows Server* 2003, 64-Bit Edition (Enterprise Server or Datacenter Server versions), with latest service pack installed
  • Windows Server 2008 for Itanium-based Systems, with the latest service pack installed
  • Windows Server 2008 R2, with the latest service pack installed
  • Linux, v2.x kernel and higher, except v2.6

Last modified on 11/01/10 3:28p Revision

DOCS/SERVER/run.gif0000755000000000000000000000014111654247274011010 0ustar GIF89aE "); Document.write(""); Document.write(""); Document.write(""); Document.write(""); Document.write(""); Document.title = "Search Results"; Document.write("

Search Results

"); Document.write("
"); Document.write("
"); if (ExcludeList.length != 0) { for (j=0; j < Entries.length; j++) { var ExcCount = 0; for (i=0; i < ExcludeList.length; i++) { ExcCount += GetEntryCount(Entries[j], ExcludeList[i]); if (ExcCount != 0) break; } if (ExcCount == 0) CurEntries[CurEntries.length] = Entries[j]; } } else CurEntries = Entries; for (i=0; i < SearchList.length; i++) { if (Exclude.indexOf(SearchList[i]) != -1) { if (Exclude_Warning != "") Exclude_Warning += ", "; Exclude_Warning += SearchList[i]; } else { FindString(SearchList[i]); } } if ((SearchList.length == 0) && (ExcludeList.length != 0)) FindString("*"); if (Exclude_Warning != "") { Document.write("

" + Exclude_Warning + ""); if (Exclude_Warning.indexOf(",") != -1) Document.write(" are common words and were ignored.
"); else Document.write(" is a common word and was ignored.
"); } for (i=0; i < Results.length; i++) { Document.write("
"); WriteResult(Results[i][1], Results[i][0], Results[i][2]); } if (Results.length == 0) { var OutStr = ""; for (i=0; i < arguments.length; i++) OutStr += " " + arguments[i]; Document.write("
"); Document.write("Your search - " + OutStr + " - did not match any documents."); Document.write("

Suggestions:
- Make sure all words are spelled correctly.
- Try different keywords
- Try more general keywords
"); } Document.write(""); Document.write(""); Document.close(); ClearArrays(); } function AddToSearchArray(str) { if (str.indexOf("+") != -1) { var len = SearchList.length; if (len != 0) { len--; SearchList[len] = SearchList[len] + str; } else SearchList[0] = str; } else if (str.indexOf("-") == 0) { str = str.substring(1, str.length); ExcludeList[ExcludeList.length] = str; } else SearchList[SearchList.length] = str; } function WriteResult(page_name, page_url, description) { if (arguments.length != 3) { return null; } if (description == "") description = "No description available"; if ((PathDiv == "/") && (page_url.indexOf("\\") != -1)) page_url = page_url.replace("\\", "/"); Document.write("
"+page_name+""); Document.write("
" + description); } function FindString(str) { for (j=0; j < CurEntries.length; j++) { var Count = 0; if (str == "*") Count += 1; Count += GetEntryCount(CurEntries[j], str); if (Count != 0) AddToResults(CurEntries[j][0], CurEntries[j][1], CurEntries[j][2], Count); } } function GetEntryCount(theEntry, str) { if (theEntry.length != 5) return 0; str = str.toLowerCase(); var Count = 0; if (str.indexOf("+") != -1) { var str_array = str.split("+"); var c1 = GetEntryCount(theEntry, str_array[0]) var c2 = GetEntryCount(theEntry, str.replace(str_array[0] + "+", "")); if ((c1 != 0) && (c2 != 0)) Count = c1 + c2; } if (theEntry[1].toLowerCase().indexOf(str) != -1) Count += 8; if (theEntry[2].toLowerCase().indexOf(str) != -1) Count += 5; if (theEntry[3].indexOf(str) != -1) Count += 10; if (theEntry[4].indexOf(str) != -1) Count += 1; return Count; } function AddToResults(url, name, desc, count) { for (k=0; k < Results.length; k++) { if (Results[k][0] == url) { count = Results[k][3] + count; Results.splice(k, 1); break; } } var NewIdx = Results.length; for (l=0; l < Results.length; l++) { if (Results[l][3] <= count) { NewIdx = l; break; } } var NewEntry = new Array(4); NewEntry[0] = url; NewEntry[1] = name; NewEntry[2] = desc; NewEntry[3] = count; Results.splice(NewIdx, 0, NewEntry); } function Splice_Fcn() { if (arguments.length < 2) return; var InsertIdx = arguments[0]; var Count = arguments[1]; var tmp = new Array(); var ModArray = new Array(); var i = 0; for (i = 0; i < InsertIdx; i++) tmp[tmp.length] = this[i]; for (i = 2; i < arguments.length; i++) tmp[tmp.length] = arguments[i]; for (i = InsertIdx + Count; i < this.length; i++) tmp[tmp.length] = this[i]; for (i = 0; i < tmp.length; i++) this[this.length] = tmp[i]; return ModArray; } function ClearArrays() { Results = new Array(); SearchList = new Array(); ExcludeList = new Array(); CurEntries = new Array(); } var Exclude = "a add all also an and and/or are as at be but by can did do for from has have how id if in into is it no non not of on once one only onto or so some than that the this to too try two use want well what when where which why will with within yes you your"; var Entries = new Array(); Entries[0] = new Array(4); Entries[0][0] = "ad_100s.htm"; Entries[0][1] = "Supported Adapters Server Pro/100"; Entries[0][2] = "Supported Intel PRO/100 Server This driver and software are designed to operate with the following Intel PRO/100 server adapters Product Name Board ID # &dagger ..."; Entries[0][3] = "adapters connections software"; Entries[0][4] = "a56831 adapter barcode board card code com/support/go/network/adapter/home controller dagger designed devices digit driver dual extension following front guide htm http intel last microsoft modified name operate port printed pro/100 product revision see server software sticker support vista windows xxx"; Entries[1] = new Array(4); Entries[1][0] = "cable.htm"; Entries[1][1] = "Attach the RJ45 Network Cable"; Entries[1][2] = "How to attach an RJ45 network cable to your adapter."; Entries[1][3] = "cable port rj45"; Entries[1][4] = "accommodate according achieve adapter addition allows any association's attach auto automatically based better between cable cases cat category caution ceilings cispr compatible compliance complies configure connect controller copper cross depending devices directly dual duplex either en50174 en55024 environment eus feature fire following gigabit industry information insert insure intel intended last length less limited link make manually may mbps mdi meters models modified more must negotiate network note operation over pair partner plenum port properly rated recommendations residential revision rj45 rooms runs safety see segment set shielded should shown single specification speed sure telecommunications terminated through tia twisted types up walls website wiring without"; Entries[2] = new Array(4); Entries[2][0] = "drivers.htm"; Entries[2][1] = "Install the Drivers"; Entries[2][2] = "Installing Microsoft Windows drivers for your adapter."; Entries[2][3] = "drivers install"; Entries[2][4] = "acceptable adapter add/remove after already any apply attempts automatically autorun before below cable cancel cannot cd click computer confirmation connections control dialog discovers displayed displays double download driver extracted files find follow found hardware insert install instructions intel intervention last located microsoft modified network new notes ok operating package panel plug procedure product programs r2 recommended regardless release revision runs screen select server software start support system them these transfer uninstall update user versions vista website whether window without wizard xp"; Entries[3] = new Array(4); Entries[3][0] = "support.htm"; Entries[3][1] = "Intel Customer Support"; Entries[3][2] = "Customer Support Intel support is available on the web or by phone. Support offers the most up to date information about Intel products, including installation ..."; Entries[3][3] = ""; Entries[3][4] = "about available corporate customer date general including information installation instructions intel internet last modified most network offers phone product revision site support tips troubleshooting up web"; Entries[4] = new Array(4); Entries[4][0] = "dupwindm.htm"; Entries[4][1] = "Configuring Speed and Duplex in Windows"; Entries[4][2] = "How to configure an adapter's speed and duplex under Microsoft Windows."; Entries[4][3] = "duplex link speed"; Entries[4][4] = "adapter administrators advertises allow always appropriate attach attempt auto available based been best cannot capable caution change choose click configure connections considerations copper default determine device differently direct disabled does down duplex either enabled establish experienced fiber force full gbps gigabit half identical ieee intel last like link manager manually match may mbps menu microsoft mode modified modules multi must native navigate need negotiate network ok older open operate option packets partner pass per performance performs present pro/100 properties pull receive requires revision runs same select send set sfp should specific speed suffer support switch tab their time up using windows would"; Entries[5] = new Array(4); Entries[5][0] = "hotwin.htm"; Entries[5][1] = "PCI Hot Plug Support for Microsoft Windows"; Entries[5][2] = "PCI Hot Plug Support for Microsoft Windows Operating Systems Intel network adapters are enabled for use in selected servers equipped with PCI Hot Plug support ..."; Entries[5][3] = "hot pci plug"; Entries[5][4] = "adapter address back before conflict connecting details documentation driver elsewhere enabled ensure equipped hardware hot identical information intel last mac member microsoft modified more network nic notes occur operating original pci plug remove replacement restore revision running see selected server setting sla support switch systems team unless up windows works"; Entries[6] = new Array(4); Entries[6][0] = "hyperv.htm"; Entries[6][1] = "Creating Virtual NICs in Hyper V"; Entries[6][2] = "Creating Virtual NICs in Microsoft Hyper V."; Entries[6][3] = "hyper hyper-v nics v virtual"; Entries[6][4] = "aaaaaaaa able adapter added address advanced alb allow any appear applies article automatically available balancing based bbbb between bind bound box bridging bypasses cannot capable cases cause cccc center change channel check click cluster com/technology/advanced comm/virtualization command communication configuration configuring connectivity considerations consolidate control core correct cpu create createteam data dcb dddddddddddddddd desire details device different directly disable documentation does driver each enable environment error etc ethernet even example faster fcoe fibre file filter follow frees general get give guest gui guid hardware higher host however htm http hyper i/o ignoring impact increases information installation instructions intel interface iov issue laa last lets line linked load lose loss lower mac machine makes management manager manger manually may memory microsoft mode modified more move ms must necessary need netbios network nic note number nvspbind offloading ok open operating operation order oses over overview packet panel parent part partition path perform performance physical please port possible present prevent primary property proset prosetcl protocol queue r2 receive reduces remote require resolve resources result revision root routes rsquo run same secondary see separate server set several share sheet simultaneously since single sits software sr standard step such support switch system tab takes tasks tcpip team team1 technet their then these they throughput together tool transmit true tttttttt unbind uncheck under underlying unique up usage utility utilization uuuu validation virtual virtualization virtualized vlan vmq vnic was windows work www wwww xxxxxxxxxxxxxxxx"; Entries[7] = new Array(4); Entries[7][0] = "insert.htm"; Entries[7][1] = "Insert the Adapter"; Entries[7][2] = "Step by step instructions on how to install a PCI or PCI X adapter into a system."; Entries[7][3] = "hot install pci plug"; Entries[7][4] = "adapter additional anything before bit bracket bus case cause caution compatible computer configuration connected connector contacts contents cord could cover damage determine documentation down each edge electrical enabled end endanger error exposed failure firmly function get hot insert install instructions it's last later make master may modified off operating pci plug power problem push remove repeat replace required revision running screw seated secure see select shut slot special start steps still supports sure system table then through touch troubleshooting turn unplug until would"; Entries[8] = new Array(4); Entries[8][0] = "ipmi.htm"; Entries[8][1] = "IPMI Manageability"; Entries[8][2] = "IPMI Manageability Overview The Intelligent Platform Management Interface IPMI allows you to monitor server physical health characteristics, such as temperature, voltage, fans, power supplies, and ..."; Entries[8][3] = "ians intelligent interface ipmi management platform tco-enabled teaming"; Entries[8][4] = "above adapter adaptive address aggregation allows any asset balancing baseboard based bmc capabilities characteristics chassis configure connected connection controller dedicated device does due dynamic enabled enables fact fans functional health however ians ieee information intelligent interface intrusion ipmi last like link load lose mac manageability management mentioned modified monitor must need network overview pass physical plan platform port power provide receive recovery requirements restricted revision same server single sla specific static such supplies system tco team temperature these tracking traffic type vlan voltage"; Entries[9] = new Array(4); Entries[9][0] = "ipsecoff.htm"; Entries[9][1] = "IP Security Offloading"; Entries[9][2] = "Internet Protocol IP Security IPSec is a set of protocols used to help secure the exchange of IP data. IP Security offloading is the assignment ..."; Entries[9][3] = "ip ipsec offloading security"; Entries[9][4] = "algorithm assignment automatically compatible computations configure confining contents cpu data decreases devices disabled enabled enabling exchange features generally hardware help increases information intel internet ip ipsec issue large last left lso may mitigate modified more network note offload pane performance place port proset protocol reduce revision secure security select send set software support table takes those through traffic used utilization window"; Entries[10] = new Array(4); Entries[10][0] = "lbracket.htm"; Entries[10][1] = "Attach the Low Profile Bracket"; Entries[10][2] = "How to attach the low profile bracket for use in systems with low profile slots."; Entries[10][3] = "bracket install low profile"; Entries[10][4] = "adapter any attach away back before bracket carefully charge come dissipate follow future ground handling install instructions last low may models modified necessary need over package product profile re remove revision screws seated securing side sized slide slot small standard static step these they tighten until used using yourself"; Entries[11] = new Array(4); Entries[11][0] = "legaldis.htm"; Entries[11][1] = "Legal Information"; Entries[11][2] = "Copyright and Legal Disclaimers Copyright 2002 2012 Intel Corporation. All rights reserved. Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124 6497 USA Intel ..."; Entries[11][3] = ""; Entries[11][4] = "any assumes brands claimed commitment contained copyright corporation countries disclaimers document does elam errors herein hillsboro information intel itanium last legal make may modified names nor omissions other parkway pentium property reserved responsibility revision rights trademarks update usa young"; Entries[12] = new Array(4); Entries[12][0] = "license.htm"; Entries[12][1] = "Software License"; Entries[12][2] = "INTEL SOFTWARE LICENSE AGREEMENT IMPORTANT READ BEFORE COPYING, INSTALLING OR USING . Do not copy, install, or use this software and any associated materials collectively, ..."; Entries[12][3] = ""; Entries[12][4] = "about above accompanied accompanying accuracy acknowledge adapt addition additional administrator advised affiliates after against agree alleges alpha alternate any appear applicable application apply arise assign assignable associated assume attempt attorney author authorized back been before below beta bound break business california capable carefully cause changes claim code collectively commercial compatible completeness component computer condition conflict conjunction consent consequential constitutes contain context contractor contracts control convenience convention copy copyright corporation correct costs could countries create creator customers damages data days death decompile defect delivered delivery derivatives design destroy developed development device dfars directly disassemble disclaims disclosure distribute documentation does done duplication emulated enclosed end engineer english entirety equipment errors estoppel et even event except excluding exclusion exclusive existing expense export express extent failure far fees final fitness following form forth found free fully function future goods governed government granted grants graphics guest harmless here herein hereunder hold i ii iii image immediately implication implied important inability incidental include incorporated indemnify indirectly inducement information injury install integral intel intellectual intended international interruption introduce items its iv jurisdiction kind labeled language larger last laws ldquo lease legal liability liable license life limitation limited links loss lost machine maintenance make manager manufacture manufacturer mask material may media medical merchantability minimum modify nations necessary negligent neither network ninety noninfringement nor normal note notice number obligated obligation occur oem offered officers operate organization original other otherwise out own ownership part particular party patent perform period personal physical please portions possibility pre prevent principles private problems product profits prohibit promised properly property proprietary protected provided provision purpose pursuant rdquo read reasonable recipient redistributables referenced regard regulates regulations related release remains remove rent replacement represent representative reproduce research resolve respect responsibility restricted restrictions retain return reverse revision right risk rsquo running safeguard sale sample saving seal secret section select sell separate seq set shall signed single site situation software sold source specifically standalone state subject sublicense subsidiaries successor such supersede suppliers support sustaining system tamper term terminate text then therein thereof these they third those time title trade trademark transfer translate treaty type unauthorized under understand unintended united unless until up update upon usage user vary version vi vii violate virtual warrant warranty was were whatsoever whole without work writing written"; Entries[13] = new Array(4); Entries[13][0] = "warranty.htm"; Entries[13][1] = "Limited Lifetime Hardware Warranty"; Entries[13][2] = "Limited Lifetime Hardware Warranty Intel warrants to the original owner that the adapter product delivered in this package will be free from defects in material ..."; Entries[13][3] = ""; Entries[13][4] = "above abuse accept accident adapter advance against agreement agrees air allow along alteration america any anyone applicable applications apply arise assume authorization authorizes back becomes before below business calling cannot care charge claims completely consequential contact container contract control costs cover critical current customer damage days dealer defective defects defend deficiency deliver department described details direct disaster disclaims discontinued distributors does either element energy entirely equivalent essential event example exceed except exclusion explanation express fitness foregoing forth found free full generation goodwill ground group guarantee hardware harmless health hereunder higher hold implied improper incidental including indemnify indirect infringement installation installed intel intellectual interruptions irrespective issue last level liability license licensee lieu lifetime limitation limited limiting locations loss material may measurable merchantability misuse modified money must neglect negligence neither new ninety noninfringement nor north notice notwithstanding nuclear number objectively obtain option original other out owner package paid part particular pay place policy possibility potential price process product profits proof property proposal provided purchase purpose received reconditioned refund registered remedies repair replace reprocurement resellers reserves respectively return revision right risk rma safety same sample satisfied see set shall ship software sole special specifically specification speculative states statutory sublicensees such support systems testing their thereof these they time tort total traffic transit under user's verifies wants warrants warranty were whether whom without workmanship"; Entries[14] = new Array(4); Entries[14][0] = "lights.htm"; Entries[14][1] = "Indicator Lights"; Entries[14][2] = "The Intel PRO/100+ adapter, PRO/100 S adapter, and PRO/100 VE and VM Desktop Adapters and Network Connections have the following indicator lights Label Indication Meaning ..."; Entries[14][3] = "connections indicator lights"; Entries[14][4] = "act act/lnk adapter amount appears between bit cable check configuration connection connector control data desktop driver dual faulty file flashes flashing following frequency go good indication indicator intel label last leds lights lnk mbps meaning modified network note off operating other panel pci per port power pro/100 problem receiving revision second sending server status switch system three traffic varies ve vm windows"; Entries[15] = new Array(4); Entries[15][0] = "mang_win.htm"; Entries[15][1] = "Power Management"; Entries[15][2] = "Setting up Power Saver options and Wake on LAN on Microsoft Windows operating systems."; Entries[15][3] = "management power remote wake wol"; Entries[15][4] = "ability acbs access accessible acpi active activity adapter advanced after allow amount any anyway apm appear auto automatically available battery between bios both bursts cable called capability capable complex computer configured connect consumption content control converged data dependant detect development device directed disabled disarms disconnected display down dual duplex during eee effect efficient enable ends energy engine enter et2 ethernet even evolved example explicitly expressmodule f4 feature few following forced full fully function functionality gigabit hibernate higher however i340 i350 idle important included includes including incorporated indicate installed intel interacting introduce keeps lan last latency led limited link lit low lowest lp magic manageability management manager may microsoft mode modified mt must needs negotiate network nic note off operating option other over override packet partner period pf port possible power previously pro/1000 proset pt quad r2 readily ready reconnected reduce remote removed replaces requests rest restored resume revision s3 s4 s5 saved saver server set several shutdown shutting simple sleep small speed standard standby state status stay support system t1 t2 t4 tab then there these they timeout traffic transition transmitted turns type under up using variety versions vista vt wake were windows wol x520 x540 xp years"; Entries[16] = new Array(4); Entries[16][0] = "manage.htm"; Entries[16][1] = "Remote Wake Up"; Entries[16][2] = "Remote Wake up and Wake on LAN basics."; Entries[16][3] = "lan remote wake wake-up"; Entries[16][4] = "ability about accept acpi activates adapter address administrators advanced allow amps any apm area around arp assigned attached awaken aware backwards based below bios board both bracket bus cable came capability capable check choosing circuitry clock compatibility complaint completely complex compliant components computer concept configure connection connector consecutive contact containing contains contents control converged corresponds could cpu current d815epea2 data defined description designed desktop details determine development device different directed disk documentation does done down draw drive driver due each early either enable equipped ethernet event every evolved example extends feature few field find first fit following format fully function generally gigabit had header hibernate hours however ibautil implementation important include information initiated installed intel interacting interface intermediate ip keyed label lan last least leds level limited list locations look low mac magic maintenance management manufacturer many may memory milliamps mode model modified more most motherboard mt multiple must named necessary need network newer note numbers off older operating operating system operational operations os out over own packet partial particular patterns pci per perform pila8460bn pila8460f pila8461 pila8900 pin plugged pme port power pro/100 pro/1000 proset protocol provide pwla8390t pwla8490xt quad querying ram rating received receives reduces referred refers refreshed reloaded remains remote removed repeated repetitions represents request require resolution response revision routed s0 s1 s2 s3 s4 s5 section see selectable selectively sending sent server set should shutdown signal similar simple sleep slot specific standby started state still stopped such supply support suspend swapped system t1 t2 technician then there these they through times titled true turning type typically under up upon user usually utility value variety various verify versions volt vt wake was were whereas without wol work x520 x540 xt years"; Entries[17] = new Array(4); Entries[17][0] = "overview.htm"; Entries[17][1] = "Overview"; Entries[17][2] = "Overview Welcome to the User's Guide for the Intel PRO/100 family of server adapters. This guide covers hardware and software installation, setup procedures, and troubleshooting ..."; Entries[17][3] = "hardware installation setup software troubleshooting"; Entries[17][4] = "adapter advanced any architecture authentication automatically available based basic click co column compatible computer configuration contents covers cpu decreasing driver enabled encryption family features follow functions further guide hardware here ia-32 includes increasing information install intel intensive ipsec itanium last latest left link list loaded make mode modified necessary network note now off offloads operating other overview platforms pro/100 problems procedure process processor refers review revision see select server set setup software start step supported sure system table these throughput tips topic troubleshooting tunnel up upgrading user's utilization varies welcome windows xp"; Entries[18] = new Array(4); Entries[18][0] = "prosetdm.htm"; Entries[18][1] = "Using PROSet"; Entries[18][2] = "Installing, using, and removing Intel PROSet for Windows Device Manager."; Entries[18][3] = "device install manager proset"; Entries[18][4] = "add/remove added additional administrator advanced automatically cd change cl command compatibility connection control core device dialog directory dmix drivers extension file following gigabit help install intel last line located manager modified must network note options panel please process product program proset prosetcl refer removing revision rights same select server services settings software support tabs under uninstall utility windows"; Entries[19] = new Array(4); Entries[19][0] = "reqs.htm"; Entries[19][1] = "System Requirements"; Entries[19][2] = "System requirements for Intel PRO/100 Server adapters."; Entries[19][3] = "32-bit 64-bit compatibility install pci pci-x requirements"; Entries[19][4] = "adapter advanced advantage architecture basic before bios bit bus check compatibility computer configuration dos drivers either following freebsd hardware hat higher hyper installed installing intel kernel last latest linux master met microsoft minimum mode modified must network open operating order pack pci platform pro/100 provided red requirements revision run server service slot software solaris sunsoft supplies support suse system takes v2 vendor vista windows xp"; Entries[20] = new Array(4); Entries[20][0] = "trbl_dm.htm"; Entries[20][1] = "Configuration and Troubleshooting"; Entries[20][2] = "Configuration and Troubleshooting Common Problems and Solutions There are many simple, easy to fix problems related to network problems. Review each one of these before ..."; Entries[20][3] = ""; Entries[20][4] = "ability accommodates active activity adapter addresses adjusting advanced affected after agent already among another any apparent applicable appropriate apps asked assumes attached attaining auto auxiliary available base basic been before behavior best better between bios boot bootagnt both bus cable cannot capabilities capacity card carrier category cause change check choose common communicate compatible compliant components computer configure conflicting conflicts connect connectivity connectors consider consistent contact cooling copper correct creating current customer damaged data default described desktop/management detect device diagnostic different disable discussion disrupted documented does down driver duplex each easy edge efficiency either enable enhanced environment established etc even exact examples exceed execution expected express fail familiar family fan feature find fix following forced frame frequently functioning further gigabit going hangs hardware here hub ibautil idle ieee implementation impose inability incompatible indicator information insert install instructions intel intended interrupt irq isn't issues jumbo kinked knowledge known lack lan last latency latest layer led length level light limited limits link list loaded look loose make manually many master match maximizing maximum may mbps memory mode modified monitor more multi multiple multiprocessor must necessarily need negotiate network newer note off offloading often operating operation opposed options os other over overdraw pair parameters partner pass pci pcie peak perform performance physical play plug points port possible power pre presence prevents problem process processor programs proper provide pxe quality questions rate re readme reboot receive recent recognized recommended related release reload replace reports represents require reserve responder resulting results review revision run rx same seat section securely see select send server service set several shared sharing shorter signal simple size slave slot slowest slowing software solution specific speed standard start stops such sufficient supply support sure switch system table teaming technically test them then there these threading time timer traffic transmission triggering trouble troubleshooting tx type unable under unload unpredictable unusual up upgrade utility v1 v2 vary verify version vlans wake while without wol wording work"; Entries[21] = new Array(4); Entries[21][0] = "pushinst.htm"; Entries[21][1] = "Microsoft Windows Push Install Instructions"; Entries[21][2] = "Microsoft Windows Push Install Instructions A Push, or unattended, installation provides a means for network administrators to easily install the drivers on systems that have ..."; Entries[21][3] = "driver install installation push unattended"; Entries[21][4] = "adapters administrators applies apps basic bit cd directory document download drivers easily equipment file following includes install instructions intel last means microsoft modified network operating product provides push push32 pushx64 r2 revision see server setup similar systems unattended vista win32 windows winx64 x64 xp"; Entries[22] = new Array(4); Entries[22][0] = "qos.htm"; Entries[22][1] = "Quality of Service QoS"; Entries[22][2] = "A brief discussion of Quality of Service QoS)."; Entries[22][3] = "balance load qos quality service tagging team"; Entries[22][4] = "adapter advanced allow bandwidth base before configured connected deal disabled does efficient enabled events first frame generation gigabit help high ieee implement include information intel knowledge last levels lower make microsoft modified more most must network note operating order packet prioritization priority priority/vlan pro/1000 processed programs proset pwla qos quality r2 real receive revision see send server service setting specify support switch system tab tagged tagging time under utility vista vlan windows xp"; Entries[23] = new Array(4); Entries[23][0] = "reg100s.htm"; Entries[23][1] = "Regulatory Information"; Entries[23][2] = "Regulatory Information Intel PRO/100 S Server Adapter Intel PRO/100 S Dual Port Server Adapter Safety Compliance UL 60950 1 Second Edition CAN/CSA C22.2 No 60950 ..."; Entries[23][3] = ""; Entries[23][4] = "a1 a11 a2 about accept accordance adapter against antenna any as/nzs australia/new australian authority back based been below between bsmi c22 can/csa canada canadian cause caution ce certification changed china circuit cispr class classe cns13438 communications community compatibility compliance comply conditions conducted conformance conformity connect consult contact control corporation correct council country dealer declaration declares described designed determined device different digital directive distributor disturbance document does dual edition efup elam electromagnetic emc emi emissions ems en en55022 en55024 encouraged end energy equipment eu european experienced fcc following found frequency general generates guarantee harmful help her hillsboro his home however ices iec immunity including increase industry information installation installed instructions intel interference international japan jf3 kcc korea last life limits listed low lvd mailstop manufacturer mark may measures modified more must ne nmb note notice occur off office operate outlet parkway part particular party people's permission phone port pro/100 product protection provide pursuant radiate radio radio/tv reasonable received receiver receiving reception recognition recycling regulatory relocate reorient republic required requirements residential responsible retailer revision rf rohs rules safety second separation server standards statement subject systems taiwan take technician technology television tested there these tick turning ul undesired union upon usa user vary vcci void voltage without young zealand"; Entries[24] = new Array(4); Entries[24][0] = "save_dm.htm"; Entries[24][1] = "Save and Restore"; Entries[24][2] = "Saving and restoring an adapter's configuration on systems running Microsoft Windows operating systems."; Entries[24][3] = "function intel proset restore save"; Entries[24][4] = "adapter administration allows any assumed backup been changed command configuration contained copy cscript current default directory disk diskette dmix drive driver error event example failure file filename floppy following former generally hard include intel just last line located may measure modified most multiple must navigate network notes open operation options os performed privileges program prompt receive reinstate requires restore result revision run same save savresdx script settings specified standalone such syntax system team these times tool type unstable using vbscript vlans was windows wmiconf"; Entries[25] = new Array(4); Entries[25][0] = "setbd_dm.htm"; Entries[25][1] = "Unattended Installation"; Entries[25][2] = "Installing the base drivers and Intel PROSet via the command line."; Entries[25][3] = "base driver install proset setupbd"; Entries[25][4] = "able above acceleration actions adapters add/remove advanced after agent already any application apply appropriate apps associated assume available base bd been between bios capable case cd change channel characters chinese chipset codes com/en command commonly complete components components/features configure core corresponds created current dcb default definition describes description deselect detects device different directory disable displays dmix does driver during dxsetup error ethernet even example exist fatal fcoe feature fibre file filename first flexibility folder following force full function get gui hide http i i/o i/oat ignored image include information instability install install/upgrade instructions intel invalid iscsi itanium known language last launches layouts level line list local log makes manager messages method microsoft modify more most msdn msi msiexec mst must necessarily need network note operating option other over package passed path preferred prior productcode programs properly property proset prosetcl prosetdx prounstl provided provides public reboot recommends reduced refer reinstall remove repair result return revision running same searches section see select selected/displayed sensitive server set setup setupbd should silent snmp space specific specify start status strings support switch syntax system system32 takes technology tested them then transform translates typical unattend under uninst uninstall updates uppercase us/library utility valid via warnings website white win32 win64 windows winnt without x64 xp"; Entries[26] = new Array(4); Entries[26][0] = "snmpwin.htm"; Entries[26][1] = "Simple Network Management Protocol SNMP"; Entries[26][2] = "Installing SNMP on Microsoft Windows operating systems."; Entries[26][3] = "agent management network protocol simple snmp"; Entries[26][4] = "about adapter additional administrators advanced agent alerts allow application autorun base before cd changes click communicate compile compliant computer configuration consoles database devices directory documentation download drivers employed event experienced features first follow information install instructions intel last manage menu mib microsoft modified more must network notices operating prior product protocol provides recognize revision screen see send should simple snmp software software/services specified start stations such support system tcp/ip teaming them translates updates utility vlans windows"; Entries[27] = new Array(4); Entries[27][0] = "team_dm.htm"; Entries[27][1] = "Teaming"; Entries[27][2] = "Description of ANS teaming modes."; Entries[27][3] = "advanced aft alb ans services sft static team teaming"; Entries[27][4] = "able according across act active adapter adaptive additional address adopted advanced advantage affected affects aft aggregation aggregator alb allow alternatively although among analyzes another any appear appropriately associated assure attention auto automatic availability available avoid back backup balance bandwidth base because becomes becoming been before begin behavior belong benefit best between beyond both bound bridging button cable cannot capability capable case cause cd center change channel check choose cisco click clients column combination common compatibility compatible component computer conditions configure connect connectivity consider contain contents continue control copper create critical currently data default delay denominator dependencies dependent design designated destination detect developed device different disable disconnect displayed documentation does don't download driver duplex during duties dynamic each effect eight either enable engine ensure etherchannel ethernet/data event example exceed experience failback failed failover fails failure fallback fast fault fcoe/dcb feature fec fiber fibre first five following force formed frame full fully functionality gbps gec gets gigabit go good grouping handles hardware highest hot however hub hyper ieee implement important inactive include increase information initial instability install integrated intel interface ip ipx issues jumbo last later latest least left lets like link list load located loms long lose loss lost lowest machine maintain make management manager manually manufacturers match maximum may member microsoft might mixed mode model modify monitored monitoring more multi multicast multiple must mvt needed negotiate netbeui network never new nic nlb/wlbs normal notes occur offload open operate options order original other over package packet pairing pane part particular pay per performance performing plug port possible preferred prevent primary primary/secondary prior priority pro/100 property proset protocol provide qos r2 rate receive reception recognize recommended recommends reconfigures redundancy regains rejoin releases reliability reload remains removed removing renamed replaces require respective restart restored restricted returned revision rlb routable routed rss run rx safety same schema second secondary see select send separate server service set several sft sheet should similar simultaneous single sla software spanning specific specify speed standard standby start static status still stp subnet such support sure switch system tab table tagging take tcp tcp/ip team technology temporary them then there these they third three throughput toe together tolerance traffic transfer transmission transmit tree tx type under until up updated various vary vendor verify version virtual vlan vmlb waiting waits way we window wizard works would"; Entries[28] = new Array(4); Entries[28][0] = "test_dm.htm"; Entries[28][1] = "Test the Adapter"; Entries[28][2] = "Testing the adapter in Windows and other operating systems."; Entries[28][3] = "diagnostics test"; Entries[28][4] = "about access adapter address allows availability below cable capabilities click communicate connection connects dependent determines device diagnostic displays does duplex each functioning hardware including information intel ip its last link lower manager maximum microsoft modified network operating optimum partner performed ping properly properties proset provide reason reports revision run select settings several speed system tab test these type whether window"; Entries[29] = new Array(4); Entries[29][0] = "trbl_win.htm"; Entries[29][1] = "Troubleshooting"; Entries[29][2] = "Troubleshooting PCI and PCI X adapters."; Entries[29][3] = "bus pci pci-x performance troubleshooting"; Entries[29][4] = "adapter after allow any appear attached automatically available been bios cannot cause clear code computer deleted device disable driver enable error event file full functionality functioning gigabit gives information install intel issues known last latest longer make manager may message microsoft modified need older open operating os play plug present problem process proset re rebooting reinstall replacing reviewed revision server session set ship should simultaneous software solution specific start support sure system table terminal then there these time trouble update upgrading versions viewer windows xp"; Entries[30] = new Array(4); Entries[30][0] = "vlwin.htm"; Entries[30][1] = "Join a Virtual LAN under Windows OS"; Entries[30][2] = "How to configure VLANs on adapters installed in systems running Microsoft Windows."; Entries[30][3] = "lans virtual vlan"; Entries[30][4] = "ability across adapter adds administration advanced any area attached based before between both broadcast building campus capability caution change child clients co collection communicate computers configure connecting connections connects considerations considered consist contents cross defined department desktop devices different dispersed each ease enterprise environments exist first functional geographically group hardware hyper ieee improve including information intel joint lan last least left limit local locations logical management match maximum membership microsoft minimize modified more most moves multiple must network note other pane parent partition per performance physical port pro/100 problems project proset protocol refers restricted revision running same security segments select servers set simplify software storms support switch tab table tagged tagging task team term them then they those together typically under untagged up updates users ve virtual vlan vm were window workers workgroups working"; Entries[31] = new Array(4); Entries[31][0] = "wminicdm.htm"; Entries[31][1] = "WMI NIC Provider"; Entries[31][2] = "Intel Network Adapters WMI Provider The Intel Network Adapters Windows Management Instrumentation WMI Provider enables WMI based management applications such as Intel PROSet for Windows ..."; Entries[31][3] = "provider wmi"; Entries[31][4] = "about access adapter allows any application apps assumptions available based between called cannot cim classes collected common configure consumer contains could data describes detailed device distribution dmi docs driver elevate embed enables enterprise external file format gigabit guide i independent information install instances instrumentation intel intelncs2 interfaces jointly kernel last layer level list local located makes manage manager manifest measurement microsoft middleware missing mode modified monitor more must namespace ncs2 network operate order page paper part pci pipeline platform please pro/100 proset provided provider refer reference registers related remote requirements revision root section see services set setup snmp software specification standards status such supported supports system technical technology then through type typical under user view vista wbem web windows wmi"; DOCS/SERVER/save_dm.htm0000755000000000000000000000712211656574604011655 0ustar Save and Restore

Saving and Restoring an Adapter's Configuration Settings

The Save and Restore Command Line Tool is a VBScript (SavResDX.vbs) that allows you to copy the current adapter and team settings into a standalone file (such as on a floppy disk) as a backup measure. In the event of a hard drive failure, you can reinstate most of your former settings.

The system on which you restore network configuration settings must have the same configuration as the one on which the save was performed.

NOTES:
  • You must have Administration privileges to run scripts. If you do not have Administration privileges, you will not receive an error, the script just will not run.
  • Only adapter settings are saved (these include ANS teaming and VLANs). The adapter's driver is not saved.
  • Restore using the script only once. Restoring multiple times may result in unstable configuration.
  • The Restore operation requires the same OS as when the configuration was Saved.

Command Line Syntax

cscript SavResDX.vbs save|restore [filename]

SavResDX.vbs has the following command line options:

save Saves adapter and team settings that have been changed from the default settings.  When you restore with the resulting file, any settings not contained in the file are assumed to be the default.
restore Restores the settings.
filename The file to save settings to or restore settings from.  If no filename is specified, the script default to WmiConf.txt.

Examples

Save Example

To save the adapter settings to a file on a floppy diskette, do the following.

  1. Open a Windows Command Prompt.
  2. Navigate to the directory where SavResDX.vbs is located (generally c:\Program Files\Intel\DMIX).
  3. Type the following:

    4. cscript SavResDX.vbs save a:\settings.txt

Restore Example

To restore the adapter settings from a file on a floppy diskette, do the following:

  1. Open a Windows Command Prompt.
  2. Navigate to the directory where SavResDX.vbs is located (generally c:\Program Files\Intel\DMIX).
  3. Type the following:

    4. cscript SavResDX.vbs restore a:\settings.txt

Last modified on 2/10/10 3:18p Revision

DOCS/SERVER/setbd_dm.htm0000755000000000000000000006127511656741062012023 0ustar Unattended Installation

Installing the Base Driver and Intel® PROSet via the Command Line

Installation Methods

Installing with DxSetup.exe

Command Line Options for msiexec.exe

Using SetupBD.exe to Install Base Drivers on Windows Server* Core Operating Systems

Uninstalling Drivers and Intel PROSet

Installation Methods

DxSetup.exe is the preferred installation method. You can use it to install the base Windows base drivers and Intel® PROSet for Windows* Device Manager.

NOTES: 
  • Windows XP x64 and Windows Server 2003 x64 do not support unattended driver installation.
  • Intel® 10GbE Network Adapters do not support unattended driver installation.
  • Intel PROSet can be installed with DxSetup.exe or msiexec.exe. Intel recommends using DxSetup.exe. DxSetup.exe detects the system's language, searches for the appropriate transform file, and applies it to MSI package. The transform file translates the installation instructions to the language associated with your operating system.

You can use the base driver install utility (SetupBD.exe) to install Microsoft Windows base drivers from a command line. If you use SetupBD.exe to install base drivers, you will not be able to use the advanced features in Intel PROSet.

Installing with DxSetup.exe

This section describes how to use DxSetup.exe to install the base drivers and Intel PROSet for Windows Device Manager from the command line.

NOTE: Intel PROSet can be installed with DxSetup.exe or msiexec.exe. Intel recommends using DxSetup.exe. DxSetup.exe detects the system's language, searches for the appropriate transform file, and applies it to MSI package. The transform file translates the installation instructions to the language associated with your operating system.

DxSetup.exe is a setup utility used for installing Intel PROSet. It detects the system language, searches for the appropriate transform file in the same folder, and then launches PROSETDX.msi in the language specific to the operating system. The transform file translates the installation instructions to the language associated with your operating system.

DxSetup.exe also takes the install options from the command line and applies them to the PROSETDX.msi command line installation.

DxSetup.exe command line switches:

Switch Description
/q[r|n] silent install options.

r Reduced GUI Install
n Silent install
/l[i|w|e|a] log file option.
i log status messages.
w log non-fatal warnings.
e log error messages.
a log the start of all actions.

DxSetup.exe Public Properties

Property Definition
BD "0", do not install base drivers.

"1", install the base drivers (default).

NOTE: BD should only be set to 0 if the Base Drivers have already been installed prior to running DxSetup.exe
ANS "0", do not install ANS.

"1", select ANS (default).
DMIX "0", do not install Intel PROSet.

"1", install Intel PROSet (default).
FCOE "0", do not install Fibre Channel Over Ethernet (FCoE) using DCB (default).

"1", install FCoE.

ISCSI "0", do not install iSCSI using DCB (default).

"1", install iSCSI using DCB.

SNMP "0", do not install the SNMP Agent (default).

"1", install the SNMP Agent.

 

NOTES:
  • If you specify a path for the log file, the path must exist. If you do not specify a complete path, the install log will be created in the current directory.
  • The ANS property should only be set to ANS=1 if DMIX=1 is set. If DMIX=0 and ANS=1, the ANS=1 is ignored and only the base driver will be installed.
  • Even if FCOE=1 is passed, FCoE will not be installed if the operating system and installed adapters do not support FCoE.
  • Even if ISCSI=1 is passed, iSCSI using DCB will not be installed if the operating system and installed adapters do not support it.
  • Public properties are case sensitive. All characters are uppercase with no white space between characters. For example:

DxSetup.exe /qn ANS=1

Any white space in "ANS=1" makes the setting invalid. "ans=1" is not a valid setting.

Command line examples

You can modify the paths for different operating systems and CD layouts and apply the command line examples.

  1. The following launches a typical install silently:

    DxSetup.exe /qn /liew install.log

    NOTE: BD, ANS and DMIX are selected by default.

  2. How to install components but deselect ANS. Set the ANS=0 in the command line:

    DxSetup.exe /qn ANS=0 /liew install.log

msiexec.exe command line options

Refer to Microsoft's website for the most current information on msiexec.exe command line options: http://msdn.microsoft.com/en-us/Library

NOTES:

  • Not all command line options Microsoft provides with msiexec.exe have been tested or are necessarily supported for Intel PROSet installation.

  • Msiexec.exe also sets an error level on return that corresponds to system error codes: http://msdn.microsoft.com/en-us/Library

  • Intel PROSet can be installed with DxSetup.exe or msiexec.exe. Intel recommends using DxSetup.exe. DxSetup.exe detects the system's language, searches for the appropriate transform file, and applies it to MSI package. The transform file translates the installation instructions to the language associated with your operating system.

Command Line Switches

This section describes how to install Intel PROSet using PROSETDX.msi and msiexec.exe from the command line.

C:\WINNT\System32\msiexec.exe /i PROSETDX.msi /qn /liew install.log

Most commonly used msiexec.exe command line options:

Switch Description
/i install
/x uninstall
/q[r|n] silent install options.

 

r Reduced GUI Install
n Silent install
 
/l[i|w|e|a] log file option.
i log status messages.
w log non-fatal warnings.
e log error messages.
a log the start of all actions.
Transforms A property used to apply transforms (a .mst file) to an MSI package. The following example applies a Chinese language transform to MSI package, so the installer displays Chinese strings during installation:
 
TRANSFORMS=2052.mst

Silent install/upgrade command line syntax

The following launches a typical installation of PROSETDX.msi.

<Full path to msiexec.exe> /i <Full path to PROSETDX.msi> /qn /liew install.log

Silent uninstall command line syntax

The following uninstalls all the Intel PROSet components. It can be used when the path to PROSETDX.msi is available.

<path to msiexec.exe> /x <path to PROSETDX.msi> /qn /liew uninstall.log

The following uninstalls all the Intel PROSet components. It can be used when the path to PROSETDX.msi is not available but the ProductCode of MSI package is known.

<path to msiexec.exe> /x <ProductCode of PROSETDX.msi> /qn /liew uninstall.log

Command line options supported by PROSETDX.msi

PROSETDX.msi provides public properties that can be used to change Intel PROSet install selections from the command line.

By setting the properties in the command line, you can disable and hide some features in PROSETDX.msi, or force some feature to be selected/displayed. This provides the flexibility to install different components/features in Intel PROSet.

Following is the list of public properties provided by PROSETDX.msi:

Property Definition
BD "0", do not install base drivers.

"1", install the base drivers (default).

NOTE: BD should only be set to 0 if the Base Drivers have already been installed prior to running DxSetup.exe
ANS "0", do not install ANS.

"1", select ANS (default).
DMIX "0", do not install Intel PROSet.

"1", install Intel PROSet (default).
FCOE "0", do not install Fibre Channel Over Ethernet (FCoE) using DCB (default).

"1", install FCoE.

ISCSI "0", do not install iSCSI using DCB (default).

"1", install iSCSI using DCB.

SNMP "0", do not install the SNMP Agent (default).

"1", install the SNMP Agent.

 

NOTES:
  • If you specify a path for the log file, the path must exist. If you do not specify a complete path, the install log will be created in the current directory.
  • The ANS property should only be set to ANS=1 if DMIX=1 is set. If DMIX=0 and ANS=1, only the base driver will be installed.
  • Even if FCOE=1 is passed, FCoE using DCB will not be installed if the operating system and installed adapters do not support it.
  • Even if ISCSI=1 is passed, iSCSI using DCB will not be installed if the operating system and installed adapters do not support it.
  • Public properties are case sensitive. All characters are uppercase with no white space between characters. For example:

msiexec.exe /i PROSETDX.msi /qn ANS=1

Any white space in "ANS=1" makes the setting invalid. "ans=1" is not a valid setting.

Command line install examples

Assume that C:\WINNT\System32 is the system32 folder and PROSETDX.msi is under the D:\Apps\PROSETDX\Win32 folder. You can modify the paths for different operating systems and CD layouts and apply the command line examples.

1.      How to install Intel PROSet silently on Windows XP:

C:\WINNT\System32\msiexec.exe /i D:\Apps\PROSETDX\Win32\PROSETDX.msi /qn /liew install.log

2.      How to install Intel PROSet silently on Windows Server 2003 for Itanium®-based systems:

C:\WINNT\System32\msiexec.exe /i D:\Apps\PROSETDX\Win64\PROSETDX.msi /qn /liew install.log

3.      How to install components but deselect ANS:

Set the ANS=0 in the command line, for example:

C:\WINNT\System32\msiexec.exe /i D:\Apps\PROSETDX\Win32\PROSETDX.msi /qn ANS=0 /liew install.log

4.      How to apply a transform file to MSI using msiexec.exe:

Set the TRANSFORMS=filename.mst in the command line. For example:

C:\WINNT\System32\msiexec.exe /i D:\Apps\PROSETDX\Win32\PROSETDX.msi /qn TRANSFORMS=2052.mst /liew install.log

NOTE: Intel recommends using DxSetup.exe to install Intel PROSet. DxSetup.exe detects the system's language, searches for the appropriate transform file, and applies it to MSI package.

Command line uninstall example

NOTE: Do not use the "ANS" option when uninstalling Intel PROSet from a command line.

First get the path of PROSETDX.msi in the local system or any other image path when you installed Intel PROSet, then use msiexec.exe to uninstall Intel PROSet.

For example, assume that C:\Windows\System is the System folder and PROSETDX.msi is in d:\unattend, then the command line will be:

C:\Windows\System\msiexec.exe /x d:\unattend\ PROSETDX.msi /qn /liew uninst.log

Command line reinstall / repair

If you need to repair an Intel PROSet installation, uninstall the application and then reinstall it. See the uninstall and install examples above for more information.

Using SetupBD.exe to Install Base Drivers on Windows Server* Core Operating Systems

NOTE: If you want to use prosetcl.exe to configure your adapters, you must use DxSetup.exe to install drivers and Intel PROSet. SetupBD.exe only installs the base drivers.

Command Line Options

SetupBD.exe supports the following command line switches. 

NOTE: You must include a space between switches.
Switch Description
/s silent install with no reboot
/r force reboot (must be used with the /s switch)
/nr no reboot (must be used with the /s switch. This switch is ignored if it is included with the /r switch)

Examples:

Option Description
SetupBD

Installs and/or updates the driver(s) and displays the GUI.
SetupBD /s Installs and/or updates the driver(s) silently.
SetupBD /s /r Installs and/or updates the driver(s) silently and forces a reboot.
SetupBD /s /r /nr Installs and/or updates the driver(s) silently and forces a reboot (/nr is ignored).

Other information

NOTES:
  • If you install drivers on a system based on a server chipset and BIOS that are Intel I/OAT capable, the /s switch (silent install) forces a reboot without the /r switch. If you do not want the system to reboot, use the /nr switch.
  • For Intel® I/O Acceleration Technology to function properly, you must reboot after driver installation.

You can use the /r and /nr switches only with a silent install (i.e. with the "/s" option).

Uninstalling Drivers and Intel PROSet

Intel recommends you use Add/Remove Programs to uninstall Intel PROSet and the base drivers. If your operating system does not have a GUI installed, you can use msiexec.exe to uninstall the base drivers and Intel PROSet.

If you only installed base drivers, you can use the PROUnstl.exe utility to remove them.

NOTE: PROUnstl.exe only removes the base drivers. Do not use this utility if Intel PROSet is installed on your system. Removing the base drivers without removing Intel PROSet will result in system instability.

PROUnstl.exe supports the following command line switch:

Switch Description
/nogui silent uninstall.

Last modified on 3/07/11 11:02p Revision

DOCS/SERVER/sit100.js0000755000000000000000000013546511701554304011101 0ustar /********************************************************************** ** ** ** I N T E L P R O P R I E T A R Y ** ** ** ** COPYRIGHT (c) 2005-2012 BY INTEL CORPORATION. ALL ** ** RIGHTS RESERVED. NO PART OF THIS PROGRAM OR PUBLICATION MAY ** ** BE REPRODUCED, TRANSMITTED, TRANSCRIBED, STORED IN A ** ** RETRIEVAL SYSTEM, OR TRANSLATED INTO ANY LANGUAGE OR COMPUTER ** ** LANGUAGE IN ANY FORM OR BY ANY MEANS, ELECTRONIC, MECHANICAL, ** ** MAGNETIC, OPTICAL, CHEMICAL, MANUAL, OR OTHERWISE, WITHOUT ** ** THE PRIOR WRITTEN PERMISSION OF : ** ** ** ** INTEL CORPORATION ** ** ** ** 2200 MISSION COLLEGE BOULEVARD ** ** ** ** SANTA CLARA, CALIFORNIA 95052-8119 ** ** ** **********************************************************************/ var Results = new Array(); var URLTarget = "_blank"; var Document = document; var PathDiv = "\\"; var SearchList = new Array(); var ExcludeList = new Array(); var CurEntries = new Array(); function Search() { if (arguments.length == 0) return; if (typeof Array.prototype.splice == "undefined") Array.prototype.splice = Splice_Fcn; if (typeof navigator.userAgent != "undefined") { var browser = navigator.userAgent.toLowerCase(); if ((browser.indexOf("netscape") == -1) && (browser.indexOf("firefox") == -1) && (browser.indexOf("gecko") == -1)) URLTarget="_self"; } if (typeof window.location.pathname != "undefined") { var nIdx = window.location.pathname.indexOf('/'); if (nIdx != -1) PathDiv = "/"; } ClearArrays(); var Exclude_Warning = ""; var FrameCnt = top.frames.length; if (FrameCnt != 0) Document = top.frames[FrameCnt-1].document; for (i=0; i < arguments.length; i++) { if (arguments[i].toString().indexOf(" ") == -1) AddToSearchArray(arguments[i].toString()); else { var arg_array = arguments[i].toString().split(" "); for (j=0; j < arg_array.length; j++) { var current = arg_array[j]; if (current == "") continue; if ((current == "+") || (current == "-")) { var next = arg_array[++j]; while ((next == "") && (j < arg_array.length+1)) next = arg_array[++j]; current = current + next; } AddToSearchArray(current); } } } Document.clear(); Document.write(""); Document.write(""); Document.write(""); Document.write(""); Document.write(""); Document.write(""); Document.title = "Search Results"; Document.write("

Search Results

"); Document.write("
"); Document.write("
"); if (ExcludeList.length != 0) { for (j=0; j < Entries.length; j++) { var ExcCount = 0; for (i=0; i < ExcludeList.length; i++) { ExcCount += GetEntryCount(Entries[j], ExcludeList[i]); if (ExcCount != 0) break; } if (ExcCount == 0) CurEntries[CurEntries.length] = Entries[j]; } } else CurEntries = Entries; for (i=0; i < SearchList.length; i++) { if (Exclude.indexOf(SearchList[i]) != -1) { if (Exclude_Warning != "") Exclude_Warning += ", "; Exclude_Warning += SearchList[i]; } else { FindString(SearchList[i]); } } if ((SearchList.length == 0) && (ExcludeList.length != 0)) FindString("*"); if (Exclude_Warning != "") { Document.write("

" + Exclude_Warning + ""); if (Exclude_Warning.indexOf(",") != -1) Document.write(" are common words and were ignored.
"); else Document.write(" is a common word and was ignored.
"); } for (i=0; i < Results.length; i++) { Document.write("
"); WriteResult(Results[i][1], Results[i][0], Results[i][2]); } if (Results.length == 0) { var OutStr = ""; for (i=0; i < arguments.length; i++) OutStr += " " + arguments[i]; Document.write("
"); Document.write("Your search - " + OutStr + " - did not match any documents."); Document.write("

Suggestions:
- Make sure all words are spelled correctly.
- Try different keywords
- Try more general keywords
"); } Document.write(""); Document.write(""); Document.close(); ClearArrays(); } function AddToSearchArray(str) { if (str.indexOf("+") != -1) { var len = SearchList.length; if (len != 0) { len--; SearchList[len] = SearchList[len] + str; } else SearchList[0] = str; } else if (str.indexOf("-") == 0) { str = str.substring(1, str.length); ExcludeList[ExcludeList.length] = str; } else SearchList[SearchList.length] = str; } function WriteResult(page_name, page_url, description) { if (arguments.length != 3) { return null; } if (description == "") description = "No description available"; if ((PathDiv == "/") && (page_url.indexOf("\\") != -1)) page_url = page_url.replace("\\", "/"); Document.write("
"+page_name+""); Document.write("
" + description); } function FindString(str) { for (j=0; j < CurEntries.length; j++) { var Count = 0; if (str == "*") Count += 1; Count += GetEntryCount(CurEntries[j], str); if (Count != 0) AddToResults(CurEntries[j][0], CurEntries[j][1], CurEntries[j][2], Count); } } function GetEntryCount(theEntry, str) { if (theEntry.length != 5) return 0; str = str.toLowerCase(); var Count = 0; if (str.indexOf("+") != -1) { var str_array = str.split("+"); var c1 = GetEntryCount(theEntry, str_array[0]) var c2 = GetEntryCount(theEntry, str.replace(str_array[0] + "+", "")); if ((c1 != 0) && (c2 != 0)) Count = c1 + c2; } if (theEntry[1].toLowerCase().indexOf(str) != -1) Count += 8; if (theEntry[2].toLowerCase().indexOf(str) != -1) Count += 5; if (theEntry[3].indexOf(str) != -1) Count += 10; if (theEntry[4].indexOf(str) != -1) Count += 1; return Count; } function AddToResults(url, name, desc, count) { for (k=0; k < Results.length; k++) { if (Results[k][0] == url) { count = Results[k][3] + count; Results.splice(k, 1); break; } } var NewIdx = Results.length; for (l=0; l < Results.length; l++) { if (Results[l][3] <= count) { NewIdx = l; break; } } var NewEntry = new Array(4); NewEntry[0] = url; NewEntry[1] = name; NewEntry[2] = desc; NewEntry[3] = count; Results.splice(NewIdx, 0, NewEntry); } function Splice_Fcn() { if (arguments.length < 2) return; var InsertIdx = arguments[0]; var Count = arguments[1]; var tmp = new Array(); var ModArray = new Array(); var i = 0; for (i = 0; i < InsertIdx; i++) tmp[tmp.length] = this[i]; for (i = 2; i < arguments.length; i++) tmp[tmp.length] = arguments[i]; for (i = InsertIdx + Count; i < this.length; i++) tmp[tmp.length] = this[i]; for (i = 0; i < tmp.length; i++) this[this.length] = tmp[i]; return ModArray; } function ClearArrays() { Results = new Array(); SearchList = new Array(); ExcludeList = new Array(); CurEntries = new Array(); } var Exclude = "a add all also an and and/or are as at be but by can did do for from has have how id if in into is it no non not of on once one only onto or so some than that the this to too try two use want well what when where which why will with within yes you your"; var Entries = new Array(); Entries[0] = new Array(4); Entries[0][0] = "ad_100s.htm"; Entries[0][1] = "Supported Adapters Server Pro/100"; Entries[0][2] = "Supported Intel PRO/100 Server This driver and software are designed to operate with the following Intel PRO/100 server adapters Product Name Board ID # &dagger ..."; Entries[0][3] = "adapters connections software"; Entries[0][4] = "a56831 adapter barcode board card code com/support/go/network/adapter/home controller dagger designed devices digit driver dual extension following front guide htm http intel last microsoft modified name operate port printed pro/100 product revision see server software sticker support vista windows xxx"; Entries[1] = new Array(4); Entries[1][0] = "cable.htm"; Entries[1][1] = "Attach the RJ45 Network Cable"; Entries[1][2] = "How to attach an RJ45 network cable to your adapter."; Entries[1][3] = "cable port rj45"; Entries[1][4] = "accommodate according achieve adapter addition allows any association's attach auto automatically based better between cable cases cat category caution ceilings cispr compatible compliance complies configure connect controller copper cross depending devices directly dual duplex either en50174 en55024 environment eus feature fire following gigabit industry information insert insure intel intended last length less limited link make manually may mbps mdi meters models modified more must negotiate network note operation over pair partner plenum port properly rated recommendations residential revision rj45 rooms runs safety see segment set shielded should shown single specification speed sure telecommunications terminated through tia twisted types up walls website wiring without"; Entries[2] = new Array(4); Entries[2][0] = "drivers.htm"; Entries[2][1] = "Install the Drivers"; Entries[2][2] = "Installing Microsoft Windows drivers for your adapter."; Entries[2][3] = "drivers install"; Entries[2][4] = "acceptable adapter add/remove after already any apply attempts automatically autorun before below cable cancel cannot cd click computer confirmation connections control dialog discovers displayed displays double download driver extracted files find follow found hardware insert install instructions intel intervention last located microsoft modified network new notes ok operating package panel plug procedure product programs r2 recommended regardless release revision runs screen select server software start support system them these transfer uninstall update user versions vista website whether window without wizard xp"; Entries[3] = new Array(4); Entries[3][0] = "support.htm"; Entries[3][1] = "Intel Customer Support"; Entries[3][2] = "Customer Support Intel support is available on the web or by phone. Support offers the most up to date information about Intel products, including installation ..."; Entries[3][3] = ""; Entries[3][4] = "about available corporate customer date general including information installation instructions intel internet last modified most network offers phone product revision site support tips troubleshooting up web"; Entries[4] = new Array(4); Entries[4][0] = "dupwindm.htm"; Entries[4][1] = "Configuring Speed and Duplex in Windows"; Entries[4][2] = "How to configure an adapter's speed and duplex under Microsoft Windows."; Entries[4][3] = "duplex link speed"; Entries[4][4] = "adapter administrators advertises allow always appropriate attach attempt auto available based been best cannot capable caution change choose click configure connections considerations copper default determine device differently direct disabled does down duplex either enabled establish experienced fiber force full gbps gigabit half identical ieee intel last like link manager manually match may mbps menu microsoft mode modified modules multi must native navigate need negotiate network ok older open operate option packets partner pass per performance performs present pro/100 properties pull receive requires revision runs same select send set sfp should specific speed suffer support switch tab their time up using windows would"; Entries[5] = new Array(4); Entries[5][0] = "hotwin.htm"; Entries[5][1] = "PCI Hot Plug Support for Microsoft Windows"; Entries[5][2] = "PCI Hot Plug Support for Microsoft Windows Operating Systems Intel network adapters are enabled for use in selected servers equipped with PCI Hot Plug support ..."; Entries[5][3] = "hot pci plug"; Entries[5][4] = "adapter address back before conflict connecting details documentation driver elsewhere enabled ensure equipped hardware hot identical information intel last mac member microsoft modified more network nic notes occur operating original pci plug remove replacement restore revision running see selected server setting sla support switch systems team unless up windows works"; Entries[6] = new Array(4); Entries[6][0] = "insert.htm"; Entries[6][1] = "Insert the Adapter"; Entries[6][2] = "Step by step instructions on how to install a PCI or PCI X adapter into a system."; Entries[6][3] = "hot install pci plug"; Entries[6][4] = "adapter additional anything before bit bracket bus case cause caution compatible computer configuration connected connector contacts contents cord could cover damage determine documentation down each edge electrical enabled end endanger error exposed failure firmly function get hot insert install instructions it's last later make master may modified off operating pci plug power problem push remove repeat replace required revision running screw seated secure see select shut slot special start steps still supports sure system table then through touch troubleshooting turn unplug until would"; Entries[7] = new Array(4); Entries[7][0] = "ipmi.htm"; Entries[7][1] = "IPMI Manageability"; Entries[7][2] = "IPMI Manageability Overview The Intelligent Platform Management Interface IPMI allows you to monitor server physical health characteristics, such as temperature, voltage, fans, power supplies, and ..."; Entries[7][3] = "ians intelligent interface ipmi management platform tco-enabled teaming"; Entries[7][4] = "above adapter adaptive address aggregation allows any asset balancing baseboard based bmc capabilities characteristics chassis configure connected connection controller dedicated device does due dynamic enabled enables fact fans functional health however ians ieee information intelligent interface intrusion ipmi last like link load lose mac manageability management mentioned modified monitor must need network overview pass physical plan platform port power provide receive recovery requirements restricted revision same server single sla specific static such supplies system tco team temperature these tracking traffic type vlan voltage"; Entries[8] = new Array(4); Entries[8][0] = "ipsecoff.htm"; Entries[8][1] = "IP Security Offloading"; Entries[8][2] = "Internet Protocol IP Security IPSec is a set of protocols used to help secure the exchange of IP data. IP Security offloading is the assignment ..."; Entries[8][3] = "ip ipsec offloading security"; Entries[8][4] = "algorithm assignment automatically compatible computations configure confining contents cpu data decreases devices disabled enabled enabling exchange features generally hardware help increases information intel internet ip ipsec issue large last left lso may mitigate modified more network note offload pane performance place port proset protocol reduce revision secure security select send set software support table takes those through traffic used utilization window"; Entries[9] = new Array(4); Entries[9][0] = "lbracket.htm"; Entries[9][1] = "Attach the Low Profile Bracket"; Entries[9][2] = "How to attach the low profile bracket for use in systems with low profile slots."; Entries[9][3] = "bracket install low profile"; Entries[9][4] = "adapter any attach away back before bracket carefully charge come dissipate follow future ground handling install instructions last low may models modified necessary need over package product profile re remove revision screws seated securing side sized slide slot small standard static step these they tighten until used using yourself"; Entries[10] = new Array(4); Entries[10][0] = "legaldis.htm"; Entries[10][1] = "Legal Information"; Entries[10][2] = "Copyright and Legal Disclaimers Copyright 2002 2012 Intel Corporation. All rights reserved. Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124 6497 USA Intel ..."; Entries[10][3] = ""; Entries[10][4] = "any assumes brands claimed commitment contained copyright corporation countries disclaimers document does elam errors herein hillsboro information intel itanium last legal make may modified names nor omissions other parkway pentium property reserved responsibility revision rights trademarks update usa young"; Entries[11] = new Array(4); Entries[11][0] = "license.htm"; Entries[11][1] = "Software License"; Entries[11][2] = "INTEL SOFTWARE LICENSE AGREEMENT IMPORTANT READ BEFORE COPYING, INSTALLING OR USING . Do not copy, install, or use this software and any associated materials collectively, ..."; Entries[11][3] = ""; Entries[11][4] = "about above accompanied accompanying accuracy acknowledge adapt addition additional administrator advised affiliates after against agree alleges alpha alternate any appear applicable application apply arise assign assignable associated assume attempt attorney author authorized back been before below beta bound break business california capable carefully cause changes claim code collectively commercial compatible completeness component computer condition conflict conjunction consent consequential constitutes contain context contractor contracts control convenience convention copy copyright corporation correct costs could countries create creator customers damages data days death decompile defect delivered delivery derivatives design destroy developed development device dfars directly disassemble disclaims disclosure distribute documentation does done duplication emulated enclosed end engineer english entirety equipment errors estoppel et even event except excluding exclusion exclusive existing expense export express extent failure far fees final fitness following form forth found free fully function future goods governed government granted grants graphics guest harmless here herein hereunder hold i ii iii image immediately implication implied important inability incidental include incorporated indemnify indirectly inducement information injury install integral intel intellectual intended international interruption introduce items its iv jurisdiction kind labeled language larger last laws ldquo lease legal liability liable license life limitation limited links loss lost machine maintenance make manager manufacture manufacturer mask material may media medical merchantability minimum modify nations necessary negligent neither network ninety noninfringement nor normal note notice number obligated obligation occur oem offered officers operate organization original other otherwise out own ownership part particular party patent perform period personal physical please portions possibility pre prevent principles private problems product profits prohibit promised properly property proprietary protected provided provision purpose pursuant rdquo read reasonable recipient redistributables referenced regard regulates regulations related release remains remove rent replacement represent representative reproduce research resolve respect responsibility restricted restrictions retain return reverse revision right risk rsquo running safeguard sale sample saving seal secret section select sell separate seq set shall signed single site situation software sold source specifically standalone state subject sublicense subsidiaries successor such supersede suppliers support sustaining system tamper term terminate text then therein thereof these they third those time title trade trademark transfer translate treaty type unauthorized under understand unintended united unless until up update upon usage user vary version vi vii violate virtual warrant warranty was were whatsoever whole without work writing written"; Entries[12] = new Array(4); Entries[12][0] = "warranty.htm"; Entries[12][1] = "Limited Lifetime Hardware Warranty"; Entries[12][2] = "Limited Lifetime Hardware Warranty Intel warrants to the original owner that the adapter product delivered in this package will be free from defects in material ..."; Entries[12][3] = ""; Entries[12][4] = "above abuse accept accident adapter advance against agreement agrees air allow along alteration america any anyone applicable applications apply arise assume authorization authorizes back becomes before below business calling cannot care charge claims completely consequential contact container contract control costs cover critical current customer damage days dealer defective defects defend deficiency deliver department described details direct disaster disclaims discontinued distributors does either element energy entirely equivalent essential event example exceed except exclusion explanation express fitness foregoing forth found free full generation goodwill ground group guarantee hardware harmless health hereunder higher hold implied improper incidental including indemnify indirect infringement installation installed intel intellectual interruptions irrespective issue last level liability license licensee lieu lifetime limitation limited limiting locations loss material may measurable merchantability misuse modified money must neglect negligence neither new ninety noninfringement nor north notice notwithstanding nuclear number objectively obtain option original other out owner package paid part particular pay place policy possibility potential price process product profits proof property proposal provided purchase purpose received reconditioned refund registered remedies repair replace reprocurement resellers reserves respectively return revision right risk rma safety same sample satisfied see set shall ship software sole special specifically specification speculative states statutory sublicensees such support systems testing their thereof these they time tort total traffic transit under user's verifies wants warrants warranty were whether whom without workmanship"; Entries[13] = new Array(4); Entries[13][0] = "lights.htm"; Entries[13][1] = "Indicator Lights"; Entries[13][2] = "The Intel PRO/100+ adapter, PRO/100 S adapter, and PRO/100 VE and VM Desktop Adapters and Network Connections have the following indicator lights Label Indication Meaning ..."; Entries[13][3] = "connections indicator lights"; Entries[13][4] = "act act/lnk adapter amount appears between bit cable check configuration connection connector control data desktop driver dual faulty file flashes flashing following frequency go good indication indicator intel label last leds lights lnk mbps meaning modified network note off operating other panel pci per port power pro/100 problem receiving revision second sending server status switch system three traffic varies ve vm windows"; Entries[14] = new Array(4); Entries[14][0] = "mang_win.htm"; Entries[14][1] = "Power Management"; Entries[14][2] = "Setting up Power Saver options and Wake on LAN on Microsoft Windows operating systems."; Entries[14][3] = "management power remote wake wol"; Entries[14][4] = "ability acbs access accessible acpi active activity adapter advanced after allow amount any anyway apm appear auto automatically available battery between bios both bursts cable called capability capable complex computer configured connect consumption content control converged data dependant detect development device directed disabled disarms disconnected display down dual duplex during eee effect efficient enable ends energy engine enter et2 ethernet even evolved example explicitly expressmodule f4 feature few following forced full fully function functionality gigabit hibernate higher however i340 i350 idle important included includes including incorporated indicate installed intel interacting introduce keeps lan last latency led limited link lit low lowest lp magic manageability management manager may microsoft mode modified mt must needs negotiate network nic note off operating option other over override packet partner period pf port possible power previously pro/1000 proset pt quad r2 readily ready reconnected reduce remote removed replaces requests rest restored resume revision s3 s4 s5 saved saver server set several shutdown shutting simple sleep small speed standard standby state status stay support system t1 t2 t4 tab then there these they timeout traffic transition transmitted turns type under up using variety versions vista vt wake were windows wol x520 x540 xp years"; Entries[15] = new Array(4); Entries[15][0] = "manage.htm"; Entries[15][1] = "Remote Wake Up"; Entries[15][2] = "Remote Wake up and Wake on LAN basics."; Entries[15][3] = "lan remote wake wake-up"; Entries[15][4] = "ability about accept acpi activates adapter address administrators advanced allow amps any apm area around arp assigned attached awaken aware backwards based below bios board both bracket bus cable came capability capable check choosing circuitry clock compatibility complaint completely complex compliant components computer concept configure connection connector consecutive contact containing contains contents control converged corresponds could cpu current d815epea2 data defined description designed desktop details determine development device different directed disk documentation does done down draw drive driver due each early either enable equipped ethernet event every evolved example extends feature few field find first fit following format fully function generally gigabit had header hibernate hours however ibautil implementation important include information initiated installed intel interacting interface intermediate ip keyed label lan last least leds level limited list locations look low mac magic maintenance management manufacturer many may memory milliamps mode model modified more most motherboard mt multiple must named necessary need network newer note numbers off older operating operating system operational operations os out over own packet partial particular patterns pci per perform pila8460bn pila8460f pila8461 pila8900 pin plugged pme port power pro/100 pro/1000 proset protocol provide pwla8390t pwla8490xt quad querying ram rating received receives reduces referred refers refreshed reloaded remains remote removed repeated repetitions represents request require resolution response revision routed s0 s1 s2 s3 s4 s5 section see selectable selectively sending sent server set should shutdown signal similar simple sleep slot specific standby started state still stopped such supply support suspend swapped system t1 t2 technician then there these they through times titled true turning type typically under up upon user usually utility value variety various verify versions volt vt wake was were whereas without wol work x520 x540 xt years"; Entries[16] = new Array(4); Entries[16][0] = "overvwit.htm"; Entries[16][1] = "Overview PRO100 Server for Itanium"; Entries[16][2] = "Overview Welcome to the User's Guide for Intel PRO/100 Server Adapters installed in Itanium based computers. This guide covers hardware and software installation, setup procedures, ..."; Entries[16][3] = "hardware installation itanium setup software troubleshooting"; Entries[16][4] = "adapter advanced any architecture authentication automatically available based basic click co column compatible computers configuration contents covers cpu decreasing driver enabled encryption family features follow functions further guide hardware ia-32 includes increasing information install intel intensive ipsec itanium last latest left link list loaded make microsoft mode modified necessary network note now off offloads operating other overview platforms pro/100 problems procedure process processor refers review revision see select server set setup software start step supported sure system table those throughput tips topic troubleshooting tunnel up upgrading user's utilization varies welcome windows xp"; Entries[17] = new Array(4); Entries[17][0] = "prosetdm.htm"; Entries[17][1] = "Using PROSet"; Entries[17][2] = "Installing, using, and removing Intel PROSet for Windows Device Manager."; Entries[17][3] = "device install manager proset"; Entries[17][4] = "add/remove added additional administrator advanced automatically cd change cl command compatibility connection control core device dialog directory dmix drivers extension file following gigabit help install intel last line located manager modified must network note options panel please process product program proset prosetcl refer removing revision rights same select server services settings software support tabs under uninstall utility windows"; Entries[18] = new Array(4); Entries[18][0] = "reqs_ita.htm"; Entries[18][1] = "Intel PRO/100 Itanium Requirements"; Entries[18][2] = "System requirements for Intel PRO/100 Server adapters on Itanium based systems."; Entries[18][3] = "32-bit 64-bit compatibility install pci pci-x requirements"; Entries[18][4] = "adapter architectures based before bios/efi bit bus check compatibility computer configuration datacenter drivers edition enterprise except following hardware higher installed installing intel itanium kernel last latest linux master microsoft minimum modified network open operate pack pci r2 requirements revision server service slot supported system v2 versions windows"; Entries[19] = new Array(4); Entries[19][0] = "trbl_dm.htm"; Entries[19][1] = "Configuration and Troubleshooting"; Entries[19][2] = "Configuration and Troubleshooting Common Problems and Solutions There are many simple, easy to fix problems related to network problems. Review each one of these before ..."; Entries[19][3] = ""; Entries[19][4] = "ability accommodates active activity adapter addresses adjusting advanced affected after agent already among another any apparent applicable appropriate apps asked assumes attached attaining auto auxiliary available base basic been before behavior best better between bios boot bootagnt both bus cable cannot capabilities capacity card carrier category cause change check choose common communicate compatible compliant components computer configure conflicting conflicts connect connectivity connectors consider consistent contact cooling copper correct creating current customer damaged data default described desktop/management detect device diagnostic different disable discussion disrupted documented does down driver duplex each easy edge efficiency either enable enhanced environment established etc even exact examples exceed execution expected express fail familiar family fan feature find fix following forced frame frequently functioning further gigabit going hangs hardware here hub ibautil idle ieee implementation impose inability incompatible indicator information insert install instructions intel intended interrupt irq isn't issues jumbo kinked knowledge known lack lan last latency latest layer led length level light limited limits link list loaded look loose make manually many master match maximizing maximum may mbps memory mode modified monitor more multi multiple multiprocessor must necessarily need negotiate network newer note off offloading often operating operation opposed options os other over overdraw pair parameters partner pass pci pcie peak perform performance physical play plug points port possible power pre presence prevents problem process processor programs proper provide pxe quality questions rate re readme reboot receive recent recognized recommended related release reload replace reports represents require reserve responder resulting results review revision run rx same seat section securely see select send server service set several shared sharing shorter signal simple size slave slot slowest slowing software solution specific speed standard start stops such sufficient supply support sure switch system table teaming technically test them then there these threading time timer traffic transmission triggering trouble troubleshooting tx type unable under unload unpredictable unusual up upgrade utility v1 v2 vary verify version vlans wake while without wol wording work"; Entries[20] = new Array(4); Entries[20][0] = "qos.htm"; Entries[20][1] = "Quality of Service QoS"; Entries[20][2] = "A brief discussion of Quality of Service QoS)."; Entries[20][3] = "balance load qos quality service tagging team"; Entries[20][4] = "adapter advanced allow bandwidth base before configured connected deal disabled does efficient enabled events first frame generation gigabit help high ieee implement include information intel knowledge last levels lower make microsoft modified more most must network note operating order packet prioritization priority priority/vlan pro/1000 processed programs proset pwla qos quality r2 real receive revision see send server service setting specify support switch system tab tagged tagging time under utility vista vlan windows xp"; Entries[21] = new Array(4); Entries[21][0] = "reg100s.htm"; Entries[21][1] = "Regulatory Information"; Entries[21][2] = "Regulatory Information Intel PRO/100 S Server Adapter Intel PRO/100 S Dual Port Server Adapter Safety Compliance UL 60950 1 Second Edition CAN/CSA C22.2 No 60950 ..."; Entries[21][3] = ""; Entries[21][4] = "a1 a11 a2 about accept accordance adapter against antenna any as/nzs australia/new australian authority back based been below between bsmi c22 can/csa canada canadian cause caution ce certification changed china circuit cispr class classe cns13438 communications community compatibility compliance comply conditions conducted conformance conformity connect consult contact control corporation correct council country dealer declaration declares described designed determined device different digital directive distributor disturbance document does dual edition efup elam electromagnetic emc emi emissions ems en en55022 en55024 encouraged end energy equipment eu european experienced fcc following found frequency general generates guarantee harmful help her hillsboro his home however ices iec immunity including increase industry information installation installed instructions intel interference international japan jf3 kcc korea last life limits listed low lvd mailstop manufacturer mark may measures modified more must ne nmb note notice occur off office operate outlet parkway part particular party people's permission phone port pro/100 product protection provide pursuant radiate radio radio/tv reasonable received receiver receiving reception recognition recycling regulatory relocate reorient republic required requirements residential responsible retailer revision rf rohs rules safety second separation server standards statement subject systems taiwan take technician technology television tested there these tick turning ul undesired union upon usa user vary vcci void voltage without young zealand"; Entries[22] = new Array(4); Entries[22][0] = "save_dm.htm"; Entries[22][1] = "Save and Restore"; Entries[22][2] = "Saving and restoring an adapter's configuration on systems running Microsoft Windows operating systems."; Entries[22][3] = "function intel proset restore save"; Entries[22][4] = "adapter administration allows any assumed backup been changed command configuration contained copy cscript current default directory disk diskette dmix drive driver error event example failure file filename floppy following former generally hard include intel just last line located may measure modified most multiple must navigate network notes open operation options os performed privileges program prompt receive reinstate requires restore result revision run same save savresdx script settings specified standalone such syntax system team these times tool type unstable using vbscript vlans was windows wmiconf"; Entries[23] = new Array(4); Entries[23][0] = "setbd_dm.htm"; Entries[23][1] = "Unattended Installation"; Entries[23][2] = "Installing the base drivers and Intel PROSet via the command line."; Entries[23][3] = "base driver install proset setupbd"; Entries[23][4] = "able above acceleration actions adapters add/remove advanced after agent already any application apply appropriate apps associated assume available base bd been between bios capable case cd change channel characters chinese chipset codes com/en command commonly complete components components/features configure core corresponds created current dcb default definition describes description deselect detects device different directory disable displays dmix does driver during dxsetup error ethernet even example exist fatal fcoe feature fibre file filename first flexibility folder following force full function get gui hide http i i/o i/oat ignored image include information instability install install/upgrade instructions intel invalid iscsi itanium known language last launches layouts level line list local log makes manager messages method microsoft modify more most msdn msi msiexec mst must necessarily need network note operating option other over package passed path preferred prior productcode programs properly property proset prosetcl prosetdx prounstl provided provides public reboot recommends reduced refer reinstall remove repair result return revision running same searches section see select selected/displayed sensitive server set setup setupbd should silent snmp space specific specify start status strings support switch syntax system system32 takes technology tested them then transform translates typical unattend under uninst uninstall updates uppercase us/library utility valid via warnings website white win32 win64 windows winnt without x64 xp"; Entries[24] = new Array(4); Entries[24][0] = "snmpwin.htm"; Entries[24][1] = "Simple Network Management Protocol SNMP"; Entries[24][2] = "Installing SNMP on Microsoft Windows operating systems."; Entries[24][3] = "agent management network protocol simple snmp"; Entries[24][4] = "about adapter additional administrators advanced agent alerts allow application autorun base before cd changes click communicate compile compliant computer configuration consoles database devices directory documentation download drivers employed event experienced features first follow information install instructions intel last manage menu mib microsoft modified more must network notices operating prior product protocol provides recognize revision screen see send should simple snmp software software/services specified start stations such support system tcp/ip teaming them translates updates utility vlans windows"; Entries[25] = new Array(4); Entries[25][0] = "team_dm.htm"; Entries[25][1] = "Teaming"; Entries[25][2] = "Description of ANS teaming modes."; Entries[25][3] = "advanced aft alb ans services sft static team teaming"; Entries[25][4] = "able according across act active adapter adaptive additional address adopted advanced advantage affected affects aft aggregation aggregator alb allow alternatively although among analyzes another any appear appropriately associated assure attention auto automatic availability available avoid back backup balance bandwidth base because becomes becoming been before begin behavior belong benefit best between beyond both bound bridging button cable cannot capability capable case cause cd center change channel check choose cisco click clients column combination common compatibility compatible component computer conditions configure connect connectivity consider contain contents continue control copper create critical currently data default delay denominator dependencies dependent design designated destination detect developed device different disable disconnect displayed documentation does don't download driver duplex during duties dynamic each effect eight either enable engine ensure etherchannel ethernet/data event example exceed experience failback failed failover fails failure fallback fast fault fcoe/dcb feature fec fiber fibre first five following force formed frame full fully functionality gbps gec gets gigabit go good grouping handles hardware highest hot however hub hyper ieee implement important inactive include increase information initial instability install integrated intel interface ip ipx issues jumbo last later latest least left lets like link list load located loms long lose loss lost lowest machine maintain make management manager manually manufacturers match maximum may member microsoft might mixed mode model modify monitored monitoring more multi multicast multiple must mvt needed negotiate netbeui network never new nic nlb/wlbs normal notes occur offload open operate options order original other over package packet pairing pane part particular pay per performance performing plug port possible preferred prevent primary primary/secondary prior priority pro/100 property proset protocol provide qos r2 rate receive reception recognize recommended recommends reconfigures redundancy regains rejoin releases reliability reload remains removed removing renamed replaces require respective restart restored restricted returned revision rlb routable routed rss run rx safety same schema second secondary see select send separate server service set several sft sheet should similar simultaneous single sla software spanning specific specify speed standard standby start static status still stp subnet such support sure switch system tab table tagging take tcp tcp/ip team technology temporary them then there these they third three throughput toe together tolerance traffic transfer transmission transmit tree tx type under until up updated various vary vendor verify version virtual vlan vmlb waiting waits way we window wizard works would"; Entries[26] = new Array(4); Entries[26][0] = "test_dm.htm"; Entries[26][1] = "Test the Adapter"; Entries[26][2] = "Testing the adapter in Windows and other operating systems."; Entries[26][3] = "diagnostics test"; Entries[26][4] = "about access adapter address allows availability below cable capabilities click communicate connection connects dependent determines device diagnostic displays does duplex each functioning hardware including information intel ip its last link lower manager maximum microsoft modified network operating optimum partner performed ping properly properties proset provide reason reports revision run select settings several speed system tab test these type whether window"; Entries[27] = new Array(4); Entries[27][0] = "trbl_win.htm"; Entries[27][1] = "Troubleshooting"; Entries[27][2] = "Troubleshooting PCI and PCI X adapters."; Entries[27][3] = "bus pci pci-x performance troubleshooting"; Entries[27][4] = "adapter after allow any appear attached automatically available been bios cannot cause clear code computer deleted device disable driver enable error event file full functionality functioning gigabit gives information install intel issues known last latest longer make manager may message microsoft modified need older open operating os play plug present problem process proset re rebooting reinstall replacing reviewed revision server session set ship should simultaneous software solution specific start support sure system table terminal then there these time trouble update upgrading versions viewer windows xp"; Entries[28] = new Array(4); Entries[28][0] = "vlwin.htm"; Entries[28][1] = "Join a Virtual LAN under Windows OS"; Entries[28][2] = "How to configure VLANs on adapters installed in systems running Microsoft Windows."; Entries[28][3] = "lans virtual vlan"; Entries[28][4] = "ability across adapter adds administration advanced any area attached based before between both broadcast building campus capability caution change child clients co collection communicate computers configure connecting connections connects considerations considered consist contents cross defined department desktop devices different dispersed each ease enterprise environments exist first functional geographically group hardware hyper ieee improve including information intel joint lan last least left limit local locations logical management match maximum membership microsoft minimize modified more most moves multiple must network note other pane parent partition per performance physical port pro/100 problems project proset protocol refers restricted revision running same security segments select servers set simplify software storms support switch tab table tagged tagging task team term them then they those together typically under untagged up updates users ve virtual vlan vm were window workers workgroups working"; Entries[29] = new Array(4); Entries[29][0] = "wminicdm.htm"; Entries[29][1] = "WMI NIC Provider"; Entries[29][2] = "Intel Network Adapters WMI Provider The Intel Network Adapters Windows Management Instrumentation WMI Provider enables WMI based management applications such as Intel PROSet for Windows ..."; Entries[29][3] = "provider wmi"; Entries[29][4] = "about access adapter allows any application apps assumptions available based between called cannot cim classes collected common configure consumer contains could data describes detailed device distribution dmi docs driver elevate embed enables enterprise external file format gigabit guide i independent information install instances instrumentation intel intelncs2 interfaces jointly kernel last layer level list local located makes manage manager manifest measurement microsoft middleware missing mode modified monitor more must namespace ncs2 network operate order page paper part pci pipeline platform please pro/100 proset provided provider refer reference registers related remote requirements revision root section see services set setup snmp software specification standards status such supported supports system technical technology then through type typical under user view vista wbem web windows wmi"; DOCS/SERVER/slideoff.gif0000755000000000000000000002046211656741062012003 0ustar GIF89a#kfdeXVWsqrpnoUTUTSTNMNJIJzyzvuvpoplkljijihifef_^_[Z[YXYWVWdzQQR||}yyzsstllmhhidde^^_]]^YYZWWXUUVïhikdeglmosuwoqs`abҟһƺ755DBBB@@PNNOMMMKK][[ZXXvttsqqSRRLKK~~}|||{{yxxutttssrqqqppnmmmllihhgfffeedcccbb`__]\\VUUrrroooZZZVVVSSSOOO,#kH*\ȰÇ#JH"DK[lcǏ CI$EAT↣ɗ0cʜI3)+*rK5 JHKnTRCЎ#Jՙtd砥TIJٳ otsgᝤaǢKnM9<Ԋ^ U;JQ1K5̹פS3N5KH!ٳkDž,*{t,Y#JWrMٽI#wIt9&6KO407B1,DG֫B#(B 5 OB[sGXR{D#<½L]n Y$QD'at3I Ҳ)dhDU` Vn}Eh!("4<(iݡWcHV3?f>) a8&G$i}n ad$" P P>;&Tl`9у``숖=drˡCT;dy%A#b{yH'p”l9m zǨdcd>$1Z+@0Q*@,%((6xX+!CH% yp8~d% y<!l1'LDnIKij9 5͊Xb@y.+K(4pS3!W:p+a H,H@;TAQB2D2r%fD2Qa ɕњAD#:ϒ~m-R(2g*NyM~$+ci U;8C(Jv-AHOg˧JH%DQY͎t"_Rhz $J֣HA*G)AFD! WU&.wPu~FZ1qdE V^Y5=0W"Kjk֠l5` "6%nۚbe(`Y 'MjrOJ>ujt=@ap.{!+;haRȎWlX {[)np`˸hSKeagU*X#h'.:'v2!Cb o"؜=o2+?lf8 Θ(>:8Dv0%!P2` ]&進_z@2WtB0#Kb p$T3!rCL ό"^F ʤ"l 멡+XF4ȡYON9(g RsQ،ʰ՘ggĞj Hk"J*AZe6 }QxCqs'[li$~̰$>}齿Cf*D~ } <~x1S_)WTAGszG[D!Gj g)azRU$g_!+%GhGcsXδ# ,R:'X5FzU|~!}$j&W.,؃s` w02Hv5(IZуR%?xE8~ηw ~bfSȂ3+n˗/ R;X=nHGG8'ssot{8Wh(OPMF48V`l}X`?Qs,(j(HT6cŃT036sw#h'XaeIU+øІTՌ68t7׸jrH?(H+@XCHmwkAT͸vx>Tw 811yXHQ+HIЏ(+X+9@mmJP +` (a S9#}' 9E&yd(HؒFvE}9DN1PnIHØkh0PbmVs0D0`nU{`tkxz0SNɏJ@? oȂؕ\IM}`6.np*iBG@i! W {,F q8YB0lYrR`vrE7O合 .RV`?Q+YP{[H )y@z ԟDv9OH Y%Ata8ٖ@YPr+ܸn+*8/@i*ZH7ZF0|'B(F.@QBC[A:DZB"Z\ ^:DYTF" ТD1:&zCZdE/psdNZ/ qZs @0&`Z:DqWb*Uj?{ 9zjDa*ꖅzLkکC٦1*FBcZ@dʪMCej ca 0 *,ʤJR= 5j->'y ʡj?ǦМ*rk7: ! RVdp"zRz[`dJʰo{YAS[hvzy5:=x9y5kZb C!jJ^ zA[vت\6jjGs E`2!ꮒZ+ʴA*6=/vd5 @ jHA=0ĩn}d+KzF( ~.궧 vgqK`z/CQrz h^+ p B1D[:JiڰgQgY w'UkyC< j-4 7ŵqދ覥xK) >|{w6q ƘPzۖ.BfS̺|VH;.Y_p+h pC0 @l| @ۿ`1ZDpq{wc)5q!j>#Ŀvxm)t+0K<7a‚?xpoUx:׷TlH4!$< qR&Iuv[41{ 'UF@B>ȸ`z|<4y&1;b;p$\dp4u7 :'s! 3! mv3q lƊCS B.!=3 K?>A]^66 @.`>^bpI$S#CG jla>SP}m}߅ 1`tx?Xkx~GqlZAP Iݶw+/$U0hm>–湽)m!#X*+ w^1q(r>QrN<O,^4wgm*q]mᮬC XlŎ]޼CXѺ#S0襖-@T:Fr\c?mFy((pcusA8=,;0PS{WEpN\`B{=N3?7A 7ak 0+yhyyWHi djC@YOEXȒ5ropo7( H#0n^ָ53o2geYa=s+An>",Qd$ )8ˎ|*xB(fT? Y $X,dCS)X!-xh17E$Y)Xt,aeSJ.$ʔ3L^O#PYrMIRTTD%-9HNnx9Mji˔*BK- lC$N |<kl k4Έ,4NG2Ԍ:dht3X4ъFd,C@Ƥ;x$dž $:Cd,9E7r .K1=D/K< K93-OId 2)QK<+=&" 2KÑD) ҿ\N[%L6} MWd(/RSՏ(uPVZmHM6^O+aVBvk-*P+55i[tzn%L6]\$eUx Vx}UѨ"̏$aE }WLl`QjHS`>Y/b|$NQY,EDЀx,2]=l =;>4gk+eWE/H$Ah3zʔt8x 5T48:c~99A9N"U57ڭ=lAt QчlFOzSRGhqӡ $ S&/S*UqAbZS^;*Wj6A*YjV#m=MYUǮwi^Wk`׺հ'E[؅4Vl:%{TV֘La5kHų=ch3JZ+Em UֶlJ[ֶ^3[pKv,HEnpmt[1׺|3cN.;6>EoË2t%ao|5V׾S/z_͗$0lSLpi+Z6؋>`sY^m5PJ !9XC`5Y.;,5Vncr ħjKx8rPbKA@E9J 7y FbIZ>`\g2Dc&?!5asfXuYFIlgb$ȚU,@N_Kb*4O[GN!9w۴]x;w3+4}יa`yyD;85y&vg{ݣ)d'_C˳^pi(eo)YAS(m,8B=@iǷ;DOCS/SERVER/snmp.htm0000755000000000000000000000361211656574604011214 0ustar Simple Network Management Protocol (SNMP)

Simple Network Management Protocol

The Simple Network Management Protocol (SNMP) is a network protocol used to manage TCP/IP networks. SNMP-compliant devices (agents) communicate with management applications (consoles) to send alerts and updates and allow configuration changes.

The Intel® SNMP Agent translates event notices from the adapter and sends them to specified SNMP management stations. The SNMP agent provides information on Intel® network adapters as well as information about advanced features, such as teaming and VLANs.

Using the Intel SNMP Agent

  • Before you install the Intel SNMP Agent on a computer, you must install SNMP on the computer. See your operating system documentation for more information.

  • To use the Intel SNMP Agent with an SNMP management application, you must first compile the Intel MIB (Management Information Base) into the management application's database. This allows the management application to recognize and support the adapter.

Look in the Table of Contents for information on installing the SNMP agent on your operating system.

Last modified on 9/03/07 4:49p Revision

DOCS/SERVER/snmpwin.htm0000755000000000000000000000441211656574604011731 0ustar Simple Network Management Protocol (SNMP)

Simple Network Management Protocol

The Simple Network Management Protocol (SNMP) is a network protocol used to manage TCP/IP networks. SNMP-compliant devices (agents) communicate with management applications (consoles) to send alerts and updates and allow configuration changes.

The Intel® SNMP Agent translates event notices from the adapter and sends them to specified SNMP management stations. The SNMP agent provides information on Intel® network adapters as well as information about advanced features, such as teaming and VLANs.

Using the Intel SNMP Agent

  • Before you install the Intel SNMP Agent on a computer, you must install SNMP on the computer. See your operating system documentation for more information.

  • To use the Intel SNMP Agent with an SNMP management application, you must first compile the Intel MIB (Management Information Base) into the management application's database. This allows the management application to recognize and support the adapter.

Installing the SNMP Agent on Microsoft* Windows* Operating Systems

This utility should only be employed by experienced network administrators. Additional software/services must be installed on your network prior to installing the Intel® SNMP Agent.

To install the SNMP Agent, start the autorun menu from the Product CD or download directory and click Install Drivers and Software. Follow the instructions on the screen.

Last modified on 9/03/07 4:49p Revision

DOCS/SERVER/style.css0000755000000000000000000000450511651733270011370 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/SERVER/support.gif0000755000000000000000000003157611651733270011731 0ustar GIF89a]h!"9)$9J,Z B R)j)R% X& e)(s!4k#2x1 k1&X1JMwuC6~9;f37j.\8%׶}$).fdӫ_m: ҅qըqaI[1ĖlpG uQW!Qd9ކvEt #81TL37Hae1`)(IroP"YBT!υT"qI}(TVOiH"3McΙᆋ¶]2833h&cv!b r$1%<3 $nxY'eqFRZ)餔VF<3Hc9|ƘllLؗ1fl3_v9z>L*c1KBxdi6lP.Ęrnaa9}y+T0b .z91IvgGU C!zJK4H"ta / w4RSx8-(Q98 3Ċ;>#hAe0H8#nA 7 .;#OH>[ҸUDBHUa-?%Agdx HJ T-pxcG#(#Aژ"btАQ]]E IH"8$@3džhLh!;Z<A01pƸx 㨑8UI˼Qxm(1 2 R&7)ǒ@Wb&H\!"yxȥ8!orH-,8 '$"X21zEcb$ -9F[Ӝ,dQ =z扅z^WpB 8Els IN3lB*:TF5a?BbG;T?@A ^TJqkt#P:uh!p!2|wѻ eHMOAO8(6a5zB`!` +)́l HH9z (3"01Jͫ^iFBK5!AT3ƍi@ʉdyq9Y`C+H8e{MjibH8Wqts Ad@("C;p+QqF `_p`` ؀ؐȉِ Jv/(ِ2P܀[8 TDE7yq P Ҩ `bu0vxqp % e |73Yxhȉ(+h  yѐ 2   ^]0}!-HLX @ bi0] `m@}FP#V `0&g (v0q\gs  p! e +A6p1\@ȏ P*9  *` *p **\) 0%لM8 Q:P[PHG R$PGP yPfsv^h'~XuG} 1H Op.-=0 ` p؉ Xz`  򀙹\KnlQ$Ii0xw E<@lp@ 0l09I8 xS&v(@qōۘi)DEpV $ gj` ЏzI_vZ  yTw+׈ x;50Awb Ds mPXx'&ʁF\˵qyv5GUGEBV'WtEpIi0'ŰxYmڦP}YsJuJ}^ K(Jp`p7fC7 P iBH^jJ&ʆ`*W` `Y|H QZ/fphpӯ PP gq1p *Jvtژ i]!]0iMyIr,°BFɑѭW[9 Y\Kf9 T@Q |{-隡p1:@'ߡC~1^Ph5i&=ڰ ԉ.q* P `@g_ eлfr`qq@p#[/o46{*iK0!YHp D盾]*J! L @Z++^k]wZ) < )`o; ,+jI*'p9pbp% l020po` p^P[&ć uXK!Q|C @Tt _g9|kAX̠&V)Ipʂ|aL`pk+AHQ2K㰿 Ȍȑ! 09;P  L+PH|Ѱ ]Q*P2p3 2I0PgpdEQL,$li|ibƅ:|_л[ Ǜ 0j Q؄oJ)xz,PzpȐ2aɊʈl7`ɞi;p{** Cl-\,؛ -m <iȘ]r,$ғ^@Ƭ̺b.Ps0ZhE9 i}Pt& K, <[  1 GQ9RS epq\okk*+q ݊NHа9lVIK M ҋEʩ} \{|ÜQL1MV0TKL!9];Gƭ2ZJLJR}+΀m5:aE Ac1 0 0 %N(paPP9\gz H_ wglўfjh,ċ݊IΩKɽ-9$i:] Y={l4^( ˾'"WXa5>ioj0#A kD$^bTp  \9(\\46m wvؤ Yg2_Puջg0'rp;dm' mℙꙹٳ O]3a+K`f&ik,:NjʎZN|0j)IpZ2m" t$ sP}҂0 zV>R3~r0 :wǻo`rot tl"WŚМ] ۮ"L4Na*  )hG4HOG/d;̠i2@Jx?Uk-7vI(tķAp8ˆ[)y_tr(%{T f,xȁ!CbF +"W;q}|-p}1HhJ1V]nP2\`nBcK31BU \*qRЁXA,A Јxp׻?ftWD')91kht2!ǘ2V-pp3!B1A2F dpMr/a XplcŔ ipE8,ssc(bÆ[ސ'!Wh%CcgZ7 3$(X3x̸41|׼0}p4!pӸ| cgx,@`l|c[; FQxiKo$pɸ? {ZzmuHޅS4_^4':!FE.<O7Ip9:\5)V@׮j4| d  #U<;%S3܀5Qp 73uG3#HM>LSo=^W`z5w{ hO1!C}Dp tXȺ [> 䳇哇OS tzx (=; zXp rC;B 7s`2g`6hM9),zch%@# a r xhyv6> =L  @cx'O+I$ 1c"t@A8pp M893bz/tM9]tT18; );Jkės8hVxh ck?p?50 E, 3?+%MgHx9/?8512 gZHЅJ49-Xm<R=RUxՅMIeԑnX7&$I KRTsHpWY=SuR؇T^V%<̺Ľ % ЙP>Xo4nxӱy K{>eU&jmhy+L6@L!-""X3!@ȧ}9@6`1hE-!rӱ#X- AN]T&?}XxHA -1J\ H\NAsG},թ\{\C }=Y\ܣ٨Ľ- pBwQR JsK+їr)^H7-!E̲[q!W|[+"83CXChOש}^b=!85\ \Mm\:j܅A)TlCӗ``a%#QXٟ]NXYTF`~tU0EUPϜE8Yħm^9^%VJF گ="%[M[%*^"8!ai:?7 7,}X_:Sԭ:mؑITxܘXO=T TVm\څ,X1:G7T]ʥa%G&T Ƈ B|Ty&dZ|b͈EK- RU!+cI`Cޱ+,k56o5HȋB5(x/˂/}:@X3t,c=~vYGgo\`@d}4:(:ۅ%Go}w]U:uȈPf`$LhQH0ɬsIiLIEϖi"蟞Bc%;!>yvcbyNjfzDg]xF/ #l^b-Ɓ 6X9]H*ȁG.C5"f7,M} 癨p:bޤĆ#$M*t xl] <p8{`Nlfj ATClˉav^,x04iHfjv%W-pXBq.O)32xcEFljj m#򮐛"X˦my,=fՌCގM;V~@bf? H.6i1-yx@ތ=mq&)8nӡ"vw0555KVfh.pRqk ߴ 610 Ca('H4#H4K÷r/O>1䕾Z" s%SQ3&ssqCЍ&`.I =M6)q7I/tLDF^f^FJc=8QSg%[G#AdiWcJkM?vd>V!f^n2bfw0Tߟ˔hn]dt*\\vISDMvye!N8뱺-(7Eb`'xWxbHׅC-pE @`#B+dy@^óSzy/AFV7x->35 G??. ЀH+}dryz,yJym!p&5Wj]8>upB8zݔ4fgZz{zE,"b~3rs9?cxf̲?{ȟF5x3$8J̸{?pz,v[goqvT/@{/yHI(5`Uͤw6v~W,_'| >1t^Ǐ;F9AxJxIc45 Y,h „ 2l!Ĉ'RH^={7jc= a$Ɣ3ڋ'0u=4(1E*ib)l\ =ŬZ꒰K.ZQEjײm-ܸrureǒOQ]ѣČÆMlhC&ĦJ {ңIXͥ"aٱ M6ܺw[};I)%x2@>$ǐ!7(MpUXӂuCӯo>~=N2U 7.8=ƆQ4\$ ZJV<0 L,"@]4NSV'.E4 HtAxD#œKKYŕWx->fbXR@"'(j\ Yc"fl}oJ5qQ<2ua]CC(p)\p#`*).D H^AѨM=`1c4("Lϐ90K,K*cd80qriK A-Z{c*2Pr^sjf{/guJ,bD/@FD1DFxZ0sN` K8*vmKU}6ib?b$4]>L 0@ZK9oPrl3t|j1ߵԬԉ|]"@<'Fd2ġCu#hu(zuCcU4*"Nc(:NٌX {8EHfBǕ(څLlGRt&ArN 6L}*T*թRV*Vխr^*X*ֱf=+X/qMLuЄTrQ Vjj_:Vj]JվO(d#+Y)qI,[TrOeٵ-jSڸL)!.Z;DOCS/SERVER/support.htm0000755000000000000000000000206611651733270011744 0ustar Intel Customer Support

Customer Support

Intel support is available on the web or by phone. Support offers the most up-to-date information about Intel products, including installation instructions, troubleshooting tips, and general product information.

Web and Internet Sites

Support: http://www.intel.com/support

Corporate Site for Network Products: http://www.intel.com/products/ethernet/overview.htm

 

Last modified on 5/12/10 3:26p Revision

DOCS/SERVER/team_dm.htm0000755000000000000000000005600611735070120011630 0ustar Teaming

Advanced Network Services Teaming

Advanced Network Services (ANS) Teaming, a feature of the Advanced Network Services component, lets you take advantage of multiple adapters in a system by grouping them together. ANS teaming can use features like fault tolerance and load balancing to increase throughput and reliability.

Supported Adapters

Teaming options are supported on Intel® PRO/100, Intel® Gigabit, and Intel® 10GbE adapters. Selected adapters from other manufacturers are also supported.
 

NOTES:

  • Not all team types are available on all operating systems or with all adapters.
  • Be sure to use the latest available drivers on all adapters.
  • If you are using an Intel® 10GbE Server Adapter and an Intel Gigabit adapter in the same machine, the driver for the Gigabit adapter must be updated with the version on the Intel 10GbE CD or respective download package.
  • If a team is bound to a Hyper-V virtual NIC, you cannot change the Primary or Secondary adapter.
  • Intel 10GbE Network Adapters may not be teamed with Intel PRO/100 adapters. Devices based on the Intel® 82597EX controller only support AFT, ALB, and SFT team types.
  • Intel adapters that do not support Intel PROSet may still be included in a team. However, they are restricted in the same way non-Intel adapters are. See Multi-Vendor Teaming for more information.
  • To assure a common feature set, some advanced features, including hardware offloading, are automatically disabled when an adapter that does not support Intel PROSet is added to a team.
  • Hot Plug operations in a Multi-Vendor Team may cause system instability. We recommended that you restart the system or reload the team after performing Hot Plug operations with a Multi-Vendor Team.
  • TOE (TCP Offload Engine) enabled devices can not be added to an ANS team and will not appear in the list of available adapters.
  • Spanning tree protocol (STP) should be disabled on switch ports connected to teamed adapters in order to prevent data loss when the primary adapter is returned to service (failback). Alternatively, an activation delay may be configured on the adapters to prevent data loss when spanning tree is used. Set the Activation Delay on the advanced tab of team properties.
  • Fibre Channel over Ethernet/Data Center Bridging will be automatically disabled when an adapter is added to a team with non-FCoE/DCB capable adapters.
  • If Intel® Active Management Technology (Intel® AMT) has been enabled on a device, then you cannot add the device to a team.

ANS Teaming Types

  • Adapter Fault Tolerance (AFT) - provides automatic redundancy for a server's network connection. If the primary adapter fails, the secondary adapter takes over. Adapter Fault Tolerance supports two to eight adapters per team. This teaming type works with any hub or switch. All team members must be connected to the same subnet.
  • Switch Fault Tolerance (SFT) - provides failover between two adapters connected to separate switches. Switch Fault Tolerance supports two adapters per team. Spanning Tree Protocol (STP) must be enabled on the switch when you create a SFT team.  When SFT teams are created, the Activation Delay is automatically set to 60 seconds.  This teaming type works with any switch or hub. All team members must be connected to the same subnet.
  • Adaptive Load Balancing (ALB) - provides load balancing of transmit traffic and adapter fault tolerance. In Microsoft* Windows* operating systems, you can also enable or disable receive load balancing (RLB) in ALB teams (by default, RLB is enabled).
  • Virtual Machine Load Balancing (VMLB) - provides transmit and receive traffic load balancing across Virtual Machines bound to the team interface, as well as fault tolerance in the event of switch port, cable, or adapter failure. This teaming type works with any switch.
  • Static Link Aggregation (SLA) - provides increased transmission and reception throughput in a team of two to eight adapters. This team type replaces the following team types from prior software releases: Fast EtherChannel*/Link Aggregation (FEC) and Gigabit EtherChannel*/Link Aggregation (GEC). This type also includes adapter fault tolerance and load balancing (only routed protocols). This teaming type requires a switch with Intel Link Aggregation, Cisco* FEC or GEC, or IEEE 802.3ad Static Link Aggregation capability.

    All adapters in a Link Aggregation team running in static mode must run at the same speed and must be connected to a Static Link Aggregation capable switch. If the speed capability of adapters in a Static Link Aggregation team are different, the speed of the team is dependent on the lowest common denominator.

  • IEEE 802.3ad Dynamic Link Aggregation - creates one or more teams using Dynamic Link Aggregation with mixed-speed adapters. Like the Static Link Aggregation teams, Dynamic 802.3ad teams increase transmission and reception throughput and provide fault tolerance. This teaming type requires a switch that fully supports the IEEE 802.3ad standard. 
  • Multi-Vendor Teaming (MVT) - adds the capability to include adapters from selected other vendors in a team. If you are using a Windows-based computer, you can team adapters that appear in the Intel PROSet teaming wizard.
IMPORTANT:
  • Be sure to use the latest available drivers on all adapters.
  • Before creating a team, adding or removing team members, or changing advanced settings of a team member, make sure each team member has been configured similarly. Settings to check include VLANs and QoS Packet Tagging, Jumbo Frames, and the various offloads. These settings are available in Intel PROSet's Advanced tab. Pay particular attention when using different adapter models or adapter versions, as adapter capabilities vary.
  • If team members implement Advanced features differently, failover and team functionality will be affected. To avoid team implementation issues:
    • Create teams that use similar adapter types and models.
    • Reload the team after adding an adapter or changing any Advanced features. One way to reload the team is to select a new preferred primary adapter. Although there will be a temporary loss of network connectivity as the team reconfigures, the team will maintain its network addressing schema.

NOTES:

  • Hot Plug operations for an adapter that is part of a team are only available in Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.
  • The FEC (Fast EtherChannel) and GEC (Gigabit EtherChannel) team types have been renamed to Static Link Aggregation.
  • For SLA teams, all team members must be connected to the same switch. For AFT, ALB, and RLB teams, all team members must belong to the same subnet. The members of an SFT team must be connected to a different switch.
  • Teaming only one adapter port is possible, but provides no benefit.

Primary and Secondary Adapters

If the primary adapter fails, another adapter will take over its duties. If you are using more than two adapters, and you want a specific adapter to take over if the primary fails, you must specify a secondary adapter.

There are two types of primary and secondary adapters:

  • Default primary adapter: If you do not specify a preferred primary adapter, the software will choose an adapter of the highest capability (model and speed) to act as the default primary. If a failover occurs, another adapter becomes the primary. The adapter will, however, rejoin the team as a non-primary.
  • Preferred Primary/Secondary adapters: You can specify a preferred adapter in Intel PROSet. Under normal conditions, the Primary adapter handles all non-TCP/IP traffic. The Secondary adapter will receive fallback traffic if the primary fails. If the Preferred Primary adapter fails, but is later restored to an active status, control is automatically switched back to the Preferred Primary adapter.

To specify a preferred primary or secondary adapter

  1. From Device Manager, open the properties of a team.

  2. Click the Settings tab.

  3. Click the Modify Team button.

  4. Select the adapter you want to be the primary adapter and click the Set Primary button.

The adapter's preferred setting appears in the Priority column.

Failover and Failback

When a link fails, either because of port or cable failure, team types that provide fault tolerance will continue to send and receive traffic. Failover is the initial transfer of traffic from the failed link to a good link. Failback occurs when the original adapter regains link. You can use the Activation Delay setting (located on the Advanced tab of the team's properties in Device Manager) to specify a how long the failover adapter waits before becoming active. If you don't want your team to failback when the original adapter gets link back, you can set the Allow Failback setting to disabled (located on the Advanced tab of the team's properties in Device Manager).

Adapter Fault Tolerance

Adapter Fault Tolerance (AFT) provides the safety of an additional backup link between the server and switch. In the case of switch port, cable, or adapter failure, network connectivity is maintained.

Adapter Fault Tolerance is implemented with a primary adapter and one or more backup, or secondary adapters. During normal operation, the backup adapters are in standby. If the link to the primary adapter fails, the link to the secondary adapter automatically takes over. For more information, see Primary and Secondary Adapters.

To use Adapter Fault Tolerance all adapters must be connected to the same subnet.

Switch Fault Tolerance

Switch Fault Tolerance (SFT) teaming allows you to connect each of two teamed adapters to a separate switch.

Switch Fault Tolerance can detect failures when they occur:

  • on either teamed adapter
  • on either cable connecting the teamed adapter to its switch
  • on switch ports connected to the adapters, if link is lost

In SFT teams, one adapter is the primary adapter and one adapter is the secondary adapter. During normal operation, the secondary adapter is in standby. In standby, the adapter is inactive and waiting for failover to occur. It does not transmit or receive other network traffic. If the primary adapter loses connectivity, the secondary adapter automatically takes over.

In SFT teams, each adapter in the team can operate at a different speed than the other.

Configuration Monitoring

You can set up monitoring between an SFT team and up to five IP addresses. This allows you to detect link failure beyond the switch. You can ensure connection availability for several clients that you consider critical. If the connection between the primary adapter and all of the monitored IP addresses is lost, the team will failover to the secondary adapter.

Adaptive Load Balancing

Adaptive Load Balancing (ALB) uses software to balance routable traffic among a team of two to eight adapters or LOMs (the team must include at least one server adapter) connected to the same subnet. The software analyzes the send and transmit loading on each adapter and balances the rate across the adapters based on destination address. Adapter teams configured for ALB also provide the benefits of fault tolerance.

NOTES:
  • ALB does not load balance non-routed protocols such as NetBEUI and some IPX* traffic.
  • You can create an ALB team with mixed speed adapters. The load is balanced according to the lowest common denominator of adapter capabilities and the bandwidth of the channel.
  • On Windows systems, Receive Load Balancing is enabled by default.
  • Receive Load Balancing is not supported on Microsoft Hyper-V*.

Virtual Machine Load Balancing

Virtual Machine Load Balancing (VMLB) provides transmit and receive traffic load balancing across Virtual Machines bound to the team interface, as well as fault tolerance in the event of switch port, cable, or adapter failure.

The driver analyzes the transmit and receive load on each member adapter and balances the traffic across member adapters. In a VMLB team, each Virtual Machine is associated with one team member for its TX and RX traffic.

If only one virtual NIC is bound to the team, or if Hyper-V is removed, then the VMLB team will act like an AFT team.

NOTES:
  • VMLB does not load balance non-routed protocols such as NetBEUI and some IPX* traffic.
  • VMLB supports from two to eight adapter ports per team.
  • You can create an VMLB team with mixed speed adapters. The load is balanced according to the lowest common denominator of adapter capabilities and the bandwidth of the channel.

Static Link Aggregation

Static Link Aggregation (SLA) is a performance technology developed by Cisco to increase throughput between switches. This team type works with:

  • Cisco EtherChannel-capable switches with channeling mode set to 'ON'
  • Intel switches capable of Link Aggregation
  • Other switches capable of static 802.3ad

The transmission speed will never exceed the adapter base speed to any single address (per specification). Teams can contain two to eight adapters, but must match the capability of the switch. Adapter teams configured for Static Link Aggregation also provide the benefits of fault tolerance and load balancing.

NOTES: 
  • The FEC (Fast EtherChannel) and GEC (Gigabit EtherChannel) team types have been renamed to Static Link Aggregation.

IEEE 802.3ad Dynamic Link Aggregation

802.3ad is an adopted IEEE standard. Teams can contain two to eight adapters, and you can have a maximum of two IEEE 802.3ad dynamic teams per server. You must use 802.3ad switches (in dynamic mode, aggregation can go across switches). Adapter teams configured for IEEE 802.3ad also provide the benefits of fault tolerance and load balancing. Under 802.3ad, all protocols can be load balanced.

Dynamic mode supports multiple aggregators. Aggregators are formed by port speed connected to a switch. For example, a team can contain adapters running at 1 Gbps and 10 Gbps, but two aggregators will be formed, one for each speed. Also, if a team contains 1 Gbps ports connected to one switch, and a combination of 1Gbps and 10Gbps ports connected to a second switch, three aggregators would be formed. One containing all the ports connected to the first switch, one containing the 1Gbps ports connected to the second switch, and the third containing the 10Gbps ports connected to the second switch.

NOTES:
  • Once you choose an aggregator, it remains in force until all adapters in that aggregator lose link.
  • In some switches, copper and fiber adapters cannot belong to the same aggregator in an IEEE 802.3ad configuration. If there are copper and fiber adapters installed in a system, the switch might configure the copper adapters in one aggregator and the fiber-based adapters in another. If you experience this behavior, for best performance you should use either copper or fiber-based adapters in a system.
  • If multiple switches are used, all team members connected to the same switch must operate at the same speed.

Before you begin

  • Verify that the switch fully supports the IEEE 802.3ad standard.
  • Check your switch documentation for port dependencies. Some switches require pairing to start on a primary port.
  • Check your speed and duplex settings to ensure the adapter and switch are running at full duplex, either forced or set to auto-negotiate. Both the adapter and the switch must have the same speed and duplex configuration. The full duplex requirement is part of the IEEE 802.3ad specification: http://standards.ieee.org/.

    If needed, change your speed or duplex setting before you link the adapter to the switch. Although you can change speed and duplex settings after the team is created, Intel recommends you disconnect the cables until settings are in effect. In some cases, switches or servers might not appropriately recognize modified speed or duplex settings if settings are changed when there is an active link to the network.

  • If you are configuring a VLAN, check your switch documentation for VLAN compatibility notes. Not all switches support simultaneous dynamic 802.3ad teams and VLANs. If you choose to set up VLANs, configure teaming and VLAN settings on the adapter before you link the adapter to the switch. Setting up VLANs after the switch has created an active aggregator affects VLAN functionality.

Multi-Vendor Teaming

MVT allows teaming with a combination of Intel adapters that support Intel PROSet, Intel adapters that do not support Intel PROSet, and non-Intel adapters. This feature is currently available under Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2. All adapters that appear in the Intel PROSet teaming wizard can be included in a team.

MVT Design Considerations

  • In order to activate MVT, you must have at least one Intel adapter or integrated connection that supports Intel PROSet in the team. That adapter or connection must be designated as the primary adapter. 
  • A multi-vendor team can be created for any team type. 
  • All members in a MVT must operate on a common feature set (lowest common denominator). 
  • Manually verify that the frame setting for all adapters in the team is the same.
  • Verify that the RSS settings for all adapters in the team are the same.

Setting Up Adapter Teaming in Microsoft* Windows*

Before you can set up ANS teaming in Microsoft Windows, you must install Intel® PROSet software. For more information, select Intel PROSet in the Table of Contents (left pane) of this window.

NOTES:
  • ANS Teaming is compatible with Microsoft Network Load Balancing (NLB/WLBS) running on Microsoft Windows Server* 2003, Microsoft Windows Server 2008, and Microsoft Windows Server 2008 R2, when in multicast mode only. To use Microsoft Network Load Balancing in an Adaptive Load Balancing (ALB) team type, Receive load balance must be disabled.
  • If Intel® Active Management Technology is enabled on an adapter, you will not be able to add it to a team. When you create or modify a team, the adapter will not be displayed in the list of available adapters. The adapter will not have a Teaming tab on its Device Manager property sheet.
  • Teaming only one adapter port is possible, but provides no benefit.

Last modified on 3/07/11 10:18p Revision

DOCS/SERVER/test_dm.htm0000755000000000000000000000343011656741062011666 0ustar Test the Adapter

Test the Adapter from Microsoft Windows*

Intel® PROSet allows you to run several diagnostic tests, including:

  • Connection Test: Tests the adapter's connection to the network. If the adapter connects below its maximum speed, the connection test reports the reason for this lower speed. If the adapter has link but does not have an IP address, the test reports whether the adapter can communicate with the link partner. If the adapter has link and has an IP address, ping tests are performed.

  • Link Test: Tests the link speed and duplex capabilities of the link partner and reports the optimum settings.

  • Cable Tests: Provide information about cable properties.

  • Hardware Tests: Determines if the adapter is functioning properly.

To access these tests, select the adapter in Windows* Device Manager, click the Link Speed tab, and click Diagnostics. A Diagnostics window displays tabs for each type of test. Click the tab and run the test.

The availability of these tests is dependent on the adapter and operating system.

Last modified on 4/20/06 3:48p Revision

DOCS/SERVER/toc_dm.htm0000755000000000000000000001136611701323440011466 0ustar
Search this guide
  

Overview

System Requirements

Supported Adapters

Hardware Installation

Insert the Adapter

Attaching a Low-Profile Bracket

Attach the Network Cable

Microsoft* Windows* Setup

Install the Drivers

Intel® PROSet

Setup Speed & Duplex

Command Line Install for Base Drivers and Intel PROSet

Windows Unattended Installs & Updates

Microsoft Windows Advanced Features

Teaming

VLANs

Power Management

Simple Network Management Protocol (SNMP)

Quality of Service (QoS)

Save & Restore

IPMI Manageability

Hot Plug

Windows Management Instrumentation (WMI)

IPSecurity Offloading

Setting up Microsoft Hyper-V* virtual NICs on teams and VLANs

Linux Setup

Install the Drivers

Installing DOS Drivers

Intel Boot Agent

Troubleshooting & Support

Configuration and Troubleshooting

Windows Issues

Windows-Based Testing

Linux-Based Testing

DOS-Based Testing

DOS Related Issues

Indicator Lights

Customer Support

Get Latest Drivers

Warranty, License, Regulatory

Limited Warranty

Software License

Regulatory Information

Copyright © 2002-2012 Intel Corporation.
Legal Information

Last modified on 1/25/11 10:09p Revision

DOCS/SERVER/toc_itdm.htm0000755000000000000000000001057111701323440012020 0ustar
Search this guide
  

Overview

System Requirements

Supported Adapters

Hardware Installation

Insert the Adapter

Attaching a Low-Profile Bracket

Attach the Network Cable

Microsoft* Windows* Setup

Install the Drivers

Intel® PROSet

Setup Speed & Duplex

Command Line Install for Base Drivers and Intel PROSet

Microsoft Windows Advanced Features

Teaming

VLANs

Power Management

Simple Network Management Protocol (SNMP)

Quality of Service (QoS)

Save & Restore

IPMI Manageability

Hot Plug

Windows Management Instrumentation (WMI)

IPSecurity Offloading

Linux Setup

Install the Drivers

Intel Boot Agent

Troubleshooting & Support

Configuration and Troubleshooting

Windows Issues

Windows-Based Testing

Linux-Based Testing

EFI-Based Testing

Indicator Lights

Customer Support

Get Latest Drivers

Warranty, License, Regulatory

Limited Warranty

Software License

Regulatory Information

Copyright © 2002-2012 Intel Corporation.
Legal Information

Last modified on 3/20/11 10:48p Revision

DOCS/SERVER/top_s.htm0000755000000000000000000000054711656577060011366 0ustar

Intel® PRO/100 Server Adapter Guide

User Guides Home

DOCS/SERVER/top_sit.htm0000755000000000000000000000066411656577060011723 0ustar

Intel® PRO/100 Server Guide
          For Itanium®-based computers

User Guides Home

DOCS/SERVER/trbl_dm.htm0000755000000000000000000003446611656741062011667 0ustar Configuration and Troubleshooting

Configuration and Troubleshooting

Common Problems and Solutions

There are many simple, easy-to-fix problems related to network problems. Review each one of these before going further.

  • Check the cable. Use the best available cabling for the intended data rate.

    • Check that the cable is securely attached at both points.

    • For copper connections, make sure the cable is a 4-pair Category-5 or better.

    • Make sure the cable length does not exceed specifications.

    • Perform a cable test.

    • Replace the cable.

  • Check the link partner (switch, hub, etc.).

    • Make sure the link partner is active and can send and receive traffic.

    • Make sure the adapter and link partner settings match one another, or are set to auto-negotiate.

    • Make sure the port is enabled.

    • Re-connect to another available port or another link partner.

  • Look for adapter hardware problems.

    • Re-seat the adapter.

    • Insert the adapter in another slot.

    • Check for conflicting or incompatible hardware devices and settings.

    • Replace the adapter.

  • Check the driver software.

    • Make sure you are using the latest appropriate drivers for your adapter from the Intel support website.

    • Disable (or unload), then re-enable (reload) the driver or adapter.

    • Check for conflicting settings. Disable advanced settings such as teaming or VLANs to see if it corrects the problem.

    • Re-install the drivers.

  • Check for recent changes to hardware, software or the network, that may have disrupted communications.

  • Check the adapter release notes (readme.txt).

    • The Known Issues section may have specific troubleshooting information for your configuration.

  • Check the Intel support website for possible documented issues.

    • Select your adapter from the adapter family list.

    • Check the Frequently Asked questions section.

    • Check the Knowledge Base.

  • Check your process monitor and other system monitors.

    • Check to see that there is sufficient processor and memory capacity to perform networking activity.

    • Look for any unusual activity (or lack of activity).

    • Use network testing programs to check for basic connectivity.

  • Check your BIOS version and settings.

    • Use the latest appropriate BIOS for your computer.

    • Make sure the settings are appropriate for your computer.

  • Reboot the computer.

The following troubleshooting table assumes that you have already reviewed the common problems and solutions.
 
Problem Solution

Your computer cannot find the adapter

Make sure your adapter slots are compatible for the type of adapter you are using:

  • PCI Express v1.0 (or newer)

  • PCI-X v2.0

  • PCI slots are v2.2 

Diagnostics pass but the connection fails

Make sure the cable is securely attached, is the proper type and does not exceed the recommended lengths. 

Try running the Sender-Responder diagnostic Test.

Make sure the duplex mode and speed setting on the adapter matches the setting on the switch.

Another adapter stops working after you installed the Intel® Network Adapter

Make sure your PCI BIOS is current. See PCI / PCI-X / PCI Express Configuration.

Check for interrupt conflicts and sharing problems. Make sure the other adapter supports shared interrupts. Also, make sure your operating system supports shared interrupts.

Unload all PCI device drivers, then reload all drivers.
Adapter unable to connect to switch at correct speed. Gigabit adapter connects at 100 Mbps and 10 gigabit adapter connects at 1000 Mbps.

This is applicable only to copper-based connections.

Make sure the adapter and the link partner are set to auto-negotiate.  

Verify that you are running the latest operating system revision for your switch and that the switch is compliant with the proper IEEE standard:

  • IEEE 802.3ad-compliant (gigabit over copper) 

  • IEEE 802.3an-compliant (10 gigabit over copper)

The adapter stops working without apparent cause

Run the adapter and network tests described under "Test the Adapter".

The Link indicator light is off

Run the adapter and network tests described under "Test the Adapter".

Make sure the proper (and latest) driver is loaded.

Make sure that the link partner is configured to auto-negotiate (or forced to match adapter)

Verify that the switch is IEEE 802.3ad-compliant.
The link light is on, but communications are not properly established

Make sure the proper (and latest) driver is loaded. 

Both the adapter and its link partner must be set to either auto-detect or manually set to the same speed and duplex settings.  

NOTE: The adapter's link indicator light may be on even if communications between the adapter and its link partner have not been properly established. Technically, the link indicator light represents the presence of a carrier signal but not necessarily the ability to properly communicate with a link partner.  This is expected behavior and is consistent with IEEE's specification for physical layer operation.
RX or TX light is off

Network may be idle; try creating traffic while monitoring the lights.

The diagnostic utility reports the adapter is "Not enabled by BIOS"

The PCI BIOS isn't configuring the adapter correctly. See PCI / PCI-X / PCI Express Configuration.
The computer hangs when the drivers are loaded

Try changing the PCI BIOS interrupt settings. See PCI / PCI-X / PCI Express Configuration.

The Fan Fail LED of the 10 Gigabit AT Server Adapter is on (red) The fan cooling solution is not functioning properly. Contact customer support for further instructions.

Multiple Adapters

When configuring a multi-adapter environment, you must upgrade all Intel adapters in the computer to the latest software.

If the computer has trouble detecting all adapters, consider the following:

  • If you enable Wake on LAN* (WoL) on more than two adapters, the Wake on LAN feature may overdraw your systems auxiliary power supply, resulting in the inability to boot the system and other unpredictable problems. For multiple desktop/management adapters, it is recommended that you install one adapter at a time and use the IBAUtil utility (ibautil.exe in \APPS\BOOTAGNT) to disable the WoL feature on adapters that do not require WoL capabilities. On server adapters, the WoL feature is disabled by default.

  • Adapters with Intel Boot Agent enabled will require a portion of the limited start up memory for each adapter enabled. Disable the service on adapters that do not need to boot Pre-Boot Execution Environment (PXE).

PCI / PCI-X / PCI Express Configuration

If the adapter is not recognized by your OS or if it does not work you may need to change some BIOS settings. Try the following only if you are having problems with the adapter and are familiar with BIOS settings. 

  • Check to see that the "Plug-and-Play" setting is compatible with the operating system you are using.

  • Make sure the slot is enabled.

  • Install the adapter in a bus-master slot.

  • Configure interrupts for level-triggering, as opposed to edge-triggering.

  • Reserve interrupts and/or memory addresses. This prevents multiple buses or bus slots from using the same interrupts. Check the BIOS for IRQ options for PCI / PCI-X / PCIe.

Here are some examples of BIOS parameters:

PCI / PCI-X / PCIe slot #: Slot where the adapter is installed
Master: ENABLED
Slave: ENABLED
Latency timer: 40 - 80
Interrupt: Choose any one of several that the BIOS provides.
Edge-level: Level

The exact wording of the parameters varies with different computers.

Other Performance Issues

Attaining the best speed requires that many components are operating at peak efficiency. Among them are the following:

  • Cable quality and length - Do not exceed the maximum recommended length for your cable type. Shorter lengths often provide better results. Check for loose or damaged connectors. Check the cable for kinked or damaged sections. 

  • Bus speed and traffic - The PCI bus speed accommodates the slowest PCI card installed. Check to see if you have a card that is slowing down your system.

  • Processor and Memory - Check your performance monitoring programs to see if traffic is being affected by your processor speed, available memory or other processes.

  • Transmission frame size - Your network performance may be enhanced by adjusting or maximizing the transmission frame size. Operating systems, switches and adapters will impose varying limits on maximum frame size. See the discussion on Jumbo Frames for your OS.

  • Operating System - Networking feature implementation will vary by operating system version, such as offloading and multiprocessor threading.

Last modified on 8/21/08 11:09a Revision DOCS/SERVER/trbl_win.htm0000755000000000000000000000543411656741062012055 0ustar Troubleshooting

Microsoft* Windows*-Specific Issues

Use the information in this table after you have reviewed common problems and solutions.
 
Problem Solution
Event viewer message: A device attached to the system is not functioning If there is a BIOS setting for "Plug and Play OS", it should be set to "NO" for all versions of Microsoft* Windows*. 
Microsoft Windows XP or Microsoft Windows Server* 2003 gives an error "Device cannot start (CODE 10)" when you install or update drivers for your gigabit adapter. 

Microsoft Windows XP and Microsoft Windows Server 2003 ship with some older plug-and-play drivers for gigabit adapters present. Windows XP has been known to have trouble replacing a driver file automatically. Updating these drivers with Intel's latest drivers may cause this error message to appear. Rebooting your computer will clear the error and allow you to use the full functionality of your adapter. 

Disable, then re-enable the adapter in Windows Device Manager.
After upgrading operating systems, Intel® PROSet is no longer available

If you are upgrading a Microsoft Windows operating system and you have Intel PROSet software installed, it will be deleted in the process. You will need to reinstall Intel PROSet.

Terminal Server support

When using Terminal Server, make sure only one session of Intel PROSet is open at any one time. Simultaneous sessions are not supported in Intel PROSet.

 

Last modified on 4/01/09 4:16p Revision DOCS/SERVER/tst_dmit.htm0000755000000000000000000000350411656741062012060 0ustar Test the Adapter

Test the Adapter

Intel® PROSet allows you to run several diagnostic tests, including:

  • Connection Test: Tests the adapter's connection to the network. If the adapter connects below its maximum speed, the connection test reports the reason for this lower speed. If the adapter has link but does not have an IP address, the test reports whether the adapter can communicate with the link partner. If the adapter has link and has an IP address, ping tests are performed.

  • Link Test: Tests the link speed and duplex capabilities of the link partner and reports the optimum settings.

  • Cable Tests: Provide information about cable properties.

  • Hardware Tests: Determines if the adapter is functioning properly.

To access these tests, select the adapter in Windows* Device Manager, click the Link Speed tab, and click Diagnostics. A Diagnostics window displays tabs for each type of test. Click the tab and run the test.

The availability of these tests is hardware and operating system dependent.

Last modified on 4/20/06 3:47p Revision

DOCS/SERVER/vcci-a.gif0000755000000000000000000007771111656741516011367 0ustar GIF89aD(((@@@UUUgggyyy! ,D#dihlp,tmx|pH,Ȥrl:ШtJZجvzxL.zn|N~ H*\ȰÇ#JHŋ3jȱǏ CIɓ(S\ɲ˗0cʜI͛8sɳϟ@ JѣH*]ʴӧPJJիXjʵׯ`ÊKٳhӪ]˶۷pʝKݻx˷߿ LÈ+^̸ǐ#KL˘3k̹ϠC@Ө~:װsfD۸sͻ Nȓ+_μУKNسkνËOӫ_Ͼ{˟OϿ(h&k4m Fhb4"f a"#h(S!+0b!3h8>S ;@c CiHRK&PfdSFiXX!Yv嗊T`iehSypiAYx/9j(Ƒ行6o@褔^)iV@f*jQꨨjg꫰j[j7JcKذ` k楬6+fmdrշZ+>e.Dk4Ѐ 0ڵ p@10C `oĞ,|{*(pFK00g$_,4ˢ3/@ R$"/s_C0mPP'+51";lp.s;@  n T0G`Ns(PmmҺKvAH*؟@ `)(1s&HPχ2^ {fW0[C>>jiRA#쏄H;\ @U|OMcQ Rg25`MɺRUJNS?XgY,ijWMB|@`+*"zЄ޲w<`u6 ], 0YζTvEPWRM 2].B+.7|k{sŁQ+Tմ&p*˂Vy` 00vS.X3l׬@Ԋe]+<;ȫ|W-1k7nEc!Z6;l a3!MrV^2V+N%M5Ol@6>ŠGT3`/7y `3փox$Oʉ8A=3? _t3ɻKWIpы .؄02;ҥ65q1Z`mpWaSc^5Ŭp ecr?0u{ *࢑#i6z+gڼ^lRKbؚkt! G:8zQp16,}(B,3gNU!"=@}n_Rt\|- =/Ad,NŝXS[},NjN.K(E_mh_K@Ygԃg(b%`,[(w]>*tG 4[CWW|gbm0"0U715{w+faaV1k=I<5mFz3C YB2AUi;}e i\ N2p}FyPliHimFc; 01r8ut'"i vvDiR^3Nзt_(+0uy@m|u+fc?f7w~`ȉ6: T0=DVct<01HIT|%/A LtANf:stV$0#I)@ҁ4)329cӐ x blYYc7" &P<+ 5ȅ39:TBdN:SJLiw4wQ@TiWlB($ch`ل" @Shij?ؙ "`iYݥӜ~'LyD@yKV5XVyU DYE-:+s ZԚ1}D96P&@^M븛ū)&]FTJyu˹}I7 jov~10 SY6:%hpbY vS*韼Y:mLYzaDq 'G-XX(ܴo7N k*v[_iN.of#Е dX`HՉw1xIGQǘh9:+TvX^Ʌ^zTZxXSXW:ӑ3J V41,2-d~/2:JlgvAk@ԍGXLN?R&86 *+2{생Hb.9i< =Eh0tq2KTYC絶9giT:fNn\8k{@j(,zo|~L E;}Qc܊Wƨ0yeyAC:suKy*0++.VOCQ@E2be/6uu0|DSh#vkZsڵ{KRXEtMhL$W) /@vEq⻠^P*uG|TI[F-̪xz h[c;f߻-gAU4UEk6 5Hӣ (AA [s]\6wK Uk(0|EH6k/kcvs0P)3Ifutcm̔*d7kE9.$*? |\\&_ ēAh$p>:eg'0=Z ]x^XPNA8n;^=6 8|EP ^;[R&hŹ:hLQLݜ%lp=X? ԻFK0tu-ci~-ߍ; fP>SS^VӦ(YNWܰ>f{ߜ<"P S$hܬ/0ebhY#w^ǚ<e')+-'-i6}FmS<9>!ꭢklM|lb"ո^Cm/ ifNPh~.2u~wJo:NVHS7~A+_i?3TE%,d/4Π3*n޵5Xb˖&?_4% œ?1^zȾL5_KoADyCLvK3C";+0x5`/|iNӽfuGf*?9ss;˒a HlB p"s FRT,[V҃4MFoI;m~ J =D^8 ع f!8)8) -A-M=z-q e:E:4 Xfa:!=,9∬$$@$.IRZO9qz0"48n5=Xj%W 4U θcZ3 6Z,xub?uQ؀'k q"XsEGz|2̓nr~-i0l.V|TB"Z~1FW}8K )20G=* 裈M,ˤz|E TeJv z@ (cuh{Kt8z2@!O_*,a7P`2Ze7p](\a`kK*8Ɣalhr'/+Xa@ţDzWHZy]|&<'񤾜(-N\d@MֽTE\ ßuRY3)DVM{Бu#p?Qv{(pSO}V {N m8EFXXʋ%߈0 gЅu8g"V|T)IU8QM㰮5/!J]}=ru+Zs0ٽ *hU b ,Cj v({1@P8saҏ"59x`V<7 :Dby`` l3úR1/tzAbP$`v 7DD4$"P"-EUS` ieùwmwF \rt )zMbKXC>Ps%6<6O %kh1/ÉLw=Z IiK:t @!Pw{`ub .@t? K9֌P <ݘ*z8l9d/FSG)@1[$//2'LS\,dBpۘ`b})j6q<$s Q!0b&^W!嗪UnX {E>p#cWΘ?2q&J9.RaOj#cN/>[?*Ϊ-u "=sM- ]!ദ %4;66HXA/PSMY5 ͥzP馍Ơ{riFV/dpyabgݜE70(:Yi`5ChD~?<+׬4`R,~wQ[li,R>8p lFqr" TؗF2KI83]_=ϠEVN`@he-H j3 Υ xTYۤ&;ziZj!ͅqn!2#K{fdY&`\Xo2LSbǞH~&9Xwfk:%mKkJ\ 4X 6.4m9Xܶjo,fW_p[E,bdnr co\Gcvq:/(x/.;kmF~__y0$l`$ خ namhYCXӘ10edvy1X_{ewP|IXԦc71vwYd zTdSceri]֒|F~] 5\61 |Y*HP)`{K#aT] usהF=#`)+M؝UU)ZgSF wB=_4(;(BI.ep%XhH@ך۪n7̼[5'ir lx&_oBmf!j39r0?*,\}V񛦁#s7hmP  Դo? m;s@Mi=BCm i)sH@L@ @4<[Ad6M^T%ܧ45ΡA}OЅ_L]!_(d0L\iyCe _DI)IQCډܘXQٍ m]VA]yĎ,XDk700ҬB0E-Pux^ =!}4[> ^09Xo"_[IlF~)=sS4_Ae_ CRIxA!>#_HU\P=\TSΝC)_8}Mf)$C7z0h J +ـ|-y6V?5և.J;QA-Cʐ-jZU DM C3Z@-@X؟H=˕#iAr昡V!1㈰apܠw;J9Q7bǘ6JS1P dBoUMi7Ui`*:Q<pzf R/@&0M$ef@4oFaJI&FDA=Ru E A\f&ah̵fGgm&e'fSBe@@od80_\PM>0c^c@2l$@,Ѥ%('yAF4ِqE`@m88$Fc"+ Р _LmgL+.@4ߤP+ʹπ&l=0h餺ZoM}ҚpR qg=Q@sւC |rvu&Xvq'0y( Kx_Cz)ݵ'v|~|Ì~\g5dhn)TinR UdЀX 2QWF ~~'7:h J*ci8$. _tP\^i$]VI*@<=ND)^i6WʐHi}vNKie5E08]^<%DYYg)BNj5 2J c)Y&ᘺǘRQd"s)zƚj4⍝Dn:2؀h~<a̢~àĄ,H,n,gVUCw0'8] Dl)!u60ı T~*%C eDJk8(x׋d]%%mM< #Z"$:@ۅRX΄͚;TI:z )ˊU$̎AP2RR-*mjIjmZ'-m8ZLȐ/:`9s{p|v"(ۗ _<]nM{΍IW0 ֋̞ ["(Sws[7 RnȰkQ:݁tVХꌴ58w]U )@{S|y+KCMg8|Oʠ;ESnTUzCƜ \QO+sS v&o oNbi(n!KeG `H ,U\eR<7<Ïë!_{DPYnx)<!j0AR(BM(0iSƛr.o;NW_4k4R3-C&H0$ Db8)TX74@gR@9GBb'"w,<<:X0r`y"]%dT#EH+Ϣ$zQI[@VȌZyMjML@PS"]G1  g G4.T: ʈѣIɴӨ'%KVo xp61%] @K"CH3`@I_79r j=;1W^p[ Xqt)wswP&J`@̳ܔ#bC2_@9g(]g@~SZ  P@kb0`(ћ,~rvbWv E1SUzQޘU|@Y" ؀o8%v~35*i X*c>+5z  %a)sRHzDۄhl<@5V~4Mֱr(sHk?aGԧ:'nՄm1Yz}auZ%p@ `a ^QU,PM^bc+89&¼.:#TQc6<5I%|*iq9yHE*`iÖ]JeVAf%ްjmBuw8{#|F䉍 2:58P)m˶/ktADtC <u1ˀ['j-΅Z( 4"3^m_/NX*m:  W/CQ9HO(d+qvKຨ*IkHU8a -@rm`BŽ`lp4̑Op*%Ԋ #P~ړ C=e "5p4G\5pr3|_1"}3 !>!3>Brh,J\z<Q ‡Hah! 1ٍS}0iAuàBb aQwBM RGb NvX S@.02S Fͩb%S7FtJVWv'8"a'pօj"^+d"o;R8DOSg=ЕYU"?BU%|j[^ď%߸`ry~biGFQ @~ 'C}Y]F1)$jsSMЊ.l9V^9t ķP A؀QF`Oֿ?l;؂WD/l?$F R!*C ,' J}`)OipL;uBqVݭolj1@r+c'Ј$"9PVP.t4R~H~AE7eY$]'"3I!XE nR"6̗ľ0]mVB('PP"OVE,2Bo]ꄞdlZ&`F% ?*WK_U2a})$c 1Dg V Šrf$j:Uq^8nh)Fv Tй7 A9Q0' f7l4}!GLUndtS6eTZ&v.o> q:PXpϴ:T+m|KXԊ3*o}$X8Aa*|A 4h}6ǙA{]k޹ԕ0=xޮwT$ok3%nY]" L -ʷd{F$CAS)HfU[?8"t1& >94 `O[K>8TyK'#Tq7109ˉԦ6`X۰ֺ\)7M;G %d+A@0%;sUa[况-*;ڛk+pv+_7% 󟏝4̓skw0@; 熥?=vj:?·fPaͯWt'2l:61+gPwLp* ( :0Ls0Y)-(4R95r 7Nc9y7'ǃҁAH@*YrQ!r€sEh,,<_!#xk%K=dZsF335i;{(HhxȈ_؇nHhȉ᠈(PGȊ芯(HhXxȋ苿(HdDxŨȌ(ȈȃH٨ȍ(爎騎ȎH^樂hȏH(Ii Ik  )Iiɑ !ɉ $)')+ɒ-[&~03I5i7))c9? A)C=)uFIIKɔM错NOIUiWY)؈S_ a)cInvekɖm8 ɕoIuiwJy )ؗy8ɘX!)Iiyə陟 |/iY8 )[IɛV7ؚ)IYIiɜIiy;ډ ȝi牞y)婞 )ȞRɟ*Jsr ʠ j jJj֑ʡԹ#J%j$'ʢ-ꢒp/J5j?7ʣ=W4?JEj5GʤMꤋ=OJUjnz3Wʥ]UD^ǃ.͘mHu`p6@J.Cv{q.`YئI}ꂱ Qz80ȕv +gЂdU"+Kp1sm3~v/꫉C\wA,neBf:ө-6`ҬraaJp}b+̺0>zNӪ[JךJҭkQMȆ:WJPCeq[qC֯i KBbk' ˰3gCOd*CByv"Hs99;nU2WT{tVk1;˺KJ%;LF  @R !]@IWkq3^`,[N@rwG@ { Pvߢh,@SK.m8) _pnl7ʳev^GN,"Vп3P9uD P$ LBQZ@  p1gBP1=&{3ga<,rta#UG0k}jk$t02SlÔU չ a;Ir:v5v3pm˰rsF0suyEaXR}N1H i,1@!tt#%}ߙFG6݄op JoSQ]C h)7@6"4}$+)>3ѿr 6àymr@e|ȄZ3|ҿzhG~A  TCu`ػEs1>}Q9{}w' ).GP[=ܷl(:]حzݭPƆE,4 `Dᡆ~u0hޗ]xlűSY+ʯ-( F$4)O Nֳ^N.+fEr =D b%N;4Ysq{nnېP,Ւ >;+QȊHܪ<XrC$`ޫJY;pV0ۆݩDŽT96U9M|CpD%mhĊv.H忽Y. L L>8 (w<#RP+Ю.82xU-P']VS`Dؖv"FQ}) ,Oˈ@R.'O( Ba3' 4mC-pZ5!oRrC$dJmsHo=\ .9%&ȊL'S@N~z p4Z~)}\^ʒ EQZLcV };T@|#o}F\dagTo%K '0Bo0~{000F#2hC "`˜R"Q(zY)1آ6i X, @ a`J#SLAQhh]O b C[B(M@`,X`VQaNraCtIvζCCϙ  .cK.Z@K؎͠Y`t9P#ƙ/#C`I9Ud N݈8B0Mف_ 3Ɖ?@BwbA_ l1@7ʓ^尅gEy$(Hi1`'B zEC_80  [64ev$_W[a6O3}iCJFw8lA*VɌH( [12CN > ,^耏Be\Kᝈ(YhF-@lXzZ(C0vp\:jBn ۔!gK>Pi`v%0֓h 3 ҂ȀhIJ; Ƹ1,ݾFe>emuՁ`IPOEՎCf&& ;!+]*6#`X $O=Ä\A hK tDv3Iŀ)]6*AxhR=k7 ͥ^LBS4oܔոDQ#Soa*6SVeLV [u`kR:Ǹ),Վ,] kW[V-lKMtSlW Y"0q84[-΂ e(V q\ju>9S"T>6:nO[8Jk½a\)c- s\4HWyu|2Anp&-\~ 0Ì}$J){V. 383%0t5Գ51,C4˝Cb?K%RDͣ(k@g,q1a{@^h`)@_|'< S "2N2FA)k_&0Ys0XܔݠYM5'؝^ =U 4!TGEFM@ %E`d^pDhȆ^ 0ŞQ[1_ `}O9(IQ`!@Ŧp_.z<͌aFǩ45N(JL$%a_ >`W#"F!FcShzNTI fa SӮ pDTtQm:bp<$Ԕg0"9ՙY@JhuHX |)AIޓ1$Q(zHۭh#$8bQN%!td,<k$|\[v@3R!2,.G@L6dCG)@EYe3UЇOH`\L$PXX^VjS;R;JKQ#_(K6Lz$ (^n8F;CH34̍x(Th0T=ɹ&^ HK!A1$]B gm:ݙXARu$#b;pWh3dWRBNvp>N2H 8\d%ӡ\>fB-!Ų\rBlZNbcNghԄ""zAh D}5`DM%T5,B'`'T("m l!IUCZ.gՠ2]%]7uwmC '`ψۼg4qJq$"iX[R.tF#70|PC]Kknhu2@^ڮd)!Kr4Q' ʗgj@$Cs^.@su'uZm'Cv';4x:j^d"!lv.@{b$ƧI\ɠ}VB~~%I)u(8@9O)Efj]0hٲjrfhU\h|cfDqhJ˄h͌hU((_g4CGzSՅ %2"h,4)X<)^ތ Z)Ry +ɀqY68`A|,]x7)VXq5Xj j.I $Ϣ6DJGRjnm ~6nTQT6ޤbKPV*AtOg2l?؜ (<M,+>RMbLXP,$ `MN3zvP:("(OYѸzPC z[욾(VVZ-g .aZ auk(-UnV&&An %/!qj_i-a(ݖ#BTy[HAQæٞ+ςCYj ¬!mоQJ**f ܚgm֭^ mm.Ȇ+N. Yo.nC 7LN.B^ndn#nnRMJZnyn嬮nԉo[ .!3j6$d>@2q lFoLo^:/elRl%qJ7xšm &"ARW z/@R+*ɝ,pΏB(ZOl\rx'.oK ץKuʺ~c, [Jױ0T(8;%h.6CJdnB~DŽ->r-ʣ! d(KA`95昶C d{:q5W@: # ?*$syӨR+dvJovƩ+0t,or~2O?M7Ǎ XZ X*raNVUzD K^=ƞR#ajL' rf,tDWML;k; ` 4" 8tCud7RsEEehtG' ʪ{tUfڑL CF4Pn&;,OC]PcQQcȷ*50L0jrCq%M5&ղ)c5h#tc2=ڒ+3Ԟ;@*nBB)<; %+PjG?'4 sN Y+@;`ɢb =J,XvI}Uhl9`@Ej-$Ғ30 @*+J'`Ica g:Ja405 4 ꮤ;c13(N%ĐYBl3$K@㬌~rZ)&!"gswwMP58ktaQ)IBȓJeB!C;ȟ"Md[+aa`Z$J6Ũe%$`z PCa/Lp2C("B(C'@c3Ds>!1(6P'9*:Xʰ/@$#Jȹ4gIm,79~RGqhG)0Ȳu;Ct:R{tZ 6tGO`@"U:j 0EnVP6t 9̑4yB)` xY6XՂϽO@AFDv^{W nO9k`@(EJpYh+Yp(ԷTWAʃQz&,KIډS7D쮖\R E,I0 3-iJ+9.'$fqh#"JChIӐKmG@"B00K8fIJZfR-@C!JeL٘˴:(GZVaص<,6#Z㜔UF\mt6f<0|=l]L p;+ X[oc@١M 4)&HVe55 T@2 e*ɼM9\>U0IqYP#~K[z !aď-EM{tV:㬉{$8MA@l]Z,W!Q0ChS%q;BYzmݘp ت !T'9ki-6PJl9 yP N. `0cyathNc%ԒUl`02x2?嶥Zlo/\9U>ܜCO=c9hN- Ho!Μ2Sz^g`.@~D=_]j5B%C˂`d43i\zԈ`y_uXCA֜5\.ZlZ {3LS|lSz:ٲ6ɳ]me}r_u~*9bۛjl ql-U'n7I\xqw^8h>`{q("@rqrsf(*G_rrsCsC&BlW9\sMҀ+C7&wWJtePp[2KAj01X'f#4u-ZawkBddjG)(&trG@:eaYxk!XmUg,:90J 5y`qø-AЃeqϓD(6hqc5(Ƈw eWW8Y[J@th0]mÆ|b%tYvC@Hz[9v=.M(+|gjҎ0PrP[ U(N7%~S|A &"#9D8֋J=Hr浌PЌvF`64~{R\-}귑wSm\V@&&A9E88hfx&cۆ"0I~"4'^Gjѐ(imIrWN6 Ň1 eCW*Y+b`($o3fOPCjN( |+0`pOmV2 h *W."S nbF#Zh Y Lfq_Y+Kova(8 շy1 ~Z49Ancr_h 0p-Օ r]t`5Hg_8y Ѩ R"KbP t] !xU@p<(24P I_r}9 EmyiJMڛS|5 `WӖ$׆`~S p故&3 ]R_uii^Ъ?Ku</)ҊQ2tR}Gp|q6m3H$ r9|ɠaa@KQZ!׆/Z prU 9m,zIx1 :J#F1:JN>Q?j~A[B|J:SKʤdbQS`X*=Zmӥ_w5io PʦmZ 1=:IvZo4Fڴ5[%?pBj`Bd}1PLpbhoyЩB6;pZn{媰ZyZb@m ԫ=:Gj(amU9]#jQ rPպ YC²V@KRsPdVKk19:[+0@mQ"h n &U/$I~ً8mT (BM0|eL,f p q;x"*`orOnF,֭T#j(t?[>p(a;m!۬ PEB;B] V31Y⻮A6*;}7x&.rm} O;T홺kj,G;&0e i`Zk`4tƆ,HM( jR6%zȖFyDk;\Bi d%6,¸9gGRѴ6(lH8&yRn`\e% B1b_f{_,.Wܦplä8L|Xv̻$Lf\0:5+%fdS]4Jm,`=%Ǵ[*El~ ulCȵ, )| ȏ?#(@м|Af>jjl\sʿ #I|0790KۉF|k|h ˂ ܭ )f 5$u@#txO ])}l"\ETy[[i C ]|фDVt}yz6~׀m(jv،WȠC܀؎ݞgq_-2R,X( *G=mcR ͑-چ<ר9;ڈװ=۴͂~A P2WUmI}W=ܙ=ǭ qMMYнklC׬m=]} ޏM}>^v] >^᳝ ">$^}&,.02>4*(^:<>@B7E>HJLNPG~SV~XZ\^ ^>d^f~hj9bpr>t^vo.y~|~肎{nɅ>舞芾莾)mއ^~阞q>k>n➎^ꪾr^~븞N޲>>^~^ʾξɎt^~ӞtNe>N>^>ނ~_>H_ ?n 8"?$_ln*,Ď.?4_6?2O<>c"@_FHMINP;LVX>]Z`b_\^?hj,ppr?\tz*ll|?yea4?#o?O)_/?/e ݻ_/V=}`@̆Fi!ğUUv(`31@ҟotΑȻ+bg/ y±<ӵ}㹾!h<"%|B)j.,*Qpс@| fv00őEi,,(5AFJNRVZ^bfjnrvz~Z~  29 Qh5<& 8 $j, "8ٞ~g"4!ė$ 13^ *t(Q˕R69%Ч@i L0D96u!El!5$S4| 6|ha@A\Ff{Ur[@jF؇g?-z4ҦOuZ 6"VQ7ubƙճxx-qybvkR@n0&J7+x ٌe XVf+ 2ؠB(jlȖm~l қ>!P%r 6;DGԹudPZuEjjM1o=~C1 g tg$PL[mIxp i0 A,$`9%9"Z"`f30WzX k!э"P0dGKФ6E9BXDl1*d:ybɀrl vFg{' ʨ[碻2iy8P¥s*ætU  *'DTj 17UkՋ]Q-G#Z&S'qJ+A 3+P3rGpl!G#K3]0ǰ6Gq x2~:ؖ7o#LS@*VC&FM> .4LxZ,@";`~CQs6K1aM^駣:D7l{6 \ 4 dܧb~2?m>A(wt@9 wWa@0a8GMĹGe䓷kqȹ t^Tg"0 \X' vjnZzǃj\<(HXiAwxN mn0XTD>1`ѝ G!"-`F |#h+b1ZZYS>ep,]XH0-@Ѓ-p?>l=|4!250d|z"[)o[%)KiSKūe`2 kAapq\3u;B7p%/rb~| c\5<|QրpxD>C$*2'=q& BC$jVȥ8e+U'0m@lJHɭ&5cM .杼 Nd Dv)Mkjӛvj|>O:XHD艮@p]B!H+Vs'O6D:l8@ h |oE2?+;yt0?q׿65: GuvcvV*ܨ1ZV!]'V`*lA1M)Ž-`p)F]M৷Uo:3$b@Dftҝ.u^ag3jًQF!Cz2a e"h(:;k*m=aZ8V;h흰qaPiKY4F029ȝ3aa(m$b P{ie:}8pC</w58l1@m Fq?}M-ds!3- cmw~}4c&I|vb`%3iKL~,A&C=0Q*f:C6@ET0P?k[9Z>i."|k~NܠE'/5ҷ::w}T1mM!-v@{xx o0Y: p 'Y @ 3'DMC^!C?5CxnY7=6Mҷ83@=!zN0{;W6ɹW ے^9K49BQ\Y_]`iF$)4d65h@-\ %E[R4y¡`:BUVK   @/ x]'$ /ߪ!0V, `Dɠ\Wd!I 1&` ` tM 5a:#BbuM!}X!E!lP``l'a ḭWp}Zʟ, 8P,|pNÛ,F22c32@/|-&N!J&`݉!*ڜ0t!"` 2il _2}# m҅MeJ[ OX3RdEZ$<1 dT4  d"x!#.}& l ^:D ;*If]3) 2ABCC@DEjVrd1ՠHH^?d& $?L]-ɘ,@@ZR[xSp 6 Slc&qUP'!XP]$K@Eā8vhfi~Lm Z STJp'Cw9:ŸVe %K`rFdڋ `UƼPwd*i'yĚhPiPY&`VNǗ '|f؂ZҶLǿA~) H*\ȰÇ#JHŋ3jȱǏ CIɓ(S\O<,cʜI͛8sɳϟ@ Jѣ4]Ґ箩ӧPJJ 3Vʵׯ`jm)YhӪ]˶FgݻxHsaKÈ{# #KLed̹ϠCOʜñ ȢS^ͺ,q.۸sڼ N7fnУCnCҳkν.5KOC˟O~3÷Ͽ &`PF(5ƒff v($؇-h,W(4hĸŒ8@ <iH&Iʐ)PF)!LXfjTf\)dZ WlYÙ%t&$i| %#砄"^i袌6Z"褔VJӀ 0 4@ 08zIpj&j *)5*Rºb$,Jli(:*ꪭZફ뺞/4@,F>[F*p-nP ݸYAT³ 0j,T+y m ڌ@@ 0 0 38`3ͮ.L]@ c2/d+0؊kC?3ɜP44ܚ@xsɹZr<` 13y<@"Qa*"г7me k&r-DJXoRø $W֨Z@/>xZܦMb?s쳢V[|; ?`#wz ,] `05 M~R5`\`jiVx,-~_j8u2W x%4"㬠4!ā >y`4 n ",Aș8މzxpA&h;k |Af+z7TUk!Q@>.o-%M܏p۟׫-_'⮈4h`Bp2Y$, Q4'¿`ۢ#Uf dH-dR޼ ԙ5{$fD$lJ')mw(N Ujiqћ_|8JdКhTF6>i;6@(}Dzt G(U& @T= Ir[!SGDRax3j 9n=TbTuDzj]$ئ Ͽ) } P 9cB&ȩ@VJ Ub\Q`cdH8Ū9<Pg>=`b+ȹY U(kZӎSRmYҊiӣL5pu$rg[_}&U U@vcd\^VGp Ҕgg%?κY2vR@4ДEdy >=tDRYTxS+zÊ FBwcթxV5/c+fՒulmƾ<}U"Ho["@`n(- PkΊ¤-/'ڱ }ml9ڒe-zO fvM-yE uխ/LVW-Ax9iWZ"g~KM(WA/}PS5ցa1<ufي 0Q.llYGB#Xg;,FJ]B|#z͝.jlH, # 囚@%r?<285ehy$kw Ln4Þg\5 fH3И=hVlQ+0,▹e@ļPk ]sVR97``D,9LvݎcTS7G+QuHw-&:~a)ZzW|)uRJ>ZP #Io@/ďO [SOx~>V|& { ƭ9Y*Q``풫f|-'{5@1Hn:p&pzge{v6~'܉U>$O@cf3_ pwG*j+4]^s2${SW"p37y3]|W6}Ϸ8,#hW}8Z-D]? GpK h4Ϣ{S/҄3PzA0l/PlE{b{{2{{]* |1P|SHEZK856$W8"n}0}j}}>WWGw?56@27gL8wqK8x+&aXx=yjĀI1Xu(-8c;cf;DϘW2XZ~҇Ya?J1w*0hs&g*F(ЄT8RxFQZSyw'}ׅ"҆fbdUhX,jx5Ŕs(DuHCuyXYŇV+6+Gᄈ `ȈxocUe 5d%Չ,5y>FXu֊iu5Dleb-` T3Sotf $D;H?T@5sbb`y)9^.$~u#y] ~2'UI2'#*O%MPQ/c-<bGtSY+#uc9v`HvG-SZ4.J~9;8*kx.? CF49cf(Ztc-vHO"00B^Ob9R ck8JZW,RtslVdgy^S-Cg^W=Cc *tG/Q|Zw&Ja c* [(I7`_u)١My'&9/+pfRCb磚,Sznz)c{di*|ś5Dv:I6JUǙG6n{']#sY5GVt[q99]~yS\JT22YXUH4`(ß>柊2Lj(h E kj=/oS:J:k:Շx/(,P5H5&CGYnb^)C:TbHj=J::[JKYeiʮ\Jokcfh:|cng`u1:C}6+;m@@.`h:ZOn~;穵)VFoRxätVgzzU@cr@xς*!:KڣuצKYӭ,Y0p7L~qȥTSKUO,42r]j:Ls:)pGXrb"7gKRF2;pd'PE"P/ @_M)Z(O$9-P^c-u9V"rٹ)5J)?)D?GRh~60uwu6mzCY6!S6CSBgDe2[6ժLxNCl;^{q607PYRz`bd[ˆvDDx%| w ]etʲM|qIb_'_9 GRބ ^(dADi[C'~WSkTA$-O1:HU5Do ]YV_E 5\⚨UMPX싢 yt Tp5a*R%mKeid**y |NZ$Q9=)&[v[KJWoǩW8li:L\ =*|YιxLZX5z\z*3"M2Gg$sXLv30Y Pn1,<\G?\g50z7f罋 {G2>K j[xBQ+MsELƃ6Aw kGƐM4Ǐ,l&LL\'WQ EE.}N)3'z*y͇ƓΜLpFW0Ģmi ʴz*Rn \I4]N QIv/djM ֟;uvo1qXVmmӊ7.y5z00> 6lp=A76+|;ӊ_A 0\ޙ7$2[ms7pb'>Rx^MPg@~R43Ϝkӏ2nMJH%O]+0\x觉GCEL.W筟~Cn_M@Mp\؉}*~AW2ϯj >EEES1`\(42A2&XgK~Banw|7Pt6:o(5=P+p@h34%}X,|ItcNۛY6oa8ܘn `/L2E+i4.4Jx5%/ϕ4_+C>3WsEN`fAW ꒂf_p/rkQ%:FuG$`.nVj'-CF '{O&JE/S'֓6fdĻwoWFc/QPOc m^Bל?yPtXEO2;9ꎃt;Rd0E"Q#_7"(! |@q< ͍n%`Md HIy)0AvAH)4b© ]@%h754e?`Ε53J ϸWT@X:]B8NRУ,Yj 8h #Ę0+^$n^*|\4f`(: ǁR:5).h11Q,;ETrHdˎ1ՔU@Pӎ@5eFu!ZҘ#q] s U4?>do{9(1+ )* Tn)w@Əmz:%33t5EC!K^TiwO+(%W*)}A\N[Sf3ИMN57x] 5N;3#(pOO?3  @P+ B& pw''gxd4D-Ea1LB؄W} 5XP7pI-JSܨTT$#YUlK5Y# ek8[(tՂxX^W%(!Cy؞ZQ:q^XYZf+ugL 0jK1l*呹o3&R\L̹ᜭBC x]Fx:\Ԉe4 Z.Y,6E qL K &tǾ؛@iXQ+og1+x#idya Rf'3N $B >j 5SC`X 8 FλBmB`: *eia#Ec`0r|eͅ@o94;]{S&5QPd~Bj0@, 6JIi] g7p6\*]#G38m@v̆ڌpqQxHa@nw,LІ!avc)mKyA-"KWښoIol`N+0 aZ (fi e;-@$C6ֻe&zb:.N4|Q8as 4SAՆӶn\#6>wA>!ۛxW7l p'Ⓒ-.p Sآ]$yzsׄ u*c[~T땻+w xbCr8%+D*+DxQT#XJXp](@'"`C5fDc|1 tg)@ :؂kFSUDC5%n l\jy@$3ܲ1g#Y@<#֌" s0O0t©Q}+A 4j~D&G* kC9%T~aЪTd,CJNwLF`STmQX|G`QrQS djkͤ7R&_c #)a)l Q$cU.-`N|wT+jcAO9,H@$DFv H(4J'IF MFhA@M8E5bdZKatie?Ս! /efRNx!( d^9d dOSP_@*+HyK0,VA3Z^U'ָ:աD ϶s!hm @b6XQEx]3Cm>(i@ A-FwXmc}Y/Lo&R}yCZYX(LrVKd>bRԙ 0JĄ.q]+WC-Mj\"DJYẑȮF]MxncSC26ra-M|7ejݗ1[8N.?a` *Px fsia!~Ro$A;8PRaY.'c)qEtf[\@JYH[d"߻[ZsXs.dr@:]^ᨍ Qg4`-p` 6%.6j/@)zHQWdx9ti3ܐolR0dU%}W Ԍ ̈́"7 r 9 =GX04KYK* J& G3]Oz6Ig/#u1 D5A7w:6NRWޞlPi^XEY`a(bYPAX ~\eS4ucYT/"͡RpË]Քb#@P fT,!V< s| ԝF΅߅n@DABLpLEWJ2xƬ!pcl=W]A9bN6]ҧx~AmAYR6Q " %6%FKTBV6 px =Yj[ZrW%e),.J^ee i^fp1 bc&-J [ЭHm-C[**Hn0n ;NVP„ƀ#JR_.G7B9Dp9-BaAF@Kױlj%kW5"UfLT%/N p!EeB <8\(چyT1,qG?E2Itf`1#+=);(êhz1)!'Z}ݣ6BI'aC>.f'H`i*u N沧p~L1:s?0]!bLvI}g1;ʇMAgBAb1ȱ-]`GSngqM "7/E\#$ .j2C:B&+)''CpY1,R&NfBqr5&/uH,u*ܥ0p1wM;tVuh 7@~s0Ƀ9JA3•<=C3_\[?2@{@_t^I.4pD5(p[DHX`tDGGmIwIJJKhPl%RG5+G2|ǾX.%nE>3ݝ!fȉY5DԜ'6i@E}!292J ӉtFa US!mBoI670$C| h$K eRxU/\#fʚF~PsIHEe*OAUjT0!#@Ӧ7aew9@^U#ģ^Շ~;#ؓ+ Cc{_s/`&k d|ǛEe3Ӂsz3`P_bہ& ye'SRȦȟ ș ^xF&(`40y_̈́+!{'h94:R8MRxL5"1$fκ:&ӮX2GX;(.nwJ|LP*܂܏{DZ QBO`Ｔ큮p:rN9W F3-,X5?lNqX|Ur?@oj)/g=`:7А흸s,vw w(l׵Ҩ:,C0軮*,/ɰAױob߃c:>Jw+rML;7b{Qg4òGμ-ן;_rj/&3CoA|HoR<\*Й utXGv @x gW'8! Xac)o.m5 Fr`Mj{hfCp#@E $pĨ( #hŸn!RG?r-6+V XTj̓2Q @\B zi͍_۱xpAK̅S(SBhAD?Dlt PmuK !>94&,$r m$kK43f =Pb.Ky/ s$ ,?*[/f8 un݌^4/';}Q mU{\C⭲JhW}H'ȸf@)8D}"p}\z 2_'.ȗߏ[&@N.AC^*{3A8& RՀMΫS8 .p+ٶG |)TjF;y~a qDwqLl(JqT,jq\Dk|d,ψ4qll8q(uTUӢ&ZŪW ְ՞Q5PWNJִulYMնut]|_ +{ a*Ve` Jv} KjveΊv--Z?ZӪvmmOQ+UvEakVv;qX w-0wms׈\)ԭu&qw ^iW-yϋ^M{ :ɕ}nկ w N a. /Nؗΰ? bnؙOb%N_ w1ozx bC"C}A"3%^< p%h" >.2cr!`]2á:c` %JFEJPg`A{!Bh58Go!d#r#'(oVVaR ho`* 8qi?w>+6:TZ03 ,PTAZ A@o LP_0#`C&,xs,q8DBf~ l3E߬eyڗ3ʖ >4}Q㞍@cSVKZ뮊OԁI} &pG yX=]m HiWa߁3ⱓe~tKT{\!ua hV#eIрI<=ΓZ9~u>8Ge7%gGr}qv"b};0ww't>Szgs>x# gxLxߠxvx1yGSyryyLyXyz(t p@~W}Hgz gq0{,R{-w2#fÂ÷.ŧ!&#Ḑ> X}ԗקؠ}=H.Q}/ᗀBuHDSotPEhg||k77:ACxX -h6p9$s !؂0a{82$@)bZ)n` |$g&4"سhj 7Z p|np23 ` ñP 1d203'{&C2dE {'`,8tLRsszQ81<1'axRW:#XG׍>S4o  @aeN5SX ,i֖ oQ a8BTp1 ' <{3 5(#艽Q( tz҆Q"Šx1J c{4 Fvƈ԰f4Sט b(h|30#!HhzID(f8q7(hHz$ل$ɄI6iɁ )}@ i^$Nӑ[\ P (+)(hW 6cU;WG~f;\} <8Q70VxL8ٝ s`xgZ0xoX5?F)'QW8Skв6"^ wIG7<eP 'zQ=\QB2s  )!Qp^ Zp;( 7xsBS,.A '&  &њҍ*:}9D ݠE -/ @WѣoTX0G0 1"iFa X Bࣸ !j~^&ipig)S+eF5"]++06(ٷl隦!*K{lG`|6pNkoǚh7sӧIxC 0`8a8S ҡ(觽cdZ 0G~B~ 0RG(Bi|`9f_J4^аiuH5:(d@ H:Z-Ԙl`ꯝgƗ f0`=lSx0wK ZP@ p=ǜ/3jG1M{ {g(w]J`jkf+hǙh;pnȫ @#/|ԛ17˒€; #1( =KpGwXq0iȮ,7p! i7L8{ /lZo|{Ќ|透I& Ȅ e-P<|Ƥ"`\ +!83ZP(Zį|e0ſ'p7ȀY#J!ZpQw^ƓǨ"2bIy<{,{}\ A SÇ+87\}:#:-x';LՒ2 hʡ,V C|\3Ij˲˺׼ ?}P1<+s܁ *eҼ ،Liaݼ|"cyj+k$Gϥ;Vϡ]\mec8xТ@*EX@lq*RwCWf (Is& ܁J!FS/I} P;'Ud5v ?!-R Ih3!E8[ٟv"K@1- Yuܥ 0qss VjmB%DB7q6+XE΋ \;S` ^4@;ߟЗKz!F~Hm1}J!䑰J>mRa- ]_f#pΐܷo}0TC1e^i렞˼:kZÎ.Ɏ~:Vwe#ݞo~q_^ IZiTь .*߹AC~fX_z ES(Oo20#_z%'),O-mSB:O2<7 @p'Z/3@I˜ &w| F`W`0\^A:T87^Wl5 cik0YIL Y]a]#VA# J&@eH$ҋBLg*QLLlNT 5vvvv76SL/ꀮaU/|rUC^'B-q. ^kP%ʴCԞ tݧP4.T]5 ת_I8`\FhZ{  \`Li4̐Q*@ .B\1["r$[#FOPk h!NN_}0`96 '%2.@ɮ YP)a!Ya! F _&MARDH!4 $r96^%"ꈡS_|AD4M@I]A!LEVdxb'@$Xb h`p-n^` `, ۑF W ͂Ex|! a-G(r4 Ca 0eY^ev-@U\#Fse&|"Tnz5$R( N`d" `DLMoXNa"#eq"z-u fP?,fa}'; %"H@neK!ƣ=^vҀo>fGZY5eFlB!BdΈe mj\&=€TAb΄hFc(2d%nfZpg~f::.iXjj&JrN lfږmBnNYorApv*h JrZ=t*^P~JАCz.k}+t4.bJ1(0.20x$+fX颉:Q\n纮سb 힌zZ rH2Z, H<8K%mu_!w $%1=;솁D+Pt@rt @:KY-vͣ1?Y^"{4 4D{xgѤ026Dr ϭ-EPHsij@PZrN-6,+7̰Lsnr\f3nGks8g9:%,D33s3T^ς 4N4SBqw=OMKAUtTrBF+p.dxt\ˢIJXMtqǴ&MMlNsN7WOSj>\P'PQ;)+(S1H2[af7t|~u58מu/j5+QVq55,_{ `3+;rXP~e7LSq xF{Ga _WíaPMi0]x-[)[tOMHІ:>πQ"NȎ~"R̓A 82WRu56A!W9wIa`ѯĮ#\)ZXpbj S=(p:1>sOlpp0ϏӜ gKJe,eB8qqks_% ~'JE[11\*90S;B]E&*HA |ޝȏqM'="g{sEA3ԠJUhb0lTH@af#xZ۴6uL=94/6kahi j46N% Z u/1` *"U9@HZ/N96Z9H*jC=4_7̓Ό*&)G6L6"cZ9Q4$/Zg*@zqֲ 'g80X[8"$#>ΈIG/mzQTpF fQB`MLa$cP4hTqc-*9N35*Y-3FŢ}J,ٜ:Ș@MGaoAܵr0W`,UapёPH*%`c@_w@Qj3 j.D+!110pyY4YUɕpMm ]Nu)9un-?Xwc8ab@"^3 #=p^`@S4T6(Ǔ|}N8U]RN; `"كmN@dgVA kl0< P()EFY鈠lؑ4`4 G4j76$[ RX-$U?5TҙUHC!m_(ƩhWo=\zBf`y>P !Ic}RсB%Cf;I&nUZe$7j @FE n `"opt\2r@J°4x'GD7ޮ)w( kw' pލW{>_ه33JrZFAػd1dM43@M<"d4=$wL"ILg. 0$J\`ۢB.Ze=nSxYTrDAC@="g2֥;Ӏ03, Q뙂87\w5 ܩB Ʊ% &Bpu2XP޴ y!Y¤L], x*hYax/i;$j@QFU1*F8;SŹgE;<Ӏ?9<@4-ۑWukl=Q=|\(pD'r*4Y7v=y &%$IVa%iΆ:lh.ѯ\k+юz ̐nB"cH% ދ+LgZq RQ(#JӞ*=(.)S\M-RԦp%I69uG)(QծӦ[éSt zhMZֶp\J׺Ŭ! xj׾ `KMAG *d'KZaց hGKҚMj-Yxx ]lgKͭnw[=6 pKM-&ʍtKZ=-t\&6 xK .2{|KW`o klXB'/;0% | @ΰ7{Fc?L(NqxC< *gL8,I@la1&;Pˀd%GXβ)^沘L2yžW6p6[8xγ/;yπMh.F;Z.AMJ[ҘJI0L{Ӡ7NԨNLjSհ}ָε5\k5N[zЎ f7ζZ{Mr; v,.Mzeޫ~[M\; 'NC;]7ոGNCW VgNKw/ֹχNc< iA좄~pY(>N =QuAFdA=KKgfeQr>O0L,]$!pi%u?%FImNf˕R pDk =eA!cRH@O9`b:+LAX!X"3dB" =O#GP fc |!U՚q1 W`-~w0k3P Yoqs  bG(.x)*qt@aR 5RQ$`+@=a[qsxJ~:z&HG/uG)*@$p:Nw *d$"Ѫc3aptz҅f2SQwVH19J#7߀*&KS v|ʕcEj 'Y7$ 7 pG7J굹p[)xY{LCH KjKe!b *z8c ) @ 1Ж㹐tCwr$(L) C9ۦR{ENpA4wqp'XPDuMd)J6(4IRk){;|}=E4dETp jZA NX$-H[IЊDuҤG(IgR, Ie ̹"7قȻS;v̋ Ӌ, ؋weؽH(DH` ꫩnԾ zʠ7TE{ ˣ|Syw ls:ưRp\$&(lŒ<.nC@$= >!i8iy&11EઘJOk X0]yGҀaLT"b0V/EWkp1xlq|lAɔrۋ{'<[# }ǖd\pI<ɊQpٙDɠ|}셉dʒ˾2=s$$V &+̈:vmNu-z 4[0"v> R3hĊ S}9  17}[ly] ɭԐ~JP]Ĉ-)*+c XQƯBv*}SjܽM~QNj\Q}'}hl ֭% W]}]P 4ݐg!jQoNuY&'cکKĂ C}BG|Is+v7*y Ҍp#ݍ%GeIlIE39 "cm*1~-b`$+gA)P^%U WZ[`^Јn7]>%< Kslwy>"⮌5O9o"׳$0.. ( iS2r19*ɠ#n海ѮRv+w% A,JPfNž/W7 24t ?%bnN@иTkzK؂* 'pM6?G_[yFLox\V?0P1D34* 8|0'3h^Ü_zP"P )O\HLQqٕq z#'h,g#{ϳ NQMWM+TߏV߬Z); SÜЧDBmJoO!?*Dx/к}_! Eߠ5/hog>==g咠%/˲]pЗl$&\_W 8ykJ{$z,@#ʅk|B US8#ZÆ=9{@ ĴPa400@@$p@Lf?X]q>裓^Φn 8GҖh׶ cq!8~;3.oty܍aWp_@Csf(*.s*@b@}ʅB@;s} a{8+ $%R`+OK}*h b0ܠ Z׊աhABH{|pǃPw16jؑpXkU@'IP&=[ 0S} . y џ?@S̢FTC!%!<9ٓ*׈@51 N9g{(Td9F/ 'pG%d #GB2 +@x҂S0SBPԮ1%FjㆨԆ<23talEW`%O>8E=ኴТ=/t>Qŝ5j`+8ʱv:1V2Di 8EJ2'?QPr&a OOL9%) t@H 14#*E!SX( :z*iWOʉޒhprxIQq#1рQy)O37s`-10Ku @B?n_8oɩ$jْe!geNM ~y,%$Z8x7id 6ֶ>Tk+c9Z{W qLr!&$\ ;o5DVp 0iU 0o&*4yZ@7a[_T8QfK8"@6!7W:֛̃0aB4Ql6g9ȝWCz'[tqǛNcAҔujM:]f\6Ul]t;w#i][VşwSa]n~?R²c<q&8y(\* q JBGkn<<Y=B:ыngj ~C=R:ի.uĺջ=b~?d_;=V1;Юv=z;&c< o#^tWC>ׅw@>=K={ߞ=o#_C?Uc?>U\?o~+???o_?G`!`:B)0`Zb`JKj` ?qx` Z^- ` jP  `. ` !.%a*2a RJRaTZrab zaƗavaޚa b!& "2b#"":$Rb%N$6$Z&rb'&n'(ہbib)*^ݵb,,+"-b.^Aa/c0- c11F19UZv|Ey3 s5Mۣ!*#4AA8XZ(Y O$@A,<5vaXZ-54" P) w]5B8r% 6a7n7d;D9n::5<;ģ==C>R?2? @@ EZv(0#9N@D6"E:c켙8Z6Qψg8UPtͩ!U %ޤ "Ueel%Z兰؂e%u\\RB]h[^TxfAXHab6c$aid'8gY&`lAv&~T{bfhxALD?<W^@礼[\oAEAfT@$}XD%gUO.8G;F>'%&hN[5}SdƌRS(!p'hYN'!U̇NBSҐAּ[()C(G(Gpe@DI7(!@ tL"ܖpe|n\W" 4/Hi))-(NiP7¡Ā=d€$'$}E**\Ԑ-)6iU<~¡TJ!Xpia (i"cAԛ)J& 0i* Ej/jE%,,* O!q+h p*JPjc.i~*eJ}~Z-Pƪ *U*8=-ǿ׬ԓMqF_Irhϸ}49;3I\D =OlTXWNMQ8X *,yAA+t1@P@qifhV>fA|$Y}Wfv\+(.~x,/XOHe8FlNTT,uEn+xrR%eɦɾP,TI˺,4jZZ"\qՎ\ES 0CHBT m]hB5$b rLKF^a&˂` WZbBP YN\$b``kGEsaHHh߅𰮉Z배6p O԰Tp i+JM1.1}f2-8 Olnnbd˨AklB#XM+q,2@++ (!2e(C0I82$[$C{W@b(A, 29[ 뢬^Ln;.( @,5⅂%/l. 3S.<35 DoC,Ц*Ò0D` ܅BE {|@@QB,#xX6*BC?NnTVOlL|MZh4P-.4L̲j&u oiVCHRP-*GAǓB4쪘>åЇPXi4Yvb$9@SQofo;v6Jh߀{eCA"`oa;abrJ(d7dWvNf{r6Kp܎jl?ojjMks~lUmmjn#5Nqw7 <$r m{BJ7 Puc8 w{RxAy 527w@oA8}wwS\nsbp~J>0yB8zBAuڪoobNx/KOIsx^gadIvAD<מ1ۂ"E9 ڦJU@l$fsz0/ HA]9 ֭:dfm9S (HACe2(Ým[잫g++66d·)7w:@£]:o5;OO_5$۩G(K h}zͺB¯@gzgod>3{/w<;*v3C@FtCb 0f)eJ\Ae-d#'P{0+,P'=Zl}b9h-<;Zon/ ,t+OgnPuD4};uy|/jZû|5Rv!9}=S< }}*.*;Wi/,D!]iRN* g+9=sLQ;-=W3hZ[ocԌsLejxt #œYb$Cjp L ĢL*& PgruaŢpb0M DvP  =2//6@fF5cՒ p(GWF% C@`EBGBPfUpp6 uIEٲ剆*E| gs xvR:jR #y@w@ `En "CmMJhg=Xfj\#ѤHʕ,[| 3̙4kڴRTn0I $IL,:B4T(s+nz@ܢQi% @ce) `EMR%-Mȿ;"ch7`zxy$X(E$p؆ ]`+hX9;4\_QR C!\.`QJjZ8GڵklSU}?ۿ$9z<'=@k6L $eD%^ T`U Ue"V%6$k 8 hlxsx]'`Q^KsV`6`b7dZhj7`f́h;ޑjvBk'lDqK&o{vpɵ@XpFh_ <I%HG9NhWwb &A^]z4^iniW8wie}%dX _$p&Ǚ` BlqTtRb!r]&P$,h4g? %Isvw:;ٰS`4#Ƙ"(  2% bOp8TuhCeUVS! _"b`FmԠO$`:(PBJg lQ{D[aS cP<ՐXDCtI|Z2ZZobo D&b}9C kxhP> 2I]JG^TgKSFPѰDVT\lZzFqE!$` f D:(XAz3oGdFIVl9 Ԗ|y42 (s}(8%8Ô/ 2q}JLy.ń^]8]|J@2nwa<1!G.5 l&/P۟@eʑWCG`Fb3m M+]# 7"k%;B3,PSB4y# |W{x>[( bn؆J1'MtqFA W UfSS C:h 9#!Ag{~7S X%/*]r@ׁ;-x `$;>~{,4H{k6 | 0X|^#I߸RЈqz^@K`m\j^`{eq>t)|~nzj~F@ ԎOŋipzZnNz}[9!FXI] ;o#o$~}Ҽx (T92gF@]W}4v]-jcg;0L&z#A!t 15?KR+C8UXP#7 Xp> {}4_3o'!q6FX>I" NAa1s@y7CrGEv.OQsX(.e@IЃYB L1F4~@Pm68e3s& wy.0:P|؇4='cH$ ֆ>az+pzvAb'%^8zGw|Pn. "QnWD0.sX8>Ԁ;Sw',+t2Dn@ EQr@TL#V3t(FWf\AEpoAav@3]lC{(I8-p>1[ fbHVH H<)RŁ ُA{q"qg5zfvHf('Fv=c5Hhv$&Ԩl֨؈H1 B (iJɔȌY&@o؏ٔ"{,92YIHy y yll  I VCY b@ ih( $x Sfh@%gY) ps:7_u <\28 d D^7wi*S @xJ ۨpvG4ɍ@WS^t`/TP 0~ ϩ5 "@3DF&_Kb>.z j >i)R 9i)`@V)Y).yC" 5BvY6i,)'+$sEV`΁Igқ;,џqH!Y-kEƜ^e9fo YhI]0?R5X`y-%KFa9Lukhf* P)ꨏJZiIQPu 1EC- Yu:P.+ R9Pk2Qu =Zid;J+ o72uJ:8z^Uz !J5.GB`bk_ Kf_z E1XvT6eZ +!3@OPڔj Pzy:*Wƫ<>0 P銬67:ӚoqU9S}0jEzw- *1 Z" Tx4/2gi FeP l q Pe ez8[ƐXպCvG4A E5%BE0Y.@!{ԭo>'B[pLl;t$Yᦞ%7?;X[e>{"p8J 2 ǻ𑽗&@v Zӛ pVHk P{P[8iȿLZ.p[  ,7rh{'!%l')+H$\#1,3L5l7Ll?.=? A,CIKME|N,SLUlW7GWQYT H]FnH^ugPi^4[w}l x}vq0S`^bnz@׺懎^0 +vͱ fL^ÜNG鶭@6PjuCFG.[0Ug^ڜ饛}{8>^w79.H;|uNPEU^Wxe)>LVt 8cqh_!`ne.1JIP0߮))^NoO'@@~qCܢ8K|0n/y\g!V ?4 j' sJР1JO[4%6!82  ?Y? F/1.ռcO8!/OTV)l@:qe{z n\R?=n.rtoou/Gp)  G۳/~U>8^x羅Ko;N2oNy/YWW?!C.(Q_r_Cءo\58;{ȕ"9JI? #+ۺ.1[nN2̮X#k0!' IB&;3:^7<.;>?` aA@OZCLTQCCRhi[ث-n.o/p0q1"#Zddefg((0H눫o۬Vmr;|<}=~ x@&2hR$ǀGjF4rx.,i$ʔ*Wl%L4dX#QA*DT v1:&v1Rj*֬Zrj\N5bp*9N 8qR#rHgg@3/) 8!Q^'Sl2̚7s5fl`5G5fЈoMӮ@ܺ@PLNv.n8ʗ3o>Lca_knڷÓddo= xM? 8 W >! J8!Zx!< b!!8"%fpK'"18#5"+ࡍ=#A 9$+6X$M:$QJّ\$YÒSj%]z%Tŕ/d&i&m9epuy'y!P{ :(z(e}>' "(J:)(F^Z)z)҂-z*Ꝧ :+zk+ ;*,:;6 Z{-C j-;n/ܺ-骻.an ;/.,{/o/|0‘  ;0p1k1{1!<2%|2)2-21<35|393=3A =4E}4I+4M; 2K=5UʫYk5Qb5a=v_}6iݟk6qgֶu}7*ѝ7}1{>83+8o8K>y~[~939{>x⟋>:^:ꩫ.!;DOCS/SERVER/vlan.gif0000755000000000000000000001066311656574604011160 0ustar GIF89a*?*?*_*_U*_*_**U****U****U****U*ߪ***U**UUUUUUUUUUU?U?UU?U?U_U_UU_U_UUUUUUUUUUUUUUUUUUUߪUUUUUUUU??U??__U__UUUUߪUUU??U??__U__UUUUߪUUU??U??__U__UԟԟUԟԟԿԿUԿԿUߪUUU??U??__U__UUUUߪU3fUUUUߪU**U****U***?*?U𠠤, H*\ȰÇ#JHŋ3jȱǏ CIѐ3raʕZL!6q@C0=J`O$*]^Z %(^ V/kU,ٰP|ziE)@ 1Ĵ߿ hd jqW1 hbƐ% `\ 8XӅO &#i^˞M`TWDVpdg|[\bAZ ]:"Wl]N6_}5bKOy]^}6ހ_!Uyu ]IulE(H$`yTW1 &y=҃NaS Ձ r+$7cH`0 S|)fe-$W#m _Qs pUyB$h浟Ox+"˦2~_^ۖ "<0ho `é{kllNgJ2CJFQfPa )UxO\ʰa t%:d]`0S֭d]HxD @]ԡM¯'4ROu5لA >dp(6PɵBAt6Ʈm k6Xgh{ᵭ!GWf^gu^ieWYN,暧˂}ItIؠ͞lrמ6Jm'|r><$WogO:Ο }R/r/ /#o_|s_'0TKwv # Ab@*C`>Mp# 23%A"-ta(C pG50?Pȑ~s`> 0Lh(ZPQDaEOըOрod#58C8)>2gxHB DT&$C:R##Iɿ<$%LyS 8kq_d񢧔E-rW@y'U2I1^N+@ /i%L@e%B+Kd.Eiiq{ .vhc g.EI%Xh\^ЩNA4Ж@h+\sx"sZCRxG lq<%jXeD%QH8W:ֱYJG?{.Q>HZѩCЇ$C>Q&cai]F^JT:ҡD\fy*ŸMMMm,Y~zQi4?jXֱhfmb/í-Hǣf\Nİ gV(&cؿNIcS.%ϡ2( l" \V!K2،M‚5y-B QWďnၘP7V֭n79c-ɴ.PY;nKIIeJQtHBcנO?561I%[H0 ί@` ωrxR;9Kʦօ+d҂*7I:6O*u<ϥʕ!묒lxŷT" bgaqUc&T:2R|XdϬy׸6Ao!6&9\]"xnW> td7zd0˸ 9%R7&5 LPK6 iK;8J z61푫 D,<dRm좗b qi[a#x.q P~/>xxכ=u]KȖKhNtڔ^4dN.xE6k9p崰YV )fׄD;ڮwg]{w*ؒkNu棧ܲES7͙/lP:8yd;1A},}D xWvl]T.ZG|)nwDaұjm[P*_о,[ⰖyOLÊI ;Oֶ; ]ѷL8NPPAy3w^,UJj 1PMQdX.% g :m7h\(cH*ߓL4M$M啈.Zx(WbZ%_Q2`O"bgz}(IbRQfR"R\vK|]6QARJeTңSaU6mW{7r%V9ar(QqfhVHz׀k=@9^rvxKw ;b/&(8؊9ItD.XȊ3Z j=SՑlQUV,Hc< IA"I$:>sePFsĈ,=|w;"WOE3dN]ZE=7GRr L铻 QxLX,fmmO֙\J%N)$NK\\P][fxX8[OH#X:1C4% Wo AS]ahQ:6yN8y8xRؗqj!qY-+7pS:5$bD\pQed%E?VW5rCeΈK=Z!sLet<4MGtU?Cfux)6:|:_HOk&$g*xBZ刡{JjfLX'b"kfg(d#ZAY'vi&9(OuV!کLQF9)^w)tfK6uPj]ezw[ӧbg@[x3av{[{};DOCS/SERVER/vlwin.htm0000755000000000000000000001140111711606312011351 0ustar Join a Virtual LAN under Windows OS

Virtual LANs

The term VLAN (Virtual Local Area Network) refers to a collection of devices that communicate as if they were on the same physical LAN. Any set of ports (including all ports on the switch) can be considered a VLAN. LAN segments are not restricted by the hardware that physically connects them.

VLANs offer the ability to group computers together into logical workgroups. This can simplify network administration when connecting clients to servers that are geographically dispersed across the building, campus, or enterprise network.

Typically, VLANs consist of co-workers within the same department but in different locations, groups of users running the same network protocol, or a cross-functional team working on a joint project. 

 

By using VLANs on your network, you can:

  • Improve network performance

  • Limit broadcast storms

  • Improve LAN configuration updates (adds, moves, and changes)

  • Minimize security problems

  • Ease your management task

Other Considerations

  • To set up IEEE VLAN membership (multiple VLANs), the adapter must be attached to a switch with IEEE 802.1Q VLAN capability.

  • A maximum of 64 VLANs per network port or team are supported by Intel software.

  • VLANs can co-exist with teaming (if the adapter supports both). If you do this, the team must be defined first, then you can set up your VLAN.

  • The Intel PRO/100 VE and VM Desktop Adapters and Network Connections can be used in a switch based VLAN but do not support IEEE Tagging.

  • You can set up only one untagged VLAN per adapter or team. You must have at least one tagged VLAN before you can set up an untagged VLAN.

CAUTION: When using IEEE 802 VLANs, settings must match between the switch and those adapters using the VLANs.

Microsoft* Load Balancing and Failover (LBFO) teams

Intel ANS VLANs are not compatible with Microsoft's LBFO teams. Intel® PROSet will block a member of an LBFO team from being added to an Intel ANS VLAN. You should not add a port that is already part of an Intel ANS VLAN to an LBFO team, as this may cause system instability.

 

In Microsoft* Windows*, you must use Intel® PROSet to set up and configure VLANs. For more information, select Intel PROSet in the Table of Contents (left pane) of this window.

Note: If you change a setting under the Advanced tab for one VLAN, it changes the settings for all VLANS using that port.

In most environments, a maximum of 64 VLANs per network port or team are supported by Intel PROSet.

Configuration notes for Microsoft Hyper-V*

If you want to have VLANs on the parent partition and on any child partitions, each child partition's VLAN must have the same VLAN ID as a VLAN on the parent partition.

Last modified on 6/17/09 9:47p Revision

DOCS/SERVER/warranty.htm0000755000000000000000000001324011651733270012073 0ustar Limited Lifetime Hardware Warranty

Limited Lifetime Hardware Warranty

Intel warrants to the original owner that the adapter product delivered in this package will be free from defects in material and workmanship. This warranty does not cover the adapter product if it is damaged in the process of being installed or improperly used.

THE ABOVE WARRANTY IS IN LIEU OF ANY OTHER WARRANTY, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF NONINFRINGEMENT OF INTELLECTUAL PROPERTY, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE.

This warranty does not cover replacement of adapter products damaged by abuse, accident, misuse, neglect, alteration, repair, disaster, improper installation, or improper testing. If the adapter product is found to be defective, Intel, at its option, will replace or repair the hardware product at no charge except as set forth below, or refund your purchase price provided that you deliver the adapter product along with a Return Material Authorization (RMA) number (see below), along with proof of purchase (if not registered), either to the dealer from whom you purchased it or to Intel with an explanation of any deficiency. If you ship the adapter product, you must assume the risk of damage or loss in transit. You must use the original container (or the equivalent) and pay the shipping charge.

Intel may replace or repair the adapter product with either new or reconditioned parts, and any adapter product, or part thereof replaced by Intel becomes Intel's property. Repaired or replaced adapter products will be returned to you at the same revision level as received or higher, at Intel's option. Intel reserves the right to replace discontinued adapter products with an equivalent current generation adapter product.

Returning a defective product

From North America:

Before returning any adapter product, contact Intel Customer Support and obtain a Return Material Authorization (RMA) number by calling +1 916-377-7000.

If the Customer Support Group verifies that the adapter product is defective, they will have the RMA department issue you an RMA number to place on the outer package of the adapter product. Intel cannot accept any product without an RMA number on the package.

All other locations:

Return the adapter product to the place of purchase for a refund or replacement.

Intel Adapter Money-back Guarantee (North America Only)

Intel wants you to be completely satisfied with the Intel adapter product that you have purchased. Any time within ninety (90) days of purchase, you may return your Intel adapter to the original place of purchase for a full refund of the purchase price from your dealer. Resellers and distributors, respectively, accepting returns and refunding money back to their customers may return Intel adapters to their original place of purchase. Intel guarantees that it will accept returns under this policy and refund the original purchase price to customers purchasing directly from Intel.

Limitation of Liability and Remedies

INTEL'S SOLE LIABILITY HEREUNDER SHALL BE LIMITED TO DIRECT, OBJECTIVELY MEASURABLE DAMAGES. IN NO EVENT SHALL INTEL HAVE ANY LIABILITY FOR ANY INDIRECT OR SPECULATIVE DAMAGES (INCLUDING, WITHOUT LIMITING THE FOREGOING, CONSEQUENTIAL, INCIDENTAL, AND SPECIAL DAMAGES) INCLUDING, BUT NOT LIMITED TO, INFRINGEMENT OF INTELLECTUAL PROPERTY, REPROCUREMENT COSTS, LOSS OF USE, BUSINESS INTERRUPTIONS, LOSS OF GOODWILL, AND LOSS OF PROFITS, WHETHER ANY SUCH DAMAGES ARISE OUT OF CONTRACT NEGLIGENCE, TORT, OR UNDER ANY WARRANTY, IRRESPECTIVE OF WHETHER INTEL HAS ADVANCE NOTICE OF THE POSSIBILITY OF ANY SUCH DAMAGES. NOTWITHSTANDING THE FOREGOING, INTEL'S TOTAL LIABILITY FOR ALL CLAIMS UNDER THIS AGREEMENT SHALL NOT EXCEED THE PRICE PAID FOR THE PRODUCT. THESE LIMITATIONS ON POTENTIAL LIABILITIES WERE AN ESSENTIAL ELEMENT IN SETTING THE PRODUCT PRICE. INTEL NEITHER ASSUMES NOR AUTHORIZES ANYONE TO ASSUME FOR IT ANY OTHER LIABILITIES.

Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations may not apply to you.

Critical Control Applications: Intel specifically disclaims liability for use of the adapter product in critical control applications (including, for example only, safety or health care control systems, nuclear energy control systems, or air or ground traffic control systems) by Licensee or Sublicensees, and such use is entirely at the user's risk. Licensee agrees to defend, indemnify, and hold Intel harmless from and against any and all claims arising out of use of the adapter product in such applications by Licensee or Sublicensees.

Software: Software provided with the adapter product is not covered under the hardware warranty described above. See the applicable software license agreement which shipped with the adapter product for details on any software warranty.

Last modified on 7/23/02 10:42a Revision

DOCS/SERVER/wminicdm.htm0000755000000000000000000000763511656574604012057 0ustar WMI NIC Provider

Intel® Network Adapters WMI Provider

Overview

The Intel® Network Adapters Windows Management Instrumentation (WMI) Provider enables WMI-based management applications such as Intel® PROSet for Windows Device Manager to monitor and configure the status of PCI network adapters. Intel Network Adapters WMI Provider uses WMI, a user-level instrumentation technology for the Microsoft Windows* platform.

WMI is a middleware layer that allows measurement and instrumentation information to be collected from kernel mode data providers. This information can then be provided to local or remote user-mode data consumers through the use of a common set of interfaces (Web-based Enterprise Management called WBEM). WMI is a data-independent pipeline between the data consumer and the data provider that makes no assumptions about the format of the data.

A guide is available on this distribution, which contains detailed information on the Intel Network Adapters WMI Provider, also referred to as Network Configuration Services (NCS2) WMI Providers. This guide is located in \APPS\WMI\DOCS. The technical reference paper describes the external view of NCS2 WMI providers so WMI-based management applications could use it to manage the network configuration for the Intel adapters.

System Requirements

  • Any Intel® PRO/100, Intel® Gigabit Network Adapter, or Intel® 10GbE Network Adapter

  • related driver software

  • a supported Microsoft* Windows* operating system. Please refer to the System Requirements page for a list of supported operating systems.

The Intel Network Adapters WMI Provider supports all Intel PRO/100, Gigabit, and 10GbE network adapters.

Installation

The Intel Network Adapters WMI Provider are installed as part of Intel® PROSet for Windows Device Manager software installation. See the Installing Intel PROSet for Windows Device Manager section for more information on how to install Intel PROSet for Windows Device Manager.

Intel PROSet for Windows Device Manager Typical Setup Type registers the Intel Network Adapters WMI Provider into the root\IntelNCS2 namespace.

Supported Standards

The Intel Network Adapters WMI Provider supports the standards based CIM 2.6 specification.

Known Issues

DMI-SNMP Instrumentation

This Intel Network Adapters WMI Provider cannot jointly operate with the Intel® DMI-SNMP instrumentation.

Missing Instances under Microsoft Windows Vista*

You must elevate (i.e., embed a manifest file) in your application in order to access all of the Intel WMI classes.

Last modified on 6/05/09 11:26a Revision DOCS/WINDOWS0000755000000000000000000000000011761422164007553 5ustar DOCS/WINDOWS/caution.gif0000755000000000000000000000130411651733270011765 0ustar GIF89a)!19)!k91J9RZBRBJcRJB{fJcsZRRckJRfZJJ{{{{{s{{ksss{sJfffZZZRRRJJJJJ9BBB333)))!!!!,(,,00 -( 40 4(0 6($99 'A/ COO; 74 ͣB0  @7.C)!5.=ҏ# %"p8JB@1xJdbT`$cG(0c R`pP#B@̜=T`#IAT@!Nm; (QƄ:J05 (;98FCG fC >xA['!0!`> BH"F$D\N4yB$;DOCS/WINDOWS/drivers.htm0000755000000000000000000000613111710273344012024 0ustar Install the Drivers

Intel Network Drivers for Microsoft* Windows* Operating Systems

Install the Drivers in Microsoft Windows

NOTE: This will update the drivers for all supported Intel® network adapters in your system.

Before installing or updating the drivers, insert your adapter(s) in the computer and plug in the network cable. When Windows discovers the new adapter, it attempts to find an acceptable Windows driver already installed with the operating system. 

If found, the driver is installed without any user intervention. If Windows cannot find the driver, the Found New Hardware Wizard window is displayed.

Regardless of whether or not Windows finds the driver, it is recommended that you follow the procedure below to install the driver. Drivers for all Intel adapters supported by this software release are installed.

  1. If you are installing drivers from the Product CD, insert the CD. If you do not have the Product CD, download drivers from the support website and transfer them to the system.

  2. If the Found New Hardware Wizard screen is displayed, click Cancel.

  3. Start the autorun located on the CD. If you downloaded the software package from the support website, the autorun automatically runs after you have extracted the files.

  4. Click Install Drivers and Software.

  5. Follow the instructions in the install wizard.

Uninstalling the Driver

These instructions uninstall the drivers for all Intel network adapters in a system.

  1. From the Control Panel, double-click Add/Remove Programs. 

  2. Select Intel(R) Network Connections Drivers.

  3. Click Add/Remove. 

  4. When the confirmation dialog displays, click OK. 

Last modified on 6/05/09 11:38a Revision

DOCS/WINDOWS/dupwindm.htm0000755000000000000000000001103211656741062012177 0ustar Configuring Speed and Duplex in Windows*

Set Up Speed and Duplex

In the default mode, an Intel® Network Adapter using copper connections will attempt to auto-negotiate with its link partner to determine the best setting. If the adapter cannot establish link with the link partner using auto-negotiation, you may need to manually configure the adapter and link partner to identical settings to establish link and pass packets. This should only be needed when attempting to link with an older switch that does not support auto-negotiation or one that has been forced to a specific speed or duplex mode.

CAUTION: Only experienced network administrators should force speed and duplex manually. The settings at the switch must always match the adapter settings. Adapter performance may suffer or your adapter may not operate if you configure the adapter differently from your switch.

Your link partner must match the setting you choose.

Fiber-based adapters operate only in full duplex, and only at their native speed.

Configuring Speed and Duplex in Microsoft* Windows*

By default, auto-negotiation is enabled. Change this setting only to match your link partner.

  1. Navigate to the Device Manager.
  2. Open Properties on the adapter you would like to configure.
  3. Click the Link Speed tab.
  4. Select the appropriate speed and duplex from the Speed and Duplex pull down menu.
  5. Click OK.

Intel® Gigabit Network Adapter Considerations

Per the IEEE specification, gigabit speed is available only in full-duplex.

The settings available when auto-negotiation is disabled are:

  • 10 Mbps or 100 Mbps Full duplex (requires a full duplex capable link partner set to full duplex). The adapter can send and receive packets at the same time. You must set this mode manually.

  • 10 Mbps or 100 Mbps Half duplex (requires a link partner set to half duplex). The adapter performs one operation at a time; it either sends or receives. You must set this mode manually.

  • Auto-Negotiation 1000 Mbps. The adapter only advertises gigabit speed at full duplex.

Intel® 10 Gigabit Network Adapter Considerations

Intel® 10 Gigabit adapters that support 1 gigabit speed allow you to configure the Speed setting. If this option is not present, your adapter only runs at its native speed.

If the adapter cannot establish link with the gigabit link partner using auto-negotiation, set the adapter to 1 Gbps Full duplex.

Intel 10 gigabit fiber-based adapters and SFP direct-attach devices operate only in full duplex, and only at their native speed. Multi-speed 10 gigabit SFP+ fiber modules support full duplex at 10 Gbps and 1 Gbps.

Intel® PRO/100 Network Adapter Considerations

The settings available when auto-negotiation is disabled are:

  • 10 Mbps or 100 Mbps Full duplex (requires a full duplex capable link partner set to full duplex). The adapter can send and receive packets at the same time. You must set this mode manually.

  • 10 Mbps or 100 Mbps Half duplex (requires a link partner set to half duplex). The adapter performs one operation at a time; it either sends or receives. You must set this mode manually.

Last modified on 12/30/09 3:51p Revision DOCS/WINDOWS/hotwin.htm0000755000000000000000000000352311656574604011674 0ustar PCI Hot Plug Support for Microsoft Windows

PCI Hot Plug Support for Microsoft* Windows* Operating Systems

Intel® network adapters are enabled for use in selected servers equipped with PCI Hot Plug support and running Microsoft* Windows* operating systems. For more information on setting up and using PCI Hot Plug support in your server, see your hardware and/or Hot Plug support documentation for details. PCI Hot Plug only works when you hot plug an identical Intel network adapter.

 

NOTES:
  • The MAC address and driver from the removed adapter will be used by the replacement adapter unless you remove the adapter from the team and add it back in. If you do not remove and restore the replacement adapter from the team, and the original adapter is used elsewhere on your network, a MAC address conflict will occur.
  • For SLA teams, ensure that the replacement NIC is a member of the team before connecting it to the switch.

 

Last modified on 9/03/07 4:49p Revision

DOCS/WINDOWS/jumbo_dm.htm0000755000000000000000000001363011656574604012160 0ustar Jumbo Frames

Jumbo Frames

Jumbo frames are Ethernet frames that are larger than 1518 bytes. You can use Jumbo Frames to reduce server CPU utilization and increase throughput. However, additional latency may be introduced. 

NOTES:

  • Jumbo Frames are supported at 1000 Mbps and 10Gbps. Using Jumbo Frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.

  • End-to-end network hardware must support this capability; otherwise, packets will be dropped.

Jumbo Frames can be implemented simultaneously with VLANs and teaming.

To configure Jumbo Frames at the switch, consult your network administrator or switch user's guide.

Restrictions:

  • Jumbo frames are not supported in multi-vendor team configurations.

  • Supported protocols are limited to IP (TCP, UDP).

  • Jumbo frames require compatible switch connections that forward Jumbo Frames. Contact your switch vendor for more information.

  • When standard sized Ethernet frames (64 to 1518 bytes) are used, there is no benefit to configuring Jumbo Frames.

  • The Jumbo Frames setting on the switch must be set to at least 8 bytes larger than the adapter setting for Microsoft* Windows* operating systems, and at least 22 bytes larger for all other operating systems.

  • The Intel® PRO/1000 PL Network Connection supports jumbo frames in Microsoft* Windows* operating systems only when Intel® PROSet for Windows Device Manager is installed.

  • The following devices do not support jumbo frames larger than 4096 bytes:

    • Intel® 82577LM Gigabit Network Connection

    • Intel® 82578DM Gigabit Network Connection.

  • The following devices do not support jumbo frames:

    • Intel® 82567V-4 Gigabit Network Connection
    • Intel® 82578DC Gigabit Network Connection
    • Intel® 82577LC Gigabit Network Connection
    • Intel® 82567LF-3 Gigabit Network Connection
    • Intel® 82567V-2 Gigabit Network Connection
    • Intel® 82567LF-2 Gigabit Network Connection
    • Intel® 82567V Gigabit Network Connection
    • Intel® 82567LF Gigabit Network Connection
    • Intel® PRO/1000 Gigabit Server Adapter
    • Intel® PRO/1000 PM Network Connection
    • Intel® PRO/1000 PM Network Connection
    • Intel® 82562V 10/100 Network Connection
    • Intel® 82562GT 10/100 Network Connection
    • Intel® 82566DM Gigabit Network Connection
    • Intel® 82566DC Gigabit Network Connection
    • Intel® 82566DC-2 Gigabit Network Connection
    • Intel® 82562V-2 10/100 Gigabit Network Connection
    • Intel® 82562G-2 10/100 Gigabit Network Connection
    • Intel® 82562GT-2 10/100 Gigabit Network Connection
    • Intel® 82552 10/100 Network Connection

Setting Up Jumbo Frames in Microsoft* Windows*

NOTE: Jumbo frames are not supported in multi-vendor team configurations.

  1. Open Microsoft* Windows* Device Manager.

  2. Open Properties on your adapter.

  3. Click the Advanced tab.

  4. Select Jumbo Frames from the list of advanced features.

  5. Set your desired packet size (based on network capability).

  6. Click OK to apply the changes. 

All equipment on the network must also support the larger frame size. When setting up Jumbo Frames on other network devices, be aware that different network devices calculate Jumbo Frame size differently. Some devices include the header information in the frame size while others do not. Intel adapters do not include header information in the frame size. When configuring Jumbo Frames on a switch, set the frame size four bytes higher for CRC, plus four bytes if you are using VLANs or QoS packet tagging.

Last modified on 8/01/11 3:59p Revision

DOCS/WINDOWS/mang_win.htm0000755000000000000000000001754011734015456012157 0ustar Power Management

Power Management

The Intel® PROSet Power Management tab replaces the standard Microsoft* Windows* Power Management tab in Device Manager. It includes the Power Saver and Wake on LAN* (WoL*) options that were previously included on the Advanced tab. The standard Windows power management functionality is incorporated on the Intel PROSet tab.

NOTES:
  • The options available on the Power Management tab are adapter and system dependant. Not all adapters will display all options.
  • The following adapters support WoL only on Port A:
    • Intel® Ethernet Server Adapter I350-T2
    • Intel® Ethernet Server Adapter I350-T4
    • Intel® Ethernet Server Adapter I340-T2
    • Intel® Ethernet Server Adapter I340-T4
    • Intel® Ethernet Server Adapter I340-F4
    • Intel® Gigabit ET2 Quad Port Server Adapter
    • Intel® PRO/1000 PF Quad Port Server Adapter
    • Intel® PRO/1000 PT Quad Port LP Server Adapter
    • Intel® PRO/1000 PT Quad Port Server Adapter
    • Intel® PRO/1000 PT Dual Port Network Connection
    • Intel® PRO/1000 PT Dual Port Server Connection
    • Intel® PRO/1000 PT Dual Port Server Adapter
    • Intel® PRO/1000 PF Dual Port Server Adapter
    • Intel® Gigabit PT Quad Port Server ExpressModule
  • The following adapters do not support WoL:
    • Intel® PRO/1000 MT Quad Port Server adapter
    • Intel® Gigabit VT Quad Port Server Adapter
    • Intel® Ethernet Server Adapter X520-2
    • Intel® Ethernet Server Adapter X520-1
    • Intel® Ethernet Server Adapter X540-T1
    • Intel® Ethernet Converged Network Adapter X540-T2
    • Intel® Ethernet Converged Network Adapter X540-T1

NOTE: If your system has a Manageability Engine, the Link LED may stay lit even if WoL is disabled.

Power Options

The Intel PROSet Power Management tab includes several settings that control the adapter's power consumption. For example, you can set the adapter to reduce its power consumption if the cable is disconnected.

If Reduce speed during standby is enabled,  then Wake on Magic Packet and/or Wake on directed packet must be enabled. If both of these options are disabled, power is removed from the adapter during standby. Wake on Magic Packet from power off state has no effect on this option.

Energy Efficient Ethernet

The Energy Efficient Ethernet (EEE) feature allows a capable device to enter Low Power Idle between bursts of network traffic. Both ends of a link must have EEE enabled for any power to be saved. Both ends of the link will resume full power when data needs to be transmitted. This transition may introduce a small amount of network latency.

NOTES:

  • Both ends of the EEE link must automatically negotiate link speed.
  • EEE is not supported at 10Mbps.

 

Intel® Auto Connect Battery Saver

The Intel® Auto Connect Battery Saver (ACBS) feature turns off the adapter when link is down or the network cable is disconnected. After a timeout period, the adapter will power off. When the network cable is reconnected and link is restored, the NIC powers up and functionality is fully restored.

ACBS only functions when the system is on battery power. If the power cable is connected, ACBS will be automatically disabled. If ACBS is active, the adapter will appear to be powered off. If you have Intel® PROSet installed, on the Link Speed tab, the Link Status will indicate Speed: Not connected. Power off.

NOTE: ACBS will not function on an adapter if the adapter has forced speed or duplex settings. ACBS will only function if the adapter is set to auto-detect or auto-negotiate.

Intel® System Idle Power Saver

The Intel® System Idle Power Saver feature sets the adapter to negotiate the lowest possible speed setting when the system and network are idle. When the system activity is detected, the link will be negotiated to a higher speed.

To support this feature, the adapter must be

  • configured to Auto Detect speed and
  • connected to a link partner that can auto-negotiate speed

Remote Wake-Up and Wake on LAN*

The ability to remotely wake computers is an important development in computer management. This feature has evolved over the last few years from a simple remote power-on capability to a complex system interacting with a variety of device and operating system power states. More details are available here.

Microsoft Windows XP, Windows Vista*, Windows 7, Windows Server* 2003, Windows Server 2008, and Windows Server 2008 R2 are ACPI-capable. These operating systems do not support wake from a power-off (S5) state, only from standby (S3) or hibernate (S4). When shutting down the system, they shutdown ACPI devices, including Intel adapters. This disarms the adapters remote wake up capability. However, in some ACPI-capable computers, the BIOS may have a setting that allows you to override the operating system and wake from an S5 state anyway. If there is no support for wake from S5 state in your BIOS settings, you are limited to Wake From Standby when using these operating systems in ACPI computers.

For some adapters, the Power Management tab in Intel PROSet includes a setting called Wake on Magic Packet from power off state. Enable this setting to explicitly allow wake up with a Magic Packet* from shutdown under APM power management mode.

In ACPI-capable versions of Windows, the Intel PROSet Power Management tab includes Wake on Magic Packet and Wake on directed packet settings. These controls the type of packets that wake up the system from standby.

Wake on Intel® Ready Access

Intel® Ready Access keeps your network connection active when the rest of your system is in sleep or standby mode, so that content on your system is readily accessible. Requests from other computers will wake up your computer.

Last modified on 7/12/11 11:49p Revision

DOCS/WINDOWS/note.gif0000755000000000000000000000073211651733270011274 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;DOCS/WINDOWS/prosetdm.htm0000755000000000000000000000472411714034554012213 0ustar Using PROSet

Intel® PROSet for Windows* Device Manager

Intel® PROSet for Windows* Device Manager is an extension to the Windows Device Manager. When you install the Intel PROSet software, additional tabs are automatically added to Device Manager.

NOTE:  You must have administrator rights to install or use Intel PROSet for Windows Device Manager.

Installing Intel PROSet for Windows Device Manager

Intel PROSet for Windows Device Manager is installed from the Product CD with the same process used to install drivers. You can select Intel PROSet for Windows Device Manager and Advanced Network Services from the Install Options dialog.

Removing Intel PROSet for Windows Device Manager

Use Add/Remove programs from the Control Panel to uninstall Intel PROSet for Windows Device Manager.

Changing Intel PROSet Settings Under Windows Server Core

You can use the command line utility prosetcl.exe to change most Intel PROSet settings under Windows Server Core. Please refer to the help file prosetcl.txt located in the \Program Files\Intel\DMIX\CL directory. For iSCSI Crash Dump cofiguration, use the CrashDmp.exe utility and refer to the CrashDmp.txt help file.

Compatibility Notes

The following devices do not support Intel PROSet for Windows Device Manager

  • Intel® 82552 10/100 Network Connection
  • Intel® 82567V-3 Gigabit Network Connection

Last modified on 8/04/10 8:12p Revision DOCS/WINDOWS/pushinst.htm0000755000000000000000000000354711735070116012232 0ustar Microsoft* Windows* Push Install Instructions

Microsoft* Windows* Push Install Instructions

A "Push," or unattended, installation provides a means for network administrators to easily install the drivers on systems that have similar equipment. The following document provides instructions for a basic unattended installation of Microsoft* Windows* that includes the installation of drivers for Intel® Network Adapters.

For 32-bit Microsoft Windows operating systems, see the Push32.txt file in the Apps\Setup\Push\Win32 directory on the Product CD or in the download directory. This file applies to the following operating systems:

  • Microsoft Windows* 7
  • Microsoft Windows Vista*
  • Microsoft Windows* XP
  • Microsoft Windows Server* 2008
  • Microsoft Windows Server* 2003

 

For x64 Microsoft Windows operating systems, see the Pushx64.txt file in the APPS\SETUP\PUSH\WINX64 directory on the Product CD or in the download directory. This file applies to the following operating systems:

  • Microsoft Windows Server* 2008 R2
  • Microsoft Windows Server* 2008 x64
  • Microsoft Windows* 7 x64
  • Microsoft Windows Vista* x64
  • Microsoft Windows* XP x64
  • Microsoft Windows Server* 2003 x64

Last modified on 2/22/10 4:47p Revision

DOCS/WINDOWS/qos.htm0000755000000000000000000000422711735070116011153 0ustar Quality of Service (QoS)

Quality of Service

Quality of Service (QoS) allows the adapter to send and receive IEEE 802.3ac tagged frames. 802.3ac tagged frames include 802.1p priority-tagged frames and 802.1Q VLAN-tagged frames. In order to implement QoS, the adapter must be connected to a switch that supports and is configured for QoS. Priority-tagged frames allow programs that deal with real-time events to make the most efficient use of network bandwidth. High priority packets are processed before lower priority packets.

Under Windows XP and Windows Server 2003, tagging is enabled and disabled using the "QoS Packet Tagging" setting in the Advanced tab in Intel® PROSet. Under Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2, tagging is enabled using the "Priority/VLAN Tagging" setting on the Advanced tab.

Once QoS is enabled in Intel PROSet, you can specify levels of priority based on IEEE 802.1p/802.1Q frame tagging.

The supported operating systems have a utility for 802.1p packet prioritization. For more information, see the Windows system help and Microsoft's knowledge base.

NOTE: The first generation Intel® PRO/1000 Gigabit Server Adapter (PWLA 8490) does not support QoS frame tagging.

 

Last modified on 4/22/09 10:46p Revision

DOCS/WINDOWS/save_dm.htm0000755000000000000000000000712211656574604012001 0ustar Save and Restore

Saving and Restoring an Adapter's Configuration Settings

The Save and Restore Command Line Tool is a VBScript (SavResDX.vbs) that allows you to copy the current adapter and team settings into a standalone file (such as on a floppy disk) as a backup measure. In the event of a hard drive failure, you can reinstate most of your former settings.

The system on which you restore network configuration settings must have the same configuration as the one on which the save was performed.

NOTES:
  • You must have Administration privileges to run scripts. If you do not have Administration privileges, you will not receive an error, the script just will not run.
  • Only adapter settings are saved (these include ANS teaming and VLANs). The adapter's driver is not saved.
  • Restore using the script only once. Restoring multiple times may result in unstable configuration.
  • The Restore operation requires the same OS as when the configuration was Saved.

Command Line Syntax

cscript SavResDX.vbs save|restore [filename]

SavResDX.vbs has the following command line options:

save Saves adapter and team settings that have been changed from the default settings.  When you restore with the resulting file, any settings not contained in the file are assumed to be the default.
restore Restores the settings.
filename The file to save settings to or restore settings from.  If no filename is specified, the script default to WmiConf.txt.

Examples

Save Example

To save the adapter settings to a file on a floppy diskette, do the following.

  1. Open a Windows Command Prompt.
  2. Navigate to the directory where SavResDX.vbs is located (generally c:\Program Files\Intel\DMIX).
  3. Type the following:

    4. cscript SavResDX.vbs save a:\settings.txt

Restore Example

To restore the adapter settings from a file on a floppy diskette, do the following:

  1. Open a Windows Command Prompt.
  2. Navigate to the directory where SavResDX.vbs is located (generally c:\Program Files\Intel\DMIX).
  3. Type the following:

    4. cscript SavResDX.vbs restore a:\settings.txt

Last modified on 2/10/10 3:18p Revision

DOCS/WINDOWS/snmpwin.htm0000755000000000000000000000441211656574604012055 0ustar Simple Network Management Protocol (SNMP)

Simple Network Management Protocol

The Simple Network Management Protocol (SNMP) is a network protocol used to manage TCP/IP networks. SNMP-compliant devices (agents) communicate with management applications (consoles) to send alerts and updates and allow configuration changes.

The Intel® SNMP Agent translates event notices from the adapter and sends them to specified SNMP management stations. The SNMP agent provides information on Intel® network adapters as well as information about advanced features, such as teaming and VLANs.

Using the Intel SNMP Agent

  • Before you install the Intel SNMP Agent on a computer, you must install SNMP on the computer. See your operating system documentation for more information.

  • To use the Intel SNMP Agent with an SNMP management application, you must first compile the Intel MIB (Management Information Base) into the management application's database. This allows the management application to recognize and support the adapter.

Installing the SNMP Agent on Microsoft* Windows* Operating Systems

This utility should only be employed by experienced network administrators. Additional software/services must be installed on your network prior to installing the Intel® SNMP Agent.

To install the SNMP Agent, start the autorun menu from the Product CD or download directory and click Install Drivers and Software. Follow the instructions on the screen.

Last modified on 9/03/07 4:49p Revision

DOCS/WINDOWS/style.css0000755000000000000000000000450511651733270011514 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } DOCS/WINDOWS/support.gif0000755000000000000000000003157611651733270012055 0ustar GIF89a]h!"9)$9J,Z B R)j)R% X& e)(s!4k#2x1 k1&X1JMwuC6~9;f37j.\8%׶}$).fdӫ_m: ҅qըqaI[1ĖlpG uQW!Qd9ކvEt #81TL37Hae1`)(IroP"YBT!υT"qI}(TVOiH"3McΙᆋ¶]2833h&cv!b r$1%<3 $nxY'eqFRZ)餔VF<3Hc9|ƘllLؗ1fl3_v9z>L*c1KBxdi6lP.Ęrnaa9}y+T0b .z91IvgGU C!zJK4H"ta / w4RSx8-(Q98 3Ċ;>#hAe0H8#nA 7 .;#OH>[ҸUDBHUa-?%Agdx HJ T-pxcG#(#Aژ"btАQ]]E IH"8$@3džhLh!;Z<A01pƸx 㨑8UI˼Qxm(1 2 R&7)ǒ@Wb&H\!"yxȥ8!orH-,8 '$"X21zEcb$ -9F[Ӝ,dQ =z扅z^WpB 8Els IN3lB*:TF5a?BbG;T?@A ^TJqkt#P:uh!p!2|wѻ eHMOAO8(6a5zB`!` +)́l HH9z (3"01Jͫ^iFBK5!AT3ƍi@ʉdyq9Y`C+H8e{MjibH8Wqts Ad@("C;p+QqF `_p`` ؀ؐȉِ Jv/(ِ2P܀[8 TDE7yq P Ҩ `bu0vxqp % e |73Yxhȉ(+h  yѐ 2   ^]0}!-HLX @ bi0] `m@}FP#V `0&g (v0q\gs  p! e +A6p1\@ȏ P*9  *` *p **\) 0%لM8 Q:P[PHG R$PGP yPfsv^h'~XuG} 1H Op.-=0 ` p؉ Xz`  򀙹\KnlQ$Ii0xw E<@lp@ 0l09I8 xS&v(@qōۘi)DEpV $ gj` ЏzI_vZ  yTw+׈ x;50Awb Ds mPXx'&ʁF\˵qyv5GUGEBV'WtEpIi0'ŰxYmڦP}YsJuJ}^ K(Jp`p7fC7 P iBH^jJ&ʆ`*W` `Y|H QZ/fphpӯ PP gq1p *Jvtژ i]!]0iMyIr,°BFɑѭW[9 Y\Kf9 T@Q |{-隡p1:@'ߡC~1^Ph5i&=ڰ ԉ.q* P `@g_ eлfr`qq@p#[/o46{*iK0!YHp D盾]*J! L @Z++^k]wZ) < )`o; ,+jI*'p9pbp% l020po` p^P[&ć uXK!Q|C @Tt _g9|kAX̠&V)Ipʂ|aL`pk+AHQ2K㰿 Ȍȑ! 09;P  L+PH|Ѱ ]Q*P2p3 2I0PgpdEQL,$li|ibƅ:|_л[ Ǜ 0j Q؄oJ)xz,PzpȐ2aɊʈl7`ɞi;p{** Cl-\,؛ -m <iȘ]r,$ғ^@Ƭ̺b.Ps0ZhE9 i}Pt& K, <[  1 GQ9RS epq\okk*+q ݊NHа9lVIK M ҋEʩ} \{|ÜQL1MV0TKL!9];Gƭ2ZJLJR}+΀m5:aE Ac1 0 0 %N(paPP9\gz H_ wglўfjh,ċ݊IΩKɽ-9$i:] Y={l4^( ˾'"WXa5>ioj0#A kD$^bTp  \9(\\46m wvؤ Yg2_Puջg0'rp;dm' mℙꙹٳ O]3a+K`f&ik,:NjʎZN|0j)IpZ2m" t$ sP}҂0 zV>R3~r0 :wǻo`rot tl"WŚМ] ۮ"L4Na*  )hG4HOG/d;̠i2@Jx?Uk-7vI(tķAp8ˆ[)y_tr(%{T f,xȁ!CbF +"W;q}|-p}1HhJ1V]nP2\`nBcK31BU \*qRЁXA,A Јxp׻?ftWD')91kht2!ǘ2V-pp3!B1A2F dpMr/a XplcŔ ipE8,ssc(bÆ[ސ'!Wh%CcgZ7 3$(X3x̸41|׼0}p4!pӸ| cgx,@`l|c[; FQxiKo$pɸ? {ZzmuHޅS4_^4':!FE.<O7Ip9:\5)V@׮j4| d  #U<;%S3܀5Qp 73uG3#HM>LSo=^W`z5w{ hO1!C}Dp tXȺ [> 䳇哇OS tzx (=; zXp rC;B 7s`2g`6hM9),zch%@# a r xhyv6> =L  @cx'O+I$ 1c"t@A8pp M893bz/tM9]tT18; );Jkės8hVxh ck?p?50 E, 3?+%MgHx9/?8512 gZHЅJ49-Xm<R=RUxՅMIeԑnX7&$I KRTsHpWY=SuR؇T^V%<̺Ľ % ЙP>Xo4nxӱy K{>eU&jmhy+L6@L!-""X3!@ȧ}9@6`1hE-!rӱ#X- AN]T&?}XxHA -1J\ H\NAsG},թ\{\C }=Y\ܣ٨Ľ- pBwQR JsK+їr)^H7-!E̲[q!W|[+"83CXChOש}^b=!85\ \Mm\:j܅A)TlCӗ``a%#QXٟ]NXYTF`~tU0EUPϜE8Yħm^9^%VJF گ="%[M[%*^"8!ai:?7 7,}X_:Sԭ:mؑITxܘXO=T TVm\څ,X1:G7T]ʥa%G&T Ƈ B|Ty&dZ|b͈EK- RU!+cI`Cޱ+,k56o5HȋB5(x/˂/}:@X3t,c=~vYGgo\`@d}4:(:ۅ%Go}w]U:uȈPf`$LhQH0ɬsIiLIEϖi"蟞Bc%;!>yvcbyNjfzDg]xF/ #l^b-Ɓ 6X9]H*ȁG.C5"f7,M} 癨p:bޤĆ#$M*t xl] <p8{`Nlfj ATClˉav^,x04iHfjv%W-pXBq.O)32xcEFljj m#򮐛"X˦my,=fՌCގM;V~@bf? H.6i1-yx@ތ=mq&)8nӡ"vw0555KVfh.pRqk ߴ 610 Ca('H4#H4K÷r/O>1䕾Z" s%SQ3&ssqCЍ&`.I =M6)q7I/tLDF^f^FJc=8QSg%[G#AdiWcJkM?vd>V!f^n2bfw0Tߟ˔hn]dt*\\vISDMvye!N8뱺-(7Eb`'xWxbHׅC-pE @`#B+dy@^óSzy/AFV7x->35 G??. ЀH+}dryz,yJym!p&5Wj]8>upB8zݔ4fgZz{zE,"b~3rs9?cxf̲?{ȟF5x3$8J̸{?pz,v[goqvT/@{/yHI(5`Uͤw6v~W,_'| >1t^Ǐ;F9AxJxIc45 Y,h „ 2l!Ĉ'RH^={7jc= a$Ɣ3ڋ'0u=4(1E*ib)l\ =ŬZ꒰K.ZQEjײm-ܸrureǒOQ]ѣČÆMlhC&ĦJ {ңIXͥ"aٱ M6ܺw[};I)%x2@>$ǐ!7(MpUXӂuCӯo>~=N2U 7.8=ƆQ4\$ ZJV<0 L,"@]4NSV'.E4 HtAxD#œKKYŕWx->fbXR@"'(j\ Yc"fl}oJ5qQ<2ua]CC(p)\p#`*).D H^AѨM=`1c4("Lϐ90K,K*cd80qriK A-Z{c*2Pr^sjf{/guJ,bD/@FD1DFxZ0sN` K8*vmKU}6ib?b$4]>L 0@ZK9oPrl3t|j1ߵԬԉ|]"@<'Fd2ġCu#hu(zuCcU4*"Nc(:NٌX {8EHfBǕ(څLlGRt&ArN 6L}*T*թRV*Vխr^*X*ֱf=+X/qMLuЄTrQ Vjj_:Vj]JվO(d#+Y)qI,[TrOeٵ-jSڸL)!.Z;DOCS/WINDOWS/support.htm0000755000000000000000000000206611651733270012070 0ustar Intel Customer Support

Customer Support

Intel support is available on the web or by phone. Support offers the most up-to-date information about Intel products, including installation instructions, troubleshooting tips, and general product information.

Web and Internet Sites

Support: http://www.intel.com/support

Corporate Site for Network Products: http://www.intel.com/products/ethernet/overview.htm

 

Last modified on 5/12/10 3:26p Revision

DOCS/WINDOWS/vlan.gif0000755000000000000000000001066311656574604011304 0ustar GIF89a*?*?*_*_U*_*_**U****U****U****U*ߪ***U**UUUUUUUUUUU?U?UU?U?U_U_UU_U_UUUUUUUUUUUUUUUUUUUߪUUUUUUUU??U??__U__UUUUߪUUU??U??__U__UUUUߪUUU??U??__U__UԟԟUԟԟԿԿUԿԿUߪUUU??U??__U__UUUUߪU3fUUUUߪU**U****U***?*?U𠠤, H*\ȰÇ#JHŋ3jȱǏ CIѐ3raʕZL!6q@C0=J`O$*]^Z %(^ V/kU,ٰP|ziE)@ 1Ĵ߿ hd jqW1 hbƐ% `\ 8XӅO &#i^˞M`TWDVpdg|[\bAZ ]:"Wl]N6_}5bKOy]^}6ހ_!Uyu ]IulE(H$`yTW1 &y=҃NaS Ձ r+$7cH`0 S|)fe-$W#m _Qs pUyB$h浟Ox+"˦2~_^ۖ "<0ho `é{kllNgJ2CJFQfPa )UxO\ʰa t%:d]`0S֭d]HxD @]ԡM¯'4ROu5لA >dp(6PɵBAt6Ʈm k6Xgh{ᵭ!GWf^gu^ieWYN,暧˂}ItIؠ͞lrמ6Jm'|r><$WogO:Ο }R/r/ /#o_|s_'0TKwv # Ab@*C`>Mp# 23%A"-ta(C pG50?Pȑ~s`> 0Lh(ZPQDaEOըOрod#58C8)>2gxHB DT&$C:R##Iɿ<$%LyS 8kq_d񢧔E-rW@y'U2I1^N+@ /i%L@e%B+Kd.Eiiq{ .vhc g.EI%Xh\^ЩNA4Ж@h+\sx"sZCRxG lq<%jXeD%QH8W:ֱYJG?{.Q>HZѩCЇ$C>Q&cai]F^JT:ҡD\fy*ŸMMMm,Y~zQi4?jXֱhfmb/í-Hǣf\Nİ gV(&cؿNIcS.%ϡ2( l" \V!K2،M‚5y-B QWďnၘP7V֭n79c-ɴ.PY;nKIIeJQtHBcנO?561I%[H0 ί@` ωrxR;9Kʦօ+d҂*7I:6O*u<ϥʕ!묒lxŷT" bgaqUc&T:2R|XdϬy׸6Ao!6&9\]"xnW> td7zd0˸ 9%R7&5 LPK6 iK;8J z61푫 D,<dRm좗b qi[a#x.q P~/>xxכ=u]KȖKhNtڔ^4dN.xE6k9p崰YV )fׄD;ڮwg]{w*ؒkNu棧ܲES7͙/lP:8yd;1A},}D xWvl]T.ZG|)nwDaұjm[P*_о,[ⰖyOLÊI ;Oֶ; ]ѷL8NPPAy3w^,UJj 1PMQdX.% g :m7h\(cH*ߓL4M$M啈.Zx(WbZ%_Q2`O"bgz}(IbRQfR"R\vK|]6QARJeTңSaU6mW{7r%V9ar(QqfhVHz׀k=@9^rvxKw ;b/&(8؊9ItD.XȊ3Z j=SՑlQUV,Hc< IA"I$:>sePFsĈ,=|w;"WOE3dN]ZE=7GRr L铻 QxLX,fmmO֙\J%N)$NK\\P][fxX8[OH#X:1C4% Wo AS]ahQ:6yN8y8xRؗqj!qY-+7pS:5$bD\pQed%E?VW5rCeΈK=Z!sLet<4MGtU?Cfux)6:|:_HOk&$g*xBZ刡{JjfLX'b"kfg(d#ZAY'vi&9(OuV!کLQF9)^w)tfK6uPj]ezw[ӧbg@[x3av{[{};DOCS/WINDOWS/vlwin.htm0000755000000000000000000001140111711606312011475 0ustar Join a Virtual LAN under Windows OS

Virtual LANs

The term VLAN (Virtual Local Area Network) refers to a collection of devices that communicate as if they were on the same physical LAN. Any set of ports (including all ports on the switch) can be considered a VLAN. LAN segments are not restricted by the hardware that physically connects them.

VLANs offer the ability to group computers together into logical workgroups. This can simplify network administration when connecting clients to servers that are geographically dispersed across the building, campus, or enterprise network.

Typically, VLANs consist of co-workers within the same department but in different locations, groups of users running the same network protocol, or a cross-functional team working on a joint project. 

 

By using VLANs on your network, you can:

  • Improve network performance

  • Limit broadcast storms

  • Improve LAN configuration updates (adds, moves, and changes)

  • Minimize security problems

  • Ease your management task

Other Considerations

  • To set up IEEE VLAN membership (multiple VLANs), the adapter must be attached to a switch with IEEE 802.1Q VLAN capability.

  • A maximum of 64 VLANs per network port or team are supported by Intel software.

  • VLANs can co-exist with teaming (if the adapter supports both). If you do this, the team must be defined first, then you can set up your VLAN.

  • The Intel PRO/100 VE and VM Desktop Adapters and Network Connections can be used in a switch based VLAN but do not support IEEE Tagging.

  • You can set up only one untagged VLAN per adapter or team. You must have at least one tagged VLAN before you can set up an untagged VLAN.

CAUTION: When using IEEE 802 VLANs, settings must match between the switch and those adapters using the VLANs.

Microsoft* Load Balancing and Failover (LBFO) teams

Intel ANS VLANs are not compatible with Microsoft's LBFO teams. Intel® PROSet will block a member of an LBFO team from being added to an Intel ANS VLAN. You should not add a port that is already part of an Intel ANS VLAN to an LBFO team, as this may cause system instability.

 

Configuring VLANs in Microsoft* Windows*

In Microsoft* Windows*, you must use Intel® PROSet to set up and configure VLANs. For more information, select Intel PROSet in the Table of Contents (left pane) of this window.

Note: If you change a setting under the Advanced tab for one VLAN, it changes the settings for all VLANS using that port.

In most environments, a maximum of 64 VLANs per network port or team are supported by Intel PROSet.

Configuration notes for Microsoft Hyper-V*

If you want to have VLANs on the parent partition and on any child partitions, each child partition's VLAN must have the same VLAN ID as a VLAN on the parent partition.

Last modified on 6/17/09 9:47p Revision

DOCS/WINDOWS/warranty.htm0000755000000000000000000001324011651733270012217 0ustar Limited Lifetime Hardware Warranty

Limited Lifetime Hardware Warranty

Intel warrants to the original owner that the adapter product delivered in this package will be free from defects in material and workmanship. This warranty does not cover the adapter product if it is damaged in the process of being installed or improperly used.

THE ABOVE WARRANTY IS IN LIEU OF ANY OTHER WARRANTY, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF NONINFRINGEMENT OF INTELLECTUAL PROPERTY, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE.

This warranty does not cover replacement of adapter products damaged by abuse, accident, misuse, neglect, alteration, repair, disaster, improper installation, or improper testing. If the adapter product is found to be defective, Intel, at its option, will replace or repair the hardware product at no charge except as set forth below, or refund your purchase price provided that you deliver the adapter product along with a Return Material Authorization (RMA) number (see below), along with proof of purchase (if not registered), either to the dealer from whom you purchased it or to Intel with an explanation of any deficiency. If you ship the adapter product, you must assume the risk of damage or loss in transit. You must use the original container (or the equivalent) and pay the shipping charge.

Intel may replace or repair the adapter product with either new or reconditioned parts, and any adapter product, or part thereof replaced by Intel becomes Intel's property. Repaired or replaced adapter products will be returned to you at the same revision level as received or higher, at Intel's option. Intel reserves the right to replace discontinued adapter products with an equivalent current generation adapter product.

Returning a defective product

From North America:

Before returning any adapter product, contact Intel Customer Support and obtain a Return Material Authorization (RMA) number by calling +1 916-377-7000.

If the Customer Support Group verifies that the adapter product is defective, they will have the RMA department issue you an RMA number to place on the outer package of the adapter product. Intel cannot accept any product without an RMA number on the package.

All other locations:

Return the adapter product to the place of purchase for a refund or replacement.

Intel Adapter Money-back Guarantee (North America Only)

Intel wants you to be completely satisfied with the Intel adapter product that you have purchased. Any time within ninety (90) days of purchase, you may return your Intel adapter to the original place of purchase for a full refund of the purchase price from your dealer. Resellers and distributors, respectively, accepting returns and refunding money back to their customers may return Intel adapters to their original place of purchase. Intel guarantees that it will accept returns under this policy and refund the original purchase price to customers purchasing directly from Intel.

Limitation of Liability and Remedies

INTEL'S SOLE LIABILITY HEREUNDER SHALL BE LIMITED TO DIRECT, OBJECTIVELY MEASURABLE DAMAGES. IN NO EVENT SHALL INTEL HAVE ANY LIABILITY FOR ANY INDIRECT OR SPECULATIVE DAMAGES (INCLUDING, WITHOUT LIMITING THE FOREGOING, CONSEQUENTIAL, INCIDENTAL, AND SPECIAL DAMAGES) INCLUDING, BUT NOT LIMITED TO, INFRINGEMENT OF INTELLECTUAL PROPERTY, REPROCUREMENT COSTS, LOSS OF USE, BUSINESS INTERRUPTIONS, LOSS OF GOODWILL, AND LOSS OF PROFITS, WHETHER ANY SUCH DAMAGES ARISE OUT OF CONTRACT NEGLIGENCE, TORT, OR UNDER ANY WARRANTY, IRRESPECTIVE OF WHETHER INTEL HAS ADVANCE NOTICE OF THE POSSIBILITY OF ANY SUCH DAMAGES. NOTWITHSTANDING THE FOREGOING, INTEL'S TOTAL LIABILITY FOR ALL CLAIMS UNDER THIS AGREEMENT SHALL NOT EXCEED THE PRICE PAID FOR THE PRODUCT. THESE LIMITATIONS ON POTENTIAL LIABILITIES WERE AN ESSENTIAL ELEMENT IN SETTING THE PRODUCT PRICE. INTEL NEITHER ASSUMES NOR AUTHORIZES ANYONE TO ASSUME FOR IT ANY OTHER LIABILITIES.

Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations may not apply to you.

Critical Control Applications: Intel specifically disclaims liability for use of the adapter product in critical control applications (including, for example only, safety or health care control systems, nuclear energy control systems, or air or ground traffic control systems) by Licensee or Sublicensees, and such use is entirely at the user's risk. Licensee agrees to defend, indemnify, and hold Intel harmless from and against any and all claims arising out of use of the adapter product in such applications by Licensee or Sublicensees.

Software: Software provided with the adapter product is not covered under the hardware warranty described above. See the applicable software license agreement which shipped with the adapter product for details on any software warranty.

Last modified on 7/23/02 10:42a Revision

DOCS/WINDOWS/wminicdm.htm0000755000000000000000000000763511656574604012203 0ustar WMI NIC Provider

Intel® Network Adapters WMI Provider

Overview

The Intel® Network Adapters Windows Management Instrumentation (WMI) Provider enables WMI-based management applications such as Intel® PROSet for Windows Device Manager to monitor and configure the status of PCI network adapters. Intel Network Adapters WMI Provider uses WMI, a user-level instrumentation technology for the Microsoft Windows* platform.

WMI is a middleware layer that allows measurement and instrumentation information to be collected from kernel mode data providers. This information can then be provided to local or remote user-mode data consumers through the use of a common set of interfaces (Web-based Enterprise Management called WBEM). WMI is a data-independent pipeline between the data consumer and the data provider that makes no assumptions about the format of the data.

A guide is available on this distribution, which contains detailed information on the Intel Network Adapters WMI Provider, also referred to as Network Configuration Services (NCS2) WMI Providers. This guide is located in \APPS\WMI\DOCS. The technical reference paper describes the external view of NCS2 WMI providers so WMI-based management applications could use it to manage the network configuration for the Intel adapters.

System Requirements

  • Any Intel® PRO/100, Intel® Gigabit Network Adapter, or Intel® 10GbE Network Adapter

  • related driver software

  • a supported Microsoft* Windows* operating system. Please refer to the System Requirements page for a list of supported operating systems.

The Intel Network Adapters WMI Provider supports all Intel PRO/100, Gigabit, and 10GbE network adapters.

Installation

The Intel Network Adapters WMI Provider are installed as part of Intel® PROSet for Windows Device Manager software installation. See the Installing Intel PROSet for Windows Device Manager section for more information on how to install Intel PROSet for Windows Device Manager.

Intel PROSet for Windows Device Manager Typical Setup Type registers the Intel Network Adapters WMI Provider into the root\IntelNCS2 namespace.

Supported Standards

The Intel Network Adapters WMI Provider supports the standards based CIM 2.6 specification.

Known Issues

DMI-SNMP Instrumentation

This Intel Network Adapters WMI Provider cannot jointly operate with the Intel® DMI-SNMP instrumentation.

Missing Instances under Microsoft Windows Vista*

You must elevate (i.e., embed a manifest file) in your application in order to access all of the Intel WMI classes.

Last modified on 6/05/09 11:26a Revision

Configuring VLANs in Microsoft* Windows*