 |
|
|
|
Welcome to the Invelos forums. Please read the forum
rules before posting.
Read access to our public forums is open to everyone. To post messages, a free
registration is required.
If you have an Invelos account, sign in to post.
|
|
|
|
|
Invelos Forums->DVD Profiler: Desktop Technical Support |
Page:
1  Previous Next
|
|
Out of memory error |
|
|
|
|
|
| Author |
Message |
| Registered: March 14, 2007 | | Posts: 26 |
| | Posted: | | | |  FWIW, I was adding multiple UPCs. The only limitation should be my available RAM. |
| | Registered: March 13, 2007 |  Posts: 1,796 |
| | Posted: | | | | DVD Profiler is v86 type program and can not run in the memory chips 4G to 12G portion of your memory. Not many programs have version that can. Check win update for any driver, etc. that need updating,
When I went Win7 64, I updated my video drivers, audio drivers, virus checking program, and a few other programs that gave an optional 64 version.
I am running Win7 and only 4Gs of memory and over 15,000 profile and I don't have any memory problems.
Try running the DVD Profiler db repair program either from the start menu or from the Tools>Options>Utilities.
can check the size of DVD Profiler loading the Windows Task Manager: hold down the Ctrl, Alt, Delete keys. Look under the process tab: dvdpro.exe *32.
My DVDProfiler memory size is 418,032k.
Your problem might the size of your of virtual memory, search that under HELP.
Normally, unless some change it usually works pretty good by letting Windows sizing it. | | | We don't need stinkin' IMDB's errors, we make our own.
Ineptocracy, You got to love it.
"Nearly all men can stand adversity, but if you want to test a man's character, give him power." - Abraham Lincoln | | | | Last edited: by Srehtims |
| | Registered: March 14, 2007 | | Posts: 26 |
| | Posted: | | | | Quoting Srehtims: Quote:
DVD Profiler is v86 type program and can not run in the memory chips 4G to 12G portion of your memory. Not many programs have version that can. Check win update for any driver, etc. that need updating,
When I went Win7 64, I updated my video drivers, audio drivers, virus checking program, and a few other programs that gave an optional 64 version.
I am running Win7 and only 4Gs of memory and over 15,000 profile and I don't have any memory problems.
Try running the DVD Profiler db repair program either from the start menu or from the Tools>Options>Utilities.
can check the size of DVD Profiler loading the Windows Task Manager: hold down the Ctrl, Alt, Delete keys. Look under the process tab: dvdpro.exe *32.
My DVDProfiler memory size is 418,032k.
Your problem might the size of your of virtual memory, search that under HELP.
Normally, unless some change it usually works pretty good by letting Windows sizing it. I appreciate your effort, Srehtims, but it is not a memory issue on my system. The PC is highly tuned and has been through numerous torture tests to find errors (and this is ongoing). I have been running Win7 64-bit Ultimate (and Enterprise) since it was in alpha, with this very system. It is very stable. It appears to be a memory issue with DVD Profiler. Does anyone know whether DVD Profiler has a limit as to how many UPCs it can handle at a time via a text file? 10? 100? 1000? 10000? | | | | Last edited: by MarkAtHome |
| | Registered: May 19, 2007 | Reputation:  |  Posts: 6,730 |
| | Posted: | | | | Quoting MarkAtHome: Quote:
I appreciate your effort, Srehtims, but it is not a memory issue on my system. The PC is highly tuned and has been through numerous torture tests to find errors (and this is ongoing). I think you misunderstood Srehtims, what he wanted to say is that all x86 (32 Bit) applications can only adress memory in the first physical 3.5 gigabyte of your memory. When this is loaded with data, you're running out of memory for other 32-Bit applications no matter how many RAM your machine actually has. EDIT: This problem is similar to the long gone times of M$-Dos 6.x and Win 3.1 which for the first time could address more memory than 640 KByte. Many programs were still limited to these first 640 K and didn't run when these were already filled with data. A lot of fine tuning in the autoexec.bat was needed those days. Does anyone still remember bootdisks for games and the commands "LOAD_HIGH" and "DEVICE_HIGH"? | | | It all seems so stupid, it makes me want to give up!
But why should I give up, when it all seems so stupid?
Registrant since 05/22/2003 | | | | Last edited: by Lewis_Prothero |
| | Registered: March 29, 2007 | | Reputation: | | Posts: 2,737 |
| | Posted: | | | | I absolutely remember the "LOAD_HIGH" and "DEVICE_HIGH" days. Sometimes you would tweak and tweak until you could finally gain that 1K which would allow you to run that one game just a little more efficiently. And always you had to reboot clean before starting any game. Sorry, it was nostalgia time.
That said, I assume you have multiple processors and cores and you are running several programs at one time. 2 things to try:
1) Find out which programs are memory intensive and shove them into another processor.
2) Always launch DVDP first before any other programs...it's worth a try anyway...just thinking out loud.
Afterthought: Have your memory chips tested for leaks, not yours, but the computers. | | | | Marty - Registered July 10, 2004, User since 2002. |
| | Registered: June 12, 2007 | Reputation:  | | Posts: 2,665 |
| | Posted: | | | | Quoting Silence_of_Lambs: Quote:
Does anyone still remember bootdisks for games and the commands "LOAD_HIGH" and "DEVICE_HIGH"? And Quarterdeck (QEMM) and 386MAX? Good times. | | | | Bad movie? You're soaking in it! |
| | Registered: March 14, 2007 | | Posts: 26 |
| | Posted: | | | | Quoting Silence_of_Lambs: Quote:
Quoting MarkAtHome:
Quote:
I appreciate your effort, Srehtims, but it is not a memory issue on my system. The PC is highly tuned and has been through numerous torture tests to find errors (and this is ongoing).
I think you misunderstood Srehtims,
what he wanted to say is that all x86 (32 Bit) applications can only adress memory in the first physical 3.5 gigabyte of your memory. When this is loaded with data, you're running out of memory for other 32-Bit applications no matter how many RAM your machine actually has.
EDIT: This problem is similar to the long gone times of M$-Dos 6.x and Win 3.1 which for the first time could address more memory than 640 KByte. Many programs were still limited to these first 640 K and didn't run when these were already filled with data. A lot of fine tuning in the autoexec.bat was needed those days.
Does anyone still remember bootdisks for games and the commands "LOAD_HIGH" and "DEVICE_HIGH"? Yes, I remember those days with QEMM, etc. I had to run OS2 Warp, on multiple PCs, for a few years, back in the bbs days, so that I could run multiple sessions, etc., before MS Windows existed. Your point is well-taken. |
| | Registered: March 14, 2007 | | Posts: 26 |
| | Posted: | | | | Quoting mreeder50: Quote:
I absolutely remember the "LOAD_HIGH" and "DEVICE_HIGH" days. Sometimes you would tweak and tweak until you could finally gain that 1K which would allow you to run that one game just a little more efficiently. And always you had to reboot clean before starting any game. Sorry, it was nostalgia time.
That said, I assume you have multiple processors and cores and you are running several programs at one time. 2 things to try:
1) Find out which programs are memory intensive and shove them into another processor.
2) Always launch DVDP first before any other programs...it's worth a try anyway...just thinking out loud.
Afterthought: Have your memory chips tested for leaks, not yours, but the computers. Yes, I am running an i7-950 at 4140 MHz with four cores and eight threads, three XMP 4G 1600 MHz RAM sticks (ended up being more stable, but warmer, than six 2G sticks), a Noctua NH-D14 heat sink and six Noctua low speed fans to keep things relatively cool and "quiet". I made sure that all resources were available to DVD Profiler when I attempted this, so short of running in safe mode, nothing else was active. Processes are able managed by the 64-bit version of Process Lasso (great stuff). RAM has gone through months of testing, with the help of both ASUS and Kingston, with them swapping motherboards and RAM sticks until everything passed vigorous tests. Kingston even had me wait until they received new chips before they built me my last set of sticks. Therefore, I am (fairly) certain that the PC is in fine shape. What I need to know, most likely from DVD Profiler's developer... , what are it inherent limits, and I will gladly work within those limits. |
| | Registered: June 12, 2007 | | Reputation: | | Posts: 2,665 |
| | Posted: | | | | Quoting MarkAtHome: Quote:
What I need to know, most likely from DVD Profiler's developer... , what are it inherent limits, and I will gladly work within those limits. How many profiles are in your database? I have over 1,600 and DVDp runs fine (Win 7 Pro 64). Others around here have 10x that number of profiles. | | | | Bad movie? You're soaking in it! |
| | Registered: March 13, 2007 | | Posts: 1,796 |
| | Posted: | | | | What version of the dvd Profiler are trying to run?
I had a similar problem.
Do have a save?
I uninstalled the dvd Profiler.
Made sure that all dvd priler files were removed, especially files in your document folder.
reload the profiler then refresh the profiler list: Online>redresh updated online profile list...
then repair db Tools>options>utilies>repair profiler data base
restore db | | | We don't need stinkin' IMDB's errors, we make our own.
Ineptocracy, You got to love it.
"Nearly all men can stand adversity, but if you want to test a man's character, give him power." - Abraham Lincoln |
| | Registered: March 14, 2007 | | Posts: 26 |
| | Posted: | | | | I have the latest and greatest DVD Profiler.
Simply, if I am entering UPCs via a text file, into a brand new database, how many lines (one UPC per line) can that text file have before DVD Profiler is overwhelmed? Cutting and pasting those lines would have the same result. |
| | Registered: March 14, 2007 |  Posts: 2,337 |
| | | Registered: May 19, 2007 | | Reputation: | | Posts: 6,730 |
| | Posted: | | | | Quoting Kulju: Quote:
Limit for 32-bit process is 2GB. A 32 Bit process (AFAIK, but I might be wrong) can only adress 2Gig of RAM max. (Limitation of Windows 32 Bit, on a 64 Bit machine the 32 Bit process can address up to 3.5 Gig), but these must be located within the first 3.5 Gig of physical RAM. Win7 32 Bit can be forced to address more than 4 Gig of RAM, not sure of what use this is supposed to be, but here's the "tweak": http://msdn.microsoft.com/en-us/library/aa366796(v=vs.85).aspx (If your CPU supports this it should be enabled automatically by OS) | | | It all seems so stupid, it makes me want to give up!
But why should I give up, when it all seems so stupid?
Registrant since 05/22/2003 | | | | Last edited: by Lewis_Prothero |
| | Registered: March 13, 2007 | Reputation:  | | Posts: 1,428 |
| | Posted: | | | | Not a definitive answer, but I just created a new database using add multiple to read a file containing 2486 UPCs.
Win 7 Pro 64bit - 4 GB memory, used physical memory never exceeded 43% during the process. Resulting database contained 2646 profiles. | | | | Registered: February 10, 2002 |
| | Registered: March 14, 2007 | | Posts: 26 |
| | Posted: | | | | Quoting greyghost: Quote:
Not a definitive answer, but I just created a new database using add multiple to read a file containing 2486 UPCs.
Win 7 Pro 64bit - 4 GB memory, used physical memory never exceeded 43% during the process. Resulting database contained 2646 profiles. That's closer to what I am looking for, greyghost. Thanks. |
|
|
|
Invelos Forums->DVD Profiler: Desktop Technical Support |
Page:
1 Previous Next
|
|
|
|
|
|
|
|
|
|
 |