zLaunch for Windows FUQPlease consult the following list for answers to the most common pre-sales questions regarding zLaunch specifically for Windows, as well as additional technical information not covered on the zLaunch Summary Page. Refer to our Needs Analysis FAQ to determine if zLaunch or some other tool is right for you.
zLaunch for Windows has been shipping since
April 1996 and zLaunch for Macintosh since June
1996, but they are sold separately. Both are mature and robust products
with a number of user-controllable options for maximum flexibility. zLaunch is not currently supported under Windows
NT, but may work for some applications. zOpen for Windows
is supported under NT. zLaunch for Windows is $299 US. For $499
US you can get the cross-platform bundle which includes both zLaunch for
Windows and zLaunch for Macintosh. Consult the
zLaunch Summary Page for details. A demo version of zLaunch for Windows can
be found in our Download Center. zLaunch supports Director 6.0, as well as
earlier versions including 5.0.1 and 4.0.4
zLaunch works with all the possible permutations
under Windows 3.1 and Windows 95 with Director 6 (and earlier versions including
5.0.1 and 4.0.4) . Refer to the General Questions
about zLaunch FAQ for more info. zLaunch works with both 16-bit and 32-bit
projectors built with Director 6.0 and 5.0.1.The Lingo command the platform
will indicate whether you are running a 16-bit or 32-bit projector, but
it does not return the specific platform. Refer to the TechNote,
"Determining the Playback Platform
at Run-Time" for more details, and see Zeus's zWinver
Xtra. zLaunch will launch the vast majority of
all Windows applications without modification. Refer to the General
Questions about zLaunch FAQ for more info.
Applications which cause a reboot, or kill
other running processes may not work completely with zLaunch. Refer to the
General Questions about zLaunch FAQ for more
info. Generally you do not need to modify your Windows
application. Refer to the General Questions about
zLaunch FAQ for more info.
Both Director and zLaunch require that you
be running under Windows, and not simply DOS. Most DOS applications that
run under Windows can be launched by zLaunch provided that:
zLaunch does not require a formal installation
procedure. Simply include zLaunch (both the 16-bit and 32-bit versions if
applicable) in the same folder as your projector. You can run it from either
a hard drive or a CD. There is no need to copy it into
the Windows System directory, or similar requirement. zLaunch for Windows will automatically adjust
for the current drive letter. Refer to the Details
on zLaunch's Capabilities FAQ for more info. zLaunch for Windows does not determine the
path to an application, but zOpen for Windows can.
zLaunch for Macintosh can locate an application
based on its Creator Code. Refer to the Details
on zLaunch's Capabilities FAQ for more information. zLaunch for Windows does not return the path
to an application, but zOpen for Windows can. Refer
to the Details on zLaunch's Capabilities FAQ
for more information. zLaunch is not really designed to control
other applications, but refer to the Details on
zLaunch's Capabilities FAQ for more info. zLaunch does not support OLE.
The latest version of zLaunch allows you to
specify the color of the background as an RGB
value. Refer to the Details on zLaunch's Capabilities
FAQ for more info. Yes, you can pass parameters to the launched
executable. Refer to the Details on zLaunch's Capabilities
FAQ for more info. zLaunch works with external
applications, not external
devices. Refer to the General Questions about
zLaunch FAQ for more info. Yes, you can set the Windows working director
for the launched application and then reset it when returning to Director.
You do not need zLaunch to solve this problem.
Refer to the TechNote, "Solving
Protection Violation Errors"
zLaunch can pass a document name to an application
when it is launched. If you want to pass documents to an existing application
while keeping Director open, use zOpen for Windows
instead.
zLaunch is an external application itself,
so it is actually initiated with using Lingo's "open...with"
command.. This starts zLaunch and gives you the opportunity to pass it the
parameters that control its execution. open "iniFileName, sectionName"
with the pathName & "zLnch32.exe" open "param1,param2....paramN" with
the pathName & "zLnch32.exe" ![[End of Page]](../images/zeop.gif){kind=small}