playing MODs

Thread View: borland.public.cppbuilder.multimedia

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by dArK cHAriSmA Sun, 16 Oct 2005 22:15

#79

Author: dArK cHAriSmA
Date: Sun, 16 Oct 2005 22:15

1 lines
992 bytes

Does anyone know how to play *.MOD(MadTracker or the like) files with BCB.

Re: playing MODs

#80

Author: Paw Suddergaard
Date: Mon, 17 Oct 2005 09:15

3 lines
1025 bytes

http://www.fmod.org/

/Paw

Re: playing MODs

#102

Author: dArK cHAriSmA
Date: Mon, 05 Dec 2005 13:18

27 lines
2196 bytes

  Paw Suddergaard wrote:

> http://www.fmod.org/
>
> /Paw

Thanks for the link Paw, but I coudn't make it work. I've downloaded 
both FModAPI.exe and miniFmod.zip and after many tries it always ended 
up with beautyful /[Linker Error] Unresolved external/...

After I read some posts about *.lib I've concluded that there is no way 
of using a lib that has header like this: !<arch>... which is 
minifmod.lib. Coff2Omf never helped me in these cases. So I gave up with 
minifmod and libs of that kind for my BCB5.
 On the other hand FModApi offers fmodex.dll(which can later be 
ImpLib-ed) or complete *valid* version for BCB: fmodex_bc.lib. So I have 
them both in project dir and .lib's path is in Directories/Conditionals 
page entered propertly as well as header file(s) in Unit1. Nevertheless, 
after initializing FMod I always get:
/[Linker Error] Unresolved external '__stdcall FMOD::System::init(int, 
unsigned int, void *)' referenced from 
$(BCB)\PROJECTS\MINIFMOD170\UNIT1.OBJ/.

Do I need to use RegSvr32 on DLL before linking? What am I doing wrong? 
I've tried any solution I came up with, which is obviously bad.

Faithfully, Danijel

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads