Common Problems with Application Builder 5.1

Common Problems with Application Builder 5.1

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."
I am using VI Server to dynamically load VIs but I receive errors that the subVI is not in the correct state.
I am using DataSocket, NI Reports, and/or 3D Graphs and my executable runs fine on the development machine but gives errors on the target machine.
My large executable displays a window with the VIs that that it is loading, but I would like it to remain silent.
I am creating an application for distribution via diskette, but the run-time engine is not included.
I cannot save my installer directly to my diskettes.
Although I included support files on a diskette distribution, they still appear uncompressed on the hard drive.
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 are included by default, but if you need them, they may be copied from the LabVIEW root 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. Also, verify that any necessary ActiveX controls have been installed.
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."
Occassionally LabVIEW can get confused about mdia32.dll. If it simply cannot find it, locate mdia32.dll with Start » Find and select it when the 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.

I am using VI Server to dynamically load VIs but I receive errors that the subVI is not in the correct state.
Dynamic VIs should be included using the "Add Dynamic VI" button rather than the "Add Top Level VI" button.

I am using DataSocket, NI Reports, and/or 3D Graphs and my executable runs fine on the development machine but gives errors on the target machine.
Make sure to install DataSocket, NI Reports, and/or 3D Graphs on the remote machine, as they are not part of the executable. An easy way to do this is to create an installer, choose "Advanced", and select the appropriate installataions from the Additional Installations listbox.

My large executable displays a window with the VIs that it is loading, but I would like it to remain silent.
The solution is to load VIs dynamically using VI Server commands.

I am creating an application for distribution via diskette, but the run-time engine is not included.
Unfortunately, the run-time engine is included in its own directory (named "Run-Time Engine" under the "Disks" directory). This will fit on two 1.4 MB diskettes; copy everything but "data2.cab" to one diskette and copy "data2.cab" to the second diskette.

I cannot save my installer directly to my diskettes.
Application Builder saves only to the hard drive. You will need to copy the files from the "Disks" directory: "setup.exe" and "data.001" to the first diskette, and "data.00n" to subsequent disks (where "n" is the number of the diskette).

Although I included support files on a diskette distribution, they still appear uncompressed on the hard drive.
There are actually two copies: one is the uncompressed version and one is the compressed version in the "Disks" directory. The setup program will uncompress the support files on the target machine.

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 the C:\winnt\system32\user32.dll (or the C:\windows\system\user32.dll for Windows 98/95 users).