| Re: This is how FU'ed the US healthcare system is [message #87231 is a reply to message #87230] |
Tue, 26 June 2007 20:23   |
Deej [4]
 Messages: 1292 Registered: January 2007
|
Senior Member |
|
|
u is one of 4 that were =
working =3D3D
> > >=3D3D3D<BR>>perfectly=3D3D20
> > > when I took my system off line. I can't imagine it =
being a =3D3D
> > >=3D3D3D<BR>>problem.=3D3D20
> > > Bent pins on SCSI cables can be a serious issue =
though. Your =3D3D
> > >=3D3D3D<BR>>system=3D3D20
> > > will not function with bad SCSI =
cables.<BR>><BR>><!DOCTYPE =3D3D
> > >HTML=3D3D20
> > > PUBLIC "-//W3C//DTD HTML 4.0=3D3D20
> > > =
Transitional//EN"><BR>><HTML><HEAD><BR>><META=3D3D20
> > > http-equiv=3D3D3D3DContent-Type =
content=3D3D3D3D"text/html;=3D3D20
> > > =3D3D3D<BR>>charset=3D3D3D3Diso-8859-1"><BR>><META =
=3D3D
> > >content=3D3D3D3D"MSHTML=3D3D20
> > > 6.00.6000.16414"=3D3D20
> > > =3D3D
> > =
>name=3D3D3D3DGENERATOR><BR>><STYLE></STYLE><BR>></HEA=3D3D
> > >D><BR>><BODY=3D3D20
> > > bgColor=3D3D3D3D#ffffff><BR>><BLOCKQUOTE=3D3D20
> > > =
dir=3D3D3D3Dltr=3D3D3D20<BR>>style=3D3D3D3D"PADDING-RIGHT: 0px; =3D
> >PADDING-LEFT: =3D3D
> > >5px;=3D3D20
> > > MARGIN-LEFT: 5px; =3D3D3D<BR>>BORDER-LEFT: #000000 =
2px solid; =3D3D
> > >MARGIN-RIGHT:=3D3D20
> > > 0px"><BR>> <DIV><FONT face=3D3D3D3DArial=3D3D20
> > > size=3D3D3D3D2></FONT> </DIV><BR>> <DIV>"Tom =3D3D
> > >Bruhl"=3D3D20
> > > <<A=3D3D3D20<BR>> href=3D3D3D3D"<A=3D3D20
> > > =3D3D
> > =3D
> =
>>href=3D3D3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:=
arp=3D
> >egi=3D3D
> > >o@comcast.net">arpegio@comcast.net</A</A>>>=3D3D20
> > > wrote =3D3D3D<BR>>in message=3D3D3D20<BR>> <A =
href=3D3D3D3D"<A=3D3D20
> > > =3D3D
> > =3D
> =
>>href=3D3D3D'news:46972376@linux">news:46972376@linux</A>...</DIV'>news:=
469=3D
> >723=3D3D
> > =
>76@linux">news:46972376@linux</A>...</DIV</A>><BR>>&nbs=3D3D
> > >p;=3D3D20
> > > <DIV><FONT face=3D3D3D3DArial size=3D3D3D3D2>This =
is really a =3D3D
> > >novice oriented=3D3D20
> > > =3D3D3D<BR>>question but . .=3D3D3D20<BR>> =3D3D20
> > > .</FONT></DIV><BR>> <DIV><FONT =3D3D
> > >face=3D3D3D3DArial=3D3D20
> > > size=3D3D3D3D2>It doesn't matter which card is the =
=3D3D
> > >=3D3D3D<BR>>"A"=3D3D3D20<BR>> =3D3D20
> > > card</FONT></DIV><BR>> <DIV><FONT =3D3D
> > >face=3D3D3D3DArial=3D3D20
> > > size=3D3D3D3D2>in your system as far as Paris' =
ID=3D3D20
> > > =3D3D3D<BR>>orientation=3D3D3D20<BR>> =3D3D20
> > > right?</FONT></DIV><BR>> <DIV><FONT =3D3D
> > >face=3D3D3D3DArial=3D3D20
> > > size=3D3D3D3D2></FONT> </DIV><BR>> =3D3D
> > ><DIV><BR>> =3D3D20
> > > <DIV><FONT face=3D3D3D3DArial size=3D3D3D3D2>Yes, =
it does, and
> the =3D3D
> > >orientation=3D3D20
> > > of<BR>=3D3D3D<BR>>the slots=3D3D3D20<BR>> you are =
using in =3D3D
> > >combination with=3D3D20
> > > the orientation of the ribbon=3D3D3D20<BR>> cables =
will
> determine =3D3D
> > >this.=3D3D20
> > > Have you changed them around during
> =3D3D3D<BR>>your=3D3D3D20<BR>> =3D3D
> > >
> > > reconfiguration?</FONT></DIV><BR>> =3D3D
> > ><DIV><FONT=3D3D20
> > > face=3D3D3D3DArial size=3D3D3D3D2></FONT> =
</DIV><BR>> =3D3D20
> > > <DIV><FONT face=3D3D3D3DArial size=3D3D3D3D2>Start =
with a new
> SCSI =3D3D
> > >cable and a=3D3D20
> > > =3D3D3D<BR>>single EDS=3D3D3D20<BR>> card. Test =
each MEC. Once
> you =3D3D
> > >know if=3D3D20
> > > there is a problem there, add a<BR>=3D3D3D<BR>>new =
=3D3D
> > >SCSI=3D3D3D20<BR>> cable=3D3D20
> > > and another card. Put different modules in the MECs =
so you
> can =3D3D
> > >=3D3D3D<BR>>see=3D3D20
> > > which=3D3D3D20<BR>> one is on card A, B, C at all =
times. this =3D3D
> > >will give you=3D3D20
> > > the info =3D3D3D<BR>>as to=3D3D3D20<BR>> how the =
cards are =3D3D
> > >initializing and=3D3D20
> > > which card is card A, B, C as you =
=3D3D3D<BR>>start=3D3D3D20<BR>> =3D3D
> > >adding more=3D3D20
> > > hardware. the MEC i sent you is one of 4 that =
were=3D3D20
> > > working<BR>=3D3D3D<BR>><BR>> perfectly when I took =
my system =3D3D
> > >off line. I=3D3D20
> > > can't imagine it being a =
=3D3D3D<BR>>problem.=3D3D3D20<BR>> Bent =3D3D
> > >pins on SCSI=3D3D20
> > > cables can be a serious issue though. Your system =
=3D
> >=3D3D3D<BR>>will=3D3D20
> > > not=3D3D3D20<BR>> function with bad SCSI=3D3D20
> > > =3D3D
> > =
>=3D3D3D<BR>>cables.</FONT></DIV></DIV></BLOCKQUOTE>=3D3D
> > >;</BODY></HTML><BR>><BR>><BR></BLOCKQUOTE>
> > ><DIV><FONT size=3D3D3D2><BR><BR>I choose Polesoft =
Lockspam to fight =3D
> >spam, =3D3D
> > >and=3D3D20
> > >you?<BR><A=3D3D20
> > =3D
> =
>>href=3D3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com=
/re
> =
<http://www.polesoft.com/refer.html">http://www.polesoft.com/re>=3D
> >fer=3D3D
> > >.html</A> </FONT></DIV></BODY></HTML>
> > >
> > >
> >
> >
> ><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 =
Transitional//EN">
> ><HTML><HEAD>
> ><META http-equiv=3D3DContent-Type =
content=3D3D"text/html; =3D
> >charset=3D3Diso-8859-1">
> ><META content=3D3D"MSHTML 6.00.2800.1400" =
name=3D3DGENERATOR>
> ><STYLE></STYLE>
> ></HEAD>
> ><BODY bgColor=3D3D#ffffff>
> ><DIV><FONT face=3D3DArial size=3D3D2>Hey =
Rod,</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>Hiding the default =
project didn't
> help=3D20
> >anything. I've never</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>had 2.?? installed =
on this comp
> so I =3D
> >think I'm safe=3D20
> >there regarding</FONT></DIV>
> ><DIV><FONT face=3D3DArial =
size=3D3D2>drivers.</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>I am only able to =
intermitantly
> get the
> =3D
> >442 working=3D20
> >as the master.</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>I think that's do =
to the scsi cable =3D
> >issue. I=3D20
> >need four new ones.</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>I am unable to get =
more than one
> EDS =3D
> >card working=3D20
> >WITH the 442.</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>Not sure why. The =
ribbons are all =3D
> >wired=3D20
> >correctly.</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>I'm off to a =
hellish gigging =3D
> >weekend. No more=3D20
> >time for hell in Paris.</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>Thanks for all your
> input,</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>Tom</FONT></DIV>
> ><BLOCKQUOTE=3D20
> >style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; =3D
> >BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> > <DIV>"Rod Lincoln" <<A=3D20
> > =3D
> =
>href=3D3D"mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com</A=
>&g
> =
<mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com</A>&g>=3D
> >t;=3D2
|
|
|
|
|
|
|
|
|
|
| Re: This is how FU'ed the US healthcare system is [message #87240 is a reply to message #87230] |
Tue, 26 June 2007 23:22   |
LaMont
Messages: 828 Registered: October 2005
|
Senior Member |
|
|
3D3D20<BR>> > =3D20
> > reconfiguration?</FONT></DIV><BR>> > =3D20
> > <DIV><FONT face=3D3D3D3DArial =
size=3D3D3D3D2></FONT>=3D20
> > </DIV><BR>> > <DIV><FONT =3D
> >face=3D3D3D3DArial=3D20
> > size=3D3D3D3D2>Start with a new SCSI cable =
=3D3D<BR>>and a =3D
> >=3D3D3D<BR>> =3D20
> > >single EDS=3D3D3D20<BR>> > card. Test each MEC. =3D
> >Once you=3D20
> > know if there is a problem there, =
add<BR>=3D3D<BR>>a<BR>> =3D20
> > =3D3D3D<BR>> >new SCSI=3D3D3D20<BR>> > cable =3D
> >and another=3D20
> > card. Put different modules in the MECs so you =
=3D3D<BR>>can =3D
> >=3D3D3D<BR>> =3D20
> > >see which=3D3D3D20<BR>> > one is on card A, B, C =3D
> >at all=3D20
> > times. this will give you the info =
=3D3D<BR>>=3D3D3D<BR>> =3D
> >>as=3D20
> > to=3D3D3D20<BR>> > how the cards are initializing and =
=3D
> >which card=3D20
> > is card A, B, C as =3D3D<BR>>you =3D3D3D<BR>> =3D
> >>start=3D3D3D20<BR>> =3D20
> > > adding more hardware. the MEC i sent you is one of 4 =
that =3D
> >were=3D20
> > =3D3D<BR>>working<BR>> =3D3D3D<BR>> =3D
> >><BR>> > =3D20
> > perfectly when I took my system off line. I can't =
imagine it=3D20
> > being<BR>=3D3D<BR>>a =3D3D3D<BR>> =3D
> >>problem.=3D3D3D20<BR>> =3D20
> > > Bent pins on SCSI cables can be a serious issue =
though. =3D
> >Your=3D20
> > system<BR>=3D3D<BR>>=3D3D3D<BR>> >will =3D
> >not=3D3D3D20<BR>> =3D20
> > > function with bad SCSI =3D3D3D<BR>> =3D20
> > =3D
> >>cables.</FONT></DIV></DIV></BLOCKQUOTE></B=3D
> >ODY></HTML><BR>> =3D20
> > ><BR>> ><BR>><BR>><BR>><BR>>I choose =3D
> >Polesoft=3D20
> > Lockspam to fight spam, and=3D20
> > you?<BR>>http://www.polesoft.com/refer.html =3D20
> > <BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML =
4.0=3D20
> > Transitional//EN"><BR>><HTML><HEAD><BR>><META=3D20
> > http-equiv=3D3D3DContent-Type =
content=3D3D3D"text/html;=3D20
> > =3D3D<BR>>charset=3D3D3Diso-8859-1"><BR>><META =3D
> >content=3D3D3D"MSHTML=3D20
> > 6.00.2800.1400"=3D20
> > =3D
> >name=3D3D3DGENERATOR><BR>><STYLE></STYLE><BR>></HEA=3D
> >D><BR>><BODY=3D20
> > bgColor=3D3D3D#ffffff><BR>><DIV><FONT =
face=3D3D3DArial=3D20
> > =3D
> >size=3D3D3D2>Guys,</FONT></DIV><BR>><DIV><FONT=3D20
> > face=3D3D3DArial size=3D3D3D2>I'm all set with the =
cables and the =3D
> >=3D3D<BR>>which=3D20
> > card is =3D
> >A=3D3D20<BR>>bit.</FONT></DIV><BR>><DIV><FONT=3D20
> > face=3D3D3DArial size=3D3D3D2>Rod you were right about =
what I=3D20
> > =3D
> >was=3D3D20<BR>>asking.</FONT></DIV><BR>><DIV><FO=3D
> >NT=3D20
> > face=3D3D3DArial size=3D3D3D2></FONT> =3D
> ></DIV><BR>><DIV><FONT=3D20
> > face=3D3D3DArial size=3D3D3D2>In any event I scaled =
down to one EDS=3D20
> > =3D3D<BR>>(Pretty sure=3D3D20<BR>>that's card A=3D20
> > right?!!!)</FONT></DIV><BR>><DIV><FONT =3D
> >face=3D3D3DArial=3D20
> > size=3D3D3D2>and plugged it into each of my two=3D20
> > =3D3D<BR>>working=3D3D20<BR>>Mecs. Paris will =
boot=3D20
> > but</FONT></DIV><BR>><DIV><FONT face=3D3D3DArial =3D
> >
> > size=3D3D3D2>even internal clock was never found =3D
> >nor<BR>=3D3D<BR>>were=3D20
> > the=3D3D20<BR>>in/outs on each=3D20
> > Mec.</FONT></DIV><BR>><DIV><FONT =3D
> >face=3D3D3DArial=3D20
> > size=3D3D3D2>The 442 on the other hand works like =3D
> >a<BR>=3D3D<BR>>champ=3D20
> > one=3D3D20<BR>>card only. I=3D20
> > suspect</FONT></DIV><BR>><DIV><FONT =3D
> >face=3D3D3DArial=3D20
> > size=3D3D3D2>either all my Mecs are screwy now or =
=3D3D<BR>>the=3D20
> > SCSI=3D3D20<BR>>cables are intermitant at=3D20
> > best.</FONT></DIV><BR>><DIV><FONT =3D
> >face=3D3D3DArial=3D20
> > size=3D3D3D2>It's working fine with the 442 so I'm =3D
> >=3D3D<BR>>sticking=3D20
> > with=3D3D20<BR>>that for=3D20
> > today.</FONT></DIV><BR>><DIV><FONT =3D
> >face=3D3D3DArial=3D20
> > size=3D3D3D2>I'll add my EDS cards one by one and =
=3D3D<BR>>see if =3D
> >that=3D20
> > is=3D3D20<BR>>back to=3D20
> > normal.</FONT></DIV><BR>><DIV><FONT =3D
> >face=3D3D3DArial=3D20
> > size=3D3D3D2></FONT> </DIV><BR>><DIV><FONT =3D
> >face=3D3D3DArial=3D20
> > size=3D3D3D2>Thanks for the help and if I need =3D
> >scsi<BR>=3D3D<BR>>cables=3D20
> > what=3D3D20<BR>>and where to buy them would be good =
info=3D20
> > too.</FONT></DIV><BR>><DIV><FONT =3D
> >face=3D3D3DArial=3D20
> > size=3D3D3D2>Mr=3D20
> > =3D
> =
>Testy</FONT></DIV><BR>><BLOCKQUOTE=3D3D20<BR>>style=3D3D=3D
> >3D"PADDING-RIGHT:=3D20
> > 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D3D<BR>>BORDER-LEFT: =3D
> >#000000 2px=3D20
> > solid; MARGIN-RIGHT: 0px"><BR>> <DIV>"Rod =
Lincoln"=3D20
> > <<A=3D3D20<BR>> =3D3D<BR>>href=3D3D3D"<A=3D20
> > =3D
> =
>href=3D3D'mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com</A=
>&a=3D
> =
>mp;g'>mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com</=3D
> >A>&g</A>=3D3D<BR>>t;=3D3D20<BR>> =3D20
> > wrote in message <A=3D3D20<BR>> href=3D3D3D"<A=3D20
> > =3D
> =
>href=3D3D'news:469780ce$1@linux">news:469780ce$1@linux</A>...</DIV><BR>I=
'>n=3D
> =
>ews:469780ce$1@linux">news:469780ce$1@linux</A>...</DIV>&l=3D
> >t;BR>I</A><BR>=3D3D<BR>>think=3D20
> > Tom=3D3D20<BR>> was asking if there was a "3.0" =
version of the =3D
> >EDS card=3D20
> > that =3D3D<BR>>needed<BR>to be=3D3D20<BR>> connected =
to =3D
> >the master.=3D20
> > The answer to that would be no. <BR>Is this =
=3D3D<BR>>what=3D20
> > you=3D3D20<BR>> were asking Tom?<BR>DJ's advice is =
very =3D
> >important=3D20
> > though. I would do =3D3D<BR>>it, if=3D3D20<BR>> you =
haven't=3D20
> > already.<BR>I don't want to sound like a "RTFM" kind =
of =3D
> >=3D3D<BR>>guy,=3D20
> > but=3D3D20<BR>> the Paris manual describes<BR>this =3D
> >procedure pretty=3D20
> > well.<BR>It's on =3D3D<BR>>page 4=3D3D20<BR>> and 5 of =
=3D
> >the 3.0=3D20
> > version.<BR>It kind of sounds to me like you may=3D20
> > not<BR>=3D3D<BR>>be=3D3D20<BR>> hooking up the correct =
eds=3D20
> > card<BR>to the master =3D
> >mec.<BR>Rod<BR>"DJ"=3D3D20<BR>> =3D20
> > <animix _ at _ animas _ dot _ net>=3D3D20<BR>> =3D20
> > wrote:<BR>><BR>><BR>><BR>> "Tom =3D
> >Bruhl"=3D20
> > <<A=3D3D20<BR>> href=3D3D3D"<A=3D20
> > =3D
> =
>href=3D3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arp=
egi=3D
> >o@comcast.net">arpegio@comcast.net</A</A>>>=3D20
> > wrote =3D3D<BR>>in message=3D3D20<BR>> =3D20
> > =3D3D3D<BR>>news:46972376@linux...<BR>> This is really =
=3D
> >a=3D20
> > =3D3D<BR>>novice oriented=3D3D20<BR>> question but . . =
=3D
> >.<BR>> It=3D20
> > doesn't matter which card is the =
=3D3D<BR>>"A"=3D3D20<BR>> =3D20
> > card<BR>> in your system as far as Paris' ID=3D20
> > orientation=3D3D20<BR>> right?<BR>><BR>> Yes, =3D
> >it does,=3D20
> > and the orientation of the =3D3D<BR>>slots=3D3D20<BR>> =
you are =3D
> >using in=3D20
> > =3D3D3D<BR>>combination with the orientation of =
the=3D20
> > =3D3D<BR>>ribbon=3D3D20<BR>> cables will determine =3D
> >=3D3D3D<BR>>this.=3D20
> > Have you changed them around =3D3D<BR>>during =
your=3D3D20<BR>> =3D
> >
> > reconfiguration?<BR>><BR>> Start with a new SCSI =3D
> >cable and=3D20
> > =3D3D<BR>>a=3D3D20<BR>> single EDS card. Test each =
MEC.=3D20
> > Once<BR>=3D3D3D<BR>>you know if there =
=3D3D<BR>>is=3D20
> > a=3D3D20<BR>> problem there, add a new SCSI cable and =
another=3D20
> > =3D3D3D<BR>>card. Put =3D3D<BR>>different=3D3D20<BR>> =
=3D
> >modules in the=3D20
> > MECs so you can see which one is on =3D3D3D<BR>>card =
A, =3D
> >=3D3D<BR>>B, C=3D20
> > at=3D3D20<BR>> all times. this will give you the info =
as to how =3D
> >the=3D20
> > =3D3D3D<BR>>cards =3D3D<BR>>are=3D3D20<BR>> =3D
> >initializing and which=3D20
> > card is card A, B, C as you start =
=3D3D<BR>>=3D3D3D<BR>>adding =3D
> >
> > more=3D3D20<BR>> hardware. the MEC i sent you is one =
of 4 that =3D
> >were=3D20
> > working =3D3D<BR>>=3D3D3D<BR>>perfectly=3D3D20<BR>> =
=3D
> >when I took my=3D20
> > system off line. I can't imagine it being a=3D20
> > =3D3D<BR>>=3D3D3D<BR>>problem.=3D3D20<BR>> Bent pins =
on =3D
> >SCSI cables=3D20
> > can be a serious issue though. Your=3D20
> > =3D3D<BR>>=3D3D3D<BR>>system=3D3D20<BR>> will not =3D
> >function with bad=3D20
> > SCSI cables.<BR>><BR>><!DOCTYPE=3D20
> > =3D3D<BR>>HTML=3D3D20<BR>> PUBLIC "-//W3C//DTD HTML =
=3D
> >4.0=3D3D20<BR>> =3D20
> > =3D
> >Transitional//EN"><BR>><HTML><HEAD><BR>>=3D
> ><META=3D3D20<BR>> =3D20
> > http-equiv=3D3D3D3DContent-Type =3D
> >content=3D3D3D3D"text/html;=3D3D20<BR>> =3D20
> > =3D3D3D<BR>>charset=3D3D3D3Diso-8859-1"><BR>><META =3D
> >
> > =3D3D<BR>>content=3D3D3D3D"MSHTML=3D3D20<BR>> =3D20
> > 6.00.6000.16414"=3D3D20<BR>> =3D20
> > =3D
> >=3D3D<BR>>name=3D3D3D3DGENERATOR><BR>><STYLE></STYLE&=3D
> >gt;<BR>></HEA=3D3D<BR>>D><BR>><BODY=3D3D20<BR>&=3D
> >gt; =3D20
> > =3D
> >bgColor=3D3D3D3D#ffffff><BR>><BLOCKQUOTE=3D3D20<BR>> =3D
> >
> > =
dir=3D3D3D3Dltr=3D3D3D20<BR>>style=3D3D3D3D"PADDING-RIGHT: 0px; =3D
> >PADDING-LEFT:=3D20
> > =3D3D<BR>>5px;=3D3D20<BR>> MARGIN-LEFT: 5px; =3D
> >=3D3D3D<BR>>BORDER-LEFT:=3D20
> > #000000 2px solid; =3D3D<BR>>MARGIN-RIGHT:=3D3D20<BR>> =
=3D20
> > 0px"><BR>> <DIV><FONT =3D
> >face=3D3D3D3DArial=3D3D20<BR>> =3D20
>
|
|
|
|
| Re: This is how FU'ed the US healthcare system is [message #87241 is a reply to message #87240] |
Tue, 26 June 2007 23:27   |
LaMont
Messages: 828 Registered: October 2005
|
Senior Member |
|
|
> size=3D3D3D3D2></FONT> </DIV><BR>> =3D
> ><DIV>"Tom=3D20
> > =3D3D<BR>>Bruhl"=3D3D20<BR>> <<A=3D3D3D20<BR>>=3D20
> > href=3D3D3D3D"<A=3D3D20<BR>> =3D20
> > =3D
> =
>=3D3D<BR>>href=3D3D3D'mailto:arpegio@comcast.net">arpegio@comcast.net&l=3D=
> =
>t;/A'>mailto:arpegi=3D3D<BR>>o@comcast.net">arpegio@comcast.net<=3D
> >;/A</A>>>=3D3D20<BR>> =3D20
> > wrote =3D3D3D<BR>>in message=3D3D3D20<BR>> <A=3D20
> > href=3D3D3D3D"<A=3D3D20<BR>> =3D20
> > =3D
> =
>=3D3D<BR>>href=3D3D3D'news:46972376@linux">news:46972376@linux</A>=3D
> =
>;...</DIV'>news:469723=3D3D<BR>>76@linux">news:46972376@linux&l=3D
> >t;/A>...</DIV</A>><BR>>&nbs=3D3D<BR>>p;=3D3D20=3D
> ><BR>> =3D20
> > <DIV><FONT face=3D3D3D3DArial size=3D3D3D3D2>This is =
really a=3D20
> > =3D3D<BR>>novice oriented=3D3D20<BR>> =3D
> >=3D3D3D<BR>>question but .=3D20
> > .=3D3D3D20<BR>> =3D3D20<BR>> =3D20
> > .</FONT></DIV><BR>> <DIV><FONT=3D20
> > =3D3D<BR>>face=3D3D3D3DArial=3D3D20<BR>> =
size=3D3D3D3D2>It =3D
> >doesn't matter which=3D20
> > card is the =3D3D<BR>>=3D3D3D<BR>>"A"=3D3D3D20<BR>> =
=3D
> >=3D3D20<BR>> =3D20
> > card</FONT></DIV><BR>> <DIV><FONT=3D20
> > =3D3D<BR>>face=3D3D3D3DArial=3D3D20<BR>> =
size=3D3D3D3D2>in your =3D
> >system as far=3D20
> > as Paris' ID=3D3D20<BR>> =3D
> >=3D3D3D<BR>>orientation=3D3D3D20<BR>>=3D20
> > =3D3D20<BR>> right?</FONT></DIV><BR>>=3D20
> > <DIV><FONT =3D3D<BR>>face=3D3D3D3DArial=3D3D20<BR>> =
=3D20
> > size=3D3D3D3D2></FONT> </DIV><BR>>=3D20
> > =3D3D<BR>><DIV><BR>> =3D3D20<BR>> =3D
> ><DIV><FONT=3D20
> > face=3D3D3D3DArial size=3D3D3D3D2>Yes, it does, and =
the=3D20
> > =3D3D<BR>>orientation=3D3D20<BR>> =3D
> >of<BR>=3D3D3D<BR>>the=3D20
> > slots=3D3D3D20<BR>> you are using in =
=3D3D<BR>>combination=3D20
> > with=3D3D20<BR>> the orientation of the =3D
> >ribbon=3D3D3D20<BR>> cables=3D20
> > will determine =3D3D<BR>>this.=3D3D20<BR>> Have you =
changed =3D
> >them around=3D20
> > during =3D3D3D<BR>>your=3D3D3D20<BR>> =3D
> >=3D3D<BR>><BR>> =3D20
> > reconfiguration?</FONT></DIV><BR>>=3D20
> > =3D3D<BR>><DIV><FONT=3D3D20<BR>> =
face=3D3D3D3DArial=3D20
> > size=3D3D3D3D2></FONT> </DIV><BR>> =3D
> >=3D3D20<BR>> =3D20
> > <DIV><FONT face=3D3D3D3DArial size=3D3D3D3D2>Start =
with a new =3D
> >SCSI=3D20
> > =3D3D<BR>>cable and a=3D3D20<BR>> =
=3D3D3D<BR>>single=3D20
> > EDS=3D3D3D20<BR>> card. Test each MEC. Once you =
=3D3D<BR>>know =3D
> >
> > if=3D3D20<BR>> there is a problem there, add=3D20
> > a<BR>=3D3D3D<BR>>new =3D3D<BR>>SCSI=3D3D3D20<BR>> =3D
> >
> > cable=3D3D20<BR>> and another card. Put different =
modules in =3D
> >the MECs so=3D20
> > you can =3D3D<BR>>=3D3D3D<BR>>see=3D3D20<BR>> =3D20
> > which=3D3D3D20<BR>> one is on card A, B, C at all =
times. this=3D20
> > =3D3D<BR>>will give you=3D3D20<BR>> the info =3D
> >=3D3D3D<BR>>as=3D20
> > to=3D3D3D20<BR>> how the cards are =
=3D3D<BR>>initializing=3D20
> > and=3D3D20<BR>> which card is card A, B, C as you=3D20
> > =3D3D3D<BR>>start=3D3D3D20<BR>> =3D3D<BR>>adding=3D20
> > more=3D3D20<BR>> hardware. the MEC i sent you is one =
of 4 that=3D20
> > were=3D3D20<BR>> =3D
> >working<BR>=3D3D3D<BR>><BR>>=3D20
> > perfectly when I took my system =3D3D<BR>>off line. =
=3D
> >I=3D3D20<BR>> can't=3D20
> > imagine it being a =3D3D3D<BR>>problem.=3D3D3D20<BR>> =
=3D
> >Bent=3D20
> > =3D3D<BR>>pins on SCSI=3D3D20<BR>> cables can be a =
serious =3D
> >issue though.=3D20
> > Your system =3D3D3D<BR>>will=3D3D20<BR>> =3D
> >not=3D3D3D20<BR>>=3D20
> > function with bad SCSI=3D3D20<BR>> =3D20
> > =3D
> >=3D3D<BR>>=3D3D3D<BR>>cables.</FONT></DIV></DIV>=3D
> >;</BLOCKQUOTE>=3D3D<BR>>;</BODY></HTML><BR>>&=3D
> >lt;BR>><BR></BLOCKQUOTE><BR>><DIV><FONT=3D20
> > size=3D3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight =3D
> >spam,=3D20
> > =3D
> =
>=3D3D<BR>>and=3D3D20<BR>>you?<BR><A=3D3D20<BR>>href=3D3D3D "<A=3D20
> > =3D
> =
>href=3D3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
> =
>'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=3D=
> >>=3D3D<BR>>.html</A>=3D20
> > =3D
> ></FONT></DIV></BODY></HTML><BR>><BR>><BR></=3D
> >BLOCKQUOTE></BODY></HTML>
> >
> >
------=_NextPart_000_003E_01C7C7D4.AF7A4AD0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I don't s'pose it could hurt if they're =
tarnished.=20
My experiences though with the issue your seeing have been bad SCSI =
cables.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Start small, test every little =
component, unless=20
you've got a bent up input pin somewhere (and I'd light them well and =
magnifying=20
lense them all) I'm having a hard time buying that you have 4 dead =
cables out of=20
the blue though, something caused that if it's the case. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>AA</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
<A href=3D"news:469b74bf@linux">news:469b74bf@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Aaron,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Hyperthreading is off. I'll =
double check=20
though. I'd love to save the money</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>on those scsi cables.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>What do you think about Deoxit in the =
female scsi=20
jacks?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Aaron Allen" <<A=20
=
href=3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>> =
wrote=20
in message <A =
href=3D"news:469aead6@linux">news:469aead6@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>This might be flogging =
the rented and=20
dead mule, but you did verify that dual core was off in this =
equation,=20
and hadn't been flipped back on by a gremlin?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>AA</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote in=20
message <A =
href=3D"news:469ad5e8@linux">news:469ad5e8@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Ya Jeff,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>At least half the times no C-16 =
was=20
attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Do you think that a bad C-16 =
cable could=20
cause these issues?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'll remove them from the setup =
until all is=20
well.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know at least a few =
times it=20
worked that the C-16 did also.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Jeff Hoover" <<A=20
href=3D"mailto:jkhoover@excite.com">jkhoover@excite.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:4699b378@linux">news:4699b378@linux</A>...</DIV>Tom,<BR><BR>=
Stupid=20
question, but did you ever start up without any c16's? If =
so did=20
<BR>you see the same issue?<BR><BR>Jeff<BR><BR><BR>Bruhl =
wrote:<BR>>=20
Rod,<BR>> I am working from a clone that was totally good =
with=20
two<BR>> fully loaded Mecs. I have to assume the =
drivers are=20
good.<BR>> I'm looking for a good vendor for SCSI cables =
now.<BR>>=20
They're called SCSI 2 right?<BR>> <A=20
=
href=3D"http://www.m2cables.com/SCSI2toSCSI2CablesHDB50MtoML6.html">http:=
//www.m2cables.com/SCSI2toSCSI2CablesHDB50MtoML6.html</A><BR >> =20
<BR>> I'm thinking of cleaning the female jacks on the mec =
and EDS to=20
be<BR>> sure all is well. Any sprays anyone =
suggests? =20
I've got Deoxit.<BR>> Good?<BR>> Tom<BR>>=20
<BR>> "Rod Lincoln" <<A=20
=
href=3D"mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com</A><B=
R>> =20
<<A=20
=
href=3D"mailto:rlincoln@nospam.kc.rr.com">mailto:rlincoln@nospam.kc.rr.co=
m</A>>>=20
wrote in message<BR>> <A=20
=
href=3D"news:4697f7e2$1@linux">news:4697f7e2$1@linux</A>...<BR>>=20
<BR>> Tom, sounds like it probably is =
a scsi=20
issue. Your running xp right?<BR>> =
The=20
new<BR>> Scherzo drivers are for xp =
verses 98=20
not for 3.0 verses 2.x<BR>> Come to =
think of=20
it. you probably whoudn't have had any old=20
drivers<BR>> on=20
your<BR>> xp sys drive anyway...never =
mind.<BR>> =20
Rod<BR>> "Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A> =
<<A=20
=
href=3D"mailto:arpegio@comcast.net">mailto:arpegio@comcast.net</A>>>=
;=20
wrote:<BR> > =2 0
><BR> > =2 0
><BR>> >Hey=20
Rod,<BR>> >Hiding the =
default=20
project didn't help anything. I've=20
never<BR>> >had 2.?? =
installed on=20
this comp so I think I'm safe there=20
regarding<BR> > &nbs
|
|
|
|
|
|
| Re: This is how FU'ed the US healthcare system is [message #87243 is a reply to message #87240] |
Tue, 26 June 2007 23:30   |
JeffH
 Messages: 307 Registered: October 2007 Location: Wamic, OR
|
Senior Member |
|
|
mp;gt; =2 0
>suspect<BR>> > =
>either=20
all my Mecs are screwy now or the SCSI cables=20
are<BR>> =20
intermitant<BR>> =20
=3D<BR> > =2 0
>at<BR>> > =20
=3D3D<BR>> > =20
>best.<BR>> > =
>It's=20
working fine with the 442 so I'm sticking with that for=20
today.<BR>> > >I'll =
add my=20
EDS cards one by one and see if that is back to=20
normal.<BR>> > =20
><BR>> > >Thanks =
for the=20
help and if I need scsi cables what and where=20
to<BR>> buy=20
=3D<BR> > =2 0
>them<BR>> > =20
=3D3D<BR>> > >would =
be good=20
info too.<BR>> > =
>Mr=20
Testy<BR>> > =
> "Rod=20
Lincoln" <<A=20
=
href=3D"mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com</A><B=
R>> =20
<<A=20
=
href=3D"mailto:rlincoln@nospam.kc.rr.com">mailto:rlincoln@nospam.kc.rr.co=
m</A>>>=20
wrote in message =3D3D<BR>> =
> =20
=
>news:469780ce$1@linux...<BR> > =2 0
> ><BR>> > =
> I think Tom was asking if there was a "3.0" version =
of=20
the<BR>> EDS=20
card<BR>> =20
=3D<BR> > =2 0
>=3D3D<BR>> > =
>that=20
needed<BR>> > =
> to be=20
connected to the master. The answer to that would=20
be<BR>> =20
no.=3D3D20<BR>> > =
> Is=20
this what you were asking =
Tom?<BR> > =2 0
> > DJ's advice is very important though. I =
would do=20
it, if you<BR>> =20
haven't<BR>> =20
=3D<BR> > =2 0
>=3D3D<BR>> > =20
>already.<BR>> > =
> =20
I don't want to sound like a "RTFM" kind of guy, but the Paris=20
=3D<BR> > =2 0
>manual<BR>> > =20
=3D3D<BR>> > =20
>describes<BR>> > =20
> this procedure pretty=20
well.<BR>> > =
> It's=20
on page 4 and 5 of the 3.0=20
version.<BR>> > =
> It=20
kind of sounds to me like you may not be hooking up=20
the<BR>> =20
correct<BR>> =20
=3D<BR> > =2 0
>eds<BR>> > =20
=3D3D<BR>> > =20
>card<BR>> > =
> to=20
the master mec.<BR>> > =
> Rod<BR>> > =20
> "DJ" <animix _ at _ animas _ dot _ net>=20
wrote:<BR>> > =
> =20
><BR>> > > =
><BR>> > > =
><BR>> > > =
> "Tom Bruhl" <<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A><BR>> =
=20
<<A=20
=
href=3D"mailto:arpegio@comcast.net">mailto:arpegio@comcast.net</A>>>=
;=20
wrote in message =3D3D3D<BR>> =
> =20
> =20
>news:46972376@linux...<BR>> =
> > > This is really a novice =
oriented=20
question but . . .<BR>> =
> =20
> > It doesn't matter which card is the "A"=20
card<BR>> > > =
> in your system as far as Paris' ID orientation=20
right?<BR>> > =
> =20
><BR>> > > =
> Yes, it does, and the orientation of the slots you=20
are<BR>> using=20
in<BR>> =20
=3D<BR> > =2 0
>=3D3D3D<BR>> > =
> =20
>combination with the orientation of the ribbon cables will=20
=3D<BR> > =2 0
>determine<BR>> > =20
=3D3D<BR>> > =20
>=3D3D3D<BR>> > =
> =20
>this. Have you changed them around during your=20
reconfiguration?<BR>> =
> =20
> ><BR>> > =
> > Start with a new SCSI cable and a single =
EDS card.=20
Test each =3D<BR>> >MEC.=20
=3D3D<BR>> > =20
>Once<BR>> > =
> =20
=3D3D3D<BR>> > =
> =20
>you know if there is a problem there, add a new SCSI=20
cable<BR>> and=20
=3D3D<BR>> > =
>another=20
=3D3D3D<BR>> > =
> =20
>card. Put different modules in the MECs so you can see=20
which<BR>> one=20
=3D<BR>> >is=20
=3D3D<BR>> > >on=20
=3D3D3D<BR>> > =
> =20
>card A, B, C at all times. this will give you the info as=20
to<BR>> how=20
=3D<BR> > =2 0
>the<BR>> > =20
=3D3D<BR>> > =20
>=3D3D3D<BR>> > =
> =20
>cards are initializing and which card is card A, B, C as=20
you<BR>> =20
start<BR>> =20
=3D<BR> > =2 0
>=3D3D<BR>> > =20
>=3D3D3D<BR>> > =
> =20
>adding more hardware. the MEC i sent you is one of 4=20
that<BR>> were=20
=3D3D<BR>> > =
>working=20
=3D3D3D<BR>> > =
> =20
>perfectly when I took my system off line. I can't imagine=20
it<BR>> =
being<BR>> =20
=3D<BR> > =2 0
>a<BR>> > =20
=3D3D<BR>> > =20
>=3D3D3D<BR>> > =
> =20
>problem. Bent pins on SCSI cables can be a serious=20
issue<BR>> though.=20
=3D<BR> > =2 0
>Your<BR>> > =20
=3D3D<BR>> > =20
>=3D3D3D<BR>> > =
> =20
>system will not function with bad SCSI=20
cables.<BR>> > =
> =20
><BR>> > > =
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0=20
Transitional//EN"><BR>> =
> =20
> =20
=
><HTML><HEAD><BR> > =2 0
> > ><META =
http-equiv=3D3D3D3DContent-Type=20
content=3D3D3D3D"text/html; =
=3D<BR> > =2 0
>=3D3D3D<BR>> > =
> =20
=
>charset=3D3D3D3Diso-8859-1"><BR>> =
=20
> > ><META content=3D3D3D3D"MSHTML=20
6.00.6000.16414"<BR>> =20
name=3D3D3D3DGENERATOR><BR>> =
> > =20
=
><STYLE></STYLE><BR> > =2 0
> > =20
></HEAD><BR>> =
> =20
> ><BODY=20
=
bgColor=3D3D3D3D#ffffff><BR> > =2 0
> > ><BLOCKQUOTE=20
dir=3D3D3D3Dltr=3D3D3D20<BR>> =
> =20
> >style=3D3D3D3D"PADDING-RIGHT: 0px; PADDING-LEFT:=20
5px;<BR>> MARGIN-LEFT:=20
=3D<BR>> >5px;=20
=3D3D<BR>> > =20
>=3D3D3D<BR>> > =
> =20
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT:=20
0px"><BR>> > =
> =20
> <DIV><FONT face=3D3D3D3DArial=20
size=3D3D3D3D2></FONT>=20
</DIV><BR>> > =
> =20
> <DIV>"Tom Bruhl"=20
<<A=3D3D3D20<BR>> =
> =20
> > <BR>> =
href=3D3D3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A><BR>> =
=20
<<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>><BR>> =
=20
=3D<BR> > =2 0
>=3D3D<BR>> > =
>wrote=20
=3D3D3D<BR>> > =
> >in=20
message=3D3D3D20<BR>> =
> =20
> > <A =
=3D<BR> > =2 0
>href=
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|