search for: simtel

| yes, the exit code will be 1 if any of the flac files failed | testing, else 0 (i.e. if all of them passed). Thank you, Josh! Now the only trick is to see whether command.com can do anything with that information.

...of the errorlevel limitation sighted above. This method won't tell you which files passed or failed. No there is no easy way to send standard error to a file so you can look at it; well not under command.com anyway. Cygwin will let you do it and there might be a wrapper utility somewhere on the simtel repository to do it as well; I think it is in sysutils or textutils in the msdos section. There might be a way to cludge around all this in Windows by using Perl and getting it to flac -t a file at a time but I honestly think cybwin would be easier. Regards, Kerry. On Sat, Dec 07, 2002 at 04:54:22...

Hi! I have problem with MEMDISK, because when I load modules in NW Client32 using NIOS.EXE commands, computer is restarted :-( Not everytime, but manytimes. The problem is with MSDOS 5.0, 6.22 and FreeDOS too. But when I create in DOS another RAMDISK and copy all data from MEMDISK to new RAMDISK and change settings and PATH to new ramdisk, all work fine. Directly from floppy or from

...ing there, but my upload throughput is in the range of 1 Mb per minute and the most generous storage quota I have is 50 Mb, so the dance of uploading filenames and downloading batch files would take much less time. | Cygwin will let you do it and there might be a wrapper utility somewhere | on the simtel repository to do it as well; I think | it is in sysutils or textutils in the msdos section. Cygwin looks like way too much for me to tackle and may be too much for my underpowered computer.

...unix command (ls,cat,sed,rm). Furthemore, make and this command must be able to overcome the MsDOS limitation about the length of a command. I used the ones coming with the djgpp compiler. According to me, they are the best version for dos and windows. You can find it in any SIMTEL mirror. If you want, I can make available a small file with only the needed tools. (3) The gnuwin32/Makefile use the g77 Fortran compiler. If you don't have it, or if you don't want to use it, you can use something like > make HAVEG77=NO or > make HAVE...

...unix command (ls,cat,sed,rm). Furthemore, make and this command must be able to overcome the MsDOS limitation about the length of a command. I used the ones coming with the djgpp compiler. According to me, they are the best version for dos and windows. You can find it in any SIMTEL mirror. If you want, I can make available a small file with only the needed tools. (3) The gnuwin32/Makefile use the g77 Fortran compiler. If you don't have it, or if you don't want to use it, you can use something like > make HAVEG77=NO or > make HAVE...

I am trying to build a simple dll with Rcmd SHLIB to link into R. The results of the build are below. From my limited knowledge of building DLLs, it looks like it worked (I didn't get any errors). F:\R\dlls> Rcmd SHLIB add.C making add.d from add.C g++ -IC:/PROGRA~1/R/src/include -Wall -O2 -c add.C -o add.o ar cr add.a *.o ranlib add.a g++ --shared -s -o add.dll add.def add.a

...unix command (ls,cat,sed,rm). Furthemore, make and this command must be able to overcome the MsDOS limitation about the length of a command. I used the ones coming with the djgpp compiler. According to me, they are the best version for dos and windows. You can find it in any SIMTEL mirror. If you want, I can make available a small file with only the needed tools. (3) The gnuwin32/Makefile use the g77 Fortran compiler. If you don't have it, or if you don't want to use it, you can use something like > make HAVEG77=NO or > make HAVE...