Winword Invalid Page Fault in module MSO97.dll

[Hakipuu geek]

I did a clean install of Windows 98 and installed Office 97 on a Dell Optiplex. I then ghosted the hard drive to another computer and when I try to print to a network printer (A local printer shared on a peer to peer network) I get the following error

WINWORD caused an invalid page fault in module MSO97.DLL at 017f:306c26c3
Registers
EAX=00c5eff0 CS=017f EIP=306c26c3 EFLGS=00010216 EBX=00c50000 SS=0187 ESP=0062ee38 EBP=0000000
ECX=00c50000 DS=0187 ESI=00c50000 FS=3cef EDX=00c5716c ES=0187 EDI=00c51068 GS=000
Bytes at CS:EIP
66 8b 30 66 85 f6 74 1d 8b f8 33 c0 66 8b c6 8b
Stack dump
0000004c 000003f7 306c24e9 00000237 00c5716c 0062eeb4 00000000 00c5716c 00000003 00000000
306c2778 00c5716c 0000004c 3000e24f 00c57170 00000000

The address is different than those talked about in the knowledge base

Word then hangs and I have to use ctrl-alt-delete to shut down the document and subsequently Word.

I also got this error with Office 2000. I removed it and assumed that the earlier version of Office would work better and faster with Windows 98. No joy. I am trying to install 32 computers in the next couple of days before the students get back. I could use any help that anyone can give. If you can reply to the email address I would appreciate it

Geoff Bickfor
(e-mail address removed)

 

[TF]

How is the printer installed? Did you install the printer driver locally and
point to the IP address of the shared printer? If not, how is it connected?
Sharing printers has always been a big problem in versions of Windows prior
to Windows 2000 and printing to a networked printer if a far more stable
solution than printing to a shared printer connected to someone's
workstation.

Also, Word is very heavy on printer drivers and needs one installed locally
to work efficiently.

--
Terry Farrell - Word MVP
http://www.mvps.org/word/

I did a clean install of Windows 98 and installed Office 97 on a Dell
Optiplex. I then ghosted the hard drive to another computer and when I try
to print to a network printer (A local printer shared on a peer to peer
network) I get the following error:

WINWORD caused an invalid page fault in module MSO97.DLL at 017f:306c26c3.
Registers:
EAX=00c5eff0 CS=017f EIP=306c26c3 EFLGS=00010216 EBX=00c50000 SS=0187
ESP=0062ee38 EBP=00000000
ECX=00c50000 DS=0187 ESI=00c50000 FS=3cef EDX=00c5716c ES=0187 EDI=00c51068
GS=0000
Bytes at CS:EIP:
66 8b 30 66 85 f6 74 1d 8b f8 33 c0 66 8b c6 8b
Stack dump:
0000004c 000003f7 306c24e9 00000237 00c5716c 0062eeb4 00000000 00c5716c
00000003 00000000
306c2778 00c5716c 0000004c 3000e24f 00c57170 00000000

The address is different than those talked about in the knowledge base.

Word then hangs and I have to use ctrl-alt-delete to shut down the document
and subsequently Word.

I also got this error with Office 2000. I removed it and assumed that the
earlier version of Office would work better and faster with Windows 98. No
joy. I am trying to install 32 computers in the next couple of days before
the students get back. I could use any help that anyone can give. If you
can reply to the email address I would appreciate it.

Geoff Bickford
(e-mail address removed)

 

[hakipuugeek]

I installed the printer with the add printer wizard and used the network printer option. It has worked fairly well before and has only given me a hiccup with this installation. It works for the other Office products like Excel and Powerpoint. Just not the Word files. They are connected in a peer to peer network using Cat5 cables and a central switch and a WINS server in the system. The port that the printer drivers print to is the network address of the printer. EX:\\host\printername. Again it works well in every other application which tells me that the MSO97.dll file is not corrupt. It also happened when I initially installed Office 2000. I uninstalled it, removed the files and cleared the registry using a third party tool called regcleaner before I tried to install Office 97. I was hoping the new installation of Office 97 would speed things up and make the problem go away. NO luck there

I am at a loss

Geoff Bickfor

----- TF wrote: ----

How is the printer installed? Did you install the printer driver locally an
point to the IP address of the shared printer? If not, how is it connected
Sharing printers has always been a big problem in versions of Windows prio
to Windows 2000 and printing to a networked printer if a far more stabl
solution than printing to a shared printer connected to someone'
workstation

Also, Word is very heavy on printer drivers and needs one installed locall
to work efficiently

--
Terry Farrell - Word MV
http://www.mvps.org/word

I did a clean install of Windows 98 and installed Office 97 on a Del
Optiplex. I then ghosted the hard drive to another computer and when I tr
to print to a network printer (A local printer shared on a peer to pee
network) I get the following error

WINWORD caused an invalid page fault in module MSO97.DLL at 017f:306c26c3
Registers
EAX=00c5eff0 CS=017f EIP=306c26c3 EFLGS=00010216 EBX=00c50000 SS=018
ESP=0062ee38 EBP=0000000
ECX=00c50000 DS=0187 ESI=00c50000 FS=3cef EDX=00c5716c ES=0187 EDI=00c5106
GS=000
Bytes at CS:EIP
66 8b 30 66 85 f6 74 1d 8b f8 33 c0 66 8b c6 8
Stack dump
0000004c 000003f7 306c24e9 00000237 00c5716c 0062eeb4 00000000 00c5716
00000003 0000000
306c2778 00c5716c 0000004c 3000e24f 00c57170 0000000

The address is different than those talked about in the knowledge base

Word then hangs and I have to use ctrl-alt-delete to shut down the documen
and subsequently Word

I also got this error with Office 2000. I removed it and assumed that th
earlier version of Office would work better and faster with Windows 98. N
joy. I am trying to install 32 computers in the next couple of days befor
the students get back. I could use any help that anyone can give. If yo
can reply to the email address I would appreciate it

Geoff Bickfor
(e-mail address removed)

 

[hakipuugeek]

Just an addendum. Thanks fr the advise. I reinstalled the driver of the disc locally and then connected it to the networked printer and the problem went away. Thanks again.

----- hakipuugeek wrote: -----

I installed the printer with the add printer wizard and used the network printer option. It has worked fairly well before and has only given me a hiccup with this installation. It works for the other Office products like Excel and Powerpoint. Just not the Word files. They are connected in a peer to peer network using Cat5 cables and a central switch and a WINS server in the system. The port that the printer drivers print to is the network address of the printer. EX:\\host\printername. Again it works well in every other application which tells me that the MSO97.dll file is not corrupt. It also happened when I initially installed Office 2000. I uninstalled it, removed the files and cleared the registry using a third party tool called regcleaner before I tried to install Office 97. I was hoping the new installation of Office 97 would speed things up and make the problem go away. NO luck there.

I am at a loss.

Geoff Bickford

----- TF wrote: -----

How is the printer installed? Did you install the printer driver locally and
point to the IP address of the shared printer? If not, how is it connected?
Sharing printers has always been a big problem in versions of Windows prior
to Windows 2000 and printing to a networked printer if a far more stable
solution than printing to a shared printer connected to someone's
workstation.

Also, Word is very heavy on printer drivers and needs one installed locally
to work efficiently.

--
Terry Farrell - Word MVP
http://www.mvps.org/word/

I did a clean install of Windows 98 and installed Office 97 on a Dell
Optiplex. I then ghosted the hard drive to another computer and when I try
to print to a network printer (A local printer shared on a peer to peer
network) I get the following error:

WINWORD caused an invalid page fault in module MSO97.DLL at 017f:306c26c3.
Registers:
EAX=00c5eff0 CS=017f EIP=306c26c3 EFLGS=00010216 EBX=00c50000 SS=0187
ESP=0062ee38 EBP=00000000
ECX=00c50000 DS=0187 ESI=00c50000 FS=3cef EDX=00c5716c ES=0187 EDI=00c51068
GS=0000
Bytes at CS:EIP:
66 8b 30 66 85 f6 74 1d 8b f8 33 c0 66 8b c6 8b
Stack dump:
0000004c 000003f7 306c24e9 00000237 00c5716c 0062eeb4 00000000 00c5716c
00000003 00000000
306c2778 00c5716c 0000004c 3000e24f 00c57170 00000000

