VA Smalltalk Readme


Welcome to VA Smalltalk Version 7.5.2

  Welcome to VA Smalltalk 7.5.2. VA Smalltalk enables software developers to create highly 
  portable, scaleable, multi-tier business applications using object-oriented technology. 
  VA Smalltalk allows for incremental and rapid development of new Smalltalk applications. 
  Developers can build and deploy enterprise Web service solutions for dynamic e-business 
  using VA Smalltalk.

  This is a maintenance release that provides defect corrections, some minor enhancements,
  and additions to the set of supported platforms.

Late-breaking news, technical tips, and product updates

  Please refer to the Instantiations Smalltalk web page for technical information, including 
  tips, and product updates made after this product release. The web page includes information 
  about what's included in the release,  and how to contact us as well as hints and tips for 
  using and deploying VA Smalltalk. 

  You can download the latest product updates from the Instantiations Smalltalk web site.

Version 7.5.2 files and installation

Distribution files

  Each supported VA Smalltalk platform has three downloadable components:

  * Client - The Client component contains the VA Smalltalk development IDE. You will need to
    install a client on each machine on which you wish to develop VA Smalltalk applications.

    You must download and install the correct client package for your workstation operating

  * Manager — The Manager component contains the VA Smalltalk source code repository ('manager')
    file and the EMSRV code used to access the repository file in a team environment. The manager
    is used in conjunction with the workstation client IDE.  One code repository can support many
    clients concurrently. Therefore you will only need to install the manager one time on a
    suitable server machine.

    You must download and install the correct manager package for your server machine's operating
    system.  It does not have to match the client operating system.  A Linux manager install, for
    example, can concurrently service Windows, AIX, Solaris and Linux clients. The same is true
    for all of the other manager installs.

  * Server Runtime — This is the runtime support needed for deploying Smalltalk applications
    developed using VA Smalltalk. There is no formal install program for Server Runtime. You
    simply use unzip to unpack the runtime files and add your packaged Smalltalk application
    into the resulting directory structure.

    You must download and unpack the correct Server Runtime package for your workstation
    operating system.

  If you do not already have a suitable unzip program, then you can download a no-charge unzip
  program such as the Info-ZIP program ( Please note that
  gunzip will not work with the VA *.zip files. The VA *.zip files are multi-file archives;
  gunzip is only designed to handle single compressed files. 

  You must unzip the client and manager zips on the same kind of machine that you intend to
  install them on.  Do not, for example, unzip a Solaris client install onto a Windows machine.

Installing VA Smalltalk

  Complete install instructions, such as how to set up EMSRV, can be found in the Installation
  Guide. The Installation Guide is in the doc directory of the unzipped client or manager
  install directory tree (it is the same document in both zip files): 
   * on Windows, open a browser on cd_c\doc\instgd.htm or cd_m\doc\instgd.htm
   * on Unix, open a browser on cd_c/doc/instgd.htm or cd_m/doc/instgd.htm 

  The Installation Guide is also available at Instantiation's Smalltalk website.
  To install VA Smalltalk, follow the instructions for your specific platform. 
  We recommend you install the manager before you install the client.

  If you are new to Smalltalk, we recommend you install the client with the on-line 
  documentation. Once you have installed the manager and the client, refer to the 
  Installation Guide for further instructions on how to configure your environment before
  you launch VA Smalltalk.
Pre-installation steps (Windows)
  Before installing VA Smalltalk, follow these steps: 
   1. If a previous version of VA Smalltalk is installed, stop any running VA Smalltalk
      images before performing a client install.

   2. If a previous version of VA Smalltalk is installed, stop EMSRV before performing a
      manager install.
Pre-installation steps (Unix)
  Before installing VA Smalltalk, follow these steps: 
   1. If a previous version of VA Smalltalk is installed, stop any running VA Smalltalk
      images before performing a client install.

   2. If a previous version of VA Smalltalk is installed, stop EMSRV before performing a
      manager install. 

   3. Some additional libraries must be installed when running on 64-bit Ubuntu.

      The Ubuntu (Debian) system dynamic library linker has been modified so that when a
      32-bit application requests access to a library, Ubuntu provides the 32-bit version
      of the library if it is available instead of the normal 64-bit version that the
      native applications require.  This works if the 'ia32' packages, which provide a
      sub-set of standard Ubuntu libraries compiled in 32-bit mode, have been installed. 

      To install the ia32-libs package use the command:
        sudo aptitude install ia32-libs
      This creates a document tree in the /emul/ia32-linux directory. By default this
      supports only console applications, basic X applications and GTK based applications.

   4. The install of VA Smalltalk must be done as root -- you can either change to be root
      now or use the 'sudo' command (available on most Unix platforms) to perform the

   5. Create the /usr/local/VASmalltalk/7.5 directory if it doesn't already exist.

   6. The installation process relies on the presence of 'csh' in the /bin directory. Most
      supported platforms have csh. However, some commonly used versions of Linux do not.

      When installing VA Smalltalk on Unix, if csh is missing from the /bin directory,
      the installer may display an error dialog the message "Runtime Error -- couldn't
      open file with UnixProcess".  However, on some platforms the installer only writes
      the error information into /tmp/vastinstall-output and exits.  

      There are two workarounds for this problem:  

       * Install csh in the /bin directory    
       * Create a symbolic link linking the bash shell as csh; bash is sufficiently
         similar to csh for the setup program to function properly:
           ln -s /bin/bash /bin/csh
Installation difficulties (Windows)
  * The default installation directory is C:\Program Files\Instantiations\VA Smalltalk\7.5\
    (or C:\Program Files(x86)\Instantiations\VA Smalltalk\7.5\ on 64-bit Windows).
    If the installer will not allow you to specify the installation directory for the 
    manager or client, this may be because you already have the current version of
    the manager and/or client installed.  The installer detects whether VA Smalltalk has
    already been installed and will not overwrite the installed version.

    Information about the installation directory is stored in the registry. To determine
    the installation directory of a previous build, start regedit to view the registry. Go to 
    HKEY_LOCAL_MACHINE > Software > Instantiations > VA Smalltalk. 
    The Client, Manager, and Help entries record the name of the respective installation
    directories as well as other relevant information about the installation.

    Based on the values of these entries, you may need to contact your network administrator
    for assistance.

  * The progress of the install is kept in log files. Clues to failed installs can be found
    in these logs. These files your TEMP directory. To determine the location of the TEMP
    directory, issue a "set temp" command (minus quotes) from a command line window.

    The following logs are created:  

     * Client install:  client.nst, act_c.txt
     * Client uninstall:  act_c_u.txt
     * Manager install:  manager.nst, act_m.txt
     * Manager uninstall:  act_m_u.txt 
Installation difficulties (Unix)
  * If the installer will not allow you to specify the installation directory for the 
    manager or client, this may be because you already have the manager/client installed.
    The installer detects whether VA Smalltalk has already been installed and reinstalls in a 
    similar manner (e.g. If you have been running the Team environment you may not have
    the necessary privileges to replace the code repository).

  * The progress of the install is kept in log files. Clues to failed installs can be found
    in the logs. These files are located in the /tmp directory.
     * Client install: client.nst, act_c.txt, vast-Install.output
     * Manager install: manager.nst, act_m.txt, vast-install.output 
     * Client uninstall: act_c_u.txt
     * Manager uninstall: act_m_u.txt

    Note that each time you run ./setup it will overwrite the vast-install.output file if it
Post-installation steps (Windows Vista)
  Windows Vista provides a new security component called User Account Control (UAC).
  UAC enables all users to perform common tasks as non-administrators, called standard
  users in Windows Vista, and as administrators when necessary.  A standard user
  account is the same as a user account in Windows XP.  UAC provides an increased
  level of security in Windows Vista compared to previous versions of Windows, but it
  also imposes some limitations on the location and usage of files.

  The following discussion assumes that your Windows Vista system is running with UAC
  enabled (as recommended by Microsoft).


  Because the VA Smalltalk Client and VA Smalltalk Manager Installer can install files
  in directories that are shared by all users on a system, these setup programs must
  run in administrator mode.


  If you choose the default location (C:\Program Files\Instantiations\VA Smalltalk\7.5)
  when doing a Manager install, you will need to move the code repository file
  C:\Program Files\Instantiations\VA Smalltalk\7.5\manager\mgr75.dat to a different
  location that is not in a UAC-protected directory.  For example, you could move it
  to C:\Instantiations\VA Smalltalk\7.5\manager\mgr75.dat.


  If you choose the default location (C:\Program Files\Instantiations\VA Smalltalk\7.5)
  when doing a Client install, you will need to move the files in the image directory
  C:\Program Files\Instantiations\VA Smalltalk\7.5\image750 to a different
  location that is not in a UAC-protected directory.  The best location for these files
  is in your user directory tree.  For example, you could move them to
  C:\Users\<yourUserName>\Documents\Instantiations\VA Smalltalk\7.5.  You will need
  to change the properties of the All Programs shortcut named VA Smalltalk Client 7.5 ->
  Development Image 7.5 so that the 'Start in:' field holds the name of the directory
  that you created above. For example, %USERPROFILE%\Documents\Instantiations\VA Smalltalk\7.5.

  Windows Themes

  You can enable Windows Themes for your Smalltalk GUIs by editing the manifest file
  associated with the VA Smalltalk executable (for example, abt.exe.manifest) and
  removing the comment markers (<!-- and -->) that surround the <dependency> clause.  
Post-installation steps (Unix)
  * Each user must specify a working directory to hold their working images when
    configuring their installation. The tool used is vasetup75.

  * The default configuration is for using the team environment with EMSRV (you  
    are NOT prompted to choose a different option during the installation).  If you wish to
    work in standalone mode on UNIX:

     1. Edit abt.ini and change the entry ServerAddress so that there are no 
        characters or blanks after the "=";  i.e. "ServerAddress=".

     2. Change the ownership of the manager so that your account has read/write 
        privileges.  The default is for only the root account to have read/write privileges
        which is the correct setup for EMSRV and the team environment.

  * On Linux, the X-Windows directory structure may need to be corrected.

    VA Smalltalk expects to have its X-lib files in the /usr/X11R6/lib/X11 directory structure.
    Most newer Linux distributions place their X-lib files under /usr/share/X11.  In this case,
    VA Smalltalk will not be able to find the X-Windows files. Linking the structure VA Smalltalk
    expects to the one actually shipped will make the X-lib files available to VA Smalltalk.
    The following commands must be issued with super user privileges.

     1. Determine if the path /usr/X11R6/lib/X11 exists; if not, use the mkdir command to create
        the full path if it does not exist.
     2. Determine if the /usr/X11R6/lib/X11/XKeysymDB file exists; if not, create a symbolic
        link using the following commands: 
          cd /usr/X11R6/lib/X11 
          ln -s /usr/share/X11/XKeysymDB 

    At this point you will be able to enter characters. Characters common across many (European)
    languages will properly display even if you are using a UTF-8 locale. However, characters with
    keysym (ASCII) values over 127, such as the copyright (©) character, will not display correctly
    under the UTF-8 locale. 

  * On Linux, the default locale may be UTF-8 which is not supported by VA Smalltalk.  If this is
    the default locale, you will experience problems displaying and entering some characters
    specific to some (European) languages.  The particular characters you will have problems with
    are characters with keysym (ASCII) values over 127, such as the umlauted vowels in German and
    the copyright (©) character.
    When VA Smalltalk detects that the locale is an unsupported one, it will log the situation to
    the console. VA Smalltalk will use the C locale in this case.

    On some versions of Linux we have found that, while the default locale may not be supported by
    VA Smalltalk, several supported locales are shipped with the operating system. On other versions,
    no suitable locale exists. This article covers both situations.

    In order to get characters in the upper range of the ASCII character set to display correctly,
    you must change the locale as outlined below.

     1. Determine whether or not a suitable iso88591 or iso885915 locale exists (e.g. en_US.iso88591 
        or de_DE.iso885915).  The command 'locale -a' will list available locales. Locales may also
        be in a compressed-format file named locale-archive. The command 'localedef -list-archive'
        will list locales in the archive file.  If a suitable locale exists, skip to step 3.

     2. If a suitable locale does not exist, one must be generated. There are two commands to
        generate a locale: locale-gen and localedef.  Locale-gen is not available on all platforms;
        it is available on Ubuntu. Refer to the man pages for information on using the locale-gen
        and localedef commands. Follow the instructions to generate your locale.

         * Ubuntu 6 and 7 ship with UTF-8 locales only. ISO 8859 locales must be generated
           on this platform before international characters will display properly.  To
           create, for example, an en_US.iso885915 locale using the locale-gen command:
             sudo locale-gen en_US.ISO-8859-15

           You should see the following output:
             Generating locales...
               en_US.ISO-8859-15... done
             Generation complete. 

           The locale is written to the directory /usr/lib/locale/en_US.iso885915 as can be seen by:
             ls /usr/lib/locale/en_US.iso885915
               LC_CTYPE    LC_MESSAGES        LC_NUMERIC   LC_TIME

           Once the locale directory is generated, it will need to be copied to /usr/share/X11/locale
           unless it has been generated and added to locale-archive using the localedef command. The
           copy must be done with super user privileges.
             cd /usr/share/X11/locale
             sudo cp -r /usr/lib/locale/en_US.iso885915 en_US.iso8885915 
           where en_US.iso885915 is the name of the locale to be used with VA Smalltalk. 

         * SUSE Enterprise 10 and openSUSE 10.1 ship with several locales suitable for VA Smalltalk.

         * Red Hat 5 Enterprise ships with several locales suitable for VA Smalltalk.

     3. A link between the X-Windows structure shipped with Linux and the structure VA Smalltalk
        expects may need to be created in order to make the locale available to VA Smalltalk. To
        do so (as super user):
          cd /usr/X11R6/lib/X11 
          ln -s /usr/share/X11/locale 

     4. Finally, the environment for the terminal in which you launch VA Smalltalk needs to be
        updated. Specifically, LANG environment variable must be set to the locale you chose or
        created (e.g., export LANG=en_US.iso885915).
    At this point your system should be properly configured to run VA Smalltalk and have characters
    with keysym values over 127 such as umlauts and the copyright symbol display properly when
    typing in text widgets. The console log should no longer contain warnings about the locale.

VA Smalltalk Migration Guide

  If you have a version of VisualAge Smalltalk installed, please 
  refer to the Migration Guide for important information before using VA 
  Smalltalk Version 7.5.2.  The Migration Guide can be installed with the VA 
  Smalltalk Client by selecting the "VA Smalltalk Documentation" feature. 

  As a starting point to migration, we recommend that you backup your existing repository
  then import the contents of the newly installed VA Smalltalk code repository into the
  existing repository.

Corrections and Enhancements

  This section lists the corrections and enhancements introduced by each release of
  the VA Smalltalk product.
Defects fixed in V7.0
	Case	Title
	-----	----------------------------------------------------------
	*****	Versioning/releasing owned parts in Organizer causes a walkback
	*****	Messages missing in AbtDirectoryPrompter
Defects fixed in V7.0.1
	Case	Title
	-----	----------------------------------------------------------
	 2493	Swapper mutation of AbtTimestamp fails 
	 3834	Broken link to ResHacker in Smalltalk User’s Guide
	 3885	AbtTimedWait is not threaded on Windows 
	 4702	AbtTimestamp wrong for dates earlier that 1901-01-01 
	 6168	User's Guide "Replacing required map" and "Exporting Components" missing punctuation
	 6204	Heterogeneous Details View Column 
	 6622	Missing documentation for 64-bit integer support
	 6851	Intermittent slowdown under heavy load on Unix
	 7156	Solaris includes extra .so files
	 7400	Database Guide is incorrect for Multi Row Query Example
	 7769	AbtPortableNotebookPageView broken for some users by V6.0.3
	 8225	IndexOutOfRange in WkTableWidget due to item deletion
	 8226	WkHierarchical listbox icons have gray background
	 8343	Sorting makes TableWidget items out of synch
	 9392	Scaling a transparent GIF causes it to lose transparency
	14316	AbtComboBox gives walkback when maxlength is set on Unix
	14317	AbtMQqm>>#terminate - dictionary concurrency problem - not thread-safe
	14608	Embedded Shell menubar item translateCoords wrong 
	14609	Integer>>#even method has poor performance 
	14610	HY024 returned on multi-row ODBC operations with DB2 
	14611	Block>>#critical should be categorized as API
	14612	FromDLL test in CgIconTests fails on Windows
	14613	Multiple examples fail due to bitmapPath being an array
	14615	Integer>>#bitAt:put: wrong
	14616	SciSocketManager>>#getHostName passes bad parameter
	14617	Error in implementation of AcoResourceManager active setting
	14618	UNIXProcesses class>>#setUpApplication has redundant toBeLoadedCode
	14619	Invalid characters in SCI trace filename
	14620	Support more than 2GB RAM on Windows
	14621	Inspector has focus on 'Bind to self' checkbox, not items in the list
	14622	Improve SCI trace output
	15002	Remove obsolete OS400 subapplications
Product enhancements in V7.0.1
  Support for Red Hat Linux 4.3
Defects fixed in V7.5
	Case	Title
	-----	----------------------------------------------------------
	16131	EtWindow>>#execLongOperation:message: behavior out of sync with method comment  
	20736	Browsing class hierarchy of TrailBlazer version of App Manager yields walkback  
	21889	(-2 reciprocal positive) should be false  
	22164	Oracle 8 cursors on Unix fails calling wrong API for binding a param name  
	24225	Cannot invoke stored procedures without parameters  
	24226	nullsOk is preset incorrectly for host variables  
	24227	implementsStoredProcs should be a class method  
	24228	Oracle RAW fields broken with 6.0.3 change  
	24852	Attempt to retry "browse implementors..." with no results  
	24917	.INI file [Help] content fixes  
	25014	Document Server writes extraneous log file -- fails on Vista  
	25123	XML local-sensitive number conversions  
	25334	Code page conversion fails on unix if passed same source an target
Product enhancements in V7.5
    Support for SUSE Enterprise 10 Linux, Windows Vista(32-bit) and Windows Themes. 
    VA Smalltalk complies with the Vista User Account Control requirements and 
    responds to themes.

    Database Support for new Oracle 10g features including LOB manipulation, 
    programmatic execution of SQL statements and expanded uses of stored procedures.

    The following tools and frameworks are shipped with the product:
    1.  ENVY QA
    2.  Refactoring Browser
    3.  SUnit framework and browser
    4.  Mastering ENVY Developer tools 

    Inclusion of an interactive web services example to assist the 
    uninitiated into the workings of the web services framework.

    Inclusion of updated icons with the development environment.

	Case	Title
	-----	----------------------------------------------------------
	 2095	Bring VA Smalltalk support current for Oracle 10g  
	 3670	Envy QA  
	 3674	Envy Extentions: Refactoring Browser  
	 3791	SUnit test framework and browser  
	16312	Web Services in 10 min example  
	16644	Windows Themes  
	18011	Windows Vista Tolerance  
	18014	Modernize IDE: update icons  
	18422	Test product on SUSE  
	21104	Documentation of Vast Unix requirements  
	23966	data type TIMESTAMP integrated into Oracle 10g  
	25060	Mastering Envy Developer  

Defects fixed in V7.5.1
	Case	Title
	-----	----------------------------------------------------------
	16118	VisualAge mentioned in the Composition Editor
	18238	GF/ST does not load easily    
	24659	widgetless AbtContainerDetailsView>>#selectColumn: sets selection incorrectly   
	24661	Attribute get/set not generated in a default category
	24662	Interface declarations not generated in a default category   
	25123	XML local-sensitive number conversions
	25416	CfsFileStream bug in the method #flush
	25787	Refactory Browser 
	26125	7.5 Packaged Image running as NT Service Issue
	26173	Broken link in Installation Guide
	26174	Bug in DateAndTime abtXmlFromTimeString: 
	26236	Code page conversion fails between 'UTF-8' and some iso code pages
	26257	Synchronize Versions of AbtCommonAppBldrEditorApp &AbtCommonAppBldrModelApp 
	26803	SST Ics missing
	27378	VASmalltalk 7.5 running out of GDI-Objects 
	28026	Bug in Behavior>>specialSelectorIndexFor: 
Product enhancements in V7.5.1
	Case	Title
	-----	----------------------------------------------------------
	26221	Consolidate EtToolsVendorExtensionsApp and VisualAgeVendorExtensionsApp  
	26976	Configuration Map Browser enhancement to lineup management   
	22060	Quick form support for DateAndTime
Defects fixed in V7.5.2
	Case	Title
	-----	----------------------------------------------------------
	 1963	readAppend stream appends are not at end of stream    
	11403	SSL memory leak    
	25634	GFST Resource Installed in Wrong Place    
	25635	GFST Help Not Found    
	25905	Convert gf/st help files to .chm format    
	28527	Loading 256 color icons on Windows is broken    
	29099	Eliminate obsolete abtexi40.dat import file    
	29520	AbtSampleCatalogClientUserInterface fails when removing last item from list    
	29652	Drop and immediately close system menu yields walkback when WkControls is loaded    
	29716	ClassDescription>>rebindVariablesIn:using: is broken    
	29908	Missing comments in Smalltalk memory verification methods    
	29925	Number>>abtAsInteger fails on some floats    
	30149	OLE Event deregistration broken    
	30209	Error adding configuration expression in ConfigMap Browser with MED loaded    
	30510	OleApplicationFrameworkBase has GUI dependencies
	30755	emadmin manifest incorrectly sets requestedExecutionLevel to 'requireAdministrator'
Product enhancements in V7.5.2
	Case	Title
	-----	----------------------------------------------------------
	16560	Transcript Help menu update
                 The VA Smalltalk Forum is now accessible directly from the Transcript Help menu
	18426	Make Solaris 10 a supported platform
	28164	Modifiable splash screen
 		 See 'Providing a customized splash screen' in the VA Smalltalk Base User's Guide
	28676	Add bindings for ProcessMemoryCountersEx Win32 API        
	28678	Add an additional editable converter example    
	30048	Update collection creation methods to enhance portability 
		 See 'Common collection protocols, Creating instances (class methods)' and 'Unique
		 collection protocol, String and DBString' in the VA Smalltalk Base Programmer's
	30264	Support Smalltalk on 64-bit systems
		 SUSE Enterprise 10 (64-bit), openSUSE 10.1 (32- and 64-bit), Red Hat Enterprise
                 Linux 5 (32- and 64-bit), Ubuntu 6 and 7 (32- and 64-bit), and Windows Vista
                 (64-bit) platforms are added to the list of supported platforms.  The complete
                 list of supported platforms can be found by following the "System Requirements"
                 link from     

Components and Features

  The following sections list some important information about some of the components and features. 
  For the latest product information, please refer to Instantiations Smalltalk web page.

Application Builder

On UNIX, "X Error: BadWindow" message appears for Slider part
  Each time the Slider part is repainted the "X Error: BadWindow (invalid Window parameter)"
  message is printed in the xterm window which VisualAge Smalltalk was launched.
  The Slider part still functions normally.
(7.0.1) AbtPortableNotebookPageView broken for some users by V6.0.3
  Migration consideration: In V6.0.3, code was changed in AbtPortableNotebookPageView
  so that invoking the aboutToBeSwitchedTo event was not deferred.  This aligned 
  its implementation with aboutToBeSwitchedFrom which is also not 
  deferred.  Before this change was made, if a user quickly clicked on 
  more than one notebook tabs which had associated events, the events 
  could be run out of order.  For example, if Page2 has both these events 
  connected, and if a user is on Page1 and rapidly clicks first on the 
  tab for Page2 and then on the tab for Page3, the events could be run in 
  the order switchFrom Page2, switchToPage2.  This is obviously incorrect 
  Unfortunately, some user applications depended on the deferral of 
  execution of the aboutToBeSwitchedTo event.  For example, it could be 
  used to set focus to a particular subpart of the notebook page when the 
  tab for the page was selected.  These application were broken by the 
  Since it is not possible to automatically satisfy the needs of both 
  sets of applications -- those that depend on execution deferral and 
  those that depend on no execution deferral, another solution is needed.
  One possible solution for these broken applications is to change their 
  implementation so that the aboutToBeSwitchedTo handler does the 
  deferral of execution itself if needed.  So a method that needs this 
  capability and that used to look like this:
  aboutToBeSwitchedTo: aComp
   aComp setFocus 
  should be rewritten as:
  aboutToBeSwitchedTo: aComp
   [aComp setFocus] abtDefer
  Another solution is to return the system's implementation to the old 
  (deferral of execution) behavior.  This can be done by changing the 
  the value of following line in the .INI file from false (6.0.3 
  behavior) to true (6.0.2 and previous behavior):
  [Version Compatibility]


(7.5.2) Modifiable splash screen
  Migration consideration: As of this release, the product splash bitmap is built into
  the Windows executable.  If you install over a previous release, you need to delete the
  abt.bmp file from the \bin directory so that the builtin splash will be used.
(7.5.1) Consolidate EtToolsVendorExtensionsApp and VisualAgeVendorExtensionsApp
  Migration consideration: The vendor extension applications were provided to allow
  add-on tool providers to extend the Smalltalk browser menus.  Historically, since they were
  not provided with the Smalltalk product itself, the vendor extension applications were
  included with each add-on tool.  This caused a problem since there were multiple incompatible 
  versions of the vendor extension applications available and included. 
  The newest version of the EtToolsVendorExtensionsApp has been included in the 
  ENVY/Image Development map and the latest version of the VisualAge VendorExtensionsApp 
  has been included in the VisualAge Development Environment map.  Add-on tool providers 
  should remove these applications from their distribution packages to ensure the vendor 
  extensions are not back-leveled. 
(7.5.1) Configuration Map Browser enhancement to lineup management
  Prior to this enhancement, the only support for reordering the required 
  maps lineup was to move selected maps to the beginning or the end of the lineup.  
  Now the Required Maps -> Move menu (and popup menu) provides 4 options -- 
    To First, 
    Down, and 
    To Last.  
  Up and Down move the selected maps up or down one position in the lineup.
(7.5) Windows theme support interferes with some testing tools
  In the past, VA Smalltalk instantiated several custom window classes to provide
  override functionality.  Some of these custom window classes interfered with Windows
  theme support.  Therefore, they were removed and only standard windows classes
  are now used.  The removed custom window classes are OSBUTTON (now BUTTON) and
  TEXTEDIT (now EDIT).  This change may cause problems with automated GUI testing
  tools (such as Mercury WinRunner) that depend on knowing the window class of
  widgets.  If you experience failures of automated tests due to this change, you
  will need to modify your tests. 
On MVS, INIs are optional for packaged applications. All other platforms, INIs are required for packaged applications
  On MVS, an .ini file is optional. On all other platforms, an .ini file is required. The .ini file 
  may have the same name and be in the same directory as your executable (on Unix, the executable is 
  es or esnx). The .ini file can also have the same name and be in the same directory as your .icx or 
  .ic file. 
  In addition, you can specify your .ini file as a command line parameter. For example, you can 
  launch your program by typing the following: 
    abt -imyapp.icx -ini:c:\any.ini
(7.0.1) Block>>#critical should be categorized as API
  The Block>>#critical method is commonly used to ensure single-threaded 
  execution of a section of code even though it is not categorized as API 
  and is not documented.  The following documentation is added and the 
  method is recategorized as CPM-API.
  The VA Smalltalk Base Programmer's Reference needs to be updated.  The 
  affected pages are:
  * 48, Block evaluation methods, Protocol synopsis, Block evaluation 
  critical Evaluates the receiver (a zero-argument block) and guarantees 
  that there will be no context switch while the receiver is being 
  evaluated.  Answers the result of the last statement to be evaluated.
(7.0.1) Support for more than 2GB memory on Windows
  The executables (abt, nodialog, esvio, abtntsir, and abtntsrv) are linked
  with the /LARGEADDRESSAWARE switch so that more than 2GB of memory can be
  be referenced if the Windows environment is setup properly to support such
  access.  For information on how to setup the Windows environment to support 
  this capability, see the MSDN article titled "4GT RAM Tuning"


  No additional information at this time.


Get schema function on Stored Procedure Specification Settings
  When using stored procedures with the new Oracle 8 database connection, the Get schema function on 
  the Stored Procedure Specification Settings view only works for procedures that are not contained 
  in packages. Users must manually define host variables for procedures that are contained in 
On Unix, running Database Features
  On Unix, if you are using database features and experience a core dump when exiting VA Smalltalk, 
  comment out the PlatformLibrary>>shutDown method. An alternative solution for your packaged 
  application is to execute the following code when exiting: 
    System primitiveExit
Oracle initialization mode can be changed without subclassing AbtOracle8DatabaseManager
  Prior to this fix, the only provided method for changing the Oracle initialization mode was to 
  create a subclass of AbtOracle8DatabaseManager in order to override the #userDefinedInitializeMode 
  method.  While this method is still available, it is now possible to change the default 
  initialization mode by setting a class variable. The provided method for doing this is 
  AbtOracle8DatabaseManager  class>>#defaultInitializeMode: . The shipped default value is 
  OCI_DEFAULT, which is unchanged from previous VA Smalltalk version.  See the comment in 
  AbtOracle8DatabaseManager class>>#defaultInitializeMode: for other possible values.
Prerequisite AbtRecordStructureApp in Database Applications
  Some database applications will need to add a prerequisite for the AbtRecordStructureApp 
  application. Applications that use Database Parts will not need to add this prerequisite because 
  the parts will include the AbtRecordStructureApp application. If an application manipulates 
  instances of any of the subclasses of AbtRow, they will probably need to add this prerequisite. 
  If you package your application and get the error The attribute Pub <Attr name> does not
  exist at runtime, you need to include the AbtRecordStructureApp application. 
(7.0.1) ODBC Drivers are not shipped with VA Smalltalk
   VisualAge Smalltalk Enterprise V4.5 was the last release to ship with 
   ODBC drivers. The drivers in V4.5 were provided by MERANT (formerly 
   INTERSOLV Inc.). If you need to obtain ODBC drivers, the DataDirect 
   product may still available directly from MERANT. 
  You can also check your Database Resource Manager for ODBC drivers. 
  Most, if not all, major Database Resource Managers now ship with ODBC 


Display Resolution for DBCS machines
  To ensure all information is displayed on your computer, we encourage you to use the highest 
  resolution offered by your display terminal. 

Documentation and Helps

Identifying browser and newsreader on Unix
  If you get no response from Smalltalk when requesting Help (from the Help menu or F1),
  the most likely cause is that the browser and/or the newsreader installed on the system
  cannot be found.  To correct this problem, edit the .ini file (for example, abt.ini)
  and add links to the installed browser and/or newsreader in the [Help] stanza -- you
  will see examples of specifying Firefox and Thunderbird.  You can specify either a
  complete path to the browser and/or newsreader (not usually necessary) or a relative path.

Domino Connection

Using an English version of Lotus Notes
  The NLS versions of Lotus Notes must be installed on the native Operating System (OS) platforms, in 
  order for Notes to work. If a US-English version of Lotus Notes is installed on the native OS, then 
  the user will not be able to input either SBCS or DBCS characters correctly. This is a restriction 
  with Lotus Notes. 
Error detaching documents using Domino Connection
  When detaching a file attachment using the Domino connection, the detached file is corrupted.  The 
  problem only shows up if the attachment is BASE64 encoded.  Detaching the same attachment using the 
  Notes Client works fine. Detaching via Domino connection also works fine if the file has been 
  attached manually using the Notes Client.


Withdrawal of EMSRV support for Windows NT/2000 on SMP hardware
  Running any release of EMSRV for Windows NT/2000 on a machine with more than one processor may 
  lead to code repositories becoming corrupt.  There are no known current issues with multiprocessor 
  boxes under any version of Windows since Windows NT.  However, since the problem was never 
  isolated to a specific cause, EMSRV issues a warning when started on MP hardware.

  EMSRV 7.1a (shipped with all versions of VA Smalltalk) --  if EMSRV detects more than one installed
  processor, and the -mp command line option is not specified, EMSRV will report the following to the
  console (or to the Application Log if EMSRV is running as a service) and then exit:
    WARNING:  Running EMSRV for Windows NT/2000 on multiprocessor hardware is not supported due to 
    suspected operating system bugs that may result in repository corruptions.  Install and run EMSRV 
    on a machine with a single processor or start EMSRV with the -mp option to bypass this check.
  The check for SMP hardware can be bypassed by starting EMSRV with the -mp command line option.  By 
  doing this, you will be running EMSRV on an unsupported platform and must assume full 
  responsibility if code repositories become corrupted.  When starting with the -mp command line 
  option, EMSRV will still report a warning to the console (or to the Application Log if EMSRV is 
  running as a service):
    WARNING:  Running EMSRV for Windows NT/2000 on multiprocessor hardware is not supported due to 
    suspected operating system bugs that may result in repository corruptions.  You have chosen to 
    start EMSRV with the -mp option to bypass a check that normally restricts EMSRV from running on 
    multiprocessor hardware.  This may cause repositories to become corrupted.
  Note that EMSRV continues to support SMP hardware in all other operating system environments.
(7.5.2) Native password validation on Linux
  EMSRV native password validation on Linux uses Pluggable Authentication Modules (PAM).  The
  sample PAM file shipped with VA Smalltalk is correct for older Linux distributions, but
  does not work for newer distributions


Copying from Windows Explorer into an OLE Client part
  Use copy and paste to share OLE objects between the Windows Explorer and an OLE Client part. 
  Dropping an OLE object that was dragged from the Windows Explorer onto an OLE Client part does not 


  No additional information at this time.


(7.5.1) HTTP server access log
  An SST HTTP server can write an "access" log containing an entry for each request received by the 
  server. Entries in the log are formatted according to the default format used by the Apache HTTP 
  server in order to enable tooling for Apache logs to be used for SST logs as well.  
  The access log is initialized in SstHttpServer>>startUp.  If an access log is desired, it can be 
  specified in 2 ways:
  1. The application can send SstHttpServer>>accessLogFormatPolicy: AND SstHttpServer>>accessLog: 
     prior to sending SstHttpServer>>startUp. 
  2. The application can be started with the following command line switch: -sstaccesslog.  This will 
     cause a log file named httpd.log to be written in the current directory.

  Migration note:  To maintain the same logging behavior in VA Smalltalk V7.5 and later that was
  provided in VisualAge Smalltalk V6.0.3, V6.0.4, VA Smalltalk V7.0 and V7.0.1 you should start
  your runtime application with the -sstaccesslog command line switch. 
Performance improvement in writing walkback log
  By default, when an error occurs, the walkback information is written to TranscriptTTY.
  This causes the walkback information to be written to the console or to a log file identified
  by the -l command line option.  Since TranscriptTTY does unbuffered character-at-a-time output,
  it can be very time consuming to write a large volume of walkback information.
  For VisualAge Smalltalk V5.5.2 and later, an alternative output mechanism is provided.  When it is 
  enabled, this mechanism writes the walkback information to a file stream just as would be done for 
  a Reduced Runtime image.  This is a buffered operation which can be more than an order of magnitude 
  faster than writing to TranscriptTTY.
  To enable writing the walkback information to a file stream, you must provide the startUp class 
  with the filename of the file to be associated with the file stream.  For example, to see the 
  difference in behavior, create an XD image and load the HelloWorld application.  Then package it 
  specifying AbtHeadlessRuntimeStartUp as the image startup class and HelloWorld haltHelloWorld
  as the application entry point.  When you execute the packaged application, a walkback will be
  written using TranscriptTTY.  However if you specify:
    System image startUpClass walkbackFileName: 'runtimeWB.log'
  before you package, the walkback will be written to the runtimeWB.log file.
SST IIOP Support is Obsolete
  CORBA IIOP facilities provided by SST in previous releases are obsolete as of this release. The 
  implementation provided in previous releases continues to be shipped with this release, but all 
  methods have been recategorized as 'OBSOLETE'. There will be no further development or enhancement 
  of these facilities, and they may be removed from the product in a future release. 
  Customer applications which made use of these facilities in a previous release will continue to be 
  supported as they are migrated to this current release.
  Customers are advised to make use of Web Services technologies, such as XML and WSDL, for future 
  interoperability strategies.
Support for JDK 1.3 using RMI
  The RMI in Server Smalltalk will run under JDK 1.3, using the same techniques that were required 
  for JDK 1.2.
UnixSocketDemux>>sstWarn: sends AbtCLDTAdditions message
  SstUnixSocketDemultiplexer>>sstWarn: sends #abtPadWith:upToLength:onRight:, which is implemented in 
  AbtCLDTAdditions - an app not in the prereq chain of the controller for 
  This method will likely be removed during packaging, causing a runtime DNU.
  Workaround: include AbtCDLTAdditions when packaging an SST app.
Using XD Interactive Debugger over TCP/IP with no nameserver
  When trying to use the interactive debugger, if you are getting the error EHOSTNOTFOUND or 
  EADDRNOTAVAIL on the runtime side, the problem may be that your runtime machine cannot resolve the 
  dotted TCP/IP address of your development machine. You can work around this problem by adding an 
  entry to the hosts file on the runtime machine for your development machine. 

VA Assist

Uninstalling VA Assist
  Uninstalling VA Assist is a bit involved. To uninstall the feature,
  1. Start with an image named the generic name: abt.icx.
  2. Launch the image.
  3. Disable VA Assist (From the Transcript choose Tools -> VA Assist Pro -> Disable.)
  4. Save (using the Transcript -> Save) and restart the image.
  5. Uninstall the feature. There are two ways to do this:
     a) From the Transcript choose Tools -> Load/Unload Features...
        Select VA_ VA Assist Pro from the right pane and move it with the << button to the 
        left pane. Dismiss the dialog with an OK.
     b) From the Transcript choose Tools -> VA Assist Pro ->Uninstall.
  6. Save the image using the Transcript -> Save.
  7. If you renamed your image, restore its former name.

