Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Marton
Sounds great, Arkady. I'm glad my code at least helped to see the bug. Please let me know if/when you fix it so I try it :) Thanks!! Marton Arkady V.Belousov wrote: > > Hi! > > 18-Сен-2006 15:29 [EMAIL PROTECTED] (Marton) wrote to > freedos-user@lists.sourceforge.net: > > M> Absolutely, the

Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Daniel Franzini
wellthis is not the "right" way to do what you want to do...altough it seems to work, despite any possible problems with FreeCOMDOS has its own, more elegant, API for file/directory listing...look for functions findfirst/findnext...they should be avaliable on your C compiler... On 9/18/06, Marton <

Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Arkady V.Belousov
Hi! 18-Сен-2006 15:29 [EMAIL PROTECTED] (Marton) wrote to freedos-user@lists.sourceforge.net: M> Absolutely, the function is simple... just to see if two directories that M> should have the same contents changed. Here it goes (hope it indents well): M> int checkdir(void) { [...] M> system("di

Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Marton
Absolutely, the function is simple... just to see if two directories that should have the same contents changed. Here it goes (hope it indents well): int checkdir(void) { int i, filesize = 0; FILE *fp, *fp2; system("dir c:\\data\\base1 >c:\\data.dir"); fp = fopen("c:\\data.dir","

Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Arkady V.Belousov
Hi! 18-Сен-2006 11:21 [EMAIL PROTECTED] (Marton) wrote to freedos-user@lists.sourceforge.net: M> I tried that exact version, when I type "ver" I get "FreeCom version M> 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]"... and the issue still M> happens... Current FreeCOM deals with "/c" option

Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Marton
I tried that exact version, when I type "ver" I get "FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]"... and the issue still happens... Arkady V.Belousov wrote: > > Hi! > > 18-Сен-2006 04:44 [EMAIL PROTECTED] (Marton) wrote to > freedos-user@lists.sourceforge.net: > > M> With "c

[Freedos-user] FreeDOS 1 install problem

2006-09-18 Thread crm
FreeDOS 1 installs to hard disk fine, but after reboot I get ..Error! If I hit enter it asks me to insert the boot disk in Drive A. It appears that Drive A is the DVD ROM drive containing the FreeDOS install CD. The live option runs just fine. For some reason it does not seem to be looking a

Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Blair Campbell
That would be the edition. On 9/18/06, Arkady V.Belousov <[EMAIL PROTECTED]> wrote: > Hi! > > 18-Сен-2006 04:44 [EMAIL PROTECTED] (Marton) wrote to > freedos-user@lists.sourceforge.net: > > M> With "current" you mean 1.0, or the latest build? 'cause I tried 1.0 > without > M> luck... > >> Tro

Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Arkady V.Belousov
Hi! 18-Сен-2006 04:44 [EMAIL PROTECTED] (Marton) wrote to freedos-user@lists.sourceforge.net: M> With "current" you mean 1.0, or the latest build? 'cause I tried 1.0 without M> luck... >> Trouble not in "delay for flush", trouble that (old) FreeCOM was >> buggy. >> Current FreeCOM deals with

Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Marton
With "current" you mean 1.0, or the latest build? 'cause I tried 1.0 without luck... Thanks!! Marton Arkady V.Belousov wrote: > > Hi! > > 16-Сен-2006 08:43 [EMAIL PROTECTED] (Marton) wrote to > freedos-user@lists.sourceforge.net: > > M> Many thanks for the suggestions but instead of doing s

Re: [Freedos-user] Need help ... calling COMMAND.COM from C

2006-09-18 Thread Arkady V.Belousov
Hi! 16-Сен-2006 08:43 [EMAIL PROTECTED] (Marton) wrote to freedos-user@lists.sourceforge.net: M> Many thanks for the suggestions but instead of doing stuff in my code... M> couldn't we somehow add a delay to FreeCOM before it exits (when called with M> /c) so everything gets flushed and it works