Touchsmart IQ 790.uk componant makes

Touchsmart IQ 790.uk
O.S Vista32 and XP
I've recentely installed XP onto a seperate partition so my system is dual-boot but I'm having problems finding drivers for the various componants for XP. Can anyone please tell me what make and model the LAN is so I can find the right driver manually.
Cheers

You can also take the Hard drive out and put it in a friend's PC (with SATA) as a second drive and copy the data off:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01060947&lc=en&dlc=en&cc=us&lang=en&rule=776&pr...
... an HP employee expressing his own opinion.
Please post rather than send me a Message. It's good for the community and I might not be able to get back quickly. - Thank you.

Similar Messages

  • Touchsmart IQ 790.uk - screen problems

    Starting today, on start up, the monitor on bootup displays only a light green screen / white horizontal gradiented lines. The graphics card in the PC died a few months ago, and I've been operating on the motherboard's VGA ever since.
    I want to determine whether the LCD screen is the problem or the motherboard. I have a VGA monitor from an old computer which I'm able to connect to my TouchSmart via a mini-VGA convertor, and I wanted to try and see if I could get the PC running off this, because if I can, the problem is with the monitor, not the motherboard.
    But my issue now with this is that I would like to know whether anybody knows of a way to get the PC to boot so that it runs the VGA monitor rather than the inbuilt monitor, without being able to use the inbuilt monitor (which is kaput).
    If this isn't possible, I might just have to remove the hard drive and get a new machine, but I'd like to avoid that if at all possible.
    So if anyone has any advice on how to do the above, I'd appreciate it!

    You can also take the Hard drive out and put it in a friend's PC (with SATA) as a second drive and copy the data off:
    http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01060947&lc=en&dlc=en&cc=us&lang=en&rule=776&pr...
    ... an HP employee expressing his own opinion.
    Please post rather than send me a Message. It's good for the community and I might not be able to get back quickly. - Thank you.

  • VGA to Component Video

    Can anyone help, I've acquired a 500 Mhz iMac and would love to mirror the display on my TV. Unfortunately the scart socket on th back of my TV is taken up with other stuff (satellite and DVD) but I do have Component Video still available. Is it possible to find a cable to go from VGA to Component, or would it be better to go from VGA to DVI and then to Component?
    I've searched Google, but am bewildered by the choices available. Can anyone provide so useful links?
    Thanks,
    Lee

    VGA to component makes more sense (and is probably less expensive). VGA is analog and so is component. DVI is digital. There is no sense in going from analog to digital and back to analog.
    But I've never tried such a cable on a Mac's VGA output, so I'm not saying it will definitely work.

  • How to center a component on the page????

    Hi all
    i want to center a component on the page
    Sorry it may be some thing trivial ???
    but i ve a command button i want to center it on the page ????
    how???

    Hi,
    try this steps:
    1-surround the command button with panelGroupLayout with layout Horizontal.
    2-In panelGroupLayout property select Style tab.
    3-in the Text tab set horizontal Align with Center.
    4-in Box tab set width with 100 Percent
    if panelGroupLayout inside any other component make this palce width 100 percent and its Align Horizontal with Center.
    Sameh Nassar

  • Development Component Structure

    Hi experts,
    I've been developing WDPJ for almost 4 months now. I've seen some "problems" caused by heavy "DCs" in my environment here. I'll try to detail the structure that I currently have:
    - A "Models" DC, which carries most Models for the whole Project;
    - A "Component" DC, which usually carries some Models, and has a dependency to the "Models" above;
    - An "Application" DC, which is the entrypoint in the iView Portal. Depends on the "Component" above.
    Well, during this time I've noticed that, having your "Models" inside your Component makes it "inflate" a lot, and since the "code generation" is automatic, it will generate all the models again and again. This consumes a lot time. Also, it increases a lot the "Build Time", and further, the Deployment, since there's more information in the Component. (Not usually visible inside the LAN, but very noticeable using VPN).
    I'd like to add that, stuffs seems to be a little bit "messy" since there were at least four different developers working in this project. So, I'm currently facing "four" coding styles, at a point of time someone decided to create this "Central Models" DC, but only for new stuff. So, DC's that had their models still the same, additions would be made to this Central Model.
    My problem:
    Build time is too high. The dependency is killing me, since when I change any Model is spawning a lot of Builds, Activation process is a pain because of that, and also, Import and Assembly fases.
    My sugestion:
    Split DC's in three parts:
    - Models, Component, Application: The Component "DC" would have a dependency to the "Models", "Application" to "Component". This should be best case scenario to avoid facing with lots of builds, etc etc, but it will increase the number of DC's inside NWDI.
    I'd like to have some different opinions about this, since I'm quite new in WDPJ and I'm currently, working alone (I hate this part, since I don't have someone else to discuss implementations).

    Hi Siarhei,
    Thanks for your reply. As my reasons to create a new DC looks almost like yours, I suggested added these two new reasons on the list.
    Basically, it would be:
    - Split the "Application" in three DC's.
        - Application DC: Carries the entry Point of your Component. - This is usually maintained once, and Build process is not needed every time you Build your component Locally to Deploy.
        - Component DC: This is what gets usually Re-Build. I'd like to add that, in only rare cases we can have a Model change that not implies in Java code being changed. As this component will have dependency to its Models DC, this is OK, most because we usually Re-Import the Models a lot less often than the Component.
        - Models DC: Carries all the Models, usually the "size" would be a lot bigger than the Component DC. Will only be Build when we have a direct change to the Model, like Re-Import, Add or Delete. Always we Build this DC once, since the Import / Re-Import / Delete process are quite "straight forward" processes.
    I do agree that the first separation is not really demanded. We could basically have both, Application / Component in the same DC. Not a big deal. Taking a look to NWDI, and the Dependency, using an approach like this.
    When we change a Model inside a DC, for example:
    - It will spawn two Builds, one for Models, one for Component.
              -- I do understand that two Builds in this time will be slower than only one Build.
    - It will spawn "N" Builds to whatever dependent DC's we have. Example, Article Master Data, usually spawns 6 Builds, since we have an Interfaced View (Article Linking) in many Applications.
              -- At this time, all these other 6 Applications will be divided. Model's DC will not be Re-Built since they don't carry the Dependency to Article. Only Components DC will be affected, and usually, the size and the TIME is a lot less than if they're all inside one single DC.
    When we finish this first Assembly phase, we need some Test in QA systems. Returning "work" would probably not be something concerning Models. Usually, it's coding stuff.
    At this time, the Development will be a lot faster. Since we don't have the Models in the way, every Build is quite fast. When we put these changes in NWDI, also, the Build time will be faster, since we will carry less data.
    I hope I make myself a little bit more clear, since in my head an approach like this would save a lot time, instead of carrying unnecessary data every Build / Deploy / Activation / Imports / Assembly.
    Regards,
    Daniel
    Edited by: Daniel Ruiz on Jul 18, 2009 1:32 AM

  • Skins that effect the host component behaviour.

    There was an interesting question that was raised in the pre-release forums about what is the appropriate way to handle animations between the skin and its host. Basically the issue was if there is an animation in the host and another in the skin what would be the best way to code it so that both animations ran in parallel, My thoughts are why not do it all in the skin. this example animates a container by resizing it and centering it in the application.
    I figured it would be an interesting topic for those that are trying adding extra component functionality into the skin.
    @PD - Maybe you could apply a little of your magic to something like this and add it your blog.
    David
    The App
    =============================================================
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
      xmlns:s="library://ns.adobe.com/flex/spark"
      xmlns:mx="library://ns.adobe.com/flex/halo"
      creationComplete="application1_creationCompleteHandler(event)" width="100%" height="100%">
    <s:layout>
    <s:BasicLayout/>
    </s:layout>
    <fx:Script>
    <![CDATA[
    import mx.collections.ArrayCollection;
    import mx.events.FlexEvent;
    protected function application1_creationCompleteHandler(event:FlexEvent):void
    menu1.verticalCenter=height/2*-1 + 35; 
    menu1.horizontalCenter=width/2*-1 + 110;
    ]]>
    </fx:Script>
    <s:SkinnableContainer id="menu1" left="10" top="10" width="200" height="50"
    skinClass="SkinnableContainerSkin2" backgroundColor="#A16969">
    </s:SkinnableContainer>
    </s:Application>
    =============================================================
    The Skin
    =============================================================
    <?xml version="1.0" encoding="utf-8"?>
    <s:Skin xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark"
        xmlns:fb="http://ns.adobe.com/flashbuilder/2009" alpha.disabled="0.5" creationComplete="skin1_creationCompleteHandler(event)">
    <fx:Declarations>
    <s:Parallel id="sizer">
    <s:Animate target="{hostComponent}" duration="2000" repeatCount="1">
    <s:SimpleMotionPath id="setheight" property="height" valueTo="500"/>
    </s:Animate>
    <s:Animate target="{hostComponent}" duration="2000" repeatCount="1">
    <s:SimpleMotionPath id="setvertical" property="verticalCenter" valueTo="0"/>
    </s:Animate>
    <s:Animate target="{hostComponent}" duration="2000" repeatCount="1">
    <s:SimpleMotionPath id="sethorizontal" property="horizontalCenter" valueTo="0"/>
    </s:Animate>
    </s:Parallel>
    </fx:Declarations>
    <fx:Metadata>
        <![CDATA[
            [HostComponent("spark.components.SkinnableContainer")]
        ]]>
        </fx:Metadata>
        <fx:Script fb:purpose="styling">
            <![CDATA[       
    import mx.events.FlexEvent;
    import mx.core.FlexGlobals;
    private var Vert:int;
    private var Horz:int;
                override protected function updateDisplayList(unscaledWidth:Number, unscaledHeight:Number) : void
                    bgFill.color = getStyle("backgroundColor");
                    bgFill.alpha = getStyle("backgroundAlpha");
                    super.updateDisplayList(unscaledWidth, unscaledHeight);
    protected function resizeMe(e:MouseEvent): void
    Vert = int(FlexGlobals.topLevelApplication.contentGroup.height/2*-1)+35;
    Horz = int(FlexGlobals.topLevelApplication.contentGroup.width/2*-1)+110;
    if (hostComponent.height < 51)
    setheight.valueTo=500;
    setvertical.valueTo=0;
    sethorizontal.valueTo=0;
    else
    setheight.valueTo=50;
    setvertical.valueTo=Vert;
    sethorizontal.valueTo=Horz;
    sizer.play();
    protected function skin1_creationCompleteHandler(event:FlexEvent):void
    Vert = int(FlexGlobals.topLevelApplication.contentGroup.height/2*-1);
    Horz = int(FlexGlobals.topLevelApplication.contentGroup.width/2*-1);
            ]]>       
        </fx:Script>
        <s:states>
            <s:State name="normal" />
            <s:State name="disabled" />
        </s:states>
        <s:Rect left="0" right="0" top="0" bottom="0">
            <s:fill>
                <s:SolidColor id="bgFill" color="0x00DDDD"/>
            </s:fill>
        </s:Rect>
        <s:Group id="contentGroup" left="0" right="0" top="0" bottom="0" minWidth="0" minHeight="0" click="resizeMe(event)">
            <s:layout>
                <s:BasicLayout/>
            </s:layout>
        </s:Group>
    </s:Skin>

    This is a good question.
    There's no hard and fast rule to apply which says "this belongs in the skin" vs. "this belongs in the component".  Similarly, there are also no hard and fast rules around when to use a the new skinning architecture vs. just creating a custom component.  Just do whatever you feel comfortable with and makes your job easier.  At the end of the day, it's about productivity and not living up to ideals.  That said, there are probably some easier and more logical ways to do some things.
    On the skinning architecture vs. custom component debate, with a SkinnableComponent we have a clear separation of the component properties and behavior on one side and the look and feel of the component on the Skin side.  Also, there's a clear contract we use to talk back and forth to one another.  The reason for the separation between the Skin and the SkinnableComponent is so that we can have one Button SkinnableComponent and multiple Skins for that Button which all tweak the visual appearance of it.
    It doesn't make sense for every component to be skinnable.  If you know what your component is going to be and look like and don't need the extra flexibility skinning provides, then you can get rid of the extra overhead that skinning requires (like having 2 classes).  An example custom component is:
    <s:Group>
    <s:Rect>
    </s:Rect>
    <mx:Image src="..." />
    <s:Panel skinClass="myCustomSkinClass">
    </s:Panel>
    </s:Group>
    If you want more flexibility and want the ability to easily change the look and feel of the component (i.e. skin it), then you'd extend SkinnableComponent, fill out the skinning lifecycle methods, and create a default Skin for its appearance.
    Now, when you're building a SkinnableComponent, there's always a question of what to put in the component vs. what to put in the skin.  In general, we try to put the core properties and behaviors in the component and anything visual in the skin.  However, another guideline to consider is whether all skins would want this behavior.  If so, then it makes sense (and makes your life easier) to put it in the SkinnableComponent rather than the Skin.  We do this in the framework for components like VSlider, where the logic for positioning the y-axis of the thumb is in the component and not the skin, even though it's a "visual" thing.  We also have discussed how we would build up a ColorPicker component, and I think the way we would go about it is by putting a lot of the "visual" logic in the component because otherwise we'd have to duplicate it across all skins.
    Now, the other question you guys are asking here are "when do I bake effects (or any behavior) in to the component (either in the skin or in the SkinnableComponent AS class) vs. when do I declare effects alongside the component".  Again, I think the answer to that is whether you want all your components to have this behavior.  If that was the case, then I'd lose no sleep baking it in to the component.  However, if it's not the case, then I'd make the end-developer delcare it when they use your component, like:
    <s:MyCustomComponent id="myComponent" />
    <s:Resize id="resizer" widthTo="100" heightTo="50" target="{myComponent}"/>
    I would think most of the time, you probably wouldn't want to bake an effect like that in to the component, especially because it has some sizing information on it.  However, we have some effects baked in to some of the framework components, like when the thumb of a Slider moves around due to someone clicking on the track.  I think it's fine that it's baked in to the component, but I do think it should probably be stylable so that a user can customize it (that's on our list of lower-priority things to do btw).
    The framework has definitely evolved.  I think we started out with a more purist attitude and wanted a clear separation between the skin and the component.  However, as we built out components, we realized it's not always practical to do that.  Similarly, we wanted our skins to be pure MXML; however, for usability reasons, we decided that our skins should be styleable, and that requires a little bit of ActionScript code.  Border is a great example where it doesn't really follow a lot of these guidelines, but it's just a styleable component; however, this component makes other people's jobs easier.  At the end of the day, it's about productivity and usability, and hopefully the Spark architecture is a step in the right direction.
    Anyways, I hope that helps some.  These are just some guidelines.  As people play around with the architecture more, I'm sure some other people will have some good advice to share as well.
    -Ryan

  • Session scope for component tree subtree

    I'm very new to JSF. Here is what I'm trying to do: I created a custom component, renderer, and tag. This custom action will always have children that are no custom, but whose rendering I must control (via encodeChildren, etc).
    The problem I have is that the CSS style of these components will change after they are rendered (DHTML & AJAX). Some are hidden, color changes, size change, etc. When I go to another page with the same custom action included, of course it just renders a new version with all of the changes lost.
    Now if this was a simple custom action with no children, I'd just create a managed bean with a value binding and there would be no problem. But what I am trying to do is save the ENTIRE subtree, ie. save the state of the custom component and all of its children also.
    Now the messy way to do this would be to take my component, make it a managed bean, then include a value binding every time I use that custom action. The custom renderer would look to the bean for how to render the children, etc. The problem I have with this approach is that I basically have to include attributes in my component (used as a managed bean) that redundantly describe the children.
    For example, my component:
    class UISearch extends UIComponentBase {
    private boolean showChild1;
    private boolean child1Color;
    etc..
    OR a better option, to have:
    private UIComponent child1;
    public setShowChild1() {
    child1.render = true;
    ....etc....
    The problem I have with the above aproach is that every time a page is requested, the UIViewRoot tree will be build, a new Child1 will be instantiated, and then during the rendering of UISearch's encodeChildren I'll have to pretty much copy over attributes..
    I wish there was a way that I could have a "managed component subtree" where UISearch and all of its children are instantiated once, held through session scope, and every time they are rendered, regardless of page, the existing, managed version is used.
    This sounds so obvious, and I am almost positive there is a way to do this, I just don't know how.
    Thank you!!!!!
    PS:
    I think I am on the wrong track. Basically all I want to do is have the UISearch and its children load the same normal way each time that they do now. I don't even care if the component tree is re-created, re-rendered, etc. But after this custom action is rendered, I call an AJAX loadConfig() type method that will return all of the style, innerHTML, src, etc. changes that must be updated.
    So my question really is.. what is the best practice for storing and retriving this information? I'm using DWR, and I'd like the loadConfig() to return an object with all the config stuff nicely organized.. so if the returned object is "search" and I need to load the 'display' CSS style for some child, i can do:
    child.style.display = search.history.clearHistoryLink.style.display;
    Who knows. Any and all ideas are welcome!
    Message was edited by:
    rrc3243

    I found example (bookstore) where I got answer about using backing bean in session scope.
    <!-- Backing Bean for bookshowcart.jsp -->
    <managed-bean>
    <managed-bean-name>showcart</managed-bean-name>
    <managed-bean-class>backing.ShowCartBean</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
    </managed-bean>
    <!-- Managed Bean -->
    <managed-bean>
    <description>
    Create a shopping cart in session scope the first
    time it is referenced.
    </description>
    <managed-bean-name>cart</managed-bean-name>
    <managed-bean-class>cart.ShoppingCart</managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    </managed-bean>
    ShoppingCart class don't have data properties like lastName or orderId
    Class have only somethings like this:
    protected BookDetails book() {
    BookDetails book =
    (BookDetails) context()
    .getExternalContext()
    .getRequestMap()
    .get("book");
    return (book);
    * <p>Return the <code>ShoppingCart</code> instance from the
    * user session.</p>
    protected ShoppingCart cart() {
    FacesContext context = context();
    ValueBinding vb =
    context.getApplication()
    .createValueBinding("#{cart}");
    return ((ShoppingCart) vb.getValue(context));
    * <p>Remove the item from the shopping cart.</p>
    public String remove() {
    BookDetails book = (BookDetails) item()
    .getItem();
    cart()
    .remove(book.getBookId());
    message(null, "ConfirmRemove", new Object[] { book.getTitle() });
    return (null);
    rule:
    Don't use backing bean with data properties in session scope!

  • Dynamic declarative component won't work properly within table row

    Hi guys,
    I built a dynamic declarative component which basically consists of an af:inputText surrounded by a af:panelLabelAndMessage tag.
    The component works fine until I put it inside a table column, then none of the attribute values get set.
    The problem seems to be related to the table row binding #{row.binding.Name.inputValue} , if I use a regular binding #{binding.Name.inputValue} it works ok.
    The declarative components attribute is defined as
    <attribute>
        <attribute-name>kbez</attribute-name>
        <attribute-class>java.lang.Object</attribute-class>
    </attribute>and is used as the inputText's value attribute
    <af:componentDef var="attrs" componentVar="component">
        <af:panelLabelAndMessage label="#{attrs.label}" id="dc_plam1"
                                 for="dc_it1" labelStyle="white-space:nowrap;"
                                 showRequired="#{attrs.showRequired}"
                                 rendered="#{attrs.rendered}">
            <af:inputText id="dc_it1" value="#{attrs.kbez}"
                          autoSubmit="true" immediate="false" ...>The component inside a table column is set like this
    <af:declarativeComponent viewId="/WEB-INF/ikb.adf.kreda.basis/mitarbeitersuche/ddc/mitarbeiterLOV.jsff"
                             id="ddc1" label="Mitarbeiter"
                             kbez="#{row.bindings.Kbez.inputValue}"/>My JDeveloper version is 11.1.1.5.
    Am I doing it wrong or is this a bug?
    Any help is appreciated.
    Thank you,
    Achim
    Edited by: Achim Rosenfeld on Mar 8, 2013 8:41 AM

    Hi,
    +#{row.binding.Name.inputValue} , if I use a regular binding #{binding.Name.inputValue} it works ok.+
    Don't think that #{binding.Name.inputValue} works okay in a table because it doesn't stamp the component per row. Actually I don't know if we support dynamic declarative components in a stamped environment (table). I know though that we don't for taglib declarative components in this context.
    Reason why it doesn't work: Tables are stamped at runtime, which means that for better performance, only the generated HTML is reused for each row with different data - not the component. Your component requires itself to be re-created for each row so it can re-read the attribute again. This is not the case in a stameped environment
    Solution: For your particular use case I don't think that a dynamic declarative component is needed as you can add the construct (af:inputText surrounded by a af:panelLabelAndMessage) directly into an af:column tag. The declarative component makes more sense for reuse of layout areas (e.g. custom tabs) that are iterated within an af:forEach (in which case instances of the decalarative components would be created).
    Bottom line: tables stamp their components and as such the attribute property exposed on a DDC doesn't seem to be called for each row, which is by design. This can be considered a bug if there is a use case demanding for a DDC in a table. If this is a requirement for you (and you can't directly add the components to the af:column tag) feel free to file this as a service request with customer support (required a support contract) so development can have a look if the requirement is feasible to implement.
    Frank

  • Want to find calling component name

    I have 2 components as below.
    component A : in component A have used component B and also embed view of component B in view containner in component A
    component B : have only layout for display data
    I'd like to know if i want to get the name of component A at the runtime in method of component B, How i can get it ?

    Hi,
    Pass the calling component name to the called component at the time of calling. Use the sample code below.
      DATA:w_url                TYPE string,
           w_value              TYPE string.
    *--  Get the URL of the called application
      CALL METHOD cl_wd_utilities=>construct_wd_url
        EXPORTING
          application_name = "called_application_name"
        IMPORTING
          out_absolute_url = w_url.
    **--  make the Value type compatible that has to be passed with the URL
      w_value = "Calling_component_name"
    Attach the parameters and its value with the URL that
    have to be passed to the 2nd application
      CALL METHOD cl_http_server=>append_field_url
        EXPORTING
          name  = 'VARIABLE_NAME'
          value = w_value
        CHANGING
          url   = w_url.nerate a popup window for the 2nd application with the above URL
      DATA lo_window_manager TYPE REF TO if_wd_window_manager.
      DATA lo_api_component  TYPE REF TO if_wd_component.
      DATA lo_window         TYPE REF TO if_wd_window.
      lo_api_component  = wd_comp_controller->wd_get_api( ).
      lo_window_manager = lo_api_component->get_window_manager( ).
      lo_window         = lo_window_manager->create_external_window(
                       url = w_url ).
      lo_window->open( ).
    And in the called application window handledefault you can retrieve the calling component name.
    In the window handedefault of called component make the VARIABLE_NAME as importing paramater, so that you will the varibale_name value in the handledefault code.
    Revert for any queries.
    Regards,
    Simi A M

  • Multiple application Configurations /Component Configurations.

    Hi,
    I want to know in which scenario we  have to create multiple application Configurations and multiple Component Configurations.
    Plz explain With examples...
    Best Regards,
    dev

    A component config controls the component it self. All views.
    eg a Component when called with config SALES, hides all PRODUCTIN fields.
    Or a Component called with config EXTERNAL automatically switches fields to DISPLAY only. whatever...
    You can see why many configs of 1 component make sense.
    Now you also know   a component can embed other components.
    SO how to you string these all together.
    When you configure an application:
        You simple choose one of the configurations for all embedded components
    that should be used.
    The APPL config tool, looks inside components to find other embedded components.
    You can have a deep selection of component configuration until you reach the lowest level.
    Hence why APPLICATION configuration is required and not just component configuration.
    The application config can have many component config selections inside it.
    Cheers
    Phil

  • NetFlix App on TouchSmart

    I have verified several times my username and password for logging into Netflix and it works fine on my browser iPad & iPhone but when I try and login to Netflix on the Touchsmart screen it fails?

    Make sure you've gone to the hp.com support pages for your model and have the newest version of the Netflix app, the older versions will do exactly this.

  • JBCL component problem,checkboxPanel

    To some who know this problem.
    I have a problem when use JBCL component ,make a
    checkboxPanel,the checkboxPanel become red background and
    can not set any property.
    how can I solve this problem?
    Thanks you
    Sen
    null

    I believe that this means that the bean is not recognized by the IDE. However, the class will still work, although you'll have to read the documentation and program it manually, which is really easy...

  • Matching Color Between 2 Images

    Selective Color Matching
    Open the image with color you like.
    Make sure your Info Palette is visible.
    Select the Eyedropper Tool.
    Look at the Options Bar, and set the sample size to 5 x 5. This will give you a good average color from a sample size larger than just one individual pixel.
    Hold the Shift key, and you'll see that the cursor changes. This signifies that you're ready to lay down a Color Sampler. Find a good spot to sample the color you want, and click there. You may lay down up to 4 Color Samplers in each image.
    Look at your Info Palette and you'll see that it has expanded to now include a pane (or panes) that display(s) the color component make-up of the spot (or spots) where you dropped a Color Sampler (or Samplers). In that pane you'll see a tiny little eyedropper icon, right below the "#1". Click and hold for a drop-down menu. Change the read-out to CMYK. This won't change the color-mode of your image, so don't worry about that. It just makes the following steps more intuitive.
    Write down the values for C, M, Y, and K.
    Open the second image in which you want to match the color to a similar color in the first.
    Now, for one of the most important parts of the process:
    Make an accurate selection of the areas you want to adjust. Save it as an Alpha Channel (Select---»Save Selection...New Channel) just to be on the safe side, and save your changes to the document.
    Using the Eyedropper again, Shift-Click to drop a Color Sampler in the new image, in an area that is similar in brightness as the sampler in Image 1.
    Change the readout of this new sampler to CMYK.
    With your object still selected, go to "Image---»Adjustments---»Selective Color..."
    Choose a color in the drop-down menu that is as close as possible to the color of the area you want to adjust.
    Now, while you keep an eye on the Color Sampler pane in the Info Palette, adjust the sliders in the Selective Color dialogue. You'll see the numbers change in the Info Palette. The numbers to the left of the slashes (/) are the "before" readouts, the numbers to the right of the slashes are the "After" readouts.
    Play around adjusting these Selective Color sliders until the "After" numbers for the second image Color Sampler match (or get really close to) the C, M, Y and K values you wrote down for the Color Sampler in the first image.
    Sometimes you'll need to work the sliders for more than one of the Selective Color drop-down menu colors. I usually start with the drop-down choice of "Neutrals," because it often allows me to do most of the correction there...lots of bang-for-the-buck. Also, you may need to make Selective Color adjustments, hit "OK" and then call the Selective Color dialogue up a secondperhaps even a thirdtime.
    Just match the "After" numbers for Image 2 to the Before numbers that you wrote down for Image 1.
    There are other methods for doing this, but this is one of the easiest ways.
    Keep in mind that the changes you make are destructive (i.e.: not reversible after you save and close the document). Because I trust my abilities, I know what I can get away with, and I'm usually satisfied with the results. If you have any worries about making permanent changes, just duplicate the layer you want to work on so you can go back to the original color if you need to.
    When you're finished, you remove the Color Samplers by again selecting the Eyedropper tool and (Shift+Option) [Shift+ALT] clicking (see the scissors cursor?) on the Color Sampler icon (s) in the image window.

    interesting,

  • Server 2012 fresh install - Running at a crawl. Possible hardware issue?

    Hello All,
    I have recently purchased a used server and just fresh installed Server 2012 to evaluate it, and I am experiencing a issue with it running very slow.   So far nothing has been setup or installed besides the OS, hard drives, and a external usb drive,
    so it is pushing me to believe my issue is hardware related.
    First let me describe the issue more.   Basically everything is slow to load.  Control panel takes 20 seconds...  trying to load disk management and other snap in from administrative tools all take 15-20secs+ and first come up in
    a greyed out window or the administrative tools window goes to "Not Responding" for a few seconds then loads it.
    I do not think it is due to the fact the server is used with slightly dated hardware as it has Dual Quad-Core 2.66 Xeons & 16gb ECC Ram, so I was thinking their must be a bad piece of hardware in there?  Maybe bad ram?
    Anyway I plan to start hardware diagnostics, but I just wanted to see if anyone had any insight or suggestions for me.  And to verify if this sounds like a hardware issue to you as well.
    Thanks!

    Windows 2008 R2 that is on top of the list of supported operating systems. It is a good choice for some testing with M350 G5. Then you can test the in-place upgrade and application compatibility test will tell you, which component makes the problem.
    If for example onboard NIC is not compatible, then you can use another NIC card that is compatible. When it is RAID controller (very often), then either use another RAID or single HDD (it is test only, not for production environment).
    You can explore the virtualization path. Get know if appropriate hypervisor from VMvare is compatible with this hardware is also compatible with Windows Server 2012 R2. VMware forum may answer your question on virtualization. Working in virtual environment
    will provide some experience too.
    Majority of current desktop equipment allows you for testing Windows Server 2012 R2. There are some exceptions, namely "high end game machines" that make you to find remedy for drivers (example
    MAXIMUS IV GENE-Z - here is a need to adapt inf file for NIC, because of there is low end NIC on motherboard.)
    For low performance issues use native tools like Performace Monitor and diagnostics - Event logs and Device Manager. For detailed analysis consider Sysinternals tools.
    HTH
    Milos 

  • How to copy a value from one Frame to another Frame.

    Hi,
    I am new to Swing and AWT prgramming .
    I have created a menu called " Test window " and it contains toplevel menu item "File" and File Menu contains subitems "Product Evaluation", "ProcessEvaluation", "ResourceEvalation", "TotalEvaluation" and "Exit".
    When i click File->Product Evaluation it displays a new Frame named frame1 , similarly if i click ProcessEvaluation , ResourceEvalation , TotalEvalation it displays frame 2 , frame 3 and frame 4 Respectively,
    frame 1 , frame 2, frame 3 contains four textfields with names t1,t2,t3 and t4.(NOTE: I have given same names for textfields in all three frames so that in future i want to extend my GUI).
    frame 4 contains 4 textfields with names t5,t6,t7,t8 and 4 buttons (b1,b2,b3,b4).
    After i compile my program i will select ProductEvaluation and enter some values in textfield of frame 1 and minimise it. Similary i will open ProcessEvaluation and TotalEvaluation and enter values in textfields of frame2 and frame3 and minimise them.
    My queston is now if i select TotalEvaluation and press Button1 in frame 4 it should display in textfield t5 the value extracted from t1 in frame1 added to the value extracted from t1 in frame 2 added to the value extracted from t1 in frame 3.
    ie after pressing Button 1 textfield t5 should conatin value of t1 in frame1+ value of t1 in frame2 + value of t1 in frame3.
    I am sending the code.
    Can you please help me.
    import java.awt.*;
    import java.awt.event.*;
    import javax.swing.*;
    import java.awt.Component;
    // Make a main window with a top-level menu: File
    public class MainWindow extends Frame {
        public MainWindow() {
            super("Test Window");
            setSize(500, 500);
            // make a top level File menu
            FileMenu fileMenu = new FileMenu(this);
            // make a menu bar for this frame
            // and add top level menus File and Menu
            MenuBar mb = new MenuBar();
            mb.add(fileMenu);
            setMenuBar(mb);
            addWindowListener(new WindowAdapter() {
                public void windowClosing(WindowEvent e) {
                    exit();
        public void exit() {
            setVisible(false); // hide the Frame
            dispose(); // tell windowing system to free resources
            System.exit(0); // exit
        public static void main(String args[]) {
            w = new MainWindow();
            w.setVisible(true);
        private static MainWindow w ;
        protected TextField t1, t2, t3, t4,t5,t6,t7,t8;
        // Encapsulate the look and behavior of the File menu
        class FileMenu extends Menu implements ActionListener {
            private MainWindow mw; // who owns us?
            private MenuItem itmPE   = new MenuItem("ProductEvaluation");
            private MenuItem itmPRE   = new MenuItem("ProcessEvaluation");
            private MenuItem itmRE   = new MenuItem("ResourceEvaluation");
            private MenuItem itmTE   = new MenuItem("TotalEvaluation");
            private MenuItem itmExit = new MenuItem("Exit");
            public FileMenu(MainWindow main) {
                super("File");
                this.mw = main;
                this.itmPE.addActionListener(this);
                this.itmPRE.addActionListener(this);
                this.itmRE.addActionListener(this);
                this.itmTE.addActionListener(this);
                this.itmExit.addActionListener(this);
                this.add(this.itmPE);
                this.add(this.itmPRE);
                this.add(this.itmRE);
                this.add(this.itmTE);
                this.add(this.itmExit);
            // respond to the Exit menu choice
            public void actionPerformed(ActionEvent e) {
                if (e.getSource() == this.itmPE) {
                   final Frame frame1 = new Frame("Frame1");
                    frame1.setSize(700,700);
                    frame1.setLayout(null);
                    t1 = new TextField("");
                    t1.setBounds(230, 230, 50, 24);
                    frame1.add(t1);
                    t2 = new TextField("");
                    t2.setBounds(330, 230, 50, 24);
                    frame1.add(t2);
                    t3 = new TextField("");
                    t3.setBounds(430, 230, 50, 24);
                    frame1.add(t3);
                    t4 = new TextField("");
                    t4.setBounds(530, 230, 50, 24);
                    frame1.add(t4);
                    frame1.addWindowListener(new WindowAdapter() {
                        public void windowClosing(WindowEvent e) {
                            frame1.dispose();
                    frame1.setVisible(true);
                else
                if (e.getSource() == this.itmPRE) {
                  final  Frame frame2 = new Frame("Frame2");
                    frame2.setSize(700,700);
                    frame2.setLayout(null);
                    t1 = new TextField("");
                    t1.setBounds(230, 230, 50, 24);
                    frame2.add(t1);
                    t2 = new TextField("");
                    t2.setBounds(330, 230, 50, 24);
                    frame2.add(t2);
                    t3 = new TextField("");
                    t3.setBounds(430, 230, 50, 24);
                    frame2.add(t3);
                    t4 = new TextField("");
                    t4.setBounds(530, 230, 50, 24);
                    frame2.add(t4);
                    frame2.addWindowListener(new WindowAdapter() {
                        public void windowClosing(WindowEvent e) {
                            frame2.dispose();
                    frame2.setVisible(true);
               else
               if (e.getSource() == this.itmRE) {
                 final   Frame frame3 = new Frame("Frame3");
                    frame3.setSize(700,700);
                    frame3.setLayout(null);
                    t1 = new TextField("");
                    t1.setBounds(230, 230, 50, 24);
                    frame3.add(t1);
                    t2 = new TextField("");
                    t2.setBounds(330, 230, 50, 24);
                    frame3.add(t2);
                    t3 = new TextField("");
                    t3.setBounds(430, 230, 50, 24);
                    frame3.add(t3);
                    t4 = new TextField("");
                    t4.setBounds(530, 230, 50, 24);
                    frame3.add(t4);
                    frame3.addWindowListener(new WindowAdapter() {
                        public void windowClosing(WindowEvent e) {
                            frame3.dispose();
                    frame3.setVisible(true);
                else
                if (e.getSource() == this.itmTE) {
                  final  Frame frame4 = new Frame("Frame4");
                    frame4.setSize(700,700);
                    frame4.setLayout(null);
                    t5 = new TextField("");
                    t5.setBounds(170, 230, 50, 24);
                    frame4.add(t5);
                    t6 = new TextField("");
                    t6.setBounds(270, 230, 50, 24);
                    frame4.add(t6);
                    t7 = new TextField("");
                    t7.setBounds(370, 230, 50, 24);
                    frame4.add(t7);
                    t8 = new TextField("");
                    t8.setBounds(470, 230, 50, 24);
                    frame4.add(t8);
                    ActionListener action = new MyActionListener(frame4, t5, t6, t7, t8);
                    Button b1  = new Button("Button1");
                    b1.setBounds(170, 400, 120, 24);
                    b1.addActionListener(action);
                    frame4.add(b1);
                    Button b2  = new Button("Button2");
                    b2.setBounds(300, 400, 120, 24);
                    b2.addActionListener(action);
                    frame4.add(b2);
                    Button b3  = new Button("Button3");
                    b3.setBounds(420, 400, 120, 24);
                    b3.addActionListener(action);
                    frame4.add(b3);
                    Button b4  = new Button("Button4");
                    b4.setBounds(550, 400, 120, 24);
                    b4.addActionListener(action);
                    frame4.add(b4);
                    frame4.addWindowListener(new WindowAdapter() {
                        public void windowClosing(WindowEvent e) {
                            frame4.dispose();
                    frame4.setVisible(true);
                else {
                    mw.exit();
          class MyActionListener implements ActionListener {
                private Frame frame4;
                private TextField t5;
                private TextField t6;
                private TextField t7;
                private TextField t8;
                public MyActionListener(Frame frame4,TextField tf5, TextField tf6, TextField tf7, TextField tf8)
                    this.frame4 = frame4;
                    this.t5 = tf5;
                    this.t6 = tf6;
                    this.t7 = tf7;
                    this.t8 = tf8;
                public void actionPerformed(ActionEvent e) {
                    String s = e.getActionCommand();
                    if (s.equals("Button1")) {
             // I think code for the Button1 action can be written here  
        

    hi,
    u have ot submit the values using
    b1 for f1,
    b1 for f2 and
    b1 forf3
    after u can access the values in to f4 other wise u con't
    what u have to do use method in each frame like
    setValueforframe1() { } and 2 and 3
    and u can call this method in frame 4 and u can get the values

Maybe you are looking for