Settings - Additional - Startup program ...
I know, but this is not the answer to my question:
- how can I disable the last-changes-dialog on startup? This dialog prevents wms from executing the scripts I scheduled.
- how can I force wms to automatically go to the system tray on startup
Search found 13 matches
- Sun Jun 05, 2011 2:35 pm
- Forum: General Discussion
- Topic: startup into system tray
- Replies: 2
- Views: 4052
- Thu Jun 02, 2011 7:20 am
- Forum: General Discussion
- Topic: startup into system tray
- Replies: 2
- Views: 4052
startup into system tray
I use wms on a unattended machine.
Is there a possibility to automatically minimize wms to the system tray on startup?
How can I disable the last-changes-dialog on startup? This dialog prevents wms from executing the scripts I scheduled.
Is there a possibility to automatically minimize wms to the system tray on startup?
How can I disable the last-changes-dialog on startup? This dialog prevents wms from executing the scripts I scheduled.
- Thu Jun 02, 2011 7:08 am
- Forum: General Discussion
- Topic: Access violation at address .... wms.dat
- Replies: 8
- Views: 8437
Re: Access violation at address .... wms.dat
version 1.09.1 resolved the access violation
- Thu Apr 21, 2011 3:59 pm
- Forum: General Discussion
- Topic: Access violation at address .... wms.dat
- Replies: 8
- Views: 8437
Re: Access violation at address .... wms.dat
You mean NOW or the next time the error occurs?
- Thu Apr 21, 2011 2:36 pm
- Forum: General Discussion
- Topic: Access violation at address .... wms.dat
- Replies: 8
- Views: 8437
Re: Access violation at address .... wms.dat
Forget the issue with wrong length. We are getting further away from the real issue. Which is: access violation reading wms.dat in wms.exe. This is a robustness problem which you have to solve in wms (exception handlers).
- Thu Apr 21, 2011 1:06 pm
- Forum: General Discussion
- Topic: Access violation at address .... wms.dat
- Replies: 8
- Views: 8437
Re: Access violation at address .... wms.dat
Try disable the script, properties will be read during preparation of list of media resources. No they are NOT read allways. That's exactly the reason I implemented this script. This was your own suggestion. See your reply on topic http://www.wildmediaserver.com/forum/viewtopic.php?f=3&t=310&am...
- Thu Apr 21, 2011 9:38 am
- Forum: General Discussion
- Topic: Access violation at address .... wms.dat
- Replies: 8
- Views: 8437
Access violation at address .... wms.dat
Allmost every day I find the following error dialog on the screen when I logon to my media server (running mediaportal and wms): File:C:\Documents and Settings\All Users.WINDOWS\Application Data\Wild Media Server\wms.dat Fout laden:Access violation at address 00405A04 in module 'wms.exe'. Read of ad...
- Mon Jan 31, 2011 12:50 pm
- Forum: General Discussion
- Topic: error reported video length
- Replies: 1
- Views: 3558
error reported video length
In the attachment a truncated video fragment of a .ts videofile. WMS reports length 26:30:44.038 Mediainfo displays the correct length. This happens regularly with recordings from Discovery channel. The problem with this is that I cannot fast forward in the file on my Sony KDL-32EX700 TV. I have WMS...
- Mon May 10, 2010 7:49 am
- Forum: General Discussion
- Topic: bug reading file properties of new files
- Replies: 7
- Views: 8065
Re: bug reading file properties of new files
I've implemented the script but I had to change Properties[mpiVideoCodec] in Properties[mpiTimeLength] to make it work correctly. Apparently sometimes on a first call to mediainfo.dll the video codec can be identified but the duration can not. Maybe because the file was still being written. This is ...
- Fri Apr 30, 2010 3:27 pm
- Forum: General Discussion
- Topic: bug reading file properties of new files
- Replies: 7
- Views: 8065
Re: bug reading file properties of new files
Thanks Eugene! I was searching for a Wms-function but couldn't find it. It didn't occur to me to look at the classes.
Could you nevertheless (in some future version) write debug information of the call to mediainfo.dll to wms.log.
Could you nevertheless (in some future version) write debug information of the call to mediainfo.dll to wms.log.