<div>
Thats got to be it. &nbsp;But they do all include that 32 bit 16 bit like #IF WIN16 THEN verification logic (pasted them in out of some other source). &nbsp; Yes of course VB5 does not EVER expect to run under 16 bit sho why leave that code in there even. &nbsp;<br />

</div>


Thats got to be it.  But they do all include that 32 bit 16 bit like #IF WIN16 THEN verification logic (pasted them in out of some other source).   Yes of course VB5 does not EVER expect to run under 16 bit sho why leave that code in there even.  


<div>
Hi!<br />
<br />
This may be a wild ques but:<br />
<br />
You must have read some DLL code and then used it in your exe project.<br />
In DLL is possible to have ability to run on both platforms<br />
and recon these automaticly, then 16bit applicaliton may use<br />
same dll than 32bit version has. <br />
<br />
<br />
Matti<br />
<br />

</div>


Hi!

This may be a wild ques but:

You must have read some DLL code and then used it in your exe project.
In DLL is possible to have ability to run on both platforms
and recon these automaticly, then 16bit applicaliton may use
same dll than 32bit version has.


Matti



<div>
First answer nailed it perfectly. &nbsp;I removed the conditional #WIN16 If statement and declares and away the prompts went. &nbsp;Never caused any problem because the IF WIN16 test failed and the code would never execute at runtime of course.<br />
<br />
Thanks<br />

</div>


First answer nailed it perfectly.  I removed the conditional #WIN16 If statement and declares and away the prompts went.  Never caused any problem because the IF WIN16 test failed and the code would never execute at runtime of course.

Thanks


<div>
<div class="content wysiwyg-content">
It asks during the build of the setup of an application for LOCATE GDI and then LOCATE USER. &nbsp;Asks each question about six times then gives up and builds an apparently perfectly good setup.exe group of files. &nbsp;What are those prompts looking for and why do they not appear to matter?
</div>
</div>


It asks during the build of the setup of an application for LOCATE GDI and then LOCATE USER.  Asks each question about six times then gives up and builds an apparently perfectly good setup.exe group of files.  What are those prompts looking for and why do they not appear to matter?

Setup Wizard asking odd question.  Ideas?

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.