Vuze : Could Not Create This File. Shall I Try Again?

In Vuze's configuration directory, at that place are several files stored. Here's a brief description of what they are (which is useful if you want to know what to go along and what to delete). If you lot are using a contempo version of Vuze, you lot can become to Options-->Files and at that place volition exist a link to the configuration directory at the bottom of the screen.

Location [edit]

Default location of the configuration files is Bone-dependant:

• In Linux the location is "~/.azureus/"
• In Mac OS X the location is "/Users/<username>/Library/Application Back up/Vuze/"

• Under OSX 10.7 Panthera leo the User Library folder is inivisible by default. Quick way to it is in the Finder, get to the "Go" menu, hold down the Selection cardinal and you should see a Library option appear. Select it and you lot're in your User/Library binder.

• In Vista and Windows seven the location is "C:\Users\<username>\AppData\Roaming\Azureus\"
• In Windows XP the location is "C:\Documents and Settings\<username>\Awarding Data\Azureus\"
  • In very old Windows 95, 98 and Me system the files may also be located in "C:\Program Files\Azureus"

Please note that the user's Windows profile directory is hidden past default, and you have to enable show subconscious files in Windows Explorer in order to come across the directory. Depending on your version of windows there may be more than one way to practise this only for a typical copy of XP and above you can do the following. Enter the Control Panel from the Starting time Menu and select Appearance and Themes (XP) or Advent and Personalization (Windows 7). Now select Folder Options and modify to the view tab. One time in that location you can select the radio button titles Show hidden files and folders.

Contents [edit]

Annotation: not complete

Name	Blazon	Description
active	Directory	Contains details information for every download that Vuze is currently managing. Each download will have a file of hashid.dat, which is essentially a copy of the torrent file used to create it, plus other values stored alongside for that particular download (created by Vuze and plugins). Torrents' status information is stored in 'downloads.config' file. one
debug	Directory	This directory is used to store screenshots, logs and other information when you choose to generate a debug report.
devices	Directory
dht	Directory	DHT stuff, I guess.
internet	Directory	Some .dat files.
logs	Directory	Contains text files containing logs relating to different parts of Vuze. If y'all select "Generate debug info" from Help card, the generated debug.zip file volition include the log files here and will exist created here.
plugins	Directory	Stores the plugin files which have been installed for your user only (rather than for all users).
rss	Directory
shares	Directory	DHT stuff, I guess.
subs	Directory	.vuze and .results files.
tmp	Directory	Temporary (.tmp) objects.
torrents	Directory	A few .tmp files.
azureus.config	Bencoded file 2	Stores all the main settings used by Vuze. Some plugins will also shop data here too.
azureus.statistics	Bencoded file	Stores a count of how many bytes you lot take downloaded and uploaded.
azureus.properties	Apparently text file	Optional: List of system properties to set - each line is of the form <property_name>=<property_value> and results in a call to System.setProperty( <property_name>, <property_value> )
banips.config	Bencoded file	Stores information about banned IPs (related to IP filters).
categories.config	Bencoded file	Stores information well-nigh each category you currently have configured.
devices.config	Bencoded file	Stores data about devices.
downloads.config	Bencoded file	Stores information about every download y'all currently have in Vuze. Some minimal status information will be stored in here virtually each download, but the bulk of data for each download will be in the corresponding *.dat file (renamed copy of original .torrent file) in the active directory.
filters.config	Bencoded file	Stores information about the IP filters you lot accept ready. Related files include: ipfilter.dl, ipfilter.ext and ipfilter.cache
friends.config	Bencoded file	Stores information about friends (if you use the azbuddy/friends functionality)
tables.config	Bencoded file	Stores data about layout and column setup of tables.
update.log	Plainly text file	Stores information regarding actions performed by Vuze that require Vuze to be airtight (and optionally restarted) before they tin be practical.

Changing Location [edit]

You tin can change the location of the configuration folder past performing the following steps:

1. Backup your existing installation!
2. Note the old location of the Vuze configuration directory, phone call this <config_old> (the main settings would therefore be in <config_old>/azureus.config)
3. Fix the new location (call it <config_new>) and ensure that your user (and the Vuze runtime procedure) has full write permission to this folder
4. Note the existing location of the Vuze installation directory (call it <install>). On Windows this the binder that contains Azureus.exe, on OSX information technology is the Vuze.app package.
5. Close Vuze
6. Copy the entire contents of <config_old> to <config_new>. If you are making <config_new> and <install> the same location then this will require yous to merge the contents of the 'plugin' sub-directories.
7. Do one of the following in order to laissez passer the location of <config_new> to Vuze on startup (aggrandize <config_new> to exist the total absolute path when inserting)
   1. Windows
      Create/edit a file named Azureus.exe.vmoptions in <install> and add the single line
       -Dazureus.config.path=<config_new>
      If there is an existing line
       -include-options ${APPDATA}\Azureus\java.vmoptions
      then supercede this with
       -include-options <config_new>\java.vmoptions
      (unless <install> is the same as <config_new>)
   2. OSX
      Locate the info.plist file in <install>/Contents (show the parcel contents of the .app if needed)
      Edit this in textedit and locate the section starting with
          <key>Properties</key>
          <dict>
      Insert afterwards the<dict>, on a new line
          <central>azureus.config.path</key>
          <cord><config_new></cord>
      (plain replacing the <config_new> ...)
   3. Linux
      Edit the startup script to add an actress parameter to java, -Dazureus.config.path=<config_new>
