kix32 /n myscript.kix

This undocumented parameter was great for local script which doesn't need network information. For example: a script to check the user's settings without login.

However, the new version 3.60 still accept the /n parameter, but if you try it without the ethernet cable plugged in, Kix will just hang... And plug the cable back in and it will continue processing your script...

I don't understand why such a change in behavior, but it's really annoying for me. So, if someone could explain that for me, it would be a real answer for my problems...