My machine does not recognize dongle when it boots up.

[Poly Kim]

hi,

I registered a ventuz presentation as startup program.(not sure if the terminology is proper) I always do this for my client when I deliver presentation.

When the machine is turned on, I see ventuz watermark with the ventuz5 runtime dongle inserted. So, I kill the presentation and re-open it, the watermark goes away.

In case of boot-up, it seems that the presentation is started before the machine recognizes the dongle. Is there any solution for this? Do I need to build up my own application which holds up the presentation until the machine recognizes the dongle?

Regards
Poly

[Karol]

Hi Poly!

This is a problem of Windows. We cannot do anything about it.
We have no influence on the device enumeration of Windows.
I think you are right. You need to somehow delay the start-up of your presentation.

Best Regards
Karol

[lerou]

You should NEVER put your VPR directly into that startup folder. Always allow Windows a bit of time.

Go to your VPR and create a batch file next to it:
start.bat

Open it and enter:

Code: Select all

timeout /t 30
start my.vpr
exit

And then you put a shortcut to that batch file into startup. Make it 30 seconds or more. Give Windows time to start its processes. Otherwise some application might even steal your focus.

Best,
rou

[Poly Kim]

hi Karol & lerou

Now, it is quite clear. Thank you, guys!

Poly

[u-double-u]

Hi,
this seems to almost work on my Surface Pro 3 ("Windows 10"), except that a dialog pops up asking how this presentation should be opened?
Selecting Ventuz 5 Presenter/Runtime then starts it.
But that's not exactly what the whole idea was.
How do I make sure it is always definitely using Ventuz 5 presenter for this?
cheers.

[lerou]

this is a Windows issue. Right click on a VPR, open with -> choose another app, select V5 and check "always open..".

Or in your batch file start not the vpr but use the absolute path to the presenter and pass on the vpr as parameter.

Cheers,
rou

[u-double-u]

Thanks,
but those things I had tried.
The only way so far seems to set the filetypes to the according applications. .vpr was assigned to an unknown (none) app.
After that, it worked.
cheers.