README.TXT Release Notes for Microsoft (R) Visual Basic (TM) Version 1.00 -- Working Model (C) Copyright Microsoft Corporation, 1991 You may make an unlimited number of copies of this program for your use and for distribution to others. However, you may not modify, reverse compile, or disassemble the program or create any derivative works based in whole or in part on the program, or otherwise use the program, or any portion thereof, for any commercial purpose whatsoever, without the express permission of Microsoft Corporation. Because this is a demo program, Microsoft makes no warranties concerning its use or operation. You accept this program "as is," without warranties of any kind. -=-=-=- Contents =========================================================================== Part Description ---- ----------- 1 Software Installation Information 2 Notes for Tutorial 3 Miscellaneous Notes and Tips Part 1: Software Installation Information =========================================================================== Installation ------------ If you already have Microsoft Windows 3.0 installed: 1. Insert Disk 1 with Setup in Drive A (or drive B). 2. From the Program Manager, choose the Run command from the File menu. 3. Type "a:setup" (or "b:setup") and press Enter. 4. When Setup is complete, double-click the "Try Visual Basic" icon. If you do not have Microsoft Windows 3.0 installed: [NOTE: This demonstration version of Windows requires a color EGA or VGA display. In order to use this Working Model on other systems, Windows 3.0 must already be installed.] 1. Insert Disk 1 with Setup in Drive A (or drive B). 2. Type "a:setup" (or "b:setup") at the DOS prompt and press Enter. 3. Follow the program's directions until Setup is complete. 4. If Setup instructs you to reboot the computer, do so. 5. At the DOS prompt, type "cd\windemo" (or substitute the directory name you specified during Setup) and press Enter, then type "windemo" and press Enter again to start Windows. 6. Once Windows is started, double-click the "Try Visual Basic" icon. RESTORE.TXT on Disk 1 contains information on removing the Working Model software from your system after you have finished using it. EXPAND.EXE ---------- Most of the files on these disks are compressed and must be expanded before they can be used. For Visual Basic to work properly, you must install the files using SETUP.EXE, or use the EXPAND.EXE utility on Disk 1 instead of copying files directly from the disks. Command syntax for EXPAND.EXE is: EXPAND [source] [target] where "source" is the full pathname of the file to be decompressed, and "target" specifies the directory where you wish to place the decompressed file. Wildcard characters (* and ?) are accepted. Part 2: Notes for Tutorial =========================================================================== Tutorial Screen Conflicts ------------------------- Some Windows programs that run in the background and automatically perform some action on the screen may behave unpredictably when the Visual Basic Tutorial is running. For this reason, we recommend that you turn off or unload screen savers and background clock-type programs before running the Tutorial. Part 3: Miscellaneous Notes and Tips =========================================================================== Running WINDEMO.EXE with Expanded Memory ---------------------------------------- Expanded memory managers such as EMM386 or 386MAX must be disabled to run the demonstration version of Windows (WINDEMO.EXE) included in the Visual Basic Working Model package. Running this demo with a LAN Manager 2.0 network ------------------------------------------------ If you are running LAN Manager 2.0 or Novell networks with the netpopup service and you do not already have Windows 3.0 installed, you may have problems running the demonstration version of Windows 3.0 included in this package. To correct this, turn off the netpopup service. To do this with a LAN Manager 2.0 network, type the following from DOS: NET PAUSE NETPOPUP To do this with a Novell network, type the following from DOS: CASTOFF ALL Deleting or Renaming Controls ----------------------------- When you delete or rename a control for which you have written event procedures, the event procedures themselves are not deleted. All such event procedures become general procedures with their names preserved. If you create a new control of the same name, those general procedures will once again become attached to that control. If you rename those general procedures to match the name of an existing control, they will become attached to that control. Note that while the event procedures are restored, the value of any properties you previously assigned to the deleted control are lost. Displaying Modal Forms from the Immediate Window ------------------------------------------------ Forms cannot be displayed modally using the Show method in the Immediate window. You can, however, call a procedure from the Immediate window which contains a Show method to display a modal form. There are no restrictions on the display of non-modal forms. Design-Time Dynamic Data Exchange (DDE) --------------------------------------- If you establish a design-time DDE link (either as a client or as a server) between another application and a Visual Basic text box, changing any property which causes the text box to be destroyed and recreated will terminate the link. For example, changing a text box from single line to multiline terminates a design-time DDE link; the Visual Basic developer must re-establish the link if it's still needed. Terminating DDE Links During Form_Unload ---------------------------------------- You must terminate all DDE links before you close a form that contains any controls involved in the link. Submenu Visibility ------------------ If you have a menu with submenu items, at least one submenu item must always be visible, i.e., the Visible property must be set to True (-1). Calling DLL Routines by Ordinal Number -------------------------------------- Some DLLs export their routines by ordinal number rather than by name. To call one of these DLL routines, you must declare it with an alias string that includes the number sign character (#) followed by the ordinal number. For example, to declare the routine with ordinal number 234: Declare Sub AnyRoutine Lib "AnyDLL" Alias "#234" (ByVal Var As Long) Default WindowState ------------------- Whatever WindowState (minimized, restored, or maximized) a form is in when Visual Basic goes to Run mode may become the new default WindowState. If you want your forms to retain a specific WindowState you must either close the form before running the application or explicitly set the WindowState in the Form_Load event. This last technique, however, prevents the application from being run in a state different from the state explicitly set. Custom Controls --------------- You must remove all instances of a custom control from project forms before removing the custom control file from the project. If you're replacing or updating a custom control file with a newer version, you should copy the new version over the old version and reload the entire project. You should not remove the old version (using the Remove File command on the File menu) and then add the new version (using the Add File command). --------------------------------------------------------------------------- The original source of this Visual Basic Working Model was: -------- FUTURETRON ONLINE SERVICES The World's Largest Windows BBS - First distributed on the 28th of June 1991 - If you have any questions concerning this demo please contact us at 114 Richmond Street Toronto Canada M5C 1P1 FUTURETRON Toronto! (416) 868-1808 Voice 9am-5pm EST We do Windows! (and OS/Too!) (416) 868-6593 V.32/V.42BIS/HST MultiCity / 11 Nodes / 3 Gigs (416) 868-6830 V.32/V.42BIS PCBoard / City2City Host (416) 868-6898 Telebit TrailBlazer --END----------------------------------------------------------------------