I need to generate a RAM (8 bits by 128 words) with RAGE. The RAGE step went well with both Alliance 3.0 (office machine, Solaris 2.5.1 on SPARC and home machine with Linux SuSE 5.2 on Pentium) and Alliance 3.2c (home machine only). I could see the generated symbolic layout with GRAAL at least at home. But when trying to use s2r to get a GDS II or cif format, the two versions behave differently: both look for a file named dtram_c, with a suffix (cif or gds) depending on environment variable RDS_OUT, but on 3.2c the file is not found, while on 3.0, if RDS_OUT is cif, a message cif105: Layer unknown, line 10 is issued. A "strace s2r <input-file-name>" shows that the dtram_c.cif is sought for first in . (where the MBK_WORK_LIB points) and then in $TOP/share/cells/rage, where $TOP is correctly replaced by the top directory of Alliance, that is the MBK_CATA_LIB variable is correctly interpreted. Copying the dtram_c.cif file from the directory tree of Alliance 3.0 to the one of Alliance 3.2c moves the result too: now both systems complain about the unknown layer in line 10..... I have some abilities with the front-end (syntesis, optimization) of Alliance, but this is the first time I try to use the back-end silicon-level tools. Please help, if possible. Thanks in advance and best regards. Aldo Mozzi -- Aldo Mozzi <aldo@protec.it> Via Monte Cimone, 17 35035 Mestrino PD Italia