Click here to comment!
1...Gary sets several action items on configuring the keyboard...
0201 - Dynamic Alternatives 562 802 1639
020101 - Mr. Garold L. Johnson
020102 - email@example.com
Errors Problems Using SDS Today
Diary Record Listed in Summary But No Record Exists How to Delete Dat
Diary Records Missing Delete Pointers to Missing Records
Pointers Delete When Switch Back from Current Diary to Schedule Task
Pointers Maintain Remove From Weekly Pointer Files for Missing Diary
Maintain Pointers Remove From Weekly Pointer Files for Missing Diary
1308 - ..
1309 - Summary/Objective
131001 - Follow up ref SDS 54 0000, ref SDS 53 0000.
131003 - Progress today getting the keyboard configured, ref SDS 0 9Y7O and
131004 - received formatted files to improve converting files into HTML.
131005 - ref SDS 0 TW6F Gary is making more use of SDS features, learning
131006 - without training and support for on-site orientation. He is running
131007 - reports using the subject index, which is a big step that reinforces
131008 - the use of flexible structure to organize subjects. ref SDS 0 VY5F
131009 - Using MS DOS for the SDS program has fixed a lot of prior issues.
131010 - ref SDS 0 YX7I He is adjusting to fragile formatting that gives
131011 - flexible structures a lot of power, ref SDS 0 TE6L, using many SDS
131012 - conventions. ref SDS 0 WWQQ and ref SDS 0 5H7F An example are
131013 - procedures for deleting data base pointers when a record has been
131014 - deleted, and for some anomalous reason the pointers remain on the
131015 - disk. ref SDS 0 HR5O Review procedures to create a record for a prior
131016 - date. ref SDS 0 NZ4G Changing a record description for an archived
131017 - diary record is different from the similar procedure for changing the
131018 - description of a current diary record. ref SDS 0 ET3O
131025 - ..
1313 - Progress
131401 - Errors and Problems Using SDS
131403 - Follow up ref SDS 54 QQ6O, ref SDS 53 QQ6O.
131405 - Received ref DRT 3 0001 from Gary explaining new problems he has
131406 - encountered using SDS, now we seem to have the program configured so
131407 - he can use it, per the record yesterday. ref SDS 54 0001
131411 - ..
131412 - Diary Records Not Found
131415 - Gary says...
131417 - I have a couple of Diary records that show up in the Diary but get
131418 - a "Does not exist" error when I try to open them. The error
131419 - message says that the file name that is being expected is
131420 - displayed, but it isn't until after pressing <enter>, which
131421 - confused me. ref DRT 3 XV6G The problem records are:
131423 - October 1, 20021354 Started working with SDS lessons, ref DRT 3
131424 - XV6G
131426 - ..
131427 - October 8, 2002 0924 Titles Off Help Incorrect. ref DRT 3 PPUP
131429 - I checked and found that these records are also missing on my
131430 - set of records for Gary.
131432 - Occasionally, a record will be deleted, but the pointers are
131433 - not updated, typically this occurs when the memory issue arises
131434 - from what I am guessing is fragmented main memory, that is
131435 - similar to fragmented hard disk space.
131437 - There are two conditions....
131439 - 1. Record should not be deleted and so the record is missing
131440 - by mistake. It should be restored from the most recent
131441 - backup.
131443 - ..
131444 - 2. Record should be deleted, and so pointers that are still
131445 - archived must be removed as well, using following
131446 - procedure.
131448 - Note: if there is a record that is to be deleted, this
131449 - can be done using the Diary menu in the record. Then
131450 - none of following steps are needed. These steps are used
131451 - when a glitch occurs and the record is missing, but
131452 - pointer files are still there. Pointer files need to be
131453 - maintained in order to avoid reports that show records
131454 - which do not exist.
131456 - ..
131457 - a. Use the editor and press F1 F3 to open the File
131458 - Access menu.
131460 - b. Enter the spec for the record descriptions...
131463 - d: sd 08 uuuuu 04 yy
131465 - ..
131466 - ...where "uuuuu" is the user ID, for Gary that is
131467 - gljdy, and "yy" is the two digit string for the year.
131468 - For Gary at this time this will be 02, and since
131469 - there are no the records, the year param can be
131470 - omitted altogether.
131472 - Note: use start with "04" because this is the record
131473 - description that has a string which shows up in the
131474 - Diary Summary which disclosed the issue, and so it is
131475 - fast and easy to recognize the record ID strings in
131476 - the weekly pointer file is the one to be deleted.
131478 - ..
131479 - Press Enter
131481 - You will get a list of weekly pointer files for the
131482 - missing record.
131484 - ..
131485 - c. Open the file number corresponding to the week for
131486 - the target record. Typically just approximate it,
131487 - and when you move the cursor to the line and press
131488 - Enter, this opens the file and you can tell
131489 - immediately if the file has the pointers for the file
131490 - you want because the date and time are in the left
131491 - column. If this is the wrong weekly pointer file,
131492 - press ESC to close it and open the next back or up.
131494 - ..
131495 - d. Scroll up in the file to the records with the date of
131496 - the missing record, and find the line with
131497 - description of the record that is missing which was
131498 - displayed in the Diary Summary, and note the time ID
131499 - string, since this is needed to find the
131500 - corresponding entries in the other pointer files.
131502 - Alt F8 deletes the line with the description of the
131503 - missing record.
131505 - Once you delete the record description, there will no
131506 - longer be a listing in the Diary Summary for the
131507 - missing record.
131509 - Press F2 to save the revised weekly pointer file.
131511 - ..
131512 - Press ESC to close the file.
131514 - e. You are back in the listing of weekly pointer files
131515 - for the record Description pointers.
131517 - Now process control field lines by move the cursor to
131518 - column 17 and change 4 to 1, then press Enter.
131520 - This opens the weekly pointer file for control field
131521 - lines, and you know it is the right one, because it
131522 - has the same spec as for the Record Description,
131523 - which you just used.
131525 - f. Perform step d. per above. ref SDS 0 093S
131526 - ..
131527 - g. Process References by repeating step e to open
131528 - weekly pointer files, changing 1 to 3 on column 17,
131529 - then repeat the process in step d
131531 - h. Process Contacts repeating step e to open weekly
131532 - pointer files, changing 1 to 5 on column 17, then
131533 - repeat the process in step d
Prior Date Diary Failing to Run
New Task in Schedule F1 Shift F1 Failed on Record Dated 021022 Possib
150401 - ..
150402 - Prior Date Diary Failing to Run
150404 - Follow up ref SDS 44 8S7J.
150406 - Gary reports today that....
150408 - I am certain that there was a way to do this mentioned in the help
150409 - files, but I couldn't find it. ref DRT 3 PPUU
150411 - I have records where I have entered follow up work in the original
150412 - record. I want to create follow up Diary records on the correct
150413 - date using the record with the extra data as a template. Then I can
150414 - just remove the stuff before the work in the new record and set up
150415 - a forward link in the original record. This should get the whole
150416 - thing correct, but I can't find how to do this. ref DRT 3 3J9K
150418 - ..
150419 - This is issue may be mostly a new user orientation and training issue,
150420 - in that gaining experience of doing the steps a few times overcomes
150421 - these proble i.
150423 - Gary's description in the second para sounds something like the F1
150424 - Shift F1 function to use a diary record for creating a new task in
150425 - the Schedule, then moving the new task in the Schedule to the desired
150426 - date.
150428 - ..
150429 - Creating a diary for a prior date is started in the Schedule.
150431 - 1. Open the Menu, Shift F10, and tab to "Diary"
150434 - 2. Press Enter with the cursor on the D in Diary, or simply click
150435 - with the pointer in the approximate middle of Diary, no need to
150436 - use the Tab key if the mouse is used.
150438 - ..
150439 - 3. Steps 1 and 2 open the Diary menu in the Schedule.
150441 - The first choice is to Make a record for a prior date, so
150442 - simply press Enter and follow the instructions.
150444 - ..
150445 - We did an exercise on 021017 that seemed to be successful at
150446 - that time. ref SDS 44 8S6J
150448 - New users easily encounter difficulties performing any series
150449 - of specific steps, often because the person who prepared the
150450 - steps left out important things because frequent experience
150451 - makes them seem obvious. But are not obvious to new
150452 - users.
150454 - That is why a number of steps using SDS were consolidated on
150455 - 000824. ref SDS 32 0001 There is still much to do.
150457 - [On 021108 Bill Gates announced a new project at Microsoft
150458 - to work on simplifying tasks, so that users will be able to
150459 - use more than 5% of program capabilities. ref SDS 56 EFBE
Save Inserts Anchor into a Headline Justified Headline Creating a Mes
Anchors Above Paragraph Rather than Embedded as the First Word in the
Anchors Add to All Para in SDS record During Save, F2 macro 142, 0702
190601 - ..
190602 - Anchors Formatted Above Paragraph Less Obtrusive
190603 - Save Inserts Anchor into Middle of Headline Creating a Mess
190606 - Gary reports today...
190608 - ..
190609 - == Anchor Insert Breaks Headline
190611 - I had one instance where Save inserted an anchor into a headline
190612 - and then wrapped the underline onto the end of the heading. Since
190613 - this is hard to reproduce, I don't know how to test it easily.
190614 - Using F1 F3 to insert and anchor doesn't wrap the headline, but it
190615 - does put the anchor on the same line as the headline. We might
190616 - consider *always* creating anchors on a line by themselves just
190617 - before the paragraph. It may sound strange, but I think they are
190618 - less obtrusive that way. ref DRT 3 PPWQ
190620 - ..
190621 - There are many scenarios that might have led to the problem Gary
190622 - reports.
190624 - Without being there it is difficult to see what formatting issues
190625 - might have caused this condition.
190627 - Might try editing the headline and starting over.
190629 - ..
190630 - Be sure to either manually putting anchors above headlines, or
190631 - letting the system do it with save.
190633 - I agree that putting anchors above paragraphs is less obtrusive, and
190634 - it provides a better setting when the record is converted to HTML and
190635 - displayed in a browser, because the extra line gives a better visual
190636 - sense of spacing.
190638 - ..
190639 - Right now we have a mixed situation.
190641 - The justify feature enables people to have an anchor above the
190642 - para and avoids placing in the text of the para.
190644 - If the user justifies from the line with anchor it will put the
190645 - anchor in the para, so people can choose what they want.
190647 - The code that adds anchors automatically to para embeds them as
190648 - the default condition, because it seemed like the easiest thing do
190649 - do at the time.
190651 - ..
190652 - Notice all of the anchors in Rod's records have the anchor on the
190653 - line above a paragraph.
Titles Off Does Not Work from Schedule
Record Description Change for Archived Diary and Current Diary Schedul
240501 - ..
240502 - Record Descriptions Changed in Schedule without Titles Off
240503 - Titles Off Does Not Work from Schedule to Change Record Descriptions
240506 - Gary reports today...
240508 - ..
240509 - == Titles Off Doesn't Work From Schedule
240511 - I had an error in the title of a Diary record that I created from
240512 - the schedule. I tired to change it with "Titles Off" from the Diary
240513 - record, but it didn't work. Editing the title in the schedule
240514 - worked fine once I remembered it. ref DRT 3 PPXR
240516 - This is a difference between the way the Schedule works and the way
240517 - the Diary works. I don't see why they shouldn't both work the same
240518 - way. If the title could be edited from the Diary screen, then the
240519 - "Titles Off" function would be redundant. Failing that, "Titles
240520 - Off" should work for a record in the Schedule as well. ref DRT 3
240521 - XO6G
240523 - This is likely related to another problem I had using a follow up
240524 - line in the SAA to try to jump to a record in the Schedule. Perhaps
240525 - we need to make certain that Diary record in the schedule are
240526 - included in some of these branching attempts. ref DRT 3 PO6N
240527 - ..
240528 - Titles off is needed in an archived Diary record (one that is
240529 - dated prior to today) because "titles" are on in a diary record so
240530 - that when the screen is scrolled up the description will continue to
240531 - display.
240533 - Displaying the record description is a helpful visual aid.
240535 - ..
240536 - The description of a diary record cannot be changed directly, because
240537 - access to those lines are protected by a command like tl 3 that
240538 - enables titles for 3 lines. Executing tl 0 from the command line or
240539 - using Titles Off in the menu turns this off temporarily so the
240540 - description can be edited.
240542 - ..
240543 - Since the the description of an archived diary record does not exist
240544 - in the Schedule, there is no ability to edit the description of an
240545 - archived diary record in the Schedule. Therefore titles off is needed
240546 - in an archived diary record, but not for a current diary record, nor
240547 - for a schedule task.
240549 - ..
240550 - For a current diary record we want to ensure conformity between the
240551 - description in the Schedule and in the diary record. Therefore,
240552 - changing the description of a current diary record or a schedule task
240553 - can only be done from the Schedule, and so there is no need for Titles
240554 - Off in a current diary record and a scheduled task.
240556 - Titles off is not needed in the Schedule because the description is
240557 - typed directly in the Schedule.
240559 - ..
240561 - Procedure to change description of a current diary record or a
240562 - schedule task.
240564 - 1. Press F2 to save the work, if desirable.
240566 - 2. Press ESC to close the record, and return to the Schedule.
240567 - ..
240568 - 3. If there are several records and files in memory you may
240569 - have to use Ctrl F6 or click on CMD in upper left corner to
240570 - switch to the Schedule.
240572 - 4. In the Schedule type over the current description for the
240573 - record to be revised, and press Enter.
240575 - This saves the new description in the Schedule, opens the
240576 - record and writes the new description and saves the file, so
240577 - the description in the record is the same as in the Schedule.
Save Justifies Paragraphs When Anchors Added Need Paragraphs with All
290401 - ..
290402 - Wrapping Text Justify with Save and Alt F9 Formatting Paragraphs
290405 - Gary reports today...
290407 - ..
290408 - == Formatting Errors on Save / Wrap
290410 - I have experienced several random errors in formatting records.
290412 - ..
290413 - The problems appear to be related to wrapping lines.
290415 - Some new records had line numbers wrapped into the paragraph
290417 - ..
290418 - I had a line number continue to be pulled into the last line of
290419 - a record during a Save operation. This appears to be caused by
290420 - trying to edit to close to the last available line of the
290421 - file. Adding more lines seemed to fix the problem. ref DRT 3
290422 - PQPR
290424 - ..
290425 - Gary makes a good point.
290427 - It is good practice for flexible structure to maintain 5 to 10 blank
290428 - lines at the end of a record. Similarly, entries in the Reference
290429 - field should have a blank line below the last entry.
290431 - Flexible structure in SDS is fragile and so sensitive to formatting,
290432 - as discussed previously on 021104. ref SDS 53 QATW
290434 - ..
290435 - The format Gary shows in his letter where a series of lines has one
290436 - line at the top that is offset from the others, per above. ref SDS 0
290437 - WW6M causes failure of the Alt F9 justify and wordwrap feature. SDS
290438 - uses a design where a para is identified by a series of lines all
290439 - beginning on the same column and with a blank above and below.
290441 - ..
290442 - If the example above did not have an anchor, and if it occurred where
290443 - the algorithm that adds anchors for the save function calculated that
290444 - an anchor was needed, then an anchor would be added and SDS would
290445 - attempt to justify the lines, resulting in a mess, because the lines
290446 - are not lined up.
SAA Making Entries for Follow Ups Procedures for to Replace an Entry
SAA Open Action Items Listed in Reference Field
SAA Opening Action Items Listed in Reference Field of Schedule Analys
340601 - ..
340602 - SAA Missing Follow Up Entries
340605 - Gary continues...
340607 - ..
340608 - == Lost Follow Up Items in SAA
340610 - The SAA record was missing some Follow Up items that I knew I had
340611 - enter 3. This probably occurred while I was having archiving
340612 - problems. ref DRT 3 PQQU
340614 - ..
340615 - I revisited all of the records (no way to search for them) and
340616 - saved each record with a Follow Up highlight. This fixed the
340617 - probl 4. ref DRT 3 265K
340619 - ..
340620 - Apparently I had missed a record, so I tried to resave that one,
340621 - and it didn't work. I restarted SDS and tried again, but it still
340622 - didn't wo j. ref DRT 3 865O
340624 - ..
340625 - I added a line to a record in order to test this, and both lines
340626 - showed up in the SAA record. This is strange. I did open the SAA
340627 - record each time to refresh it. ref DRT 3 F66J
340630 - ..
340631 - Sounds like Gary followed good recovery procedures, and solved some
340632 - of the issues.
340634 - Gary is showing sophisticated understanding of SDS by recognizing that
340635 - when a record is saved with a change in Follow Up action items, to see
340636 - it in the SAA, the SAA has to be closed and then opened, if it was in
340637 - memory when the procedure was taken. ref SDS 0 SH6J
340639 - Hopefully Gary will be able to search for information to find it when
340640 - needed soon to correct deficit reported, per above. ref SDS 0 PH8A
340641 - Welch records being sent to Gary periodically indicate a procedure
340642 - creating record segments and organic structures that make finding
340643 - information fast and easy.
Subject Index Has Been Significantly Changed from SDS Standards Where
Reports Subject Using SDS Organic Structures in Subject Index
410501 - ..
410502 - Subject Reports Operational with MS DOS
410504 - Follow up ref SDS 54 VY5F, ref SDS 53 VY5F.
410506 - Gary reports today...
410508 - I was able to do a search to find all of the KeyNote records. This
410509 - indicates that there is some advantage for including multiple
410510 - levels of the index in the records. I was after KeyNote Recipes,
410511 - but all the records had KeyNote. The Recipes category under that
410512 - should be KeyNote Recipes, combining 2 levels of the index in a
410513 - single subject. ref DRT 3 WF7K
410515 - ..
410516 - I made this change in the Subject Index and used the search to find
410517 - all the KeyNote records. I then updated the subject descriptions.
410518 - ref DRT 3 EG8H
410520 - Sounds like good progress using the SI.
Font Nesting Errors with A and B Commands Primary Cause of Opra Faili
Nesting Errors Font with A and B Commands Primary Cause of Opra Faili
Convert SDS Record to HTML Failing on Large Record, 0704050
HTML Convert Subject Reports for Use on Internet
Anchors Cause Line Spacing Problem Used with Outline and DIR Commands
Validator Program Shows HTML Code Defective, Gary Johnson
HTML Problems in SDS Conversion Disclosed Changes Made to SDS Code
Johnson, Gary Submits Templates to Conform SDS to Industry Standards
Nesting Font Bold Anchor Command Errors HTML in SDS Records Documents
531201 - ..
531202 - HTML Code Template Shows Support Opera Web Browser
531203 - Nesting Errors HTML Code to Support Opera Web Browser
531204 - Font Command Nesting Errors Must be Eliminated for Opera
531206 - Follow up ref SDS 54 TW6F, ref SDS 53 TW6F.
531208 - Received ref DRT 2 0001 from Gary transmitting template files to
531209 - guide improvements on converting documents and SDS records to HTML
531210 - for publishing on the Internet.
531212 - ..
531213 - Template files provide a good target for working on HTML improvements.
531214 - Gary says....
531216 - ..
531217 - The attached files are an original and a corrected for the letter
531218 - and the SDS record I was working with before.
531220 - a. Original SDS record, ref DRT 2 EX8G, for 021028,
531221 - ref SDS 50 0001,
531223 - Corrected version has Gary's comments. ref DRT 2 EQRQ
531225 - [On 021111 implemented Gary's suggestions.
531226 - ref SDS 58 HE4U
531228 - ..
531229 - b. Original letter, ref DRT 2 PRQV, is dated 021028,
531230 - ref DIP 1 0001,
531232 - Corrected version has Gary's comments. ref DRT 2 0952
531234 - [On 021111 implemented Gary's suggestions.
531235 - ref SDS 58 FO4O
531237 - ..
531238 - The fixed records [SDS and letter] generate some warnings in the
531239 - HTML validator, but no errors.
531241 - ..
531242 - Both corrected records display correctly in the Opera 6.04
531243 - browser!
531245 - If necessary, I can walk you through some of the changes and the
531246 - reasons that I made them.
531248 - These appear to be simple corrections for SDS. The header changes
531249 - should be easy enough in the document file, but not sure about how to
531250 - to implement changes to the font comment. Nesting problems should be
531251 - easy to fix.
531253 - [On 021111 implemented Gary's suggestions. ref SDS 58 0001
531255 - [On 021114 Gary reports SDS records and documents display better
531256 - showing better compliance with standards. ref SDS 59 0001
25.Bat and 001 DIR Command Different Format for Windows 98 Not Assemb
DIR /Z Command DOS4 /Z Switch Requires Revising SDS Code for Archivin
Pointers Global Using OTS for Sort, Select
Archive and Reports Use DIR /Z Switch for DOS4 Macros 001 and 0011 Bo
25.bat Global Pointers Archive SDS Records
610901 - ..
610902 - DOS4 Failing Using Switches for Compliance with MS DOS to Run SDS
610903 - Subject Reports and Archiving Failing Under 4DOS, Try MS DOS
610904 - 25.bat Archive Op and Subject Failing Under 4DOS, Might Try MS DOS
610906 - Follow up ref SDS 54 YX7I, ref SDS 53 YX7I.
610908 - Gary reports today...
610910 - == Using MSDOS Fixes Several Problems
610912 - Changing to MSDOS also appears to have corrected the problems with
610913 - searching the Subject Index. ref DRT 3 PQSS
610915 - Above he explains success doing subject reports. ref SDS 0 VY5F
Ergonomic Keyboard for Efficient Use of SDS Gary Has Omnikey Keyboard
Keyboard Omnikey with Function Keys Optimized for SDS Need to Set Dip
Keyboard Function Keys Optimized for SDS Gary Has an Omnikey 5001 Key
Progress Gary Seems to be Making Excellent Headway Learning SDS
6707 - 1654
670801 - ..
670802 - Keyboard for Ergonomic Use of SDS Enables High Speed Production
670804 - Follow up ref SDS 54 9Y7O, ref SDS 47 YF4I.
670806 - Received a copy of a letter, ref DRT 1 0001 from Gary to Don Strait
670807 - following up Don's response to Gary's request on 021007 for help
670808 - configuring the Omnikey keyboard. ref SDS 38 7U6L
670810 - ..
670811 - Gary sets several action items on configuring the keyboard...
670813 - It took a while to get into the keyboard, but it does have a set
670814 - of DIP switches. I don't know what to set them to, but I expect
670815 - that you have instructions.
670817 - You mentioned a keyboard test program - I would like to have it.
670819 - [On 021109 Gary reports progress on keyboard. ref SDS 57 9Y7O
670821 - ..
670822 - If I can get the orientation changed, I would like to order the
670823 - keycaps and the puller. How do I go about doing that?
670825 - Will the switches change the function without changing the
670826 - keycaps in order to test it?
670828 - Is there a manual for the OmniKey keyboard(s) online anywhere?
Distribution. . . . See "CONTACTS"