Solving EAccessViolation

[Omron Forums Support]

If PeWin32Pro2 crashes on startup with the EAccessViolation error message (shown below), look in the C:\Windows\PEWIN32PRO2.INI file and then locate and remove the correct INI file as specified by the ActiveIni line. PeWin will recreate the initialization file on startup. By default, this initialization file is PEWIN32PRO2_Default.INI in your PeWin32Pro2 folder (C:\Program Files\Delta Tau\PMAC Executive Pro2 Suite\Pewin32Pro2\ by default).

 

[Ben Adams]

I followed these instructions, but they did not work. PEWIN32Pro2 did not remake the .ini files, and I continue to get an EAccessViolation error message.

I'm using Windows 7 64-bit if that makes a difference. My PEWIN32PRO2.ini file had the following line:

ActiveIni=C:\PROGRAM FILES (X86)\DELTA TAU\PMAC EXECUTIVE PRO2 SUITE\PEWIN32PRO2\PEWIN32PRO2_Defaultx64.INI

That's the file I deleted per the post above.

[Omron Forums Support]

If my fix above does not work for you, please email support at deltatau dot com, and we can send you a working .ini file.

[Unit101]

I've had this same issue several times, also when using Win7 x64.

 

For me the fix every time is to:

Control Panel - Programs - Repair PeWin application

 

Has worked several times for me... I suspect it corrects the real issue CP is describing.

[steve.milici]

Try also deleting C:\Windows\PEWIN32PRO2.INI.

[TSV]

When you replace your INI-config file with the default one, you loose all your workspace settings (Project files, Layout, Editor fonts|colors, Settings of child windows etc.).

 

My way to go:

 

1. Get current INI-file from C:\Windows\PEWIN32PRO2.INI

2. Find and open file in text-editor

3. Remove line DefaultDevice=nnnnnn in the section [MainForm] or set DefaultDevice=0

4. Save file.

5. Run Pewin32

[TSV]

Here is short video guide:

https://drive.google.com/file/d/1Ldt9bdfzJzJHxdk4ffmdUcrd1ZdbBX1F/view?usp=sharing

[alvarog3]

On 9/7/2021 at 11:36 AM, TSV said:

Here is short video guide:

https://drive.google.com/file/d/1Ldt9bdfzJzJHxdk4ffmdUcrd1ZdbBX1F/view?usp=sharing

me puedes ayudar a configurar una waterjet flow 2031b que perdio toda la informacion?  es año 2012 y flow no me quiere dar soporte. te lo agradeceria. soy de venezuela

[steve.milici]

We do not have any Flow Waterjet configuration or documentation files. You will need to contact Flow Waterjet for any service or troubleshooting of their machines. They will contact Omron technical support for any issues they cannot solve.

 

No tenemos ningún archivo de configuración o documentación de Flow Waterjet. Deberá ponerse en contacto con Flow Waterjet para cualquier servicio o solución de problemas de sus máquinas. Se comunicarán con el soporte técnico de Omron para cualquier problema que no puedan resolver.

 

[khumas2]

On 4/5/2011 at 9:04 PM, Omron Forums Support said:

If PeWin32Pro2 crashes on startup with the EAccessViolation error message (shown below), look in the C:\Windows\PEWIN32PRO2.INI file and then locate and remove the correct INI file as specified by the ActiveIni line. PeWin will recreate the initialization file on startup. By default, this initialization file is PEWIN32PRO2_Default.INI in your PeWin32Pro2 folder (C:\Program Files\Delta Tau\PMAC Executive Pro2 Suite\Pewin32Pro2\ by default).

 

What should I do if PeWin32Pro2 crashes on startup with an EAccessViolation error? please let me know, I know this is an old discussion but the answer to my question is very important I am appealing to the admin. Please approve my post, Thanks

Edited October 14, 2023 by khumas2

[Unit101]

10 hours ago, khumas2 said:

What should I do if PeWin32Pro2 crashes on startup with an EAccessViolation error? please let me know, I know this is an old discussion but the answer to my question is very important I am appealing to the admin. Please approve my post, Thanks

Try these steps and see which works...

1. delete INI file as described above

2. Control Panel - Programs - Repair PeWin application

3. Uninstall Pewin - remove ALL files in Directories - reinstall

-be sure you are ADMIN, Run install as ADMIN, and have user UAC turned all the way down to Minimum

-pewin need to edit the registry and this is often restricted in windows

 

Edited October 14, 2023 by Unit101