Screen flickers after boot camp 2.1 upgrade

I have been running boot camp 2.0 and WinXP for a few weeks on my iMac 24" 3.06 Ghz 4 Gb running 10.5.5. I had installed the nvidia 177.98 drivers and they improved gaming performance and work great.
I installed the boot camp 2.1 upgrade and the video drivers changed back to the boot camp 2.1 drivers. I re-installed the nvidia 177.98 drivers.
I now have two issues:
1. the monitor is listed as generic plug and play. Is there a driver for the iMac 24" display?
2. My room is dark so I use F1 to reduce the screen brightness. The whole screen flickers or flashes continuously. IF i have the brightness up near make the flickers or flashing stops. Anyone sen this or have any thoughts?
If i can't stop the flickering and flashing, I will eventually delete the WinXP system and re-create it and stick with boot camp 2.0.
..Bob

Before you re-do everything consider other options.
This is the procedure for uninstalling and installing drivers. A program called driver sweeper is required. To uninstall your old drivers you must boot into safe mode, uninstall your old drivers, use driver sweeper to eliminate any remaining fragments of your driver and then install new driver.
http://www.guru3d.com/category/driversweeper/
http://forums.guru3d.com/forumdisplay.php?f=29
Maybe you need to do 2.1 first? or use later drivers?
nVIDIA ForceWare X 179.13 for Windows XP/2K 32bit
http://www.laptopvideo2go.com/drivers/xp/179.13
In the future, you might want to use something to regularly backup, but for now, WinClone can take a full snapshot image for restore, and runs in OS X. DataBackupPC from Prosoft Engineering (Data Rescue II folks) or similar backup / cloning software (Acronis doesn't support GPT and EFI, so no Mac support).

Similar Messages

  • Driver BSOD on Startup after Boot Camp 3.0 Upgrade.

    Hello all you support board types. I have a little bit of a problem these days.
    Yesterday I went and installed the Boot Camp 3.0 Drivers from my shiny new Snow Leopard Disc. The install went off without a hitch and I hit restart to complete the install.
    And then I hit a nice big blue screen of death.
    Here is the info from the blue screen:
    Driver in Question: NV4_DISP (sounds like graphics card driver to me) thrown into an infinite loop.
    *STOP: 0x000000EA (0x8A46E428, 0X8A91A1B8, 0XF78C3CBC, 0X0000000)
    NV4_DISP
    It will not start up with multiple restarts. It will start in safe mode. You cannot reinstall the Boot Camp drivers while in safe mode (a feature, it seems, of safe mode, natch).
    Any ideas?
    Thanks.

    Your assupmtion is right....its a problem with the nvidia display driver.
    Try booting in safemode and deinstalling the driver. This should at least make u able to boot normally. Then try to install one of those modded-drivers. I've been using those for a long time without problems

  • Satellite C55-A5182 - Screen flickering after windows 10 upgrade.

    Satellite C55-A5182: screen flickers after windows 10 upgrade....help!!!

    Hi there ,  Thank you for visiting the HP Support Forums and Welcome! This is a great site to get answers and ask questions. I read your post on the HP Support Forums and I understand that you are having an issue with the Touchscreen on your HP Notebook - 15-ac020nr. You had mentioned that since your Windows 10 Upgrade, it no longer works.  Have you tried doing all updates (Windows, HP Support Assistant, BIOS)?Have you tried restarting the Notebook a couple of times?Have you tried to run the Windows Troubleshooter? Here is a link to the HP Support Assistant. Just download and run the application and it will help with the software and drivers on your system that need updating for Windows 10. The HP Support Assistant will also help find a proper driver for you to use.  Updated Windows 10 drivers will become available on the HP Drivers and Downloads Page for your product. They will be released as they become available to HP. I did find a troubleshooting document for you called Touch Screen Issues. Although it does say it is for Windows 8, it will still work for Windows 10.  Please follow the provided troubleshooting steps and re-post with the results.  Have a great day!

  • Cannot install Boot Camp 3.2 upgrade for Windows 7 64 bit

    I recently installed Windows 7 64 bit on my macbook. I also installed Boot Camp 3.0.1 after Windows 7 installation, however, WiFi did not work. Therefore, I needed to upgrade to the latest Boot Camp 3.2. However, when I tried to install Boot Camp 3.2 upgrade for Windows 7 74 bit, I got an error message saying that I needed Boot Camp 3.1 installed first. I CANNOT find Boot Camp 3.1 upgrade for Windows 7 64 bit on Apple website at all. Can someone please help me on this? Is there a way to get the complete Boot Camp 3.2 package that can simply be installed on version 3.0.1??

    here is the link to bootcamp 3.1 for windows 7 64 bit http://support.apple.com/kb/DL1336 .. and no there is no package that can be applied to the windows side to go from 3.0.1 to 3.2

  • HT1899 How do i boot to mac after boot camp

    How do i boot back to mac after boot camp? I was in the middle of installing windows 7 when i received an error message saying the partition needs to be in a diff format ( NFTS ). I tried restarting my mac but now its saying "no bootable device - insert boot disk"

    Welcome to the Apple Support Communities
    You have to format the volume using NTFS in Windows installer. After you've installed Windows, press X key while your computer is starting to start in Mac OS X

  • Can't get past gray screen after Boot Camp Assistant

    So last night I decided it was time to start experimenting with Boot Camp and Windows XP Pro. I fired up Boot Camp Assistant and allocated a 32gb partition of my HD for the XP install. When prompted, I put in the XP Pro CD and restarted. It booted into the XP install utility, but when asking about which partition to use, instead of the 32gb partition, all I saw was a 131gb partition. Thinking that it was my OS X partition, I decided to cancel out of the install and do some more investigating. When it restarted, all I got was a blank gray screen, no spinning gear, no logos, nothing. When rebooting while holding down a mouse button, I was able to eject the Windows XP cd. Here's what I've tried so far:
    CDs: Leopard, Original OS X Disk 1, Windows XP, None
    Keys: none
    Result: Gray screen
    Keys: option
    Result: Gray screen with mouse pointer that initially is moveable, but then freezes
    Keys: c
    Result: Gray screen
    Keys: d
    Result: Gray Screen
    Keys: shift
    Result: Gray Screen
    Keys: command + r + p
    Result: Gray Screen
    Holding power button
    Result: Long tone while starting up, then gray screen.
    What can I do?? I'm thinking that Boot Camp fried my HD partition data, but I can't seem to access any of the boot disks or any sort of disk utilities

    I did. I took it into the Apple store and they replaced my hard drive. It was under warranty, so it wasn't a problem. I got them to give me my old hard drive back, which I hooked up to an external SATA enclosure. My mac recognized it, but said it wasn't initialized. I downloaded Data Rescue II and it recovered all of my software. I'm now using it as a Time Machine disk.
    After further research, I found out the my main problem was that I used Windows XP SP1. You NEED to use SP2, otherwise, this problem will occur. I figured I could just upgrade later, but nope, you need a native SP2 disk.
    If your Mac isn't under warranty, try this post:
    http://phail.net/2008/04/10/bootcamp-windows-xp-sp1-epic-phail/
    and his solution:
    http://phail.net/2008/04/13/bootcampsp1-white-screen-of-death-a-solution/
    In short, you need another Leopard computer. I bet if you print out the instructions and take them to the Apple store with you, the Genius Bar will help you, they've always been super helpful/nice with me.
    Good luck!!

  • Problems with graphics after Boot Camp upgrade (from 3.1 to 3.2)

    Right, today I upgraded Boot Camp (the first time I used iTunes on Windows so thats way I never did the upgrade before) from 3.1 to 3.2 and after the installation my screen went blank/black. After restarting iMac it the screen appeared but in 1024x768 resolution and without working graphic drivers.
    I tried many different options to update the ATI HD 4850 driver, but none of them worked. It always says that there is some problem with it, but it also is up to date every time I try to update it manually for the drivers which comes with 10.12 Catalyst.
    I spend several hours trying to solve it, but I just can't and I really don't know what to do next.

    Right, I managed to fix it by updating the software manually, but selecting to choose from the list and I had to install the mobility drivers.

  • Why do I get a dark screen in Windows 7 after Boot Camp?

    Hello fellows!
    What is wrong?
    About this week I have tried to install Windows – Windows 7 Ultimate 32-bit – on my MacBook Pro(Early 2011-model). Everything works perfectly, except one thing! The screen.
    Before I am installing the drivers from Windows Support the screen is lightly and everything, but after the restart, everything on the screen goes dark. I have tried to find the correct drivers, but then it tells me that: I don't have to correct Graphic adapter.
    I have to graphic cards: an AMD Radeon HD 6750M and an Intel HD Graphics 3000.
    Yesterday I downloaded a program known as gfxCardStatus – a program, which can switch between the graphic cards on your computer –, and I tried it.
    Before installing this program I knew that Mac OS X was running the Intel-model, when Windows 7 was running the AMD. Then, I switched from Intel to AMD on MAC OS X, then I booted up Windows and reinstalled the drivers from WindowsSupport, and everything worked properly! Until I rebooted to get multicore working.
    I was so frustrated that I gave up and waited for today. Then this morning I tried to do the same thing, to get a lightly screen again. But a terrible thing happened. Mac OS X got the same problem. But after some time working things out it worked properly.. On Mac OS X!
    What can you do for me?
    I hope you can tell me what is wrong with the Boot Camp. I really want Windows to run properly. I cannot accept a dark screen, and I hope somebody out there has experience and at the same time got the awesome personality to help me through this problem.
    Operating System on Mac: Mac OS X Lion.
    Opereating System on Windows: Windows 7 Ultimate 32-bit
    Have a nice day, everybody.

    I can easily get into Windows. It is just that the drivers don't seem to work correct, and makes the screen dark.

  • Windows 7 - Blue screen of death after Boot Camp install

    Hello! I have done some searches with no answers, so...
    After installing Windows 7 from scratch I then install Boot Camp 3.0 which then leads to the Windows blue screen of death upon reboot. I then have to recover Windows to the previous state prior to installing Boot Camp.
    Help!?

    Most likely, Apple HFS read-only, which is AppleHFS.sys and AppleMNT.sys - rename those and see.
    You might want to run chkdsk after all this to make sure there are no errors with the drive and file system.
    Windows Explorer will not accept HFS+ filenames with special characters and will "green bar" and hang when it does, too.
    The faulty HFS driver is a valid concern.
    Rename AppleHFS.sys and AppleMNT.sys
    By doing the following you will disable HFS mount / read mode on windows XP, Vista, 7.
    Navigate to c:/windows/system32/drivers/AppleMNT.sys, rename the AppleMNT.sys file to something like AppleMNT_keep.sys or something of your likings.
    The faulty HFS driver is a valid concern. It seems to happen on many systems.
    You find it in Windows/system32/drivers/AppleHFS.sys
    Renaming to AppleHFS_disabled.sys will avoid the blue screens until you have found another solution or Apple updates Bootcamp 3
    After renaming both myself because they are no longer "*.sys" or something? they are gone. In my case AppleHFS prevented Windows Backup from running to end and was causing error "some files skipped" and while some might find reading convenient, I prefer Windows not have even read-only access.
    You can probably do better with MacDrive, or probably Paragon's HFS driver, to read AND write if needed, to HFS from Windows.

  • Windows 7 Black screen with cursor after boot camp partition

    So I realise this is a problem that was plaguing people a few years back. So I'll go from the very start.
    I've downloaded a copy of windows 7 professional 64bit from the Microsoft website. My optical/CD drive isn't working, so I've been unable to use it
    to install windows. I decided I'd try booting from my USB. So I have the ISO file and formatted my USB and I've downloaded the latest drivers for boot camp assistant on my mac (version 5.0.4) I'm up to date with every update for my mac. Now, I do realise that Apple doesn't recommend using a USB to load windows, but I watched this http://www.youtube.com/watch?v=8z1gqw0ougo and it explained how to get the checkbox up when you're in boot camp so you can run from your USB.
    My problem now, is that straight after I have partitioned my hard drive, it goes on to install windows but upon restarting it reaches "the black screen of death" with just the white cursor blinking. I've tried multiple times and keep getting the same result. I've even tried what Apple suggested and only have one USB device plugged in http://support.apple.com/kb/TS4536
    The details for my mac are as follows:
    Model Name:
    iMac
      Model Identifier:
    iMac10,1
      Processor Name:
    Intel Core 2 Duo
      Processor Speed:
    3.06 GHz
      Number of Processors:
    1
      Total Number of Cores:
    2
      L2 Cache:
    3 MB
      Memory:
    4 GB
      Bus Speed:
    1.07 GHz
      Boot ROM Version:
    IM101.00CC.B00
      SMC Version (system):
    1.53f13
      Serial Number (system):
    W800992A5PE
      Hardware UUID:
    A108E54E-3C53-5AF8-BFDF-2CF7ED567A74
    and it's a late 2009 model.

    I have solved this issue now but seem to have encountered another one. I solved the above issue simply by keep on trying time and time again, partitioning the hard drive and trying to install windows 7.
    Anyway, I have encountered this error: windows setup could not apply the configuration set. The WINDOWS folder cannot be found.
    Please help!

  • Black Screen after Boot Camp

    Hello,
    i want start saying that i don't speak english so i want apologize for my text error, anyway, as the title say after the creation of boot camp partition, i start to install Windows 7 Ultimate and it gone fine, but after this the installation requires system restart, i press "Alt" and choose to boot in Windows partition and then come the black screen with a flashing dash in the top left, i wait for 4 hours and nothing. After this i tried more times to install Windows and i try to reset PRAM and SMC too, but nothing.
    Please Help me.

    repost in the Boot Camp forum: https://discussions.apple.com/community/windows_software/boot_camp

  • After boot camp setup, white screen

    Hello boys and girls.
    So finally I decided I'd benefit from a bootcamp setup with Windows 7.
    My setup is a MBP 15" late 2011 running OS X 10.8.5. 240Gb SSD in main hard drive slot with some alternative version of OptiBay, in other words I exchanged my DVD for another hard drive (the original 500Gb SATA).
    The thought is to run OS X from the SSD and bootcamp on a 100Gb partition on the SATA disc. The remaining 400Gb should be shared between the two systems so I guess ntfs is the file system to go? Anyways, so far so good..
    I used bootcamp to download the required software onto an external USB drive and chose to restart my computer, boot camp stated something about changing boot order and tbh I didn't pay all that much attention, just hammered "OK".
    Mac reboots with a blank white screen, nothing happens. Doesn't matter if I unplug USB-drive or USB-DVD, still same wierd error. Googled it and tried a PRAM(correct me if I'm wrong) -reset. OS X is now booting up properly again but now I'm back to square one...
    Perhaps I should also mention that ever since my MBP was brand new it have been freezing randomly a couple of times per month, wheel just starts spinning and I have to restart it using power button long press. Some times when it boots up, it has a folder with a questionmark in it, blinking. That too, seems very random and came from the store..
    Maybe that's not the same problem and if so, this is about trying to figure out what makes boot camp screw up boot..
    Thanks in advance!
    Simon.

    I do had the same issue with my build in iSight camera, but it did not seem to be related to the boot camp partition
    (macbook pro, late 2007 model, OSX 10.4.11 Tiger, BootCamp Partition with XP).
    The camera stopped working ramdomly, as mentioned above, not detected by any software or system profiler. The solution was always rebooting, sometimes twice.
    When it finally completely stopped working a few days ago I've tried:
    - safe reboot
    - resetting the PRAM
    - resetting the SMC
    - rebooting several times
    none of it worked. I've tried the camera in BootCamp Windows, but it did not detect it either.
    It seems to be a common problem, as I found issues in several forums but unfortunately no solution.
    Today I've called apple support, they said it might be a contact problem or a defect iSight.
    I wish I had better news. Anyone else with a mor helpful suggestion?

  • Mac Won't Boot after Boot Camp Windows Update - Macbook Pro Mid 2010

    Hello All, and thanks in advance for any assistance you can provide.
    I have a Mid 2010 Macbook Pro. Last year I upgraded the RAM, then this year I decided to upgrade the hard drive to an SSD-hybrid. Everything went perfectly smoothly with both upgrades, and I was a happy camper.
    I had also installed Boot Camp with Windows 7 and everything worked perfectly. Then last night, I boot in to Windows 7 and it gives me a 'service pack update'. After installing it, I had to reboot my computer. Rebooted it and it accidently started booting OSX. No problem, I thought. I held down the power button, and booted back in to Windows. The service pack installation continued and it had me restart my computer an obscene amount of times during the installation. This is when I initially thought "this is weird".
    Finally the service pack installs, and I'm able to use Windows 7 again. Then I shut down the machine and tried to boot back into OSX. No dice.
    Here's how the OSX booting process goes:
    First, the Apple logo appears, then what appears to be a progressive loading bar at the bottom. After a few seconds, the loading bar disappears. Then it's just at the Apple booting screen with the spinning wheel/gear and sits there indefinitiely. I let it sit there for over an hour last night and nothing happened.
    Any suggestions? I tried resetting the NVRAM and the SMC.
    Thanks so much,
    dlevv

    It looks like a hard disk problem. Press Command and R keys on boot, open Disk Utility, select Macintosh HD in the sidebar and repair your drive

  • Apple Store Refuses to Diagnose Hardware Issue after Boot Camp Installed

    I previously reported an issue in the Boot Camp Beta forum, but figured I share this with other MBP users as well. After loading the updated firmware, running boot camp to partion my drive, I installed Windows XP Professional. During the install, the screen would go dark, and come back at irregular intervals, as if there was a video sync problem of something. I managed to get XP installed, and booted it and loaded the updated drives from the Boot Camp driver CD which I had earlier created. Subsequent attempt to use the XP installation result in a constantly blank screen, with only occational glitches, as if there is some activity coming out of the GPU, but it's not working correctly.
    This is what led me to take my machine to my local (15 miles away) Apple Retail Store (Washington Sqaure, Tigard, Oregon), and attempt to show the problem to a "genius". HOWEVER... As soon as I mentioned "Boot Camp" and XP, they went into the whole "public beta, blah, blah, blah", "not supported", etc. I tried to explain that I was not reporting a SOFTWARE issue with Boot Camp, but rather a HARDWARE ISSUE which is exposed on my machine only after using BOOT CAMP to partition the hard drive, and then installing Windows XP. All I get was "Well, it works fine in OSX, and Boot Camp is Public Beta, so there's nothing we're going to do". Obviously, I'm livid. And, will pursuing any and all avenues to bring this problem to Apple Management attention. First it was Mark Pienpakdee the "genius" who tried to help me, and then I was further rebuked by Mark Macsurak, Assistant Manager. So, I'm left with broken hardware which won't work correctly running Windows, and no recourse until Boot Camp isn't "Public Beta". What a load of crap. I was so mad, I didn't even bother buying the extra AC adapter I was planning on picking up. ARGHHHHHHHHHHH!!!!!!!!!!!!!!!
    I was absolutly shocked that the "genius" didn't react with anything like "wow, what an interesting problem, let's see if we can diagnose it". He didn't even want to see me boot XP to show the problem, only wanted to see that OSX was working normally and send me on my way.
    If you have had similar problem at the Washington Square store in Oregon, be sure to let them know by sending e-mail to [email protected], I know I will...
    Eric

    If you are going to send an e-mail you should send it to [email protected] However, nobody from Apple is going to send you a response. The Software is Beta which means it is not ready for Prime Time (Also that means that the drivers are beta too). Plus they say before you decide to install any of this in their write ups that they do not and will not provide any support for BootCamp and/or Windows. So they are right not to do anything if the computer works like it is supposed to under OS 10.4.6. Now they might take a look at somethings when OS 10.5 comes out if it has BootCamp in it. They may have something similiar in it, or it might be a perfected BootCamp. However, I doubt that they will ever provide any support for Windows. There has been some talk that Microsoft is looking into supporting Windows on the MAC. However, as far as I have heard no decision on that has come out as of yet.

  • MacBook Pro 13" Late 2011 Experiencing Significant Slow Down After Boot Camp Installation

         Okay, so today, after installing Windows 7 on my MacBook Pro via Bootcamp Assistant, I experienced significant performance slow down (fans going at full blast, applications opening after extended periods of time, keystrokes not being registered) when I returned to my OS X partition/second hard drive. I have dual hard drives, one of them being a Samsung 256 GB SSD with OS X Mavericks and the other being my original 500 GB HDD, divided into a 250 GB OS X Mavericks partition and a 250 GB Windows partition. I have the SSD set as my startup disk and I have it located in the main HDD bay. I moved the old HDD into a caddy and placed it where the optical drive normally should be.
          After multiple failed attempts to install Windows via USB and Bootcamp Assistant, I decided to reinstall my optical drive and use a Windows installation disk. This attempt proved successful, and I was able to install Windows 7 onto the 250 GB partition I had created for it on the 500 GB HDD. After completing basic setup of Windows, I removed the optical disk drive and reinstalled the SSD and the HDD into their original spots (SSD in the main HDD bay, HDD in the caddy where the optical drive normally is).
         After completing this tedious process, I booted my Mac back up using the SSD. However, I noticed something was wrong when the login screen, apps, and nearly everything else on my desktop had slowed to crawl. I decided to check my Activity Monitor to see what the problem might be. Activity Monitor told me that the task "kernel_task" was taking up anywhere from 200-600% of my CPU, which explained the slowdown in performance. I looked around to see if there were others with the same problem as me, and I found that Spotlight Indexing might be an issue, with a potential remedy being move my Bootcamp Partition into the Privacy section of Spotlight under System Preferences. After doing that, I experienced no increase in performance and everything was still going very slowly.
         The next step I took was to see if booting into Safe Mode would help the issue. After booting into Safe Mode on my SSD, I noticed that things were back to their normal speeds, with applications opening at the speed they should be and keystrokes being registered instantaneously. However, the fans were still going and had not shut off once booting into Safe Mode. In addition, I checked Activity Monitor and the "kernel_task" in question was no longer taking up massive amounts of the CPU.
         At this point, I don't know what to do and I need help in restoring my Mac to original speeds. I may end up deleting my Boot Camp partition as a last measure if all else fails, seeing as I installed Windows in the first place for running a few programs and games that I can live without. However, I'd prefer to not have things come to that and fix things before deleting the Boot Camp Partition. I've heard that if everything runs normally in Safe Mode, then the issue is third-party software. Is this true?
         Any help would be greatly appreciated as I am writing this from the MacBook in question in Safe Mode because it's essentially useless in normal SSD operation.

    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.
    Don't be put off merely by the seeming complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
    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 behest 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 ' \*AutoCad \*dropbox \*GoogleDr\* vidinst\* ' 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 1000 MB com.apple.AirPortBaseStationAgent 464843899 );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^\([0-9]+\) /,"");n=$0;getline;} $NF=="'${p[26]}')" { 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/) ' ' /:$/{ N;/:.+:/d;s/ *://;b0'$'\n'' };/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;};$b0'$'\n'' d;:0'$'\n'' x;s/\n\n//;/Apple[ ,]|Intel|SMSC/d;s/\n.*//;/\)$/p;' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/ / { n++;print;} END { if(n<200) print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { 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{next}'"`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}(.+) <.+/\1/p' ' /Launch[AD].+\.plist$/ { n++;print;} END { print "'${p[41]}'";if(n<200) print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$|'${p[41]}'/ { print $3;} ' ' /\.(framew|lproj)|\):/d;/plist:|:.+(Mach|scrip)/s/:[^:]+//p ' '/root/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/ { n++;print;} END { if(n<1000) print "/System/";} ' '/^\/usr\/lib\/.+dylib$/p' ' /Temp|emac/ { next;} /(etc|Preferences|Launch[AD].+)\// { sub(".(/private)?","");n++;print;} END { print "'${p[41]}'.plist\t'${p[42]}'";if(n<500) print "Launch";} ' ' /\/(Contents\/.+\/Contents|Frameworks)\/|\.wdgt\/.+\.([bw]|plu)/d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| |\n","\\|\\|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/ ) ' ' $1~"lR"&&$2<='${p[25]}';$1~"li"&&$3!~"wpa2";' ' BEGIN { FS=":";} { n=split($3,a,".");sub(/_2[01].+/,"",$3);print $2" "$3" "a[n]" "$1;b=b$1;} END { if(b) 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!~/^(AS.+ (En.+ )?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);} ' ' /^ +[NP].+ =/h;/^( +D.+[{]|[}])/{ g;s/.+= //p;};' 's/0/Off/p' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' / / { print "'"${p[28]}"'";exit;};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" ' $10~/\(L/&&$9!~"localhost" { sub(/.+:/,"",$9);print $1": "$9;} ' '/^ +r/s/.+"(.+)".+/\1/p' 's/(.+\.wdgt)\/(Contents\/)?Info\.plist$/\1/p' 's/^.+\/(.+)\.wdgt$/\1/p' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil 'PlistBuddy 2>&1 -c "Print' 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 sudo\ lsof test );c2=(com.apple.loginwindow\ LoginHook '" /L*/P*/loginw*' '" L*/P*/*loginit*' 'L*/Ca*/com.ap*.Saf*/E*/* -depth 1 -name In*t -exec '"${c1[14]}"' :CFBundleDisplayName" {} \;' '~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 \)' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' :${p[35]}\" :Label\" '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status " -F '\$Time \$Message' -k Sender kernel -k Message Req 'bad |Beac|caug|dead[^bl]|FAIL|fail|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA\(|pagin|proc: t|Roamed|rror|ssert|Thrott|tim(ed? ?|ing )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/r*/com.apple.*.{BS,Bas,Es,J,OSXU,Rem,up}*.bom' '{/,}L*/Lo*/Diag* -type f -regex .\*[cgh] ! -name *ag \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true \) -execdir stat -f:%Sc:%N -t%F {} \;|sort -t: -k2 |tail -n'${p[38]} '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Ca*/*/Ex,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo,Widg}* -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto,{cron,fs}tab,hosts,{[lp],sy}*.conf,pam.d/*,ssh{,d}_config,*.local} {,/usr/local}/etc/periodic/*/* /L*/P*{,/*}/com.a*.{Bo,sec*.ap}*t /S*/L*/Lau*/*t .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers\ "${p[N5]}" -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\ / '-R -l1 -n1 -o mem -stats command,uid,mem' -i4TCP:0-1023 com.apple.dashboard\ layer-gadgets '-d /L*/Mana*/$USER&&echo On' '-app Safari WebKitDNSPrefetchingEnabled' );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 Wi-Fi Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight Memory Listeners Widgets Parental\ Controls Prefetching );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 >&-;date '+Start time: %T %D%n';};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 [[ "$i" ]]&&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: <(printf "${v[$1]}") <(printf "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v=`grep -Fv "${v[$1]}"<<<"$v"`;};C0(){ [[ "$v" ]]&&echo "$v";};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;D23 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 44 54 45;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;D13 24 24 32 31;D13 25 37 32 33;A2 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;};D13 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;B1&&D23 35 45 55 46;D23 32 31 43 38;D12 36 47 32 48;D13 20 42 32 41;D13 14 2 48 43;D13 4 5 32 1;D22 4 4 50 0;D13 4 3 32 5;D12 26 48 49 49;B3 4 22 57;A1 26 46 56;B7 22;B3 0 0 58;C3 47;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" or "Event not found," 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 the words "Start Time." 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.

Maybe you are looking for