There were some applications that didn't look for SHARE.EXE in memory, but
simply checked that it was being loaded in AUTOEXEC.BAT and therefore
assumed it was running, Adding the entry is always recommended. You can
take a do-nothing EXE from the DOS folder, copy it, and rename it to
share.exe. It might have been MODE.EXE that was a popular choice, but a bit
of experimenting should reveal a suitable candidate..
--
Jeff Richards
MS MVP (Windows - Shell/User)
"glee" wrote in message
...
That's the error that is usually worked around by creating a dummy
share.exe as i described earlier. It's not working for you, obviously,
but I don't know why.

This page, http://kb.iu.edu/data/aglc.html suggests also adding this line
to the end of the autoexec.bat, though I can't see what that would do:

rem start.exe
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/
http://dts-l.org/goodpost.htm


"Leon Howell" wrote in message
...
What is the *exact* error message you are getting, and when?

After I select full instalation and answer the questions about Lotus-123
support, it says "Setup was unable to find SHARE.EXE on your system. It
is
required to run this application. Please fix your system and rerun Setup"
I
click OK and it says Microsoft Office Setup was not completed
successfuly."

...

Computers don't lie ... unless they feel like it.