[Freedos-user] New VirtualBox images / FreeDOS networking

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 Fre

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

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 exis

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

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:

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

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

Re: [Freedos-user] INTERLINK

> 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.

Re: [Freedos-user] INTERLINK

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 FD

Re: [Freedos-user] INTERLINK

> 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. O

Re: [Freedos-user] INTERLINK

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

Re: [Freedos-user] INTERLINK

> 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 /AU

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

> > 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

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

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 re

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

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,

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

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 E

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

> 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.lazybrown

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

> 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

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

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

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

> 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!

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

> 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

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

> 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 FDCONF

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

> 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 a

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

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.n

[Freedos-user] VirtualBox and FreeDOS

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 c

Re: [Freedos-user] Keyboard input absent

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

Re: [Freedos-user] Keyboard input absent

>> >> 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 discov

Re: [Freedos-user] Keyboard input absent

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 t

[Freedos-user] Mounting VirtualBox FreeDOS images in Windows

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 y

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

> 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 a

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

> 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/e

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

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 user

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

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/ulr

Re: [Freedos-user] M2WAT

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/

Re: [Freedos-user] M2WAT

> 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

Re: [Freedos-user] M2WAT

> 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 Ara

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

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 r

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

> 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 do

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

> 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. --

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

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 Debi

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

hell. > 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. >

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

> 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

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

> 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, min

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

> 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: >>

Re: [Freedos-user] questions on FreeDOS

> 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 star

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

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 t

[Freedos-user] FreeDOS images for VirtualBox

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/ -

Re: [Freedos-user] FreeDOS images for VirtualBox

> 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.

Re: [Freedos-user] FreeDOS images for VirtualBox

>> 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

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

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 driv

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

> 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 cu

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

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 d

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

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 Stern

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

> 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 > suppo

[Freedos-user] intel PRO/

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:

Re: [Freedos-user] M2WAT

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:

Re: [Freedos-user] M2WAT

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:

Re: [Freedos-user] M2WAT

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>>%W

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

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

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

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

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

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:

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

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,

Re: [Freedos-user] FreeDOS images for VirtualBox

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:

Re: [Freedos-user] questions on FreeDOS

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:

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

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:

Re: [Freedos-user] FreeDOS images for VirtualBox

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:

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

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:

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

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:

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

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:

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

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

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

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.

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

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

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

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

[Freedos-user] Full Networked FreeDOS image for VirtualBox

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

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

tp://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 bla

Re: [Freedos-user] mTCP source code released

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 increa

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

d 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

Re: [Freedos-user] Basic networking abilities

at 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,

Re: [Freedos-user] Why I use FreeDOS

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

Re: [Freedos-user] Packet Driver

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 ne

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

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 fa

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

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

Re: [Freedos-user] FTP Server testing needed

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

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

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

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

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 2

[Freedos-user] FreeDOS and virtualbox

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)

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

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

Re: [Freedos-user] FDAPM

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 Idl

Re: [Freedos-user] FDAPM

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 r

Re: [Freedos-user] FDAPM

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

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

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

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

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

Re: [Freedos-user] FreeDOS Security

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 wha

Re: [Freedos-user] [Freedos-devel] FreeDOS 1.1 released

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 dedica

[Freedos-user] VirtualBox FreeDOS HowTo

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

[Freedos-user] UIDE.SYS delays boot process in VirtualBox

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

Re: [Freedos-user] UIDE.SYS delays boot process in VirtualBox

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 loa

[Freedos-user] Fwd: VirtualBox FreeDOS HowTo

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 ou

[Freedos-user] FreeDOS 1.1: JemmEx conflicts with Keyb

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

Re: [Freedos-user] FreeDOS 1.1: JemmEx conflicts with Keyb

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) key

Re: [Freedos-user] FreeDOS 1.1: JemmEx conflicts with Keyb

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 > ul

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

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 t

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> >>> 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 i

  1   2   >