newsposter

thanks, just double checking because some post whore elsewhere was making a big deal about it.

is KB931756 a valid hotfix for wmp11 and the slipstreamer??

all that work for nothing..... www.driverpacks.net

On the other paw, if the 'cheap server' is really cheap, you can expect bottom-of-the-line network and disk interfaces. Usually that means that most of the functionality of those interfaces is handled at the os/driver level instead of in hardware. So in this instance, a dual-core will potentially go a long ways toward taking care of driver-related OS stalls.

ANyone know if Intellitype requires the availability of all of the stock keyboard and language layouts to function properly?

BIOS update? I've found that with Intel P4 CPU mobos, a BIOS update will more often than not reflash the microcode that is **inside* the CPU as well as the mobo BIOS. SL7xxx (espec the SL7EY) series CPUs are more effected by this than some, but the whole of the P4 family had more microcode updates than people generally know.

Seems to be working fine and a bit faster than before as well. thanks!

to refresh my memory on integrating the whole of the BtS driverpacks using nlite: Extract the BtS driver packs to a directory tree. Tell nlite to grab them all as PnP drivers. Extract all of the BtS text-mode drivers into another directory tree Expand the .sys_ to .sys, etc, etc. Tell nlite to grab all of these as text-mode drivers Carry on with other nlite goodness........ Is that roughly (or even close to exactly) close enough to get the job done correctly? Oh, and are the .ini files that are packages with the BtS driver packs of any use to nlite and if so, where shoudl they be placed in relation to the extracted drivers? thanks!!!

well. you can get started at www.blackviper.com. BV has 'matured' somewhat in the past 2 years and his 'recomendations' are more functional and useful than they used to be. Be sure to look up other opinions like theeldergeek.com for contrasting or verifying points of view. The major point being; XP pretty much works for everyone out of the box. Once you start killing services it becomes highly personalized for YOUR use and at that point, all you can do is experiment and keep good notes as you go.

:woot: (for all of those 'final festishists' out there anyway......)

cool beans, does this imply an RC3 in the pipeline?

One potential 'fix' could be as simple as having nlite always clear read-only attributes in a similar way to what the BtS Driver Base does. Has anyone tried a 'hung' .iso in a VM other than VMWare or Microsoft VirtPC? How about adding Virtualbox to the testing mix. A BITS/network driver/connectivity issue could be related to how VMWare does it's device presentation to a client OS. That we have someone reporting an OK result with VPC and failures with VMWare begs for a third test with Xen or Virtualbox. Nuhi has chased other obscure 'bugs' before and the end result was always an improved nlite.

ah ha! A glimmer of light.. Anyway, if we are integrating a root cert update KB, these KBs often head out to MSFT to verify root certs. If these things depend on having BITS up and running, I can well see the thing failing and causing a problem at either t9 or t13. It "appears" as though rootsupd.exe can fail in several ways, both at t9 (fatal) and at t13 (recoverable with a click on a dialog box) and that it's dependant on network latency to MU as well as whether or not BITS is running. Can someone with a better understanding of hotfix packaging, in particular the root cert hotfix packaging, check this out. Also might be an unintended consequence of using nlite to remove all lan drivers and then replacing them with the BtS packs. If nlite has pulled all lan drivers, then XP setup won't be able to setup and start a network, which in turn might be required for rootsupd.exe to run properly. BtS drivers (I think) don't get unpacked until after first boot/login. These might be dependancies nuhi can test for and then advise people to help them away from making bad choices......

any progress?

http://www.memtest.org/ Get the bootable cd-rom image and run it on your machine for 24-36 hours. This will at least point towards any kind of hardware (memory, memory controller, cpu) problem you might have.

......on the other hand, it takes me less than 30 minutes to go take a fresh XP 'install source', run through wmp11 integration, nlite, all of the BtS Driverpacks, and then ISO generation. testing the thing in a VM takes another 45 minutes. Burning a fresh DVD and putting it on the shelf is another 10 minutes. I just keep my install sources up to date as new releases come out and when I actually need a new ISO I run through the process. This takes a lot less time (and guarantees a good, bootable, installable ISO) than manually hacking an existing ISO and hoping for the best. BTW, my install/test machine is a Pentium4, 1.6 Gz, 512 Mb ram spining a 5400rpm disk drive. So you don't need enormous amounts of horsepower to run things properly.

actually, the 'real' improvement would be to force addon makers to use the same date format and to also force the date to reflect when the addonpack was built, not when the software was first released. Either that or add support in the addon packs for both dates, addon pack creation and software release date. The important thing is a standardized format for date. I've seen at least 5 different formats including mixed numbers/letters.

www.jrmediacenter.com

Joy of joys...... There are enough changes in there, new modules and functionality, that methinks I'll wait 2+ patch-tuesday cycles after official release before I give it a try. the rest of you can finish beta testing the thing.

Lots of retail systems (cash register) use tk still.

nice...... any chance we could induce you to make a pack with all of the addons, adverts turned off, and all but the most basic toolbars turned off?

Nuhi asked, politely, that you not redistribute nlite and that should be the end of it.

I find it hard to believe that rick is 'banned'. Try again. Why have the recycle bin on the start menu? To clean up the desktop. This hack doesn't eliminate the possibility of having it on the desktop, just provides an alternative. I think you'd be surprised how many people have used this one.

Additionally, ricktendo64 has created an awesome reg hack that moved the recycle bin to the start menu. I'd post the reg code here but it's his to post. Perhaps you can bug him for permission.

How about **adding** these tweaks: (to enable fast user switching on corporate edition installs that are not on an AD network) KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon Value NameAllowMultipleTSSessions Value TypeREG_DWORD Value Data0x00000001 (to define the windows install path as \i386 from the root of the default/system disk drive) (also requires that the user copy their i386 from the install media to this dir on the system drive) KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ Value NameSourcePath Value TypeREG_SZ Value Data%SystemDrive%\i386