The address is different than those talked about in the knowledge base.

Word then hangs and I have to use ctrl-alt-delete to shut down the document
and subsequently Word.

I also got this error with Office 2000. I removed it and assumed that the
earlier version of Office would work better and faster with Windows 98. No
joy. I am trying to install 32 computers in the next couple of days before
the students get back. I could use any help that anyone can give. If you
can reply to the email address I would appreciate it.

Geoff Bickford
(e-mail address removed)

 

[TF]

I'm please that fixed it for you. I've seem a similar problem on many
occasions. Usually the printer has been installed locally but by
'double-clicking' the printer across the network, so getting the driver
installed from the host (usually a server). This just doesn't seem to work
the same as installing the driver locally straight from the disk and
pointing the Port to the IP address or UNC address of the printer.

Terry


Just an addendum. Thanks fr the advise. I reinstalled the driver of the
disc locally and then connected it to the networked printer and the problem
went away. Thanks again.

----- hakipuugeek wrote: -----

I installed the printer with the add printer wizard and used the
network printer option. It has worked fairly well before and has only given
me a hiccup with this installation. It works for the other Office products
like Excel and Powerpoint. Just not the Word files. They are connected in
a peer to peer network using Cat5 cables and a central switch and a WINS
server in the system. The port that the printer drivers print to is the
network address of the printer. EX:\\host\printername. Again it works well
in every other application which tells me that the MSO97.dll file is not
corrupt. It also happened when I initially installed Office 2000. I
uninstalled it, removed the files and cleared the registry using a third
party tool called regcleaner before I tried to install Office 97. I was
hoping the new installation of Office 97 would speed things up and make the
problem go away. NO luck there.

I am at a loss.

Geoff Bickford

----- TF wrote: -----

How is the printer installed? Did you install the printer driver
locally and
point to the IP address of the shared printer? If not, how is it
connected?
Sharing printers has always been a big problem in versions of
Windows prior
to Windows 2000 and printing to a networked printer if a far more
stable
solution than printing to a shared printer connected to someone's
workstation.

Also, Word is very heavy on printer drivers and needs one
installed locally
to work efficiently.

--
Terry Farrell - Word MVP
http://www.mvps.org/word/

I did a clean install of Windows 98 and installed Office 97 on a
Dell
Optiplex. I then ghosted the hard drive to another computer and
when I try
to print to a network printer (A local printer shared on a peer to
peer
network) I get the following error:

WINWORD caused an invalid page fault in module MSO97.DLL at
017f:306c26c3.
Registers:
EAX=00c5eff0 CS=017f EIP=306c26c3 EFLGS=00010216 EBX=00c50000
SS=0187
ESP=0062ee38 EBP=00000000
ECX=00c50000 DS=0187 ESI=00c50000 FS=3cef EDX=00c5716c ES=0187
EDI=00c51068
GS=0000
Bytes at CS:EIP:
66 8b 30 66 85 f6 74 1d 8b f8 33 c0 66 8b c6 8b
Stack dump:
0000004c 000003f7 306c24e9 00000237 00c5716c 0062eeb4 00000000
00c5716c
00000003 00000000
306c2778 00c5716c 0000004c 3000e24f 00c57170 00000000

The address is different than those talked about in the knowledge
base.

Word then hangs and I have to use ctrl-alt-delete to shut down the
document
and subsequently Word.

I also got this error with Office 2000. I removed it and assumed
that the
earlier version of Office would work better and faster with
Windows 98. No
joy. I am trying to install 32 computers in the next couple of
days before
the students get back. I could use any help that anyone can give.
If you
can reply to the email address I would appreciate it.

Geoff Bickford
(e-mail address removed)