webmedic

ok windows can use new styles along wiht the old traditional style window themes. The current way that windows xp is setup you can only use certified mocrosfot themes. The uxtheme.dll makes it so that you can use third party themes that microsoft would not normaly let you use. This lets you use any of the visual styles that are available for windows xp. Normally you would have to use stylexp or windowblinds to use these themes.

hm well i cant say for that but the inf file I showed you works fine and soes not need a restart to test. It should be saved as test.inf or whatever you want to call it.

ok since I dont have it all finished yet I wanted to show the inf file I use for this. It looks more or les the same accept you can change the header stuff so it does not say windows update. ; ; Version 2.0 ; Copyright : © 2000,2001,2002,2003 ; by Brook Humphrey (bah@webmedic.net) ; for Mobile PC Medic OEM systems ; [version] signature = "$CHICAGO$" Compatible = 1 AdvancedINF = 2.5,"You need a newer version of AdvPack.DLL!" LayoutFile = layout.inf, layout1.inf, layout2.inf [DefaultInstall] AddReg = AdvSetup [DefaultInstall2] BeginPrompt = InstallBegin SmartReboot = N [InstallBegin] Prompt = "Do you want to install the WindowsXP Shell Toy?" ButtonType = YESNO Title = "The Mobile PC Medic Shell Toy" [AdvSetup] HKLM,%RunOnce%setup," Shell Install XP by Brook Humphrey",0,"" HKLM,%RunOnce%setup," © 2000, 2001, 2002, 2003",0,"" HKLM,%RunOnce%setup," www.webmedic.net",0,"" HKLM,%RunOnce%setup,"_______________________",0,"" HKLM,%RunOnce%setup," ",0,"" ;HKLM,%RunOnce%Setup,"Installing Shell Toy",0,"RunDll32.exe advpack.dll,LaunchINFSection %1%\test.INF,DefaultInstall2" ;HKLM,%RunOnce%setup," ",0,"c:\\install\\applications\\pspad\\pspad426inst_en.exe" HKLM,%RunOnce%setup,"Ad-Aware", 0, "%systemdrive%\\install\\applications\\adaware\\aaw6181.exe /s" ;HKLM,%RunOnce%setup,"TweakUI Link",0,"COPY %TweakUILink% %TweakUILinkDest%" HKLM,%RunOnce%setup,"K-Lite Codec Pack 2.04 Basic", 0, "%systemdrive%\\install\\applications\\codecs\\klcodec204f.exe /VERYSILENT /SP-" HKLM,%RunOnce%setup,"QuickTime Alternative 1.11", 0, "%systemdrive%\\install\applications\\codecs\\quicktimealt111.exe /VERYSILENT /SP-" HKLM,%RunOnce%setup,"Real Alternative 1.02", 0, "%systemdrive%\\install\applications\\codecs\\realalt102.exe /VERYSILENT /SP-" HKLM,%RunOnce%setup,"Kazaa Lite K-plus-plus 2.41", 0, "%systemdrive%\\install\\applications\\Kazaa\\klitekpp241e.exe /verysilent" HKLM,%RunOnce%setup,"ATI Control Panel for Catalyst 3.6",0,"%systemdrive%\\install\\applications\\ATI_CP_3_6\\Setup.exe -s -f1\"%systemdrive%\\install\\Applications\\ATI_CP_3_6\\setup.iss\"" HKLM,%RunOnce%setup,"Flashget 1.4", 0, "%systemdrive%\\install\\applications\\flashget\\fgf140.exe /S" HKLM,%RunOnce%setup,"Nero Burning ROM v6.0.0.11", 0, "%systemdrive%\\install\\applications\\Nero\\Nero60011.exe /silent /noreboot" HKLM,%RunOnce%setup,"Registering Nero Burning ROM...",0,"REGEDIT /S %systemdrive%\\install\\Applications\\Nero\\register.reg" HKLM,%RunOnce%setup,"Nforce Audio Controle Panle", 0 ,"RunDll32.exe advpack.dll,LaunchINFSection %systemdrive%\\drivers\\nforce\\AudioUtl\\nvautils.inf,DefaultInstall" HKLM,%RunOnce%setup,"Startup Control Panel v2.8...",0, "RunDll32.exe advpack.dll,LaunchINFSection %systemdrive%\\install\\applications\\StartupCPL\\startup.inf,DefaultInstall" HKLM,%RunOnce%setup,"Sun Java VM 1.4.1", 0, "%systemdrive%\\install\applications\\SunJava_1_4_1\\setup.exe -s -f1\"%systemdrive%\\install\\Applications\\SunJava_1_4_1\\setup.iss\"" HKLM,%RunOnce%setup,"Open Office 1.1rc2", 0, "%systemdrive%\\install\applications\\OOo_1.1rc2\\setup.exe -r:%systemdrive%\\install\\Applications\\OOo_1.1rc2\\openoffice.txt -debug" HKLM,%RunOnce%setup,"Mozilla 1.4", 0, "%systemdrive%\\install\applications\\Mozilla\\setup.exe -ma -ira" [Del.AdvSetup] HKLM,%RunOnce%setup,"Installing Shell Toy",0,"" [Strings] systemdrive = "c:" Product = "Shell Toy XP" DiskName = "Shell Toy XP, Setup Disk #1" Uninstall = "Software\Microsoft\Windows\CurrentVersion\Uninstall\" Runonce = "SOFTWARE\Microsoft\Windows\CurrentVersion\Runonce\" Setup = "SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" DosHere = "DOS PROMPT HERE" Edi = "01,00,00,00" SubDir = "WINDOWS" EXPLO = "Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" KEY_RUNONCE = "SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" KEY_INSTALLEDCOMPS="SOFTWARE\Microsoft\Active Setup\Installed Components" OnlineLong = "Online Services" KEY_IEXPLORERMAIN="Software\Microsoft\Internet Explorer\Main" NAME_RUNONCE= "MPCM Settings" w95u1 = "rundll.exe setupx.dll,InstallHinfSection" wNTu1 = "RunDll32 syssetup.dll,SetupInfObjectInstallAction" wu2 = "DefaultUninstall 132" AppDir = AppGroup = AppName = "My Application" CopyrightMessage = "Copyright (c) 2003. All rights reserved. My Company. www.pablovandermeer.nl." TweakUILink = "\"c:\\install\\PowerToys\\TweakUI 2.10 Powertoy.lnk\"" TweakUILinkDest = "\"c:\\Documents and Settings\\All Users\\Start Menu\\Programs\\\"" there are some things I'm testing in there but you get the idea how it's done. Shortly I will add to it I think I have found a way to include other things that dont want to install nicely. Like tweakui for now you can just drop this onto your desctop or anyware and as long as you have the install files on your hard drive under install then it will start installing them. Just right click on it and select install to see how it looks. Man when i saw the other way of doing this I realized I have had this sitting around for a long time. I had a little thing I called shell toy that would add right click command propmt and whatnot to your shell stuff and you could ininstall it also so I just modified this to do what I wanted for the installer. Enjoy all. Let me know I can also turn most or the registry tweeks into little inf files like this so you can uninstall them if you want. I dont know why I did not think of this sooner. Change it how ever you like I only ask you leave in the header.

well I cant speak for him but I have a way to do this that is a little different. It laods it all through an inf file. But it looks perty and is somewhat customizable for the way it looks.

Yea there is that. I tried it first but it made non bootable cd's so I'm not using it anymore. My scripts are not as automatic however. I just downlaoded it again to see how I could modify it to make a complete package using my scripts for the hotfix generation. And I will look through it to see what if anything else may be upgraded to work better. For instance that thing it not exactly automatic. I will work on making things a little more automaitic. which i have had planned anyway.

Yes I have it that way already but durring the install for some reason it can't find were it extracts the files to. I hate that part. I will most liekly have to add another switch to get it working but that is a rather minor issue right now.

well what I have could not exactly be called a hotfix list as it does oh so much more than that. Really though it is much more automatic than that.

yes I have a cmd file that will do all your hotfixes with much less trouble than that but I also have a cmd file that will compile your hotfixes into your installer. You will need to have sp1 installed first. I will try to get this out tomarrow if I have time. I wanted to get it out today but I just now got my system up and running and I dont really want to stay up much later. I originaly got thiws idea and the orginal cmd file from another guy on these forums but i have since greatly enhanced it to include many more hot fixes than the original would work with.

instead just put your themes into /$OEM$/$$/Resources/Themes then the installer will automaticly copy them for you and wont wont need to use xcopy or copy.

Ok I'm back and posting from my fresh install. I think i have about every thing worked out. It even installed onto my sata drive no problems. Last few issues 1) that stupid mdac hotfix does not want to slipstream into the installer. 2) I need to figure out how to get the nvidia audioutils to install correctly. Other than that it's all working. 1) Raid controllers for promise, Highigh point, ans silicone image on abit, epox, gigabyte, shuttle, soltek and aopen boards working. It should in thoery work jsut fine for asus also but I dont have one to test. It should also qork for third party add on boards. 2) Hotfixes accept for mdac are slipstreamed. I'm sorry I got all this done so late I'll try to make a readme along with the files needed and the folders into a nice little setup for you all and get it out tomarrow. all the rest is regualr stuff you all are doing more or less. I have it also setup to use 2cd's and i include some themes and lots of drivers. This thing has been tested on allot of amd boards and I have to rma an epox intel board but when that comes back I'll test it on that also.

Well they have been using cmd here and it works fine. So would bat they are the same thing.

yes that will let windows use your drivers during the graphical mode for install and after you have installed the os. It will not give you extra needed drivers during textmode if you need raid drivers and such.

Yes I need to get the winders box back up today though. It's down right now and it is the one with all my stuff on it.

hotfix.cmd >> log.txt

I have a script that will automate this. You just drop all your wanted hotfixes into the directories and run the cmd file. It's on my other computer but i can post it tomarrow.

Yes look at it carefully it will check to see witch drive o=is your cdrom then it will copy all the files from the second cdrom to your hard drive. Then it starts to run the extra cmd files from the second cdrom as well as the ones from the first cdrom. Then it finishes everything off and does a reboot.

yes sorry I dont have the nfo in front of me but I'll post the way to do it tomarrow when i have the info avaialble.

thanks I'll try to have it done soon. I only have one small thing buging me about it still.

yes in the switch that says fullunatended use prvoidedefaults instead.

You most likely wont that is accordng to microsoft the correct wat to do it but I was never able to get it to work either along with many others.

I guess my problem is I see no reason to waste my time with a windows firewall that my be compromised due to lack of any decent amount of any real security in the os to begin with. All my stuff sits behind my linux firewall. Not only that but the linux firewall was a snap to set up. I have done the same thing for other small business in my area. It works quite well and they dont have disruptions like a few weeks ago. For them it's all business as usuall while everybody else is struggeling to get thier systems back up. As for the hot fixes it is still a good policy for any admin to aply them internaly or you could be just like microsoft and hewlet packard themselves who got allot of system infected by sqlslammer. I good firewall on a windows box is an oxymorron.

Well I have multiple cd's so I ave still used the remove cdrom method along with copy and past it into place. This is all done durring the first boot into the os as a user. I think I have it running out of my customize batch as one of the last things right before I issue the shutdown command.

I have tried my sugestion above and windows filew protection does kick into play. The only solution I have found to work is to simply remove the cd fro mthe cdtray before you do any of the replacements. I have solved this in my case since i use either two cd's for the install or a dvd. I have my batch setup to check for the cdrom including the i386folder and if it is there it will ask you to remove it and will not let you go on untill it has been removed. I'm trying to find a little better way ot do this but for now it works lik i have it.

Well I must say thanks for the registry key. I have not experianced any of hte other errors with hte patches but I have slipstreamed them into the installer now. So I dont need any hotfixes.bat to include them.

I was never able to get this working with multiple different driver sets. I do however have it working with the txtsetup.sif and winnt.sif. It is also much easier to setup this way and does not require as much work as the txtsetup.oem file does. Especially considering I have implimented all the current ide and sata raid drivers I could find.