Image rescue

Information

  • Patent Grant
  • 9213606
  • Patent Number
    9,213,606
  • Date Filed
    Friday, April 20, 2012
    12 years ago
  • Date Issued
    Tuesday, December 15, 2015
    9 years ago
Abstract
An image rescue system includes an application program for communication with a mass storage device, the application program being in communication with an operating system layer for accessing the mass storage device to read and write information. The image rescue system further includes a device driver in communication with the application program, the operating system layer and the mass storage device, the device driver for allowing the application program to access the mass storage device to read and write information by bypassing the operating system layer, the device driver for communicating with the mass storage device to allow the application program to access information in the mass storage device considered damaged by the operating system layer, the damaged information being inaccessible to the operating system layer, wherein the image rescue system accesses the mass storage device to retrieve and recover information accessible and inaccessible to the operating system layer.
Description
TECHNICAL FIELD

The present invention relates generally to the field of retrieval and recovery of information and particularly to rapid and efficient retrieval and recovery of information stored in a mass storage device, which is accessible or inaccessible to an operating system.


BACKGROUND

In modern electronic systems, storage, retrieval, and recovery of digital information plays a significant role in the operation of devices included within such systems. A common example of an electronic system is a personal computer (PC), which requires access to digital data for processing thereof to perform and execute a wide variety of tasks. Digital data may be stored in a PC either internally as in a hard disk or externally in a mass storage data device such as a digital photo reader or a compact flash reader device.


In the conventional methods of accessing digital data, as implemented in electronic systems, an application program operating under a standard commercially available operating system accesses a mass storage data device for reading and/or writing of digital data. The operating system recognizes the mass storage data device and “mounts” it as an operating system data volume, i.e., a “disk drive”. The application program thereby accesses the mass storage data device at the logical level within the operating system using the operating system formatting information included within the mass storage data device.


However, the conventional methods of accessing digital data have a limitation that is encountered when the mass storage data device is for some reason corrupted. In the event of corruption of the mass storage data device, the electronic system cannot recover the digital data simply because the operating system is unable to communicate with the mass storage data device. Another limitation of the conventional methods of accessing digital data is that the application program commands the mass storage data device only with standard commands available to the operating system.


In light of the foregoing, it is desirable to develop a method and apparatus for accessing digital data even when the mass storage data device is corrupted and the operating system cannot communicate therewith. Further, the method and apparatus should not interfere with normal operations of the operating system, i.e. be transparent to the operating system. The desired method and apparatus should be able to access, retrieve, and recover information efficiently and cost-effectively.


SUMMARY

Briefly, an embodiment of the present invention includes an image rescue system having an application program for communication with a mass storage device, said application program being in communication with an operating system layer for accessing said mass storage device to read and write information. The image rescue system further includes a device driver in communication with said application program, said operating system layer and said mass storage device, said device driver for allowing said application program to access said mass storage device to read and write information by bypassing said operating system layer, said device driver for communicating with said mass storage device to allow said application program to rapidly access information in said mass storage device considered damaged by said operating system layer, said damaged information being inaccessible to said operating system layer, wherein said image rescue system accesses said mass storage device to rapidly and efficiently retrieve and recover information accessible and inaccessible to said operating system layer.


The foregoing and other objects, features and advantages of the present invention will be apparent from the following detailed description of the preferred embodiments which make reference to several figures of the drawing.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows an image rescue system 10, in accordance with an embodiment of the present invention.



FIG. 2 shows a representation of physical blocks and the file allocation grouping as used by the operating system, in accordance with an embodiment of the present invention.





DETAILED DESCRIPTION

The present invention employs a technique for directly accessing common mass storage data devices at the physical, rather than logical, device level; without assistance from operating system programming facilities. This allows for recovery, reconstruction and retrieval of valid user data files from a mass storage data device that the operating system would normally consider a “damaged” or corrupted mass storage data device.


The present invention allows the operating system to be extended to support the addition of an external mass storage data device to be added to the operating system as a standard system data volume or what is commonly known as a “disk drive”. An application program in concert with a device driver for the mass storage data device allow for rapid retrieval of what appears to be to the operating system “lost” or corrupted data from the mass storage data device.


In one embodiment of the present invention, the “mass storage data device” for which the application and driver is designed is Lexar Media, Inc. brand compact Flash cards connected to a personal computer (PC) or a Macintosh computer (Mac) via a universal serial bus (USB) 1.x connection via a Lexar Media brand Jumpshot cable. The application is not limited to this type of mass storage data device or this type of connection to the computer. The techniques described below will work for almost any mass storage data device, any storage technology, which is connected to the host computer in almost any way.


As will be explained in further detail with respect to FIG. 1, the application program employs a novel I/O access technique to allow the application program that is operating under a standard commercially available operating system to access a mass storage data device for reading or writing, regardless of whether or not the operating system recognizes the mass storage data device as a valid operating system formatted storage device such as a disk volume. That is, communication with the mass storage data device is possible through the Lexar application program whether or not the operating system recognizes the mass storage data device and “mounts” it as an operating system data volume, i.e. “disk drive”. The application can access the mass storage data device at the physical device level, as opposed to what is commonly known as the logical device level within the operating system. This is accomplished by a unique and novel method within the Lexar Media operating system extension device driver that supports the mass storage data device. The device driver is commonly supplied by the mass storage data device manufacturer or the author of the application program utility, i.e. Lexar Media. The technique employed is to include an additional proprietary layer of program interface within the standard device driver. This additional layer provides added functionality to allow an application program that is aware of this added interface to directly access the facilities provided within the device driver while circumventing the operating system. The operating system is completely unaware of this added proprietary access interface within the device driver. The device driver appears to the operating system to be a “standard” device driver in all respects; the operating system is completely unaware of the additional proprietary interface. The application program is able to locate the proprietary interface within the device driver using standard operating system functions and procedures. Once the proprietary interface is located and “attached” to the application program, the application program can call the functions and procedures located within the proprietary interface. The functions and procedures within the proprietary interface are “invisible” to the operating system and do not interfere with the operating system and its normal interaction with the Lexar device driver. The functions and procedures within the proprietary interface allow the Lexar application program to access the mass storage data device at the physical level; allowing the application program to command the mass storage data device with standard commands along with vendor unique commands; thus allowing the application program to access information and data areas that are not normally accessible to the operating system.


Referring now to FIG. 1, an image rescue system 10 is shown to include a personal computer (PC) 12 coupled to a device 14 in accordance with an embodiment of the present invention. The device 14 can be one of many types of devices, examples of which are compact flash reader devices, a digital photo reader, a Jumpshot product manufactured by Lexar Media, Inc. of Fremont, Calif., or any other type of mass storage product.


The PC 12 is shown to include an application program 16, which is in communication with the operating system layer 18 through an application program interface 22. The operating system layer 18 is shown to be in communication with a driver 20 through an operating system input/output (I/O) interface 24 and a driver I/O interface 32. The driver 20 is shown to include an access interface 26, which causes direct communication with the device 14 through a hardware interface layer 28 and the hardware bus 30. As shown in FIG. 1, the application program 16 is in direct communication with the access interface 26 through the direct access bus 34 thereby circumventing the operating system layer 18.


In various embodiments of the present invention, the hardware bus 30 conforms to different standards and is thus referred to as a different interface. Examples of the different types of hardware bus 30 are USB, PCMCIA, IDE, mass storage interface, fire wire and blue tooth.


In prior art methods, the application program must communicate through the operating system layer to the driver. The problem with such prior art methods is that in the event of some sort of corruption of the device 14, the system can not recover the device simply because the operating system is unable to communicate with the device. In the present invention however, the driver 20 identifies the device 14 and recovers the information previously stored in the device even though the device 14 includes corrupt information. It should be noted that different drivers 20 are employed for different types of devices that device 14 can be. Similarly, the access interface 26 includes different extensions based upon the kind of device employed as device 14. Bypassing the operating system layer 18 enables establishing communication with devices, as device 14, that the PC 12 is not able to communicate with if the operating system layer 18 is not bypassed.


Referring still to FIG. 1, the application program 16 rapidly searches and recovers certain types of user data files from a corrupted or non-corrupted mass storage data device, i.e. device 14. The device 14 is searched at the physical “raw” device level without the benefit of using the operating system layer 18 formatting information that may or may not be included within the device 14.


The technique employed searches for certain data file types that have distinguishable data “headers”. The “header” area includes data patterns that are unique to certain file types, for example, but not limited to, joint photographic experts group (JPEG) files or tagged image file format (TIFF) files. The application program also utilizes information gathered from the mass storage data device to formulate an algorithm to allow for an intelligent search of the mass storage data device instead of a “brute force” byte-by-byte search. The application program first directly queries the mass storage data device for its device characteristics using the access technique described hereinabove. This information is used to establish the absolute size in bytes of the device 14 along with obtaining its physical block size.


The physical block size, described in units of bytes, is the smallest unit of access that can be read or written to the mass storage data device. This unit is usually described as a binary multiple of a number of bytes, usually in the range of hundreds or thousands of bytes. The application will then attempt to read the operating system formatting information on the mass storage data device. This information is operating system dependent, the application knows what operating system it is running under and interprets the data accordingly. Since the formatting data may be damaged or corrupted, the application program attempts to determine if the formatting information is valid by examining certain operating system specific parameters contained within the formatting information for reasonable values.



FIG. 2 shows a representation of “search allocation units” 40. In FIG. 2, after investigating the formatting information, if the application determines that the information is valid, it will retrieve the operating system “file allocation unit” 41. This value is the smallest sized data block that the operating system will access file data on the mass storage data device. This value is usually described in units of physical block size 42; therefore the file allocation unit 41 is a multiple of physical block size; usually in the range of thousands of bytes. The application program will then use the largest determined block size 42 as its search allocation unit; this will be either the physical block size 42 or the operating system allocation unit size 41.


Knowing that the operating system will only write file data in units of file allocation unit sizes, the application program searches for pertinent file header information 43 at the boundaries of these units; at the very most, the file allocation unit 41; at the very least the physical block size 42 of the mass storage data device.


This, therefore, will substantially increase the speed of the search as opposed to a byte-by-byte search on the mass storage data device. It is only necessary to examine the beginning of the search allocation units for the file header information 43. If no match of header information is found, the search algorithm skips to the beginning of the next search allocation unit on the mass storage data device. This process is continued until all areas on the mass storage data device have been examined.


Although the present invention has been described in terms of specific embodiment, it is anticipated that alterations and modifications thereof will no doubt become apparent to those more skilled in the art. It is therefore intended that the following claims be interpreted as covering all such alterations and modification as fall within the true spirit and scope of the invention.

Claims
  • 1. An image rescue system comprising: a personal computer having an operating system layer and in communication with a device through a device driver, wherein the device driver has a driver input/output interface for communication with an application program through the operating system layer, and an access interface for providing the application program direct access to the device driver while bypassing the operating system layer;wherein the driver input/output interface is configured to facilitate communicating from the application program to the device using a first set of commands available to the operating system layer;wherein the access interface is configured to facilitate communicating from the application program to the device using a second set of commands not available to the operating system layer; andwherein the second set of commands facilitate access to information of the device considered damaged by the operating system layer, the information considered damaged by the operating system layer being inaccessible using the first set of commands.
  • 2. The image rescue system of claim 1, further including a hardware interface layer in communication with the access interface.
  • 3. The image rescue system of claim 2, further including a hardware bus coupled to cause communication between the device and the hardware interface layer.
  • 4. The image rescue system of claim 1, wherein the device is a compact flash reader device.
  • 5. The image rescue system of claim 1, wherein the device is a digital photo reader.
  • 6. The image rescue system of claim 1, wherein the access interface is configured to provide access to information in the device that is considered damaged by the operating system layer.
  • 7. The image rescue system of claim 1, wherein the access interface is configured to provide access to information in the device without using formatting information of the operating system layer.
  • 8. The image rescue system of claim 1, wherein communication between the application program and the device driver using the access interface comprises different commands than communication between the application program and the device driver using the driver input/output interface.
  • 9. An image rescue system comprising: an operating system layer in communication with an application program;a device driver having a first interface for communicating with the application program through the operating system layer, and having a second interface for communicating with the application program without assistance from programming facilities of the operating system layer; anda hardware bus configured for communicating between the device driver and a mass storage data device;wherein the first interface is configured to facilitate communicating from the application program to the mass storage data device using a first set of commands available to the operating system layer; andwherein the second interface is configured to facilitate communicating from the application program to the mass storage data device using a second set of commands in addition to the first set of commands, wherein the second set of commands is not available to the operating system.
  • 10. The image rescue system of claim 9, wherein the second interface of the driver is configured to facilitate access to areas of the mass storage device that are considered damaged by the operating system layer.
  • 11. The image rescue system of claim 9, further comprising the mass storage data device.
  • 12. The image rescue system of claim 11, wherein the mass storage data device is a compact flash card.
  • 13. The image rescue system of claim 9, wherein the application program is configured to access the mass storage data device at a logical device level when communicating with the mass storage data device through the first interface of the device driver, and to access the mass storage data device at a physical device level when communicating with the mass storage data device through the second interface of the device driver.
  • 14. The image rescue system of claim 9, wherein the application program is configured to access the mass storage data device through the second interface of the device driver even if the operating system layer does not recognize the mass storage data device as a valid operating system formatted storage device.
  • 15. The image rescue system of claim 9, wherein the hardware bus is selected from the group consisting of USB, PCMCIA, IDE, mass storage interface, fire wire and blue tooth buses.
  • 16. The image rescue system of claim 9, wherein the image rescue system is a personal computer.
  • 17. The image rescue system of claim 9, wherein the second interface is configured to provide access to information in the mass storage data device without using formatting information of the operating system layer.
  • 18. The image rescue system of claim 9, wherein functions and procedures within the second interface do not interfere with normal interaction between the operating system layer and the device driver.
