DESKTOP/1000pt1p.gif0000755000000000000000000000511611656741062010747 0ustar GIF89a{_\]2./EBDzxyokmhfhPLN~{|⭭?<=efi"rqs'#%!,{dihz~lp,tmޭ[/HH^h\:&t&Zի+R2.x#f/N_nwA yns~f}i d fcimHq`qZq?u;V0-aS/2gP.«N-ҥ13,-1e{ϙt@Kx$j"}01=]mÒq"IX"݈ek: Ӧsg6o%|1)Q:$R|vTxu^$uZJfPa6*Zk˦ VI\vsmzY^JSݚm[{]yh{\^YcȲ>7v[%NN:5Zʜ,/+ )0|lЉvDN-<]j', T ?_\Le~ b ~-&{8Мt(GCߩ,~؝^xНu 5䆢a̧*\!3/c@sycfpJRB2de rkGTY E<9ۇ&&ige#`f!m21&08Hx€Joxr 6/YNh!>G}Ffbz)r)ix:*mzjlh*#@&`£,7ѕ2_x`H @0+$9X 찞ftKX @&'FyglFt,QXچc!1 ' 7p)@8l SqT|{h o),DP{D" ·M krQ ,Lk 34[j @AC<54J@Z* N/`x QF@b#Mva  w? ף {a!O┽Ttr7@o \ӷ]֊@86JϭǗ_||,D .Og63dC э|+\<(&2,pVE+&*f7zyNTHv+fbcmbscxqu$&c!H)r UEJ#$wI>1ad'90)?yJQ6reE@FU~$=ȃ$`;w,f17Laӆ( 1@ъ2 Hj,D@NbH۔:iNt]k1>gcl\й ,:*M~pEg9jHHGJҒr'P@ ^'WRnIf;LT10 | TU*ײm mC jZm9%Y92~@ gнm o,૷Ѿjv*&#zQbwA˗5Glbh<=~Tv !y!@D~2\nvQ;DESKTOP/45double.gif0000755000000000000000000001647311656741062011215 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;DESKTOP/KCCA.gif0000755000000000000000000007240511656741516010274 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:<_;DESKTOP/ad_1gd.htm0000755000000000000000000002675411735067552010742 0ustar Supported Adapters - Desktop Gigabit

Supported Intel® Gigabit Desktop Adapters

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

Product Name Board ID #† Controller
Intel® Gigabit CT2 Desktop Adapter E98157-xxx 82574L
Intel® 82579LM Gigabit Network Connection n/a 82579LM
Intel® 82579V Gigabit Network Connection n/a 82579V
Intel® 82578DM Gigabit Network Connection n/a 82578DM
Intel® 82578DC Gigabit Network Connection n/a 82578DC
Intel® 82567V-4 Gigabit Network Connection n/a 82567V
Intel® 82567V-3 Gigabit Network Connection n/a 82567V
Intel® 82567LM-4 Gigabit Network Connection n/a 82567LM
Intel® 82567LF-3 Gigabit Network Connection n/a 82567LF
Intel® 82567LM-3 Gigabit Network Connection n/a 82567LM
Intel® Gigabit CT Desktop Adapter E25867-xxx 82574L
Intel® 82574L Gigabit Network Connection n/a 82574L
Intel® 82567LM-2 Gigabit Network Connection n/a 82567LM
Intel® 82567LF-2 Gigabit Network Connection n/a 82567LF
Intel® 82567V-2 Gigabit Network Connection n/a 82567V
Intel® 82567LM Gigabit Network Connection n/a 82567LM
Intel® 82567LF Gigabit Network Connection n/a 82567LF
Intel® 82567V Gigabit Network Connection n/a 82567V
Intel® 82566DC-2 Gigabit Network Connection n/a 82566DC-2
Intel® 82566DM-2 Gigabit Network Connection n/a 82566DM-2
Intel® 82562V-2 10/100 Network Connection n/a 82562V-2
Intel® 82562G-2 10/100 Network Connection n/a 82562V-2
Intel® 82562GT-2 10/100 Network Connection n/a 82562V-2
Intel® 82562GT 10/100 Network Connection n/a 82562V
Intel® 82562V 10/100 Network Connection n/a 82562V
Intel® 82566DC Gigabit Network Connection n/a 82566DC
Intel® 82566DM Gigabit Network Connection n/a 82566DM
Intel® PRO/1000 PT Desktop Adapter C89516-xxx
D36739-xxx		 82572EI
Intel® PRO/1000 PT Network Connection n/a 82572EI
Intel® PRO/1000 PF Network Connection n/a 82572EI
Intel® PRO/1000 PM Network Connection n/a 82573E
Intel® PRO/1000 PL Network Connection
 n/a 82573L
Intel® PRO/1000 GT Desktop Adapter C80235-xxx 82541PI
Intel® PRO/1000 CT Network Connection n/a 82547GI
Intel® PRO/1000 T Desktop Adapter A62947-xxx

82544
Intel® PRO/1000 MT Desktop Adapter A78408-xxx
C91016-xxx
C39226-xxx
A95833-xxx

82540, 82541
Intel® PRO/1000 T Network Connection n/a 82544GC
Intel® PRO/1000 MT Network Connection n/a 82541GI
Intel® PRO/1000 MT Desktop Connection n/a 82541EI
Intel® PRO/1000 Network Connection n/a 82541ER

†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

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

Compatibility Notes

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

  • Intel® PRO/1000 CT Network Connection
  • Intel® PRO/1000 T Desktop Adapter
  • Intel® PRO/1000 T Network Connection
  • Intel® PRO/1000 XT Network Connection
  • Intel® PRO/1000 XF Network Connection
  • Intel® PRO/1000 XT Desktop Adapter

The following devices are not supported by Microsoft Windows Vista*, Windows* 7:

  • Intel® PRO/1000 CT Network Connection
  • Intel® PRO/1000 T Desktop Adapter
  • Intel® PRO/1000 T Network Connection
  • Intel® PRO/1000 XT Network Connection
  • Intel® PRO/1000 XF Network Connection
  • Intel® PRO/1000 XT Desktop Adapter

Last modified on 8/04/10 9:07p Revision

DESKTOP/adpins01.gif0000755000000000000000000002127411656741062011204 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 Intel® Active Management Technology

Intel® Active Management Technology

Intel® Active Management Technology (Intel® AMT) is a hardware-based solution that uses out-of-band communication for management access to networked client computers. Even when the client computer is powered down or has a non-operational OS, Intel AMT enables you to access and manage the system over the network. You can easily get accurate platform information, and can perform remote updating, diagnostics, debugging, and repair of a system, regardless of the state of the OS and the power state of the system. For example, if an OS has failed, you can establish a remote-control session to the failed system and then remotely reboot the failed system to a known good OS image on a remote drive. After the system reboots, you can remotely manage the reinstallation of the OS or repair.

For more information on Intel AMT features, see the documentation that came with your system.

NOTE:  Intel Active Management Technology drivers are installed as part of the base driver installation on Intel AMT capable systems.
DESKTOP/attnew.gif0000755000000000000000000001740511656741062011070 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<;DESKTOP/box.gif0000755000000000000000000000074711651733270010354 0ustar GIF89aM3!,MI8ͻ`(dihlp,tmx|pH,$J8ШtJZجvz zn|NnB. LJ+^̸ǐ#KL˘3k̹ϠC;DESKTOP/bra_st.gif0000755000000000000000000001676011656741062011043 0ustar GIF89a,0!!!999bbb,,0I8ͻ`(diRp,tmS|oH9C'l:(Q tzŵP0(zrܐhxpqsgyz!92NзϿ~jן}i{&l!vVeXI#VW/FZcCW+VHxNjN~R8oWв+FI`E)a1*!jJiZ;E.϶;ɐ𳏬ƈ9i L p!iJ0_i۪FLg>L1 #R@iq2P,0!)/\Ҭs<@MD`$H'Ғ4 P"4T]Xˠu>wl, F.l6q1uqw-m;?1$p،]ڐGN&Wny֘|rwǠ=: *鴛`˸N^;w!gκ7[<G/=GaOOڧAO|;Nȟ;MO;B:A?0  7ALr#AlqBpp% B0o- C0n5H1mYf-˖˶m<+qL!/s,0gge|)P&6;mn8yq<~I7uxs9f|8ZΏӧ8ySM :Α3AJӝUgFϹQrv4fH9Rl'fJReBv fKeRŴ3iMx=Ow\ԨC^PMRU9UTmu]W)e Y9 WzOO]%ZN&_C֓e^J}x+ zL`dQHRh},)>XE:O) q`{X>BYC>D-VF+m-;K敹T?K6-rSn}5bjV>.0˫v"EP7e*=s_ֽBkZZ75x[` =iO8", /LHAaℂ I8qs8.z y!IA7"/yKxUe!5=p\o@{ [1ӌQ@Ad'3kLcW2V,}K?X|  4.:Ώ\ `JXPhÄ1aOLY̕19XcM$@@$`1Kv6gi ^JѺu.c['@Je{Z$2p ? \Vz0B+೙X˲Vg hp4F G ȑ=of1M8lˍE eK*,0Fn#F3)cw'Tr}b0$"HcOݜ;yb8mm -73i< q[@O6 PNΚ;uƘ܈6'_O]d A;) !WV !Y)@cP0^Y8-|@s>`9{B췁Ev`~f<cugE8X8o[.gVqrlc5 y$CxXd+lȷyB57%R1Xx/w{H-P/0,aV!F xV؃8A xpExjRbʧuKpp +jNrk}8 lu1~dVhH|`gʅ/UC!q)8qc'X>k)芰GF0Frw~7r5z!t-<Ė\ƽKSȔhɂdĔ9zƭlz 0Z\U̕QQeSˏ 6,Uyrƶ|Ŝ+t#!j,QU ̨WѬ[ͽ\ΎlpŬ|Ʉ;-0t+,ZzNjΝ;b2|Ϟ\г]-о; rK8G: ,@}ҿ'K֛>ӺiiVJ`*, HĄPcҿ,Z* \\ZԥLHm ARl.Z1 zx*I!\؂=؄b [،؅] }y]ٖ#]HɼW}R٠ڡ]ӷX&jffZ.%-W۶}۵b{HۘYG ܏P8x m^ݰ5̙5fоp`ߍr3㍿m]p]4 SQFBA1YAJMc96W.8 k ;7P2FωdGeP׭h igH%(hk0.5.<A3@"VII*PVP띒 9i ,WcQ^[N^>T.i.k83&}HT0J>^cI1e)p8g^8l`YG /0 h>~l榾.EVgEaEׂyg.dZf.~Ϟ.an.,>S{ܞΪ q,zZ%\>Nӎ.)0Σ0p1b}>WWŏh+~XW1y02|.OCc$ڋ,+㛎=o"/yl~94?CSy[*8X10A^-^D/:nS_{,fmJ ]xN5-.h_@NSo'n ՊZw՗hr߮hfexOɞmar[ :qoa~Uo ~뻞Eafshο8Nٗ5)~?^No.oItQmCSlDQ(APYuf-{"O99T`. b\Fhk)` P c8c )qL\zpHS;hmJhECee9Xa!;N~>">hXε*M E`NMI(x(HѧqoĮw+ )/%ĉ;*pݬRH%GJlѤ-2gęSg.6,P@F;?4TR=dJiTUrsz5H]~csrVRWZEV\YAS6.]}7^ {aōt gjdʇ!Wf\Y˔3osϡMWiJS7^Zv׊c]۹}{mo<o^\/ѭh.uac]~^ye^{?}70@+<C0aG~-H!#7#0Id@'2JVJ+MòTK,1"LѦNK5Ad<7,1SE;3MO? ;4ХE=QUQI4)K/)S6'Ow5ԙFթTSu{THW5^uM12CZkʛYKN9xm #1@creqWb2d/hvڨT6\X%[o* u8`cUrL{hPs] TRi@5Ӂ U^ X )w^bF&%?jqRYVk_` ٤j 2jYm=b\8IޕNcT|MXZNea.XFUŖБ0ZkPiynȮ_Lp EYGh wr a [+`Y>Rgҍ6* d}+gKm:.v!~,C4@Řo ,]fç}ʳ20jϞ p#R BzOnS<#%8KwBSpwŰd)& z+^? D ?B-`b|ŁuVI XÙ\A h4Jꐵ)Lv2|m_;rtDԀ9":kL$¸0.Q&aI<2' 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

DESKTOP/caut2.gif0000755000000000000000000000065011651733270010573 0ustar GIF89aՈ|ɂvpjc]xtWkhQ_\KSPDFD>:88FDDSQQ_]]xvvkjj͵!",pHH.Ĥ83`ѐqH@dg"9J8CYxA['!0!`> BH"F$D\N4yB$;DESKTOP/ce.gif0000755000000000000000000000203311656741516010150 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@;DESKTOP/d1000.js0000755000000000000000000014263311701554312010152 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_1gd.htm"; Entries[0][1] = "Supported Adapters Desktop Gigabit"; Entries[0][2] = "Supported Intel Gigabit Desktop This driver and software are designed to operate with the following Intel Gigabit desktop adapters Product Name Board ID # &dagger ..."; Entries[0][3] = "adapters connections supported"; Entries[0][4] = "a62947 a78408 a95833 adapter barcode board built c39226 c80235 c89516 c91016 card code com/support/go/network/adapter/home connect controller ct ct2 d36739 dagger designed desktop devices digit driver e25867 e98157 extension feature following front gigabit gt guide htm http intel lan last microsoft modified motherboard mt n/a name network operate opposed pf pl plugged pm printed pro/1000 product pt r2 revision see server software sticker support vista windows xf xt xxx"; Entries[1] = new Array(4); Entries[1][0] = "amt.htm"; Entries[1][1] = "Intel Active Management Technology"; Entries[1][2] = "Intel Active Management Technology Intel Active Management Technology Intel AMT is a hardware based solution that uses out of band communication for management access to ..."; Entries[1][3] = "access active amt manage management technology"; Entries[1][4] = "access accurate active after amt band base came capable client communication computer control debugging diagnostics documentation down drive driver easily enables establish even example failed features get good hardware image information installation installed intel known manage more network note operational os out over part perform platform power reboot regardless reinstallation remote repair see session solution state system technology then updating uses"; Entries[2] = new Array(4); Entries[2][0] = "cable.htm"; Entries[2][1] = "Attach the RJ45 Network Cable"; Entries[2][2] = "How to attach an RJ45 network cable to your adapter."; Entries[2][3] = "cable port rj45"; Entries[2][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[3] = new Array(4); Entries[3][0] = "drivers.htm"; Entries[3][1] = "Install the Drivers"; Entries[3][2] = "Installing Microsoft Windows drivers for your adapter."; Entries[3][3] = "drivers install"; Entries[3][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[4] = new Array(4); Entries[4][0] = "support.htm"; Entries[4][1] = "Intel Customer Support"; Entries[4][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[4][3] = ""; Entries[4][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[5] = new Array(4); Entries[5][0] = "dupwindm.htm"; Entries[5][1] = "Configuring Speed and Duplex in Windows"; Entries[5][2] = "How to configure an adapter's speed and duplex under Microsoft Windows."; Entries[5][3] = "duplex link speed"; Entries[5][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[6] = new Array(4); Entries[6][0] = "hotwin.htm"; Entries[6][1] = "PCI Hot Plug Support for Microsoft Windows"; Entries[6][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[6][3] = "hot pci plug"; Entries[6][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[7] = new Array(4); Entries[7][0] = "hyperv.htm"; Entries[7][1] = "Creating Virtual NICs in Hyper V"; Entries[7][2] = "Creating Virtual NICs in Microsoft Hyper V."; Entries[7][3] = "hyper hyper-v nics v virtual"; Entries[7][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[8] = new Array(4); Entries[8][0] = "insert.htm"; Entries[8][1] = "Insert the Adapter"; Entries[8][2] = "Step by step instructions on how to install a PCI or PCI X adapter into a system."; Entries[8][3] = "hot install pci plug"; Entries[8][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[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] = "jumbo_dm.htm"; Entries[10][1] = "Jumbo Frames"; Entries[10][2] = "Setting up jumbo frames on adapters installed in systems running Microsoft Windows."; Entries[10][3] = "device frames jumbo latency manager throughput"; Entries[10][4] = "adapter additional administrator advanced apply aware based benefit bytes calculate capability changes click compatible configure connection consult contact cpu crc desired device different dropped end equipment ethernet features following forward four frame gigabit guide hardware header higher however implemented include increase information installed intel introduced ip jumbo larger last latency least limited link list loss manager may mbps microsoft modified more multi must network note ok open operating other otherwise packet performance pl plus pm poor pro/1000 properties proset protocols qos reduce require restrictions result revision select server set simultaneously size standard support switch systems tab tagging tcp team there throughput udp up user's utilization vendor vlans while windows"; Entries[11] = new Array(4); Entries[11][0] = "lbracket.htm"; Entries[11][1] = "Attach the Low Profile Bracket"; Entries[11][2] = "How to attach the low profile bracket for use in systems with low profile slots."; Entries[11][3] = "bracket install low profile"; Entries[11][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[12] = new Array(4); Entries[12][0] = "legaldis.htm"; Entries[12][1] = "Legal Information"; Entries[12][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[12][3] = ""; Entries[12][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[13] = new Array(4); Entries[13][0] = "license.htm"; Entries[13][1] = "Software License"; Entries[13][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[13][3] = ""; Entries[13][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[14] = new Array(4); Entries[14][0] = "warranty.htm"; Entries[14][1] = "Limited Lifetime Hardware Warranty"; Entries[14][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[14][3] = ""; Entries[14][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[15] = new Array(4); Entries[15][0] = "lights.htm"; Entries[15][1] = "Indicator Lights"; Entries[15][2] = "The Intel PRO/1000 PT Desktop Adapter have the following indicator lights Label Indication Meaning ACT/LNK Green on The adapter is connected to a valid link ..."; Entries[15][3] = "indicator installation lights"; Entries[15][4] = "act/lnk activity adapter blinking button connected control ct ct2 data desktop flashing following gigabit green help identify identity indication indicator information intel label last lights link mbps meaning modified more mt off orange partner pro/1000 proset pt revision see valid yellow"; Entries[16] = new Array(4); Entries[16][0] = "mang_win.htm"; Entries[16][1] = "Power Management"; Entries[16][2] = "Setting up Power Saver options and Wake on LAN on Microsoft Windows operating systems."; Entries[16][3] = "management power remote wake wol"; Entries[16][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[17] = new Array(4); Entries[17][0] = "manage.htm"; Entries[17][1] = "Remote Wake Up"; Entries[17][2] = "Remote Wake up and Wake on LAN basics."; Entries[17][3] = "lan remote wake wake-up"; Entries[17][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[18] = new Array(4); Entries[18][0] = "overview.htm"; Entries[18][1] = "Overview"; Entries[18][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[18][3] = "64 ia-32 installation software"; Entries[18][4] = "adapter advanced any architecture available based basic click column computer configuration contents covers desktop driver family features follow gigabit guide hardware here ia-32 install intel itanium last latest left link list make modified network note operating other overview platforms problems procedure process refers review revision see select set setup software start step supported sure system table these tips topic troubleshooting upgrading user's varies welcome windows"; Entries[19] = new Array(4); Entries[19][0] = "prosetdm.htm"; Entries[19][1] = "Using PROSet"; Entries[19][2] = "Installing, using, and removing Intel PROSet for Windows Device Manager."; Entries[19][3] = "device install manager proset"; Entries[19][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[20] = new Array(4); Entries[20][0] = "reqd_gig.htm"; Entries[20][1] = "System Requirements for Gigabit Adapters"; Entries[20][2] = "System requirements for Intel Gigabit desktop adapters."; Entries[20][3] = "32-bit 64-bit compatibility gigabit install pci pci-x requirements"; Entries[20][4] = "adapter advanced advantage architecture basic before bios bit bus check compatibility computer configuration depending dos drivers either express following gigabit hardware hat higher hyper installed installing intel kernel last latest linux master mb memory met mhz microsoft minimum mode modified must netware network newer novell open operating order pack pci platform r2 recommended red requirements revision run server service slot software sp2 sp5 sp7 supplies supported supports suse system takes types v1 v2 vista windows xp"; Entries[21] = new Array(4); Entries[21][0] = "trbl_dm.htm"; Entries[21][1] = "Configuration and Troubleshooting"; Entries[21][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[21][3] = ""; Entries[21][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[22] = new Array(4); Entries[22][0] = "pushinst.htm"; Entries[22][1] = "Microsoft Windows Push Install Instructions"; Entries[22][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[22][3] = "driver install installation push unattended"; Entries[22][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[23] = new Array(4); Entries[23][0] = "qos.htm"; Entries[23][1] = "Quality of Service QoS"; Entries[23][2] = "A brief discussion of Quality of Service QoS)."; Entries[23][3] = "balance load qos quality service tagging team"; Entries[23][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[24] = new Array(4); Entries[24][0] = "reg1000d.htm"; Entries[24][1] = "Regulatory"; Entries[24][2] = "Regulatory Compliance Statements Intel Gigabit CT Desktop Adapter Intel PRO/1000 GT Desktop Adapter Intel PRO/1000 PT Desktop Adapter Safety Compliance UL 60950 1 Second Edition ..."; Entries[24][3] = ""; Entries[24][4] = "a1 a11 a2 about accept accordance adapter against antenna any as/nzs australia/new australian authority back 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 ct 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 gigabit gt 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 nmb note notice occur off office operate outlet parkway part particular people's permission phone pro/1000 product protection provide pt pursuant radiate radio radio/tv reasonable received receiver receiving reception recognition recycling regulatory relocate reorient republic required requirements residential 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 usa user vary vcci void voltage without young zealand"; 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"; DESKTOP/drivers.htm0000755000000000000000000000613111710273344011253 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

DESKTOP/dupwindm.htm0000755000000000000000000001103211656741062011426 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 DESKTOP/hotwin.htm0000755000000000000000000000352311656574604011123 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

DESKTOP/hyperv.htm0000755000000000000000000002101311735070120011100 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

DESKTOP/index.htm0000755000000000000000000000102411656574420010710 0ustar Intel® Gigabit Desktop Network Adapters /html> DESKTOP/insert.htm0000755000000000000000000000534011656741062011110 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

DESKTOP/insscrew.gif0000755000000000000000000001616411656741062011424 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;DESKTOP/ioat.htm0000755000000000000000000001134411735070120010525 0ustar Intel® I/OAT

Intel® I/O Acceleration Technology

Intel® I/O Acceleration Technology (Intel® I/OAT) is an Intel platform network technology that accelerates, optimizes and seamlessly scales enterprise servers on Microsoft Windows Server* and Linux* operating systems.

  • Acceleration moves networking data to applications faster.

  • Optimization allows you to increase the load on your servers without increasing power consumption.

  • Seamless multiple port scaling gives you increased networking throughput from teaming along with reliable server and application availability.

Implementing Intel I/OAT requires no change to your existing network configuration or existing security implementations.

System Requirements

This is a platform-level solution for data movement. Thus, several ingredients are necessary for a system to be Intel I/OAT capable:

Platform The platform must be based on a server chipset and BIOS that are Intel I/OAT capable.
Operating System
  • Microsoft Windows Server* 2003, with Service Pack 1 and the Scalable Networking Pack, or with Service Pack 2 (SP2 contains the Scalable Networking Pack).
  • Microsoft Windows Server 2008
  • Microsoft Windows Server 2008 R2
  • Linux: Enabled in the kernel only as of kernel version 2.6.33
Network Connectivity Hardware Intel I/OAT is supported on specific server adapters and network connections available from Intel and other vendors. If you have multiple network adapters in your system, Intel I/OAT will operate automatically on the compatible models, while non-compatible adapters will pass traffic normally.
Drivers and Connectivity Software Intel I/OAT becomes active when all required software support is loaded & enabled.
  • Windows: The IOATDMA driver and NDIS miniport driver version 9.3.31.0, or greater, must be installed.
  • Linux: The Intel ioatdma module must be loaded. I/OAT support must be enabled in the kernel.

NOTES: 
  • At least one Intel I/OAT-capable port must be enabled when your system starts up. If no Intel I/OAT-capable ports are enabled at system startup, the IOATDMA driver will not register with NDIS and Intel I/OAT-capable ports enabled after system startup will show no DMA activity. Enable an Intel I/OAT-capable port and reboot to resolve this issue.
  • Intel® Chipset QuickData Technology Devices (except the Intel® 5100 and 7300 Chipset QuickData Technology Devices) support only Direct Cache Access (DCA) on Windows Server 2003. DMA offloading is not supported by these devices.

