Replies

I have had a different problem with 2464588 (Powerpoint 2003). When installed, it caused Outlook to freeze up when viewing an email. Possibly related to the graphics pulled down from a website. The freeze was a good one – it took many attempts to end the program through Task Manager to kill it.

I did not install the hotfix 2543241 because that fix relates to a Powerpoint problem. I un-installed 2464588 (and there it will stay) and Outlook recovered.

My setup is WinXP Home SP3 with Office 2003 Professional SP3.

Chris

I have since installed the later Powerpoint patch 2535812 sucessfully, so it looks like the problem I had with 2464588 was fixed by the subsequent patch.

Chris

Chris
Win 10 Pro x64 Group A

I have had a different problem with 2464588 (Powerpoint 2003). When installed, it caused Outlook to freeze up when viewing an email. Possibly related to the graphics pulled down from a website. The freeze was a good one – it took many attempts to end the program through Task Manager to kill it.

I did not install the hotfix 2543241 because that fix relates to a Powerpoint problem. I un-installed 2464588 (and there it will stay) and Outlook recovered.

My setup is WinXP Home SP3 with Office 2003 Professional SP3.

Chris

Chris
Win 10 Pro x64 Group A

Just to close the loop on this one, the overheating problem was nothing to do with the cpu usage. This laptop is one of those affected by the nVidia gpu defect problem (Windows Secrets Michael Lasky 9 April 2009). The overheating (and probably the disk errors) was caused by the GF8400M gpu quietly cooking away prior to catastrophic failure on 27 Oct 2010. More detail on the problem and claim procedure is at http://www.nvidiadefect.com/ and http://www.hplies.com/ .

Interestingly, I reported the overheating to HP in August. Despite the fact that they were well aware of the problem at the time they just replied that I was out of warranty. Another unreliable brand from the service point of view.

Chris

Chris
Win 10 Pro x64 Group A

Susan

Thanks for your answer. I fully understand the proviso in your last sentence.

Regards

Chris

Chris
Win 10 Pro x64 Group A

Susan

I am not completely clear, and you did not cover it in today’s Windows Secrets. Are the .NET patches in MS10-70 safe to install for WXP-SP3 and Vista SP2 standalone workstations at this stage?

Chris

Chris
Win 10 Pro x64 Group A

Mercyh – I’ll check out the links. However, I also get the message that I am getting distracted with the cpu cycles and need to spend a bit more time on the possible/probable hardware faults.

Thanks for your help,everyone.

Chris

Chris
Win 10 Pro x64 Group A

Joe/P T

Now I am just as confused. The process that is starting all the cpu churning is audiodg.exe, which is described on Process Library as:

“udiodg.exe is a Windows Audio Device Graph Isolationr from Microsoft Corporationr belonging to Microsoft® Windows® Operating Systemr . It is part of Windows and ensures that the content and plug-ins are not modified by another application such as spyware.”

That means closing down items in msconfig would not be expected to help, but on the other hand the problem goes away in safe mode….

Perhaps I should explore fan speeds as Paul suggests, and then move to Windows 7.

Chris

Chris
Win 10 Pro x64 Group A

Joe

Thanks – that is probably the tool I was looking for,

Chris

Chris
Win 10 Pro x64 Group A

Paul

I am fully patched, and normally am. I have been fighting the problem for some weeks, so it is showing no sign of settling down by iteslf. On the other points:
1 Everything has been cleaned out with a vacuum and with compressed air – no dust clouds. As a laptop, the CPU is not easily accessible.
2 Fan seems to be running OK when hot
3 Not accessible
4 I will have a look for Speedfan

Chris

Chris
Win 10 Pro x64 Group A

Ted

I should have said – yes I tried that, as another obvious possibility, and it did not help. In fact, ZA is running in safe mode where I have minimal CPU activity and on another PC, running XP and the same build of ZA, I see 5% CPU activity when other applications are quiet.

Chris
Win 10 Pro x64 Group A

I suspect the answer to this problem may lie in Fred Langa’s article in Windows Secrets (paid edition) of 11 March 2010:

“More on Win7-NAS networking problems

