TIP: Click on subject to list as thread! ANSI
echo: os2dos
to: CORIDON HENSHAW
from: BOB WRIGHT
date: 1997-10-23 19:07:00
subject: Win32s?

 Coridon Henshaw hastily said to Andrew Leary:
 CH>>> I've got a wierd problem with Win32s under Warp 4.  With both 1.20
 CH>>> and 1.25a, any attept to run a Win32s program results in a Windows
 CH>>> dialog box complaining that some component of 'the system' is of a
 CH>>> previous version.  It does not, however, tell me which component.
 AL>> Does the program require 1.30?  If so, you're out of luck for the
 AL>> moment.
 CH> Freecell does this...
Not surprising, given the source.. :)
However, I recall there having been a thread here a year or so ago dealing 
with a way to trick Windows into thinking it had 1.3.   If my memory hasn't 
completely deserted me...
I think the trick was to save the ver 1.25 dll's and such, then install 1.30, 
then replace all the dll's with the 1.25 ones.  This left the ini's reporting 
ver 1.30, and Windows was satisfied.  (Seems that the only difference was 
that 1.30 allowed a *HUGE* address that WinOS/2 choked on... --- someone,,, 
anyone,, correct me if I'm wrong here .... please  ).
        -- Bob
--- GoldED 2.41
---------------
* Origin: Merlin's Tower - Surrey, BC (1:153/944)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.