bug setting packers

[Lisandro]

What's up!!!!    

I cannot even schedule a task?!  :'(

Vlk, the same error again...  
I just boot, open Enhanced Interface, go to Scheduler and try to delete an event... The error freeze the system, then with TaskManager I need to close all avast! applications and restart the computer...

I did again, to delete another event. The same happened!  

[sowen]

Yes, I get the error ALL the time. I don't even both going to the 'scheduler' folder any more, and just schedule tasks from the 'tasks' folder, because otherwise the Enhanced interface gets a Runtime error and/or a memory fault. :'(

[Lisandro]

Yes, I get the error ALL the time. I don't even both going to the 'scheduler' folder any more, and just schedule tasks from the 'tasks' folder, because otherwise the Enhanced interface gets a Runtime error and/or a memory fault. :'(

Definetively, there is a bug  

[sowen]

Vlk, Roman,

Here's an update on the Runtime error and memory fault, which I get when in the Scheduler folder of the Enhanced interface:

When I am working locally on the computer, I get the error as described in this message

However - and this may help locate the bug - I cannot reproduce this error when connected to the computer using the WinXP Remote Desktop client.

Again, when I get the error, the following message appears in the event log:
       ODBC function SQLAllocHandle() - dbsObjectsQuery() failed. Error description: .

Hope this helps!

[Roman Svihalek]

Currently I am able to simulate reported bug, I will try to fix it ASAP. I saw it for the first when I have tried to delete scheduled event...

Thanks again, sowen

[Roman Svihalek]

Fix to overwriting settings of provider packers is available at http://cat.asw.cz/~svihalek/fix.zip

Bug invoking "Runtime error" message box is not fixed yet  

[Roman Svihalek]

good news: runtime error is probably fixed. Can I ask you to test it?

fixed file named ashSODBC.dll has been added to fix.zip from previous post, so it is available for download to everyone interested :-)

thanks to all...

[Lisandro]

good news: runtime error is probably fixed. Can I ask you to test it?

fixed file named ashSODBC.dll has been added to fix.zip from previous post, so it is available for download to everyone interested :-)

thanks to all...

Roman, I forget to uncheck the automatic update of program... avast! was updated to 4.1.319 and I think the files 'went' back to their original state  

I'll install the files again and turn off the update (basic) settings. When will be  the next program update (major update)?

[Lisandro]

Ooopss. I change the settings to 'ask when available' for updates. Stop all proccesses of avast. Copy the 'new files'. Boot. When avast! starts, I checked the settings: everything ok ('ask when available'). Connect to Internet. ...   The update of 4.1.319 overwrite again the copied files and even ask me?

Why does the option 'ask when available' exist?  

I won't try again. I'll wait for the next major update.

[sowen]

Hi Roman,

Technical is right, Avast keeps writing over these files even when 'Ask' or 'Manual' is selected for the program updates. Apparently (I'm just verifying this now), even an iAVS update is causing .dll's to be replaced!).

Ok, so I set both iAVS and program updates to 'manual', replaced the files, and did the testing.

• bug setting packers for default task: resolved
• bug where a disabled scheduled task runs anyway: resolved
• runtime error when editing schedules in the scheduler folder of the Enhanced interface: resolved
  (there's still a bug in the sort-order of the sheduler folder, but I assume that's in ashEnhcd.exe.) By the way, did you see my bug-reports regarding ashCmd.exe?

Thanks for the good work!
Sincerely,
Scott.



 

[sowen]

Roman, I just confirmed it:

Even if I have program updates set to 'Ask' or 'Manual', and 'running mode' is set to either 'Normal' or 'Silent', when an iAVS update is done (either automatically or manually), the DLLs and default.xms files are all replaced with their original versions. Only in one case -- presumably when one of the DLLs was in use -- did it ask if I wanted to reboot.

Is it a bug or a feature?  

Scott.

[Vlk]

It's feature. I admit, sometimes it's a nuisance (e.g in this particular case, when trying out unofficial patches) but generally it pays off. Unfortunately there's probably no way to turn it off...

We call it the 'auto-correct' feature. There has been a discussion about it couple of times on this forum already...

[sowen]

Sorry, third posting in a row here...
I've been having a strange problem with my LDAP-server recently, which uses ODBC and an Access database for my addresses. Lo-and-behold, when I install your new ashSODBC.dll, my LDAP works fine again!

So please release at least the new ashSODBC.dll as soon as possible!

Thanks,
Scott.

[Vlk]

A program update is (unofficially) scheduled to take place at the end of next week...

[sowen]

Actually, the 'auto-correct' is a very nice feature indeed, and it shouldn't be 'disablable'. Just tell me about these features if you want me to test for you!