jaclaz

Well,you are mixing more things in the same bag. Let's go back to our 16 sectors device, and simplify the setup with a single partition/filesystem. You see the mapping as: 0123456789AB(CDEF) and let us assume that that (by pure chance) does correspond to the real device mapping, i.e.: 0123456789AB=0123456789AB You write to the device 4 files, each a sector in length, which is symbolized as xywz: 0123456789AB 0123456789AB xywz---------- The particular file z is often (re-)written, so after a number of rewrite attempts the wear leveling algorithm kicks in and makes the thing: 0123456789AB 012B3456789A xywz---------- After a huge number of rewrites and after a number of wear leveling sector exchanges, let's say the next is: 0123456789AB 012AB3456789 xywz---------- one sector (A) goes bad, and is thus removed from the available pool, replaced by C (which is in the overprovisioning area): 0123456789AB 012CB3456789 xywz---------- For all you know (and for what the OS knows), all this time, xywz occupied sectors 0123, while in reality xyw always stayed on the initial sectors 012 BUT z has gone through all the other sectors (exception made for 012) and when a sector eventually died, an overprovisioning area sectors was put in use. You have to think about two (complex) systems (one is the OS, and the filesystems, and the partitioning, etc. and the other is the device processor and its internal OS) that only talk between themselves through a (standard) protocol that simply does not allow the exchange of detailed information. When the OS asks for the location of file z, the device replies "Not your business, the file is wherever I see fit, all you need to know is that you can access it by querying for fourth sector, whether what I provide you when you ask for fourth sector is actually the fourth sector of the device or an arbitrary one that I temporary address a "fourth sector" is irrelevant". As well when the OS asks for a (contiguous) extent on the device (let's say to create in it a partition), the device simply provides a sequence of contiguous addresses (that are internally translated to either contiguous or not contiguous areas). There is also a difference on the philosophy of the two tasks (wear leveling vs. over provisioning) the wear level algorithms attempt to have at all times all cells/sectors be written (roughly) the same number of times, the overprovisioning only comes into play when an emergence (a cell or sector has gone bad) providing a replacement. Now imagine a hotel with 16 rooms, with on average 10 of them booked. The hotel manager will attempt to assign the rooms to customers in such a way that all rooms are used the same number of times in a year, that is wear leveling. But the (smart) hotel manager will always rent no more than 15 rooms, keeping one free until - say 11:30 PM (i.e. until after most if not all booked guests checked in) - for emergencies (an appliance breaks, a last-last minute customer, etc.), that is overprovisioning. When you book the room, you don't actually know which room number you will get, all you know is that you have a room (with given characteristics) booked, and even when you check in, until you are given the room key you don't know which room number the hotel manager will give you, and - even once you are given the key to the room you don't really know for sure if that particular room yesterday had the same room number it would be possible that the (mad) hotel manager every day re-numbers his rooms and re-tags the keys ... jaclaz

*Need* for play? I mean, usually gamers have the latest, newest of everything including both hardware and software (and OS), whilst to play (say) Hearts, a small lag is not that much relevant. jaclaz

There is another related thread, here: about using a proxy. jaclaz

@1024x768 To clarify (if needed) VirusTotal is an "aggregator" of antivirus engines, it lists a large number of them, some really of doubtful quality and/or of very limited diffusion. Each and every antivirus will use its own "method" to determine if a file is a risk or not, and it very often happens that one or two of the "minor" ones (but sometimes it happen also for "mainsteream ones such as - say - NOD32, Avast, Avira, Bitdefender, etc.) mark a "new" file as dangerous even when it is perfectly clean, and particularly with new releases of installers it is rare to get 0/60. The Virus Total user is expected to analyze the result and decide if the file is to be trusted (because 59 out of 60 antivirus engines consider it clean) or if it is not to be trusted (because a single antivirus engine out of sixty marks it as "dangerous"). Additionally in the case of tools like StartisBack, which Author is a long standing, well-known member of the Community, the only thing to do is to check that the file you have has been downloaded correctly and without modification from the Author's repository, i.e. you should trust the Author and his reputation much more than anything a stupid antivirus engine may believe. jaclaz

What do you mean "restart"? You can have a batch (or vbs, or other script) initiated by TaskScheduler (or good ol'AT) to kill a running process and then restart it, you will need to provide some detail, or, even without task scheduling involved you could have an autorun script at login that check the current date and does (or does not) something based on some calculation on the date. If you want a free, no hassle thingy (with the advantage of being capable to run on *any* MS OS) this is one: http://www.freebyte.com/fbtaskscheduler/ jaclaz

Sure it is not a direct MS responsibility, but surely it is an indirect one. What do you think that dumbifying everything produces? Smarter, more informed people or careless morons? jaclaz

Not really-really Windows 10 related, but close enough: https://arstechnica.com/security/2017/03/doxed-by-microsofts-docs-com-users-unwittingly-shared-sensitive-docs-publicly/ jaclaz

Maybe you are underestimating yourself. Please meet dumphex: http://rbach.priv.at/DumpHex/ So you could easily dump the first four bytes of each .pdf and compare the output with the result of a good .pdf, such as: C:>dumphex /L4 /nc agoodpdf.pdf DumpHex Version 1.0.1 Copyright (c) 2003 Robert Bachmann 00000000h: 25 50 44 46 BUT, trid: http://mark0.net/soft-trid-e.html might be easier. Of course using a "whole" database would be probably a tadbit slower, so creating a specific definition file might be better. Unfortunately current version of trid seemingly chokes on .xml files created by tridscan, you can however use the attached, it is Trid version 1.56 with ONLY the appropriate adobe_pdf.trid.xml C:\VSS\VSS2\tridpack\Simple>trid agoodpdf.pdf TrID/32 - File Identifier v1.56 - (C) 2003-04 By M.Pontello Collecting data from file: agoodpdf.pdf Definitions found: 1 Analyzing... 100.0% (.PDF) Adobe Portable Document Format (7000/1) C:\VSS\VSS2\tridpack\Simple>trid abadpdf.pdf TrID/32 - File Identifier v1.56 - (C) 2003-04 By M.Pontello Collecting data from file: abadpdf.pdf Definitions found: 1 Analyzing... Unknown! jaclaz Trid_for_Den.7z

Guillaume. you have an excess "IF" (on a line by itself) and, besides that, you should check the FOR syntax. The /R switch applies to "each item in files" while you are using it for a "list of names of files" (the kb.txt), see: https://ss64.com/nt/for.html Post the first few lines of your kb.txt, so that I can understand if they include a path, etc. jaclaz

You have to understand how the SSD is laid down and interrogated (internally) has very little (or nothing) to do with what the OS sees (or to what the SSD - or hard disk for that matters - internal processor and mappings let the OS see through the data exchange protocol). Imagine for a moment a SSD (an extremely small one ) with just 16 sectors. Assume that these sectors are identified by a single hex number, ranging from 0 to F, and let's say that 0 to B are actual storage and that C to F are "overproivisioning". You are led to believe (because this is what you apparently see through the OS and each and every tool running on the OS) that these sectors are laid down sequentially as follows: 0123456789ABCDEF but that is ONLY a representation that seems logical and "simple", what you actually know is that, upon interrogation from the OS the device returns those mappings. So when you create your partitions (let's use 4, 5, 3 sectors ones), you are led to believe that your device layout is: 0123-45678-9AB-(CDEF), i.e.: First partition: 0123 Second partition: 45678 Third partition: 9AB Overprovisioning (invisible): (CDEF) In reality the device is (say) laid down as follows (for *whatever*reason, including easier seeking or queing or thermal considerations, whatever): 0F1E2D3C4B5A6978 <- just an example so your partitions may be 0F1E-2D3C4-B5A-(6978) or (for all you know) 0F1E(2)-D3C4B(5)-A69(78). The point is that with any device (including hard disks) manufactured in the last 10-15 years at least there is NO correspondence between the physical layout of the device and its representation to the OS. jaclaz

Maybe, it depends on the reason why it happens, JFYI: http://www.laptop-junction.com/toast/content/dell-ac-power-adapter-not-recognized Provided that the actual charger works properly and the "ID part" is gone, there is actually a "fix", but you won't like it: http://hackaday.com/2014/03/03/hacking-dell-laptop-charger-identification/ jaclaz

Two things (not necessarily useful). Batch files on non DOS based Windows (aka any NT version) should have the .cmd extension (and not the .bat one). Having a long file name with spaces in it starting with "Setup" most probably results in some "non-obvious place" as "Setup~1", possibly also influenced by the hiding of the extensions of the files, this and some other "remains" from previous versions of windows may actually be part of the problem. Questions: Does Setup_Log_File.cmd give the same issue? Does Setup Log Something.cmd? (i.e. are you sure that the issue is the keyword "Setup" and not the keyword "File"?) jaclaz

I would prefer to imagine that all software wouldn't depend on some (lazy? ) guys at MS (or elsewhere for that matters) updating (or failing to update) symbols on their servers... ... a man can dream, cant he ...? jaclaz

See link given here: Make sure that all the drivers are actually installed and compare with that set of instructions (they may be inaccurate, it depends on the specific drivers you need). Otherwise you will need to try a driver injection tool, right now the references I have on 911cd (gone for good) and reboot.pro (hopefully only temporarily down) are unavailable. Try the links given here: via Wayback Machine. jaclaz

Google for: wja72-2305-xp-en.exe Try here: ftp://ftp.psu.ac.th/pub/hp/printserver/wja72-2305-xp-en.exe I believe that around that version they dropped XP support, but maybe there are later versions that are still compatible. jaclaz

But as you just demonstrated, this party NEVER ends! jaclaz

It seems to me like a line has just been crossed https://support.microsoft.com/en-us/help/4012982/discusses-an-issue-in-which-you-receive-a-your-pc-uses-a-processor-tha TL;DR Just §@ç#ing update to Windows 10! jaclaz

Loosely the attributes relate to two different "items" The "Creation date" is an attribute of the file in the context of the "current" filesystem. The "Modified date" is an attribute of the file "in itself". It is typical of a copied file from another volume/filesystem, depending on how exactly the file was copied (or saved). Old KB on the matter: https://support.microsoft.com/en-us/help/299648/description-of-ntfs-date-and-time-stamps-for-files-and-folders jaclaz

Nice one, I would have never thought of that, something to remember, particularly when one is tired and/or hits a roadblock and insists on it head down, without taking some time out for a walk ... Haopy everything is well now. jaclaz

The message "No Phy: Staggered Spin bypass" should have no relevance. Now if you can recover your data, good , then perform the Seagate tests, BOTH the Short and the Long ones, and if any of the two fail, the disk is no good (cannot and shouldn't be re-used). jaclaz

It works here (the batch I mean) just like the command line version, (XP PRO SP2 Italian), it must be something specifically on your machines, but really cannot say what it could be. The output of the simple command here is this: Try this (but I don't think that it will change anything: jaclaz

No ideas. Try asking here: http://malthus.mooo.com/viewforum.php?f=83 jaclaz

Then, ask Syvet (whoever he/she is, do you mean member SvyatPro?). jaclaz

WHAT is "it"? I gave you a list of options EXACTLY because there is a serious miscommunication going on, with you insisting on posting mostly vague one-liners instead of proper, articulated, exact exhaustive questions and statements. Again, does the original WineD3D under Linux work for the "single DX10/11 SDK example"? If it does, then the windows port should work as well, if it doesn't it is NOT a matter of compiling anything, but rather to rewrite part(s) of the WineD3D, and if it was a matter of recompiling it (possibly with some small changes in the compiling options) at least you were given a good starting point. jaclaz

Are you saying that (please choose one or more of the following) : 1) WineD3D (the official source code for Linux) does support DX10/11? 2) That it does not compile for windows using the instructions and scripts by Federico Dossena? https://github.com/adolfintel/wined3d4win 3) That the pre-built version on his site (stated to be DX1-11) does not actually support DX10/11? http://fdossena.com/?p=wined3d/index.frag 4) Something else (please detail) jaclaz