Why does this *work*? (Using MST & autrun.inf on CD)

J

John Straffin

Hey all,

Here's what I did:

1) Made an ISO of Microsoft Office Professional Enterprise Edition
2003 (Volume License) using WinISO
2) Used the Microsoft Office 2003 Resource Kit's Custom Installation
Wizard to create an MST with my desired settings.
3) Changed the AUTORUN.INF on the CD to the following:

[autorun]
ICON=SETUP.EXE,1

shell\configure=C&onfigure...
shell\configure\command=SETUP.EXE

shell\install=&Default Install...
shell\install\command=SETUP.EXE

shell\CDSS=&CDSS Install...
shell\CDSS\command=SETUP.EXE TRANSFORMS="CDSS.MST" /qb-

4) Added modified AUTORUN.INF and the CDSS.MST to the root of the ISO.
5) Burned the ISO to CD.
6) Insert CD, installation automatically begins and installs Office
2003 with all of my settings.

Why?!?! I had expected Autorun to do *nothing* because I removed the
"OPEN=SETUP.EXE /AUTORUN" line from the AUTORUN.INF. And then, I would
have expected an "autoran" setup to be the standard non-quiet,
prompt-for-the-key installation.

- How did the installation automatically begin?
- How did the installation pick up my MST file without being
explicitly told to use it?

I'm happy that it works, but I'd love to know why...

- John
 
M

Milly Staples [MVP - Outlook]

Because it is Microsoft and Microsoft stuff just works!!!!

<rotfl>


--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, John Straffin
asked:

| Hey all,
|
| Here's what I did:
|
| 1) Made an ISO of Microsoft Office Professional Enterprise Edition
| 2003 (Volume License) using WinISO
| 2) Used the Microsoft Office 2003 Resource Kit's Custom Installation
| Wizard to create an MST with my desired settings.
| 3) Changed the AUTORUN.INF on the CD to the following:
|
| [autorun]
| ICON=SETUP.EXE,1
|
| shell\configure=C&onfigure...
| shell\configure\command=SETUP.EXE
|
| shell\install=&Default Install...
| shell\install\command=SETUP.EXE
|
| shell\CDSS=&CDSS Install...
| shell\CDSS\command=SETUP.EXE TRANSFORMS="CDSS.MST" /qb-
|
| 4) Added modified AUTORUN.INF and the CDSS.MST to the root of the ISO.
| 5) Burned the ISO to CD.
| 6) Insert CD, installation automatically begins and installs Office
| 2003 with all of my settings.
|
| Why?!?! I had expected Autorun to do *nothing* because I removed the
| "OPEN=SETUP.EXE /AUTORUN" line from the AUTORUN.INF. And then, I would
| have expected an "autoran" setup to be the standard non-quiet,
| prompt-for-the-key installation.
|
| - How did the installation automatically begin?
| - How did the installation pick up my MST file without being
| explicitly told to use it?
|
| I'm happy that it works, but I'd love to know why...
|
| - John
 
M

Milly Staples [MVP - Outlook]

Because it is Microsoft and Microsoft stuff just works!!!!

<rotfl>


--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, John Straffin
asked:

| Hey all,
|
| Here's what I did:
|
| 1) Made an ISO of Microsoft Office Professional Enterprise Edition
| 2003 (Volume License) using WinISO
| 2) Used the Microsoft Office 2003 Resource Kit's Custom Installation
| Wizard to create an MST with my desired settings.
| 3) Changed the AUTORUN.INF on the CD to the following:
|
| [autorun]
| ICON=SETUP.EXE,1
|
| shell\configure=C&onfigure...
| shell\configure\command=SETUP.EXE
|
| shell\install=&Default Install...
| shell\install\command=SETUP.EXE
|
| shell\CDSS=&CDSS Install...
| shell\CDSS\command=SETUP.EXE TRANSFORMS="CDSS.MST" /qb-
|
| 4) Added modified AUTORUN.INF and the CDSS.MST to the root of the ISO.
| 5) Burned the ISO to CD.
| 6) Insert CD, installation automatically begins and installs Office
| 2003 with all of my settings.
|
| Why?!?! I had expected Autorun to do *nothing* because I removed the
| "OPEN=SETUP.EXE /AUTORUN" line from the AUTORUN.INF. And then, I would
| have expected an "autoran" setup to be the standard non-quiet,
| prompt-for-the-key installation.
|
| - How did the installation automatically begin?
| - How did the installation pick up my MST file without being
| explicitly told to use it?
|
| I'm happy that it works, but I'd love to know why...
|
| - John
 
M

Milly Staples [MVP - Outlook]

Because it is Microsoft and Microsoft stuff just works!!!!

<rotfl>


--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, John Straffin
asked:

| Hey all,
|
| Here's what I did:
|
| 1) Made an ISO of Microsoft Office Professional Enterprise Edition
| 2003 (Volume License) using WinISO
| 2) Used the Microsoft Office 2003 Resource Kit's Custom Installation
| Wizard to create an MST with my desired settings.
| 3) Changed the AUTORUN.INF on the CD to the following:
|
| [autorun]
| ICON=SETUP.EXE,1
|
| shell\configure=C&onfigure...
| shell\configure\command=SETUP.EXE
|
| shell\install=&Default Install...
| shell\install\command=SETUP.EXE
|
| shell\CDSS=&CDSS Install...
| shell\CDSS\command=SETUP.EXE TRANSFORMS="CDSS.MST" /qb-
|
| 4) Added modified AUTORUN.INF and the CDSS.MST to the root of the ISO.
| 5) Burned the ISO to CD.
| 6) Insert CD, installation automatically begins and installs Office
| 2003 with all of my settings.
|
| Why?!?! I had expected Autorun to do *nothing* because I removed the
| "OPEN=SETUP.EXE /AUTORUN" line from the AUTORUN.INF. And then, I would
| have expected an "autoran" setup to be the standard non-quiet,
| prompt-for-the-key installation.
|
| - How did the installation automatically begin?
| - How did the installation pick up my MST file without being
| explicitly told to use it?
|
| I'm happy that it works, but I'd love to know why...
|
| - John
 
M

Milly Staples [MVP - Outlook]

Because it is Microsoft and Microsoft stuff just works!!!!

<rotfl>


--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, John Straffin
asked:

| Hey all,
|
| Here's what I did:
|
| 1) Made an ISO of Microsoft Office Professional Enterprise Edition
| 2003 (Volume License) using WinISO
| 2) Used the Microsoft Office 2003 Resource Kit's Custom Installation
| Wizard to create an MST with my desired settings.
| 3) Changed the AUTORUN.INF on the CD to the following:
|
| [autorun]
| ICON=SETUP.EXE,1
|
| shell\configure=C&onfigure...
| shell\configure\command=SETUP.EXE
|
| shell\install=&Default Install...
| shell\install\command=SETUP.EXE
|
| shell\CDSS=&CDSS Install...
| shell\CDSS\command=SETUP.EXE TRANSFORMS="CDSS.MST" /qb-
|
| 4) Added modified AUTORUN.INF and the CDSS.MST to the root of the ISO.
| 5) Burned the ISO to CD.
| 6) Insert CD, installation automatically begins and installs Office
| 2003 with all of my settings.
|
| Why?!?! I had expected Autorun to do *nothing* because I removed the
| "OPEN=SETUP.EXE /AUTORUN" line from the AUTORUN.INF. And then, I would
| have expected an "autoran" setup to be the standard non-quiet,
| prompt-for-the-key installation.
|
| - How did the installation automatically begin?
| - How did the installation pick up my MST file without being
| explicitly told to use it?
|
| I'm happy that it works, but I'd love to know why...
|
| - John
 
M

Milly Staples [MVP - Outlook]

Because it is Microsoft and Microsoft stuff just works!!!!

<rotfl>


--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, John Straffin
asked:

| Hey all,
|
| Here's what I did:
|
| 1) Made an ISO of Microsoft Office Professional Enterprise Edition
| 2003 (Volume License) using WinISO
| 2) Used the Microsoft Office 2003 Resource Kit's Custom Installation
| Wizard to create an MST with my desired settings.
| 3) Changed the AUTORUN.INF on the CD to the following:
|
| [autorun]
| ICON=SETUP.EXE,1
|
| shell\configure=C&onfigure...
| shell\configure\command=SETUP.EXE
|
| shell\install=&Default Install...
| shell\install\command=SETUP.EXE
|
| shell\CDSS=&CDSS Install...
| shell\CDSS\command=SETUP.EXE TRANSFORMS="CDSS.MST" /qb-
|
| 4) Added modified AUTORUN.INF and the CDSS.MST to the root of the ISO.
| 5) Burned the ISO to CD.
| 6) Insert CD, installation automatically begins and installs Office
| 2003 with all of my settings.
|
| Why?!?! I had expected Autorun to do *nothing* because I removed the
| "OPEN=SETUP.EXE /AUTORUN" line from the AUTORUN.INF. And then, I would
| have expected an "autoran" setup to be the standard non-quiet,
| prompt-for-the-key installation.
|
| - How did the installation automatically begin?
| - How did the installation pick up my MST file without being
| explicitly told to use it?
|
| I'm happy that it works, but I'd love to know why...
|
| - John
 
G

GMAN Slater

Now try to make you a custom setup.ini file with all the patches chained during install. Have the patches on the CD as well. See how well Microsoft's stuff just *works* (or not)!
 
G

GMAN Slater

Now try to make you a custom setup.ini file with all the patches chained during install. Have the patches on the CD as well. See how well Microsoft's stuff just *works* (or not)!
 
G

GMAN Slater

Now try to make you a custom setup.ini file with all the patches chained during install. Have the patches on the CD as well. See how well Microsoft's stuff just *works* (or not)!
 
G

GMAN Slater

Now try to make you a custom setup.ini file with all the patches chained during install. Have the patches on the CD as well. See how well Microsoft's stuff just *works* (or not)!
 
G

GMAN Slater

Now try to make you a custom setup.ini file with all the patches chained during install. Have the patches on the CD as well. See how well Microsoft's stuff just *works* (or not)!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Trying to create a One Click Autorun DVD for Office 2007 5
Office 2003 rollout - workstations need the install after every re 0
Office 2003 does not Autorun Setup 2
Office XP Pro with Frontpage autorun problem 1
Help! Using an MST file to modify installation with group policy 2
Office 2003, Custom Installation Wizard, MST 45
MST error 3
Office 2003 Hangs during installation 5

Top