|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: OT: Tascam FW-1804 [message #88329 is a reply to message #88328] |
Thu, 19 July 2007 22:39   |
Aaron Allen
 Messages: 1988 Registered: May 2008
|
Senior Member |
|
|
t 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
|
|
|
|
|
|