Atari800XL

Thanks, the new and improved x64 W8.1 cpu check is great, along with the "save all productkeys"!!!

Thank you very much for the new version. Of course I already saw your message two days ago, but I wanted to wait for other reactions first. Well, there aren't any (yet). Now there must surely be (a lot?) more users of WinNTSetup, right? With every new version, I'm amazed by this wonderful tool, and of course the fact that you want to share it with us, for free! Thanks x1000 I like the new "Product keys" feature! It finds all keys on all my OS partitions. When multiple keys are found, only one is saved, is it possible change that, or to add "Save all"? The new WinNTSetup cpu check on the P4 (mentioned a few posts up) says it is W8.1x64 ready (but it's not). But never mind for now...

On a test of two systems, these were the differences in the CoreInfo ouput: Intel® Pentium® 4 CPU 3.00GHz Intel64 Family 15 Model 4 Stepping 3, GenuineIntel SSSE3 - Supports Supplemental SIMD Extensions 3LAHF-SAHF - Supports LAHF/SAHF instructions in 64-bit modePDCM - Supports Performance Capabilities MSRTM2 - Implements Thermal Monitor 2 controlCNXT-ID * L1 data cache mode adaptive or BIOSPREFETCHW - Supports PREFETCHW instructionIntel® Core2 Duo CPU E4500 @ 2.20GHz x86 Family 6 Model 15 Stepping 13, GenuineIntel SSSE3 * Supports Supplemental SIMD Extensions 3LAHF-SAHF * Supports LAHF/SAHF instructions in 64-bit modePDCM * Supports Performance Capabilities MSRTM2 * Implements Thermal Monitor 2 controlCNXT-ID - L1 data cache mode adaptive or BIOSPREFETCHW * Supports PREFETCHW instructionSo I concluded that it had to be Prefetch and LAHF/SAHF, as they were mentioned in the Windows 8.1 x64 requirements. Also, Windows 8.1 installs on the Core2, but not on the P4-630. But I guess everything might be a bit more complicated.

Intel® Core2 Duo CPU E4500 @ 2.20GHz Your console app reports: Windows 8 Support:+ PAE+ SSE2+ NXWindows 8.1 x64 Support:+ CMPXCHG16B+ LAHF/SAHF- PREFETCHW (AMD)But Sysinternals' Coreinfo says (Asterisk means: supported): CX16 * Supports CMPXCHG16B instructionLAHF-SAHF * Supports LAHF/SAHF instructions in 64-bit modePREFETCHW * Supports PREFETCHW instructionAnd Windows 8.1 x64 installs OK. ..so it looks your console app doesn't report PREFETCHW correctly (yet?). Thanks for picking this up anyway, after some more thinking about this, I do believe it would be pretty cool if WinNTSetup would report this info beforehand. Thanks!!

Would it be possible to let WinNTSetup check for the new Windows 8.1 processor requirements? As luck has it, I was testing on a p4-630 (which runs Windows 8.0 just fine), this system can't install 8.1 x64 because it lacks CMPXCHG16b, prefetchW, LAHF/SAHF. I used Sysinternals' Coreinfo.exe to check for these requirements. Of course the apply stage goes without problems, but on reset the system errors out. I think it would look really professional if WinNTSetup could check for this. Just an idea, please put it on the "maybe next year" list... Now I'm on to checking 8.1 x64 on more systems... EDIT: Hmm, never mind, forget about that, not worth the trouble, besides: easier to check in my own program prior to calling WinNTSetup. Thanks for listening, anyway...

Well, no bad luck for you on friday the 13th. I tested (my usual) triple setup W7/W8/XP on one PC, everything A-OK!!! Beautiful!!!! So now we're back to cosmetics-only remarks, because the only thing I noticed was the "ready?" screen timer counts down from 10 to 1 with XP (nt5) , while with W7/W8 (nt6) it doesn't count down, but mentions "30 seconds". Sorry, once a nitpicker... On to 3.0 alpha!

Can I test it please? (It's friday the 13th? Besides, you wanted a full week off...)

hexoxssaa, can you be a little more specific? What is going on, did you use WinNTSetup, and then your system driveletter was D: instead of C:? Is that your problem?

JFX, have a happy holiday, thanks for quickly fixing the last issue I mentioned in my last message. (I noticed you changed 20130907 to 20130907rev1 after I had written it). You didn't mention it, but I had a feeling I should check it out once more.,, The only driver you have to worry about now is the one driving you to the nightclubs

I didn't expect a new version so soon from what you said, but was very curious, so here we go again. (Just saw your message again from 28 aug, :"Please report any Bugs you find.", until you say otherwise, I will keep on testing and replying). A little Q and A: - Driverpath now modified with existing driverpackpaths?: YES (path is added, not replaced). - Driverpath takes *all* paths from supplied winnt.sif: NO (but that's OK, as long as we know the behaviour, we can work around that). - Winnt.sif looking good prior to reboot?: Hmmm, it has shrunken considerably, only a few lines left, not sure what that's about (lines like Productkey, Resolution, Adminpassword, etc are gone. Not sure about the consequences of that). - XP installs OK anyway? NO, this is what I get after reboot (after loading textmode drivers, translated): "Please insert the cdrom named 'Windows XP professional edition sp3' in the drive" Just reporting... I'm back to the previous version 20130904rev1 for now (and, of course, version 2.x). Too bad we can't just take the existing winnt.sif and only add the path of the newly added drivers from the "-drivers" switch. I know why this is, you explained that, but still, too bad to see that things have become a bit more complicated in this respect. Take your time please...

I was going to be quiet for a change, but I decided to modify my previous message with an updated and tested script, with comments, for people who are trying to figure out what all the fuss is about... But a funny thing happened that I had to share: - The "runafter" command doesn't seem to work (yet?) with version 3 and XP (nt5). Sigh... :-) just when I thought I had a clever way of working around the drivers thingy... Never mind, just thought I'd mention it. I will execute the command manually for now (it *does* work!), and try (again) to wait patiently...

I think the "one supplied by user" should naturally *replace* the winnt.sif in the xp source. The same goes for the first one in your list. The others look like they could/should be appended. I'll patiently await your best decision... Edit: Something like this might tie me over until a new WIP version (take your time!) (sorry, Autohotkey is about as fancy as I get) Untested Tested and working ; I use an XP source (iso) with already integrated DPbase mass storage; drivers, the paths to these drivers are located in winnt.sif, in; the variale OemPnpDriversPath; This winnt.sif file is located in the WinNTSetup folder, for easy; maintenance: when a change is made, there's no need to rebuild the iso.; When I use WinNTSetup (version 2.x), more drivers are added using; its "Add Drivers" option, this time from an ISO file (determined by PC; type, eg. video, sound, etc.). ; WinNTSetup 2.x **APPENDS** the paths; to these drivers in the OemPnpDriversPath.; The new 3.x version of WinNTSetup **REPLACES** the OemPnpDriversPath; when it adds drivers. In my case this means the MassStoragedrivers path; is gone, and XP won't boot from a SATA drive.; To solve this, I need to replicate the 2.x behaviour, and **APPEND**; the MassStorage to the OemPnpDriversPath.; Luckily, this can be done after WinNTSetup finishes, and prior to the; final reboot (that starts the XP setup) by using the "-RunAfter" parameter.; This script should be compiled with Autohotkey to ModifyDriverPath.exe.; Then the following switch can be added to the WinNTSetup 3.x commandline:; -runafter:"ModifyDriverPath.exe"; ===================================; This script starts execution after WinNTSetup has written all XP install; files to c:\; We now have to append the path in our original winnt.sif (from the; WinNTSetup program folder) to the modified (replaced) path which now; resides on the c: driveoriginalfile=%a_scriptdir%\winnt.sifmodifiedfile=c:\$WIN_NT$.~BT\winnt.sifIniRead, ExistingPath, %originalfile%, Unattended, OemPnpDriversPathIniRead, ModifiedPath, %modifiedfile%, Unattended, OemPnpDriversPath; Now we join the original path with the new path (using ";") and; write it (in textquotes) to the winnt.sif file on c:IniWrite, "%ExistingPath%;%ModifiedPath%", c:\$WIN_NT$.~BT\winnt.sif, Unattended, OemPnpDriversPath

Thanks. Good enough for me, take your time. I was just thinking: In V2, it could hardly be an "accident" that the path was appended instead of replaced. Isn't this the normal way of treating driverspaths?

Thanks guys. No, I did not know you were *not* the original developer. Sorry about that... Very strange about the driver line. It seemed so natural to me to just "add" the new path, instead of replace. So your advice would be to "take care" of that line myself, prior to reboot? If so, I'm still glad we figured this one out... Or maybe still a chance that WinNTSetup can use "add" instead of "replace" like in v2? I would really like that!

Your question: "In v2 do you have an winnt.sif file?": Yes, see point (1) and (2), these are from the working v2 version (2.3.6). To me (with just basic scripting abilities, no real programming) it seems like a case of path=oldpath+newpath, where maybe something has gone wrong :-) You *did* know you already coded this correctly in v2, right? If not, then who are you, and what have you done to "our" JFX

Maybe we're getting somewhere again. Babysteps... (1) Here's my (working and tested x1000) commandline for WinNTSetyp (2.3.6) WinNTSetup2_x86.exe -nt5 -source:k: -syspart:c: -unattend:winnt.sif -savedriveletters -drivers:L: -reboot (2) From that winnt.sif (which is a *separate* file, not in the iso): OemPnpDriversPath="Drivers\1;Drivers\2;Drivers\3;Drivers\4;Drivers\5;Drivers\6;D\M\3;D\M\A;D\M\AD; (etc.)! as you can see, the first 6 folders are my own pc-specific drivers, the rest is de Driverpacks Mass Storage drivers (method 1). The resultant \$WIN_NT$.~BT\winnt.sif indeed has this full line! (As confirmed from my folder with the saved setup files). At the very end, WinNTSetup adds ";DRV;DRV\1;DRV\2", etc. (From the mounted L: drive). Now on to the new version 3WIP: (3) Commandline is the same (with "nt5" without the dash, of course) (4) The separate winnt.sif is also the same (5) The resultant \$WIN_NT$.~BT\winnt.sif only has: OemPnpDriversPath="Drivers\1;Drivers\2;Drivers\3;Drivers\4;Drivers\5;Drivers\6" Aah, so I guess we found another thing: WinNTSetup 3WIP doesn't add the *existing* part of this line at the beginning. I must admit I only found this as I was typing this... I'll await your response, but it looks like this can be resolved?!

