VBA-M

Squall_Leonhart · Post by **Squall_Leonhart** » Fri Aug 15, 2008 6:01 pm

Overview
The Microsoft Visual C++ 2008 Redistributable Package (x86) installs runtime components of Visual C++ Libraries required to run applications developed with Visual C++ on a computer that does not have Visual C++ 2008 installed.

System Requirements
Supported Operating Systems: Windows 2000 Service Pack 4; Windows Server 2003; Windows Vista; Windows XP
Required Software:
o Windows Installer 3.0 Windows Installer 3.1 or later is recommended.
Disk Space Requirements: 6 MB (x86)

Your problem evades me.

Deathlike2 · Post by **Deathlike2** » Fri Aug 15, 2008 7:19 pm

The Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) installs runtime components of Visual C++ Libraries required to run applications developed with Visual C++ SP1 on a computer that does not have Visual C++ 2008 SP1 installed.

System Requirements
Supported Operating Systems: Windows Server 2003; Windows Server 2008; Windows Vista; Windows XP

Minimum: 6 MB (x86)

Required Software: Windows Installer 3.0 Windows Installer 3.1 or later is recommended.

VBA-M Readme wrote:Microsoft Visual C++ 2008 SP1 Redistributable Package (x86):
http://www.microsoft.com/downloads/deta ... layLang=en

Let me know when you've paid attention to your own documentation.

Squall_Leonhart · Post by **Squall_Leonhart** » Fri Aug 15, 2008 7:35 pm

VBA-M works fine on the non sp1 version as far as i've seen.

you can just download the missing dll's and drop them in the folder anyway.

Bugs fixed in MFC in Visual Studio 2008 SP1

Hello, everyone. This is Pat Brenner. I’m an SDE on the Visual C++ Libraries team.

We’ve just released Visual Studio 2008 SP1, and it includes about 55 fixes to the MFC library. Many of these fixes are for the new features that were added in the Feature Pack, but others were bugs in the RTM version of Visual Studio 2008 that we have fixed. Here is a partial list of the issues that we addressed:

· Some accessibility issues in toolbar and ribbon components were fixed.

· Running MFC applications on Windows 2000 (with or without GDIPlus.dll) is supported.

Deathlike2 · Post by **Deathlike2** » Fri Aug 15, 2008 7:40 pm

I'm having problems finding the dlls to work around this (but I'll eventually try downloading the redist and see if it'll be happy, though I don't recall if I have the required Windows Installer version).

In any case, it helps if that stuff is provided on your file server and/or provide a link to the non-SP1 distrubutable in the readme (or something along those lines) to make life easier. You can't assume everyone's just going to figure it out automatically. People read the readme after all (well, maybe not).

mudlord · Post by **mudlord** » Fri Aug 15, 2008 11:37 pm

VBA-M works fine on the non sp1 version as far as i've seen.

Err, squall, I think you need to check the SVN...Spacy upgraded to MSVS2008 SP1. As a result, targeted OSes changed, thanks to MS >.>

I'm having problems finding the dlls to work around this (but I'll eventually try downloading the redist and see if it'll be happy, though I don't recall if I have the required Windows Installer version).

In any case, it helps if that stuff is provided on your file server and/or provide a link to the non-SP1 distrubutable in the readme (or something along those lines) to make life easier. You can't assume everyone's just going to figure it out automatically. People read the readme after all (well, maybe not).

Sorry about the issues you are having.

I will try and upload the non SP1 redists when I can.

Squall_Leonhart · Post by **Squall_Leonhart** » Wed Aug 20, 2008 11:59 pm

mudlord wrote:
VBA-M works fine on the non sp1 version as far as i've seen.
Err, squall, I think you need to check the SVN...Spacy upgraded to MSVS2008 SP1. As a result, targeted OSes changed, thanks to MS >.>

I'm having problems finding the dlls to work around this (but I'll eventually try downloading the redist and see if it'll be happy, though I don't recall if I have the required Windows Installer version).

In any case, it helps if that stuff is provided on your file server and/or provide a link to the non-SP1 distrubutable in the readme (or something along those lines) to make life easier. You can't assume everyone's just going to figure it out automatically. People read the readme after all (well, maybe not).
Sorry about the issues you are having. I will try and upload the non SP1 redists when I can.

That explains things, i'll tell him to compile with support for Win2k

franpa · Post by **franpa** » Mon Aug 25, 2008 1:28 pm

I can't execute QT build 606, yes I updated the QT files too.

---------------------------
E:\Emulators\gameboy advance\VisualBoyAdvance.exe
---------------------------
E:\Emulators\gameboy advance\VisualBoyAdvance.exe

This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

---------------------------
OK
---------------------------

mudlord · Post by **mudlord** » Tue Aug 26, 2008 1:15 am

