Tripredacus

I recall we used to have a different layout saying what MSFN is. When the redesign for this forum skin was done, I guess that disappeared. It stands for Microsoft Software Forum Network. Our Admin, Xper owns the site. We are not part of Microsoft. Basically as you can see from the forum layout, we have 2 main sections for Microsoft software: usage and installation. Then of course there are the member projects and the other stuff.

If you are not using Volume License, you will need a product key for each one.

For the problem of getting the answer file to be read by the WIM file... Rename your answer file unattend.xml. Then mount your image and put the unattend.xml file into mount\windows\system32\sysprep. Then commit your changes and try to apply your image. Alternatively, another option is you can run setup and use the /unattend switch to specify the location of the answer file, rather than having to manually put it in the image. For the parsing error, you'll need to attach your xml file to a post (make sure to edit out your domain information and product key) so we can look at it. Otherwise you can validate it in WSIM to make sure you do not have any errors it can find.

Asus merely gives it a name (Graphix Boost) but the technology isn't theirs. It is actually Intel's technology. http://www.intel.com/support/graphics/sb/CS-031103.htm

If that was the case, why would the topic still exist? Anyways, this topic comes up every now and then, as mentioned. There's no harm in leaving it here in case Xper wants to reply to it and others can read his response.

I tend to agree with the response you got on Technet. That event alone is not enough information. I would look in Event Viewer for any additional information.

I want to be clear about your post. You had Windows 8 You tried to install XP using Win2flash

Maybe by the time the Enterprise Channel gets off XP and hits Windows 7, Microsoft will have made some tool that lets them manage the online component of Windows 8. But if the old trend of OS usage in the enterprise holds true, Windows 8 will be skipped just like Vista was.

I remember a time I was looking for a free music app. See, back then I have Windows XP SP2 and didn't want to get SP3. And then i had my new iPod and iTunes refused to install. After nearly breaking my OS trying to trick iTunes to install, I found that Winamp worked with iPods just fine.

I think that with the internet, we are all a lot closer to each other than ever before. Just even look at this forum (or any other) and people are from all over the place, and we come together and help each other and talk about things. I never would have imagined it 30 years ago. Its obvious that we aren't really "there" yet, but since we can't talk about politics on MSFN, you'll have to go find that part of the discussion someplace else.

Latest numbers, Windows Phone moves into the 3rd spot, overtakes Blackberry. http://www.ign.com/articles/2013/05/17/windows-phone-overtakes-blackberry-as-third-largest-mobile-os I wonder who is #1 and #2...

I doubt it will change any. Intel rarely will actually update a driver when a new package is released. This is why driver versions in Device Manager rarely (if ever) match up to the version of teh Chipset driver package.

So there is some condition that is met by the INF that is causing the Chipset Setup to "remove" it from the installation queue. It eventually just removes all of the INFs and doesn't install anything. Here is a truncated parsing, I left out all the Hardware ID matches. Current INF = D:\Programas\Drivers\Intel® Chipset Device Software\All\5000XZVP.inf Date = 02/25/2013 Version = 9.1.9.1003 ClassGUID = {4D36E97D-E325-11CE-BFC1-08002BE10318} PackageInfo.Name = Chipset PackageInfo.Sequence = 0 PackageInfo.INFSource = PackageInfo.ConditionIfNotInstalledDriverName = Provider(Microsoft)||InstalledDriverName(Chipset)||Provider() Inf supports 64 bit. Manufacturer = INTEL,NT.5.1,NTAMD64 Resolved Manufacturer = INTEL.NT.5.1 Here is the only other mention of this driver file, where it gets filtered out. Also note the awesome typo. [Manditory Filters] Condition = Provider(Microsoft)||InstalledDriverName(Chipset)||Provider() Condition Removed INF = D:\Programas\Drivers\Intel® Chipset Device Software\All\5000XZVP.inf If I were to guess, it is saying that if the current driver for the device has Microsoft as the provider, then it doesn't try to install it. If you look at this link here: http://communities.intel.com/thread/28114 The "answer" implies that Setup.exe does additional checks that aren't based solely on whether or not the drivers will work manually, as you have seen. In the INF itself, this comes from the PackageInfo: [PackageInfo] Name=Chipset Condition=Provider(Microsoft)||InstalledDriverName(Chipset)||Provider() The following link says that a PackageInfo Condition is used by a third-party co-installer, in this case, Intel's Chipset Setup.exe. http://www.osronline.com/showthread.cfm?link=204870 So you could try removing the Condition line from the INF and see what that does.

