To elaborate on Ken Gober's answer, you want one of the following:

• Microsoft Windows Resource Kit for Operating System Version 3.1, Pages 75 through 82 (Using Automated Setup: Setup /h) for a quick start and, for more detail, Chapter 2: The Windows Setup Information Files (pages 85 through 133)

• Microsoft Windows for Workgroups Resource Kit for Operating System Version 3.1, Pages 3-22 through 3-30 (Using Automated Setup: Setup /h) for a quick start and, for more detail, Chapter 5: Windows for Workgroups Setup Information Files (pages 5-1 through 5-74)

(I have no clue what the absolute page numbers would be as you'd find in a PDF. I only have them in their original dead tree form.)

The TL;DR if you don't have a copy of the resource kit handy is:

1. Make and customize a copy of the example SETUP.SHH file from Windows 3.1 Disk 1 or Windows for Workgroups 3.1 Disk 1.

   (The "Addendum for Operating System Version 3.11" doesn't have a section for this, but I checked my floppies and can confirm the location is unchanged.)

2. Invoke Windows Setup as setup /h:<path to SHH file>

If you used setup /a to unpack the Windows files to a network server to be depended on by setup /n or setup /h:<path to SHH file> /n (basically, thin client install), then setup.shh will get copied to the network server so you can just customize it in place rather than having to update your network-enabled DOS boot floppy every time your deployment image changes.

The resource kit warns you that parsing of the .SHH file will not be affected by your locale settings and to only use "ANSI characters", but I can't remember whether they mean 7-bit ASCII or are following the vernacular of back in the day and are using it as an incorrect name for the system's default codepage. (Codepage 437 for machines sold in Redmond, WA.)

Combined with the later sections on customizing .ini and .inf files for stuff like preloading custom program groups, PIFs, etc., the detailed information section contains everything you need to turn the Windows 3.1x installer into a full-blown automated deployment solution, but those customizations aren't specific to automated installs and you can learn how to do that by examining a system restore CD which does so.

(For example, the Gateway 2000 System CD version 3.0 (Windows 3.1) or 3.6 (Windows 3.11 for Workgroups.)

To elaborate on Ken Gober's answer, you want one of the following:

• Microsoft Windows Resource Kit for Operating System Version 3.1, Pages 75 through 82 (Using Automated Setup: Setup /h) for a quick start and, for more detail, Chapter 2: The Windows Setup Information Files (pages 85 through 133)

• Microsoft Windows for Workgroups Resource Kit for Operating System Version 3.1, Pages 3-22 through 3-30 (Using Automated Setup: Setup /h) for a quick start and, for more detail, Chapter 5: Windows for Workgroups Setup Information Files (pages 5-1 through 5-74)

(I have no clue what the absolute page numbers would be as you'd find in a PDF. I only have them in their original dead tree form.)

The TL;DR if you don't have a copy of the resource kit handy is:

1. Make and customize a copy of the example SETUP.SHH file from Windows 3.1 Disk 1 or Windows for Workgroups 3.1 Disk 1.

   (The "Addendum for Operating System Version 3.11" doesn't have a section for this, but I checked my floppies and can confirm the location is unchanged.)

2. Invoke Windows Setup as setup /h:<path to SHH file>

If you used setup /a to unpack the Windows files to a network server to be depended on by setup /n or setup /h:<path to SHH file> /n (basically, thin client install), then setup.shh will get copied to the network server so you can just customize it in place rather than having to update your network-enabled DOS boot floppy every time your deployment image changes.

The resource kit warns you that parsing of the .SHH file will not be affected by your locale settings and to only use "ANSI characters", but I can't remember whether they mean 7-bit ASCII or are following the vernacular of back in the day and are using it as an incorrect name for the system's default codepage. (Codepage 437 for machines sold in Redmond, WA.)

Combined with the later sections on customizing .ini and .inf files for stuff like preloading custom program groups, PIFs, etc., the detailed information section contains everything you need to turn the Windows 3.1x installer into a full-blown automated deployment solution, but those customizations aren't specific to automated installs and you can learn how to do that by examining a system restore CD which does so.

(For example, the Gateway 2000 System CD version 3.0 (Windows 3.1) or 3.6 (Windows 3.11 for Workgroups).)

To elaborate on Ken Gober's answer, you want one of the following:

• Microsoft Windows Resource Kit for Operating System Version 3.1, Pages 75 through 82 (Using Automated Setup: Setup /h) for a quick start and, for more detail, Chapter 2: The Windows Setup Information Files (pages 85 through 133)

• Microsoft Windows for Workgroups Resource Kit for Operating System Version 3.1, Pages 3-22 through 3-30 (Using Automated Setup: Setup /h) for a quick start and, for more detail, Chapter 5: Windows for Workgroups Setup Information Files (pages 5-1 through 5-74)

(I have no clue what the absolute page numbers would be as you'd find in a PDF. I only have them in their original dead tree form.)

Combined with the later sections on customizing .ini and .inf files, the detailed information section contains everything you need to turn the Windows 3.1x installer into a full-blown automated deployment solution.

The TL;DR if you don't have a copy of the resource kit handy is:

1. Make and customize a copy of the example SETUP.SHH file from Windows 3.1 Disk 1 or Windows for Workgroups 3.1 Disk 1.

   (The "Addendum for Operating System Version 3.11" doesn't have a section for this, but I checked my floppies and can confirm the location is unchanged.)

2. Invoke Windows Setup as setup /h:<path to SHH file>

If you used setup /a to unpack the Windows files to a network server to be depended on by setup /n or setup /h:<path to SHH file> /n (basically, thin client install), then setup.shh will get copied to the network server so you can just customize it in place rather than having to update your network-enabled DOS boot floppy every time your deployment image changes.

The resource kit warns you that parsing of the .SHH file will not be affected by your locale settings and to only use "ANSI characters", but I can't remember whether they mean 7-bit ASCII or are following the vernacular of back in the day and are using it as an incorrect name for the system's default codepage. (Codepage 437 for machines sold in Redmond, WA.)

You can also customize other things like .ini and .inf files before deploying and documenting those files is a large part of the rest of the resource kit, but those customizations aren't specific to automated installs and you can learn how to do that by examining a system restore CD which does so.

(For example, the Gateway 2000 System CD version 3.0 (Windows 3.1) or 3.6 (Windows 3.11 for Workgroups.)

To elaborate on Ken Gober's answer, you want one of the following:

• Microsoft Windows Resource Kit for Operating System Version 3.1, Pages 75 through 82 (Using Automated Setup: Setup /h) for a quick start and, for more detail, Chapter 2: The Windows Setup Information Files (pages 85 through 133)

• Microsoft Windows for Workgroups Resource Kit for Operating System Version 3.1, Pages 3-22 through 3-30 (Using Automated Setup: Setup /h) for a quick start and, for more detail, Chapter 5: Windows for Workgroups Setup Information Files (pages 5-1 through 5-74)

(I have no clue what the absolute page numbers would be as you'd find in a PDF. I only have them in their original dead tree form.)

The TL;DR if you don't have a copy of the resource kit handy is:

1. Make and customize a copy of the example SETUP.SHH file from Windows 3.1 Disk 1 or Windows for Workgroups 3.1 Disk 1.

   (The "Addendum for Operating System Version 3.11" doesn't have a section for this, but I checked my floppies and can confirm the location is unchanged.)

2. Invoke Windows Setup as setup /h:<path to SHH file>

If you used setup /a to unpack the Windows files to a network server to be depended on by setup /n or setup /h:<path to SHH file> /n (basically, thin client install), then setup.shh will get copied to the network server so you can just customize it in place rather than having to update your network-enabled DOS boot floppy every time your deployment image changes.

The resource kit warns you that parsing of the .SHH file will not be affected by your locale settings and to only use "ANSI characters", but I can't remember whether they mean 7-bit ASCII or are following the vernacular of back in the day and are using it as an incorrect name for the system's default codepage. (Codepage 437 for machines sold in Redmond, WA.)

Combined with the later sections on customizing .ini and .inf files for stuff like preloading custom program groups, PIFs, etc., the detailed information section contains everything you need to turn the Windows 3.1x installer into a full-blown automated deployment solution, but those customizations aren't specific to automated installs and you can learn how to do that by examining a system restore CD which does so.

(For example, the Gateway 2000 System CD version 3.0 (Windows 3.1) or 3.6 (Windows 3.11 for Workgroups.)