jaclaz

I thought I was clear enough initially: So, if you still insist in having a monolithic boot and system volume/partition, and you find 800 Gb "tight" (though the "scratch space" as well as the pagefile can be - JFYI - somewhere else), you can make a 1 Gb disk (be it a single device or a striped volume over two devices) MBR partitioned, and assemble the other devices the way you want and make them - say - a huge 3Tb GPT partitioned striped set. jaclaz

It's not about being good at electronics . If you are not good at electronics you should NOT use the CA-42 or DKU-5 cable EXACTLY for the reasons expressed in point #10 of the READ-ME-FIRST, but if you already have such a cable and you already cannibalized it on one side, you can as well cannibalize it on the other one and map the cable colours as in the provided link in FGA #6: http://buffalo.nas-central.org/wiki/Use_a_Nokia_Serial_Cable_on_an_ARM9_Linkstation Even if you don't have a multimeter, you can see the different colours soldered to which pin on the telephone side, a multimeter is something that you can buy anywhere for anything between 3 and 15 US$, but a very poor man continuity tester to check which wire goes to which pin (still on the phone side connector) is not really difficult to make out of scrap parts you surely have: http://www.seekic.com/circuit_diagram/Measuring_and_Test_Circuit/CONTINUITY_TESTER_FOR_LOW_RESISTANCE_CIRCUITS.html In any case, you posted the picture of the wrong side of the board, post one of the other side (where the cables are actually soldered), maybe there are the actual "names" of the connection. jaclaz

