jaclaz

Yes , being satisfied of what you have. You have a running Windows 7, actually running good enough for your scopes . (for other scopes it may be different and you will find a big number of peeps telling you that with that configuration it would be "slow as molasses") WHAT is the problem? The good MS guys, for once in their life asking for beefier hardware than the real bare minimum? It has been proven how in the past the "hardware requirements" MS set up front were sometimes excessively minimal or anyway not corrresponding to "real life usage", anyone running XP (32 bit) on a Pentium 233-megahertz with 64 Mb RAM )or even on a 300 Mhz with 128 won't ever call it "snappy" http://support.microsoft.com/kb/314865/en-us BUT that is not the actual Minimum requirement: http://winhistory.de/more/386/xpmini.htm.en jaclaz

Broken google/MSFN Search? jaclaz

3rd (third) sticky here: http://www.msfn.org/board/forum/157-install-windows-from-usb/ i.e. here: jaclaz

Good , I am removing BOTH 001 AND 002 , please meet 003 . (I forgot "Current_head" field in previous ones, and have now added a clearer - hopefully - view) jaclaz P.S. File updated, small typo, I had "lost" a "%" in the %Volume_Label% of first view. view_bs_003.zip

Really? , right on this same page : Anyway, happy you made it . jaclaz

Anything ES2 is NOT on the present thread, but here: jaclaz

JFYI : http://reboot.pro/2362/page__st__31 jaclaz

Ow, comeon, how many accidental (NOT intentional) MD5 collisions did you ever see in your experience? I would call them UNlikely. But as seen here: given the right scenario , ....: jaclaz

Here it is : With your settings size is 4th token (and not 3rd which happens when you have 24h time set). But then why the other forms of filename work baffles me. Attached version 002 with the %~z1 approach, please re-test, so that I can remove version 001. jaclaz Attachment removed, see below.

Actually jaclaz only said: and he will do that AGAIN , this time actually implying that also SHA-1 is getting old: Hmmm. http://blog.dustintrammell.com/2009/01/07/md5-really/ http://csrc.nist.gov/groups/ST/toolkit/documents/shs/hash_standards_comments.pdf http://csrc.nist.gov/groups/ST/hash/statement.html And the new SHA-3 is to be soon selected. http://csrc.nist.gov/groups/ST/hash/sha-3/index.html http://csrc.nist.gov/groups/ST/hash/sha-3/Round3/March2012/index.html jaclaz

JFYI, try asking me about *any* multi-lingual/international .iso image.... http://www.911cd.net/forums//index.php?showtopic=18045&st=27 BTW the design of the *any* key has been improved, from: to: and some instructions were added: jaclaz

Sure , I have used for years a CRAY-1: http://en.wikipedia.org/wiki/Cray-1 to store DOS games and serve them on the intranet . Comeon , a server is designed to be online the most time, and RAID controllers are a complement to it, they are really NOT meant to be hybernated or go in sleep mode. Maybe you could disable the RAID controllers and use software RAID with them disks. But I am not sure to understand which is the actual issue. If it's just Windows explorer not showing drive letters, you can kill the explorer process, since it is the shell it will be re-started, and at this time drive letters should be assigned and visible. jaclaz

@Kel Black swan : http://en.wikipedia.org/wiki/Black_swan_theory it may exist even if you never saw it . @MarkR123 Generally speaking (and not necessarily aplliable to the mentioned models) Seagate disk drives (I mean inside Seagate enclosures, but WD are not that much different) are (or think to be) "smart" and, because they offer such features as "green" *whatever* and *onetouch*, and *Goflex* and *whatnot* tend to give any kind of headache. If I were you, I would try with a "generic", "no-name", USB enclosure (putting in it a Seagate or other make hard disk), as they tend to be "simpler" and thus more "compatible". For "stationary" work, I would prefer anytime: a 3.5" HDD over a 2.5" one (another issue in your case may also be the power the router may - or may fail to - provide on the USB connection ) an enclosure with a fan or an aluminium one with good heat sink but I am particularly old-fashioned . jaclaz

