🚀 go-pugleaf

In article <50dik5$1td6@news-s01.ny.us.ibm.net>,
Duane A. Chamblee <duanec@ibm.net> wrote:
>os2-l@mistik.express.net (Mustafa Soysal MS57) wrote:
>
>>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?
>
>Please try to "hack" it.

Thanks to all who had helpful hints.  I followed them, yet it seems that
win32s simply isn't possible to run under OS/2.  I got as far as
following the instructions in the _msstart.bat manually.

I got to start PhotoWorks, however, I get an error message that win32s
needs to be reinstalled since some files seem corrupt...At best, I get a
message that says it needs to find w32s.386 which I have already copied
to various places <G>

In the process, I replaced the winmm16.dll and w32sys.dll as well.  I
don't know what effect it has, but HPFS seems to have sped up <G>.  I
guess it is still using some undocumented windows calls <G>....

>
>I know that MS Office leaves a file called _MSSTART.BAT/EXE in the Windows
>directory when it needs a "reboot" to complete.
>
>The main problem with win32s 1.30 under OS/2 is that the memory scheme in 1.30
>pushes memory past the DOS limit, breaking it under WinOS/2's virtual DOS
>session.
>
>Good luck.
>

Thanks, but no cigar.  I asked Seattle FilmWorks to send me the DOS
version.  I also e-mailed a sample picture to the authors of PMJPEG.

Again, thanks to all responses, the hacks have been much easier.

I did the following hacks.

1. After starting the program manager in enhanced version, I renamed
   winos2.com into xwinos2.com <G>

2. I started the installation from the program manager menu "Run" which
   copies files into a directory, and then calls mssetup.

3. Since the setup program is impossible to exit without shutting down
   OS/2, I did just that, after adding the additional win32s directory
   into the paths where winos2 had appeared only by itself.

4. Of course, I renamed xwinos2 into winos2 to stat the program manager,
   and then renamed it onto xwinos2 again.

5. In another attempt I did all of the above and edited win32s.ini and
   changed setup=0 for PhotoWorks and did the install again (FilmWorks
   recommendaton)

6. I gave up in frustration, however, smiled when I noticed that my
   system seemed to be running slightly faster.  At least, it wasn't for
   nothing....

7. Yet, had to conclude that I need to dump IBM before IBM dumps OS/2.

Best regards,

Mustafa Soysal

--
-------------------------------------------------------------------------------
Mustafa Soysal               (313) 741-1844 Voice                      TeamOS/2
MISTIK Systems               (313) 741-1937 Fax          Author of UnTieCom(tm)
PO Box 7064                              Authorised Motorola and ZyXEL Reseller
Ann Arbor, MI 48107-7064, USA                          os2-l@mistik.express.net
                  http://www.express.net/mistik/pricelist.html
-------------------------------------------------------------------------------