Hi Viswanathan,
What would you like to achieve with your script. I've got a ton of experience writing and tweaking startup scripts. What would you like to do with them? If you don't need to do anything special, you can just use the standard files that come with Creo. They only start to come in handy when you need to do something special.
For instance, at my job, we have a "company-wide" config.pro and config.sup file that's maintained by me and the other support administrators. We needed a way that we would make a change and have it instantly "pushed out" to all users without having everyone loading Creo off a single server. By using a startup script, we're able to put those files into the hands of our users each time they launch Creo.
We have expanded our startup script so that we can now offer upgrades to users when they launch Creo. If they're not running the latest version, they can be prompted to upgrade. We haven't deployed this yet but it's an example of what you can do with a startup script.
What particular things would you like to do? I'll be happy to help.
Thanks!
-Brian