cluberti

For an existing system with ER enabled during install, yes, you need to check the box. If you put the above code in your .sif file during install, it will all be configured properly by default (ER disabled, boxes checked, etc) and you would not have to do anything further.

The actual settings are defaults - the question is, do you want those files on your installation media? - Clock.avi is an old file from Windows 3.x/Windows 9x that was meant for specific Video For Windows video drivers to synch up video before playing. Since VFW was a standard that did not get ported to 2000 (or XP, or Vista, etc), but Microsoft switched to WDM drivers, I don't think this file has actually had a specific use for many years. VFW drivers won't work on XP, so it's a holdover for who knows why . - Yahoo.bmp is a file that shipped with IE4 and 5, and could be found on the XP CD for IE6. This is no longer used in IE, and you'll find it missing from IE7 and on Vista/2008. I believe this was displayed as part of the old Internet Connection wizard (not used since SP1, I believe, on XP). It's not needed. - Swtchbrd.bmp was used by the Novell / Groupwise client. Unless you actually use the Novell client that ships with Windows (instead of the "good" one from Novell), then you do not need this file either.

Hello ishwash, and welcome to THE forums! Hope you find what you need here, and are able to give back too.

Welcome to THE forums! Feel free to post your questions in our Unattended sections, or check out nLite or HFSLIP as well.

No problem, glad to see you here. And welcome to THE forums!

First, thank you very much if you do choose to donate, it is always very much appreciated - and welcome to THE forums!

No worries about offensive replies here, we're a very civil bunch. Glad to have you aboard at THE forums!

Fantastic - and welcome to THE forums!

Awesome that you figured it out. And welcome to THE forums!

Probably because the poll was first started in 2003???

I installed the software et launch the command. here is the link .cab file yeah i'm from france Cool, it worked. I'll need the other two files as well (they're probably much larger), but I wanted to save you the trouble just in case it didn't work .

The very first thing you must do is download and install the Windows Performance Tools Kit (x86 for 32bit, x64 package for 64bit) - choose the "complete" option during install. Next, open a command prompt, and type the proper command for the trace you'd like to execute: For boot tracing: xbootmgr -trace boot -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP For shutdown tracing: xbootmgr -trace shutdown -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP For Standby+Resume: xbootmgr -trace standby -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP For Hibernate+Resume: xbootmgr -trace hibernate -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP replace C:\TEMP with any temp directory on your machine as necessary to store the output files All of these will shutdown, hibernate, or standby your box, and then reboot to finish tracing. Once Vista does reboot, log back in as necessary and once the countdown timer finishes, you should now have some tracing files in C:\TEMP. If asked, upload or provide the file(s) generated in C:\TEMP (or the directory you chose) on a download share for analysis.

Well, I speak in software terms unless I'm in the hardware forums, so in this case I do actually mean "installed Windows+apps" == built the box.

Well, I won't get into the debate between French and French-Canadian since you may actually be from France, but I do have something you can try - we will probably have to break out the more advanced tools to get this: 1. Download and install the Windows Performance Tools Kit (x64 package for 64 bit) - choose the "complete" option during install 2. Open a command prompt, and type the following command: "xbootmgr -trace rebootCycle -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP"replace C:\TEMP with any temp directory on your machine as necessary to store the output files This will reboot your box. Once it does, log back in and once the countdown time finishes, you should now have some files in C:\TEMP. I'm interested in the .cab file, specifically.

From your problem description and the procmon log, your box spends the most time during boot scanning the registry (not sure why). Have you added or modified any software since you built the box? We will probably have to break out the more advanced tools to get this: 1. Download and install the Windows Performance Tools Kit (x64 package for 64 bit) - choose the "complete" option during install 2. Open a command prompt, and type the following command: "xbootmgr -trace rebootCycle -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP"replace C:\TEMP with any temp directory on your machine as necessary to store the output files This will reboot your box. Once it does, log back in and once the countdown time finishes, you should now have some files in C:\TEMP. I'm interested in the .cab file, specifically.

Awesome. I'm watching, because I have similar complaints/requests...

Server service is meant for INBOUND connections to your box - it might be better to figure out why you're seeing all of those inbound connection attempts, rather than to mess with nonpaged pool or to try and tweak the connection defaults in the server service (trust me). The root cause is not your client, but the amount of INBOUND connections TO your Vista box. Fix that, and you'll not see the other problems.

According to this, we go from the initial call into starting smss.exe at 10:26:11 to winlogon.exe starting to begin processing for the "Welcome" screen at 10:26:23 (12 seconds), and almost all of the time between is csrss.exe parsing the registry hives that are being loaded (this does take time, so if your registry gets "large" over time, booting WILL be slower). Winlogon takes ~1second to get to it's LSA call to be ready to accept credentials, and from there I see lsass.exe and wininit.exe starting up (meaning we're loading the security subsystem) and then services.exe kick in to start up the "delayed start" services (at approximately 10:26:26), and then the logonui.exe begins (to actually display the Welcome page). From there, we go through svchost parsing the power settings and event logging, and then we start processing group policy extensions at 10:26:36 (10 seconds later). This takes less than a second, and I see you started to get a desktop (explorer.exe) at 10:26:37, and from there everything appears to be working swimmingly. Therefore, it appears that we're parsing the registry hives for power and service start information where the largest delay is, so perhaps this is either registry bloat, or a driver that's causing the delay? It's not obvious here, and the event log stating that policy processing caused the delay is not entirely accurate - we weren't able to process policies until the registry and power scheme checks completed, and those are the things that are taking most of the boot time you would notice...

This is actually something you might want to post directly on the zune.net community support forums, because these are actually monitored. I'm honestly not sure why the podcast issue would happen, but you are correct, 2.5 is a great update to the Zune software and I have the same want for you on this .

Honestly, other than a network trace to make sure what's coming back from the file server over the wire isn't causing the problem, I'd engage Microsoft support (866-234-6020) and get a free case based on the fact that an update (in this case, SP3) caused the problem.

This is what I want. How could I get that on this 2000 machine? You don't, but the Kodak Image Viewer is available to install from the W2K CD, and it's basically the same type of app.

If you disable the Error Reporting service, make sure you also have the "do not tell me when errors occur" checkbox selected, or you'll get this pop-up. If you reinstall Windows XP a lot, add the following to your .sif answer file to disable it during install: [PCHealth] ER_Display_UI = 0 ER_Enable_Applications = None ER_Enable_Kernel_Error = 0 ER_Enable_Reporting = 0 ER_Enable_Windows_Components = 0 ER_Force_Queue_Mode = 0 ER_Include_MSApps = 0 ER_Include_Shutdown_Errs = 0

The ISO contains some of the extra support tools updated to SP3, the .NET framework, and some documentation. That's the only difference (well, of course it also includes the .exe file to install SP3, but that's a given).

Unless you're installing from a DOS boot disk, you need to make sure MsDosInitiated = 0, not 1, for starters. Also, you do not need both a ProductKey and ProductID field, one or the other will do (I use ProductKey, but that's just preference). Also, considering that your network section is just providing defaults, try just using the following: [Networking] InstallDefaultComponents = YES [NetServices] MS_Server=params.MS_PSched [NetOptionalComponents] Beacon = 0

It's saying it doesn't like the pathname (for some reason), and it could potentially be something in that remote folder it doesn't like. If you create a new folder for that user on the remote server (with the appropriate permissions) and make sure the source folder is empty of any files, what happens? Otherwise, you may have found a bug you need to report...