Home
Web Hosting
Web Design
Reseller
Support
Payments
Signup
Contact Us
Our Online Support Manual is updated monthly to reflect new changes in service and procedure.

Please Send E-mail if you need personalized support or in the case of an emergency please call 202-517-9106.

We appreciate your business and are here to address all of your concerns.


Uploading Files

Once you receive your Web Hosting information that contains your IP address, username, and password, you are ready to start uploading files into your account. There are a number of FTP programs on the market that can be used to upload your files, but we suggest using WS_FTP for the PC and Fetch for the Mac. When using any type of FTP program there are three key things to keep in mind when connecting to your account.

  1. Your host name would be your IP address or domain name
  2. Your username is the username we provided in the Web Hosting IP e-mail that we sent you.
  3. Your password is the password we provided in the Web Hosting IP e-mail that we sent you.

Keep in mind no matter what FTP program you may be using, these three above items are needed to connect to your account.

Below are screen shot examples of how WS_FTP  would look if you were to use it.

WS_FTP

This is what the initial login screen would look like.

Note to Microsoft FrontPage Users
Customers with  FrontPage extensions installed on their site should use only the FrontPage publishing feature to transfer files. Using regular FTP can corrupt the extensions, disabling the functionality of the FrontPage web and requiring that the site be deleted to reinstall the extensions. (See Below)


Back to Main Top


Microsoft FrontPage

Customers with  FrontPage extensions installed on their site should use only the FrontPage publishing feature to transfer files. Using regular FTP can corrupt the extensions, disabling the functionality of the FrontPage web and requiring that the site be deleted to reinstall the extensions.

Click the publish button in the upper left-hand corner of your FrontPage Explorer.  A screen like below should appear.   You need to type in your domain name or IP address then click OK.  All that is left to do is enter your username and password.

Front Page Visual


Back to Main Top


Setting CGI Scripts

To start, 90% of your form processing needs can be solved by MailForm.exe, which requires no CGI programming.

MailForm.exe is located in you cgi-bin.

If there are any questions about specific scripts that you wish to use,
Send E-mail.



Back to Main Top



MailForm Features

MailForm.exe allows you to create sophisticated forms without CGI scripting.

To use MailForm.exe, create a form with any decent web page creation software.

All MailForm configuration fields begin with an underscore character, a number, and then another underscore (eg _1_). This identifies them as a MailForm field, and the number is a code used to identify the particular type of field.

Currently there are five different type of MailForm fields:

    _1_    System field
    _2_    Ignore field
    _3_    Credit card number field
    _4_    Required field
    _5_    Email field

The form action line should be:

<form ACTION="/cgi-bin/mailform.exe" METHOD="POST" NAME="signup">
<input type="hidden" name="_1_mailto" value="you@yourcompany.com">
<input type="hidden" name="_1_mailfrom" value="signup@bis-inet.com"><input type="hidden" name="_1_MailServer" value="mail.yourcompany.com"><input type="hidden" name="_1_MailSubject" value="Sales Order Form">

MailForm.exe will do all the programming work for you. You alter the behavior of MailForm by using hidden fields in your form or by using a configuration file called mailform.ini.

The System fields are as follows:

_1_MailTo :The address to email the results to

_1_MailServer :The address of the SMTP mail server (eg mail.company.com)

_1_MailSubject :The subject line of the email

_1_MailFrom : The address email is to "come from" (can be any valid address)

_1_CCMailFrom : The email is also sent to the address in the MailFrom field

_1_SuccessDocument : URL to return if the operation succeeds

_1_FailureDocument :  URL to return if the operation fails

_1_InvalidCardDocument :  URL to return for an invalid credit card number

_1_RequiredFieldDocument : URL to return if a required field is missing

_1_CardNotAcceptedDocument : URL to return for a credit card that's not accepted

_1_InvalidEmailDocument : URL to return for an invalid email address

_1_NoHotmailDocument : URL to return for a "hotmail" email address

_1_BadRefererDocument : URL to return when the form is "referred" by an invalid host

_1_SortFields : Set this field to cause fields to be sorted in the email

_1_TextLog : Set this to log all form submissions to a text file

_1_HTMLLog : Set this to log all form submissions to an HTML file

_1_CommaDelimitedLog : Set this to log all form submissions to a comma-delimited text file

_1_StripEmptyFields : Set this to cause empty fields to be removed

_1_AcceptedCards :  Set this to specify the credit cards accepted

_1_NoHotmail : Set this to reject "hotmail" addresses

_1_MailTemplate : Specifies a template to generate the message with

_1_INIFile : Specifies an alternative ini file to use

_1_MailIntro : Sets the email introduction line (header)

_1_AcceptEmptyCardField : Will accept an empty _3_ field as valid

_1_ConditionalSuccessDocument : Conditionally redirect to a different document on success

MailForm also has the option of an external configuration file. This file must be called mailform.ini, and placed in the cgi-bin directory along with the mailform.exe program.

Currently the mailform.ini file consists of a single section, Settings, with several optional parameters (the values given for each parameter below are just examples):

[Settings]
MailIntro=Submitted at %1 from %2
MailServer=mail.company.com
MailTo=me@company.com
SuccessDocument=http://www.company.com/success.htm
FailureDocument=http://www.company.com/failure.htm
InvalidCardDocument=http://www.company.com/badcard.htm
RequiredFieldDocument=http://www.company.com/required.htm
CardNotAcceptedDocument=http://www.company.com/wrongcard.htm
InvalidEmailDocument=http://www.company.com/bademail.htm
NoHotmailDocument=http://www.company.com/bademail.htm
FooterMessage=\n\nThis is a custom footer message!
TextLog=c:\logs\formslog.txt
HTMLLog=c:\logs\formslog.htm
CommaLog=c:\logs\commalog.txt
Status=303
RefererCheck=company.com

The MailIntro parameter allows you to change the introduction line of mail messages that MailForm sends. Use %1, %2, etc, to insert information about the current message.

The codes available are:

    %1    Date & Time
    %2    Remote address
    %3    Remote user
    %4    HTTP agent (ie the user's Browser)

The MailServer parameter allows you to configure a global mail server for use with MailForm. If the _1_MailServer line is not given in the form, the value supplied here will be used as a default. You may want to use this if you don't want to make the address of your mail server known publicly.



Back to Main Top


Secure Socket Layers

How do I call web pages securely using your Thawte certificate?

All pages that reside in your secure_html directory are secure if you call them the following way:
https://secure.bis-inet.com/your_domain/file.name

1.The https://secure.bis-inet.com is the name of the server that your web site is hosted on (email support@bishosting.com if you don't know the name of the server your on).
2.The /your_domain/ is the name of your domain without the .com, .net, etc.
3.The file.name is the name of the file you are calling.

Executing CGI Scripts under a secure connection

There is one way to execute CGI scripts under a secure connection. Your local cgi-bin which requires the Support Dept. to enable that feature.

Using your local cgi-bin your path would look like this:
https://bishosting.com/your_domain/cgi-bin/file.name

Remember if you need your secure server name or need your secure cgi-bin enabled email support@bishosting.com

Back to Main Top


Home Page | Web Hosting
Web Design | Resellers  | Support
Payments | Sign Up | Contact Us


1999 Business InterNet Systems, Inc.