cableguy_uk

what would we do without these driver packs LOL!! nice guy

Thats a shame, i thought seen as it was talking to the RIS server had grabbed an ip via DHCP from boot. And at that early stage its transferring files and communicationg with it that i could somehow include a share on the server that the host pc could see. Thanks anyways...

Just wondering if this can be achieved. Instead of having OemPnPDriversPath="drivers\chipset\intel;drivers\chipset\nvidia" Have something like this OemPnPDriversPath=\\servername\path\drivers\chipset\intel" Thereby speeding up the installation as you wouldn't have to copy the driver folder onto the pc. The PC would then check the server for the correct driver. Can anyone shed any light on this.

does anyone know if ForceHALDetection would be the answer

okay everything works great, but every now and then i get an Hal.dll error, it happens just after second reboot when files have copied over just before the setup screens. If i restart the RIS install or even restart a CD based install it installs fine second time. I can only put it down to the fact that PC's straight out the box has a second partiton of about 10meg EISA or maybe with a backup bios on it, and its not getting rid of it for some reason. If the unattened install is installed on a cleanly formatted pc then no probs...clean install. But its the new pc's straight out of the box that i have to repeat, surely this is not right. I've set both the RIS server and CD/DVD based install the same to get rid of any partitions and format. Not sure what do now, has anyone else come across this one. Is it just a case of wash and repeat.

I actually believe in unattended, but i'm in a position where i have to convince others to convert over. I just need more ammunition...unattended is better because..... But thanks everyone for your input

bump can anyone post any links to pros and cons of this type of install seems unattended is leading at the moment overall.

THIS IS GREAT STUFF KEEP IT COMING i'm not sure about formatting the pc before the image goes on, in the past i haven't done this. Unattended on the otherhand i do format, albeit only a quick format. With ghost for example you use a boot disk(ghost.exe) and then copy the image over, i don't think it formats but i could be wrong on this.

Does anyone know which method is best overall Obviously Imaged PCs are faster at rebuilding than Unattended ones Are imaged systems more reliable?, anyone else have any points on this as i'm really finding it hard to justify using Unattended disks over Imaged ones on our small network. please anyone have any info or links to where i can read up, cheers

excellent i was almost there myself cheers

Almost done my Setup now Just need a reg to disable/remove My Music and My Pictures in XP default start menu. Has anyone got these, before anyone says use the search i have but it keeps crashing out. please if anyone can post these it would be great thanks.

Brilliant and informative reply's as always, i was thinking along these lines myself as i'm using this install on a large number of pc's, and want to make sure that WFC is turned back on after t13 or at the very least after first logon via a reg tweak. I didn't realize it was a small hack on the dll, sounds like it might work. I will post results from both SP1 & SP2 builds as i'm using both at the moment. many many thanks.....

So basically what your saying is disable with modified SFC_OS.dl_. Then turn it back on with a registry tweak during T-13 setup or first logon. Even though i have a hacked SFC_OS.dll file on the install, will turning it back on with a reg tweak after logon work with a hacked file or not. I can turn it off no problem at all, thanks to info gained from this forum, but i want to turn it back on during first logon or at the very end of an XP setup rebuild. thanks for your prompt reply Alanoll

Thanks to some bright people on here, most now know how to disable SFC in XP. But i would like to switch it back on after setup so my system is more secure. Now is this as easy as copying the original SFC_OS.dll back after setup via a small batch script or is it more involved. Has anyone done this.... its really annoying coming back to a pc after 3 hours to find it hanging during setup as i've overwritten some file or other.....grrrrrrr. Any help will be greatly appreciated

ditto