jaclaz

The good MS guys made a mess. There is (was) three main types of product (both CD and License) that could end up in the hands of a "final" user: 1) FULL <- you can install it on *any* hardware (and change hardware any time you want, as long as you don't run concurrently more PC's than licenses) 2) OEM <- you can install it on *any* hardware (and then changing the hardware is not allowed - though technically possible - and usually MS would re-validate it on new hardware, provided that some reason is given, like replaced motherboard and similar) 3) Large OEM <- you can install it only on the hardware for which it is licensed (and then changing the hardware is not allowed - though technically possible, and usually having MS re-validate it was difficult or impossible) The last one later evolved in OEM SLP (used by very large OEM's like, say DELL, HP, Toshiba, etc.), where activation is not needed at all, as it is automated through a code embedded in the BIOS of the machine it is sold with. nlite is only a tool, to give you an example of a possible use (on a "same" computer) you may have bought a PC with a SATA controller but you would be forced to install XP in "IDE compatibility mode" (slightly slower than "pure" SATA) because the SATA driver is not included (slipstreamed) in the install CD and - for whatever reasons - you cannot go throught the "traditional" F6 floppy routine to install it. jaclaz

It is entirely possible that they took the servers down recently, tough I doubt they did that in march 2017 (as in the given link). The OP managed to connect with the automated phone activation servers just fine (so they still exist) the issue here is that - for some reason - the procedure didn't work. The MGADIAG however says: so, if I recall correctly, SLP cannot (and never could) be activated online, they are intended as self-activating IF they find the same hardware they were released for, But not really my (narrow) field of competence. So, if OP is using the same hardware, then the nlite *somehow* made the install not valid (changed/removed OEMBIOS and related files?), while if the hardware changed then technically the license is not valid. jaclaz

Maybe she was one of the common (usually outsorced) "first level responder" which often, not always but often enough, are clueless. The MGADIAG tool is something you need to download from MS, here: http://go.microsoft.com/fwlink/?linkid=52012 And here you can find some basic usage instructions: https://www.raymond.cc/blog/checking-genuine-windows-and-making-it-genuine/ jaclaz

Hmmm. Maybe it is a "specific" thing for the "specific" (you choose, it's a mess, version, release, SKU, whatever) "item" you have in your hands, but I still don't think that they (again, product code, activation number, whatever) can actually "expire", while it is possible that (again for whatever reasons) the thing was somehow "blacklisted". I mean, if the activation wasn't working in an absolute way (i.e. it was intentionally "retired" by MS) the telephone method wouldn't have even looked up for the number. I suspect that for one reason or the other you are in a situation similar to this reported one (circa 2008): https://askleo.com/why_cant_i_activate_windows_xp/ maybe triggered by some "aggressive" use of nlite. If you google a bit around you will find a number of ways to "force" activation, but if not directly to the "dark side", they belong to a "gray area", so, sorry but I can't provide you with a direct link to these resources jaclaz

How exactly MS expressed this? I mean, did you phone them and talked with a representative, or e-mailed them, or what? Latest news I recall were that normally both "online" and (in case that failed) "automated telephone" worked still just fine, maybe they just changed something recently? jaclaz

To recap, I offered what I had, and tested one of the possible solutions (wscript sendkeys as they are said everywhere to be able to do that) and found out that for *some reason* the method doesn't work specifically for sending an ALT SPACE LETTER specifically to cmd.exe. So the sendkeys method that generically works just fine specifically doesn't work (at least here), so it does not represent a possible solution (unless there is some trick to have it working for the specific task). jaclaz

I think I have to give up , but I will try yet another time, Sending *any* keys/text via sendkeys works just fine on cmd.exe here, including commands like dir, echo, etc. BUT the sequence (via Sendkeys) ALT+SPACE DOES NOT. If I issue a ALT SPACE I (italian equivalent for the english ALT SPACE N) I obtain a space an a I on the command line. Still here, the SAME sendkeys script to *another* window (I tried Notepad) works just fine with ALT+SPACE. FINAL recap: The OP may get away with his request by issuing a ALT SPACE N (or I, etc, as said this is language dependent), so the only interesting thing is to succeed in specifically sending to cmd,exe specifically ALT SPACE N, so anyting else (that is working just fine) doesn't matter. With "normal" keyboard keypresses just entering ALT and space opens the dropdown box, and then the following letter is the choice. With sendkeys (as said here at least) sending ALT and space does not, it simply adds a space on the command line. jaclaz

Did you try the actual sctipts? The ALT+Space (actual keys) do work on all windows, it is the wscript SendKeys method that doesn't work here, for CMD.EXE only. jaclaz

But seemingly you tested *everything* BUT the ALT+SPACE combo (i.e. the one needed and that doesn't seem to work on cmd.exe, it seemingly works just fine on - say - notepad). Maybe a wrapper *like* Conemu is needed (but not applicable to the OP situation) jaclaz

The "close" X can be disabled, but then again that would require *something* that you don't want, i.e.: http://www.uwe-sieber.de/files/consolenoclose.zip But if the (small) cmd.exe window falls "inside" a largish HTA Windows you should be able to bring that HTA window to the front via VBS, can't you? But is it a HTA now?, wasn't it before a second cmd window? @gunsmokingman Any idea why the sendkeys method that as said works just fine in Notepad doesn't work in the CMD.EXE window? :unsure: jaclaz

Just for the record, besides the language dependent issue, I tested using sendkeys, and it doesn't work (on my XP), the cmd prompt doesn't open the menu with ALT+SPACE (it works just fine with - say - Notepad). It seems like half the internet is full of this, here is a clear sample of the VBS code: https://stackoverflow.com/questions/10964630/how-to-mock-the-background-window-to-active-state-using-vb-script but it simply doesn't work for a CMD.EXE window, here is said that is should work on 2K and XP (but it doesn't ) and that it doesn't work on Vista and 7: https://groups.google.com/forum/#!topic/microsoft.public.scripting.wsh/rPS5OUmixU4 A workaround (not a solution) may be to issue a (say) MODE 14,1 directly from batch, then issue a (say) MODE 80,25 to "restore" it jaclaz

That is in English. In Italian it is ALT+SPACE, I , in other words it is language dependent.. I know, I did read and perfectly understood the question, then I asked another question, strictly related, and made a suggestion, not strictly related, but solving the issue nonetheless. I have to guess that the art of being polite is lost to you. jaclaz

Which (simulated) keypresses need to be sent (to minimize/restore the command prompt window)? I would rather try Nircmd, cmdow or similar. jaclaz

Just in case , standard litany: https://web.archive.org/web/20160604095422/http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/problem-report-standard-litany.html jaclaz

... which creates the questions: Is it possible (and if yes, how) replace the wdfldr.sys 1.9 with a newer one? Is the "newer" backwards compatible with the wdfldr.sys 1.9? Or in other words, is there a way to "update" the boot.wim and install.wim in such a way that is compatible with both "old" anf "new" drivers using the co-installer (regardless if they are these specific VIA USB 3.x drivers)? jaclaz

Looks like a Conexant modem. (ISDN? ) If you don't use it, it would make IMHO more sense to just disconnect/remove it. jaclaz

Good . The DON'T PANIC (in large, friendly letters) is not so casual , there is a huge emotional component in doing this kind of repairs (besides steady hands also a not-so-faint heart is needed). Yet another happy bunny in the basket : jaclaz

No need to. Usually when cdob posts something, it is: 1) accurate 2) tested (unless explicitly marked as "experimental") 3) working In this case the "experimental" thread was: http://reboot.pro/topic/16769-usb3-issues/ while the given one: http://reboot.pro/topic/21231-can-w7-be-booted-from-usb30-port/ is AFAIK/AFAICR "final", but you seem like being in a yet different case, with VIA hardware (and drivers), so you will need to adapt the batch or change manually the relevant keys. jaclaz

