TWI497414B - File executing method and system - Google Patents

Description

File execution method and system

The present invention relates to a file execution method and system, and more particularly to a file execution method and system for executing a computer executable code set stored in a hidden storage area of a storage device.

Digital cameras, mobile phones and MP3s have grown very rapidly in recent years, and the demand for storage media has increased rapidly. Because Flash Memory has the characteristics of non-volatile data, power saving, small size and no mechanical structure, it is most suitable as a portable storage device. In addition, with the development of plug-and-play connection interfaces (for example, Universal Serial Bus (USB)), portable storage devices have been widely used for storage of digital content.

In order to be able to make the portable storage devices sold in the market more competitive, the storage device is often stored in the portable storage device sold for the purchase of the portable storage device. Use. For example, a manufacturer develops a disk management program for a portable storage device and pre-stores it in a portable storage device so that a user can use the disk management program to manage the storage state of the portable storage device.

At present, in order to enable the user's computer host to execute an application provided by such a manufacturer, the application is pre-stored in a partition (or storage area) of the portable storage device that can normally store data. Eli computer host access. Since the application can be accessed by the host computer by means of general access to the file, the application can be easily copied and distributed, so that the intellectual property of the application developer cannot be effectively protected. Although the manufacturer of the portable storage device has configured a hidden storage area (ie, a storage area that the host computer cannot access) in the portable storage device to store the data to be kept secret, such an application must be hosted by the computer. The operating system executive can operate, so storing the application in a hidden storage area can avoid copying and distributing, but it also prevents users from using the application. Therefore, there is a need to develop a method for directly executing a computer execution code group stored in a hidden storage area.

The present invention provides a file execution method capable of directly executing a computer execution code group stored in a hidden storage area of a storage device.

The present invention provides a file execution system that is capable of directly executing a computer executable code group stored in a hidden storage area of a storage device.

An exemplary embodiment of the present invention provides a file execution method for executing a computer executable file stored in a storage device in an operating system of a host computer, wherein the storage device includes a general storage area and a hidden storage area. This computer execution code group is stored in a hidden storage area. The file execution method according to this exemplary embodiment includes connecting a storage device to a computer host, wherein the computer host has a main memory. The file execution method also includes providing a loader to manage the computer execution code group stored in the hidden storage area. The file execution method further includes running a loader in the main memory; requesting the operating system to allocate (Allocate) the first address segment for running the loader in the host memory; Loading the computer execution code group into the first address field in the hidden storage area; the loader converts the loaded computer execution code group into executable content executable by the operating system and converts the executable executable At least a portion of the content is stored in the first address section; and a derivative execution procedure is established by the loader to execute the converted executable content.

In an embodiment of the present invention, the step of establishing a derivative executable program by the loader to execute the converted executable content includes: requesting, by the loader, the operating system to establish a load for rerunning in the main memory. Derivative executor and requesting the operating system to allocate a second address segment for the derived executor in the main memory; suspend execution of the derived executor by the loader; write the above executable content by the loader Entering into the second address section; and continuing execution of the derived executable by the loader.

In an embodiment of the present invention, the file execution method further includes: determining, by the loader, whether the size of the second address segment is smaller than a size of the executable content, wherein when the size of the second address segment is smaller than When the size of the content is executed, the loader requests the operating system to allocate a third address segment in the main memory so that the size of the second address segment and the third address segment are larger than the executable content. size.

In an embodiment of the present invention, the file execution method further includes configuring an automatic execution file in the storage device and automatically executing the automatic execution file by the operating system, wherein the automatic execution file runs the loader in the main memory. .

In an embodiment of the invention, the file execution method further includes configuring the loader in a general storage area of the storage device.

In an embodiment of the present invention, the file execution method further includes configuring a special storage area in the storage device and configuring the automatic execution file and the loader in a special storage area of the storage device, wherein the special storage area Compatible with the ISO 9660 standard.

In an embodiment of the present invention, the file execution method further includes configuring the loader in a computer host.

In an embodiment of the invention, the file execution method further includes decrypting the computer-executed code group.

