Screen updation in RMWB

Hi,
I need to add a new button in the extended search functions tab in RMWB transaction. When you run tansaction RMWB the initial screen will come with Recipe,Substance, Packaging, Material & Favourites in the navigation area of the screen. And when you double click on any on the application are on the right side will change. And in the application area there are boxes for validity area, Restricting criteria for search and extended search funtions. My requirement is to add a new button in Extended search functions to search for specifications having a text in a defined field. So when you click on the button it will pop up a screen where you can enter the text to search. Can anyone provide any solutions for this.
Thanks
Varghese

Varghese,
Check the link
http://help.sap.com/saphelp_utilities472/helpdata//EN/60/ee1a3a0792a622e10000000a114084/frameset.htm
There may be some settings to be done in SPRO. Check it.
Regards
Prakash.

Similar Messages

ScreenUpdating=False fails to prevent screen updating, and causes bizarre behaviour

I have recently installed Office 2013 (MSO Standard 2013) on my (Win 7 Professional) computer. During a brief transitional period, Office 2003 will remain on my computer.
I had been looking forward to running the many Excel VBA applications on Excel 2013, but am not only disappointed, but alarmed. We are significantly dependent on over 50 business applications running in Excel VBA (many of which are complex,
and many of which I have developed), but we now find that seemingly one difference alone (though we may yet discover more) is rendering many of them virtually unusable. That difference is the behaviour of the Application.ScreenUpdating method.
In Excel 2003, the ScreenUpdating method behaved intuitively, predictably and reliably. It basically does what it says - all screen updating, except for the status bar, is frozen. To allow users to peek at any updates, one would simply
set ScreenUpdating=True and at the appropriate point freeze updating with ScreenUpdating=False. Now, in Excel 2013, we are instead finding behaviour which has to be described as bizarre, counterintuitive and destructive. Essentially, what is happening
is that whenever another worksheet is activated, ScreenUpdating=False does not prevent screen updating - and for good measure, there are a number of other unpleasant side-effects. I have spent many long hours searching through hundreds of forum posts
and testing workarounds - all without success. I have seen many posts complaining about ScreenUpdating in Excel 2013, but not a single implementable solution. Yes, I've seen the advice about replacing Select or Activate methods with objects, but
this workaround would not only be extremely costly and impractical in our case (it would require reworking tens of thousands of lines of code and would probably take many person months of unjustifiable work), it almost certainly wouldn't work. (You'll
have to take my word on that.) And all because ScreenUpdating=False doesn't really prevent screen updating any more! I cannot accept that ScreenUpdating is working properly in Excel 2013, nor that its functionality is in any way acceptable.
The problems are best illustrated with a simple example. I created this example to verify that the flickering was unrelated to the complexity of the business applications I referred to above. In this example, there is a "master"
workbook named "ScreenUpdatingTest.xls". This contains a single button on its only worksheet, and this button executes macro "TestScreenUpdating". This macro turns screen updating off, then sequentially opens workbook AAA.xls,
workbook BBB.xls and workbook CCC.xls with a 3 second interval between each workbook being opened. After 3 more seconds, it activates workbook ScreenUpdatingTest.xls and then turns screen updating on. Along the way, it reports these actions in
the status bar. One would expect that this would result in AAA, BBB and CCC being opened in the background, with the user seeing no changes on the screen apart from the status bar and the workbooks appearing in the task bar. This is precisely what
happens in Excel 2003.
By contrast, Excel 2013 seems to do absolutely nothing for about 12 seconds (even the task bar and the status bar remains unchanged), then, AAA, BBB and CCC can be seen to open (in maximized windows) in rapid succession. The only message I see in the
status bar is the last one, "Switched back to ScreenUpdatingTest.xls." Even more bizarrely, that there is a call to Msgbox "Hi" just before the Application.ScreenUpdating=True at the end of the subroutine - and this should be unrelated
to which workbook the focus end up with, right? Wrong! If Msgbox "Hi" is commented out, the focus ends up with CCC.xls - in other words, Workbooks(ThisWorkbook.Name).Activate seems to be ignored. But if Msgbox "Hi" is
uncommented, the focus ends up with ScreenUpdatingTest.xls! This is crazy, isn't it?
Sub TestScreenUpdating()
Application.ScreenUpdating = False
Application.Wait Now() + TimeValue("00:00:03")
Workbooks.Open ThisWorkbook.Path & "\AAA.xls"
Windows("AAA.xls").Activate
Application.StatusBar = "AAA.xls has been opened."
'Excel 2003:
' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
' AAA.xls is open in the task bar.
' The message that AAA.xls has been opened appears in the status bar.
'Excel 2013:
' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
' AAA.xls is >>>NOT<<< open in the task bar
' >>>NO<<< message that AAA.xls has been opened appears in the status bar.
Application.Wait Now() + TimeValue("00:00:03")
Workbooks.Open ThisWorkbook.Path & "\BBB.xls"
Windows("BBB.xls").Activate
Application.StatusBar = "BBB.xls has been opened."
'Excel 2003:
' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
' AAA.xls and BBB.xls are open in the task bar.
' The message that BBB.xls has been opened appears in the status bar.
'Excel 2013:
' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
' AAA.xls and BBB.xls are >>>NOT<<< open in the task bar.
' >>>NO<<< message that BBB.xls has been opened appears in the status bar.
Application.Wait Now() + TimeValue("00:00:03")
Workbooks.Open ThisWorkbook.Path & "\CCC.xls"
Windows("CCC.xls").Activate
Application.StatusBar = "CCC.xls has been opened."
'Excel 2003:
' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
' AAA.xls, BBB.xls and CCC.xls are open in the task bar.
' The message that CCC.xls has been opened appears in the status bar.
'Excel 2013:
' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
' AAA.xls, BBB.xls and CCC.xls are >>>NOT<<< open in the task bar.
' >>>NO<<< message that CCC.xls has been opened appears in the status bar.
Application.Wait Now() + TimeValue("00:00:03")
Workbooks(ThisWorkbook.Name).Activate
Application.StatusBar = "Switched back to ScreenUpdatingTest.xls."
MsgBox "Hi"
Application.ScreenUpdating = True
'Excel 2003:
' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
' AAA.xls, BBB.xls and CCC.xls are open in the task bar.
' The message that we have switched back to ScreenUpdatingTest.xls appears in the status bar.
'Excel 2013:
' Workbooks AAA.xls, BBB.xls and CCC.xls appear in rapid succession.
' When execution ends:
' If Msgbox "Hi" is commented out, the focus is with CCC.xls.
' If Msgbox "Hi" is uncommented, the focus is with ScreenUpdatingTest.xls.
' AAA.xls, BBB.xls and CCC.xls are >>>NOT<<< open in the task bar.
' The message that we have switched back to ScreenUpdatingTest.xls appears in the status bar.
End Sub
Surely it is reasonable to expect that such functionality should remain consistent from one version to the next! Our applications in Excel 2003 had a professional, elegant user interface, and they behaved predictably, intuitively and robustly.
With Excel 2013, this is utterly trashed, with flickering, unpredictable behaviour (who knows what will get the focus?) and inefficiency (things are so much slower when the screen updates). With Office 2003 going out of support, vast numbers of people
in my company will be moving to Excel 2013 as Excel 2003 is decommissioned. I imagine the same will be happening in many other companies. We now find ourselves on the cusp of being dealt us a devastating blow due to ONE DYSFUNCTIONAL METHOD, and
we are desperate for a solution. A solution would either have to restore the former Excel 2003 functionality of ScreenUpdating, or it would have to introduce a new method which really does turn screen updating on or off without exception.
Please, HELP!
-Peter

Thanks for the input, Jim.
I don't think the Single Document Interface is contributing to the problem. Since installing Office 2013, Excel 2003 has also inherited a Single Document Interface - yet while it behaves like a charm, Excel 2013 behaves ineptly.
Whatever the reasons for the problem, the fact is that this functionality is now broken - one might even say catastrophically broken - and some sort of resolution is essential. It would be madness to allow something like this to have such a severe
impact on business operations.
My call for help is still out there, as loud as ever! BTW, I can send my example files, zipped, to anyone who might like to look at them.
Peter
Sydney, Australia

A question about screen updation of T61

Hi there
I got a question about screen updation.
Currently, my T61's screen is 14.1 XGA TFT 1028x768, and it can't work, thus I am considering to replace it with the better 14.1" SXGA+ LCD SCREEN .
However, I am a little concerned about the compatiblility problem, hence I just wonder whether the new SXGA+ screen can fit for my current T61 laptop or not?? Thanks a lot for your answers!
Regards
Peng

you can buy it from IBM parts, and it will then sure to work for your laptop.
Here is the manual that shows you how and what parts you need:
http://www-307.ibm.com/pc/support/site.wss/MIGR-67979.html
P.S. If you have warranty this upgrade will void your remaining laptop warranty, as the LCD is not CRU (customer replaceable unit).
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

Glance screen update for lumia 520

Why will 520 not get glance screen update..? Im aware tat both 720 n 520 chip set ram everything is same.. But y shld 520 users miss it?
Solved!
Go to Solution.

I was told that the type of screen used on the 520 wasn't compatible with glance screen which could make sense as the screen is of noticeably lower quality than the one on the 620 and 720. So perhaps it wasn't possible to add that feature without it being a massive battery drainer.
I don't think they've withheld the feature just to make you buy a better model.

HT5422 How to get an better screen-update? The view on the remote Mac is nearly static.

How to get an better screen-update? The view on the remote Mac is nearly static.

You can try reducing the bit depth of the screen image via the slider in the upper-right of the Control window. If that doesn't help, you may just not have a sufficiently fast network connection to correctly handle the data transfer necessary. This is often the case if you're connecting across the Internet. What is your network speed between the administration system and the client?
Regards.

Luminary Micro OLED screen updates so slowly.

I am evaluating the Luminary Micro LM3s8962 Eval Board using the LabVIEW for ARM toolkit. I have created a global variable that represents a 128x96 pixel image that I then write pixel by pixel to the OLED Screen. It takes over ten minutes to write the final image to the screen.
Why is it taking so long, Am I doing something completly incorrect?
Any help with this problem or to hear from anyone else evaluating this board would great.
I have attached my VI below:
Attachments:
Display.vi ‏17 KB

Hi phil_dal,
At a first glace, I see one minor change that could drastically inprove your screen update rate. In your program, you have your innermost loop calling the Display Set Foreground subVI and the Display Draw Pixel subVI. I would recommend not updating your screen after accessing each individual pixel. (Wire a FALSE input into the Display Draw Pixel.) You can then update your screen once after all the pixels have been loaded by using the Display Update VI. Do this outside of both loops.
I hope this helps,
Kevin S.
Applications Engineer
National Instruments

Threads shutdown screen updates

Hi.
I'm working on a web browser in java that asynchronously creates URL connections and downloads the data. The problem that I'm having is that while this download is going on, the standard UI threads seem completely locked out, and I cannot update the screen with a partial image or to display the progress on the download. I've tried setting the Thread priority for these new threads to Thread.MIN_PRIORITY, and explicitly calling Thread.currentThread().yield() after a data update, but the screen never updates. Interestingly though, if I add the same yield command in the read() method of my inputstream, I do get screen updates (although this has a tremendous hit on the performance of the downloading threads and is not a viable option)
Does anyone have any suggestions?

It sounds like your AWT thread is either deadlocking or is being kept busy with something too time-consuming to allow normal processing of GUI events and updates.

Us Draw/Picture vi's or 3D active-X to draw w/o screen update timing glitches?

For a visual component of a multisensory psychophysical task I need temporal precision. Should I use Draw/Picture vi's or 3D active-X to draw 2D objects w/o screen update timing glitches? How should I synchronize the screen presentation with analog in data streams (within 1 ms)? Should the loop involved in (drawing and) updating the display window be running in parallel to my data collection loop?

