jaclaz

http://www.technologyreview.com/news/508311/the-woman-charged-with-making-windows-8-succeed/ Missing end of the sentence/interview: Too bad that the space on that page wasn't enough to contain these last statements... jaclaz

You can try the Toshiba ones: http://web1.toshiba.ca/support/isg/drivers/archives/files_Archive/Index/display_drivers.htm jaclaz

Where exactly did you get the data for the fan? Unless I am mistaken, the specs are here: http://www.delta.com.tw/product/cp/dcfans/dcfans_product.asp?pcid=1&ptid=1 http://www.delta.com.tw/product/cp/dcfans/download/pdf/AFB/AFB120x120x38mm.pdf or here (more likely): http://www.delta-america.com/Products/FANUploads/Specification/AFB1212HHE.pdf jaclaz

Do we have ANY valid members who identify their OS as Vista Business x86 AND are not lying at it? jaclaz

Never said that you were telling me lies, but maybe the actual specs may contain additional info that I would like to see and that you omitted as you rated them "unnecessary". What about the EXACT Delta fan model and motherboard make/model? You know. like : jaclaz

Who knows? It depends from which issue is your disk suffering from, actually WHAT caused the issue. NO guaranteee of any kind. Take some time reading ATTENTIVELY the read-me-first: Normally yes, the data is back "as it was before", BUT sometimes partition or file based recovery is necessary (and sometimes even these fail) In any case you DO NOT attempt booting from that disk, you try first thing (if the BSY or LBA0 issue is resolved) imaging it on another disk surely working and attempt recovering the data. jaclaz

Good , and the reason why I asked for them is because those data you provided are NOT enough for me to give you an accurate suggestion, and they sound "queer" to me. If you prefer I would like to read myself the specs, or if you prefer even better I don't trust you on the info you posted . . Mind you I am (was) trying to help you, it is only logical that if you cannot judge by yourself if that fan is suitable , you evidently miss some related electric/electronic knowledge , EXACTLY the same one that would allow you to decide what is necessary and what it is not. And, as a standard, preventive disclaimer : jaclaz

Just for the record, I am not a sound engineer nor a certified electronics technician. (but I did stay at a Holiday Inn ) jaclaz

Generally speaking PE 2.x and 3.x (and most probably 4.x) tend to have some issues with enumerating drives (when compared to BIOS enumeration). Since you booted from the USB stick, that stick became "first disk" in BIOS, whilst when you used the CD/DVD the internal disk remained "first disk" in BIOS, it is very possible that this somehow altered the order of the other disks too. See also: http://social.technet.microsoft.com/Forums/uk/configmgrosd/thread/d703ce21-dc70-40e0-a347-e9bfc5b845a5 jaclaz

@MagicAndre1981 Do check the mentioned Courier links. http://www.youtube.com/watch?v=6WYWGKnVkEw http://news.cnet.com/8301-10805_3-20128013-75/the-inside-story-of-how-microsoft-killed-its-courier-tablet/ As I see it (and as said before) a pen interface makes much more sense than a "touch" one by itself, and still IMHO the "book-like" two sided thingy looks a lot more usable, besides being a "common gesture" to open a book. At least it would have been "new". jaclaz

