jaclaz

Good , what was the IT that worked? (just to make your report useful to other people with the same issue) jaclaz

Well, I thought more along the "philosophical" or "historical" side of it, as in "history repeats itself": http://en.wikipedia.org/wiki/Historic_recurrence This document has always been for me a very interesting reading : http://en.wikipedia.org/wiki/United_States_Declaration_of_Independence jaclaz

http://thesaurus.com/browse/no+guts jaclaz

Another proof (if needed) of how the Pareto principle is loosely mixed with arrogance and misundertood "popularity" in the good MS guys' (perverted) minds. A blast from the past : http://www.crn.com/news/security/18821726/microsofts-ceo-80-20-rule-applies-to-bugs-not-just-features.htm jaclaz

Hmmm. Something you can try (NOT on your production system!) could be that of removing SYSTEM write access to that bag, (and/or monitor that particular folder bag with procmon/regmon and find out what service accesses and writes to it changing the value, and in which occasions this happens). jaclaz

Yes and no. The "original" guide is about having the PCB completely detached from the hard disk. Then there are people that had success with a slip of paper under the head contacts and some that had success with it under the motor contacts. Try with the PCB completely detached first (only to see if you can get to the F3> prompt this way). Can you confirm that it is a 7200.11 (AND NOT an ES2 drive)? http://www.msfn.org/board/topic/129551-unlocking-terminal-of-seagate-es2-in-bsyled000000cc-state/ jaclaz

Have you ever seen a 1776 "continental" coin? or a "Fugio" cent? http://en.wikipedia.org/wiki/Fugio_Cent Wouldn't there be a reason if Benjamin Franklin designed it with the words "Mind you business" on it? Coins or more generally money were the only "mass media" available at the time, that was essentially the first "large audience" message given by the Founding Fathers to their people, it must have had some meaning. jaclaz

My bad, wrong post ProcessHacker is a very good tool, at least on XP. jaclaz

Good , which one, specifically? I mean, what did you actually do that solved the issue? jaclaz

Rest assured, Ponch and me are not at all "fighting". BUT you seem like not having fully grasped the "general concept" of drive lettering under a Windows NT system. The matter is a bit complex, but basically the Active partition on first disk will get drive letter C: during a new install (unless some "special" measures are taken). This means that any other volume will get a non-C: drive letter. This is not an issue, as said multiple boot systems are in use commonly since NT 3.51 times: http://www.msfn.org/board/topic/169320-dual-booting-dos-and-win7/?p=1058478 deciding if you want this second install have a C: or a non-C: drive letter is just a matter of personal preferences, but you have to know what will happen beforehand. It is quite simple to fix/repair a BOOT.INI file, no problems there. See: http://www.msfn.org/board/topic/25365-bootini-and-different-hard-drive/ jaclaz

Yep , but semantics (or even reading a bit on them) may tell you that svchost.exe is actually a service host : http://en.wikipedia.org/wiki/Svchost i.e. a number of different processes can appear under the "generic" svchost.exe name, and - if I were you - I wouldn't disable lsass.exe : http://en.wikipedia.org/wiki/Local_Security_Authority_Subsystem_Service jaclaz

But that is the list of files (and not that of the processes that write to them). I mean, several tens (or hundreds) of processes will write to the Registry, like C:\WINDOWS\system32\config\software and consequently C:\WINDOWS\system32\config\software.LOG, the point here is whether those processes are actually NEEDed and if they actually NEED to write to that specific file (rest assured that SOME processes DO NEED to write to the Registry), on the other hand only the WIA service will write on wiadebug.log and wiaservc.log : http://www.hsc.fr/ressources/articles/win_log_files/index.html.en#stisvc so you can probably set it to not write debug info : http://support.microsoft.com/kb/307001/en-us As well you can also disable/remove WMI/WBEM subsytem, but a large numbers of tools won't work anymore . You should use the BlackViper lists as a base to see which services can (or may) be disabled and/or which effects you will have: http://www.blackviper.com/ jaclaz

