jaclaz

Good. Then it is the Linux based version. Possibly you can use a method similar to the one used in the mentioned thread: http://reboot.pro/topic/12406-editing-iso-files/ making use of isoinfo to automatically (by batch) find which LBA extents that need to be hooked specifically to the (ElTorito) device (or reading these data directly from the bootcatalog). I have never used it, but there is (for Linux) a "dumpet" tool: http://dev.man-online.org/man1/dumpet/ that may be useful jaclaz

Good question. You will need AFAIK to register the <<spam>> tool for US$ 23.75, JFYI: http://reboot.pro/topic/19715-windows-image-file-boot-wimboot/page-2#entry186856 http://reboot.pro/topic/19715-windows-image-file-boot-wimboot/?p=186871 jaclaz

zamarac, in the original post by cdob: http://reboot.pro/topic/20004-boot-a-acronis-true-image-2014-iso-image-with-grub2-at-uefi/ there is NO "extraction" of anything, a loopback device is "hooked" to a sectors extent. The extent is determined by the LBA addresses in the .iso that Isobuster should show. Maybe the .iso you have has different location (or extents). And of course, if your version is Windows PE based it will be completely different. You normally don't want to actually "know" what is inside (or access) the bootcatalog, but if you really-really want to, this (seemingly unrelated) thread might be of interest to you: http://reboot.pro/topic/12406-editing-iso-files/ usually (but not always) the bootcatalog is on LBA 32, just before the boot image, you can dump it and have a look at it's contents with a hex editor/viewer easily: http://will.tip.dhappy.org/projects/unsorted/xp_cds/eltorito_extraction.html http://wiki.osdev.org/El-Torito If it is WinPE based, it is possible that it has been "burned" with just the "bios" provisions and not with the "UEFI" ones, see this (also seemingly unrelated) thread: http://www.msfn.org/board/topic/172122-got-tips-on-how-to-make-a-bootable-cd-from-bootable-usb/ Can you post the output of a DIR /S command listing the contents of the .iso? jaclaz

