THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700


S U M M A R Y


DIARY: February 27, 2001 07:14 AM Tuesday; Rod Welch

Microsoft unable to solve w2k problem on inconsistent memory.

1...Summary/Objective
.....KM Causes Resistance to Investing Intellectual Capital
.....Microsoft Support Provides Reliable Applications
.....Solution May Not be Possible


..............
Click here to comment!

CONTACTS 
0201 - Microsoft Corporation                Telephone
020101 - Mr. Joe NLN; DOS Engineer =704 582 8692
020102 - joegr@microsoft.com
020103 - Windows 2000 Support  =800 936 4900
020104 - Applications and Performance
0202 - Microsoft Corporation                Telephone
020201 - Mr. Einar Ekholm; Technician =425 635 2997 x32383
020202 - v-1eekh@mssupport.microsoft.com
020203 - Windows 2000 Support  =800 936 4900
020204 - Applications and Performance

SUBJECTS
SDS and Medit
Performance Slower for SDS Reports than C11
Config.nt in 00 02 System32, 010202
Autoexec.nt in 00 02 System32, 010202
Performance Slower on Faster Machine
Microsoft Case SRX010207601263 W2K Crashed Installation Support Corre
Config.nt
Microsoft Requests Test EMM386

2110 -    ..
2111 - Summary/Objective
2112 -
211201 - Follow up ref SDS 39 0000, ref SDS 37 0000.
211202 -
211203 - Received ref DRT 1 0001 from Joe responding to the email reminder sent
211204 - yesterday, ref SDS 39 0001, asking about progress responding to our
211205 - letter, ref DIP 1 0001, linked to the record on 010220. ref SDS 37
211206 - 0001
211207 -
211208 - Did not receive response from Kenneth Burgener on request for
211209 - re-submission of information he submitted on 010207, but was lost when
211210 - c13 crashed and had to be installed several more times. ref SDS 24
211211 - 5Z3H, as shown in the letter to Joe yesterday. ref SDS 39 Y64L
211212 -
211213 - Einar Ekhorn and his manager, Kelly Mondlock, did not respond to the
211214 - notice in the email sent to Joe requesting Einer to coordinate
211215 - response with Kelly's support, per Einar's letter on 010209.
211216 - ref SDS 26 LF6O
211217 - ..
211218 - Joe does not mention getting help from Einar nor Kelly, and does
211219 - not say anything about contacting Kenneth, requested in the letter
211220 - yesterday. ref SDS 39 FE5F
211221 - ..
211222 - Joe says if your DOS application does not require DMPI memory,
211223 - then you do not need to load DOSX. ref DRT 1 PG6N
211224 -
211225 -     This reflects the record on 010202 showing we have tried this and
211226 -     found SDS runs, but the solution is inconvenient, ref SDS 18 DG3J,
211227 -     and constitutes a product defect which Microsoft is responsible to
211228 -     correct under its promise on 010209 to provide a solution
211229 -     satisfactory to the customer. ref SDS 26 1800
211230 -
211231 - Joe sets out information on the Microsoft Knowledge Base.....
211232 -
211233 -
211234 -               http://www.microsoft.com
211235 -
211236 -
211237 - ....concerning various memory management issues that relate to dosx.
211238 - ref DRT 1 2C7H
211239 - ..
211240 - Joe further explains....
211241 -
211242 -     I have tested a Dell 866 running on a 133 MHZ buss using Win98 to
211243 -     boot to a command prompt.  If you attempt to use emm386 and
211244 -     include the c800-cfff memory range, which is the next block above
211245 -     the VGA video range, the machine will not even boot to a MS-DOS
211246 -     prompt. ref DRT 1 MD5L
211247 -
211248 -         We have reported that our problem is running on a Pentium 4
211249 -         1.4 GHz 400 MHz bus running with w2k.
211250 -
211251 -         We have further reported that running w2k on other systems
211252 -         caused dosx to load high, and that dosx was loading high on
211253 -         our current machine, until we had to re-install w2k.
211254 -     ..
211255 -     Try this on the system in question and see if you don't get
211256 -     the same behavior. Therefore the NTVDM will not attempt to use the
211257 -     memory area either. ref DRT 1 XD6G
211258 -
211259 -         We need Joe to provide a sample config.nt file showing the
211260 -         precise command string to try.
211261 -
211262 -         Per below, sent a letter asking for guidance. ref SDS 0 RP5G
211263 -
211264 -     I have noticed that if DOSX starts loading in the upper c000 range
211265 -     both stubbs load. If DOSX starts loading in the D000 range, only
211266 -     one stub loads.  Each one of these ranges is a 64K block of
211267 -     memory.  In your case you only have the D000 range to load into
211268 -     thus not having enough room to load both DOSX stubbs.  This is a
211269 -     hardware/BIOS issue that we may not be able to workaround using
211270 -     software. ref DRT 1 XK6J
211271 -         ..
211272 -         Why can't we determine what is in c000 and go tell that
211273 -         to load somewhere else.
211274 -
211275 -
211276 -
211277 -  ..
2113 -
2114 -
2115 - 0731
2116 -
211601 - Sent a letter to Joe asking.....
211602 -
211603 -    Joe,
211604 -
211605 -    Thanks for information this morning on our problem.  Can you call
211606 -    me please to discuss your letter. ref DIT 1 0003
211607 -
211608 -    My number is:  415 781 5700
211609 -
211610 -    Thanks.
211611 -    ..
211612 -    Rod
211613 -
211614 - Note:  later reported this letter at attachment to ref DIT 1 0001,
211615 - sent later in the day, ref DIT 1 0003, per below.
211616 -
211617 -
211618 -
211619 -
2117 -
2118 -
2119 - 0745
2120 -
212001 - Received letter from Joe....
212002 -
212003 -    Hello Rod,
212004 -    ..
212005 -    And what would you like to discuss?
212006 -
212007 -    Joe
212008 -
212009 -
212010 -  ..
2121 -
2122 -
2123 - 0933
2124 -
212401 - Submitted ref DIT 1 0001 responding to Joe's request for scope of
212402 - discussions requested in my letter asking for help implementing the
212403 - test he proposed on c13, per above. ref SDS 0 QP8O
212404 -
212405 - We need help using information in Joe's first letter this morning per
212406 - above, ref SDS 0 QP8O, for solving the problems under this case, per
212407 - our telecon on 010220. ref SDS 37 IY4I
212408 -
212409 - Point out that talking to an expert expedites use of technical
212410 - information, and avoids the time and expense of rework, by applying
212411 - expert experience to take steps in the right order, and to recognize
212412 - early when anticipated results require adjusting course and further
212413 - research.  Without this support, experience shows implementing
212414 - information you submitted could take days, even weeks.  With direct
212415 - personal support of an expert, this can be reduced to a few minutes.
212416 - That's the power of "knowledge." ref DIT 1 5S7F
212417 - ..
212418 - Discussion on 010220 showed Joe has a lot of knowledge and
212419 - experience with Microsoft design and engineering requirements,
212420 - ref SDS 37 NU5K, that can supplement information in your letter this
212421 - morning, that will save time and money in completing this case.
212422 - ref DIT 1 ES7N
212423 -
212424 -
212425 -  ..
2125 -
2126 -
2127 - 0955
2128 -
212801 - Received ref DRT 2 0001 from Joe responding to the previous letter
212802 - explaining Joe's expertise and experience is needed to implement his
212803 - request for testing c13, per above. ref SDS 0 M54O
212804 -
212805 -
212806 -
212807 -
2129 -

