vDOS 2018.05.01, closes #4880 @0.4h

packages/vdos/tools/chocolateyinstall.ps1

@@ -6,7 +6,7 @@
 # package installs to 'default' location: c:\vDOS 
 
 $packageName	= 'vdos'
-$version        = '2017.08.01'
+$version        = '2018.05.01'
 $installerType	= 'exe'
 $scriptPath     =  $(Split-Path $MyInvocation.MyCommand.Path)
 $setupFullPath  = Join-Path $scriptPath 'vDosSetup.exe'

packages/vdos/tools/chocolateyuninstall.ps1

@@ -2,7 +2,7 @@
 # 2011-2018 foo.li systeme + software
 
 $packageName	= 'vdos'
-$version        = '2017.08.01'
+$version        = '2018.05.01'
 $vdosPath		= "$env:SystemDrive" + "\vDos"
 
 try {

packages/vdos/vdos.nuspec

@@ -2,7 +2,7 @@
 <package xmlns="http://schemas.microsoft.com/packaging/2011/08/nuspec.xsd">
     <metadata>
         <id>vdos</id>
-        <version>2017.08.01</version>
+        <version>2018.05.01</version>
         <title>vDOS</title>
         <authors>Jos Schaars</authors>
         <owners>foo.li systeme + software</owners>
@@ -10,12 +10,12 @@
         <projectUrl>https://sourceforge.net/projects/vdos/</projectUrl>
         <iconUrl>https://git.foo.li/peter/chocolatey/raw/branch/master/icons/vdos.png</iconUrl>
         <requireLicenseAcceptance>true</requireLicenseAcceptance>
-        <description>KVM Virt Viewer</description>
+        <description>vDos: Run DOS applications in Windows</description>
         <summary>Windows 64-bit doesn’t support DOS applications. Windows 32-bit included NTVDM,
 		to some extend facilitating DOS programs to run. PC’s now come with Windows 10 64-bit installed,
 		mostly without an option to downgrade to Windows 32-bit. vDOS takes care of this limitation.
 		</summary>
-        <releaseNotes>initial packaging</releaseNotes>
+        <releaseNotes>see notes at https://www.vdos.info/download.html</releaseNotes>
         <tags>dos vdos windows10x64</tags>
     </metadata>
 </package>