jaclaz

I can confirm, the M is VERY loud (which is a good thing IMHO). Clickity, clickity, click. jaclaz

No. It all depends on how much time you want to spend in creating an alternate booting sequence, if you want/can use a different CD bootsector/loader, etc. etc. If everything has to come from MS, yes. jaclaz

In an attempt to better the little batch, I actually seemingly bettered it. Now: it can run on 2K too (no need for fsutil) it can run on read-only media (no more temp file) can process files larger than 512 bytes (like whole floppy or super-floppy images) values are now right-aligned it is a tadbit slower in first screen coming up, though Verson 0.05 attached. (don't try finding version 0.04, it was for internal use only) In order to remove the temp file I had to introduce a possible bug, that along the good old tradition I will call "feature" . If the bootsector starts with "::" i.e. with 3A3A the first two bytes will be reported as 0000. I'll see if I can later remove this "feature". jaclaz view_bs_005.zip

A few questions: Do you understand the difference between KB and KiB, MB and MiB, GB and GiB, TB and TiB? Do you realize that "free space" and "size" are not interchangeable tems? Is the partition you can see, by any chance, formatted with the NTFS filesystem? Which EXACT make/model is that hard disk? Do you have a specific reason to suspect the presence of a hidden partition? Start with #1: http://en.wikipedia.org/wiki/Gigabyte jaclaz

Yes, you can, but as said the result being functional depends on a number of factors, that tutorial is about: "standard MS source" "standard Service Pack" integration What you have in your hands may be: a OEM Install disk (and the OEM may have added something that need "additional" or "more relaxed" settings) a OEM Recovery disk (and the OEM may have added something that need "additional" or "more relaxed" settings) any of the above with additional KB integrated (and this may need "additional" or "more relaxed" settings) to the above you add the possible case-sensitiveness involved in either the ripping, the running OS or the file copying The good news are that you have nothing or very little to lose, in the worst case you will have one more shiny coaster. jaclaz

WHY? The "recommended" way is to use mkisofs (with the proper switches) or OSCDIMG (again with the proper switches). And you should always IMHO use nothing but IMGBURN to burn the .iso to media. jaclaz

Could you replace the "usual" with the actual EXACT set of commands you issued? There is very little of "usual" in this kind of things, expecially if you don't specify if what you tried initially was the BSY or LBA fix, since you are talking of spin down/spin up and of detaching the board, I presume you used the set of commands for BSY, but it would be really of help if you could post the full list of commands you issued or confirm that those that ended up successfully were EXACTLY those on the mentioned page: http://computersciencelabs.blogspot.com/2011/02/seagate-720012-sim-error-firmware-fault.html jaclaz

The parameters you gave mkisofs simply do not sound "right". Particularly on Linux sytems you should be VERY aware on CaSe SeNsItIvEnEsS. A "normal" XP INSTALL (NOT recovery, which is what you asked about) disk has the /I386 folder and it is populated by 8+3 CAPITAL ONLY files. A SP integrated INSTALL disk (or a Recovery disk, or anyway an OEM disk) may have the need for a "wider" -iso-level and/or -multidot. The typical mkisofs command used (on Windows) to take care of most of the issues (but the name of files must be compliant on source) is more complex, in your case it could be: mkisofs -v -iso-level 4 -l -N -D -d -J -joliet-long -r -volid "Advent6415-WinXP-patch1" -A MKISOFS -sysid "Win32" -b cdboot.bin -no-emul-boot -boot-load-size 4 -allow-multidot -hide cdboot -hide boot.catalog -o Advent6415-WinXP-patch1.iso See more here: http://reboot.pro/9696/ AND here: http://ubuntuforums.org/archive/index.php/t-338906.html "Microsoft Corporation.img" could be another problem (the space in it and the mixed mode CAPITAL and small letters). Rename it to "cdboot.bin". All in all your command line (still in Windows) could be: mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -r -volid "Advent6415-WinXP-patch1" -A MKISOFS -sysid "Win32" -b cdboot.bin -no-emul-boot -boot-load-size 4 -allow-multidot -hide cdboot -hide boot.catalog -o Advent6415-WinXP-patch1.iso You will have to verify if the particular MKISOFS you are using supports the used options. The page you quoted says: You seemingly did not use the -N, nor the -relaxed-filenames nor the -d -D ! If you check *any* tutorial about re-creating a Windows XP INSTALL disk after having slipstramed a service pack with mkisofs, you will see how the mentioned switches are always present: http://www.g-loaded.eu/2007/04/25/how-to-create-a-windows-bootable-cd-with-mkisofs/ http://sysblogd.wordpress.com/2008/04/23/how-to-build-a-windows-xp-sp3-integrated-installation-cd/ http://www.montanalinux.org/SlipstreamWithLinux.html jaclaz

Set aside legal implications (about License), the answer is Yes/No. http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/questions-with-yes-or-no-answers.html Yes, generally speaking it is possible but No, it depends greatly on the specific way the Recovery Disk is made. The "proper" way is to install to the 7096 from a "full" (and legally Licensed) source, then create a Recovery CD/DVD for it. 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