Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - CDRWSel

Pages: 1 ... 7 8 [9] 10 11 ... 28
121
Article Discussions / ClamAV GUI version 2.1.0
« on: 2011.02.26, 12:02:28 »
http://www.os2world.com/content/view/20595/2/
Quote
Posted by Martin Iturbide - Tuesday, 22 February 2011


[a href. .. .

One more time, I'm unable to add any updates into ClamAV GUI version 2.0.0 forum entry (blank page !)

Hi Dave,

It looks like starting ClamD from config.sys makes it ignore the  "LocalSocket" which could not be initialized.
This makes Clamdscan not been able to communicate with it.
* For system protection, starting Clamd from config.sys is ok
* To use Clamdscan with Clamd, the LocalSocket must be enabled and this requires to start Clamd out of config.sys

If Clamd is added into config.sys, prefer use Clamscan or stop/re-start Clamd before use of Clamdscan
You can do like this (with rxu.dll into dll path):
- Show PIDs
- Kill Clamd process
- Verify Daemons
- Start ClamDaemon

Or, you can update startup.cmd to start clamd after eCS full initialization
I'll update docs with these restrictions.

About the clamd.conf problem you reported, I'm correcting it.
Could you please tell under which path you have clamd.conf available when installed through RPM/YUM ?
Thanks

Kind regards,
Remy

122
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.25, 22:36:14 »
Hi Dave,

"One strange thing at this point is if I choose 'Clamdscan (conf)' it displays the file /etc/clamd.conf"
Hum ! This may be a bug in my code when ClamAV is RPM/YUM installed. I'll check this.

About "Can't connect to clamd: ..." it looks like the parameters in config.sys are ignored. I will check what happens here... 

123
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.23, 01:15:52 »
How to add "ClamAV scan..." under Folder menu ?    
Open:
"Local system" folder
      - Open "System Setup" folder
             - Open "Extented Menu Option" folder
               1/ Create a new program
               2/ Give the name as you want have it display under Folder Menu
               3/ Specify ClamAVGUI.exe full path as program path
               4/ Add default parms like it is under original program folder.
Save and close all
Now do a try

To edit contain of an open/inuse logfile:
Create a temporary file through:
TYPE logfile > tempfile
Edit tempfile

Kind regards,
Remy

124
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.22, 20:28:19 »
Hi Doug,

I understand you position and I agree with most of them.
RPM/YUM (I hate) but I had to do with those using it.

By default, there is no entries under WPS to call ClamDscan under WPS options.
This means you wrote a program to update WPS entries and add ClamDscan as option

Of course, you can drag/drop a file or a folder on ClamAV-GUI and it works with the advantage to have the a log file, use of your usual conf file etc... 
Only when you drag/drop more than one file, it opens one ClamAV instance and because it is the same time, there is a shared log access issue. This can be improved next....

Have a nice evening
Cheers
Remy
   
 

125
I think having found what happens and this is a Firefox V4 bug whish has to be corrected.

The VDM\proxy browser thread start as soon to "clear recent history"
I have set:
Browsing & download history
Form & search history
Cookies
Cache
Offline web site data

Because I have it set to clear recent history at close time, it always start thez VMD...  (bug!)
I think you can do it a try and you'll get it too.

Cheers
Remy   

126
Strange !

I can do any try to use it and each time a close Firefox v4, Firefow closes but I "VDM proxy browser" thread using about 25% of my CPU is running then and it didn't end.
I have to kill this thread from under TOP.

Could you check under TOP if some thread remain after close of firefox v4 ?
Thanks

Remy

127
Try following script (generated by AVxCAT with less modifications)

Change ff_inputfile
And ff_outputfile
don't try to use higher video size... (it will no work)
the -async is for video/audio syncro (suggested but not required)
The mapping is planned for video + audio stream
If you don't know, just set it to "", ffmpeg will use defaults
change ffmpeg path to your ffmpeg path

/* */
ff_inputfile="C:\MMOS2\MOVIES\ecs.mpg"
ff_inputfile='"'||ff_inputfile ||'"'
ff_outfile="C:\home\default\.avxcat\ecs.mpg"
Out_AVmap=" -map 0.0 -map 0.1"
more_map=""
ff_outfile='"'||ff_outfile||'"'
ffmpeg_prms=' -i '||ff_inputfile||''||Out_AVmap||' -s 480x360 -vcodec mpeg1video -b 1000k -r 25.00 -async 3'
ffmpeg_prms=ffmpeg_prms||' -ar 44100 -acodec mp2 -ab 160k -vol 256 -ac 2'
ffmpeg_prms=ffmpeg_prms||' '||ff_outfile||' '||more_map
'C:\PROGRAMS\FFMPEGCA\FFMPEG-R25157\ffmpeg.exe -y '||ffmpeg_prms
Exit

Advices:
ffmpeg doesn't support 5.1 audio stream (be carefull with WMV)
OS/2 mpg file has mp2 audio stream in it and this has to be specified to have a compatible
video file. The OS/2 and eCs default player are same and it should work under OS/2 as well under eCS.

You can do a try adding -f mpeg1video but this should make the video not work !

Cheers
Remy

128
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.22, 10:17:48 »

Quote
ClamAV-GUI doesn't need unixroot an I may suggest you give it a try :-D

I have tried it, and I don't like the way you do it (just my own preference, there is really nothing wrong with what you do), although SAMBA quit working after I installed ClamAVGUI, so I uninstalled it (Samba is more important).


Humm !
You didn't understand how UNIXROOT is used when installed via the "not official" ClamAV WPI build I did and how it is used with ClamAV-GUI
(You may see that what you have no reason to do it like you do)  

Let me tell you how the UNIXROOT is used when WPI installed.
The only required path using UNIXROOT is for the ClamAV database (This isn't the case when using RPM/YUM)

Why don't you add required ClamAV database under your existing UNIXROOT path ?
Realy, there is no need to create a batch programs to set environment variable and run ClamAV from it!        

Under a second system, I have ClamAV installed under  C:\programs\ClamAV
and "SET UNIXROOT=E:"     << see, it is not ClamAV installation path

How to do ?
Add under UNIXROOT used by SAMBA following directories
SAMBA_UNIXROOT\var\lib\clamav
That's all for "unixroot" and nothing to install  

Now, under ClamAV-GUI, set manually the database path to this created path and save despite the red led is on.  Run database update and it will updated config file and load database files into the right directory.  That's all and very easy to do (no batch or extra process to use and your SAMBA as well as ClamAV will work)

This is much easier to do as your suggestion  ;)

Futur ClamAV have more products dependencies and my latest tested WPI always fail depite adding more required dlls - internal error - It seems requiring RPM/YUM process :(
This may suppose you to review all your installation !

ClamAV is compatible with ClamAV WPI or RPM/YUM packaged  


Hi Dave,
Just create lists for you PMMail and you can scan it at request but if you start ClamD, no need to scan you PMMail path, mails are checked by ClamAV daemon     

Best regards,
Remy

129
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.22, 09:58:24 »
Quote
One more issue resolved.

Perhaps not. It looks, to me, that David has his INI entries for PMMail messed up, somehow. They certainly are not right. These are the ones that should be there:

[HINI_USER_PROFILE\PMMail/2]
InstallRoot="W:\APPS\PMMail\BIN"
(path should, of course, match reality)

[HINI_USER_PROFILE\WPURLDEFAULTSETTINGS]
DefaultMailExe="W:\APPS\PMMail\BIN\pmmail.exe"
DefaultMailWorkingDir="W:\APPS\PMMail\Accounts"
DefaultMailParameters="-cwd W:\APPS\PMMail\Accounts -s DOUGB00.ACT"
(again, the paths need to match reality).

I'm sure he has InstallRoot correct or it will not start
About other entries,  only
DefaultMailParameters="-cwd W:\APPS\PMMail\Accounts -s DOUGB00.ACT"
Wasn't correctly set but no need to have the account name appended to the parms.
(See PMMail doc)
Having  DefaultMailParameters="-cwd C:\programs\PMMail\Accounts" is enought and correct
Only in case of migration and with more accounts, adding the account name is helpfull here

But no matter about how his ini entries are. I do several check and able to start PMMail if default ini entries are set or not and if DefaultMailParameters are bad, I'm able to try new default parms....
What is making you tell "Parhaps NO" about my ClamAV-GUI resolved PMMail issue when starting it ?
Did you analyze my code ?  
  

130
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.22, 00:15:08 »
Fine,

One more issue resolved.

Kind regards,
Remy

131
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.21, 20:53:24 »
Hi Dave,

Please replace the exe file with this new one and tell how it works.
http://remydodin.levillage.org/outils/ClamAVGUI.ziq    (rename ziq ti zip)

Thanks

Kind regards,
Remy

132
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.21, 15:19:19 »
Hi Dave,

Ok
 
DefaultMailParameters seems strange because "-compose" is thunderbird parm.
It  looks for me more interesting to have
DefaultMailParameters  -cwd  C:\programs\PMMail\Accounts

then, I didn't expect to see
DefaultMailWorkingDir   C:\programs\PMMail\Accounts      << this is account path !
I wrote the program in hope to find
DefaultMailWorkingDir   C:\programs\PMMail\bin               << same as suggested by Jep 

Now I know why it fail. I have to review my code to be able to manage parms like you have.
Until I did changes, could you do a try changing to:

DefaultMailParameters    -cwd  "C:\programs\PMMail\Accounts"   
(I set this when defaultmailexe is not Pmmail and you set "use it as default")

and
DefaultMailWorkingDir   C:\programs\PMMail\bin

don't forget to add the trailing blanks    '00'x   

133
http://www.os2world.com/content/view/20568/2/
Quote
Posted by Martin Iturbide - Tuesday, 15 February 2011


Rich Wa. .. .

At close time,
I always have a "VDM.... browser" thread running and using high CPU until I kill it !
How to have a real close at close time ?

(After I kill this thread, I'm getting a popup message with strange characters in it)
Thanks
Remy 

134
Article Discussions / bout
« on: 2011.02.20, 23:43:55 »
ClamAV-GUI doesn't need unixroot an I may suggest you give it a try :-D
It is checking for it when ClamAV was installed through RPM/YUM which requires UNIXROOT being set into config.sys and when using latest ClamAV 0.96.4.x (@UNIXROOT should be set at root level). This is main RPM/YUM requirement

About PMMail install path, it is like I wrote due I installed latest PMMail WPI package and I checked all ini setting after a well installation.
PMMail is installed under  boot_drive\...\PMMail\bin
the account are under boot_drive\...\PMMail\Account
This is conform to what Jep wrote too.

The reported question was not about how to scan PMMail message but about how to write to me using the
clamav-gui "write to author" option with PMMail. 

kind regards
Remy

135
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.20, 21:21:22 »
Hi Dave,

I did my test using latest PMMail program.
The program path should have a \bin in its name. Right ?
It looks like something isn't set as expected under your environement.

I just added a check about the path but something may be wrong under you os2 ini setting for pmmail.
I would like know what you have into your os2 ini file about default mail program and Pmmail ?
(of course, you can get the file again from my web link)

e.g.
PMMail/2      InstallRoot     c:\programs\PMMAil\bin

And
WPURLDEFAULTSETTINGS    DefaultMailExe    c:\programs\PMMail\bin\pmmail.exe
                                                          DefaultMailParameters   ........
                                                          DefaulMailWorkingDir    c:\programs\PMMail\bin

Thanks
Remy

Pages: 1 ... 7 8 [9] 10 11 ... 28