The service request was opened in March of 2006
The last email shows that you were informed that this would be turned into a feature request, since preserving the case sensitivity was not an option with shared folders. Feature requests are taken under consideration for a future release. It seems that you were given the workaround of using Samba, have you tried that for now as a work around?
We were promised (by email 10th april 2006) that
The status of your support request will be marked as "Pending/Problem Report"
until the feature request is closed.
Feature request # 100352 was apparently created. However you did not
keep your promise, because on 28th august 2007 (one and a half year
later) we receive an email saying
I am just cleaning the database and found this case being owned by a former
Would like to apologize for that and answer your question.
I wonder what question (I should answer) and how (the SR was closed)?
You can check the status of your SR's here:
I have also checked the status of your feature request.
It is not yet fixed because this behaviour is cause by the SAMBA project that
is having the same issue.
This obviously shows that the problem I originally filed has been
misunderstood. The problem is related to VMware Shared Folder. My description (which can be found on
refered to samba server because I thought/expected that VMware Shared Folders was basically a samba server, but I have been corrected in the SR communication, that VMware Shared Folders is a hgfs file system.
But there is a fix planned for WS 6.5
Well, I will probably try out the beta.
I am closing this SR as I don't think we need to research anything here
Interesting, especially because we didn't have a chance to comment on that; replying to firstname.lastname@example.org told us that the SR was closed, and any other direct communication required a support agreement.
I would love to see the SR reopened again until the feature request is closed, just as you promised 10th april 2006. Further I would like to have access to view the status of the feature request that you created upon this problem, I consider that good customer service.