new HP monitor takes longer to switch video modes

[ginahoy]

I just upgraded my monitor from an LG L1710 to an HP L1965. The first thing I noticed is that switching video modes takes significantly longer.

I rourtinely use DOS batch files to maintain active processes, browser cookies, etc. Even though I have echo turned off, calling a batch file causes the video to switch modes to DOS (black screen) and then back. With the LG monitor, this all took less than a second. Hardly noticeable. But with the new HP monitor, it's taking about 4 seconds.

One difference is that the LG monitor uses VGA connection but the HP uses DVI. So was the delay related to the DVI output on my video card? To test this, I swapped cables and connected the HP using VGA cable. This improved the delay by about a second, but still three times longer than the LG. So this is definitely a monitor issue.

I really like the HP. Is there anything I can do to improve the switching delay?

[Sterling_Aug]

You are complaining about 3 seconds lost in your life? Wow.

[ginahoy]

Your point is taken. Assuming I can even solve the problem, it would probably take a few months to make up the time it takes me to find a solution. That said, I use batch files multiple times a day and it's becoming more of an annoyance.

Besides, I've seen plenty of other folks drilling down on far less significant performance issues ;)

Does Windows provide an alternative method for scripting batch files without having to use DOS?

[Midknyte]

You shouldn't have to go full screen to run batch files. I run batch files in windowed mode. Is it a batch that affects video specifically?

[Sterling_Aug]

Anything you can do in DOS you should be able to use VB script to do.

[ginahoy]

You shouldn't have to go full screen to run batch files. I run batch files in windowed mode. Is it a batch that affects video specifically?Oh, Sh$#
I hadn't even thought about the DOS PIF. I just checked the properties for the Shortcuts I use to call the batch files. Bingo. They defaulted to Full Screen mode. I just changed to window mode and problem solved!!! Thanks!