On 4/20/07, <b class="gmail_sendername">Olivier</b> <<a href="mailto:oza-4h07@myamail.com">oza-4h07@myamail.com</a>> wrote:<div><span class="gmail_quote"></span><div><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div>Are you sure eyeBeam config are binary ?<br>I thought it was just the case for XLite.</div></div></blockquote><div><br>Having looked into it further, you're right. For some inexplicable reason it's not putting the files where the manual says they should be - instead of a directory called "eyeBeam
n.n" they're in a folder called 'RegNow Basic', but the .CPS files there are indeed in XML rather than binary format. When I last looked, I suspect I assumed that eyeBeam stored it's configs in the X-Lite directory and was thus looking at the configs for the free version that were no longer being accessed.
<br><br>That does help a little for provisioning, as I can at least generate the configs and then place them someone central, but actually getting them to the phone is still kludgey. Since they are in the Local Settings folder, they can't be made part of a roaming profile. I've tried moving the CounterPath directory from "\Documents and Settings\username\Local Settings\Application Data" to "\Documents and Settings\username\Application Data", but the phone never references the configs held there. Right now (with X-Lite) i'm configuring each phone manually, then zipping up the configs and storing them in a location named for the windows username. On login, the zipfile is fetched and unzipped to the right location. Inelegant to be sure, but it works. XML just saves me having to do the configuration manually.
<br><br>In any case, this is now going down an OT path - I'll take it up with CounterPath on their forums. Thanks for the pointer.<br><br></div><br></div>