You can download knoppic in .iso format and burn to cd,
Quads
Rossonero,
Your files will be okay. Obviously you will need to update Windows & Media Player afterwards but that is about it.
Just wanted to update everyone on this issue. Thanks to Quads' and blec's help, I think I've managed to get this resolved. First, I used the Windows XP Installation Disc to perform a repair install. As blec stated, of the three options that are presented when you boot from the CD, choose the first. The CD will scan your hard drive, see that you already have a copy of Windows XP installed, and ask if you'd like to repair the current installation or proceed with a fresh installation. Since I wanted to preserve my files, I chose to repair the current installation. It looked a lot like a typical XP installation from there, and takes about 30-45 minutes or so. But, one important difference is that your files are preserved.
The installation appears to have gone smoothly, and Windows XP now boots up completely. No more BSOD! My files all look like they're in place as well.
I can't thank you enough for your help!! As an aside, I contacted Symantec tech support via chat before coming to this forum, and they were nowhere near as helpful. I described my issue with the same level of detail that I did in my original post here (word for word in fact), but they continued asking questions that I had already answered and suggesting actions that I had already attempted with no luck. I was told that they were overseas, and unfortunately they had poor written command of the English language. I say "they" because the first tech guy was so clueless that he ultimately transferred me to his supervisor, who was only marginally better. They didn't know their way around a Windows system nearly as well as the people I've seen in this forum. In the end, after about an hour of chatting, the supervisor told me that he just couldn't help, and that I should contact Dell! Overall a complete waste of time. Frankly, they were an embarrassment to Symantec. Whatever salary they are paid should be redirected by Symantec to the fine contributors in this forum, who perform a great service to the company. Again, thank you all, and I'll keep you posted if anything changes.
Glad everything worked out for you on this one Rossonero. I was fortunate enought to have a recovery disc by the software I recommended, and then restored the drive from the image. I wasn't so well off on the Win 7 drive.
These things will happen from time to time. Power goes off, malware damages system files, driver and program conflicts cause disk errors. Anyone without a valid operating system disk should be downloading some of the free backup programs that can solve these issues with minimal damage and delay. It keeps us from pulling our hair out.
I have a system with Windows 7 Home Premium SP1 and my NIS is updated to the latest version. After getting this last update Installed I have started facing the blue screen of death issues.
Just after the installation the blue screen came up and system restarted;
Secondly, the blue screen comes up on its own at different times and system starts again..
Thirdly the blue screen also comes up if I press certain buttons in the NIS like(Scan Now, Manage, etc.)
I have tried to remove the NIS and re-install it but the listed above issues are still there.
On the blue screen it also points to a file named igdpmd64.sys
Request your immediate help regarding this problem.
- DB
The problem was because of a Windows update. Thanks for your help.
Glad you were able to spot and fix the problem.
ma_db wrote:The problem was because of a Windows update. Thanks for your help.
Could you tell us which update it was since that could help all of us .....
Any more background on how you tracked it down would help too.
I nearly bet it was the Windows Update KB2670838 from 28.02.2013 for the Internet Explorer 10.
I also had this problems with my notebook (windows 7 64 bit, switchable grafic) after the upgrade to NIS14, although the windows update is already from February and it worked fine with NIS13 all the time. After I have uninstalled this update everything works - no bluescreen any more!
At my desktop-PC (also windows 7 64 bit, no switchable grafic) I had no problems at all.
Thats correct. I had the same issues as written above & it's to do with switchable graphics.
Thanks for the confirmation ....
As I keep on reminding people here: It isn't always Norton !
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I nearly bet it was the Windows Update KB2670838 from 28.02.2013 for the Internet Explorer 10.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi, just wondering which version of IE you are running now because IE 10 cannot work without this update.
You cannot make work the parent 64 bit iexplore.exe process of IE 10, even without EPM enabled, with the absence of this update.
My guess is that something else is the culprit.
Regards,
Hi Apostolos, after uninstalling the windows update is IE9 on my laptop now, but i dont`t mind, cause my favorite browser is firefox anyway!
I agree, the blue screens were not caused by the windows update, cause it worked for more than six months without any problems with NIS13. After the upgrade to NIS14 the problems were starting! So at least a change in NIS14 was also culpable!
Regards
Hi huwyngr,
I don`t understand your conclusion that this is not Norton's fault at all. This windows update was working for more than six months until Norton's upgrade from NIS13 to NIS14. So finally a change in NIS 14 caused the problems!
Regards
Hi Guggi,
OK, all is clear now, you have reverted from IE 10 to IE9, however, I did the same thing on one of my systems, uninstaled IE 10 and went back to IE 9 but didn't uninstall the Windows KB update in question and I do not seem to have any issues with NIS 21.1.0.18 and my W7 x64 OS.
Regards,
Hi Guggi .....
<< I don`t understand your conclusion that this is not Norton's fault at all. This windows update was working for more than six months until Norton's upgrade from NIS13 to NIS14. So finally a change in NIS 14 caused the problems! >>
Because the OP said << Thats correct. I had the same issues as written above & it's to do with switchable graphics. >> as well as << On the blue screen it also points to a file named igdpmd64.sys >>
While Microsoft has said in http://support.microsoft.com/kb/2670838
<< Important Some portable computers that have a combination of Intel and AMD video cards in a hybrid configuration have drivers that are incompatible with this platform update for Windows 7 SP1 and Windows Server 2008 R2 SP1.
After you install this update and then restart the computer, the symptoms of this incompatibility are the computer crashes.
This Stop error includes the text PAGE_FAULT_IN_NONPAGED_AREA and one of the file names: igdpmd64.sys or igdpmd32.sys.>>
And because if you Google on KB2670838 the first few pages of references are devoted to this problem ..... There's no indication that all the users reporting the problem are using Norton and I'd suggest it is statistically unlikely.
The reason I make the point is that this is not the first time that a situation has been encountered where a fault occurred when Norton was present (N360 was a classic a few years ago when it updated from V2 to V3) and did not when it was removed and the fault was occurring in third party applications such as PowerDesk or a couple of image editors as well as in Windows Explorer the file manager.
Uninstall Norton -- no problem; reinstall Norton -- problem ....
But it was eventually tracked that the third parties had not implemented the change and nor had Microsoft so there was no problem until Microsoft did and the combination of the change in Windows and a program like Norton that had been updated with a third party application that had not implemented the change would cause the crash on that computer which no longer happened when the third party updated their program with a fix OR if an updated program was not there, ie Norton was removed.
Weird, but it's what logicians call a Post Hoc Propter Hoc fallacy: because A happens after you do B that A is caused by B ....
Clear now why I say "It's not always caused by Norton ..."
In this case it seems it only happens with a specific kind of graphics chipset AND the Windows Update .....
Hi Hugh,
thanks for your explanation. Hope you are right. And hopefully the third party does its job and I don't face blue screens then within a future windows update IE11 is published!
Guggi
Guggi wrote:Hi Hugh,
thanks for your explanation. Hope you are right. And hopefully the third party does its job and I don't face blue screens then within a future windows update IE11 is published!
Guggi
Don't hold your breath!