Revision history for WinXpAdat
Additions:
//{{color text="IMPORTANT NOTE JAN 1 2010" c="red"}}: [[MikeAudet Mike Audet's]] [[http://www.ensoniq.ca/drivers.html Multicore Drivers]] solve this problem. Mike (and in fact Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course the aging PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up; during bootup the software would essentially say "any ADAT cards there?" but lose interest and run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it. The "highest numbered slots" solution referenced below has to do with the order in which the software asks for the cards to "sign in", so this solution might still be of use to those who haven't bought Mike's drivers.//
Deletions:
Additions:
//{{color text="IMPORTANT NOTE JAN 1 2010" c="red"}}: [[MikeAudet Mike Audet's]] [[http://www.ensoniq.ca/drivers.html Multicore Drivers]] solve this problem. Mike (and in fact Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course the aging PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up; the software would essentially say "any ADAT cards there?" but lose interest and run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it. The "highest numbered slots" solution referenced below has to do with the order in which the software asks for the cards to "sign in", so this solution might still be of use to those who haven't bought Mike's drivers.//
Deletions:
Additions:
//{{color text="IMPORTANT NOTE JAN 1 2010" c="red"}}: [[MikeAudet Mike Audet's]] [[http://www.ensoniq.ca/drivers.html Multicore Drivers]] solve this problem. Mike (and in fact Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course the aging PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up. The software would essentially say "any ADAT cards there?" but run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it. The "highest numbered slots" solution referenced below has to do with the order in which the software asks for the cards to "sign in", so this solution might still be of use to those who haven't bought Mike's drivers.//
Deletions:
Additions:
//{{color text="IMPORTANT NOTE JAN 1 2010" c="red"}}: [[MikeAudet Mike Audet's]] [[http://www.ensoniq.ca/drivers.html Multicore Drivers]] solve this problem. Mike (and in fact Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course the PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up. The software would essentially say "any ADAT cards there?" but run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it. The "highest numbered slots" solution referenced below has to do with the order in which the software asks for the cards to "sign in", so this solution might still be of use to those who haven't bought Mike's drivers.//
Deletions:
Additions:
//{{color text="IMPORTANT NOTE JAN 1 2010" c="red"}}: [[MikeAudet Mike Audet's]] [[http://www.ensoniq.ca/drivers.html Multicore Drivers]] solve this problem. Mike (and in fact Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course the PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up. The software would essentially say "any ADAT cards there?" but run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it. The "highest number slots" solution has to do with the order in which the software asks for the cards to "sign in", so this solution might still be of use to those who haven't bought Mike's drivers.//
Deletions:
Additions:
//{{color text="IMPORTANT NOTE JAN 1 2010" c="red"}}: [[MikeAudet Mike Audet's]] [[http://www.ensoniq.ca/drivers.html Multicore Drivers]] solve this problem. Mike (and in fact Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course the PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up. The software would essentially say "any ADAT cards there?" but run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it.//
Deletions:
Additions:
//{{color text="IMPORTANT NOTE JAN 1 2010" c="red"}}: [[MikeAudet Mike Audet's]] [[http://www.ensoniq.ca/drivers.html Multicore Drivers]] solve this problem. Mike (and in fact Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course - the PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up. The software would essentially say "any ADAT cards there?" but run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it.//
Deletions:
Additions:
//{{color text="IMPORTANT NOTE JULY 31 2008" c="red"}}: Mike Audet's Multicore Drivers solve this problem. Mike (and in fact Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course - the PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up. The software would essentially say "any ADAT cards there?" but run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it.//
Deletions:
//So - what was this bug all about, and why do Mike's drivers fix it? Mike (and actually Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course - the PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up. The software would essentially say "any ADAT cards there?" but run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it.//
Additions:
//So - what was this bug all about, and why do Mike's drivers fix it? Mike (and actually Chris Thoman before him too) discovered that the faster computers became, the more they sped up the execution of the PARIS software code running on your computer. Of course - the PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up. The software would essentially say "any ADAT cards there?" but run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it.//
Deletions:
Additions:
//So - what was this bug all about, and why do Mike's drivers fix it? Mike discovered that the faster computers became, the more it sped up the execution of the PARIS software code running on your computer - but of course the PARIS hardware wasn't speeding up to match. After a certain point, the PARIS hardware simply couldn't keep up. The software would essentially say "any ADAT cards there?" but run off to other tasks before the cards could respond. Mike's judicious tweaking of the "time windows" fixed it.//
Additions:
//{{color text="IMPORTANT NOTE JULY 31 2008: Mike Audet is debugging the ADAT dll as we speak - check the PARIS NG for updates and a beta dll to try! It will be linked here ASAP. With any luck, *all* of these issues may be a thing of the past." c="red"}}//
Additions:
Back to [[BugsTroubleshooting Bugs and Troubleshooting]]
Additions:
=====Workaround for Multiple ADAT Card Bug under WinXP=====
Deletions:
Additions:
----
//>I seem to remember that some of you using XP had no problems with ADAT
----
----
Just because it's the way I preferred my physical layout from day one, ''my ADAT cards have always been in the highest numbered slots. In every MEC, my card sequence, from low to high slot number is:
----
at the end of the MEC - the higher numbered slots.''//
//>I seem to remember that some of you using XP had no problems with ADAT
----
----
Just because it's the way I preferred my physical layout from day one, ''my ADAT cards have always been in the highest numbered slots. In every MEC, my card sequence, from low to high slot number is:
----
at the end of the MEC - the higher numbered slots.''//
Deletions:
//--------------------------
//Just because it's the way I preferred my physical layout from day one, ''my ADAT cards have always been in the highest numbered slots. In every MEC, my card sequence, from low to high slot number is:
at the end of the MEC - the higher numbered slots.''
From: Brian T <gbtmusic@comcast.net>
//
Additions:
=====Multiple ADAT Card Bug under WinXP=====
Deletions:
news:47eea09d@linux...