Web Connection

Web Connection does not support DBCS char for Cookies
  DBCS cookies are not supported using the Servlet Interface.  This is a limitation of the HTTP 


  No additional information at this time.


Suppress serialization of nil attribute values when attribute mapping specifies Required="false"
  This change does NOT affect objects that utilize an XML schema for serialization.
  Nil attribute values are now suppressed during serialization of attributes with attribute mappings 
  that specify 'Required="false".
  For example:
  <ClassElementMapping ElementTagName="customer" ClassName="AbtXmlSampleCustomer" >
  <AttributeMapping ClassAttribute="lastName" Required="false"><Attribute>lastName</Attribute>
  If the lastName attribute of a serialization target object is nil, the serializer will not render 
  the 'lastName' attribute.  
XML code page conversion (unsupported encodings)
  The XML parser automatically performs code page conversion before attempting to parse an XML 
  stream. Many code pages are handled seamlessly using the default code page conversion routine of 
  the runtime operating system. However, there are some character encodings that cannot be converted. 
  Unsupported code page conversions cause walkbacks at execution time. 
  The following code pages are not supported: 
   * EUC_JP conversion is not properly supported by native Windows code page routines.
  * The code page ISO-2022-JP is not supported by native routines
  The VA Smalltalk XML support attempts to map XML character set encodings to valid code pages. The 
  default mappings can be overridden using the API shown in the following example: 
  AbtXmlStreamConverter mapEncoding: 'UTF-8' toCodePage:  65001.
  VA Smalltalk uses the code page conversion support APIs that are built in to each of the supported 
  platforms. Therefore, code page mappings may be different for different operating systems. If you 
  encounter a debugger with the following message it is likely that you have encountered an unmapped 
  or mismapped encoding. 
  Abt.Nls.160.e: Conversion from code page <sourceCodePage> to code page <targetCodePage> is not 


  (C) Copyright Instantiations Corporation 2005,2007. All rights reserved.