Ethnograph v5 Updates

Patch7n Updates v5.x to v5.04 and fixes the following bugs:
Download Patch7n 1356K ( 3-15 minutes to download)  Please Print this Page.

Patch7n incorporates all fixes in Patch1N..4N  (See Below)

Patch7n

There is no Patch5n or Patch6n.  The primary issue for the network version since Patch4n has been implementing TCP/IP protocol.  We have finally resolved this problem. To see changes in Patches 5, 6, and 7 please check the Patch7s history.  

Patch4n

GENERAL:

DIALOGS ONLY PARTIALLY VISIBLE WHEN USING LARGE FONTS.  V5 was originally designed to be viewed using small fonts and screens set for 800 x 600 resolution or better.  On larger monitors (17"+) and at higher resolutions,  many dialogs and other screens were not displayed properly.  Now all dialogs and screens display and work properly.  You no longer need to reset your display to small fonts and lower resolution.

EDITOR:

LINES OF TEXT WERE CUT OFF WHEN THEY WERE SAVED IN THE EDITOR AND THE MONTOR DISPLAY WAS SET TO LARGE FONTS.  When you created and saved data files in the Ethnograph Editor, and if your montor was set to use Large Fonts, the ends of lines were cut off.  You would see this in the Code procedure.  This is now fixed.

ADDING/DELETING SPACES IN WORDS: (This bug mysteriously reappeared. And hopefully has been fixed for good.)  Under certain circumstances, when you selected any reformat option, a blank space was added or deleted from one or more positions in the text. Thus "next word" might appear as "nextword" or "next" might appear as "n ext". This no longer happens.

MEMO'S:

THE ENTIRE MEMO WOULD NOT PRINT: Under certain conditions only the first 256 characters of a memo would print.  This has been fixed.

BACKUP AND RESTORE USING FLOPPY DISKS:

VERY LARGE CODE BOOKS and MEMOS COULD NOT BE BACKED UP TO FLOPPY DISKS.  If a Code Book or Memo file was larger than the capacity of a floppy disk (1.4megabytes), the back up process would not work.  You needed a Code Book with over 2000 code words to experience this problem. Now, if you have a very large Code Book (2000 to 8000 code words) it automatically compresses the Code Book so it can be backed up to a floppy disk, and restored from a floppy disk.  The same works if you have a very large set of Memo's.  Since the size of an individual memo can vary from 1 to 16 or more pages, it is difficult to define what a "very large set of Memo's" is.  But with compression, the backup problem should be a very rare problem.  

NOTE: This problem does not affect backing up to large capacity removable media such as  ZIP disks and JAZZ disks, or Hard Disks.

RESTORED CODE BOOK DOES NOT HAVE CODES, DEFINITIONS OR CODE FAMILIES. When you restore a backed up code book, a dummy code book is created for the Project. Then the old code book is copied into the dummy code book. Under certain conditions the code book was not restored.  Also, under other circumstances, the code book was not backed up.  This problem has been fixed.

BACKUP TO A DIRECTORY ON A FLOPPY DISK. If you backed up a project to a directory on a floppy disk (e.g., A:\BACKUP o instead of A:\), and if the backup required 2 or more floppy disks, the directory would not be created on the 2nd disk.  It would backup and restore properly, but on the additional disks the files would be written to the root directory.  Now the directory is created and written to on each additional disk.

BACKUP TO THE ROOT DIRECTORY ON A FLOPPY.  If you backed up a project to the root directory on a floppy disk (e.g., A:\) , and if the root directory already contained files of any type, you are asked if you want to erase the disk.  Only files in the root directory were erased.  Now the entire floppy disk, including all subdirectories, is erased.  

NOTE:  If you back up to a directory on a floppy disk, and there are files of any type already in that directory, only the contents of that directory are erased.  No files in the root directory, or any other directory are erased.

Patch3N incorporates all fixes in Patch1N and Patch2N (See Below)

CODING:

CANNOT PERFORM THIS OPERATION ON A CLOSED DATASET.    This bug appeared after you had added a data file to the project and then opened the CODING procedure. The full message was Application error. Exception EDatabase Error in module coding.dll at 002611EB. Cannot perform this operation on a closed dataset  This error occurred when the program attempted to open the tertiary files (e.g., Memo.FFD, CodeBook.FFD), but they were not there.  This upset the program and it generated the above error message and crashed the program.  This bug is now fixed. 

This bug was caused by a bug fix made in Patch2S.  See File Manager, EXISTING CODEBOOK DELETED below. 

Patch2n incorporates all fixes included in Patch1n (see below).

CODING:

DISAPPEARING CODES: Under some conditions the program would insert "garbage"codes in your data set.  This would cause codes below the "garbage" code not to be displayed in your data file. You could see the "garbage" if you switched to "view code sets" in the Code a Data File Procedure. Patch2S removes the "garbage" codes, and any other anomalous codes when it opens a data file.

DOUBLE CLICK CODE BOOK BUTTON: If you double clicked on the Code Book button on the tool bar, the program would hang. This no longer happens.

CODE LIST BUTTON: When you are in either the Quick Code screen, or the Code Set screen, and you click on the Code List button, it now puts you directly in the Find field of the Code List form.

RETURN TO TOP OF FILE FROM CODE BOOK: When you would go to the Code Book, it returned you to the top of the file. Now it returns you to the place in the file you were at before you went to the code book.

CLICKING OUTSIDE OF QUICK CODE, CODE SET, MEMO: When you were in Quick Code, if you entered a Code Word, then a Start Line, and then clicked outside of the Quick Code screen (for example, to scroll the data file) without entering a Stop Line, many strange things happened. This also was true for Code Set and Memo screens. All of these have been fixed.

FROM FILE MEMO TO TEXT MEMO:  If you click on Memo before selecting start and stop lines, you get a File Memo. If you then changed that to a Text Memo, under certain conditions you would get the message, "cannot focus a disabled or invisible window". This has been fixed.

"YOU MUST ENTER A START LINE": In Quick Code, if you had entered a Code Word, and then clicked anywhere else, you got trapped in a loop with the above message.  This has been fixed.  You only get the message if you click the Okay button.

CLICK ON "M" TO VIEW MEMO:  If a memo in a previous file started on the same line, you got that memo instead of the one you clicked on.  This has been fixed.  You now get the correct memo.

STARTING WITH BLANK CODE SET:  If you opened a blank Code Set Window, and you changed the start line from 0 to some number( e.g., 5), when you clicked in the first code word slot, the highlight would go backwards (e.g., 1-5).  Then, when you entered a stop line (e.g., 10) the highlight would be correct (e.g., 5-10).  Now when you click in the code word only the start line is highlighted. 

EDITOR: Reformatting Documents.

REFORMAT PUT YOU AT BOTTOM OF FILE: When you pasted a document in the editor, it left you at the end of the document. Now you are put at the beginning of the document

INDENTED CONTEXTUAL COMMENTS: If you selected the Identifiers are marked reformat option, it would indent contextual comments. Now contextual comments remain in column 1.

ADDING/DELETING SPACES IN WORDS: Under certain circumstances, when you selected any reformat option, a blank space was added or deleted from one or more positions in the text. Thus "next word" might appear as "nextword" or "next" might appear as "n ext". This no longer happens.

EDIT, SAVE, REFORMAT:  If you did this sequence, the edited file was saved, but the reformat cut the file off at the edit point.  This no longer happens.

IDENTIFIER SHEETS:

CRASH WHEN PICKING FILE FROM FILE LIST:  After you add a data file to a project using the editor, if you go directly to Identifier Sheets, and if you select a data file from the File List, and if you then select a second data file from the list, the program would crash.  This has been fixed.

PROJECT MANAGER:

EXISTING CODE BOOK DELETED:  If you created a new project, and if there were already tertiary files (Memos, Code Book, etc) in the directory, a message asked if it was OK to delete the tertiary Files.  If you said NO, the Code Book would still be deleted.  This has been fixed.

GENERAL:

200 FILE LIMIT:  There were two places where we forgot to remove the old v4 200 File Limit.  These have been removed and you can have an unlimited number of files everywhere.

Patch1N Updates v5.0 to v5.01 and fixes the following bugs:

DISCONNECTS: The Server had a tendency to disconnect from the client after very short intervals.  This bug has been fixed.

CODING: Screen not Redrawing Properly

This one looked worse than it really was.  Under certain conditions, lines in the screen would either be duplicated or deleted.  This was purely a cosmetic bug and has been fixed.  This one caused a great deal of distress and we apologize for it.  The culprit was a tiny change we had made on the day we sent the disk to be manufactured.  Up to that time everything else was working fine. 

BACKUP:"Cannot open file xxxxxxxx.NUM"

If you had been coding a data file and tried to do a  backup in the Project Manager, the backup would crash with the message "Cannot open file xxxxxxxx.NUM".  This has been fixed.

BACKUP: Destination Directory

If you typed a backup destination of D:, the last open directory on D would be the back up directory.  Two changes have been made:

1) Now, if you type a backup destination of D: or A:, a backslash is automatically added so that the backup destination becomes the root directory, e.g. D:\ or A:\.  Of course you can always back up to D:\<folder>

