C
Carlo R
Hoping someone can offer some assistance:
Any idea why Publisher 2003 would cause a machine to lock up?
This has happened on a couple of machines in my office now. One was an
upgrade installation on a machine that previously has Publisher 2000
installed on it. The other was on a stripped down machine where I had
completely removed MS Office 2000 and Outlook and then done a complete
install of Publisher 2003. Both machines froze up after Publisher 2003 was
in use.
Any assitance would be appreciated.
Specifics: Dell Optiplex GX240 or GX260, running Windows 2000 SP4; Pentium
4; minimum 256K RAM (I even tried adding extra memory to one machine and it
still locked up); 18 GB Hard Drive, with at least 10 GB free; ATI RADEON 7500
video driver with Dell M991 monitors.
Installed locally as part of Microsoft Office and installed into its own
folder, NOT installed and running from network.
No error messages and nothing reported in Event Viewer.
In many instances, this was the ONLY program that was actively running and
it still froze up, though there could have been a few others in the
background, but even beefed up to 384K RAM?
Any idea why Publisher 2003 would cause a machine to lock up?
This has happened on a couple of machines in my office now. One was an
upgrade installation on a machine that previously has Publisher 2000
installed on it. The other was on a stripped down machine where I had
completely removed MS Office 2000 and Outlook and then done a complete
install of Publisher 2003. Both machines froze up after Publisher 2003 was
in use.
Any assitance would be appreciated.
Specifics: Dell Optiplex GX240 or GX260, running Windows 2000 SP4; Pentium
4; minimum 256K RAM (I even tried adding extra memory to one machine and it
still locked up); 18 GB Hard Drive, with at least 10 GB free; ATI RADEON 7500
video driver with Dell M991 monitors.
Installed locally as part of Microsoft Office and installed into its own
folder, NOT installed and running from network.
No error messages and nothing reported in Event Viewer.
In many instances, this was the ONLY program that was actively running and
it still froze up, though there could have been a few others in the
background, but even beefed up to 384K RAM?