DJX, so; you're saying that with 32 bit XP installed; the system is ignoring those 64 bit drivers I accidentally installed? The generic RealTech driver that I went to RealTech's website and found, was marked Win 2000 and Win XP 2003 32/64 There was only one .exe in the download, so I guess that particular driver senses whether it's a 32 or 64 bit system that's running.
Of course, it's a moot point anyway, since you don't find much XP 64 around.That generic RealTech audio driver is working fine, no need to look for a better one than that. I really don't care if 8 channel surround sound is implemented or not, so the generic driver is fine, I only want it for screenreader speech anyway. As for the lack of the usual Windows dialog when a USB thumb drive is plugged in, it's not much inconvenience, USB transfers work anyway. I didn't disable plug and play, maybe it's just how this current motherboard reacted to XP 32.
Thanks for your expertise, Indigo L On 12/2/2011 4:33 PM, D!J!X! wrote:
Hi, you can't really use 64 bit drivers on a 32 bit OS, so I can certainly tell you that your xp drivers are 32 bit. If you downloaded windows7 drivers they must have been one of those generic packs which include drivers for various platforms. So you have nothing to worry about, those drivers are fine, if they work then that's all that matters. 64 bit and 32 bit are 2 completely different platforms, so I'm sure that the drivers won't work on one to the next, unless they were 32bit drivers to begin with. You can use 32bit stuff on 64 bit (most times), but you can't use 64 on 32... The USB issue you describe, if you're talking about flash drives and such, it's the autoplay dialog. Did you disable it? Did you turn off services on xp? Perhaps the plug and play service is disabled. Regard background services, leave the processor scheduling for programs, background services, though asio is a service, will not work well for Sonar, cakewalk has tested to this fact already. That feature is more useful for server type systems anyway. If that's xp 32bit, you probably will only see 3.5 to 3.75GB of RAM. XP can't see a full 4, due to the way addresses and such are handed out on x86 systems. Disabling the page file should prove useful and helpful since you've got ram maxed out. HTH, D!J!X! -----Original Message----- From: realmusicians-bounce@xxxxxxxxxxxxx [mailto:realmusicians-bounce@xxxxxxxxxxxxx] On Behalf Of Indigo Sent: Friday, December 02, 2011 11:44 AM To: realmusicians@xxxxxxxxxxxxx Subject: [realmusicians] So Far, So Good! So far, inspite of 64 bit drivers installed, Windows XP Pro 32 is running like The old Orange Blossom special with Caysey at the throttle, and John Henry shoveling on the coal. Everything looks close to the same as in Windows 7, like 4 cores and 4 hyperthreads are shown in Control Panel, Systems, ghz is 3.4, I looked in System tools info trying to learn how much memory is recognized, but couldn't find the report on that. RealTech is behaving, WinAmp is playing through it normally. Installation times are phenomenal! Reaper took no more than 10 seconds to install. So wonderful, this early time with an operating system, when it's still virginal and un encumbered, fast as greased lightening! I found where the mistaken 64 bit drivers went in the registry, all of them are there together in a MSI folder. I'm sure not gonna remove any of them until I get proper XP 32 drivers, if such exist. So far, it acts like a normal XP, and a very happy Winize 6.1. I love XP! I like those precise little Germanic clicks when I press a key, and the instantaneous response I find only 1 little thing that's different from my other XP machines. When I plug a USB drive in, I'm not getting the usual Microsoft dialog about opening it. It just says: Hardware Device Detected 125W. I suppose it does need a USB driver it doesn't have at the moment, to speak that dialog; but copying from USB drives to the computer are behaving normally. I'll try writing to USB to test it, but I'd expect writing to be normal. One question: Is it true that it's best to use a specialized driver removal tool, or is it sufficient just to delete the 64 bit drivers in the registry, once I have correct 32 bit equivalents? Another tiny question, does setting performance to give preference to background services matter much? I've heard differences of opinion on that. Some are saying that certain music programs run from services that are nnot in the background, and don't do as well . with that tweak. I'll surely go and set page file to none; as DJX advises I'm totally convinced of the value of that tweak. . All power plans are set to never off, and I've done most of those other little tweaks. The monitor image looks fine, according to Hannah, so I'm not going to worry much about that driver. If Reaper and ReaAccess behave themselves, and some of my power hungry STI's play nicely, can't wait to hear Native Instruments Massive, next I'll try Sonar 8.5.3 and give it a few CPU vampires to play; ; and learn if it's as tempermental and prone to crash as it was on the old slow machine. Thanks for any info, Indigo L ?.
