CONTACTS 

SUBJECTS
Schedule Fail Launch from Group Manager Nothing Evident Wrong in the

1703 -
1703 -    ..
1704 - Summary/Objective
1705 -
170501 - Follow up ref SDS 11 0000. ref SDS 10 0000.
170502 -
170503 - Discovered today that Gary's computer at work running Windows 2000 has
170504 - run out of memory for performing the 25a.cmd op that assembles global
170505 - pointers.  Gary is thinking about creating a separate utility to
170506 - accomplish this function. ref SDS 0 SG3I
170507 -
170508 -
170509 -
170510 -
170511 -
170512 -
170514 -  ..
1706 -
1707 -
1708 - Progress
1709 -
170901 - Gary reported a problem similar to 050928. ref SDS 11 6L5I  The
170902 - problem on 050928 turned out to be an inadvertant corruption of the
170903 - date in the Schedule; the program could not find the next date,
170904 - ref SDS 11 7P7O  But, that is not the problem in this case.
170905 -
170906 -     [On 060220 Gary had similar problem, and solved it by using
170907 -     Microsoft DOS. ref SDS 14 LR4G
170909 -  ..
170910 - Gary submitted his SDS files for review.
170912 -  ..
170913 - Attempting to launch SDS normally on Gary's records ran successfully
170914 - on my computer.  Successful launch further supports the conclusion
170915 - that Gary's records are not corrupted in some quirky way. ref SDS 0
170916 - 6L5I
170918 -  ..
170919 - This is bad news.
170921 -  ..
170922 - Guess I should test this again, because on 050329 Gary reported a
170923 - problem with schedule launch to create a record for a prior date.
170924 - When I ran it on c14 it initially passed, but later failed.
170925 - ref SDS 8 Z942  Went ahead and ran SDS launch on Gary's records again,
170926 - and it was again successful.
170928 -  ..
170929 - Does not seem like an archive problem with pointers, because the
170930 - Schedule for 060214 does not have any records to archive.
170932 -  ..
170933 - Possibly a drive on Gary's computer is full, or very fragmented.  How
170934 - often is the disk maintained?  Windows has gotten better at not
170935 - getting lost, but this is still something to check.
170936 -
170937 -     [On 060220 Gary had similar problem, and solved it by using
170938 -     Microsoft DOS. ref SDS 14 LR4G
170939 -
170940 -
170942 -  ..
1710 -
1711 -
1712 - 0919
1713 -
171301 - Called Gary.  No answer.
171302 -
171303 - We need to find approximately where the problme is occurring.
171305 -  ..
171306 - For example, does the initial stuff scroll on the screen to archive
171307 - the prior records, is there a blank screen in the beginning?
171309 -  ..
171310 - We can perform a debug diagnostic op using 04702.
171312 -  ..
171313 - Background...
171314 -
171315 -    SDS launch was improved.................. 051106, ref SDS 12 9S5M
171316 -
171317 -    Launch creating record for
171318 -    prior date............................... 050329, ref SDS 8 QD5O
171320 -     ..
171321 -    Launched on Gary's home computer
171322 -    running XP, due to using 4DOS............ 040913, ref SDS 7 4Q5Y
171323 -
171324 -
171326 -  ..
1714 -
1715 -
1716 - 0938
1717 -
171701 - Submitted letter to Gary with link to this record...
171702 -
171703 -
171704 -
171706 -  ..
1718 -
1719 -
1720 - 1126
1721 -
172101 - Gary said that file...
172102 -
172103 -                    0704081
172104 -
172105 - ...is different.
172107 -  ..
172108 - Testing.
172110 -  ..
172111 - Line 1140, ref OF 5 TL3M,
172112 -
172114 -  ..
172115 - Line 1440, ref OF 5 MA5M, -label dneS in 04702 about 60 lines below
172116 -
172117 -    linecnt 120 0
172118 -
172119 -
172121 -  ..
172122 - Line 1640, ref OF 5 RD5F,
172123 -
172124 -    line @10
172125 -
172127 -  ..
172128 - Line 1760, ref OF 5 469I,
172129 -
172130 -    trying debug here.
172131 -
172132 -
172134 -  ..
172135 - Line 1520, ref OF 5 4X5J, -label dneS in 04702 about 100 lines below
172136 -
172137 -    Debug test here.
172139 -  ..
172140 - Line 1600, ref OF 5 QTYT,
172141 -
172142 -    End debug here.
172143 -
172144 -
172146 -  ..
172147 - Line 2850, ref OF 5 7650, -goto bRstop in 04072
172148 -
172149 -    25.bat temporarily unplug utility that assembles global pointers.
172150 -
172152 -  ..
172153 - With backup and global pointer ops unplugged, Gary's program runs
172154 - normally.  Further checking found that 25.bat to assemble global
172155 - pointers is causing Gary's computer running Windows 2000 to fail.
172157 -  ..
172158 - We unplugged this feature in Gary's 04702 program macro.
172160 -  ..
172161 - Gary is working on creating a utility to assemble global pointers.
172162 -
172163 -     [On 060216 Morris may have started work on b.exe to assemble
172164 -     global pointers. ref SDS 13 2Z4N
172165 -
172166 -     [On 060220 Gary had similar problem, and solved it by using
172167 -     Microsoft DOS. ref SDS 14 LR4G
172169 -  ..
172170 - Background on 25.BAT is reported on...
172171 -
172172 -        History of failure and
172173 -        consideration of revisions.......... 040707, ref SDS 6 GR5L
172174 -
172175 -        Gary worked on 001 and
172176 -        25.bat.............................. 021023, ref SDS 2 OG8N
172178 -         ..
172179 -        Process explained................... 021023, ref SDS 2 4Q7K
172181 -         ..
172182 -        Gary had similar problem and
172183 -        discovered DOS4 does not run
172184 -        SDS well; switching back
172185 -        to Microsoft DOS.................... 021029, ref SDS 3 0001
172187 -         ..
172188 -        Similar problem running SDS under
172189 -        4DOS after Gary switched to
172190 -        Windows XP operating system......... 040913, ref SDS 7 4Q5Y
172191 -
172192 -            [On 060220 Gary had similar problem, and solved it by using
172193 -            Microsoft DOS. ref SDS 14 LR4G
172195 -         ..
172196 -        Some detailed review of 25.bat
172197 -        which is now 25a.cmd................ 021022, ref SDS 1 044H
172198 -
172199 -
172200 -
172201 -
172202 -
172203 -
172204 -
172205 -
172206 -
172207 -
172208 -
172209 -
172210 -
1723 -