Thanks @JeffBH for the suggestion. I was about to give this a whirl when I received a notification that ProScan has released update 17.8.0. I downloaded and installed this version in the usual manner. ProScan V17.8.0 appears to be functioning in all respects now, in my installation. Thanks everyone!I had this also. Temp fix is open Comm port, change to "None", hit SET, change back to URL, hit SET.
Neither 17.7.0 or 17.8.0 worked for me. Exact issue as described by
johnbednarski. I've reverted to 17.6, it's working fine.
Is this the issue? It was fixed in 17.8 and the OP noted it. So I'm not sure if you are referring to this or something else. The absolute best way to resolve any issues is by email. When I get bug reports via email, I send out test files 90% of the time until fixed or at least to see what's going on. Why don't you send me an email, that is if you want to help fix it if needing fixing.Thanks @JeffBH for the suggestion. I was about to give this a whirl when I received a notification that ProScan has released update 17.8.0. I downloaded and installed this version in the usual manner. ProScan V17.8.0 appears to be functioning in all respects now, in my installation. Thanks everyone!
I keep posting the Bug Reporting link. I guess people don't read it. Here's the contents.I've noticed a big increase in CPU usage in 17.8. I have about 0.2% per instance in 17.6, and about 12% per instance in 17.8 - Not sure why that is. Is there a setting added that could impact CPU that much?
No setting. Can you send me an email so I can start to send you test files.Wow.... I was asking if there was a setting that may affect it... Guess I 'can't read'....
If anyone is experiencing a high CPU usage in 17.8, please email me so I can send out test files. I never received an email from beachside so I don't know if this is an issue.I've noticed a big increase in CPU usage in 17.8. I have about 0.2% per instance in 17.6, and about 12% per instance in 17.8 - Not sure why that is. Is there a setting added that could impact CPU that much?
I just checked. No issues here.If anyone is experiencing a high CPU usage in 17.8, please email me so I can send out test files. I never received an email from beachside so I don't know if this is an issue.
If anyone is experiencing a high CPU usage in 17.8, please email me so I can send out test files. I never received an email from beachside so I don't know if this is an issue.
I just checked. No issues here.
Thanks for the feedback. I haven't received any emails on this so I take it there's no issues.No issues on my end either.
Negative, Someone emailed me a few days ago on the Web Server causing ProScan to crash so I will be looking at it this week and next week. Revert back and let me know what happens.Any word on when 17.9 is coming? I may revert back to an older version if it's gonna be a while. Currently can't rely on webserver in 17.8.
Yes, email me so I will have all the info in one place and I will send you test files to see what's going on.Apologies, I started a separate thread and last corrispondence I had with you said not to email you because you had been notified by someone elae with the same issue.
Shall I email you the information? Or would you like to check the original post out?
For clarification, the person that emailed me a few days ago is the same person I referred to in the other thread. I sent him 1 file with a small change and it failed so I will be looking into it this week and next week in detail. I have 2 reports on 17.8 including your report.Apologies, I started a separate thread and last corrispondence I had with you said not to email you because you had been notified by someone elae with the same issue.
Shall I email you the information? Or would you like to check the original post out?