Opened 8 years ago

Last modified 2 years ago

#28 new enhancement

Update setenv.bat for Windows "PowerShell"

Reported by: Jeff McKenna Owned by: Jeff McKenna
Priority: major Milestone: 5.0.0 release
Component: MS4W - Base Version: 3.1.0
Keywords: Cc:
Blocked By: Blocking:

Description

Newer machines (such as Windows 2012 Server) contains only powershell (not cmd.exe). The existing setenv.bat script will fail.

Possible new command:

$ENV:PATH+=';C:\ms4w\Apache\cgi-bin;C:\ms4w\tools\gdal-ogr;C:\ms4w\tools\mapserv;C:\ms4w\tools\shapelib;C:\ms4w\proj\bin;C:\ms4w\tools\shp2tile;C:\ms4w\tools\shpdiff;C:\ms4w\tools\avce00;C:\ms4w\python\gdal;C:\ms4w\tools\php;C:\ms4w\tools\mapcache;C:\ms4w\tools\berkeley-db;C:\ms4w\tools\sqlite;C:\ms4w\tools\spatialite;C:\ms4w\tools\unixutils'

Howto: http://blogs.technet.com/b/heyscriptingguy/archive/2011/07/23/use-powershell-to-modify-your-environmental-path.aspx

Change History (9)

comment:1 by Jeff McKenna, 8 years ago

A workaround is to just use the native "cmd.exe" which actually exists (somewhere like C:\Windows\WinSxS\).

comment:2 by Jeff McKenna, 8 years ago

Milestone: 3.1.1 release3.1.2 release

comment:3 by Jeff McKenna, 8 years ago

Milestone: 3.1.2 release4.0 release

comment:4 by Jeff McKenna, 8 years ago

Type: defectenhancement

comment:5 by Jeff McKenna, 8 years ago

Milestone: 4.0 release4.1 release

comment:6 by Jeff McKenna, 4 years ago

Milestone: 4.1 release4.2 release

Milestone renamed

comment:7 by Jeff McKenna, 4 years ago

Milestone: 4.2 release4.1 release

Milestone renamed

comment:8 by Jeff McKenna, 3 years ago

Milestone: 4.1 release4.1.0 release

Milestone renamed

comment:9 by Jeff McKenna, 2 years ago

Milestone: 4.1.0 release5.0.0 release

Milestone renamed

Note: See TracTickets for help on using tickets.