I am in a similar situation. My products are not put on the Internet (I distribute by CDROM).  So Internet, even MSIE browser, is not an issue for me. I intend to use .exe as my main product.

I don't have 200+ hotspots/radar points on one map, but I definitely have 200+ scenes (pano, still photos, etc.) in one package with several maps.  Linking two separate .exe files might work for me (I have not  tried nor know how to do this yet, but will try).  But, if it is not "seamless" and "transparent" to the customer using my tour product, and he/she can't easily go back and forth between two .exe files... then I've failed in my product.  But, I will try what Genseng suggests for my application, and see what happens.

I am also ready to experiment and test connecting two .exe projects because I have more than 200 scenes in my entire project.

What action do I put on the Button or Hotspot to go from Floor1.exe (or Floor1.html) to Floor2.exe (or Floor2.html)?  Javascript code?  What code is needed.  Will it invoke an Active Script warning since my .exe files are on my CDROM/local drive?

If using .exe files, will the first .exe file stop running when I go to the second floor .exe file? or will I end up with multiple .exe files being executed at the same time and have to close floor1.exe manually?

I'm anxious to try this.  I like the Floor1, Floor2 ... html demo in the previous messages.

Does anyone have the javascript code to link multiple .exe tours using buttons?