THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net
S U M M A R Y
DIARY: September 13, 2004 04:52 PM Monday;
Rod Welch
Gary reports problems launching SDS on Windows XP at home.
1...Summary/Objective
..............
Click here to comment!
CONTACTS
SUBJECTS
OS XP SDS Launch Failed Medit Failed to Run DOS DOSE Investigation S
Root Cause Analysis 4DOS Rather than Windows XP Cmd.exe Caused SDS L
DOS4 Alternate to MS DOS May Cause Problems
1005 -
1005 - ..
1006 - Summary/Objective
1007 -
100701 - Follow up ref SDS 14 0000. ref SDS 11 0000.
100702 -
100703 - On 040823 Gary switched OS to Windows XP. ref SDS 15 HM7L At that
100704 - time, Gary reported a problem using SDS under XP, which turned out to
100705 - be caused by Medit handling of the dos and dose commands. ref SDS 15
100706 - U27K On 040902, Morris fixed this problem. ref SDS 16 U27K
100708 - ..
100709 - Yesterday, Gary reported a new problem saying SDS would not launch on
100710 - his home computer running under XP.
100711 -
100712 - 1. Subject: Broke it again!
100713 - Date: Sun, 12 Sep 2004 13:27:26 -0700
100717 - ..
100718 - 2. Rod,
100720 - ..
100721 - SDS launch on XP (at home) breaks again.
100723 - ..
100724 - 3. It hangs in an empty command window with a title of "AI -
100725 - c:\sd\01\e dirx c:\sd\03\001".
100727 - ..
100728 - 4. It needs to archive, and the messages indicate that it is doing
100729 - that, but never finishes, since it archives every time it
100730 - launches.
100732 - ..
100733 - 5. The e:\sd\08\fun file with the directory does get saved.
100735 - ..
100736 - 6. I will in home later today.
100738 - ..
100739 - 7. I won't be at work tomorrow -- taking the dog to the vet. I
100740 - should be home during the afternoon.
100742 - ..
100743 - 8. Thanks,
100745 - ..
100746 - 9. Gary
100747 -
100749 - ..
100750 - This afternoon, Gary called and we reviewed the problem.
100752 - ..
100753 - Initially, submitted an SDS update to ensure that Gary has the most
100754 - recent SDS code.
100756 - ..
100757 - This did not solve the problem.
100759 - ..
100760 - We used the record on 040317, when this issue was worked on a similar
100761 - matter, that facilitates access to code for SDS program launch.
100762 - ref SDS 9 HJ5H
100764 - ..
100765 - Experiments were configured by setting macro 040702 with debug, and
100766 - and unplugging various features, then SDS was run to failure on
100767 - multiple passes in order to discover the cause of the problem Gary
100768 - reported today.
100770 - ..
100771 - Gary described events when SDS is launched as the "screen going black,
100772 - flashing, and then everything stops," per his letter today, shown
100773 - above. ref SDS 0 L39Y
100775 - ..
100776 - This sounds similar to the problem he reported on 040902 when we
100777 - discovered that dos and dose commands were not running under Windows
100778 - XP.
100780 - ..
100781 - Gary did an experiment running Medit to test dos and dose commands.
100782 - He indicated that these commands failed. Since Morris fixed this on
100783 - 040902, ref SDS 16 0001, there is a suggestion that these tools (SDS,
100784 - Medit) are not being run under Windows cmd.exe, which is the design
100785 - platform for SDS, beginning on 030202, ref SDS 5 QR3G, based on Gary's
100786 - recommendation earlier on 021016. ref SDS 3 UZ6G
100788 - ..
100789 - Gary investigated and found that he made changes to his computer that
100790 - resulted in running Medit and SDS under a DOS shell program called
100791 - 4DOS, similar to experience on 021105. ref SDS 4 TY6M
100792 -
100793 - On 040905 SDS support for root cause analysis was reviewed; the
100794 - record today illustrates this support, ref SDS 17 2S4J, based
100795 - on the definition developed through research at that time.
100796 - ref SDS 17 AZ9J
100797 -
100798 - [On 040915 Gary was unaware that SDS supports root cause
100799 - analysis. ref SDS 18 Z47N
100801 - ..
100802 - Gary changed his computer to run SDS under cmd.exe, and this solved
100803 - the problem, indicating the root cause of the problem today was 4dos
100804 - configuration, similar to experience when SDS was installed in 2002,
100805 - reported on 021105. ref SDS 4 TY6M
100806 -
100807 - [On 060220 Gary had similar problem, and solved it by using
100808 - Microsoft DOS. ref SDS 19 LR4G
100809 -
100810 -
100811 -
100812 -
100813 -
100814 -
100815 -
100816 -
100817 -
1009 -