Re: IE dialer hassles

Josh Hillman ( (no email) )
Fri, 27 Jun 1997 13:33:48 -0400

Ted, are you using MS IEAK to create your MSIE installation disks? If so,
there might be something wrong in there.

For our Windows 3.1x users, we use MSIE 3.02a Full-install (4-3.5" disks)
and it works 100% of the time (so long as the user doesn't have an RPI or
some other non-cooperative piece of junk modem). Every once in a while,
we'll come across some error about an environment variable not being loaded
in autoexec.bat, but that's easily fixed by moving anything with
"c:\iexplore" in it to an area in autoexec.bat after the PATH statement and
before loading any other batch files, as well as the "win" line. Sometimes
MSIE puts a few lines at the very beginning of autoexec.bat and so long as
those lines are moved, everything works fine.

Josh Hillman

> From: Ted Olson <>
> We're trying to implement the IE Dialer as a replacement for Trumpet on
> subscriber Win 3.1 platforms. Been running preliminary in-house
> installation and configuration testing with very mixed and random
> such as:
> 1. After creating (and saving!) a new connection profile, double-clicking
> on the new icon brings up a blank properties tab ... no name, password,
> dial-up number. Type it all in again, save it, same thing. Only a manual
> edit of the .con file solves this.
> 2. Or, we create a new connection profile, double-click on the new icon,
> and it brings up another "create a new connection" dialog tab ... problem
> is that the .con file name was not appended to iedial.exe on the command
> line in icon properties, so we have to add it manually.
> 3. Or, when fine tuning the additional properties of a working connection
> profile (such as start IE automatically, minimize on connect, display
> terminal window, etc) -- then close and save, but they don't "stay
> only solution is to edit the .con file manually.
> These problems are occuring randomly with both the 2.0 and 3.0 versions,
> different machines with no pattern we've been able to recognize yet. We
> obviously don't want to package this for subscribers until these bugs(?)
> are solved ... anyone have ideas or suggestions?
> Thanks much,
> -Ted
> ---------------------------------------------------------------------
> Ted Olson President, System Manager OCSNet
> Olson Computer Services
> OCS Software, Inc.
> Phone 209.781.4123 Fax 209.781.3718 Porterville, CA USA
> ---------------------------------------------------------------------
> ----------------------------------------------------------
> NTISP Mailing List