Sorry, I don't know what that's all about. I haven't used DOSIDLE.
Sounds vaguely familiar with the issue of running an MS-DOS utility while a different version of the MS-DOS command interpreter is loaded (ie what version of DOS you booted from). The workaround for this was to load a device driver in CONFIG.SYS (or was it AUTOEXEC.BAT?) called SETVER which would somehow set up a version table that allowed newer and older versions of MS-DOS utilities to be compatible with that of the version of COMMAND.COM currently in memory that the machine was booted with.
I could be WAAAAAAY off on this one though.
VCDX3 #34, VCDX4, VCAP4-DCA #14, VCAP4-DCD #35, VCPx4, vEXPERTx3, MCSEx3, MCSAx2, MCP, CCAx2, A+
