Specific Problem With iChat 4 (Leopard)

Just tried video chatting and screen sharing with a friend, both ways, multiple times. We are both .mac and both using intel iMacs in the same city with the same provider. When I invite him I receive a message that he has cancelled the invitation. On his end it says there was a communication error. Same thing when we try it the other way 'round. I do not use iChat normally but was curious with the new features. Anyone have any suggestions as to what might be wrong?

I have the same issue that's been introduced by Leopard. I've upgraded one machine in the house, my Core Duo 17" MacBook Pro, to Leopard. Once we started testing out iChat, we found that we couldn't start a video chat with the machine running Leopard/iChat 4. The Leopard machine repeatedly gets the "did not receive a response" communication error.
I don't think I can blame this on ports or router configuration or anything else. All machines are connecting through an Airport Extreme base station; I've tried to connect to the MBP with one machine that's also wireless and with one machine that's plugged into the base station.
The other two machines, a Power Mac G5 and a MacBook both running the latest Tiger update, can video chat with each other fine. And the MBP connected happily prior to Leopard.
The G5 is using an AIM login while the MB is logged in via .Mac. I normally use an AIM login on the MBP, but have also tried logging in via .Mac and creating a video chat using Bonjour.
iChat has always had occasional connection problems like this but those were easily solved by one or both parties logging off and back into iChat. That's not working in this case. I was looking forward to checking out the effects and other cool features in iChat 4. So far it's been nothing but a big disappointment.

