Vicktor reported that he could not get kylix Open Edition to run after installation from CD5 (not 4) using YaST2. I installed kylix, then opened a terminal and entered 'startkylix'. After a couple of seconds I received a message stating "jerry@jerrykreps:~> startkylix Can't open configuration file /home/jerry/.borland/.borlandrc, $HOME/.borland/.borlandrc or shared configuration file /usr/local/etc/borlandrc.conf jerry@jerrykreps:~>" I manually created /home/jerry/.borland/.borlandrc and then reran startkylix. The message then became "jerry@jerrykreps:~> startkylix Warning: no valid DOS drive found, check your configuration file. Warning: could not find wine.conf [Drive x] entry for current working directory /home/jerry; starting in windows directory. Invalid path 'c:\windows' for windows directory Perhaps you have not properly edited or created your Wine configuration file. This is either /usr/local/etc/borlandrc.conf or $HOME/.borland/.borlandrc or it is determined by the -config option or from the WINE_INI environment variable. Wine has used /home/jerry/.borland/.borlandrc as configuration file. jerry@jerrykreps:~>" startkylix contains: jerry@jerrykreps:~> cat /opt/kylix/bin/startkylix #!/bin/bash source /opt/kylix/bin/kylixpath /opt/kylix >/dev/null /opt/kylix/bin/Kylix $* I understand what "source /opt/kylix/bin/kylixpath" does. I am not sure what "/opt/kylix >/dev/null" since /opt/kylix is a directory, not a program. I checked my copy of Kylix Desktop Edition and did not find a configuration file by the name of .borlandrc. The only files under the .borland subdir was an odbc config file, a couple of other config files relating to components, and a binary file which a binary editor revealed to contain 'short cuts'. ?? So, it looks like either SuSE supplies the necessary information and/or install patches, or the Kylix OE will never be run on 7.3. Jerry