Michel: Although I have not used musixflx.exe on Win XP, I routinely run it on Win2K and Win98 (at home)... I am not sure what may cause the problem you are having, but I will offer some suggestions.
Just to test a more recent compile, I downloaded the musixflx.c file archived in: http://icking-music-archive.org/software/musixtex/musixflx.zip ... and I recompiled it with Microsoft Visual C++ (as a C console program) on my Win98 installation (okay... not recent here!:-). I don't think it will make the difference, but you can try running that executable if you like... I put it on the web at: http://www.i2k.com/~jhunsberger/dlfiles/musixflx_msvc60.zip This musixflx.exe should be the same as the Win32 musixflx.exe already in the archive. If anything helps, it would be some dependency rooted in updates to the MSVC runtimes... It is more likely that the .TeX input has something to do with it. Possibly there is a quirk related to some special feature. If you can provide your .TeX file, it may be possible to track down what is causing the problem. I do know that musixflx.c code is NOT an example of particularly good C coding! :-)... It was conceived in the very early days of MusiCTex (now MusiXTex) to handle the calculation of spacing across each staff. A few have attempted to improve it, with the last activity being a bug fix in 1997 to handle 'sign changes in Xbars, at the end of measures, when MusixTex revokes the need to accommodate the extra space...' which was not anticipated within musixflx, but this got fixed. Although the code is old, it is hardly worth recoding, since it would probably be more of a problem in the end. Try running musixflx.exe in DEBUG mode... The command line: > musixflx file f (adding the 'f' character) causes musixflx to show statistics for each output line, one by one, and the results shown are also stored in a debug output file 'file.mxl' where file.tex is the file you are processing. At least you could see how far musixflx is getting before failing. The command line: >musixflx file s (adding the 's' character) causes musixflx.exe to print a summary of spacings calculated for each line. Again, you may be able to see how far it is getting. Another approach may be to decimate (reduce) your input file in stages, and try to isolate the input code that causes musixflx to choke. Possibly there is a \mulooseness setting with a parameter out of bounds? Does musixflx always quit, or do you have any input files where it does work? It is very likely that one setting or another may be 'out of bounds' for musixflx, although MusixTex does not care about it. Hopefully you can find the offending setting, and maybe it can be avoided by changing it (in the MusixTex input code.) Good luck. Joel Hunsberger ----- Original Message ----- From: "maurizio codogno" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 06, 2004 11:19 AM Subject: [TeX-music] [ADMIN] Forwarding message > I do not know why the messages from Michel got blocked - maybe > there is some attachment... > > ciao, .mau. > > >From: "Michel Steudler" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Subject: Problem using musixflx > >Date: Wed, 6 Oct 2004 17:11:43 +0200 > > > > > >Dear all, > > > >this is the continuation of a mail I sent this morning. > > > >I'm starting with M-Tex, with Windows XP. I am able to generate a .mx1 > file, > >but when I run musixflx.exe, I have the following message : > > > >Exiting due to signal SIGSEGV > >General protection fault at eip=00006b0b, and so on... > > > >So the .mx2 is not created, and I guess it's for this reason the PDF file > >is unreadable. > > > >Have you an idea about this issue? > > > >Thanks in advance. > > > >Best regards. > > > >Michel Steudler > >Fine messaggio allegato > > > > > _______________________________________________ > TeX-music mailing list > [EMAIL PROTECTED] > http://icking-music-archive.org/mailman/listinfo/tex-music > _______________________________________________ TeX-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
