Microsoft KB Archive/104001

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:47, 20 July 2020 by X010 (talk | contribs) (Text replacement - ">" to ">")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)



Network Installation of MSDL Video Drivers

Last reviewed: November 21, 1994
Article ID: Q104001



The following information applies to:

  • Microsoft Windows operating system versions 3.1, 3.11
  • Microsoft Windows for Workgroups versions 3.1, 3.11

SUMMARY

This article lists the steps needed to install a video driver from the Microsoft Download Service (MSDL) on a network installation of Windows or Windows for Workgroups.

NOTES

  • In this example, the SETUP /A (the network administrative setup) is set up to F:\WINSHARE and the SETUP /N (network node setup) is set up to the user's local hard disk in the C:\WIN31 directory and the video driver from the MSDL is S3.EXE. Replace these directory names and driver names with the names specific to your installation.
  • This procedure does NOT apply to network MSDL printer driver installations.

MORE INFORMATION

  1. Log on as Supervisor or Administrator (or an equivalent with FULL rights) to the workstation that requires the upgraded video driver.
  2. Go to the WINSHARE directory on drive F.
  3. Create a subdirectory called S3 and then change to that subdirectory.
  4. Copy the file S3.EXE to the S3 subdirectory (F:\WINSHARE\S3), type "S3" (without the quotation marks) to extract the files, then delete the file S3.EXE.
  5. Ensure that the PATH statement in the AUTOEXEC.BAT file (or in your login script) is correct. It should be similar to the following:

    path=c:\win31;f:\winshare;c:\dos

  6. Use the EXPAND command in the Windows directory to decompress all the files in the S3 subdirectory by typing:

    expand -r *.*

  7. Delete the uncompressed files by typing:

    del *.??_

  8. Rename the expanded files by typing the following (in the given order), pressing ENTER after each line:

    ren *.fo *.fon ren *.lg *.lgo ren *.38 *.386 ren *.rl *.rle ren *.?g *.?gr ren *.dr *.drv

  9. Copy the OEMSETUP.INF file to the root directory of drive C and delete the OEMSETUP.INF file in the S3 subdirectory.
  10. Change to the WINSHARE subdirectory and remove the read-only attribute on the files in the WINSHARE subdirectory by typing the following at the F:\WINSHARE prompt:

    attrib -r *.*

    NOTE: It may also be necessary to take off any network-specific flags.

  11. Change to the S3 subdirectory and copy all the files from the S3 subdirectory to the WINSHARE subdirectory as follows:

    copy *.* \winshare

  12. Delete the files in the S3 subdirectory with the following command:

    del *.*

  13. Type the following command:

    copy c:\oemsetup.inf f:\winshare\s3

  14. Type the following command:

    del c:\oemsetup.inf

  15. Change to the WINSHARE subdirectory and make the files in the WINSHARE subdirectory read-only by typing the following:

    attrib +r *.*

    NOTE: It may also be necessary to replace any network-specific flags.

  16. Change to the WIN31 subdirectory.
  17. Run Setup and choose Display, then select "Other (Requires Disk Provided by a Hardware Manufacturer)." When prompted for the location of the files, type "f:\winshare" (without the quotation marks) and choose the appropriate driver from the list that appears.

    This ends Setup, returns you to the C:\WIN31 directory, and creates an OEM0.INF file. If you install more than one MSDL driver, the OEM<#>.INF file is incremented (for example, OEM1.INF, OEM2.INF, and so on).

  18. Restart Windows.



KBCategory: kbnetwork kbdisplay kbsetup

KBSubcategory: win31 wfw wfwg windrvr
Additional reference words: 3.10 3.1 3.11 install installation setup
setting up net network setup /a setup /n display


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 21, 1994
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.