Floppy Disk Archive Simulation

Par 5
Question 17intermediateSheet 1750822302

Deep Breath

A retro computing enthusiast stores modern data on virtual 1.44MB floppy disks. Large files must be split across multiple disks with authentic loading delays and motor sounds. The system occasionally displays disk swap prompts like Please insert disk 47 of 2,847 for video files. Your task: Manage modern file storage using authentic 1990s floppy disk limitations.

Why You're Doing This

You're building a file management system with severe storage constraints and authentic retro user experience. This tests file chunking algorithms, storage optimization, and user experience design with artificial limitations. It's like building a modern streaming service but with the user experience of installing Windows 95.

Take the W

  • Correctly calculates disk requirements for file sizes
  • Implements authentic floppy disk loading experience
  • Handles file spanning across multiple disks

Hard L

  • Ignores 1.44MB capacity limits
  • Allows instant file access (breaks authenticity)
  • Crashes on files requiring excessive disk count

Edge Cases

  • File smaller than single floppy disk
  • Corrupted disk in middle of file sequence
  • User inserting disks out of order
  • Modern file with metadata larger than entire floppy
  • Attempting to store compressed file that exceeds disk count limit
Input Format:
File metadata object with size and user experience preferences
Expected Output:
Storage plan with disk allocation and authenticity features
Example:
{file: 'vacation_video.mp4', size: '500MB', nostalgia_level: 'maximum'} → {disks_required: 347, loading_experience: 'authentic_motor_sounds_with_seeking', authenticity: 95}
Hints
  • 💡 Floppy capacity: 1.44MB formatted minus file system overhead
  • 💡 Loading time: 2-5 seconds per disk with authentic motor sounds
  • 💡 High nostalgia level demands longer seek times and more disk swapping prompts