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 - David McKenna

Pages: 1 2 [3] 4 5 ... 9
31
Hardware / Re: Benchmarks on real vs virtualised hardware
« on: 2011.04.13, 22:55:51 »

@ David McKenna:
I did try the same as you suggested, does have a USB Ubuntu stick running with OS/2 Warp 4 inside Virtualbox 4.04. However I did not configure it to "autostart". These links here might be interesting for you:

http://forums.virtualbox.org/viewtopic.php?t=12426&postdays=0&postorder=asc&start=15
(How to autostart a VM with Virtualbox)

http://www.pendrivelinux.com/yumi-multiboot-usb-creator/
(How to boot Multi OS with a small Linux)

Hope this is of some help.

Cheers

Sigurd

  Thanks for those links! I'll give this some consideration over the weekend...

Regards,

Dave McKenna

32
Hardware / Re: Benchmarks on real vs virtualised hardware
« on: 2011.04.13, 01:50:06 »
Hi Paul,

  Those results are fantastic! I have often wondered if it would be possible to set up an absolutely minimalist Linux (I haven't found a distribution I really liked) that all it does is run VirtualBox and somehow you could have it boot to a VirtualBox menu where you then choose your OS... sort of like a Boot Manager or AirBoot ... and then run whatever OS's you like virtually. A 'VirtualOS' or BootOS' so to speak. Your results show it could be a viable solution.

  As you know, I too got a new motherboard and processor and am less than thrilled with how eCS runs on it, although it seems certain the issues will be taken care of eventually. I think I will spend some time looking at Linux again...

  Hope everything works out with your knee.

Regards,

Dave McKenna

33
Hardware / Re: Getting 1.2 to boot on 64 bit
« on: 2011.03.30, 02:19:00 »
OriAl,

  An alternative to Pete's suggestion is boot to a command line (via the <alt>F1 menu) and type: HCIMONIT

  You will get a message saying exactly what and how many USB controllers are detected. Then you can manually change CONFIG.SYS using TEDIT.

Regards,

Dave McKenna

34
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.03.08, 14:19:53 »
Hi Remy,

  Yes... the new one you sent now works correctly. Thanks for your great work!

Regards,

Dave McKenna

35
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.03.08, 02:13:18 »
Hi Remy,

  I got your new build - thanks! - but it still does the same thing.

  There is no C: anymore - even ClamAVGUI does not put a C: in its *.conf files. I believe this is the way it should be for the RPM version of ClamAV.

  What is strange is even ClamAVGUI created freshclam.conf files will be re-written the first time after starting ClamAVGUI and saving ClamAVGUI settings. Every time after that if I click 'save' in ClamAV GUI settings, no new freshclam.conf file is created.

  Here is a step-by-step example:

1. Start ClamAVGUI
2. Go to 'Settings' -> ClamAV GUI
3. Click 'Save'. The console says a new freshclam.conf is created and the old one is saved with a new suffix.
4. Go to 'Settings' -> ClamAV GUI
5. Click 'Save'. The console says nothing and no new files are created.
6. You can repeat 4 & 5 and always nothing.
7. Close ClamAVGUI
8. Restart ClamAVGUI
9. Go to 'Settings' -> ClamAV GUI
10. Click 'Save' The console says a new freshclam.conf file is created and the old one saved with a new suffix.
11. Go to 'Settings -> ClamAV GUI
12 Click 'Save' The console says nothing and no new file is created.
...etc...

  Is there something different about the way ClamAVGUI determines whether the freshclam.conf file has been changed the first time it looks compared to later times?

Regards,

Dave McKenna

36
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.03.08, 00:11:38 »
Hi Remy,

  I got your latest update (2.1.3f). It seems that now clamd.conf and freshclam.conf files created by ClamAVGUI leave off the leading C: (good!) on paths with RPM checked. But still I get a new freshclam.conf file written the first time I save ClamAVGUI settings after starting ClamAVGUI. It is strange it is only the first time...

Regards,

Dave McKenna

37
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.03.06, 22:39:46 »
Hi Remy,

  Freshclam.conf (and clamd.conf) does have the DatabaseDirectory entry as:

DatabaseDirectory /var/lib/clamav

  There is no leading C: - presumably it gets that from the UNIXROOT= value. This is how ClamAV (the RPM version) creates clamd.conf and freshclam.conf. I now notice when ClamAVGUI writes freshclam.conf it adds the leading C: to this line. Maybe this is where the trouble is?

Regards,

Dave McKenna

38
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.03.06, 20:28:29 »
Hi Remy,

  I received your updated INI and EXE files and applied them.

  Now it seems I always get /etc/clamd.conf and /etc/freshclam.conf when I go to 'Clamdscan (conf)' or 'Freshclam (conf)' - even after I hit 'save' in ClamAV GUI settings. Thanks!

  One thing still seems not right...  every time I hit 'save' in ClamAV GUI settings - even if I do not make any changes - a new freshclam.conf is written the first time I run ClamAVGUI settings. Now with this new version it is written in /etc and overwrites my original ClamAV freshclam.conf (and creates a backup). Is this what you intend? It seems to me that a new one should only be written if a change that effects freshclam.conf is made.

  With respect to the RPM checkbox - yes, now that you mention it it makes sense to set that first. Maybe you could somehow check when the startup object (or line in CONFIG.SYS) is created that the file the object is set to use actually exists and if not, give a warning message? Just a thought...

  Thanks for your continued development.

Regards,

Dave McKenna

39
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.03.06, 18:13:40 »
Hi Remy,

  I sent the ClamAVGUI.ini file today - I hope you got it.

  I am using version 2.1.2e.

  I tried deleting ClamAVGUI.ini and restarted ClamAVGUI, then went to Settings -> ClamAV GUI and set up everything and saved, but still have the same issues I reported.

  Then, I deleted ClamAVGUI using WarpIn and deleted the remaining ClamAVGUI folders and Clamd object in my startup folder and re-installed ClamAVGUI. During install I was warned that 2 freshclam.conf files exist and to choose 'Yes' if I want to use the ClamAVGUI one. I chose 'No' in order to use the ClamAV one. Same with clamd.conf. Then I was asked about adding clamav.dll to a path and I chose to leave as-is.

  Next, I started ClamAVGUI and went File -> Start Clam Daemon. I was asked how I want to start clamd and I chose put object in startup folder. An object was put into the startup folder called 'Clamd using ClamAVGUI-config'. An error appeared in the ClamAVGUI console saying 'Clam daemon failed (used parms --config-file=C:/etc/clamd.conf RPM installed =0). Looking at the 'Path and File Name' settings of the object in the startup folder, I see it is set to: C:\BIN\CLAMD.EXE. It should be C:\USR\SBIN\CLAMD.EXE. The 'Working Directory' is wrong too.I change them to C:\USR\BIN, then restart Clamd.

  Now I go to 'Settings -> ClamAV GUI'. I click the 'RPM' check box. The paths to ClamAVScan and ClamAV Updater are both set to C:\BIN\xxx.exe. They should be C:\USR\BIN\xxx.exe I change them and the indicators turn green. I hit 'Save' and a message warns that the ClamAV DB path is not correct ( \var\lib\clamav even though the indicator is green) and it changes to C:\var\lib\clamav. I hit 'OK" and then 'Save'.

  Choose Settings -> Clamdscan (conf) and the file C:\Programs\ClamAVGUI\clamd.conf opens. Choose Settings -> Freshclam (conf) and the file C:\Programs\ClamAVGUI\freshclam.conf opens. Now close ClamAVGUI and restart, choose Settings -> Clamdscan (conf) and the file C:\etc\clamd.conf opens. Go to Settings -> ClamAV GUI and hit 'Save'. A new Freshclam.conf is written. Go to Settings -> Clamdscan (conf) and the file C:\Programs\ClamAVGUI.conf opens. Clamd is using C:\etc\clamd.conf as far as I can tell. It seems as long as I do not hit 'Save' in ClamAV GUI settings, the correct *.conf files are displayed.

HTH,

Dave McKenna

40
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.03.05, 20:03:10 »
Hi Remy,

  I tried the latest (2.1.2) ClamAVGUI and I still see this issue:


 Start ClamAVGUI, go to 'Settings' -> 'Clamdscan(conf)' and /etc/clamd.conf opens. Go to 'Settings' -> 'Freshclam(conf)' and /etc/freshclam.conf opens. This is correct for my setup.

 Now go to 'Settings' -> 'ClamAV GUI' and hit 'Save' (you can make a change or not). Go back to either 'Clamdscan(conf)' or 'Freshclam(conf)' and now it opens C:\Programs\ClamAVGUI\xxx.conf. This is not correct.

  Also I still get a new freshclam.conf file and copied backup the first time I hit save in ClamAV GUI settings.



 other than that everything seems to work well.

Regards,

Dave McKenna

41
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.03.01, 00:23:12 »
Hi Remy,

  I tried this test version 2.1.2 and I still see the following issue:

 Start ClamAVGUI, go to 'Settings' -> 'Clamdscan(conf)' and /etc/clamd.conf opens. Go to 'Settings' -> 'Freshclam(conf)' and /etc/freshclam.conf opens. This is correct for my setup.

 Now go to 'Settings' -> 'ClamAV GUI' and hit 'Save' (you can make a change or not). Go back to either 'Clamdscan(conf)' or 'Freshclam(conf)' and now it opens C:\Programs\ClamAVGUI\xxx.conf. This is not correct.

  Also I still get a new freshclam.conf file and copied backup the first time I hit save in ClamAV GUI settings.

  I tried the drag and drop and it seemed to work well... very nice!

Regards,

Dave McKenna

42
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.02.27, 18:22:22 »
Hi Remy,

  I tried your test version 2.1.2 and it seems to work as you describe. It would be nice if when using Clamdscan(conf) the software could automatically detect which conf file is in use and just open that one... don't know if that is possible. In any case having the choice is good.

  One minor thing I just noticed. After starting ClamAVGUI, when going to ClamAVGUI settings then hitting 'save' a new freshclam_GUI.conf file is created in the ClamAVGUI directory (not /etc) and the original one saved even if there are no changes. It only happens the first time after starting ClamAVGUI. Due to all my testing I had about 60 saved freshclam_GUI.conf files in my ClamAVGUI directory. I am not sure this is what you intend.

  FYI - I start ClamD from an object in the startup folder and that seems to work well with Clamdscan.

Regards,

Dave McKenna

43
Article Discussions / Re: ClamAV GUI version 2.1.0
« on: 2011.02.26, 16:22:48 »
Hi Remy,

  OK, thanks - I'll try starting Clamd either from the startup folder or startup.cmd. RPM puts clamd.conf (and freshclam.conf) in /etc .

Regards,

Dave McKenna

44
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.25, 19:42:40 »
Remy,

  I finally got a chance to play around with starting Clamd from CONFIG.SYS. When I use 'Start ClamDaemon' and allow it to insert a line in my CONFIG.SYS, the next boot hangs at MPTSTART. If I move that line to the end of all 'RUN=...' lines in CONFIG.SYS, then booting completes.

  Then when I start ClamAVGUI, it shows that 'ClamD is Running', but if I try to perform a scan (using Clamdscan) I get buzzing and a message: ERROR: Can't connect to clamd: Can't assign requested address.

 One strange thing at this point is if I choose 'Clamdscan (conf)' it displays the file /etc/clamd.conf NOT C:\Programs\ClamAVGUI\clamd_GUI.conf (as directed by the clamd parameter '--config-file=...' added by ClamAVGUI in CONFIG.SYS). Going in to ClamAVGUI settings and saving, then using Clamdscan (conf) again displays C:\Programs\ClamAVGUI\clamd_GUI.conf. This is confusing - which file is clamd really using?

  If clamd is not started from CONFIG.SYS, but manually started from ClamAVGUI using 'Start ClamDaemon', then I can perform scans using clamdscan with no trouble. It's not clear to me what may be wrong...

Regards,

Dave McKenna

45
Article Discussions / Re: ClamAV GUI version 2.0.0
« on: 2011.02.22, 02:54:58 »
Doug,

  Thanks for the heads-up about IAI (yes... I was using that). Fixed my entries as you suggest and still ClamAVGUI 'write to GUI Author' works fine. Maybe because I only have one account...

  I am intrigued by your suggestions for using ClamAV with PMMail and plan on giving them a try. Maybe they are something that can be added to a future version of PMMail...

Regards,

Dave McKenna

Pages: 1 2 [3] 4 5 ... 9