cluberti

ADMT and USMT (both Microsoft tools) should fit the bill. http://www.microsoft.com/technet/prodtechn...278a277537.mspx

Not a problem. Keep us updated .

Probably a silly question - but is there a command.com file on the network image root? Make sure there is a command.com in the path your PXE boot is connecting to, or you'll get this error. Could be something else, but it's definitely looking for a command.com file somewhere .

This has been discussed before on the boards - you may want to search for "Marvell RIS" either here or on google. Basically, you're going to need to rewrite the .inf file to get it to work, and it isn't pretty. Marvell NICs are widely regarded as the absolute worst NICs to use for RIS, unfortunately.

Already answered. I know you said that you couldn't use Linux in your environment, even Novell's - is this a secure site that cannot be changed, or just a mindset set on Microsoft/Novell at the higher levels? Unless it's a secure site, it seems a little silly not to use Novell's Linux in your environment, but that's just me .

No, clean HDD will work just fine, as would using the old.

The problem is that the novell client replaces the default msgina.dll with it's own, and it lacks the winlogon hooks to look in \\dc\netlogon\default user - so yes, it's (sort of) by (a lack of) design. This is an issue I've run into many times, and there is no workaround short of not using the novell client. The only other thing you could do is prepopulate the default user profile on the machine with one from your network after installation (either RIS or CD), but you'd need a script that would do this on each machine (either runonceex or domain admin login script). This also won't help you on existing machines, but it'd at least be a workaround for new ones. Have you considered migrating your network servers to Novell's Linux? It would negate the need for the netware client.

For those of you bashing Microsoft about the latest vulnerability (and yes, we do deserve some of the licks, but not all): The patch has been available for a few days, but it needs to be tested in over 20 localized languages, and by certain third-parties before it will be released as stable to the public. Everyone want hotfixes released right away, but no one wants the hotfix doing anything negative to their systems - so you want a hotfix coded, tested, and released in 24 hours for what amounts to 4 different operating systems in over 20 different languages, on millions of hardware and software configurations? I think that's being just a wee bit overzealous here - I think it's important to remember that Microsoft has a responsibility for the hotfixes and patches it releases, not to mention the publicity hit we'd take if a hotfix wasn't released in top form. What would happen if a hotfix was released a week ago, but broke 10% of systems out there (that's millions of PC's and servers)? We'd be bashed for releasing an untested or unstable hotfix - perhaps you see the conundrum? The hotfix will be released when it's tested and stable, and won't cause more harm than it fixes. I know the workaround isn't the best, but at least it's a workaround .

Have you considered configuring the PC to do a complete memory dump, not automatically reboot, and then configure driver verifier? This could just be a hardware or PSU problem, but if it's an OS problem the aforementioned steps should help you catch the culprit. To turn on the verifier, type "verifier" in the run box or at a command prompt, and select "Create Standard Settings", then "Automatically select unsigned drivers", then select drivers from the list that you'd like to watch.

You don't need 98 installed - just start the install with the XP Pro disc, and provide the Win98 disc when prompted.

System restore?

Running perfmon and poolmon should tell you what is using all of that memory - sounds like a leak in something running in the winlogon.exe process. Do you perchance have Citrix or Symantec PC Anywhere installed? The only reason I ask, is we only see winlogon leaks when a program has replaced the default gina with it's own (which both of the above do). There are others, but those are the ones I see the most.

Well, I can't tell you exactly WHY they're happening without of a complete dump, and even then I can only see stack traces (so if it's an app, you'll have to track down the problem with the vendor). Make sure your paging file is on the drive Windows is installed on, and it's at least RAM+50MB to get a complete dump (otherwise it'll truncate and be corrupt). Sorry I can't help you further, but whatever you installed is causing your graphics driver to fault (and bugcheck the box). What exactly does that software do ?

What type is this modem exactly? I'm guessing you're going to be out of luck, but if you can give me any more info on the modem itself I can at least look it up.

I don't like to do this, but I'll bust out my "credibility" stick - I work for MS Support at the highest levels in Core OS platform support, and I can tell you that NOD32 uses almost as much memory as the absolute worst, McAfee 8 (although SAV 9.x and older are right behind - SAV10 with the latest update runs entirely in paged pool, which is much better). NOD32 installations can have serious issues in nonpaged pool usage on "power-user" and server-class systems, that to my knowledge have not been fixed for quite some time. It should be OK on a 64bit system (where nonpaged pool is now 128GB rather than 256MB or 128MB), but it's still not a very well-written product, memory-wise. And yes, it does install to "program files (x86)" by default, meaning it's still a 32bit application.

You may want to run drwtsn32 and change the dump type to full, but I can tell you from your minidumps that the reboot isn't really a reboot - it's a bugcheck (BSOD) STOP EA, and it looks like the culprit is the file ati2mtag.sys, AKA your video driver. All three dumps have different functions that are causing your crashes, but all have hal.dll in their callstack, which may mean that the problem that caused a GRAPHICS_DRIVER_FAULT may be hardware issues as well - just an FYI, if the driver update (or, downgrade, if you're using the latest) doesn't solve it.

Install UPHClean (http://www.microsoft.com/downloads/details.aspx?FamilyID=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en), and it will tell you what it had to force closed to get the user to log off or the machine to shut down in the event log. Just so you are aware, these are usually caused by antivirus/antispyware programs or (surprise) print drivers...

Are we talking about sharing it over the network sans PC, or when connected to a PC?

Well, I'd strongly suggest starting with your RAM (with hardware failures, it's often the culprit - so it's at least a place to start). http://oca.microsoft.com/en/windiag.asp

Well, if it works in x32 but not x64, it could be a driver incompatibility, or a hardware incompatibility. Have you made certain that your chipset and modem drivers are WHQL-certified Windows x64 versions?

There is a very good article on the Microsoft site regarding STOP: 0x0000009C errors: http://support.microsoft.com/?kbid=329284&sd=RMVP Basically, your processor balked at a command it was given, and these are almost always caused by a hardware error. Perhaps the software you installed exacerbated a pre-existing condition that you didn't notice otherwise, or perhaps the two issues are completely unrelated and your hardware problem is just a massive coincidence with installing software (hey, it does happen). If it's a hardware problem, it is going to be in the processor, the system bus, or the memory subsystem (controller or RAM). I'd suggest going back to a known-good state with your operating system, then use a memory tester (such as the one we provide, http://oca.microsoft.com/en/windiag.asp) to make sure the RAM is OK. From there, a good hardware tester that runs from a boot CD or floppy would be your best bet to make sure the hardware is indeed OK, or if you have a problem, point out the problem's origins. Good luck - sounds like you may need it .

I'm not the best with flags, but it looks like your nationality is Polish? Perhaps you could post this again using the subject line - Help, need polish translation of unattended.msfn.org? Sorry, but I only speak German, English, and Italian...

All of the installation-specific information is in http://unattended.msfn.org under the Intermediate Users section - take some time there, and you'll find all of your questions have been answered very clearly there. As to the other questions, simple searches of the forums will gather the answers you need.

Windows keeps a few log files of the setup process, the most important of which are setuplog.txt and setuperr.txt. Edit: sorry, should've mentioned that these are in the root of the Windows directory.

I suppose it's possible to install WMP on Win9x by also copying out all of the .dll files that WMP 10 relies on in Windows XP, but you cannot do that for a Win2K machine without doing some serious surgery and disabling the SFC as well (as far as I'm aware, all attempts at doing this on Win2K have failed thus far). WMP 10 is pretty reliant on Windows XP system components, just as WMP 11 will be quite reliant on Vista (and possibly back-ported to XP) system components.