Re: [Freedos-user] Virtualbox Networking Issue

2021-05-27 Thread Ralf Quint
On 5/27/2021 12:06 PM, Michael Brutman wrote: Ralf: Traceroute is interesting, and it's on the todo list.  This is more equivalent to a TCPDUMP trace. Yeah, that would be really helpful. As I mentioned, ping (without any such logging enabled) isn't really a diagnostic tool. It just tells you

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-27 Thread Michael Brutman
Kelley: That version of mTCP is nearly 8 years old ... Please get the current version and repeat the trace file steps. It might even just work without debugging ... I've made a lot of reliability improvements in the past 8 years. Also, please email me *directly* ... this is an mTCP question, n

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-27 Thread Ralf Quint
On 5/26/2021 10:17 PM, Kelley McChesney wrote: Hi Michael, I went through the instructions to enable debugging and pinged www.brutman.com . I have attached my MTCP config file and the trace.txt file for you. Thank you for looking at this. Just had a look at that log file

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-27 Thread Ralf Quint
On 5/26/2021 8:04 PM, Michael Brutman wrote: Hi - I'm the author of mTCP. mTCP is shipped with FreeDOS but it is an independent project. Please check the PDF, specifically the section on debugging.  I'd like to see a trace from your system when you are using a bridged Ethernet connection.  Us

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-26 Thread Kelley McChesney
Hi Michael, I went through the instructions to enable debugging and pinged www.brutman.com. I have attached my MTCP config file and the trace.txt file for you. Thank you for looking at this. On Wed, May 26, 2021 at 11:05 PM Michael Brutman wrote: > Hi - I'm the author of mTCP. mTCP is shipped wi

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-26 Thread Michael Brutman
Hi - I'm the author of mTCP. mTCP is shipped with FreeDOS but it is an independent project. Please check the PDF, specifically the section on debugging. I'd like to see a trace from your system when you are using a bridged Ethernet connection. Use PING (the one that comes with mTCP), but specify

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-26 Thread Eric Auer
Hi again, > Hi Ralf, I actually can't use traceroute to find the problem. This is in a > VM and as far as I know traceroute doesn't exist for FreeDOS. According to http://www.bttr-software.de/freesoft/comm1.htm there is a traceroute (tracert) included with wattcp32. Other implementations cou

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-26 Thread Kelley McChesney
Hi Ralf, I actually can't use traceroute to find the problem. This is in a VM and as far as I know traceroute doesn't exist for FreeDOS. I have tried other VMs and they seem to work fine with different OS's, so this is purely a FreeDOS issue. On Wed, May 26, 2021 at 5:09 PM Ralf Quint wrote: > O

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-26 Thread Ralf Quint
On 5/26/2021 1:45 PM, Kelley McChesney wrote: Hi Eric, I've actually been trying DHCP, which seems to be fine. I tried your recommendations and tested both my router's gateway as a nameserver and checked what my host computer was using. Unfortunately, my host computer was using the same server

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-26 Thread Kelley McChesney
Hi Eric, I've actually been trying DHCP, which seems to be fine. I tried your recommendations and tested both my router's gateway as a nameserver and checked what my host computer was using. Unfortunately, my host computer was using the same server as the DHCP server was giving FreeDOS and my route

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-26 Thread Eric Auer
Hi! > Unfortunately it does actually seem to be a networking issue. I just tried > to wget the current fdnpkg file from ibiblio.org and it failed, reporting: > "Resolving www.ibiblio.org... failed: No address associated with hostname. Note that 8.8.8.8 is a nameserver outside your house, you co

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-26 Thread Kelley McChesney
Unfortunately it does actually seem to be a networking issue. I just tried to wget the current fdnpkg file from ibiblio.org and it failed, reporting: "Resolving www.ibiblio.org... failed: No address associated with hostname. wget.exe: unable to resolve host address 'www.ibiblio.org'". I did forget

Re: [Freedos-user] Virtualbox Networking Issue

2021-05-25 Thread Jerome Shidel
Since you had ping working, you probably had networking working. So, it may just be an issue with the config file for FDNPKG that got installed. You should verify the settings in C:\FDOS\BIN\FDNPKG.CFG or you can just fetch the latest version of the package from the online repository at http:/

Re: [Freedos-user] virtualbox int 15 memdisk failure - was: Unable to install FreeDOS 1.2 on VirtualBox

2018-07-31 Thread Mercury Thirteen via Freedos-user
Both "int" and "raw" launch properly, but "bigint" gives the same ol' "Invalid Opcode" loop. VirtualBox doesn't have an explicit setting for AHCI versus IDE, but you can get the same effect through what type of storage controller you add to your virtual machine; if you want it handled as AHCI,

Re: [Freedos-user] virtualbox int 15 memdisk failure - was: Unable to install FreeDOS 1.2 on VirtualBox

2018-07-31 Thread Eric Auer
Hi! > To further isolate the Invalid Opcode issue, I extracted the floppy > image (FDBOOT.IMG from the ISOLINUX folder) from the ISO and booted > it as a floppy disk in VirtualBox which launched the installer > flawlessly. Thanks for the testing! So apparently NOINVLPG would not have helped. Ho

Re: [Freedos-user] virtualbox int 15 memdisk failure - was: Unable to install FreeDOS 1.2 on VirtualBox

2018-07-30 Thread Mercury Thirteen via Freedos-user
So, being a VirtualBox "owner", I did some testing. :) First, I tested three methods of installing FreeDOS 1.2: FD12CD.iso, FD12LGCY.iso, and FLOPPY.IMG from FD12FLOPPY.ZIP. The infinite Invalid Opcode loop only occurs for me when booting FD12CD.iso. Oddly enough, booting FD12LGCY.iso on Virtua

Re: [Freedos-user] VirtualBox and FTP

2014-09-01 Thread Ulrich
Am 01.09.2014 um 21:51 schrieb Michael Brutman : > On 9/1/2014 12:30 PM, Tom Ehlert wrote: >> any good reason mTCP and DHCP can't update/use WATTCP.directly ? >> >> imho there should be a *single* network configuration file, used by >> *all* network stuff on the machine. >> >> changing mTCP to

Re: [Freedos-user] VirtualBox and FTP

2014-09-01 Thread Michael Brutman
On 9/1/2014 12:30 PM, Tom Ehlert wrote: > any good reason mTCP and DHCP can't update/use WATTCP.directly ? > > imho there should be a *single* network configuration file, used by > *all* network stuff on the machine. > > changing mTCP to understand WATTCP.CFG is trivial. (WATTCP.CFG has > been arou

Re: [Freedos-user] VirtualBox and FTP

2014-09-01 Thread Tom Ehlert
Hi, > I don't want to brag too much, but M2WAT shows the absolute brilliance > of separating the DHCP process from the programs. ;-0 The mTCP programs > do not know or care about DHCP; they behave the same whether they have a > static IP address or a DHCP obtained one. M2WAT helps the WATTCP >

Re: [Freedos-user] VirtualBox and FTP

2014-09-01 Thread dmccunney
On Mon, Sep 1, 2014 at 2:44 PM, Mateusz Viste wrote: > DHCP separation can be nice, but it has also its downsides. > > It's definitely a nice choice because it makes programs a bit smaller. > However, a problem might appear in the (unlikely?) situation where a > user plays with a network-enabled p

Re: [Freedos-user] VirtualBox and FTP

2014-09-01 Thread Michael Brutman
The expiring lease problem is irritating. My answer to that is have people choose reasonable lease times and to run DHCP before doing something that might run a while. "Reasonable" generally means at least 8 hours ... If 8 hours is too long a nice work around is to configure the DHCP server

Re: [Freedos-user] VirtualBox and FTP

2014-09-01 Thread Mateusz Viste
DHCP separation can be nice, but it has also its downsides. It's definitely a nice choice because it makes programs a bit smaller. However, a problem might appear in the (unlikely?) situation where a user plays with a network-enabled program while his lease expires. Say, my DHCP router provides

Re: [Freedos-user] VirtualBox and FTP

2014-09-01 Thread Michael Brutman
I don't want to brag too much, but M2WAT shows the absolute brilliance of separating the DHCP process from the programs. ;-0 The mTCP programs do not know or care about DHCP; they behave the same whether they have a static IP address or a DHCP obtained one. M2WAT helps the WATTCP programs be

Re: [Freedos-user] VirtualBox and FTP

