Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Chapa9ai

Profile Information

  • OS
    XP Pro x86
  1. Chapa9ai

    FDV fileset for XP

    Er- yep. A belated response, but I've been working on a certain issue for a while. As far as I can tell XP Pro SP3 with the fdv files is generally stable. The one thing I haven't been able to do is to get the fdv files, along with an HFSlip version of XP Pro SP3, to "play nice" with a Hauppauge Nova-S PCI TV tuner card. Basically the card drivers won't install properly if I include these files.. A Hauppauge utility called "prodinfo" (on the installation CD) gives a "No Device Data Available" message. This is after the drivers have supposedly been installed "successfully." I have noticed certain key files don't even get placed in the system32 directory (where they do in the XP version I'm currently using to run the TV card). Have also done some testing with a program called a program called "EPG Collector" http://sourceforge.net/projects/epgcollector/ This error message shows up in a log file after attempting to run it: "Exception: Retrieving the COM class factory for component with CLSID {B64016F3-C9A2-4066-96F0-BD9563314726} failed due to the following error: 80040154." I believe the fdv fileset removes COM (Component Object Model) related services, but I couldn't work out which files specifically are involved... Out of ideas and feeling pretty much out of my depth here!
  2. Chapa9ai

    FDV fileset for XP

    An “amateur workaround” for the mofcomp.exe issue would be as follows: 1) Create the following folder: HFSLIP\SOURCE\$OEM$\$$\SYSTEM32\wbem 2) Get a copy of mofcomp.exe (e.g. use a program like “universal extractor,” extract it from SOURCE\i386\mofcomp.ex_), and put it in the above wbem folder. The issue involving audio codecs and/or drivers seems to relate to Windows File Protection and “System File Checker” (sfc_os.dll in Win XP). See: http://www.tomshardware.com/forum/76178-45-silent-driver-installation-problem and http://support.microsoft.com/default.aspx?scid=kb;en-us;831583&FR=1&PA=1&SD=HSCH A workable solution here (see post 12 therein by jdoe) : http://www.msfn.org/board/topic/110834-disable-xp-sfcwfp-works-with-sp3/ For some reason FDV’s sfcfiles.dll (http://www.vorck.com/windows/xpsp4.html under "Shutting off WFP with a hacked DLL") doesn’t seem to work with XP Pro SP3.
  3. Chapa9ai

    FDV fileset for XP

    Hi guys. I thought I might wade in with a response to some issues raised by ebernard (post 67) a while ago- if anyone is still interested! I have not read anything explicit from fdv about XP Pro v. XP Home, either online or in the readme.txt that comes with the fdv fileset. It seems unlikely that the files will work with XP Home. The fdvfiles version of txtsetup.sif (not “textsetup.sif” btw ) corresponds to files found in the XP Pro CD I386 directory. (My testing involves running .iso files on Virtualbox, either created by HFSLIP or directly from a tweaked SOURCESS folder.) Using an XP Home SOURCE, and deleting fdv’s version of this file from the HFSLIP\FDVFILES folder (effectively using the one in the original XP Home SOURCE\i386 directory instead) gets rid of the admtoolw.chm etc errors, and also the HFSLIPnnn.INF file errors you mention in Question 2. However the issue of a desktop with no taskbar, start menu, and desktop icons etc., remains. I don't think the "black desktop" as such is an issue. With an XP Pro SOURCE folder, and obviously fdv’s version of txtsetup.sif undeleted, said errors do not occur, and there is a viable taskbar etc. after logon, though some “issues” remain. Brabant, in post #65, mentions mofcomp.exe and audio codecs etc.- my post below has a couple of workarounds for this. The Administrator logon issue referred to in Question 3 probably doesn’t have anything to do with the fdv files as such. A couple of good references on this subject are: http://www.overclockers.com/windows-xp-unattended-installation-part-ii/ (note what it says about winnt.sif) and http://unattended.msfn.org/unattended.xp/view/web/27/SESSID=06b865e538896ca624168c8a4f502bde
  • Create New...