Sign in with
Sign up | Sign in
Your question

autorun.inf

Last response: in Windows XP
Share
August 18, 2005 10:59:56 AM

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

Running XP Media Center Edition, Version 2002, SP 2

I created several CD on our old computer running Win 98SE using
autorun.inf file to automatically open an *.html page containing an
index of the contains of the CD(s). The autorun.inf on those CDs don't
work on any of our XP computers. The CDs are recognized easily by these
computers running XP but won't open the autorun.inf files.

Nowww do note autorun CDs that come with programs, that we buy, run with
no trouble which means the autorun option is definitely on. I have even
copied the autorun.inf files from program/purchased CDs and changed the
file to open name to the *.html file on the CDs and still they won't
work. Again do note these CDs with autorun.inf that I created easily run
on all our Win98 computers.

Here are samples of text I've tried:

[autorun]
open = start photoalbum_2a.html

[autorun]
open = photoalbum_2a.html

[autorun]
open = start E:\photoalbum_2a.html

[autorun]
run = start photoalbum_2a.html

[autorun]
run = start E:\photoalbum_2a.html

Yes, I'm doing all this in a text editor. Yes, the file name is autorun.inf.

What am I doing wrong?

TIA

--- Susan

More about : autorun inf

Anonymous
August 18, 2005 12:43:50 PM

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

"Susan" <SGTaylor1@NOSPAMworldnet.com> wrote in message
news:MlWMe.109940$5N3.55008@bgtnsc05-news.ops.worldnet.att.net...
> Running XP Media Center Edition, Version 2002, SP 2
>
> I created several CD on our old computer running Win 98SE using
> autorun.inf file to automatically open an *.html page containing an index
> of the contains of the CD(s). The autorun.inf on those CDs don't work on
> any of our XP computers. The CDs are recognized easily by these computers
> running XP but won't open the autorun.inf files.
>
> Nowww do note autorun CDs that come with programs, that we buy, run with
> no trouble which means the autorun option is definitely on. I have even
> copied the autorun.inf files from program/purchased CDs and changed the
> file to open name to the *.html file on the CDs and still they won't work.
> Again do note these CDs with autorun.inf that I created easily run on all
> our Win98 computers.
>
> Here are samples of text I've tried:
>
> [autorun]
> open = start photoalbum_2a.html
>
> [autorun]
> open = photoalbum_2a.html
>
> [autorun]
> open = start E:\photoalbum_2a.html
>
> [autorun]
> run = start photoalbum_2a.html
>
> [autorun]
> run = start E:\photoalbum_2a.html
>
> Yes, I'm doing all this in a text editor. Yes, the file name is
> autorun.inf.
>
> What am I doing wrong?
>
> TIA
>
Try this:
[autorun]
open = start iexplore photoalbum_2a.html
August 18, 2005 12:43:51 PM

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

Mark Weinreb wrote:

> "Susan" <SGTaylor1@NOSPAMworldnet.com> wrote in message
> news:MlWMe.109940$5N3.55008@bgtnsc05-news.ops.worldnet.att.net...
>
>>Running XP Media Center Edition, Version 2002, SP 2
>>
>>I created several CD on our old computer running Win 98SE using
>>autorun.inf file to automatically open an *.html page containing an index
>>of the contains of the CD(s). The autorun.inf on those CDs don't work on
>>any of our XP computers. The CDs are recognized easily by these computers
>>running XP but won't open the autorun.inf files.
>>
>>Nowww do note autorun CDs that come with programs, that we buy, run with
>>no trouble which means the autorun option is definitely on. I have even
>>copied the autorun.inf files from program/purchased CDs and changed the
>>file to open name to the *.html file on the CDs and still they won't work.
>>Again do note these CDs with autorun.inf that I created easily run on all
>>our Win98 computers.
>>
>>Here are samples of text I've tried:
>>
>>[autorun]
>>open = start photoalbum_2a.html
>>
>>[autorun]
>>open = photoalbum_2a.html
>>
>>[autorun]
>>open = start E:\photoalbum_2a.html
>>
>>[autorun]
>>run = start photoalbum_2a.html
>>
>>[autorun]
>>run = start E:\photoalbum_2a.html
>>
>>Yes, I'm doing all this in a text editor. Yes, the file name is
>>autorun.inf.
>>
>>What am I doing wrong?
>>
>>TIA
>>
>
> Try this:
> [autorun]
> open = start iexplore photoalbum_2a.html
>

Thanks, Mark, but that didn't work either. I finally "Google"
autorun.inf and came up with a freebie autorun.inf editor:

http://downloads-zdnet.com.com/Autorun-Inf-Editor/3000-...

This didn't work at first until I read the help file - you know, when
all else fails I read the instructions. <g> In the files it expanded to
was one called opener.exe. I had to add this program to the coding and
also add the program (Opener.exe) to the CD. Now it opens the *.html
file in the browser of choice with no problems. The coding is:

[autorun]
open=opener.exe photoalbum_2a.html

Gee, the help file said the commands for autorun.inf would not open a
document or webpage without the opener program onboard. It insinuated
only programs *.exe could be opened with the regular commands.
Strangeeeee... for documents, *.html, webpages, etc... can all be opened
with the open command on our Win98 computers.

Thanks again.

--- Susan
Related resources
Anonymous
August 18, 2005 1:34:53 PM

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

> I created several CD on our old computer running Win 98SE using
> autorun.inf file to automatically open an *.html page containing an index
> of the contains of the CD(s). The autorun.inf on those CDs don't work on
> any of our XP computers. The CDs are recognized easily by these computers
> running XP but won't open the autorun.inf files.

I am shocked that you actually had this work in Windows 98SE. The open
command in an autorun.inf file MUST be a executable file (.EXE), and was
under the impression that that has always been the case. Not withstanding
the fact that it worked in W98SE, you need to get a third-part executable
that will open .html files in XP. Search Google for autorun.inf.

--
..__
(__
__ )teve www.steve.shattuck.net steve@shattuck.net
Anonymous
August 18, 2005 5:51:35 PM

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

"Steve Shattuck" <steve@shattuck.net> wrote:

> I am shocked that you actually had this work in Windows 98SE. The
> open command in an autorun.inf file MUST be a executable file (.EXE),
> and was under the impression that that has always been the case.

Under Win98/Win98SE, "start" is an *external* command in contrast to
WinNT/Win2K/WinXP as already posted in this thread. Therefore, this
command refers to "start.exe", existing in the search path of Win98.
Under NT based systems, programs like "shelexec.exe" may be used in
order to launch any document on CD via its associated application.

--
d-d
Anonymous
August 18, 2005 10:46:53 PM

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

Start is an external program in 9x and an internal command in NT systems. Therefore it is not available for use in Autorun.inf. There are different rules for 98 and NT. 98 is compatable on NT (your problem is using a program that doesn't exist) plus it can do more (it doesn't need to use Start - Start functionality is built in).

