Windows failed to initialize

[Joe Lewis Wilkins]

Hi everyone,

I just saved my current stack as a standalone. The Mac Version is  
flawless. The Window's version, however, puts up a "Failed to  
initialize" dialog almost immediately. There was a number like  
xx00005 or something similar posted; is that number meaningful? The  
only issues that I can think of that may have caused a problem are:

At one point this mainstack had a substack that is no longer being  
used. All references to it were deleted and the substack itself were  
deleted, but I was never able to completely remove or delete all  
"indications" of that substack from the mainstack. Apparently this  
caused no problems in the Mac version, but I wonder if this may have  
been the cause of confusion in the Window's standalone.

There are some references to the various menu buttons, either  
enabling or disabling portions from time to time. I did not use any  
conditionals in the scripts that checked for the platform, assuming  
that Rev would take care of those kinds of things automatically.

The externals, audio clips, are linked through player "paths" and  
work fine on the Mac version, and they have ended up in a folder  
named "Externals" on the Window's version, but did Rev handle the  
rest of that conversion properly, or could that be my problem.

I guess, what I'm asking is: when this kind of thing happens, how do  
we debug our Rev stack to fix it?

TIA,

Joe Wilkins