jaclaz

Yep but - on the other hand - you should take into account that in these long seven years new techniques may have been developed .... and think about the big money these data recovery companies can make by keeping their abilities secret and selling the technology to noone . There is simply no way to convince a believer, at the most we can try and cite what is documented, but of course the fact that something is not documented and is not reproducible doesn't mean that it doesn't exist or rather that it may exist. Absence of evidence ... https://en.wikipedia.org/wiki/Argument_from_ignorance#Absence_of_evidence Now, for NO apparent reason, an excerpt from pressing the "Reionize Electrons" button here: http://tinyurl.com/lgme3zu jaclaz

Good, then try following EXACTLY the given reference using a plain DVD: http://h10032.www1.hp.com/ctg/Manual/c01717787.pdf As said, BEFORE that you should be able to boot a Windows 7 install DVD and from the PE on it (press Shift+F10) you should be able to run wpeutil Updatebootinfo, etc. so that you are sure you are able to boot in the "right" mode or if you need to experiment with your firmware settings. And again that report without EXACT DETAILS of what (STEP by STEP, long, expanded, detailed) you did is totally meaningless. jaclaz

And these opinions and facts continue to be ultimately and utterly irrelevant. Today is a bit cold but the sun is shining here, hopefully the 1st of January it won't rain or snow, how is the weather wherever you live? How will it be where Samuka lives? Hey, dencorso, how is it in Brazil? Would you use detetado or detectado in Portuguese? jaclaz

Yes, but "I tried x and it didn't work" or "I tried y and it didn't work" are unfortunately not detailed enough reports to attempt helping you. I know it is a PITA, but each of the *whatever* you tried implies a number of choices and an almost infinite number of possibilities on EXACTLY how it is carried. We don't even know how EXACTLY (and no "Partitioning:GPT Format(Windows 10 is preinstalled so)" is not a description of how EXACTLY) your disk is partitioned. You previously hinted that Windows 7 install in csm mode worked (or did you mean that booting the install media of Windows 7 in csm mode worked)? Maybe we could start from the beginning. BIOS (or CSM) booting works as follows: BIOS->MBR of first disk->bootsector of active partition in MBR->BOOTMGR->Settings in \boot\BCD->windows\System32\WINLOAD.EXE->Windows UEFI booting: UEFI->EFI bootloader in EFI NVRAM (residing on a FAT32 dedicated partiton) typically \EFI\Microsoft\Boot\bootmgfw.efi ->Settings in \EFI\MICROSOFT\BOOT\BCD->\windows\system32\winload.efi -> Windows If you actually had installed *something* you shouldn't be able to still boot Windows 10 (unless you installed on different partitions/in some strange ways) . Please boot the Windows 10 and post the output of the diskpart command like in here: https://technet.microsoft.com/en-us/library/dn336950.aspx DISKPART> select disk 0 DISKPART> list volume Volume ### Ltr Label Fs Type Size Status Info ---------- --- ------ ----- ---------- ------- --------- ------ Volume 0 D NTFS Partition 103 GB Healthy Volume 1 C NTFS Partition 49 GB Healthy Boot Volume 2 S FAT32 Partition 200 MB Healthy System so that we can understand your Disk partitioning (and mounting letters). Do you have a working DVD drive so that we can try directly from a DVD instead of using a USB stick? Or can you boot from USB a (Windows 7 based is better) PE of some kind (as said if you can boot the Windows 7 install media or an iso image it will be OK)? From it (see here): https://www.eightforums.com/tutorials/29504-bios-mode-see-if-windows-boot-uefi-legacy-mode.html run: wpeutil UpdateBootInfo and: reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType thus detecting if you could boot in UEFI or are still in CSM mode? jaclaz

Good . Keep us posted please, a daily update would probably be overkill , but once a week would be OK. @Vinifera Fresh from the press, maybe of interest to you: https://articles.forensicfocus.com/2016/12/30/who-why-what-android-spying/ jaclaz

