"Windows Low On Memory" Error

[Scott]

Attempting to open/convert Publisher 2000 files with Publisher 2003.

Attempted on machines running XP SP1 (PIII 500Mhz/384Mb ram, McAfee
7.0) and XP SP2 (McAfee 8.0, AMD 64 3.0Ghz/2Gb RAM).

Found many links referencing scripting and interference with Norton
antivirus. Verified McAfee Virus settings do not prevent scripting.

Found many links referencing fragmentation of the pagefile or not a
large enough pagefile (3x Publisher file size minimum). Both machines
recently defragged and the AMD machine has a 3 Gb (with a max set to
4gb) pagefile.

Possible XP SP2 issue, so I attempted on a box I have not yet applied
XP SP2 on and had the same result.

I've also attempted this on Publisher files that are < 6Mb since the
original issue appeared on a 65Mb Publisher file.

Any ideas? Any help appreciated. Thank you in advance.

 

[Mary Sauer]

Large Publisher 2000 publication opens slowly in Publisher 2002 or 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;289010

Earlier there was a poster who made a change in McAfee. She did specifically say what
it was but maybe you can sort it out with this quote...
"I do not have Norton, as I use McAfee; but I went in and changed the
security to disable script blocking. Then I found a note from McAfee in
reference to another setting that might need changed in Internet Explorer 6
(with Windows XP SP2 updates), and made that change as well."

 

[Scott]

Thanks Mary.

I disabled McAfee services on both machines (again one is XP SP1 with
McAfee 7.0 and the other XP SP2 with McAfee 8.0). I've checked the
Security tab, Scripting and all are currently enabled. I searched the
KB on McAfee's site and didn't find any relative results.

 

[Scott]

I have been accessing the Publisher 2000 file with Publisher 2003 via
a network drive. Just out of curiosity I copied the file locally and
tried it again. It wasn't the cure-all, but I noticed the "Windows
Low On Memory" error popped up immediately when accessing it locally.
I can only assume the delay in opening it from the network drive is
due to the local caching of the file?

I took the disabling of McAfee one step further and went to msconfig
and removed the McAfee services and startup items and rebooted. This
didn't change anything when I attempted to convert the file again.

Oh, another difference is that I kept Office 2003 "out of the box" and
didn't apply any Office updates to the low end machine (XP SP1, PIII
500 384 Mb RAM). The Office 2003 on the AMD / high end box (XP SP2,
AMD 64 3.0 2Gb RAM) has all of the Office Updates.

I'm running out of ideas and time. I hate to have to recreate this
monthly publication from scratch AND not be able to open my previous
two years of publications for historical reference!

 

[Mary Sauer]

Can you send me the file? Maybe some corruption is going on.
Remove "my" to reply.

 

[Mary Sauer]

This article may help
You receive a "Not enough memory to load graphics or embedded objects" error message
when you open a Publisher 2000 publication
http://support.microsoft.com/default.aspx?scid=kb;en-us;262855

 

[Robin C.]

Having the exact same problem as Scott so I didn't start a new thread. I've
made sure that I have adequate paging memory, turned off hardware
acceleration for the video card, emptied temp folders, turned off McAfee 8.0
and monitored memory useage with Task Manager. My files aren't large -- 20 -
50 MB. All of my files are subsets of a larger document so it is possible I
have something in common -- I just can't find the problem. Possibly too many
objects? Some common corruption? Pictures at large resolution? Any ideas?
Thanks.