Martin Zugec

Try this (not sure, if it will work for local) On error resume next Set WshNetwork = WScript.CreateObject("WScript.Network") Set oDrives = WshNetwork.EnumNetworkDrives Set oPrinters = WshNetwork.EnumPrinterConnections For i = 0 to oDrives.Count - 1 Step 2 WshNetwork.RemoveNetworkDrive oDrives.Item(i),true,true Next For i = 0 to oPrinters.Count - 1 Step 2 WScript.Echo oPrinters.Item(i+1) WshNetwork.RemovePrinterConnection oPrinters.Item(i+1) Next

OEAccess during unattended, StubPath for existing installations

Well, I am not happy about this situation I would rather use WinPE than BartPE... But I dont have any chance to solve this situation

2Chris: Thanks for your help... I found out someone in my company tried to save some money, so my licence dont cover using WinPE Switching to BartPE....

So vbscript? Or you need it also for 9x?

When I use Virtual PC, everything works fine, strange is that with Broadcom (1Gb) NIC when I try to use ipconfig /all command, I get only Windows IP Configuration line. Also I dont see any network adapters in task manager I downloaded different NIC driver, but it didnt help

You are not bugging It is difference package between two time points - Point 1 - create initial snapshot (what files, registry etc.) Run installations, modify every setting you want Point 2 - create secondary snapshot (what files were added, deleted or modified) So it will create .exe (or sometimes .msi, it depends on snapshot program) file, that will contain informations what to change. It will save you lot of time - but later, when you will encounter any problem, it is really hard to find out why and whats happening. I am using this snapshot method only when if there is no other solution and I spend a lot of time removing trash from end package. It is not worth the problems it brings with itself... One things that it can be used for is recording tweaks.

Only XP, servers (TS) and Longhorn If you want to manage 9x stations, you must use 3rd party tools

Lot of stuff - mostly problems you woudnt expect When I was beginning with deployment (heh, long time ago), I started using snapshots, because other method were not documented as today - and often encountered many strange problems - for example I found out, that with Office 97 I distributed also part of my IM history... Or icon for one program was automatically changed to Recycle Bin... Or similar prolems. I do not use snapshots as installation method and also I dont use AutoIt macro setups (it is not stable enought for corporate use)

From CD... BTW InstDrv is from NT DDK, right?

It is not good way - InstallRite is only snapshot installation, so I wouldnt recommend it to create installation packages... I am using it sometimes - when I need to make snapshot (not for installations, but to see what changed between two time stamps)

This is the part, where you control if name of partition is hddinst (ready for installation, e.g. gdisk was run before. Section2 is where installation continue. %ramd%\gdisk\gdisk.exe 1 /status|%ramd%\gdisk\find.exe /i "hddinst" if not errorlevel 1 goto section2 goto gdisk :gdisk %ramd%\gdisk\gdisk.exe 1 /mbr /wipe /y > nul %ramd%\gdisk\gdisk.exe 1 /cre /pri /sz:4096 /for /v:hddinst %ramd%\gdisk\reboot.com /c > nul goto end

BTW Nice message about hardware minimum 0.0GHz CPU needed

you mean like wmic os get countrycode ?

File not found EDIT: Sorry, Monday, I see what you ment... Will try it and let you know

Hi! I got some problems adding broadcom drivers to WinPE - I copied .inf to i386\Inf I copied .sys to i386\System32\Drivers But it is doesnt work Any ideas?

Post HijackThis log please.

SingleSignOn in company, RoboForm for personal use...

Nope, on server... PXE on workstation other than Linux is quite problem

Well, script kiddies

RIS from Microsoft...

My work PC is reinstalled once per two years, test machine next to me is reinstalled 2-3 times every day...

SUS/WSUS are free... It will allow you to centralize patches on intranet server. Have a look here: www.susserver.com

Nope, there isnt timeout...

Not sure, but it shouldnt work on NT4 - one great way to use this is creating NT boot disc - just COPY ntldr, boot.ini and ntdetect.com to cd/floppy and thats all, you will be able to boot to windows from boot medium. I use it together with modified boot.ini, that will allow me to attach debugger