Did you start it with wrun32 -le some-error-file object-name ? Are you attempting to start the runtime that is on a mapped drive?

Exception c0000006 is EXCEPTION_IN_PAGE_ERROR. It means Windows tried to read a page from a filesystem into memory, but the operation failed, generally due to an I/O error. Most often it indicates a hardware problem with a disk drive or network card. It's also quite common if you're trying to run a program from an optical or external drive. It may be that one of the disk sectors that contains part of wrun32.exe has become damaged, for example.

If running from a mapped drive (network share) 0xc0000006 is an NTSTATUS code. Specifically it is STATUS_IN_PAGE_ERROR.

It is not uncommon to see these errors when you attempt to run an executable from a network volume. For whatever reason, if there is any even intermittent problem accessing the network volume, then you may see this error. When a module is loaded, the code is not physically loaded until it is needed. A memory mapped file is created, and when a particular page is needed, it is brought into physical memory on demand. If your network fails to meet this demand, your application stops with STATUS_IN_PAGE_ERROR.

The common ways to deal with this include:

Getting a more robust connection to your network volumes.

Copying the executable file to a local drive and running it from there.

Thank you, our consultant is indeed running from a network volume, so I am pretty sure that is the answer. She is going back to the client on next week and will install and run from a local drive and we will see what happens, but I am pretty sure you are correct.

Many thanks, I will post again if the problem persists, which I think is unlikely.

Thank you, our consultant is indeed running from a network volume, so I am pretty sure that is the answer. She is going back to the client on next week and will install and run from a local drive and we will see what happens, but I am pretty sure you are correct.

Many thanks, I will post again if the problem persists, which I think is unlikely.

Just to finalize, everything is OK when running on a local drive, and since this is not a major problem when using the application, we will continue to run that way.

Many thanks for the helpful suggestions