# What differentiates a MakeCode device drive from regular drives?

**URL:** https://forum.makecode.com/t/what-differentiates-a-makecode-device-drive-from-regular-drives/4815
**Category:** Help
**Created:** [December 5, 2020, 8:33pm UTC](https://forum.makecode.com/t/what-differentiates-a-makecode-device-drive-from-regular-drives/4815 "2020-12-05T20:33:36Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![UnsignedArduino](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/unsignedarduino/32/592_2.png) [@UnsignedArduino](https://forum.makecode.com/u/UnsignedArduino)
#### Post date: [December 5, 2020, 8:33pm UTC](https://forum.makecode.com/t/what-differentiates-a-makecode-device-drive-from-regular-drives/4815/1 "2020-12-05T20:33:36Z")

</div>

I couldn’t find a category that fit, so I just choose #Share-your-Arcade-projects-here help.

* * *

I’m trying to make a Python script that detects MakeCode devices in bootloader mode. When a MakeCode device enters bootloader mode, a drive shows up, where you can copy a `.uf2` file to flash the device. Can I guarantee that `CURRENT.UF2` is always on the drive? Or is the some attribute of the drive that differentiates it from regular drives?