Atari800XL

Thanks harkaz, can you tell us which modifications you made (and maybe where this particular version is from)? So we can apply the changes to localized versions and/or for "safety"'s sake? Thanks!

Yes, working now in normal XP. So what error message would that be? It correctly asks to download the files now, so I'm wondering now what has changed, I certainly did not change anything on this particular XP setup. Thanks again JFX, you're the best!!!!

Thanks for the new version. A quick test in 32bit XP (old laptop) doesn't seem to work, though? When I start WinNTSetup_x86.exe, there's just a quick flash. Maybe something's going wrong in checking for/ loading the tools? When I add the tools from a previous version, everything works fine in PE, but on a normal XP it briefly flashes, then quits. Test in (normal, not PE) 32-bit Windows 7: OK Test in (normal) 32-bit Windows 8.1: OK So it looks like starting from XP doesn't work, I'm not sure since which version this is the case, it's not a problem really, just wanted to mention it. If running from XP is no longer possible, maybe you can add some sort of warning, instead of just exiting? As I said, no biggie, thanks again for the new version!!!!

Well sorry, I screwed up yesterday (must have had my tests messed up somehow). The new beta2 works perfectly on the new (unchanged) Nonno pack, I can confirm. Works with both "XPSP3 with NonnoPack" and "XPSP3 with NonnoPack + slightly nLited". To be sure that beta2 indeed is the solution here, I tested again with the previous WinNTSetup version, and as expected, the 5 files were not found. For that case, there's the "add the files manually" solution. So the new beta2 is VERY welcome after all! Sorry for confusing things... EDIT: To make this post slightly more useful, I would like to add a little plug (advertisement) for Nonno's new pack. One of the great things about it is that you can enter these settings in Winnt.sif, to turn off certain components you don't need in a setup: (and of course, with WinNTSetup it's easy to have more than one Winnt.sif around). eg.: [Components] ... WDSearch = off ... These are the components you can add here (use the component name on the left only, followed by "= off"). BitLockerToGo = BitLocker To Go Reader BrowserChoice = Browser Choice DirectX = DirectX Post-SP3 Update ICCDSCD = Windows Feature Pack for Storage IMAPI2 = Image Mastering API MDX = DirectX Managed Code MSXML4 = MSXML 4.0 SP3 Parser (KB2721691) MU = Microsoft Update NETFX30 = Microsoft .NET Framework 3.0 Service Pack 2 NETFX35 = Microsoft .NET Framework 3.5 SP1 NETFX40 = Microsoft .NET Framework 4 PowerShell = Windows PowerShell PowerShellISE = Windows PowerShell ISE Silverlight = Microsoft Silverlight WDSearch = Windows Desktop Search WgaNotify = Windows Genuine Advantage Notifications WinRM = Windows Remote Management (WS-Management) WRMC = Windows Rights Management Client XP_EOS = Microsoft Windows XP End of Service Notification

bphlpt, thanks, and yes, I agree with you. It's up to JFX... I will test the new beta2 again with an unmodified OnePiece pack (maybe 2 or 3 more times), but if it still doesn't work, I really don't want to "bother" JFX with it anymore, specially when the "manual" method works OK.

OK, here's the deal: Test 1: Took Nonno Fabio's tips to edit entries.ini, zipped up new pack, made new iso. Tested: Didn't help. Test 2: Used new WinNTSetup beta2: Also didn't help So it looks like JFX's original suggestion was the most simple and the only effective one so far: Just manually add the files to the iso. JFX, if it's up to me, you can remove the new "copy the 6 files" feature in beta 2, the previous version worked perfectly well as long as I add the files manually... (just for the record: beta2 doesn't "hurt" when I add the files manually, it just seems unnecessary now.).

OK, I will test as soon as I can. Remember, these issues were only with the new OnePiece pack, my other source had no problems, I hope the new change will not affect other sources...

In the meantime, Nonno Fabio has added another workaround/ solution to modify the new updatepack specially for WinNTSetup: http://www.ryanvm.net/forum/viewtopic.php?p=136877#136877 Everybody's so friendly and helpful!!! I will test this later today, if it works, then maybe there's no need to change anything in WinNTSetup, but of course that's up to JFX, I guess checking the files won't hurt either? Thanks...

Thanks JFX, that's a very clear explanation (even for me...). So you think you can add a special "OnePiece UItimate Post-SP3 pack" check? That would be great, no need to add them manually then... I couldn't fully understand, but these 5 files (or six?), are the only "problem cases"? Once again, thank you very much...

"OnePiece Alb" made a quite lenghty response on the RyanVM board: http://www.ryanvm.net/forum/viewtopic.php?p=136874#136874 Maybe you want to check it out. Most of this stuff is going over my head, but I will try to understand, I will read it more throughly when I get home (at work at the moment).

But we can agree that OnePiece created a very nice new pack?

YES!!!! That did the trick! Thank you!!! You really are THE MAN, JFX! I will make a post on the RyanVM board, i just hope I won't be treated *too* harshly :-) http://www.ryanvm.net/forum/viewtopic.php?t=6438&start=2900 As I said, OnePiece is sure there's nothing "wrong" with the updatepack, and of course I believe him, but do you have any idea what the cause might be of this? Of course, the easiest way is for "us" here at the WinNTSetup forum is to blame *them*, and for *them* to blame WinNTSetup. Never mind, the important thing is I now have an extra brand new "Ultimate" XP, which might come in handy sometimes. (There are still a lot of expensive [industrial] peripherals that "happen" to be connected to XP PC's!!) So if anybody's looking for a localized "Ultimate XP", look here: http://www.ryanvm.net/forum/viewtopic.php?t=10445

Thanks, I will check it out someday... I've also tried the new Nonno Fabio "ultimate" Update pack last weekend. Looking good, and he was kind enough to build it in a bunch (around 20?) localized versions!! I tried the Dutch version. Now I know JFX doesn't like "nlited sources", etc., but this one (as I'm sure you know) is very clean, it only requires one RyanVM run, then one DPbase run for storage drivers. I tested it and it works OK, it just can't find 5 files at textmode filecopy stage (ie4uinit.mui, iedkcs32.mui, ieframe.mui, mshta.mui, msrating.mui). I mentioned this on the RyanVM board, they told me to install from a normal CD first. It's just that I never use CDs/DVDs anymore, only Win8PESE from USB, never had any trouble with using WinNTSetup with XP installs for two years now, even with my somewhat "thrown-together" iso (well, it might sound that way, but it's actually very "clean": Dutch updatepack from oct/2013, NetFX and IE8 addon packs, then nLited with newer hotfixes, no tweaks or weird stuff except for classic setup screens, DPbase for storage drivers). I've used a selfmade monthly updated iso this way for months, never any problem. And I still use it (mostly on offline systems now). So please could you give any hints or tips on how I can prevent the "not found" errors on the new Fabio source? Maybe the entries in txtsetup.sif and dosnet.inf will help (I must admit I don't know myself what these mean, I just provide them for info): txtsetup.sif (looks like these are the only files with both "_x" and "244", not sure what that means...): ie4uinit.mui = 100,,,,,,_x,244,0,0,ie4uinit.exe.mui iedkcs32.mui = 100,,,,,,_x,244,0,0,iedkcs32.dll.mui ieframe.mui = 100,,,,,,_x,244,0,0,ieframe.dll.mui mshta.mui = 100,,,,,,_x,244,0,0,mshta.exe.mui msrating.mui = 100,,,,,,_x,244,0,0,msrating.dll.mui dosnet.inf (double entries!) d1,ie4uinit.mui d1,ie4uinit.mui,ie4uinit.mu_ d1,iedkcs32.mui d1,iedkcs32.mui,iedkcs32.mu_ d1,ieframe.mui d1,ieframe.mui,ieframe.mu_ d1,mshta.mui d1,mshta.mui,mshta.mu_ d1,msrating.mui d1,msrating.mui,msrating.mu_ I've tried removing the double entries, but that doesn't seem to work either. Any tips would be very welcome, but if you can't be bothered, that OK as well, I have my "other" source as well, and as I said, that version is working perfectly with WinNTSetup. Thanks guys!!!!

Thanks JFX, specially for the info that there is a lot more work involved to create a hardware independent XP image. I think I will pass on it. I just didn't know if there maybe were new developments in this field, etc. (I was wondering why you added the new functionality). Keeping w7/w8.1 install.wim files up to date is enough work for now :-) Even the latest 8.1update files are not without "issues". I was used to modifying new Windows 8 install.wims with DISM (adding netfx, removing most AppxPackages), but with the new 8.1update iso, I even have to add kb2934018 in the wim, or else the new ("Update") install will require you to install the "Update" all over, straight after a fresh new install! (Unbelievable...)

Thanks JFX, I must admit I never tried sysprep with XP, but I use it with W7 and W8.1 all the time. I'm not a pro, but I do like creating updated install media, and through the years I figured out how to do it. For XP, I just created my latest (final?) iso, using RyanIntegrator (for updatepacks and addon packs), nLite for latest hotfixes, DP for sata drivers, then Ultraiso for adding everything to a multiboot iso thingy, etc. etc. I can use this iso for burning a CD (if I ever need it for an old system), or for using with WinNTSetup, of course. For W7, I install a clean wim in audit mode, let it update, generalize/shutdown, capture. For 8.1, I install a clean wim in user mode, let it update, enter sysprep, cleanup image/ resetbase/ etc, then capture. As you can see, I have some limited experience with this, but just in a very narrow field. My question is: What is the advantage of using sysprep with XP, how can I do that, maybe you can link me to some info? That would be great, I'd love to try it (only if it makes sense, of course). Thanks JFX, you're the best!!!

Well, not exactly normal (it only appears in some very specific circumstances, 8.1 only) and I'm still not sure we're talking about the same thing, but we'll let it rest (once again), there are more important things. I'm curious to see what 8.1.1 will bring...

So you're saying it's normal that a full-screen "Metro-like" screen is apearing at the end of setup? (I don't like it). It's not *after* setup, but *at the end*, so that's why I thought that maybe there could be a way for WinNTSetup to prevent it. I will do another setup in a minute, hope I can catch the exact text and details of the screen. EDIT: The install.wim I'm using is original, but I added netfx3 (dism enable-feature) and removed 20 appx packages (Remove-ProvisionedAppxPackage). You don't think this extra setup screen tries to make me me re-install these again (when it sees I only have one Metro app: "Store"), do you???! No matter what, it would be nice to prevent it... Other people use the word "Kiddy screen", that's how it looks to me. EDIT2: Last setup I did: No animantion/ extra screen. Weird. Some extra info: the first setup I did was with the install.wim I mentioned above. I used this install for an "update run": I let it update, enter auditmode, generalize/ shutdown, capture updated win. When I installed using this updated wim, the animation wasn't there. So I guess my conclusion for now: It only appears with an original wim? Ah, we'll just forget about it for now... Thanks for listening anyways!!

JFX, did you ever have that new Windows 8.1 setup animation right at the end of setup? It only appears on PC's that are online at the time of install. It looks like the "old" Windows 8 animation (that I turn off with WinNTSetup using -win8noanimation, of course). It says something like "You can now download aps from the store". As I said, it's just before the desktop appears. Anyone else notice this or know about a way to turn it off? (Just realized I've used WinNTSetup for 2 years now, never used a normal Windows setup since!!)

I share your enthusiasm, thanks ChrisR for all your work.

Well Jaclaz, you're making a lot of sense, thanks for your contribution. I'm certainly not in the category of users who want audio/ full hires, etc. I don't even need net connectivity most of the time. It's really quite amazing how flexible the project is, when it can serve "minimalists" and "maximalists" at the same time. About your "seperated disk image", I use something like that. I have most standard WB/SE project apps deselected (actually: removed) and only use a few tiny scripts, one of these is for autohotkey.exe (just the exe and the main ini with "runonce" code and key assignments). I use this as an autorun, on boot it mounts a file called "q.iso" as drive q:, this iso holds all my portable aps (Acronis, HWINfo, TCCLE, WinNTSetup, XYplorer, my favorite viewers, editors, packers, fonts, etc. etc). Almost all of these are portable, only Acronis needs a few driver files installed in a script (so along with the Autohotkey script I have an "Acronis drivers" script, same for Macrium mount drivers and AOMEI drivers). Total for my "Scripts-Aps" folder is 4mb (which makes for super fast builds, specially with extracted wim files) Total for my q.iso (the portable aps container) is 172mb (super easy to maintain and update, one large iso files copies to USB a lot faster than hundreds of small files). Do you think something like this (well, more the way *you* described it, maybe) should be built into SE, or do you think it should be left to the users to decide?

Thank you ChrisR (and all contributors), the best PE project just got even better...

Wow, almost three weeks without traffic. I guess WinNTSetup has reached the point where it is 100% perfect, and so easy to use that there are no further questions or criticisms. Congratulations, JFX! Maybe it's like Windows XP, I've heard it will only need a few more updates before it will be perfect as well! (sorry, didn't mean to compare these two, just kidding).

WinNTSetup and Bootice, is there anything they can't do? (Tried my first Bootice multi-partition USB stick today, nice to have a small partition on my large USB to put those Grub4dos-loaded PE isos, which can't be fragmented of course. Now I only have to empty/ format that small partition when there are new versions, and can leave the large OS isos on another partition, ready for install with WinNTSetup.)

JFX (or xcv150, who brought up GPT ESP partitions), I was interested in JFX's example of creating an EFI system partition with Bootice. In your example above, it looks like you're creating an NTFS partition of 10gb, while "create ESP" and "create MSR" are both selected. As I don't have a GPT disk to test on, please could you explain how this is done? Does Bootice "subtract" some mb's from the single NTFS partition to create those two partitions, or are there more screens after this one where you select those sizes? I *have* done some rescue/ repair work on newer laptops (using W8PESEx64, on secureboot systems), but no reinstalls yet, so I was wondering how to go about it if the situation would present itself. Right now on MBR disks, I never use the "extra" partitions (seperate boot/msr/recovery), so I would imagine on GPT, I would only create the Fat32-ESP and use the rest for normal partitions. As Bootice can be nicely "integrated" into WinNTSetup, this would seem like a great (and simple) setup. I was just wondering if this way of thinking is correct, any comments are very welcome.

Sounds good. So to be clear: esd files are compressed better, but take longer to apply? If that's the case, I'm not sure I would like them for normal use (I like faster apply better than smaller size, but I'm sure it could be useful for some). Those LSMS compressed wim files are created by using "/compress:recovery" with DISM? That's how I understood it, but it really doesn't make sense... ("/compress:lsms" or something would be clearer, but that's Microsoft for ya...)