mpp-beta Mailing List for mIRC Power Pack

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

http://mircpowerpack.net/

i need some help testing the top 2 topics

-d

mIRC Power Pack 8.0.0 RC13 Build 7.167

After some delays, MPP RC13 has finally been released.

Grab it here:

http://sourceforge.net/project/showfiles.php?group_id=183794
<http://sourceforge.net/project/showfiles.php?group_id=183794&package_id=213
511&release_id=581015> &package_id=213511&release_id=581015

Report any problems to the forums or the mailing list.

/sgt

mIRC Power Pack 8.0.0 RC12 Released!

Codename:  Into The Lungs Of Hell

Build:  7.159

Date:  May 15, 2007

http://mIRCPowerPack.net/

CD-ROM ISO Images

CD-ROM ISO Images of MPP 8.0.0 RC12 are available NOW but ONLY upon email
request.

If you would like ALL of the files in the MPP 8.0.0 RC12 Release (221 megs!)
in one ISO file (that you can burn to a CD), send me an email message NOW
and request your ISO!

MPP-Beta Mailing List

If you are not signed up on the MPP-Beta Mailing List, you will not receive
future email messages.

To join the MPP Mailing Lists:  http://sourceforge.net/mail/?group_id=183794

/sgt

7.159...  anyone?

i'd like to release rc12 tomorrow, but i haven't gotten any feedback on
build 7.159.

i really need vista users to test this build and check the notes in the
readme.

let me know asap!

/sgt

build 7.159 "refresh" is ready for testing

build 7.159 fixes all currently known problems with windows vista (i hope).

refresh:  small problem, fixed, see the readme

readme:

http://mircpowerpack.net/mpp/7159/7159.txt

beta team...

update your svn folders, upgrade nsis to 2.27 and also install my new
plugins pack (below).  after installing nsis, put plugins.exe in your nsis
folder and double click it...  select "overwrite all" if prompted.  after
that, run your mpp installer build tools.

nsis 2.27

<http://superb-east.dl.sourceforge.net/sourceforge/nsis/nsis-2.27-setup.exe>
http://superb-east.dl.sourceforge.net/sourceforge/nsis/nsis-2.27-setup.exe

updated nsis plugins

 <http://ucheetmfer.com/files/plugins.exe>
http://ucheetmfer.com/files/plugins.exe

everyone else...

http://mircpowerpack.net/mpp/7159/

/sgt

build 7.159 is ready for testing

build 7.159 fixes all currently known problems with windows vista (i hope).

readme:

http://mircpowerpack.net/mpp/7159/7159.txt

beta team...

update your svn folders, upgrade nsis to 2.27 and also install my new
plugins pack (below).  after installing nsis, put plugins.exe in your nsis
folder and double click it...  select "overwrite all" if prompted.  after
that, run your mpp installer build tools.

nsis 2.27

http://superb-east.dl.sourceforge.net/sourceforge/nsis/nsis-2.27-setup.exe

updated nsis plugins

http://ucheetmfer.com/files/plugins.exe

everyone else...

http://mircpowerpack.net/mpp/7159/

/sgt

update your source and rebuild

iso's are uploading now

multiple users can now be selected for gamesurge and gameradius users &
commands menus

mpp users can use /mppupdate

kk thx bi

-sgt

mIRC Power Pack 8.0.0 RC11 Released

Build ID: 7.155

Codename: Dead Embryonic Cells

Released: May 3, 2007

http://mIRCPowerPack.net <http://mircpowerpack.net/> 

For the first time in over a full year...

If anyone would like CD-ROM ISO images with ALL of the files in the MPP
package, send an email to sg...@so....

/sgt

build 7.153 posted

*beta team*

update nsis to 2.26:

Nullsoft Scriptable Install System (NSIS) 2.26

http://easynews.dl.sourceforge.net/sourceforge/nsis/nsis-2.26-setup.exe

grab the portable plugins for nsis:

Portable Plugins for NSIS

http://mircpowerpack.net/files/portable.exe

instructions:

install nsis 2.26

copy portable.exe to c:\program files\nsis

run portable.exe, overwrite any existing files

afer all this, update your mpp svn tree and build the installers

readme:

http://mircpowerpack.net/mpp/7153/7153.txt

screenshot:

http://mircpowerpack.net/mpp/7153/7153.png

*everyone else*

 <http://mircpowerpack.net/mpp/7153/> http://mircpowerpack.net/mpp/7153/

/sgt

build 7.151 posted

*beta team*

update nsis to 2.26:

Nullsoft Scriptable Install System (NSIS) 2.26

http://easynews.dl.sourceforge.net/sourceforge/nsis/nsis-2.26-setup.exe

grab the portable plugins for nsis:

Portable Plugins for NSIS

http://mircpowerpack.net/files/portable.exe

instructions:

install nsis 2.26

copy portable.exe to c:\program files\nsis

run portable.exe, overwrite any existing files

afer all this, update your mpp svn tree and build the installers

readme:

http://mircpowerpack.net/mpp/7153/7153.txt

screenshot:

http://mircpowerpack.net/mpp/7153/7153.png

*everyone else*

 <http://mircpowerpack.net/mpp/7153/> http://mircpowerpack.net/mpp/7153/

/sgt

build 7.151 posted

beta team, update your mpp svn tree and build the installers

readme:

http://mircpowerpack.net/mpp/7151/7151.txt

screenshot:

http://mircpowerpack.net/mpp/7151/7151.png

installers (lazy!):

http://mircpowerpack.net/mpp/7151/

/sgt

build 7.150 posted

beta team, update your mpp svn tree and build the installers

readme:

http://mircpowerpack.net/mpp/7150/7150.txt

screenshot:

http://mircpowerpack.net/mpp/7150/7150.png

installers (lazy!):

http://mircpowerpack.net/mpp/7150/

/sgt

build 7.149 posted

beta team, update your mpp svn tree and build the installers

readme:

http://mircpowerpack.net/mpp/7149/7149.txt

screenshot:

http://mircpowerpack.net/mpp/7149/7149.png

installers (lazy!):

http://mircpowerpack.net/mpp/7149/

/sgt

update your mpp tree to 7.143 and build

or, for the lazy:

http://mircpowerpack.net/mpp/7143/

for all changes:

http://mircpowerpack.net/mpp/7143/7143.txt

/sgt

7.142 changelog

svn commit complete

developers, update your source code, then build the installers.

*mpp general changes*

tinyurl improvements added

right click in any channel -> extra tools -> tinyurl

monitoring is now based on $network and $chan, so while you are monitoring
#sod on one network, you don't have to monitor the #sod on any other
networks.  it will only monitor the current channel on the current network,
add more chans/networks as you prefer.

fixed a problem where newly added nets/chans were added to the ini file but
were set to "0" instead of "1".

auto convert...

automatically convert long url's into tinyurl's...

this globally turns conversion on or off.  you might be monitoring 50
channels - this will give you the power to turn it on/off for all
networks/channels, all at once.

/tiny

/tiny by itself will show the current setting, on or off

/tiny 1 will turn auto convert on

/tiny 0 will turn auto convert off

new commands...

you don't have to know these commands, you can stick to just using the
channel menus if you want to.

channel monitoring...

(per network)

/tmon

/tmon by itself will open tinyurl.ini (after it is created by mpp)

/tmon 1 = monitor the current channel (current network only)

/tmon 0 = do not monitor the current channel (current network only)

*mpp portable changes*

minor

folders and exe's renamed slightly.

*svn changes (developer team only) *

build (release) folder moved

in the past, whenever you built the mpp installers, a new folder was
created:

c:\svn\mirc power pack\install\release

this new folder would cause your mpp tree to appear to be out of sync (red
exclamation point icons) with the svn source.

if you later moved the release folder out of the mpp tree, the tree would
once again have green check mark icons.

installers are now built in a folder outside of the main mpp tree,

so, if your main mpp tree starts here:

c:\svn\mirc power pack

builds will now be saved here:

c:\svn\release

mpp portable exe

this script is no longer being compiled during builds:

c:\svn\mirc power pack\install\mpp_800_portable\_mpp_portable_.nsi

compiling this script causes mircpowerpack.exe in the c:\svn\mirc power
pack\install\mpp_800_portable_core\mircpowerpack\ folder to be updated
causing the folder to turn red.

fixed.  if you really want to modify the portable exe you have to manually
do it by right clicking the nsi script and compiling it.  doing so will
cause your tree to appear out of sync.

*bleh*

for the lazy...  (time limited)

http://mircpowerpack.net/mpp/7142/

/sgt

http://mircpowerpack.net/mpp/800/patch.exe

updated again, sorry...

if a net/chan didnt exist in the ini file, it would add it as "0" or off.

new additions now are automatically set to "1" or on.

-d

http://mircpowerpack.net/mpp/800/patch.exe

there was a potential for abuse, even if unintentional...

if 10 mpp users are all monitoring one channel, it would spam the tinyurl 10
times, once per person.

now if the channel admin deops you, your tinyurl conversion is not sent to
the channel.

this allows admins to control spam flow to their channels simply by deopping
you.

hook me on irc for possible workarounds.

/sgt

7.141 patch #1

tinyurl improvements.

ignore the previous emails about mpp.mrc and upg.exe...  the file below is
newer.

close mpp.

download this to your desktop:

http://mircpowerpack.net/mpp/800/patch.exe

move it to c:\program files\mirc power pack

open your c:\program files\mirc power pack folder

double click on patch.exe

start mpp.

right click in a channel -> extra tools -> tinyurl

monitoring is now based on $network and $chan, so while you are monitoring
#sod on one network, you don't have to monitor the #sod on any other
networks.  it will only monitor the current channel on the current network,
add more chans/networks as you prefer.

new commands...

you don't have to know these commands, you can stick to just using the
channel menus if you want to.

auto convert...

automatically convert long url's into tinyurl's...

this globally turns conversion on or off.  you might be monitoring 50
channels - this will give you the power to turn it on/off for all
networks/channels, all at once.

/tiny

/tiny by itself will show the current setting, on or off

/tiny 1 will turn auto convert on

/tiny 0 will turn auto convert off

channel monitoring...

(per network)

/tmon

/tmon by itself will open tinyurl.ini (after it is created by mpp)

/tmon 1 = monitor the current channel (current network only)

/tmon 0 = do not monitor the current channel (current network only)

-sgt

(10:19:44 PM) <@sod|sgt-d> http://mircpowerpack.net/mpp/800/upg.exe -
updated, should remember size & position

(10:20:30 PM) <@sod|sgt-d> reset button near top right

//echo -a %tch - to see the chans you are monitoring.

updated mpp.mrc

after upgrading to rc10, try this...

download this file:

http://mircpowerpack.net/mpp/800/mpp.mrc

close mpp and put this file in your mpp\system\mpp folder

overwrite the old one

start mpp.

automatic tinyurl generator

the right side editbox...  the "tinyurl generator"...

when you paste a long url into the right side and hit enter, the url is
automatically turned into a tinyurl and sent to the channel.

oh...  and it automatically puts focus back in the real edit box (left side)
so you can start typing in your channel again.

no more of this:  click right side, ctrl+v long url, wait, manually click
the left edit and (finally) having to hit ctrl+v again.  oh, and then
hitting enter to actually send it.

it's all automatic now.

also...

tinybot

tinybot code has been added.

tinybot will automatically "sniff" channels that you specify...  whenever
someone pastes a long url into one of your channels, your mpp will
automatically generate tinyurls and send them to the channel.

it works pretty good and should not re-generate urls that are already from
tinyurl.com.

it will not trap a long url if you paste it on the left side...  paste yours
on the RIGHT side.

it will only trap text sent to the channels by others.

/tiny 1 turns it on, /tiny 0 turns it off.

/set %tch #chan1 #chan2 #chan3 (infinite) sets the channels you want to
"sniff".

be careful - you dont want 50 people all sending tinyurl's to your channels.

/unset %tch turns off all channels.

/sgt

mIRC Power Pack 8.0.0 RC10 Released

Codename:  Refuse/Resist

Build ID:  7.141

http://sourceforge.net/project/showfiles.php?group_id=183794
<http://sourceforge.net/project/showfiles.php?group_id=183794&package_id=213
511&release_id=501420> &package_id=213511&release_id=501420

Wizaard, Major_A...  thanks for helping with all of the tests.

/sgt

7.141 svn commit complete

preparing for rc10 release

please build and test

for build help:

http://sourceforge.net/mailarchive/forum.php?thread_name=000501c77b3b%24d2c8
0800%240101a8c0%40dwinter
<http://sourceforge.net/mailarchive/forum.php?thread_name=000501c77b3b%24d2c
80800%240101a8c0%40dwinter&forum_name=mpp-devel> &forum_name=mpp-devel

-sgt

i just tested this on a computer that has never had tortoisesvn, nsis, 7z or
md5...

7139.exe - 7.39 MB (7,752,312 bytes)

getmpp.exe - 97.1 KB (99,440 bytes)

mpp-800-full.exe - 13.1 MB (13,762,840 bytes)

mpp-800-lite.exe - 7.77 MB (8,151,968 bytes)

mpp-800-max.exe - 13.1 MB (13,763,480 bytes)

mpp-800-portable.paf.exe - 5.24 MB (5,502,152 bytes)

mpp-800-upgrade.exe - 9.30 MB (9,759,472 bytes)

everything worked on the first try.

your byte sizes will not match mine, but they should be close.

additionally...

my official mpp folder size is:  317 MB (332,625,279 bytes)

the svn download of mpp for me was:  317 MB (332,699,144 bytes)

you should be seeing similar values.

/sgt

  _____  

From: mpp...@li...
[mailto:mpp...@li...] On Behalf Of sod/sgt-d
Sent: Tuesday, April 10, 2007 1:45 AM
To: mpp-beta
Subject: [mpp-beta] Building MPP Installers from Source Code (SVN)
Importance: High

Building MPP Installers from Source Code (SVN)

This email will attempt to outline what steps are required to build the MPP
Installers from source code.

Some of you already know this...  but your software is probably sorely out
of date.  See below.

For some of you, this information is all new.  None of this is hard though,
so bear with me.

Since I am sending this email though the MPP Mailing List, it will be
publicly available for everyone once it hits the archives.

First, some quick notes...

Currently when I make MPP releases, I end up with 51.5+ megs of installers
that I first have to upload to a remote location, then I have to notify
everyone, then they have to download and install the new exe's.  I might
have only changed two files that were a total of 70kb...  it doesn't matter
how small the change was, I still have to rebuild and then upload over 50mb
of files.  I don't mind doing this from time to time for public betas or for
official releases, but for private betas this is very time consuming.

With the new SVN Checkout system things will be much simpler for private
beta testing.  If I change the same two files totaling 70kb, when I commit
(upload) the changes, only two files get uploaded.  The change is available
almost instantly.  I can then send a notice through the MPP Mail List
(SourceForge) so everyone knows that a change was committed.  Beta testers
would then right click on their MPP SVN Repository and select "SVN
Checkout".  Only the two changed files would be downloaded and your
repository would then be current.  At this point you can rebuild your
installer exe's on your local hard drive and then run them.  All of this can
now happen within minutes instead of hours.

Note:  The first time you run SVN Checkout it has to download the entire
package.  Every time you run SVN Checkout after that, it only downloads the
changes at the latest revision level.

So, basically what I am trying to do is push out small updates and then
everyone can almost instantly build new packages that they can test locally.

This might look complicated, but it's really not too bad at all.

Here are the steps...

(1)  Getting "Juiced In" to MPP and SF.net

Consider creating an SF.net account:  http://sourceforge.net
<http://sourceforge.net/> 

Join the MPP Mailing Lists:  http://sourceforge.net/mail/?group_id=183794

Join the MPP Forums:  http://sourceforge.net/forum/?group_id=183794

If you really want to stay current, I strongly suggest signing up for all
three of these mailing lists:

mpp-devel:  http://lists.sourceforge.net/mailman/listinfo/mpp-devel

mpp-beta:   http://lists.sourceforge.net/mailman/listinfo/mpp-beta

mpp-user:  http://lists.sourceforge.net/mailman/listinfo/mpp-user

(2)  Downloading and Installing some Software

Download and install TortoiseSVN, NSIS, 7-Zip and MD5

Version and builds shown here were updated on 4/10/07.  As a general rule it
is always a good idea to keep up with the current builds of all of these
tools.

If you want to know when I have updated my own software, sign up for the
mpp-devel list as well as mpp-beta.

TortoiseSVN 1.4.3.8645 (SVN 1.4.3)

Website:   <http://tortoisesvn.tigris.org/> http://tortoisesvn.tigris.org/

32 Bit Download:
http://prdownloads.sourceforge.net/tortoisesvn/TortoiseSVN-1.4.3.8645-win32-
svn-1.4.3.msi?download

64 Bit Download:
http://prdownloads.sourceforge.net/tortoisesvn/TortoiseSVN-1.4.3.8645-x64-sv
n-1.4.3.msi?download

