I'm not sure if this is the right place to ask, seeing as I don't currently have any code to share, but perhaps someone has an insight.
I have a very old Flash MX projection (.exe file) that was written and compiled in flash MX 2004. It's a simple interactive app - a test where a user picks an answer to a question and pushes ENTER to move to the next question.
The projection works fine on WinXP SP3 but doesn't work in win7, failing with a "class not registered" error.
It does work after I install flash player activex (I tried installing the latest, and also legacy version 6 r71), but then it doesn't register any keyboard commands and crashes a short while after a key is pressed.
Any idea what can be causing this?
So far I've tried fiddling with IE security settings, disabling DWM and windows themes, compatibility settings, etc., with no luck.
Also, despite the fact that the compiled projection is supposed to have all necessary components to run inside, it doesn't run if flash.ocx isn't registered. Isn't that weird?
Any help will be appreciated. I know this is old stuff and no one promises compatibility etc. And I don't even have the code as of now (not sure I can find it; assume I can't) - but this app is somewhat important to my company and this really seems like a "small" issue - if I could just find it...
Update - it kinda works if install the latest flash player and run it in compatibility mode - but it hangs after about a minute, regardless of what i do.
if i run it without compatibility mode, it doesn't run with a "library not registered" error.
You might want to repackage it.
Extract SWF from projector executable, for example, using this tool.
Get the newest standalone Flash Player and check if your .swf-file works with it.
Now export new projector file.
If this doesn't work for you, the only other way to do this is to recompile your .swf from source.
I agree with Ale's solution.
Have you tried Window's compatibility options to run the .exe as it would in an older compatibility mode ? This may work.
Related
I got a weird problem with my VB app that has got me very confused. I am updating an existing program. I had to add some processing queue capabilities. On my system, unit testing worked great but when I compile it and run it on a different computer (a network server machine) it first tries to open an office install. If I cancel this, the program seems to run fine. The problem is that this program will be run in the background and I can't be hitting cancel each time it runs.
So my question is this: what is going on here? I'm usually a java developer we eclipse so I'm used to being able to include all the needed libs into the jar files automatically. It doesn't seem like the case with VB6. it seems like it expects all the same libs to be on all the systems. Is there any way to tell what might be triggering this?
The only thing I can think of that is causing it is that I'm using the "OpenProcess" function in the kernal32 lib. that the only major change I have made.
any help would be very appricated. thanks!
EDIT:
It seems that multiple versions of word were installed on the system and it was screwing things up somehow. We uninstalled one and it fixed it.
I ran into this a while ago and it was related to my installer for the VB6 app overwriting some system files for Office that it shouldn't have. Any time one of the System dlls was accessed Windows would determine that something was wrong and the Office installer would start up.
The short-term fix was to let the Office Installer repair the broken chain of dlls.
The long-term fix was to never overwrite built-in Windows System dlls.
You could also check out the Microsoft Fix it Center.
I have been searching for the answer for this for 2 days. We have an application that uses ReportViewer 9. However, clicking on the print button in IE10 causes the browser to stop working (with the "Debug" or "Close Program" buttons). Everything else seems to work fine.
We tried using ReportViewer 10 but we get the same issue.
We are using Visual Studio 2010, Windows 7, IE 10, and targeting .NET 4.0. The crashes happen in the IDE and through IIS.
EDIT: Things I Have Tried:
I have tried adding my website to Trusted Sites, lowered the security setting, and I think I've tried every possible combination of checkboxes in the "custom" security box.
I've tried enabling Protected Mode and Enhanced Protected Mode, with a variety of check box combinations from Custom security level that sounded promising.
I've tried forcing IE10 to run in 64-bit mode (including the tabs), but our app forces the tab to run in 32-bit anyway.
Someone suggested that it might be a Kill Bit issue, so I tried editing the registry to ignore kill bits just to see if it would work (it didn't).
Also, I'm pretty sure I've tried just about every permutation of all the variables I've already mentioned. (I'm a little burnt out at this point, so I might have missed 1 :S)
This thread seemed promising but I could not get it to work. It is talking about Win8 but I thought I might be able to apply them to my situation.
I found a suggestion changing the BuildProvider assembly to type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.WEBFORMS ..." (instead of Common), but so far that is not working either.
Tried installing Report Viewer 11, and installing a very old version of our application. Both give me the same result.
Aha! OK, so it turns out that my issue is NOT with ReportViewer, but rather with RSClientPrint. Once I did a google search for that I quickly found that the answer is: Upgrade to Sql Server 2008 R2 SERVICE PACK 2.
The version of RsClientPrint you get with R2/SP2 is 10.50.4000, while the version I had was 10.50.1600.
In conclusion, it appears that RSClientPrint 10.50.1600 is NOT COMPATIBLE with IE10, but version 10.50.4000 IS.
I REALLY hope this helps someone else!!
I am trying to use the HP Fortify Static Code Analyzer to analyze security concerns in a large C application and I have run into various bugs in the software itself that I cannot seem to find any answers to anywhere on the Internet. I am using version 3.4 of the software and running it on a Linux x64 system.
The main bug that I am encountering that makes it very difficult to use this product at all is that in various different places in their Audit Workbench GUI the program will just close for no reason. An example is whenever a pop-up window shows asking you a question and your answer to the question is just to close the pop-up window by either clicking on the close button or the cancel button, the whole program ends instead of returning you back to where you were when you originally got the pop-up. Another example is when I try to open the Rules Editor, either for a new Rule Pack or an existing Rule Pack, the program opens up a progress window with a moving progress bar that sits there and moves for a while but when it is finished, instead of opening up the Rules Editor, the whole program just ends suddenly.
Has anyone out there seen behavior like this? If so, please let me know what I can do about it. Thank you.
I would highly recommend upgrading to the latest (4.10 at the time of this post) version. One thing you can do to help diagnose issues is to look at the log files. These are located in (by default) [user.home]/fortify/AWB-3.40/log.
Also, since you are using Linux 64bit, you will want to ensure that AWB isn't trying to access the 32bit JRE at any time. This can be accomplished by removing [fortify install root]/jre and renaming [fortify install root]/jre64 to [fortify install root]/jre. Some of the tools default to /jre and so you can run into issues on Linux 64bit.
I have a windows mobile project in VS2005. Initially I could not get any breakpoints to enable on windows mobile 6 device but they worked on PocketPC2003 Emulator. It's a new computer at work and after a while I realised I had no installed any SDK's beyond 2003. Having now installed SDK's for windows mobile 5.0 6.0 and 6.5.3 I now have SOME of my breakpoints active.
My solution consists of a main application under which there are a few screens and associated code. There are also a series of other classes each of which compiles to a separate DLL. It seems the issue I have is that any breakpoints in these separate classes
work perfectly now. However any breakpoints in the main application class give an error "The breakpoint will not currently be hit. No symbols have been loaded for this document." I've tried a number of things including deleting the bin\debug and obj folders to clear old debug information. The PBD files appear to be created ok for the exe files as well as the class DLL's but only the Dll's work correctly in debug.
Any ideas guys. I really have to get this working as it needs to work on a device not just an emulator. I have an external DLL I need to use as part of testing that is very specific to a brand and model range of hardware. I wont explain why here, just suffice it to say I really need to get this sorted.
I'm still learning VS2005 So please be specific with suggestions as I might not yet know where to locate certain functionality.
I should probably add it works fine in windows mobile 5.0 emulator but I don't have a windows mobile 5 device to test with
Thanks in anticipation.
Well I don't know exactly what I did but it is now working. I read an article on here about enabling the module tab in the debug menu and after doing that it worked however I had done a couple of other things prior to doing that and hadn't tested it so not sure which it was that fixed it.
I have a game that I have made in C# and it installs and runs as expected under Windows XP. However when I install it on a Windows 7 machine, then it either simply doesn't work (without any error message) or it gives a generic error message. Is there anything special that I have to do in order to be able to use SDL.Net with a Windows 7 computer?
UPDATE: I have just been informed that it doesn't even work on XP. Both XP machines I tried it on had SDL.NET installed (I didn't know that one of them already had it when I used it for testing). So pretty much if SDL.NET SDK is not installed on a computer my program doesn't work. Does anyone have some insight into what exactly needs to accompany my program from SDL in order to make it work properly? right now I have all the base SDL_*.dll and SdlDotNet.dll and Tao.Sdl.dll. More needed? Or is there some kind of SDL runtime that I have to install with my program in order to use it? I am really stuck with this one.
Have you tried running it as admin? I don't mean happening to be logged in as an admin account, I mean right click the exe and Run As Administrator? If you do that and don't get the error, then your problem will be quite easily solved, without requiring it to always Run As Admin.
Added every Dll including those that weren't explicitly needed and it now works. Apparently there are some hidden links between dll's that I didn't know about.