Frank, Thank you for the information. One major issue is my source installation server is a Windows server, so I am unable to use the great tools that yast supplies to do this. One thought I had has to create a Sles9 server and use yast to create my Sles9 SP1 directory tree. Then copy it all to my Windows server. Any thoughts? What will Windows do with the symbolic links? Any other suggestions? I am even seeing issues with my boot CD since I changed the "Linux" and "initrd" files to the SP1 versions. I am so close, but yet so far with this whole project. It seems so straight forward, but I can't get it to work. Thanks for the help! Bridgette -----Original Message----- From: Frank Steiner [mailto:fsteiner-mail@bio.ifi.lmu.de] Sent: Friday, April 01, 2005 7:12 AM To: Radzai, Bridgette A. Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] SLES9 Installation Tree I had the same problem as you can see in the archives. It seems that things can go wrong if you set up your installation directory manually and then try to integrate the SP1 stuff. Rename you current directory, and setup the installation sources again with yast. Then also add the SP1 sources with yast. Then it should work, and will still continue working if you rename the directories (fixing their names in the yast (inst)order, too) afterwards. I could even remove the CD? subdirectories and put all the stuff in the same directory, i.e., just having sles9/ and sles9-SP1/ directories with no further CD? subdirectories. SDK sources could not be added with yast, I added them manually after renaming the subdirs. And that worked fine. cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *