Thanks pryrt - I couldn't carry out that test as the laptop I am currently using doesn't have Perl installed
Perhaps start was needed just to allow a relative directory for the icon file.
| [reply] |
Perhaps start was needed just to allow a relative directory for the icon file.
Nope, even if I have the full path to the icon file, I still needed the start.
My guess was actually because I was running from an existing cmd.exe console, so maybe there are some things you're not allowed to change on that window.
If I run the similar command from the Win+R Run menu, without the start and with full path to the icon, it also works -- again, it's creating a fresh console window rather than relying on a pre-existing window.
If I put it into a batch file, which I run perl (without the start prefix) from either the cmd.exe window or from double-clicking via explorer, then it does change the icon for either. And when the batch file is done, the window continues to use the new icon. Interesting.
Anyway, hope this helps the OP.
| [reply]
[d/l]
[select] |
My guess was actually because I was running from an existing cmd.exe console, so maybe there are some things you're not allowed to change on that window.
An existing console window does have some limitations on what is permitted. So your guess is very plausible. I can't recall exactly what the limitations are but changing the icon could very well be one.
| [reply] |
| [reply] |