|
From: Ja-rod on 4 Dec 2007 14:02 I have created a Director projector using Director MX 2004. The program works fine in Windows XP, but when run on Windows Vista, it will crash in certain areas. All of my Xtra's are registered. Is the problem due to a compatability issue with Director and Vista? Will the issue go away once the newest version of Director is released and I recompile my code on it? Thanks, Jared
From: Sean Wilson on 4 Dec 2007 14:19 > Is the problem due to a compatability > issue with Director and Vista? Will the issue go away once the newest version > of Director is released and I recompile my code on it? No-one can answer those questions. There is no fundamental difference between Vista and XP other than UAC and Aero, so if it works on XP it should also work on Vista. Does it crash in the same place/s consistently? Does the app just vanish, or is there an error dialog posted? If the latter, what does the error message say, or does it identify a "module" that threw the error?
From: Mike Blaustein on 4 Dec 2007 14:29 Since you have not given us any real information about what the problem is, we can only guess. But the main difference that I have found with running projectors on Vista is the security model. Normal users do not have access to write to common locations, like program files or the HKEY_local_machine hive of the registry. The biggest issue I have had with Vista not running my programs has been places where I was trying to write to something that Vista would not let me write to. If that is the case, you need to rework your program in such a way that it reads/writes to the appropriate places. This sort of issue would not be fixed simply by using a different version of Director. You need to identify the problem and fix it.
From: alchemist on 4 Dec 2007 14:40 > There is no fundamental difference between Vista and XP other than UAC and > Aero That's not really accurate. Many parts of the core have been redesigned in Vista. Personally, I've found at least one system function (memory related) that is less tolerant in the new OS. Meaning that, code that didn't go by the book may lead to crashes or erroneous results when run on Vista. I'd suggest you try testing each Xtra you are using separately, cause there is a good chance that one of them is causing the problem. "Sean Wilson" <webforumsuser(a)macromedia.com> wrote in message news:fj497q$n8l$1(a)forums.macromedia.com... >> Is the problem due to a compatability issue with Director and Vista? >> Will the issue go away once the newest version of Director is released >> and I recompile my code on it? > > No-one can answer those questions. There is no fundamental difference > between Vista and XP other than UAC and Aero, so if it works on XP it > should also work on Vista. > > Does it crash in the same place/s consistently? Does the app just vanish, > or is there an error dialog posted? If the latter, what does the error > message say, or does it identify a "module" that threw the error?
From: Ja-rod on 5 Dec 2007 09:22
The program does crash in Windows Vista in the same place consistently at multiple locations. It once did [u]not[/u] crash at a location that normally crashes which was odd. Yet the same areas work fine in Windows XP. I am not writing anything to the harddrive. The program is a children's safety program. Children and adults simply navigate through the program, menus, answer questions (which are not saved) and watch video or interact with the environment. Video is either mpg, which I have the MPG Advance Xtra or using a swf. The code for an instance where the program is crashing is: on exitFrame me cursor 200 global gPause global gFinished global gFreeze if gPause = 0 then -- the home button has not been touched if sprite(4).playing then go to the frame else set gFinished = 1 go "Scene_117" end if else -- the home button has been touched go to the frame end if end The error I get is something of the nature of "Director projector has to close". Any help and direction will be greatly appretiated. |