From: mcchow AT onebox DOT com (Jabez McClelland) Newsgroups: comp.os.msdos.djgpp Subject: Re: Allegro: slow install_sound() on 486 Date: 28 Nov 2001 19:50:32 -0800 Organization: http://groups.google.com/ Lines: 32 Message-ID: References: NNTP-Posting-Host: 66.92.149.119 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1007005832 19844 127.0.0.1 (29 Nov 2001 03:50:32 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: 29 Nov 2001 03:50:32 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote in message news:... > On 27 Nov 2001, Jabez McClelland wrote: > > > install_sound(DIGI_AUTODETECT,MIDI_NONE,NULL) still > > takes 36 seconds. Rats. Any further ideas? I'm thinking of copying > > the code for install_sound() to my_install_sound() and adding a bunch > > of timing diagnostics... But that's messy. Surely someone out there > > knows what's going on in this function and can chime in? > > Since the sources are freely available, that someone could be you. > Adding time measurements to the function and reporting results here > might just be the missing piece in this puzzle; armed with that > information, either you or someone else could find the reason and > suggest a solution. Problem solved! This is really moronic of me. I never ran setup.exe, so I never made an allegro.cfg file. Apparently things still run without the allegro.cfg file, but the routine must wait for a timeout of some kind. Now that I have allegro.cfg, it's lightning fast! (well, it's still a 486...) Thought I'd post the resolution to this in case there are any lurkers. How about adding the following FAQ: Q: Why does install_sound take so long to execute? A: Be sure you have run setup.exe and created a configuration file allegro.cfg. Bye, Jabez