Yes, this is the problem. As mentioned on the GEM website (but unfortuanetly not in the FAQ...I'll fix this), you have to type Gem (with the upper case). For an obscure reason lost in history, the entrance point to GEM is a function called Gem_setup...and that is the function name that PD searches for. In the next release, I'll probably put some hooks in so that you can type GEM, or gem, or gEm, or whatever.
GEM shouldn't be sensitive to where pd.exe is actually located, but it must be able to find the .dll. I avoid this problem by making sure that pd.exe is my path environment.
Also, for people who are concerned about the speed of their computer, if you get a Voodoo2 graphics accelerator, GEM works great with it.
Please let me know if you are having any other problems.
Later, Mark
-- Mark Danks -- mdanks@stormfront.com
-- http://www.danks.org/mark
-----Original Message----- From: Soeren Bovbjerg [mailto:bovbjerg@musik.auc.dk] Sent: Sunday, October 11, 1998 12:20 PM To: pd-list@iem.mhsg.ac.at Subject: Sv: Need help starting GEM on Win 95
Hi,
I have just startet using PD and GEM, but I also also had the same problem - and solved it. It seems, that the PD commandline parameters are case sensitive (!!!!) In my case it works fine if I type:
pd -lib /pd/gem/Gem
(with an uppercase G)
Remember to put both the 'pd' and 'pd/gem' directories in your path!
However, GEM also seems to be sensitive to where PD is located. I could not start GEM when I installed PD in a subdirectory (e.g. c:\music\pd\ with gem in c:\music\pd\gem) but that doesn't seem to be your problem.