MRT - Some Suggestions [ Take Them or Leave Them ]
Posted: March 24th, 2020, 5:53
Well,
I think the ladies out there " or males pretending to be ladies " , Sorry but this is quite common in china , You people need to sit back a little and appreciate suggestions that pour out in HDDguru , I do not see were your staff actually helps anyone on the forums ,Other then making marketing posts .I have personally gone through hell when i tried to fight back with MRT guys that they sold me 2 Card updates and never kept thier promise of free software update ,I will make a specific thread on HDDguru for that ,Anyways the current thing is this ,This is what i feel ...
1 : Beta Testers : I would suggest you find who are your real users ,who can test software on many many different drives ,Most of your resellers are just your marketing agencies without much knowledge of data recovery .Example in every country or few of the countries you should have beta testers who get your tool free and they use it and report back on things they tested .Example india is a big country , every zone has a different bunch of drives that sell more there ,So you can have a few here ,In smaller countries might be one guy or company ,This will really help to refine the tool
2 : Company policy change : Why not take a poll of the changes you plan to go for thier entire userbase ,before you implement it ,I would really appreciate if you could have a sticky post that talks about current company policies ,Example if someone buys your tool how much period you provide hardware warranty , how much period you provide software support and updates ,Whats your support policy etc etc
PS : You guys released the Ver 2141 update after users like me started cribbing about headmap etc issues with MRT Labs for slyplass series ,That issue is solved but i would like to ask do you guys really never test your tool in beta test ,Charger headmap starts halts at 50 odd percent ,The tool crashes when trying to read Mod 190 in charger ,It literally crashed possibly its a large mod and your internal array buffers when you codded get full creating appcrash .I mean really give some of us the opportunity to refine the tool please
I think the ladies out there " or males pretending to be ladies " , Sorry but this is quite common in china , You people need to sit back a little and appreciate suggestions that pour out in HDDguru , I do not see were your staff actually helps anyone on the forums ,Other then making marketing posts .I have personally gone through hell when i tried to fight back with MRT guys that they sold me 2 Card updates and never kept thier promise of free software update ,I will make a specific thread on HDDguru for that ,Anyways the current thing is this ,This is what i feel ...
1 : Beta Testers : I would suggest you find who are your real users ,who can test software on many many different drives ,Most of your resellers are just your marketing agencies without much knowledge of data recovery .Example in every country or few of the countries you should have beta testers who get your tool free and they use it and report back on things they tested .Example india is a big country , every zone has a different bunch of drives that sell more there ,So you can have a few here ,In smaller countries might be one guy or company ,This will really help to refine the tool
2 : Company policy change : Why not take a poll of the changes you plan to go for thier entire userbase ,before you implement it ,I would really appreciate if you could have a sticky post that talks about current company policies ,Example if someone buys your tool how much period you provide hardware warranty , how much period you provide software support and updates ,Whats your support policy etc etc
PS : You guys released the Ver 2141 update after users like me started cribbing about headmap etc issues with MRT Labs for slyplass series ,That issue is solved but i would like to ask do you guys really never test your tool in beta test ,Charger headmap starts halts at 50 odd percent ,The tool crashes when trying to read Mod 190 in charger ,It literally crashed possibly its a large mod and your internal array buffers when you codded get full creating appcrash .I mean really give some of us the opportunity to refine the tool please