1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Error from START cmd, "cannot find the file"

Discussion in 'Support' started by BobK, Dec 20, 2010.

  1. BobK

    Joined:
    Sep 11, 2009
    Messages:
    35
    Likes Received:
    0
    A while ago, ADOBE reader offered to download & install READER 10.0. Which I allowed. Now, when I attempt to START SOMEFILE.FLV, I get this error:
    "TCC: (Sys) The system cannot find the file specified.
    "C:\Program Files (x86)\Adobe\Reader 9.0\Reader\AcroRd32.exe"

    The old Reader 9.0 directory is still there, but empty!
    ASSOC .FLV had a key which FTYPE didn't recognize, I tried to 'fix' things but nothing worked.
    I thought by installing FLASH2X (which I didn't have before) would fix all. ASSOC .FLV now has a key which FTYPE DOES recognize, which points the the FLASH2X program..
    BUT
    I STILL get that "cannot find the file"

    ? WHERE AND HOW Does TCC determine what to call via a START CMD???
    and how do I 'fix' it??
    Bob K.
     
  2. Charles Dye

    Charles Dye Super Moderator
    Staff Member

    Joined:
    May 20, 2008
    Messages:
    3,301
    Likes Received:
    39
    That looks like a 64-bit version of Windows. Are you using a 64-bit Take Command? Which version?
     
  3. BobK

    Joined:
    Sep 11, 2009
    Messages:
    35
    Likes Received:
    0

    Yes to both, 64 bit Window 7 & up-to-date, TCC v11.00.49x64

    I can add, that even though ALLOC & FTYPE now point to FLASH2X,
    After a reboot, still gat the same error this AM.

    Bob
     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    TCC just queries Windows (via the AssocQueryString API) for the command associated with that extension. If you're registry is munged (as seems to be the case here) there's nothing that TCC can do about it.
     
  5. BobK

    Joined:
    Sep 11, 2009
    Messages:
    35
    Likes Received:
    0
    Thanks for that terse guesswork. I've already examined the registry.
    There's nothing wrong there.

    Why should all other file types be properly handled, but not .FLV?
    Why does TCC not obey the rules of ALLOC & FTYPE?!
     
  6. Charles Dye

    Charles Dye Super Moderator
    Staff Member

    Joined:
    May 20, 2008
    Messages:
    3,301
    Likes Received:
    39
    Have you checked both the system settings (under HKEY_CLASSES_ROOT) and the per-user settings (HKEY_CURRENT_USER\Software\Classes) ? I think sometimes the per-user settings override the system ones -- or is it the other way around? -- which always confuses me when it happens.

    (Might be handy if FTYPE and ASSOC had options to check whichever one it is they don't. Maybe both a /S and a /U, with the default clearly noted.)
     
  7. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    TCC *does* obey the rules of ALLOC and FTYPE -- it obviously works for every other file type!

    Until you post the contents of your ALLOC and FTYPE for that extension, I can't begin to guess what is wrong.
     
  8. BobK

    Joined:
    Sep 11, 2009
    Messages:
    35
    Likes Received:
    0
    RCONN: As I explained in my 12/20 post:

    Since the empty directory structure for ADOBE Reader 9.0 was still there, I deleted it all, hoping that TCC would stop giving the error. But it STILL named Reader 9.0 in the error message.

    I then exported the Registry, (converted all x'00's to null and eliminated blank lines to make it all readable).
    I used my editor to find any occurance of Reader 9.0, I did find 316 correct occurances of entries naming Reader 10.0. and two entries with Reader 9.0!
    Those two entries were both under:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders]
    "C:\\Program Files (x86)\\Adobe\\Reader 9.0\\"="1"
    "C:\\Program Files (x86)\\Adobe\\Reader 9.0\\Reader\\"="1"

    My understanding is that IS NOT AN EXECUTABLE section of 4,305 named folders - NO executable names. Note there is no "ACRORD32.EXE" named in those two entries.

    I ran CCLeaner to clean my registry and it DID remove those two Reader 9.0 entries.. BUT I STILL GET THE ERROR..

    To wit:

    C:\]start video.flv
    TCC: (Sys) No application is associated with the specified file for this operation.
    "C:\video.flv"

    Note, it no longer names Reader 9.0 as it did before. Just some mysterious lost executable.. And for my final,,
    Here is my CURRENT ASSOC & FTYPE, copy/pasted

    [C:\]assoc .flv
    .flv=Flash2X.Player
    [C:\]ftype flash2x.player
    flash2x.player=C:\Program Files (x86)\Flash2X\Flash Player\FlashPlayer.exe "%1"
    [C:\]

    I just tried DOUBLE double quotes ("""") & they STILL get stripped out!

    What else can I show you? So far JP "Support" has not supported me.

    Bob
     
  9. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    The error (and error message) is coming from Windows, not from TCC.

    The associations (which are handled by Windows, not TCC) are not only in HKEY_LOCAL_MACHINE; they are also in HKEY_CURRENT_USER and HKEY_CLASSES_ROOT. Windows will look in those registry hives before it looks in HKLM.

    Start a CMD session and try executing the .flv file there. If it also fails in CMD, then your problem is with your Windows configuration. If it works in CMD, then run ASSOC and FTYPE there and see how your file associations are defined.
     
  10. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    It appears that you haven't included the (mandatory) double quotes around the program name.
     
  11. BobK

    Joined:
    Sep 11, 2009
    Messages:
    35
    Likes Received:
    0
    If the quotes should be there, it was FLASH2X that omitted them.
    I wouldn't think a product that's been around as long as that, would
    make that kind of error.
     
  12. BobK

    Joined:
    Sep 11, 2009
    Messages:
    35
    Likes Received:
    0
    ? How did "Windows" use the "TCC:" error message??

    The following failed... with error msg
    [C:\]ftype="C:\Program Files (x86)\Flash2X\Flash Player\FlashPlayer.exe" "%1
    TCC: (Sys) The specified path is invalid.
    ""

    This worked... (is this the right way??)
    ftype filetype=["C:\Program Files (x86)\Flash2X\Flash Player\FlashPlayer.exe" "%1]

    BUT STILL GET error! ..
    [C:\]start video.flv
    TCC: (Sys) No application is associated with the specified file for this operation.

    "C:\start video.flv"
    This CMD session also fails, but perhaps from my 'messing around' trying to put those quotes in (which, BTW, were removed when I requested what FTYPE has??!)

    Under CMD, FTYPE still shows, but ASSOC says "association not found"????? (this is getting wierd)

    Under CMD:
    C:\>assoc .flv
    File association not found for extension .flv
    C:\>ftype flash2x.player
    flash2x.player=C:\Program Files (x86)\Flash2X\Flash Player\FlashPlayer.exe "%1"

    Under TCC:
    C:\AOL>exit <<< back to TC
    [C:\AOL]assoc .flv
    .flv=Flash2X.Player
    [C:\AOL]ftype flash2x.player
    flash2x.player=C:\Program Files (x86)\Flash2X\Flash Player\FlashPlayer.exe "%1"

    Now I HAD NOT touched either of those values, FLASH2X installed them.

    But I still had the original ASSOC & FTYPE pointing to READER 10.0 but TCC (or Windows) was Calling READER 9.0 which didn't exist
     
  13. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,520
    Likes Received:
    4
    BobK:
    | rconn:
    || It appears that you haven't included the (mandatory) double quotes
    || around the program name.
    |
    | If the quotes should be there, it was FLASH2X that omitted them.
    | I wouldn't think a product that's been around as long as that, would
    | make that kind of error.

    Unfortunately such things often happen when a new release is issued. A common cause is the use of a new installer (or installer version). The installed product is OK, but a mistake in the control information provided to the installer makes it inaccessible...
    --
    Steve
     
  14. BobK

    Joined:
    Sep 11, 2009
    Messages:
    35
    Likes Received:
    0
    I'll accept that screw up by FLASH2X.
    But how should I code the fixed FTYPE?? When I added the double quotes it wouldn't work.. When I put the FILTYPE=[... the double quotes were stripped out?

    Ok.. went into the registry... No quotes on cmd.. So, I added them..
    BUT.. when I issued FTYPE .... fro cmd line (under TC),, it showed NO quotes, and still fails on "START x.FLV ..

    I just tried DOUBLE double quotes ("""") & they STILL get stripped out!


    Obviously, I keep 'guessing' wrong!!
     
  15. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    When you see "(Sys)" in the error message, that means it's a Windows error, not a TCC error. TCC is merely displaying the text of the Windows error.

    That syntax is invalid; you're missing the file type.

    No; the brackets are meaningless.

    Note that the START is unnecessary here (it just slows things down and uses more memory).

    That wouldn't have anything to do with quoting the argument in FTYPE.

    Windows, not TCC. TCC doesn't know or care what the file association is; it simply calls Windows.

    I suspect you have multiple definitions for the file association & type in HKLM, HKCR, and HKCU.
     
  16. samintz

    samintz Scott Mintz

    Joined:
    May 20, 2008
    Messages:
    1,187
    Likes Received:
    11
    In my case I have the following values:

    assoc .flv
    .flv=RealPlayer.FLV.6

    ftype RealPlayer.FLV.6
    RealPlayer.FLV.6="c:\program files\real\realplayer\\RealPlay.exe" "%1"

    For you, if you want to use Flash2X, then use:

    assoc .flv=Flash2X.Player
    ftype Flash2X.Player="C:\Program Files (x86)\Flash2X\Flash
    Player\FlashPlayer.exe" "%%1"

    Notice the use of double percents in the ftype command. That is so %1 is
    not evaluated and replaced prior to executing the FTYPE command. If that
    happens then you end up with no file specified to the FlashPlayer program.

    -Scott

    BobK <> wrote on 12/27/2010 06:26:19 PM:


    error:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders]

     
  17. BobK

    Joined:
    Sep 11, 2009
    Messages:
    35
    Likes Received:
    0
    Here's all FLASH2X in my directory that either ARE associated to .FLV, or appear to be important to .FLV ... That second set below looks wrong, but obviously I don't know HOW to use FTYPE correctly, as when I use it the way I *THINK* it seems to be documented, I get an error. And now I see those square brackets and they appear wrong.. HOW should I code FTYPE to make it right??

    If you'd like, I can send you my converted & exported REGEDIT into the form you see below, no x'00's, and no blank lines but it IS 24Mb !!
    I'm COMPLETELY at a loss..


    [HKEY_CLASSES_ROOT\.flv] <<< ASSOC KEY....
    @="Flash2X.Player"
    [HKEY_CLASSES_ROOT\.flv\OpenWithProgIds]
    "WindowsLive.MovieMaker.asset"=hex:


    [HKEY_CLASSES_ROOT\FileType\SHELL\OPEN\COMMAND]<FTYPE p KEY<>@="[\"\"C:\\Program Files (x86)\\Flash2X\\Flash Player\\FlashPlayer.exe\"\" \"\"]" <<< FTYPE KEY result

    [HKEY_CLASSES_ROOT\Flash2X.Player]
    [HKEY_CLASSES_ROOT\Flash2X.Player\DefaultIcon]
    @="C:\\Program Files (x86)\\Flash2X\\Flash Player\\flash_player_document.ico"
    [HKEY_CLASSES_ROOT\Flash2X.Player\Shell]
    [HKEY_CLASSES_ROOT\Flash2X.Player\Shell\Open]
    [HKEY_CLASSES_ROOT\Flash2X.Player\Shell\Open\Command]
    @="C:\\Program Files (x86)\\Flash2X\\Flash Player\\FlashPlayer.exe \"%1\""

    [HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache]
    .........
    .........
    "C:\\Program Files (x86)\\Flash2X\\Flash Player\\FlashPlayer.exe"="FlashPlayer.exe"
    ..........

    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{C90DBB52-46E0-4E65-92BC-799ADEE54C86}\InprocServer32]
    @="C:\\PROGRA~2\\Flash2X\\FLASHP~1\\FLASHP~1.DLL"

    [HKEY_CLASSES_ROOT\.flv]
    @="Flash2X.Player"

    [HKEY_CLASSES_ROOT\FileType\SHELL\OPEN\COMMAND]
    @="[\"\"C:\\Program Files (x86)\\Flash2X\\Flash Player\\FlashPlayer.exe\"\" \"\"]"

    [HKEY_CLASSES_ROOT\Flash2X.Player]
    [HKEY_CLASSES_ROOT\Flash2X.Player\DefaultIcon]
    @="C:\\Program Files (x86)\\Flash2X\\Flash Player\\flash_player_document.ico"
    [HKEY_CLASSES_ROOT\Flash2X.Player\Shell]
    [HKEY_CLASSES_ROOT\Flash2X.Player\Shell\Open]
    [HKEY_CLASSES_ROOT\Flash2X.Player\Shell\Open\Command]
    @="C:\\Program Files (x86)\\Flash2X\\Flash Player\\FlashPlayer.exe \"%1\""

    [HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache]
    "%ProgramFiles(x86)%\\Windows Media Player\\wmplayer.exe"="Windows Media Player"
    "C:\\Program Files (x86)\\Flash2X\\Flash Player\\FlashPlayer.exe"="FlashPlayer.exe"

    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{C90DBB52-46E0-4E65-92BC-799ADEE54C86}\InprocServer32]
    @="C:\\PROGRA~2\\Flash2X\\FLASHP~1\\FLASHP~1.DLL"

    Results: (note the quotes and square brackets are not showing now!)
    [C:\]assoc .flv
    .flv=Flash2X.Player
    [C:\]ftype Flash2X.Player
    Flash2X.Player=C:\Program Files (x86)\Flash2X\Flash Player\FlashPlayer.exe "%1"
     

Share This Page