List of Changes
Resolved Requests from the Error Tracker
RQID________: 33
PRODUCT_____: TargetD64
COMPONENT___: Executable
VERSION_____: V0.3
FIXED_VERS__:
OS__________: All
ORIGINATOR__: Professor Dredd
TYPE________: Problem report
STATE_______: Resolved
SEVERITY____: Low
DATE________: 07.12.01
SUBJECT_____: Six pack archives are not supported ([1-6]!*)
ANALYSIS____:
Six packed files are not recognized and processed by TargetD64. As they
contain bit stream encoding in general it makes no sense to produce D64 from
them because D64 only reflects block oriented access. Conversion in general
results in important loss of information (e.g. copy protection).
CONCLUSION__:
Will not be nativly supported. You may use an external helper to process these files with targetd64.
RQID________: 36
PRODUCT_____: TargetD64
COMPONENT___: Executable
VERSION_____: V0.3
FIXED_VERS__:
OS__________: Win2000
ORIGINATOR__: Professor Dredd
TYPE________: Problem report
STATE_______: Resolved
SEVERITY____: Medium
DATE________: 13.05.02
SUBJECT_____: CCS_WIN32 requires fully qualified path for call
DETAILS_____:
Referring back to "RQID________: 31", I found it useful to make the
following changes:
As described in "RQID________: 31", the full path to TARGETD64 should
be appended to the PATH environment variable. Additionally I appended the
full path to CCS.EXE so it looks like
"{pathinfo};C:\Documents and Settings\Ken\My Documents\C-64\TargetD64;C:\Documents
and Settings\Ken\My Documents\C-64\CCS64_32"
Now I was having difficulty with CCS.EXE because calling it from the
command line (as TARGETD64 presumably does) leaves it's execution path set
to the path of the archive file. CCS.EXE looks for it's support files (C64.CFG,
ROM.CFG and the default .ROM files) in the current command line path and if
not found it will malfunction.
So when dropping an archive onto the TARGETD64 shortcut on the Desktop,
CCS.EXE looks for its support files on the Desktop. Because the support
files don't exist on the desktop, CCS.EXE malfunctions and must be exited
with ALT-Q. This is proven because after exiting CCS.EXE creates a dummy
C64.CFG on the desktop!
I got around this problem by editing my TARGETD64.INI file to use the
following command when executing CCS.EXE:
"Cmd = cd c:\docume~1\ken\mydocu~1\c-64\ccs64_32\; ccs.exe %s2,0"
This seems to work well but please tell me if there is a better solution.
ANALYSIS____:
It is sufficient to call ccs.exe from command line with a fully qualified
path. This spares changing the current directory to the ccs64 installation
path (which would work, too). So change the Cmd line of the targetd64.ini
file to:
"Cmd = c:\docume~1\ken\mydocu~1\c-64\ccs64_32\ccs.exe %s2,0"
where "c:\docume~1\ken\mydocu~1\c-64\ccs64_32" is the installation
path of ccs64.
CONCLUSION__:
No changes of TargetD64 needed.
RQID________: 40
PRODUCT_____: TargetD64
COMPONENT___: Executable
VERSION_____: V0.3
FIXED_VERS__: V0.3.2
OS__________: WinXP
ORIGINATOR__: Scott Gray
TYPE________: Bug report
STATE_______: Resolved
SEVERITY____: High
DATE________: 11.09.03
SUBJECT_____: Keep Original Filename does not work
DETAILS_____:
Suppose I have a file to convert named "myfile.prg" -- it's a c64 program in the raw, and needs to be in a .d64 file for use with my emulator. I drag and drop the "myfile.prg" as directed, and TargetD64 produces "target.d64" -- with the program inside (and upon a test load & run in the simulator, works fine). BUT! I canNOT get it to call the .d64 file anything except "target.d64" (or "target0.d64" etc. if there's already a file by the name "target.d64"). I have done "set TD64_DEFAULT_OPTIONS=-k" *and* "KeepOriginalFilename = 1" in the .INI file, along with "ConvertOnlyDirectory = c:\Temp". The "convert only" option works like a charm, but the "KeepOriginalFilename" doesn't seem to do anything...I still get things named just "targetxxx.d64" no matter what I do. I have almost 600 files to convert, and I *REALLY* don't want to have to rename them all one-at-a-time by hand afterward. What am I doing wrong?
ANALYSIS____:
The source filename is NOT used for the D64 archive for non resolvable files (raw c64), instead the resulting D64 has the default name targetXXX.d64
CONCLUSION__:
Even for non resolvable filenames use filename for resulting D64 if this is indicated by -k option. If there are more than one non resolvable files put into the same D64 archive use the first for D64 filename.
RQID________: 41
PRODUCT_____: TargetD64
COMPONENT___: Executable
VERSION_____: V0.3
FIXED_VERS__: V0.3.2
OS__________: WinXP
ORIGINATOR__: Scott Gray
TYPE________: Bug report
STATE_______: Resolved
SEVERITY____: Low
DATE________: 11.09.03
SUBJECT_____: Keep Original Filename (case of characters)
DETAILS_____:
The only thing "wrong" with it now is that this "Ace_of_Aces(1983).prg" becomes "ace_of_aces(1983).d64". This is a VERY minor thing. If you want to change it so it keeps the capital letters, I'll be even happier, but it is NOT a complaint.
ANALYSIS____:
Characters are explicitly set to lower case for the resulting D64 filename
CONCLUSION__:
Remove conversion to lower case and keep the case as is.