'wfm02_2009' is not recognized as an internal or external command,
operable program or batch file.
I read through the articles in the list serve that I could find concerning
this, but nothing jumped out at me..
I have walked through the checking of the environment variables with a
buddy at a different place to make sure that I have the equivalent that he
does, but feel that I must be missing something.
In User Variables, I have
PATH c:\admb\gcc440\bin; c:\gnu\gcc\bin; c:\gnu\gdb\bin;
I thought I remembered having to tinker with something in the System
Variables part of the Env Variables last time I did an install, but cannot
remember what it was and we could not find anything corresponding to admb
in System variables on my colleagues computer.
I have tried the install twice (removing all signs of ADMB in between) but
to no avail. I am not sure if there is something on the federal IT system
that is blocking it from creating the .exe file, but the furthest it gets
is creating a .cpp and .htp files. When I try and run an old project with
a already created .exe file, it works just fine.
Can anyone help me out or let me know what kind of questions I should be
asking my IT folks?
Thanks a bunch..
Users mailing list
tpl2cpp.exe has encountered a problem and needs to close. We are sorry for the inconvenience.I don't know if these problems are somehow related to the configuration of federal computers, or just any setup with a non-administrative user. Either way, it would be good to get things working, but I'm afraid we'll need Arni's advice on what to try next.
The INCLUDE and LIB variables are unnecessary and should not be defined.
Probably not the root of the problem, but I recommend leaving them
AD Model Builder with GCC requires only two env variables, ADMB_HOME and
PATH, and ADMB-IDE needs a third variable HOME. The ADMB-IDE installer
tries to set these three variables, and the values you list above look
If you can translate simple.tpl to simple.cpp and simple.htp, then at
least tpl2cpp is working. It sounds like you are unable to build
simple.exe out of simple.cpp and simple.htp. The first test, then, is to
check whether GCC is able to build hello.exe out of hello.cpp.
Create c:/hello/hello.cpp from
http://helloworldsite.he.funpic.de/hello.htm#C++-ISO, open a Dos shell,
navigate to c:/hello, and run Test #1:
g++ -s -static -Wall hello.cpp -o hello
If your setup passes this first test and creates a healthy hello.exe, then
GCC is working. The next test is to copy simple.tpl and simple.dat to
directory c:/simple, open a Dos shell, navigate to c:/simple, and run Test
If your setup passes this second test and creates a healthy simple.exe,
then ADMB is working and the problem is either ADMB-IDE or a
misunderstanding of how it works. Before we go there, it would be great if
you can run these two tests to narrow the search.
P.S. Many beginning users can benefit from this discussion. You made a
good effort reading through old messages on the mailing list, but luckily
Ian Taylor has taken the initiative and is preparing an ADMB FAQ, where
previous help-related discussions will be archived in an organized way
that's easy to browse. An alpha version is already on the web in a secret
One problem was the finicky nature of the Environmental Variables (no
spaces allowed), and the other was that in the process of changing
settings on my computer, I somehow must have corrupted the simple.tpl
file or something else in that directory that I was using to test the
compiling. I finally thought to try compiling a different file which
worked fine, and after wiping out and replacing the directory with the
simple.tpl file that caused tpl2cpp to crash, that test is working again
In case anyone else wants to try the setup, and for completeness in the
email archives, here are the steps that seem to get the current version
of the ADMB-IDE working for non-administrative user accounts.
1. Have an administrator run the ADMB-IDE installer to create the full
2. As the non-admin user, create the following User Variables (via right
click on My Computer > Properties > Advanced > Environmental Variables >
New), making sure the paths all match existing directories and that you
have no spaces:
One issues worth noting is that the files created by the installer
c:/~/.emacs or c:/~/.recentf may need to have their security settings
changed if the non-admin user wants to modify the setup or get a list of
recently used files within the ADMB-IDE. Second, for users of R, the
creation of a HOME variable has implications for where R looks for
things. It seems you can override this by creating an additional
variable called R_USER pointing to where you want R to look for packages.