Freezing and rendering problems

Hi all,
I run an eMac PPC with OS 10.3.4. It is about three years old. I switch power off each night and restart every morning with automatic login for myself. Lately I have the following problems:
1. The system sometimes (read: often nowadays) freezes a very short time after boot-up. I can move the mouse and perhaps select something, but then everything freezes and I have to reboot with the on-off switch. If the system does NOT freeze a very short time after booting, I can usually do a day's work without serious problems.
2. Mail crashes quite frequently. This could of course be a separate problem.
3. Sometimes the Mac screensaver, which shows a selection of photographs zooming in slowly, has problems rendering the pictures. I see a lot of flickering small rectangles in the pictures. The desktop picture (which is steady, not zooming) has no trouble of this kind.
4. Sometimes there are tiny errors on the screen: small short lines where they should not be, small pieces of a line or characters missing. In these cases usually also problem 3 shows up.
Are these problems related? Can reinstalling the system help? Can monitor problems cause system freezes? Please tell me this is not a hardware problem...
Greetings,
Sjaak

Not that you want to hear this, but it's probably a hardware problem.
2004 eMacs had an issue with a batch of capacitors that went bad, leaking and bulging, consequently causing issues with graphics, freezing and power exactly as you have described.
Fortunately Apple recognised the problem and initiated a repair extension program on the affected models. To see if you qualify check your mac against the details here http://www.apple.com/support/exchange_repair/emac.html to see if you qualify.
I have the same issues, and have found a workaround that's doing great until I can get my machine to a service centre, in order to ease the problem boot the mac in safe mode (hold down shift) and log in as admin. navigate to system then library and find all the graphics drivers (I can't remember where) and delete all the nvidia and old ati ones (basically leaving only those that are correct for your machines card). I've lost some graphical abilities but otherwise everything is great.

Similar Messages

I'm having problems with 7.1 update my flash "flashes" now when I receive txt's and notifications! And I'm also having problems with freezing and wifi problems! How do I solve this?

I'm having problems with 7.1 update my flash "flashes" now when I receive txt's and notifications! And I'm also having problems with freezing and wifi problems! How do I solve this?

Doh! Rectified flash!
But when face timing 2 seconds after it connects wifi disconnects? Any thoughts

Freeze Frame Rendering Problem

I have a problem with the rendering of freeze frames that are part of a one-hour video I created in Final Cut Express 4 when burning the video using iDVD.
I'm exporting the video from FCE to a non-self contained Quicktime movie which I then drop into my iDVD template. One or two of the freeze frames (5 10-second freeze frames and 5 5-second freeze-frames) end up with a vibrating horizontal motion.
This does not occur when I play the video file in Quicktime -- the freeze frame is solid as a rock. I've burned the DVD using all three "quality" settings in the iDVD project settings, from "best performance" to "professional" quality. Every burn ends up with a vibrating freeze frame when played from the DVD.
All the rest of the video is beautiful. I'm not sure if this is a rendering problem or some other setting issue in iDVD. All help or suggestions appreciated.
Mike

IMHO, the best thing you can do is keyframe some motion on your freeze frames. In all likelihood, you are dealing with an interlace issue. A TV screen use an interlaced signal where one line is drawn quickly followed be the second. In motion video, you will never notice interlacing. On a freeze frame however, you will certainly be able to see it. If you add some motion (Ken Burns effect), you can minimize this. You could try keeping the freeze frame... frozen and use a de-interlace filter.
Mike

Spry Menu Bar 2.0 (1.0) - Handling of widget generated CSS, placement and rendering problems in CSS

