[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference tnpubs::nscc

Title:NSCC
Moderator:TNPUBS::ICENOGLE
Created:Sat Jan 13 1996
Last Modified:Tue Jun 11 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:41
Total number of notes:140

29.0. "Multimedia Tools Activities" by TNPUBS::ICENOGLE (Kathy) Thu Jan 18 1996 11:29

This topic is reserved for info on what people
in the cost center are doing with, or learning
about using multimedia tools (eg. MultiMedia Viewer,
Asymmetrix Toolbook, MacroMind Director, 
Icon Author, DemoQuick, etc.)

If you are having trouble with a multimedia tool,
or for more info on multimedia development in general, 
you might be better off discussing the problem in either the 
PC Multimedia Development conference on XSTACY::PC_MULTIMEDIA, 
or in the CBT authoring conference on SPRITE::AUTHORING.
T.RTitleUserPersonal
Name
DateLines
29.1Converting MM Viewer files to WinHelp 4.0TNPUBS::ICENOGLEKathyThu Jan 18 1996 13:0526
From:	DEMON::DOWNING "Jack Downing DTN:227-3257  21-Dec-1995 0957" 21-DEC-1995 

Viewer to WinHelp 4.0 Conversion
--------------------------------
I've recently completed an evaluation of WinHelp 4.0 as the
target platform for people moving from Viewer 2.0. 

I met with the PATHWORKs writers who are writing tutorials using Viewer.
This group wants to move to WinHelp 4.0. The task of moving to
Viewer involves quite a bit of work. You really can't convert the
.MVP file to an .HPJ because many of the Viewer configuration macros
are unsuppoted.  Microsoft recommends a 5-step process:

	1. Update your macro references
	2. Update your multimedia references
	3. Convert the MVP to a new HPJ
	4. Create a contents file (if applicable)
	5. Build the new Help file

People needing to convert from Viewer to WinHelp 4.0 should read pages 
64-70 in the Help Author's Guide for Microsoft Windows 95 and Windows 
NT 3.51. This file is available from:

    DEMON::DEMON35:[shelf2.wn95help]winhelp.ps or winhelp.doc

-Jack
29.2Probs w/ Video for Windows on Win95TNPUBS::ICENOGLEKathyMon Feb 19 1996 17:315
See note 24.1 for info on problems people
are having with installing Video for Windows
on Win95.

Kathy
29.3More re: installing VFW on Win95TNPUBS::ICENOGLEKathyFri Mar 01 1996 14:1177
This is a follow up to messages you may have received about
Video for Windows 1.1e (VFW) causing problems on Windows 95.

Bottom line:

	The problems that people were attributing to installing VFW 
	on Win95 were due to having old video drivers.. *NOT* VFW. 

	However, since Win95 comes with a 32-bit version of VFW installed,
	you should still avoid installing anything called
	Video for Windows 1.1e (16-bit software) on your Win95 system... 
	or else you may experience problems in running *future*
	32-bit video applications.

DETAIL ABOUT THE PROBLEM:

As it turns out, the problems were NOT due to incompatibilities
between Video for Windows 1.1e and Windows 95... they were due
to some systems not having the most current video drivers.
Both Linda Marsh and the SES Cornerstone team have apparently
instaleld Video for Windows 1.1e on Win95 without any
*apparent* problems... 

However, you need to be aware that, installing Video for Windows 1.1e
on Windows 95 is:

	a) not necessary (Win95 comes with VFW installed)

	I have been able to run both the video portions of the 
	SES Cornerstone workbench, and a multimedia course called
	ABC's of Multimedia (both of which use VFW), without 
	installing VFW 1.1e... the version of VFW that was 
	installed with Win95 works fine.
	
	b) not recommended

	If you do install VFW 1.1e on your Win95
	system, you will be replacing your 32-bit version
	of VFW with an older 16-bit version of that software.
	Older 16-bit video applications will run, but you will
	probably experience problems if/when newer 32-bit video 
	applications come out.

HOW TO AVOID INSTALLING VFW 1.1e on Win95:

If, in the course of installing MM applications, you run across 
a message box that says it will be installing VFW1.1e, you can
use the following procedure to abort that installation:

1. Click OK on the message box (if it's your only choice).

	This will launch the SETUP.EXE for Video for Windows, 
	which will display a dialog box that asks if you want to 
	Continue or Exit the installation.
	
2. Click on Exit.

	Another message box displays to confirm the Exit.

3. Click on Exit again.

The files for whatever you were installing should be installed
and will run with the Video for Windows software that is already
on your PC.

TO ABORT THE INSTALLATION LESS GRACEFULLY:

When you see a message saying that Video for Windows is about
to be installed:

	1. Press CTRL-ALT-DELETE to display the Task dialog box.

	2. Select the task called SETUP (or possibly, INSTALL)

	3. Click on End Task.

	4. Confirm that you want to end the task.
29.4Input from MultiMedia group on Win95 problemsTNPUBS::ICENOGLEKathyWed Apr 17 1996 01:20146
From:	SUPER::DEMON::TARQUINIO "Paul Dyer Tarquinio  11-Apr-1996 1520"
11-APR-1996 16:58:21.89
To:	@IMM_FORUM
CC:	@BONNIE.DIS
Subj:	Update on recent PC problems encountered during MMCBT delivery

Hi,

This mail is a summary of the results and recommendations for
my recent testing regarding the following problems/isues:

1) MMTASK error   (when running CBIquick on certain systems)

2) MPLAYER error  (When running Microsoft RLE compressed AVI files)

3) Video for Windows 1.1 e problems on Windows 95

Contact me if you have any questions or if you have
any additional information to share.

Paul

---------------------------------------------------------------------

MMTASK error
------------

This error:  MMTASK error
     	     Details:  MMTASK error caused a general protection
     		       fault in module GDI.EXE

Occurrence:   On Windows 95 systems when running CBIquick software
     	      from IconAuthor courseware.

Side effects:  After occurrence of error, any AVI files will display
     	       error and will not run.  Rebooting system does not
     	       fix problem.

System Fix:	Reboot, install Video for Windows 1.1e.  All non CBIquick
     	        AVI files will run without problems.  CBIquick 
     		invocation will cause error again.

Test results:   On Celebris system where problem occurred, updating
     		to latest video drivers fixed problem.

     		On lab PC  (590 Pentium)  updating drivers did not fix	
     	        problem.  AMT.Corp.  indicated that other customers
     		have had this problem. They  have had success with
     		following recognition:

     		Under SETUP- system properties-Performance-Graphics, 
     		change Hardware acceleration from Full to None.
     		They have found this suggestion fixes problem on
     		all systems they encountered. ( This did not fix 590 system)

     		However, when I reinstalled Windows 95 to different directory
     		to create clean testbed for Windows 95, the Windows NT 
     		MMCBT course with CBIquick exercises ran fine with
     		no problems.  Since no other systems at TAY2 have
     		encountered this MMTASK error, I'm assuming there
     		is some unique problem with  the Windows 95 setup.
     		(I'm not planning to spend any  more time on this unless
     		 problem reoccurs.)

Recommendation: If problem occurs, check system for latest video drivers.  
     		Also try hardware acceleration modification.

MPlayer error
-------------

This error:  Mplayer error
     	     Details:  Mplayer error caused a general protection
     		       fault in module GDI.EXE

Occurrence:   On Windows 95 systems ( that have never installed Video for 
     	      Windows) when running  Microsoft RLE compressed
     	      AVI files.  This problem does not occur on Windows 3.1.
     	      NOTE:  RLE graphic files display with no problems.

System Fix:    After occurrence of error, any AVI files will display
     	       error and will not run.  Rebooting system clears up
     	       problem until you try invoking another Microsoft RLE AVI.

Test results:   This error occurred on DECpc LPx 560 (2 systems) and
     		on  Pentium 590  Windows 95 clean testbed. Testing 
     		indicates this error will occur on any system running 
     		Windows 95 that has not installed Video for Windows.

     		On these systems, properties function on the AVI file
     		indicates video format is unknown.  However in preview
     		option, file runs fine without errors.  Only when you
     		invoke file using double click option does Mplayer
     		error occur.

     		Installing Video for Windows 1.1e will fix problem.
     		However, installation of Video for Windows is not
     		suppose to be necessary for Windows 95 systems.  Also,
     		Microsoft contacts have confirmed that Video for Windows
     		installation modifies some Windows 95 files/attributes
     		which may ( or may not) cause problems.  If problems
     		occur, users can reinstall Windows 95, selecting option:
     		'Restore windows  files that are changed or corrupted'.
     		This installation could take 20-30 minutes; all previous
     		settings remain the same, so pretty straightforward
     		(but time consuming and inconvenient). However,
     		after this install, all Video for Windows files and
     		Windows 95 will function properly.

     		

Recommendation: Don't use Microsoft RLE compression format.  Indeo
     		or Microsoft video 1 work fine and are recognized
     		by Windows 95.  For hotline calls for courses already
     		on the shelf, installation of Video for Windows is quickest 
     		fix.  Since Microsoft isn't communicating that 
     		Video for Windows installation could be an issue, 
     		I would recommend Video for Windows install.



Video for Windows 1.1 e problems on Windows 95
----------------------------------------------

 Microsoft Windows 95 support contact indicated that
installing Video for Windows on Windows 95 systems makes
changes that could cause unwanted side effects.

Note: Most developers have Video for Windows installed on
      their Windows 95 environments and haven't noticed
      any problems.  (That's the good news :)  )

The contact recommended not installing Video for Windows.
If Video for Windows has already been installed, then
he recommends reinstallation of Windows 95 with option:

     'Restore windows  files that are changed or corrupted'

Recommendation: All release engineering testing should
occur on clean Windows 95 systems (without Video for Windows)
or other installed software that may have unintended
side effects. The support contact at Microsoft provided
a method where we can create clean Windows 95 environments
very easily and switch back and forth between environments.

I will send future mail with process to set up environment.