So,

Use (and you may need to specify a path to the html file) to access the internal commands

cmd /c start photoalbum_2a.html

or just use one of the newer commands

Autorun.inf Commands

--------------------------------------------------------------------------------

This topic is a reference for the commands that can be used in an Autorun.inf file.

a.. [AutoRun] Commands
b.. [DeviceInstall] Commands
[AutoRun] Commands
a.. icon
b.. label
c.. open
d.. shellexecute
e.. shell
f.. shell\verb
icon
The icon command specifies an icon which represents the AutoRun-enabled drive in the Microsoft® Windows® user interface.

icon=iconfilename[,index]Parameters
a.. iconfilename
Name of an .ico, .bmp, .exe, or .dll file containing the icon information. If a file contains more than one icon, you must also specify zero-based index of the icon.

Remarks
The icon, together with the label, represents the AutoRun-enabled drive in the Windows user interface. For instance, in Windows Explorer, the drive is represented by this icon instead of the standard drive icon. The icon's file must be in the same directory as the file specified by the open command.

The following example specifies the second icon in the MyProg.exe file.

icon=MyProg.exe,1label
The label command specifies a text label which represents the AutoRun-enabled drive in the Windows user interface.

label=LabelTextParameters
a.. LabelText
A text string containing the label. It can contain spaces.

Remarks
The label, together with an icon, represents the AutoRun-enabled drive in the Windows user interface.

The following example specifies "My Drive Label" as the drive's label.

label=My Drive Labelopen
The open command specifies the path and file name of the application that AutoRun launches when a user inserts a disc in the drive.

open=[exepath\]exefile [param1 [param2] ...] Parameters
a.. exefile
Fully qualified path of an executable file that runs when the CD is inserted. If only a file name is specified, it must be in drive's root directory. To locate the file in a subdirectory, you must specify a path. You can also include one or more command-line parameters to pass to the startup application.

Remarks
For more information about startup applications, see Tips for Writing AutoRun Startup Applications.

shellexecute
Version 5.0. The shellexecute command specifies an application or data file that AutoRun will use to call ShellExecuteEx.

shellexecute=[filepath\]filename[param1, [param2]...] Parameters
a.. filepath
A string that contains the fully qualified path of the directory that contains the data or executable file. If no path is specified, the file must be in the drive's root directory.

b.. filename
A string that contains the file's name. If it is an executable file, it is launched. If it is a data file, it must be a member of a file class. ShellExecuteEx launches the default command associated with the file class.

c.. paramx
Contains any additional parameters that should be passed to ShellExecuteEx.

Remarks
This command is similar to open, but it allows you to use file association information to run the application.

shell
The shell command specifies a default command for the drive's shortcut menu.

shell=verbParameters
a.. verb
The verb that corresponds to the command. The verb and its associated command must be defined in the Autorun.inf file with a shell\verb command.

Remarks
When a user right-clicks the drive icon, a shortcut menu appears. If an Autorun.inf file is present, the default shortcut menu command is taken from it. This command also executes when the user double-clicks the drive's icon.

To specify the default shortcut menu command, first define its verb, command string, and menu text with shell\verb. Then use shell to make it the default shortcut menu command. Otherwise, the default menu item text will be "AutoPlay", which launches the application specified by the open command.

shell\verb
The shell\verb command adds a custom command to the drive's shortcut menu.

shell\verb\command=Filename.exe
shell\verb=MenuTextParameters
a.. verb
The command's verb. The shell\verb\command command associates the verb with an executable file. Verbs must not contain embedded spaces. By default, verb is the text that is displayed in the shortcut menu.

b.. Filename.exe
The path and file name of the application that performs the command.

c.. MenuText
This parameter specifies the text that is displayed in the shortcut menu. If it is omitted, verb is displayed. MenuText can be mixed-case and can contain spaces. You can set a shortcut key for the menu item by putting an ampersand (&) in front of the letter.

Remarks
When a user right-clicks the drive icon, a shortcut menu appears. Adding shell/verb commands to the drive's Autorun.inf file allows you to add commands to this shortcut menu.

There are two parts to this command, which must be on separate lines. The first part is shell/verb/command. It is required. It associates a string, called a verb, with the application to launch when the command runs. The second part is the shell/verb command. It is optional. You can include it to specify the text that displays in the shortcut menu.

To specify a default shortcut menu command, define the verb with shell/verb, and make it the default command with shell.

The following sample Autorun.inf fragment associates the readit verb with the command string "Notepad abc\readme.txt". The menu text is "Read Me", and 'M' is defined as the item's shortcut key. When the user selects this command, the drive's abc\readme.txt file opens with Microsoft Notepad.

shell\readit\command=notepad abc\readme.txt
shell\readit=Read &Me[DeviceInstall] Commands
a.. DriverPath
DriverPath
The DriverPath command specifies a directory to search recursively for driver files. This command is used during a driver installation and is not part of an AutoRun operation. The [DeviceInstall] section is only supported under Windows XP.

[DeviceInstall]
DriverPath=directorypathParameters
a.. directorypath
A path to a directory that Windows searches for driver files, along with all of its subdirectories.

Remarks
Do not use drive letters in directorypath as they change from one computer to the next.

To search multiple directories, add a DriverPath command for each directory as in this example.

[DeviceInstall]
DriverPath=drivers\video
DriverPath=drivers\audioTo indicate that the media contains no driver files so that it is not searched at all, include a [DeviceInstall] section in Autorun.inf that contains no DriverPath commands.


--------------------------------------------------------------------------------

© 2003 Microsoft Corporation. All rights reserved.


--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.htm...
=================================================
"Susan" <SGTaylor1@NOSPAMworldnet.com> wrote in message news:8vXMe.110111$5N3.71125@bgtnsc05-news.ops.worldnet.att.net...
> Mark Weinreb wrote:
>
>> "Susan" <SGTaylor1@NOSPAMworldnet.com> wrote in message
>> news:MlWMe.109940$5N3.55008@bgtnsc05-news.ops.worldnet.att.net...
>>
>>>Running XP Media Center Edition, Version 2002, SP 2
>>>
>>>I created several CD on our old computer running Win 98SE using
>>>autorun.inf file to automatically open an *.html page containing an index
>>>of the contains of the CD(s). The autorun.inf on those CDs don't work on
>>>any of our XP computers. The CDs are recognized easily by these computers
>>>running XP but won't open the autorun.inf files.
>>>
>>>Nowww do note autorun CDs that come with programs, that we buy, run with
>>>no trouble which means the autorun option is definitely on. I have even
>>>copied the autorun.inf files from program/purchased CDs and changed the
>>>file to open name to the *.html file on the CDs and still they won't work.
>>>Again do note these CDs with autorun.inf that I created easily run on all
>>>our Win98 computers.
>>>
>>>Here are samples of text I've tried:
>>>
>>>[autorun]
>>>open = start photoalbum_2a.html
>>>
>>>[autorun]
>>>open = photoalbum_2a.html
>>>
>>>[autorun]
>>>open = start E:\photoalbum_2a.html
>>>
>>>[autorun]
>>>run = start photoalbum_2a.html
>>>
>>>[autorun]
>>>run = start E:\photoalbum_2a.html
>>>
>>>Yes, I'm doing all this in a text editor. Yes, the file name is
>>>autorun.inf.
>>>
>>>What am I doing wrong?
>>>
>>>TIA
>>>
>>
>> Try this:
>> [autorun]
>> open = start iexplore photoalbum_2a.html
>>
>
> Thanks, Mark, but that didn't work either. I finally "Google"
> autorun.inf and came up with a freebie autorun.inf editor:
>
> http://downloads-zdnet.com.com/Autorun-Inf-Editor/3000-...
>
> This didn't work at first until I read the help file - you know, when
> all else fails I read the instructions. <g> In the files it expanded to
> was one called opener.exe. I had to add this program to the coding and
> also add the program (Opener.exe) to the CD. Now it opens the *.html
> file in the browser of choice with no problems. The coding is:
>
> [autorun]
> open=opener.exe photoalbum_2a.html
>
> Gee, the help file said the commands for autorun.inf would not open a
> document or webpage without the opener program onboard. It insinuated
> only programs *.exe could be opened with the regular commands.
> Strangeeeee... for documents, *.html, webpages, etc... can all be opened
> with the open command on our Win98 computers.
>
> Thanks again.
>
> --- Susan
>
>
August 18, 2005 10:46:54 PM

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

David,

Thank you!!! It works like a champ on XP without the need of putting a
utility program on the CD, using your coding:

[autorun]
open = cmd /c start photoalbum_2a.html

However, doesn't work on our 9X computers. :(  Soooo it appears I'll
have to add the opener.exe program to our CDs and code the autorun.inf
with "opener.exe" to make sure the CDs will work on both 9X and XP:

[autorun]
open=opener.exe photoalbum_2a.html

Nowwwww I have a 2nd grade question to ask about external vs internal.
When you say:

> Start is an external program in 9x and an internal command in NT systems.

Does this mean the "start" program was in the system files on the CD (a
CD being an external source) when used in 9X and now is built into the
OS XP somewhere?

[autorun]
open = start photoalbum_2a.html

called up "start" on the CD in 9X and

[autorun]
open = cmd /c start photoalbum_2a.html

calls up "start" on the hard drive in XP? I warned you this was a 2nd
grade now maybe a kindergarten question.

Thanks again.

--- Susan


David Candy wrote:
> Start is an external program in 9x and an internal command in NT systems. Therefore it is not available for use in Autorun.inf. There are different rules for 98 and NT. 98 is compatable on NT (your problem is using a program that doesn't exist) plus it can do more (it doesn't need to use Start - Start functionality is built in).
>
> So,
>
> Use (and you may need to specify a path to the html file) to access the internal commands
>
> cmd /c start photoalbum_2a.html
>
> or just use one of the newer commands
>
> Autorun.inf Commands
>
> --------------------------------------------------------------------------------
>
> This topic is a reference for the commands that can be used in an Autorun.inf file.
>
> a.. [AutoRun] Commands
> b.. [DeviceInstall] Commands
> [AutoRun] Commands
> a.. icon
> b.. label
> c.. open
> d.. shellexecute
> e.. shell
> f.. shell\verb
> icon
> The icon command specifies an icon which represents the AutoRun-enabled drive in the Microsoft® Windows® user interface.
>
> icon=iconfilename[,index]Parameters
> a.. iconfilename
> Name of an .ico, .bmp, .exe, or .dll file containing the icon information. If a file contains more than one icon, you must also specify zero-based index of the icon.
>
> Remarks
> The icon, together with the label, represents the AutoRun-enabled drive in the Windows user interface. For instance, in Windows Explorer, the drive is represented by this icon instead of the standard drive icon. The icon's file must be in the same directory as the file specified by the open command.
>
> The following example specifies the second icon in the MyProg.exe file.
>
> icon=MyProg.exe,1label
> The label command specifies a text label which represents the AutoRun-enabled drive in the Windows user interface.
>
> label=LabelTextParameters
> a.. LabelText
> A text string containing the label. It can contain spaces.
>
> Remarks
> The label, together with an icon, represents the AutoRun-enabled drive in the Windows user interface.
>
> The following example specifies "My Drive Label" as the drive's label.
>
> label=My Drive Labelopen
> The open command specifies the path and file name of the application that AutoRun launches when a user inserts a disc in the drive.
>
> open=[exepath\]exefile [param1 [param2] ...] Parameters
> a.. exefile
> Fully qualified path of an executable file that runs when the CD is inserted. If only a file name is specified, it must be in drive's root directory. To locate the file in a subdirectory, you must specify a path. You can also include one or more command-line parameters to pass to the startup application.
>
> Remarks
> For more information about startup applications, see Tips for Writing AutoRun Startup Applications.
>
> shellexecute
> Version 5.0. The shellexecute command specifies an application or data file that AutoRun will use to call ShellExecuteEx.
>
> shellexecute=[filepath\]filename[param1, [param2]...] Parameters
> a.. filepath
> A string that contains the fully qualified path of the directory that contains the data or executable file. If no path is specified, the file must be in the drive's root directory.
>
> b.. filename
> A string that contains the file's name. If it is an executable file, it is launched. If it is a data file, it must be a member of a file class. ShellExecuteEx launches the default command associated with the file class.
>
> c.. paramx
> Contains any additional parameters that should be passed to ShellExecuteEx.
>
> Remarks
> This command is similar to open, but it allows you to use file association information to run the application.
>
> shell
> The shell command specifies a default command for the drive's shortcut menu.
>
> shell=verbParameters
> a.. verb
> The verb that corresponds to the command. The verb and its associated command must be defined in the Autorun.inf file with a shell\verb command.
>
> Remarks
> When a user right-clicks the drive icon, a shortcut menu appears. If an Autorun.inf file is present, the default shortcut menu command is taken from it. This command also executes when the user double-clicks the drive's icon.
>
> To specify the default shortcut menu command, first define its verb, command string, and menu text with shell\verb. Then use shell to make it the default shortcut menu command. Otherwise, the default menu item text will be "AutoPlay", which launches the application specified by the open command.
>
> shell\verb
> The shell\verb command adds a custom command to the drive's shortcut menu.
>
> shell\verb\command=Filename.exe
> shell\verb=MenuTextParameters
> a.. verb
> The command's verb. The shell\verb\command command associates the verb with an executable file. Verbs must not contain embedded spaces. By default, verb is the text that is displayed in the shortcut menu.
>
> b.. Filename.exe
> The path and file name of the application that performs the command.
>
> c.. MenuText
> This parameter specifies the text that is displayed in the shortcut menu. If it is omitted, verb is displayed. MenuText can be mixed-case and can contain spaces. You can set a shortcut key for the menu item by putting an ampersand (&) in front of the letter.
>
> Remarks
> When a user right-clicks the drive icon, a shortcut menu appears. Adding shell/verb commands to the drive's Autorun.inf file allows you to add commands to this shortcut menu.
>
> There are two parts to this command, which must be on separate lines. The first part is shell/verb/command. It is required. It associates a string, called a verb, with the application to launch when the command runs. The second part is the shell/verb command. It is optional. You can include it to specify the text that displays in the shortcut menu.
>
> To specify a default shortcut menu command, define the verb with shell/verb, and make it the default command with shell.
>
> The following sample Autorun.inf fragment associates the readit verb with the command string "Notepad abc\readme.txt". The menu text is "Read Me", and 'M' is defined as the item's shortcut key. When the user selects this command, the drive's abc\readme.txt file opens with Microsoft Notepad.
>
> shell\readit\command=notepad abc\readme.txt
> shell\readit=Read &Me[DeviceInstall] Commands
> a.. DriverPath
> DriverPath
> The DriverPath command specifies a directory to search recursively for driver files. This command is used during a driver installation and is not part of an AutoRun operation. The [DeviceInstall] section is only supported under Windows XP.
>
> [DeviceInstall]
> DriverPath=directorypathParameters
> a.. directorypath
> A path to a directory that Windows searches for driver files, along with all of its subdirectories.
>
> Remarks
> Do not use drive letters in directorypath as they change from one computer to the next.
>
> To search multiple directories, add a DriverPath command for each directory as in this example.
>
> [DeviceInstall]
> DriverPath=drivers\video
> DriverPath=drivers\audioTo indicate that the media contains no driver files so that it is not searched at all, include a [DeviceInstall] section in Autorun.inf that contains no DriverPath commands.
>
>
> --------------------------------------------------------------------------------
>
> © 2003 Microsoft Corporation. All rights reserved.
>
>
August 18, 2005 10:46:54 PM

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

