jaclaz

Seemingly more details are here: http://www.neowin.net/forum/topic/1105733-bypass-metro-ui-while-login-windows-server-2012-like/ jaclaz

Yep, that's the tricky part. See what the Atola tool has to say, first thing (remember that it is just a "semi-random guess" that the drive self-capped ). http://blog.atola.com/restoring-factory-hard-drive-capacity/ whether tool will work under 7 and particularly under 7 x64 is up to you to find out. jaclaz

Well, this has actually nothing to do with WIndows 8 (i.e. it's collateral damage) it is evident how the idea is to push Chrome. And as well, the good thing is as always freedom I cannot imagine how much should Symantec pay me to install any of their bloated crapware on any of my machines, as an example . jaclaz

Something wrong with your link, it doesn't work. It looks like an old link. This works: http://wayback.archive.org/web/*/http://xoomer.virgilio.it/gloriosus/software/programs/regcompact1.0.zip jaclaz

Run CHKDSK /R Then, try accessing the disk with TESTDISK. The partition should show "normally" (it might protest about the backup of the bootsector, but that is irrelevant), then by pressing "p" you should be able to access (and copy) files (with "c"). You most probably cannot access the files directly because of NTFS permissions, since we are into "living dangerously" you can try faking to be "System", here: http://reboot.pro/17501/ try using RunasSystem to launch a file manager (like 7-zip) or a command console and see if you can copy the files to another disk (or you may create another partition on the rest of the 1 Tb disk).. jaclaz

Exactly ... among those you were able to find, of course . (that's the whole point , I always get goose bumps when I read "absolutely absolute" statements ). jaclaz

I would rephrase that in a less "absolute" meaning, nonetheless, those drivers may exist but be not publically available, as well the same could happen for other drivers, more recent than the ones you have ... jaclaz

Cannot say. Another "queer" behaviour of Winddows 7? Post a screenshot of Disk Management... jaclaz

Hey peeps , what about making some order? As seen from the outside: The OP mrbigmouth50 asked (vaguely) for drivers for a "generic" Intel PRO/Wireless 2200 card (but he did detail how the intended target is an Acer Travelmate 4502Lmi ) submix8c pointed to a resource on the Lenovo site about a card Intel PRO Wireless 2200BG but with NO driver for Win98 PROBLEMCHYLD (rather apodictically) stated how WIn98 drivers for that (which?) card do not exist jumper provided a link (still on the Lenovo site) for the Intel PRO/Wireless LAN 2100 3B card and some ideas to modify the 2K drivers for use with WIN98 PROBLEMCHYLD stated how the given links were not working (possibly meaning that the links do work in the sense that they open a page, but that the drivers in it are not suitable for the card (which?) the OP asked about) jumper confirmed that drivers for WIn98 drivers exist (for which card?) and that the links are working (possibly in the sense that they do open a page) I guess that in comparison the guys building the Tower of Babel were kids when it comes to mis-communication..... 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