DOSBox provides a (mostly) elegant solution to this -= - just share your files directly. Unlike other VMs, DOSBox allows you to di= rectly mount the host filesystem within the DOS VM -- so you can just edit = the files directly using your editor of choice on Windows, then switch to D= OSBox and build them. (You do need to watch out for long filenames, though.= ) In the odd occurrence of being out of sync, the DOSBox command "resy= nc" will refresh its cached directory of the host FS.

Damian

On Sun, Aug 30, 2020 at 12:09 PM sleepy_dog AT gmx DOT de [via djgpp AT delorie DOT com] <djgpp AT delorie DOT com> wrote:

Hi,

> I thought he was running DJGPP under DOSBox and not directly under Win= dows 7.

No no, I planned to make the programs run under DOSbox, but compiling is fr= om within windows.
I guess for debugging I would have to use RHIDE within DOSbox, esp. because= Graphics modes are involved.
But I'd prefer not to use it as an actual editor.

> How about trying some other kind of virtual machine, eg. QEMU or VMWar= e?

I was now thinking of running a VirtualBox WinXp32 image on my system,
with a shared folder for the sources, and a build script I trigger manually= .
That would be somewhat workable, I guess.

I have no experience with QEMU or VMWare, and interoperability with
stuff that runs on the host system.

> Hi all,
>
> On Sun, 30 Aug 2020 at 17:10, Eli Zaretskii (eliz AT gnu DOT org) [via
> djgpp AT delorie DOT c= om] <djgpp AT de= lorie.com> wrote:
>>> From: "sleepy_dog AT gmx DOT de [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
>>> Date: Sun, 30 Aug 2020 18:32:41 +0200
>>>
>>> go32/v2 version 2.0 built Oct 18 2015 09:41:08
>>> Usage: go32 coff-image [args]
>>> Rename this to go32.exe only if you need a go32 that can run v= 2 binaries as
>>>=C2=A0 =C2=A0 well as v1 binaries (old makefiles).=C2=A0 Put ah= ead of the old go32 in
>>> your PATH
>>>=C2=A0 =C2=A0 but do not delete your old go32 - leave it in the= PATH after this one.
>>> Set GO32_V2_DEBUG=3Dy in the environment to get verbose output= .
>>>
>>> DPMI memory available: 704964 Kb
>>> DPMI swap space available: 0 Kb
>>>
>>> Hm. DPMI swap space 0 =3D bad?
>> No, that's OK.=C2=A0 Many "modern" DPMI providers ju= st lump all the memory
>> together (700MB in your case), and don't bother separating the= m into
>> RAM and swap.
>>
>> The memory amount sounds enough, so I'm puzzled what could be = the
>> problem.=C2=A0 Maybe some Windows 7 specific problem?=C2=A0 I thin= k someone
>> posted here long ago tricks to get the Windows DPMI provider more<= br> >> friendly...=C2=A0 Anyone?
> I thought he was running DJGPP under DOSBox and not directly under
> Windows 7.=C2=A0 DOSBox is designed to be able to run old games, so no= t
> even long filenames are implemented.=C2=A0 How about trying some other= kind
> of virtual machine, eg. QEMU or VMWare?
>
> I've said it before, but NT series Windows support for DOS program= s is
> pathetic (and on 64-bit versions it is nonexistent).=C2=A0 Then again,=
> Linux never directly supported DOS programs at all.=C2=A0 In both case= s,
> virtual machines are the solution.
>
> Cheers,
> Albert.
>