Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jouke (587)


Jouke has been programming Perl since 1997 and started using Perl to write programs to make life and communication easier for disabled people early 2001. Take a look at his website [] for more information.

Journal of jouke (587)

Monday May 17, 2004
02:10 AM

pVoice 2.1 as good as finished (or not?)

[ #18785 ]
After fixing the bug I've been working on for months, I continued to finish pVoice 2.1. Except for some non-coding work (like writing the Dutch helpfiles and things like that) it all works now.

I created a standalone executable of this with PAR on my Windows XP system, ran it there and everything worked fine. I then moved the file to my daughter's Win 98 SE machine, and the executable failed to start, giving me an access violation in 7049C8B1.DLL. Now I presume this DLL is somewhere in the PAR generated .exe, but I can't find it. And since it's not giving me any useable information on *what* is actually going wrong I don't know what to do next.

ActiveState's PerlApp isn't very helpful either, because it can't handle BOM and (afaik) I need it in my preferences dialog (where you can select your language).

Suggestions welcome...
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • This might be a red herring, but is wxWidgets built to use unicows.dll?

    What happens if you run pVoice on your win98 box without PAR?

    • I intentionally used a non-unicode version of wxPerl to prevent possible problems, if that runs, I'll use a Unicode version, indeed using MSLU=1 and thus the unicows.dll.
      The problem just became weirder...I set up a Windows 98 SE environment in VMWare (under my XP system), installed pVoice 2.1-to-be there and it works like a charm. Same amount of memory, same amount of harddisk space.
      Now I must say that the system on which it failed runs Win98SE for 4 consecutive years now, so I'm beginning to think I'll nee