2) You can no longer backup to the root directory of the C: drive.  This is usually the boot drive on a computer.  If you tried a backup to C:\, all of your system files would be erased. This would be bad. The program no longer accepts a backup destination of C:\.  It will accept C:\<folder>

FREQUENCY OUTPUT: Using Identifier Filters

If you had used only one identifier filter but two or more code words, Only the first code word would be printed on the output.  The values for each code word frequency were correct, but the labels were wrong.  This bug has been fixed.

FREQUENCY OUTPUT:  Save as Raw Data File

Oops!  We forgot to activate this when we finished the program.  This option saves frequency output as a comma delimited ASCII file.  You can import this file into spreadsheets, data bases, and statistical packages.  After you have generated frequencies, click PRINT on the Menu Bar to get at this option.

SEGMENT OUTPUT: Printing Expanded Segments

If you did a segment search, set the display to Expanded, and then printed out the expanded segments, the line identifying the data file from which the segment came was not printed with the segment.  This bug has been fixed.

CODING: Screen not Redrawing Properly

This one looked worse than it really was.  Under certain conditions, lines in the screen would either be duplicated or deleted.  This was purely a cosmetic bug and has been fixed.  This one caused a great deal of distress and we apologize for it.  The culprit was a tiny change we had made on the day we sent the disk to be manufactured.  Up to that time everything else was working fine. 

Return to Homepage