Re: autorun.inf

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. 


.

Relevant Pages

  • Re: passing argument to the main program
    ... The VERB definition language (CDU) is certainly different, but the contents look very much like some simple configuration file...the syntax is quite straight forward. ... At this point one has a choice of loading that verb definition into the user's command tables, into the system's command tables, and/or the verb can be compiled in to object code that can be linked into the program. ... plus procedures to compile the source (PASCAL and SET COMMAND, ...
    (comp.lang.fortran)
  • Re: Custom Forms Designer Context Menus
    ... Public Sub AddCommand(ByVal command As ... Public Sub AddVerb(ByVal verb As System.ComponentModel.Design.DesignerVerb) ... Dim menuItem As MenuItem = New MenuItem ... Dim designer As IDesigner = host.GetDesigner ...
    (microsoft.public.dotnet.framework.windowsforms.designtime)
  • Re: passing argument to the main program
    ... At least that is how programs under DCL were supposed to do it. ... _VERB_ to invoke your program, along with defined PARAMETERS and/or QUALIFIERS. ... At this point one has a choice of loading that verb definition into the user's command tables, into the system's command tables, and/or the verb can be compiled in to object code that can be linked into the program. ... "$ run myprog string1 string2". ...
    (comp.lang.fortran)
  • Re: Programmatically set printer, copy count, paper size, zoom, and other propeties for job
    ... This page is the closest I can find to an explanation of the "printto" verb: ... You might find it easier to run a command line. ... > one for each of the doc types we use) to specify the printer without ...
    (microsoft.public.win2000.printing)
  • Re: Newbie with command file problem
    ... > at the command prompt caused the file GPJSHQ.COM to be typed. ... TYPE, RENAME, SET, DELETE, COPY and LOGOUT are all DCL verbs. ... verb since DCL only parses the first four characters, ... command file would have done, but it was NOT your command file doing ...
    (comp.os.vms)
Loading