[
https://issues.apache.org/jira/browse/VCL-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016442#comment-16016442
]
ASF subversion and git services commented on VCL-1013:
------------------------------------------------------
Commit 1795560 from [email protected] in branch 'vcl/trunk'
[ https://svn.apache.org/r1795560 ]
VCL-1013
Removed Windows.pm::setup_check subroutine and vcld -setup 'Check Windows OS
Module' menu item. It was only checking for XP and 2003 product keys.
> Modernize parts of Windows code
> -------------------------------
>
> Key: VCL-1013
> URL: https://issues.apache.org/jira/browse/VCL-1013
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Fix For: 2.5
>
>
> The Windows code does several cleanup actions during pre_capture. Some of
> them are a bit crude and could cause problems with things such as Windows
> Update. For example, the following are being deleted:
> * C:\Windows\ServicePackFiles\*
> * C:\SoftwareDistribution\Download\*
> It would be better to let dism.exe and cleanmgr.exe handle all of the cleanup
> unless there are files known to be 100% safe to delete.
> The cleanmgr.exe code has hard-coded registry entries for items to clean up.
> These represent the checkboxes you see when you run _Disk Cleanup_. The
> options vary based on version and which features are installed. There are
> options for Windows 8 and later not being used. This should be updated.
> There are other details which should be removed:
> * Defragment hard drive - I see no real advantage for this anymore. It's
> detrimental for some VM images if the image is stored thin. Under
> VMware/thin, if a file is created and deleted or moved to an empty location,
> the original space isn't reclaimed without special operations
> (sdelete/punchzero). Bare metal use of VCL is rare these days and I don't
> see much of a benefit regardless.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