To answer your question, I would recommend using the LabVIEW display VIs as opposed to ActiveX objects if you are worried about the screen update rate from code to display. You can definitely benchmark the time required to run ActiveX code as compared to LabVIEW display VIs, but you cannot benchmark when the interface has actually updated. However, because ActiveX has an additional layer of communication, I would assume that this could potentially extend the time that this operation would take.
For your application as a whole, I also have other reservations about the timing requirements you have. Specifically, you might not be able to ensure that you have accurate correlation within 1 ms depending on the specifications of the machine and concurrent processes running. By this I mean that the screen update for any operation depends on how fast Windows can process the command to redraw the screen. If you have a slow machine, or a large amount of concurrent tasks for the processor, this timing will be more of an issue.
The ideal platform that I would suggest would be a Windows machine dedicated to the display of these images. You could then run the acquisition code on a real-time processor and use the Windows host as a time server. By doing this, you can then correlate the timestamps of a screen update with the DAQ timestamps. I hope this information is useful for you. Please post back if you have any further questions.
Mike D.
National Instruments
Applications Engineer

Finally Found a Solution to the Missing Palettes/No Screen update problem!

Ever since CS3 came out, Photoshop and Illustrator in particular (the worst offenders) wouldn't run properl
y on my system unless I did a full reboot before running either. Photoshop would load, but all palettes would be empty. Illustrator would forget t
o update the client area of the screen. Neither application was useable in that state. I have complained about it before, to no avail.
Now I have found the fix: Increasing the User Handle and GDI handle limits in Windows.
Here's an article on how to do this:
Increasing User Handle and GDI Handle Limits
Have you ever been working with a good number of applications at once? Are you a naturally born multi tasker? Alright, answer me this - who has had Windows buckle under the weight of all of these applications and display error messages stating that the system is out of memory or out of resources, buttons and menus do not work correctly, or you get an error sound but no message on the screen? I’ve hit this numerous times, to the point that I’ve lost work because of it…
(By the way, Adobe, can you please implement that little feature that Microsoft Office has had for years known as “auto save”? I don’t know how many times I’ve managed to completely max out Windows designing a web site and have had Photoshop fall over dead and disappear off my screen, only to find out that when I open Photoshop up again that the entire thing saved jack-all, all of those layers and documents gone poof into the void of darkness… if Microsoft can do it, why can’t you?)
Sometimes this happens even when you have a lot of system memory (RAM) still available. For instance, open up Internet Explorer and hold Ctrl+N to open up as many Internet Explorer windows as you can before menus, icons, and menus start displaying incorrectly, disappear, buttons aren’t clickable, etc. Close a few out and check your Windows Task Manager in the “Performance” tab, I bet you will find that a lot of your Physical Memory is still available.
This publication applies to:
    * Microsoft Windows 2000 Professional
    * Microsoft Windows 2000 Server
    * Microsoft Windows 2000 Advanced Server
    * Microsoft Windows XP Home Edition
    * Microsoft Windows XP Professional
    * Microsoft Windows XP Professional x64 Edition
    * Microsoft Windows XP Media Center Edition
    * Microsoft Windows XP Tablet PC Edition
DISCLAIMER: mikedopp.com and mikedopp hold no responsibility or liability whatsoever should something go wrong, or if you incorrectly modify the Windows Registry. Please take extreme caution while following this publication and follow the steps correctly.
“Okie-dokie, if I have all of this memory still available, why is Windows saying I’m out of memory and out of system resources!?”
Simple. You have hit the “user handle” or “GDI handle” limit in Windows. This limit is there for two reasons:
    * Leaky applications or faulty code & malware can’t easily crash the system by attempting to overflow the system with GDI handles, making everything un-usable until a reboot is performed.
    * To prevent a user from opening up more applications than the system can handle.
