jdeboeck

Member
  • Content count

    375
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jdeboeck

Contact Methods

  • Website URL
    http://jdeboeck.msfnhosting.com
  1. Because MCE2005 includes WMP10 and SP3 only includes WMP9 the slipstream can't work. The files required for WMP9 and WMP10 are different, but it is the service pack that decides which files will be installed, because the service pack may include new files of its own. Since XP isn't componentized, it's either the MCE2005 file list without service pack resource files, or the SP3 file list without WMP10. Neither will work, though it should be possible to merge DOSNET.INF and TXTSETUP.SIF manually. The XPSP3 team screwed up big time.
  2. you can activate an OEM version in just the same way as a retail version you can activate it as many times as you want, but it must be on basically the same hardware that's why OEM version is cheaper, it will work on that one computer, but it will not activate on different hardware if you swap too much hardware your OEM version may not activate again, as it is considered a new computer calling microsoft for activation may help, but in theory you are screwed OEM versions are great if you plan to install them on notebooks, because you can't change the hardware too much they are not so great for a desktop PC that you upgrade frequently, because sooner or later the hardware hash will fail NOTE: we are talking about an OEM version of Vista that you "buy" and which comes with a product key. the OEM versions that are distributed by Dell/HP/... are an entirely different thing. These won't activate on non Dell/HP/... hardware, with or without the matching product key, but then again, you didn't "buy" these. NOTE: there is no difference between a retail and an OEM disc, only the product key is different. the installation is the same, but OEM licenses are essentially locked to the hardware you activate it on the first time.
  3. ah nuhi, been a while the integrated DVD has the following: The boot.wim image has mostly 6001.18000 files The install.wim image has mostly 6001.18000 files Most other files on the disc are 6001.18000 as well The servicing stack is different, but 6000.16386 files are also on the disc, probably for backwards compatibility There are a number of extra Packages in the install.wim but I forgot to check the boot.wim Some of the Components have extra features, but nothing shocking, DisableWER is nice (error reporting off) I think you need the new servicing stack ON THE DISC if you want to integrate post-SP1 updates or use the new unattended features
  4. I have Vista installation media with SP1 integrated and it is very different than what you end up with after reverse integration. The setup.exe is different, the boot.wim is very different, there are extra folders that contain the new servicing stack, there are new unattended settings. Reverse integration will not do all these things. Stop promoting reverse integration of Vista SP1!
  5. You really need to get SP1 integrated media. Reverse integration of SP1 is a waste of time. You will only have SP1 in your install.wim and not in your boot.wim or any of the RTM files on the installation media. Updated boot drivers and new servicing stack won't be available during setup. I fully support customizing your windows image, but service packs are not customization, they should be done right.
  6. Reverse integration is also not the way to go, because you would get SP1 in the install.wim, but you would still have RTM in the boot.wim. It would just be a selfmade mess, if any of the boot drivers happen to be updated or if vulnerabilities in the WinPE needed to be patched. I see how integrating SP1 into Vista RTM would take a lot of time, because all the seperate images would need to be updated. I don't see how this would change for SP2, which can only be bigger than SP1. Unless you are supposed to integrate SP2 into an SP1 disc. I say get yourself some official SP1 media when it's released: either buy the software assurance discs for $10 or so, borrow somebody's retail disc, or download it somewhere. Packing an online image is for building a corporate install, that includes default settings, drivers and third party software, it was never intended for just integrating microsoft updates.
  7. You need to check the Windows AIK documentation on WinPE for more info. You need to format with DISKPART I believe or it won't work. In DISKPART run these commands select disk 1 --------------------------------------------- MAKE SURE THIS IS YOUR USB DRIVE FIRST: list disk TO CHECK clean create partition primary select partition 1 active format fs=fat32 assign exit
  8. I've had the same problem. Windows Vista BSOD while it is booting on its own for the first time and everytime after until I set SATA mode to ATA. Either you load a driver during setup (on the hard disk partitioning screen) or you add the driver to WinPE. Look for more info on peimg.exe /inf in the Windows AIK documentation. You need the driver in the boot.wim, I guess, but I haven't had time to do it yet.
  9. it works quite well, and the USB drive boots noticably faster than the DVD however installing from DVD extracts the OS image from the DVD onto the intended folders harddrive installation from USB drive copies the image to the a temporary folder on the harddrive BEFORE extracting it into the intended folders on the harddrive this leaves the overall speed increase open for debate of course it is very useful if you want to change your unattend xml or modify your configuration set easily
  10. It would be better if Microsoft did a little cleanup, by releasing an update rollup Anyone have any idea when that might happen?
  11. But you must use the corresponding PRO product key. *wink* So the OEMBIOS check does not fail and activation is not required. *wink* The OEMBIOS check only checks the hardware and the product key. *wink* Not whether it is Media Center Edition or regular. *wink* Windows does not check the product key to see if it is Media Center Edition. *wink* It checks... something else. *wink* Enough winking. I used Microsoft's Product key for preserving Preactivation. http://www.microsoft.com/technet/prodtechn...y/oempreac.mspx And I used the OEMBIOS files that came with my recovery CD. I was puzzled myself
  12. Just 5 files? MCE2005 has media player 10 builtin, while SP2 does not. The product key determines which version will be installed. Unfortunately there are no VLK product keys for MCE. So you can only mix and match between OEM cds.
  13. Right files, wrong product key: the one one the COA on the bottom of your Dell/HP/Compaq is a dud. For preactivated install you use the files mentioned, along with the product key in winnt.sif on your Dell/HP/Compaq install cd. Works for me, with extra benefits... @getwired: if you get a preactivated cd, like most recovery cds, the product key on the box can not be activated over the internet. regular oem cds work as usual, but recovery cds need a special product key. this way the oem product key on the box can't be reused. microsoft changed their policy on this a couple of months ago.
  14. And for Belgium that would be 720x576 @ 25Hz because we use PAL. As said, both widescreen and fullscreen DVD use the same resolution, but widescreen DVD are usually (but not always) anamorphic. This means the image in the 720x576 frame is stretched vertically. When displayed on a 16:9 television it is stretched horizontally, because of non-square pixels, and the image is normal once again. When displayed on a 4:3 television, one in four vertical lines is dropped. This will fit the entire frame on the television screen. Or the image is zoomed to fit, but then you lose the wide edges. When you are encoding for display on a PC, always use square pixels. Even when your PC is attached to a television, it is better to use powerstrip to force a true widescreen resolution.
  15. These private hotfixes are only intended to work around very uncommon problems in very uncommon situations. If you don't have that problem you really should not use them. They are not tested as much as public hotfixes and public hotfixes are not tested to work with private hotfixes. There is also no information as to when private hotfixes are superceded. You may be including dozens of workarounds that have been fixed by a single public hotfix. There is no indication that all these private hotfixes will be (or even be included in) the next service pack. The new service pack is likely to include new builds of all the core components, and many of the uncommon problems will go away and many new will appear.