jaclaz

I don't get it, if it works for you, why you don't just use that? However there is (was) a freeware version of Registrar Lite, version 2.00 which is (was) probably the most similar to the one you posted about (actually IMHO "better"). It can still be found via Wayback Machine: https://web.archive.org/web/20050706043434/http://www.resplendence.com/downloads I have no idea if it works (never tested it) on later OS than XP. There are new versions (latest is on its home page) : http://www.resplendence.com/downloads currently 8.01, but for some reasons (which I cannot remember) I never upgraded. Try them and see if they fit the bill. jaclaz

To be fair the characteristic of Nostradamus "visions" are that they are not dated, not even approximately. Everyone of course can see the difference between "I see Windows 10 installed on a billion devices ..." and "I see Windows 10 installed on a billion devices by mid-2018.", the latter is now seemingly debunked, we will see if the first will become true, now worded as "I see Windows 10 installed on a billion devices, before or later ..." . jaclaz

Naahh, the drivers in use IN the laptop are "standard", when it is in the laptop the hard disk is connected directly to the SATA bus (nothing "USB related" is in use), the issue/conflict may be with the drivers used to have USB connectivity via the PCIe card, i.e. the "Renesas" ones. See if you can find some friend with another computer with a (surely working) USB 3.0 port (I hate to say this, but it could the one and only case where a system with 8/8.1/10 may actually have some use). The same (or another) friend may have a (surely working) USB 3.0 external hard disk that you could try attaching to your machine and even - possibly - try exchanging the USB A to USB C (I presume) cable. With these tests (depending on results of course) we may be able to exclude part of the possible culprits, and (hopefuly) pin down the cause of the issue (though even then not necessarily a solution might be available :(). jaclaz

Hmmm, I guess that if dencorso can post a (nice BTW) 10 years old totally unrelated graph, I can do the same, but at least one that is only 7 years old : http://www.mkomo.com/cost-per-gigabyte jaclaz

Since a weak WHAT? (result in spelling competition, I have to presume ). Seriously now, take care, sonny. jaclaz

You mean the "faster, shinier, better" editor, I believe. On a side note, but to connect to your comment, once upon a time (like in Babylon times) the architects and engineers were required to stay under the bridge they designed or built while it was load tested. We could do the same, send bunches of programmers to the moon (and possibly back) on vehicles governed by the software they wrote. We would surely have soon a sharp decrease on the number of programmers, but most probably have as a counter-effect some better software. jaclaz

100 Gb is a small (by today standards) disk, no posiibility that it is an AF disk, or similar the 7200.1 dates back to 2005 or 2006. The 0.58A does exceed (by itself, but the more if summed to the - low - amount of current needed to actually drive the controller/bridge inside the case) the (theoretical) amount of power a USB 2.0 port provides (though in practice most motherboards provide more power than the 500 mA of the standard) but (and this is the reason why Y cables were quite common in the past for 2.5" USB cases) one of the good things about USB 3.0 is the increase in available current, which is now 900mA. So it could be possible if it was the other way round, but is "queer", it is like it is "reversed". Could it be that *somehow*, *something* (possibly in the USB cable) triggers (improperly) a different UPD level and this *confuses* the power supply? https://en.wikipedia.org/wiki/USB#USB_Power_Delivery_.28UPD.29 Possibly totally unrelated but there is a nice guy that as a hobby tests USB 3.x cbales (USB C) for coompliance to standards and he has found MUCH MORE problematic devices than what was expected/expectable: http://www.extremetech.com/computing/225719-amazon-bans-cheap-usb-c-cables-in-wake-of-google-engineers-crusade https://docs.google.com/spreadsheets/u/1/d/1wJwqv3rTNmORXz-XJsQaXK1dl8I91V4-eP_sfNVNzbA/htmlview?usp=sharing&sle=true but even in this case the issue is usually that the cables allows to draw too much power (and not too less), examples: http://www.amazon.com/review/R1D8S7Y96B05RT/ref=as_li_ss_tl?ie=UTF8&ASIN=B010SFDKC6&channel=detail-glance&nodeID=2335752011&store=wireless&linkCode=sl2&tag=nexususb-20&linkId=74ee4588b47a5d6d1ebe27c9d323855f http://www.amazon.com/review/R1IFFRJQYIPG87/ref=as_li_ss_tl?ie=UTF8&linkCode=sl2&tag=nexususb-20&linkId=afa5cb960c9c041bace9b3dba8bd099c There is the possibility however that the cable creates *some confusion*, example: http://www.amazon.com/review/R1FNBAO3HQN3SN/ref=as_li_ss_tl?ie=UTF8&linkCode=sl2&tag=nexususb-20&linkId=0b0b6bf820789f8e9a882ef38edb658a As you declared initially , it is a strange problem. Now that we know it is a 7200.1, could it be the "power management" settings (though why this only happens with USB 3.0 is "queer", maybe then the issue is with the Renesas - or whatever- specific USB 3.0 drivers): http://www.thinkwiki.org/wiki/Problem_with_hard_drive_clicking IF the volume(s) on the disk (though clicking) is/are accessible through USB 3.0 a CHKDSK (as an example of an operation that keeps the disk drive busy) should make the clicking/ticking go temporarily away. jaclaz

Every time I read "faster, shinier, better hardware" i tend to mentally translate to "faster, untested, incompatible hardware" (partly because of the hardware itself, but largely because of the "faster, shinier, better" OS or software that accompanies it). Most probably the race to nonsense (in hardware) has slowed a little bit since Moore's Law trend is slightly diverging from hardware speed increase, and however we are nearing the limits of "practical" speed. I often think what the good people that worked on the AGC: https://en.wikipedia.org/wiki/Apollo_Guidance_Computer would have done if they had ARM dual/quad/octa cores CPU's like there is one in any recent smartphone. I mean, it wouldn't seem like rocket science nowadays.... , still try the procedure to migrate your phone directory from - say - a two years old phone to latest version of another manufacturer (different OS) phone, likely it will involve installing two communication suites (each several tens or hundred of megabytes) fight with USB cables/drivers/virtual ports, and what not only to transfer what could be (without loss of information) stored in a few Kb CSV file. jaclaz

Well, you actually asked for this : jaclaz

No, the BIOS is not (should be not) connected with device access at OS level. How big is the hard disk? (and which make/model is it?) There are some cases where an USB enclosure/converter detects wrongly sector size of AF disks, but I doubt that it is your case since when connected to USB 2.0 the same case/converter works, and in any case the symptoms would have been different (disk seen as Raw in device manager). The clicking you mentioned is actually strange. , if it was the other way round (disk working on USB 3.0 but not on USB 2.0) it might have been connected with "not enough power" but it cannot be the case on USB 3.0. There is another known issue with mismatch of HD geometry (a lot of laptops use/used 240 heads geometry on hard disk devices, whilst USB cases/converters uses the "normal" 255), but again that wouldn't cause normally the clicking. I see that the case is UAS/UASP enabled/compatible: https://en.wikipedia.org/wiki/USB_Attached_SCSI a loooong shot, but maybe *something* in the OS (for *whatever reasons*) talks to the device in "BOT" and the device replies in "UAS" (and thus they fail to communicate), this would explain why same device works connected to USB 2.0 port (which is BOT only) and fails when connected to a USB 3.x one, still the clicking remains a mystery. No other ideas right now . Post the details on the hard disk and on the drivers in use, someone may spot something useful to solve the issue. jaclaz

Frankly I don't know, but judging from the over-engineering, I guess that it would be much better to be subscribed than to pay for repairs once warranty has expired. Check contents of spoiler (components of a single, §@ç#ing hinge of a Surface): jaclaz

Windows 7 has not USB 3.0 drivers by default, you need to add/install a specific driver for USB 3.0, probably the reason is a missing or misconfigured driver, what do you see in device manager? See also: http://www.sevenforums.com/drivers/337753-driver-usb-3-0-pcie-card.html Or it did work with other disks (as USB 3.0) BUT not with the specific laptop hdd? jaclaz

@Windows2000 @Dibya Out of curiosity, what were the parts in the above that prompted the question and the answer? jaclaz

I will try to re-word my previous post, AFAIK the "Device and printers" is DESIGNED to NOT show any internal hard disk like device, so it would be interesting to know how exactly you had managed to make it/them show before. There is (was?) a known issue/bug on some motherboards/installs where an internal SATA device was seen as ESATA and thus did appear as external and was listed in "devices and printers", maybe that is what happened before to the 1 TB SSD, this Registry key "TreatAsInternalPort" may be the culprit, see: http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/my-internal-sata-device-appears-in-devices-and/722221d6-d59c-4cf7-803c-8203e6344b93 but that won't apply I believe to a PCIe SSD. jaclaz

Are you sure: 1) that internal hard disk like devices should show up in "Device and Printer"? 2) that before you installed the SSD the 1 TB SSD actually showed there? Last time I checked "Devices and Printers" listed ONLY external devices, if #2 is accurate it would seem to me like that was an issue, not what you describe now, which appears to me as "correct" or at least "normal". jaclaz

Only a (sorry) not particularly useful comment: mup.sys is usually a red herring, it is the last thing loaded properly BEFORE the one that hangs the system (which you don' t get to know because the system hangs before the related entry is written to the log.). jaclaz

BUT it is much more readable than CMD , at least according to someone (JFYI ) http://reboot.pro/topic/21074-windows-10-is-now-shipping-with-linux-command-line/?p=198581 jaclaz

Which errors? Please be explicit, report the EXACT errors and when they happen. Before needing to reinstall a whole OS they must be VERY SERIOUS errors. jaclaz

Well, specifically to the KB 8225688, I tested it and it worked fine for me, as said it may work or completely fail to, it is anyway worth a try. It worked for me BOTH in Opera (Presto) and Iron (Chrome) based, it may well depend to the location from which you request it. And the link was delivered fine to my (gmail) address. The actual download link leads to hotfixv4.microsoft.com, so this is another thing worth a try when looking for "strange" MS hotfixes: https://web.archive.org/web/*/http://hotfixv4.microsoft.com/* jaclaz

The tomasz86's repository is hidden here: BUT : jaclaz

Does either model run "Windows Mobile" (which is where you posted)? Anyway, the only possible advice is "do the right thing". You do realize that you already have a more than two years old, discontinued or obsolete phone, additionally only 32 bit: https://en.wikipedia.org/wiki/List_of_iOS_devices#Obsolete_or_discontinued_models What have you been waiting for to replace it with a newer model? Of course get a 6s plus as soon as possible, and then get a 7 (or whatever it will be called) as soon as it comes out, think about all the people seeing you with such an old phone, what are they thinking of you? jaclaz

Which ones? Here it seems supported: http://blog.livedoor.jp/blackwingcat/archives/1925833.html Maybe there is a mistake in the list of supported cards? jaclaz

@dencorso I know how Bell Labs/System V was not at all about freedom, but Linux (and derivatives) should be. The GNU approach on one side is a very good one in theory, in practice it creates more damages than needed. as a matter of fact its license is either non-enforced or non-enforceable, noone can really be sure to comply with it, giving it's verbosity, complexity, different versions/revisions, etc. the whole "fork" approach is something that may have been good in the good ol' days but currently the main effect is of having a zillion versions of everything (none actually working as it should of course) and an increasing number of difficulties in dealing with real devices in real world. Of course it is not the fault of the good GNU people, I am only commenting on the actual, real (terrible) situation we live in. The BSD license is IMHO much better, still it allowed the abomination that Mac OSX represents, a "free" OS that gives you not any degree of freedom. Android for certain aspects is even worse. jaclaz

So, since in your specific case the problem was fixed we shouldn't leave any hint/suggestion for other people that - having a similar problem - may actually need those patched files? Btw, my post hinted that WHEN: a hotfix is not downloadable AND MS has not a link to the hotfix e-mail sending service page,you can try to access that page nonetheless, and in SOME cases it still works: hxxps://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=<actual KB number>&kbln= As a side note: the thread is not titled "Please help me with all the issue I am having and will have installing Windows 2000", in order to keep things as easy to find as possible it would be nice if you could start a new thread for this new, different issue. It seems however that the issue was - at least partially - with your "WPA supplicant" and its configuration, just in case (and for other readers landing here): And also: http://w1.fi/wpa_supplicant/ Linux but there is also a Windows binary, cannot say specifically if it works on 2K. , let alone on a specific machine, it is largely a hit and miss game (with a lot of misses) when it comes to Windows 2000 and newish hardware/protocols. jaclaz

Well, you just deleted by mistake some 80 Gb of precious files, you are understandably preoccupied/under stress, it is unlikely that you would remember that, as well most - if not all - people will continue fiddling with the computer for hours, while I was trying ot make the point that the best (in the sense of action that provides the most probabilities of recovering deleted or lost files) thing to do is easy, pull the plug, as soon as you can, even shutting down the device through the OS could make things worse. Every hour, minute, second the machine is on there is a higher risk of *something* overwriting *something else*. jaclaz