IT still doesn't work. Looks like there's still something wrong with the mass storage drivers. The install folders look OK this time ("almost" the same as the 2.3.6 ones), and the setup looks like everything's going OK. But the final reboot into XP fails (the quick flashing bluescreen looks familiar, like there are no SATA drivers at all). To me it looks like the drivers *are there* this time, but some setting(s) are still wrong/missing. Please let me know what I can do to debug this.

Oh man, I'm so glad you're still smiling... As I said, I was not feeling too good about this at all, luckily it's resolved, and just before dinnertime for me :-) I was just running another test copying the $oem$ folder manually (from the "old" folder) before reboot. I guess this test will be successful :-) So now you're saying copying the $oem$ folder wasn't even included in v3 yet!? Aargghh, now I want my money back! Oh wait... THANKS!!!!!

I don't use the DPBase option *in* WinNTSetup, the $1 folder is there already in the *source*. I'm really sorry to keep getting on about this, please tell me to shut up anytime. As you might recall, I copied all files from C: just before the first reboot using 2.3.6, I still have this folder so I can compare how the new version differs. Maybe we can take this one step at a time: The folder "old" (= setup files created by 2.3.6) *does* have the \oem$\$1\d subfolder (seems logical to me, as it's copied along with the full $oem$ folder, which also holds other stuff, like cmdlines.txt), while the folder "new" (= setup files created by 3WIP) does not. To me that looks like something is missing? I think we should "forget" about DPbase, and focus on why the $oem$ folder isn't copied?

Sorry, I don't understand your second sentence. Yes, I chose Method 1 in DPBase, and this way has always worked with WinNTSetup. What do you mean with: "Both versions actually setting..."? Both versions of what? Sorry... I was under the impression that using version 3 it might work the same as version 2.3.6? Once again: With the *same* source, version 2.3.6 *is* creating the \$1 subfolder, but v3 is not (and so the Mass storage drivers are missing in Windows). OK, another edit: I use DPMassstorage *before* I use WinNTSetup, to create the ISO. I *don't* use the WinNTOption "Run Driver Packs". I think this is the source of the confusion!? My XP iso (which I also use as source to burn a CD), has the $oem$\$1 folder "burnt-in", so it was automatically copied along, in older WinNTSetup versions).

