Re: [Freedos-user] Cobalt OS 1.2

[Don Flowers]

This  works best, but requires UMBM.EXE from the last release of UMBPCI and
I don't know what your distro restrictions are
5?DEVICE=C:\FDOS\BIN\UMBM.EXE
5?DEVICE=C:\FDOS\BIN\JEMMEX.EXE X=TEST I=TEST NOVME NOINVLPG FRAME=NONE
DOS=HIGH,UMB
DOSDATA=HIGH
SHELLHIGH=(you get  the idea.)
After everything loads I have 622K + 32MB

On Thu, May 19, 2016 at 3:48 PM, Don Flowers  wrote:

>
> This one works (not perfectly, but doesn't hang) on my 2 least JEMMEX
> friendly machines,
> DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
>
> On Thu, May 19, 2016 at 3:38 PM, Corbin Davenport  wrote:
>
>> > How are you detecting VBox?
>>
>> I'm using a program called RBPCI
>>  to scan all devices connected
>> to whatever machine the Cobalt setup is running on. During setup, it uses
>> RBPCI to scan for a device with a DeviceID of "BEEF" - which is the
>> VirtualBox display driver.
>>
>> > What programs break? I'm not denying the possibility, but turning off
>> VT-X makes things much much slower. I honestly wouldn't turn it off for all
>> programs, by default.
>>
>> The biggest culprit I found was Windows 3.x.
>>
>> > File sharing? Good luck! Outside of VMSMOUNT (VMware specific), I'm
>> not aware of any others. Perhaps you can use FTPSRV?
>>
>> Pretty much. I'm hoping something like this guide
>> 
>> will work, and I can configure Cobalt to show the IP address of the server
>> at startup for easily connecting. Also thanks for letting me know about
>> VMSMOUNT, I had no idea that existed!
>>
>> > I would recommend that on  the Boot to command line option, that
>> HIMEMX should replace JEMMEX (two of my computer's are hanging on your
>> JEMMEX config [check our Jerome's command line, it works]), and also bypass
>> blackout and break off so the user can see what is happening. and maybe
>> include DEVLOAD so the CDROM can be loaded after a successful boot to the
>> command line.
>>
>> What JEMMEX config would you think works the best?
>>
>> Corbin 
>>
>> On Thu, May 19, 2016 at 8:24 AM, Don Flowers  wrote:
>>
>>> Hi Corbin,
>>> I would recommend that on  the Boot to command line option, that HIMEMX
>>> should replace JEMMEX (two of my computer's are hanging on your JEMMEX
>>> config [check our Jerome's command line, it works]), and also bypass
>>> blackout and break off so the user can see what is happening. and maybe
>>> include DEVLOAD so the CDROM can be loaded after a successful boot to the
>>> command line.
>>>
>>> On Thu, May 19, 2016 at 1:19 AM, Rugxulo  wrote:
>>>
 Hi,

 I have not tested it, but 

 On May 18, 2016 10:22 PM, "Corbin Davenport"  wrote:
 >
 > A few months ago I posted here about my new FreeDOS
 > distribution aimed at beginner DOS users, named Cobalt.
 >
 > - VirtualBox is now fully supported. Right now Cobalt can detect
 > if it is running under VirtualBox, and suggests the user disable
 > the VT-x/AMD-V virtualization feature that breaks a lot of DOS
 > programs. In the future, I'm going to try and extend this to
 > some form of file sharing.

 1). How are you detecting VBox?

 2). What programs break? I'm not denying the possibility, but turning
 off VT-X makes things much much slower. I honestly wouldn't turn it off for
 all programs, by default.

 3). File sharing? Good luck! Outside of VMSMOUNT (VMware specific), I'm
 not aware of any others. Perhaps you can use FTPSRV?


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


>>>
>>>
>>> --
>>> 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] Cobalt OS 1.2

[Don Flowers]

This one works (not perfectly, but doesn't hang) on my 2 least JEMMEX
friendly machines,
DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG

On Thu, May 19, 2016 at 3:38 PM, Corbin Davenport  wrote:

> > How are you detecting VBox?
>
> I'm using a program called RBPCI 
> to scan all devices connected to whatever machine the Cobalt setup is
> running on. During setup, it uses RBPCI to scan for a device with a
> DeviceID of "BEEF" - which is the VirtualBox display driver.
>
> > What programs break? I'm not denying the possibility, but turning off
> VT-X makes things much much slower. I honestly wouldn't turn it off for all
> programs, by default.
>
> The biggest culprit I found was Windows 3.x.
>
> > File sharing? Good luck! Outside of VMSMOUNT (VMware specific), I'm not
> aware of any others. Perhaps you can use FTPSRV?
>
> Pretty much. I'm hoping something like this guide
> 
> will work, and I can configure Cobalt to show the IP address of the server
> at startup for easily connecting. Also thanks for letting me know about
> VMSMOUNT, I had no idea that existed!
>
> > I would recommend that on  the Boot to command line option, that HIMEMX
> should replace JEMMEX (two of my computer's are hanging on your JEMMEX
> config [check our Jerome's command line, it works]), and also bypass
> blackout and break off so the user can see what is happening. and maybe
> include DEVLOAD so the CDROM can be loaded after a successful boot to the
> command line.
>
> What JEMMEX config would you think works the best?
>
> Corbin 
>
> On Thu, May 19, 2016 at 8:24 AM, Don Flowers  wrote:
>
>> Hi Corbin,
>> I would recommend that on  the Boot to command line option, that HIMEMX
>> should replace JEMMEX (two of my computer's are hanging on your JEMMEX
>> config [check our Jerome's command line, it works]), and also bypass
>> blackout and break off so the user can see what is happening. and maybe
>> include DEVLOAD so the CDROM can be loaded after a successful boot to the
>> command line.
>>
>> On Thu, May 19, 2016 at 1:19 AM, Rugxulo  wrote:
>>
>>> Hi,
>>>
>>> I have not tested it, but 
>>>
>>> On May 18, 2016 10:22 PM, "Corbin Davenport"  wrote:
>>> >
>>> > A few months ago I posted here about my new FreeDOS
>>> > distribution aimed at beginner DOS users, named Cobalt.
>>> >
>>> > - VirtualBox is now fully supported. Right now Cobalt can detect
>>> > if it is running under VirtualBox, and suggests the user disable
>>> > the VT-x/AMD-V virtualization feature that breaks a lot of DOS
>>> > programs. In the future, I'm going to try and extend this to
>>> > some form of file sharing.
>>>
>>> 1). How are you detecting VBox?
>>>
>>> 2). What programs break? I'm not denying the possibility, but turning
>>> off VT-X makes things much much slower. I honestly wouldn't turn it off for
>>> all programs, by default.
>>>
>>> 3). File sharing? Good luck! Outside of VMSMOUNT (VMware specific), I'm
>>> not aware of any others. Perhaps you can use FTPSRV?
>>>
>>>
>>> --
>>> 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
>>>
>>>
>>
>>
>> --
>> 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
>>
>>
>
>
> --
> 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 

Re: [Freedos-user] Cobalt OS 1.2

[Corbin Davenport]

> How are you detecting VBox?

I'm using a program called RBPCI 
to scan all devices connected to whatever machine the Cobalt setup is
running on. During setup, it uses RBPCI to scan for a device with a
DeviceID of "BEEF" - which is the VirtualBox display driver.

> What programs break? I'm not denying the possibility, but turning off
VT-X makes things much much slower. I honestly wouldn't turn it off for all
programs, by default.

The biggest culprit I found was Windows 3.x.

> File sharing? Good luck! Outside of VMSMOUNT (VMware specific), I'm not
aware of any others. Perhaps you can use FTPSRV?

Pretty much. I'm hoping something like this guide
 will
work, and I can configure Cobalt to show the IP address of the server at
startup for easily connecting. Also thanks for letting me know about
VMSMOUNT, I had no idea that existed!

> I would recommend that on  the Boot to command line option, that HIMEMX
should replace JEMMEX (two of my computer's are hanging on your JEMMEX
config [check our Jerome's command line, it works]), and also bypass
blackout and break off so the user can see what is happening. and maybe
include DEVLOAD so the CDROM can be loaded after a successful boot to the
command line.

What JEMMEX config would you think works the best?

Corbin 

On Thu, May 19, 2016 at 8:24 AM, Don Flowers  wrote:

> Hi Corbin,
> I would recommend that on  the Boot to command line option, that HIMEMX
> should replace JEMMEX (two of my computer's are hanging on your JEMMEX
> config [check our Jerome's command line, it works]), and also bypass
> blackout and break off so the user can see what is happening. and maybe
> include DEVLOAD so the CDROM can be loaded after a successful boot to the
> command line.
>
> On Thu, May 19, 2016 at 1:19 AM, Rugxulo  wrote:
>
>> Hi,
>>
>> I have not tested it, but 
>>
>> On May 18, 2016 10:22 PM, "Corbin Davenport"  wrote:
>> >
>> > A few months ago I posted here about my new FreeDOS
>> > distribution aimed at beginner DOS users, named Cobalt.
>> >
>> > - VirtualBox is now fully supported. Right now Cobalt can detect
>> > if it is running under VirtualBox, and suggests the user disable
>> > the VT-x/AMD-V virtualization feature that breaks a lot of DOS
>> > programs. In the future, I'm going to try and extend this to
>> > some form of file sharing.
>>
>> 1). How are you detecting VBox?
>>
>> 2). What programs break? I'm not denying the possibility, but turning off
>> VT-X makes things much much slower. I honestly wouldn't turn it off for all
>> programs, by default.
>>
>> 3). File sharing? Good luck! Outside of VMSMOUNT (VMware specific), I'm
>> not aware of any others. Perhaps you can use FTPSRV?
>>
>>
>> --
>> 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
>>
>>
>
>
> --
> 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
>
>
--
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] Cobalt OS 1.2

[Don Flowers]

Hi Corbin,
I would recommend that on  the Boot to command line option, that HIMEMX
should replace JEMMEX (two of my computer's are hanging on your JEMMEX
config [check our Jerome's command line, it works]), and also bypass
blackout and break off so the user can see what is happening. and maybe
include DEVLOAD so the CDROM can be loaded after a successful boot to the
command line.

On Thu, May 19, 2016 at 1:19 AM, Rugxulo  wrote:

> Hi,
>
> I have not tested it, but 
>
> On May 18, 2016 10:22 PM, "Corbin Davenport"  wrote:
> >
> > A few months ago I posted here about my new FreeDOS
> > distribution aimed at beginner DOS users, named Cobalt.
> >
> > - VirtualBox is now fully supported. Right now Cobalt can detect
> > if it is running under VirtualBox, and suggests the user disable
> > the VT-x/AMD-V virtualization feature that breaks a lot of DOS
> > programs. In the future, I'm going to try and extend this to
> > some form of file sharing.
>
> 1). How are you detecting VBox?
>
> 2). What programs break? I'm not denying the possibility, but turning off
> VT-X makes things much much slower. I honestly wouldn't turn it off for all
> programs, by default.
>
> 3). File sharing? Good luck! Outside of VMSMOUNT (VMware specific), I'm
> not aware of any others. Perhaps you can use FTPSRV?
>
>
> --
> 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
>
>
--
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] Cobalt OS 1.2

[Rugxulo]

Hi,

I have not tested it, but 

On May 18, 2016 10:22 PM, "Corbin Davenport"  wrote:
>
> A few months ago I posted here about my new FreeDOS
> distribution aimed at beginner DOS users, named Cobalt.
>
> - VirtualBox is now fully supported. Right now Cobalt can detect
> if it is running under VirtualBox, and suggests the user disable
> the VT-x/AMD-V virtualization feature that breaks a lot of DOS
> programs. In the future, I'm going to try and extend this to
> some form of file sharing.

1). How are you detecting VBox?

2). What programs break? I'm not denying the possibility, but turning off
VT-X makes things much much slower. I honestly wouldn't turn it off for all
programs, by default.

3). File sharing? Good luck! Outside of VMSMOUNT (VMware specific), I'm not
aware of any others. Perhaps you can use FTPSRV?
--
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

[Freedos-user] Cobalt OS 1.2

[Corbin Davenport]

A few months ago I posted here about my new FreeDOS distribution aimed at
beginner DOS users, named Cobalt. Today I released Cobalt OS 1.2, and I
wanted to share the most exciting new changes.

- VirtualBox is now fully supported. Right now Cobalt can detect if it is
running under VirtualBox, and suggests the user disable the VT-x/AMD-V
virtualization feature that breaks a lot of DOS programs. In the future,
I'm going to try and extend this to some form of file sharing.

- Support for Windows 3.0, 3.1, and 3.11. Cobalt detects if Windows is
installed, and if so, tells the user they can use the 'RUNWIN' command to
start Windows. The runwin command is basically a batch file to run the DOSX
executable directly, since win.com has issues on FreeDOS.

- Greatly improved the installer to support repairing an existing
installation of Cobalt. And as always, you can 'upgrade' to Cobalt from an
existing installation of MS-DOS/FreeDOS without losing any files.

- Cobalt has switched to JEMMEX for memory management.

That's pretty much it, feel free to check out the GitHub project
 to download
the disc image. I would love to hear any feedback you might have.

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