Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by Spheris

  1. ;Speed up NTFS


    "NtfsDisable8dot3NameCreation"=dword:00000001 = dangerous and breaks regression and some ntfs regression compatibility with non 2k/xp certified and ntfs aware applications

    "Win31FileSystem"=dword:00000000 = safe

    "Win95TruncatedExtensions"=dword:00000001 = dangerous and breaks regression compatibility only for use with 2k and xp certified apps

    "NtfsDisableLastAccessUpdate"=dword:00000001 = safe

    ;RAM usage tweaks

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

    "DisablePagingExecutive"=dword:00000001 = safe with non ati video drivers

    "LargeSystemCache"=dword:00000001 = safe with non ati video drivers

    "IoPageLockLimit"=dword:1bf00000 = unneccessary with the kernal update 820128 and can cause memory starvation in low/mid memory systems under 1gb

    "SecondLevelDataCache"=dword:00000100 = safe

    ;Prefetcher tweak

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters]

    "EnablePrefetcher"=dword:00000003 = unnecessary, set by guisetup to default, interloks to ntfs journaling and index manager = do not disable it

  2. sfc is a system control file and service

    ties to the windows file protection database, indexing service and ntfs hooks

    to replace non compliant and potentially damaging mismatched dll and support files in the windows 2000/xp and athena systems and will be replaced/integrated with the winfs files system in blackcomb and later releases.

    it can be disabled for what its worth but can and does cause the following side effects

    1:) nulls any protection possible against forcible insertion of a mismatched or altered file into your system, either by setup installer or by forced entry(hack) from external source

    2:) breaks and errors with the indexing service and causes minor errors in catalogue files associated with windows components and hotfix installers intermittently

    3:) causes your wife to make you sleep on the couch because you f***ed up your install and she had plans to do some cruising at porn sites/amazon to do shopping etc...this is the one that seems to cause the most trouble for people. Use all caution :)

  3. its not a hotfix at all, which is why you are having the problem

    just an update and addon component, nothing more or less..just like dx 9

    there is no slipstream mechanism for it either outside of the svcpack install route and it is that way by design for support reasons

  4. as it stands right now

    all the type ones are working in the svcpack dir

    only 2 of the type twos are verified for a non running system



    the mdac remains problematic as some of the dlls do not register succesfully from a guisetup

    best to be installed at guirunonce

    as for unpacked dlls, ntdll is the only existing one for now

    the rest accounted for in the current hql list are compressor pack compatible

    but ntdll is called at txtxmode

    so if its compressed, it will default to the normal one and not unpack as it is in memory at runtime.

  5. as an alternate, if you really feel the need

    you can try the inf from the unpack, but bear in mind..it will not load the additional options and will break the component add/remove in the shell. There is no fault in the installer, but there is no regression mechanism built into it to allow slipstreaming. only side streaming as its inf does not correspond to the txtsif

    unpack to dest dir

    cmdlines.txt with the update as executable with absolute path setting in the line directly before it.

    you have a 50/50 chance of bsod and 75/25 of breaking the components shell.

    But have fun anyway.

  6. Box, the hotfix packages must remain in svcpack for the reason that some of the component changes were not only binary based but in a few cases were also adjustments,compensations in the registry to alter a behaviour, such as with the compile error catalogued - the cache would discharge from kernal before compile was finished and would require refresh of all core code, slowing compiles to a crawl in large memory situations.

    the type twos are all classed as unreliable outside of their packages because the dlls are forced into the register mode, they are not natively self registering in most packages. They may or may not register even by command from the setup gui itself as we have found as some of the mods done to the code itself do not always respond to the guisetup protocol to call api/dll self registration.

  7. The advanced networking package is a side stream upgrade for the internal ip6 support and adds tentative P2P support for upcoming server products for integration. It has not been regression tested and will not be offered except as a stand alone upgrade to support those two technologies in windows xp but will be fully integrated supported in both the athena and blackcomb releases.

    ip6 support is built into the base windows xp installation, enabled by command prompt switch and unless the p2p option is necessary for developer purposes. is an optional only. Not a required to have ip6 functionality

  8. There is no known upper limit in the icon cache mechanism in xp (although 2k has a threshold of 4096)

    However, there is the same problem with it as caching too many fonts within a system in that it can and will go into memory starvation dependent on loading of the core kernal and available memory to processes

    rule of thumb 1024 icons per 512 mb of memory is best practice.

    Good luck maz

  9. We got svcpack working last night with two small hitches

    but got them ironed out

    Also went through the orca and found a lacking in the reg injection that needs to be addressed, but did get some time with someone at engineering and went through the internal references and best cases

    guirunonce is seemingly the most stable and does offer an advantage over the inf, which is that as sif, it does the loading independent of user profile (and apparently is recommended if slipping any last minute or trouble prone hotfixes into the system before first login)

    Will send you the detailing and you can test it out and give me your thoughts and feedback on it. We did find the component that is breaking the printer, but it cannot be worked around as yet

    apparently an advpack installer module is the problem but cannot self register without the advpack infs force of it. We spent a good half hour making fun of the IE team for that one, but then another banging our heads on trying to work around it with no luck short of a wise installscript

  10. Aarons thread, I'm going to expand on a bit

    In a slipstreamed disc, the files are hard coded with the fixes detailed. But as an integrated install it will appear to Update as any normal SP1 disc for the same reason SP1 shows as it does.

    The markers in the registry that are used to ID updates and hotfixes aren't there because they are not needed and no mechanism provided at install time - that is why the opk method includes the instruction to slipstream and force the hotfix installers to enter those entries and use the mechanism that allows qcheck and WU to see the hotfixes.

    I'm going to throw a question out before we go further with this

    If the idea is to make a slipstreamed disc or to create a hotfix enabled streamline of their installs as separate entities.

    either can be done, neither have any benefit functionally over the other. But both require different approaches and Aaron/medic and I will do our best to accomodate the general concensus on how to approach it

    but we need a clear answer.

    so the answers on this thread should go as:

    1: Slipstream compacted (updated files and cats only) no hotfix accompanying them

    2: Mixed approach (same as above but with the hotfix packs to enable qcheck and WU to tell you what you already know is there)

    3: Any reasonable alternate, you would like researched. Or to propose

    I want this thred kept clear and clean, we can start discussions and debates over ideas in following threads. But lets keep this one to answers only on direction, so we can get a clear view and get on with making it happen.

    Fair enough?

  11. everything discussed here so far (barring warez) IS in bounds


    integration scripts

    the documentations used and their references

    the infs (although medic and I need to talk about the tags he's modifying them with as they are lifted from some of the internal infs) not a big problem but say if he issues a client a custom disc, he would have some liability in the alteration of code for distribution aftermarket.

    dx9 is questionable as it uses a hacked setup

    I'll get you the proper OPK installer today

    .net was questionable but I did impress that it is an internal intitiative and this sort of thing only will help drive its adoption among the "working" IT community. so that gets the worriers off the back for a time.

    the svcpack method is documented and not restricted for copy and usage so no foul there.

    Aaron, 99% of everything here is perfectly good, only the dx and medic and I noodling with slipping the net runtime was iffy.

    You keep rolling, I'll get you the missing dx component, it is an opk item. But that's easy enough to make a workaround that keeps everyone happy and above board.

  12. Not at all, just that some of the mechanisms that are being discussed (alteration of .net to slipstream and that lot) are out of spec and was gently reminded that those things are not covered in support calls, which sometimes they turn into when people try these things without really having a clear idea.

    The rest is just rumbling to the effect, don't you have better things to do :)

    I do, but really enjoy watching all this and bringing some of those ideas back to the table here. I see it as a sort of GPL type experiment/collaboration and those always are good

  13. I have some good news for the lot. On the slipstream and DX9/NET etc

    But I'll be passing it along to you. We'll get it together. But a quasi SP2 is a lot more possible now than the coming summer.

    Side note:I got a tap on the shoulder about my activities here lately.

    Which means I'm not the only one from redmond here. Be extremely judicious about some of the activation and warez talk in the threads, Aaron, just good advice.

    But apparently, they're only watching and not terribly thrilled with some of the help and insight into some of the more vague mechanisms (particularly .NET) I've been giving. Go figure, until I'm being paid hourly for my free time.

    They can keep watching and tap all they like. :)

    talk to you soon

  14. Oh dear.

    Hands Aaron the icepack.

    I'll have a revised procedure for the rollup install to you in a little bit

    in the meantime, do not slipstream the files to i386 until I get that to you as they will blow the install out under uncontrolled conditions

    (some of the files mismatch out of the driver and sp1 cabs (known problem)

  • Create New...