Casio256

I can confirm that this is an issue for DOS printing. We had a client that rang us a number of weeks ago about an issue that was spreading on their mini network. PC's that had been working fine with the application on Windows 7 32bit PCs had suddenly started to 'stall' while the DOS application was printing. All other functions of the application were fine. We asked the client what changed and they said nothing had changed. We then started to uninstall applications, printers, drivers, tried setting different printers, uninstalling windows updates, downloading new windows updates, disabling the ESET by 'pausing protection' etc etc Eventually in desperation, we uninstalled ESET and found the application returned to normal and worked fine. The client had upgraded the ESET package to Version 9 and didn't regard this as a change but as a normal task that there thought they were supposed to do. It is differently the new version 9 that is causing these issues. We have reverted to the older version for the moment until this issue is resolved.

Hi We have just experienced the exact same issue, a legacy DOS accounts application that has been running fine for years suddenly started to stall the PC until the application finished printing. Each time the users print from the package there would be a 2-3 minute delay and the PC would 'lockup'. Once the job has printed the PC would continue fine until the next print job. We spent several days trying to find what had changed and never thought that ESET was the culprit as it's always been stable and well behaved. Unknown to us the end users had upgraded the ESET to the new Version 9. We eventually started to uninstall printers / applications, rebooting each time until after uninstalling ESET V9 it worked fine. We then replaced all the printers / applications that we had removed and it's still working fine. So it is defiantly the ESET that is at issue. We did try 'pause protection' and also making the application folder as an 'exception' but it made no difference. The only solution that worked was a complete uninstall. We then found this post after we did the above and just wanted to confirm that this is an issue for anyone using DOS applications with ESET v9.