Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Out of memory error on Windows XP

Status
Not open for further replies.

Peepain

Programmer
May 15, 2002
43
AR
Hello,

I am trying to resolve this problem but it seems to be difficult. Maybe somebody can help me.

When my users install my applications on Windows XP (not always) the app can´t start because of "out of memory (error 7)". This happens specially when the user has installed Office XP before my applications.

I am delivering the OCXs and DLLs from SP5 of Visual Basic 6.

Does somebody how to solve this problem?

Thanks a lot.

Diego
 
Er...we need a little more information...e.g what does your program actually do, particularly on startup?
 
Hello Strongm,

Thanks for your reply.

Actually my program does not do anything strange. In fact any EXE program (compiled with VB) runs. All of them have the same problem. It looks like an environment problem.

The programs are not started on startup. The installer creates icons on the desktop and on the menu. Nothing strange.

Thanks.

Diego

 
I can think of a couple things that might be wrong:

1) Your install is missing some dependencies (like parts of the VB runtime, or some custom controls, or the lastest MDAC_Typ.exe)

2) Your install is sending some operating-system version dependent files (the classic one people send when they shouldn't is SHDOCVW.DLL).

So, I would review what's being packaged and sent. At least to start.

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first
 
Um...sorry, should have been clearer myself; I meant on startup of the program, not of Windows.
 
I understand what you say.

However, the programs are not using MDAC_typ.exe or SHDOCVW.DLL.

It is really important for me anyway that you did not experienced this problem before. What it shows me is only mine and I should pay more attention when creating the packages.

I will check each OCX and DLL that I am sending and the package. Maybe the problem is there.

Thanks for your help
Diego
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top