Corrupted Quicktime file, CHKDSK issue

Hi there,
I have a corrupted/unreadable Quicktime file, so I can't uninstall it or reinstall a new version until I get rid of it or fix it. I'm trying to run CHKDSK, but it won't run on reboot. I went into Task Scheduler, and the log says it fails to run because of "Login failure: Unknown user name or bad password". When I go into the properties of the scheduled task, I have "Run whether user is logged in or not" selected, so I don't know what else to do...

Hi, bozzah
I probably can do it.
I will need two things:
A sample of your corrupted file and a 10 seconds good recording done with the exact same settings as the corrupted file.
Drop me an email and I explain you the details.
Regards, BJ

Similar Messages

Corrupt quicktime files in Final Cut Pro

I have several long quicktime files that I used in a Final Cut Pro project. The files were captured to a firewire drive. Because the drive was formated in MS Fat32, the long capture was broken up into 2gig files with the same name and a number added (file, file1, file2, etc.) The movies worked fine for several months but now won't open in Final Cut or Quicktime. All that shows up is player that looks like an audio file but has no sound.
I recently reinstall my OS, but I tried opening the files on another mac and got the same results.
thanks,
Jim Thompson

I tried your tip but it didn't seem to work. The clips have a "v" after the file name if that helps. The first clip in the sequence opens like there's no video and will play, but has no sound. the second clip gets the error "not a movie file"
I have Quicktime Pro but don't know how to join the clips together.
Any additional advice would be appreciated

How to fix a corrupt QuickTime file?

Hey all,
Today I recorded all of our church services via iMovie (one long 4 hour clip), as I have been doing for more than a month now. However, the guy running the camera turned the camera off before I told iMovie to stop importing, so iMovie literally trashed the file.
I pulled the 50GB file out of the trash, but now QuickTime is giving me an error: "The movie could not be opened. The file is not a movie file." When I open the file in MPEG Streamclip, It says "File open error: unrecognized file type", and I click "Open Anyway". It tries to open it, but sfter 20 minutes, I get the error: "File open error: can't find video or audio tracks".
Any idea how to fix this file? (That is, outside of paying $150 for this service: http://simplemoviex.com/movierepair/repair.html .) It is not mission critical to have this file, but there was a baptism this morning that I would like to have...
Matthew

Hi Janke,
If you have Time Machine or another backup system that keeps multiple versions, you may be able to work our way back to a version that does not demonstrate the corruption.
Regards,
Barry

Corrupted Quicktime files

recently our company purchased a new Intel dual quad with 4 GB ram. We are running Leopard. We have a Kona LHE Card and an AJA Break Out Box for Analog. Right away we found problems were happening but the weirdest problem we have is that everything we do with Quicktime results in corrupted files. Just a basic drag and drop from another hard drive, will result %80 of the time in a file that eitehr wont play or will play but have the pink digital static midway through for a few seconds. When we bring a completely clean Quicktime into FCP, most of the time it will then have digital corruption on one frame or another. When we go back to the original QT file it is clean. If we take a perfectly Clean QT file and try to save as or Export, we will recieve a corrupted or distorted QT File in return. Basically every time we touch a QT file something gets corrupted.

I don't know how to fix what was already modified, but in Premiere Preferences, there is a box that is checked by default, something about "Write XMP data" or similar, you'll want to uncheck that.
Thanks
Jeff Pulera
Safe Harbor Computers

Corrupt Quicktime files from Photo Booth

I am looking for a Quicktime Repair tool for Mac OS X. Preferably one that can re-write / repair quicktime headers and verify video frame data.
My 4 year old was making some videos of himself using Photo Booth .. my wife and I happened to discover them a few nights ago and were laughing like mad.. was really cute and funny.
So you can imagine our disappointment when I logged in today to move them to a safe location, and couldn't see them in Photo Booth. Inside the filesystem, I show a number of .MOV files, but none of them play. Quicktime reports "The movie could not be opened. The file is not a movie file." Seven of Fourteen movie files in the folder are like this.
When I try to open it in VLC I get a more detailed message in the message log (i've snipped it down for the purpose of posting)
access_file debug: opening file `/Users/family/Movies/kids/Movie 36.mov'
main debug: using access2 module "access_file"
main debug: pre-buffering...
main debug: received first data for our buffer
main debug: pre-buffering done 851942 bytes in 0s - 7424 kbytes/s
mp4 debug: found Box: mdat size 32
mp4 debug: skip box: "mdat"
mp4 debug: found Box: wide size 8
mp4 debug: skip box: "wide"
mp4 debug: found an empty box (null size)
mp4 debug: dumping root Box "root"
mp4 debug: | + mdat size 32
mp4 debug: | + wide size 8
mp4 debug: file type box missing (assuming ISO Media file)
mp4 error: MP4 plugin discarded (no moov box)
I loaded the file up in 0xED (a Hex Editor) and the raw file header in the BAD files look like:
... mdatftypftypftypftypftypftypftyp....wide....mdat h.......
while a GOOD file header look something like
... ftypqt ....qt ......................wide...smdat h .....
It looks corrupt to me. I'd like to think that only the header is corrupt, and the video data is still fine ... I was curious if anyone had anything to assist?
The only other thing I could think about doing was hexediting the headers, swapping good headers for the bad ones (since the videos from Photo Booth share the same dimension, FPS, etc)

Was this problem ever solved? I've got a similar one.

Corrupted QuickTime file

Hi All,
Here's my problem.
Last night I was capturing a live A/V performance using "New Movie Recording" in QT PRO. Hooked via firewire to my laptop (PowerBook G4, 1ghz) I had a Canopus ADVC-100 capture card. I used the "Good (MPEG-4)" settings in the recording preferences. All was fine and I ran some tests before the main recording which all worked well. I was recording to an 7200rpm external LaCie hard-drive, with at least 80GB of free space.
The recording was all fine, though quite long at around 3 hours. The final file size has come in at around 400meg.
I was able to stop the recording at the end of the show however before I was able to save the QT file, my external hard-drive was accidentally unplugged by someone a little too keen on packing up after the show. The drive naturally dissapeared and subsequently the QT file has been corrupted . When I try to open it, I now get the "Error Opening Movie - This movie could not be opened" dialogue.
I can see the QT file on the hard-disk, and when I 'get info' on the file I can see that it's 407 megs large. The OS is seeing the .MOV file fine, icon and so on, and still attempts to open the file in QT when launching out of the finder.
My question; is there some way of repairing the file so that I can get QT to play it? I thought an application like Autodesk's 'Cleaner' might help, however I don't own a copy of it, and am unlikey to buy it just to recover this file.
Any help any of you can provide would be fantastic.
Regards,
Boz
PowerBook G4, 1G Mac OS X (10.4.7)
PowerBook G4, 1G Mac OS X (10.4.7)

Hi, bozzah
I probably can do it.
I will need two things:
A sample of your corrupted file and a 10 seconds good recording done with the exact same settings as the corrupted file.
Drop me an email and I explain you the details.
Regards, BJ

Lightroom corrupting RAW files? Hardware issue?

I've started having some issues with RAW files being corrupted when I open them in Lightroom. I've done a lot to troubleshoot and narrow down the symptoms, and here is what I can tell you. If anyone has any ideas for how to solve this, I'd really appreciate it!
Equipment
Canon 7D, 1 32GB CF card, 1 4GB CF card
Lenovo Laptop, Win 8; Lightroom 4
Dell PC, Win7, Lightroom 5
Here's what the corruption looks like in my Library view. Note that all of the photos are the same. I just rapid-fired a bunch of shots down the hallway to test this out.
I first noticed the corruption on the PC, pulling photos from the 32GB card. I bought a new hard drive (SSD hybrid), installed a clean version of Windows 7, and upgraded to Lightroom 5, then the 5.3 update. I re-downloaded some photos from the 32GB card, and they still show up corrupted. So here is my further testing:
I shot a series of photos like shown above on the 32GB card, downloaded them on the laptop with a new USB cable. The photos look good.
I shot a series of photos on the 4GB card, downloaded them to the laptop with the same cord, they look good.
I imported the same photos photos from the 4GB card and from the 32GB card on the PC with my existing Lighrtoom Catalog and they are corrupted.
I created a new Lightroom Catalog on the PC and downloaded the same photos from the 4GB card and from the 32GB card on the PC and they are corrupted.
So what gives? I think we can rule out corruption or issues on the hard drive, the OS, the USB cable, and both of the CF cards. It baffles me that a new HD, clean OS install, new catalog, new USB cable, and upgraded Lightroom haven't solved the problem. Is it possible that there is some other part of the hardware on my PC which is corrupting the files?
I'd love some insight if folks have any ideas!
Thanks,
Adam

Was this ever figured out AdamCohn? I have a very similar issue. I have actually watched two photos over the last two days become corrupt while viewing them in Lightroom. I am not suggesting LR is the cause (as I know this is almost always hardware related) but it has happened right in front of my eyes while LR is interacting with the images (I believe).
Scenario:
Images were
* Imported into LR on different days (about a week apart)
* Imported to different hard drives during import (one an SSD, another to a typical HDD)
* Behaving normally in LR until corruption (i.e. previews were built without issue, was able to develop and export images. Showed fine in Finder).
After viewing the images in Loupe view and watching them flip instantly to a visual mis-mash similar to what you showed the images were permanently screwed. The appear the same way in Finder and in Photoshop
I have not noticed any other issues in any other app or area of the system. Everying seems to be running smoothly.
Troubleshooting:
* Memory tests:
- Built-in Apple memory test (normal + extended).
- MemTest (as described here: MemTest for Mac OS X Tests your RAM). Ran it twice, all tests passed.
* I am running some HDD checks now, but with the two images being on two different drives I suspect the likelihood of this being a drive issue is extremely small.
Suggestions?

The file \ipod_Control\iTunes\iTunesDB is corrupt & unreadable run chkdsk

the file \ipod_Control\iTunes\iTunesDB is corrupt & unreadable run chkdsk utility.
iTunes recognizes the nano. it seams to be accepting songs, but when I drag and drop this is the message that appears. None of the songs I dragged and dropped are on the nano. The nano seems to be working fine otherwise.
HELLLLLLPPPPP!!!
Thanks

hi Andrew!
first let's try this technique:
iPod: What to do if Windows displays an "itunes.exe - Corrupt File" message
keep us posted. (if he's around, Da Gopha may be able to help with more advanced treatments.)
love, b

MPEGstreamclip corrupts m2t files translating them into Quicktime for FCP

Recently purchased and tested the Firestore FS-4. Had no problems whatsoever capturing the clips perfectly as m2t files in the FS-4.
But when I run those m2t files through MPEGstreamclip to translate them into Quicktime files so FCP can read them, the clips get corrupted.
The translated QT files seem speeded-up as though I had been recording through my Sony Z1U at high speed / fast forward speed. Please see the file in question, pay close attention to how the cars go by at top speed in the middle of the clip:
http://www.joric.com/freewayclip.mov
No problems with the m2t files, the problems occur after those files get translated into QT files.
Is MPEG streamclip the problem? Is there any other solution for translating m2t to Quicktime other than MPEGstream clip???
Desperate to find a solution.
- Nicholas

So, I take it QT Pro will not handle m2t files? I just downloaded Streamclip today, and it worked just fine for my application (demux mpeg-2 file). If you are desparate, as you say, you could try SnapzPro by Amborsia Software. (I have no relationship with them--other than being a customer.) You can capture the video going to your monitor and save it in any QT format your system can handle. It only works with certain video cards, so make sure you can use it before you purchase--but I'm pretty sure there's a trial version. So why does this Firestore save in m2t format?

I am trying to convert a standard definition AVI file 720x576 widescreen file into a full sized Quicktime file in imovie but having cropping issues

Hi
I am trying to convert a standard definition AVI file 720x576 (16:9) file into a full sized Quicktime file in imovie 11. When importing the file I get two options either import as large 960 x540 or full original size. So I choose full original size but when I drag this imported clip to my timeline the bottom of the clip has been cut off? I tried to export it as a quicktime file thinking that perhaps it might resize to the original size but of course that was wishful thinking
Any ideas appreciated?

Hi No I have just checked its definitely a PAL 16;9 project. I am also slightly confused because when importing the video into the project it has squashed it into 4:3 format even though my file is 16:9?

Corrupt sparseimage file (not same old Filevault issue)

I'm having a problem -- I have a corrupt Sparseimage file, but none of the solutions that others have proposed have worked.
No matter what I try, it keeps getting reported as corrupt.
For example, the "half mount" tip that others have used to recover things:
$ sudo hdid -nomount SecureSparse.sparseimage
Password:
hdid: attach failed - corrupt image
That's all I can get. Launching it in the finder gives me the same thing, only in a dialog box.
Trying to verify or repair it in Disk Utility does the same.
The most verbose response I've gotten out of any utility is this:
$ hdiutil convert -format UDZO -verbose -o disk.dmg SecureSparse.sparseimage
hdiutil: convert: processing "SecureSparse.sparseimage"
DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score 200, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: interface 4, score -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: interface 5, score -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CCarbonBackingStore
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding
DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding
DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CUDIFEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding
DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding
DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIDiskImageInstantiatorProbe: interface 0, score 0, CDARTDiskImage
DIDiskImageInstantiatorProbe: interface 1, score 0, CDiskCopy42DiskImage
DIDiskImageInstantiatorProbe: interface 2, score -1000, CNDIFDiskImage
DIDiskImageInstantiatorProbe: interface 3, score -1000, CUDIFDiskImage
DIDiskImageInstantiatorProbe: interface 5, score -100, CRawDiskImage
DIDiskImageInstantiatorProbe: interface 6, score -100, CShadowedDiskImage
DIDiskImageInstantiatorProbe: interface 7, score 1000, CSparseDiskImage
DIDiskImageInstantiatorProbe: interface 8, score -1000, CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: interface 9, score -100, CWrappedDiskImage
DIDiskImageInstantiatorProbe: selecting CSparseDiskImage
DIDiskImageNewWithBackingStore: CSparseDiskImage
DIDiskImageNewWithBackingStore: instantiator returned 103
convert: unable to recognize "SecureSparse.sparseimage":
corrupt image.hdiutil: convert: result: 103
hdiutil: convert failed - corrupt image
I am somewhat desperate here. I have several backups of this sparse file, but they are ALL CORRUPTED IDENTICALLY. (My machine syncs to the backup server every night, and apparently it synced after the corruption happened, and clobbered the un-corrupted version.)
Does anyone have any idea how to interpret the above messages? I'd be interested in just knowing why this happened for a start, and in what way the file is corrupted...I'm willing to invest significant resources in recovering the data.
Most of the recovery utilities I've seen will only work if Mac OS X will partially mount the image, and that isn't the case here.
Power Macintosh G5 Dual 2GHz Mac OS X (10.4.6)

Does anyone have an answer to this. Lots and Lots of data lost.
The tail of
hdiutil attach -debug myimage.sparseimage
syncPhysicalAndLogicalForkLengths: returning 0 (cached logEOF: 3592318976, physEOF: 3592318976)
CBSDBackingStore::closeDataFork: about to close 5CSparseFile::~CSparseFile: WARNING flushing header and index nodes failed. Invalid argument
syncPhysicalAndLogicalForkLengths: entry (cached logEOF: 3592318976, physEOF: 3592318976)
: returning 0 (new cached logEOF: 3592318976, physEOF: 3592318976)
DIDiskImageNewWithBackingStore: returning 0x00000067
DIResolveBackingStoreToDiskImage: unable to resolve to any disk image class. 103.
DIResolveURLToDiskImage: resolving disk image format failed. 103.
status proc called: attach
error code: 103
status proc called: cleanup
2006-05-25 18:36:04.170 diskimages-helper[547] DIHelperAttach performOperation: returning 103
2006-05-25 18:36:04.170 diskimages-helper[547] DIHelper perform_operation: returning {payload = {}; "result-code" = 103; }
2006-05-25 18:36:04.170 hdiutil[546] connectToFramework: proxy has finished operation
2006-05-25 18:36:04.171 hdiutil[546] results are: {payload = {}; "result-code" = 103; }
2006-05-25 18:36:04.171 hdiutil[546] _threadResultsError is 103
2006-05-25 18:36:04.171 hdiutil[546] connectToFramework: terminating proxy
2006-05-25 18:36:04.171 diskimages-helper[547] terminateHelper
DIHLDiskImageAttach() returned 103
<CFDictionary 0x323870 [0xa08011c0]>{type = immutable, count = 0, capacity = 0, pairs = (
hdiutil: attach failed - corrupt image
nebula:/Volumes/Europa/bad/Disk Images cgraham$ 2006-05-25 18:36:04.272 diskimages-helper[547] -DIHelperAgentMaster terminateUIAgentConnection
2006-05-25 18:36:04.272 diskimages-helper[547] -exitIfPossible:0 (_drivesServed 0)
2006-05-25 18:36:04.273 diskimages-helper[547] -exitWatchThread: trying to get exit lock
2006-05-25 18:36:04.273 diskimages-helper[547] -exitWatchThread: got exit lock
2006-05-25 18:36:04.273 diskimages-helper[547] -exitWatchCompleted:0
2006-05-25 18:36:05.273 diskimages-helper[547] suicide:<NSCFTimer: 0x320770>

Corrupt image files cause upgraded iPhoto to crash

I have been spending some time trying to find and remove corrupt image files from my iPhoto library. These are not just scrambled images when viewed they crash any and every program you view them with. Including Finder. I accidentally put one on my desktop and finder went into a auto restart cycle I could not stop. until I removed the file with pathfinder. I have found about 30 of these so far (my library is about 25,000) Many of these are in the data file but some are not. They are of all types (jpg,tiff,psd) Thorsten Lemke, (Lemke Software) tells me it is a quicktime issue.
Here is a link to one of these files. Warning it will crash safari if you try o view it.
http://vincentdavis.net/try/try.jpg
Here are my questions.
1. is there some way to fix these
2. is there some efficient way to find and remove/fix them?
3. how did this happen? I had no problem before update (that I knew of)
Thanks
Vincent

I did try the link, and as you said - it crashed Safari. However, I have google searched and also searched the Apple Support sites for 'fix corrupt images' with no luck. I'm sorry but I think the only way of knowing is to try and open each of them.
However, I did read on Macworld's site once that sometimes photoshop or other image editing programs can open the corrupt files.
Sorry for not being much help here - I hoped that my first suggestion would have done the trick.
Sam

Corrupted quicktime video during backup

When I tried copying over a quicktime video from one hard drive to another, I noticed that it cause major issues with the videos image and audio. Completely scrambling the video and creating a loud buzzing sound when the video played.
Here is a still frame of the corrupted quicktime video.
Fortunately the original video file was fine so I just copied the file over and it was okay the second time, but does anyone know causes this to occur? How do you prevent this from occurring in the future. What is it called when this happens?

uluulu
Happened to me once as well. Never happened again but I am a curious sort. Let's see if an expert can help. This reply will give the Q a boost in the list.
CCC

Corrupt audio file prevents me from opening Logic project file

Hello,
I've been running Logic 8 for a couple years off my MacBook and have never encountered any significant problems of file corruption until recently.
The issue I encountered is this:
I've been producing a lengthy track in an on-going Logic project file for some time and after completing a recording session I saved and started deleting excess track copies to clean up my arrange window. Upon doing so Logic unexpectedly crashed.
After attempting to reopen the project file, it started its normal process of loading its respective audio files, but now it hangs on one particular audio file indefinitely (I'll refer to it as 'audio file x' for ease of reference), freezing and crashing Logic as a result. All of this project file's auto backup files are also incapable of being opened without giving me the same result and crashing Logic.
I have no way of opening this project file and getting at my most recent saved sequence!
I've tried removing this corrupt 'audio file x' from the project's audio folder and dragging it to the desktop, but this had no effect and I still can't open any recent version of the project file.
Older saved copies of the current project file do still open though (most likely because they were saved prior to the corruption caused by this suspect 'audio file x.') When opening an earlier iteration of the project, I get a message '1 invalid audio region found' (I assume referring to the corrupt suspect 'audio file x' that I removed to the desktop) but the project file is still able to open.
I realize I could import the audio files from the most recent version of the crashed file to an older project version and reconstruct things back to the way they were, but it would take me a lot of time and I'm hoping there may be some way to recover the un-openable project file by getting it to stop looking for this corrupted 'audio file x' on startup.
When I click 'show package contents' of the Logic Project file, I notice two items labeled 'displayState' and 'documentData.' From my troubleshooting I've come to the basic understanding that the 'documentData' file contains all the sequence data and settings for its respective Logic Project file.
I think the 'document data' of the unopenable project file in question may be corrupt because whenever I replace it with the 'document data' from an earlier Project file version, the file is able to open. This doesn't do me much good though, because it's document data from an earlier iteration of the project and I need to be able to get at the current sequence I had right before my file crashed.
Is there anyway to open a project file without letting it load its audio files? Or is there anyway I could get inside the 'document data' file to delete the reference/pathway in its audio bin to the corrupt 'audio file x' its hanging on?
Any insights would be greatly appreciated. I'm hoping there's some way I won't have to repeat a couple days worth of work. Thanks for your help!

stooby3535 wrote:
After further troubleshooting I've realized that the suspicious audio file that prevents the project file from opening is actually not corrupted itself. I can still play the audio file in other media software like Quicktime, etc. with no problem.
This leads me to believe the problem opening the project file lies solely with the corrupted 'documentData' file.
Does anyone have any ideas about how I could somehow open this project file and delete the reference of the troublesome audio file from the project's audio bin?
Well... it really sounds like the project itself is corrupted, that's one of the reasons all project files won't load from a certain point on.
Try this.
Reboot the Mac.
Open the Applications folder and boot Logic from it's icon.
As soon as the Logic Logo/graphic window appears on the screen hold down the control key. You will see a message pop up that says something like "Launch the Core Audio Driver" there will be yes/no choice available... select NO.
Go to the File menu and selct "open" go find your project file and see if it will open. If it does.. delete the audio file in question... however.. I would also look at any plugins you recently installed and are possibly using in this project...this sounds more like a plugin problem rather than an audio file problem, but that's just a gut feeling.
Anyway, if it opens delete whatever you suspect and save under a different name.
Reboot Logic and see if it can load the project.
pancenter-

Corrupted itunes file???????????

someone please help
in the next two days
i am leaving the country for 18 days and i MUSt figure this out soon. Whenever i start iTUnes a little bubble/message pops up on the taskbar on the bottom .
It says one of my itunes files if corrupt. I uninstalled it , reinstalled, and it gave me the same thing. Once it was UNinstalled, i downloaded it and ALL of my old itunes library was still in there and it was still corrupt. SOmeone please help.
-confused one--

Does it look like that?
Fix: Check Disk Utility
Read this before running the fix!
We recommend using the latest iPod Updater to restore iPod because this will address the file system issue and will also defragment the iPod drive. Although you can use the Chkdsk utility to fix file system errors on the drive mapped to iPod, Chkdsk will not defragment the drive.
Warning: The restore process cannot be undone. All of your songs and files will be deleted. Always make a backup of your important data.
Tip: Make sure you always eject iPod properly and that you wait for the orange light to stop blinking before disconnecting iPod shuffle. Click here to learn more about iPod shuffle status lights.
This issue may be more likely to occur on iPod shuffle if iPod shuffle's file system has become heavily fragmented. A restore will eliminate fragmentation. Chkdsk will not.
If this information doesn't help you, I did a search to find some of this information but you can look for more topics related to your issue... by Clicking Here. - Apple Forum Search

Corrupted Quicktime file, CHKDSK issue

Similar Messages

Maybe you are looking for