• Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About Atari800XL

Profile Information

  • OS
    none specified
  • Country
  1. I'm using OSFMount for mounting iso's in WinPE (it's based on IMDisk). It's fully portable, I use it like this in (any) PE: -a -t file -f y:\portable\q.iso -m q: This example mounts an iso of portable software to letter Q: in PE. As I said, the IMDisk developer probably deserves all the credit, but for me OSFmount is just a bit easier because it is completely portable. The only problem I've found so far is it doesn't run in w10-10586x86 PE (it's fine in the x64 version, just not in x86). It looks like 10586 is not very good anyway (there are several problems with it), for now I'm testing build 14295 PE, and here everything seems OK again. If I only needed to mount iso's for WinNTSetup, I would have used the standard JFX method, but if you need it in PE for other things, OSFMount might be an option. I use it for mounting my Q: drive, but also to mount driver iso's for WinNTSetup. A script determines which hardware I'm on, OSFMount mounts the drivers for that PC (and bitness), then WinNTSetup is started with the "-drivers" command line option, and it integrates them just fine! I like this a lot better than manually inserting the drivers into the wim files (which can lead to all sorts of interesting problems).
  2. "Flashed", WinNTSetup supports Vista, I have done some testing on that last year (I'll try to find the exact post later). You just need to install it once in the standard way (create a usb, do a normal setup, sysprep, capture), then after that this .wim can be installed with WinNTSetup (without the system partition being "D:" instead of "C:") EDIT: Read the posts from 18 December 2014 onward in this topic. The next part of your question is not very clear, I'm afraid. You say that "from" and "onto" is not clear in your language. So please try to rephrase what you mean: Install XP **from** USB with WinNTSetup? YES, that's possible, I use it all the time... You can use a POS update pack to create a fully updated XP iso. Install XP **onto** USB? I would use a "live" XP for that, maybe try "Gena" from TheOven (google it).
  3. Thanks JFX, I really appreciate your help. This is a strange case, I never had this problem before (a driver that installs fine when done manually, but not automatically through WinNTSetup). I will try your suggestion ASAP and investigate further...
  4. This is the driver install section, it's in Dutch, but maybe you see something special, of course I can translate some sections if you want me to (just testing the new board "spoiler" thingy).
  5. Thanks for your reply, but I have those lines in winnt.sif already, it must be something else. It must have something to do with the fact that this might not be an official driver, I can't find any official download (just the DriverPackSolution version). As I said, manual install does work, after I click "continue anyway" at the "Windows logo warning" prompt. It's a a driver for ATI Mobility Radeon HD 4200.
  6. The new ini stuff looks very nice, I'm looking forward to testing it... In the meantime, I'm installing XP on a Compaq Presario CQ56, I've had a special request to install XP on it, and give it back with an easy way to reinstall it, when needed. Of course, for this purpose I'm using a WinPESE usb, with WinNTSetup. I'm making everything unattended and automatic, so I'm pre-mounting an .iso file with the needed drivers (found them in an older DriverPackSolution pack). I am using the "-L drivers:" command line, which points to the mounted iso. Everything installs just fine (as it always has, I've used this sort of setups hundreds of time), LAN/ WLAN/ Sound, etc. is fine, but the videodrivers seem to be unsigned, and don't install automaticcally. After setup, I get a yellow question mark, "the driver couldn't start", I have to remove it, reboot, then install the driver manually, click OK on "Are you sure you want to install this unsigned driver", and everything's OK after that. Now, I'm sure I'm overlooking something here, but is there anything I'm missing here, to make the driver work automatically with this sort of setup? Thanks!!!
  7. I make a new XP iso every month (with latest POS updates, using OnePiece DXUPAC-made addons etc). I always put a winnt.sif in the i386 folder (in case I ever need to install if from CD, which I haven't done for months). I only use this iso with WinNTSetup (boot from PESE usb, mount iso), using command line winnt.sif selection. I never have any problems with this, the winnt.sif from the command line is always used. About your other issues: Can't you automate this with command line options as well?
  8. Thanks ChrisR, good to see you're not in any kind of trouble with the ISP yourself. Thanks to JFX for letting us "borrow" this thread for a bit. Hey, WinNTSetup is already perfect, so there's not a lot of traffic here anyway.
  9. Does anyone know what's going on with Looks like somebody forgot to pay the bill? (Sorry for the offtopic, but maybe JFX or someone else knows?)
  10. Also, have you installed this on a multiboot setup? Did you let WinNTSetup change the boot sector?
  11. Yes, I use it for XP all the time. JFX even was so kind to include special modifications for it to work with OnePiece-pack created iso's. I created a new iso last tuesday, with the latest FinalXP pack from OnePiece, and the latest POS updates. I don't remember exactly if I saw your error codes before, but are you sure you included both text-mode and windows SATA drivers in your source?
  12. JFX, just had to share this: Just finished installing the new Windows 10 preview (14251 build), using WinNTSetup of course. Install went fine, even with all my usual tweak etc. All fully unattended, etc. I just find it so funny that WinNTSetup is installing this without a single problem, when even Microsoft's "standard" setup is refusing/ giving setup errors, etc. At least that's what I'm reading on all the forums. I must admit I usually only test new Previews (quickly) to make sure my normal setup and PostInstall still works fine (just to check if there are no unpleasant MS surprises or "features"), but I think this is another fine example of the power of WinNTSetup. WinNTSetup is the best!!!
  13. "When can we wait"? I guess you can start waiting right now :-) Just kidding, I think you should re-read JFX's last reply, I think you might have misunderstood the "That's easy" part...
  14. (about "capture" and the new Wimlib versions): I finally tested Wimlib (1.9.0b6) capture, to see how it compares to Dism in speed, and how much info is added (and displayed in WinNTSetup). The speed is really good, around one third (33%) faster than DISM, with comparable image sizes (2.66 and 2.7gb in my test). The latest Wimlib seems to automatically add all descriptions/ information needed, some of it seems to be different than DISM (with the same captured windows version), but I'm sure that can be solved. So thanks for the tips on Wimlib, JFX (saw you on the forum), great to see you helped out!!
  15. See, that's what I love about WinNTSetup (and the WinPESE projects) as well. Always nice to see the reactions of another fan... Thanks again to JFX for his continued support in 2016!!!