jaclaz

Knowing how generally Japanese people (and possibly Japanese CEO's are better at it) are usually very formal, polite and diplomatic, if Osamu Suzuki: https://en.wikipedia.org/wiki/Geo_Metro described it as "a fishbone in my throat" there must be a reason.... Making a joint venture between Japanese and Americans to have a car made by Canadians? jaclaz

Nice! Also: http://www.msfn.org/board/topic/113791-uberskin-theme-velvet98/ http://tihiy.net/uber/ (maybe useful) However: but maybe ... http://www.msfn.org/board/topic/116260-shell-95-update-project-sh95upd/ http://www.geocities.ws/liuwoonyung/SH95UPD/index.html jaclaz

The 127 was actually considered one of the BEST cars around at the time (in it's class of course) and much, much loved . It was the direct counterpart to the Renault R4 and later of the R5 and (very like them) it was practically indestructible, extremely reliable and even when something went wrong it was easy to repair/fix. The "real" 127 had the 903 cc engine of the 850 "Sport" (with reversed rotation) which was in itself an evolution of the engine of the 600, and extremely reliable/tough, later some "sport versions" and the "made in Brazil" Rustica (147) http://www.targhenere.net/gallery/photogallery.php?photo_id=4937 had a senseless 1050 cc engine that burned more fuel than you can imagine for all in all a very modest increase in performances. Just like Panda's of the first and second series (and all R4's and first series of the R5), unless the body had corrosion issues, after many, many years of service you would normally have to put 'em down (with much grief ), as they still somehow worked, without maintenance or care, they insisted on running.... jaclaz

Maybe Cleartype? (but it shouldn't be in XP) jaclaz

Well, there is always Murphy's Law hanging around, the cable may stick in the "full throttle" position while you drive on the highway and you will have issues when you want to low down/stop (say beacuse a car in front of you brakes), it wouldn't be a UA event but a CS (Cannnot Stop) one . Still OT , one of the most curious cases of UA was on some old car models (never happened to me recently or heard of it lately, but it happened more than once in the good ol' days) with Diesel engines having a depressor pump for power steering/braking. Basically you had this nice, self igniting Diesel engine running rather hot on an accurately dosed mix of air and diesel fuel, then, all of a sudden the depressor membrane broke and ALL the lubricating oil in the engine was sucked in the intake, becoming to all practical effects fuel and revving up the engine to the max. You had to be quick in depressing the clutch, find a nearby wall or a ditch, and turn the engine off by "pushing" the car against it in 4th or 5th gear, as the engine would seize up in no time. jaclaz

Yep , let's just say that - curiously enough - at the time it had a much lower selling price than other comparable cars. I wonder WHY exactly that happened. jaclaz

Sure, and you also liked/like Vista, I like coincidences . jaclaz

And now that the actual issue is solved , let's talk of whiskers (tin ones ). I would assume that people at NASA are not particularly interested in sponsoring old technologies http://nepp.nasa.gov/whisker/index.html http://nepp.nasa.gov/whisker/reference/tech_papers/2011-NASA-GSFC-whisker-failure-app-sensor.pdf and while my laptop may well represent a non-mission-critical item, possibly the accelerator pedal sensors in my car might be thought as rather important . Personally I would like NOT to be involved in a UA (Unintended Acceleration) event ... jaclaz

Well, what do you do when you are looking to buy a car?you go to the car dealer and see what is on salein no more than 10 minutes you decide which model(s) you are interested in, basing the decision on price, features and looksif possible you arrange for a test drive for ONLY the model(s) that you fancied in #2 (in other words, you are not going to test drive a yellow 1977 Ford Pinto Cruising Wagon, because you excluded it because on how ugly it is ): jaclaz

It is rare the occasion to disagree with Dencorso, so I'll take it swiftly . Sooner or later, if you give different drive letters to same volumes (under different OS) or same drive letters to different volumes you will delete or overwrite the "wrong" file (actually the "right" file, but on the "wrong" volume). There is NO requirement WHATEVER for XP (and I believe for later Windows as well) to have C: (as a matter of fact NT based systems were designed to NOT reside on a primary partition. MS (as often happens) has it "reversed".when it calls the volumes "boot" and "system": http://www.multibooters.co.uk/system.html And even Windows 9x can be installed on an extended with a couple tricks, the only "real" requisite is that the DOS system files are on an active primary partition on first disk, which will be "C:" under Windows 9x, and to which you would normally have the NTLDR/BOOT.INI/NTDETECT.COM and/or the BOOTMGR/\boot\BCD. (and while it is a nice thing to have and very handy, there is no real *need* for grub4dos in a simple double or triple boot setup). jaclaz

The ATX is actually (as "form factor") an "industry standard", it's dimensions (and location of screws, etc.) are documented: http://www.pcguide.com/ref/power/sup/form_ATX.htm so, instead of posting the dimensions of the (stupid) HP "original" PSU, it would be easier if JorgeA could check it against the above specs. It would be NOT the first time that HP uses a non-standard case/PSU, but most are actually "standard" units, and in this specific case, the unit seems really "plain enough": http://h10032.www1.hp.com/ctg/Manual/c01570902.pdf http://www.impactcomputers.com/463318-001.html http://www.thebestpartinc.com/463318-001.html What would I take more care about is the actual power rating on the single lines, over the years I have seen PSU's with every kind of "queer" combination of volts/amperes that although "summing up" to the "label" 300 W were (sometimes) very different on the single line/voltage. Of course if you "step up" and go for a 400 W unit the above potential problem should "vanish". As well (but again this is not the case -pardon me the pun - since it is a "micro-tower" unit) there may be some issues with actual length of cables. It seems to me (but *needs* to be double checked): http://www.ebay.ie/itm/Hewlett-packard-463318-001-Power-supply-300-Watts-/371156353028?pt=PCA_UPS&hash=item566aa48004 like the HP 463317-001/463318-001 (PFC/No PFC) is exactly the same as the HP 5188-2625, i.e. any among: LiteON PS-5301-08HADelta DPS-300ABBestec ATX0300D5WCHiPro HP-D3057F3Rwere "original OEM's" for it, but *any* no-name (and el-cheapo) unit should do nicely. jaclaz P.S.: As a side note, the way most brands/firms name their parts/spare parts deserve a special mention in the annals of stupidity .

The actual question is: Given that only one guy worked on this for the last few weeks, did they really *need* to choose the one retarded guy to work on it? jaclaz

RoHS (just for the record) is IMNSHO one among the stupidest standards EVER made: http://www.rohscompliancedefinition.com/ http://en.wikipedia.org/wiki/Restriction_of_Hazardous_Substances_Directive http://en.wikipedia.org/wiki/Restriction_of_Hazardous_Substances_Directive#Criticism Basically with the "noble" scope of freeing us from lead poisoning (something that may happen if you suck on a PCB 24/7 for several months/years) they managed (while reducing the amount of lead used in industry of a very negligible quantity, something like maybe 1.50% or 2.00%) to raise by 15 to 30 degrees the temperature of soldering alloys (which causes a number of serious issues, particularly shortening lifetime of electronic components, increase NOTICEABLY cases of cracking AND making repairs a little bit more difficult): http://en.wikipedia.org/wiki/Solder curiously, the military, the medical and the aerospace/data transmission industries are largely exempted, but the differences between RoHS 2.03 and 2.04 are seemingly two version that HP "invented", it is possible that the former is an old version, and the latter is "latest" 2011 version or that the former is the 2011 "current" version and the latter is one of the "amendments". These amendments, particularly, are interesting: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:32014L0013 http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:32014L0012 . As I see it, it is a very good thing that "important" things are made with reliable, proven to be working fine, materials, but I completely fail to understand why my laptop actually *needs* (by Law) to be made with less reliable (and actually more costly) materials. jaclaz

A typical issue with notebooks is the "blanking contact" in the external sound socket (the one you plug in external speakers or headsets). The socket is used normally much more than on desktops, and there is in it a small springy contact that is supposed, when the plug is in to disconnect the internal speakers. It is common that some dirt/oxidation prevents this to make contact when the plug is removed. So the advice is to first thing test with an external device (speakers/headset) and clean (with some contact cleaner) the socket. jaclaz

Yep, but do check also how the BIOS sees it. A BSY disk won't be detected at all. A LBA0 will be detected but with 0 size. jaclaz

Well, you can disable WFP. Or am I missing something? jaclaz

Nice , very, VERY nice Yep , I would have considered offensive to represent MS customers as sheep[*] and would have failed to have a gnome acting as shepherd. jaclaz [*] Though cannot really say if offensive for the customers or for the sheep.

I see . So one could setup Task Manager with the "right" columns added to show, then makes a series of screenshots (every 1 second or so) , OCR the screenshots , calculate the differences and graph them? Maybe using Nirsoft's Sysexp: http://www.nirsoft.net/utils/sysexp.html one could get rid of the screenshot capture and of the OCR parts . Rough example/random idea : @ECHO OFFSETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSIONSET /A Counter=0SET /A loops=60IF EXIST Data.csv DEL Data.csv:loopsysexp.exe /Title "Task Manager Windows" /class SysListView32 /Visible Yes /scomma "c:\temp\1.csv"SET /A Counter+=1FOR /F "tokens=1,9,10 delims=," %%A IN ('TYPE c:\temp\1.csv ^| FIND "lsass.exe"') DO (ECHO %%A, !time!, %%B, %%C>>Data.csvECHO %%A, !time!, Read bytes %%B, Write Bytes %%C)REM The following is just a poor man's WAIT, the 55 is to be changed to get as result a 1 second cycleREM which will depend on the actual PC and on the amount of commands in the loop and it won't be anywyayREM very accurateFOR /L %%B in (0,1,55) DO PING -n 1 127.0.1.1>nulIF %Counter% LEQ %loops% GOTO :loopjaclaz

This is classism, or oligarchy and not democracy. (you have it right, BTW ). http://www.msfn.org/board/topic/172856-guideway-to-disable-keylogger-well-im-not-sure/?p=1087279 jaclaz

Besides being a poor implementation it is also (mostly) a duplicated one. Since most of the running Windows Systems use a NTFS filesystem, there is already a (pretty much accurate ) indexing in the $MFT, something that most "smart" quick search tools make use of. jaclaz

That is the actual point to find out. For all we know, the "control panel" (software) may be showing a "proposed" setting which is in reality overridden (or whatever) by *something else*, possibly a lost/wrong EDID sent by the monitor (hardware) or from a wrong interpretation of the EDID data from the driver (software again) or from any of the automagical "side apps" that the Intel graphics "full install" provides (again software). Right now the only excluded thing is the VGA cable failing to "deliver" the EDID (hardware). The fact that it is recognized by the INTEL thingy as "W2043" but it is "generic Plug 'n Play" in Control Panel may mean *something*, but cannot really say *what*, just as a guess it is possible that the "normal" MS resolution setting is "fighting" against the Intel driver setting, and for *whatever* reasons sometimes one or the other "wins". Removing the device and letting the OS re-recognize it and uninstalling/re-installing/updating/downgrading the driver may work to *somehow* reset the situation, but it is just an attempt. When you reply to a post you have a set of icons at the top, the first one on the left that *seem* like representing a paper clip, but cannot really make out what the heck it should mean, will toggle between "plain" BBCODE and senseless "visual style" . jaclaz

To reinforce the idea, you could also go through this : http://www.msfn.org/board/topic/150215-dont-even-think-of-swapping-pcbs-on-720011/ which is also a sticky. The disk operates more or less like this: the disk microprocessor boots by reading the contents of a flash chip <-(imagine it as something like a BIOS) then executes some instructions in it then reads some data from the actual disk surface (stored in areas that are not normally accessible)UNLIKE normal BIOSes, the contents of the flash chip are partially CODE (the same for all chips with a same firmware) and partially "local" addressess/settings DATA that are specific to the disk that is "coupled" to the PCB. You CANNOT swap a PCB. You CAN however swap a PCB IF you "transplant" the "old" chip on the "new" PCB (AND if the "new" PCB is 100% compatible). This is something that needs a little bit more experience than the average DIY guy, but that is entirely doable with all in all cheap and readily available tools (magnifying lens, soldering iron (or better a resoldering station) some soldering paste, etc.) There are tools (that sell for several thousands US$ AND need some specific "advanced" training) that are able to: read the whatever is in the chip (both CODE and DATA)correct the whatever is in the chip (both CODE and DATA)load partially CODE or DATA (from the chip and from an external source)read the whatever is on the disk plattercorrect the whatever is on the disk platter Right now for all we know the issues you are having could be connected to one or more than one among: corrupted data in the chip "code" part corrupted data in the chip "data" part corrupted data on the disk failure of the disk head(s) failure of the disk self-positioning head arm failure of *any* component on the PCBto which you add that we don't really know for sure IF your cable/adapter (or the settings you are using or even the connection you made) are "good" and working. So, your next step would be to get another (working) 7200.11 and test if your procedure work for accessing it (and if it doesn't change the adapter/procedure) Given that you succeed (i.e. that your tools and procedure are correct) you have a PCB that doesn't respond. The next step would be to get yourself a compatible set of tools (and if you have no experience with this learn to solder/desolder tiny surface mounted components - as said doable but not easy-peasy) and transplant the chip from the "old" PCB to the new one. In, say, the 75% of cases where you will manage to make the transplant without frying the chip, you will have access to the PCB terminal, then, you will have NO IDEA (just like we have none ) of the following steps (commands to issue, etc.) which, even if known, may work in say 25% of the cases, in another 25% you will need to use a loader because the contents of the chip are corrupted, in another 25% of the cases you will need to replace a head assembly (which is NOT a DIY job unless you spend a few thousands dollars in tools, training, etc.) and in the remaining 25% the actual disk is really "gone for ever" and no data can be retrieved from it anyway. To sum up (given that it is a generic, undiagnosed "click of death" and NOT a BSY and NOT a LBA0), if you do a PCB swap: in 25% of cases you will fry the chip in the transplant in 75%*25% of cases=18.75% you did i right but DO NOT know what to do next in 2*75%*25% of cases=37.50% you did i right but have NO WAY to perform next step in 75%*25% of cases=18.75% you did i right but THERE IS NOTHING to be done Since 25%+18.75%+37.50%+18.75% sum up to a neat 100%, you have NO chance in practice to revive that disk AND you have big chances to accidentally make things so worse that even a professional service that has *some* chance to get the data now from the disk "as is" will have no chances left after. Of course the above calculations are totally faked, and it is entirely possible that if any of the percentages adopted are wrong you have some teeny-tiny possibilities, but I wouldn't count on them. I understand how sad it is , but you have to evaluate attentively the above before deciding for: suicide ask for a professional service repairgive up and call it a daysomething else jaclaz

A (late ) update. The Novena has made it on crowdsupply : https://www.crowdsupply.com/kosagi/novena-open-laptop jaclaz

For NO apparent reason : jaclaz

Well, before killing yourself, you might want to take a nice walk outside, maybe you change your mind about this. In any case, often (but not always) a professional may be able to recover the data (with a cost that can be *anything* between €250 and € 1,000, not exactly "cheap", but still IMHO more affordable than suicide ). jaclaz