Windows

{mod note}This is a copy of a tutorial created by user Glijnos back in 2012. Unfortunately Glijnos made a lot of use of IMG tags, which the forum now deprecates for security reasons (offsite images can be substituted with nasty stuff that we won't go into), hence his tutorial was ruined. Presented below is the same tutorial using local attachments, broken into multiple posts so that each post can remain below the forums three attachments limit
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Tutorial: Installing Windows For Workgroups 3.11 (Windows 3.11) on VirtualBox with full driver support.

Introduction
For this Tutorial VirtualBox has to be installed (correctly) on your computer.
This tutorial was tested on the hosts Windows 7 SP1 and Linux (Ubuntu 11.04). But should probably work on other hosts as well.
For this tutorial I used my 3.5-inch floppy disks of MS-DOS 6.22 and Windows 3.11. My present pc no longer has a floppy disk drive, so I used an old pc to create floppy images (.IMA) from my old floppy's.

: floppyimages.jpg (55.78 KiB) Viewed 90277 times

Now that we have created the floppy images we can start to configure VirtualBox.
Create a virtual machine
Create in VirtualBox a new virtual machine with the name Windows 3.11 or any name you like. By OS Type select the Operating System: Microsoft Window. Under version select: Windows 3.1.

: vitualboxnewvm.jpg (50.34 KiB) Viewed 90277 times

Hit Next.
By memory use the default Base memory size of 32 megabyte.
Hit Next.
Create a new hard disk.
Hit Next.
Use the default file type: VDI (Others may also work).
Hit Next.
By storage details use the option you like (I used Dynamically allocated)
Hit Next.
If you like, you can give the virtual disk another name or location.
Use the default disk size of 1,00 Gigabyte (MS-DOS 6.22 can only recognise hard disks up to 2.1 GB)
Hit Next, then two times Create to create the virtual machine.

Glijnos

Before you start the virtual machine you have to add a floppy controller.
Right click on the new virtual machine, then Settings, under Storage click: Add floppy controller.

: newvmcreatedfloppy.jpg (38.54 KiB) Viewed 90193 times

Add the newly added controller click on the green plus(+). A new window will popup, select: leave empty.

: floppyleaveempty.jpg (44.12 KiB) Viewed 90193 times

Now that this is finished you can start the virtual machine.

Glijnos

MS-DOS is needed to run Windows 3.11. You can see Windows 3.11 as a graphical shell that depends on MS-DOS architecture.

Now that your virtual machine is running you will get the following message:

: vmrunninghalted.jpg (18.19 KiB) Viewed 90084 times

In the menu bar click on devices then --> Floppy Devices --> Choose a virtual floppy disk file... then select your first MS-DOS 6.22 setup floppy image file.

: vmrunningselectmsdosflo.jpg (32.7 KiB) Viewed 90084 times

Hit Right Ctrl + R or use the menu bar --> Machine --> Reset to reboot the virtual machine.

After the reboot VirtualBox loads the floppy Image and it will show the MS-DOS setup screen.

: msdossetup.jpg (49.46 KiB) Viewed 90084 times

Glijnos

Hit Enter to start the setup.

Next Choose: Configure Unallocated disk space.
Next, hit Enter to reboot your virtual machine.
After the reboot MS-DOS will format the virtual hard disk.

: msdosformat.jpg (31.13 KiB) Viewed 90132 times

If the formatting hangs on 0%, then you have to reboot the virtual machine (right ctrl + R) and hit F8 until you see the following screen:

: msdossetuphitf8screen.jpg (26.61 KiB) Viewed 90132 times

Refuse loading of AUTOEXEC.BAT
When the A:\> prompt will appears, give the command "format c:" and enter the command "setup" once formatting is done.

: msdossetuphitf8screenfo.jpg (41.05 KiB) Viewed 90132 times

when the MS-DOS setup is running again you can follow the instructions on screen for installing MS-DOS.

Glijnos

When the MS-DOS setup asks for Setup Disk #2, you have to load the next MS-DOS Floppy image.

Click on devices in the menu bar again, then --> Floppy Devices --> Choose a virtual floppy disk file... then select your next MS-DOS 6.22 floppy image file.

Use the same method for disk #3.

: msdossetupnewdisk.jpg (43.79 KiB) Viewed 90132 times

When the setup is done, remove the floppy disk from the virtual drive, and press ENTER.

: msdossetupfinishremoved.jpg (41.01 KiB) Viewed 90132 times

Setup complete:

: msdossetupfinishfinal.jpg (33.21 KiB) Viewed 90132 times

Glijnos

After the reboot the MS-DOS 6.22 prompt will be loaded.

Glijnos

Now that MS-DOS is installed we can start to run the Windows 3.11 setup.
Click on devices in the menu bar again then --> Floppy Devices --> Choose a virtual floppy disk file... then select your first Windows 3.11 floppy image file.
At the C:\> prompt, give the command "A:\" and enter the command 'setup' once the prompt A:\> will appear and hit enter.
The Windows for Workgroups 3.11 setup screen will appear.

: 311setupscreen.jpg (36.69 KiB) Viewed 90133 times

Hit enter to setup Windows for Workgroups 3.11.
On the next screen choose the Express Setup with the enter key (the express setup is usually fine).
Windows will now be installed. When the setup asks for disk 2, click on devices in the menu bar again then --> Floppy Devices --> Choose a virtual floppy disk file... then select your next Windows 3.11 floppy image file.
After that the setup will reboot to a more graphical style and ask for your name, company and product number (use your windows 3.11 product number )

: 311setupproductnumber.jpg (60.39 KiB) Viewed 90133 times

Click Continue.
Verify your information and Click Continue.
The setup will now continue. When it ask for the next disk, select your next Windows 3.11 floppy image and hit Enter.

: 311setupfloppydisk3.jpg (47.49 KiB) Viewed 90133 times

Repeat this action for the following floppy disks.

Glijnos

When it asks for printer installation, just leave the "No Printer Attached" option selected and press the Install button.
When it asks for Network Setup, just press continue (You have to configure this later).
When it asks for the application name for C:\DOS\EDIT.COM, leave the default "MS-DOS Editor" option enabled and press OK.
You can choose to either Run Tutorial or Skip Tutorial.
Setup complete!
Remove your last floppy Image and press Restart Computer.

: 311setupcomplete.jpg (49.87 KiB) Viewed 90133 times

After the reboot, you can type win into the MS-DOS command line to see your new, working Windows 3.11! It is fully usable at this point, but continue with the rest of this tutorial to enable network support, CD-ROM drivers, video drivers, sound drivers and Internet Explorer.

: 311windows.jpg (76.71 KiB) Viewed 90132 times

Glijnos

It works quicker to load all drivers and setup files on a single CD-ROM disk image then on multiple floppy's images, so the first thing we need to do is to configure the ms-dos/Win 3.11 installation to recognise the VirtualBox (virtual) CD-ROM drive.
Search the web for the file AOATAPI.SYS and Copy the AOATAPI.SYS file to a floppy disk image, or use the CD-ROM driver floppy Image that I already made for you.
Start your virtual machine. Load the floppy Image, and then type COPY A:\AOATAPI.SYS C: at the command prompt to copy the AOATAPI.SYS file to your C: drive.
After that you must edit your AUTOEXEC.BAT and CONFIG.SYS files.
At the C:\ command prompt type EDIT AUTOEXEC.BAT. Place the line: c:\dos\mscdex.exe /d:idecd000 in the autoexec.bat and save, then exit (use the Alt key to activate the menu).

: cdromeditautoexec.jpg (45.24 KiB) Viewed 90131 times

At the C:\ prompt type EDIT CONFIG.SYS. Place the line device=c:\aoatapi.sys /d:idecd000 in the config.sys and then save, then exit.

: cdromeditconfig.jpg (45.65 KiB) Viewed 90131 times

Restart the virtual machine and go into windows. Open the File Manager and now you will see Drive D for the CD ROM.
I loaded the VirtualBox Guest additions for testing.

: cdromloaded.jpg (45.47 KiB) Viewed 90131 times

Glijnos

Search the web for the Sound Blaster 16/AWE for DOS/Windows 3.1 drivers and Copy them to a CD-ROM disk image or floppy disk image, or use the CD-ROM disk image that I already made for you.
Start-up MS-DOS to a C:\ prompt. Load the floppy or CD image, access the SoundBlaster 16 drivers on the A: or D: drive, then type install.
Note: On my driver CDROM type CD sb16 at the command prompt and then install.

: soundinstallcmd.jpg (32.32 KiB) Viewed 90243 times

Accept all of the defaults in the installation.

: soundinstallsettings.jpg (45.51 KiB) Viewed 90243 times

When the installation is complete you can run windows with sound.
When you run windows it will create a Audio Program Group automatically.

: soundwindows311.jpg (38.2 KiB) Viewed 90243 times

Glijnos

Search the web for the "AMD PCNET Family (NDIS2/NDIS3)" driver and the " Microsoft TCP-IP-32 3.11b"drivers for Windows 3.11. Copy them to a CD-ROM disk Image or floppy disk Image, or use the CD-ROM disk Image that I already made for you.
Boot into windows 3.11 and open the program group "Main". In "Main" open the program "Windows Setup", click "options" and then "Change Network Settings".

: networksetup.jpg (60.12 KiB) Viewed 90132 times

On the "Network Setup" screen click on networks. On the next screen select "Install Microsoft Windows Network" and hit "OK".

: networkinstallnetwork.jpg (65.24 KiB) Viewed 90132 times

Click "OK" again on the "Network Setup" screen.
On the "Add Network Adapter" screen select the "Unlisted or Updated Network Adapter" option and click "OK".

: networksetupunlisted.jpg (51.35 KiB) Viewed 90132 times

Glijnos

On the CDROM drive or Floppy disk Image select the directory where you stored the " AMD PCNET Family " drivers --> windowsnetdrv (windowsn) and click "OK".

: networkdriverlocationse.jpg (61.76 KiB) Viewed 90132 times

And "OK" again, then select the "Advanced Micro Devices PCNET family" driver and click "OK" again.

: networkdriveramdselect.jpg (51.05 KiB) Viewed 90132 times

Enter an User Name, Workgroup and Computer Name or keep the defaults and click "OK" again.

: networkcomputername.jpg (42.49 KiB) Viewed 90132 times

Glijnos

When the setup asks for your Windows 3.11 Disk 7 and 8 floppy, load them and Click "OK".
When the installation is complete click "OK" and then click "Restart Computer".
Don't forget to remove your windows 3.11 installation floppy!

: networksetupfinishmodif.jpg (50.58 KiB) Viewed 90086 times

When the reboot is complete start Windows Again. You get the messenger: welcome to Windows for Workgroups. Click "OK" to make a new password or "Cancel" the start the Program Manager.

: welcomecq.jpg (31.09 KiB) Viewed 90086 times

Go to the program group "Network" and click "Network Setup". On the Network setup click on "Drivers", then "Add protocol" and select "Unlisted or Updated Protocol", then hit "ÖK".

: networkprotocolsetup.jpg (59.64 KiB) Viewed 90086 times

Glijnos

On the CDROM drive or Floppy disk Image select the directory where you stored the "Microsoft tcpip311b" drivers and click "OK".
Select the Microsoft TCP/IP32 3.11b protocol and click "OK" again.

: networkmicrosoftprotoco.jpg (53.93 KiB) Viewed 89827 times

When the installation is complete click "Close", after that click "OK".
When the "Microsoft TCP/IP configuration" window pops up select "Enable Automatic DHCP configuration" or use your own configuration and hit "OK".

: networkdhcp.jpg (53.92 KiB) Viewed 89827 times

Click on "Restart Computer" to finish the installation.
To confirm that networking is working at this stage, try opening a MS-DOS Prompt from the "Main" group and type "ping http://www.google.nl".

: networkping.jpg (54.55 KiB) Viewed 89827 times

If you get a reply, then your network installation is working correctly. Type exit to return to windows.

Glijnos

To browse the internet you need to install a browser.
Search the web for the "Internet Explorer 5 (windows 3.11)" and copy the installer to a CD-ROM disk Image. You can also use the CD-ROM disk image that I made for you.
In windows open the File Manager, open your D:\ drive and run the msie501w311 installer.

: ie5setupbrowse.jpg (45.28 KiB) Viewed 89869 times

WinZip will extract the installation files and start the setup.

: ie5setup.jpg (58.7 KiB) Viewed 89869 times

Click "Next >" and accept the agreement. Click "Next >" again.
Use the default Full install and click "Next >".

: ie5setupfullinstall.jpg (61.88 KiB) Viewed 89869 times

Parameter	Project Type	Description
/p"password"	Basic MSI, InstallScript MSI	If you configured the password-related settings for your release on the Setup.exe tab in the Releases view, the end user must specify the password with the /p option when running the installation silently. A typical command is as follows: Setup.exe /s /p"password"
/r	InstallScript, InstallScript MSI	Use this command line to run the installation in record mode. In order to run an InstallScript MSI or InstallScript installation in silent mode, you must first run Setup.exe with the /r option to generate a response file, which stores information about the data entered and options selected by the user at run time. Launching an InstallScript MSI or InstallScript installation with the /r parameter displays all the run-time dialogs and stores the data in a file called Setup.iss, created inside the system’s Windows folder. To specify an alternative response file name and location, use the /f1 option, described below. Basic MSI projects do not create or use a response file for silent installations.
/s	Basic MSI, InstallScript, InstallScript MSI	For an InstallScript MSI or InstallScript project, the command Setup.exe /s runs the installation in silent mode, by default based on the responses contained in a response file called Setup.iss in the same directory. (Response files are created by running Setup.exe with the /r option.) To specify an alternative file name or location of the response file, use the /f1 option. The command Setup.exe /s also suppresses the Setup.exe initialization dialog for a Basic MSI installation, but it does not read a response file. To run a Basic MSI installation silently, use the following command line: Setup.exe /s /v/qn To specify the values of public properties for a silent Basic MSI installation, you can use a command such as the following one: Setup.exe /s /v"/qn INSTALLDIR=D:\Destination" Note • Using this command-line parameter to launch an installation that includes an InstallShield prerequisite does not automatically run the prerequisite installation silently. You may also need to specify a valid silent command-line parameter for the InstallShield prerequisite in the Specify the command line for the application when the setup is running in silent mode setting on the Application to Run tab in the InstallShield Prerequisite Editor. For more information, see Specifying Command-Line Parameters for an InstallShield Prerequisite.
/f1	InstallScript, InstallScript MSI	Using the /f1 option enables you to specify where the response file is (or where it should be created) and what its name is, as in the following example: Setup.exe /s /f1"C:\Temp\Setup.iss" Specify an absolute path; using a relative path gives unpredictable results. The /f1 option is available both when creating a response file (with the /r option) and when using a response file (with the /s option).
/f2	InstallScript, InstallScript MSI	When running an InstallScript MSI or InstallScript installation in silent mode (using the /s option), the log file Setup.log is by default created in the same directory and with the same name (except for the extension) as the response file. The /f2 option enables you to specify an alternative log file location and file name, as in the following example: Setup.exe /s /f2"C:\Setup.log" Specify an absolute path; using a relative path gives unpredictable results.

Parameter	Project Type	Description
/a	Basic MSI, InstallScript MSI	Note • The /a parameter does not work with Update.exe. Update.exe launches a patch that accesses and modifies an existing cached .msi file on the system, and an administrative installation does not cache the .msi file. The /a option causes Setup.exe to perform an administrative installation. An administrative installation copies (and uncompresses) your data files to a directory that is specified by the user, but it does not create shortcuts, register COM servers, or create an uninstallation log. Tip • If an installation contains InstallShield prerequisites and you want to extract them from Setup.exe, add a path after the /a parameter to extract the prerequisites to that location. A sample command is Setup.exe /a"C:\temp".
/j	Basic MSI, InstallScript MSI	The /j option causes Setup.exe to perform an advertised installation. An advertised installation creates shortcuts, registers COM servers, and registers file types, but does not install your product’s files until the user invokes one of these “entry points.”
/x	Basic MSI, InstallScript MSI	The /x option causes Setup.exe to uninstall a previously installed product.
/uninst	InstallScript, InstallScript MSI (if the InstallScript user interface (UI) style is the traditional style, which uses the InstallScript engine as an external UI handler)	Important • This parameter does not apply to InstallScript MSI projects in which the InstallScript UI style is the new style (which uses the InstallScript engine as an embedded UI handler). To learn more, see Using the InstallScript Engine as an External vs. Embedded UI Handler for InstallScript MSI Installations. The /uninst option is provided for compatibility with earlier versions of InstallShield. This option causes the InstallScript engine to execute the event handler function OnUninstall, whose default code uninstalls the previously installed product. Project • Note that in InstallScript MSI installations, the /uninst parameter does not invoke the InstallScript engine uninstall behavior that processes install log and removes any resources that were created and logged through script. However, the /removeonly option does invoke this behavior.
/removeonly	InstallScript, InstallScript MSI	The /removeonly option sets the REMOVEONLY system variable equal to a non-zero value. The default code for the OnMaintUIBefore event handler function conditionally displays the SdWelcomeMaint dialog, depending on the value of REMOVEONLY.
/instance=<InstanceId>	Basic MSI	The /instance=<InstanceId> option—which is available for Basic MSI projects that support the installation of multiple instances of a product—lets you specify which instance you want to install, update, or uninstall. <InstanceId> represents the value of the InstanceId property that identifies the instance. Whenever you use this option and include a valid InstanceId value, the installation suppresses the instance selection dialog. For example, the following sample command line installs the instance that has 2 as the value of the InstanceId property: Setup.exe /instance=2 Use default to identify the instance that is installed by the base installation package, as in the following example: Setup.exe /instance=default To specify the instance that you want to uninstall, include the /x option with the /instance=<InstanceId> option. For more information, see Naming an Instance and Run-Time Behavior for Installing Multiple Instances of a Product.

Parameter	Project Type	Description
/v	Basic MSI, InstallScript MSI	Use the /v option to pass command-line options and values of public properties through to Msiexec.exe. If you want to pass more than one argument to Msiexec.exe, you can use the /v option multiple times at the command line, once for each argument. For example: Setup.exe /v"/lv c:\test.log" /v"MYPROPERTY1=value1" /v"/qb" As an alternative, you can pass multiple arguments through the /v option as in the following example: Setup.exe /v"/lv c:\test.log MYPROPERTY1=value1 /qb" Note • If you pass the /v parameter at the command prompt when launching Setup.exe, any parameters that are specified for the CmdLine keyname in Setup.ini are ignored. To learn more, see Setup.ini.
/v"ISSCRIPTCMDLINE=\"<Option1> <Option2>\""	Basic MSI projects that have InstallScript custom actions	This option specifies command-line parameters to be passed to the script. Any property supported by InstallScript MSI (where appropriate) can be specified. (The most common ones are /d and /z.) For example, the following indicates that you want to debug the script, and that the CMDLINE variable should contain TEST. Setup.exe /v"ISSCRIPTCMDLINE=\"-d -zTEST\"" Note that as shown above, when you want to specify that a double quote character is not a delimiter for the command line but a delimiter for the property, use \". Note also that as with any public Windows Installer property, this property should be specified with all uppercase letters.
/z	InstallScript MSI	The /z option is used to pass data to the InstallScript system variable CMDLINE, as in the following example: Setup.exe /z"My Custom Data" When this command line is used, the variable CMDLINE contains the string My Custom Data.

Parameter	Project Type	Description
/ua /uw	Basic MSI, InstallScript MSI	In the Release Wizard, you can specify download locations for the Windows Installer installers InstMsiA.exe and InstMsiW.exe. A user can specify an alternative URL at run time using the /ua option (for the InstMsiA.exe location) and /uw option (for the InstMsiW.exe location), as in the following example: Setup.exe /uw"http://www.otherlocation.com/engines" The file name is not necessary. Note • You must specify the full URL with the parameters.
/um	Basic MSI, InstallScript MSI	In the Release Wizard, for a Web Downloader build, you can specify a download location for your .msi database. A user can specify an alternative URL using the /um option, as in the following example: Setup.exe /um"http://www.otherlocation.com/packages/product.msi" Note • You must specify the full URL with the parameter.
/b	Basic MSI, InstallScript MSI	In the Release Wizard, for a Downloader build, you can specify whether to cache the contents of a compressed package on the local system. With the /b option, the user can specify the directory in which to cache the installation files, as in the following example: Setup.exe /b"C:\CacheDirectory" Note • You must specify the full URL with the parameter.

Parameter	Project Type	Description
/d	Basic MSI projects with InstallScript custom actions, InstallScript, InstallScript MSI	For an InstallScript project, running the command Setup.exe /d runs the installation program with the InstallScript Debugger. Note • Debugging InstallScript code requires the debug-information file Setup.dbg to be available. In addition, in order to debug an installation on a system other than your development machine, you need to copy certain files from your development machine to the debugging machine. To learn more, see Debugging an Installation on Any Computer. For a Basic MSI project, the following command runs your InstallScript custom actions in the InstallScript Debugger: Setup.exe /v"ISSCRIPTDEBUG=1 ISSCRIPTDEBUGPATH=\"path-to-Setup.dbg\""
/debuglog	Basic MSI, InstallScript MSI	The /debuglog parameter lets you generate a log file for Setup.exe. To generate a log named InstallShield.log in the same directory as the Setup.exe file, pass just the command-line parameter. Note that this does not work if the Setup.exe file is in a read-only location. For example: setup.exe /debuglog To specify the name and location of the log file, pass the path and name, as in the following example: Setup.exe /debuglog"C:\PathToLog\setupexe.log" To generate a log file for the feature prerequisites in the installation, use the /v parameter to set the ISDEBUGLOG property to the full path and file name for the log file, as follows: Setup.exe /debuglog"C:\PathToSetupLogFile\setup.log" /v"ISDEBUGLOG=prereq.log" You can use directory properties and environment variables in the path for the feature prerequisite log file.

Befehl	Tastenkombination
Ausgewählten Inhalt kopieren	STRG + C
Ausgewählten Inhalt einfügen	STRG + V
Mehrfachauswahl	STRG + Maus
Alles markieren	STRG + A
Ausgewählten Inhalt ausschneiden	STRG + X
Rückgängig	STRG + Z
Wiederherstellen	STRG + Y
Neues Dokument/Fenster erstellen	STRG + N
Neuen Ordner erstellen	STRG + Shift + N
Vorhandene Datei öffnen	STRG + O
Zum Anfang des Dokuments wechseln	STRG + POS1
Zum Ende des Dokuments wechseln	STRG + ENDE
Suche im Dokument	STRG + F
Größe der Seite ändern (auszoomen/einzoomen)	STRG + Maus-Scrollrad
Cursor an den Anfang des vorherigen Wortes positionieren	STRG + ⇐
Cursor an den Anfang des nächsten Wortes positionieren	STRG + ⇒

Befehl	Tastenkombination
Taskmanager/Anmeldebildschirm aufrufen	STRG + ALT + ENTF
Geöffnete Windows-Anwendung wechseln	ALT + TAB
Windows-Anwendung wechseln (Rückwärts)	ALT + Shift + TAB
Geöffnetes Fenster minimieren	Windows + ⇓
Verkleinertes Fenster vergrößern	Windows + ⇑
Geöffnetes Fenster links anordnen	Windows + ⇐
Geöffnetes Fenster rechts anordnen	Windows + ⇒
Windows-Anwendungen wechseln mit 3D-Effekt	Windows + TAB
Alle auf der Taskleiste vorhandenen Fenster minimieren	Windows + M
Alle Fenster auf der Taskleiste minimieren bzw. diesen Vorgang rückgängig machen	Windows + D
Durch die Programme der Taskleiste navigieren	Windows + T
Rückwärts durch die Programme der Taskleiste navigieren	Windows + Shift + T
Fenster innerhalb der Anwendung wechseln (anwendungsspezifisch)	STRG + TAB
Fenster innerhalb der Anwendung wechseln	STRG + ⇑ + TAB
Fenster innerhalb der Anwendung schließen (anwendungsspezifisch)	STRG + F4
Fenster schließen	ALT + F4
Startmenü aufrufen	STRG + ESC
Taskmanager aufrufen	STRG + Shift + ESC
Ausführen	Windows + R
Computer sperren	Windows + L
Windows-Explorer öffnen	Windows + E
Windows-Suche öffnen	Windows + F
Präsentationsmodus	Windows + P
Systemeigenschaften öffnen	Windows + Pause
Kopiert Bildschirmfotos in die Zwischenablage	Windows + Druck
Kopiert Bildschirmfotos des aktiven Fensters in die Zwischenablage	Windows + ALT + Druck
Screenshot/Bildschirmaufnahme	Windows + Shift + S
Zwischenablage abrufen	Windows + V

Befehl	Tastenkombination
Neuen Tab öffnen	STRG + T
Aktuelle Seite als Lesezeichen speichern	STRG + D
Den geöffneten Tab schließen	STRG + W
Seite neu laden	STRG + R = F5
Mit dem Cursor in die Adresszeile gelangen	STRG + L
Ansicht vergrößern	STRG + +
Ansicht verkleinern	STRG + –

Befehl	Tastenkombination
Schriftgröße um einen Punkt verringern (nur bei Microsoft 365)	STRG + 8
Schriftgröße um einen Punkt vergrößern (nur bei Microsoft 365)	STRG + 9
Fett	STRG + Shift + F
Unterstreichen	STRG + Shift + U
Kursiv	STRG + Shift + K
Hochgestellt	STRG + +
Tiefgestellt	STRG + #
Geschütztes Leerzeichen	ALT + 0160
Gedankenstrich	ALT + 0150
Speichern	STRG + S
Speichern unter	STRG + ⇑ + S = F12
Drucken	STRG + P

Zeichen	Befehl	Tastenkombination
„	Anführungszeichen unten (öffnend)	Alt + 0132
“	Anführungszeichen oben (schließend)	Alt + 0147
‚	Anführungszeichen unten (einfach öffnend)	Alt + 0130
‘	Anführungszeichen oben (einfach schließend)	Alt + 0145
–	Gedankenstrich	Alt + 0150
’	Apostroph	Alt + 0146
[	Öffnende eckige Klammer	Alt Gr + 8
]	Schließende eckige Klammer	Alt Gr + 9
{	Öffnende geschweifte Klammer	Alt Gr + 7
}	Schließende geschweifte Klammer	Alt Gr + 0
\|	Senkrechter Strich	Alt Gr + <
\	Umgekehrter Schrägstrich (Backslash)	Alt Gr + ß
®	Registered Trademark	Alt + 0174
©	Copyright	Alt + 0169
™	Trademark	Alt + 0153
∗	Sternchen (Asterisk)	Shift + +
°	Gradzeichen	Shift + ^
∼	Tilde (mathematisch)	Alt Gr + +
π	Pi	Alt + 0227

Befehl	Tastenkombination
Schnellaufruf von Hilfestellungen	F1
Dateien umbenennen	F2
Suchfeld	F3
Aufrufen der Adresszeile im Internet-Explorer	F4
Aktualisiert die geöffnete Webseite im Browser	F5
URL in der Adresszeile markieren	F6
Funktioniert nur in Kombination mit anderen Tasten	F7
Abgesicherter Modus	F8
Funktioniert nur in Kombination mit anderen Tasten	F9
Menüleiste im Browser auswählen	F10
Vollbildmodus aktivieren	F11
Funktioniert nur in Office-Programmen	F12

Hersteller	Aufruf BIOS-Menü	Aufruf Boot-Menü
Acer	F2 oder ENTF	F12
ASRock	F2 oder ENTF	F11
ASUS	F2 oder F10	ESC
Dell	F2	F12
Fujitsu	F2	F12
Gigabyte	ENTF	-
HP	F2 oder F10	F9 oder ESC
Intel	F2	F12
Lenovo	F1	F12
Medion	F2	F10
Microsoft	Lauter und Power
MSI	ENTF	F11
Samsung	F2	ESC
Sony	F2	F11
Terra	F2	F7
Toshiba	Starten mit ESC gedrückt, dann F1	F12
Zotac	ENTF	F12

Windows

Installer-Krams

Microsoft Standard Installer Command-Line Optionen

/help

Beispiele

/quiet

Beispiele

/passive

Beispiele

/norestart

Beispiele

/forcerestart

Beispiele

/promptrestart

/deinstallieren (Produkt)

Parameter

/uninstall (Patch)

Parameter

/log

/package

Parameter

/update

Parameter

Empfohlener Inhalt

Befehlszeilenoptionen - Win32 apps

Befehlszeilenoptionen, die von Self-Extractor-Paketen unterstützt werden - Windows Client

ALLUSERS-Eigenschaft - Win32 apps

Debuggen von Systemfehlercodes

Weitere Möglichkeiten zum Suchen eines Fehlercodes

Fehlercodes von Drittanbietern

Systemfehlercodes

Setup.exe and Update.exe Command-Line Parameters

Backup and Restore Office 2016 / 2019 Activation

Drucker-Krams

Drucker vollständig entfernen

Drucker installieren inklusive Treiber mit PowerShell

Freigegebenen Drucker eines Printservers installieren

Lokalen Drucker installieren mit PowerShell

Treiber zu Store hinzufügen

Drucker-Treiber installieren

Drucker-Port erstellen

Drucker installieren

Beep Code des BIOS

Windows 10 Benutzerprofile sauber löschen

Dies und das

Windows 11 ohne Microsoft-Konto

Schortcuts

1. Unbekannte Shortcuts/Tastenkombinationen

2. Die wichtigsten Shortcuts für effiziente Büroarbeit

3. Tastaturkürzel für Windows-Nutzer

4. Shortcuts für den Browser

5. Tastenkombinationen zur Dokumentbearbeitung

6. Shortcuts für (Sonder)-Zeichen

7. Die F-Tastenkombinationen

8. Mit einem Shortcut überall Emojis einfügen können

9. Anwendung von Shortcuts im Alltag

Video-Anleitung zu den 7 erstaunlichsten Tastenkombinationen

Inhalt dieses Video-Tutorials:

10. Der Unterschied zwischen CTRL- und der STRG-Taste

Bios F-Tasten

Win3.11

DosBox, Windows 3.11 & Games

DosBox installieren

Laufwerk anlegen und einbinden

Windows 3.11 installieren

Mamba auf das Laufwerk auf und starten

Tutorial: Installing Windows 3.11 with (working) drivers! [Updated]

Proxy setzen

Windows: Proxy-Server-Einstellungen per Skript setzen

Gruppenrichtlinie

Befehl

Registry

Skript

Weiteres

Automatisch per WPAD

Vorsicht Falle!

Quellen

Windows 11-Installationsmedium mit Tiny11 abspecken

Certutil