Which user account do you want to use to run this program (1 Viewer)

[greybox]

Every time the scheduled recording starts, I am getting a pop up message on the screen: "Which user account do you want to use to run this program", exactly like described here: Run As Shortcut Fix. But the solution offered in that article did not help me. I am using Windows XP.

Everything worked fine with 1.1.0. I disabled all TV plugins including comskip, same problem with the pop-up. Reversed back to 1.1.0 - the problem has gone.

Attempted to upgrade to 1.1.1 again (with TV service stopped) - the MP runs but locks up when I attempt to record manually from EPG.

MediaPortal Version: MediaPortal 1.1.1
MediaPortal Skin: Blue3Wide
Windows Version: Windows XP Professional
CPU Type: Intel Core I7 2.8GHz
HDD: WDC SATA-2 80GB; Samsung SATA2, 750GB; Blu Ray drive: LiteOn iHES108
Memory: 4GB DDR3
Motherboard: Asus P7P55D PRO
Video Card: ASUS GeForce 9600GT Silent 650MHZ 512MB 1.8GHZ DDR3 PCI-E Dual DVI-I HDCP HDTV
Video Card Driver: Latest
Sound Card: IDT High Definition
Sound Card AC3: Optical out
Sound Card Driver: Latest
1. TV Card: Hauppauge WinTV HVR-1800, PCIe
1. TV Card Type: analog, ATSC
1. TV Card Driver: Latest
2. TV Card: Twinhan AD-SE200 (1028), PCIe
2. TV Card Type: DVB-S
2. TV Card Driver: Latest
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider: FTA/Cable/OTA
HTPC Case: Custom
Cooling:
Power Supply:
Remote: Universal, URC 200
TV: Samsung 58" 1080p Plasma HDTV (PN58B530)
TV - HTPC Connection: DVI/HDMI

 

[arion_p]

I think your problem is the same as this: 0003065: Spawned processes popup hidden "Run as..." dialog - MediaPortal Bugtracker
The issue has already been fixed, but thanks for reporting anyway.

 

[elliottmc]

I think your problem is the same as this: 0003065: Spawned processes popup hidden "Run as..." dialog - MediaPortal Bugtracker
The issue has already been fixed, but thanks for reporting anyway.

Arion,

Has this already been fixed? It is not fixed according to mantis, and I can't see anything in SVN for it.

Mark

 

[arion_p]

My apologies, I was obviously not thinking straight!

The issue has NOT been fixed. I had a patch prepared and discussed this with chemelli but have not yet tested and committed.
I will post back as soon as this is in SVN.

 

[ccna55]

I too have this RunAs Dialog box issue.
I have attached a small video of how i am able consistently able to reproduce this on Windows XP SP3 fully patched.
Please keep me informed of a potential fix.
I just installed 1.1.1.0 a few days ago,I had no issues on 1.0.2
I also have full admin rights on my p.c

Attached are the logs and short video.

 

[globaldonkey]

+1 here with the "run as" dialog problem when Comskip Launcher plugin tries to launch comskip. You can replicate it easily by using the "Test" button available in the Comskip Launcher plugin.

I think the problem was introduced in 1.1.1. I don't recall observing it while I was running 1.1.0

EDIT: I think it is also causing scheduled recordings to not stop. I've got a few recordings now that do not stop and have consumed 50GB+ of disk space each.

 

[greybox]

I have also seen the recording non-stop behavior, reported here:

https://forum.team-mediaportal.com/...ing-end-schedule-87359/index2.html#post665041
https://forum.team-mediaportal.com/bugreports-74/recording-not-stopping-87427/index2.html#post665036

 

[ccna55]

As i was experiencing Live Recording Freezing, Runas dialog box and Endless Recording in version 1.1.1 i decided to try and drop down to Version 1.1.0 and see if there are any issues to my surprise all works well with no known issues so far been a few days,I am going to try this weekend and upgrade back up to 1.1.1

I backed up all my settings using the backup plugin uninstalled fully,Then did a clean install of version 1.1.0(Did not delete my DB) and restored my settings and all works well now.

Thanks,
ccna55

 

[valtam]

Getting this problem to for Comskip looking forward to a fix soon

 

[jameson_uk]

This was introduced in 1.1.1 and is fixed in SVN so will be in the next release