2014-09-01 Thread Ulrich Hansen
> Am 01.09.2014 um 17:05 schrieb Ulrich : > > Mike, what do you think - would it be a good idea to ship it with your mTCP > package? If this is Ok with Dave, I should have written of course. -- Slashdot TV. Video for

Re: [Freedos-user] VirtualBox and FTP

2014-09-01 Thread Ulrich
Hi Thanks a lot, Dave, for the program. I was eager to try it, so I downloaded OpenWatcom and compiled my first DOS program :-)) Had some time, while my son listened to some audiobook called "Mama Muh". :-) I copied the program lines to a file m2wat.c and used these settings: wcc m2wat /ms wli

Re: [Freedos-user] VirtualBox and FTP

2014-08-31 Thread Michael Brutman
On 8/31/2014 1:36 PM, Rugxulo wrote: > Hi, > > On Sat, Aug 30, 2014 at 10:10 PM, Michael Brutman > wrote: >> It pains me to see this much effort going into what should be a small >> utility that takes the relevant mTCP obtained network parameters and >> writes them into the WATTCP file. There ar

Re: [Freedos-user] VirtualBox and FTP

2014-08-31 Thread cordata02
>I suggest that somebody write a small program that takes the current >>configuration parameters from the mTCP configuration file and updates a >WATTCP >configuration file. It should not be a terribly complicated program - >you just >have to do some light string processing. Here' you go:

Re: [Freedos-user] VirtualBox and FTP

2014-08-31 Thread Rugxulo
Hi, On Sat, Aug 30, 2014 at 10:10 PM, Michael Brutman wrote: > > It pains me to see this much effort going into what should be a small > utility that takes the relevant mTCP obtained network parameters and > writes them into the WATTCP file. There are 15 invocations of the > mt.exe program in th

Re: [Freedos-user] VirtualBox and FTP

2014-08-31 Thread cordata02
tuff in "otherwat.cfg" ... Most (likely all) of that other stuff is not needed anyway. Dave -Original Message- From: Ulrich To: Discussion and general questions about FreeDOS. Sent: Sun, Aug 31, 2014 12:15 pm Subject: Re: [Freedos-user] VirtualBox and FTP I am sorr

Re: [Freedos-user] VirtualBox and FTP

2014-08-30 Thread Ulrich
Am 31.08.2014 um 05:31 schrieb dmccunney : > it looks like > > mt -b- -c -n wattcp.cfg #ipaddr = my_ip= #netmask = netmask= #gateway > = gateway= #nameserver = nameserver= #hostname = hostname= > > would do the same thing. Hmm. Doesn't. Scrambles wattcp.cfg. :-( But was a good idea. --

Re: [Freedos-user] VirtualBox and FTP

2014-08-30 Thread dmccunney
On Sat, Aug 30, 2014 at 11:10 PM, Michael Brutman wrote: > > It pains me to see this much effort going into what should be a small > utility that takes the relevant mTCP obtained network parameters and > writes them into the WATTCP file. There are 15 invocations of the > mt.exe program in that sc

Re: [Freedos-user] VirtualBox and FTP

2014-08-30 Thread Michael Brutman
It pains me to see this much effort going into what should be a small utility that takes the relevant mTCP obtained network parameters and writes them into the WATTCP file. There are 15 invocations of the mt.exe program in that script. I suggest that somebody write a small program that takes

Re: [Freedos-user] VirtualBox and FTP

2014-08-30 Thread Ulrich
I am sorry, there were some errors in my previous post: The batchfile has to be called like this in AUTOEXEC.BAT, right after the line DHCP: DHCP CALL C:\FDOS\M2WAT.BAT Otherwise it wouldn't return to AUTOEXEC.BAT. There were also errors in the batchfile itself. I made some changes, now it se

Re: [Freedos-user] VirtualBox and FTP

2014-08-30 Thread Ulrich
Am 30.08.2014 um 23:56 schrieb Mateusz Viste : > Thanks for sharing! > I might have missed something, but why haven't you used the DHCP.COM tool > from Dave Dunfield, instead of all the sed-like magic? Just curious. The main reason is that (unfortunately) DHCP.COM doesn't seem to be free softw

Re: [Freedos-user] VirtualBox and FTP

