Anyway, I just downloaded a new rom fresh, and it won't run zipped or unzipped, and my other versions of VBA won't run it either. All of my GB/GBC roms I tested run perfectly, and they're in the same folders and everything (e.g. I doubt that only the GBA roms would get corrupted and nothing else).
Â
He did try it on VBA, I think [img]<fileStore.core_Emoticons>/emoticons/unsure.png[/img]/emoticons/unsure@2x.png 2x" width="20" height="20" />
Â
What ROMs are you using?
Iconoclast, if you're not going to read my posts thoroughly and just jump to conclusions about me, how are you supposed to solve my problem?
Â
vba-m doesn't need any dll's or codecs to run games, all of it is self contained for the most part now.
DirectX, OpenGL...
Â
He did try it on VBA, I think [img]<fileStore.core_Emoticons>/emoticons/unsure.png[/img]/emoticons/unsure@2x.png 2x" width="20" height="20" />
Â
What ROMs are you using?
I tried Super Mario Advance, Pokémon... y'know, the big ones. Or do you mean something else?
Â
Let's see... ROMs are clean, emulator works fine for others, DirectX up to date, all DLLs present and accounted for...
I'm stumped. [img]<fileStore.core_Emoticons>/emoticons/sad.png[/img]/emoticons/sad@2x.png 2x" width="20" height="20" />
Last ideas I have, since I can't think of anything else, is that you could need bios files. I know that it's doubtful you will need those, I'm just suggesting. If you already have those, then if you haven't already, try playing without them. If it still doesn't work, then try switching rendering engines. If that doesn't work, then.... there's no other idea I got.
He did try it on VBA, I think [img]<fileStore.core_Emoticons>/emoticons/unsure.png[/img]/emoticons/unsure@2x.png 2x" width="20" height="20" />
Â
Well that deduces less that the "Core", VBA-M "Bugs and Support" forum was an appropriate placement, if the issue persists across the core of any GBA emulator the user was willing to try. But I suppose it's hard to think what better forum this mistaken little incident could have gone in.
Â
It's one thing to tag details at the end, but it's more important that the tester is thorough with retrieving the information. Actually testing another emulator does not necessarily correlate to the information I could have meant. Just as an example, the user could have lazily used the installation of VBA in the same read-directory as VBA-M, which could have only deceived him into thinking he ruled that possibility out because libraries are still being shared by both packages.
Â
It's not a fault within VBA-M if the user is not thorough enough with his experiments. [img]<fileStore.core_Emoticons>/emoticons/smile.png[/img]/emoticons/smile@2x.png 2x" width="20" height="20" />
Â
For example,
Â
Let's see... ROMs are clean, emulator works fine for others, DirectX up to date, all DLLs present and accounted for...
I'm stumped. [img]<fileStore.core_Emoticons>/emoticons/sad.png[/img]/emoticons/sad@2x.png 2x" width="20" height="20" />
Â
Things like "DirectX up to date" and whether DLLs are present, have nothing to do with things like ROM info not working and GBA-only-specific ROM initialization failures (e.g. missing libraries would have raised an initialization fault prompt in the OS). "Accounted for" is a repetitive phrase re-instating his notion of "present" to further deduce his lack of creativity and thinking about his individual issue from the hints being offered.
Â
Although, insofar as the possibilities, I agree with Universal that the BIOS setting is definitely possible, since the original poster stated that GB and GBC games work, but not GBA. BIOS bins are platform-specific after all.
Â
if you're not going to read my posts thoroughly and just jump to conclusions about me, how are you supposed to solve my problem?
Â
Even if the thread was in the correct forum, the only one here who can fix your problem is you. We don't have access to your computer testing environment to do things right for you, and we can't give you medicine to control how you behave. [img]<fileStore.core_Emoticons>/emoticons/smile.png[/img]/emoticons/smile@2x.png 2x" width="20" height="20" /> It is a good idea to use your ability to listen to others' ideas while thinking about your problem on your own, so that you can solve it. Simply feeling like you're being attacked, judged, and lectured by the right and wrong ideas doesn't automatically fix your problem for you.
Â
If you would like to change the discussion about conclusions being made about the problem versus you that I am sure can go in another forum please.
Â
Good luck.
disable your shit antivirus's sandbox mode.
Last ideas I have, since I can't think of anything else, is that you could need bios files. I know that it's doubtful you will need those, I'm just suggesting. If you already have those, then if you haven't already, try playing without them. If it still doesn't work, then try switching rendering engines. If that doesn't work, then.... there's no other idea I got.
I only have the GBA bios, I think. I tried it with and without it on.
I already tried the switching the engine too (that was part of what I meant by "no matter what I do").
It seems I have a one-in-a-million problem here. Thanks for trying though. [img]<fileStore.core_Emoticons>/emoticons/sad.png[/img]/emoticons/sad@2x.png 2x" width="20" height="20" /> Maybe I should try it on a newer version of Windows.
Â
disable your shit antivirus's sandbox mode.
What the heck does that even mean? XP doesn't even have any antivirus software. It's on VMware, so I don't even need it. Even if I had, how do you know it's bad or has a "sandbox" mode?
Even a windows system inside a Virtual Machine requires an antivirus software. VMware even tells you that. A Virtual Machine is still considered a computer and some viruses could get on there. But that's besides the point of this thread. As for a sandbox mode, that's where it copies the file into an area of the hard drive and makes it believe it's still in it's normal spot. Best place to see this example is http://sandboxie.com/
Â
Still, if other software can't even read the rom data, then it's more than just a problem with the emulator. For all you know, there could be a virus that you non-existant virus scanner didn't see on your virtual machine.
Indeed another likely possibility. Not to mention, Windows XP is theoretically about the least secure operating system at this stage of time (insofar as current susceptibility to infections).
Â
That would have been an important piece of information to specify to begin with, but I think that with responses like this:
Â
What the heck does that even mean? XP doesn't even have any antivirus software. It's on VMware, so I don't even need it. Even if I had, how do you know it's bad or has a "sandbox" mode?
Â
The end user is knowingly skipping critical information such as the machine type (virtual, which is highly sensitive to changes over the years), and waiting for responses like squall's so that he can "retaliate against them" by only then choosing to specify that information as though everyone should have known all along.
Â
Additionally, he declined to honor any of the rules for posting in this forum:
http://vba-m.com/forum/Thread-when-reporting-bugs
even though some of those were indirectly, "relatively" specified.
Â
There should have been more things added to that thread like the operating system. Allowing a virtual machine emulation environment is a huge difference in emulator support.
Â
So due to continual absence of adherence to the forum support rules, contemptuous posting, and off-topic assertions, user support is adjourned until since a two-day timeout.
Â
The thread has been moved outside of the "Core" forum since it has nothing to do with core issues and is a generic attempt to request support.
a vm shouldn't cause GBA roms to goof, however a clean unpatched XP running in a vm might be missing a required instruction if the user has dropped msvc dll's into the directory.
Yeah, the gist insofar as that point was that you've seen people nagging other emulators like Project64 with bug reports who were really using Macintosh + a VM, but yes I generalized.
Â
Either the actual operating system or an indicator in the form of whether the emulation thread is running physically or on a VM is what I meant.
