On a related note, I'm running 32-bit XP Pro, can uwin rip a 64-bit process within that?
> Send uwin-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.research.att.com/mailman/listinfo/uwin-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of uwin-users digest..." > > > Today's Topics: > > 1. Re: UWIN 64 - perl and groff install fails on Windows7 > (Matt Lewandowsky) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 8 May 2013 10:09:50 +0000 > From: Matt Lewandowsky <[email protected]> > To: Glenn Fowler <[email protected]> > Cc: "[email protected]?=" > <[email protected]> > Subject: Re: [uwin-users] UWIN 64 - perl and groff install fails on > Windows7 > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > > Hi, > > > Out of curiosity, when you update the perl and groff packages, are the x* > packages also on the agenda? > > > Thanks, > > > Matt > > > -- > Matt Lewandowsky > Big Geek > Greenviolet > [email protected] http://www.greenviolet.net > +1 415 578 5782 (US) +44 844 484 8254 (UK) > > > From: Glenn Fowler > Sent: ?April? ?25?, ?2013 ?11?:?14? ?AM > To: [email protected], [email protected] > CC: [email protected] > Subject: Re: [uwin-users] UWIN 64 - perl and groff install fails on > Windows7 > > > > > On Thu, 25 Apr 2013 19:39:40 +0200 Simon Toedt wrote: >> On Thu, Apr 25, 2013 at 4:24 PM, Bear Limvere >> <[email protected]> wrote: >> >>> When I tried to install either uwin-groff.2008-11-15.win32.i386 or >> >>> uwin-perl-58.2005-11-04.win32.i386, I get an open command prompt >> with the >> >>> message "cannot find UWIN registry keys" > > the installation registry was reorganized a few years back > the intention was to keep it backwards compatible but that > obvisouly didn't work > > we'll repackage groff and and updated perl 32 bit for next week > >> Is there still anyone left who didn't abandon UWIN? The UWIN lists are >> pretty much like a desert when I compare it to the hundreds of posting >> I get from the Cygwin lists > > a bunch of non-cygwin code and packages need #ifdef CYGWIN > and that generates a lot of traffic > > also, while cygwin was/is busy posting about how hard it would be to get > 64 bit > native executables working we implemented it 2 years ago on uwin with > transparent > access between uwin*32 and uwin*64 bit processes and files > and via the virtual /32/ and /64/ mounts we also managed to tame the > microsoft penchant for adding a new api for the cross product of > file/registry X ucs16/utf X 32bit/64bit > > for the past year or so we have been concentrating on performance in the > face of heavy process load -- the internal test scripts we have regularly > crashed uwin and cygwin -- getting uwin through that has been a chore > > we're also in the process of thread-safing many of the libast apis > and that's another time-consuming activity that thankfully is nearing > conclusion > > _______________________________________________ > uwin-users mailing list > [email protected] > http://lists.research.att.com/mailman/listinfo/uwin-users > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.research.att.com/pipermail/uwin-users/attachments/20130508/81235cbc/attachment-0001.html> > > ------------------------------ > > _______________________________________________ > uwin-users mailing list > [email protected] > http://lists.research.att.com/mailman/listinfo/uwin-users > > > End of uwin-users Digest, Vol 98, Issue 2 > ***************************************** > _______________________________________________ uwin-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/uwin-users