Tuning Your System

Memory

Your system memory channels should be fully populated. Intel recommends a minimum of 4 GB of system memory or 1 GB per channel. Refer to your system guide for specific information regarding memory channels.

Windows Adapter Settings

In a Windows environment, the following advanced settings must be enabled (see the Intel® PROSet link in the left pane):

  • RSS
  • Offload Receive IP Checksum
  • Offload Receive TCP Checksum

Last modified on 3/07/11 2:01p Revision

DESKTOP/ipsecoff.htm0000755000000000000000000000345111656574604011411 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

DESKTOP/jumbo_dm.htm0000755000000000000000000001363011656574604011407 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

DESKTOP/lbracket.htm0000755000000000000000000000424111656741062011372 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

DESKTOP/legaldis.htm0000755000000000000000000000205611701323454011361 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 DESKTOP/license.htm0000755000000000000000000003527311654245266011241 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

DESKTOP/lights.htm0000755000000000000000000000750711656574420011107 0ustar Indicator Lights

Indicator Lights

The Intel® PRO/1000 PT Desktop Adapter have the following indicator lights:

 Label

 Indication Meaning
 ACT/LNK Green on The adapter is connected to a valid link partner.
Green flashing Data activity
Off No link.
   
10=OFF
100=GRN
1000=YLW		 Off 10 Mbps
Green 100 Mbps
Yellow 1000 Mbps
Orange flashing Identity. Use the "Identify Adapter" button in Intel® PROSet to control blinking. See Intel PROSet Help for more information.