David,

Thank you!!! It works like a champ on XP without the need of putting a
utility program on the CD, using your coding:

[autorun]
open = cmd /c start photoalbum_2a.html

However, doesn't work on our 9X computers. :(  Soooo it appears I'll
have to add the opener.exe program to our CDs and code the autorun.inf
with "opener.exe" to make sure the CDs will autorun on both 9X and XP:

[autorun]
open=opener.exe photoalbum_2a.html

Nowwwww I have a 2nd grade question to ask about external vs internal.
When you say:

> Start is an external program in 9x and an internal command in NT systems.

Does this mean the "start" program was in the system files on the CD (a
CD being an external source) when used in 9X and now is built into the
OS XP somewhere?

[autorun]
open = start photoalbum_2a.html

called up "start" on the CD in 9X and

[autorun]
open = cmd /c start photoalbum_2a.html

calls up "start" on the hard drive in XP? I warned you this was a 2nd
grade now maybe a kindergarten question.

Thanks again.

--- Susan


David Candy wrote:

> Start is an external program in 9x and an internal command in NT systems. Therefore it is not available for use in Autorun.inf. There are different rules for 98 and NT. 98 is compatable on NT (your problem is using a program that doesn't exist) plus it can do more (it doesn't need to use Start - Start functionality is built in).
>
> So,
>
> Use (and you may need to specify a path to the html file) to access the internal commands
>
> cmd /c start photoalbum_2a.html
>
> or just use one of the newer commands
>
> Autorun.inf Commands
>
> --------------------------------------------------------------------------------
>
> This topic is a reference for the commands that can be used in an Autorun.inf file.
>
> a.. [AutoRun] Commands
> b.. [DeviceInstall] Commands
> [AutoRun] Commands
> a.. icon
> b.. label
> c.. open
> d.. shellexecute
> e.. shell
> f.. shell\verb
> icon
> The icon command specifies an icon which represents the AutoRun-enabled drive in the Microsoft® Windows® user interface.
>
> icon=iconfilename[,index]Parameters
> a.. iconfilename
> Name of an .ico, .bmp, .exe, or .dll file containing the icon information. If a file contains more than one icon, you must also specify zero-based index of the icon.
>
> Remarks
> The icon, together with the label, represents the AutoRun-enabled drive in the Windows user interface. For instance, in Windows Explorer, the drive is represented by this icon instead of the standard drive icon. The icon's file must be in the same directory as the file specified by the open command.
>
> The following example specifies the second icon in the MyProg.exe file.
>
> icon=MyProg.exe,1label
> The label command specifies a text label which represents the AutoRun-enabled drive in the Windows user interface.
>
> label=LabelTextParameters
> a.. LabelText
> A text string containing the label. It can contain spaces.
>
> Remarks
> The label, together with an icon, represents the AutoRun-enabled drive in the Windows user interface.
>
> The following example specifies "My Drive Label" as the drive's label.
>
> label=My Drive Labelopen
> The open command specifies the path and file name of the application that AutoRun launches when a user inserts a disc in the drive.
>
> open=[exepath\]exefile [param1 [param2] ...] Parameters
> a.. exefile
> Fully qualified path of an executable file that runs when the CD is inserted. If only a file name is specified, it must be in drive's root directory. To locate the file in a subdirectory, you must specify a path. You can also include one or more command-line parameters to pass to the startup application.
>
> Remarks
> For more information about startup applications, see Tips for Writing AutoRun Startup Applications.
>
> shellexecute
> Version 5.0. The shellexecute command specifies an application or data file that AutoRun will use to call ShellExecuteEx.
>
> shellexecute=[filepath\]filename[param1, [param2]...] Parameters
> a.. filepath
> A string that contains the fully qualified path of the directory that contains the data or executable file. If no path is specified, the file must be in the drive's root directory.
>
> b.. filename
> A string that contains the file's name. If it is an executable file, it is launched. If it is a data file, it must be a member of a file class. ShellExecuteEx launches the default command associated with the file class.
>
> c.. paramx
> Contains any additional parameters that should be passed to ShellExecuteEx.
>
> Remarks
> This command is similar to open, but it allows you to use file association information to run the application.
>
> shell
> The shell command specifies a default command for the drive's shortcut menu.
>
> shell=verbParameters
> a.. verb
> The verb that corresponds to the command. The verb and its associated command must be defined in the Autorun.inf file with a shell\verb command.
>
> Remarks
> When a user right-clicks the drive icon, a shortcut menu appears. If an Autorun.inf file is present, the default shortcut menu command is taken from it. This command also executes when the user double-clicks the drive's icon.
>
> To specify the default shortcut menu command, first define its verb, command string, and menu text with shell\verb. Then use shell to make it the default shortcut menu command. Otherwise, the default menu item text will be "AutoPlay", which launches the application specified by the open command.
>
> shell\verb
> The shell\verb command adds a custom command to the drive's shortcut menu.
>
> shell\verb\command=Filename.exe
> shell\verb=MenuTextParameters
> a.. verb
> The command's verb. The shell\verb\command command associates the verb with an executable file. Verbs must not contain embedded spaces. By default, verb is the text that is displayed in the shortcut menu.
>
> b.. Filename.exe
> The path and file name of the application that performs the command.
>
> c.. MenuText
> This parameter specifies the text that is displayed in the shortcut menu. If it is omitted, verb is displayed. MenuText can be mixed-case and can contain spaces. You can set a shortcut key for the menu item by putting an ampersand (&) in front of the letter.
>
> Remarks
> When a user right-clicks the drive icon, a shortcut menu appears. Adding shell/verb commands to the drive's Autorun.inf file allows you to add commands to this shortcut menu.
>
> There are two parts to this command, which must be on separate lines. The first part is shell/verb/command. It is required. It associates a string, called a verb, with the application to launch when the command runs. The second part is the shell/verb command. It is optional. You can include it to specify the text that displays in the shortcut menu.
>
> To specify a default shortcut menu command, define the verb with shell/verb, and make it the default command with shell.
>
> The following sample Autorun.inf fragment associates the readit verb with the command string "Notepad abc\readme.txt". The menu text is "Read Me", and 'M' is defined as the item's shortcut key. When the user selects this command, the drive's abc\readme.txt file opens with Microsoft Notepad.
>
> shell\readit\command=notepad abc\readme.txt
> shell\readit=Read &Me[DeviceInstall] Commands
> a.. DriverPath
> DriverPath
> The DriverPath command specifies a directory to search recursively for driver files. This command is used during a driver installation and is not part of an AutoRun operation. The [DeviceInstall] section is only supported under Windows XP.
>
> [DeviceInstall]
> DriverPath=directorypathParameters
> a.. directorypath
> A path to a directory that Windows searches for driver files, along with all of its subdirectories.
>
> Remarks
> Do not use drive letters in directorypath as they change from one computer to the next.
>
> To search multiple directories, add a DriverPath command for each directory as in this example.
>
> [DeviceInstall]
> DriverPath=drivers\video
> DriverPath=drivers\audioTo indicate that the media contains no driver files so that it is not searched at all, include a [DeviceInstall] section in Autorun.inf that contains no DriverPath commands.
>
>
> --------------------------------------------------------------------------------
>
> © 2003 Microsoft Corporation. All rights reserved.
>
>
August 18, 2005 10:46:54 PM

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

David,

Thank you!!! It works like a champ on XP without the need of putting a
utility program on the CD, using your coding:

[autorun]
open = cmd /c start photoalbum_2a.html

However, doesn't work on our 9X computers. :(  Soooo it appears I'll
have to add the opener.exe program to our CDs and code the autorun.inf
with "opener.exe" to make sure the CDs will work on both 9X and XP:

[autorun]
open=opener.exe photoalbum_2a.html

Nowwwww I have a 2nd grade question to ask about external vs internal.
When you say:

> Start is an external program in 9x and an internal command in NT systems.

Does this mean the "start" program was in the system files on the CD (a
CD being an external source) when used in 9X and now is built into the
OS XP somewhere?

[autorun]
open = start photoalbum_2a.html

called up "start" on the CD in 9X and

[autorun]
open = cmd /c start photoalbum_2a.html

calls up "start" on the hard drive in XP? I warned you this was a 2nd
grade now maybe a kindergarten question.

Thanks again.

--- Susan


David Candy wrote:
> Start is an external program in 9x and an internal command in NT systems. Therefore it is not available for use in Autorun.inf. There are different rules for 98 and NT. 98 is compatable on NT (your problem is using a program that doesn't exist) plus it can do more (it doesn't need to use Start - Start functionality is built in).
>
> So,
>
> Use (and you may need to specify a path to the html file) to access the internal commands
>
> cmd /c start photoalbum_2a.html
>
> or just use one of the newer commands
>
> Autorun.inf Commands
>
> --------------------------------------------------------------------------------
>
> This topic is a reference for the commands that can be used in an Autorun.inf file.
>
> a.. [AutoRun] Commands
> b.. [DeviceInstall] Commands
> [AutoRun] Commands
> a.. icon
> b.. label
> c.. open
> d.. shellexecute
> e.. shell
> f.. shell\verb
> icon
> The icon command specifies an icon which represents the AutoRun-enabled drive in the Microsoft® Windows® user interface.
>
> icon=iconfilename[,index]Parameters
> a.. iconfilename
> Name of an .ico, .bmp, .exe, or .dll file containing the icon information. If a file contains more than one icon, you must also specify zero-based index of the icon.
>
> Remarks
> The icon, together with the label, represents the AutoRun-enabled drive in the Windows user interface. For instance, in Windows Explorer, the drive is represented by this icon instead of the standard drive icon. The icon's file must be in the same directory as the file specified by the open command.
>
> The following example specifies the second icon in the MyProg.exe file.
>
> icon=MyProg.exe,1label
> The label command specifies a text label which represents the AutoRun-enabled drive in the Windows user interface.
>
> label=LabelTextParameters
> a.. LabelText
> A text string containing the label. It can contain spaces.
>
> Remarks
> The label, together with an icon, represents the AutoRun-enabled drive in the Windows user interface.
>
> The following example specifies "My Drive Label" as the drive's label.
>
> label=My Drive Labelopen
> The open command specifies the path and file name of the application that AutoRun launches when a user inserts a disc in the drive.
>
> open=[exepath\]exefile [param1 [param2] ...] Parameters
> a.. exefile
> Fully qualified path of an executable file that runs when the CD is inserted. If only a file name is specified, it must be in drive's root directory. To locate the file in a subdirectory, you must specify a path. You can also include one or more command-line parameters to pass to the startup application.
>
> Remarks
> For more information about startup applications, see Tips for Writing AutoRun Startup Applications.
>
> shellexecute
> Version 5.0. The shellexecute command specifies an application or data file that AutoRun will use to call ShellExecuteEx.
>
> shellexecute=[filepath\]filename[param1, [param2]...] Parameters
> a.. filepath
> A string that contains the fully qualified path of the directory that contains the data or executable file. If no path is specified, the file must be in the drive's root directory.
>
> b.. filename
> A string that contains the file's name. If it is an executable file, it is launched. If it is a data file, it must be a member of a file class. ShellExecuteEx launches the default command associated with the file class.
>
> c.. paramx
> Contains any additional parameters that should be passed to ShellExecuteEx.
>
> Remarks
> This command is similar to open, but it allows you to use file association information to run the application.
>
> shell
> The shell command specifies a default command for the drive's shortcut menu.
>
> shell=verbParameters
> a.. verb
> The verb that corresponds to the command. The verb and its associated command must be defined in the Autorun.inf file with a shell\verb command.
>
> Remarks
> When a user right-clicks the drive icon, a shortcut menu appears. If an Autorun.inf file is present, the default shortcut menu command is taken from it. This command also executes when the user double-clicks the drive's icon.
>
> To specify the default shortcut menu command, first define its verb, command string, and menu text with shell\verb. Then use shell to make it the default shortcut menu command. Otherwise, the default menu item text will be "AutoPlay", which launches the application specified by the open command.
>
> shell\verb
> The shell\verb command adds a custom command to the drive's shortcut menu.
>
> shell\verb\command=Filename.exe
> shell\verb=MenuTextParameters
> a.. verb
> The command's verb. The shell\verb\command command associates the verb with an executable file. Verbs must not contain embedded spaces. By default, verb is the text that is displayed in the shortcut menu.
>
> b.. Filename.exe
> The path and file name of the application that performs the command.
>
> c.. MenuText
> This parameter specifies the text that is displayed in the shortcut menu. If it is omitted, verb is displayed. MenuText can be mixed-case and can contain spaces. You can set a shortcut key for the menu item by putting an ampersand (&) in front of the letter.
>
> Remarks
> When a user right-clicks the drive icon, a shortcut menu appears. Adding shell/verb commands to the drive's Autorun.inf file allows you to add commands to this shortcut menu.
>
> There are two parts to this command, which must be on separate lines. The first part is shell/verb/command. It is required. It associates a string, called a verb, with the application to launch when the command runs. The second part is the shell/verb command. It is optional. You can include it to specify the text that displays in the shortcut menu.
>
> To specify a default shortcut menu command, define the verb with shell/verb, and make it the default command with shell.
>
> The following sample Autorun.inf fragment associates the readit verb with the command string "Notepad abc\readme.txt". The menu text is "Read Me", and 'M' is defined as the item's shortcut key. When the user selects this command, the drive's abc\readme.txt file opens with Microsoft Notepad.
>
> shell\readit\command=notepad abc\readme.txt
> shell\readit=Read &Me[DeviceInstall] Commands
> a.. DriverPath
> DriverPath
> The DriverPath command specifies a directory to search recursively for driver files. This command is used during a driver installation and is not part of an AutoRun operation. The [DeviceInstall] section is only supported under Windows XP.
>
> [DeviceInstall]
> DriverPath=directorypathParameters
> a.. directorypath
> A path to a directory that Windows searches for driver files, along with all of its subdirectories.
>
> Remarks
> Do not use drive letters in directorypath as they change from one computer to the next.
>
> To search multiple directories, add a DriverPath command for each directory as in this example.
>
> [DeviceInstall]
> DriverPath=drivers\video
> DriverPath=drivers\audioTo indicate that the media contains no driver files so that it is not searched at all, include a [DeviceInstall] section in Autorun.inf that contains no DriverPath commands.
>
>
> --------------------------------------------------------------------------------
>
> © 2003 Microsoft Corporation. All rights reserved.
>
>
August 18, 2005 10:46:54 PM

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

