Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Posts posted by Mercury_22

  1. Hi!

    Just a little tweack for your bat files If you want them to run no matter the location of bdaforserver folder !

    -> So NO NEED FOR

    and it will extract as "bdaforserver" to your windows

    installation drive,thats were the setup MUST be runned from, otherwise it wont work




    cd /d %0\..
    @echo off
    and replace
    (also add quotes " at the end of the line)

    For example

    @echo off

    cd /d %0\..

    copy %systemroot%\system32\bdaplgin.ax "../source\x64\System32"

    copy %systemroot%\system32\kstvtune.ax "../source\x64\System32"

    copy %systemroot%\system32\ksxbar.ax "../source\x64\System32"

    copy %systemroot%\system32\Mpeg2Data.ax "../source\x64\System32"

    copy %systemroot%\system32\mpg2splt.ax "../source\x64\System32"

    copy %systemroot%\system32\MSDvbNP.ax "../source\x64\System32"

    copy %systemroot%\system32\MSNP.ax "../source\x64\System32"

    copy %systemroot%\system32\MSVidCtl.dll "../source\x64\System32"

    copy %systemroot%\system32\en-US\MSVidCtl.dll.mui "../source\x64\System32"

    copy %systemroot%\system32\en-US\kstvtune.ax.mui "../source\x64\System32"

    copy %systemroot%\system32\en-US\kswdmcap.ax.mui "../source\x64\System32"

    copy %systemroot%\system32\en-US\ksxbar.ax.mui "../source\x64\System32"

    copy %systemroot%\system32\psisdecd.dll "../source\x64\System32"

    copy %systemroot%\system32\psisrndr.ax "../source\x64\System32"

    copy %systemroot%\system32\VBICodec.ax "../source\x64\System32"

    copy %systemroot%\system32\vbisurf.ax "../source\x64\System32"

    copy %systemroot%\system32\WSTPager.ax "../source\x64\System32"

    copy %systemroot%\SysWOW64\bdaplgin.ax "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\kstvtune.ax "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\ksxbar.ax "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\Mpeg2Data.ax "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\mpg2splt.ax "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\MSDvbNP.ax "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\MSNP.ax "../source\x64\SysWOW64'

    copy %systemroot%\SysWOW64\MSVidCtl.dll "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\en-US\MSVidCtl.dll.mui "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\en-US\kstvtune.ax.mui "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\en-US\kswdmcap.ax.mui "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\en-US\ksxbar.ax.mui "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\psisdecd.dll "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\psisrndr.ax "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\VBICodec.ax "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\vbisurf.ax "../source\x64\SysWOW64"

    copy %systemroot%\SysWOW64\WSTPager.ax "../source\x64\SysWOW64"


    Good luck with your work !

  2. Hey Guys -

    I know someone in an earlier post mentioned that they were getting the messages that their tuner card couldn't be communicated with. I have solved that problem on my system with the following set of commands:

    regsvr32 /s Mpeg2Data.ax

    regsvr32 /s mpg2splt.ax

    regsvr32 /s kstvtune.ax

    regsvr32 /s MSDvbNP.ax

    regsvr32 /s MSNP.ax

    regsvr32 /s VBICodec.ax

    regsvr32 /s vbisurf.ax

    regsvr32 /s bdaplgin.ax

    regsvr32 /s ksxbar.ax

    regsvr32 /s psisrndr.ax

    regsvr32 /s WSTPager.ax

    I grabbed those files from my Vista 32-bit install and it works (they will be under system32 and need to be copied to system32 on your 2008 install.) You can put the commands in a batch file for ease of running them. It just registers a whole bunch of ax filter files that aren't registered by default. My TV (Hauppauge HVR-1600) now works in DScaler, but I still can't get the WinTV software working.

    Hope this helps someone.

    You're wrong your Card it's working because it's a CX2388x card and it's using DScaler's own drivers (NO WDM drivers ?!) !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    Any CX2388x & SAA713x Cards it will work with DScaler 4.1.17 on a tipical (out of the box) install of Windows Server 2008 Standard Trial x86 & x64 + drivers !!! All you have to do it's to say yes when DScaler it's asking you if it should use his own drivers instead of typical (WDM?!) drivers !

    The Proof is the fact that your app (WinTV software) it's not working!!!!

  3. Just Right click on Vista.bat and select Run as Administrator ! :P (= sudo B) )

    Or to enable the built-in ADMINISTRATOR ACCOUNT right click on computer select "manage" then select "Local Users and Groups" then "Users" double click "Administrator" or right click on it and select "Properties" then uncheck "Account is disabled" :angel

    And now you can log off and log in as "built-in ADMINISTRATOR ACCOUNT" (= root :rolleyes: )

  4. Ok! So you're gone do this on your girlfriend computer where as i understend you have installed WAIK and all the files from vista's DVD it's on E:\ Vista ! Right :huh: ? Also, it's vista x86 ?

    Well if all of above are correct then all you have to do it's to copy the code below to notepad and then save that notepad as Vista.bat anywhere you like and execute it ! B)

    "%PROGRAMFILES%\Windows AIK\Tools\PETools\oscdimg.exe" /b"%PROGRAMFILES%\Windows AIK\Tools\PETools\x86\boot\etfsboot.com" /h /lLRMCFRE_EN_DVD /o /u2 E:\Vista C:\Image.iso

    Then transfer Image.iso to yor linux and burn it! ;)

    Let me know if you succeed !

  5. OK ! but just to be clear please tell me:

    1 - on which OS / computer are you planning to create and burn the ISO file ? linux or windows?

    2 - when you're saying "Vista's files" you mean the files from vista's dvd or the files from C:\ drive of your girlfriend's computer ?

  6. For those interested in the next version of Business Desktop Deployment (BDD) 2007:

    Microsoft Deployment unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. The fourth generation deployment accelerator adds integration with recently released Microsoft deployment technologies to create a single path for image creation and automated installation. Microsoft Deployment’s tools and end-to-end guidance reduce deployment time, standardize desktop and server images, limit service disruptions, reduce post-deployment help desk costs, and improve security and ongoing configuration management.

    Microsoft Deployment technologies eliminate interaction time required to install desktop and server operating systems. Interaction at the targeted computer may take a few moments using the Lite Touch Installation (LTI) method or it can be completely automated using Zero Touch Installation (ZTI). Zero Touch Installation utilizes Microsoft System Center Configuration Manager 2007 or Systems Management Server 2003 with the Operating System Deployment Feature Pack. Lite Touch Installation can be used when software distribution tools are not in place.

    Microsoft Deployment also uses Configuration Manager 2007’s stand-alone media-initiated operating system deployment feature. This release offers project management guidance for all deployment roles and separates technical documentation for the products and technologies to facilitate automation tasks.

    Microsoft Deployment enables deployment of the following Microsoft products:

    Windows Vista Business, Enterprise, and Ultimate (32 and 64 bit)

    Office Professional, Professional Plus, Enterprise, and Ultimate 2007

    Windows Server 2003 R2 (32 and 64 bit)

    Windows XP Professional with Service Pack 2 (32 and 64 bit) or Windows XP Tablet PC Edition

    Pre-release versions of Windows Server 2008 (32 and 64 bit)

  7. I've tested my system (2x74 RAPTOR RAID 0) with pagefile and without pagefile and i discover that i'm better without pagefile :thumbup

    That's because you've changed your commit limit, and forced the NT memory manager to be biased towards committing to RAM so that it will only be able to commit VA pages from applications into RAM. The memory manager can only commit pages to a backing store (RAM or paging file), and if you only have RAM (or RAM and a very small paging file), all or most of your pages committed will have to be in RAM because they can be nowhere else. It'd be a problem if you tried to commit more VA than you have RAM in the box, but that's the only drawback to not having a paging file performance-wise. You can't dump the box or get data from a crash without a paging file, but that has nothing to do with performance.

    So what's your recommendation in this case for the best performance & stability ? (with or without pagefile) :rolleyes: And why? B)

  8. I have the same amount of ram 4GB and i'm not using pagefile ! :angel

    I've tested my system (2x74 RAPTOR RAID 0) with pagefile and without pagefile and i discover that i'm better without pagefile :thumbup

    So i recommend you that if the amount of memory used by the applications usually open at the same time on your system it's lower than 3GB, to forget about pagefile :P

    At least try and convince yourself ! :yes:

  • Create New...