Hello:
I wanted to repost my question to re-frame the issue based on what I have learned thus far.
I am working on a website that has been developed using the Spry Menu Bar Framework UI (2.0) I.0, that has some peculiar rendering problems that affect IE 6 in particular. The CSS is reprinted below.
In particular, when I post the widget generated CSS in the head as it is orginally situated by the framework, the menu bar works fine. However, it seemed to me that I should be able to reduce page weight (an important consideration considering my target population) by placing it in the general style sheet governing the entire site.
When I place the styles at the beginning of the style sheet the menu doesn't render at all in any of the browsers (IE 6+, Firefox, Opera, Safari, Netscape, etc.) as it conflicts with the general rules governing links that appear later in the style sheet. When I place the styles specific to the Menu bar at the end of the style sheet, then the menu bar renders properly in all browsers except IE 6.
The odd thing is that the only way to ensure that the menu bar works in IE 6 is to keep the menu related styles in the head of each page. This raises problems related to page weight (not an insurmountable consideration if no other solution can be found) but still an issue. Likewise I need to support IE 6, again given the target audience/population. The issue obviously has something to do with specificity, but I am not certain that is the only consideration at work here. I have not tried the !important selector in regard to the menu, as IE 6 seems to only partially support this.
Thanks in advance for any advice or insight that can be provided. Thanks in particular to Martin for his contributions to my earlier question related to this issue.
Steve Webster.
The CSS governing the horizontal menu bar is as follows: (currently the following CSS is embedded in the head of the web page)
<style type="text/css">
/* -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles -- */
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
   these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
     These assume the following widget classes for menu layout (set in a preset)
   .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
    .MenuBarVertical - vertical main bar; all submenus are pull-right.
   You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
    They only apply to horizontal menu bars:
        MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
        MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
        MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
        MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                        and centered in its parent container.
        MenuBarFullwidth - Grows to fill its parent container width.
    In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
   with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
    there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
    background-color:transparent;
   font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                MenuItem, and MenuItemLabel
                                                at a given level all use same definition for ems.
                                                Note that this means the size is also inherited to child submenus,
                                                so use caution in using relative sizes other than
                                                100% on submenu fonts. */
    font-weight: normal;
    font-size: 17px;
    font-style: normal;
    padding:0;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
    display:none;