2014-08-30 Thread Mateusz Viste
Hi Ulrich, Thanks for sharing! I might have missed something, but why haven't you used the DHCP.COM tool from Dave Dunfield, instead of all the sed-like magic? Just curious. Mateusz On August 30, 2014 11:47:35 PM GMT+02:00, Ulrich wrote: > >I think I found a solution. > >The problem was:

Re: [Freedos-user] VirtualBox and FTP

2014-08-30 Thread Ulrich
I think I found a solution. The problem was: When I choose "NAT" as network type for a VirtualBox FreeDOS 1.1 guest, only mTCP DHCP.EXE is able to get the correct IP addresses from the DHCP server provided by VirtualBox. WATTCP applications fail to get their IPs from that DHCP server. The i

Re: [Freedos-user] VirtualBox and FTP

2014-08-30 Thread Ulrich
.cfg #netmask = netmask= >> mt -b- -c -n wattcp.cfg #gateway = gateway= >> mt -b- -c -n wattcp.cfg #nameserver = nameserver= >> mt -b- -c -n wattcp.cfg #hostname = hostname= >> >> >> Step 3 Run it after MTCP DHCP. >> >> Dave >> >> >

Re: [Freedos-user] VirtualBox and FTP

2014-08-29 Thread Anton D . Kachalov
Hello, Tom. Previously, we use ODI stack (Novell) with NIC autodetection (net.bat): https://github.com/ya-mouse/dos-net-odi/ It is already contains a few drivers. It's easy to add more. I hope iPXE would have packet's driver support soon. 29.08.2014, 14:58, "Tom Ehlert" : >>  We use undipd

Re: [Freedos-user] VirtualBox and FTP

2014-08-29 Thread Tom Ehlert
> We use undipd driver: > http://www.shikadi.net/network/files/undi2pd/undipd.com this is great - if and only if booted from PXE. Tom > It is widely tested on the newest hardware: notebooks, desktops and servers. > 28.08.2014, 23:14, "Rugxulo" : >> Hi, >> >> On Mon, Aug 25, 2014 at 10:59

Re: [Freedos-user] VirtualBox and FTP

2014-08-28 Thread Anton D . Kachalov
Hello. We use OpenWatcom compiled version of Watt32: https://github.com/ya-mouse/dos-utils This repo contains watt32-version of curl also. We use undipd driver: http://www.shikadi.net/network/files/undi2pd/undipd.com It is widely tested on the newest hardware: notebooks, desktops and

Re: [Freedos-user] VirtualBox and FTP

2014-08-28 Thread Rugxulo
Hi, On Mon, Aug 25, 2014 at 10:59 PM, Mateusz Viste wrote: > > Might be that the DHCP implementation of VirtualBox is incompatible with > the DHCP client embedded in Watt32... A PCAP capture might show more, > although not sure if there is any point, since watt32 probably won't be > updated/fixed

Re: [Freedos-user] VirtualBox and FTP

2014-08-27 Thread Ulrich
iginal Message- > From: Michael Brutman > To: Discussion and general questions about FreeDOS. > > Sent: Tue, Aug 26, 2014 10:53 am > Subject: Re: [Freedos-user] VirtualBox and FTP > > > David Dunfield has a utility called DHCP that will work with both mTCP

Re: [Freedos-user] VirtualBox and FTP

2014-08-27 Thread cordata02
about FreeDOS. Sent: Tue, Aug 26, 2014 10:53 am Subject: Re: [Freedos-user] VirtualBox and FTP David Dunfield has a utility called DHCP that will work with both mTCP and WATTCP. I've not tried it, but David is well known in vintage-computer circles and his software is supposed to be

Re: [Freedos-user] VirtualBox and FTP

2014-08-26 Thread Michael Brutman
David Dunfield has a utility called DHCP that will work with both mTCP and WATTCP. I've not tried it, but David is well known in vintage-computer circles and his software is supposed to be pretty good. http://www.classiccmp.org/dunfield/dos/index.htm Mike --

Re: [Freedos-user] VirtualBox and FTP

2014-08-25 Thread cordata02
>mTCP vs wattcp.cfg - I agree this would be awesome if mTCP could read/write >>WatTCP config files for backward compatibility :) Step 1: Install minitrue on your PC. mt.exe ... google it. Step 2: Create a batch file called "M2WAT.BAT" Put this stuff in the batch file: @echo off rem con

