Randomness:
This is an Ampro 7200 series (7100 actually) LCD Lightvalve + CRT projector.
One of mine works perfectly. The other does not. Autoconverge isn't working.
If anyone has a service manual or a way to get one, contact me.
Hi.
I'm Brian.
I am a nerd.
I work for Served Computing.
I also worked for Infinite Campus (Summer 07).
This is my desk.
Info:
CoreFoundation is present in iTunes, Safari, and QuickTime SDK on Windows. The iTunes and Safari ones are simple .DLLs, while the QuickTime SDK (which iTunes also uses) is a ghetto shim that dispatches through QuickTime.qts.
The QuickTime.qts and CoreFoundation.dll modules are INCOMPATABLE ENTIRELY; you CANNOT mix and match or pass data between them.
Examples:
Distribution of Examples.zip is ENTIRELY LEGAL: from the source files (all of them):
Apple grants you a personal, non-exclusive
* license, under Apple's copyrights in this original Apple software (the
* "Apple Software"), to use, reproduce, modify and redistribute the Apple
* Software, with or without modifications, in source and/or binary forms;
Copy all the .DLLs from a certain web browser to the same directory as these samples to run them.
Examples include:
OutlineExample - CoreGraphics PDF Outline example (most interesting one of these)
String/Allocator/Dictionary examples - CoreFoundation examples; really only interesting as proof-of-concepts.
The OutlineExample has issues with PDF files which are not in the same directory; put them in the same directory and reference them directly i.e. "Test.pdf" not "C:\This\Is\A\Directory\Test.pdf"
Some PDFs don't work with it; this is true for this application on all platforms.
Using the DLLs from that certain web browser may be in violation of its license; it is your responsibility not to violate your software licenses.
Censored by Apple: The Story:
I've not used Safari/Win32 to compile against CoreFoundation and CoreGraphics on Win32 natively. Or anything of the sort. Don't ask me. However, in theory (due to a general knowledge of the operation of Windows and no actual disassembly or anything like that), if you were to look at DLL exports, you might be able to figure out what they were called. And, since it's after all the same-named libraries these exports might take exactly the same parameters as their counterparts on an operating system made by the same company which developed said libraries. And therefore it may or may not be possible to use headers from said operating system's development kit to link against said libraries using MingW on Win32. This is all theoretical, of course.