Similar Messages

  • Problems with iChat 4.0.2 / Leopard / BT HomeHub

    I have a .Mac account and iChat 4 on a iMac running Leopard 10.5.2 and using A BT Home Hub for my internet connection. I am able to have a video chat with my wife who has a Powerbook / Leopard / iChat 4 set up in our house, both using the BT Home Hub. But when I try to set up a video chat with my friend in Copenhagen who has a .Mac account and a Powerbook running Leopard it won't let us connect. It will let us have a text only chat.
    I have read various posts on this subject and changed the firewall to let iChat in, changed the Quicktime streaming to 1.5 Mbps and changed the port in iChat server settings to 443.
    Has anyone else any ideas, I am thinking maybe the Home Hub is the problem as i can connect to my wife's Powerbook on our home network.

    I too am having problems with iChat 4.02 on an iMac running Leopard 10.5.2 as are numerous people having different hardware/software configurations. I've tried some of the suggestions like changing the server settings to 443, and changing the firewall to let iChat in. I believe somewhere, somehow Apple or AOL have changed something that may be causing these problems. I'm not technical enough to go changing a bunch of things and hope it works.
    iChat was working for me about a week or so ago using AIM. I could video chat with a MacBook running 10.5.2, a MacBook Pro running Tiger and a Dell PC. Last night when I tried using AIM and iChat i could only text. However, I could video chat using our dotmac accounts and server settings 5190. But for some reason you aren't able to do that.
    At first I thought it was because I stumbled into using CUPS to get my Xerox color laser printer finally working (after getting the new iMac) by changing localhost:631 to find my printer at port 9100 (whatever all of this means). But deleting the printer didn't restore iChat.
    Someone on this forum suggested that installing Safari 3.1.1 may have somehow caused the problem. Maybe they are on to something!
    My most recent software updates are:
    2008-04-08 15:27:20 -0400: Installed "AirPort Utility" (5.3.1)
    2008-04-08 15:27:24 -0400: Installed "Digital Camera RAW Compatibility Update" (2.0)
    2008-04-08 15:27:48 -0400: Installed "QuickTime" (7.4.5)
    2008-04-08 15:28:32 -0400: Installed "iTunes" (7.6.2)
    2008-04-08 15:30:25 -0400: Installed "GarageBand ’08 Instruments and Apple Loops" (1.0)
    2008-04-08 15:30:40 -0400: Installed "Time Machine and AirPort Updates" (1.0)
    2008-04-08 15:30:45 -0400: Installed "Keynote Update" (4.0.3)
    2008-04-08 15:30:54 -0400: Installed "Front Row Update" (2.1.3)
    2008-04-08 15:31:30 -0400: Installed "Security Update 2008-002" (1.1)
    2008-04-08 15:31:47 -0400: Installed "Safari" (3.1)
    2008-04-16 17:47:07 -0400: Installed "iMac EFI Firmware Update" (1.3)
    2008-04-16 17:47:09 -0400: Installed "Aluminum Keyboard Firmware Update" (1.0)
    2008-04-16 17:47:26 -0400: Installed "Safari" (3.1.1)
    2008-04-23 19:31:31 -0400: Installed "iMac EFI Firmware Update" (1.3)
    At the moment I need my printer working, more than I need iChat. But I do hope someone figures out why this isn't working!

  • Problem with ichat, error message says computer does not support video chat

    I have never had a problem with Ichat until yesterday...now apparently I don't have the video capability.  I am running 10.7.2.  I turned off Facetime.  I now have the video camera image but it won't let me video chat.  Any ideas?

    Hi,
    In iChat open the Connection Doctor (Video menu) and the the Capabilities option
    Are all items showing Green ?
    Try restarting iChat (It re-reads the computers Ability at each launch)
    If that does not work try restarting the Computer.
    Make sure that in iChat menu > Preference > Video Section the Bandwidth Limit is not set to 100kbps (this is too Low for 1-1 video chats)
    Do a Speed test
    "Real World" speeds need at least 256kbps both up and down.
    Check the System Profiler is "seeing" the camera.
    It will be in Hardware > USB
    10:30 PM      Tuesday; March 27, 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

  • Problem with iChat changing my custom away message after 30 minutes

    Lately, I've been having a big problem with iChat changing any custom away message that I put up to "Away" after 30 minutes or so. Is there anything I can do to make it stop? Another issue I'm having is that sometimes when people on my buddy list change their away message, it doesn't show up on iChat unless I go offline and then sign back on. Any idea why it's doing that, and what I can do to get it to stop?
    Thanks.
    - Danielle
    G3 iMac   Mac OS X (10.3.9)  

    Hi ienjoyanime,
    Go to the General Section of iChat Preferences.
    Does it say you are set to Go to Away when you log off/QUit iChat ?
    is the computer going to Sleep at this point ?
    10:59 PM Saturday; April 1, 2006

  • I installed lv 6.1 on a windows 98 system. As I am having problems of stability (much more than with the former release 6.0), I would like to know if there is some specific problem with windows 98 or there is some patch.

    I installed lv 6.1 on a windows 98 system. As I am having problems of stability (frequent crashes, much more than with the former release 6.0), I would like to know if there is some specific problem with windows 98 or there is some patch available.

    My experience with Win98 is that it is not a very stable system, regardless of software used. For example, Win2000 and XP are far more stable than 98. I've had it crash on its own if I leave the computer on for several days.
    I wouldn't recommend running programs for long time (few days) on this OS.
    This being said, can you be more specific in your question. What kind of stability problems did you have, which VIs did you run (if possible post them here), did you change the interrupts and priority levels on those VI, do you get error messages or blue screen....
    Zvezdana S.

  • Problem with Snow Leopard 10.6.8

    I recently faced problem with Snow Leopard 10.6.8, and my system started getting shut down before login screen appears. I contacted apple support,and they replaced my Logic board.
    Now i am facing problem with track pad, and there is a huge degradation in system performance.
    Neither, bluetooth and internet port is working.
    Is that a known problem with 10.6.8 ? or does the people who worked upon replacing the logic board messed up something ?
    they recommended me to re-install Mac OS which came along with system.
    --Manish

    Thanks for a super Quick response.
    I have tried re-installing the MAC on top of the current installation 10.6.8 and, ( as system is so slow, it took around 5 hours for installation to complete ), yet the problem persisted.
    Currently i formatted the Macintosh HD, and i am doing a fresh installation. Hope it does work .. ??
    Else, i am not sure, what to go ahead with..
    The person who replaced LB, had an external hard drive with 10.6.7 installed on it, when system was booted from that disc , the things starts working normally.
    if after the fresh installation, problem persist, i will update.
    Also, please let me know if you have some solution for this problem.
    --Manish

  • Specific problem with trackpad

    I have this specific problem with my trackpad, it doesnt work this 2 functions:  Swipe between pages and scroll direction: natural.
    all other functions are working.
    i don't know what to do .

    Hello, Gonzalo andres. 
    Thank you for visiting Apple Support Communities. 
    I had an issue with this after upgrading to OS X 10.9.  I would verify that the gestures have been configured in System Preferences > Trackpad > Scroll & Zoom/More Gestures. 
    OS X Mavericks: Change keyboard, mouse, and trackpad settings
    http://support.apple.com/kb/PH14317
    OS X Mavericks: Change the way your trackpad works
    http://support.apple.com/kb/PH13804
    Cheers,
    Jason H. 

  • Epson R2880 printer driver problems with Snow Leopard

    I’m running 10.6.4 on a new Mac mini and I’m trying to print to a new Epson R2880. If I let the system choose the printer driver in the print and fax utility, I get a sort of generic print dialogue box without many options, but it prints. If I go into the print and fax utility and manually choose the driver, I get a different print dialog box with all the appropriate print options. I checked and it matches the screen shots for this printer that are posted on the Epson site, so I feel sure this the correct driver. However, when I try to print with this driver, I get this error message. Error:/Library/Printers/EPSON/InkjetPrinter2/Filter/rastertoescpll.app/Contents /MacOS/rastertoescpll failed.
    This seems to be a common problem with Snow Leopard and the R2880 Epson printers, and it seems that most people are able to solve it by deleting the printer from the printer queue and resetting the printer queue. But that hasn’t solved my problem.
    Here’s what I’ve done:
    Manually deleted the Epson folder from the hard drive and trashed it, repaired disk permissions, uninstalled the Epson driver, updated software, downloaded and installed the Apple/Epson driver, deleted the printer from the print queue, and reset the printer queue. I’ve done all of these things several times over. And still I get the same error message every time I try to print from the driver with the print options. Does anyone have any other suggestions for a fix?

    Some of the previous users had success when they restarted after deleting the /Library/Printers/EPSON and /Library/Caches/Epson folders. You might also try deleting the /Library/Cache folder. There is a solution posted from someone at Epson:
    http://discussions.apple.com/thread.jspa?messageID=10909012#10909012
    Substitute 2880 for RX580:
    Make sure that you have completely removed the Stylus Photo RX580 driver, then install the new driver from System Update:
    1. Power off the printer
    2. Open System Pref. and Print/Fax
    3. Highlight the RX580 printer
    4. Click on the ""-"" sign
    5. Close Print and Fax
    6. Open your Mac's Hard Drive
    7. Open the Library Folder
    8. Open Printer and delete the EPSON Folder
    9. Open the PPDs folder find the Epson Stylus Photo RX580.gz and delete the file
    10. Close the PPD and the Printer folder
    ->11. In the Library folder, open the Caches Folder
    ->12. Delete the Epson folder
    ->13. Restart the Mac
    14. Power on the printer
    15. Click on the Apple Icon and System Update
    16. Follow the directions to install the new driver
    Hope this helps.

  • New problem with iChat

    Good morn
    I still haven resoved my previous post about connection problems with iChat, but hope to do that when I visit my dad next month. Thanks for all the advice anyway.
    A new problem has emerged, and seemed to coincide with the install of Tiger 10.3 last week. Now when I try to connect to various tests sites, I get an "insufficient bandwidth" error.
    Is this likely to be a problem with Tiger, as I have not changed my isp, settings or broadband type?
    Or could it just be the exess load on the system over the Christmas period with all those naughty teenage boys downloading **** and playing games during the school hols?
    Any suggestions and/or fixes greatfully accepted.
    Thanks
    Tim R

    Hi,
    Glad to hear you are up and running.
    New Discussions ReponsesThe new system for discussions asks that after you mark your question as Solved. You should take the time to mark any posts that have aided you with the tag and the post that provided your answer with the tag. This not only gives points to the posters, but points anyone searching for answers to similar problems to the proper posts.
    Alternatively, you can change the status to Answered.
    If we use the forums properly they will work well...
    Ralph

  • Specific problems with SB Live! 24-bit (SB04

    <SPAN>Hello all,
    <SPAN>I just recently purchased a Sound Blaster Li've! 24-bit card for my PC. The installation process went without a hitch - I disabled the onboard sound and uninstalled its drivers, then proceeded to install the new card and its drivers off of the included CD. Generally, the card seems to be working fine, but there are a few nagging problems with certain games.
    <B><SPAN>Far Cry</B><SPAN> - Referencing two related posts I've seen on other forums (but not my own), the problem is as follows:
    <SPAN>)<I> In farcry i get a ways into the game and the </I><I><SPAN>sound</I><I><SPAN> starts to have a high pitch squeel and then static and then no </I><I><SPAN>sound</I><I><SPAN>? I have a </I><I><SPAN>sound</I><I></I><I><SPAN>blaster</I><I><SPAN> li've 7. 24-bit </I><I><SPAN>sound</I><I><SPAN> card and no idea what is causing this. (I have it patched to .3)</I>
    <SPAN>2)<EM> so i get in the water and when i'm almost at shore, there's this HORRIBLE screeching sound and it gets louder. it's really insane. it lasts for a few seconds and then the sound goes out (no more sound in the game) and the game freezes after that - </EM>an<EM> </EM>addition<EM>, </EM>this<EM> </EM>user<EM> </EM>was<EM> </EM>using<EM> a </EM>Sound Blaster<EM> </EM>Audigy<EM> </EM>LS<EM>, </EM>which<EM>, </EM>if<EM> </EM>I'm<EM> </EM>not<EM> </EM>mistaken<EM>, </EM>is<EM> </EM>what<EM> </EM>the<EM> </EM>SB<EM> </EM>Li've<EM>! </EM>24<EM>-</EM>bit<EM> </EM>is<EM> </EM>based<EM> </EM>on<EM>.</EM>
    <SPAN>I have the exact same problem.<SPAN> Upon entering and exiting the water (only with EAX enabled, though) the sound screeches horribly for a few seconds, and then stops entirely.<SPAN> I?m not sure what?s causing it, but it only seems to occur while swimming, then coming up for air, and only with EAX enabled.
    <B><SPAN>UT2004</B><SPAN> ? Unreal Tournament 2004 also has errors when using hardware-accelerated and/or EAX enhanced sound.<SPAN> It?s most noticeable when firing a weapon rapidly.<SPAN> It?s a bit hard to describe, really.<SPAN> Instead of the sound being a continuous chain of assault rifle bursts, the sound created by firing the first bullet is canceled out by the successi've one. That is, only the last shot in the clip has its sound played completely, with a few exceptions - every once in a while, the full sound is played for a shot, but it seems to be at random.<SPAN> The full sound is simply not being played. With regular 3D sound (non hardware-accelerated or EAX) enabled, the sound is played correctly.<SPAN> I hope that?s a decent enough description.
    <SPAN>I?d like to use the EAX on this card to its full capabilities, but I?m currently unable to do so with these errors.<SPAN> I?ve ran through the basic troubleshooting one does with a new sound card, but these seem to be very specific problems with these two games.<SPAN> Or, I may have missed something.<SPAN> Any help would be greatly appreciated.<SPAN> Thanks in advance.
    <I><SPAN></I>
    <SPAN>
    Message Edited by Mortal_Quietus on 2-29-2004 06:36 AM

    Well here it is, I have a audigy LS sound card and for a bit now I have been taking my cpu apart to find out what is causing my memory dumps and restarts in a game called city of heros. I went through alot of testing to find out that its not my graphics card hard dri've or memory stix causing the problem, what I did find was that when i get the blue screen of death it shows the cause being p7.sys driver which is a driver to the sound card. And when I turn off hardware sound acceleration in my direct x my restarts stop and no more memory dumps, when I turn the acceleration off it switches off the p7 to one that seems to work better. But the problem is now im in emulated mode and sound isnt all great. I bought the sound card to get better quality than the last card I had but it seems im having more trouble with the card than its worth. I'd appreciate any help with this problem as soon as possible, I have reinstalled drivers several times and tried changing pci ports checking for conflicts but all is good except It does that memory dump in the game. Im considering returning it if i can't resolve this soon thx for any help that may come.

  • Tons of problems with Snow Leopard

    Made this post over at my blog but I figure this would be a better forum for it in hopes we can get some of these issues resolved... it seems like Apple has pulled a Microsoft and released what appears to be a beta version of Snow Leopard! Inexcusable bugs are appearing left and right, and the supposed "improvements" have actually hindered my computer performance and productivity...
    This really surprised me. After years of releasing amazing OS upgrades that seemed to make the best OS even better, it seems like Apple has taken 2 steps back with Snow Leopard. I can't tell you how upset I was to realize I was experiencing many problems that I previously only saw on PCs.
    After one of the many bugs popped up again on my computer, I got frustrated and started combing the internets for a list of known bugs in the OS and the inevitable slew of Apple users registering their disgust. Unfortunately, my search didn't turn up anything but positive reviews of the OS and very limited complaints on a few message boards. To this end, I'm posting this entry to try and help other users who are experiencing similar issues and hopefully get Apple to clean up this mess of an OS.
    Below I've created (and will be adding to) a list of problems I've experienced in OS X 10.6, Snow Leopard. I encourage everyone to list your Snow Leopard issues in the comments as well, in hopes we can create a master list of problems.
    I am using a 2 GHz Black MacBook (Core 2 Duo) with 2GB of RAM. Keep in mind Leopard (OS 10.5) was running flawlessly on this more than capable machine. I am currently running the latest Snow Leopard build, 10.6.1. I upgraded 10.5 with the retail version of Snow Leopard, integrating my current apps into 10.6 (did not do a clean install). I've organized my issues below by application. This post is less about third-party applications and more about Apple apps/built-in OS features, as Apple is fully accountable for these pieces.
    APPLE APPS
    Airport:
    • Airport is now incredibly slow getting past the "searching" status message and into what was known as "scanning" status in 10.5 (now called "Looking For Networks…" status message). This issue occurs most often when I revive the computer from sleep. I have to turn Airport off and on again, then wait an inordinate amount of time to get past the useless "Searching…" message.
    Volume and Sound:
    • I rely on my volume control icon on the toolbar. I change my system volume dozens of times every day (due to my job)... previously, I could click the volume icon then simply roll the scroll wheel on my two-button mouse to adjust the volume. Now, I have to actually move my mouse down onto the volume slider area before my scroll wheel works! What gives? In allowing the user to fine-tune the volume levels, Apple removed this functionality for some reason? This is a real pain for me as the extra second it takes to do this really adds up by the end of the day.
    • Sound now starts stuttering for no reason? When I wake my computer up from sleep and I have headphones or speaker plugged in, the audio stutters greatly. I have to unplug then re-plug my speakers or headphones to fix the issue! This is a problem I saw on many PCs due to sound cards not playing with Windows nicely, but was NEVER an issue I experienced using OS X.
    • The Mac OS startup chime plays on my MacBook external speaker when I startup, even though I have speakers or headphones plugged in! It also does not matter if I had my system volume on mute when restarting • the OS seems to now decide what volume my system should be at when I start up!
    Safari:
    • Defaults to 64-bit mode silently, and this breaks most plug-ins (my issue was with download manager iGetter, specifically). I had to manually Get Info on the app, then switch back to 32-bit mode, which it seems Apple has not designed Snow Leopard to support properly?
    • Freezes and crashes more often, most often when running Flash video. This occurs when I open multiple videos on YouTube, for example.
    • Hogging memory even more than it used to (1GB of RAM to run the app?? Really?)
    Stacks:
    • Apple seems to have completely removed the functionality or sortable sub-folder listings? For example, if I choose to sort my stack by "Date Modified", the initial list of folders in the stack appear by date, but all my sub-folders appear in Alpha order, and there is no way to change this! Come on Apple, why remove this?
    iPhoto:
    • Freezes completely when I go to "Export…". My Export opens on the Facebook tab of the dialogue box, and it seems the issue occurs when iPhoto can't find the source image. Rather than an error message though, I get the color wheel of death.
    Spotlight/Search:
    • When I search from a Finder window, sometimes I get the new feature of sortable results columns to work, but sometimes I don't. Seems arbitrary when it works and when it doesn't.
    System Preferences:
    • More of an annoyance, System Preferences now has to restart the first time I click on any third-party preference in "Other". Some work, most don't.
    Install:
    • In previous OS X upgrades, Apple gave me the option to "Backup and Install". This option was not present on Snow Leopard, so not sure what a user can d if they do not have a Time Machine backup and their install fails.
    Preview:
    • Preview slows down considerably when opening multiple files.
    THIRD-PARTY APPS
    Entourage:
    • Entourage froze up when I tried to simply delete one of my email accounts. The Accounts window went blank and the application froze.
    CS3:
    • Slower than ever, Photoshop is running at a snail's pace.
    I hope everyone can contribute to this string and get Apple to fix these problems.

    I can address some of these:
    Safari defaults to 64-bit mode silently, and this breaks most plug-ins (my issue was with download manager iGetter, specifically). I had to manually Get Info on the app, then switch back to 32-bit mode, which it seems Apple has not designed Snow Leopard to support properly?
    All applications, to the best of my knowledge, will run in 64-bit if they include 64-bit code. With most you'll never notice, but if an application supports plugins, then you have to pay attention to whether the plug-in is available in a 64-bit version. More and more are becoming available, but not all. If you have plug-ins that aren't, you need to set the app - Safari or whatever - to 32-bit mode. This is not a bug; it's necessitated by the conversion to full-time 64-bit support. The developer of iGetter claims that an update for compatibility with Safari in 64-bit mode is under development but no time frame has been given.
    Snow Leopard is perfectly capable of running 32-bit apps. You just can't mix them, running a 32-bit plugin in a 64-bit app.
    Freezes and crashes more often, most often when running Flash video. This occurs when I open multiple videos on YouTube, for example.
    Have you installed the latest version of Flash? Flash is almost always a bit problematical, but I've had no problems running Flash content on any site with SL.
    Hogging memory even more than it used to (1GB of RAM to run the app?? Really?)
    This may just be an issue of not being clear on how Mac OS X allocates memory. This article may provide some insight:
    http://support.apple.com/kb/HT1342
    More of an annoyance, System Preferences now has to restart the first time I click on any third-party preference in "Other". Some work, most don't.
    This is normal if a preference pane has not been provided in a 64-bit version.
    In previous OS X upgrades, Apple gave me the option to "Backup and Install". This option was not present on Snow Leopard
    Actually it was called "archive and install" and was removed as an option as no longer necessary. The normal installation creates all necessary new files and more robustly replaces old ones, so having an archive of the old system folder was deemed to no longer be needed.
    so not sure what a user can d if they do not have a Time Machine backup and their install fails.
    To restore completely from a full Time Machine backup, you erase the disk using Disk Utility from the menu in the Installer, then choose to restore from a TM backup.
    Preview slows down considerably when opening multiple files.
    Seems to work OK for me. I've had as many as twenty open with no noticeable slowdown. But you may be opening much larger documents than I have.
    Entourage froze up when I tried to simply delete one of my email accounts. The Accounts window went blank and the application froze.
    Impossible to offer any advice here without knowing what version of Entourage you're using, whether it's been fully updated, and what type of email account this was.
    Regards.

  • Package permissions problem with Snow Leopard

    Under Leopard, changing permissions at the Get Info window for a package file also changes the package contents to the same permission settings. This no longer works in Snow Leopard. For example, I have tried adding another user name with read & write privileges. The package file displays the correct setting, but all the contents of the package have the newly added user as read only. This is causing me problems with a virtual machine I want to share with other users of my computer. I also tested it with iWork (Pages) packages - in Leopard the package contents keep the r&w setting for the new user, but not in Snow Leopard. Note that for package files, there is no option to apply to contents, as is the case for folders, but it should do it automatically.
    I would be grateful if someone could verify this bug. Also, I intend to use chmod -R at the terminal, but I am not sure how to use it to add a specific user with r&w privileges, so any help appreciated.
    Many thanks
    George

    I don't believe it's ever worked you the way you describe in leopard. I just tried it on my leopard machine with an application package and changing permissions to the package itself did nothing to its contents.
    you can change permissions recursively from terminal but it's easier from GUI.
    make a folder and put the package in that folder. *DO NOT* use system created folders for this. go to the permissions panel for the folder and set permissions as you like. then click on the "gears" action button at the bottom of the "get info" popup and select "apply to enclosed items". This will change permissions recursively on everything in that folder.
    NOTE: as I said, never do it with system created folders as they often have hidden ACLs and doing so will propagate those ACLs inside.
    to give a particular user read+write right to the whole package from terminal run the following terminal command
    chmod -R +a "username allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,
    readextattr,writeextattr,readsecurity" /path/to/package

  • Problem with iChat AIM - Multiple login, log out

    I am having a recurring problem with my iChat. Every time I try to log into AIM when I'm home, it rapidly logs in and logs out, and then tells me that I have loged in too many times and need to wait a few minutes to try again. I have tried the delete .plist file solution, but this did not work. This is a very very annoying problem, because I love using iChat when it actually works.
    I have also tried using other IM applications, and they all work flawlessly... whats up iChat? Any Ideas?
    R.V.

    Hi,
    The problem is not limited to Netgears.
    In fact I never had the issue with the Netgear I had.
    It is an extremely well documented issue with Zyxel devices since iChat 2
    134 response to Searching for Zyxel across iChat 2 and 3 forums.
    It sort of goes like this.
    At one time routing modems or routers could only do Port Forwarding
    This involved pointing one port at One IP (Computer)
    You could not forward a Port to two computers (IPs)
    Since then manufacturers have added in stating Protocols as well as Ports to open.
    So as UDP and TCP protocols tend to be the ones on ports above 1024 you have some apps that have both Protocols in use and in some cases on the same port.
    It does seem that this business of not being able to Forward a Port twice also effects those were you ow have to state Protocols as well.
    iChat uses two ports twice.
    Port 5190 is used to do the AIM Log in and basic Text chats on TCP
    It used UDP to Send Files, Pics-in-Chats (Direct IMs) and certain Buddy List feedback and Group chats (Chatrooms).
    Less effected is the Bonjour Port 5298
    The regular posters have long since held the view that the AIM servers sometimes can not handle all the login and text traffic on just port 5190 (ICQ is also owned by AOL and on this same port).
    We Suggest port 443 for several reasons.
    However it is mainly as this is below the threshold of 1024
    There are in fact 65535 ports that could be in use.
    Most domestic devices have the port up to 1024 open to all computers connected.
    This means Web Browsing (Port 80) and Mail (ports 110, 443, 567, 955 and others) are below this threshold and will work "out-of-the-box"
    As any firewall included in the device or on a Mac with Tiger or Earlier the port 443 is likely to be opened for a Mail App (It is also used in Web Browsing to Secure sites like Banks and the Apple Discussions Log in page) so that several apps can use the port.
    It is worth noting that the Leopard Firewall works differently in allowing the ports associated with an App on an Certificated (by app) basis so there is no Piggy-backing.
    On the SPI (Or if you have DOS) Front.
    These features tend to be Threshold based.
    DOS comes from the time when so called Hackers got together to all try the same web site/page and repeatedly refresh the page so that the server got lots of incoming requests.
    This overloaded the server and brought down the whole web server and the computer it was on lost connection to the internet as a whole.
    DOS protection looks to see if this "Too Much Data, Too Quickly" scenario is happening and will cut that one port (In the case of iChat 4) that it is happening on.
    (iChat Can send LOTS of data)
    SPI tends to try and filter things in a different manner by checking if the data looks valid.
    IT seems in some cases it can not keep up with the amount of data iChat can stream and consequently cuts the connection the same as DOS does.
    Both are dependent on how fast your Buddies Processor is, how fast their Internet Connection.
    (Some Buddies can send only 15fps of a 640 X 480 pixel pic other can manage 30fps or twice as much data)
    This is somewhat augmented (or not) by how fast you can accept data both over your Download speeds and your processor dealing with it.
    Therefore it can seem to be an intermittent problem depending on the circumstances of the connection of that chat.
    My Netgear had DOS and It had it Off (Along with the Ping Blocking)
    My Current Sagem Fast 2504 has only the Block to Internet Pings settings which is Off
    So on the whole Experience and Practice.
    9:44 PM Friday; March 27, 2009

  • External display problems with snow leopard

    I just upgraded from Leopard to Snow Leopard on my Macbook and it's created lots of problems with my LCD external display:
    - The display won't work at its native resolution (1680x1050) - it will flash up an image for 1/10 of second and then go black. I can only get it to work at a lower resolution, which looks AWFUL.
    - If I try to start up my Macbook with the lid closed and the display connected, the display won't work at all (it jams on the start up screen). It only works if I keep both of them running
    I never had these problems when using Leopard. I've searched lots of forums and found that many people are having similar problems with external displays. Apple still haven't fixed the bug after repeated efforts from people to get if fixed.
    Here are some threads (now closed) on this if you're looking for solutions:
    http://discussions.apple.com/thread.jspa?threadID=2132912&tstart=0
    http://discussions.apple.com/thread.jspa?threadID=2136455&tstart=1
    http://discussions.apple.com/thread.jspa?threadID=2132837&tstart=0
    http://discussions.apple.com/thread.jspa?messageID=10084332
    Common suggested fixes are:
    - Force OS X to use LCD font smoothing (does not work for me)
    - Clear the PRAM on start-up (does not work for me)
    - Delete /Library/Preferences/com.apple.windowserver.plist (does not work)
    - Change energy management setting to high performance (only works on graphics cards in Macbook 15" and 17").
    From reading these forums it appears that this is a well-know bug. Has anyone else got any suggestions to fix this? And why hasn't Apple fixed this yet after so many people bringing it to their attention? It's clearly a bug that wasn't in Leopard.

    I'M FED UP WITH APPLE! They've always been a little shady, but the last half of 2010 took the cake!
    First it was the iPhone 3g "upgrade" to IOS4 which was garbage and killed my ability to use the 3g until I figured out how to crack the software, wipe the thing clear then reinstall the original software. Next up was purchasing the iphone 4 as a Christmas gift for someone running tiger on their mac, only to find out that the iphone 4 doesn't work on tiger when they tried to sync their contacts - and then having to rush out and purchase snow leopard so that they could enjoy my gift. Then I install Snow Leopard (note - I purchased the family pack) onto my own leopard-running(10.5.+) powerbook only to have the external LCD display I've been using for years suddenly stop working.
    Oh, okay, to be fair, it works IF I RESIGN MYSELF TO SET it to "mirror image" (which defeats the purpose of having multiple displays) and drop the resolution down to a pathetic, unsharp, nearly distored setting that is almost painful to look at knowing that this monitor was just A COUPLE OF DAYS AGO showing me crystal clear images.
    Then I exhaust myself trying to find a fix only to discover that APPLE in their infinite brilliance (AKA - their torture of loyal customers) knows of the issue - worked it out - then created an update that created the issue all over again. I'm so done! No more macs. I'm going back to the evil land of PCs. At least there, you know you're getting crap, it doesn't sneak up on you after getting you to trust it time and time again.

  • Specific Problem with Library Module 1:1 Preview Loading

    Hi everyone.  I've spent hours searching Google & forums for specific tips to try but I've found nothing that solved my problem.  I have a very specific problem loading 1:1 previews in Lightroom 3.3 while zoomed to 1:1.
    When I initially import a shoot (usually 3000 to 6000 images), I always render 1:1 previews during import.  My understanding is that this activity writes full-sized previews to the "Previews" folder, but I also have observed that .DAT files are created in the "Camera Raw Cache" folder.  I have my Lightroom Previews folder and my Adobe Camera Raw Cache folder on the **same** solid-state hard disk, which is dedicated to Lightroom.
    When I browse these newly-imported images in the Library module in Loupe view at 1:1 zoom, it's very zippy and fast to switch between images.  The images load without any message at a lower resolution, and then "snap" to full resolution after 0.25 to 0.5 seconds. No "Loading" message appears.
    However, once the previews have "sat around for a while", even if they are still supposedly available in the Previews folder, loading the image at 1:1 in Loupe as described takes 3-5 seconds.  Shortly after going to an image, the message "Loading..." is displayed (it doesn't say where from), and 3-5 seconds later, the full res image appears.
    This has nothing to do with changes to image settings requiring re-rendering of the preview.  These are images that I've imported but haven't browsed in a while.  I know that the previews are valid, because I can go to "Library > Previews > Render 1:1 Previews", and the task will complete within 20 or 30 seconds without re-rendering any photos after examining them and apparently finding that there are still valid 1:1 previews for all 4000 of them.  After doing this "re-render," the slow loading behavior is the same as before, because the re-render process always completes without actually updating the previews that it found are already there and presumably decided were still valid.  Discarding previews by "Library > Previews > Discard 1:1 Previews" and then trying to re-render them also does nothing, because LR3 apparently doesn't immediately delete the discarded previews, so they are picked back up again As-Is by the re-rendering process.
    If I had to guess at the reason for this behavior based on the symptoms, I would say that it seems like Lightroom is forcing itself to re-render 1:1 previews upon browsing to images that are older than a certain age (very possibly the same "30 days" after which the 1:1 previews are supposed to be discarded).
    Now, I've also observed that deleting the DAT files in the Camera Raw Cache folder has no adverse impact on load speed (which is what I would have expected to see if LR3 was looking for and loading images from this cache instead of the Previews folder).
    What this means to me is that once the image previews reach this "outdated" state, I can't get fast 1:1 browsing performance in Loupe with any reliable procedure other than manually deleting [in Windows Explorer] the entire Preview folder and then re-rendering the 1:1 previews for this shoot.  This is of course terribly inconvenient when there are recent previews that I want to save.
    Note:  I do not have any slowness under any circumstance when browsing at "Zoom to Fit".  This is only a problem when I'm browsing at 1:1 zoom (like when I'm comparing sharpness between a set of photos).
    Note:  For images with the slow behavior described, once the image has been loaded once at 1:1 zoom, it's henceforth snappy again when returning to the image (as if Lightroom was once again accepting the Preview file as valid).
    So, here's a summary:
    Previews (X:\Lightroom Catalog Previews\) and Camera Raw Cache (X:\Lightroom Cache\) are on same, dedicated, fast drive
    1:1 previews from recently-imported files load full-res at 1:1 zoom in less than 1/2 second.
    Older 1:1 previews take 3-5 seconds to load full-res at 1:1 zoom, even though the previews are supposedly being loaded from still-valid 1:1 previews in the Previews folder.
    I'm really tired, so i hope this makes sense.  I don't see how this could be a hardware problem, because I get good performance with recently-imported images.  I'm running LR3.3 on Win 7 Pro x64 with 8 GB of RAM and a 2.4 GHz Intel Core2 Quad CPU.  Never had LR3 beta installed - upgraded to 3.0 from the last 2.X version.  After upgrading, in response to this exact issue, I deleted my entire previews folder and rebuilt, but I continue to have the exact same problem on every shoot that I import.  It's most noticeable on the large shoots, because I end up having to browse at 1:1 zoom to compare a set of similar images.
    Only workaround I've found:  in Windows Explorer, manually delete the Previews folder.  Return to Lightroom and rebuild 1:1 previews.  This forces the previews to be rebuilt for all images.
    Another possible workaround I am going to experiment with: setting the Previews to "Do Not Discard", in case the defualt "Discard after 30 days" that I've used is causing or contributing to the problem.  If Lightroom is actually discarding the images after 30 days but forgetting that it had discarded them when asked to re-render 1:1's, maybe setting to "Do not discard" will bandage that problem by never discarding them to begin with.
    All right, I'm falling asleep at the keyboard.  I'm afraid to add more details as they may become incoherent.  Hope to hear some good news, as fixing this problem would make my LR3 experience so much more pleasant.
    Can anyone assist with this problem?
    - Tyson

    function(){return A.apply(null,[this].concat($A(arguments)))}
    Ian Lyons wrote:
    The behaviour after previews have been around for a while (i.e. previews for unedited images) is not normal. There have been a few other reports of similar behaviour, but no real clues as to why it happens.
    Yes - this is my problem.  Previews should still be valid, and "Library > Previews > Render 1:1 Previews" says the images are still valid, but then Loupe rebuilds them anyways.
    function(){return A.apply(null,[this].concat($A(arguments)))}
    Ian Lyons wrote:
    If everything was working correctly, the setting for discard shouldn't have any effect on whether the previews go stale or not. ...
    My understanding is that if everything were working as intended, the "setting for discard" that I was referring to (Edit > Catalog Settings > File Handling > "Automatically Discard 1:1 Previews") should be the sole determinant of whether 1:1 previews must be rebuilt for images with unmodified settings.
    For example, if I import an image and render a 1:1 preview, and if I set the "Auto Discard 1:1" setting to "30 Days", and if I make no changes to the image's settings, then I would expect that the image should render quickly (under 1/2 second) at 1:1 zoom in Loupe view for the next 30 days.  On the 31st day, I would expect the image to take longer to load as a new 1:1 preview was rendered and stored, and then I would expect this new preview to be retained for another 30 days.
    I would furthermore expect that the 30-day counter would be reset every time the image was re-rendered (i.e. if I go into Develop and change something).
    To a certain extent, this is functioning correctly on my system.  When I go to one of these "problem images" that inexplicably load slowly, returning to them subsequently is quick.  I think my problem is just, as Rob suggested, that some part of Lightroom's "brain" has wacky ideas about whether an up-to-date 1:1 preview exists or not.
    If I choose to "Never" automatically discard 1:1 previews (which is what I just switched to), then I should "Never" see unmodified images taking 3-5 seconds to "Load" at 1:1 zoom in Loupe.
    Since I just nuked my Previews folder again last night and re-rendered 1:1's overnight for a 3000 image shoot, it might be a while before I start encountering this bug again.  I will certainly post any further related experiences here and will keep checking for anyone who has further insight.
    function(){return A.apply(null,[this].concat($A(arguments)))}
    Ian Lyons wrote:
    ...we know that Lr3.4 RC fixed the manual discard bug, so, if I were you I would focus any further tests on Lr3.4RC.
    Thanks for pointing this out.  I will upgrade to 3.4RC - at least then I will be able to force a rebuild of previews from one shoot without having to manually delete the previews for my entire catalog.  I'll no longer have to throw out all the food in the refrigerator just because something smells funny.
    function(){return A.apply(null,[this].concat($A(arguments)))}
    Ian Lyons wrote:
    The DAT files are created at the same time as Library previews. However, they are only used in Develop module.
    Yes, I definitely agree with this (although, the Cache is probably also used while rendering new previews after "Quick Develop" changes in the Library module....).  I posted my observations to this effect just in case someone else wondered the same thing I did.  It is clear that the DAT files get written every time a preview is rendered for RAW file.  Rob, now that I'm thinking with a clearer mind, I think the only thing these Cached files are used for is if you "return" to recently rendered settings in Develop or Quick Develop - then, that particular combination of settings yields a match in the cache, and LR loads the image from the Cache into Previews and onto the screen.  It is logical that the cache wouldn't help us when going to new settings, because the new settings would create a partially or completely different rendering than any other combination of settings.  Adobe may be going to more advanced levels of "reusability" than this, but I'm sure this is the general state of things.
    You may want to open back up write access to that Cache folder...
    Thanks, Rob & Ian!
    So, my question, or bug report, still remains for now - why am I biting into a bag of chips marked "Fresh" and finding them Stale?  And why does it say "Paper Jam" when there is no paper jam?

Maybe you are looking for

  • File - AS2 Scenario

    Hello all, we have a procject with a customer, but if we try to send an document, we get follow error back: Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failu

  • HR Structural Authorization DSO's

    Hi, I have developed HR module for the first time. I need to create the authorization objects for the HR reports. I found 0PA_DS02 and 0PA_DS03 for structural authorizations in HR. I dont understand the purpose of these DSO's. Can some one explain wh

  • CS4 and IPS monitor???

    I came to realize that my old basic LCD monitor was making my results in CS4 really bad.  Last night I received my Dell 2410U IPS LCD monitor and I am floored!  What a difference.  I set it up DVI and went to Adobe RGB, and now I need to wear sun gla

  • Default Print Options when issuing output

    Dear Experts: I came across a issue regarding print options when issuing output from the billing document. my first question is, this default print options seems to be coming from my output record as for print immediately option. where does Recipient

  • Upgrade from Windows version to a Mac Version?

    All, I started on Director over 10 years ago but it all died off. Seems it has rekindled a bit with version 12? My license (still have the box, CD's and license keys) are for Windows. If/When I upgrade, can I specify a MAC license so I can develop fo