Here are slight specifics that occured after that mail:
I've been able to reproduce these setup problems somewhat, and more:
I installed to c:\uwinboot:
UWIN 4.2 installation had 1 error and 2 warnings. Installation failed
and then a messagebox:---------------------------UWIN
Setup---------------------------UWIN installation failed with exit status
256---------------------------OK ---------------------------
I left that alone, no uninstall/cleanup, and then installed to c:\uwin2.
Same result I think. Plus I got a "data execution prevention" error in the net
command.
I started another install on top of c:\uwin2.
This netted:
---------------------------ksh.exe - Application
Error---------------------------The application failed to initialize properly
(0xc0000005). Click on OK to terminate the application.
---------------------------OK ---------------------------
There are no debugging symbols in ksh, andI haven't yet built my own, so I
didn't debug this.
This error occured twice.
Then it complained of inability to stop all uwin processes.When the AV popup
was up, I did run another ksh under a debugger, to see if there were any
symbols, but I'm not sure these things coincided.
I can get uwin installed and working ok.But these are bugs.
(I had found the assertion that buildingfrom source required a binary
distribution first,and was going to try installing to \uwinboot
andbuilding/installing to \uwin. I think I won't now.)
- Jay
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: non specific errors from uwin
setupDate: Fri, 11 Apr 2008 06:08:01 +0000
I installed uwin-base on two machines running XP.On both I installed to
c:\uwin.I don't like "program files" -- too long and a space....
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
