os2sdk/os2doc/read.me! - annotate

Return to read.me! CVS log

Up to [OS/2 SDKs] / os2sdk / os2doc

Annotation of os2sdk/os2doc/read.me!, revision 1.1.1.1

1.1 root 1: All documentation has been moved to the C binaries diskette under the
2: OS2DOC subdirectory.
3:
4: Problems:
5:
6: Information about this release of the MS OS/2 SDK release can be obtained
7: from the DIAL bulletin board. Below are some last minute caveates:
8:
9: Binary and Dyna-Link Libraries (DLL) must be from the same version. DO
10: NOT MIX VERSIONS !
11:
12: There are three install programs - INSTAID, INSTIBM and INSTMS. What is
13: the difference between these three ?
14:
15: All three install programs generate compatible versions of MS OS/2.
16: The difference lies in the names of the directories created and the
17: location of the system files. The MS OS/2 installation program, INSTAID
18: (misnamed INSTALL in the documentation) and INSTIBM create two
19: directories, OS2 and SPOOL, then copies system files to OS2 and the
20: root directory.
21:
22: The alternate install, INSTMS, creates several additional directories
23: and distributes the various files among them. This configuration is
24: recommended for application program developers. The directories created
25: by this method are described in the Microsoft Operating System/2 Setup
26: Guide.
27:
28: I have a PS/2 machine and when booting from the Installation Diskette the
29: machine just freezes. What's the deal ?
30:
31: If you have a PS/2 machine with an ESDI hard disk (i.e. 71MB or larger)
32: the default disk driver must be changed. You simply copy the Disk01.ESD
33: to Disk01.SYS and then re-boot the machine. The bottom line is that
34: if you have a low level formatted hard disk and try the instaid program
35: with the wrong disk device driver your machine will freeze.
36:
37: When I installed the latest release of OS/2 with the dual boot option
38: the autoexec.bat file is not executed when I switch to the 3.x box
39: for the first time. What gives?
40:
41: With Dual boot, to avoid conflicts, the names of Config.Sys and
42: Autoexec.Bat are changed to Config.OS2 and Autoexec.OS2. This
43: can be overcome by copying the parts of Autoexec.Bat that you
44: desire into the Autoexec.OS2.
45:
46: When running Win 2.0 in the 3.x box, Terminal, the Win 2.0 disktop
47: app, cannot connect to COM1. I get a message from the app stating
48: it can't connect. However, if I use another Async comm product it
49: does work. Ideas?
50:
51: There is a little utility called SETCOM40 that (dis/en)ables the
52: comm ports for the real mode box. Other programs are probably
53: rude and don't follow the protocol to determine if the port is in
54: use or not.
55:
56:
57: I have an EGA card listed with in the MS OS/2 SDK installation notes, yet
58: my machine doesn't run OS/2 correctly, what is the problem.
59:
60: If you're experiencing EGA problems with a valid EGA card call
61: manufacturer to determine if EGA ROMS are up to date.
62:
63: The installation guide is confusing, can you give me three easy steps to
64: installing the SDK?
65:
66: Sure. First, put the program diskette into your machine and reboot it.
67: Follow the instructions. If you have a new machine, first format the
68: hard drive, then reboot with the program diskette.
69:
70: Second: copy the files \OS2DOC\INPUT.EXE and \OS2DOC\INSTSDK.CMD from the
71: TOOLKIT diskette to the root of your hard drive. Run the program INSTSDK
72: and answer its questions.
73:
74: Thats, all.
75:
76: I selected the root directory for installing the SDK portion of this kit.
77: All of the directories were built, however none of the files were copied
78: there. What gives?
79:
80: The installation script has a bug. If you are in a subdirectory and
81: specify the root of your hard drive it will make the directories in the
82: correct place, but copy the files to the directory that you are in.
83:
84: When I created the SDK with the INSTSDK.BAT using DOS, the OS2INIT.CMD
85: contains real mode paths. What's the deal ?
86:
87: Command mode batch processing does not allow for very elegant parsing
88: of the environment. As a result, you will have to edit the resulting
89: autoexec to remove real mode references. A second alternative is to
90: install the SDK using OS/2.
91:
92: Some of my demo programs that worked with the previous SDK now die with a
93: stack fault.
94:
95: The minimum thread stack recommended is 2KB. More is needed if you
96: use the stack very much.
97:
98: The C compiler can't find libraries
99:
100: C compiler libraries have to be built before linking will work. See the
101: hard copy readme included with this kit. Execute the program LIBBUILD
102: without any command line arguments for instructions on how to build
103: libraries. The procedure to build all models with the floating point
104: emulator is as follows:
105:
106: 1. make sure your os2init.cmd file is set up per the installation notes.
107: 2. cd to the library directory
108: 3. enter the following command:
109:
110: for %i in (s m c l) do libbuild %i em %LIB%
111:
112: Libbuild will create the libraries needed by the C compiler for the
113: (s)mall, (m)edium, (c)ompact and (l)arge models with the floating point
114: (em)ulator package.
115:
116:
117: PS doesn't run, I get a system fault.
118:
119: PS and profiling will GP fault unless the developers kernel is installed.
120: See the relevant sections of the hard copy readme.
121:
122: MS OS/2 clobbered my MS-DOS system
123:
124: When using the MS installation aid and setting a dual boot configuration
125: if you try to re-install, you will clobber the previous dual boot
126: information. I.E. it won't work. To preserve your original version of
127: dos, re-sys dos to the hard drive, then re-install OS/2 using the
128: installation aid and select dual boot.
129:
130: My bound programs don't run anymore
131:
132: Tools and utilities that were bound (BIND) with the previous SDK may
133: not load and execute on this version of OS/2. The fix is to simply
134: recompile and bind the executable.
135:
136: How can I get my environment set in new screen groups?
137: Programs started by the program selector have no environment set.
138: My program cannot be started from the program selector.
139:
140: When you "start" a new screen group the file "os2init.cmd" is run by
141: the CMD processor. You can put your environment initalization stuff
142: in there.
143:
144: If you are starting a program from the program selector, the file os2init
145: is not run by the CMD processor. The way around this is to leave the
146: pathname name blank and put the following line in the argument line
147:
148: TITLE foo application
149:
150: PATHNAME C:\CMD.EXE (This could be left blank)
151:
152: PARAMETERS /c c:\os2init & foo.exe
153:
154: If you put '@echo off' as the first line in os2init.cmd this
155: all works really nicely.
156:
157: What is a Matrox disk drive?
158:
159: Oops, that was intended to be Maxtor.
160:
161: The color switches for the editor SDKED have changed, what are they?
162:
163: The editor has changed radically, the color switches are completely
164: different. all are just standard hex attribute bytes now, i.e. "0F" is
165: black background, intense white forground.
166:
167: ; error color
168: errcolor:c
169: ; color of current window "foreground color"
170: fgcolor:1A
171: ; color of "highlight" in searching
172: hgcolor:21
173: ; "information" color on status line, textarg color
174: infcolor:
175: ; "status" color
176: stacolor:0F
177: ;
178:
179: Confidence Testing Corrections
180:
181: Step 7 : Select the MS-DOS Command Prompt, not COMMAND.COM as indicated.
182:
183: Step 11: Select OS/2 Comand Prompt 1, not THREADS Screen Group, as
184: indicated.

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.