OK.... sounds like BootManger has tied itself to XP HDD (not sure why). Reconnect everything, boot Win7, hit Win+R and type "msconfig". Go to the Boot tab and select the XP OS.... hit Delete. This will not actually delete your XP install but remove its entry from the Boot Manager.

If no issues on reboot, then you should be AOK to format the XP drive and move on :)

Would it be better to get an external drive for saving your disk images to, rather than the hassles and risks involved in trying to use your secondary drive?

The advantage with that, is that you could then keep any misc files which [B]you don't need backed up in the basic disk image[/B] on the secondary drive (backing those up separately), keeping any image of the primary drive as small as need be. An external drive is also much easier to unplug when not required :)

He may have joined some time ago, but given the post-rate, I'd say he hasn't actually [I]been here[/I] for most of that time.

As has been pointed out, it is indeed opened with last tool utilised.

Over here is exam period for all the Uni students, so a dent there in free time for them.

[QUOTE=Bob_180_Bob;1050173]P.S. Ensure that you remove any anti-virus program from your PC as they are worse than anything you can get on line. I have it directly from kaninelupus, an expert.
Sorry, this is is my last post about or to him.[/QUOTE]

I love how the self-confessed crippled geriatric adores taking ppl's post completely out ppl's context... about as mature as this drive-by sniping, accompanied by the whole "I'm not talking to you" routine... I'm sure he's only a little boy using a virtual cane to whack everyone with!

[QUOTE=Bob_180_Bob;1050110]I thought that is what I was doing, research, but then all i did was to ask questions and get answers. Now I know a little more than I did before he answered. I thought you were going to argue this fact with crunchie as he disagrees with you. You have your thoughts and he has his, don't come to me telling me what you wont say to him. Either you are right and he is wrong or the other way but please tell him he is wrong don't tell me he is wrong. I believe crunchie and I would take his statements about this as being correct. I dismiss every word you say to me about it as I trust his.[/QUOTE]

HUH? WTF are you on about? The post you are referring to (apart from being unrelated to [I]this[/I] thread) was a disagreement over semantics and nothing more... which was brought up in the actual thread in question if I remember correctly. Kind keep your minuscule thoughts on point, rather than taking a random thread off topic for you own warped benefits... you do the OP no favours!

[QUOTE=Bob_180_Bob;1049637]Two open threads..possible pirate copy of windows!!! see..

Again "Bob", if you can't do anything other than preach over an irrelevant issue, then why bother posting. All he wants is help trying to track down the appropriate drivers for his PC's hardware!

@makaveli7 - please see your relevant thread for appropriate advice... no point in double posting ;)

[QUOTE=Bob_180_Bob;1049628]Your friend has copied his installation disk for you and given you his product key. If he is still using his copy of XP Home, you can not load it to your PC. You will not be able to register or activate it unless it is a pirate copy.
I think you first need to go and buy your own copy of a Windows operating system.
If you have the only copy, he has uninstalled it from his PC and you have registered and activated it in your PC, please tell us the information Microsoft gave you when you rang them to activate.[/QUOTE]

Oh pleeease, you're not preaching again are you "Bob"?? Whether or not the OP is or isn't running a legit copy of XP is utterly and entirely beside the point. He's [B]not asking for a means of bypassing any Windows anti-piracy limitations (has not even expressed any such issues)[/B] so your rant is a time-waster at best.... "Bob"!

It sounds as if the OP has gone from using an OEM XP install (where all the HW Drivers would have been included; to now trying to source and install the drivers him/herself.

@makaveli7 - if this is indeed the case, you don't need to know all the HW models to get started. If it is an OEM (Branded, ie Dell, HP etc), so long as you know your PC's model, you can go to the manufacturer's website and look up your model in the driver downloads page - ...

jephthah commented: take your incessant whining and go somewhere else with it. -1

[QUOTE=Pim;1045133]I am using Windows XP home (which is a 32 bit edition of windows). Reinstalling the operating system, or a different windows operating system is not a solution at all. The problem wasn't there at first, and now it is there, so there must have been some mutation which caused the problem to occur.

I'd like to ask you to stop fighting with each other and help me troubleshoot the problem.

Another thing: as I posted before I found out that the problem isn't necessarily a sound card problem:

The sound card I have is a Audigy LS card.[/QUOTE]

Do you have some idea [I]when[/I] the issues first occurred, or any changes made around that time? Sounds like you've rolled back the last XP service pack, so unlikely to be that. Have you recently installed anything else which may have tipped the balance? Have you tried uninstalling the drivers (via Device Manager) and reinstalling? We really need more info as to what system changes were made prior to things going pear-shaped.

Taking closer look at specs, seems is not so recent at all - my error - which does make things a little more difficult... the sound card is outside it's support cycle, meaning new drivers are a fantasy. It does also introduce an ugly possibility... that parts are beginning to fail (although we can hope otherwise, you do need to consider that.)

[QUOTE=Bob_180_Bob;1042564]Thank you for that, I was just interested in why anyone would look at an anti-virus program for that type of error. Someone did and fixed theirs and now you fixed yours. A lot more people should do a lot more searching on-line before they post a question.
Again thank you for your reply.[/QUOTE]

Again "Bob", you might want to do a little more research on AV erros, in particular in relation to false positives; as well as general application errors and high resource usage. In some cases, the AV can act like a bigger parasite than that which it is s'posed to be protecting the system from. While there are some fantastic AV/anti-malware offerings, there are also some awful products available on the market that far from live up to their descriptions.

What is all that rubbish about?
Anti- virus programs do not attack other programs unless they are a virus![/QUOTE]

Actually "Bob", you might want to do your research on AV's and false positives. The sad fact is that certain AV's (namely Norton and AVG in particular) have a rather bad reputation of falsely identifying perfectly safe (even important) files an processes as being "malicious", neither offering any easy method of undoing said file/process removal. As much as I have used Symantec's [I]corporate[/I] offering for a number of years, this issues was a regular frustration. When I installed Win7 RC1 (which Symantec's Endpoint was not fully compatible with at the time), I have been making use of Comodo's offering. For the first time, I now have the ability to over-ride/undo any file/process which gets erroneously removed/quarantined, which has made life so much easier. Would suggest having a look at what they have to offer.

Hmmmm...... the drivers they supply in the realm of backwards-compatibility are usually buggy as all hell, and are well known for this. Trust me, as one who has long used their hardware (as an anti-Apple evangalist, I long clung to the hopes and dreams that their Zen line would actually squash the iPod trends); I have time and time been sorely disappointed by that particular corporation. They have one of the [I]shortest[/I] hardware support cycles I have ever come across - roughly [B]two years[/B] - meaning new Windows editions are frequently never supported. When they actually [I]do[/I] either port drivers for new Win edits, or backdate their drivers, they often tend to be rushed, and as a result, are bug-ridden.

@Bob - sure a quick Google will give you the surface info/results, but only actual experience will provide deeper illumination as to the actual facts!

It is not a case of being "to advanced for XP". It is a case of many recent components not being [I]supported[/I] for XP... ie, manufacturers/designers [B]not providing any XP-based drivers for their wares.[/B] Yes Vista/Win7 provide hardware-based options which were only at conception form at the time of XP's delivery - CPU-GPU collaboration, hybrid HDD's (ie, turbo caching), many of the hardware accelerations found post-XP.

The simple fact is this; yes some hardware is incompatible with XP [I]solely[/I] on the basis that the relevant manufacturer saw no compelling reason to continue to support that OS in their hardware offerings, but also true is the fact that other recent hardware offerings move beyond the capabilities of what XP is capable of supporting.

[QUOTE=Bob_180_Bob;1044576]God bless you jupiter 2,
How do the error messages described in kb/319595 have anything to do with the posters problem?

"Ctplay2.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

Eacontrol.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

SoundBlaster card needs to be installed."[/QUOTE]

Well given the questionable quality of your usual "advice" offerings, you might want to pull your head in. There is actually some merit to his line of thought....

The OP has listed having [B]4GB of RAM[/B] installed - meaning that is his Windows installation is going to actually be [I]capable[/I] of using all that, he is using XP x64. The biggest problem this OS has always had is that many manufacturers never released more than buggy HW drivers for that OS version.... Creative being leader of that rather ugly pack.

In Win7 x64, MS has finally taken the initiative, rolling out a large number of generic drivers to fill that void, thus making the transition to x64 Windows much easier.... this was never the case with XP x64, and likely will remain that way.