8. Restart Vuze

Clear settings [edit]

If you manage to somehow break Vuze's configuration and you can't get things to piece of work over again, you might endeavour to reset settings and start again with the default settings.

A new Reset option was added to Mode options in version 4.4.1.0. ³ In the older Vuze clients (before version 4.four.i.0), there was no built-in command to clear the settings, so you would have to do information technology manually.

• Note: uninstall/reinstall of Vuze does not modify the settings.

Yous can hands articulate settings past deleting the respective files from this configuration directory. Please note that the configuration files usually accept a backup copy (*.bak), so recollect to delete it, too.

1. Exit Vuze properly (and bank check that the process actually died). Vuze always saves the configuration files at exit, so deleting the files while Vuze is still active does not produce expert results.
2. Delete the file 'azureus.config' (and its backup 'azureus.config.bak'), where the main settings are stored, and almost all options in Vuze return to default settings.
3. Table layout settings (consequence of cavalcade setup deportment etc.) are stored in 'tables.config'. Delete it, and you get the default columns dorsum to most tables (Library, Peers, etc.)

At that place are likewise other configuration files, similar explained in table in a higher place, but those files should non concern most users.

Note virtually active torrents: Similar explained in the table higher up, all condition data about the currently agile torrents is stored in the file 'downloads.config' and in the directory 'active'. Deleting them will remove all status information about your current torrents. Then, be careful with those files.

Note about plugins: Although deleting the settings file azureus.config does clear settings related to well-nigh plugins, it does not remove or uninstall plugins. You accept to uninstall plugins through the uninstall wizard in Vuze menus or manually remove plugin files (the subdirectory and the files) either from the configuration directory or the Vuze program directory.

Configuration Presets [edit]

You can create a file containing configuration presets (i.east. initial values) that you want Vuze to use past creating a folder named 'custom' in the configuration directory and so placing a text file in that binder that has a proper noun ending in ".config" - for example <config_dir>/custom/mypresets.config

This file should contain lines in the following format:

<parameter_name>=<type>:<value>        

• parameter_name - the internal parameter name used by Vuze for the configuration setting
• type - one of 'long', 'bool' (value 'truthful' or 'false'), 'string', 'bladder', 'byte[]' (value must be encoded as base16 string), 'list' or 'map' (last 2 utilize a bencoded cord to stand for the value)

The post-obit sets the default relieve location to 'C:\My Downloads\ and TCP listen port to 48787:

Default\ relieve\ path=string:c:\\My Downloads TCP.Listen.Port=long:48787        

Note that spaces in the config cardinal name (the part before the = sign) need to be escaped by prefixing with a \, likewise any \ characters in the value itself.

Once the settings have been applied the file will be renamed to have a suffix of ".applied" - this means the settings will only exist practical in one case, not every time Vuze is started.

Notes [edit]

Note 1: If you want to add all active torrents dorsum into Vuze, you should re-create across the agile directory to your new configuration directory. If you lot aren't able to add together your torrents back in from the location that you lot saved your torrents to, then you can always re-create the .dat files from active directory across to a temporary directory, rename them from *.dat to *.torrent and elevate them into Vuze. If all goes well, Azureus will match the hash ID stored in the renamed *.dat file, so load up all the previous settings related to that download from the *.dat file in the agile directory.

Note ii: Bencoded files are specially encoded files used by torrent programs. Usually they can be read also with text/hex editors, although their contents will await like gibberish. There are special Bencode editors, which enable proper handling of the data. 1 of the best editors is Ultima's Bencode Editor, which was originally distributed at the uTorrent forums, http://forum.utorrent.com/viewtopic.php?id=31306 , but has at present besides a site at Google: http://sites.google.com/site/ultimasites/bencode-editor

Annotation 3: A built-in command to reset configuration to default values was introduced in version 4.4.1.0. The control resides in the Mode options, where a Reset button will make clean options stored in azureus.config to the default values.

navadienteor.blogspot.com

Source: https://wiki.vuze.com/w/Configuration_directory

Share this post