Sure , that is a "perfectly normal" setup in a multi-boot environment, but if you remove the need for the XP and the other Operating Systems, you remain with 64 Gb for Windows 7, let's double it for 8 and double again the result to get the space for all the programs on Earth that you don't have+ huge slack space and you still get around 500 Gb. I doubt that anyone could find that a "tight" space. I mean, once someone has entered the idea/approach that a single huge system and data volume is not possible (besides not being particularly handy in case of needing a CHKDSK or the like) it would make sense to have ONLY the OS + programs in the smallest (while still comfortably) sized volume and have more space for the data on another volume. Until everything is on the same volume as NoelC pointed out the available space is one "chunk", while when there are two volumes it becomes "two chunks", it is less inconvenient if the "chunks" are 0+3.5 Tb instead of (say) 0.5+3 Tb. I am still missing how exactly NoelC plans to access anything beyond the LBA corresponding to 2.2 Tb on a MBR scheme, however. Maybe Windows 8 (and those SSD's and his RAID card(s)) can somehow work in "native" 4K sectors , but if this is the case then there is no need to make two volumes, and I am not at all familiar with a RAID 0 stripe across 8 devices (actually any stripe with more than two devices), so I may well be waaaay off target. jaclaz

WHO are the "we"? I beg to differ. How big is an OS these days? Pure OS install? 30 Gb? How much are all the stupid updates all together? 20 Gb? How much space do all the programs on Earth + their settings BUT NOT data actually need? 100 Gb? 200 Gb? What else (besides OS+updates+programs+their settings) is actually needed on the "system" (what MS calls "boot") volume? another 100 Gb? 30+20+200+100=350 Gb, add another 150 Gb of "slack space" and you get at the very most 500 Gb. Hint: smaller volumes are faster to dd (if you are going to use dd or similar forensic sound image) And a reminder (just in case), volumes can be mounted to folders inside another (NTFS) volume alright .... jaclaz

Maybe you are making it a bigger issue than it really is. If you can afford 8x512 SSD's you can probably afford another tiny "boot only" device. BUT your alternative is actually much better than the original idea of having a huge single boot and system volume, IMHO. jaclaz

Yep. You can "conventionally" think at DVI as "replacement for VGA" and at HDMI "replacement for DVI with a particular accent for multimedia" (less clutter because a same cable carries both video and audio). jaclaz

That is what they (the cable sellers) want you to believe but no, it's just the same: http://www.cnet.com/news/hdmi-vs-displayport-vs-dvi-vs-vga-which-connection-to-choose/ http://www.cnet.com/news/why-all-hdmi-cables-are-the-same/ The debate (if any) is whether on the relatively "low", "common" resolutions, and provided that good equipment is involved, there is an actual difference between VGA and any of the digital formats: http://www.msfn.org/board/topic/162901-computer-connections/ (and no , there is nothing that you will be able to notice on a working setup). jaclaz

First thing thanks for your thingies. Of course *anyone* would be interested to a redistributable version of devcon , if you could publish it as a standalone it would be nice. About srvany, though you already nicely solved the issue , I can recommend using instead of it the NSSM: https://nssm.cc/ but having an alternative is always a good thing. jaclaz

Well, seemingly giganews is hiring: http://www.giganews.com/careers/ http://www.giganews.com/careers/open-jobs.html so it must be not that bad. jaclaz

I don' t know. I mean, I do like some of the features of ReFS, but it's not like any of them (BTW nice) are really-really *needed* or *make a difference* in practice when compared with NTFS (the exception would be of course data centers and similar where they most probably use Zfs or the like, not the PC). exFAT (which the good MS guys managed to bastardize releasing - without documenting it - a few slightly different versions, including TexFAT) makes no sense at all, if not - maybe - on dedicated hardware (like the phones, and the like). In practice the filesystem that never was (though it is available in newer systems) given a chance is UDF (that besides the pompous and extremely inaccurate name, since noone uses it if not on optical discs) which would be otherwise particularly suitable for storage or for USB sticks and the like. jaclaz

Look on the OTHER side of the DKU cable. that would be FGA (Frequently Given Answer) #6 : http://www.msfn.org/board/topic/147532-fga-for-the-seagate-720011-drives/ AND have a look at the READ-ME-FIRST point #10: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ jaclaz

And, conversely, now that CHS is not used anymore in actual OS operations, it would be trivial to invent a "new standard" where the CHS area of the MBR partition entry is used to hold the further "high bytes" of the LBA addresses, giving it a new "generic" protective partition ID, by stealing one of the ID's that are unused and that were (senselessly) claimed or "reserved" by Operating Systems that never were or that are totally irrelevant/abandoned: http://www.win.tue.nl/~aeb/partitions/partition_types-1.html so that the only limit/requirement for booting with an UNmodified BIOS would be that the Active partition has "conventional LBA addressing" and resides within the first 2.2 Tb of the disk, making m00t of the supposed *need* for GPT disks. For the record the *only* "advantage" GPT disks have in "real world" is (besides the larger addressing extents) that you can have countless (like 128 or more) primary partitions (not really a "limit", since most people seemingly use single extremely large volumes and rarely needs more than 4, and even when they do, logical volumes work fine since what 20 or more years) and the freedom from the 256 partition ID's limit, which, given that the available number is now so mindboggingly huge makes it improbable that there will be a collision (see point #7 here): http://reboot.pro/topic/19516-hack-bootmgr-to-boot-windows-in-bios-to-gpt/?p=186493 And - still for the record - more wasted bytes: http://reboot.pro/topic/19516-hack-bootmgr-to-boot-windows-in-bios-to-gpt/?p=186341 jaclaz

But this has nothing to do with the actual filesystem, the "normal" NTFS can do nicely much more than any "practical" size : http://en.wikipedia.org/wiki/NTFS#Scalability The good MS guys introduced artificially (as they often do) an incompatibility between BIOS based hardware and GPT disks, or better didn't bother to update the real mode part of the BOOTMGR, most probably in order to push the EFI/UEFI platform, there is no real reason why the non-EFI bootmgr cannot access/understand/parse/use GPT volumes. jaclaz

BUT it does NOT say ANYTHING about multiple values in "netcards =" (as a matter of fact it doesn't even mention "netcards"). However, here there is another example of having a PNP id: http://download.modem-help.co.uk/mfcs-J/JAHT/driver/jn110rw-driver.zip.php?showFile=JN-110RW%2FBOOTROM%2FSUBOOT%2FPROTOCOL.INI And an even more interesting thing: http://ftp.lakesoft.net/ftp/drivers/nic/davicom%20lan/davicom9102/bootrom/ntsrv/win95/protocol.ini a direct reference to PCI VEN and DEV Which makes me think that my previous guess was completely wrong , and the value is a sort of "binding" between the driver instance and corresponding piece of hardware, that at this point can seemingly be referred to by Hardware ID, PNP ID or some sort of "friendly name" as the "ATHEROSL2" Sfor has, Unrelated, but interesting: ftp://ftp.microsoft.com/MISC1/BUSSYS/WINNT/KB/Q185/9/16.TXT jaclaz

As a matter of fact the (smart? ) main point of that experimental approach is that the "hidden" partition (i.e. if it is not "indexed" in the GPT partitition table) is pretty much "hidden" and "safe" in "normal operation". It is placed on sectors 63-2047: the MBR is on LBA 0the EFI PART header is on LBA 1the GPT partition table will be starting on sector 2 and extend up to sector 33 for 128 available partition entries - unless you create a zillion partitions/volumes in it, it will *never* reach sector 63the Disk Manager and/or diskpart in the default settings will do nothing to any sector before 2048 on a largish diskthe adding or removing of volumes will affect the GPT partition table but not the MBR, leaving untouched the protective entry and the code (that should not be there)changes (if any) in Disk Signature will obviously not affect anything "on disk" though depending on the actual contents of the \boot\BCD in the "hidden" partition this may need to be adaptedSo, in practice only if you manage to delete the Magic Bytes 55AA from the MBR (thus creating the need to re-initialize the disk) you will have to "re-start from scratch", but if you re-initialize the disk you need to start from scratch anyway. If it's a hardware controller, it's operation is AFAIK "completely transparent" to BIOS (and of course as well to MBR code and grub4dos), so it should not change anything. jaclaz

Well, not really-really. The limit in size is still there of course, but it is perfectly possible with a few tricks to boot a GPT disk from BIOS, and what happens later depends on the size of disk sector and on the actual OS. A MBR partition entry still has a field for size that is a double word so anything more than FFFFFFFF or 4294967295 can't be wrtten to it, so that anything above 4294967295*512=2199023255040 will still become a suffusion of yellow. So, you need anyway a small "system" (MS terminology reversed, "wrong") or "boot" (logical terminology, "right") volume, and then the OS needs to be able to use GPT disks natively. This is normally achieved using a hybrid MBR/GPT disk, which has a number of issues: http://www.rodsbooks.com/gdisk/hybrid.html The above site http://www.rodsbooks.com/gdisk/is currently the most complete (and seemingly only) source of information on GPT disks in the "Windows world". However: http://reboot.pro/topic/19516-hack-bootmgr-to-boot-windows-in-bios-to-gpt/ http://reboot.pro/topic/20002-map-mbr-style-disk-on-gpt-partition/ It is possible to Boot from BIOS on a non-hybrid GPT disk . Final (at the moment) solution here: http://reboot.pro/topic/19516-hack-bootmgr-to-boot-windows-in-bios-to-gpt/?p=186656 jaclaz

They won't end anyway , the marketing guys have them taught since they are little children, it is a sort of "imprinting": http://en.wikipedia.org/wiki/Imprinting_(psychology) What really surprises me in that e-mail snippet is how the failed to say how they were "proud and excited to announce" this new driver. Sure , but still no gaming (which is the field where increases in reliability and speed should be measured, usually by a teenager researcher using Twitter to publish the resulting whitepapers). This is more like it (nice marketing lingo), it must not be casual that the Author is Head of Software Marketing for AMD: http://community.amd.com/community/amd-blogs/amd-gaming/blog/2014/12/08/a-very-special-edition-driver-amd-catalyst-omega Unless I am mistaken, this means more or less that these drivers were custom made for the specific hardware, and that the specific hardware works better with some other hardware by the same manufacturer and with these appropriate drivers, in gameplay. I would have been surprised of the contrary.... But they are good guys, they tested this more, much more than before (which logically means that they over-tested these or that for years they provided not tested enough drivers): And they are your Christmas Gift: jaclaz

Did you actually mean "But seriously you don't need a win10, do you?" jaclaz

Most probably you should find a suitable head arm set from a donor drive, replace/transplant it, re-program if needed the adaptive data of the heads and inject a custom SA in the disk firmware so that it skips the disk-resident indexing area, get the full raw data, de-ECC them, reassemble them as sequentially as you can then carve the results. (this is if you want to try getting data back) If you want to fix the disk drive instead you just change the platters and the head arm set, then re-calibrate the whole thing performing a factory format. jaclaz

I don't get it. You seem to use that card and driver for something called "work". The declared improvements are related to another thing, much better than "work", called "games" (LOL): Benchmarks measure - more or less objectively - speed, what was promised is "faster gameplay" and "faster gaming performance", and you completely failed to measure the "enhanced energy efficiency" , and of course it is too early to verify the "enhanced reliability". And, hey, man, it's free (LOL). jaclaz

How do you know? I spray my ceilings with high resistance glue once a week . jaclaz

You mean convert them ? Like: http://oooconv.free.fr/batchconv/batchconv_en.html http://dag.wiee.rs/home-made/unoconv/ jaclaz

Yes, he knows. (and his name - difficult as it may seem - is Kelsenellenelvian) You see , people that do have a proper "clean room" (which is what you see on the ads and that actually is a "laminar flow hood") do not post these questions or do not post them here on MSFN.ORG. Good , and the answer is 42.00% (give or take a measuring error of +/- 0.2%) jaclaz

Well, what about Colinux and/or andlinux? http://www.colinux.org/ http://andlinux.org/ jaclaz

I have no idea on what can still be done in a DIY environment. That "Error 1008" has been *somehow* reported as being a head issue, but as always happen with this kind of matters, noone really knows what he is talking about and those that actually know stay silent or post deceiving info, just for making some fun of the non-pros. You can try if Sediv now supports that model , otherwise the only resource I can think of is that you can try asking here: http://malthus.mooo.com/index.php? the place is where the good guys (maybe not really pros, but friendly enough) use to gather. jaclaz