No, I think it is perfectly valid. Even if you had done it by accident or unknowingly, it is a clear way to see that the BCD is being modified. Otherwise it should have resumed normally! Also I don't think I have anything that lets me boot from something else on hibernate. Most of the systems I use seem "aware" at the BIOS level that the HDD is in hibernate, and none of the function keys "work" except maybe going into the BIOS. Even so, I wouldn't only be able to confirm that it does indeed do that or not, and not really be able to offer any other thoughts on the subject like a fix or whatever else. Truthfully, the BCD still kinda scares me.

Forgive me if this was brought up already... It seems that those who use Windows 8 Pro VLK are not allowed to install or use Windows Media Player. The issue seems to be those companies that use certain License contracts for Windows, the education, government, etc. Some selected quotes... I giggled. You can read the whole thing here: http://social.technet.microsoft.com/Forums/en-US/w8itproinstall/thread/da8b1554-af4a-467b-a93b-0d18f079f19c

I've never considered booting to PE a machine that was hibernating... But I wonder if you tested this using a CD as well? (Not that I expect it to be any different, but you never know).

I'd like to clarify what you say and compare to what WinOutreach4 posted. It is that Windows 8 Setup.exe does not support this. But a person could use Windows 8 DISM to do it instead.

Oh and you (Dogway) said that when you run Setup.exe, nothing gets installed. Did you check the log file in C:\Intel to see if it says anything in there?

I have not used IE10 yet, but what is the message you get?

Maybe times are changing, but I still think of bees and ants when I hear or read the word "drone" as well as the song by Fear Factory.

The actual problem is that on some of this new hardware, you can't read from WMI. Its not across the board. I am testing on a NUC now and it does not exhibit this problem. I'll keep an eye out for one that gets the error and then run the command you requested. I just got one on the DB75EN. Wmic was able to read that field in the BIOS just fine but.... it has "technically" invalid information. I can't post what shows up, but it isn't the model number. This in itself shouldn't matter with generating the GUI. I think instead I should get a Quad opened with Intel as this might be related.

Crosspost from here: http://www.autoitscript.com/forum/topic/150866-strange-wmi-problem-on-intel-hardware/ I don't think it is an AutoIT problem. I've been getting reports from manufacturing that some of our applications have been generating an error, such as: AUTOIT ERROR LINE 1165(X:\windows\system32\program.exe) ERROR: Subscript used w/ non-array variable I have determined what is causing this error, and at which point, but not why and have not been able to determine a way to program around it. I am actually seeing this error in any application that reads from the WMI, here is an example script: $sWMIService = "winmgmts:\\" & @ComputerName & "\root\CIMV2" $objWMIService = ObjGet($sWMIService) IF IsObj($objWMIService) Then $colItems = $objWMIService.ExecQuery("SELECT * FROM Win32_ComputerSystem") If IsObj($colItems) Then For $oItem In $colItems $sModel = StringReplace( $oItem.Model , "/" , "" ) Next EndIf EndIf The application reads from WMI to get the Model number for 2 reasons. 1 it displays it on the screen and 2 it looks up that value on the server so that it can generate the GUI. Obviously, if the field is empty an error is generated. However, it does not care if it cannot find the value on the server, as if the value does not match, it shows a default message. So the way it is currently written, I know exactly what the error means when it appears. It means the field is empty. There was only 1 hardware I had where the field actually WAS empty, and it was a prototype unit. If a production unit had no value there, we would defect it out for obvious reasons. Now on to where the error occurs. The application is compiled for 64bit. Case where error occurs (not 100% of hardware, but 100% on the hardware it happens on unless workaround.) - Intel BIOS has both UEFI and Legacy Boot enabled. - BIOS-level PXE* boot to WinPE 4.0 x64 - Run application - WMI value is an object, but the object is empty, or null. * I don't think PXE is a requirement, but I don't boot via CD or USB. Workaround - Disable UEFI boot in the BIOS. If you can think of any thing I could try to find out what the problem could be, let me know. I may end up posting this question elsewhere as well. For those who are interested, hardware effected: Intel DB75EN Intel NUC (D33217GKE/DC3217YE)

You can't install applications with DISM, but you can with MDT. You add it to the Task Sequence or create a custom one. http://social.technet.microsoft.com/Forums/en-US/mdt/thread/0d37367d-6ac7-459e-b54f-78bbcdfbb114/ There are some different methods to deploying favorites here: http://social.technet.microsoft.com/Forums/en-US/mdt/thread/758d5bbd-bfb5-4500-be0f-ea49d8cc968f

This topic is a magnet for spammers.

It means that the OS' inbox driver is to be used. There is no problem? If you wanted to test, you could change part of the INF from NO_DRV to PCI_DRV, but you could protentially cause a BSOD or other errors by trying to install it. If you did it this way, you would probably need to update the driver using Device Manager instead of Setup.