[comp.sys.mac.hypercard] HELP! with video drivers

gyarneau@bcm.tmc.edu (Herman Glenn Yarneau) (05/15/91)

Help!  Help! HELP!!!!!

I am creating a level three interactive video disc and  I have reached a wall
that I can not get over.  

I need to drive a Sony 1200 player.  
I have a hypercard stack which has the driver for a sony 1500 
I believe it is the Voyager series of XCMD's and XFCN's (there are a lot of
them, as compared to the other series which only has one XCMD's for each type of
player) 
I know that this driver works because I have used it in hypercard
I am using SuperCard to build the computer interface.
I know thatSuperCard can drive video drivers because I have used the smaller set
before (but not the large (Voyager?) set)
When I import the Xcmd's and XFCN's into SuperCard  They dont work properly
When executing the "VideoStatus () " XFCN I keep getting an "abort" message

Can anyone help me to solve this problem?
I cant find a phone number for the voyager company

I will be waiting anxiously by the mailbox for any kind of help.

Thanks

Glen Yarneau
gyarneau@bcm.tmc.edu

Irv.Kanode@p3.f53.n114.z1.fidonet.org (Irv Kanode) (05/25/91)

> I need to drive a Sony 1200 player.  
> I have a hypercard stack which has the driver for a sony 1500 
> I believe it is the Voyager series of XCMD's and XFCN's (there are a lot of
> them, as compared to the other series which only has one XCMD's for each 
type
> When I import the Xcmd's and XFCN's into SuperCard  They dont work properly
> When executing the "VideoStatus () " XFCN I keep getting an "abort" message
> 
> Can anyone help me to solve this problem?
> I cant find a phone number for the voyager company
> 
> I will be waiting anxiously by the mailbox for any kind of help.


I am not familiar with the Voyager XCMD's.  However, the most common reason
for HyperCard XCMD's not working in SuperCard is the existance of system level
 
resources used by the XCMD or XCFN.  These other resources are most often 
string
resources (used to report text based error messages) or DRVR resources.  
SuperCard
does not normally import them when you convert a stack to a project.  (You may
 
be able to import them by specifying a custom placement in the importation 
dialog
box-but Ive never tried it.  I use ResEdit as described below.)

Open the HyperCard stack containing the XCMD/XCFN's with ResEdit and look for
other resources that by name or by ASCI content appear releated to the XCMDs.
 Copy these resources (if you are not sure copy everything) to the resource
fork of your SuperCard project.  

Before you call the XCMD, tell SuperCard to Open resources--check the 
SuperCard
manual for the exact wording and syntax.  When finished, tell SuperCard to 
Close
resources.  This usually works.  

However, some XCMDs call other XCMDs and expect to find each other in the 
resource
fork.  With experimentation, you can determine which ones should go in the 
SuperCard
resource window and which ones  (maybe all) have to go in the resource fork.
 You will again have to use open and close resources.  

If you still havent met with success, try moving the XCMDS and related 
resources
to your shared file, or to a SuperCard stand-alone, or to SuperCard itself.
 

The odds of eventual success are very high--approaching 100% unless they are
new XCMDs which take advantage of the NEW features of HyperCard 2.x.  Your 
message
sounds like the XCMD is looking for a string resource to report the video 
status
of the player.

Good Luck!

 

--  
Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!53.3!Irv.Kanode
Internet: Irv.Kanode@p3.f53.n114.z1.fidonet.org