英語 での The archive file の使用例とその 日本語 への翻訳
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Programming
Save the archive file.
Unable to finalize the archive file.
The archive file has a size of %1.
Load K2HASH data from the archive file.
The archive file name is not valid.
Check the right side of the archive file.
Develop the archive file which You downloaded.
While using the system,users may accidentally tap on the delete option and end up losing the archive file.
Importing the archive file'%1'into the folder'%2' succeeded.
In Plesk, go to Files, click the httpdocs folder to open it, click Upload,select the archive file, and then click Open.
When outputting the archive file of K2HASH, specify the file path.
If K2HASH data exists before calling the k2h_load_archive function,the contents of the archive file are overwritten in the K2HASH data.
You may decompress the archive file and begin using the application straight away.
In Plesk Customer Panel, open the Files section, click the httpdocs folder to open it, click Upload,select the archive file, and click Open.
Returns the name of the archive file that was created, as string value. Parameters.
The archive file can simultaneously contain images of several disks and/or disk partitions.
System specification logged to a file System specification containing information about computer processor and amount of memory available is logged to a System-info. json file, which is used for diagnostic purposes and included in the archive file with logs.
The archive file format of bzip2(. bz2) is incompatible with that of its predecessor, bzip(. bz).
This task writes the client devices that were decommissioned to an archive file. The archived client devices are written to a file in the MobileFirst Server home\devices_archive directory. The name of the file contains the time stamp when the archive file is created. Default: 90 days.
If you have downloaded Mercalli, the archive file will first be decompressed and then the installation will start.
This task writes the client devices that were decommissioned to an archive file. The archived client devices are written to a file in the Mobile Foundation Server home\devices_archive directory. The name of the file contains the time stamp when the archive file is created. Default: 90 days.
Unzip the archive file(if necessary) and navigate to the project directory through the command line on your computer:.
You can import the archive file in Structure101 and save it as a project file. kwstruct101 is installed with the Klocwork Server.
The archive file no longer contains the web preview files or skins that were possible in previous versions of Mobile Foundation.
The archive file may be handled by F-Secure Corporation, our affiliated companies, relevant subcontractors, and our support partners, but only for the purposes set out in this policy.
The archive file uses gr_common. a generated by the build of the Web compiler, but when changing the library, it is recommended to use an IDE that allows project management such as e2studio.
The archive file contains the files for building an image(dependencies and mfpf-libs) and the files for building and deploying a MobileFirst Application Center on Kubernetes bmx-kubernetes.
The archive file contains the files for building an image(dependencies and mfpf-libs) and the files for building and deploying a MobileFirst Server and MobileFirst Analytics on Kubernetes bmx-kubenetes.
The archive file contains the files for building an file layout(dependencies and mfpf-libs),the files for building and deploying a MobileFirst Analytics Container(mfpf-analytics) and files for configuring a MobileFirst Server Cloud Foundry app(mfpf-server-libertyapp).