gN4NGe7kM93IDeDRnu5DPd [binary] XEkARsqVwypXEkARsqVwypXEkARsqVwypXEkARsqVwypXEkARsqVwypXEkAR sqVwypXEkARsqVwypXEkARsqVwypXEkARsqVwypXEkARsqVwypXEkARsqVwy [binary]
br /> [binary]
ml" target="_blank">http://www.m2cables.com/SCSI2toSCSI2CablesHDB50MtoML6.html > > > > I'm thinking of cleaning the female jacks on the mec and EDS to be > > sure all is well. Any sprays anyone suggests? I've got Deoxit. > > Good? > > Tom > > > > "Rod Lincoln" <rlincoln@nospam.kc.rr.com > <mailto:rlincoln@nospam.kc.rr.com> > > <mailto:rlincoln@nospam.kc.rr.com>> wrote in message > > news:4697f7e2$1@linux... > > > > Tom, sounds like it probably is a scsi issue. Your running xp > right? > > The new > > Scherzo drivers are for xp verses 98 not for 3.0 verses 2.x > > Come to think of it. you probably whoudn't have had any old > drivers > > on your > > xp sys drive anyway...never mind. > > Rod > > "Tom Bruhl" <arpegio@comcast.net <mailto:arpegio@comcast.net> > <mailto:arpegio@comcast.net>> wrote: > > > > > > > > >Hey Rod, > > >Hiding the default project didn't help anything. I've never > > >had 2.?? installed on this comp so I think I'm safe there > regarding > > >drivers. > > > > > >I am only able to intermitantly get the 442 working as the > master. > > >I think that's do to the scsi cable issue. I need four new > ones. > > >I am unable to get more than one EDS card working WITH the 442. > > >Not sure why. The ribbons are all wired correctly. > > > > > >I'm off to a hellish gigging weekend. No more time for > hell in Paris. > > >Thanks for all your input, > > >Tom > > > "Rod Lincoln" <rlincoln@nospam.kc.rr.com > <mailto:rlincoln@nospam.kc.rr.com> > > <mailto:rlincoln@nospam.kc.rr.com>> wrote in message = > > >news:4697ab8a@linux... > > > > > > Did you try hiding the default ppj to see if it would boot up > > with a = > > >MEC when > > > creating a new session?=20 > > > Rod > > > "Tom
0 >cables are intermitant at=20 > > > best. > > >face=3D3DArial=20 > > > size=3D3D2>It's working fine with the 442 so I'm = > > >=3D >sticking=20 > > > with=3D20 >that for=20 > > > today. > > >face=3D3DArial=20 > > > size=3D3D2>I'll add my EDS cards one by one and > =3D >see if = > > >that=20 > > > is=3D20 >back to=20 > > > normal. > > >face=3D3DArial=20 > > > size=3D3D2> > > >face=3D3DArial=20 > > > size=3D3D2>Thanks for the help and if I need = > > >scsi =3D >cables=20 > > > what=3D20 >and where to buy them would be good info=20 > > > too. > > >face=3D3DArial=20 > > > size=3D3D2>Mr=20 > > > = > > >Testy ><BLOCKQUOTE=3D20 >style=3D= > > >3D"PADDING-RIGHT:=20 > > > 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; > =3D >BORDER-LEFT: = > > >#000000 2px=20 > > > solid; MARGIN-RIGHT: 0px"> > "Rod Lincoln"=20 > > > <<A=3D20 > =3D >href=3D3D"<A=20 > > > = > > > >href=3D'mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com&a= > > > >mp;g'>mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com</= > > >A>&g=3D >t;=3D20 > =20 > > > wrote in message <A=3D20 > href=3D3D"<A=20 > > > = > > > >href=3D'news:469780ce$1@linux">news:469780ce$1@linux... I'>n= > > >ews:469780ce$1@linux">news:469780ce$1@linux... &l= > > >t;BR>I =3D >think=20 > > > Tom=3D20 > was asking if there was a "3.0" version of > the = > > >EDS card=20 > > > that =3D >needed to be=3D20 > connected to = > > >the master.=20 > > > The answer to that would be no. Is this =3D >what=20 > > > you=3D20 > were asking Tom? DJ's advice is very = > > >important=20 > > > though. I would do =3D >it, if=3D20 > you haven't=20 > > > already. I don't want to sound like a "RTFM" kind of = > > >=3D >guy,=20 > > > but=3D20 > the Paris manual describes this = > > >procedure pretty=20 > > > well. It's on =3D >page 4=3D20 > and 5 of = > > >the 3.0=20 > > > version. It kind of sounds to me like you may=20 > > > not =3D >be=3D20 > hooking up the correct eds=20 > > > card to the master = > > >mec. Rod "DJ"=3D20 > =20 > > > <animix _ at _ animas _ dot _ net>=3D20 > =20 > > > wrote: > > > > "Tom = > > >Bruhl"=20 > > > <<A=3D20 > href=3D3D"<A=20 > > > = > > > >href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi= > > >o@comcast.net"><a href="mailto:arpegio@comcast.net" targ
>novice oriented=3D20 > question but . . = > > >. > It=20 > > > doesn't matter which card is the =3D >"A"=3D20 > =20 > > > card > in your system as far as Paris' ID=20 > > > orientation=3D20 > right? > > Yes, = > > >it does,=20 > > > and the orientation of the =3D >slots=3D20 > you are = > > >using in=20 > > > =3D3D >combination with the orientation of the=20 > > > =3D >ribbon=3D20 > cables will determine = > > >=3D3D >this.=20 > > > Have you changed them around =3D >during your=3D20 > = > > > > > > reconfiguration? > > Start with a new SCSI = > > >cable and=20 > > > =3D >a=3D20 > single EDS card. Test each MEC.=20 > > > Once =3D3D >you know if there =3D >is=20 > > > a=3D20 > problem there, add a new SCSI cable and > another=20 > > > =3D3D >card. Put =3D >different=3D20 > = > > >modules in the=20 > > > MECs so you can see which one is on =3D3D >card A, = > > >=3D >B, C=20 > > > at=3D20 > all times. this will give you the info as to > how = > > >the=20 > > > =3D3D >cards =3D >are=3D20 > = > > >initializing and which=20 > > > card is card A, B, C as you start =3D >=3D3D >adding = > > > > > > more=3D20 > hardware. the MEC i sent you is one of 4 > that = > > >were=20 > > > working =3D >=3D3D >perfectly=3D20 > = > > >when I took my=20 > > > system off line. I can't imagine it being a=20 > > > =3D >=3D3D >problem.=3D20 > Bent pins on = > > >SCSI cables=20 > > > can be a serious issue though. Your=20 > > > =3D >=3D3D >system=3D20 > will not = > > >function with bad=20 > > > SCSI cables. > > > > =3D >HTML=3D20 > PUBLIC "-//W3C//DTD HTML = > > >4.0=3D20 > =20 > > > = > > >Transitional//EN"> > >= > > ><META=3D20 > =20 > > > http-equiv=3D3D3DContent-Type = > > >content=3D3D3D"text/html;=3D20 > =20 > > > =3D3D >charset=3D3D3Diso-8859-1"> > > > > > > =3D >content=3D3D3D"MSHTML=3D20 > =20 > > > 6.00.6000.16414"=3D20 > =20 > > > = > > >=3D >name=3D3D3DGENERATOR> > </STYLE&= > > >gt; ></HEA=3D >D> ><BODY=3D20 &= > > >gt; =20 > > > = > > >bgColor=3D3D3D#ffffff> ><BLOCKQUOTE=3D20 > = > > > > > > dir=3D3D3Dltr=3D3D20 >style=3D3D3D"PADDING-RIGHT: 0px; = > > >PADDING-LEFT:=20 > > > =3D >5px;=3D20 > MARGIN-LEFT: 5px; = > > >=3D3D >BORDER-LEFT:=20 > > > #000000 2px solid; =3D >MARGIN-RIGHT:=3D20 > =20 > > > 0px"> > > >face=3D3D3DArial=3D20 > =20 > > > size=3D3D3D2> > = > > > "Tom=20 > > > =3D >Bruhl"=3D20 > <<A=3D3D20 >=20 > > > href=3D3D3D"<A=3D20 > =20 > > > = > > > >=3D >href=3D3D'mailto:arpegio@comcast.net">arpegio@comcast.net&l= > > >t;/A'>mailto:arpegi=3D >o@comcast.net">arpegio@comcast.net<= > > >;/A>>=3D20 > =20 > > > wrote =3D3D >in message=3D3D20 > <A=20 > > > href=3D3D3D"<A=3D20 > =20 &
> > > > > > > >=3D3D3D > > > >charset=3D3D3D3Diso-8859-1"> > > > > name=3D3D3D3DGENERATOR> > > > > > > > > > > > > > > > > > > >style=3D3D3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; > MARGIN-LEFT: =3D > >5px; =3D3D > > >=3D3D3D > > > >BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> > > > > = > > > > "Tom Bruhl" <<A=3D3D3D20 > > > >=20 > = href=3D3D3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net <mailto:arpegio@comcast.net">arpegio@comcast.net>> > =3D > >=3D3D > > >wrote =3D3D3D > > > >in message=3D3D3D20 > > > > = >href=3D3D3D3D"news:46972376@linux">news:46972376@linux... <news:46972376@linux">news:46972376@linux... > > > > > This is = really a > novice > =3D > >=3D3D > > >oriented =3D3D3D > > > >question but . .=3D3D3D20 > > > > . > > > > It = doesn't matter > which > =3D > >card =3D3D > > >is the =3D3D3D > > > >"A"=3D3D3D20 > > > > card > > > > in your = system as > far =3D > >as =3D3D > > >Paris' ID =3D3D3D > > > >orientation=3D3D3D20 > > > > right? > > > > = > > > > > > > > Yes, it = does, and > the =3D > >=3D3D > > >orientation of > > > =3D3D3D > > > >the slots=3D3D3D20 > > > > you are using in combination with the orientation of = the =3D3D > > >ribbon=3D3D3D20 > > > > cables will determine this. Have you changed them = around > during > =3D > >=3D3D3D > > > >your=3D3D3D20 > > > > reconfiguration? > > > > = > > > > Start = with a new > SCSI =3D > >cable =3D3D > > >and a =3D3D3D > > > >single EDS=3D3D3D20 > > > > card. Test each MEC. Once you know if there is a = problem > there, > =3D > >add > > =3D3D > > >a > > > =3D3D3D > > > >new SCSI=3D3D3D20 > > > > cable and another card. Put different modules in the = MECs > so you > =3D > >=3D3D > > >can =3D3D3D > > > >see which=3D3D3D20 > > > > one is on card A, B, C at all times. this will give = you > the info > =3D > >=3D3D > > >=3D3D3D > > > >as to=3D3D3D20 > > > > how the cards are initializing and which card is = card A, > B, C as > =3D > >=3D3D > > >you =3D3D3D > > > >start=3D3D3D20 > > > > adding more hardware. the MEC i sent you is one of 4 = that > were =3D > >=3D3D > > >working > > > =3D3D3D > > > > > > > > perfectly when I took my system off line. I can't = imagine it =3D > >being > > =3D3D > > >a =3D3D3D > > > >problem.=3D3D3D20 > > > > Bent pins on SCSI cables can be a serious issue = though. Your =3D > >system > > =3D3D > > >=3D3D3D > > > >will not=3D3D3D20 > > > > f
unction with bad SCSI =3D3D3D > > > >cables. > > > > > > > > > > > > > > > > > > > >I choose Polesoft Lockspam to fight spam, and you? > > >http://www.polesoft.com/refer.html =3D20 > > > > > > > > > > > > > >charset=3D3D3Diso-8859-1"> > > > > > > > > > > > > > > > Guys, > > > I'm all set with = the > cables and > =3D > >the =3D3D > > >which card is A=3D3D20 > > >bit. > > > Rod you were = right about > what I > =3D > >was=3D3D20 > > >asking. > > > > > > In any event I = scaled down > to =3D > >one EDS =3D3D > > >(Pretty sure=3D3D20 > > >that's card A right?!!!) > > > and plugged it = into each > of my =3D > >two =3D3D > > >working=3D3D20 > > >Mecs. Paris will boot but > > > even internal = clock was > never =3D > >found nor > > =3D3D > > >were the=3D3D20 > > >in/outs on each Mec. > > > The 442 on the = other hand > works > =3D > >like a > > =3D3D > > >champ one=3D3D20 > > >card only. I suspect > > > either all my = Mecs are > screwy =3D > >now or =3D3D > > >the SCSI=3D3D20 > > >cables are intermitant at best. > > > It's working = fine with the > 442 =3D > >so I'm =3D3D > > >sticking with=3D3D20 > > >that for today. > > > I'll add my EDS = cards one > by one > =3D > >and =3D3D > > >see if that is=3D3D20 > > >back to normal. > > > > > > Thanks for the = help and if I =3D > >need scsi > > =3D3D > > >cables what=3D3D20 > > >and where to buy them would be good info = too. > > > Mr = Testy > > ><BLOCKQUOTE=3D3D20 > > >style=3D3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; = MARGIN-LEFT: > 5px; =3D > >=3D3D > > >BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> > > > "Rod Lincoln" <<A=3D3D20 > > > =3D3D > > =3D > = >>href=3D3D3D"mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com= = <mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com=3D > >>&g=3D3D > > >t;=3D3D20 > > > wrote in message <A=3D3D20 > > > =3D > = >href=3D3D3D"news:469780ce$1@linux">news:469780ce$1@linux... <BR= >I > = <news:469780ce$1@linux">news:469780ce$1@linux... I> > > =3D3D > > >think Tom=3D3D20 > > > was asking if there was a "3.0" version of the EDS card = that =3D3D > > >needed to be=3D3D20 > > > connected to the master. The answer to that would be = no. Is =3D > >this =3D3D > > >what you=3D3D20 > > > were asking Tom? DJ's advice is very important = though. I > would =3D > >do =3D3D > > >it, if=3D3D20 > > > you haven't already. I don't want to sound like a = "RTFM" > kind of > =3D > >=3D3D > > >guy, but=3D3D20 > > > the Paris manual describes this procedure pretty > well. It's =3D > >on =3D3D > > >page 4=3D3D20 > > > and 5 of the 3.0 version. It kind of sounds to me = like you > may =3D > >not > > =3D3D > > >be=3D3D20 > > > hooking up the correct eds card to the master =3D > >mec. Rod "DJ"=3D3D20 > > > <animix _ at _ animas _ dot _ net>=3D3D20 > > > wrote: > > > > "Tom Bruhl" <<A=3D3D20 > > > = href=3D3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net <mailto:arpegio@comcast.net">arpegio@comcast.net>> =3D > >wrote =3D3D > > >in message=3D3D20 > > > =3D3D3D >news:46972376@linux... > This is really = a =3D3D > > >novice oriented=3D3D20 > > > question but . . . > It doesn't matter which card is = the =3D3D > > >"A"=3D3D20 > > > card > in your system as far as Paris' ID = orientation=3D3D20 > > > right? > > Yes, it does, and the orientation of = the =3D3D > > >slots=3D3D20 > > > you are using in =3D3D3D >combination with the = orientation > of the > =3D > >=3D3D > > >ribbon=3D3D20 > > > cables will determine =3D3D3D >this. Have you = changed them > around > =3D > >=3D3D > > >during your=3D3D20 > > > reconfiguration? > > Start with a new SCSI cable = and =3D3D > > >a=3D3D20 > > > single EDS card. Test each MEC. Once =3D3D3D >you = know if > there > =3D > >=3D3D > > >is a=3D3D20 > > > problem there, add a new SCSI cable and another > =3D3D3D >card. Put > =3D > >=3D3D > > >different=3D3D20 > > > modules in the MECs so you can see which one is on > =3D3D3D >card =3D > >A, =3D3D > > >B, C at=3D3D20 > > > all times. this will give you the info as to how the = =3D > >=3D3D3D >cards =3D3D > > >are=3D3D20 > > > initializing and which card is card A, B, C as you = start =3D3D > > >=3D3D3D >adding more=3D3D20 > > > hardware. the MEC i sent you is one of 4 that were = working =3D3D > > >=3D3D3D >perfectly=3D3D20 > > > when I took my system off line. I can't imagine it = being a =3D3D > > >=3D3D3D >problem.=3D3D20 > > > Bent pins on SCSI cables can be a serious issue though. = Your =3D3D > > >=3D3D3D >system=3D3D20 > > > will not function with bad SCSI = cables. > > > >HTML=3D3D20 > > > PUBLIC "-//W3C//DTD HTML 4.0=3D3D20 > > > Transitional//EN"> > ><META=3D3D20 > > > http-equiv=3D3D3D3DContent-Type = content=3D3D3D3D"text/html;=3D3D20 > > > =3D3D3D >charset=3D3D3D3Diso-8859-1"> > > >content=3D3D3D3D"MSHTML=3D3D20 > > > 6.00.6000.16414"=3D3D20 > > > =3D3D > > = >name=3D3D3D3DGENERATOR> > ></HEA=3D3D > > >D> ><BODY=3D3D20 > > > bgColor=3D3D3D3D#ffffff> ><BLOCKQUOTE=3D3D20 > > > = dir=3D3D3D3Dltr=3D3D3D20 >style=3D3D3D3D"PADDING-RIGHT: 0px; =3D > >PADDING-LEFT: =3D3D > > >5px;=3D3D20 > > > MARGIN-LEFT: 5px; =3D3D3D >BORDER-LEFT: #000000 2px = solid; =3D3D > > >MARGIN-RIGHT:=3D3D20 > > > 0px"> > > > size=3D3D3D3D2> > "Tom =3D3D > > >Bruhl"=3D3D20 > > > <<A=3D3D3D20 > 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>=3D3D20 > > > wrote =3D3D3D >in message=3D3D3D20 > <A = href=3D3D3D3D"<A=3D3D20 > > > =3D3D > > =3D > = >>href=3D3D3D'news:46972376@linux">news:46972376@linux...</DIV'>news:= 469=3D > >723=3D3D > > = >76@linux">news:46972376@linux... >&nbs=3D3D > > >p;=3D3D20 > > > This is = really a =3D3D > > >novice oriented=3D3D20 > > > =3D3D3D >question but . .=3D3D3D20 > =3D3D20 > > > . > > >face=3D3D3D3DArial=3D3D20 > > > size=3D3D3D3D2>It doesn't matter which card is the = =3D3D > > >=3D3D3D >"A"=3D3D3D20 > =3D3D20 > > > card > > >face=3D3D3D3DArial=3D3D20 > > > size=3D3D3D3D2>in your system as far as Paris' = ID=3D3D20 > > > =3D3D3D >orientation=3D3D3D20 > =3D3D20 > > > right? > > >face=3D3D3D3DArial=3D3D20 > > > size=3D3D3D3D2> > =3D3D > > > > =3D3D20 > > > Yes, it = does, and > the =3D3D > > >orientation=3D3D20 > > > of =3D3D3D >the slots=3D3D3D20 > you are using = in =3D3D > > >combination with=3D3D20 > > > the orientation of the ribbon=3D3D3D20 > cables will > determine =3D3D > > >this.=3D3D20 > > > Have you changed them around during > =3D3D3D >your=3D3D3D20 > =3D3D > > > > > > reconfiguration? > =3D3D > > > <FONT=3D3D20 > > > face=3D3D3D3DArial size=3D3D3D3D2> > = =3D3D20 > > > Start with = a new > SCSI =3D3D > > >cable and a=3D3D20 > > > =3D3D3D >single EDS=3D3D3D20 > card. Test each = MEC. Once > you =3D3D > > >know if=3D3D20 > > > there is a problem there, add a =3D3D3D >new = =3D3D > > >SCSI=3D3D3D20 > cable=3D3D20 > > > and another card. Put different modules in the MECs so = you > can =3D3D > > >=3D3D3D >see=3D3D20 > > > which=3D3D3D20 > one is on card A, B, C at all = times. this =3D3D > > >will give you=3D3D20 > > > the info =3D3D3D >as to=3D3D3D20 > how the cards = are =3D3D > > >initializing and=3D3D20 > > > which card is card A, B, C as you = =3D3D3D >start=3D3D3D20 > =3D3D > > >adding more=3D3D20 > > > hardware. the MEC i sent you is one of 4 that = were=3D3D20 > > > working =3D3D3D > > perfectly when I took my = system =3D3D > > >off line. I=3D3D20 > > > can't imagine it being a = =3D3D3D >problem.=3D3D3D20 > Bent =3D3D > > >pins on SCSI=3D3D20 > > > cables can be a serious issue though. Your system =3D > >=3D3D3D >will=3D3D20 > > > not=3D3D3D20 > function with bad SCSI=3D3D20 > > > =3D3D > > >=3D3D3D >cables. =3D3D > > >; > > > > > I choose Polesoft = Lockspam to fight =3D > >spam, =3D3D > > >and=3D3D20 > > >you? <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 > > > > > > > > > > > > > > > > >charset=3D3Diso-8859-1"> > > > > > > > > > > Hey Rod, > > Hiding the default = project didn't > help=3D20 > >anything. I've never > > had 2.?? installed on = this comp > so I =3D > >think I'm safe=3D20 > >there regarding > > drivers. > > > > I am only able to = intermitantly > get the > =3D > >442 working=3D20 > >as the master. > > I think that's do to = the scsi cable =3D > >issue. I=3D20 > >need four new ones. > > I am unable to get more = than one > EDS =3D > >card working=3D20 > >WITH the 442. > > <FONT
"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&g>=3D > >t;=3D20 > > wrote in message <A=3D20 > >=20 > = href=3D3D"news:4697ab8a@linux">news:4697ab8a@linux... Did > <news:4697ab8a@linux">news:4697ab8a@linux... Did> = =3D > >you try=3D20 > > hiding the default ppj to see if it would boot up with a = MEC =3D > >when creating=3D20 > > a new session? Rod "Tom Bruhl" <<A=3D20 > > = href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net>=3D20 &g
=20 "Tom Bruhl" <arpegio@comcast.net=20 <<A=20 = href=3D"mailto:arpegio@comcast.net">mailto:arpegio@comcast.net>&gt= ;=20 wrote: > =2 0 > > =2 0 > > >Hey=20 Rod, > >Hiding the default = project=20 didn't help anything. I've = never > =2 0 >had 2.?? installed on this comp so I think I'm safe there=20 regarding > =2 0 >drivers. > =2 0 > > >I am only able to=20 intermitantly get the 442 working as the=20 master. > >I think that's do = to the=20 scsi cable issue. I need four new=20 ones. > >I am unable to get = more than=20 one EDS card working WITH the = 442. > =2 0 >Not sure why. The ribbons are all wired=20 correctly. > =2 0 > > >I'm off to a hellish = gigging=20 weekend. No more time for hell in=20 Paris. > >Thanks for all your = input, > =2 0 >Tom > > "Rod = Lincoln"=20 <<A=20 = href=3D"mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com<B= R>> =20 <<A=20 = href=3D"mailto:rlincoln@nospam.kc.rr.com">mailto:rlincoln@nospam.kc.rr.co= m>>=20 wrote in message =3D > =2 0 >news:4697ab8a@linux... > =2 0 > > > Did you try = hiding the=20 default ppj to see if it would boot = up > with=20 a =3D > >MEC=20 when > > creating a new = session?=3D20 > > =20 Rod > > "Tom Bruhl" = <<A=20 href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net <<A=20 = href=3D"mailto:arpegio@comcast.net">mailto:arpegio@comcast.net>&gt= ; > =20 wrote: > > =20 > > > =20 > > > =20 >Guys, > > >I'm = all set=20 with the cables and the which card is A=20 bit. > > >Rod you = were right=20 about what I was asking. > = > =20 > > > >In any = event I=20 scaled down to one EDS (Pretty sure that's=20 card > A=20 =3D3D > > =20 >right?!!!) > > = >and=20 plugged it into each of my two working Mecs. Paris=20 will > boot=20 but > > >even = internal clock=20 was never found nor were the in/outs = on > each=20 Mec. > > >The 442 on = the=20 other hand works like a champ one card only. I=20 =3D > =2 0 >suspect > > = >either all=20 my Mecs are screwy now or the SCSI cables=20 are > =20 intermitant > =20 =3D > =2 0 >at > > =20 =3D3D > > =20 >best. > > >It's = working=20 fine with the 442 so I'm sticking with that for=20 today. > > >I'll add = my EDS=20 cards one by one and see if that is back to=20 normal. > > =20 > > > >Thanks for = the=20 help and if I need scsi cables what and where=20 to > buy=20 =3D > =2 0 >them > > =20 =3D3D > > >would be = good info=20 too. > > >Mr=20 Testy > > > = "Rod=20 Lincoln" <<A=20 = href=3D"mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com<B= R>> =20 <<A=20 = href=3D"mailto:rlincoln@nospam.kc.rr.com">mailto:rlincoln@nospam.kc.rr.co= m>>=20 wrote in message =3D3D > = > =20 >news:469780ce$1@linux... > =2 0 > > > > = > =20 I think Tom was asking if there was a "3.0" version of=20 the > EDS = card > =20 =3D > =2 0 >=3D3D > > >that=20 needed > > > = to be=20 connected to the master. The answer to that would=20 be > =20 no.=3D3D20 > > = > Is this=20 what you were asking Tom? > = > =20 > DJ's advice is very important though. I would do it, if=20 you > = haven't > =20 =3D > =2 0 >=3D3D > > =20 >already. > > = > I=20 don't want to sound like a "RTFM" kind of guy, but the Paris=20 =3D > =2 0 >manual > > =20 =3D3D > > =20 >describes > > = > =20 this procedure pretty well. > = > =20 > It's on page 4 and 5 of the 3.0=20 version. > > > = It kind=20 of sounds to me like you may not be hooking up=20 the > = correct > =20 =3D > =2 0 >eds > > =20 =3D3D > > =20 >card > > > = to the=20 master mec. > > = > =20 Rod > > > "DJ" = <animix _ at _ animas _ dot _ net>=20 wrote: > > > =20 > > > > =20 > > > > =20 > > > > = > =20 "Tom Bruhl" <<A=20 = href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net > = =20 <<A=20 = href=3D"mailto:arpegio@comcast.net">mailto:arpegio@comcast.net>&gt= ;=20 wrote in message =3D3D3D > = > =20 > = >news:46972376@linux... > =2 0 > > > This is really a novice oriented = question=20 but . . . > > = > =20 > It doesn't matter which card is the "A"=20 card > > > = > =20 in your system as far as Paris' ID orientation=20 right? > > > =20 > > > > = > =20 Yes, it does, and the orientation of the slots you=20 are > using = in > =20 =3D > =2 0 >=3D3D3D > > = > =20 >combination with the orientation of the ribbon cables will=20 =3D > =2 0 >determine > > =20 =3D3D > > =20 >=3D3D3D > > = > =20 >this. Have you changed them around during your=20 reconfiguration? > > = > =20 > > > > = > =20 Start with a new SCSI cable and a single EDS card. Test each=20 =3D > >MEC.=20 =3D3D > > =20 >Once > > > = =3D3D3D > > > = >you=20 know if there is a problem there, add a new SCSI=20 cable > and=20 =3D3D > > >another=20 =3D3D3D > > > = >card.=20 Put different modules in the MECs so you can see=20 which > one=20 =3D > >is=20 =3D3D > > >on=20 =3D3D3D > > > = >card=20 A, B, C at all times. this will give you the info as=20 to > how=20 =3D > =2 0 >the > > =20 =3D3D > > =20 >=3D3D3D > > = > =20 >cards are initializing and which card is card A, B, C as=20 you > = start > =20 =3D > =2 0 >=3D3D > > =20 >=3D3D3D > > = > =20 >adding more hardware. the MEC i sent you is one of 4=20 that > were=20 =3D3D > > >working=20 =3D3D3D > > > =20 >perfectly when I took my system off line. I can't imagine=20 it > = being > =20 =3D > =2 0 >a > > =20 =3D3D > > =20 >=3D3D3D > > = > =20 >problem. Bent pins on SCSI cables can be a serious=20 issue > though.=20 =3D > =2 0 >Your > > =20 =3D3D > > =20 >=3D3D3D > > = > =20 >system will not function with bad SCSI=20 cables. > > > =20 > > > > =20 > > = > =20 > =20 > > =2 0 > > > =2 0 >=3D3D3D > > = > =20 = >charset=3D3D3D3Diso-8859-1"> > = =20 > > > =20 name=3D3D3D3DGENERATOR> > = > =20 > =20 = > > =2 0 > > =20 > > > =20 > ><BODY=20 bgColor=3D3D3D3D#ffffff> > = > =20 > ><BLOCKQUOTE=20 dir=3D3D3D3Dltr=3D3D3D20 > = > =20 > >style=3D3D3D3D"PADDING-RIGHT: 0px; PADDING-LEFT:=20 5px; > MARGIN-LEFT:=20 =3D > >5px;=20 =3D3D > > =20 >=3D3D3D > > = > =20 >BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT:=20 0px"> > > > = >&am