BeenThereB4

Normally after a repair, you need to reinstall all hotfixes. The fixed files have been replaced by what is on the CD. If your CD has all the hotfixes integrated, however, you got the correct files back during the repair. But, the repair option does not know this and removed the hotfixes from Add/Remove thinking that you will have to reinstall them.

Use the search function - discussed long ago. Oh, and it will excede your wildest expectations, way better than the many great projects on this board. But, it's far from free. "Free" trumps everything.

Nice work, actually very helpful. I am running it from svcpack.inf. Everything worked except the user that I created did not get auto-logged on. They had a name like this "John Smith" and a blank password.

Search for free "xxcopy".

@snekul Nice post, thanks!

Yeah, it does not work. As I'm sure you noticed, Google does not know the answer. (Although it will now.) OK, here is the workaround: Start the command prompt Type: net use H: \\machinename\d (substitute your computer name and drive here) then press enter It will prompt for a user name and password. When you are done, the drive will be mapped. This is the way we had to do it back in ancient times!

GreenMachine has a long and proud history here of helping people for free. It is extremely unlikely that your email address will get away from him. There is no sense trying to insult or cajole him into answering. As others have said, only a very major life problem could explain his absence. After all, he has a great deal of his life invested in this program, years actually.

It might work well to start with Nlite and remove almost everything except Internet Explorer and the lock down what's left as needed.

If you still think that the modern bios cannot be hacked and overwritten, here is one of the tools that circulates in the hacker community: Scroll down on this page for FirstBIOS Editor

Has anyone determined the best stripe size for Raid 0 using the SI3112 for just average business computer use? What about the cluster size? Any tips for that from experience? I did search, but did not find this. I know that it's not as safe, but these drives are backed up every day and have nothing critical on them besides.

Put in both of these: UpdateInstalledDrivers=yes DriverSigningPolicy=Ignore

Already answered in this area, look at the topics!

You might try the script that I posted here: WUS Script Note that it has to be edited to point to your server --- look for the note in the script.

FOXCONN "K7S741GXMG-6L" SiS 741GX Chipset Motherboard For AMD Socket A CPU -RETAIL Model# K7S741GXMG-6L Item # N82E16813186029 Specifications: Supported CPU: Socket A for AMD Athlon XP/Athlon/Duron/Sempron Chipset: SiS741GX + 963L FSB: 333MHz RAM: 2x 184-pin DIMM for DDR 333/266 (Max. 2GB) IDE: 2x ATA 133 up to 4 Devices Slots: 1x AGP 8X/4X, 3x PCI Ports: 2x PS/2, 1x COM, 1xVGA, 1x LPT, 6x USB2.0(Rear 4), 1x LAN, Audio Ports Onboard Audio: Integrated 5.1 channel AC97 (Realtek) Onboard LAN: Integrated Fast Ethernet (10/100) MAC + PHY (Realtek) Onboard Video: Integrated SiS high-performance graphics Form Factor: microATX The board offered to you does support Sempron ***************************************************************** Elite K7S5A DDR motherboard for AMD® K7 socket A processors with 266/200 MHz FSB Integrated with the most advanced technologies: Suspend to RAM Keyboard power on Hardware monitoring LAN/Modem wake up PROCESSORS 462 pin Socket A supports the AMD® K7 processors Athlon XP / Athlon / Duron processors Your current board does not support Sempron

Play around with the dir command until you find a short name that works. dir atalog??.? dir atalog>?.? dir atalog>?. If you still can't get it try going to the directory above it. Change to the C:\windows\system32\config\systemprofile\local settings\temporary internet files\content.ie5 then type: attrib -r -s -h 4L1XJE7O\*.* /s press enter then rd 4L1XJE7O /s/q