Another line of thought is this:
Given the high-end (and quite modern) specifications of his machine, it is highly likely that he has either bought a system designed for Vista and downgraded it to XP - not a good idea by the way - or has built a system with parts not fully supported by XP. Either way, a ...

[QUOTE=jbennet;1021000]MS should have worked harder to get a good in-place upgrade method sorted out IMHO.[/QUOTE]

I often wonder how many ppl actually make [I]use[/I] of such upgrade paths anyhow? To be honest, have never seen a seamless upgrade install (on any OS) that was picture perfect, or that didn't end up to some degree as a kind of Frankenstein OS install. As to an upgrade from XP to Win7 - remember that a whole raft of software (not to mention all those drivers) which are not cross-compatible... trying to make such an upgrade possible would be nigh on impossible, especially for the average end-user to perform.

To be honest, I always prefer to simply back-up all important data externally and run a fresh install anyhow.... much easier to trouble-shoot if something goes awry on all the subsequent app and driver installs :)

Good luck getting Win7 drivers for an older ATI card... they've always been slack with supporting newer Windows releases on older cards (or even on cards not so old).... nVidia still runs rings around them on that front. You might have to use Google to do a bit of hunting around to see if an "unofficial" driver-stack exists in the wild for your particular card.

OK - that's an overly complex answer for a question which requires a simple answer.

Right-click on image and save.... nothing more complex required

[B]@Gribouillis[/B] - bear in mind that if the OP is even [I]asking[/I] how to source the original image, it makes me wonder if he is even the [I][B]owner[/B][/I] of said image!

Glad to hear mate. Just remember to mark thread as [B]solved[/B] to prevent others from jumping on :)

Well, to put that in perspective, simply relying on an [B]error category[/B] is not always the most precise method, as some initial failures can cause [I][B]cascading failures[/B][/I].... thus the suggestion to deliberately push for a BSOD.

That being said, the "100000ea" error code [I]does[/I] shine a light in the general direction of the cause... your Vid Card. The three most likely causes for the problem are as follows:
[]Issues with device driver
]Insufficient power supply, leaving card under-powered
[*]A cooked card
More info on the error can be found [URL="http://support.microsoft.com/default.aspx?scid=kb;EN-US;q293078"]here[/URL]

Ironically, after an hour hunting after info, almost all complainants for this particular error were on [B]Windows XP![/B] Speaking from someone who's been using both Vista and Win7, both from pre-release builds (and as one who [B]frequently[/B] pushes system to the max), both Windows builds have an advantage in this area. In XP, a Vid Card failure almost always crashes the entire system... in the more recent Windows platforms, the OS almost ALWAYS recovers with little more than a restart to the Explorer process.

Smiles all round - and at least you have a few more tools in your kit-belt for next time. Just be sure to mark thread as [B]solved[/B] to avoid other "Help-Me's" chiming in :)

Sing out if you get stuck again

Use the time stamp as your guide - is difficult for us to guide you on this one as we don't know the exact time you last blue-screened.

As a tip, try pushing system to BSOD and look for an error code with a format similar to this:


Might be a different error code in your case, but this is the sort of thing to look for, and will be mighty helpful in pinning down the likely source of your problems. The BSOD should last long enough to write it down - even better, if you have a camera, take a photo of the entire screen and attach here, so we can pick out the relevant data. Also, [B]directly after recovery and reboot from BSOD[/B], open up event viewer and go to through the newest entries for any details provided.

If looking to the software option, what applications are you running on the new box which was absent from the old system?

System crashes/freezing (especially when triggered by high resource loading), while yes can occasionally be caused by software incompatibilities, is usually a hardware-related issue. BTW, when your system crashes, is it Blue Screening, or simply shutting down? If BSOD'ing, what are the error codes displayed?

Norton, while being a resource hog, shouldn't be affecting the system in this manner. You'd be seeing problems across the board if Norton was the likely candidate.
While installing SP3 is certainly advisable, I'm also not sure this is candidate either. While one or two of the games may have been updated in a manner which creates dependencies to the SP3 upgrade, it is highly unlikely that [B]all[/B] the problematic game have done so. While the OP can certainly try this, would be surprised if this solved all the issues.

While it [I]does[/I] sound like [B]neither[/B] stick of RAM is all that healthy, it looks as if there may be other issues contributing.

Have you checked to ensure you have the latest drivers for your Vid card?