The Intel® Gigabit CT2, Gigabit CT, PRO/1000 T, and PRO/1000 MT Desktop Adapters have the following indicator lights:

 Label

 Indication Meaning
 ACT/LNK Green on The adapter is connected to a valid link partner.
Green flashing Data activity
Off No link.
Yellow flashing Identity. Use the "Identify Adapter" button in Intel® PROSet to control blinking. See Intel PROSet Help for more information.
10=OFF
100=GRN
1000=YLW		 Off 10 Mbps
Green 100 Mbps
Yellow 1000 Mbps

Last modified on 8/04/10 9:07p Revision

DESKTOP/manage.htm0000755000000000000000000002521311734015456011033 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 DESKTOP/mang_win.htm0000755000000000000000000001754011734015456011406 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

DESKTOP/note.gif0000755000000000000000000000073211651733270010523 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 ;DESKTOP/overview.htm0000755000000000000000000000535511656574420011462 0ustar Overview

Overview

Welcome to the User's Guide for the Intel® Gigabit 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.

For Itanium®-based computers, see the Itanium 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 network drivers.

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

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

Once you have installed the network adapter(s), you can set other advanced features. The available features and the configuration process varies with the adapter and your operating system.

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

DESKTOP/pro1000c.gif0000755000000000000000000001342111656741062011024 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;;DESKTOP/prosetdm.htm0000755000000000000000000000472411714034554011442 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 DESKTOP/pushinst.htm0000755000000000000000000000354711735070116011461 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

