[Chapa9ai]

Brabant, on 15 May 2010 - 06:40 AM, said:

The only file missing is mofcomp.exe (or so). [...] I think it's the audio codecs and/or drivers that take a long time to install. (after a while there's a message that they did'nt pass M$ labs -> 'continue anyway') But then I got a nice empty desktop. [...]

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.tomshardw...llation-problem
and
http://support.micro...=1&PA=1&SD=HSCH

A workable solution here (see post 12 therein by jdoe) :
http://www.msfn.org/...works-with-sp3/

For some reason FDV’s sfcfiles.dll (http://www.vorck.com...dows/xpsp4.html under "Shutting off WFP with a hacked DLL") doesn’t seem to work with XP Pro SP3.

This post has been edited by Chapa9ai: 25 June 2011 - 05:19 PM

[PROBLEMCHYLD]

Anyone using the latest version of fdv fileset for WinXP and have a stable system?

[Chapa9ai]

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.n...s/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!

This post has been edited by Chapa9ai: 12 October 2012 - 08:47 PM

[Brabant]

So I've got to use XP anyway...

Chapa9ai
Thanks for pointing to sfc_os.dll. It now installs faster and without this nonsense about things being unsigned.
And the mofcomp error is not in the latest file set.

A few things:
I have bmp2png in the windows/system dir. But if I do c:\bmp2png it is an "unrecognized internal or external etc..." , so it can't find the path I'd say.
In the environment variables there is %systemroot%/system and system32 and system32/wbem, all separated by colons. What's going on?

The Effects (under Display Properties -> Appearance) are unavailable. See attached pic if it's unclear what I mean. Having ClearType is essential.

Not sure if the following are sources of these problems but I ran this HFSLIP without any HFs to speed things up and I'm running XP in VPC2007.

Attached File(s)

•  effects.png (11.5K)
  Number of downloads: 4

This post has been edited by Brabant: 28 February 2013 - 07:20 AM

[Brabant]

Those three greyed out settings get enabled by changing

HKEY_CURRENT_USER\Control Panel\Desktop\UserPreferencesMask

from "00 00 00 00" to "b0 12 01 80", a value I borrowed from a non-fdv-xp install. I don't know yet if it breaks anything but these things can now be accessed.

Now what's wrong with me %systemroot%\system and other paths?

Edit:
starting a cmd box and giving PATH
gives PATH=C:\WINDOWS; ..etc.. in the non-fdv-xp box but
gives PATH=%SystemRoot%; ..etc.. in fdv-xp

Any ideas about this please?

This post has been edited by Brabant: 01 March 2013 - 03:40 PM

[Brabant]

The Path variable in

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

must be a REG_EXPAND_SZ and not a REG_SZ like it is in the file set.

Now the command Path gives PATH=C:\WINDOWS;C:\WINDOWS\System; ..etc..

But the command %Path% gives 'C:\WINDOWS' is not recognized as an internal..etc..

Is that OK? I thought %Path% should just print the paths without the "PATH=" part. (And Path to be for setting paths or querying if you want)

[jaclaz]

Brabant, on 02 March 2013 - 10:17 AM, said:

But the command %Path% gives 'C:\WINDOWS' is not recognized as an internal..etc..

Is that OK? I thought %Path% should just print the paths without the "PATH=" part. (And Path to be for setting paths or querying if you want)

Yes, it's "normal": %path% is NOT a COMMAND , it is a VARIABLE .
Try either of:

SET PATH

ECHO %PATH%

jaclaz

[Brabant]

I see

HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Environment","Path",0x00020002,"%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem"

in HIVESYS.INF.

And

HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Environment","Path",,"%SystemRoot%;%SystemRoot%\system;%SystemRoot%\system32;%SystemRoot%\system32\WBEM"

in AXANT5.IN_.

The code above is for including "%SystemRoot%\system" so I'll add 0x00020002 between the commas after Path, maybe they cause the wrong type REG_SZ.

>> Yes, that seems to have done it.

This post has been edited by Brabant: 03 March 2013 - 01:10 PM

[jaclaz]

Brabant, on 02 March 2013 - 03:04 PM, said:

But even so I thought just entering it would print the current path(s).

Well, then, you are insisting in the error.
PATH is a command (internal to command.com or cmd.exe)
PATH is also a (system/environment) variable %PATH% is expanded to this variable value.
http://ss64.com/nt/path.html

Try this in a command window:

Quote

SET notepadr=notepad
%notepad%
SET notepad=paint
%notepad%
SET notepad=mickey mouse
%notepad%

jaclaz