Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

54 Excellent

About alacran

Profile Information

  • OS
    Windows 7 x64
  • Country

Recent Profile Visitors

2,719 profile views
  1. I use since long time ago this free firewall controler from sordum.org and it works great. Firewall App Blocker (Fab) v1.6: https://www.sordum.org/8125/firewall-app-blocker-fab-v1-6/
  2. I updated my 7x64 Iso upto Dic/2017 just before all the debacle about Meltdown and Spectre, and installed the OS, since then I decided to stop updating the OS, since every update is full of telemetry and also very frecuently bugy, I have Avast Free AV, and run maybe once every 2 months the AV and also Malwarebytes Antimalware free, just to confirm the PC is clean, and I haven't got a single virus. So only updates on my PC are for FireFox, Avast and Antimalware. Now Win7 support is very close to end, I may update my Iso with the final last update, (cleaning as much telemetry as possible) and reinstall 7x64 and will use it as log as there are AV and browser available for it. So my OS do not grow at same rate as yours, it is using right now 21.5 GB from a 50 GB partition, System restore is deactivated, since I make periodicaly full images of each OS in the PC, documents, all games and majority of programs are installed on another partition, I have backups of all important info on external disks, the idea is keep to OS partition basicaly with only the OS, Office, AV and browser to get the smaller size when making an image of the OS partition. Also have 10x64 on another partition (it was done to get the free HWID register only, almost never used), and Linux Mint 19.2 Cinnamon x64 on a secondary disk, wich I have been testing for about 2 or 3 weeks now and so far found it is a good solid OS (and you get about twice or thrice a week small size updates) only issues are many games and Autocad do not run on Linux, but for anything else it is very fine.
  3. Well, you always had the answer all the time.
  4. You could also try using the online free version of Sketchup directly on your browser (from Linux): https://www.sketchup.com/plans-and-pricing/sketchup-free I think FireFox or Google Chrome will work fine for this.
  5. @Windows 2000 I think you should buy the best AMD CPU with included graphics, and compatible Motherboard you can pay, and it will have better graphic capavilities and will be good for long time, about the storage I differ a little with WalkInSilence, since for starting the SSD you selected is good enought for OS (32 GB is the requirement for any x64 OS) and still have some space (about 85 GB) available, then latter when/if required you can add a secondary (mechanical) HDD or a secondary bigger SSD if you prefer, to increase the storage. So better put more the money on CPU and motherboard than in a bigger SSD. Or you will lament it later. About the Motherboard: Asus is my prefered option even the entry level models. Gigabyte is also a reputable brand and would be my second option. Don't buy a cheaper brand as they usually faill sooner than the 2 mentioned brands, just to let you know I still have an i3 3225 running on an Asus MB (first and only MB used), and another i3 3225 (My brother PC) still working (both builded with a difference of 3 months) is on its third MB (one Asrock and now on second Biostar), soket 1155 MBs were not available anymore but I had 2 used Biostar from upgraded PCs.
  6. I think it will work fine at 1080p, but not fine at 4K Full HD = 1920 horizontal lines by 1080 vertical lines 4K = 3840 horizontal lines by 2160 vertical lines It means 4K has double horizontal lines by double vertical lines, 2 x 2 = 4 times the Full HD resolution or 4 times the load to the GPU. See this review: https://www.windowscentral.com/amd-athlon-200ge-worth-it
  7. Thanks for your quick answer. Ok, as when 8.1U1 started with wimboot MS recommended to use Dim, and also I have seen DismApi.dll just next to Dism, I had the idea it used a different Api. And yes you are right the problem is only present when using a custom WimBootCompress.ini on wimgapi, I apologize for insisting on this subject. The key word is as you said: wimboot mode is a deprecated feature. At least we can use wimlib for our custom lists.
  8. @JFX I have been using WinNTSetup since long time ago and I love this little and very useful program, in fact AFAIR I was the first translator (spanish 2058.dll, just to do something in return for this fantactic tool and make it available to more people). I liked now wimlib and BootIce are included on download, no more copy paste from previous folder and sometimes having copied an older version of wimlib. This are my thoughts about future version 4: Now that WinNTSetup is capable to capture installed OSs, it became a Backup tool and it needs to be trustable on all cases with no exception. Not that it wasn't trustable before, but it is not so critical a new installed OS than a redeploy from your backup full with vital info, programs and third party drivers of our devices. On new installs where no third party drivers are installed yet it seems there is not any issue, also this applies to standard installs (not wimboot) with third party drivers included. It seems wimgapi is not a good option when dealing with wimboot when having third party drivers included on the *.wim, maybe it could be replaced by Dism for this job. I know Dism is slower but better slow than wrong. Of course this may apply for people who only want to use MS tools. B_7 was maybe working a little better since it was capable to extract fine all Windows (not third party) drivers (as per \Windows\System32\drivers\*.sys) and could be used on new installs including wimboot installs where no third party drivers are involved. I think it is necesary to test Compact installs by means of wimgapi when having third party drivers included on the *.wim, to check if it can work fine on this scenario or not. And in case of troubles maybe it could be replaced by Dism for this job too. As said before I know Dism is slower but better slow than wrong. Of course this may apply for people who only want to use MS tools. Other option may be use only wimlimb on this scenarios, since it is very reliable and block wimgapi use (or hard code the automatic use of wimlib) on those scenarios where wimgapi has issues. Maybe easier way is to do this is adding on main screen an user option for select: new install to let the program (B_7 looks fine to me) work as usuall (with wimgapi or wimlib as selected). or redeploy backup to force only the use of wimlib looks like not a bad idea particularly for new users. I know select wimlib is available but not so easy to find, and as when selected the selection is not persistent (looks fine to me), then it is easy to forget re-selecting it next time. And for capture the installed systems always use wimlib (at least as preselected option), faster, smaller size images and more reliable. I haven't use this new feature of WinNTSetup yet but when selecting wimlib I don't see the very usefull option append (unless you aren't using capture and using directly append wich appends to existing file or creates it, if it do not exist), please would you confirm this? Also when selecting wimlib don't see an option for wimboot capture. have you any plans for adding it? I have been using wimlib for very long time, first on command line and latter by means of its GUI wimlib-clc (I'm beta tester and Spanish translator of this tool) for making (all included divers and programs) wimboot VHDs and later compressed (130 MB and smaller) by lz4 (using lz4 Compressor) capable to Ramboot in just a few seconds without any issue. Also as my backup tool for about 5 years and never had a single trouble, when I redeploy my OS from the backup image it always works flawlessly (7, 8.x or 10). Best Regards alacran
  9. @wimb I assume you are running WinNTSetup_x64.exe, it uses WinNTSetup\Tools\x64\wimgapi.dll version 10.018362.1. And WinNTSetup_x86.exe still uses WinNTSetup\Tools\x86\wimgapi.dll version 10.015063.0 You may try using WinNTSetup_x64.exe with wimgapi.dll x64 v10.015063.0, version used on older WinNTSetup (x64 & x86), since other versions were buggy, use GetWaikTools to download it. EDIT: Also we need to remember there has been a change in certificate driver enforcement requiring only SHA2 (since Windows 10, version 1803) and the wimgapi version in use may or may not be able to support SHA1, SHA2 or both. wimgapi.dll version 10.015063.0 (15063= v1703) from the table on previous link 10 v1703 supports SHA1 and also SHA2. alacran
  10. To have all drivers available (not as pointers) and avoid troubles when using wimboot mode it is good to add this line \Windows\System32\drivers\*.sys under [PrepopulateList] to your custom WimBootCompress.ini used for capture. (I'm assuming this was done) When you capture an install in wimboot mode using wimlib and use a custom WimBootCompress.ini, the internal Windows\System32\WimBootCompress.ini file is replaced by the custom file used during capture, then latter it is used during applying it in Wimboot mode. wimlib works fine doing so from wimb reports and in my own experience. It seems to me for some reason when using on WinNTSetup wimgapi + WimBoot this is not following this procedure and it is using maybe the file list on WinNTSetup\Tools\WimBootCompress.ini, then as a result having pointers to the required drivers in this case, or perhaps wimgapi do not use the WimBootCompress.ini file anymore (based on JFX comment). Easy way to verify if there is real extracted files or pointers is open your unmounted VHD with 7zip, go to check some of required driver files and see its compressed size, where 0 = Pointer file to source *.wim, >0 = Real extracted file. Also check size for some of files listed on WinNTSetup\Tools\WimBootCompress.ini and then you will have enought info to know if your custom list, internal list of WinNTSetup or none are used durig applying the wimboot install. Sorry I can't help any further but I haven't deal with this problem since when making Wimboot VHDs I always prefer to use wimlib for capture and apply them. alacran
  11. @JFX Attached new version of Spanish Translation with some improvements. alacran 2058.7z
  12. & Then why not install Win 10 on VirtualBox? or maybe before doing this, update the video drivers on your (virtual) win 7 install or try selecting a different virtual video card (if available, since I don't remember right now if this is possible on VirtualBox), it is the video card (dedicated or integrated into CPU) who runs/uses by means of its respective drivers OpenGL 3.0 or higher. alacran
  13. Well, I could say there is no news, just bad updates every month, another thing I can say is they are very consintence. IMHO this is caused mainly because they are always trying to introduce new features/changes every month, they need to stop thinking this way and concentrate all efforts and all required time in fixing all that is wrong first, then when having the OS working flawlessly, they can comeback to introduce new features/changes but not before making extensive tests. alacran
  14. @JFX Good work my friend, congratulations, your tool is always geting better on every new version. Attached improved Spanish translation (based on version 4 Beta 5), VHDs descriptions didn't fit on available space on my previous translations. alacran 2058.7z
  15. @JFX Attached Updated Spanish translation to 4.0 B3 alacran Updated Spanish translation.7z
  • Create New...