MRT - Some Suggestions [ Take Them or Leave Them ]

[Amarbir[CDR-Labs]]

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

[lcoughey]

I'm beginning to wonder if they are even in business any more.

[Amarbir[CDR-Labs]]

I'm beginning to wonder if they are even in business any more.

Well,
The international sales are being destroyed by those men or girls who are irresponsible and do not know how to run the show ,I wish i was employed by this stupid company then might be i could show them how to handle international sales .

[lcoughey]

All my suggestions have fallen on deaf ears.

[HaQue]

I think you could have left out some of the first sentence...

[Amarbir[CDR-Labs]]

I think you could have left out some of the first sentence...

No,
I am serious ,I really mean because i have observed and been in communication ,You are taking it in different sense i have fully experienced it

[ccc]

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

Hi Amarbir

Can you tell me how it is solved?.....I have here 2 WD40NMZW-11GX6S1 spyglass drives that I try to do HM in RAM but it does not work.They both have diferent firmware problems and I want to try to fix the problem using HM in RAM. Here is the log:

Obtaining headmap data from RAM
Read code address map : ........................:Success
Code base address : ............................: 0xFFE67800
Code length : ..................................: 0x10000
Read code : ....................................:Success

key code type : ................................: 0
failed to search

key code type : ................................: 8
failed to search

key code type : ................................: 9
failed to search

key code type : ................................: 7
failed to search

key code type : ................................: 10
failed to search

key code type : ................................: 1
failed to search

key code type : ................................: 2
failed to search

key code type : ................................: 3
failed to search

key code type : ................................: 5
failed to search

key code type : ................................: 6
failed to search

key code type : ................................: 4
failed to search
Code base address : ............................: 0xFFE08230
Code length : ..................................: 0x10000
Read code : ....................................:Success

key code type : ................................: 0
failed to search

key code type : ................................: 8
failed to search

key code type : ................................: 9
failed to search

key code type : ................................: 7
failed to search

key code type : ................................: 10
failed to search

key code type : ................................: 1
failed to search

key code type : ................................: 2
failed to search

key code type : ................................: 3
failed to search

key code type : ................................: 5
failed to search

key code type : ................................: 6
failed to search

key code type : ................................: 4
failed to search
Code base address : ............................: 0xFFE00000
Code length : ..................................: 0x50000
Read code : ....................................:Success

key code type : ................................: 0
failed to search

key code type : ................................: 8
failed to search

key code type : ................................: 9
failed to search

key code type : ................................: 7
failed to search

key code type : ................................: 10
failed to search

key code type : ................................: 1
failed to search

key code type : ................................: 2
failed to search

key code type : ................................: 3
failed to search

key code type : ................................: 5
failed to search

key code type : ................................: 6
failed to search

key code type : ................................: 4
failed to search
Code base address : ............................: 0x1081A800
Code length : ..................................: 0x50000
Get headmap data : .............................: Failed


When the "Code base address : ............................: 0x1081A800" appears the hdd makes a loud click and resets itself (and it's firmware of course)...I believe is an illegal address request or something else.

So , how did you solve it? Am I doing something wrong? Is there a trick ?

Thanks
Regards

[Amarbir[CDR-Labs]]

Hello,
I am not talking of Headmap is RAM with creating a headmap when we are cloning the hard drive ,If this is not working like you said its another bloody blunder and bug ,I encourage user to add buys of MRT in this tread ,This will force these guys to do something

[ccc]

HI
If you still have those spyglass drives you can try HM in RAM and see if it works.

So, if it matters, we can add another bug on the list of bugs of ver 2.1.4.1

MRT team I hope you will read this and come with an answer!!!!

Rgds

[labtech]

They have been unresponsive during these couple of months due to coronavirus... That's sales. Support? I have no idea how that works.

[Amarbir[CDR-Labs]]

HI
If you still have those spyglass drives you can try HM in RAM and see if it works.

So, if it matters, we can add another bug on the list of bugs of ver 2.1.4.1

MRT team I hope you will read this and come with an answer!!!!

Rgds

Hello ,
For sure i can try ,But why is it useful for you ,Do you have a case you are trying to solve and cannot due to this

[Amarbir[CDR-Labs]]

They have been unresponsive during these couple of months due to coronavirus... That's sales. Support? I have no idea how that works.

Well,
They have the world's @$%^^*#%& support ,if we call get together we can force them to provide us proper stuff that we have paid for to them .How many units do you have ,I have 3, 1 ultra and 2 express units

[ccc]

HI
If you still have those spyglass drives you can try HM in RAM and see if it works.

So, if it matters, we can add another bug on the list of bugs of ver 2.1.4.1

MRT team I hope you will read this and come with an answer!!!!

Rgds

Hello ,
For sure i can try ,But why is it useful for you ,Do you have a case you are trying to solve and cannot due to this

Yes, I have a case where I need to cut H0 and try to start from copy 1. But without HM in Ram is imposible.

[ccc]

Hi Amarbir

Did you have a chance to try it? Or anyone else who have MRT last version can do a test on a spyglass/palmer drive? At least we can see if they (MRT) lied in their update log or not.

[Amarbir[CDR-Labs]]

Hi Amarbir

Did you have a chance to try it? Or anyone else who have MRT last version can do a test on a spyglass/palmer drive? At least we can see if they (MRT) lied in their update log or not.

Hello ,
We are in complete lockdown since 23rd till 14 april sorry brother

[extremestyle]

Hi Amarbir

Did you have a chance to try it? Or anyone else who have MRT last version can do a test on a spyglass/palmer drive? At least we can see if they (MRT) lied in their update log or not.

i have ultra offline
not working, try it today,
i have more questions to support but, support not working

[ccc]

You are saying that you tried to do HM in Ram and is not working? Or your ultra card is offline and not working?
You have to have the latest version of Mrt software to try HM in Ram.

Anyway I've also seen that their support in offline too...I hope they are OK and will come back soon.

Regards

[extremestyle]

You are saying that you tried to do HM in Ram and is not working?
Regards

yes

[ccc]

From their update log:

WD Utility, Version: 2.2.8.0
1. Adds new family Spyglass（800041）,Plamer（800066）, Charger
2. Optimizes the module 01 analysis to avoid disorder of ABA address (800041,800066.etc)
3. Support for headmap creation of HDDs with PCB ver.800041,8000066
4. Support for editing headmap in RAM for HDDs with PCB ver.800041, 800055, 800066

So it seems that statement at point 4 is not true....Typical for MRT.

[Amarbir[CDR-Labs]]

From their update log:

WD Utility, Version: 2.2.8.0
1. Adds new family Spyglass（800041）,Plamer（800066）, Charger
2. Optimizes the module 01 analysis to avoid disorder of ABA address (800041,800066.etc)
3. Support for headmap creation of HDDs with PCB ver.800041,8000066
4. Support for editing headmap in RAM for HDDs with PCB ver.800041, 800055, 800066

So it seems that statement at point 4 is not true....Typical for MRT.

Well,
They never test ,They are short of real pro users who can beta test ,Until some wise guy does not handle thier international sales ,its a bummer ,And mates kindly note they are in wuhan " The epicenter of Corona Virus " in the world ,beware of stocks that are coming to different places ,Precautions should be used