Home » The PARIS Forums » PARIS: Main » Reverse engineering a disaster
|
|
|
|
| Re: Reverse engineering a disaster [message #74482 is a reply to message #74473] |
Thu, 19 October 2006 22:42   |
excelav
Messages: 2130
Registered: July 2005
Location: Metro Detroit
|
Senior Member |
|
|
"DJ" <no@way.jack> wrote:
>I was talking to Morgan today about computers. Since my Paris rig has been
>amazingly stable for the last few years, I was really surprised when it
>started giving me problems last weekend. He made the comment that audio
DAWs
>seem to be almost human and have personalities. I have noticed this too
on
>my native machine, but not wo much with Paris. The problem I was having
was
>a problem I've always been able to solve involving just reseating a cable
>between the master EDS card and the MEC. We'll this didn't work on repeated
>ovccasions and I finally just threw up my hands.
>
>Well, I just restored a Ghost image of an old install and it is back up
and
>running. What seems to have happened is that I changed from Matrox to NForce
>video cards. the rig was extremely stable. Then I decided to do an
>experiment and so I removed the original NForce video card and replaced
it
>with a similar model card GE Force 5500 dual head, but it was not an
>*NVidia* model, it was by another manufacturer. I started having some wierd
>glitches which required me to uninstall/reinstall and chase my tail around
>for a while (I posted about this on another thread last weekend). Well,
it
>seems that this was what caused Paris to start misbehaving. Apparently the
>driver snafu somehow affected the ability of the Paris.ini to initialize
the
>MEC on card A. I have recreated the problem exactly and fixed it by a simple
>uninstall/reinstall of Paris..sooo.the moral to this story is if you start
>having what appear to be mechanical problems, the first thing you should
do
>is uninstall/reinstall the Paris app. I'm hoping this will also fix my car
>too.
>
>;o)
>
>
With video cards, often the third party manufactures ship their cards with
their own version of the driver. It's a crap shoot when it comes to which
driver to use, the Third party's or the chip manufacture's driver. If your
having problems, try the other driver.
James
|
|
|
|
| Re: Reverse engineering a disaster [message #74483 is a reply to message #74482] |
Thu, 19 October 2006 22:43 |
excelav
Messages: 2130
Registered: July 2005
Location: Metro Detroit
|
Senior Member |
|
|
By the way, I'm glad your back on track!
James
"James McCloskey" <excelsm@hotmail.com> wrote:
>
>"DJ" <no@way.jack> wrote:
>>I was talking to Morgan today about computers. Since my Paris rig has been
>
>>amazingly stable for the last few years, I was really surprised when it
>
>>started giving me problems last weekend. He made the comment that audio
>DAWs
>>seem to be almost human and have personalities. I have noticed this too
>on
>>my native machine, but not wo much with Paris. The problem I was having
>was
>>a problem I've always been able to solve involving just reseating a cable
>
>>between the master EDS card and the MEC. We'll this didn't work on repeated
>
>>ovccasions and I finally just threw up my hands.
>>
>>Well, I just restored a Ghost image of an old install and it is back up
>and
>>running. What seems to have happened is that I changed from Matrox to NForce
>
>>video cards. the rig was extremely stable. Then I decided to do an
>>experiment and so I removed the original NForce video card and replaced
>it
>>with a similar model card GE Force 5500 dual head, but it was not an
>>*NVidia* model, it was by another manufacturer. I started having some wierd
>
>>glitches which required me to uninstall/reinstall and chase my tail around
>
>>for a while (I posted about this on another thread last weekend). Well,
>it
>>seems that this was what caused Paris to start misbehaving. Apparently
the
>
>>driver snafu somehow affected the ability of the Paris.ini to initialize
>the
>>MEC on card A. I have recreated the problem exactly and fixed it by a simple
>
>>uninstall/reinstall of Paris..sooo.the moral to this story is if you start
>
>>having what appear to be mechanical problems, the first thing you should
>do
>>is uninstall/reinstall the Paris app. I'm hoping this will also fix my
car
>
>>too.
>>
>>;o)
>>
>>
>
>With video cards, often the third party manufactures ship their cards with
>their own version of the driver. It's a crap shoot when it comes to which
>driver to use, the Third party's or the chip manufacture's driver. If your
>having problems, try the other driver.
>
>James
>
|
|
|
|
| Re: Reverse engineering a disaster [message #74484 is a reply to message #74483] |
Thu, 19 October 2006 23:14 |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
Man.it's been a struggle..thanks
;o)
"James McCloskey" <excelsm@hotmail.com> wrote in message
news:45386203@linux...
>
> By the way, I'm glad your back on track!
>
> James
>
> "James McCloskey" <excelsm@hotmail.com> wrote:
>>
>>"DJ" <no@way.jack> wrote:
>>>I was talking to Morgan today about computers. Since my Paris rig has
>>>been
>>
>>>amazingly stable for the last few years, I was really surprised when it
>>
>>>started giving me problems last weekend. He made the comment that audio
>>DAWs
>>>seem to be almost human and have personalities. I have noticed this too
>>on
>>>my native machine, but not wo much with Paris. The problem I was having
>>was
>>>a problem I've always been able to solve involving just reseating a cable
>>
>>>between the master EDS card and the MEC. We'll this didn't work on
>>>repeated
>>
>>>ovccasions and I finally just threw up my hands.
>>>
>>>Well, I just restored a Ghost image of an old install and it is back up
>>and
>>>running. What seems to have happened is that I changed from Matrox to
>>>NForce
>>
>>>video cards. the rig was extremely stable. Then I decided to do an
>>>experiment and so I removed the original NForce video card and replaced
>>it
>>>with a similar model card GE Force 5500 dual head, but it was not an
>>>*NVidia* model, it was by another manufacturer. I started having some
>>>wierd
>>
>>>glitches which required me to uninstall/reinstall and chase my tail
>>>around
>>
>>>for a while (I posted about this on another thread last weekend). Well,
>>it
>>>seems that this was what caused Paris to start misbehaving. Apparently
> the
>>
>>>driver snafu somehow affected the ability of the Paris.ini to initialize
>>the
>>>MEC on card A. I have recreated the problem exactly and fixed it by a
>>>simple
>>
>>>uninstall/reinstall of Paris..sooo.the moral to this story is if you
>>>start
>>
>>>having what appear to be mechanical problems, the first thing you should
>>do
>>>is uninstall/reinstall the Paris app. I'm hoping this will also fix my
> car
>>
>>>too.
>>>
>>>;o)
>>>
>>>
>>
>>With video cards, often the third party manufactures ship their cards with
>>their own version of the driver. It's a crap shoot when it comes to which
>>driver to use, the Third party's or the chip manufacture's driver. If
>>your
>>having problems, try the other driver.
>>
>>James
>>
>
|
|
|
|
| Re: Reverse engineering a disaster [message #74523 is a reply to message #74473] |
Fri, 20 October 2006 13:33 |
TCB
Messages: 1261
Registered: July 2007
|
Senior Member |
|
|
First, all due respect to Morgan but computers don't have personalities, preferences,
or emotions any more than your microwave does. We carbon based systems and
our massively parallel pattern matching brains like to think the rest of
the world works and doesn't work like us, and to a point that's a useful
way to explain things only becasue it's familiar. But that pattern matching
gets us in trouble when we start applying it to things like machines, which
is unsurprising when it's remembered we evolved to survive on African grasslands
full of somewhat similar things that we needed to eat or might want to eat
us, but with very few big block 390s, Rolex watches, and yes computers. But
when it gets down to it computers are devices and files. Nothing more. One
of the great things about linux is that nearly every file you might need
to find is a text config file, and if it's a binary file that is the problem
you can always get the text file that was used to create the binary. People
think us linux dweebs are cheap, but that's not really the point.
Anyway, for you Deej, do you back up your registry before making a hardware
change? I'd say 99% of the serious hardware problems can be fixed by changing
back the hardware and replacing the registry. If I'm worried about something
I'll do it the cave man way, which is boot off of a CD and copy every file
in c:\Windows\system32\config to a folder in C:\temp\reg_bac. If something
goes to hell just boot off a CD again, copy the files back, and that's that.
TCB
"DJ" <no@way.jack> wrote:
>I was talking to Morgan today about computers. Since my Paris rig has been
>amazingly stable for the last few years, I was really surprised when it
>started giving me problems last weekend. He made the comment that audio
DAWs
>seem to be almost human and have personalities. I have noticed this too
on
>my native machine, but not wo much with Paris. The problem I was having
was
>a problem I've always been able to solve involving just reseating a cable
>between the master EDS card and the MEC. We'll this didn't work on repeated
>ovccasions and I finally just threw up my hands.
>
>Well, I just restored a Ghost image of an old install and it is back up
and
>running. What seems to have happened is that I changed from Matrox to NForce
>video cards. the rig was extremely stable. Then I decided to do an
>experiment and so I removed the original NForce video card and replaced
it
>with a similar model card GE Force 5500 dual head, but it was not an
>*NVidia* model, it was by another manufacturer. I started having some wierd
>glitches which required me to uninstall/reinstall and chase my tail around
>for a while (I posted about this on another thread last weekend). Well,
it
>seems that this was what caused Paris to start misbehaving. Apparently the
>driver snafu somehow affected the ability of the Paris.ini to initialize
the
>MEC on card A. I have recreated the problem exactly and fixed it by a simple
>uninstall/reinstall of Paris..sooo.the moral to this story is if you start
>having what appear to be mechanical problems, the first thing you should
do
>is uninstall/reinstall the Paris app. I'm hoping this will also fix my car
>too.
>
>;o)
>
>
|
|
|
|
| Re: Reverse engineering a disaster [message #74524 is a reply to message #74523] |
Fri, 20 October 2006 13:44 |
John [1]
Messages: 2229
Registered: September 2005
|
Senior Member |
|
|
Mine has a personality. Sometimes it's fans scream at me so I kick it.
Works great. :-)
John
TCB wrote:
> First, all due respect to Morgan but computers don't have personalities, preferences,
> or emotions any more than your microwave does. We carbon based systems and
> our massively parallel pattern matching brains like to think the rest of
> the world works and doesn't work like us, and to a point that's a useful
> way to explain things only becasue it's familiar. But that pattern matching
> gets us in trouble when we start applying it to things like machines, which
> is unsurprising when it's remembered we evolved to survive on African grasslands
> full of somewhat similar things that we needed to eat or might want to eat
> us, but with very few big block 390s, Rolex watches, and yes computers. But
> when it gets down to it computers are devices and files. Nothing more. One
> of the great things about linux is that nearly every file you might need
> to find is a text config file, and if it's a binary file that is the problem
> you can always get the text file that was used to create the binary. People
> think us linux dweebs are cheap, but that's not really the point.
>
> Anyway, for you Deej, do you back up your registry before making a hardware
> change? I'd say 99% of the serious hardware problems can be fixed by changing
> back the hardware and replacing the registry. If I'm worried about something
> I'll do it the cave man way, which is boot off of a CD and copy every file
> in c:\Windows\system32\config to a folder in C:\temp\reg_bac. If something
> goes to hell just boot off a CD again, copy the files back, and that's that.
>
>
>
> TCB
>
> "DJ" <no@way.jack> wrote:
>> I was talking to Morgan today about computers. Since my Paris rig has been
>
>> amazingly stable for the last few years, I was really surprised when it
>
>> started giving me problems last weekend. He made the comment that audio
> DAWs
>> seem to be almost human and have personalities. I have noticed this too
> on
>> my native machine, but not wo much with Paris. The problem I was having
> was
>> a problem I've always been able to solve involving just reseating a cable
>
>> between the master EDS card and the MEC. We'll this didn't work on repeated
>
>> ovccasions and I finally just threw up my hands.
>>
>> Well, I just restored a Ghost image of an old install and it is back up
> and
>> running. What seems to have happened is that I changed from Matrox to NForce
>
>> video cards. the rig was extremely stable. Then I decided to do an
>> experiment and so I removed the original NForce video card and replaced
> it
>> with a similar model card GE Force 5500 dual head, but it was not an
>> *NVidia* model, it was by another manufacturer. I started having some wierd
>
>> glitches which required me to uninstall/reinstall and chase my tail around
>
>> for a while (I posted about this on another thread last weekend). Well,
> it
>> seems that this was what caused Paris to start misbehaving. Apparently the
>
>> driver snafu somehow affected the ability of the Paris.ini to initialize
> the
>> MEC on card A. I have recreated the problem exactly and fixed it by a simple
>
>> uninstall/reinstall of Paris..sooo.the moral to this story is if you start
>
>> having what appear to be mechanical problems, the first thing you should
> do
>> is uninstall/reinstall the Paris app. I'm hoping this will also fix my car
>
>> too.
>>
>> ;o)
>>
>>
>
|
|
|
|
Goto Forum:
Current Time: Mon Jan 13 15:52:14 PST 2025
Total time taken to generate the page: 0.00945 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
