🚀 go-pugleaf

In article <3oarqb$mue@news.iastate.edu>, barisax@iastate.edu says...
>
>This is a cry for help to anyone who has seen this problem before. For
>no apparent reason, one of my clients has lost the ability to run any of
>his windows applications. Whenever he tries to launch a windows based
>application, or a win-os2 window or full screen session, the hard drive
>is accessed for about a half second, and then nothing. The apps will not
>run from the launchpad, or from their original icons. They will not run
>from an os2 command line or a dos command line. I have tried the
>following, unsuccessfully, to resolve the problem:
>        * re-migrate the applications to the desktop
>        * check settings on the apps AND the win-os2 sessions
>        * reboot
>        * re-install win-os2 support (and remigrate again)
>        * run chkdsk
>        * boot from a desktop archive
>I do not know if the client removed anything that should not have been.
>I checked all of the os2 and windows system files that I could think of
>and found no problems there. I have not ruled out a hardware problem, as
>he has had trouble with it in the past. (His keyboard died, and it
>needed to be replaced) Here is the system:
>        HP Vectra 5/60 (60 MHz Pentium)
>        16Mb RAM
>        540Mb Hard Drive
>        SVGA Monitor (Ergo Ultra, uses cirrus logic drivers)
>
>If anyone has *any* idea what the problem might be, I would be eternally
>greatful. If any other information about the system is required, I will
>post here. 
>

You didn't say whether you had plain warp or fullpack.  I have
the latter & this bug has been around since 2.1 GA.  When
you click on the icon, Winos2 attempts to load & then quits.

On some advice I got somewhere, I bleeped off all the windows 
folders/pgms & re-installed winos2 from the CD.  Rather than
migrate win pgms, using a program template, I directly set up 
a seamless session to start winfile (file manager). For some 
reason on my system, certain small windows pgms such filemanager
& write in the winos2 directory start just fine in seamless this way.
Once winos2 starts, other seamless pgms, e.g., MS word, excel etc., 
on other paths start o.k.   

N.B. some of the big win pgms may have to be re-installed in a
full screen winos2 session to work properly in seamless.
 
If this works, tune-up the session notebook settings for winfile 
& make a seamless template for installing other win pgms you want
to run in a seamless session.  

Fastload should have the same effect, but I find it's more convenient
to put winfile in the startup folder & start it minimized using
the minrun utility that lurks somewhere on the ftp sites.
If you have access to windows for workgroups 3.11, patch in the
winfile from wfwg 3.11 over win 3.1 /winos2.  Works fine & is 
much more useful.

Whether this work-around is good on any other systems, I can't
say, but it works for a few people.

I've seen this bug reported many times.  IBM should have fixed it
long ago.

Otherwise keep the heat on IBM to fix this thing.

-bb

-- 
Byron Bodo     240 Markham St.        tel: (416) 967 7286
|>    |>       Toronto, ON            fax: (416) 967 9004
|>    |>       Canada  M6J 2G6        email: bodo@io.org