Win2000 and Win16 app --> lack of GDI resources
-
Hello all, I need to perform some operation on some old 16 bit application (compiled under borland). Operation requires some text drawing (custom text control) and there is a problem. I use script which calls about 5000 such operations. After circa 500th there is a GDI problem. The result is that I receive dialog box "GDI cannot execute operation" and content of every window is not painted correctly (looks like global GDI failure). I tried to peridically closing this app, but I didn't notice any improve. I wonder is there any solution of this? Maybe I should try to change OS to Win9x, which has different old Win app emulation? Or maybe there is some app, which 'cleans' unused GDI resources? Any anser will be appreciate. I use Win2000, 128MB RAM, 32MB Video. Regards Bartek
-
Hello all, I need to perform some operation on some old 16 bit application (compiled under borland). Operation requires some text drawing (custom text control) and there is a problem. I use script which calls about 5000 such operations. After circa 500th there is a GDI problem. The result is that I receive dialog box "GDI cannot execute operation" and content of every window is not painted correctly (looks like global GDI failure). I tried to peridically closing this app, but I didn't notice any improve. I wonder is there any solution of this? Maybe I should try to change OS to Win9x, which has different old Win app emulation? Or maybe there is some app, which 'cleans' unused GDI resources? Any anser will be appreciate. I use Win2000, 128MB RAM, 32MB Video. Regards Bartek
If don't know if this is possible to do from a script. But, if you could kill the "NTVDM" process (Windows NT Virtual DOS Machine) process, the GDI resources used by 16-bit programs should be free'ed... - Anders Money talks, but all mine ever says is "Goodbye!"
-
If don't know if this is possible to do from a script. But, if you could kill the "NTVDM" process (Windows NT Virtual DOS Machine) process, the GDI resources used by 16-bit programs should be free'ed... - Anders Money talks, but all mine ever says is "Goodbye!"
Yes, thank you - I found this method useful yesterday. Instead of killing NTVDM process - I kill wowexec (all resources are freed, too). I wonder which method is more correct? Regards Bartek