Files sent.
Wait your response.

Enigma wrote: Wed Jun 23, 2021 10:41 am Please let us know:
1. What version of EVB do you use? This is very important, because in recent release we have fixed similar problem

I use:
enigmavb_9.70_20210329

Enigma wrote: Wed Jun 23, 2021 10:41 am 2. What version of Windows do you use?

Windows 10 Home 64 bit
Version 21H1
Build 19043.1052

Thank.

I tried with both SYSTEM and WINDOWS folder, same error.
Exactly which files should they send to support?
1- .enigma project
2- Appplication test.exe
3- OCX and DLL

Thank you.

Thanks for the quick reply.
The OCX file is set up just as shown in the your tutorial, as images below:

What's wrong?

https://www.vbcorner.net/images/EP_ERRORS/ep_ocd_err1.png

https://www.vbcorner.net/images/EP_ERRORS/ep_ocd_err2.png
Please note that the others libraries (DLL) are not ...

I'm testing Enigma Protector trial (for next purchase) but I can't figure out how to configure the project.
If I start the 'protected' file locally it works fine, but when I transfer this file to a virtual machine and run it it tells me it can't find the OCX file or one of its components.
Where am I ...

I have created a test VB6 project that uses the Common Dialog via API (ie without using the COMDLG32.OCX control) and the ìnormal 'executable works fine.
When I run the boxed version the program starts but when I open any Open / Save dialog box after a few seconds it crashes, everything disappears ...

A boxed application doesn't work if run on Windows 10 Pro (build 10240) - 64bit
I have virtualized some OCX, but when run application I receive the error 339 (see image) and stop work.

Please note that same application work correctly on Windows 7 SP1 - 64bit.

When I double-click a .evb project file from Windows Explorer, EVB load the last project, instead.

Example:

- from Windows Explorer :
- double-click D:\VSInstaller4.3\VS6Installer43.evb project file
- EVB load the last project file D:\VSInstaller4.2\VS6Installer42.evb .

To open the correct ...

Can you try to reproduce the bug ?
No, of course, because the problem isn't the executable generated by VirtualBox,
but the system where all attached components has been un-registered.


Now I removed 7.20 and reinstalled the 7.10 (which I have never had problems), when I have a little time I'll ...

First of all, I tell you that with the previous version 7.10 I have never had any problems and I'm successfully deploying my VS6 installer v.4.0 (http://nuke.vbcorner.net)

Using the latest version 7.20 happened to me a disaster. :cry:
I wanted to try with my application in which I use some OCX ...