Word 2002 and Open Office Writer Open Command Crashes App

On Jul 3, 1:50 am, "Terry Farrell" <terryfarr...@msn.com> wrote:
> This MSKB article may be a solution.
>
> http://support.microsoft.com/kb/928149
>
> --
> Terry Farrell - MS Word MVP
>
> "Peter Foldes" <o...@hotmail.com> wrote in message
>
> news:%234SnsjRvHHA.3444@TK2MSFTNGP04.phx.gbl...
> posted to the word.application.errors via crosspost
>
> "Fwedfwelldown" <Fwedfwelld...@discussions.microsoft.com> wrote in message
>
> news:53CF6E62-EC47-4A9F-A479-275387AFBA25@microsoft.com...
>
>
>
>
>
> > OK, I've made a bit of progress and found the culprit. Here's the problem
> > report I pulled up under Problem Reports and Solutions.
>
> > Problem signature
> > Problem Event Name: APPCRASH
> > Application Name: WINWORD.EXE
> > Application Version: 10.0.2627.0
> > Application Timestamp: 3a9cdbe7
> > Fault Module Name: PROPSYS.dll
> > Fault Module Version: 6.0.6000.16386
> > Fault Module Timestamp: 4549bd96
> > Exception Code: c0000005
> > Exception Offset: 0000a8f9
> > OS Version: 6.0.6000.2.0.0.768.3
> > Locale ID: 1033
>
> > The villain is PROPSYS.dll
>
> > I haven't figured out how to fix it yet.
>
> > I have tried uninstalling Office XP and Open Office and then reinstalling
> > only Office XP as you suggested, but I still have the same problem with
> > it.
>
> > I brought the computer home today so I could use my broadband connection.
> > I'm currently downloading all the updates to Vista that Microsoft says I
> > need. We'll see if that does anything.- Hide quoted text -
>
> - Show quoted text -

You know what? It's just way way way too late in the history of
personal computers for people to have to screw with this sort of
thing. Ten years ago Bill Gates was talking about applicance
computers. They turn on instantly, are as reliable as your
television, never blue screen. It hasn't happened. Some kind of
weird freaks must have hijacked development at Microsoft. They had 5
years and gigabucks to make Windows work better. Instead they made it
work worse.

If the early eighties Microsoft release of DOS 3.0 and the early
nineties release of Windows 3.1 are what propelled Microsoft to
success, the release of Vista and the incredibly pitiful Office 2007
will be what destroy Microsoft or at least marginalize it. Don't
blame Google. Microsoft is in self destruct mode.

And this post resolved some problems for anyone?

Terry

"SMHealthNick" <SMHealth@gmail.com> wrote in message
news:1183488326.174665.56120@a26g2000pre.googlegro ups.com...
> On Jul 3, 1:50 am, "Terry Farrell" <terryfarr...@msn.com> wrote:
>> This MSKB article may be a solution.
>>
>> http://support.microsoft.com/kb/928149
>>
>> --
>> Terry Farrell - MS Word MVP
>>
>> "Peter Foldes" <o...@hotmail.com> wrote in message
>>
>> news:%234SnsjRvHHA.3444@TK2MSFTNGP04.phx.gbl...
>> posted to the word.application.errors via crosspost
>>
>> "Fwedfwelldown" <Fwedfwelld...@discussions.microsoft.com> wrote in
>> message
>>
>> news:53CF6E62-EC47-4A9F-A479-275387AFBA25@microsoft.com...
>>
>>
>>
>>
>>
>> > OK, I've made a bit of progress and found the culprit. Here's the
>> > problem
>> > report I pulled up under Problem Reports and Solutions.
>>
>> > Problem signature
>> > Problem Event Name: APPCRASH
>> > Application Name: WINWORD.EXE
>> > Application Version: 10.0.2627.0
>> > Application Timestamp: 3a9cdbe7
>> > Fault Module Name: PROPSYS.dll
>> > Fault Module Version: 6.0.6000.16386
>> > Fault Module Timestamp: 4549bd96
>> > Exception Code: c0000005
>> > Exception Offset: 0000a8f9
>> > OS Version: 6.0.6000.2.0.0.768.3
>> > Locale ID: 1033
>>
>> > The villain is PROPSYS.dll
>>
>> > I haven't figured out how to fix it yet.
>>
>> > I have tried uninstalling Office XP and Open Office and then
>> > reinstalling
>> > only Office XP as you suggested, but I still have the same problem with
>> > it.
>>
>> > I brought the computer home today so I could use my broadband
>> > connection.
>> > I'm currently downloading all the updates to Vista that Microsoft says
>> > I
>> > need. We'll see if that does anything.- Hide quoted text -
>>
>> - Show quoted text -
>
> You know what? It's just way way way too late in the history of
> personal computers for people to have to screw with this sort of
> thing. Ten years ago Bill Gates was talking about applicance
> computers. They turn on instantly, are as reliable as your
> television, never blue screen. It hasn't happened. Some kind of
> weird freaks must have hijacked development at Microsoft. They had 5
> years and gigabucks to make Windows work better. Instead they made it
> work worse.
>
> If the early eighties Microsoft release of DOS 3.0 and the early
> nineties release of Windows 3.1 are what propelled Microsoft to
> success, the release of Vista and the incredibly pitiful Office 2007
> will be what destroy Microsoft or at least marginalize it. Don't
> blame Google. Microsoft is in self destruct mode.
>
>

