iamtheky

kicking it off from a batch with diskpart up front. Bartpe and Nu2menu will make it pretty, there are simpler ways though. diskpart.exe /s client.txt @echo off set SETUP=where\ever\you\put\I386 format c: /fs:ntfs /v:OS /q /y start /wait %SETUP%\winnt32.exe /s:%SETUP% /unattend:%SETUP%\winnt.sif /syspart:c: /tempdrive:c: /makelocalsource /noreboot client.txt select disk 0 clean create partition primary noerr assign letter=c noerr exit

setupcomplete.cmd is imho the easiest method for all those tasks. i liken it to runonceex.

taskkil /IM is* provided its the only task that begins with is

The following works excellent for a single partition occupying the entire disk. I would like to specify a C partition with <size>20000</size> and a D partition that is extended occupying the rest of the disk. I have tried many a different ways to accomplish this and 7 liked none of them, so I figured it best to provide the working single disk and let some kind soul add the additional disk with the proper syntax I seem to lack. <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Format>NTFS</Format> <Label>Seven</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration>

Why the talk of CabTool and 'Installers"? Just toss them in the fonts folder prior to iso. Then run the reg file from the runonce. I am just curious as those seem like unnecessary additional steps, but would like to learn if they are facilitating something I had no need for.

same username and password (with admin group rights) on both boxes clears it up in our environment. If you have the same UN and different passwords, that might not be helping the cause.

http://unattended.msfn.org/unattended.xp/view/web/18/ this will teach you all about the $oem$ folder structure. You can place all the items you need in this area and abuse them from the runonceex.cmd http://unattended.msfn.org/unattended.xp/view/web/31/

You can most certainly place them in the c:\windows\fonts folder prior to .iso and run the .reg file from the runonce all my barcode fonts are deployed this way.

*You posted in the MS office area* Are you talking Operating System XP SP2? (the question is oddly worded for an office updates issue as they are defined by year as well).

why not just add them to the c:\windows\fonts and then register them if necessary with a reg file that looks like: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "MW6 PDF417R3 (True Type)"="MW6PDF417R3.TTF" Where "MW6 PDF417R3 (True Type)" = the name of the file as it appears on your computer AND "MW6PDF417R3.TTF" = the actual name of the font file (right click, properties, and its at the top of the general tab)

you made sure to clear your cache, flush your dns, confirm the issue on multiple browsers, all the helpful client side things right...

you would still need full paths. this portion c:\temp\rebuilder\ from your first example

as long as you have a VLK or unique key for each, using the same source files is not an issue.

Yeah that doesnt sound like a school assignment at all* you should try googling them one by one, its easier. the first return for "Set the free / busy period in the calendar option to 24 months" http://office-outlook.com/outlook-forum/index.php/m/137233/ in the amount of time you spent registering forums and posting your question you could have been finished.

True, i got a D on that one I should have certainly caveated that with - i use the bart solution - that and I partition (diskpart) separately from wiping/erasing. *And 7 passes is indeed overkill, but satisfying arbitrary requirements is my livelihood

make your usb bootable: http://www.bootdisk.com/pendrive.htm put sdelete on it: http://technet.microsoft.com/en-us/sysinte...s/bb897443.aspx sdelete -p 7 -q -c c: ;;;;would make 7 passes on the c: drive (some pseudo DOD action)

Assuming there is one HD with one partition: a floppy, a usb device, a firewire device, a zip disk any of those with sdelete or your favorite write to 0s script.

http://www.archive.org/details/ccope2009-01-29.km184.flac16

*that seems contradictory since it appears to be estimating @ 3.23GB of fragmented space caused by 2 files: do you have a full system backup sitting on the C or did you copy all the cab files over with your install? Maybe some other very large file it cant touch (encrypted files maybe a DB backup, seems too small a number of files with a large footprint to be restore points)

possible, maybe. supportable, surely not. *not that its supported anyway, but makes troubleshooting inordinately more difficult* I use cdimage, there is a nice version out with a GUI but the command line would look something like: sourcefolder = the one that contains the i386 folder. deployfolder = wherever you want the output cdimage -CDNAME -b%sourcefolder%\bootsect.bin -h -n -o -m -w2 %sourcefolder% %deployfolder%\output.iso"

see that folder that says XPkeygen, you need to read rule 1a) then ban yourself.

Yup I just copy the whole office07 folder to the disc and call setup.exe from the runonce, as Clu said the .msp will run automatically if placed in the updates folder (within the office folder). I put the office folder in I386\$oem$\d so the user gets a copy on their d drive, and i get better load times running from there than off the disc.

way to not read rule 1a) xp black is as warez as they come.

http://quick.mixnmojo.com/usb-disk-ejector how to use the command line http://www.howtogeek.com/howto/windows-vis...ific-usb-drive/

I think you have been misled http://desktop.google.com/support/bin/answ...mp;answer=12403 So after its done with the one time index, you can turn indexing off in the application if it is a concern. though it does only run when idle.