Those are two different errors, though both are related to Winload failing to find the right files or due to a misconfiguration of the BCD, maybe I am starting to understand , so the issue is not (as I had understood initially , my bad) that you installed the Vista and that it doesn't boot, it is the install media that doesn't boot properly, right? ). If this is the case, it is possible that *something* in your Rufus based USB stick is causing the issue (maybe you are using the Rufus NTFS EFI driver?), you can try using WinntSetup after having booted a PE from a "normal" stick or - since the Windows 7 install boots, use its setup PE to run WinntSetup. The generic idea behind it is simple, it derives from this: http://reboot.pro/topic/10126-nt-6x-fast-installer-install-win7-directly-to-usb-external-drive/ the idea is to deploy the install.wim and then create a proper BCD. Even if Vista (x64 and in UEFI mode) is probably the "less tested" OS with WinntSetup, it should work fine with it. Particularly on laptops, finding the "right" mode to boot is usually a nightmare, if your source is already SP1/2 you need to boot in UEFI mode, see if this helps (your firmwaer settings should be similar): http://h10032.www1.hp.com/ctg/Manual/c01717787.pdf jaclaz

Well, the paper theorized 20 years ago that data recovery through MFM and/or STM was possible (and does not suggest in any way that other methods exists). AGAIN that paper is ONLY theoretical, no documented experiments ever managed to retrieve any meaningful data with any means from any disk, if not - maybe - a single experiment that allegedly managed to recover some partial data at an excruciating slow rate from an extremely old and low density disk, JFYI: http://www.forensicfocus.com/Forums/viewtopic/p=6581471/ BUT, let's put it in another way. CERTAINLY a very restricted number of people with infinite time and infinite budget can do that and much more than that. If you are paranoid, the ONLY way to make sure that noone is ever capable of reading your precious data is to destroy physically the media, break it in several pieces and mail these to random addresses (in China or elsewhere), JFYI: http://www.forensicfocus.com/Forums/viewtopic/t=9682/ BUT, conversely those same people have no issues whatsoever in reading your mind WHILE you are writing or reading the data, so even destroying the media would be untimely. We have some solutions for these problems also, still JFYI: http://reboot.pro/topic/13177-an-improved-electromagnetical-shielding-device/ For all normal people one single 00 pass is enough, please DO NOT recommend to other people to stress their devices without any need, or accept the fact that every time you will post your "advice", if I see it, I will reply stating how it represents a baseless assumption that carries no connection whatsoever with reality, at least from the reality as perceived from all the published works on the matter. jaclaz

Besides the fact that whether Samuka is a girl or a boy does not matter at all, in English speaking countries Samantha is often abbreviated to Sam, Samy or Sammy. Andrea is sometimes (mis)used in Italian also as a female name (but it is normally male). jaclaz

Well, you either have CSM (please read as BIOS) or you don't have it. If you use CSM/BIOS you need a MBR style disk, GPT booting support is NOT available in Vista (as said there may be complex workarounds that allow BIOS booting from GPT style disks, but they would need some specific reason to take the effort). Try spending a few words describing: 1) the machine in question (EXACT make/model and possibly the BIOS or UEFI, let's call it "firmware" version). 2) How (EXACTLY) is the disk partitioned 3) How (EXACTLY) you are trying to install the Vista (like from CD, from USB, which program you used to modify the source -if any - which program you are using to assist you in the install -if any - etc.) Right now the "best" (IMHO) approach is JFX's WinNTSetup: but BEFORE attempting using it, it is better if we can assist you in making a "plain" install, as your particular case could be aN "edge one" for which the above program has not been tested against. jaclaz

UEFI booting of Vista is simply not supported, let alone on GPT. You can most probably (but it has to be seen) boot Vista in BIOS (or CSM) on GPT, using a number of tricks. If your computer is UEFI only with no CSM support you simply cannot boot Vista from it, unless *somehow* one of the later (8/8.1/10) .EFI bootloaders are (or can be made) compatible with Vista. jaclaz

Moonchild WHO? jaclaz

Hmmm. Maybe you need to reword that. Possibly keeping BIOS as counterpart of UEFI and MBR as counterpart of GPT. Last time I checked Windows 8 and 8.1 (cannot say 10) booted from MBR really fine, whilst XP could definitely not boot in UEFI mode and not even from GPT disk on BIOS. jaclaz

