Pram reset question

hi everyone,
a co worker of mine decided it would be a good idea to reset the PRAM on a macbook here in our office (while I wasn't there, of course), because he said the charging icon just kept saying it was calculating even though the battery was full - anyway, he tried to do a PRAM reset and apparently held down apple/option/R/P and then held the power button down, to which he said the "breathing light" on the front of the macbook started blinking a lot and there was a noise from the speakers, he let go and the machine booted ok. I did a proper pram reset on the machine and repaired permissions and the battery charging/etc. is reading correct now... so my only question is, will this affect the machine? Is there anything that could have been messed up by this, or should it be ok because it was just a wrong button config? I can't see anything wrong with the machine, but I just want to make sure.
Being in IT is fun. ;P
Just wondering... help is appreciated, thanks.

thanks Troy, I think it's ok, everything seems to be ok, and the PRAM seems to be holding all info ok, like if I shut it down it remembers the previous volume settings, etc. so I'm sure it's fine. Thanks for the help, it means a lot. I was just worried because of the whole "weird noise and the light blinking a lot" thing... mostly I was worried that the RAM could have been damaged because the power was held down while the PRAM reset keys were held down, that didn't sound good to me, but these machines are pretty resilient, so I think I'm ok.

Similar Messages

  • Flashing question mark on start up -Pram reset worked now it's back and pram doesn't work

    So the other half has crashed my mid 2012 macbook pro twice in two days (watching youtube). First time I managed to get passed the flashing question mark folder icon using pram reset now this doesn't work and it just goes to that icon. Hard drive is missing in. utility so can't whipe that either
    any suggestions on what has failed, it's only 1.5 years old so I'm really disappointed

    A flashing question mark or globe appears when you start your Mac
    Question (?) Mark, Blinking Folder, or Gray Screen at Startup
    These are related but not identical issues. Their causes are outlined in Intel-based Mac- Startup sequence and error codes, symbols. Solutions may be found in:
    A flashing question mark appears when you start your Mac
    Mac OS X- Gray screen appears during startup
    In most cases the problems may be caused by one or more of these:
    a. Problem with the computer's PRAM - See Resetting your Mac's PRAM and NVRAM.
    b. Boot drive's directory has been corrupted - Repair with Disk Utility.
    c. Critical system files are damaged or deleted - Reinstall OS X.
    d. The disk drive is physically non-functional - Replace the hard drive.
    Note that the information I have provided is what Apple recommends, If other users suggest different solutions than found here, then be sure what they recommend does not impact on your warranty, if any, or ability to get continuing Apple service.
    Please don't start removing drives or changing cables unless you know what you are doing and have exhausted other non-invasive alternatives outlined here. If you perform any work yourself that is unapproved by Apple, then you will void any warranty you may have and lose all further Apple Support.
    Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    The main difference if you are using Lion or Mountain Lion is that you must first boot from the Recovery HD. Simply boot from the Recovery HD to perform the above.
    Reinstall Snow Leopard Without Erasing The drive
    1. Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Reinstall Snow Leopard
    If the drive is OK then quit DU and return to the installer.  Proceed with reinstalling OS X.  Note that the Snow Leopard installer will not erase your drive or disturb your files.  After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
    Download and install Mac OS X 10.6.8 Update Combo v1.1.
    Reinstalling Lion/Mountain Lion Without Erasing The Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

  • Macbook Pro Retina over 200F 5-10 fps in games (after SMC/PRAM Reset)

    I have struggled with this for too long now.
    I have read every single thread I can find about the issue and tried both complete reinstalled of Bootcamp, SMC reset, PRAM Reset, EFI updates, etc.
    When I first got the Macbook, I could run our game development setup in around 60-80 fps.
    I use the labtop for game development in Bootcamp (Windows 7 64)
    Currently im not able to get more than 10 FPS. And it runs very bad - it runs in 30 fps the first second, the next its a 5, and then it goes up again.
    Even though nothing happens on screen.
    When i launch a game the GPU and CPU is over 200F in heat.
    And thats with all the fans on constantly.
    Im very worried here - Im travelling next week where I need this machine to be able to work.
    What should I do? Is it broken? Should I get a new one, or will the same thing happen?
    Thanks a lot in advance guys!

    I would strongly suggest you take it into Apple Store to get it looked at.
    In the mean time I can only suggest changing power management to see if this fixes it for now:
    You can change the way your computer hybernates from hybernatemode 3 to 0.
    3 = RAM is powered on while sleeping, but RAM contents are also written to disk before sleeping. In the event of total power loss, the system enters hibernation mode automatically. The downside to this mode is that it is very slow. The upside is that it is very unlikely that you will lose any unsaved work should your mbp lose power.
    0 = RAM powered on while sleeping, safe sleep disabled, and super-fast wake. The downside to this mode is that it does not save any of your work, should your mbp lose power, and you would have to remember to manually save before putting to sleep. The upside is that your computer would sleep & wake up in around 2 seconds.
    Go to Terminal & type:
    pmset -g | grep hibernatemode
    That should give you a result of 3.
    To change it to 0 type:
    sudo pmset -a hibernatemode 0
    It might ask you to enter your password.
    Then delete the old sleepimage file:
    cd /var/vm
    sudo rm sleepimage
    Just remember, saving will have to be done manually by you,

  • OS wont start up, PRAM reset not working :(

    Hey all,
    I came home one day to my dual 1.8 power mac frozen and fans
    blowing on high. I shut it down, and when starting up...I just got thegray screen with the apple logo, nothing else. I read through the support advice and after multiple combinations of SMU, PRAM, NVRAM
    resets, I was able to FINALLY get OS up and running. As soon as I shut
    it down, the start up issue began once again. After spending 20 min on
    the phone with tech support, learning about holding down the power
    button and waiting for the high pitch tone,resetting the PRAM( 4 - 5x)successfully (but only after many failed attempts) with the option-command-p-r key hold and then performing an archive and reinstall...it all happened again after using the computer for 1/2 the day.
    Except now (as before) I cant seem to reset the PRAM no matter when I time the command-option-P-R or in what sequence I do it in. Ive plugged/unlplugged, waited to hold/immeditately held the keys down, pushed the SMU
    button on the board/didnt push the button, opened firmware page and
    reset all and tried it from there...nothing reproduces the multiple
    chimes and PRAM reset I was able to do the 2 previous times this
    occured. I even went out and bought a new battery for the
    board(installed correctly)and nothing is helping. When holding the
    command optionp r keys, I dont even get the grey screen with the apple. If I leave the keyboard alone and perform all other possible resets...the gray apple appears, no other graphics show up, and definitely never get the
    spinning gear...just a steady increase in fan speed the longer I let it
    sit. It's like the PRAM is not able to reset, and when it
    does, all is good. The timing of the push and hold on the keys seemed
    to be crucial the last 2 times, some time after the chime, but before
    thegray screen. The tech associate told me to push and hold them immediately...that has never worked.
    Any thoughts anyone? Is there another way to reset the PRAM? Any help or advice would much appreciated.

    Alright. Here's the update.
    The computer continued to give me startup issues. Unfortunately,
    the logic board pressing must have been coincidental. And an archive install of 10.4 didnt help. The machine is
    definitely behaving erratically. It starts up when it decides, I seems
    to cycle through few and many (50) startup attempts . I recently backed
    up all my data, erased my drive, and did a clean reinstall. my last
    hope that this is a software issue was about to be
    tested. And sure enough, the computer worked well for 24
    hours.When I was about done updating OS 10.39 with 2007-2008 security
    update when suddenly...frozen again. I've read a few horror stories about this update so I wont make that mistake again.
    It then took me close to 100 attempts to get the **** thing to boot, but I did...attempted
    to reinstall windows and during the process or loading disc 2, the
    machine just went to sleep. Never has this occured. I had the fans out
    of the machine and felt the problem may be temperature related. SO now im
    back to trying to start it up again. Anyone know how to startup to CD
    from open firmware? Besides the usual mac-boot, or holding down C at startup? Is this sounding more like a power supply issue to anyone? Thanks. Gonna try and part this thing out if I cant narrow down the problem.
    I have already given up on this machine and just bought at macbook pro from Feb 08 on amazon. Im definitely getting apple care. I was so close to going back to PC. Grrrr.

  • Hi I want to change your e-secret questions because I forgot the answers I have tried sending reset questions on my mail and I have not received mail

    hi I want to change your e-secret questions because I forgot the answers I have tried sending reset questions on my mail and I have not received mail
    New mail that I want is [email protected]
    Alternative to the Old one

    From  King Penguin
    If you have a rescue email address set up on your account then you can try going to https://appleid.apple.com/ and click 'Manage your Apple ID' on the right-hand side of that page and log into your account. Then click on 'Password and Security' on the left-hand side of that page and on the right-hand side you might see an option to send security question reset info to your rescue email address.
    If you don't have a rescue email address set up then go to Express Lane  and select 'iTunes' from the list of 'products' in the middle of the screen.
    Then select 'iTunes Store', and on the next screen select 'Account Management'
    Next choose 'iTunes Store Account Questions' or 'iTunes Store account security' (it appears to vary by country) and fill in that you'd like your security questions/answers reset.
    You should get an email reply within about 24 hours (and check your Spam folder as well as your Inbox)

  • Help with BBOD!  Can't seem to get to the bottom of it.  Have tried SMC reset, PRAM reset, reinstall of Mavericks, Carbon copy clone, checked my CPU, Memory is 500GB and I'm only using 250GB thereabouts.

    Here's what I've tried;
    SMC reset
    Pram reset
    Looked at activity monitor - mostly seems OK aside from a kernel task taking up memory (approx 460MB) but CPU is around 96% idle.
    Fan seems to be running constantly - heats up noticeably when I close the MBP
    Despite a re-install of Mavericks, MBP is running frustratingly slow.  Just typing is enough to bring on the beach ball.
    Have backed up everything, reinstalled from a clone, checked through Apple Hardware test and carried out a Verify Disk Permission - nothing was reported, erased the drive and set up again - problem still stands.
    Memory is running at 3.43 GB without anything really running bar Safari.
    A little loath to install SMC fan control without knowing what's wrong.
    Checked software updates.
    Can anyone tell me what the matter is?  Does this have a fix?
    Have been reading up various posts but to no avail so have resorted to posting myself.
    Does this sound familiar to anyone?
    Many, many thanks
    Roque

    1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
    2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
    There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
    3. Below are instructions to run a UNIX shell script, a type of program. All it does is to collect information about the state of the computer. That information goes nowhere unless you choose to share it. However, you should be cautious about running any kind of program (not just a shell script) at the request of a stranger. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them. Ask for other options.
    Here's a summary of what you need to do, if you choose to proceed:
    ☞ Copy a line of text in this window to the Clipboard.
    ☞ Paste into the window of another application.
    ☞ Wait for the test to run. It usually takes a few minutes.
    ☞ Paste the results, which will have been copied automatically, back into a reply on this page.
    The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
    4. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
    5. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
    6. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
    Triple-click anywhere in the line of text below on this page to select it:
    PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts 51 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports 'com.autodesk.AutoCad com.evenflow.dropbox com.google.GoogleDrive' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 ` route -n get default|awk '/e:/{print $2}' ` 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^\([0-9]+\) /,"");n=$0;getline;} $NF=="'${p[45]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n\t(%s)\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}')printf("%s (UID %s) is using %s '${p[$2]}'",$0,u,q);} ';};s=(' /^ *$|CSConfigDot/d;s/^ */   /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/\/Users\/[^/]+/~/g ' ' s/^ +//;5p;6p;8p;12p;' ' {sub(/^ +/,"")};NR==6;NR==13&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: [^EO]|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ s/ *:$//;x;s/\n//;/Apple|Genesy|Intel|SMSC/d;s/\n.*//;/\)/p;};/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;} ' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/:/;END { if(NR<100)print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { $4="";gsub("  "," ");gsub(/:[0-9:a-f]{14}/,"");} { print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}')print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR==2'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' ' s/^.{52}//;s/ .+//p ' ' /Launch[AD].+\.plist$/;END{if(NR<100)print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$/ { print $3;} ' '/\.(framew|lproj)/d;/plist:|:.+(M.+exec|scrip)/s/:[^:]+//p' '/root/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/;END{if(NR<100)print "/System/"};' '/^\/usr\/lib\/.+dylib$/p' '/\/etc\/(auto_m|hosts[^.]|peri)/s/^\.\/[^/]+//p' ' /\/(Contents\/.+\/Contents|Frameworks)\//d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| ","||kMDItem'${p[35]}'=");sub("^.."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[9]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/ { next;} /%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a) print "CPU: "a;if(b) print "I/O: "b;if(c) print "Net: "c" (KiB/s)";if(d) print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' /lR/ { if($2<='${p[25]}')print $2;} ' ' BEGIN { FS=":";} $3~/(sh|ng|ic)$/ { n=split($3,a,".");sub(/_2.+/,"",a[n-1]);b=b"\n"$2" "a[n-1]" "a[n]" "$1;c=c$1;} END { d="sort|tail -n'${p[38]}'";print b|d;close(d);if(c)print("\n\t* Code injection");} ' ' NR!=4{next} {$NF/=10240} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L) f=f"\n   "$0;} END { F=FILENAME;if(!F) exit;if(!f) f="\n   [N/A]";"file -b "F|getline T;if(T!~/^(A.+ E.+ text$|POSIX sh.+ text ex)/) F=F" ("T")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n   ...and %s more line(s)\n",l-L);} ' ' BEGIN{FS="= "} /Path/{print $2} ' ' /^ +B/{ s/.+= |(-[0-9]+)?\.s.+//g;p;} ' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' /:/{$0="'"${p[28]}"'"};1;' '/ en/!s/\.//p' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil PlistBuddy whoami cksum kextstat launchctl sudo\ launchctl crontab 'sudo defaults read' stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' defaults\ read scutil sudo\ dtrace sudo\ profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup mdutil );c2=(com.apple.loginwindow\ LoginHook '-c Print /L*/P*/loginw*' '-c Print L*/P*/*loginit*' '-c Print L*/Saf*/*/E*.plist' '~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 \)' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' '-c Print\ :'${p[35]}' 2>&1' '-c Print\ :Label 2>&1' '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status '-F bsd -k Sender kernel -k Message Req "Beac|caug|dead[^bl]|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA\(|pagin|proc: t|Roamed|rror|ssert|Thrott|timed? ?o|WARN" -k Message Rne "Goog|ksadm|SMC:" -o -k Sender fseventsd -k Message Req "SL"' '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/*/*.{BS,Bas,Es,OSXU,Rem}*.bom' '{/,}L*/Lo*/Diag* -type f \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true \) -execdir stat -f:%Sc:%N -t%F {} \;' '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo}* -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto_master,{cron,fs}tab,hosts,{launchd,sysctl}.conf} /usr/local/etc/periodic/*/* .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l -s\ / );N1=${#c2[@]};for j in {0..8};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n 'syscall::'${p[33+j]}':return {@out[execname,uid]=sum(arg0)} tick-10sec {trunc(@out,1);exit(0)}'";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents launchd Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP RSSI Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear;};for i in 0 1;do eval ' A'$((1+i))'() { v=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};A'$((3+i))'() { v=` while read i;do eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "$v" ]];};A'$((5+i))'() { v=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "$v" ]];};';done;A7(){ v=$((`date +%s`-v[3]));};B2(){ v[$1]="$v";};for i in 0 1;do eval ' B'$i'() { v=;((v['$((i+1))']==0))||{ v=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v=` paste -d: <(echo "${v[$1]}") <(echo "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v=`grep -Fv "${v[$1]}"<<<"$v"`;};C0(){ test "$v"&&echo "$_";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "$s"<<<"$v"`&&C1 1 $1;};for i in 1 2;do for j in 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;A0;{ A2 0 $((N1+1)) 2;C0;A1 0 $N1 1;C0;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D22 0 $((N1+4)) 5 4;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 14 12 14;D22 6 36 13 15;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D22 11 17 17 20;for i in 0 1;do D22 28 $((N2+i)) 45 $((N4+i));done;};D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A3 14 6 32 0;B4 0 5 11;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A3 14 7 32 6;B4 0 7 11;B3 4 0 22;A3 14 6 32 0;B4 0 8 11;B5 7 8;B1&&{ A2 19 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;A2 4 20 21;B7 6;B2 9;A4 14 7 52 9;B2 10;B6 9 10 4;C3 25;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;D23 24 24 32 31;D13 25 37 32 33;A1 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D13 21 0 32 19;D13 10 42 32 40;D22 29 35 46 39;};D23 14 1 48 42;D12 34 43 53 44;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 26 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;D22 32 31 43 38;D23 20 42 32 41;D23 14 2 48 43;D13 4 5 32 1;D22 4 4 50 0;D13 14 3 49 5;D23 22 9 37 7;A7;C2 2;} 2>/dev/null|pbcopy;exit 2>&-  
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    7. Launch the built-in Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
    8. If you see an error message in the Terminal window such as "syntax error," enter
    exec bash
    and press return. Then paste the script again.
    9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
    If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
    10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
    [Process completed]
    to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report the results. No harm will be done.
    11. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
    At the top of the results, there will be a line that begins with "Model Identifier." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
    If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
    12. When you post the results, you might see the message, "You have included content in your post that is not permitted." It means that the forum software has misidentified something in the post as a violation of the rules. If that happens, please post the test results on Pastebin, then post a link here to the page you created.
    Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
    Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

  • Could a SMC or PRAM Reset Affect a Superdrive's CD and DVD Read/Write?

    Hi. Would a SMC or PRAM reset make the Superdrive read CD and DVDs better (it mounts CD-RWs and DVD+RWs which is usually labels as untitled DVD but it can't seem to mount original disks that are in good condition like: Snow Leopard DVDs that came with this iMac, Grand Theft Auto IV, Spellforce 2: Shadow Wars)? Or SMS and PRAM resets are not related to Superdrive?
    Thank you in advance.
    God bless.

    The SMCreset does affect the superdrive but your condidion may be from dust/dirt in the DVD on the lens system. Mine is real sensitive to dirt and smudges on the actual DVD but occasional lens cleaning helps. You can get DVD lens cleaners (with the tiny brushes on the disk) from most vendors that carry the media.

  • HT1379 PRAM reset not working as it is described in the Apple Help

    I tried the reset several times but there is never a second start up sound! I really tried specifically holding command - option (alt)- and P and R-before the grey secreen came up--- no second start up sound. Any clue? This is an IMAC ... I was given the advice to do the reset and NVRAM and PRAM reset as I have severe problems with my intelsat 27 inch  IMAC - it loses the WLAN connection all the time. is really slow. loses passwords in the keychain all the time and I have 10 days left for the apple protection plan and I am getting pretty annoyed with all the instructions that are not even working... any advice?

    The heavy computer and as I am having bluetooth troubles as well as I starting to think I did something wrong. Issue of PRAM restart was solved by fixing the bluetooth connection to the keyboard that happens all the time so I paired it again (for the 100th time), But you are right - I am going there tomorrow. This is taking too much time and if it is my fault I am getting rid of this IMAC for good. No internet on a stable level, no bluetooth connection on a stable level, passwords getting lost... if this is MAC OS 1.6 - I am saying good bye to Apple. 10.8 is not guaranteed to work for some of important  programs... so updating is not an option for me at the moment. Thanks for kicking me!

  • Display problem fixed with PRAM reset????

    My 1.5G 15" Powerbook G4 had a weird fuzzy messed up display when started today. Shutdown and restart didn't help. I read in Support a video problem might need a PRAM reset. So I held down the Command-Option-P-R keys during restart and display looked fine. Might just be a coincidence so I'm wondering if this could have helped the problem. If so does it need new internal batteries? Can they be replaced by me? Are there instructions somewhere? Are there two batteries called System and Backup?
    Phil

    Hi, Phil. Some display settings are stored in PRAM, and resetting PRAM restores them to their defaults. There are some other settings that can affect the display's appearance (notably in Universal Access) that may not be wiped away by resetting PRAM, but evidently your problem was traceable to something that had been stored in PRAM — probably a reduced resolution setting.
    Unless you have some other indication that one of your PB's batteries — which are commonly called the main battery and the internal backup battery — is bad, there's no need to replace them.

  • After a PRAM reset my MBP 1,1 display is split into 4 parts each displaying the same image. What is causing this and how can I fix it?

    After resetting the PRAM/NVRAM (control, option, P, R) on my Macbook Pro 1,1 (2007) running 10.6.8 The screen is now split into 4 parts, each displaying the same thing. The screen immediately appears this way at the first grey screen, however if I do another NVRAM reset, upon restart after the second startup chime, the screen is normal but once it gets to a certain point around thetime the cog stops spinning, the screen flickers, turns blue and splits into four again.
    Another thing is when I tried using the Apple Hardware Test I couldn't read the instructions as the resolution was too small, but once I restarted and change my display resolution in System Preferences, the resolution was readable in AHT. I assumed the System Settings were loading when the OS had booted and that AHT runs without any of these settings (if that makes sense?)
    I've not used any third party utilites and everything working fine except for some battery issues which are gone now (the reason I tried the PRAM reset)
    Any help would be much appreciated

    Reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.
    *Press and hold Shift and left-click the Reload button.
    *Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
    *Press "Command + Shift + R" (MAC)
    Clear the cache and the cookies from sites that cause problems.
    "Clear the Cache":
    *Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
    "Remove Cookies" from sites causing problems:
    *Firefox/Tools > Options > Privacy > Cookies: "Show Cookies"
    Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
    *Do NOT click the Reset button on the Safe Mode start window or otherwise make changes.
    *https://support.mozilla.org/kb/Safe+Mode
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

  • Migrated to ML from OS/X 10.6.8 on an iMAC 24'' (2009). Now system starts up in verbose mode and holds on the root(!) prompt. PRAM reset doesn't solve the problem

    This is really buggy, because anybody could enter the system as "root" after switching on the system.
    A PRAM reset works only for the actual boot; after a cold start the system holds again on root prompt.

    If you've tried everything else there's always the SMC reset:
    http://support.apple.com/kb/HT3964

  • Mac Mini won't boot after PRAM reset

    My mac mini has been running very slow, VERY VERY SLOW, then it would seem it would catch up with itself and run fine for a few minutes, then slow down again. It got to the point where I would have to do hard resets, but it still wouldn't work all that great. So I read on here to do a PRAM reset, which I did by holding down controloption+PR, and i got a gray screen with a status bar. But now the mac won't even boot up, even when I try safe mode. I turn it on, and i hear the start up tone, and get to the gray screen with status bar, but then it just shuts off. Does anyone have any suggestions?
    Message was edited by: akiemele

    From your user guide:
    1 Disconnect all external devices from your Mac mini, except the keyboard and mouse.
    If you have an Ethernet cable connected, disconnect it.
    2 Restart your Mac mini while holding down the D key.
    3 When the Apple Hardware Test chooser screen appears, select the language you want
    to use.
    4 Press the Return key or click the right arrow button.
    5 When the Apple Hardware Test main screen appears (after about 45 seconds), follow
    the onscreen instructions.
    6 If Apple Hardware Test detects a problem, it displays an error code. Make a note of the
    error code before pursuing support options. If Apple Hardware Test doesn’t detect a
    hardware failure, the problem may be software-related.
    If this procedure doesn’t work, you can insert the Applications Install DVD that came
    with your Mac mini to use Apple Hardware Test. For more information, see the Apple
    Hardware Test Read Me file on the Applications Install DVD.
    When prompted, choose the extended test.

  • I have just recently lost use of 2 USB ports and my isight camera.  I have an isight G5 imac that has been working great.  I have rebooted, reloaded my OS, and tried PRAM reset.  I can use my keyboard, but not other peripherals.  Any ideas on diagnostics?

    I have just recently lost use of 2 USB ports and my isight camera.  My keyboard works fine, but there is not any indication of connections when probing USB in "About this MAC".  I have rebooted, executed a PRAM reset, and reloaded my OS, but to no avail I am out 2 of my 3 USB ports.  I don't know how to diagnose the issue.  Any ideas?
    --kevinfromflagstaff

    Well, if you've tried different USB cords and devices and have reset your PRAM:
    http://support.apple.com/kb/HT1379
    And SMC:
    http://support.apple.com/kb/HT3964
    I'd say your USB ports are shot - since they are an integral part of the logic board, replacing it will most likely be expensive. I'd still go for a definitive diagnosis at the Genius Bar.

  • Keep receiving "USB Over Current Notices" since updating to OSX 10.6.8. I have no devices plugged into my Imac and running everything wireless. SMB/PRAM resetting did not work. Does anyone have some advice or can help?

    Keep receiving "USB Over Current Notices" since updating to OSX 10.6.8. I have no devices plugged into my Imac and running everything wireless. SMC/PRAM resetting did not work. Does anyone have some advice or can help?

    Hi Melissa,
    Pretty strange, but...
    Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, does it happen in Safe Mode? Reboot when it completes.
    (Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)

  • Hello, my backspace and enter keys suddenly stopped working. I have done a PRAM reset and used the keyboard viewer to see if the buttons work and they don't.  The PRAM reset didn't work  either

    Dear All,  the backspace and enter keys on my wireless keyboard suddenly stopped working.  Im using OS 10.7.5 and have tried a PRAM reset which didn't work.  I also used the keyboard viewer to see if the keys worked on that but they don't.  This is driving me mad, can anyone please tell me what to do?  It happened just after an update but this could be a coincidence.  Thank you for your time 

    For my computers, though some of them support BlueTooth devices and accessories,
    my preference and economy of standard, is to have wired USB and also use powered
    USB hubs for accessories.
    I've used USB wired keyboards and mouse products; and some I've bought from the
    original owners who had upgraded to BT, and never used the new Apple USB model;
    so I have spares of these on-hand since they seldom fail, but do work when BT won't.
    {A SMC reset should not cause a problem, or seldom has; but can solve some.}
    In my opinion, the wired USB keyboard is an essential accessory, if not a necessary
    primary means of user access on a continuous basis. At least until the wires fail...!

Maybe you are looking for