Author Topic: Webshield tutorial  (Read 2578 times)

0 Members and 1 Guest are viewing this topic.

RF

  • Guest
Webshield tutorial
« on: July 22, 2007, 06:24:27 AM »
Hi -
I don't use Win98se anymore but I wanted to point out that the tutorial for setting up webshield for IE, while technically not in error, could easily be misconstrued. In the port box, what the tutorial says to do is to type in 12080. The animation does in fact do this but then the "1" mysteriously drops out, leaving 2080 as the final number. Firefox, on the other hand, gets it right.

http://www.avast.com/files/tutorials/ws_ieproxy.htm

Now that worldwide use of Windows 98 is down to about 17 people perhaps it doesn't matter much, but I thought I'd point it out.

Regards,
Roger

Offline lukor

  • Administrator
  • Super Poster
  • ***
  • Posts: 1884
    • AVAST Software
Re: Webshield tutorial
« Reply #1 on: July 22, 2007, 09:28:35 AM »
Yes. I agree it is really a great mystery where the number of "1" is hidden. Do you have any suggestion how this may be fixed in the tutorial?


Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: Webshield tutorial
« Reply #2 on: July 22, 2007, 09:49:39 AM »
The tutorial was created by really recording the actual screens.
So, this is how it looked on our Win98 installation (the box is probably too small to house 5 digits).

I guess it depends on the screen resolution.


Thanks
Vlk
If at first you don't succeed, then skydiving's not for you.

Offline oldman

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 4142
  • Some days..... MOS...this bug's for you
Re: Webshield tutorial
« Reply #3 on: July 22, 2007, 10:25:43 AM »
Maybe. It shows up at 800x600

RF

  • Guest
Re: Webshield tutorial
« Reply #4 on: July 22, 2007, 05:04:07 PM »
One possibilty is to (alas) redo the IE tutorial using a smaller font for inserting the typed information. The font size is a function of the browser settings, which may explain why there was no problem in Firefox.