From: Tim M. <or...@le...> - 2012-09-02 15:04:18
|
david wrote: > So you add ANOTHER DRIVE to the system???? That's what I do. Yes, I could have picked up an old drive somewhere and stuffed it into the box. I even considered picking up an IDE to SATA adapter so that I could attempt to use a newer drive, but the bottom line was that the machine itself was hopelessly out of date. A 550MHz Pentium III processor with 256M of ram (apparently HP's upper limit for that motherboard) is hardly sound-barrier stuff these days. Rather than pouring more money into a lost cause, I decided to upgrade. > Didn't have to modify any apps to run on 64-bit. Which apps are you > talking about? The first example that comes to mind is an obscure program called "Rosegarden" and how it deals with library paths. On a Slackware system, 32-bit stuff typically goes into /usr/lib, while 64-bit stuff ends up in /usr/lib64. Because I had built and installed DSSI and LADSPA from source, they ended up in the 64-bit library where Rosegarden couldn't find them. My initial workaround was to place symlinks in the 32-bit library, but eventually I got around to patching src/sound/DSSIPluginFactory.cpp and src/sound/LADSPAPluginFactory.cpp with more complete path info. Other programs that needed adjustment were mostly things that I had written years ago that contained snippets of truly ancient code. Back in the 16-bit days, for instance, we made assumptions about the size of an "int" that are no longer valid. Tim |