tim

Did you do this?

Try giving the memory a good test. Look here : http://www.memtest.org/

Heh, I like a challenge This VBscript will read the Settings REG_BINARY, write it out to a temporary .REG file and then import it. You can amended individual bytes before they get written out. 'Initialization Section Option Explicit Const RegKey = "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams\" Const OutKey = "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams" Dim WSS, FSO, OutFile, OutFileName, RegOut, RegOutH(100), RunReg, xl, x 'Set up an instance of the WSS and FSO objects Set WSS = WScript.CreateObject("WScript.Shell") Set FSO = WScript.CreateObject("Scripting.FileSystemObject") 'Get settings REG_BINARY (should return an array of variants) RegOut = WSS.RegRead(RegKey & "Settings") 'Output should be an array of variants If varType(RegOut) <> 8204 then WScript.Quit 'Convert variant array to an array of hex numbers xl = Ubound(RegOut) For x = 0 to xl RegOutH(x) = Right("0" & Hex(Cint(RegOut(x))),2) Next 'Do your updates here like this... 'Change byte 33 (array starts at 0) to 02 (hex) RegOutH(32) = "02" 'Prepare output file OutFileName = WSS.ExpandEnvironmentStrings("%TEMP%") & "\~RegSet.reg" Set OutFile = FSO.OpenTextFile(OutFileName, 2, "True") 'Write data to reg file OutFile.WriteLine("Windows Registry Editor Version 5.00") OutFile.WriteBlankLines(1) OutFile.WriteLine("[" & OutKey & "]") OutFile.Write("""Settings""=hex:" & RegOutH(0)) If xl > 0 then For x = 1 to xl If (x mod 21) = 0 then OutFile.WriteLine(",\") OutFile.Write(" " & RegOutH(x)) Else OutFile.Write("," & RegOutH(x)) End if Next End If OutFile.Close() 'Run the reg file Set RunReg = WSS.Exec("REGEDIT /S " & OutFileName) 'Wait for it to finish Do While RunReg.Status = 0 WScript.Sleep 100 Loop 'Finish up Wscript.Quit You can run it from CMDLINES.TXT like this "CScript RegSet.vbs //NoLogo //T:10"

The NIC specific drivers only install/load when the relevent hardware is found. The only way to verify correct installaton will be to do the install for real on the target machine.

Cool, thanks for the info

You can't delete values using the regedit '-' (minus) sign? I will look into that. This will do the trick but there must be simpler way: 'Initialization SectionConst RegKey = "HKCU\SomeKey\"Const RegVal = "SomeStringValue" 'Set up an instance of the WSS objectSet WSS = WScript.CreateObject("WScript.Shell") 'Try deal with any errorsOn Error Resume Next WSS.RegDelete RegKey & RegValIF Err <> 0 then Err.Clear Set WSS = NothingWscript.QuitSave this as a .vbs file. Run with CScript.exe or WScript.exe like this: "CScript DelReg.vbs //NoLogo"

With VBscript you can use object.RegDelete Is that all you needed to know?

That would normally be a VGA driver issue. What VGA card you got? Have you got the latest driver for your VGA card? Have you got DX9.0b installed OK?

My is cmdlines.txt is like this [COMMANDS]"REGEDIT /S XPtweak.reg""CScript UsbIdle.vbs //NoLogo //T:10"The actual VBscript is here : http://www.msfn.org/board/index.php?showtopic=8341&st=440 (page 45 if you have 10 posts per page) Tested OK with a WinXP Pro SP1 install. I gonna give Win2003 Standard a go soon, should work just the same. This could be used for all sorts of interesting tweaks eh? (P.S Sorry if this is old news)

This normally means that the MBR and/or the BOOT sector are not correct. The BIOS can't find any valid boot code. First the MBR is loaded and run then, if this is succesfull, it searches for an active partition. The boot sector from the active partition is loaded and run. It is this second stage that will find and run NTLDR. Somewhere the chain is breaking down. Most likely the BOOT sector stage.

I can get hold of this patch if you really want it. It's about 3MB. Is somebody willing to host it?

Twice now I have got email from MSFN like this: I did not instigate a password recovery. Does this mean somebody is trying to get into my account? Can you trace who initiated the request?

Out of interest I have been checking out this tweak This will only have an effect on the first USB controller. There may be more controller keys. The 4 digit number at the right end increases with each extra controller or USB device. So here it is. My very first ever VBscript. I only started reading the book this morning This will go thru the numbered keys and update only the ones related to controllers. It is designed to be run with CScript (command prompt, text output). It bloody well works I tell ya!!!!

My apologies for the incorrect info. Ya live and learn

Great, thanks. BTW the 'More tweaks' link at the bottom of the page doesn't work

Ok, actually went thru all the posts in that thread. It did not have answer Anyone else please?

Sorry if this has been asked before. I did a search but could find the answer. Does anybody know of a reg tweak to disable the Configure Server screen that comes up at first logon? I wanna add this to my unatttended reg tweaks. TIA

I think I saw somewhere that there is a 64KB limit. Do a search on the forum.

Just do a normal scan. It will ask if you want a boot time scan if it can't delete anything found as spyware.

I think they are known as CLASS IDs. They are used to connect things together within the resgistry, a kind of cross reference. Yes they look a load of bollocks, and no I dunno why Microsoft chose such a long and cumbersome looking method for cross reference. There must have been a better surely?

Ad-Aware 6 will remove it with it's boot time scan. Worked for me!

Had similar questions myself. I got most of the info I needed here http://unattended.msfn.org/ Hope that helps.

Ok found this: ;Detail mode in all folder [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams] "Settings"=hex:09,00,00,00,04,00,00,00,00,00,00,00,00,77,7e,13,73,35,cf,11,ae,\ 69,08,00,2b,2e,12,62,04,00,00,00,03,00,00,00,43,00,00,00 Bit reluctant to use a stream. If ya know anything about Win32 programming you'll realise that it's not a good idea. When a stream is copied to an area of memory, it must map to the layout the program expects. If a future update changes the layout then having this reg tweak could give trouble. (Feel free to correct me, i'm no Win32 expert)

Anyone sussed "Detail view" yet? The links above did not seem to have a reg entry to do the trick. This is the last tweak I need and i'm done

I switched my brain on and got it sorted. I'm just using 2 files : cmdlines.txt and XPtweak.reg cmdlines.txt has: [COMMANDS] "REGEDIT /S XPtweak.reg" and this works! No need for the .CMD (in my case anyway). Thanks for all the quick and helpful replies!