Re: [Freedos-user] state of play

Thankyou everyone for your answers. I've made a lot of progress and Freedos is looking fantastic. The first problem I would like to address is that I have installed the DOS version of mplayer and the video is working fine, but there is no audio. Some research said that I need to use jemm with /s

[Freedos-user] state of play

Hi folks. Freedos 1.3 RC5 is now good enough for my main need which is to do development work using gccwin (similar to mingw) to build Win32 executables. (making use of HX too). I am now looking for Freedos to be a viable alternative to Windows for the rest of the things I would like to do. What

Re: [Freedos-user] command.com and long commands

Hi Jeremy. I just realized that the bug fix you have already committed is enough to unblock what I am doing. All I need to do is run “pdmake –n” to produce a batch file, and then I don’t need command.com to accept a long parameter. It would certainly be nice if it did, but it is not necessary. I wa

Re: [Freedos-user] command.com and long commands

Resending – I think it didn’t get through ... Hi Jeremy. I just realized that the bug fix you have already committed is enough to unblock what I am doing. All I need to do is run “pdmake –n” to produce a batch file, and then I don’t need command.com to accept a long parameter. It would certainly b

Re: [Freedos-user] command.com and long commands

> Yes, I had hoped to get a release out already but ran > into build issues getting all compilers to build which > was just fixed*. I will look into the cmdline issue, > already filled a bug for it. Then post the release. Hi Jeremy. Thanks for filing the bug report. Could you please hold off doi

Re: [Freedos-user] command.com and long commands

IMO it's a bug in FD command.com. If a command line exceeds 126 bytes, the value at [PSP:80h] "should" be 0x7Fh ( and a 0x0D "should" be placed at [PSP:FFh] ) - that's at least what COMMAND.COM of Win95/98 does. The environment variable CMDLINE will then contain the full command line. It's documen

[Freedos-user] command.com and long commands

Hello. When I run a long command, e.g. pdptest ... (to exceed 126 characters), and it is a Win32 executable so HX gets involved, I get a crash. Japheth has debugged it and reported his findings. Could someone please confirm that his analysis below is correct and it is a Freeco

[Freedos-user] DOS extenders with 32-bit INT 21H

Hi all. A short time ago I was made aware of this: http://dos32a.narechk.net/manual/index.html which is a 32-bit INT 21H AH=40H call that does a "write". Exactly the same as 16-bit INT 21H, except with 32-bit registers. Given that Microsoft don't have such a thing, it means that anyone who cre

Re: [Freedos-user] CMDLINE

Hi Eric. I went to github, but the readme didn't show the "/e" parameter. I looked around in the "docs" and "cmd" but nothing stood out. I don't want to report a bug unless I can see the documentation myself that says 32768. Currently I only see it when I go command /? on my version which is pres

Re: [Freedos-user] CMDLINE

Thanks Eric - 32766 solved the problem! Now I'm on to my next problem. This is behaving normally (there is no temp.c): C:\DEVEL\binutils-2.14a>gcc386 -S temp.c j d dd jj doing CreateFile with Xtemp.c

Re: [Freedos-user] CMDLINE

Hi Eric. Thanks for your reply. "hexdump" is my own program and does not have a version. But it's the same with any program - command.com complains before executing the program. The environment used to be set to the default, I wasn't using the "shell" command. But I switched to the max when I g

[Freedos-user] CMDLINE

Can someone please explain the below: C:\>hexdump bb Commandline longer t