TargetD64 Changes for V0.3.3

List of Changes
 

• Introduced a copy template for .targetd64rc which is used whenever this file is not found in $HOME
• Finally providing a configure script for building
  

Resolved Requests from the Error Tracker

RQID________: 24
PRODUCT_____: TargetD64
COMPONENT___: Source Distribution
VERSION_____: V0.2.2
FIXED_VERS__: V0.3.3
OS__________: Linux
ORIGINATOR__: Gaelyne R. Gasson
TYPE________: Problem report
STATE_______: Resolved
SEVERITY____: Low
DATE________: 04.10.99
SUBJECT_____: Use ./configure to configure generation process
DETAILS_____:
./configure is a UNIX/Linux standard to configure builds and missing for TargetD64.
ANALYSIS____:
CONCLUSION__: Finally using autoconf and configure script.


RQID________: 31
PRODUCT_____: TargetD64
COMPONENT___: Manual
VERSION_____: V0.3
FIXED_VERS__: V0.3.3
OS__________: All
ORIGINATOR__: Professor Dredd
TYPE________: Problem report
STATE_______: Resolved
SEVERITY____: Low
DATE________: 07.12.01
SUBJECT_____: Configuration of PATH variable for Windows 2000
DETAILS_____: Windows 2000 does not execute AUTOEXEC.BAT. The manual does not explain how to set the PATH variable there. This is necessary to call TargetD64 from command line without typing the complete path name.
ANALYSIS____:
Use Settings->Control Panel from Start button and execute System from there. Select the advanced tab and click on the Environment Variables button there. A definition for the Path variable should be already there in the system variables block. Edit this definition by adding the TargetD64 installation directory.
CONCLUSION__:
Add this description to the manual.

RQID________: 38
PRODUCT_____: TargetD64
COMPONENT___: Executable
VERSION_____: V0.3.1
FIXED_VERS__: V0.3.3
OS__________: Linux
ORIGINATOR__: Karlheinz Langguth
TYPE________: Bug report
STATE_______: Resolved
SEVERITY____: Low
DATE________: 27.06.03
SUBJECT_____: Exception occurs when using option -c dir with dir in different device as TMPDIR
DETAILS_____:
ANALYSIS____:
It seems that rename() function is only able to rename files within a device and not across device boundaries
CONCLUSION__:
Replace rename() call by something else (research necessary maybe hand coded).


RQID________: 42
PRODUCT_____: TargetD64
COMPONENT___: Source Distribution
VERSION_____: V0.3.2
FIXED_VERS__: V0.3.3
OS__________: Linux
ORIGINATOR__: msremac
TYPE________: Bug report
STATE_______: Resolved
SEVERITY____: Low
DATE________: 03.07.04
SUBJECT_____: Makefile does not work with GNU make version 3.79.1
DETAILS_____: No make happens, instead error message appears: makefile:100: *** commands commence before first target.  Stop.
ANALYSIS____:
The makefile contains DOS newlines which are coded by "\r\n". Linux makefile need only "\n". It seems that other make versions are fault tolerant.
CONCLUSION__:
Convert the newlines. As a workaround use the following commands to convert:
char=`echo -e "\r"`
sed -e "s/$char$//" makefile >makefile.new
mv makefile.new makefile

RQID________: 43
PRODUCT_____: TargetD64
COMPONENT___: Source Distribution
VERSION_____: V0.3.2
FIXED_VERS__: V0.3.3
OS__________: All
ORIGINATOR__: Karlheinz Langguth
TYPE________: Bug report
STATE_______: Resolved
SEVERITY____: Medium
DATE________: 13.11.06
SUBJECT_____: Order of input files is not necessarily preserved in resulting D64 image
DETAILS_____: "targetd64 a b" could result in a D64 image with file order "b a"
ANALYSIS____:
Reading out the filesystem with opendir/readdir in Linux and FindFirstFile in Win32 does not necessarily lead to file ordering by creation time. Even sorting the files by last modification timestamp is a no go because we have filesystems with timestamp resolution of a second (happens to me with ReiserFS and Linux).
CONCLUSION__:
Assure that created files timestamp differ at least a second by setting timestamp explicitly. Read in all entries of the directory to process and sort them by last modification timestamp. Mind that this will not work for "external helpers" because it is hard to manipulate the timestamps created by those.


RQID________: 44
PRODUCT_____: TargetD64
COMPONENT___: Source Distribution
VERSION_____: V0.3.2
FIXED_VERS__: V0.3.3
OS__________: Linux
ORIGINATOR__: Karlheinz Langguth
TYPE________: Bug report
STATE_______: Resolved
SEVERITY____: High
DATE________: 28.06.03
SUBJECT_____: Source will not compile with gcc 4.1.
DETAILS_____: 
ANALYSIS____:
gcc >= 4.0 does a more strict syntax analysis on C++.
CONCLUSION__:
Correct syntax.