The Following Files Are Included in the Lvwutil32.Zip File

The following files are included in the lvwutil32.zip file:

README.DOC(this document)

MANUAL.DOC(explanations of the VIs)

WINUTIL.LLB(VI Library)

WINEVENT.LLB(VI Library)

WINKEY.LLB(VI Library)

WINNET.LLB(VI Library)*New!

WINSYS.LLB(VI Library)

LVWUTIL32.DLL(32-bit Windows DLL used by the VI libraries)

Documentation is saved in Word for Windows 6.0 format.

VI Libraries are saved in LabVIEW 4.0.

Contents of the Libraries

winutil.llbWindow Management VIs

Window Refnum (control)

Not a Window Refnum

Get Window Refnum.vi

Get Window Name.vi

Get Window Rectangle.vi

Minimize Window.vi

Maximize Window.vi

Resize Window.vi

Restore Window.vi

Move Window.vi

Rename Window.vi

Hide Window.vi

Show Window.vi

Flash Title Bar.vi

Move Window to Top.vi

Make Window Always on Top.vi

Revoke Window Always on Top.vi

Move Window to Bottom.vi

winevent.llb Windows Interaction VIs

FileMan Open File.vi

FileMan Print File.vi

System Exec+.vi

Run Application.vi

Quit Application.vi

Start Windows Screen Saver.vi

Get Windows Task List.vi

Show Windows Task List.vi

Exit Windows.vi

Call WinHelp.vi

Message Window Dialog Box w/ Sound.vi

winsys.llb Windows System Utility VIs

Get Cursor Position.vi

System Information.vi

Get Screen Size.vi

Get System Path.vi

Get Windows Path.vi

Screen Saver Control.vi

WINNET.LLBWindows Networking VIs (NEW FOR WIN32)

Disconnect Network Resource.vi

Add Network Resource.vi

winkey.llb Windows Keyboard Filter VIs (NOT FUNCTIONAL IN WIN32)

Install Keyboard Filter.vi

Remove Keyboard Filter.vi

After unzipping the files:

You should place LVWUTIL32.DLL in the same directory as the LLBs - namely user.lib. In any event, place the DLL in a directory that appears in LabVIEW's VI Search Path or the PATH statement in your AUTOEXEC.BAT file (i.e. the PATH environment variable). This will make the VIs easier to use. If you do not place LVWUTIL32.DLL in a directory that appears in one of these items, you may receive a dialog prompting you to locate a DLL when opening the VIs. This is because the DLL could not be found. If this happens, and you find the DLL via the dialog box, the change in location of the DLL will not be saved with the VI unless you change the configuration of the Call Library Function icon(s) appearing on the diagram yourself and save the changes to the VI. You will then need to do this for every Call Library Function icon in all of these VIs -- which could be tedious. It is easiest to place the DLL in a path in your LabVIEW VI Search Path, or in a directory appearing in the PATH environment variable.

Adding a path to LabVIEW's VI Search Path:

Adding a path to LabVIEW's VI Search Path is simple. First, start LabVIEW. Then, select Preferences... from the Edit menu. In the dialog that appears, select the Paths preference. You will see another menu ring from which you need to select VI Search Path. Make sure the 'Use default' box does not have an X in it. Then, use the Browse... option to select the path, or type the path to the directory in which you are storing the DLL into the field next to the Browse... button. For example, if you choose to store the DLL in the directory C:\LABVIEW, then type this into the text box. You should then choose where you want to place this path in the list and use the Insert Before or Insert After button to place the path into the list. Consult the online help (Path Preferences topic) or LabVIEW User Manual for Windows for more information.

To place these VIs in the LabVIEW Functions menu:

Place the libraries in the LabVIEW directory called USER.LIB. The next time you start LabVIEW, you will see the following new subpalettes in the User Libraries palette:

Windows Interaction VIs

Windows Keyboard Filter VIs

Windows Networking VIs

Windows System Utility VIs

Window Management VIs

You will also a new item in the User Controls palette:

Window Ctrls

If your machine crashes when using these VIs:

These VIs have been tested, but not rigorously. They have not been formally adopted as a part of a future LabVIEW release, but are under consideration. They have only been superficially tested in Windows 95 and Windows NT 3.51 using LabVIEW 4.0. If the VIs crash, contact me directly via email or voice mail, with a detailed description of which VIs you were using, what you were using them for, and which applications you were running at the time. If you have access to our ftp site, you may want to send the VIs to the /incoming directory and tell me the name of the file(s).

If you have questions or comments about these VIs:

Contact me directly via email or voice mail. Please restrict your questions and comments to this group of VIs. As I am currently under some very pressing development deadlines, I may not be able to provide immediate help or solutions, but will try. Other questions not pertaining directly with these VIs should be handled through standard support procedures. You can contact me at:

Steve Orth

Software Engineer

National Instruments

email: