WEIRD FIREWIRE/DV MYSTERY

hi there, I have a used g5 at my house that has been inconsistently reading the DV stream, by this I mean that FCP reads vtr ok and has audio but no video. I try both basic and standard for the device control, but not dice. Sometimes when I swithc it will freeze the first frame of video and hold it. Same for QT, which leads me to belive that its a firewire problem. So I take my camera and tapes to the local college's mac lab and hook it into their g5 there, SAME FREAKING PROBLEM, which would make one deduce that its either the camera or tape. So i give it one last chance and hook my camera into the college's g4 imacs and wa-la everythings kosher. So what gives? My theory is that its some weird interface problem with the g5 and my model of palmcorder (jvc), but it seems firewire should be standard. any tips would be appreciated as I am pulling my hair out on this on, thanks

JVC's camera will probably use FireWire Basic as a device control. But installing QT 7 might also be part of the problem. Here's the fix for the QT problem: http://docs.info.apple.com/article.html?artnum=301852
Also you should be running 10.4.7 and the latest version of QT with FCP 5.0.4 or 5.1.1. as a combo of software.
Jerry

Similar Messages

Weird Firewire backup problem

Hi all,
I'm currently suffering from a really weird firewire problem that's affecting my backups and given the fun I've been having with the recent updates I'm not inclined to do anymore updates until I get this problem sorted.
My firewire drive is split into three partitions, two are used for backing up my PowerBook and the third partition holds iTunes and some other stuff.
I boot into safe mode and use Disk Utility to restore my disk onto one of two backup partitions. Today I did a backup onto one of my partitions (Three) and rebooted (setting that partition as the boot disk) but for some reason my machine booted from the other partition on the firewire disk (Four.)
I've tried this several times now and even attempted a second backup but it appears that Three is simply not seen, or if it is then somehow it is being linked to partition Four.
The reason I think it's being ignored or there is some sort of weird link there is because if it was trying to boot from Three but failing then I should see either a flashing apple sign or I should receive a kernel panic but this isn't happening. Four is definately booting when it should be Three.
I don't suppose anybody has any ideas about why this is happening?
Thanks
Richard

Ignore permissions was unchecked, I've got into the habit of doing that as soon as the restore is complete. In the end I booted from the volume that I was leaving alone, I then restored the PowerBook to the other volume and it worked fine. I don't recall having to used to have to do it this way before so maybe something has been tweaked somewhere with 10.4.3.
I just need to remember this for next time.
Thanks.
Richard

Weird firewire error: no valid selfIDs

We are having an issue with firewire on two different macs. One is mac pro running 10.5.5 and the other g5 running 10.4.11 ( i am not on my home machine). We were shooting tethered to a hasselblad h3d via firewire 800 this morning when we first encountered the problem, although subsequently all firewire devices (externals, various manufacturers Lacie, iomega) drives were affected. The camera, and the the hardrives were not recognised. We have followed all steps appart from step 9 in this document http://www.thexlab.com/faqs/firewiretroubleshooting.html . We have also ran permissions repairs and subsequently applejack http://applejack.sourceforge.net/ Reseting the PRAM resulted in sucessful remounting of the external hardrives but when we started the camera it was not recognised. I subsequently noted the external hardrives that had remounted after the pram reset were no longer mounted although i am not sure when this happened.
This message shows up repeatedly in the system events log, even when no firewire devices are physically connected.:
Jan 19 15:55:02 Mac-Pro kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
A similar message repeatedly shows up in 10.4.11. I would have said that the fact it was not working on two different machines would isolate it to the camera (changed firewire cables too) but these messages on both systems is just weird =. Help very appreciated!!!

here are a few bits of the log from the g5
Jan 19 12:46:30 Studio-G5 configd[35]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Jan 19 12:46:30 Studio-G5 configd[35]: posting notification com.apple.system.config.network_change
Jan 19 12:46:30 Studio-G5 lookupd[85]: lookupd (version 369.8) starting - Mon Jan 19 12:46:30 2009
Jan 19 12:46:32 Studio-G5 configd[35]: target=enable-network: disabled
Jan 19 12:47:40 Studio-G5 kernel[0]: Bad SelfID packet 3: 0x0 != 0xffffffff!
Jan 19 12:47:49 Studio-G5 kernel[0]: Bad SelfID packet 3: 0x0 != 0xffffffff!
Jan 19 12:47:51 Studio-G5 kernel[0]: Bad SelfID packet 3: 0x0 != 0xffffffff!
Jan 19 12:48:02 Studio-G5 kernel[0]: Bad SelfID packet 3: 0x0 != 0xffffffff!
Jan 19 12:49:22 Studio-G5 kernel[0]: FireWire (OHCI) Apple ID 52 built-in: 274 bus resets in last minute.
Jan 19 12:50:26 Studio-G5 kernel[0]: FireWire (OHCI) Apple ID 52 built-in: no valid selfIDs for more than 2 minutes after bus reset.
and
Jan 19 13:19:14 Studio-G5 kernel[0]: FireWire (OHCI) Apple ID 52 built-in: no valid selfIDs for more than 2 minutes after bus reset.
Jan 19 13:22:26 Studio-G5 kernel[0]: FireWire (OHCI) Apple ID 52 built-in: no valid selfIDs for more than 2 minutes after bus reset.
Jan 19 15:09:24 Studio-G5 kernel[0]: disk1s1: media is not present.
Jan 19 15:09:24 Studio-G5 kernel[0]: disk1s1: media is not present.
Jan 19 15:09:24 Studio-G5 kernel[0]: disk1s1: media is not present.
Jan 19 15:09:24 Studio-G5 kernel[0]: disk1s1: media is not present.
there

Weird Firewire Issue since 10.5.6 update

Hey guys!
I'm a musician so I use an audio interface (Presonus FP10) to record my stuff. It's a firewire interface and it used to work perfectly fine.
However, since the 10.5.6 update there seems to be something wrong with my firewire port and I haven't found anything on the web that fits my problem.
If I plug in my interface into the firewire port, it doesn't work. It neither goes on nor is recognized by the OS.
Although, once I plug in my ethernet cable for internet access, it works fine.
Problem with this is that in my music room there is no possibiliy of pluging an ethernet cable.
I hope somebody can tell me what to do in order to get this fixed, whether this problem is caused by Leopard or by my interface.
Thanks,
Mark

That was my first guess, too. See, that's what makes it all so weird:
I have the device plugged in with no other cable. Nothing happens. I have the ethernet cable plugged in without anything connected to that. Nothing happens. I then plug it into an internet router ét voilá! It works...Could it maybe be a lack of electricity coming from a damaged AC-Unit connected to the device?
But then again, it all worked fine up to the 10.5.6 update. Did the apple people do something to the firewire driver?I hear the new Macbooks come without Firewire...

Weird Firewire issues: spontaneous disconnecting of drives

I have bought two 1TB harddisks recently and have been struggling with the connections to my 1st gen Intel iMac core duo.
If I connect the drives each to a different firewire port, everything works fine
If I connect the drives to a "loop through" firewire port on another harddisk, that's fine
Whenever I connect a device to the loop-through firewire on the 1TB, Finder starts to show the spinning ball of death and eventually the system states that the 1TB harddisk is removed improperly.
I have 4 firewire harddisks connected to my iMac, the 1TB harddisks are the last in each chain:
iMac -> Lacie -> 1TB freecom
iMac -> iomega -> 1TB freecom
this setup works fine, but whenever I connect a device on the freecoms I get the problems. I tried switching the ports, same effect. Putting the freecoms first in a chain doesn't work.
Sounds to me that the freecoms have a problem or could it be Mac related? (I'm going to ask freecom support as well)

Since it works when the freecom drive is not first, I would suspect a problem with the freecom drive's daisy chain port.

Weird Firewire Port

Front port of new 2.0MP not working. At first there was absolutely nothing. Then I tried zapping pram and firmware reset. Now what's happening is that my firewire hd is still not mounting, but all the info shows up in system profiler. But, on the other hand, when I open Final Cut Pro with my camera plugged in, the window saying my firewire device is missing shows. If my HD info didn't show in SP, I'd just assume the port was fried, which seems to have had happened more with the October 2005 G5's. Any other suggestions before taking it to the Genius Bar? Any help is appreciated

Nothing. Now, it's not even showing the FWHD info. After doing a bit of research, it seems that this isn't that uncommon. I was planning to get an additional FW card anyway, but I paid a good chunk for this and wouldn't mind it working right right out of the box. According to XLR8your mac, this model(Dual 2G Late October 2005)has a 22% first year major problem rate. The second worst for Apple ever.

Weird square box mysteriously appears

Occasionally after editing a photo in ACR and opening it in Photoshop CS4, a square box appears in the photo, as if I selected a small square area and darkened it using curves. Any thoughts about how to prevent this or how to get rid of the box if it happens? I am using a Mac Pro tower with the latest OS 10.6 (although I remember it happening once using OS 10.4) and the most updated version of CS4. Thanks!!

This is a very strange problem. Sounds to me like some sort of graphics card glitch more than anything else.
Is Camera RAW genuinely rendering a square selection darker than the surrounding pixels? when you move the image around your monitor, and measure the pixels with the eyedropper is this still apparent?
Since its most likely to be what I suggested above - try turning Open GL on and off in Preferences.

Trying to fix dead Firewire

My firewire ports mysteriously died the other day. Big drag.
I've found a lot of posts on software/firmware fixes, but to no avail so far. I've tried resetting the ports by unplugging the machine for a half hour, resetting nvram and resetting all in open firmware, zapping the pram multiple times, and doing an archive and reinstall of the OS.
Anyway, it seemed like it must be hardware, so in trying to keep as close to my budget of $0 as possible, I bought a via card on ebay. it's a combo firewire/usb2 card. the plan was to replace the usb2 only card that i currently use.
anyway, the computer doesn't recognize the card, the firewire ports, or even the usb ports. installing the driver that came with the card made no difference.
looks like i need to get my money back and get another card. it has to be a combo firewire/usb2 card with 4 usb2 ports and at least 2 firewire ports. i need the combo card because i have no more free slots.
any recommendations? or any software stones that i haven't left unturned?
much appreciated.
g4 dual processor gigabit ethernet Mac OS X (10.4.4) 1.75 gigs ram

Here's the Adaptec USB 2.0/FireWire combo card. If you need more USB ports, I'd suggest a powered hub.

Can I daisy-chain a G-RAID Pro 2TB with a bunch of other G-RAID's?

Hey there,
I'm wondering if there would be any issues adding a G-RAID Pro into my current daisy-chained G-RAID configuration.
- I've got seven 500GB G-RAID's all daisy-chained together and running into my G5.
- Two of my 500GB G-RAID's are RAIDed together so the first one is connected to the onboard Firewire 800 port of my G5 and the other to my additional Firewire PCI card.
- The remaining 5 drives are daisy-chained into the drive that is connected to the onboard FW 800.
This hasn't posed a problem thus far, but I'm wondering if adding a whole new G-RAID Pro is possible with this configuration, or if there's anything I should know before I decide. I left a message for the tech department at G-Tech but they're so busy over there I figured I check in here.
I'm thinking about getting the G-RAID Pro 2 TB because I have 2 projects coming up for which I'll need a whole lot more space than I currently have. If anybody has any other hard drive suggestions I'd be open to them as well, of course.
Thanks a lot for any thoughts,
Joni
Mac G5 Mac OS X (10.4.7) FCP 5.0.4, G5 Dual 2 GHz, AJA Kona 2 card, 5.5 GB DDR SDRAM
Mac G5 Mac OS X (10.4.7) FCP 5.0.4, G5 Dual 2 GHz, AJA Kona 2 card, 5.5 GB DDR SDRAM

Jerry, did you see my post the other day? I don't know if there is a conflict or not, but I've had some serious firewire problems for the last year and just last weekend I was unable to access any media files that were on a lacie for a specific project. And when I tried to copy the files (after closing fcp and running diskwarrior on the drive), I kept getting error messages. When I came in the next day and started the system with the graids disconnected, the lacie performed perfectly. Seems like there might be some sort of conflict. Or just a weird one time occurence. But since I've been having all sorts of weird inconsistent problems with firewire drives and I did have a mixture of lacie and gtech drives my instinct says it might be the source of the problem. I just installed a burly 5 bay sata enclosure, so my need for firewire drives, except for sneakernet, is over.
I post this kind of stuff with the hope that if someone is experiencing weird firewire behavior, they can try to eliminate at least this possible cause.

Freezing video when exporting

The past 3 weeks at work on my G5, I have been experiencing a problem with iMovie. Problem is when I am done editing and go to export thru my GL2 Canon camcorder to my VCR, about 20 minutes into exporting my video freezes on the monitor, but the audio is still going. I was wondering if iLIfe '06 will help this bug issue? HOPE there is help out there!
Focused

Hi Foucused:
I'm going to tell you the same thing I just told another poster having similar problems.
Sometimes updating your OS system one update at a time causes weird firewire problems. (ie., update 10.3.8 to 10.3.9 etc)
The Combined System Updater from Apple may fix this. You might try this in case the stutters are being caused by a Firewire communication problem. It won't hurt anything to apply this update on top of your existing System updates.
http://www.apple.com/support/downloads/macosxcombinedupdate1039.html
Can't hurt-
Sue

No audio when I print to video

Video is fine, in AV settings I have Firewire audio selected. Audio sounds fine from timeline but when I print to video i get nothing not even a tone with bars at beginning of print down. I've tried different cameras so I'm thinking it is a setting in FCP that I don't have right... Any suggestions? could something like this be the cable I'm using or a weird Firewire problem like not enough power because too many devices are plugged in? I know that the "official" word is (with puffed out chest) Firewire can handle up to blah blah blah devices, But my experience with Firewire is that it is finicky. So, just wondering if it could be something like that. Off to do some experimenting...
Ive tried unplugging all other firewire devices and works fine on my powerbook with what seems to be the same settings...?

Hi,
It appears from what I found online that there are some A/V settings you should check before exporting your video.
Check out this first link(make sure to click in the " Re:" lnks to read the replies from other users):
http://forums.creativecow.net/readpost/8/967816
Also, there is another link with another users experiencing the same problem:
http://www.2-popforums.com/forums/showthread.php?t=71453
Let me know if that information helps you,
Vicente

I think I have a GHOST in my computer! Need some exorcism!

OK, it's not a ghost, but it's a mysterious "t" file that shows up on my office computer's desktop whenever anything is moved to/from the desktop or saved on it. Every time I click on it, it disappears!! It doesn't seem to cause any other problems, but I want to make sure that it's not a sign of anything scary.
For your convenience, here's a photo too!
http://flickr.com/photos/verushka26/2311957380/in/photostream/
Thanks so much for any help/insight,
Vera
PS - I've totally verified and repaired the heck out of that hard drive
PPS - I'm not too computer-savvy, although I can learn quickly. So if you drop some Terminal Terminology on me, please be precise and thorough.
PPPS - Isn't it funny how a lowercase t actually looks like a little white floating ghost??

I can't comment specifically about your mysterious file, but judging from the screen shot you put up you're running your boot drive much too full. A general rule of thumb is that you should have at least 15% free and yours has only about 4% free. IMHO you're courting disaster. Having that little free space can/will cause file corruption problems, your computer to slow down/feel sluggish and may cause weird problems like mysterious 't' files…
I'd try freeing up some space and seeing if the 't' file goes away.

The Great iMac FireWire Mystery

I'm stumped on this one and was wondering if anyone had any suggestions.
A couple of months ago I replaced my mother's mirror door G4 (2x1GHz) with a 20" 2.16GHz Intel iMac (the last of the all-white iMacs). Her G4 had an 80GB and a 60GB internal hard drives, with the 80GB being the boot drive and the 60GB being accessed exclusively by Retrospect to do incremental backups on a nightly basis and a recycle backup once a month. This system worked quite well for the past couple of years.
Her iMac has a 250GB internal drive. I added a Newer Tech miniStack v2 200GB hard drive which I have connected via FireWire. Using the same Retrospect-based system, backups are performed regularly. However, there's a fly in the ointment. Occasionally and for reasons unknown the computer will unmount the FireWire drive all by itself. This happens regardless of whether the computer is idle or in use. Power cycling the drive will remount it and all is well afterwards -- until the next time. It seems to happen about once every 2-3 days. The drive can be connected for 2-3 days at a time without any problems, but then it just disappears. Poof.
Things to remove from the list right off the bat...
1. The miniStack drive is fine, having performed its duties on several other computers in the past and operating flawlessly in the same capacity on other computers (including a MacBook Pro and an aluminum iMac).
2. OS X is set to sleep the drive when it's not in use. Since the incremental backup process takes less than five minutes a day to complete, having the drive spun up 24/7/365 makes little sense. The drive happily spins up when Retrospect does its thing (assuming the drive is still on the desktop at that time, of course) and the drive happily spins down shortly after Retrospect finishes (again, assuming...). A suggestion of "turn drive sleep off" is not acceptable for this reason, and for the fact that the other computers that the drive was attached to also had drive sleep enabled and didn't have this problem.
3. The OS X installation (10.4.10) is very clean, having been installed when the iMac was installed. There are no "haxies" or anything weird like that installed. The only "modification" to the system is enabling the DEBUG menu in Safari. When I put the iMac into target disk mode and boot my wife's MacBook Pro from the iMac's hard drive, the miniStack drive does not show this problem. If the OS X installation was to blame then the MacBook Pro should also have lost the drive.
4. I've also gone the other way, booting the iMac from the MacBook Pro's OS (10.4.8 and 10.4.10) in target disk mode. The problem remains on the iMac.
5. The iMac itself has been checked out by Tekserve and the Apple Store, both in Manhattan, and has been pronounced 100% without error or problem. The iMac also passes the hardware test provided on the Apple CD and the TechTool Pro diagnostic. All other aspects of the computer perform flawlessly.
6. The FireWire cable has been replaced, and both the old and new cables are perfectly functional with all other drives and computers tested.
7. With one exception, other FireWire devices on the iMac seem to work flawlessly in all other regards. I've tried two camcorders, an iSight webcam, a friend's FireWire-to-MIDI box, a DVD burner, and a FireWire CF card adapter. All perform perfectly. The one exception is a 60GB portable FireWire hard drive. This drive performs exactly the same way on the iMac; that is; you can connect it and use it without a problem, but if you keep it connected for 2-3 days it too disappears from the desktop just like the miniStack drive. (I had a 2GB CF card connected to a FireWire CD card adapter, and it was mounted on the desktop as a formatted Mac volume. This card stayed on the desktop for five days without a problem, so the problem seems to be localized to actual hard drives and not just mass storage devices.)
8. The iMac performs perfectly in target disk mode. I had it in TDM connected to the MacBook Pro for several days and it never disappeared.
So, I'm at a loss. My current "fix" is to connect the drive to the iMac via USB and that seems to be working. That seems to indicate that it's a FireWire problem but I've never heard of one so specific to one particular category of hardware before (e.g., hard drives). Regardless, that doesn't solve this mystery. Yes, the drive works under USB....but why not FireWire like it should?

I have been having similar problems with a Mybook FW HD disappearing and remounting at random intervls. I am in the process of replacing it with a Fantom 1000.( I have a 300G Fantom with an Oxford chipsest that has been completley reliable for > 2yrs attached via FW400).
The Fantom 1000 mounted immediately with FW800, but as it was Fat32 formatted I decided to erase and reformat with MacOS extended using disk utility. I haven't been able to mount the final product, although it is recognized and described by the System. Disk utility can't verify or repair due to a formatting error.. I should mention that disk utility never gave any indication that it had finished the formating.. the blue barber pole was still spinning after 12 hrs
How long should it take to format a 1T disk?
Anyway now I am trying using a FW400 port and am about 1 hr into it...... next I will try USB and if that fails I will try to return to FAT 32... I should have quit while I was ahead
My question .... is this a FW problem, a Fantom problem or a formatting (Disk utility probem)

Firewire 800 speed weirdness

I recently purchased a four bay RAID array to replace the multitude of external drives that I've collected over the years. I installed four 1TB drives in a RAID 5 configuration to make up a 3TB array. The RAID model is the DM4 from Sabio (Sabio DAS DM4).
I connected it to my iMac via Firewire 800 (it has 2x FW800 ports, 1x FW400, 1x USB 2.0, 1x eSATA), and after hours of copying from the external USB drives I finally got everything migrated over to the new monster drive. However, I am seeing some weirdness in transfer speeds.
My iMac specs are as follows:
Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.8 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: IM71.007A.B03
SMC Version (system): 1.21f4
I was testing copy speeds to the array by using the cp command in the terminal and watching the disk activity in iStat Menus (but you can get the same information out of Activity Monitor on the Disk Activity tab). Using cp, I was only able to push about 45MiB/s, which I found strange since this is near the maximum of FW400 (50MiB/s).
The truly weird thing, though, was using the same file, copying to the array in the Finder pushed the transfer up to 65MiB/s. The main question I have is why would that be? I've tried alternates on the command line as well, such as rsync but nothing moves as fast as the finder.
Now I get that writing to the array is going to be slower considering that I'm writing parity to all the drives, but I don't get the speed difference between the command line tools and the GUI Finder. Maybe it's a caching issue?
I'm also seeing a hit between the command line and the Finder with reads from the array. Unsurprisingly the reads are better than the writes, since I'm pulling from four drives. With the Finder, I'm able to pull at an average rate of 75MiB/s. The command line I read around 63MiB/s to 66MiB/s.
All these tests are the same file. The drive in the iMac is actually brand new (1TB Seagate), and it has barely anything on it so it's not some type of fragmentation issue. The only external drive on the iMac is this Sabio array.
So, does anyone have any ideas why I'm seeing such a speed difference between the command line and the GUI? Also, is there a way to work around this slow down on the command line? Hopefully someone knows more than I've found thus far.
Thanks for your time,
Adam.

You're right, I could use the Finder to do all my copies, but I typically don't use my systems at that level. I know that sounds weird, but I'm a Linux admin and systems engineer by trade and I live in the command-line/terminal all day long. I am a lot faster at manipulating the system via the command-line than I am with point and click. There are a lot of times that I just quit the Finder outright so I don't have to look at my Desktop icons (though I have the desktop turned off right now so I don't see any icons at all).
I generally use my iMac as a media center, where it serves media to my PS3 and what not. I also use it for some development work. My wife will use the machine for graphic design when she is working form home thus she's in the Adobe Creative Suite a lot of the time. With that said, the machine is mutli-user, and I typically use command-line programs to ensure that what I copy is copied correctly via rsync, or the cp -Rp commands.
Now, my observations were not really a concern, but more of a why-on-earth-is-this-happening type of thing. In the past, it used to be a lot faster and more efficient CPU wise to copy via the command-line than it was in the Finder. Now with Snow Leopard they seem to have gone the other way around. To me, it just seems that the command-line equivalent, which doesn't have any glitz or glamour at all, should be natively faster than the Finder, which has progress bars, drag-and-drop, etc.
So yeah, I can use the Finder, but it's not what I use normally.

Updated: Firewire audio recording on brand new iMac makes weird digital noise

I am running Ableton Live 8 Suite on a 2011 Entry level iMac. i am using an Maudio Firewire 410 with a FireWire 400 to 800 cable. recently when i record audio (say from a guitar) the audio will cut out and be replaced by a wierd low freq digital noise. i uploaded a clip of it. its not just static. it will come in and out as i play.
http://cl.ly/3f3R2H2z3H3K3F3z1P3d
Things i have tried:
-different guitars
-Maudio FireWire Solo (different interface)
-uninstalled and reinstalled the driver
-Different firewire cable
-turned off Bluetooth on computer and Bluetooth devices
-turned off airport
when i restart the interface or computer it works for about 5-10mins then cuts out again...
but i still get normal audio through it (iTunes, internet, even Ableton)
it seems to be isolted to just audio input. i had multiple tracks playing in Live. my input was working fine but when it punched in to record it morphed to the weird digital noise.
i could record a single channel fine with nothing else playing but recording with multiple channels playing seems to "lock up" the audio though i am only using 25% CPU...
is this something with my iMac or Lion? i changed out interfaces, cables, and drivers....thats the only thing i can think of…
any thoughts from you smart people out there?

ok so i tried a differnet cable and the same thing happened...
i had multiple tracks playing in Live. my input was working fine but when it punched in to record it morphed to the weird digital noise.
is this something with my iMac or Lion? i changed out interfaces, cables, and drivers....thats the only thing i can think of...

WEIRD FIREWIRE/DV MYSTERY

Similar Messages

Maybe you are looking for