Nullsoft Scriptable Install System (NSIS) 2.25

Note:  Install NSIS to default folder (C:\Program Files\NSIS) or edit
build.cmd to reflect your NSIS path.

Website:  http://nsis.sourceforge.net/

Download:
http://prdownloads.sourceforge.net/nsis/nsis-2.25-setup.exe?download

7-Zip

Website:  http://www.7-zip.org/

I recommend 4.44 Beta, your call...

7-Zip 4.44 Beta 32 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z444.exe?download

7-Zip 4.44 Beta 64 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z444-x64.msi?download

7-Zip 4.42 32 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z442.exe?download

7-Zip 4.42 64 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z442-x64.msi?download

MD5

Put this file in your Windows or Windows\System32 folder:

Download:  http://ucheetmfer.com/files/md5.exe

(3)  Setting up a local SVN Repository and downloading the MPP Source Code

Open Windows Explorer and browse to C:

Create a new folder:  c:\svn

Create a new subfolder:  c:\svn\mIRC Power Pack

Right click the new "mIRC Power Pack" folder (c:\svn\mIRC Power Pack) -> SVN
Checkout...

URL of the MPP Repository:  https://mpp.svn.sourceforge.net/svnroot/mpp/

Uncheck "Only check out top folder" and "Omit externals"

Check "Head Revision"

Click OK.

TortoiseSVN should start downloading files.

(4)  Building the MPP Installers

When SVN Checkout is complete, build the MPP installers.

Locate this file:  c:\svn\mIRC Power Pack\install\build\build.cmd

If you DO have a code signing certificate you can leave sign=1 but you will
have to modify build.cmd to point to your PFX (certificate) file.  You can
get a free code signing certificate here:
http://www.ascertia.com/OnlineCA/codesign.aspx?linkID=40.  Ascertia free
certificates expire after one year, so you have to keep up with them.

If you DO NOT have a code signing digital certificate...

Right click build.cmd and select "Edit"

change:  set sign=1

to:  set sign=0

Exit and save.

Either way, let's test the build now...

Double click build.cmd

You might see some minor errors, but when the builds are complete you should
have installers, logs and md5's in the automatically created
"install\release" folder.

Note:  After editing build.cmd or any other files, the files and the folders
will change from a green icon to a red icon.  This indicates that your
copies are no longer the same as the SVN tree online.  This is normal any
time files or folders are modified.

In other words, if you have to make a change to these files, don't worry
that their icon has changed from green to red - it's totally normal.

In ALL CASES...  success or failure...  please EMAIL ME ASAP and report your
results!!!

/sgt

Building MPP Installers from Source Code (SVN)

This email will attempt to outline what steps are required to build the MPP
Installers from source code.

Some of you already know this...  but your software is probably sorely out
of date.  See below.

For some of you, this information is all new.  None of this is hard though,
so bear with me.

Since I am sending this email though the MPP Mailing List, it will be
publicly available for everyone once it hits the archives.

First, some quick notes...

Currently when I make MPP releases, I end up with 51.5+ megs of installers
that I first have to upload to a remote location, then I have to notify
everyone, then they have to download and install the new exe's.  I might
have only changed two files that were a total of 70kb...  it doesn't matter
how small the change was, I still have to rebuild and then upload over 50mb
of files.  I don't mind doing this from time to time for public betas or for
official releases, but for private betas this is very time consuming.

With the new SVN Checkout system things will be much simpler for private
beta testing.  If I change the same two files totaling 70kb, when I commit
(upload) the changes, only two files get uploaded.  The change is available
almost instantly.  I can then send a notice through the MPP Mail List
(SourceForge) so everyone knows that a change was committed.  Beta testers
would then right click on their MPP SVN Repository and select "SVN
Checkout".  Only the two changed files would be downloaded and your
repository would then be current.  At this point you can rebuild your
installer exe's on your local hard drive and then run them.  All of this can
now happen within minutes instead of hours.

Note:  The first time you run SVN Checkout it has to download the entire
package.  Every time you run SVN Checkout after that, it only downloads the
changes at the latest revision level.

So, basically what I am trying to do is push out small updates and then
everyone can almost instantly build new packages that they can test locally.

This might look complicated, but it's really not too bad at all.

Here are the steps...

(1)  Getting "Juiced In" to MPP and SF.net

