Attention: HPIO Trap Monitor wake issues on Leopard

Guys, I've never had any sleep issues with my Intel iMac before; but it seems like the latest 10.5 updates are NOT compatible with the HPIO Trap Monitor, which is part of the software package installed for HP all-in-one printers on Macs...
In 2 or 3 occasions during the last couple of months, I wasn't able to wake my iMac from sleep, having to resort to a hard reboot. It's nothing with 10.5.7, because this ALSO happened with 10.5.6.
After some analysis of console messages, I discovered the following:
Process: HPIO Trap Monitor [97]
Path: /Library/Printers/hp/hpio/HPIO Trap Monitor.app/Contents/MacOS/HPIO Trap Monitor
Identifier: HPIO Trap Monitor
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1]
Date/Time: 2009-05-17 17:34:41.205 +0200
OS Version: Mac OS X 10.5.7 (9J61)
Report Version: 6
Anonymous UUID: 71B7EADA-0821-4669-9BC2-2CD6D1E42348
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
My question: my printer works fine so far, but I am afraid this driver or specific process is not compatible anymore with Leopard...what happens if I erase it from my system? Thanks in advance!

Reinstall the latest HP software. I have no such crashes with my Photosmart 4280 AIO attached to my iMac. Version 2.6.0 runs without issues.

Similar Messages

HPIO Trap Monitor

I keep getting a popup message that says, "The application HPIO Trap Monitor quit unexpectedly. "Mac OS X and other applications are not affected." I can't close it out. Should I delete this dialog from Finder to get rid of it? I don't want to delete my printer software by accident.

Aren't us HP printer owners lucky (and I got mine from an Apple Store)... I found the following on an Apple support site (see next to last paragraph). I don't know if this applies to our HPIO problem.
Labeled "Mac OS X 10.5 Leopard build 9A559," the new release came just hours after the Cupertino-based company issued two minor updates to the previous full-sized build (9A527), both of which were aimed at testing the system's automated Software Update mechanism.
Developers who successfully applied both of the automatic software updates saw their version of Leopard upgraded to build 9A528d. By contrast, Friday evening's release of build 9A559 was issued as a 6.5GB web download to all Apple Developer Connection members, whether they had installed the previous builds or not.
People familiar with the new release say it contains only two known issues and may be considered the first of several release candidates, the latter of which would eventually be declared Gold Master and shipped off for duplication and retail packaging.
Of the two known issues in build 9A559, one relating to archive installs appears to be the most critical. Those people familiar with the matter say archive installs from Tiger to Leopard may fail on some Power PC systems if the user attempts to preserve their user settings. To remedy this problem, Apple reportedly suggests that users perform an upgrade install, a clean install or opt out of preserving user settings.
The second known issue affects users who have HP printers connected to their system or are upgrading from a Tiger system with an HP printer that had previously been configured. Though Apple did not specify the root of the problem, it recommended that these users perform a custom install of Leopard and de-select the HP printer drivers in the installer. The proper drivers would be delivered via Software Update following the Leopard install, the company added.
With a self-imposed October launch timeframe quickly approaching, Apple would need to declare a build of Leopard Gold Master sometime in the next three weeks in order to meet the tail-end of that deadline.

The application HPIO trap monitor quit unexpectedly?/??

I just updated to Leopard and I repeatedly get the error message box that says "The application HPIO trap monitor quit unexpectedly" Then it gives me three choices..ignore which keeps it offf for a few minutes and then it pops back up, report, same thing and relaunch..it immediately comes back. Does anyone know what the HPIO trap monitor is and what I can do to stop this super annoying box from popping up ? btw Happy New Year

It's the startup item associated with an HP printer—HP input/output trap monitor. Your best bet is to reinstall the latest HP software available for your printer. I'm running an HP PSC 1510 AIO and the trap monitor daemon isn't crashing. Downloads at http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?lc=en&cc=us&dlc=en&product=4 28800&os=219&lang=en&

HPIO Trap Monitor nightmare . . .

Since upgrading my iMac to Leopard I keep getting a persistant box that says "The application HPIO Trap Monitor quit unexpectedly" (Ignore, Report, Relaunch). No matter what I do, 30 seconds later the box re-appears. I researched this a bit and found a "fix" which involves making some HP folder into an "app". This did not fix the problem. I've written to HP and Leo LaPort but have yet to receive a response. Does anyone have a real fix for this? Thanks!

