The way we used to do this was to redefine something we used relatively frequently, such as REDRAW, to include a check on the time since the last saving command, by comparing the value in the DATE System Variable to that in TDUPDATE. If that's more than a certain amount, do QSAVE. I expect a lot of people don't use REDRAW so much any more, probably because most people don't work with blips turned on [I do, because they provide real and worthwhile information], so that may not be the best command to use for the purpose, but it could be done with some other command, preferably not a drafting one like Line but something display-related like Zoom?
EDIT:
Like this, included at the front of whatever command you make a new definition of:
(if (> (rem (- (getvar 'date) (getvar 'tdupdate)) 1.0) 0.00347222)
(command "_.qsave")
); if
[Those System Variables report in decimal days, and 5 minutes is one 288th or .00347222... of a day. Adjust for other intervals.]
It should be a non-transparent-capable command [so not Zoom after all] that is redefined to include such a thing, because QSAVE itself cannot be invoked transparently. I think maybe we used to have it set up so that it didn't just QSAVE, but asked whether you wanted to do so. But I don't use that any more -- I just save [like voting] "early and often."
In any case, it needs to be tied to doing something, that is, triggered by something, because I don't think there's anything in AutoCAD that is constantly monitoring the passage of time, that could make it happen regularly on its own. And besides, when you step away from your computer for a while, would you really want the drawings you have open QSAVEd over and over when nothing has happened in them?
Kent Cooper, AIA