Re: [Freedos-user] VirtualBox and FTP

2014-08-25 Thread Mateusz Viste
Hi, Might be that the DHCP implementation of VirtualBox is incompatible with the DHCP client embedded in Watt32... A PCAP capture might show more, although not sure if there is any point, since watt32 probably won't be updated/fixed any time soon. About some programs needing a fixed IP: yes, t

Re: [Freedos-user] VirtualBox and FTP

2014-08-25 Thread Ulrich
Am 22.08.2014 um 00:47 schrieb Ulrich : > As the guest is connected through NAT, he can also do network operations like > "FDNPKG update". I just tried that and "FDNPKG update" still doesn't work. This seems to be caused by WATTCP. WATTCP.CFG has the line my_ip = DHCP so it should get the s

Re: [Freedos-user] VirtualBox and FTP

2014-08-21 Thread Mateusz Viste
>Just use passive mode >connections >and you'll be fine. It's exactly the other way around ;) Ulrich has its server behind a masquerading PAT, not the client. So ACTIVE mode is what should work, IF its ftp client is smart enough to ignore the IP presented by the server in the control channel

Re: [Freedos-user] VirtualBox and FTP

2014-08-21 Thread Ulrich
Am 21.08.2014 um 22:47 schrieb Michael B. Brutman : > I am a little late in responding; moving an entire house of belongings > and children is not fun. Wow, best wishes! We are looking for a new house at the moment, so this is something that might happen to our family too, sooner or later. >

Re: [Freedos-user] VirtualBox and FTP

2014-08-21 Thread Michael B. Brutman
I am a little late in responding; moving an entire house of belongings and children is not fun. Mateusz provided a good explanation - it is "active" vs. "passive" mode connections. Back 15 years ago before NAT was in widespread use all FTP connections were "active." The client would initiate

Re: [Freedos-user] VirtualBox and FTP

2014-08-20 Thread Ulrich
Hi Mateusz, Am 20.08.2014 um 08:23 schrieb Mateusz Viste : > If your client is behind NAT, the ACTIVE mode will not work without > special hacks, because the server won't be able to reach the client. > If your server is behind NAT, then it's PASSIVE mode that won't work, > because your server w

Re: [Freedos-user] VirtualBox and FTP

2014-08-19 Thread Mateusz Viste
Hi, FTP is a nasty protocol, that never should have existed in the first place... But once it's done, it's impossible to get rid of it, unfortunatly. The problem is that FTP is an out-of-band protocol, meaning it separates data and control in two different channels (aka connections). There are

Re: [Freedos-user] VirtualBox

2013-03-24 Thread john s wolter
Cheers, John S Wolter > Dunno about the future. Honestly, most people probably would just > throw it all away instead of trying hard to emulate it (which is > tricky). If it's something they don't use (or sell or support), they > don't care. :-( > I'm more upbeat about

Re: [Freedos-user] VirtualBox

2013-03-23 Thread Rugxulo
Hi, On Sat, Mar 23, 2013 at 3:32 PM, john s wolter wrote: > >> It's never going to be full speed nor perfect emulation. > > I'm aware an application running on FreeDOS inside of VirtualBox has to be > much slower. That said, understand the future of most legacy operating > systems that ran on ol

Re: [Freedos-user] VirtualBox

2013-03-23 Thread john s wolter
Rugxulo, It's never going to be full speed nor perfect emulation. It's too > tricky to emulate everything (esp. pmode). Anything to do with > segmentation is probably lower priority (due to complexity and > deprecation) than the bare minimum (686-ish pmode) that *nix and > Windows require. > I'm

Re: [Freedos-user] VirtualBox

2013-03-23 Thread Rugxulo
Hi, On Sat, Mar 23, 2013 at 11:11 AM, john s wolter wrote: > > I've been using VirtualBox in Windows 7 on a Sony Vaio Duo Core /w 4 > gigabytes of RAM. VirtualBox's load times are okay but the execution of > MS-DOS & a particular character-display application program is usable very > but slow. I

Re: [Freedos-user] VirtualBox

2013-03-23 Thread john s wolter
I've been using VirtualBox in Windows 7 on a Sony Vaio Duo Core /w 4 gigabytes of RAM. VirtualBox's load times are okay but the execution of MS-DOS & a particular character-display application program is usable very but slow. Understanding this issue is best approached by examining VirtualBox and

Re: [Freedos-user] VirtualBox FreeDOS HowTo

2012-01-16 Thread Jim Hall
>> 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 > That looks great, you've done an awesome job

Re: [Freedos-user] VirtualBox FreeDOS HowTo

2012-01-11 Thread Bernd Blaauw
Op 11-1-2012 0:58, Ulrich Hansen schreef: > 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 That looks

Re: [Freedos-user] VirtualBox troubles

2008-06-23 Thread Larry
; > Subject: Re: [Freedos-user] VirtualBox troubles > To: freedos-user@lists.sourceforge.net > Date: Monday, June 23, 2008, 8:42 AM > Larry escreveu: > > I run freedos in vmware. > > I use it sometimes. The only problem is that graphics mo

Re: [Freedos-user] VirtualBox troubles

2008-06-23 Thread Giorgos
> > Interesting! > What version exactly are you using? I tried CTMOUSE v2.1 beta and it > definetely doesn't work. Then I switched to the version 1.9 final, and it > works like a charm :-) > Hi! :-) I'm using ctmouse v2.0a4 (from sf.net project dl page). I tried also the latest updates that E

Re: [Freedos-user] VirtualBox troubles

2008-06-23 Thread Alain M.
Larry escreveu: > I run freedos in vmware. I use it sometimes. The only problem is that graphics mode is vry slow. Alain - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services

Re: [Freedos-user] VirtualBox troubles

2008-06-23 Thread Eric Auer
Hi Japheth, > Both problems with the keyboard and the mouse are known and were > already posted in this list. However, the posts were related to Qemu > ... Since VirtualBox is - to a large degree - a clone of Qemu... > There exist workarounds. The Ctmouse problem can be cured by using > a certai

Re: [Freedos-user] VirtualBox troubles

2008-06-22 Thread Jim Hall
On Sat, Jun 21, 2008 at 10:26 AM, Mateusz Viste <[EMAIL PROTECTED]> wrote: > Hi folks! > > I'm trying to get rid of my "DOS Machine" (I have a PC which I use only for > FreeDOS) by moving all my FreeDOS files to a VirtualBox machine on my Linux > computer. > Unfortunately, I'm experiencing some t

Re: [Freedos-user] VirtualBox troubles

2008-06-22 Thread Japheth
Both problems with the keyboard and the mouse are known and were already posted in this list. However, the posts were related to Qemu, not VirtualBox. Since VirtualBox is - to a large degree - a clone of Qemu, the issues occur with this virtualizer as well. There exist workarounds. The Ctmouse

Re: [Freedos-user] VirtualBox troubles

2008-06-22 Thread Mateusz Viste
On Saturday 21 June 2008, Giorgos wrote: > Personally speaking, I switched to vbox (from vmware server). > I didn't had so far, any ctmouse2 conflicts. Interesting! What version exactly are you using? I tried CTMOUSE v2.1 beta and it definetely doesn't work. Then I switched to the version 1.9 fin

Re: [Freedos-user] VirtualBox troubles

2008-06-21 Thread Giorgos
> > Has anybody tried to run FreeDOS in such environment? What kind of troubles > d'you got? Have you resolved any? How? > > bye! > Mateusz Viste Hi Mateusz! :-) Personally speaking, I switched to vbox (from vmware server). I didn't had so far, any ctmouse2 conflicts. Although with vbox I'm e

Re: [Freedos-user] VirtualBox troubles

2008-06-21 Thread Larry
I tried the mouse (after install ctmouse) in my freedos vmware install. It seemed to work fine, as well as did the cursor keys. I've heard that virtualbox might take a bit more tuning that vmware, so I bet you'll get it to work fine if you play with it. --- On Sat, 6/21/08, Mateusz Viste <[EMA

Re: [Freedos-user] VirtualBox troubles

2008-06-21 Thread Larry
I run freedos in vmware. I've not tried it in virtualbox. I'm running mostly small apps, a forth compiler I wrote, the Microsoft Quick Pascal compiler, the Microsoft Quick C compiler. No keyboard problems I'm aware of. I'm not sure I've tried the mouse. Let me give it a whirl. --- On Sat,