As an unabashed fan of perl2exe, I'm curious about your "bugginess" comment. I've used it without a hitch on programs incorporating a wide range of modules, including Tk and Windows serial I/O. What sorts of problems are you encountering? | [reply] |
Find a WinNT box (or scrounge up a, um, underutilized CD of WinNT and dual-boot your WinME box) and compile your application there with PerlApp.
It will run just fine on WinME, Win98, or whatever.
The requirement for PerlApp is only the flavor of Windows on which it will compile and is not a restriction on the flavor of Windows on which it will run.
On a side note, I'm a big fan of PerlApp. It's well written and has given me few problems.
Hope this helps :-)
| [reply] |
well, i know perlapp generated programs run fine on me, but i wanna USE perlapp on me...what do you mean dual-boot? how do i do that?
| [reply] |
In that case, you should complain to Microsoft. The APIs necessary for PerlApp aren't included with WinME. In fact, the guts of the various Microsoft flavors are quite different across the board. Honestly, I've had more problems porting from Win98 to WinNT than Win98 to Solaris for some applications.
(I'm done ranting now.)
As far as dual boot, it means that you have two operating systems on one computer (e.g., WinME and WinNT). I don't know how it's done on Windows. On Linux, it's such old hat that you could probably find a score of HOWTOs on the web.
On Windows, if you have to ask what dual-booting means, you're probably better off spending some money on a commercial package (for example System Commander) that will walk you through the process.
Hope this helps :-)
| [reply] |
As a developer, why are you using Windows Me?
(not bashing -- any advise on "update" or "dual boot it" needs to know details as to why you're using a OS intended for computer-as-appliance-for-barely-literate. E.g. that's all that runs on the hardware.)
I wonder if the Perl2Exe problems are related to that.
| [reply] |