Re: [Freedos-user] FDI Preview 15, update 2

[Jerome Shidel]

> On Apr 10, 2016, at 12:59 PM, Don Flowers  wrote:
> 
> I just tried an install with FDI-SLiM.img from my GRUB2 boot menu and it was 
> super fast. I forgot to go to the advanced menu (maybe the final should have 
> the options following the language menu?); so my GRUB got wiped but SUPER 
> GRUB DISC fixed that pronto.
> Very cool to do it this way.

Oh, you can switch into advanced mode at the language screen as well.

Actually, into and out of advanced mode anytime FDI is waiting for you to 
choose something. 

However, you need to be in advanced mode when you continue from the welcome 
screen. Otherwise, it assumes the default answers to a question like target 
directory, drive, MBR, formatting  And you'll really only get the option to 
do detailed package selection. Oh, and maybe zip backup if a OS was detected.

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! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Jerome Shidel]

> On Apr 10, 2016, at 12:59 PM, Don Flowers  wrote:
> 
> I just tried an install with FDI-SLiM.img from my GRUB2 boot menu and it was 
> super fast. I forgot to go to the advanced menu (maybe the final should have 
> the options following the language menu?); so my GRUB got wiped but SUPER 
> GRUB DISC fixed that pronto.
> Very cool to do it this way.

:-) FDI normal mode install is definitely quick and easy.  On reasonable 
hardware or a quick VM, it can be under a minute. 

Update on QEMU support.

Well, I had a few minutes today to add some CPU detection to V8. Unfortunately, 
qemu is detected as 486 not 386. So, I will have to figure out a way to 
directly detect it. 

--
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! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Don Flowers]

I just tried an install with FDI-SLiM.img from my GRUB2 boot menu and it
was super fast. I forgot to go to the advanced menu (maybe the final should
have the options following the language menu?); so my GRUB got wiped but
SUPER GRUB DISC fixed that pronto.
Very cool to do it this way.

On Wed, Apr 6, 2016 at 5:38 AM, Jerome E. Shidel Jr. 
wrote:

> Hello,
>
> On Apr 5, 2016, at 12:58 PM, Louis Santillan  wrote:
>
> QEMU supports VNC like VirtualBox and VMware.
>
> http://wiki.qemu.org/download/qemu-doc.html#sec_005finvocation
>
>
> Thanks, I though of trying that and I will do so. However, I know it has
> got to be
> very slow. Also, It may not exhibit the same issue under double
> virtualization.
>
> Anyhow, this is how I have decided to resolve the issue.
>
> I will add some simple and easily understood CPU level testing to the
> vinfo /M.
> This was the idea anyway when I added the DOSBox test. It return
> errorlevel 101
> when running under DOSBox. I had plans to add 1=80186, 2=80286, 3=80306,
> 4=80486 and maybe 586 & 686. So once added, it should return 3 for QEMU
> i386.
> Since that would be extremely rare piece of real hardware, it would be
> acceptable
> for FDI to see a 386 and just skip some of the automatic importing and
> configuration
> things it does during the setup. This would leave the user of a QEMU VM
> and any
> real 386 to manually format and configure partitions on a blank drive.
> But, they
> should be used to doing it.
>
> Now, I just have to find a few minutes to add it to vinfo in the V8Power
> Tools and
> FDI.
>
> Thanks, Jerome.
>
>
> --
>
> ___
> 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! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Jerome E. Shidel Jr.]

Hello, 

> On Apr 5, 2016, at 12:58 PM, Louis Santillan  > wrote:
> 
> QEMU supports VNC like VirtualBox and VMware.
> 
> http://wiki.qemu.org/download/qemu-doc.html#sec_005finvocation 
> 
Thanks, I though of trying that and I will do so. However, I know it has got to 
be
very slow. Also, It may not exhibit the same issue under double virtualization.

Anyhow, this is how I have decided to resolve the issue.

I will add some simple and easily understood CPU level testing to the vinfo /M.
This was the idea anyway when I added the DOSBox test. It return errorlevel 101
when running under DOSBox. I had plans to add 1=80186, 2=80286, 3=80306, 
4=80486 and maybe 586 & 686. So once added, it should return 3 for QEMU i386.
Since that would be extremely rare piece of real hardware, it would be 
acceptable 
for FDI to see a 386 and just skip some of the automatic importing and 
configuration
things it does during the setup. This would leave the user of a QEMU VM and any
real 386 to manually format and configure partitions on a blank drive. But, they
should be used to doing it.

Now, I just have to find a few minutes to add it to vinfo in the V8Power Tools 
and
FDI.

Thanks, Jerome.--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Louis Santillan]

QEMU supports VNC like VirtualBox and VMware.

http://wiki.qemu.org/download/qemu-doc.html#sec_005finvocation

On Tue, Apr 5, 2016 at 7:23 AM, Jerome E. Shidel Jr. 
wrote:

> Hello Don,
>
> > What QEMU version are you using?
> > 2.5.0 for me (I'm on Xubuntu 16.04).
>
> Well, It is a bit of a pain for me to run QEMU.
>
> Basically, I can only run it on my server. It is a 2 x XEON
> 3.0Ghz w/dual core cpus, 36GB RAM and Multi-TB RAID,
> running OpenSUSE Tumbleweed with QEMU 2.4.0.
>
> The painful part is the server boots to and runs at runlevel 3. So, to
> use QEMU I need to STAND at the server and startx to mess around
> with QEMU. When done, rebooting machine.
>
> For some reason, when I ssh into my server from my Mac and run
> QEMU, none the VM’s key codes are all screwed up. Only the QEMU
> VM, not the ssh terminal or remote X session.
>
> So, I don’t know when I will get to mess with figuring out the QEMU
> issue.
>
> Jerome
>
>
>
>
> --
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Jerome E. Shidel Jr.]

Hello Don,

> What QEMU version are you using?
> 2.5.0 for me (I'm on Xubuntu 16.04).

Well, It is a bit of a pain for me to run QEMU.

Basically, I can only run it on my server. It is a 2 x XEON 
3.0Ghz w/dual core cpus, 36GB RAM and Multi-TB RAID, 
running OpenSUSE Tumbleweed with QEMU 2.4.0.

The painful part is the server boots to and runs at runlevel 3. So, to
use QEMU I need to STAND at the server and startx to mess around
with QEMU. When done, rebooting machine. 

For some reason, when I ssh into my server from my Mac and run 
QEMU, none the VM’s key codes are all screwed up. Only the QEMU 
VM, not the ssh terminal or remote X session. 

So, I don’t know when I will get to mess with figuring out the QEMU 
issue.

Jerome



--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Don Flowers]

What QEMU version are you using?
2.5.0 for me (I'm on Xubuntu 16.04).

On Mon, Apr 4, 2016 at 7:08 PM, Jerome E. Shidel Jr. 
wrote:

>
> > On Apr 4, 2016, at 6:13 PM, Rugxulo  wrote:
> >
> > Hi,
> >
> > On Mon, Apr 4, 2016 at 12:28 AM, Jerome E. Shidel Jr. 
> wrote:
> >>
> >> I have tested under QEMU on Linux and have detected the issue and its
> cause.
> >>
> >> It appears to be that SHSURDRV is locking up the system in DOSBox and
> QEMU.
> >> It does not seem to have this issue on the native hardware I’ve tested.
> >
> > Are you sure?
>
> Fairly sure. I noticed that it was the problem under DOSBox. So, I added a
> DOSBox
> detector to V8Power Tools and skip it inside DOSBox. After hearing of the
> issue,
> the issue under QEMU sounded exactly the same. So, went straight to the
> RAM Drive
> creation and skipped it. FDI works fine afterwords. All other external
> utilities that are
> used by FDI are used in may places. So, if one of those was the culprit,
> it would
> exhibit issues elsewhere as well.
>
> HOWEVER, that being said, that does not mean there is a bug in SHSURDRV.
> The problem could be in the kernel, freecom. Or, even possibly in my
> FDITEMP.BAT.
> I have not tested had a chance to fully examine the problem. But, so lar
> it appears
> to be SHSURDRV.
>
> > I often use SHSURDRV (386, XMSv3 version) as RAM drive
> > under QEMU with no problems.
> > Of course, my version is reassembled without the (bloated, unused by
> > me) ZLIB/"GZIP" stuff (so it's only like 6 kb now).
> >
> > What QEMU version are you using?
>
> Don’t know about everyone else. But, I tested it on 2.4.0.
>
> > I think I'm on 2.5.0 at this point,
> > but newer versions are coming soon.
> > (Yeah, some Linux distros, e.g. Ubuntu LTS, still only have older
> > 2.0.0.) I get mine for Win32/64 (precompiled) from
> > http://qemu.weilnetz.de .
> >
> >> Drawbacks of not having the RAM DISK or RAM DISK creation failure:
>
>
>
> --
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Jerome E. Shidel Jr.]

> On Apr 4, 2016, at 6:13 PM, Rugxulo  wrote:
> 
> Hi,
> 
> On Mon, Apr 4, 2016 at 12:28 AM, Jerome E. Shidel Jr.  
> wrote:
>> 
>> I have tested under QEMU on Linux and have detected the issue and its cause.
>> 
>> It appears to be that SHSURDRV is locking up the system in DOSBox and QEMU.
>> It does not seem to have this issue on the native hardware I’ve tested.
> 
> Are you sure?

Fairly sure. I noticed that it was the problem under DOSBox. So, I added a 
DOSBox
detector to V8Power Tools and skip it inside DOSBox. After hearing of the issue,
the issue under QEMU sounded exactly the same. So, went straight to the RAM 
Drive
creation and skipped it. FDI works fine afterwords. All other external 
utilities that are 
used by FDI are used in may places. So, if one of those was the culprit, it 
would 
exhibit issues elsewhere as well.

HOWEVER, that being said, that does not mean there is a bug in SHSURDRV. 
The problem could be in the kernel, freecom. Or, even possibly in my 
FDITEMP.BAT.
I have not tested had a chance to fully examine the problem. But, so lar it 
appears
to be SHSURDRV.

> I often use SHSURDRV (386, XMSv3 version) as RAM drive
> under QEMU with no problems.
> Of course, my version is reassembled without the (bloated, unused by
> me) ZLIB/"GZIP" stuff (so it's only like 6 kb now).
> 
> What QEMU version are you using?

Don’t know about everyone else. But, I tested it on 2.4.0. 

> I think I'm on 2.5.0 at this point,
> but newer versions are coming soon.
> (Yeah, some Linux distros, e.g. Ubuntu LTS, still only have older
> 2.0.0.) I get mine for Win32/64 (precompiled) from
> http://qemu.weilnetz.de .
> 
>> Drawbacks of not having the RAM DISK or RAM DISK creation failure:


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Rugxulo]

Hi,

On Mon, Apr 4, 2016 at 12:28 AM, Jerome E. Shidel Jr.  wrote:
>
> I have tested under QEMU on Linux and have detected the issue and its cause.
>
> It appears to be that SHSURDRV is locking up the system in DOSBox and QEMU.
> It does not seem to have this issue on the native hardware I’ve tested.

Are you sure? I often use SHSURDRV (386, XMSv3 version) as RAM drive
under QEMU with no problems.
Of course, my version is reassembled without the (bloated, unused by
me) ZLIB/"GZIP" stuff (so it's only like 6 kb now).

What QEMU version are you using? I think I'm on 2.5.0 at this point,
but newer versions are coming soon.
(Yeah, some Linux distros, e.g. Ubuntu LTS, still only have older
2.0.0.) I get mine for Win32/64 (precompiled) from
http://qemu.weilnetz.de .

> Drawbacks of not having the RAM DISK or RAM DISK creation failure:
>
> FDI will not be able to import language or target directory settings from a
> previous installation.
>
> FDI will not be able to automatically partition an empty drive in normal mode.
> (False back to running fdisk)
>
> I will look into detecting QEMU tomorrow sometime.

I don't know of a really good way to detect QEMU.

Sometimes the VESA string tells what emulator, but here it's only
saying "VESA 3.0 SeaBIOS VBE(C) 2011".

Another way is to check the processor string (e.g. cpulevel.com | find
/i "This CPU calls itself"), but that's only available in later cpus,
so you can't exactly use "-cpu pentium" (or even pentium2 or pentium3)
and expect it to work. But if you omit any cpu restrictions, by
default (for me) it now says "QEMU Virtual CPU version 2.5+".

Not sure of other ways (though check news://comp.os.msdos.programmer,
I think it was discussed there before). I think you can detect things
like DOSEMU via BIOS date.

EDIT: I'm guessing this is the thread I'm thinking of: "detecting
emulation or console windows" (May 31, 2014):

https://groups.google.com/forum/#!topic/comp.os.msdos.programmer/l2e4kYnhX-8

> I would hate to have to disable automatic drive partitioning. QEMU seemed a 
> slow compared to
> VMware and native hardware.

QEMU is indeed slower than VBox (with VT-X), but KVM (QEMU with VT-X)
is pretty speedy too. But I think they still use TCG as quasi-JIT, so
it's not as slow as it could be.

--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Don Flowers]

Jerome, Eric, and others,
I used the SLIM image for a quick test on QEMU edited the FDITEMP.BAT file
and now have a successful (basic) install.
Will test the Full install with the 512 image later today.


On Mon, Apr 4, 2016 at 8:14 AM, Jerome E. Shidel Jr. 
wrote:

>
> > On Apr 4, 2016, at 8:00 AM, Jim Hall  wrote:
> >
> > Thanks! I'll try it out tonight.
> >
> > I didn't see the link for the USB image, but I see that it is there. I
> saw the link for Download and the link for Latest, then a bunch of text
> that I didn't read. My bad. ;-)
>
> No problem.
>
> My CMS is only setup to have multiple versions on the Floppy Image.
> The USB images are always the latest FDI and are not versioned.
>
> For the current 4/3/16 images, just remember to add that line of text to
> FDITEMP.BAT.
>
> > For now, the lockup can be avoided by adding
> >
> > goto IsDOSBox
> >
> > at line 26 in the \FDSETUP\SETUP\FDITEMP.BAT portion of FDI.
> > This will cause FDI to just assume RAM DISK creation for initial
> > temporary storage has failed and will proceed with the installation
> > process. FDI will still function like this. However, a few things will
> > not automatically be handled for the user.
>
> Running installer under QEMU….
>
> > qemu-system-i386 -m 32M -hda FDI-USB.img -hdb drivec.img
> >
> > then after install
> >
> > qemu-system-i386 -m 32M -hda drivec.img
>
> At present, I’m looking into detecting QEMU so I don’t have to drop
> the blank drive auto partitioning in Normal mode.
>
> Thanks, Jerome
>
>
>
> --
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Jerome E. Shidel Jr.]

