Klaassh

Having the same problem Going by GrofLuigi's post, I am missing "network location awareness" from services altogether. No services were removed on this setup, nor was the service enable/disable tab used. All the other services listed by GrofLuigi are running and still nothing

I have 12 different 7zip sfx's I use in my unattended. It works for all of them eg: start "" /wait %systemdrive%\CDWrite.exe -y /q /r:n

-y /q /r:n will extract a 7zip self extractor

I believe you set it up how you want it and then export this key [HKEY_CURRENT_USER\Control Panel\PowerCfg\PowerPolicies\0] EG: ;Set Power Configuration [HKEY_CURRENT_USER\Control Panel\PowerCfg] "CurrentPowerPolicy"="0" [HKEY_CURRENT_USER\Control Panel\PowerCfg\PowerPolicies\0] "Policies"=hex:01,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,02,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,2c,01,00,00,32,32,00,03,04,00,00,00,04,00,\ 00,00,01,00,00,00,14,f2,06,00,30,2a,00,00,2c,01,00,00,00,00,00,00,58,02,00,\ 00,00,00,64,64,64,64,95,71

If it's setupmgr.exe, it's in deploy.cab on your windows cd

I tried this with the same result. When i use 'winnt' unter DOS, the 2nd folder is created. No explanation to this behavior... If you are using the /unattend:c:\unattend.txt switch, cut your unattend.txt down to just the basics needed in it for now. I have a fairly large unattend and it didn't like it Nice Post, gosh I have no checking to base this on but I do believe that this method cuts a couple of mb more than just manually deleteing the files, at least the finished iso from this and my other clean ISO are different in size but I can't be sure I didn't add something to the previous one or do something different (theres been so many)

I don't use NTFS and I get them, but it seems the difference is "I can delete them"

Not got 4gig to test with, but I would say it would be automatic like the multiprocessor one is in our case (hyperthreaded anyway)

On your original windows cd in the directory "SUPPORT\TOOLS" find the file DEPLOY.CAB in it you will find a tool (setupmgr.exe) for building custom unattend.txts, use this tool to build a basic one which includes your language settings. then either rename the output to WINNT.SIF or incorporate the output into your WINNT

Therre are actually 4 versions of the kernel ntoskrnl.exe Uniprocessor x86 architecture systems with 4 GB of physical memory or less. ntkrnlpa.exe Uniprocessor x86 architecture systems with PAE support. ntkrnlmp.exe Multiprocessor x86 architecture systems with 4 GB of physical memory or less. ntkrpamp.exe Multiprocessor x86 architecture systems with PAE support.

Look HERE

Run an update (without switches) manually, now leave the window open without pressing next and somewhere on your system you should have one of these folders. I can do this and on pressing cancel the folder disappears. but not so on my install cd the folders do not delete. It's not a big deal for me, as I can delete it manually after but I can see where neophyte would be frustrated, not being able to delete these folders. Neophyte, do you disable sfc? perhaps try this, disabling it to delete them and if sfc is a feature you use, reenable it afterwards. Still not a fix though

Hmmm no help here but I get the same folders. Mine occur on E: drive and they delete easily (but still have to do it manually).

My apologies, I thought this is what a forum was for.

@thanatos I used chaninja blue because it fitted and didn't use a shellstyle.dll, which meant no editing of the msstyle (to point to metallic or homestead, etc), that meant only 2 files to replace, LUNA.MS_ & LUNA.TH_. But the theme I used in side of LUNA.TH_ was edited to include the extra's I mentioned above.

requires the replacement uxtheme.dll 3- You can't remove it, but you can replace it with a theme with the same structure, basically using the same method scankurban listed for the wallpapers. Plus the theme is only a text file and you can edit it(well set it up on your pc or a vm first) to include cursors, sounds & some icon replacements as well. You will have to edit your msstyles properly to reflect the default location (homestead, metallic, etc) if you use a custom shellstyle.dll

Ahhh yeah I know, it was this bit I was saying I didn't get, sorry if you missed it. there was actually more to the post but I edited it out so as not to be longwinded By the way, gosh, quality posts you've been making, I prefer the editing of the actual cd contents, rather than changing them later.

Copied this from the other thread as it's unrelated I have an XP CD that I made 12 months ago, that replaces most of the pretty files(bmp's, theme's, user dll's, etc) and some dll's that doesn't give the errors you mention even though it doesn't use a WINNT.SIF. See below for an image, thats how it looks on 1st boot after installing normally, no batchs or unattends. Here is the setuperr.log from that install. If you notice that out of all the files I replaced (some 100+) it is only the dll's and exe's that get logged Error: Setup detected that the system file named [c:\windows\system32\logon.scr] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Error: Setup detected that the system file named [c:\windows\system32\logonui.exe] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Error: Setup detected that the system file named [c:\windows\resources\themes\luna\luna.msstyles] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Error: Setup detected that the system file named [c:\windows\system32\msgina.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Error: Setup detected that the system file named [c:\windows\system32\shdocvw.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Error: Setup detected that the system file named [c:\windows\system32\shell32.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Error: Setup detected that the system file named [c:\windows\resources\themes\luna\shell\normalcolor\shellstyle.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Error: Setup detected that the system file named [c:\windows\resources\themes\luna\shell\metallic\shellstyle.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Error: Setup detected that the system file named [c:\windows\system32\uxtheme.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. ***

Hmmm, this is a cut down nvidia install, might shave another 10 or so MB off your CD. These drivers will brand your card as MSI in the device manager, no big deal but may be to some. By the way, I haven't tested these release Repackaged MSI Win2k & WinXP Detonator Driver v45.32 Date: Oct 03, 2003 Size: 6.87Mb Release Notes: The drivers can only be installed via the Device Manager due to all the language files being taken out nVidia GeForce FX 5200SE & GeForce FX 5950 Ultra appear in the nv4_disp configuration file All language and help files have been removed to ease Dial-up users No word on compatibility or performance from this release All nVidia cards are supported in this release Files are dated: Aug 29, 2003 Originally released by MSI Repackaged by Firecat Winzip Packaged Download HERE

I second that, thanks

Try this thread, Prometheus. haven't got to that point myself so can't say if it works. Installing RAID directly (on WinXP SP1 CD) ?