Perpendicular recording completely changes the rules of the game. Anyway from the paper (which was and is a theoretical paper and not - as half of the world read it a factual report): Please consider additionally how in the 20 (twenty) years since the paper was published noone ever documented having successfully retrieved any meaningful info from a disk that has been wiped with a single pass of 00's. Of course this may be the result of a conspiracy by three or more letter government agencies, but - as I said before - with older drives at least the theory was sound, with modern drives even the theory is invalid. jaclaz

You mean you know noone actually working? jaclaz

Yes, it's safe, it's very safe, it's so safe you wouldn't believe it. jaclaz

Actually they are over-oversimplified, and not only here. It simply makes no sense saying that system x is more secure than system y, because you never have the counter evidence, system x may be resistant to attack #1 (while system y is not) and system y may be resistant to attack #2 (while system x is not) and both may be non resistant to attack #3. jaclaz

No, actually the system is isolated, any OS would do, in this case: https://www.theguardian.com/technology/2016/jan/16/trident-old-technology-brave-new-world-cyber-warfare jaclaz

Here (just for the record): http://winhistory.de/more/386/xpmini.htm.en jaclaz

As a matter of fact there is an "official" way out, the GGK: Whether one of those can still be found is another thing. jaclaz

When you installed the XP, the install has overwritten the bootsector of your (I presume NTFS) boot partition (the one that MS calls "system") i.e. where your NTLDR and BOOT.INI (and NTDETECT.COM are. This is "normal", the XP install knows nothing about Vista or any later OS and does not "preserve" such installations. Leave alone EasyBCD. The easiest for you is to: 1) get a recent grub4dos, any 0.4.5c or 0.4.6a version from 2016 would do: http://grub4dos.chenall.net/categories/downloads/ This (latest 0.4.6a) would do: http://dl.grub4dos.chenall.net/grub4dos-0.4.6a-2016-12-24.7z 2) extract from the .7z file just the grldr and the \sample\menu.lst, and place them in the root of the partition where you have NTLDR and BOOT.INI 3) edit BOOT.ini adding to it a line: c:\grldr="grub4dos" and increase the Timeout value to - say - 10 seconds, your BOOT.INI should look *like*: [boot loader] timeout=10 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect c:\grldr="grub4dos" Boot and choose "grub4dos", you should have a menu with - among other choices - "load BOOTMGR of Windows VISTA/WIN7/WIN2008 on ...", choose that one and you should be able to boot to Vista as you could before. jaclaz

Please do not contribute to this unfounded myth, if something is overwritten once it stays overwritten and NOTHING can find what was there before. Though no one ever recovered anything meaningful when at least the theory was valid, nowadays, in times of perpendicular recording, not even the theory stands. Making more than a single overwriting pass is only a good way to stress the device, even the Author of the most famous (and BTW most misinterpreted) paper on the subject has added some "Epilogues" (still written somewhat - I have to believe intentionally - ambiguously) : https://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html Nowadays on hard disks nothing more that a single 00 pass is needed. jaclaz

It's simply not possible to run Windows 95 with 2 Mb of RAM (maybe it is possible, but it won't actually run, maybe "crawl"). The minimum hardware required (the one that you have to double to have actually working system and quadruple to have an actually running one) is 4 Mb, you actually need at the very least 8 and - more realistically - 16 Mb (and this still is too little to have anything connected to the web actually working decently). jaclaz

I will throw this on the table (and quickly hide my hand behind my back ): https://www.haiku-os.org/ Also the Linux world has (since many years) gone wild with processor and memory requirements, and - actually - most of RAM is needed for actually browsing stupidly massive web sites, among the various Linux distro's, besides Puppy Linux andd Slitaz, you may want to try Vector Linux: http://vectorlinux.com/ jaclaz P.S.: A nice coincidence: https://www.raspberrypi.org/blog/pixel-pc-mac/

Does this mean that the Virtual hardware of virtualbox is compatible with Kmuland's laptop hardware (or viceversa) or that the VirtualBox driver is "not only for virtualbox"? The driver info is here: http://www.os2museum.com/wp/nt-video-miniport-for-virtualbox-with-source-code/ but it doesn't mention anything about "real hardware". jaclaz