home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
oswafild.txt
< prev
next >
Wrap
Text File
|
1997-02-03
|
2KB
|
63 lines
OSWAFILD - OS/2 FOR WINDOWS FILE-DEPENDENCY REQUIREMENTS
01/30/96
=======================================================================
OS/2 for Windows File-Dependency Requirements
All OS/2 Releases
=======================================================================
Please Read Entire Document for Full Explanation of Procedures
--------------------------------------------------------------
DESCRIPTION
OS/2 for Windows requires that files have an exact size. If any of the
files differ, the installation process does not generate an error, and
the Program Manager will not load. This is a dependency requirement for
the Windows system to load.
RESOLUTION
Compare Windows system files to the file sizes listed below.
System Files
------------
These need to be dated 3-10-92:
KRNL386.EXE 75490 bytes
GDI.EXE 220800 bytes
USER.EXE 264016 bytes
WINFILE.EXE 146864 bytes
CONTROL.EXE 15872 bytes
COMM.DRV 9280 bytes
MOUSE.DRV 10672 bytes
TIMER.DRV 4192 bytes
VGA.DRV 73200 bytes
8514.DRV 92032 bytes
COM Files
---------
The .COM files listed are necessary to start Windows or to launch a
WIN-OS/2 Full Screen session. WIN.COM and WINOS2.COM should be the same
size. WINDOS.COM is larger, because it becomes WIN.COM when DOS is
started.
These need to be dated 10-20-93:
WIN.COM 25640 bytes
WINOS2.COM 25640 bytes
This file becomes WIN.COM when started in DOS.
WINDOS.COM 44170 bytes
______________________________________________________________________
IBM disclaims all warranties, whether express or implied, including
without limitation, warranties of fitness and merchantability with
respect to the information in this document. By furnishing this
document, IBM grants no licenses to any related patents or copyrights.
Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product
or brand names referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark
information.