Hi Ismael! 64bit can address more memory (I think this relates to RAM. I think the integer size used by the CPU is larger. So good for large numbers? and for a lot of mem. Some people also claim in RT apps it's faster, but I don't really believe that. 32bit: All the wndows dlls will run. I guess you'lll also find more precompiled half-closed software pieces for 32bit. Mplayer and some other programs can use .dll and other windows shared libs to support audio/video formats and maybe more. Java shouldn't be an issue. You should only need the java interpreter and the rest is byte-code, that's supposed to be the same for all systems. but 32bit might also be nice if you're going to use VST(I)s, because they too are pieces of 32bit windws software. But I'm not sure how far the technology has gone here. Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

On 08/14/2009 06:12 AM, Ismael Valladolid Torres wrote: I recently (1 week ago) did a comprehensive QA on Fedora 11 x86_64 from a "normal" users perspective. Here's my findings in brief... - Beware of the 64 bit version of libflashplayer. It is hardcoded to use /usr/lib so it will not work with pulseaudio on a 64 bit distro unless you have your 64 bit libs in /usr/lib instead of the more usual /usr/lib64/. If you don't want pulseaudio and go direct to the alsa layer then it will not release the sound device can be a hassle as you need to shutdown firefox before using any other sound apps if you have previously been using flash with audio (ex. youtube) If you do go with flash(64)+pulseaudio on 64 bit you will not be able to use 32 bit apps with pulseaudio (realplayer, skype) as the libraries for 32 bit are found in the same location /usr/lib/ and replacing them with 64bit libs will mean they cannot work with pulseaudio. So, if you get good performance from the 32 bit flash plugin then everything should be smooth sailing regarding sound over pulseaudio. FYI, many people have found the 64 bit flash plugin is faster and more stable than the 32 bit plugin. - In addition if you want to use jack you will need to disable/kill pulseaudio before starting up. There are several methods available for this now which have been recently discussed on this list or you can install jack2 which has internal logic for this process but currently just bypasses pulseaudio instead of reconnecting it to jack. - If you want to use pulseaudio with jack and get the best of everything then you should use v0.9.16 or later for stability and the methods referenced above. IIUC, no distros are currently shipping that version. If you choose to upgrade manually you will find there is very little build documentation and you may have trouble building the 32 bit version of the libraries for compatibility with 32 apps (realplayer, skype). - There is a 64 bit beta version of helix and realplayer avialable as a nightly build but in my testing they didn't work for streaming audio. That could be a known bug (probably) and might change quickly or it might not be part of the current dev cycle in which case it could take a while to be fixed. - A lot of people have issues with skype over pulseaudio and if you use it over alsa it hogs the device so if you want to use it you should look at getting a usb phone to save hassles. Just make sure it is usb-1.0 as the usb-2.0 drivers are not well tested with many devices yet and to make things more frustrating, many usb-2.0 devices are not standards compliant. - My camera, printer and dual monitor setups worked out of the box with Fedora 11. I had some trouble with my scanner but got it to work eventually with the "sane" drivers and apps. - I had to install the manufacturers version of the driver for my wifi card manually to get it to work. Otherwise wifi is a breeze to work with. Cheers. Patrick Shirkey Boost Hardware Ltd