World: r4wp

I could have used you in the past week, but I just fixed cURL networking 
on Windows, after setting up a Windows installation for the first 
time in almost a decade

:-)

We still have a problem playing sound with SDL on Windows, so if 
you could do something there, that would be great

Well good thing is that I have access to good size lab at work.

Can you reproduce the problem?

Yes, it produces an error on XP, but on 7, you see it play in the 
mixer without producing any sound

Even odder is that it just works on WINE

If I can reproduce it then we should have no problem fixing it.

What is SDL?

The error on XP seems to be related to DirectSound. Perhaps it needs 
a newer DirectX or a driver, but I'd think SDL would drop down to 
a more primitive sound system

http://www.libsdl.org

The test binaries are here:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip

It's best to use the MSDOS folder. The Windows folder is less complete 
and compiled as GUI apps, so no command line output

The SDL audio program is MSDOS\RedSystem\play-SDL-wav.exe. There's 
a test file sample.wav

Ok, lot of stuff there. So let me explain how I typically operate 
to make this the easiest way for me to help.  I need ONLY the relevant 
files to install, complete with same instrucitons for installation 
that produced the error.  I need to know specific versions as well. 
 Once I know I can re-create the problem, then I need sources (at 
least any programming sources you have) and any symbol files you 
may have or can generate (pdb) files preferred.

If you wait half an hour, I'll have new binaries

No problem Kaj.

No installation is needed, but Red doesn't generate extra symbol 
files

Paul: all of them. :-)

I don't have any older XP in the house so I may have to do it in 
the lab at work or install it via as a VM and see if it reproduces.

No problem Doc.

The source is here:

As Kaj said, we do have somtimes odd issues on Windows with some 
third-party libs.

http://red.esperconsultancy.nl/Red-SDL/dir?ci=tip

Yeah, I spend the days debugging control systems and lots of third 
party stuff.

I do my share too from time to time using IDA Pro. ;-)

Yeah, I am familiar  with IDA Pro, but we use WinDBG mostly.

I'm using it also sometimes, but IDA is really great.

Yeah I hear good stuff about it.

We do on premises debugging a lot in front of customers so we have 
to use WinDBG.  Plus some of the software engineers I work with know 
the tool pretty well.  I work with a lot of peole from Sybase, Siemens, 
Rockwell, GE

I franckly sometimes wouldn't mind some more arms for debugging native 
stuff as it can be quickly time-consuming.

not a problem.

What native architectures are you targeting with RED?

We talking ARM, and Intel?

Currently we support IA-32 (Pentium 1 being the lowest CPU supported) 
and ARMv5.

Excellent.

In the future, we will target also higher version of ARM, Thumb ARM 
mode, and IA-64.

Fresh binaries have arrived in the test repository

those binaries also exhibiting the same behavior?

Yes, the SDL problem has been very stable

The easiest way to get all the files is to use the download.r script:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip

Put it in a folder with a Fossil executable and just run the script 
with REBOL

http://www.fossil-scm.org/download.html

What all is that going to download?  Just Red or does that include 
SDL also?

Not really Red, but the compiled executables in the test repository. 
The needed libraries are also in there, including SDL, so you can 
run the programs straight away from their folders

The script also downloads the sources of all the bindings used, including 
the Red/System SDL binding

I was going to run download.r with REBOL but when I double clicked 
it - it launched.  I'm assuming fossil.exe had something to do with 
that.

Fossil shouldn't affect that. What do you mean by launching?