
12-08-2009 06:26 PM
good example. the question is: how did you find out about the issue and that it was related to the update? was it something your company found upon testing and then re-released the old code to make the machines work again? or did you guys find it out from the customer? if you found it in your testing, you would know there is something wrong. imagine if one of your customers had a machine, told you there was something wrong after the update but did not return the machine to you (or have you guys come out there) how would you know what the issue is?
charettepa wrote:
oneDMAC wrote:
Wow 30 min is a fast turn around. Is your companies software as complex? Is there even enough time to properly test it? And on top of that if they are investigating the issue don't you think it would be in their best interest to investigate those who are blaming the FW for their BD no longer functioning? I would think that the BD issue is the worst of the 2 and should be handled first. The truth is none of us really know for sure what they are doing. Nor do we know why the BT syncing only affects some with a slim and not all. Same thing goes for the BD issue.
our software can be quite complex
it is used to abstract and capture patient flow in hospitals
like i said there is nothing to test
its a rollback
example
release 3.1
release 3.2
3.2 causes issue
re-release 3.1 as 3.1b which has the right to install over 3.2
this temporarily resolves the issue while we fix the problem
12-08-2009 06:43 PM
autohacker2000 wrote:good example. the question is: how did you find out about the issue and that it was related to the update? was it something your company found upon testing and then re-released the old code to make the machines work again? or did you guys find it out from the customer? if you found it in your testing, you would know there is something wrong. imagine if one of your customers had a machine, told you there was something wrong after the update but did not return the machine to you (or have you guys come out there) how would you know what the issue is?
charettepa wrote:
oneDMAC wrote:
Wow 30 min is a fast turn around. Is your companies software as complex? Is there even enough time to properly test it? And on top of that if they are investigating the issue don't you think it would be in their best interest to investigate those who are blaming the FW for their BD no longer functioning? I would think that the BD issue is the worst of the 2 and should be handled first. The truth is none of us really know for sure what they are doing. Nor do we know why the BT syncing only affects some with a slim and not all. Same thing goes for the BD issue.
our software can be quite complex
it is used to abstract and capture patient flow in hospitals
like i said there is nothing to test
its a rollback
example
release 3.1
release 3.2
3.2 causes issue
re-release 3.1 as 3.1b which has the right to install over 3.2
this temporarily resolves the issue while we fix the problem
this isnt just one client
everyone with a slim is reporting the issue
yet they still deny it weeks later
12-08-2009 06:58 PM
that's not what i was asking
charettepa wrote:
autohacker2000 wrote:
good example. the question is: how did you find out about the issue and that it was related to the update? was it something your company found upon testing and then re-released the old code to make the machines work again? or did you guys find it out from the customer? if you found it in your testing, you would know there is something wrong. imagine if one of your customers had a machine, told you there was something wrong after the update but did not return the machine to you (or have you guys come out there) how would you know what the issue is?
this isnt just one client
everyone with a slim is reporting the issue
yet they still deny it weeks later
12-08-2009 07:43 PM
charettepa wrote:THE PROBLEM IS NOT THE PS3 IT IS THE FIRMWARE
I HAVE GONE BACK TO THE STORE AND RETURNED 3X
IT WORKS THEN I APPLY THE 3.1 FIRMWARE THEN I HAVE THE INTERMITANT BLUETOOTH SYNC ISSUE
ALL SLIM OWNERS HAVE THE SAME ISSUE
BUT SONY WONT ACCEPT THIS FACT
There is no across-the-board problem with the 3.1 firmware. Do not make blanket statements. And ALL Slim owners do not have "the same issue". Again ... blanket statements ...bad. You are frustrated, we know, but you have not been elected to represent anyone other than yourself. Just sayin'.