Just a few notes to add at this point. 1. You cannot usually flash the boot block as doing this requires applying a trigger voltage to a certain pin on the flash memory chip. This is so only the factory can program or erase the boot block. In other words, the boot block is a special hardware protected area of the flashable chip. There are exceptions to the way the boot block is handled. Some bios chips use a protected backup scheme for the boot block, so that it can be updated by the end user. But, in this case, it will revert to the backup if the update is invalid. 2. The remaining area of the Bios Flash Memory chips is a passive device, many are not designed to be able to detect what is about to be written to them and cannot reject it if they don't like it. Some attempt to protect themselves by requiring a "Digital Signature" in the new bios. This can sometimes be circumvented by hacked flashing software. Most however can be set to not allow any flashing at all, in the bios settings, to protect against viruses that overwrite the bios. Some have a jumper on the motherboard to protect against unintentional flashing. Seems like we never got all the details that would be needed to come to any firm conclusion. There is a lot more to the subject than one would expect.

Try this: 1. Start a command prompt 2. Change to the C:\windows\system32\config\systemprofile\local settings\temporary internet files\content.ie5\4L1XJE7O Directory 3. Type dir /x /a and press enter (look carefully for the short file name of the problem file) 4. type attrib "short file name here" -r -s and press enter 5. type del "short file name here" and press enter

You better check with this "IcemanND" guy that they found. He seems to have a handle on the problem.

This is thought to be part of "Hacker Defender" which is a rootkit -- not good!!

You might want to remove KB887742 from non-critical updates now that you have it included in critical.

Possible causes: 1. bad memory 2. overclocking 3. bad driver 4. bad motherboard 5. bad processor This is more or less the order to check. As always YMMV.

You must add the actual drivers yourself. I use FilesCD\$OEM$\$1\Drivers\SI3112 and place the actual drivers there. Modify winnt.sif with: [Unattended] UnattendMode=FullUnattended OemPreinstall=No TargetPath=\WINDOWS OemSkipEula=Yes Hibernate=0 UnattendSwitch="Yes" OEMPnPDriversPath="Drivers\si3112" For some reason, I'm able to integrate drivers like this but you should set OemPreinstall=Yes Here is what I have in xpcreate.ini: DOPATH=NO DOSATA=YES DOSVCPACK=YES DRIVERDIR=$OEM$\$1\DRIVERS I know this works because I just used it within a few days.

It might be that these people have disabled the Computer Browser service on all their machines. People with real servers on their network or with this service running might not have a problem.

Compare It! - Grig Software File Difference Command Line "C:\Program Files\Compare It!\wincmp3.exe" %1 %2 File Merge Command Line "C:\Program Files\Compare It!\wincmp3.exe" %1 %2 Merge v6.5 for Windows - Araxis Ltd. File Difference Command Line "C:\Program Files\Araxis\Araxis Merge 2001 v6.0 Professional\compare.exe" %1 %2 /wait /max Usage compare [/? | /h] [/wait] [/aN] [/swap] [/max] [[/titleN:"<NthFileTitle>"]...] [/2 | /3] <firstFile> <secondFile> [<thirdFile>] [<mergedOutputFile>] File Merge Command Line "C:\Program Files\Araxis\Araxis Merge 2001 v6.0 Professional\compare.exe" %1 %2 /wait /max Tip: You may also want to disable the confirmation to close Merge when file comparisons are open. Go to the 'View' menu, select 'Options', select the 'Application' node and un-check 'Confirm application close when file comparisons are open'. WinMerge on sourceFORGE.net File Difference Command Line "C:\Program Files\WinMerge\WinMerge.exe" %1 %2 File Merge Command Line "C:\Program Files\WinMerge\WinMerge.exe" %1 %2 BeyondCompare - ScooterSoftware Inc. File Difference Command Line "C:\Program Files\Beyond Compare 2\BC2.exe" %1 %2 /readonly File Merge Command Line "C:\Program Files\Beyond Compare 2\BC2.exe" %1 %2 Tip: Uncheck the checkbox on the initial startup dialog if you want BeyondCompare to go immediately to the file comparison view. WinDiff - Microsoft WinDiff.exe is file difference program supplied by Microsoft with various development tools. It does not handle merging and it's features are limited. File Difference Command Line WinDiff.exe %1 %2 File Merge Command Line None.

Right on GreenMachine, your CD is the base for mine. Oh and I believe that OEMPnPDriversPath does work because the drivers that I integrate follow your procedure.