jaclaz

Well, what would have been the alternative, stealing 'em rights? jaclaz

@Steve Thanks, though at first sight I am failing to see why you are not using a FOR /L loop. Also, how long does the message: Sync cancelled. Logging off...stay visible on screen? jaclaz

For the record, a large part of the world does drink good coffee (of course NOT in ether Dunkin Donuts or Starbucks, but in real coffee shops/bars). Not so much unrelated to the way economical results of companies are presented or commented and to be tagged as part of Mr. La Palisse Corner: http://www.nber.org/papers/w19429 unfortunately the article is not free , unless you are from US Government or a journalist or live in a third world country (the political correct term is "developing country or transition economy"). The list of such countries - last updated in 1999 - includes (among many others): Andorra, Lichtenstein, Vatican City State, Gibraltar, San Marino <- among the countries with the higher income pro-capitaArgentina, Bolivia, Brazil, Chile, Mexico, Panama and Venezuela Iceland and GreenlandAll ex-URSS countriesChinaIndiaSingapore and Hong KongCzech Republic, Slovenia, RomaniaTurkeyI guess that something has changed in the world economy and the good guys over there (which by trade do high level studies on world society and it's economy, National Bureau of Economic Research) didn't have any time in the last 14 years to change the pricing policy and/or update the list of "countries in need that may be exempted". Basically if you are not one of the "elected", you'll have to fork from 5 bucks to have the pleasure to read the whole set of totally obvious considerations interesting article choking full of new findings, or use any proxy residing in one of the listed countries. Still for Mr. La Palisse Corner, but this time really OFF TOPIC http://www.nber.org/papers/w19521 jaclaz

It seems to me like Ponch "knows your question" alright. The issue here is that it seems like you "know not your question" (and it is not that re-asking it in the exact same way and without providing any meaningful detail will help much). Q.Can a standard windows XP Setup work in UDF? A1. A suffusion of yellow. A2. Try it and you will see if it does. A3. Who knows? A standard XP setup CD is CDFS (and NOT UDF) and there is not one reason in the worlds to try if it works as UDF. (as it already works as CDFS) Q. You mean that the "standard" Windows XP setup won't work in UDF or that the particular modified Windows XP setup I put together into a single 5 Gb .exe file(and that I won't detail how exactly I made) won't work? A1. Both, as a double suffusion of yellow (with some touches of orange). A2. Try them and you will see if they do. A3. Who knows? Noone ever made a single 5 Gb .exe file from a Windows XP setup. You are a pioneer in the field. Semi-random stuff: http://support.microsoft.com/kb/321640/en-us http://support.microsoft.com/kb/899527/en-us http://club.myce.com/f61/need-udf-file-handler-win-xp-277044/ jaclaz

More generally, it seems to me like you are slipping on a chocolate covered banana http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html Try describing what your final GOAL is (as opposed on asking how to solve an issue coming from a procedure that you think would be needed/useful to reach it). Or, if you really want to continue on that particular path, provide the Standard Litany, please: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html For the record, a CD or DVD does not normally have any actual "partition", it is usually a single volume, thus it may have a "filesystem", which can be CDFS or UDF commonly, but it is also possible (for largish files or if needed for any other reason) to use Hard Disk Emulation INSTEAD (this latter will actually have a partition and the filesystem of this partition can be any among FAT and NTFS). jaclaz

That tends to be an error (like electrical interference or bad/intermittent contact) in the actual cable/connector (SATA in this case). As an example, it was typical of ATA66+ IDE hard disk drives on 40 pin cable I would verify contacts/connector and try replacing the cable, before anything else. jaclaz

On other news (not really news, actually ) Linus Torvalds politely explained why exactly adding secureboot related features to the Linux kernel is not such a great idea: http://arstechnica.com/information-technology/2013/02/linus-torvalds-i-will-not-change-linux-to-deep-throat-microsoft/ and in some more recent ones , how random values should actually be random and NOT generated by a dedicated (proprietary) hardware: http://www.theregister.co.uk/2013/09/10/torvalds_on_rrrand_nsa_gchq/ jaclaz

According to my rough calculations, on 3rd June 2014 anyone will be able to get US $100,00 in cash if they collect a Surface RT from a Microsoft Store... jaclaz

Good. (which means bad ) So - since it doesn't work as well on another PC we can exclude that is anything connected to the OS (or it's Registry). And evidently also not the case (all parts of it) since the same disk in another case also fails to work. Next thing is to check if the drive is operational (it spins). For this test normally you can hear it (the motor whirls) as soon as you provide power to the case, if you are in a silent environment. If you hold the drive in your hand (flat/horizontal) and try to move it in a vertical position and back, you should feel "nothing" when the drive is powered off, while you should be able to feel the "gyroscopic effect", i.e. you will feel a kind of resistance while attempting to turning it. When you power it you may also hear/feel some "clicks" if there are none or just one or two it's ok, if more than that (like 8 or 11) there is an issue but it is another one . If the disk spins (and doesn't click), the next test needs a direct (SATA) connection to a (desktop) motherboard header (you might need a SATA internal cable), it is better if you also hook the disk to the PC PSU power header (i.e. do not connect - unless really needed - a disk powered through an "external" power supply directly to a motherboard SATA header). The idea is that once you boot the PC, you press DEL/F1/or whatever key is used on that PC to access the BIOS and try to detect hard disks. If it is NOT found, it may be a BSY (or BUSY) state. If it is found, but reported as 0 in size, it may be a LBA0 state. If it is found, but with some gibberish instead of a "senceful" device name/size is an alltogether different issueFor #1 or #2 the (hopefully) solution might be in the "monster thread" you already posted to, BUT you do not really need to read that thread, if you just read: the Read-me-first: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/the FGA's: http://www.msfn.org/board/topic/147532-fga-for-the-seagate-720011-drives/and Carter in Canada guide: http://www.msfn.org/board/topic/133387-debricking-the-seagate-drives/will be enough. After reading those, you should have a fair idea of the procedure and methods, and if you have further questions/doubts, you can post them (here or on the "mega thread"). 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