Search. There are multiple threads here on this with suggestions, and I found an answer for the previous one with a Google search; it was the top result.

Problem re-installing my HP photosmart C4280, HPIO Trap Monitor quits

I had my HP C4280 installed on my intel Mac and it worked fine. We moved and I did nothing more than disconnect it, when I set my Mac back up the printer wouldn't work. So, I uninstalled it and reinstalled it then right after the software installed I got a pop up box that read, the application HPIO Trap Monitor quit unexpectedly, I reported it to Apple and then I couldn't finish the installation process because when it says to choose your printer from the list, there is nothing on the list. I have uninstalled and reinstalled many times and get the same results. I would really appreciate any help you guys could give.
Thanks, Lee

Go to http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=mp-55008-2 &lc=en&cc=us&lang=en&os=219&ts=true&product=3192753&dlc=en and download the HPInstaller_PSC4200v9.7.1 installer. Install it and restart. Mine works without any issues.
BTW, take a few minutes to fill out your My Settings and adding your computer/OS info so we don't have to guess what you're running.

What is HPIO Trap Monitor

"The application HPIO Trap Monitor quit unexpectedly."
I got this message over and over again. If I choose relaunch, the message appears again. If I choose Ignore, it shows up minutes later. What is it? And how do I get rid of it?

It's a Hewlett Packard thingy. Go here and read about it and it's problems: http://discussions.apple.com/thread.jspa?threadID=1198099&start=0&tstart=0

HPIO trap monitor quit

I keep getting this error message. the computer asks me to either ignor, relauch or report. No matter what I do it continues to come up. Any recommendation. I just installed Leopard how did that effect this message coming in

Same happens here since I installed leopard, but only on the iMac, not on my powerbook. very strange and have not found any way to deal with it. Only thing currently to avoid this is to put the message somewhere where it doesn't disturb, no new message would come.
If you found a way to deal with it, please let me know - very keen to get this fixed.

HPIO trap message - what does it mean?

I keep getting some sort of error message about an "HPIO Trap" whenever I restart my Mac. I'm pasting below the entire report. Anybody know what this means and what I can do about it?
Process: HPIO Trap Monitor [142]
Path: /Library/Printers/hp/hpio/HPIO Trap Monitor.app/Contents/MacOS/HPIO Trap Monitor
Identifier: HPIO Trap Monitor
Version: ??? (???)
Code Type: PPC (Translated)
Parent Process: launchd [1]
Date/Time: 2008-11-16 11:50:36.418 -0800
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6
Exception Type: EXC_CRASH (SIGTRAP)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 ??? 0x801a308a 0 + 2149200010
1 translate 0xb80ecef0 gettimeofday_wrapper + 38072
Thread 1:
0 translate 0xb81529ef spinlockwrapper + 90931
1 translate 0xb8183633 CallPPCFunctionAtAddressInt + 169935
2 translate 0xb81861e2 CallPPCFunctionAtAddressInt + 181118
3 translate 0xb80dfb0b 0xb8000000 + 916235
Thread 2:
0 translate 0xb81529ef spinlockwrapper + 90931
1 translate 0xb8183633 CallPPCFunctionAtAddressInt + 169935
2 translate 0xb81861e2 CallPPCFunctionAtAddressInt + 181118
3 translate 0xb80dfb0b 0xb8000000 + 916235
Thread 3:
0 translate 0xb81529ef spinlockwrapper + 90931
1 translate 0xb8183633 CallPPCFunctionAtAddressInt + 169935
2 translate 0xb81861e2 CallPPCFunctionAtAddressInt + 181118
3 translate 0xb80dfb0b 0xb8000000 + 916235
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x810e9a34 ecx: 0xb7fffa6c edx: 0x801a308a
edi: 0x80802e00 esi: 0x00000005 ebp: 0xb7fffa98 esp: 0xb7fffa6c
ss: 0x0000001f efl: 0x00000246 eip: 0x801a308a cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0xa09cd214
Binary Images:
0xb8000000 - 0xb81d7fe7 translate ??? (???) /usr/libexec/oah/translate
Translated Code Information:
NO CRASH REPORT