SUBJECTS
Accountability Burdensom Metric for Executives
Accountability Writing Feared Talking Gives Deniability Get Credit
Psychologically Demanding Com Manager
Resist Get Mad Angry Com Manager Just One Person's Opinion

3107 -
310701 -      ..
310702 -     KM Causes Resistance to Investing Intellectual Capital
310703 -
310704 -     Thank you for all of the Roses Rod, but I am hesitant to continue
310705 -     discussing issues over the phone because you are making the
310706 -     information available on a public website. ref DRT 2 0001
310707 -
310708 -         Joe's concern is the opposite of many who fear accountability.
310709 -         Normally, folks want to talk because they feel this provides
310710 -         deniability.  They avoid writing.  Joe writes up a record
310711 -         showing failure to perform, and avoids talking.
310712 -
310713 -
310714 -      ..
310715 -     Microsoft Support Provides Reliable Applications
310716 -
310717 -     Also, it is up to the software designers on how they access memory
310718 -     above 1 Megabyte and that is not an issue I need to be involved
310719 -     in. Microsoft has consulting service for that type of assistance.
310720 -     ref DRT 2 245L
310721 -
310722 -         Microsoft has an interest in assisting customers obtain
310723 -         consistent performance so there is high reliability in using
310724 -         Microsoft products.
310725 -
310726 -
310727 -     The issue that we are working on is not how you design your
310728 -     software, but why DOSX is loading low.  Thus far the answer to
310729 -     DOSX loading low is because of the hardware you have selected.
310730 -     ref DRT 2 L56F
310731 -         ..
310732 -         Designing software has not been presented nor discussed
310733 -         with Microsoft.  We have reported that disparate results occur
310734 -         running applications with w2k on different computers.  We are
310735 -         attempting to obtain consistent results so the performance of
310736 -         Microsoft applications is consistent and reliable.
310737 -
310738 -
310739 -
3108 -

