Hi Scott, Sorry, I misunderstood your requirement and am not familiar with this part.
But, having had a quick look at the related files, it seems you will have to create a customized installer which copies over your customized files settings to the correct location. Based on your requirements, I think these would be the following files: %APPDATA%\Wireshark\disabled_protos %APPDATA%\Wireshark\preferences Or perhaps, it might be better to create a customized profile by creating a directory called %APPDATA%\profiles\custom_name and having these files there, and then asking users to switch to this profile when required. Abhik. On Wed, Aug 13, 2008 at 12:12 PM, <[EMAIL PROTECTED]> wrote: > > Hi Abhik, > I've looked at that - was hoping to find a config file I could tweak for > deployment, that would become the default profile on installation > > I've tweaked the services file so that my ports are detected correctly > just reading through the NSI file to see where it's copied from - or is it > generated on first run? > > Cheers > > Scott > > > > "Abhik Sarkar" <[EMAIL PROTECTED]> > Sent by: [EMAIL PROTECTED] > > 13/08/2008 08:25 > > Please respond to > Developer support list for Wireshark <wireshark-dev@wireshark.org> > To > "Developer support list for Wireshark" <wireshark-dev@wireshark.org> > cc > Subject > Re: [Wireshark-dev] Deploying 'default' properties with installation > > > > > Hi Scott, > > Have you already seen this: > http://www.wireshark.org/docs/wsug_html_chunked/ChCustConfigProfilesSection.html > > Abhik. > > On Wed, Aug 13, 2008 at 11:15 AM, <[EMAIL PROTECTED]> wrote: >> Hi guys >> I'm wondering what my options are in terms of preconfiguring an >> installation >> for a specific environment. >> We have our own custom dissector which is a stub of GIOP, and I'd like to >> disable PARLAY, TANGO and DNP 3 which can cause problems with our >> dissector. >> There are a couple of other tweaks to standard preferences for IP and TCP >> which I'd like to change too - >> Ideally I'd set up two new config profiles for the two modes (i.e. one for >> legacy code, one of current code reflecting our two plugins) >> Is this possible? >> >> Many thanks >> Scott >> >> >> _______________________________________________ >> Wireshark-dev mailing list >> Wireshark-dev@wireshark.org >> https://wireshark.org/mailman/listinfo/wireshark-dev >> >> > _______________________________________________ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > > > > -- > This e-mail is intended for the named addressees only. Its contents may be > privileged or confidential and should be treated as such. If you are not an > intended recipient please notify the sender immediately and then delete it; > do not copy, distribute, or take any action based on this e-mail. In the > pursuit of its legitimate business activities and its conformance with > relevant legislation, Quantel may access any e-mail (including attachments) > it originates or receives, for potential scrutiny. > > Quantel is the trade name used by Quantel Holdings Limited and its > subsidiaries. Quantel Holdings Limited is registered in England & Wales. > Registration No: 4004913 > Contact details for all Quantel Offices and Companies can be found on our > website www.quantel.com or by writing to the holding company. > Registered address: Turnpike Road, Newbury, Berkshire, RG14 2NX, United > Kingdom > _______________________________________________ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > > _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev