www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2015/02/10/18:45:10

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: "Rod Pemberton" <buzz AT notnotnontnooatno DOT cmm>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Develop djgpp program using Windows 7 ?
Date: Tue, 10 Feb 2015 18:38:03 -0500
Organization: Aioe.org NNTP Server
Lines: 52
Message-ID: <op.xtu7xpemv6dtjm@localhost>
References: <3c287821-c0dd-4533-b513-247f89da252f AT googlegroups DOT com>
NNTP-Posting-Host: n4wpt9zq8xR26Ttf9mo2BA.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse AT aioe DOT org
User-Agent: Opera Mail/12.16 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Bytes: 3475
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

On Tue, 10 Feb 2015 17:19:20 -0500, Georg Potthast <dosusb AT googlemail DOT com>  
wrote:

> I have been using a Windows XP system up to now to develop djgpp
> programs. To be able to run e.g. the latest virus scanner on my PC I
> need to move to Windows 7 or later. I guess my Windows XP system is
> already the member of several bot networks.
>
> What is the recommended environment to develop djgpp programs then?
> Should I use a Virtual PC, Qemu or else? Or should I setup a Linux
> system instead?
>
> Booting DOS is too slow for me since I then have to run a long file name
> driver which makes it much slower than a command window on Windows XP.
>

I was using MS-DOS from Windows 98/SE.  The Windows DOS console once
you boot into 98/SE is very fast, basically it's full 32-bit PM DOS.

My suggestion would be to install a new harddrive for Windows 7,
and keep Windows XP as an alternate, bootable drive.  If your
PC has a BBS menu when booting, usually F11, you can easily boot
an alternate drive at power-up.  Otherwise, you may need to install
a boot manager that's compatible with Windows XP and 7.

Currently, I have Linux installed, but I haven't compiled anything
with DJGPP from Linux.  I can boot my actual MS-DOS drive using QEMU,
DOSBox, and dosemu.  Each of these seems to have various DOS emulation
and emulation of DOS disk mounting issues under Linux.  DOSBox seems
to run everything, but many hardware related things seem to be flat
out wrong.  dosemu is slow but everything seems to be correct that
I've tested.  QEMU is fast, but it seems to fail sometimes with CWSDPMI.

One of the three environments doesn't flush changes to files you've
edited in DOS to your mounted drive at all, but the changed file is
cached somewhere ...  I.e., when you restart, it appears that the
modified file is present on your DOS drive, but if you actually boot
DOS, it isn't.  The other two flush.  IIRC, all three of them won't
recognize changes to files edited from Linux, e.g., via VI, until
you restart them.  I also ran into an issue with running all three
at once against the same physical drive.  So, I would recommend only
editing files from an actual DOS boot, or Windows XP console, or
be very careful and very things.  I lost some changes with this stuff.

BTW, it's *not* usually recommended to use an actual DOS partition
with any of these, and those issues may be some of the reasons why ...
I wanted access to my real partition, text files, and code.
AIR, you're supposed to setup a file to be used as partition in
Linux for the emulated DOS environment.


Rod Pemberton

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019