Help! XP & Quick Basic 4.5 Program

[Mort Middleman]

I recently installed a new system running Windows XP Home Edition. I
started the process of bringing my Quick Basic 4.5 programs over. In
my test, I brought up the command prompt and entered the path for the
compiled program - c:\basic\(program name).exe. A message appeared in
the command window as follows: Input run-time module path:

The program had been compiled using the runtime option (brun45.exe). I
entered that path - c:\qb45\brun45.exe and the same message appeared
again. I also tried entering c:\qb45\brun45.lib and got the same
result.

When running Quick Basic programs on my old system I did not have to
enter the run-time module path.

Using my old computer, I recompiled the program without the run-time
option, which produces an exe file about four times the size of the
exe file used with the run-time module. I ported this exe file over to
the new system and it ran successfully. But I really don't want to
have to recompile all of these programs, (there are loads of them,)

Any assistance offered would be greatly appreciated. Please respond
here - I am using a false address on all news group postings, as I
think my real address was harvested by the worm hackers and I am
receiving lots of fake e-mail purporting to be from Microsoft,
Returned Mail, etc.

[RipVanWinkle]

Copy BRUN45.EXE to the folder where you are executing the program or, if you
prefer, anywhere else on your path.

Post by Mort Middleman
I recently installed a new system running Windows XP Home Edition. I
started the process of bringing my Quick Basic 4.5 programs over. In
my test, I brought up the command prompt and entered the path for the
compiled program - c:\basic\(program name).exe. A message appeared in
The program had been compiled using the runtime option (brun45.exe). I
entered that path - c:\qb45\brun45.exe and the same message appeared
again. I also tried entering c:\qb45\brun45.lib and got the same
result.
When running Quick Basic programs on my old system I did not have to
enter the run-time module path.
Using my old computer, I recompiled the program without the run-time
option, which produces an exe file about four times the size of the
exe file used with the run-time module. I ported this exe file over to
the new system and it ran successfully. But I really don't want to
have to recompile all of these programs, (there are loads of them,)
Any assistance offered would be greatly appreciated. Please respond
here - I am using a false address on all news group postings, as I
think my real address was harvested by the worm hackers and I am
receiving lots of fake e-mail purporting to be from Microsoft,
Returned Mail, etc.

[Mort Middleman]

Thanks Rip, but after moving brun45.exe to the same folder which
contains the exe for the program, the results were exactly the same.
Any other ideas? Anyone else with another idea?

By the way, I think the compiler generates a link in the program exe
that points to the original location of brun45.exe, which is folder
QB45. There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

Post by RipVanWinkle
Copy BRUN45.EXE to the folder where you are executing the program or, if you
prefer, anywhere else on your path.

Post by Mort Middleman
I recently installed a new system running Windows XP Home Edition. I
started the process of bringing my Quick Basic 4.5 programs over. In
my test, I brought up the command prompt and entered the path for the
compiled program - c:\basic\(program name).exe. A message appeared in
The program had been compiled using the runtime option (brun45.exe). I
entered that path - c:\qb45\brun45.exe and the same message appeared
again. I also tried entering c:\qb45\brun45.lib and got the same
result.
When running Quick Basic programs on my old system I did not have to
enter the run-time module path.
Using my old computer, I recompiled the program without the run-time
option, which produces an exe file about four times the size of the
exe file used with the run-time module. I ported this exe file over to
the new system and it ran successfully. But I really don't want to
have to recompile all of these programs, (there are loads of them,)
Any assistance offered would be greatly appreciated. Please respond
here - I am using a false address on all news group postings, as I
think my real address was harvested by the worm hackers and I am
receiving lots of fake e-mail purporting to be from Microsoft,
Returned Mail, etc.

[Paul O. BARTLETT]

[cut]
[...] There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

As far as Bill Gate$ is concerned, DOS is dead. It would not
surprise me at all if the DOS emulation in XP is imperfect, so that
programs which were developed originally for a strictly DOS environment
may no longer run correctly. (That's just a guess. Win 95/98/ME
actually have an underlying DOS, but NT/2000/XP do not.)

