[Win98 + PB 4.50 + 4.51 RC 1] No compilation possible

[Shardik]

When trying to compile a program in Windows 98 SE using PB 4.50 or 4.51 RC 1
an error message is displayed.

If trying to compile a program or only just one line as for example

Code: Select all

Debug "Test" 

or

Code: Select all

MessageRequester("Info", "Test")

a message box with the title "PureBasic - Resource error" and the message
*** No message for error 0x8006 ***
is displayed.

In PB 4.41 the compilation works...

[c4s]

You probably did it already but how about reinstalling it and maybe deleting the preference files (located in the APPDATA path)?!

[Shardik]

You probably did it already but how about reinstalling it and maybe deleting the preference files (located in the APPDATA path)?!

In fact I tried it both and I also tried to start the PureBasic.exe with the /LOCAL and /PORTABLE
switch. And I always received the above error message when trying to compile any source
code.

[Shardik]

I have tried to install PureBasic 4.51 RC1 on a second PC with Windows 98
on which PureBasic had never been installed before, displaying the same
error when trying to compile as reported above. Is there any other user
who can confirm the finding that PureBasic support for Windows 98 is broken
since PB 4.50?

[Fred]

I just tried on my win98 installation and it works without problem. Do you have enough space on your boot drive ? You also probably need to install IE6 so you get the newer system libs

[Shardik]

@Fred,
thank you for testing. I just discovered my error. I had to uncheck "Enable XP skin support"
before compiling in Windows 98. In previous versions like 4.31 and 4.41 this definitely was
not necessary (I just tested it). So when crosstesting in previous PB versions in Windows 98,
Windows XP and Windows 7 I didn't have to remove the XP skin checkmark for Windows 98
when loading the source code from my fileserver and the source code contained "; EnableXP"
at its end...

[Fred]

That's good to know as it should actually work.. I will take a closer look to see what happens exactly.

[Rescator]

Maybe it's time to "split" the compiling?

I.e. instead of ASCII and Unicode choice, and XP Theme or no XP Theme, why not change all that so there is:

[ ] Windows 4.x (Win9x/NT4) (ASCII and no XP Theme, no Vista usermode)
[ ] Windows 5.x+ (W2K,XP,Vista,Win7) (Unicode and XP Theme on, Vista+ usermode choices available)

I'm only guessing here, but those who make Ascii apps usually wish to target Windows 4.x (Win9x and old NT),
and those who make Unicode usually wish to target Windows 5.0 or later (as unicode doesn't work on Win9x anyway).

And since Windows4.x apps still work on Windows5.x I don't think it's that much of an issue to "split" old and new this way.
I myself have stopped supporting anything older than Windows 5.0 (Windows 2000) so I only do Unicode apps with XP Theme now and also use Vista usermode settings.

And slowly starting to move the older Windows 4.x stuff into Legacy status might help future development.
(a lot of the old APIs are deprecated on Windows 5.0 and later, and it would allow the compiler to use "new" Windows 5.0+ API's where appropriate)
It kinda would make sense too as PureBasic 4.xx could then eventually become the "Legacy" (ASCII, Win9x/old NT) branch and PureBasic 5.xx supporting only Windows 5.0 and later (Unicode, XP Theme, +vista usermode support, and taking advantage of Windows 5.0+ features where available).

I'd be happy to "re-purchase" PureBasic for that indeed

But for now, consolidating ASCII and XP Theme etc. into a Legacy and Modern toggle should avoid most of the issues currently I think.
It certainly seems like people forget that XP Theme and Unicode is only supported on Windows 5.0 or later, and that a manifest can cause issues with Win9x.
Sorry I can't recall what exactly, but there is a tweak needed to the manifest. (just like there is a tweak needed to the Vista user mode manifest to avoid it crashing on XP SP2, ugh).

[DoubleDutch]

I tried to compile my program in Windows Me (fresh install, all updates installed) and have the same error using a fresh install of 4.51 - I tried turning off the XP skin support - no difference.

[DoubleDutch]

If I turn off the icon and vista user mode request it works. Must be something to do with the resources...

[Shardik]

If I turn off the icon and vista user mode request it works. Must be something to do with the resources...

Confirmed for Windows 98 SE and PB 4.51 final.

The following options in "Compiler Options" have to be turned off, otherwise the
compilation fails with the error message "*** No message for error 0x8006 ***":
- Use icon:
- Enable XP skin support
- Request Administrator mode for Windows Vista
- Request User mode for Windows Vista (no virtualisation)

In PB 4.41 all these options may be turned on and don't produce any compilation
error in Windows 98 SE.

[Fred]

FIxed the issue, all is back to normal on the Win9x side