.MenuBarLeftShrink {
    float: left; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarRightShrink {
    float: right; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarFixedLeft {
    float: left;
    width: 80em;
.MenuBarFixedCentered {
    float: none;
    width: 80em;
    margin-left:auto;
    margin-right:auto;
.MenuBarFixedCentered br {
    clear:both;
    display:block;
.MenuBarFixedCentered .SubMenu br {
    display:none;
.MenuBarFullwidth {
    float: left;
    width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
    padding: 0px 0px 0px 0px;
    margin: 0;     /* Zero out margin on the item containers. The MenuItem is the active hover area.
                For most items, we have to do top or bottom padding or borders only on the MenuItem
                or a child so we keep the entire submenu tiled with items.
                Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
    padding: 10px 10px 10px 4px;
    background-color:#000088;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
    background-repeat:repeat-x;
#MenuBar .MenuItemFirst {
    border-style: none none none none;
#MenuBar .MenuItemLast {
    border-style: none none none none;
#MenuBar .MenuItem .MenuItemLabel{
    text-align:center;
    line-height:1.4em;
    color:#ffffff;
    background-color:transparent;
    padding: 0px 18px 0px 5px;
    width: 10em;
    width:auto;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
    width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
    font-family: Arial, Helvetica, sans-serif;
    font-weight: bold;
    font-size: 15px;
    font-style: normal;
    background-color:#000088;
    padding:0px 2px 0px 0px;
    border-width:0px;
    border-color: #cccccc #cccccc #cccccc #cccccc;
    /* Border styles are overriden by first and last items */
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
    border-style: none;
    padding: 0px;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
    padding-top: 0px;
#MenuBar .SubMenu .MenuItemLast {
    border-style: none none none none;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
    padding-bottom: 10px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
    text-align:left;
    line-height:1em;
    background-color:transparent;
    color:#ffffff;
    padding: 10px 10px 10px 10px;
    width: 240px;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
    background-color: #2E35A3;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
    background-repeat:repeat-x;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #ffffff;
#MenuBar .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #ffffff;
#MenuBar .SubMenu .MenuItemHover {
    background-color:#2E35A3;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #ffffff;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
    background-color: transparent;
   min-width:0%; /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
    border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
    top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
    left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                    and your personal taste.
                   0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                    on MenuItemContainer and MenuItem on the parent
                    menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                    the dropdown with the left of the menu item label.*/
    z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
    top: 0px;
    left:100%;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
    background-color: transparent;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
    top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                vertically 'centered' on its invoking item */
    left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
* all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #ffffff;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #ffffff;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
    margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
/* EndOAWidget_Instance_2141544 */
/* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
</style>
The CSS governing the site generally is reproduced below: (my belief is that it is the a:link, a:visited, a:hover, a:active styles that may be in conflict).
@charset "utf-8";
body {
    font: 100% Verdana, Arial, Helvetica, sans-serif;
   min-height: 0; /* This is necessary to overcome the "haslayout" bugthat is found in Windows 7 in conjuction with IE8. For Moreinformation see: URL -- http://reference.sitepoint.com/css/haslayout.html */
    margin: 0; /* it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
    padding: 0;
    text-align:center; /* This allows for the centering of the container and overcomes a bug inherent in IE 5 */
    color: #000000;
    list-style-image: none;
    background-color: #FCFCFC;
h1,h2,h3,h4,h5,h6 {
color:#000066;
a:link {
    color: #151A96;
    text-decoration: underline;
a:visited {
    text-decoration: underline;
    color: #1B8DCD;
a:hover {
    text-decoration: none;
    color: #F30A0A;
a:active {
    text-decoration: underline;
    color: #151A96;
#container {
    width: 960px;
    margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
    text-align: left; /* this overrides the text-align: center on the body element. */
    background-image:
    url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Midsection %20_960.png);
    background-repeat: repeat-y;
#header {
       padding: 0; /* this padding matches the left alignment of the elementsin the divs that appear beneath it. If an image is used in the #headerinstead of text, you may want to remove the padding. */
        width:960px;
        height:332px;
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Header_960 .png);
        background-repeat:no-repeat;
#header h1 {
    margin-right: 0px; /* zeroing the margin of the last element in the #header div will avoid margin collapse - an unexplainable space between divs. If the div has a border around it, this is not necessary as that also avoids the margin collapse */
    padding: 0; /* using padding instead of margin will allow you to keep the element away from the edges of the div */
    display:none;
#header img {
    display: none;
#Main_nav_contents {
    padding: 0;
    margin-top: 0px;
    height: 39px;
    width: 950px;
    padding-top: 275px;
    padding-left: 39px;
    z-index: 3;
#MenuBarVertical {
    margin-bottom: 50px;
    padding-top: 50px;
    padding-bottom:200px;
    padding-left: 15px;
    padding-right: 15px;
.mainContent_left {
   margin: 0;/* the right margin on this div element creates the columndown the right side of the page - no matter how much content thesidebar1 div contains, the column space will remain. You can removethis margin if you want the #mainContent div's text to fill the#sidebar1 space when the content in #sidebar1 ends. */
    padding-left:30px;
    padding-right:20px; /* remember that padding is the space inside the div box and margin is the space outside the div box */
    width: 600px;
    float: left;
.sidebar_right {
    float: right; /* since this element is floated, a width must be given */
    width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
    margin-top: 30px;
    margin-left:0;
    margin-right:10px;
    font-size:90%;
.mainContent_right {
    margin-left: 10px;
    padding-left:30px;
    padding-right:20px;
    width: 600px;
    float: right;
.sidebar_left {
    float: left; /* since this element is floated, a width must be given */
    width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
    margin-top: 30px;
    margin-left:30px;
    margin-right:0;
    overflow: hidden;
    font-size:90%;
.main_content_centered {
    width: 650px;
    margin-left: 155px;
.main_content_centered_header {
    margin-left: 75px;
.sidebar_textbox {
    margin: 0px;
    width: 260px;
    padding: 2px;
.sidebar_textbox_header {
    width:255px;
    height:58px;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Header.png);
.sidebar_textbox_background_middle {
     width: 255px;
    padding-top: 12px;
    padding-bottom: 10px;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Middle.png);
    background-repeat: repeat-y;
.sidebar_textbox_content {
   /* The width and padding are set as follows to accomodate quirks inbrowser rendering and to ensure that text is contained within thebackground of the text box */
    width: 230px;
    padding-left: 20px;
    padding-right: 40px;
.sidebar_textbox_footer {
    width:255px;
    height:64px;
background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Port rait%20Textbox%20Footer.png);
#issues_menu a:link {
    color: #151A96;
    text-decoration: none;
    font-weight:bold;
#issues_menu a:visited {
    color: #151A96;
    font-weight:bold;
    text-decoration: none;
#issues_menu a:hover {
    color: #F30A0A;
    font-weight:bold;
    font-style: oblique;
    text-decoration: none;
#issues_menu a:active {
    color: #151A96;
    font-weight:bold;
    text-decoration: none;
#archives {
    padding-top: 15px;
    padding-right: 15px;
    padding-bottom: 20px;
    padding-left: 0px;
.landscape_textbox {
    width: 500px;
    margin-right: 0px;
    margin-left: 30px;
    padding-top:35px;
    padding-bottom: 25px;
    font-style: normal;
    font-weight: normal;
.landscape_textbox_hdr {
    width:500px;
    height:38px;
    margin:auto;
    padding:0;
    background-image:
url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Landscape%20Textbox%2 0Header.png);
.landscape_textbox_middle {
    width:auto;
    margin:auto;
    padding-top: 12px;
    padding-bottom: 12px;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/lan dscapte%20Textbox%20Middle.png);
    background-repeat:repeat-y;
.landscape_textbox_content {
    width:450px;
    padding:25px;
.landscape_textbox_ftr {
    width:500px;
    height:44px;
    margin:auto;
    padding:0;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Lan dscape%20Textbox%20Footer.png);
#footer {
    padding: 0; /* this padding matches the left alignment of the elements in the divs that appear above it. */
    width: 960px;
    height: 222px;
    background-image:
    url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Footer%20_ 960.png);
    background-repeat:no-repeat;
#footer p {
   margin: 0px; /* zeroing the margins of the first element in the footerwill avoid the possibility of margin collapse - a space between divs */
    padding:0px; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
    text-align:center;
    margin-left: 50px;
    margin-right: 50px;
    padding: 10px;
    font-size: small;
#footer h5 {
text-align:center;
.fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
    float: right;
    margin-left: 8px;
.fltlft { /* this class can be used to float an element left in your page */
    float: left;
    margin-right: 8px;
.clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
    clear:both;
    height:0;
    font-size: 1px;
    line-height: 0px;
.dropcap {
    display: block;
    float: left;
    line-height: 80%;
    font-size: 250%;
    font-weight: bolder;
    color: #000066;
    padding: .03em .1em 0 0;
.red_arrows {
    list-style-position: outside;
    list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Arrow%20Large.png);
.blue_bullets {
    list-style-position: outside;
    list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Bullet%20Medium%20Fu ll.png);
.attention {
    color: #F30A0A;
    font-size:x-large;
    font-family: Georgia, "Times New Roman", Times, serif;
    font-style: italic;
    font-weight:900;
.attention_small {
    color: #F30A0A;
    font-size:large;
    font-family: Georgia, "Times New Roman", Times, serif;
    font-style: italic;
    font-weight:900;
.table {
    table-layout:fixed;
.blue {
    color: #00F;
#container .mainContent_left p .blue {
    color: #0303A0;

Hi Nancy:
The specific code that I am referring to is the CSS code governing the styling of the spry menu widget that only works in IE 6 if, and only if, it remains in the head of the web page. If removed and placed in a stylesheet, the IE plugins fail to compensate for the IE 6 "gap" bug. As I said, it doesn't make sense to me that, assuming specificity is addressed, that these can not be included in an external style sheet. I am looking for a) an explanation why they must remain embedded in the web page; and 2) any means by which I might be able to export them.
I will reproduce the specific css style (code) below: it should also be visable through reveal source --
Thanks again, Steve Webster.
The CSS governing the horizontal menu bar is as follows: (currently the following CSS is embedded in the head of the web page)
<style type="text/css">
/* -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles -- */
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
   these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
     These assume the following widget classes for menu layout (set in a preset)
   .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
    .MenuBarVertical - vertical main bar; all submenus are pull-right.
   You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
    They only apply to horizontal menu bars:
        MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
        MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
        MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
        MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                        and centered in its parent container.
        MenuBarFullwidth - Grows to fill its parent container width.
    In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
   with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
    there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
    background-color:transparent;
   font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                MenuItem, and MenuItemLabel
                                                at a given level all use same definition for ems.
                                                Note that this means the size is also inherited to child submenus,
                                                so use caution in using relative sizes other than
                                                100% on submenu fonts. */
    font-weight: normal;
    font-size: 17px;
    font-style: normal;
    padding:0;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
    display:none;
.MenuBarLeftShrink {
    float: left; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarRightShrink {
    float: right; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarFixedLeft {
    float: left;
    width: 80em;
.MenuBarFixedCentered {
    float: none;
    width: 80em;
    margin-left:auto;
    margin-right:auto;
.MenuBarFixedCentered br {
    clear:both;
    display:block;
.MenuBarFixedCentered .SubMenu br {
    display:none;
.MenuBarFullwidth {
    float: left;
    width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
    padding: 0px 0px 0px 0px;
    margin: 0;     /* Zero out margin on the item containers. The MenuItem is the active hover area.
                For most items, we have to do top or bottom padding or borders only on the MenuItem
                or a child so we keep the entire submenu tiled with items.
                Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
    padding: 10px 10px 10px 4px;
    background-color:#000088;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
    background-repeat:repeat-x;
#MenuBar .MenuItemFirst {
    border-style: none none none none;
#MenuBar .MenuItemLast {
    border-style: none none none none;
#MenuBar .MenuItem .MenuItemLabel{
    text-align:center;
    line-height:1.4em;
    color:#ffffff;
    background-color:transparent;
    padding: 0px 18px 0px 5px;
    width: 10em;
    width:auto;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
    width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
    font-family: Arial, Helvetica, sans-serif;
    font-weight: bold;
    font-size: 15px;
    font-style: normal;
    background-color:#000088;
    padding:0px 2px 0px 0px;
    border-width:0px;
    border-color: #cccccc #cccccc #cccccc #cccccc;
    /* Border styles are overriden by first and last items */
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
    border-style: none;
    padding: 0px;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
    padding-top: 0px;
#MenuBar .SubMenu .MenuItemLast {
    border-style: none none none none;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
    padding-bottom: 10px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
    text-align:left;
    line-height:1em;
    background-color:transparent;
    color:#ffffff;
    padding: 10px 10px 10px 10px;
    width: 240px;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
    background-color: #2E35A3;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
    background-repeat:repeat-x;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #ffffff;
#MenuBar .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #ffffff;
#MenuBar .SubMenu .MenuItemHover {
    background-color:#2E35A3;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #ffffff;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
    background-color: transparent;
   min-width:0%; /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
    border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
    top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
    left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                    and your personal taste.
                   0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                    on MenuItemContainer and MenuItem on the parent
                    menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                    the dropdown with the left of the menu item label.*/
    z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
    top: 0px;
    left:100%;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
    background-color: transparent;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
    top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                vertically 'centered' on its invoking item */
    left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
* all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #ffffff;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #ffffff;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
    margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
/* EndOAWidget_Instance_2141544 */
/* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
</style>

PowerBook Constant Freeze and Graphics Problems

I have a Powerbook 12" 1.33Ghz Leopard 10.5.2 , I star to work in anything and in a few minutes its freezes and appears a Kernel Panic or de backend System Text start to output reports overwriting the last graphic image.. here a picture..
http://cyberkiko3d.com/down/photo.jpg
I remove the memory card, and stills hapening..
I want to know is this is just a kernel problem that it stops formating or is a hardware problem involving the LogicBoard or Graphic Card..
Thanks

I guess memory can fail over time. I just haven't experienced it myself. (Or heard of it, but it is a piece of hardware).
You can test your RAM by either using your system installation / restore discs (the original grey discs that came with your machine) and pop in Disc 1 and reboot the computer holding down the OPTION key and from there, you will get the choice for Apple Hardware Test, which you can use to do a basic test of your RAM.
Second, if you ever signed up for AppleCare and got the TechTool Deluxe disc that comes with it, you can use that too for a more extensive RAM test. Just be careful not to use it to diagnose anything with your hard drive. Just use it for RAM. (Be warned, as their is an incompatibility with Tiger that can ruin your drive. Though I see you have Leopard, so don't even know if it works).
The other test you can do, as suggested by many of the top users in these forums is "Rember" which tests your RAM and should let you know what's going on. I used it once after using it as a suggestion (taking someone else's suggestion and using it for my own testing) and it showed the second module of memory that I bought on eBay--the one that doesn't cause kernel panics--to pass.
You can find that here: [http://www.kelleycomputing.net:16080/rember>
Also, when you get your RAM replacement, I highly recommend getting Apple OEM suppliers such as modules from Samsung, Hynix, or Micron (manufactured by Crucial). They should be trouble free.
I say should because the Samsung 1GB module I bought for my 12-inch PowerBook from OtherWorld Computing has worked flawlessly for almost two years now. The one I was talking about previously, that crashed my 15-inch machine? A Samsung one as well. So, it is true that these Aluminum PowerBook G4s are picky about the RAM installed.
Message was edited by: Pismo 900
I forgot to ask you... what brand RAM do you have installed? (If you know and it is labeled).

RE: freezing and resetting problems when syncing a large music library

Hi there,
I got a new ipod classic 160gb for christmas. I updated the firmware to 1.0.3 and synced it for the first time. When I tried to play any music it locked up and went into a loop of resetting itself which I could only break by forcing the ipod into disk mode.
I restored the ipod and tried again syncing the music in chunks. This worked until the ipod was about 50% full then it started to freeze and reset again. I took this ipod back to the store but the new one had the exact same problem!
Through a lot of trial and error I have managed to get the ipod working with only part of my library synced. By syncing music a few albums at a time I have managed to get about 86gb (of 120gb) onto it, but surely this is not how it is supposed to be! I have a dual boot system and have the same problems using windows XP or vista.
I know that I'm not the only person experiencing resetting problems with the ipod classic. Are the users who are experiencing these endless resetting problems with the ipod classic those who have large music libraries (i.e over 80gb)? Can the ipod classic simply not handle the large volumes of music it was designed to hold?
The only features I was looking forward to in the new ipod were a) larger capacity hard drive and b) the ability to organise playlists into folders on the ipod for easier browsing. As it stands I cannot sync my full library and navigating through my playlists is so slow it is hardly worth bothering. I never had a minutes trouble with my 5th gen.
Have I been unlucky and the ipod classics I have recieved have been duds? In which case should I arrange another replacement? Or is this typical of the ipod classic user experience when the user has a large music library and many playlists? Should I await a firmware update that might remedy my problems?
Lastly am I doing something wrong? Any help or workarounds would be gratefully appreciated.

best thing to do is use Playlist and Smart Playliss to fill your iPod. Just so you know, since your post seemed to indicate you thought the playlists have to be tailored to what is already on the iPod, when you sync to playlists, any songs needed for those playlists are automatically moved onto the iPod. And any songs NOT in the playlists get removed.
Patrick

XRPM missing ivew and rendering problem

Hi, guys:
I am working with a RKT 2008 system and facing some XRPM issues. Would any of you be so kind to give me some comments or hints if you got?
Iview 'task' is missing.
Rendering problem happens whereever a chart or graphic is supposed to be created.
Thanks very much in advance and kind regards,
Robert

I see you followed Jerry's advice to post over here, and haven't got any responces, so I'll at least try to get a little more information into the discussion.
Since the document prints to pdf correctly, but not to the actual printer, it seems likely that it is a print driver issue. In the Numbers discussion on the issue, the original person with the issue was using a HP printer with a postscript driver. Since the HP support site was not very clear about whether a driver for that printer on Mavericks even existed, and the recommendation for a generic driver was for a PCL driver, not postscript, I suspect that they were not using a recommended configuration. It would probably be helpful to know the details about your printer and print driver.
Do you have access to more than one printer to test this on?
The new versions of Numbers and Pages are doing something strange in terms of how they copy tables to the system clipboard; the pdf version is no longer available, only bitmap images. Print to pdf, however seems to still get the pdf data. I don't think this should have anything to do with the data getting to the print driver, but it does seem consistent with your results.

Issues with freezes and HD problem from DU

I could write multiple pages about all the symptoms and everything that happened, but knowing that many won't read it anyway here is a short story of what happened to my MBP. Please help me out if you can!
Lately my MCP13 has been freezing and the only way was to get it out was shutting it off and turning it on. Once I couldn't boot it. Of course, I tried everything but the only solution was to boot it from the install disk and run disk utility. Many times the computer froze as soon as I launched DU or it could not find my MacintoshHD. After three times of rebooting, it detected the MacintoshHD and said that it is corrupt (number of volumes incorrect xxxxxy instead of xxxxxx). I repaired it and it seemed fine after one more check. Then I rebooted the computer and ran DU again. It said that the files were corrupt (same problem), I turned off the computer, launched it from the disk again and repaired it. Once I turn it on from MacHD I run DU again and it says that files are corrupt again.
Anything had similar issues? What should I do besides taking it to the AppleStore?
Thanks for reading this,

If it's under warranty, Apple will do it. If not, search the Apple Support site for the instructions for your model. Example:
MacBook Pro (13-inch, Mid 2009) - Hard Drive Replacement Instructions

MSI twin frozr II freeze and glitch problem.

Hi everyone,
I have a very annoying problem with my card. Whenever I play BF3 with a total random time I get some green glitches and the display freeze (see the attached screen).
Normally I get right back on windows with this little popup "display driver stopped answer and recovery successful". But now it just freeze and I have to do a hard reboot...
Here is my config:
-I7 2600k
-Asus p8p67 pro rev 3.1
-2x4Gb Ripjaws X
-OCZ 850w 80gold+
-MSI twin frozr II GTX 580 with latest drivers
-Win 7 64b
I've already look around google, I'm not alone but it seems there is no real solution. It's really sad to have this kind of prob with that expensive card... without any solution.
Some help would be very nice.
Thanks for any help.

Quote from: messem on 08-November-11, 00:11:28
I've never flash my vbios.
But after downloading and trying to flash it with the link you provide nvflash says that my current version is: 70.10.20.00.01 and the one I downloaded is 70.10.17.00.01.
So am I already in the lastest ?
Thanks
this number is not vBIOS ID, so in all cases it will remain the same.

Random Freezing and booting problems

My MBP (4 years old) randomly freezes and the only button works is the power button. It has booting problems as well
Done already
clean install of snow leopard
PRAM reset
Safe Boot (boots again after using safe boot but still freezes after a couple of minutes)
AHT hardware test with no result
Still freezes after 1 to 15 minutes.
Anything else I cab do?

Wow my first time i use this forum and a fast reply.
Unfortunately not at home at the moment so can not give exact answers.
When my mac book freezes the fan still works, keyboard and touch pad do not work anymore. I don't think caps lock light works but not sure.
Have original ram and a retail SL disc.
When I have booting problems I can see the spinning wheel and after that only blue screen. If I power off and start in safe mode and then restart again mbp will boot again for 2,3 or 4 times and then stop booting again but still freezing after a couple of minutes.
The funny thing with the booting is after I see the blue screen I can still connect from my mac mini and browse my MBP from my mac mini.(screen sharing does not work though).
And do not know what smart status is
But thank you for your quick reply.

Power Manager and LCD Brightness, System Freezes, and other Problems

I have a brand new X200 with PM 1.54. At first everything was working great. Over the past few days I've noticed a few things:
1. When running on battaries, the screen brightness changes about every 10 seconds even though the profile I'm using has that feature turned off.
2. After running the computer for about 1/2 hr, suddenly the PM shows a dramatic reduction in amount of time left on my battery which coinsides with:
a) fan consantly running; AND
b) about 10 minuntes later my entire system freezes and I have to push the power button to force a reboot.
Any ideas what's wrong?

Since your Mac Pro is new, you would do well to contact Apple about this problem while the warranty is still in effect.

Freezing and Restore Problems

I've been having major problems with my iPod for the past few days. It continuously froze and made strange click-whir sounds so I restored it. I put my files back onto the iPod.
Now, whenever it freezes and I reset it, it acts like it has been restored. I have to readjust my settings and it says that none of my music files are loaded. But when I plug it into my computer, my computer says that all music files are intact. I unplug it from my computer and everything is fine until the next time it freezes.
I've heard a lot of complaints about freezing, but from what I've read, I haven't found anything that seems to match what is wrong with my iPod. I don't have the latest iTunes version so that can't be my problem. Does anyone know how I can make it stop freezing or, at least, keep it from appearing like it's been restored?

i got it out of recovery mode and booted it up as per normal.
It only did it once today but then I did a hard reset on it and it hasn't occured again!!
Well the nearest apple store is an hour away
thankz guys ( Just hope apple posts new iTunes with bug fixes!)
if any1 has any solutions I would be happy to try it out
thankz

Often hanging, freezing and overheat problem

hi, i have a laptop of model no presario cq62 262tu which gets freezes and hanging often from a week , it is so painfull that i am unable to work after 20 minutes , pls help me , it gets overheated also , if i retain the laptop unoperational standmode , it automatically recovers but after 20 minutes it also gets the same problem which i have mentioned you
thanking you
hope for your support

Dear Roh32173 -
I understand that your computer is overheating and causing it to freeze. Please see the HP support document HP Notebook PCs - Reducing heat inside the PC to prevent overheating to troubleshoot and find solutions for the overheating problem.
You should also look at this HP support document entitled HP PCs - Computer Locks Up or Freezes (Windows 7) for other possible solutions.
Sincerely,
dhtp
DH
I work on behalf of HP.
Please click "KUDOS Thumbs Up" if I have helped you, and click "Accept as Solution" if your problem is solved. Thanks for the feedback!

Final Cut Pro - Freeze and Display Problem

When I try to render something in Final Cut, it renders for a few minutes but then the system freezes. I can still vaguely make out a dock and menu bar and final cut windows, but it's all pixelated and distorted. There are some black I can still move the mouse around (which is also distorted) but nothing happens when i click stuff. Has anyone else experienced this? Could this be a problem with my graphics card? (I bought my iMac new November 2007)
I've got FCS 2 and have installed all of the updates.

Is this a new, recent problem?
Or has this been the case since you installed it on your iMac?

Corrupted video and rendering problems

Before I upgraded the software (FCP 5.0.3 to 5.0.4, and the latest OS X update) I could capture and export movies with no problems. Using the “File>Export>Quicktime Movie” option set to “Use current settings” provides the disastrous results of digital garbage flashing on the screen like psychedelic Lego blocks every couple of seconds at random intervals. They appear at different points with every export. It’s like it’s taking an I-frame from a Jackson Pollack painting. I tried using the following codecs (Sorry if I’m using the wrong terminology, I’m a PC head making my first steps into the Mac universe): Apple Intermediate Codec, DV NTSC 48 KHz (the project’s setting), DV50 NTSC 48 KHz, MPEG IMX 8-bit NTSC – 50 MB/s – 48KHz and the Uncompressed 8-bit NTSC 48 KHz all with similar hideous results. So why does the video look so bad?
Also when I try to render my files the progress bar flashes on the screen for about a second and then goes away, leaving my timeline with the same red bar across the top (AKA unrendered). Are these two problems related?
I hope that is a detailed enough description of my plight to inspire an answer. Thanks in advance.

Yes, I have tried it in a new sequence and a new project but nothing has changed. What I am trying to do is take our catalog of "How to" videos from the miniDV tapes and create DVDs using DVDSP4 since nobody buys VHS anymore. All I'm doing is capturing the 25+ minute project and trimming off the wasted spaces at the beginning and the end. Two cuts, that's it. I'm not reassembing anything and this is becoming a bigger project than the original editing. I had captured the original video I am currently working with before the OS upgrade with no problems and it looks fine on anything I use to view the Quicktime file with. But when I export to anything besides Compressor all I get is junk when Compressor decides not to give ma a "Quicktime Error: 0". What is that about? Anyone?
Also, the tutorial on preview rendering is good and I learned quite a bit. Unfortunately nothing worked on solving my problem. The progress bar still flashes on the screen and when it hits 0% completed it disappears leaving everything unrendered. Grrrr.
Thanks again.

Freezing and rendering problems

Similar Messages

Maybe you are looking for