US20070214187A1 - Self-Contained Application Disk for Automatically Launching Application Software or Starting Devices and Peripherals - Google Patents
Self-Contained Application Disk for Automatically Launching Application Software or Starting Devices and Peripherals Download PDFInfo
- Publication number
- US20070214187A1 US20070214187A1 US11/748,340 US74834007A US2007214187A1 US 20070214187 A1 US20070214187 A1 US 20070214187A1 US 74834007 A US74834007 A US 74834007A US 2007214187 A1 US2007214187 A1 US 2007214187A1
- Authority
- US
- United States
- Prior art keywords
- application
- removable media
- disk
- media
- participating
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
Definitions
- the present invention relates to application software contained on removable storage media.
- the present invention relates to a system wherein instructions to configure operating system environmental variables and to load predetermined application software are stored on removable media such that the application and its associated data files are automatically launched for use upon insertion of the removable disk into a removable media drive.
- this figure fails to account for the shared files that Microsoft® Excel97 requires for proper execution. Because of the increase in size and complexity of modern software, applications are no longer developed to be executed from a single piece of removable media, and at a minimum, must be partially installed to the computer's hard disk drive for use.
- a first problem is that managing data files has become increasingly difficult. With personal computer hard drives exceeding 20 GB in storage capacity, users can store almost everything they generate and download. Naming, organizing and differentiating between data files is extremely difficult, particularly in view of the common practice of users to name and save files using cryptic or uninformative names (e.g., today.doc, temp.xls, or junk.txt).
- a typical user may have a computer at home, a computer at work, and a portable computer (e.g., notebook) that he or she uses every day.
- a portable computer e.g., notebook
- the user must manually copy the data file(s) to a removable disk and either access the data file(s) from the removable disk or copy them to the other computer.
- each computer that the user wants to use must have the particular piece of software that generated the data file(s) installed thereon in order to properly access the data.
- data is lost as newer files are overwritten by older versions.
- Peripheral devices and their associated software have become numerous and are in many cases difficult to use.
- peripheral devices create data files that must be saved for use by other application software.
- an application that automatically launches another application upon insertion of the removable media into a computer and include the Windows® “Autorun” feature which automatically runs an application contained on, e.g., a CD-ROM.
- the operating system checks for a file named “autorun.inf” in the root directory of the CD.
- the autorun.inf file is a pointer to an executable file named “autorun.exe” which launches the software on the CD.
- the Autorun feature is used to launch software setup/install routines to install software contained on the CD to the hard drive.
- the autorun feature is limited in that it does not configure a computer to run application software based on instructions contained on the removable media, nor does the Autorun feature have the ability to manage events such as ejection of the removable media, closing of the application running from the removable media, and storage of data files to the removable media.
- computers remain difficult for many people to use. For example, when a user turns on the computer, he or she is most often presented with the graphical user interface. At this point, it is up to the user to navigate to and launch the application software that he or she desires to use. Although this task seems relatively easy, it is not for many users as there is no standardization on where a particular application software is located on the computer. Clearly, the personal computer has failed to achieve the simplicity of other home appliances, which has prevented large numbers of people from accepting and using computers.
- an application or service that resides on a computer that automatically, and without requiring any user intervention, recognizes the insertion of a piece of removable media.
- the removable media contains a task disk control file that contains all of the configuration information necessary to run participating applications from the removable media.
- the task disk control file contains three sections of configuration information as follows: pre-run, application run, and clean-up.
- the pre-run section configures registry information such that the operating system is aware of the path, environmental variables and command line to launch the participating application.
- the pre-run section may specify files (e.g., executable files, DLLs, device drivers, etc.) that are to be copied to the hard drive to properly execute the participating application.
- the application run section instructs the operating system to load the participating application, which launches the participating application for use by a user.
- the clean-up section removes all registry information added by the pre-run section.
- the clean-up section may remove from the hard drive the files copied thereto to execute the participating application.
- the participating application After reading the task disk control file and configuring the computing device, the participating application is then launched for use by a user. Once the user is finished using the participating application, the removable disk is automatically ejected. In addition to monitoring for insertion of the removable media, events such as a completion of the self-contained application and a request to eject the media are monitored. When a completion event is encountered, all data files are saved, temporary files are deleted and configuration information is removed prior to the removable disk ejection. When an ejection event is encountered, the computing device is instructed to wait until the completion events are executed prior to actual ejection of the removable media.
- the system of the present invention serves to greatly simplify the use and operation of computer application software, devices and peripherals because users are not required to have any knowledge of how to launch the application or start the devices and peripherals they wish to use other than such applications, devices and peripherals will be launched/started automatically upon insertion of the removable media. Other features of the invention are described below.
- FIG. 1 is a block diagram of the components of a personal computer in which the present invention is embodied
- FIG. 2 is a block diagram of the components of a preferred removable media drive shown in FIG. 1 ;
- FIG. 3 is a flow chart illustrating an overview of the processes performed by the present invention.
- FIG. 4 is an exemplary task disk control file in accordance with the present invention.
- the present invention provides a novel application on a removable disk used within a computing environment to maintain application software, data and devices.
- a user inserts the removable disk containing the application software to be executed into the personal computer, and the software application or device is automatically launched/started and readied for use.
- the present invention advantageously allows a user to maintain everything he or she needs using a removable disk.
- the preferred platform is a personal computer (PC) 20 , which may comprise Windows® 95/98 or Windows NT®.
- PC personal computer
- Workstation-based personal computer having, e.g., an Intel Pentium® processor or higher, a long-term non-removable storage device (e.g., a IDE or SCSI hard disk), a removable media drive (e.g., CD-R, CD-RW, DVD, or other removable floppy or hard disk drive), random access memory (RAM), communication peripherals (e.g., network interface card, modem, and/or terminal adapter), and suitable application programs (e.g., Dial-up networking software and a Web Browser).
- PC personal computer
- the PC 20 may be divided between internal and external components.
- the internal components include a Basic Input/Output System (BIOS) 70 and a processor (CPU) 66 that control the overall functioning of the PC 20 .
- BIOS Basic Input/Output System
- CPU processor
- Memory 64 a hard disk drive 76 , a floppy disk drive 74 , a tape drive 78 , a CD-ROM drive 80 , a MODEM/Terminal Adaptor/Network Interface Card 82 , and a removable media drive 52 a are also connected to the CPU 66 .
- the removable media drive 52 a or 52 b operates to read and/or write to a storage media contained within a removable storage cartridge 28 .
- the exemplary PC 20 of FIG. 1 is configured with two removable media drives 52 a and 52 b to emphasize that a removable media drive can be implemented in either internal or external form.
- the removable media 28 may comprise a ZIP® disk manufactured by Iomega Corporation, Roy, Utah.
- Each Iomega ZIP® disk contains a unique serial number that is written to a predetermined track during the formatting process which may be used as the unique identifier.
- the serial number is preferably created by but not limited to a pseudo random number generator.
- the media 28 has been described in terms of a ZIP® disk, it is not limited to the ZIP® disk, as the use of other removable media types having a unique serial number is within the scope and spirit of the present invention such as CD-R, DVD-RAM, and other removable floppy and hard disks.
- the MODEM/Terminal Adaptor/Network Interface Card 82 may comprise individual cards performing communications-related functions, as known in the art.
- the MODEM/Terminal Adaptor/Network Interface Cards 82 are included within PC 20 to provide communications to external networks to which the PC 20 is connected.
- the MODEM/Terminal Adaptor/Network Interface Card 82 may be used to access LAN 14 , ISP 18 and network infrastructure 12 .
- a serial/parallel/USB port controller (which may comprise separate controllers) 58 , a monitor controller (video card) 60 , and a keyboard and mouse controller 62 each provide an interface between the CPU 66 and an external removable media drive 52 b (or printer), monitor 54 , and keyboard and mouse device 56 , respectively.
- a hard disk and floppy disk controller 72 serves as an interface between the CPU 66 and the hard disk 76 and the CD-ROM drive 80 , and the floppy disk 74 and tape drive 78 , respectively. It will be appreciated by those skilled in the art that the disk controller 72 may comprise separate floppy and hard disk controllers (e.g., IDE or SCSI controller).
- a removable media controller 68 serves as an interface between the removable media drive 52 a and the CPU 66 .
- the removable disk controller 68 may comprise a Small Computer System Interface (SCSI) or Integrated Drive Electronics (IDE) interface controller.
- a hard disk and floppy disk controller 72 serves as an interface between the CPU 66 and the hard disk 76 and the CD-ROM drive 80 , and the floppy disk 74 and tape drive 78 , respectively.
- the removable media drive 52 a may utilize the disk controller 72 as an interface to the CPU 66 .
- the media drive 52 preferably comprises, a ZIP® drive, manufactured by Iomega Corporation, Roy, Utah; however, the present invention is not limited to such removable media drives and other media drives may be used as media drive 52 .
- the media drive 52 includes components that provide for communication between the read/write channel for the media (lower right side of diagram) and the PC 20 (upper left side of diagram).
- the media drive 52 includes an AIC chip 101 which performs the SCSI 102 , the direct memory access (DMA) 103 , and disk formatter 104 functions.
- DMA direct memory access
- the interface also includes a PHAEDRUS 105 which includes an 8032 microcontroller 106 , a 1 kbyte RAM 107 and an application specific integrated circuit (ASIC) 108 .
- the ASIC 108 may perform various functions, such as servo sequencing, data splitting, EOC, ENDEC, A-to-D, and D-to-A conversion.
- the communication between the media drive 52 and the PC 20 is accomplished through transfers of data between the input/output channel of the media drive 52 and the media controller 68 (e.g., SCSI controller) of the PC 20 .
- the media controller 68 e.g., SCSI controller
- the present invention runs as a background task or service that recognizes and reads a task disk control file stored on the removable media upon detection of insertion of the removable media into the computer.
- the task disk control file includes instructions to configure the computer operating environment and launch application software resident on the removable media or the computer's hard disk (or on both).
- the task disk control file may be used to start application software that controls computer devices and/or the devices themselves.
- the system of the present invention serves to greatly simplify the use and operation of computer application software, devices and peripherals because users are not required to have any knowledge of how to launch the application or start the device or peripheral they wish to use. In other words, all the user needs to know is that the application, device or peripheral he or she wants to use will be automatically launched/started upon insertion of the removable media.
- An application or system service running on the PC 20 monitors device commands to and from the removable media drive 52 (step 200 ). It is preferable that this be a background application or service that is loaded when the computer is booted-up.
- An example of such an application to monitor device commands to the removable media drive 52 is IOwatch, available from IOmega Corporation, Roy, Utah.
- the application or service resides on the computer 20 and automatically, and without requiring any user intervention, recognizes the insertion of a piece of removable media.
- a monitored device command is “a media change condition.”
- Media change conditions indicate that removable media 28 has been inserted in to the removable media drive 52 or that some action has occurred with regard to the removable media 28 currently in the drive 52 . If no media change condition is present at step 202 , then processing returns to step 200 to monitor for subsequent device commands.
- a media change condition is present at step 202 , then the present invention begins its processing by identifying an event type associated with the media change condition.
- Events that may be identified and routed at step 204 include, but are not limited to: device events and events resulting from calls from a “participating application” 201 .
- a “participating application” 201 is defined herein as a software application that has knowledge of, and cooperates with, the present invention by making and accepting event calls to and from the present invention.
- the participating application may be located on, e.g., the hard disk 76 , the removable media 28 , a CD-ROM, or network location.
- participating applications may control peripherals and devices attached to or within the computer (e.g., tape drives, scanners, etc.).
- Media change conditions are provide to the present invention by known mechanisms such as inter-application messages, program calls, and event notifications.
- a first identified event may be a media insertion event (step 206 ), which is a condition that exists when the removable media 28 is inserted into the removable media drive 52 .
- the media may be detected as inserted by the drive in accordance with the method of U.S. Pat. No. 5,854,719, to Ginosar et al., which is incorporated herein by reference in its entirety.
- the system then checks for the presence of a task disk control file (TDCF) 220 on the media 28 .
- TDCF task disk control file
- An exemplary task disk control file 220 is illustrated in FIG. 4 , and contains configuration and execution information and regarding the participating application.
- the TDCF 220 may contain information such as the executable filename, path information, and Windows® registry data, including the identification of necessary device drivers, Dynamic Link Libraries, VxDs, etc. The contents of the TDCF will be discussed in greater detail below.
- TDCF task disk control file
- the system returns to step 200 to monitor for subsequent device commands, as the disk cannot be used to configure and launch an application or device.
- a message may be generated and displayed to the user indicating the TDCF 220 is not valid.
- a unique identifier e.g., serial number
- the TDCF 220 may be encrypted using the media serial number as an encryption key to provide an added measure of security and to prevent the application software from being copied and run from another piece of media.
- any encryption algorithm may be used.
- the media serial number may be obtained by an application running on the PC 20 that reads the unique identifier and authentication code. This is performed by querying the media using an application programming interface (API) such as the Iomega Ready API, or other suitable method.
- API application programming interface
- the Iomega Ready API when invoked causes the media drive to read the unique serial number from the predetermined track by using the SCSI 0.times.06 Non-Sense Command.
- the media serial number may be determined by reading offset bytes 20 - 59 of the returned data structure.
- the unique serial number should contain a sufficient number of bits (length) to ensure that no two pieces of media have the same identifier.
- each Iomega ZIP® disk contains a unique 39 byte (312 bits) serial number, and other bit lengths may be utilized.
- the task disk control file (TDCF) 220 is processed at step 214 , where it is decrypted using the media serial number as a decryption key. It is noted that encryption of the TDCF 220 is not necessary for the operation of the present invention, and is provided as a security feature to prevent, e.g., illegal copying of copyrighted program files on the removable media 28 . Accordingly, step 210 may be provided with a mechanism to determine if the TDCF is encrypted, and if not, jump to step 216 .
- the unencrypted TDCF 220 is read and the system environment is configured in accordance with information contained in the TDCF 220 prior to launching the participating application.
- the TDCF 220 contains three sections of configuration information labeled as follows: pre-run, application run, and clean-up.
- the pre-run section configures registry information such that the operating system is aware of the path, environmental variables and commands to launch the participating application.
- the pre-run section may specify files (e.g., executable files, DLLs, device drivers, etc.) that are to be copied to the hard drive to properly execute the participating application.
- the application run section instructs the operating system to load the participating application, which launches the participating application for use by a user (see, step 218 , below).
- the clean-up section removes all registry information added by the pre-run section (see, step 224 , below).
- the clean-up section may remove from the hard drive the files (e.g., executable files, DLLs, device drivers, etc.) copied thereto to execute the participating application.
- the TDCF 220 may configure the system environment to run applications in several modes.
- a first mode of operation the participating application is stored on, and run from, the removable media 28 upon insertion.
- this first mode of operation everything necessary to run the participating application is maintained and executed from the removable media 28 .
- no files are copied to the hard drive, nor are any files required to be on the hard drive to run the participating application.
- a second mode of operation the participating application cannot be run from the removable media 28 alone.
- certain files are copied to the hard disk as specified in the pre-run section of the TDCF 220 .
- These files may include, but are not limited to the above-mentioned executable files, DLLs, device drivers, etc. It may be necessary to copy files to the hard disk to because of limitations in speed or size of the removable media 28 .
- the second mode when the participating application is closed or the removable disk 28 ejected, the previously copied files are removed from the hard drive in accordance with the clean-up section such that the hard disk is returned to essentially the same state it was in prior to the insertion of the removable media 28 .
- a third mode the participating application cannot be run from the removable media 28 alone, as in the second mode. However, in this mode when the participating application is closed or the disk ejected, the files are not removed from the hard drive. In the third mode, the previously copied files remain on the hard disk in accordance with the clean-up section, such that any subsequent insertion of the removable media 28 would not require copying of the specified files to the hard drive.
- This third mode of operation speeds up the launching of the participating application for second and subsequent insertions of the removable disk 28 into the removable media drive 52 .
- the participating application is installed to, and stored on, the computer's hard drive.
- the participating application's installation program preferably includes an option to make it “participating” in accordance with the present invention.
- a plug-in may be used to hook into the participating application to make it “participating” in accordance with the present invention.
- the pre-run section of the TDCF contains all of the instructions necessary to automatically launch the participating application from the hard drive and, optionally, load data files as the participating application is launched.
- the data files are preferably on the removable media 28 , but also may reside on the hard disk.
- the TDCF 220 contains a list of instructions to open and close the participating application, such that the removable media acts as a “key” to automatically open the participating application upon insertion into the removable media drive 52 .
- the TDCF 220 of FIG. 4 is provided herein for exemplary purposes only. Further, the TDCF 220 may contain additional or fewer instructions to configure the computer 20 , copy files to the computer 20 , etc. than illustrated. Further, additional or few modes of operation are possible. In accordance with the present invention, the TDCF 220 contains the instructions necessary to properly configure and launch the participating application upon insertion of the removable media 28 , and gracefully remove configuration settings and save data files without the need for user intervention.
- step 218 once the PC 20 is configured in accordance with the TDCF 220 , the participating application is launched for use and the system returns to step 200 to monitor for new events.
- a Save/Close Complete event occurs when the user has finished using the participating application and either selects exit or clicks the “.pi.” box (i.e., close window box) in the application window.
- the participating application saves all data files, deletes all temporary files and indicates to the system that it is ready to terminate.
- the data files may be saved in accordance with a predetermined file path set by the TDCF 220 .
- all configuration information is removed from the PC 20 in accordance with the clean-up section of the TDCF 220 .
- the clean-up section will perform certain clean-up functions based on a mode of operation, as noted above.
- the participating application terminates and the removable media 28 is ejected by the present invention from the media drive 52 . Processing then continues at step 200 .
- a Media Eject Request Event is a condition that exists when the user has initiated an eject function by pressing an eject button provided on the drive 52 or through a provide software eject feature.
- the participating application is notified via inter-application mechanisms, such as a message, that a “request for media eject” was detected.
- the system executes steps 222 - 226 as discussed above to complete. Once the present invention is notified of a completion at step 234 , processing returns to step 200 to monitor for new events.
- the present invention provides a new and improved system for managing data files and applications that requires very little, if any, user attention.
- the user need only know that insertion of a particular piece of removable media launches a particular application or starts a particular device or peripheral that he or she wants to use.
- the user's data files are saved to the same piece of removable media or other specified location for easy retrieval, therefore, the user's data is easily obtainable for use when the application is launched.
- the removable media is ejected from the computer to be placed away for safekeeping.
Abstract
A system and method for automatically executing a participating application upon insertion of a removable media into a computing device. When the computing device detects that the removable media containing has been inserted, a task disk control file is read from the removable media. The task disk control file contains all of the configuration information necessary to run the participating application from the removable media The participating application is then launched for use by a user. After the user is finished using the participating application, the removable disk is automatically ejected. In addition to monitoring for insertion of the removable media, events such as a completion of the self-contained application and a request to eject the media are monitored. When a completion event is encountered, all data files are saved, temporary files deleted and configuration information removed prior to the removable disk ejection. When an ejection event is encountered, the computing device is instructed to wait until the completion events are executed prior to actual ejection of the removable media.
Description
- This application is a divisional of U.S. patent application Ser. No. 10/367,650, filed Feb. 14, 2003, which is a continuation of U.S. patent application Ser. No. 09/360,337 filed Jul. 26, 1999, which issued as U.S. Pat. No. 6,529,992 on Mar. 4, 2003.
- The present invention relates to application software contained on removable storage media. In particular, the present invention relates to a system wherein instructions to configure operating system environmental variables and to load predetermined application software are stored on removable media such that the application and its associated data files are automatically launched for use upon insertion of the removable disk into a removable media drive.
- In the beginning of the personal computing era, software applications were simple and small mainly because of limitations in storage and computing power. For example, one of the first widely used software applications, VisiCalc, was only 25 kB in size and was typically run from a floppy disk. Because of these limitations, data files created by VisiCalc were often stored on the same floppy disk as the program file. However, as processing power and capabilities of personal computers increased, additional features were added to software applications to take advantage the increased processing power. These features have lead to a tremendous increase in the size of software applications. For example, Microsoft® Excel97 now has an executable file that is approximately 5.4 MB, which is an increase of 21,600% over the early VisiCalc spreadsheet software. In addition, this figure fails to account for the shared files that Microsoft® Excel97 requires for proper execution. Because of the increase in size and complexity of modern software, applications are no longer developed to be executed from a single piece of removable media, and at a minimum, must be partially installed to the computer's hard disk drive for use.
- While modern software applications have greater functionality and are easier to use than their early counterparts, they have created usability problems for end users. A first problem is that managing data files has become increasingly difficult. With personal computer hard drives exceeding 20 GB in storage capacity, users can store almost everything they generate and download. Naming, organizing and differentiating between data files is extremely difficult, particularly in view of the common practice of users to name and save files using cryptic or uninformative names (e.g., today.doc, temp.xls, or junk.txt).
- Another problem has been created by the shear number of personal computers an peripherals devices. A typical user may have a computer at home, a computer at work, and a portable computer (e.g., notebook) that he or she uses every day. Thus, if a user wants to use a particular data file(s) on more than one computer, the user must manually copy the data file(s) to a removable disk and either access the data file(s) from the removable disk or copy them to the other computer. In addition, each computer that the user wants to use must have the particular piece of software that generated the data file(s) installed thereon in order to properly access the data. Inevitably, as users move data from one computer to another, data is lost as newer files are overwritten by older versions. Further complicating file management tasks is when the user creates several pieces of removable media containing several versions of the data files and then must figure out which version is the correct version by looking at the time stamps or inspecting the contents of each of the data files. Peripheral devices and their associated software have become numerous and are in many cases difficult to use. In addition, many peripheral devices create data files that must be saved for use by other application software.
- There have been some advances in file management. These include file managers and applications that synchronize files between computers to reduce the effort necessary to maintain current versions of data files on multiple computers. However, these programs are severely limited because they typically cannot synchronize files between more than two computers. In addition, the files to be synchronized are often manually selected by the users. Thus, if a particular piece of software creates and access multiple data files, the user must manually select all of the data files for synchronization between two computers, otherwise errors may occur. Often users forget to select a particular data file for synchronization and later find that they are unable to utilize any of the data on another computer. This problem not only affects synchronization programs, but also occurs when users manually copy data files to removable media, in the scenario noted above.
- There have been other advances in making computers easier use, such as graphical user interfaces and applications that automatically launch programs contained on removable media. An example of an application that automatically launches another application upon insertion of the removable media into a computer and include the Windows® “Autorun” feature which automatically runs an application contained on, e.g., a CD-ROM. When the CD-ROM is inserted into the drive, the operating system checks for a file named “autorun.inf” in the root directory of the CD. Within the autorun.inf file is a pointer to an executable file named “autorun.exe” which launches the software on the CD. Typically, the Autorun feature is used to launch software setup/install routines to install software contained on the CD to the hard drive. However, the Autorun feature is limited in that it does not configure a computer to run application software based on instructions contained on the removable media, nor does the Autorun feature have the ability to manage events such as ejection of the removable media, closing of the application running from the removable media, and storage of data files to the removable media.
- However even with the above advancements, computers remain difficult for many people to use. For example, when a user turns on the computer, he or she is most often presented with the graphical user interface. At this point, it is up to the user to navigate to and launch the application software that he or she desires to use. Although this task seems relatively easy, it is not for many users as there is no standardization on where a particular application software is located on the computer. Clearly, the personal computer has failed to achieve the simplicity of other home appliances, which has prevented large numbers of people from accepting and using computers.
- In view of the above, there is a need for a method and apparatus for facilitating the maintenance and use of a user's data, application software and computer devices. Further, there is a need for a method and apparatus that performs these functions automatically with little or no input from the user in order to prevent accidental loss of data and to provide ease of application use. Such a need would be solved by an self-contained application stored on removable media that is adapted to automatically start devices or launch application software from the removable media or the computer's hard drive upon insertion into the computer, while also saving the data files to the removable media or other predetermined location. The present invention provides such a solution.
- In view of the above, the present invention, through one or more of its various aspects and/or embodiments is thus presented to accomplish many advantages, such as those noted below.
- In accordance with the present invention, there is provided an application or service that resides on a computer that automatically, and without requiring any user intervention, recognizes the insertion of a piece of removable media. The removable media contains a task disk control file that contains all of the configuration information necessary to run participating applications from the removable media. In particular, the task disk control file contains three sections of configuration information as follows: pre-run, application run, and clean-up. The pre-run section configures registry information such that the operating system is aware of the path, environmental variables and command line to launch the participating application. Optionally, the pre-run section may specify files (e.g., executable files, DLLs, device drivers, etc.) that are to be copied to the hard drive to properly execute the participating application. The application run section instructs the operating system to load the participating application, which launches the participating application for use by a user. The clean-up section removes all registry information added by the pre-run section. Optionally, the clean-up section may remove from the hard drive the files copied thereto to execute the participating application.
- After reading the task disk control file and configuring the computing device, the participating application is then launched for use by a user. Once the user is finished using the participating application, the removable disk is automatically ejected. In addition to monitoring for insertion of the removable media, events such as a completion of the self-contained application and a request to eject the media are monitored. When a completion event is encountered, all data files are saved, temporary files are deleted and configuration information is removed prior to the removable disk ejection. When an ejection event is encountered, the computing device is instructed to wait until the completion events are executed prior to actual ejection of the removable media.
- The system of the present invention serves to greatly simplify the use and operation of computer application software, devices and peripherals because users are not required to have any knowledge of how to launch the application or start the devices and peripherals they wish to use other than such applications, devices and peripherals will be launched/started automatically upon insertion of the removable media. Other features of the invention are described below.
- The foregoing summary, as well as the following detailed description of the preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings an embodiment that is presently preferred, in which like reference numerals represent similar parts throughout the several views of the drawings, it being understood, however, that the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:
-
FIG. 1 is a block diagram of the components of a personal computer in which the present invention is embodied; -
FIG. 2 is a block diagram of the components of a preferred removable media drive shown inFIG. 1 ; -
FIG. 3 is a flow chart illustrating an overview of the processes performed by the present invention; and -
FIG. 4 is an exemplary task disk control file in accordance with the present invention. - The present invention provides a novel application on a removable disk used within a computing environment to maintain application software, data and devices. In accordance with the present invention, a user inserts the removable disk containing the application software to be executed into the personal computer, and the software application or device is automatically launched/started and readied for use. The present invention advantageously allows a user to maintain everything he or she needs using a removable disk.
- Referring now to
FIGS. 1-2 , exemplary hardware in which the present invention may be embodied will be described. As illustrated, the preferred platform is a personal computer (PC) 20, which may comprise Windows® 95/98 or Windows NT®. Workstation-based personal computer having, e.g., an Intel Pentium® processor or higher, a long-term non-removable storage device (e.g., a IDE or SCSI hard disk), a removable media drive (e.g., CD-R, CD-RW, DVD, or other removable floppy or hard disk drive), random access memory (RAM), communication peripherals (e.g., network interface card, modem, and/or terminal adapter), and suitable application programs (e.g., Dial-up networking software and a Web Browser). - As shown, the
PC 20 may be divided between internal and external components. The internal components include a Basic Input/Output System (BIOS) 70 and a processor (CPU) 66 that control the overall functioning of thePC 20.Memory 64, ahard disk drive 76, afloppy disk drive 74, atape drive 78, a CD-ROM drive 80, a MODEM/Terminal Adaptor/Network Interface Card 82, and a removable media drive 52 a are also connected to theCPU 66. The removable media drive 52 a or 52 b operates to read and/or write to a storage media contained within aremovable storage cartridge 28. Theexemplary PC 20 ofFIG. 1 is configured with two removable media drives 52 a and 52 b to emphasize that a removable media drive can be implemented in either internal or external form. - By way of a non-limiting example, the
removable media 28 may comprise a ZIP® disk manufactured by Iomega Corporation, Roy, Utah. Each Iomega ZIP® disk contains a unique serial number that is written to a predetermined track during the formatting process which may be used as the unique identifier. The serial number is preferably created by but not limited to a pseudo random number generator. Further, while themedia 28 has been described in terms of a ZIP® disk, it is not limited to the ZIP® disk, as the use of other removable media types having a unique serial number is within the scope and spirit of the present invention such as CD-R, DVD-RAM, and other removable floppy and hard disks. - The MODEM/Terminal Adaptor/Network Interface Card 82 may comprise individual cards performing communications-related functions, as known in the art. The MODEM/Terminal Adaptor/Network Interface Cards 82 are included within
PC 20 to provide communications to external networks to which thePC 20 is connected. In particular, the MODEM/Terminal Adaptor/Network Interface Card 82 may be used to access LAN 14, ISP 18 and network infrastructure 12. - Communications between internal and external devices may be accomplished via controllers provided within the
PC 20. A serial/parallel/USB port controller (which may comprise separate controllers) 58, a monitor controller (video card) 60, and a keyboard and mouse controller 62 each provide an interface between theCPU 66 and an external removable media drive 52 b (or printer), monitor 54, and keyboard and mouse device 56, respectively. A hard disk andfloppy disk controller 72 serves as an interface between theCPU 66 and thehard disk 76 and the CD-ROM drive 80, and thefloppy disk 74 andtape drive 78, respectively. It will be appreciated by those skilled in the art that thedisk controller 72 may comprise separate floppy and hard disk controllers (e.g., IDE or SCSI controller). - A
removable media controller 68 serves as an interface between the removable media drive 52 a and theCPU 66. For example, theremovable disk controller 68 may comprise a Small Computer System Interface (SCSI) or Integrated Drive Electronics (IDE) interface controller. A hard disk andfloppy disk controller 72 serves as an interface between theCPU 66 and thehard disk 76 and the CD-ROM drive 80, and thefloppy disk 74 andtape drive 78, respectively. Alternatively, the removable media drive 52 a may utilize thedisk controller 72 as an interface to theCPU 66. - Referring now to
FIG. 2 , there is illustrated a block diagram of an exemplary media drive 52 having a SCSI interface to the PC 20 (via controller 68). The media drive 52 preferably comprises, a ZIP® drive, manufactured by Iomega Corporation, Roy, Utah; however, the present invention is not limited to such removable media drives and other media drives may be used as media drive 52. The media drive 52 includes components that provide for communication between the read/write channel for the media (lower right side of diagram) and the PC 20 (upper left side of diagram). The media drive 52 includes anAIC chip 101 which performs theSCSI 102, the direct memory access (DMA) 103, anddisk formatter 104 functions. The interface also includes aPHAEDRUS 105 which includes an 8032microcontroller 106, a 1kbyte RAM 107 and an application specific integrated circuit (ASIC) 108. TheASIC 108 may perform various functions, such as servo sequencing, data splitting, EOC, ENDEC, A-to-D, and D-to-A conversion. The communication between the media drive 52 and thePC 20 is accomplished through transfers of data between the input/output channel of the media drive 52 and the media controller 68 (e.g., SCSI controller) of thePC 20. - Referring now to
FIG. 3 , there is a flow chart illustrating the processes performed by the present invention. As will become evident to those of ordinary skill in the art, the features and aspects of the present invention discussed below may be implemented by any suitable combination of hardware, software and/or firmware. Preferably, the present invention runs as a background task or service that recognizes and reads a task disk control file stored on the removable media upon detection of insertion of the removable media into the computer. The task disk control file includes instructions to configure the computer operating environment and launch application software resident on the removable media or the computer's hard disk (or on both). Also, the task disk control file may be used to start application software that controls computer devices and/or the devices themselves. Upon closing the predetermined application software or device, data files are saved in accordance with instructions in the control file, the computer's environment is cleaned-up and the removable media is ejected. As will be described below, the system of the present invention serves to greatly simplify the use and operation of computer application software, devices and peripherals because users are not required to have any knowledge of how to launch the application or start the device or peripheral they wish to use. In other words, all the user needs to know is that the application, device or peripheral he or she wants to use will be automatically launched/started upon insertion of the removable media. - The details of the present invention will now be described with reference to
FIG. 3 . An application or system service running on thePC 20 monitors device commands to and from the removable media drive 52 (step 200). It is preferable that this be a background application or service that is loaded when the computer is booted-up. An example of such an application to monitor device commands to the removable media drive 52 is IOwatch, available from IOmega Corporation, Roy, Utah. The application or service resides on thecomputer 20 and automatically, and without requiring any user intervention, recognizes the insertion of a piece of removable media. - At
step 202 it is determined if a monitored device command is “a media change condition.” Media change conditions indicate thatremovable media 28 has been inserted in to the removable media drive 52 or that some action has occurred with regard to theremovable media 28 currently in thedrive 52. If no media change condition is present atstep 202, then processing returns to step 200 to monitor for subsequent device commands. - If a media change condition is present at
step 202, then the present invention begins its processing by identifying an event type associated with the media change condition. Events that may be identified and routed atstep 204 include, but are not limited to: device events and events resulting from calls from a “participating application” 201. A “participating application” 201 is defined herein as a software application that has knowledge of, and cooperates with, the present invention by making and accepting event calls to and from the present invention. The participating application may be located on, e.g., thehard disk 76, theremovable media 28, a CD-ROM, or network location. In addition, participating applications may control peripherals and devices attached to or within the computer (e.g., tape drives, scanners, etc.). Media change conditions are provide to the present invention by known mechanisms such as inter-application messages, program calls, and event notifications. - A first identified event may be a media insertion event (step 206), which is a condition that exists when the
removable media 28 is inserted into the removable media drive 52. The media may be detected as inserted by the drive in accordance with the method of U.S. Pat. No. 5,854,719, to Ginosar et al., which is incorporated herein by reference in its entirety. Atstep 208, the system then checks for the presence of a task disk control file (TDCF) 220 on themedia 28. - An exemplary task
disk control file 220 is illustrated inFIG. 4 , and contains configuration and execution information and regarding the participating application. For example theTDCF 220 may contain information such as the executable filename, path information, and Windows® registry data, including the identification of necessary device drivers, Dynamic Link Libraries, VxDs, etc. The contents of the TDCF will be discussed in greater detail below. - If a valid task disk control file (TDCF) 220 does not exist (step 210), the disk is mounted for use, however, the system returns to step 200 to monitor for subsequent device commands, as the disk cannot be used to configure and launch an application or device. Alternatively, a message may be generated and displayed to the user indicating the
TDCF 220 is not valid. If avalid TDCF 220 exists, then atstep 212, a unique identifier (e.g., serial number) of themedia 28 is read. In accordance with a feature of the present invention, theTDCF 220 may be encrypted using the media serial number as an encryption key to provide an added measure of security and to prevent the application software from being copied and run from another piece of media. For the purposes of the present invention, any encryption algorithm may be used. - The media serial number may be obtained by an application running on the
PC 20 that reads the unique identifier and authentication code. This is performed by querying the media using an application programming interface (API) such as the Iomega Ready API, or other suitable method. - The Iomega Ready API when invoked causes the media drive to read the unique serial number from the predetermined track by using the SCSI 0.times.06 Non-Sense Command. In particular, by invoking the Disk Status Page (page 0.times.02) of the Non-Sense Command, the media serial number may be determined by reading offset bytes 20-59 of the returned data structure. Exemplary source code for reading the serial number of an Iomega ZIP® drive and disk is as follows:
Void CClientApp::GetZipDrive( ) { int j,k; m_DriveNum = 0; for(j = 0;j < 26;j++ // scan the drive and find the IOMEGA drives { if(IsIomegaDrive(j)) { k = GetGeneralDevType(j); if( k == DRIVE_IS_ZIP ) { m_DriveNum = j; j = 26; } } } } void CClientApp::GetSerialNumber( ) { unsigned char szBuffer[1024]; memset(szBuffer,0,sizeof(szBuffer)); memset(&m_SerialNumber,0,40); GetInfoNonSense(m_DriveNum,0x02,szBuffer); Memcpy(&m_SerialNumber,&szBuffer[22],39); } - It can be appreciated that the unique serial number should contain a sufficient number of bits (length) to ensure that no two pieces of media have the same identifier. For example, each Iomega ZIP® disk contains a unique 39 byte (312 bits) serial number, and other bit lengths may be utilized.
- Once the media serial number is read, the task disk control file (TDCF) 220 is processed at
step 214, where it is decrypted using the media serial number as a decryption key. It is noted that encryption of theTDCF 220 is not necessary for the operation of the present invention, and is provided as a security feature to prevent, e.g., illegal copying of copyrighted program files on theremovable media 28. Accordingly, step 210 may be provided with a mechanism to determine if the TDCF is encrypted, and if not, jump to step 216. - At
step 216, theunencrypted TDCF 220 is read and the system environment is configured in accordance with information contained in theTDCF 220 prior to launching the participating application. - Referring to
FIG. 4 , theTDCF 220 contains three sections of configuration information labeled as follows: pre-run, application run, and clean-up. The pre-run section configures registry information such that the operating system is aware of the path, environmental variables and commands to launch the participating application. Optionally, the pre-run section may specify files (e.g., executable files, DLLs, device drivers, etc.) that are to be copied to the hard drive to properly execute the participating application. The application run section instructs the operating system to load the participating application, which launches the participating application for use by a user (see, step 218, below). The clean-up section removes all registry information added by the pre-run section (see, step 224, below). Optionally, the clean-up section may remove from the hard drive the files (e.g., executable files, DLLs, device drivers, etc.) copied thereto to execute the participating application. - In accordance with the present invention, the
TDCF 220 may configure the system environment to run applications in several modes. In a first mode of operation, the participating application is stored on, and run from, theremovable media 28 upon insertion. In this first mode of operation, everything necessary to run the participating application is maintained and executed from theremovable media 28. Thus, no files are copied to the hard drive, nor are any files required to be on the hard drive to run the participating application. - In a second mode of operation, the participating application cannot be run from the
removable media 28 alone. In this mode, certain files are copied to the hard disk as specified in the pre-run section of theTDCF 220. These files may include, but are not limited to the above-mentioned executable files, DLLs, device drivers, etc. It may be necessary to copy files to the hard disk to because of limitations in speed or size of theremovable media 28. In the second mode, when the participating application is closed or theremovable disk 28 ejected, the previously copied files are removed from the hard drive in accordance with the clean-up section such that the hard disk is returned to essentially the same state it was in prior to the insertion of theremovable media 28. - In a third mode, the participating application cannot be run from the
removable media 28 alone, as in the second mode. However, in this mode when the participating application is closed or the disk ejected, the files are not removed from the hard drive. In the third mode, the previously copied files remain on the hard disk in accordance with the clean-up section, such that any subsequent insertion of theremovable media 28 would not require copying of the specified files to the hard drive. This third mode of operation speeds up the launching of the participating application for second and subsequent insertions of theremovable disk 28 into the removable media drive 52. - In a fourth mode, the participating application is installed to, and stored on, the computer's hard drive. The participating application's installation program preferably includes an option to make it “participating” in accordance with the present invention. Optionally, a plug-in may be used to hook into the participating application to make it “participating” in accordance with the present invention. The pre-run section of the TDCF contains all of the instructions necessary to automatically launch the participating application from the hard drive and, optionally, load data files as the participating application is launched. The data files are preferably on the
removable media 28, but also may reside on the hard disk. In this fourth mode, theTDCF 220 contains a list of instructions to open and close the participating application, such that the removable media acts as a “key” to automatically open the participating application upon insertion into the removable media drive 52. - It is noted that the
TDCF 220 ofFIG. 4 is provided herein for exemplary purposes only. Further, theTDCF 220 may contain additional or fewer instructions to configure thecomputer 20, copy files to thecomputer 20, etc. than illustrated. Further, additional or few modes of operation are possible. In accordance with the present invention, theTDCF 220 contains the instructions necessary to properly configure and launch the participating application upon insertion of theremovable media 28, and gracefully remove configuration settings and save data files without the need for user intervention. - Returning again to FIG. e, at
step 218, once thePC 20 is configured in accordance with theTDCF 220, the participating application is launched for use and the system returns to step 200 to monitor for new events. - Returning again to step 204, if an event identified is a Save/Close Complete event, then processing continues at
step 222. A Save/Close Complete event occurs when the user has finished using the participating application and either selects exit or clicks the “.pi.” box (i.e., close window box) in the application window. Atstep 222 the participating application saves all data files, deletes all temporary files and indicates to the system that it is ready to terminate. The data files may be saved in accordance with a predetermined file path set by theTDCF 220. Atstep 224 all configuration information is removed from thePC 20 in accordance with the clean-up section of theTDCF 220. The clean-up section will perform certain clean-up functions based on a mode of operation, as noted above. Next, atstep 226, the participating application terminates and theremovable media 28 is ejected by the present invention from themedia drive 52. Processing then continues atstep 200. - Again returning to step 240, if an event detected a Media Eject Request Event, then processing continues at
step 228. A Media Eject Request Event is a condition that exists when the user has initiated an eject function by pressing an eject button provided on thedrive 52 or through a provide software eject feature. Atstep 230, the participating application is notified via inter-application mechanisms, such as a message, that a “request for media eject” was detected. Next, atstep 232, the system executes steps 222-226 as discussed above to complete. Once the present invention is notified of a completion atstep 234, processing returns to step 200 to monitor for new events. - Thus, as described above, the present invention provides a new and improved system for managing data files and applications that requires very little, if any, user attention. In accordance with the present invention, the user need only know that insertion of a particular piece of removable media launches a particular application or starts a particular device or peripheral that he or she wants to use. The user's data files are saved to the same piece of removable media or other specified location for easy retrieval, therefore, the user's data is easily obtainable for use when the application is launched. When the user has completed using the application and exits, the removable media is ejected from the computer to be placed away for safekeeping.
- It is noted that the foregoing examples have been provided merely for the purpose of explanation and are in no way to be construed as limiting of the present invention. While the invention has been described with reference to preferred embodiments, it is understood that the words which have been used herein are words of description and illustration, rather than words of limitations. Further, although the invention has been described herein with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed herein; rather, the invention extends to all functionally equivalent structures, methods and uses, such as are within the scope of the appended claims. Those skilled in the art, having the benefit of the teachings of this specification, may effect numerous modifications thereto and changes may be made without departing from the scope and spirit of the invention in its aspects.
Claims (6)
1. A computer-readable medium having stored thereon a task list control file comprising: a pre-run section containing instructions to be executed by a computer-implemented device prior to launching a predetermined participating application; an application run section data containing instructions to launch said participating application; and a clean-up section containing instructions to be executed upon closing said participating application.
2. The task list control file of claim 1 , wherein said pre-run section comprises instructions to configure registry information such that the operating system is aware of at least one of a path, environmental variables and commands to launch said participating application.
3. The task list control file of claim 2 further comprising instructions to specify files to be copied to a hard drive of said computer-implemented device to execute said participating application.
4. The task list control file of claim 1 , wherein said application run section comprises instructions for the operating system to load said participating application for use.
5. The task list control file of claim 1 , wherein said clean-up section removes all registry information added by the pre-run section.
6. The task list control file of claim 5 , wherein said clean-up section removes from the hard drive the files copied thereto to execute the participating application as specified by said pre-run section.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/748,340 US20070214187A1 (en) | 1999-07-26 | 2007-05-14 | Self-Contained Application Disk for Automatically Launching Application Software or Starting Devices and Peripherals |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/360,337 US6529992B1 (en) | 1999-07-26 | 1999-07-26 | Self-contained application disk for automatically launching application software or starting devices and peripherals |
US10/367,650 US20040083473A1 (en) | 1999-07-26 | 2003-02-14 | Self-contained application disk for automatically launching application software or starting devices and peripherals |
US11/748,340 US20070214187A1 (en) | 1999-07-26 | 2007-05-14 | Self-Contained Application Disk for Automatically Launching Application Software or Starting Devices and Peripherals |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/360,337 Continuation US6529992B1 (en) | 1999-07-26 | 1999-07-26 | Self-contained application disk for automatically launching application software or starting devices and peripherals |
US10/367,650 Division US20040083473A1 (en) | 1999-07-26 | 2003-02-14 | Self-contained application disk for automatically launching application software or starting devices and peripherals |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070214187A1 true US20070214187A1 (en) | 2007-09-13 |
Family
ID=23417562
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/360,337 Expired - Lifetime US6529992B1 (en) | 1999-07-26 | 1999-07-26 | Self-contained application disk for automatically launching application software or starting devices and peripherals |
US10/367,650 Abandoned US20040083473A1 (en) | 1999-07-26 | 2003-02-14 | Self-contained application disk for automatically launching application software or starting devices and peripherals |
US11/748,340 Abandoned US20070214187A1 (en) | 1999-07-26 | 2007-05-14 | Self-Contained Application Disk for Automatically Launching Application Software or Starting Devices and Peripherals |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/360,337 Expired - Lifetime US6529992B1 (en) | 1999-07-26 | 1999-07-26 | Self-contained application disk for automatically launching application software or starting devices and peripherals |
US10/367,650 Abandoned US20040083473A1 (en) | 1999-07-26 | 2003-02-14 | Self-contained application disk for automatically launching application software or starting devices and peripherals |
Country Status (3)
Country | Link |
---|---|
US (3) | US6529992B1 (en) |
EP (1) | EP1072976A3 (en) |
JP (1) | JP2001075813A (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080120439A1 (en) * | 2006-11-16 | 2008-05-22 | International Business Machines Corporation | Automated solution to provide immediate requisite access to data and applications on an attached external device |
US20090216916A1 (en) * | 2008-02-27 | 2009-08-27 | Samsung Electronics Co., Ltd. | Method and apparatus for inputting/outputting data using virtualization technique |
US20090313406A1 (en) * | 2008-06-16 | 2009-12-17 | Suh Sang-Bum | Apparatus and method for adaptation of input/output interface in virtualization environment |
US20100064063A1 (en) * | 2008-04-04 | 2010-03-11 | Option | Wireless modem device usable on computer device without driver installation |
US20100185843A1 (en) * | 2009-01-20 | 2010-07-22 | Microsoft Corporation | Hardware encrypting storage device with physically separable key storage device |
US20100318810A1 (en) * | 2009-06-10 | 2010-12-16 | Microsoft Corporation | Instruction cards for storage devices |
US20100325736A1 (en) * | 2009-06-17 | 2010-12-23 | Microsoft Corporation | Remote access control of storage devices |
US20110047599A1 (en) * | 2009-08-24 | 2011-02-24 | Wagan Sarukhanov | Microminiature personal computer and method of using thereof |
US20140156885A1 (en) * | 2011-08-26 | 2014-06-05 | Xin Lian | External Device Extension Method and External Device |
WO2014147865A1 (en) | 2013-03-18 | 2014-09-25 | Kabushiki Kaisha Toshiba | Information processing system, control program, and information processing device |
US10437608B2 (en) | 2009-08-24 | 2019-10-08 | Wagan Sarukhanov | Microminiature personal computer and method of using thereof |
Families Citing this family (103)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6954279B2 (en) * | 1998-12-08 | 2005-10-11 | Canon Kabushiki Kaisha | Automated output of user guide |
US20040230710A1 (en) * | 1999-07-27 | 2004-11-18 | Inline Connection Corporation | System and method of automatic installation of computer peripherals |
JP2001109617A (en) * | 1999-10-06 | 2001-04-20 | Seiko Epson Corp | Recording medium for setup and setup method |
US7152156B1 (en) * | 2000-02-17 | 2006-12-19 | Hart Intercivic, Inc. | Secure internet voting system with bootable disk |
US7444645B1 (en) * | 2000-04-21 | 2008-10-28 | Microsoft Corporation | Method and system for detecting content on media and devices and launching applications to run the content |
GB0017478D0 (en) * | 2000-07-18 | 2000-08-30 | Bit Arts Ltd | Computer software installation |
US6681324B1 (en) * | 2000-09-07 | 2004-01-20 | Cisco Technology, Inc. | Application appliance enabling operating system and applications to run from a CDROM by determining local configuration and license status |
US20020145632A1 (en) * | 2000-10-27 | 2002-10-10 | Shimon Shmueli | Portable interface for computing |
US7373656B2 (en) * | 2000-10-27 | 2008-05-13 | Sandisk Il Ltd. | Automatic configuration for portable devices |
US20020162009A1 (en) * | 2000-10-27 | 2002-10-31 | Shimon Shmueli | Privacy assurance for portable computing |
US11467856B2 (en) | 2002-12-12 | 2022-10-11 | Flexiworld Technologies, Inc. | Portable USB device for internet access service |
US20020101990A1 (en) * | 2001-02-01 | 2002-08-01 | Harumi Morino | Data receiving apparatus and data reproducing apparatus |
FR2823576B1 (en) * | 2001-04-12 | 2004-04-02 | Gerard Sinpraseuth | REMOVABLE RECORDING MEDIUM |
FR2824929B1 (en) | 2001-05-18 | 2003-08-08 | Gemplus Card Int | APPLICATION DEPLOYMENT FROM A CHIP CARD |
US20030105970A1 (en) * | 2001-11-30 | 2003-06-05 | Phillip Yuan Pei Jen | Systems and methods for enforcing single computer use of software |
GB0205751D0 (en) * | 2002-03-12 | 2002-04-24 | James Barry E | Improvements relating to memory devices |
US20030188145A1 (en) * | 2002-03-27 | 2003-10-02 | Richardson Tanna Marie | Method and system for peripheral device installation |
GB2389208A (en) * | 2002-05-31 | 2003-12-03 | Child Safety Network Ltd | Raising an alert |
US7603406B2 (en) * | 2002-07-25 | 2009-10-13 | Sony Corporation | System and method for wireless software download and remote transaction settlement |
JP2004078268A (en) * | 2002-08-09 | 2004-03-11 | Fujitsu Ltd | Information processor, information processing method and program |
US7069354B2 (en) * | 2002-10-01 | 2006-06-27 | Hewlett-Packard Development Company, L.P. | Method and apparatus for identifying multiple paths to a SCSI device using a calculated unique identifier |
US7441108B2 (en) * | 2002-11-19 | 2008-10-21 | Ken Scott Fisher | Portable memory drive with portable applications and cross-computer system management application |
US20040103115A1 (en) * | 2002-11-26 | 2004-05-27 | Vandewater Eric J. | System and method of protecting digital content |
US7908401B2 (en) | 2002-12-12 | 2011-03-15 | Flexiworld Technology, Inc. | Method and device for wireless communication between computing devices |
WO2004057474A1 (en) * | 2002-12-20 | 2004-07-08 | Koninklijke Philips Electronics N.V. | Pre-configured backup dvd-rws |
WO2004072973A1 (en) * | 2003-02-12 | 2004-08-26 | Koninklijke Philips Electronics N.V. | Storage medium with reserved area for file system data and application start-up data |
US20040172526A1 (en) * | 2003-02-27 | 2004-09-02 | Tann Johnathan P. | Universal loader for portable electronic devices |
US20040186746A1 (en) * | 2003-03-21 | 2004-09-23 | Angst Wendy P. | System, apparatus and method for storage and transportation of personal health records |
JP2004295358A (en) * | 2003-03-26 | 2004-10-21 | Internatl Business Mach Corp <Ibm> | Information processor, encryption processing system thereof and method for controlling external storing device |
CN107832241B (en) * | 2003-04-11 | 2021-10-08 | 富意科技公司 | Integrated circuit storage device or method capable of realizing automatic operation |
US7073013B2 (en) * | 2003-07-03 | 2006-07-04 | H-Systems Flash Disk Pioneers Ltd. | Mass storage device with boot code |
CN100383756C (en) * | 2003-07-22 | 2008-04-23 | 深圳市朗科科技有限公司 | Method for implementing automatic performance using semiconductor memory device |
JP3961462B2 (en) * | 2003-07-30 | 2007-08-22 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Computer apparatus, wireless LAN system, profile updating method, and program |
US20050038879A1 (en) * | 2003-08-14 | 2005-02-17 | International Business Machines Corporation | System and method for discovery of remote device driver functionality and interface |
US7225448B2 (en) * | 2003-08-14 | 2007-05-29 | Lenovo (Singapore) Pte. Ltd. | System and method for hibernating application state data on removable module |
US7308584B2 (en) * | 2003-08-14 | 2007-12-11 | International Business Machines Corporation | System and method for securing a portable processing module |
US20050066324A1 (en) * | 2003-09-22 | 2005-03-24 | Microsoft Corporation | Method and system for distributing and installing software |
JP4532877B2 (en) * | 2003-10-16 | 2010-08-25 | 株式会社アイ・オー・データ機器 | Removable media device, host device, program and recording medium thereof |
US7275150B2 (en) * | 2004-03-15 | 2007-09-25 | International Business Machines Corporation | Method and system for adding frequently selected applications to a computer startup sequence |
US7370166B1 (en) | 2004-04-30 | 2008-05-06 | Lexar Media, Inc. | Secure portable storage device |
US7797697B2 (en) * | 2004-05-05 | 2010-09-14 | Bea Systems, Inc. | System and method for deploying applications with library modules |
US20050251495A1 (en) * | 2004-05-06 | 2005-11-10 | Bea Systems, Inc. | System and method for unified file management |
US7730112B2 (en) * | 2004-05-10 | 2010-06-01 | Bea Systems Inc. | Scoped applications |
US7428733B2 (en) * | 2004-05-13 | 2008-09-23 | Bea Systems, Inc. | System and method for custom module creation and deployment |
US7814484B2 (en) * | 2004-05-14 | 2010-10-12 | Bea Systems, Inc. | System and method for web application extensibility |
US7707572B2 (en) * | 2004-05-19 | 2010-04-27 | Bea Systems, Inc. | System and method for application container architecture |
US20060026414A1 (en) * | 2004-07-29 | 2006-02-02 | International Business Machines Corporation | Managing the environmental configuration for an application disposed in removable storage |
US7530064B2 (en) * | 2004-09-21 | 2009-05-05 | Hewlett-Packard Development Company, L.P. | Method and apparatus for automated registry clean-up |
US20060118636A1 (en) * | 2004-12-07 | 2006-06-08 | Planready, Inc. | System and method for coordinating movement of personnel |
US7712086B2 (en) * | 2004-12-15 | 2010-05-04 | Microsoft Corporation | Portable applications |
EP1836706A4 (en) * | 2005-01-12 | 2010-08-25 | Samsung Electronics Co Ltd | Information storage medium storing management information of application executable from a plurality of storage media, and method and apparatus for executing the application |
EP1696321A1 (en) * | 2005-02-23 | 2006-08-30 | Deutsche Thomson-Brandt Gmbh | Method and apparatus for executing software applications |
CN100365572C (en) * | 2005-03-03 | 2008-01-30 | 华为技术有限公司 | Software packaging method |
CN1648863A (en) * | 2005-03-07 | 2005-08-03 | 优网通国际资讯股份有限公司 | Portable software application method |
US20060288057A1 (en) * | 2005-06-15 | 2006-12-21 | Ian Collins | Portable data backup appliance |
JP4502898B2 (en) * | 2005-07-26 | 2010-07-14 | 株式会社バッファロー | External hard disk storage device, external hard disk storage device control method, and external hard disk storage device control program |
US7555573B2 (en) * | 2005-08-05 | 2009-06-30 | Microsoft Corporation | Initiating software responses based on a hardware action |
US7702830B2 (en) * | 2005-10-12 | 2010-04-20 | Storage Appliance Corporation | Methods for selectively copying data files to networked storage and devices for initiating the same |
US20070162271A1 (en) * | 2005-10-12 | 2007-07-12 | Storage Appliance Corporation | Systems and methods for selecting and printing data files from a backup system |
US7899662B2 (en) * | 2005-10-12 | 2011-03-01 | Storage Appliance Corporation | Data backup system including a data protection component |
US7844445B2 (en) * | 2005-10-12 | 2010-11-30 | Storage Appliance Corporation | Automatic connection to an online service provider from a backup system |
US7813913B2 (en) * | 2005-10-12 | 2010-10-12 | Storage Appliance Corporation | Emulation component for data backup applications |
US20070091746A1 (en) * | 2005-10-12 | 2007-04-26 | Storage Appliance Corporation | Optical disc for simplified data backup |
US7818160B2 (en) * | 2005-10-12 | 2010-10-19 | Storage Appliance Corporation | Data backup devices and methods for backing up data |
US20080028008A1 (en) * | 2006-07-31 | 2008-01-31 | Storage Appliance Corporation | Optical disc initiated data backup |
US8195444B2 (en) * | 2005-10-12 | 2012-06-05 | Storage Appliance Corporation | Systems and methods for automated diagnosis and repair of storage devices |
US8069271B2 (en) * | 2005-10-12 | 2011-11-29 | Storage Appliance Corporation | Systems and methods for converting a media player into a backup device |
US7822595B2 (en) * | 2005-10-12 | 2010-10-26 | Storage Appliance Corporation | Systems and methods for selectively copying embedded data files |
US7917487B2 (en) | 2005-12-13 | 2011-03-29 | Microsoft Corporation | Portable application registry |
KR100809295B1 (en) * | 2006-04-06 | 2008-03-04 | 삼성전자주식회사 | Apparatus and method for installing software |
US9122719B2 (en) * | 2006-04-28 | 2015-09-01 | Bmc Software, Inc. | Database application federation |
US7984995B2 (en) * | 2006-05-24 | 2011-07-26 | Smart Technologies Ulc | Method and apparatus for inhibiting a subject's eyes from being exposed to projected light |
US20100115145A1 (en) * | 2006-05-26 | 2010-05-06 | Smart Technologies Ulc | Plug-and-play device and method of using the same |
US8190785B2 (en) * | 2006-05-26 | 2012-05-29 | Smart Technologies Ulc | Plug-and-play device and method for enhancing features and settings in an interactive display system |
US20080005472A1 (en) * | 2006-06-30 | 2008-01-03 | Microsoft Corporation | Running applications from removable media |
US20080082453A1 (en) * | 2006-10-02 | 2008-04-03 | Storage Appliance Corporation | Methods for bundling credits with electronic devices and systems for implementing the same |
US20080126446A1 (en) * | 2006-11-27 | 2008-05-29 | Storage Appliance Corporation | Systems and methods for backing up user settings |
US20080163201A1 (en) * | 2006-12-29 | 2008-07-03 | Fabrice Jogand-Coulomb | Apparatuses for launching a program application |
US8533741B2 (en) * | 2006-12-29 | 2013-09-10 | Sandisk Technologies Inc. | Methods for launching a program application |
WO2008085323A2 (en) * | 2006-12-29 | 2008-07-17 | Sandisk Corporation | Method and apparatus for launching a program application |
US20080172487A1 (en) * | 2007-01-03 | 2008-07-17 | Storage Appliance Corporation | Systems and methods for providing targeted marketing |
US20080226082A1 (en) * | 2007-03-12 | 2008-09-18 | Storage Appliance Corporation | Systems and methods for secure data backup |
US20080271112A1 (en) * | 2007-04-30 | 2008-10-30 | Waker Philip M | Automatic file transfer |
US20090031298A1 (en) * | 2007-06-11 | 2009-01-29 | Jeffrey Brunet | System and method for automated installation and/or launch of software |
US20090030955A1 (en) * | 2007-06-11 | 2009-01-29 | Storage Appliance Corporation | Automated data backup with graceful shutdown for vista-based system |
US20090006968A1 (en) * | 2007-06-29 | 2009-01-01 | Keoki Trask | System, computer-implemented method, and removable computer-readable medium with software for creating and displaying dynamically and automatically in real time a transient themed digital multimedia slide show presentation |
EP2015212A1 (en) * | 2007-06-29 | 2009-01-14 | Axalto SA | Portable mass storage device with hooking process |
US9092638B2 (en) * | 2007-08-16 | 2015-07-28 | Blackberry Limited | System and method for managing docking applications for a portable electronic device |
JP2009086955A (en) * | 2007-09-28 | 2009-04-23 | Toshiba Corp | Camera apparatus and control method thereof |
JP4451480B2 (en) * | 2007-11-01 | 2010-04-14 | オリンパスイメージング株式会社 | Electronic camera and storage medium |
US20090183182A1 (en) * | 2008-01-10 | 2009-07-16 | Microsoft Corporation | Dynamic Composition of Virtualized Applications |
JP2012508424A (en) * | 2008-11-07 | 2012-04-05 | オパンガ ネットワークス インコーポレイテッド | Portable data storage device using host device to start data transfer |
US20100313135A1 (en) * | 2009-06-05 | 2010-12-09 | Mark Rogers Johnson | Virtual Disc Enabled Media Player |
US8413137B2 (en) * | 2010-02-04 | 2013-04-02 | Storage Appliance Corporation | Automated network backup peripheral device and method |
JP4922421B2 (en) * | 2010-02-23 | 2012-04-25 | 株式会社バッファロー | External hard disk storage device, external hard disk storage device control method, and external hard disk storage device control program |
JP5335737B2 (en) * | 2010-07-23 | 2013-11-06 | レノボ・シンガポール・プライベート・リミテッド | Computer that can change the operating environment |
TWI505189B (en) | 2010-08-27 | 2015-10-21 | Ibm | A method computer program and system for automatic upgrade of virtual appliances |
JP5002719B1 (en) | 2011-03-10 | 2012-08-15 | 株式会社東芝 | Information processing device, external storage device, host device, relay device, control program, and information processing device control method |
EP2745203B1 (en) | 2011-08-19 | 2016-09-21 | Kabushiki Kaisha Toshiba | Information processing apparatus |
CN107276936B (en) | 2011-10-27 | 2020-12-11 | 英特尔公司 | Block-based Crest Factor Reduction (CFR) |
US9203893B2 (en) * | 2013-03-08 | 2015-12-01 | Lincoln Global, Inc. | System and method for installing device drivers on welding equipment |
DE102013021158A1 (en) * | 2013-12-10 | 2015-06-11 | Fresenius Medical Care Deutschland Gmbh | Method for updating and / or upgrading the operating software of an electronic device |
US9575775B2 (en) * | 2014-03-07 | 2017-02-21 | International Business Machines Corporation | Autorun on eject |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4833554A (en) * | 1987-02-25 | 1989-05-23 | Tandon Corporation | Hard disk drive module and receptacle therefor |
US5488522A (en) * | 1994-11-14 | 1996-01-30 | Combyte, Inc. | Ejection apparatus for ejecting storage media positioned in a computer mass storage media drive |
US5493461A (en) * | 1994-11-14 | 1996-02-20 | Combyte, Inc. | Storage media lockout device for a computer mass storage media drive |
US5711672A (en) * | 1994-07-01 | 1998-01-27 | Tv Interactive Data Corporation | Method for automatically starting execution and ending execution of a process in a host device based on insertion and removal of a storage media into the host device |
US5732266A (en) * | 1994-09-02 | 1998-03-24 | Compaq Computer Corporation | Storage medium storing application programs and application initialization files and automatic launching of computer applications stored on the storage medium |
US5764972A (en) * | 1993-02-01 | 1998-06-09 | Lsc, Inc. | Archiving file system for data servers in a distributed network environment |
US5819082A (en) * | 1995-06-07 | 1998-10-06 | Sierra On-Line, Inc. | Data storage optimization using an access order resource list |
US5832523A (en) * | 1995-08-30 | 1998-11-03 | Kabushiki Kaisha Toshiba | Archiving device and data file server using data file recorded in division over recording media |
US5832213A (en) * | 1996-07-03 | 1998-11-03 | Sun Microsystems, Inc. | Flexible mounting and unmounting of user removable media |
US5999722A (en) * | 1994-11-18 | 1999-12-07 | Iomega Corporation | Method of cataloging removable media on a computer |
US6006034A (en) * | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
US6170055B1 (en) * | 1997-11-03 | 2001-01-02 | Iomega Corporation | System for computer recovery using removable high capacity media |
US6205558B1 (en) * | 1998-10-07 | 2001-03-20 | Symantec Corporation | Recovery of file systems after modification failure |
US6208044B1 (en) * | 1993-08-13 | 2001-03-27 | Apple Computer, Inc. | Removable media ejection system |
US6222799B1 (en) * | 1997-05-02 | 2001-04-24 | Intellectual Science And Technology Inc. | High-performance information processing apparatus having multitasking functions |
US6249806B1 (en) * | 1998-04-03 | 2001-06-19 | Fujitsu Limited | Apparatus and method for providing information about two-way computer communication services |
US6405362B1 (en) * | 1998-11-13 | 2002-06-11 | Microsoft Corporation | Automatic software installation and cleanup |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5642417A (en) * | 1994-11-25 | 1997-06-24 | Testdrive Corporation | Virtualized installation of material |
US5680540A (en) * | 1995-01-31 | 1997-10-21 | Bell Usa, L.P. | Suspend-to-disk system for removable hard drive |
DE69613156T2 (en) * | 1995-10-09 | 2001-10-25 | Matsushita Electric Ind Co Ltd | Optical playback device for playing encrypted information |
US6496979B1 (en) * | 1997-10-24 | 2002-12-17 | Microsoft Corporation | System and method for managing application installation for a mobile device |
EP0914001A1 (en) * | 1997-10-28 | 1999-05-06 | CANAL+ Société Anonyme | Downloading of applications in a digital decoder |
FR2780177B1 (en) * | 1998-06-17 | 2001-10-05 | Schlumberger Ind Sa | SOFTWARE PROTECTION SYSTEM |
-
1999
- 1999-07-26 US US09/360,337 patent/US6529992B1/en not_active Expired - Lifetime
-
2000
- 2000-07-21 EP EP00402100A patent/EP1072976A3/en not_active Withdrawn
- 2000-07-26 JP JP2000225696A patent/JP2001075813A/en not_active Withdrawn
-
2003
- 2003-02-14 US US10/367,650 patent/US20040083473A1/en not_active Abandoned
-
2007
- 2007-05-14 US US11/748,340 patent/US20070214187A1/en not_active Abandoned
Patent Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4833554A (en) * | 1987-02-25 | 1989-05-23 | Tandon Corporation | Hard disk drive module and receptacle therefor |
US5764972A (en) * | 1993-02-01 | 1998-06-09 | Lsc, Inc. | Archiving file system for data servers in a distributed network environment |
US6208044B1 (en) * | 1993-08-13 | 2001-03-27 | Apple Computer, Inc. | Removable media ejection system |
US5711672A (en) * | 1994-07-01 | 1998-01-27 | Tv Interactive Data Corporation | Method for automatically starting execution and ending execution of a process in a host device based on insertion and removal of a storage media into the host device |
US5732266A (en) * | 1994-09-02 | 1998-03-24 | Compaq Computer Corporation | Storage medium storing application programs and application initialization files and automatic launching of computer applications stored on the storage medium |
US5835759A (en) * | 1994-09-02 | 1998-11-10 | Compaq Computer Corporation | Launching computer applications |
US5488522A (en) * | 1994-11-14 | 1996-01-30 | Combyte, Inc. | Ejection apparatus for ejecting storage media positioned in a computer mass storage media drive |
US5493461A (en) * | 1994-11-14 | 1996-02-20 | Combyte, Inc. | Storage media lockout device for a computer mass storage media drive |
US5999722A (en) * | 1994-11-18 | 1999-12-07 | Iomega Corporation | Method of cataloging removable media on a computer |
US5819082A (en) * | 1995-06-07 | 1998-10-06 | Sierra On-Line, Inc. | Data storage optimization using an access order resource list |
US5832523A (en) * | 1995-08-30 | 1998-11-03 | Kabushiki Kaisha Toshiba | Archiving device and data file server using data file recorded in division over recording media |
US5832213A (en) * | 1996-07-03 | 1998-11-03 | Sun Microsystems, Inc. | Flexible mounting and unmounting of user removable media |
US6006034A (en) * | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
US6222799B1 (en) * | 1997-05-02 | 2001-04-24 | Intellectual Science And Technology Inc. | High-performance information processing apparatus having multitasking functions |
US6170055B1 (en) * | 1997-11-03 | 2001-01-02 | Iomega Corporation | System for computer recovery using removable high capacity media |
US6249806B1 (en) * | 1998-04-03 | 2001-06-19 | Fujitsu Limited | Apparatus and method for providing information about two-way computer communication services |
US6205558B1 (en) * | 1998-10-07 | 2001-03-20 | Symantec Corporation | Recovery of file systems after modification failure |
US6405362B1 (en) * | 1998-11-13 | 2002-06-11 | Microsoft Corporation | Automatic software installation and cleanup |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080120439A1 (en) * | 2006-11-16 | 2008-05-22 | International Business Machines Corporation | Automated solution to provide immediate requisite access to data and applications on an attached external device |
US8041863B2 (en) * | 2006-11-16 | 2011-10-18 | International Business Machines Corporation | Automated solution to provide personalized user environment on any public computer using portable storage devices with personalized user settings uploaded to local registry of public computer |
US20090216916A1 (en) * | 2008-02-27 | 2009-08-27 | Samsung Electronics Co., Ltd. | Method and apparatus for inputting/outputting data using virtualization technique |
US8966142B2 (en) * | 2008-02-27 | 2015-02-24 | Samsung Electronics Co., Ltd. | Method and apparatus for inputting/outputting virtual operating system from removable storage device on a host using virtualization technique |
US9164919B2 (en) | 2008-02-27 | 2015-10-20 | Samsung Electronics Co., Ltd. | Method and apparatus for inputting/outputting virtual operating system from removable storage device on a host using virtualization technique |
US8250244B2 (en) * | 2008-04-04 | 2012-08-21 | Interdigital Patent Holdings, Inc. | Wireless modem device usable on computer device without driver installation wherein computer has a proxy server application and pre-installed generic drivers |
US20100064063A1 (en) * | 2008-04-04 | 2010-03-11 | Option | Wireless modem device usable on computer device without driver installation |
US8527679B2 (en) * | 2008-06-16 | 2013-09-03 | Samsung Electronics Co., Ltd. | Apparatus and method for adaptation of input/output interface in virtualization environment |
US9046931B2 (en) | 2008-06-16 | 2015-06-02 | Samsung Electronics Co., Ltd. | Apparatus and method for adaptation of input/output interface in virtualization environment |
US20090313406A1 (en) * | 2008-06-16 | 2009-12-17 | Suh Sang-Bum | Apparatus and method for adaptation of input/output interface in virtualization environment |
US20100185843A1 (en) * | 2009-01-20 | 2010-07-22 | Microsoft Corporation | Hardware encrypting storage device with physically separable key storage device |
US20100318810A1 (en) * | 2009-06-10 | 2010-12-16 | Microsoft Corporation | Instruction cards for storage devices |
US9330282B2 (en) | 2009-06-10 | 2016-05-03 | Microsoft Technology Licensing, Llc | Instruction cards for storage devices |
US20100325736A1 (en) * | 2009-06-17 | 2010-12-23 | Microsoft Corporation | Remote access control of storage devices |
US9111103B2 (en) | 2009-06-17 | 2015-08-18 | Microsoft Technology Licensing, Llc | Remote access control of storage devices |
US8321956B2 (en) | 2009-06-17 | 2012-11-27 | Microsoft Corporation | Remote access control of storage devices |
US10437608B2 (en) | 2009-08-24 | 2019-10-08 | Wagan Sarukhanov | Microminiature personal computer and method of using thereof |
US20110047599A1 (en) * | 2009-08-24 | 2011-02-24 | Wagan Sarukhanov | Microminiature personal computer and method of using thereof |
US20140156885A1 (en) * | 2011-08-26 | 2014-06-05 | Xin Lian | External Device Extension Method and External Device |
US9311017B2 (en) * | 2011-08-26 | 2016-04-12 | Xin Lian | External device extension method for enabling an external device to be operated by a host without installing a driver |
US9619170B2 (en) | 2013-03-18 | 2017-04-11 | Kabushiki Kaisha Toshiba | Information processing system having a data migration log |
US9811277B2 (en) | 2013-03-18 | 2017-11-07 | Toshiba Memory Corporation | Information processing system |
US10089027B2 (en) | 2013-03-18 | 2018-10-02 | Toshiba Memory Corporation | Information processing system |
WO2014147865A1 (en) | 2013-03-18 | 2014-09-25 | Kabushiki Kaisha Toshiba | Information processing system, control program, and information processing device |
Also Published As
Publication number | Publication date |
---|---|
US6529992B1 (en) | 2003-03-04 |
EP1072976A2 (en) | 2001-01-31 |
JP2001075813A (en) | 2001-03-23 |
US20040083473A1 (en) | 2004-04-29 |
EP1072976A3 (en) | 2004-04-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6529992B1 (en) | Self-contained application disk for automatically launching application software or starting devices and peripherals | |
US20040172427A1 (en) | Self-contained application disk for automatically launching application software or starting devices and peripherals | |
US6728711B2 (en) | Automatic backup/recovery process | |
US7849267B2 (en) | Network-extended storage | |
US20080126446A1 (en) | Systems and methods for backing up user settings | |
US6260043B1 (en) | Automatic file format converter | |
US7194510B2 (en) | Maintaining a sliding view of server-based data on a handheld personal computer | |
US6131192A (en) | Software installation | |
US7606946B2 (en) | Removable device and program startup method | |
CN100399310C (en) | Information processing apparatus, information processing method, program and recording medium used therewith | |
JP4578119B2 (en) | Information processing apparatus and security ensuring method in information processing apparatus | |
US20040158730A1 (en) | Running anti-virus software on a network attached storage device | |
BRPI0305401B1 (en) | method and system in a computer-readable computing environment | |
US6408326B1 (en) | Method and system for applying a policy to binary data | |
US6714951B2 (en) | Continuous journaling of objects within a hierarchical directory tree | |
US7013392B1 (en) | File processing unit | |
JP5475199B2 (en) | File processing apparatus for executing preprocessed file and recording medium for performing the method by computer | |
US20050044330A1 (en) | System, apparatus and method for controlling a storage device | |
WO2000060453A2 (en) | Method and system for managing data in computer memory | |
WO2024031864A1 (en) | Automatic restoration method and system for vxworks system startup failure, storage medium, and device | |
JP4331440B2 (en) | Information management server, information processing apparatus, information management system, control method therefor, and program | |
JP6949338B2 (en) | Electronic data management equipment, electronic data management system, programs and recording media for that purpose | |
JP2002528790A (en) | Method and apparatus for capturing image file changes | |
JP2021174432A (en) | Electronic data management method, electronic data management device, and program and storage medium for the same | |
JPH103380A (en) | Computer system and file managing system for the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: IOMEGA CORPORATION, UTAH Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:THOMAS, TRENT M.;LOW, CHRISTOPHER R.;MCBRIDE, STEPHEN LARRY;AND OTHERS;REEL/FRAME:019290/0644;SIGNING DATES FROM 19990629 TO 19990721 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: EMC CORPORATION,MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IOMEGA CORPORATION;REEL/FRAME:024001/0708 Effective date: 20100211 |