Hi,
I am getting the following error on some drives (eg. Jamaica 4KV) and SS won't start:

BG_PST_DISABLED_VIA_DEBUGSTOP
error code: 3807

Can you help me? Which module to modify and how?
Thank you in advance.

_________________
Those who know don’t talk. Those who talk don’t know.

As I may have read somewhere that in order to do any self scan, modules should be fine and should read by id and aba both. Also drive parameters should load normally. If that is unchecked, then one could lead into problems.
Wrong do can cause HDD to go into ERR state on connection.

Rgds
--

Thanks, but modules are OK. Problem is that SS is locked. Some softwares can unlock it. Would like to know, how it is done manually.

_________________
Those who know don’t talk. Those who talk don’t know.

Are you paid a commission?

Let me clarify my question: How to modify the necessary module in a hex editor to ensure start of selfscan in drives where SS otherwise won't start?

_________________
Those who know don’t talk. Those who talk don’t know.

I don't have an answer, but module 02 has the enable/disable flags for various features. Perhaps you could compare it against modules 802E and 802F?

_________________
A backup a day keeps DR away.

helpless,
Try this. Only free tools need. Tested on some Zephyres.
Put the disc in the "not full initialized" mode by editing of addresses of regions of service area +1. Then download module 11 overlay, read 04 sectors of CONFIG_FILE in RAM by the demo WDMarvel in "Work with RAM". It is an essential module 02 to start of selfscan. Then return addresses of SA regions back. Save your 02 module, record obtained 02 in the service area and start selfscan. After selfscan end, return your saved 02 back.

So no changes in rom, ah?

What is the drive?
Spildit selftest and wdmarvel = problems.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

pikus_09
Drive is WD2500BPVT-22JJ5T0 Jamaica 4KV

E123
Thanks for your suggestion, however I cannot write modified 02.mod back to system area.

error writing module ID02 - success

Original 02.mod can be written without problem. Maybe there is a check before writing and header is different and causes trouble?
Here are the first four sectors of CONFIG_FILE read from RAM:

_________________
Those who know don’t talk. Those who talk don’t know.

Well, you are in the position to compare firmware before and after unlock, that would be real help.

Those mods are basically empty.

_________________
Those who know don’t talk. Those who talk don’t know.

It`s not a valid 02 module. Everything is done correctly, but part of the necessary data is abscent. Here is my method will not work. Can I look at your right 02 module?

Here is the original mod 02.

_________________
Those who know don’t talk. Those who talk don’t know.

Try it, but I think it also will not work.
I do not see anything like the required mark.

I don't know what mark you were looking for, but selfscan started!
I shall compare these modules and try to find out the right procedure myself. Should I fail, I shall turn to you for explanation.
Thanks a lot!

_________________
Those who know don’t talk. Those who talk don’t know.

- I have too little data to determine exactly which key is responsible for enabling the desired mode. There are only guesses. You have added a little bit of information to think about.

Fzabkar was right and wdmarvel use changes in rom only to get right flags in 02.

sorry i got it confused in 01 and 02....02 is id right?

rgds
--

_________________
THERE IS ALWAYS HOPE TILL YOU LOSE IT.

So can we imply that if ID is lost, the SS won't run?

rgds
--

_________________
THERE IS ALWAYS HOPE TILL YOU LOSE IT.