🚀 go-pugleaf

Either Envlop has a problem with networks (or possibly just CLient32
and DUN) or I've just had bad luck. In case it is the former, I
thought I'd post this Envlop warning.

I read a blurb in Byte Magazine about Envelop, a freeware visual
programming environment for Win95/NT available from
http://www.envelop.com. I downloaded the 6.5Mb and installed it on my
home 8Mb P75 (no network). If would not run after the install (not
enough resources, I suppose), but politely uninstalled and did no
damage.

I tried installing envlop on my 16Mb P75 at the office, which is
connected to the LAN with Novell's Client32c. The installation asked
for a reboot, which I kindly did. On reboot, the Client32 spash screen
came up, then the login box. Problem is, there are now no fields in
which to type my login name and password. The OK button is greyed out.
X works, however, so I pushed it and W95 loaded normally, though with
no network connections (of course).

I was able to login from a DOS prompt under W95 and then some network
resources became available. After login at the DOS prompt, I saw
"Warning: Unexpected error 9 (ffff)" Unexpected? I'll say.

I use Microsoft's DUN to connect to our ISP. I've been leaving the ISP
password in the DUN connect box. After this fiasco, the password is
gone and I no longer have available the clickbox  to save the password
(the checkbox is greyed out).

I wonder what else Envelop has changed/corrupted in this machine.

I am not looking forward to rebuilding this computer from a backup
just because of Envelop. Be warned - if you must try Envelop, make a
backup (or two) immediately prior. Then think about whether you really
want the headache after all.