version 1.0.0 Preview-5 (Feb 23, 2014) Finally got to the bottom of the file corruption problem that occurred when the Image Explorer is used to insert files into an ATR image. Issue: When a binary file is inserted into an ATR via Image Explorer by either "Add File" menu item, or by drag and drop functionality, AspeQt was doing a text conversion and dropping $0D characters from the binary file causing the corruption of the said file. Reason: The primary reason was I believe the Image Explorer has never been fully tested and was (and still is) under development as indicated by the AspeQt manual. But the specific reason for the above issue was an improper IF statement which had an if condition that should have really been an else condition and vice versa. Fix: Changed the offending if statement and tested the Text Conversion logic to make sure text and binary files are processed correctly. Also cleaned-up code which displayed a vague error message when number of bytes read from the file did not match expected number of bytes. Proper procedure for converting text files with AspeQt Text Conversion feature: Case-1: Atari format text file is on the PC and you want to add it to the ATR image, simply insert/drop the file into Image Explorer window with Text Conversion OFF Case-2: Atari format text file is on the PC and you want to convert it to the PC format (using AspeQt like a text converter), simply insert/drop the file into Image Explorer window with Text Conversion OFF, then extract/drag-and-drop from the Image Explorer to the PC with Text Conversion ON. Case-3: Atari file format text file is on Atari and you want to add it to the ATR image, simply copy the file with your Atari to the drive where the ATR image is mounted. Case-4: Atari file format text file is on Atari and you want to copy it to your PC in PC text file format, first copy the file with your Atari to the drive where the ATR image is mounted, then extract/drag-and-drop the file from Image Explorer to PC with Text Conversion ON Above procedure text will also be added to AspeQt manual for the upcoming v1.0.0 release