Hi, after finally getting my MSI K8T Neo VIA SATA controller to work somewhat by turning on udma2 support, I ran into some new problems e.g. when trying to install the w32codecs for xine and also get them to work with xine (either the suse x86_64 rpms or my custom built packages from cvs). But let me not bore you with these detail but ask some general questions for my understanding: 1.) As I understand 32bit programs can not dynamically link to 64bit .so libs. In no case. Can you confirm that? [I.e. my xine must be 32bit if I want to use the 32bit w32codecs] How can 64bit and 32bit program then interact at all? Only via sockets or rpc? 2.) Could my remaining problems with my Athlon64 K8T board be related to the bios not being well tested when running in 64bit mode (due to the lack of a 64bit windows)? In some cases Suse 9.1 AMD64 contains also 32bit versions of frequently used libraries. 3) How can I compile/rebuild these libs preferably from the suse sources to a 32bit package and get the installation location right (relocation). Using linux32 and rpmbuild or simply from 32bit suse 9.1 DVDs as binary rpms? 4) How do I relocate non-suse source rpms correctly so that when I compile to 64bit, they end up in the correct /usr/lib64 directories? And then when I start the app how does it know where to find the 64bit .so libs? 5) *-devel packages are noarch (i.e. they work for both 32 and 64 bit), correct? 6) Is there is method to change compiler flags (e.g. add -fPIC) when building a package without actually unpacking, changing the spec file, repacking and trying it again? Then finally just out of general interest, has anybody ever benchmarked the 32bit Suse Linux against its 64bit sister on the same Athlon64 machine? I searched on the web quite a bit but couldn't find any good explanations. Therefore Any hints or links would be greatly appreciated. best regards, Jan