Good news . (The new job : , not the fact that you won't be around much ). jaclaz

Maybe it would be easier to address the actual issues? Like (just ideas): http://www.atrandom.iansharpe.com/setres.php http://www.nirsoft.net/utils/wireless_key.html But you can of course save the Registry and restore it, simply it is not - as wimb said - the "right choice" as is it easy (as you just experienced) when merging registries to create unbootable systems. What are you using to build the PE? I mean "standard" WAIK/AIK/ADK or some Winbuilder projects (or something else)? jaclaz

Yep , but usually people that are allergic to command prompt window know how to hide it, as said there are tens of utilities that can have it hidden, but also making a batch and "wrapping it" in a .vbs should do, like: http://serverfault.com/questions/522255/how-to-prevent-schtasks-on-windows-7-from-showing-the-command-prompt-after-execu http://www.msfn.org/board/topic/78097-release-cmdhideexe/ etc. What I personally have on all my systems is nircmd (that can do that and much more): http://www.nirsoft.net/utils/nircmd.html but as said you will have to check if these programs work on your version of windows. jaclaz

Well in "Window" (and no, I did not missed writing the final s ) a botched z-order of windows is of very little importance as you should really (according to the good MS guys) have ONLY one window open, full screen. On the other hand, I would be interested in knowing how many people (excluded obviously the good Russians and the people in business with them ) have really appreciated the possibility of typing directly the new Ruble symbol, particularly through the OSK Virtual Keyboard, and were excited by this brand new feature... http://support.microsoft.com/kb/2970228/en-us jaclaz

Sure , but if the OCD actually causes "fits" when (if) a black window flashes briefly, it sounds as being at a rather preoccupying level. jaclaz

Wouldn't be more important to get cured for the OCD? Can you post the specific command line that produces the "command prompt windows flashing" when added to SCHTASKS? If this is confirmed, you can use any among the various different tools that "hide" that "command prompt window flashing", though I haven't tested any of them on 8/8.1 there are at first sight no reasons for them to not work. jaclaz

No. Meaning that a clone is a "clone". If there are CHKDSK issues, it means that the filesystem (or the new disk ) is not entirely "sound". You should make a (further) clone of the disk as is and then repair thoroughly the filesystem with chkdsk. It is extremely rare (I would say "impossible", but of course eveything is possible ) that a "good" disk, after a few CHKDSK (with the right options) passes is not fully restored to 100% working (unless there is some kind of hardware malfunctioning, let's say a flaky hard disk data cable, a corrupted driver or some "malware" of *some* kind). Since you just changed your old disk drive, it would not be such a bad idea to thoroughly test the "old" hard disk drive on another machine, as it is *possible* that the disk is fine but there is some other hardware malfunctioning on the machine (and this is the reason why the new disk has issues). In any case you can try (still you will need another disk if the "old" one is found to be actually defective and cannot be reused) to make instead of a "clone" a "logical copy", more or less what XXCLONE (don't be fooled by the name) will do: http://www.xxclone.com/ The data (but ONLY indexed/accessible data) will be on a brand new (freshly formatted) filesystem and CHKDSK will have no issues whatever with it. See also here (for an idea about the differences between different forms of cloning/imaging): http://www.msfn.org/board/topic/157634-hard-disk-cloningimaging-from-inside-windows/ jaclaz

It's strange, I thought that DWM was a "core" part of the GUI. Historically the whole idea of the "embedded" was that it is a "componentized" version of the main OS, so it all depended on which components were included at build time, but it seems to me that the good MS guys (how surprising ) have changed the approach and Windows 8/8.1 Embedded is seemingly a "rather normal" Windows 8/8.1 with "lockdowns" and "filters". Possibly re-deploying without the "ISKU-Embedded-Features" http://msdn.microsoft.com/en-us/library/dn609858(v=winembedded.82).aspx will make the DWM process run normally, but at first sight it doesn't seem like any of the lockdown and filters would stop it. jaclaz

Thanks for deciding to protect the innocents. jaclaz

Yep, it is very possible that your friend, when he installed the "new" windows overwrote the MBR (or the PBR or both) with a "normal" one whilst the Toshiba may use a "special" one, and the same may have happened for the \boot\BCD on the partition that MS calls "system"(and that is actually the "boot" partition) or for other settings in the \boot\BCD. JFYI, see these two thread (one about HP?s and one about Fujitsu Siemens, the former using a special MBR and the latter using the "Windows built-in F8 feature) http://www.msfn.org/board/topic/131620-hp-notebook-the-recovery-partition-could-not-be-found/ http://www.msfn.org/board/topic/128727-cant-access-repair-my-pc-option-via-f8-startup/ The applying of the .wim obviously affected only the partition to which it was applied, whilst re-doing the recovery "from start" (or however re-running the similar recovery before) recreated the "right" "special" MBR (or whatever). I strongly suspect that what the Toshiba uses is the "C:\Recovery\Windows RE\WinRE.wim you mentioned when the F8 is pressed. jaclaz

Well, you open the goflex case and find out if inside it is a 7200.11, If it is, then you can try the "fix". jaclaz

Hmmm. Both dribbel and dribble are behind the green glass door. (together with Kel and Larry but not ROTS) http://www.msfn.org/board/topic/149540-what-is-behind-the-green-glass-door/ jaclaz

Maybe Kel intended it using the same root as edible/edibility : http://dictionary.reference.com/browse/edible http://dictionary.reference.com/browse/edibility jaclaz

You see the not-so-trifling advantage of helping a local friend (as opposed ot a remote one)? Free Beer! Happy everything went fine, thanks for reporting and "finalizing" the thread with the procedure that actually worked. jaclaz

As written where? AFAICR the Xeno port to Windows 9x worked (on some hardware). Good. But I believe that once you "Like" a post, you can later "Unlike" it. Why not? Because business of can openers manufacturers may (hypothetically) become at risk ? (though only a few of them remain, I don't think they are registered as "protected species" ) jaclaz

No prob. ... everything is well that ends well ... jaclaz

If you read attentively my previous post, it is not at all related to the whining (and never said that you - specifically - were whining ) it was about the futility of re-doing here the debate about this should be default, no this other should be default, but it used to be this the default, no, it was this other one that was default, I had an OS install that had this as default, no, I had that same OS and it was this other as default, etc. And yes, after the debate, whatever the developer will choose as default, someone will come here and whine. jaclaz

Ow, come on . This senseless debate on whether Aero should be enabled or not when on battery dates back to Windows Vista , it has been talked about and everything (and the contrary of it) has been written about it, several OEM's provided their laptops with specific apps, tens of independent Authors wrote software to fine tune this (or that) aspect of the interface when running on battery and noone ever found a "one-size-fits-all" solution that prevented someone from whining about the default setting (whatever it was). It is about freedom, it is about having options to do what you want with the stupid GUI of the stupid OS, just like themes, just like having Aero enabled or not. The default for AeroGlass is to turn Aero off on battery. <- this is a decision by it's Author, the last character is a "full stop" or "period". This prevents the whining from people that like it disabled on battery, BUT it provokes the whining by those that like it enabled. IF the default setting will be changed to Aero On on battery, we will have all the people wanting it Off whining as well. A simple Registry edit or using the installer by moataz can change this setting in no time. Please read the above as "there is NO issue whatever", you can't prevent everyone from whining there will always be someone unhappy about any decision taken by someone else . jaclaz

Very little E, nothing M, and NO P, though. The device selling for US$ 5 is too similar to an urban legend to not be an urban legend, at first sight. However, as often happens, California came first : http://abcnews.go.com/US/video/car-thieves-tech-gadgets-baffle-police-18891078 It makes a lot more sense: http://jalopnik.com/whats-the-secret-device-thieves-in-california-are-using-471782175 that it is a sort of "RF brute forcing", and not a EMP device: http://hackaday.com/2013/06/09/ask-hackaday-can-you-steal-a-car-with-a-mini-tesla-coil/ Of course it is impossible to reproduce a signal like the original car remote: http://www.today.com/news/police-admit-theyre-stumped-mystery-car-thefts-6C10169993 Or maybe not https://eprint.iacr.org/2010/332.pdf http://www.theinquirer.net/inquirer/news/2285482/luxury-car-hacking-findings-blocked-by-high-court http://www.cs.ru.nl/~flaviog/publications/Gone_in_360_Seconds_Hijacking_with_Hitag2-USENIX_2012.pdf jaclaz

Also, remember that the Wayback Machine may have cached a lot of contents: https://web.archive.org/web/*/http://www.mdgx.com/ even if a file is not cached, it is sometimes possible to find it googling for it's filename. The ME SP1 Beta 9 should be the latest one on Mdgx site and it appears to be named: https://web.archive.org/web/20140729154329/http://www.mdgx.com/ http://www.msfn.org/board/topic/46581-98-fe-98-se-me-updates-patches-hotfixes/ MESP1.EXE and might (or might not) be found elsewhere on the Internet (or some member that downloaded it in the past may be able to find an archived copy and provide it). Hopefully Mdgx's site will be back soon . jaclaz

Well, then you will have to thank me (and the OP is very welcome to unthank me ). jaclaz

Well, you will need to make a post about the actual meaning of "Run on battery", and noone will actually read that post (just as they won't read any among the zillion post about the Registry battery setting on the Aeroglass threads). What will happen will be that they will instead make a new post whining not only about the Aeroglass not working but also about the "Aero Glass Customizer" having too complex options. jaclaz