Gracias, I'll keep this info handy for the near future.


Paul wrote:
> Nicholas wrote:
>> Thank you Paul for the clear and concise information. I now see where
>> you were going. It has been a while since I really built a system (6
>> years). If I remember correctly, a change of mobo would require mobo
>> driver changes as well and assorted other configuration work. If I
>> could just slot in the current hard drives and go I would consider it.
>> At present, a clean HD and reloading all the software is not something
>> I'd like to undertake.
>>
>> I will be in the market for a new machine later next year. I am not
>> sure where 64bit systems have reached or whether the Windows XP/Vista
>> 64 bit OS's have reached the point where they make a usable difference
>> for me. At present my main software is 32bit. CorelDRAW X3, AutoCad,
>> and Sketchup. Again, I'll need to research the compatibilities of
>> OS's/hardware/software for what I want to do. I do have preference for
>> AMD.
>>
>> I have also been paying a little attention to the Apple systems
>> capable of running Windows, purely because a majority of people in my
>> field use Apple machines. That in itself would never a be a deciding
>> factor, but if I came across Apple only program that I had to have
>> then...
>>
>> What is the "cutting edge" AMD platform that I might look at, that
>> will still around next year? i.e. Socket what?
>>
>
> Socket AM2 will still be around next year. AM2 uses DDR2 RAM, and the
> degree of improvement from the RAM perspective, may depend on what
> speed and CAS value you buy. DDR2 is still a bit on the expensive side,
> and the price will settle down next year.
>
> In terms of the near future, this article has some hints as to what
> AMD may want to change in terms of that socket. The AM2+ split plane
> concept, allows running the two cores in a dual core processor, at
> different voltages. That is to allow a power saving over current
> day operation. It is a small refinement that doesn't impact performance.
> I expect in terms of clock rate, things will be more or less the
> same next year, as they are now for Athlon64 X2. (In other words,
> faster processors will come out, but you won't be able to afford
> them.)
>
> http://www.theinquirer.net/default.aspx?article=35211
> http://www.theinquirer.net/default.aspx?article=35902
>
> In terms of changing motherboards in your existing machine, you can
> do a "repair install". That preserves your settings and your
> existing third party software installs. My recommended upgrade
> procedure, is to buy a new hard drive, make an exact copy of your
> current disk (I do that with an old copy of Partition Magic, but
> maybe the disk manufacturer has software to do something
> like that too.) Once you have the exact copy disk in hand, you are
> prepared if something goes wrong. You can uninstall your current
> video card drivers, just before shutting down and starting
> "surgery" inside the computer case. Then, reinstall the video card
> drivers after the new motherboard chipset drivers have been installed.
>
> Instead of doing a repair install (which requires putting back service
> packs and all those Microsoft patches), you can create a new hardware
> profile (I've used that in Win2K), or you could delete the whole hardware
> enum in the registry (another method to get rid of the old drivers).
> Techniques like that are more difficult to get right in one attempt.
> Which is why you have the exact disk image, in case you need to back out
> and try again. For example, in retrospect, on my last motherboard
> upgrade, I should have removed my old sound card software before
> I changed the hardware. I now have a mixer panel running, for
> a sound card that doesn't exist :-) While a repair install
> takes care of most of the details, using your brain and thinking
> about what is changed between the old system and new, is a
> good thing to spend 5 minutes thinking about. Expect the software
> side of things, to cost you a couple of evenings, and perhaps
> an extra grey hair or two.
>
> In terms of logistics, it may be easier to remove all the components
> from the computer, and set them up on a table. Don't put the components
> back into the computer case, until the repair install has been sorted
> out with the new motherboard. It is a lot easier to work on a table
> top, with everything easy to reach, and unplug etc., than to be doing
> all the work while everything is inside the computer case. I put a
> thick telephone book with cardboard cover, underneath the motherboard,
> to provide support. The only dangerous part of doing stuff like that,
> is the risk of pulling the video card out of the slot. Don't allow
> any small children around the table, while you are working on
> the system. My last two upgrades, were completely booted and tested,
> while sitting on the table in pieces.
>
> Paul