If you have 1 gigabyte (or 1024MB) of RAM or higher, the default User Handle and GDI Handle limits can be pretty restrictive when running a large working set of applications that demand the most from your system and tax it heavily.
“Do you feel my pain?”
Yes, of course. Otherwise, I wouldn’t be writing this article that is more than likely a good 2 or 3 pages in length.
I’m a designer and coder, I use Adobe Photoshop with a lot of documents opened up - on top of that, I usually listen to music while working as it helps me work better, so Windows Media Player 10 is usually open on my machine. Also opened are Windows Messenger, Microsoft Office Outlook 2003, SmartFTP (one of the best FTP clients I’ve ever used, highly recommended), Microsoft Word, a few dozen Internet Explorer windows, some Mozilla Firefox windows with a few tabs opened in each one, and EditPlus 2 for coding.
That’s a pretty heavy working set of applications, and I demand the most out of my computer when it comes to multitasking (I have a Pentium 4 2.66GHz, with 1.5GB of RAM just for those who are wondering).
I too have nailed these handle limits - more than once. After much searching and pondering I have finally come up with a working solution around this issue (hurray!)
“Yeah yeah, stop rambling and cut to the chase!”
First and foremost, I must warn you that modifying these settings incorrectly can render your Windows installation near useless. Also, depending on your computer configuration and the amount of RAM in your system, you may wish to play around with the numbers until you find a setting that is perfect for your computer.
To back up everything, open the Registry Editor (click on Start, Run, and then type “regedit.exe” (without the quotes).
To backup a registry key:
    * In the Registry Editor on the left hand side, you will see the navigation pane. Using your mouse or keyboard, navigate to the following subkeys:
    * HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems
    * HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows
    * Right click on each of the subkeys above in the left hand pane and from the context menu that appears, choose the “Export” option. Save the exported registry data file where ever you wish, but make sure that it will be accessible should we need to restore the files.
“OK, I’ve backed everything up! Now what!?”
Don’t quit the Registry Editor just yet - we still need to make some modifications in order to increase the handle limits in Windows.
With the Registry Editor opened, navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems. You will notice a set of “REG_MULTI_SZ” and “REG_EXPAND_SZ” keys in the right hand pane. The one that we are interested in modifying is called “Windows”.
To modify the key, double click on it. It should look something like this:
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16
The section of this string we are interested in modifting is “SharedSection”.
In the SharedSection part of the string you will notice 3 numbers. What we are interested in is the middle value, “3072?. Modify this value so that the middle number is “8192?.
It should look something like this after modifying the value:
   %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,8192,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16
Now that we’ve changed this, lets continue, shall we?
In the left hand pane of the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows. In the right hand side, you will see two REG_DWORD values, named “GDIProcessHandleQuota” and “USERProcessHandleQuota”. We will need to modify both of these.
The first key we will want to modify is “GDIProcessHandleQuota”. This keys value can be set between 256 and 16,384 (maximum), and the default value is 10,000. I’d recommend using 15,000 as a value for this key, however if you are doing a lot of multitasking, shoot for the stars and go with 16,384.
This key can not be set past 16,384 as it is the maximum acceptable value.
Now, lets modify “USERProcessHandleQuota”. This keys value can be set between 200 and 18,000 (maximum), with a default value of 10,000. I’d recommend increasing this value to the same number used with “GDIProcessHandleQuota”, however as previously mentioned if you are working with a hefty application workload, shoot for the stars and go wth the maximum value of 18,000.
This key can not be set past 18,000 as it is the maximum acceptable value.
Do NOT attempt to increase these values past the maximum - Windows will become very unstable and may even stop working correctly. If Windows starts acting up after changing these values, lower them until the issues are resolved, or restore the backups of these keys’ values that we created before making modifications.
Now that you’ve changed these values, restart your computer and tax the system using the Internet Explorer trick mentioned previously - open Internet Explorer and hold down Ctrl+N on your keyboard to open up new Internet Explorer windows. Continue this until menus, buttons, and user interface elements stop working correctly. Also, open any applications you run day-to-day while you are performing this, so that you can get more of an idea if you have everything configured correctly.
You may also want to monitor your memory usage and handles information in Task Manager to see whether or not the above registry values need any more modifications.
I hope this helps with any multi-tasking issues you may have run into while running Microsoft Windows, now get back to work!

You work like I do. It's very cool that you published this fix for XP people, but yow, what a lot of detailed things to check/set! Seems like it might just be simpler just to move up to Windows 7...
-Noel

Finally Found a Solution to the No Screen update problem!

Ever since CS3 came out, Photoshop and Illustrator in particular (the worst offenders) wouldn't run properl
y on my system unless I did a full reboot before running either. Photoshop would load, but all palettes would be empty. Illustrator would forget t
o update the client area of the screen. Neither application was useable in that state. I have complained about it before, to no avail.
Now I have found the fix: Increasing the User Handle and GDI handle limits in Windows.
Here's an article on how to do this:
Increasing User Handle and GDI Handle Limits
Have you ever been working with a good number of applications at once? Are you a naturally born multi tasker? Alright, answer me this - who has had Windows buckle under the weight of all of these applications and display error messages stating that the system is out of memory or out of resources, buttons and menus do not work correctly, or you get an error sound but no message on the screen? I’ve hit this numerous times, to the point that I’ve lost work because of it…
(By the way, Adobe, can you please implement that little feature that Microsoft Office has had for years known as “auto save”? I don’t know how many times I’ve managed to completely max out Windows designing a web site and have had Photoshop fall over dead and disappear off my screen, only to find out that when I open Photoshop up again that the entire thing saved jack-all, all of those layers and documents gone poof into the void of darkness… if Microsoft can do it, why can’t you?)
Sometimes this happens even when you have a lot of system memory (RAM) still available. For instance, open up Internet Explorer and hold Ctrl+N to open up as many Internet Explorer windows as you can before menus, icons, and menus start displaying incorrectly, disappear, buttons aren’t clickable, etc. Close a few out and check your Windows Task Manager in the “Performance” tab, I bet you will find that a lot of your Physical Memory is still available.
This publication applies to:
    * Microsoft Windows 2000 Professional
    * Microsoft Windows 2000 Server
    * Microsoft Windows 2000 Advanced Server
    * Microsoft Windows XP Home Edition
    * Microsoft Windows XP Professional
    * Microsoft Windows XP Professional x64 Edition
    * Microsoft Windows XP Media Center Edition
    * Microsoft Windows XP Tablet PC Edition
DISCLAIMER: mikedopp.com and mikedopp hold no responsibility or liability whatsoever should something go wrong, or if you incorrectly modify the Windows Registry. Please take extreme caution while following this publication and follow the steps correctly.
“Okie-dokie, if I have all of this memory still available, why is Windows saying I’m out of memory and out of system resources!?”
Simple. You have hit the “user handle” or “GDI handle” limit in Windows. This limit is there for two reasons:
    * Leaky applications or faulty code & malware can’t easily crash the system by attempting to overflow the system with GDI handles, making everything un-usable until a reboot is performed.
    * To prevent a user from opening up more applications than the system can handle.
If you have 1 gigabyte (or 1024MB) of RAM or higher, the default User Handle and GDI Handle limits can be pretty restrictive when running a large working set of applications that demand the most from your system and tax it heavily.
“Do you feel my pain?”
Yes, of course. Otherwise, I wouldn’t be writing this article that is more than likely a good 2 or 3 pages in length.
I’m a designer and coder, I use Adobe Photoshop with a lot of documents opened up - on top of that, I usually listen to music while working as it helps me work better, so Windows Media Player 10 is usually open on my machine. Also opened are Windows Messenger, Microsoft Office Outlook 2003, SmartFTP (one of the best FTP clients I’ve ever used, highly recommended), Microsoft Word, a few dozen Internet Explorer windows, some Mozilla Firefox windows with a few tabs opened in each one, and EditPlus 2 for coding.
That’s a pretty heavy working set of applications, and I demand the most out of my computer when it comes to multitasking (I have a Pentium 4 2.66GHz, with 1.5GB of RAM just for those who are wondering).
I too have nailed these handle limits - more than once. After much searching and pondering I have finally come up with a working solution around this issue (hurray!)
“Yeah yeah, stop rambling and cut to the chase!”
First and foremost, I must warn you that modifying these settings incorrectly can render your Windows installation near useless. Also, depending on your computer configuration and the amount of RAM in your system, you may wish to play around with the numbers until you find a setting that is perfect for your computer.
To back up everything, open the Registry Editor (click on Start, Run, and then type “regedit.exe” (without the quotes).
To backup a registry key:
    * In the Registry Editor on the left hand side, you will see the navigation pane. Using your mouse or keyboard, navigate to the following subkeys:
    * HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems
    * HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows
    * Right click on each of the subkeys above in the left hand pane and from the context menu that appears, choose the “Export” option. Save the exported registry data file where ever you wish, but make sure that it will be accessible should we need to restore the files.
“OK, I’ve backed everything up! Now what!?”
Don’t quit the Registry Editor just yet - we still need to make some modifications in order to increase the handle limits in Windows.
With the Registry Editor opened, navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems. You will notice a set of “REG_MULTI_SZ” and “REG_EXPAND_SZ” keys in the right hand pane. The one that we are interested in modifying is called “Windows”.
To modify the key, double click on it. It should look something like this:
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16
The section of this string we are interested in modifting is “SharedSection”.
In the SharedSection part of the string you will notice 3 numbers. What we are interested in is the middle value, “3072?. Modify this value so that the middle number is “8192?.
It should look something like this after modifying the value:
   %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,8192,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16
Now that we’ve changed this, lets continue, shall we?
In the left hand pane of the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows. In the right hand side, you will see two REG_DWORD values, named “GDIProcessHandleQuota” and “USERProcessHandleQuota”. We will need to modify both of these.
The first key we will want to modify is “GDIProcessHandleQuota”. This keys value can be set between 256 and 16,384 (maximum), and the default value is 10,000. I’d recommend using 15,000 as a value for this key, however if you are doing a lot of multitasking, shoot for the stars and go with 16,384.
This key can not be set past 16,384 as it is the maximum acceptable value.
Now, lets modify “USERProcessHandleQuota”. This keys value can be set between 200 and 18,000 (maximum), with a default value of 10,000. I’d recommend increasing this value to the same number used with “GDIProcessHandleQuota”, however as previously mentioned if you are working with a hefty application workload, shoot for the stars and go wth the maximum value of 18,000.
This key can not be set past 18,000 as it is the maximum acceptable value.
Do NOT attempt to increase these values past the maximum - Windows will become very unstable and may even stop working correctly. If Windows starts acting up after changing these values, lower them until the issues are resolved, or restore the backups of these keys’ values that we created before making modifications.
Now that you’ve changed these values, restart your computer and tax the system using the Internet Explorer trick mentioned previously - open Internet Explorer and hold down Ctrl+N on your keyboard to open up new Internet Explorer windows. Continue this until menus, buttons, and user interface elements stop working correctly. Also, open any applications you run day-to-day while you are performing this, so that you can get more of an idea if you have everything configured correctly.
You may also want to monitor your memory usage and handles information in Task Manager to see whether or not the above registry values need any more modifications.
I hope this helps with any multi-tasking issues you may have run into while running Microsoft Windows, now get back to work!

You work like I do. It's very cool that you published this fix for XP people, but yow, what a lot of detailed things to check/set! Seems like it might just be simpler just to move up to Windows 7...
-Noel

Real Time Screen Updation in the Front End

I working for a banking sector, My requirement is that, there is a screen which stays open 24 hours 365 days , there are some database changes happening in the backend , the data needs to get refreshed in the page without actually clicking any refesh button.If possible please provide me with some page codes.

Code sample its up to you. Its a design issue and can be solved using RMI. The database sends an update flag to the registry object on the server.
The gui on the client side can be threaded for say every 100 mills seconds to download the RMI object from the sever and check the update flag. If true, to get the update field values with it.
Don't forget when you threaded to get the next update, to put a wait monitor till you get a response from the server and have a timeout just in case the server is not running, i.e restarted for example...

Dynamic screen update options?

We have a complex web-based user interface that is rendered using XSLT from a J2EE application. Each screen consists of lots of HTML fields, some of which are grouped together into what we call "multi-row blocks". A new block can be added by pressing a "+" button.
What our customers would like is that new blocks are added without the screen refreshing or changing. We used to have a JavaScript/Dynamic HTML solution that would do the complex HTML manipulation needed (insert new sections of HTML and re-name any fields in following blocks) but this was:
- very specific to IE 6's internals (it's manipulating how IE internally represents HTML, which can be different to the output of the original XSLT transformation);
- a couple of thousand lines of very brittle code, generally driven by regular expressions that kept breaking;
- was unacceptably slow for large screens (more than a 20-ish blocks)
To get around this we re-worked it to do a full server round-trip, using HTML Anchor tags to return the user to the start of the new block.
However, Internet Explorer has a very annoying bug that it refreshes the screen, shows the top of the form, then after a couple of seconds it then "bounces" down to the anchor position.
Does anyone know how we can get around this anchor problem? Or a better way to fix the solution, avoiding the screen refresh?
Our customers have recommended using AJAX, but that doesn't get around the problem of making a large amount of updates to the current HTML form, so would do little to help us?
Thanks,
Chris Nappin.

AJAX is really just a cadillac solution on top of your html DOM manipulation. In your case, if the client side can decide how to modify itself when the plus button is added, then ajax would just be overkill.
DOM manipulation while ugly is still probably your best bet.
AJAX, beyond what you have done already, just allows you to make server calls to get data without reloading the page. As it seems you don't need new data, ajax wouldn't help.

No Screen Update of the video

Hi
When I play the video that is placed in the timeline of the project, it plays all well,
but when I use my arrow keys a to go frame by frame it refuses to update the video.
Never had this before and have no clue where to find the error.
Love some help.
Thanks Jeanne

The video was shot in HDV 1440x1080i.
I created a sequence of 1024x576 and placed the clips in there.
I am using two monitors and one is for the video view only.
So no external TV or other screen
Thanks
Jeanne

Slow Screen Updates - MacPro, Nvidia 8800, and 30" Cinema HD

I've noticed some truly odd behavior from my rockin' box. The cursor update is really sluggish as I draw over an image. The lasso, paintbrush... well every tool chugs along at about 10-15 fps as I edit an image. It feels incredibly laggy (I'm using CS3).
I've also noticed that Quicktime doesn't play any movie smoothly. Even though Quicktime Player Pro reports a movie is playing back at 30 fps, the screen clearly isn't keeping up (it's maybe displaying 15-20 fps).
Has anyone else run into this?

Did you add the 8800 card sometime after you bought your Mac Pro, or was this something that's been going on from the start? There are some problems reported with the card using Apple's Motion.

Screen updates in Unix(AIX) vs. Windows

I have a Swing application that functions as the front-end controller to start tasks. The task are run in threads. I pass a JTextField variable to the class being started in the thread so that the task can return progress statistics to the screen. This all works fine on Windows NT, but in Unix(AIX) the updates to the screen appear to queue up and then flood to the screen when the thread ends. Any thoughts?
Thanks

It is not a buffered stream. Here is an example.
This would be in the main class.
class MyClient extends JFrame
          implements ActionListener
JTextField countTxtField = new JTextField("0");
public void actionPerformed(ActionEvent event)
String actionCommand = event.getActionCommand ();
if (actionCommand.equals ("getData"))
GetData gd = new GetData(inFileName, outFileName,
     urlName, countTxtField);
     gd.start();
countTxtField is passed so that it can be upddated by gd.
Here is an example piece of the GetData class.
class GetData extends Thread {
JTextField countTxtField;
long count;
public GetData(String inFileName, String outFileName,
String urlName, JTextField countTxtField)
this.countTxtField = countTxtField;
     public void someRoutine()
try
// some processing is done and count is keeping track
// a incrementing value that at certain intervals is
// displayed in countTxtField.
count1Txt.setText(Long.toString(count));
When running on Windows, the updates to countTxtField are displayed in realtime. When running on Unix(AIX), the updates do not come through until the thread finishes.
I hope that explains it better.

Screen updation in RMWB

Similar Messages

Maybe you are looking for