-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error 0xc000007b appears out of nowhere #152
Comments
You mean it's not fixed yet?
…On Thu, Sep 14, 2023, 23:11 Linkinho ***@***.***> wrote:
The new version isn't working use version 1.6
—
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARF4YJTVFOPFYUC4X3KMT3DX2NXJZANCNFSM6AAAAAA4LS43WI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The 0xC000007B error is a very generic Windows error. It could have several causes, from corrupted sys files, missing files, or the incorrect dlls for example. What version of Windows are you using? I've tested GBE+ 1.7 on a few different Windows machines (2 on Windows 10 and 1 on Windows 8), so I'd need more details to figure out what's going on. |
im using windows 10 |
Would be good if this was fixed in later version
…On Sun, Mar 10, 2024, 11:13 Ivan951236 ***@***.***> wrote:
same thing...
Untitled.png (view on web)
<https://github.com/shonumi/gbe-plus/assets/101629412/6eeb30ac-c409-4f15-b519-3d2a99b029fe>
I'm also using Windows 10
—
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARF4YJXNXCVC5LX7QK2MPK3YXQW5JAVCNFSM6AAAAAA4LS43WKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBXGE3TCOBSGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Like I said, the error listed is very, very generic. It's basically Windows saying "There was a problem" and not being anymore specific than that, which makes it very hard to pinpoint. If anything, it's probably Qt related. The CLI version seems unaffected. This is likely another reason to eventually move away from Qt entirely in future versions. |
There wasn't cli version on page
…On Fri, Mar 22, 2024, 20:44 D. S. Baxter ***@***.***> wrote:
Like I said, the error listed is very, very generic. It's basically
Windows saying "There was a problem" and not being anymore specific than
that, which makes it very hard to pinpoint.
If anything, it's probably Qt related. The CLI version seems unaffected.
This likely another reason to eventually move away from Qt entirely in
future versions.
—
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARF4YJTDXZRAAFIUH5W3M63YZSCZPAVCNFSM6AAAAAA4LS43WKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVG44TGMRUGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The command line version is the file gbe_plus.exe. It's included with the Qt version gbe_plus_qt.exe. |
i don't know why i get it even if i have missing files present
The text was updated successfully, but these errors were encountered: