VC executes things as if it were in the root of your project folder.
ie: you have a project called circle, and you compiled at as a release,
assuming
MSDEV is installed in c:\program files\msdev
your project folder would be:
C:\Program Files\Msdev\Projects\Circle
your executable is:
C:\Program Files\Msdev\Projects\Circle\Release\circle.exe
when you select execute on the menu, it runs the following line:
release\circle.exe
This can be seen on the project settings.....
What this all means is that in order to run circle outside of VC, you have
to open up a dos prompt. Switch to the root directory of your mud
(c:\program files\msdev\projects\circle) and type release\circle
hope this helps you :)
-Steven
----------
> From: Andrew <object@ALPHALINK.COM.AU>
> To: CIRCLE@post.queensu.ca
> Subject: [VC++5] Executing circle.exe from outside compiler
> Date: Saturday, October 10, 1998 12:13 AM
>
> Hi all. I've been having trouble executing circle.exe when I haven't been
in
> the actual MSVC++ 5.0 compiler. I go start->run, and then type in
> \circle\circle30bpl14\bin\circle.exe, and it starts up but almost
immediately
> a SYSERR: comes up in the app, and immediately quits. I can't read the
SYSERR,
> and log files don't work with Win95.
>
> However, if I'm in VC++ and open my workspace and go Build->Execute
everything
> works fine. It's a pain in the bum though starting up VC++ whenever I
want to
> run circle.
>
> Any ideas?
>
> -- Andrew.
>
> | Andrew Ritchie, object@alphalink.com.au.
>
>
> +------------------------------------------------------------+
> | Ensure that you have read the CircleMUD Mailing List FAQ: |
> | http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
> +------------------------------------------------------------+
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST