When I used to plug in my USB, autoplay would open but now it doesnt and since there is no device listing, I can't change the settings for it. I tried the "net start shellhwdetection" thing but it says "denied error 5" what do i do to make autoplay work for all my devices again? I loaned my laptop to someone major mistake — when I got it back I noticed in the autoplay defaults selections I now have a new item — the guys name and ipod.
I see no way to delete this from my list of default choices. Do you have a solution? Click here to cancel reply. Notify me of followup comments via e-mail. Subscribe without commenting E-Mail:. Want to have your AD seen here? What Next? Leave a comment Subscribe to Watching The Net. Is there an answer to this dilemma?
Ben Clarkson It seems that no third party utility exist to change Autoplay options other than defaults in Vista. He then inserts an audio CD. In such a case, interrupting the music that's currently playing is probably not what the user expects. For non-volume devices, let's assume that the user has indicated through the user interface that Application A is to handle video camera events. But for some reason the user prefers Application B for video editing.
He opens Application B and begins editing some previously acquired video, then decides to add some newly acquired content to the video being edited. He invokes Application B's import function and is prompted to turn on the video camera to acquire the latest video content from the camera.
Usually this would trigger the launch of Application A, the user's preferred application for video camera events. Fortunately, Application B has cancelled Autoplay processing of video camera events while the user is editing video content. In this case, the cancellation of Autoplay processing by Application B has created a better user experience.
The purpose of Autoplay is not to provide a reaction to every single hardware event, but rather to help the user accomplish specific tasks related to hardware events of interest. When the software reaction would be disruptive to the current flow of work, or just plain annoying, Autoplay cancellation can be invoked. Volume and non-volume Autoplay are cancelled in different ways. Furthermore, volume events can be cancelled using one of two methods depending on whether the application is in the foreground.
Each one of these cases is explained next. Volume Autoplay Cancellation Since its first incarnation, Autoplay always provided a cancellation mechanism. If the application wants to cancel Autoplay only when it's in the foreground, the application can listen to the QueryCancelAutoplay message. The component will be called whenever an event generates an Autoplay action. The code that is shown is extracted from Sample 3.
See Figure 13 for the possible values defined in shobjidl. An application returns a similar bitmask indicating which Autoplay content types are not to be handled in response to this event.
The values for these flags begin at two for backward compatibility reasons. Prior to Windows XP, applications were required to return one if they wanted to cancel Autoplay.
Sample 3 contains code to determine if the application is running on Windows XP or higher. The IQueryCancelAutoplay interface shown here is also defined in shobjidl. When applicable, the label and serial number of the media is provided to help the application decide if Autoplay should be canceled. Obviously, this information is not available for blank CDs. Using the IQueryCancelAutoplay interface in this way can be especially useful to cancel Autoplay for the second or subsequent CD of a multiple CD setup program or game.
As a side note, the QueryCancelAutoplay message cancellation mechanism can also be used for this purpose, since these applications are most often in the foreground when the user is required to insert the next CD. If a failure code is returned, it is ignored and treated as if the application allows Autoplay. It is important to note that all applications are granted a three-second window in which to cancel Autoplay. Any cancellation query response received after this three-second period is ignored and Autoplay proceeds.
This is necessary because Autoplay loses much of its value when the period between the triggering hardware event and the software response is too long. Usability studies have demonstrated that users often try to launch an application manually when the period between the media insertion and the Autoplay action extends beyond five to seven seconds. Unfortunately, the time delay due to hardware is already quite long on fast CD drives.
Ironically, the faster the CD drive, the longer it takes to bring it up to its operating speed. This does not leave much time to query the applications for cancellation requests. Therefore, applications should register for cancellation only when appropriate and return promptly from the AllowAutoplay call. For backward compatibility, the Windows message mechanism is always used before the IQueryCancelAutoplay mechanism. Refer to Sample 3 for a typical implementation of this mechanism. Non-volume Autoplay Cancellation Non-volume Autoplay cancellation is similar to the volume Autoplay cancellation mechanism for non-foreground applications.
IHWEventHandler interface is defined in shobjidl. For the ROT's Register method call to succeed with this flag, the component being registered must have the correct security settings. See the section Autoplay V2 Registration Mechanism earlier in this article for information on how to register the AppID information for a component.
In contrast to when the interface is used to handle an event, the Initialize method will not be called before HandleEvent when the interface is used for event cancellation. As with volume Autoplay cancellation, Windows allows only three seconds for applications to return from the HandleEvent call. A typical implementation of this cancel mechanism is provided in Sample 2. Autoplay Diagnostic Tools Two tools for download have been provided with the samples accompanying this article.
The first one, APDiag. The tool performs two tasks. First it sets the following registry value:. Then the APDiag. This tool is mostly useful for diagnosing non-volume Autoplay problems, but it can also be used in some cases to trace volume Autoplay operations.
This tool performs an Autoplay post-mortem diagnosis of the last Autoplay attempt for a specific drive. It is meant to be used for the diagnosis of volume Autoplay events. As its name implies, it should be run after a volume Autoplay scenario has been carried out.
Conclusion Autoplay provides users and software with rich mechanisms for interacting with hardware events on the computer. When used properly by applications, Autoplay's open registration mechanism can significantly enhance the user experience with the many devices that connect to the modern PC.
He likes COM and the opening curly bracket on the line following the 'if' statement. When AutoPlay is presented with a mixed content medium, it requires user input before it can take action. In this case, the user is presented with a dialog box containing a filtered list of all appropriate registered applications available for the content types present on the media.
The user can choose one of these applications to AutoPlay that particular content type, while the rest remain untouched. As the composition of mixed content media varies with each individual disc, there is no option to save this choice as a default. A dialog box similar to the following is displayed when any supported media not yet assigned a default AutoPlay action is presented to the system. A user can also save a choice as the default action for this medium by clicking the Always do the selected action box.
Once this choice is made, the dialog is not shown again. However, in Windows XP Service Pack 1 SP1 , if a new application that can handle a particular media type is added to the computer, the dialog is once again presented to the user, giving them the opportunity to select the new application as the default AutoPlay action. Applications can also set themselves as the default selection when they are installed. Windows XP SP1 also adds a feature that retains the user's choice of AutoPlay action if they do not click the Always do the selected action box.
If a user chooses an AutoPlay action for a single instance, the next time that dialog is presented for that media type, the same action is the default selection. For an application to be included in the list of possible actions, it must be registered with AutoPlay. It should be under Devices With Removable Storage, but it does not appear. Is there a way to make it show up? How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. This site in other languages x.
0コメント