- File Storage Companion For Mac
- File Storage Companion
- File Storage Companion Mac
- File Storage App
- Portable File Box Legal Size
- File Storage For Mac
- 카테고리:Business
- 최근 업데이트: 2020-12-20
- 현재 버전: 3.5
- 파일 크기: 638.60 kB
- 개발자:Delite Studio S.r.l.
- 호환성: 필요 Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1 and Windows 10
Xbstorage is a command line tool, run from the XDK command prompt, for managing locally cached Connected Storage on the Xbox console. The xbstorage tool can be found in the Xbox XDK under the file path: /Program Files (x86)/Microsoft Durango XDK/bin/xbstorage.exe. Gamesaveutil is a command line tool for managing UWP locally cached Connected Storage on PC.
Germany was particularly effective in deporting and killing Jews during its occupation of the Netherlands during World War II. Of the 140,000 Jews in 1941, inclusive both of Dutch Jews and the refugees ensnared by the German invasion of 1940, about 38,000 survived at war's end in 1945. ADVANTUS Companion Letter/Legal Portable Plastic File Box, Includes Lid and Handles, 17 x 14 x 11 Inches, Black (TLF-2B) Available from these sellers. Files are transferred directly and instantly on your local network. No need to upload your files to the Internet and then download them on any device. File Transfer is compatible with File Storage. Trusted Mac download File Storage Companion 3.5. Virus-free and 100% clean download. Get File Storage Companion alternative downloads.
다운로드 링크
앱 다운로드 ⇩Windows PC에서 File Storage Companion를 다운로드하여 설치하고 즐기십시오.
사용 File Storage Companion 귀하의 Windows 컴퓨터에서 실제로 매우 쉽습니다하지만 당신 이이 과정을 처음 접한다면, 당신은 분명히 아래 나열된 단계에주의를 기울일 필요가있을 것입니다. 컴퓨터 용 데스크톱 응용 프로그램 에뮬레이터를 다운로드하여 설치해야하기 때문입니다. 다운로드 및 설치를 도와 드리겠습니다 File Storage Companion 아래의 간단한 4 단계로 컴퓨터에서:1 : Windows 용 Android 소프트웨어 에뮬레이터 다운로드
에뮬레이터의 중요성은 컴퓨터에서 안드로이드 환경을 흉내 내고 안드로이드 폰을 구입하지 않고도 안드로이드 앱을 설치하고 실행하는 것을 매우 쉽게 만들어주는 것입니다. 누가 당신이 두 세계를 즐길 수 없다고 말합니까? 우선 아래에있는 에뮬레이터 앱을 다운로드 할 수 있습니다.
A. Nox App . OR
B. Bluestacks App.
Bluestacks는 매우 대중적이므로 개인적으로 'B'옵션을 사용하는 것이 좋습니다. 문제가 발생하면 Google 또는 Naver.com에서 좋은 해결책을 찾을 수 있습니다.
2 : 이제 Windows PC에 소프트웨어 에뮬레이터 설치
Bluestacks.exe 또는 Nox.exe를 성공적으로 다운로드 한 경우 컴퓨터의 다운로드 폴더 또는 다운로드 한 파일을 일반적으로 저장하는 곳으로 이동하십시오.
찾으면 클릭하여 응용 프로그램을 설치하십시오. PC에서 설치 프로세스를 시작해야합니다.
다음을 클릭하여 EULA 라이센스 계약에 동의하십시오.
응용 프로그램을 설치하려면 화면 지시문을 따르십시오.
위 사항을 올바르게 수행하면 소프트웨어가 성공적으로 설치됩니다.
3 : Windows PC 용 File Storage Companion 사용 방법 - Windows 7/8 / 8.1 / 10
이제 설치 한 에뮬레이터 애플리케이션을 열고 검색 창을 찾으십시오. 지금 입력하십시오. - File Storage Companion 앱을 쉽게 볼 수 있습니다. 그것을 클릭하십시오. 응용 프로그램 창이 열리고 에뮬레이터 소프트웨어에 응용 프로그램이 표시됩니다. 설치 버튼을 누르면 응용 프로그램이 다운로드되기 시작합니다. 이제 우리는 모두 끝났습니다.
그런 다음 '모든 앱'아이콘이 표시됩니다.
클릭하면 설치된 모든 응용 프로그램이 포함 된 페이지로 이동합니다.
당신은 File Storage Companion 상. 그것을 클릭하고 응용 프로그램 사용을 시작하십시오.
보너스 : Android 및 iOS 용 다운로드
Android에서 다운로드개발자 설명
Exchange files and folders with your iPhones, iPads, iPod touches, and Androids over WiFi.It is quick and easy. No configuration required, no need to enter an address to connect. Devices are automatically discovered. Drag folders and files and they are transferred to your device in seconds. Without iTunes and without USB cable. It is not a cloud. Files are transferred directly on your local network. No need to upload your files to the Internet, then download them on any device. File Storage Companion requires Local Cloud*, File Storage**, or File Transfer*** to be installed on your device.With File Storage Companion you can share files only with smartphones and tables. If you want to receive files from computers, you need File Transfer**.File Storage Companion is optimized for your MacBook Pro with Retina display.Delite Studio develops high-quality native applications and delivers a great customer service. Do you enjoy using this app? Write a positive review. Do you need help? Let us know, we will do everything to help you.* For iPhone, iPad, and iPod touch. Available on the App Store: products.delitestudio.com/go/local-cloud-ios** For iPhone, iPad, and iPod touch. Available on the App Store: products.delitestudio.com/go/file-storage-ios*** For Mac, Windows, iPhone, iPad, iPod touch, and Android. Available on products.delitestudio.com/file-transfer/
Although Connected Storage is used to store your game data in the cloud, there is also a local storage component to the Connected Storage service.
Whether you are on a PC or Xbox console (Xbox One or later), there is a local cache of the Connected Storage data which contains the data synced to the cloud.
The appropriate tool to manage your locally cached Connected Storage data depends on the platform:
| Title Classification | Device | Local Storage Tool |
|---|---|---|
| XDK | Xbox Console | xbstorage |
| UWP | PC | gamesaveutil |
| UWP | Xbox Console | Partner Center |
Xbstorage is a command line tool, run from the XDK command prompt, for managing locally cached Connected Storage on the Xbox console. The xbstorage tool can be found in the Xbox XDK under the file path: /Program Files (x86)/Microsoft Durango XDK/bin/xbstorage.exe
Gamesaveutil is a command line tool for managing UWP locally cached Connected Storage on PC. The gamesaveutil tool comes packaged with the Windows 10 SDK for Fall Creators Update and later( build 10.0.16299.15 and later). Once you've installed the appropriate version of the Windows 10 SDK, gamesaveutil can be found under the folder: ProgramFiles(x86)/Windows Kits/10/bin/[SDK Version]/x64/gamesaveutil.exe.
Partner Center is an online portal that allows you to manage the locally cached Connected Storage UWP data on your Xbox console. To learn to use Partner Center, read Device Portal for Xbox.
Xbstorage
Xbstorage allows clearing locally cached data Connected Storage data from the hard drive, as well as importing and exporting of data for users or machines from Connected Storage spaces by using XML files.
When an operation is performed on local data using the xbstorage tool, the system will behave as if that operation had been performed by the app itself, so the act of reading the data from a Connected Storage space to a local file will cause synchronization with the cloud prior to copying.
Similarly, a copy of data from an XML file on the development PC to a Connected Storage container on the Xbox One (or later) dev kit will cause the console to start uploading that data to the cloud.
However, there are conditions in which this will not occur: if the dev kit cannot acquire the lock, or if there is a data conflict between the containers on the console and those in the cloud, the console will behave as if the user had decided not to resolve the conflict by picking one version of the container to keep, and the console will behave as if the user is playing offline until the next time the title is started.
The one exception to these commands is reset/force which clears the local storage of saved data for all SCIDs and users, but does not alter the data stored in the cloud.This is useful for putting a console into the state it would be in if a user was roaming to a console and downloading data from the cloud upon playing a title.
Xbstorage commands
Xbstorage has the following six commands developers can use with the XDK command prompt to manage local data on their Xbox Development Kit:
| Command | Description |
|---|---|
| reset | Performs a factory reset on Connected Storage. |
| import | Imports data from the specified XML file to a Connected Storage space. |
| export | Exports data from a Connected Storage space to the specified XML file. |
| delete | Deletes data from a Connected Storage space. |
| generate | Generates dummy data and saves to the specified XML file. |
| simulate | Simulates out of storage space conditions. |
xbstorage reset
xbstorage reset [/force]
Erases all local data in Connected Storage from the local console, restoring it to factory settings.Data that has been persisted to the cloud is not modified and will be downloaded again as necessary.
| Option | Description |
|---|---|
| /force | Confirms that Connected Storage should be reset. Running the reset command without specifying /force causes the following message to be displayed: As Connected Storage factory reset is a potentially destructive operation this command does not perform the reset unless the /force flag is present. |
xbstorage import
xbstorage import *file-name* [/scid:*SCID*] [/machine] [/msa:*account*] [/replace] [/verbose]
Imports data specified in filename to a Connected Storage space.The file is an XML file that contains the data.
For an example, see xbstorage generate.For more information about the file's XML format, see Import and export file format, below.
There are two ways to specify the Connected Storage space:
If the input file has a ContextDescription section that is correctly populated, then this will be used to specify the Connected Storage space.
The storage space can also be partially or fully specified via command-line parameters, which take precedence over the respective elements of the storage space specified in the input file.
Examples of usage:
Note
Before importing to the specified Connected Storage space, the system will attempt to synchronize with the cloud using the same logic that runs when a Connected Storage space is acquired by a running app.
If an application with the same Primary SCID is running, this operation could cause a race condition, and the contents of the Connected Storage space could be in an indeterminate state.
If /replace is not specified, the containers specified in the input file will be erased before writing the blobs specified in the input file. Containers in the Connected Storage space not specified in the input file will remain untouched.
| Option | Description |
|---|---|
| file-name | Specifies an XML file that contains the data to import. |
| /scid:SCID | Specifies the Service Configuration Identifier (SCID). |
| /machine | Specifies a per-machine Connected Storage space. This option cannot be used simultaneously with the /msa option. |
| /msa:account | Specifies an account to use for per-user Connected Storage. The user must be signed in to the console for the space to be used. This option cannot be used simultaneously with the /machine option. |
| /replace | Deletes all containers in the specified Connected Storage space before importing. |
| /verbose | Displays the status of the importation. |
xbstorage export
xbstorage export *outfile* [/context:*input-file*] [/scid:*SCID*] [/machine] [/msa:*account*] [/verbose]
Exports data from a Connected Storage space to the file specified by outfile.The file is an XML file that contains the data.
See xbstorage generate to see how to generate an example.For more information about the file's XML format, see Import and export file format, below.
There are two ways to specify the Connected Storage space:
If the /context parameter is used, and the file name specified by <infile> has a ContextDescription section that is correctly populated, then that file will be used to specify the Connected Storage space.
The storage space can also be partially or fully specified via command-line parameters, which take precedence over the respective elements of the storage space specified in the /context file.
Examples of usage:
Note
Before exporting the specified Connected Storage space, the system will attempt to synchronize with the cloud using the same logic that runs when a Connected Storage space is acquired by a running app.
If an application with the same Primary SCID is running, this operation could cause a race condition, and the contents of the Connected Storage space could be in an indeterminate state.
| Option | Description |
|---|---|
| outfile | XML file the data will be exported to. |
| /context:input-file | Specifies an input file from which to read the space information. |
| /scid:SCID | Specifies the service configuration identifier (SCID). |
| /machine | Specifies a per-machine Connected Storage space. This option cannot be used simultaneously with the /msa option. |
| /msa:account | Specifies an account to use for per-user Connected Storage. The user must be signed in to the console for the space to be used. This option cannot be used simultaneously with the /machine option. |
| /verbose | Displays the status of the export operation. |
xbstorage delete
xbstorage delete [/context:*input-file*] [/scid:*SCID*] [/machine] [/msa:*account*] [/verbose]
Deletes all data from a Connected Storage space.
There are two ways to specify the Connected Storage space:
If the /context parameter is used, and the file name specified by <infile> has a ContextDescription section that is correctly populated, then that file will be used to specify the Connected Storage space.
The storage space can also be partially or fully specified via command-line parameters, which take precedence over the respective elements of the storage space specified in the /context file.
Examples of usage:
Note
Before deleting the specified Connected Storage space, the system will attempt to synchronize with the cloud using the same logic that runs when a Connected Storage space is acquired by a running app.
If an application with the same Primary SCID is running, this operation could cause a race condition, and the contents of the Connected Storage space could be in an indeterminate state.
| Option | Description |
|---|---|
| /context:input-file | Specifies an input file from which to read the space information. |
| /scid:SCID | Specifies the service configuration identifier (SCID). |
| /machine | Specifies a per-machine Connected Storage space. This option cannot be used simultaneously with the /msa option. |
| /msa:account | Specifies an account to use for per-user Connected Storage. The user must be signed in to the console for the space to be used. This option cannot be used simultaneously with the /machine option. |
| /verbose | Displays the status of the delete operation. |
xbstorage generate
xbstorage generate *file-name* [/containers:*n*] [/blobs:*n*] [/blobsize:*n*]
Generates dummy data and saves to a file specified by <filename>.
For more information about the file's XML format, see Import and export file format, later in this article.
The service configuration identifier (SCID) will be set to 00000000-0000-0000-0000-000000000000, and the account will be set for a per-machine Connected Storage space.If you want to change those values, you can edit the file directly after it is generated.
Examples of usage:
Note
The byte data is a simple ascending sequence; for example, a five-byte blob would have the following bytes: 00 01 02 03 04. >> If you want to specify a per-user Connected Storage space, change the Account node in the XML file to something like the following:
| Option | Description |
|---|---|
| file-name | XML file the data will be written to. |
| /containers:n | Specifies the number, n, of containers to generate. The default count is 2. |
| /blobs:n | Specifies the number, n, of blobs to generate. The default count is 3. |
| /blobsize:n | Specifies the number, n, of bytes per blob. The default size is 1024 bytes. |
xbstorage simulate
xbstorage simulate [/reserveremainingspace] [/forceoutoflocalstorage] [/stop] [/verbose]
Simulates 'ran out of local storage' conditions for the Connected Storage service.
| Option | Description |
|---|---|
| /reserveremainingspace | Reserves all remaining space in Connected Storage. Deleting something from ConnectedStorage will open up space that you can use. |
|/forceoutoflocalstorage | Simulates the Connected Storage Service having no available space left. Deleting something from Connected Storage will not change the Connected storage service from reporting out of memory. |
|/stop | Stops all simulations. |
|/verbose | Displays the status of the simulated operation. |
Common Options
xbstorage [/?] [/X*:address* [*+accesskey*] ]
| Option | Description |
|---|---|
| /? | Displays help for xbstorage.exe |
| /X*:address* [+accesskey] | Specifies the host name or address (shown as Tools IP on the console) of a targeted console, but does not change the default console. If you do not use this option, the default console is used.Accesskey is a string that you can use to restrict access to a console to only those people who know the access key. Set the access key by using the command xbconfig **accesskey=**your-key; then, restart your console to make the access key effective. To access a console that is configured with an access key, you must include a plus sign (+) and the access key after the IP address or host name of the console. |
Note
If an access key is provided when the default console is set by xbconnect, then the access key is stored as part of the address of the default console.|
Gamesaveutil
Gamesaveutil allows you to manage locally cached Connected Storage for your app with all of the same functions that xbstorage provides.
Just like the xbstorage tool, gamesaveutil offers the same six data managing functions, with some differences in behavior.The import, export, delete, and reset commands require an Xbox Live user to be signed in.
You can use the Xbox App in Windows 10 to view and change the current user.
Commands
| Command | Description |
|---|---|
| import | Imports data from the specified XML file |
| export | Exports data to the specified xml file |
| delete | Deletes data from the specified app |
| reset | deletes local data only for the specified app |
| generate | generates dummy data and saves to the specified xml file |
| simulate | simulates special conditions that are difficult to test |
Gamesaveutil import
gamesaveutil import <filename> [/pfn:<PFN>] [/scid:<SCID>] [/replace]
Imports data specified in <filename>
The file is an XML file that contains the data. Type gamesaveutil help generate to see how to generate an example.
There are two ways to specify the app PFN and SCID where the data is saved:
If the input file has a ContextDescription section that is correctly populated, then this will be used to specify the target app PFN and SCID.
The PFN and SCID can be partially or fully specified via command-line parameters, which take precedence over the respective elements of the specified PFN and SCID from the input file.
| Option | Description |
|---|---|
| /pfn:<PFN> | Specifies the Package Family Name(PFN) for the app to perform the import for. The app must be installed. |
| /scid:<SCID> | Specifies the Service Configuration Identifier (SCID). This is from your Xbox Live configuration. |
| /replace | Delete all containers before performing the import. |
Example Usages:
Note
The app must be installed and have synced data already in order to import.
If /replace is not specified, existing containers will not be touched unlessthey are specified in the input file.
gamesaveutil export
gamesaveutil export <outfile> [/pfn:<PFN>] [/scid:<SCID>] [/context:<infile>]
Exports data to the file specified by <outfile>.The file is an XML file that contains the data.
Type gamesaveutil help generate to see how to generate an example.
There are two ways to specify the location of the data to export:
If the /context parameter is used, and the filename specified by
<infile>has a ContextDescription section that is correctly populated, then that file will be used to specify the location of the source data.The location can also be specified via command-line parameters, which take precedence over the respective elements specified by the
/contextfile.
| Option | Description |
|---|---|
| /context:<infile> | Use the specified file to specify the app PFN and SCID. |
| /pfn:<PFN> | Specifies the Package Family Name(PFN) for the app to perform the export from. The app must be installed. |
| /scid:<SCID> | Specifies the Service Configuration Identifier (SCID). This is from your Xbox Live configuration. |
Example Usages:
Note
The app must be installed and have synced data already in order to export.
gamesaveutil delete
File Storage Companion For Mac
gamesaveutil delete [/pfn:<PFN>] [/scid:<SCID>] [/context:<infile>]
Deletes all data for the specified PFN and SCID.
There are two ways to specify the location of the data to delete:
If the
/contextparameter is used, and the filename specified by <infile> has a ContextDescription section that is correctly populated, then that file will be used to specify the location of the source data.The location can also be specified via command-line parameters, which take precedence over the respective elements specified by the
/contextfile.
| Option | Description |
|---|---|
| /context:<infile> | Use the specified file to specify the app PFN and SCID. |
| /pfn:<PFN> | Specifies the Package Family Name(PFN) for the app to delete the data from. The app must be installed. |
| /scid:<SCID> | Specifies the Service Configuration Identifier (SCID). This is from your Xbox Live configuration. |
Example Usages:
Note
The app must be installed in order to delete containers.
gamesaveutil reset
File Storage Companion
gamesaveutil reset [/pfn:<PFN>] [/scid:<SCID>] [/context:<infile>]
Deletes all local data for the specified PFN and SCID.
File Storage Companion Mac
There are two ways to specify the location of the data to delete:
If the
/contextparameter is used, and the filename specified by <infile> has aContextDescriptionsection that is correctly populated, then that file will be used to specify the location of the source data.The location can also be specified via command-line parameters, which take precedence over the respective elements specified by the
/contextfile.
| Option | Description |
|---|---|
| /context:<infile> | Use the specified file to specify the app PFN and SCID. |
| /pfn:<PFN> | Specifies the Package Family Name(PFN) for the app to delete the data from. The app must be installed. |
| /scid:<SCID> | Specifies the Service Configuration Identifier (SCID). This is from your Xbox Live configuration. |
Example Usages:
Note
The app must be installed in order to delete local data.
gamesaveutil generate
gamesaveutil generate <filename> [/containers:<n>] [/blobs:<n>] [/blobsize:<n>]
Generates dummy data and saves to a file specified by <filename>.
The Service Configuration Identifier (SCID) will be set to 00000000-0000-0000-0000-000000000000.To change those values, you can edit the file manually after generation.
| Option | Description |
|---|---|
| /containers:<n> | Specifies how many containers to generate. Default is 2. |
| /blobs:<n> | Specifies how many blobs per container to generate. Default is 3. |
| /blobsize:<n> | Specifies how many bytes per blob. Default is 1024. |
Example Usages:
Note
The byte data is a simple ascending sequence; for example, a 5-byte blob would have the bytes 00 01 02 03 04.
gamesaveutil simulate
gamesaveutil simulate [/markcontainerschanged] [/stop]
Simulates special conditions for testing certain scenarios.
| Option | Description |
|---|---|
| /markcontainerschanged | Forces all containers to look like they have been changed when an app resumes from suspend and gets a new provider. Affects all apps until cleared with /stop. |
| /stop | Stops all simulations. |
Import and export file format
The XML file used with the import, export, and generate commands with the xbstorage tool has the format shown in the following example.
The only change needed to format this xml for import, export, and generate in gamesaveutil is to replace the <Account> member node of the <ContextDescription> node with a <PackageFamilyName> node.That will change the <ContextDescription> node from this:
to this:
Note
The format of data in these XML files is not identical to what's on the platform, it is for import and export purposes only. The data format for these XML files could potentially change in the future, so they should be treated as an intermediate or utility format, not an archival format.
The ContextDescription node is optional.If you are making a Connected Storage space for a machine, you can use <Account machine='true'/> instead of <Account msa='user@domain.com'/>.Otherwise, the context can be specified on the command line for importation.
File Storage App
Blobs and containers should have the corresponding names given to them by the game or application for which the file is being generated.The contents of each blob should be a string wrapped in a CDATA tag, which is generated by calling CryptBinaryToStringW with the flag CRYPT_STRING_BASE64 providing the data for that blob as a raw byte array.
Portable File Box Legal Size
Conversely, blob data can be converted back by calling CryptStringToBinary and providing the formerly encrypted string.
File Storage For Mac
An example of using these two functions is shown in CryptBinaryToString returns invalid bytes in the MSDN forums for Visual Studio.