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

2016-02-01 Thread 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: "

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

2016-01-12 Thread 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 exis

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

2016-01-08 Thread Rugxulo
Hi, On Thu, Jan 7, 2016 at 7:22 PM, wrote: >> Which VirtualBox? > VBox 5.0.12, 64-bit, host is 64 bit Windows 8.1 I'm still using 4.3.x ("active maintenance") atop Win7 (SP1) 64-bit because I didn't want to be a first-adopter for VBox 5.x and run into a bunch of bugs. Granted, that doesn't mean

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

2016-01-07 Thread Rugxulo
Hi, On Wed, Jan 6, 2016 at 5:15 PM, wrote: > > Hello! Basically, my issue is summarized in the title. "FreeDOS in VirtualBox: Bad or missing command interpreter and keyboard doesn't work" > I have installed a FreeDOS 1.1 install as a VirtualBox guest, Which VirtualBox? 5.x (64-bit)? Atop what

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

2016-01-07 Thread Rugxulo
Hi, On Thu, Jan 7, 2016 at 8:45 AM, Jim Hall wrote: > On Wednesday‎, ‎January‎ ‎6‎, ‎2016 ‎5‎:‎25‎ ‎PM Jim Hall wrote: > >> I wonder if your system installed a CONFIG.SYS file? This is what sets >> the path to the COMMAND.COM shell. Can you boot from the install >> media, drop to a shell, and che

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

2016-01-07 Thread Matt Rienzo
There wasn't an option. If you choose the option to use fdisk to partition the harddisk and keep pressing esc until it drops to a prompt. 73 Matt Rienzo W9ERA B.S.E.E | B.S. Music On Jan 7, 2016 8:46 AM, "Jim Hall" wrote: > On Wednesday‎, ‎January‎ ‎6‎, ‎2016 ‎5‎:‎25‎ ‎PM Jim Hall wrote: > > I

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

2016-01-06 Thread Jim Hall
On Wed, Jan 6, 2016 at 5:15 PM, wrote: > 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,

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

2016-01-06 Thread caswellrienzo
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 a