[a***@NOW.AT.arargh.com]

On Tue, 30 Sep 2003 16:20:14 -0400, "Paul O. BARTLETT"

Post by Paul O. BARTLETT

[cut]
[...] There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

As far as Bill Gate$ is concerned, DOS is dead. It would not
surprise me at all if the DOS emulation in XP is imperfect, so that
programs which were developed originally for a strictly DOS environment
may no longer run correctly. (That's just a guess. Win 95/98/ME
actually have an underlying DOS, but NT/2000/XP do not.)

There is a DOS in 'Win 95/98/ME', but it's not much more than a
program loader. Once Win loads, everything is handled by Win, AFAIK.

[a***@NOW.AT.arargh.com]

Post by Mort Middleman
Thanks Rip, but after moving brun45.exe to the same folder which
contains the exe for the program, the results were exactly the same.
Any other ideas? Anyone else with another idea?
By the way, I think the compiler generates a link in the program exe
that points to the original location of brun45.exe, which is folder
QB45. There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

Off hand, I doubt that. It would make no sense to have any fixed
locations hard coded in the runtime.

[Todd Vargo]

Post by Mort Middleman
Thanks Rip, but after moving brun45.exe to the same folder which
contains the exe for the program, the results were exactly the same.
Any other ideas? Anyone else with another idea?
By the way, I think the compiler generates a link in the program exe
that points to the original location of brun45.exe, which is folder
QB45. There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

Do you have XP running the QB program on a local drive or from a server?

--
Todd Vargo (body of message must contain my name to reply by email)

[Mort Middleman]

On a local drive.

Post by Todd Vargo

Post by Mort Middleman
Thanks Rip, but after moving brun45.exe to the same folder which
contains the exe for the program, the results were exactly the same.
Any other ideas? Anyone else with another idea?
By the way, I think the compiler generates a link in the program exe
that points to the original location of brun45.exe, which is folder
QB45. There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

Do you have XP running the QB program on a local drive or from a server?

[n***@bounceall.net]

Post by Mort Middleman
On a local drive.

Post by Todd Vargo

Post by Mort Middleman
Thanks Rip, but after moving brun45.exe to the same folder which
contains the exe for the program, the results were exactly the same.
Any other ideas? Anyone else with another idea?
By the way, I think the compiler generates a link in the program exe
that points to the original location of brun45.exe, which is folder
QB45. There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

Do you have XP running the QB program on a local drive or from a server?

Have you used google to search the issue. There are many XP groups
where you may find an answer. Also do not forget that XP uses config.nt
and autoexec.nt.

LB

[Mort Middleman]

Thanks. I will check it out.

Post by n***@bounceall.net

Post by Mort Middleman
On a local drive.

Post by Todd Vargo

Post by Mort Middleman
Thanks Rip, but after moving brun45.exe to the same folder which
contains the exe for the program, the results were exactly the same.
Any other ideas? Anyone else with another idea?
By the way, I think the compiler generates a link in the program exe
that points to the original location of brun45.exe, which is folder
QB45. There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

Do you have XP running the QB program on a local drive or from a server?

Have you used google to search the issue. There are many XP groups
where you may find an answer. Also do not forget that XP uses config.nt
and autoexec.nt.
LB

[Guido ( Chris Harper )]

Check your PATH line in your DOS call. On 2000Pro it's in AUTOEXEC.NT in the
WINDOWS\SYSTEM32 directory. If the path line hits both directories, you wont
need to move brun45.exe.

Post by Todd Vargo

Post by Mort Middleman
Thanks Rip, but after moving brun45.exe to the same folder which
contains the exe for the program, the results were exactly the same.
Any other ideas? Anyone else with another idea?
By the way, I think the compiler generates a link in the program exe
that points to the original location of brun45.exe, which is folder
QB45. There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

