CONTACTS 
0201 - Microsoft Corporation              Telephone
020101 - Mr. Mike NLN; Technician; MS Dos Support  800 936 5700 (costs $35)

SUBJECTS
Corps of Engineers, SFD
Installation, Mouse, Network
Windows 3.1
Mouse Fails in SDS under Windows, MS Incident:  19112701

0806 -    ..
0807 - Summary/Objective
0808 -
080801 - Followed up work at ref SDS 8 line 48, ref SDS 7 line 41, re
080802 - line 29, ref SDS 4 line 48, ref SDS 3 line 40, ref SDS 2
080803 -
080804 - Tried idea from Morris the other day, ref SDS 8 line 144, except I
080805 - did not re-run "setup" from the Windows subdirectory.
080806 -
080807 -
080808 -
0809 -
0810 -
0811 - Progress
0812 -
081201 - Still wasn't able to get the mouse to work in Windows for SDS.
081202 -
081203 - I tried Morris' idea of ensuring compatibility between mouse driver in
081204 - autoexec.bat and in Windows.  I have put Tom's original win.ini and
081205 - system.ini in the directories:
081206 -
081207 -     f: 04 00065 00 MD KC system.org   Tom's original system.ini
081208 -     f: 04 00065 00 MD KC win.org      Tom's original win.ini
081209 - ..
081210 - I put the system.ini and win.ini as I have modified them to try
081211 - to get the mouse to run in SDS in the following directories on CPU #8
081212 - for analysis:
081213 -
081214 -     f: 04 00065 00 MD KC system.rod   Tom's original system.ini
081215 -     f: 04 00065 00 MD KC win.rod      Tom's original win.ini
081216 -
081217 -        ...there is actually no change to win.ini, but we track it to
081218 -        ensure common treatment to configuring the computer.
081219 -
081220 - I put the autoexec.bat and config.sys files as I have modified them to
081221 - try to get the mouse to run in SDS in the following directories on CPU
081222 - #8 for analysis:
081223 -
081224 -     f: 04 00065 00 MC CC AUTOEXEC.TOM   Autoex by Rod with mouse driver
081225 -     f: 04 00065 00 MC CC CONFIG.TOM     Config by Rod with mouse driver
081226 -
081227 -        ...there is actually no change to config.sys, but we track it
081228 -        to ensure common treatment to configuring the computer.
081229 -
081230 - ..
081231 - Below is the configuration we have now on Tom's computer.  The
081232 - mouse seems to run everything as it did before, except it will not run
081233 - in SDS.
081234 -
081235 -
081236 -
0813 -
0814 -
0815 - AUTOEXEC.TOM
0816 -
081601 - This is a file I created from the original autoexec.bat file on Tom's
081602 - computer to call the mouse driver I have been using so the mouse will
081603 - run in SDS.
081604 -
081605 - Line 3 has following:
081606 -
081607 -            set mouse=C:\00\013
081608 -            C:\00\013\mouse.exe                   93246  93-08-16
081609 -
081610 -
081611 -
0817 -
0818 -
0819 - ėR551 SYSTEM.ROD
0820 -
082001 - Line 10 has following line:
082002 -
082003 -                     mouse.drv=mouse.drv
082004 -
082005 -      ...this is the same command as in my system.ini, and I copied
082006 -
082007 -                h: 00 02 system mouse.drv         10672  93-12-31
082008 -
082009 -      ... from my CPU #9 to Tom's computer in the following
082010 -      directory:
082011 -
082012 -                c: windows system mouse.drv
082013 - ..
082014 - There is nothing apparent about how the program knows where
082015 - mouse.drv is located, but I assume the program is coded to look for it
082016 - in the system subdirectory of the Windows main directory, wherever
082017 - that happens to be.
082018 -
082019 -
082020 -
082021 -
0821 -
0822 -
0823 - WIN.ROD
0824 -
082401 - Line 10 - this has no call of any kind I can find to a mouse driver.
082402 -
082403 -    When I installed the mouse program from within Windows using the
082404 -    File "Run" operation on...
082405 -
082406 -                         c: 00 013 install.exe
082407 -
082408 -       ...that operation created the following line in win.ini
082409 -
082410 -          load=C:\00\013\POINTER.EXE M:\KEYVIEW\kwldmgr.exe
082411 -    ..
082412 -    That line however, is not in win.ini for my Winodws program,
082413 -    so I commented it out.  Moreover, when it was plugged in, it didn't
082414 -    do any good.  Unplugging it seems to have no effect on the
082415 -    performance of the mouse.
082416 -
082417 -    So the net effect is that there is nothing in win.ini about
082418 -    running the mouse.
082419 -
082420 -
082421 -
082422 -
082423 -
0825 -
0826 -
0827 - 2034 call Microsoft
0828 -   ..
082801 - It costs $35 per incident; used MBNA:
082802 -
082806 -
082807 - Talked to Marlie - a girl.
082808 -
082809 - Talked to Robert.               Incident:  19112701
082810 -
082811 -    He thinks the pif file may be incorrect.
082812 -
082813 -    To test this idea, we can run the SDS application, do "FILE," then
082814 -    RUN, and type
082815 -
082816 -                           command
082817 -
082818 -    press enter to DOS prompt and try to run SDS in this mode.
082819 -    ..
082820 -    If we have the mouse, it means the pif file is incorrect.
082821 -
082822 -    Robert thinks the problem is a memory conflict.  He indicated that
082823 -    Windows trys to load the mouse driver into upper memory.  We need
082824 -    to make sure we have allocated some upper memory for this.  I may
082825 -    have set everything to 0.
082826 -
082827 -    Other than that, there is nothing in the pif file about the mouse.
082828 -
082829 -    Try copying default pif file to the SDS.pif name.  This provides
082830 -    several parameters that we know are correct.
082831 -
082832 -    Actually, it does not seem very promising.  I tried it on CPU #9
082833 -    which has win3.1 by changing the only memory parameter and it did
082834 -    not affect the use of the mouse.  I set the value to 0, and the
082835 -    mouse still ran.
082836 -
082837 -
082838 -
082839 -
082840 -
0829 -