home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.ms-windows.apps:6402 comp.sys.mac.apps:18923
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!asuvax!ncar!noao!amethyst!organpipe.uug.arizona.edu!argon!ianbjor
- From: ianbjor@argon.gas.uug.arizona.edu (Ian D. Bjorhovde)
- Newsgroups: comp.os.ms-windows.apps,comp.sys.mac.apps
- Subject: Re: AfterDark PC to MAC
- Message-ID: <1992Dec23.002905.1412@organpipe.uug.arizona.edu>
- Date: 23 Dec 92 00:29:05 GMT
- References: <pqfr_9=@lynx.unm.edu> <MARK.92Dec22093022@indian.prepress.com>
- Sender: news@organpipe.uug.arizona.edu
- Organization: University of Arizona, Tucson
- Lines: 24
-
- In article <MARK.92Dec22093022@indian.prepress.com> mark@prepress.com (Mark S. Bubien) writes:
- >
- >>Does anyone know of a way to translate MAC afterdark modules to PC modules, or
- >>vice-versa?
- >
- >The AD modules aren't just files, they're code resources which are
- >loaded and executed by the AD Control Panel.
-
- Well, actually they are DLLs, according to the AfterDark SDK.
-
- I am not really sure if it would be that easy to just 'recompile' the
- sources (even if you _did_ fix the mac specific code to windows
- specifics) because if that was possible, then the Mac versions would
- have the same savers as the windows versions and vice-versa. The latest
- Mac version of AD has some really good savers, that would just be too
- BIG (even without memory leakage) to be useful... unless you have 64 Mb
- base ram :-)
-
-
-
- --Ian D. Bjorhovde
- ianbjor@gas.uug.arizona.edu
- Department of Materials Science and Engineering
- The University of Arizona
-