TwoJ

Hi Kel Thanks I agree that its probably faster to check file sizes or registry keys then to ennumerate the w32_products list each time, but there is a lot of info about the programs that you can read from wmi. Last week i was deploying some software from group policy and you can do a wmi filter on the client so it checks for office (win32_product where Caption LIKE (%Microsoft Office%)), i think that is something like the command - the LIKE and % are wildcards so Microsoft Office XP and Microsoft Office 2003 will both be true. But i also needed to filter by the language of the office, and there is a (win32_product where language = English) or something like that, the probem is that, that function is only available on Vista, it would return a false on WinXP even if it was true. Also perhaps another benifit is that sometimes i am using wpi just to do updates and its nice if you can scan a computer and greyout any versions of software that are current and try to highlight any installers that are more recent on wpi. This is where i think the need for additional condition statements come-in; Maybe instead of having the greyedout option just put it as a choice in the conditional statement, ie; if condition1=true then [option choices] if software1=v1.0.1 then greyedout if software1<v1.0.1 then (highlight red & Set default tag) if software2=v1.10 & language = ENU then highlight Blue if software2<v1.10 then hightlight gren food for thought, it might be very difficult to implement But that was just to say that there is alot more info about the software installed that might be useful for making choices about which installer to use for WPI. thanks again

I've already put a few comments into the wishlist in the sticky section but i wanted to start a new thread for this because it goes a bit beyond wishlist First i was really happy to see wpi start to use wmi so that some instllations can be somewhat automated obviously determining if you have a 32 or 64 bit OS will change some applications as well as language, etc,etc There is certainly a lot you can use out of the wmi to get info back about the system, but one of the problems is coming up, namely the isInstalled() function, which i'm guessing is the win32_product class I've come across this problem because i deploy software by group policy and occasionally need to do wmi filtering which is the same stuff. The problem is that the stuff in win32_product is only the programs that have used the microsoft installer (msi), so if you have another program like 7zip that uses the nullsoft installer (i think), then it will not register in w32_product. So theres nothing wrong with wpi or the isinstalled(), just that its not going to be complete. You can try isInstalled(7-Zip xxx) and it should return a false even if you have it installed.Personally i would love to have a complete isInstalled function but from what i know it can only be done through wmi & reading the registry (vbs,autoit, etc). As i mentioned in the official wishlist was the capability to have operators like (AND, LIKE, OR) that are available in the wmi scripting, so that you can say something like getOSver==XP AND getOSlang=="ENU" to single out a XP English computer Also to put in multiple conditions and greyouts, I don't know if this would require a change of the configuration file, but i suspect so, for you guys to decide whats best enough for now - thanks again for all your work you guys do great stuff

Things are really moving along! v7 is still bigger & better! Now that the wmi calls to determine OS type, version, etc can be used to determine different files for different conditions, i notice that there is now a need to have multiple conditions statements & greyed conditions; Right now i believe you have the 1 conditional statement and 1 greyed condition that resolves to a true/false and displays the line accordingly. It would also be necessary to have a conditional priority where condition1 is applied first condition2, etc. it might be good to have a dropdown box with some choices based on the conditions, such as choice1=Hide installer, choice2=Display in colour1, choice3 Diplay in colour2 Also i wanted to know can you perform operations sunch as AND LIKE OR operators like in wmi? for the conditional statements, ie [getOSver==xp" AND getOSlang=='"ENU] to get an english XP system? Update - i just tried some basic operators (AND, OR) in the greyed out condition box and i just got errors, i'm not very good with wmi calls but i know that you can do logical operator calls such as the example above. Do you think its possible to build that into the next release where you can do a greyout or conditional statement based on 1 or more conditions? Also in the changelog you mention that the function isInstalled doesn't work on 2003, is that just because wmi is turned off by default? if it was turned on would it work? thanks again for all the work Still fooling around with it; maybe some more ideas The isInstalled functions is very nice to determine the software installed, but it does have a few drawbacks 1) - its slow - maybe consider using a scan button, if someone wants to test if software is installed then they can leave it auto-on/off or manual scan, that way it wont slow it down unnecessarily 2) - i think its picking up the Caption title which is the one that appears in the Add/Remove list however it doesn't always give the version, i forget if or what the handle is but i think there is one that gives the exact version because something like Adobe Flash appears in the add/remove as adobe flash activex - no version #. this might be problematic since it seems you might need some way of doing an iteration, i'm not sure There is scriptomatic from microsoft and an autoit version that is really good for looking at the wmi handles available -also for wmi - i got burned on this recently to find that some handles are not available on all versions of windows, some like caption are universal but i was using one on vista that i tried on XP and it wasn't available. so just a caution

Nuhi - any chance that you can integrate this one without it defaulting to Kabul Timezone? It Seems the new patch is; KB951072 which replaces the old patch KB942763 thanks

Althought this post has been inactive for a while its been of invaluable assistance I thought i would just maybe try to add a bit more info if for any future use; the CIWSUPP is probably Custom Installation Wizard SUPPort hense the reason why this table entry in the msi would need to be set in order to support mst transforms and the CMWSUPP is probably Custom Maintenance Wizard SUPPort which are modifications done after the installation A big thanks to ender51282 for this information!

I know that is one solution but i was more hoping that there would be a way of integrating it without causing the problem

Well it took almost a day of trials to track this down to this thread, but it seems this problem still exists. I was wondering why the timezone setting in my winnt.sif which had always worked was now giving a time zone of Kabul! It seems that it comes down to KB942763, at least on my system It will also affect WU as well when the time is off. I hope there is a solution, i will try the post installation suggestion but it would be nice to have it integrated the first time Thanks

I was anxiously awaiting the inclusion of redirecting profile folders such as Favorites and others, my current DC (2003) is doing 'My Documents' and 'Desktop' redirection. However i installed 2008 to another server, i've upgraded the schema to 2008, and joined that server as a member server not a DC. Now when i go into the group policy management console in 2008, I can see the other options (including preferences) but when I try to add redirection to folders such as Favorites, the checkbox for 'Also apply redirection policy to Windows 2000, Windows 2000 Server, Windows XP, and Windows Server 2003 operating systems' is greyed out. Hense it does not apply this to non-vista machines. How can i make this option available?

Thanks a lot for the program Boooggy! I wanted to know, can you list the 'tweaks' or changes done to the Vanilla version to change it to the Tweaked version? these registry changes where are they controlled from? an ini? I'm interested in having more or less a vanilla installation with wga but implement 1 or 2 registry changes. thanks

Sorry for barking I'm an a** sometimes - one of those days where 3 hours on google led in a big circle I still have a feeling that $winnt$.inf is a little bit more than just a copy of winnt.sif I think that there are some more controls that are perhaps added to it once it is copied to the hard drive. It would probably take some more research that i don't have time for now, but i have the essential info Thanks again

The size will not be any smaller, you are just selecting whether to install them or not. I'm curious to see if anyone else has the stupid registration window and why there's no control or registry key to turn it off. It appears that it will activate for each user as well. I think the solution is to delete the file in the OnlineServices folder?

Belarc Advisor can get the keys for Acrobat. I've been waiting for product key explorer to do it, but the program only gets the hash, but they don't seem to know how to decrypt the hash to get the key. If anyone knows how to decrypt the hash like belarc can, i would appreciate any info thanks

If you use the default command file from millenx it installs a few of the components I guess one of those other components is doing it I'm trying to find which one is causing it, it seems related to the OnlineServices group If you rename or delete the file NOSProductRegistration.dll in Program Files\Nero\Nero8\OnlineServices that seems to eliminate the Window on initial launch of Nero. On another installation i have of Nero that file is not even present??? I thought that it was perhaps a registry setting to determine if registration was done or not but i can't find any registry setting which controls that.. Any ideas?

Thanks a lot MillenX Its a great guide, i was so pleased to get nero to install like this. 1 comment & 1 question -Watch out in 6 & 7 that your path for those folders do not contain any spaces (ie anything in Documents & Settings), the DOS command will not run if there are spaces in the path the way it is written below -Question - the install works great, but when i first click on the application, it pops up a windoes for product registration & getting on their email list for news & information, etc, etc. Do you know is there any way to turn this off? Thanks

Thanks for the info, but the information seems a little incomplete, I was more hoping to know when the file is copied, is it in the text mode setup or at T39? Also it doesn't seem to be just a copy since there are additional entries in the file such as; floppylessbootpath=no producttype=winnt standardserverupgrade=no winntupgrade=no win9xupgrade=no win31upgrade=no Which were not in my winnt.sif file, and i can find no mention of these commands and by what process is the winnt.sif transformend to $winnt$.inf? Also according to this article; http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true It seems that the setup is reading information from the $winnt$.inf on the hard drive and not winnt.sif on the CD? @Neo While i do appreciate for your input, i can assure you that i spend sufficent time researching a question before i would post it in the forum, hense just posting a link to the main guide does not really help because there is no reference to $winnt$.inf in the guide, and i was NOT asking for an explination of winnt.sif, which i am familiar enough with and believe that you might have misinterpted my question. thanks

xehqter, i was wondering if you could modify oemscan so that it takes the path of the ini file as an argument? I am trying to integrate oem scan into a multiboot dvd but the main problem i am running into is that oemscan expects the ini file within the same location. If the path could be added as an argument then the calling function could apply a specific ini for the specific OS BTW are there any arguments that can be used with oemscan?

I am trying to understand the how/where/when etc of the $winnt$.inf I know it is related to winnt.sif, but i'm unclear of the details.

Bezalel - Not that i want to beat a dead horse, but Do you think that the 2B9D18CF BIOS set could be used for pre-activation? i remember reading one post where the SLP 'Key' (ie usually the OEM name) was encrypted into the dat file, and that some people had the tools to decrypt the dat files. Is it possible that the 2B9D18CF BIOS set has got some string like 'Pheonix' that it searches for in the BIOS which would allow it to pre-activate the system? I realize that it would mean that pretty much all BIOS manufactures would have to incorporate the string into their bios so that it would activate but other than that it seems like the generic 2B9D18CF BIOS set is useless and so why include it on the CD?

thanks severach But i think i didn't explain my question properly; I am trying to understand why there would be a oembios file (2B9D18CF) since my understanding is that the normal oembios file (such as HP/Dell/etc) are to pre-activate the computer. hense what purpose does the oembios file (2B9D18CF) serve if it cannot pre-activate the computer? Is it like a requirement that all OEM windows copies have a OEMBIOS file? If this was the case then i guess one could use it as another test to see if the computer uses SLP?

Ok thats great But what do you think of collecting the oembios files and other OEM specific information? I think i can whip up a little autoit script to collect the individual files and zip it up. it would be great if i could also include a ftp client to upload it to my FTP server. The only problem is really hosting, i think it would be really benifical to have the SLP keys that are usually included in the oobeinfo.ini file but i know that most people don't want to host that since that would probably be agaist MS. I'll also have to try to find out about the legality of the oembios files as well, i don't think the oemlogo are a problem legally. Let me know, i'll PM you later for some more details on this project if you are in to it

Getting caught up with old posts OK - i forget which forum i've posted to with this problem but i think i've gotten it It seems that within nlite & the rvmintegrator there is a process of repacking the drivers.cab file, while it seems that most errors are coming from a corrupt drivers.cab file i don't think it is solely that. I think there is also missing and / or corrupt files when installing discs made with nlite and the rvm integrator that are not part of the drivers cab file. What i believe it is on my computer is that before i had 2 sticks of memory, 1 - 256MB & 1 - 1GB, different companies as well, i removed the 256MB stick and i belive the problems have disappeared. I recall before seeing something about mismatched memory causing problems but it was hard to believe that JUST these 2 programs would be having problems. Anyhow if someone else finds this info helpful let others know

I've got a Windows XP Home CD, i assume it is OEM, and i just got the CRC32 of the oembios.cat file as 2B9D18CF If i understand from severach, this is a general (generic) OEMBIOS files. What i don't understand is that since this will not eliminate the need for activation, which would be the case for the retail versions, then what is the point of having the oembios files?

Hi ZaForD I too have just being looking around for oemlogo's, however it seems that no one has made a collection. The reason i am looking is i have started to get into oemscan, and since i see you made a post last year about collecting oemlogo i assume you are still in the process? Since i don't think it has been created, i want to propose a collection that may help the Bezalel's oemscan project as well. I recently downloaded a small AutoIT program called GetFileSet from Siginet's forum, this is a small program (apparenly based on Bezalel's script) to collect oembios files from an OEM computer. I was thinking if we could modify that script to also collect any OEM specific files such as the oembios.*, oembios.bmp, oeminfo.ini, etc the script could also collect oobeinfo.ini which should have the OEM SLP keys While i would like to keep this as legal as possible i do consider that we are not trying to do this in order to bypass or hack Windows, but solely to make re-installation more efficient. Tell me what you think, and then maybe we could both approch Bezalel and Siginet and see whether the community can help us put together a repository of OEM files. Just off the top of my head i have a FTP site that could be used for uploading, and perhaps i could do the work of organizing the files if Bezalel could host them on his site? Let me know and then i can get some priliminary research done

It seems like one of those days where everything doesn't work For some reason IE7 doesn't want to take my msfn username/password - thank goodness there is firefox! Anyhow - i can relate - on my labtop a toshiba satellite a20 i am having the same issues, i googled the amdk6.sys file and found this thread I was also having problems with mfc40u.dll so it seem weird that this is happening, i have had problems with memory before but i find it strange that it is only happening i think when using nlite or RVM integrator. i am going to try and do the same procedure from another computer and see what the results are. It's one of those problems that is hard to track down exactly where the error is getting introduced. I'll try to update with any fresh info

C'est longtemps que je ne pas ecrite en francaise, et en plus sur une clavier anglais, alors desole pour les faults et l'orthograph! Si ca marcher avant avec l'ancienne version, puis pas maintenant avec le nouveau je croix tu dois regarder dans le config.js pour voir si c'est tous est comme le vieux version, ex les "paths" sont le meme ;ex cmd1[pn]=['%CDROM%\\Install\\7-Zip\\7z432.exe /S'] Le location default pour les logiciel est dans le ficher 'Install' dans le ficher 'WPI', alors poue l'example en haut le structure est; -Root- Win51 Setup.exe [i386] <- ficher [$OEM$] [WPI] -wpi.ico -[Audio] -[install] -[7-zip] - 7z432.exe Alors si c'est comme ca, j'espoir que ca marcher pour toi Bonne Chance