Well, this only suppresses messages, maybe it would work if also specific device drivers are removed form the system repository. I guess that blocking a given device or class is what the OP would like to do, something along the lines of: http://wiki.answers.com/Q/How_do_you_prevent_the_Add_Hardware_Wizard_from_asking_you_to_install_a_new_printer_every_time_the_computer_boots_up or possibly some trickery with devcon: http://support.microsoft.com/kb/311272/en-us Something like this, I mean: http://www.codeproject.com/Articles/14500/Detecting-Hardware-Insertion-and-or-Removal Or maybe using (in reverse ) this policy approach: http://technet.microsoft.com/en-us/library/dd919224(WS.10).aspx#bkmk_share2 http://technet.microsoft.com/en-us/library/cc770453(WS.10).aspx ClassGUIDs: http://msdn.microsoft.com/en-us/library/ff553426(v=VS.85).aspx Or using (again in reverse) this one: http://support.microsoft.com/kb/841567/en-us (just ideas .... ) jaclaz

http://www.netgear.com/landing/en-us/readyshare.aspx jaclaz

Sure: http://en.wikipedia.org/wiki/Windows_Resource_Protection http://msdn.microsoft.com/en-us/library/Aa382530 (no actual "answer" in post 12, BTW, just hints) Of course you can disable TrustedInstaller, but all in all it all bils down to ACL's. Strangely enough actual good info comes directly from MS: http://technet.microsoft.com/en-us/magazine/2007.06.acl.aspx How to set ACL's during install (or immediately after) is to be found, as well as the detailed procedure. These may be of use: http://www.robvanderwoude.com/allhelpw7rc_en.php#ICACLS http://lallousx86.wordpress.com/2009/06/14/resetting-ntfs-files-security-and-permission-in-windows-7/ http://social.technet.microsoft.com/Forums/en/w7itprosecurity/thread/1c922194-dd30-4674-afb1-ca72672a6172 jaclaz

Hmmm. http://www.mscs.dal.ca/~selinger/md5collision/ jaclaz

Strange. It works here. I tried in both a FAT32 and a NTFS volume (in case the issue is due to the fact that the file is stored directly in the $MFT) but it still does work. Try replacing: with: but it shouldn't make any difference . Create an :ERROR2 at the end and change one of the the two lines to point to :ERROR2 instead of :ERROR1, let's see which one creates the exception. Post the output of: Try replacing: with: jaclaz

WHICH page? You should: be terrified (not about the dropping support, rather by the futility of running Vista at all) IF you are going to upgrade get a Windows 7 instead As I personally see it, Vista is a bettered XP, only worse , while 7 is a bettered Vista, actually bettered . Seriously, I also doubt that there will be any actual difference between the various editions when it comes to malware/security. jaclaz

Just to keep things as together as possible: http://50.23.143.69/showthread.php?p=1706389 here are some more details: http://forum.notebookreview.com/hp-pavilion-notebooks/641171-unable-adjust-brilliance.html The fact that other FN keys work is good, but it is possible that different HP specific apps are loaded each hooking one or two Fn keys. It's strange, as these are normally functions of the BIOS, i.e. these keys should work also in other Operating Systems. Check your BIOS settings: http://h30434.www3.hp.com/t5/Notebook-Hardware/HP-pavilion-disable-keyboard-function-quot-fn-quot-key/td-p/480389/page/2 http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02035108&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN You could try loading *any* Linux LiveCD and see if in it they work as expected. Possibly a valid answer here: http://forums.cnet.com/7723-19411_102-554397/brilliance-control-problem/ What is wrong with it? Have you actually attempted installing the HP video driver software on the notebook? (maybe it contains some add-on). It would have been a good idea, before installing a new Win7 to image the Recovery partition (or maybe it is still available? - if this is the case it is advised that you do so, just in case) jaclaz

