This is an interesting development. Pd stopped letting me access the "path" and "startup" GUIs, nothing happens when I select them; So I redownloaded and reinstalled elsewhere, and the new pd.exe still tries to read the bins I had selected for the old one, and still won't let me view them. I searched for .pdrc, but I'll try searching again.

On 9/8/05, Chuckk Hubbard badmuthahubbard@gmail.com wrote:

I hate having to ask these questions because I know it seems like I didn't check Google or the archives, but I did. I have zexy working, if I manually open zexy.pd before trying to use any of it. However, I can't figure out how to get Gem to work. I also see now it should be possible for zexy to be loaded automatically so I don't have to open that file first. I'm on WinXP, with Pd 0.38.3. There's a GUI for startup binaries and flags... One odd thing about it is that deleting something from any of these fields, and hitting the Apply and Save Settings buttons over and over has no effect: the commands that didn't work are reinserted when I restart Pd. I can deal with that... So, if I have gem.dll and zexy.dll in particular locations, shouldn't I be able to paste the entire paths to them in quotes into the "binaries to load on startup", and it will find them? I also put in the -path and -lib flags suggested in the readmes. I don't fully understand the process Pd goes through. If it can find the .dll, is that all it should need? As of now I get a message for each startup bin saying Pd couldn't load the library. Also, in reference to .pdrc, what is the syntax for it? Should I just type a bunch of flags into a text editor and save as .pdrc?

Thanks guys! -Chuckk

-- "It is not when truth is dirty, but when it is shallow, that the lover of knowledge is reluctant to step into its waters." -Friedrich Nietzsche, "Thus Spoke Zarathustra"

Boy, was that painfully simple. So ">pd -lib gem -lib zexy" was all I needed; but now I am still unable to change the startup flags or bins from the GUI... any ideas?

On 9/8/05, Chuckk Hubbard badmuthahubbard@gmail.com wrote:

I hate having to ask these questions because I know it seems like I didn't check Google or the archives, but I did. I have zexy working, if I manually open zexy.pd before trying to use any of it. However, I can't figure out how to get Gem to work. I also see now it should be possible for zexy to be loaded automatically so I don't have to open that file first. I'm on WinXP, with Pd 0.38.3. There's a GUI for startup binaries and flags... One odd thing about it is that deleting something from any of these fields, and hitting the Apply and Save Settings buttons over and over has no effect: the commands that didn't work are reinserted when I restart Pd. I can deal with that... So, if I have gem.dll and zexy.dll in particular locations, shouldn't I be able to paste the entire paths to them in quotes into the "binaries to load on startup", and it will find them? I also put in the -path and -lib flags suggested in the readmes. I don't fully understand the process Pd goes through. If it can find the .dll, is that all it should need? As of now I get a message for each startup bin saying Pd couldn't load the library. Also, in reference to .pdrc, what is the syntax for it? Should I just type a bunch of flags into a text editor and save as .pdrc?

Thanks guys! -Chuckk

-- "It is not when truth is dirty, but when it is shallow, that the lover of knowledge is reluctant to step into its waters." -Friedrich Nietzsche, "Thus Spoke Zarathustra"