kernel32.dll problem at Win98

[Sisophon2001]

Hi:

I tested FreeBASIC code on Win ME and Win XP using Screen 19 and Screen 13 with no crashes.

On WinXP screen 13 failed to select fullscreen, but backed up to windowed mode and worked correctly. The same exe selected fullscreen on WinME. Screen 19 worked identically on both computers.

Garvan

[MystikShadows]

I would say, just to be on the safe side, to make sure that you compile your EXE on the platform that you are testing on.

Compile on XP if you will run it on XP, compile on Windows 98 if you'll be running it on 98....Se of that temporarily fixes the problem.

In a VB program I've worked on, I had to do that on applications that made excessive use of the Windows API for example. It helped the problem itself and it also helped create the right "installation package" for the application as well....no garantees it will fix your problem. But it might, in which case, FreeBasic could perhaps detect the windows version when compiling or something to filter things out.

Let me know if it works...if it's what you've been doing all along, compiling on the respective platform, then disregard this message as it will not help you ;-).

[lillo]

Sorry to say this but it doesn't make sense to use a different environment to compile onto. A Win32 program compiled under WinXP should work also on older Windows versions, as long as the program doesn't make API calls introduced in WinXP. Shame on MS though as they also changed many existing API calls since the Win95 days, sometimes breaking compatibility; so a library like gfxlib should take care to use only calls compatible among different Windows versions... and that's the point. Too bad I'm a newbie when it comes to lowlevel Win32 API development (gfxlib is my first experience with it!) so I don't know all the quirks yet. But I'm learning

BTW, SCREEN 13 could not work in fullscreen on some machines as DX could not support it for your card. By default lowres modes are handled using ModeX by DirectX, and maybe your card doesn't support it. Now I just made gfxlib to force DX to use BIOS mode 13h for 320x200x8 mode, so it should work. Fix in CVS (use the recent fbc binary and runtime lib posted on this thread with gfxlib CVS snapshot)

[fielden]

Ver 13 fixed my 98 problems with ListView and RichEdit, I thougt it was my sorry programming. I was getting a GPF with ListView and one when I clicked in a RichEdit Box, but they did work with XP alright.

Thanks.........Jerry Fielden

[Monty Python]

Hi, I still have the same problem even after downloading an altered graphic library linked in a different thread.

I can PM the fault logs if they will help at all.

Monty.

[lillo]

It'd be nicer if you could hang on the IRC channel #badlogic at EFnet; look for me and we'll try to find the problem together...

[Sisophon2001]

Hi, I still have the same problem even after downloading an altered graphic library linked in a different thread.

I can PM the fault logs if they will help at all.

Monty.

Hi:

Downloading the gfxlib in other posts can screw things up unless you have the latest CVS, and have compiled it yourself. The FB versions are moving very quickly, and compatibility with development and user versions are now a problem.

The only solution is more frequent beta releases. I am looking forward to 0.13

Anybody listening?


Have fun.

Garvan

[lillo]

Hopefully 0.13 will be out soon. I just finished making the runtime library fully thread-safe, and this was a major stopper for the new release, at least for me. V1ctor?

[v3cz0r]

Sure, I'm just waiting for the contributions with examples for the new libs (please help :P), and i will finish the var-initializers support, TYPE's and run-time are missing, the most complex anyway.. heh

[Monty Python]

Hi, sorry I haven't posted or been on chat but I am experiencing a few problems with this computer now and I have a feeling it may be hardware related (done all the malware scans, reinstalled drivers etc. it made no difference) so what I'm saying is that this problem may not be due to FB.

Thanks for all you replies and will try FB again when I have this figured out,

Monty.