vdr June 2006

vdr@linuxtv.org

109 participants
101 discussions

[ANNOUNCE] VDR maintenance patch 1.4.1-1
by Klaus Schmidinger 18 Jun '06

18 Jun '06

VDR maintenance patch 1.4.1-1 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-1.diff This is a 'diff' against the official version 1.4.1. Small fixes to the officially released VDR versions will be first made available as "maintenance patches" in the Developer directory, so that they can be reviewed and tested before a new official release is published. So please apply the above patch to the original VDR version 1.4.1 and report whether it works (or if it causes any new problems). This version is binary compatible to the previous version, so plugins don't need to be recompiled. The changes since version 1.4.1: - Added "-fPIC" to the compiler options in Make.config.template when compiling plugins (thanks to Udo Richter). If you use your own Make.config file, you may want to add these lines there, too. - Added some comment to cDevice::GetDevice() to explain how the individual conditions are put together to make a decision on which device to use. - Updated 'S13E' in 'sources.conf' (thanks to Antti Hartikainen). - Now making sure VPS timers don't get stuck with outdated events, and that the actual device isn't used for updating a VPS timer's event as long as other free devices are available. - Modified rcu.c to better handle RC5 codes. - Added a missing variable initialization in cRingBufferLinear::cRingBufferLinear() (thanks to Prakash Punnoor). - Fixed handling relative link targets in the ReadLink() function (reported by Patrick Cernko). - Now making sure a VPS timer has a schedule in case the epg.data file didn't contain one when VDR was started. Have fun! Klaus

1 0

softdevice2net plugin
by Luis Palacios 17 Jun '06

17 Jun '06

Hi, I'm having this problem compiling the plugin and wonder if you could help me. Could also any of the developers comment on the future of this plugin?. I think it's a very good idea. Thanks, luis make[1]: Entering directory `/home/vdr/ies-1.4.0/vdr-1.4.0/PLUGINS/ src/softdevice2net-0.0.1' g++ -g -O2 -Wall -Woverloaded-virtual -c -DUSE_MMX -DUSE_MMX2 - DPLUGIN_NAME_I18N='"softdevice2net"' -D_GNU_SOURCE -I../../../../DVB/ include -I../../../include -I../../../../DVB/include -I/usr/include/ ffmpeg/ -I/usr/lib/libavformat video-net.c video-net.c: In member function `AVStream* cFBVideoOut::add_video_stream(AVFormatContext*, int)': video-net.c:39: error: cannot convert `AVCodecContext**' to `AVCodecContext*' in assignment video-net.c:49: error: 'struct AVCodecContext' has no member named 'frame_rate' video-net.c:50: error: 'struct AVCodecContext' has no member named 'frame_rate_base' video-net.c: In member function `void cFBVideoOut::open_video (AVFormatContext*, AVStream*)': video-net.c:102: error: cannot convert `AVCodecContext**' to `AVCodecContext*' in assignment video-net.c: In member function `void cFBVideoOut::write_video_frame (AVFormatContext*, AVStream*, AVFrame*)': video-net.c:177: error: cannot convert `AVCodecContext**' to `AVCodecContext*' in assignment video-net.c: In member function `void cFBVideoOut::close_video (AVFormatContext*, AVStream*)': video-net.c:210: error: cannot convert `AVCodecContext**' to `AVCodecContext*' for argument `1' to `int avcodec_close (AVCodecContext*)' video-net.c: At global scope: video-net.c:222: warning: 'fb_mutex' defined but not used make[1]: *** [video-net.o] Error 1

1 0

Explaining VPS
by Suur Karu 17 Jun '06

17 Jun '06

Hi, all! Please explain me how VPS works in VDR? I reside in GMT+2 (+3h in summertime) timezone and when watching for example ZDF EPG shows correct time, but VPS reports +1h. Is it transmitted in localtime? Example: EPG: 06.06.2006 21:15-22:00 (45 min) VPS: 06.06 20:14 and as result +1:01 Is it correct? Regards, SK

2 2

False "video data stream broken"
by Darren Salt 17 Jun '06

17 Jun '06

Situation: an incomplete recording of a programme on BBC Three. The recording was started just before the changeover between CBBC and BBC3, and I use a recording margin of three minutes; the recording was started at 18:57. I should mention that these two channels share the same VPID and APIDs, and here is a short interval in which nothing is being broadcast on those PIDs. I also have the channel update set for names only (altering this setting is not an option). This usually does not cause a problem. This time, however... The "video data stream broken" timeout was reached, resulting in an emergency exit. Of course, vdr can't be restarted immediately, and runvdr (mine) decided to sleep for five minutes because of too many restart attempts in too short a time... whoops, there go the first few minutes of the programme which I wanted to record... Maybe I should put in a short delay in runvdr.c to make this less likely. Or I could increase MAXBROKENTIMEOUT. Or perhaps VDR should be fixed so as not to assume that no data == broken stream if it can receive *any* other data from the same multiplex, or maybe channels could be individually protected against updates...? -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Use more efficient products. Use less. BE MORE ENERGY EFFICIENT. A blue box with a light on top.

3 2

Q: vdr-1.4.0/1.4.1 fail to compile
by andreyv 16 Jun '06

16 Jun '06

Hi, does anybody had a problem to compile vdr-1.4.0/1.4.1 with next error make[1]: *** No rule to make target `sys/capability.h', needed by `vdr.o'. Stop. a quick check gives next locate capability.h /usr/include/linux/capability.h if I modify vdr.c to look for linux/capability.h instead sys/capability.h I am getting next error g++ -g -O2 -Wall -Woverloaded-virtual -c -DREMOTE_KBD -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE -DVIDEODIR=\"/video\" -DPLUGINDIR=\"./PLUGINS/lib\" vdr.c vdr.c: In function 'bool SetCapSysTime()': vdr.c:116: error: 'cap_t' was not declared in this scope vdr.c:116: error: expected `;' before 'caps' vdr.c:117: error: 'caps' was not declared in this scope vdr.c:121: error: 'caps' was not declared in this scope vdr.c:121: error: 'cap_set_proc' was not declared in this scope vdr.c:123: error: 'cap_free' was not declared in this scope vdr.c:126: error: 'caps' was not declared in this scope vdr.c:126: error: 'cap_free' was not declared in this scope make[1]: *** [vdr.o] Error 1 System: OS: Mandriva 2006 (tried Mandriva 2005 with same error) Kernel: 2.6.12-12mdk DVB card: Nexus-S CPU: Athlon 1200 It looks like vdr-1.4.0/1.4.1 doesn't like my capability.h and I can not find what could be a solution. Is there requirements for newer version of kernel? Thanks, Andy

3 2

streamdev-server for 1.4.1
by Gavin Hamill 16 Jun '06

16 Jun '06

Sorry to bore you all with this old topic, but is there anyone who has a working tarball of vdr-1.4.1/PLUGINS/src/streamdev they could send me? I've spent the last 20 minutes with Google trying to pick my way through German wiki/forum posts without success :( If it contains support for the 'Extern' URL form to pipe the TS through /root/externremux.sh, that'd be perfect! :) Cheers, Gavin.

3 3

VDR help - no OSD provider Available
by Gulab Chandra Yadava 16 Jun '06

16 Jun '06