On Jul 3, 12:58 pm, "Terry Farrell" <terryfarr...@msn.com> wrote:
> And this post resolved some problems for anyone?
>
> Terry
>
> "SMHealthNick" <SMHea...@gmail.com> wrote in message
>
> news:1183488326.174665.56120@a26g2000pre.googlegro ups.com...
>
>
>
> > On Jul 3, 1:50 am, "Terry Farrell" <terryfarr...@msn.com> wrote:
> >> This MSKB article may be a solution.
>
> >>http://support.microsoft.com/kb/928149
>
> >> --
> >> Terry Farrell - MS Word MVP
>
> >> "Peter Foldes" <o...@hotmail.com> wrote in message
>
> >>news:%234SnsjRvHHA.3444@TK2MSFTNGP04.phx.gbl.. .
> >> posted to the word.application.errors via crosspost
>
> >> "Fwedfwelldown" <Fwedfwelld...@discussions.microsoft.com> wrote in
> >> message
>
> >>news:53CF6E62-EC47-4A9F-A479-275387AFBA25@microsoft.com...
>
> >> > OK, I've made a bit of progress and found the culprit. Here's the
> >> > problem
> >> > report I pulled up under Problem Reports and Solutions.
>
> >> > Problem signature
> >> > Problem Event Name: APPCRASH
> >> > Application Name: WINWORD.EXE
> >> > Application Version: 10.0.2627.0
> >> > Application Timestamp: 3a9cdbe7
> >> > Fault Module Name: PROPSYS.dll
> >> > Fault Module Version: 6.0.6000.16386
> >> > Fault Module Timestamp: 4549bd96
> >> > Exception Code: c0000005
> >> > Exception Offset: 0000a8f9
> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> > Locale ID: 1033
>
> >> > The villain is PROPSYS.dll
>
> >> > I haven't figured out how to fix it yet.
>
> >> > I have tried uninstalling Office XP and Open Office and then
> >> > reinstalling
> >> > only Office XP as you suggested, but I still have the same problem with
> >> > it.
>
> >> > I brought the computer home today so I could use my broadband
> >> > connection.
> >> > I'm currently downloading all the updates to Vista that Microsoft says
> >> > I
> >> > need. We'll see if that does anything.- Hide quoted text -
>
> >> - Show quoted text -
>
> > You know what? It's just way way way too late in the history of
> > personal computers for people to have to screw with this sort of
> > thing. Ten years ago Bill Gates was talking about applicance
> > computers. They turn on instantly, are as reliable as your
> > television, never blue screen. It hasn't happened. Some kind of
> > weird freaks must have hijacked development at Microsoft. They had 5
> > years and gigabucks to make Windows work better. Instead they made it
> > work worse.
>
> > If the early eighties Microsoft release of DOS 3.0 and the early
> > nineties release of Windows 3.1 are what propelled Microsoft to
> > success, the release of Vista and the incredibly pitiful Office 2007
> > will be what destroy Microsoft or at least marginalize it. Don't
> > blame Google. Microsoft is in self destruct mode.- Hide quoted text -
>
> - Show quoted text -

Yes it did. Anyone who is thinking of making the mistake of buying
office 2997.