Actually Human wrote:
I keep getting some sort of error message about an "HPIO Trap" whenever I restart my Mac.
That's not an error message, but a message that the Hewlett Packard Input/Output Trap Monitor app crashed. I haven't seen any of those for over a year. Follow Barry's advice and update to 10.5.5 and then install the HP Printer Driver update http://www.apple.com/support/downloads/hpprinterdriver111.html

Monitor wake up issues

I am having inconsistent monitor wake up issues. If the CPU is on and past the bios boot and THEN I turn on the monitor all works properly. However, the monitor will NOT come out of power save / hibernation mode. I have tried different monitors with the same behavior and am on my second ATI 9600 Pro 128MB graphic card. I have installed the latest Catalyst drivers (4.0) and flashed the MoBo bios (amibos 3.31a) and still no change in the effect. I am suspect that it is some bios setting but can't figure out what the issues are. As a side note, I have had twice in about 40 boots an error: "Dram timing is too tightly so reload timing". The DRAM timing configuration is enabled by SPD at 3-3-3-8-8 (unchangeable in current mode).
Suggestions greatly appreciated!
SYSTEM:
P4 2.8GHz w/ 800M and 512K
2 DDR 256 / DDR400 CL3 PC3200 (Kingston)
ATI Radeon 9600 Pro 128MB
MSI 865PE Neo2-PLS
Viewsonic E90f 19" monitor
Windows XP Pro SP1.1a

You can set your DDR timings manually by disabling SPD in BIOS. Before you do that, be aware of the exact description of your memory sticks and try to find out in Kingston Website about possible timing values.
About the problems with the Monitor, in BIOS you should have a menu 'Power Management Features'. If you have
ACPI Standby State choose 'Auto'
Re-Call VGA BIOS at S3 resuming choose 'Disabled'
Power Management/APM choose ' Enabled'
Suspend Time Out 'Disabled'
On this menu if you have a Submenu 'Set Monitor Events', get in, and if you have something like
FDC/LPT/COM Ports choose 'Monitor'
Primary Master IDE 'Monitor'
Primary Slave 'Ignore'
Secondary Master IDE 'Monitor'
Secondary Slave IDE 'Ignore'

Creating SNMP Trap Monitors in 2012 R2

