Vlad, the files are in the PZU directory, they were not created from SA - i went no where near SA functions at this stage of using the program - the files were never in the SA folder - they're in the same root PZU directory they've always been in, as i did as Spildit suggested and immeditely backed up my WDMarvel directory in an archive when problems started to occur.
As i've said earlier the drive is no longer responding to commands since writing the invalid rom "like it's not even connected" and that includes trying to read the rom now - the only way i can get it to respond is by enabling the hardware "modes" mentioned earlier, and even then - in these modes a rom dump results in a file which is 16mb in size.... which is useless, unless you have any idea why this is the case?
You can not know now, produced your files by "Read ROM" button, or by "Create ROM from SA copies" button
I want to see, that button "Read ROM" dumps empty FW
Sorry, my mistake i meant "read flash button" like i said above the drive will no longer respond to commands since writing the invalid rom.... Also i should note these invalid dumps are not completely empty, just the data relevent to the modules 0A, 0B etc... (attached)
Your suggestions grounds on the assumption, that ROM dump can be invalid
My point of view - ROM dump can not be invalid
Till we not have drive, where button "Read ROM" dumps empty FW, your suggestions is fighting with windmills
Well other than the rom dumps missing the previously mentioned information, there has been other ocassions of invalid rom dumps, for example the obvious one - a 0kb file - again obvious, and another which i beleive was 355kb - these just seemed to be completely random and minor hiccups and these files were uncommon but they were dumped and again are invalid.... surely you are familiar with this? as i've seen several posts of people mentioning this - aswell as posts with people mentioning rom mismatches for 192kb/256kb files
Only one questions
When program should to do this?
well i think you should make this feature optional (checkbox) but enabled by default - if/when enabled it should dump relevent files for all new drives (drives not defined in the set directory) when in PIO mode, if the drives model/name changes it should again dump all relevent info to the drives relevent folder. maybe provide a second optional checkbox for incremental auto backups or just have a set auto backup should the day change etc etc