thing is...

running a test depends on the infringed technology if its used as an OS environment like 445 or an application environment as in voice recorder...

Used as a voice recorder application, as e.Digital implements, could theoretically partition space on the SSD and keep issues separate...of a presiding OS environment. Using e.Digitals methods would require the application to master over a territory of free space within the ssd in order to create data files in the way it does....and know where the dead memory is within that space....and the presiding OS would have to know not allocate its methods in this space...

That would be the long way around..to avoid infringement...however, it's possible.

What e.Digital is seeking is how bad memory is managed across the whole SSD....and how the presiding OS manages that detail.

Thing is, 445 has a portability to utilize the attributes of other operating systems...in other words an underlying structure that replaces the typical OS structure.

If they are managing dead memory in the manner e.Digital does, they are implementing a data structure that complements the dead memory management across the whole ssd.

doni