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

By convention, sentences with a little hook sign "?" appended are meant as "questions". It would be nice to have "answers" to them. Examples of issues connected with wrong .inf or EDID: http://superuser.com/questions/713487/getting-proper-resolution-with-windows-7-and-older-monitor https://www.omnivex.com/support/kb/204 http://www.intel.com/support/graphics/sb/cs-030332.htm You could try updating (or downgrading) your video card drivers (or maybe even uninstalling and re-installing them might do) Try checking the monitor with: http://www.entechtaiwan.com/util/moninfo.shtm and try making an EDID override .inf jaclaz

Unfortunately no. If you are having a "click of death", the CAUSE is very different (and unfortunately there are NO known AFAIK DYI way outs for it). In the case of the LBA0 or BSY the issue is that the firmware on the disk enters a "loop" of some sort. Imagine (in pseudo code, batch in this example) that it is executing a program like: @ECHO OFFSETLOCAL ENABLEEXTENSIONSSET Counter=0:repeatSET /A counter+=1SET /A Issue=%RANDOM%/512:loopECHO %Counter% %Issue%IF %counter% GTR %issue% GOTO :loopIF %counter% LEQ 9 GOTO :repeatIf you run this program a few times, you will soon enter a loop from which you can only exit by pressing Ctrl+C. The "click of death" is instead seemingly like the program file would be missing altogether. The Ctrl+C is a sort of "reset" similar to the procedure for BSY or LBA0, there are no solutions (short of re-writing the batch) for the missing file. You are very welcome , though I am afraid we won't solve the problem. jaclaz

Well, if you had read it, you wouldn't be asking questions about TTL levels/adapter cables (that have been detailed in it). As well, if you do not report that you tried swapping Tx and Rx, since my crystal ball is (again ) in the shop for maintenance, I have no way to know that. The point of note here is that you are seemingly NOT in a LBA0 or BSY case, but even for them the "original" way to access the terminal was to completely separate the PCB from the disk, procedure that was later replaced by insulation the motor or head contacts. As a matter of fact the "intermittent" nature of your issue could actually be connected to bad contacts, so removing the PCB and thoroughly cleaning contacts wouldn't be a bad idea anyway. The "3.86 Gb size" is usually connected to yet another issue, however, and - usually - with a number of "clicks" when spinning up, called in jargon "click of death", see: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=862696 http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=1086659 jaclaz

Why not using Task Manager (adding the relevant columns to the display)? http://www.bleepingcomputer.com/tutorials/how-to-use-the-windows-task-manager/ http://www.online-tech-tips.com/windows-xp/an-introduction-to-the-windows-xp-task-manager-processes-programs-and-performance-part-2/ jaclaz

READ the read-me-first: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ it will answer most of your questions. Try with the PCB completely detached from the disk. Try inverting Tx and Rx. jaclaz

Before I forget , in order to keep things as together as possible , here is another example of when a "peculiar" setting/edit is needed: http://www.msfn.org/board/topic/149758-win7pe-se/page-6#entry1067197 Basically, if a "dual boot" BIOS/UEFI CD/DVD is made with OSCIMG using grldr (but I believe *any* non-2048 or non 4096 bytes loader are likely to behave the same ), on some older BIOSes the thingy won' t boot and there is the need to edit the "Size to be initially loaded" to 2048 bytes. jaclaz

Just in case: http://www.msfn.org/board/topic/83347-vxd-files-structure-and-disassembly/ http://www.msfn.org/board/topic/135527-vxds-and-related-stuff-help/ And of course: http://jls.chez.com/vxdasm.html Maybe some of our good 95/98 aficionados members may try to contact the Author of the tool above and/or the guys here: http://www.techsoftpl.com/vxd/index.php who seemingly provided at the time useful tools (Commercial) to see if - given that expecting nowadays any income from the sale of these tools is futile - they would be so kind as to release a public, free, version. jaclaz

Ah well, if they asked for it, then that's fine. , after all the good google guys' motto is "Don't be Evil": http://en.wikipedia.org/wiki/Don't_be_evil jaclaz

I wouldn't be so sure/I don't know. The point is that the TTL level in the given link is given as 5V TTL (seemingly the "wrong" one or TTL/CMOS), you possibly missed the READ-ME-FIRST: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ particularly point 6 and the visual representation (original page is down now, but till viewable through Wayback Machine): https://web.archive.org/web/20140829053839/http://www.interfacebus.com/voltage_threshold.html AND point 10. This might also possibly clear the matter: http://www.msfn.org/board/topic/152653-bsy-bug-for-seagate-momentus-72004/?p=972251 the difference between SHOUTED ENGLISH and whispered English easier to grasp . So, while it is well possible that the Author of the "hacking adapter" is "wrong" (and the actual TTL level between the Prolific chip and the Max213 is the "right" one at 3.3V) I would need some definite report of this hack (or of a similar one) working with one of these stupid 7200.11's before being convinced that it could represent a viable solution. jaclaz

Sure the HAL is "involved in it", but I believe that it is only one of the variables in the equation. jaclaz

To be fair, once upon a time in a far away galaxy, in order to be able to drop support you needed to provide it until the change. Otherwise people won't notice it. Claiming that you supported it and that you will stop doing that on a given date (and bragging a lot about it and how dangerous it will be if you don't switch to the new supported OS before that) is not exactly the same. jaclaz

Well, of course it's up to him , but it is not particularly difficult/complex, anyone with a minimum of patience/attention can do it, see this as an example: http://www.msfn.org/board/topic/139328-disc-drive-unable-to-eject/ jaclaz

IRQ issues are very tough to pinpoint and troubleshoot, there are so many variables in the *whatever* that causes their assignments that it is often impossible to solve them, especially on a laptop as usually these have a somehow "reduced/locked" BIOS and of course you can not make experiments disconnecting/recoonecting cards/devices. Usually (but not always) the "internal" PS/2 pointing device is "connected" with the keyboard (and that would be IRQ1 http://www.sebsworld.net/information/?page=IRQ this would explain why the PS/2 internal device "locks" *somehow* the keyboard. jaclaz

And are all these dramatic changes relevant enough to justify the quantum leap of naming the thingy Windows 10 (as opposed to Windows 8.2, which is what the thingy actually is - though possibly Windows 8.1.1.1 would have been even more suited) ? jaclaz

No. Fully half the people in the world may be ignorant, in the sense of not knowing or not knowing enough about something (ignorance has nothing to do with intelligence or lack of it, and can usually be cured ). Please take note how "serious lawsuit" could be considered an oximoron , and you need a special license to post one of those on MSFN Seriously, the point is IMHO not much about the actual data (if any), but about the concept, you are asked to authorize the collection of *any* data in an unspecified amount, with unspecified means, and without any control on which data is collected and transmitted. I personally find this a "serious" issue. jaclaz .

You paid for regular (current version and it's updates) activation keys, not for the Beta Program. Usually a list of current users is made, an then from it a certain number of Beta Testers are chosen according to any among these: people that substantially contributed in early (or however previous) developmentpeople that the developer simply likes to includepeople that are drawn at random from the listPoor little thing, you were not chosen among the elected ones and you weren't lucky enough to have a winning ticket of the lottery , I feel for your pain, it is ... , it is .... unfair . jaclaz