The original Actel database format for the design consisted of multiple ascii text files. This was followed in Designer 3.0 and 3.1 with a single .adb file and the Objectstore database. Designer 3.11 and later software stopped using Objectstore and went to a proprietary format. This application note will provide a procedure for updating old Objectstore databases to the new format.
(Courtesy of A. Jeong.)
This application note is supplemental to Actel's Designer Series Development System Conversion Guide - Windows Environment, which is included in the on-line documentation that comes with the Actel Designer software. This note applies only to ObjectStore database conversions on PCs running Win95. It is assumed that the reader is familiar with creating and running DOS batch files, as well as setting and reading DOS environmental variables.
The earliest versions of Actel software, first called ALS and then Designer, used multiple text files to store design information. Designer software versions 3.0 and 3.1 saved design information in a commercial database offered by ObjectStore. Later versions of Designer software, 3.1.1 and higher, use an Actel proprietary database that does not require the ObjectStore software. Designer versions 3.0 and earlier will not run on Win95.
To enable a 3.1.1 or higher version of Designer to directly read an ObjectStore database, the database must be converted into the new Actel format. Converting an ObjectStore design database involves reading the database into Designer 3.1.1 or higher, with the ObjectStore software running, and then saving the database. The newly saved database will be in the new Actel format.
To convert an ObjectStore database, the ObjectStore software must be available. Although any version of Designer software 3.1.1 or higher (as of this writing, up to R2-98) can be used, it is recommended that the Designer 3.1.1u1 software is used to convert designs. Once the design database is saved using the Designer 3.1.1u1 software, any newer version of Designer software can read the database directly, without requiring the ObjectStore software.
It is also recommended that the ObjectStore software is installed in its own directory and this installation shared, if necessary, by different versions of Designer software. If the ObjectStore software is installed in the same directory as the Actel software (i.e. both program's executables are in the same bin directory), when you un-install the ObjectStore software, the Actel software will be deleted as well.
From the Designer 3.1.1 CD, install the ObjectStore software contained in the \OSTORE (not the \OSTORE3) directory, using the install.exe program contained in the \OSTORE directory.
From the Designer 3.1.1 CD, install the 3.1.1 software, following the instructions provided. From the Designer 3.1.1u1 CD, install the 3.1.1u1 update software, following the instructions provided.
Note: The Designer software does not read any variables in the registry, though during installation variables may be added to the registry for use by other software programs.
To make it easier to switch between different versions of Designer software, it is recommended that you create batch files for each version of software and run the batch file in a DOS window. Each batch file should set the environmental variables ALSDIR and PATH for the version of Designer desired, and then invoke the Designer software. A sample batch file is shown below. The Designer software is assumed to be installed in the c:\ACT311U1 directory. A suggested name for this batch file might be RUN311U1.BAT.
Note: Make sure that the PATH variable doesn't exceed 127 characters. Specifying the exact path instead of appending to the current path (as shown below) would help avoid this.
REM The "call" command line is needed only for ObjectStore.
REM Make sure the batch file c:\OS_AUTO.BAT exists and is correct before calling it.
call c:\os_auto
set ALSDIR=c:\act311u1
set PATH=c:\act311u1\bin;%PATH%
designer
A sample OS_AUTO.BAT file is shown below:
@ECHO OFF
SET OS_ROOTDIR=C:\OSTORE
SET ODI_SERVER_DIR=C:\TEMP
SET PATH=C:\OSTORE\BIN;%PATH%
SET LIB=C:\OSTORE\LIB;%LIB%
SET INCLUDE=C:\OSTORE\INCLUDE;%INCLUDE%
- If you have created a batch file to run Designer 3.1.1u1 with the Ostore software, then use it to invoke the software and skip to step 3). Otherwise, open a DOS window and type "set". Verify that the ObjectStore environmental variables are set and that the ObjectStore executables are in the path. Also verify that the Designer 3.1.1u1 environmental variables are set and that these are the only Designer executables in the path. See the Conversion Guide for more information.
- From the DOS window, type "designer".
- Open the 3.0 or 3.1 Designer design database and save it. The newly saved database will be in an updated format and now can be read by any 3.1.1 or higher version of Designer software without requiring the ObjectStore software.
VII. Some potential problems when using Win95 that are not included in the Conversion Guide
1. Running out of environment space.
If you run out of environment space, add the following line to the end of the autoexec.bat file:
shell=c:\windows\ command.com /e:4096 /p
Note: You may need to modify the above line to point to a different command.com file.
If you already have a similar line in your autoexec.bat file, do not add this line but change the number after the "e:" on your existing line to something larger. If there is no /e option, add it as shown above. Refer to the DOS help command for more information.
Re-boot the PC after making these changes.
2. Designer hangs when invoked.
First, note any pertinent messages in your %ODI_SERVER_DIR%\osserver.txt file and look at the section "ObjectStore Will Not Start" in the Conversion Guide. If none of the situations described in the Conversion Guide are relevant, try re-initializing the ObjectStore transaction log file. Verify in a DOS window that the ObjectStore variables and path are set correctly. At the DOS prompt, type "ossetup" and do the following:
a) If ObjectStore was already running, you will be asked what you want to do. Select "Shutdown services".
b) Select "Re-initialize Server" from the main menu.
c) If desired, change the location of the transaction file. Select "OK".
d) Select "Yes", "Initialize Server", "OK", and finally "Exit" to complete the server log file initialization.
e) Re-try the procedure under "Converting a Design".
Home
Last Revised: January 09, 2002
Digital Engineering Institute
Web Grunt: Richard Katz