Hi Thank Udo Richter Quarries asked for my problem. 1. Do you have a 'full-featured' card (with TV out and mpeg decoder) or a 'budget' card (without TV-out)? ----I have budget card (Hauppauge WinTv NOVA-S Plus) digital satellite receiver. ----I get the follwing messages regarding Hauppauge card:- Jun 14 19:23:31 localhost kernel: CORE cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S [card=37,autodetected] Jun 14 19:23:31 localhost kernel: tveeprom 1-0050: Hauppauge model 92001, rev B1B1, serial# 415502 Jun 14 19:23:32 localhost kernel: cx88[0]: hauppauge eeprom: model=92001 Jun 14 19:23:32 localhost kernel: input: cx88 IR (Hauppauge Nova-S-Plus as /class/input/input0 Jun 14 19:23:32 localhost kernel: cx88[0]/2: cx2388x based dvb card Jun 14 19:23:32 localhost kernel: DVB: registering new adapter (cx88[0]). Jun 14 19:23:32 localhost kernel: DVB: registering frontend 0 (Conexant CX24123/CX24109)... now I run "# vdr -Pxine" I get the fiollwing messages in /var/log/messages but still there is no OSD (Almost same message for mplayer) Jun 14 19:31:47 localhost vdr: [3666] VDR version 1.3.43 started Jun 14 19:31:47 localhost vdr: [3666] switched to user 'vdr' Jun 14 19:31:47 localhost vdr: [3666] loading plugin: /usr/lib/vdr/libvdr-xine.so.1.3.43 Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/setup.conf Jun 14 19:31:47 localhost vdr: [3666] ERROR: unknown config parameter: InitialChannel = 8 Jun 14 19:31:47 localhost vdr: [3666] ERROR: unknown config parameter: InitialVolume = 1 Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/sources.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/diseqc.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/channels.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/timers.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/commands.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/reccmds.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/svdrphosts.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/remote.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/keymacros.conf Jun 14 19:31:47 localhost vdr: [3666] found 1 video device Jun 14 19:31:47 localhost vdr: [3666] initializing plugin: xine (0.7.6): Software based playback using xine Jun 14 19:31:47 localhost vdr: [3666] setting primary device to 2 Jun 14 19:31:47 localhost vdr: [3666] SVDRP listening on port 2001 Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/themes/sttng-default.theme Jun 14 19:31:47 localhost vdr: [3666] starting plugin: xine Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/themes/sttng-default.theme Jun 14 19:31:47 localhost vdr: [3666] ERROR: remote control XineRemote not ready! Jun 14 19:31:57 localhost vdr: [3666] switching to channel 1 I get follwing messages also regarding dvb Jun 14 19:23:29 localhost kernel: Linux video capture interface: v1.00 Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget dvb'. Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget_av'. Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget_ci dvb'. Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget_patch dvb'. Jun 14 19:23:29 localhost kernel: saa7146: register extension 'dvb' Can u suugset me what should I do now. --Thanks and Regards Gulab Chandra Yadava -----Original Message----- From: vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf Of vdr-request(a)linuxtv.org Sent: Wednesday, June 14, 2006 3:32 PM To: vdr(a)linuxtv.org Subject: vdr Digest, Vol 17, Issue 19 Send vdr mailing list submissions to vdr(a)linuxtv.org To subscribe or unsubscribe via the World Wide Web, visit http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr or, via email, send a message with subject or body 'help' to vdr-request(a)linuxtv.org You can reach the person managing the list at vdr-owner(a)linuxtv.org When replying, please edit your Subject line so it is more specific than "Re: Contents of vdr digest..." Today's Topics: 1. VDR help - no OSD provider Available (Gulab Chandra Yadava) 2. Re: VDR help - no OSD provider Available (Udo Richter) 3. witch softdevice output depending on hard and soft (Leo M?rquez) ---------------------------------------------------------------------- Message: 1 Date: Tue, 13 Jun 2006 17:11:15 +0530 From: "Gulab Chandra Yadava" <gulab.chandra.yadava(a)celstream.com> Subject: [vdr] VDR help - no OSD provider Available To: <vdr(a)linuxtv.org> Message-ID: <CCEE49B9CE065146BA4FE34B2748A532017BC934(a)CEL-BANGT-M01.celstream-in.com > Content-Type: text/plain; charset="us-ascii" hi I am new to linux as well as VDR. I have DVB Hauppauge DVB card. I have installed vdr-1.3.43. and I am using 2.6.16 kernel when I run vdr through console I get message vdr: no primary device found - using first device! on the same console. I am not getting any OSD for VDR. and I have also installed xine and Mplayer as a plugin to VDR. I give the following command to run the VDR $ vdr and I get the following message in /var/log/messages Jun 5 15:28:40 localhost vdr: [3361] VDR version 1.3.43 started Jun 5 15:28:40 localhost vdr: [3361] switched to user 'vdr' Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/setup.conf Jun 5 15:28:40 localhost vdr: [3361] ERROR: unknown config parameter: InitialChannel = 8 Jun 5 15:28:40 localhost vdr: [3361] ERROR: unknown config parameter: InitialVolume = 1 Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/sources.conf Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/diseqc.conf Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/channels.conf Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/timers.conf Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/commands.conf Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/reccmds.conf Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/svdrphosts.conf Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/remote.conf Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/keymacros.conf Jun 5 15:28:40 localhost vdr: [3361] found 1 video device Jun 5 15:28:40 localhost vdr: [3361] ERROR: invalid primary device number: 2 Jun 5 15:28:40 localhost vdr: [3361] ERROR: no primary device found - using first device! Jun 5 15:28:40 localhost vdr: [3361] setting primary device to 1 Jun 5 15:28:40 localhost vdr: [3361] SVDRP listening on port 2001 Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/themes/sttng-default.theme Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/themes/sttng-default.theme Jun 5 15:28:40 localhost vdr: [3361] ERROR: no OSD provider available - using dummy OSD! Jun 5 15:28:50 localhost vdr: [3361] switching to channel 1 Jun 5 15:28:50 localhost vdr: [3361] ERROR: no OSD provider available - using dummy OSD! Jun 5 15:28:52 localhost vdr: [3366] channel 11 (306) event 21:30 'M -23/06/98 Chan 5454 Program #17' status 4 Jun 5 15:28:52 localhost vdr: [3366] channel 12 (407) event 21:50 'W -23/06/98 Chan 5455 Program #26' status 4 Jun 5 15:28:53 localhost vdr: [3366] channel 8 (Sky Sports 2) event 22:02 'H -23/06/98 Chan 5451 Program #54' status 4 Jun 5 15:28:53 localhost vdr: [3366] channel 9 (229) event 22:10 'C -23/06/98 Chan 5452 Program #9' status 4 Jun 5 15:28:53 localhost vdr: [3366] channel 10 (302) event 22:10 'K -23/06/98 Chan 5453 Program Can any body help me please --Thanks and Regards Gulab Chandra Yadava ______________________________________________________________ DISCLAIMER: This electronic message, and any attachments to this electronic message are intended for the exclusive use of the addressee(s)named herein and may contain legally privileged and confidential information. It is the property of Celstream Technologies Pvt. Ltd. If you are not the intended recipient, you are hereby strictly notified not to copy, forward, distribute or use this message or any attachments thereto. If you have received this message in error, please delete it and all copies thereof from your system and notify the sender at Celstream Technologies or administrator(a)celstream.com immediately _______________________________________________________________

