Re: Word illegal operations

[Roy Anderson <royanderson -at- MINDSPRING -dot- COM>]

Dear all,

My humble apologies for atrocious typos in my earlier post re this subject.

Was rushing on deadline but wanted to disclose information about existence of
microsoft.public.word.application.errors newsgroup to aid AlQuin. I neglected
run a spell check on the note before posting. I'm embarrassed and contrite. So
sorry. Here's hoping you're having a better Monday... (Groan.)

Roy

Roy Anderson wrote:
>
> I respectfully suggest you ask your Word application technical question in
> the Microsoft news forums because you're more likely to obtain satisfaction
> there. Resolving technical questions is their reason for existence. You'll
> probably need to provide greater details (about your configuration: RAM,
> software version, operating system, and what you were doing at the time
> of the crash) to aid them in resolving your problem. I've found MS news
> forums useful in resolving detailed technical matters.
>
> 1. Subscribe to the Microsoft news server at "msnews.microsoft.com"
>
> 2. Subscribe to "microsoft.public.word.application.errors" and re-post
>    your question--providing more detail about your PC environment, other
>    open apps, and so forth.
>
> There are 15-20 technical Word groups on the MS News server to handle
> problems arising with numbering, tables, and so forth.
>
> If you visit the Microsoft news groups, I suggest you refrain from using
> terms such as "detestable Word application" in your notes. Some people
> actually prefer MS Word to market alternatives.
>
> Good luck. Hope this input helps you.
>
> Roy
>
> AlQuin wrote:
> >
> > Tech pages and Microsoft did not help me until now, but I have to produce
> > some text by this detestable Word application in a few days now.
> > Word95 and 97 regularly present me with "This program has performed an
> > illegal operation and will be shut down" messages.
> > It happens at saving to another but the default disk, or just scrolling
> > throught the document.
> > I openend one of the details once:
> > "
> > Winword caused invalid page fault in module PICTMM32.FLT at 0137:
> > 1c003fdf.
> > Registers:
> > EAX=00000000 CS=0137 KIP1c003fdf EFLGS=00000202
> > KBX=00000001 SS=013f ESP=0062e698 EBP=0062f224
> > ECX=00000004 DS=013f ESI=00000001 FS=1287
> > EDX=1c01376c ES=013f EDI=00000000 GS=0c86
> > Bytes at CS:KIP:
> > 8b 01 89 02 86 59 04 be 01 00 00 00 89 5a 04 8b
> > Stack dump:
> > 0062f224 00000000 00000001 00000001 7bb80000
> > 01177fb2 18d07fb5 012f0001 4ae17bfa
> > 00080000 7bd40000 01177fb2 18c87fb5 00000117 012f00c0
> > 4c6e7c0e
> > "
> > Has anyone any hint combat this blockade.
> > Responding off-list will be the fastest help.
> >
> > Txs
> > Kees de Bondt
> >
> > AlQuin Total Quality
> >
> > * Technical communication is
> >   writing in the customer's interest.
> >
> > From ??? -at- ??? Sun Jan 00 00:00:00 0000==
>
> From ??? -at- ??? Sun Jan 00 00:00:00 0000==


 From ??? -at- ??? Sun Jan 00 00:00:00 0000=