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

[Rugxulo]

Hi, thanks for the response!

On Mon, May 16, 2016 at 11:17 PM, Kenneth Davis  wrote:
> On Sun, May 15, 2016 at 6:10 PM, Rugxulo  wrote:
>>
>> I notice that there is seemingly one bug / regression
>
> Try http://www.fdos.org/kernel/testing/truename/KERNEL.SYS

Using this one, everything seems fine (although more testing needed is
always a given).

--
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.2 - Preview 17

[Kenneth Davis]

On Sun, May 15, 2016 at 6:10 PM, Rugxulo  wrote:
> Hi again,
...
> I notice that there is seemingly one bug / regression, otherwise all
> my "tests" (MetaDOS) seem to work fine. (I assume Jeremy will notice
> this and that I don't have to file a separate bug report or email him
> privately. If not, I'll try to remember later.)
>
> In an attempt to not load the RAM driver over and over again, I had a
> naive "if exist %RAMDRIVE%:\nul goto end" inside the actual
> RAMDRIVE.BAT file (which is called by autoexec).
>
...

Try http://www.fdos.org/kernel/testing/truename/KERNEL.SYS
I have to revisit commit r1724 which was to fix an issue opening
character devices with bad paths as it is the cause of this issue.
Thank you for the testing and report with details for me to duplicate.

Jeremy

--
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.2 - Preview 17

[Rugxulo]

Hi again,

On Sun, May 15, 2016 at 3:47 PM, Jerome Shidel  wrote:
>> On May 15, 2016, at 4:19 PM, Rugxulo  wrote:
>>> On May 11, 2016, at 11:11 PM, perditi...@gmail.com wrote:
>>>
>>> Kernel update is forthcoming.
>>> I still need to run some tests and make 386+ builds, but updated
>>> packages will be available at
>>> http://www.fdos.org/kernel/release/LATEST/fdpkg/ and release builds
>>> uploaded to SF.
>>
>> Uh, it doesn't work. Any attempt to download the 2042 files from
>> SF.net fails with an error message.
>
> I had no problem downloading them from the provided link. Also, put them into 
> FDI - P19 that I released earlier today.

Okay, I just grabbed it from above (and not SF.net).

I notice that there is seemingly one bug / regression, otherwise all
my "tests" (MetaDOS) seem to work fine. (I assume Jeremy will notice
this and that I don't have to file a separate bug report or email him
privately. If not, I'll try to remember later.)

In an attempt to not load the RAM driver over and over again, I had a
naive "if exist %RAMDRIVE%:\nul goto end" inside the actual
RAMDRIVE.BAT file (which is called by autoexec).

That no longer works. Apparently it's even getting confused about
drives since "\tmp" already exists on boot drive. "if exist g:\tmp\nul
echo Yup!" succeeds (as does "q:" or "z:" or anything else, which is
way past my setting for LASTDRIVE). Same with "a:\extras" or
"a:\system" or "a:\network".

So "A:\> if exist z:\network\nul echo Yup!" says "Yup!" when it
shouldn't (because "a:\network" exists). But "if exist z:\netwrk\nul
echo Yup!" still fails (as it should).

--
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.2 - Preview 17

[Rugxulo]

Hi,

On Sun, May 15, 2016 at 10:24 AM, Jerome E. Shidel Jr.
 wrote:
>
> On May 11, 2016, at 11:11 PM, perditi...@gmail.com wrote:
> [..]
>
> Kernel update is forthcoming.
> I still need to run some tests and make 386+ builds, but updated
> packages will be available at
> http://www.fdos.org/kernel/release/LATEST/fdpkg/ and release builds
> uploaded to SF.
>
> Jeremy
>
>
> I just realized it was available.
>
> So, even though I pushed FDI Preview 18 last night…
>
> I took a few seconds, and Preview 19 is now out the door. It uses and
> installs 2042.

Uh, it doesn't work. Any attempt to download the 2042 files from
SF.net fails with an error message.

--
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.2 - Preview 17

[Jerome E. Shidel Jr.]

:-)

> On May 11, 2016, at 11:11 PM, perditi...@gmail.com wrote:
> [..]
> Kernel update is forthcoming.
> I still need to run some tests and make 386+ builds, but updated
> packages will be available at
> http://www.fdos.org/kernel/release/LATEST/fdpkg/ 
>  and release builds
> uploaded to SF.
> 
> Jeremy

I just realized it was available.

So, even though I pushed FDI Preview 18 last night…

I took a few seconds, and Preview 19 is now out the door. It uses and installs 
2042.

Unrelated to 2042, with the additional sources in some of the other packages. I 
had to stop
installing a couple things due running out of space on the 32MB USB stick. I 
picked not to 
install MTCP, WGET and VMSMOUNT. They are still included on the Big USB and 
CD-ROM
images as uninstalled EXTRAS. Either the USB stick had to grow or something had 
to go.

Jerome--
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.2 - Preview 17

[perditionc]

On Sat, May 7, 2016 at 10:02 AM, Don Flowers  wrote:
>>Other than Package and Package Data updates, no further updates are
>>planned for FDI before FreeDOS 1.2 Final.
>
> No KERNEL update?
>
> On Sat, May 7, 2016 at 9:55 AM, Jerome E. Shidel Jr. 
> wrote:
>>
>> Hello all,
>>
>> I have just released Preview 17, http://up.lod.bz/FDI
>>
>> This release contains:
>>
>> * Minor package and data updates.
>> * Some internal improvements.
>> * Some VirtualBox compatibility updates.
>> * USB versions include FDIDEV.BAT to aid in
>>   replicating the FDI Build Environment.
>>
>> Other than Package and Package Data updates, no further updates are
>> planned for FDI before FreeDOS 1.2 Final.
>>
>> Thanks, Jerome
>>


Kernel update is forthcoming.
I still need to run some tests and make 386+ builds, but updated
packages will be available at
http://www.fdos.org/kernel/release/LATEST/fdpkg/ and release builds
uploaded to SF.

Jeremy

--
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.2 - Preview 17

[Jerome E. Shidel Jr.]

> On May 7, 2016, at 8:43 PM, Corbin Davenport  wrote:
> 
> Thanks for the explanation, that was very interesting! However, I will say 
> that I haven't had any issues with El Torito under VirtualBox. I am currently 
> developing a FreeDOS distribution called Cobalt 
> , and the installer CD uses El 
> Torito. Granted, I'm using FreeDOS 1.1 with my own custom installer, so I 
> can't say if it's an issue with either FreeDOS 1.2 or FDI.

Like I said. The only thing I know for a fact regarding the issue is that it is 
not FDI or V8Power Tools.

Take the existing Floppy Image that FDI uses to boot. 

Lets assume partitioned and blank formatted drive C:

Modify the auto exec to jumping past FDI’s startup after the drivers 
finish loading.
Thereby avoiding any calls to any part of FDI and any usage of V8Power 
Tools.

Run FreeDOS Edit (from prompt):

A:  (fine)
A:\FDSETUP\BIN\EDIT.EXE (fine)
C:  (fine)
A:\FDSETUP\BIN\EDIT.EXE   (fine)
D:  (fine)
A:\FDSETUP\BIN\EDIT.EXE   (system lockup)

What is odd though the system does not lockup when using the DIR 
command.

for example:

A:
dir
c:
dir:
d:
dir
cd util
dir
type d:\pkginfo\command.txt
(no problems)

This is not a program problem. This also cause lockup:

grep -i dos d:\pkginfo\command.com

So, as far as I can determine it is either a VirtualBox, FreeCOM, 
Kernel or the CDROM driver. However,
the issue occurs only from programs and not the built in shell 
commands. Also, it only occurs in VirtualBox
when booting the El Torito CD. It does not occur in VMware when booting 
the CD-ROM. It also does not 
occur under VirtualBox using any other boot method. This includes not 
happening when the same floppy
image is used to boot as a floppy.








--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

[Corbin Davenport]

Yep, Cobalt is essentially the final stable release that never happened
with the Carbon OS project. It still has the same goal of making DOS as
easy to use as possible for new users, and I'm super excited for the
upcoming 1.2 release :)

Corbin
On 8 May 2016 6:24 a.m., "Don Flowers"  wrote:

> Corbin,
> Your Cobalt seems familiar;  did you take over the CarbonOS project?
> I am looking forward to the finished product :^)
>
> On Sat, May 7, 2016 at 8:43 PM, Corbin Davenport  wrote:
>
>> Thanks for the explanation, that was very interesting! However, I will
>> say that I haven't had any issues with El Torito under VirtualBox. I am
>> currently developing a FreeDOS distribution called Cobalt
>> , and the installer CD uses
>> El Torito. Granted, I'm using FreeDOS 1.1 with my own custom installer, so
>> I can't say if it's an issue with either FreeDOS 1.2 or FDI.
>>
>> Corbin 
>>
>> On Sat, May 7, 2016 at 6:20 PM, Alain Mouette  wrote:
>>
>>> This disks boots well under VirtualBox (and any machine that I have seen
>>> so far...)
>>> http://suporte.cosmodata.com.br/downloads/moni/CosmoData-M16012.iso
>>>
>>> If you care to have a look, I hope that it helps...
>>>
>>> Sorry, it is in portuguese. And there is a comercial program in it (it
>>> has a password) use it for test only
>>>
>>> what I could no do is find a CD driver that works everywhere :(
>>> my simple fix was to increase the size of drive A: so that everything
>>> that I nedd fits in it.
>>>
>>> Alain
>>>
>>>
>>> On 07-05-2016 18:38, Jerome E. Shidel Jr. wrote:
>>> > Hello Corbin,
>>> >
>>> >> I'm really curious about the VirtualBox compatibility fixes, was
>>> there any major changes?
>>> >> Corbin
>>> >>
>>> > Simple answer:
>>> >
>>> > Not really. :-)
>>> >
>>> > Long answer:
>>> >
>>> > The changes only effect VirtualBox. Real hardware and other Virtual
>>> Machines are unchanged.
>>> >
>>> > Really, really, really long answer:
>>> >
>>> > Basically, there were two issues with compatibility in VirtualBox.
>>> Neither, were bugs or problems in FDI or any of the utilities it relies
>>> upon. The first issue was the installed FDCONFIG.SYS default option 1 would
>>> cause the virtual machine to crash when loading JEMM. The second issue
>>> sprung up when creating a El Torito Boot CD. Basically, when booting even a
>>> stripped down version FreeDOS (more or less only the Kernel, FreeCOM and CD
>>> Driver), any program that would access the CD portion of the media caused
>>> VirtualBox to lockup.
>>> >
>>> > So, here was the solution.
>>> >
>>> > I added VirtualBox detection to the V8Power Tools vinfo utility. It
>>> already detects CPUs from 8086-80686, DOSBox, QEMU and general emulation. I
>>> added VirtualBox and VMware to it. I planned adding this detector since
>>> about Preview 13, I just finally got around to doing it.
>>> >
>>> > Next, the logic that creates the FDCONFIG.SYS file was already setup
>>> in Preview 16 to change the installed Default choice to Option 2. It was
>>> only waiting on the vinfo utility.
>>> >
>>> > Finally, there is no way to make the El Torito CD work under
>>> VirtualBox at present. This is not an issue with FDI. But, having the
>>> installer lockup part of the way into the process (when it access the CD
>>> portion) would create a very bad user experience. So, I made the best
>>> compromise I could. Under VirtualBox, if you boot the CD, the installer UI
>>> is never seen. You get a message telling you that it won’t work and to use
>>> one of the other installation media and a command prompt. Not perfect, but
>>> the best solution at present. This only is an issue under VirtualBox when
>>> booting the from the CD. No other virtual machine platforms exhibit this
>>> issue. No other method on VirtualBox does either. There is only one version
>>> of FDI for all media and it uses the same utilities. I’m not pointing a
>>> finger at VirtualBox. But, it is the primary suspect for the problem.
>>> >
>>> > Regardless of all of that, I have switched building of the FDI
>>> previews over to using VirtualBox. Originally, I was building them in
>>> VMware. But, VirtualBox is about 5 times faster in the build process. To
>>> build a release under VMware took about 15 minutes. Under VirtualBox about
>>> 3. The occasional rebuild of all of the package data information files used
>>> by FDIMPLES took about 90 minutes. Now, under VirtualBox 15 minutes.
>>> >
>>> > Thanks, Jerome
>>> >
>>> >
>>> >
>>> --
>>> > Find and fix application performance issues faster with Applications
>>> Manager
>>> > Applications Manager provides deep performance insights into multiple
>>> tiers of
>>> > your business applications. It resolves application problems quickly
>>> and
>>> > reduces your MTTR. Get your free trial!
>>> > 

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

[Corbin Davenport]

Thanks for the explanation, that was very interesting! However, I will say
that I haven't had any issues with El Torito under VirtualBox. I am
currently developing a FreeDOS distribution called Cobalt
, and the installer CD uses El
Torito. Granted, I'm using FreeDOS 1.1 with my own custom installer, so I
can't say if it's an issue with either FreeDOS 1.2 or FDI.

Corbin 

On Sat, May 7, 2016 at 6:20 PM, Alain Mouette  wrote:

> This disks boots well under VirtualBox (and any machine that I have seen
> so far...)
> http://suporte.cosmodata.com.br/downloads/moni/CosmoData-M16012.iso
>
> If you care to have a look, I hope that it helps...
>
> Sorry, it is in portuguese. And there is a comercial program in it (it
> has a password) use it for test only
>
> what I could no do is find a CD driver that works everywhere :(
> my simple fix was to increase the size of drive A: so that everything
> that I nedd fits in it.
>
> Alain
>
>
> On 07-05-2016 18:38, Jerome E. Shidel Jr. wrote:
> > Hello Corbin,
> >
> >> I'm really curious about the VirtualBox compatibility fixes, was there
> any major changes?
> >> Corbin
> >>
> > Simple answer:
> >
> > Not really. :-)
> >
> > Long answer:
> >
> > The changes only effect VirtualBox. Real hardware and other Virtual
> Machines are unchanged.
> >
> > Really, really, really long answer:
> >
> > Basically, there were two issues with compatibility in VirtualBox.
> Neither, were bugs or problems in FDI or any of the utilities it relies
> upon. The first issue was the installed FDCONFIG.SYS default option 1 would
> cause the virtual machine to crash when loading JEMM. The second issue
> sprung up when creating a El Torito Boot CD. Basically, when booting even a
> stripped down version FreeDOS (more or less only the Kernel, FreeCOM and CD
> Driver), any program that would access the CD portion of the media caused
> VirtualBox to lockup.
> >
> > So, here was the solution.
> >
> > I added VirtualBox detection to the V8Power Tools vinfo utility. It
> already detects CPUs from 8086-80686, DOSBox, QEMU and general emulation. I
> added VirtualBox and VMware to it. I planned adding this detector since
> about Preview 13, I just finally got around to doing it.
> >
> > Next, the logic that creates the FDCONFIG.SYS file was already setup in
> Preview 16 to change the installed Default choice to Option 2. It was only
> waiting on the vinfo utility.
> >
> > Finally, there is no way to make the El Torito CD work under VirtualBox
> at present. This is not an issue with FDI. But, having the installer lockup
> part of the way into the process (when it access the CD portion) would
> create a very bad user experience. So, I made the best compromise I could.
> Under VirtualBox, if you boot the CD, the installer UI is never seen. You
> get a message telling you that it won’t work and to use one of the other
> installation media and a command prompt. Not perfect, but the best solution
> at present. This only is an issue under VirtualBox when booting the from
> the CD. No other virtual machine platforms exhibit this issue. No other
> method on VirtualBox does either. There is only one version of FDI for all
> media and it uses the same utilities. I’m not pointing a finger at
> VirtualBox. But, it is the primary suspect for the problem.
> >
> > Regardless of all of that, I have switched building of the FDI previews
> over to using VirtualBox. Originally, I was building them in VMware. But,
> VirtualBox is about 5 times faster in the build process. To build a release
> under VMware took about 15 minutes. Under VirtualBox about 3. The
> occasional rebuild of all of the package data information files used by
> FDIMPLES took about 90 minutes. Now, under VirtualBox 15 minutes.
> >
> > Thanks, Jerome
> >
> >
> >
> --
> > Find and fix application performance issues faster with Applications
> Manager
> > Applications Manager provides deep performance insights into multiple
> tiers of
> > your business applications. It resolves application problems quickly and
> > reduces your MTTR. Get your free trial!
> > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> > ___
> > Freedos-user mailing list
> > Freedos-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
>
> --
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> Freedos-user mailing list
> 

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

[Alain Mouette]

This disks boots well under VirtualBox (and any machine that I have seen 
so far...)
http://suporte.cosmodata.com.br/downloads/moni/CosmoData-M16012.iso

If you care to have a look, I hope that it helps...

Sorry, it is in portuguese. And there is a comercial program in it (it 
has a password) use it for test only

what I could no do is find a CD driver that works everywhere :(
my simple fix was to increase the size of drive A: so that everything 
that I nedd fits in it.

Alain


On 07-05-2016 18:38, Jerome E. Shidel Jr. wrote:
> Hello Corbin,
>
>> I'm really curious about the VirtualBox compatibility fixes, was there any 
>> major changes?
>> Corbin
>>
> Simple answer:
>
> Not really. :-)
>
> Long answer:
>
> The changes only effect VirtualBox. Real hardware and other Virtual Machines 
> are unchanged.
>
> Really, really, really long answer:
>
> Basically, there were two issues with compatibility in VirtualBox. Neither, 
> were bugs or problems in FDI or any of the utilities it relies upon. The 
> first issue was the installed FDCONFIG.SYS default option 1 would cause the 
> virtual machine to crash when loading JEMM. The second issue sprung up when 
> creating a El Torito Boot CD. Basically, when booting even a stripped down 
> version FreeDOS (more or less only the Kernel, FreeCOM and CD Driver), any 
> program that would access the CD portion of the media caused VirtualBox to 
> lockup.
>
> So, here was the solution.
>
> I added VirtualBox detection to the V8Power Tools vinfo utility. It already 
> detects CPUs from 8086-80686, DOSBox, QEMU and general emulation. I added 
> VirtualBox and VMware to it. I planned adding this detector since about 
> Preview 13, I just finally got around to doing it.
>
> Next, the logic that creates the FDCONFIG.SYS file was already setup in 
> Preview 16 to change the installed Default choice to Option 2. It was only 
> waiting on the vinfo utility.
>
> Finally, there is no way to make the El Torito CD work under VirtualBox at 
> present. This is not an issue with FDI. But, having the installer lockup part 
> of the way into the process (when it access the CD portion) would create a 
> very bad user experience. So, I made the best compromise I could. Under 
> VirtualBox, if you boot the CD, the installer UI is never seen. You get a 
> message telling you that it won’t work and to use one of the other 
> installation media and a command prompt. Not perfect, but the best solution 
> at present. This only is an issue under VirtualBox when booting the from the 
> CD. No other virtual machine platforms exhibit this issue. No other method on 
> VirtualBox does either. There is only one version of FDI for all media and it 
> uses the same utilities. I’m not pointing a finger at VirtualBox. But, it is 
> the primary suspect for the problem.
>
> Regardless of all of that, I have switched building of the FDI previews over 
> to using VirtualBox. Originally, I was building them in VMware. But, 
> VirtualBox is about 5 times faster in the build process. To build a release 
> under VMware took about 15 minutes. Under VirtualBox about 3. The occasional 
> rebuild of all of the package data information files used by FDIMPLES took 
> about 90 minutes. Now, under VirtualBox 15 minutes.
>
> Thanks, Jerome
>
>
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

[Jerome E. Shidel Jr.]

Hello Corbin,

> I'm really curious about the VirtualBox compatibility fixes, was there any 
> major changes?
> Corbin
> 

Simple answer: 

Not really. :-)

Long answer: 

The changes only effect VirtualBox. Real hardware and other Virtual Machines 
are unchanged. 

Really, really, really long answer:

Basically, there were two issues with compatibility in VirtualBox. Neither, 
were bugs or problems in FDI or any of the utilities it relies upon. The first 
issue was the installed FDCONFIG.SYS default option 1 would cause the virtual 
machine to crash when loading JEMM. The second issue sprung up when creating a 
El Torito Boot CD. Basically, when booting even a stripped down version FreeDOS 
(more or less only the Kernel, FreeCOM and CD Driver), any program that would 
access the CD portion of the media caused VirtualBox to lockup. 

So, here was the solution.

I added VirtualBox detection to the V8Power Tools vinfo utility. It already 
detects CPUs from 8086-80686, DOSBox, QEMU and general emulation. I added 
VirtualBox and VMware to it. I planned adding this detector since about Preview 
13, I just finally got around to doing it.

Next, the logic that creates the FDCONFIG.SYS file was already setup in Preview 
16 to change the installed Default choice to Option 2. It was only waiting on 
the vinfo utility.

Finally, there is no way to make the El Torito CD work under VirtualBox at 
present. This is not an issue with FDI. But, having the installer lockup part 
of the way into the process (when it access the CD portion) would create a very 
bad user experience. So, I made the best compromise I could. Under VirtualBox, 
if you boot the CD, the installer UI is never seen. You get a message telling 
you that it won’t work and to use one of the other installation media and a 
command prompt. Not perfect, but the best solution at present. This only is an 
issue under VirtualBox when booting the from the CD. No other virtual machine 
platforms exhibit this issue. No other method on VirtualBox does either. There 
is only one version of FDI for all media and it uses the same utilities. I’m 
not pointing a finger at VirtualBox. But, it is the primary suspect for the 
problem.

Regardless of all of that, I have switched building of the FDI previews over to 
using VirtualBox. Originally, I was building them in VMware. But, VirtualBox is 
about 5 times faster in the build process. To build a release under VMware took 
about 15 minutes. Under VirtualBox about 3. The occasional rebuild of all of 
the package data information files used by FDIMPLES took about 90 minutes. Now, 
under VirtualBox 15 minutes. 

Thanks, Jerome


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

[Corbin Davenport]

I'm really curious about the VirtualBox compatibility fixes, was there any
major changes?

Corbin
On 7 May 2016 9:56 a.m., "Jerome E. Shidel Jr."  wrote:

> Hello all,
>
> I have just released Preview 17, http://up.lod.bz/FDI
>
> This release contains:
>
> * Minor package and data updates.
> * Some internal improvements.
> * Some VirtualBox compatibility updates.
> * USB versions include FDIDEV.BAT to aid in
>   replicating the FDI Build Environment.
>
> Other than Package and Package Data updates, no further updates are
> planned for FDI before FreeDOS 1.2 Final.
>
> Thanks, Jerome
>
>
> --
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

[Jerome E. Shidel Jr.]

Don, 

> No KERNEL update?

The kernel is just another package.

All packages were updated to their latest available version that is available 
on the ibiblio package repository on 4/24/16. Packages that have been updated 
since then have not yet been incorporated. This is partially do to some issues 
with the LSM package data files that need updating. Also, software and packages 
that have newer versions than those on the repository, will not be included. 
Unfortunately, I do not have the time to provide all of those updates. Anyone 
who wishes to see some of those packages updated will need to contact the 
repository maintainer. I obviously can not speak for him. However, I think he 
would appreciate any help he can get in updating those packages.

Thanks, Jerome--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

[Don Flowers]

>Other than Package and Package Data updates, no further updates are
>planned for FDI before FreeDOS 1.2 Final.

No KERNEL update?

On Sat, May 7, 2016 at 9:55 AM, Jerome E. Shidel Jr. 
wrote:

> Hello all,
>
> I have just released Preview 17, http://up.lod.bz/FDI
>
> This release contains:
>
> * Minor package and data updates.
> * Some internal improvements.
> * Some VirtualBox compatibility updates.
> * USB versions include FDIDEV.BAT to aid in
>   replicating the FDI Build Environment.
>
> Other than Package and Package Data updates, no further updates are
> planned for FDI before FreeDOS 1.2 Final.
>
> Thanks, Jerome
>
>
> --
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.2 - Preview 17

[Jerome E. Shidel Jr.]

Hello all, 

I have just released Preview 17, http://up.lod.bz/FDI

This release contains:

* Minor package and data updates.
* Some internal improvements.
* Some VirtualBox compatibility updates.
* USB versions include FDIDEV.BAT to aid in 
  replicating the FDI Build Environment.

Other than Package and Package Data updates, no further updates are
planned for FDI before FreeDOS 1.2 Final.

Thanks, Jerome

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user