Home » The PARIS Forums » PARIS: Main » XP tweaks for Paris share findings...
|
|
|
|
|
|
|
|
|
|
|
|
| Re: XP tweaks for Paris share findings... [message #80171 is a reply to message #80167] |
Fri, 16 February 2007 08:47   |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Kim,
Interesting about ram.
What ram was the old and waht is the new ?
I have Kingston value ram 512 sticks 3 pc133 SDRAM.
Here is what I do in registry:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/SessionM anager/MemoryManagement
There you find or if not creat a dword
DisablePagingExecutive and put value data 1
Also for dword LargeSystemCache put also 1
for PagedPoolSize dword put 0xfffffff (4294967295)
for SystemPages dword put 0x000c3000 (798720)
for dword IOPageLockLimit put 0x00040000(262144)
Before doing all these export your registry file to a safe place so you can
recover it in case something will get screwed up...
No big deal though.
Now I don't get that exception until I reload while Paris is opened on a
specific waves project and I reload another waves oriented project without
first closing Paris...
Regards,
Dimitrios
"Kim W." <no@way.com> wrote:
>
>Wow!!
>I was getting that very same message with a comp I was upgrading
>for a friend, just the other day. (He uses paris as well and
>has waves).
>I tried different ram and the problem went away completely.
>This is wierd. It would be interesting to try these tweaks
>with the old ram, and see if it fixes the c000000005 thing.
>Dimitrios, could you be a little more specific how to apply
>these?
>Cheers,
>Kim
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>Exactly Neil.
>>I was getting it almost everytime loading a song with DX waves plugins
loaded...
>>Unhandled exception c0000005 at adress: ......
>>You know the picture...
>>Now I am getting this when I try to reload a project after I have loaded
>>succesfully the first time.
>>I changed for that the disablepagingexecutive(1) and LargeSystemCache(1).
>>The other strings I have put (that moght helped too) are on same registry
>>place where the above are...
>>How did you get around with these unhandled exceptions and when are you
>getting
>>it ?
>>Regards,
>>Dimitrios
>>
>>"Don Nafe" <dnafe@magma.ca> wrote:
>>>Were you getting get an error message stating "C0000005" or something
like
>>
>>>that ?
>>>
>>>and where do I find these two lines on my computer?
>>>
>>> IOPageLockLimit=0x00040000
>>> Pagedpoolsize=0xfffffffS
>>>
>>>Don
>>>
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote in message news:45d55898$1@linux...
>>>>
>>>> Hi,
>>>> I seem to find that some xp tweaks can cause Paris either to run better
>>or
>>>> worse.
>>>> The disablepagingexecutive(1) and LargeSystemCache(1) has helped me
a
>>lot
>>>> with waves plugins sometimes crashing when loading a song containing
>them
>>>> in Paris.
>>>> IOPageLockLimit=0x00040000
>>>> Pagedpoolsize=0xfffffffS
>>>> The above applies if you have some hefty memory like 1GB.
>>>> Any findings that you wanna share here that can make Paris run more
stable
>>>> ?
>>>> Regards,
>>>> Dimitrios
>>>
>>>
>>
>
|
|
|
|
|
|
| Re: XP tweaks for Paris share findings... [message #80176 is a reply to message #80171] |
Fri, 16 February 2007 09:14 |
Kim W
Messages: 165
Registered: July 2006
|
Senior Member |
|
|
Hi, Dimitrios.
Actually, I made a mistake.
I had two distinct problems with this machine. (based on an
asus p4p800s, 2.8ghz p4, single 512 RAM).
First problem was the c5000000 error.
After a reboot, sometimes I could open the project.
Flashing the bios to the last beta version fixed that problem,
but I still had ongoing wierdness, where the simple act of
locating to a new point in a song, and starting playback, would
temporarily hang paris. Nothing would happen, windows would go
blank, and the mouse pointer would change to an hourglass.
Then, maybe up to 30 seconds later, Paris would come back to life
and start playing. That problem was solved by replacing the RAM
(Both old and new were nothing special, just generic ddr400).
I suspect both problems were related to the RAM, and how the bios
was handling it.
Thanks for the registry instructions. I'll add them to my
Paris "scrapbook", for future reference in case that c500000 error
appears again.
Thanks also for your "workarounds" post. That also goes into my scrapbook.
Cheers,
Kim
"Dimitrios" <musurgio@otenet.gr> wrote:
>
>Kim,
>Interesting about ram.
>What ram was the old and waht is the new ?
>I have Kingston value ram 512 sticks 3 pc133 SDRAM.
>Here is what I do in registry:
> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/SessionM anager/MemoryManagement
>There you find or if not creat a dword
>DisablePagingExecutive and put value data 1
>Also for dword LargeSystemCache put also 1
>for PagedPoolSize dword put 0xfffffff (4294967295)
>for SystemPages dword put 0x000c3000 (798720)
>for dword IOPageLockLimit put 0x00040000(262144)
>
>Before doing all these export your registry file to a safe place so you
can
>recover it in case something will get screwed up...
>No big deal though.
>
>Now I don't get that exception until I reload while Paris is opened on a
>specific waves project and I reload another waves oriented project without
>first closing Paris...
>
>Regards,
>Dimitrios
>"Kim W." <no@way.com> wrote:
>>
>>Wow!!
>>I was getting that very same message with a comp I was upgrading
>>for a friend, just the other day. (He uses paris as well and
>>has waves).
>>I tried different ram and the problem went away completely.
>>This is wierd. It would be interesting to try these tweaks
>>with the old ram, and see if it fixes the c000000005 thing.
>>Dimitrios, could you be a little more specific how to apply
>>these?
>>Cheers,
>>Kim
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>Exactly Neil.
>>>I was getting it almost everytime loading a song with DX waves plugins
>loaded...
>>>Unhandled exception c0000005 at adress: ......
>>>You know the picture...
>>>Now I am getting this when I try to reload a project after I have loaded
>>>succesfully the first time.
>>>I changed for that the disablepagingexecutive(1) and LargeSystemCache(1).
>>>The other strings I have put (that moght helped too) are on same registry
>>>place where the above are...
>>>How did you get around with these unhandled exceptions and when are you
>>getting
>>>it ?
>>>Regards,
>>>Dimitrios
>>>
>>>"Don Nafe" <dnafe@magma.ca> wrote:
>>>>Were you getting get an error message stating "C0000005" or something
>like
>>>
>>>>that ?
>>>>
>>>>and where do I find these two lines on my computer?
>>>>
>>>> IOPageLockLimit=0x00040000
>>>> Pagedpoolsize=0xfffffffS
>>>>
>>>>Don
>>>>
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote in message news:45d55898$1@linux...
>>>>>
>>>>> Hi,
>>>>> I seem to find that some xp tweaks can cause Paris either to run better
>>>or
>>>>> worse.
>>>>> The disablepagingexecutive(1) and LargeSystemCache(1) has helped me
>a
>>>lot
>>>>> with waves plugins sometimes crashing when loading a song containing
>>them
>>>>> in Paris.
>>>>> IOPageLockLimit=0x00040000
>>>>> Pagedpoolsize=0xfffffffS
>>>>> The above applies if you have some hefty memory like 1GB.
>>>>> Any findings that you wanna share here that can make Paris run more
>stable
>>>>> ?
>>>>> Regards,
>>>>> Dimitrios
>>>>
>>>>
>>>
>>
>
|
|
|
|
| Re: XP tweaks for Paris share findings... [message #80177 is a reply to message #80173] |
Fri, 16 February 2007 09:17 |
Kim W
Messages: 165
Registered: July 2006
|
Senior Member |
|
|
Hi again.
Don't jump into buying new RAM just yet.
Maybe try to remove one or two, and/or swap around.
Your RAM may be fine.
See my previous reply.
Kim
"Dimitrios" <musurgio@otenet.gr> wrote:
>
>What PC133 512mb sticks are better than my Kingston valueram ?
>I have a P4B Asus mb with intel P4 2.6ghz cpu (vintage he?)
>Regards,
>Dimitrios
>
>
>"Kim W." <no@way.com> wrote:
>
>
>>
>>Wow!!
>>I was getting that very same message with a comp I was upgrading
>>for a friend, just the other day. (He uses paris as well and
>>has waves).
>>I tried different ram and the problem went away completely.
>>This is wierd. It would be interesting to try these tweaks
>>with the old ram, and see if it fixes the c000000005 thing.
>>Dimitrios, could you be a little more specific how to apply
>>these?
>>Cheers,
>>Kim
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>Exactly Neil.
>>>I was getting it almost everytime loading a song with DX waves plugins
>loaded...
>>>Unhandled exception c0000005 at adress: ......
>>>You know the picture...
>>>Now I am getting this when I try to reload a project after I have loaded
>>>succesfully the first time.
>>>I changed for that the disablepagingexecutive(1) and LargeSystemCache(1).
>>>The other strings I have put (that moght helped too) are on same registry
>>>place where the above are...
>>>How did you get around with these unhandled exceptions and when are you
>>getting
>>>it ?
>>>Regards,
>>>Dimitrios
>>>
>>>"Don Nafe" <dnafe@magma.ca> wrote:
>>>>Were you getting get an error message stating "C0000005" or something
>like
>>>
>>>>that ?
>>>>
>>>>and where do I find these two lines on my computer?
>>>>
>>>> IOPageLockLimit=0x00040000
>>>> Pagedpoolsize=0xfffffffS
>>>>
>>>>Don
>>>>
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote in message news:45d55898$1@linux...
>>>>>
>>>>> Hi,
>>>>> I seem to find that some xp tweaks can cause Paris either to run better
>>>or
>>>>> worse.
>>>>> The disablepagingexecutive(1) and LargeSystemCache(1) has helped me
>a
>>>lot
>>>>> with waves plugins sometimes crashing when loading a song containing
>>them
>>>>> in Paris.
>>>>> IOPageLockLimit=0x00040000
>>>>> Pagedpoolsize=0xfffffffS
>>>>> The above applies if you have some hefty memory like 1GB.
>>>>> Any findings that you wanna share here that can make Paris run more
>stable
>>>>> ?
>>>>> Regards,
>>>>> Dimitrios
>>>>
>>>>
>>>
>>
>
|
|
|
|
| Re: XP tweaks for Paris share findings... [message #80179 is a reply to message #80170] |
Fri, 16 February 2007 09:29 |
Kim W No2waycom
Messages: 1
Registered: February 2007
|
Junior Member |
|
|
Hi, Bill.
That tip, if memory serves, came compliments of Dimitrios
himself. I would go one better, do a fresh install onto the root
of C:. (make sure you navigate to the same
directory when installing the effects subsystem fix).
Also install all vst's into a directory on the root.
I did this to a friends system a few days ago, (using an asus
p4800s, which I retired prior to going to a K8NS ultra,)
and MAN!!, I could't get that box to fall over even after giving it hell.
(inserting-deinserting plugins whilst playing back with
editor on full zoom....32 tracks, relocating without stopping
etc etc.)
I wish I got that system running so well when it was MINE!!
:-))
Kim
hell
"Bill Terry" <nospam@nospam.com> wrote:
>
>I don't know if this would be considered a tweak, but by far the single
best
>thing I've done to stabilize my system was move the Paris install directory
>right up to root level on the drive.
>
>I installed the app and drivers EXACTLY as instructed for XP, but I still
>had all sorts of issues with the effects sub-system (at least that's what
>it seemed like) some times crashing the app in spectacular fashion, but
more
>often just hanging. I found the tip about moving the install directory up
>in a post here I think, never saw it mentioned in any of the online references.
>
>Since I moved the install directory, the system has gone from semi-flakey
>to an absolute rock.
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>Hi,
>>I seem to find that some xp tweaks can cause Paris either to run better
>or
>>worse.
>>The disablepagingexecutive(1) and LargeSystemCache(1) has helped me a lot
>>with waves plugins sometimes crashing when loading a song containing them
>>in Paris.
>>IOPageLockLimit=0x00040000
>>Pagedpoolsize=0xfffffffS
>>The above applies if you have some hefty memory like 1GB.
>>Any findings that you wanna share here that can make Paris run more stable
>>?
>>Regards,
>>Dimitrios
>
|
|
|
|
| Re: XP tweaks for Paris share findings... [message #80180 is a reply to message #80179] |
Fri, 16 February 2007 09:38 |
Miguel Vigil [1]
Messages: 258
Registered: July 2005
|
Senior Member |
|
|
Hi Kim,
It may have come from Dimitrios, I really don't remember, but you described
exactly what I did. I'm not sure which part of that process 'fixes' the problem,
but it does. Prior to that, I was VERY careful about not diddling inserts
on the fly, dragging the now line around during playback etc. and now, like
you, I can't seem to find anything that causes problems. :-)
BT
"Kim W." No2way.com wrote:
>
>Hi, Bill.
>That tip, if memory serves, came compliments of Dimitrios
>himself. I would go one better, do a fresh install onto the root
>of C:. (make sure you navigate to the same
>directory when installing the effects subsystem fix).
>Also install all vst's into a directory on the root.
>I did this to a friends system a few days ago, (using an asus
>p4800s, which I retired prior to going to a K8NS ultra,)
>and MAN!!, I could't get that box to fall over even after giving it hell.
>(inserting-deinserting plugins whilst playing back with
>editor on full zoom....32 tracks, relocating without stopping
>etc etc.)
>I wish I got that system running so well when it was MINE!!
>:-))
>Kim
>hell
>
>"Bill Terry" <nospam@nospam.com> wrote:
>>
>>I don't know if this would be considered a tweak, but by far the single
>best
>>thing I've done to stabilize my system was move the Paris install directory
>>right up to root level on the drive.
>>
>>I installed the app and drivers EXACTLY as instructed for XP, but I still
>>had all sorts of issues with the effects sub-system (at least that's what
>>it seemed like) some times crashing the app in spectacular fashion, but
>more
>>often just hanging. I found the tip about moving the install directory
up
>>in a post here I think, never saw it mentioned in any of the online references.
>>
>>Since I moved the install directory, the system has gone from semi-flakey
>>to an absolute rock.
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>Hi,
>>>I seem to find that some xp tweaks can cause Paris either to run better
>>or
>>>worse.
>>>The disablepagingexecutive(1) and LargeSystemCache(1) has helped me a
lot
>>>with waves plugins sometimes crashing when loading a song containing them
>>>in Paris.
>>>IOPageLockLimit=0x00040000
>>>Pagedpoolsize=0xfffffffS
>>>The above applies if you have some hefty memory like 1GB.
>>>Any findings that you wanna share here that can make Paris run more stable
>>>?
>>>Regards,
>>>Dimitrios
>>
>
|
|
|
|
| Re: XP tweaks for Paris share findings... [message #80181 is a reply to message #80171] |
Fri, 16 February 2007 10:28 |
Chris Ludwig
Messages: 868
Registered: May 2006
|
Senior Member |
|
|
Hi Dimitrios,
If you are using any version of waves prior to 5.2 you should try
running the current pace software update. Windows SP2 had issues with
older pace versions that would give blue screen memory address type
things your seeing.
It had something to do with the DEP I believe.
Chris
Dimitrios wrote:
> Kim,
> Interesting about ram.
> What ram was the old and waht is the new ?
> I have Kingston value ram 512 sticks 3 pc133 SDRAM.
> Here is what I do in registry:
> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/SessionM anager/MemoryManagement
> There you find or if not creat a dword
> DisablePagingExecutive and put value data 1
> Also for dword LargeSystemCache put also 1
> for PagedPoolSize dword put 0xfffffff (4294967295)
> for SystemPages dword put 0x000c3000 (798720)
> for dword IOPageLockLimit put 0x00040000(262144)
>
> Before doing all these export your registry file to a safe place so you can
> recover it in case something will get screwed up...
> No big deal though.
>
> Now I don't get that exception until I reload while Paris is opened on a
> specific waves project and I reload another waves oriented project without
> first closing Paris...
>
> Regards,
> Dimitrios
> "Kim W." <no@way.com> wrote:
>> Wow!!
>> I was getting that very same message with a comp I was upgrading
>> for a friend, just the other day. (He uses paris as well and
>> has waves).
>> I tried different ram and the problem went away completely.
>> This is wierd. It would be interesting to try these tweaks
>> with the old ram, and see if it fixes the c000000005 thing.
>> Dimitrios, could you be a little more specific how to apply
>> these?
>> Cheers,
>> Kim
>>
>> "Dimitrios" <musurgio@otenet.gr> wrote:
>>> Exactly Neil.
>>> I was getting it almost everytime loading a song with DX waves plugins
> loaded...
>>> Unhandled exception c0000005 at adress: ......
>>> You know the picture...
>>> Now I am getting this when I try to reload a project after I have loaded
>>> succesfully the first time.
>>> I changed for that the disablepagingexecutive(1) and LargeSystemCache(1).
>>> The other strings I have put (that moght helped too) are on same registry
>>> place where the above are...
>>> How did you get around with these unhandled exceptions and when are you
>> getting
>>> it ?
>>> Regards,
>>> Dimitrios
>>>
>>> "Don Nafe" <dnafe@magma.ca> wrote:
>>>> Were you getting get an error message stating "C0000005" or something
> like
>>>> that ?
>>>>
>>>> and where do I find these two lines on my computer?
>>>>
>>>> IOPageLockLimit=0x00040000
>>>> Pagedpoolsize=0xfffffffS
>>>>
>>>> Don
>>>>
>>>>
>>>> "Dimitrios" <musurgio@otenet.gr> wrote in message news:45d55898$1@linux...
>>>>> Hi,
>>>>> I seem to find that some xp tweaks can cause Paris either to run better
>>> or
>>>>> worse.
>>>>> The disablepagingexecutive(1) and LargeSystemCache(1) has helped me
> a
>>> lot
>>>>> with waves plugins sometimes crashing when loading a song containing
>> them
>>>>> in Paris.
>>>>> IOPageLockLimit=0x00040000
>>>>> Pagedpoolsize=0xfffffffS
>>>>> The above applies if you have some hefty memory like 1GB.
>>>>> Any findings that you wanna share here that can make Paris run more
> stable
>>>>> ?
>>>>> Regards,
>>>>> Dimitrios
>>>>
>
--
Chris Ludwig
ADK Pro Audio
(859) 635-5762
www.adkproaudio.com
chrisl@adkproaudio.com
|
|
|
|
Goto Forum:
Current Time: Tue Dec 24 13:54:32 PST 2024
Total time taken to generate the page: 0.02289 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
