ChiefZeke

The MD5 is 1E73B24A89ECEAB9D50585B92DB5482F of the one listed as version 3.0 which I downloaded earlier today.

Go to www.cyberguys.com for the online catalog of the items listed above. Probably easier to find here than at your local computer store.

Did Dell provide a CD with the system or did it come with a recovery parition which can be used to install everything back to original factory conditions?

The recovery partition is designed to return the system on which it was installed back to its original condition as it came from the factory - you cannot just move the drive to a different computer and expect it to work. the install/setup routine is designed to look for a particular motherboard, cpu, etc and won't work on a different system; unless that 'new' system has exactly the same components as the original. If there is a way around this someone here will point out how that could be done.

I did a Google search on mup.sys and found quite a few possible reasons for your problem - too many to post here.

.NET Framework 1.1 is on its own. .NET Framework 3.5 will install 2.0, 3.0 and 3.5. .NET Framework 4.0 is also standalone. Once installed appropriate updates can/will be applied.

Try the Rogue Spear drivers and don't use Mass Storage; http://www.doitrightconsulting.net/forum/index.php - might make a difference.

You can download the Mass Storage Driver Pack from http://forum.driverpacks.net/ and integrate it into your XP CD using the Driver Packs Base program: DPs_BASE_10111b29.exe (found in the same forun). The Mass Storage Driver Pack has the latest AHCI drivers and will provide the drivers needed during the installation routine. Driver Packs and the Base are compatible with nLite.

There is no wireless video card/adapter or monitor on the market today - answer , for now, is no.

Check AutoPatcher - it may do what you want. (I am not familier with the programs you mentioned so this is just a guess.) http://www.autopatcher.com/forums/

Google for a program UltraMon - it comes in 32-bit and 64-bit versions - it may help.

The info on EasyBCD indicates it should work on 98/2K/XP - Google search should indicate download location. Latest is: 2.0.2

You should be able to find info on the drivers you need here: http://forum.driverpacks.net/ They will post up-dated drivers for just about everything and they are easily integrated using nLiet or the RyanVM Integrator - http://siginetsoftware.com/forum/ and http://www.ryanvm.net/forum/

As the name implies - it 'repairs' Windows back to its original state with the exception that it makes no changes to the other software you may have installed - thereby saving you the time and effort of installing all of the other stuff you have on your system. Depending on the verion of Windows involved you could have 'updated' the original Windows CD via slipstreaming/integrating any updates that came out after the release of the original CD so that the 'repair' is as up-to-date as the updates rather than using the original CD whcih could be months/years out-of-date. A Google search of 'slipstreaming' will provide further info on that subject.

There is a perfectly capable program to use to slipstream/integrate Office 2003 and all updates; see: http://siginetsoftware.com/forum/ to download the program and updates.

Messenger 4.7 was the default install but Messenger 7.5 is available as a download from Microsft. Also, you need to upgrade your version of XP to SP3 - SP2 is no longer supported.

My install of Win7 64-bit on a 250Gb partition takes up 25Gb of space - includes Office Home and Student 2010 plus a number of other programs.

P.S: some users find difficulty when rt 7 lite installing only in C:\ I will change this settings and rt 7 lite can be installed in any partition and you can launch from that. And those of us that have Win7 installed in drives/partitions other than C:\> are ready to test things when the updates/changes are made.

This program only works if you installed Win7 on the C:\ drive - and from what you posted above about error messages, if I read things correctly, you installed Win7 on the E:\ drive. The fact RT 7 Lite mandates the user to adhere to their requirements, specifically - install Win7 to the C:\ drive, prevents many users from adopting the program. This issue has been mentioned to those responsible for the program and their position is: Tough!!! It's your problem - not ours.

When the PSU went and maybe took the video card it could have affected the motherboard video card connector itself - burnt some of the internal parts of the connector. It would be very hard to visually look inside the connector for scorch/burn marks but you could try. I'm assuming the motherboard does not have onboard video which could be turned on to check things out? Motherboard have an onboard POST code indicator?

My initial guess is the power supply died and, probably, in the process it took out the motherboard and the new video card. The new video card - did it come with specifications for the required size of the power supply? First, check the power supply for a fuse. Probably not there but won't hurt to check. If you're familier with electronic parts/devices look for leaking/bulging capacitors, burnt/scorched items on the motherboard/video card, odor of electronic items that were overheated.

Did you check the Event Viewer to see what 'event' could be causing the problem? Administrative Tools > Event Viewer

Windows always uses all core unless you REDUCE the usage. You see the ReadyBoot effect: Not to dispute what's been said, but that's just not my own experience. On my main system, I'm running Windows 7 Ultimate 64 and I have an AMD 5200+ dual core CPU. I had to tell the stupid OS that there are two cores or it would have remained forever set to just 1 core. Windows is SO stupid. On my Acer Aspire ONE Netbook, the Atom processor comes up in the config page, (the one listed above) with two cores, but as usual only one was selected. I set it to 2. On my 8 yr old AMD 3000+ (single core) CPU, the config box showed ONLY ONE core, which is correct. It would seem, from all of this that if you (or somebody) doesn't tell Windows how many cores you actually have, it will run on just one, till the cows come home. Cheers Mates! B) Your situation does not apply to everyone. I have an ABIT IX48GT3 motherboard with an Intel Core2 Quad9650 cpu with XP Pro w/SP3, XP Pro x64 w/SP2, Win7 32-bit, and Win7 64-bit installed and at no time did I have to tell any of the versions of Windows how many cores I had. The installation routine of all four operating systems recognized the type of motherboard and cpu combination I had and installed the necessary drives and when the install was finished Device Manager had the correct information. So, don't blame Windows for what appears to be a hardware discrepancy in place prior to the operating system being installed.

I have two monitors and have had a similar problem. What I had done that caused the problem was I had started a program and moved its window to monitor #2. I then turned off monitor #2 forgetting to move that program's window back to monitor #1. Next day I booted the computer and started the program again but this time I was puzzled - where had the programs's window gone? It took me a while to remember I had moved the program's window to #2 monitor - so I simply turned on #2 and moved the window back - problem solved. My guess is - you had moved the now missing program's window to your #2, shut the system down, disconnected #2 monitor and now, without the monitor connected you can't get the window back. I know you probably don't want to do this but the easy solution is to reconnect the monitor, turn it on, the missing window should be visible, move it back to #1, turn off #2, and now disconnect it from your system. Long way around - but it works.

So the man claiming performance gains by altering the core# in startup options was clearly mistaken then? Anyone? Chief? I have no idea as I am not familier with the chip in question. I just mentioned the hyperthreading as a possibility if that is really a selection in the BIOS. There are those that do confuse dual-core and/or hyperthreading as meaning the same thing though they are not. In some case you can have dual or quad core cpu's and a hyperthreading option also - which results in the system 'seeing' eight (8) processor's if quad-core and hyperthreading are both available.