jaclaz

Just for the record (NOT related to the previous issue) there are a few multivolume .EXE/.RAR files that have issues with 7-zip (9.32 alpha). Used "plain", i.e. directly, not through Universal Extractor (which probably would use Unrar instead) But I had no time to check if they were OK with previous versions. Both these sets of Server2003 files (huge): http://www.microsoft.com/en-us/download/details.aspx?id=24445 http://www.microsoft.com/en-us/download/details.aspx?id=19727 But, generally speaking, some kind of mechanism to be able to "retry" with an older (possibly "stable" or however "non-alpha") version or to choose among different versions would be IMHO a not-so-trifling improvement (and not only limited to 7-zip). jaclaz

This is very strange. The first method should not work because RunAsSystem (according to the docs) will only accept a process name (and no further parameters)-. The second should work unless the cmd.exe that is spawned by the batch changes back to "admin" user. If this is the case also the compiled batch (actually a SFX installer) behaves the same. Try running this batch through RegAsSystem: whoami /allpausereg. exe /?whoami /allpauseand compare with the output of whoami /all given from the command prompt opened by RunAsSystem. Otherwise it will be needed a "real" executable. On another approach, what happens using Nirsoft's nircmd? http://www.nirsoft.net/utils/nircmd.html the command runassystem: http://www.nirsoft.net/utils/nircmd2.html#using allows process and command line parameters. jaclaz

Which EXACT make/model is the "microcontroller"? If you format the SD card (i.e. you create a single volume in it) with a recognized filesystem (such as FAT16/32/NTFS etc.) that Windows recognizes, the volume will get a drive letter and if you assign to it a volume label, in Explorer you will see it with the drive letter and the Label, the drive letter may change when you connect it to another system (as drive letters are automatically assigned by windows) whilst the Label will obviously remain the same. But the Volume Label is on a much higher level than device ID (PID/VID) and Device name, these are stored in the "microcontroller", together with it's "on device" firmware. jaclaz

Well, good news but being a picky guy I cannot but underline how the given link: http://www.dvice.com/2014-5-26/your-existing-ssd-can-be-made-300-faster-and-60-more-efficient? is "via" Neowin: http://www.neowin.net/news/ssd-breakthrough-means-300-speed-boost-60-less-power-usage-even-on-old-drives which was "via" pocket-lint: http://www.pocket-lint.com/news/129023-ssd-breakthrough-makes-drives-300-per-cent-faster-and-60-per-cent-more-power-efficient which finally links to the actual source Techon: http://techon.nikkeibp.co.jp/english/NEWS_EN/20140522/353388/ And the actual graph of the simulation: http://techon.nikkeibp.co.jp/english/NEWS_EN/20140522/353388/?SS=imgview_e&FD=48575398&ad_q Seems like telling a different story. See also here: http://www.synergymx.com/post/2014/05/27/4x-ssd-speed-jump-not-so-fast/ IF (and when) the actual paper "NAND Flash Aware Data Management System for High-Speed SSDs by Garbage Collection Overhead Suppression." will be available, we might be able to see how much is reality and how much is hype. And IF (and WHEN) some SSD manufacturer will actually have it working, we will be able to see how it performs. jaclaz

Sure it is possible. That would be FAQ/FGA's here: http://technet.microsoft.com/en-us/library/ee406170(v=winembedded.0).aspx#Q4 jaclaz

Define "can" I mean : can I use a 5" switchblade instead of keys to open my car? (is it smart/suitable?) can I use a 5" switchblade instead of keys to open my car? (is it possible?) can I use a 5" switchblade instead of keys to open any car? (is it legal/allowed?)Some information: http://technet.microsoft.com/en-us/library/ee406170(v=winembedded.0).aspx http://msembedded.biz/en/windows-embedded-posready-2009/general-posready-2009.html http://msembedded.biz/en/windows-embedded-posready-2009/posready-2009-difference-to-xpe-pro.html http://download.microsoft.com/download/7/E/E/7EEEDFD3-DC86-4EBD-A491-94C210285249/WindowsEmbeddedLicensing-McAuliffe.pdf jaclaz

Strange. And I mean it. What actually means "did not work"? I mean is the test2.bat not executed or it is not executed as system or *something else*? I have not a way to reproduce/test this right now. Try just running RunAsSystem. And in the command prompt that results try running test2.bat. What happens if you try "compiling" ( please notice the double quotes) the second batch? Like (say) with this: http://www.f2ko.de/programs.php?lang=en&pid=b2e jaclaz

It is not clear (to me) what you are after. A USB stick (pendrive) is something completely different from a SD card. A USB stick has inside it a "bridge" between USB and the Flash memory, a controller. This controller is what has the (USB) PID and VID and the Name (like Sandisk Pen Drive). A USB stick is comparable to a SD card reader (which has the controller, and has the Vid/Pid and "Name") + a SD card inside it (which is more like a good ol'floppy, or a CD/DVD, only some "media"). What do you mean by "renaming the SD card" in Windows? Changing the Volume's Label? jaclaz

what. jaclaz

Sure , that is the reason why, since "they" provide so much confusing and contradicting information, "we" need to be VERY accurate. Remember that they can play the secret 7 anytime : http://homepage.ntlworld.com./jonathan.deboynepollard/Humour/microsoft-monopoly.html jaclaz

Well, no, he also did some changes to the install routines/interface and some good work with translations (besides updating a number of "extracting" programs) . But still, with no offence intended for anyone , I have had the impression that a number of updates were just for the "fun of it", and I personally do not like the approach taken for the installing with it's "closed" installer, etc., most proably Gora was/is concerned with the possibility of people "mangling" with it and releasing "malware" versions: http://buttontc.7zsfx.info/files/UExtract/FileList.txt jaclaz

@ SevenOptimus I am not at all suggesting you to fork anything , only to think about using a different name (and/or version numbers) to distinguish from the "other" unofficial versions submix8c mentioned and from the original. The "Gora" versions have continued the same versioning numbers from 1.6.1, but added a "G" at the end (in the versions posted by ricktendo, but NOT on the ones "direct" from Gora. <- anyway IMHO not a very easy to spot difference. You may want to call this one "UniExtract 1.6.5 SO <- but before or later someone will not understand how much the "G" or the "SO" appended is relevant for identifying a version and some confusion will be made. The full changelog of the Gora version is here: http://buttontc.7zsfx.info/files/UExtract/changelog.txt via Google Translate: https://translate.google.it/translate?sl=ru&tl=en&js=y&prev=_t&hl=it&ie=UTF-8&u=http%3A%2F%2Fbuttontc.7zsfx.info%2Ffiles%2FUExtract%2Fchangelog.txt&edit-text= And there are other forks/versions already, like the DreamLair one: http://72.233.112.78:9000/topic.cgi?forum=5&active=3&topic=20420&start=220 So, it is ALREADY a mess, I only suggested that it would be advisable to find some way (whatever it is) to reduce the possibility of confusion. jaclaz

Well, to be fair, the updates on the "gora" or "ricktendo" versions are seemingly mostly "marginal" or completely unlike *needed* , whilst the ones listed by SevenOptimus are seemingly much more interesting/useful . I mean, Trids definitions database updates are a good thing BUT they make no sense unless such updates BOTH: 1. reference executable (sfx) or archive files 2. the "identified through the update" new filetypes do actually "trigger" a new (or updated) extraction tool As an example, imagine that an update to Triddefs adds two filetypes, a spreadsheet format and a graphic one. What would be the difference between running Uniextract with the "old" definitions or with the "updated" ones? None, as both those kind of files are outside the usage paradigm of Uniextract. @submix8c The latest "official" version is 1.6.1, it is from 2010 and can be found on it's homepage: http://www.legroom.net/software/uniextract The one you referenced to is an older version from 2008, which I believe should now be left alone anyway. Maybe, to avoid confusion, SevenOptimus might want to rename his updated version of UNIExtract to (say) UNIExtractSE (for Second Edition) or UNIExtractNE (for New Edition) or something like that UniextractNU (New Unoffical) and/or start from version 2. jaclaz

WHICH example script? The commands in the procedures given about Push-Button reset use a folder alright. http://technet.microsoft.com/en-us/library/hh824917.aspx jaclaz

Why? The /s switch is an option. http://technet.microsoft.com/en-us/library/dd744347(v=ws.10).aspx http://msdn.microsoft.com/en-us/library/hh824874.aspx AND it is even tagged as "not to be used in typical deployment scenarios" If the switch is missing, the BCDBOOT will use the "default" volume, i.e. the Active partition (please read as System partition) in a BIOS system or the EFI System partition on UEFI. jaclaz

Have you tried running a batch file? I mean, Runassystem accepts only one parameter, the name of the process to start, anything else is simply ignored. jaclaz

Well, you are also probably pretty wrong, as the announcement was given on May 27: http://chrome.blogspot.ca/2014/05/protecting-chrome-users-from-malicious.html jaclaz

What I ALREADY suggested you, and that you completely failed to read or decided to ignore. Try re-reading, slowly this time the read-me-first (which you should have read first), particularly point #5: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ And this post: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-121#entry932258 Try also reading this one: http://www.msfn.org/board/topic/155484-seagate-barracuda-es2-hp-branding/#entry1003378 I doubt I can be more explicit without offending someone. WHAT is the difficult part in them? You were EXTREMELY LUCKY in succeeding to recover whatever you recovered from a defective disk. Now you test it with BOTH the Seagate Short and Long test. If it passes both, then the disk drive is as reliable as it was before the bricking (very little). <- it is of course entirely up to you to decide if you want to continue using it, keeping on it not backed up data, I have a word to define people which will take this decision, but I won't use it as I don't want to offend you . If it fails to pass even only one of the two tests, the disk is gone forever and it should actually be thrown away, or used as a doorholder (or similar). You ALREADY did a BIG mistake in not having those data backed up (before the disk bricked itself) data (if it has any value) should exist ALWAYS on at least two separate media. Like most people you never considered the possibility of a disk failing (this is normal, both that you were not aware of the risk and that a disk actually failed) but now that you know that this possibility exists and you actually already experienced it, you are going to insist on it? I mean: http://en.wiktionary.org/wiki/errare_humanum_est jaclaz

Well, no, no. Meaning: 1) that those articles are seemingly "generic" and NOT specific to "OEM System Builder Kit" or "Enterprise" 2) I can see nothing "wrong" in what is described in http://technet.microsoft.com/en-us/library/hh825089.aspx or in http://technet.microsoft.com/en-us/library/hh825041.aspx BUT if you have found something "wrong" in them, please tell us WHAT EXACTLY it is. jaclaz

http://forum.wordreference.com/showthread.php?t=1056284 jaclaz

Sure jaclaz

DO NOT EVEN THINK of updating the firmware, that is point #5 of the read-me-first: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ See also: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-121#entry932258 Try making a DISK image (from Linux and using ddrescue from it). You were ALREADY told what the suggested procedure was, the idea is to start a new thread to get help if you have problems following THAT suggested procedure, not to propose alternate (BTW wrong ) procedures. That disk clearly has a number of issues (of unknown nature) that most probably were the causes that made it a "brick". The fact that you unbricked it successfully has not "fixed" the other (previous and underlying) issues that caused the bricking. Your ONLY chance is to manage to image as many sectors as possible to a disk image residing on a new disk (or however a surely working one), and to do this you need to use tools (such as ddrescue) intended for this type of imaging from defective media. jaclaz

Well, the pins circled in that last image are strangely similar to those in the original post by johnmar http://www.msfn.org/board/topic/129551-unlocking-terminal-of-seagate-es2-in-bsyled000000cc-state/ BTW, re-checking the above, it seems that my memory is not as good as it used to be: the PCB needs to be CONNECTED AND the shortcircuit made, I am correcting my previous post. jaclaz

The $OEM$ folder is the "traditional" way to do this manually, like: http://www.ehow.com/how_7475136_slipstream-drivers-windows-xp.html the reason why very often nlite is (or the driverpacks or both): http://driverpacks.net/ are used is because the procedure is complex and prone to errors. But HFSLIP will also do nicely: http://www.msfn.org/board/topic/63302-integrating-drivers-with-hfslip/ though still some manual intervention/work is needed. jaclaz

You seem like forgetting a lot of passwords (besides forgetting to reply to threads you started ): http://www.msfn.org/board/topic/171838-big-problem-hdd-password-locked/ jaclaz