JedMeister

My initial reaction is "of course it'll work!" but I must say that your research that found that the versions had "MAJOR programming differences" really surprises me. I have no idea why they'd do that. I was under the impression that all English speaking versions were the same (just set your language/keyboard/locality setting, etc) and it is just (non-English speaking) localised (eg Russian, Chinese, etc) versions that were different, and even then the differences were only skin deep (ie many references and labels in the local language). It sounds I may be wrong. The only reason I could see MS making "MAJOR programming differences" would be to comply with some specific UK or EU laws to release it onto the UK market. But if so I would imagine that it would be documented somewhere.

I have no idea what Vitas just said (I'm not up with Chinese - I struggle with English - hehe!) but I suspect you may have troubles there! the only way you'll get it to work is if you find out the chips used and get the drivers from manufacturues or other third party vendors. Then you'll probably need to hack them to make them install (although could raise legal issues - ie breech of license). Have you asked Acer? I had a friend who had a similar experience (although I don't think it was Acer...) and was directed to a similar model, from which the XP drivers 'should' work. I'm not sure how it went as I haven't spoken to him since then. Could be worth a shot.

XP has a "Files and Settings Transfer Wizard" which has varying levels of success. I'm sure Vista has a similar tool (which I would hope would be a little more successful). I wouldn't recommend trying to get your current OS to run on your new hardware. Whilst its possible, my personal experience has been a fairly unstable PC. Someone else on here may know of some tool or something that will allow you to do it (although there could be legal issues if its an OEM OS). The programs themselves may have some way of exporting their config and settings, if its not obvious then perhaps you can contact the vendor for hints. For the cleanest install and with maximum chances of everything working ok, I would suggest you bite the bullet and just do a clean install of the lot. [edit] Another option I just thought of that may be acceptable is converting your current PCs OS to a virtual machine and run that inside your new OS?

I could be wrong but I'm pretty sure that whilst one of these may be guilty, it could be any software installed on your PC that hooks into explorer.exe. So your list of possibilities is not limited to entries in your context menu, although if they appear there they definitely do! Even with your list, without version numbers, you can't be assured that your comparing apples to apples. For example I have a copy of WinRAR installed which causes me no problems, but you may have an earlier or later version that had/has a bug that could cause a crash. Just to complicate the issue, it could be caused by a combined effect of two (or more) apps interacting poorly. The only way you'll be able to figure it out, is if you get some of the Win gurus here to check out your dump file or do what crahak suggested and disable shell extensions using something like Autoruns. I'd do a full system scan using your current tools, and for good measure try some 2nd and 3rd opinions (such as Spybot, BitDefender online scan, AVG AntiRootkit, etc). As crahak says shell extensions often do bad things, and it doesn't get any badder than malware! [edit: poor grammar]

I have no idea. I am running SP3 and its still there on mine (actually I've got it twice, one in drivers and one in dllcache). For interest its version 5.1.2600.0 (so XP SP0). I installed SP3 redistributable version (ie full version ~300MB) over the top of SP2. I think I just downloaded mine from the main MS download. So not sure even if its the same one as you have, I'd assume they'd be the same (but I could be wrong). I'd probably be a little concerned that its gone. Although, personally I'd probably just copy it across from somewhere else if you can, and see if that works.

This is possible in XP, but you need to hack a system file and I'm not clear on the legality of doing that. I suspect that it would be a breech of your license. So that leaves you with nitroshift's suggestion. If you must use RDP then you'll need for Server 2003 (or 2008 no doubt does it too), which allows you to do that. I'm not completely sure but I think it may even allow more than 2 simultaneous loggins.

Have you tried it in safe mode to reduce the cahnce of it being something else interfering? (Probably a long shot but worth a try). Personally I'd try using something like a Linux LiveCD (check you get one that supports USB external drives - I think most would but pretty sure Ubunutu does) or a BartPE CD (UBCD4Win[.org] is probably the easiest way to make one if you don't know what I'm talking about). If that works perhaps you need a clean install, or if that doesn't work it sounds like hardware issue (motherboard?).

PCLinuxOS - but I voted Mandriva as that is what its derived from. I've tried Ubuntu a few times before and run into issues so given up and gone back to windows. Finally I pushed through the 'pain barrier' when I bought a (ASUS custom Xandros based) EeePC and tweaked it to just how I wanted it and learned a huge amount into the deal. Since then I haven't looked back and have downloaded a huge amount of distros to install on my new system that I am building. I came across Mandriva in my travels and I really liked it, then I found PCLinuxOS (a Mandriva derivative) which I really like. One of the features I really like is that you can set it up and create your own custom install CD from your setup fairly easily (I haven't tried it yet, only read about it so can't say to much yet). Basically it is similar to imaging a system but it is 'universal' and not hardware defendant (as images are). So once you've set your PC up haw you like it, you can share it with your friends (it can boot as a Live CD or as an install disk).

[edit] Sorry about the really long post - it wasn't intended - I just got carried away! [/edit] When you say "freezing" do you mean that fully locks up (it freezes indefinitely - and you need to press the reset button and reboot) or that it becomes unresponsive for a while and then comes back? If it requires a reboot, then I'm with these guys above. If you've done a clean install and you're still having problems, then you're problems most likely are related to hardware and/or other external sources. If you get any BSODs then copy the STOP codes, they may help you to troubleshoot. If you get random reboots you will want to turn that off (so you can read the STOP codes off the BSOD). Search (google or this forum) for instructions to do that, its easy. If its just becoming unresponsive then check in task manager what is chewing up your CPU cycles. Or better still download Process Explorer (google it - it's owned by MS and is a fuller featured task manager). That should help you troubleshoot. Also check to see if there are updated drivers for your hardware. Hardware issues could still apply though (still likely because you have a clean install). So, its probably worth testing your hardware as follows (try all of this if you are experiencing lockups, some of it is less relevant if your system is just unresponsive): HDD: - Run checkdisk - type "chkdsk" (no quotes) in a command window (Start > Run > type "cmd") note: You will only need to do this if you did a "Quick Format" on install as it runs automatically at install if you do a "Full Format". - Use a utility such as HDDHealth to check the health of your HDD. This app allows access to the SMART data on your HDD which will let you know if there are specific problems. It's not 100% and can give false negatives (ie says its fine but its not). I've never known SMART to give false positives (ie says its bad and it isn't). RAM: - As eyeball says run MemTest! CPU (&RAM): - Try using a stress test of some sort (the ones used by overclockers to test system stability - such as Prime95) to try to diagnose heat/power issues with your CPU (often these tests stress RAM as well so test that as above first). Other hardware (and software such as drivers etc): - Test in Safe Mode. Safe Mode enables only the base hardware and uses generic Windows drivers. If that helps, use msconfig (Type "msconfig" in a command window) to disable and enable services and startup apps to find the culprit. - If you have an after market video card and onboard video, try removing it and see if things change. If you have onboard video only or add-on card only, see if you can borrow a vid card from a friend. - Remove any other add-no cards and test your system without them. - Check all plugs and cables for any that are loose. - Remove dust and grot, especially from fans and heatsinks. Freezing can often be caused by overheating. Clean out air-vents to ensure good airflow through your case. Obviously do any hardware changes with the machine turned off! Hope this helps!

I think having Docs & Settings on a separate partition is a good idea. Having your system temp directories and pagefile on different partition is probably a good idea too as you won't want to waste image space on stuff like that. As for the program files directory, having that on a separate partition seems like a silly idea to me. That is unless you're going to backup and restore the registry at the same time as you restore your image, which sort of half defeats the purpose of restoring an image (as you'll be restoring a potentially gunked up registry)! Some of your updated programs may work, others may not (as they will rely on updated registry info as well as updated data in Program Files). If you really want to run with this plan, then my suggestion would be to keep copies of all the .exes of the updates and new progs you install, then when you restore your old image, update all your progs and reinstall any new ones, reinstall any MS updates and then take a new image (ready for the next time you restore an image). This will keep the image more up to date and mean less work required to get you back to where you were prior to your last image restore (less any unrequired gunk). To be honest though it sounds like a lot of work to me. I prefer a clean install every 2 yrs or so.

Perhaps then it is the Windows Removable Storage drivers that are corrupt rather than USB drivers. Perhaps its worth running System File Check utility ("sfc /scannow" at the commandline) to check all your Windows Files are ok? Not sure if that checks the generic Windows drivers but worth a shot. Be aware though it will overwrite any patched files (if you have them - such as tcpip.sys and uxtheme.dll) with Windows originals so you will need to re patch them afterwards.

Congratulations on both counts!!

Hmm, so from your comments it seems that they exist in Device Manager but not in Disk Manager? Got me stumped. I was hoping that it would show in Disk Management but not Explorer, I've encountered that before. This one I haven't come across before and I'm not sure at all. Sorry

They will be in i386 but not sure exactly where, you'll need to go digging!

First thing to check is device manager and make sure there are no exclamation marks. Perhaps your USB 2.0 drivers have been corrupted or something? Only guessing really. Try uninstalling all USB drivers and restart.

I haven't come across that issue before. Do they exist in Disk Management (Right click My Computer > Manage > Disk Management)? As for the appearance. I'm pretty sure that SP3 updates UXTheme.dll so you will need to patch it again (I assume that you were using a non-signed theme and its now reverted to 'classic theme'). Most of the changes in SP3 are 'behind the scenes' and are not meant to make any UI changes.

UBCD4Win is an easy BartPE style environment to build with little or no knowledge. Have a look at www.ubcd4win.org. You can then follow the above advice to save your system (assuming you've gat a non-corrupted restore point).

I use a freeware prog called WinMerge on to keep my portable drive synced with both a folder at home and one at work. Could be a bit painful if you had too much stuff to compare though.

My advice: Get used to it, or; Copy everything you want to keep off C:. Disconnect all drives other than D: (the one you want to be C: on your new setup). Install Windows to the new C: drive. Reconnect all other drives and configure to desirable drive letters using XPs built in Disk Manager. PS what you want to do can be done in theory, but it will bring you a whole world of pain. It would probably take you the same time to do a clean reinstall of Windows 5 times over!

Has it always been like this and you've just decided to do something about it? Did it suddenly start doing this sometime recently for no apparent reason? When you say you've tried all available power setting options did you mean in the BIOS too? I would run memtest too, to check that your ram is ok.

+1 for what crahak said!

I'm not sure but a quick google, suggests to me that possibly you've been duped by a nasty "rouge" spyware/AV application. From what I just read, whatever you do, don't buy the app that told you you have this infection. Either do what I did and search google, or download some good freeware anti-malware like Spybot S&D, Adaware, Avast/AVG. Also there are some good online AV scanners (good for a second or third opinion) such as BitDefender, Panda and Kaspersky. Finally can't go past HijackThis, although you'll need someone knowledgeable to help you with reading the log and helping you fix it (you can break stuff if you do the wrong things - there are many forums where people will help you - maybe even on here, not sure). Good luck!

That is absolutely crazy! Got me completely beat!

For me personally I like the modified version (ie finished) version of Royale-Noir. I even quite like the orange/black of zune (but it gets a bit much after a while). On older machines I work on I always set it to Windows classic for best performance though.

I doubt this will fix your login problems, but but may fix your iexplore.exe hanging problem. I had a similar problem some time ago that was introduced by an update (strangely it only happened on some machines though, not all) and I found an MS hotfix which solved it. Sorry I haven't got it handy so you'll have to do some searching. When I get a chance I'll see if I can find it and let you know the KB number. In the meantime, happy hunting!