HarryTri

Member
  • Content count

    325
  • Joined

  • Last visited

Community Reputation

12 Good

About HarryTri

  • Birthday

Profile Information

  • OS
    Windows 8 x64
  • Country

Recent Profile Visitors

643 profile views
  1. The product key can be retrieved from the BIOS with several programs. And the hardware doesn't last for ever...
  2. Is there a real difference between OEM System Builder and "mere" OEM editions of Windows 8? I red somewhere that it is practically the same, "System Builder" is a term that remained from older versions of Windows. Anyway in Reddit, Tomshardware and other sites it is clearly stated that in contrast to Windows 7 OEM (preactivated) Windows 8 OEM (not preactivated) is transferrable to other hardware (including different motherboard)/ computer, there are even people who say that they have done it themselves, I don't know if this was reverted in the case of Windows 8.1 and 10 but I doubt it.
  3. Windows 8 and newer OEM license can be transferred to an other computer, have a look at this link (for Windows 8): http://personaluselicense.windows.com/en-US/default.aspx So you can use an OEM version key as far as it is not used on another computer.
  4. After a further investigation it appears that Windows 8 and newer OEM Windows license can be transferred to another computer, have a look here (for Windows 8): http://personaluselicense.windows.com/en-US/default.aspx EDIT: Maybe the things are a bit different, have a look here: http://www.msfn.org/board/topic/176310-toshiba-satellite-c655-clean-windows-7-home-premium-installation/?do=findComment&comment=1133863 Anyway the thing is technically possible and at least for a VM Microsoft will probably cooperate (some say they do for even more).
  5. For Windows 8 and newer this is unneeded, OEM Windows license can be transferred to an other computer, have a look here (for Windows 8): http://personaluselicense.windows.com/en-US/default.aspx EDIT: Maybe the things are a bit different, have a look here: http://www.msfn.org/board/topic/176310-toshiba-satellite-c655-clean-windows-7-home-premium-installation/?do=findComment&comment=1133863 Anyway the thing is technically possible and at least for a VM Microsoft will probably cooperate (some say they do for even more).
  6. I wouldn't update to Windows 10 in anyway so I guess I'm in level 1. However what does this "creator" thing has more or different than the current Windows 10? Is it going to replace any existing version(s) of them or it is just a new version?
  7. It is strange that it happened on both of your systems at about the same time. Maybe something that you installed or upgraded recently on both of them has to do with it?
  8. After a check on my system I found the known junctions referenced (Documents and Settings etc.) but no symlinks or symlinked directories. It seems that the later were used in older versions of Windows. Just for the history. And of course thanks again for the information jaclaz.
  9. That seems to indicate that using OEM version of Windows in a virtual machine isn't exactly illegal (I'll have a separate license of Windows 10 of course). The thing is that I also wasn't able to find an oembios.bin file in my Windows 8 installation and in the BIOS the Windows license is referenced as "WINDOWS 8 STD MLT" (Windows 8 Standard Multiple I suppose), there is no clue it is an OEM license. Maybe from Windows 8 and on there isn't really such a thing as OEM versions?
  10. Let me just say that the problem is the following: The flash drive usually has FAT32 as file system and when you copy the recovery partition to it the one several GB xxx.wim file that it contains is split to these several .swm files. If you join them to make the initial xxx.wim file you are (?I am not sure that this is always enough) done. Surely jaclaz knows more about it. Of course the question is how to join them, maybe extracting the files they contain and use them in another way is more feasible. I write this post without having read the ones that jaclaz points to, I don't have the time now. Anyway these are just my thoughts...
  11. I have a Lenovo laptop with Windows 8 x64. I retrieved its serial number from the BIOS. I also have a Windows 8 x64 DVD - the official generic one - from the internet (downloaded as an ISO image). If my laptop "dies" and I buy a new one with Windows 10 will I be able to install and activate Windows 8 with the mentioned DVD and my current laptop's serial number on Virtual Box?
  12. It seems that symlinks/junction points are what I referred to as "hardlinks". Hardlinks seem to be the real answer to the mystery. On a site I red some time ago that all the system files of Windows 8 are hardlinks from WinSxS and I didn't believe it. It seems that the guy was right: Thanks for the help jaclaz, you are great!
  13. Hardlinks are not accessible even from an elevated command prompt: Symlinks? Are they different than hardlinks? As for sparse files this is a possibility but 5.32 GB? Note that huge possibly sparse files like pagefile.sys add their size to the allocated disk space shown in Windows Explorer: if they grow (you know when) it grows too. And what about the 39901 more files in dir/a/s?
  14. Well, the case is that Windows themselves find (with dir/a/s) more files and allocated disk space than the ones shown in chkdsk or Windows Explorer...
  15. Thanks for the response Tripedacus but no, dir/a/s and 7-zip show all these files. Can somebody check on his system (Windows 8 or newer) to see if he has similar results? Perhaps Microsoft uses some kind of trick to present fewer files and allocated disk space in the Windows partition (the other partitions give normal results as I have found)?