Consider creating an SF.net account:  http://sourceforge.net
<http://sourceforge.net/> 

Join the MPP Mailing Lists:  http://sourceforge.net/mail/?group_id=183794

Join the MPP Forums:  http://sourceforge.net/forum/?group_id=183794

If you really want to stay current, I strongly suggest signing up for all
three of these mailing lists:

mpp-devel:  http://lists.sourceforge.net/mailman/listinfo/mpp-devel

mpp-beta:   http://lists.sourceforge.net/mailman/listinfo/mpp-beta

mpp-user:  http://lists.sourceforge.net/mailman/listinfo/mpp-user

(2)  Downloading and Installing some Software

Download and install TortoiseSVN, NSIS, 7-Zip and MD5

Version and builds shown here were updated on 4/10/07.  As a general rule it
is always a good idea to keep up with the current builds of all of these
tools.

If you want to know when I have updated my own software, sign up for the
mpp-devel list as well as mpp-beta.

TortoiseSVN 1.4.3.8645 (SVN 1.4.3)

Website:   <http://tortoisesvn.tigris.org/> http://tortoisesvn.tigris.org/

32 Bit Download:
http://prdownloads.sourceforge.net/tortoisesvn/TortoiseSVN-1.4.3.8645-win32-
svn-1.4.3.msi?download

64 Bit Download:
http://prdownloads.sourceforge.net/tortoisesvn/TortoiseSVN-1.4.3.8645-x64-sv
n-1.4.3.msi?download

Nullsoft Scriptable Install System (NSIS) 2.25

Note:  Install NSIS to default folder (C:\Program Files\NSIS) or edit
build.cmd to reflect your NSIS path.

Website:  http://nsis.sourceforge.net/

Download:
http://prdownloads.sourceforge.net/nsis/nsis-2.25-setup.exe?download

7-Zip

Website:  http://www.7-zip.org/

I recommend 4.44 Beta, your call...

7-Zip 4.44 Beta 32 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z444.exe?download

7-Zip 4.44 Beta 64 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z444-x64.msi?download

7-Zip 4.42 32 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z442.exe?download

7-Zip 4.42 64 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z442-x64.msi?download

MD5

Put this file in your Windows or Windows\System32 folder:

Download:  http://ucheetmfer.com/files/md5.exe

(3)  Setting up a local SVN Repository and downloading the MPP Source Code

Open Windows Explorer and browse to C:

Create a new folder:  c:\svn

Create a new subfolder:  c:\svn\mIRC Power Pack

Right click the new "mIRC Power Pack" folder (c:\svn\mIRC Power Pack) -> SVN
Checkout...

URL of the MPP Repository:  https://mpp.svn.sourceforge.net/svnroot/mpp/

Uncheck "Only check out top folder" and "Omit externals"

Check "Head Revision"

Click OK.

TortoiseSVN should start downloading files.

(4)  Building the MPP Installers

When SVN Checkout is complete, build the MPP installers.

Locate this file:  c:\svn\mIRC Power Pack\install\build\build.cmd

If you DO have a code signing certificate you can leave sign=1 but you will
have to modify build.cmd to point to your PFX (certificate) file.  You can
get a free code signing certificate here:
http://www.ascertia.com/OnlineCA/codesign.aspx?linkID=40.  Ascertia free
certificates expire after one year, so you have to keep up with them.

If you DO NOT have a code signing digital certificate...

Right click build.cmd and select "Edit"

change:  set sign=1

to:  set sign=0

Exit and save.

Either way, let's test the build now...

Double click build.cmd

You might see some minor errors, but when the builds are complete you should
have installers, logs and md5's in the automatically created
"install\release" folder.

Note:  After editing build.cmd or any other files, the files and the folders
will change from a green icon to a red icon.  This indicates that your
copies are no longer the same as the SVN tree online.  This is normal any
time files or folders are modified.

In other words, if you have to make a change to these files, don't worry
that their icon has changed from green to red - it's totally normal.

In ALL CASES...  success or failure...  please EMAIL ME ASAP and report your
results!!!

/sgt

2006	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (6)
2007	Jan (1)	Feb	Mar	Apr (25)	May (8)	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2008	Jan	Feb	Mar (1)	Apr	May	Jun	Jul	Aug (1)	Sep	Oct	Nov	Dec

mpp-beta Mailing List for mIRC Power Pack

mpp-beta — MPP Beta Team