2 1

[ANNOUNCE] VDR version 1.4.1 released
by Klaus Schmidinger 15 Jun '06

15 Jun '06

VDR version 1.4.1 is now available at ftp://ftp.cadsoft.de/vdr/vdr-1.4.1.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.0-1.4.1.diff A summary of all the major changes since the last stable version can be found at http://www.cadsoft.de/vdr/download.htm This version is source compatible with the previous version, so plugins only need to be recompiled. Thanks to the many people who have contributed in the making, testing and debugging of this new version of VDR. Have fun! Klaus

7 10

Mailing List Etiquette
by Clemens Kirchgatterer 15 Jun '06

15 Jun '06

This is the 'official' and updated vdr-mailing-list-etiquette-reminder. Please take this as a serious advice. Take the time to read it, especially if you are new to mailinglists in general. E-mail formatting ================= Mailing list email should fit the following criteria: DO == * Trim quoted material to the minimum needed to clarify what you're talking about. * Add a blank line _before_ and _after_ each quote for better readability. * Make sure you are attributing material to the correct person (i.e. make sure the "On 19/07/2002, Joe Bloggs said:" is correct) * Write your responses _after_ the quoted text, not before. If your mail client makes it difficult to do this, get a new one. * Make sure lines are wrapped at maximum 76 characters (to fit an 80 character wide screen), even if the text had been quotet several times. * Use the correct number of ">" characters at the start of each quoted line. * Set your mail client to "english headers" to avoid subjects like: "AW: Antwort: Re: AW: AW: AW: Re: Some Topic allready trunkated" If you see one, don't just add another "Re:" but remove all "AW:" and other chained "Re:". * Use a descriptive subject! A message titled "A small wish" doesn't tell what it is about. Better use something like "should do xyz" or "crashes when doing xyz". * If the topic of the thread changed/degrades meanwhile, change the subject too. That means: Before you start to answer, have a look into the subject your are going to reply to. For example use: New topic [WAS] old topic * Always write one separate message per topic. some people (especially those who matter) might not read mixed-up and lengthy threads. * Start a new thread when posting a new subject. * Make emails as short as possible whilst keeping them comprehensible. Don't ===== * Don't post in either HTML-only or in Text and HTML. If your mail client doesn't support this, change it. * Don't top post. * Don't give a one line answer having quoted the whole post. * Don't use a too long signature. Approx. 4 lines should always be enought. * Don't reply where you should have started a new thread. This means, make sure that you're not responding to an existing posting. Just changing the subject header and deleting any quoted text is NOT enough, because the message's header will still contain references to other messages. * Don't break threads by sending a new mail, where you should have replied. * Don't test post. Send your test posts to "echo(a)fu-berlin.de" or similar reply machines. * Don't use lengthly disclaimers. If not possible, use a freemail account. * Don't quote disclaimers and other footers. General Etiquette ================= This can really be summed up in one phrase - 'be polite'. Allways use your 'Real Name' when posting to mailinglists or newsgroups. If you think something is off-topic, don't reply to the list although you may want to send a short and *polite* note to the person privately telling them which list would be more appropriate; don't just say - "that is OT here". Before asking a question, please Have a look at the mailing list archives at http://www.linuxtv.org/pipermail/vdr/ If someone flames or trolls the list, don't reply - it wastes everyones bandwidth and time. Don't reply to spam which gets through to the list - just ignore it when it does. Resources ========= * The ultimate guide to most matters to do with email etiquette is RFC-2822 which can be found at: ftp://ftp.isi.edu/in-notes/rfc2822.txt * A german site set up by some usenet-people, who take it even more serious with netiquette. http://learn.to/quote