Hello,
For the past week or so I have been attempting to create a MP for my company's UPSs to be monitored in SCOM 2012 R2. I have created a custom MP with custom datasources and objects. All seems to go according to the plan until I attempt to create a SNMP
Trap monitor for those objects. I am able to verify that the device is discovered and is sending the traps successfully with a view. The problem seems to lie within the setup of the monitor. I have followed the steps as much as I can from this page http://technet.microsoft.com/en-us/library/hh563870.aspx
to create a monitor that will be triggered by an incoming trap saying the UPS is on Battery Power.
This is the initial or trigger event information received by SCOM:
<EventData>
<DataItem type="System.SnmpData" time="2014-07-03T08:48:07.6990732-07:00" sourceHealthServiceId="26DF02E5-DEA0-BED0-443B-3605A05D4790">
<Source>10.51.85.40</Source>
<Destination>127.0.0.1</Destination>
<ErrorCode>1</ErrorCode>
<Version>1</Version>
<SnmpVarBinds>
<SnmpVarBind>
<OID>.1.3.6.1.2.1.1.3.0</OID>
<Syntax>67</Syntax>
<Value VariantType="19">17567220</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.6.3.1.1.4.1.0</OID>
<Syntax>6</Syntax>
<Value VariantType="8">.1.3.6.1.4.1.318.0.5</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.4.1.318.2.3.3.0</OID>
<Syntax>4</Syntax>
<Value VariantType="8">UPS: On battery power in response to an input power problem.</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.6.3.1.1.4.3.0</OID>
<Syntax>6</Syntax>
<Value VariantType="8">.1.3.6.1.4.1.318</Value>
</SnmpVarBind>
</SnmpVarBinds>
</DataItem>
</EventData>
This is the event should signal that everything is operating normally once again.
<EventData>
<DataItem type="System.SnmpData" time="2014-07-03T08:48:12.9133769-07:00" sourceHealthServiceId="26DF02E5-DEA0-BED0-443B-3605A05D4790"><Source>10.51.85.40</Source>
<Destination>127.0.0.1</Destination>
<ErrorCode>1</ErrorCode>
<Version>1</Version>
<SnmpVarBinds>
<SnmpVarBind>
<OID>.1.3.6.1.2.1.1.3.0</OID>
<Syntax>67</Syntax>
<Value VariantType="19">17567730</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.6.3.1.1.4.1.0</OID>
<Syntax>6</Syntax>
<Value VariantType="8">.1.3.6.1.4.1.318.0.9</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.4.1.318.2.3.3.0</OID>
<Syntax>4</Syntax>
<Value VariantType="8">UPS: No longer on battery power.</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.6.3.1.1.4.3.0</OID>
<Syntax>6</Syntax>
<Value VariantType="8">.1.3.6.1.4.1.318</Value>
</SnmpVarBind>
</SnmpVarBinds>
</DataItem>
</EventData>
You may notice that these traps are being sent as SNMP v1. I am unable to change that on the UPS so i have modified the monitors to account for that. Here is the code for the monitor:
<UnitMonitor ID="UIGeneratedMonitorc2c65f3c85fe42f48ce8d2580c57bbae" Accessibility="Public" Enabled="true" Target="APC.MP.UPS" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="SNL!System.NetworkManagement.SnmpTrapProvider.2SingleEvent2StateMonitorType" ConfirmDelivery="false">
<Category>Custom</Category>
<AlertSettings AlertMessage="UIGeneratedMonitorc2c65f3c85fe42f48ce8d2580c57bbae_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId2750c1ab2cd14b4a8a8e9f4633eba0b0" MonitorTypeStateID="SecondEventRaised" HealthState="Success" />
<OperationalState ID="UIGeneratedOpStateId5753748399984d08953c1a46895df99c" MonitorTypeStateID="FirstEventRaised" HealthState="Warning" />
</OperationalStates>
<Configuration>
<FirstIP>$Target/Property[Type="SNL!System.NetworkManagement.Node"]/SNMPAddress$</FirstIP>
<FirstVersion>1</FirstVersion>
<FirstOIDProps>
<OIDProp>.1.3.6.1.4.1.318</OIDProp>
</FirstOIDProps>
<FirstExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">.1.3.6.1.4.1.318.0.5</Value>
</ValueExpression>
</SimpleExpression>
</FirstExpression>
<SecondIP>$Target/Property[Type="SNL!System.NetworkManagement.Node"]/SNMPAddress$</SecondIP>
<SecondVersion>1</SecondVersion>
<SecondOIDProps>
<OIDProp>.1.3.6.1.4.1.318</OIDProp>
</SecondOIDProps>
<SecondExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">.1.3.6.1.4.1.318.0.9</Value>
</ValueExpression>
</SimpleExpression>
</SecondExpression>
</Configuration>
</UnitMonitor>
I tried the following things while attempting to troubleshoot this issue:
Leaving First
SnmpTrapProvider and Second
SnmpTrapProvider blank while creating the monitor.
Adding "" and also '' around the value as it is a string and perhaps that was the cause.
Changing the First and Second SNMPTrapProvider to .1.3.6.1.6.3.1.1.4.1.0 since that is the specific OID I am looking for the value of.
Reading every page of the internet and bashing my head on the keyboard.
I am guessing that the issue will reside in the the monitor creation and definition, but I have not found anything that clearly describes how to fill out the SNMP Trap Monitor wizard given the trap info. Especially since the trap I am receiving does
not seem to contain the usual OID with a common Int or string value. Hopefully someone can provide assistance as I am nearing my wits end with this problem.

