http://bugzilla.wpkg.org/show_bug.cgi?id=93 Summary: 64-bit OS support announcement Product: WPKG Client Version: unspecified Platform: PC OS/Version: Windows XP Status: NEW Severity: enhancement Priority: P2 Component: WPKG Client AssignedTo: mangoo at wpkg.org ReportedBy: skybeam at users.sourceforge.net QAContact: wpkg-users at lists.sourceforge.net Created an attachment (id=84) --> (http://bugzilla.wpkg.org/attachment.cgi?id=84) 64-bit enhanced version including 64-bit launch-wrapper Hi all, It's me again :-) I am just about to migrate my infrastructure to Windows Vista x64 when I run into several problems when using WPKG client with WPKG 1.0-RC4 on Vista x64. I just decided to fix the problems immediately. Unfortunately the main problem was that WPKG Client is a 32-bit application and Microsoft decided that 32-bit applications will be redirected to different registry keys and folders. As a result it is not possible to directly access the 64-bit program files and registry keys when run from wpkg client (due to the fact that the invoked cscript.exe is 32-bit only as well). To work around this I wrote a wrapper which will invoke a copy of the 64-bit cmd.exe where the 64-bit cscript.exe can be accessed. Again: This is a work-around. A clean solution would be if WPKG client would be a 64-bit application which invokes the 64-bit cscript.exe instead of the 32-bit version on Windows x64 editions. So that's what I ask for to be changed. An intermediate solution could be to write a small 64-bit "launcher" which is run on 64-bit systems to invoke cscript.exe instead of running it directly from the 32-bit WPKGSrv.exe. Here's a description of my changes. Files attached. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |