Windows 7 on iMac experiencing frequent screen-wrap?

I installed Windows 7 on my iMac with no issues, and the first few times it loaded up just fine. However now I experience frequent screen-wrap, or screen issues in general when booting up into windows.
I'll start up the computer, and sometimes the left edge of the Windows start-up screen will start in the middle of the iMac screen, wrapping around with the far right edge coming back to the center from the left side (I hope I'm explaining this alright). Sometimes it'll wrap from top to bottom, and sometime I can only see the very bottom of the start up screen up at the very top of the actual iMac display. I end up just doing a hard restart with the button on the back until the screen is properly positioned on my iMac. Sometimes it takes a few restarts, sometimes it comes up correctly the first time. After it loads up correctly, I have no issues until it comes to turning it back on again after any restarts or shutting down for the night. I've tried running all sorts of anti-virus, but I haven't found anything (I'm not sure where I would have picked anything up from in the first place).
I've been seeing many posts regarding a black screen during/after installation, but I don't think that's my issue since I can run windows just fine when I can see it. Is there any way to fix this?
Thanks. (This is my first post, so please let me know if I'm not explaining this very well)

Ah sorry, I can try to do a screen shot, but is it possible to do one while the computer is still starting up? As for model, I know it's a 27 inch iMac that I bought brand new about 4 years ago. I'll have to log of and log onto the Mac OS side, as I'm on the windows side right now.
Thanks

Similar Messages

Frequent screen freezes with os 10.8.3

I am experiencing frequent screen freezes with OS 10.8.3 on my 27" iMac, Late 2009. Sometimes while using Safari, sometimes while using Photoshop CS5.1, Sketchup 8, or other software. Rarely does it coincide with a processor intensive operation. I have not had this problem since my old white G5 iMac. Then it was aleading indicator that the CPU or power supply needed replacing (I went through 5 processors and 6 power supplies with that machine.) I took my current iMac in to the Apple Store and had it checked out. Hardware checked out fine, but the freezes are becoming more frequent. Does anyone have any suggestions?

The next time you have the problem, note the exact time: hour, minute, second.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console 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 Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Scroll back in the log to the time you noted above. Select any messages timestamped from then until the end of the episode. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

After errors with disk partition, I removed Windows from my iMac. Now when I start my computer it goes into a black screen and not straight into the Mac area like it used to, unless I hold Alt straight away to give me the option. Any help?

Hi,
Sorry, I'm new to the community, so apologies if I'm repeating myself.
OK, so I tried to install Windows Vista onto my iMac with the disk partition. Everything was going fine and it wasn't until last minute, when it was installed that an error came up saying that this can only be done with Windows 7. After this error, I couldn't access any errors of my iMac and when I shut down and restarted my computer, it automatically logged into Windows.
So after a panic, I rang Apple Care and the lady helped me log into my apple area, delete Windows from my iMac, and all was restored.
However, now when I shut down my computer and boot it back up, I think my iMac is trying to log into Windows areas that no longer exist. It loads up a black screen and doesn't move from there. To log into my Apple area, I have to do the whole process of holding Alt immediately after I switch the power on and access the Mac drive and log in that way.
It's beginning to become a real pain and I'm paranoid this process is going to damage my computer. Any advice on how to restore logging-in back to it's former glory when I first purchased it?
Thanks

Solved it. Thank you very much for that!

I have a new (mid-2011 27" Imac with 2 Thunderbolt ports each driving one 27" Thunderbolt display. The 3 displays work perfectly in OSX Lion but in Bootcamp 4.0 with Windows 7 (64 bit) only 2 screens come up. everything is up to date. Anyonce who can help

I have a new (mid-2011 27" Imac with 2 Thunderbolt Ports each driving one 27" Thunderbolt display.
Graphic card is AMD Radeon HD 6970M with 2Gb of VRAM. All works 100% in Lion but
in Bootcamp 4.0 running windows 7 Professional (64 bit) Only 2 of the 3 screens work not all three.
Tried updates, calling Apple etc. But no luck. Windows doesn't recognize the 3rd screen while
checking on the driver in windows is tells me it's the latest and best available. ? In VMware
Windows 7 also works fine over three screens so windows can do it. But I need it natively to
work. (i.o.w. in Bootcamp). Does Anybody know how to solve this, or if Apple is working on a
solution for this ? It really hurts to have one of these expensive screens staring at you being dead.

I have a new (mid-2011 27" Imac with 2 Thunderbolt Ports each driving one 27" Thunderbolt display.
Graphic card is AMD Radeon HD 6970M with 2Gb of VRAM. All works 100% in Lion but
in Bootcamp 4.0 running windows 7 Professional (64 bit) Only 2 of the 3 screens work not all three.
Tried updates, calling Apple etc. But no luck. Windows doesn't recognize the 3rd screen while
checking on the driver in windows is tells me it's the latest and best available. ? In VMware
Windows 7 also works fine over three screens so windows can do it. But I need it natively to
work. (i.o.w. in Bootcamp). Does Anybody know how to solve this, or if Apple is working on a
solution for this ? It really hurts to have one of these expensive screens staring at you being dead.

I have a 24" imac model 9,1 running OS 10.6.8 and I am experiencing frequent freezes and crashes. How can I solve this problem?

I have a 24" imac model 9,1 running OS 10.6.8 and I am experiencing frequent freezes and crashes. How can I solve this problem?
Hal

As old as your iMac is, have you cleaned out the dust? Dust buildup can lead to over heating issues. Remove any and all things plugged into it including the power cord, Remove the RAM access grille. Vacuum all openings starting with the RAM access area (air intake). Vacuum all ports and plugs, DVD slot and the opening across the top of the rear of the body. Blow compressed air through all your openings and vacuum again to remove any dust you loosend. Reinstall the RAM grille. Plug in the keyboard and mouse if not blue tooth. Insert power cord...
You are now in a perfect position to do a
SMC RESET
http://support.apple.com/kb/HT3964
Shut down the computer.
Unplug the computer's power cord and ALL peripherals.
Wait 15 seconds.
Attach the computers power cable.
Wait another 5 seconds and press the power button to turn on the computer.
It is the 5 second timing that initiates the reset.
Here is a link to a Widget to monitor your temps and other operations:
http://islayer.com/apps/istatpro/
since you are running 10.6.8 did you install the combo update?
Mac OS X 10.6.8 Update Combo v1.1
It is more stable than the regular version.
You could use your original install disc and boot from the disc, run Disc Utility and do a repair disk.

My IMac is experiencing frequent freezing. How do I overcome this?Thanks

I am experiencing frequent freezing on my IMac. Can anayone assist to ssolve this issue? Thanks

Run Apple Hardware Test (AHT) on your system, if not problems are found run Disk Utility and click the repair button to check and repair your hard drive.

IMac 10,1 screen flickers

The screen flickers after I have been on the computer for 10-15 minutes. Back in January, the hard drive failed and was replaced. Is flickering a sign that the video display is about to die, or something less of a pain in the rear?

Unfortunately I cannot help, but I have the same issue. What I observe is that it tends to get better the longer the machine runs, i.e. heat becomes it. From Leopard to Lion the iMac would not go to sleep ever, only display sleep (black screen), but the rest would be running. During that time I hardly ever had any screen flickering issues. Only when I booted up after a prolonged period of rest (the machine, not me). Under Mountain Lion it seems it's gotten past its insomnia. So I have frequent screen flickering, but after some 30 minutes of activity it tends to bget better. But I seem to observe a slow digression. That's all I can say. My Harddisk was replaced years ago by an Apple Store. I am wondering whether it's financially wise to bother with an old machine like that. But I hate to throw things away...

Mac Pro (early 2008) still experiencing frequent Kernel Panic freezing ... ugh

My early 2008 Mac Pro (2 x 2.8 GHz Quad-Core Intel Xeon, 24 GB 800 MHz DDR2 FB-DIMM) is still experiencing frequent Kernel Panic freezing.
Some days I can go the whole day without one, other days I will experience many, some while using the computer, some after waking it up, some after restarting from one.... its a mess.
I thought it might be RAM related. So I ran different tests on all the chips, found nothing, no errors reported after overnight looping tests. I added more RAM (I ordered 4 2Gb chips so I'd have a total of 16Gb, they sent me 4Gb cards, so now I have 24Gb. I have heard its best to have all cards of the same size, so I ran it with just the new 4Gb cards giving it 16Gb, it still crashed.) I tested the new ram alone, in 2 card groups, in different configurations on the RAM boards, nada.
Maybe it's the graphics card? But I get no weird graphics artifacts (which I did used to experience with my old iMac before it died).
The fans seem to run normally, not too fast or too loud. Sometimes after repeated crashes I'll open up the computer and blow it out with compressed air. That does seem to help, but not always. It's not real dusty, though there is a fine layer of dust that seems to be stuck/ coat the boards.
In Activity Monitor, the kernel_task hovers at about 1.22 Gb of RAM.
I can not iron down what the problem stems from. Nothing seems to alleviate the crashing, which has become more and more frequent it seems...
Anyone have any suggestions? I have tried using Hardware Test using the original OS disks. I have tried Memtest in Terminal. All to no avail. Nothing turned up any errors. I am not sure what to do next besides call for an Exorcism.
Please help!

They keep happening. In the time it took to select the latest one, copy and paste it here, and then write this, a dozen more were logged... Is that normal??
Process:
hasplmd [1024]
Path:
/usr/libexec/hasplmd
Identifier:
hasplmd
Version:
Code Type:
X86 (Native)
Parent Process: launchd [1]
User ID:
0
Date/Time:
2012-10-20 15:28:56.159 -0700
OS Version:
Mac OS X 10.8.2 (12C60)
Report Version: 10
Crashed Thread: 0
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
VM Regions Near 0:
--> __PAGEZERO
0000000000000000-0000000000001000 [
4K] ---/--- SM=NUL /usr/libexec/hasplmd
__TEXT
0000000000001000-00000000001d2000 [ 1860K] r-x/rwx SM=COW /usr/libexec/hasplmd
Thread 0 Crashed:
0   ???
0000000000 0 + 0
1   libsystem_kernel.dylib
0x9a40b9fb mig_get_reply_port + 10
2   libsystem_kernel.dylib
0x9a404c04 task_set_exception_ports + 86
3   ???
0x0048f73a 0 + 4781882
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x0048f63c ecx: 0x00000001 edx: 0x9a40b77e
edi: 0x00000907 esi: 0x00000000 ebp: 0xbffffce8 esp: 0xbffffcdc
   ss: 0x00000023 efl: 0x00010286 eip: 0x00000000   cs: 0x0000001b
   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
cr2: 0x00000000
Logical CPU: 6
Binary Images:
0x1000 -   0x1d0fff hasplmd (???) <0315D420-D963-3935-5106-C26DA1355A48> /usr/libexec/hasplmd
0x8fe6d000 - 0x8fe9fe57 dyld (210.2.3) <23516BE4-29BE-350C-91C9-F36E7999F0F1> /usr/lib/dyld
0x90007000 - 0x90019ff7 libdispatch.dylib (228.23) <86EF7D45-2D97-3465-A449-95038AE5DABA> /usr/lib/system/libdispatch.dylib
0x913cb000 - 0x91433ff7 com.apple.framework.IOKit (2.0 - 755.18.10) <9A80E97E-544F-3A45-916D-6DB7ED217E33> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x91786000 - 0x91788fff libdyld.dylib (210.2.3) <05D6FF2A-F09B-309D-95F7-7AF10259C707> /usr/lib/system/libdyld.dylib
0x91932000 - 0x91940ff7 libz.1.dylib (43) <245F1B61-2276-3BBB-9891-99934116D833> /usr/lib/libz.1.dylib
0x91a4e000 - 0x91a90ff7 libauto.dylib (185.1) <B2B5B639-6778-352A-828D-FD8B64A3E8B3> /usr/lib/libauto.dylib
0x91ac3000 - 0x91ae0fff libxpc.dylib (140.41) <1BFE3149-C242-3A77-9729-B00DEDC8CCF2> /usr/lib/system/libxpc.dylib
0x91b38000 - 0x91b39fff libquarantine.dylib (52) <D526310F-DC77-37EA-8F5F-83928EFA3262> /usr/lib/system/libquarantine.dylib
0x92cda000 - 0x92e96ffd libicucore.A.dylib (491.11.1) <B19E450A-BAF1-3967-9C95-7F77DC0B4639> /usr/lib/libicucore.A.dylib
0x92f15000 - 0x92f19ffe libcache.dylib (57) <834FDCA7-FE3B-33CC-A12A-E11E202477EC> /usr/lib/system/libcache.dylib
0x92f1a000 - 0x93102ff3 com.apple.CoreFoundation (6.8 - 744.12) <E939CEA0-493C-3233-9983-5070981BB350> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9342a000 - 0x93436ffe libkxld.dylib (2050.18.24) <48A75AF6-9D5A-3552-948E-30A1682D3664> /usr/lib/system/libkxld.dylib
0x94183000 - 0x9418efff libcommonCrypto.dylib (60026) <A6C6EDB8-7E69-3827-81F3-9A74D0935461> /usr/lib/system/libcommonCrypto.dylib
0x94230000 - 0x9423afff libsystem_notify.dylib (98.5) <7EEE9475-18F8-3099-B0ED-23A3E528ABE0> /usr/lib/system/libsystem_notify.dylib
0x94db5000 - 0x94dbcfff libsystem_dnssd.dylib (379.32.1) <6A505284-2382-3F27-B96F-15FFDACF004E> /usr/lib/system/libsystem_dnssd.dylib
0x94dbd000 - 0x94e1ffff libc++.1.dylib (65.1) <C0CFF9FF-5D52-3EAE-B921-6AE1DA00A135> /usr/lib/libc++.1.dylib
0x9510b000 - 0x9510eff7 libcompiler_rt.dylib (30) <CE5DBDB4-0124-3E2B-9105-989DF98DD108> /usr/lib/system/libcompiler_rt.dylib
0x9524c000 - 0x9524cfff libSystem.B.dylib (169.3) <4F99C03B-BBFF-3BF8-8CC2-2DA764447446> /usr/lib/libSystem.B.dylib
0x95675000 - 0x95679ff7 libmacho.dylib (829) <5280A013-4F74-3F74-BE0C-7F612C49F1DC> /usr/lib/system/libmacho.dylib
0x9567a000 - 0x9567bffd libunc.dylib (25) <58599CBF-E262-3CEA-AFE1-35560E0177DC> /usr/lib/system/libunc.dylib
0x956e6000 - 0x956e7fff libsystem_sandbox.dylib (220) <4E42390B-25EC-3530-AF01-337E430C16EB> /usr/lib/system/libsystem_sandbox.dylib
0x95745000 - 0x95745fff libsystem_blocks.dylib (59) <3A743C5D-CFA5-37D8-80A8-B6795A9DB04F> /usr/lib/system/libsystem_blocks.dylib
0x95746000 - 0x95747fff libdnsinfo.dylib (453.18) <41C7B8E2-2A81-31DE-BD8B-F0C29E169D4F> /usr/lib/system/libdnsinfo.dylib
0x95e05000 - 0x95e0cfff liblaunch.dylib (442.26.2) <310C99F8-0811-314D-9BB9-D0ED6DFA024B> /usr/lib/system/liblaunch.dylib
0x95e28000 - 0x95e8cff3 libstdc++.6.dylib (56) <F8FA490A-8F3C-3645-ABF5-78926CE9C62C> /usr/lib/libstdc++.6.dylib
0x9778f000 - 0x97796ffb libunwind.dylib (35.1) <E1E8D8B3-3C78-3AB1-B398-C180DC6DCF05> /usr/lib/system/libunwind.dylib
0x98944000 - 0x98a51057 libobjc.A.dylib (532.2) <FA455371-7395-3D58-A89B-D1520612D1BC> /usr/lib/libobjc.A.dylib
0x98fa8000 - 0x98fa9fff libremovefile.dylib (23.1) <98622D14-DAAB-3AD8-A5D9-C322BF572A98> /usr/lib/system/libremovefile.dylib
0x9907d000 - 0x9907dfff libkeymgr.dylib (25) <D5E93F7F-9315-3AD6-92C7-941F7B54C490> /usr/lib/system/libkeymgr.dylib
0x9907e000 - 0x990a0fff libc++abi.dylib (24.4) <06479DA4-BC23-34B6-BAFC-A885814261D0> /usr/lib/libc++abi.dylib
0x990a1000 - 0x990edfff libcorecrypto.dylib (106.2) <20EBADBA-D6D6-36F0-AE80-168E9AF13DB6> /usr/lib/system/libcorecrypto.dylib
0x990ee000 - 0x990fcff3 libsystem_network.dylib (77.10) <7FBF5A15-97BA-3721-943E-E77F0C40DBE1> /usr/lib/system/libsystem_network.dylib
0x9912f000 - 0x9915bff7 libsystem_info.dylib (406.17) <AA5611DB-A944-3072-B6BE-ACAB08689547> /usr/lib/system/libsystem_info.dylib
0x996a8000 - 0x996d5ffe libsystem_m.dylib (3022.6) <9975D9C3-3B71-38E3-AA21-C5C5F9D9C431> /usr/lib/system/libsystem_m.dylib
0x99bc8000 - 0x99bc9fff libDiagnosticMessagesClient.dylib (8) <39B3D25A-148A-3936-B800-0D393A00E64F> /usr/lib/libDiagnosticMessagesClient.dylib
0x9a18e000 - 0x9a24bfeb libsystem_c.dylib (825.25) <B1F6916A-F558-38B5-A18C-D9733625FDC9> /usr/lib/system/libsystem_c.dylib
0x9a2d8000 - 0x9a2e0fff libcopyfile.dylib (89) <4963541B-0254-371B-B29A-B6806888949B> /usr/lib/system/libcopyfile.dylib
0x9a2e1000 - 0x9a2f3fff libbsm.0.dylib (32) <DADD385E-FE53-3458-94FB-E316A6345108> /usr/lib/libbsm.0.dylib
0x9a3f9000 - 0x9a413ffc libsystem_kernel.dylib (2050.18.24) <C17D49D0-7961-3B67-B443-C788C6E5AA76> /usr/lib/system/libsystem_kernel.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 303
thread_create: 1
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=41.8M resident=27.1M(65%) swapped_out_or_unallocated=14.7M(35%)
Writable regions: Total=10.1M written=16K(0%) resident=52K(1%) swapped_out=0K(0%) unallocated=10.0M(99%)
REGION TYPE
VIRTUAL
===========
=======
Memory tag=35
3424K
Stack
64.0M
__DATA
3468K
__DATA/__OBJC
52K
__HASP_SRM_3_50
64K
__IMPORT
8K
__LINKEDIT
31.2M
__PAGEZERO
4K
__TD
4K
__TEXT
10.6M
__UNICODE
544K
mapped file
168.4M
shared memory
12K
===========
=======
TOTAL
281.6M

Since installing Mavericks, I have experienced frequent "freezes" in which I can do nothing but power down.

I downloaded Mavericks about 3 months ago. Eversince I have been experiencing frequent system "freezes" not always accompanined by the spinning color ball. When this occurs I can do nothing but power down.
Also another issue: After shutting down and opening numbers I get the message that updates are available.. When I go the Apple store it tells me there are no updates available I am using Numbers 09 version 2.1. I thought when I downloaded Mavericks I got the latest version, but apparently not.
normfromnc

When you next have the problem, note the exact time: hour, minute, second.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console 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 Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above. Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first. Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough. It is never necessary or helpful to post more than about 100 lines. "The more, the better" is not the rule here.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

I am running Safari 5.1.7 on 10.6.8 and experiencing frequent freezes and crashes, how do I solve this problem? Hal Harris

I am running Safari 5.1.7 on 10.6.8 and experiencing frequent freezes and crashes, how do I solve this problem?
Hal Harris

The best way is to post the crash log next time it crashes. That will contain specific information that will help find the problem. Logs are cryptic but there are people here who can make some sense of them.
I'm running 5.1.7 under 10.6.8 on both my iMac and MacBook Pro and it is completely stable. However I have no extensions installed. Incompatible extensions are a common source of Safari instability

IMac 27" frozen screen

just can not identify in what situations, but when my Mac has a frozen screen, I have no other alternative but to push the off button. The most ironic thing is that, clearly the internet connection keeps. I know this because I'm usually listening to online radio. When it occurs, I can not change my dashboard and also can not switch to another application because I can not use the keyboard and the mouse click does not work.
I am currently using Mac OS X Yosemite, but the problem has persisted for several other versions of the system.
I

I have exactly the same problem with a my 27" iMac of exactly the same vintage and configuration. It freezes this way anywhere between once a day and once a week.
I also see an additional variation of this crash, where when I wake up the machine from sleep, the backlight comes on, but no image is drawn. It glows gray. In the form of the crash that Helton reports, the cursor moves with the mouse, but nothing responds to clicks. I've also seen where streaming (and I believe locally stored iTunes) continue) to play. I am not sure whether the machine remains visible on the network.
I have never used any anti-virus on this machine. In a desperate attempt to isolate the problem I have done the following:
Fresh clean install of Mavericks onto a new, external Firewire 800 drive
After the install, I only re-installed the apps I use frequently: iTunes, Aperture, Chrome, Adobe Flash and Microsoft Remote Desktop, HP printer driver, TextWrangler. That's it.
Replaced 3rd-party memory I had installed with the original factory installed 2x 2GB DIMMs
Blown out the bottom vents and the circular vent in back with canned air
Unplugged the external DVI monitor I was using
Done the usual setting resets via the startup
Ran the built-in memory checker at startup
Ran checks on the harddrives for errors, permission problems, etc...
Wiped the internal drive clean, and did a fresh install on that
The crashes still occur.
The system does not appear to be hotter than normal. I used to have a widget that monitors temps (but doesn't change fan speeds).
This system has the Seagate 1TB harddrive that was eligible for a recall, but I didn't do it. The drive has never reported any SMART errors.
Since you are still seeing crashes after updating to Yosemite, I'm not sure what to try next, myself. I've considered pulling it apart to make sure there is no dust in the fans. It doesn't seem to be overheating, but despite the sensors, there doesn't seem to be a way to record a regular temperature history to see what the temps were like at the moment of the freeze.
Of course, it's out of warranty. It's five years old, but it's plenty fast enough for me. The screen is still gorgeous. If it weren't for this, I'd use it for at least another two years. I was thinking of getting a MacMini to plug into it and use the iMac as a screen, but the new MacMinis are dual-core. It wouldn't be a nice leap in performance.

TS1717 I can't open iTunes. I'd been experiencing frequent freezes when I was using the iTunes store the past few days. What can I do to open iTunes?

? I can't open iTunes at all. When I hit the icon, it lights up but doesn't engage to open the program. The past few days I'd been experiencing frequent freezes when using the iTunes Store. Any ideas for how to open iTunes?

I would copy over the entire thing if you have room. With iTunes 10.4 though, you can download any previous iTunes purchases you have made in the past with your current iTunes account. While in iTunes, look at the left hand side of your screen and select "Purchases" and look at the bottom right corner of the screen and select "Download Previous Purchases". If you have an iPhone, iPod and/or iPad...you can do the same thing from each device. Nice new feature...just remember that those ripped CDs need a back-up!!! Enjoy...

Windows XP Mode in Win7 off-screen?

When I open Windows XP Mode in Windows 7 Enterprise the icon appears on the task bar but it can not be made to open on-screen, nor can it be closed by using the close-window selection on the drop-down screen.
Hitting alt/tab shows it with the other running programs, but clicking on it only returns to the desktop.
Clicking on the task-bar icon causes a rapid transparent box to move to the lower right side of the screen very rapidly, clicking again makes the same transparent box to move rapidly to the task-bar icon.
Could it be that the window somehow moved off the screen? If so, how to get it back. I've tried deleting the .vsv file, but that does not cause any apparent change.
Anyone heard of this before - and hopefully a fix?
Aboonah

No help there...and this is a single-monitor set-up.
Another thing I experienced since posting the original question: I tried to simply open the application I need to run - by clicking on it in the Virtual XP Applications folder.
The application opened and ran. I could read and write data, but could not print. When I attempted to print, the application crashed each time.
I also cannot close the XP virtual machine icon on the task-bar. I have to use task-manager to close the process.
Aboonah

I have an 27 inch apple iMac 2010. Can I upgrade by buying a Mac book pro and use plug in and use the iMac as a screen only?

I have an 27 inch apple iMac 2010. Can I upgrade by buying a Mac book pro and use plug in and use the iMac as a screen only?

Yes your 2010 supports Target Display Mode using MiniDisplay Port input.
check out FAQ #4 > Target Display Mode: Frequently Asked Questions (FAQ)

Just got the new iMac. The screen keeps jumping to the launch pad screen randomly when I am working in other applications. Please help.

Just got the new iMac. The screen keeps jumping to the launch pad screen randomly when I am working in other applications.
I have the magic mouse, don't know whether it is something to do with that? Any ideas?

If gumsie's suggestion isn't the answer, try logging into another account, like Guest, and see if you get the same behavior. You may need to clean the windows on the bottom of the mouse.

Windows 7 on iMac experiencing frequent screen-wrap?

Similar Messages

Maybe you are looking for