RELATED APPLICATIONS

This application is a divisional of U.S. application Ser. No. 11/654,290, titled “IMAGE RESCUE,” filed Jan. 16, 2007 now U.S. Pat. No. 8,166,488, which is a continuation of U.S. application Ser. No. 10/371,930, filed Feb. 21, 2003, now U.S. Pat. No. 7,231,643, which claims the benefit of U.S. Provisional application No. 60/359,510, filed on Feb. 22, 2002, each of which is incorporated by reference in their entirety.

US Referenced Citations (263)
Number Name Date Kind
4099069 Cricchi et al. Jul 1978 A
4130900 Watanabe Dec 1978 A
4210959 Wozniak Jul 1980 A
4309627 Tabata Jan 1982 A
4355376 Gould Oct 1982 A
4398248 Hsia et al. Aug 1983 A
4405952 Slakmon Sep 1983 A
4414627 Nakamura Nov 1983 A
4450559 Bond et al. May 1984 A
4456971 Fukuda et al. Jun 1984 A
4468730 Dodd et al. Aug 1984 A
4473878 Zolnowsky et al. Sep 1984 A
4476526 Dodd Oct 1984 A
4498146 Martinez Feb 1985 A
4525839 Nozawa et al. Jun 1985 A
4532590 Wallach et al. Jul 1985 A
4609833 Guterman Sep 1986 A
4616311 Sato Oct 1986 A
4654847 Dutton Mar 1987 A
4710871 Belknap et al. Dec 1987 A
4746998 Robinson et al. May 1988 A
4748320 Yorimoto et al. May 1988 A
4757474 Fukushi et al. Jul 1988 A
4774700 Satoh et al. Sep 1988 A
4780855 Iida et al. Oct 1988 A
4788665 Fukuda et al. Nov 1988 A
4797543 Watanabe Jan 1989 A
4800520 Iijima Jan 1989 A
4829169 Watanabe May 1989 A
4843224 Ohta et al. Jun 1989 A
4896262 Wayama et al. Jan 1990 A
4914529 Bonke Apr 1990 A
4920518 Nakamura et al. Apr 1990 A
4924331 Robinson et al. May 1990 A
4943745 Watanabe et al. Jul 1990 A
4953122 Williams Aug 1990 A
4970642 Yamamura Nov 1990 A
4970727 Miyawaki et al. Nov 1990 A
5070474 Tuma et al. Dec 1991 A
5093785 Iijima Mar 1992 A
5168465 Harari Dec 1992 A
5198380 Harari Mar 1993 A
5200959 Gross et al. Apr 1993 A
5218695 Noveck et al. Jun 1993 A
5220518 Haq Jun 1993 A
5226168 Kobayashi et al. Jul 1993 A
5227714 Lou Jul 1993 A
5253351 Yamamoto et al. Oct 1993 A
5267218 Elbert Nov 1993 A
5268318 Harari Dec 1993 A
5268870 Harari Dec 1993 A
5270979 Harari et al. Dec 1993 A
5293560 Harari Mar 1994 A
5303198 Adachi et al. Apr 1994 A
5305276 Uenoyama Apr 1994 A
5305278 Inoue Apr 1994 A
5315541 Harari et al. May 1994 A
5315558 Hag May 1994 A
5329491 Brown et al. Jul 1994 A
5337275 Garner Aug 1994 A
5341330 Wells et al. Aug 1994 A
5341339 Wells Aug 1994 A
5341341 Fukuzo Aug 1994 A
5353256 Fandrich et al. Oct 1994 A
5357475 Hasbun et al. Oct 1994 A
5359569 Fujita et al. Oct 1994 A
5365127 Manley Nov 1994 A
5369615 Harari et al. Nov 1994 A
5371702 Nakai et al. Dec 1994 A
5381539 Yanai et al. Jan 1995 A
5382839 Shinohara Jan 1995 A
5384743 Rouy Jan 1995 A
5388083 Assar et al. Feb 1995 A
5396468 Harari et al. Mar 1995 A
5404485 Ban Apr 1995 A
5406527 Honma Apr 1995 A
5418752 Harari et al. May 1995 A
5422842 Cernea et al. Jun 1995 A
5422856 Sasaki et al. Jun 1995 A
5428621 Mehrotra et al. Jun 1995 A
5430682 Ishikawa et al. Jul 1995 A
5430859 Norman et al. Jul 1995 A
5431330 Wieres Jul 1995 A
5434825 Harari Jul 1995 A
5438573 Mangan et al. Aug 1995 A
5465235 Miyamoto Nov 1995 A
5465338 Clay Nov 1995 A
5471478 Mangan et al. Nov 1995 A
5473765 Gibbons et al. Dec 1995 A
5479638 Assar et al. Dec 1995 A
5485595 Assar et al. Jan 1996 A
5490117 Oda et al. Feb 1996 A
5495442 Cernea et al. Feb 1996 A
5504760 Harari et al. Apr 1996 A
5508971 Cernea et al. Apr 1996 A
5513138 Manabe et al. Apr 1996 A
5515333 Fujita et al. May 1996 A
5519847 Fandrich et al. May 1996 A
5523980 Sakui et al. Jun 1996 A
5524230 Sakaue et al. Jun 1996 A
5530673 Tobita et al. Jun 1996 A
5530828 Kaki et al. Jun 1996 A
5530938 Akasaka et al. Jun 1996 A
5532962 Auclair et al. Jul 1996 A
5532964 Cernea et al. Jul 1996 A
5534456 Yuan et al. Jul 1996 A
5535328 Harari et al. Jul 1996 A
5541551 Brehner et al. Jul 1996 A
5544118 Harari Aug 1996 A
5544356 Robinson et al. Aug 1996 A
5552698 Tai et al. Sep 1996 A
5554553 Harari Sep 1996 A
5563825 Cernea et al. Oct 1996 A
5566314 DeMarco et al. Oct 1996 A
5568439 Harari Oct 1996 A
5572466 Sukegawa Nov 1996 A
5579502 Konishi et al. Nov 1996 A
5581723 Hasbun et al. Dec 1996 A
5583812 Harari Dec 1996 A
5592415 Kato et al. Jan 1997 A
5592420 Cernea et al. Jan 1997 A
5596526 Assar et al. Jan 1997 A
5598370 Niijima et al. Jan 1997 A
5602987 Harari et al. Feb 1997 A
5603001 Sukegawa et al. Feb 1997 A
5606660 Estakhri et al. Feb 1997 A
5611067 Okamoto et al. Mar 1997 A
5640528 Harney et al. Jun 1997 A
5642312 Harari Jun 1997 A
5648929 Miyamoto Jul 1997 A
5663901 Wallace et al. Sep 1997 A
5671442 Feeney et al. Sep 1997 A
5693570 Cernea et al. Dec 1997 A
5712819 Harari Jan 1998 A
5719808 Harari et al. Feb 1998 A
5723990 Roohparvar Mar 1998 A
5734567 Griffiths et al. Mar 1998 A
5745418 Ma et al. Apr 1998 A
5754567 Norman May 1998 A
5757712 Nagel et al. May 1998 A
5758100 Odisho May 1998 A
5761117 Uchino et al. Jun 1998 A
5768190 Tanaka et al. Jun 1998 A
5768195 Nakamura et al. Jun 1998 A
5773901 Kantner Jun 1998 A
5778418 Auclair et al. Jul 1998 A
5781478 Takeuchi et al. Jul 1998 A
5787445 Daberko Jul 1998 A
5787484 Norman Jul 1998 A
RE35881 Barrett et al. Aug 1998 E
5799168 Ban Aug 1998 A
5802551 Komatsu et al. Sep 1998 A
5809515 Kaki et al. Sep 1998 A
5809558 Matthews et al. Sep 1998 A
5809560 Schneider Sep 1998 A
5818350 Estakhri et al. Oct 1998 A
5818781 Estakhri et al. Oct 1998 A
5822245 Gupta et al. Oct 1998 A
5822252 Lee et al. Oct 1998 A
5822781 Wells et al. Oct 1998 A
5831929 Manning Nov 1998 A
5835935 Estakhri et al. Nov 1998 A
5838614 Estakhri et al. Nov 1998 A
5845313 Estakhri et al. Dec 1998 A
5847552 Brown Dec 1998 A
5860083 Sukegawa Jan 1999 A
5860124 Matthews et al. Jan 1999 A
5862099 Gannage et al. Jan 1999 A
5890192 Lee et al. Mar 1999 A
5901086 Wang et al. May 1999 A
5901312 Radko May 1999 A
5907856 Estakhri et al. May 1999 A
5909586 Anderson Jun 1999 A
5920884 Jennings, III et al. Jul 1999 A
5924113 Estakhri et al. Jul 1999 A
5928370 Asnaashari Jul 1999 A
5930815 Estakhri et al. Jul 1999 A
5933368 Ma et al. Aug 1999 A
5933846 Endo Aug 1999 A
5936971 Harari et al. Aug 1999 A
5937425 Ban Aug 1999 A
5953737 Estakhri et al. Sep 1999 A
5956473 Ma et al. Sep 1999 A
5959926 Jones et al. Sep 1999 A
5966727 Nishino Oct 1999 A
5974439 Bollella Oct 1999 A
5986933 Takeuchi et al. Nov 1999 A
5987563 Itoh et al. Nov 1999 A
5987573 Hiraka Nov 1999 A
5991849 Yamada et al. Nov 1999 A
6011322 Stumfall et al. Jan 2000 A
6011323 Camp Jan 2000 A
6018265 Keshtbod Jan 2000 A
6021408 Ledain et al. Feb 2000 A
6026020 Matsubara et al. Feb 2000 A
6026027 Terrell, II et al. Feb 2000 A
6029179 Kishi Feb 2000 A
6034897 Estakhri et al. Mar 2000 A
6035357 Sakaki Mar 2000 A
6040997 Estakhri Mar 2000 A
6047307 Radko Apr 2000 A
6047352 Lakhani et al. Apr 2000 A
6055184 Acharya et al. Apr 2000 A
6055188 Takeuchi et al. Apr 2000 A
6069827 Sinclair May 2000 A
6072796 Christensen et al. Jun 2000 A
6076137 Asnaashari Jun 2000 A
6081447 Lofgren et al. Jun 2000 A
6081878 Estakhri et al. Jun 2000 A
6084483 Keshtbod Jul 2000 A
6097666 Sakui et al. Aug 2000 A
6115785 Estakhri et al. Sep 2000 A
6122195 Estakhri et al. Sep 2000 A
6125424 Komatsu et al. Sep 2000 A
6125435 Estakhri et al. Sep 2000 A
6128695 Estakhri et al. Oct 2000 A
6134145 Wong Oct 2000 A
6134151 Estakhri et al. Oct 2000 A
6138200 Ogilvie Oct 2000 A
6141249 Estakhri et al. Oct 2000 A
6145051 Estakhri et al. Nov 2000 A
6151247 Estakhri et al. Nov 2000 A
6172906 Estakhri et al. Jan 2001 B1
6173291 Jenevein Jan 2001 B1
6173362 Yoda Jan 2001 B1
6181118 Meehan et al. Jan 2001 B1
6182162 Estakhri et al. Jan 2001 B1
6202138 Estakhri et al. Mar 2001 B1
6223308 Estakhri et al. Apr 2001 B1
6226708 McGoldrick et al. May 2001 B1
6230234 Estakhri et al. May 2001 B1
6262918 Estakhri et al. Jul 2001 B1
6272610 Katayama et al. Aug 2001 B1
6275436 Tobita et al. Aug 2001 B1
6279069 Robinson et al. Aug 2001 B1
6279114 Toombs et al. Aug 2001 B1
6285607 Sinclair Sep 2001 B1
6327639 Asnaashari Dec 2001 B1
6345367 Sinclair Feb 2002 B1
6374337 Estakhri Apr 2002 B1
6393513 Estakhri et al. May 2002 B2
6397314 Estakhri et al. May 2002 B1
6411546 Estakhri et al. Jun 2002 B1
6467021 Sinclair Oct 2002 B1
6490649 Sinclair Dec 2002 B2
6567307 Estakhri May 2003 B1
6578127 Sinclair Jun 2003 B1
6587382 Estakhri et al. Jul 2003 B1
6711059 Sinclair et al. Mar 2004 B2
6725321 Sinclair et al. Apr 2004 B1
6728851 Estakhri et al. Apr 2004 B1
6751155 Gorobets Jun 2004 B2
6757800 Estakhri et al. Jun 2004 B1
6813678 Sinclair et al. Nov 2004 B1
6898662 Gorobets May 2005 B2
6912618 Estakhri et al. Jun 2005 B2
6950918 Estakhri Sep 2005 B1
6957295 Estakhri Oct 2005 B1
6973519 Estakhri et al. Dec 2005 B1
6978342 Estakhri et al. Dec 2005 B1
7000064 Payne et al. Feb 2006 B2
7499966 Elnozahy et al. Mar 2009 B2
20030033471 Lin et al. Feb 2003 A1
Foreign Referenced Citations (83)
Number Date Country
0 557 723 Jan 1987 AU
0 220 718 May 1987 EP
0 243 503 Nov 1987 EP
0 392 895 Oct 1990 EP
0 424 191 Apr 1991 EP
0 489 204 Jun 1992 EP
0 522 780 Jan 1993 EP
0 544 252 Jun 1993 EP
0 613 151 Aug 1994 EP
0 617 363 Sep 1994 EP
0 619 541 Oct 1994 EP
0 663 636 Jul 1995 EP
0 686 976 Dec 1995 EP
0 691 008 Jan 1996 EP
0 722 585 Jul 1996 EP
0 852 765 Jul 1998 EP
0 852 766 Jul 1998 EP
0 861 468 Sep 1998 EP
0 891 580 Jan 1999 EP
0 896 699 Feb 1999 EP
0 897 579 Feb 1999 EP
0 910 826 Apr 1999 EP
0 978 040 Feb 2000 EP
1 157 328 Nov 2001 EP
93 01908 Aug 1993 FR
2 251 323 Jul 1992 GB
2 291 990 Feb 1996 GB
2 291 991 Feb 1996 GB
2 297 637 Aug 1996 GB
2 304 428 Mar 1997 GB
2 348 991 Oct 2000 GB
2 351 822 Jan 2001 GB
2 384 072 Jul 2003 GB
2 384 337 Jul 2003 GB
2 384 338 Jul 2003 GB
2 384 883 Aug 2003 GB
2 411 499 Aug 2005 GB
117881 May 2003 IS
58-215794 Dec 1983 JP
58-215795 Dec 1983 JP
59-045695 Mar 1984 JP
59-162695 Sep 1984 JP
60-212900 Oct 1985 JP
61-096598 May 1986 JP
62-283496 Dec 1987 JP
62-283497 Dec 1987 JP
63-183700 Jul 1988 JP
1-138694 May 1989 JP
3-228377 Sep 1991 JP
4-057295 Feb 1992 JP
4-254994 Sep 1992 JP
4-268284 Sep 1992 JP
4-278297 Oct 1992 JP
4-332999 Nov 1992 JP
5-128877 May 1993 JP
5-282883 Oct 1993 JP
6-004399 Jan 1994 JP
6-036578 Feb 1994 JP
6-124175 May 1994 JP
6-124231 May 1994 JP
6-131889 May 1994 JP
6-132747 May 1994 JP
6-149395 May 1994 JP
6-266596 Sep 1994 JP
7-084871 Mar 1995 JP
7-093499 Apr 1995 JP
7-114499 May 1995 JP
7-141258 Jun 1995 JP
7-235193 Sep 1995 JP
7-311708 Nov 1995 JP
7-334996 Dec 1995 JP
8-018018 Jan 1996 JP
8-069696 Mar 1996 JP
9-147581 Jun 1997 JP
1388877 Apr 1988 SU
1408439 Jul 1988 SU
1515164 Oct 1989 SU
1541619 Feb 1990 SU
1573458 Jun 1990 SU
1686449 Oct 1991 SU
WO 8400628 Feb 1984 WO
WO 9420906 Sep 1994 WO
WO 9749056 Jun 1997 WO
Non-Patent Literature Citations (32)
Entry
Mendel Rosenblum and John K. Ousterhout, The Design and Implementation of a Log-Structured File System, article, 1991, 15 pgs., Berkeley, USA.
Brian Dipert and Markus Levy, Designing with Flash Memory, book, Apr. 1994, 445 pgs., Annabooks, San Diego, USA.
Science Forum, Inc., Flash Memory Symposium '95, symposium,1995, 13 pgs.; Hongo, Bunkyo-ku, Tokyo.
Ross S. Finlayson and David R. Cheriton, An Extended File Service Exploiting Write-Once Storage, article, 1987, 10 pgs. ACM.
Jason Gait, The Optical File Cabinet: A Random-Access File System for Write-Once Optical Disks, article, Jun. 1988, 12 pgs., Beaverton, Oregon.
Henry G. Baker, Memory Management, book, 1995, 19 pgs., Springer-Verlag Berlin Heidelberg, Germany.
Sape J. Mullender and Andrew S. Tanenbaum, A Distributed File Service Based on Optimistic Concurrency Control, article, 1985, 12 pgs., ACM.
Hiroshi Nakamura, Junichi Miyamoto, Kenichi Imamiya and Yoshihisa Iwata, A Novel Sense Amplifier for Flexible Voltage Operation NAND Flash Memories, symposium, 1995, VLSI Circuits Digest of Technical Papers, 2 pgs.
Hiroshi Nakamura, Junichi Miyamoto, Kenichi Imamiya, Yoshihisa Iwata, Yoshihisa Sugiura and Hideko Oodaira, A Novel Sensing Scheme with On-Chip Page Copy for Flexible Voltage NAND Flash Memories, article, Jun. 1996, 9 pgs., vol. E79-C. No. 6.
Takaaki Nozaki, Toshiaki Tanaka, Yoshiro Kijiya, Eita Kinoshita, Tatsuo Tsuchiya and Yutaka Hayashi, A 1-Mb EEPROM with MONOS Memory Cell for Semiconductor Disk Application, article, 1991, 5 pgs., Journal of Solid-State Circuits, vol. 26, No. 4.
Kai Hwang and Faye A. Briggs, Computer Architecture and Parallel Processing, book, 1984, McGraw-Hill, Inc. 2 pgs., US.
Walter Lahti and Dean McCarron, State of the Art: Magnetic VS. Optical Store Data in a Flash, article, 1990, 7 pgs., vol. 15, No. 12, McGraw-Hill. Inc., US.
Ron Wilson, Integrated Circuits; 1-Mbit flash memories seek their role in system design, article, Mar. 1, 1989, 2 pgs., No. 6, Tulsa, OK.
S. Mehroura, J.H. Yuan, R.A. Cemea, W.Y. Chien, D.C. Guteman, G. Samachisa, R.D. Noman, M. Mofidi, W. Lee, Y. Fong, A. Mihnea, E. Hann, R.W. Gregor, E.P. Eberhardt, J.R. Radosevich, K.R. Stiles, R.A. Kohler, C.W. Leung, and T.J. Mulrooney, Serial 9Mb F EEPROM for Solid State Disk Applications, symposium. 1992, 2 pgs., Mountain View, CA.
Steven H. Leibson, Nonvolatile, in-circuit-reprogrammable memories, article, Jan. 3, 1991, 12 pgs., EDN, Circle No. 12.
Ramon Caceres, Fred Douglis, Kai Li and Brian Marsh, Operating System Implications of Solid-State Mobile Computers, article, 7 pgs., Oct. 1993, Workshop on Workstation Operating Systems.
Michael Wu and Wily Zwaenepoel, A Non-Volatile, Main Memory Storage System, 12 pgs., 1994, ACM, San Jose, CA USA.
Dave Bursky, Innovative flash memories match DRAM densities: available with a choice of features, flash memories are finding homes in many systems (includes related articles on the origins of flash, and on the differences between NAND and NOR flash memories), article, May 16, 1994, 9 pgs., Electronic Design, v. 42, n. 10, The Gale Group.
Anthony Cataldo, New flash enhancements up ante. (Intel's 28F400BV-120 and 28F004BV-120, Atmel's AT29BV010 and AT29BV020, and Samsung Semiconductor's KM29V32000 *flash* memory* devices)(Product Announcement), article, Mar. 13, 1995, 4 pgs., Electronic News, v. 41, n. 2056, The Gale Group.
Sam Weber, *Flash* modules' portability, reusability, small size valued for a host of APPs-Consumer formats flocking to *flash*, article. Jul. 22, 1996, 9 pgs., Electronic Engineering Times, n. 911, CMP Media.
Toshiba, MOS Memory (Non-Volatile), 1995, Data Book.
Stan Baker, But Integration Calls for Hardware, Software Changes: Flash: designers face the dawn of a new memory age, article, Sep. 12, 2003, 5 pgs., Electronic Engineering Times, 1990, N. 619, 41, CMP Media.
Toshiba, Toshiba MOS Digital Integrated Circuit Silicon Gate CMOS, (TC58NS512DC) Mar. 21, 2001, 43 pgs., Data Book.
Toshiba Corporation, SMIL (Smartmedia Interface Library) Hardware Edition Version 1.00. Jul. 1, 2000, 36 pgs., Data Book.
Toshiba, Toshiba MOS Digital Integrated Circuit Silicon Gate. (TC58512FT), Mar. 5, 2001, 43 pgs., Data Book.
Toshiba, Toshiba MOS Digital Integrated Circuit Silicon Gate. (TC58DVM92A1FT00). Jan. 10, 2003, 44 pgs., Data Book.
35Nonvolatile Memory Technology Review, A Time of Change, Proceedings 1993 Conference, Jun. 22-24, 1993, Linthlcum Heights, MD USA.
Toshiba Corporation, SMIL (Smartmedia Interface Library) Software Edition Version 1.00, Jul. 1, 2000, 136 pgs., Data Book.
Toshiba. MOS Memory (Non-Volatile), 1996, 279 pgs., Data Book.
Dan Auclair, Optimal Solid State Disk Architecture for Portable Computers, symposium, Jul. 9, 1991, 7 pgs., SunDisk Corporation.
1992 Symposium of VLSI Circuits Digest of Technical Papers, “EEPROM for Solid State Disk Applications”, S. Mehoura et al., SunDisk Corporation, Sank Clara, CA. R.W. Grepor et al., AT&T Bell Laboratories, Allentown, PA. pp. 24 and 25.
“UNIX / Linux File System Recoverability” Ontrack Data Recovery, 2001, pp. 1-2, XP002469567, www.ontrackdatarecovery.com/unix-file-recovery/.
Related Publications (1)
Number Date Country
20120204192 A1 Aug 2012 US
Provisional Applications (1)
Number Date Country
60359510 Feb 2002 US
Divisions (1)
Number Date Country
Parent 11654290 Jan 2007 US
Child 13451594 US
Continuations (1)
Number Date Country
Parent 10371930 Feb 2003 US
Child 11654290 US