David,

Gee, my newsreader in Mozilla has messed up and AT&T is having newserver
problems. I so hope this will reply/post to the message. If not my apology.

Thank you!!! It works like a champ on XP without the need of putting a
utility program on the CD, using your coding:

[autorun]
open = cmd /c start photoalbum_2a.html

However, doesn't work on our 9X computers. :(  Soooo it appears I'll
have to add the opener.exe program to our CDs and code the autorun.inf
with "opener.exe" to make sure the CDs will work on both 9X and XP:

[autorun]
open=opener.exe photoalbum_2a.html

Nowwwww I have a 2nd grade question to ask about external vs internal.
When you say:

> Start is an external program in 9x and an internal command in NT systems.

Does this mean the "start" program was in the system files on the CD (a
CD being an external source) when used in 9X and now is built into the
OS XP somewhere?

[autorun]
open = start photoalbum_2a.html

called up "start" on the CD in 9X and

[autorun]
open = cmd /c start photoalbum_2a.html

calls up "start" on the hard drive in XP? I warned you this was a 2nd
grade now maybe a kindergarten question.

Thanks again.

--- Susan


David Candy wrote:

> Start is an external program in 9x and an internal command in NT systems. Therefore it is not available for use in Autorun.inf. There are different rules for 98 and NT. 98 is compatable on NT (your problem is using a program that doesn't exist) plus it can do more (it doesn't need to use Start - Start functionality is built in).
>
> So,
>
> Use (and you may need to specify a path to the html file) to access the internal commands
>
> cmd /c start photoalbum_2a.html
>
> or just use one of the newer commands
>
> Autorun.inf Commands
>
> --------------------------------------------------------------------------------
>
> This topic is a reference for the commands that can be used in an Autorun.inf file.
>
> a.. [AutoRun] Commands
> b.. [DeviceInstall] Commands
> [AutoRun] Commands
> a.. icon
> b.. label
> c.. open
> d.. shellexecute
> e.. shell
> f.. shell\verb
> icon
> The icon command specifies an icon which represents the AutoRun-enabled drive in the Microsoft® Windows® user interface.
>
> icon=iconfilename[,index]Parameters
> a.. iconfilename
> Name of an .ico, .bmp, .exe, or .dll file containing the icon information. If a file contains more than one icon, you must also specify zero-based index of the icon.
>
> Remarks
> The icon, together with the label, represents the AutoRun-enabled drive in the Windows user interface. For instance, in Windows Explorer, the drive is represented by this icon instead of the standard drive icon. The icon's file must be in the same directory as the file specified by the open command.
>
> The following example specifies the second icon in the MyProg.exe file.
>
> icon=MyProg.exe,1label
> The label command specifies a text label which represents the AutoRun-enabled drive in the Windows user interface.
>
> label=LabelTextParameters
> a.. LabelText
> A text string containing the label. It can contain spaces.
>
> Remarks
> The label, together with an icon, represents the AutoRun-enabled drive in the Windows user interface.
>
> The following example specifies "My Drive Label" as the drive's label.
>
> label=My Drive Labelopen
> The open command specifies the path and file name of the application that AutoRun launches when a user inserts a disc in the drive.
>
> open=[exepath\]exefile [param1 [param2] ...] Parameters
> a.. exefile
> Fully qualified path of an executable file that runs when the CD is inserted. If only a file name is specified, it must be in drive's root directory. To locate the file in a subdirectory, you must specify a path. You can also include one or more command-line parameters to pass to the startup application.
>
> Remarks
> For more information about startup applications, see Tips for Writing AutoRun Startup Applications.
>
> shellexecute
> Version 5.0. The shellexecute command specifies an application or data file that AutoRun will use to call ShellExecuteEx.
>
> shellexecute=[filepath\]filename[param1, [param2]...] Parameters
> a.. filepath
> A string that contains the fully qualified path of the directory that contains the data or executable file. If no path is specified, the file must be in the drive's root directory.
>
> b.. filename
> A string that contains the file's name. If it is an executable file, it is launched. If it is a data file, it must be a member of a file class. ShellExecuteEx launches the default command associated with the file class.
>
> c.. paramx
> Contains any additional parameters that should be passed to ShellExecuteEx.
>
> Remarks
> This command is similar to open, but it allows you to use file association information to run the application.
>
> shell
> The shell command specifies a default command for the drive's shortcut menu.
>
> shell=verbParameters
> a.. verb
> The verb that corresponds to the command. The verb and its associated command must be defined in the Autorun.inf file with a shell\verb command.
>
> Remarks
> When a user right-clicks the drive icon, a shortcut menu appears. If an Autorun.inf file is present, the default shortcut menu command is taken from it. This command also executes when the user double-clicks the drive's icon.
>
> To specify the default shortcut menu command, first define its verb, command string, and menu text with shell\verb. Then use shell to make it the default shortcut menu command. Otherwise, the default menu item text will be "AutoPlay", which launches the application specified by the open command.
>
> shell\verb
> The shell\verb command adds a custom command to the drive's shortcut menu.
>
> shell\verb\command=Filename.exe
> shell\verb=MenuTextParameters
> a.. verb
> The command's verb. The shell\verb\command command associates the verb with an executable file. Verbs must not contain embedded spaces. By default, verb is the text that is displayed in the shortcut menu.
>
> b.. Filename.exe
> The path and file name of the application that performs the command.
>
> c.. MenuText
> This parameter specifies the text that is displayed in the shortcut menu. If it is omitted, verb is displayed. MenuText can be mixed-case and can contain spaces. You can set a shortcut key for the menu item by putting an ampersand (&) in front of the letter.
>
> Remarks
> When a user right-clicks the drive icon, a shortcut menu appears. Adding shell/verb commands to the drive's Autorun.inf file allows you to add commands to this shortcut menu.
>
> There are two parts to this command, which must be on separate lines. The first part is shell/verb/command. It is required. It associates a string, called a verb, with the application to launch when the command runs. The second part is the shell/verb command. It is optional. You can include it to specify the text that displays in the shortcut menu.
>
> To specify a default shortcut menu command, define the verb with shell/verb, and make it the default command with shell.
>
> The following sample Autorun.inf fragment associates the readit verb with the command string "Notepad abc\readme.txt". The menu text is "Read Me", and 'M' is defined as the item's shortcut key. When the user selects this command, the drive's abc\readme.txt file opens with Microsoft Notepad.
>
> shell\readit\command=notepad abc\readme.txt
> shell\readit=Read &Me[DeviceInstall] Commands
> a.. DriverPath
> DriverPath
> The DriverPath command specifies a directory to search recursively for driver files. This command is used during a driver installation and is not part of an AutoRun operation. The [DeviceInstall] section is only supported under Windows XP.
>
> [DeviceInstall]
> DriverPath=directorypathParameters
> a.. directorypath
> A path to a directory that Windows searches for driver files, along with all of its subdirectories.
>
> Remarks
> Do not use drive letters in directorypath as they change from one computer to the next.
>
> To search multiple directories, add a DriverPath command for each directory as in this example.
>
> [DeviceInstall]
> DriverPath=drivers\video
> DriverPath=drivers\audioTo indicate that the media contains no driver files so that it is not searched at all, include a [DeviceInstall] section in Autorun.inf that contains no DriverPath commands.
>
>
> --------------------------------------------------------------------------------
>
> © 2003 Microsoft Corporation. All rights reserved.
>
>
Anonymous
August 19, 2005 3:39:01 AM

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

