From "Glenn Fowler" <[email protected]> on Saturday, May 16, 2009 7:15
AM:
I go through the dialogs (why does it install to C:\Program Files instead
of
C:\Program Files (x86), by the way?),
first things first
(working uwin, then installs in the right place)
Fair enough. It would probably help portability to non-English-language
systems if it used the value of %PROGRAMFILES% somehow. But, then, the
installer may have to be able to deal with UTF-8 paths. (I keep meaning to
see what happens with UWIN on non-Latin-script Windows versions, for
amusement.)
try the 2009-05-15 beta
I did, as mentioned in my next email. Same results of nothingness. In fact,
that same exact install attempt is still running; I've not yet bothered to
kill the dozens of running ksh.exe processes it spawned. (Sadly, End Process
Tree doesn't seem to work on them...)
most of our experience is with 32-bit xp/vista/w7
As is mine. :)
the goal is to eventually build native 64-bit too
That would be awesome; but, for now (at least until whatever is after
Windows "7", when Win32 apparently goes away), 32-bit is fine. Who needs a
cat which can read 4GB at once? ;)
P.S. Does this UWIN beta include the ksh 2009-05-05 beta (and, if so,
presumably the rest of the 2009-05-05 ast)?
yes
Awesome.
Thanks,
--Matt
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
