Semagic - blah

[plonq]

The latest Semagic has become an unstable piece of excrement under Win2K. I'm going to see if I have an older version that I can roll back to, but right now I'm dead in the water. =/

Has anyone else had problems with the later versions? Does anyone else out there use Semagic?

[Edit: I found an older version kicking around and it runs just fine, so until further notice I'm going to keep using version 1.5.1.5U.]

Comments

[feren.livejournal.com]

I've been using Semagic for the last year and a half or so, running on both 2k and on XP. I don't have the most current version (1.5.3.1) on either OS so I can't vouch for the (in)sanity of it. However, my Win2k box is currently using version 1.5.2.6U and it has behaved admirably for me.

[quirrc.livejournal.com]

when exactly did it crash? could you mail me a crash dump that was saved into semagic folder?

[plonq.livejournal.com]

It started crashing right after I upgraded to the latest version. It complained that "dgbhelp.dll" was the wrong version on my computer, or that it couldn't find the dll at all (it changed from run to run). I updated the dll from the version on the Microsoft site, but that didn't seem to help.

Even the older version (1.5.1.5U) even tends to crash at random (in fact it just spontaneously died again while I was typing this). Not sure if this helps, but the requestor reads as follows:

The instruction "0x76ff4b77" referenced memory at "0x00eee258". The memory could not be "read".

I should mention that I am running the latest version at home under XP Pro, and it's stable and happy there. It's only on this Win2K machine at work that I'm having problems (and given some of the funky things they've done with this version of Win2K I'm surprised that ANYTHING runs).

I've found the dump file you mentioned, and I'll mail it to you momentarily. Hope it helps!

[quirrc.livejournal.com]

http://www.livejournal.com/community/ljwin32_sema/11901.html?thread=1770621#t1770621

one user reported the same behavior on 2k, the dump that I got from him showed error at the same place inside the program and that place cannot contain error. So my guess was that there is a random memory corruption that depends on previous operations that the program performed (opened history, used auto spellchecker etc.)
then I provided 2 versions to try so I can compare dumps and maybe guess the source of the memory leak. But before I also made certain change with login window that normally should not change anything but for that user turned out to solve the problem. your dump showed memory error inside CRT and other threads of the program itself already terminated so that info does not help much.
Try both versions from that link, if 2k crashes and 9x not, continue to use 9x version. If both crash, mail me dumps for both programs but if they will be like the previous that won't help much.

[plonq.livejournal.com]

I've removed and installed both versions from that link, and so far I haven't been able to get either one of them to crash on this Win2K box.

I have the XP/2K version running right now and I'll let you know if it starts misbehaving again. So far so good.