They were using Start.exe. Part of 9x (but not NT).

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.htm...
=================================================
"Steve Shattuck" <steve@shattuck.net> wrote in message news:e4mfem$oFHA.1968@TK2MSFTNGP14.phx.gbl...
>> I created several CD on our old computer running Win 98SE using
>> autorun.inf file to automatically open an *.html page containing an index
>> of the contains of the CD(s). The autorun.inf on those CDs don't work on
>> any of our XP computers. The CDs are recognized easily by these computers
>> running XP but won't open the autorun.inf files.
>
> I am shocked that you actually had this work in Windows 98SE. The open
> command in an autorun.inf file MUST be a executable file (.EXE), and was
> under the impression that that has always been the case. Not withstanding
> the fact that it worked in W98SE, you need to get a third-part executable
> that will open .html files in XP. Search Google for autorun.inf.
>
> --
> .__
> (__
> __ )teve www.steve.shattuck.net steve@shattuck.net
>
>
Anonymous
August 19, 2005 8:16:37 AM

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

Someone copied Start from 9x to the CD (or maybe the normal search path is followed in which case it wouldn't need to be on CD at all).

An external command is a command in a program file, like notepad (it may or may not be a part of XP). An internal command is a command built into the command interpreter. Usually this terminology is used with command line programs. Take Dir (type cmd in Start Run then type dir) the most used internal command. This is a command inside cmd.exe (or command.com in 9x). You cannot execute a internal command outside of the environment - typing Dir in Start Run just gives File Not Found - because there isn't one.

Conceptually the File Open command in notepad is an internal command - you can't access it from outside of notepad. So when you type a command (say Dir) in a command prompt (cmd.exe in XP) it checks it's internals commands for a match and if found handles it internally. If there is no internal command it is executed as a program.

What one does is set the 9x entries then set the XP entries (ShellExecute=). 9x will ignore the newer XP autorun commands.

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.htm...
=================================================
"Susan" <SGTaylor1@NOSPAMworldnet.com> wrote in message news:p K2Ne.629363$cg1.345270@bgtnsc04-news.ops.worldnet.att.net...
> David,
>
> Thank you!!! It works like a champ on XP without the need of putting a
> utility program on the CD, using your coding:
>
> [autorun]
> open = cmd /c start photoalbum_2a.html
>
> However, doesn't work on our 9X computers. :(  Soooo it appears I'll
> have to add the opener.exe program to our CDs and code the autorun.inf
> with "opener.exe" to make sure the CDs will work on both 9X and XP:
>
> [autorun]
> open=opener.exe photoalbum_2a.html
>
> Nowwwww I have a 2nd grade question to ask about external vs internal.
> When you say:
>
>> Start is an external program in 9x and an internal command in NT systems.
>
> Does this mean the "start" program was in the system files on the CD (a
> CD being an external source) when used in 9X and now is built into the
> OS XP somewhere?
>
> [autorun]
> open = start photoalbum_2a.html
>
> called up "start" on the CD in 9X and
>
> [autorun]
> open = cmd /c start photoalbum_2a.html
>
> calls up "start" on the hard drive in XP? I warned you this was a 2nd
> grade now maybe a kindergarten question.
>
> Thanks again.
>
> --- Susan
>
>
> David Candy wrote:
>> Start is an external program in 9x and an internal command in NT systems. Therefore it is not available for use in Autorun.inf. There are different rules for 98 and NT. 98 is compatable on NT (your problem is using a program that doesn't exist) plus it can do more (it doesn't need to use Start - Start functionality is built in).
>>
>> So,
>>
>> Use (and you may need to specify a path to the html file) to access the internal commands
>>
>> cmd /c start photoalbum_2a.html
>>
>> or just use one of the newer commands
>>
>> Autorun.inf Commands
>>
>> --------------------------------------------------------------------------------
>>
>> This topic is a reference for the commands that can be used in an Autorun.inf file.
>>
>> a.. [AutoRun] Commands
>> b.. [DeviceInstall] Commands
>> [AutoRun] Commands
>> a.. icon
>> b.. label
>> c.. open
>> d.. shellexecute
>> e.. shell
>> f.. shell\verb
>> icon
>> The icon command specifies an icon which represents the AutoRun-enabled drive in the Microsoft® Windows® user interface.
>>
>> icon=iconfilename[,index]Parameters
>> a.. iconfilename
>> Name of an .ico, .bmp, .exe, or .dll file containing the icon information. If a file contains more than one icon, you must also specify zero-based index of the icon.
>>
>> Remarks
>> The icon, together with the label, represents the AutoRun-enabled drive in the Windows user interface. For instance, in Windows Explorer, the drive is represented by this icon instead of the standard drive icon. The icon's file must be in the same directory as the file specified by the open command.
>>
>> The following example specifies the second icon in the MyProg.exe file.
>>
>> icon=MyProg.exe,1label
>> The label command specifies a text label which represents the AutoRun-enabled drive in the Windows user interface.
>>
>> label=LabelTextParameters
>> a.. LabelText
>> A text string containing the label. It can contain spaces.
>>
>> Remarks
>> The label, together with an icon, represents the AutoRun-enabled drive in the Windows user interface.
>>
>> The following example specifies "My Drive Label" as the drive's label.
>>
>> label=My Drive Labelopen
>> The open command specifies the path and file name of the application that AutoRun launches when a user inserts a disc in the drive.
>>
>> open=[exepath\]exefile [param1 [param2] ...] Parameters
>> a.. exefile
>> Fully qualified path of an executable file that runs when the CD is inserted. If only a file name is specified, it must be in drive's root directory. To locate the file in a subdirectory, you must specify a path. You can also include one or more command-line parameters to pass to the startup application.
>>
>> Remarks
>> For more information about startup applications, see Tips for Writing AutoRun Startup Applications.
>>
>> shellexecute
>> Version 5.0. The shellexecute command specifies an application or data file that AutoRun will use to call ShellExecuteEx.
>>
>> shellexecute=[filepath\]filename[param1, [param2]...] Parameters
>> a.. filepath
>> A string that contains the fully qualified path of the directory that contains the data or executable file. If no path is specified, the file must be in the drive's root directory.
>>
>> b.. filename
>> A string that contains the file's name. If it is an executable file, it is launched. If it is a data file, it must be a member of a file class. ShellExecuteEx launches the default command associated with the file class.
>>
>> c.. paramx
>> Contains any additional parameters that should be passed to ShellExecuteEx.
>>
>> Remarks
>> This command is similar to open, but it allows you to use file association information to run the application.
>>
>> shell
>> The shell command specifies a default command for the drive's shortcut menu.
>>
>> shell=verbParameters
>> a.. verb
>> The verb that corresponds to the command. The verb and its associated command must be defined in the Autorun.inf file with a shell\verb command.
>>
>> Remarks
>> When a user right-clicks the drive icon, a shortcut menu appears. If an Autorun.inf file is present, the default shortcut menu command is taken from it. This command also executes when the user double-clicks the drive's icon.
>>
>> To specify the default shortcut menu command, first define its verb, command string, and menu text with shell\verb. Then use shell to make it the default shortcut menu command. Otherwise, the default menu item text will be "AutoPlay", which launches the application specified by the open command.
>>
>> shell\verb
>> The shell\verb command adds a custom command to the drive's shortcut menu.
>>
>> shell\verb\command=Filename.exe
>> shell\verb=MenuTextParameters
>> a.. verb
>> The command's verb. The shell\verb\command command associates the verb with an executable file. Verbs must not contain embedded spaces. By default, verb is the text that is displayed in the shortcut menu.
>>
>> b.. Filename.exe
>> The path and file name of the application that performs the command.
>>
>> c.. MenuText
>> This parameter specifies the text that is displayed in the shortcut menu. If it is omitted, verb is displayed. MenuText can be mixed-case and can contain spaces. You can set a shortcut key for the menu item by putting an ampersand (&) in front of the letter.
>>
>> Remarks
>> When a user right-clicks the drive icon, a shortcut menu appears. Adding shell/verb commands to the drive's Autorun.inf file allows you to add commands to this shortcut menu.
>>
>> There are two parts to this command, which must be on separate lines. The first part is shell/verb/command. It is required. It associates a string, called a verb, with the application to launch when the command runs. The second part is the shell/verb command. It is optional. You can include it to specify the text that displays in the shortcut menu.
>>
>> To specify a default shortcut menu command, define the verb with shell/verb, and make it the default command with shell.
>>
>> The following sample Autorun.inf fragment associates the readit verb with the command string "Notepad abc\readme.txt". The menu text is "Read Me", and 'M' is defined as the item's shortcut key. When the user selects this command, the drive's abc\readme.txt file opens with Microsoft Notepad.
>>
>> shell\readit\command=notepad abc\readme.txt
>> shell\readit=Read &Me[DeviceInstall] Commands
>> a.. DriverPath
>> DriverPath
>> The DriverPath command specifies a directory to search recursively for driver files. This command is used during a driver installation and is not part of an AutoRun operation. The [DeviceInstall] section is only supported under Windows XP.
>>
>> [DeviceInstall]
>> DriverPath=directorypathParameters
>> a.. directorypath
>> A path to a directory that Windows searches for driver files, along with all of its subdirectories.
>>
>> Remarks
>> Do not use drive letters in directorypath as they change from one computer to the next.
>>
>> To search multiple directories, add a DriverPath command for each directory as in this example.
>>
>> [DeviceInstall]
>> DriverPath=drivers\video
>> DriverPath=drivers\audioTo indicate that the media contains no driver files so that it is not searched at all, include a [DeviceInstall] section in Autorun.inf that contains no DriverPath commands.
>>
>>
>> --------------------------------------------------------------------------------
>>
>> © 2003 Microsoft Corporation. All rights reserved.
>>
>>
>
!