DisabledTrucker

You could always write a small app which will put something up in a box on the screen, using XML, which says "it's working" or something to that effect, making a call to something which is only used in version 4. Not having enough knowlege in XML yet, I wouldn't know what to tell you to call for using a simple if-then type statement.

4? *EDITED* Check your PM nolookingca, please.

Well I can't post what the RoyalBlack one looks like, but all it requires is that you put uxtheme patch, which is widely available in these threads, to use. Look here to grab the uxtheme. Then go to ThemeXP.org and search for "RoyalBlack" and download it and install both. The uxtheme.dll goes into your system32 folder in your Windows folder and the RoyalBlack theme goes into your Windows\Resources\Themes folder. Somewhere on these forums I have a pic of what it looks like, well a shot of a folder anyways, it doesn't look all that bad, now if it were just combined with the Royal-5-color-pack version of the black theme there, where it would use the green coloring of the windows close button and start menu button with the tabs in a clearish/greenish color when not/in use. I was going to post a new one here but there isn't a link here to upload one. Plus these forums are giving me a hard time. Either way I don't use anything but the hacked file for the uxtheme to use any of my skins, which doesn't hurt anything when it's done, all it does is take off the M$ restrictions for using an .msstyles style theme.

Another little handy thread I started: Time/Language Codes for WinNT.SIF In it you can find a txt file which has all the Time/Language codes for your WinNT.SIF file for those who don't always use the SetupManager.exe program to build your .SIF's. This file is geared for Windows XP-SP-2 as some of the codes only work in it, though most will work for Y2K, (all versions,) and 2K3 server as well.

could be your virus scanner, what are you using?

When you do your search, look for "two cd" it has been covered here before. Just follow those directions and it should tell you how to do it in that thread, it's the same for DVD's.

Thanks. I would also like to note, that the TimeZone entry doesn't require a 3 digit code, but that's how it was listed, the smallest number you can use works.

Might I also add if you look in the Drivers section of the board, you will find your answers stickied to the top of the first page, as Bâshrat has done all the work for you.

I have attached a file with all the Time Codes and Language codes for Windows XP SP-2. Most will work in other Windows versions, but some are new to Windows XP SP-2. I have compiled a full list from Microsoft's website which you can download below. These figures are for when you are making your WinNT.sif file from scratch and want to know what to put in the [GuiUnattended] TimeZone=### [RegionalSettings] LanguageGroup=##,##,##,etc Language=######## portion of WinNT.sif Feel free to download it for future reference. Right Click To "Save As" 46.1kb TimeLanguageCodes.txt

I have a question, in a batch file, can you use for/next switches? I was thinking I could do the lookup for cd's by using this: For %drive% = "D" to "Z" step 1 IF EXIST %drive%:\WIN51 set CDROM="%drive%:" GOTO STEP next %drive% STEP .... I want to use this in a batch file, but I also want to assure that the Windows CD is in the drive.

I'll be your guinea pig, I am fixing to reinstall XP-SP-2 as I type this so I will have a clean install to work with. I was also looking for a way to integrate that into the installation other than the way I am doing it now.

What path does the DevCon file need to be in? How do you put it in the installation path?

That I did not understand yet, sorry. I decided to keep my folder structure the way I mentioned in my first post because I do not yet use any driver packs. So if I keep the folder structure as it is, will there be any problem ? I would not know how to split the VIA drivers between Intel and AMD systems but I thought that whatever system I am running it on, Windows will simply take the drivers it needs from the OEMPnPDrivers path ... IF you make your folder structure such as: $OEM$\$1\Drivers\ ~~~Nvidia\32 ~~~Nvidia\64 ~~~Via\AMD ~~~Via\Intel Then you can seperate them as I was talking about earlier. One thing I noticed you had in your WinNT.sif file earlier was a link on the OemPnpDriversPath to "Drivers\Nvidia" and "Drivers\Via" Since your linking to the .inf files you shouldn't need to link to those folders directly. If your going to do it with a RunOnceEx file, I'm not so sure you will need all the others since your using an installer. (Others="Drivers\Nvidia\Audio" for example.) It comes down to wheither or not your installing from within WinNT.sif or not I believe. Someone else may have to correct me on this, but that's what I believe it says in M$'s instructions.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup] "SourcePath"="C:\\I386" "Installation Sources"=hex(7):43,00,3a,00,5c,00,49,00,33,00,38,00,36,00,00,00,\ 00,00 You can also put whatever you want to there, but you actually have to have the i386 files there.

If you put the SFCDisable in the HIVESFT.INF then you don't need the registry tweak. Which is where it has to be to make the SFC_OS.DL_ file to work in the i386 folder. When disabling it during the installation, I make a registry key to enable it and call it prior to booting that runs in WinNT.sif at the RegOneOnce line. You are correct in the tweak about the BITS service in SP-2 requirement to be running if AutoUpdate service is running, set them both to 2. Also, PopupMgr is the pop-up blocker, confirmed. And I believe it's also correct that you would use the .ca for canada as well, to make sure, go to google for your country and see what it is, that's what you'll use instead of .com if it's not U.S. The first one needs to be changed if you are in U.S. Also, when I exported my registry for the Device Manager, this is what I get: Windows Registry Editor Version 5.00 *Edited for content* [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\DevMgr\command] @="mmc.exe %Systemroot%\\System32\\Devmgmt.msc" But like was mentioned it doesn't work correctly apparently.

on this page http://msdn.microsoft.com/library/default....g/debugging.aspIt's like much anything else it's merely personal preference, I for one have seen a big improvement using this tweak in XP, I have used it since my first use of XP when it was released. As for the proper way of adding it, it's not a seperate key but a value added to a string, inside the key. If you use some poorly written programs which make use of .dll's then it will kill them when they are not in use, instead of letting them continue running in the background using valuable resources.

This is incorrect as well: ;----- Force DLL To Unload From Memory ;----- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AlwaysUnloadDLL] "Default"="1" should be: ;----- Force DLL To Unload From Memory ;----- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer] "AlwaysUnloadDLL"="1" also, found another one I haven't seen in there I use: ;----- Preset Folder Customizations for dialog box. ;----- Sets default to My Computer ;----- then lists My Computer, C:, D:, E:, and Network Places on side ;----- C: here is represented as %systemdrive% in the registry ;----- [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\comdlg32\PlacesBar] "Place0"=dword:00000011 "Place1"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,44,00,72,00,69,00,76,\ 00,65,00,25,00,5c,00,00,00 "Place2"="D:\\" "Place3"="E:\\" "Place4"=dword:00000012 @=dword:00000011

Here's one I like to add when I do mine. This works for U.S. but not sure about other countries. ;----- ;----- Add Government and Military to auto url searches ;----- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\UrlTemplate] "5"="www.%s.gov" "6"="www.%s.mil" @joebells Did you try?: @="mmc.exe %systemroot%\\devmgmt.msc"FWIW, I haven't either as of yet, but was asking.

There have been many mods of this one, I use the one I found on Themexp.org. Though I don't reccommend Themexp.org for many of thier adware packaged files, this one come out nicely and wasn't packaged that way when I downloaded it. Was listed, I believe, as Royal Black theme. You will need the uxtheme hack for it to work though.

