How does launchbox work relative to roms on different drives?

[klepp0906]

Let me explain.

I'm slowly moving from using retroarch as my primary frontend, to launchbox.    retroarch would only spin up a drive containing a rom if i tried to launch said rom.  This is central to my "non nas having, non parity/redundancy having" setup.   Considering some platforms go unplayed for varying lengths of time, and as such - the drives stay spun down/sleeping more often than not.  Thus ideally increasing the lifespan.

Does launchbox behave the same way?  If i have 4 different platforms set up, each on a different hard disk - and fire up launchbox, can i expect those drives to stay spun down until I launch a game, and then, only the drive from which the game is launched to spin up?

(all metadata and media is housed within launchbox directory, only roms are not)

Edited September 22, 2019 by klepp0906

[DOS76]

I don't know this definitively but LB doesn't actually do anything with your ROMs its populated with data in the xml files so I don't see why it would force your drives to spin up just by opening it. I would assume that when you launch a ROM and the command line calls for it. It will spin up. Even with RetroArch that wasn't something you set up right it was just Windows using your systems power settings I'm assuming.

[Jason Carr]

I can confirm that LaunchBox won't access any ROM files while simply browsing, only once a game is launched, which I believe should alleviate your concerns.