EDIT: with the advent of the native client launcher, and the death of Java Web Start, This entire thread is somewhat defunct. However, if you want to replace the shell, here is the TLDR version. [quote=“JordanCClark, post:17, topic:3979”]
If your project has a desktop icon, you can copy the contents of the target field into the registry key value.
For those playing along at home we had a topic here and other places discussing auto-launching a client and all the associated problems with it-- like people messing around with the 'puter and doing things they shouldn’t.
So, to get around all this, I’ve written an executable (in AutoIt, if anyone’s interested) to replace the Windows shell (explorer.exe). I’ve tested this on XP and Windows 7 without issue, but, Windows being Windows, your mileage may vary… I stuck a youtube vid to show it in action.
Before I go on, I will say that my anti-virus (Vipre) tagged the executable as a trojan. This is a false positive because of stupid malicious hacker-types (as opposed to me-- I only use my powers for good) doing stupid things to other people with their stupid code. This got tagged because we’re doing network calls, and then executing external code (the Ignition client). Other antivirus software may or may not tag it as well. If it does, let me know which ones, along with what it got tagged as, so I can submit there as well. I’ve submitted the .exe to Vipre, and should get cleared up in a day or two. I’ve added to source code so you can see what I’m doing.
EDIT (2013-09-05): I’ve submitted the file to VirusTotal. Here are the results.
Now this involves registry editing, and not necessarily for the faint of heart. The usual rules of “change at your own risk” is in full force. I recommend backing it up, just in case.
The zip file contains four files:
[ul]IgnitionShell.exe: the actual shell
ignition.ini: this ini file holds vital settings-- like where the server is and what project you’re running…
Ignition Shell.au3– source code. feel free to play with, improve, whatever. I’m not squeamish.
shell.reg: registry file to help with the one registry change you’ll need.
The .exe and .ini need to go into the C:windows/system32/ folder. This is squarely in the path of the search for executables, and for some reason, the shell couldn’t ever find the ini file until I explicitly told it where it was. So I picked the system32 folder. Put them both there and you’re good to go.
Next modify the ini file to reflect your setup. More details are in the ini file itself.
Now, you can either run regedit and go to the following key:
and change the entry from explorer.exe to Ignition_shell.exe
click on the .reg file and let it do it for you. Your choice! You can right-click on the file and pick Edit to see the contents beforehand.
Reboot and let 'er rip!
The good thing about this setup is that the new shell starts checking the server status right away and with no explorer.exe running, there’s nothing to click on-- a kiosk mode, if you want to call it that. I even made the status window non-clickable. And, you can still Ctrl-Alt-Del your way into the task manager and manually run explorer, regedit, Ignition_shell, whatever, if needed.
Ignition_shell.zip (283 KB)