Jump to content

getwired

Member
  • Posts

    231
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by getwired

  1. Vista WinPE isn't terribly different from WinPE 2005 at this point, with one exception, which is boot from WIM. Otherwise, it's effectively identical...
  2. I think he was probably looking for a legal and supported way to do this.
  3. Extenders only show the Media Center experience (ehshell.exe), they cannot show anything else, or run any other application(s).
  4. I think they were probably looking for a legal and supported way to do this.
  5. BartPE is a reverse engineered version of WinPE - and that comes with all the fun (sarcasm) caveats of any reverse engineered product. Caveat haxor.
  6. You both missed the window for this - it ran for several months late last year and early this one. You'll need to buy a copy from one of the resellers carrying it (NewEgg, etc.)
  7. Alas, WinPE was not engineered in quite the same manner as XP Embedded or Windows CE. You must resolve any API dependencies yourself. If you are developing an actual solution and licensing WinPE from Microsoft for redistribution, there is some rudimentary help they can offer if you hit hiccups - but generally you are on your own.
  8. Ah. For the minimize, look in OC.bat. That's the file that launches OC2.bat, which is the one that runs minimized. Can't remember it off the top o'my head.
  9. NTOSKRNL.exe, and no, they aren't interchangeable.
  10. VB and WSH aren't interrelated at all - if you add the VB binaries to make WSH work, you'll be adding two unnecessary binaries. Odds are, if you are getting an error of some kind, then the COM object(s) you're interacting with are missing some dependency or registry entry.
  11. No, VB is not a requirement for WSH to work. If it was, WSH could not run on Windows 64-bit versions, where there is no version of non .NET VB. I think something failed to register... Does it work if you change: CreateObject("wscript.shell") to WScript.CreateObject("wscript.shell") ?
  12. http://news.com.com/No+Vista+Beta+2+this+y...6_3-5975648.htm Second half of 2006. Anyone care to place a wager?
  13. If the HAL is different, it isn't supported by Microsoft. Taking a Sysprep image of an ACPI system to a non-ACPI system won't work and isn't supported. Taking a PIC MP image to an APIC MP system won't work either. APIC UP images can go to APIC MP systems and vice versa, and PIC UP images can go to PIC MP systems and vice versa - but neither is supported to go to an ACPI or non-ACPI single-processor system.
  14. Yup, it is - or at least the product key you have used there is using a key generator.
  15. WIM = Windows Imaging. Believe it or not, the M doesn't really stand for anything (not Management, not anything). The M is a placeholder to create a third letter, so the files would have a three letter extension. Really. Think of WIM as an analog to Ghost/Powerquest formats of the past/present. It is file-based, as you've read, and that allows for countless advantages - namely aggressive compression, single-instancing of shared files (even across image captures), and more - Longhorn WinPE, for example was engineered to boot from within a WIM file to save space - it takes up almost no space as a result, since the majority of it's files are shared with the version of Windows it is installing. Note that the previous poster was not quite correct - WinPE stays completely compressed in the WIM, even when booting. The WIM is simply an overlay on the RAMDisk - files are never decompressed. Look for information on the Windows Automated Installation Kit and you should find some more info about WIM. Note that the version of WIM available today (in the SMS OSD Feature Pack) is only capable of editing by extracting the image and recapturing/appending. The version of XImage (the WIM capture/apply tool) included in the WAIK is the first version which has key Longhorn functionality, mount and modify (think editing an image from Explorer or the command-prompt as easily as adding or deleting files from your own HDD). HTH
  16. Business Desktop Deployment (a whitepaper/architecture to help enterprise customers deploy) and Operating System Deployment - a component of SMS Service Pack 1 that helps with Windows Deployment - uses WinPE and an early version of the Longhorn WIM infrastructure to help companies upgrade to Windows XP.
  17. Actually to RAMDrive boot properly, you will need Windows Server 2003 SP1.
  18. You don't need syslinux or pxelinux to PXE boot WinPE from an ISO into a RAMDisk... you need a PXE server - it can be RIS, or any other - and WinPE - but that's it.
  19. Booting WinPE from PXE (via ISO RAMDisk) isn't exactly easy to set up - so the steps that are there - while I agree they are convoluted - will work... Good luck.
  20. If you have a properly licensed copy, the directions on how to do this should be in the media and tools that came with WinPE.
  21. 1: It's prosecute , not persecute. 2: Microsoft never said, "it's okay", they just haven't prosecuted anyone for copyright violations, yet. 3: I'm not arguing to be arguing, I'm arguing because most people here don't seem to comprehend the very finite differences between "Bart{E" and WinPE. The builder has everything to do with it, as that is the part that Bart reverse engineered. Microsoft had their own build tool set (mkimg.cmd, etc) and Bart engineered a set of tools that did effectively the exact same thing, plus was able to integrate in his "plug-ins". 4: It's not Windows XP as a product, it's a set of features that were consciously designed as a separate technology, WinPE - which happened to ship on the same codebase, and even on the same day as Windows XP. It is reverse engineering the build process - it's a TEXTBOOK EXAMPLE of reverse engineering, in fact. 5: As noted before "BartPE" is no "OK'd" by Microsoft. Nobody has been prosecuted for using it, yet. I'd hardly call me uninformed on this matter.
  22. Not boot a RAMDisk FROM floppy, no. You can use a system that supports PXE, or a PXE emulation boot floppy (RIS has one, and two companies - Em-Boot and Argon Technologies) make them... Then you can PXE boot to a RAMDisk.
×
×
  • Create New...