Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

POMAH-PRESS

Member
  • Content Count

    24
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

0 Neutral

About POMAH-PRESS

  • Rank
    whaaa?

Profile Information

  • OS
    Windows 7 x64

Recent Profile Visitors

1,072 profile views
  1. So when is version 3 coming out?.. Gonna be doing some lite'ing soon...
  2. Updated the package today. Changes in changelog.txt.
  3. Sooooo... Have you figured that out or what???
  4. Well, it's like it is written in the guide 1. You don't start run.cmd, in fact there is no run.cmd, not until you start USBMultiWimSetup.cmd. That's what you should be doing. To do that you boot into PE - the boot.wim from your installation media (you must put it on your USB drive as described in the guide). When PE boots and the welcome screen is shown you press Shift+F10 to start cmd window. Then you go to the root of the drive where your wims and xmls are and where your USBMultiWimSetup.cmd should be. If you're not used to cmd interface you can just type notepad there, then in notepad windo
  5. Yeap, that's the way to go I think... 7 and Vista should be deployed separately using this method. I didn't think about Vista when developing this anyway.
  6. That would be great and appreciated. Didn't get that.
  7. Well, I don't see why it shouldn't. I don't have any Vista's to test though.
  8. I've put together techniques from different guides and made a script that allows one to place several WIM's and XML answer files in some directories on one disk (USB, HDD, CD/DVD,...) and have them listed in script's menu after the installation media's PE boot. You can select an image and an answer file to use and start the installation. How it works. PE boots. If you've injected the autostart script into it - disks are scanned and when found USBMultiWIMSetup.cmd is started (if you haven't injected the autostart script you have to manually start the USBMultiWIMSetup.cmd from command prompt). I
  9. And those of us that have Win7 installed in drives/partitions other than C:\> are ready to test things when the updates/changes are made. +1
  10. Hey everyone)... Cool down, LOL)... I'm just saying I'll stick to vLite, for now... And then, well... We'll see)... And yes, having Nuhi back here would be really fantastic...
  11. Well, what Nuhi did several years before for Vista fully suits my needs today with my W7... And it is far more stable for me then this tool specifically designed for W7... vLite is a quality product, proven with time.
  12. Hahaha)))... What a nice progie))))... Good luck to you, Dev's... With that kind of attitude and... "quality")))... ChiefZeke: Thnx for clearing this up... P.S. : vLite and DISM rule!) P.P.S. : Nuhi is da BEST!)))
  13. Yes... Why? Is there a difference? Should I use x86 one? I'm on Winx64. Update: Tried x86 version 1.4.0 on W7 x86, same story, but I figured out a way to lunch the app by first pressing "quit" in an error window, and then pressing "Continue" in a second identical window. However, when I'm trying to do something I get the same error repeatedly... So no-go ( ...
×
×
  • Create New...