• Options
• Login
• Register
• Desktop Style
• Accelerated Mobile Pages Theme

Limitation when using QAP in a command line window (CMD)

• Index

  • Jean Lalonde Support Forum
  • QUICK ACCESS POPUP FORUM
  • QAP SUPPORT
  • Limitation when using QAP in a command line window (CMD)
• Limitation when using QAP in a command line window (CMD)

• Limitation when using QAP in a command line window (CMD)

  LaurentHaas > 2025-05-09 07:42

  Hi Jean
  
  When you use QAP in a “CMD” command line window, the directory change only works correctly if you are already on the correct drive. In fact, QAP only sends the command “CD {FolderPath}”, which fails if the current drive is different from the one specified in FolderPath. This has been the case for decades.
  
  The solution would be to send the command :
  
  {drive:} && CD {folderpath}
  
  for example:
  
  C: && CD “C:\Program Files”
  
  This way, regardless of the current drive, the command will first change the current drive to the FolderPath drive, then send a CD which will define the correct directory.
  
  This only affects the CMD.EXE command prompt, not the PowerShell console, which is unaffected, but I'm afraid you can't make the distinction in the code.

• RE: Limitation when using QAP in a command line window (CMD)

  LaurentG > 2025-05-09 09:24

  In which environment are you ?
  In W10 Pro at least, it works fine, switching drive then switching directory

• RE: Limitation when using QAP in a command line window (CMD)

  LaurentHaas > 2025-05-09 19:43

  I use Win11 24H2
  
  The command sent by QAP is :
  
  CD "Drive:\PathToTheFolder"
  
  but the drive can't switch in DOS cmd.exe (as explained earlier), so I remain in the current directory if my current drive is different from the one specified in the command.
  
  PS : After reviewing the code, it seems that the problem stems from the use of multi-tab Windows Terminal - wt.exe (which is the default terminal in Win11).

• RE: Limitation when using QAP in a command line window (CMD)

  LaurentG > 2025-05-10 08:24

  I just did a test, and I confirm what you say : In W11, contrary to what happens in W10, drive switching do not occur....
  And you are likely correct in your explanation : even if we explicitely launch cmd.exe, it actually starts wt.exe (that is not the case in W10)

• RE: Limitation when using QAP in a command line window (CMD)

  LaurentHaas > 2025-05-10 08:52

  Indeed.
  
  IMHO, the only way to deal with this problem is to adapt the QAP code to the Windows terminal and send a two-step command, to ensure compatibility between the “DOS command" prompt and the PowerShell prompt, which can be opened by the user :
  
  Drive:
  CD FullPath
  
  Unless you can distinguish between the two types of prompt (which I doubt).

• RE: Limitation when using QAP in a command line window (CMD)

  Jean Lalonde > 2025-05-10 10:19

  I'll test it later on Win11. But on Win 10, with a Folder favorite with the Location "O:\Temp", QAP is sending the command
  
  C:\>CD /D "O:\Temp"
  O:\Temp>
  
  Maybe the "/D" option doing the drive change on Win 10 is not supported by Windows Terminal on Win 11. I'll be back on this tomorrow when I have more time.

• RE: Limitation when using QAP in a command line window (CMD)

  LaurentHaas > 2025-05-10 10:28

  Hi Jean
  
  To sum up :
  
  1/ The Win11 Windows terminal is not currently recognized as a "cmd.exe" process, so the /D switch is not sent
  
  2/ The windows terminal is a multi-tab terminal where the user can choose between a "legacy DOS prompt", or a Windows PowerShell (or an Azure Cloud Shell - ignored for now). So, depending on the active tab, the command sent by QAP must be adapted (if you can distinguish what prompt is in the foreground - I doubt it), or you will have to send a command (or several commands in a row) that are compatible with both prompts.

• RE: Limitation when using QAP in a command line window (CMD)

  Jean Lalonde > 2025-05-10 22:02

  > 1/ The Win11 Windows terminal is not currently recognized as a "cmd.exe" process, so the /D switch is not sent
  
  This is true. If QAP would treats WindowsTerminal.exe as it does for CMD.exe, the issue would be easily solved... but only in CMD.exe tabs.
  
  There would remain an issue in PowerShell tabs. In these cases, the /D added by QAP cause an error (InvalidArgument).
  
  The solution, as you proposed, is to execute the command in two steps: 1) change drive (if a drive is specified in the location), 2) change folder.
  
  This is noted for the next bug fix release.
  
  Thank you for reporting this.

• RE: Limitation when using QAP in a command line window (CMD)

  Jean Lalonde > 2025-05-12 15:47

  This has been fixed in v11.6.4.4. Thanks for reporting this.
  
  See: https://forum.quickaccesspopup.com/showt...11#pid8311

• RE: Limitation when using QAP in a command line window (CMD)

  LaurentHaas > 2025-05-12 15:51

  Thank you !
• Next Oldest Next Newest