Atari800XL

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.

Thanks. The quotes did cause some problem somewhere, but that's not important. Thanks for the explanation, I will use L: from now on without the quotes. Please take your time for the next update, enjoy your weekend. (For me it's actually kind of fun to "play around" with this!). I will take this time to test W7, I don't expect any problems there. One question that was still on my mind: For W7/W8 I use -runafter:CopySetupScripts.exe (which is a silent WinRAR SFX) which I find very convenient (easy to maintain etc). I notice that "runafter" is launched from a cmd prompt (is that correct?) so a console window is briefly visible. Is it possible you could make some kind of "RunAfter" that doesn't show a window? No hurry, and also not superimportant, I was just wondering! Thanks!

Thanks JFX, looks like W8/W8.1Preview/W8.1WIP is sorted now, at least as far as I can see. Congratulations! I think the bits are now pretty much "burnt-in" to the partition (you know, like an old CRT) after a bunch of test-setups. So that's partition 2 covered. Leaves p1 for Windows 7 and p3 for XP. I'm testing XP first. Uh-oh, doesn't work. After the first reboot I get "not enough memory for iastor.sys". So I'm on to figuring out what's going on there. I rebooted in Win8PESE and copied all files from C: to a folder on another drive in a folder called "new" (for comparison). Then I formatted C: and started the *old* WinNTSetup with the same source. Right before reboot I copied everything to another drive in a folder called "old". Those two folders look quite different! I'll let you know the details later, but right now XP is installing with the "old" files on C:, just to make sure it installs OK! (which it does...) I'm not trying to take up all your time, just telling you how my test is going. Please take your time! If you already have an idea about what's going on, I'd love to hear it, otherwise I'll come back here later and pass along some more details about the differences in dir structures between "old" and "new". Seems like one has the driverfiles extracted while the other has them compressed. This might have something to do with it, but first I'll await the successful "old" XP install (to rule out errors in my XP source). EDIT1: OK, old setup went OK (as expected). Now back to new WinNTSetup again. Some details: (1)I launch it with commandline options, had to change -drivers:"L:" back to -drivers:L: (this was discussed before in this thread) (2) I see a yellow exclamation mark on "NTLDR PBR" which I never saw before. Not sure what that's about (never have trouble with booting, I use Grub4Dos after OS install, so I can boot from 3 primary partitions). OK, that's it for now, on to more checking and testing...

Nice! - You say "BootToDesktop" was not integrated, but I believe that one *did* work. Not important, now it works with double power. (1) Can you please make the "setup" button the default button again like in the 2.x version? This way, when I start with commandline options (and nothing has to be changed) I only need to hit "Enter" (VERY convenient! eg. when run from a hotkey). On the other hand, if I want to do some minor adjustments (say, a different wim, or a different unattend file for audit mode, etc), I only need to change a few thing here and there. This is what's so great about WinNTSetup!! (2) In the latest version, in the last screen (just before apply), the bootsector dropdown now defaults to "Do not update the bootcode". Is this by design? I would like it to default to one of the other options (not sure which was default before, bootsect.exe or bootice). I believe this changed in this latest version. Hope you don't mind the continuous testing, it's just a very nice task for my spare nc6320 sitting quietly in the corner...

Well JFX, sometimes I can't believe that not "everybody" uses WinNTSetup... These are just things I run into when using your fine tool... More hunting: (1) My unattended file is not (fully?) used, even though it's specified in the commandline (and also ticked and selected in the GUI). I'm sure you're aware of this? If not, let me know, I'll give more details (tested: The new W8WIP version, first with new WinNTSetup 3, then with old WinNTSetup 2.6.x. First setup was not unattended, second *was*). (2) BootToDesktop was not executed for W8WIP. Same story: 2.6.x: OK 3WIP: Not OK. ...although I must add that W8WIP setup using 2.6.x version stalled right at the end of setup [needed an extra reboot]. Not sure exactly what's going on there, but this might not be WinNTSetup-related. Needs even more testing (has the unattend.xml syntax changed? etc). Still, (1) and (2) above do seem to differ between 2.6 and 3. I'll await your response, we'll see after that. Please let me know when/ if a new WIP version becomes available! And thanks again for your programs!

OK, so both points were valid? Thanks, I will test further... EDIT1: Did a successful test with the new V3WIP version to install a W8 version that has been around as long as V3WIP. Works fine! EDIT2: Could it be that the commandline option "-reboot" doesn't "take" in the gui? (ie: the option is not ticked).

Thanks, I will test the new version with XP, W7, W8. Nice to see the commandline is still supported and, in fact, enhanced. As there is no new howto's as far as I can see, I assume the commandline in the testversion is the same as the last version in the 2.x branch. [sorry, didn't see/read the helpfile, didn't think it was available yet, as pressing F1 didn't bring it up. Turns out it *is* available from the sysmenu] EDIT1: First quick test: Boot Win8PESE, tccle prompt: WinNTSetup_x86.exe nt6 -source:y:\OS\w7.wim (OK, source detected) WinNTSetup_x86.exe nt5 -source:d: (Source not detected). When I select drive D: in the gui, everything's fine. Also tested with -source:d:\ -source:"d:" (d: is a mounted xp iso).