TELVM

I missed this party, better late than never. To test if a PSU is alive out-of-comp, we jump-start it with a paperclip or piece of wire bridging the green wire (PS-ON) with any black wire (ground) on the ATX20/24 connector. _____ Though the Corsair CX430 is miles better than the original junk that came with your comp, beware that on this 'entry-level' model Corsair most graciously fits low quality chinese crapacitors in the secondary, that might not last long once warranty expires (3 years for the CX430 I believe).

Not worth the trouble IMHO to sacrifice half the L2 cache. I'd better overclock the Cumine 850. I'd steer clear of the 1100/1133 Cumines. I'd get a 1000/133 and then OC the hell out of it. _____ For the paleontological interest, with a bit of tinkering you can run a Tualatin on some Slot-1 boards. _____ Attack of the mutant Tualatinsaurus-Rexes : http://www.vogons.org/viewtopic.php?f=25&t=42416 http://www.vogons.org/viewtopic.php?f=46&t=32786 http://www.msfn.org/board/topic/155832-resurrecting-a-1999-vintage-win98se-machine/page-3#entry1003131

^ You know what those Windows 1.0, flat, monochrome, low contrast, hieroglyphic icons look like? Low-visibility insignia, "... used to increase ambiguity ... and to avoid compromising the camouflage ...". Exactly what you need for UI ease of usability.

The 'Pro' version of SSD Tweaker can manually TRIM many brands of SSD.

^ An intriguing notion, I have no idea. For what it's worth, this guy tested that Se7en's chkdsk.exe doesn't work on XP.

A solution to cap x64 Se7en's chkdsk /r runaway memory usage: https://lowleveldesign.wordpress.com/2013/11/21/set-process-memory-limit-with-process-governor/

Microsoft to double price of XP’s post-retirement support

XP is much nicer after switching to some non-Playskool theme like Royale Remixed.

Yep the PAE overhead adds some drag, specially in floating point performance. See this comparison of Se7en x86 vs x64 running Linx, both on same system with 16GB of RAM: http://www.msfn.org/board/topic/171177-xp-to-vista-is-it-worth-it/page-3#entry1075735 That said, in typical use the 'seat of the pants' is very similar. Yes, plus the overhead from the ramdisk application. But you may not notice any extra drag. In fact if you move the pagefile, enviroment variables %TEMP% and %TMP%, etc. to ramdisk you'll most probably feel it faster.

And you've not even bothered to disinfect your SSD to install XP on it.

Now I get it, by refusing to submit and be assimilated we're bursting the man's housing bubble. Astroturfers gonna astroturf.

Don't use a repair disk. Easiest way is to partition/format the SSD from Disk Manager on a running comp with Vista/Se7en installed. ^ Here a 120GB SSD with a single 100GB NTFS partition, and the remaining space unallocated (for over provisioning). I could format that partition, unplug SSD from Se7en comp, plug into XP comp, and start installing XP. It would show as 'C: Partition 1 [NTFS]' or alike in the XP Setup. Then I'd select that partition, and choose 'To set up Windows XP on the selected item, press ENTER'. Thus XP would install on a correctly aligned partition, and run like a monkey from SSD. Or I could directly paste a system image of XP from old HDD into the new SSD. (Of course instead of just a single partition, from Vista/Se7en Disk Management you may create as many partitions as you like, and/or leave no unallocated space for over provisioning, etc. At your leisure.) Another way would be using Gparted from a CD or similar to partition/format and correctly align the SSD before installing XP. And yet another way would be re-aligning XP after installation, with something like Paragon Alignment Tool.

Allow me to share this, I believe many habituals to this thread will find it interesting and humorous. After watching the world famous Chris Pirillo's Dad first testing on Windows 8 video, this aussie kid grabbed his mum and subjected her to a similar torment : As you would expect the lady was seriously traumatized, but survived the ordeal. Since then mum has tested , , , , , , and . And even , , and . Here her first impressions on Windows 10 Build 9841: How many teenagers do you know that tinker with PC OS's way older than them just for the pleasure?

^ You got it right. All the 'disables' are to spare writings to the SSD, but this ain't so mission critical with today's SSDs, so if you're particularly fond of any of those services you may let them activated (except defrag, defragging SSDs is usually not a good idea). Correct partition alignment and manually TRIMming are more relevant. Under heavy SSD usage manually TRIMming more frequently would be better, say once per day. Under normal use once a week will be fine. Beware some SSD makers like Crucial don't bundle a software tool for manually TRIMming, make sure the SSD brand and model you get for XP/Vista comes with such a tool. Don't worry, lots of people succesfully run XP from a SSD. If you got a comp with Vista, first plug the SSD into that comp to partition/format it like any HDD. Unlike XP, from Vista onwards Windows aligns partitions correctly by default (see here). Once partitioned/formatted, then either unplug SSD from Vista comp, plug into XP comp and install XP normally (preserving the partition/s), or just paste on the SSD a system image of XP from HDD. XP will run from a SSD with non-optimal partition alignment, but reads/writes will be slower and you may experience occasional 'stuttering'. Another healthy trick for a SSD under XP, without native TRIM, would be some overprovisioning. When partitioning the SSD just leave some unpartitioned space as 'strategical reserve', say if the SSD is a 128GB one, partition just 100GB and leave the rest unpartitioned, blank, to help with SSD housekeeping (TLDR on overprovisioning SSDs).

XP can't TRIM by itself, however we can manually TRIM SSDs under XP from some applications bundled with SSDs (provided the hardware ain't too ancient). I've tested the TRIM button in Corsair SSD Toolbox, OCZ Toolbox, and Samsung Magician under XP with success and no explosions. Extra touches to help SSD life under XP: - XP can't align partitions correctly for SSDs, so better partition and format in advance in another comp with Windows 7, then install XP. - Disable prefetch. - Disable indexing. - Disable hibernation. - Disable scheduled defrag. - Disable pagefile, or move it to an HDD or a ramdisk. - Let the system idle logged-off for an hour or more from time to time, so garbage collection can work.

I think having CEIP deactivated and of course discarding KB3021917 safeguards Se7en from this 'performance improvement' (my foot ).

^ Epic.

JorgeA, to here your servant the true intentions behind this 'generous freeness' are crystal clear.

^ :lol: . Microshaft vs the non-retarded users, round three. Seconds out!!! The tool that brings back some sanity, banned. What does this tell us about what can be expected 'beyond the threshold'?

Thought this would be appreciated here. Flat Design Is Going Too Far Epic comments:

That's ~30TB a year from OS housekeeping only ... Has Microshaft started selling SSDs or something?