doc: os_win32: More cleanup #3884

Follow-up to ee1f8ea

Roger Knobbe is still mentioned in intro.txt, for anyone wondering.

1 files changed, 1 insertions, 38 deletions

diff --git a/runtime/doc/os_win32.txt b/runtime/doc/os_win32.txt
index 2ee9c6d3c7..57a6ad9f3a 100644
--- a/runtime/doc/os_win32.txt
+++ b/runtime/doc/os_win32.txt
@@ -7,7 +7,7 @@
 						*win32* *Win32* *MS-Windows*
 This file documents the idiosyncrasies of the Win32 version of Vim.
 
-The Win32 version of Vim works on Windows NT, XP, Vista and Windows 7.
+The Win32 version of Vim works on Windows XP, Vista and Windows 7.
 There are both console and GUI versions.
 
 The 32 bit version also runs on 64 bit MS-Windows systems.
@@ -33,7 +33,6 @@ Win32 GUI			|gui-w32|
 
 Credits:
 The Win32 version was written by George V. Reilly <george@reilly.org>.
-The original Windows NT port was done by Roger Knobbe <RogerK@wonderware.com>.
 The GUI version was made by George V. Reilly and Robert Webb.
 
 ==============================================================================
@@ -105,14 +104,6 @@ A. In the GUI version, you can use the 'guifont' option.  Example: >
 <  In the console version, you need to set the font of the console itself.
    You cannot do this from within Vim.
 
-Q. How do I type dead keys on Windows NT?
-A. Dead keys work on NT 3.51.  Just type them as you would in any other
-   application.
-   On NT 4.0, you need to make sure that the default locale (set in the
-   Keyboard part of the Control Panel) is the same as the currently active
-   locale.  Otherwise the NT code will get confused and crash!  This is a NT
-   4.0 problem, not really a Vim problem.
-
 Q. I'm using Vim to edit a symbolically linked file on a Unix NFS file server.
    When I write the file, Vim does not "write through" the symlink.  Instead,
    it deletes the symbolic link and creates a new file in its place.  Why?
@@ -147,28 +138,6 @@ A. Basically what you need is to put a tee program that will copy its input
 	:set shellpipe=\|\ tee
 <  to your _vimrc.
 
-Q. I'm storing files on a remote machine that works with VisionFS, and files
-   disappear!
-A. VisionFS can't handle certain dot (.) three letter extension file names.
-   SCO declares this behavior required for backwards compatibility with 16bit
-   DOS/Windows environments.  The two commands below demonstrate the behavior:
->
-	echo Hello > file.bat~ 
-	dir > file.bat
-<
-   The result is that the "dir" command updates the "file.bat~" file, instead
-   of creating a new "file.bat" file.  This same behavior is exhibited in Vim
-   when editing an existing file named "foo.bat" because the default behavior
-   of Vim is to create a temporary file with a '~' character appended to the
-   name.  When the file is written, it winds up being deleted.
-
-   Solution: Add this command to your _vimrc file: >
-	:set backupext=.temporary
-
-Q. How do I change the blink rate of the cursor?
-A. You can't!  This is a limitation of the NT console.  NT 5.0 is reported to
-   be able to set the blink rate for all console windows at the same time.
-
 							*:!start*
 Q. How can I run an external command or program asynchronously?
 A. When using :! to run an external command, you can run it with "start": >
@@ -211,12 +180,6 @@ A. You have two possible solutions depending on what you want:
 <  The first command runs notepad minimized and the second one runs it
    normally.
 
-Q. I use Vim under Win32s and NT.  In NT, I can define the console to default to
-   50 lines, so that I get a 80x50 shell when I ':sh'.  Can I do the same in
-   W3.1x, or am I stuck with 80x25?
-A. Edit SYSTEM.INI and add 'ScreenLines=50' to the [NonWindowsApp] section.  DOS
-   prompts and external DOS commands will now run in a 50-line window.
-
 						*windows-icon*
 Q. I don't like the Vim icon, can I change it?
 A. Yes, place your favorite icon in bitmaps/vim.ico in a directory of