CONTACTS 
0201 - Microsoft Corporation              Telephone
020101 - Mr. Philip NLN; Technician =900 896 9000
020102 - MS Dos Support  206 646 5108 (costs $25)

SUBJECTS
Kwan Henmi SDS
Develop & Maintain Hardware System
Eliminate Quicken from Windows
Program Manager

0506 -    ..
0507 - Summary/Objective
0508 -
050801 - Investigated SDS record on Denis' Windows problem at ref SDS 8 line
050802 - 130912.
050803 -
050804 - Looks like we can investigate all *.ini files to see where quicken
050805 - might be specified.  Actually, it seems we just need to delete the
050806 - stuff from progman, and change the names of the files quicken.grp, per
050807 - ref SDS 5 line 125.
050808 -
050809 -
0509 -
0510 -

SUBJECTS
Kwan Henmi SDS
Screen Delayed in Reports, under Windows
Config.sys (himem.sys /m:n)
Mouse, Microsoft v. 8.20a, 920710
Supersort, 910306
SDS Reports Slow under Windows

0909 - Summary/Objective
0910 -
0911 - 0831 Called DOS Support
0912 -
091201 - This follows up problem on Denis' computer at ref SDS 8 line 41.
091202 -
091203 - Could not get through to Windows Support, so called DOS support for
091204 - $25.  This took about an hour on the phone, but we may have solved it.
091205 -
091206 -     I accept this charge as part of installation expense.
091207 -
091208 - Phil suggested we change config.sys, and it seems to have eliminated
091209 - the screen referesh delay in Windows on my computer.  I tried several
091210 - File Access operations, and there was no delay.  Turned out later
091211 - though that there remained a problem with SDS reports which required
091212 - further adjustment, reported in the record visiting Kwan Henmi's
091213 - office. ref SDS 9 F59K
091214 -
091215 -
091216 -  ..
0913 -
0914 -
0915 - config.sys
0916 -
091601 - Line 1 - This formerly read:
091602 -
091603 -                DEVICE=H:\00\02\HIMEM.SYS /M:11
091604 -
091605 -   ...Phil suggested trying:
091606 -
091607 -
091608 -                DEVICE=H:\00\02\HIMEM.SYS /M:1
091609 -
091610 - Phil said "/M:n" controls the timing for the "A20" gate (switch), i.e.
091611 - the speed at which it is accessed.  He referred to the DOS 5.0
091612 - manual, which says on page 611:
091613 -
091614 -    /machine:xxx
091615 -
091616 -      Specifies the A20 handler to be used.  An A20 handler is a part
091617 -      of your computer that gives it access to the high memory area.
091618 -      The xxxx value can be any of the following codes or their
091619 -      equivalent numbers:
091620 -
091621 - This suggests /m:n, also relates to memory addresses.
091622 -
091623 - Phil suggested the /m:11 param we had previously specified may have
091624 - been in conflict with another device driver.  We have to experiment to
091625 - find one that works best with the configuration for each computer.
091626 - The options for IBM compatible machines are shown on DOS 5.0 Manual
091627 - page 611, as:
091628 -
091629 -                         m:1
091630 -                         m:11
091631 -                         m:12
091632 -                         m:13
091633 -
091634 -    ...Phil said m:1 is the system default.  In that case why can't we
091635 -    just eliminate the call entirely.
091636 -
091637 -
091638 -    History of /m:n Application
091639 -
091640 -    On 920428 tried "/m:11" orginally because of delayed performance of
091641 -    function keys. ref SDS 1 NL6N
091642 -
091643 -    On 920517 tried eliminating "/m:11"  ref SDS 2 0001
091644 -
091645 -    On 920612 tried "/m:n"  ref SDS 3 TO7H
091646 -
091647 -    On 920629 summary of history on m:n issue. ref SDS 4 MD8A
091648 -
091649 -
091650 - It is not clear that we may still not have a memory conflict in some
091651 - other aspect of the program.  I sure like the effect for now of this
091652 - solution though.  Tried scanner, and it seems to work okay.  Not sure
091653 - about the tape drive and modem.
091654 -
091655 - Tape drive worked, but the mouse does not work in SDS running from
091656 - DOS prompt.  This is not a big problem for me, but for others???
091657 -
091658 - Tried warm boot.  This brought the mouse back in SDS at DOS prompt.
091659 - Looks like mouse only crashes in SDS, after exiting from Windows.
091660 -
091661 -
091662 - Slight Mouse Problem
091663 -
091664 - Tried Windows, and still have the mouse.  Exited from Windows, and
091665 - called SDS, no mouse.
091666 -
091667 -    The mouse works under this configuration when DOS is first
091668 -    started, and it works in Windows.  The only time there is a
091669 -    problem is in DOS after closing Windows.
091670 -
091671 -
091672 -
091673 -
0917 -
0918 -
0919 - 1715 Further Research
0920 -
092001 - As a result of problem encountered at Denis' office today where SDS
092002 - reports are hanging the system, ref SDS 9 F59K, I did some SDS reports
092003 - on CPU #3 under Windows and got same results.  This means the /m:1
092004 - param on himem.sys is not a complete solution.
092005 -
092006 - Examined entire section in DOS 5.0 manual for himem.sys, and found on
092007 - page 610, the following:
092008 -
092009 -    HIMEM.SYS manages programs' use of extended memory and of the high
092010 -    memory area (HMA). This prevents programs from simultaneously using
092011 -    the same area of memory. You install the HIMEM.SYS device driver by
092012 -    adding a device command for it in your CONFIG.SYS file. The device
092013 -    command for HIMEM.SYS must precede any device commands for programs
092014 -    or device drivers that use extended memory (such as SMARTDRV.SYS,
092015 -    RAMDRIVE.SYS, and EMM386.EXE). For an introduction to using
092016 -    extended memory, see Chapter 12, "Optimizing Your System."
092017 -
092018 -      Syntax
092019 -
092020 -        device=[drive:][path]himem.sys [/hmamin=m] [/numhandles=n]
092021 -        [/int15=.r.rrx] [/machine:xxxx] [/a20control:onloff]
092022 -        [/shadowram:onloff] [/cpuclock:onloff]
092023 -
092024 -
092025 -      Switches
092026 -
092027 -        /hmamin=n
092028 -
092029 -           Specifies the amount of memory (in kilobytes) a program must
092030 -           use before HIMEM.SYS permits the program to use the high
092031 -           memory area. Valid values for m are in the range O through
092032 -           63. The default value is 0.
092033 -
092034 -        /numhandles=n
092035 -
092036 -           Specifies the maximum number of extended-memory-block (EMB)
092037 -           handles that can be used simultaneously. Valid values for n
092038 -           are in the range I through 128. The defauit value is 32.
092039 -           Each additional handle requires an additional 6 bytes of
092040 -           resident
092041 -
092042 -        /intl5=xxxx
092043 -
092044 -           Allocates the specified amount of extended memory (in kilo-
092045 -           bytes) for the interrupt 15h interface.  Some older programs
092046 -           use a conflicting extended-memory scheme.  To use memory
092047 -           allocated by this switch, programs must recognize VDisk
092048 -           headers.  To ensure enough memory is available, add 64 to
092049 -           the value you want to specify for xxxx. Valid values for
092050 -           xxxx are in the range 64 through 65535. If you specify a
092051 -           value less than 64. the value becomes 0.  The default value
092052 -           is 0.
092053 -
092054 -
092055 -  ..
092056 - Supersort May Be Problem
092057 -
092058 - The explanation for "/int15=xxxx," suggested that Supersort may be
092059 - hanging the program.  It is common to both File List and SDS reports
092060 - operations, and was developed in the early 1980's.  Tried following
092061 - change to config.sys:
092062 -
092063 -
092064 -            DEVICE=H:\00\02\HIMEM.SYS /int15=128 /M:11
092065 -
092066 -    DOS manual says the param should be applied with increments of 64,
092067 -    so just tried 128, i.e. 2 x 64.  There is no information on
092068 -    choosing a particular increment from 64 to 65535, so it is nothing
092069 -    more than a guess.
092070 -
092071 -
092072 - Solution
092073 -
092074 - After making the above change, tested File List and SDS Reports, and
092075 - both return a screen immediately.  Have done some scanning and other
092076 - applications in SDS and through other programs.  Everything seems to
092077 - work.
092078 -
092079 -    Failure
092080 -
092081 -    Actually, this solution does not seem to be permanent.
092082 -
092083 -    [On 930427 experience over the next several days showed it only
092084 -    supports limited number of reports. ref SDS 10 0001
092085 -
092086 -
092087 -
092088 -
092089 -
092090 -
0921 -
0922 -

SUBJECTS
DNRC
Develop & Maintain Hardware System

1005 - Summary/Objective
1006 -
100601 - Discussed with Phil, Wayne's problem getting mouse to work with the
100602 - ethernet card.  Phil reminded me of following command in DOS 5.0:
100603 -
100604 -                       msd
100605 -
100606 - This shows irq assignments.  The mouse in my machine, CPU #3, is
100607 - assigned to IRQ 2, because it is a bus mouse.  This seems similar to
100608 - the idea Wayne mentioned where Jack is intending to try DOS 6.0 to
100609 - figure out IRQ assignments, ref SDS 7 line 121409.
100610 -
100611 - He generally agreed with the idea that the mouse does not know the
100612 - Ethernet card is there, and so is using an address it needs, ref SDS 6
100613 - line 122606. Phil will send Wayne via fax some ideas on solving this
100614 - problem.
100615 -
100616 - I called for Wayne and spoke to Patty.  She said Wayne is at the
100617 - Governor's office until noon.  I advised that Microsoft is sending
100618 - Wayne a fax with ideas to solve his configuration problem, last
100619 - discussed at, ref SDS 7 line 121403.
100620 -
100621 -
100622 -
100623 -
1007 -
1008 -