Thought that was the case of the NVidia control panels, just couldnt remember, as it's been a while since I did an unattended on that system, the ATI on the other hand I do remember having the problem with it's installation on systems which had the NVidia card instead as it always gave an error when trying to install and crashed the unattended on me when I tried it. Which is why I use the way I suggested and made two different UXPCD's one for NVidia based and one for ATI based systems, as I couldn't get around the problems. On the ATI based system, I use a shortcut on the desktop which installs the media center after my install is complete. This is the only thing I use a batch file to install during my installs for the ATI control panel to be installed as well. I am going to change this in a future update I am working on for my unattended which will call a script to check and see which board is being used, once I find the calls for it, and place them both back onto one DVD, (what I use for all my unattended's.) Though I will have to resort to using some sort of batch file to install this, it seems this is the best way of doing this as well as a couple of other installations I want to do in the future.

Did you say this because of my attempt to install the audio utility during runonceex or because I left all the inf files in their folders and added each path in my winnt.sif ? This was inre to putting in the NRM and Audio utility, as these will only install if you have an Nvidia based card, in the instance of the NRM you must have an NForce3 motherboard for these to work at all. As well as shorten it, especially useful if your using multiple driver packs from the top of the thread list. Mhh, I´d rather not do this through shortcuts because this shortcut would also appear on INTEL systems for instance and it would then be up to the user to install this which I would like to avoid ( my future user base probably does not know about the internals of their PC´s ) I have read in recent threads that one can test for certain hardware by running a script or by testing for the existance of special files. However I only found references to ATI video cards not NVIDIA chipset boards ... I know that my runonceex should read something like: if exists ......... then REG ADD %KEY%\001 /V 1 /D "%SYSTEMDRIVE%\drivers\NVIDIA\AudioUtl\Setup.exe -s" /f but I am not sure what to "test" for that would always be present on an NVIDIA board with activated onboard NVIDIA audio. Thanks for your help ! Alex The part about the call to determine the type of card is something that I am unsure of, but from what I gather, you can go into the O/S once you have installed everything, prior to the user getting the computer and either deleting the shortcut or installing it then removing it and resealing the computer. One could do a test for all the others in the script with the final outlook being that one has an Nvidia based motherboard and thus installing the Nvidia boards drivers if all the other checks fail. Though the NRM wont install on other than NForce3 boards, which if your not distributing prior boards, (NForce, Nforce2,) with your systems then you wont have that problem. By putting all the drivers into the base Nvidia folder not only cuts down on space, but also keeps everything into one link from the WinNT.sif file as well. I use that exclusively to install my drivers as I don't use the RunOnceEx.cmd to install them, since Windows XP will install the PNP drivers from that exclusively and does it's own checks. Also if your using multiple driver packs from one of the threads above, then you will run out of space if you keep doing it the way that is mentioned in the installation files in the packs. This keeps my OemPnPDriversPath= to as much of a minimum as possible. I should also mention too, that when I install my PNP Drivers as well as my txtmode drivers, I do so from i386\$OEM$ folder not from the external $OEM$ folder. Doing this Windows XP will delete all these files when it is done with the installation and I don't have to put in a cleanup.cmd file to remove them. One more thing to keep in mind if your installing Via drivers, you should split them between AMD and Intel in subfolders as their drivers are different. The Nvidia's aren't all that much different, with the exception of the 64 and 32-bit versions, in that case you can seperate them, (if different,) by subfolders in the Nvidia folder, and only adding the files which are different between the 32 and 64-bit version in the 64 bit folder thus cutting down even more space, as the 32-bit files contain a lot of the same drivers that are used in the 64-bit version. Glad to be of assistance, if anyone else has a way to do this other than what I mentioned please post your results, as I for one would be interested in them as well.

Problem with doing a combination pack with the display drivers is the control panels. If your not interested in the control panels then you can just take the drivers and place them into a single folder, such as: ~\Drivers\ATI ~\Drivers\Nvidia and place all the driver files from the ~\WinXP folders into the above folders. Windows will find them if you put "Drivers\ATI;Drivers\Nvidia" in your WinNT.sif file, with the OemPreinstall=Yes switch. The control panels will have to be called once your into the O/S from an installer link on the desktop, as attempting to put them both into an unattended install will cause errors, unless someone knows the checks for the individual boards which will allow for a script to do it in unattended. By checking the id of the board, you can theoretically do the unattended from the script for the individual boards, but you would need to have the id's for all the video cards so as to assure that the correct drivers are installed. Having attempting this myself, that is what I have concluded. I would also like to add if you have an AIW card, then that further complicates things, if your going to attempt to install things such as the ATI DVD player, because that too wont install on Nvidia based boards and attempting to do so will only cause errors in the install. Though the basic drivers are installed ok, the rest will not. I can only assume the same problems with the Nvidia Personal Cinema, as I don't have one of those, on an ATI card. Thus, these things will only be able to install once you have come to the desktop. This can be done by leaving the ATI and Nvidia drivers in the C:\Install\Drivers\ folder and placing a link to them in your $OEM$\$Docs\All Users\Desktop folder for installation after the original install. One other way to get around this is to make two seperate installers one for Nvidia and one for ATI and silently install the one onto the corresponding video card based system, then use the full silent installations for each individual one which can be found elsewhere in the forum.

You also need "GenNvRaidDisk"

The problem you will most likely have is that it will attempt to install these drivers even on a computer that doesn't have/use their drivers only to get errors either during the installation or after the initial logon. From my prior experience of attempting this scenerio when using a motherboard not compatible with these drivers, it made the installation freeze and give out all kinds of errors. My advice is to wait until you have booted into the O/S to apply the NVidia audio panel using a shortcut or something which can be deleted if your not using an Nvidia board. As far as making sure you have all the other drivers for your motherboards, I would reccommend removing all the internal folders and putting everything into a folder such as Nvidia or Via, in this manner: ~\Drivers\ .....Intel .....NVidia .....Via Then in your WinNT.sif file you can call just your Intel, Nvidia, or Via folder like this: Drivers\Intel;Drivers\NVidia;Drivers\Via. This will allow you to cut down on your calls, as well as allow for your individual boards find their drivers without any other calls as WinNT.sif will look for them when OemPreinstall=Yes. What it will need to find is the .inf files which if you move everything from their seperate folders into one folder will require less calls for the individual drivers. Since there is no duplication of the files in NVidia, (this is the one I know, not sure about the others,) placing them all into one folder will make it easier. I should note that if there are any folders such as "WinXP" or anything like that in the folder without any other files in the main folder you can pull those files out and place them directly into the Nvidia folder. For ex: ~\Nvidia\ ...Audio ...Audio Utility ...Ethernet ...Ethernet\NRM ......\NRM\WinXP ...Ethernet\WinXP ...Gart ...IDE ...IDE\WinXP ...MemCtl ...SMBus can all be compressed down to: ~\Nvidia\ ...AudioUtility ...NRM ...NRM\WinXP Now I would like to mention, if your not going to be installing on 64-bit systems, you can do without the NRM folder as it only works on Nforce3 motherboards which are only compatible with 64-bit systems. The audio utility can be done away with as well as the audio drivers if your not using them either because your motherboard isn't fully nforce compatible (such as a chaintech,) or because your using another sound card for audio (such as MAudio.) Same can be used for the other drivers in the pack, though for 99.9% of Nvidia boards the rest are used. If you include the AudioUtility folder, I reccommend putting a shortcut to the installer on the desktop using $OEM$\$Docs\All Users\Desktop folder. This will allow for installation only on those motherboards that actually use it. Same for the NRM. HTH.

Thanks prathapml for posting this, hopefully we can keep this one from becoming so messed up that noone can really tell what is new and what isn't. Thanks also to JohnnyDo for compiling all of this for us, I was working on it myself, but gave up due to the ammount of webpages in the last one that I had to weed through. Glad you were able to do it.