On Jul 3, 12:58 pm, "Terry Farrell" <terryfarr...@msn.com> wrote:
> And this post resolved some problems for anyone?
>
> Terry
>
> "SMHealthNick" <SMHea...@gmail.com> wrote in message
>
> news:1183488326.174665.56120@a26g2000pre.googlegro ups.com...
>
>
>
> > On Jul 3, 1:50 am, "Terry Farrell" <terryfarr...@msn.com> wrote:
> >> This MSKB article may be a solution.
>
> >>http://support.microsoft.com/kb/928149
>
> >> --
> >> Terry Farrell - MS Word MVP
>
> >> "Peter Foldes" <o...@hotmail.com> wrote in message
>
> >>news:%234SnsjRvHHA.3444@TK2MSFTNGP04.phx.gbl.. .
> >> posted to the word.application.errors via crosspost
>
> >> "Fwedfwelldown" <Fwedfwelld...@discussions.microsoft.com> wrote in
> >> message
>
> >>news:53CF6E62-EC47-4A9F-A479-275387AFBA25@microsoft.com...
>
> >> > OK, I've made a bit of progress and found the culprit. Here's the
> >> > problem
> >> > report I pulled up under Problem Reports and Solutions.
>
> >> > Problem signature
> >> > Problem Event Name: APPCRASH
> >> > Application Name: WINWORD.EXE
> >> > Application Version: 10.0.2627.0
> >> > Application Timestamp: 3a9cdbe7
> >> > Fault Module Name: PROPSYS.dll
> >> > Fault Module Version: 6.0.6000.16386
> >> > Fault Module Timestamp: 4549bd96
> >> > Exception Code: c0000005
> >> > Exception Offset: 0000a8f9
> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> > Locale ID: 1033
>
> >> > The villain is PROPSYS.dll
>
> >> > I haven't figured out how to fix it yet.
>
> >> > I have tried uninstalling Office XP and Open Office and then
> >> > reinstalling
> >> > only Office XP as you suggested, but I still have the same problem with
> >> > it.
>
> >> > I brought the computer home today so I could use my broadband
> >> > connection.
> >> > I'm currently downloading all the updates to Vista that Microsoft says
> >> > I
> >> > need. We'll see if that does anything.- Hide quoted text -
>
> >> - Show quoted text -
>
> > You know what? It's just way way way too late in the history of
> > personal computers for people to have to screw with this sort of
> > thing. Ten years ago Bill Gates was talking about applicance
> > computers. They turn on instantly, are as reliable as your
> > television, never blue screen. It hasn't happened. Some kind of
> > weird freaks must have hijacked development at Microsoft. They had 5
> > years and gigabucks to make Windows work better. Instead they made it
> > work worse.
>
> > If the early eighties Microsoft release of DOS 3.0 and the early
> > nineties release of Windows 3.1 are what propelled Microsoft to
> > success, the release of Vista and the incredibly pitiful Office 2007
> > will be what destroy Microsoft or at least marginalize it. Don't
> > blame Google. Microsoft is in self destruct mode.- Hide quoted text -
>
> - Show quoted text -

Please do not top post Terry. It is important for the market to
publicize the deficiencies of Visa and Office 2007 in hops Microsoft
will correct them -- thought I admit that is unlikely.

"Terry Farrell" wrote:

> This MSKB article may be a solution.
>
> http://support.microsoft.com/kb/928149

Thanks for the suggestion and link, Terry. I will check it out and let you
know if that worked.

"Terry Farrell" wrote:

> This MSKB article may be a solution.
>
> http://support.microsoft.com/kb/928149

That didn't work.

I've also tried to overwrite propsys.dll with a copy from a different
computer, but it won't give me permission to access the system32 folder. I
tried doing this from the command prompt as administrator, and it says
"access denied."

Is there any way to get around that?

"Fwedfwelldown" wrote:

>
>
> "Terry Farrell" wrote:
>
> > This MSKB article may be a solution.
> >
> > http://support.microsoft.com/kb/928149
>
> That didn't work.
>
> I've also tried to overwrite propsys.dll with a copy from a different
> computer, but it won't give me permission to access the system32 folder. I
> tried doing this from the command prompt as administrator, and it says
> "access denied."
>
> Is there any way to get around that?

Nevermind. I figured it out...and it seems to have solved the problem, too!

It wouldn't let me overwrite propsys.dll, so:
1. I renamed the other copy of propsys.dll to propsystest.dll and copied it
into the system32 folder. It let me do that with no problem.
2. I then took control of the original propsys.dll as administrator via
right click/Properties and renamed it to propsys1.dll.
3. I then renamed propsystest.dll to propsys.dll.

Opened Word, and I was able to navigate from disc drive to disc drive and
folder to folder with no crashes.

Thanks for all the help, even though I eventually found the solution on my
own.

I probably never would have thought of doing something this simple if I
hadn't exhausted every other possibility.

