Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: (split) windows 9x support (Read 6259 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

(split) windows 9x support

Egotistical egostroking question

Since Foobar doesn't run on Win98, will this mean that us 98'ers are left without you coding goodies for our old machines too.

Dangnabbit

And a semi-non-techie question. Why can't Foobar run on Win98?
 

(split) windows 9x support

Reply #1 –
Quote
Egotistical egostroking question

Since Foobar doesn't run on Win98, will this mean that us 98'ers are left without you coding goodies for our old machines too.

Dangnabbit

And a semi-non-techie question. Why can't Foobar run on Win98?

Unicode features that are supported only on XP/2k are not supported by Win98 (look at in_vorbis config in WA2 config - it also tells something about unicode features).

(split) windows 9x support

Reply #2 –
i've been dreaming about nuking win9x support in all my code for months, now i can finally have it and i enjoy it.
killing win9x support nicely avoids all the mess with "unicode support" and international characters in filenames. making fb2k run on win9x would require huge amount of stupid hacks everywhere, just to wrap calls to all unicode functions that aren't supported on win9x; IMO it's not worth it, since even microsoft drops win9x support.

< insert flame about windowx 9x stability and being generally useless for work of any kind >

and no, i don't use xp, i have win2k on both my boxes, not planning to ever replace it with anything else, at least on these machines.
Microsoft Windows: We can't script here, this is bat country.

(split) windows 9x support

Reply #3 –
Is it because of XP styles, buttons, big icons or something else (I use custom manifest for foobar - looks much nicer to me )?
BTW, why don't you like caps?

<9X flaming>
Have I ever told you how crappy this shit is?
</9X flaming>

(split) windows 9x support

Reply #5 –
well, OK, i can remove the startup error (for whatever next build comes out after 0.28), good luck trying to get it to work. you will need redistributables linked above.
Microsoft Windows: We can't script here, this is bat country.

(split) windows 9x support

Reply #6 –
Isn't the unicode issue a "tag display" issue only here.

If so, I'd say stick displaying tags up someone's bum. If Foobar is so good as people make it sound like, I could probably handle a tag-handicapped or tagless Win98 version

(split) windows 9x support

Reply #7 –
its about *all* text being WCHAR* internally, not just tags.
i might take the "win9x challenge" when i get totally bored, i guess i have more amusing things to do now.
even if it ever runs on win9x, expect things to be fuct since i'm not getting near to any machine running win9x, so random weird problems will happen.
Microsoft Windows: We can't script here, this is bat country.

(split) windows 9x support

Reply #8 –
Quite understandable.

Don't mind me. I'll just sit here pegged, pining for Foobar looking out at the fjords in the meantime.

(split) windows 9x support

Reply #9 –
Or you could free up a couple of gigs for a new NTFS partition and install 2000 or XP. Or maybe I'm just spouting nonsense here. ;P

(split) windows 9x support

Reply #10 –
been trying to put some basic modifications in the direction of making the exe run on win9x, result: accidentially broke unicode somehere, nowhere close to actually making it run on win9x.
i think it might be possible to make a separate compile for win9x tho, that sounds relatively painless.
Microsoft Windows: We can't script here, this is bat country.

(split) windows 9x support

Reply #11 –
Well, I've downloaded the redistributables,
and it still doesn't work.

Quote
From M$DN:
To compile an application that uses MSLU

  1. Add the following two files to your project:
         * UnicoWS.dll -- the Microsoft Layer for Unicode DLL
         * UnicoWS.lib -- the LIB file to which you link

         Thus, do not put UnicoWS.dll there unless you are running from
a system process that is located there. Instead, keep the UnicoWS.dll
in your application directory and call LoadLibraryA yourself to ensure
that you load the correct .dll.
  2. Add the following to the link options for your application
(note that these libraries are not separated by commas because
that is how you add them to the link list):
         * First, add the following: /nod:kernel32.lib /nod:advapi32.lib
/nod:user32.lib /nod:gdi32.lib /nod:shell32.lib /nod:comdlg32.lib
/nod:version.lib /nod:mpr.lib /nod:rasapi32.lib /nod:winmm.lib
/nod:winspool.lib /nod:vfw32.lib /nod:secur32.lib
/nod:oleacc.lib /nod:oledlg.lib /nod:sensapi.lib.
         * Then add UnicoWS.lib.
         * Finally, add the libraries that the Microsoft Layer for
Unicode uses explicitly: kernel32.lib advapi32.lib user32.lib gdi32.lib
shell32.lib comdlg32.lib version.lib mpr.lib rasapi32.lib winmm.lib
winspool.lib vfw32.lib secur32.lib oleacc.lib oledlg.lib sensapi.lib.
In this step, omit any libraries listed after kernel32.lib whose APIs
are not used in your application. However, if your application
uses another component, such as MFC, ATL, or CRT, be sure to
include any libraries on which the component depends.

UnicoWS.lib is in Platform SDK, which probably is included with MSVC++.

You could put this redistributable on your page. It is there:
http://download.microsoft.com/download/pla...-US/unicows.exe
It is 262 KB long.
I've changed only because of myself.
Remember, when you quote me, you're quoting AstralStorm.
(read: this account is dead)

(split) windows 9x support

Reply #12 –
Quote
I use custom manifest for foobar - looks much nicer to me

Is there somewhere I can go to find how to do this? Custom manifests sound interesting...

(split) windows 9x support

Reply #13 –
Quote
Well, I've downloaded the redistributables,
and it still doesn't work.QUOTE]

You could put this redistributable on your page. It is there:
http://download.microsoft.com/download/pla...-US/unicows.exe
It is 262 KB long.

so this works by statically linking shit to executable ? meh....
i believe i have nt4 working now in current pre-0.32 (you just need to switch outputs in config before attempting to play). current source should compile for win9x with just a bunch of different global #defines, i'm too lazy to check it now, but there are real chances of 0.32 having separate set of executables running without unicode.
Microsoft Windows: We can't script here, this is bat country.

(split) windows 9x support

Reply #14 –
current pre-0.32 ANSI build confirmed running on win98se.
Microsoft Windows: We can't script here, this is bat country.

(split) windows 9x support

Reply #15 –
When will it be on site? I'm eager to test it...
I've changed only because of myself.
Remember, when you quote me, you're quoting AstralStorm.
(read: this account is dead)

(split) windows 9x support

Reply #16 –
i guess 0.32 will be delayed a little bit because windowsupdate has just happily hosed my laptop.
for future reference: if you ever see "updated keyboard/mouse drivers" on windowsupdate, dont install them.
Microsoft Windows: We can't script here, this is bat country.

(split) windows 9x support

Reply #17 –
Nah. Don't even try to install any drivers from Windows Update. SP's and hotfixes are good, drivers are bad.