MSVC2008 SP1 files you need in that case.

From now on, we will use non SP1. Saves all the hassles Deathlike2 and co are having.

franpa · Post by **franpa** » Thu Aug 28, 2008 12:43 pm

http://vba-m.ngemu.com/vbam/vbacompiles ... ance634.7z
Fails to run for me, I have tried the included DLL files And the ones found in the same spot on the site.

---------------------------
E:\Emulators\gameboy advance\VisualBoyAdvance.exe
---------------------------
E:\Emulators\gameboy advance\VisualBoyAdvance.exe

This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

---------------------------
OK
---------------------------

Deathlike2 · Post by **Deathlike2** » Thu Aug 28, 2008 2:17 pm

franpa, I have zero idea how you even get those errors. A screenshot would be better served.. unless that's a log. Even then... there's something probably wrong with your setup... maybe you should reinstall DX... but it seems like a bigger problem at work.

Start here: http://tinyurl.com/63jo8z

mudlord, it's still looking for the new stuff (mfc90.dll and probably some more).

franpa · Post by **franpa** » Thu Aug 28, 2008 3:03 pm

The DLL files in the pic are currently the ones provided in DLL.ZIP. yes I did try the ones included with VBA-M but theres no difference in the outcome.

kode54 · Post by **kode54** » Thu Aug 28, 2008 8:46 pm

I can get the MFC build to run just fine, but for some reason, the Qt build crashes in ATI's OpenGL module.

I'll try updating my drivers a little later and see if that fixes the problem.

escapee · Post by **escapee** » Sat Aug 30, 2008 12:11 pm

I recieve the same error message as franpa. Build 589 is the last one to work properly for me. Windows XP SP3, everything up-to-date.

Simea · Post by **Simea** » Thu Sep 04, 2008 3:36 am

I had the same error as franpa and escapee. Try installing the Visual C++ 2008 redist. That solved the problem for me.

link

mudlord · Post by **mudlord** » Thu Sep 04, 2008 3:59 am

but for some reason, the Qt build crashes in ATI's OpenGL module.

For some reason, in my head, those 2 words bring a whole world of hurt. Though, it could be something simple on our end, like with mixing QPainter and OGL.

mudlord, it's still looking for the new stuff (mfc90.dll and probably some more).

Checked out the latest stuff? If not, I might have to make matters into my own hands.

franpa · Post by **franpa** » Thu Sep 04, 2008 3:03 pm

Yea deathlike, I did update directX, no difference. I looked at the eventlogs and found it was indeed refrencing VC90.CRT which I don't have.

Post by **odditude** » Thu Sep 04, 2008 4:29 pm

franpa wrote:Yea deathlike, I did update directX, no difference. I looked at the eventlogs and found it was indeed refrencing VC90.CRT which I don't have.

Simea wrote:I had the same error as franpa and escapee. Try installing the Visual C++ 2008 redist. That solved the problem for me.

link

franpa · Post by **franpa** » Fri Sep 05, 2008 2:58 am

Do you think I can be bothered downloading/installing something from microsoft that is hundreds of megabytes in size, just for one program?

is what I would be saying, but I checked the link and it is only 4mb, and it indeed worked

funkyass · Post by **funkyass** » Fri Sep 05, 2008 3:05 am

hundreds of megs? think again franpa

do you even bother following links... Why do I ask, you don't.

franpa · Post by **franpa** » Fri Sep 05, 2008 3:08 am

I was thinking the "redistribution" version was the whole thing and not just the runtime stuff. Like the Direct X bi-monthly updates and the DirectX redistribution pack.

mudlord · Post by **mudlord** » Fri Sep 05, 2008 6:00 am

*facepalm*

You mean the SDK, which is several hundred MB.

You only need the redist or the web updater on our server.

mudlord · Post by **mudlord** » Mon Sep 08, 2008 2:49 am

new Windows SVN compile out, for those that care.

Deathlike2 · Post by **Deathlike2** » Fri Sep 12, 2008 8:29 pm

The readme still links to the SP1 redist... which is not useful.

mudlord · Post by **mudlord** » Sun Sep 14, 2008 6:38 am

Stuff should be statically linked.

In other news, I quit working on this thing. I know spacy, chrono, blargg, nach, jonas and co will do a good job. chrono made some patches for UPS/PPF support if people even give a fuck for this code. plus fixed some memory leaks in the core. So, if someone can remove my "VBA Developer" tag, that would be great.

Thanks.

adventure_of_link · Post by **adventure_of_link** » Sun Sep 14, 2008 6:44 am

No problem, for the time being I guess this can be crunched, till a new head dev steps in.

It's been a good run.

also sorry to hear that Mudlord. Hope you'll be able to come back one day.