Promise VTrak M500f/Support Case Log: Difference between revisions

From fakedWiki
Jump to: navigation, search
No edit summary
m (8 revisions imported)
 
(4 intermediate revisions by the same user not shown)
Line 183: Line 183:


ah, fuck it, you won't understand it anyway.|Request:-  |3rd August 2011 at 5:35}}
ah, fuck it, you won't understand it anyway.|Request:-  |3rd August 2011 at 5:35}}
----
Let's call Promise's german marketing department... and voila, after that:
----


{{Quote|We do appreciate that you found a problem with our system. This system is already discontinued and we do not plan the updates.
{{Quote|We do appreciate that you found a problem with our system. This system is already discontinued and we do not plan the updates.
Line 222: Line 229:
Now you're more specific. We could more constructive dialog from the beginning. I will need to perform some tests and I will contact you again with the results.
Now you're more specific. We could more constructive dialog from the beginning. I will need to perform some tests and I will contact you again with the results.


As for information that you ask, I could not provide it to you now because this information is confidential.
As for information that you ask, I could not provide it to you now because this information is confidential.|Response By:- Sergiy Voskoboynikov |5th August 2011 at 3:14}}


Request:-  5th August 2011 at 3:30
{{Quote|Well, we could have gotten there a lot faster and easier if you wouldn't have tried to convince me that this is because of faulty hardware - which i pointed out to you multiple times by telling you to read my previous messages.
{{Quote|Well, we could have gotten there a lot faster and easier if you wouldn't have tried to convince me that this is because of faulty hardware - which i pointed out to you multiple times by telling you to read my previous messages.


Line 230: Line 236:
Now if i wouldn't have to find out myself how to get them, but just get them, there's nothing i could publish, right?
Now if i wouldn't have to find out myself how to get them, but just get them, there's nothing i could publish, right?


On a sidenote, where do you provide the sourcecode for your firmware? As you're using GPL licensed code, you MUST release the corresponding source code, in case you didn't know... a good starting point: http://gpl-violations.org/faq/vendor-faq.html|Response By:- Sergiy Voskoboynikov |5th August 2011 at 3:14}}
On a sidenote, where do you provide the sourcecode for your firmware? As you're using GPL licensed code, you MUST release the corresponding source code, in case you didn't know... a good starting point: http://gpl-violations.org/faq/vendor-faq.html|Request:- |5th August 2011 at 3:30}}
 
{{Quote|Hi Jan,
 
My name is Richard Payne and I'm a Promise FAE.
 
I'm sorry for the communication issues that came before, but technical support was not aware of this issue.
 
This is a known issue that has been fixed in all current products. The fix has not been back-ported to EOL products. I will do what I can and file a bug for this issue against the M500x.
 
You are correct that this is not a hardware issue.|Response By:- Richard Payne|5th August 2011 at 10:31}}

Latest revision as of 21:10, 26 August 2016