In an embodiment of the present invention, the file execution method further includes initializing a hidden storage area by a loader.

In an embodiment of the invention, the executable content is compatible with a portable executable file format.

An exemplary embodiment of the present invention provides a file execution system for executing a computer execution code group stored in a storage device, wherein the storage device includes a general storage area and a hidden storage area, and the computer execution code group is stored in the hidden storage area. A file execution system according to an exemplary embodiment of the present invention includes a computer host and a loader. The host computer includes the operating system and main memory. The loader is coupled or removably coupled to the host computer and the storage device and has an application execution unit, wherein the application execution unit is configured to execute a computer execution code group stored in the hidden storage area. The operating system runs the loader in the main memory and allocates a first address section for running the loader in the host memory. The application execution unit loads the computer execution code group from the hidden storage area into the first address area, and converts the loaded computer execution code group into executable content executable by the operating system, and converts the converted code to The execution content is stored in the first address section and a derivative executable is created to execute the executable content.

In an embodiment of the present invention, the application execution unit requests the operating system to establish a derivative executable program in the main memory for re-running the loader and requests the operating system to allocate the primary memory for the derivative. Execute the second address section of the program. In addition, the application execution unit suspends execution of the derived executor, writes the executable content into the second address section, and continues to execute the derived executor.

In an embodiment of the present invention, the application execution unit determines whether the size of the second address segment is smaller than the size of the executable content, wherein when the size of the second address segment is smaller than the size of the executable content, The application execution unit requests the operating system to allocate the third address segment in the main memory such that the size of the second address segment and the third address segment is greater than the size of the executable content.

In an embodiment of the present invention, the file execution system further includes an automatic execution file configured in the storage device, wherein when the storage device is coupled to the computer host, the operating system automatically executes the automatic execution and automatically executes the file. The above loader will be run in the main memory.

In one embodiment of the invention, the loader described above is disposed in a general storage area of the storage device.

In an embodiment of the invention, the storage device further includes a special storage area, and the automatic execution and loader configuration described above is stored in the special storage area, wherein the special storage area is compatible with the ISO 9660 standard.

An exemplary embodiment of the present invention provides a file execution method for executing a computer execution code group stored in a storage device in an operating system of a computer host, wherein the storage device includes a general storage area and a hidden storage area, and the computer performs code group storage. In the hidden storage area. This file execution method includes providing a loader to manage computer execution code groups stored in hidden storage areas. The file execution method also includes using the loader to load the computer execution code group directly from the hidden storage area into the host computer, and converting the loaded computer execution code group into executable content executable by the operating system. This file execution method further includes copying this executable content and executing this executable content.

The exemplary embodiment of the present invention provides a programmable storage device. The programmable storage device records a code that can be executed by a computer host. After the computer host loads the code and executes the file execution method, the file execution method can be implemented.

Based on the above, the exemplary embodiment of the present invention can directly execute a computer execution code group stored in a hidden storage area of the storage device, and the user cannot easily copy and distribute the computer execution code group stored in the hidden storage area, thereby can.

The above described features and advantages of the present invention will be more apparent from the following description.

1 is a schematic block diagram of a file execution system according to a first exemplary embodiment of the present invention.

