Hallo Herr Jerome E. Shidel Jr.,

am 22. Januar 2016 um 20:33 schrieben Sie:

> I emailed with Jim the other day. He is extremely busy at present.
> However, he stated that he wished to get FreeDOS 1.2 out the 
> door very soon. He did mention some reasons for getting it 
> released. But, I’m not going to go into them. 

> I see no reason why a beta release is not ready in the next
> few days-weeks. So, I highly recommend taking a look at the
> package list files and making any requests you may have for 
> additions or removals.

> https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_BASE.LST
> https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_ALL.LST

> Also, Option 1 in the FDCONFIG.SYS file that FDI creates has issues 
> with VirtualBOX. Someone who is more up to date on the memory 
> managers should do an install and take a look at the config files. Then,
> let me know what needs changed. Otherwise, It won’t get fixed.

> FDI status update:

> It is still finished. However, I just implemented a couple changes:

>         Removed the XMGR
if YOU feel like it; seems you are the new boss here


>         and UIDE packages.
that sounds like a very bad idea


regarding ALL:

ping, wget and possibly some more belong to the same package as mtcp,
but only make sense if you also install some package drivers.
same for rsync and curl


which is afaik included in command.com, at least the one I have

I'd put doslfn in the base package



Tom


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to