(8.96-8.88)/8.88=0.009 or less than 1%, well within common tolerances. No issues whatever with voltage, if the motherboard provides 12 V (usually and more likely 12.2 or 12.3 V) this value will never be increased. The 12.8 is the max rated voltage of the fan, if it has a max rated consumption of 0.70 A it will consume at the most 0.70 A (+ or - some tolerance, typically 2.5 or 5%) Voltage levels and current absorption are not linear when it comes to electrical motors. Loosely, you can: Think at Volts as you would think at the inner area of a water pipe. Think at Ampere as you would think at the pressure of the water flowing through it. Think at Watts as the quantity (instantly or per unit of time) of water coming out of the open end of the pipe. To get more water you increase the pressure (the diameter of the pipe remains the same), as well if instead of flowing free from an open end of the pipe you make it deliver water in a container that is in depression, more water will flow (actually the delta of pressure is increased as well) An electrical motor will normally attempt when under heavy stress/load (and this is not the case of a fan unless you "brake" it or it gets clogged with dust or whatever) to compensate a lower level of voltage by absorbing more Amperes. As well, there could be issues with the (very brief in time) increase of Amperes needed to spin up, but any hardware manufacturer would take this into account when rating the current a header designed to have an electric motor connected to it can provide. I see that you were not satisfied by the replies received here : http://www.overclock.net/t/1337574/fan-amps-and-watts where at least you provided the make of the fan, Delta. Now if you would be so kind as to provide the EXACT model of the Delta fan AND the EXACT make/model of your motherboard, one could have a look at the spec sheets of both and possibly give you some more detailed advise. jaclaz

It didn't seem right to me, but its easy enough to do a test. Now I do recall that WinPE 2.x diskpart operated a little differently, so perhaps it is knowledge leftover and not corrected. However, at least in WinPE 3 and 4 (x64) it is easy enough to test. I can confirm that if you use the CLEAN command on a GPT disk, it does indeed revert the disk back to MBR format, or at least it ceases to be GPT. Consider this result: Sure , this is "logical" but, I am afraid, "general/generic" . What I suspect is that the specific hardware the OP has *somehow* implements some non-standard features that (still *somehow*) "connect" the BIOS with the disk device and it's partitioning, at least this is what I can understand from the given links. And still I have not seen any mention in the OP posts about having attempted the conversion using either Disk Manager or diskpart.from GPT to MBR. In any case following to the letter that tutorial, that seemingly has worked for several users, cannot in any way make things "worse" than they are now. jaclaz

No more simply "check if there is no full moon when sending spinning asterisks" or "only do that during daytime": jaclaz

And be aware of the risk of unclogging cables sending asterisks through them! jaclaz

Well, as I see it, it is more or less the same trend that led to the idea of replacing a simple, plain text file like BOOT.INI with a Registry Hive (\boot\BCD) additionally "always in use" by the system, they all seem like having been not in class when they were teaching about Occam's Razor or the KISS principle. The combined effect of unneededly complex implementation with scarce or no proper documentation will eventually lead to the extinction of the human race, through building systems so complex that no one will be able to manage them properly.... .... the machines will get self aware soon jaclaz

I was passing by and a few random links fell off my bag-o-links http://www.hardwaresecrets.com/article/410 http://docs.oracle.com/cd/B19306_01/server.102/b28051/tdppt_degrade.htm http://uk.answers.yahoo.com/question/index?qid=20070728035026AAabNLU jaclaz

Look, basically you were asking for suggestions, they were given to you, and they are (IMHO) good ones, you can choose to either follow them or to not follow them , in the first case, just do what you were told, avoiding the unneeded nitpicking, if the second, you can as well avoid the nitpicking as it would be pointless. Just for the record however, you are fundamentally wrong: different drivers #5 on same OS #3 may well give different resuts, as well different (compatible between them) OS's #3 with same drivers #5 may give different results. as well the motherboard #2 may - for *any* reason - provoke a malfunctioning of the sound card #6 (as an example by providing low voltage or current or "dirty" power, among other things) jaclaz

While you are booted in the PE, can yousee that file on the C:\ drive if you execute a DIR command? (Open a command prompt, type in it dir C:\ and press [ENTER]) Boot to the "full system" and try again the above command. Do you see dfferences in the listed files? Which EXACT command(s) are included in your startnet.cmd? And in Winpeshl.ini? (post a copy of them) AND check this thread: jaclaz

Hmmm, I think I will try again. The "chain" is: Audio Source -> Hardware (PC) -> Software (Os) -> Software (player) -> Software (driver) -> hardware (Sound card) -> hardware (loudspeakers/earphones/etc) -> Perception (subjective, your ear) The appropriate and suggested procedure is to try item #6 while keeping the same items #1, #2, #7 and #8 with different items #3, #4, #5. Then trying another item #6 (and if needed an appropriate corresponding item #5) while keeping untouched items from #1 to #4 and from #6 to #8. This is enough to understand if the sound card has an issue (hardware) or *something else* is the problem. You either conduct these two tests or you will be - besides sad - a doubtful, insecure bunny for a long time . jaclaz

Still on the OT tablet topic: http://mvardon.com/2010/01/22/lost-17-years-apples-tablet-specs/ http://www.pratikpramanik.com/2012/06/industry-contrarian-microsoft-surface-and-why-the-industry-still-hasnt-figured-out-tablets/ And a nice image from the above: The article above includes a couple interesting links to the almost forgotten (and canceled) Courier project..... And (yet another) article about the Surface being what?: http://www.zdnet.com/surface-rt-hands-on-not-a-good-tablet-not-a-good-laptop-7000007830/ jaclaz

From what you reported it seems to me like he actually replied, saying he doesn't know. I guess everyone is allowed to not know something.... I presume that the issue with Win 3.1 is only that of finding viable drivers for the specific screen/pen, compare with: http://www.vintage-computer.com/vcforum/showthread.php?26914-Windows-for-Pen-for-Compaq-Concerto jaclaz

NOT what you asked for, but in batch: http://reboot.pro/topic/5881-ipconfig/ the code is "botched" you may want to use this: http://pastehtml.com/view/b4t99xk89.html Basically it amounts to: @ECHO OFF for /f "tokens=2 delims=:" %%A in ('IPCONFIG^|FIND "IP"') do echo %%A jaclaz

Well, with all due respect you asked about cheap ways to measure every kind of signals. I had the impression that you knew what to do with these measurements, otherwise it would be pointless. I mean, let's say hypothetically that Santa Claus makes you find a brand new spectro-foto-turbo-cyber-oscillo-mega-scope, a (fictional) instrument very suited to measure accurately any kind of signals and worth a few thousands bucks, what you would do with it (exception made for using it as a very expensive door holder )? You expressed the wish to have cheap measurement devices for signals, not for learning overnight (and by sheer magic) a few month's worth of electronic design, troubleshooting and engineering (and some more months of practice besides the theory). Short of using (appropriately) a signal measurement device you have only two options, that should however be BOTH tried: try that same sound card on that same PC system with another OS (install or "LiveCD") try that same sound card on another PC system (and with another OS install and/or "LiveCD") if it still malfunctions, then there is definitely a hardware issue of some kind. But let's say (still hypothetically) that there is an actual issue on that sound card hardware and that by pure chance my crystal ball is tuned and I could tell you that you have to replace the chip marked as IC18 on the board, what would you do? Have you the experience/capability/tools to desolder a SMC, find a replacement and re-solder it properly? Again with all due respect, you seem to me more like Robert De NIro in Analyze This , I guess your next move will to shoot a pillow.... jaclaz

The linked to tutorial seems to me like implying that this is not the case, that's why I thought to bring up the issue. That tutorial in a nutshell says that if the "existing" disk/partition/filesystem is not "converted to MBR" when it is validly "formatted" (please take all the terms used in this sentence as "vague" and not exact) the only way is to intitiate an ATA Safe Erase: which points to this other tutorial: http://www.overclock.net/t/1227597/how-to-secure-erase-your-solid-state-drive-ssd-with-parted-magic though essentially the same can be made with hdparm: https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase surely from Linux, but most probably from a PE too, see: http://reboot.pro/topic/13601-software-to-wipe-a-systemdrive-from-windows/ and possibly also from DOS using the (but DOS may have issues recognizing the disk drive/device): http://cmrr.ucsd.edu/people/Hughes/SecureErase.shtml jaclaz

Yes, this is the "strange" part. Normally a "working" hard disk (not in BSY state) does connect when "fully assembled". The disconnecting of either the head or the motor (of both as in the original tutorial) is only a way (or rather a "trick") to exit the "loop" that is causing the BSY state. jaclaz