I tested the new version, only upto just before the final reset (to install XP) but there's still no $1$ folder in $win_nt$.~ls\$oem$ ... I guess there's no point in letting the setup continue? I guess the oem folder still isn't copied? EDIT: For completeness, here's the structure from the same setup with 2.3.6: $WIN_NT$.~LS -$OEM$ --$1 ---D (Mass storage drivers)

Hmmm, sorry, things are getting a little confusing now. You say "driver integration was successful" and "in TXT phase the driver isn't installed". Maybe I don't understand you correctly, but going back (another testrun), I again saved all contents of C:\ just before reboot (after WinNTSetup finishes) so I can compare later. There is no $1 folder at all in $WIN_NT$.~LS\OEM$ (which normally holds the Driverpack folder "D" and all its subfolders). Maybe this is what you meant (or just the opposite). So now I'll have to go back *once again* and see if the failure to integrate the drivers is my error, or if WinNTSetup "forgot" to add them. EDIT: OK, went in one more time, looks like 3WIP "simply" (?) didn't copy the $OEM$ dir from my XP source, as it normally does... Any ideas? (Sorry, had to figure this one out in my mind. Of course the TXTmode storage drivers were there, but the Windows mode [sATA] drivers were not).

JFX, thanks for the new version. I just got home from work, but just had to check this new version out. Everything seems to work OK, tested XP setup on my testlaptop. One thing I wonder: what was the new method of installing XP all about? I now feel kind of "guilty" that you had to revert back to the "old" method? I hope you didn't have to do a lot of work for nothing? It's not that I tested on some weird config or something, I mean 512mb may be not be a lot for Win8 (even though it still installs fine, as you might recall), but for XP 512mb is OK, isn't it? Just wondering what your new method was... But as a conclusion from me, testing the new v3WIP version, everything seems to work great for installing XP/W7/W8/W8.1 from USB using Win8PESE. Again, congratulations on this new version, I hope it will take WinNTSetup into many more productive years!!! THANKS!!!! EDIT: Seems I spoke too soon. After the full XP setup, after the last reboot, Windows doesn't boot and errors out. So I tried again and noticed that -SaveDriveLetters didn't set the checkbox for "Use migrate.inf for driveletter preaasignment". So I manually ticked that box and thought that was it. After another full setup still no luck, no boot. I'm not sure what's going on, looks like the SATA drivers are not installed? (BTW: as I mentioned before, this exact same setup works with 2.6.x)

Now that you mention it, yes 8.1 lets you do this via settings. I assumed this was a reg tweak that applied to 8 also. If it was in 8.0 already, there would have been no reason to release 8.1

- click-click, you're aware that BootToDesktop is for Windows 8.1 only, right? - I agree with you on XP, please keep it around. I need it on several PC's that control weighing systems, etc. My tiny usb stick with Win8PESE, several OS install iso's and WinNTSetup are perfect for installing any OS anywhere/ anytime. XP will live on for years and years on similar systems, never mind the support. People seem to forget that some of these systems are offline, so even on XPSP3 without any further updates, they run perfectly fine. But of course, reinstalls always will occur due to hardware/ user failure, etc.