jaclaz

It is EXACTLY as fast as FCIV! A few runs place it within +/- 2 hundredth of seconds with FCIV, well within the possible timing/repeat loop error Now, it would be interesting to understand why exactly it doesn't work on 2K. A quick run of BINText seems to imply it uses the procedures: MD5init MD5Final MD5Update which possibly belong to Advapi32.dll, compare with: http://www.autoitscript.com/forum/topic/112711-gui-md5forfile/ Which should mean that blackwingcats' Kernelex: would do. I found here: http://d-h.st/bk4 a "very similar" 2048 bytes program, actually I believe it is the same one re-compiled (and possibly "optimized", but it is as fast as the one bhplt found) jaclaz

I will tell you this ONLY ONCE again, READ the given thread : Check the USB_MultiBoot.cmd: each and every "trick" needed (and used) is there, publicly available, you cannot really pretend that any of us will go over that again after 5 yerars, nor that we can remember exactly each and everything. STOP nagging us , START reading! jaclaz

Well, this option/possibility is relatively recent in many countries, and I presume that it is still the "norm" in some If you prefer it is a lot like a "back to the past". To give you an example, in Italy (which has been a democracy since WW2) until the 1980's there were just three channels (all "national" i.e. controlled/provided by the government), actually only 1 between 1954 and 1961, 2 between 1961 and 1975, in 1975 the control passed from the government to the parliament, but from this to "plurality", especially related to News, it has been a looong way. jaclaz

This is not really "good news" for a "supporter" of Vista . The data can be read in terms of "diifferential interest" over the "previous OS" . Vista -> slow rate as perceived as not much an improvement over XP 7 -> fast rate as perceived as lots of improvements over Vista 8 -> slow rate as perceived as not much an improvement over 7 Though we all know how 7 is a further Service Pack to Vista actually bettering it and 8 is a further Service Pack actually MUCH worsening it (at least when it comes to interface). jaclaz

This one: still seems the winner (re: size) BUT the one by Glenn9999 is MUCH FASTER and actually almost as fast as FCIV. On a 512.000.000 bytes file: md5file.exe 2.67 md5_file.exe 1.75 fciv.exe 1.58 dsfo.exe 2.03 (but it also shows progress and time) On a 2,615,529,472 bytes file: md5file.exe 37.49 md5_file.exe 19.92 fciv.exe 19.71 dsfo.exe 35.45 jaclaz

Well, as a matter of fact we have had this for years, it is called "television". It's interesting while the manufacturers made TV sets into (Linux running) PC's, someone is going to dumb down back the terminal. JFYI: http://reboot.pro/topic/9915-the-good-thing-is-that-engineers-never-stop-to-surprise-me/ jaclaz

There must be some "basic" issue with MMC. You can try opening the event files with the nice Nirsoft tool: http://www.nirsoft.net/utils/my_event_viewer.html see also these: About re-registering dll's, the trick of re-registering each and every .dll has traditionally saved more than one installs If you can do a "parallel" install of Server 2003, you might be able to do something along the lines of this: http://reboot.pro/topic/3717-xpsp1-with-full-commandline-and-ntfs-below-10-mb/?p=154017 which made use of another nice Nirsoft tool, dllregview: http://www.nirsoft.net/utils/registered_dll_view.html that would give you more control (as opposed to registering *everything*) jaclaz

It depends on what was the original cause of the BSY or LBA0 issue (or other issue) you had and that the procedure managed to re-set. The general idea is that "unbricking" a disk is just a possible way to recover data from it, once you managed to recover the data, you do BOTH the short and long test with Seatools, and if any of them fails, you simply throw the disk in the dustbin (or if the disk is still under warranty, RMA it for a replacement). Actually repairing or reconditioning a disk (apart from the "reset" done through the described procedure) is simply outside the scope of this thread and well beyond the knowledge/experience/capabilities of anyone taking part to the thread , is a "professional" chore to be carried by a pro, with professional software and hardware/tools (and with professional level knowledge). To give you an example, if something has gone wrong with one head (electrical/electronic) it is very possible that the disk will work alright for a few more years (in the reduced at 62% status), but if a head has touched a platter (mechanical damage), the disk working status will likely come to an end within days or weeks, possibly enlarging the 38% bad area, and thus corrupting data in the currently good 62% area. As a matter of fact, I have read how it is possible that a reconditioned disk can sometimes be made out of a larger disk with one or more heads disabled in firmware. (but this is again "reserved" to manufacturers/professionals) jaclaz

