←  General Discussion

AutoPatcher Forum

»

Office Addons

DesertJerry's Photo DesertJerry 24 Apr 2008

AutoPatcher > Microsoft Office Addons > Office Update Runtime was showing as black, I selected it (among other updates), clicked Next and it turned blue. No problem.

A few days later running AutPatcher I noticed it was black again. What happened? Time to try to figure out.

I finally determined the operative file was: OPUC.DLL and I had been moving it from \Windows to \Windows\System, thereby causing the color change from blue back to black.

Why you may ask.

Well, from the early years of Windows I had been used to seeing all DLLs in the \System folder and would move them as required; knowing that the default path included \Windows and \Windows\System.

The advent of Windows XP just added \System32 to the mix so I changed my procedure to sort DLLs so the *.DLL went to \System and *32.DLL went to \System32.

This had me checking the appropriate APM file and noticed it was set to send OPUC.DLL to \Windows. Is this a mandatory requirement set by some Microsoft guru somewhere?

Also, while looking at the APM file I noticed the FilePath was shown as windows:\ so how would I change it to read \windows\system for my system?

Unless I can convince you to make the permanent location \windows\system.

Thanks :rolleyes:
Quote

Erik Ramey's Photo Erik Ramey 24 Apr 2008

This is the default install location for this DLL when you go to the office update site: http://office.micros...spx?ofcresset=1 - Check for updates in the upper right hand corner. If you want to move the dll, you have to unregister and re-register the dll using regsvr32 and regsvr32 /u respectivly. You can also update the detections from the module but if you run APUP, it will always be deleted.

Since this is how Microsoft installs this runtime, I'm leaving the offical module alone.
Quote

DesertJerry's Photo DesertJerry 25 Apr 2008

 Erik Ramey, on Apr 24 2008, 06:06 AM, said:

Since this is how Microsoft installs this runtime, I'm leaving the offical module alone.
That's why I asked - Microsoft again. :(
Quote

darthyoda6's Photo darthyoda6 25 Apr 2008

Eeek, I hope your not still dumping to the system directory. I believe only 16 bit dlls go there. Everything else should be in system32 directory.
Quote

DesertJerry's Photo DesertJerry 26 Apr 2008

 darthyoda6, on Apr 25 2008, 05:06 AM, said:

Eeek, I hope your not still dumping to the system directory. I believe only 16 bit dlls go there. Everything else should be in system32 directory.
As I said above, those items listed as *32.dll go in \system32, those *.dll go in \system. :P
Quote

darthyoda6's Photo darthyoda6 26 Apr 2008

system directory - 13 dll files
system32 directory - 1508 dll files
Quote

DesertJerry's Photo DesertJerry 26 Apr 2008

Numbers of DLLs only mean something if we had exactly the same programs installed.
Quote

darthyoda6's Photo darthyoda6 27 Apr 2008

I'm just saying that the system32 is the main directory for 2000 & xp. system is only for old programs that work on windows 3.1. Although vista 64 bit is even more confusing.
Quote

DesertJerry's Photo DesertJerry 27 Apr 2008

 darthyoda6, on Apr 27 2008, 03:46 AM, said:

I'm just saying that the system32 is the main directory for 2000 & xp. system is only for old programs that work on windows 3.1.
Who says so? Do you have a reference?

I've been dividing the DLLs on my system for years as stipulated above and have had no problems.
Quote