Re: Bug in DOSemu-FreeDOS-bin?

Re: Bug in DOSemu-FreeDOS-bin?

[Stas Sergeev]

Hello.

kontrare wrote:
> i dont know if this will help but i seem to remember
> doing a bit of  coding a ways back and using
> fopen("c:\filename","r+b") in dos it wouldn't see the
> file till i did fopen("c:\\filename","r+b") so it may be
> the doshell is eating the first backslash
This has to do nothing with dosshell neither
with DOS or anything else of that kind.
The special chars in C must be prepended with
the backslash which discards their special
meaning or adds a special meaning to a normal
chars. Backslash itself is a special char also.
Just run the program like that:
---
#include <stdio.h> 

 
                    int main() { 

  printf("test\test\n"); 

} 

---
The result will be:
test    est

and with "test\\test\n" it will finally be
test\test

Re: Bug in DOSemu-FreeDOS-bin? (fwd)

[Bart Oldeman]

On Wed, 13 Aug 2003, Claudia Neumann wrote:

> I am running an application in dosemu-1.1.5 and its fine with MS-DOS 7.1. Now
> I would like to switch to FreeDOS. The dosemu-freedos-bin from the dosemu
> download directory doesn't load a file "c:\info\infdbf.exe", but only a file
> "infdbf.exe".  One part of the application wants to load the file
> "c:\info\infdbf.exe", doesn't find it and aborts. In MS-DOS 7.1 and 6.2 this
> is no problem. With the newest freedos the application aborts right in the
> beginning.
>
> Should I post this problem to dosemu or to the freedos mailinglist?

doesn't really matter -- but please try to replace your kernel.sys with
the newest version (2031, fat32 or fat16 doesn't matter) and see if that
helps. See http://freedos.sourceforge.net.

You're using dosemu-freedos-b8p-bin.tgz right now, right?

Bart

Re: Bug in DOSemu-FreeDOS-bin?

[Claudia Neumann]

Hi all,

Am Donnerstag, 14. August 2003 11:05 schrieb Bart Oldeman:

> doesn't really matter -- but please try to replace your kernel.sys with
> the newest version (2031, fat32 or fat16 doesn't matter) and see if that
> helps. See http://freedos.sourceforge.net.

Itried it, it is the same. You can't call c:\info\infdbf.exe, changing to 
c:\info and calling infdbf.exe is okay.

Regards

Claudia

Re: Bug in DOSemu-FreeDOS-bin?

[Claudia Neumann]

Hi all, Hi Bart

> doesn't really matter -- but please try to replace your kernel.sys with
> the newest version (2031, fat32 or fat16 doesn't matter) and see if that
> helps. See http://freedos.sourceforge.net.

It's the same with the new kernel ke2031_32.zip. I played a bit with the 
program. I found:

in the program you have to define the directory for the programm infdbf.exe.

As default it says: c:\info\

with MS-DOS 7.1 the program finds the infdbf.exe, in FreeDOS it only finds the 
infdbf.exe, if I define the directory as: c:\info (without Backslash). 

Okay, you could say define it as c:\info, but if I define it at 
program-startup as c:\info the program doesn't find it eiter. May be it is a 
MS-DOS 7.1-bug?

Regards

Claudia

Re: Bug in DOSemu-FreeDOS-bin?

[kontrare]

On Tuesday 19 August 2003 21:13, Claudia Neumann wrote:
> Hi all, Hi Bart
>
> > doesn't really matter -- but please try to replace your kernel.sys with
> > the newest version (2031, fat32 or fat16 doesn't matter) and see if that
> > helps. See http://freedos.sourceforge.net.
>
> It's the same with the new kernel ke2031_32.zip. I played a bit with the
> program. I found:
>
> in the program you have to define the directory for the programm
> infdbf.exe.
>
> As default it says: c:\info\
>
> with MS-DOS 7.1 the program finds the infdbf.exe, in FreeDOS it only finds
> the infdbf.exe, if I define the directory as: c:\info (without Backslash).
>
> Okay, you could say define it as c:\info, but if I define it at
> program-startup as c:\info the program doesn't find it eiter. May be it is
> a MS-DOS 7.1-bug?
>
> Regards
>
> Claudia
>
hello
	i dont know if this will help but i seem to remember doing a bit
of  coding a ways back and using fopen("c:\filename","r+b") in dos
it wouldn't see the file till i did fopen("c:\\filename","r+b") so it may
be the doshell is eating the first backslash, linux's bash will do this
too i.e if you do:-
	echo -e \\f
you get a formfeed but a single backslash and you it just prints 'f'
so maybe its seeing it c:info ?
			HTH		kontrare

Re: Bug in DOSemu-FreeDOS-bin?

[Claudia Neumann]

Hi all

Am Freitag, 22. August 2003 05:45 schrieben Sie:
> 	i dont know if this will help but i seem to remember doing a bit
> of  coding a ways back and using fopen("c:\filename","r+b") in dos
> it wouldn't see the file till i did fopen("c:\\filename","r+b") so it may
> be the doshell is eating the first backslash, linux's bash will do this
> too i.e if you do:-
> 	echo -e \\f
> you get a formfeed but a single backslash and you it just prints 'f'
> so maybe its seeing it c:info ?
> 			HTH		kontrare

Maybe that's the bug, but can't we get it right in FreeDOS so that we can get 
rid of MSDOS?

cu

Claudia

Re: Bug in DOSemu-FreeDOS-bin?

[Bart Oldeman]

Hi all, Hi Claudia,

On Tue, 19 Aug 2003, Claudia Neumann wrote:

> > doesn't really matter -- but please try to replace your kernel.sys with
> > the newest version (2031, fat32 or fat16 doesn't matter) and see if that
> > helps. See http://freedos.sourceforge.net.
>
> It's the same with the new kernel ke2031_32.zip. I played a bit with the
> program. I found:
>
> in the program you have to define the directory for the programm infdbf.exe.
>
> As default it says: c:\info\
>
> with MS-DOS 7.1 the program finds the infdbf.exe, in FreeDOS it only finds the
> infdbf.exe, if I define the directory as: c:\info (without Backslash).
>
> Okay, you could say define it as c:\info, but if I define it at
> program-startup as c:\info the program doesn't find it eiter. May be it is a
> MS-DOS 7.1-bug?

possibly, but it might also be a bug in the MFS (Mach File System, aka
"what lredir gives you") in DOSEMU.

If you have any problems on the command prompt with FreeDOS then first try
to use FreeCOM (the command.com that is also in the above mentioned
.zip) instead of the default comcom. The plan is to deprecate comcom
anyway.

If there are still problems then, well you have 4 combinations:
c:\info + MSDOS
c:\info\ + MSDOS
c:\info + FreeDOS
c:\info\ + MSDOS

It's probably possible to solve the bug if you mail me (not the list) some
debug output, i.e. the file "log" from
[x]dosemu -D+dD -o log
compressed with bzip2 for all the 4 combinations.

Bart

Bug in DOSemu-FreeDOS-bin?

[Claudia Neumann]

Hi,

I am running an application in dosemu-1.1.5 and its fine with MS-DOS 7.1. Now 
I would like to switch to FreeDOS. The dosemu-freedos-bin from the dosemu 
download directory doesn't load a file "c:\info\infdbf.exe", but only a file 
"infdbf.exe".  One part of the application wants to load the file 
"c:\info\infdbf.exe", doesn't find it and aborts. In MS-DOS 7.1 and 6.2 this 
is no problem. With the newest freedos the application aborts right in the 
beginning. 

Should I post this problem to dosemu or to the freedos mailinglist?

Regards

Claudia