Home » The PARIS Forums » PARIS: Main » I think I found my problem
|
|
|
|
|
|
|
|
| Re: I think I found my problem [message #90133 is a reply to message #90132] |
Fri, 21 September 2007 18:16   |
Neil
Messages: 1645
Registered: April 2006
|
Senior Member |
|
|
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine when I pulled
=
>it from the rack.=20
>
>I've noticed a few posts recently regarding errors. Maybe no more than =
>usual, but it seemed like an unusually high number to me over the last =
>few weeks. Errors I'm not familiar with. It will have been 10 years in =
>November since Paris shipped. I wonder if the lifespan of this hardware
=
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html
>
><!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.16525" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial size=3D2>Tom,</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>Do you think the one I sent was =
>bad ?=20
></FONT><FONT face=3DArial size=3D2>It was working fine when I pulled it
=
>from the=20
>rack. </FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>I've noticed a few posts recently =
>regarding errors.=20
>Maybe no more than usual, but it seemed like an unusually high number to
=
>me over=20
>the last few weeks. Errors I'm not familiar with. It will have been =
>10=20
>years in November since Paris shipped. I wonder if the lifespan of this
=
>hardware=20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>Deej</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:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3DArial size=3D2>3 bad mecs.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>I'll know for a fact next Tuesday =
>when=20
> there's</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>time to test a couple on another=20
> system.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam,
=
>and=20
> you?<BR><A=20
> =
>href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
|
|
|
|
| Re: I think I found my problem [message #90136 is a reply to message #90133] |
Fri, 21 September 2007 18:35 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_006A_01C7FC97.5E61D6C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until Tuesday=20
when I'll check the two that might 'still work'. The hardware solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a 442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris freaked
and I went through days of turmoil looking to get back to where
I was. Paris refused to boot with mecs and no 442 at that time.
Next I built another comp to test eds and cables and the 442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never got a=20
good Paris boot. Every time it wouldn't boot there was a Mec attached.
Even the 442 boots were flakey (no patchbay connections). I didn't =
learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's mec
and the 442. We used the mec throughout all testing until the end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and Paris
would not boot with my other Mec that is loaded to the gills. I deleted
the Scherzo drivers, reloaded the new ones I just got, uninstalled the
subsystem and reloaded it. Once I changed to the 442 the system was =
fine.
Let me rephrase "Paris would not boot" . . . Actually it would usually =
start
up but no audio was available in the patchbay except with the 442.
My take is that the introduction of DJ's mec (whether it worked or =
didn't,
let's assume that it worked) was screwy probably by my own doing. I
removed it and later shorted a SCSI 2 cable at the Master Mec sometime =
during that
next week. There was smoke in the power supply area so I never tried =
that
Mec again. My other mec was attached at that time. I now think it =
fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio on =
Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine when I =
pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe no more =
than =3D
>usual, but it seemed like an unusually high number to me over the =
last =3D
>few weeks. Errors I'm not familiar with. It will have been 10 years =
in =3D
>November since Paris shipped. I wonder if the lifespan of this =
hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I sent was =
=3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine when I =
pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts =
recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually high number =
to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will have been =
=3D
>10=3D20
>years in November since Paris shipped. I wonder if the lifespan of =
this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact next =
Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to fight =
spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_006A_01C7FC97.5E61D6C0
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Intersted people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is unlikely. =
It's not=20
confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two </FONT><FONT =
face=3DArial=20
size=3D2>that might 'still work'. The hardware =
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most logical at =
this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with 2 mecs =
loaded to the=20
gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and bought one =
from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding my =
default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of turmoil =
looking to get=20
back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to boot with =
mecs and no=20
442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to test eds =
and cables=20
and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the studio with =
both=20
computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every time it =
wouldn't boot=20
there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey (no =
patchbay=20
connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs place with =
the Paris=20
comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used the mec =
throughout all=20
testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris =
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was introduced Paris =
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not =
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my original C =
drive (no=20
default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my other Mec =
that is=20
loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded the new =
ones I just=20
got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded it. Once I =
changed to=20
the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would not boot" =
.. . . =20
Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available in the =
patchbay=20
except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the introduction of =
DJ's mec=20
(whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own doing. =
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted a SCSI 2 =
cable at the=20
Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was smoke in the =
power=20
supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My other mec was =
attached at=20
that time. I now think it fried something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my hopefully =
unfried mec at=20
another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If I'm wrong =
then we're=20
back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In =
all=20
seriousness - THREE bad MEC's??? What's the real<BR>likelihood of =
that? Unless=20
all 3 PSU's got hit hard with a<BR>voltage spike or something weird =
like that,=20
is it really<BR>possible that ALL of his MECs went=20
bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at _ animas _ dot _ =
net>=20
wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you think the one =
I sent=20
was bad ? It was working fine when I pulled<BR>=3D<BR>>it from the=20
rack.=3D20<BR>><BR>>I've noticed a few posts recently regarding =
errors.=20
Maybe no more than =3D<BR>>usual, but it seemed like an unusually =
high number=20
to me over the last =3D<BR>>few weeks. Errors I'm not familiar =
with. It will=20
have been 10 years in =3D<BR>>November since Paris shipped. I =
wonder if the=20
lifespan of this hardware<BR>=3D<BR>>is starting to fade. TG for =
TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
=3D<BR>>news:46f44c75$1@linux...<BR>> 3 bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll know for =
a fact=20
next Tuesday when there's<BR>> time to test a couple on =
another=20
system.<BR>><BR>><BR>><BR>> <BR>> I choose =
Polesoft=20
Lockspam to fight spam, and you?<BR>> <A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0=20
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT =
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>Do you think the one I sent was =
=3D<BR>>bad=20
?=3D20<BR>></FONT><FONT face=3D3DArial size=3D3D2>It =
was working fine=20
when I pulled it<BR>=3D<BR>>from the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2>I've noticed a few posts recently =3D<BR>>regarding=20
errors.=3D20<BR>>Maybe no more than usual, but it seemed like an =
unusually=20
high number to<BR>=3D<BR>>me over=3D20<BR>>the last few weeks. =
Errors I'm=20
not familiar with. It will have been =3D<BR>>10=3D20<BR>>years =
in November=20
since Paris shipped. I wonder if the lifespan of=20
this<BR>=3D<BR>>hardware=3D20<BR>>is starting to fade. TG for =
TheSoniq, I=20
guess.</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT =
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: =
5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl" =
<<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>> =
<DIV><FONT=20
face=3D3DArial =
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial =
size=3D3D2>I'll=20
know for a fact next Tuesday =3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20<BR>> =20
system.</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> </DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam to fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =
you?<BR><A=3D20<BR>> =20
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_006A_01C7FC97.5E61D6C0--
|
|
|
|
| Re: I think I found my problem [message #90137 is a reply to message #90136] |
Fri, 21 September 2007 18:44 |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_00DF_01C7FC87.E3E2E1F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
WOW!!!........man........I'm sorry you're having to go through this kind =
of grief Tom. I hope it wasn't the MEC I sent you. Was that the one with =
the black gaffers tape holding the bottom plate? If so, it's not my =
fault. I got it from Rick. ;oD
Seriously, I am bummed out for you. there's norhting worse than having =
to deal with this kinda' stuff, IMO. You have my permission to use the =
MEC for target practice if that will help.
;o(
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until Tuesday=20
when I'll check the two that might 'still work'. The hardware =
solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a 442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris freaked
and I went through days of turmoil looking to get back to where
I was. Paris refused to boot with mecs and no 442 at that time.
Next I built another comp to test eds and cables and the 442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never got a=20
good Paris boot. Every time it wouldn't boot there was a Mec =
attached.
Even the 442 boots were flakey (no patchbay connections). I didn't =
learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's mec
and the 442. We used the mec throughout all testing until the end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and Paris
would not boot with my other Mec that is loaded to the gills. I =
deleted
the Scherzo drivers, reloaded the new ones I just got, uninstalled the
subsystem and reloaded it. Once I changed to the 442 the system was =
fine.
Let me rephrase "Paris would not boot" . . . Actually it would =
usually start
up but no audio was available in the patchbay except with the 442.
My take is that the introduction of DJ's mec (whether it worked or =
didn't,
let's assume that it worked) was screwy probably by my own doing. I
removed it and later shorted a SCSI 2 cable at the Master Mec sometime =
during that
next week. There was smoke in the power supply area so I never tried =
that
Mec again. My other mec was attached at that time. I now think it =
fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio on =
Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine when I =
pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe no more =
than =3D
>usual, but it seemed like an unusually high number to me over the =
last =3D
>few weeks. Errors I'm not familiar with. It will have been 10 years =
in =3D
>November since Paris shipped. I wonder if the lifespan of this =
hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I sent =
was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine when I =
pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts =
recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually high =
number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will have been =
=3D
>10=3D20
>years in November since Paris shipped. I wonder if the lifespan of =
this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact next =
Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to fight =
spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_00DF_01C7FC87.E3E2E1F0
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.16525" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>WOW!!!........man........I'm sorry =
you're having to=20
go through this kind of grief Tom. I hope it wasn't the MEC I sent you. =
Was that=20
the one with the black gaffers tape holding the bottom plate? If so, =
it's not my=20
fault. I got it from Rick. ;oD</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Seriously, I am bummed out for you. =
there's=20
norhting worse than having to deal with this kinda' stuff, IMO. You have =
my=20
permission to use the MEC for target practice if that will =
help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>;o(</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:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Intersted people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. It's not=20
confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two </FONT><FONT =
face=3DArial=20
size=3D2>that might 'still work'. The hardware =
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most logical at =
this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with 2 mecs =
loaded to the=20
gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and bought one =
from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding my =
default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of turmoil =
looking to get=20
back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to boot =
with mecs and=20
no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to test eds =
and cables=20
and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed =
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the studio with =
both=20
computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every time it =
wouldn't=20
boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey (no =
patchbay=20
connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs place =
with the Paris=20
comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used the mec =
throughout all=20
testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris =
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was introduced =
Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not =
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my original C =
drive (no=20
default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my other Mec =
that is=20
loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded the new =
ones I just=20
got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded it. Once =
I changed=20
to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would not =
boot" . .=20
. Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available in the =
patchbay=20
except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the introduction of =
DJ's mec=20
(whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own doing. =
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted a SCSI 2 =
cable at=20
the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was smoke in =
the power=20
supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My other mec =
was attached=20
at that time. I now think it fried something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my hopefully =
unfried mec at=20
another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If I'm =
wrong then we're=20
back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In =
all=20
seriousness - THREE bad MEC's??? What's the real<BR>likelihood of =
that?=20
Unless all 3 PSU's got hit hard with a<BR>voltage spike or something =
weird=20
like that, is it really<BR>possible that ALL of his MECs went=20
bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at _ animas _ dot =
_=20
net> wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you =
think the=20
one I sent was bad ? It was working fine when I =
pulled<BR>=3D<BR>>it from=20
the rack.=3D20<BR>><BR>>I've noticed a few posts recently =
regarding=20
errors. Maybe no more than =3D<BR>>usual, but it seemed like an =
unusually=20
high number to me over the last =3D<BR>>few weeks. Errors I'm not =
familiar=20
with. It will have been 10 years in =3D<BR>>November since Paris =
shipped. I=20
wonder if the lifespan of this hardware<BR>=3D<BR>>is starting to =
fade. TG=20
for TheSoniq, I guess.<BR>><BR>>Deej<BR>><BR>> =
"Tom Bruhl"=20
<<A =
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote=20
in message =3D<BR>>news:46f44c75$1@linux...<BR>> 3 bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll know =
for a fact=20
next Tuesday when there's<BR>> time to test a couple on =
another=20
system.<BR>><BR>><BR>><BR>> <BR>> I choose =
Polesoft=20
Lockspam to fight spam, and you?<BR>> <A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0=20
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do you=20
think the one I sent was =3D<BR>>bad =
?=3D20<BR>></FONT><FONT=20
face=3D3DArial size=3D3D2>It was working fine when I pulled=20
it<BR>=3D<BR>>from the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts recently=20
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more than usual, =
but it seemed=20
like an unusually high number to<BR>=3D<BR>>me =
over=3D20<BR>>the last few=20
weeks. Errors I'm not familiar with. It will have been=20
=3D<BR>>10=3D20<BR>>years in November since Paris shipped. I =
wonder if the=20
lifespan of this<BR>=3D<BR>>hardware=3D20<BR>>is starting to =
fade. TG for=20
TheSoniq, I =
guess.</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: =
5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl" =
<<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2>I'll know for a =
fact next=20
Tuesday =3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20<BR>> =20
system.</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =
you?<BR><A=3D20<BR>> =20
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BODY ></HTML>
------=_NextPart_000_00DF_01C7FC87.E3E2E1F0--
|
|
|
|
| Re: I think I found my problem [message #90140 is a reply to message #90137] |
Fri, 21 September 2007 19:03 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0088_01C7FC9B.4CAF8450
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I still owe you for the thing!!!
I can't say it was the Mec but it was at that time that the *)#& began =
to fly.
I was the navigator so blame me.
t
"DJ" <animix _ at _ animas _ dot _ net> wrote in message =
news:46f47556@linux...
WOW!!!........man........I'm sorry you're having to go through this =
kind of grief Tom. I hope it wasn't the MEC I sent you. Was that the one =
with the black gaffers tape holding the bottom plate? If so, it's not my =
fault. I got it from Rick. ;oD
Seriously, I am bummed out for you. there's norhting worse than having =
to deal with this kinda' stuff, IMO. You have my permission to use the =
MEC for target practice if that will help.
;o(
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Interested people,
I know 3 fried mecs is unlikely. It's not confirmed until Tuesday=20
when I'll check the two that might 'still work'. The hardware =
solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a 442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris freaked
and I went through days of turmoil looking to get back to where
I was. Paris refused to boot with mecs and no 442 at that time.
Next I built another comp to test eds and cables and the 442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never got a =
good Paris boot. Every time it wouldn't boot there was a Mec =
attached.
Even the 442 boots were flakey (no patchbay connections). I didn't =
learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's mec
and the 442. We used the mec throughout all testing until the end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and Paris
would not boot with my other Mec that is loaded to the gills. I =
deleted
the Scherzo drivers, reloaded the new ones I just got, uninstalled =
the
subsystem and reloaded it. Once I changed to the 442 the system was =
fine.
Let me rephrase "Paris would not boot" . . . Actually it would =
usually start
up but no audio was available in the patchbay except with the 442.
My take is that the introduction of DJ's mec (whether it worked or =
didn't,
let's assume that it worked) was screwy probably by my own doing. I
removed it and later shorted a SCSI 2 cable at the Master Mec =
sometime during that
next week. There was smoke in the power supply area so I never =
tried that
Mec again. My other mec was attached at that time. I now think it =
fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio on =
Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine when I =
pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe no more =
than =3D
>usual, but it seemed like an unusually high number to me over the =
last =3D
>few weeks. Errors I'm not familiar with. It will have been 10 =
years in =3D
>November since Paris shipped. I wonder if the lifespan of this =
hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I sent =
was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine when I =
pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts =
recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually high =
number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will have =
been =3D
>10=3D20
>years in November since Paris shipped. I wonder if the lifespan =
of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact next =
Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_0088_01C7FC9B.4CAF8450
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I still owe you for the =
thing!!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I can't say it was the Mec but it was =
at that time=20
that the *)#& began to fly.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was the navigator so blame=20
me.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>t</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>"DJ" <animix _ at _ animas _ dot _ net> wrote in message <A =
href=3D"news:46f47556@linux">news:46f47556@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>WOW!!!........man........I'm sorry =
you're having=20
to go through this kind of grief Tom. I hope it wasn't the MEC I sent =
you. Was=20
that the one with the black gaffers tape holding the bottom plate? If =
so, it's=20
not my fault. I got it from Rick. ;oD</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Seriously, I am bummed out for you. =
there's=20
norhting worse than having to deal with this kinda' stuff, IMO. You =
have my=20
permission to use the MEC for target practice if that will =
help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>;o(</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=20
message <A =
href=3D"news:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Interested people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. It's not=20
confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT face=3DArial=20
size=3D2>that might 'still work'. The hardware =
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most logical =
at this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with 2 mecs =
loaded to=20
the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and bought =
one from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding my =
default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of turmoil =
looking to=20
get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to boot =
with mecs=20
and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to test =
eds and=20
cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed =
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the studio =
with both=20
computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every time =
it wouldn't=20
boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey (no =
patchbay=20
connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs place =
with the=20
Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used the mec =
throughout=20
all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was introduced =
Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not =
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my original C =
drive (no=20
default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my other =
Mec that is=20
loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded the =
new ones I=20
just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded it. =
Once I changed=20
to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would not =
boot" . .=20
. Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available in =
the patchbay=20
except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the introduction of =
DJ's mec=20
(whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own doing. =
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted a SCSI =
2 cable at=20
the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was smoke in =
the power=20
supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My other mec =
was attached=20
at that time. I now think it fried something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my hopefully =
unfried mec at=20
another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If I'm =
wrong then=20
we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In =
all=20
seriousness - THREE bad MEC's??? What's the real<BR>likelihood of =
that?=20
Unless all 3 PSU's got hit hard with a<BR>voltage spike or =
something weird=20
like that, is it really<BR>possible that ALL of his MECs went=20
bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at _ animas _ =
dot _=20
net> wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you =
think the=20
one I sent was bad ? It was working fine when I =
pulled<BR>=3D<BR>>it from=20
the rack.=3D20<BR>><BR>>I've noticed a few posts recently =
regarding=20
errors. Maybe no more than =3D<BR>>usual, but it seemed like an =
unusually=20
high number to me over the last =3D<BR>>few weeks. Errors I'm =
not=20
familiar with. It will have been 10 years in =3D<BR>>November =
since Paris=20
shipped. I wonder if the lifespan of this =
hardware<BR>=3D<BR>>is starting=20
to fade. TG for TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" =
<<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote in=20
message =3D<BR>>news:46f44c75$1@linux...<BR>> 3 bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll know =
for a=20
fact next Tuesday when there's<BR>> time to test a couple =
on=20
another system.<BR>><BR>><BR>><BR>> <BR>> I =
choose=20
Polesoft Lockspam to fight spam, and you?<BR>> <A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0=20
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do you=20
think the one I sent was =3D<BR>>bad =
?=3D20<BR>></FONT><FONT=20
face=3D3DArial size=3D3D2>It was working fine when I pulled=20
it<BR>=3D<BR>>from the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts recently=20
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more than usual, =
but it=20
seemed like an unusually high number to<BR>=3D<BR>>me =
over=3D20<BR>>the=20
last few weeks. Errors I'm not familiar with. It will have been=20
=3D<BR>>10=3D20<BR>>years in November since Paris shipped. I =
wonder if=20
the lifespan of this<BR>=3D<BR>>hardware=3D20<BR>>is =
starting to fade.=20
TG for TheSoniq, I=20
guess.</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT: 5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl" =
<<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20<BR>> =20
system.</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BODY></HTML>
------=_NextPart_000_0088_01C7FC9B.4CAF8450--
|
|
|
|
| Re: I think I found my problem [message #90142 is a reply to message #90140] |
Fri, 21 September 2007 19:44 |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_002B_01C7FC90.34EFCF10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
If it's a doorstop, you don't owe me anything at all. No kiddin'. I =
trust you. Just lunch it if it's dead.
Deej
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f4797a@linux...
I still owe you for the thing!!!
I can't say it was the Mec but it was at that time that the *)#& began =
to fly.
I was the navigator so blame me.
t
"DJ" <animix _ at _ animas _ dot _ net> wrote in message =
news:46f47556@linux...
WOW!!!........man........I'm sorry you're having to go through this =
kind of grief Tom. I hope it wasn't the MEC I sent you. Was that the one =
with the black gaffers tape holding the bottom plate? If so, it's not my =
fault. I got it from Rick. ;oD
Seriously, I am bummed out for you. there's norhting worse than =
having to deal with this kinda' stuff, IMO. You have my permission to =
use the MEC for target practice if that will help.
;o(
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Interested people,
I know 3 fried mecs is unlikely. It's not confirmed until Tuesday =
when I'll check the two that might 'still work'. The hardware =
solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a 442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris freaked
and I went through days of turmoil looking to get back to where
I was. Paris refused to boot with mecs and no 442 at that time.
Next I built another comp to test eds and cables and the 442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never got =
a=20
good Paris boot. Every time it wouldn't boot there was a Mec =
attached.
Even the 442 boots were flakey (no patchbay connections). I =
didn't learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's mec
and the 442. We used the mec throughout all testing until the =
end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and =
Paris
would not boot with my other Mec that is loaded to the gills. I =
deleted
the Scherzo drivers, reloaded the new ones I just got, uninstalled =
the
subsystem and reloaded it. Once I changed to the 442 the system =
was fine.
Let me rephrase "Paris would not boot" . . . Actually it would =
usually start
up but no audio was available in the patchbay except with the 442.
My take is that the introduction of DJ's mec (whether it worked or =
didn't,
let's assume that it worked) was screwy probably by my own doing. =
I
removed it and later shorted a SCSI 2 cable at the Master Mec =
sometime during that
next week. There was smoke in the power supply area so I never =
tried that
Mec again. My other mec was attached at that time. I now think =
it fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio on =
Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine when =
I pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe no =
more than =3D
>usual, but it seemed like an unusually high number to me over =
the last =3D
>few weeks. Errors I'm not familiar with. It will have been 10 =
years in =3D
>November since Paris shipped. I wonder if the lifespan of this =
hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I =
sent was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine when =
I pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts =
recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually high =
number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will have =
been =3D
>10=3D20
>years in November since Paris shipped. I wonder if the lifespan =
of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact =
next Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_002B_01C7FC90.34EFCF10
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.16525" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>If it's a doorstop, you don't owe me =
anything at=20
all. No kiddin'. I trust you. Just lunch it if it's dead.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Deej</FONT></DIV>
<DIV> </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:46f4797a@linux">news:46f4797a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I still owe you for the =
thing!!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I can't say it was the Mec but it was =
at that=20
time that the *)#& began to fly.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was the navigator so =
blame=20
me.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>t</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>"DJ" <animix _ at _ animas _ dot _ net> wrote in message =
<A=20
href=3D"news:46f47556@linux">news:46f47556@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>WOW!!!........man........I'm sorry =
you're=20
having to go through this kind of grief Tom. I hope it wasn't the =
MEC I sent=20
you. Was that the one with the black gaffers tape holding the bottom =
plate?=20
If so, it's not my fault. I got it from Rick. ;oD</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Seriously, I am bummed out for you. =
there's=20
norhting worse than having to deal with this kinda' stuff, IMO. You =
have my=20
permission to use the MEC for target practice if that will=20
help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>;o(</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=20
message <A =
href=3D"news:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Interested people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. It's=20
not confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT=20
face=3DArial size=3D2>that might 'still work'. The hardware=20
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most logical =
at this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with 2 =
mecs loaded to=20
the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and bought =
one from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding my =
default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of =
turmoil looking to=20
get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to =
boot with mecs=20
and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to test =
eds and=20
cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed =
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the studio =
with both=20
computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every time =
it wouldn't=20
boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey =
(no patchbay=20
connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs =
place with the=20
Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used the =
mec throughout=20
all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was introduced =
Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not=20
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my original =
C drive (no=20
default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my other =
Mec that is=20
loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded the =
new ones I=20
just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded it. =
Once I=20
changed to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would not =
boot" . .=20
. Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available in =
the patchbay=20
except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the introduction =
of DJ's mec=20
(whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own doing. =20
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted a =
SCSI 2 cable=20
at the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was smoke =
in the power=20
supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My other =
mec was=20
attached at that time. I now think it fried =
something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my hopefully =
unfried mec=20
at another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If I'm =
wrong then=20
we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A =
href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> wrote=20
in message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
all seriousness - THREE bad MEC's??? What's the =
real<BR>likelihood of=20
that? Unless all 3 PSU's got hit hard with a<BR>voltage spike or =
something weird like that, is it really<BR>possible that ALL of =
his MECs=20
went bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at _ =
animas _ dot=20
_ net> wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do =
you think=20
the one I sent was bad ? It was working fine when I=20
pulled<BR>=3D<BR>>it from the rack.=3D20<BR>><BR>>I've =
noticed a=20
few posts recently regarding errors. Maybe no more than =
=3D<BR>>usual,=20
but it seemed like an unusually high number to me over the last=20
=3D<BR>>few weeks. Errors I'm not familiar with. It will have =
been 10=20
years in =3D<BR>>November since Paris shipped. I wonder if =
the lifespan=20
of this hardware<BR>=3D<BR>>is starting to fade. TG for =
TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" =
<<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote in=20
message =3D<BR>>news:46f44c75$1@linux...<BR>> 3 bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll =
know for a=20
fact next Tuesday when there's<BR>> time to test a =
couple on=20
another system.<BR>><BR>><BR>><BR>> <BR>> I =
choose=20
Polesoft Lockspam to fight spam, and you?<BR>> <A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0=20
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do you=20
think the one I sent was =3D<BR>>bad =
?=3D20<BR>></FONT><FONT=20
face=3D3DArial size=3D3D2>It was working fine when I pulled=20
it<BR>=3D<BR>>from the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts recently=20
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more than =
usual, but it=20
seemed like an unusually high number to<BR>=3D<BR>>me=20
over=3D20<BR>>the last few weeks. Errors I'm not familiar =
with. It will=20
have been =3D<BR>>10=3D20<BR>>years in November since =
Paris shipped. I=20
wonder if the lifespan of =
this<BR>=3D<BR>>hardware=3D20<BR>>is=20
starting to fade. TG for TheSoniq, I=20
guess.</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT: 5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl" =
<<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A =
href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2>time to test a couple on=20
another=3D20<BR>> =
system.</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>> =
<DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQUOTE></BO=
DY></HTML>
------=_NextPart_000_002B_01C7FC90.34EFCF10--
|
|
|
|
| Re: I think I found my problem [message #90145 is a reply to message #90142] |
Fri, 21 September 2007 20:51 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_00B0_01C7FCAA.4FC92290
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hey Deej,
If you know it worked then it did. My other mecs are another story.
I don't think you're mec had it out for them. . . well maybe huh?
The new kid in town?=20
I might be going to Namm in Anaheim 1/16-21/08. Could be a helluva
good time after the holiday season. I'll get you lunch and whatever =
else
happens that night if you can make it.
GOOD NEWS! I can finally hear audio again!!!
All 5 EDS cards are working perfectly in the Magma. I am Acronising the =
whole
shootin' match before throwing the UAD back in. No IRQ sharing except =
with
USB that is never in use except for backups after the session. I can =
deal
with that.
Huge gigging weekend ahead of me but I have a s eatin' grin on my face =
all the sudden.
This should last until Sunday night when it's over.
Woohoo!
Tom
"DJ" <animix _ at _ animas _ dot _ net> wrote in message =
news:46f4834a@linux...
If it's a doorstop, you don't owe me anything at all. No kiddin'. I =
trust you. Just lunch it if it's dead.
Deej
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f4797a@linux...
I still owe you for the thing!!!
I can't say it was the Mec but it was at that time that the *)#& =
began to fly.
I was the navigator so blame me.
t
"DJ" <animix _ at _ animas _ dot _ net> wrote in message =
news:46f47556@linux...
WOW!!!........man........I'm sorry you're having to go through =
this kind of grief Tom. I hope it wasn't the MEC I sent you. Was that =
the one with the black gaffers tape holding the bottom plate? If so, =
it's not my fault. I got it from Rick. ;oD
Seriously, I am bummed out for you. there's norhting worse than =
having to deal with this kinda' stuff, IMO. You have my permission to =
use the MEC for target practice if that will help.
;o(
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Interested people,
I know 3 fried mecs is unlikely. It's not confirmed until =
Tuesday=20
when I'll check the two that might 'still work'. The hardware =
solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a =
442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris freaked
and I went through days of turmoil looking to get back to where
I was. Paris refused to boot with mecs and no 442 at that time.
Next I built another comp to test eds and cables and the 442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never =
got a=20
good Paris boot. Every time it wouldn't boot there was a Mec =
attached.
Even the 442 boots were flakey (no patchbay connections). I =
didn't learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's =
mec
and the 442. We used the mec throughout all testing until the =
end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and =
Paris
would not boot with my other Mec that is loaded to the gills. I =
deleted
the Scherzo drivers, reloaded the new ones I just got, =
uninstalled the
subsystem and reloaded it. Once I changed to the 442 the system =
was fine.
Let me rephrase "Paris would not boot" . . . Actually it would =
usually start
up but no audio was available in the patchbay except with the =
442.
My take is that the introduction of DJ's mec (whether it worked =
or didn't,
let's assume that it worked) was screwy probably by my own =
doing. I
removed it and later shorted a SCSI 2 cable at the Master Mec =
sometime during that
next week. There was smoke in the power supply area so I never =
tried that
Mec again. My other mec was attached at that time. I now think =
it fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio =
on Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine =
when I pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe no =
more than =3D
>usual, but it seemed like an unusually high number to me over =
the last =3D
>few weeks. Errors I'm not familiar with. It will have been 10 =
years in =3D
>November since Paris shipped. I wonder if the lifespan of =
this hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" =
name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I =
sent was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine =
when I pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts =
recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually =
high number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will =
have been =3D
>10=3D20
>years in November since Paris shipped. I wonder if the =
lifespan of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad =
mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact =
next Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple =
on another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_00B0_01C7FCAA.4FC92290
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hey Deej,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If you know it worked then it =
did. My other=20
mecs are another story.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I don't think you're mec had it out for =
them. . .=20
well maybe huh?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The new kid in town?</FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I might be going to Namm in Anaheim=20
1/16-21/08. Could be a helluva</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good time after the holiday =
season. I'll get=20
you lunch and whatever else</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>happens that night if you can make =
it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>GOOD NEWS! <FONT =
face=3DArial=20
size=3D2>I can finally hear audio again!!!</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>All 5 EDS cards are working perfectly =
in the=20
Magma. I am Acronising the whole</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>shootin' match before throwing the UAD =
back=20
in. No IRQ sharing except with</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>USB that is never in use except for =
backups after=20
the session. I can deal</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>with that.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Huge gigging weekend ahead of me but I =
have a s=20
eatin' grin on my face all the sudden.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>This should last until Sunday night =
when it's=20
over.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Woohoo!</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>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></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>"DJ" <animix _ at _ animas _ dot _ net> wrote in message <A =
href=3D"news:46f4834a@linux">news:46f4834a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>If it's a doorstop, you don't owe me =
anything at=20
all. No kiddin'. I trust you. Just lunch it if it's dead.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Deej</FONT></DIV>
<DIV> </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:46f4797a@linux">news:46f4797a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I still owe you for the =
thing!!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I can't say it was the Mec but it =
was at that=20
time that the *)#& began to fly.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was the navigator so =
blame=20
me.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>t</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>"DJ" <animix _ at _ animas _ dot _ net> wrote in =
message <A=20
href=3D"news:46f47556@linux">news:46f47556@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>WOW!!!........man........I'm =
sorry you're=20
having to go through this kind of grief Tom. I hope it wasn't the =
MEC I=20
sent you. Was that the one with the black gaffers tape holding the =
bottom=20
plate? If so, it's not my fault. I got it from Rick. =
;oD</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Seriously, I am bummed out for =
you. there's=20
norhting worse than having to deal with this kinda' stuff, IMO. =
You have=20
my permission to use the MEC for target practice if that will=20
help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>;o(</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=20
message <A =
href=3D"news:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Interested people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. It's=20
not confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT=20
face=3DArial size=3D2>that might 'still work'. The =
hardware=20
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most =
logical at this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with 2 =
mecs loaded=20
to the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and =
bought one from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding =
my default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of =
turmoil looking=20
to get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to =
boot with=20
mecs and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to =
test eds and=20
cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed =
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the =
studio with both=20
computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every =
time it=20
wouldn't boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey =
(no patchbay=20
connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs =
place with the=20
Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used the =
mec=20
throughout all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was =
introduced Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not=20
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my =
original C drive=20
(no default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my =
other Mec that=20
is loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded =
the new ones=20
I just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded =
it. Once I=20
changed to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would =
not boot" . .=20
. Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available =
in the=20
patchbay except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the =
introduction of DJ's=20
mec (whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own doing. =
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted a =
SCSI 2 cable=20
at the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was =
smoke in the=20
power supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My other =
mec was=20
attached at that time. I now think it fried =
something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my =
hopefully unfried=20
mec at another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If =
I'm wrong then=20
we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A =
href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> wrote=20
in message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
all seriousness - THREE bad MEC's??? What's the =
real<BR>likelihood of=20
that? Unless all 3 PSU's got hit hard with a<BR>voltage spike =
or=20
something weird like that, is it really<BR>possible that ALL =
of his=20
MECs went bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at =
_=20
animas _ dot _ net>=20
wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you think =
the one=20
I sent was bad ? It was working fine when I =
pulled<BR>=3D<BR>>it from=20
the rack.=3D20<BR>><BR>>I've noticed a few posts =
recently=20
regarding errors. Maybe no more than =3D<BR>>usual, but it =
seemed=20
like an unusually high number to me over the last =
=3D<BR>>few weeks.=20
Errors I'm not familiar with. It will have been 10 years in=20
=3D<BR>>November since Paris shipped. I wonder if the =
lifespan of=20
this hardware<BR>=3D<BR>>is starting to fade. TG for =
TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" =
<<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote in =
message =3D<BR>>news:46f44c75$1@linux...<BR>> 3 =
bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll =
know for=20
a fact next Tuesday when there's<BR>> time to test a =
couple=20
on another =
system.<BR>><BR>><BR>><BR>> <BR>> I=20
choose Polesoft Lockspam to fight spam, and you?<BR>> =
<A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 =
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do=20
you think the one I sent was =3D<BR>>bad=20
?=3D20<BR>></FONT><FONT face=3D3DArial =
size=3D3D2>It was=20
working fine when I pulled it<BR>=3D<BR>>from =
the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts recently =
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more than =
usual, but it=20
seemed like an unusually high number to<BR>=3D<BR>>me=20
over=3D20<BR>>the last few weeks. Errors I'm not familiar =
with. It=20
will have been =3D<BR>>10=3D20<BR>>years in November =
since Paris=20
shipped. I wonder if the lifespan of=20
this<BR>=3D<BR>>hardware=3D20<BR>>is starting to fade. =
TG for=20
TheSoniq, I =
guess.</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT: 5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid;=20
MARGIN-RIGHT: 0px"><BR>> <DIV>"Tom Bruhl"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A =
href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> <DIV><FONT face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2>time to test a couple on=20
another=3D20<BR>> =20
system.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam =
to fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =3D<BR>>href=3D3D"<A =
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQUOTE></BL=
OCKQUOTE></BODY></HTML>
------=_NextPart_000_00B0_01C7FCAA.4FC92290--
|
|
|
|
| Re: I think I found my problem [message #90157 is a reply to message #90136] |
Sat, 22 September 2007 02:50 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0020_01C7FCD4.0F98B1C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Dude, if you have 3 toasted MEC's I think it VERY likely you had a bad =
cable that put the hurt on them all as you swapped around parts.=20
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until Tuesday=20
when I'll check the two that might 'still work'. The hardware =
solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a 442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris freaked
and I went through days of turmoil looking to get back to where
I was. Paris refused to boot with mecs and no 442 at that time.
Next I built another comp to test eds and cables and the 442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never got a=20
good Paris boot. Every time it wouldn't boot there was a Mec =
attached.
Even the 442 boots were flakey (no patchbay connections). I didn't =
learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's mec
and the 442. We used the mec throughout all testing until the end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and Paris
would not boot with my other Mec that is loaded to the gills. I =
deleted
the Scherzo drivers, reloaded the new ones I just got, uninstalled the
subsystem and reloaded it. Once I changed to the 442 the system was =
fine.
Let me rephrase "Paris would not boot" . . . Actually it would =
usually start
up but no audio was available in the patchbay except with the 442.
My take is that the introduction of DJ's mec (whether it worked or =
didn't,
let's assume that it worked) was screwy probably by my own doing. I
removed it and later shorted a SCSI 2 cable at the Master Mec sometime =
during that
next week. There was smoke in the power supply area so I never tried =
that
Mec again. My other mec was attached at that time. I now think it =
fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio on =
Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine when I =
pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe no more =
than =3D
>usual, but it seemed like an unusually high number to me over the =
last =3D
>few weeks. Errors I'm not familiar with. It will have been 10 years =
in =3D
>November since Paris shipped. I wonder if the lifespan of this =
hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I sent =
was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine when I =
pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts =
recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually high =
number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will have been =
=3D
>10=3D20
>years in November since Paris shipped. I wonder if the lifespan of =
this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact next =
Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to fight =
spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_0020_01C7FCD4.0F98B1C0
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.16525" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dude, if you have 3 toasted MEC's I =
think it VERY=20
likely you had a bad cable that put the hurt on them all as you =
swapped=20
around parts. </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:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Intersted people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. It's not=20
confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two </FONT><FONT =
face=3DArial=20
size=3D2>that might 'still work'. The hardware =
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most logical at =
this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with 2 mecs =
loaded to the=20
gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and bought one =
from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding my =
default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of turmoil =
looking to get=20
back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to boot =
with mecs and=20
no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to test eds =
and cables=20
and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed =
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the studio with =
both=20
computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every time it =
wouldn't=20
boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey (no =
patchbay=20
connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs place =
with the Paris=20
comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used the mec =
throughout all=20
testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris =
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was introduced =
Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not =
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my original C =
drive (no=20
default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my other Mec =
that is=20
loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded the new =
ones I just=20
got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded it. Once =
I changed=20
to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would not =
boot" . .=20
. Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available in the =
patchbay=20
except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the introduction of =
DJ's mec=20
(whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own doing. =
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted a SCSI 2 =
cable at=20
the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was smoke in =
the power=20
supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My other mec =
was attached=20
at that time. I now think it fried something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my hopefully =
unfried mec at=20
another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If I'm =
wrong then we're=20
back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In =
all=20
seriousness - THREE bad MEC's??? What's the real<BR>likelihood of =
that?=20
Unless all 3 PSU's got hit hard with a<BR>voltage spike or something =
weird=20
like that, is it really<BR>possible that ALL of his MECs went=20
bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at _ animas _ dot =
_=20
net> wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you =
think the=20
one I sent was bad ? It was working fine when I =
pulled<BR>=3D<BR>>it from=20
the rack.=3D20<BR>><BR>>I've noticed a few posts recently =
regarding=20
errors. Maybe no more than =3D<BR>>usual, but it seemed like an =
unusually=20
high number to me over the last =3D<BR>>few weeks. Errors I'm not =
familiar=20
with. It will have been 10 years in =3D<BR>>November since Paris =
shipped. I=20
wonder if the lifespan of this hardware<BR>=3D<BR>>is starting to =
fade. TG=20
for TheSoniq, I guess.<BR>><BR>>Deej<BR>><BR>> =
"Tom Bruhl"=20
<<A =
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote=20
in message =3D<BR>>news:46f44c75$1@linux...<BR>> 3 bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll know =
for a fact=20
next Tuesday when there's<BR>> time to test a couple on =
another=20
system.<BR>><BR>><BR>><BR>> <BR>> I choose =
Polesoft=20
Lockspam to fight spam, and you?<BR>> <A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0=20
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do you=20
think the one I sent was =3D<BR>>bad =
?=3D20<BR>></FONT><FONT=20
face=3D3DArial size=3D3D2>It was working fine when I pulled=20
it<BR>=3D<BR>>from the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts recently=20
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more than usual, =
but it seemed=20
like an unusually high number to<BR>=3D<BR>>me =
over=3D20<BR>>the last few=20
weeks. Errors I'm not familiar with. It will have been=20
=3D<BR>>10=3D20<BR>>years in November since Paris shipped. I =
wonder if the=20
lifespan of this<BR>=3D<BR>>hardware=3D20<BR>>is starting to =
fade. TG for=20
TheSoniq, I =
guess.</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: =
5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl" =
<<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2>I'll know for a =
fact next=20
Tuesday =3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20<BR>> =20
system.</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =
you?<BR><A=3D20<BR>> =20
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BODY ></HTML>
------=_NextPart_000_0020_01C7FCD4.0F98B1C0--
|
|
|
|
| Re: I think I found my problem [message #90159 is a reply to message #90137] |
Sat, 22 September 2007 03:49 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
phew...i thought i'd never get dragged into this thread. 'bout damn
time i say. thanx
;o)
On Fri, 21 Sep 2007 19:44:56 -0600, "DJ" <animix _ at _ animas _ dot _
net> wrote:
>WOW!!!........man........I'm sorry you're having to go through this kind of grief Tom. I hope it wasn't the MEC I sent you. Was that the one with the black gaffers tape holding the bottom plate? If so, it's not my fault. I got it from Rick. ;oD
>
>Seriously, I am bummed out for you. there's norhting worse than having to deal with this kinda' stuff, IMO. You have my permission to use the MEC for target practice if that will help.
>
>;o(
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message news:46f472e2@linux...
> Intersted people,
> I know 3 fried mecs is unlikely. It's not confirmed until Tuesday
> when I'll check the two that might 'still work'. The hardware solution
> is seeming to be the most logical at this point. Here's why:
>
> I was working perfectly with 2 mecs loaded to the gills and a 442.
> I wanted one more mec and bought one from Deej. Mistakenly,
> I installed it without hiding my default project. Paris freaked
> and I went through days of turmoil looking to get back to where
> I was. Paris refused to boot with mecs and no 442 at that time.
>
> Next I built another comp to test eds and cables and the 442.
> Everything went fine. No probs. This seemed promising.
>
> Next I tried again in the studio with both computers and never got a
> good Paris boot. Every time it wouldn't boot there was a Mec attached.
> Even the 442 boots were flakey (no patchbay connections). I didn't learn
> anything from this effort.
>
> 2 days ago I went to a techs place with the Paris comp, Deej's mec
> and the 442. We used the mec throughout all testing until the end.
> Fresh C drive, fresh Paris install.
> As soon as the 442 was introduced Paris booted. Likely the Deej
> mec is faulty but not necessarily.
>
> Today I went back to my original C drive (no default proj) and Paris
> would not boot with my other Mec that is loaded to the gills. I deleted
> the Scherzo drivers, reloaded the new ones I just got, uninstalled the
> subsystem and reloaded it. Once I changed to the 442 the system was fine.
>
> Let me rephrase "Paris would not boot" . . . Actually it would usually start
> up but no audio was available in the patchbay except with the 442.
>
> My take is that the introduction of DJ's mec (whether it worked or didn't,
> let's assume that it worked) was screwy probably by my own doing. I
> removed it and later shorted a SCSI 2 cable at the Master Mec sometime during that
> next week. There was smoke in the power supply area so I never tried that
> Mec again. My other mec was attached at that time. I now think it fried something
> in their too.
>
> I am trying DJs and my hopefully unfried mec at another studio on Tuesday to confirm
> that neither works. If I'm wrong then we're back to software.
>
> It ain't over till it's over.
> Tom
>
>
>
>
> "Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
>
> In all seriousness - THREE bad MEC's??? What's the real
> likelihood of that? Unless all 3 PSU's got hit hard with a
> voltage spike or something weird like that, is it really
> possible that ALL of his MECs went bad?
>
> Neil
>
>
>
> "DJ" <animix _ at _ animas _ dot _ net> wrote:
> >
> >
> >Tom,
> >
> >Do you think the one I sent was bad ? It was working fine when I pulled
> =
> >it from the rack.=20
> >
> >I've noticed a few posts recently regarding errors. Maybe no more than =
> >usual, but it seemed like an unusually high number to me over the last =
> >few weeks. Errors I'm not familiar with. It will have been 10 years in =
> >November since Paris shipped. I wonder if the lifespan of this hardware
> =
> >is starting to fade. TG for TheSoniq, I guess.
> >
> >Deej
> >
> > "Tom Bruhl" <arpegio@comcast.net> wrote in message =
> >news:46f44c75$1@linux...
> > 3 bad mecs.
> >
> > Hmmm?
> >
> > I'll know for a fact next Tuesday when there's
> > time to test a couple on another system.
> >
> >
> >
> >
> > I choose Polesoft Lockspam to fight spam, and you?
> > http://www.polesoft.com/refer.html
> >
> ><!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.16525" name=3DGENERATOR>
> ><STYLE></STYLE>
> ></HEAD>
> ><BODY bgColor=3D#ffffff>
> ><DIV><FONT face=3DArial size=3D2>Tom,</FONT></DIV>
> ><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> ><DIV><FONT face=3DArial size=3D2>Do you think the one I sent was =
> >bad ?=20
> ></FONT><FONT face=3DArial size=3D2>It was working fine when I pulled it
> =
> >from the=20
> >rack. </FONT></DIV>
> ><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> ><DIV><FONT face=3DArial size=3D2>I've noticed a few posts recently =
> >regarding errors.=20
> >Maybe no more than usual, but it seemed like an unusually high number to
> =
> >me over=20
> >the last few weeks. Errors I'm not familiar with. It will have been =
> >10=20
> >years in November since Paris shipped. I wonder if the lifespan of this
> =
> >hardware=20
> >is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
> ><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> ><DIV><FONT face=3DArial size=3D2>Deej</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:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> > <DIV><FONT face=3DArial size=3D2>3 bad mecs.</FONT></DIV>
> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> > <DIV><FONT face=3DArial size=3D2>Hmmm?</FONT></DIV>
> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> > <DIV><FONT face=3DArial size=3D2>I'll know for a fact next Tuesday =
> >when=20
> > there's</FONT></DIV>
> > <DIV><FONT face=3DArial size=3D2>time to test a couple on another=20
> > system.</FONT></DIV>
> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> > <DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam,
> =
> >and=20
> > you?<BR><A=20
> > =
> >href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
> >.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
> >
> >
|
|
|
|
| Re: I think I found my problem [message #90160 is a reply to message #90157] |
Sat, 22 September 2007 04:14 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0118_01C7FCE8.46723310
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I'll double check Aaron.
Continuity is my middle name.
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f4e6c0@linux...
Dude, if you have 3 toasted MEC's I think it VERY likely you had a bad =
cable that put the hurt on them all as you swapped around parts.=20
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until Tuesday=20
when I'll check the two that might 'still work'. The hardware =
solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a 442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris freaked
and I went through days of turmoil looking to get back to where
I was. Paris refused to boot with mecs and no 442 at that time.
Next I built another comp to test eds and cables and the 442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never got a =
good Paris boot. Every time it wouldn't boot there was a Mec =
attached.
Even the 442 boots were flakey (no patchbay connections). I didn't =
learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's mec
and the 442. We used the mec throughout all testing until the end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and Paris
would not boot with my other Mec that is loaded to the gills. I =
deleted
the Scherzo drivers, reloaded the new ones I just got, uninstalled =
the
subsystem and reloaded it. Once I changed to the 442 the system was =
fine.
Let me rephrase "Paris would not boot" . . . Actually it would =
usually start
up but no audio was available in the patchbay except with the 442.
My take is that the introduction of DJ's mec (whether it worked or =
didn't,
let's assume that it worked) was screwy probably by my own doing. I
removed it and later shorted a SCSI 2 cable at the Master Mec =
sometime during that
next week. There was smoke in the power supply area so I never =
tried that
Mec again. My other mec was attached at that time. I now think it =
fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio on =
Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine when I =
pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe no more =
than =3D
>usual, but it seemed like an unusually high number to me over the =
last =3D
>few weeks. Errors I'm not familiar with. It will have been 10 =
years in =3D
>November since Paris shipped. I wonder if the lifespan of this =
hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I sent =
was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine when I =
pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts =
recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually high =
number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will have =
been =3D
>10=3D20
>years in November since Paris shipped. I wonder if the lifespan =
of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact next =
Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_0118_01C7FCE8.46723310
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I'll double check Aaron.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Continuity is my middle =
name.</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 in=20
message <A =
href=3D"news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Dude, if you have 3 toasted MEC's I =
think it VERY=20
likely you had a bad cable that put the hurt on them all as you =
swapped=20
around parts. </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:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Intersted people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. It's not=20
confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT face=3DArial=20
size=3D2>that might 'still work'. The hardware =
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most logical =
at this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with 2 mecs =
loaded to=20
the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and bought =
one from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding my =
default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of turmoil =
looking to=20
get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to boot =
with mecs=20
and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to test =
eds and=20
cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed =
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the studio =
with both=20
computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every time =
it wouldn't=20
boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey (no =
patchbay=20
connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs place =
with the=20
Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used the mec =
throughout=20
all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was introduced =
Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not =
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my original C =
drive (no=20
default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my other =
Mec that is=20
loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded the =
new ones I=20
just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded it. =
Once I changed=20
to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would not =
boot" . .=20
. Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available in =
the patchbay=20
except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the introduction of =
DJ's mec=20
(whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own doing. =
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted a SCSI =
2 cable at=20
the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was smoke in =
the power=20
supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My other mec =
was attached=20
at that time. I now think it fried something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my hopefully =
unfried mec at=20
another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If I'm =
wrong then=20
we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In =
all=20
seriousness - THREE bad MEC's??? What's the real<BR>likelihood of =
that?=20
Unless all 3 PSU's got hit hard with a<BR>voltage spike or =
something weird=20
like that, is it really<BR>possible that ALL of his MECs went=20
bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at _ animas _ =
dot _=20
net> wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you =
think the=20
one I sent was bad ? It was working fine when I =
pulled<BR>=3D<BR>>it from=20
the rack.=3D20<BR>><BR>>I've noticed a few posts recently =
regarding=20
errors. Maybe no more than =3D<BR>>usual, but it seemed like an =
unusually=20
high number to me over the last =3D<BR>>few weeks. Errors I'm =
not=20
familiar with. It will have been 10 years in =3D<BR>>November =
since Paris=20
shipped. I wonder if the lifespan of this =
hardware<BR>=3D<BR>>is starting=20
to fade. TG for TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" =
<<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote in=20
message =3D<BR>>news:46f44c75$1@linux...<BR>> 3 bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll know =
for a=20
fact next Tuesday when there's<BR>> time to test a couple =
on=20
another system.<BR>><BR>><BR>><BR>> <BR>> I =
choose=20
Polesoft Lockspam to fight spam, and you?<BR>> <A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0=20
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do you=20
think the one I sent was =3D<BR>>bad =
?=3D20<BR>></FONT><FONT=20
face=3D3DArial size=3D3D2>It was working fine when I pulled=20
it<BR>=3D<BR>>from the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts recently=20
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more than usual, =
but it=20
seemed like an unusually high number to<BR>=3D<BR>>me =
over=3D20<BR>>the=20
last few weeks. Errors I'm not familiar with. It will have been=20
=3D<BR>>10=3D20<BR>>years in November since Paris shipped. I =
wonder if=20
the lifespan of this<BR>=3D<BR>>hardware=3D20<BR>>is =
starting to fade.=20
TG for TheSoniq, I=20
guess.</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT: 5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl" =
<<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial size=3D3D2>time to test a couple on =
another=3D20<BR>> =20
system.</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BODY></HTML>
------=_NextPart_000_0118_01C7FCE8.46723310--
|
|
|
|
|
|
|
|
| Re: I know I found my problem [message #90554 is a reply to message #90160] |
Tue, 25 September 2007 18:59 |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_00DF_01C7FFAE.A46A70E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
OY!!!!
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f9621b@linux...
Most absolutely hardware. 3 Mecs down for the count.
No word on the 10 modules that were onboard during
the mishap.
Anyone have a spare mec they can part with?
Assamundo
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f4fa9a@linux...
I'll double check Aaron.
Continuity is my middle name.
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f4e6c0@linux...
Dude, if you have 3 toasted MEC's I think it VERY likely you had a =
bad cable that put the hurt on them all as you swapped around parts.=20
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until =
Tuesday=20
when I'll check the two that might 'still work'. The hardware =
solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a =
442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris freaked
and I went through days of turmoil looking to get back to where
I was. Paris refused to boot with mecs and no 442 at that time.
Next I built another comp to test eds and cables and the 442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never =
got a=20
good Paris boot. Every time it wouldn't boot there was a Mec =
attached.
Even the 442 boots were flakey (no patchbay connections). I =
didn't learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's =
mec
and the 442. We used the mec throughout all testing until the =
end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and =
Paris
would not boot with my other Mec that is loaded to the gills. I =
deleted
the Scherzo drivers, reloaded the new ones I just got, =
uninstalled the
subsystem and reloaded it. Once I changed to the 442 the system =
was fine.
Let me rephrase "Paris would not boot" . . . Actually it would =
usually start
up but no audio was available in the patchbay except with the =
442.
My take is that the introduction of DJ's mec (whether it worked =
or didn't,
let's assume that it worked) was screwy probably by my own =
doing. I
removed it and later shorted a SCSI 2 cable at the Master Mec =
sometime during that
next week. There was smoke in the power supply area so I never =
tried that
Mec again. My other mec was attached at that time. I now think =
it fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio =
on Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine =
when I pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe no =
more than =3D
>usual, but it seemed like an unusually high number to me over =
the last =3D
>few weeks. Errors I'm not familiar with. It will have been 10 =
years in =3D
>November since Paris shipped. I wonder if the lifespan of =
this hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" =
name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I =
sent was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine =
when I pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts =
recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually =
high number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will =
have been =3D
>10=3D20
>years in November since Paris shipped. I wonder if the =
lifespan of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad =
mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact =
next Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple =
on another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_00DF_01C7FFAE.A46A70E0
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.16525" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>OY!!!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </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:46f9621b@linux">news:46f9621b@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Most absolutely hardware. 3 =
Mecs down for=20
the count.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>No word on the 10 modules that were =
onboard=20
during</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the mishap.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Anyone have a spare mec they can part =
with?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Assamundo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></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=20
message <A =
href=3D"news:46f4fa9a@linux">news:46f4fa9a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll double check =
Aaron.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Continuity is my middle =
name.</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>>=20
wrote in message <A=20
href=3D"news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Dude, if you have 3 toasted MEC's =
I think it=20
VERY likely you had a bad cable that put the hurt on them =
all as you=20
swapped around parts. </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:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Intersted people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. It's=20
not confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT=20
face=3DArial size=3D2>that might 'still work'. The =
hardware=20
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most =
logical at this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with 2 =
mecs loaded=20
to the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and =
bought one from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding =
my default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of =
turmoil looking=20
to get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to =
boot with=20
mecs and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to =
test eds and=20
cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed =
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the =
studio with both=20
computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every =
time it=20
wouldn't boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey =
(no patchbay=20
connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs =
place with the=20
Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used the =
mec=20
throughout all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was =
introduced Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not=20
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my =
original C drive=20
(no default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my =
other Mec that=20
is loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded =
the new ones=20
I just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded =
it. Once I=20
changed to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would =
not boot" . .=20
. Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available =
in the=20
patchbay except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the =
introduction of DJ's=20
mec (whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own doing. =
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted a =
SCSI 2 cable=20
at the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was =
smoke in the=20
power supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My other =
mec was=20
attached at that time. I now think it fried =
something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my =
hopefully unfried=20
mec at another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If =
I'm wrong then=20
we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A =
href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> wrote=20
in message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
all seriousness - THREE bad MEC's??? What's the =
real<BR>likelihood of=20
that? Unless all 3 PSU's got hit hard with a<BR>voltage spike =
or=20
something weird like that, is it really<BR>possible that ALL =
of his=20
MECs went bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at =
_=20
animas _ dot _ net>=20
wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you think =
the one=20
I sent was bad ? It was working fine when I =
pulled<BR>=3D<BR>>it from=20
the rack.=3D20<BR>><BR>>I've noticed a few posts =
recently=20
regarding errors. Maybe no more than =3D<BR>>usual, but it =
seemed=20
like an unusually high number to me over the last =
=3D<BR>>few weeks.=20
Errors I'm not familiar with. It will have been 10 years in=20
=3D<BR>>November since Paris shipped. I wonder if the =
lifespan of=20
this hardware<BR>=3D<BR>>is starting to fade. TG for =
TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" =
<<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote in =
message =3D<BR>>news:46f44c75$1@linux...<BR>> 3 =
bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll =
know for=20
a fact next Tuesday when there's<BR>> time to test a =
couple=20
on another =
system.<BR>><BR>><BR>><BR>> <BR>> I=20
choose Polesoft Lockspam to fight spam, and you?<BR>> =
<A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 =
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do=20
you think the one I sent was =3D<BR>>bad=20
?=3D20<BR>></FONT><FONT face=3D3DArial =
size=3D3D2>It was=20
working fine when I pulled it<BR>=3D<BR>>from =
the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts recently =
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more than =
usual, but it=20
seemed like an unusually high number to<BR>=3D<BR>>me=20
over=3D20<BR>>the last few weeks. Errors I'm not familiar =
with. It=20
will have been =3D<BR>>10=3D20<BR>>years in November =
since Paris=20
shipped. I wonder if the lifespan of=20
this<BR>=3D<BR>>hardware=3D20<BR>>is starting to fade. =
TG for=20
TheSoniq, I =
guess.</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT: 5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid;=20
MARGIN-RIGHT: 0px"><BR>> <DIV>"Tom Bruhl"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A =
href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> <DIV><FONT face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2>time to test a couple on=20
another=3D20<BR>> =20
system.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam =
to fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =3D<BR>>href=3D3D"<A =
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQUOTE></BL=
OCKQUOTE></BODY></HTML>
------=_NextPart_000_00DF_01C7FFAE.A46A70E0--
|
|
|
|
| Re: I know I found my problem [message #90560 is a reply to message #90160] |
Tue, 25 September 2007 20:11 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0080_01C7FFC1.13352710
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I'll also toss out an edumacated guess that only the interface portion =
got fried and all your MEC cards are likely to be ok... holla back on =
that man.=20
Sorry, no spare MEC's around here, in fact I'm going to be growing my =
rig again shortly with a few more EDS cards :)
Say Tom, have you called The Soniq about repairing yours... he offers =
warranty on his work yano :)
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f9621b@linux...
Most absolutely hardware. 3 Mecs down for the count.
No word on the 10 modules that were onboard during
the mishap.
Anyone have a spare mec they can part with?
Assamundo
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f4fa9a@linux...
I'll double check Aaron.
Continuity is my middle name.
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f4e6c0@linux...
Dude, if you have 3 toasted MEC's I think it VERY likely you had a =
bad cable that put the hurt on them all as you swapped around parts.=20
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until =
Tuesday=20
when I'll check the two that might 'still work'. The hardware =
solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a =
442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris freaked
and I went through days of turmoil looking to get back to where
I was. Paris refused to boot with mecs and no 442 at that time.
Next I built another comp to test eds and cables and the 442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never =
got a=20
good Paris boot. Every time it wouldn't boot there was a Mec =
attached.
Even the 442 boots were flakey (no patchbay connections). I =
didn't learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's =
mec
and the 442. We used the mec throughout all testing until the =
end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and =
Paris
would not boot with my other Mec that is loaded to the gills. I =
deleted
the Scherzo drivers, reloaded the new ones I just got, =
uninstalled the
subsystem and reloaded it. Once I changed to the 442 the system =
was fine.
Let me rephrase "Paris would not boot" . . . Actually it would =
usually start
up but no audio was available in the patchbay except with the =
442.
My take is that the introduction of DJ's mec (whether it worked =
or didn't,
let's assume that it worked) was screwy probably by my own =
doing. I
removed it and later shorted a SCSI 2 cable at the Master Mec =
sometime during that
next week. There was smoke in the power supply area so I never =
tried that
Mec again. My other mec was attached at that time. I now think =
it fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio =
on Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine =
when I pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe no =
more than =3D
>usual, but it seemed like an unusually high number to me over =
the last =3D
>few weeks. Errors I'm not familiar with. It will have been 10 =
years in =3D
>November since Paris shipped. I wonder if the lifespan of =
this hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" =
name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I =
sent was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine =
when I pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts =
recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually =
high number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will =
have been =3D
>10=3D20
>years in November since Paris shipped. I wonder if the =
lifespan of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad =
mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact =
next Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple =
on another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to =
fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_0080_01C7FFC1.13352710
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.16525" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I'll also toss out an edumacated guess =
that only=20
the interface portion got fried and all your MEC cards are likely to be =
ok...=20
holla back on that man. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sorry, no spare MEC's around here, in =
fact I'm=20
going to be growing my rig again shortly with a few more EDS cards=20
:)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Say Tom, have you called The Soniq =
about repairing=20
yours... he offers warranty on his work yano :)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>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 message=20
<A href=3D"news:46f9621b@linux">news:46f9621b@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Most absolutely hardware. 3 =
Mecs down for=20
the count.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>No word on the 10 modules that were =
onboard=20
during</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the mishap.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Anyone have a spare mec they can part =
with?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Assamundo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></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=20
message <A =
href=3D"news:46f4fa9a@linux">news:46f4fa9a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll double check =
Aaron.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Continuity is my middle =
name.</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>>=20
wrote in message <A=20
href=3D"news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Dude, if you have 3 toasted MEC's =
I think it=20
VERY likely you had a bad cable that put the hurt on them =
all as you=20
swapped around parts. </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:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Intersted people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. It's=20
not confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT=20
face=3DArial size=3D2>that might 'still work'. The =
hardware=20
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most =
logical at this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with 2 =
mecs loaded=20
to the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and =
bought one from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding =
my default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of =
turmoil looking=20
to get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to =
boot with=20
mecs and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to =
test eds and=20
cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed =
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the =
studio with both=20
computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every =
time it=20
wouldn't boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey =
(no patchbay=20
connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs =
place with the=20
Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used the =
mec=20
throughout all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was =
introduced Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not=20
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my =
original C drive=20
(no default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my =
other Mec that=20
is loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded =
the new ones=20
I just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded =
it. Once I=20
changed to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would =
not boot" . .=20
. Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available =
in the=20
patchbay except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the =
introduction of DJ's=20
mec (whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own doing. =
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted a =
SCSI 2 cable=20
at the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was =
smoke in the=20
power supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My other =
mec was=20
attached at that time. I now think it fried =
something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my =
hopefully unfried=20
mec at another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If =
I'm wrong then=20
we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A =
href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> wrote=20
in message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
all seriousness - THREE bad MEC's??? What's the =
real<BR>likelihood of=20
that? Unless all 3 PSU's got hit hard with a<BR>voltage spike =
or=20
something weird like that, is it really<BR>possible that ALL =
of his=20
MECs went bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at =
_=20
animas _ dot _ net>=20
wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you think =
the one=20
I sent was bad ? It was working fine when I =
pulled<BR>=3D<BR>>it from=20
the rack.=3D20<BR>><BR>>I've noticed a few posts =
recently=20
regarding errors. Maybe no more than =3D<BR>>usual, but it =
seemed=20
like an unusually high number to me over the last =
=3D<BR>>few weeks.=20
Errors I'm not familiar with. It will have been 10 years in=20
=3D<BR>>November since Paris shipped. I wonder if the =
lifespan of=20
this hardware<BR>=3D<BR>>is starting to fade. TG for =
TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" =
<<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote in =
message =3D<BR>>news:46f44c75$1@linux...<BR>> 3 =
bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll =
know for=20
a fact next Tuesday when there's<BR>> time to test a =
couple=20
on another =
system.<BR>><BR>><BR>><BR>> <BR>> I=20
choose Polesoft Lockspam to fight spam, and you?<BR>> =
<A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 =
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do=20
you think the one I sent was =3D<BR>>bad=20
?=3D20<BR>></FONT><FONT face=3D3DArial =
size=3D3D2>It was=20
working fine when I pulled it<BR>=3D<BR>>from =
the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts recently =
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more than =
usual, but it=20
seemed like an unusually high number to<BR>=3D<BR>>me=20
over=3D20<BR>>the last few weeks. Errors I'm not familiar =
with. It=20
will have been =3D<BR>>10=3D20<BR>>years in November =
since Paris=20
shipped. I wonder if the lifespan of=20
this<BR>=3D<BR>>hardware=3D20<BR>>is starting to fade. =
TG for=20
TheSoniq, I =
guess.</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT: 5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid;=20
MARGIN-RIGHT: 0px"><BR>> <DIV>"Tom Bruhl"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A =
href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> <DIV><FONT face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2>time to test a couple on=20
another=3D20<BR>> =20
system.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam =
to fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =3D<BR>>href=3D3D"<A =
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQUOTE></BL=
OCKQUOTE></BODY></HTML>
------=_NextPart_000_0080_01C7FFC1.13352710--
|
|
|
|
| Re: I know I found my problem [message #90569 is a reply to message #90560] |
Tue, 25 September 2007 22:46 |
Neil
Messages: 1645
Registered: April 2006
|
Senior Member |
|
|
Tom, check the "For sale" section of the NG, since someone JUST
posted a bunch'o' Paris gear for sale, including MEC's - if
that doesn't work out for you I have ONE I can lend you, not
for sale, but can lend it to you for a short time if you're
willing to pay for shipoing both ways. Post here to lemme know
if you need that for a favor; at which point we can negotiate
for your firstborn or something lol!
Neil
"Aaron Allen" <know-spam@not_here.dude> wrote:
>
>
>I'll also toss out an edumacated guess that only the interface portion =
>got fried and all your MEC cards are likely to be ok... holla back on =
>that man.=20
>Sorry, no spare MEC's around here, in fact I'm going to be growing my =
>rig again shortly with a few more EDS cards :)
>
>Say Tom, have you called The Soniq about repairing yours... he offers =
>warranty on his work yano :)
>
>AA
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =
>news:46f9621b@linux...
> Most absolutely hardware. 3 Mecs down for the count.
> No word on the 10 modules that were onboard during
> the mishap.
>
> Anyone have a spare mec they can part with?
> Assamundo
>
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =
>news:46f4fa9a@linux...
> I'll double check Aaron.
>
> Continuity is my middle name.
> "Aaron Allen" <know-spam@not_here.dude> wrote in message =
>news:46f4e6c0@linux...
> Dude, if you have 3 toasted MEC's I think it VERY likely you had a
=
>bad cable that put the hurt on them all as you swapped around parts.=20
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =
>news:46f472e2@linux...
> Intersted people,
> I know 3 fried mecs is unlikely. It's not confirmed until =
>Tuesday=20
> when I'll check the two that might 'still work'. The hardware =
>solution
> is seeming to be the most logical at this point. Here's why:
>
> I was working perfectly with 2 mecs loaded to the gills and a =
>442.
> I wanted one more mec and bought one from Deej. Mistakenly,
> I installed it without hiding my default project. Paris freaked
> and I went through days of turmoil looking to get back to where
> I was. Paris refused to boot with mecs and no 442 at that time.
>
> Next I built another comp to test eds and cables and the 442. =20
> Everything went fine. No probs. This seemed promising.
>
> Next I tried again in the studio with both computers and never =
>got a=20
> good Paris boot. Every time it wouldn't boot there was a Mec =
>attached.
> Even the 442 boots were flakey (no patchbay connections). I =
>didn't learn=20
> anything from this effort.
>
> 2 days ago I went to a techs place with the Paris comp, Deej's =
>mec
> and the 442. We used the mec throughout all testing until the =
>end.
> Fresh C drive, fresh Paris install.
> As soon as the 442 was introduced Paris booted. Likely the Deej
> mec is faulty but not necessarily.
>
> Today I went back to my original C drive (no default proj) and =
>Paris
> would not boot with my other Mec that is loaded to the gills. I
=
>deleted
> the Scherzo drivers, reloaded the new ones I just got, =
>uninstalled the
> subsystem and reloaded it. Once I changed to the 442 the system
=
>was fine.
>
> Let me rephrase "Paris would not boot" . . . Actually it would
=
>usually start
> up but no audio was available in the patchbay except with the =
>442.
>
> My take is that the introduction of DJ's mec (whether it worked
=
>or didn't,
> let's assume that it worked) was screwy probably by my own =
>doing. I
> removed it and later shorted a SCSI 2 cable at the Master Mec =
>sometime during that
> next week. There was smoke in the power supply area so I never
=
>tried that
> Mec again. My other mec was attached at that time. I now think
=
>it fried something
> in their too.
>
> I am trying DJs and my hopefully unfried mec at another studio =
>on Tuesday to confirm
> that neither works. If I'm wrong then we're back to software.
>
> It ain't over till it's over.
> Tom
>
>
>
> =20
> "Neil" <IOU@OIU.com> wrote in message news:46f46d03$1@linux...
>
> In all seriousness - THREE bad MEC's??? What's the real
> likelihood of that? Unless all 3 PSU's got hit hard with a
> voltage spike or something weird like that, is it really
> possible that ALL of his MECs went bad?
>
> Neil
>
>
>
> "DJ" <animix _ at _ animas _ dot _ net> wrote:
> >
> >
> >Tom,
> >
> >Do you think the one I sent was bad ? It was working fine =
>when I pulled
> =3D
> >it from the rack.=3D20
> >
> >I've noticed a few posts recently regarding errors. Maybe no
=
>more than =3D
> >usual, but it seemed like an unusually high number to me over
=
>the last =3D
> >few weeks. Errors I'm not familiar with. It will have been 10
=
>years in =3D
> >November since Paris shipped. I wonder if the lifespan of =
>this hardware
> =3D
> >is starting to fade. TG for TheSoniq, I guess.
> >
> >Deej
> >
> > "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
> >news:46f44c75$1@linux...
> > 3 bad mecs.
> >
> > Hmmm?
> >
> > I'll know for a fact next Tuesday when there's
> > time to test a couple on another system.
> >
> >
> >
> >
> > I choose Polesoft Lockspam to fight spam, and you?
> > http://www.polesoft.com/refer.html =20
> >
> ><!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.6000.16525" =
>name=3D3DGENERATOR>
> ><STYLE></STYLE>
> ></HEAD>
> ><BODY bgColor=3D3D#ffffff>
> ><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I =
>sent was =3D
> >bad ?=3D20
> ></FONT><FONT face=3D3DArial size=3D3D2>It was working fine =
>when I pulled it
> =3D
> >from the=3D20
> >rack. </FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few posts
=
>recently =3D
> >regarding errors.=3D20
> >Maybe no more than usual, but it seemed like an unusually =
>high number to
> =3D
> >me over=3D20
> >the last few weeks. Errors I'm not familiar with. It will =
>have been =3D
> >10=3D20
> >years in November since Paris shipped. I wonder if the =
>lifespan of this
> =3D
> >hardware=3D20
> >is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> ><BLOCKQUOTE dir=3D3Dltr=3D20
> >style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
>MARGIN-LEFT: 5px; =3D
> >BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> > <DIV>"Tom Bruhl" <<A=3D20
> > =
>href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =3D
> >in message=3D20
> > <A =
>href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>3 bad =
>mecs.</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact =
>next Tuesday =3D
> >when=3D20
> > there's</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>time to test a couple
=
>on another=3D20
> > system.</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> > <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to
=
>fight spam,
> =3D
> >and=3D20
> > you?<BR><A=3D20
> > =3D
> =
>>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
>fer=3D
> >.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
> >
> >
>
>
><!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.16525" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial size=3D2>I'll also toss out an edumacated guess
=
>that only=20
>the interface portion got fried and all your MEC cards are likely to be
=
>ok...=20
>holla back on that man. </FONT></DIV>
><DIV><FONT face=3DArial size=3D2>Sorry, no spare MEC's around here, in =
>fact I'm=20
>going to be growing my rig again shortly with a few more EDS cards=20
>:)</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>Say Tom, have you called The Soniq =
>about repairing=20
>yours... he offers warranty on his work yano :)</FONT></DIV>
><DIV> </DIV>
><DIV><FONT face=3DArial size=3D2>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 message=20
> <A href=3D"news:46f9621b@linux">news:46f9621b@linux</A>...</DIV>
> <DIV><FONT face=3DArial size=3D2>Most absolutely hardware. 3 =
>Mecs down for=20
> the count.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>No word on the 10 modules that were =
>onboard=20
> during</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>the mishap.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Anyone have a spare mec they can part
=
>
> with?</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Assamundo</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></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=20
> message <A =
>href=3D"news:46f4fa9a@linux">news:46f4fa9a@linux</A>...</DIV>
> <DIV><FONT face=3DArial size=3D2>I'll double check =
>Aaron.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Continuity is my middle =
>name.</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>>=20
> wrote in message <A=20
> href=3D"news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV>
> <DIV><FONT face=3DArial size=3D2>Dude, if you have 3 toasted MEC's
=
>I think it=20
> VERY likely you had a bad cable that put the hurt on them =
>all as you=20
> swapped around parts. </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:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
> <DIV><FONT face=3DArial size=3D2>Intersted people,</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
>unlikely. It's=20
> not confirmed until Tuesday </FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>when I'll check the two =
></FONT><FONT=20
> face=3DArial size=3D2>that might 'still work'. The =
>hardware=20
> solution</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>is seeming to be the most =
>logical at this=20
> point. Here's why:</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>I was working perfectly with 2
=
>mecs loaded=20
> to the gills and a 442.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>I wanted one more mec and =
>bought one from=20
> Deej. Mistakenly,</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>I installed it without hiding =
>my default=20
> project. Paris freaked</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>and I went through days of =
>turmoil looking=20
> to get back to where</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>I was. Paris refused to =
>boot with=20
> mecs and no 442 at that time.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Next I built another comp to =
>test eds and=20
> cables and the 442. </FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
>face=3DArial=20
> size=3D2>fine. No probs. This seemed =
>promising.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Next I tried again in the =
>studio with both=20
> computers and never got a </FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>good Paris boot. Every =
>time it=20
> wouldn't boot there was a Mec attached.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Even the 442 boots were flakey
=
>(no patchbay=20
> connections). I didn't learn </FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>anything from this =
>effort.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs =
>place with the=20
> Paris comp, Deej's mec</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>and the 442. We used the =
>mec=20
> throughout all testing until the end.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris=20
> install.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>As soon as the 442 was =
>introduced Paris=20
> booted. Likely the Deej</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>mec is faulty but not=20
> necessarily.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Today I went back to my =
>original C drive=20
> (no default proj) and Paris</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>would not boot with my =
>other Mec that=20
> is loaded to the gills. I deleted</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded =
>the new ones=20
> I just got, uninstalled the</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>subsystem and reloaded =
>it. Once I=20
> changed to the 442 the system was fine.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would =
>not boot" . .=20
> . Actually it would usually start</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>up but no audio was available =
>in the=20
> patchbay except with the 442.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>My take is that the =
>introduction of DJ's=20
> mec (whether it worked or didn't,</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
></FONT><FONT=20
> face=3DArial size=3D2>was screwy probably by my own doing. =
>
> I</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>removed it and later shorted a
=
>SCSI 2 cable=20
> at the Master Mec sometime during that</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>next week. There was =
>smoke in the=20
> power supply area so I never tried that</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Mec again. My other =
>mec was=20
> attached at that time. I now think it fried =
>something</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>I am trying DJs and my =
>hopefully unfried=20
> mec at another studio on Tuesday to confirm</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>that neither works. If =
>I'm wrong then=20
> we're back to software.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>It ain't over till it's =
>over.</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>
> <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>"Neil" <<A =
>href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> wrote=20
> in message <A=20
> =
>href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
> all seriousness - THREE bad MEC's??? What's the =
>real<BR>likelihood of=20
> that? Unless all 3 PSU's got hit hard with a<BR>voltage spike
=
>or=20
> something weird like that, is it really<BR>possible that ALL =
>of his=20
> MECs went bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at =
>_=20
> animas _ dot _ net>=20
> wrote:<BR>><BR>><BR>>Tom,<BR>><BR>>Do you think =
>the one=20
> I sent was bad ? It was working fine when I =
>pulled<BR>=3D<BR>>it from=20
> the rack.=3D20<BR>><BR>>I've noticed a few posts =
>recently=20
> regarding errors. Maybe no more than =3D<BR>>usual, but it =
>seemed=20
> like an unusually high number to me over the last =
>=3D<BR>>few weeks.=20
> Errors I'm not familiar with. It will have been 10 years in=20
> =3D<BR>>November since Paris shipped. I wonder if the =
>lifespan of=20
> this hardware<BR>=3D<BR>>is starting to fade. TG for =
>TheSoniq, I=20
> guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" =
><<A=20
> =
>href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote in =
>
> message =3D<BR>>news:46f44c75$1@linux...<BR>> 3 =
>bad=20
> mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll =
>know for=20
> a fact next Tuesday when there's<BR>> time to test a =
>couple=20
> on another =
>system.<BR>><BR>><BR>><BR>><BR>> I=20
> choose Polesoft Lockspam to fight spam, and you?<BR>> =
><A=20
> =
>href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
>.html</A> =20
> <BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 =
>
> =
>Transitional//EN"><BR>><HTML><HEAD><BR>><META=20
> http-equiv=3D3DContent-Type content=3D3D"text/html;=20
> =3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
>content=3D3D"MSHTML=20
> 6.00.6000.16525"=20
> =
>name=3D3DGENERATOR><BR>><STYLE></STYLE><BR>></HEA=
>D><BR>><BODY=20
> bgColor=3D3D#ffffff><BR>><DIV><FONT =
>face=3D3DArial=20
> =
>size=3D3D2>Tom,</FONT></DIV><BR>><DIV><FONT=20
> face=3D3DArial size=3D3D2></FONT>=20
> </DIV><BR>><DIV><FONT face=3D3DArial =
>size=3D3D2>Do=20
> you think the one I sent was =3D<BR>>bad=20
> ?=3D20<BR>></FONT><FONT face=3D3DArial =
>size=3D3D2>It was=20
> working fine when I pulled it<BR>=3D<BR>>from =
>the=3D20<BR>>rack.=20
> </FONT></DIV><BR>><DIV><FONT =
>face=3D3DArial=20
> size=3D3D2></FONT> =
></DIV><BR>><DIV><FONT=20
> face=3D3DArial size=3D3D2>I've noticed a few posts recently =
>
> =3D<BR>>regarding errors.=3D20<BR>>Maybe no more than =
>usual, but it=20
> seemed like an unusually high number to<BR>=3D<BR>>me=20
> over=3D20<BR>>the last few weeks. Errors I'm not familiar =
>with. It=20
> will have been =3D<BR>>10=3D20<BR>>years in November =
>since Paris=20
> shipped. I wonder if the lifespan of=20
> this<BR>=3D<BR>>hardware=3D20<BR>>is starting to fade. =
>TG for=20
> TheSoniq, I =
>guess.</FONT></DIV><BR>><DIV><FONT=20
> face=3D3DArial size=3D3D2></FONT>=20
> </DIV><BR>><DIV><FONT face=3D3DArial=20
> =
>size=3D3D2>Deej</FONT></DIV><BR>><DIV><FONT=20
> face=3D3DArial size=3D3D2></FONT>=20
> </DIV><BR>><BLOCKQUOTE=20
> dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
>PADDING-LEFT: 5px;=20
> MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid;=20
> MARGIN-RIGHT: 0px"><BR>> <DIV>"Tom Bruhl"=20
> <<A=3D20<BR>> href=3D3D"<A=20
> =
>href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
>o@comcast.net">arpegio@comcast.net</A</A>>>=20
> wrote =3D<BR>>in message=3D20<BR>> <A =
>href=3D3D"<A=20
> =
>href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
>f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
>> =20
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
> mecs.</FONT></DIV><BR>> =
><DIV><FONT=20
> face=3D3DArial size=3D3D2></FONT> =
></DIV><BR>> =20
> <DIV><FONT face=3D3DArial=20
> size=3D3D2>Hmmm?</FONT></DIV><BR>> =20
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> =
>
> </DIV><BR>> <DIV><FONT face=3D3DArial=20
> size=3D3D2>I'll know for a fact next Tuesday=20
> =3D<BR>>when=3D20<BR>> =20
> there's</FONT></DIV><BR>> =
><DIV><FONT=20
> face=3D3DArial size=3D3D2>time to test a couple on=20
> another=3D20<BR>> =20
> system.</FONT></DIV><BR>> =
><DIV><FONT=20
> face=3D3DArial size=3D3D2></FONT> =
></DIV><BR>> =20
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> =
>
> </DIV><BR>> <DIV><FONT=20
> size=3D3D2><BR><BR>I choose Polesoft Lockspam =
>to fight=20
> spam,<BR>=3D<BR>>and=3D20<BR>> =20
> you?<BR><A=3D20<BR>> =3D<BR>>href=3D3D"<A =
>
> =
>href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
>'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>>=3D<BR>>.html</A>=20
> =
></FONT></DIV></BLOCKQUOTE></BODY></HTML><BR=
>>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BL=
>OCKQUOTE></BODY></HTML>
>
>
|
|
|
|
| Re: I know I found my problem [message #90575 is a reply to message #90560] |
Wed, 26 September 2007 00:53 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0123_01C7FFF0.DBC4CC10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Aaron,
Thanks, I won't know about the modules until some new Mecs get delivered =
here.
I think I have the four I need almost on their way from multiple =
sources.
It looks like a chip in the master section of the scsi scorched mec got =
hit bad. We're
looking for the chip now. The other mecs may have less of a problem. =
Maybe some DC=20
down the WC line? Just a guess. Everything was AC grounded and no =
polarity shift.
We learned there's all kinds of protection fuses in line on the master =
section. It seems 'they' weren't
fried but the expensive stuff right after them was. . .
Tom
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f9cf56@linux...
I'll also toss out an edumacated guess that only the interface portion =
got fried and all your MEC cards are likely to be ok... holla back on =
that man.=20
Sorry, no spare MEC's around here, in fact I'm going to be growing my =
rig again shortly with a few more EDS cards :)
Say Tom, have you called The Soniq about repairing yours... he offers =
warranty on his work yano :)
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f9621b@linux...
Most absolutely hardware. 3 Mecs down for the count.
No word on the 10 modules that were onboard during
the mishap.
Anyone have a spare mec they can part with?
Assamundo
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f4fa9a@linux...
I'll double check Aaron.
Continuity is my middle name.
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f4e6c0@linux...
Dude, if you have 3 toasted MEC's I think it VERY likely you had =
a bad cable that put the hurt on them all as you swapped around parts.=20
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until =
Tuesday=20
when I'll check the two that might 'still work'. The hardware =
solution
is seeming to be the most logical at this point. Here's why:
I was working perfectly with 2 mecs loaded to the gills and a =
442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris =
freaked
and I went through days of turmoil looking to get back to =
where
I was. Paris refused to boot with mecs and no 442 at that =
time.
Next I built another comp to test eds and cables and the 442. =
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and never =
got a=20
good Paris boot. Every time it wouldn't boot there was a Mec =
attached.
Even the 442 boots were flakey (no patchbay connections). I =
didn't learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, Deej's =
mec
and the 442. We used the mec throughout all testing until the =
end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the =
Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) and =
Paris
would not boot with my other Mec that is loaded to the gills. =
I deleted
the Scherzo drivers, reloaded the new ones I just got, =
uninstalled the
subsystem and reloaded it. Once I changed to the 442 the =
system was fine.
Let me rephrase "Paris would not boot" . . . Actually it =
would usually start
up but no audio was available in the patchbay except with the =
442.
My take is that the introduction of DJ's mec (whether it =
worked or didn't,
let's assume that it worked) was screwy probably by my own =
doing. I
removed it and later shorted a SCSI 2 cable at the Master Mec =
sometime during that
next week. There was smoke in the power supply area so I =
never tried that
Mec again. My other mec was attached at that time. I now =
think it fried something
in their too.
I am trying DJs and my hopefully unfried mec at another studio =
on Tuesday to confirm
that neither works. If I'm wrong then we're back to software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message =
news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine =
when I pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe =
no more than =3D
>usual, but it seemed like an unusually high number to me =
over the last =3D
>few weeks. Errors I'm not familiar with. It will have been =
10 years in =3D
>November since Paris shipped. I wonder if the lifespan of =
this hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" =
name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one I =
sent was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working fine =
when I pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few =
posts recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually =
high number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will =
have been =3D
>10=3D20
>years in November since Paris shipped. I wonder if the =
lifespan of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad =
mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a fact =
next Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a =
couple on another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam =
to fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_0123_01C7FFF0.DBC4CC10
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Aaron,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks, I won't know about the modules =
until some=20
new Mecs get delivered here.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I think I have the four I need almost =
on their way=20
from multiple sources.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It looks like a chip in the master =
section of the=20
scsi scorched mec got hit bad. We're</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>looking for the chip now. The =
other=20
</FONT><FONT face=3DArial size=3D2>mecs may have less of a =
problem. Maybe some=20
DC </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>down the WC line? Just a =
guess. =20
Everything was AC grounded and no polarity shift.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We learned there's all kinds of =
protection fuses in=20
line on the master section. It seems 'they' weren't</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>fried but the expensive stuff right =
after them was.=20
.. .</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>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></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 in=20
message <A =
href=3D"news:46f9cf56@linux">news:46f9cf56@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll also toss out an edumacated =
guess that only=20
the interface portion got fried and all your MEC cards are likely to =
be ok...=20
holla back on that man. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sorry, no spare MEC's around here, in =
fact I'm=20
going to be growing my rig again shortly with a few more EDS cards=20
:)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Say Tom, have you called The Soniq =
about=20
repairing yours... he offers warranty on his work yano :)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>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:46f9621b@linux">news:46f9621b@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Most absolutely hardware. 3 =
Mecs down for=20
the count.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>No word on the 10 modules that were =
onboard=20
during</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the mishap.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Anyone have a spare mec they can =
part=20
with?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Assamundo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></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=20
message <A =
href=3D"news:46f4fa9a@linux">news:46f4fa9a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll double check =
Aaron.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Continuity is my middle =
name.</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>>=20
wrote in message <A=20
href=3D"news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Dude, if you have 3 toasted =
MEC's I think=20
it VERY likely you had a bad cable that put the hurt on them =
all as=20
you swapped around parts. </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 <A =
href=3D"news:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Intersted =
people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. =20
It's not confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT=20
face=3DArial size=3D2>that might 'still work'. The =
hardware=20
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most =
logical at this=20
point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly with =
2 mecs=20
loaded to the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and =
bought one from=20
Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without hiding =
my default=20
project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of =
turmoil=20
looking to get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused to =
boot with=20
mecs and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp to =
test eds and=20
cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went </FONT><FONT =
face=3DArial=20
size=3D2>fine. No probs. This seemed =
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the =
studio with=20
both computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. Every =
time it=20
wouldn't boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were =
flakey (no=20
patchbay connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a techs =
place with=20
the Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used =
the mec=20
throughout all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was =
introduced Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not=20
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my =
original C drive=20
(no default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my =
other Mec=20
that is loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, reloaded =
the new=20
ones I just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded =
it. Once I=20
changed to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris would =
not boot" .=20
. . Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was available =
in the=20
patchbay except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the =
introduction of DJ's=20
mec (whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it worked) =
</FONT><FONT=20
face=3DArial size=3D2>was screwy probably by my own =
doing. =20
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later shorted =
a SCSI 2=20
cable at the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was =
smoke in the=20
power supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My =
other mec was=20
attached at that time. I now think it fried=20
something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my =
hopefully unfried=20
mec at another studio on Tuesday to confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. If =
I'm wrong=20
then we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's=20
over.</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>
<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>"Neil" <<A =
href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>>=20
wrote in message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
all seriousness - THREE bad MEC's??? What's the =
real<BR>likelihood=20
of that? Unless all 3 PSU's got hit hard with a<BR>voltage =
spike or=20
something weird like that, is it really<BR>possible that ALL =
of his=20
MECs went bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ =
at _=20
animas _ dot _ net>=20
wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you =
think the=20
one I sent was bad ? It was working fine when I=20
pulled<BR>=3D<BR>>it from the =
rack.=3D20<BR>><BR>>I've noticed=20
a few posts recently regarding errors. Maybe no more than=20
=3D<BR>>usual, but it seemed like an unusually high =
number to me=20
over the last =3D<BR>>few weeks. Errors I'm not familiar =
with. It=20
will have been 10 years in =3D<BR>>November since Paris =
shipped. I=20
wonder if the lifespan of this hardware<BR>=3D<BR>>is =
starting to=20
fade. TG for TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" =
<<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote=20
in message =3D<BR>>news:46f44c75$1@linux...<BR>> =
3 bad=20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll =
know=20
for a fact next Tuesday when there's<BR>> time to =
test a=20
couple on another=20
system.<BR>><BR>><BR>><BR>> <BR>> I =
choose=20
Polesoft Lockspam to fight spam, and you?<BR>> <A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML =
4.0=20
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do=20
you think the one I sent was =3D<BR>>bad=20
?=3D20<BR>></FONT><FONT face=3D3DArial =
size=3D3D2>It was=20
working fine when I pulled it<BR>=3D<BR>>from =
the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts =
recently=20
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more than =
usual, but=20
it seemed like an unusually high number to<BR>=3D<BR>>me=20
over=3D20<BR>>the last few weeks. Errors I'm not familiar =
with. It=20
will have been =3D<BR>>10=3D20<BR>>years in November =
since Paris=20
shipped. I wonder if the lifespan of=20
this<BR>=3D<BR>>hardware=3D20<BR>>is starting to fade. =
TG for=20
TheSoniq, I=20
guess.</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT: 5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT: 0px"><BR>> <DIV>"Tom Bruhl"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A =
href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial =
size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2>time to test a couple on=20
another=3D20<BR>> =20
system.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial =
size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft Lockspam =
to fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQUOTE></BL=
OCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0123_01C7FFF0.DBC4CC10--
|
|
|
|
| Re: I know I found my problem [message #90576 is a reply to message #90569] |
Wed, 26 September 2007 00:56 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_012F_01C7FFF1.28AFA770
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Neil,
Thanks. It seems Mecs should be floating in so I
shouldn't need to borrow yours. Thanks a lot for your offer.
Tom
"Neil" <OIUOIU@OIU.com> wrote in message news:46f9f242$1@linux...
Tom, check the "For sale" section of the NG, since someone JUST
posted a bunch'o' Paris gear for sale, including MEC's - if
that doesn't work out for you I have ONE I can lend you, not
for sale, but can lend it to you for a short time if you're
willing to pay for shipoing both ways. Post here to lemme know
if you need that for a favor; at which point we can negotiate
for your firstborn or something lol! =20
Neil
"Aaron Allen" <know-spam@not_here.dude> wrote:
>
>
>I'll also toss out an edumacated guess that only the interface =
portion =3D
>got fried and all your MEC cards are likely to be ok... holla back on =
=3D
>that man.=3D20
>Sorry, no spare MEC's around here, in fact I'm going to be growing my =
=3D
>rig again shortly with a few more EDS cards :)
>
>Say Tom, have you called The Soniq about repairing yours... he offers =
=3D
>warranty on his work yano :)
>
>AA
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f9621b@linux...
> Most absolutely hardware. 3 Mecs down for the count.
> No word on the 10 modules that were onboard during
> the mishap.
>
> Anyone have a spare mec they can part with?
> Assamundo
>
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f4fa9a@linux...
> I'll double check Aaron.
>
> Continuity is my middle name.
> "Aaron Allen" <know-spam@not_here.dude> wrote in message =3D
>news:46f4e6c0@linux...
> Dude, if you have 3 toasted MEC's I think it VERY likely you =
had a
=3D
>bad cable that put the hurt on them all as you swapped around =
parts.=3D20
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f472e2@linux...
> Intersted people,
> I know 3 fried mecs is unlikely. It's not confirmed until =
=3D
>Tuesday=3D20
> when I'll check the two that might 'still work'. The =
hardware =3D
>solution
> is seeming to be the most logical at this point. Here's why:
>
> I was working perfectly with 2 mecs loaded to the gills and a =
=3D
>442.
> I wanted one more mec and bought one from Deej. Mistakenly,
> I installed it without hiding my default project. Paris =
freaked
> and I went through days of turmoil looking to get back to =
where
> I was. Paris refused to boot with mecs and no 442 at that =
time.
>
> Next I built another comp to test eds and cables and the 442. =
=3D20
> Everything went fine. No probs. This seemed promising.
>
> Next I tried again in the studio with both computers and =
never =3D
>got a=3D20
> good Paris boot. Every time it wouldn't boot there was a Mec =
=3D
>attached.
> Even the 442 boots were flakey (no patchbay connections). I =
=3D
>didn't learn=3D20
> anything from this effort.
>
> 2 days ago I went to a techs place with the Paris comp, =
Deej's =3D
>mec
> and the 442. We used the mec throughout all testing until =
the =3D
>end.
> Fresh C drive, fresh Paris install.
> As soon as the 442 was introduced Paris booted. Likely the =
Deej
> mec is faulty but not necessarily.
>
> Today I went back to my original C drive (no default proj) =
and =3D
>Paris
> would not boot with my other Mec that is loaded to the gills. =
I
=3D
>deleted
> the Scherzo drivers, reloaded the new ones I just got, =3D
>uninstalled the
> subsystem and reloaded it. Once I changed to the 442 the =
system
=3D
>was fine.
>
> Let me rephrase "Paris would not boot" . . . Actually it =
would
=3D
>usually start
> up but no audio was available in the patchbay except with the =
=3D
>442.
>
> My take is that the introduction of DJ's mec (whether it =
worked
=3D
>or didn't,
> let's assume that it worked) was screwy probably by my own =
=3D
>doing. I
> removed it and later shorted a SCSI 2 cable at the Master Mec =
=3D
>sometime during that
> next week. There was smoke in the power supply area so I =
never
=3D
>tried that
> Mec again. My other mec was attached at that time. I now =
think
=3D
>it fried something
> in their too.
>
> I am trying DJs and my hopefully unfried mec at another =
studio =3D
>on Tuesday to confirm
> that neither works. If I'm wrong then we're back to =
software.
>
> It ain't over till it's over.
> Tom
>
>
>
> =3D20
> "Neil" <IOU@OIU.com> wrote in message =
news:46f46d03$1@linux...
>
> In all seriousness - THREE bad MEC's??? What's the real
> likelihood of that? Unless all 3 PSU's got hit hard with a
> voltage spike or something weird like that, is it really
> possible that ALL of his MECs went bad?
>
> Neil
>
>
>
> "DJ" <animix _ at _ animas _ dot _ net> wrote:
> >
> >
> >Tom,
> >
> >Do you think the one I sent was bad ? It was working fine =
=3D
>when I pulled
> =3D3D
> >it from the rack.=3D3D20
> >
> >I've noticed a few posts recently regarding errors. Maybe =
no
=3D
>more than =3D3D
> >usual, but it seemed like an unusually high number to me =
over
=3D
>the last =3D3D
> >few weeks. Errors I'm not familiar with. It will have been =
10
=3D
>years in =3D3D
> >November since Paris shipped. I wonder if the lifespan of =
=3D
>this hardware
> =3D3D
> >is starting to fade. TG for TheSoniq, I guess.
> >
> >Deej
> >
> > "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D3D
> >news:46f44c75$1@linux...
> > 3 bad mecs.
> >
> > Hmmm?
> >
> > I'll know for a fact next Tuesday when there's
> > time to test a couple on another system.
> >
> >
> >
> >
> > I choose Polesoft Lockspam to fight spam, and you?
> > http://www.polesoft.com/refer.html =3D20
> >
> ><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 =3D
>Transitional//EN">
> ><HTML><HEAD>
> ><META http-equiv=3D3D3DContent-Type =
content=3D3D3D"text/html; =3D3D
> >charset=3D3D3Diso-8859-1">
> ><META content=3D3D3D"MSHTML 6.00.6000.16525" =3D
>name=3D3D3DGENERATOR>
> ><STYLE></STYLE>
> ></HEAD>
> ><BODY bgColor=3D3D3D#ffffff>
> ><DIV><FONT face=3D3D3DArial size=3D3D3D2>Tom,</FONT></DIV>
> ><DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> </DIV>
> ><DIV><FONT face=3D3D3DArial size=3D3D3D2>Do you think the =
one I =3D
>sent was =3D3D
> >bad ?=3D3D20
> ></FONT><FONT face=3D3D3DArial size=3D3D3D2>It was working =
fine =3D
>when I pulled it
> =3D3D
> >from the=3D3D20
> >rack. </FONT></DIV>
> ><DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> </DIV>
> ><DIV><FONT face=3D3D3DArial size=3D3D3D2>I've noticed a =
few posts
=3D
>recently =3D3D
> >regarding errors.=3D3D20
> >Maybe no more than usual, but it seemed like an unusually =
=3D
>high number to
> =3D3D
> >me over=3D3D20
> >the last few weeks. Errors I'm not familiar with. It will =
=3D
>have been =3D3D
> >10=3D3D20
> >years in November since Paris shipped. I wonder if the =3D
>lifespan of this
> =3D3D
> >hardware=3D3D20
> >is starting to fade. TG for TheSoniq, I =
guess.</FONT></DIV>
> ><DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> </DIV>
> ><DIV><FONT face=3D3D3DArial size=3D3D3D2>Deej</FONT></DIV>
> ><DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> </DIV>
> ><BLOCKQUOTE dir=3D3D3Dltr=3D3D20
> >style=3D3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =3D
>MARGIN-LEFT: 5px; =3D3D
> >BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> > <DIV>"Tom Bruhl" <<A=3D3D20
> > =3D
>href=3D3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote =3D3D
> >in message=3D3D20
> > <A =3D
>href=3D3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> > <DIV><FONT face=3D3D3DArial size=3D3D3D2>3 bad =3D
>mecs.</FONT></DIV>
> > <DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> </DIV>
> > <DIV><FONT face=3D3D3DArial =
size=3D3D3D2>Hmmm?</FONT></DIV>
> > <DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> </DIV>
> > <DIV><FONT face=3D3D3DArial size=3D3D3D2>I'll know for a =
fact =3D
>next Tuesday =3D3D
> >when=3D3D20
> > there's</FONT></DIV>
> > <DIV><FONT face=3D3D3DArial size=3D3D3D2>time to test a =
couple
=3D
>on another=3D3D20
> > system.</FONT></DIV>
> > <DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> </DIV>
> > <DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> </DIV>
> > <DIV><FONT size=3D3D3D2><BR><BR>I choose Polesoft =
Lockspam to
=3D
>fight spam,
> =3D3D
> >and=3D3D20
> > you?<BR><A=3D3D20
> > =3D3D
> =3D
=
>>href=3D3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com=
/re=3D
>fer=3D3D
> >.html</A> </FONT></DIV></BLOCKQUOTE></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.6000.16525" name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>I'll also toss out an edumacated =
guess
=3D
>that only=3D20
>the interface portion got fried and all your MEC cards are likely to =
be
=3D
>ok...=3D20
>holla back on that man. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Sorry, no spare MEC's around =
here, in =3D
>fact I'm=3D20
>going to be growing my rig again shortly with a few more EDS =
cards=3D20
>:)</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Say Tom, have you called The =
Soniq =3D
>about repairing=3D20
>yours... he offers warranty on his work yano :)</FONT></DIV>
><DIV> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>AA</FONT></DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote =3D
>in message=3D20
> <A href=3D3D"news:46f9621b@linux">news:46f9621b@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Most absolutely hardware. 3 =
=3D
>Mecs down for=3D20
> the count.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>No word on the 10 modules that =
were =3D
>onboard=3D20
> during</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>the mishap.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Anyone have a spare mec they =
can part
=3D
>
> with?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Assamundo</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <BLOCKQUOTE dir=3D3Dltr=3D20
> style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
=3D
>wrote in=3D20
> message <A =3D
>href=3D3D"news:46f4fa9a@linux">news:46f4fa9a@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll double check =3D
>Aaron.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Continuity is my middle =3D
>name.</FONT></DIV>
> <BLOCKQUOTE dir=3D3Dltr=3D20
> style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Aaron Allen" <<A=3D20
> =3D
=
>href=3D3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>>=3D=
20
> wrote in message <A=3D20
> href=3D3D"news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Dude, if you have 3 =
toasted MEC's
=3D
>I think it=3D20
> VERY likely you had a bad cable that put the hurt on them =3D
>all as you=3D20
> swapped around parts. </FONT></DIV>
> <BLOCKQUOTE dir=3D3Dltr=3D20
> style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px;
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =3D
>wrote in=3D20
> message <A =3D
>href=3D3D"news:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Intersted =
people,</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I know 3 fried mecs is =
=3D
>unlikely. It's=3D20
> not confirmed until Tuesday </FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>when I'll check the two =
=3D
></FONT><FONT=3D20
> face=3D3DArial size=3D3D2>that might 'still work'. The =3D
>hardware=3D20
> solution</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>is seeming to be the =
most =3D
>logical at this=3D20
> point. Here's why:</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I was working perfectly =
with 2
=3D
>mecs loaded=3D20
> to the gills and a 442.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I wanted one more mec =
and =3D
>bought one from=3D20
> Deej. Mistakenly,</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I installed it without =
hiding =3D
>my default=3D20
> project. Paris freaked</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>and I went through days =
of =3D
>turmoil looking=3D20
> to get back to where</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I was. Paris refused to =
=3D
>boot with=3D20
> mecs and no 442 at that time.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Next I built another =
comp to =3D
>test eds and=3D20
> cables and the 442. </FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Everything went =
</FONT><FONT =3D
>face=3D3DArial=3D20
> size=3D3D2>fine. No probs. This seemed =3D
>promising.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Next I tried again in =
the =3D
>studio with both=3D20
> computers and never got a </FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>good Paris boot. Every =
=3D
>time it=3D20
> wouldn't boot there was a Mec attached.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Even the 442 boots were =
flakey
=3D
>(no patchbay=3D20
> connections). I didn't learn </FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>anything from this =3D
>effort.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>2 days ago I went to a =
techs =3D
>place with the=3D20
> Paris comp, Deej's mec</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>and the 442. We used the =
=3D
>mec=3D20
> throughout all testing until the end.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Fresh C drive, fresh =
Paris=3D20
> install.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>As soon as the 442 was =
=3D
>introduced Paris=3D20
> booted. Likely the Deej</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>mec is faulty but =
not=3D20
> necessarily.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Today I went back to my =
=3D
>original C drive=3D20
> (no default proj) and Paris</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>would not boot with my =
=3D
>other Mec that=3D20
> is loaded to the gills. I deleted</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>the Scherzo drivers, =
reloaded =3D
>the new ones=3D20
> I just got, uninstalled the</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>subsystem and reloaded =
=3D
>it. Once I=3D20
> changed to the 442 the system was fine.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Let me rephrase "Paris =
would =3D
>not boot" . .=3D20
> . Actually it would usually start</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>up but no audio was =
available =3D
>in the=3D20
> patchbay except with the 442.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>My take is that the =3D
>introduction of DJ's=3D20
> mec (whether it worked or didn't,</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>let's assume that it =
worked) =3D
></FONT><FONT=3D20
> face=3D3DArial size=3D3D2>was screwy probably by my own =
doing. =3D
>
> I</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>removed it and later =
shorted a
=3D
>SCSI 2 cable=3D20
> at the Master Mec sometime during that</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>next week. There was =3D
>smoke in the=3D20
> power supply area so I never tried that</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Mec again. My other =3D
>mec was=3D20
> attached at that time. I now think it fried =3D
>something</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>in their =
too.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I am trying DJs and my =
=3D
>hopefully unfried=3D20
> mec at another studio on Tuesday to confirm</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>that neither works. If =
=3D
>I'm wrong then=3D20
> we're back to software.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>It ain't over till it's =
=3D
>over.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Tom</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2> </FONT> </DIV>
> <BLOCKQUOTE=3D20
> style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: =3D
>5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Neil" <<A =3D
>href=3D3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> wrote=3D20
> in message <A=3D20
> =3D
=
>href=3D3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>I=
n=3D20
> all seriousness - THREE bad MEC's??? What's the =3D
>real<BR>likelihood of=3D20
> that? Unless all 3 PSU's got hit hard with a<BR>voltage =
spike
=3D
>or=3D20
> something weird like that, is it really<BR>possible that =
ALL =3D
>of his=3D20
> MECs went bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at =
=3D
>_=3D20
> animas _ dot _ net>=3D20
> wrote:<BR>><BR>><BR>>Tom,<BR>><BR>>Do you think =3D
>the one=3D20
> I sent was bad ? It was working fine when I =3D
>pulled<BR>=3D3D<BR>>it from=3D20
> the rack.=3D3D20<BR>><BR>>I've noticed a few posts =3D
>recently=3D20
> regarding errors. Maybe no more than =3D3D<BR>>usual, but =
it =3D
>seemed=3D20
> like an unusually high number to me over the last =3D
>=3D3D<BR>>few weeks.=3D20
> Errors I'm not familiar with. It will have been 10 years =
in=3D20
> =3D3D<BR>>November since Paris shipped. I wonder if the =3D
>lifespan of=3D20
> this hardware<BR>=3D3D<BR>>is starting to fade. TG for =3D
>TheSoniq, I=3D20
> guess.<BR>><BR>>Deej<BR>><BR>> "Tom Bruhl" =3D
><<A=3D20
> =3D
>href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in =3D
>
> message =3D3D<BR>>news:46f44c75$1@linux...<BR>> 3 =3D
>bad=3D20
> mecs.<BR>><BR>> Hmmm?<BR>><BR>> I'll =3D
>know for=3D20
> a fact next Tuesday when there's<BR>> time to test a =3D
>couple=3D20
> on another =3D
>system.<BR>><BR>><BR>><BR>><BR>> I=3D20
> choose Polesoft Lockspam to fight spam, and you?<BR>> =3D
><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> =3D20
> <BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 =3D
>
> =3D
>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.6000.16525"=3D20
> =3D
>name=3D3D3DGENERATOR><BR>><STYLE></STYLE><BR>></HEA=3D
>D><BR>><BODY=3D20
> bgColor=3D3D3D#ffffff><BR>><DIV><FONT =3D
>face=3D3D3DArial=3D20
> =3D
>size=3D3D3D2>Tom,</FONT></DIV><BR>><DIV><FONT=3D20
> face=3D3D3DArial size=3D3D3D2></FONT>=3D20
> </DIV><BR>><DIV><FONT face=3D3D3DArial =3D
>size=3D3D3D2>Do=3D20
> you think the one I sent was =3D3D<BR>>bad=3D20
> ?=3D3D20<BR>></FONT><FONT face=3D3D3DArial =3D
>size=3D3D3D2>It was=3D20
> working fine when I pulled it<BR>=3D3D<BR>>from =3D
>the=3D3D20<BR>>rack.=3D20
> </FONT></DIV><BR>><DIV><FONT =3D
>face=3D3D3DArial=3D20
> size=3D3D3D2></FONT> =3D
></DIV><BR>><DIV><FONT=3D20
> face=3D3D3DArial size=3D3D3D2>I've noticed a few posts =
recently =3D
>
> =3D3D<BR>>regarding errors.=3D3D20<BR>>Maybe no more than =
=3D
>usual, but it=3D20
> seemed like an unusually high number =
to<BR>=3D3D<BR>>me=3D20
> over=3D3D20<BR>>the last few weeks. Errors I'm not familiar =
=3D
>with. It=3D20
> will have been =3D3D<BR>>10=3D3D20<BR>>years in November =
=3D
>since Paris=3D20
> shipped. I wonder if the lifespan of=3D20
> this<BR>=3D3D<BR>>hardware=3D3D20<BR>>is starting to fade. =
=3D
>TG for=3D20
> TheSoniq, I =3D
>guess.</FONT></DIV><BR>><DIV><FONT=3D20
> face=3D3D3DArial size=3D3D3D2></FONT>=3D20
> </DIV><BR>><DIV><FONT face=3D3D3DArial=3D20
> =3D
>size=3D3D3D2>Deej</FONT></DIV><BR>><DIV><FONT=3D20
> face=3D3D3DArial size=3D3D3D2></FONT>=3D20
> </DIV><BR>><BLOCKQUOTE=3D20
> dir=3D3D3Dltr=3D3D20<BR>>style=3D3D3D"PADDING-RIGHT: 0px; =
=3D
>PADDING-LEFT: 5px;=3D20
> MARGIN-LEFT: 5px; =3D3D<BR>>BORDER-LEFT: #000000 2px =
solid;=3D20
> MARGIN-RIGHT: 0px"><BR>> <DIV>"Tom 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>> <A =3D
>href=3D3D3D"<A=3D20
> =3D
=
>href=3D3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news=
:46=3D
>f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=3D
>> =3D20
> <DIV><FONT face=3D3D3DArial size=3D3D3D2>3 bad=3D20
> mecs.</FONT></DIV><BR>> =3D
><DIV><FONT=3D20
> face=3D3D3DArial size=3D3D3D2></FONT> =3D
></DIV><BR>> =3D20
> <DIV><FONT face=3D3D3DArial=3D20
> size=3D3D3D2>Hmmm?</FONT></DIV><BR>> =3D20
> <DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> =3D
>
> </DIV><BR>> <DIV><FONT face=3D3D3DArial=3D20
> size=3D3D3D2>I'll know for a fact next Tuesday=3D20
> =3D3D<BR>>when=3D3D20<BR>> =3D20
> there's</FONT></DIV><BR>> =3D
><DIV><FONT=3D20
> face=3D3D3DArial size=3D3D3D2>time to test a couple on=3D20
> another=3D3D20<BR>> =3D20
> system.</FONT></DIV><BR>> =3D
><DIV><FONT=3D20
> face=3D3D3DArial size=3D3D3D2></FONT> =3D
></DIV><BR>> =3D20
> <DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> =3D
>
> </DIV><BR>> <DIV><FONT=3D20
> size=3D3D3D2><BR><BR>I choose Polesoft Lockspam =3D
>to fight=3D20
> spam,<BR>=3D3D<BR>>and=3D3D20<BR>> =3D20
> you?<BR><A=3D3D20<BR>> =3D3D<BR>>href=3D3D3D"<A =3D
>
> =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></BLOCKQUOTE></BODY></HTML><BR=3D
=
>>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BL=3D
>OCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_012F_01C7FFF1.28AFA770
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Neil,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks. It seems Mecs should be =
floating in=20
so I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>shouldn't need to borrow yours. Thanks =
a lot=20
for your offer.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Neil" <<A =
href=3D"mailto:OIUOIU@OIU.com">OIUOIU@OIU.com</A>> wrote=20
in message <A=20
=
href=3D"news:46f9f242$1@linux">news:46f9f242$1@linux</A>...</DIV><BR>Tom,=
check=20
the "For sale" section of the NG, since someone JUST<BR>posted a =
bunch'o'=20
Paris gear for sale, including MEC's - if<BR>that doesn't work out for =
you I=20
have ONE I can lend you, not<BR>for sale, but can lend it to you for a =
short=20
time if you're<BR>willing to pay for shipoing both ways. Post here to =
lemme=20
know<BR>if you need that for a favor; at which point we can =
negotiate<BR>for=20
your firstborn or something lol! =20
<BR><BR>Neil<BR><BR><BR>"Aaron Allen" <<A=20
=
href=3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>>=20
wrote:<BR>><BR>><BR>>I'll also toss out an edumacated guess =
that only=20
the interface portion =3D<BR>>got fried and all your MEC cards are =
likely to=20
be ok... holla back on =3D<BR>>that man.=3D20<BR>>Sorry, no =
spare MEC's=20
around here, in fact I'm going to be growing my =3D<BR>>rig again =
shortly=20
with a few more EDS cards :)<BR>><BR>>Say Tom, have you called =
The Soniq=20
about repairing yours... he offers =3D<BR>>warranty on his work =
yano=20
:)<BR>><BR>>AA<BR>> "Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
=3D<BR>>news:46f9621b@linux...<BR>> Most absolutely =
hardware. =20
3 Mecs down for the count.<BR>> No word on the 10 modules =
that were=20
onboard during<BR>> the mishap.<BR>><BR>> Anyone =
have a=20
spare mec they can part with?<BR>> =20
Assamundo<BR>><BR>><BR>> "Tom Bruhl" <<A =
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
=3D<BR>>news:46f4fa9a@linux...<BR>> I'll =
double check=20
Aaron.<BR>><BR>> Continuity is my middle=20
name.<BR>> "Aaron Allen" <<A=20
=
href=3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>> =
wrote in=20
message =
=3D<BR>>news:46f4e6c0@linux...<BR> > =2 0
Dude, if you have 3 toasted MEC's I think it VERY likely you had=20
a<BR>=3D<BR>>bad cable that put the hurt on them all as you swapped =
around=20
parts.=3D20<BR> > &a mp;nbsp; "Tom =
Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
=
=3D<BR>>news:46f472e2@linux...<BR> > &a mp;n=
bsp; =20
Intersted people,<BR> > &a mp;nbsp; I =
know 3=20
fried mecs is unlikely. It's not confirmed until=20
=
=3D<BR>>Tuesday=3D20<BR> > &a mp;nbsp; =
when=20
I'll check the two that might 'still work'. The hardware=20
=3D<BR>>solution<BR> > &a mp;nbsp; =
is seeming=20
to be the most logical at this point. Here's=20
why:<BR>><BR> > &a mp;nbsp; I was =
working=20
perfectly with 2 mecs loaded to the gills and a=20
=3D<BR>>442.<BR> > &a mp;nbsp; I =
wanted one=20
more mec and bought one from Deej. =20
Mistakenly,<BR> > &a mp;nbsp; I =
installed it=20
without hiding my default project. Paris=20
freaked<BR> > &a mp;nbsp; and I went =
through=20
days of turmoil looking to get back to=20
where<BR> > &a mp;nbsp; I was. =
Paris=20
refused to boot with mecs and no 442 at that=20
time.<BR>><BR> > &a mp;nbsp; Next I =
built=20
another comp to test eds and cables and the 442.=20
=3D20<BR> > &a mp;nbsp; Everything =
went=20
fine. No probs. This seemed=20
promising.<BR>><BR> > &a mp;nbsp; =
Next I=20
tried again in the studio with both computers and never =3D<BR>>got =
a=3D20<BR> > &a mp;nbsp; good Paris =
boot. =20
Every time it wouldn't boot there was a Mec=20
=3D<BR>>attached.<BR> > &a mp;nbsp; =
Even the=20
442 boots were flakey (no patchbay connections). I =
=3D<BR>>didn't=20
learn=3D20<BR> > &a mp;nbsp; anything =
from this=20
effort.<BR>><BR> > &a mp;nbsp; 2 =
days ago I=20
went to a techs place with the Paris comp, Deej's=20
=3D<BR>>mec<BR> > &a mp;nbsp; and =
the=20
442. We used the mec throughout all testing until the=20
=3D<BR>>end.<BR> > &a mp;nbsp; =
Fresh C drive,=20
fresh Paris install.<BR> > &a mp;nbsp; =
As soon=20
as the 442 was introduced Paris booted. Likely the=20
Deej<BR> > &a mp;nbsp; mec is faulty =
but not=20
necessarily.<BR>><BR> > &a mp;nbsp; =
Today I=20
went back to my original C drive (no default proj) and=20
=3D<BR>>Paris<BR> > &a mp;nbsp; =
would not=20
boot with my other Mec that is loaded to the gills.=20
=
I<BR>=3D<BR>>deleted<BR> > &a mp;nbsp; =
the=20
Scherzo drivers, reloaded the new ones I just got, =
=3D<BR>>uninstalled=20
the<BR> > &a mp;nbsp; subsystem and =
reloaded=20
it. Once I changed to the 442 the system<BR>=3D<BR>>was=20
fine.<BR>><BR> > &a mp;nbsp; Let me =
rephrase "Paris would not boot" . . . Actually it=20
would<BR>=3D<BR>>usually=20
start<BR> > &a mp;nbsp; up but no =
audio was=20
available in the patchbay except with the=20
=
=3D<BR>>442.<BR>><BR> > &a mp;nbsp; =
My=20
take is that the introduction of DJ's mec (whether it =
worked<BR>=3D<BR>>or=20
didn't,<BR> > &a mp;nbsp; let's assume =
that it=20
worked) was screwy probably by my own =3D<BR>>doing. =20
I<BR> > &a mp;nbsp; removed it and =
later=20
shorted a SCSI 2 cable at the Master Mec =3D<BR>>sometime during=20
that<BR> > &a mp;nbsp; next =
week. There=20
was smoke in the power supply area so I never<BR>=3D<BR>>tried=20
that<BR> > &a mp;nbsp; Mec =
again. My=20
other mec was attached at that time. I now =
think<BR>=3D<BR>>it fried=20
something<BR> > &a mp;nbsp; in their=20
too.<BR>><BR> > &a mp;nbsp; I am =
trying DJs=20
and my hopefully unfried mec at another studio =3D<BR>>on Tuesday =
to=20
confirm<BR> > &a mp;nbsp; that neither =
works. If I'm wrong then we're back to=20
software.<BR>><BR> > &a mp;nbsp; It =
ain't=20
over till it's over.<BR> > &a mp;nbsp; =
=
Tom<BR>><BR>><BR>><BR> > &a mp;nbsp;&n=
bsp; =20
=3D20<BR> > &a mp;nbsp; =
"Neil"=20
<<A href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> wrote in =
message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...<BR>><BR>&g=
t; &nbs p; =20
In all seriousness - THREE bad MEC's??? What's the=20
real<BR> > &a mp;nbsp; =
likelihood=20
of that? Unless all 3 PSU's got hit hard with=20
a<BR> > &a mp;nbsp; =
voltage spike=20
or something weird like that, is it=20
really<BR> > &a mp;nbsp; =
possible=20
that ALL of his MECs went=20
=
bad?<BR>><BR> > &a mp;nbsp;  =
;=20
=
Neil<BR>><BR>><BR>><BR> > &a mp;nbsp;&=
nbsp; =20
"DJ" <animix _ at _ animas _ dot _ net>=20
wrote:<BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =20
>Tom,<BR> > &a mp;nbsp; =
><BR> > &a mp;nbsp; =
>Do you=20
think the one I sent was bad ? It was working fine =3D<BR>>when I=20
pulled<BR> > &a mp;nbsp; =20
=3D3D<BR> > &a mp;nbsp; =
>it from=20
the =
rack.=3D3D20<BR> > &a mp;nbsp;  =
;=20
><BR> > &a mp;nbsp; =
>I've=20
noticed a few posts recently regarding errors. Maybe =
no<BR>=3D<BR>>more than=20
=3D3D<BR> > &a mp;nbsp; =
>usual,=20
but it seemed like an unusually high number to me =
over<BR>=3D<BR>>the last=20
=3D3D<BR> > &a mp;nbsp; =
>few=20
weeks. Errors I'm not familiar with. It will have been =
10<BR>=3D<BR>>years in=20
=3D3D<BR> > &a mp;nbsp; =
>November=20
since Paris shipped. I wonder if the lifespan of =3D<BR>>this=20
hardware<BR> > &a mp;nbsp; =
=3D3D<BR> > &a mp;nbsp; =
>is=20
starting to fade. TG for TheSoniq, I=20
guess.<BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =20
>Deej<BR> > &a mp;nbsp; =
><BR> > &a mp;nbsp; =
> =20
"Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
=3D3D<BR> > &a mp;nbsp; =20
=
>news:46f44c75$1@linux...<BR> > &a mp;nbsp;&=
nbsp; =20
> 3 bad=20
mecs.<BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =
> =20
Hmmm?<BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =
> =20
I'll know for a fact next Tuesday when=20
there's<BR> > &a mp;nbsp; =20
> time to test a couple on another=20
system.<BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =
> =20
I choose Polesoft Lockspam to fight spam, and=20
you?<BR> > &a mp;nbsp; =
> =20
<A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
=3D20<BR> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =20
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0=20
=
=3D<BR>>Transitional//EN"><BR> > &a mp;nb=
sp; =20
=
><HTML><HEAD><BR> > &a mp;nbsp;&=
nbsp; =20
><META http-equiv=3D3D3DContent-Type content=3D3D3D"text/html;=20
=3D3D<BR> > &a mp;nbsp; =20
=
>charset=3D3D3Diso-8859-1"><BR> > &a mp;n=
bsp; =20
><META content=3D3D3D"MSHTML 6.00.6000.16525"=20
=
=3D<BR>>name=3D3D3DGENERATOR><BR>> =
=20
=
><STYLE></STYLE><BR> > &a mp;nbs=
p; =20
=
></HEAD><BR> > &a mp;nbsp; =
=20
><BODY=20
=
bgColor=3D3D3D#ffffff><BR> > &a mp;nbsp;&nbs=
p; =20
><DIV><FONT face=3D3D3DArial=20
=
size=3D3D3D2>Tom,</FONT></DIV&am p;gt; <BR>> &n=
bsp; =20
><DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> =
=
</DIV><BR> > &a mp;nbsp;  =
;=20
><DIV><FONT face=3D3D3DArial size=3D3D3D2>Do you think =
the one I=20
=3D<BR>>sent was=20
=3D3D<BR> > &a mp;nbsp; =
>bad=20
?=3D3D20<BR> > &a mp;nbsp; =
></FONT><FONT face=3D3D3DArial size=3D3D3D2>It was =
working fine=20
=3D<BR>>when I pulled=20
it<BR> > &a mp;nbsp; =20
=3D3D<BR> > &a mp;nbsp; =
>from=20
=
the=3D3D20<BR> > &a mp;nbsp; =
>rack.=20
=
</FONT></DIV><BR> > &a mp;nbsp;&nbs=
p; =20
><DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> =
=
</DIV><BR> > &a mp;nbsp;  =
;=20
><DIV><FONT face=3D3D3DArial size=3D3D3D2>I've noticed =
a few=20
posts<BR>=3D<BR>>recently=20
=3D3D<BR> > &a mp;nbsp; =20
>regarding=20
=
errors.=3D3D20<BR> > &a mp;nbsp; &nb=
sp;=20
>Maybe no more than usual, but it seemed like an unusually =
=3D<BR>>high=20
number =
to<BR> > &a mp;nbsp; =20
=3D3D<BR> > &a mp;nbsp; =
>me=20
=
over=3D3D20<BR> > &a mp;nbsp; =
=20
>the last few weeks. Errors I'm not familiar with. It will =
=3D<BR>>have=20
been =
=3D3D<BR> > &a mp;nbsp; =20
=
>10=3D3D20<BR> > &a mp;nbsp; &nbs=
p;=20
>years in November since Paris shipped. I wonder if the =
=3D<BR>>lifespan=20
of this<BR> > &a mp;nbsp; =20
=3D3D<BR> > &a mp;nbsp; =20
=
>hardware=3D3D20<BR> > &a mp;nbsp; &nbs=
p; =20
>is starting to fade. TG for TheSoniq, I=20
=
guess.</FONT></DIV><BR> > &a mp;nbs=
p; =20
><DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> =
=
</DIV><BR> > &a mp;nbsp;  =
;=20
><DIV><FONT face=3D3D3DArial=20
=
size=3D3D3D2>Deej</FONT></DIV&am p;gt; <BR>> &n=
bsp; =20
><DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT> =
=
</DIV><BR> > &a mp;nbsp;  =
;=20
><BLOCKQUOTE=20
=
dir=3D3D3Dltr=3D3D20<BR> > &a mp;nbsp; &nb=
sp; =20
>style=3D3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
=3D<BR>>MARGIN-LEFT:=20
5px; =
=3D3D<BR> > &a mp;nbsp; =20
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT:=20
0px"><BR> > &a mp;nbsp; =
> <DIV>"Tom Bruhl"=20
=
<<A=3D3D20<BR> > &a mp;nbsp; &=
nbsp;=20
> =3D<BR>>href=3D3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =
=3D3D<BR> > &a mp;nbsp; =
>in=20
=
message=3D3D20<BR> > &a mp;nbsp; &nb=
sp;=20
> <A =3D<BR>>href=3D3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> &a mp;nbsp; =20
> <DIV><FONT face=3D3D3DArial size=3D3D3D2>3 bad=20
=
=3D<BR>>mecs.</FONT></DIV> <BR>> =
=20
> <DIV><FONT face=3D3D3DArial =
size=3D3D3D2></FONT>=20
=
</DIV><BR> > &a mp;nbsp;  =
;=20
> <DIV><FONT face=3D3D3DArial=20
=
size=3D3D3D2>Hmmm?</FONT></DIV&a mp;gt; <BR>> &=
nbsp; =20
> <DIV><FONT face=3D3D3DArial =
size=3D3D3D2></FONT>=20
=
</DIV><BR> > &a mp;nbsp;  =
;=20
> <DIV><FONT face=3D3D3DArial size=3D3D3D2>I'll =
know for a=20
fact =3D<BR>>next Tuesday=20
=3D3D<BR> > &a mp;nbsp; =20
=
>when=3D3D20<BR> > &a mp;nbsp; &n=
bsp;=20
> =20
=
there's</FONT></DIV><BR> > &a mp;nb=
sp; =20
> <DIV><FONT face=3D3D3DArial size=3D3D3D2>time =
to test a=20
couple<BR>=3D<BR>>on=20
=
another=3D3D20<BR> > &a mp;nbsp; &nb=
sp;=20
> =20
=
system.</FONT></DIV><BR> > &a mp;nb=
sp; =20
> <DIV><FONT face=3D3D3DArial =
size=3D3D3D2></FONT>=20
=
</DIV><BR> > &a mp;nbsp;  =
;=20
> <DIV><FONT face=3D3D3DArial =
size=3D3D3D2></FONT>=20
=
</DIV><BR> > &a mp;nbsp;  =
;=20
> <DIV><FONT size=3D3D3D2><BR><BR>I =
choose=20
Polesoft Lockspam to<BR>=3D<BR>>fight=20
spam,<BR> > &a mp;nbsp; =20
=3D3D<BR> > &a mp;nbsp; =20
=
>and=3D3D20<BR> > &a mp;nbsp; &nb=
sp;=20
> =20
=
you?<BR><A=3D3D20<BR> > &a mp;nbsp;&nb=
sp; =20
> =
=3D3D<BR> > &a mp;nbsp; =20
=3D<BR>>>href=3D3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/re'>h=
ttp://www.polesoft.com/refer.html">http://www.polesoft.com/re</A>=3D<B=
R>>fer=3D3D<BR> > &a mp;nbsp; &nb=
sp;=20
>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
> > &a mp;nbsp; =20
><BR> > &a mp;nbsp; =20
><BR>><BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML =
4.0=20
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>I'll=20
also toss out an edumacated guess<BR>=3D<BR>>that =
only=3D20<BR>>the=20
interface portion got fried and all your MEC cards are likely to=20
be<BR>=3D<BR>>ok...=3D20<BR>>holla back on that man.=20
</FONT></DIV><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2>Sorry, no spare MEC's around here, in =3D<BR>>fact=20
I'm=3D20<BR>>going to be growing my rig again shortly with a few =
more EDS=20
=
cards=3D20<BR>>:)</FONT></DIV> <BR>><DIV><FONT =
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>Say Tom, have you called The Soniq =
=3D<BR>>about=20
repairing=3D20<BR>>yours... he offers warranty on his work yano=20
:)</FONT></DIV><BR>><DIV>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2>AA</FONT></DIV> ; <BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: =
5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl" =
<<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A href=3D3D"<A=20
=
href=3D'news:46f9621b@linux">news:46f9621b@linux</A>...</DIV'>news:46f962=
1b@linux">news:46f9621b@linux</A>...</DIV</A>><BR>>&nbs=
p;=20
<DIV><FONT face=3D3DArial size=3D3D2>Most absolutely =
hardware. 3=20
=3D<BR>>Mecs down for=3D20<BR>> the=20
count.</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>No word on the 10 modules that were=20
=3D<BR>>onboard=3D20<BR>> =20
during</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>the mishap.</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial =
size=3D3D2>Anyone=20
have a spare mec they can part<BR>=3D<BR>><BR>> =20
with?</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>Assamundo</FONT></DIV > <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>> <BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>> style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT: 5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
=3D<BR>>wrote in=3D20<BR>> message <A=20
=3D<BR>>href=3D3D"<A=20
=
href=3D'news:46f4fa9a@linux">news:46f4fa9a@linux</A>...</DIV'>news:46f4fa=
9a@linux">news:46f4fa9a@linux</A>...</DIV</A>><BR>>&nbs=
p; =20
<DIV><FONT face=3D3DArial size=3D3D2>I'll double check=20
=3D<BR>>Aaron.</FONT></DIV> <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>Continuity is my middle=20
=3D<BR>>name.</FONT></DIV> <BR>> =20
<BLOCKQUOTE dir=3D3Dltr=3D20<BR>> =
style=3D3D"PADDING-RIGHT:=20
0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: =
#000000 2px=20
solid; MARGIN-RIGHT: 0px"><BR> > =2 0
<DIV>"Aaron Allen" =
<<A=3D20<BR> > =2 0
=3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>>=3D20=
'>mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>>=
;=3D20</A><BR> > =2 0
wrote in message <A=3D20<BR>> =
href=3D3D"<A=20
=
href=3D'news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV'>news:46f4e6=
c0@linux">news:46f4e6c0@linux</A>...</DIV</A>><BR>>&nbs=
p; =20
<DIV><FONT face=3D3DArial size=3D3D2>Dude, if you have 3 =
toasted=20
MEC's<BR>=3D<BR>>I think =
it=3D20<BR>> VERY=20
likely you had a bad cable that put the hurt on them =3D<BR>>all as =
you=3D20<BR>> swapped around parts.=20
</FONT></DIV><BR>> =
<BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>> =
style=3D3D"PADDING-RIGHT:=20
0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px;<BR>=3D<BR>>BORDER-LEFT: =
#000000 2px=20
solid; MARGIN-RIGHT:=20
0px"><BR> > &a mp;nbsp; =
<DIV>"Tom=20
Bruhl" =
<<A=3D20<BR> > &a mp;nbsp; =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
=3D<BR>>wrote =
in=3D20<BR> > &a mp;nbsp; message=20
<A =3D<BR>>href=3D3D"<A=20
=
href=3D'news:46f472e2@linux">news:46f472e2@linux</A>...</DIV'>news:46f472=
e2@linux">news:46f472e2@linux</A>...</DIV</A>><BR>>&nbs=
p; &nbs p;=20
<DIV><FONT face=3D3DArial size=3D3D2>Intersted=20
=
people,</FONT></DIV><BR> > &a mp;nb=
sp; =20
<DIV><FONT face=3D3DArial size=3D3D2>I know 3 fried mecs =
is=20
=3D<BR>>unlikely. =
It's=3D20<BR> > &a mp;nbsp; =20
not confirmed until Tuesday=20
=
</FONT></DIV><BR> > &a mp;nbsp;&nbs=
p;=20
<DIV><FONT face=3D3DArial size=3D3D2>when I'll check the =
two=20
=
=3D<BR>></FONT><FONT=3D20<BR>> &nbs=
p; =20
face=3D3DArial size=3D3D2>that might 'still work'. The=20
=
=3D<BR>>hardware=3D20<BR> > &a mp;nbsp; =
;=20
=
solution</FONT></DIV><BR> > &a mp;n=
bsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>is seeming to be the =
most=20
=3D<BR>>logical at =
this=3D20<BR> > &a mp;nbsp; =20
point. Here's=20
=
why:</FONT></DIV><BR> > &a mp;nbsp;=
=20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>I was working =
perfectly with=20
2<BR>=3D<BR>>mecs =
loaded=3D20<BR> > &a mp;nbsp; =20
to the gills and a=20
=
442.</FONT></DIV><BR> > &a mp;nbsp;=
=20
<DIV><FONT face=3D3DArial size=3D3D2>I wanted one more mec =
and=20
=3D<BR>>bought one =
from=3D20<BR> > &a mp;nbsp; =20
Deej.=20
=
Mistakenly,</FONT></DIV><BR>>  =
; =20
<DIV><FONT face=3D3DArial size=3D3D2>I installed it =
without hiding=20
=3D<BR>>my =
default=3D20<BR> > &a mp;nbsp; =20
project. Paris=20
=
freaked</FONT></DIV><BR> > &a mp;nb=
sp; =20
<DIV><FONT face=3D3DArial size=3D3D2>and I went through =
days of=20
=3D<BR>>turmoil =
looking=3D20<BR> > &a mp;nbsp; =20
to get back to=20
=
where</FONT></DIV><BR> > &a mp;nbsp=
; =20
<DIV><FONT face=3D3DArial size=3D3D2>I was. Paris refused =
to=20
=3D<BR>>boot =
with=3D20<BR> > &a mp;nbsp; mecs=20
and no 442 at that=20
=
time.</FONT></DIV><BR> > &a mp;nbsp=
; =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>Next I built another =
comp to=20
=3D<BR>>test eds =
and=3D20<BR> > &a mp;nbsp; =20
cables and the 442.=20
=
</FONT></DIV><BR> > &a mp;nbsp;&nbs=
p;=20
<DIV><FONT face=3D3DArial size=3D3D2>Everything went=20
</FONT><FONT=20
=
=3D<BR>>face=3D3DArial=3D20<BR> > &a mp;nbsp=
; =20
size=3D3D2>fine. No probs. This seemed=20
=
=3D<BR>>promising.</FONT></DIV> <BR>> &=
nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>Next I tried again in =
the=20
=3D<BR>>studio with =
both=3D20<BR> > &a mp;nbsp; =20
computers and never got a=20
=
</FONT></DIV><BR> > &a mp;nbsp;&nbs=
p;=20
<DIV><FONT face=3D3DArial size=3D3D2>good Paris boot. =
Every=20
=3D<BR>>time =
it=3D20<BR> > &a mp;nbsp; wouldn't=20
boot there was a Mec=20
=
attached.</FONT></DIV><BR> > &a mp;=
nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>Even the 442 boots =
were=20
flakey<BR>=3D<BR>>(no=20
patchbay=3D20<BR> > &a mp;nbsp; =
connections). I=20
didn't learn=20
=
</FONT></DIV><BR> > &a mp;nbsp;&nbs=
p;=20
<DIV><FONT face=3D3DArial size=3D3D2>anything from this=20
=
=3D<BR>>effort.</FONT></DIV> <BR>> &nbs=
p; =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>2 days ago I went to =
a techs=20
=3D<BR>>place with =
the=3D20<BR> > &a mp;nbsp; =20
Paris comp, Deej's=20
=
mec</FONT></DIV><BR> > &a mp;nbsp;&=
nbsp;=20
<DIV><FONT face=3D3DArial size=3D3D2>and the 442. We used =
the=20
=3D<BR>>mec=3D20<BR> > &a mp;nbsp; =
throughout=20
all testing until the=20
=
end.</FONT></DIV><BR> > &a mp;nbsp;=
=20
<DIV><FONT face=3D3DArial size=3D3D2>Fresh C drive, fresh=20
Paris=3D20<BR> > &a mp;nbsp; =20
=
install.</FONT></DIV><BR> > &a mp;n=
bsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>As soon as the 442 =
was=20
=3D<BR>>introduced =
Paris=3D20<BR> > &a mp;nbsp; =20
booted. Likely the=20
=
Deej</FONT></DIV><BR> > &a mp;nbsp;=
=20
<DIV><FONT face=3D3DArial size=3D3D2>mec is faulty but=20
not=3D20<BR> > &a mp;nbsp; =20
=
necessarily.</FONT></DIV><BR>> &nbs=
p; =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>Today I went back to =
my=20
=3D<BR>>original C =
drive=3D20<BR> > &a mp;nbsp; =20
(no default proj) and=20
=
Paris</FONT></DIV><BR> > &a mp;nbsp=
; =20
<DIV><FONT face=3D3DArial size=3D3D2>would not boot with =
my=20
=3D<BR>>other Mec =
that=3D20<BR> > &a mp;nbsp; =20
is loaded to the gills. I=20
=
deleted</FONT></DIV><BR> > &a mp;nb=
sp; =20
<DIV><FONT face=3D3DArial size=3D3D2>the Scherzo drivers, =
reloaded=20
=3D<BR>>the new =
ones=3D20<BR> > &a mp;nbsp; I=20
just got, uninstalled=20
=
the</FONT></DIV><BR> > &a mp;nbsp;&=
nbsp;=20
<DIV><FONT face=3D3DArial size=3D3D2>subsystem and =
reloaded=20
=3D<BR>>it. Once =
I=3D20<BR> > &a mp;nbsp; =20
changed to the 442 the system was=20
=
fine.</FONT></DIV><BR> > &a mp;nbsp=
; =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>Let me rephrase =
"Paris would=20
=3D<BR>>not boot" . =
..=3D20<BR> > &a mp;nbsp; .=20
Actually it would usually=20
=
start</FONT></DIV><BR> > &a mp;nbsp=
; =20
<DIV><FONT face=3D3DArial size=3D3D2>up but no audio was =
available=20
=3D<BR>>in =
the=3D20<BR> > &a mp;nbsp; patchbay=20
except with the=20
=
442.</FONT></DIV><BR> > &a mp;nbsp;=
=20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>My take is that the=20
=3D<BR>>introduction of=20
DJ's=3D20<BR> > &a mp;nbsp; mec =
(whether it=20
worked or=20
=
didn't,</FONT></DIV><BR> > &a mp;nb=
sp; =20
<DIV><FONT face=3D3DArial size=3D3D2>let's assume that it =
worked)=20
=
=3D<BR>></FONT><FONT=3D20<BR>> &nbs=
p; =20
face=3D3DArial size=3D3D2>was screwy probably by my own doing.=20
=3D<BR>><BR> > &a mp;nbsp; =20
=
I</FONT></DIV><BR> > &a mp;nbsp;&nb=
sp;=20
<DIV><FONT face=3D3DArial size=3D3D2>removed it and later =
shorted=20
a<BR>=3D<BR>>SCSI 2=20
cable=3D20<BR> > &a mp;nbsp; at the =
Master Mec=20
sometime during=20
=
that</FONT></DIV><BR> > &a mp;nbsp;=
=20
<DIV><FONT face=3D3DArial size=3D3D2>next week. There was=20
=3D<BR>>smoke in =
the=3D20<BR> > &a mp;nbsp; =20
power supply area so I never tried=20
=
that</FONT></DIV><BR> > &a mp;nbsp;=
=20
<DIV><FONT face=3D3DArial size=3D3D2>Mec again. My other =
=3D<BR>>mec=20
was=3D20<BR> > &a mp;nbsp; attached at =
that=20
time. I now think it fried=20
=
=3D<BR>>something</FONT></DIV> <BR>> &n=
bsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>in their=20
=
too.</FONT></DIV><BR> > &a mp;nbsp;=
=20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>I am trying DJs and =
my=20
=3D<BR>>hopefully=20
unfried=3D20<BR> > &a mp;nbsp; mec at =
another=20
studio on Tuesday to=20
=
confirm</FONT></DIV><BR> > &a mp;nb=
sp; =20
<DIV><FONT face=3D3DArial size=3D3D2>that neither works. =
If=20
=3D<BR>>I'm wrong =
then=3D20<BR> > &a mp;nbsp; =20
we're back to=20
=
software.</FONT></DIV><BR> > &a mp;=
nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2>It ain't over till =
it's=20
=
=3D<BR>>over.</FONT></DIV> <BR>> =
=20
<DIV><FONT face=3D3DArial=20
=
size=3D3D2>Tom</FONT></DIV&g t; <BR>>  =
; =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3DArial size=3D3D2> </FONT>=20
</DIV><BR> > &a mp;nbsp; =20
<BLOCKQUOTE=3D20<BR> > &a mp;nbsp; =20
style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
=3D<BR>>5px;=20
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT:=20
0px"><BR> > &a mp;nbsp; =
<DIV>"Neil" <<A =3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:IOU@OIU.com">IOU@OIU.com</A'>mailto:IOU@OIU.com">IOU@OI=
U.com</A</A>>>=20
=
wrote=3D20<BR> > &a mp;nbsp; =
in=20
message =
<A=3D20<BR> > &a mp;nbsp; =
=3D<BR>>href=3D3D"<A=20
=
href=3D'news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=3D=
20'>news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV&=
gt;<BR>In=3D20</A><BR> > &a mp;nbsp; =
; =20
all seriousness - THREE bad MEC's??? What's the=20
=3D<BR>>real<BR>likelihood=20
of=3D20<BR> > &a mp;nbsp; =
that?=20
Unless all 3 PSU's got hit hard with a<BR>voltage=20
=
spike<BR>=3D<BR>>or=3D20<BR> > &a mp;nbsp;&n=
bsp; =20
something weird like that, is it really<BR>possible that ALL =
=3D<BR>>of=20
his=3D20<BR> > &a mp;nbsp; =
MECs went=20
=
bad?<BR><BR>Neil<BR&g t;<BR><BR><BR> "DJ" =
<animix _ at=20
=
=3D<BR>>_=3D20<BR> > &a mp;nbsp; =
=20
animas _ dot _=20
=
net>=3D20<BR> > &a mp;nbsp;  =
;=20
=
wrote:<BR>><BR>>&a mp;lt;BR>>Tom,<BR>>&l t;BR&=
gt;>Do=20
you think =3D<BR>>the=20
one=3D20<BR> > &a mp;nbsp; =
I sent=20
was bad ? It was working fine when I=20
=3D<BR> >pulled<BR>=3D3D<BR>& gt;it=20
=
from=3D20<BR> > &a mp;nbsp; =
the=20
rack.=3D3D20<BR>><BR>& ;gt;I've noticed a few posts=20
=
=3D<BR>>recently=3D20<BR> > &a mp;nbsp; =
; =20
regarding errors. Maybe no more than =3D3D<BR>>usual, but it=20
=
=3D<BR>>seemed=3D20<BR> > &a mp;nbsp; &=
nbsp; =20
like an unusually high number to me over the last=20
=3D<BR>>=3D3D<BR>>few=20
=
weeks.=3D20<BR> > &a mp;nbsp; =
Errors=20
I'm not familiar with. It will have been 10 years=20
in=3D20<BR> > &a mp;nbsp; =20
=3D3D<BR>>November since Paris shipped. I wonder if the=20
=3D<BR>>lifespan=20
of=3D20<BR> > &a mp;nbsp; =
this=20
hardware<BR>=3D3D<BR>>is starting to fade. TG for=20
=3D<BR>>TheSoniq,=20
I=3D20<BR> > &a mp;nbsp; =20
guess.<BR>><BR>>De ej<BR>><BR>> =
"Tom Bruhl"=20
=
=3D<BR>><<A=3D20<BR> > &a mp;nbsp;&nbs=
p; =20
=3D<BR>>href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote in=20
=
=3D<BR>><BR> > &a mp;nbsp; =
=20
message =3D3D<BR>>news:46f44c75$1@linux...<BR>> 3=20
=
=3D<BR>>bad=3D20<BR> > &a mp;nbsp; &nbs=
p; =20
mecs.<BR>><BR>> Hmmm?<BR>><BR>> =
I'll=20
=3D<BR>>know=20
for=3D20<BR> > &a mp;nbsp; =
a fact=20
next Tuesday when there's<BR>> time to test a=20
=
=3D<BR>>couple=3D20<BR> > &a mp;nbsp; &=
nbsp; =20
on another=20
=
=3D<BR> >system.<BR>><BR>& amp;gt;<BR>><BR>>=
;<BR>>=20
I=3D20<BR> > &a mp;nbsp; =
choose=20
Polesoft Lockspam to fight spam, and you?<BR>>=20
=
=3D<BR>><A=3D20<BR> > &a mp;nbsp; &n=
bsp; =20
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=3D20<BR> > &a mp;nbsp; =20
<BR>><BR>>< !DOCTYPE HTML PUBLIC "-//W3C//DTD HTML =
4.0=20
=
=3D<BR>><BR> > &a mp;nbsp; =
=20
=
=3D<BR>>Transitional//EN" ><BR>><HTML>&l t;HEAD><=
;BR>><META=3D20<BR> > &a mp;nbsp; =
; =20
http-equiv=3D3D3DContent-Type=20
=
content=3D3D3D"text/html;=3D20<BR> > &a mp;nbsp=
; =20
=3D3D<BR>>charset=3D3D3Diso-8859-1"><BR>><META =
=
=3D<BR>>content=3D3D3D"MSHTML=3D20<BR>> &nbs=
p; =20
=
6.00.6000.16525"=3D20<BR> > &a mp;nbsp; &n=
bsp; =20
=
=3D<BR> >name=3D3D3DGENERATOR><BR>&g t;<STYLE></STYLE&=
gt;<BR>></HEA=3D<BR> >D><BR>><BODY=3D20 <BR>&=
gt; &nb sp; =20
bgColor=3D3D3D#ffffff><BR>>& lt;DIV><FONT=20
=
=3D<BR>>face=3D3D3DArial=3D20<BR> > &a mp;nb=
sp; =20
=
=3D<BR> >size=3D3D3D2>Tom,</FONT>< ;/DIV><BR>><=
;DIV><FONT=3D20<BR> > &a mp;nbsp; &n=
bsp; =20
face=3D3D3DArial=20
=
size=3D3D3D2></FONT>=3D20<BR> > &a mp;=
nbsp; =20
</DIV><BR>><DIV&am p;gt;<FONT face=3D3D3DArial=20
=
=3D<BR>>size=3D3D3D2>Do=3D20<BR> > &a mp;=
nbsp; =20
you think the one I sent was=20
=
=3D3D<BR>>bad=3D20<BR> > &a mp;nbsp;&n=
bsp; =20
?=3D3D20<BR>></FONT>& lt;FONT face=3D3D3DArial=20
=3D<BR>>size=3D3D3D2>It=20
was=3D20<BR> > &a mp;nbsp; =
working=20
fine when I pulled it<BR>=3D3D<BR>>from=20
=
=3D<BR>>the=3D3D20<BR>>rack.=3D20 <BR>> &n=
bsp; =20
</FONT></DIV><BR>& amp;gt;<DIV><FONT=20
=
=3D<BR>>face=3D3D3DArial=3D20<BR> > &a mp;nb=
sp; =20
size=3D3D3D2></FONT>=20
=
=3D<BR> ></DIV><BR>>&l t;DIV><FONT=3D20 <BR>>&nbs=
p; &nbs p; =20
face=3D3D3DArial size=3D3D3D2>I've noticed a few posts recently=20
=
=3D<BR>><BR> > &a mp;nbsp; =
=20
=3D3D<BR>>regarding errors.=3D3D20<BR>>Maybe no more =
than=20
=3D<BR>>usual, but=20
it=3D20<BR> > &a mp;nbsp; =
seemed=20
like an unusually high number=20
=
to<BR>=3D3D<BR>>me=3D20<BR >> &nb=
sp; =20
over=3D3D20<BR>>the last few weeks. Errors I'm not familiar=20
=3D<BR>>with.=20
It=3D20<BR> > &a mp;nbsp; =
will have=20
been =3D3D<BR>>10=3D3D20<BR>&a mp;gt;years in November =
=3D<BR>>since=20
=
Paris=3D20<BR> > &a mp;nbsp; =
shipped. I wonder if the lifespan=20
of=3D20<BR> > &a mp;nbsp; =20
this<BR>=3D3D<BR>>hardwar e=3D3D20<BR>>is =
starting to fade.=20
=3D<BR>>TG=20
for=3D20<BR> > &a mp;nbsp; =
TheSoniq,=20
I=20
=
=3D<BR> >guess.</FONT></DIV>& lt;BR>><DIV><FO=
NT=3D20<BR> > &a mp;nbsp; =20
face=3D3D3DArial=20
=
size=3D3D3D2></FONT>=3D20<BR> > &a mp;=
nbsp; =20
</DIV><BR>><DIV&am p;gt;<FONT=20
=
face=3D3D3DArial=3D20<BR> > &a mp;nbsp; &n=
bsp; =20
=
=3D<BR> >size=3D3D3D2>Deej</FONT>< ;/DIV><BR>><=
;DIV><FONT=3D20<BR> > &a mp;nbsp; &n=
bsp; =20
face=3D3D3DArial=20
=
size=3D3D3D2></FONT>=3D20<BR> > &a mp;=
nbsp; =20
=
</DIV><BR>><BLOCKQ UOTE=3D20 <BR>> &n=
bsp; =20
dir=3D3D3Dltr=3D3D20<BR>>style=3D3D3D"PADDING-RIGHT: 0px;=20
=3D<BR>>PADDING-LEFT:=20
=
5px;=3D20<BR> > &a mp;nbsp; =20
MARGIN-LEFT: 5px; =3D3D<BR>>BORDER-LEFT: #000000 2px=20
=
solid;=3D20<BR> > &a mp;nbsp; =
=20
MARGIN-RIGHT: 0px"><BR>> <DIV>"Tom=20
=
Bruhl"=3D20<BR> > &a mp;nbsp; =
=20
<<A=3D3D20<BR>>=20
=
href=3D3D3D"<A=3D20<BR> > &a mp;nbsp; &=
nbsp; =20
=
=3D<BR>>href=3D3D'mailto:arpegio@comcast.net">arpegio@comcast.net&l=
t;/A'>mailto:arpegi=3D<BR>>o@comcast.net">arpegio@comcast.net<=
;/A</A>>>=3D20<BR> > &a mp;nbsp;&nb=
sp; =20
wrote =3D3D<BR>>in message=3D3D20<BR>> <A=20
=
=3D<BR>>href=3D3D3D"<A=3D20<BR> > &a mp;n=
bsp; =20
=
=3D<BR>>href=3D3D'news:46f44c75$1@linux">news:46f44c75$1@linux</=
A>...</DIV'>news:46=3D<BR>>f44c75$1@linux">news:46f44c75$1=
@linux</A>...</DIV</A>&am p;gt;<BR>=3D <BR>>>=20
=3D20<BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3D3DArial size=3D3D3D2>3=20
bad=3D20<BR> > &a mp;nbsp; =
mecs.</FONT></DIV><BR& ;gt;>=20
=
=3D<BR>><DIV><FONT=3D20<BR>> =
=20
face=3D3D3DArial size=3D3D3D2></FONT> =
=3D<BR>></DIV><BR>>=20
=3D20<BR> > &a mp;nbsp; =20
<DIV><FONT=20
=
face=3D3D3DArial=3D20<BR> > &a mp;nbsp; &n=
bsp; =20
size=3D3D3D2>Hmmm?</FONT></DIV&a mp;gt;<BR>>=20
=3D20<BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT>=20
=
=3D<BR>><BR> > &a mp;nbsp; =
=20
</DIV><BR>> <DIV><FONT=20
=
face=3D3D3DArial=3D20<BR> > &a mp;nbsp; &n=
bsp; =20
size=3D3D3D2>I'll know for a fact next=20
=
Tuesday=3D20<BR> > &a mp;nbsp;  =
;=20
=3D3D<BR>>when=3D3D20<BR> >=20
=3D20<BR> > &a mp;nbsp; =20
there's</FONT></DIV><BR&a mp;gt;>=20
=
=3D<BR>><DIV><FONT=3D20<BR>> =
=20
face=3D3D3DArial size=3D3D3D2>time to test a couple=20
on=3D20<BR> > &a mp;nbsp; =20
another=3D3D20<BR>>=20
=3D20<BR> > &a mp;nbsp; =20
system.</FONT></DIV><BR&a mp;gt;>=20
=
=3D<BR>><DIV><FONT=3D20<BR>> =
=20
face=3D3D3DArial size=3D3D3D2></FONT> =
=3D<BR>></DIV><BR>>=20
=3D20<BR> > &a mp;nbsp; =20
<DIV><FONT face=3D3D3DArial size=3D3D3D2></FONT>=20
=
=3D<BR>><BR> > &a mp;nbsp; =
=20
</DIV><BR>>=20
=
<DIV><FONT=3D20<BR> > &a mp;nbsp; =
; =20
size=3D3D3D2><BR><BR>I choose Polesoft Lockspam =
=3D<BR>>to=20
=
fight=3D20<BR> > &a mp;nbsp; =
spam,<BR>=3D3D<BR>>and=3D 3D20<BR>>=20
=3D20<BR> > &a mp;nbsp; =20
you?<BR><A=3D3D20<BR>& ;gt; =
=3D3D<BR>>href=3D3D3D"<A=20
=
=3D<BR>><BR> > &a mp;nbsp; =
=20
=
=3D<BR>>href=3D3D'http://www.polesoft.com/refer.html">http://www.po=
lesoft.com/refer=3D<BR>>'>http://www.polesoft.com/refer.html">ht=
tp://www.polesoft.com/refer</A=3D<BR>>>=3D3D<BR>>.html&=
lt;/A>=3D20<BR> > &a mp;nbsp; &nb=
sp;=20
=
=3D<BR> ></FONT></DIV></BL OCKQUOTE></BODY></=
HTML><BR=3D<BR> >>><BR>><BR ></BLOCKQUOTE&=
gt;</BLOCKQUOTE></BLOCKQUOTE>&am p;lt;/BLOCKQUOTE></BL=3D <BR=
> >OCKQUOTE></BODY></HTML&a mp;gt; <BR>><BR>><BR></BLOCKQUO=
TE></BODY></HTML>
------=_NextPart_000_012F_01C7FFF1.28AFA770--
|
|
|
|
| Re: I know I found my problem [message #90627 is a reply to message #90575] |
Wed, 26 September 2007 22:34 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_005F_01C800A6.99CD7850
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
AA,
I did find one scsi cable that had a couple dead pins out of five =
cables.
It allowed the 442 to work though. ? . Maybe those pins aren't used
in the Paris pin out? I chucked it anyway. Could be the source of
all evil.
Tom
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46fa1183@linux...
Aaron,
Thanks, I won't know about the modules until some new Mecs get =
delivered here.
I think I have the four I need almost on their way from multiple =
sources.
It looks like a chip in the master section of the scsi scorched mec =
got hit bad. We're
looking for the chip now. The other mecs may have less of a problem. =
Maybe some DC=20
down the WC line? Just a guess. Everything was AC grounded and no =
polarity shift.
We learned there's all kinds of protection fuses in line on the master =
section. It seems 'they' weren't
fried but the expensive stuff right after them was. . .
Tom
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f9cf56@linux...
I'll also toss out an edumacated guess that only the interface =
portion got fried and all your MEC cards are likely to be ok... holla =
back on that man.=20
Sorry, no spare MEC's around here, in fact I'm going to be growing =
my rig again shortly with a few more EDS cards :)
Say Tom, have you called The Soniq about repairing yours... he =
offers warranty on his work yano :)
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f9621b@linux...
Most absolutely hardware. 3 Mecs down for the count.
No word on the 10 modules that were onboard during
the mishap.
Anyone have a spare mec they can part with?
Assamundo
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f4fa9a@linux...
I'll double check Aaron.
Continuity is my middle name.
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f4e6c0@linux...
Dude, if you have 3 toasted MEC's I think it VERY likely you =
had a bad cable that put the hurt on them all as you swapped around =
parts.=20
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until =
Tuesday=20
when I'll check the two that might 'still work'. The =
hardware solution
is seeming to be the most logical at this point. Here's =
why:
I was working perfectly with 2 mecs loaded to the gills and =
a 442.
I wanted one more mec and bought one from Deej. Mistakenly,
I installed it without hiding my default project. Paris =
freaked
and I went through days of turmoil looking to get back to =
where
I was. Paris refused to boot with mecs and no 442 at that =
time.
Next I built another comp to test eds and cables and the =
442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and =
never got a=20
good Paris boot. Every time it wouldn't boot there was a =
Mec attached.
Even the 442 boots were flakey (no patchbay connections). I =
didn't learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, =
Deej's mec
and the 442. We used the mec throughout all testing until =
the end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely the =
Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) =
and Paris
would not boot with my other Mec that is loaded to the =
gills. I deleted
the Scherzo drivers, reloaded the new ones I just got, =
uninstalled the
subsystem and reloaded it. Once I changed to the 442 the =
system was fine.
Let me rephrase "Paris would not boot" . . . Actually it =
would usually start
up but no audio was available in the patchbay except with =
the 442.
My take is that the introduction of DJ's mec (whether it =
worked or didn't,
let's assume that it worked) was screwy probably by my own =
doing. I
removed it and later shorted a SCSI 2 cable at the Master =
Mec sometime during that
next week. There was smoke in the power supply area so I =
never tried that
Mec again. My other mec was attached at that time. I now =
think it fried something
in their too.
I am trying DJs and my hopefully unfried mec at another =
studio on Tuesday to confirm
that neither works. If I'm wrong then we're back to =
software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message =
news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working fine =
when I pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. Maybe =
no more than =3D
>usual, but it seemed like an unusually high number to me =
over the last =3D
>few weeks. Errors I'm not familiar with. It will have =
been 10 years in =3D
>November since Paris shipped. I wonder if the lifespan of =
this hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" =
name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the one =
I sent was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working =
fine when I pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few =
posts recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an unusually =
high number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It will =
have been =3D
>10=3D20
>years in November since Paris shipped. I wonder if the =
lifespan of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I =
guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad =
mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a =
fact next Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a =
couple on another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft =
Lockspam to fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_005F_01C800A6.99CD7850
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>AA,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I did find one scsi cable that had =
a couple=20
dead pins out of five cables.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>It allowed the 442 to work though. ? =
.. Maybe=20
those pins aren't used</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in the Paris pin out? =
I=20
chucked it anyway. Could be the source of</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>all evil.</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>
<DIV><FONT face=3DArial size=3D2></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:46fa1183@linux">news:46fa1183@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Aaron,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks, I won't know about the =
modules until some=20
new Mecs get delivered here.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I think I have the four I need almost =
on their=20
way from multiple sources.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It looks like a chip in the master =
section of the=20
scsi scorched mec got hit bad. We're</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>looking for the chip now. The =
other=20
</FONT><FONT face=3DArial size=3D2>mecs may have less of a =
problem. Maybe=20
some DC </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>down the WC line? Just a =
guess. =20
Everything was AC grounded and no polarity shift.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We learned there's all kinds of =
protection fuses=20
in line on the master section. It seems 'they' =
weren't</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>fried but the expensive stuff right =
after them=20
was. . .</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>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></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:46f9cf56@linux">news:46f9cf56@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll also toss out an edumacated =
guess that=20
only the interface portion got fried and all your MEC cards are =
likely to be=20
ok... holla back on that man. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sorry, no spare MEC's around here, =
in fact I'm=20
going to be growing my rig again shortly with a few more EDS cards=20
:)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Say Tom, have you called The Soniq =
about=20
repairing yours... he offers warranty on his work yano =
:)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>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:46f9621b@linux">news:46f9621b@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Most absolutely hardware. 3 =
Mecs down=20
for the count.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>No word on the 10 modules that =
were onboard=20
during</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the mishap.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Anyone have a spare mec they can =
part=20
with?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Assamundo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></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=20
message <A =
href=3D"news:46f4fa9a@linux">news:46f4fa9a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll double check =
Aaron.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Continuity is my middle =
name.</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>>=20
wrote in message <A=20
href=3D"news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Dude, if you have 3 toasted =
MEC's I think=20
it VERY likely you had a bad cable that put the hurt on them=20
all as you swapped around parts. </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=20
in message <A=20
=
href=3D"news:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Intersted =
people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is =
unlikely. =20
It's not confirmed until Tuesday </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT=20
face=3DArial size=3D2>that might 'still work'. The =
hardware=20
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most =
logical at=20
this point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly =
with 2 mecs=20
loaded to the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and =
bought one=20
from Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without =
hiding my=20
default project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days of =
turmoil=20
looking to get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris refused =
to boot with=20
mecs and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp =
to test eds=20
and cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went =
</FONT><FONT face=3DArial=20
size=3D2>fine. No probs. This seemed=20
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the =
studio with=20
both computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. =
Every time it=20
wouldn't boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were =
flakey (no=20
patchbay connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this =
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a =
techs place with=20
the Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We used =
the mec=20
throughout all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was =
introduced Paris=20
booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not=20
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my =
original C=20
drive (no default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot with my =
other Mec=20
that is loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, =
reloaded the new=20
ones I just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded =
it. Once I=20
changed to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris =
would not boot"=20
. . . Actually it would usually start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was =
available in the=20
patchbay except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the =
introduction of=20
DJ's mec (whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it =
worked)=20
</FONT><FONT face=3DArial size=3D2>was screwy probably by my =
own=20
doing. I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later =
shorted a SCSI 2=20
cable at the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There was =
smoke in the=20
power supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My =
other mec was=20
attached at that time. I now think it fried=20
something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my =
hopefully=20
unfried mec at another studio on Tuesday to =
confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. =
If I'm wrong=20
then we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's=20
over.</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>
<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>"Neil" <<A =
href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>>=20
wrote in message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
all seriousness - THREE bad MEC's??? What's the =
real<BR>likelihood=20
of that? Unless all 3 PSU's got hit hard with a<BR>voltage =
spike=20
or something weird like that, is it really<BR>possible =
that ALL of=20
his MECs went bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" =
<animix _ at=20
_ animas _ dot _ net>=20
wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you =
think the=20
one I sent was bad ? It was working fine when I=20
pulled<BR>=3D<BR>>it from the =
rack.=3D20<BR>><BR>>I've=20
noticed a few posts recently regarding errors. Maybe no =
more than=20
=3D<BR>>usual, but it seemed like an unusually high =
number to me=20
over the last =3D<BR>>few weeks. Errors I'm not =
familiar with. It=20
will have been 10 years in =3D<BR>>November since Paris =
shipped.=20
I wonder if the lifespan of this hardware<BR>=3D<BR>>is =
starting=20
to fade. TG for TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom =
Bruhl"=20
<<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>>=20
wrote in message =
=3D<BR>>news:46f44c75$1@linux...<BR>> 3=20
bad mecs.<BR>><BR>> =
Hmmm?<BR>><BR>> I'll=20
know for a fact next Tuesday when there's<BR>> =
time to=20
test a couple on another=20
system.<BR>><BR>><BR>><BR>> <BR>> I =
choose=20
Polesoft Lockspam to fight spam, and you?<BR>> <A =
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML =
4.0=20
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META=20
content=3D3D"MSHTML 6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2>Do you think the one I sent was =
=3D<BR>>bad=20
?=3D20<BR>></FONT><FONT face=3D3DArial =
size=3D3D2>It was=20
working fine when I pulled it<BR>=3D<BR>>from =
the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> =
</DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2>I've noticed a few posts =
recently=20
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more =
than usual, but=20
it seemed like an unusually high number =
to<BR>=3D<BR>>me=20
over=3D20<BR>>the last few weeks. Errors I'm not =
familiar with.=20
It will have been =3D<BR>>10=3D20<BR>>years in =
November since=20
Paris shipped. I wonder if the lifespan of=20
this<BR>=3D<BR>>hardware=3D20<BR>>is starting to =
fade. TG for=20
TheSoniq, I=20
guess.</FONT></DIV><BR>><DIV><FONT =
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT:=20
5px; MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px =
solid;=20
MARGIN-RIGHT: 0px"><BR>> <DIV>"Tom =
Bruhl"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A =
href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =
<DIV><FONT face=3D3DArial =
size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2>time to test a couple on=20
another=3D20<BR>> =20
system.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT> =
</DIV><BR>> =20
<DIV><FONT face=3D3DArial =
size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT=20
size=3D3D2><BR><BR>I choose Polesoft =
Lockspam to=20
fight spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQUOTE></BL=
OCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_005F_01C800A6.99CD7850--
|
|
|
|
| Re: I know I found my problem [message #90683 is a reply to message #90627] |
Thu, 27 September 2007 22:36 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0064_01C80167.9FD736C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I had a SCSI that did that.. worked w/442, but wouldn't with a MEC. I =
think you probably hit it right on the head.=20
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46fb4262@linux...
AA,
I did find one scsi cable that had a couple dead pins out of five =
cables.
It allowed the 442 to work though. ? . Maybe those pins aren't used
in the Paris pin out? I chucked it anyway. Could be the source =
of
all evil.
Tom
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46fa1183@linux...
Aaron,
Thanks, I won't know about the modules until some new Mecs get =
delivered here.
I think I have the four I need almost on their way from multiple =
sources.
It looks like a chip in the master section of the scsi scorched mec =
got hit bad. We're
looking for the chip now. The other mecs may have less of a =
problem. Maybe some DC=20
down the WC line? Just a guess. Everything was AC grounded and no =
polarity shift.
We learned there's all kinds of protection fuses in line on the =
master section. It seems 'they' weren't
fried but the expensive stuff right after them was. . .
Tom
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f9cf56@linux...
I'll also toss out an edumacated guess that only the interface =
portion got fried and all your MEC cards are likely to be ok... holla =
back on that man.=20
Sorry, no spare MEC's around here, in fact I'm going to be growing =
my rig again shortly with a few more EDS cards :)
Say Tom, have you called The Soniq about repairing yours... he =
offers warranty on his work yano :)
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f9621b@linux...
Most absolutely hardware. 3 Mecs down for the count.
No word on the 10 modules that were onboard during
the mishap.
Anyone have a spare mec they can part with?
Assamundo
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f4fa9a@linux...
I'll double check Aaron.
Continuity is my middle name.
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f4e6c0@linux...
Dude, if you have 3 toasted MEC's I think it VERY likely you =
had a bad cable that put the hurt on them all as you swapped around =
parts.=20
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until =
Tuesday=20
when I'll check the two that might 'still work'. The =
hardware solution
is seeming to be the most logical at this point. Here's =
why:
I was working perfectly with 2 mecs loaded to the gills =
and a 442.
I wanted one more mec and bought one from Deej. =
Mistakenly,
I installed it without hiding my default project. Paris =
freaked
and I went through days of turmoil looking to get back to =
where
I was. Paris refused to boot with mecs and no 442 at that =
time.
Next I built another comp to test eds and cables and the =
442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and =
never got a=20
good Paris boot. Every time it wouldn't boot there was a =
Mec attached.
Even the 442 boots were flakey (no patchbay connections). =
I didn't learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, =
Deej's mec
and the 442. We used the mec throughout all testing until =
the end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely =
the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default proj) =
and Paris
would not boot with my other Mec that is loaded to the =
gills. I deleted
the Scherzo drivers, reloaded the new ones I just got, =
uninstalled the
subsystem and reloaded it. Once I changed to the 442 the =
system was fine.
Let me rephrase "Paris would not boot" . . . Actually it =
would usually start
up but no audio was available in the patchbay except with =
the 442.
My take is that the introduction of DJ's mec (whether it =
worked or didn't,
let's assume that it worked) was screwy probably by my own =
doing. I
removed it and later shorted a SCSI 2 cable at the Master =
Mec sometime during that
next week. There was smoke in the power supply area so I =
never tried that
Mec again. My other mec was attached at that time. I now =
think it fried something
in their too.
I am trying DJs and my hopefully unfried mec at another =
studio on Tuesday to confirm
that neither works. If I'm wrong then we're back to =
software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message =
news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the real
likelihood of that? Unless all 3 PSU's got hit hard with =
a
voltage spike or something weird like that, is it really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working =
fine when I pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. =
Maybe no more than =3D
>usual, but it seemed like an unusually high number to =
me over the last =3D
>few weeks. Errors I'm not familiar with. It will have =
been 10 years in =3D
>November since Paris shipped. I wonder if the lifespan =
of this hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =
=3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" =
name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the =
one I sent was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working =
fine when I pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a few =
posts recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an =
unusually high number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It =
will have been =3D
>10=3D20
>years in November since Paris shipped. I wonder if the =
lifespan of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I =
guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad =
mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial =
size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for a =
fact next Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a =
couple on another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft =
Lockspam to fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_0064_01C80167.9FD736C0
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.16525" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I had a SCSI that did that.. worked =
w/442, but=20
wouldn't with a MEC. I think you probably hit it right on the head.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>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 message=20
<A href=3D"news:46fb4262@linux">news:46fb4262@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>AA,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I did find one scsi cable that =
had a couple=20
dead pins out of five cables.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>It allowed the 442 to work though. ? =
.. =20
Maybe those pins aren't used</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in the Paris pin =
out? I=20
chucked it anyway. Could be the source of</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>all evil.</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>
<DIV><FONT face=3DArial size=3D2></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=20
message <A =
href=3D"news:46fa1183@linux">news:46fa1183@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Aaron,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks, I won't know about the =
modules until=20
some new Mecs get delivered here.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I think I have the four I need =
almost on their=20
way from multiple sources.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It looks like a chip in the master =
section of=20
the scsi scorched mec got hit bad. We're</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>looking for the chip now. The =
other=20
</FONT><FONT face=3DArial size=3D2>mecs may have less of a =
problem. Maybe=20
some DC </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>down the WC line? Just a =
guess. =20
Everything was AC grounded and no polarity shift.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We learned there's all kinds of =
protection=20
fuses in line on the master section. It seems 'they'=20
weren't</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>fried but the expensive stuff right =
after them=20
was. . .</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>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></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>>=20
wrote in message <A=20
href=3D"news:46f9cf56@linux">news:46f9cf56@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll also toss out an edumacated =
guess that=20
only the interface portion got fried and all your MEC cards are =
likely to=20
be ok... holla back on that man. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sorry, no spare MEC's around =
here, in fact=20
I'm going to be growing my rig again shortly with a few more EDS =
cards=20
:)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Say Tom, have you called The =
Soniq about=20
repairing yours... he offers warranty on his work yano =
:)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>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:46f9621b@linux">news:46f9621b@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Most absolutely hardware. =
3 Mecs down=20
for the count.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>No word on the 10 modules that =
were onboard=20
during</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the mishap.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Anyone have a spare mec they =
can part=20
with?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Assamundo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></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 <A =
href=3D"news:46f4fa9a@linux">news:46f4fa9a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll double check =
Aaron.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Continuity is my middle=20
name.</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>>=20
wrote in message <A=20
=
href=3D"news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Dude, if you have 3 toasted =
MEC's I=20
think it VERY likely you had a bad cable that put the hurt =
on them=20
all as you swapped around parts. </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>>=20
wrote in message <A=20
=
href=3D"news:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Intersted =
people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is=20
unlikely. It's not confirmed until Tuesday =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT=20
face=3DArial size=3D2>that might 'still work'. The =
hardware=20
solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the most =
logical at=20
this point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly =
with 2 mecs=20
loaded to the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec and =
bought one=20
from Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without =
hiding my=20
default project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days =
of turmoil=20
looking to get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris =
refused to boot=20
with mecs and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another comp =
to test eds=20
and cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went =
</FONT><FONT=20
face=3DArial size=3D2>fine. No probs. This =
seemed=20
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in the =
studio with=20
both computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. =
Every time it=20
wouldn't boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were =
flakey (no=20
patchbay connections). I didn't learn </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this=20
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a =
techs place=20
with the Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We =
used the mec=20
throughout all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh =
Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was =
introduced=20
Paris booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not=20
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my =
original C=20
drive (no default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot =
with my other Mec=20
that is loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, =
reloaded the new=20
ones I just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded =
it. Once=20
I changed to the 442 the system was fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris =
would not=20
boot" . . . Actually it would usually =
start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was =
available in the=20
patchbay except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the =
introduction of=20
DJ's mec (whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it =
worked)=20
</FONT><FONT face=3DArial size=3D2>was screwy probably by =
my own=20
doing. I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later =
shorted a SCSI 2=20
cable at the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There =
was smoke in=20
the power supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My =
other mec=20
was attached at that time. I now think it fried=20
something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their =
too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my =
hopefully=20
unfried mec at another studio on Tuesday to =
confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. =
If I'm=20
wrong then we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's=20
over.</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>
<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>"Neil" <<A =
href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>>=20
wrote in message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
all seriousness - THREE bad MEC's??? What's the=20
real<BR>likelihood of that? Unless all 3 PSU's got hit =
hard with=20
a<BR>voltage spike or something weird like that, is it=20
really<BR>possible that ALL of his MECs went=20
bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at _ =
animas _=20
dot _ net>=20
wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you =
think=20
the one I sent was bad ? It was working fine when I=20
pulled<BR>=3D<BR>>it from the =
rack.=3D20<BR>><BR>>I've=20
noticed a few posts recently regarding errors. Maybe no =
more=20
than =3D<BR>>usual, but it seemed like an unusually =
high number=20
to me over the last =3D<BR>>few weeks. Errors I'm not =
familiar=20
with. It will have been 10 years in =3D<BR>>November =
since=20
Paris shipped. I wonder if the lifespan of this=20
hardware<BR>=3D<BR>>is starting to fade. TG for =
TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom =
Bruhl"=20
<<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>>=20
wrote in message =
=3D<BR>>news:46f44c75$1@linux...<BR>> =20
3 bad mecs.<BR>><BR>> =
Hmmm?<BR>><BR>> =20
I'll know for a fact next Tuesday when =
there's<BR>> =20
time to test a couple on another=20
system.<BR>><BR>><BR>><BR>> <BR>> I =
choose=20
Polesoft Lockspam to fight spam, and you?<BR>> =
<A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD =
HTML 4.0=20
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META=20
content=3D3D"MSHTML 6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2>Do you think the one I sent was =
=3D<BR>>bad=20
?=3D20<BR>></FONT><FONT face=3D3DArial =
size=3D3D2>It=20
was working fine when I pulled it<BR>=3D<BR>>from=20
the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2>I've noticed a few posts recently =
=3D<BR>>regarding=20
errors.=3D20<BR>>Maybe no more than usual, but it =
seemed like=20
an unusually high number to<BR>=3D<BR>>me =
over=3D20<BR>>the=20
last few weeks. Errors I'm not familiar with. It will =
have been=20
=3D<BR>>10=3D20<BR>>years in November since Paris =
shipped. I=20
wonder if the lifespan of =
this<BR>=3D<BR>>hardware=3D20<BR>>is=20
starting to fade. TG for TheSoniq, I=20
=
guess.</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial=20
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT:=20
5px; MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 =
2px solid;=20
MARGIN-RIGHT: 0px"><BR>> <DIV>"Tom =
Bruhl"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A =
href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad=20
mecs.</FONT></DIV><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial =
size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2>time to =
test a=20
couple on another=3D20<BR>> =20
system.</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial =
size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>> =20
<DIV><FONT size=3D3D2><BR><BR>I =
choose=20
Polesoft Lockspam to fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQUOTE></BL=
OCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML >
------=_NextPart_000_0064_01C80167.9FD736C0--
|
|
|
|
| Re: I know I found my problem [message #90700 is a reply to message #90683] |
Fri, 28 September 2007 08:40 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_001A_01C801C4.5290AC90
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Aaron,
Thanks for the reinforcement.
Tom
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46fc943b@linux...
I had a SCSI that did that.. worked w/442, but wouldn't with a MEC. I =
think you probably hit it right on the head.=20
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46fb4262@linux...
AA,
I did find one scsi cable that had a couple dead pins out of five =
cables.
It allowed the 442 to work though. ? . Maybe those pins aren't used
in the Paris pin out? I chucked it anyway. Could be the source =
of
all evil.
Tom
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46fa1183@linux...
Aaron,
Thanks, I won't know about the modules until some new Mecs get =
delivered here.
I think I have the four I need almost on their way from multiple =
sources.
It looks like a chip in the master section of the scsi scorched =
mec got hit bad. We're
looking for the chip now. The other mecs may have less of a =
problem. Maybe some DC=20
down the WC line? Just a guess. Everything was AC grounded and =
no polarity shift.
We learned there's all kinds of protection fuses in line on the =
master section. It seems 'they' weren't
fried but the expensive stuff right after them was. . .
Tom
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f9cf56@linux...
I'll also toss out an edumacated guess that only the interface =
portion got fried and all your MEC cards are likely to be ok... holla =
back on that man.=20
Sorry, no spare MEC's around here, in fact I'm going to be =
growing my rig again shortly with a few more EDS cards :)
Say Tom, have you called The Soniq about repairing yours... he =
offers warranty on his work yano :)
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f9621b@linux...
Most absolutely hardware. 3 Mecs down for the count.
No word on the 10 modules that were onboard during
the mishap.
Anyone have a spare mec they can part with?
Assamundo
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f4fa9a@linux...
I'll double check Aaron.
Continuity is my middle name.
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f4e6c0@linux...
Dude, if you have 3 toasted MEC's I think it VERY likely =
you had a bad cable that put the hurt on them all as you swapped around =
parts.=20
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed =
until Tuesday=20
when I'll check the two that might 'still work'. The =
hardware solution
is seeming to be the most logical at this point. Here's =
why:
I was working perfectly with 2 mecs loaded to the gills =
and a 442.
I wanted one more mec and bought one from Deej. =
Mistakenly,
I installed it without hiding my default project. Paris =
freaked
and I went through days of turmoil looking to get back =
to where
I was. Paris refused to boot with mecs and no 442 at =
that time.
Next I built another comp to test eds and cables and the =
442. =20
Everything went fine. No probs. This seemed promising.
Next I tried again in the studio with both computers and =
never got a=20
good Paris boot. Every time it wouldn't boot there was =
a Mec attached.
Even the 442 boots were flakey (no patchbay =
connections). I didn't learn=20
anything from this effort.
2 days ago I went to a techs place with the Paris comp, =
Deej's mec
and the 442. We used the mec throughout all testing =
until the end.
Fresh C drive, fresh Paris install.
As soon as the 442 was introduced Paris booted. Likely =
the Deej
mec is faulty but not necessarily.
Today I went back to my original C drive (no default =
proj) and Paris
would not boot with my other Mec that is loaded to the =
gills. I deleted
the Scherzo drivers, reloaded the new ones I just got, =
uninstalled the
subsystem and reloaded it. Once I changed to the 442 =
the system was fine.
Let me rephrase "Paris would not boot" . . . Actually =
it would usually start
up but no audio was available in the patchbay except =
with the 442.
My take is that the introduction of DJ's mec (whether it =
worked or didn't,
let's assume that it worked) was screwy probably by my =
own doing. I
removed it and later shorted a SCSI 2 cable at the =
Master Mec sometime during that
next week. There was smoke in the power supply area so =
I never tried that
Mec again. My other mec was attached at that time. I =
now think it fried something
in their too.
I am trying DJs and my hopefully unfried mec at another =
studio on Tuesday to confirm
that neither works. If I'm wrong then we're back to =
software.
It ain't over till it's over.
Tom
=20
"Neil" <IOU@OIU.com> wrote in message =
news:46f46d03$1@linux...
In all seriousness - THREE bad MEC's??? What's the =
real
likelihood of that? Unless all 3 PSU's got hit hard =
with a
voltage spike or something weird like that, is it =
really
possible that ALL of his MECs went bad?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>
>Tom,
>
>Do you think the one I sent was bad ? It was working =
fine when I pulled
=3D
>it from the rack.=3D20
>
>I've noticed a few posts recently regarding errors. =
Maybe no more than =3D
>usual, but it seemed like an unusually high number to =
me over the last =3D
>few weeks. Errors I'm not familiar with. It will have =
been 10 years in =3D
>November since Paris shipped. I wonder if the =
lifespan of this hardware
=3D
>is starting to fade. TG for TheSoniq, I guess.
>
>Deej
>
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =
=3D
>news:46f44c75$1@linux...
> 3 bad mecs.
>
> Hmmm?
>
> I'll know for a fact next Tuesday when there's
> time to test a couple on another system.
>
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!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.6000.16525" =
name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial =
size=3D3D2>Tom,</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>Do you think the =
one I sent was =3D
>bad ?=3D20
></FONT><FONT face=3D3DArial size=3D3D2>It was working =
fine when I pulled it
=3D
>from the=3D20
>rack. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>I've noticed a =
few posts recently =3D
>regarding errors.=3D20
>Maybe no more than usual, but it seemed like an =
unusually high number to
=3D
>me over=3D20
>the last few weeks. Errors I'm not familiar with. It =
will have been =3D
>10=3D20
>years in November since Paris shipped. I wonder if =
the lifespan of this
=3D
>hardware=3D20
>is starting to fade. TG for TheSoniq, I =
guess.</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial =
size=3D3D2>Deej</FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; =3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =3D
>in message=3D20
> <A =
href=3D3D"news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>3 bad =
mecs.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial =
size=3D3D2>Hmmm?</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'll know for =
a fact next Tuesday =3D
>when=3D20
> there's</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>time to test a =
couple on another=3D20
> system.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft =
Lockspam to fight spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_001A_01C801C4.5290AC90
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Aaron,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for the =
reinforcement.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</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 in=20
message <A =
href=3D"news:46fc943b@linux">news:46fc943b@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I had a SCSI that did that.. worked =
w/442, but=20
wouldn't with a MEC. I think you probably hit it right on the head.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>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:46fb4262@linux">news:46fb4262@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>AA,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I did find one scsi cable that =
had a=20
couple dead pins out of five cables.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>It allowed the 442 to work though. =
? . =20
Maybe those pins aren't used</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in the Paris pin =
out? =20
I chucked it anyway. Could be the source of</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>all evil.</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>
<DIV><FONT face=3DArial size=3D2></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=20
message <A =
href=3D"news:46fa1183@linux">news:46fa1183@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Aaron,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks, I won't know about the =
modules until=20
some new Mecs get delivered here.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I think I have the four I need =
almost on=20
their way from multiple sources.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It looks like a chip in the =
master section of=20
the scsi scorched mec got hit bad. We're</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>looking for the chip now. =
The other=20
</FONT><FONT face=3DArial size=3D2>mecs may have less of a =
problem. =20
Maybe some DC </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>down the WC line? Just a =
guess. =20
Everything was AC grounded and no polarity shift.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We learned there's all kinds of =
protection=20
fuses in line on the master section. It seems 'they'=20
weren't</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>fried but the expensive stuff =
right after=20
them was. . .</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>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></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>>=20
wrote in message <A=20
href=3D"news:46f9cf56@linux">news:46f9cf56@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll also toss out an =
edumacated guess that=20
only the interface portion got fried and all your MEC cards are =
likely=20
to be ok... holla back on that man. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sorry, no spare MEC's around =
here, in fact=20
I'm going to be growing my rig again shortly with a few more EDS =
cards=20
:)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Say Tom, have you called The =
Soniq about=20
repairing yours... he offers warranty on his work yano =
:)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>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 =
message <A =
href=3D"news:46f9621b@linux">news:46f9621b@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Most absolutely =
hardware. 3 Mecs=20
down for the count.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>No word on the 10 modules =
that were=20
onboard during</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the mishap.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Anyone have a spare mec they =
can part=20
with?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Assamundo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></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=20
in message <A=20
=
href=3D"news:46f4fa9a@linux">news:46f4fa9a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I'll double check =
Aaron.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Continuity is my middle=20
name.</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>>=20
wrote in message <A=20
=
href=3D"news:46f4e6c0@linux">news:46f4e6c0@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Dude, if you have 3 =
toasted MEC's I=20
think it VERY likely you had a bad cable that put the hurt =
on them=20
all as you swapped around parts. </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>>=20
wrote in message <A=20
=
href=3D"news:46f472e2@linux">news:46f472e2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Intersted =
people,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I know 3 fried mecs is=20
unlikely. It's not confirmed until Tuesday =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when I'll check the two =
</FONT><FONT face=3DArial size=3D2>that might 'still =
work'. =20
The hardware solution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is seeming to be the =
most logical=20
at this point. Here's why:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was working perfectly =
with 2 mecs=20
loaded to the gills and a 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I wanted one more mec =
and bought=20
one from Deej. Mistakenly,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I installed it without =
hiding my=20
default project. Paris freaked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and I went through days =
of turmoil=20
looking to get back to where</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I was. Paris =
refused to boot=20
with mecs and no 442 at that time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I built another =
comp to test=20
eds and cables and the 442. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything went =
</FONT><FONT=20
face=3DArial size=3D2>fine. No probs. This =
seemed=20
promising.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Next I tried again in =
the studio=20
with both computers and never got a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>good Paris boot. =
Every time=20
it wouldn't boot there was a Mec attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Even the 442 boots were =
flakey (no=20
patchbay connections). I didn't learn =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>anything from this=20
effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2 days ago I went to a =
techs place=20
with the Paris comp, Deej's mec</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the 442. We =
used the mec=20
throughout all testing until the end.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Fresh C drive, fresh =
Paris=20
install.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As soon as the 442 was =
introduced=20
Paris booted. Likely the Deej</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mec is faulty but not=20
necessarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Today I went back to my =
original C=20
drive (no default proj) and Paris</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>would not boot =
with my other=20
Mec that is loaded to the gills. I deleted</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Scherzo drivers, =
reloaded the=20
new ones I just got, uninstalled the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>subsystem and reloaded =
it. =20
Once I changed to the 442 the system was =
fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Let me rephrase "Paris =
would not=20
boot" . . . Actually it would usually =
start</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up but no audio was =
available in=20
the patchbay except with the 442.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My take is that the =
introduction of=20
DJ's mec (whether it worked or didn't,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>let's assume that it =
worked)=20
</FONT><FONT face=3DArial size=3D2>was screwy probably =
by my own=20
doing. I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>removed it and later =
shorted a SCSI=20
2 cable at the Master Mec sometime during =
that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There =
was smoke in=20
the power supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. =
My other mec=20
was attached at that time. I now think it fried=20
something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their =
too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my =
hopefully=20
unfried mec at another studio on Tuesday to =
confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither =
works. If I'm=20
wrong then we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's =
over.</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>
<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>"Neil" <<A=20
href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>> wrote =
in message=20
<A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
all seriousness - THREE bad MEC's??? What's the=20
real<BR>likelihood of that? Unless all 3 PSU's got hit =
hard=20
with a<BR>voltage spike or something weird like that, =
is it=20
really<BR>possible that ALL of his MECs went=20
bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at _ =
animas=20
_ dot _ net>=20
wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do =
you think=20
the one I sent was bad ? It was working fine when I=20
pulled<BR>=3D<BR>>it from the =
rack.=3D20<BR>><BR>>I've=20
noticed a few posts recently regarding errors. Maybe =
no more=20
than =3D<BR>>usual, but it seemed like an unusually =
high=20
number to me over the last =3D<BR>>few weeks. =
Errors I'm not=20
familiar with. It will have been 10 years in =
=3D<BR>>November=20
since Paris shipped. I wonder if the lifespan of this=20
hardware<BR>=3D<BR>>is starting to fade. TG for =
TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom =
Bruhl"=20
<<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>>=20
wrote in message=20
=3D<BR>>news:46f44c75$1@linux...<BR>> 3 =
bad=20
mecs.<BR>><BR>> =
Hmmm?<BR>><BR>> I'll=20
know for a fact next Tuesday when =
there's<BR>> time=20
to test a couple on another=20
system.<BR>><BR>><BR>><BR>> <BR>> =
I choose=20
Polesoft Lockspam to fight spam, and =
you?<BR>> <A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD =
HTML 4.0=20
=
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML 6.00.6000.16525"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Tom,</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Do you think the one I sent was =
=3D<BR>>bad=20
?=3D20<BR>></FONT><FONT face=3D3DArial =
size=3D3D2>It=20
was working fine when I pulled it<BR>=3D<BR>>from=20
the=3D20<BR>>rack.=20
</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>I've noticed a few posts recently=20
=3D<BR>>regarding errors.=3D20<BR>>Maybe no more =
than usual,=20
but it seemed like an unusually high number =
to<BR>=3D<BR>>me=20
over=3D20<BR>>the last few weeks. Errors I'm not =
familiar=20
with. It will have been =
=3D<BR>>10=3D20<BR>>years in=20
November since Paris shipped. I wonder if the lifespan =
of=20
this<BR>=3D<BR>>hardware=3D20<BR>>is starting to =
fade. TG=20
for TheSoniq, I=20
=
guess.</FONT></DIV><BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><DIV><FONT face=3D3DArial =
=
size=3D3D2>Deej</FONT></DIV& gt; <BR>><DIV><FONT=20
face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT:=20
5px; MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 =
2px=20
solid; MARGIN-RIGHT: 0px"><BR>> =
<DIV>"Tom=20
Bruhl" <<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A =
href=3D3D"<A=20
=
href=3D'news:46f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV'>news:46=
f44c75$1@linux">news:46f44c75$1@linux</A>...</DIV</A>><BR>=
> =20
<DIV><FONT face=3D3DArial size=3D3D2>3 bad =
mecs.</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial =
size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT =
face=3D3DArial=20
=
size=3D3D2>Hmmm?</FONT></DIV& ;gt; <BR>> =20
<DIV><FONT face=3D3DArial =
size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>I'll know for a fact next Tuesday=20
=3D<BR>>when=3D20<BR>> =20
there's</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2>time =
to test a=20
couple on another=3D20<BR>> =20
system.</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial =
size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>> =
<DIV><FONT =
size=3D3D2><BR><BR>I choose=20
Polesoft Lockspam to fight=20
spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =
=3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQUOTE></BL=
OCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE ></BODY></HTM=
L>
------=_NextPart_000_001A_01C801C4.5290AC90--
|
|
|
|
Goto Forum:
Current Time: Thu Dec 12 05:33:34 PST 2024
Total time taken to generate the page: 0.11111 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
