Microsoft Office XP doesn't run.

[Michael Sofer]

I would expect that a double-click on OSA.EXE found in

C:\Program Files\Microsoft Office\Office10

would result in some kind of action ... but nothing happens. Access through the start menu goes as:

Start --> All Programs --> Starup --> Microsoft Office

Is this "Startup" file folder on the menu a clue? (I don't know.) Using the start menu in this way causes no action either. The target specification in that shortcut is

"C:\Program Files\Microsoft Office\Office10\OSA.EXE" -b -l

.... any ideas? (Incidentally, I don't even know what Microsoft Office is supposed to do -- but I do think it should do something.)

I wonder ... could the problem have to do with the following registry key?

[HKEY_CLASSES_ROOT\CLSID\{9EFBF860-5685-11D3-AA3D-00C04F4C5275}\InprocServer32]
@="c:\\windows\\system32\\cdooff.dll"

The file "cdooff.dll" occurs in only one place on My Computer:

C:\Program Files\Microsoft Office\Office10\cdooff.dll

All other registry keys which contain this DLL as part of the data do assign the value appropriate to its location:

@="C:\\Program Files\\Microsoft Office\\Office10\\cdooff.dll"

.... Or is this registry inconsistency just another problem?

 

[Susan Ramlet]

Hi, Michael,

When you say Office XP doesn't run, do you mean the applications within
Office XP, such as Word? What happens if you click on the Word icon?

Here's information on what OSA does:

290144 - OFFXP: What Is the Osa.exe File and What Does It Do?:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290144&Product=ofw

--
Susan Ramlet
MVP - Microsoft Office
----------------------------------------------
Please post replies to the newsgroup where all may benefit.


I would expect that a double-click on OSA.EXE found in

C:\Program Files\Microsoft Office\Office10

would result in some kind of action ... but nothing happens. Access through
the start menu goes as:

Start --> All Programs --> Starup --> Microsoft Office

Is this "Startup" file folder on the menu a clue? (I don't know.) Using
the start menu in this way causes no action either. The target
specification in that shortcut is

"C:\Program Files\Microsoft Office\Office10\OSA.EXE" -b -l

.... any ideas? (Incidentally, I don't even know what Microsoft Office is
supposed to do -- but I do think it should do something.)

I wonder ... could the problem have to do with the following registry key?

[HKEY_CLASSES_ROOT\CLSID\{9EFBF860-5685-11D3-AA3D-00C04F4C5275}\InprocServer
32]
@="c:\\windows\\system32\\cdooff.dll"

The file "cdooff.dll" occurs in only one place on My Computer:

C:\Program Files\Microsoft Office\Office10\cdooff.dll

All other registry keys which contain this DLL as part of the data do assign
the value appropriate to its location:

@="C:\\Program Files\\Microsoft Office\\Office10\\cdooff.dll"

.... Or is this registry inconsistency just another problem?

 

[Mike101]

Hello,

It's Michael "posting" back (only this time, a little more anonymously [no
q's in my e-mail address]). The applications within Office XP work fine --
however, until now I didn't know that they were "within" it. I was just
puzzled when I found something on the start menu I could click on and
nothing visible would happen (except perhaps the appearance of that
hourglass symbol for a split second). But that's exactly what should
happen -- nothing visible -- because running OSE.EXE initializes a shared
code to produce an effect that you can't see ... that is ... until you start
an Office XP program, because the shared code which OSE initializes causes
those programs to start faster. ... And I tell you ... since I clicked on
that little OSE Genie, I've never seen Word, or Outlook, or OE ever snap
open so fast! In the end, OSE.EXE does cause something visible to happen.

There is, of course, something else visible that could have happened but
didn't, and that's the appearance the OSB (Office Shortcut Bar). In order
for that to happen the following registry setting must be present:
Registry Path: HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Shortcut Bar
Name: AutoStart
Value: 1
Type: DWORD

Registry Path:
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Osa\Autostart
Name: NotFindFast
Value: 1
Type: DWORD

But my computer's registry doesn't have it.


.... As for the registry inconsitency I mentioned ... is there an answer for
that?

[HKEY_CLASSES_ROOT\CLSID\{9EFBF860-5685-11D3-AA3D-00C04F4C5275}\InprocServer
32]
@="c:\\windows\\system32\\cdooff.dll"

The file "cdooff.dll" occurs in only one place on My Computer:

C:\Program Files\Microsoft Office\Office10\cdooff.dll

All other registry keys which contain this DLL as part of the data do assign
the value appropriate to its location:

@="C:\\Program Files\\Microsoft Office\\Office10\\cdooff.dll"

Hi, Michael,

When you say Office XP doesn't run, do you mean the applications within
Office XP, such as Word? What happens if you click on the Word icon?

Here's information on what OSA does:

290144 - OFFXP: What Is the Osa.exe File and What Does It Do?:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290144&Product=ofw

--
Susan Ramlet
MVP - Microsoft Office
----------------------------------------------
Please post replies to the newsgroup where all may benefit.


I would expect that a double-click on OSA.EXE found in

C:\Program Files\Microsoft Office\Office10

would result in some kind of action ... but nothing happens. Access through
the start menu goes as:

Start --> All Programs --> Starup --> Microsoft Office

Is this "Startup" file folder on the menu a clue? (I don't know.) Using
the start menu in this way causes no action either. The target
specification in that shortcut is

"C:\Program Files\Microsoft Office\Office10\OSA.EXE" -b -l

... any ideas? (Incidentally, I don't even know what Microsoft Office is
supposed to do -- but I do think it should do something.)

I wonder ... could the problem have to do with the following registry key?

[HKEY_CLASSES_ROOT\CLSID\{9EFBF860-5685-11D3-AA3D-00C04F4C5275}\InprocServer
32]
@="c:\\windows\\system32\\cdooff.dll"

The file "cdooff.dll" occurs in only one place on My Computer:

C:\Program Files\Microsoft Office\Office10\cdooff.dll

All other registry keys which contain this DLL as part of the data do assign
the value appropriate to its location:

@="C:\\Program Files\\Microsoft Office\\Office10\\cdooff.dll"

... Or is this registry inconsistency just another problem?

 

[Susan Ramlet]

Hi, Mike,

Thanks for the post back. So, it appears your application issues are
resolved.

Regarding the registry question, I'm not a Windows Registry expert, so maybe
someone else will post who knows more intimately what Office does with the
registry. My feeling is that if it's running, I'm not going to worry about
it <g>. But that's just me. I'll bet there is a lot of "dirty" code in
most of the applications that are installed on our computers...but if
everything's running as you expect it, it's probably nothing to be too
concerned about.

However, if you do decide to experiment by changing registry values (which I
don't really recommend), make sure you export the registry keys first, to
back them up, so they can be quickly restored in case something goes wrong.

--
Susan Ramlet
MVP - Microsoft Office
----------------------------------------------
Please post replies to the newsgroup where all may benefit.

Hello,

It's Michael "posting" back (only this time, a little more anonymously [no
q's in my e-mail address]). The applications within Office XP work fine --
however, until now I didn't know that they were "within" it. I was just
puzzled when I found something on the start menu I could click on and
nothing visible would happen (except perhaps the appearance of that
hourglass symbol for a split second). But that's exactly what should
happen -- nothing visible -- because running OSE.EXE initializes a shared
code to produce an effect that you can't see ... that is ... until you start
an Office XP program, because the shared code which OSE initializes causes
those programs to start faster. ... And I tell you ... since I clicked on
that little OSE Genie, I've never seen Word, or Outlook, or OE ever snap
open so fast! In the end, OSE.EXE does cause something visible to happen.

There is, of course, something else visible that could have happened but
didn't, and that's the appearance the OSB (Office Shortcut Bar). In order
for that to happen the following registry setting must be present:
Registry Path: HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Shortcut Bar
Name: AutoStart
Value: 1
Type: DWORD

Registry Path:
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Osa\Autostart
Name: NotFindFast
Value: 1
Type: DWORD

But my computer's registry doesn't have it.


... As for the registry inconsitency I mentioned ... is there an answer for

that?

[HKEY_CLASSES_ROOT\CLSID\{9EFBF860-5685-11D3-AA3D-00C04F4C5275}\InprocServer
32]
@="c:\\windows\\system32\\cdooff.dll"

The file "cdooff.dll" occurs in only one place on My Computer:

C:\Program Files\Microsoft Office\Office10\cdooff.dll

All other registry keys which contain this DLL as part of the data do assign
the value appropriate to its location:

@="C:\\Program Files\\Microsoft Office\\Office10\\cdooff.dll"

Hi, Michael,

When you say Office XP doesn't run, do you mean the applications within
Office XP, such as Word? What happens if you click on the Word icon?

Here's information on what OSA does:

290144 - OFFXP: What Is the Osa.exe File and What Does It Do?:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290144&Product=ofw

--
Susan Ramlet
MVP - Microsoft Office
----------------------------------------------
Please post replies to the newsgroup where all may benefit.


I would expect that a double-click on OSA.EXE found in

C:\Program Files\Microsoft Office\Office10

would result in some kind of action ... but nothing happens. Access through
the start menu goes as:

Start --> All Programs --> Starup --> Microsoft Office

Is this "Startup" file folder on the menu a clue? (I don't know.) Using
the start menu in this way causes no action either. The target
specification in that shortcut is

"C:\Program Files\Microsoft Office\Office10\OSA.EXE" -b -l

... any ideas? (Incidentally, I don't even know what Microsoft Office is
supposed to do -- but I do think it should do something.)

I wonder ... could the problem have to do with the following registry key?

[HKEY_CLASSES_ROOT\CLSID\{9EFBF860-5685-11D3-AA3D-00C04F4C5275}\InprocServer

32]
@="c:\\windows\\system32\\cdooff.dll"

The file "cdooff.dll" occurs in only one place on My Computer:

C:\Program Files\Microsoft Office\Office10\cdooff.dll

All other registry keys which contain this DLL as part of the data do assign
the value appropriate to its location:

@="C:\\Program Files\\Microsoft Office\\Office10\\cdooff.dll"

... Or is this registry inconsistency just another problem?

 

[Mike101]

Thanks.

Hi, Mike,

Thanks for the post back. So, it appears your application issues are
resolved.

Regarding the registry question, I'm not a Windows Registry expert, so maybe
someone else will post who knows more intimately what Office does with the
registry. My feeling is that if it's running, I'm not going to worry about
it <g>. But that's just me. I'll bet there is a lot of "dirty" code in
most of the applications that are installed on our computers...but if
everything's running as you expect it, it's probably nothing to be too
concerned about.

However, if you do decide to experiment by changing registry values (which I
don't really recommend), make sure you export the registry keys first, to
back them up, so they can be quickly restored in case something goes wrong.

--
Susan Ramlet
MVP - Microsoft Office
----------------------------------------------
Please post replies to the newsgroup where all may benefit.

Hello,

It's Michael "posting" back (only this time, a little more anonymously [no
q's in my e-mail address]). The applications within Office XP work fine --
however, until now I didn't know that they were "within" it. I was just
puzzled when I found something on the start menu I could click on and
nothing visible would happen (except perhaps the appearance of that
hourglass symbol for a split second). But that's exactly what should
happen -- nothing visible -- because running OSE.EXE initializes a shared
code to produce an effect that you can't see ... that is ... until you start
an Office XP program, because the shared code which OSE initializes causes
those programs to start faster. ... And I tell you ... since I clicked on
that little OSE Genie, I've never seen Word, or Outlook, or OE ever snap
open so fast! In the end, OSE.EXE does cause something visible to happen.

There is, of course, something else visible that could have happened but
didn't, and that's the appearance the OSB (Office Shortcut Bar). In order
for that to happen the following registry setting must be present:
Registry Path: HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Shortcut Bar
Name: AutoStart
Value: 1
Type: DWORD

Registry Path:
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Osa\Autostart
Name: NotFindFast
Value: 1
Type: DWORD

But my computer's registry doesn't have it.


... As for the registry inconsitency I mentioned ... is there an answer for

that?

[HKEY_CLASSES_ROOT\CLSID\{9EFBF860-5685-11D3-AA3D-00C04F4C5275}\InprocServer

32]
@="c:\\windows\\system32\\cdooff.dll"

The file "cdooff.dll" occurs in only one place on My Computer:

C:\Program Files\Microsoft Office\Office10\cdooff.dll

All other registry keys which contain this DLL as part of the data do assign
the value appropriate to its location:

@="C:\\Program Files\\Microsoft Office\\Office10\\cdooff.dll"

Hi, Michael,

When you say Office XP doesn't run, do you mean the applications within
Office XP, such as Word? What happens if you click on the Word icon?

Here's information on what OSA does:

290144 - OFFXP: What Is the Osa.exe File and What Does It Do?:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290144&Product=ofw

--
Susan Ramlet
MVP - Microsoft Office
----------------------------------------------
Please post replies to the newsgroup where all may benefit.


I would expect that a double-click on OSA.EXE found in

C:\Program Files\Microsoft Office\Office10

would result in some kind of action ... but nothing happens. Access through
the start menu goes as:

Start --> All Programs --> Starup --> Microsoft Office

Is this "Startup" file folder on the menu a clue? (I don't know.) Using
the start menu in this way causes no action either. The target
specification in that shortcut is

"C:\Program Files\Microsoft Office\Office10\OSA.EXE" -b -l

... any ideas? (Incidentally, I don't even know what Microsoft Office is
supposed to do -- but I do think it should do something.)

I wonder ... could the problem have to do with the following registry key?

[HKEY_CLASSES_ROOT\CLSID\{9EFBF860-5685-11D3-AA3D-00C04F4C5275}\InprocServer

32]
@="c:\\windows\\system32\\cdooff.dll"

The file "cdooff.dll" occurs in only one place on My Computer:

C:\Program Files\Microsoft Office\Office10\cdooff.dll

All other registry keys which contain this DLL as part of the data do assign
the value appropriate to its location:

@="C:\\Program Files\\Microsoft Office\\Office10\\cdooff.dll"

... Or is this registry inconsistency just another problem?