Talk about SyMenu or post suggestions, requests, or how-to questions
	Line length Limit? 
		
	
 
		
		
	
	
		| laffin_boy Posts: 14 
 21/07/2023
 | Using SysMenu I've built a "Troubleshooting Tools"  "disk" to be able to work on other computers.  When I do so I want to begin by loading my normal desktop environment ( since an as-installed Windoze desktop is just about worthless).  And, once again, I have a problem with paths. 
 (1) I built a "Startup.cmd" file for the 6 apps I want to load - trying ".\Sysmenu|\App\App.exe" and "#:\SysMenu\App\App.exe"  for paths but when SysMenu passes these paths to CMD and CMD reads the file it doesn't have a drive to start from so it's lost.  And I can't specify a drive in advance.
 
 (2) So instead of pointing SM to an existing CMD file I used SM's own command option.  I linked all 6 commands together (with " & ") on a single line.  But that only starts 4 of the six apps because SM appears to have a string length limit for entering commands.  My full single line command is 381 characters long but if I attempt to "scroll" to the end of the line it only shows about 2/3 of it so I assume that there's some internal limit that cuts off the end of my command.
 
 So how can I manually (no autostart) start up  the 6 apps I want with one click?
 | 
	
		|  | link | 
	
	
		| Gianluca Administrator Posts: 1347 
 21/07/2023
 | Your first attempt is correct. If you don't want to use  Autoexec and want to execute a single application to start other six,  your option is to perfect the Startup.cmd file.
 
 Anyway  SyMenu (not SysMenu...) is in charge of starting Startup.cmd and, in that  context, it's able to use a relative path (.\) or the universal unit  path (#:\).
 
 But what Startup.cmd does after that moment is no more a SyMenu business.
 So inside Startup.cmd you can't use for sure #:\
 I  suggest you to work with relative path but you need to calculate the  relative path starting from the working folder of Startup.cmd
 
 
 Example
 SyMenu\ProgramFiles\Start\Startup.cmd
 SyMenu\ProgramFiles\P1\Prog1.exe
 SyMenu\ProgramFiles\P2\Prog2.exe
 
 If you start Startup.cmd with working folder .\ (its same folder) you can reach the two programs this way
 ..\P1\Prog1.exe
 ..\P2\Prog2.exe
 
 Hope this helps and please report the outcome.
 | 
	
		|  | link | 
	
	
		| laffin_boy Posts: 14 
 22/07/2023
 | Thanks. 
 Here's my SyMenu folder structure:
 
 .\SyMenu\x64\Category\App\app.exe
 and
 .\SyMenu\x64\Startup\Load_Desktop.cmd
 
 so once I changed the entries in my "Load_Desktop.com to:
 
 start ..\System\File_Sys\XYPlorer\XYplorer.exe
 start ..\Desktop\ClipCache\ClipCache_x64.exe
 
 etc
 Then everything worked like it does in the movies.
 
 
 In other words by using ".." in front of the address the command program is told to move back up one directory level - to the "x64" folder - from where it can now find the path to all of the apps.
 
 
 My problem here was understanding what the command program's working folder was - which has to do, I think, with how SyMenu "hands over" the cmd file to CMD.exe.
 
 
 BTW, sorry about renaming your program. SyMenu never made sense to me so I just decided  that it should be SysMenu and in the process of doing so I managed to convince myself that the program was named SysMenu.  ;^)
 | 
	
		|  | link |