> On Apr 4, 2016, at 8:00 AM, Jim Hall  wrote:
> 
> Thanks! I'll try it out tonight.
> 
> I didn't see the link for the USB image, but I see that it is there. I saw 
> the link for Download and the link for Latest, then a bunch of text that I 
> didn't read. My bad. ;-)

No problem. 

My CMS is only setup to have multiple versions on the Floppy Image. 
The USB images are always the latest FDI and are not versioned.

For the current 4/3/16 images, just remember to add that line of text to 
FDITEMP.BAT.

> For now, the lockup can be avoided by adding
> 
> goto IsDOSBox
> 
> at line 26 in the \FDSETUP\SETUP\FDITEMP.BAT portion of FDI.
> This will cause FDI to just assume RAM DISK creation for initial
> temporary storage has failed and will proceed with the installation
> process. FDI will still function like this. However, a few things will
> not automatically be handled for the user.

Running installer under QEMU….

> qemu-system-i386 -m 32M -hda FDI-USB.img -hdb drivec.img
> 
> then after install
> 
> qemu-system-i386 -m 32M -hda drivec.img

At present, I’m looking into detecting QEMU so I don’t have to drop
the blank drive auto partitioning in Normal mode.

Thanks, Jerome


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Jerome E. Shidel Jr.]

No testing has been done on QEMU on linux.

I will have to look into the issue. 

It may related to startup temp storage RAM drive creation.

--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Don Flowers]

I just tried it and got the same hang. I'll have to try it on another linux
machine tomorrow.

On Sun, Apr 3, 2016 at 7:28 PM, Jim Hall  wrote:

> Is anyone else testing using QEMU (virtual machine on Linux)? I'm not
> getting anywhere. The installation seems stuck after 'Done processing
> startup files FDCONFIG.SYS and AUTOEXEC.BAT'.
>
> The screen just hangs there. I've left it running for other fifteen
> minutes before shutting it down (installing FreeDOS 1.1 on QEMU is
> fast until it starts to install packages. Then it's slow, so I've
> learned to just let QEMU do its thing.)
>
> So I'm not seeing the test.
>
>
>
> My QEMU setup:
>
> * Drive C image initialized with:
> qemu-img create drivec.img 100M
>
> * QEMU command:
> qemu-system-i386 -m 32M -hda $drivec -fda FDI.img -boot ac
>
>
> I'm using FDI-2016-04-03-0.pre.zip
>
>
>
> On Sun, Apr 3, 2016 at 11:53 AM, Jerome E. Shidel Jr. 
> wrote:
> >
> > Hello All,
> >
> > I just pushed another minor update to Preview 15.
> >
> > changes:
> >
> > - Typo correction on Partition Drive Screen.
> > - Automatic updating of installed FDNPKG drive letters to C:
> > (some were pointing to D: after USB stick installation)
> >
> > Thanks, Jerome
>
>
> --
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Jim Hall]