Well, I did my best to try and avoid you fall for the chocolate covered banana trap : http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html but you apparently are very convinced of the method you chose, which is good as one should always defend his/her beliefs. Still, if you want to do that, you will have to go through the historical thread and understand what winsetupfromUSB 0.2.3 actually does (which as said would be much easier to understand reading the batches that USB_MultiBoot.cmd is made of). You might also be interested in this thread: which is about installing XP from USB without using any third party tool. And in this one: Which here: page__view__findpost__p__842814 reveals one of the "tricks" used to avoid the deletion of the $WIN_NT$.~LS folder. jaclaz

Naah it's only because it is easily available on my italian keyboard, as said it is up to you to find a character that is not used in "Korean" (or "other rare language" files). BTW it is possible (but you will have to experiment) that you can use one of the "lower" ASCII Characters, in the range 0 to 31 decimal, really cannot say. jaclaz

Sure , but WHAT is the reason why you should use this "mixed mode"? If you want to make manually something, you NEED to study the mentioned "historical" thread and then INSTEAD of winsetupfromusb 0.2.3, you should use as "base" wimb's USB_MultiBoot.cmd: as it is written in batch, so you can better analyze the steps it makes and either change them or replicate them manually. jaclaz

Yes, the semicolon is the default EOL of the FOR, you can do something like: FOR /F "eol=§ tokens=1,2 delims=, " %%a in ('TYPE 1.inf') do echo %%a,%%b The § character is in "Windows", in command line it will "look" different, it's ALT+0167, but you can use any other "extended ASCII" character that won't be normally used in a .inf. jaclaz

I am not getting it. What is the problem? You want to make manually something that WinsetupfromUSB already does? Then you will need to go through ALL the "historical thread": Which version of WinsetupfromUSB are you using? I presume the old 0.2.3, try the 1.0 beta 8 instead: DO NOT double post. (your post in the main thread was merged to here). jaclaz

Due to the stupid board software all links that contains brackets are parsed incorrectly. Here are the two cdob posted in a clickable format (it is needed to post them using the little icon looking like a chain): http://technet.microsoft.com/en-us/library/dd799299(v=WS.10).aspx http://msdn.microsoft.com/en-us/library/windows/desktop/aa365449(v=vs.85).aspx A set of refereces should be also: http://technet.microsoft.com/en-us/library/hh825689.aspx http://technet.microsoft.com/en-us/library/hh825691.aspx http://technet.microsoft.com/en-us/library/hh825709.aspx http://technet.microsoft.com/en-us/library/hh825691.aspx This is the refeference to set id: http://technet.microsoft.com/en-us/library/cc753840(v=ws.10).aspx ... but if you are not an OEM, additionally experienced with GPT disk, you cannot use it : jaclaz

Yes it is, one uses TYPE, the other uses FINDSTR More seriously, try them on a UNICODE .inf and check the differences. See here: http://www.robvanderwoude.com/type.php Convert Unicode to ASCII vv TYPE is UNICODE compliant (and the result will normally be "plain text"), FINDSTR is not. jaclaz

Well, the perplexing thing is that you doubted my word for it. I stand by my comparison to exposing merchandise in the shop window but require that passers have special glasses/viewers to see it: jaclaz

Well, Google actually maps odours too: http://www.google.com/intl/en/landing/nose/ jaclaz

You mean UNICODE? jaclaz

In what sense precautions? The file TYPEd must be "plain text", that's all. jaclaz

See if anything here is of use/help/etc.: ?p=160588 This: should work alright (but is about Windows 8 on USB hard disk, so you will need to experiment, reportedly it is possible to use a Windows 7 VHD with this, though cannot say if in the "native" mode). jaclaz

Just to keep you informed, you have at least one satisfied user of the new set : http://reboot.pro/topic/11852-make-pe3-program-to-create-portable-windows-7-pe/?p=170386 jaclaz

It would be interesting to know HOW exactly you got to know that it is "rubbish" (it is not ). If you want to learn WHY it is not, read : (where you will also find some links to simple, clear, complete Tutorials by Steve6375) Well, if you are looking for a multiboot USB stick you are in the wrong place, this is: MSFN Forum > Unattended Windows Discussion & Support > Multi-Boot CD/DVDs Since what you really want is a multi-boot USB stick to install from it different flavours of windows, this is more suited : MSFN Forum > Member Contributed Projects > Install Windows from USB http://www.msfn.org/board/forum/157-install-windows-from-usb/ jaclaz

See if this works: http://md5sum.codeplex.com/ Executable is 7168 bytes. Or this one: http://keir.net/md5file.html 6656 bytes. jaclaz

Try with a "plain": FOR /F "tokens=1,2 delims=, " %%a in ('TYPE 1.inf') do echo %%a,%%b jaclaz

Pipe it into FIND. FINDSTR/IR "sp.qfe" 1.inf | FIND /i "SP2QFE" jaclaz