DESKTOP/qos.htm0000755000000000000000000000422711735070116010402 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

DESKTOP/reg1000d.htm0000755000000000000000000001363411656741516011037 0ustar Regulatory

Regulatory Compliance Statements

  • Intel® Gigabit CT Desktop Adapter
  • Intel® PRO/1000 GT Desktop Adapter
  • Intel® PRO/1000 PT 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 Part 15 Radiated & Conducted Emissions (USA)
  • ICES-003 Radiated & Conducted Emissions (Canada)
  • CISPR 22 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 Radiated & Conducted Emissions (Japan)
  • CNS13438 Radiated & Conducted Emissions (Taiwan)
  • AS/NZS CISPR 22 Radiated & Conducted Emissions (Australia/New Zealand)
  • KCC notice 1997-41, 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 markings 
  • VCCI marking
  • Australian C-Tick Mark
  • Korea KCC mark
  • Taiwan BSMI mark
  • People's Republic of China "EFUP" mark

Electromagnetic Compatibility Notices

FCC Declaration of Conformity Statement

The Intel Gigabit CT Desktop Adapter, PRO/1000 PT and PRO/1000 GT Desktop Adapter 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

Manufacturer Declaration

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

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.

VCCI Class B Statement (Japan)

China RoHS Declaration

KCC Notice Class B (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.

 

Intel Corporation, Mailstop JF3-446
5200 N.E. Elam Young Parkway
Hillsboro, OR 97124-6497

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

DESKTOP/remscrew.gif0000755000000000000000000001752011656741062011413 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};DESKTOP/reqd_gig.htm0000755000000000000000000000633711735067552011377 0ustar System Requirements for Gigabit Adapters

