I saw 8GB of DDR3-1600 (2x4GB) in my local shop for $52 and thought I would grab it - after the hard drive fiasco I thought it was time to get some more RAM
before Mother Nature flattened the RAM factories (and human nature took advantage by doubling prices). I now have 16GB and man it is soooo much faster! (well, not at all).
Unbelievably, Windows decided that adding 8GB of RAM is a 'major hardware change'. WTF? Fair enough a hard drive (serial number) or network card (MAC address) but adding RAM?
Looking at some forums, one bloke even reckons he had to reactivate simply by swapping the slots of his two RAM modules.
After having to phone Microsoft to get 8 six-number codes to input to reactivate it I was left...bemused? I mean it's no big deal, it's back to normal now but I can see how a newbie would
assume from the automatic activation failure that they needed to buy a new key - choices were 'retype your key', 'buy another key' or 'phone Microsoft'.
Now that I have played with Windows 8 for long enough I will need windows 7 for many years to come...
that's a major OS change
i wonder if the rules also changed for win 7 ?
as i recall, the amount of RAM was not one of the tested properties for XP authentication
as for not seeing an improvement - you may, if you have many windows open, and you are editing a video or something
i recently upgraded both of my XP machines from 1 GB to 2 GB
in normal use, i see little difference, if any
but, with 1 GB, if i was converting a video from one format to another, i more or less had to leave the machine alone
now, i can do other things at the same time :P
The only thing I have changed on my win7 box was adding 2 x 1TB hard disks and there was no problem at all but the version is the black box ultimate version that cost me a fortune that can be reinstalled over ad over again.
Is that why I never had problems Hutch? Interesting. I first installed Win7 Ultimate 32bit on my machine, reinstalled it many times no hassle. Then I built the new 64bit box and was ready to make a call to MS since it was a MAJOR hardware change :-) Nope, installed and activated nooooo problems, even used the same CD key(Ultimate came with a 32bit and 64bit dvd) Since I built this, I installed more RAM sticks, a new video card and no problems.
Just changed my motherboard - the old one went up in smoke , literally - I knew that I would have to contact Microsoft to re-activate, so I used the Auto Phone Activation. I had to enter 9 x 6 digit numbers on my touch phone key pad & then enter another 9 x 6 digit numbers read out over the phone on my keyboard, 108 digits altogether, luckily i didn't make a mistake & Windows was re-activated. I wonder what would happen if you did make a mistake - start again?
I've done several clean installs on different hardware, changed my graphics card, added and removed hard drives with no problems. Accepts the key, activates OK.
I was just amazed that for such a simple change it needed reactivation. Maybe hardware is weighted - I changed a network card, Windows needed reactivating.
MAC beats HDD serial but RAM serial beats all? One of Microsoft's recommendations is to increase your RAM...it's a conspiracy!
Could also be a cumulative thing, you can only get away with so many changes.
yah - it's a cumulative response to several things
i think the NIC counts as 2 or 3 "points" in a 10-point system
I've not had problems upgrading the memory in a number of Win7 systems. This includes systems with Starter, Home, Pro and Ultimate, and ones where the memory was upgraded more that once. (6GB -> 8GB -> 16GB)
Laptop DDR3 1333 was $20 USD before tax for 4GB sticks last week.
10 items checked for WPA
* Display Adapter
* SCSI Adapter
* IDE Adapter (effectively the motherboard)
* Network Adapter (NIC) and its MAC Address
* RAM Amount Range (i.e., 0-64mb, 64-128mb, etc.)
* Processor Type
* Processor Serial Number
* Hard Drive Device
* Hard Drive Volume Serial Number (VSN)
* CD-ROM / CD-RW / DVD-ROM
the NIC counts as 3 points
i believe you have to get 7 points to pass
Its probably a case of using an OEM version versus a retail version. The latter is far more expensive but you can keep re-installing it as long as its only on 1 machine.
that's probably right
there is a big difference in how windows activates OEM builds
i happen to have 2 identical sony machines (consecutive serial numbers) - they use the same 25-digit code
the sticker on the outside of the box has a different code
in the case of XP Media Center Edition, i think that OEM is the only way it was ever made available
if you build your own machine, and buy windows off the shelf, you have "the real McCoy" :P
Mine are all OEM, I don't recall buying a full-up retail version in forever. The OEM versions are generally available with the purchase of a token piece of hardware, and clearly on all the prebuilt systems.
I've been pretty happy with the "Anytime Upgrade" function for Win7. It does seem rather stupid however that I can pick up the kits at my retailer cheaper than the direct prices Microsoft charges if you just use your credit card.
I'll also note that a lot of the memory sticks are serialized, the EEPROM with the timing parameters usually has part numbers, manufacturer and serial numbers. Try looking with CPUIDZ next time you're thinking of updating.
One area of frustration I have been having is with getting accurate information about the size of memories supported by various motherboards. ie a lot that suggest they only support 2GB sticks, when 4GB sticks will work. I'd imagine some of the 8GB sticks would also work, but the pricing delta is too high to experiment. And all the Intel Atom netbooks can only support 2GB total, the older ones DDR2 and the newer DDR3.
Still, now I have a growing cache of 2GB DIMMs
:bg
> Still, now I have a growing cache of 2GB DIMMs
I have a draw full of memory from the 486 days onwards, some of it would even be rare. One of the things that pisses me off is the rate of change with memory, each board generation requires a different type of memory that as usual you have to buy at top price while the board is current.
At least the two quads I use both use DDR3 1333 but then I am sure that the next computer will not be able to use it.
I'm looking at upgrading to the latest cpu with the fastest spinning fan, and about 8Gs of mem or so... :green2
Which OS.. hmmm .. this is a good question - whatdya say on this, mate ??
Maybe I'll hang on a bit until all the sh1t gets ironed out....
:dazzled:
:bg
Van, there is great wisdom in that, let some other DILL do all the beta testing of new hardware. I have long worked on the view of buying trailing edge technology as you get the fastest and most reliable version for a fraction of the price. Did it with a 3.8 gig PIV, did it with the 3 gig quad I develop on and did it with the i7 quad that I have win64 on, all perfect well sorted out hardware.
i7 quad, win 7-64 - Hutch's machine sounds pretty good
not sure i want 64-bit win7 :P
i suppose, if i were buying a new machine, i would get it just to tinker with 64-bit code a little
certainly, any machine you buy nowdays is likely to be 64-bit
not sure how well 32-bit win7 flies on them
there are several editions of win7
i think i would try to avoid the "home" editions and get something called "premium" or "ultimate"
XP home editions were somewhat handicapped - it may not be so bad for win7
sinsi is probably a good guy to talk to if you want to roll your own (he's a gamer :P )
get a m/b that you can upgrade in steps, as desired
add more RAM - later
upgrade video - later, if desired
add a RAID card - later, if desired
that way, you don't have to fork out too much cash up front
you can spend money on the m/b, CPU, and OS, for now
All you need for a decent transplant is a motherboard with usb3/sata3 ($90), 8GB DDR3 ($50) and nowadays some sort of i5/i7 ($100+), AMD are cheaper but for a dev box intel have better SSEx support.
Gaming machine? Same cheap mobo/ram/hdd, expensive vga/psu.
I bought win7 pro oem for $99, so even though I have complained it has survived 2x reinstalls, new video cards, more ram...
32-bit programs run as well if not better under win64, I think because the address space isn't as crowded - a lot of 32-bit dlls seem to be just stubs, so less memory used.
There is still the 4GB limit but a 64-bit OS can give more physical RAM to more 32-bit processes, assuming the RAM is there (mine has 16GB at the moment).
Dave,
I think you can do a much better price in the US, I got ripped off by Microsoft OZ to the tune of $407.00 AUD but the version to have is the black box Ultimate edition that is NOT an OEM version. RE the hardware, when I bought the i7 quad, I just picked the price point which at the time was a 2.93 gig i7 where the slightly faster ones were over a grand each. Put it into a Gigabyte P55A-UD3 board with a good quality power supply with 8 gig of memory, should buy 16 gig while the price is down but I cannot be bothered at the moment.
This Core2 quad I develop on is a faultless machine and I own a mountain of software that runs perfectly on it so I am in no hurry to use the 64 bit OS box.
Dave,
There is plenty of crippled crap out there that still runs 32-bit, or lacks hardware virtualization, Intel is known for selling a wide array of chip variants with a mismash of features enabled/disabled to provide pricing stratification. Most Atom implementations are sold as 1GB 32-bit platforms. Most AMD platforms in last several years support virtualization and 64-bit.
While Win 7 32-bit is probably becoming far less prevalent I'd certainly check what was being sold, as you can't really upgrade 32-bit to 64-bit after the fact without a reinstall, or at least that's how I understand the "Ultimate" version. Machines sold with 3.00-3.99GB, or less, are likely to be 32-bit.
The biggest problem with Win7 is that it doesn't want to run old 16-bit code, but at least with Win 7 Professional you can get a free download of Microsoft's Virtual PC, which includes XP you can run in a box. Personally I prefer VirtualBox, but to each their own. This can be a bit of a bugger if you have to maintain some old code, or systems, using vintage compilers/tools. If you have the sources in a HLL, a quick recompile, and bug fix, is usually all that is required.