Firstly, thank you Michael Skov, knowing that the First and Second SnmpTrapProvider or <FirstOIDProps> in the xml, needed to be blank got me pointed in the right direction. I figured I would come back and share my final working code snippet in case
others run across a similar issue.
<UnitMonitor ID="UIGeneratedMonitorf9f671e5456c44fd807d6ec2bd09621d" Accessibility="Public" Enabled="true" Target="Disc!APC.Disc.UPS" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="NetworkManagement!System.NetworkManagement.SnmpTrapProvider.2SingleEvent2StateMonitorType" ConfirmDelivery="false">
<Category>Custom</Category>
<AlertSettings AlertMessage="UIGeneratedMonitorf9f671e5456c44fd807d6ec2bd09621d_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Warning</AlertSeverity>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId8700c95344254f87a60c92d30d4a3953" MonitorTypeStateID="SecondEventRaised" HealthState="Success" />
<OperationalState ID="UIGeneratedOpStateId7bf68c6cfe3d4faabe83e630781c7327" MonitorTypeStateID="FirstEventRaised" HealthState="Warning" />
</OperationalStates>
<Configuration>
<FirstIP>$Target/Property[Type="NetworkManagement!System.NetworkManagement.Node"]/SNMPAddress$</FirstIP>
<FirstVersion>1</FirstVersion>
<FirstOIDProps />
<FirstExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">.1.3.6.1.4.1.318.0.5</Value>
</ValueExpression>
</SimpleExpression>
</FirstExpression>
<SecondIP>$Target/Property[Type="NetworkManagement!System.NetworkManagement.Node"]/SNMPAddress$</SecondIP>
<SecondVersion>1</SecondVersion>
<SecondOIDProps />
<SecondExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">.1.3.6.1.4.1.318.0.9</Value>
</ValueExpression>
</SimpleExpression>
</SecondExpression>
</Configuration>
</UnitMonitor>

Trap monitor?