System Requirements

Before installing the network adapter, check your system for the following minimum configuration requirements for Intel® Gigabit Network Adapters.

Hardware Compatibility - Gigabit Adapters

  • The latest BIOS for your computer
  • One of the following slot types, depending on your adapter:
    • One open PCI bus master slot, 32-bit or 64-bit, operating at 33 or 66 MHz
    • One open PCI-X slot operating at 66, 100 or 133 MHz(recommended)
    • One open PCI-Express slot (v1.0a or newer), 4x, 8x or 16x.
  • 64 MB of system memory

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 7, 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
  • Novell* NetWare*  5.1 SP7, 6.0 SP5, 6.5 SP2

Intel® 64 Architecture Platform Requirements

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

  • Microsoft Windows XP, with latest service pack installed
  • Microsoft Windows Vista, with latest service pack installed
  • Microsoft Windows 7, with latest service pack installed
  • Microsoft Windows Server 2003, with latest service pack installed
  • Microsoft Windows Server 2008, with latest service pack installed
  • Microsoft Windows Server 2008 R2, 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
  • 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

DESKTOP/run.gif0000755000000000000000000000014111654247274010363 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

DESKTOP/setbd_dm.htm0000755000000000000000000006127511656741062011376 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

DESKTOP/slideoff.gif0000755000000000000000000002046211656741062011356 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Ƿ;DESKTOP/snmp.htm0000755000000000000000000000361211656574604010567 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