Good. JFYI, a small batch file (by mere coincidence also using FC.EXE) I just posted: Take into account that it is posted in a very specific thread and aimed mainly at people that do know where their towel is and it is admittedly experimental. jaclaz

Aceinfinity, take it easy, man . I will try to explain to you the issues with your batch and post (nothing personal, only trying to tell you plainly what may have contributed to the present misunderstanding) Facts: what you posted is NOT a batch file (see below ) it misses a simple, basic explanation of it's intended usage paradigm Explanation: If I remove from it the several lines of copyright related matters, it amounts to a handful of "normal", "common", batch commands (which can be made "better", as seen). It completely misses a number of checks for "sanity" and "safety" (just imagine that you compare with it two say, DVD .iso's, and you will get a bin_output\results.txt of several Gb's , and probably take a bit of time to run with CPU at 100% It cannot run from read only media (and does not provide the user for a way to choose an alternate target location), it does not check for existence of compared files, it makes no checks for runnning OS, etc., etc.. To invoke a Copyright on something, it must be something more "substantiated", IMHO, compare with: http://www.copyright.gov/circs/circ61.pdf All in all it amounts to a quick and dirty script to quickly do something VERY specific, like: on 2K/XP and later ONLY with relatively small files only on a Read/Write device only reliable if drag 'n drop is used Nothing particularly "bad" about the above , simply these things might have been specified from the beginning. jaclaz

Find attached a revised version of KFF spreadsheet. I corrected the issue by "forcing" anything in the 639<n<2399 sectors size to have 2 sectors per clusters. This leaves open a possible mistake (still to be verified) about media type 250, but I don't think it is a "real issue". I re-added the image making part <- please do test it. and report. The spreadsheet still misses some features, like the 2K/XP vs. DOS reserved sectors emulation for biggish images and a few more, including some switch to more finely choose label, and label type (BS, BS+FS, FS only and 08 vs. 28 type) and possibly a few more bits, but it should be basically working. I am removing anyway the previous attachment in post #111 For NO apparent reason attached is also a small batch to view bootsector contents and make BPB data "human redable". Clever parts: it uses built-in FC.EXE to do the binary reading, no need for external tools the output (left part - hex text) can be copied and pasted directly in Tiny Hexer or similar all variables are defined in the batch as seen on screen (useful for derivative work) and the FULL variable contains the hex text very handy to quickly show contents of a FAT1x bootsector Limits: only XP and later NOT (yet) duly tested with "strange" characters in text fields like OEM_String, Volume_Label or System_ID Experimental (release 0.01 ALPHA) Have fun. jaclaz Attachment view_bs_001.zip removed, see below. Known_floppies2.zip

Though it may be harder to copyright this new version I hereby claim copyright 2012 for the use of SHIFT /2 jaclaz

I am not getting it. This thread is about Seagate 7200.11. The XT are not 7200.11 (or are they? ) Basically on 7200.11's you can "work with terminal" in 4 (four) modes (all of them with the PCB powered through the SATA power connector): PCB attached to the drive (BOTH Head and Motor contacts connected) PCB NOT attached to the drive (NO contacts connected) PCB attached to the drive BUT with Head contacts insulated (and with Motor contacts connected) PCB attached to the drive BUT with Motor contacts insulated (and with Head contacts connected) If you are suffering from LBA0 you use mode #1 above If you are suffering from BSY you use mode #2 above (and you need to re-connect the board "live") Modes #3 and #4 are workarounds or im'provements of mode #2 to reduce or eliminate the risk of re-connecting the whole PCB "live". Your report is VERY interesting, BUT you should post (in a NEW thread) a complete description of: the EXACT issue you had the EXACT sequence of commands you used WHICH EXACTLY of the above described modes you used this way we would hopefully have a resource for the XT family of drives . Without more data it simply means that this: is true, but without exact symptoms and exact (working ) cure it would be of little help to other users. From here your other problems sound a lot like either a defective PSU (more common) or a particular setup with different peripherals drawing power from a same line (more rare) or, as you think, a shot mobo/CPU, but this is really rare. jaclaz