SUBJECTS
SDS and Medit
Performance Slower for SDS Reports than C11
Microsoft Requests Test EMM386
Microsoft SRX010207601263 W2K Crashed Installation Support

4007 -
400701 -      ..
400702 -     Solution May Not be Possible
400703 -
400704 -     There may be no work around.  At least so far, I have not found
400705 -     one and it does not appear to be likely.  I have suggested a test
400706 -     on the equipment you have. If the results of that test are the
400707 -     same as mine, then we are 99% sure that there is no workaround and
400708 -     you must design your MS-DOS application to use less memory.
400709 -     ref DRT 2 H76J
400710 -
400711 -     Please provide the results of that test. ref DRT 2 K77F
400712 -
400713 -
400714 -
400715 -  ..
4008 -
4009 -
4010 - 1144
4011 -
401101 - Submitted ref DIT 2 0001 responding to Joe's letter per above,
401102 - ref SDS 0 SE8G, that is not very useful, because it does not address
401103 - Joe's specific idea to do a test, because his request is buried in the
401104 - letter, and so the thing I noticed was he was does not think the test
401105 - will work anyway, i.e., there is no solution.
401106 -
401107 -     Explain worry about the record can be resolved by submitting
401108 -     corrections, so that intellectual capital, ref OF 4 1101, is
401109 -     invested to grow useful knowledge. ref DIT 2 XF6L
401110 -     ..
401111 -     Cite report on 010223 on world conference in Paris,
401112 -     ref DIT 2 006O, that industry is going bankrupt because of not
401113 -     supporting customers. ref SDS 38 FM6J and ref SDS 38 W56J
401114 -     ..
401115 -     Mention that c13 ran with dosx in high memory when we
401116 -     received it from the vendor. ref DIT 2 004O
401117 -     ..
401118 -     Ask Joe for customer's follow up options, when Microsoft
401119 -     engineer confirms product defect. ref DIT 2 00FR
401120 -
401121 -
401122 -
401123 -
401124 -
401125 -
4012 -

SUBJECTS
Microsoft Requests Test EMM386
EMM386 Needed to Perform Test Requested by Microsoft, Request Support
Microsoft Requests Test EMM386

4406 - 2253
4407 -
440701 -  ..
440702 -
440703 - After getting other stuff done today, late this evening reviewed Joe's
440704 - letter again, per above, ref SDS 0 XU7O, and noticed he makes a
440705 - specific suggestion to experiment with emm386. ref SDS 0 XU7O  His
440706 - last letter this afternoon affirms his request for a test. ref SDS 0
440707 - 4641
440708 -
440709 - Tried following in config.nt
440710 -
440711 -     dos=high, umb
440712 -     device=%SystemRoot%\system32\himem.sys
440713 -     emm386 c800 cfff
440714 -     files=50
440715 - ..
440716 - Ran DOS and found that it was successfully.
440717 -
440718 - Ran mem /d at DOS prompt and it did not list emm386 was loaded into
440719 - memory.
440720 -
440721 - Turns out we don't seem to have emm386*.* on the system, and it does
440722 - not seem to be part of w2k system CD.
440723 -
440724 - Need suggestion from Joe on how to conduct experiment.  What is the
440725 - command string, where to put it, and where to get emm386?
440726 -
440727 -    [On 010228 submitted letter to Joe linked to this report, per his
440728 -    request. ref SDS 40 0001
440729 -
440730 -
440731 -
440732 -
440733 -
440734 -
440735 -
440736 -
Distribution. . . . See "CONTACTS"