jaclaz

I thought that .net shouldn't even be. Yes, last character in the above is a dot, or full stop or period. jaclaz

No, actually we do , issue is with the reliability of those thingies. @vipejc READ this: AND links in it. jaclaz

Carpenter's comparison : The car engine model or serial would not be a problem as I always have 1 hammer in the toolbox . The only time when an engine gets replaced with a new one is when it starts making an odd noise. I really need to study this subject, but feel - having not yet studied/understood ANYTHING about engine replacement or mechanics in general and what is involved in them, that I can hammer the new one into place allright. Really, you should READ the given thread: and if you have doubts on what is written there, ask about those doubts (as opposed to insist in making guesses - BTW wild ones - assuming - BTW wrongly - or downright do things that you may later regret). More or less the idea of coming to a forum and ask a question, is to get answers to the question and learn (by listening to advice and doing your own experiments, as you should not trust anyone, EVER) how to do things from people that should know more than you do on the specific matter. Please consider how this does not in any way limit your freedom to do or not do anything (right or wrong) that crosses your mind, but you could show at least a very minimal form of respect for the time people spends in trying to explain to you the matter by actually reading and try to understand the suggestions given to you. jaclaz

NO, you cannot. You can restore the contents (files/directories) to a NEW (smaller) partition, using robocopy, which AGAIN is short for robust FILE copy. It copies files, and NOT filesystem/partitions/volumes. Namely you will lose: Volume Serial (you are not restoring a partition, you are restoring the contents of the old partition to a new one) PBR/bootsector code (unless the original has the "standard" code of the OS you are creating the NEW (smaller) partition Any contents of the "reserved sectors" more likely than not creation date/times of folders (it depends on version of robocopy and of course on the switches used) Of course if it is just a data partition this may have no consequences whatsoever. You are doing FILE BASED save and restore, NOT partition/volume/filesystem based save and restore (they are NOT the same thing). jaclaz

Probably not what Mr. Ballmer expected from Consumer Report: http://news.consumerreports.org/electronics/2012/12/why-you-might-want-to-stick-with-windows-7-for-now.html For NO apparent reason: jaclaz

Probabilities is a tricky field. If you assign a very high percentage to the probability of a CD drive to NOT work, when you try first one you have 50% possibilities. So if first one fails, when you try the second, you are doing that because you fell in the 50% of the first one failing. Then when you try the third, you are doing that because you fell in the 50% of the second failing, thus in the 50% of the intial 50%. i.e. 25% Then when you try the fourth, you are doing that because you fell in the 50% of the third failing thus 50% of the 25%, i.e. 12.5%. With a fifth you are at 6.25% With a sixth at 3.125%. With a seventh at 1.5625%. With an eigth at 0.78125%. Hence you need to try 8 CD drives to have probabilities less than 1%, assuming that there is a 50% probability that a CD drive got for a few bucks on e-bay or similar actually works. BUT, if you assume that the probability of a CD drive not working is lower than that (i.e. you trust in the good faith and honesty of the sellers, let's say that they are 80% like that) like 20%, you have: second 20% of 20%= 4% third 20% of 4% = 0.8% fourth 20%of 0.8%= 0.16% jaclaz

For NO apparent reason : jaclaz

Mind you not necessarily the case at hand, but I translate "before" as: "when the card was new and there was no dust of any kind on it, all contacts were clean and cold solderings (if any) had not enough time to oxidize" jaclaz

You don't need to "see" it, you have to either believe it or not. Rest assured that dust/dirt is one of the major causes for malfunctioning of any electronic card, expecially high frequency ones (no not particularly audio frequency, usually much higher ones such as TV signals), but contacts are affected in any case.. First google result for "dust electronic failure": http://www.computerdust.com/downloads/special_report_on_the_effect_of_dust_on_electronics.pdf a few results below: http://www.ipcoutlook.org/pdf/impact_of_dust_ipc.pdf No, that's up to jumper. jaclaz

IF 80 wires cables are used, which additionally are colour coded: http://www.pcguide.com/ref/hdd/if/ide/confCable80-c.html Older 40 wires cable did not have this limitations: http://www.pcguide.com/ref/hdd/if/ide/conf_Cable.htm unless you were using a Cable Select setting (strongly discouraged by me): http://www.pcguide.com/ref/hdd/if/ide/conf_CS.htm In case of cable select, often the Slave/Master are INVERTED when compared to the 80 Wire cables. jaclaz

Sometimes "washing a card" means simply "washing a card". Unlike most people thinks, electronic cards can be washed (of course using some common sense). See: http://www.forensicfocus.com/Forums/viewtopic/t=10038/ In your case actually washing it may be overkill, but taking it out of the case, carefully and thoroughly cleaning it from dust with compressed air, then use some isopropyl alcohol to clean contacts could be advised. There are mainly two kinds of dust, one that is dry (which goes away easily with compressed air or with a soft brush) and one that is "oily" and that doesn't go away with compressed air. When this latter kind is on a card, the easiest way is to wash the card with some mildly hot water and some soap. (and of course thoroughly rinse and let it dry afterwards) jaclaz

The image in the signature of Ultimatesilence is a seemingly plain .jpg hosted there: hxxp://yyyy.freeimagehosting.net/newuploads/7preh.gif If that is the culprit, each and every page where there is a post by that member should give you that same warning. jaclaz

But have you SHOUTED at them hard enough? jaclaz

Sure it won't . jaclaz

Sure, it was additionally before the iPad RELEASE: http://en.wikipedia.org/wiki/IPad but I doubt that the good Apple guys managed to get the idea on the 22 January 2010 and released a finished product (including BOTH hardware and software) in the millions in two an and a half months . Specifically the iPad has been one of the most talked about before release products in the history of electronic devices: http://billpetro.com/history-of-the-iPad This is from September 2009: http://www.ilounge.com/index.php/backstage/comments/ten-new-details-on-the-apple-tablet/ three months later at MS they tested a Windows NT OS on a touch screen device, I mean WOW, original idea, they forecasted that their competitors already had ready for the market a kick a** device and did some tests about possibly doing the same? (and then it took them almost two years to actually release a product) Prototypes and tests should be compared to prototypes and to tests, as well released products should be compared to released products. jaclaz

You do understand how: bound to a given HAL/driver set only (moved or plain sysprepped XP) offline syprepped XP Win7 Win8 Universal lie on a logarithmic scale, don't you? http://en.wikipedia.org/wiki/Logarithmic_scale jaclaz

Just for the record the "historical" forum/reference for Offline Sysprep is here: http://www.911cd.net/forums//index.php?showforum=43 @Atari800XL If you check this: http://www.911cd.net/forums//index.php?showtopic=22064 you should have a clear idea of what are the "missing pieces" of the puzzle in an ordinary sysprep and which ones Offline Sysprep provides. jaclaz

Well, noone talked of a battery, we were talking after having expressly said "(simplified, and in order to let you understand)" of a PC power supply connected to mains and about a brushless DC motor, which is both a resistive load and an inductive one (actually essentially the second), and unlike the "will burn", "very likely to burn" was used instead for example #4. Ohm's Law was cited AFTER the 4 examples and as an additional point, to exemplify how powering (within a bearable range) a device (still talking of an electric DC motor) connected to a PC power supply) with higher voltage will reduce the amount of current needed and how current absorption is linked to the voltage level supplied. In the case of an electric radiator suited for 220 V , actually norms are about 230 V with some slightly different tolerances: http://en.wikipedia.org/wiki/Mains_electricity#Standardization labeled 1000 W, we can use: W = V x I to get I=1000/230=~4.35 A and then use I = V / R to get that the resistance of the thingy is about 53 Ohms as 230/53=~4.34 But now, when we use the AA battery 1.5 V we have: I=1.5/4.34 =~0.35 A or 350 mA Since a normal AA battery (alkaline) has a capacity of roughly 2200 mAh, and without taking into consideration a number of factors, it will last 2200/350=~ 6h30 which, while NOT being accurate, it is still more accurate than "a few hours". jaclaz

Right. So, in the future, i.e. WHEN (after it will be profoundly modified in such ways that) it will actually work, we will use the NCI (hoping that in the meantime the geniuses will come out at least with a name for it ). NOW, it's the present, and we are going to use what we see fit NOW (the desktop). jaclaz

@vipejc 1. What are called "storage" are actually not drivers for the "storage devices" (which are "standard" and already included in any PE or Windows System), but drivers for the "storage controllers", i.e. what you may miss if you don't add it to the build could be the SATA/AHCI controller driver, the controller to which BOTH SATA hard disks and SATA CD/DVD drives are connected to. 2. I guess you might find some interest in reading this thread: it seems like you have not (yet ) very clear the difference between cloning, imaging and backup/restore. (don't worry it is seemingly very common because even the terminology used is often "vague" or "mixed"). Macrium Reflect is essentially an imaging solution (disk or volume/filesystem oriented). Robocopy is a robust file copy (file based). jaclaz

Naah, the real problem are the added costs of deciding NOT to standardize on a single modern browser or to support or allow the use of nonstandard browsers in the enterprise. and following few posts up to here: jaclaz

Because last time I checked in the MBR the Start LBA (sectors before the partition) and Num LBA (number of sectors in a partition entry) were made of 4 bytes. so, if you have first partition starting (say) at offset 2048 (0x00000800) and you set the number of sectors in it to 4294967295 (0xFFFFFFFF) you have already used all the addressable space. (still talking of 512 bytes/sector disks). And of course these guys here are liars according to your experience : http://knowledge.seagate.com/articles/en_US/FAQ/218619en http://www.uefi.org/learning_center/UEFI_MBR_Limits_v2.pdf http://www.hgst.com/tech/techlib.nsf/techdocs/D213A024C090CE9F862577D5002600FC/$file/FinalHiCap_2.2TB_TechBrief.pdf jaclaz

Sure , that depends on how much you fill the 16 Gb you are given of local storage. As everyone knows, 1's weight a little bit more than 0's (because the 0's are full of air). jaclaz

OP stopped replying becayse he went almost THREE MONTHS ago to a six month English course, expect a reply in around THREE MORE MONTHS...... jaclaz

The whole point that you (and now you are in good company with dencorso ) seemingly missed is that THERE IS NO NEED WHATEVER to completely wipe a disk if not in one single case, which is when you are going to give the disk away, and you fear for the data that may have remained on it. What it may be needed at the most when there is a "tricky" issue connected to detection of a disk or (and this is not the case) booting issues may be to wipe: 2 (two) bytes OR 512 (fivehundredandtwelve) bytes OR some initial sectors, at the very most 2048 of them Can you access more than 2.2 Tb on a MBR disk? jaclaz