Where Jennefer keeps files

Jennefer keeps its apps and its big files, your models, Studio packs and the local runtime, in one Jennefer folder. You pick it in Setup and can move it later in Hub > Settings > Storage, for example when your C: drive is nearly full.

Pick the folder in Setup#

• Setup's first screen has Install to: one button per drive with its free space, and Choose a folder.
• A drive becomes a Jennefer folder on that drive, for example D:\Jennefer. The line below says Apps, models and packs go to D:\Jennefer.
• Picking the Windows drive keeps the default places in your user folder.
• When the Windows drive has less than 40 GB free and another drive has at least twice as much, Setup says so, for example C: has 21 GB free. Models take 5 to 20 GB each; D: has 410 GB.

See Installation for the rest of Setup.

What goes where#

The small files always stay in .jennefer. Your choice of folder is saved there too, in location.json. See Engine.

Move to another drive#

1. 1

   Open Hub > Settings > Storage

   It shows the Jennefer folder, the space it Used, the space Free on its drive, and the size of Models, Studio packs and Local runtime.

2. 2

   Pick the new place

   Under Move to, choose a drive, or Choose a folder.

3. 3

   Confirm

   The Hub asks, for example, Move 18 GB to D:\Jennefer? It says whether the move takes a moment (same drive) or is a copy (another drive). Choose Move.

4. 4

   Wait for the move

   A bar shows what is moving and how much is copied. When it is done, the Hub shows Moved and the new folder.

• While files move, local models, pack installs and Studio jobs wait, and Studio says why. Endpoint models keep working.
• Apps you install from then on go to the new folder. Installed apps stay where they are. They are small, about 10 to 30 MB each.
• To go back, choose Move back to the default folder.
• Hub > Models shows where your models are saved, with Saved in, the free space and a pointer to Settings > Storage.

When a move is refused#

The Engine checks before it starts and refuses the move when:

• the folder cannot be written, or it is the folder already in use;
• work is running: a download, a pack setup or a GPU job. Let it finish or stop it first;
• the new folder already holds files, or it is inside the current folder;
• the drive has too little free space for a copy.

If a step fails during the move, the work so far is undone and the old folder stays in use. The message ends with Nothing was changed.

FAQ#