Category : Printer + Display Graphics
Archive   : VIDVUE24.ZIP
Filename : README.WRI

 
Output of file : README.WRI contained in archive : VIDVUE24.ZIP
1¾«£DOOOOOPShareware Distribution
If your disk(s) contains VIDVUE24.ZIP; feel free to copy and distribute it, unmodified. You can
also copy and distribute your registered disk(s) set as long as you DELETE the TECHSUPP.TXT
file (only registered users get telephone support) and do not disclose your Personal S/N.

DEMO.TXT: Slideshow Example
In your VIDVUE app directory is a text file - DEMO.TXT. This file shows you how to write a
multimedia slideshow script. Simply change the "FILENAME=" keyword to equivalent files in
your own drive/directory then save the text file with a *.SHO extension (eg., DEMO.SHO).
See VIDVUE.HLP file for details on how to write user-scripted slideshows.

Diagnosing MCI Installation in Windows
If you get MCI driver errors when loading AVI, WAV, MID or FLI files, you may have a parameter
missing from your SYSTEM.INI or WIN.INI file. Ensure that you have installed the MCI drivers by
using the Media Player to verify successful installation.

If you downloaded NEWPLA.ZIP (from GO ASOFT or a BBS) or WAPLAY.EXE (from
GO GRAPHSUP at CIS) instead of AAWIN11.ZIP (or higher) to play FLI/FLC animation files, you
may get MCI errors with VIDVUE, since original setup program is not included.

Copy SYSTEM.INI and WIN.INI to *.BAK; this way you can undo changes. Enter items that
DO NOT EXIST in each of the INI files with a text editor. Close and restart Windows.

Entries in SYSTEM.INI file:

[mci]
WaveAudio=mciwave.drv
Sequencer=mciseq.drv
AVIVideo=mciavi.drv
Animation1=mciaap.drv

[drivers]
midimapper=midimap.drv
VIDC.MSVC=msvidc.drv
VIDC.RT21=indeo.drv

Entries in WIN.INI file:

[mci extensions]
wav=waveaudio
mid=sequencer
rmi=sequencer
avi=AVIVideo
fli=Animation1
flc=Animation1

VIDVUE.INI and MCI Initialization
Due to the way different systems react to MCI device initialialization; VIDVUE now includes
every possible combination for MCI devices initialization. If the the default routines still result
in an MCI error loading AVI, WAV, MID or FLI files, after

1. verifying that all relevant entries are in SYSTEM.INI or WIN.INI file
2. and Media Player plays the files,

then you can use a text editor to add/modify the following entries in the VIDVUE.INI file.

AUDINIT=n
AAAINIT=n
VIDINIT=n

where n=1,2 or 3

"AUDINIT=" modifies WAV and MID initialization.
"AAAINIT=" modifies FLI and FLC initialization.
"VIDINIT=" modifies AVI initialization.

If you have problems loading WAV and MID files, experiment by adding:
AUDINIT=1
or
AUDINIT=2
or
AUDINIT=3
restart Windows, run VIDVUE and play your WAV or MID file to see if it loads correctly.

If you have problems loading FLI and FLC files, experiment by adding:
AAAINIT=1
or
AAAINIT=2
or
AAAINIT=3
restart Windows, run VIDVUE and play your FLI or FLC file to see if it loads correctly.

If you have problems loading AVI files, experiment by adding:
VIDINIT=1
or
VIDINIT=2
or
VIDINIT=3
restart Windows, run VIDVUE and play your AVI file to see if it loads correctly.

Apple QuickTime for Windows (QTW) Runtime
To run *.MOV (Apple QTW MOVie) files, installed MCI drivers for Windows are required.
To check if the drivers are installed, use the Media Player accessory to play *.MOV files;
if you can play *.MOV files via Media Player then VIDVUE can too.

If you purchased and are currently using any of the following products:

Adobe Premiere 1.0 (or later) for Windows
Macromedia Action 2.5 (or later) for Windows
Macromedia Authorware Pro 2.0 (or later) for Windows

then you probably have installed MCI drivers for MOV playback; verify proper
MCI installation via Media Player.

If you don't have the Quicktime for Windows drivers, then CompuServe subscribers can:

1. GO MACDEV.
2. Download LICENS.TXT from Library 8.
3. Read and abide to terms and conditions in LICENS.TXT.
4. If you agree to LICENS.TXT, then download QTDSK1.ZIP and QTDSK2.ZIP.

Note: QTDSK1.ZIP and QTDSK2.ZIP are NOT distributable files.
Only YOU can download and use them (see LICENS.TXT).
READ THE README.WRI FILE IN QTDSK1.ZIP.

5. Extract QTDSK1.ZIP to a blank, formatted 1.44 MB disk.

Example:

If you dowloaded the *.ZIP files to d:\CSERVE\DOWNLOAD then

a - Insert your blank, formatted 1.44 disk in Drive A:
b - in DOS, type "A:" to goto Drive A:
c - Type "PKUNZIP -d d:\cserve\download\QTDSK1.ZIP"
to extract files to directories.

6. Extract QTDSK2.ZIP to another blank, formatted 1.44 MB disk.
7. Insert DISK1, run Windows and run SETUP.

Note: If for some strange reason SETUP cannot find DISK2 when it requests it,
rename the DISK2 directory on DISK2 to "DISK1" then reinstall. You may
have to use a utility like Norton or PCtools to do this.

If you are not yet a CompuServe subscriber, but have a CDROM and several CDROM titles,
you may already have the QTW runtime files BUT may not be setup for MCI playback.

1. Copy all QTW runtime files to your \windows\system directory.
The QTW files are usually placed in a separate directory; you must have:

MCIQTW.DRV, MCIQTENU.DLL, QTIMCMGR.DLL, QTIM.DLL
QTOLE.DLL, QTHNDLR.DLL, QTVHDW.DLL, QTNOTIFY.EXE
PLAYENU.DLL, VIEWENU.DLL, and several *.QTC files

Note: Since YOU purchased the book w/ a CDROM or CDROM title, only YOU are
licensed to use the QTW runtime files on ONE/YOUR single computer.
YOU CANNOT DISTRIBUTE THE QTW RUNTIME FILES OR COPY THEM TO
ADDITIONAL MACHINES/COMPUTERS OR SHARE THEM VIA NETWORKS
OR OTHER SHARED DEVICES.

2. Create a QTW.INI file and place it in your \windows directory and
add the following sections and entries.

[Options]
VideoOptimize=DIB

[Video]
Optimize=driver

[QuickTime for Windows]
Implementation=Full

3. Modify your SYSTEM.INI file; add under the [mci] section

QTWvideo=MCIQTW.DRV

4. Modify your WIN.INI file; add under the [mci extensions] section

MOV=QTWvideo

HiColor DDB (Device Dependent Bitmap) Frame Grabs
Since 32K or 64K color modes are the preferred modes for viewing video files, Video for
Windows 1.1 (or higher) and Apple Quicktime 1.1.1 (or higher) displays video as DDBs for
speed on 32K/64K color displays. DDBs are DEVICE DEPENDENT; thus, you have to tell
VIDVUE how to use them. A special entry in the VIDVUE.INI file tells VIDVUE how to
access DDBs. This is ONLY required if you want to grab video frames from AVI
or MOV video files on 32K/64K color displays. Run VIDVUE and select
"Help-System/Video Info". If "Bits/Pix=16" or "Bits/Pix=15" then this affects you.
Otherwise, skip this setup.

Using a text editor (eg., NOTEPAD), add the following entry to the VIDVUE.INI file:

HiColorGrab=RGB

where RGB=0 (will save to a 24-bit DIB; this is the default)
RGB=555 (will save to standard 32K HiColor DDB format)
RGB=565 (will save to an XGA-type DDB format)
RGB=655 (will save to a non-standard XGA-type DDB format
typically found with ATI cards)
RGB=664 (will save to a non-standard DDB format typically found with ATI cards)

If you have an ATI card, run the FlexDesk utility then click the Advanced button,
the "16 BPP RGB Mode" frame will tell you how you are currently setup.

If you have one of the newer Windows accelerator cards, try

HiColorGrab=565

most will typically default to this mode.

If "Help-System/Video Info" shows "Bits/Pix=15" then try.

HiColorGrab=555


If you don't know what RGB mode you are in, experiment with:

HiColorGrab=555
or
HiColorGrab=565
or
HiColorGrab=0

