[Freedos-user] New VirtualBox images / FreeDOS networking

[Ulrich Hansen]

I have updated my website about FreeDOS in VirtualBox. Please take a look at:
https://www.lazybrowndog.net/freedos/virtualbox/ 


You find three VirtualBox images for download:

FreeDOS 1.1 - everything as freshly installed from a FreeDOS 1.1 CD
FreeDOS 1.1plus - like 1.1 but installed with FDNPKG, so you can easily update.
FreeDOS 1.1net - with more networking abilities (f.i. MS Client).

I wrote also some HowTos about the installation in VirtualBox. And about 
networking - especially about MS Client. 
FreeDOS networking should be a lot of fun with this image.

If you have additional ideas, wishes, questions, let me know.
Thanks. Best wishes
Ulrich


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS in VirtualBox: Bad or missing command interpreter and keyboard doesn't work

[Ulrich Hansen]

I have heard about this problem from some users of the FreeDOS VirtualBox 
images at 
https://www.lazybrowndog.net/freedos/virtualbox/ 
 

As far as I found out, "Bad or missing command interpreter" doesn’t necessarily 
mean COMMAND.COM doesn’t exist. It can also mean it can’t be loaded. This seems 
to be an issue of JEMMEX on some machines.

You could experiment with JEMMEX settings. Others here know a lot more about 
that and perhaps have the time to help you. 

Another possibility: If you use FreeDOS for non-commercial purposes, it would 
be legal to use the memory manager of Calderas DR-DOS instead. The full DR-DOS 
can be found here ftp://ftp.uni-bayreuth.de/pub/pc/caldera 
 with all the necessary notes and 
licensing information. Please read it. For your convenience the driver alone 
can be downloaded here: https://www.lazybrowndog.net/freedos/dremm386.zip 
. 

Unzip it to a folder like C:\UTIL\DRDOS.

Look for a line similar to this one in C:\FDCONFIG.SYS:

15678?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG

and replace it by this one

15678?DEVICE=C:\UTIL\DRDOS\DREMM386.EXE NOEMS EXCLUDE=D000-D7FF

And in C:\AUTOEXEC.BAT after the following line

IF „%config%“==„4“ goto end

add this line:

C:\UTIL\DRDOS\DREMM386.EXE PIC=ON

Please give some feedback if this works for you.

Note: DR-DOS EMM386 doesn’t have all the features of JEMMEX so you need to test 
if your programs work with this driver. Try also different settings to get more 
free memory. I know that this is not a perfect solution.

Ulrich



> Am 07.01.2016 um 00:15 schrieb caswellrie...@gmail.com:
> 
> Hello! Basically, my issue is summarized in the title.
> 
> I have installed a FreeDOS 1.1 install as a VirtualBox guest, but when I boot 
> I get the error “Bad or missing command interpreter” and then a prompt to 
> enter the path to COMMAND.COM .  However, when this 
> prompt is issued, the system stops accepting keyboard input.  The keyboard 
> works before this prompt.  Possibly related, but I had to try to install from 
> the CD image twice, because the first time the installer froze after I 
> selected my language/keyboard layout.
> 
> Any and all help would be greatly appreciated.
> 
> Thanks, Matt
> 
> Sent from Windows Mail
> 
> --
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/freedos-user 
> 
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS in VirtualBox: Bad or missing command interpreter

[Ulrich Hansen]

I experimented with JEMMEX settings, but unfortunately even 

DEVICE=C:\FDOS\BIN\JEMMEX.EXE X=A000- NOHI NOVME NOINVLPG

in FDCONFIG.SYS leads to a crash of the FreeDOS 1.1 guest in a Windows 8 host. 
On my Mac there’s no such problem.

The JEMMEX documentation says about the settings above:

"This is the safest combination. If this doesn't work, Jemm most likely isn't 
compatible with the current DOS/BIOS.“

VirtualBox is the newest version 5.0.14.

For my VirtualBox image with network ("FreeDOS 1.1net") I created a new 
version, which uses the old HIMEM.EXE and EMM386.EXE couple from FreeDOS 1.0. 
They seem to work fine. If anyone wants to try it out:

https://www.lazybrowndog.net/freedos/virtualbox/downloads/vdi/FreeDOS1.1net-test.zip
 
<https://www.lazybrowndog.net/freedos/virtualbox/downloads/vdi/FreeDOS1.1net-test.zip>

Installation is explained here: 
https://www.lazybrowndog.net/freedos/virtualbox/ 
<https://www.lazybrowndog.net/freedos/virtualbox/downloads/vdi/FreeDOS1.1net-test.zip>

Not using UMBs at all isn’t such a good idea. With HIMEM.EXE and EMM386.EXE I 
get 509K free conventional memory after loading all the drivers for MS Client 
and TCP/IP. Without UMBs I loose another 59K so I think some programs wouldn’t 
even start.

Thanks!
Ulrich



> Am 13.01.2016 um 00:49 schrieb Ulrich Hansen :
> 
> I have heard about this problem from some users of the FreeDOS VirtualBox 
> images at 
> https://www.lazybrowndog.net/freedos/virtualbox/ 
> <https://www.lazybrowndog.net/freedos/virtualbox/> 
> 
> As far as I found out, "Bad or missing command interpreter" doesn’t 
> necessarily mean COMMAND.COM <http://command.com/> doesn’t exist. It can also 
> mean it can’t be loaded. This seems to be an issue of JEMMEX on some machines.
> 
> You could experiment with JEMMEX settings. Others here know a lot more about 
> that and perhaps have the time to help you. 
> 
> Another possibility: If you use FreeDOS for non-commercial purposes, it would 
> be legal to use the memory manager of Calderas DR-DOS instead. The full 
> DR-DOS can be found here ftp://ftp.uni-bayreuth.de/pub/pc/caldera 
> <ftp://ftp.uni-bayreuth.de/pub/pc/caldera> with all the necessary notes and 
> licensing information. Please read it. For your convenience the driver alone 
> can be downloaded here: https://www.lazybrowndog.net/freedos/dremm386.zip 
> <https://www.lazybrowndog.net/freedos/dremm386.zip>. 
> 
> Unzip it to a folder like C:\UTIL\DRDOS.
> 
> Look for a line similar to this one in C:\FDCONFIG.SYS:
> 
> 15678?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
> 
> and replace it by this one
> 
> 15678?DEVICE=C:\UTIL\DRDOS\DREMM386.EXE NOEMS EXCLUDE=D000-D7FF
> 
> And in C:\AUTOEXEC.BAT after the following line
> 
> IF „%config%“==„4“ goto end
> 
> add this line:
> 
> C:\UTIL\DRDOS\DREMM386.EXE PIC=ON
> 
> Please give some feedback if this works for you.
> 
> Note: DR-DOS EMM386 doesn’t have all the features of JEMMEX so you need to 
> test if your programs work with this driver. Try also different settings to 
> get more free memory. I know that this is not a perfect solution.
> 
> Ulrich
> 
> 
> 
>> Am 07.01.2016 um 00:15 schrieb caswellrie...@gmail.com 
>> <mailto:caswellrie...@gmail.com>:
>> 
>> Hello! Basically, my issue is summarized in the title.
>> 
>> I have installed a FreeDOS 1.1 install as a VirtualBox guest, but when I 
>> boot I get the error “Bad or missing command interpreter” and then a prompt 
>> to enter the path to COMMAND.COM <http://command.com/>.  However, when this 
>> prompt is issued, the system stops accepting keyboard input.  The keyboard 
>> works before this prompt.  Possibly related, but I had to try to install 
>> from the CD image twice, because the first time the installer froze after I 
>> selected my language/keyboard layout.
>> 
>> Any and all help would be greatly appreciated.
>> 
>> Thanks, Matt
>> 
>> Sent from Windows Mail
>> 
>> --
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net 
>> <mailto:Freedos-user@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/freedos-user 
>> <https://lists.sourceforge.net/lists/listinfo/freedos-user>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take correcti

[Freedos-user] Fascinating HowTo about installing MS DOS (with network)

[Ulrich Hansen]

I just want to share this website:

http://www.legroom.net/howto/msdos

It’s fascinating to read. It includes mTCP and other networking stuff. I was 
just looking for a solution how to get DNS resolving going with MS Client and 
DNR.EXE. And then this guy explains DOS from A to Z. It’s even under a CC 
license. Thank you very much, Mr. Jared Breland!
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

> Am 05.02.2016 um 03:35 schrieb Jose R Gimenez :
> 
> Just want to know if FreeDOS can run interlink.exe and intersrv.exe

In theory. Out of curiosity I booted two Compaq Contura Aeros, installed 
intersvr and interlnk and tried it. It didn’t work for me so far. The intersvr 
machine runs great. But on the one with interlnk I get an error after loading 
the driver in FDCONFIG.SYS with 

DEVICE=C:\INTERLNK.EXE /AUTO /NOPRINTER

dos mem corrupt
panic: mcb chain corrupted
system halted

The error was only visible when both computers were NOT connected. If I connect 
both computers over LPT and boot again the interlnk machine just freezes.

I tried with memory managers on and off and even with a nearly empty 
AUTOEXEC.BAT and FDCONFIG.SYS (well the SHELL command was the only other line 
in it).

I confess, both machines are still running FreeDOS 1.0, so maybe it’d work with 
FreeDOS 1.1. And both Aeros have the 16 MB RAM extension module installed, 
which unfortunately has a bug by design. So it may work with different hardware 
and if you try hard enough.

Filemaven, which Eric suggested, worked for me out of the box and without 
changing FDCONFIG.SYS. So try it, if you don’t need the intersvr program 
running as TSR in the background and providing you with a drive letter for the 
remote machine. 

regards

PS: Wow, I still had the centronics cable and the LPT adapter in a box!
 




--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

Tom suggested to put a line 

version=3.31

in FDCONFIG.SYS, right before 

DEVICE=C:\INTERLNK.EXE /AUTO /NOPRINTER

This solved the problem of the crash/freeze. (Thanks!) 

As you can see in the first picture, interlnk is now able to make a connection. 
I tried it with an empty AUTOEXEC.BAT and FDCONFIG.SYS, but it also worked with 
the old EMM386 and HIMEM (it’s still a FreeDOS 1.0 machine).

https://www.lazybrowndog.net/freedos/interlnk/interlnk1.jpg 


Unfortunately the characters are garbled though.

https://www.lazybrowndog.net/freedos/interlnk/interlnk2.jpg 


I tried it with and without any country/codepage settings, so I am pretty sure 
that’s not the problem. File dates and times also don’t make a lot of sense, if 
you take a look. :-> 

The program on the second picture is Necromancers DOS Navigator. But also 
without GUI, when I change to D: (the remote drive) on the command line of the 
client and do „dir“, it types a long list of weird filenames and characters.



--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

> I've used David Dunfield's DDLINK[0] successfully in VirtualBox over
> the virtual switch & NICs.
> 
> [0] http://www.classiccmp.org/dunfield/dos/index.htm

Yesterday evening I tried winlink, filemaven and DDLINK. DDLINK was by far the 
easiest to configure and use. 
Put it on both machines. 

On the server command:
DDLINK /S L=1
On the client command:
DDLINK L=1

while L=1 means LPT1.

Seemed to work without problem on the two machines with FreeDOS 1.
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

With a lot of help by Tom (thanks!!), here is more information about INTERLINK 
and FreeDOS. 

Microsofts INTERLNK program doesn’t work with FreeDOS at the moment. There is a 
bug in the FreeDOS kernel that makes some programs crash the system, one of 
those is INTERLNK.EXE.

As long as this isn’t fixed, it is possible to patch INTERLNK.EXE to make it 
work with FreeDOS. Here is how:

Get INTERLINK from the Microsoft FTP server ftp.microsoft.com.

Login with a FTP client like FileZilla, username is „anonymous“, password is 
your email.

Change to the directory Softlib/MSLFILES.

Get the file OLDDOS.EXE. It includes the two programs for INTERLINK: 
INTERSVR.EXE which is used by the server and INTERLNK.EXE for the client.

Please check the license file. You have the right to use the software "in 
conjunction with licensed copies of  Microsoft Windows 95“. Please make sure 
you have such a license.

The server program INTERSVR.EXE runs fine in FreeDOS. To share the C: 
harddrive, just command:

C:\UTIL\INTERSVR.EXE C:

On the client you need to run INTERLNK.EXE. It has to be loaded as device 
driver in FDCONFIG.SYS with a line like this:
DEVICE=C:\UTIL\INTERLNK.EXE /AUTO /NOPRINTER

At the moment, such a line in FDCONFIG.SYS will crash FreeDOS.

To get INTERLNK.EXE working, you could patch the file:

Open the file INTERLNK.EXE in a hex editor. Find the following pattern:

00 05 72 56 8b 1e 55 04

and replace it with:

00 05 eb 56 8b 1e 55 04

This replaces the „JB“ instruction in assembly language (conditioned jump) with 
an unconditioned „JMP“. The condition was about the DOS version detected. 

As you can see in the following pictures, such a patched version of 
INTERLNK.EXE boots just fine.
https://www.lazybrowndog.net/freedos/interlnk/interlnk-boot.png

And it connects with INTERSRV.EXE on the remote computer.
https://www.lazybrowndog.net/freedos/interlnk/interlnk-connection.jpg

Hope this helps someone someday.
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

> Am 11.02.2016 um 14:55 schrieb  :
> 
> Something else that should work if you don't want to modify it, add /low 
> option which will also bypass the problematic code.
> 

Oh, that’s interesting. If I load the original, unpatched INTERLNK.EXE in 
FDCONFIG.SYS with

DEVICE=C:\UTIL\INTERLNK.EXE /AUTO /NOPRINTER /LOW

it’s working. The machine is still on FreeDOS 1.0 and loads HIMEM.EXE and 
EMM386.
So with this „/LOW" everything seems to work fine too.

> Tom's workaround will be in svn kernel soon, but I need to do some more 
> testing as I'm still getting crashes, but haven't determined if its because 
> of memory managers, virtual box, or another kernel issue with interlnk.  (It 
> crashes later in booting, but only if I load interlnk, though it's fine if I 
> add low to interlnk which seems odd as functionally should behave same with 
> applied patch.)
> 
The patched version of ITERLNK leads to problems if I still have a line
version=3.31
before it in FDCONFIG.SYS. The computer boots but other drivers don’t seem to 
get loaded, keyboard, mouse, the whole AUTOEXEC.BAT stuff.

It’s not really comparable to your configuration of course, as you use a 
different kernel.--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 Package LSM Data Verification

[Ulrich Hansen]

> 
> WATTCP is the only one remaining. 
> 

The license of WATTCP is a bit hard to find out. At the moment it is 
distributed by its author Erick Engelke at:
http://www.erickengelke.com/wattcp/ 

The license of this official version from 14. September 2015 is in the 
/include/copyrigh.h file. I append it as text further down this mail.

As I understand it, you can use the WATTCP library to produce commercial or 
open source software. The library itself is not allowed to be sold. This could 
conflict with FreeDOS, as some vendors in the past have bundled their hardware 
with FreeDOS which could be seen as commercial distribution.

In 2005 WATTCP was distributed by a site called http://www.wattcp.com/ 
. This site also sold the WATTCP manual. The download 
file was called wat1104.zip and included a copyrigh.h file which stated WATTCP 
was GNU LGPL. I also quote this text a bit further down in  this mail.

The FreeDOS site at 
http://www.freedos.org/software/?prog=wattcp 

points to another version of WATTCP at 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/wattcp/ 


This version is from 05. June 2001 and includes a copyrigh.h file similar to 
the version from 2015.

All versions contain sources. As I see it, the relevant license is the one from 
September 2015.

I send this mail in BCC to Erick Engelcke in the hope, he might give us a hint 
if WATTCP can or should be distributed with FreeDOS.

Thanks a lot!




-- Copyright WATTCP 14. September 2015 


/*
 *   WATTCP - TCP/IP library routines
 *
 *   Copyright (c) 1990, 1991, 1992, 1993 Erick Engelke
 *
 *   Portions Copyright (c) 1993  Quentin Smart
 *   Portions Copyright (c) 1990  National Center for Supercomputer Applications
 *   Portions Copyright (c) 1990  Clarkson University
 *   Portions Copyright (c) 1983, 1986, Imagen Corporation
 *
 *  This software is distributed in the hope that it will be useful,
 *  but without any warranty; without even the implied warranty of
 *  merchantability or fitness for a particular purpose.
 *
 *   RESTRICTIONS
 *   
 *   You may freely use this library to produce programs which you may give
 *   away or sell in source format, or as compiled executables, or both.
 *
 *   You may not sell this library or a portion thereof or distribute modified
 *   versions the library code in either source or OBJect or LIBrary format
 *   without written permission from the author.  The author still maintains
 *   copyright privileges and will assert the privileges of ownership for
 *   purposes of royalties such distributions.
 *
 *   Portions of this code were written or enhanced by others and offerred
 *   to me for distribution in WATTCP under my copyright.  To my knowledge,
 *   all copyrights exercised are listed at the top of this file.  If this
 *   is incorrect, please contact me so I can rectify the situation.
 *
 *
 *   OFFICIAL SITE
 *   -
 *   The official distribution site for WATTCP (and many other TCP goodies)
 *   is dorm.rutgers.edu in pub/msdos/wattcp  (thanks Jim!)
 *
 *   That is where I upload the latest libraries, my own free applications
 *   and other applications I have collected and find useful.
 *
 *
 *   DOCUMENTATION
 *   -
 *   A programmer's reference manual I wrote is now available from the
 *   publisher.  They provide no additional support and cannot help
 *   you with any aspect of the software.  But they do pay a royalty
 *   to me which has been used to compensate my costs for developing
 *   this software and extending it, so I am very appreciative.
 *
 *   That manual is copyrighted and protected by international law.
 *   It may not be copied without the authors permission.  And its
 *   sale does not constitute a warranty or an automatic license to
 *   use WATTCP beyond the terms described in this file.
 *
 *  WATTCP Manual
 *  www.wattcp.com
 *
 */
#define WATTCP_C "WATTCP_C"





-- Copyright WATTCP 02. November 2004 from WAT1104.zip 


/*
 *   WATTCP - TCP/IP library routines
 *
 *
 * This library is free software; you can redistribute it and/or
 * modify it under the terms of the GNU Library General Public
 * License as published by the Free Software Foundation; either
 * version 2 of the License, or (at your option) any later version.
 * 
 * This library is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 * Library General Public License for more details.
 * 
 * You should have received a copy of the GNU Library General Public
 * License along with this library; if not, write to the
 * Free Software Foundation, Inc.

[Freedos-user] Fwd: FreeDOS 1.2 Package LSM Data Verification

[Ulrich Hansen]

And this is what Erick Engelke replied a few minutes ago.

Anfang der weitergeleiteten E‑Mail:

> The authors all wanted to create free TCP implementations for everyone.
> GPL has some limitations that you can't sell some things, BSD is more free
> to my thinking, but not everyone agree.
> 
> I don't really care what people do with the WATCP software anymore.
> 
> E
> 
> On Fri, May 20, 2016 at 7:10 PM, Ulrich Hansen <


--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

Hi Abe,

if you like, take a look at:

https://www.lazybrowndog.net/freedos/virtualbox 


There are three VirtualBox images of FreeDOS 1.1. 

I put quite some effort in them to make them work. I remember the crash you are 
talking about, but, sorry, I don’t remember how I fixed it (wasn’t it something 
about not loading high something?? Very sorry. Maybe you compare the 
AUTOEXEC.BAT and FDCONFIG.SYS of the FreeDOS 1.1 VirtualBox image?

-
AUTOEXEC.BAT

@echo off
SET LANG=EN
SET MTCPCFG=C:\FDOS\MTCP.CFG
SET WATTCP.CFG=C:\FDOS
SET PATH=%dosdir%\BIN;C:\DOSZIP
SET NLSPATH=%dosdir%\NLS
SET HELPPATH=%dosdir%\HELP
SET TEMP=%dosdir%\TEMP
SET TMP=%TEMP%
SET BLASTER=A220 I5 D1 H5 P330
SET DIRCMD=/P /OGN /4
SET COPYCMD=/-Y
if "%config%"=="4" goto end
SHSUCDX /QQ /D3
LH SHSUCDHD /QQ /F:FDBOOTCD.ISO
LH FDAPM APMDOS
IF "%config%"=="2" LH SHARE
LH DOSLFN
REM NLSFUNC C:\FDOS\BIN\COUNTRY.SYS
REM DISPLAY CON=(EGA),858,2)
REM MODE CON CP PREP=((858) C:\FDOS\CPI\EGA.CPX)
REM KEYB US,858,C:\FDOS\bin\keyboard.sys
REM KEYB GR,,keyboard.sys /NOHI
REM CHCP 858
IF "%config%"=="2" PCNTPK INT=0x60
IF NOT "%config%"=="2" LH PCNTPK INT=0x60
DHCP
REM M2WAT.COM  transfers the mTCP configuration to 
WATTCP.CFG.
REM Disable it, if you want to use a custom WATTCP.CFG.
C:\FDOS\M2WAT.COM 
MOUSE
DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5
SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D /D:?FDCD0002,D 
/D:?FDCD0003,D
MEM /C /N
IF NOT "%config%"=="4" SHSUCDX /D
GOTO END
:END
SET AUTOFILE=%0
SET CFGFILE=C:\FDCONFIG.SYS
alias reboot=fdapm warmboot
alias reset=fdisk /reboot
alias halt=fdapm poweroff
alias shutdown=fdapm poweroff
alias cfg=edit %cfgfile%
alias auto=edit %0
echo Done processing startup files %cfgfile% and %0
echo Type HELP to get support on commands and navigation
echo.
echo Welcome to the FreeDOS 1.1 operating system (http://www.freedos.org 
)


-
FDCONFIG.SYS

!COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS 
!SET DOSDIR=C:\FDOS
!LASTDRIVE=Z
!BUFFERS=20 
!FILES=40
!MENUCOLOR=7,0
MENUDEFAULT=1,5
MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free
MENU 2 - Load FreeDOS with EMM386 (Expanded Memory) and SHARE loaded
MENU 3 - Load FreeDOS including XMGR XMS-memory driver
MENU 4 - Load FreeDOS without drivers 
123?DOS=HIGH
12?DOS=UMB
12?DOSDATA=UMB
1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
2?DEVICE=C:\FDOS\BIN\HIMEMX.EXE 
2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG
3?DEVICE=C:\FDOS\BIN\XMGR.SYS 
3?SHELL=C:\FDOS\bin\4dos.com  C:\FDOS\bin /E:1024 
/P:C:\AUTOEXEC.BAT  
4?SHELL=C:\FDOS\BIN\COMMAND.COM  C:\FDOS\BIN /E:1024 
/P=C:\AUTOEXEC.BAT 
12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM  C:\FDOS\BIN /E:1024 
/P=C:\AUTOEXEC.BAT --
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

Hi Abe (and hi Eric!)

> Am 28.06.2016 um 16:42 schrieb Abe Mishler :
> 
> 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=C900-DFFF I=TEST NOVME NOINVLPG
> 
> Boot option 1 (http://tinypic.com/r/zm1boj/9 ):
> Total memory Free: 26,699K
> Total Expanded (EMS): 8,576K
> Free Expanded (EMS): 8,192K
> Largest executable program size: 597K
> Largest free upper memory block: 2K


With the FreeDOS 1.1 default line

1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG

I get less free conventional memory:

Boot option 1 
(https://www.lazybrowndog.net/freedos/files/freedos1.1-vbox-opt1-memory.png 
)
Total memory Free: 26,682K
Total Expanded (EMS): 8,576K
Free Expanded (EMS): 8,192K
Largest executable program size: 579K
Largest free upper memory block: 2K

If I try your configuration in my FreeDOS 1.1 VirtualBox image I get even 601K 
executable program size BUT:
If I look closely, I find that PCNTPK crashes at boot. So I have no network. No 
wonder all the memory is free.
https://www.lazybrowndog.net/freedos/files/freedos1.1-vbox-opt1-memory2.png 


So your solution won’t work for all VirtualBox users…
I have Version 5.0.14 r105127 running in OS X 10.10.5.


PS: I use a screencast software to record boot messages in VBox - otherwise 
they move to quickly to read them.

--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

> Am 28.06.2016 um 20:41 schrieb Ulrich Hansen :
> 
> If I look closely, I find that PCNTPK crashes at boot. So I have no network. 
> No wonder all the memory is free.
> https://www.lazybrowndog.net/freedos/files/freedos1.1-vbox-opt1-memory2.png 
> <https://www.lazybrowndog.net/freedos/files/freedos1.1-vbox-opt1-memory2.png>
> 
> So your solution won’t work for all VirtualBox users…
> I have Version 5.0.14 r105127 running in OS X 10.10.5.

Okay. I also tried it with the new version 5.0.22 but everything’s the same. 
BUT:

The trick is to load PCNTPK low in option 1. Then it won’t crash with your 
JEMMEX options. At least for me. :-)

PCNTPK INT=0x60


--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

> Am 28.06.2016 um 21:19 schrieb Ulrich Hansen :
> 
> The trick is to load PCNTPK low in option 1. Then it won’t crash with your 
> JEMMEX options. At least for me. :-)
> 
> PCNTPK INT=0x60

Okay, and FDAPM crashes too. I need to load it into conventional memory as well.

All in all it seems your configuration 

> 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=C900-DFFF I=TEST NOVME NOINVLPG


is pretty unstable, at least for me.

But the default line didn’t work for you at all. Hmm.


--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

Am 28.06.2016 um 22:55 schrieb Abe Mishler :

>> is pretty unstable, at least for me.
> It seems like you should be excluding a different region of memory. From your 
> screenshot: E300-EDFF.

The packet driver works, but FDAPM is still crashing when I exclude E300-EDFF.  

>> But the default line didn’t work for you at all. Hmm.
> Strange, right? And not just on one computer, but three separate ones; each 
> running different hardware and software (host OS). Although I would expect 
> that the underlying differences are abstracted away by VirtualBox.

I created the VirtualBox „FreeDOS 1.1.net" image in February. Immediately five 
people complained (very politely) about crashes. No boot menu option worked 
that included JEMMEX or JEMM386.

As temporary fix, I replaced JEMMEX with the obsolete HIMEM.EXE and EMM386.EXE 
from FreeDOS 1.0. There has been no complaint since. (The "FreeDOS 1.1net" 
VirtualBox image has been downloaded 815 times in 2016). 


> Am 29.06.2016 um 00:24 schrieb Eric Auer :
> 
> To explain the different memory types:

Thank you! Clears things up and refreshes the memory. This should be part of 
the FreeDOS wiki. Reminds me of the time, when I was reading the MS-DOS 5.0 
manual in 1992. Got my first computer the day before and intended to read the 
manual first. So I sat on a river bench and read about optimizing the use of 
UMBs. :-)

> UMB - provided by EMM386 - lets you load various drivers
>  high, can also be provided by UMBPCI or other hardware
>  drivers, can cause stability issues in conflict cases

This is the reason I want some EMM. For DOS networking I need to load drivers, 
especially for MS Client.
--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

> Am 29.06.2016 um 13:08 schrieb Don Flowers :
> 
> The only drivers that work for this is Ulrich's FreeDOS 1.0 drivers Himem.exe 
> and "EMM386.EXE NOEMS"

Before someone gets it wrong: The drivers were written by Tom Ehlert, Michael 
Devore and other fine people. Thanks!



--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

> I think FreeDOS in QEMU on linux is the way to go (for me, at this time).

Inspired by this thread I also looked into qemu (even installed it on my Mac).

Just in case you missed it: 
There’s a great tutorial about running FreeDOS 1.1 in qemu.
Part three is all about networking. :-)

The author is Patrick G. Horneker.

http://pclosmag.com/html/issues/201206/page08.html 

http://pclosmag.com/html/Issues/201207/page11.html 

http://pclosmag.com/html/issues/201208/page11.html 

http://pclosmag.com/html/Issues/201210/page11.html 



--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

> Am 01.07.2016 um 01:51 schrieb Abe Mishler :
> 
>  I have been learning a lot about JEMMEX as compared to the other drivers 
> lately. 

Hi Abe,

If you don’t mind, it would be great if you could try one last thing with 
VirtualBox and JEMMEX:

Please try to start JEMMEX with this line in FDCONFIG.SYS:

1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=B000-B7FF I=C800-EFFF NOVME 
NOINVLPG

Important are both includes I=B000-B7FF I=C800-EFFF. 
Does this change anything for you? Does it still crash?

Thanks!


--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

> Am 01.07.2016 um 14:59 schrieb Abe Mishler :
> 
>> 
>> 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=B000-B7FF I=C800-EFFF
>> NOVME NOINVLPG
>> 
> That works like a charm! Do those regions work for you?

Yes. I tested it on a FreeDOS 1.1 guest on my Mac. 

And, as I don’t have Windows machine anymore, I started a Windows 10 VirtualBox 
guest, and inside of it I used VirtualBox for Windows and tested it there with 
a FreeDOS 1.1 guest. Normally JEMMEX crashes there, but not this time.

> Could you provide an explanation regarding those regions?

Actually they discussed it in the VirtualBox forum:

https://forums.virtualbox.org/viewtopic.php?f=4&t=77078&sid=4702e57e2da69b00248e9a82eeffbe98
 


Seems some people at Oracle are still interested in DOS.

> I will now revisit my decision to use QEMU on linux... except linux can 
> mount raw images for native file sharing without having to FTP into 
> FreeDOS (which I got working).

Yes, this is nice. On OS X you can just double-click the image to mount it.

Just a quick review about qemu and networking: 

Networking with qemu is difficult. Per default it uses NAT, but only for TCP. 
So I can’t ping the outside world. WGET works. I managed to transfer files with 
FileZilla to mTCP ftpsrv. (Which is a miracle as all other clients won’t even 
do a directory listing.)

For bridged networking I’d have to install a TUN/TAP software on the host. 
Complicated.

I start qemu with:

qemu-system-i386 -hda freedos.img -boot c -m 32 -netdev 
user,id=usernet,net=192.168.3.0/24,dhcpstart=192.168.3.101 -device 
pcnet,netdev=usernet -redir tcp:2121::21

With „-device pcnet“ qemu supports the AMD PCFastIII (pcnet) network card, so 
the packet driver in FreeDOS 1.1 (PCNTPK) can be used. 

> Thanks a lot for re-opening my can of worms!!! :-p

Brr. :-)

Good luck!!

--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1 crashing in VirtualBox 5.0.22

[Ulrich Hansen]

Hi Abe,

> Am 01.07.2016 um 14:59 schrieb Abe Mishler :
> 
> except linux can 
> mount raw images for native file sharing 

Today I found out: If I choose „VHD“ as type for the virtual harddisk in 
VirtualBox, I am able to mount the VirtualBox image in Windows too. 

See: https://www.lazybrowndog.net/freedos/files/vhd.png 


Now I just open „Computer Management“ in Windows, right-click on "Disk 
Management" and choose "Attach VHD“.
See this description here: 
http://www.online-tech-tips.com/computer-tips/create-mount-vhd-windows/ 


(You can only attach local VHDs, not those on a network share.)

And for the record: For OS X there is a free program by Paragon, which does the 
same:

https://www.paragon-software.com/home/vd-mounter-mac-free/ 


So another thing VirtualBox can do as good as qemu.

Ulrich


--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] VirtualBox and FreeDOS

[Ulrich Hansen]

Just a quick update about FreeDOS and VirtualBox: 

The problem with UIDE.SYS freezing the boot process has been fixed in 
VirtualBox. The problem was caused by some unexpected behaviour of VirtualBox. 
Jack R. Ellis did provide a workaround since 2012, but it's good to see that 
also Oracle took care of the problem.

Another problems is also solved by VirtualBox: FreeDOS 1.1 now sees imediately 
if you connect a different CD image or change the floppy image. The "dir" 
command always shows the correct contents.

The "ICH9" chipset in VirtualBox "System" - "Motherboard" still conflicts with 
networking. The packet driver seems to load now, but still can't be reached by 
networking programs AFAIK. So FreeDOS users should stay with the default 
"PIIX3".

I updated the relevant VirtualBox pages in the FreeDOS wiki.

I also added a page about the JEMMEX crash at boot, several users reported. 
http://freedos.sourceforge.net/wiki/index.php/VirtualBox_-_JEMMEX

The new installer for FreeDOS 1.2 seems to be able to detect VirtualBox. 
@Jerome: What do you think about putting the correct includes for JEMMX into 
the line of option 1 in FDCONFIG.SYS if VirtualBox is detected? Probably after 
some more testing?

Ulrich
--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Keyboard input absent

[Ulrich Hansen]

Hi John,

> After running a Windows command line application from 
> "P&E Microcomputer Systems" to program Freescale MCU's there is no 
> keyboard input in the VDM. FreeDOS launches normally but there is no 
> keyboard input. If in Full Screen mode, Ctrl Esc works.

So the keyboard driver works in the Virtual DOS Machine (VDM) but it is still 
occupied by the P&E program.

> Perhaps the vectors are being 
> hi-jacked or the keyboard driver being replaced?

I am not an expert, but it seems you are right.

> P&E will not address 
> the problem. 

I just tried to research the problem and the first link on

http://www.pemicro.com/software/index.cfm

leads to

http://10.0.0.8/getting_started/dev_and_debug/flash_programming.cfm

So that does speak for itself.

Googling the problem brought two things:

This site says you could delete the keyboard controller from the device manager:

http://discussions.virtualdr.com/showthread.php?1426-Keyboard-suddenly-won-t-work-in-MS-DOS-mode

And this page suggests to use a ps/2 keyboard:

https://support.microsoft.com/en-us/kb/310923

Both answers do not sound exactly right for the problem...

Maybe someone else here has an idea how to completely unload the previous 
program.

Ulrich--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Keyboard input absent

[Ulrich Hansen]

>> 
>> leads to
>> 
>> http://10.0.0.8/getting_started/dev_and_debug/flash_programming.cfm
>> 
>> So that does speak for itself.
> 
> So somebody accidentally made that an intranet link there :-p

It was just a funny thing to see, but not relevant to your question. Normally 
these things are discovered pretty quickly. So either there is no customer 
interest in that page or they don’t read their weblogs. Or they just don’t 
care. :-)

Now about the problem:

Perhaps it is possible to try this program: TSRCOM (MARK and RELEASE). You get 
it here:

ftp://ftp.icm.edu.pl/pub/msdos/coast/tsrutil/

Look for a file TSRCOM35.ZIP. The function is explained in the TSR.DOC file. It 
is free for distribution and you are allowed to use it without paying anything 
- but it is not free software.

It works like this: You start MARK.COM. After that you start your P&E program. 
After you finished working with it, you run RELEASE.EXE.

Maybe this way it is possible to remove the P&E program completely from memory.

Good luck 
Ulrich





--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Keyboard input absent

[Ulrich Hansen]

I doubt it, but perhaps you check the environment settings with the command:

SET

Maybe there’s a wrong keyboard setting the P&E program left behind and you can 
delete it with:

SET NAMEOFVARABLE=

(I know, I know, this is too easy, but sometimes…) :-)

Ah and because you can’t get the keyboard to work AFTER you started the P&E 
program, try to chain that program with SET. I didn’t find a way to do it with 
command.com („&“ doesn’t work) so start 4dos first:

4dos

and then:

yourproblematicprogram.exe ^ SET

Just an idea...






--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Mounting VirtualBox FreeDOS images in Windows

[Ulrich Hansen]

After several tests I have decided to switch the ready-to-use FreeDOS images I 
provide on

https://www.lazybrowndog.net/freedos/virtualbox

to the VHD image type. Using VHD instead of VDI (the default type of 
VirtualBox) has the advantage that it can be mounted in Windows and other 
systems. So you can easily exchange files. You find a walkthrough at:

https://www.lazybrowndog.net/freedos/virtualbox/?page_id=443

I got the idea from our latest discussions, so thanks again!
--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Mounting VirtualBox FreeDOS images in Windows

[Ulrich Hansen]

> Am 09.07.2016 um 02:22 schrieb Rugxulo  >:
>> Using VHD instead of VDI has the advantage that it can be mounted in Windows
>> and other systems.
> 
> What other systems support VHD? Are there different versions (besides VHDX)?

You can mount the image in Windows, OS X and GNU/Linux. 

That just means you can open the virtual FreeDOS drive C:\ in Windows Explorer, 
Finder or Nautilus. 
It doesn’t mean that it runs with other virtualization software.

> Hmmm, I don't see any mention of "vhd" in qemu-img --help. And yet one
> random page says it supports "vhdx". Eh? Do they just call it "vpc"
> instead? Apparently so. (qemu-img does mention "vpc“.)

No. VHD has nothing to do with qemu. You can convert it though with "qemu-img" 
or with "VBoxManage clonehd“.

> But, once again, although I've never run many and thus don't know all
> the incompatibilities, I'd advise people not to be too trusting of
> so-called compatibility between emulators. Just because one partially
> supports .VMDK doesn't mean that it supports every feature (or every
> newer version). Caveat emptor. Bugs often happen, so test test test
> before you assume full compatibility with anything.

You are right. VirtualBox states VHD is fully supported.
https://www.virtualbox.org/manual/ch05.html#vdidetails 


I tested it the last days. I even tried to manipulate the harddisk image in 
Windows Explorer while FreeDOS was running, which is not advised. I couldn’t 
get it to break. 

Most people who are using FreeDOS in VirtualBox run Windows as host. Giving 
them the possibility to mount the FreeDOS disk C:\ to get their work into 
FreeDOS or out of it, seems like good idea. 

But I will keep the VDI updated and available on the website too. So everybody 
has a choice.

> So I'm not fully convinced (yet) that there is one portable, neutral
> format that will work across most emulators.

Me neither. VMDK might be a candidate. It is also fully supported by 
VirtualBox. And there even seems to be a vmware utility to mount the VMDK file 
as disk. 

https://my.vmware.com/web/vmware/details?productId=46&downloadGroup=WKST-550-DISK-MOUNT-UTL#product_downloads
 


Unfortunately this software is quite old and no longer supported so I am not 
sure about it.





.--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Mounting VirtualBox FreeDOS images in Windows

[Ulrich Hansen]

> Am 10.07.2016 um 10:42 schrieb userbeit...@abwesend.de:
> 
> VirtualPC version 2004 and 2007 are still freely available. I didn't 
> test if those versions work under Windows 7, 8/8.1 or 10 though, but if 
> they do this would be great news.
> 
> Virtual PC 2004 SP1:
> http://www.microsoft.com/en-US/download/details.aspx?id=3243
> 
> Virtual PC 2007 SP1:
> http://www.microsoft.com/en-US/download/details.aspx?id=24439

I tried the 2007 version on Windows 10. It’s the usual Windows crap: It 
installs fine. And then it tells you it can’t run.

As I found out, some version of VirtualPC is supposed to run under Windows 7 
Home. Higher versions (or Pro) are not supported. 


--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 - Preview 22

[Ulrich Hansen]

Thanks! This is really impressive!!

Just a quick remark:

I see that the Norton Commander clone doszip (DZ.EXE) is installed by default. 
Which is great! In VirtualBox though it would be better to activate in „Setup" 
- "System Options":

[ x ] „Use DOS Idle Int 2Fh“

Otherwise for VirtualBox users the CPU usage goes up to a 100 percent.

See: https://www.lazybrowndog.net/freedos/files/doszip-idle.png 


To prevent this, download
https://www.lazybrowndog.net/freedos/files/CFGDOS 


(which is an adapted configuration file of doszip)
and copy it, if the installation detects VirtualBox, into C:\FDOS\BIN.

This will activate the above setting.

regards
Ulrich


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] intel PRO/1000 DOS packet driver

[Ulrich Hansen]

Hi,

I found that the intel DOS packet driver for the PRO/1000 network card isn’t in 
the CRYNWR package.

As it is Open Source since 2007 I felt free to package it into an FDNPKG 
compatible zip-file. 

You can find it here: 
https://github.com/ulrich-hansen/E1000PKT 
<https://github.com/ulrich-hansen/E1000PKT>

cheers
Ulrich

--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] M2WAT

[Ulrich Hansen]

> Am 26.08.2016 um 00:29 schrieb Rugxulo :
> I’ve (also) put it here:
> 
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/e1000pkt.zip
> 
> (If you can think of a better place for it, let me know.)

Thank you. There is of course no better place.

What do you think of M2WAT? I use it quite often. It is Open Source, written by 
cordata, a FreeDOS user, in a post to this list. Wouldn’t it be a good 
candidate for the net section of your repo? I know it is a very small utility…

https://github.com/ulrich-hansen/M2WAT <https://github.com/ulrich-hansen/M2WAT>

cheers
Ulrich

--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] M2WAT

[Ulrich Hansen]

> Am 26.08.2016 um 08:28 schrieb Louis Santillan :
> 
> Made my own dog food:
> 
> 

Hi Louis,
Thanks for your work! It’s a nice idea to use a batch file for it. I just tried 
it. It works but has some flaws yet. Here’s the feedback:

1. If I run the program in AUTOEXEC.BAT I get several error messages. See:
https://www.lazybrowndog.net/freedos/files/m2wat.bat.png 


2. There should be some confirmation like "WATTCP.CFG has been updated".

3. The WATTCP.CFG is written with the values from MTCP.CFG. BUT: WATTCP.CFG is 
overwritten. 
Only the values from MTCP.CFG are kept. 

This can be a problem: WATTCP.CFG can be carefully crafted. Sometimes even 
passwords are stored there. It shouldn’t be overwritten.

See https://www.lazybrowndog.net/freedos/files/wattcp.cfg 
 for an example 
WATTCP.CFG with lots of settings. 

> On Thu, Aug 25, 2016 at 7:33 PM, Rugxulo  wrote:
>> 
>> Two minor nitpicks:
>> 
>> 1). The .COM isn't even UPX'd. Bloat!  ;-)
>> 2). The source is named "W2WAT.C", which is confusing.
>> 
>> Otherwise, seems fine. Should these minor issues be fixed first?

Yes I think these errors have been committed by me. I look into it (and might 
need some help with it).
M2WAT.COM  worked with the example WATTCP.CFG and just 
updated the lines that needed it.

Thanks for your help!
cheers
Ulrich




--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] M2WAT

[Ulrich Hansen]

> Am 27.08.2016 um 02:35 schrieb Louis Santillan :
> 
> My intention was to
> simply map what is obvious.  If someone has additional config, I'd
> suggest doing something like
> 
>   dhcp
>   m2wat
>   type %WATTCP.CFG%\WATPERM.CFG>>%WATTCP.CFG%\WATTCP.CFG

That wouldn’t work. For instance for Arachne the WATTCP.CFG could look like 
this:

my_ip = 0.0.0.0
netmask = 255.255.255.0
gateway = 0.0.0.0
#
sockdelay=40
hostname=arachne
mss=512

and the nameservers would be configured in ARACHNE.CFG. 

Your workaround would configure nameservers in WATTCP.CFG too. But this could 
mess things up. It shouldn’t configure a nameserver if there is none configured 
in WATTCP.CFG.

Unfortunately M2WAT.COM by cordata also does not get this right.

David Dunfields DHCP program from 
http://classiccmp.org/dunfield/dos/index.htm

does it correctly. There is even an option /F where you can choose to "fill-in 
config items not supplied in original file“.

The program is a bit hard to figure out, because the description in DCHP.TXT is 
not correct. 

Instead of 
DHCP P=60 /W='C:\FDOS\WATTCP.CFG'  /M='C:\FDOS\MTCP.CFG‘
you would need to write:
DHCP P=60 /W C:\FDOS\WATTCP.CFG
DHCP P=60 /M C:\FDOS\MTCP.CFG

(You can not write the /M option and the /W option in the same line.)

It does get the environment variable MTCPCFG from AUTOEXEC.BAT, but it doesn’t 
get the environment variable WATTCPCFG.

So
DHCP /M
would work, while
DHCP /W
wouldn’t.

But anyway you can work around this and the program works fine. Unfortunately 
there is no source file on the website and no license, so it couldn’t be 
bundled with FreeDOS.

cheers
Ulrich
























--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 official release!

[Ulrich Hansen]

Congratulations! Thanks to everybody who put so much work in it! 

Merry Christmas!

> Am 25.12.2016 um 16:17 schrieb Jim Hall :
> 
> I am proud to announce the release of FreeDOS 1.2! You can download it from 
> our website at www.freedos.org.
> 
> The latest official FreeDOS distribution is the result of the hard work from 
> many people. Thanks to everyone in the FreeDOS Project for their work towards 
> this new release! There are too many of you to recognize individually, but 
> you have all helped enormously. Thank you!
> 
> DOS is one of the oldest PC operating systems. FreeDOS has an equally long 
> history. We started the FreeDOS Project in 1994 to create a free, open source 
> software version of DOS. We made our first Alpha release in September 1994, 
> and our first Beta in March 1998. In September 2006, we finally released 
> FreeDOS 1.0. And in January 2012, we released FreeDOS 1.1.
> 
> The new FreeDOS 1.2 is mostly an incremental change over FreeDOS 1.1, 
> although you'll find a few nice surprises.
> 
> FreeDOS 1.2 now makes it easier to connect to a network. We include a 
> revamped network setup and useful network applications to get you online. Try 
> the Dillo web browser for a graphical web experience, or the Links web 
> browser if you want just the text.
> 
> If you're interested in updated functionality, you can find new tools under 
> the Utilities section. For example, FreeDOS 1.2 provides several image 
> enhancement programs like Pngcrush and Gifsicle. Or you can enhance the DOS 
> command line with Unix-like utilities like sed, grep, tee, head, and bc.
> 
> Many people use FreeDOS to play games, and FreeDOS 1.2 now includes several 
> open source games for you to try. We include Freedoom and Boom for classic 
> first-person shooter fans. Arcade-style game fans will like Wing, a familiar 
> space shooter game, or Kiloblaster, a fast-paced arcade shooter. Classic 
> gamers will want to try Nethack, Invaders, Sudoku, and Tetris. For those who 
> want to play their own classic DOS games, we provide other tools like 
> Slowdown, so you can run certain older games on a fast modern computer.
> 
> But I think the first thing you'll notice about FreeDOS 1.2 is the new 
> installer! I wanted to make the install process an easy one, for new and 
> experienced users alike. And we have that in the new FreeDOS 1.2 installer, 
> thanks to Jerome Shidel. If you are a new user, the installer makes it easy 
> to install FreeDOS and get going with a few defaults. If you're an 
> experienced DOS user, you can unlock the Advanced installer that lets you 
> tweak the FreeDOS install to your preference.
> 
> I'm very excited for the new FreeDOS 1.2 distribution!
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bug with FreeDOS 1.2 and "find"?

[Ulrich Hansen]

> Am 16.01.2017 um 13:12 schrieb BlameTroi :
> I got this after a FIND command.
> 
> C:\ELVIS\DOC>find /i "env" e*.htm
>  file list ...
> Error reading from drive A: DOS area: general failure
> 
> I've triple checked and I have nothing in my autoexec or config that
> points to drive A:, nor does A: show up in any of the environment
> variables. Of course, that drive is empty.

I can verify the problem in FreeDOS 1.2. It doesn’t happen in FreeDOS 1.1. 
Look at the screenshot:
https://lazybrowndog.net/freedos/files/find-bug.png




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bug with FreeDOS 1.2 and "find"?

[Ulrich Hansen]

> Am 20.01.2017 um 17:21 schrieb Tom Ehlert :
> 
> as stated elsewhere, the bug happens when
> 
>FIND is compiled using TC 2.01
>you have no drive in A:
> 
> it's simply a bug in FIND

Thank you very much. I was just curious. Never came across it before.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Some struggle with SSH2DOS (solved)

[Ulrich Hansen]

Hi all,

Thanks to Jerome, there is now SSH2DOS in the FreeDOS net repo, which is great!

Unfortunately even this free SSH client is getting a bit rusty, the latest 
version is 11 years old.

As I found out, it wouldn’t connect to my server (Ubuntu 16.04 LTS). 
But it still connected fine to a Debian Wheezy machine.

In the end I found the problem: OpenSSH versions >=6.7 have disabled a 
necessary KexAlgorithm and a Cipher.

Here is a report. I also posted it on the SSH2DOS page on SourceForge.

Hope this helps others eventually...
Ulrich



1. The solution:

Add the following lines to /etc/ssh/sshd_config on the server:

Ciphers aes128-cbc
KexAlgorithms diffie-hellman-group-exchange-sha1


2. The problem:

SSH2DOS works fine with a Debian Wheezy machine with OpenSSH 6.0.

But it does not connect to a Debian 8 machine with OpenSSH 6.7.
It also does not connect to a Ubuntu 16.04 server with OpenSSH 7.2.

SSH2DOS gives the following error code:

C:\> ssh2d386 username 192.168.1.136
SSH2DOS v0.2.1. 386+ version
Remote host closed connection
DH key exchange failed
Socket write error. File: transprt.c, line:698
Remote reset connection

On the server /var/log/auth.log says:
Jan 23 00:17:25 debian8 sshd [1883]: fatal: Unable to negotiate a key exchange 
method [preauth]

SSH2D386 with the -d option writes the following DEBUG.PKT:


---

RECEIVED packet:
14 63 99 7B 69 DA 8E 90 00 02 0A 69 D1 32 93 26 
E1 00 00 00 96 63 75 72 76 65 32 35 35 31 39 2D 
73 68 61 32 35 36 40 6C 69 62 73 73 68 2E 6F 72 
67 2C 65 63 64 68 2D 73 68 61 32 2D 6E 69 73 74 
70 32 35 36 2C 65 63 64 68 2D 73 68 61 32 2D 6E 
69 73 74 70 33 38 34 2C 65 63 64 68 2D 73 68 61 
32 2D 6E 69 73 74 70 35 32 31 2C 64 69 66 66 69 
65 2D 68 65 6C 6C 6D 61 6E 2D 67 72 6F 75 70 2D 
65 78 63 68 61 6E 67 65 2D 73 68 61 32 35 36 2C 
64 69 66 66 69 65 2D 68 65 6C 6C 6D 61 6E 2D 67 
72 6F 75 70 31 34 2D 73 68 61 31 00 00 00 41 73 
73 68 2D 72 73 61 2C 72 73 61 2D 73 68 61 32 2D 
35 31 32 2C 72 73 61 2D 73 68 61 32 2D 32 35 36 
2C 65 63 64 73 61 2D 73 68 61 32 2D 6E 69 73 74 
70 32 35 36 2C 73 73 68 2D 65 64 32 35 35 31 39 
00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C 
79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F 
6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73 
31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63 
74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70 
65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36 
2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 
00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C 
79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F 
6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73 
31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63 
74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70 
65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36 
2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 
00 00 00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40 
6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 
2D 31 32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68 
2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 
35 36 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 
6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 
2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 
2C 68 6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F 
70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 
36 34 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 
6D 61 63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E 
63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 
36 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C 
68 6D 61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61 
63 2D 36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68 
2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74 
6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 
61 63 2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40 
6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 
2D 73 68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70 
65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 
68 61 31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 
63 6F 6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E 
73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 
40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 
63 2D 73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D 
73 68 61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68 
61 31 00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40 
6F 70 65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E 
6F 6E 65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68 
2E 63 6F 6D 00 00 00 00 00 00 00 00 00 00 00 00 
00 
.c.{i..i.2.&
.curve25519-
sha...@libssh.or
g,ecdh-sha2-nist
p256,ecdh-sha2-n
istp384,ecdh-sha
2-nistp521,diffi
e-hellman-group-
exchange-sha256,
diffie-hellman-g
roup14-sha1...As
sh-rsa,rsa-sha2-
512,rsa-sha2-256
,ecdsa-sha2-nist
p256,ssh-ed25519
...lchacha20-pol
y1...@openssh.co
m,aes128-ctr,aes
192-ctr,aes256-c
tr,aes128-gcm@op
enssh.com,aes256
-g...@openssh.com
...lchacha20-pol
y1...@openssh.co
m,aes128-ctr,aes
192-ctr,aes256-c
tr,aes128-gcm@op
enssh.com,aes256
-g...@openssh.com
umac-64-etm@
openssh.com,umac
-128-etm@openssh
.com,hmac-sha2-2
56-etm@openssh.c
om,hmac-sha2-512
-e...@openssh.com
,hmac-sha1-etm@o
penssh.com,umac-
6...@openssh.com,u
ma

Re: [Freedos-user] SSH2DOS - no connection with recent servers

[Ulrich Hansen]

q
.xterm...P..
..

SENT packet:
62 00 00 00 00 00 00 00 05 73 68 65 6C 6C 01 
bshell.






> Am 23.01.2017 um 01:22 schrieb Ulrich Hansen :
> 
> Hi all,
> 
> Thanks to Jerome, there is now SSH2DOS in the FreeDOS net repo, which is 
> great!
> 
> Unfortunately even this free SSH client is getting a bit rusty, the latest 
> version is 11 years old.
> 
> As I found out, it wouldn’t connect to my server (Ubuntu 16.04 LTS). 
> But it still connected fine to a Debian Wheezy machine.
> 
> In the end I found the problem: OpenSSH versions >=6.7 have disabled a 
> necessary KexAlgorithm and a Cipher.
> 
> Here is a report. I also posted it on the SSH2DOS page on SourceForge.
> 
> Hope this helps others eventually...
> Ulrich
> 
> 
> 
> 1. The solution:
> 
> Add the following lines to /etc/ssh/sshd_config on the server:
> 
> Ciphers aes128-cbc
> KexAlgorithms diffie-hellman-group-exchange-sha1
> 
> 
> 2. The problem:
> 
> SSH2DOS works fine with a Debian Wheezy machine with OpenSSH 6.0.
> 
> But it does not connect to a Debian 8 machine with OpenSSH 6.7.
> It also does not connect to a Ubuntu 16.04 server with OpenSSH 7.2.
> 
> SSH2DOS gives the following error code:
> 
> C:\> ssh2d386 username 192.168.1.136
> SSH2DOS v0.2.1. 386+ version
> Remote host closed connection
> DH key exchange failed
> Socket write error. File: transprt.c, line:698
> Remote reset connection
> 
> On the server /var/log/auth.log says:
> Jan 23 00:17:25 debian8 sshd [1883]: fatal: Unable to negotiate a key 
> exchange method [preauth]
> 
> SSH2D386 with the -d option writes the following DEBUG.PKT:
> 
> 
> ---
> 
> RECEIVED packet:
> 14 63 99 7B 69 DA 8E 90 00 02 0A 69 D1 32 93 26 
> E1 00 00 00 96 63 75 72 76 65 32 35 35 31 39 2D 
> 73 68 61 32 35 36 40 6C 69 62 73 73 68 2E 6F 72 
> 67 2C 65 63 64 68 2D 73 68 61 32 2D 6E 69 73 74 
> 70 32 35 36 2C 65 63 64 68 2D 73 68 61 32 2D 6E 
> 69 73 74 70 33 38 34 2C 65 63 64 68 2D 73 68 61 
> 32 2D 6E 69 73 74 70 35 32 31 2C 64 69 66 66 69 
> 65 2D 68 65 6C 6C 6D 61 6E 2D 67 72 6F 75 70 2D 
> 65 78 63 68 61 6E 67 65 2D 73 68 61 32 35 36 2C 
> 64 69 66 66 69 65 2D 68 65 6C 6C 6D 61 6E 2D 67 
> 72 6F 75 70 31 34 2D 73 68 61 31 00 00 00 41 73 
> 73 68 2D 72 73 61 2C 72 73 61 2D 73 68 61 32 2D 
> 35 31 32 2C 72 73 61 2D 73 68 61 32 2D 32 35 36 
> 2C 65 63 64 73 61 2D 73 68 61 32 2D 6E 69 73 74 
> 70 32 35 36 2C 73 73 68 2D 65 64 32 35 35 31 39 
> 00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C 
> 79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F 
> 6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73 
> 31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63 
> 74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70 
> 65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36 
> 2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 
> 00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C 
> 79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F 
> 6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73 
> 31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63 
> 74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70 
> 65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36 
> 2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 
> 00 00 00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40 
> 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 
> 2D 31 32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68 
> 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 
> 35 36 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 
> 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 
> 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 
> 2C 68 6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F 
> 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 
> 36 34 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 
> 6D 61 63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E 
> 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 
> 36 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C 
> 68 6D 61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61 
> 63 2D 36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68 
> 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74 
> 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 
> 61 63 2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40 
> 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 
> 2D 73 68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70 
> 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 
> 68 61 31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 
> 63 6F 6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E 
> 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 
> 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 
> 63 2D 73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D 
> 73 68 61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68 
> 61 31 00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40 
> 6F 70 65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E 
> 6F 6E 65 2C 7A 6C 69

Re: [Freedos-user] SSH2DOS - no connection with recent servers

[Ulrich Hansen]

> Am 26.01.2017 um 18:19 schrieb Karen Lewellen :
> 
> As I am presently writing this e-mail using ssh2d386 from the ssh2dos 
> package ssh2021b,  perhaps I can help you troubleshoot.

Hi Karen!

I am using the exact same program and version.

> for the record, I am not using freedos, but  the ms dos 7.10 package 
> mentioned on this list.
> Still every day several times a day I connect  to two different servers 
> using  this package.

I guess your servers still run OpenSSH in versions earlier than 6.9.

> may I ask again what your issue is presently?

Actually I have given up on it. I spent another day trying to get it to work, 
but without success.

The problem is that I can’t connect to an Ubuntu 16.04 LTS server with OpenSSH 
7.2.

SSH2D386 gives the message:

 Expected KEX_DH_GEX_GROUP
 DH key exchange failed

The server logs:
 Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol error: 
type 30 seq 1 [preauth]
 Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received disconnect 
from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO

As I wrote I already had problems connecting to a Debian 8 server with OpenSSH 
6.7. 
But there I could fix it with these lines in /etc/ssh/sshd_config on the server.

 Ciphers aes128-cbc
 KexAlgorithms diffie-hellman-group-exchange-sha1
 MACs hmac-sha1
 HostKeyAlgorithms ssh-css

But in OpenSSH 7.2 this didn’t work. 

What else did I try?

I tried to set MTU=576 in C:\FDOS\WATTCP.CFG.

I tried to recompile OpenSSH.
The first time with adding this line in in compat.c: 
 { "SSHDOS*",   SSH_OLD_DHGEX },
The second time with this one:
 { "SSHDOS*",   SSH_BUG_NOREKEY|SSH_BUG_FIRSTKEX },

Both were not able to let SSH2D386 connect. It worked great with other SSH 
clients.

The idea was that SSH2DOS uses code from PuTTY and there were already several 
exceptions in combat.c for old PuTTY versions. The reason seems to be that 
OpenSSH implemented RFC4419 and old PuTTY versions and SSH2DOS did not. See 
[1], [2]. 

I even looked at the SSH2DOS source code. But I have no experience with 
OpenWatcom. I installed it but gave up, when I saw I also had to compile the 
WATT32 TCP/IP stack.

SSH2DOS uses PuTTY code, which is also Free Software. So in theory it should be 
possible to replace the old PuTTY code with a more recent one.

cheers
Ulrich


[1] https://forums.red-gate.com/viewtopic.php?f=198&t=78958
[2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/rfc4419.html



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] SSH2DOS - no connection with recent servers

[Ulrich Hansen]

Wow. I am stunned. This has solved the problem. I have spent more than a day 
searching for such a solution.

I am now able to log into a Ubuntu 16.04 LTS server with OpenSSH 7.2
Client is a fresh install of FreeDOS 1.2 where I installed ssh2dos with "FDNPKG 
install ssh2dos"

Thank you very, very much!

Ulrich



> Am 27.01.2017 um 06:39 schrieb Dan Schmidt :
> 
> I forgot - you may need to regenerate your keys with "ssh-keygen -A" after 
> modifying the server. 
> 
> On Thu, Jan 26, 2017 at 10:38 PM, Dan Schmidt  <mailto:helpdesk...@gmail.com>> wrote:
> I am unsure what it is that makes ssh2dos so unstable for me - nobody else 
> has this issue? 
> 
> I would like to answer Ulrich on how he can modify his Ubuntu server, but 
> first, a warning: These algorithms were disabled because they are obsolete 
> and insecure.  Using a token based login, such as google-authenticator, may 
> be advisable if your server is public facing.  
> 
> Firstly, add this to your server's /etc/ssh/sshd_config:
> 
> KexAlgorithms diffie-hellman-group1-sha1,curve25519-sha...@libssh.org 
> <mailto:curve25519-sha...@libssh.org>,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
> Ciphers 3des-cbc,blowfish-cbc,aes128-cbc,aes128-ctr,aes256-ctr
> HostKeyAlgorithms +ssh-dss
> 
> Then, make use of the -g option - it goes BEFORE your username in ssh2dos.  
> You should now be able to connect.  
> 
> I do not know why simply adding +diffie-hellman-group1-sha1 doesn't work, it 
> seems it should.  Also, I was in a rush - I may be excluding some newer 
> options - report back if you find/add them with success. 
> 
> -Dan
> 
> On Thu, Jan 26, 2017 at 9:42 PM, Karen Lewellen  <mailto:klewel...@shellworld.net>> wrote:
> Hi Bill,
> While I appreciate your desire for wisdom, I feel rather sure  my specific 
> situation will not apply to anyone else here most likely.
> I use ssh2d386 to  access at least one commercial shell, but those shell 
> services are maintained by others.  I am not for example accessing my own 
> server.
> If the servers you desire reaching are run by other people,  give me an 
> example and I will try.
> If my many years of computing has taught me anything is that the word 
> Personal  is important for a reason.
> Kare
> 
> 
> 
> On Thu, 26 Jan 2017, William Dudley wrote:
> 
> Karen,
> 
> If you know how to get ssh2d386 to connect to a modern openssh, as on
> Ubuntu 16.04,
> please share the recipe with us!
> 
> Thanks,
> Bill Dudley
> 
> 
> This email is free of malware because I run Linux.
> 
> On Thu, Jan 26, 2017 at 9:10 PM, Karen Lewellen  <mailto:klewel...@shellworld.net>>
> wrote:
> 
> Well, if you have given up no point in my sharing.
> We use the same edition of Ubuntu, both with dreamhost who has my office,
> and here at shellworld.
> While the latter requires me to make use of a few ssh2021b options, the -g
> option  for example, I encounter no issues.
> I am going to guess that  things like machine speed, mine is a p3 with
> allot of memory, impacts your situation.
> nor, I would hope, your  location in the world.
> Sorry I did not notice your post before you abandoned  the effort.
> Kare
> 
> 
> 
> On Fri, 27 Jan 2017, Ulrich Hansen wrote:
> 
> 
> Am 26.01.2017 um 18:19 schrieb Karen Lewellen  <mailto:klewel...@shellworld.net>>:
> 
> As I am presently writing this e-mail using ssh2d386 from the ssh2dos
> package ssh2021b,  perhaps I can help you troubleshoot.
> 
> 
> Hi Karen!
> 
> I am using the exact same program and version.
> 
> for the record, I am not using freedos, but  the ms dos 7.10 package
> mentioned on this list.
> Still every day several times a day I connect  to two different servers
> using  this package.
> 
> 
> I guess your servers still run OpenSSH in versions earlier than 6.9.
> 
> may I ask again what your issue is presently?
> 
> 
> Actually I have given up on it. I spent another day trying to get it to
> work, but without success.
> 
> The problem is that I can’t connect to an Ubuntu 16.04 LTS server with
> OpenSSH 7.2.
> 
> SSH2D386 gives the message:
> 
> Expected KEX_DH_GEX_GROUP
> DH key exchange failed
> 
> The server logs:
> Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol
> error: type 30 seq 1 [preauth]
> Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received
> disconnect from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO
> 
> As I wrote I already had problems connecting to a Debian 8 server with
> OpenSSH 6.7.
> But there I co

Re: [Freedos-user] SSH2DOS - no connection with recent servers

[Ulrich Hansen]

> Am 28.01.2017 um 06:23 schrieb Karen Lewellen :
> 
> To answer your question for myself, I never have this issue.  No crashes, and 
> i  can spend hours working on line.  Further I have done more than my share 
> of downloads with sftpd386 as well.


> On Fri, 27 Jan 2017, Dan Schmidt wrote:
>> 
>> My ssh2dos is very unstable - it usually crashes on exit or after five to
>> ten minutes.  Do you have this issue as well?  I am curious if I should try
>> a different version of DOS.



I made the same experience as Karen: I had SSH2D386 running more or less the 
whole morning while logged into the server. I even ran „top“ for over an hour 
to test the program. No crashes, no sudden exits.

Other experiences:

- As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does use 
the host’s CPU by 100 percent. I limit the CPU execution cap in the VirtualBox 
settings to 40%, but the fan of my MacBookPro is still running constantly (but 
on a lower level than at 100%).

- After logging into the server, I run the command "export LANG=C“ first. 
Otherwise „graphical“ console programs like midnight commander or 
dpkg-reconfigure will show wrong characters in SSH2DOS.

So far so good. Thanks to you everything is working well now.

Ulrich


.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] questions on FreeDOS

[Ulrich Hansen]

> Am 01.02.2017 um 07:06 schrieb herminio.hernande...@gmail.com:
> 
> I launched the VM verifed it has an ip address and I can ping out, but
> my laptop cannot ping FreeDOS. However FreeDOS can ping my laptop…

No of course not. There’s no service running that can answer the ping.
You need to start a service that listens to the network. For instance mTCP’s 
ftpsrv.

You need to configure the network and ftpsrv first. See:

http://wiki.freedos.org/wiki/index.php/VirtualBox_-_Chapter_5 

and
http://wiki.freedos.org/wiki/index.php/VirtualBox_-_Chapter_7 


(both pages were updated this morning...)

Good luck!


> 
> Herminio
> 
> On Tue, 2017-01-31 at 21:08 -0800, Louis Santillan wrote:
>> In VirtualBox, you can start the VM with VNC enabled [0].
>> 
>> 
>> [0] https://www.virtualbox.org/manual/ch07.html
>> 
>> On Tue, Jan 31, 2017 at 8:31 PM,  
>> wrote:
>>> Corbin,
>>> 
>>> Thanks that did it!
>>> 
>>> Herminio
>>> 
>>> On Wed, 2017-02-01 at 03:20 +, Corbin Davenport wrote:
 1. You can get sound in VirtualBox by changing the VM audio
 device to
 SoundBlaster 16. You can do this by opening the VM settings,
 going to
 sound, and selecting SoundBlaster 16 as the audio controller.
 
 2. I'm not sure if this is possible, maybe someone else can chime
 in
 about that.
 
 Corbin
 
 
 On Tue, Jan 31, 2017 at 10:15 PM 
 wrote:
> Hello,
> 
> I just started tinkering with FreeDOS after listening  to Jim
> Hall
> on
> the Lunduke Hour. I think this project is so cool! I do have
> some
> questions.
> 
> 1. is there any way to have sound working while in Virtualbox?
> 
> 2. is there a way to set FreeDOS as a VNC, telnet, or even SSH
> server?
> I would have a full screen session when playing some of the DOS
> games.
> 
> Thanks for you time!
> Herminio---
> 
> ---
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> 
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 
 
 --
 Corbin D
 
 
 ---
 
 ---
 Check out the vibrant tech community on one of the world's most
 engaging tech sites, SlashDot.org! http://sdm.link/slashdot
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user
 
>>> 
>>> -
>>> -
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>> 
>> 
>> ---
>> ---
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! 
> http://sdm.link/slashdot___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.2 & VirtualBox: Wiki updated

[Ulrich Hansen]

I have updated the pages at:

http://wiki.freedos.org/wiki/index.php/VirtualBox 


FreeDOS 1.2, especially the new installer, FDIMPLES and FDNPKG have made many 
things easier, especially installing a network. :-)

I also added an explanation how to mount the FreeDOS image in Windows, Mac and 
Ubuntu. And there’s a page about configuring a VirtualBox network with NAT and 
port forwarding. 

By the way: Jim Hall has repaired the upload of pictures to the wiki, which was 
broken. So if anybody else wants to add knowledge and screenshots and 
explanations to the wiki, now is probably a good time to mail Jim for a login  
:-)--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS images for VirtualBox

[Ulrich Hansen]

I also had time to update my VirtualBox images of FreeDOS. So if anybody liked 
these images in the past: Here are the new ones: :-)

https://www.lazybrowndog.net/freedos/virtualbox/ 




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS images for VirtualBox

[Ulrich Hansen]

> Am 02.02.2017 um 08:57 schrieb Ralf Quint :
> Well,...
>> Not Found
>> 

Oh, sorry. I forgot to change one of the two links there. Thanks!! I repaired 
it.

> On the side for the version supposedly without network, you are talking an 
> awful lot about the networking stuff being installed

Hmm. You’ve got a point. The thing is: FTPSRV was for some years the fastest 
way of getting files in and out of the FreeDOS guest. So I considered it 
something most people would want, also in the „normal“ image without additional 
networking software.

Now with the VHD image type, you can mount it in your host OS and drag’n drop 
files with your Explorer, Nautilus, Finder, whatever. So now in VirtualBox 
FreeDOS can be used fine without a network.

So you’re right. But what are you suggesting? Making the FreeDOS1.2 image just 
a pure FreeDOS 1.2 version without any changes?



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS images for VirtualBox

[Ulrich Hansen]

>> 2017-02-03 Ralf Quint:
> 
>>> Well, that works only with VMware, but unfortunately not with
>>> VirtualBox, AFAIK.
> 
>> Right.
> 
> As with drivers for other things, it would still be good to
> include vmsmount for those who use vmware to run FreeDOS :-)

Vmware uses vmdk images, my VirtualBox images are VHD. So that’s a whole new 
story. 

I don’t see much use in including vmsmount on VHD image. And I have no 
experience with converting everything to VMDK images, how reliable they work 
with VirtualBox on Windows, Ubuntu and Mac hosts or how they can be mounted 
from the host OS. So that would require some researching and creating and 
converting and re-writing. 

At the moment I would prefer a separate image for vmware users.

@Eric and @Ralf: About the clean FreeDOS 1.2 VirtualBox image:

I have done it: It is now EXACTLY what you get by installing manually with the 
FD12CD.iso and accepting everything. No networking. :-)

See: https://www.lazybrowndog.net/freedos/virtualbox/?page_id=21 


cheers
Ulrich--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

[Ulrich Hansen]

In FreeDOS 1.1 there was a boot option 4 „Load FreeDOS without drivers“. [see 
picture 1]
It booted a clean system, with SYSTEM and COMMAND and nothing else. [2]

In FreeDOS 1.2 there is a boot option 3 „Load FreeDOS without drivers 
(Emergency Mode) [3]
If you choose it, you load FreeDOS with drivers: HIMEMX, FDAPM, CTMOUSE, UDVD2, 
SHSUCDX… [4]

Wouldn’t it be better not to load drivers? If people choose not to? It’s called 
„Emergency mode“ after all...

There is also a boot option 4 „Load FreeDOS low with some drivers (Safe Mode)“ 
[5]
But it is not loaded LOW, as promised. In FDCONFIG.SYS you find:
124?DOS=HIGH
…
124?DOSDATA=UMB
Isn't this the opposite of low? [6] 

Probably there’s a quick way to fix the whole thing: Exchange only the titles 
of menu options  3 and 4 and delete every 4? in FDCONFIG.SYS except the line 
that loads SHELL=C:\FDOS\BIN\COMMAND.COM.  [7] 

Wouldn’t this make more sense? Please correct me if I’m wrong.

[1] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers.png 

[2] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers2.png 

[3] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers.png 

[4] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers2.png 

[5] https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers.png 

[6] https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers2.png 


[7] New FDCONFIG.SYS:

SET DOSDIR=C:\FDOS

!COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS
!LASTDRIVE=Z
!BUFFERS=20
!FILES=40
!MENUCOLOR=7,0

MENUDEFAULT=2,5
MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free
MENU 2 - Load FreeDOS with EMM386 (Expanded Memory) and SHARE loaded
MENU 3 - Load FreeDOS low with some drivers (Safe Mode)
MENU 4 - Load FreeDOS without drivers (Emergency Mode)

12?DOS=HIGH
12?DOS=UMB
12?DOSDATA=UMB
1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
23?DEVICE=C:\FDOS\BIN\HIMEMX.EXE
2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG
34?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT
12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

[Ulrich Hansen]

> Am 08.02.2017 um 22:46 schrieb Jerome Shidel  >:
> 
> Bug? Not really.
> Is it correct? Not even close.

Then lets correct it. :-) It’s pretty easy, as I showed in my last mail. 

> Also, #2 should not say EMM386 when it uses JEMM386. 

That’s even easier. :-)

> The current 1.2 config files are based on a clean install of 1.1 into VMware 
> Fusion. Then a some things were added, moved, changed and removed.

Yes, the following line (which skipped all the drivers)

if "%config%“=="4" GOTO END

was left in AUTOEXEC.BAT although the "no drivers“ option was changed to config 
3 in FDCONFIG.SYS. That may have been the root of all evil…

At the moment both options are doing the opposite of what they say they do. 
Instead of loading DOS low with some drivers, option 4 loads DOS high with no 
drivers. Nobody complained about that, so here is another suggestion: 

How about DROPPING option 4 (SOME DRIVERS) completely? Was it ever useful? 
People can always hit F8 for singlestepping...

I suggest to keep the NO DRIVERS option though, which should be exactly that: 
No drivers, no memory managers, DOS not loaded high.

Dropping option 4 and keeping a clean option3 would mean deleting everything 
with a 4 in FDCONFIG.SYS and removing the 3 from the HIMEMX line. And changing 
the line in AUTOEXEC.BAT to 

if "%config%“=="3" GOTO END

If this is too radical, see the suggestion in my last mail...

Ulrich--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] SSH2DOS - no connection with recent servers

[Ulrich Hansen]

> Am 13.02.2017 um 06:19 schrieb Dan Schmidt  <mailto:helpdesk...@gmail.com>>:
> 
> I hope I am not committing the dreaded "forum necromancy“ 

I had to look that up… I really liked the picture of the ghoul in the first 
google result :-))

> but I thought I might document that the 386 version, combined with the 
> mentioned "reset" trick, has solved my issues with ssh2dos stability, thank 
> you for the idea.  

Congratulation! But as I see it, it was your idea all along. 
> 
> Also, quick type-o - "I am not sure why you would want to run SSH in DOS in 
> VirtualBox"  I did not mean to imply that running Dos on VirtualBox is at all 
> strange. 

Well… It kind of IS strange. ;-) The reason is simple: I have a bit time to 
kill at the moment, so I was taking another look at my 
VirtualBox/FreeDOS/Networking images I started a few years ago at 
https://www.lazybrowndog.net/freedos/virtualbox/ 
<https://www.lazybrowndog.net/freedos/virtualbox/>. I updated them to FreeDOS 
1.2 and was checking if everything still works as expected. And well, SSH2DOS 
wasn’t and I was unable to find a fix. So thank you again for your help!

At the moment I’m updating the MS Client pages (sigh). 



> Am 13.02.2017 um 06:19 schrieb Dan Schmidt :
> 
> I hope I am not committing the dreaded "forum necromancy" but I thought I 
> might document that the 386 version, combined with the mentioned "reset" 
> trick, has solved my issues with ssh2dos stability, thank you for the idea.  
> 
> Also, quick type-o - "I am not sure why you would want to run SSH in DOS in 
> VirtualBox"  I did not mean to imply that running Dos on VirtualBox is at all 
> strange.  
> 
> On Mon, Jan 30, 2017 at 9:35 PM, Dan Schmidt  <mailto:helpdesk...@gmail.com>> wrote:
> I didn't try the 386 version, perhaps that will be more stable.  Also, if you 
> type "reset" before exiting, you can avoid "missing dos screen."  (IE - the 
> crash every time I exited)  
> 
> Ulrich, my friend, I am not sure why you would want to run DOS in VIrtualBox 
> on a MacBookPro, but I am glad I could help you.  :-)  Years ago, several 
> other technicians laughed at me when I bought an old Pentium for $5 
> saying"You can't do anything with that!" FreeDos helped me prove them wrong.
> 
> On Sat, Jan 28, 2017 at 8:02 AM, Ulrich Hansen  <mailto:my.gr...@mailbox.org>> wrote:
> 
>> Am 28.01.2017 um 06:23 schrieb Karen Lewellen > <mailto:klewel...@shellworld.net>>:
>> 
>> To answer your question for myself, I never have this issue.  No crashes, 
>> and i  can spend hours working on line.  Further I have done more than my 
>> share of downloads with sftpd386 as well.
> 
> 
>> On Fri, 27 Jan 2017, Dan Schmidt wrote:
>>> 
>>> My ssh2dos is very unstable - it usually crashes on exit or after five to
>>> ten minutes.  Do you have this issue as well?  I am curious if I should try
>>> a different version of DOS.
> 
> 
> 
> I made the same experience as Karen: I had SSH2D386 running more or less the 
> whole morning while logged into the server. I even ran „top“ for over an hour 
> to test the program. No crashes, no sudden exits.
> 
> Other experiences:
> 
> - As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does 
> use the host’s CPU by 100 percent. I limit the CPU execution cap in the 
> VirtualBox settings to 40%, but the fan of my MacBookPro is still running 
> constantly (but on a lower level than at 100%).
> 
> - After logging into the server, I run the command "export LANG=C“ first. 
> Otherwise „graphical“ console programs like midnight commander or 
> dpkg-reconfigure will show wrong characters in SSH2DOS.
> 
> So far so good. Thanks to you everything is working well now.
> 
> Ulrich
> 
> 
> .
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot 
> <http://sdm.link/slashdot>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net <mailto:Freedos-user@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/freedos-user 
> <https://lists.sourceforge.net/lists/listinfo/freedos-user>
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! 
> http://sdm.link/slashdot___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] WIFI on DOS (was: bsum - compute BSD checksums of your files)

[Ulrich Hansen]

Several years ago I wrote everything I could find out about DOS and Wifi here:

http://wiki.freedos.org/wiki/index.php/WiFi

If anybody finds out more about it, please give some feedback...


> On Wed, 19 Apr 2017 15:07:35 -0400 dmccunney 
> writes:
>> On Wed, Apr 19, 2017 at 11:14 AM, Dale E Sterner 
>>  wrote:
>>> I see that someone on Ebay is selling an HP mini
>>> with a FREEDOS os installed. All the HP minis that
>>> I've seen have wifi & bluetooth built in. That would
>>> mean an 802.11 client to do it. The ad doesn't
>>> mention wifi or bluetooth but every mini that I've seen
>>> has it.
>> 
>> The machine may have the *hardware*.  Whether the hardware will be
>> *usable* will depend on software.
>> 
>> MSDOS was written back before Wifi and Bluetooth *existed*.  FreeDOS
>> tries to be compatible with MSDOS, which means "support for what
>> existed when MSDOS was current."
>> 
>> I would *not* expect Wifi or Bluetooth to be usable on the machine 
>> in
>> FreeDOS, because the drivers don't exist.  If you want to use Wifi 
>> or
>> Bluetooth on that hardware, you'll need to install another OS that
>> supports them.  (Depending on exactly which HP mini model it is, 
>> there
>> might be a flavor of Linux that can do it.)
>> __
>> Dennis
>> 
>> 
> -
> -
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> 
> 
> 
> **
>> From Dale Sterner - MS organic chemistry
> http://pubs.acs.org/doi/abs/10.1021/jo00975a052
> ***
> 
> 
> The Easiest Way To Shed Deep Fat?
> 3 Harmful Foods
> http://thirdpartyoffers.juno.com/TGL3141/58f7bb5e84cae3b5e7b11st02duc
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] WIFI on DOS (was: bsum - compute BSD checksums of your files)

[Ulrich Hansen]

> Am 24.04.2017 um 07:07 schrieb Dan Schmidt :
> 
> Is this thread still about wireless for Dos?  If not, sorry for posting. 
> 
> If so, I bought a wireless to ethernet bridge - smaller than a deck of cards, 
> runs on usb power - works great for my Dos machine.  I tried a wifi card that 
> supposedly supported dos - never could get it working, threw it away in 
> disgust. 

This sounds interesting. Is it something like this?
https://www.amazon.com/dp/B00TQEX8BO/ref=psdc_300189_t2_B00HZWOQZ6
Thanks for the hint.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] intel PRO/

[ULRICH HANSEN]

From: Ulrich Hansen 


--===0960103510740450048==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_580697E5-5269-4247-B825-0748D819AC18"


--Apple-Mail=_580697E5-5269-4247-B825-0748D819AC18
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8

Hi,

I found that the intel DOS packet driver for the PRO/1000 network card isnrCOt
in the CRYNWR package.

As it is Open Source since 2007 I felt free to package it into an FDNPKG
compatible zip-file.

You can find it here:
https://github.com/ulrich-hansen/E1000PKT
<https://github.com/ulrich-hansen/E1000PKT>

cheers
Ulrich


--Apple-Mail=_580697E5-5269-4247-B825-0748D819AC18
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8

Hi,I found that
the intel DOS packet driver for the PRO/1000 network card isnrCOt in the CRYNWR
package.As it is Open
Source since 2007 I felt free to package it into an FDNPKG compatible
zip-file. You can
find it here: https://github.com/ulrich-hansen/E1000PKT";
class="">https://github.com/ulrich-hansen/E1000PKTcheersUlrich
--Apple-Mail=_580697E5-5269-4247-B825-0748D819AC18--


--===0960103510740450048==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--

--===0960103510740450048==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--===0960103510740450048==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99)

---
 * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] M2WAT

[ULRICH HANSEN]

From: Ulrich Hansen 


--===2823962537366983409==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_4A53FD72-58A0-4B41-8873-E5198FB577F7"


--Apple-Mail=_4A53FD72-58A0-4B41-8873-E5198FB577F7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8


> Am 26.08.2016 um 00:29 schrieb Rugxulo :
> IrCOve (also) put it here:
>
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/e1000pkt.zip
>
> (If you can think of a better place for it, let me know.)

Thank you. There is of course no better place.

What do you think of M2WAT? I use it quite often. It is Open Source, written
by cordata, a FreeDOS user, in a post to this list. WouldnrCOt it be a good
candidate for the net section of your repo? I know it is a very small
utilityrCa

https://github.com/ulrich-hansen/M2WAT
<https://github.com/ulrich-hansen/M2WAT>

cheers
Ulrich


--Apple-Mail=_4A53FD72-58A0-4B41-8873-E5198FB577F7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8

Am 26.08.2016 um
00:29 schrieb Rugxulo <mailto:rugx...@gmail.com";
class="">rugx...@gmail.com>:IrCOve (also) put it here:http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/e1000pkt.zip";
class="">http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/e1000pkt.zi
(If you can think of a better place for it, let
me know.)Thank you.
There is of course no better place.What do
you think of M2WAT? I use it quite often. It is Open Source, written by
cordata, a FreeDOS user, in a post to this list. WouldnrCOt it be a good
candidate for the net section of your repo? I know it is a very small
utilityrCahttps://github.com/ulrich-hansen/M2WAT";
class="">https://github.com/ulrich-hansen/M2WATcheersUlrich
--Apple-Mail=_4A53FD72-58A0-4B41-8873-E5198FB577F7--


--===2823962537366983409==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--

--===2823962537366983409==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--===2823962537366983409==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99)

---
 * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] M2WAT

[ULRICH HANSEN]

From: Ulrich Hansen 


--===5150565058904733598==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_B8112CCC-E4B4-4DE3-A7F4-7595968965AD"


--Apple-Mail=_B8112CCC-E4B4-4DE3-A7F4-7595968965AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8


> Am 26.08.2016 um 08:28 schrieb Louis Santillan :
>
> Made my own dog food:
>
> <https://github.com/lpsantil/m2wat.bat>

Hi Louis,
Thanks for your work! ItrCOs a nice idea to use a batch file for it. I just
tried it. It works but has some flaws yet. HererCOs the feedback:

1. If I run the program in AUTOEXEC.BAT I get several error messages. See:
https://www.lazybrowndog.net/freedos/files/m2wat.bat.png
<https://www.lazybrowndog.net/freedos/files/m2wat.bat.png>

2. There should be some confirmation like "WATTCP.CFG has been updated".

3. The WATTCP.CFG is written with the values from MTCP.CFG. BUT: WATTCP.CFG is
overwritten.
Only the values from MTCP.CFG are kept.

This can be a problem: WATTCP.CFG can be carefully crafted. Sometimes even
passwords are stored there. It shouldnrCOt be overwritten.

See https://www.lazybrowndog.net/freedos/files/wattcp.cfg
<https://www.lazybrowndog.net/freedos/files/wattcp.cfg> for an example
WATTCP.CFG with lots of settings.

> On Thu, Aug 25, 2016 at 7:33 PM, Rugxulo  wrote:
>>
>> Two minor nitpicks:
>>
>> 1). The .COM isn't even UPX'd. Bloat!  ;-)
>> 2). The source is named "W2WAT.C", which is confusing.
>>
>> Otherwise, seems fine. Should these minor issues be fixed first?

Yes I think these errors have been committed by me. I look into it (and might
need some help with it).
M2WAT.COM <http://m2wat.com/> worked with the example WATTCP.CFG and just
updated the lines that needed it.

Thanks for your help!
cheers
Ulrich





--Apple-Mail=_B8112CCC-E4B4-4DE3-A7F4-7595968965AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8

Am 26.08.2016 um
08:28 schrieb Louis Santillan <mailto:lpsan...@gmail.com";
class="">lpsan...@gmail.com>:Made my own dog food:<https://github.com/lpsantil/m2wat.bat";
class="">https://github.com/lpsantil/m2wat.bat>Hi
Louis,Thanks for your work! ItrCOs a nice idea to use a batch file
for it. I just tried it. It works but has some flaws yet. HererCOs the
feedback:1. If I run the program in
AUTOEXEC.BAT I get several error messages. See:https://www.lazybrowndog.net/freedos/files/m2wat.bat.png";
class="">https://www.lazybrowndog.net/freedos/files/m2wat.bat.png
br class="">2. There should be some confirmation like "WATTCP.CFG
has been updated".3. The WATTCP.CFG is
written with the values from MTCP.CFG. BUT: WATTCP.CFG is
overwritten. Only the values from MTCP.CFG are
kept. This can be a problem: WATTCP.CFG
can be carefully crafted. Sometimes even passwords are stored there. It
shouldnrCOt be overwritten.See https://www.lazybrowndog.net/freedos/files/wattcp.cfg";
class="">https://www.lazybrowndog.net/freedos/files/wattcp.cfg for an
example WATTCP.CFG with lots of settings. On Thu, Aug 25, 2016 at 7:33 PM, Rugxulo
<mailto:rugx...@gmail.com"; class="">rugx...@gmail.com>
wrote:Two minor nitpicks:1). The .COM isn't even UPX'd. Bloat!  ;-)2). The
source is named "W2WAT.C", which is confusing.Otherwise, seems fine. Should these minor issues be fixed first?Yes I
think these errors have been committed by me. I look into it (and might need
some help with it).http://M2WAT.COM";
class="">M2WAT.COM worked with the example WATTCP.CFG and just updated
the lines that needed it.Thanks for your help!cheersUlrich
--Apple-Mail=_B8112CCC-E4B4-4DE3-A7F4-7595968965AD--


--===5150565058904733598==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--

--===5150565058904733598==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--===5150565058904733598==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99)

---
 * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] M2WAT

[ULRICH HANSEN]

From: Ulrich Hansen 



> Am 27.08.2016 um 02:35 schrieb Louis Santillan :
>
> My intention was to
> simply map what is obvious.  If someone has additional config, I'd
> suggest doing something like
>
>   dhcp
>   m2wat
>   type %WATTCP.CFG%\WATPERM.CFG>>%WATTCP.CFG%\WATTCP.CFG

That wouldnrCOt work. For instance for Arachne the WATTCP.CFG could look like
this:

my_ip = 0.0.0.0
netmask = 255.255.255.0
gateway = 0.0.0.0
#
sockdelay=40
hostname=arachne
mss=512

and the nameservers would be configured in ARACHNE.CFG.

Your workaround would configure nameservers in WATTCP.CFG too. But this could
mess things up. It shouldnrCOt configure a nameserver if there is none
configured in WATTCP.CFG.

Unfortunately M2WAT.COM by cordata also does not get this right.

David Dunfields DHCP program from
http://classiccmp.org/dunfield/dos/index.htm

does it correctly. There is even an option /F where you can choose to "fill-in
config items not supplied in original filerCL.

The program is a bit hard to figure out, because the description in DCHP.TXT
is not correct.

Instead of
DHCP P=60 /W='C:\FDOS\WATTCP.CFG'  /M='C:\FDOS\MTCP.CFGrCy
you would need to write:
DHCP P=60 /W C:\FDOS\WATTCP.CFG
DHCP P=60 /M C:\FDOS\MTCP.CFG

(You can not write the /M option and the /W option in the same line.)

It does get the environment variable MTCPCFG from AUTOEXEC.BAT, but it
doesnrCOt get the environment variable WATTCPCFG.

So
DHCP /M
would work, while
DHCP /W
wouldnrCOt.

But anyway you can work around this and the program works fine. Unfortunately
there is no source file on the website and no license, so it couldnrCOt be
bundled with FreeDOS.

cheers
Ulrich
























--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99)

---
 * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Some struggle with SSH2DOS (solved)

[Ulrich Hansen]

From: Ulrich Hansen 


Hi all,

Thanks to Jerome, there is now SSH2DOS in the FreeDOS net repo, which is great!

Unfortunately even this free SSH client is getting a bit rusty, the latest
version is 11 years old.

As I found out, it wouldnrCOt connect to my server (Ubuntu 16.04 LTS).
But it still connected fine to a Debian Wheezy machine.

In the end I found the problem: OpenSSH versions >=6.7 have disabled a
necessary KexAlgorithm and a Cipher.

Here is a report. I also posted it on the SSH2DOS page on SourceForge.

Hope this helps others eventually...
Ulrich



1. The solution:

Add the following lines to /etc/ssh/sshd_config on the server:

Ciphers aes128-cbc
KexAlgorithms diffie-hellman-group-exchange-sha1


2. The problem:

SSH2DOS works fine with a Debian Wheezy machine with OpenSSH 6.0.

But it does not connect to a Debian 8 machine with OpenSSH 6.7.
It also does not connect to a Ubuntu 16.04 server with OpenSSH 7.2.

SSH2DOS gives the following error code:

C:\> ssh2d386 username 192.168.1.136
SSH2DOS v0.2.1. 386+ version
Remote host closed connection
DH key exchange failed
Socket write error. File: transprt.c, line:698
Remote reset connection

On the server /var/log/auth.log says:
Jan 23 00:17:25 debian8 sshd [1883]: fatal: Unable to negotiate a key exchange
method [preauth]

SSH2D386 with the -d option writes the following DEBUG.PKT:


---

RECEIVED packet:
14 63 99 7B 69 DA 8E 90 00 02 0A 69 D1 32 93 26
E1 00 00 00 96 63 75 72 76 65 32 35 35 31 39 2D
73 68 61 32 35 36 40 6C 69 62 73 73 68 2E 6F 72
67 2C 65 63 64 68 2D 73 68 61 32 2D 6E 69 73 74
70 32 35 36 2C 65 63 64 68 2D 73 68 61 32 2D 6E
69 73 74 70 33 38 34 2C 65 63 64 68 2D 73 68 61
32 2D 6E 69 73 74 70 35 32 31 2C 64 69 66 66 69
65 2D 68 65 6C 6C 6D 61 6E 2D 67 72 6F 75 70 2D
65 78 63 68 61 6E 67 65 2D 73 68 61 32 35 36 2C
64 69 66 66 69 65 2D 68 65 6C 6C 6D 61 6E 2D 67
72 6F 75 70 31 34 2D 73 68 61 31 00 00 00 41 73
73 68 2D 72 73 61 2C 72 73 61 2D 73 68 61 32 2D
35 31 32 2C 72 73 61 2D 73 68 61 32 2D 32 35 36
2C 65 63 64 73 61 2D 73 68 61 32 2D 6E 69 73 74
70 32 35 36 2C 73 73 68 2D 65 64 32 35 35 31 39
00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C
79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73
31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63
74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36
2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C
79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73
31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63
74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36
2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
00 00 00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40
6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63
2D 31 32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68
2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32
35 36 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32
2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
2C 68 6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F
70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D
36 34 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75
6D 61 63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E
63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35
36 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C
68 6D 61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61
63 2D 36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68
2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74
6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D
61 63 2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40
6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63
2D 73 68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73
68 61 31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E
63 6F 6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E
73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38
40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61
63 2D 73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D
73 68 61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68
61 31 00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40
6F 70 65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E
6F 6E 65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68
2E 63 6F 6D 00 00 00 00 00 00 00 00 00 00 00 00
00
..c.{i..i.2.&
..curve25519-
sha...@libssh.or
g,ecdh-sha2-nist
p256,ecdh-sha2-n
istp384,ecdh-sha
2-nistp521,diffi
e-hellman-group-
exchange-sha256,
diffie-hellman-g
roup14-sha1...As
sh-rsa,rsa-sha2-
512,rsa-sha2-256
,ecdsa-sha2-nist
p256,ssh-ed25519
lchacha20-pol
y1...@openssh.co
m,aes128-ctr,aes
192-ctr,aes256-c
tr,aes128-gcm@op
enssh.com,aes256
-g...@openssh.com
lchacha20-pol
y1...@openssh.co
m,aes128-ctr,aes
192-ctr,aes256-c
tr,aes128-gcm@op
enssh.com,aes256
-g...@openssh.com
.umac-64-etm@
openssh.com,umac
-128-etm@openssh
..com,hmac-sha2-2
56-etm@openssh.c
om,hmac-sha2-512
-e...@openssh.com
,hmac-sha1-etm@o
penssh.com,umac-
6...@openssh.com,u
mac-128@openssh.
com,hmac

Re: [Freedos-user] SSH2DOS - no connection with recent servers

[Ulrich Hansen]

From: Ulrich Hansen 


Update:

The solution I found last night seems to work only for older OpenSSH servers.

For Ubuntu 16.04 LTS (with OpenSSH 7.2.) I also had to add:

HostKeyAlgorithms ssh-dss

to /etc/ssh/sshd_config because ssh-dss seems to have been deactivated by
default since OpenSSH 6.9.

But in the end SSH2DOS was still not able to connect to OpenSSH 7.2.

Perhaps someone has an idea?

At the moment SSH2DOS can only be used to connect to older servers, running
f.i. Debian Wheezy (OpenSSH 6.0) or Jessie (OpenSSH 6.7).

So soon there will be no functioning SSH client anymore for FreeDOS. :-(

Here are the messages:

SSH2DOS error message is:

C:\> ssh2d386 username 192.168.1.131
SSH2DOS v0.2.1. 386+ version
Expected KEX_DH_GEX_GROUP
DH key exchange failed
Remote host closed connection
Socket write error. File: transprt.c, line:698
Connection closed by peer

On the server, Ubuntu 16.04 LTS (with OpenSSH 7.2.), /var/log/auth.log says:

Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: error: kex protocol error: type
30 seq 1 [preauth]
Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: error: Received disconnect from
192.168.1.110 port 564:3: Expected KEX_DH_GEX_GROUP [preauth]
Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: Disconnected from 192.168.1.110
port 564 [preauth]


C:\> ssh2d386 -d username 192.168.1.131

wrote the following output in C:\SSH2DOS\DEBUG.PKT:

---

RECEIVED packet:
14 BE 6D 01 48 D3 E5 EB 2A C1 81 DE E7 31 AB DB
B2 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C
6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E
67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64
73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63
00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00
00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31
32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36
2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2D 65
74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68
6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F 70 65
6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 36 34
40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61
63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36 2C
68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C 68 6D
61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61 63 2D
36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74 6D 40
6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63
2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73
68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70 65 6E
73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61
31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E 73 73
68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 40 6F
70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D
73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D 73 68
61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68 61 31
00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E 6F 6E
65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 00 00 00 00 00 00 00 00 00 00 00 00 00
...m.H...*1..
."diffie-hell
man-group-exchan
ge-sha1ssh-d
ssaes128-cbc
.aes128-cbc..
...umac-64-etm@op
enssh.com,umac-1
28-etm@openssh.c
om,hmac-sha2-256
-e...@openssh.com
,hmac-sha2-512-e
t...@openssh.com,h
mac-sha1-etm@ope
nssh.com,umac-64
@openssh.com,uma
c-...@openssh.co
m,hmac-sha2-256,
hmac-sha2-512,hm
ac-sha1umac-
64-etm@openssh.c
om,umac-128-etm@
openssh.com,hmac
-sha2-256-etm@op
enssh.com,hmac-s
ha2-512-etm@open
ssh.com,hmac-sha
1-...@openssh.co
m,umac-64@openss
h.com,umac-128@o
penssh.com,hmac-
sha2-256,hmac-sh
a2-512,hmac-sha1
.none,zlib@op
enssh.comnon
e,zlib@openssh.c
om.

SENT packet:
14 25 81 88 A7 CD 90 15 0E 5E 3B 7C B4 0B 1E 9D
CA 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C
6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E
67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64
73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63
00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00
00 09 68 6D 61 63 2D 73 68 61 31 00 00 00 09 68
6D 61 63 2D 73 68 61 31 00 00 00 09 6E 6F 6E 65
2C 7A 6C 69 62 00 00 00 09 6E 6F 6E 65 2C 7A 6C
69 62 00 00 00 00 00 00 00 00 00 00 00 00 00
..%...^;|
."diffie-hell
man-group-exchan
ge-sha1ssh-d
ssaes128-cbc
.aes128-cbc..
...hmac-sha1h
mac-sha1none
,zlibnone,zl
ib.

SENT packet:
1E 00 00 04 00
..

RECEIVED packet:
03 00 00 00 01
..

SENT packet:
03 00 00 00 02
..

SENT packet:
01 00 00 00 03 00 00 00 19 45 78 70 65 63 74 65
64 20 4B 45 58 5F 44 48 5F 47 45 58 5F 47 52 4F
55 50 00 00 00 00
..Expecte
d KEX_DH_GEX_GRO
UP

SENT packet:
62 00 00 00 00 00 00 00 07 70 74 79 2D 72 65 71
01 00 00 00 05 78 74 65 72 6D 00 00 00 50 00 00
00 18 00 00 00 00 00 00 00 00 00 00 00 00
bpty-req
..xterm...P..

Re: [Freedos-user] SSH2DOS - no connection with recent servers

[Ulrich Hansen]

From: Ulrich Hansen 


--===1286602081422601077==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_FB62985E-3376-4E71-8B37-98EBAD86AAFE"


--Apple-Mail=_FB62985E-3376-4E71-8B37-98EBAD86AAFE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8

Wow. I am stunned. This has solved the problem. I have spent more than a day
searching for such a solution.

I am now able to log into a Ubuntu 16.04 LTS server with OpenSSH 7.2
Client is a fresh install of FreeDOS 1.2 where I installed ssh2dos with "FDNPKG
install ssh2dos"

Thank you very, very much!

Ulrich



> Am 27.01.2017 um 06:39 schrieb Dan Schmidt :
>
> I forgot - you may need to regenerate your keys with "ssh-keygen -A" after
modifying the server.
>
> On Thu, Jan 26, 2017 at 10:38 PM, Dan Schmidt mailto:helpdesk...@gmail.com>> wrote:
> I am unsure what it is that makes ssh2dos so unstable for me - nobody else
has this issue?
>
> I would like to answer Ulrich on how he can modify his Ubuntu server, but
first, a warning: These algorithms were disabled because they are obsolete and
insecure.  Using a token based login, such as google-authenticator, may be
advisable if your server is public facing.
>
> Firstly, add this to your server's /etc/ssh/sshd_config:
>
> KexAlgorithms diffie-hellman-group1-sha1,curve25519-sha...@libssh.org
<mailto:curve25519-sha...@libssh.org>,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
> Ciphers 3des-cbc,blowfish-cbc,aes128-cbc,aes128-ctr,aes256-ctr
> HostKeyAlgorithms +ssh-dss
>
> Then, make use of the -g option - it goes BEFORE your username in ssh2dos.
You should now be able to connect.
>
> I do not know why simply adding +diffie-hellman-group1-sha1 doesn't work, it
seems it should.  Also, I was in a rush - I may be excluding some newer options
- report back if you find/add them with success.
>
> -Dan
>
> On Thu, Jan 26, 2017 at 9:42 PM, Karen Lewellen mailto:klewel...@shellworld.net>> wrote:
> Hi Bill,
> While I appreciate your desire for wisdom, I feel rather sure  my specific
situation will not apply to anyone else here most likely.
> I use ssh2d386 to  access at least one commercial shell, but those shell
services are maintained by others.  I am not for example accessing my own
server.
> If the servers you desire reaching are run by other people,  give me an
example and I will try.
> If my many years of computing has taught me anything is that the word
Personal  is important for a reason.
> Kare
>
>
>
> On Thu, 26 Jan 2017, William Dudley wrote:
>
> Karen,
>
> If you know how to get ssh2d386 to connect to a modern openssh, as on
> Ubuntu 16.04,
> please share the recipe with us!
>
> Thanks,
> Bill Dudley
>
>
> This email is free of malware because I run Linux.
>
> On Thu, Jan 26, 2017 at 9:10 PM, Karen Lewellen mailto:klewel...@shellworld.net>>
> wrote:
>
> Well, if you have given up no point in my sharing.
> We use the same edition of Ubuntu, both with dreamhost who has my office,
> and here at shellworld.
> While the latter requires me to make use of a few ssh2021b options, the -g
> option  for example, I encounter no issues.
> I am going to guess that  things like machine speed, mine is a p3 with
> allot of memory, impacts your situation.
> nor, I would hope, your  location in the world.
> Sorry I did not notice your post before you abandoned  the effort.
> Kare
>
>
>
> On Fri, 27 Jan 2017, Ulrich Hansen wrote:
>
>
> Am 26.01.2017 um 18:19 schrieb Karen Lewellen mailto:klewel...@shellworld.net>>:
>
> As I am presently writing this e-mail using ssh2d386 from the ssh2dos
> package ssh2021b,  perhaps I can help you troubleshoot.
>
>
> Hi Karen!
>
> I am using the exact same program and version.
>
> for the record, I am not using freedos, but  the ms dos 7.10 package
> mentioned on this list.
> Still every day several times a day I connect  to two different servers
> using  this package.
>
>
> I guess your servers still run OpenSSH in versions earlier than 6.9.
>
> may I ask again what your issue is presently?
>
>
> Actually I have given up on it. I spent another day trying to get it to
> work, but without success.
>
> The problem is that I canrCOt connect to an Ubuntu 16.04 LTS server with
> OpenSSH 7.2.
>
> SSH2D386 gives the message:
>
> Expected KEX_DH_GEX_GROUP
> DH key exchange failed
>
> The server logs:
> Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol
> error: type 30 seq 1 [preauth]
> Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received
> disconnect from 192.168.1

Re: [Freedos-user] SSH2DOS - no connection with recent servers

[Ulrich Hansen]

From: Ulrich Hansen 



> Am 26.01.2017 um 18:19 schrieb Karen Lewellen :
>
> As I am presently writing this e-mail using ssh2d386 from the ssh2dos
> package ssh2021b,  perhaps I can help you troubleshoot.

Hi Karen!

I am using the exact same program and version.

> for the record, I am not using freedos, but  the ms dos 7.10 package
> mentioned on this list.
> Still every day several times a day I connect  to two different servers
> using  this package.

I guess your servers still run OpenSSH in versions earlier than 6.9.

> may I ask again what your issue is presently?

Actually I have given up on it. I spent another day trying to get it to work,
but without success.

The problem is that I canrCOt connect to an Ubuntu 16.04 LTS server with
OpenSSH 7.2.

SSH2D386 gives the message:

 Expected KEX_DH_GEX_GROUP
 DH key exchange failed

The server logs:
 Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol error:
type 30 seq 1 [preauth]
 Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received disconnect
from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO

As I wrote I already had problems connecting to a Debian 8 server with OpenSSH
6.7.
But there I could fix it with these lines in /etc/ssh/sshd_config on the
server.

 Ciphers aes128-cbc
 KexAlgorithms diffie-hellman-group-exchange-sha1
 MACs hmac-sha1
 HostKeyAlgorithms ssh-css

But in OpenSSH 7.2 this didnrCOt work.

What else did I try?

I tried to set MTU=576 in C:\FDOS\WATTCP.CFG.

I tried to recompile OpenSSH.
The first time with adding this line in in compat.c:
 { "SSHDOS*",   SSH_OLD_DHGEX },
The second time with this one:
 { "SSHDOS*",   SSH_BUG_NOREKEY|SSH_BUG_FIRSTKEX },

Both were not able to let SSH2D386 connect. It worked great with other SSH
clients.

The idea was that SSH2DOS uses code from PuTTY and there were already several
exceptions in combat.c for old PuTTY versions. The reason seems to be that
OpenSSH implemented RFC4419 and old PuTTY versions and SSH2DOS did not. See
[1], [2].

I even looked at the SSH2DOS source code. But I have no experience with
OpenWatcom. I installed it but gave up, when I saw I also had to compile the
WATT32 TCP/IP stack.

SSH2DOS uses PuTTY code, which is also Free Software. So in theory it should be
possible to replace the old PuTTY code with a more recent one.

cheers
Ulrich


[1] https://forums.red-gate.com/viewtopic.php?f=198&t=78958
[2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/rfc4419.html



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS images for VirtualBox

[Ulrich Hansen]

From: Ulrich Hansen 


--===8066260093034722502==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_C66AE06C-D551-4755-886A-D2A39B14C871"


--Apple-Mail=_C66AE06C-D551-4755-886A-D2A39B14C871
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252


> Am 02.02.2017 um 08:57 schrieb Ralf Quint :
> Well,...
>> Not Found
>>

Oh, sorry. I forgot to change one of the two links there. Thanks!! I repaired
it.

> On the side for the version supposedly without network, you are talking an
awful lot about the networking stuff being installed

Hmm. YouAve got a point. The thing is: FTPSRV was for some years the fastest
way of getting files in and out of the FreeDOS guest. So I considered it
something most people would want, also in the anormalo image without additional
networking software.

Now with the VHD image type, you can mount it in your host OS and dragAn drop
files with your Explorer, Nautilus, Finder, whatever. So now in VirtualBox
FreeDOS can be used fine without a network.

So youAre right. But what are you suggesting? Making the FreeDOS1.2 image just
a pure FreeDOS 1.2 version without any changes?




--Apple-Mail=_C66AE06C-D551-4755-886A-D2A39B14C871
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252

Am 02.02.2017 um
08:57 schrieb Ralf Quint <mailto:freedos...@gmail.com";
class="">freedos...@gmail.com>:
Well,...

  Not 
FoundOh, sorry. I forgot 
to change one of the two links there. Thanks!! I repaired it.On the side for the version supposedly without network, 
you are talking an awful lot about the networking stuff being 
installedHmm. YouAve got a point. 
The thing is: FTPSRV was for some years the fastest way of getting files in and 
out of the FreeDOS guest. So I considered it something most people would want, 
also in the anormalo image without additional networking 
software.Now with the VHD image type, you 
can mount it in your host OS and dragAn drop files with your Explorer, 
Nautilus, Finder, whatever. So now in VirtualBox FreeDOS can be used fine 
without a network.So youAre right. But what 
are you
suggesting? Making the FreeDOS1.2 image just a pure FreeDOS 1.2 version without 
any changes?
--Apple-Mail=_C66AE06C-D551-4755-886A-D2A39B14C871--


--===8066260093034722502==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===8066260093034722502==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--===8066260093034722502==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] questions on FreeDOS

[Ulrich Hansen]

From: Ulrich Hansen 


--===4236074997370426021==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_DD3BCAAE-3DDC-4235-9057-DF7D96A882AD"


--Apple-Mail=_DD3BCAAE-3DDC-4235-9057-DF7D96A882AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8


> Am 01.02.2017 um 07:06 schrieb herminio.hernande...@gmail.com:
>
> I launched the VM verifed it has an ip address and I can ping out, but
> my laptop cannot ping FreeDOS. However FreeDOS can ping my laptoprCa

No of course not. ThererCOs no service running that can answer the ping.
You need to start a service that listens to the network. For instance mTCPrCOs
ftpsrv.

You need to configure the network and ftpsrv first. See:

http://wiki.freedos.org/wiki/index.php/VirtualBox_-_Chapter_5
<http://wiki.freedos.org/wiki/index.php/VirtualBox_-_Chapter_5>
and
http://wiki.freedos.org/wiki/index.php/VirtualBox_-_Chapter_7
<http://wiki.freedos.org/wiki/index.php/VirtualBox_-_Chapter_7>

(both pages were updated this morning...)

Good luck!


>
> Herminio
>
> On Tue, 2017-01-31 at 21:08 -0800, Louis Santillan wrote:
>> In VirtualBox, you can start the VM with VNC enabled [0].
>>
>>
>> [0] https://www.virtualbox.org/manual/ch07.html
>>
>> On Tue, Jan 31, 2017 at 8:31 PM,  
>> wrote:
>>> Corbin,
>>>
>>> Thanks that did it!
>>>
>>> Herminio
>>>
>>> On Wed, 2017-02-01 at 03:20 +, Corbin Davenport wrote:
>>>> 1. You can get sound in VirtualBox by changing the VM audio
>>>> device to
>>>> SoundBlaster 16. You can do this by opening the VM settings,
>>>> going to
>>>> sound, and selecting SoundBlaster 16 as the audio controller.
>>>>
>>>> 2. I'm not sure if this is possible, maybe someone else can chime
>>>> in
>>>> about that.
>>>>
>>>> Corbin
>>>>
>>>>
>>>> On Tue, Jan 31, 2017 at 10:15 PM 
>>>> wrote:
>>>>> Hello,
>>>>>
>>>>> I just started tinkering with FreeDOS after listening  to Jim
>>>>> Hall
>>>>> on
>>>>> the Lunduke Hour. I think this project is so cool! I do have
>>>>> some
>>>>> questions.
>>>>>
>>>>> 1. is there any way to have sound working while in Virtualbox?
>>>>>
>>>>> 2. is there a way to set FreeDOS as a VNC, telnet, or even SSH
>>>>> server?
>>>>> I would have a full screen session when playing some of the DOS
>>>>> games.
>>>>>
>>>>> Thanks for you time!
>>>>> Herminio---
>>>>> 
>>>>> ---
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>>>> 
>>>>> ___
>>>>> Freedos-user mailing list
>>>>> Freedos-user@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>>>
>>>>
>>>> --
>>>> Corbin D
>>>>
>>>>
>>>> ---
>>>> 
>>>> ---
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>>> ___
>>>> Freedos-user mailing list
>>>> Freedos-user@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>>
>>>
>>> -
>>> -
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>
>> ---
>> ---
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> ___
>> Freedo

[Freedos-user] FreeDOS 1.2 & VirtualBox: Wiki updated

[Ulrich Hansen]

From: Ulrich Hansen 


--===2810073566745673569==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_174A7072-BFE5-4F39-AF5B-72325F7F4E0A"


--Apple-Mail=_174A7072-BFE5-4F39-AF5B-72325F7F4E0A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8

I have updated the pages at:

http://wiki.freedos.org/wiki/index.php/VirtualBox
<http://wiki.freedos.org/wiki/index.php/VirtualBox>

FreeDOS 1.2, especially the new installer, FDIMPLES and FDNPKG have made many
things easier, especially installing a network. :-)

I also added an explanation how to mount the FreeDOS image in Windows, Mac and
Ubuntu. And thererCOs a page about configuring a VirtualBox network with NAT
and port forwarding.

By the way: Jim Hall has repaired the upload of pictures to the wiki, which was
broken. So if anybody else wants to add knowledge and screenshots and
explanations to the wiki, now is probably a good time to mail Jim for a login
:-)
--Apple-Mail=_174A7072-BFE5-4F39-AF5B-72325F7F4E0A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8

I have updated the
pages at:http://wiki.freedos.org/wiki/index.php/VirtualBox";
class="">http://wiki.freedos.org/wiki/index.php/VirtualBoxFreeDOS 1.2, especially the new
installer, FDIMPLES and FDNPKG have made many things easier, especially
installing a network. :-)I
also added an explanation how to mount the FreeDOS image in Windows, Mac and
Ubuntu. And thererCOs a page about configuring a VirtualBox network with NAT
and port forwarding. By the way: Jim Hall has repaired the upload of pictures to the wiki,
which was broken. So if anybody else wants to add knowledge and screenshots and
explanations to the wiki, now is probably a good time to mail Jim for a login
 :-)
--Apple-Mail=_174A7072-BFE5-4F39-AF5B-72325F7F4E0A--


--===2810073566745673569==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===2810073566745673569==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--===2810073566745673569==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS images for VirtualBox

[Ulrich Hansen]

From: Ulrich Hansen 


--===6012861226599600310==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_D27D0CEF-402E-483B-8C06-876F4F5D24B5"


--Apple-Mail=_D27D0CEF-402E-483B-8C06-876F4F5D24B5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8


>> 2017-02-03 Ralf Quint:
>
>>> Well, that works only with VMware, but unfortunately not with
>>> VirtualBox, AFAIK.
>
>> Right.
>
> As with drivers for other things, it would still be good to
> include vmsmount for those who use vmware to run FreeDOS :-)

Vmware uses vmdk images, my VirtualBox images are VHD. So thatrCOs a whole new
story.

I donrCOt see much use in including vmsmount on VHD image. And I have no
experience with converting everything to VMDK images, how reliable they work
with VirtualBox on Windows, Ubuntu and Mac hosts or how they can be mounted
from the host OS. So that would require some researching and creating and
converting and re-writing.

At the moment I would prefer a separate image for vmware users.

@Eric and @Ralf: About the clean FreeDOS 1.2 VirtualBox image:

I have done it: It is now EXACTLY what you get by installing manually with the
FD12CD.iso and accepting everything. No networking. :-)

See: https://www.lazybrowndog.net/freedos/virtualbox/?page_id=21
<https://www.lazybrowndog.net/freedos/virtualbox/?page_id=21>

cheers
Ulrich
--Apple-Mail=_D27D0CEF-402E-483B-8C06-876F4F5D24B5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8

2017-02-03 Ralf Quint:Well, that works only with VMware, but unfortunately not withVirtualBox, AFAIK.Right.As with drivers for other things, it would still be good toinclude vmsmount for those who use vmware to run FreeDOS :-)Vmware uses vmdk images, my VirtualBox
images are VHD. So thatrCOs a whole new story. I
donrCOt see much use in including vmsmount on VHD image. And I have no
experience with converting everything to VMDK images, how reliable they work
with VirtualBox on Windows, Ubuntu and Mac hosts or how they can be mounted
from the host OS. So that would require some researching and creating and
converting and re-writing. At the moment I would prefer a separate image for vmware users.@Eric and @Ralf: About the clean FreeDOS 1.2 VirtualBox
image:I have done it: It is now EXACTLY what you get
by installing manually with the FD12CD.iso and accepting everything. No
networking. :-)See: https://www.lazybrowndog.net/freedos/virtualbox/?page_id=21";
class="">https://www.lazybrowndog.net/freedos/virtualbox/?page_id=21cheersUlrich
--Apple-Mail=_D27D0CEF-402E-483B-8C06-876F4F5D24B5--


--===6012861226599600310==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===6012861226599600310==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--===6012861226599600310==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

[Ulrich Hansen]

From: Ulrich Hansen 


--===7417113793669517128==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_E891E33A-2D32-4678-A835-C43199D3E41C"


--Apple-Mail=_E891E33A-2D32-4678-A835-C43199D3E41C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8

In FreeDOS 1.1 there was a boot option 4 rCRLoad FreeDOS without driversrCL.
[see picture 1]
It booted a clean system, with SYSTEM and COMMAND and nothing else. [2]

In FreeDOS 1.2 there is a boot option 3 rCRLoad FreeDOS without drivers
(Emergency Mode) [3]
If you choose it, you load FreeDOS with drivers: HIMEMX, FDAPM, CTMOUSE, UDVD2,
SHSUCDXrCa [4]

WouldnrCOt it be better not to load drivers? If people choose not to? ItrCOs
called rCREmergency moderCL after all...

There is also a boot option 4 rCRLoad FreeDOS low with some drivers (Safe
Mode)rCL [5]
But it is not loaded LOW, as promised. In FDCONFIG.SYS you find:
124?DOS=HIGH
rCa
124?DOSDATA=UMB
Isn't this the opposite of low? [6]

Probably thererCOs a quick way to fix the whole thing: Exchange only the titles
of menu options  3 and 4 and delete every 4? in FDCONFIG.SYS except the line
that loads SHELL=C:\FDOS\BIN\COMMAND.COM.  [7]

WouldnrCOt this make more sense? Please correct me if IrCOm wrong.

[1] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers.png
<https://www.lazybrowndog.net/freedos/files/1.1-without-drivers.png>
[2] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers2.png
<https://www.lazybrowndog.net/freedos/files/1.1-without-drivers2.png>
[3] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers.png
<https://www.lazybrowndog.net/freedos/files/1.2-without-drivers.png>
[4] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers2.png
<https://www.lazybrowndog.net/freedos/files/1.2-without-drivers2.png>
[5] https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers.png
<https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers.png>
[6] https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers2.png
<https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers2.png>

[7] New FDCONFIG.SYS:

SET DOSDIR=C:\FDOS

!COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS
!LASTDRIVE=Z
!BUFFERS=20
!FILES=40
!MENUCOLOR=7,0

MENUDEFAULT=2,5
MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free
MENU 2 - Load FreeDOS with EMM386 (Expanded Memory) and SHARE loaded
MENU 3 - Load FreeDOS low with some drivers (Safe Mode)
MENU 4 - Load FreeDOS without drivers (Emergency Mode)

12?DOS=HIGH
12?DOS=UMB
12?DOSDATA=UMB
1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
23?DEVICE=C:\FDOS\BIN\HIMEMX.EXE
2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG
34?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT
12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT



--Apple-Mail=_E891E33A-2D32-4678-A835-C43199D3E41C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8

In FreeDOS 1.1 there
was a boot option 4 rCRLoad FreeDOS without driversrCL. [see picture 1]It booted a clean system, with SYSTEM and COMMAND and nothing else.
[2]In FreeDOS 1.2 there is
a boot option 3 rCRLoad FreeDOS without drivers (Emergency Mode) [3]If you choose it, you load FreeDOS with drivers: HIMEMX, FDAPM,
CTMOUSE, UDVD2, SHSUCDXrCa [4]WouldnrCOt it be better not to load drivers? If people choose not to?
ItrCOs called rCREmergency moderCL after all...There is also a boot option 4 rCRLoad FreeDOS low
with some drivers (Safe Mode)rCL [5]But it is not loaded
LOW, as promised. In FDCONFIG.SYS you find:124?DOS=HIGHrCa124?DOSDATA=UMBIsn't this the opposite of low?
[6] Probably
thererCOs a quick way to fix the whole thing: Exchange only the titles of menu
options  3 and 4 and delete every 4? in FDCONFIG.SYS except the line that
loads SHELL=C:\FDOS\BIN\http://command.com"; class="">COMMAND.COM.
 [7] WouldnrCOt
this make more sense? Please correct me if IrCOm wrong.[1] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers.png";
class="">https://www.lazybrowndog.net/freedos/files/1.1-without-drivers.png[2] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers2.png"; 
class="">https://www.lazybrowndog.net/freedos/files/1.1-without-drivers2.png[3] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers.png"; 
class="">https://www.lazybrowndog.net/freedos/files/1.2-without-drivers.png[4] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers2.png"; 
class="">https://www.lazybrowndog.net/freedos/files/1.2-without-drivers2.png[5] https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers.png"; 
class="">https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers.png[6] https://www.lazybrowndog.net/freedos/files/1.2-with-s

Re: [Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

[Ulrich Hansen]

From: Ulrich Hansen 


--===7381254713677974754==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_F6D80F5B-4C1C-4E48-8341-93D55F699976"


--Apple-Mail=_F6D80F5B-4C1C-4E48-8341-93D55F699976
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8


> Am 08.02.2017 um 22:46 schrieb Jerome Shidel mailto:jer...@shidel.net>>:
>
> Bug? Not really.
> Is it correct? Not even close.

Then lets correct it. :-) ItrCOs pretty easy, as I showed in my last mail.

> Also, #2 should not say EMM386 when it uses JEMM386.

ThatrCOs even easier. :-)

> The current 1.2 config files are based on a clean install of 1.1 into VMware
Fusion. Then a some things were added, moved, changed and removed.

Yes, the following line (which skipped all the drivers)

if "%config%rCL=="4" GOTO END

was left in AUTOEXEC.BAT although the "no driversrCL option was changed to
config 3 in FDCONFIG.SYS. That may have been the root of all evilrCa

At the moment both options are doing the opposite of what they say they do.
Instead of loading DOS low with some drivers, option 4 loads DOS high with no
drivers. Nobody complained about that, so here is another suggestion:

How about DROPPING option 4 (SOME DRIVERS) completely? Was it ever useful?
People can always hit F8 for singlestepping...

I suggest to keep the NO DRIVERS option though, which should be exactly that:
No drivers, no memory managers, DOS not loaded high.

Dropping option 4 and keeping a clean option3 would mean deleting everything
with a 4 in FDCONFIG.SYS and removing the 3 from the HIMEMX line. And changing
the line in AUTOEXEC.BAT to

if "%config%rCL=="3" GOTO END

If this is too radical, see the suggestion in my last mail...

Ulrich
--Apple-Mail=_F6D80F5B-4C1C-4E48-8341-93D55F699976
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8

Am 08.02.2017 um 22:46 schrieb Jerome
Shidel <mailto:jer...@shidel.net";
class="">jer...@shidel.net>:Bug? Not
really.Is it correct? Not even close.Then lets correct it. :-) ItrCOs pretty easy, as I showed in my last
mail. Also, #2
should not say EMM386 when it uses JEMM386. ThatrCOs even easier. :-)The current 1.2 config files are based on a clean install
of 1.1 into VMware Fusion. Then a some things were added, moved, changed and
removed.Yes, the following line (which
skipped all the drivers)if "%config%rCL=="4" GOTO
ENDwas left in AUTOEXEC.BAT although the "no
driversrCL option was changed to config 3 in FDCONFIG.SYS. That may have been
the root of all evilrCaAt the moment both options are
doing the opposite of what they say they do. Instead of loading DOS low with
some drivers, option 4 loads DOS high with no drivers. Nobody complained about
that, so here is another suggestion: How about
DROPPING option 4 (SOME DRIVERS) completely? Was it ever useful? People can
always hit F8 for singlestepping...I suggest to keep
the NO DRIVERS option though, which should be exactly that: No drivers, no
memory managers, DOS not loaded high.Dropping option
4 and keeping a clean option3 would mean deleting everything with a 4 in
FDCONFIG.SYS and removing the 3 from the HIMEMX line. And changing the line in
AUTOEXEC.BAT to if "%config%rCL=="3" GOTO
ENDIf this is too radical,
see the suggestion in my last mail...Ulrich
--Apple-Mail=_F6D80F5B-4C1C-4E48-8341-93D55F699976--


--===7381254713677974754==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===7381254713677974754==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--===7381254713677974754==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] SSH2DOS - no connection with recent servers

[Ulrich Hansen]

From: Ulrich Hansen 


--===0481829807500901100==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36"


--Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8


> Am 13.02.2017 um 06:19 schrieb Dan Schmidt mailto:helpdesk...@gmail.com>>:
>
> I hope I am not committing the dreaded "forum necromancyrCL

I had to look that uprCa I really liked the picture of the ghoul in the first
google result :-))

> but I thought I might document that the 386 version, combined with the
mentioned "reset" trick, has solved my issues with ssh2dos stability, thank you
for the idea.

Congratulation! But as I see it, it was your idea all along.
>
> Also, quick type-o - "I am not sure why you would want to run SSH in DOS in
VirtualBox"  I did not mean to imply that running Dos on VirtualBox is at all
strange.

WellrCa It kind of IS strange. ;-) The reason is simple: I have a bit time to
kill at the moment, so I was taking another look at my
VirtualBox/FreeDOS/Networking images I started a few years ago at
https://www.lazybrowndog.net/freedos/virtualbox/
<https://www.lazybrowndog.net/freedos/virtualbox/>. I updated them to FreeDOS
1.2 and was checking if everything still works as expected. And well, SSH2DOS
wasnrCOt and I was unable to find a fix. So thank you again for your help!

At the moment IrCOm updating the MS Client pages (sigh).



> Am 13.02.2017 um 06:19 schrieb Dan Schmidt :
>
> I hope I am not committing the dreaded "forum necromancy" but I thought I
might document that the 386 version, combined with the mentioned "reset" trick,
has solved my issues with ssh2dos stability, thank you for the idea.
>
> Also, quick type-o - "I am not sure why you would want to run SSH in DOS in
VirtualBox"  I did not mean to imply that running Dos on VirtualBox is at all
strange.
>
> On Mon, Jan 30, 2017 at 9:35 PM, Dan Schmidt mailto:helpdesk...@gmail.com>> wrote:
> I didn't try the 386 version, perhaps that will be more stable.  Also, if you
type "reset" before exiting, you can avoid "missing dos screen."  (IE - the
crash every time I exited)
>
> Ulrich, my friend, I am not sure why you would want to run DOS in VIrtualBox
on a MacBookPro, but I am glad I could help you.  :-)  Years ago, several other
technicians laughed at me when I bought an old Pentium for $5 saying"You can't
do anything with that!" FreeDos helped me prove them wrong.
>
> On Sat, Jan 28, 2017 at 8:02 AM, Ulrich Hansen mailto:my.gr...@mailbox.org>> wrote:
>
>> Am 28.01.2017 um 06:23 schrieb Karen Lewellen mailto:klewel...@shellworld.net>>:
>>
>> To answer your question for myself, I never have this issue.  No crashes,
and i  can spend hours working on line.  Further I have done more than my share
of downloads with sftpd386 as well.
>
>
>> On Fri, 27 Jan 2017, Dan Schmidt wrote:
>>>
>>> My ssh2dos is very unstable - it usually crashes on exit or after five to
>>> ten minutes.  Do you have this issue as well?  I am curious if I should try
>>> a different version of DOS.
>
>
>
> I made the same experience as Karen: I had SSH2D386 running more or less the
whole morning while logged into the server. I even ran rCRtoprCL for over an
hour to test the program. No crashes, no sudden exits.
>
> Other experiences:
>
> - As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does
use the hostrCOs CPU by 100 percent. I limit the CPU execution cap in the
VirtualBox settings to 40%, but the fan of my MacBookPro is still running
constantly (but on a lower level than at 100%).
>
> - After logging into the server, I run the command "export LANG=CrCL first.
Otherwise rCRgraphicalrCL console programs like midnight commander or
dpkg-reconfigure will show wrong characters in SSH2DOS.
>
> So far so good. Thanks to you everything is working well now.
>
> Ulrich
>
>
> .
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
<http://sdm.link/slashdot>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net <mailto:Freedos-user@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/freedos-user
<https://lists.sourceforge.net/lists/listinfo/freedos-user>
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tec

Re: [Freedos-user] WIFI on DOS (was: bsum - compute BSD checksumsof yo

[Ulrich Hansen]

From: Ulrich Hansen 


--===7907458448220515418==
Content-Type: multipart/alternative;
boundary=Apple-Mail-D1E116D4-F5D2-4F31-A6E9-29483B8E1920
Content-Transfer-Encoding: 7bit


--Apple-Mail-D1E116D4-F5D2-4F31-A6E9-29483B8E1920
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Several years ago I wrote everything I could find out about DOS and Wifi here:

http://wiki.freedos.org/wiki/index.php/WiFi

If anybody finds out more about it, please give some feedback...


> On Wed, 19 Apr 2017 15:07:35 -0400 dmccunney 
> writes:
>> On Wed, Apr 19, 2017 at 11:14 AM, Dale E Sterner
>>  wrote:
>>> I see that someone on Ebay is selling an HP mini
>>> with a FREEDOS os installed. All the HP minis that
>>> I've seen have wifi & bluetooth built in. That would
>>> mean an 802.11 client to do it. The ad doesn't
>>> mention wifi or bluetooth but every mini that I've seen
>>> has it.
>>
>> The machine may have the *hardware*.  Whether the hardware will be
>> *usable* will depend on software.
>>
>> MSDOS was written back before Wifi and Bluetooth *existed*.  FreeDOS
>> tries to be compatible with MSDOS, which means "support for what
>> existed when MSDOS was current."
>>
>> I would *not* expect Wifi or Bluetooth to be usable on the machine
>> in
>> FreeDOS, because the drivers don't exist.  If you want to use Wifi
>> or
>> Bluetooth on that hardware, you'll need to install another OS that
>> supports them.  (Depending on exactly which HP mini model it is,
>> there
>> might be a flavor of Linux that can do it.)
>> __
>> Dennis
>>
>>
> -
> -
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>
>
> **>>>>
>> From Dale Sterner - MS organic chemistry
> http://pubs.acs.org/doi/abs/10.1021/jo00975a052
> ***>>>>
>
> 
> The Easiest Way To Shed Deep Fat?
> 3 Harmful Foods
> http://thirdpartyoffers.juno.com/TGL3141/58f7bb5e84cae3b5e7b11st02duc
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user

--Apple-Mail-D1E116D4-F5D2-4F31-A6E9-29483B8E1920
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

Several years ago I
wrote everything I could find out about DOS and Wifi
here:http://wiki.freedos.org/wiki/index.php/WiFi";>http://wiki.freedos.org/wiki/index.php/WiFiIf
 anybody finds out more about it, please give some 
feedback...On Wed, 19 Apr 2017 15:07:35 -0400 
dmccunney <mailto:dennis.mccun...@gmail.com";>dennis.mccun...@gmail.com>writes:On Wed, Apr 19, 2017 at 11:14 AM, Dale E Sterner 
<mailto:sunbeam...@juno.com";>sunbeam...@juno.com> 
wrote:I see that someone on Ebay is selling an HP 
miniwith a FREEDOS os installed. All the HP minis 
thatI've seen have wifi & bluetooth built in. 
That wouldmean an 802.11 client to do it. The 
ad doesn'tmention wifi or bluetooth but every 
mini that I've seenhas 
it.The 
machine may have the *hardware*.  Whether the hardware will 
be*usable* will depend on 
software.MSDOS 
was written back before Wifi and Bluetooth *existed*. 
 FreeDOStries to be c
ompatible with MSDOS, which means "support for 
whatexisted when MSDOS 
was current."I would 
*not* expect Wifi or Bluetooth to be usable on the machine 
inFreeDOS, because the drivers don't exist.  If you want 
to use Wifi orBluetooth on that hardware, you'll need to install another OS 
thatsupports them. 
 (Depending on exactly which HP mini model it is, 
theremight be a flavor of Linux that can do 
it.)
__Dennis--Check out the vibrant tech community on one of the world's 
mostengaging tech sites, 
http://Slashdot.org";>Slashdot.org! http://sdm.link/slashdot";>http://sdm.link/sl

Re: [Freedos-user] WIFI on DOS (was: bsum - compute BSD checksumsof yo

[Ulrich Hansen]

From: Ulrich Hansen 


> Am 24.04.2017 um 07:07 schrieb Dan Schmidt :
>
> Is this thread still about wireless for Dos?  If not, sorry for posting.
>
> If so, I bought a wireless to ethernet bridge - smaller than a deck of cards,
runs on usb power - works great for my Dos machine.  I tried a wifi card that
supposedly supported dos - never could get it working, threw it away in
disgust.

This sounds interesting. Is it something like this?
https://www.amazon.com/dp/B00TQEX8BO/ref=psdc_300189_t2_B00HZWOQZ6
Thanks for the hint.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] network and usb floppy access on mac [was: Dhcp]

[Ulrich Hansen]

Am 12.01.2011 23:48, schrieb Rugxulo:

> I do know that VirtualBox has some issues with DOS (e.g. no SB
> support), so normally I don't use DOS there. Not sure if they fixed
> some of them (EMM386 conflict) though one of the recent ones claims
> to. Probably unchecking VT-X in the config helps but is slower.

Yes, Virtualbox 3.2.6 did crash if an Expanded Memory Manager was 
loaded. I wrote a bug report about that last summer [1].

Today I had time to try FreeDOS with the new Virtualbox 4.0.0 and the 
bug is FIXED.

So this is good news! :-)

I just played around with the installation I did last summer and 
networking seems to work fine from within Virtualbox. At least ping 
and surfing with Arachne worked.

The packet driver needed for Virtualbox is pcntpk.com from the package 
amdpd.zip [2].

For file exchange with my host system (Ubuntu 10.04) I run the FTP 
server ftpsrv32 from the watt32 suite [3] in the Freedos guest and 
connect from my host with Filezilla. Of course you can also use 
MS-Client, but most times I am too lazy to do that.

The new ftpsrv app from mTCP works, but at least on my system seems to 
have problems with showing correct DOS paths. For instance it shows 
c:\ as "c:/\". So f.i. creating new directories in filezilla doesn't 
work without manual correction.

regards
Uli


[1] http://www.virtualbox.org/ticket/3365
[2] http://www.crynwr.com/drivers/amdpd.zip
[3] http://www.filegate.net/utiln/utilnet/wt32apps.zip

--
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] network and usb floppy access on mac [was: Dhcp]

[Ulrich Hansen]

Am 15.01.2011 18:10, schrieb Michael B. Brutman:
> On 1/15/2011 10:23 AM, Ulrich Hansen wrote:
>> The new ftpsrv app from mTCP works, but at least on my system seems to
>> have problems with showing correct DOS paths. For instance it shows
>> c:\ as "c:/\". So f.i. creating new directories in filezilla doesn't
>> work without manual correction.

> That's a Filezilla thing - Filezilla is too 'smart' to honor what my
> server is returning for the current working directory, and it's trying
> to fix the directory delimiters.

Unfortunately mTCP ftpsrv doesn't seem to work correctly with any 
graphical FTP clients I tried.

In Filezilla file uploads are answered with a Error 550 Bad path.

The FireFTP plugin for Firefox connects with the same error message:
"550 "/C:": Bad path"
And when I try to upload a file I also get the 550 message.

gFTP didn't give me any directory listings at all.

Anyway, it is really great to have a new FTP-Server for DOS to 
experiment with. I already tried ftpsrv32, NOS/EZ-NOS, quikserv, 
Sockets ftpd and SwsSock ftpd and didn't really expect to see another 
one. :-) Thanks!

regards
Uli

--
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Full Networked FreeDOS image for VirtualBox

[Ulrich Hansen]

Hi list!

I have built a special FreeDOS 1.0 image for Virtualbox:

Networking should be much easier with this image. The appropriate 
packet driver for Virtualbox is already loaded at boot. So file 
exchange between host and client over the network shouldn't be a 
problem any more.

The image and an installation walkthrough can be found at:



Please feel free to download and play with it!

It would be great to get some feedback. Please send improvements. IMHO 
the memory management could be better, especially with MS Client loaded.

Thanks! Happy hacking ;-)
Ulrich

--
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] mTCP 2011-05-20 Version

[Ulrich Hansen]

Hi Michael,

thanks a lot! I tried the ftpsrv app with Filezilla and it works much 
better now (I missed the update before, so maybe this is not really 
news).

Directory browsing with Filezilla as FTP client and mTCP ftpsrv as 
server seems to be no problem anymore. Thanks!

And I especially like the precise logging of events to the screen of 
the DOS machine. I miss this in WATT32 ftpsrv32.

Unfortunately there still seem to be some issues of mTCP ftpsrv with 
Filezilla:

1. When I try to copy a file with a long filename in Filezilla to the 
FreeDOS machine mTCP ftpsrv will not store it. Instead it responds 
with "550 Bad path". Filezilla translates this to "Critical error". In 
comparison, WATT32 ftpsrv32 stores it anyway and lets FreeDOS cut the 
name.

2. Another behaviour I saw: Successfully copied files are sometimes 
not listed automatically in the right window with the files on the 
server in Filezilla. So sometimes I have to push the refresh button.

3. Filezilla seems to show a random date of the files I copied to the 
server (neither the original date nor the actual one). If I stop the 
server and check them in FreeDOS the copied files have the actual date.

4. If I try to copy a file that already exists on the server, ftpsrv 
responds with "553 File exists already" which causes Filezilla to stop 
the transfer and say "Critical error". By default Filezilla should 
open its dialogue window which asks if I want to overwrite, rename or 
keep the duplicate on the server.

Sorry to report this. Most of these bugs may relate more to Filezilla 
than to your FTP server. I work with Filezilla 3.3.1 in Ubuntu 10.04 
LTS and use freedos in Virtualbox.

BTW I have updated the mtcp files in the virtualbox image at
http://lazybrowndog.net/freedos/virtualbox/

:-)

thanks again, regards
Ulrich Hansen




--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] mTCP source code released

[Ulrich Hansen]

Wow! Great news. Thanks a lot!

Am 27.05.2011 23:49, schrieb Michael B. Brutman:
>
> I released mTCP as open source today: http://code.google.com/p/mtcp/
>
>
> Enjoy!
> Mike

--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] mTCP 2011-05-20 Version

[Ulrich Hansen]

HI Michael,

thanks a lot for the detailed answer!

>> 1. When I try to copy a file with a long filename in Filezilla to the
>> FreeDOS machine mTCP ftpsrv will not store it. Instead it responds
>> with "550 Bad path". Filezilla translates this to "Critical error". In
>> comparison, WATT32 ftpsrv32 stores it anyway and lets FreeDOS cut the
>> name.
>
> I aggressively parse the file and path to ensure that they are valid
> and are not going to cause buffer overruns. I'm kind of paranoid about
> buffer overruns, especially since so many versions of DOS can be used.
> (I've tested on everything from PC 2.1 up to DOSBox's emulation of
> DOS.) I could truncate the requested filename, but I think that
> returning the error is the more proper thing to do.

I think users will like that your server takes good care of the data 
and doesn't loose or damage them. This is an important thing. On the 
other hand, most people will connect to the FTP server from more 
popular operating systems than DOS. So it is likely they use long 
filenames. A server that gives them the option to automatically 
truncate the filenames to 8.3 would spare them the work of renaming 
the files by hand.
>
>> 2. Another behaviour I saw: Successfully copied files are sometimes
>> not listed automatically in the right window with the files on the
>> server in Filezilla. So sometimes I have to push the refresh button.
>
> A comparison of the trace from an FTP server that works and mTCP would
> tell me what is going wrong.

I will try to do that, when I am back home. For the next week I am 
working in a different city (Dresden).
>
>> 3. Filezilla seems to show a random date of the files I copied to the
>> server (neither the original date nor the actual one). If I stop the
>> server and check them in FreeDOS the copied files have the actual date.
>
> This probably requires a trace too, although it pleases me greatly
> that the file timestamps are correct. Have you tried using another FTP
> client to "peek in" while FTPSRV and Filezilla are still active?

I will also do that.

>> 4. If I try to copy a file that already exists on the server, ftpsrv
>> responds with "553 File exists already" which causes Filezilla to stop
>> the transfer and say "Critical error". By default Filezilla should
>> open its dialogue window which asks if I want to overwrite, rename or
>> keep the duplicate on the server.
>
> Well, the file does exist. The proper action is to delete the file on
> the server first, and then start again. I could be wrong but if the
> ftpserver just clobbered files (overwrite) without complaining that
> would lead to more problems with partial files overlaying good ones.

Normally there is a Filezilla dialog box, that deals with the problem. 
As I understand it, the solution works like this: When a file already 
exists on the server, Filezilla should get a notification about that 
("File exists already"), open that box and then either abort the 
upload, rename the file or order the ftpserver to replace the file.

>> BTW I have updated the mtcp files in the virtualbox image at
>> http://lazybrowndog.net/freedos/virtualbox/
>>
> Thanks! I refer people to that fairly often - it is a good FreeDOS and
> networking sampler.

Yes, I put a lot of effort in it. It should people help to try out DOS 
networking without having too much work with it.

Now that mTCP is Free Software, I think the next version of FreeDOS 
should focus on getting basic networking abilities.

kind regards
Ulrich Hansen


--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Basic networking abilities

[Ulrich Hansen]

Am 01.06.2011 04:49, schrieb Michael B. Brutman:
> On 5/31/2011 2:23 AM, Marcos Favero Florence de Barros wrote:
>> Hi Ulrich, Michael, others,
>>> Now that mTCP is Free Software, I think the next version of
>>> FreeDOS should focus on getting basic networking abilities.
>> That's wonderful news :-)

Actually this is not really news but just a wish from my side. The 
discussion what*s part of FreeDOS 1.1 takes place since some time at 
freedos-devel. I think the developers decide, while we users should 
publish our expectations and wishes.

So I really hope with the release of mTCP as Free Software, mTCP will 
become part of FreeDOS 1.1 as it has been already discussed in 
freedos-devel.

>> Are you also contemplating networks for sharing files, i.e., a client-
>> server scheme on which a database could operate? (I use DataPerfect.)

> There are a lot of possibilities.  I had some ideas for a TSR that would
> present a new DOS drive letter and use a machine elsewhere on the
> network to provide the actual storage, either in the form of a virtual
> hard drive or through SMB.  It would use the DOS network redirector
> interface which is not documented by Microsoft, but there are some books
> and sample code around.  But that code is quite a bit different in
> nature than any of the mTCP code that I have written, so it has not been
> started yet.

Many FreeDOS users (and projects like network bootdisk) still rely on 
MS Client, which is unfree. If such a mTCP TSR could help us to get 
rid of this necessity, this would be great. Such a software would 
adress a real need of users. And it would also be a progress for 
FreeDOS, just like the MS Workgroup Add-on for DOS has been for MS DOS 
5.0.

BTW: As a user I find your choice of the GPL as license great. I think 
everybody has learned the last years that GPL software can be used 
without any second thoughts and distributed freely. And the software 
will always be open for development, it will never vanish, just 
because its author has lost interest or has other reasons to stop his 
work. That's fine for those who want to use the software.

I am also a real fan of the Free Software idea. Otherwise I wouldn't 
use FreeDOS (which is released under the GPL as well). Some developers 
may not be too happy about the license choice, especially those who 
would like to grab your code and try to make money from it by making 
it part of an unfree software. But who cares about them? I think the 
GPL is about having fun, about trust and fairness and about learning 
from others and alllowing others to participate. So this is great for 
a software project like the one you are just about to start.

That's just my opinion.
regards
Ulrich Hansen

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Why I use FreeDOS

[Ulrich Hansen]

Am 06.06.2011 01:24, schrieb David C. Kerber:

>> On Sun, Jun 5, 2011 at 3:15 PM, Mike Eriksen
 Neither XP nor "light" Linuxes typically run well (if at
>> all) in even
 128 MB of RAM, so saying 20 years is a bit of an
>> exaggeration, even

 > I ran my home web server with debian Lenny in 128MB for a long 
time.  Once I added Tomcat and an e-mail server, I had to add more 
ram, but for just http serving, 128MB was fine.

Hmm. I confess, I run my home webserver with Debian GNU/Linux 4 (Etch) 
and 20 MB Ram and a 486SX which is 18 years old.  Check it at: 


As long as you don't run X and you do build an own small kernel, the 
OS, Apache 2   and some services like smb and ssh work fine on such an 
old plastic brick. As the install process is really slow, I normally 
install Linux by plugging the harddisk into another machine, install 
the OS there, compile the kernel and put it back into the old machine. 
It still takes some time (and some tricks) to do it.

Of course FreeDOS works great on the machine too (and is much! faster 
up and running). I am using it for occasional maintenance of the 
server and, of course, for fun.






--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Packet Driver

[Ulrich Hansen]

Am 18.07.2011 22:54, schrieb Bernd Blaauw:

> The DRDOS website has some networking info at:
> http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Network

We also have something about DOS WiFi in our Wiki:


I never heard that anyone had a WiFi adapter working in DOS that was 
faster than 11 Mbps (802.11b), sorry. But of course feel free to prove 
it wrong.

I think the easiest way would be to use a wired network adapter or 
indeed install FreeDOS in a virtual machine as Cordata suggested (if 
your computer is powerful enough).

Have fun!
Uli

--
Storage Efficiency Calculator
This modeling tool is based on patent-pending intellectual property that
has been used successfully in hundreds of IBM storage optimization engage-
ments, worldwide.  Store less, Store more with what you own, Move data to 
the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FD 1.0 installation... very instable?

[Ulrich Hansen]

Am 02.08.11 04:08, schrieb e.a...@jpberlin.de:

>> - network
>> its a 3c905b. It should work using the NDIS driver included with
>
> That 3com series sounds classic, so I assume there will be a
> direct packet driver on crynwr which does not need NDIS/ODI.

Found a packet driver for the 3c905b-c family. Perhaps you like to try it?

See: http://lazybrowndog.net/3c90xpd


--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Connectivity (ethernet card drivers)

[Ulrich Hansen]

Am 14.08.11 21:43, schrieb julio cortese:
> You understood well, but i already have some drivers for the ethernet card,
> and the question is: as they are for win32 will they work on freedos? what
> kind of extension do they should have and, how do i install a driver?.

Okay, you have a Atheros L2 nic. Congrats!
Thanks to the great guys at  we have a 
working NDIS driver for that. I already extracted it for you to this 
place: 

So please download the driver. We will make it act like a packet 
driver in FreeDOS.

If you like to understand what you are doing, please read my 
description of how to get NDIS drivers to work with DOS at:



In short just follow these instructions:

1. Make a directory C:\NET

2. Copy the downloaded file L2.DOS into C:\NET

3. Get the first disk of the free MS Client from Microsoft:
ftp://ftp.microsoft.com/bussys/Clients/MSCLIENT/DSK3-1.EXE

4. Save the file DSK3-1.exe to an empty directory for instance: C:\TEST

5. Run DSK3-1.exe. It will unzip all the files into the empty folder 
C:\TEST.

6. Two of the files needed are still compressed. Uncompress them by 
running these two commands inside C:\TEST:

expand -r protman.do_
expand -r protman.ex_

7. Copy the three files protman.dos, protman.exe and netbind.com from 
C:\TEST to C:\NET. Afterwards you may delete C:\TEST.

8. Create a file with the name PROTOCOL.INI inside the C:\NET 
directory. Edit it and fill in the following lines:

[protman]
DriverName=PROTMAN$

[ATL2]
DriverName=ATL2$

[PKTDRV]
drivername=PKTDRV$
bindings=ATL2
intvec=0x60
chainvec=0x68

9. Add these lines to the end of your fdconfig.sys:

DEVICEHIGH=C:\NET\PROTMAN.DOS /I:C:\NET
DEVICEHIGH=C:\NET\L2.DOS
DEVICEHIGH=C:\FDOS\BIN\DIS_PKT.DOS

10. Add this line to your autoexec.bat:

C:\NET\NETBIND.COM

11. Reboot. You should now have a working packet driver for your nic.


Ulrich

PS: Loading the above ndis/packet driver shim consumes of course more 
memory than a native packet driver. Unfortunately I couldn't find such 
a native packet driver for the Atheros L2. You might want to search 
yourself to be sure.





--
FREE DOWNLOAD - uberSVN with Social Coding for Subversion.
Subversion made easy with a complete admin console. Easy 
to use, easy to manage, easy to install, easy to extend. 
Get a Free download of the new open ALM Subversion platform now.
http://p.sf.net/sfu/wandisco-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Ulrich Hansen]

Hi Michael!

I played around with Filezilla and Cyberduck on my Mac. Everything 
seems to work OK for me. That's really great! Made some test 
directories and browsed through them. I forgot that DOS directory 
names are limited to 8 letters, got a "550 Bad path" and nearly blamed 
you for it ;-)

I also tried Datalight sockets on FreeDOS (Virtualbox) which seem to 
work OK too - but it was just a short login and I am not really 
familiar with the client.

A DOS client that connected but was unable to browse was Minuet. I 
have placed the screenshot of the error message here:


ftp://96.42.66.188:2021/INCOMING/TEST/TEST1/TEST11/TEST112/TEST1122

:-)

Google Chrome v14 (Mac) seems to be unable to open the ftp adress 
above, while Firefox 7 (Mac) and 6.02 (Ubuntu 11.04) didn't have a 
problem.

Your site also worked OK with AndFTP on my crappy Sony Ericsson Xperia 
with Android 2.1. I switched to the directory above and downloaded the 
image.

All in all it was a lot of fun.
Thanks.
Ulrich




Am 29.09.11 21:14, schrieb Michael B. Brutman:
>
> Alex,
>
> Interesting bug.  I thought that this would be an easy catch, but it is
> more subtle than I thought.  I can't recreate it here.
>
> Your client sends a PASV command before attempting to put the file,
> which is the correct behavior.  Under normal circumstances that just
> tells the server to start listening on port for an incoming connection
> from your client.  If a PORT command or another PASV command is issued
> that listening socket gets tossed away.
>
> In this case it is behaving like your client actually started connecting
> on that socket, or even connected.  So there is an open data connection
> but no data flowing.  And the next command (the dir or ls) requires a
> data connection, but it can't just blast the existing one.  Hence the
> error message.
>
> I'm not sure what's going on, but I suspect that after about 10 seconds
> it would go away if it was just a connection that was starting.  At
> worst case that session is hosed up until that user logs out.
>
> I'm going to keep looking at it, but it's not obvious.  It's also
> probably been in the code since day one - you just got lucky enough to
> hit it.
>
>
> Mike
>
>
> On 9/29/2011 9:20 AM, Single Stage to Orbit wrote:
>> On Thu, 2011-09-29 at 08:37 -0500, Michael B. Brutman wrote:
>>> I have made a large round of improvements to the FTP server in mTCP and
>>> I am looking for a little testing help with it.  If you have a few spare
>>> moments over the next day or two just try to connect to it and browse
>>> the file structure.  Using a few different clients will help me shake
>>> out any new bugs.  Upload some relevant files if you are adventurous.
>> Uploads to incoming doesn't quite work for me. Here's the transcript of
>> my session:
>>
>> $ ftp -n -p 96.42.66.188 2021
>> Connected to 96.42.66.188 (96.42.66.188).
>> 220 mTCP FTP Server
>> ftp>   user anonymous
>> 331 Anonymous ok, send your email addr as the password
>> Password:
>> 230-Welcome to Mike's PCjr running the mTCP FTP server!  This machine
>> 230-was released by IBM in 1983 and features a 4.77Mhz Nec V20 CPU (an
>> 230-upgrade from the standard 8088), an XT-IDE modified for the PCjr, a
>> 230-Western Digital 8003 Ethernet card, and a 20GB Maxtor hard drive.
>> 230-It is running DOS 3.3 so most of the hard drive is not being used.
>> 230-Please poke around, test things out, report any problems you might
>> 230-have, and enjoy!  Incoming files may be deposited at /incoming, and
>> 230-you can create subdirectories there if needed.   -Mike
>> 230 User logged in
>> ftp>   put alex_was_here
>> local: alex_was_here remote: alex_was_here
>> 227 Entering Passive Mode (96,42,66,188,11,76)
>> 550 You need to be in the /INCOMING directory to upload
>> ftp>   cd incoming
>> 250 CWD command successful
>> ftp>   put alex_was_here
>> local: alex_was_here remote: alex_was_here
>> 227 Entering Passive Mode (96,42,66,188,8,221)
>> 550 Bad path
>> ftp>   dir
>> 425 Transfer already in progress
>> Passive mode refused.
>> ftp>   ls
>> 425 Transfer already in progress
>> Passive mode refused.
>> ftp>   bye
>> 221 Server closing connection
>>
>> Hope this helps
>
>
>
> --
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fr

Re: [Freedos-user] Grr ... (Was: Re: mTCP-2011-10-01 is available

[Ulrich Hansen]

Thanks for this nice DOS FTP server!

I installed it under FreeDOS 1.0 in VirtualBox 4.1.4 (32 MB RAM) and 
on a real machine (Compaq Contura Aero 4/33 20MB RAM).

I then compared the performance of mTCP ftpsrv with other DOS 
FTP-servers. The competition was: EZ-NOS 2 [1], Datalight sockets ftpd 
[2], WATT32 ftpsrv32 [3] and SwsSock ftpd [4].

Client was Filezilla 3.5.1 on a MacBook Pro 2011 with OS X 10.6.8.

I transferred a mp3 song (Dylan/Cash: Girl from the North Country) 
with 8934148 bytes. The results:


Upload from Mac to DOS server

real machine virtualbox
EZ-NOS 275 sec.  4 sec.
Datalight Sockets   61 sec.  4 sec.
WATT32 ftpsrv32 21 sec. 11 sec.
mTCP ftpsrv 24 sec.  4 sec.
SwsSock ftpd32 sec.  4 sec.



Download from DOS server to Mac

real machine virtualbox
EZ-NOS 2154 sec.   135 sec.
Datalight Sockets70 sec. 4 sec.
WATT32 ftpsrv32  31 sec. 2 sec.
mTCP ftpsrv  23 sec. 2 sec.
SwsSock ftpd 94 sec.77 sec.


Datalight sockets works as TSR in the background so that may be a 
reason for its lack of speed in some tests. EZ-NOS 2 and SwsSock ftpd 
were very slow downloading the file. So I tested them a second and a 
third time, but came to the same result.

As you can see mTCP ftpsrv shows a very good performance.

regards
Ulrich




[1] EZ-NOS 2 (GPL 2) is a descendant of KA9Q and has been developed by 
Ken. His site  
is defunct, which is a real loss for every user interested in DOS 
networking. A working mirror can be found here: 


[2] Datalight Sockets is a commercial software that enables embedded 
DOS systems to connect to the internet. A free single user version for 
non-commercial purposes can be downloaded here:


[3] WATT32 ftpsrv32 (probably GPL 2) is an example app by the WATT32 
developers and can be found here:


[4] SwsSock is cross platform networking library. It comes with the 
source code and is called freeware. Companies and other organisations 
need a license, though. I used ftpd.exe from the prebuilt DOS examples 
a bit further on the page.


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Grr ... (Was: Re: mTCP-2011-10-01 is available

[Ulrich Hansen]

Thanks for the suggestions. I tested mTCP ftpsrv again *) with these 
values:

MTU 1472
FTPSRV_FILEBUFFER_SIZE 16
FTPSRV_TCPBUFFER_SIZE 16
FTPSRV_PACKETS_PER_POLL 2**)

Now look at the results!


Upload from Mac to DOS server

real machine virtualbox
EZ-NOS 275 sec.  4 sec.
Datalight Sockets   61 sec.  4 sec.
WATT32 ftpsrv32 21 sec. 11 sec.
mTCP ftpsrv 15 sec.  2 sec.
SwsSock ftpd32 sec.  4 sec.
PCTCP ftpsrv60 sec.  4 sec.


Download from DOS server to Mac

real machine virtualbox
EZ-NOS 2154 sec.   135 sec.
Datalight Sockets70 sec. 4 sec.
WATT32 ftpsrv32  31 sec. 2 sec.
mTCP ftpsrv  15 sec. 1 sec.
SwsSock ftpd 94 sec.77 sec.
PCTCP ftpsrv187 sec. 7 sec.

I think the numbers speak for themselves. mTCP ftpsrv seems to be the 
fastest DOS FTP server ever.

regards
Ulrich



*) To mention it again, the test was done by copying a 8934148 bytes 
big mp3 file. Client was Filezilla 3.5.1 on a MacBook Pro 2011 with OS 
X 10.6.8. As servers I used a FreeDOS 1.0 installation in VirtualBox 
4.1.4 (32 MB RAM) and a real machine (Compaq Contura Aero 4/33 20MB RAM).

**)  The value "FTPSRV_PACKETS_PER_POLL 10" you suggested slowed down 
the uploads to mTCP in virtualbox (7 sec. instead of 2 sec.). In 
detail the upload started, but shortly after the start paused for 3 or 
4 sec. With the value 2 there was no such delay.





--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS and virtualbox

[Ulrich Hansen]

I had time to work with freedos in virtualbox the last two days. I 
experienced some odd overheating problems. The Macbook Pro I used was 
getting hot at the bottom and shut down automatically.

It seems that FreeDOS grabs all the CPU power it finds. The Activity 
Monitor (Applications - Utilities) show CPU Usage of 100 or 102 %.

The solution I found:

For normal work at the DOS terminal (prompt only) the problem is 
solved by having a line

LH FDAPM APMDOS

in AUTOEXEC.BAT. (Another program people recommend is DOSIDLE, but it 
is unfree and doesn't seem to work better than FDAPM.)

With this trick CPU usage goes down from 100% to 4%.

But as soon as programs like edit, nc or nc clones (doszip) or other 
foreground or background applications are started (ftpsrv, sockets 
ftpd etc.) CPU usage goes up again to 100 %.

This can be avoided by Virtualbox itself: In the processor settings 
for the virtual machine you can limit the CPU usage. I set a limit of 
40 %.

What does FreeDOS want with 40% of an i5 anyhow?

Does anyone has more ideas about that problem?

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Weird UIDE.SYS (FreeDOS 1.1 Test) behavior under VirtualBox

[Ulrich Hansen]

I am opening this conversation again about CD support in VirtualBox:

It is true that the delay of UIDE at boot can be solved by selecting
ICH9 and Enable IO APIC in VirtualBox (> System->Motherboard).

Unfortunately this breaks networking in VirtualBox 4.0.12 and 4.1.4. 
The PCNTPK packet driver v. 1.20 for the PCnet-FAST III (Am79C973) 
VirtualBox NIC tells us:

"PCNTPK-DOS-015:Device not found"

Which means [1] that the driver cannot find an Ethernet controller. 
The driver 2.2 (which is included in FD 1.1beta) seems to install 
(after some time) but also doesn't work. Choosing another virtual NIC 
or disabling IO APIC doesn't solve it.

There is already a bugreport at the VirtualBox site [2]. It seems to 
be the fault of the ICH9 virtual chipset.

So at the moment you cannot have both with FreeDOS 1.1 in VirtualBox: 
CD/DVDs and network.

regards
Ulrich

[1] http://ps-2.kev009.com:8081/eprmhtml/epr3a/8498.htm
[2] https://www.virtualbox.org/ticket/9301



Am 24.07.11 04:29, schrieb Kenneth J. Davis:
> On Sun, Jul 17, 2011 at 11:13 PM, Juan Castro  wrote:
>> The first line (starting with "UIDE.SYS") stays there for 19 seconds. Then
>> the second one (starting with "IDE0 Controller") stays there for 49 seconds.
>> Then I get that error message. In  a real machine, UIDE loads lightning
>> quick.
>>
>> Screenshot: http://i.imgur.com/7rI2X.png
>>
>> Juan
>
> In your Virtualbox configuration (only tested with just released 4.1,
> but may also work with older releases) make sure under
> System->Motherboard  both ICH9 and Enable IO APIC are selected.  This
> will allow UIDE to load almost immediately same as in VMWare.  Note:
> the IO APIC may not be needed, but Virtualbox won't allow selecting
> ICH9 without it.  I am not sure what this actually changes with the
> emulation, but does stop the long delay.  Also even with the 4.1.0
> release, UIDE still displays the EDD error for C: and D: drives (BIOS
> drives 0x80 and 0x81), but I believe this is another Virtualbox error
> - haven't had the time to study Virtualbox's source to see what is
> wrong (I had hoped 4.1.0 would fix it since there is supposed to be a
> fix with the checksum).
>
> Jeremy
>
> --
> Magic Quadrant for Content-Aware Data Loss Prevention
> Research study explores the data loss prevention market. Includes in-depth
> analysis on the changes within the DLP market, and the criteria used to
> evaluate the strengths and weaknesses of these DLP solutions.
> http://www.accelacomm.com/jaw/sfnl/114/51385063/
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDAPM

[Ulrich Hansen]

Am 08.10.11 06:59, schrieb Marcos Favero Florence de Barros:

> FDAPM is *very* effective, but softwares must be FDAPM-aware.
>
> DosZip is FDAPM-aware and will typically use only 2% of CPU time,
> provided it is configured for that. Go to the Setup, System Options
> menu and chech the "Use DOS Idle Int 2Fh" checkbox.

Thanks a lot! CPU usage dropped from 100% to 4% with that setting.
I also will look into DPAKBD.

It would be really good if a helpful FreeDOS developer could add FDAPM 
awareness to more important programs in FreeDOS.

The unlimited CPU usage of FreeDOS programs running in VirtualBox is 
not a virtual or theoretical problem. It is real and it can cause real 
physical damage. My laptop was in fact overheating and shut down 
automatically.

Until this is solved, people should be recommended to limit at least 
the CPU usage in VirtualBox. But even with 40 percent the laptop gets 
too warm.

Have a nice weekend!
Ulrich

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDAPM

[Ulrich Hansen]

Am 08.10.11 19:54, schrieb Rugxulo:
>> It would be really good if a helpful FreeDOS developer could add FDAPM
>> awareness to more important programs in FreeDOS.
> I assume the shell would benefit from this the most, if not already.

The shell has no problem. CPU usage is normal (4%) if FDAPM is 
running, which is the default in FreeDOS. I often work with a nc 
clone, so finding out about the option in doszip was very helpful. I 
also replaced FreeDOS Edit with Pedit [1] which is freeware (but 
unfortunately not open source).

> Perhaps you can manually configure your Mac OS X to "power saver"
> (decrease or disable one of the cores) at those times?

If I leave FreeDOS running in VirtualBox with a not FDAPM aware 
program like FreeDOS Edit, after 30 minutes OS X will pop up a nice 
half transparent window. It tells me that my computer needs now to be 
shut down and that I should push the power button long enough to do 
so. There is no other option. It's the Mac version of the BSOD.

> There really is no perfect answer as modern hardware is just too
> powerful to run without a fan.

If the problem meant that just a fan is running, it would be cool with 
me. But I doubt that a CPU running _constantly_  at 100, even at 40% 
is such a good idea. I mean even when I open a large picture with 
Photoshop, CPU usage goes up to 40 only for a second and then stays at 
6 or 7 percent.

I will do some more tests if the problem occurs on my old laptop with 
Windows XP and with Ubuntu as well.

regards
Ulrich

[1] http://www.goldshell.com/pedit/

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDAPM

[Ulrich Hansen]

Am 09.10.11 02:21, schrieb Jack:
> Absolutely NO "self respecting" computer, or computer program,
> should at-all REQUIRE using "FDAPM" or any equivalents!   What
> has happened to Industrial RESPONSIBILITY, i.e. making systems
> that RUN, WITHOUT requiring such "Band Aid" power software??!!
>
> In my opinion, and "laptop" OR NOT, any computer that DOES get
> too hot just "sitting there" is a HOPELESS piece of TRASH that
> should be sent back for a REFUND (if possible!), or should get
> the solution that "DOS386" voiced on this forum (in one word!)
> about my ATROCIOUS medical bills, 4 months ago:  KALASHNIKOV!!

Wasnt't this in "Tron"?

FDAPM-aware software: "Nooo! I just wanted to respect the FDAPM!"

Master Control Program: "Die, you hopeless piece of crap!"

bangbangbangbangbang

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] New networked VirtualBox image (FreeDOS 1.1)

[Ulrich Hansen]

I have updated the networked FreeDOS image for VirtualBox to FreeDOS 
1.1Beta.

http://http://lazybrowndog.net/freedos/virtualbox/

For my changes to the original FreeDOS installation see the CHANGELOG 
at the end of the webpage.

I hope this helps everyone who wants to try DOS networking.

regards
Ulrich

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Heat problems of FreeDOS running in VirtualBox

[Ulrich Hansen]

I have written a description of the heat problems you get if you run 
DOS or FreeDOS in VirtualBox.

It can be found at: http://lazybrowndog.net/freedos/virtualbox/heat

Thanks again to Marcos for his suggestions.

regards
Ulrich

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Security

[Ulrich Hansen]

There is already a SSH project at:

http://sourceforge.net/projects/sshdos/

ssh2dos is working great for me. I really like to login into Debian with a DOS 
client...


Am 27.10.2011 um 18:22 schrieb Single Stage to Orbit:

> On Tue, 2011-10-25 at 21:49 -0500, Michael B. Brutman wrote:
> 
>> So what is it that you are trying to do?  If you are just going to
>> have a DOS machine in your house to play network Doom, then don't
>> worry, you don't have security problems.  If you are going to do
>> something else network related then it depends on the program.
>> Running FTP and Telnet on modern networks is a problem because those
>> send passwords "in the clear" on the wire, which can be dangerous on
>> the open Internet. 
> 
> Can we expect mSSH in the works any time soon? :) FWIW, the SSH protocol
> is fairly open and there's nothing to stop anybody from writing new
> SSH/SCP utility programs for DOS. 
> -- 
> Tactical Nuclear Kittens
> 
> 
> 
> --
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn 
> about Cisco certifications, training, and career opportunities. 
> http://p.sf.net/sfu/cisco-dev2dev
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] [Freedos-devel] FreeDOS 1.1 released

[Ulrich Hansen]

Congratulations to FreeDOS 1.1 !!

There are newsitems on two important german IT News sites:

http://www.heise.de/newsticker/meldung/FreeDOS-1-1-freigegeben-1403219.html
http://www.golem.de/1201/88775.html

Thanks!
Ulrich


Am 04.01.2012 um 15:13 schrieb escape:

> Announce on Russian sites dedicated to free and open source software
> caused a lot of discussion:
> http://www.opennet.ru/opennews/art.shtml?num=32720
> http://www.linux.org.ru/news/opensource/7213522
> 
> On 04.01.12 00:39, James Hall wrote:
>> I'm collecting news items for our "FreeDOS in the news" page. Let me
>> know if you see more coverage:
>> http://www.freedos.org/freedos/news/
>> 
>> -jh
> 
> --
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual 
> desktops for less than the cost of PCs and save 60% on VDI infrastructure 
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> ___
> Freedos-devel mailing list
> freedos-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] VirtualBox FreeDOS HowTo

[Ulrich Hansen]

I have started a VirtualBox HowTo in our FreeDOS wiki.
It is a sort of installation walkthrough with many pictures.

It can be found here:

http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Installing_FreeDOS_in_VirtualBox

Feel free to take a look. 

Please write if you find something that should be corrected or added. Or add it 
yourself if you like (it is a wiki after all).

regards
Ulrich



--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] UIDE.SYS delays boot process in VirtualBox

[Ulrich Hansen]

I have written a description of the boot delay caused by the loading of 
UIDE.SYS in VirtualBox.

https://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_8

Anybody has an idea how to solve this with free software? Would the 
eltorito.sys driver help? I never worked much with CD drives in FreeDOS, so I 
am a bit stuck.

Thanks,
Ulrich
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] UIDE.SYS delays boot process in VirtualBox

[Ulrich Hansen]

Am 12.01.2012 um 20:20 schrieb Jack:
> 
>> Loading UIDE at runtime instead of boottime is also possible, in some
>> theoretical CDROM.BAT for example ...
> 
> Doubtful this would help at all, since UIDE is going to do exactly the
> same checks of the PCI bus for CD/DVD drives, whenever it gets loaded.

Correct. It takes the same amount of time. Fortunately the batchfile is run 
whenever the user wants, which is more acceptable than such a long delay at 
boot.

And the boot delay is not really acceptable. Stopwatch says 2min and 49sec. 
This is much more than the 60sec I thought it would be.


>> Alternatives are creating and using an ISO file:
>> OMI.EXE D: C:\FDBOOTCD.ISO
>> 
>> Or replacing the CD-driver by the closed-source generic OAKCDROM.SYS or
>> VIDE-CDD.SYS drivers [http://www.opus.co.tt/dave/indexall.htm].
> 
> I do NOT recommend any of the older "generic" drivers, since none of them
> have UltraDMA logic, and none use file/directory caching.   Omitting both
> of these items will cause CD/DVD transfers to run 3 or 4 times slower!
> 
> Also, a "generic" driver normally uses only "Legacy IDE" device addresses
> and cannot "see" a controller whose addresses might be assigned by PCI to
> other values.   This is true for VIDE-CDD, OAKCDROM, my "old" XCDROM, and
> about all other "generic" CD/DVD drivers.
> 
> Note also that GCDROM/XGCDROM (BAD "hacks" of XCDROM!) "claim" to support
> other addresses, but in fact they have PROBLEMS!

And we also should not suggest in our WIki that our users should use unfree 
software illegally to use FreeDOS. So this is not really an option anyway.

>> Jack's UIDE.SYS driver performs chipset initialisation which is
>> apparently still implemented in a buggy way in the VirtualBox software.
> 
> No other way possible for UIDE!   CD/DVD drives are not part of the BIOS,
> so UIDE must "detect" them by (A) finding all SATA/IDE controllers on the
> PCI bus, then (B) examining each controller's device slots for "ATAPI CD"
> drives.
> 
> If some of the VirtualBox "chipset" options exhibit LONG delays when UIDE
> issues an "Identify ATAPI Device" command, VirtualBox needs to get FIXED!

As DOS seems not really to be Oracles priority, we may have to wait. In the 
meantime it is IMHO a good idea that VirtualBox users use Bernds batchfile to 
mount the VirtualBox virtual CD drive whenever they can afford the time.

Thanks!


 --
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Fwd: VirtualBox FreeDOS HowTo

[Ulrich Hansen]

Sorry I meant to send this earlier, but accidentally chose the wrong sender 
address. So it wasn't accepted by the list server. Here it comes again:

Am 11.01.2012 um 18:27 schrieb Bernd Blaauw:

> Op 11-1-2012 0:58, Ulrich Hansen schreef:
>> I have started a VirtualBox HowTo in our FreeDOS wiki.
>> http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox
> 
> That looks great, you've done an awesome job at posting such a detailed 
> guide. I'm so happy I kept things simple for now so not that many issues 
> will arise.

Thanks! Congratulations to your own good work! The installation process seemed 
a lot easier to me than with 1.0. 
And the unfortunate network setup of 1.0 is gone, which is great. And we have a 
clean boot menu where all four options actually work (not just the first 3).

> Thanks for your guide, I hope Jim will link it from the download page.

I made a link to it from the HOWTO page in our wiki [1]. 

Today I added the description of the heat problems you get with DOS systems in 
VirtualBox [2] Since now I had this page on my own server. But now we have a 
place of information about VirtualBox in our wiki, it makes more sense to put 
the information there.

regards
Ulrich


[1] http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Howto
[2] 
https://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_7--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.1: JemmEx conflicts with Keyb

[Ulrich Hansen]

This seems to be a minor (but annoying) bug in FreeDOS 1.1: The german keyboard 
does not work after the install. If I install the US keyboard, there is no 
problem.

Description: I have installed FreeDOS 1.1 with german language and keyboard. If 
I boot (after a fresh install) with bootmenu option 1 (Load FreeDOS with 
JemmEx) keyb will crash with the error message:

Keyboard layout : C:\FDOS\bin\keyboard.sys:GR [858](3)
Critical error: cannot allocate memory. DOS reported error: 8

The rest seems to boot okay, but of course I have the wrong keyboard layout 
afterwards...

If I choose bootmenu 2 (Load FreeDOS with EMM386) instead of 1, everything 
works fine and I have all my umlaute back ;-).

Solution: Today I have solved this problem by removing "X = TEST" from the 
JemmEx line in FDCONFIG.SYS. So the line looks like this:

1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS I=TEST NOVME NOINVLPG

Bootmenu 1 boots OK now, with keyb not crashing.

Now my question: What do I lose by removing "X=TEST"? Will the system become 
more unstable? 

I experienced this with my VirtualBox installation of FreeDOS. Is it possible, 
that this is only relevant in VirtualBox? Does anyone else know this "bug"?

Thanks! regards
Ulrich 



--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1: JemmEx conflicts with Keyb

[Ulrich Hansen]

Am 13.01.2012 um 18:54 schrieb Bernd Blaauw:

> Op 13-1-2012 16:11, Ulrich Hansen schreef:
>> 
>> Description: I have installed FreeDOS 1.1 with german language and keyboard. 
>> If I boot (after a fresh install) with bootmenu option 1 (Load FreeDOS with 
>> JemmEx) keyb will crash with the error message:
>> 
>> Keyboard layout : C:\FDOS\bin\keyboard.sys:GR [858](3)
>> Critical error: cannot allocate memory. DOS reported error: 8
> 
> could you try adding "/NOHI" at your KEYB line please? 

Wow. This worked! 

In AUTOEXEC.BAT I have now a line:

KEYB GR,,keyboard.sys /NOHI

In FDCONFIG.SYS I went back to all the original settings of FreeDOS 1.1. So the 
JemmEx line looks like this again:

1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG

> X=TEST is just a test for checking which UMB areas are (un)safe to use.
> 
> Could you perhaps try adding X=TEST to option 2 (EMM386) ? See if that 
> works. I've not been able to reproduce your case in VMWARE Workstation 8.

X=TEST is originally in option 2. The lines in FDCONFIG.SYS (untouched after 
installation) look like this:

2?DEVICE=C:\FDOS\BIN\HIMEMX.EXE
2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG

So this is OK. 

I don't really understand why leaving out "X=TEST" in option 1 solved the 
problem too. Testing the UMBs should lead to a more stable behavior of 
JEMMEX.EXE. Instead it crashed KEYB somehow. It's odd but it's easy to 
reproduce with any fresh FreeDOS installation on VirtualBox with the default 
settings (and choosing german keyboard layout).

Anyway, starting KEYB with /NOHI seems to be the more elegant and logical 
solution. 
Thanks!

If this could be the default in FreeDOS, I think it would help other users. At 
least the german ones... ;-)

regards
Ulrich





--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.1: JemmEx conflicts with Keyb

[Ulrich Hansen]

Am 14.01.2012 um 00:17 schrieb Rugxulo:

>> In FDCONFIG.SYS I went back to all the original settings of FreeDOS 1.1. So 
>> the JemmEx line looks like this again:
>> 
>> 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
> 
> Why is this using NOVME NOINVLPG? Is it trying to be
> ultra-conservative? Is there a known VirtualBox (or other) bug
> somewhere? Seems odd ... though INVLPG is 486 and VME is 586, perhaps
> you're trying for old 386 compatibility?? (And I blindly assume
> JEMM386 already is aware of when it's safe to use.)

Like I said, this line is from the FDCONFIG.SYS that the FreeDOS 1.1 installer 
produces. It is the same on every system with FreeDOS 1.1 installed. It has 
nothing to do with VirtualBox.

>>> X=TEST is just a test for checking which UMB areas are (un)safe to use.
>>> 
>>> Could you perhaps try adding X=TEST to option 2 (EMM386) ? See if that
>>> works. I've not been able to reproduce your case in VMWARE Workstation 8.
> 
> If VMware doesn't exhibit it, it may be a VirtualBox bug. Remember,
> VBox is not perfect, esp. for DOS, sadly, as it's not a priority for
> them (e.g. D3X extender).

Possibly. I didn't have the time to check the behavior of KEYB and JemmEx on a 
real machine. Maybe the bug is just caused by the way VirtualBox allocates its 
system ROM.

>> I don't really understand why leaving out "X=TEST" in option 1
>> solved the problem too. Testing the UMBs should lead to a
>> more stable behavior of JEMMEX.EXE. Instead it crashed
>> KEYB somehow.
> 
> Dunno, and haven't checked, but I hope we're using latest KEYB 2.01 here.

Yes, KEYB.EXE ver. 2.01 from 18.08.2011

>> It's odd but it's easy to reproduce with any fresh FreeDOS
>> installation on VirtualBox with the default settings (and
>> choosing german keyboard layout).
> 
> Does "default" mean with or without VT-X enabled? Neither is perfect.

At least on my host system, VirtualBox enables it in every new virtual machine 
by default. Disabling it manually doesn't have an effect. Still KEYB crashes. 
To make it work, you have to a) start it with the option "/NOHI". Or you b) 
start JemmEX without the option "X=TEST".

>> If this could be the default in FreeDOS, I think it would help other
>> users. At least the german ones... ;-)
> 
> Well, presumably most German users know to press F8 and manually
> disable stuff if they run into problems (or F5 for clean boot, worst
> case scenario). DOS really isn't that user friendly. Caveat emptor.
> ;-)

Maybe that's why people still like to use it. :-)

I did some further testing and KEYB also crashes for the french, the dutch and 
the spanish users. (BTW: For the polish, it says "codepage not found in 
definition file - 437", so KEYB aborts anyway...). I think we can assume that 
the bug is present for every FreeDOS user that doesn't use an US keyboard.

If we can avoid somehow that an important system driver like KEYB doesn't work 
after a fresh install of FreeDOS 1.1 for many people using a popular platform, 
we should do it.

--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

[Ulrich Hansen]

Hi Wolfgang, 

I just tested this with FreeDOS 1.1 as guest and VirtualBox 4.1.14 under OS X 
as host and it works for me.

I start FreeDOS with option 1 in the start menu.

I did not load UIDE.SYS in AUTOEXEC.BAT, as I normally don't work with CDs in 
FreeDOS anyway and VirtualBox conflicts with the driver. See (1).

I added a Virtual Floppy Drive in the settings of the VirtualBox guest by going 
to "Storage"  selecting the IDE Controller and clicking the second "+" sign to 
"Add floppy controller". Afterwards I added a floppy drive by clicking on the 
small floppy symbol in the line "floppy controller". I leave the floppy drive 
empty. I then can choose to load a floppy image by selecting in the VirtualBox 
menu "Devices" - "Floppy devices" - " Choose a virtual floppy disk file".

Changing between floppies works for me without having to do anything in 
FreeDOS. I just enter "A:" in DOS. As soon as I change to a new image in the 
Devices menu FreeDOS recognizes it and shows the contents by running the "dir" 
command in A:. I don't even have to change to C: and back to A: to make FreeDOS 
recognize the new floppy, I just stay in A: and get the new contents by running 
"dir". 

Maybe the virtual floppy image is the problem? I think there are various ways 
to create them with free tools. I was so lazy to create "img"-files with the 
non-free utility "WinImage" (2) in Windows XP. These work for me.

regards
Ulrich

(1) 
http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_8
(2) http://http://www.winimage.com


Am 16.05.2012 um 18:33 schrieb Wolfgang Schechinger:

> Dear experts, 
> 
> I have some floppy images I want to use with FreeDos that is running in a VM 
> (VirtualBox). The images work fine with e.g. Windows in such an environment.
> 
> However with the virtual FreeDos, disk changes are not recognized: Only the 
> first Image that has been used after boot is show with e.g. dir, even when 
> the image has been remove or replaced.
> 
> I suppose that the problem is how to tell FreeDos that the disk has changed.
> 
> Anything I could do?
> 
> Thanks for your help!
> 
> Wo
> 
> PS The host system is Opensuse Linux 11.4
> -- 
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
> 
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

[Ulrich Hansen]

> 
>>> thanks for the hint! I have commented out the line in autoexec.bat which
>>> loads the UIDE.SYS cdrom driver. Now there is no problem accessing the
>>> floppy images.
>> 
>> So maybe there is a problem with floppy change signalling
>> versus caches - would be interesting to know whether it is
>> sufficient to keep UIDE but run UIDE in no-cache mode, and
>> if "lbacache flop" (lbacache with floppy caching enabled)
>> would work correctly with floppy changes in virtualbox.
> 
> UIDE does not include logic to "ignore" a diskette drive.   If one or
> two are present, UIDE will always cache them.   I never expected any-
> one would need (or want!) to run diskettes without caching.   One can
> use UIDEJR instead, but UIDEJR is only a "driver" with no caching and
> thus would not perform as well.
> 
> Folks really should INSIST that the writers of VirtualBox "Follow the
> RULES!" for PC hardware, instead of leaving you and I (perhaps others
> as well) to make changes in long-established programs just for them!!
> 
> Jack R. Ellis


Hi Jack, 

I think the /B switch works for me.


/B   For UIDE only, requests a basic "stand alone" UltraDMA driver
   for disks or CD/DVD drives (no cache or diskettes). This
   may help in tests or diagnostics. The basic UIDE can use
   128K of XMS memory and can now load in HMA space. UIDEJR
   will ignore /B.


If I now change the floppy in the VirtualBox devices menu, this is recognized 
immediately in FreeDOS. So everything seems to be correct with this setting.

The downside is that booting takes much longer, as the VirtualBox default 
chipset PIIX3 still conflicts with UIDE.SYS.The alternate chipset ICH9 works 
fine with UIDE.SYS but unfortunately conflicts with the ethernet controller. (1)

regards
Ulrich


(1) 
http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_8

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user