I am still 19.2. I've heard form a colleague that we can request certain files be exempt from the virus scan. Which files should I ask for .lock ? .err? .log? .out? Which files do we think Ansys is trying to access during startup. It dies before an output window even pops up. Thanks,, Dan -----Original Message----- From: Tom <cameljoe@optonline.net> Sent: Friday, April 12, 2024 8:54 AM To: XANSYS Mailing List Home <xansys-temp@list.xansys.org> Cc: Keith DiRienz <fea-technologies@cox.net>; aaron.caba@baesystems.us; Bohlen, Dan (GE Aerospace, US) <dan.bohlen@ge.com> Subject: EXT: Re: [Xansys] FW: New machine - new error Ansys APDL (classic) WARNING: This email originated from outside of GE. Please validate the sender's email address before clicking on links or attachments as they may not be safe. Dan, What version of ansys are you running? I found that, when running v2022r2 distributed under windows 10 with Crowdstrike installed, my solve times increased 10 to 20x. My model had roughly 15 million dof. User beware. Tom Caltabellotta Caci Senior mechanical engineer Sent from my iPhone On Apr 12, 2024, at 8:21 AM, Bohlen, Dan (GE Aerospace, US) via Xansys <xansys-temp@list.xansys.org> wrote: Hi Keith, Aaron, I think Aaron may have hit on it. In my Ansys start up script I do have the command to remove an existing .lock files that exist. Not sure that's the issue, but my test is going to be to use our system start.ans file (versus mine personal one) and see if that fixes it. So it is probably the "permissions" related to all the security stuff we have. We have "crowdstrike falcon sensor service" (some sort of anti-hacking software) in addition to some AI stuff, Anti-malware, VPN software running . There's enough software running in the background - seems plausible one of them thinks Ansys is attacking my machine! I will keep you all posted. Many thanks! Dan OhpleasePCletansysclassicstartupforme Bohlen -----Original Message----- From: Keith DiRienz <fea-technologies@cox.net> Sent: Friday, April 12, 2024 12:00 AM To: XANSYS Mailing List Home <xansys-temp@list.xansys.org> Cc: Bohlen, Dan (GE Aerospace, US) <dan.bohlen@ge.com> Subject: EXT: Re: [Xansys] FW: New machine - new error Ansys APDL (classic) WARNING: This email originated from outside of GE. Please validate the sender's email address before clicking on links or attachments as they may not be safe. Dan, Concerning the write error on unit 6, back in the old days unit 6 was associated with the text output file. So it might be related permissions, available disk or firewall. Keith DiRienz FEA Technologies Dana point, CA > On Apr 11, 2024, at 7:50 AM, Bohlen, Dan (GE Aerospace, US) via Xansys <xansys-temp@list.xansys.org> wrote: > > Removing inline attachment to get this message out there while awaiting moderator approval of the original message. > > From: Bohlen, Dan (GE Aerospace, US) > Sent: Thursday, April 11, 2024 9:35 AM > To: XANSYS Mailing List Home <xansys-temp@list.xansys.org> > Subject: New machine - new error Ansys APDL (classic) > > Hi All, > > Got a new desktop workstation a DELL Precision 7865. Pretty peppy. Had a hard time installing all the GE junk and applications. It is a windows 10 O/S. > > Sometimes Ansys19 APDL (classic) starts up fine, but randomly I get > this error box > > (I will try an inline attachment here.) > > > > It reads Intel(r) Visual Fortran run-time error > > Forrtl:severe (38): error during write, unit 6 file CONOUT$ > Image PC Routine Line Source > > (then a whole bunch of ANSYS.EXE ****** unknown lines and ***.dll **** Unknown lines. > > Any clues? > > Many thanks in advance. > > Dan Bohlen > Senior Engineer, Stress Analysis > STAR review chairman, military structures GE Aerospace > 1 Neumann Way > Evendale, OH 45215 USA > > Building B90 Column L 3.75 > M/D H358 Cell 513-917-3402 > > Building 200 Desk Phone 3-8816 > > GE FOCUS: Safety, Quality, Delivery, Cost > > "In God we trust, all others bring data." W Edwards Deming > > [IMG_0492] > > > _______________________________________________ > Xansys mailing list -- xansys-temp@list.xansys.org To unsubscribe send > an email to xansys-temp-leave@list.xansys.org If you are receiving too > many emails from XANSYS please consider changing account settings to Digest mode which will send a single email per day. > > Please send administrative requests such as deletion from XANSYS to > xansys-mod@tynecomp.co.uk and not to the list <image002.gif> _______________________________________________ Xansys mailing list -- xansys-temp@list.xansys.org To unsubscribe send an email to xansys-temp-leave@list.xansys.org If you are receiving too many emails from XANSYS please consider changing account settings to Digest mode which will send a single email per day. Please send administrative requests such as deletion from XANSYS to xansys-mod@tynecomp.co.uk and not to the list