Common Problems with Application Builder 5.0 (or Earlier)
- Application Builder runs fine on the development machine but crashes on the target machine.
- Application Builder either cannot find mdia32.dll or it crashes with an error message about "LabVIEW caused invalid page fault
Module MDIA32.dll@0137:04086083."
- My large executable displays a window with the VIs that
it is loading, but I would like it to remain silent.
- I installed Application Builder but it does not show up
in the Project menu.
- The installer crashes on the remote machine.
- I would like to use my own icon for my executable,
instead of the LabVIEW icon.
- I would like to have my executable shutdown Windows
when it exits.
- Application Builder runs fine on the development machine but crashes on the target machine.
This could be caused by several problems.
1) Make sure that the daqdrv file (for DAQ) and/or the serpdrv file (for
serial communication) is located in the same directory as the executable.
These files can be copied directly from the LabVIEW directory.
2) If you are using our hardware drivers (DAQ, GPIB, VXI), make sure that
you have installed the drivers on the remote machine with LabVIEW support.
3) Make sure that the executable is for the same operating system that
the development system is using.
4) Make sure that you are using the same version of Application Builder as
LabVIEW. Please note that if you have LabVIEW 5.0.1 and bought Application
Builder after you upgraded, you will need to re-install the upgrade. If you
have Application Builder 4.x with LabVIEW 5.0.x, you will need to apply for
the free Application Builder upgrade.
5) Check that there is adaquate free space on the driver where the temp file
is stored.
6) Make sure that the TMP and TEMP variables are define and point to a valid
directory.
-
Application Builder either cannot find mdia32.dll or it crashes
with an error message about "LabVIEW caused invalid page fault Module
MDIA32.dll@0137:04086083."
During the upgrade from LabVIEW 5.0 to 5.0.1, LabVIEW can get
confused about the mdia32.dll. If it cannot find it, you can manually locate the mdia32.dll
with Start >> Find. Then, select the file when the application builder dialog box appears asking for it.
If Application Builder is crashing, make sure that there is only one copy
of mdia32.dll. Delete any duplicates that Start >> Find locates.
- My large executable displays a window with the VIs that it is
loading, but I would like it to remain silent.
You will need to load VIs dynamically using VI Server commands.
- I installed Application Builder but it does not show up in the
Project menu.
Either Application Builder was installed into the wrong directory
(make sure that the base directory is the LabVIEW root directory) or the
version of Application Builder is different than that of LabVIEW--you may
need to apply for the free Application Builder upgrade.
- The installer crashes on the remote machine.
Follow the steps for creating an executable and
the steps for creating a distribution kit exactly.
If you do not follow every step exactly when creating the executable, it is possible
that the executable could be created incorrectly.
- I would like to use my own icon for my executable, instead of the
LabVIEW icon.
You will need to use the Icon Editor from Measurement Studio or a third-party resource editor to change the icon. However, Application Builder for LabVIEW 5.1 allows you to specify
any .ico file for the icon.
- I would like to have my executable shutdown Windows when it exits.
If you have Windows NT 4.0, you can set your executable to be the
user's shell, so that when they exit the executable, they are logged off. Set
the Registry entry
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Winlogon
\Shell
to app.exe. Alternatively, you could call the
ExitWindowsEx command from C:\winnt\system32\user32.dll
(or the C:\windows\system\user32.dll for Windows 98/95 users).
|
|