Referring to FIG. 1, the file execution system 100 is capable of executing a computer executable code group 160 stored in a hidden storage area 152 of the storage device 150. Specifically, the storage device 150 includes a hidden storage area 152 and a general storage area 154, wherein the hidden storage area 152 is a storage area that cannot be accessed by the operating system of the computer (ie, the operating system of the computer cannot directly be in the hidden storage area according to a general procedure. The medium is read and written, and the general storage area 154 is a storage area accessible to the operating system of the computer. In the present exemplary embodiment, the storage device 150 is a portable storage device (for example, a flash drive, a mobile hard disk, etc.) that uses a flash memory as a storage medium. For example, the storage device 150 includes a controller 156 and a flash memory chip 158. The controller 156 is used to control the overall operation of the storage device 150. The flash memory chip 158 includes a hidden storage area for storing data and computer applications. 152 and general storage area 154. However, it must be understood that the present invention is not limited thereto, and the storage device 150 may be a magnetic tape, a floppy disk, an optical data storage device, or other storage device. In addition, it is worth mentioning that the controller 156 can encrypt the data or application and store it in the hidden storage area 152, thereby providing further protection of the data or the application. In addition, the computer execution code group 160 may not display related information in the File Allocation Table (FAT) of the storage device 150, that is, the operating system 118a cannot recognize the computer execution code group 160 as a file.

The file execution system 100 includes a computer host 110 and a loader 120.

The host computer 110 is a platform for executing a computer executable code group 160. In the present exemplary embodiment, the computer main unit 110 is a desktop personal computer. It must be understood that the present invention is not limited thereto, and is embodied in another example of the present invention. In the example, the host computer 110 can also be a notebook computer, a server, or any other computer host capable of executing a computer program.

The mainframe 110 includes a central processing unit 112, a main memory 114, an input and output unit 116, and a storage unit 118 in which the operating system 118a is stored.

The central processing unit 112 is used to interpret computer instructions and process data in the computer software.

The main memory 114 is coupled to the central processing unit 112 and is used to load a wide variety of programs and materials for direct execution and operation by the central processing unit 112. Specifically, the main memory 114 has characteristics such as read/write speed and fast read/write speed, and thus the main memory 114 is a temporary data storage medium used as the operating system 118 or other programs being executed. In the present exemplary embodiment, the main memory 114 is a Dynamic Random Access Memory (DRAM). In addition, it should be understood that, in another exemplary embodiment of the present invention, the operating system may also use the virtual memory simulated by the storage space of the storage device as a temporary data storage medium for executing the application, in this example, The main memory further includes such virtual memory.

The input and output unit 116 is coupled to the central processing unit 112 for providing an interface for the user to input data or instructions to or output data from the host computer 110. In the present exemplary embodiment, the input/output unit 116 includes a keyboard, a mouse, and a display (not shown).

The storage unit 118 is coupled to the central processing unit 112 for use as a primary storage medium for the computer host 110. In the present exemplary embodiment, the storage unit 118 is a hard disk, however, it must be understood that the present invention is not limited thereto. The storage unit 118 stores a program for operating the computer hardware and computer software resources, and is also the core and foundation of the computer host 110. Specifically, the operating system 118a is used to manage and configure the main memory 114, determine the priority of supply and demand of system resources (eg, central processing unit 112, main memory 114, input and output unit 116), and control input and output devices 116. Management of file systems and other operations. In the present exemplary embodiment, the operating system 118a is a Windows (Windows) operating system of Microsoft Corporation. However, it must be understood that the present invention is not limited thereto, and the present invention is also applicable to other operating systems.

The loader 120 can be coupled to or can be stored in the computer host 110 and the storage device 150, and has a plurality of logic gates or control commands implemented in a hard type or a tough/soft type to manage hidden storage stored in the storage device 150. The application in area 152 (e.g., computer execution program 160). In more detail, in the present exemplary embodiment, the loader 120 is provided by the manufacturer of the storage device 150 and is capable of accessing data or applications stored in the hidden storage area 152 according to the specifications of the hidden storage area 152. Program.

In the present exemplary embodiment, the control instructions of the loader 120 are implemented in a software version and are stored in advance in the general storage area 154 of the storage device 150. That is, when the user operates the computer host 110 to browse the storage device 150 connected to the computer host 110, the user can click on the loader 120 stored in the general storage area 154 to make the control command of the loader 120 The operating system 180 is operated (Run), thereby accessing the hidden storage area 152. In detail, after the control command of the loader 120 is run in the operating system 180, a predetermined command is sent to the storage device 150, and the storage device 150 will go to the hidden storage area 152 when accepting the command. Read the predetermined data. In addition, in another exemplary embodiment of the present invention, the loader 120 implemented in a software type may also be stored in a hard disk (not shown) of the optical disk or the host computer 110, thereby being selected by the user. The loader 120 can operate in the operating system 180.

It should be noted that in another exemplary embodiment of the present invention, the loader 120 can also be implemented in the storage device 150 or the host computer 110 in a hardware format.

2 is a schematic block diagram of a loader according to a first exemplary embodiment of the present invention.

Referring to FIG. 2, the loader 120 includes a main control unit 122, an initialization unit 124, an application adding unit 126, an application editing unit 128, an application deleting unit 130, and an application executing unit 132.

The main control unit 122 is used to control the overall operation of the loader 120.

The initialization unit 124 is coupled or linked to the main control unit 122 and is used to initialize the hidden storage area 152 of the storage device 150. Specifically, when the initialization unit 124 operates, the initialization unit 124 confirms the information such as the address, size, and the like of the hidden storage area 152, and erases and formats the hidden storage area 152.

The application adding unit 126 is coupled or linked to the main control unit 122 and is used to write an application (for example, the computer execution code group 160) that the user wants to store into the hidden storage area 152.

The application editing unit 128 is coupled or linked to the main control unit 122 and is used to edit an application list to browse applications stored in the hidden storage area 152 of the storage device 150.

The application deletion unit 130 is coupled or coupled to the main control unit 122 and is used to delete an application stored in the hidden storage area 152 of the storage device 150. For example, the application deletion unit 130 may delete the computer execution code group 160 from the hidden storage area 152.

The application execution unit 132 is coupled or coupled to the main control unit 122 for executing an application stored in the hidden storage area 152 of the storage device 150. For example, the application execution unit 132 loads the computer execution code group 160 into the main memory 114 and executes the computer execution code group 160 on the operating system 118a of the computer host 110.

FIG. 3 is a schematic diagram showing the operation of the main memory when the operation loader is executed to execute the computer execution code group in the hidden storage area according to the first exemplary embodiment of the present invention.

Referring to FIG. 3, when the user clicks on the loader 120 by operating the operating system 118a of the computer host 110 through the input and output unit 116, the operating system 118a specifies a one of the main memory 114 for executing the loader. Execution point 302 and allocating a first address section 310 (shown in (a) of FIG. 3) as a starting point for loading control instructions and temporary storage of loader 120 The data used when the feeder 120 is operating.

In addition, when the user executes the code execution group 160 stored in the hidden storage area 152 by the loaded loader 120, the application execution unit 132 executes the code group 160 of the computer stored in the hidden storage area 152. Loading into the first address field 310 (such as the computer execution code group 160' shown in FIG. 3(b)) and converting the loaded computer execution code group 160' into executable by the operating system 118a. Execution of content 162. At the same time, the application execution unit 132 stores the executable content 162 in the first address section 310 (as shown in (c) of FIG. 3). In the present exemplary embodiment, the executable content 162 of the corresponding computer execution code group 160 is a portable executable (PE) file format compatible with the Windows operating system.

In the present exemplary embodiment, the application execution unit 132 is further configured to request, from the operating system 118a, an execution point 304 for re-running the derivative executable program 350 of the loader 120 and a second status area required to derive the execution program 350. Section 320, wherein, in the present exemplary embodiment, the derivative execution procedure 350 uses the fork process to run the loader 120 again, but may also use multi-threads. ) and other multiplex implementation methods to implement. In particular, the operating system 118a, at the request of the application execution unit 132, specifies in the main memory 114 the starting point (ie, execution point 304) at which the derivative executable program 350 is executed and the allocation for the derivative execution program 350. The second address section 320 (shown in (d) of FIG. 3).

In particular, the application execution unit 132 in accordance with the present exemplary embodiment will use the derived executable 350 to execute the executable content 162 of the corresponding computer executable code set 160.

Specifically, when the application execution unit 132 establishes the derivative execution program 350, the application execution unit 132 suspends execution of the derivative execution program 350, and overwrites the executable content 162 of the corresponding computer execution code group 160 from the execution point 304 to The second address section 320 (ie, the executable content 162') may continue to execute the derived executable 350. At this time, since the code in the derivative executable 350 has been replaced by the executable content 162' of the corresponding computer execution code group 160, the computer execution code group 160 can be successfully executed by the computer host 110. Specifically, when the application execution unit 132 converts the computer execution code group 160 into the executable content 162, it may add information about the computer execution code group 160 (eg, the code size) to the header of the executable content 162. Thus, when the operating system 118a executes the derived executable 350 written by the executable content 162' from the execution point 304, it can correctly execute the corresponding code.

It is worth mentioning that since the derived executable 350 is used to execute the loader 120 again, the size of the second address section 320 is the same as the first address section 310. In another exemplary embodiment of the present invention, the application execution unit 132 is further configured to determine whether the size of the second address section 320 is sufficient to accommodate the executable content 162 ′, wherein the capacity of the second address section 320 is less than When the size of the content 162' is executed, the application execution unit 132 requests the third address segment (not shown) in the main memory 114 from the operating system 118a to ensure that there is sufficient memory address in the main memory 114. To write executable content 162'.

FIG. 4 is a flowchart of a file execution method according to a first exemplary embodiment of the present invention.

Referring to FIG. 4, first, the storage device 150 is connected to the host computer 110 in step S401, and the first address segment 310 and the run loader 120 are allocated in the main memory 114 in step S403, where the loading is performed. The operation of the device 120 has been described in detail above, and the description will not be repeated here.

Thereafter, the computer executable code group 160 is loaded from the hidden storage area 152 of the storage device 150 to the first address portion 320 using the loader 120 in step S405 to become the computer executable code group 160'. The loaded computer executable code group 160' is then converted to executable content 162 using the loader 120 in step S407 and the executable content 162 is stored in the first address field 320.

Then, the executable content is executed using the loader 120 in step S409. Specifically, in step S409-1, the operating system 118a is requested to establish a derivative execution program 350 for re-running the loader 120 in the main memory 114 and request the operating system 118a to be allocated for execution in the main memory 114. The second address section 320 of the program 350. Then, the execution execution program 350 is suspended using the loader 120 in step S409-3, and the executable content 162 is written into the second address portion 320 into the executable content 162' in step S409-5. Finally, the derivative execution program 350 continues to be executed in step S409-7.

As described above, in another exemplary embodiment of the present invention, step S409 may further include determining whether the size of the second address section 320 is smaller than the size of the executable content 162', and if the second address section 320 is The requesting operating system 118a is more likely to allocate a third address segment in the main memory 114 when the size is less than the size of the executable content 162'.

FIG. 5 is a schematic block diagram of a file execution system according to a second exemplary embodiment of the present invention.

Referring to FIG. 5, the file execution system of the second exemplary embodiment is different from the file execution system of the first exemplary embodiment in that the file execution system of the second exemplary embodiment configures the automatic execution file 502 to automatically perform loading. 120. Specifically, when the storage device 150 is coupled to the host computer 110, the automatic execution file 502 is automatically executed and the automatic execution file 502 runs the loader 120 in the main memory 114. For example, in the present exemplary embodiment, the storage device 150 further includes a special storage area 550 compatible with the ISO 9660 standard, and the special storage area 550 stores the automatic execution file 502 and loading implemented in the form of autorun.inf. The operating system 118a automatically executes the automatic execution of the file 502 and thereby operates the loader 120 when the storage device 150 is coupled to the host computer 110. In particular, the user can pre-set the application to be executed (for example, the computer execution code group 160) in the loader 120, and when the loader 120 is running, the preset application can be automatically executed.

FIG. 6 is a flowchart of a file execution method according to a second exemplary embodiment of the present invention.

Referring to FIG. 6, first, the storage device 150 is connected to the computer host 110 in step S601, and the automatic execution file 502 is automatically executed by the work system 118a in step S603. Thereafter, the loader 120 is automatically executed in step S605 and the preset application (for example, the computer execution code group 160) in the hidden storage area 152 is automatically executed in step S607, in which the loader 120 is executed and executed. The steps of storing the application in the hidden storage area 152 are the same as steps S403, S405, S407, S409-1, S409-3, S409-5, and S409-7 of FIG. 4, and the description will not be repeated here.

In another exemplary embodiment of the present invention, the loader 120 will automatically close (ie, end the operation of the loader 120) after automatically executing the preset application.

The file execution method of the exemplary embodiment of the present invention can be implemented as a computer readable code on a computer readable recording medium (or a programmable storage device). The computer readable recording medium can be any data storage device that can thereafter be read by a computer system. Examples of computer readable recording media include read-only memory (ROM), random-access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and carrier wave. (for example, data transmission over the Internet).

In summary, the present invention reads a computer execution code group in a hidden storage area of a storage device by a loader, converts a computer execution code group into executable content in a main memory of the computer host, and replaces The derivative execution program executes the converted executable content, thereby successfully executing the computer execution code group stored in the hidden storage area that the host computer cannot access on the host computer. Moreover, since the executable content of the computer execution code group and the corresponding computer execution code group is temporarily stored in the main memory in a non-file type, the user cannot easily copy and distribute the computer execution code stored in the hidden storage area. group.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the invention, and any one of ordinary skill in the art can make some modifications and refinements without departing from the spirit and scope of the invention. The scope of the invention is defined by the scope of the appended claims.

100. . . File execution system

110. . . Computer host

112. . . Central processing unit

114. . . Main memory

116. . . Input and output unit

118. . . Storage unit

118a. . . working system

120. . . Loader

122. . . Master unit

124. . . Initialization unit

126. . . Application addition unit

128. . . Application editing unit

130. . . Application removal unit

132. . . Application execution unit

150. . . Storage device

152. . . Hidden storage area

154. . . General storage area

156. . . Controller

158. . . Flash memory chip

160, 160’. . . Computer execution code group

162, 162’. . . Corresponding content of the computer execution code group

302, 304. . . Execution point

310. . . First address section

320. . . Second status section

350. . . Derivative executive

502. . . Automatic execution

550. . . Special storage area

S403, S405, S407, S409-1, S409-3, S409-5, S409-7. . . File execution steps

S601, S603, S605, S607. . . File execution steps

1 is a schematic block diagram of a file execution system according to a first exemplary embodiment of the present invention.

2 is a schematic block diagram of a loader according to a first exemplary embodiment of the present invention.

FIG. 3 is a schematic diagram showing the operation of the main memory when the operation loader is executed to execute the computer execution code group in the hidden storage area according to the first exemplary embodiment of the present invention.

FIG. 4 is a flowchart of a file execution method according to a first exemplary embodiment of the present invention.

FIG. 5 is a schematic block diagram of a file execution system according to a second exemplary embodiment of the present invention.

FIG. 6 is a flowchart of a file execution method according to a second exemplary embodiment of the present invention.

S403, S405, S407, S409-1, S409-3, S409-5, S409-7. . . File execution steps

Claims (20)

A file execution method for executing a computer execution code group stored in a storage device in an operating system of a computer host, wherein the storage device includes a general storage area and a hidden storage area and the computer executes the code group Stored in the hidden storage area, the file execution method includes: connecting the storage device to the computer host, wherein the computer host has a main memory; and providing a loader for managing storage in the hidden storage area The computer executes a code group; runs the loader in the main memory; requests the operating system to allocate a first address segment for the loader in the host memory; from the loader Loading the computer execution code group into the first address field in the hidden storage area; converting the loaded computer execution code group into an executable content executable by the operating system by the loader And storing at least a portion of the executable content in the first address section; and the loader establishing a derivative executable to execute the executable content. The file execution method of claim 1, wherein the step of establishing the derivative executable program by the loader to execute the executable content comprises: requesting, by the loader, the operating system in the main memory Establishing the derived executable and requesting the operating system to allocate for use in the primary memory a second address section of the derived executor, wherein the derived executor is for running the loader again; suspending execution of the derived executor by the loader; the executable content is executed by the loader Writing to the second address section; and continuing execution of the derived executable by the loader. The file execution method of claim 2, further comprising: determining, by the loader, whether the size of the second address segment is smaller than a size of the executable content; and when the second address portion When the size of the executable content is smaller than the size of the executable content, the loader requests the operating system to allocate a third address segment in the main memory, so that the second address segment and the third bit The size of the address section is larger than the size of the executable content. The file execution method of claim 1, further comprising: configuring an automatic execution file in the storage device, wherein the step of operating the loader in the main memory comprises: coupling the storage device When the host computer is reached, the automatic execution file is automatically executed by the operating system and the loader is operated in the main memory by the automatic execution file. The file execution method of claim 1, further comprising: configuring the loader in the general storage area of the storage device. For example, the file execution method described in item 4 of the patent application scope is further included. Included: a special storage area is disposed in the storage device; and the automatic execution file and the loader are disposed in a special storage area of the storage device, wherein the special storage area is compatible with the ISO 9660 standard. The file execution method of claim 1, further comprising: configuring the loader in the computer host. For example, the file execution method described in claim 1 of the patent application further includes decrypting the computer to execute the code group. The file execution method of claim 1, further comprising initializing the hidden storage area by the loader. The file execution method of claim 1, wherein the executable content is compatible with a portable executable file format. A file execution system for executing a computer execution code group stored in a storage device, wherein the storage device includes a general storage area and a hidden storage area, and the computer execution code group is stored in the hidden storage area, The file execution system includes: a computer host including an operating system and a main memory; and a loader coupled or communicably coupled to the computer host and the storage device and having an application execution unit, Executing the computer execution code group stored in the hidden storage area, wherein the operating system runs the loader in the main memory and allocates a first address for the loader in the host memory Section, The application execution unit loads the computer execution code group into the first address segment from the hidden storage area, and converts the loaded computer execution code group into a executable file executable by the operating system. Executing the content and storing the executable content in the first address section, wherein the application execution unit suggests a derivative executable to execute the executable content. The file execution system of claim 11, wherein the application execution unit requests the operating system to establish the derivative executable program in the main memory and request the operating system to allocate the main execution memory for the Deriving a second address segment of the executor, wherein the derived executor is configured to run the loader again, wherein the application execution unit suspends execution of the derived executor, writing the executable content to the second In the address section, and continue to execute the derived executor. The file execution system of claim 12, wherein the application execution unit determines whether the size of the second address segment is smaller than a size of the executable content, and when the size of the second address segment When the size of the executable content is smaller, the application execution unit requests the operating system to allocate a third address segment in the main memory, so that the second address segment and the third address region The size of the segment is larger than the size of the executable content. The file execution system of claim 11, further comprising an automatic execution file disposed in the storage device, wherein the storage system is coupled to the computer host The automatic execution is automatically executed and the automatic execution runs the loader in the main memory. The file execution system of claim 11, wherein the loader is disposed in the general storage area of the storage device. The file execution system of claim 14, wherein the storage device further comprises a special storage area compatible with the ISO 9660 standard, wherein the automatic execution file and the loader are configured in the storage In a special storage area of the device. A file execution method for executing a computer execution code group stored in a storage device in an operating system of a computer host, wherein the storage device includes a hidden storage area and the computer execution code group is stored in the hidden storage In the area, the file execution method includes: providing a loader to manage the computer execution code group stored in the hidden storage area; the loader directly loads the computer execution code group from the hidden storage area Up to the host computer; converting the loaded computer executable code group into an executable content executable by the operating system; copying the executable content; and executing the executable content. A programmable storage device that records a code executable by a host computer. When the computer host loads the code and executes the file, the file execution method can be implemented. The file execution method includes: Loading a computer execution code group directly into the computer host from a hidden storage area of the computer host; converting the loaded computer execution code group into an executable content executable by an operating system; copying the Executable content; and executing the executable content. The program storage device of claim 18, wherein the file execution method further comprises: adding or deleting data stored in the hidden storage area. The program storage device of claim 18, wherein the file execution method further comprises: editing a computer executable code group list for managing the computer execution code group stored in the hidden storage area.