firstly, can you opt to encrypt existing chat log files, or is it only after you select to encrypt files that only thereafter new logs are produced that are then encrypted accordingly?

secondly, can you opt to remove an encryption from a log file once it has been encrypted, ie, so you dont have to type in the password any longer? (ie getting that padlock icon off the log files)

thanks,
malf

Only new logs created will be encrypted after you set encryption.

You can encrypt existing logs (and more) from the commandline with the logviewer application:


Results of run > "C:\Program Files\Messenger Plus! Live\Log Viewer.exe" /?

Note: strings which contain spaces need to be inside quotes. eg:
"C:\Program Files\Messenger Plus! Live\Log Viewer.exe" /encrypt="c:\my logs\contact1@hotmail.com.txt" /pwd="my password"

In this post you can find a bat file created by CookieRevised that decrypts all log files in a folder and its subfolders when run from inside that folder.

Edit: you're welcome
Edit2: to make things even more clear i added the full command to encrypt a log. Note: the full path/name to the to encrypt log needs to be specified (just like the full path needs to be entered to the event viewer app). If you use the parameter /overwrite an encrypted logfile with same name (with .ple extension) in same folder will be created, but when a file with that name already exist that one will be overwritten.
("C:\Program Files\Messenger Plus! Live\Log Viewer.exe" /encrypt="c:\my logs\contact1@hotmail.com.txt" /pwd="my password" /overwrite).

my God that was a fast reply! thank you! if i have any Qs after tryin the above il addend them!

I've modified the BATCH file u mentioned backwards so now u can encrypt all the non-encrypted files. that would help on older conversations and save time on modifiyng file per file

Moderator Edit: Attachment deleted; please read the following posts for more information

Well, after running your encrypt script on my (irritatingly large) archive of logs, I now can't open them again.

Any chance of an error in the script? I'm going to have a read through it but I must admit my batch script knowledge is limited.

EDIT:

Phew! Must admit you scared me there... Thankfully a very simple (and odd) issue - you hard-coded a password in there, rather than using the one entered on the command-line :

code:

---

ECHO "%LOGVIEWER%" /encrypt="%%I" /pwd="zheykster" >> TEMP.BAT

---

Both batch files from Zheyk and cbuckley contain bugs.

I also would have appreciated it if I was contacted before the original batch file I wrote is being messed up like that, Zheyk...

For a proper working EncryptAll (and DecryptAll), see
CookieRevised's reply to About uncrypting logs (i've got password!)

Apologies, my fault for not reading either the post or the comments, I just noticed the major bug and provided a fix. I had contacted Zheyk when I assumed it was his software...