cluberti

In the service properties, is the Workstation service configured to run services.exe? Also, did you modify services.exe in any way? If you create an OS based on a real SP4 source and remove the same services, do you get the same result?

- Create a folder on the C: drive called "websymbols" (without the quotes) - Click Start > Control Panel, and open the "System" applet - Click the "Advanced" tab - Click the "Environment Variables" button - Under the "System variables" box, click the "New" button - In the "Variable name:" dialog box, type the following exactly as shown: _NT_SYMBOL_PATH - In the Variable value:" dialog box, type the following exactly as shown: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols - Click OK 3 times Then try again.

sfman32.dll is related to your Sound Blaster software, so reinstalling/repairing that should resolve the issue.

When do you receive this error? Can you perhaps post a screenshot showing this occurring?

If something is causing a runtime error in IE, it's likely because a 3rd party add-in is trying to load and is failing - IE should not have this problem when opened multiple times by multiple users, as it is a separate process per user. The only way to be sure what BHO or COM add-in is causing this, we would need to see a process dump of Internet Explorer's iexplore.exe process crashing: 1. Please install the "Debugging Tools for Windows" from: http://www.microsoft.com/whdc/devtools/deb...installx86.mspx 2. Create a directory called C:\adplus 3. Open a command prompt and change to the directory where you installed the debugging tools. By default, this is "C:\Program Files\Debugging Tools for Windows" 4. Type the following command in the command prompt: cscript adplus.vbs -crash -o c:\adplus -quiet -sc "C:\Program Files\Internet Explorer\iexplore.exe" 5. Internet Explorer should open and crash, and another cdb.exe window (minimized) should open and close Once the crash dump has completed, you should have new folders and files inside C:\adplus - including a file with a .dmp extension in the "Crash Mode" folder. That file can be opened in windbg and will tell us what is causing the IE process to crash. Myself or anyone else here with debugging experience can look at that and tell you what is happening.

Is the SIS Groveler service running on the server hosting the RIS image? What the error message says is that a file (or files) that were supposed to be copied to the machine are actually just links, and are stored elsewhere on the RIS volume (reparse points created by the SIS groveler). If your account doesn't have rights to the location where the reparse point is directing the file copy to, or the SIS groveler service is not running, you will get this message.

http://www.magicaljellybean.com/keyfinder.shtml It can be grabbed from the registry manually too, but this is a personal favorite and it's easy to use.

The error message you see maps to "STATUS_ILLEGAL_INSTRUCTION", so I'd say it's likely that something else is passing a parameter or command to lsass.exe that is causing lsass.exe to bugcheck. I'd say do a thorogh virus sweep and spyware sweep (again) in safe mode, then reboot and run sfc /scannow to make sure that your system is using files that checksum from dllcache or the Windows CD, and see if the issue continues.

Well, if it sees both processors in XP and not 2003 (which is really odd if you've got a multiprocessor kernel installed), perhaps the vendor has a BIOS update that can help?

Go to the device manager and see what Computer type your system sees - if it says uniprocessor PC, you'll need to change it and install the Multiprocessor PC type.

If you are to get event log messages when a machine dumps, you need to make sure that write an event to the system log is checked in the startup and recovery settings, as well as at least generating a kernel dump. If you are set to small dump (or your crash was a STOP 0x1A), you are likely not going to get anything written to the event log.

Try the following commands: regsvr32 /u "%windir%\system32\itss.dll” regsvr32 /u "%windir%\system32\itircl.dll" regsvr32 /u "%windir%\system32\hhctrl.ocx" regsvr32 "%windir%\system32\itss.dll" regsvr32 "%windir%\system32\itircl.dll" regsvr32 "%windir%\system32\hhctrl.ocx" After a reboot, try a .chm file again. If any of the above commands fail, you may have to do an sfc /scannow with the XP installation CD in the CD drive.

"Downgrade"?

Well, a stop 0x21a can occur when a critical system process is terminated, for whatever reason - and the processes that can cause a stop 0x21a specifically are unexpected terminations of lsass.exe, csrss.exe, and winlogon.exe. Which one of these processes terminated (you should've seen that info on the bluescreen)? The best thing to do, especially if you're seeing this frequently, is to configure for a complete dump, set the page file to RAM+64MB on the same partition Windows is on, and the next time the issue occurs, you should get a memory.dmp file in the Windows directory that can be debugged with cdb or windbg to determine the root cause.

I would have to say that I only ever install Windows when I am either installing on new hardware, or installing a new version of the OS (as is the case with my install of Vista x64 recently).

Note that the version of Windows that shipped with your Dell is only legal (at least in the US) when installed on said Dell - moving it to other hardware invalidates the license (not that it matters much now - Windows 2000 is in extended support).

You may find this helpful: http://www.realtimesoft.com/multimon/resul...Type=SearchCard

There are known issues when using WinPE in RIS if you don't use the RAMDISK method - you can have a few users on it at a time, but it will cause clients (or even the RIS server) to hang if you don't use the RAMDISK with enough users attached at any one time. WinPE wasn't ever meant to be used this way, so that's one of the many reasons the RAMDISK functionality was built into 2005 .

Are you certain that's not exchange 5.5?

I've actually seen this happen in the order you described when running real-time SAV scanning (rtvscan.exe or doscan.exe) at the same time an image was uploading. The SAV real-time scanning of the incoming files screws up the SIS groveler, causing retries (and thus riprep starts failing). If you UNINSTALL (not just disable) any real-time A/V scanning on the system, that may resolve the issue as well.

Are you booting into WinPE from RIS to do this, or simply using RIS to launch the text mode setup? If you're using WinPE (and not using the RAMDISK method), this sort of thing is known to happen.

If OemPreinstall=Yes, then you should consider using the TEXTMODE method of getting the drivers working in RIS, rather than integrating a whole driverpack (I love Bashrat's driver pack, but not for RIS - it doesn't always work as expected). If you need help, let me know which driver set you've downloaded and I can take a look and tell you what surgery you'll need to do to get it to work from the TEXTMODE folder. I had the same problem with Adaptec 1200a and 2400 controllers, which was resolved by editing the driver's installation files. This is likely going to be fixed the same way.

Open Task Manager and see if it shows two processors? Or open device manager and see if your computer type is uni or multiprocessor?

Are we talking about slowing the actual boot process, or slowing the logon time during an RDP or Citrix connection to the machine?