Hi,
Has anybody been able to install and use PD Extended on Vista and if so, how did you do it?
Here are the troubles I have been having:
Extended, it was not extended, that is, it wouldn't load the libraries.
Then I executed the "pd-settings.reg" file but nothing changed
Then I figured out that the .reg file was putting the settings in a
key, while the program was actually loading them from another key, in the registry
put the loadlib keys in the correct place.
And it did, but PD still would load the libraries
Then I noticed that, though the "loadlib" keys had been modified
correctly, the "nloadlib" key still was "1" (though in the file there IS a line to change it to 35, but for some reason it didn't work). Same for npath that was still at 0 instead of 1 (and the one font path was set correctly)
"npath" to 1
doesn't even output any message to the console, not even the [import]-related one that it used to print even when it didn't load the libraries. I cannot even close it, I have to use Task Manager to kill it
Anybody else using Vista?
thanks m.
Wow, I had installed it in a custom folder in the D: drive.
Now I've installed it in the default C:%Program Files%\ folder and (after the registry tricks) it does work.
So for some reason it doesn't work if installed in a custom folder...
Any idea why?
Matteo Sisti Sette escribió:
Hi,
Has anybody been able to install and use PD Extended on Vista and if so, how did you do it?
Here are the troubles I have been having:
- I downloaded and run the installer package, and when I run PD
Extended, it was not extended, that is, it wouldn't load the libraries.
Then I executed the "pd-settings.reg" file but nothing changed
Then I figured out that the .reg file was putting the settings in a
key, while the program was actually loading them from another key, in the registry
- So I manually modified the .reg file and executed it so that it would
put the loadlib keys in the correct place.
And it did, but PD still would load the libraries
Then I noticed that, though the "loadlib" keys had been modified
correctly, the "nloadlib" key still was "1" (though in the file there IS a line to change it to 35, but for some reason it didn't work). Same for npath that was still at 0 instead of 1 (and the one font path was set correctly)
- So I changed manually the "nloadlib" registry key to 35 and the
"npath" to 1
- Now PD hangs at startup: I open it and it becomes unresponsive. It
doesn't even output any message to the console, not even the [import]-related one that it used to print even when it didn't load the libraries. I cannot even close it, I have to use Task Manager to kill it
Anybody else using Vista?
thanks m.
On Sun, 2010-01-10 at 18:38 +0100, Matteo Sisti Sette wrote:
Wow, I had installed it in a custom folder in the D: drive.
Now I've installed it in the default C:%Program Files%\ folder and (after the registry tricks) it does work.
So for some reason it doesn't work if installed in a custom folder...
Any idea why?
sounds like hard-coded paths. Pd-vanilla on windows used to work from any install location; too bad that isn't the case any more with a recent Pd-extended. On Linux, pathes have been hard-coded since i know Pd.
Roman
Roman Haefeli escribió:
Pd-vanilla on windows used to work from any install location;
Yes it does. Indeed it doesn't even have an installer, it's just a zip you unpack wherever you want. I've always moved the folder around at my will and often had multiple different version on the same machine. Never had any issues with it with Vanilla.
The possibility to have different versions installed, running independedtly without interfering with each other should always be taken into account. Now I need to have both vanilla and extended and it's being difficult like hell: imagine trying to have a couple of different versions of Extended...
On Sun, 2010-01-10 at 19:46 +0100, Matteo Sisti Sette wrote:
Roman Haefeli escribió:
Pd-vanilla on windows used to work from any install location;
Yes it does. Indeed it doesn't even have an installer, it's just a zip you unpack wherever you want. I've always moved the folder around at my will and often had multiple different version on the same machine. Never had any issues with it with Vanilla.
The possibility to have different versions installed, running independedtly without interfering with each other should always be taken into account.
I also would prefer, if _all_ Pd versions wouldn't rely on hard-coded pathes.
Roman
On Jan 10, 2010, at 2:06 PM, Roman Haefeli wrote:
On Sun, 2010-01-10 at 19:46 +0100, Matteo Sisti Sette wrote:
Roman Haefeli escribió:
Pd-vanilla on windows used to work from any install location;
Yes it does. Indeed it doesn't even have an installer, it's just a
zip you unpack wherever you want. I've always moved the folder around
at my will and often had multiple different version on the same machine.
Never had any issues with it with Vanilla.The possibility to have different versions installed, running independedtly without interfering with each other should always be
taken into account.I also would prefer, if _all_ Pd versions wouldn't rely on hard-coded pathes.
Roman
I don't think anyone would argue with that, its just a matter of
someone making it work :)
.hc
'You people have such restrictive dress for women,’ she said, hobbling
away in three inch heels and panty hose to finish out another pink-
collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
At the end I deleted and re-installed pd-extended, and though I have installed it on the D drive (custom folder), it does work now. The Windows way of fixing problems...
I had to manually modify and run the .reg file to store the loadlib keys into the location where the program expects them to be.
Now I only have to struggle to have PD Vanilla work as Vanilla (i'll try -noprefs, hope it won't have side effects)....
Hans-Christoph Steiner escribió:
On Jan 10, 2010, at 2:06 PM, Roman Haefeli wrote:
On Sun, 2010-01-10 at 19:46 +0100, Matteo Sisti Sette wrote:
Roman Haefeli escribió:
Pd-vanilla on windows used to work from any install location;
Yes it does. Indeed it doesn't even have an installer, it's just a zip you unpack wherever you want. I've always moved the folder around at my will and often had multiple different version on the same machine. Never had any issues with it with Vanilla.
The possibility to have different versions installed, running independedtly without interfering with each other should always be taken into account.
I also would prefer, if _all_ Pd versions wouldn't rely on hard-coded pathes.
Roman
I don't think anyone would argue with that, its just a matter of someone making it work :)
.hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf