tag:blogger.com,1999:blog-5710205.post116455613525917308..comments2024-02-08T11:00:53.069-06:00Comments on Gordon's Tech: The memory could not be read: Anatomy of a complex series of Microsoft defectsJGFhttp://www.blogger.com/profile/14580785981874040314noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5710205.post-33353224281122398432011-08-20T08:32:17.641-05:002011-08-20T08:32:17.641-05:00you're welcome Andrew. Every so often these ol...you're welcome Andrew. Every so often these old posts do seem to be valuable.JGFhttps://www.blogger.com/profile/14580785981874040314noreply@blogger.comtag:blogger.com,1999:blog-5710205.post-69896955677381251422011-08-17T22:30:56.472-05:002011-08-17T22:30:56.472-05:00Gordon
Well Done mate.
Many other suggestions from...Gordon<br />Well Done mate.<br />Many other suggestions from other places, mostly involving getting help from MS.<br />But before trying that drastic step, I kept looking and came across your suggestion.<br />Yes - I had reorganised my disks, specifying an older drive for my temp stuff, then later on I changed my mind and used a different old disk.<br />Editing the Registry was the answer to my woes.<br />2 mins to apply the fix and 5 minutes to re-apply the updates.<br />Job done. No need to involve others (especially MS).<br />You're a star.Andrew Whittingtonnoreply@blogger.comtag:blogger.com,1999:blog-5710205.post-1165450932927604082006-12-06T18:22:00.000-06:002006-12-06T18:22:00.000-06:00Use Regedit to find "LocalCacheDrive" settings for...Use Regedit to find "LocalCacheDrive" settings for Office. Notice that the drive letter is "D" when it should be "C". Change it.<BR/><BR/>What a godsend. I had moved my disks around and changed the drive letters and could no longer get the Office updates to run. Applied the above registry change and it worked great for the first test update I tried. I'm applying all the other stacked up patches now. Thanks again,<BR/>GregAnonymousnoreply@blogger.com