> It wouldn't let me overwrite propsys.dll, so:
> 1. I renamed the other copy of propsys.dll to propsystest.dll and copied it
> into the system32 folder. It let me do that with no problem.
> 2. I then took control of the original propsys.dll as administrator via
> right click/Properties and renamed it to propsys1.dll.
> 3. I then renamed propsystest.dll to propsys.dll.
>
> Opened Word, and I was able to navigate from disc drive to disc drive and
> folder to folder with no crashes.
>
> Thanks for all the help, even though I eventually found the solution on my
> own.
>
> I probably never would have thought of doing something this simple if I
> hadn't exhausted every other possibility.

I spoke too soon. It worked a couple of times and then started crashing
again. ARGHHH!

On Jul 5, 10:46 am, Fwedfwelldown
<Fwedfwelld...@discussions.microsoft.com> wrote:
> > It wouldn't let me overwrite propsys.dll, so:
> > 1. I renamed the other copy of propsys.dll to propsystest.dll and copied it
> > into the system32 folder. It let me do that with no problem.
> > 2. I then took control of the original propsys.dll as administrator via
> > right click/Properties and renamed it to propsys1.dll.
> > 3. I then renamed propsystest.dll to propsys.dll.
>
> > Opened Word, and I was able to navigate from disc drive to disc drive and
> > folder to folder with no crashes.
>
> > Thanks for all the help, even though I eventually found the solution on my
> > own.
>
> > I probably never would have thought of doing something this simple if I
> > hadn't exhausted every other possibility.
>
> I spoke too soon. It worked a couple of times and then started crashing
> again. ARGHHH!

That's because Microsoft carefully designed all of their software
changes for the past 4 years to completely ruin what was a great
product -- Microsoft Office.

i have a try according the direction and it can not resolve the same problem
in office 2007!

"Terry Farrell" wrote:

> And this post resolved some problems for anyone?
>
> Terry
>
> "SMHealthNick" <SMHealth@gmail.com> wrote in message
> news:1183488326.174665.56120@a26g2000pre.googlegro ups.com...
> > On Jul 3, 1:50 am, "Terry Farrell" <terryfarr...@msn.com> wrote:
> >> This MSKB article may be a solution.
> >>
> >> http://support.microsoft.com/kb/928149
> >>
> >> --
> >> Terry Farrell - MS Word MVP
> >>
> >> "Peter Foldes" <o...@hotmail.com> wrote in message
> >>
> >> news:%234SnsjRvHHA.3444@TK2MSFTNGP04.phx.gbl...
> >> posted to the word.application.errors via crosspost
> >>
> >> "Fwedfwelldown" <Fwedfwelld...@discussions.microsoft.com> wrote in
> >> message
> >>
> >> news:53CF6E62-EC47-4A9F-A479-275387AFBA25@microsoft.com...
> >>
> >>
> >>
> >>
> >>
> >> > OK, I've made a bit of progress and found the culprit. Here's the
> >> > problem
> >> > report I pulled up under Problem Reports and Solutions.
> >>
> >> > Problem signature
> >> > Problem Event Name: APPCRASH
> >> > Application Name: WINWORD.EXE
> >> > Application Version: 10.0.2627.0
> >> > Application Timestamp: 3a9cdbe7
> >> > Fault Module Name: PROPSYS.dll
> >> > Fault Module Version: 6.0.6000.16386
> >> > Fault Module Timestamp: 4549bd96
> >> > Exception Code: c0000005
> >> > Exception Offset: 0000a8f9
> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> > Locale ID: 1033
> >>
> >> > The villain is PROPSYS.dll
> >>
> >> > I haven't figured out how to fix it yet.
> >>
> >> > I have tried uninstalling Office XP and Open Office and then
> >> > reinstalling
> >> > only Office XP as you suggested, but I still have the same problem with
> >> > it.
> >>
> >> > I brought the computer home today so I could use my broadband
> >> > connection.
> >> > I'm currently downloading all the updates to Vista that Microsoft says
> >> > I
> >> > need. We'll see if that does anything.- Hide quoted text -
> >>
> >> - Show quoted text -
> >
> > You know what? It's just way way way too late in the history of
> > personal computers for people to have to screw with this sort of
> > thing. Ten years ago Bill Gates was talking about applicance
> > computers. They turn on instantly, are as reliable as your
> > television, never blue screen. It hasn't happened. Some kind of
> > weird freaks must have hijacked development at Microsoft. They had 5
> > years and gigabucks to make Windows work better. Instead they made it
> > work worse.
> >
> > If the early eighties Microsoft release of DOS 3.0 and the early
> > nineties release of Windows 3.1 are what propelled Microsoft to
> > success, the release of Vista and the incredibly pitiful Office 2007
> > will be what destroy Microsoft or at least marginalize it. Don't
> > blame Google. Microsoft is in self destruct mode.
> >
> >
>