Hey guys, sorry if I sound like a total noob here but I'm not used to Macs and I'm getting by the best way I can. I downloaded an .exe file (Microsoft Publisher 2000) and everything worked fine. However, when I go to open the MSPUB.exe file, I get the following error message: "Windows is low on memory, or your hard disk is full. Try closing other programs and freeing up some space on your hard disk before starting publisher."
Our computer at work is an iMac Tiger 10.4.11 and it has about 150 GB of memory available. Any help will be greatly appreciated!
Memory Problems when trying to open .exe
-
- Newbie
- Posts: 2
- Joined: Mon Aug 09, 2010 5:18 pm
Re: Memory Problems when trying to open .exe
According to the AppDB, Publisher 2000 has never worked due to the error message you cite.Rhinorocka14 wrote:Hey guys, sorry if I sound like a total noob here but I'm not used to Macs and I'm getting by the best way I can. I downloaded an .exe file (Microsoft Publisher 2000) and everything worked fine. However, when I go to open the MSPUB.exe file, I get the following error message: "Windows is low on memory, or your hard disk is full. Try closing other programs and freeing up some space on your hard disk before starting publisher."
http://appdb.winehq.org/objectManager.p ... ngId=31984
It also appears that no one has ever filed a bug for this. Please file one.
-
- Newbie
- Posts: 2
- Joined: Mon Aug 09, 2010 5:18 pm
new
I'm using the newest version of wine it was just downloaded last week and I will file a bug. Is there a craps chance in plungerville that the bug will be fixed in a week? Again, thank for the help meng keep it comin
There was a bug filed for a similar problem with Publisher 2003, but it was closed as a duplicate of another bug.marty39 wrote:Hello, was that bug ever filed? If it was, how can I find it? If not, I want to file it myself.
http://bugs.winehq.org/show_bug.cgi?id=14408
http://bugs.winehq.org/show_bug.cgi?id=7873
Thanks. You're right, it's a similar bug to 7873. The workaround for that one was to use winetricks to install dcom98. I did that, and now MS Publisher 2000 starts. But according to the discussion for 7873, that's just a workaround; the bug still needs to be fixed.
My next step is to see if Publisher 2000 works well enough for me to use it, and in any case I'll post an AppDB entry for it.
My next step is to see if Publisher 2000 works well enough for me to use it, and in any case I'll post an AppDB entry for it.