Simple question about dropdown screen times

Noticed when using a drop down screen, like clicking on "forums", that the list is displayed for a fraction of a moment.

Also, when clicking start>run>(for instance "fsutil dirty query d:" that the window (is it DOS?) closes really fast.

Where is the setting that controls how long windows like this stay open?

Quote from jogalot : Noticed when using a drop down screen, like clicking on "forums", that the list is displayed for a fraction of a moment. Also, when clicking start>run>(for instance "fsutil dirty query d:" that the window (is it DOS?) closes really fast. Where is the setting that controls how long windows like this stay open?

dunno about the first thing, but for the second, open a cmd window and then run your command:

start > run > cmd

cmd> fsutil.....

I assume when you run the command directly it simply executes and then exits so you'd need to add a 'wait' command. It's much easier just to open a cmd window

http://www.addictivetips.com/wind...windows-7/

Should be same registry edit in each version running back to XP. Change at your own risk.

Not sure if all your menus are doing this or just on SD, but that's a useful setting.

You are talking about two very different things.

The "Forums" button on this page is a menu built with javascript. It's delay in opening and closing is based off the javascript code for this specific site, and in no way is affected by your computer settings. It cannot be adjusted by you.

Similarly, there is no setting that will make the black window (cmd window) stay up longer after executing a command from the run window. As instructed above, you need to first open a command window rather than running the command in the run box.

The link for the reg edits are specific to delays when hovering over a start menu folder for example.

Hope this helps.

Hey, thanks PP, never would have thought of calling it that. Changed the setting once and it helped, going to choose a higher number to tweak it and appreciate your help -- very much.

And thanks for the CMD info, too. I always thought that was synonymous with the run command.

This all started when the PC ran a disk check on drive D at startup, and that's been cured. Don't know what or why things changed, but settings were altered.

For DOS-based apps you need to run cmd first THEN the program otherwise the window will close quickly.

Quote from jogalot : Hey, thanks PP, never would have thought of calling it that. Changed the setting once and it helped, going to choose a higher number to tweak it and appreciate your help -- very much. And thanks for the CMD info, too. I always thought that was synonymous with the run command. This all started when the PC ran a disk check on drive D at startup, and that's been cured. Don't know what or why things changed, but settings were altered.

Congrats on finally reaching 100 posts.

Quote from PerfectPoo : You are talking about two very different things. The "Forums" button on this page is a menu built with javascript. It's delay in opening and closing is based off the javascript code for this specific site, and in no way is affected by your computer settings. It cannot be adjusted by you. Similarly, there is no setting that will make the black window (cmd window) stay up longer after executing a command from the run window. As instructed above, you need to first open a command window rather than running the command in the run box. The link for the reg edits are specific to delays when hovering over a start menu folder for example. Hope this helps.

ding ding ding, we've got a winner. Despite the moniker, they know what they're talking about!

Quote from jogalot : Noticed when using a drop down screen, like clicking on "forums", that the list is displayed for a fraction of a moment.

Forums is disappearing so fast because you're clicking on it. Hovering will trigger the menu and it will stay open as long as you're hovering over it or any of the menu items.

Quote from jogalot : Hey, thanks PP, never would have thought of calling it that. Changed the setting once and it helped, going to choose a higher number to tweak it and appreciate your help -- very much. And thanks for the CMD info, too. I always thought that was synonymous with the run command. This all started when the PC ran a disk check on drive D at startup, and that's been cured. Don't know what or why things changed, but settings were altered.

Quote from Dr. J : For DOS-based apps you need to run cmd first THEN the program otherwise the window will close quickly.

It is very, very, very rare to encounter a program built for DOS these days. If you were to try to use one, there is a very high probability you would already know how to use it. What Dr. J is calling "DOS-based apps" are actually Windows apps with no GUI (graphical user interface). They need to be run from the command line, and, that said, what Dr. J claimed is, with regard to command-line apps, false. The Run command does almost the exact same thing as the command line, only it is limited in that it cannot execute any commands other than opening a file. There is absolutely no need to open a command line to run a command-line app. Just type the file location and name in the Run box and hit Run. You won't see the program run besides a brief flash on the screen, but it will run.

As an example, create a batch file with the following code:

@set /p foo="Please enter a value: "
@echo %foo% >> bar.txt

Save it to an empty folder on your hard drive. Run the file from the Run line. It will prompt you to input a number or string. Enter whatever you please and hit return. The application will create a text file in the same folder as the batch file. This text file will contain whatever text you entered. It will change the contents of this file every time you rerun the application, regardless of whether you run it from the Run box or from the command line.