True Progressive?

I was wondering if when you export to Quicktime at Quicktime 720p or HDV 720p if FCP will actually convert interlaced footage to progressive? I want to convert interlaced digital8 footage to hd (through the Instant HD FCP Filter plug-in) but require progressive footage instead of interlaced. So will exporting interlaced footage using one of these settings actually make it progressive or should I look elsewhere?
Any help would be appreciated. Thank you.
iMac Intel Duo 1.83GHz   Mac OS X (10.4.6)  

I have a tutorial on how to upconvert DV to DVCPRO HD. This might point you in the right direction on how to get digital 8 to HDV:
http://proapptips.com/tips/article.php?story=20061003052011208
Shane

Similar Messages

  • Interpret interlaced video with 2:2 telecine pulldown as true progressive?

    Hope my title makes sense. Not sure how well I will be able to explain.
    We have interlaced video files from film telecine. The telecine transfer were made at 25fps as the machines are PAL and this allows us to capture each descrete film frame within the 2 interlaced video fields. I believe this is called 2:2 pulldown. 2 fields for every film frame. The film is captured to V210 10-bit uncompressed blackmagic .avi files. We have films intended to be played back at anything from 12fps to 25fps. Everything is captured at 25fps as the only other available speed is 16 2/3rds fps which creates duplicated fields (3:2) and only works for 16fps content.
    So, even though the video file is interlaced (top field first) by combining the fields you get a progressive film frame. Is there anyway to tell Premiere to interpet this footage as progressive without dumping half the fields? As far as I am aware if I work with a progressive sequence or interpret the footage as progressive Premiere will retain the dominant fields and interpolate the rest. I understand this for interlaced content where each field is from a different temporall moment but we actually have the ptrogressive frames just stored as 2 fields.
    Any advice appreciated.
    Thanks
    Message was edited by: mojibake

    Premiere Pro will automatically interpret footage that is shot as progressive-as-interlaced, like 25p or 30p, but that (to my knowledge) only works correctly with footage that is from a camcorder. That's because the file is flagged in such a manner that Premiere Pro knows to put the interlaced fields in the correct order for progressive display. I work with 480/30p and 1080/30p footage (which are both interlaced as shot) frequently, and Premiere Pro does things correctly there.
    However, I think it will be a different matter in your case, unless the captures are being flagged as they are created. What does Premiere Pro say that the clips' field order (or lack thereof) is when imported? As you've surmised, if this isn't the case, telling Premiere Pro to interpret the footage as progressive is likely going to result in some unwanted artifacts. You could probably test this by importing two instances of your clip, interpreting one as progressive, and then placing them in a progressive sequence (one on top of the other) and toggling visibility between the tracks. You should quickly see if it's having the desired effect or... something else. Instinct tells me that Premiere Pro won't handle this correctly, however.
    This might be a job for After Effects, which is a certain degree smarter and more capable of interpreting such things. I'm not exactly sure how to handle it there, but the After Effects forum might be the best place to ask.

  • FCP studio 3 support for 'progressive segmented frames'

    Anyone got the new version of FCP. Do you happen to know if it handles 'progressive segmented frames' as anything other than interlaced.
    My sony hvr vie shoots what it call 'progressive'. This is explained by Sony as 'scanning progressively' yet laying down to tape as interlaced. Result is that FCP won't accept it as 'progressive' and you have to treat it as interlaced.
    Peter

    Hi Andy, the problem is that FCP 6 does not have a capture or edit preset for PsF. It offers either Interlaced or progressive presets. PsF is neither true progressive or true interlaced. So if I'm aiming at a Progressive product say for Bluray and I want to shoot using PsF which 'scans' progressively I am stuck with having to ingest the 'progressively scanned ' footage into FCP as interlaced which it isn't.
    Yes I can capture it as anything I want and render the arse off it but that's getting it wrong from the get-go.
    Just as a comparison, for a long while I was shooting 'progressively' as I thought, making a progressive m2v for SD DVD and importing it into DVDSP, all the while ignorant that DVDSP ONLY does interlaced. DVDSP would accept the progressive footage into the interlaced track without complaint but the results were always degraded because of incorrect source material.
    I don't want to make those same mistakes again with the BlUray format, I want my source material to be handled correctly from capture to disc. And at the moment it's a toss up, do I shoot progressivley, record it to tape as interlaced ( although not true interlaced ) orthen import it into FCP as, WHAT? interlaced or progressive ? and render the arse off it before I start working with it.
    Thats my conundrum, hope its clear
    Peter

  • Implements the progress bar in user defined form

    Hi Experts,
    As i am new to SAP B1 add on development field so i wants  to set the progress bar in user defined screen through sdk code. Can you guide me?
    Regards,
    silambu

    Rahul,
             It is really helped to me. But progress bar only showed.I need  Loading part  mention by some color or something..
    my coding...
    Dim progress As SAPbouiCOM.ProgressBar
    progress = oApplication.StatusBar.CreateProgressBar("Importing Data From Excel", oMatrixTml.VisualRowCount, True)
               progress.Value = 0
                For i As Integer = 0 To dataset.Tables(0).Rows.Count - 1
                    If i <> 0 Then
                        oGFun.SetNewLine(oMatrixTml, oDBDSDetail, 0, "")
                        oDBDSDetail.SetValue("U_Check", i - 1, "Y")
                        oDBDSDetail.SetValue("U_DelrCode", i - 1, dataset.Tables(0).Rows(i)("F3").ToString)
                        oDBDSDetail.SetValue("U_OrdrType", i - 1, dataset.Tables(0).Rows(i)("F4").ToString)
                        oDBDSDetail.SetValue("U_OrderNo", i - 1, dataset.Tables(0).Rows(i)("F6").ToString)
                        oMatrixTml.LoadFromDataSource()
                        progress.Value += 1
                    End If
                Next
               progress.Stop()   // stop the progress bar
                progress = Nothing
    Thanks,
    Silambu

  • "Deinterlace renders" effects a progressive project?

    Does choosing the "deinterlace renders" selection inside the project settings tab have an effect on a project that is (was shot and edited in fcp) progressive? I shot my film using a JVC HDV camera in 25p mode, ingested and edited on fcp using ProRes 422 at 25p, and then sent to color for color correcting. I'm not doing the color correcting however, an operator is, and when she set up the project, she changed the quicktime export codec to Uncompressed 10 bit 422, and then checked the "deinterlace renders" box (she turned it on). The renders seem fine to me on the small monitor, however it will be transferred to 35mm film. I noticed that when I click and unclick the box in color, the shot which is selected changes slightly and I see a shift of movement in the parade and vector scopes. The operator insists checking deinterlaced renders does nothing to the images, and that she does that for every project she does... however... any other opinions on this? The manual says nothing on the issue. Thanks!

    If you have 50 fields, then you are likely working in a "Segmented", not "interlaced" mode and that may explain why you see a little shift when checking the button. If the base video frame rate is 25, then each frame is still made of two components -- interlaced means they are temporally displaced, segmented means that although the frame was composed progressively, half of it is field 1 and the other half is field 2. You can get away with screwing up the dominance because there is no temporal displacement -- no one would notice if field 2 came before field 1-- there is no bouncing ball that would appear to stutter back and forth...
    True progressive is actually still kind of rare, especially in tape formats.
    Film isn't either progressive or interlaced -- it is the whole frame at a time as shot in camera.
    A laser recorder does scan a progressive image onto intermediate or negative, and the CRT film recorders display whole-frame images through a progression of R-G-B filters. The lasers are better in my experience, both for consistent contrast and color accuracy.
    jPo

  • CAPTURING TRUE 25P

    Hi -- I just got myself Canon's XL2 camera and am keen to try its true 25P recording capability. My questions are:
    In FCP 5.1.2:
    Do we set a specific capture setting for True 25P? Or do I just use the DV PAL setting? I see separate settings for HDV (Interlaced and Progressive) but not for DV. Would the DV PAL timeline conform to the 25P framerate?
    In DVD Studio Pro 4.1.1:
    To output as a "Progressive Scan" DVD, do I need to set a particular setting?
    Editing:
    Is Pogressive media (at 25fps) more difficult to edit?
    Rationale:
    Does Progressive make for a better DVD experience? I've read that interlaced are sharper whilst progressives are softer. I'm also using Magic Bullet to soften my movies and would like an opinion as to whether switching to True Progressive is worth all the hype -- and if so, what makes it worth it?
    Thanks...

    In FCP 5.1.2:
    Do we set a specific capture setting for True 25P? Or
    do I just use the DV PAL setting?
    Yes, use the stock PAL DV "easy setup" and you should be good to go... nothing special with DV progressive video...
    PAL is 25fps... you're good to go with the stock preset
    In DVD Studio Pro 4.1.1:
    To output as a "Progressive Scan" DVD, do I need to
    set a particular setting?
    Nope...
    Editing:
    Is Pogressive media (at 25fps) more difficult to
    edit?
    Nope...
    Rationale:
    Does Progressive make for a better DVD experience?
    I think it does.
    I've read that interlaced are sharper whilst
    progressives are softer.
    I don't see a ton of difference, but I've not really done a side by side of the same shot either...
    would like an opinion as to
    whether switching to True Progressive is worth all
    the hype -- and if so, what makes it worth it?
    Interlaced video has problems with stills, and some compression artifact might show up with it that wouldn't look as bad with Progressive. It just looks better to my old eyes... also matches the look of film better. still it's not what film looks like completely, but closer than interlaced video seems to look.
    Computer displays are progressive, so video intended for the web will benefit too.
    Jerry

  • Need help with easy setup - shot in progressive scan 29.98

    i decided to shot this evening in progress scan on my sony vx2100.... i have two clients that are asking for progressive scan... i've had no luck capturing the video.... not sure of the setup settings
    thanks

    you right... i learned last night it is 29.98 but i also got this response from my fcp users group.
    If I understand your problem correctly, you can get the footage into FCP, but it looks like ****.
    That's what happens when you use "progressive" mode on a VX2100 or a PD150. It's not really a true progressive image, and was never intended for professional production use. (I have no idea what it was intended for, frankly, other than a selling point -- i.e., to claim it does "progressive" when it actually doesn't.)
    which isn't good news if it's true...
    any thoughts

  • Mixing interlaced and progressive HDV footage?

    Is anyone mixing interlaced and progressive footage on a FCP 5 timeline? Would you set the timeline up for progressive or interlaced settings? Would there be any loss in quality? I'm specifically wondering how well the true progressive of the JVC HD100 would combine with the "faux" progressive of the Canon A1.

    I was hoping someone else would jump in with answers, because I am not familiar with either camera, and can't give you a definite answer, but I would hazard a guess that if you set both cameras to a 1/30th shutter, you would be able to mix the footage, but it would be very difficult to shoot, because it is such a slow shutter.
    Other routes, would be converting the footage using compressors advanced formats conversion, and other tricks on the timeline, with removing fields and blending etc.
    I think generally though, if you were going to intercut footage, you would notice it, at some level.
    Some tests would help you enormously, as would renting a second camera identical to the first.
    Good luck - post back with what worked and what didn't.

  • Progressive vs d-Interlaced

    1. Is there a way to convert interlaced to progressive inside FCP
    2. What is the difference between de-interlaced and progressive.
    Is there a setting to make the time line progressive in FCP? I read here that someone had his time line set to progressive. I could not find it.
    I have heard that a lot of people are shooting progressive these days, unfortunately my Canon XH A1 doesn't have the progressive settings.

    If you want to maintain high quality you should de-interlace in Compressor with Frame controls On.
    You can de-interlace in FCP, look under Video Filters > Video, but this is a poor attempt at what Compressor does MUCH better. For the most part, it will simply throw away half the resolution to create a de-interlaced image.
    De-interlaced is the considered to be the same as progressive, but you have to accept that some information had to be thrown away to make it progressive.
    A sequence with Field Dominance set to None is a progressive sequence. Look under Sequence (menu) > Settings.
    I would bet money your XH A1 has a progressive settings. Canons brochure says you can select frame rates of 60i, 30F or 24F. The HDV tape format records each of these in a 60i envelope, but they are true progressive images.

  • Progressive FCP project comes back Interlaced from Color

    Working with Sony XDCAM EX 1080 30p project. I sent it to COLOR and then rendered the clips individually out from color using 422 Color codec. Imported the clips back into FCP and they show me as interlaced. (upper field). I can't really tell (visually) if they are... don't have an HD monitor. I can send the timeline back to FCP and that sequence show as None under field dominance, but I still want to edit the corrected clips in another sequence.... so I would prefer to just used rendered (exported) files for editing and compositing in Motion.

    Some background reading, maybe... http://forums.creativecow.net/readpost/142/858269
    But in fact I get something similar even in HDCamSR 1080P2997sF.
    There is no truly progressive 1080 codec in the Final Cut World, and so PsF is treated as interlaced.
    720 doesn't exhibit this issue because it can exist as true progressive.
    And then it gets really messy, because all Solid State monitors are progressive.
    jPo

  • Using a second Mac as a display for a first

    Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
    This Frequently answered question (FAQ) comes about:
    Can an iMac/iBook/Powerbook/MacBook act as a display for another Mac since they all have a built-in display?
    The truth is complicated because you have to consider who is doing the processing, and who has the drivers for the work being done.
    1. For people who want the processing power of multiple Macs together, there is
    Daugerresearch.com's Pooch.
    2. Apple's Target Disk Mode lets you treat the hard disk of one Mac as an external drive to another. You do have to be careful with this, only the Mac that is currently booted to an active screen has its drivers enabled. If you need the drivers of the other Mac to do some sort of installation, it may not work right, or if you need it to run specific software.
    3. The iMac 27" now has a DisplayPort Input port that allows displaying from a second Mac. See Using a 27-inch iMac as an external display. There are some hurdles to get there, however some third party solutions for those hurdles are listed on:
    http://lowendmac.com/ed/bashur/09db/dvi-to-mini-displayport.html
    4. If you have a second screen to initially setup a Mac as a server of some sort you can make it "headless" (i.e. no second screen necessary) using one of these solutions:
    iChat Screen Sharing
    OSX VNC
    Netopia's Timbuktu
    Apple Remote Desktop
    Microsoft Remote Desktop
    Screen Recycler
    Finder Screen Sharing
    The speed of your network though can make such solutions appear too slow for words. If you use IP over Firewire on Mac OS X
    10.5, 10.4, or 10.3 reasonable speeds can be obtained.
    Elgato makes Firewire compatible capture devices which can capture S-Video. If you output the video of that Mac to an S-Video connector, you can view its video on the Elgato capture screen in 720 x 480 resolution. This usually is too little real estate for an effective second display, but for some it may be the quickest solution available.
    In addition, Mac Minis, Intel based iMacs and Mac Pros do accept any display that supports VGA or DVI. Contrary to what you might think, you aren't stuck to Apple's displays. The Apple displays themselves are true Progressive LCDs that are widescreen with color matching, extra ports, and an extra place to put an iSight mount if you can find an original iSight. DVI supports more resolutions, and dual-link DVI even more.
    This is the 2nd version of this tip. It was submitted on March 12, 2010 by a brody.
    Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information.

    Hi Brian,
    Thanks for using Apple Support Communities.  You can mirror the displays or make whichever display you want the primary in Extended Desktop mode.  See this article for details:
    How to use multiple displays with your Mac
    http://support.apple.com/kb/HT5019
    The white bar at the top of the left blue box represents the menu bar and determines which display is your primary display. To change your primary display, click the white bar and drag and drop it on the blue box representing the display you would prefer to be your primary display.
    Cheers,
    - Ari

  • Loading an image into an Applet from a JAR file

    Hello everyone, hopefully a simple question for someone to help me with!
    Im trying to load some images into an applet, currently it uses the JApplet.getImage(url) method just before registering with a media tracker, which works but for the sake of efficiency I would prefer the images all to be contained in the jar file as oppossed to being loaded individually from the server.
    Say I have a class in a package eg, 'com.mydomain.myapplet.class.bin' and an images contained in the file structure 'com.mydomain.myapplet.images.img.gif' how do I load it (and waiting for it to be loaded before preceeding?
    I've seen lots of info of the web for this but much of it is very old (pre 2000) and im sure things have changed a little since then.
    Thanks for any help!

    I don't touch applets, so I can't help you there, but here's some Friday Fun: tracking image loading.
    import java.awt.*;
    import java.awt.image.*;
    import java.beans.*;
    import java.io.*;
    import java.net.*;
    import javax.imageio.*;
    import javax.imageio.event.*;
    import javax.imageio.stream.*;
    import javax.swing.*;
    public class ImageLoader extends SwingWorker<BufferedImage, Void> {
        private URL url;
        private JLabel target;
        private IIOReadProgressAdapter listener = new IIOReadProgressAdapter() {
            @Override public void imageProgress(ImageReader source, float percentageDone) {
                setProgress((int)percentageDone);
            @Override public void imageComplete(ImageReader source) {
                setProgress(100);
        public ImageLoader(URL url, JLabel target) {
            this.url = url;
            this.target = target;
        @Override protected BufferedImage doInBackground() throws IOException {
            ImageInputStream input = ImageIO.createImageInputStream(url.openStream());
            try {
                ImageReader reader = ImageIO.getImageReaders(input).next();
                reader.addIIOReadProgressListener(listener);
                reader.setInput(input);
                return reader.read(0);
            } finally {
                input.close();
        @Override protected void done() {
            try {
                target.setIcon(new ImageIcon(get()));
            } catch(Exception e) {
                JOptionPane.showMessageDialog(null, e, "Error", JOptionPane.ERROR_MESSAGE);
        //demo
        public static void main(String[] args) throws IOException {
            final URL url = new URL("http://blogs.sun.com/jag/resource/JagHeadshot.jpg");
            EventQueue.invokeLater(new Runnable(){
                public void run() {
                    launch(url);
        static void launch(URL url) {
            JLabel imageLabel = new JLabel();
            final JProgressBar progress = new JProgressBar();
            progress.setBorderPainted(true);
            progress.setStringPainted(true);
            JScrollPane scroller = new JScrollPane(imageLabel);
            scroller.setPreferredSize(new Dimension(800,600));
            JPanel content = new JPanel(new BorderLayout());
            content.add(scroller, BorderLayout.CENTER);
            content.add(progress, BorderLayout.SOUTH);
            JFrame f = new JFrame("ImageLoader");
            f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
            f.setContentPane(content);
            f.pack();
            f.setLocationRelativeTo(null);
            f.setVisible(true);
            ImageLoader loader = new ImageLoader(url, imageLabel);
            loader.addPropertyChangeListener( new PropertyChangeListener() {
                 public  void propertyChange(PropertyChangeEvent evt) {
                     if ("progress".equals(evt.getPropertyName())) {
                         progress.setValue((Integer)evt.getNewValue());
                         System.out.println(evt.getNewValue());
                     } else if ("state".equals(evt.getPropertyName())) {
                         if (SwingWorker.StateValue.DONE == evt.getNewValue()) {
                             progress.setIndeterminate(true);
            loader.execute();
    abstract class IIOReadProgressAdapter implements IIOReadProgressListener {
        @Override public void imageComplete(ImageReader source) {}
        @Override public void imageProgress(ImageReader source, float percentageDone) {}
        @Override public void imageStarted(ImageReader source, int imageIndex) {}
        @Override public void readAborted(ImageReader source) {}
        @Override public void sequenceComplete(ImageReader source) {}
        @Override public void sequenceStarted(ImageReader source, int minIndex) {}
        @Override public void thumbnailComplete(ImageReader source) {}
        @Override public void thumbnailProgress(ImageReader source, float percentageDone) {}
        @Override public void thumbnailStarted(ImageReader source, int imageIndex, int thumbnailIndex) {}
    }

  • A problem in provisioning target computer

    Guys, I am engaged on keyboard driver developement. In host computer, the tool sets include visual studio 2013 and WDK 8.1 and in target computer, I installed WDK driver test service and run it as automatic service. The host OS is win7 ultimate version 64bits
    and the target OS is win7 Embedded Standard 64bits. When I provision the target computer in visual studion 2013, at the step of Provision Computer and choose debugger settings->windows debugger(kernel mode), I selected serial as connection between host
    and target, and then a series of steps are performed in configuration proccess. At last the proccess failed at the step, 'creating system restore point', the followings are logs, I just copied from log file,
    Progress event: Current: 0, Max: -1, Message: "Connecting to computer "vsapp-enc""
    Initialize: Computer: vsapp-enc
    InstallComputer: Host Computer: AVU-CLIENT
    InstallComputer: Host Architecture: x86
    InstallComputer: Host 64bit Operating System: True
    InstallComputer: Host Operating System Version: 6.1.7601.65536
    InstallComputer: Process Administrator Privilege: True
    Progress event: Current: 1, Max: 17, Message: "Connecting to driver test automation service"
    Progress event: Current: 2, Max: 17, Message: "Getting computer system information"
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Progress event: Current: 3, Max: 17, Message: "Copying driver test automation files"
    Progress event: Current: 3, Max: 17, Message: "Copying driver test automation files succeeded"
    Progress event: Current: 4, Max: 17, Message: "Configuring WDK Remote User Account"
    Progress event: Current: 4, Max: 17, Message: "WDK Remote User Account successfully created"
    Initialize: Computer:
    Initialize: Computer: vsapp-enc
    Start result group:
      Name: Install Driver Test Components
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestGroups\Install Driver Test Components.xml
      Computer: vsapp-enc
    Initialize: Computer: vsapp-enc
    Initialize: Computer:
    Initialize: Computer:
    Initialize: Computer:
    Initialize: Computer:
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Progress event: Current: 5, Max: 17, Message: "Installing .NET Framework (possible reboot)"
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\dotNetFx40_Full_x86_x64.exe" /select:"@Name='Installing .NET Framework (possible reboot)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_.NET_Framework_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:05:259]: [Installing .NET Framework (possible reboot)] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\dotNetFx40_Full_x86_x64.exe" /select:"@Name='Installing .NET Framework (possible reboot)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_.NET_Framework_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing .NET Framework (possible reboot) 00008.xml
      Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing .NET Framework (possible reboot) 00008.log
      Computer: vsapp-enc
      Test Binary: %SystemDrive%\DriverTest\Setup\dotNetFx40_Full_x86_x64.exe
      Test Name:  Installing .NET Framework (possible reboot)
      Test Display Name: Installing .NET Framework (possible reboot)
    Initialize: Computer:
    Initialize: Computer:
    RemoteExecute: Binary: %SystemDrive%\DriverTest\Setup\dotNetFx40_Full_x86_x64.exe
    RemoteExecution: Arguments: /q /norestart /log %SystemDrive%\DriverTest\Logs\DotNetInstall.log
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: 0
    Result completed
    Test process exit code: 0
    Result status updated: Pass
    Initialize: Computer:
    Initialize: Computer:
    Progress event: Current: 6, Max: 17, Message: "Installing test automation (x86)"
    Initialize: Computer:
    Initialize: Computer:
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing test automation (x86)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_test_automation_(x86)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:23:724]: [Installing test automation (x86)] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing test automation (x86)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_test_automation_(x86)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing test automation (x86) 00008.xml
      Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing test automation (x86) 00008.log
      Computer: vsapp-enc
      Test Binary: msiexec.exe
      Test Name:  Installing test automation (x86)
      Test Display Name: Installing test automation (x86)
    Initialize: Computer:
    Initialize: Computer:
    RemoteExecute: Binary: msiexec.exe
    RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\Test Authoring and Execution Framework x86-x86_en-us.msi" /qb- KITSROOT="%ProgramFiles%\Windows Kits\8.1" KITTARGET=1 /l*v "%SystemDrive%\DriverTest\Logs\Test Authoring
    and Execution Framework x86-x86_en-us.msi_install.log"
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: 0
    Result completed
    Test process exit code: 0
    Result status updated: Pass
    Initialize: Computer:
    Progress event: Current: 7, Max: 17, Message: "Installing test automation (x64)"
    Initialize: Computer:
    Initialize: Computer:
    Initialize: Computer:
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing test automation (x64)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_test_automation_(x64)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:24:720]: [Installing test automation (x64)] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing test automation (x64)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_test_automation_(x64)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing test automation (x64) 00008.xml
      Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing test automation (x64) 00008.log
      Computer: vsapp-enc
      Test Binary: msiexec.exe
      Test Name:  Installing test automation (x64)
      Test Display Name: Installing test automation (x64)
    Initialize: Computer:
    Initialize: Computer:
    RemoteExecute: Binary: msiexec.exe
    RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\Test Authoring and Execution Framework x64-x64_en-us.msi" /qb- KITSROOT="%ProgramFiles(x86)%\Windows Kits\8.1" KITTARGET=1 /l*v "%SystemDrive%\DriverTest\Logs\Test Authoring
    and Execution Framework x64-x64_en-us.msi_install.log"
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: 0
    Result completed
    Test process exit code: 0
    Result status updated: Pass
    Initialize: Computer:
    Progress event: Current: 8, Max: 17, Message: "Installing debuggers (x86)"
    Initialize: Computer:
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    Initialize: Computer:
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing debuggers (x86)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_debuggers_(x86)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:25:582]: [Installing debuggers (x86)] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing debuggers (x86)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_debuggers_(x86)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing debuggers (x86) 00008.xml
      Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing debuggers (x86) 00008.log
      Computer: vsapp-enc
      Test Binary: msiexec.exe
      Test Name:  Installing debuggers (x86)
      Test Display Name: Installing debuggers (x86)
    Initialize: Computer:
    RemoteExecute: Binary: msiexec.exe
    RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\X86 Debuggers And Tools-x86_en-us.msi" /qb- /l*v "%SystemDrive%\DriverTest\Logs\X86 Debuggers And Tools-x86_en-us.msi_install.log"
    Initialize: Computer:
    Initialize: Computer:
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: 0
    Result completed
    Test process exit code: 0
    Result status updated: Pass
    Initialize: Computer:
    Initialize: Computer:
    Progress event: Current: 9, Max: 17, Message: "Installing debuggers (x64)"
    Initialize: Computer:
    Initialize: Computer:
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing debuggers (x64)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_debuggers_(x64)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:26:641]: [Installing debuggers (x64)] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing debuggers (x64)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_debuggers_(x64)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing debuggers (x64) 00008.xml
      Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing debuggers (x64) 00008.log
      Computer: vsapp-enc
      Test Binary: msiexec.exe
      Test Name:  Installing debuggers (x64)
      Test Display Name: Installing debuggers (x64)
    Initialize: Computer:
    RemoteExecute: Binary: msiexec.exe
    RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\x64 Debuggers And Tools-x64_en-us.msi" /qb- /l*v "%SystemDrive%\DriverTest\Logs\x64 Debuggers And Tools-x64_en-us.msi_install.log"
    Initialize: Computer:
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: 0
    Result completed
    Test process exit code: 0
    Result status updated: Pass
    Progress event: Current: 10, Max: 17, Message: "Installing driver test framework"
    Initialize: Computer:
    Initialize: Computer:
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    Initialize: Computer:
    Initialize: Computer:
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing driver test framework'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_driver_test_framework_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:27:707]: [Installing driver test framework] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing driver test framework'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_driver_test_framework_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing driver test framework 00008.xml
      Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing driver test framework 00008.log
      Computer: vsapp-enc
      Test Binary: msiexec.exe
      Test Name:  Installing driver test framework
      Test Display Name: Installing driver test framework
    Initialize: Computer:
    RemoteExecute: Binary: msiexec.exe
    RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\Windows Driver Testing Framework (WDTF) Runtime Libraries-x64_en-us.msi" /qb- KITTARGET=1 /l*v "%SystemDrive%\DriverTest\Logs\Windows Driver Testing Framework (WDTF) Runtime Libraries-x64_en-us.msi_install.log"
    Initialize: Computer:
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: 0
    Result completed
    Test process exit code: 0
    Result status updated: Pass
    Initialize: Computer:
    Initialize: Computer:
    Progress event: Current: 11, Max: 17, Message: "Registering logging components"
    Initialize: Computer:
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\regsvr32.exe" /select:"@Name='Registering logging components'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Registering_logging_components_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:28:743]: [Registering logging components] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\regsvr32.exe" /select:"@Name='Registering logging components'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Registering_logging_components_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Registering logging components 00008.xml
      Log Path:
      Computer: vsapp-enc
      Test Binary: regsvr32.exe
      Test Name:  Registering logging components
      Test Display Name: Registering logging components
    Initialize: Computer:
    RemoteExecute: Binary: regsvr32.exe
    RemoteExecution: Arguments: /s %SystemDrive%\DriverTest\WTTLogcm.dll
    Initialize: Computer:
    Initialize: Computer:
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: 0
    Result completed
    Test process exit code: 0
    Result status updated: Pass
    Initialize: Computer:
    Progress event: Current: 12, Max: 17, Message: "Configure debugger settings (x64) (possible reboot)"
    Initialize: Computer:
    Initialize: Computer:
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    Initialize: Computer:
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    [11:23:29:020]: Removing any existing files from test execution folder
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureKernelDebugger'" /p:"DebugTransport=SERIAL" /p:"SerialPortNumber=1" /p:"BaudRate=115200"
    /p:"StartPolicy=Active" /p:"IgnoreUserModeExceptions=0" /p:"SuppressReboot=1" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_debugger_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:29:373]: [Configure debugger settings (x64) (possible reboot)] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureKernelDebugger'" /p:"DebugTransport=SERIAL" /p:"SerialPortNumber=1" /p:"BaudRate=115200" /p:"StartPolicy=Active"
    /p:"IgnoreUserModeExceptions=0" /p:"SuppressReboot=1" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_debugger_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Configure debugger settings (x64) (possible reboot) 00008.xml
      Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Configure_debugger_settings_(x64)_(possible_reboot)_00008.wtl
      Computer: vsapp-enc
      Test Binary: C:\Program Files (x86)\Windows Kits\8.1\Testing\Tests\Utilities\X64\DriverTestTasks.dll
      Test Name:  DriverTestTasks::_ConfigureKernelDebugger
      Test Display Name: Configure debugger settings (x64) (possible reboot)
    Initialize: Computer:
    RemoteExecute: Binary: $KitRoot$\Testing\Runtimes\TAEF\te.exe
    RemoteExecution: Arguments: "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureKernelDebugger'" /p:"DebugTransport=SERIAL" /p:"SerialPortNumber=1" /p:"BaudRate=115200"
    /p:"StartPolicy=Active" /p:"IgnoreUserModeExceptions=0" /p:"SuppressReboot=1" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_debugger_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Initialize: Computer:
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: 0
    Initialize: Computer: vsapp-enc
    Initialize: Computer: vsapp-enc
    [11:23:30:613]: Result Summary: Total=1, Passed=1, Failed=0, Blocked=0, Warned=0, Skipped=0
    Result completed
    Test process exit code: 0
    Result status updated: Pass
    Initialize: Computer:
    Initialize: Computer:
    Initialize: Computer:
    Initialize: Computer:
    Progress event: Current: 13, Max: 17, Message: "Configure computer settings (x64) (possible reboot)"
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    [11:23:31:204]: Removing any existing files from test execution folder
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureCommonSettings'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_computer_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:31:596]: [Configure computer settings (x64) (possible reboot)] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureCommonSettings'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_computer_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Configure computer settings (x64) (possible reboot) 00008.xml
      Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Configure_computer_settings_(x64)_(possible_reboot)_00008.wtl
      Computer: vsapp-enc
      Test Binary: C:\Program Files (x86)\Windows Kits\8.1\Testing\Tests\Utilities\X64\DriverTestTasks.dll
      Test Name:  DriverTestTasks::_ConfigureCommonSettings
      Test Display Name: Configure computer settings (x64) (possible reboot)
    RemoteExecute: Binary: $KitRoot$\Testing\Runtimes\TAEF\te.exe
    RemoteExecution: Arguments: "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureCommonSettings'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_computer_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Initialize: Computer:
    Initialize: Computer:
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: 0
    Initialize: Computer: vsapp-enc
    Initialize: Computer: vsapp-enc
    Initialize: Computer: vsapp-enc
    [11:23:33:864]: Result Summary: Total=1, Passed=1, Failed=0, Blocked=0, Warned=0, Skipped=0
    Result completed
    Test process exit code: 0
    Result status updated: Pass
    Initialize: Computer:
    Initialize: Computer:
    Initialize: Computer:
    Initialize: Computer:
    Progress event: Current: 14, Max: 17, Message: "Creating system restore point"
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    Initialize: Computer: vsapp-enc
    InternalRunTest: Host Computer: AVU-CLIENT
    InternalRunTest: Host Architecture: x86
    InternalRunTest: Host 64bit Operating System: True
    InternalRunTest: Host Operating System Version: 6.1.7601.65536
    InternalRunTest: Process Administrator Privilege: True
    Initialize: Computer: vsapp-enc
    GetMachinePropertiesFromService: Computer Name: vsapp-enc
    GetMachinePropertiesFromService: Architecture: AMD64
    GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
    GetMachinePropertiesFromService: Operating System Product Type: 1
    GetMachinePropertiesFromService: Domain Joined: True
    ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\cscript.exe" /select:"@Name='Creating system restore point'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Creating_system_restore_point_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    [11:23:34:288]: [Creating system restore point] Command Line:
    te.exe "%SystemDrive%\DriverTest\Run\cscript.exe" /select:"@Name='Creating system restore point'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Creating_system_restore_point_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
    /runas:Elevated
    Created new result:
      Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Creating system restore point 00008.xml
      Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Creating system restore point 00008.log
      Computer: vsapp-enc
      Test Binary: cscript.exe
      Test Name:  Creating system restore point
      Test Display Name: Creating system restore point
    Initialize: Computer:
    RemoteExecute: Binary: cscript.exe
    RemoteExecution: Arguments: %SystemDrive%\DriverTest\Setup\CreateRestore.js
    Initialize: Computer:
    RemoteExecute: Process creation return code: 0
    RemoteExecute: Process exit code: -2147217406
    Result completed
    Test process exit code: -2147217406
    Result status updated: Fail
    Initialize: Computer:
    Initialize: Computer:
    Initialize: Computer:
    Initialize: Computer:
    Progress event: Current: 14, Max: 17, Message: "Creating system restore point failed. Please ensure connectivity with the remote machine, and then restart the provisioning process."
    Initialize: Computer:
    Initialize: Computer:
    [11:23:35:413]: Install Driver Test Components summary:
    [11:23:35:413]:   Installing .NET Framework (possible reboot): Pass
    [11:23:35:413]:   Installing test automation (x86): Pass
    [11:23:35:413]:   Installing test automation (x64): Pass
    [11:23:35:413]:   Installing debuggers (x86): Pass
    [11:23:35:413]:   Installing debuggers (x64): Pass
    [11:23:35:413]:   Installing driver test framework: Pass
    [11:23:35:413]:   Registering logging components: Pass
    [11:23:35:413]:   Configure debugger settings (x64) (possible reboot): Pass
    [11:23:35:413]:   Configure computer settings (x64) (possible reboot): Pass
    [11:23:35:413]:   Creating system restore point: Fail
    Result Group Completed: Fail
    Progress event: Current: 17, Max: 17, Message: ""
    Progress event: Current: 17, Max: 17, Message: "Computer configuration log
    My question is why I got such an error? And does this step depend on any service of target computer? I surf the net a little, it seems there is Volume Shadow Copy Service relevant. But it is missing in the target computer's service list, I found. Is this
    the root cause?
    Appreciate any help.

    Hi Suma,
    Did you check that VIRSANH/VIRSAHR BAPI are correctly installed on relevant back-ends ? Moreover, if using CUA to provision users, BAPI should be installed not only on the system hosting the CUA, but on every client system (eg. ECC, SRM, BI, ...).
    You also may verify in SPAM transaction that you installed correct BAPI depending on your basis install (640, 700, ...) and on your GRC AC version (5.1, 5.2, ...). For example, if you are installing AC 5.2 on a BASIS700 system, corresponding package should be VIRSANH520_700 and/or VIRSAHR520_700. You may find more detailed information in "GRC Access Control ABAP install guide".
    Best regards,
    JC

  • Importing AVCHD 720p30 makes 60fps

    I'm using a Panasonic HMC40 to shoot 720p30 video clips. When I log and transfer, the clips import fine but they play at twice the speed. When I right-click on a clip in the browser and select item properties it states the video is 60fps. I have Easy Setup set at HDV 720P30. There is no AVCHD 720p option. Anyone know where I'm going wrong? FCE V 4.01

    The Specifications/Technical Info page of your camera manual will probably mention it in one sentence.
    Most consumer camcorders shot interlaced until recently. Now some of them give the choice of interlaced or progressive.
    However, it would be quite complicated to change to true progressive so when put in progressive mode, they simply shoot 2 identical fields per frame which is pretty much the same as 1 field per frame.
    The correct name for this system is Progressive Segmented Frames (PSF).
    http://en.wikipedia.org/wiki/Progressivesegmentedframe

  • ScreenRecycler Alternatives?

    Hi, I'm just wondering if anyone knew of an alternative way to use my MacBook Pro as a second monitor for my Mac Pro besides using ScreenRecycler (http://www.screenrecycler.com)? I'm just interested if there are other options.
    I've read a few times that these features are built into Leopard, but I've only been able to mirror my Mac Pro's monitor, I haven't been able to use my MBP as a second, extended monitor.
    Any help would be appreciated, thanks!

    Here's a user tip which hasn't yet been finalized which may have sufficient info for your needs:
    Can an iMac/iBook/Powerbook/MacBook act as a display for another Mac since they all have a built-in display?
    The truth is complicated because you have to consider who is doing the processing, and who has the drivers for the work being done.
    1. For people who want the processing power of multiple Macs together, there is
    Daugerresearch.com's Pooch.
    2. Apple's Target Disk Mode lets you treat the hard disk of one Mac as an external drive to another. You do have to be careful with this, only the Mac that is currently booted to an active screen has its drivers enabled. If you need the drivers of the other Mac to do some sort of installation, it may not work right, or if you need it to run specific software.
    3. If you have a second screen to initially setup a Mac as a server of some sort you can make it "headless" (i.e. no second screen necessary) using one of these solutions:
    iChat Screen Sharing
    OSX VNC
    Netopia's Timbuktu
    Apple Remote Desktop
    Microsoft Remote Desktop
    Screen Recycler
    The speed of your network though can make such solutions appear too slow for words. If you use Firewire over IP on Mac OS X
    10.5, 10.4, or 10.3 reasonable speeds can be obtained.
    Elgato makes Firewire compatible capture devices which can capture S-Video. If you output the video of that Mac to an S-Video connector, you can view its video on the Elgato capture screen in 720 x 480 resolution. This usually is too little real estate for an effective second display, but for some it may be the quickest solution available.
    In addition, Mac Minis, and Mac Pros do accept any display that supports VGA or DVI. Contrary to what you might think, you aren't stuck to Apple's displays. The Apple displays themselves are true Progressive LCDs that are widescreen with color matching, extra ports, and an extra place to put an iSight mount if you can find an original iSight. DVI supports more resolutions, and dual-link DVI even more.

Maybe you are looking for