Strangely enough the reference is in the tool's "Step_By_Step" guide: http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step Hidden in a part titled "Selection_of_files_to_recover": http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step#Selection_of_files_to_recover Such Options for Files are in the tool under a menu curiously called "[File Opt]" As in: http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step#Source_partition_selection jaclaz

Sure, there WAS A reason AT THE TIME you created the first file, ANOTHER reason AT THE TIME you created the second file (several months later) and NOW (some more months later) you have forgotten BOTH and you just deleted the "wrong" file (just saying ), that's more or less the essence of Murphy's Law. Seriously, it is just a matter of personal "tastes" and "habits", everyone should be free to choose the setup he/she finds "better" . jaclaz

Well, how big are the actual .pst files on the filesystem? AFAIK, the difference between the "normal" format and the "unicode" one is in the addresses, that are 64 bit instead of 32 ("ealrier" vs. 2003/2007): http://en.wikipedia.org/wiki/Personal_Storage_Table#Formats_and_size I don't think that there are much differences between 2003/2007 and 2010 jaclaz

BTW, you cannot link to (say): http://enenews.com/harvard-website-media-blindly-reports-tepcos-false-radiation-levels-says-****ushima-official-press-wont-report-truth-its-still-scary-in-tokyo-people-move-away-due-to-hotspots-e as even if you spell that name correctly, (without the c between the u and the k) the communist censorship word filter of the board intervenes to change: F u k u s h i m a to ****ushima in the link, even in code-box: http://enenews.com/harvard-website-media-blindly-reports-tepcos-false-radiation-levels-says-****ushima-official-press-wont-report-truth-its-still-scary-in-tokyo-people-move-away-due-to-hotspots-eBUT shortening the URL works: http://enenews.com/harvard-website-media-blindly-reports-tepcos-false-radiation-levels-says- Oops , let me rephrase : jaclaz

Maybe a dosimeter would be more handy than a Geiger counter. Personal electronic ones should be available for around 500 bucks. jaclaz

Sure , but his streaming HD/1080p p0rn may stutter a bit . jaclaz

Ponch, how exactly did you "move" those e-mails? jaclaz

Ponch, there must be a misunderstanding (or you are making the wrong examples)? With "my" approach, as an example in a dual boot with two active partitions, first partition is always C: and second partition is always D:. if you boot in "first" OS and delete (say) the file C:\myfile.txt, you are deleting the file myfile.txt on the first partition. if you boot in "second" OS and delete (say) the file C:\myfile.txt, you are STILL deleting the file myfile.txt on the first partition.When you use "C: as system drive", if you boot in "first" OS and delete (say) the file C:\myfile.txt, you are deleting the file myfile.txt on the first partition. if you boot in "second" OS and delete (say) the file C:\myfile.txt, you are INSTEAD deleting the file myfile.txt on the SECOND partition.jaclaz

Well, that is a pretty much strong statement. Really? I presume that also commercially available cables exceeding specified standards are a no-no. I will then venture to say that if it works, it works, if it doesn't, it does not. Come on ... @AmazingGecko Generally speaking the good thing about standards are that there are so many of them.... A CAT5 cable (the RJ45 you mentioned) can be as long as 100 mt: http://en.wikipedia.org/wiki/Category_5_cable for 100 Mb connections. For Gb connections you'd better go for a CAT6 cable (still RJ45 connector) that can go as well up to 100 m (and you can have as well some 37 m if using it on a 10 Gb connection). A RJ11 cable can be with 2, 4 or even 6 wires. http://en.wikipedia.org/wiki/Telephone_plug http://en.wikipedia.org/wiki/RJ11#RJ11 The most common is using normally a 6P4C RJ14 connector, i.e. it is 4 wires, of which two are unused, the additional unused wires may provide a primitive form of shielding, while a 2 wires connection is better avoided if not for very short extensions, a 4 wires one may do. There is no actual standard about length of a phone line extension, BUT you have to be aware that whenever signals are transmitted "solid copper" has dramatically better performance than "stranded" wire AND signal transmission MUST be carried over twisted pair cable to limit "cross-talking" and interferences with other cables and/or radio signals, so, if you are planning to use some "solid copper" twisted pair cable it may do, simply forget about stranded cable or non-twisted pair ones(as many commercially available extension cords use). BUT, follow me please, if you have the router close to the telephone socket and a CAT5 or CAT6 extension cable to your PC (or hub or intralan router), you have at both ends of the cable an "active" device under your control (i.e. something that you can use to troubleshoot an issue - if any), whilst if you put an extension telephone cable between router and phone socket, that length of cable will be nothing but an extension of the telephone line, on one end you will have the router (under your control) on the other end there will be the ISP device(s), in case of troubles the ISP won't be able to detect if there is a problem on "their" line (up to the wall socket) or after it. Typically they will ask you how far is the router from the socket and ask you to put it as near to it as possible (i.e. with an as short as possible extension cable), and IF a technician is sent to solve the problem AND the cause of the issue is attributed (and you have no way on earth to be sure that it is the actual case) to "your" extension cable, they may even bill you for the intervention. On the other hand, the ADSL/DSL technology is designed to cover with "good" bandwidth approximately 2 km distances over copper wire: http://en.wikipedia.org/wiki/Digital_subscriber_line typically having a degrading of bandwidth, with behaviour like the following: 24 Mbit/s -> 1 km 20 Mbit/s -> 1.6 km 12 Mbit/s -> 2.5 km 8 Mbit/s -> 3.0 km 4 Mbit/s -> 3.9 km Even if the 5/10/15 meters of the telephone line extension you may need are very little when compared to the amount of cable needed to have an attenuation of the signal, they may contribute to it, and surely - depending on the quality of the cable used and if it goes near other cables - they are an "entrance point" for interferences. So BOTH "common sense" and technical reasons suggest (if possible) to put the router near the telco/ISP wall socket and to use CAT5 or CAT6 cable connected to the router to connect to devices in other rooms. Mind you the above does not mean that extending the telephone line won't work, only that by doing that you are introducing a possible cause of issue (and we have anyway Murphy's Law waiting to prove itself right once again ) In the same spirit of the previous replies, do the right thing: http://www.imdb.com/title/tt0097216/quotes?item=qt0362962 jaclaz

The idea of "example" is - strangely enough - that of it being an "example". BTW it seems like that thing is Cardbus (not PCMCIA), see: http://www.msfn.org/board/topic/141776-modifying-a-really-old-dell-laptop/ though cannot say if it can be connected to the issue. Those IRQ/Resource conflicts are usually a nightmare , and on a laptop there are very little changes you can make, but since the thingy works in XP, it should mean that *somehow* it can be solved through software only (either "better" drivers or different resource allocation). You can *try* listing ALL the IRQ/resource settings in XP and see if you can manually replicate them under Win98, possiby disabling/removing some other devices, but it is hard to say if you may succeed . jaclaz

@Moodie1 Don't worry , if you install this new instance on the "second" volume/partition, you will be making simply a "dual boot" system. The only "issue" you may have is/will be drive lettering and the two installs will "share" a common NTLDR+NTDETECT.COM+BOOT.INI on your first volume, which is and will remain the "active" partition. In your current status you have the current XP install on the first volume, which by default has got the drive letter C:, the second install will get - still by default - the drive letter D: (or a higher letter, it depends on the devices connected to the PC at install time). There are two common "theories of operation", one (wrong BTW ) adopted by most people that want their operating system to reside on "C:" (to be more "standard") and one (right ) that makes setup so that no matter which OS is booted the same volume gets the same drive letter (which limits the risk of modifying the "wrong" volume). So, you will need to make a choice, if you are OK with the second install having a non-C: drive letter you can go on, if you on the other hand need/want to have this second install be residing on a volume with drive letter C: you need further instructions. jaclaz

Check the Octopus Read starting from here: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-153#entry968299 a few posts (the above link has just been re-posted in order to help Casalla1 ) up to here: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=968346 jaclaz

Most probably the $MFT was "small enough" and has been completely overwritten Yep, that is the issue with "pure file based" recovery, but I guess that is better to have files (eiher mixed or without original names) than having no files at all . Remember that there are no real "assurance" that a recovered file is valid (contiguous files will be, non-contiguous most probably not) so you will need anyway open/check them one by one. jaclaz