Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!bywater!arnor!larios!db3l From: db3l@arnor.UUCP (David Bolen) Newsgroups: comp.os.os2.apps Subject: Re: Word for OS/2 Message-ID: Date: 19 Mar 91 15:47:02 GMT Article-I.D.: larios.DB3L.91Mar19104702 References: <11991@uhccux.uhcc.Hawaii.Edu> Sender: news@arnor.uucp (NNTP News Poster) Organization: Laboratory Automation, IBM Thomas J. Watson Research Center Lines: 48 In-Reply-To: tholen@uhccux.uhcc.Hawaii.Edu's message of 17 Mar 91 23:07:40 GMT In article <11991@uhccux.uhcc.Hawaii.Edu> tholen@uhccux.uhcc.Hawaii.Edu (David Tholen) writes: >Only Standard Edition is affected, not Extended Edition. >Only version 1.3 is affected, not version 1.2 or 1.21. >Only SYSLEVEL XR00000 is affected. The implication is that there is a more >recent CSD revision to OS/2 SE version 1.3, but I saw no information about >it on the IBM BBS in Atlanta; it had only CSDs to version 1.2. > >Also, the implication is that the problem is with OS/2, not with Word. >Because the Word replacement DLL only fixes the problem for Word, this bug >could potentially affect other OS/2 PM applications, (...) Well, I'm definitely no more official a source than anyone else, but what I've heard is that the bug was in Word and not in OS/2. The problem was that Word used some internal knowledge about OS/2 and/or made assumptions about some undocumented OS/2 features. In other words, Word was not a "nice" program. When OS/2 1.3 came out (SE), that internal behavior changed, and thus Word began to break. The reason that it happens with SE and not EE is that EE has a couple of month lag time behind SE and generally gets some updates applied to fix problems that show up in SE. These same fixes are then eventually released as an SE CSD. One of the things I think that was done was to restore the undocumented behavior, or at least fix it so that programs that depended on it (not sure of anything around besides Word) would still work. So I don't think this is the sort of thing you need to worry about breaking most other programs. I believe that applications written to the documented interfaces shouldn't experience any problems. I don't think there are any CSDs around yet for 1.3 SE, so the reference you got to the specific syslevel was probably just to keep the information accurate if and when CSDs are released. They would know that any future CSD would fix the problem since the first CSD to be released should include any fixes that were added to EE following the SE release. -- -- David -- /-----------------------------------------------------------------------\ \ David Bolen / | Laboratory Automation, IBM Thomas J. Watson Research Center | / P.O. Box 218, Yorktown Heights, NY 10598 \ | - - - - - - - - - - - - M i t h r a n d i r - - - - - - - - - - - - | | Internet : db3l@ibm.com | Bitnet : db3l@yktvmv | | Usenet : uunet!bywater!arnor!larios!db3l | Phone : (914) 945-1940 | | /---------------------------------------------------------------\ | \-( All comments/opinions are mine and don't represent those of IBM )-/ \---------------------------------------------------------------/