Windows 2000 (insufficient space on system partition for app logs): An application writes very large logs to %SystemRoot%\Temp and cannot change its log path. The system partition lacks free space, but a second disk is available. How can you run the app without changing its configured path while keeping other settings intact?

Introduction / Context:
Some legacy applications hard-code log or temp locations (e.g., %SystemRoot%\Temp). When the system partition is short on space, Windows 2000 supports NTFS mount points that let you graft another volume into a folder path, effectively expanding capacity at that exact directory without changing the application configuration.

Given Data / Assumptions:

• Application writes to %SystemRoot%\Temp and cannot change the path.
• System partition lacks space; a second disk is available.
• Goal: increase capacity at that specific path without breaking the app.

Concept / Approach:
Create a new NTFS volume on the second disk and mount it as a folder at %SystemRoot%\Temp. This mount point makes the application write to the new volume transparently. Shortcuts or shares do not redirect file system I/O; only an NTFS mount point ensures the path resolves to a different volume at the kernel level.

Step-by-Step Solution:
Add the second disk and initialize it in Disk Management.Create and format a new NTFS partition.Empty %SystemRoot%\Temp (back up and delete transient files as allowed).In Disk Management, assign “Mount in the following empty NTFS folder” → select %SystemRoot%\Temp.

Verification / Alternative check:
Confirm that the new volume appears as a mounted folder and that free space reflects the new volume’s capacity. Run the application to verify log creation and monitor space consumption on the mounted partition.

Why Other Options Are Wrong:
Creating a share or shortcut: Does not redirect file system writes at the same path; the app will still write to the original volume.

Mounting the system partition elsewhere (option c): Reverses the direction and fails to relieve space at %SystemRoot%\Temp.

None of the above: Incorrect because NTFS mount points solve the exact constraint.

Common Pitfalls:
Leaving existing files in %SystemRoot%\Temp so the mount fails (folder must be empty), or assuming mapped drives/shortcuts change the path for app I/O.

Final Answer:
Add a second disk; create and format a partition, then mount that partition as %SystemRoot%\Temp