Application built-in type disk for automatically starting application software, storage device or peripheral equipment
Abstract
[Task] Provides a way to automatically run related applications when removable media is inserted into a computer device.
Solution.When the removable media is inserted, the task disk control file is read from the removable media and the related application is launched. The task disk control file contains all the configuration information needed to run related applications from its removable media. The removable disk is automatically ejected when the associated application is no longer used. When a completion event occurs, all datafiles are saved, temporary files are erased, and configuration information is deleted before the removable disk is ejected.

Term
Term ended
Projected expiry passed 26 July 2020, 6.2 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
26 claims: 3 independent, 23 dependent
- 1【特許請求の範囲】 【請求項1】 リムーバブル・メディアに含まれるタスク・ディスク制御ファイルに従って関連アプリケーションまたはデバイスを管理する方法であって、前記関連アプリケーションまたはデバイスがリムーバブル・メディア・ドライブを有するコンピュータでランするようになっており、 前記リムーバブル・メディア・ドライブへの前記リムーバブル・メディアの挿入を検出する工程、 前記リムーバブル・メディアに含まれる前記タスク・ディスク制御ファイルに従って前記コンピュータ・デバイスを構成する工程、 前記タスク・ディスク制御ファイルの情報に従って前記関連アプリケーションを起動する工程、 前記関連アプリケーション・ソフトの実行が完了するまで前記リムーバブル・メディア・ドライブおよび前記関連アプリケーションの事象を監視する工程、および、 前記リムーバブル・メディア・ドライブから前記リムーバブル・メディアを排出する工程、を含む方法。
- 2【請求項2】 請求項1記載の方法であって、前記タスク・ディスク制御ファイルに従う前記コンピュータ・デバイスの前記構成工程は、 前記リムーバブル・メディアの特有な識別子を決定する工程、 前記特有な識別子に従って前記タスク・ディスク制御ファイルにアクセスする工程、および前記コンピュータ・デバイスに対して実行可能ファイル、リンクされたライブラリ・ファイル、デバイス・ドライバ、パス情報、環境情報およびレジストリ・エントリの少なくとも1つを提供することによって前記コンピュータ・デバイスを構成する工程、を含む方法。
- 3【請求項3】 請求項2記載の方法であって、前記タスク・ディスク制御ファイルへのアクセス工程は、前記特有な識別子を暗号解読のキーとして使用して前記タスク・ディスク制御ファイルを復号化する工程を含む方法。
- 4【請求項4】 請求項1記載の方法であって、前記リムーバブル・メディア・ドライブ中の前記事象監視工程は、アプリケーション保存/クローズ・完了事象の監視工程を含む方法。
- 5【請求項5】 請求項4記載の方法であって、更に、前記タスク・ディスク制御ファイルに指定された予め決められた場所にすべてのデータ・ファイルを保存する工程、 一時ファイルを消去する工程、および前記タスク・ディスク制御ファイルに従って前記コンピュータ・デバイスの構成を元に戻す工程、を含む方法。
- 6【請求項6】 請求項5記載の方法であって、前記構成を元に戻す工程は、実行可能ファイル、リンクされたライブラリ・ファイル、デバイス・ドライバ、パス情報、環境情報およびレジストリ・エントリの少なくとも1つを前記コンピュータ・デバイスから削除する工程を含む方法。
- 7【請求項7】 請求項1記載の方法であって、前記監視工程は、前記リムーバブル・メディアの排出要求を監視する工程を含む方法。
- 8【請求項8】 請求項7記載の方法であって、更に、すべてのデータ・ファイルを前記リムーバブル・メディアへ保存する工程、 すべての一時ファイルを消去する工程、 前記タスク・ディスク制御ファイルに従って前記コンピュータ・デバイスの構成を元に戻す工程、および前記構成を元に戻す工程が完了した後で前記リムーバブル・メディアを排出する工程、を含む方法。
- 9【請求項9】 請求項8記載の方法であって、前記構成を元に戻す前記工程は、実行可能ファイル、リンクされたライブラリ・ファイル、デバイス・ドライバ、パス情報、環境情報およびレジストリ・エントリの少なくとも1つを削除する工程を含む方法。
- 10【請求項10】 請求項1記載の方法であって、前記関連アプリケーションは、前記リムーバブル・メディアまたはリムーバブルでない記憶メディア上に記憶されるようになっており、また前記タスク・ディスク制御ファイルの情報に従って前記関連アプリケーションを起動する前記工程は、前記リムーバブル・メディア、前記リムーバブルでない記憶メディアあるいは前記リムーバブル・メディアおよび前記リムーバブルでないメディアの両方から前記関連アプリケーションを起動する工程を含む方法。
- 11【請求項11】 コンピュータ読み取り可能なメディアを受け取るリムーバブル・メディア・ドライブを有するコンピュータ・デバイスによって実行される命令を含むコンピュータ読み取り可能なメディアであって、前記命令は、 前記コンピュータ読み取り可能なメディアに含まれるタスク・ディスク制御ファイルに従って前記コンピュータ・デバイスを構成すること、前記タスク・ディスク制御ファイルの情報に従って関連アプリケーションを起動すること、 前記関連アプリケーション・ソフトの実行が完了するまで前記リムーバブル・メディア・ドライブおよび前記関連アプリケーションの事象を監視すること、および、 前記コンピュータ読み取り可能なメディアを前記リムーバブル・メディア・ドライブから排出すること、を実行するものであるコンピュータ読み取り可能なメディア。
- 12【請求項12】 請求項11記載のコンピュータ読み取り可能なメディアであって、前記タスク・ディスク制御ファイルに従って前記コンピュータ・デバイスを構成する前記工程は、更に、 前記コンピュータ読み取り可能なメディアの特有な識別子を決定する工程、 前記特有な識別子に従って前記タスク・ディスク制御ファイルにアクセスする工程、および前記コンピュータ・デバイスに対して実行可能ファイル、リンクされたライブラリ・ファイル、デバイス・ドライバ、パス情報、環境情報およびレジストリ・エントリの少なくとも1つを提供することによって前記コンピュータ・デバイスを構成する工程、を含むコンピュータ読み取り可能なメディア。
- 13【請求項13】 請求項12記載のコンピュータ読み取り可能なメディアであって、前記タスク・ディスク制御ファイルへのアクセス工程は、前記特有な識別子を暗号解読のキーとして使用して前記タスク・ディスク制御ファイルを復号化する工程を含むコンピュータ読み取り可能なメディア。
- 14【請求項14】 請求項11記載のコンピュータ読み取り可能なメディアであって、前記リムーバブル・メディア・ドライブの事象を監視する前記工程は、アプリケーション保存/クローズ・完了事象を監視する工程を含むコンピュータ読み取り可能なメディア。
- 15【請求項15】 請求項14記載のコンピュータ読み取り可能なメディアであって、更に前記タスク・ディスク制御ファイルに指定された予め決められた場所にすべてのデータ・ファイルを保存する工程、 一時ファイルを消去する工程、および前記タスク・ディスク制御ファイルに従って前記コンピュータ・デバイスの構成を元に戻す工程、を含むコンピュータ読み取り可能なメディア。
- 16【請求項16】 請求項15記載のコンピュータ読み取り可能なメディアであって、前記構成を元に戻す工程は、実行可能ファイル、リンクされたライブラリ・ファイル、デバイス・ドライバ、パス情報、環境情報およびレジストリ・エントリの少なくとも1つを前記コンピュータ・デバイスから削除する工程を含むコンピュータ読み取り可能なメディア。
- 17【請求項17】 請求項11記載のコンピュータ読み取り可能なメディアであって、前記監視工程は、前記リムーバブル・メディアの排出要求を監視する工程を含むコンピュータ読み取り可能なメディア。
- 18【請求項18】 請求項17記載のコンピュータ読み取り可能なメディアであって、更に、 すべてのデータ・ファイルを前記コンピュータ読み取り可能なメディアへ保存する工程、 すべての一時ファイルを消去する工程、 前記タスク・ディスク制御ファイルに従って前記コンピュータ・デバイスの構成を元に戻す工程、および前記構成を元に戻す工程が完了した後で前記コンピュータ読み取り可能なメディアを排出する工程、を含むコンピュータ読み取り可能なメディア。
- 19【請求項19】 請求項18記載のコンピュータ読み取り可能なメディアであって、前記構成を元に戻す前記工程は、実行可能ファイル、リンクされたライブラリ・ファイル、デバイス・ドライバ、パス情報、環境情報およびレジストリ・エントリの少なくとも1つを削除する工程を含むコンピュータ読み取り可能なメディア。
- 20【請求項20】 請求項11記載のコンピュータ読み取り可能なメディアであって、前記関連アプリケーションは、前記コンピュータ読み取り可能なメディアまたはリムーバブルでない記憶メディア上に記憶されるようになっており、また前記タスク・ディスク制御ファイルの情報に従って前記関連アプリケーションを起動する前記工程は、前記コンピュータ読み取り可能なメディア、前記リムーバブルでない記憶メディアあるいは前記コンピュータ読み取り可能なメディアおよび前記リムーバブルでないメディアの両方から前記関連アプリケーションを起動する工程を含むコンピュータ読み取り可能なメディア。
- 21【請求項21】 タスク・リスト制御ファイルを有するコンピュータ読み取り可能なメディアであって、 予め決められた関連アプリケーションを起動する前にコンピュータを組み込まれたデバイスによって実行すべき命令を含む予備実行区分、 前記関連アプリケーションを起動するための命令を含むアプリケーション実行区分データ、および前記関連アプリケーションをクローズする時に実行すべき命令を含むクリーン・アップ区分、を含むコンピュータ読み取り可能なメディア。
- 22【請求項22】 請求項21記載のタスク・リスト制御ファイルであって、前記予備実行区分は、 レジストリ情報を構成する命令であって、オペレーティング・システムが、前記関連アプリケーションを起動するためのパス、環境変数およびコマンドの少なくとも1つを知るようにする命令、を含んでいるタスク・リスト制御ファイル。
- 23【請求項23】 請求項22記載のタスク・リスト制御ファイルであって、更に、前記関連アプリケーションを実行するために前記コンピュータを組み込まれたデバイスのハード・ドライブへ複写すべきファイルを指定する命令を含むタスク・リスト制御ファイル。
- 24【請求項24】 請求項21記載のタスク・リスト制御ファイルであって、前記アプリケーション実行区分は、前記関連アプリケーションをロードして使えるようにするためのオペレーティング・システムに対する命令を含んでいるタスク・リスト制御ファイル。
- 25【請求項25】 請求項21記載のタスク・リスト制御ファイルであって、前記クリーン・アップ区分は、前記予備実行区分によって加えられたすべてのレジストリ情報を削除するようになったタスク・リスト制御ファイル。
- 26【請求項26】 請求項25記載のタスク・リスト制御ファイルであって、前記クリーン・アップ区分は、前記予備実行区分によって指定されるように前記関連アプリケーションを実行するためにハード・ドライブに複写されたファイルを削除するようになったタスク・リスト制御ファイル。
Independent claims26
106 paragraphs in 1 section, as filed
Description: TECHNICAL FIELD [Detailed description of the invention]
【0001】
[Technical field to which the invention belongs]
The present invention relates to application software stored in a removable storage medium. Specifically, the present invention stores instructions for configuring environment variables of an operating system and instructions for loading predetermined application software on removable media, and the removable media drive stores the instructions. For systems where when a removable disk is inserted, its application and associated data files are automatically launched and made available.
【0002】
[Conventional technology]
At the dawn of the personal computer era, applications were simple and small, primarily due to storage and computing power constraints. For example, one of the most widely used application software in the early days, VisiCalc, was only 25kB in size and was usually run from a floppy (registered trademark) disk. Due to these restrictions, the data files created by VisiCalc were often stored on the same floppy disk as the program files. However, as the processing power and performance of personal computers have improved, additional functions have been added to application software to take advantage of the increasing processing power. These features have led to the tremendous size of application software. For example, Microsoft's Excel 97 now has about 5.4 MB of executable files. That's 21,600% of the early VisiCalc spreadsheet-style software. What's more, this number doesn't include the shared files that Microsoft's Excel 97 needs for proper execution. As a result of the increasing size and complexity of modern software, applications that run from a single piece of removable media are no longer developed and are at least partially installed on your computer's hard disk drive. You can't use it without it.
【0003】
Although recent application software has improved in terms of functionality and ease of use compared to its corresponding early versions, it poses problems for end users in terms of usability. The first problem is that managing data files is becoming more difficult. Computer hard drives with storage capacity over 20GB allow users to store almost anything they generate or download. Data files are extremely difficult to name, organize and distinguish, and use implicit or default names (such as today.doc, temp.xls and junk.txt) as a common convention for users. This is especially true when naming and saving files.
【0004】
Another problem is caused by a huge number of personal computers and peripheral devices. A typical user has one computer at home and one at work, as well as a portable computer (eg, a notebook) that they use every day. Thus, if a user wants to use a particular data file (s) on multiple computers, the user manually copies the data file (s) to a removable disk. , You must access the data files (s) from the removable disk or copy them to another computer. In addition, each computer used by a user must have special software installed on that computer to generate the data file (s) in order to access the data correctly. Inevitably, when a user moves data from one computer to another, it is inevitable that new files will be overwritten and lost by older versions. If a user creates multiple removable media that contains several versions of the data file (s), then examine or create the contents of each of the data files (s). File management tasks become even more complicated if you have to look up the dates to determine which version is the correct version. Peripheral devices and their related software have become enormous and difficult to use in many cases. In addition, many peripheral devices generate data files that need to be stored for use with other application software.
【0005】
File management is not without progress. Among them are file managers and applications that synchronize files between computers to reduce the effort required to maintain the latest version of data files on multiple computers. However, such programs are often restricted because they often cannot synchronize files between more than two computers. In addition, the files to be synchronized are often manually selected by the user. In this case, if the particular software were to generate and access multiple data files, the user would have to manually select all the data files to synchronize between the two computers. , Otherwise you will get an error. It is possible for a user to forget to select the specific data needed for synchronization and later discover that none of that data is available on another computer. Not only does this problem affect synchronization programs, but it also occurs when users manually copy data files to removable media in situations such as those mentioned above.
【0006】
Progress has also been made in making computers easier to use. For example, a graphical user interface (GUI) or an application that automatically launches a program stored on removable media. One such application automatically launches another application when the removable media is inserted into the computer, for example the Windows® "Autorun" that automatically runs the application stored on a CD-ROM. Includes features. When the CD-ROM is inserted into the drive, the operating system checks the root directory of the CD for a file named autorun.inf. Inside this autorun.inf file is a pointer to an executable file named "autorun.exe" that launches the software on that CD. This Autorun feature is commonly used to launch software setup / installation routines to install the software on the CD to your hard drive. However, this Autorun feature is limited. That's because it doesn't configure the computer to run the application software based on the instructions contained in the removable media, and the Autorun feature runs from removable media eject, removable media. It does not have the ability to manage events such as closing applications or storing data files on removable media.
【0007】
PROBLEM TO BE SOLVED: To solve an invention.
However, despite the advances mentioned above, computers remain difficult for many to use. For example, when a user turns on a computer, they are typically provided with a graphical user interface. At this point, it's up to the user to get to the application software they want to use and launch it. This task may seem relatively easy, but for many users it isn't. There is no standard rule as to where the special application software is located on the computer. Obviously, personal computers have failed to achieve the convenience of other home appliances. That is a major obstacle for many people to accept and use computers.
【0008】
In view of the above, there is a demand for methods and devices to facilitate the maintenance and use of user data, application software and computer devices. In addition, there is a demand for methods and devices that automatically perform those functions with little or no user input to avoid accidental data loss and facilitate the use of the application. Exists. Such demand is such that when inserted into a computer, application software is automatically launched or the device is automatically started from the computer's hard drive or removable media, while data. Resolved by removable media with built-in applications that now store files on removable media or other predetermined locations. The present invention provides such a solution.
【0009】
From the above viewpoint, the present invention is presented as realizing many features as described below through one or more aspects / embodiments of various aspects.
【0010】
[Means for solving problems]
According to the present invention, there is provided an application or service that resides on a computer and automatically recognizes the insertion of removable media without the need for user intervention. This removable media contains a task disk control file, which contains all the configuration information needed to run related applications from the removable media. Specifically, the task disk control file contains three configuration information categories: pre-execution, application execution, and cleanup. The pre-execution indicator configures registry information, which allows the operating system to know the path, environment variables, and command line for launching its associated application. Optionally, the pre-execution indicator can specify files that should be copied to the hard drive (eg, executable files, DLLs, device drivers, etc.) in order for the associated application to run correctly. The application execution indicator commands the operating system to load its associated application, which launches the associated application and makes it available to the user. The cleanup indicator removes all registry information added by the preparatory run indicator. Optionally, the cleanup indicator can also remove files that have been copied to your hard drive to run related applications.
【0011】
After reading the task disk control file and configuring the computer device, the associated application is launched and made available to the user. The removable disk is automatically ejected when the user terminates the use of the associated application. In addition to monitoring removable media inserts, events such as built-in application completion and media ejection requests are monitored. When a completion event occurs, all data files are saved, temporary files are erased, and configuration information is removed before the removable disk is ejected. When a discharge event occurs, the computer device is instructed to wait until the completion event is executed before the actual discharge of removable media.
【0012】
The system of the present invention greatly simplifies the operation and use of computer application software. It is how the user launches the application they want to use and the device and peripherals, except that such applications, devices and peripherals are automatically launched / started when the removable media is inserted. This is because it is not required to have knowledge about whether to start. Other features of the present invention will also be described below.
【0013】
The above overview is best understood with the accompanying drawings, along with the following detailed description of preferred embodiments. For convenience of description of the present invention, the drawings show embodiments that are considered preferred at this time, but it is understood that the present invention is not limited to the particular methods and devices disclosed. Similar parts are labeled with the same reference numerals throughout all drawings.
【0014】
BEST MODE FOR CARRYING OUT THE INVENTION
The present invention provides a novel application on a removable disk used to maintain application software, data and devices in a computer environment. According to the present invention, the user inserts a removable disk containing application software to be executed into a personal computer. Then, the application software or device is automatically started / started and becomes available. The present invention allows users to maintain everything they need in an advantageous way with removable disks.
【0015】
Here, an example of hardware for carrying out the present invention will be described with reference to FIGS. 1 and 2. As shown, a suitable platform is a personal computer (PC) 20, such as an Intel Pentium processor or a higher-level processor thereof, a long-term non-removable storage device (eg, an IDE or SCSI hard disk). , Removable media drives (eg CD-R, CD-RW, DVD, or other removable floppy or hard disk drives), random access memory (RAM), peripherals for communication (eg) A Windows 95/98 or Windows NT workstation-based personal computer with a network interface card and / or terminal adapter) and suitable application programs (eg, dial-up network software and web browsers). Can be included.
【0016】
As shown, the PC20 will be divided into internal and external components. Internal components include a basic input / output system (BIOS) 70 and a processor (CPU) 66 that control the overall functionality of the PC 20. Memory 64, hard disk drive 76, floppy disk drive 74, tape drive 78, CD-ROM drive 80, modem / terminal adapter / network interface card 82 and removable media drive 52a also on CPU 66 It is connected. The removable media drive 52a or 52b reads and / or writes to and from the storage media contained in the removable storage cartridge 28. The example PC20 in Figure 1 is configured to include two removable media drives 52a and 52b to emphasize that the removable media drive can be embedded both internally and externally.
【0017】
As a non-limiting example, the removable media 28 can include a ZIP disc manufactured by Iomega, Inc. of Roy, Utah, USA. Each Iomega ZIP disc contains a unique serial number written to a predetermined track during the formatting process, which will be used as an identifier. This serial number is preferably generated by a pseudo-random number generator, but is not limited thereto. Further, although the media 28 has been described as being a ZIP disk, it is not limited to the ZIP disk. The use of other types of removable media with unique serial numbers, such as CD-Rs, DVD-RAMs and other removable floppy or hard disks, is also within the scope of the invention.
【0018】
The modem / terminal adapter / network interface card 82 can include individual cards that perform functions related to communication, as known to those skilled in the art. A modem / terminal adapter / network interface card 82 is included in the PC20 to provide communication to the external network to which the PC20 is connected. Specifically, the modem / terminal adapter / network interface card 82 is used to access LAN14, ISP18 and network infrastructure 12.
【0019】
Communication between the internal device and the external device is performed via a controller provided inside the PC 20. The serial / parallel / USB port controller (which may be a separate controller) 58, the monitor controller (video card) 60 and the keyboard and mouse controller 62 are CPU66 and external removable, respectively. Provides an interface between the media drive 52b (or printer), monitor 54 and keyboard and mouse device 56. The hard disk and floppy disk controller 72 serve as interfaces between the CPU 66 and the hard disk 76, CD-ROM drive 80, floppy disk 74, and tape drive 78, respectively. As will be appreciated by those skilled in the art, the disk controller 72 may be a separate controller (eg, IDE or SCSI controller) for the floppy and hard disks.
【0020】
The removable media controller 68 acts as an interface between the removable media drive 52a and the CPU 66. For example, the removable disk controller 68 can include a peripheral device interface (SCSI) or integrated drive electronics (IDE) interface controller for small computers. The hard disk and floppy disk controller 72 serve as interfaces between the CPU 66 and the hard disk 76, CD-ROM drive 80, floppy disk 74, and tape drive 78, respectively. Alternatively, the removable media drive 52a can utilize the disk controller 72 as an interface with the CPU 66.
【0021】
Next, with reference to FIG. 2, a block diagram of Media Drive 52 is shown as an example having a SCSI interface with PC 20 (via controller 68). The media drive 52 preferably includes a ZIP drive manufactured by Iomega, Utah, USA, but the present invention is not limited to the removable media drive, but other media drives. It can be used as a media drive 52. The media drive 52 includes components for providing communication between the read / write channel for media (lower right in the drawing) and the PC 20 (upper left in the drawing). The media drive 52 includes an AIC chip 101 that performs SCSI 102, direct memory access (DMA) 103, and disk formatter 104 functions. This interface includes PHAEDRUS 105, which includes 8032 microprocessor 106, 1 kilobyte RAM 107 and an application specific integrated circuit (ASIC) 108. The ASIC108 performs various functions such as servo ordering, data division, EOC, ENDEC, AD conversion and DA conversion. Communication between the media drive 52 and the PC 20 is performed via data transfer between the input / output channels of the media drive 52 and the media controller 68 (eg, SCSI controller) of the PC 20.
【0022】
Next, referring to FIG. 3, a flow chart showing the process performed by the present invention is shown. As will be apparent to those skilled in the art, the features and aspects of the invention described below will be realized by any suitable combination of hardware, software and / or firmware. Preferably, the invention runs as a background task or service to recognize and read the task disk control file stored on the removable media when it is inserted into the computer. The task disk control file contains instructions for configuring the operating environment of the computer and launching application software contained on removable media and / or the hard disk of the computer. In addition, the task disk control file is used to start application software that controls the computer device and / or the device itself. When the predetermined application software or device is closed, the data file is saved according to the instructions of the control file, the computer environment is cleaned up, and the removable media is ejected. As described below, the systems of the present invention help greatly simplify the use and operation of computer application software, devices and peripherals. This is because the user is not required to have the necessary knowledge to launch the application he / she wants to use or to start the device or peripheral device. In other words, all the user needs to know is that the application, device or peripheral they want to use will be automatically launched / started when the removable media is inserted.
【0023】
Next, the details of the present invention will be described with reference to FIG. An application or system service running on PC20 monitors device commands to and from removable media drive 52 (step 200). This is preferably a background application or service that is loaded when the computer boots up. An example of such an application that monitors device commands to removable media drive 52 is the IOwatch commercially available from Iomega, Roy, Utah, USA. This application or service resides on computer 20 and automatically recognizes the insertion of removable media without any user intervention.
【0024】
In step 202, it is determined whether the monitored device command is in a "media exchange state". The media exchange state means that the removable media 28 has been inserted into the removable media drive 52, or that some operation has occurred with respect to the removable media 28 currently in the drive 52. If no media exchange condition occurs in step 202, the process returns to step 200 and is monitored for subsequent device commands.
【0025】
If a media exchange state is present in step 202, the invention initiates the process by identifying the type of event associated with that media exchange state. Events identified and routed through step 204 include, but are not limited to, device events and events resulting from a call from "related application" 201. The "related application" 201 is defined herein as an application software that cooperates with the present invention and has knowledge of the present invention by calling and accepting an event with and from the present invention. Related applications are located, for example, on hard disk 76, removable media 28, CD-ROM or network. In addition, related applications control peripherals and devices (eg, tape drives, scanners, etc.) that are in or attached to the computer. The media exchange state is provided to the present invention by known mechanisms such as messages between applications, program calls and event notifications.
【0026】
The first event identified is the media insertion event (step 206). This is the state that exists when the removable media 28 is inserted into the removable media drive 52. The media is detected inserted by a drive according to the method of US Pat. No. 5,854,719 by Ginosar et al., Which captures the entire media here by reference. In step 208, the system checks for the presence of a task disk control file (TDCF) on media 28.
【0027】
Figure 4 shows an example of the task disk control file 220. It contains configuration and execution information about related applications. For example, the TDCF220 contains executable file names, path information, and information such as required device drivers, dynamic link libraries, Windows registry data including identification of VxDs, etc. The contents of TDCF will be described in detail below.
【0028】
If a valid task disk control file (TDCF) 220 does not exist (step 210), the disk will be mounted for use, but the disk cannot be used to configure and launch applications or devices. The system returns to step 200 to monitor subsequent device commands. Alternatively, a message can be generated and displayed to the user indicating that the TDCF220 is not valid. If a valid TDCF220 is present, step 212 reads a media 28-specific identifier (eg, serial number). According to the features of the present invention, the TDCF220 uses the serial number of the media as an encryption key to encrypt it for increased confidentiality and prevent the application software from being copied or executed from another medium. You can also do it. Any encryption algorithm can be used for the purposes of the present invention.
【0029】
The media serial number is obtained by an application running on the PC20 that reads a unique identifier and authorization code. This is done by querying the media using an application programming interface (API) such as the Iomega Ready API, or by any other suitable method.
【0030】
When called, the Iomega Ready API causes the media drive to read a unique serial number from a predetermined track by using the SCSI 0x06 Non-Sense command. Specifically, by calling the disk status page (page 0x02) of the Non-Sense command, the media serial number is determined by reading the offset bytes 20-59 of the returned data structure. Here is an example source code for reading the Iomega ZIP drive and disk serial numbers:
【0031】
<img file="JP2001075813A_D0001.tif" />【0032】
<img file="JP2001075813A_D0002.tif" />【0033】
The unique serial number contains a sufficient number of bits (long) to ensure that no two media have the same identifier. For example, each Iomega ZIP disk has a unique 39-byte (312-bit) serial number. Other bit lengths may be used.
【0034】
Once the media serial number has been read, the task disk control file (TDCF) 220 is processed in step 214, where it is decrypted using the media serial number as the decryption key. It should be noted that TDCF220 encryption is not required for the operation of the present invention and is provided, for example, as a security measure to prevent illegal copying of copyrighted program files on removable media 28. That is. Therefore, step 210 is provided with a mechanism for determining whether the TDCF is encrypted, and if not, jumps to step 216.
【0035】
In step 216, the unencrypted TDCF220 is read and the system environment is configured according to the information contained in the TDCF220 before launching the associated application.
【0036】
Referring to FIG. 4, the TDCF220 contains a section of configuration information named Preliminary Run, Application Run and Cleanup. Preliminary execution partitions configure registry information to know the paths, environment variables, and commands for the operating system to launch related applications. Optionally, the pre-execution indicator can specify files that should be copied to the hard drive (eg, executable files, DLLs, device drivers, etc.) in order for the relevant application to run properly. The application execution indicator commands the operating system to load the associated application that launches the associated application for use by the user (see step 218 below). The cleanup indicator deletes all registry information added by the preparatory run indicator (see step 224 below). Optionally, the cleanup indicator can remove files that have been copied to the hard drive (eg, executable files, DLLs, device drivers, etc.) to run related applications.
【0037】
According to the present invention, the TDCF220 can configure the system environment to run applications in several modes. In the first mode of operation, related applications are stored on removable media 28 and run from there upon insertion. In this first mode of operation, everything needed to run the associated application is maintained and performed from removable media 28. Thus, no files are copied to the hard drive and no files are needed on the hard disk to run the associated application.
【0038】
In the second mode of operation, related applications cannot be run solely from removable media 28. In this mode, the specific file specified in the TDCF220 pre-execution indicator is copied to the hard disk. These files include, but are not limited to, the executable files, DLLs, device drivers, etc. mentioned above. The reason why copying files to hard disk is necessary is due to the limited speed and dimensions of removable media 28. In the second mode, when the related application is closed or the removable disk 28 is ejected, the previously copied files are deleted from the hard drive according to the cleanup classification, which causes the hard disk to be removed. , Returns to essentially the same state as before the removable media 28 was inserted.
【0039】
In the third mode, related applications cannot be run solely from removable media 28, as in the second mode. However, when the associated application closes or the disk is ejected in this mode, the files are not deleted from the hard drive. In the third mode, the previously copied file remains on the hard disk according to the cleanup classification, so the next time the removable media 28 is inserted, the specified file will be copied to the hard drive. No need. This third mode of operation speeds up the launch of related applications on the second and subsequent insertions of the removable disk 28 into the removable media drive 52.
【0040】
In the fourth mode, related applications are installed and stored on your computer's hard drive. A program that installs a related application preferably includes an option to "associate" it in accordance with the present invention. Optionally, a plug-in may be used to connect to the relevant application and "associate" it according to the present invention. The TDCF pre-execution indicator contains all the instructions needed to automatically launch the associated application from the hard drive and optionally load the datafiles when the associated application launches. These data files are preferably on removable media 28, but may be on hard disks. In this fourth mode, the TDCF220 contains a list of instructions for opening and closing related applications, because removable media automatically opens related applications when inserted into removable media drive 52. Acts as the "key" of.
【0041】
It should be noted that the TDCF220 in Figure 4 is shown here as just an example. In addition, the TDCF220 may include more or less instructions than those shown here to configure computer 20 or copy files to computer 20. In addition, more or less operating modes than those shown here are possible. According to the present invention, the TDCF220 properly configures and launches related applications when inserting removable media 28, removes configuration settings and saves data files in a sophisticated way, without the need for user intervention. Includes the instructions needed to do so.
【0042】
Returning to Figure 3, if the PC20 is configured according to the TDCF220, the relevant application will be launched and available in step 218, and the system will return to step 200 to monitor for new events.
【0043】
Returning to step 204 again, if the identified event is a save / close / complete event, processing continues to step 222. The save / close completion event occurs when the user terminates the use of the related application and selects an exit or clicks the close window box of the application window. In step 222, the associated application saves all data files, erases all temporary files, and indicates to the system that it is ready to exit. The datafiles will be saved according to the preset file path set by the TDCF220. In step 224, all configuration information is removed from the PC according to the TDCF220 cleanup classification. The cleanup indicator executes a specific cleanup function based on the mode of operation, as described above. Next, in step 226, the related application is terminated and the removable media 28 is ejected from the media drive 52 according to the present invention. The process follows step 200.
【0044】
Returning to step 240 again, if the detected event is a media emission request event, the process continues to step 228. The media discharge request event is a state that exists when the user activates the discharge function by pressing the discharge button provided on the drive 52 or by giving a software discharge command. In step 230, the relevant application is notified via a mechanism between the applications, such as a message, that a "media ejection request" has been detected. Then in step 232, the system performs steps 222-226 for completion, as described above. When the invention is notified of completion in step 234, the process returns to step 200 to monitor for new events.
【0045】
Thus, as mentioned above, the present invention provides a novel and advanced system for managing data files and applications that require the attention of the slightest user, if any. According to the present invention, users only need to know that the insertion of certain removable media launches a special application they want to use, or launches a special device or peripheral. The user's data files are stored on the same removable media or other designated location for easy retrieval, so the user's data is readily available when the application is launched. When the user completes the use of the application and exits, the removable media can be ejected from the computer and taken out for safe storage somewhere.
【0046】
It should be noted that the above example was chosen solely for convenience of explanation and was not chosen with the intent of limiting the invention to it. Although the present invention has described preferred embodiments, it should be understood that the text used herein is a text for explanation and not a limited text. Furthermore, although the present invention has been described herein with respect to special means, materials and embodiments, the present invention is not limited to those specifics disclosed herein. Instead, the invention extends to all functionally equivalent structures, methods and uses within the claims. Those skilled in the art will understand that, in the teaching of this specification, numerous modifications and modifications to it can be made in that manner without departing from the scope and spirit of the present invention.
[Simple explanation of drawings]
[Figure 1]
The block diagram of the part of the personal computer which carried out this invention.
[Figure 2]
Block diagram of suitable removable media drive components shown in Figure 1.
[Fig. 3]
A flow chart showing the entire process performed by the present invention.
[Fig. 4]
An example of a task disk control file according to the present invention.
[Explanation of symbols]
12 Network infrastructure 14 LAN 18 ISP 20 Personal computer (PC) 28 Removable Media 52 Removable media drive 54 monitor 56 Keyboard and mouse device 58 Serial / Parallel / USB Port Controller 60 monitor controller 62 mouse controller 64 memory 66 Processor (CPU) 68 media controller 70 Basic I / O System (BIOS) 74 floppy disk drive 76 hard disk drive 78 tape drive 80 CD-ROM drive 82 Modem / Terminal Adapter / Network Interface Card 101 AIC chip 102 SCSI 103 Direct Memory Access (DMA) 104 Disc formatter 105 PHAEDRUS 106 8032 Microcontroller 107 RAM 108 Application-specific integrated circuits 220 task disk control file
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10936394B2 | Cited by | United States of America | Applicant |
| JP2012027733A | Cited by | Japan | Examiner |
| US9201602B2 | Cited by | United States of America | Applicant |
| US11544131B2 | Cited by | United States of America | Applicant |
| US8631191B2 | Cited by | United States of America | Applicant |
| JP2012508424A | Cited by | Japan | Examiner |
| US8667216B2 | Cited by | United States of America | Applicant |
| US8683117B2 | Cited by | United States of America | Applicant |
| US8756367B2 | Cited by | United States of America | Applicant |
| JP2005122451A | Cited by | Japan | Search report |
| US9785494B2 | Cited by | United States of America | Applicant |
| JP2007035136A | Cited by | Japan | Examiner |
| JP2010198722A | Cited by | Japan | Search report |
| US7387258B2 | Cited by | United States of America | Applicant |
| US11880267B2 | Cited by | United States of America | Applicant |
| JP2006520032A | Cited by | Japan | Examiner |
| US10338985B2 | Cited by | United States of America | Applicant |
7 members in 3 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 360337 | United States of America | – | |
| 36033799 | United States of America | A |
Members7
| Document | Office | Kind | |
|---|---|---|---|
| EP1072976A2 | European Patent Office (EPO) | A2 | |
| JP2001075813AThis record | Japan | A | |
| US6529992B1 | United States of America | B1 | |
| EP1072976A3 | European Patent Office (EPO) | A3 | |
| US2004083473A1 | United States of America | A1 | |
| US2004172427A1 | United States of America | A1 | |
| US2007214187A1 | United States of America | A1 |
1 legal event, as the office reported them to INPADOC
Events
| Event | Code | |
|---|---|---|
| Application deemed to be withdrawn because no request for examination was validly filedWithdrawnJAPANESE INTERMEDIATE CODE: A300A300 | A300 |
Numbers
- Publication
- 2001-75813
- Application
- 225696
Titles2
- Japanese
- アプリケーション・ソフト、記憶装置あるいは周辺機器を自動的に起動するためのアプリケーション内蔵型ディスク
- English
- Description: A disk with a built-in application for automatically starting application software, a storage device, or a peripheral device.
Classification
- CPC, 1
- G06F9/445
- IPC, 5
- G06F1 00
- G06F9 445
- G06F21 12
- G06F21 14
- G06F21 60