CAN execute programs via the command prompt but get error - Windows NT

This is a discussion on CAN execute programs via the command prompt but get error - Windows NT ; On Windows 2000, recently, whenever I use [Start | Run] and type in a program name (such as "regedit"), I get an error popup saying that the named program or one of its components cannot be found. However, the program ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: CAN execute programs via the command prompt but get error

  1. CAN execute programs via the command prompt but get error

    On Windows 2000, recently, whenever I use [Start | Run]
    and type in a program name (such as "regedit"),
    I get an error popup saying that the named program
    or one of its components cannot be found.
    However, the program does launch and run normally.
    When I dismiss the error popup, the Run dialog box
    comes back up, as if the program had not launched.
    The running program is not recorded in Run dialog history.

    What could this mean?

    I don't think I have a Virus (and neither does Norton).

  2. Re: CAN execute programs via the command prompt but get error

    Christopher C. Stacy wrote...
    >
    >On Windows 2000, recently, whenever I use [Start | Run]
    >and type in a program name (such as "regedit"),
    >I get an error popup saying that the named program
    >or one of its components cannot be found.
    >However, the program does launch and run normally.
    >When I dismiss the error popup, the Run dialog box
    >comes back up, as if the program had not launched.
    >The running program is not recorded in Run dialog history.
    >
    >What could this mean?
    >
    >I don't think I have a Virus (and neither does Norton).


    Here is a way to troubleshoot.

    1. download a tool "listdlls" from http://www.sysinternals.com
    2. launch regedit on your problem system
    3. run "listdlls regedit" on your system to display all the dll
    details where regedit depends on
    4. on a good W2K system, repeat steps 2 and 3
    5. compare the results in steps 3 and 4.
    Note if there is any dll missing. Compare the dll versions too.

    Also, try checking the event log to see if you can get more details
    on the problem.

    For example, on my XP system:

    c:\>listdlls regedit

    ListDLLs V2.23 - DLL lister for Win9x/NT
    Copyright (C) 1997-2000 Mark Russinovich
    http://www.sysinternals.com

    regedit.exe pid: 3408
    Command line: "C:\WINDOWS\regedit.exe"

    Base Size Version Path
    0x01000000 0x63000 5.01.2600.1106 C:\WINDOWS\regedit.exe
    0x77f50000 0xa7000 5.01.2600.1217 C:\WINDOWS\System32\ntdll.dll
    0x77e60000 0xe6000 5.01.2600.1560 C:\WINDOWS\system32\kernel32.dll
    0x77c10000 0x53000 7.00.2600.1106 C:\WINDOWS\system32\msvcrt.dll
    0x77dd0000 0x8d000 5.01.2600.1106 C:\WINDOWS\system32\ADVAPI32.dll
    0x78000000 0x87000 5.01.2600.1361 C:\WINDOWS\system32\RPCRT4.dll
    0x7f000000 0x41000 5.01.2600.1561 C:\WINDOWS\system32\GDI32.dll
    0x77d40000 0x8d000 5.01.2600.1634 C:\WINDOWS\system32\USER32.dll
    0x71950000 0xe5000 6.00.2800.1643
    C:\WINDOWS\WinSxS\x86_Microsoft.Windows.
    Common-Controls_6595b64144ccf1df_6.0.2600.1643_x-ww_7c3a9bc6\COMCTL32.dll
    0x70a70000 0x66000 6.00.2800.1612 C:\WINDOWS\system32\SHLWAPI.dll
    0x763b0000 0x45000 6.00.2800.1106 C:\WINDOWS\system32\comdlg32.dll
    0x7cd00000 0x7fa000 6.00.2800.1643 C:\WINDOWS\system32\SHELL32.dll
    0x76cc0000 0x10000 5.01.2600.1634 C:\WINDOWS\System32\AUTHZ.dll
    0x71550000 0x1d000 5.01.2600.0000 C:\WINDOWS\System32\ACLUI.dll
    0x4fec0000 0x136000 5.01.2600.1619 C:\WINDOWS\system32\ole32.dll
    0x77120000 0x8b000 3.50.5016.0000 C:\WINDOWS\system32\OLEAUT32.dll
    0x71fa0000 0x44000 5.01.2600.0000 C:\WINDOWS\System32\ulib.dll
    0x6f2b0000 0x6000 5.01.2600.0000 C:\WINDOWS\System32\clb.dll
    0x5ad70000 0x34000 6.00.2800.1106 C:\WINDOWS\System32\uxtheme.dll
    0x74720000 0x44000 5.01.2600.1106 C:\WINDOWS\System32\MSCTF.dll
    0x605d0000 0x8000 5.01.2600.1106 C:\WINDOWS\System32\mslbui.dll



  3. Re: CAN execute programs via the command prompt but get error

    harryooopotter@hotmail.co_ (Harry) writes:
    > Christopher C. Stacy wrote...
    > >
    > >On Windows 2000, recently, whenever I use [Start | Run]
    > >and type in a program name (such as "regedit"),
    > >I get an error popup saying that the named program
    > >or one of its components cannot be found.
    > >However, the program does launch and run normally.
    > >When I dismiss the error popup, the Run dialog box
    > >comes back up, as if the program had not launched.
    > >The running program is not recorded in Run dialog history.
    > >
    > >What could this mean?
    > >
    > >I don't think I have a Virus (and neither does Norton).

    >
    > Here is a way to troubleshoot.
    >
    > 1. download a tool "listdlls" from http://www.sysinternals.com
    > 2. launch regedit on your problem system
    > 3. run "listdlls regedit" on your system to display all the dll
    > details where regedit depends on
    > 4. on a good W2K system, repeat steps 2 and 3
    > 5. compare the results in steps 3 and 4.
    > Note if there is any dll missing. Compare the dll versions too.
    >
    > Also, try checking the event log to see if you can get more details
    > on the problem.


    There's nothing in the event log (that's the first place I looked).

    Thanks for the good suggestions.

    It looks like the DLLs are the same for the two systems.
    (But the good system was a W2KS; my broken system is W2KP.)
    Actually, the broken one has more DLLs loaded:
    LgWndHk.dll and LgMsgHk.dll (Logitech hook/handler),
    ophook32.dll (some OCR thing - why this?),
    ole32.dll, OLEAUT32.dll (something for OLE?)
    VERSION.dll (MS?), LZ32.DLL (compression, maybe ???)

    The problem is not specific to Regedit -- the problem
    happens no matter what program is invoked.
    All applications launch and operate perfectly correctly.

    Maybe one of those "extra" DLLs is somehow the problem?

    How do those extra DLLs wind up getting loaded there, anyway?
    Maybe some kind of Registry entry causes them to get
    attached via some global hooking point?
    Maybe something else on that list is missing?
    (I don't really know how COM works or about the Registry,
    so I am just wildly guessing here.)

    What do you recommend I look at next?

  4. Re: CAN execute programs via the command prompt but get error

    Christopher C. Stacy wrote...

    >It looks like the DLLs are the same for the two systems.
    >(But the good system was a W2KS; my broken system is W2KP.)
    >Actually, the broken one has more DLLs loaded:
    >LgWndHk.dll and LgMsgHk.dll (Logitech hook/handler),
    >ophook32.dll (some OCR thing - why this?),
    >ole32.dll, OLEAUT32.dll (something for OLE?)
    >VERSION.dll (MS?), LZ32.DLL (compression, maybe ???)
    >
    >The problem is not specific to Regedit -- the problem
    >happens no matter what program is invoked.
    >All applications launch and operate perfectly correctly.
    >
    >Maybe one of those "extra" DLLs is somehow the problem?
    >
    >How do those extra DLLs wind up getting loaded there, anyway?
    >Maybe some kind of Registry entry causes them to get
    >attached via some global hooking point?
    >Maybe something else on that list is missing?
    >(I don't really know how COM works or about the Registry,
    >so I am just wildly guessing here.)
    >
    >What do you recommend I look at next?


    Try rename those "extra" dll's (maybe one at a time) to .dl_ ,
    and see the error will go away (or getting worse) when you
    run some programs.




+ Reply to Thread