Are there any risks when renaming programs to a name that's already taken by another program?
Okay, some context is definitely needed. In my animation and video game design class, we occasionally get free time to do whatever on the computers. A
Okay, some context is definitely needed. In my animation and video game design class, we occasionally get free time to do whatever on the computers. A common thing we like to do is play a game called "Xonotic". However, a blocking program named "LanSchool" has begun to close out the game whenever we open it, as well as any other application.
I eventually found a way to bypass this, as the program is relatively simple. It goes by a whitelist on the programs' names. For example, Google Chrome is unblocked because the .exe is named "chrome.exe", which is on the whitelist. Thus, renaming "Xonotic" to "chrome" allows us to play the game without it being closed.
The teacher was fine with this, but recently he found out that we were renaming the program, and said that it might have some long-term effects of the computer's memory. I've had trouble actually finding anything saying that it does, but I haven't found anything that has said that it doesn't either.
The teacher isn't sure if he's correct either, but he said to not rename anything until we've figured out if it's a problem or not.
or:Okay, some context is definitely needed. In my animation and video game design class, we occasionally get free time to do whatever on the computers. A common thing we like to do is play a game called \"Xonotic\". However, a blocking program named \"LanSchool\" has begun to close out the game whenever we open it, as well as any other application.I eventually found a way to bypass this, as the program is relatively simple. It goes by a whitelist on the programs' names. For example, Google Chrome is unblocked because the .exe is named \"chrome.exe\
