jaclaz

That's an actual stupid thing of Windows Vista and later that - probably for the first time - turned around as a good thing . You imaged a DISK (or \\.\PhysicalDrive) you have to restore the image to a DISK (or \\.\PhysicalDrive) NOT to a DRIVE (or \\.\LogicalDrive). In my example: you use the line with the RED drive letter to identify the GREEN parent and you supply it (the parent or the GREEN BOLDED one) to dsfi.... DISK=PhysicalDrive=bigger container=starts at absolute sector 0 LBA=what you see in Disk management in the lower pane, on the left DRIVE=LogicalDrive=Primary Partition (or Logical Drive inside Extended Partition) contained inside DISK=starts at whatever sector is addressed for it in the MBR or in the EPBR=what you see in the top pane in Disk Management (and has normally a Drive letter assigned or in the lower pane on the right as part of the DISK The good MS guys made their best to confuse the matter, rest assured that you are not the first one (and unfortunately not even the last one ) to fall for this misunderstanding. jaclaz

Thanks, almost perfect , though I do miss the possibility of quickly re-ordering the fonts.... jacla

migrate.inf? http://www.911cd.net/forums//index.php?showtopic=19663 http://www.911cd.net/forums//index.php?showtopic=18782 jaclaz

Well, what most people tend to confuse is file format with file extension. What you made with datarescue.dd is a RAW (file format) image, i.e. an exact, byte-by-byte, sector-by-sector, image of the source hard disk. You can give it *any* name, and as well *any* extension, like .dd or .img, it will still remain a RAW image. If you prefer the extension given to a filename has two scopes: be a "mnemonic" to quickly know what file format it is (of course only useful if you give appropriate extensions) be useful for associating those files to a given program for all it matters you could name the image mynicespreadsheet.xls (only Excel will choke if you attempt double clicking on the file ). Which process? If you dd the 137 Gb image to the 1 Tb disk you need NOT the original disk connected. On the other hand if you already recovered most of the files from the "capped" hard disk or from the dd image, you may want to "skip" this part (you already have the image, so if needed you can do this later) and check just the "failed" disk with the Atola tool. Unless *somehow* we change something in the failed disk, the accessible data will still remain the 137 Gb you already imaged. "Restoring" the dd image to the "new" disk is simply an approach that allows the use of CHKDSK and TESTDISK on a "full sized" space, which may (or may not) help to fix the filesystem/access the files IF you did not managed to already save them (anything beyond the image size will remain anyway "a suffusion of yellow"). Easiest? Create a small partition on the disk and format it. Open tiny hexer, FIle->Disk->Open Drive, you wil normally see something like (example): The right PHYSICALDRIVE is the "parent" of the drive letter assigned to the newly created partition. jaclaz

I guess you will have to "dirty your hands" with SID's, those are created "on-the-fly" at logon. See (as an example): http://www.raygibson.net/kb/profile_migration/ The actual values are stored in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon See: http://blogs.technet.com/b/heyscriptingguy/archive/2007/01/23/how-can-i-get-the-name-of-the-last-user-to-log-on-to-a-computer.aspx This may be of use as a quick reference: http://www.scriptlogic.com/support/CustomScripts/environmentVariableReference.html jaclaz

I call that foolproof instead. And of course: Usually it is a no-win/no-win situation, what you get at the end is more complex code/script, and anyway someone will be able to have it break or do something else. I believe more in making the bare minimum checks and make the final user break it at will until he/she learns how to use it properly, i.e. make him/her more responsible, or if you prefer to behave more proactively than the usual "passive mode", expecially since batches/little .vbs scripts are normally a QUICK workaround around an issue or a more convenient way to run a set of otherwise complex commands. The fact that I know not any other programming language and the usual guy which comes out saying "it can't be done in batch" sometimes causes the creation of one of my senselessly complex batches (that a real programmer would write in a much more suitable language), but they still remain "quick and dirty tools" or (working ) POC's, I would say that a suitable adjective for batches (and to a lesser extent .vbs) is "legacy": http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/legacy-is-not-a-pejorative.html Now, the essence of a "quick and dirty" tool is to be BOTH quick AND dirty..... jaclaz

