Free
Message: So for all who are waiting
1
Nov 16, 2007 08:07AM
1
Nov 16, 2007 08:33AM
1
Nov 16, 2007 08:38AM
3
Nov 16, 2007 10:10AM
3
Nov 16, 2007 11:41AM
1
Nov 16, 2007 11:42AM
2
Nov 16, 2007 02:38PM
4
Nov 16, 2007 04:01PM
2
Nov 16, 2007 04:41PM

Nov 16, 2007 05:07PM
1
Nov 16, 2007 05:31PM
2
dlj
Nov 16, 2007 08:55PM

Nov 18, 2007 07:22AM
1
Nov 18, 2007 08:23AM

Nov 18, 2007 08:45AM

Nov 18, 2007 08:47AM

Nov 18, 2007 08:54AM
1
Nov 18, 2007 08:56AM

Nov 18, 2007 09:08AM

Nov 18, 2007 09:32AM

Nov 18, 2007 11:10AM

Nov 18, 2007 11:19AM

Nov 18, 2007 11:30AM

Nov 18, 2007 11:46AM

Nov 18, 2007 03:06PM
1
Nov 18, 2007 03:17PM
1
Nov 18, 2007 03:22PM
1
Nov 19, 2007 02:28AM
2
Nov 19, 2007 03:33AM
2
Nov 19, 2007 04:15AM
1
Nov 19, 2007 05:12AM

Nov 19, 2007 05:28AM
1
Nov 19, 2007 05:43AM

Nov 19, 2007 05:48AM

"My concern is the manner they use to manage the FAT .....do they do it in the same manner e.Digital does. How do they manage the virtual tables? Within the flash,  or , status quo through RAM processes?"

That statement may be out of scale with regard to punctuation and grammar....however, I don't give a rats ass.

I'm dead serious when I comment of the manner that e.Digital manages FAT and hands it off to a higher level OS.

They announced their ability over 3 years ago...the ability of 12..16 and 32.

There are no explanations of how they do it, however, If they are doing it under their proprietary ability...I can most definitely see how they would do it...and it would be without  normally associated allocation tables. Their ability is physical location within the flash...and that is the level they would manage FAT....under a physical condition...not virtually with significant RAM resource as others would have to do.

DM is looking at something serious...and I have no doubt they understand it.

doni 

 

Share
New Message
Please login to post a reply