Also, while RAM is playing up, you might want to bump up the size of your Page File (virtual memory) to help carry the load

No probs - glad to hear things back on track :)

BTW, got a mental block on the technical term, but the hash [B]#[/B] at the start of the line ensures the following text is inactive - used where descriptions and examples are provided.

Don't stress... is just fine :)

The original "hosts" file actually has no file-type prefix... but it also has no active content from memory. If you are really worried, here's how to recreate new Hosts file:

Open Notepad (open start menu, go to Accessories, right-click and select "run as Admin"
Copy/paste content from link I gave you.
Go to the File menu, and select "Save As" -> enter Hosts as the name (no file type) and ensure "ANSI" is set as encoding.
Wala - you have successfully recreated the Hosts file.

Windows doesn't activate the Hosts file by default. Am too tired to go into a full definition, but here is a Wiki for a (rather technical) definition... Google for something more understandable. Is most commonly used for local domain redirects, but is all to commonly hijacked for more malicious intents.

BTW, Hosts.old is simply the original Hosts file, with a ".old" prefix added so is retained but deactivated (rather than deleting). The tool linked in the site I posted will do exactly the same... is it recommends either using the tool [I]or[/I] following instructions to reset manually, not both :)

Which Win x64 by the way? Remember XP x64 was 1st-gen move to the x64 environ, where have made the move to x64 in Win7 very smoothly.... anyhow.

The fact that things are crashing under high loads does suggest one of two likely factors - [B]hardware [/B]or [B]drivers[/B]. Now finally managed to source specs for your drives (took a while, but lopped the last sequence in the drive names provided), and both, being Caviar Blue's, should be more than up to the task. Vid-card also should be up to handling things (although you may still not be able to use max-resolution on high-resource games even still). I would however recommend checking that you have the latest display drivers, as updates often tweak both performance and stability.

Other component to consider is your RAM. Faulty RAM can cause all sorts of freezing and crashes. In the case where you have two sticks, it may be that is only shutting down when system is trying to use more memory than faulty RAM is capable of handling.

Easiest way to test, is shut-down Windows, remove [B]one stick of RAM[/B] and reboot, and run problematic games. If issues re-occurs, try again with other stick. If RAM is functioning as it should, high loads should only induce sluggishness, not a complete freeze or crash.

Also consider that not all RAM is created equal. If you are using PC as a gaming system, you're best off investing in [B]gaming-class RAM[/B]... G.Skill and Kingstone's HyperX series present ...

smitty260 commented: Thank you for helping me with my computer problem. Hopefully it can be 100% fixed. +0

[B]remove anything to do with Mirar[/B], and allow HijackThis to fix following lines:

[]R1 - HKCU\Software\Microsoft\Internet Explorer\Main,Search Bar = [url]http://www.mirarsearch.com/?useie5=1&q=[/url]
]R0 - HKLM\Software\Microsoft\Internet Explorer\Search,SearchAssistant =
[]R0 - HKLM\Software\Microsoft\Internet Explorer\Search,CustomizeSearch =
]R1 - HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings,ProxyOverride = .local
]R0 - HKCU\Software\Microsoft\Internet Explorer\Toolbar,LinksFolderName =
[*]O1 - Hosts: ::1 localhost
Lastly, read here[URL="http://www.removevirus.org/how-to-guides/how-to-reset-hosts-file-xp-vista-windows-7/"]http://www.removevirus.org/how-to-guides/how-to-reset-hosts-file-xp-vista-windows-7/[/URL] and follow instructions on resetting Hosts file, as appears to have been hijacked

Will check back in later, as have to go out :)

OK - a few things am noting in your HW config that already puts you behind the eight-ball, performance wise:
[]You may have 4GB RAM [I]installed[/I], but a 32-bit Windows install is only capable of using around 3.3 max - thus the " 3328 Megabytes Usable Installed Memory" notation
]No listed GPU (Vid Card)
[*]No info provided for RPM of hard-drives (or write speed), [I][B]both of which are important considerations on a gaming box.[/B][/I]

From a software side, do you have the right DirectX versions installed and up-to-date?

Also, although am not familiar with those [I]particular[/I] games, but do know that already quite a few more recent game releases are simply not fully compatible with XP, and never will be, especially now as Win7 is far more optimised for usage as a gaming system.

majestic0110 commented: This is all true! Good points :) +6

How'd you go with those scans?