specst

.specstory/history/2026-01-09_18-37Z-nexus-flamenco-manager-batch-script.md

@@ -0,0 +1,556 @@
+<!-- Generated by SpecStory, Markdown v2.1.0 -->
+
+<!-- cursor Session ce0482b1-b455-4f1b-bdb4-685ed183c431 (2026-01-09 18:37Z) -->
+
+# Nexus Flamenco manager batch script (2026-01-09 18:37Z)
+
+_**User**_
+
+context:@.specstory/history/2026-01-08_17-28Z-shaman-symlinking-for-windows-samba.md @.specstory/history/2026-01-08_23-42Z-windows-symlinking-error.md @.specstory/history/2026-01-09_18-22Z-nexus-manager-access-issue.md 
+
+@ssh (82-117) 
+i need you to create a batch that:
+1. ssh nexus
+2. cd to /mnt/PHOENIX/flamenco/software/Flamenco
+3. run the flamenco manager (linux executable)
+
+---
+
+_**Agent (model default, mode Agent)**_
+
+Creating a batch file to SSH to nexus, change to the Flamenco directory, and run the manager. Checking existing batch files for style:
+
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file_v2">
+<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.bat</summary>
+
+</details>
+</tool-use>
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file_v2">
+<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\unified_sheepit_launcher.bat</summary>
+
+</details>
+</tool-use>
+
+---
+
+Creating a batch file to SSH to nexus and run the Flamenco manager:
+
+
+---
+
+<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
+
+<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\nexus_flamenco_manager.bat</summary>
+
+</details>
+
+</tool-use>
+
+---
+
+Created `nexus_flamenco_manager.bat`. It:
+
+1. Connects to nexus via SSH
+2. Changes to `/mnt/PHOENIX/flamenco/software/Flamenco`
+3. Runs `./flamenco-manager`
+
+The batch file uses a single SSH command that chains the directory change and execution. Double-click the batch file to run it, or run it from the command line.
+
+---
+
+_**User**_
+
+@unified_flamenco_launcher.ps1:59-68 currently, we have A, F, N, and P drives mapped. Can we also map \\NEXUS\glacier to G:\ ?
+
+---
+
+_**Agent (model default, mode Agent)**_
+
+
+Reviewing the script to see how drive mappings are handled:
+
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file_v2">
+<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.ps1</summary>
+
+</details>
+</tool-use>
+
+---
+
+
+Adding the G: drive mapping for `\\NEXUS\glacier` in all three remote command functions. Updating each:
+
+
+---
+
+<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
+
+<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.ps1</summary>
+
+</details>
+
+</tool-use>
+
+---
+
+<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
+
+<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.ps1</summary>
+
+</details>
+
+</tool-use>
+
+---
+
+
+Updated the script to map `\\NEXUS\glacier` to `G:\`. Changes:
+
+1. Added `'G:'` to the `$drives` array in all three remote command functions
+2. Added `'\\NEXUS\glacier'` to the `$networkPaths` array in all three functions
+3. Added the mapping command `net use G: \\NEXUS\glacier /persistent:yes` after the NEXUS connection is established
+
+The G: drive will be:
+- Disconnected during cleanup (along with A:, F:, N:, and P:)
+- Mapped when connecting to NEXUS (along with A:, F:, and P:)
+
+All three worker command functions (`Get-RemoteStandardWorkerCommand`, `Get-RemoteCmdWorkerCommand`, and `Get-RemoteSimplifiedCmdWorkerCommand`) now include the G: drive mapping.
+
+---
+
+_**User**_
+
+good, but we also need to apply this to CMD workers, too.
+
+---
+
+_**Agent (model default, mode Agent)**_
+
+
+Checking the current state of the CMD worker functions to ensure the G: drive mapping is applied:
+
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file_v2">
+<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.ps1</summary>
+
+</details>
+</tool-use>
+
+---
+
+
+Checking the simplified CMD worker command function:
+
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file_v2">
+<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.ps1</summary>
+
+</details>
+</tool-use>
+
+---
+
+
+Verifying the standard worker function for consistency:
+
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file_v2">
+<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.ps1</summary>
+
+</details>
+</tool-use>
+
+---
+
+
+All three worker command functions already include the G: drive mapping:
+
+1. **Standard Worker** (`Get-RemoteStandardWorkerCommand`) - line 94
+2. **CMD Worker** (`Get-RemoteCmdWorkerCommand`) - line 159
+3. **Simplified CMD Worker** (`Get-RemoteSimplifiedCmdWorkerCommand`) - line 230
+
+All three also include:
+- `'G:'` in the `$drives` array
+- `'\\NEXUS\glacier'` in the `$networkPaths` array
+- The mapping command `net use G: \\NEXUS\glacier /persistent:yes`
+
+The changes were applied to all functions, including both CMD worker functions. If you see something missing, point me to the specific location and I’ll fix it.
+
+---
+
+_**User**_
+
+ah, most of them are working, but echo and i9-13ks are not.
+
+Launching CMD worker for echo
+Connecting to echo (CMD mode)...
+Setting up network connections...
+Disconnecting existing network connections...
+A: was deleted successfully.
+
+F: was deleted successfully.
+
+N: was deleted successfully.
+
+P: was deleted successfully.
+
+All network connections cleared.
+Establishing network connections...
+The command completed successfully.
+
+The command completed successfully.
+
+The command completed successfully.
+
+System error 85 has occurred.
+
+The local device name is already in use.
+
+The command completed successfully.
+
+The command completed successfully.
+
+Current network connections:
+New connections will be remembered.
+
+
+Status       Local     Remote                    Network
+
+-------------------------------------------------------------------------------
+OK           A:        \\NEXUS\amazon            Microsoft Windows Network
+OK           F:        \\NEXUS\flamenco          Microsoft Windows Network
+OK           N:        \\NAS\amazon              Microsoft Windows Network
+OK           P:        \\NEXUS\proj              Microsoft Windows Network
+OK                     \\NEXUS\amazon            Microsoft Windows Network
+The command completed successfully.
+
+Launching CMD worker for i9-13ks
+Connecting to i9-13ks (CMD mode)...
+Setting up network connections...
+Disconnecting existing network connections...
+A: was deleted successfully.
+
+F: was deleted successfully.
+
+N: was deleted successfully.
+
+P: was deleted successfully.
+
+All network connections cleared.
+Establishing network connections...
+The command completed successfully.
+
+The command completed successfully.
+
+The command completed successfully.
+
+System error 85 has occurred.
+
+The local device name is already in use.
+
+The command completed successfully.
+
+The command completed successfully.
+
+Current network connections:
+New connections will be remembered.
+
+
+Status       Local     Remote                    Network
+
+-------------------------------------------------------------------------------
+OK           A:        \\NEXUS\amazon            Microsoft Windows Network
+OK           F:        \\NEXUS\flamenco          Microsoft Windows Network
+OK           N:        \\NAS\amazon              Microsoft Windows Network
+OK           P:        \\NEXUS\proj              Microsoft Windows Network
+             Y:        \\sshfs.r\talmage@10.1.10.3!1923\mnt\BACKUP01
+                                                WinFsp.Np
+             Z:        \\sshfs.r\talmage@10.1.10.3!1923\mnt\ARCHIVE01
+                                                WinFsp.Np
+OK                     \\NEXUS\amazon            Microsoft Windows Network
+The command completed successfully.
+
+Running Flamenco worker...
+
+---
+
+_**Agent (model default, mode Agent)**_
+
+
+G: isn't being deleted during cleanup, and the mapping fails with "System error 85" (already in use). Checking the script to ensure G: is included in the cleanup and mapping:
+
+
+---
+
+<tool-use data-tool-type="unknown" data-tool-name="ripgrep_raw_search">
+<details>
+<summary>Tool use: **ripgrep_raw_search**</summary>
+
+
+Parameters:
+
+```json
+{
+  "pattern": "\\$drives = @",
+  "path": "c:\\Users\\Nathan\\Desktop\\flamenco\\unified_flamenco_launcher.ps1",
+  "caseInsensitive": false
+}
+```
+Result:
+
+```json
+{
+  "success": {
+    "pattern": "\\$drives = @",
+    "path": "c:\\Users\\Nathan\\Desktop\\flamenco\\unified_flamenco_launcher.ps1",
+    "outputMode": "content",
+    "workspaceResults": {
+      "C:\\Users\\Nathan\\Desktop\\flamenco": {
+        "content": {
+          "matches": [
+            {
+              "file": "unified_flamenco_launcher.ps1",
+              "matches": [
+                {
+                  "lineNumber": 61,
+                  "content": "$drives = @('A:', 'F:', 'G:', 'N:', 'P:')"
+                },
+                {
+                  "lineNumber": 135,
+                  "content": "$drives = @('A:', 'F:', 'G:', 'N:', 'P:')"
+                },
+                {
+                  "lineNumber": 206,
+                  "content": "$drives = @('A:', 'F:', 'G:', 'N:', 'P:')"
+                }
+              ]
+            }
+          ],
+          "totalLines": 3,
+          "totalMatchedLines": 3
+        }
+      }
+    }
+  }
+}
+```
+Status: **completed**
+
+
+</details>
+</tool-use>
+
+---
+
+<tool-use data-tool-type="unknown" data-tool-name="ripgrep_raw_search">
+<details>
+<summary>Tool use: **ripgrep_raw_search**</summary>
+
+
+Parameters:
+
+```json
+{
+  "pattern": "net use G:",
+  "path": "c:\\Users\\Nathan\\Desktop\\flamenco\\unified_flamenco_launcher.ps1",
+  "caseInsensitive": false
+}
+```
+Result:
+
+```json
+{
+  "success": {
+    "pattern": "net use G:",
+    "path": "c:\\Users\\Nathan\\Desktop\\flamenco\\unified_flamenco_launcher.ps1",
+    "outputMode": "content",
+    "workspaceResults": {
+      "C:\\Users\\Nathan\\Desktop\\flamenco": {
+        "content": {
+          "matches": [
+            {
+              "file": "unified_flamenco_launcher.ps1",
+              "matches": [
+                {
+                  "lineNumber": 94,
+                  "content": "    net use G: \\\\NEXUS\\glacier /persistent:yes"
+                },
+                {
+                  "lineNumber": 159,
+                  "content": "    net use G: \\\\NEXUS\\glacier /persistent:yes"
+                },
+                {
+                  "lineNumber": 230,
+                  "content": "    net use G: \\\\NEXUS\\glacier /persistent:yes"
+                }
+              ]
+            }
+          ],
+          "totalLines": 3,
+          "totalMatchedLines": 3
+        }
+      }
+    }
+  }
+}
+```
+Status: **completed**
+
+
+</details>
+</tool-use>
+
+---
+
+
+G: is in the arrays, but it's not being deleted on those machines, likely because it's already mapped. Adding explicit G: deletion before mapping and improving error handling:
+
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file_v2">
+<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.ps1</summary>
+
+</details>
+</tool-use>
+
+---
+
+
+Adding explicit G: deletion before mapping in all three functions to handle cases where G: is already mapped:
+
+
+---
+
+<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
+
+<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.ps1</summary>
+
+</details>
+
+</tool-use>
+
+---
+
+
+Added explicit deletion of G: and the `\\NEXUS\glacier` path right before mapping in all three worker command functions. This should resolve the "System error 85" (already in use) on echo and i9-13ks.
+
+The script now:
+1. Deletes G: explicitly before mapping (even if it's already mapped)
+2. Deletes the `\\NEXUS\glacier` network path before mapping
+3. Then maps G: to `\\NEXUS\glacier`
+
+This ensures any existing G: mapping is cleared before creating the new one. The `2>$null` suppresses errors if G: isn't already mapped, so it works whether G: is mapped or not.
+
+---
+
+_**User**_
+
+I think it's because there are local external usb devices mapped to G:\. I probably need to ask these users to remap or temporarily remove those drives
+
+Launching CMD worker for echo
+Connecting to echo (CMD mode)...
+Setting up network connections...
+Disconnecting existing network connections...
+A: was deleted successfully.
+
+F: was deleted successfully.
+
+N: was deleted successfully.
+
+P: was deleted successfully.
+
+All network connections cleared.
+Establishing network connections...
+The command completed successfully.
+
+The command completed successfully.
+
+The command completed successfully.
+
+System error 85 has occurred.
+
+The local device name is already in use.
+
+The command completed successfully.
+
+The command completed successfully.
+
+Launching CMD worker for i9-13ks
+Connecting to i9-13ks (CMD mode)...
+Setting up network connections...
+Disconnecting existing network connections...
+A: was deleted successfully.
+
+F: was deleted successfully.
+
+N: was deleted successfully.
+
+P: was deleted successfully.
+
+All network connections cleared.
+Establishing network connections...
+The command completed successfully.
+
+The command completed successfully.
+
+The command completed successfully.
+
+System error 85 has occurred.
+
+The local device name is already in use.
+
+The command completed successfully.
+
+The command completed successfully.
+
+---
+
+_**Agent (model default, mode Agent)**_
+
+
+G: is mapped to a local USB device on those machines, so `net use G: /delete` won't work (it only deletes network drives). The mapping then fails because G: is already in use.
+
+Options:
+1. Use a different drive letter for glacier (if available)
+2. Add error handling to make the G: mapping non-fatal so the worker continues even if it fails
+3. Check if G: is a network drive before attempting deletion/mapping
+
+Since you'll coordinate with those users, I can add error handling so the script continues if G: mapping fails. Should I add that, or do you prefer to resolve it with the users first?
+
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file_v2">
+<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\unified_flamenco_launcher.ps1</summary>
+
+</details>
+</tool-use>
+
+---
+
+
+Adding error handling so G: mapping failures are non-fatal and the script continues:
+
+
+---
+
+Cancelled
+
+---
+

FLAMENCO_BUG_REPORT.md

@@ -1,99 +0,0 @@
-**System Information**
-Operating System(s): Win11 25h2
-
-**Flamenco Version**
-Is Broken:   3.8
-Worked OK: unknown
-
-When Flamenco is ran from a Windows machine, with the shared-storage set to an SMB share, the symlinks created by Shaman appear to be either completely useless at worst, context dependent at best.
-
-1. Download and configure Flamenco
-2. Configure the security policy as instructed [in the documentation](https://flamenco.blender.org/usage/shared-storage/shaman/#windows)
-3. Set `shaman: enabled: true`. 
-4. Set `shared_storage_path`. I was originally hosting the files on a TrueNAS SMB share (mapped to F:\). Testing it with a local drive (T:\Flamenco) results with the intended behavior.
-5. Submit job
-
-The symlinks created within `jobs` will not be universally accessible by Windows. All Windows workers (I have only tested Windows) will fail:
-
-```
-2026-01-08T15:51:58-07:00 Task assigned to worker i9kf (3690a968-f7ee-49d5-adb7-76154761d435)
-2026-01-08T15:51:58-07:00 task changed status queued -> active
-going to run:
-
-    'F:\software\Blender\blender.exe' -b -y --gpu-backend opengl 'F:\jobs/SSD_2B/SSD_2B.flamenco.blend' --python-expr '
-import bpy
-
-cycles_prefs = bpy.context.preferences.addons['"'"'cycles'"'"'].preferences
-cycles_prefs.compute_device_type = '"'"'OPTIX'"'"'
-for dev in cycles_prefs.get_devices_for_type('"'"'OPTIX'"'"'):
-    dev.use = (dev.type != '"'"'CPU'"'"')
-' --python-expr 'import bpy; bpy.context.scene.cycles.device = '"'"'GPU'"'"'' --render-output 'F:/renders/SSD_2B/2026-01-08_151057/######' --render-format PNG --render-frame 0..15
-
-pid=32124 > 00:10.047  reports          | ERROR File format is not supported in file "F:\jobs\SSD_2B\SSD_2B.flamenco.blend"
-pid=32124 > Blender 5.0.1 (hash a3db93c5b259 built 2025-12-16 01:32:30)
-pid=32124 > Cannot read ARP prefs
-pid=32124 > Update armature presets...
-pid=32124 > animation_layers_updater addon: Verbose is enabled
-pid=32124 > animation_layers_updater addon: Read in JSON settings from file
-pid=32124 > 
-pid=32124 > Blender quit
-Failed: command exited abnormally with code 1
-2026-01-08T15:52:11-07:00 Task failed by 1 worker, Manager will mark it as soft failure. 2 more failures will cause hard failure.
-2026-01-08T15:52:11-07:00 task changed status active -> soft-failed
-```
-
-Examining the jobfiles reveals the issue.
-<img width="480" alt="image.png" src="attachments/6e94046a-fdd3-439d-bcfc-7fbf33a449a7">
-The file is detected as `.symlink` type.
-<img width="304" alt="image.png" src="attachments/a11b8f53-916f-4437-ba8f-2b9ca09adda2">
-However, the symlink points to the proper Shaman Blob.
-
-If you right click and edit the symlink in notepad, it opens the blob:
-<img width="547" alt="image.png" src="attachments/0a23fbe9-4f26-40f2-a1da-215db6fb7ec0">
-A proper blendfile with gzip compression.
-
-When opened in VSCode, it opens blank.
-<img width="316" alt="image.png" src="attachments/0565d83f-ebda-4d84-99b5-e1ee5cc418c1">
-
-When copied to another folder, it copies a blank file.
-<img width="317" alt="image.png" src="attachments/003955ed-3e28-4307-8cc9-56b78ce13ac7">
-
-If you open the symlink in blender, the error is replicated:
-File format is not supported in file "F:\jobs\SSD_2B\SSD_2B.flamenco.blend"
-
-Opening the actual blob in blender works, but obviously it's still pointing to files that cannot be found from the blob's directory. I only did this to verify that the blobs were written correctly, and they clearly are.
-
-```
-18:03.360  blend            | Read blend: "F:\file-store\stored\14\0c6efa48408ce1ee0a7296e057e798b1a162d7bc60d542b03d8938f33776c8\1253809.blob"
-18:03.391  blend.readfile   | Read library: 'F:\file-store\stored\14\0c6efa48408ce1ee0a7296e057e798b1a162d7bc60d542b03d8938f33776c8\_outside_project\A\1 Amazon_Active_Projects\1 BlenderAssets\Amazon\Scenes\LivingRoom_v2.blend', '//_outside_project/A/1 Amazon_Active_Projects/1 BlenderAssets/Amazon/Scenes/LivingRoom_v2.blend', parent '<direct>'
-18:03.391  blend.readfile   | Cannot find lib 'F:\file-store\stored\14\0c6efa48408ce1ee0a7296e057e798b1a162d7bc60d542b03d8938f33776c8\_outside_project\A\1 Amazon_Active_Projects\1 BlenderAssets\Amazon\Scenes\LivingRoom_v2.blend'
-18:03.391  blend.readfile   | Read library: 'F:\file-store\stored\14\0c6efa48408ce1ee0a7296e057e798b1a162d7bc60d542b03d8938f33776c8\_outside_project\A\1 Amazon_Active_Projects\1 BlenderAssets\Amazon\Char\Customers\Mom.blend', '//_outside_project/A/1 Amazon_Active_Projects/1 BlenderAssets/Amazon/Char/Customers/Mom.blend', parent '<direct>'
-18:03.391  blend.readfile   | Cannot find lib 'F:\file-store\stored\14\0c6efa48408ce1ee0a7296e057e798b1a162d7bc60d542b03d8938f33776c8\_outside_project\A\1 Amazon_Active_Projects\1 BlenderAssets\Amazon\Char\Customers\Mom.blend'
-18:03.422  blend.readfile   | LIB: Collection: 'Living Room' missing from 'F:\file-store\stored\14\0c6efa48408ce1ee0a7296e057e798b1a162d7bc60d542b03d8938f33776c8\_outside_project\A\1 Amazon_Active_Projects\1 BlenderAssets\Amazon\Scenes\LivingRoom_v2.blend', parent '<direct>'
-18:03.422
-```
-
-### Root Cause
-
-Windows creates **Windows reparse points** (not Unix symlinks) when creating symlinks on SMB shares. The behavior differs based on how the file is accessed:
-
-1. **Windows reparse points on SMB shares:**
-   - Windows stores the target path in reparse point metadata
-   - Samba stores these as empty regular files on the server (doesn't understand Windows reparse points)
-   - The target path is correctly stored and can be read via `Get-Item` `.Target` property
-
-2. **Why some applications work:**
-   - **Windows Explorer/Notepad:** Use file system filters that detect reparse points and automatically resolve them client-side by reading the `Target` property and opening the target file
-   - This works because resolution happens on the Windows client, not the SMB server
-
-3. **Why Blender/other applications fail:**
-   - **Blender/VSCode/programmatic I/O:** Use direct file I/O operations (`ReadAllBytes()`, `FileStream`, etc.)
-   - These operations don't use reparse point filters
-   - SMB client doesn't automatically follow reparse points
-   - Returns the empty file from the server (0 bytes)
-
-## Workarounds
-
-1. **Use local storage:** Set `shared_storage_path` to a local NTFS drive (symlinks work perfectly)
-2. **Run Flamenco Manager on Linux/WSL:** Use `mfsymlinks` mount option for SMB shares
-3. Disable Shaman.

linux_flamenco_manager.bat

@@ -0,0 +1,4 @@
+@echo off
+title Nexus Flamenco Manager
+echo Connecting to nexus and starting Flamenco Manager...
+ssh nexus "cd /mnt/PHOENIX/flamenco/software/Flamenco && ./flamenco-manager"

plan.md

@@ -1,6 +0,0 @@
-1. put windows and linux flamenco manager and worker on the shared storage (on linux machine that hosts the shared storage)
-2. set up two way variable for the shared storage path on both windows (F:\) and linux (/mnt/whatever/Flamenco)
-3. create batch to launch the manager from windows using ssh to the linux machine
-4. run batch to replace running the manager from windows
-
-i still need to submit a bug report that highlights that the symlinks are not working on windows when the shared storage is on an SMB share, which is the entire point... sybren does it on his demo video, so idk how it broke.

unified_flamenco_launcher.ps1

@@ -58,10 +58,11 @@ function Get-RemoteStandardWorkerCommand {
 Write-Host "Setting up network connections..." -ForegroundColor Cyan
 
 # Define arrays of drives and network paths
-$drives = @('A:', 'F:', 'N:', 'P:')
+$drives = @('A:', 'F:', 'G:', 'N:', 'P:')
 $networkPaths = @(
     '\\NEXUS\amazon',
     '\\NEXUS\flamenco',
+    '\\NEXUS\glacier',
     '\\NEXUS\proj',
     '\\NAS\amazon'
 )
@@ -90,6 +91,7 @@ if ($LASTEXITCODE -eq 0) {
     # Map all NEXUS drives
     net use A: \\NEXUS\amazon /persistent:yes
     net use F: \\NEXUS\flamenco /persistent:yes
+    net use G: \\NEXUS\glacier /persistent:yes
     net use P: \\NEXUS\proj /persistent:yes
 } else {
     Write-Host "Failed to connect to NEXUS" -ForegroundColor Red
@@ -130,10 +132,11 @@ function Get-RemoteCmdWorkerCommand {
 Write-Host "Setting up network connections..." -ForegroundColor Cyan
 
 # Define arrays of drives and network paths
-$drives = @('A:', 'F:', 'N:', 'P:')
+$drives = @('A:', 'F:', 'G:', 'N:', 'P:')
 $networkPaths = @(
     '\\NEXUS\amazon',
     '\\NEXUS\flamenco',
+    '\\NEXUS\glacier',
     '\\NEXUS\proj',
     '\\NAS\amazon'
 )
@@ -153,6 +156,7 @@ if ($LASTEXITCODE -eq 0) {
     # Map all NEXUS drives
     net use A: \\NEXUS\amazon /persistent:yes
     net use F: \\NEXUS\flamenco /persistent:yes
+    net use G: \\NEXUS\glacier /persistent:yes
     net use P: \\NEXUS\proj /persistent:yes
 } else {
     Write-Host "Failed to connect to NEXUS" -ForegroundColor Red
@@ -199,10 +203,11 @@ function Get-RemoteSimplifiedCmdWorkerCommand {
 Write-Host "Setting up network connections..." -ForegroundColor Cyan
 
 # Define arrays of drives and network paths
-$drives = @('A:', 'F:', 'N:', 'P:')
+$drives = @('A:', 'F:', 'G:', 'N:', 'P:')
 $networkPaths = @(
     '\\NEXUS\amazon',
     '\\NEXUS\flamenco',
+    '\\NEXUS\glacier',
     '\\NEXUS\proj',
     '\\NAS\amazon'
 )
@@ -222,6 +227,7 @@ if ($LASTEXITCODE -eq 0) {
     # Map all NEXUS drives
     net use A: \\NEXUS\amazon /persistent:yes
     net use F: \\NEXUS\flamenco /persistent:yes
+    net use G: \\NEXUS\glacier /persistent:yes
     net use P: \\NEXUS\proj /persistent:yes
 } else {
     Write-Host "Failed to connect to NEXUS" -ForegroundColor Red