Memory could not be written error

[bennett10]

Hi everyone,

I have recently created a WinPE CD, which contains a Visual Basic GUI.

However, I seem to be getting an error that I cannot seem to solve. Basically when I click a button my GUI I get the following:

The instruction at 0x769c737d referenced memory at 0x006e0069. The memory could not be written.

Does anyone know why I might be getting this?. I've tried my WinPE on 2 PCs, and get the same error.

Thanks

[Tripredacus]

What is the size of your boot.wim (on the CD) and the size of physical memory in the client? Here are some practical examples of requirements:

a ~200MB boot.wim x86 requires 512MB RAM on the client

a ~200MB boot.wim x64 requires ~1GB RAM on the client

however a 600MB boot.wim x86 will not work on a system with 4GB RAM on the client

[bennett10]

What is the size of your boot.wim (on the CD) and the size of physical memory in the client? Here are some practical examples of requirements:

a ~200MB boot.wim x86 requires 512MB RAM on the client

a ~200MB boot.wim x64 requires ~1GB RAM on the client

however a 600MB boot.wim x86 will not work on a system with 4GB RAM on the client

It's 169 MB and there is 2GB RAM available. Hmmmm

Is there any way to cut the size down?.

Thanks

EDIT

----

I've now tried it on 3 different PCs (all with RAM above 1GB) and I get the same error.

Edited May 19, 2010 by bennett10

[Tripredacus]

The RAM on the clients should be OK then. Next you need to troubleshoot your app in the PE. You did not say what version PE it is, or what architecture. If it is WinPE v2.1 x86, does you app run in a Vista SP1 PC? If your app makes use of .NET Framework shared assemblies, note that WinPE does not have .NET support. Use ProcMon or Dependency Walker to make sure your program has all the files it needs to run properly.

[bennett10]

I'm using Windows PE 2.0 x86 for Windows Vista.

The PC OS is Windows XP + SP2.

The program is a basic GUI created in VB 6 that has 3 buttons, and uses FSO to check the files exist and open them. The buttons open programs stored on the disc.I've ensured all the necessary scripting files are on the disc as well. Also, the program loads up from winpeshl.ini.

The funny thing is. When the error pops up (if I ignore it) i'm able to click a test button I created that opens Notepad. I can then browse to one of the programs (e.g. Norton Ghost) and it will open fine. It just doesn't seem to like opening from the GUI.

Also, if I set winpeshl.ini to open a program such as Norton Ghost from boot up it works. Very interesting.

p.s. Once upon a time I had it working with the same setup. Unless i'm missing something that i've forgot about, i'm not sure what the problem is.

Edited May 19, 2010 by bennett10

[allen2]

As Tripredacus already said, try procmon (from sysinternals).

I suppose you can launch your prog later by pointing in winpeshl.ini to cmd.exe and launch the gui after procmon.

Usualy those errors come from an application trying to write where it doesn't have the rights or can't (with the winpe CD ).

[bennett10]

As Tripredacus already said, try procmon (from sysinternals).

I suppose you can launch your prog later by pointing in winpeshl.ini to cmd.exe and launch the gui after procmon.

Usualy those errors come from an application trying to write where it doesn't have the rights or can't (with the winpe CD ).

I managed to solve the issue by not using objFSO. I was using this to check if the files existed, but considering everything is on disc the files will exist anyway. Not sure why objFSO wouldn't work though, but it's no big deal now.

Thanks

[allen2]

To my knowledge objfso is depending on WMI to work. And your winpe might not have wmi support.