I finally decided to install Leopard (successfully enough that I'm posting this from the computer I just installed it on), and got the error "Trap monitor unexpectedly quit" when the installation was done. I had walked away while it was installing, so don't know if anything else led up to this, but it kept reappearing after I clicked "relaunch" and only went away when I told it to ignore it. So, three related questions:
1) What IS a Trap monitor?
2) Is it something important, or just an accessory I can safely function without?
3) If it's important, how do I fix whatever it is that's crashing? (Or...If it's not important, can I just trash it so I stop getting this error, and where do I find it?)
I'll hold off on setting up Time Machine until I know if this is something that's going to require another installation so I don't lose my backup of my old files on the external drive. Hopefully this is something minor (keeping fingers crossed!)

First rule for using these forums is to search them. A search for *trap monitor* brings up http://discussions.apple.com/thread.jspa?messageID=5817251

HP Trap Monitor taking a lot of resources

I have a color laserjet 1312nfi. I looked at my activity monitor and noticed "Trap Monitor" taking about 350mb of memory. I killed it, launched some hp programs and printed again, but it hasn't come back. Does anyone know what Trap Monitor is and what I can do to prevent it from coming back in the future?

Hello the:
Direct answer to both of your questions - no. However, unless you are having some sort of performance problem, why do you care? You did not indicate why you were looking at the activity monitor (which should be, IMHO, used only when there is some sort of performance issue).
Barry

Mac Pro with Dell UP2414Q Sleep Wake Issue

Hi,
I have *two* Dell UP2414Q displays connected to a new Mac Pro, both using Display Port 1.2 (MST) setting in order to get 4K @ 60Hz.
Works fine. Except Google Chrome which is really lame at redrawing all these pixels when you scroll up/down.
The issue is: when the displays go to sleep for a longer period of time (actually it's probably when the Mac Pro itself has gone to sleep) and I wake the system up, the Dells sometimes won't wake up!
And if I start fiddling with the display buttons I will get a half image (left half of the screen). Same problem on each display except sometime it's the first one that doesn't wake up, sometimes it's the second one and sometimes it's both. Unfortunately the situation where they both wake up is extremely rare
Has anyone else had similar troubles?
Note: I have had similar sleep wake issues with just one UP2414Q connected.
I'm running OS X 10.9.4 (of course).
I'm also having a 3rd smaller display connected though a DVI adapter. That one wakes up 100% of the time. I previously had 3 of these and they did always wake up all 3 without issues.
-Francois.

I have this issue with the UP2414Q monitor and my new Mac Pro . . . . . and then some.
I started by losing the right half of the screen on wake up. After about two months of use, my monitor has developed a fault where both sides of the monitor are displayed but at seemingly very different calibrations. The left half is contrasty and the right half seems to be correctly matched to my working profile. This is using the display port connections. HDMI doesn't have this problem but it also won't run at 60Hz, which was an important factor in my choice of this monitor.
At this point I contacted both Apple and Dell. Although I have had quite a few different Apple support staff over a period of a week or so, they did keep good notes, were very patent and seemed to take a genuine interest into trouble shooting it. I cannot say the same for Dell. At first they did ask questions and did the right thing by sending a replacement. It worked fine on display port, then on HDMI but when I connected it back to display port the split screen problem occurred on the brand new replacement one too. After a day of fiddling with connections it went back to displaying correctly with all connections and has not reverted but it does now have the dead right halve on wakeup more frequently than before. I reconnected the original monitor but that has the split screen problem and I can't find a way of getting it to go away. It is unusable.
This incident with the replacement monitor was five days ago. In that time I have tried to contact Dell support by the original e-mail of the technician that initially helped and by phone, through the support number. The email gets the repeated response "Dear Sir/Madam, Thank you for your email. I have left for the day, hence my reply will be delay". It happens in the mooring or the afternoon. A phone call to Dell's support number always starts with a promise to be transferred to the technician dealing with my case and, without fail ends by me being left on hold indefinitely with a terrible one minute audio loop followed by a repeated promise of the next available agent. I once waited over 30 minutes, just to test it. I live in Australia but this was clearly an international call centre. Dell obviously have no intention of dealing with my case. They will have to talk soon though because I still have an extra one of their monitors.
Unless there is a firmware update for this monitor, I would strongly advise against buying one for a Mac, or any Dell product for that matter.

Connecting external NEC PA271W via Displayport cable to MBPr has sleep/wake issues

I am experiencing strange sleep/wake issues after connecting my NEC PA271W 27'' external monitor via a mini-displayport to displayport cable to my MBPr.
Waking up from sleep mode, the resolution of my monitor would be set to 1440x768 instead of the proper 2560x1440 and I always have to go to system settings to get it right.
NEC claims this may be due to cable issues and Apple using a "wrong" mini displayport standard but I have tried 4 different cable manufacturers and this is just strange.
Anybody else experiencing similar issues?

I am experiencing strange sleep/wake issues after connecting my NEC PA271W 27'' external monitor via a mini-displayport to displayport cable to my MBPr.
Waking up from sleep mode, the resolution of my monitor would be set to 1440x768 instead of the proper 2560x1440 and I always have to go to system settings to get it right.
NEC claims this may be due to cable issues and Apple using a "wrong" mini displayport standard but I have tried 4 different cable manufacturers and this is just strange.
Anybody else experiencing similar issues?

Constant/Random Sleep/Wake issues

I'm on a new 17 inch MacBook Pro and I've been having problems ever since October with waking issues. Most of the features on the MBP work completely fine until I decide to close the lid and let the mac fall asleep.
One of the random issues I receive is the inability to wake from sleep.
I open the lid hoping the mac will start up as it should, but about 70% of the time the screen stays dark while I still hear the fans and machinery within it work.
I usually have to perform a hard restart by holding down the power button to get a fully functional macbook pro again...
The second issue occurs when I am actually ABLE to wake the Macbook Pro from sleep. The mouse turns horribly unsmooth and jumpy and programs seem to work slower than they normally should.
I experience a few other random problems in addition to these wake issues, but these are basically the main ones.
The only solution I have right now is holding down the power button and performing a full restart, risking closing and deleting all previous programs I was working with...
Can somebody show me a solution to this problem?
Would a clean re-install of Leopard help? I've tried it once before but more and more new problems keep showing up...
Anyways, I hope I can get help on this subject
Thanks

Same issue with my 17". The mouse problem is very annoying. If your screen does not turn on after it has fallen asleep, I push the Screen Brightness up Function key and after about a minute or less the screen makes all the sounds like you pushed the buttons or button all at once and resumes normal functionality. If you have the sluggish mouse, I just insert a wired mouse and it moves fine. As soon as I move my finger over the trackpad the sluggishness continues, but only on the trackpad.
I hope Apple has an Update for this issue soon it happens very frequently. As a matter of fact, right before I typed this message.

Attention: HPIO Trap Monitor wake issues on Leopard

Similar Messages

Maybe you are looking for