Jump to content

jdeboeck

Member
  • Posts

    375
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Belgium

Posts posted by jdeboeck

  1. look in the nvidia driver inf, if it goes to an nvidia app, the reg key must be there

    it should be under a clsid for the desktop, and it won't have the "digital display" in the registry because its in a shell extension dll, like winzip. The winzip context menu aren't in the registry either, they're in a dll

  2. AccessOpt = On Accessibility Wizard? Nope, acc wizard AND cursors

    Dialer = On Network Diallers??? nope, its the phone dialer

    OEAccess = On Outlook Express? just the shortcut to it

    WMAccess = On Windows Media internet accessability? Nope, its the shortcut to win messenger

    why don't you just look em up yourself

    findstr /i /c:COMPONENTNAME %WINDIR%\INF\*.INF

    that should give you the filename where the component is defined. Look in there for more info.

  3. uxtheme.dll is the dll for xp visual styles, or at least one of them. It is is built to allow only MS-signed visual styles (which means just luna) and that's why everybody wants a patched version of it. A patched uxtheme.dll will display any visual style, just like styleXP... That is all patching uxtheme does tho

  4. @davidyang:

    The filenames will not be hard-coded anymore, so the >> issue will be fixed. this was just a typo, it doesn't matter if files with ,3,3 flags in txtsetup.sif are removed or not.

    I didn't know the filesystem was case sensitive, I'm pretty sure I have a working CD with all lowercase filenames. Furthermore, Ntldr is not touched by the batchfiles...

    Installing afterwards works for a lot of components, but not all. Some have their files copied by the component inf, but have the dll's registered by syssetup.inf... Doing it 'at a later time' will only copy the files, not register the dll's... so there's no easy way to do it. Just remove what you don't need, and if in doubt don't remove it.

    make an sp2/rc1 version of the batch files as sp2 may be out for upto 3 months

    only if you promise not to use them on a longhorn alpha :)

  5. Does it say on my site to delete the .cab files yourself?

    Anyway you messed up. You're getting errors because you already ran the batchfiles. Restart from a clean cd.

    run it in root of XPCD local copy
    batch file in the root folder

    the folder one level up from I386

    Put batchfile in CD root, next to i386

    and that's just from the last ten replies, it should be clear where the batchfile must be placed

  6. @hajj: Read the site for complete instructions. Put batchfile in CD root, next to i386. Make sure source is not readonly. Run batchfile. If there are errors, you did one of these things wrong. Remember there is no need to mess with anything yourself, not even in winnt.sif. All you have to do is run the batchfile.

  7. @hajj: if you set messenger and msnexplr off in winnt.sif, the files won't be needed. However just removing them will cause errors when copying files.

    moviemaker 1 and media player 8 are not installed by XP SP2 RC1, I mentioned that the files were not removed from the source. This means they take up space on the cd, but are not in dosnet.inf or txtsetup.sif... It is possible the slipstream process will be cleaned up, but SP1 had similar issues (ati drivers in i386 among others, which carried over to SP2)...

  8. my guess is they are a decimal representation of three bitflags (1, 2 and 4) but I have no idea what they would represent. What I find even stranger is why the two entries that do not have an INF file associated, have one field less in the comma seperated line; and why they don't have to be hidden ...

    NtComponents=ntoc.dll,NtOcSetupProc,,4

    WBEM=ocgen.dll,OcEntry,wbemoc.inf,hide,7

    Display=desk.cpl,DisplayOcSetupProc,,7

    Fax=fxsocm.dll,FaxOcmSetupProc,fxsocm.inf,,7

    does anyone know how this works or what ntcomponents and display actually do...

×
×
  • Create New...