jaclaz

When you have BOTH networks connected, can you run an IPCONFIG /ALL>C:\mynicconfig.txt and post the result? (edit/redact sensible data, obviously) jaclaz

Besides what you expect people to actually want , it would not be possible most likely (and besides the issues with UEFI) because of the lack of drivers compatible with 2K or XP. jaclaz

Let's make a simpler example. Let's say that you have a directory C:\tests and in this directory you have a text file c:\tests\mytest.txt with these contents (copy and paste in a new notepad window and save as c:\tests\test.txt: Line #1: This is first line Line #2: this is second line Line #3: this is third line And let's say that you want to remove the second line, i.e. your expected result is: Line #1: This is first line Line #3: this is third line There is NO command built in in the batch language NOR any tool shipped with any DOS/Windows release capable of removing a line from a text file. Is this clear enough till now? There is a workaround that is to read the WHOLE contents of the file and re-writing a new file filtering out the unwanted line. Open a command prompt window and in it type )or copy/paste): TYPE C:\tests\mytest.txt [ENTER] You will see the three lines. now try: TYPE C:\tests\mytest.txt|FIND /V "#2" [ENTER] You will see your desired result, the line #2 is filtered out by the FIND /V command. now try: TYPE C:\tests\mytest.txt|FIND /V "#2">C:\tests\mynewtest.txt [ENTER] Open in Explorer the folder C:\tests\ and you will find in it a file named mynewtest.txt with the same output you before saw in the command window (i.e. the desired result). What you have done was to "pipe" (or redirect) the output of the command TYPE to the input of FIND command and later redirected this latter's standard output to a file. Is this clear enough? Besides your "dyslexia along with ADHD" troubles, you need ANYWAY to read and study the batch commands syntax and understand it if you want to write a batch file. The given site: http://www.robvanderwoude.com/ http://www.robvanderwoude.com/batchfiles.php contains both "basic" syntax and "advanced" one explanations, examples and what not. Start reading, at the light of this post, these: http://www.robvanderwoude.com/type.php http://www.robvanderwoude.com/find.php http://www.robvanderwoude.com/redirection.php jaclaz

Yep, though the general rule is to never trust an hard disk (NEVER), and never, ever consider SMART data to be reliable in a positive way (i.e. a disk sporting "perfect" SMART data may fail in any instant, no matter what the SMART says) a negative SMART setting may be an alarm signal, that in this case seems like being confirmed by the manufacturer tool . You can still keep using that hard disk, but only if you have a working/checked backup strategy (at least TWO copies of the data on different media) and a sound/tested "recovery from bare metal" method/strategy. It is well possible that the drive will whirl away happily for another few years before actually failing, though. jaclaz

http://www.benchmarkhq.ru/english.html?/be_hdd2.html jaclaz

You will need to find a special carpenter that has "that special size drill bit." . Or you might get away with adhesive stand-offs or with PCB feets (examples): http://www.avtic.com/pcb_accessories/plastic_pcb_spacers/adhesive_pcb_spacers http://www.mikesarcade.com/cgi-bin/store.pl?sku=PCBFEET jaclaz

Yeah , like you need to be a member of the club and learn the secret hand-shake to be able to simply google for it and get this public document : http://www.t13.org/documents/UploadedDocuments/docs2005/e05148r0-ACS-SMARTAttributesAnnex.pdf How EXACTLY have you checked that the drive "however works just fine except for that error, no surface problems or anything" ? Check it with it's manufacturer test tool. If it passes it, it is OK, if it doesn't it is NOT (which does not mean that it will fail tomorrow or the day after, only that it does not meet the requirements it's original manufacturer has set, and I personally believe that the hard disk manufacturer knows more about it's products than anyone else). Since it is a laptop it is more common that "episodes" (falls/hits/whatever) may have triggered an error. jaclaz

Phaenius, if you have a computer with a case fan or a PSU with a 120 mm fan, observe it accurately (with a torch since not only the PC is off but - for safety reasons - you have cut out electricity in your neighbourhood ). That fan is mounted to EXTRACT air from the case. The hypothetically finger cutting blades are on the INNER side. A typical fan (like the one we were talking about) will have 7 (seven) blades. Roughly 2/3 of the circular corona between the central motor and the outer of the fan is "blades" and 1/3 is "air". At the very outer part of the fan, let's assume 110 mm you have a circumference of 110*Pi. Your "target" when you will attempt to insert a finger in it is at the most 1/7*1/3*110*Pi=~16.45 mm wide. The thickness of the fan is 38 mm (i.e. the actual hypothetically cutting edges of the blades are some 35 mm from the exterior). But the blade is rotating by definition at 3.000 RPM, this means that it's speed at 110 mm outer diameter is 110*3000/60=5,500 mm/s Your target is "covered" in 16.45/5,500=~0,00299 seconds, let's say 3/1000 of a second. You finger has to travel linearly "inside" the target for 35 mm in 3/1000 of a second to reach the cutting edge of the blade, i.e. it has to travel at around 11,706 mm/s i.e. 11.7 m/s, i.e. roughly 42 km/h. Presuming that your hand starts from still with the point of your finger at 10 cm from the fan, the tip of your finger will need to accelerate from 0 to 42 km/h in 10 cm. Assuming that acceleration is linear, the 10 cm will be covered at an average speed of 5.85 m/s (or 21 km/h) and will thus take .10/5.85=0,017094 seconds, i.e. roughly 2/100. So we have 11.7/0.02=585 m/s2 or 59.65 G. I guess that if your finger (and hand and arm) can stand that kind of acceleration, it will survive the fan-through experience alright jaclaz

Hmmm. http://www.mrexcel.com/forum/general-excel-discussion-other-questions/654094-windows-automatic-updates-creating-havoc.html I guess SP3 is not considered an "update": http://tech.slashdot.org/story/08/05/09/1258229/windows-xp-sp3-creating-havoc jaclaz

Add "less than 9 Watt" to the search keywords to limit the awful number of verified accidents that you will find with your keywords . Also add right before your addition (that would become 1.b ): 1.a SECURE the fan with at least four bolts to the case and fix the case to the bench using straps, vises or similar before connecting, make sure that the bench is bolted securely to the floor AND to a wall, there are cases of small fans that took off taking the case and the bench with them. jaclaz

Sure . Lots of people from South Korea also fear those http://en.wikipedia.org/wiki/Fan_death http://konglishadventures.wordpress.com/2010/06/13/the-rumored-fan-death/ jaclaz

No, that's by design and for your own good. Next release of the OS you will only be able to access MS news. jaclaz

See: http://en.wikipedia.org/wiki/Live_CD of course a LiveCd does not really *need* to be Linux based, as an exampe there are several PE 1.x, 2.x or 3.x derived from either XP/2003, Vista / 2008, 7/2008 R2 with added features including sound support, but they need to be "built" from your source and this procedure is not as easy as getting a pre-built Linux based Live CD. jaclaz

Also handy: jaclaz

Sure , low power computer case fans are known as the third main responsible of accidents on the job and sixth at home accordingly to a recent survey. http://www.overclockers.com/forums/showthread.php?t=484942 When testing these: the standard advice is to get to Antarctica (and have a looong range remote to switch it on) jaclaz

Choose here: http://software.opensuse.org/122/en between LIVE KDE or LIVE GNOME Or use a USB stick: http://en.opensuse.org/SDB:Live_USB_stick jaclaz

It seems to me like the result of the usual "infinite monkeys approach" that most people new to scripting tend to use initially . http://en.wikipedia.org/wiki/Infinite_monkey_theorem obviously the probabilities to get a correct command line are much higher than re-writing all of Shakespeare's plays , but still they are infinitely low . jaclaz

Maybe you are focusing to the specifics and not to the generic. What you want to do, which is "How do I remove lines from a HOST file?" is a sub-set of the generic "How do I remove lines from a plain text file?". The latter has TWO different answers: there is NO provision without using third party tools to delete lines from a plain text file what you can do instead is to re-write the text file omitting the lines that you do not want Typically this can be done using a FOR loop and either the FIND or FINDSTR commands. FOR /F "tokens=* delims=" %%A IN ('type "%WinDir%\system32\drivers\etc\hosts"') DO ECHO %%A FOR /F "tokens=* delims=" %%A IN ('type "%WinDir%\system32\drivers\etc\hosts"^|FIND /V "www.etcetc.org"') DO ECHO %%A>>"%WinDir%\system32\drivers\etc\hosts1" FOR /F "tokens=* delims=" %%A IN ('type "%WinDir%\system32\drivers\etc\hosts1"^|FIND /V "etc etc.org"') DO ECHO %%A>>"%WinDir%\system32\drivers\etc\hosts2" FOR /F "tokens=* delims=" %%A IN ('type "%WinDir%\system32\drivers\etc\hosts2"^|FIND /V "update.etcetc.org"') DO ECHO %%A>>"%WinDir%\system32\drivers\etc\hosts3" NOTEPAD "%WinDir%\system32\drivers\etc\hosts3" Within limits, you can use more FIND /V on the same command in the FOR loop, if all you have to do is to remove three lines, you can do it in one command. then, once you are satisfied with the result, you delete the original file and rename the temp file, like: del "%WinDir%\system32\drivers\etc\hosts" ren "%WinDir%\system32\drivers\etc\hosts3" hosts Take some time on: http://www.robvanderwoude.com/ntfor.php http://www.robvanderwoude.com/ntfortokens.php http://www.robvanderwoude.com/find.php http://www.robvanderwoude.com/findstr.php What I don't understand is if these lines (site addresses) are always three, are always the same three, etc. etc. or if you need to call the command with a parameter (the line/site address to be deleted). jaclaz

We are getting at every post nearer to : http://www.imdb.com/title/tt0074860/quotes?qt=qt0247572 What one normally do would be: connect the fan to a 12V DC power source (directly coming from the PSU observe if it starts spinning if NO goto 10 if Yes goto 5 let the motor warm a little, let's say by having it spin 15 minutes connect it through a multimeter to the same power source measure the amount of current it absorbs at start and when fully spinning if current is within specs, goto END and mount it to the case if current is above specs goto 10 remove (carefully) the label of the fan remove the little retaining washer underneath disassemble the fan from the motor clean whatever residual of oil/grease is there spray the bearing with some WD40 or similar apply a tiny quantity of Superlube grease or similar re-assemble the fan goto 1 jaclaz

My bad , I didn't scroll on the senslessly whitish/low information density/designed by a pre-school kid page . Now that I read the "right" data you were referring to, yes, they make no sense. My average NT 4.0 BSOD's (number of BSOD/months) are (for a few machines I have total and "logged" control): 0/142=0 (data since April 2001 running 24/7) My average Windows 2000 BSOD's: 0/119=0 (data since March 2003 running 24/7) 0/87=0 (data since August 2003 NOT running 24/7) My average Windows XP BSOD's: 2/52=0,0385 (data since September 2008 NOT running 24/7) As a matter of fact this should be halved, since one of the two BSOD's was due to hardware fault jaclaz

That is not about BSOD's (which could be an actual measure of the stability of the OS) they are about application crashes that are very likely to be associated to the actual application (and NOT to the OS in which they run). Check the home page of this wonderful "it's like magic" app: https://www.soluto.com/ and guess WHO exactly could be the users base. JFYI: http://blog.soluto.com/ And - for no apparent reason - a link to the personal blog of the Chief product officer at Soluto: http://roee.co/2012/03/06/what-i-wouldnt-do-to-welcome-windows-8-into-the-world-hello-metro/ I have a completely different idea of "casual sampling" and "independent survey". jaclaz

But you failed to post these data. No, what you are basically missing, and I am trying - at this point desperately - to try telling you is that if you connect a (say) 24 V device (or a 36 V or a 48 V or a 5 V or *whatever* voltage) to a 12 V outlet, the max voltage present at the outlet will remain 12 V, it is what "comes out" of the outlet and not the specs of the device attached to it. The specific device (fan) can run continuously at 12.8 V but it is designed to be powered at 12V (i.e. it has a target of being operated at 12 V though it can accept as low as 6V and as much as 12.8V). Power absorption is another matter, if you attach a device rated for a higher power absorption (but within the right Voltage specs) to a power outlet, the device will attempt to get more power (up to it's own specifications). As a matter of fact when you connect a load to a voltage output, the voltage level might drop a little, but NEVER increase, if your motherboard ouputs 12V (as a matter of fact, if you had a mutimeter, you would measure on it - as said - most probably 12.2 or 12.3 V with no load connected to it and exactly 12 V or more likely 11.9 V with a "heavy" load connected) you will NEVER be able to get 12.8V from it. Examples (simplified, and in order to let you understand) in case of BOTH an unprotected/unlimited power supply and of an unprotected/unlimited device: Power supply specs: 12V 1A hence 12W If you attach to it a device rated 6V 1A (6W) continuous, the device will burn in no time (because the voltage operating range of the device is greatly exceeded) . If you attach to it a device rated 12V 1A (12W) continuous, both the device and power supply will work for years without issues (this device may well have peaks or "MAX" of up to 40% more than standard absorption - or even higher "transient" current spikes without any consequences to the device or to the power supply) If you attach to it a device rated 6V 2A (12W) continuous the power supply OR the device will burn in no time.(because the voltage operating range of the device is greatly exceeded OR the current capabilities of the power supply are greatly exceeded) If you attach to it a device rated 24V 1A (24W) continuous the power supply is very likely to burn (because the device will attempt to draw more current to compensate for the lower voltage) Additionally voltage and current are linked together by Ohm's Law: http://en.wikipedia.org/wiki/Ohm's_law that is the same, written differently, that gives you V x A = W (when talking of DC, NOT AC) http://www.csgnetwork.com/ohmslaw2.html the MAX current that device will draw is 0.70A at 12V, if you supply it with a higher voltage, let's say 12.8V it will draw LESS current, i.e. 12 x 0.70 = 12.8 x X -> X=~0.66 A If you attach to an outlet (BTW surely protected from overcurrents) rated for 12 V 0.74A that particular fan, it will run normally at 12V (and NOT at any higher voltage) absorbing normally 0.51A with the possibility of peaks up to 0.70A. The outlet can provide UP TO 0.74A at 12V (8.88W), the device will nornally use 0.51A at 12V (6.12W) with peaks up to 0.70A at 12V (8.40W). You are well within the specs. jaclaz

Also, generically speaking, do not forget the power of collective knowledge (and experience) : jaclaz

As a matter of fact that seems a lot a (BTW an IMHO badly designed) GFXboot image from a GRUB or grub4dos and has nothing actually to do with XP or any other MS Operating System. Specifically the use of a bootmanager such as GRUB or grub4dos (or Syslinux/Isolinux/memdisk) is logically contrasting with the idea of "unattended". These programs give you boot choices, and there must be someone "attending" the boot process in order to take these choices. Of course you can add a "fully unattended" XP setup to a multiboot device, but his is not in any way different from making the multiboot device and adding to it a "plain", "normal", "attended" XP setup. jaclaz

From the linked to: http://blogs.law.harvard.edu/philg/2012/12/05/christmas-gift-for-someone-you-hate-windows-8/ I find this a good one: jaclaz