Charles Ojserkis also wrote a follow-up note, but on a different issue:
 “Just wanted to comment on the ‘Solving Windows 7 Networking Problems’ item in the Feb. 25 issue.

“I had the same problem with two older NAS (network attached storage) units on my LAN when I went from XP to Vista. They were older (like 1999) Linux-based Iomega devices.

“There was a problem with the method of encryption used by the new OS to communicate with the network shares. As I recall, I had to go into the OS and reduce the type of encryption/handshaking used by the new OS. Once I made the change, I was able to create the share. Prior to the change, the share could not be created. Hope this helps.”
Thanks, Charles. Yes, it’s confirmation of one of the items I suspected and described this way: “But HomeGroup — and related elements of Win7’s networking, such as 128-bit encryption for shared files — introduces new and added complexity into your local networking mix.”

To change Win7’s network-share encryption levels, go into the Network and Sharing Center and do the following:
 Open Control Panel (default view), click Network and Internet, then click Network and Sharing Center.
 In the Network and Sharing Center’s left-hand pane, select Change advanced sharing settings.
 Select the appropriate type of networking profile: Home or work or Public (LANs are likely to be the former); then scroll down to File Sharing Connections and make your selection. (See Figure 1.)

Figure 1. In the Network and Sharing Center’s advanced settings, you can change the encryption level for Win7 network shares.

If 128-bit encryption is selected, try the 40- or 56-bit option. Win7 should now communicate with older and non-Win7 devices.”

However, for the life of me I cannot find the equivalent of the Change Advanced Sharing Settings in Vista – although Charles Ojserkis clearly could. Has anyone any idea where it might be?

Chris B

Chris
Win 10 Pro x64 Group A

As James Sykes has remarked, Intuit precipitously discontinued Quicken in the UK market quite a while ago, which does not help. I am using Quicken 2002 Deluxe & Business, having started with Quicken 3 many years ago. What locks me in is the need to interrogate old data, but my worry is that at some stage it will fail to respond to a new operating system or its file size will fall over. My main file is 20MB, so James you should be safe for a while. The problem I will have then is that I doubt I will be able transfer my old data to a new package.

I also object to the Rent Me approach to pricing, and refused to upgrade when that came in. However, I do not download stock prices, because I trust my own real return calculations not those of a package. On the other hand, I have always regarded Quicken’s reporting routines to be the best of the bunch.

I have a big problem with Intuit’s approach to service which started with Quicken 2002. I found that their computation of VAT was wrong, which exposed me to the sledgehammer of the Inland Revenue, and that this version removed all the timesaving features of Business transaction entry (memorised transactions specifically). Net result was a great deal more time spent on input and on detailed checking of VAT each period. Intuit refused to acknowledge the problems, let alone correct them, despite the legal liability that their clients were exposed to from the VAT flaws.

I have introduced a client to MYOB, which I think is a good package, but I did not use it myself because of the weaker reporting and the fact that transferability of data substantially locks me into Quicken.

Chris
Win 10 Pro x64 Group A

Do you have update KB 973475 installed? That seems to be one of the many bugs with that particular update.

Rory – what a brilliant “get”. I did indeed install it on 12 Nov, and as far as I can see my first problems occurred on 20 Nov. This particular bug, I find after your prompt, is documented in
http://support.microsoft.com/kb/973475.

I tested on one of the spreadsheets, disabling freeze frames per the MS article, and the formula worked without a crash. I will stick with this workaround unless the problem occurs too often, in which case I will uninstall KB973475.

Many thanks for your help.

Chris

Chris
Win 10 Pro x64 Group A

Just tried to do the same thing on the same spreadsheet in Excel 2007 and it worked fine. Looks like an Excel 2003 bug, methinks.

Chris B

Chris
Win 10 Pro x64 Group A

I am not convinced. In one case I had to rebuild anyway, since I had not saved for an hour. In the other, I continued using it with a bodge to achieve what I wanted. In any case, Excel itself thought it had a problem, since it “called home”.

I will try it in Excel 2007 in a bit, to see if the same thing happens.

Chris

Chris
Win 10 Pro x64 Group A