then restart VIDVUE and try to Grab a video frame; see VIDVUE.HLP if you don't know
how to grab video frames.
NS.TXT.
4. If you agree to LICENS.TXT, then download QTDSK1.ZIP and QTDSK2.ZIP.

Note: QTD€–w˜t²pÑl0h2dX`Z\WXYT%PbL b…wU s— o» kÈ gì cù _
[
Wi Sk O• K • — w÷s˜okEg»c'_f[}WÄSÔOK xrtàpÃlèhd$`T\^X…TPåL åïw6s:ok+g“c¬_ê[ÿWSOK 3w£s:ok+g“c¬_ê[ÿWSOK€˜ÿÿúÿÿWÿÿ²ÿÿ´ÿÿÑÿÿ.ÿÿŠÿÿäÿÿ0ÿÿ2ÿÿZÿÿºÿÿÿÿWÿÿYÿÿ¦ÿÿÿÿSÿÿUÿÿU­ÿÿÿÿÿÿ#ÿÿ%ÿÿ,ÿÿCÿÿYÿÿnÿÿ…ÿÿ‡ÿÿ’ÿÿªÿÿÀÿÿÕÿÿ×ÿÿñÿÿóÿÿÿÿÿÿ#ÿÿ2ÿÿ@ÿÿPÿÿ`ÿÿbÿÿ…ÿÿâÿÿHÿÿƒÿÿ…ÿÿÏÿÿõÿÿ÷ÿÿS ÿÿU ÿÿ` ÿÿk ÿÿv ÿÿx ÿÿx Š ÿÿŒ ÿÿ½ ÿÿî ÿÿ
ÿÿ
ÿÿ`
ÿÿk
ÿÿo
ÿÿz
ÿÿ~
ÿÿ‰
ÿÿâ
ÿÿä
ÿÿ+ ÿÿ6 ÿÿ: ÿÿE ÿÿI ÿÿT ÿÿT ­ ÿÿ¯ ÿÿî ÿÿù ÿÿý ÿÿ ÿÿ ÿÿ ÿÿi ÿÿk ÿÿ— ÿÿî ÿÿJ
ÿÿ
ÿÿ
ÿÿØ
ÿÿÚ
ÿÿÿÿ5ÿÿlÿÿlnÿÿ¼ÿÿàÿÿâÿÿ9ÿÿ;ÿÿJÿÿrÿÿ¬ÿÿõÿÿ÷ÿÿ5ÿÿlÿÿ–ÿÿ˜ÿÿÓÿÿÕÿÿâÿÿäÿÿ$ÿÿ$&ÿÿaÿÿ‘ÿÿÏÿÿøÿÿúÿÿ;ÿÿhÿÿjÿÿ¹ÿÿÿÿ>ÿÿ@ÿÿ˜ÿÿëÿÿíÿÿ/ÿÿ|ÿÿ~ÿÿ³ÿÿ³èÿÿÿÿ ÿÿlÿÿ±ÿÿïÿÿ*ÿÿEÿÿGÿÿÿÿ¹ÿÿ»ÿÿÆÿÿÙÿÿÛÿÿäÿÿõÿÿ÷ÿÿÿÿ%ÿÿ%'ÿÿdÿÿfÿÿ{ÿÿ}ÿÿÂÿÿÄÿÿÒÿÿÔÿÿÿÿ`ÿÿºÿÿÿÿdÿÿ³ÿÿùÿÿNÿÿlÿÿnÿÿÃÿÿÃÅÿÿØÿÿÚÿÿÿÿTÿÿ…ÿÿÁÿÿåÿÿ8ÿÿ:ÿÿÿÿÕÿÿ×ÿÿÿÿÿÿ)ÿÿ+ÿÿVÿÿXÿÿ“ÿÿ“•ÿÿ¨ÿÿªÿÿ¬ÿÿêÿÿìÿÿÿÿÿÿÿÿÿ ÿÿ1ÿÿ3ÿÿˆÿÿ£ÿÿ¥ÿÿ)ÿÿ+ÿÿVÿÿXÿÿ“ÿÿ Arial.1.1 (or higher) displays video as DDBs for
speed on 32K/64K color displays. DDBs are DEVICE DEPENDENT; thus, you

  3 Responses to “Category : Printer + Display Graphics
Archive   : VIDVUE24.ZIP
Filename : README.WRI

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/