1 0

vdr help - no OSD for VDR
by Gulab Chandra Yadava 15 Jun '06

15 Jun '06

Hi I have budget card (Hauppauge WinTv NOVA-S Plus) digital satellite receiver. Kernel 2.6.16.18 Vdr-1.3.43 I am not getting osd after running vdr. ----I get the follwing messages regarding Hauppauge card during boot:- Jun 14 19:23:31 localhost kernel: CORE cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S [card=37,autodetected] Jun 14 19:23:31 localhost kernel: tveeprom 1-0050: Hauppauge model 92001, rev B1B1, serial# 415502 Jun 14 19:23:32 localhost kernel: cx88[0]: hauppauge eeprom: model=92001 Jun 14 19:23:32 localhost kernel: input: cx88 IR (Hauppauge Nova-S-Plus as /class/input/input0 Jun 14 19:23:32 localhost kernel: cx88[0]/2: cx2388x based dvb card Jun 14 19:23:32 localhost kernel: DVB: registering new adapter (cx88[0]). Jun 14 19:23:32 localhost kernel: DVB: registering frontend 0 (Conexant CX24123/CX24109)... If I run "# vdr -Pxine" I get the fiollwing messages in /var/log/messages but still there is no OSD (Almost same message for mplayer) Jun 14 19:31:47 localhost vdr: [3666] VDR version 1.3.43 started Jun 14 19:31:47 localhost vdr: [3666] switched to user 'vdr' Jun 14 19:31:47 localhost vdr: [3666] loading plugin:/usr/lib/vdr/libvdr-xine.so.1.3.43 Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/setup.conf Jun 14 19:31:47 localhost vdr: [3666] ERROR: unknown config parameter: InitialChannel = 8 Jun 14 19:31:47 localhost vdr: [3666] ERROR: unknown config parameter: InitialVolume = 1 Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/sources.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/diseqc.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/channels.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/timers.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/commands.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/reccmds.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/svdrphosts.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/remote.conf Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/keymacros.conf Jun 14 19:31:47 localhost vdr: [3666] found 1 video device Jun 14 19:31:47 localhost vdr: [3666] initializing plugin: xine (0.7.6): Software based playback using xine Jun 14 19:31:47 localhost vdr: [3666] setting primary device to 2 Jun 14 19:31:47 localhost vdr: [3666] SVDRP listening on port 2001 Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/themes/sttng-default.theme Jun 14 19:31:47 localhost vdr: [3666] starting plugin: xine Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/themes/sttng-default.theme Jun 14 19:31:47 localhost vdr: [3666] ERROR: remote control XineRemote not ready! Jun 14 19:31:57 localhost vdr: [3666] switching to channel 1 I get follwing messages also regarding dvb during boot up Jun 14 19:23:29 localhost kernel: Linux video capture interface: v1.00 Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget dvb'. Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget_av'. Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget_ci dvb'. Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget_patch dvb'. Jun 14 19:23:29 localhost kernel: saa7146: register extension 'dvb' Can any body suggest me what should I do to get VDR OSD. --Regards Gulab Chandra Yadava ______________________________________________________________ DISCLAIMER: This electronic message, and any attachments to this electronic message are intended for the exclusive use of the addressee(s)named herein and may contain legally privileged and confidential information. It is the property of Celstream Technologies Pvt. Ltd. If you are not the intended recipient, you are hereby strictly notified not to copy, forward, distribute or use this message or any attachments thereto. If you have received this message in error, please delete it and all copies thereof from your system and notify the sender at Celstream Technologies or administrator(a)celstream.com immediately _______________________________________________________________

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr June 2006