Win XP Service Pack 2
Someone said earlier that it rearranges all the IRQs.......check your system page: may have to do a fresh install of Scope drivers - or have you tried that already ?
BTW, just been using your Bass Amp - one of the best plugins for Scope - fantastic on Bass & Guitars.....thanks again for your great work
<font size=-1>[ This Message was edited by: Plato on 2004-09-14 20:09 ]</font>
BTW, just been using your Bass Amp - one of the best plugins for Scope - fantastic on Bass & Guitars.....thanks again for your great work

<font size=-1>[ This Message was edited by: Plato on 2004-09-14 20:09 ]</font>
-
- Posts: 162
- Joined: Sat Jul 31, 2004 4:00 pm
- Location: England
I heard a rumour that a certain SP2 security feature can block certain drivers...
If it is what I suspect it may be (I am just guessing anyways) goto this link for more information and a suggestion for a temporary fix (only do this if the drivers are still not working after a SCOPE 4 re-install)
http://support.divx.com/cgi-bin/divx.cf ... MQ**&p_li=
If it is what I suspect it may be (I am just guessing anyways) goto this link for more information and a suggestion for a temporary fix (only do this if the drivers are still not working after a SCOPE 4 re-install)
http://support.divx.com/cgi-bin/divx.cf ... MQ**&p_li=
In fact, after many attempts to reinstall the driver, I was able to see it, and Scope lauches correctly, but it can't work because of a lack of clock !!! The sample rate window (44.1/48k in settings) is totally empty, and therefore no sounds are produced.
Also, the red Led sync indicators stay black
Bad news?
Also, the red Led sync indicators stay black
Bad news?
Any chance this could be relevant?
It's from the Cakewalk forum:
Here is some information on the use of SONAR 3 (or earlier versions) with XP SP 2.
SP2 adds a security feature called Data execution prevention (DEP) aka "NX memory" (NX = no execute). The idea is that viruses often enter a computer by coming in via a data buffer, and then injecting code into the data buffer and running that code. SP2 locks that down by only allowing true code pages to be run.
On later model AMD chips (the AMD 64 in particular), NX has hardware support. The chip itself will trigger an exception if a virus tries to run in data memory.
SONAR 3's (and earlier generations) mix engine uses self-generating/modifying code, which is equivalent to code running in data memory. After installing SP2, running SONAR may cause XP to warn about a Windows security problem.
To prevent XP stopping SONAR, go to the system control panel and find the tab where DEP is configured. In there you are allowed to specify applications for which NX can be shut off. If you are using SONAR 3 you will need to add SONARPDR.EXE or SONARSTD.EXE to the list. Choose the appropriate name for the executable file.
You may also configure this via the warning dialog box that XP displays when a it detects DEP. Click Advanced in that dialog to get to the DEP configuration and set it as described above. For more detailed instructions, click the link below and scroll to the bottom of the page.
For more information on the DEP feature in XP SP2 refer to the following Microsoft link:
Detailed description of the data execution prevention feature in Windows XP SP2
R
It's from the Cakewalk forum:
Here is some information on the use of SONAR 3 (or earlier versions) with XP SP 2.
SP2 adds a security feature called Data execution prevention (DEP) aka "NX memory" (NX = no execute). The idea is that viruses often enter a computer by coming in via a data buffer, and then injecting code into the data buffer and running that code. SP2 locks that down by only allowing true code pages to be run.
On later model AMD chips (the AMD 64 in particular), NX has hardware support. The chip itself will trigger an exception if a virus tries to run in data memory.
SONAR 3's (and earlier generations) mix engine uses self-generating/modifying code, which is equivalent to code running in data memory. After installing SP2, running SONAR may cause XP to warn about a Windows security problem.
To prevent XP stopping SONAR, go to the system control panel and find the tab where DEP is configured. In there you are allowed to specify applications for which NX can be shut off. If you are using SONAR 3 you will need to add SONARPDR.EXE or SONARSTD.EXE to the list. Choose the appropriate name for the executable file.
You may also configure this via the warning dialog box that XP displays when a it detects DEP. Click Advanced in that dialog to get to the DEP configuration and set it as described above. For more detailed instructions, click the link below and scroll to the bottom of the page.
For more information on the DEP feature in XP SP2 refer to the following Microsoft link:
Detailed description of the data execution prevention feature in Windows XP SP2
R
I've had Service Pack 2 installed for a while. But today, my plugins won't run. Just my plugin packs and store-bought synths, the rest works. This has happened before, and been fixed by Ralf.
But this time, I haven't used the "my page", no new CW files are involved. XP's Restore System function won't restore, gives me the "Restore Incomplete" page every time. It used to work. I found the DEP tab, then found this thread on Z. hmmm.
But this time, I haven't used the "my page", no new CW files are involved. XP's Restore System function won't restore, gives me the "Restore Incomplete" page every time. It used to work. I found the DEP tab, then found this thread on Z. hmmm.
I'm not going to install SP2 yet, cause my experience in using ms patches is rather bitter - after installing ANY patch on DAW sfp starts to fall off running state...
Also i've noticed that ms server 2003 runs multimedia (after some tunuing, of course) much more stable and patches have same effect
My solution - no internet @DAW, no patches and no problems
Also i've noticed that ms server 2003 runs multimedia (after some tunuing, of course) much more stable and patches have same effect

My solution - no internet @DAW, no patches and no problems

My solution - a mac as DAW with all regular M$ programs working (internet, office, players), if necessory during mixdown, no patchesOn 2004-09-19 08:13, Vasfed wrote:
My solution - no internet @DAW, no patches and no problems![]()
and no problems

<font size=-1>[ This Message was edited by: hubird on 2004-09-19 08:45 ]</font>
Most of the soft that SP2 "broke" (meaning the broken code that the software worked around has now been fixed or changed) were office and productivity apps, predominantly Microsoft progs ironically.
MS Office 2003 or Photoshop may give you some trouble but I don't think most of our multimedia stuff has been hit much. I haven't found a single app that I use that has given me any trouble.
But by all means, be cautious.
sAm
MS Office 2003 or Photoshop may give you some trouble but I don't think most of our multimedia stuff has been hit much. I haven't found a single app that I use that has given me any trouble.
But by all means, be cautious.
sAm
heh i disagree..sp2 hasn't caused any problems here and I use a ton of multimedia AND graphics apps (and the occasional office app).
Also there seem to be a lot of reports that Sp2 has again improved ACPI support. Also most of the newer OS components have been compiled under later compilers so users of modern cpu's should see some actual performance benefit at the OS level (for instance I no longer have problems doing multiple tasks in a single Explorer.exe shell (copying while continuing to browse etc).
Also there seem to be a lot of reports that Sp2 has again improved ACPI support. Also most of the newer OS components have been compiled under later compilers so users of modern cpu's should see some actual performance benefit at the OS level (for instance I no longer have problems doing multiple tasks in a single Explorer.exe shell (copying while continuing to browse etc).
I had the "Access Denied" on oxe files before getting SP2.
I thought SP2 was causing me some probs, but it's not turning out to be that way.
There is the DEP thing under the performance tab of the device manager, under "advanced". You can list executables there, if you think the DEP is stopping them from running.
I thought SP2 was causing me some probs, but it's not turning out to be that way.
There is the DEP thing under the performance tab of the device manager, under "advanced". You can list executables there, if you think the DEP is stopping them from running.