Then this is another (entirely different) issue, the .iso actually boots, then *something* else (which includes your unattended file) makes the stuff not working for installs. This has nothing to do apparently with the creating of the .iso, as long as the no-emulation bootsector is executed and loads setupldr.bin, and this latter goes on for the very initial part of the text mode setup the .iso is fine. You will have to post your unattended file, hoping that someone can spot where the issue can be, Also please describe (as much as you can) what actually happens. A good (alternative) idea would be to attempt the install/booting in a VM and create a video of it, so that willing helpful members can understand at which step (and how) the booting fails. jaclaz P.S.: did you use this: https://msdn.microsoft.com/en-us/library/dd458832(v=winembedded.20).aspx https://msdn.microsoft.com/en-us/library/dd458837(v=winembedded.20).aspx https://msdn.microsoft.com/en-us/library/dd458830(v=winembedded.20).aspx as reference, right?

Well, the EXACT hardware you have, the EXACT drivers you added and rhe EXACT way you have integated it (and the EXACT Registry changes you made) may make a difference, anyway try this: http://reboot.pro/topic/21231-can-w7-be-booted-from-usb30-port/ jaclaz

Queer. I see no reasons why Imgburn could have issue creating a "no emulation" el-Torito bootable CD, the setting you posted seem fine, unless -somehow- the cd.img has not been extracted correctly. Try using another program to extract the bootable image, see: http://reboot.pro/topic/12406-editing-iso-files/ for various alternatives, but in this case you can use 7-zip just fine. jaclaz

What is "cd,img"? How big is it in size? (in bytes) jaclaz

No problem with speed/power, but how would you actually scan "real" (paper" documents? An entry level but good fax/printer/photocopier (B/W, laser, NOT one of those stupid inkjets that would cost a fortune on proprietary ink) is likely to be in the US$ 200-300 range, example: https://www.bestbuy.com/site/brother-mfc-l2740dw-wireless-black-and-white-all-in-one-laser-printer-black/8162187.p?skuId=8162187&ref=199&loc=zhehdLHc0f8&acampID=1&siteID=zhehdLHc0f8-sfLxRnYXElBe4FHA5887sg If you have some old (usually SCSI) scanner a suitable printer to revive, then it's another thing, of course. jaclaz

Good (both for you and for the others). What I was missing (and still miss ) is any connection(s) with the WannaCry/Wannacrypt patch Microsoft issued for XP wihich this thread is about . Most probably there is one (or more than one), but I failed to understand what this/these is/are. jaclaz

Sure, but that has nothing to do with a service (or *whatever*) watching it. jaclaz