Outcome#
You can reach the shared Windows Blade server, use it for appropriate GUI and
prototype work, place durable data under the assigned project share, use D:
only temporarily, and avoid C: and personal profile folders.
Concept#
Blade is a shared Windows engineering workstation, not an HPC cluster or
permanent personal drive. Data left only on local C: or temporary D: can be
lost, while heavy computation can degrade every interactive user.
Worked Example#
The durable copy remains on P:, D: is clean, C: was not used, and no heavy unattended compute was started.
A correct example uses these decisions:
- Where does durable Blade project work belong? In the approved P: supervisor and username folder.
- What is Blade primarily for? Interactive Windows GUI software and light prototyping.
Common Trap#
Keeping the only copy on C: or D:, treating Blade as a general ML server, or exposing the real mapped path in the public submission.
If Blocked#
Check VPN, exact hostname, account format, and assigned supervisor folder. Do not use another person's saved credentials, install remote services, or select another mapped drive. Use the remote access guide.
Useful references:
Understand Before Accepting AI Output#
An agent must not install system features, choose another drive, or run a heavy local workload because Euler access is inconvenient. Verify host, storage, and shared-resource impact.