Home » The PARIS Forums » PARIS: Main » My Error 7/7 dilemma continued...
| My Error 7/7 dilemma continued... [message #94380] |
Sat, 05 January 2008 15:56  |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
So....... ;o)
It occurred to me that I should put more effort into resolving this on the
existing MB. Just after some comments if you have any. Currently Paris attempts
to load, the MEC or 442 starts its "boot" and stops right at that point where
the internal sync light and the 48k light come on together. They stay that
way for far too long (compared to "normal") and then the 7/7 error appears.
IIRC that phase is when the MEC is actually attempting to make the audio
link with the EDS card. Presumably this is when EDS comms are going to suddenly
increase from some minor discussions about the boot process to an actual
stream of audio data traffic, so I can see that an IRQ issue might cause
issues at that point.
I'm currently exploring the idea that it's just an IRQ conflict, which seems
possible.
(*) I've noted that my "working" Paris install image is in ACPI mode. I'm
just changing to Standard PC to see if we can't sort some stuff out because...
(*) I noted that the Scherzo driver was being allocated to IRQ 19 by Windows.
It was on its own, but that's not the real IRQ (which was 5, but I've moved
it to 7), but a virtual Windows one. Why Windows made this crazy allocation
I'm not sure. Hopefully Standard PC mode will put it back on 7.
(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the crazy
MB has done something silly here.
In any case, the install image used to work, so this ACPI thingy doesn't
seem the likely cause. A BIOS reset may do it. Or it still could be a MB
hardware fault.
Annoying... ;o)
Cheers,
Kim.
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94382 is a reply to message #94380] |
Sat, 05 January 2008 16:12  |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
Mmm... neither the BIOS Defaults reset or the Standard PC thing seem to
have fixed it. Same deal.
Gosh damnit. ;o)
I'm just going to be really annoyed if I buy a new MB and that's not it.
I've tried a number of things here, many with some confidence of a result,
but nuttin' worked. I've got $4500 I plan to spend on car restorations in
the next 6 weeks. I know a MB is only $70 but I'm runnin' on empty. ;o)
But what I wouldn't do to get Paris up and running. I'm almost considering
loading Reaper to get some stuff done... :oS
Cheers,
Kim.
"Kim" <hiddensounds@hotmail.com> wrote:
>
>
>So....... ;o)
>
>It occurred to me that I should put more effort into resolving this on the
>existing MB. Just after some comments if you have any. Currently Paris attempts
>to load, the MEC or 442 starts its "boot" and stops right at that point
where
>the internal sync light and the 48k light come on together. They stay that
>way for far too long (compared to "normal") and then the 7/7 error appears.
>IIRC that phase is when the MEC is actually attempting to make the audio
>link with the EDS card. Presumably this is when EDS comms are going to suddenly
>increase from some minor discussions about the boot process to an actual
>stream of audio data traffic, so I can see that an IRQ issue might cause
>issues at that point.
>
>I'm currently exploring the idea that it's just an IRQ conflict, which seems
>possible.
>
>(*) I've noted that my "working" Paris install image is in ACPI mode. I'm
>just changing to Standard PC to see if we can't sort some stuff out because...
>
>(*) I noted that the Scherzo driver was being allocated to IRQ 19 by Windows.
>It was on its own, but that's not the real IRQ (which was 5, but I've moved
>it to 7), but a virtual Windows one. Why Windows made this crazy allocation
>I'm not sure. Hopefully Standard PC mode will put it back on 7.
>
>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the crazy
>MB has done something silly here.
>
>In any case, the install image used to work, so this ACPI thingy doesn't
>seem the likely cause. A BIOS reset may do it. Or it still could be a MB
>hardware fault.
>
>Annoying... ;o)
>
>Cheers,
>Kim.
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94384 is a reply to message #94382] |
Sat, 05 January 2008 15:28 |
Morgan
Messages: 133
Registered: August 2005
|
Senior Member |
|
|
Hi Kim,
I tried to respond to another post on this a while back
and got a posting error, I hope this one makes it.
We had some rigs that would get into a 7/7 error mode,
this always means the hardware cannot be seen.
We would use a pencil eraser on the contacts of the EDS
card and clean out the pci slot the best we could with a
De-Oxit type of spray . That usually would do the trick.
In a multi card system - do one card at a time :)
I hope this helps :)
Morgan
"Kim" <hiddensounds@hotmail.com> wrote in message news:47800ece$1@linux...
>
>
> Mmm... neither the BIOS Defaults reset or the Standard PC thing seem to
> have fixed it. Same deal.
>
> Gosh damnit. ;o)
>
> I'm just going to be really annoyed if I buy a new MB and that's not it.
> I've tried a number of things here, many with some confidence of a result,
> but nuttin' worked. I've got $4500 I plan to spend on car restorations in
> the next 6 weeks. I know a MB is only $70 but I'm runnin' on empty. ;o)
>
> But what I wouldn't do to get Paris up and running. I'm almost considering
> loading Reaper to get some stuff done... :oS
>
> Cheers,
> Kim.
>
> "Kim" <hiddensounds@hotmail.com> wrote:
>>
>>
>>So....... ;o)
>>
>>It occurred to me that I should put more effort into resolving this on the
>>existing MB. Just after some comments if you have any. Currently Paris
>>attempts
>>to load, the MEC or 442 starts its "boot" and stops right at that point
> where
>>the internal sync light and the 48k light come on together. They stay that
>>way for far too long (compared to "normal") and then the 7/7 error
>>appears.
>>IIRC that phase is when the MEC is actually attempting to make the audio
>>link with the EDS card. Presumably this is when EDS comms are going to
>>suddenly
>>increase from some minor discussions about the boot process to an actual
>>stream of audio data traffic, so I can see that an IRQ issue might cause
>>issues at that point.
>>
>>I'm currently exploring the idea that it's just an IRQ conflict, which
>>seems
>>possible.
>>
>>(*) I've noted that my "working" Paris install image is in ACPI mode. I'm
>>just changing to Standard PC to see if we can't sort some stuff out
>>because...
>>
>>(*) I noted that the Scherzo driver was being allocated to IRQ 19 by
>>Windows.
>>It was on its own, but that's not the real IRQ (which was 5, but I've
>>moved
>>it to 7), but a virtual Windows one. Why Windows made this crazy
>>allocation
>>I'm not sure. Hopefully Standard PC mode will put it back on 7.
>>
>>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the
>>crazy
>>MB has done something silly here.
>>
>>In any case, the install image used to work, so this ACPI thingy doesn't
>>seem the likely cause. A BIOS reset may do it. Or it still could be a MB
>>hardware fault.
>>
>>Annoying... ;o)
>>
>>Cheers,
>>Kim.
>
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94385 is a reply to message #94384] |
Sat, 05 January 2008 17:02 |
Morgan
Messages: 133
Registered: August 2005
|
Senior Member |
|
|
Hi Kim,
Here is the error message I was getting:
Outlook Express could not post your message. Subject 'Re: OK, so my Paris
machine is still cactus... ;o)', Account: 'news.parisnewsgroup.com',
Server: 'news.parisnewsgroup.com', Protocol: NNTP, Server Response: '441
Message is too old', Port: 119, Secure(SSL): No, Server Error: 441, Error
Number: 0x800CCCA9
"Morgan" <morganp@ntplx.net> wrote in message news:47801367@linux...
> Hi Kim,
> I tried to respond to another post on this a while back
> and got a posting error, I hope this one makes it.
>
> We had some rigs that would get into a 7/7 error mode,
> this always means the hardware cannot be seen.
>
> We would use a pencil eraser on the contacts of the EDS
> card and clean out the pci slot the best we could with a
> De-Oxit type of spray . That usually would do the trick.
> In a multi card system - do one card at a time :)
> I hope this helps :)
>
> Morgan
> "Kim" <hiddensounds@hotmail.com> wrote in message news:47800ece$1@linux...
>>
>>
>> Mmm... neither the BIOS Defaults reset or the Standard PC thing seem to
>> have fixed it. Same deal.
>>
>> Gosh damnit. ;o)
>>
>> I'm just going to be really annoyed if I buy a new MB and that's not it.
>> I've tried a number of things here, many with some confidence of a
>> result,
>> but nuttin' worked. I've got $4500 I plan to spend on car restorations in
>> the next 6 weeks. I know a MB is only $70 but I'm runnin' on empty. ;o)
>>
>> But what I wouldn't do to get Paris up and running. I'm almost
>> considering
>> loading Reaper to get some stuff done... :oS
>>
>> Cheers,
>> Kim.
>>
>> "Kim" <hiddensounds@hotmail.com> wrote:
>>>
>>>
>>>So....... ;o)
>>>
>>>It occurred to me that I should put more effort into resolving this on
>>>the
>>>existing MB. Just after some comments if you have any. Currently Paris
>>>attempts
>>>to load, the MEC or 442 starts its "boot" and stops right at that point
>> where
>>>the internal sync light and the 48k light come on together. They stay
>>>that
>>>way for far too long (compared to "normal") and then the 7/7 error
>>>appears.
>>>IIRC that phase is when the MEC is actually attempting to make the audio
>>>link with the EDS card. Presumably this is when EDS comms are going to
>>>suddenly
>>>increase from some minor discussions about the boot process to an actual
>>>stream of audio data traffic, so I can see that an IRQ issue might cause
>>>issues at that point.
>>>
>>>I'm currently exploring the idea that it's just an IRQ conflict, which
>>>seems
>>>possible.
>>>
>>>(*) I've noted that my "working" Paris install image is in ACPI mode. I'm
>>>just changing to Standard PC to see if we can't sort some stuff out
>>>because...
>>>
>>>(*) I noted that the Scherzo driver was being allocated to IRQ 19 by
>>>Windows.
>>>It was on its own, but that's not the real IRQ (which was 5, but I've
>>>moved
>>>it to 7), but a virtual Windows one. Why Windows made this crazy
>>>allocation
>>>I'm not sure. Hopefully Standard PC mode will put it back on 7.
>>>
>>>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the
>>>crazy
>>>MB has done something silly here.
>>>
>>>In any case, the install image used to work, so this ACPI thingy doesn't
>>>seem the likely cause. A BIOS reset may do it. Or it still could be a MB
>>>hardware fault.
>>>
>>>Annoying... ;o)
>>>
>>>Cheers,
>>>Kim.
>>
>
>
|
|
|
|
| Re: My Error 7/7 dilemma continued... Post error [message #94386 is a reply to message #94385] |
Sat, 05 January 2008 18:25 |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
Morgan,
That seems to be a local issue with your machine.
http://support.microsoft.com/kb/297166/en-us
Let me know if you need help with it.
Cheers,
Kim.
"Morgan" <morganp@ntplx.net> wrote:
>Hi Kim,
>
>Here is the error message I was getting:
>
>Outlook Express could not post your message. Subject 'Re: OK, so my Paris
>machine is still cactus... ;o)', Account: 'news.parisnewsgroup.com',
>Server: 'news.parisnewsgroup.com', Protocol: NNTP, Server Response: '441
>Message is too old', Port: 119, Secure(SSL): No, Server Error: 441, Error
>Number: 0x800CCCA9
>
>
>"Morgan" <morganp@ntplx.net> wrote in message news:47801367@linux...
>> Hi Kim,
>> I tried to respond to another post on this a while back
>> and got a posting error, I hope this one makes it.
>>
>> We had some rigs that would get into a 7/7 error mode,
>> this always means the hardware cannot be seen.
>>
>> We would use a pencil eraser on the contacts of the EDS
>> card and clean out the pci slot the best we could with a
>> De-Oxit type of spray . That usually would do the trick.
>> In a multi card system - do one card at a time :)
>> I hope this helps :)
>>
>> Morgan
>> "Kim" <hiddensounds@hotmail.com> wrote in message news:47800ece$1@linux...
>>>
>>>
>>> Mmm... neither the BIOS Defaults reset or the Standard PC thing seem
to
>>> have fixed it. Same deal.
>>>
>>> Gosh damnit. ;o)
>>>
>>> I'm just going to be really annoyed if I buy a new MB and that's not
it.
>>> I've tried a number of things here, many with some confidence of a
>>> result,
>>> but nuttin' worked. I've got $4500 I plan to spend on car restorations
in
>>> the next 6 weeks. I know a MB is only $70 but I'm runnin' on empty. ;o)
>>>
>>> But what I wouldn't do to get Paris up and running. I'm almost
>>> considering
>>> loading Reaper to get some stuff done... :oS
>>>
>>> Cheers,
>>> Kim.
>>>
>>> "Kim" <hiddensounds@hotmail.com> wrote:
>>>>
>>>>
>>>>So....... ;o)
>>>>
>>>>It occurred to me that I should put more effort into resolving this on
>>>>the
>>>>existing MB. Just after some comments if you have any. Currently Paris
>>>>attempts
>>>>to load, the MEC or 442 starts its "boot" and stops right at that point
>>> where
>>>>the internal sync light and the 48k light come on together. They stay
>>>>that
>>>>way for far too long (compared to "normal") and then the 7/7 error
>>>>appears.
>>>>IIRC that phase is when the MEC is actually attempting to make the audio
>>>>link with the EDS card. Presumably this is when EDS comms are going to
>>>>suddenly
>>>>increase from some minor discussions about the boot process to an actual
>>>>stream of audio data traffic, so I can see that an IRQ issue might cause
>>>>issues at that point.
>>>>
>>>>I'm currently exploring the idea that it's just an IRQ conflict, which
>>>>seems
>>>>possible.
>>>>
>>>>(*) I've noted that my "working" Paris install image is in ACPI mode.
I'm
>>>>just changing to Standard PC to see if we can't sort some stuff out
>>>>because...
>>>>
>>>>(*) I noted that the Scherzo driver was being allocated to IRQ 19 by
>>>>Windows.
>>>>It was on its own, but that's not the real IRQ (which was 5, but I've
>>>>moved
>>>>it to 7), but a virtual Windows one. Why Windows made this crazy
>>>>allocation
>>>>I'm not sure. Hopefully Standard PC mode will put it back on 7.
>>>>
>>>>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the
>>>>crazy
>>>>MB has done something silly here.
>>>>
>>>>In any case, the install image used to work, so this ACPI thingy doesn't
>>>>seem the likely cause. A BIOS reset may do it. Or it still could be a
MB
>>>>hardware fault.
>>>>
>>>>Annoying... ;o)
>>>>
>>>>Cheers,
>>>>Kim.
>>>
>>
>>
>
>
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94387 is a reply to message #94384] |
Sat, 05 January 2008 18:28 |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
Morgan,
Thanks for that. I'll give it a shot. You're not the first to suggest it
(Steve did I think). I'm a little pessimistic about it however as I have
removed both cards, tried just one, then the other, and different slots,
and I would have thought that simply luck of the draw would mean it would
have randomly started at some point if that was the issue. You'd have more
experience on this level than myself though, so I'll put it next on the list.
I do hate pulling the box apart though... :o(
Cheers,
Kim.
"Morgan" <morganp@ntplx.net> wrote:
>Hi Kim,
>I tried to respond to another post on this a while back
>and got a posting error, I hope this one makes it.
>
>We had some rigs that would get into a 7/7 error mode,
>this always means the hardware cannot be seen.
>
>We would use a pencil eraser on the contacts of the EDS
>card and clean out the pci slot the best we could with a
>De-Oxit type of spray . That usually would do the trick.
>In a multi card system - do one card at a time :)
>I hope this helps :)
>
>Morgan
>"Kim" <hiddensounds@hotmail.com> wrote in message news:47800ece$1@linux...
>>
>>
>> Mmm... neither the BIOS Defaults reset or the Standard PC thing seem
to
>> have fixed it. Same deal.
>>
>> Gosh damnit. ;o)
>>
>> I'm just going to be really annoyed if I buy a new MB and that's not it.
>> I've tried a number of things here, many with some confidence of a result,
>> but nuttin' worked. I've got $4500 I plan to spend on car restorations
in
>> the next 6 weeks. I know a MB is only $70 but I'm runnin' on empty. ;o)
>>
>> But what I wouldn't do to get Paris up and running. I'm almost considering
>> loading Reaper to get some stuff done... :oS
>>
>> Cheers,
>> Kim.
>>
>> "Kim" <hiddensounds@hotmail.com> wrote:
>>>
>>>
>>>So....... ;o)
>>>
>>>It occurred to me that I should put more effort into resolving this on
the
>>>existing MB. Just after some comments if you have any. Currently Paris
>>>attempts
>>>to load, the MEC or 442 starts its "boot" and stops right at that point
>> where
>>>the internal sync light and the 48k light come on together. They stay
that
>>>way for far too long (compared to "normal") and then the 7/7 error
>>>appears.
>>>IIRC that phase is when the MEC is actually attempting to make the audio
>>>link with the EDS card. Presumably this is when EDS comms are going to
>>>suddenly
>>>increase from some minor discussions about the boot process to an actual
>>>stream of audio data traffic, so I can see that an IRQ issue might cause
>>>issues at that point.
>>>
>>>I'm currently exploring the idea that it's just an IRQ conflict, which
>>>seems
>>>possible.
>>>
>>>(*) I've noted that my "working" Paris install image is in ACPI mode.
I'm
>>>just changing to Standard PC to see if we can't sort some stuff out
>>>because...
>>>
>>>(*) I noted that the Scherzo driver was being allocated to IRQ 19 by
>>>Windows.
>>>It was on its own, but that's not the real IRQ (which was 5, but I've
>>>moved
>>>it to 7), but a virtual Windows one. Why Windows made this crazy
>>>allocation
>>>I'm not sure. Hopefully Standard PC mode will put it back on 7.
>>>
>>>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the
>>>crazy
>>>MB has done something silly here.
>>>
>>>In any case, the install image used to work, so this ACPI thingy doesn't
>>>seem the likely cause. A BIOS reset may do it. Or it still could be a
MB
>>>hardware fault.
>>>
>>>Annoying... ;o)
>>>
>>>Cheers,
>>>Kim.
>>
>
>
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94388 is a reply to message #94387] |
Sat, 05 January 2008 19:01 |
Neil
Messages: 1645
Registered: April 2006
|
Senior Member |
|
|
Kimmers, i think you're gonna have to yank the machine apart
no matter what... IIRC, that error 7/7 is indeed an EDS-card-
related thing, and it COULD be just the connection/connectors.
Best to yank it apart & rule out a bad EDS card by cleaning
the connectors & see if that works.
Neil
"Kim" <hiddensounds@hotmail.com> wrote:
>
>
>Morgan,
>
>Thanks for that. I'll give it a shot. You're not the first to suggest it
>(Steve did I think). I'm a little pessimistic about it however as I have
>removed both cards, tried just one, then the other, and different slots,
>and I would have thought that simply luck of the draw would mean it would
>have randomly started at some point if that was the issue. You'd have more
>experience on this level than myself though, so I'll put it next on the
list.
>
>I do hate pulling the box apart though... :o(
>
>Cheers,
>Kim.
>
>"Morgan" <morganp@ntplx.net> wrote:
>>Hi Kim,
>>I tried to respond to another post on this a while back
>>and got a posting error, I hope this one makes it.
>>
>>We had some rigs that would get into a 7/7 error mode,
>>this always means the hardware cannot be seen.
>>
>>We would use a pencil eraser on the contacts of the EDS
>>card and clean out the pci slot the best we could with a
>>De-Oxit type of spray . That usually would do the trick.
>>In a multi card system - do one card at a time :)
>>I hope this helps :)
>>
>>Morgan
>>"Kim" <hiddensounds@hotmail.com> wrote in message news:47800ece$1@linux...
>>>
>>>
>>> Mmm... neither the BIOS Defaults reset or the Standard PC thing seem
>to
>>> have fixed it. Same deal.
>>>
>>> Gosh damnit. ;o)
>>>
>>> I'm just going to be really annoyed if I buy a new MB and that's not
it.
>>> I've tried a number of things here, many with some confidence of a result,
>>> but nuttin' worked. I've got $4500 I plan to spend on car restorations
>in
>>> the next 6 weeks. I know a MB is only $70 but I'm runnin' on empty. ;o)
>>>
>>> But what I wouldn't do to get Paris up and running. I'm almost considering
>>> loading Reaper to get some stuff done... :oS
>>>
>>> Cheers,
>>> Kim.
>>>
>>> "Kim" <hiddensounds@hotmail.com> wrote:
>>>>
>>>>
>>>>So....... ;o)
>>>>
>>>>It occurred to me that I should put more effort into resolving this on
>the
>>>>existing MB. Just after some comments if you have any. Currently Paris
>
>>>>attempts
>>>>to load, the MEC or 442 starts its "boot" and stops right at that point
>>> where
>>>>the internal sync light and the 48k light come on together. They stay
>that
>>>>way for far too long (compared to "normal") and then the 7/7 error
>>>>appears.
>>>>IIRC that phase is when the MEC is actually attempting to make the audio
>>>>link with the EDS card. Presumably this is when EDS comms are going to
>
>>>>suddenly
>>>>increase from some minor discussions about the boot process to an actual
>>>>stream of audio data traffic, so I can see that an IRQ issue might cause
>>>>issues at that point.
>>>>
>>>>I'm currently exploring the idea that it's just an IRQ conflict, which
>
>>>>seems
>>>>possible.
>>>>
>>>>(*) I've noted that my "working" Paris install image is in ACPI mode.
>I'm
>>>>just changing to Standard PC to see if we can't sort some stuff out
>>>>because...
>>>>
>>>>(*) I noted that the Scherzo driver was being allocated to IRQ 19 by
>>>>Windows.
>>>>It was on its own, but that's not the real IRQ (which was 5, but I've
>
>>>>moved
>>>>it to 7), but a virtual Windows one. Why Windows made this crazy
>>>>allocation
>>>>I'm not sure. Hopefully Standard PC mode will put it back on 7.
>>>>
>>>>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the
>
>>>>crazy
>>>>MB has done something silly here.
>>>>
>>>>In any case, the install image used to work, so this ACPI thingy doesn't
>>>>seem the likely cause. A BIOS reset may do it. Or it still could be a
>MB
>>>>hardware fault.
>>>>
>>>>Annoying... ;o)
>>>>
>>>>Cheers,
>>>>Kim.
>>>
>>
>>
>
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94392 is a reply to message #94388] |
Sat, 05 January 2008 20:53 |
tonehouse
Messages: 184
Registered: July 2006
|
Senior Member |
|
|
That's what I did, and it fixed my problem.....although it did not say "7/7"
it said "Paris engine not responding".
"Neil" <OIUIU@OI.com> wrote in message news:4780366a$1@linux...
>
> Kimmers, i think you're gonna have to yank the machine apart
> no matter what... IIRC, that error 7/7 is indeed an EDS-card-
> related thing, and it COULD be just the connection/connectors.
>
> Best to yank it apart & rule out a bad EDS card by cleaning
> the connectors & see if that works.
>
> Neil
>
>
> "Kim" <hiddensounds@hotmail.com> wrote:
> >
> >
> >Morgan,
> >
> >Thanks for that. I'll give it a shot. You're not the first to suggest it
> >(Steve did I think). I'm a little pessimistic about it however as I have
> >removed both cards, tried just one, then the other, and different slots,
> >and I would have thought that simply luck of the draw would mean it would
> >have randomly started at some point if that was the issue. You'd have
more
> >experience on this level than myself though, so I'll put it next on the
> list.
> >
> >I do hate pulling the box apart though... :o(
> >
> >Cheers,
> >Kim.
> >
> >"Morgan" <morganp@ntplx.net> wrote:
> >>Hi Kim,
> >>I tried to respond to another post on this a while back
> >>and got a posting error, I hope this one makes it.
> >>
> >>We had some rigs that would get into a 7/7 error mode,
> >>this always means the hardware cannot be seen.
> >>
> >>We would use a pencil eraser on the contacts of the EDS
> >>card and clean out the pci slot the best we could with a
> >>De-Oxit type of spray . That usually would do the trick.
> >>In a multi card system - do one card at a time :)
> >>I hope this helps :)
> >>
> >>Morgan
> >>"Kim" <hiddensounds@hotmail.com> wrote in message
news:47800ece$1@linux...
> >>>
> >>>
> >>> Mmm... neither the BIOS Defaults reset or the Standard PC thing seem
> >to
> >>> have fixed it. Same deal.
> >>>
> >>> Gosh damnit. ;o)
> >>>
> >>> I'm just going to be really annoyed if I buy a new MB and that's not
> it.
> >>> I've tried a number of things here, many with some confidence of a
result,
> >>> but nuttin' worked. I've got $4500 I plan to spend on car restorations
> >in
> >>> the next 6 weeks. I know a MB is only $70 but I'm runnin' on empty.
;o)
> >>>
> >>> But what I wouldn't do to get Paris up and running. I'm almost
considering
> >>> loading Reaper to get some stuff done... :oS
> >>>
> >>> Cheers,
> >>> Kim.
> >>>
> >>> "Kim" <hiddensounds@hotmail.com> wrote:
> >>>>
> >>>>
> >>>>So....... ;o)
> >>>>
> >>>>It occurred to me that I should put more effort into resolving this on
> >the
> >>>>existing MB. Just after some comments if you have any. Currently Paris
> >
> >>>>attempts
> >>>>to load, the MEC or 442 starts its "boot" and stops right at that
point
> >>> where
> >>>>the internal sync light and the 48k light come on together. They stay
> >that
> >>>>way for far too long (compared to "normal") and then the 7/7 error
> >>>>appears.
> >>>>IIRC that phase is when the MEC is actually attempting to make the
audio
> >>>>link with the EDS card. Presumably this is when EDS comms are going to
> >
> >>>>suddenly
> >>>>increase from some minor discussions about the boot process to an
actual
> >>>>stream of audio data traffic, so I can see that an IRQ issue might
cause
> >>>>issues at that point.
> >>>>
> >>>>I'm currently exploring the idea that it's just an IRQ conflict, which
> >
> >>>>seems
> >>>>possible.
> >>>>
> >>>>(*) I've noted that my "working" Paris install image is in ACPI mode.
> >I'm
> >>>>just changing to Standard PC to see if we can't sort some stuff out
> >>>>because...
> >>>>
> >>>>(*) I noted that the Scherzo driver was being allocated to IRQ 19 by
>
> >>>>Windows.
> >>>>It was on its own, but that's not the real IRQ (which was 5, but I've
> >
> >>>>moved
> >>>>it to 7), but a virtual Windows one. Why Windows made this crazy
> >>>>allocation
> >>>>I'm not sure. Hopefully Standard PC mode will put it back on 7.
> >>>>
> >>>>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the
> >
> >>>>crazy
> >>>>MB has done something silly here.
> >>>>
> >>>>In any case, the install image used to work, so this ACPI thingy
doesn't
> >>>>seem the likely cause. A BIOS reset may do it. Or it still could be a
> >MB
> >>>>hardware fault.
> >>>>
> >>>>Annoying... ;o)
> >>>>
> >>>>Cheers,
> >>>>Kim.
> >>>
> >>
> >>
> >
>
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94397 is a reply to message #94380] |
Sun, 06 January 2008 07:58 |
mike audet[3]
Messages: 88
Registered: June 2008
|
Member |
|
|
Hi Kim,
I did more reading on IRQs as part of my research for working on the PARIS
driver.
IRQ 19 is the real IRQ. The cards are given a slot number and an irq letter
by the bios and then the IRQ handler/device assigns an irq. Modern computers
can assign 24 or more "real" unshared IRQs that map directly to the slot/letter
combination of the card.
Eben if they are shared, it shouldn't be a problem. Sharing support is required
in all PCI drivers, and it is literally 2 or three lines of code. It would
be very unusual if a card's driver didn't support sharing these days.
Have you tried deleting any default project that you have? I apologize if
that was suggested/tried before.
Good luck!!
Mike
"Kim" <hiddensounds@hotmail.com> wrote:
>
>
>So....... ;o)
>
>It occurred to me that I should put more effort into resolving this on the
>existing MB. Just after some comments if you have any. Currently Paris attempts
>to load, the MEC or 442 starts its "boot" and stops right at that point
where
>the internal sync light and the 48k light come on together. They stay that
>way for far too long (compared to "normal") and then the 7/7 error appears.
>IIRC that phase is when the MEC is actually attempting to make the audio
>link with the EDS card. Presumably this is when EDS comms are going to suddenly
>increase from some minor discussions about the boot process to an actual
>stream of audio data traffic, so I can see that an IRQ issue might cause
>issues at that point.
>
>I'm currently exploring the idea that it's just an IRQ conflict, which seems
>possible.
>
>(*) I've noted that my "working" Paris install image is in ACPI mode. I'm
>just changing to Standard PC to see if we can't sort some stuff out because...
>
>(*) I noted that the Scherzo driver was being allocated to IRQ 19 by Windows.
>It was on its own, but that's not the real IRQ (which was 5, but I've moved
>it to 7), but a virtual Windows one. Why Windows made this crazy allocation
>I'm not sure. Hopefully Standard PC mode will put it back on 7.
>
>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the crazy
>MB has done something silly here.
>
>In any case, the install image used to work, so this ACPI thingy doesn't
>seem the likely cause. A BIOS reset may do it. Or it still could be a MB
>hardware fault.
>
>Annoying... ;o)
>
>Cheers,
>Kim.
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94467 is a reply to message #94392] |
Mon, 07 January 2008 21:21 |
Deej
Messages: 130
Registered: September 2006
|
Senior Member |
|
|
Neil and Tonehouse are right. Sometimes a connouter valve will spontaneously
crossthread some of the PVC fittings that are wired to the flush handle and
when that happens, you can sometimes try to fumigate the blowhole sprocket
with a steam iron, but usually it's quicker to just reseat the PCI cards.
;o)
"tonehouse" <zmcleod@comcast.net> wrote in message news:47805cb8$1@linux...
> That's what I did, and it fixed my problem.....although it did not say
> "7/7"
> it said "Paris engine not responding".
> "Neil" <OIUIU@OI.com> wrote in message news:4780366a$1@linux...
>>
>> Kimmers, i think you're gonna have to yank the machine apart
>> no matter what... IIRC, that error 7/7 is indeed an EDS-card-
>> related thing, and it COULD be just the connection/connectors.
>>
>> Best to yank it apart & rule out a bad EDS card by cleaning
>> the connectors & see if that works.
>>
>> Neil
>>
>>
>> "Kim" <hiddensounds@hotmail.com> wrote:
>> >
>> >
>> >Morgan,
>> >
>> >Thanks for that. I'll give it a shot. You're not the first to suggest it
>> >(Steve did I think). I'm a little pessimistic about it however as I have
>> >removed both cards, tried just one, then the other, and different slots,
>> >and I would have thought that simply luck of the draw would mean it
>> >would
>> >have randomly started at some point if that was the issue. You'd have
> more
>> >experience on this level than myself though, so I'll put it next on the
>> list.
>> >
>> >I do hate pulling the box apart though... :o(
>> >
>> >Cheers,
>> >Kim.
>> >
>> >"Morgan" <morganp@ntplx.net> wrote:
>> >>Hi Kim,
>> >>I tried to respond to another post on this a while back
>> >>and got a posting error, I hope this one makes it.
>> >>
>> >>We had some rigs that would get into a 7/7 error mode,
>> >>this always means the hardware cannot be seen.
>> >>
>> >>We would use a pencil eraser on the contacts of the EDS
>> >>card and clean out the pci slot the best we could with a
>> >>De-Oxit type of spray . That usually would do the trick.
>> >>In a multi card system - do one card at a time :)
>> >>I hope this helps :)
>> >>
>> >>Morgan
>> >>"Kim" <hiddensounds@hotmail.com> wrote in message
> news:47800ece$1@linux...
>> >>>
>> >>>
>> >>> Mmm... neither the BIOS Defaults reset or the Standard PC thing seem
>> >to
>> >>> have fixed it. Same deal.
>> >>>
>> >>> Gosh damnit. ;o)
>> >>>
>> >>> I'm just going to be really annoyed if I buy a new MB and that's not
>> it.
>> >>> I've tried a number of things here, many with some confidence of a
> result,
>> >>> but nuttin' worked. I've got $4500 I plan to spend on car
>> >>> restorations
>> >in
>> >>> the next 6 weeks. I know a MB is only $70 but I'm runnin' on empty.
> ;o)
>> >>>
>> >>> But what I wouldn't do to get Paris up and running. I'm almost
> considering
>> >>> loading Reaper to get some stuff done... :oS
>> >>>
>> >>> Cheers,
>> >>> Kim.
>> >>>
>> >>> "Kim" <hiddensounds@hotmail.com> wrote:
>> >>>>
>> >>>>
>> >>>>So....... ;o)
>> >>>>
>> >>>>It occurred to me that I should put more effort into resolving this
>> >>>>on
>> >the
>> >>>>existing MB. Just after some comments if you have any. Currently
>> >>>>Paris
>> >
>> >>>>attempts
>> >>>>to load, the MEC or 442 starts its "boot" and stops right at that
> point
>> >>> where
>> >>>>the internal sync light and the 48k light come on together. They stay
>> >that
>> >>>>way for far too long (compared to "normal") and then the 7/7 error
>> >>>>appears.
>> >>>>IIRC that phase is when the MEC is actually attempting to make the
> audio
>> >>>>link with the EDS card. Presumably this is when EDS comms are going
>> >>>>to
>> >
>> >>>>suddenly
>> >>>>increase from some minor discussions about the boot process to an
> actual
>> >>>>stream of audio data traffic, so I can see that an IRQ issue might
> cause
>> >>>>issues at that point.
>> >>>>
>> >>>>I'm currently exploring the idea that it's just an IRQ conflict,
>> >>>>which
>> >
>> >>>>seems
>> >>>>possible.
>> >>>>
>> >>>>(*) I've noted that my "working" Paris install image is in ACPI mode.
>> >I'm
>> >>>>just changing to Standard PC to see if we can't sort some stuff out
>> >>>>because...
>> >>>>
>> >>>>(*) I noted that the Scherzo driver was being allocated to IRQ 19 by
>>
>> >>>>Windows.
>> >>>>It was on its own, but that's not the real IRQ (which was 5, but I've
>> >
>> >>>>moved
>> >>>>it to 7), but a virtual Windows one. Why Windows made this crazy
>> >>>>allocation
>> >>>>I'm not sure. Hopefully Standard PC mode will put it back on 7.
>> >>>>
>> >>>>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case the
>> >
>> >>>>crazy
>> >>>>MB has done something silly here.
>> >>>>
>> >>>>In any case, the install image used to work, so this ACPI thingy
> doesn't
>> >>>>seem the likely cause. A BIOS reset may do it. Or it still could be a
>> >MB
>> >>>>hardware fault.
>> >>>>
>> >>>>Annoying... ;o)
>> >>>>
>> >>>>Cheers,
>> >>>>Kim.
>> >>>
>> >>
>> >>
>> >
>>
>
>
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94470 is a reply to message #94467] |
Tue, 08 January 2008 02:23 |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
Deej,
Nobody but other smartasses likes a smartass.
;o)
"Deej" <noway@jose.org> wrote:
>Neil and Tonehouse are right. Sometimes a connouter valve will spontaneously
>crossthread some of the PVC fittings that are wired to the flush handle
and
>when that happens, you can sometimes try to fumigate the blowhole sprocket
>with a steam iron, but usually it's quicker to just reseat the PCI cards.
>
>;o)
>
>"tonehouse" <zmcleod@comcast.net> wrote in message news:47805cb8$1@linux...
>> That's what I did, and it fixed my problem.....although it did not say
>> "7/7"
>> it said "Paris engine not responding".
>> "Neil" <OIUIU@OI.com> wrote in message news:4780366a$1@linux...
>>>
>>> Kimmers, i think you're gonna have to yank the machine apart
>>> no matter what... IIRC, that error 7/7 is indeed an EDS-card-
>>> related thing, and it COULD be just the connection/connectors.
>>>
>>> Best to yank it apart & rule out a bad EDS card by cleaning
>>> the connectors & see if that works.
>>>
>>> Neil
>>>
>>>
>>> "Kim" <hiddensounds@hotmail.com> wrote:
>>> >
>>> >
>>> >Morgan,
>>> >
>>> >Thanks for that. I'll give it a shot. You're not the first to suggest
it
>>> >(Steve did I think). I'm a little pessimistic about it however as I
have
>>> >removed both cards, tried just one, then the other, and different slots,
>>> >and I would have thought that simply luck of the draw would mean it
>>> >would
>>> >have randomly started at some point if that was the issue. You'd have
>> more
>>> >experience on this level than myself though, so I'll put it next on
the
>>> list.
>>> >
>>> >I do hate pulling the box apart though... :o(
>>> >
>>> >Cheers,
>>> >Kim.
>>> >
>>> >"Morgan" <morganp@ntplx.net> wrote:
>>> >>Hi Kim,
>>> >>I tried to respond to another post on this a while back
>>> >>and got a posting error, I hope this one makes it.
>>> >>
>>> >>We had some rigs that would get into a 7/7 error mode,
>>> >>this always means the hardware cannot be seen.
>>> >>
>>> >>We would use a pencil eraser on the contacts of the EDS
>>> >>card and clean out the pci slot the best we could with a
>>> >>De-Oxit type of spray . That usually would do the trick.
>>> >>In a multi card system - do one card at a time :)
>>> >>I hope this helps :)
>>> >>
>>> >>Morgan
>>> >>"Kim" <hiddensounds@hotmail.com> wrote in message
>> news:47800ece$1@linux...
>>> >>>
>>> >>>
>>> >>> Mmm... neither the BIOS Defaults reset or the Standard PC thing
seem
>>> >to
>>> >>> have fixed it. Same deal.
>>> >>>
>>> >>> Gosh damnit. ;o)
>>> >>>
>>> >>> I'm just going to be really annoyed if I buy a new MB and that's
not
>>> it.
>>> >>> I've tried a number of things here, many with some confidence of
a
>> result,
>>> >>> but nuttin' worked. I've got $4500 I plan to spend on car
>>> >>> restorations
>>> >in
>>> >>> the next 6 weeks. I know a MB is only $70 but I'm runnin' on empty.
>> ;o)
>>> >>>
>>> >>> But what I wouldn't do to get Paris up and running. I'm almost
>> considering
>>> >>> loading Reaper to get some stuff done... :oS
>>> >>>
>>> >>> Cheers,
>>> >>> Kim.
>>> >>>
>>> >>> "Kim" <hiddensounds@hotmail.com> wrote:
>>> >>>>
>>> >>>>
>>> >>>>So....... ;o)
>>> >>>>
>>> >>>>It occurred to me that I should put more effort into resolving this
>>> >>>>on
>>> >the
>>> >>>>existing MB. Just after some comments if you have any. Currently
>>> >>>>Paris
>>> >
>>> >>>>attempts
>>> >>>>to load, the MEC or 442 starts its "boot" and stops right at that
>> point
>>> >>> where
>>> >>>>the internal sync light and the 48k light come on together. They
stay
>>> >that
>>> >>>>way for far too long (compared to "normal") and then the 7/7 error
>>> >>>>appears.
>>> >>>>IIRC that phase is when the MEC is actually attempting to make the
>> audio
>>> >>>>link with the EDS card. Presumably this is when EDS comms are going
>>> >>>>to
>>> >
>>> >>>>suddenly
>>> >>>>increase from some minor discussions about the boot process to an
>> actual
>>> >>>>stream of audio data traffic, so I can see that an IRQ issue might
>> cause
>>> >>>>issues at that point.
>>> >>>>
>>> >>>>I'm currently exploring the idea that it's just an IRQ conflict,
>>> >>>>which
>>> >
>>> >>>>seems
>>> >>>>possible.
>>> >>>>
>>> >>>>(*) I've noted that my "working" Paris install image is in ACPI mode.
>>> >I'm
>>> >>>>just changing to Standard PC to see if we can't sort some stuff out
>>> >>>>because...
>>> >>>>
>>> >>>>(*) I noted that the Scherzo driver was being allocated to IRQ 19
by
>>>
>>> >>>>Windows.
>>> >>>>It was on its own, but that's not the real IRQ (which was 5, but
I've
>>> >
>>> >>>>moved
>>> >>>>it to 7), but a virtual Windows one. Why Windows made this crazy
>>> >>>>allocation
>>> >>>>I'm not sure. Hopefully Standard PC mode will put it back on 7.
>>> >>>>
>>> >>>>(*) I'm thinking of doing a BIOS reset, or indeed reload, in case
the
>>> >
>>> >>>>crazy
>>> >>>>MB has done something silly here.
>>> >>>>
>>> >>>>In any case, the install image used to work, so this ACPI thingy
>> doesn't
>>> >>>>seem the likely cause. A BIOS reset may do it. Or it still could
be a
>>> >MB
>>> >>>>hardware fault.
>>> >>>>
>>> >>>>Annoying... ;o)
>>> >>>>
>>> >>>>Cheers,
>>> >>>>Kim.
>>> >>>
>>> >>
>>> >>
>>> >
>>>
>>
>>
>
>
|
|
|
|
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94525 is a reply to message #94516] |
Wed, 09 January 2008 12:59 |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
Not Skype as such, but I have a VOIP router and hence can call O.S. generally
for under $2 an hour, which isn't going to break the bank.
Shoot me an email perhaps with your number, however I probably should, at
least, do some actual cleaning of the contacts on the EDS as everyone seems
to have unanimously suggested. I have two things on my todo list before I
panic. ;o)
1) Clean the EDS contacts and
2) I think that one particular PCI slot has been involved in every test,
so I want to try at least one EDS in a different slot.
The EDS contacts don't look dirty, which is why I haven't given them a good
clean. I did look. Also, I would think that of TWO EDS cards, after being
reseated, it seams unlikely that neither would work even intermittantly.
Could be wrong. If I'm going to ask advice though I'd best follow it. ;o)
But from my end the plausable idea that one of the PCI slots has been involved
in every test seems very much to be a possible cause.
Cheers,
Kim.
"Mike Audet" <mike@...> wrote:
>
>Hi Kim,
>
>Are you on skype? Maybe we could chat about this and see if we can come
>up with something.
>
>Hope to talk to you soon,
>
>Mike
>
>
>"Deej" <noway@jose.org> wrote:
>>
>>"Kim" <hiddensounds@Hotmail.com> wrote in message news:4783412b$1@linux...
>>>
>>>
>>> Deej,
>>>
>>> Nobody but other smartasses likes a smartass.
>>>
>>> ;o)
>>>
>>
>>Sheesh!!!.what an ingrate!!!! See if I come to the rescue the next time
>the
>>silicon in the transdermal metering guages starts to bubble and send off
>
>>fumes and you're wondering why a bunch of pasty faced reptilian'esque
>>humanoids come slithering around with glass pipes topped with aluminum
foil
>
>>wanting to smoke the stuff. No more tech support calls for you dude.
>>
>>;o)
>>
>>
>
|
|
|
|
| Re: My Error 7/7 dilemma continued... [message #94526 is a reply to message #94513] |
Wed, 09 January 2008 13:03 |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
"Deej" <noway@jose.org> wrote:
>Sheesh!!!.what an ingrate!!!! See if I come to the rescue the next time
the
>silicon in the transdermal metering guages starts to bubble and send off
>fumes and you're wondering why a bunch of pasty faced reptilian'esque
>humanoids come slithering around with glass pipes topped with aluminum foil
>wanting to smoke the stuff. No more tech support calls for you dude.
>
>;o)
Right! That's it! I'm blocking your IP! EVERYBODY knows lizards only smoke
from wooden pipes!
Yee dawgies.
;o)
|
|
|
|
Goto Forum:
Current Time: Sat Nov 09 00:42:45 PST 2024
Total time taken to generate the page: 0.02989 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
