🚀 go-pugleaf

In message <3228af3d.4d495354494b@mistik.express.net> -
os2-l@mistik.express.net (Mustafa Soysal MS57)Sat, 31 Aug 1996
17:31:41 -0400 writes:
:>
:>I think the win32s thing is the key, since that application
:>(http://www.filmworks.com/) will also choke on the win32s.
:>
:>I am wondering if this can be solved by simply setting the path or dpath
:>variables differently.  It seemed that win32s.386 could not be found.
:>
:>Seattle Filworks gave me a workaround since the windows installation
:>program was refusing to set it up under WinOS2, but they didn't have
:>anything further.  When I get to start the program by fiddling with
:>default directories etc, I can still get the system to tell me that
:>win32s was not installed properly.  Basically, the reboot part of the
:>installation is missing, and it could be that the last step of the
:>installation was not done.  Any hacks?
:>
:>
<Snipped older post>

It sounds like you are trying to install it in Win-OS/2.  A lot of
Windows programs seem to require a restart of Windows after install. 
Have you tried installing this program under Real Windows (not
Win-OS/2) and then migrating it to the desktop?

At least if you know it has installed correctly and runs properly
under Real Windows then you'll know the problems under Win-OS/2 don't
involve the installation itself, only the running of the program.

Same for installing the Win32s software itself.

Richard Person
richbp@ix.netcom.com