Dream Feature--IfHarddiskBusy

armsys · Post by **armsys** » Tue Dec 02, 2003 12:43 am

It would be nice if IfHarddiskBusy is added into the Macro Script command set. The busy status of a hard disk tends to prolong the timeout of the following commands:

WaitCursorChanged
WaitWindowOpen
WaitWindowClosed
etc.

How do you think there's a need for the command? Please comment.

Bob Hansen · Post by **Bob Hansen** » Tue Dec 02, 2003 1:29 am

Hi Armstrong....

How about an example of how you might use this?

Also need to allow for multiple drives, mapped and UNC:
If HardDrive(HDN)Busy.....with a user defined parameter:
Let>HD1=C
Let>HD2=G
Let>HD3=\\server\share for drive that use UNC vs mapping?
Let>HDX=appply to all drives, local, remote, networked, mapped, etc.

And perhaps the negative might be easier to use:
IfHardDrive(HD3)NotBusy>...........

I guess this might end up replacing some basic Wait> commands as well?

I suspect you would also want some type of timeout with a userdefined default value? Need a separate Timeout for each HDN?

Don't mean to complicate the request, just wondering about problems I might see if using it.

armsys · Post by **armsys** » Tue Dec 02, 2003 3:14 am

Hi Bob,

Hope you're doing fine lately. When Windows just starts (from cold boot) and there are simply too many windows (instances) singing and dancing, if I start Outlook's Calendar view (through a hot key, of course), it takes relatively longer for Macro Scheduler's wait commands thanks to hard disk's busy status. Therefore, all simulated keystrokes (PRESS> and SEND>) will be missed entirely. It would be nice if the timeout can be adjusted in accordance with the hard disk's busy status.

Bob, the scenario isn't that complicated as you might imagine.

The virtual command can be applied as follows:

Label>PleaseWaitHere
Wait>.5
IfHarddiskBusy>PleaseWaitHere
...do this and do that

Bob Hansen · Post by **Bob Hansen** » Tue Dec 02, 2003 6:08 am

What about WaitReady>1 ?

I have used that in a number of places, usually as part of a three statement command structure:

WaitWindowOpen>.......
SetFocus>........
WaitReady>1

armsys · Post by **armsys** » Thu Dec 04, 2003 12:43 am

Bob,

You're absolutely right. Adding Waitready>1 helps immensely. Strangely, it wasn't required for Office 2002 and 2000. For the time being, your tip does eliminate the need for the dream command. Thanks a lot.