jaclaz

Nice. jaclaz

Good, now we have seemingly the confirmation that that stupid program needs to be launched once having changed dir to it's directory (which means that some of the needed files to execute it are in that directory). So, change the test.cmd to: @ECHO OFFSETLOCAL ENABLEEXTENSIONSCD /D %~dp0sccui.exeand it should work. If it does, try using in startnet: START "Mycmd" /D "%systemroot%\System32\bin" /W "%systemroot%\System32\bin\sccui.exe" jaclaz

Good. Now remove from test.cmd the "CD .." line. @ECHO OFFSETLOCAL ENABLEEXTENSIONSECHO Test.cmdECHO %~dp0ECHO Changing directory ...CD /D %~dp0ECHO Now executing %~dp0sccui.exePAUSEsccui.exeAnd now what happens if you press the CTRL+C and what happens if instead you do "press the any key"?jaclaz

It is seemingly the "wrong" type of converter. Compare with: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-163#entry988633 http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-108#entry915966 Particularly check this (also linked in the read-me-first): http://www.interfacebus.com/voltage_threshold.html The seagate disk - for all we know - uses TTL, i.e. it understands anything between 2.0 and 3.3 V as a "high" and anything between 0.35V and 0.8 V as a "low" (and emiits the same signal levels), if your converter, as I believe uses instead TTL/CMOS levels, the "highs" can be higher that 3.3V and the disk will NOT understand them (the lows should not be a problem). If you bought it, ask the vendor about which EXACT TTL levels (NOT the Vcc voltage at which it can be powered and from which a device can be powered) the converter uses, since this: http://www.mikroe.com/downloads/get/1509/max3232_manual_v100.pdf seems like a "simple" circuit I believe that it is NOT a "variable" one (but it could be ). HOW EXACTLY are you powering that converter? jaclaz P.S.: Maybe you can get away with a 2.2 kOhm resistor: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-141#entry956029

There has been a misunderstanding actually more than one, and possibly a couple of mistakes in the posted batch. Let's start from scratch, OK Check that the test.cmd is in the directory X:\windows\system32\bin\ i.e. %systemroot%\system32\bin\ and that it has these contents: @ECHO OFFSETLOCAL ENABLEEXTENSIONSECHO Test.cmdECHO %~dp0ECHO Changing directory ...CD /D %~dp0CD ..ECHO Now executing %~dp0sccui.exePAUSEsccui.exeWhen you are prompted to "Press any key", press CTRL+C instead to stop the batch. Are you having a console with prompt: X:\windows\system32\bin>Yes or No? IF you have it as above, and type in it: sccui.exeand press [ENTER] what happens? jaclaz

Breaking the Law is illegal. Breaching a contract may be illegal ONCE (and IF) a Court has ruled that the contract breach happened AND it was illegal (i.e. it is breaking the Law) and that the contract is legal. It is NOT the same thing. jaclaz

Well, no. Meaning that you posted about having a converter (it is not a controller) based on MAX232 and capable of doing BOTH the "low" and the "high" TTL levels. (historically 90% - say - of converters based on a MAX232 are ONLY "high" level TTL) IF - for any reason - that converter works at the "high" TTL level, a loopback test will work alright, BUT it won't be EVER capable of "talking" to the disk. You have to make SURE that your converter is actually designed to work at the "low" TTL levels AND that is working at those levels. Please check again the Read-me-first: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ particularly point #6 And/or post a link to the specifications of the actual converter you are using or schematics (if autobuilt). jaclaz

Yep, but it makes no sense that from a "same" command prompt the stupid thingy works AFTER the first time (when the error presents itself and you press Ok to it and you run the command again) . At least this is the behaviour I understood from the tests performed @ jbrush115 Usually giving up is NOT an option. Maybe we could call this a "time-out" waiting if some other member has an idea for further tests/approaches.... jaclaz

Well, actually it is not respecting the PCI standards, being "illegal" is different. These clowns here: https://www.pcisecuritystandards.org/ https://www.pcisecuritystandards.org/security_standards/role_of_pci_council.php just as any self-appointed, self-generated assembly of clowns calling themselves an "industry standard" remain mainly worth-nothing/do-nothing people that pontificate about theories, are of not any practical use if not to provide a valid justification for the big Credit/Debit Card circuits (Visa, Mastercard, American Express, etc.) continuing to do whatever they see fit and keep their dominance on market and market shares. Whether a country or state Law - separately and independently form the above - do coincidentally prohibit that storing, it is another thing. jaclaz

Sure, Seatools for DOS: http://www.seagate.com/support/downloads/item/seatools-dos-master/ they come as a bootable .iso. jaclaz

The ONLY things that should be done after an unbricking are: image the disk/save the data (if needed) run the Seagate tests, BOTH the short and the long oneif any of the two tests fail, throw the stupid disk in the dustbin. jaclaz

Try describing your issue in more detail, as is it is not understandable (by me at least). jaclaz

No guide . You can try tracing the SATA channel back from the chip pins (READ the given thread), but you will have to see how encryption (if any) works. Basically you are in a Catch22 situation, if you have to ask (and ask here on MSFN) you won't be able to do it. @bphlpt That family of WD drives have on the PCB a SATA to USB bridge, there is NO SATA connectors exposed (if you prefer the external case is just an external case with NO SATA to USB bridge, and the stupidly tiny USB connector of the cable coming from the computer is inserted directly to the disk drive PCB). jaclaz

That would really be cruel (after all the good guys from NSA that will listen to it are good chaps) . About the botched Surface 2 update, traditionally MS excuse (about botched updates for conventional PC's) was "there are so many different possible combinations of hardware that notwithstanding our extensive testing it is still possible that this update is conflicting with some other installed software on a minimal amount of PC's" Proof we are not alone: http://www.pcdoctor-community.com/blog/posts/2013/10/22/9-Things-Microsoft-Could-Do-To-Fix-Windows-8.1/ jaclaz

Is in any way the command prompt you get when pressing CTRL+C to stop the batch different from the one that you get after the error? jaclaz

Strange. I mean if it is "too early", it shouldn't work from the command line after the error. Try again with: @ECHO OFFSETLOCAL ENABLEEXTENSIONSECHO Test.cmdECHO %~dp0ECHO Changing directory ...CD /D %~dp0CD ..ECHO Now executing %~dp0sccui.exePAUSEbin\sccui.exeTry with the above.Once "normally" i.e. pressing "any key" to end the pause, and once pressing CTRL+C to stop the batch and issuing to that command prompt manually the bin\sccui.exe. Result should be the same (cannot say if working or not working). jaclaz

My bad remove the "\bin" from lines "ECHO Now executing %~dp0bin\sccui.exe" and "%~dp0bin\sccui.exe" : jaclaz

Or maybe it is initiated "too early". If this is the case a PAUSE won't be useful. Try using in startnet: cmd.exe /k %systemroot%\system32\bin\test.cmdand put in %systemroot%\system32\bin\ a test.cmd with the content: @ECHO OFFSETLOCAL ENABLEEXTENSIONSECHO Test.cmd ECHO %~dp0ECHO Now executing %~dp0bin\sccui.exePAUSE%~dp0bin\sccui.exejaclaz

Yep, but when you open a command console by default it will open in C:\Windows\System32 (more accurately it will open in %systemroot%\system32 ). Try doing either: CD /D %systemroot%\system32 & bin\sccui.exeor %systemroot%\system32\bin\sccui.exejaclaz

WHERE (exactly) did you learn that? WHICH (specific) model of WD disk drive are you referring to? jaclaz P.S.: Do you mean a SATA bypass, such as: http://cdn.shopify.com/s/files/1/0207/3304/files/usb_to_sata_conversion.jpg?1921 http://malthus.zapto.org/viewtopic.php?f=3&t=569

Post the EXACT command line you use in the command prompt window (which works) and the EXACT command you added to startnet (which fails) and the EXACT error message you get. It is possible (probable) that it is an issue connected with PATHs or however with environment variables, could it be that the program "automated launch" happens to early? Have you tried spawning a new console through startnet?. jaclaz

Maybe if you actually describe in detail the workaround you found, it would be useful to someone else. What do you mean by: can you expand on the exact procedure you used which exact files are involved, etc.? jaclaz

Prepare the USB stick from your original CD on someone else's computer with a working CD/DVD drive. Find a friend or relative that has a working PC and use it to prepare the USB stick, or at least to make a .iso of the original CD. jaclaz

Which presumably is a non-original, heavily modified XP source, (please read as WAREZ) . READ, this time ATTENTIVELY, MSFN Etiquette: http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules Particularly point #1.a: You won' t have support on this board for using that. jaclaz

Yep, all browsers I tested (with the exception of Opera ) always added that senseless Alternate Data Stream (of course on NTFS only). BUT : http://support.microsoft.com/kb/883260/en-us maybe the issues NotTakenUsername is having are connected with DefaultFileTypeRisk or with filetypes associated to a given risk level: http://www.msfn.org/board/topic/170513-how-to-disable-security-popups-under-winpe/ jaclaz