BGInfo via VBS startup script?

Got bored with fighting BGInfo in the end and did the logon background with a scripted reg hack and copying the bitmap over... can live with doing it manually for that one.

Quote:

---

Originally Posted by gshaw

Hmmmm I wonder if that's it... maniac what version are you running exactly? Any chance of posting it up so I can try the older one?

Just checked, got v4.14 on one network, v4.12 on the other (that version isn't working via VBS on startup at the moment) and the website shows a v4.15 as the latest one

If not I'll leave BGInfo and just use a reg hack pointing to BMP files I create manually :rolleyes:

---

Actually funny enough it's 4.15 I'm using, it must have been out for a while as I downloaded it quite a while back so I kinda assumed it would be an older version.

Mike.

::ho hum::

Re. my mysteriously slow BGInfo times it was obvious really.

Screamingly, screamingly obvious.

As usual, if there's no sane reason for [some behaviour] then it's:

A/V interfering!

Quote:

---

Originally Posted by PiqueABoo

::ho hum::

Re. my mysteriously slow BGInfo times it was obvious really.

Screamingly, screamingly obvious.

As usual, if there's no sane reason for [some behaviour] then it's:

A/V interfering!

---

Haha welcome to my world... AV is messing up my Computer Settings loading times but no fix as yet :(

I know this is an old thread, but we just ran into this issue at our company. Just wanted to post what we saw and the solution we implemented.

For our company, the issue was with the WScript.Shell Run method. This method has a syntax of WScript.Shell.Run (strCommand, [intWindowStyle], [bWaitOnReturn]). In our environment we were, originally, specifying False for bWaitOnReturn (and it worked). At some point, this stopped working. When we changed bWaitOnReturn to True, it started working as expected.

Keep in-mind, that in the code mentioned in the original post, no bWaitOnReturn parameter is provided, which is the same as stating False.

In our environment, I believe a Group Policy Object (GPO) changed that also changed the functionality (possibly Synchronous vs Asynchronous execution); but I have not verified this.

I hope this helps others experiencing this same issue.

Also, adding a WScript.Shell.Run command for %WinDir%\System32\RUNDLL32.EXE user32.dll,UpdatePerUserSystemParameters will allow the logon screen to update after execution of BGInfo. Be sure to use the same WScript.Shell.Run method format.