From: paul <pl...@ro...> - 2002-12-26 08:00:29
|
I am having problems starting MH 2.75 using Perl 5.8. Keep getting the following error at startup. ============================================ Code Directories: - E:/misterhouse_src_275/paul/code - ./../code/common Perl diaganotics module (perl -w) has been turned on Loading Windows modules Error in loading module=Win32::DriveInfo: Can't locate Win32/API.pm in @INC (@INC contains: E:/misterhouse_src_275/paul/ code ./../code/common ./../lib ./../lib/site . C:/Perl/lib C:/Perl/site/lib . ./ ../lib/site_win58) at ../lib/site/Win32/DriveInfo.pm line 5. BEGIN failed--compilation aborted at ../lib/site/Win32/DriveInfo.pm line 5. Compilation failed in require at (eval 26) line 2. BEGIN failed--compilation aborted at (eval 26) line 2. - See install.html for instructions on how to install perl module Win32::DriveI nfo Error in loading module=Win32::SerialPort: Can't locate Win32/API.pm in @INC (@INC contains: E:/misterhouse_src_275/paul/ code ./../code/common ./../lib ./../lib/site . C:/Perl/lib C:/Perl/site/lib . ./ ../lib/site_win58) at ../lib/site/Win32API/CommPort.pm line 5. BEGIN failed--compilation aborted at ../lib/site/Win32API/CommPort.pm line 5. Compilation failed in require at ../lib/site/Win32/SerialPort.pm line 4. BEGIN failed--compilation aborted at ../lib/site/Win32/SerialPort.pm line 4. Compilation failed in require at (eval 42) line 2. BEGIN failed--compilation aborted at (eval 42) line 2. - See install.html for instructions on how to install perl module Win32::Serial Port ================================================================= I search for API.PM and found it in the following directories: ./../lib/site_win50 ./../lib/site_win56 The error looks like it is trying to find API.PM in site_win58 directory however I cannot find site_win58 directory in the distro. Anyone else have this problem or have any suggestion(s) ? Paul |
From: Tom K. <tko...@in...> - 2002-12-26 16:24:32
|
Paul. I have been having similar problems with my Perl 5.80 installation. I did a check and found that the perl directory that I have in the perl path in my Autoexec.bat, the perl environmental variables shown by executing >perl -V from DOS and the perl Verison indicated by MH (5.008) do not agree. I'm in the process of sorting this out. Regards, Tom ----- Original Message ----- From: "paul" <pl...@ro...> To: <mis...@li...> Sent: Thursday, December 26, 2002 3:01 AM Subject: [misterhouse-users] Startup problems with Perl 5.8 and MH 2.75 > I am having problems starting MH 2.75 using Perl 5.8. > Keep getting the following error at startup. > ============================================ > Code Directories: > - E:/misterhouse_src_275/paul/code > - ./../code/common > Perl diaganotics module (perl -w) has been turned on > Loading Windows modules > > Error in loading module=Win32::DriveInfo: > Can't locate Win32/API.pm in @INC (@INC contains: > E:/misterhouse_src_275/paul/ > code ./../code/common ./../lib ./../lib/site . C:/Perl/lib C:/Perl/site/lib > . ./ > ../lib/site_win58) at ../lib/site/Win32/DriveInfo.pm line 5. > BEGIN failed--compilation aborted at ../lib/site/Win32/DriveInfo.pm line 5. > Compilation failed in require at (eval 26) line 2. > BEGIN failed--compilation aborted at (eval 26) line 2. > - See install.html for instructions on how to install perl module > Win32::DriveI > nfo > > > Error in loading module=Win32::SerialPort: > Can't locate Win32/API.pm in @INC (@INC contains: > E:/misterhouse_src_275/paul/ > code ./../code/common ./../lib ./../lib/site . C:/Perl/lib C:/Perl/site/lib > . ./ > ../lib/site_win58) at ../lib/site/Win32API/CommPort.pm line 5. > BEGIN failed--compilation aborted at ../lib/site/Win32API/CommPort.pm line 5. > Compilation failed in require at ../lib/site/Win32/SerialPort.pm line 4. > BEGIN failed--compilation aborted at ../lib/site/Win32/SerialPort.pm line 4. > Compilation failed in require at (eval 42) line 2. > BEGIN failed--compilation aborted at (eval 42) line 2. > - See install.html for instructions on how to install perl module > Win32::Serial > Port > ================================================================= > I search for API.PM and found it in the following directories: > ./../lib/site_win50 > ./../lib/site_win56 > > The error looks like it is trying to find API.PM in site_win58 directory > however I cannot find site_win58 directory in the distro. > > Anyone else have this problem or have any suggestion(s) ? > > Paul > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > |
From: Bruce W. <br...@mi...> - 2002-12-26 20:08:15
|
> I am having problems starting MH 2.75 using Perl 5.8. > Keep getting the following error at startup. > ============================================ > Code Directories: > - E:/misterhouse_src_275/paul/code > - ./../code/common > Perl diaganotics module (perl -w) has been turned on > Loading Windows modules > > Error in loading module=Win32::DriveInfo: > Can't locate Win32/API.pm in @INC (@INC contains: > E:/misterhouse_src_275/paul/ > code ./../code/common ./../lib ./../lib/site . C:/Perl/lib > C:/Perl/site/lib > . ./../lib/site_win58) at ../lib/site/Win32/DriveInfo.pm line 5. My bad. I had created a mh/lib/site_win58 dir here, but forgot to add it to the packageing script, so it never made it into the source zip file. It looks like ActiveState started to put the Win32::API module in their 5.8 distro, but didn't do it correctly. I had to manually install it here (I forgot how, maybe with ppm, but I think maybe that failed also). I just copied the mh\lib\site_win58\*.* files to here: http://misterhouse.net/public/mh_win58.zip unzip from one dir above your mh dir (i.e. the interanal zip path is mh/lib/site_win58) Bruce |
From: Bruce W. <br...@mi...> - 2002-12-26 22:27:55
|
> > I am having problems starting MH 2.75 using Perl 5.8. On a related topic, our new friend Randy Kobes just compiled the Win32-Setupsup module for us (lets us control other windows with SendKeys). That was the last windows module missing from 5.8. To install: ppm > repository add http://theoryx5.uwinnipeg.ca/cgi-bin/ppmserver?urn:/PPMServer58 ppm> install Win32-Setupsup I think you don't need to do the repository add if you already did it to install the other modules. Bruce |
From: paul <pl...@ro...> - 2002-12-27 23:39:24
|
> > > I am having problems starting MH 2.75 using Perl 5.8. > >On a related topic, our new friend Randy Kobes just compiled the >Win32-Setupsup module for us (lets us control other windows with SendKeys). >That was the last windows module missing from 5.8. To install: > > ppm > repository add >http://theoryx5.uwinnipeg.ca/cgi-bin/ppmserver?urn:/PPMServer58 > ppm> install Win32-Setupsup > >I think you don't need to do the repository add if you already did it to >install the other modules. > >Bruce Bruce, I downloaded http://misterhouse.net/public/mh_win58.zip and copy to mh\lib\ directory it works fine. Thanks fyi ... I tried ppm to install Win32-Setupsup and getting this error: "Error: no suitable installation target found for package Win32-Setupsup." It looks like the Win32-Setupsup module is not there. |
From: Bruce W. <br...@mi...> - 2002-12-28 06:06:09
|
Paul, Did you do that 'repository add' command first? Anyone else try the Win32-Setupsup on 5.8 yet? Bruce -----Original Message----- > > I am having problems starting MH 2.75 using Perl 5.8. On a related topic, our new friend Randy Kobes just compiled the Win32-Setupsup module for us (lets us control other windows with SendKeys). That was the last windows module missing from 5.8. To install: ppm > repository add http://theoryx5.uwinnipeg.ca/cgi-bin/ppmserver?urn:/PPMServer58 ppm> install Win32-Setupsup ... fyi ... I tried ppm to install Win32-Setupsup and getting this error: "Error: no suitable installation target found for package Win32-Setupsup." It looks like the Win32-Setupsup module is not there. |
From: paul <pl...@ro...> - 2002-12-29 02:03:35
|
Bruce, I think my ppm is messed up. I found Win32-Setupsup when I search the repository and when I display the ppm target, it only have perl 5.6. I think that's why I am getting the error because 5.8 is not in the target. I uninstall both perl 5.6 and 5.8 and reinstall 5.8 to see if 5.8 will be in the target. Now I can't get ppm to start ... Not good :( Once I get 5.8 ppm working, I''ll try install Win32-Setupsup again. What better way to learn about Perl and ppm. ;) Paul >Paul, > >Did you do that 'repository add' command first? Anyone else try the >Win32-Setupsup on 5.8 yet? > >Bruce > >-----Original Message----- > > > > I am having problems starting MH 2.75 using Perl 5.8. > >On a related topic, our new friend Randy Kobes just compiled the >Win32-Setupsup module for us (lets us control other windows with SendKeys). >That was the last windows module missing from 5.8. To install: > > ppm > repository add >http://theoryx5.uwinnipeg.ca/cgi-bin/ppmserver?urn:/PPMServer58 > ppm> install Win32-Setupsup > >... > >fyi ... I tried ppm to install Win32-Setupsup and getting this error: >"Error: no suitable installation target found for package Win32-Setupsup." >It looks like the Win32-Setupsup module is not there. > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >________________________________________________________ >To unsubscribe from this list, go to: >http://sourceforge.net/mail/?group_id=1365 |
From: Steve S. <st...@sw...> - 2002-12-27 03:53:20
|
Bruce, Based on the below, I thought I'd share my idea for an MH directory structure, as I thought it would be nice to incorporate this into the distro. (best viewed with a fixed width font) \mh \2.74 <-- from distro zip, renamed mh dir to version # \bin \code \common ...etc \data \lib \sounds \web \2.75 <-- from distro zip, renamed mh dir to version # \bin \code \common ...etc \data \lib \sounds \web \data \web \code <-- my private code directory \sounds \mh.private.ini When I download a new version, I simply unzip and copy to a new dir, based on the version number. The environment vars point to my mh.private.ini, which setup references to my private code, data, sound, etc directories, and many other parms. When I first started running MH, the upgrade procedure (and the installation/config procedure) confused me to no end. I couldn't figure out how to upgrade without re-modifying al the code files, or remembering to copy the updated code files to the new version, overwriting the old code, etc. If you included this type of directory structure inside the distro zip files, it would be much more plain on how to upgrade, as simply unzipping over the root directory would copy the new version into a new directory, leaving the old version completely available should something go totally wrong with the new version. When I upgrade, I simply modify the shortcut to point to: "c:\mh\2.75\bin\mh.bat" instead of: "c:\mh\2.74\bin\mh.bat" (and do the same to "start in" dir) This has proven to be a very quick and painless way to upgrade/downgrade as often as I want to... Iv'e even created a few "2.74test1,2,3" directories while we were creating the "respond" functionality. :) It worked well. All this said, I hope you can take this idea and use it to incorporate an easier to recognise directory structure. To avoid overwriting the user's private dir structure, maybe we should have a zip inside of a zip. IN the main zip there's only a version dir (2.75) and a user.zip and maybe a readme.txt file. Unzipping user.zip within that dir will create the user's private code/sound/web/etc directories, with text code in the user dir. Including this in the main zip would add the test code to the user's dir every time they upgraded! It might be annoying to find your MH install running goofy.pl after every upgrade! LOL Thanks for listening to my ramblings... I'm too tired to proofread, I hope it makes sense. :) -- Steve Switzer steve (at) switzerny (dot) org Quoting Bruce Winter <br...@mi...>: ... > I just copied the mh\lib\site_win58\*.* files to here: > > http://misterhouse.net/public/mh_win58.zip > > unzip from one dir above your mh dir (i.e. the interanal zip path is > mh/lib/site_win58) > > Bruce |
From: Pete F. <pj...@ca...> - 2002-12-27 04:37:07
|
Steve, Bruce Sorry I must disagree, I'm on Linux, and I really like the rpm updates. Perhaps we could so something similar using an 'old' structure that parallels the the current (I do this anyway for reference and backtracking a rev out). At least this won't gobble up the Drive space so quickly. unless of course the sub-dir structure Steve suggests is a 'diff' between revs (of course the customs wind up being diffs too). I'm not saying It's a bad Idea, but I think we need to keep the newbies in mind, as well as developers, we don't want to upgrade them out of disk space. Trust me on this one I've seen a lot of '10t errors that were even simpler than running low on space .... after all the distro is starting to plump up (RPM's are over 5M now). If we do a diff we'll need to make it simple for everyone (more man pages too of course). Bruce, Speaking of upgrade glitches ... the 'setup' (web menu setup functions) settings seem to be getting overwritten. I noticed it first 2 revs ago, but I thought it was me ;) It happened again on the 2.75 update, so I suspect I'm not alone (now)...maybe the modules just changed, or I've been staring at QNX code way too long, or (most likely) I'm just loosing it. Cheers Pete Flaherty On Thu, 2002-12-26 at 22:53, Steve Switzer wrote: > Bruce, > Based on the below, I thought I'd share my idea for an MH directory > structure, as I thought it would be nice to incorporate this into the distro. > (best viewed with a fixed width font) > > \mh > \2.74 <-- from distro zip, renamed mh dir to version # > \bin > \code > \common > ...etc > \data > \lib > \sounds > \web > \2.75 <-- from distro zip, renamed mh dir to version # > \bin > \code > \common > ...etc > \data > \lib > \sounds > \web > \data > \web > \code <-- my private code directory > \sounds > \mh.private.ini > > When I download a new version, I simply unzip and copy to a new dir, based on > the version number. The environment vars point to my mh.private.ini, which > setup references to my private code, data, sound, etc directories, and many > other parms. > When I first started running MH, the upgrade procedure (and the > installation/config procedure) confused me to no end. I couldn't figure out > how to upgrade without re-modifying al the code files, or remembering to copy > the updated code files to the new version, overwriting the old code, etc. > If you included this type of directory structure inside the distro zip > files, it would be much more plain on how to upgrade, as simply unzipping over > the root directory would copy the new version into a new directory, leaving > the old version completely available should something go totally wrong with > the new version. > When I upgrade, I simply modify the shortcut to point to: > "c:\mh\2.75\bin\mh.bat" > instead of: > "c:\mh\2.74\bin\mh.bat" > (and do the same to "start in" dir) > > This has proven to be a very quick and painless way to upgrade/downgrade as > often as I want to... Iv'e even created a few "2.74test1,2,3" directories > while we were creating the "respond" functionality. :) It worked well. > > All this said, I hope you can take this idea and use it to incorporate an > easier to recognise directory structure. > > To avoid overwriting the user's private dir structure, maybe we should have a > zip inside of a zip. IN the main zip there's only a version dir (2.75) and a > user.zip and maybe a readme.txt file. Unzipping user.zip within that dir will > create the user's private code/sound/web/etc directories, with text code in > the user dir. Including this in the main zip would add the test code to the > user's dir every time they upgraded! It might be annoying to find your MH > install running goofy.pl after every upgrade! LOL > > Thanks for listening to my ramblings... I'm too tired to proofread, I hope it > makes sense. :) > > -- > Steve Switzer > steve (at) switzerny (dot) org > > > Quoting Bruce Winter <br...@mi...>: > > ... > > I just copied the mh\lib\site_win58\*.* files to here: > > > > http://misterhouse.net/public/mh_win58.zip > > > > unzip from one dir above your mh dir (i.e. the interanal zip path is > > mh/lib/site_win58) > > > > Bruce > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > |
From: Steve S. <st...@sw...> - 2002-12-27 04:57:29
|
Pete, I would suggest also changing the target directory for the RPM files as well, so upgrades would as well be this easy. When I move back to Linux, I will probably do it this way as well... but only if I can maintain a directory structure like that one I currently have. Of course, last time I used Linux for MH, I wasn't very familiar with MH... so I am probably missing something, but maybe it's negligeable or easily dealt with. -- Steve Switzer steve (at) switzerny (dot) org Quoting Pete Flaherty <pj...@ca...>: > Steve, Bruce > > Sorry I must disagree, I'm on Linux, and I really like the rpm updates. > Perhaps we could so something similar using an 'old' structure that > parallels the the current (I do this anyway for reference and > backtracking a rev out). At least this won't gobble up the Drive space > so quickly. unless of course the sub-dir structure Steve suggests is a > 'diff' between revs (of course the customs wind up being diffs too). > I'm not saying It's a bad Idea, but I think we need to keep the newbies > in mind, as well as developers, we don't want to upgrade them out of > disk space. Trust me on this one I've seen a lot of '10t errors that > were even simpler than running low on space .... after all the distro is > starting to plump up (RPM's are over 5M now). If we do a diff we'll > need to make it simple for everyone (more man pages too of course). > > Bruce, > Speaking of upgrade glitches ... the 'setup' (web menu setup functions) > settings seem to be getting overwritten. I noticed it first 2 revs ago, > but I thought it was me ;) It happened again on the 2.75 update, so I > suspect I'm not alone (now)...maybe the modules just changed, or I've > been staring at QNX code way too long, or (most likely) I'm just loosing > it. > > Cheers > Pete Flaherty > > > On Thu, 2002-12-26 at 22:53, Steve Switzer wrote: > > Bruce, > > Based on the below, I thought I'd share my idea for an MH directory > > structure, as I thought it would be nice to incorporate this into the > distro. > > (best viewed with a fixed width font) > > > > \mh > > \2.74 <-- from distro zip, renamed mh dir to version # > > \bin > > \code > > \common > > ...etc > > \data > > \lib > > \sounds > > \web > > \2.75 <-- from distro zip, renamed mh dir to version # > > \bin > > \code > > \common > > ...etc > > \data > > \lib > > \sounds > > \web > > \data > > \web > > \code <-- my private code directory > > \sounds > > \mh.private.ini |
From: Bruce W. <br...@mi...> - 2002-12-27 20:59:42
|
> Speaking of upgrade glitches ... the 'setup' (web menu setup functions) > settings seem to be getting overwritten. I noticed it first 2 revs ago, > but I thought it was me ;) It happened again on the 2.75 update, so I > suspect I'm not alone (now)...maybe the modules just changed, or I've > been staring at QNX code way too long, or (most likely) I'm just loosing > it. Do you mean the data_dir/select_code.txt and select_code2.txt files? These pick which files you want and don't want out of the common and user_code dirs. If you do not have your own data_dir, these indeed would be overwritten by the defaults in the mh/data_dir dir. To fix that problem, make your own data_dir, and point to it with your mh.ini data_dir parm. If that is not the problem, do you have a few more details? Bruce |
From: David N. <jud...@ad...> - 2002-12-27 19:39:06
|
I have almost the exact structure on my linux system. My parent directory is /misterhouse, not /mh to avoid confusion. The tar.gz distributions extract into misterhouse-2.75 directory, so I leave them that way and just create a symbolic link called "mh" that points to misterhouse-2.75. All I have to do to upgrade is un-tar the release into /misterhouse/misterhouse-2.xx and change the symbolic link /misterhouse/mh to point to it. Too bad Windows doesn't have symbolic links. The RPM folks don't care to keep multiple versions around, as we just heard. If they want to go back to an old version, they just install the old RPM file. This brings up another issue. We need a Windows Setup script for Misterhouse. It should setup the directory structure with custom code, data, sounds, and web directories. It should create a beginner private.ini and a program group with a shortcut to start misterhouse. Plus, it should handle upgrades and downgrades easily. Like the RPM users, these users won't want multiple versions installed as long as it's easy to downgrade. Anybody have experience with installers for Windows? David ----- Original Message ----- From: "Steve Switzer" <st...@sw...> To: <mis...@li...> Sent: Thursday, December 26, 2002 7:53 PM Subject: [misterhouse-users] MH installation directories > Bruce, > Based on the below, I thought I'd share my idea for an MH directory > structure, as I thought it would be nice to incorporate this into the distro. > (best viewed with a fixed width font) > > \mh > \2.74 <-- from distro zip, renamed mh dir to version # > \bin > \code > \common > ...etc > \data > \lib > \sounds > \web > \2.75 <-- from distro zip, renamed mh dir to version # > \bin > \code > \common > ...etc > \data > \lib > \sounds > \web > \data > \web > \code <-- my private code directory > \sounds > \mh.private.ini > > When I download a new version, I simply unzip and copy to a new dir, based on > the version number. The environment vars point to my mh.private.ini, which > setup references to my private code, data, sound, etc directories, and many > other parms. > When I first started running MH, the upgrade procedure (and the > installation/config procedure) confused me to no end. I couldn't figure out > how to upgrade without re-modifying al the code files, or remembering to copy > the updated code files to the new version, overwriting the old code, etc. > If you included this type of directory structure inside the distro zip > files, it would be much more plain on how to upgrade, as simply unzipping over > the root directory would copy the new version into a new directory, leaving > the old version completely available should something go totally wrong with > the new version. > When I upgrade, I simply modify the shortcut to point to: > "c:\mh\2.75\bin\mh.bat" > instead of: > "c:\mh\2.74\bin\mh.bat" > (and do the same to "start in" dir) > > This has proven to be a very quick and painless way to upgrade/downgrade as > often as I want to... Iv'e even created a few "2.74test1,2,3" directories > while we were creating the "respond" functionality. :) It worked well. > > All this said, I hope you can take this idea and use it to incorporate an > easier to recognise directory structure. > > To avoid overwriting the user's private dir structure, maybe we should have a > zip inside of a zip. IN the main zip there's only a version dir (2.75) and a > user.zip and maybe a readme.txt file. Unzipping user.zip within that dir will > create the user's private code/sound/web/etc directories, with text code in > the user dir. Including this in the main zip would add the test code to the > user's dir every time they upgraded! It might be annoying to find your MH > install running goofy.pl after every upgrade! LOL > > Thanks for listening to my ramblings... I'm too tired to proofread, I hope it > makes sense. :) > > -- > Steve Switzer > steve (at) switzerny (dot) org > > > Quoting Bruce Winter <br...@mi...>: > > ... > > I just copied the mh\lib\site_win58\*.* files to here: > > > > http://misterhouse.net/public/mh_win58.zip > > > > unzip from one dir above your mh dir (i.e. the interanal zip path is > > mh/lib/site_win58) > > > > Bruce > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > |
From: Bruce W. <br...@mi...> - 2002-12-27 20:59:42
|
> I have almost the exact structure on my linux system. My parent directory > is /misterhouse, not /mh to avoid confusion. The tar.gz distributions > extract into misterhouse-2.75 directory, so I leave them that way and just > create a symbolic link called "mh" that points to misterhouse-2.75. All I > have to do to upgrade is un-tar the release into > /misterhouse/misterhouse-2.xx and change the symbolic link /misterhouse/mh > to point to it. Too bad Windows doesn't have symbolic links. I use the same here, on both windows and linux. On windows, I simply rename the mh_version dir, to mh, or leave it as is if I do not need to have mh/bin in my path. Your directory structure graph matches the one in install.pod, except yours has more than one version of mh listed, and your mh dirs are not mh, but version numbers. I added an example of an old version of mh to the picture (attached). > This brings up another issue. We need a Windows Setup script for > Misterhouse. It should setup the directory structure with custom code, > data, sounds, and web directories. It should create a beginner > private.ini > and a program group with a shortcut to start misterhouse. Plus, it should > handle upgrades and downgrades easily. Like the RPM users, these users > won't want multiple versions installed as long as it's easy to downgrade. > Anybody have experience with installers for Windows? No experience here. An installer would indeed be nice. I looked at the windows msi installer once, but quickly got overwhelmed. Plus I didn't see a nice free version. Bruce ------- misterhouse--+ +--mh.private.ini <--- my private mh.ini parms +--code <--- my code +--data <--- my data +--sounds <--- my sounds +--mh-----+ <--- Current mh installed here +--bin +--code +--data +--docs +--lib +--sounds +--web +--mh_123-+ <--- Old mh 123 version +--bin +--code +--data +--docs +--lib +--sounds +--web |
From: Sean W. <li...@su...> - 2002-12-27 21:21:17
|
> No experience here. An installer would indeed be nice. I looked at the > windows msi installer once, but quickly got overwhelmed. Plus I > didn't see > a nice free version. > > Bruce Installshield is overpriced and dramatic overkill. You could always Pimp out the software. The WinAMP guys give out their installer software for free. I've never tried it, but there are lots of people using it so it can't be terrible. http://www.nullsoft.com/free/nsis/ -- Sean Walker http://sean.surfmy.net/ |