Backup

[mr breeze]

went to my current backup ext hd and in windows explorer, i can see the files (flacs, etc), but when i run their ffp or md5 to check them, theres no data in the files... nothin?!
wtf?
nightmare time...
any ideas?

[mr breeze]

Originally Posted by mr breeze

went to my current backup ext hd and in windows explorer, i can see the files (flacs, etc), but when i run their ffp or md5 to check them, theres no data in the files... nothin?!
wtf?
nightmare time...
any ideas?

nevermind, it was something else.
YESTERDAY: when i double clicked on an .ffp file in windows explorer, it gave me an error message.
TODAY: i decided to backtrack through the folders to check sorted by the backup dates and brought up the full tlh app to go through the folders using that. the checksums worked correctly and i have the files and they verified okay.
its kinda strange, as i recall, on my other machine, just double clicking on a checksum file would bring up tlh and run through the verification process.
i guess that doesn't work that way on this machine.
kinda ruined my night, but live and learn, i guess.

[Orangeboy]

Are you comfortable with Windows command line, and know the path the TLH?

ftype /?
Displays or modifies file types used in file extension associations

FTYPE [fileType[=[openCommandString]]]

  fileType  Specifies the file type to examine or change
  openCommandString Specifies the open command to use when launching files
                    of this type.

Type FTYPE without parameters to display the current file types that
have open command strings defined.  FTYPE is invoked with just a file
type, it displays the current open command string for that file type.
Specify nothing for the open command string and the FTYPE command will
delete the open command string for the file type.  Within an open
command string %0 or %1 are substituted with the file name being
launched through the assocation.  %* gets all the parameters and %2
gets the 1st parameter, %3 the second, etc.  %~n gets all the remaining
parameters starting with the nth parameter, where n may be between 2 and 9,
inclusive.  For example:

    ASSOC .pl=PerlScript
    FTYPE PerlScript=perl.exe %1 %*

would allow you to invoke a Perl script as follows:

    script.pl 1 2 3

If you want to eliminate the need to type the extensions, then do the
following:

    set PATHEXT=.pl;%PATHEXT%

and the script could be invoked as follows:

    script 1 2 3

So you maybe able to reassociate .ffp (and other) files with ASSOC and FTYPE, with something like this:

ASSOC .ffp=TLHfile
FTYPE TLHfile="<path to tlh executable>" "%1"

[mr breeze]

thanks for the help Orangeboy!
been a while since i've been to the command prompt.
seems like each succeeding version of windows makes it harder to find, or i'm just getting more dense.
i think there's a windows interface to allow me to do the file association?
i might try that first.
thanks!

[joujoujou]

Originally Posted by mr breeze

[...]
i think there's a windows interface to allow me to do the file association?
[...]

It is.

Right-click on file -- "open with..." -- "browse" -- choose the program to be associated with -- OK (make sure the box near "always use this program" is ticked).

[Orangeboy]

Sure, you COULD do it like that, but if there's an antiquated, harder way of doing it that may or may not succeed, why would you?