Do you have XP running the QB program on a local drive or from a server?
--
Todd Vargo (body of message must contain my name to reply by email)

[computerd]

If you have the code then use the bc.exe program to compile the code. Use
bc /o this option will compile to an executable without having to use the
brun45.exe library. Basically making it a standalone executable. It should
work fine then. I have compressed several files without any problems under
Windows XP.

Just an example. If you have quickbasic version 4.5. Then compile your
.bas file in the following way.
Example using a file called trackit.bas

bc /o
Source Filename [.bas]: Trackit <---enter your name of
the .bas file here without the extension. Then press enter
Object Filename [Trackit.obj] <just press enter here
Source Listing [Nul.lst] <just press enter
here

This will create trackit.obj file.

Link trackit.obj

Then press enter 3 times to compile it. If you have a special Library then
make sure you link the necessary library as well. In most cases you will
not use it unless you bought some assembly routines like me.

Hope this works.

Post by Mort Middleman
Thanks Rip, but after moving brun45.exe to the same folder which
contains the exe for the program, the results were exactly the same.
Any other ideas? Anyone else with another idea?
By the way, I think the compiler generates a link in the program exe
that points to the original location of brun45.exe, which is folder
QB45. There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

Post by RipVanWinkle
Copy BRUN45.EXE to the folder where you are executing the program or, if you
prefer, anywhere else on your path.

Post by Mort Middleman
I recently installed a new system running Windows XP Home Edition. I
started the process of bringing my Quick Basic 4.5 programs over. In
my test, I brought up the command prompt and entered the path for the
compiled program - c:\basic\(program name).exe. A message appeared in
The program had been compiled using the runtime option (brun45.exe). I
entered that path - c:\qb45\brun45.exe and the same message appeared
again. I also tried entering c:\qb45\brun45.lib and got the same
result.
When running Quick Basic programs on my old system I did not have to
enter the run-time module path.
Using my old computer, I recompiled the program without the run-time
option, which produces an exe file about four times the size of the
exe file used with the run-time module. I ported this exe file over to
the new system and it ran successfully. But I really don't want to
have to recompile all of these programs, (there are loads of them,)
Any assistance offered would be greatly appreciated. Please respond
here - I am using a false address on all news group postings, as I
think my real address was harvested by the worm hackers and I am
receiving lots of fake e-mail purporting to be from Microsoft,
Returned Mail, etc.

_______________________________________________________________________________
Posted Via Uncensored-News.Com - Accounts Starting At $6.95 - http://www.uncensored-news.com
<><><><><><><> The Worlds Uncensored News Source <><><><><><><><>

[Mort Middleman]

I have already tried your suggested method and it works. But the .exe
files are much larger than those compiled with brun45.exe. My drive
is partitioned and I am using QuickBasic in a DOS partition, which is
much smaller than the Windows partition.

Post by computerd
If you have the code then use the bc.exe program to compile the code. Use
bc /o this option will compile to an executable without having to use the
brun45.exe library. Basically making it a standalone executable. It should
work fine then. I have compressed several files without any problems under
Windows XP.
Just an example. If you have quickbasic version 4.5. Then compile your
.bas file in the following way.
Example using a file called trackit.bas
bc /o
Source Filename [.bas]: Trackit <---enter your name of
the .bas file here without the extension. Then press enter
Object Filename [Trackit.obj] <just press enter here
Source Listing [Nul.lst] <just press enter
here
This will create trackit.obj file.
Link trackit.obj
Then press enter 3 times to compile it. If you have a special Library then
make sure you link the necessary library as well. In most cases you will
not use it unless you bought some assembly routines like me.
Hope this works.

Post by Mort Middleman
Thanks Rip, but after moving brun45.exe to the same folder which
contains the exe for the program, the results were exactly the same.
Any other ideas? Anyone else with another idea?
By the way, I think the compiler generates a link in the program exe
that points to the original location of brun45.exe, which is folder
QB45. There must be some reason why it works from a DOS window in
Win95 but is not working in XP.

Post by RipVanWinkle
Copy BRUN45.EXE to the folder where you are executing the program or, if

you

Post by Mort Middleman

Post by RipVanWinkle
prefer, anywhere else on your path.

Post by Mort Middleman
I recently installed a new system running Windows XP Home Edition. I
started the process of bringing my Quick Basic 4.5 programs over. In
my test, I brought up the command prompt and entered the path for the
compiled program - c:\basic\(program name).exe. A message appeared in
The program had been compiled using the runtime option (brun45.exe). I
entered that path - c:\qb45\brun45.exe and the same message appeared
again. I also tried entering c:\qb45\brun45.lib and got the same
result.
When running Quick Basic programs on my old system I did not have to
enter the run-time module path.
Using my old computer, I recompiled the program without the run-time
option, which produces an exe file about four times the size of the
exe file used with the run-time module. I ported this exe file over to
the new system and it ran successfully. But I really don't want to
have to recompile all of these programs, (there are loads of them,)
Any assistance offered would be greatly appreciated. Please respond
here - I am using a false address on all news group postings, as I
think my real address was harvested by the worm hackers and I am
receiving lots of fake e-mail purporting to be from Microsoft,
Returned Mail, etc.

_______________________________________________________________________________
Posted Via Uncensored-News.Com - Accounts Starting At $6.95 - http://www.uncensored-news.com
<><><><><><><> The Worlds Uncensored News Source <><><><><><><><>

[Paul O. BARTLETT]

On Wed, 15 Oct 2003, Mort Middleman wrote:

[concerning compiling to a standalone executable without use of
BRUN45.EXE:"]

Post by Mort Middleman
I have already tried your suggested method and it works. But the .exe
files are much larger than those compiled with brun45.exe. [...]

This is normal and to be expected. When you generate an executable
to use BRUN45.EXE, the latter must be available to the running program.
Many utility routines and functions are included in BRUN45.EXE, so they
do not have to be part of the compiled code. On the other hand, if you
compile with the /O switch, all the necessary functions and subroutines
must be taken from the BCOM45.LIB library at link time and *included*
in the completely standalone executable. Consequently, it necessarily
will have to be larger. Nothing exotic about that. Nothing is wrong.
(This is all going from memory, as it has been a while since I have
used QB45. Others please correct any errors of my faulty memory.)

[Back2Dos]

Yeah i know what your problem is... I just mucked around with compiling qb
programs requiring brun45.exe

The brun45.exe file cannot be specified in the prompt - it just doesnt work.

I think if you just specify an executable from "Run..." it defaults the
working directory to C:\DOCUMENTS AND SETTINGS\[USERNAME] in Windows XP.

To get your programs to work, make sure brun45.exe is in the the above
directory, and then when you start your programs, they will look for the
brun45.exe in that directory.

If this doesnt work then try putting the brun45.exe file in the folder with
the executables and making sure that when you run these executables that the
working directory is the one with brun45.exe in it.

Hope this helps =)

Post by Paul O. BARTLETT
[concerning compiling to a standalone executable without use of
BRUN45.EXE:"]

Post by Mort Middleman
I have already tried your suggested method and it works. But the .exe
files are much larger than those compiled with brun45.exe. [...]

This is normal and to be expected. When you generate an executable
to use BRUN45.EXE, the latter must be available to the running program.
Many utility routines and functions are included in BRUN45.EXE, so they
do not have to be part of the compiled code. On the other hand, if you
compile with the /O switch, all the necessary functions and subroutines
must be taken from the BCOM45.LIB library at link time and *included*
in the completely standalone executable. Consequently, it necessarily
will have to be larger. Nothing exotic about that. Nothing is wrong.
(This is all going from memory, as it has been a while since I have
used QB45. Others please correct any errors of my faulty memory.)
--
Paul Bartlett
bartlett at smart.net
PGP key info in message headers