Hi Datadocen
It is likely that you are aware of some of the issues my answer will touch upon but I will include them anyway, because they will probably be of relevance to most XP users. I am also conscious that others experiencing similar issues might come across your question and the related answers while searching for solutions, as you have.
One main constraining factor for XP users is that its built-in IE browser tops out at IE8. XP will not upgrade to newer editions of IE beyond IE8. Increasingly browser technology is veering towards compatibility with tablet and smartphone technology, so browser interfaces are updating rapidly to keep up with the mobile internet devices that an increasing number of users require. It is of course possible for you to use XP with alternative, more up-to-date browsers such as the latest versions Firefox, Google Chrome, Safari, Opera, Avant, Wyzo and others.
Another pivotal issue is, as your question implies you already know, that all Microsoft support, automatic updates, service packs, application upgrades and security patches for XP, IE8, .net framework (for XP), and MediaPlayer (for XP) will cease from April 8, 2014 onwards, which is almost exactly 4 months away. Depending on the approach that Microsoft decide to adopt, the termination of support could also have a negative impact on the availability of XP compatible device drivers, which could hamper users needing to do fresh reinstalls of XP, without dedicated device drivers on disc or saved on storage devices.
On the issue of XP automatic updates, security patches and service packs, sometimes these cannot be installed out of sequence, in the sense that to upgrade from state a to state c may not be possible without first updating to state b. This does not apply in all instances but it certainly applies to some updates and patches and certain aspects of XP service packs and can lead to irredeemable corruption of the registry or the entire operating system.
On the issue of service packs, XP SP1 cannot function properly on today's internet because of its browser limitations. IE6 has serious, widely acknowledged security flaws and is no longer supported by some browsers.
The RAM limit in XP is a BIOS issue that can sometimes be resolved via BIOS updates for your computer's motherboard. There are however, some motherboards on which this is impossible and the 3Gb RAM limit cannot be exceeded.
Slipstreaming and unattended installations are only viable when the number of variables are limited. The huge volume of updates, patches and new utilities spanning XP SP1, SP2 and SP3 updated to December 2013, creates too many variables for you to efficiently, effectively and accurately script a foolproof selective automated updating methodology. The most likely outcome with any attempt at this will be a corrupted and/or stalled or aborted installation.
The firmaware and BIOS built into modern components' and devices' controller boards and motherboards often make them incompatible with XP, causing aborted installations and the problem will become more acute when support for XP stops. Computer component and device manufacturers will stop producing device drivers and firmware that will be recognized by XP, making increasing numbers of processors, motherboards, high speed RAM modules, ultra high speed Hard Disk Drives and Solid State Drives incompatible with any version of XP, no matter how it is configured. It is possible that this is the reason for the difficulty you have been experiencing with installations on your SSD. Many of today’s latest desktop and laptop motherboards will also automatically abort any attempted XP installation.
The best solution for you ultimately, if you wish to keep using XP, would probably be to network and file share your XP and Win 7 devices and use the Win 7 system for online use and the XP system for offline use, for as long as the XP hardware, software and utilities maintain normal functionality.
I recommend lots of restore points and user data backups leading up to and beyond the April 08 2014 deadline.
If you have not already done so, I would recommend that you join the Microsoft Community and make full use of the Support Services available from the community, some of whose members might be able to offer you some additional insights.
http://windows.microsoft.com/en-GB/windows/end-support-help
http://support.microsoft.com/contactus/?ws=mscom
I hope this helps.
Rgds
Stoic
Update:
As I explained in the introduction to my answer, my answer was a broad-based response to your question, without the benefit of in depth knowledge of your hardware setup or background knowledge of your expertise in IT. I always answer these questions comprehensively, making no assumptions about the experience of the asker and with a thought to anyone with similar problems (but perhaps without deep IT expertise) later coming across this question online and using the answers provided to try to solve their problems. So, my answer was for you (who is not willing to adopt 7), where relevant, and also for anyone else with similar difficulties to yours but less IT expertise (who might be willing to consider 7).
Your additional background gives a better picture of your capabilities and of what you have and have not tried. So it is now easier to give a focused response specifically to you, to add to the generalized answer I gave before.
So I'll now address the points in your follow up comments.
The people who suggested Linux, 7 or 8, did not offer "incorrect" solutions to your question, they just offered 100% effective solutions that would resolve all the issues you raised, but that you are not prepared to consider (which is completely your prerogative) because you are committed to XP (which is completely your prerogative).
The RAM limit in XP is a BIOS issue in older machines (I had no background information on your hardware from your original question) in that it can be resolved with BIOS flashes and/or updates, if they are available for the motherboard concerned. For newer machines it might not be a BIOS issue. I have updated several motherboard BIOSs to recognize more than 3Gb in XP. Your motherboard either will or will not allow it. There might be a way of fooling XP SP3 into accepting a higher RAM limit but my answer was not given in the context of hacking. In a hacking and recoding context, the possibilities are endless and are best discussed on hacking forums, not here.
I did not claim that SSDs are impossible to use with XP, just that there may be immediate compatibility issues with certain models of SSD and ultra high spin speed HDD. Nor did I claim that it would be impossible to slipstream XP updates and patches, just that it might be problematic. If you are willing to laboriously manually compile a preferred combination of updates laboriously by trial-and-error, then there is nothing to stop you from creating your own updates slipstreaming protocol and burning it onto a DVD as a disaster recovery tool.
My point about IE8 was advice for anyone with a similar problem to yours who happens to be emotionally attached to IE even tough there are alternative browsers (just like you are emotionally attached to XP even though there are alternative OSs).
I am unsure about your rationale in saying that the other browser alternatives (which I did mention in my original answer) would definitely be viable with XP SP1 or a modified variant thereof (which is what your question suggested you wanted to try). I believe the latest browser technologies and the very latest essential browser utilities and their updates (java, flash, shockwave, etc.) also require certain features that only exist in SP3.
Browser technology will obviously keep evolving. Browser dependent utilities will also keep evolving. Malware threats to browsers and OSs will also keep evolving. I am not sure I understand how you intend to stay ahead of all these 3 curves with no further XP compatible updates from utilities providers and no more updates and security patches from Microsoft, unless you intend to and have the ability and time code your own future updates and patches.
I don't share your apparent confidence that post-2014 browser, browser utilities, antivirus and antispyware updates will not potentially expose an essentially static OS, devoid of any updates and security patches, to system instability.
As for drivers, there are several freeware compilations containing between 100k and 250k or more device drivers for XP and other MS OSs available for download online. A retrospective driver library should serve you fairly well. The only potential driver problem could arise if a future graphics card upgrade to keep up with future developments in video streaming and flash technology needs XP drivers.
My networking suggestion was based on the future browser and updates/security patches issues I mentioned eventually making some websites eventually become inaccessible if you insist on confining yourself to XP. One occasionally hears about people with machines running '95, '98 ME and 2K, but not that some parts of the internet are inaccessible to those using such machines (such as considerable parts of YouTube).
Anyway, you have my answer. Comprehensive XP driver libraries are available. A manually compiled custom updates library is feasible. A slip-streaming protocol for all of the above is technically possible. I do not believe that XP SP1, even with modifications, is viable for long term, universal internet access after 2014. I also believe that the lack of updates and security patches post-2014 will inevitably result in diminishing internet navigability.
I don't see any other solutions available to the question you asked.
That's my answer. It's the best I can do. Good luck.
Stoic