que3jxp

Well just to clarify something... The p*** poor performance is even between a 10/100 device and the server. 802.11 just compounds the slowness as it is a less efficient than 802.3.

I have a client that has a small Windows network of 1 200 SP4 server and 6 Windows XP Pro PCs. They are operating on a 10/100 network with wireless-G for some equipment. We recently set up 2 of the PCs on a wireless network only to discover that there is a serious issue with the server. The problem is that when communicating from a client TO the server, it is extremely slow. QCheck reports that speeds never exceed 1 Mbps. However, when communicating from the server to a client or between two clients, there is no problem at all. This, theoretically isolates the problem to the server. I have swapped all the hardware in the server and the problem persists. This should eliminate the hardware as a possible source. Any help is greatly appreciated.

Thanks! I will give it a try.

I was hoping that I could get it integrated at the earliest point in the install. Any suggestions?

Well I tried it and a few other things and I think that my problem has more to do with the fact that I am trying to get Nforce2 drivers to work. I have read a ton of threads on the subject, tried some of the suggestions, but so far, no go. What is the absolute most fool proof way to get the NForce2 drivers integrated into an unattended install? Thanks, Jason.

Ahhhhhhh........... Thanks!!!!! I will be retesting tonight.

I am assuming that is a yes to the quotation marks... Also, I am at work right now looking at the corporately built W2K unattended install and the thing that catches my eye with it is that they put the $oem$ folder structure in the i386 folder. What would be the benefit to this? And how would one reference the directory structure from the answer file? OR Is this just something that is unique to W2K? Anyhow, on a side note, the unattended install build by my higher-ups is SWEET!!!! Been using it for a few years. It even spans across 3 disks. I wish that I could share the secrets of it but most of the automation is actually achieved wiht custom written .exe's. Even the answer file is generated anew each time the process is started. It is made by an interactive EXE that asks for certain pieces of information. Thanks, Jason.

This is the first time that I have tried to include additional drivers in my unattended install and the first test of it failed. I double checked everyting in the guide here and nada. Here is what I have right now: Unattended section of answer file: [Unattended] UnattendMode=FullUnattended UnattendSwitch=yes OemSkipEula=Yes OemPreinstall=No TargetPath=\WINDOWS Hibernation=1 DriverSigningPolicy=ignore WaitForReboot=no OemPnPDriversPath=\drivers\000_mobo;\drivers\001_network;\drivers\002_audio;\drivers\003_video Do I NEED quotes around the OemPnPDriversPath= variable? Here is the dir structure: $oem$ $1 Drivers 000_Mobo 001_network 002_Audio 003_Video Thanks in advance! Jason.

This may not be the answer, but it sounds suspiciously like a bad or incompatible burn of the CD. A friend of mine did a normal install with a bad disk one day and skipped a (Not the same one) file and in the end the install was a failure. I would make sure that the disk or the drive or both are not bad. Good luck! Jason.

Actually, the comment for UnattendSwitch is the same as from the Deploy help file. I think that someone needs to put that it is actually NEEDED to be able to run an unattended install. When I did not have that switch, there were a lot more things than just the network and user ID wizard that were no longer unattended. Perhaps someone should have a section in an FAQ listing the absolute minimum items necessary to allow for a fully unattended install for each of the NT based Windows OSes.

I tested my more extensive answer file and all is very well. In the process, I guess I discovered a new option for the [unattended] section: UnattendSwitch=Yes This will give you the fully unattended install (I must say that it is not very well documented in the deploy help file) UnattendedSwitch=Yes This will make all but the VERY last portion of the GUI install be unattended. Having the "ed" at the end of Unattend seems to be accepted but I cannot find it documented in the deploy help file. Thanks for the help! Jason.

Ok... That is funny because the help file has no "ED" either and I managed to put the "ED" and it still basically worked except for the very last wizard. WIERD!!!! Anyhow, I am about to test a more extensive answer file so I will take the ED off the line. Thanks for catching that!!

Ok. I tried adding the following to the [unattended] section: UnattendedSwitch=yes This took care of the stopping at the EULA. But I am still getting the stupid "Welcome to WXP" wizard that asks for the IDs that you want to set up on the PC so if anyone has the switch for that, it would be great. Thanks, Jason.

Ok. It looks like I need to explain myself a bit here... I am well aware of how to configure an unattended setup. I know the switches for the winnt.exe. I know the critical options in the winnt.sif file.... What I dont know is the answer to the following........ I start the unattended install... The first file copy runs... PC Reboots... The second file copy process starts.... PC Reboots... (P.S. -- ALL of the above performs completely unattended.) PC starts in GUI for the VERY FIRST TIME... Bullet Points at the left are about to be proceeded through... BOOM!!!!!!!! The install will not do the bullet point portion of the install unattendedly. It kicks up the EULA screen and then the rest of the install is very much attended. I am NOT talking about anything after windows is fully installed, nor am I talking about that inconcequential (yet annoying) Welcome to WXP wizard (Which I am pleased to have the switch to stop now. Thanks) This is what is going on. Please stop suggesting that I go and read something that I already have read. Thanks, Jason.

That is fine and dandy that I know that, but I am going to be a lot happier when I can get past the EULA at the very start of the GUI install portion. Way before you get to that stupid Welcome to WXP screen. If that is all that switch is going to save me, then I need more help. Thanks, Jason.