dencorso

Another fine alternative formulation is: The patient's condition has evolved... ... to expiry!

Of course it can! When that free thing gathers your private info and sends it elswhere to undisclosed parts, it becomes (at least potentially) monetarily expensive... and actually behaves as a trojan horse. You see, the horse was free, but cost Troy its actual existence (can anything be more costly than that?).

In the deep blue sea, circumnavigating the world with Mr. Belfiore? I wouldn't mind if Joe found a nice tropical island (the more remote the better) and decided to stay there... and invited some of his cohorts in Redmond to join him. They might as well start a coconut water and fried fish parlor there... I bet it'd be more profitable than Windows Phones...

From a command prompt impersonating the TrustedInstaller one can also freely edit the registry with Regedit...

Try: if /I "%COMPUTERNAME:~0,4%" == "home" goto :home goto :end :homecopy c:\test.txt "%programfiles(x86)%\Adobe\Reader 11.0\Reader\" /fstart "" "%programfiles(x86)%\Adobe\Reader 11.0\Reader\AcroRd32.exe" /fexit :end

Sure we do understand one another, Noel! What is curious is that we actually have exchanged positions. Now your position is clearly more radical than mine. Yet, my position didn't change any. I have, from day one, decided to avoid all patches intended to "ease" moving to Win 10, as well as those intended to perform the actual move. But just those. Meanwhile you've lost any faith you still had in MS. And I do think you may as well be right to distrust them absolutely. I've still to reach that point myself, but I'm not quite there, yet.

While that's certainly true, and applies also to older OSes, BTW, this thread in particular is about those "updates" that are clearly unnecessary and/or ought obviously to be avoided. So, we must strive to keep the 1st post as up-to-date as possible, right ? @JorgeA: Thanks for the heads up, and for helping keep this thread up-to-date! You rock!

Thanks for the heads up!

Even when using non-lossy formats, like GIF, TIFF or PNG, when a image is shrunk, there'll be less pixels per feature than originally, so that resolution is therefore lost. For enlarging, one may even use refined methods of pixel interpolation to restore some of the lost resolution, but the results will still be less satisfactory than the original, non-manipulated image.

But it could as well give some feedback as to why nothing is listed... even if, of course, no news == good news!

They may work fine , but the drive letter N: is nowhere to be seen in the output, which should mean that it is not a partition that is mounted to drive letter N: . Of course! N: is a 12.5 GB Gavotte Ramdisk !!!

All 3 work OK ... see, for instance: N:\>WMIC Path Win32_LogicalDiskToPartition Get Antecedent, DependentAntecedent Dependent\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="C:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #1, Partition #0" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="D:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="E:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #2, Partition #0" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="F:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="G:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #1, Partition #1" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="H:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #2, Partition #1" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="I:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #3, Partition #1" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="J:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #3, Partition #0" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="K:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="L:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #8, Partition #0" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="T:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #8, Partition #1" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="V:"\\MACHINE-NAME\root\cimv2:Win32_DiskPartition.DeviceID="Disk #5, Partition #0" \\MACHINE-NAME\root\cimv2:Win32_LogicalDisk.DeviceID="Y:"

Something is not right... sorry! Here's what i get (after pressing the <SpaceBar>, of course!): N:\>logphysThis cmd has been run from LogicalDrive N:\Press any key to continue . . .N:\>

Well, in that vein, Windows 10 er... X might as well mean "eXtreme Surveilance Version"...

Well, at the end of the day, that's exactly how it should be, because higher Win version can only mean much more bloat, unfortunately!

One must understand this actually is a brave new world: for now, we´ve already got a continually involutionary OS (viz. Win 10)... underflowing beer glasses should be the next step, logically! Then again, better not start holding your breaths too soon...

... and I bet it'll be the 1st post of a brand-new member.

As I see it, a better analogy would be you go to sleep on your own bed and wake up in it... then as you go outside, you notice it's not your neighborhood at all, anymore, and someone passes by you and says, quite merrily "good morning, Number 6!"... Of course, dhjohns, you're much welcome to present your perception of it, and I'm, in fact, glad to see, at least for you, 10 is not bad at all.

Sure! You're right and it's official! It's already available here: sw_lic_full_installer.exe as the non-adware English EXE version...

And that is why I use Windows XP SP3. It is even more secure. Now, let's let things as they are, my friends: no reason to start a session of "did NOT!" / "did TOO!" at this point, right? We all know and respect each other's positions, AFAICR... right?

The link I gave, namely: sw_lic_full_installer.exe always points to the current (= latest) non-adware English version... It's actually a permanent link.

hmm probably that then +1

No issue taken. Then again, the link I gave is to the official non-adware installer (yes: there are two types of installer!)...

Shockwave 12.2.1.171 (EN) is out!

Does it happen regardless of filesystem or is it a NTFS-only issue? BTW, xxcopy makes sure to copy both long and short names and to keep them synchronized.