I often get this message:
[attachimg=1]
Any idea whats bad? (It also happens when I only fire up WinApe and leave it a while alone!)
I usually get this message when compiling a program with a incbin"" or read"" command with incorrect filename
Which OS do you use? Under Win7 if the sound card is deactivated, you'll get that kind of error.
Quote from: Devilmarkus on 01:30, 09 January 12
I often get this message
I get it with address "00499737" on Windows 7, when I want to leave the full screen mode. (F10)
Well, I never hat that problem with WinApe and Windows 7.
Can this error be reproduced with a freshly started Windows 7 and only using WinApe?
I assume that another program may be responsible for this error (since I never ever got it).
Thanks for the feedback, I'll try and fix the read/incbin issue, and send you the latest version of the executable so I can find the error address Markus. Does this happen when a screen saver is about to start?
No, I have no screensaver active.
But it mainly happens when I bring WinApe back to top.
Or when I play around with debugger/assembler (WinApe window then has no focus)
Quote from: TFM/FS on 19:31, 09 January 12
Well, I never hat that problem with WinApe and Windows 7.
Can this error be reproduced with a freshly started Windows 7 and only using WinApe?
I assume that another program may be responsible for this error (since I never ever got it).
Stay humble... Don't search elsewhere before watching at home.
The only reason of crashes are untested NULL pointers, because unexpected cases are not handled by this program.
Well the bug appeared again.
I forgot to post the error message before:
[attachimg=1]
How it happened?
- I opened a DSK file with WinApe
- I opened the filemanager (CTRL+F1)
- I dragged'n'dropped a file to a folder on my PC (Winape then was minimized)
- When I wanted to maximize it back, this bug happened.