Yup - it's definitely something to do with where the project file folder resides. I tried this at work just now and it ran perfectly - just a shell project. I guess I'm so used to GLPRO that I've been trying to keep my projects in the afterGrasp directory - and that just does not work.
Thanks Erwin for jumping in with another good suggestion. Perhaps a quick start guide bundled into the releases would help folks with some of the blind alleys (no offense to John - this is a great list) for us occational (read - would like to get paid to create software with this tool) users. Regards, Tom N. New News Productions -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Erwin Sent: Tuesday, May 16, 2006 1:22 AM To: [email protected] Subject: RE: Unable To Compile Hi, I noticed some time before that the path of your project schould be without spaces (\program files does not work, \progam_files does) Regards, Erwin Eliveld -- ==> This email and any files transmitted with it are confidential/private and intended solely for the use of the individual or entity to whom they are addressed. Unauthorized use of this message, or any portion of it, will be prosecuted to the maximum extent possible under the law. If you have received this email in error please notify [EMAIL PROTECTED] --------- Oorspronkelijk bericht -------- Van: [email protected] Naar: [email protected] <[email protected]> Onderwerp: RE: Unable To Compile Datum: 15/05/06 23:59 > > Hello again, > > I tried option number 1. Same problem. > > Then I tried option number 2, and felt like I was getting farther away from > the solution. > > So I tried option number 1 again. > This time I deleted the AfterGrasp directory, and double checked that > the registry was deleted properly. Then I rebooted. > > Next I created a new project, and for some reason decided to try the folder > where the AG editor wanted to put it, which was C:testproject (instead > of inside the AG directory) That worked. > Next I tried the exact same project but inside the AG directory ( c:program > filesaftergrasptest. That returned an error of "an unnamed file > was not > found". > > Back to my memory - Did I remember reading somewhere that AG projects > need to be in the root directory? > > Thanks for your help. > > Tom N. > New News Productions > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > On Behalf Of John Bridges > Sent: Monday, May 15, 2006 7:38 AM > To: [email protected] > Subject: Re: Unable To Compile > > > On 5/14/06, TNovotny <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > I am getting the "unable to compile" message on the > latest build. > > I uninstalled the old version, and reinstalled the latest "mother's day > > build" just released. I seem to remember a post where the registry had to > be > > tweaked or something. > > > > I'm running XP Home, with SP2 > > > > Thanks in advance for any help in getting this up and running. > > > > Regards, > > > > Tom N. > > > > I just downloaded the install, and ran it on a fresh machine (one that > never had AfterGRASP installed on it). I then ran the script editor, > started a new project called tested, let it create the default script, > and ran it using F10. > > I'm pretty confident the build up there right now works on a clean machine. > > Are you trying a default blank project, or something more complex? > > If it's the default blank project, then I'm going to assume something > is left over from a previous install that is causing a problem. > > Two things to try. > > 1. Uninstall AfterGRASP, then go into the registry with REGEDIT, and > delete the Pallas Press registry branch: > [HKEY_CURRENT_USERSoftwarePallas Press] > > Reinstall AfterGRASP and see if it works. > > 2. Rename C:GLPROGLBIND32.EXE to C:GLPROGLBIND32.ORIGINAL. Then copy > AGEXE.EXE into C:GLPROGLBIND32.EXE. Now try compiling and running your > script with GLPRO (CTRL-F10, F10 won't work). (substitute whatever > directory you have GLPRO installed to if it's not C:GLPRO). > > > If it's truely a compile error, I suggest using the GLPRO editor with > AGEXE as GLBIND32 since AGEDIT doesn't display compiler errors. But > AGEXE does. > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "aftergrasp" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/aftergrasp -~----------~----~----~----~------~----~------~--~---