DESKTOP/snmpwin.htm0000755000000000000000000000441211656574604011304 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

DESKTOP/style.css0000755000000000000000000000450511651733270010743 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 } DESKTOP/support.gif0000755000000000000000000003157611651733270011304 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;DESKTOP/support.htm0000755000000000000000000000206611651733270011317 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

DESKTOP/team_dm.htm0000755000000000000000000005600611735070120011203 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

DESKTOP/test_dm.htm0000755000000000000000000000343011656741062011241 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

DESKTOP/toc_dm.htm0000755000000000000000000001352111701323364011041 0ustar
Search this guide
  

Overview

System Requirements

Supported Adapters

Intel® Active Management Technology

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

Jumbo Frames

Teaming

VLANs

Power Management

Simple Network Management Protocol (SNMP)

Quality of Service (QoS)

Save & Restore

Hot Plug

Windows Management Instrumentation (WMI)

IPSecurity Offloading

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

Linux Setup and Features

Install Drivers and Features

FreeBSD Setup and Features

Install the Drivers

Setup Speed & Duplex

Jumbo Frames

Netware Setup and Features

Install the Drivers

Setup Speed & Duplex

Jumbo Frames

Hot Plug

Simple Network Management Protocol (SNMP)

Installing DOS Drivers

Intel Boot Agent

EFI

Technical Information & Support

Configuration and Troubleshooting

Other 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 8/12/11 10:40a Revision

DESKTOP/top_d1g.htm0000755000000000000000000000054711656574420011147 0ustar

Intel® Gigabit Desktop Adapter Guide

User Guides Home

DESKTOP/trbl_dm.htm0000755000000000000000000003446611656741062011242 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 DESKTOP/trbl_win.htm0000755000000000000000000000543411656741062011430 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 DESKTOP/vcci-a.gif0000755000000000000000000007771111656741516010742 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⟋>:^:ꩫ.!;DESKTOP/vlan.gif0000755000000000000000000001066311656574604010533 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{[{};DESKTOP/vlwin.htm0000755000000000000000000001140111711606312010724 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

DESKTOP/warranty.htm0000755000000000000000000001324011651733270011446 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

DESKTOP/wminicdm.htm0000755000000000000000000000763511656574604011432 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