Is anyone else testing using QEMU (virtual machine on Linux)? I'm not
getting anywhere. The installation seems stuck after 'Done processing
startup files FDCONFIG.SYS and AUTOEXEC.BAT'.

The screen just hangs there. I've left it running for other fifteen
minutes before shutting it down (installing FreeDOS 1.1 on QEMU is
fast until it starts to install packages. Then it's slow, so I've
learned to just let QEMU do its thing.)

So I'm not seeing the test.



My QEMU setup:

* Drive C image initialized with:
qemu-img create drivec.img 100M

* QEMU command:
qemu-system-i386 -m 32M -hda $drivec -fda FDI.img -boot ac


I'm using FDI-2016-04-03-0.pre.zip



On Sun, Apr 3, 2016 at 11:53 AM, Jerome E. Shidel Jr.  wrote:
>
> Hello All,
>
> I just pushed another minor update to Preview 15.
>
> changes:
>
> - Typo correction on Partition Drive Screen.
> - Automatic updating of installed FDNPKG drive letters to C:
> (some were pointing to D: after USB stick installation)
>
> Thanks, Jerome

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Don Flowers]

Cool - thanks for the tip!

On Sun, Apr 3, 2016 at 4:49 PM, Jerome E. Shidel Jr. 
wrote:

> Hello Don,
>
> > Are you ready for a chuckle? My server drive is mapped to F:  - the same
> as the CDROM drive assignment . LOL
> > no worries - I will modify it on my end.
> >
>
> Well, you’ll probably like this then.
>
> If you have correctly configured FDNPKG.CFG. And basically, have switched
> to a package based FreeDOS system. You could more or less stick in some
> REPO media and run fdimples /update, then select OK and it will remove and
> then install updated packages through FDINST. This would get a little
> tricky if you booted from the FDI media and want to install packages to C:.
> To do that, I would recommend setting the DOSDIR to the system DOS dir. The
> backing up the FDNPKG.CFG, like to FDNPKG.OLD. The running type FDNPKG.OLD
> | vstr /u /b /s C:\ D:\ >FDNPKG.CFG. That  basically has vstr convert input
> to uppercase, strip out blank lines and replace all “C:\” with “D:\”
>
> FDIMPLES does all kinds of stuff. It is really nice for browsing the
> packages on the FDI USB image.
>
> :-)
>
> Thanks, Jerome
>
>
>
> --
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Jerome E. Shidel Jr.]

Hello Don,

> Are you ready for a chuckle? My server drive is mapped to F:  - the same as 
> the CDROM drive assignment . LOL
> no worries - I will modify it on my end. 
> 

Well, you’ll probably like this then. 

If you have correctly configured FDNPKG.CFG. And basically, have switched to a 
package based FreeDOS system. You could more or less stick in some REPO media 
and run fdimples /update, then select OK and it will remove and then install 
updated packages through FDINST. This would get a little tricky if you booted 
from the FDI media and want to install packages to C:. To do that, I would 
recommend setting the DOSDIR to the system DOS dir. The backing up the 
FDNPKG.CFG, like to FDNPKG.OLD. The running type FDNPKG.OLD | vstr /u /b /s C:\ 
D:\ >FDNPKG.CFG. That  basically has vstr convert input to uppercase, strip out 
blank lines and replace all “C:\” with “D:\” 

FDIMPLES does all kinds of stuff. It is really nice for browsing the packages 
on the FDI USB image.

:-) 

Thanks, Jerome


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FDI Preview 15, update 2

[Don Flowers]

Hey Jerome,

Are you ready for a chuckle? My server drive is mapped to F:  - the same as
the CDROM drive assignment . LOL
no worries - I will modify it on my end.

On Sun, Apr 3, 2016 at 12:53 PM, Jerome E. Shidel Jr. 
wrote:

> Hello All,
>
> I just pushed another minor update to Preview 15.
>
> changes:
>
> - Typo correction on Partition Drive Screen.
> - Automatic updating of installed FDNPKG drive letters to C:
> (some were pointing to D: after USB stick installation)
>
> Thanks, Jerome
>
>
> --
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FDI Preview 15, update 2

[Jerome E. Shidel Jr.]

Hello All, 

I just pushed another minor update to Preview 15.

changes:

- Typo correction on Partition Drive Screen.
- Automatic updating of installed FDNPKG drive letters to C:
(some were pointing to D: after USB stick installation)

Thanks, Jerome

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user