Thanks for the leghty response, but im acutally using OSX. Creating batch files, or command? files in OSX is different than in windows because when i rename the command file, it loses its "executable" qualities? It gives me errors when i double click it. Thanks
Hi,
don't let them funny *nix folks get you all mixed up! To my knowledge, a pdrc is a useless file in windoze because you don't have a "home" directory. At least not in the Unix world-concept.
For your needs, it is best to take Florian's advice a post or two back in the thread and put everything together in your pd.bat file. I reprint his post below:
never properly having worked with dos commands before i used pd, i had lots
of trouble loading externals when i first started. i suggest you might do as IOhannes said but make yourself a .bat file to start pd instead of typing all stuff into the command window:
open a new text file in windows notepad, type in all your paths, flags, lib
locations sth like:
c:\pd\bin\pd.exe -nomidin -nomidiout -font 10 -blablabla -path
c:\thepathtofiles (if needed, this should be in the externals readme you want to load) -lib c:\thepathtothedlloftheexternal;c:\thepathtoanotherexternal....
save it (*.txt), close it and simply rename to .bat instead of .txt. now
either double-click or load from a command prompt.
You are probably having trouble starting PD from the DOS shell because it is in a funny place like C:\Program Files or something like that with a space in it. You will need to type the full path name to PD, and as IOhannes suggested, avoid directories with spaces because "C:\Program Files" actually must be typed as "C:\Program\ Files" to be read properly, or else DOS thinks that the path is "C:\Program" and that "Files" is a command or some additional info... Better to move your whole PD directory tree directly to "C:". Trust me, it will be easier that way.
I could go on, but a good resource for PD on windows for the wet-behind-the-ears newbie is here:
http://www.parasitaere-kapazitaeten.net/Pd/start_pd_win.htm
This should explain path names and .bat files very clearly. Why isn't this info part of the Friendly Manual [TM], anyway? ;-)
good luck, d
doniguan@stny.rr.com wrote:
Is the pdrc file something only found in the enhanced version of pd? I
installed version .37 from an installer, i dont think i have the enhanced version.
doniguan@stny.rr.com wrote:
Thanks for the leghty response, but im acutally using OSX.
OOOOPPPPS!
Sorry. My mistake! I really thought somewhere in the thread you mentioned windoze. I think a few others did as well. It helps to be *very* explicit about this kind of stuff :-)
If you want to edit your PD start file for OSX, you shouldn't use a GUI text editor, as it can introduce funny formatting and permissions, and as you have seen, it can kill the executable part of your file.
My suggestion is to open a terminal and use the app "pico" to edit your preexisting PD start file. Pico doesn't change any of the permissions [this includes executable] so you should be safe.
Type:
pico /path/to/pd.command
I think it is better not to use line breaks in this file, but to seperate your startup flags with spaces.
You can also make a .pdrc file in your home directory. You can use line breaks to seperate the flags as Sara has done on the umatic.nl page I mention below.
Both ways will do the same thing, so choose which one works for you. There is no .pdrc by default, you must create one yourself.
More info on PD for OSX can be found here as well:
http://www.umatic.nl/pdp_install.html
There is a section on creating your .pdrc and your pd.command file. Bonus info is one way to install PDP. But you should tackle that later...
good luck, d.