"Error Allocating windows memory"
 

What is "Error Allocating windows memory" and how do i get rid of it.:?

I would defrag my Ram. I use a program called System Mechanic to do this.

I hope this helps.

Jim :g

Nope, done that and recovered all memory.

This in not a random problem. It happens during the conversion process.

i was just reading about that , and from what i read they said something about "cleaning out your registry", and that there is too many programs running, but don't take my word for it, i think the best way was to go to microsoft online crash analysis, and they have a free download on checking out your pc/laptops memory.

Thanks, I have done that. Still does it.:)

Laddie,
MTU will see this report and address the problem.

Thanks

Jim :g

ccleaner (dot) com is free

Yea, I was going to put in a support ticket today. Just thought I would check the forum first.

Thanks:)

Never mind, I was able to determine what they are and why i got them.:)

So share it Laddie. I know some others have seen this as well. Glad you figured it out.:g

Yea Laddie, what's your secret? :g :c

Jim :g

Sorry, didn’t have time to get back to this yesterday.
The error occurred while converting file in 4.2. I had about twelve bad zip files and got 45 <SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Verdana','sans-serif'">"Error Allocating windows memory".<?xml:namespace prefix = o ns = "urnhttp://forum.mtu.com/ /><o:p></o:p><...oNormal style=<o:p></o:p>
I noted the filename of the 12 bad zips and noted the record number of the "Error Allocating windows memory".<o:p></o:p>
<o:p></o:p>
I went back to source files and found that the 12 bad zip files would open and play, but for some reason Hoster did not like the file. To be safe I converted the original mp3+g and reloaded them. This fixed all the bad Zips.<o:p></o:p>
<o:p></o:p>
I looked at the original files for the "Error Allocating windows memory" (I had to open the songs database, find the record number, and retrieve the Disc ID) and found that these files would not unzip. The files were corrupt. I reloaded these files from the original disk.<o:p></o:p>
<o:p></o:p>
I think this error occurs because the convert application cannot determine the title of the bad .kma file. This, I believe, is a bug. It was relative simple for me to find and fix the files. But, for someone who as limited understanding of computers, (database) this could be annoying.<o:p></o:p>
<o:p></o:p>
I noted in other post that people were deleting bad zips. This is not necessary all you have to do is reload a good copy of the file. Once I reloaded all with good files, the convert program finished.<o:p></o:p>
<o:p></o:p>
And all is well in my world.:)<o:p></o:p>
<o:p></o:p>

Thanks Laddie. Good find.:c
I don't use zip files, so had not been able to figure out the memory allocation error. Now we can help the rest who are getting this problem.
I think one person had solved this problem by moving his files to another folder. This would refresh the load. The problem may not be the file itself but a problem with the drive's file allocation table or a sector of the file itself losing changing the location of the next sector. I know that gets a bit deep but I am looking for the root problem. The thing I am wondering is if a simple check disk would have solved both problems. Have to wait for the next one with this.
Thanks again Laddie!:g

Before updating to 4.2, I made a copy of my .kma files on another external drive. I went back to the backup, switched to 4.3 and tried to run the files that had showed up as bad Zips. These files ran.
I also tried to run the files that came up as “error allocating widows memory”. These files did not run.
<?xml:namespace prefix = o ns = "urnhttp://forum.mtu.com/ /><o:p><FONT s...<P><FONT face=I believe the files were just bad zips to start with. The older Hoster was not as discriminating as the new Hoster and it's convert application. I believe the new Hoster will prevent the loading of a bad zip.
<o:p></o:p>
So this is a good thing.:)