Questions

can I do this to XP-64 . . .

+
0 Votes
Locked

can I do this to XP-64 . . .

Who Am I Really
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Folder\shell\Cmd Prompt Here]

[HKEY_CLASSES_ROOT\Folder\shell\Cmd Prompt Here\command]
@="cmd.exe /k pushd %1"

I saw it here:
http://techrepublic.com.com/5208-13583-0.html?forumID=102&threadID=329711&messageID=3289985


I've been searching for a method to do this to an XP-64 system,

I've got a method I currently use to get to locations in command windows,
but it's four times as long and 3x the steps,
currently I have to;
a> open a normal command window
b> select the destination I wish to go to from the explorer address bar
c> in the command window do the following
-1> type: CD (space);
-2> Alt+Space (opens the window control menu);
-3> e (opens the edit sub-menu);
-4> p (pastes the contents of the clipboard);
-5> type the drive letter if necessary
  • +
    0 Votes
    TobiF

    Does the powertoy work on a 64bit system?
    http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx

    +
    0 Votes
    Who Am I Really

    things like;
    - Process Monitor
    - Process Explorer
    from the sys-internals suite
    actually spawn a 64-bit copy when run on XP-64

    but they're not really classified as powertoys


    I already have:
    - CmdHere.exe
    for XP
    as well as the older version
    - CmdHere.inf
    from the win2K resource-kit

    +
    0 Votes
    seanferd

    Just copy and paste this into a text file and name it CmdHere.inf. 64-bit should make no difference.

    -------------begin----------------

    ;
    ; "CMD Prompt Here" PowerToy
    ;
    ; Copyright 1996 Microsoft Corporation
    ;
    [version]
    signature="$CHICAGO$"

    [CmdHereInstall]
    CopyFiles = CmdHere.Files.Inf
    AddReg = CmdHere.Reg

    [DefaultInstall]
    CopyFiles = CmdHere.Files.Inf
    AddReg = CmdHere.Reg

    [DefaultUnInstall]
    DelFiles = CmdHere.Files.Inf
    DelReg = CmdHere.Reg

    [SourceDisksNames]
    55="CMD Prompt Here","",1

    [SourceDisksFiles]
    CmdHere.INF=55

    [DestinationDirs]
    CmdHere.Files.Inf = 17

    [CmdHere.Files.Inf]
    CmdHere.INF

    [CmdHere.Reg]
    HKLM,%UDHERE%,DisplayName,,"%CmdHereName%"
    HKLM,%UDHERE%,UninstallString,,"rundll32.exe syssetup.dll,SetupInfObjectInstallAction DefaultUninstall 132 %17%\CmdHere.inf"
    HKCR,Directory\Shell\CmdHere,,,"%CmdHereAccel%"
    HKCR,Directory\Shell\CmdHere\command,,,"%11%\cmd.exe /k cd ""%1"""
    HKCR,Drive\Shell\CmdHere,,,"%CmdHereAccel%"
    HKCR,Drive\Shell\CmdHere\command,,,"%11%\cmd.exe /k cd ""%1"""

    [Strings]
    CmdHereName="CMD Prompt Here PowerToy"
    CmdHereAccel="CMD &Prompt Here"
    UDHERE="Software\Microsoft\Windows\CurrentVersion\Uninstall\CmdHere"


    ------------end------------

    Tip:
    You should be able to right-click and paste into the cmd window. More fun available if you enable the Quick Edit mode.

    Further:
    http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/cmd.mspx?mfr=true on tweaking CMD behavior. All the fun registry stuff is here:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\ ... including path completion for commands.

    +
    0 Votes
    seanferd

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\Directory\shell\Command Prompt\Command]
    @="Cmd.exe /k cd \"%1\""

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\Command Prompt\Command]
    @="Cmd.exe /k cd \"%1\""

    ; edit:
    ; name it and hotkey option:

    [HKEY_CLASSES_ROOT\Directory\shell\Command]
    @="Commanding &Prompts"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\Command]
    @="Commanding &Prompts"


    ;Or the context menu item is "Command
    ;Prompt" with C as default hotkey. Hotkey
    ;follows the ampersand, given there is not
    ;conflicting windows hotkey

    +
    0 Votes
    santeewelding

    You know too much...

    +
    0 Votes
    seanferd

    With her or his hands, perhaps in a mirror?

    That was me and the Windows 95 registry.

    +
    0 Votes
    Who Am I Really

    combos to work since XP SP1

    I tried to get things to work that way with fresh installs of XP SP2, & SP3
    nope, nada, not happening, not responding, windows is ignoring me, . . . etc.

    I used to set these in win3.1x
    ie.
    ALT+F would pop the file manager open or bring it to the front as the active window
    ALT+M would pop open a DOS window
    ALT+W would pop Word-Perfect - but only from closed, if I tried it while it was open I'd get the lovely little dialog:
    "can't start the specified application"


    I have an older workstation that started with XP SP1 and is currently @ SP3
    I programmed those keys to pop my apps while it was still SP1
    ie.
    CTRL+Shift+N pops open notepad
    CTRL+Shift+R pops open Real Producer
    etc.

    the keys still function carried over into the SP updates

    but they don't even work on any system starting with SP2
    (and I've installed and configured several XP SP2 & SP3 installs)

    they can be assigned in the properties dialog for shortcuts but fail to do anything but fill up the Shortcut Key space in the properties dialog, and windows whines if I try and assign the same key combo to another prog.

    ie.
    CTRL+Shift+P is supposed to open mspaint but does nothing

    +
    0 Votes
    Who Am I Really

    I have that in the win2K resource kit
    big book about 3" thick 9" h x 7.25" w
    1,649 pages not including glossary & index which are another 116 pages

    came with a CD also

    +
    0 Votes
    seanferd

    Not sure which RK or version of Powertools I originally pulled it from.

    Posted that one before I'd seen anything but the OP since I hadn't refreshed the page. Weird that 64-bit is actually that picky about this.

    I think the reg entries are supposed to work, though.

    If they don't, try it by adding cmd.exe /k cd "%1" as a command to Folder under Folder Options - File Types.

    Some of those books are thick enough to stun an ox.

    +
    0 Votes
    Who Am I Really

    I'm not anywhere near the machine again until next week, so I can't test the ideas yet

    cheers

    +
    0 Votes
    Who Am I Really

    here's the plan:

    I have an idea,

    I exported the registry keys from an XP-32 system with the
    Command Prompt Here
    PowerToy installed

    the keys are as follows:

    Key 1
    _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\cmd]
    @="Open Command Window Here"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\cmd\command]
    @="cmd.exe /k \"cd %L\""
    _____________________________________________

    Key 2
    _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Drive\shell\cmd]
    @="Open Command Window Here"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Drive\shell\cmd\command]
    @="cmd.exe /k \"cd %L\""
    _____________________________________________

    if all goes well I'll post back

    +
    0 Votes
    seanferd

    Hope it works for you.

    +
    0 Votes
    Who Am I Really

    I just got brave and tried it !!

    using the two (posted previously) exported keys from XP-32 system,
    with the Command Prompt Here Powertoy installed

    I now have a functional Command window here context menu Item on XP-64
    which opens the correct cmd.exe for XP-64 (not the cmd.exe *32)

  • +
    0 Votes
    TobiF

    Does the powertoy work on a 64bit system?
    http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx

    +
    0 Votes
    Who Am I Really

    things like;
    - Process Monitor
    - Process Explorer
    from the sys-internals suite
    actually spawn a 64-bit copy when run on XP-64

    but they're not really classified as powertoys


    I already have:
    - CmdHere.exe
    for XP
    as well as the older version
    - CmdHere.inf
    from the win2K resource-kit

    +
    0 Votes
    seanferd

    Just copy and paste this into a text file and name it CmdHere.inf. 64-bit should make no difference.

    -------------begin----------------

    ;
    ; "CMD Prompt Here" PowerToy
    ;
    ; Copyright 1996 Microsoft Corporation
    ;
    [version]
    signature="$CHICAGO$"

    [CmdHereInstall]
    CopyFiles = CmdHere.Files.Inf
    AddReg = CmdHere.Reg

    [DefaultInstall]
    CopyFiles = CmdHere.Files.Inf
    AddReg = CmdHere.Reg

    [DefaultUnInstall]
    DelFiles = CmdHere.Files.Inf
    DelReg = CmdHere.Reg

    [SourceDisksNames]
    55="CMD Prompt Here","",1

    [SourceDisksFiles]
    CmdHere.INF=55

    [DestinationDirs]
    CmdHere.Files.Inf = 17

    [CmdHere.Files.Inf]
    CmdHere.INF

    [CmdHere.Reg]
    HKLM,%UDHERE%,DisplayName,,"%CmdHereName%"
    HKLM,%UDHERE%,UninstallString,,"rundll32.exe syssetup.dll,SetupInfObjectInstallAction DefaultUninstall 132 %17%\CmdHere.inf"
    HKCR,Directory\Shell\CmdHere,,,"%CmdHereAccel%"
    HKCR,Directory\Shell\CmdHere\command,,,"%11%\cmd.exe /k cd ""%1"""
    HKCR,Drive\Shell\CmdHere,,,"%CmdHereAccel%"
    HKCR,Drive\Shell\CmdHere\command,,,"%11%\cmd.exe /k cd ""%1"""

    [Strings]
    CmdHereName="CMD Prompt Here PowerToy"
    CmdHereAccel="CMD &Prompt Here"
    UDHERE="Software\Microsoft\Windows\CurrentVersion\Uninstall\CmdHere"


    ------------end------------

    Tip:
    You should be able to right-click and paste into the cmd window. More fun available if you enable the Quick Edit mode.

    Further:
    http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/cmd.mspx?mfr=true on tweaking CMD behavior. All the fun registry stuff is here:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\ ... including path completion for commands.

    +
    0 Votes
    seanferd

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\Directory\shell\Command Prompt\Command]
    @="Cmd.exe /k cd \"%1\""

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\Command Prompt\Command]
    @="Cmd.exe /k cd \"%1\""

    ; edit:
    ; name it and hotkey option:

    [HKEY_CLASSES_ROOT\Directory\shell\Command]
    @="Commanding &Prompts"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\Command]
    @="Commanding &Prompts"


    ;Or the context menu item is "Command
    ;Prompt" with C as default hotkey. Hotkey
    ;follows the ampersand, given there is not
    ;conflicting windows hotkey

    +
    0 Votes
    santeewelding

    You know too much...

    +
    0 Votes
    seanferd

    With her or his hands, perhaps in a mirror?

    That was me and the Windows 95 registry.

    +
    0 Votes
    Who Am I Really

    combos to work since XP SP1

    I tried to get things to work that way with fresh installs of XP SP2, & SP3
    nope, nada, not happening, not responding, windows is ignoring me, . . . etc.

    I used to set these in win3.1x
    ie.
    ALT+F would pop the file manager open or bring it to the front as the active window
    ALT+M would pop open a DOS window
    ALT+W would pop Word-Perfect - but only from closed, if I tried it while it was open I'd get the lovely little dialog:
    "can't start the specified application"


    I have an older workstation that started with XP SP1 and is currently @ SP3
    I programmed those keys to pop my apps while it was still SP1
    ie.
    CTRL+Shift+N pops open notepad
    CTRL+Shift+R pops open Real Producer
    etc.

    the keys still function carried over into the SP updates

    but they don't even work on any system starting with SP2
    (and I've installed and configured several XP SP2 & SP3 installs)

    they can be assigned in the properties dialog for shortcuts but fail to do anything but fill up the Shortcut Key space in the properties dialog, and windows whines if I try and assign the same key combo to another prog.

    ie.
    CTRL+Shift+P is supposed to open mspaint but does nothing

    +
    0 Votes
    Who Am I Really

    I have that in the win2K resource kit
    big book about 3" thick 9" h x 7.25" w
    1,649 pages not including glossary & index which are another 116 pages

    came with a CD also

    +
    0 Votes
    seanferd

    Not sure which RK or version of Powertools I originally pulled it from.

    Posted that one before I'd seen anything but the OP since I hadn't refreshed the page. Weird that 64-bit is actually that picky about this.

    I think the reg entries are supposed to work, though.

    If they don't, try it by adding cmd.exe /k cd "%1" as a command to Folder under Folder Options - File Types.

    Some of those books are thick enough to stun an ox.

    +
    0 Votes
    Who Am I Really

    I'm not anywhere near the machine again until next week, so I can't test the ideas yet

    cheers

    +
    0 Votes
    Who Am I Really

    here's the plan:

    I have an idea,

    I exported the registry keys from an XP-32 system with the
    Command Prompt Here
    PowerToy installed

    the keys are as follows:

    Key 1
    _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\cmd]
    @="Open Command Window Here"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\cmd\command]
    @="cmd.exe /k \"cd %L\""
    _____________________________________________

    Key 2
    _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Drive\shell\cmd]
    @="Open Command Window Here"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Drive\shell\cmd\command]
    @="cmd.exe /k \"cd %L\""
    _____________________________________________

    if all goes well I'll post back

    +
    0 Votes
    seanferd

    Hope it works for you.

    +
    0 Votes
    Who Am I Really

    I just got brave and tried it !!

    using the two (posted previously) exported keys from XP-32 system,
    with the Command Prompt Here Powertoy installed

    I now have a functional Command window here context menu Item on XP-64
    which opens the correct cmd.exe for XP-64 (not the cmd.exe *32)