|
SvenH Posts: 27
23 days ago
|
Hello!
See the attached gif files (had to record two files due to the size limitation). The error message states that the path is not found. The problem with Unicode should be solved, right?
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
23 days ago
|
Indeed the solved problem was not related to Unicode character but with special characters I escaped because of the Windows shell needs. If I well remember you had a problem with ampersand (&) character but the problem affected even other chars like parentesis ( and ).
Now we have a different problem but, as usual, it's strange. Why other items work well and that particular one doesn't? For example I guess that ".Skapa * Anteckningar" works well, doesn't it?
Is it something tied with the shortcut rather than SyMenu?
|
|
|
link
|
|
SvenH Posts: 27
22 days ago
|
Yes, it works for ".Skapa⭐ Anteckningar". But one difference is that ".Skapa⭐ Anteckningar" gets item "Program" while ".Skapa⭐ Office - Access" gets item "Document".
The links work outside SyMenu, but the properties of the links also look different, see the image.
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
22 days ago
|
Everything seems so strange to me.
I created a shortcut to a program.
Then I renamed it as ".Skapa⭐ Anteckningar".
Then I drop the shortcut on SyMenu.
As expected SyMenu takes the shortcut and tries to understand what's that thing.
It opens the shortcut (the shortcut properties indeed), finds the target (the program full path), and creates a logical item inside its menu representing the target program not the shortcut.
The only remnant of the old shortcut is its name because that name is used to name the SyMenu item.
In your case instead it seems that SyMenu creates its item linking the shortcut.
This is the problem. The problem is not the error during the item execution but the lacking resolution during the creation of the item.
When you d&d a shortcut to SyMenu you should see in the Path field the program path, not the shortcut's.
Since I'm not able to reproduce the problem I have to ask you for some help.
You should d&d a shortcut in SyMenu and check the Path. If the path is the shortcut's, you should change something on the shortcut and try again, until you find what is breaking the system.
You can try to change the shortcut location, name, attributes... whatever. When you know for sure what's the problem I can fix it.
|
|
|
link
|
|
SvenH Posts: 27
22 days ago
|
Don't really know what I should be able to change in Properties for the Shortcut. Do you have any suggestion? Could you test if you got my shortcut?
I have another problem with SyMenu not finding all programs on %windir%\system32\. Do you want me to create another case for that?
(It was ".Skapa⭐ Office - Access" that didn't work, you accidentally typed ".Skapa⭐ Anteckningar".)
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
22 days ago
|
Well... not a clear idea as I previously told you but, when I have no idea on how the bug is, I proceed step by step.
Let's make an example.
I have a program like this:
D:\\.xy⭐ zk - 00\.xy⭐ zk - 00.exe
and the related shortcut:
C:\Users[user]\AppData\Roaming\Microsoft\Windows\Start Menu\.xy⭐ zk - 00.lnk
If I'm sure the shortcut works on Windows, my first attempt would be to add that shortcut to SyMenu and check the path SyMenu gets doesn't point to the shortcut but to the program.
If it doesn't I have my bugged case.
1) attempt:
- rename the folder using only ANSI chars getting D:\\.xy zk - 00\.xy⭐ zk - 00.exe
- create a new shortcut
- try to import in SyMenu and check the path
If I still have the problem..
2) attempt:
- rename the file using only ANSI chars getting D:\\.xy zk - 00\.xy zk - 00.exe
- create a new shortcut
- try to import in SyMenu and check the path
If I still have the problem it means the UTF8 has nothing to do with the bug. So rename path and program as they were before and go ahead
3) attempt:
- check the Windows permissions on the shortcut and the program
- compare the permissions with another item working on SyMenu
- as before if the permissions are different try to change them and check if it works
And so on.
In other words you have to fix the problem by trial and error to understand what the problem is.
The problem with the system32 folder is a well known one. It depends on the Windows permissions on those folders and files.
If an executable is not working or not showing in SyMenu try to make its permissions more loose.
I'm very sorry for not being able to help you more but everything works on my PC even with the strangest cases I tested.
|
|
|
link
|
|
SvenH Posts: 27
22 days ago
|
Unfortunately removing the star in the name made no difference and in terms of permissions it makes no difference if I compare to Notepad (see image). But I can proceed by registering the program manually instead.
As for System32, I try to register the program manually, but since it doesn't appear in SyMenu's file list, it doesn't work. In this case, it applies to the SnippingTool, which is not shown in the file list. I have compared its permissions with the Notepad permission, which appears in SyMenu's file list, without finding any difference, see the second image.
I fully understand that it is difficult for you to find a fault when it works for you!
 
|
|
|
link
|