|
Knowledgebase
|
|
 |
Part Six
- Real
Audio/Real Video
- Microsoft
Front Page Extensions
- Additional
Users on your Domain
Real
Audio/Real Video
Real
Audio is a real time audio transmission/player system. A digital audio
stream is transmitted from the server over the Internet to the destination
and played immediately, rather than being stored to disk first and
then played.
You
can stream Real Audio/Video through http stream as opposed to using
a Real Server. This is the method we use to stream Real files.
Each
audio clip requires two files: a metafile with extension .ram, and
the digital audio clip itself, with extension .ra.
The
.ram file holds one or more lines of ASCII text, each of which references
the .ra file to be played when the .ram file is accessed by the
browser.
Real
Audio/Video FAQ
Some
basic questions about running Real Audio/Video files on our servers.
(1)
You do not have the RealServer software running on your servers.
Will we be able to stream RealMedia files?
Yes,
you will be able to stream RealMedia files. You will need to create
a .ram file that calls your real audio/video file. The .ram file
is a text file with an absolute URL. This URL will need to be:
http://full.domain.name/directory/filename.rm
(2)
Is there a difference between streaming using the PNM-protocol and
the HTTP-protocol?
If
you visit http://www.real.com/, you might come across a term called
"pseudo-streaming". According to audiohost.com:
"Pseudo-streaming"
is a discriminating name for HTTP-stream. It was invented by the
RealAudio promotion to suggest that you need to use the RealAudio
server if you want to get "real" streaming. Here's a free
translation: "Streaming RealAudio files without using RealAudio
server software". That's all there is to it! The RealAudio
server actually has some special features that cannot be achieved
(in RealAudio) without it. Regarding "streaming" we cannot
find a difference between the two protocols.
(3) What are some of the special features of the RealServer?
With
the Real Server, you are able to take advantage of "bandwidth
negotiation". This feature takes into account the bandwidth
of the surfer's Internet connection when clicking on the hyperlink
that requests the RealMedia file. Depending on the connection, the
RealServer will provide a different version of the RealMedia file
that best suits the visitor's bandwidth connection. You also need
the RealServer to broadcast live on the Internet.
(4) How do I get around not having "bandwidth negotiation"?
While
encoding, if you set the target audience to 28 K modem, you will
be able to reach the largest audience possible. If you want your
higher bandwidth connection visitors to receive better quality recordings,
you can always create a second link to a RealMedia file that is
encoded with a target audience of a higher bandwidth connection.
What is the Correct Path for Real Audio/Video?
Typically
you'll create a realaudio file subdirectory under domain-www, and
put all your audiofiles there.
Then
your .ram file, a.k.a., metafile, will contain an address with this
format:
http://fulldomainname/subdirectory/filename.rm
The
"subdirectory" is a subdirectory of your domain-www directory.
So
for example:
http://musicforyou.com/ra/music.rm
Notice:
The above address goes in the .ram/metafile, not in your HTML code.
Your HTML code calls the .ram/metafile. Then the .ram/metafile is
used to call up the .rm/realmedia file. So for example, your HTML
code would look something like this:
<a
href="http://musicforyou.com/ra/music.ram">Click here
to listen to music.</a>
Microsoft
Front Page Extensions
Publishing
a Web
After you have built your html documents and are ready to upload
them to our server:
1.
Open the web you've created on your PC using FP Explorer.
2. Choose File > Publish
3. If your "Destination Web Server" doesn't appear in the Publish
window (it won't the first time you publish to our server)
CHOOSE "More Webs" and type the location of the web to publish to.
Hit return.
IMPORTANT: Use www.yourdomain.com as the Destination Web
Server to publish to our server.
Leave the "Destination Web Name" BLANK.
4. You will be asked for your USERNAME and PASSWORD. This is your
domain's
USERNAME and your FrontPage PASSWORD (which may be different than
your regular telnet/ftp/POP password). If you're not sure what it
is or if you aren't allowed past this point, you'll need to contact
us for a new FP password.
5. You can watch the progression of the upload by looking at the
bottom left corner of FP
Explorer.
Opening
an Existing Web
1.
Open FP Explorer and choose File > Open Front Page Web.
2. You can now choose to open a previously created web on your PC
or your web on our server.
3. Highlight the appropriate web or type in the web address (www.yourdomain.com)
and click OK.
4. Enter your USERNAME and FP PASSWORD if required.
5. Make modifications and recalculate links if needed. (See
FP help docs for info on when it's neccessary to recalculate links.
Troubleshooting Common Problems with FP98/2000
Getting
error - "Root Web Busy"
FTP or telnet to your site and remove the "service.lck" file in
/www/_vti_pvt. This usually happens when an FP session is
interrupted before completion.
Server
timing out when publishing large sites.
This difficulty arises when the uploading link times out in the
process of copying the web to our server. The only suggestion
Microsoft has offered so far is to break the main web into a group
of sub webs on your PC, then upload these individually. If
this problem persists for you, please contact support.
Getting
Error - "Front Page Extensions not Installed"
We often see this error being reported even when the extensions
have been installed. If you get this error, please contact
support and we'll make sure the extensions are installed and repair
them if necessary.
NOTE: The extensions are easily corrupted. Please use
only FP Explorer to update your web site on the server, not FTP.
I
published but my web's not there!
This will happen when the "Destination Web Name" is filled in when
publishing to our server.
This box should be left blank. If you put any other name in
this box it will create a subdirectory off of your root web and
copy all of your files into it. Your site will exist under
a subdirectory instead of at the top level /www where it should
be.
My
counter, bbs, guestbook, etc isn't working.
These problems are generally due to incorrect permissions on either
the directory, file(s) or cgi script(s) that are associated with
them. Please don't change the permissions of your files or
directories unless you have a specific reason for doing so and you
know what effect it will have on your site.
My
forms won't work through the Secure Server.
The call to a cgi script using the Secure Server
must not be within a webbot. Use a normal cgi call in your
html script for Secure Server calls.
My
search bot doesn't return any results.
The /public_html directory must be world readable AND you need to
recalculate links BEFORE publishing (or after editing directly on
the server). If it still doesn't work: FTP to
the server and go to the /public_html/_vti_txt/default.wti directory.
Delete any files that begin with "ALL.". Don't delete any
other files. Then using Windows Explorer, do the same thing
on your PC. Recalculate links, test locally with your browser
and publish.
FP
starts the Web Publishing Wizard when I try to publish.
Cancel the operation and contact support to have the FP extensions
installed/repaired.
Why
is my page renamed on the server when I publish?
The "Default Document" of your web is automatically renamed by the
server to what is required by the configuration of the server.
For example, if you've named the main page "index.html", it may
be renamed "default.html". Just check the links to your main
page to make sure they
refer to it the same way.
NOTE:
If you are using
FrontPage, you should NEVER use regular FTP to upload your files.
This will damage the extensions. Stick with one or the other all
the time.
Notes:
FP 2000 deletes the server secure control panel when uploading files
to my root web.
How do I stop this?
Answer:
When you're uploading in "mirror" mode, FP will sync your DocumentRoot
with your local web site.
Make sure to select "Upload Changed Files only", so that it doesn't
attempt to destroy the contents of
the DocumentRoot before uploading.
Would
I have any problems after I install the Frontpage extensions?
Answer:
Note
that some people report that the Front Page 2000 client will delete
any files it did not
create itself. Also, in some cases FP2000 will refuse to upload
if it cannot change permissions
on
any files in the web directories. You will need to modify the ownership
and/or permissions of
those files to allow Front Page to do so.
Additional
Users on your Domain
If you have asked for
additional POP/FTP/Telnet accesses on your domain, the users of these
additional accounts can access the server via FTP, Telnet, and Email
with the following parameters:
Hostname: yourdomain.com
Username: their unique
username
Password: their unique
password
POP Account: their
unique username@yourdomain.com
SMTP Server: yourdomain.com
When they login
via FTP or Telnet, they will be taken to their directory, where
they will see their own www directory
Note: If you can
access your control panel, you should not use these addresses,
instead, use the support form in your control panel. This makes
support much easier and includes information we need to process your
request.
If you can not access your site or your control panel,
and need support use the link below:
-Open a trouble ticket using email to:
support@scorpionsystems.net
Make sure to include:
-Your Domain Name
-Username
-Problem you are having
-Address we can reply to
-Control panel password to verify your account
(important!)
Before you e-mail support,
it is a good idea to consider that if a problem is server or network
wide, we know about it. We have several systems montioring our servers
and they notify us when there is a problem.
Note: We do not offer telephone support at this time.
|
.
