From: Kenneth J.Davis (jeremyd@computer.org)
Date: Thu Jun 13 2002 - 19:21:28 EDT
r coyne <duckingsnofair@yahoo.com> wrote on 6/13/2002 6:49:22 PM:
>
>I'm not sure whether I have one problem/bug or two, or
I'd say two, one with Word import and the other seems
like mismatched plugins.
>what component it's in, and I need some advice before
>I can clarify what's happening; anyway, I need a
>quick solution more than an eventual bugfix. So I
>figure, let's try this list first, and maybe do a
>formal Bug (or two) later if appropriate.
I am not sure about the Word doc crash, can you submit
the Word document that causes the crash along with
your bug report? or does it contain confidential material?
[without the document causing the crash, it may be
difficult to track down the cause]
>
>My situation: Someone sent me a couple of MS Word
>files/documents that I need to edit. (Sorry, I don't
..
>so I downloaded it and installed it. This is AbiWord
>1.0.2 with BiDi, the Windows Installer.
>
>System: WinNT4 with SP6, installed clean on an old PC
>I just bought second-hand. It's only 100/300 MHz, 64
>MB RAM and 3 GB HD, but there's not much on it yet, so
>no discernible cramping. Nothing on it that would
>have any obvious interaction with Abi (except perhaps
>in its Web features, which do not seem relevant -- I
>have installed Mozilla as my default browser).
Seems fine, though I haven't tried on NT4 in a while
>
>Installing Abi (the first time), I unchecked Update
>Registry, both shortcuts, and Clipart, and for
>safety's sake I chose to install as an unprivileged
>user, in a deeply nested directory. With other
>programs this has sometimes caused problems, but Abi
>seemed to install perfectly and in fact behaved
>impressively well -- just as an installer should.
good :-)
>
>Well, I ran Abi, and opened (File > Open) the first
>document, and it opened, edited, and Save[d]As just
>fine, no problems. I did this (so far as I recall) in
>a single burst/window, so there were not a lot of
>anythings open. So I Opened the second document --
>and Abi immediately closed itself. I tried this
>several times, always with the same result, and in the
>one case when I had the other doc also open
>underneath, it took that with it, too; in other words,
>the close is of the whole application, not just the
>window or document. At this point my list of files
>included one with extension .CRASH , which I did not
>look at, unfortunately, before deleting it, and no
>other CRASH file has since been created -- Might this
>have been Abi's emergency save of the *other* doc?
Unfortunately when AbiWord crashes (an internal error
occurs) then all open documents within the same instance
of AbiWord are gone (though it is possible to open multiple
instances of AbiWord). Yes, the .CRASH file is AbiWord's
attempt to save your current work, depending on the
cause of the crash, this may be an usable document, other
times you may be able to reclaim your text from it but
it isn't directly openable, or it may be useless.
>
>The problem document is longer than the other -- but
>still not long, only maybe a dozen pages compared to
>one -- and more complex, presumably with some
..
Can't comment here since I have barely looked at
the Word import code.
>I went back to abisource and downloaded abiImageMagick
>as looking the most relevant. And it seemed to
>install OK; the installer found the main Abi directory
>correctly, and I left it at that.
Ahh, you downloaded just the abiMagick plugin from
the plugins page, correct? Well it won't work.
The link was not updated for the 1.0.1 release,
and the rest of the plugins on that page are
for the 1.0.1 release. And your error message below
confirms this, as it is basically the error message
you get. I forget the correct URL, but check on
sourceforge for the Tools and IE (import/export) plugin
sets, as only the plugin sets were built for AbiWord 1.0.2
>
>But then on starting up Abi itself again, a new
>problem appeared. I got an alert: "AbiWord.exe -
>Entry Point Not Found / The procedure entry point
>?generateImage@FG_GraphicRaster@@UAEPAVGR_Image@@PAVGR_Graphics@@@Z
>could not be located in the dynamic link library
This particular plugin relies on an earlier release
of AbiWord.exe, so it is a correct message.
..
>"active," Magick was not. So I tried to "uninstall"
>it by hand, by renaming it so that the extension was
>no longer .dll , and thus presumably making it
odd, renaming the abiMagick.dll should have correctly
stopped the error message (when testing I often
rename them to do this), anyway, I suggest you
delete it.
>unfindable. But the entry-point problem/message
>remains, which I find quite mysterious.
see above, basically it is a mismatched plugin and
AbiWord.exe
>
>I returned to the (more critical) crash-on-open issue.
> A Bugzilla check suggested that it might matter *how*
>one opened the file: drag-and-drop might work where
>File > Open didn't. I tried this. Dragging into the
>Abi window/worksheet had exactly the same effect as
..
drag-n-drop and File->Open should both crash if it
really is a file import error (which is what it looks
like your problem is -- but I could be mistaken), the
other is probably an unrelated drag-n-drop crash.
..
>in what directories DrWatson needs to write, and
>whether it will overwrite or append to an existing
>(empty/blank) file with that name, so that I can allow
>it access *only* as truly needed? If I could do that,
>I could get more information out of this crash -- if
>it's really needed at all.
I know nothing of DrWatson (I always found it easier
to just let my debugger replace it).
>
>Also -- back to the entry-point issue -- it occurs to
..
>Magick. But since I don't understand this whole
>thing, can someone tell me exactly what DLLs are
>needed, and how/where Abi and Magick go about finding
>them; in other words, where might it help to put
>copies or links of them?
To run AbiWord all you really need is AbiWord.exe,
though for spell checking, help and various other
things you need the support files. The only executable
files are AbiWord.exe, Microsoft's files (Windows &
the C runtime library), and the plugins, which
are located in the plugins folder (found in a directory
relative to AbiWord.exe, ..\plugins\ ). All the plugins
are dlls that also link with AbiWord.exe, so it is
important that the plugins (DLLs) used are the ones meant
for a particular AbiWord.exe version. [Plugins may also
rely on external programs that are unrelated to AbiWord.]
>
>__________________________________________________
I suggest for the lesser problem you delete all the
plugins and if you still want them, install the plugins
for 1.0.2, as for the Word import problem, please check
AbiWord's bugzilla for any reports that match yours and
either add revelant information there (if possible with
the document causing the crash) or open a new bug as
appropriate.
Thank you,
Jeremy Davis
jeremyd@computer.org
-----------------------------------------------
To unsubscribe from this list, send a message to
abiword-user-request@abisource.com with the word
unsubscribe in the message body.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 20:41:21 EDT