Which link? In which post? Since this thread is now 214 pages, you looked at less that 5% of it, no wonder you didn't find a reference to it. What is the actual question? Which specific firmware do you need/want? jaclaz

To be fair , it is a UEFI vulnerability, a similar one already found and published for MAC's by some good guys from down under. Unsurprisingly, freedom vs. security imply some trade off's: http://blogs.msdn.com/b/b8/archive/2011/09/22/protecting-the-pre-os-environment-with-uefi.aspx http://www.itsec.it/2012/09/18/uefi-technology-say-hello-to-the-windows-8-bootkit/ jaclaz

Slightly bigger but allows to copy and paste the script "as is" (without any need for carets) at the END of the batch.... @ECHO OFF SETLOCAL ENABLEEXTENSIONS FOR /F "tokens=1 delims=[]" %%A in ('FIND /N "::THIS IS START OF VBS SCRIPT::" %~dpnx0') DO SET More_offset=%%A ECHO 'Hi I am yanklines.vbs script>yanklines.vbs FOR /F "tokens=*" %%A IN ('MORE +%More_offset% %~dpnx0') DO ECHO %%A>>yanklines.vbs ECHO do whatever the batch is supposed to do GOTO :EOF ::THIS IS START OF VBS SCRIPT:: If WScript.Arguments.Count <> 2 then WScript.Quit end If Const ForReading=1, ForWriting=2 Dim i,j Set objFSO=CreateObject("Scripting.FileSystemObject") Set objInputFile=objFSO.OpenTextFile(WScript.Arguments.Item(0),ForReading) Set objOutputFile=objFSO.OpenTextFile (WorkingDir & WScript.Arguments.Item(1),ForWriting,True) Set objDict=CreateObject("Scripting.Dictionary") objDict.CompareMode=1 j=0 On Error Resume Next While Not objInputFile.AtEndOfStream arrinputRecord=split(objInputFile.Readline,"vbNewLine") strFirstField=arrinputRecord(0) If objDict.Exists(strFirstField) then j=j+1 Else objDict.add strFirstField,strFirstField End If Wend colKeys=objDict.Keys For Each strKey in colKeys objOutputFile.writeline objDict.Item(strKey) Next objInputFile.Close objOutputFile.Close jaclaz

No. You are not in the same situation as described in the mentioned thread. In that situation the firmware enters in a kind of loop, doesn't accept commands, shows continuoausly a LED:00000xyz FAddr:0000mnop kind of error and detaching the board (completely and/or just the head or the motor and - in some cases shorting the read channel) is a way to exit that loop and make the interface accept the commands. The whole point, in your situation, is that we don't know WHICH commands (if existing at all) may correct the issue that makes the drive spin continuously and be BSY. The "common" issue is a continuous loop of the firmware that creates the BSY state, your particular one is evidently - while still a BSY - caused by "something else". You have to understand that all we know are "crumbs" , see: jaclaz

Well, at least we tried . But what would be the use of choosing the partition in your particular setup? jaclaz

That's better. (but not yet the "full story", JFYI: http://support.microsoft.com/kb/196288/en-us http://support.microsoft.com/kb/220853/en-us These might apply to 2K also: http://unattended.msfn.org/unattended.xp/view/web/7/ jaclaz

JFYI : http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/legacy-is-not-a-pejorative.html

Any Top Level Executive actually saying the highlighted/bolded sentences in public: Should be IMMEDIATELY taken to a Court and judged (and condemned) for "utter lack of intelligence and common sense", IMHO. Being a clown is not an offense per se, but there are limits..... jaclaz

I don't get it. That would be a check to make sure that exactly 2 arguments are passed to the script, if the script is invoked only from a batch and only with the correct 2 arguments there is no need for that check (which should be made BEFORE in the calling batch). Or am I missing something? jaclaz

But does it spin down when you issue the corresponding Z command? jaclaz

I think noone said that, what has been said or just hinted is that you posted a series of contrasting statements and a number of plainly wrong data, i.e. you failed to fully comply with the Standard Litany: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html and/or you falled by slipping on a chocolate covered banana : http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html If you prefer it was a (kind) invitation to better organze your reports, so that people willing to help you will need not to use their crystal ball or guess which among the contrasting statement or among the provided data is the right one. Mind you this will usually result in boith faster and "better" help/support provided, so ultimately it is an advantage to you . jaclaz

AWSUM EVEN IF I GUES U CANT MAK EVRYONE FINE jaclaz

I am not sure to understand (actually I am sure I don't understand ), you posted: In that occasion HOW (which media if not the CD) did you use to attempt installing the XP? But what I meant was that it is possible that you have "other" issues with booting from CD (such as BIOS settings, a "bad" drive or bad cable/connection) but that right now the culprit sounds being the non bootable CD, as that PC can boot from the CD device (if bootable media is used), and you actually booted from it recently, didn't you? jaclaz

The ONLY set of instructions we have are here (and they are not validated by any other member, so more than the usual YMMV ) (already linked to thread): specifically the quote in this post: jaclaz

IMHO this is - besides smaller - "plainer": 1.000 bytes instead of 1.356 BUT including 10 bytes for the "@ECHO OFF", so actually 366 bytes smaller or almost 27% smaller . @ECHO OFF&( ECHO ^If WScript.Arguments.Count ^<^> 2 then ECHO WScript.Quit ECHO end ^If ECHO Const ForReading=1, ForWriting=2 ECHO Dim i,j ECHO Set objFSO=CreateObject^("Scripting.FileSystemObject"^) ECHO Set objInputFile=objFSO.OpenTextFile^(WScript.Arguments.Item^(0^),ForReading^) ECHO Set objOutputFile=objFSO.OpenTextFile ^(WorkingDir ^& WScript.Arguments.Item^(1^),ForWriting,True^) ECHO Set objDict=CreateObject^("Scripting.Dictionary"^) ECHO objDict.CompareMode=1 ECHO j=0 ECHO On Error Resume Next ECHO While Not objInputFile.AtEndOfStream ECHO arrinputRecord=split^(objInputFile.Readline,"vbNewLine"^) ECHO strFirstField=arrinputRecord^(0^) ECHO ^If objDict.Exists^(strFirstField^) then ECHO j=j+1 ECHO Else ECHO objDict.add strFirstField,strFirstField ECHO End ^If ECHO Wend ECHO colKeys=objDict.Keys ECHO For Each strKey in colKeys ECHO objOutputFile.writeline objDict.Item^(strKey^) ECHO Next ECHO objInputFile.Close ECHO objOutputFile.Close )>yanklines.vbs jaclaz

Wouldn't it be protected by Copyright Laws? In any case you could have people to which you provide the install routine to sign a NDA: http://en.wikipedia.org/wiki/Non-disclosure_agreement You know, just to be on the safe side. jaclaz

Define latest. Googling for: "Download:" "visual c++ redistributable Package" gives results up to 2010 SP1, and also this search: http://www.microsoft.com/en-us/download/search.aspx?q=Microsoft+Visual+C%2b%2b+Redistributable+Package gives more or less the same results. jaclaz

HOPE DAT LOLCAT SPEEK IZ STILL K? http://speaklolcat.com/ jaclaz

Where? EXACT model make of the PC AND of the graphic card, please. A plus would be having also make/model of the monitor/display. Explanation: you have not installed the proper graphic card driver and you are using the default "one-size-fits-all" VGA driver, which is limited in BOTH resolution and number of available colours. With the data you provide we might be able ot help you locating the proper drivers on the Manufacturer website or elsewhere. jaclaz