That doesn't fix it though. We've already wrapped those calls.
We have to remove the A4D plug-in from the Win4DX folder on the server
to get 4D Client or 4D mono to launch.
If one of our customers that uses our web serving module has this
problem we have no solution, because we can't remove the plug-in from
their server.
I wonder if they have QuickTime installed on the Client machine. If
not, see if installing that will help.
One simple solution would be to wrap the calls to A4D_Startup
and A4D_Init in a check for Client to avoid calling them at
all. Active4D really doesn't do much of anything until it is
initialized with 'A4D Init'.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoy.org
_______________________________________________
Active4D-dev mailing list
Active4D-dev@aparajitaworld.com
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
