xp blows... this makes no sense

Archived from groups: microsoft.public.windowsxp.video (More info?)

Do you have the necessary codecs installed to play this
file ??
>-----Original Message-----
>this makes no sense on my computer w/ windows 2000 this
>video plays no problem on the comp w/ xp I get this area
>how is that possible... the address is obviously right...
>
>"File Open" Error Message Using Windows Media Player
>View products that this article applies to.
>This article was previously published under Q234292
>SYMPTOMS
>When you type the name of a file to play with Windows
>Media Player, you may receive one or more of the
>following error messages:
>
>Cannot open file (Error=80040216)
>
>
>Cannot open 'http://Servername/Path/Filename.asf'.
Please
>verify that the path and filename are correct and try
>again.(Error=80070002)
>
>
>Cannot open '\\Server\Directory\Filename'. Please verify
>that the path and filename are correct and try again.
>(Error=80070035)
>
>
>Cannot open '\\Server\Filename.' Please verify that the
>path and filename are correct and try again.
>(Error=80070043)
>
>
>Cannot open 'protocol://server/directory/filename'.
>Please verify that the path and filename are correct and
>try again. (Error=80070005)
>
>
>The specified path is invalid (Error=800700A1)
>
>
>The server or proxy was not found (Error=800C0005)
>
>
>The protocol is not known and no pluggable protocols
have
>been entered that match. (Error=800C000D)
>
>
>The specified stream type is not recognized.
>(Error=C00D07E2)
>
>
>The system cannot find the file specified.
>(Error=C00D001A)
>
>
>You do not have access to the location or file. (Error
>80070005)
>CAUSE
>Windows Media Player cannot find the specified file
name.
>Most likely the name has been misspelled, or the path to
>the file is incorrect. There are many different ways to
>create a file path; the method used depends on how you
>are trying to access the multimedia content. Below are
>examples of the correct syntax for common methods used
to
>gain access to multimedia files.
>MORE INFORMATION
>To Play a Multimedia File Located on Your Computer
>DriveLetter:\DirectoryName\FileName
>
>DriveLetter is the letter associated with the disk where
>the multimedia file is located (usually C:\). Directory
>is any folder in which the multimedia file resides.
>Please note that backslashes are used between each
>directory name and the colon following the DriveLetter.
>Filename is the name of the multimedia file. DriveName
>and FileName are required parts of the path.
>DirectoryName is optional, depending on where the
>multimedia content is stored.
>To Play a Multimedia File Located on the World Wide Web
>Protocol://DomainName/DirectoryName/FileName
>
>Protocol is a set of formats and procedures that enable
>computers to exchange information. Protocols used by
>Windows Media Player include HTTP (Hypertext Transfer
>Protocol) and MMS (Microsoft Media Server protocol).
>DirectoryName is optional, depending on where the
>multimedia files are located on the Web site. FileName
is
>the name of the multimedia file. Please note that the
>protocol is followed by a colon and two forward slashes,
>and a forward slash is used between each folder name as
>well as the file name. Protocol, DomainName and FileName
>are all required parts of the path. DirectoryName is
>optional, depending on where the multimedia content is
>stored.
>To Play a Multimedia File Located on a Local Area Network
>\\ServerName\ShareName\FileName
>
>ServerName is the name of the computer on the Local Area
>Network where the multimedia file is located. ShareName
>is the shared folder, located on the server, in which
the
>multimedia file resides. FileName is the name of the
>multimedia file. Please note that two backslashes
precede
>the ServerName and single backslashes appear between
each
>folder name as well as the file name. ServerName,
>ShareName and FileName are all required parts of the
>path.
>To Play a Multimedia File Located on a Network, Using a
>Protocol
>Protocol://ServerName/ShareName/FileName
>
>Protocol is a set of formats and procedures that enable
>computers to exchange information. Protocols used by
>Windows Media Player include HTTP (Hypertext Transfer
>Protocol) and MMS (Microsoft Media Server protocol).
>ServerName is the name of the computer on the network on
>which the multimedia file is located. ShareName is the
>name of the shared folder, located on the server, in
>which the multimedia file resides. FileName is the name
>of the multimedia file. Please note that the protocol is
>followed by a colon and two forward slashes, and a
>forward slash is used between each folder name as well
as
>the file name. Protocol, ServerName, ShareName, and
>FileName are all required parts of the path.
>Resolution
>Ensure that file name is not misspelled and the path to
>the file is correct and try again. If you received the
>error message by clicking a link on a Web page, contact
>the content provider for an updated link.
>
>Note that the error message can also occur if you are
>playing an .asx file and the .asx file refers to a path
>that does not exist (possibly because of reorganized
>content on the host site). The path to the .asx file is
>correct; the problem is that a path embedded inside
>the .asx file is no longer correct. Retyping the path to
>the .asx file does not resolve this issue.
>The information in this article applies to:
>Microsoft Windows Media Player 9 Series for Windows XP
>Microsoft Windows Media Player 9 Series for Windows 2000
>Microsoft Windows Media Player 9 Series for Windows
>Millennium Edition
>Microsoft Windows Media Player 9 Series for Windows 98
>Second Edition
>Microsoft Windows Media Player for Windows XP Home
Edition
>Microsoft Windows Media Player for Windows XP
Professional
>Microsoft Windows Media Player 7.1
>Microsoft Windows Media Player 7
>Microsoft Windows Media Player 6.4
>Microsoft Windows Media Player 6.1
>Microsoft Windows Media Player 6.0
>Last Reviewed: 9/15/2003 (4.0)
>Keywords: kberrmsg kbprb kbProd2Web KB234292
>
>
>
>
>
> Contact Us
>
>
>© 2004 Microsoft Corporation. All rights reserved.
Terms
>of use Security & Privacy Accessibility
>.
>