So my new job started. The company provided me with a computer with a Windows Server 2008 operating system and they told me I should watch some Live Meeting recorded instructions and demonstrations about how the system works that I will be working on.
Live Meeting, in case you don’t know, has a very cool feature where you can record a power point and video demonstration and play it back later. The problem is that the video part does not work for a 64 bit operating system like Windows Server 2008. An error prompts you to download an MSA1 codec.
After a few attempts to solve the problem, I asked the administrative assistant for a second computer which she gave me. But it turns out the only one I got was one with a Vista 64 bit operating system and I found I still had the same problem with the new computer.
I have a 32 bit Vista operating system computer at home so I took the files home to see if I could run the Live Meeting recordings there. To my shock, I got the same error.
That is the problem I have. Now here are my questions. Where in the world do I get the codec for MSA1? How do I install this file on my computer? Surely there must be some sort of work-around for the computers with the 64 bit operating system. What are these work-arounds? I have searched the internet and I have yet to find a solution.
What fun!
http://ochoco.blogspot.com/2009/03/convert-your-live-meeting-recordings-to.html?
The tool mentioned in the above answer does not work any more. So for
people still struggling with the issue in 2021, most of the links of converter and codecs are dead. The converter is available on alternate site but biggest problem was to get hold of the codecs.After trying tons of options following worked for me on windows 10 64 bit
Download converter - the official link is https://social.technet.microsoft.com/wiki/contents/articles/30328.convert-and-edit-microsoft-office-live-meeting-recordings.aspx in case it is not working search for it and you might find alternate links for it.
Download codec - On running this converter the conversion fails because new version of windows do not have required codec and finding the codec was the most difficult part .Download the scdec.dll from here https://samples.ffmpeg.org/drivers32/newcodecpack/ Register the dll manually using by running the command from a elevated command prompt => regsvr32 scdec.dll
Now you can use the converter to convert the live meeting recording into a wmv , select the meeting recording folder and click on convert.
Related
Problem: I have an Roland Edirol UA-1000 10-Channel audio interface. It is still as good as what is out there and the last driver update for it was based upon Windows 7. It is hit/miss on Windows 10 compatibility.
What I would like to do is decrypt the driver and update it to work. I'm not sure if that is possible but this interface does much more than anything out there right now (i.e. clocking, optical, midi, coaxial, ADAT, etc.) unless you want to buy 3-4 separate pieces. The driver is just incompatible with Win10.
I have worked as a developer the past 10 years (e.g., VB.net, Java, Javascript, VBScript, SQL, Android) so I would like to try updating the driver for this interface.
Would it be possible... any suggestions outside of "buy something new?"
Check on GearSpace.com. My house in disarray now because we're having some work done so I can't look for my notes. My UA-1000 DOES work with Win 10, there are drivers that work and a procedure to follow and I believe I found the info on GearSpace.com. I just updated my software to REAPER and although I haven't recorded anything yet the meters on my UA-1000 and the input show up in REAPER on my PC so don't go nuts trying to rewrite software.
The only downside to the UA-1000 is the 8 audio in's and outs because if you want to expand to 16 ch's using ADAT and another interface you can't record above 48Khz.
Possible, but difficult. You will need to learn C or C++, a lot about Windows driver APIs, and a lot about reverse engineering. The existing driver may not be much help at all. You won't be able to extract any kind of readable code from it. You would basically be starting from scratch, with black-box observation and/or disassembly of the existing driver as guidelines. It would be difficult work, and the result would be something that would have limited use to other people anyway, thanks to Windows driver signing.
I love my UA-1000 and did get it working on both Windows 10 and 11 using the Windows 7 64-bit drivers from Roland:
https://www.roland.com/global/support/by_product/ua-1000/updates_drivers/
Note: For Windows 11, the install will tell you that "Memory Integrity" security will need to be turned off. There's no way I found to get around it. If you need to turn it back on, uninstall the UA-1000 driver then search for the "Core Isolation" settings and re-enable Memory Integrity. Basically, the old UA-1000 driver isn't built to the latest Windows driver security standards.
Install Steps:
Download Windows Vista 64-bit drivers.
Unzip the archive into a folder.
Connect the UA-1000 to the computer and turn it on.
Right click Start menu and search for the "Device Manager".
The UA-1000 appears in the "Sound, video and game controllers" with a yellow triangle.
Right click on EDIROL UA-1000 and select "Update driver".
Select "Browse my computer for drivers." Point to the folder containing the drivers you unzipped in step #2.
Click "Next" and the drivers will be installed.
You may need to reboot. By the way, I've written drivers for Windows and OS/2 (yeah, I'm old) -- you don't want to do that, so enjoy the steps above.
Note 2: Initially, my UA-1000 was recognized but not outputting any sound. But once I did a factory reset on the UA-1000, it sprang to life. Resetting the UA-1000 is described on page 44 of the user manual which you can get from the same link above. Have fun!
I am attempting to install the Arelle XBRL software and these are the steps I am following.
Download the Windows 64 bit version from http://arelle.org/pub/applications/
Double click on installer
As soon as I click the installer I get an NSIS Error message depicted below.
What I have tried:
E-mailing the Arelle support dept but they don't seem to answer at all
Searched for a solution
The most common solution I have found was to run the installer from the command prompt with the below syntax. This seems to have worked for many people but I am still getting the exact same error.
"C:\Users\MyPc\Desktop\arelle-win-x64-2019-07-24.exe" /NCRC
This problem has existed for weeks and it doesn't make sense as Arelle is a widely used program for use with XBRL and many people have downloaded it.
Disk checks and various error checks are being done frequently by the company's administrator so computer maintenance is always occurring.
Any ideas?
I've had the same issue, I've downloaded installer from another computer and another net, run it on computer where was issue, and it works.
I am new in windows logo test . I heard this process from my friend . I created a application which consist of some drivers . so I need to sign from Microsoft for trusted installations of my software . I heard the windows logo process for sign my driver through some test conducted by me and need to send this report back to windows . So I have some doubt to setup this process .
How to setup this process ? (how many system needed ? and which OS I should install for testing) and what are the requirements ?
I think there is a server and client machine (So 2 system is needed ?) . How to setup this system ? can you provide step by step tutorials ?
Your understanding is correct. The testing goes by a few names, WHQL, hardware certification, logo test, etc. Just to give a few more keys words to google.
Microsoft outlines the steps that you need to take https://msdn.microsoft.com/en-us/windows/hardware/hh833792. Honestly, the process is not that bad all things considered:
Buy a code signing certificate. Microsoft lists who they support and there are plenty of discussions on the OSR forums that discuss signing requirements in great detail. We use Digitcert and have no issue. I recommend reading up on this article to make your life easier: http://www.davidegrayson.com/signing/. The whole cross-certificate detail is glossed over in the Microsoft docs.
Setup your company in the hardware dashboard. Pretty straightforward here; just follow the directions for uploading your code cert. Sign all the legal stuff and setup any other developers on your team if they need access.
Install the HCK. We bought the MSDN OS pack ($800 USD) just for the WHQL and it has been awesome. I used Server 2012 to run as the HCK server and installed it as a virtual machine on a pretty beefy PC. Runs great, no problems installing it, and configuration is intuitive. More details are here: https://msdn.microsoft.com/en-us/windows/hardware/jj123537.aspx
Configure your test PCs. I used a mix of VMs and physical PCs for this part. Going through the provisioning process is automated for the most part. I recommend taking VM snapshots once completed in case something goes south during testing.
The HCK server walks you through the tests you need to perform depending on the type of driver you are testing. For example, we are working on a printer so all of our testing involved printing.
We tested against XP SP3 all the way through Windows 8.1, both 32 and 64 bit though your needs may differ. We needed the driver in Windows update, not necessarily the hardware logo. Once completed we simply uploaded the passing report through the hardware dashboard and that was that.
It seems like a huge task but it is not the worst thing in the world so keep at it you will get it done!
There is a file I would really like to use on my mac, but it is .exe and I cannot open it. It is called MCreator, and the file is mcreator.exe, and is used for making minecraft mods without knowing any java. I have tried numerous applications that supposedly can do this, such as wine, mono, and crossover, but none of them seem to work. When I use mono, I type in this, and it returns an error:
Howards-Mac-mini:Mcreator 1.4.2 [1.6.4] Jared$ mono mcreator.exe
Cannot open assembly 'mcreator.exe': File does not contain a valid CIL image.
When I use wine, it just quits and doesn't do anything, even though it displays the icon for MCreator. I cant figure out how to get open a preexisting file on crossover. Does anyone have any ways to fix my problems and/or run this file?
Your best bet is probably to run a virtual machine. Windows XP is good for this inside VirtualBox, as it can run on as little as 512mb of RAM, and 1 single-core virtual processor. Download VirtualBox by going to www.virtualbox.org and as for Windows XP, you can probably get your hands on that but I unfortunately cannot help with that unless you have a genuine COA.
Thanks
You could also try running it in Wine. It allows you to run Windows apps in OS X without a copy of Windows. I've used it successfully before; your mileage may vary.
1)Install Wine and Winebottler from http://winebottler.kronenberg.org/
2)You may have to change the System Preferences >Security & Privacy>Allow Apps downloaded from>Anywhere
2)Run the xyz.exe using winebottler.
I am using "Microsoft Visual Studio" to work with an "MFC application".
I am using "Installshield" to create the setup file for this application.
I get a "setup.exe" file.
If I run this setup on a "Windows XP 32 bit" machine, the installation ends properly.
Yet, when I try to start the installed program, I get the message:
"The procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll."
In debug mode, I can't find the moment the error occurs because whatever the breakpoint I put in the code, the message appears before reaching the breakpoint, I guess at the very beginning of the program execution...
Note: It works for Vista 32 bit and Seven 64 bit.
It appears lots of people do have the same problem but I couldn't find a solution for myself.
Can you help?
Thank you.
Welcome to the world of DLL hell and application dependency analysis.
I found that DLL on my Win8 machine in the SYSWOW64 (32bit System32 folder ) with version 7.0.9200.16384. Looking at it using Dependency Walker I can see it in fact exports the function you are looking for.
I also see on my InstallShield machine a merge module called MSVCRT.MSM that redistributes version 6.00.8797.0 of this file. However when I look it using Dependency Walker, I see it has the exported functions _except_handler2 and _except_handler_3 but not _except_handler_4_common.
So therefore you need a newer DLL and that merge module won't help you. Microsoft used to have this cool website called DLL Help Database that told you all the versions of a file and what shipped them but sadly they killed it.
BTW, I can also see that this DLL is installed with Windows these days. Windows XP? I'm not so sure as I'd have to fire up a VM and look.
A couple possible resolutions:
Find out what SP or Hotfix of Windows fixes this and make it a dependency of your MSI.
Grab the DLL from a Win 8 machine and add it to your INSTALLDIR and deploy it privately.
One final note. This is either caused by the version of Windows XP comes with an old version of the DLL ( A related KB Article says it does ) or that a third party application whacked the DLL causing the problem. Some more study is required here.
I recommend you first try installing the MSVC Redist version 2008. That one does include the implementation of the missing function.
This post is old but I wanted to leave my solution since this problem was hell to me. My python app was working for Linux, Win7, 8 and 10 but WinXP refused to work with that message.
I was using py2exe to get an executable and it will put some DLLs along with the exe file.
Deleting some dlls from the exe's directory was the only thing that make the app work in XP and continue working in the other systems:
[ "POWRPROF.dll","IPHLPAPI.DLL","USP10.DLL", "DNSAPI.DLL" ]
Also distributing "Microsoft.VC90.CRT" directory along with the exe file, with it's manifest and DLL files.
I hope this will be useful for someone, since it took me weeks to figure it out.
(i know the OP wasn't working with python, but the error is just the same)
Your program has a dependency which is not being satisfied on Windows XP. You might try using Dependency Walker to identify it, or you might check for known limitations. For example, Visual Studio 2012 doesn't support Windows XP until update 1 and a build option change - is that what you're using?
The problem was probably because you might used a corrupted DirectX version on your Win XP. It happened to me as well because I randomly downloaded a DirectX setup which was corrupted and caused these. The solution I did was is I deleted all the files that has anything to do with directX from C:Windows/System32, deleted the directX from add/remove program as well and completely removed the whole registry key from regedit. Local_machine/software/microsoft/DirectX... What I did then was found a original values and keys for DirectX 9 on the net and made a new registry key.
The DirectX folder was once completely and originally back on regedit and it showed in dxdiag that the directX is installed.
In case you encounter crashes in the game, I suggest you to download .NET Framework 3.5 Service Pack 1 and then make a backup on your PC (If you're not using nVIDIA graphic cards like I do, I use ATI Radeon) and download nVIDIA PhysX system software driver and see if it works. (You need nVIDIA phydX drivers to run this game without crashes only if you use Win XP, the problem shouldnt encounter on Win 7) In case the drivers screw up your PC (The nVIDIA PhysX one) you will be able to restore your old PC function before those drivers (If you made a backup of your PC, I suggest using Acronis Boot for backups) it means you're totally out of luck if you're not able to get the nVIDIA PhysX on ur for example, ATI graphics on Windows XP, because without nvidia physx, on Win XP, Metro wont run, while on Win 7 / Vista / 8 it should.
I just installed the latest VS 2017 and was running into the same problem. I googled everything but couldn't find any solution, so I just defined it myself:
extern "C" int _except_handler4_common() {
return 0; // whatever, I don't know what this is
}
I've spent the last 8 hours picking my code apart with this exact same error and it turned out to be a line of code in my application, specifically a check for IPv6 support in the OS:
conf.IPv6Disabled = !(Socket.OSSupportsIPv6);
I commented that line out and voila, error disappeared.
This problem persists to every software or game that requires windows 7 or 8 or vista but is made run into windows xp. So if you want to resume or start your program you need to upgrade your windows to 7 or 8 or vista as per the system requirements of the program.
HOPE IT WAS HELPFUL
THANKS