[missing-sync-pocketpc-talk] Re: Bluetooth

[Craig Simmons]

I found the threats an interesting touch to get a response from 
Mark/Space, but I think it is bogus to threaten and then say that you 
will stick with the product for a while. I have also had problems with 
the product, but the problems are connected to issues that Mark/Space 
could not have foreseen.

First of all, when I had first experienced problems with my Dell Axim 
failing to connect, it carried similar problems that others have 
reported. In my case the problem turned out to be that when my computer 
was set to dhcp, the system would do a reverse name lookup and come up 
with a different name then my actual machine. This confused Missing 
Sync, because 1 minute it would use my machine name and the other, it 
would use the dhcp assigned name, I believe, causing the connection to 
fail. By setting my machine to a non-dhcp number, this cured the 
problem, but I can see that I'm not alone. If Mark/Space can resolve 
this issue, this will probably resolve these other issues.

Just a suggestion,

Craig.

On Nov 11, 2003, at 8:47 PM, Brian Hall wrote:

>> I'll stick with Missing Sync for a while but it needs to measure up
>> to its promise or the switch could be occur
>
> To be fair here, what is it you think we promised and didn't include?
>
> There was a mixup with the 1.0 press release where we mentioned 
> bluetooth,
> but it wasn't in 1.0. We added that for 1.0.1 a month after the 1.0 
> release.
>
> We have always been up-front that we do not yet support Entourage, and 
> that
> if Entourage support is a requirement, this product is not *yet* for 
> you.
>
> (We can not state a date at this time, but we have been/already are 
> working
> on it).
>
> We have a software engineer working on the reported Bluetooth and "I
> upgraded to Panther" issues. It should be noted that while these issues
> seem to be very vocal on this discussion list, the number of people 
> that
> have reported the problem is very small (<1%). I realize this is little
> consolation if you are one of those people whom are effected, but I 
> also
> want to put it into perspective. We tested with Panther on a variety of
> machines before Panther was released and at release, and did not see 
> these
> issues ourselves. The hardest part of being able to address an issue is
> being able to reproduce it on our own systems (unless you happen to be
> local to one of our engineers and we can check out your system in 
> person).
>
> While we (mark/space employees) don't respond to every message on this
> list, we do read all of them and take your feedback and comments into
> account.
>
> Related to that...
>
> The best way to get a bug logged in our database and have an engineer
> assigned to it is to send a complete report to support at markspace.com
>
> Brian
>
> -- 
> _____________________________________________________________________
> Mark/Space, Inc.                                   voice 408-293-7299
> 540 N. Santa Cruz Ave. #300                          fax 408-293-7298
> Los Gatos, CA 95030                        <http://www.markspace.com>
> _______________________________________________
> missing-sync-pocketpc-talk mailing list
> missing-sync-pocketpc-talk at lists.markspace.com
> Unsubcribing information, subscription options and list archives can 
> be found at:
> http://lists.markspace.com/mailman/listinfo/missing-sync-pocketpc-talk
>