Issue 8666 - Strange Errormsg. if run on Windows 95 w/o UNICOWS.DLL
Summary: Strange Errormsg. if run on Windows 95 w/o UNICOWS.DLL
Status: CLOSED FIXED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: 643
Hardware: PC Windows 95
: P4 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@udk
URL:
Keywords:
: 9681 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-10-24 10:44 UTC by joerg.skottke
Modified: 2003-03-16 20:12 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description joerg.skottke 2002-10-24 10:44:29 UTC
When executing soffice.exe on a Windows machine like Win95 without DCOM update
an errormessage is displayed which offers no information about the cause but
just passes through the errorcode from the os.

FYI: #104350#
Comment 1 Unknown 2002-10-25 21:21:41 UTC
I see this on two different systems, both Windows 95 OSR2.  The error
message is, roughly, "No DCOM update installed.  The application may 
not run stable."  There's no indictation as to what DCOM is, what it's
for, why OO wants it, why it needs to be updated, or where to get the
update.  Worse, it comes up _every_ time OO is launched.

Is there a workaround for this?  What's DCOM and what _else_ will be
changed if I install such an update?
Comment 2 hennes.rohling 2002-10-28 09:00:36 UTC
Changed the misleading title and component. There's an 
errormessage "Systemmessage 0x12345: UNICOWS.DLL" when running on 
Windows 95 and the MSLU loader cannot find the required UNICOWS.DLL. 
Windows 98/ME display an appropriate error message. The error 
message should be "The program cannot find the required library: 
UNICOWS.DLL". Seems as on Windows 95 the system error message 
resources are weak.

@eady: Read the run time requirements and/or the readme that points 
out where to obtain DCOM. The error message is only for those who 
don't care about runtime requirement instructions. FYI: DCOM update 
is a fix available by Microsoft that fixes error in COM/OLE. 
Otherwise the clipboard and drag&drop may not work.

@armin: Please add the UNICOWS.DLL runtime requirement to the readme.
Comment 3 Unknown 2002-10-28 11:18:43 UTC
added unicows.dll requirement to readlicense/source/readme/readme.html 
and readlicense/source/readme/wntmsci7.pro/readme.txt on HEAD and 
OO643C. Text as in release notes of 643. 

Comment 4 Unknown 2002-10-29 14:55:21 UTC
can we close this issue? 
Comment 5 jonadab 2002-10-29 18:00:08 UTC
hro:  sorry for the confusion, but I'm not familiar with the runtime
requirements; where are they listed?  All I can find are the system
requirements: http://www.openoffice.org/dev_docs/source/sys_reqs.html
which don't seem to address this issue.  

I do see the information in the readme now, but I had assumed that it
contained licensing info (as is usual for software from the Unix and
open-source world) and so had not read it, since I am familiar with
the licensing already.  (I use OO on my Linux/Gnome system, and was
installing it on Win95 for a coworker.)  This information should be
listed in the system requirements at minimum and probably on the
downloads page as well (or at least a "System Requirements" link
should be there).  Should I file this under documentation?
Comment 6 Unknown 2002-10-30 11:02:59 UTC
Yes, it is a good idea to file an issue or add to this issue 
where you think the information is missing. You've done this now 
so you won't have to file an extra issue now. I will review the 
system requirements page. 

thanks
Comment 7 hennes.rohling 2002-12-02 09:56:00 UTC
*** Issue 9681 has been marked as a duplicate of this issue. ***
Comment 8 Unknown 2002-12-03 10:24:48 UTC
the requirement for unicows.dll is documented on several places 
(readme, releasenotes, builddocs. system requirement page). 

closing issue for now. 
Comment 9 michael.bemmer 2003-03-16 20:08:48 UTC
As discussed with Armin, he thought these bug were closed, he sees all of them
as verified.
Comment 10 michael.bemmer 2003-03-16 20:12:36 UTC
As discussed with Armin, he thought these bug were closed, he sees all of them
as verified.