Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Input run-time module path

Input run-time module path

Input run-time module path

I compiled my program to require brun45 (it won't compile without it), is that what it's looking for, because I keep telling it that brun45 is in c:\qb45\, but it keeps prompting me.

RE: Input run-time module path

maybe you need brun45 in the same folder as the compiled program or maybe the / at the end of c:/brun45/ shouldnt be there

RE: Input run-time module path

Never mind, I figured out what was giving me so many errors and fixed it, I no longer require brun45.
But I do have another question: My game seems to be a bit unstable at times, the main reason is that I have it switching between exe programs frequently (a movie/wave player and a menu.)  I restablized them greatly by adding the CLEAR statement to the end of the program.

My question:  Is there an advantage to using END or SYSTEM or STOP, compared to simply ending the program, and if so, what are they for each?

RE: Input run-time module path

you use end if you want to stop the program halfway through instead of using a large amount of goto's.               you probaly know this already.

RE: Input run-time module path

I'm talking about at the end of the program. I know that they all clear the stack space, memory, and close all files, but what do they do differently?

RE: Input run-time module path

Back in the old days, END was used to terminate the program at a particular point of the program. By terminating with END, it was supposed to close all open files and release/clean out the stacks.  As for personal opinion, END is used for self-contianed programs.

As for SYSTEM, it would stop the processes of the program and return to the DOS command (or calling program--similar to chain & run commands) only problem I'm aware of is that it was leaving files open and not relinquishing the stacks (memory was at a premium then)

When w95 came out that's when I noticed the differences between the two.  By way of .PIFs, my programs that ended with END -- the DOS title bar would say FINISHED - you prog.  And those with SYSTEM, the DOS box would simply close.

Nowadays, with all that darn patch work from MS, you have to modify the .LNKs to "close on exit".

You should play around with them to see for yourself.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close