jaclaz

Possibly yes, but I would first check a number of other things. An External Hard Disk Drive basically is made of four things: the actual hard disk drive the actual enclosure (metal or plastic case) some electronics (to provide power to the hard disk) some (more complex) electronics, including a controller that converts the hard disk bus (SATA) to the external (USB) busExcluded #2 above, any of the other three may be cause (or part of the cause) of your issue, to which you add that there could be similar issues caused by the actual OS install/Registry settings. If I were you I would start a new thread here: http://www.msfn.org/board/forum/169-hard-drive-and-removable-media-issues/ speciific to your issue. Once your issue will be diagnosed and will result as belonging to a "bricked" disk, you may be pointed back to here, but right now it is only a possible but not particularly probable. In any case you might need additional instructions/advice on how to disassemble that external case that surely do not belong to this thread. jaclaz

Two or three OS releases late , but still acceptable . You can however use slightly shorter poles safely, in case: http://www.msfn.org/board/topic/125258-nlite-and-microxp/#entry807225 Fair comparison of things that make sense tend to make sense. (but are often boring) Fair (or unfair for that matter ) comparisons of senseless things or comparisons between something that makes sense and something that doesn't, hardly so, but they can be fun alright. Windows 8 (8.1) is probably the first (and hopefully last) OS targeted to Media Center that requires an additional license to play a DVD.... Like, you know, compare a QNX RTOS against a with a 8.1 Media Center edition and see which runs smoother on a PC with the minimum requirements: http://windows.microsoft.com/en-us/windows-8/system-requirements Back to topic/idea, there is no "real" reason to make a "forensic sound" image, one can make it a much simplified (and smaller) backup through a number of approaches, it could be an idea to start a new thread on how exactly this can be done. (still it will be mostly boring and non-exciting IMHO). jaclaz

The Gimp? http://gimp-win.sourceforge.net/ should work with transparencies alright. jaclaz

Ask a polar question ..... http://en.wikipedia.org/wiki/Yes%E2'> jaclaz

Thank goodness de gustibus .... jaclaz

AS is not NS (i.e. ES2 which this thread is about). Check here: http://www.msfn.org/board/topic/153298-seagate-720012-fix/ jaclaz

There may be, as hinted in the given links TWO different problems that may cause that behaviour. If the target volume is formatted as NTFS and it is formatted as such on a later system, it is possible that the NTFS permissions get in the way. The specific BIOS of the machine (or an unsuitable command in device mapping) "confuses" the install routine.The questions I asked (and to which you did not answer) were asked in order to understand your current setup/procedure and (hopefully) provide some possible - if not solution - workaround. Standard Litany, please .): http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html jaclaz

Have you re-formatted the partition on which you are going to install XP (more exactly where the $Win_nt$.~bt will be written, to, usually the primary, active partition) through the setup? Or is it a NTFS partition formatted from the Windows 7? What is your partitioning scheme? Can you try (for experiment) to install to a FAT 16 or 32 formatted partition? That is an error (probably) that is connected to either NTFS/ACL permissions: http://support.microsoft.com/kb/246187/en-us or *somehow* with boot order/drive letter assignment, see this: http://www.msfn.org/board/topic/121114-sp3-usb-multiboot-10-kbdusdll-error/ And there is another similar issue in a seemingly completely unrelated thread (as well possibly connected with device order/drive letter): http://www.911cd.net/forums//index.php?showtopic=24880 jaclaz

This is just for Charlotte's interest, OBEY: http://www.iamanangelchaser.com/expressions/subliminal_screens/subliminal_screens.html jaclaz P.S.: Forgot the Wayback machine link to the "new" MS product: https://web.archive.org/web/20020811093649/http://www.microsoft.com/presspass/Features/2001/Sep01/09-20tvphotoviewer.asp

For NO apparent reason , I will risk a couple links to Commercial Products (Game Controllers): http://www.comfyland.com/products/comfy-products/iCam?Itemid=221 vs. : http://steelseries.com/products/other/simraceway-s1-steering-wheel But - in passing by - this is also worth some notice: http://steelseries.com/products/other/steelseries-touchscreen-gaming-controls jaclaz

If I may, instead of calling WDC_WD10EADS a "Caviar green" they would call them "slow molasses" the name would be appropriate, however there is a record for these "family" of drives to start becoming not responsive at boot time. I would thus additionally check the drive with the Western Digital test tools as the symptom may be connected to an actual drive issue. jaclaz

The generic idea is that if there is a facility capable of recycling in an area, and if the recycling method is convenient economically or approved by local Laws (and sometimes financed by the municipality/state), service companies or "aggregators" may decide to create "delivery points" or "collection points" in the surrounding area. See - as an example - what happens in New England/Massachussets: http://www.recyclingelectronics.com/index.php/About and they have "collection days", "residential pickup" days and CRT collection "events" : http://www.recyclingelectronics.com/index.php/Fundraising jaclaz

Well, the statement reported in that article: Implies that they actually borrowed affected Surface's from affected users (which - seen from another angle - plainly means that they were UNABLE to reproduce the issue on their own devices ). Now, I can well understand how a "race condition" (here probably created by some serious bug in sequencing/verifying the operations) is well possible, and that it can be a "rare" occasion, but it is the first time that I heard a software house incapable of reproducing such a bug on hardware they themselves produce. We have been told by the good MS guys for years that the blame for - say - 50% of the bugs in their stuff was because of third party hardware makers that badly implemented a standard or a guideline and that it was not possible to test Windows on all hardware, and that was the reason why the good Apple guys managed to produce less bugged OS (or at least less BSOD's - please read as unhappy faces), because they had the advantage of controlling the hardware manufacture. Now, that they are on a par, it seems to me like that excuse doesn't hold anymore. jaclaz

Though it is unlikely that anyone with a Surface RT will ever take part to this thread, and almost certainly not the tiny minority (0.1% or 1 out of 1,000 ) that managed to brick their device, I am wondering about WHY exactly the "recovery image", here is the article on The Verge containing the Official statement from MS: http://www.theverge.com/2013/10/21/4861538/surface-rt-recovery-image-windows-rt-8-1-update-issues has a filename of "Surface RT 8.0 North America.zip" (and no - as a side note - they haven't yet understood how spaces in a filename may create issues, as an example I am seeing the actual URL as download.microsoft.com/download/8/3/7/837ABEB8-D419-43E0-8C7F-474004F2C016/Surface%20RT%208.0%20North%20America.zip) jaclaz

In windows 8.1 sidebar icons/glyph are lighter and tend to float towards the top of the screen when compared to 8. jaclaz

As a comparison (related to my previous post, and thus as well OT), the good ol' way to do things (... and we liked it ): http://blogs.plos.org/neurotribes/2011/11/22/the-sketchbook-of-susan-kare-the-artist-who-gave-computing-a-human-face/ jaclaz

Meanwhile, in Cupertino : http://reboot.pro/topic/19077-where-ios-7-icons-created-in-microsoft-word/ jaclaz

Nice, he is making (much better than me) those same points. JFYI (and as a side note) a real-life experience on how a trifling thing can be made (unneededly) complex: http://reboot.pro/topic/15207-why-everything-is-so-dmn-diificult-a-web-quest-for-ddexe/ Not that finding a file or the other on MS servers is any easier, mind you. jaclaz

bummers! May I then ask WHEN will it be available? (just to do so before anyone else asks that ) jaclaz

If you disconnected everything how can it boot (at all)? (there would be NO devices to boot from) You should be able to ONLY access the BIOS with everything but keyboard, screen and single stick of RAM connected. Anyway, there is not much else that you can do, the only things remaining are to try (won't likely change anything) disconnect the clock battery for - say - half an hour (with the PC of course disconnected from mains) and re-flashing the BIOS (but I also doubt that the symptoms may be connected to this). Before trying the above, if that BIOS has a "reset configuration data" (or something similar) provision, try using it. As well try (if you have such an option) to set "safe settings". You can try to run the Lenovo diagnostic utilities see the hardware manual here: http://support.lenovo.com/en_US/guides-and-manuals/detail.page?DocID=UM000486 maybe they can pinpoint a specific issue/defect. jaclaz

My bad . So it is needed to add the /SEC parameter or explicit /COPY:DATSOU (or as suggested use the /COPYALL). Editing previous post to avoid confusion.... Anyway testing with a subset of files is recommended. jaclaz

Actually, JFYI, the - I guess only - CRT glass recycling plant in the US is near NY: http://www.nulifeglass.com/index.htm (it is supposed to be the "cleanest" of the possible alternatives ) jaclaz

Try disconnecting EVERYTHING, leaving connected ONLY monitor and keyboard and a single (surely working) RAM stick. What happens (please describe) when you boot in this configuration (you may want to disable BIOS splash screen - if any - and attempt to reach the BIOS setup through it's hotkey, should be Ibelieve F1 or F2 on Lenovo's )? How much slow is to get to the BIOS setup page? Since you have another PC of the same model, next test would be to transplant (temporarily) the PSU (Power Supply Unit) of the other PC onto that one and see if anything changes. jaclaz

Robocopy is the tool intended to be used to keep all permissions: http://ss64.com/nt/robocopy.html Since parameters are complex and not very intuitive, I would recommend you to do a few experiments before issuing the command on the "bulk" of files. Some help may come by the use of one of the GUI's for it (a few more are listed at the bottom of the page for this one): http://betterrobocopygui.codeplex.com/ Since /COPY:DATS /COPY:DAT is "default", it is very possible that a simple command like: http://superuser.com/questions/562375/how-to-copy-only-new-files-and-only-those-that-are-modified-after-a-certain-date Robocopy c:\ e:\ *.* /MAXAGE:20130301 /XO /Ewould do, as in the above link, try with the /L switch to verify if the result is the one expected. BUT THE ABOVE WILL NOT COPY THE SECURITY AND OWNER PERMISSIONS, so you will need to add the /COPY:DATSOU or the equivalent /COPYALL switch. Also, you should check if the actual permissions/security info of the backed up files is valid (this may depend on HOW exactly the backup was made and on which filesystem). jaclaz P.S.: Edited to correct wrong info, see below post by Yzöwl

SCOOP! Here is a prototype of the MS steering wheel 8.2! jaclaz