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

Isn't an already compiled build good enough? You know *like*: https://sourceforge.net/projects/wined3d4win/ Or you could ask there if you have issues with: or, you know, here: https://github.com/adolfintel/wined3d4win jaclaz

Yes (or possibly No). http://web.archive.org/web/20160304215417/http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/questions-with-yes-or-no-answers.html jaclaz

Not only, they also break in any kind of different ways. jaclaz

There is a known method, through using a valid, legit key[1], that is exactly what you lamented being unable to find: jaclaz [1] or, as you prefer, "a key that works".

Basically you are asking for a working key that definitely falls under Rule 1.a of the Board: http://www.msfn.org/board/guidelines/ and anyway the first two Rules of the Pirate Club are: 1) You don't talk of the installation of a pirate copy of Windows 2) you DO NOT talk of the installation of a pirate copy of Windows jaclaz

All is well that ends well. jaclaz

I missed the previous episode ... Maybe you could point us to it or provide some more details on what happened before. First thing I would personally try would be to add a new user, and verify that the behaviour is the same (or it is not) with this new account. jaclaz

Yes, to be a "hard disk like" device the card needs to be partitioned. Do check it (after having partitioned it "normally" with fdisk) with Ranish Partition Manager (or use directly RPM to partition it), and take note of the CHS geometry that is detected by BIOS, I seem to remember that (it depends on specific CF cards and also on their size) some may have "queer" geometries which won't affect normal usage but that may be an issue when/if some tools are used that assume a "conventional" 255/63 one. jaclaz

Yes, that's normal: jaclaz