Jump to content

[TiLT]

Member
  • Posts

    15
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Sweden

Posts posted by [TiLT]

  1. Vastly improved networking, brilliant memory management, consistently better performance on newish computers.

    Application startup time has to be seen to be believed.

    I really like how the thread priorities are set-up off the shelf too. In XP it was pretty much impossible to limit background processes from hogging CPU (no matter what settings you applied), but in Vista background processes really are background processes.

    I didn't even look at Vista for over a year because of all the bad press. I decided to try it in preparation for SP1 and I've been very impressed. It's really surpassed my expectations. I'm glad I wasn't around at RTM to be disappointed.

  2. use Windows\Setup\Scripts\setupcomplete.cmd to "reg add" runonce.cmd to the HKLM RunOnce

    runonce.cmd then sets the HKCU RunOnce cmd that I want via "reg add" and reboots via shutdown /r.

    I run all .cmd with hidec and they work fine that way.

    Edit: You may be able to set the HKLM RunOnce key at another time in your unattended.xml too, but that's how I did it since I was using setupcomplete.cmd already. Hidec also works fine for batch files executed from your unattended.xml

  3. md c:\mount

    imagex /mountrw xxx.wim 2 c:\mount

    the 2 there says which image in the wim to mount. i can't remember how to list them, but i usually need #2.

    make your changes, then imagex /unmount /commit c:\mount

  4. woot! got it working. HKCU Run & RunOnce were being obliterated before first logon (even when I locked down permissions on them beforehand), but HKLM RunOnce stays intact.

    so I used HKLM RunOnce to run a script that adds a key to HKCU RunOnce and then reboots.

    I needed to use both because certain pesky registry tweaks will only "stick" if run from HKCU, while others only "stick" when run from HKLM.

    Had to combine setupcomplete.cmd with the RunOnce keys to finally set all the keys I wanted.

    specialize, oobeSystem, and even auditUser passes were all (mostly) worthless.

    (this was all with SP1 RTM btw)

    P.S. - Another thing I noticed early on, you can't use regedit to import the Run\RunOnce keys, they won't be written. Instead I used reg add or regini. I never tried reg import.

  5. Maybe we can pool the data here for easy addition to vLite?

    I'll start it off. The patches are for enabling

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

    "TcpNumConnections"=dword:X

    version 6.0.6000.16627 x86

    7F 7A -> [@ 0x140]
    A9 91

    0F 87 8B 00 00 00 -> [@ 0x3F4B9]
    90 90 90 90 90 90

    version 6.0.6001.18000 x86

    28 75 0E -> [@ 0x140]
    40 9F 0D

    0F 87 8B 00 00 00 -> [@ 0x4C59E]
    90 90 90 90 90 90

    EDIT: Well, I don't have SP1 installed yet...but if it really does have the same driver verification that x64 has then you can consider it a big NM to this idea.

×
×
  • Create New...