Screen sharing in listen mode only

Hello readers
I try to use either VNC or "Screen sharing" to connect to a remote mac Mini.
Both works. If I use a VNC clienet, I can set "Observing Mode", which does prevent all mouse and keybord action to be sent to the remote host. Unfortunately I can't do that with "Screnn sharing". I prefer this Mac OS X tool as I can easely use it in a bash script to do the connection automatically. I didn't find a VNC client which is scriptable either by AppleScript or command line.
So If someone can tell me, if it is possible to change the behavior of "Screen sharing" to "Obeserve mode" is appreceated.
Kind regarsd from Switzerland
Thoams Thaler
Message was edited by: Thomas Thaler1

I have no idea if it works for what you want, but have you looked at this hint?
http://www.macosxhints.com/article.php?story=20071127183240696
Scott

Similar Messages

  • Screen sharing only in one way

    Hi, I'm doing screen sharing everyday -mostly for helping other with their macs- with no problem but with one person (an uncle of mine).
    He uses a new 20" iMac (the late one), we can text chat, videoconferencing, audioconferencing and screen sharing in one way, I can let him control my mac but it's impossible to let me control his Mac.
    The fourth button in ichat (where to ask for permission or give permission to screen sharing) is half enable, only one of the options is enabled to click on, the option for "ask for screen sharing" isn't. So I can give him permission to control my mac but not to control his mac.
    How can this be possible? I asume screen sharing works in the same protocols in both ways, above all when we can do video and audio conferencing.
    Thanks in advance for your help

    Hi Ralph,
    When you have ticked the screen sharing option in iChat>video>screen sharing and your buddy "high lights" (one click) your screen name the screen sharing icon will be displayed in black on his end indicating "enabled".
    This way he can ask for your permission to share your screen.
    When your contact has not ticked the screen sharing option the screen sharing icon in your contact list will be grey.
    When your contact has ticked the screen sharing option as well the screen sharing icon in your contact list will be black as well.
    Of course all other requirements for iChat screen sharing have to be met.
    More important: I wish you a very happy new year!

  • Screen sharing- not showing who is on my mac

    i've got screen sharing setup on all our macs and works great- HOWEVER, on occasion, a number of things can happen:
    1- i am unable to access a computer even though i accessed it earlier; i need to restart the computer and then it works
    2- when i shut down the computer, a message pops up that 2users are accessing the computer though there is only one or even none on the network that can do so and the remote computer icon shows only 1computer address or no icon present (does that mean someone is hacking my computer?)
    3- when i shut down the computer, a message pops up that there is a user and there is no remote computer icon visible (again, is someone hacking my computer?)
    2 and 3 above concern me the most especially since at times i don't see the screen sharing icon, so don't know who's accessing the computer... and no one knows how to access my main computer which is where this problem occurs. 1 happens on the other macs when trying to access the main computer.
    i've got my network running on a timecapsule with WPA2 personal security, password for timecapsule disk, password for computers, screen sharing set to admin only with no other people listed for access so a bit concerned about this would GREATLY appreciate the help/information anyone has!
    thanks
    ps- i also had this problem in snow leopard

    The upgrade just showed up for me when the criteria was met. Try reindexing your Mac.
    Spotlight: How to re-index folders or volumes -
    http://support.apple.com/kb/ht2409

  • Screen Sharing Fails After 5 Seconds

    Heres the deal.
    1) Both running Snow Leopard.
    2) New Macbook Pro and New iMac top of the line.
    3) Fast Bandwidth speeds.
    4) Florida <--> Utah.
    5) Screen Sharing not working! Steve Jobs ***!
    Can anyone help with this issue? And Ralph Johns, if you have any advice please share. I just dont want to hear how it works on your G4/1Ghz Dual Processor! That just wouldn't really help.
    Sean

    Hi,
    So iChat 5
    Which increment versions ? (if Updated)
    Snow Leopard.
    Update to ?
    Exactly what is "Fast Bandwidth" where you are ?
    In iChat, in the Video menu, have you turned On Screen Sharing ?
    In your routing device have you used UPnP to open the ports iChat uses ?
    Do you get any error message ?
    Does the Connection Doctor say anything in the Errors tab ?
    Do you get the Pop up to Send to Apple (Or not) ?
    My ageing MacBook Pro of only 3 years of age can also Screen Share
    Sometimes I even let it do it to the 8 and 1/2 year old G4/Dual 1Ghz
    Your reason for telling me your 2) is to Say "I have the Latest and Greatest, so it should work".
    My Reason for telling people my G4 can do it is to say "It can be run on anything above a G4/1Ghz Dual processor, so it's not the Mac or the App"
    Notes.
    iChat 4 and 5 use 20 ports to do various bits.
    One of these, that is used during Screen Sharing is Random. Only UPnP will get around this. (Or Port Mapping Protocol on a Apple Base Station).
    My Internet Connection is 8Mbps down (I get about 7.25) and 780 up (I get about 700) and this is average here.
    24Mbps both up and down is about top of the Range. 8Mbps down and 500 up is more common.
    In Australia anything faster than 128kbps outside of a major town is considered fast.
    What is the internet speed like in Utah ?
    Are we talking a town or somewhere a bit more remote ?
    Re 5)
    It's nice that you rate Steve jobs with 3 stars (I presume there are only three stars in your rating system). I don't see what that has to do with Screen Sharing though.
    11:07 PM Sunday; June 13, 2010
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

  • Force curtain mode during screen sharing

    We have an interesting use case. Under normal circumstances when someone goes to connect to a remote Mac OS device with screen sharing the device's screen keyboard and mouse still work. Most sites I've been to have recommended "Pay $80 and get Apple Remote Desktop". We actually do have a license for it here and use it for admin tasks (like, Hey... let me share your screen and help you out with your problem). However, we have another use case... We have a lot of iMacs here at the office. In the event of a snow storm the user wants to work from home. So they set up an SSH tunnel into my network and do a screen sharing session. Another user actually comes in to the office that day and can see everything the person is doing on their iMac (and actually do things to the screen themselves). Our compliance manager is having a fit because of this. Now, I can't force all my users to go out and buy ARD for their personal devices. Even if we did, I can't prevent them from using their normal screen sharing app to connect to their machines instead of ARD. So, ARD isn't an option.
    So, I'm hoping there is another solution to the problem. Questions...
    * Where are the ARD plist files and is there a setting that says "Always use Curtain Mode when connecting to this machine". I can probably use Profile Manager to force Remote Management (versus screen sharing alone) and set the ARD plist file to force curtain mode.
    * Is it better to use "Remote Management" or "Screen Sharing" to accomplish this?
    * Any other alternatives?
    Thanks,
    Scott

    Hi.
    How did you fix your problem?  I have the same issue where the option to "switch to control mode" is greyed out. I have 4 macs at home with the same set up"it looks like the same set up" and it only happens on my new iMac.
    I appreciate your help.
    Yvon.

  • Connect from Windows through screen sharing (VNC) and get out of full screen mode

    How do you get out of fullscreen mode?
    I connect to a OS X Lion computer through a Windows computer (which actually also is remote).
    I use TightVNC software on Windows to connect. It's the only VNC software I am able to connect to OS X Lion with. TightVNC is kind of weak otherwise in the way that it does not have features for OS X targets - like you can't send "command" key pushes, or even Ctrl pushes and other F2 etc keys just don't really work.
    Which means I cannot exit full screened apps by way of Command-F or similar. Moving the mouse cursor to the top of the screen also does not pop down the menu (although on some occasions I have been able to do this, I'm not sure how and it's terribly hard to reproduce).
    I'd need a on-screen way (like a button to click) to get out of full screen mode.
    Any ideas???

    Are you using TightVNC because you found it was the only VNC client that worked well with Mac OS X built-in VNC server?  Or is there another reason?
    Vine Server (aka OSXvnc - free to use the server)
    <http://www.macupdate.com/info.php/id/11283/vine-server-%26-viewer>
    plays nicer with 3rd party VNC clients, so that you could try any number of other WIndows VNC clients.  Maybe one of those will do a better job of sending Command/Control/Option keys.
    But if you do install Vine server make sure you turn off Mac OS X Screen Sharing (and/or Remote Managment) so that you do not conflict with port 5900.  Or via Vine Server configs, tell Vine Server to use a different port number, such as 5901, then make sure you connect to the correct port from your Windows client.

  • IChat screen sharing fails (only screen sharing though)

    I was trying to assist my in-laws the other day and have never used Screen Sharing in iChat before. We started an A/V session (which works fine), but when we started the Screen Sharing session, it dies after about 5 seconds of use. Both sides get the error "no activity after 10 seconds...". Thinking it was an internet thing (perhaps firewall settings), i tried internally on my LAN with a MacBook Pro and a new Mac Mini, same thing. Either way the session is initiated, failure.
    Did some research through these discussions and found the common thread was the UPnP and internal preference settings. Have checked both, they all seem ok.
    Some statistics of my example: (Remote machine) Mac#1 is an iMac G5 20" 2GHz running Snow Leopard fully updated, with Comcast as the IP and an Airport Express as the router. Port Mapping is turned on in NAT, and Screen Sharing is turned on in preferences -> Sharing.
    (Local machine) Mac#2 is a Mac Mini 2.4 GHz Core 2 Duo running Snow Leopard, with Comcast as the IP and a Time Machine as the router. Both settings above turned on.
    (Local machine) Mac#3 is a MacBook Pro 15" 2.53 GHz Core 2 Duo running Snow Leopard (same IP as #2) on the same LAN as #2.
    All 3 accounts are on MobileMe, A/V chats work fine without problems for limitless amounts of time. Have tried screen sharing both ways, same result.
    Here's a log between #2 and #3 fail (sorry for long post):
    Date/Time: 2010-07-08 19:13:41 -0500
    OS Version: 10.6.4 (Build 10F569)
    Report Version: 4
    iChat Connection Log:
    2010-07-08 19:13:31 -0500: 0x11ae38640: State change from AVChatStateConnected to AVChatStateEnded.
    2010-07-08 19:13:31 -0500: 0x11ae38640: Error -20 (No data has been received for the last 10 seconds.)
    2010-07-08 19:13:31 -0500: **[email protected]: State change from AVChatStateConnected to AVChatStateEnded.
    2010-07-08 19:13:31 -0500: **[email protected]: Error -20 (No data has been received for the last 10 seconds.)
    Video Conference Error Report:
    Video Conference Support Report:
    8.275079 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2059 type=2 (00000000/0)
    [Connection Data for call id: 1 returns 1
    9.155420 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2074 type=2 (00000000/0)
    [Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
    9.165268 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [INVITE sip:user@lip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7cc8269d38bfe756
    Max-Forwards: 70
    To: 0 <sip:user@lip:16402>
    From: u0 <sip:user@rip:16402>;tag=457027611
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 1 INVITE
    Contact: <sip:user@rip:55667>;isfocus
    User-Agent: Viceroy 1.4
    Content-Type: application/sdp
    Content-Length: 702
    [v=0
    o=Merricks 0 0 IN IP4 rip
    [email protected]
    c=IN IP4 rip
    b=AS:2147483647
    t=0 0
    a=hwi:1056:2:2400
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 55667 RTP/AVP 110 12 124 3 0
    a=rtcp:55667
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:124 iLBC/8000
    a=fmtp:124 mode=30
    a=rtpID:1740916373
    m=video 55667 RTP/AVP 123 126 34
    a=rtcp:55667
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 55667 VIDEO 55667
    a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
    a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
    a=rtpID:3396090499
    9.165844 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [SIP/2.0 100 Trying
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7cc8269d38bfe756
    To: 0 <sip:user@lip:16402>
    From: u0 <sip:user@rip:16402>;tag=457027611
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 1 INVITE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    9.165935 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [SIP/2.0 180 Ringing
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7cc8269d38bfe756
    To: 0 <sip:user@lip:16402>;tag=116363815
    From: u0 <sip:user@rip:16402>;tag=457027611
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 1 INVITE
    Contact: <sip:user@rip:55051>
    User-Agent: Viceroy 1.4
    Content-Length: 0
    9.176133 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7cc8269d38bfe756
    To: 0 <sip:user@lip:16402>;tag=116363815
    From: u0 <sip:user@rip:16402>;tag=457027611
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 1 INVITE
    Contact: <sip:user@rip:55051>
    User-Agent: Viceroy 1.4
    Content-Type: application/sdp
    Content-Length: 436
    v=0
    o=jmerrick 0 0 IN IP4 rip
    [email protected]
    c=IN IP4 rip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2530
    a=bandwidthDetection:YES
    a=iChatEncryption:NO
    m=audio 55051 RTP/AVP 110
    a=rtcp:55051
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpID:1191125273
    m=video 55051 RTP/AVP 123
    a=rtcp:55051
    a=rtpmap:123 H264/90000
    a=RTCP:AUDIO 55051 VIDEO 55051
    a=fmtp:123 imagesize 0 rules 20:640:480:640:480
    a=rtpID:4102577296
    9.178372 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [ACK sip:user@lip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK323287a4467da958
    Max-Forwards: 70
    To: 0 <sip:user@lip:16402>;tag=116363815
    From: u0 <sip:user@rip:16402>;tag=457027611
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 1 ACK
    User-Agent: Viceroy 1.4
    Content-Length: 0
    9.181889 @:0 type=1 (00000000/0)
    [Bandwidth Detection]
    [Received the first BWD packet from rip:55667]
    9.495818 @:0 type=1 (00000000/0)
    [Bandwidth Detection]
    [Avg=100964.70, NSDev=1.29%]
    9.600142 @:0 type=1 (00000000/1)
    [Bandwidth Detection]
    [Avg=883694.30, NSDev=10.60%]
    9.689564 @:0 type=1 (00000000/2)
    [Bandwidth Detection]
    [Avg=10202609.90, NSDev=206.74%]
    23.854766 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [MESSAGE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK2fe1d4391a735632
    Max-Forwards: 70
    To: u0 <sip:user@rip:16402>;tag=457027611
    From: 0 <sip:user@lip:16402>;tag=116363815
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 1 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 16
    VCRemoteMuted:ON]
    23.861278 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK2fe1d4391a735632
    To: u0 <sip:user@rip:16402>;tag=457027611
    From: 0 <sip:user@lip:16402>;tag=116363815
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 1 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    27.969942 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [MESSAGE sip:user@lip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK38c4bd117f30ee85
    Max-Forwards: 70
    To: 0 <sip:user@lip:16402>;tag=116363815
    From: u0 <sip:user@rip:16402>;tag=457027611
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 2 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 4
    [PING]
    27.972367 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK38c4bd117f30ee85
    To: 0 <sip:user@lip:16402>;tag=116363815
    From: u0 <sip:user@rip:16402>;tag=457027611
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 2 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    30.000459 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [MESSAGE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK4210350f26913012
    Max-Forwards: 70
    To: u0 <sip:user@rip:16402>;tag=457027611
    From: 0 <sip:user@lip:16402>;tag=116363815
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 2 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 4
    PING]
    30.004047 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK4210350f26913012
    To: u0 <sip:user@rip:16402>;tag=457027611
    From: 0 <sip:user@lip:16402>;tag=116363815
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 2 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    31.622031 @/SourceCache/VideoConference/VideoConference-415.22/VCChannel/VCChannel.m:302 type=2 (00000000/0)
    [VCChannel prepareConnectionWithRemoteConnectionData - remote VCConnectionData: 1]
    31.886122 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [MESSAGE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6525ce694ef2153c
    Max-Forwards: 70
    To: u0 <sip:user@rip:16402>;tag=457027611
    From: 0 <sip:user@lip:16402>;tag=116363815
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 3 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 17
    VCRemotePaused:ON]
    31.898618 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6525ce694ef2153c
    To: u0 <sip:user@rip:16402>;tag=457027611
    From: 0 <sip:user@lip:16402>;tag=116363815
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 3 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    32.026459 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [MESSAGE sip:user@lip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7caf68b0330b846f
    Max-Forwards: 70
    To: 0 <sip:user@lip:16402>;tag=116363815
    From: u0 <sip:user@rip:16402>;tag=457027611
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 3 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 17
    [VCRemotePaused:ON]
    32.026863 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7caf68b0330b846f
    To: 0 <sip:user@lip:16402>;tag=116363815
    From: u0 <sip:user@rip:16402>;tag=457027611
    Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
    CSeq: 3 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    57.667457 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2059 type=2 (00000000/0)
    [Connection Data for call id: 2 returns 1
    69.057730 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2074 type=2 (00000000/0)
    [Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
    69.059710 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2266 type=2 (00000000/0)
    [Initiate Conference To User: u0 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
    69.629813 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6d0a0202172485ce
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@rip:55051>;isfocus
    User-Agent: Viceroy 1.4
    Content-Type: application/sdp
    Content-Length: 703
    v=0
    o=jmerrick 0 0 IN IP4 rip
    s=0
    c=IN IP4 rip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2530
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 55051 RTP/AVP 110 12 124 3 0
    a=rtcp:55051
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:124 iLBC/8000
    a=fmtp:124 mode=30
    a=rtpID:2054428442
    m=video 55051 RTP/AVP 123 126 34
    a=rtcp:55051
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 55051 VIDEO 55051
    a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
    a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
    a=rtpID:2001158912
    69.646627 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [SIP/2.0 100 Trying
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6d0a0202172485ce
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 1 INVITE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    69.646674 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [SIP/2.0 180 Ringing
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6d0a0202172485ce
    To: "u0" <sip:user@rip:16402>;tag=74774650
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@rip:55667>
    User-Agent: Viceroy 1.4
    Content-Length: 0
    69.656640 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6d0a0202172485ce
    To: "u0" <sip:user@rip:16402>;tag=74774650
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@rip:55667>
    User-Agent: Viceroy 1.4
    Content-Type: application/sdp
    Content-Length: 434
    [v=0
    o=Merricks 0 0 IN IP4 rip
    s=0
    c=IN IP4 rip
    b=AS:2147483647
    t=0 0
    a=hwi:1056:2:2400
    a=bandwidthDetection:YES
    a=iChatEncryption:NO
    m=audio 55667 RTP/AVP 110
    a=rtcp:55667
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpID:794658613
    m=video 55667 RTP/AVP 123
    a=rtcp:55667
    a=rtpmap:123 H264/90000
    a=RTCP:AUDIO 55667 VIDEO 55667
    a=fmtp:123 imagesize 0 rules 20:640:480:640:480
    a=rtpID:3616868992
    69.656733 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [ACK sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK19b439ee7b1a3a93
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>;tag=74774650
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 1 ACK
    User-Agent: Viceroy 1.4
    Content-Length: 0
    69.660304 @:0 type=1 (00000000/0)
    [Bandwidth Detection]
    [Received the first BWD packet from rip:55667]
    69.975012 @:0 type=1 (00000000/0)
    [Bandwidth Detection]
    [Avg=100985.80, NSDev=2.06%]
    70.079592 @:0 type=1 (00000000/1)
    [Bandwidth Detection]
    [Avg=889226.20, NSDev=6.32%]
    70.150256 @:0 type=1 (00000000/2)
    [Bandwidth Detection]
    [Avg=3506655.00, NSDev=39.71%]
    76.718688 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [MESSAGE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK680d8ec50284d4dd
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>;tag=74774650
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 2 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 16
    VCRemoteMuted:ON]
    76.721457 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK680d8ec50284d4dd
    To: "u0" <sip:user@rip:16402>;tag=74774650
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 2 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    85.580688 @/SourceCache/VideoConference/VideoConference-415.22/VCChannel/VCChannel.m:302 type=2 (00000000/0)
    [VCChannel prepareConnectionWithRemoteConnectionData - remote VCConnectionData: 1]
    85.824030 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [MESSAGE sip:user@lip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK13543b054db63f4b
    Max-Forwards: 70
    To: "0" <sip:user@lip:16402>;tag=1160108830
    From: "u0" <sip:user@rip:16402>;tag=74774650
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 1 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 17
    [VCRemotePaused:ON]
    85.824453 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK13543b054db63f4b
    To: "0" <sip:user@lip:16402>;tag=1160108830
    From: "u0" <sip:user@rip:16402>;tag=74774650
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 1 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    86.016699 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [MESSAGE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK54989b9f3ab846c0
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>;tag=74774650
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 3 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 17
    VCRemotePaused:ON]
    86.021704 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK54989b9f3ab846c0
    To: "u0" <sip:user@rip:16402>;tag=74774650
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 3 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    87.965096 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [MESSAGE sip:user@lip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK4189780d0f2ba815
    Max-Forwards: 70
    To: "0" <sip:user@lip:16402>;tag=1160108830
    From: "u0" <sip:user@rip:16402>;tag=74774650
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 2 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 4
    [PING]
    87.965318 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK4189780d0f2ba815
    To: "0" <sip:user@lip:16402>;tag=1160108830
    From: "u0" <sip:user@rip:16402>;tag=74774650
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 2 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    90.000670 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
    [MESSAGE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK2ad74c4851d9447d
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>;tag=74774650
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 4 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Type: text/plain
    Content-Length: 4
    PING]
    90.004582 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
    [SIP/2.0 200 OK
    Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK2ad74c4851d9447d
    To: "u0" <sip:user@rip:16402>;tag=74774650
    From: "0" <sip:user@lip:16402>;tag=1160108830
    Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
    CSeq: 4 MESSAGE
    User-Agent: Viceroy 1.4
    Content-Length: 0
    Video Conference User Report:
    0.000000 @:0 type=5 (00000000/16402)
    [Local SIP port]
    0.000041 @:0 type=5 (00000000/16402)
    [Local SIP port]
    0.000079 @:0 type=5 (00000000/16402)
    [Local SIP port]
    9.155545 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
    [Remote Router]
    [FULLCONE]
    9.155553 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
    [Remote CommNAT Result: 0x00000102
    9.166348 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2547 type=5 (FFFFFFFF/0)
    [Caller User Agent: Viceroy 1.4]
    9.166350 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceGlobalObjects.m:1670 type=5 (00000000/0)
    [Router]
    [FULLCONE]
    9.166355 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceGlobalObjects.m:1672 type=5 (00000000/0)
    [CommNAT Result: 0x00000102
    9.166754 @:0 type=5 (00000000/1)
    [Accept conference from user]
    [[email protected]]
    9.693286 @:0 type=5 (00000000/60)
    [Detected bandwidth (kbits/s): 929 up, 929 down. (00000000)
    9.698468 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2423 type=5 (00000000/0)
    [Start Conference With UserID: [email protected]]
    69.057850 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
    [Remote Router]
    [FULLCONE]
    69.057857 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
    [Remote CommNAT Result: 0x00000102
    69.059714 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceGlobalObjects.m:1670 type=5 (00000000/0)
    [Router]
    [FULLCONE]
    69.059720 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceGlobalObjects.m:1672 type=5 (00000000/0)
    [CommNAT Result: 0x00000102
    70.160706 @:0 type=5 (00000000/60)
    [Detected bandwidth (kbits/s): 2317 up, 2317 down. (00000000)
    70.164156 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2423 type=5 (00000000/0)
    [Start Conference With UserID: u0]
    Thanks in advance for any suggestions.
    <Edited by Host>

    Hi,
    The "Share a Public IP" can be a bit misleading if your Modem routes (does DHCP itself)
    If you turn this Off (Bridge Mode) the IP address come from the previous device that issues IPs
    From a Cable Modem this is likely to be from the ISP and not likely that you have two Public IPs
    Also the range you describe seems to be from a LAN Device (one that issues IPs in one of three ranges of which 10.xxx.xxx.xxx is one)
    However although I have not seen it done I presume the Apple Airport devices can be set to Manually (Static routing). They can be set to use the 10.xxx.xxx.xxx range as well (with the early ones it was the default range).
    With the Share A Public IP Off I don't think you get a NAT tab on that same screen.
    However in the NAT tab is the Port Mapping Protocol which is Apple's version of UPnP (very basic comparison).
    This should be on for two devices to use the same ports.
    See pic
    If the modem is the device that is issuing IPs then this should have UPnP Enabled.
    You need this rather than Port Forwarding (Or Triggering) as the Screen Share uses a Random port which cannot be forwarded or Triggered).
    A Video that drops out with the 10 secs error points to features in routing devices that "protect" you from getting overloaded with a data stream.
    Look for DOS or SPI (Denial of Service or Stateful Packet Inspection) which may be separate items and standalone or be included in any firewall the device may have.
    At this point I am confused.
    You say Comcast which I believe is cable Only meaning their Modem does not do DHCP and passes the Public IP to the Time Capsule.
    Yet you say the Time Capsule is not doing DHCP (Share a Public IP).
    What do you have at the top of the Screen ?
    This pics shows Ethernet to a Cable Router which gives a Public IP starting 70.xxx.xxx.xxx
    And you also confirm that the Share a Public IP box in the Pic is set to Static Routing and from there you are using the 10.xxx.xxx.xxx range ?
    9:39 PM Wednesday; July 14, 2010
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

  • How to see only one of two displays in Snow Leopard Screen Sharing?

    I am trying to set up screen sharing and find that since I have two monitors working on the machine that I want to connect to, two monitors show up on the client that I am connecting with. This causes a problem in that the scaled screen image that appears on my macbook pro is too hard to see and work on.
    Is there a way to specify only one monitor image to appear in screen sharing?

    On my Mac OS X Screen Sharing display, it has a display selection pop-up in the upper left side of the Screen Sharing display
    Both Displays: 3760 x 1920
    Display 1: 2560 x 1440
    Display 2: 1200 x 1920

  • Screen sharing in full screen mode

    Hi,
    I didn't find a way to scroll a screen from a remote computer that has an applcaction open in full screen mode.
    This is the issue :
    The remote computer has an open application open in full screen mode (ie Safari)
    My computer is also in full screen mode, so the application "Screen sharing" is open in fill screen mode.
    So when in move the tree fingers on the trackpadd this is moving my windows (on the local computer) not on the remote computer...
    Does some one can help me on this ?
    Many thanks

    If you ever find out how, please post the solution here.

  • Start Screen Sharing Connection in Observe Mode?

    Hi,
    I've been able to add the toolbar button to switch screen sharing between the control and observe modes using tips I've found around the web.
    I need to be able to check on what's going on with one of the computers on my home network without taking control of the mouse and keyboard.
    Screen sharing defaults to control mode on connection, does anyone know if there's a way to make it default to observe or if not then to start a specific connection in observe?
    TIA,
    Rob.

    You need Leopard and iChat 4 to work with Shinywhitebox's[Chatter|http://www.shinywhitebox.com/chatter/chatter.html]

  • How to end full screen mode in screen sharing, how to end full screen mode in screen sharing

    I inadvertently hit the 2 little arrows invoking full screen mode while in the screen sharing app. I can't get out of it now, and returned to the windowed mode. Help says to click the 2 little arrows, but I'm not being given 2 little arrows to click.
    I see the screen sharing window, no border, against what looks like a background of denim.
    pressing esc does nothing.
    thanks for clues!
    ray

    When you move your cursor to the top of the screen the local mac's menu bar will appar out of hiding. The "two arrows" you're looking for are in a blue button on the right hand side of this menu bar.

  • ARD 3.2.2 - only screen sharing on 3 clients available

    Hello,
    on our computer lab in my school are installed 32 eMacs (10.4.11). Before updated on ARD 3.2.2 all eMacs can be controlled very well, all informations are available, but now after the update three clients will only connected by direct control tab. The status only shows "screen sharing", and the ip number can be read - nothing else.
    This issue are the same on my MBP 15'' (10.5.5) and the xserve (10.4.11) in the lab.
    I delete the caches in /var/db/RemoteManagement/.... on the xserve, also the ard preferences on the clientes. I also create the lokal ard users new. For a few moments it seems to be okay, but some minutes later the same problems.
    Anything ideas.
    Thanks for all the great workarounds in these discussions.
    And greatings from Germany
    Alfons

    I have the same problem (MacBook 10.5.5, ARD 3.2.2). Some Macs are shown in dark gray in the scanner list. Trying to register them again - before 3.2.2 everything worked fine - the information window scrolls down for a second and scrolls up again.
    The access to the same computers from my earlier machine with 10.4.11 still works fine.
    Does anyone knows a workaround?
    Ruedi Heimlicher

  • Screen sharing stuck on 'Connect...' - but only on one client account. Please help!

    I've got a bizarre problem that cropped up sponaneously, and which I can't for the life of me seem to reslove.
    I have 2 home machines:
    MacBook running 10.6.8  (Server / Media machine)
    MacBook Pro running 10.7.4 (Client machine).  Apple Remote Desktop software is installed on this machine, and connections through it work fine.
    A few days ago, the sidebar "Share Screen..." link on the client machine stopped working.  All I get is the 'Connecting...' dialog box, endlessly.  The bugger of it is that this is only happening with my main account on the client machine. Switching into another (unused) admin account on the client results in the 'Share Screen...' button working as expected.
    I've tried the following cures, found on these forums, to no avail:
    Reset PRAM and NVRAM on both systems
    updated all software
    repaired permissions on both systems
    changed bonjour names of both machines
    rebooter & power-cycled router
    killed the NetAuthAgent process a billion times
    trashed all of the preferences, caches, etc. for screen sharing and remote desktop in the afflicted user account on client machine
    etc. etc.
    As far as screen sharing connection options go, these are my results:
    using connect to server (via finder > go > connect to server), and plugging in the address (vnc://192.168.0.103): works
    launching /System/Library/CoreServices/Screen Sharing.app, and plugging in the above address: works
    connecting via the Apple Remote Desktop software: works
    using the "Share Screen..." link from the Lion Sidebar: DOES NOT WORK and results in the stall mentioned above, constrained to my primary user account on the client machine.
    As mentioned, this was working properly until a few days ago, and stopped spontaneously, with no changes to either system.
    Any help finding a resolution to this would be greatly appreciated; this is driving me utterly bananas .
    -Tim
    Message was edited by: Timoluka

    My wife ran into the very same problem today, while trying to connect Screen Sharing to her media center Mac Mini (server) from a Mac Book Pro (client). I was also unable to connect from my machine as well when logged into my usual account but noticed I had no problem with a Guest User account (as you've described), but had also tried most of the unsuccessful attempts at solutions that you've enumerated.
    Then, I read this very similar thread: https://discussions.apple.com/thread/4131788?start=0&tstart=0
    ...and logged out of our now defunct MobileMe accounts on the affected machines. Upon hitting the "Share Screen..." button again, I was now prompted for a local login and password to the Mini, and once that was input, Screen Sharing connected and started up without any problems! Yes!
    Given the similarity of our problems, I hope this works for you as well. My best guess is that Screen Sharing might be prioritizing the use of MobileMe authentication over local logins and passwords, and some of Apple's recent work in decommissioning MobileMe had unexpected results for folks like us.
    Jim

  • Since me and my mother moved from iChat to iMessage bêta, screen sharing works only one way. I can share my screen with her but not the reverse. When actually what I would like to do is share her screen. Video works fine both ways.

    Screensharing works only one way since we moved from iChat to iMessage bêta. Before that we have never had any problem with screen sharing. We haven't changed anything else, just installed iMessage. What I need to do is share her screen, and the only thing I can do is share my screen...
    Thanks for your help.

    HI,
    On the whole I am finding it very stable.  (it presents the same quirks in the same manner each time)
    It has some things that are more Feature requests than "Bugs" per se about the way it works that I would like to change.
    It can also be difficult to tell exactly what is going on whenyou are hearing about it third hand.
    Sounds like you have a plan.
    8:35 PM      Tuesday; March 20, 2012
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Lion 10.7.3)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • Blue screen at start up,safe mode only, resolved ,what next?

    I got the old stuck on blue screen at start up ,
    would only boot in safe mode , after two afternoons of RAM test , repairing disk permissions , hrdware tests , zapping PRam and the likes to no avail , I finally resolved the problem thanks to a tip from this forum:
    bad video card drivers ( ATIRadeon 8500 ) , after removing them from the extension folder , it boots up! ( I tried to reset the pram , it won't work though , one chime only then nothing).
    so I'm wondering what's next , can i reinstall the video card drivers only ?
    is it the card itself ? (everything looks normal) or should I go for an archive and install ?
    any input would be great,
    Thanks,
    JB

    Hi-
    Jean Baptiste mentioned that he removed extensions for the drivers.
    Removing a conflicting driver is fine as long as the driver specific for the card installed remains.
    In this case, I think it may have been a corrupt driver, rather than a conflicting driver.
    Radeon drivers in OS X have a good track record of compatibility, and such driver conflict is not a historically common occurrence.
    Hard drive maintenance with Disk Warrior is the best way to correct corrupt files, unless bad RAM is corrupting the files.....
    In your case, it shouldn't hurt anything to remove the Radeon 8500 drivers.
    Could it be the driver extensions that are preventing a proper boot. The monitor displays perfectly in safe mode so I don't understand why it would be the video card.
    Booting to Safe mode unloads drivers. Only very basic core graphics rendering drivers are loaded.
    No Quartz/Quartz Extreme, no Core Image, no 3D acceleration, etc.
    This doesn't tax a graphics card.
    Failure to boot, or failure of graphics when drivers are loaded are due to one of two things- corrupt drivers or failing components on the graphics card.
    A reinstall of the OS can rule out the first.
    Installing a different graphics card is the only way to rule out the second.
    Before buying a new card, I would try a fresh OS.
    Installing a new OS on a separate drive, and booting to that is an easy way to test.

Maybe you are looking for