[Freedos-user] Installation with Grub already installed

[JR]

Hi there
I would like to install FreeDos 1.3 on my hard drive. I have Windows XP 
and Lubuntu 18.04 installed, both bootable from the Grub boot manager. 
The first partition is FAT and 2G in size and where I would like to 
install FreeDos. Is it possible to install FreeDos without destroying 
Grub and the current installation and how would I do this?

Thanks
John Ritchie


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

[Freedos-user] retro gamer review of FreeDOS 1.3

[Herminio Hernandez, Jr.]

Has anyone watched this review of FreeDOS 1.3 by a Retro Gamer on YouTube.
I thought it was a pretty good and fair review.

https://www.youtube.com/watch?v=SNeq-F84Lx4
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] installing FD13RC5 and FD12 in virtmanager

[Herminio Hernandez, Jr.]

I am running into an issue with installing FreeDOS in virtmanger on Debian
10. FD12 iso boots fine and I can go through the fdisk wizard, I reboot and
start the format and install and I get a warning saying the system files
cannot be found. I drop the console and run "format c:/s" and only the
kernel.sys and command.com are copied which allows the system to boot but I
have no utilities. FD13RC5 will not load the fdisk utility. I tried to run
fdisk from the console and I get "invalid drive designation" the same thing
when I try in gnome boxes. However I can install it on VirtualBox just
fine. I am not sure if it is my setup that is the issue.

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

[Freedos-user] Country Code

[JR]

Hi there
I have a really basic question regarding the date format.
After decades, I decided I would like the date format to be -mm-dd 
instead of mm-dd-yy

The "International English" country code of 061 will do the job.
See. http://wiki.freedos.org/wiki/index.php/Country_codes
I am running FreeDos under Windows XP and included the line 
"country=061,437,c:\windows\system32\country.sys" in the 
c:\windows\system32\config.nt file.
Syntax for the country command is:- country code, code page, path to 
country.sys
This command is apparently ignored as there is no change in the date 
format. I have tried rebooting as well. Any ideas please.
The current code page page can be queried with the chcp command or the 
mode command (CON:)

Is there any means of checking the country code?
Any help appreciated.
Thanks
John


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

Re: [Freedos-user] Why do you use DOS

[JR]

On 2021/04/15 18:05, Liam Proven wrote:

On Thu, 15 Apr 2021 at 14:17, JR  wrote:

  I run DOS under XP with
"TAME" to stop 100% CPU usage.

I am curious -- how? In some sort of VM? MS VirtualPC is a free
download now... something like that?

I've got the name wrong. It's TameDOS.
Nope, not free. It appears to be still available at $20 from the author
http://www.tamedos.com/tame/tamehome.htm
100% CPU usage on a notebook is very noisy with the fan running flat out.




and then Mark William's COHERENT.

Ah, that was an amazing OS in its day. So Unix-like, AT sent Dennis
Ritchie himself to the MWC offices to check it wasn't pirated. It
wasn't.
I didn't know that ;-) Coherent was advertised in BYTE magazine and was 
very reasonably priced at the time. It came with and impressive 1200 
page plus printed manual. When I moved to DOS, I think I used Kermit to 
transfer my source files from Coherent to a DOS partition.


https://groups.google.com/g/alt.folklore.computers/c/_ZaYeY46eb4/m/5B41Uym6d4QJ

It's FOSS now.

http://www.nesssoftware.com/home/mwc/





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

Re: [Freedos-user] Why do you use DOS

[JR]

Hi All
I am 66 years old and have been developing microprocessor based products 
for over 35 years and use DOS 90% of the time. I run DOS under XP with 
"TAME" to stop 100% CPU usage. The XP PC is on my network but remains 
invisible to the Internet. A MikroTik router has been setup to 
accomplish this. I use a dedicated PC running LUBUNTU for email and Web. 
(Thunderbird and Firefox). Prior to DOS I used TSC's Flex, TSC's Uniflex 
and then Mark William's COHERENT.

Principle DOS applications that I run are:-
CO - Michael Mefford's DirMagic
MS - Micro Star from Borland's Editor Toolbox
SP - Sprint - Borland's Word Processor - Produce Postscript files which 
are converted to PDF's. Used for all documentation, letters and quotations.

AS12 - Motorola's open source assembler for the HCS12 family.
asm03 - Budd Pass's 68XX assembler
asm8 - Tony Papadimitriou's freeware assembler for Motorola/ Freescale/ 
NXP HCS08 MCU family

TCC - Borland's C compiler.
grep - Borland's version.

Fast, vanilla and solid!

Regards, John

On 2021/04/14 17:59, Johnpaul Humphrey wrote:

In light of the "DOS was dead" discussion, I wanted to ask a question.
I was *born* after support was dropped for MS-DOS, so I can't claim
nostalgia as my reason for use. Recently I installed FreeDOS on my
modern HP-Pavilion laptop, alongside BSD, Linux, and plan9. I did this
because I like DOS's speed and assembly programming.
It worked fine after I fixed the beep bug with your help.
So my question is, why do YOU use FreeDOS?
Is it primarily nostalgia? Legacy program support? Speed?
Note that I don't consider running legacy software a bad reason. I was
shocked by how much good software has been "thrown away" because of
its age. On Linux all my favorite software (vi, siag office, twm,
motif ) was written before I was born. However, that is not my
primary reason for using FreeDOS. my primary reason is because it is
like the motorcycle of operating systems. It is lightweight, has no
red tape to cut through to do things, and is monotasking. (Monotasking
is also why I don't use it as much as I would like to, but why I use
it at all.)
I figured that if I had a different reason than what everybody
assumes, that some of you might as well. Everyone seems to assume that
DOS is used by people who are unable to cope with progress and have to
run their ancient version of word perfect. If that is your reason, it
is not a bad reason. I was thinking of eventually writing a 64-bit dos
work [sort of] alike eventually, but it would not be able to support
legacy programs due to segment offset addressing and a million other
things.


___
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] DO FreeDOS in the Cloud

[Herminio Hernandez, Jr.]

that is pretty awesome!

On Fri, Dec 28, 2018 at 9:00 AM Jerome Shidel  wrote:

> Hi everybody.
>
> We are still hard at work on the upcoming FreeDOS 1.3.
>
> But, I just couldn't help sharing something really cool about the new
> version. It has a completely new release build process. It can even create
> stock or custom releases on compatible cloud hosting.
>
> If you want to see 1.3 built in the cloud on DigitalOcean, check out the
> https://youtu.be/XZoWCFJDdqY
> 
>  video.
> The first 2:30 is the setup process for the cloud server. The next 4
> minutes is the release builder toolchain installation.
>
> But if you only want to see the release build process, skip ahead to 6:45.
> It takes the server about 10 minutes to build the Floppy, 2 USB stick
> images and the Legacy CD.
>
> Eventually, building of the LiveCD will be added to the release build
> process. It will be replacing the Normal CD.
>
> Hopefully, we will have the remainder of items needed for 1.3 wrapped up
> soon and get RC1 out the door.
>
> Anyhow, I hope you enjoy the video.
>
> 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] questions on FreeDOS

[Herminio Hernandez, Jr.]

From: "Herminio Hernandez, Jr." <herminio.hernande...@gmail.com>

--===5566256051986094646==
Content-Type: multipart/alternative; boundary=94eb2c1b4eaad5cf3c05477bff02

--94eb2c1b4eaad5cf3c05477bff02
Content-Type: text/plain; charset=UTF-8

I realized it was a listening issue. I ran netcat to listen on a port and I
was able to test that the port was open.

Thanks for the feedback!

On Wed, Feb 1, 2017 at 10:10 AM, Rugxulo <rugx...@gmail.com> wrote:

> Hi,
>
> On Tue, Jan 31, 2017 at 9:14 PM,  <herminio.hernande...@gmail.com> wrote:
> >
> > 2. is there a way to set FreeDOS as a VNC, telnet, or even SSH server?
> > I would have a full screen session when playing some of the DOS games.
>
> First of all, I misread your question. But, just for clarity, (IIRC)
> you can make VBox full-screen using Host-F (N.B. Host is usually Right
> Ctrl).
>
> Secondly, although this isn't super helpful advice (and yet
> freedos.org does imply gaming), I don't think VirtualBox is ideal for
> games. It just lacks some compatibility that some games need. Maybe
> it'll work for some of your use cases, but normally it is suggested to
> use (non-FreeDOS) DOSBox emulator instead, which has much better sound
> and graphics support and can dynamically adjust cycles (among other
> things).
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>

--94eb2c1b4eaad5cf3c05477bff02
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I realized it was a listening issue. I ran netcat to listen on a
port and I was able to test that the port was open.Thanks
for the feedback!-aOn Wed, Feb 1, 2017 at 10:10 AM, Rugxulo mailto:rugx...@gmail.com;
target="_blank">rugx...@gmail.com wrote:Hi,

On Tue, Jan 31, 2017 at 9:14 PM,-a mailto:herminio.hernande...@gmail.com;>herminio.hernandezjr@gmail.com
 wrote:

 2. is there a way to set FreeDOS as a VNC, telnet, or even SSH server?
 I would have a full screen session when playing some of the DOS games.

First of all, I misread your question. But, just for clarity, (IIRC)
you can make VBox full-screen using Host-F (N.B. Host is usually Right
Ctrl).

Secondly, although this isnt super helpful advice (and yet
http://freedos.org; rel="noreferrer" target="_blank">freedos.org
does imply gaming), I dont think VirtualBox is ideal for
games. It just lacks some compatibility that some games need. Maybe
itll work for some of your use cases, but normally it is suggested to
use (non-FreeDOS) DOSBox emulator instead, which has much better sound
and graphics support and can dynamically adjust cycles (among other
things).

--
Check out the vibrant tech community on one of the worlds most
engaging tech sites, SlashDot.org!
http://sdm.link/slashdot; rel="noreferrer"
target="_blank">http://sdm.link/slashdot
___
Freedos-user mailing list
mailto:Freedos-user@lists.sourceforge.net;>Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user;
rel="noreferrer" 
target="_blank">https://lists.sourceforge.net/lists/listinfo/freedos-user


--94eb2c1b4eaad5cf3c05477bff02--


--===5566256051986094646==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===5566256051986094646==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===5566256051986094646==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDO

[JEROME E. SHIDEL JR.]

From: "Jerome E. Shidel Jr." <jer...@shidel.net>


> On Nov 3, 2016, at 6:24 PM, Louis Santillan <lpsan...@gmail.com> wrote:
>
> WOW!  Awesome work here.  Thanks for posting this!
>

Thanks.

I see there might be a possible version regression with a couple base
packages. I will have to look into those.

Jerome
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99)

---
 * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Cannot

[JEROME E. SHIDEL JR.]

From: "Jerome E. Shidel Jr." <jer...@shidel.net>



> On Oct 28, 2016, at 1:04 PM, Simon Atkinson <simonatkin...@operamail.com>
wrote:
>
> Hi there
>
> I presume that FreeDOS, like other versions of DOS, will run on an
8086-based system or have I missed something?
>
> I have tried to boot FreeDOS on a IBM PS/2 Model 30 (8086 CPU and standard
8-bit ISA and version with a 1.44MB floppy drive), but have had little luck.
>
> The boot disks I created for MSDOS5.0 and OpenDOS 7.01 and DRDOS7.02 work
fine rCo dropping me into the DOS prompt. I can then use their respective
versions of FDISK to see to the installed 20MB hard disk etc. These boot disks
also work fine if the hard disk is removed allowing me to run the respective
version of DOS from the floppy.
>
> However, FreeDOS doesnrCOt boot at all! IrCOm puzzled... IrCOve tried simple
boot disks that I have created based on FreeDOS 1.1 and 1.2, but no luck. For
1.2, for example, I just get a series of dots and the word rCLERROR!rCY When I
have tried FreeDOS 1.1, with the hard disk in place, it boots to the point
where it list the hard diskrCOs CHS geometry and then just hangs
>
> Any ideas?


I canrCOt say for FreeDOS 1.1 distribution files.

However, some of the utilities required by the 1.2 Previews require a 386 or
better to function. Also, CD-ROM and bootable USB really was not supported
pre-386. So, all of the release images for FreeDOS 1.2 use the kernel built for
386 or better processors. The kernel package that is included with 1.2 contains
both the 386 and x86 kernels along with several docs and batch file utilities.

Jerome



--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99)

---
 * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.

[JEROME E. SHIDEL JR.]

From: "Jerome E. Shidel Jr." <jer...@shidel.net>

Have you wondered exactly what has been updated in the new FreeDOS release
since version 1.1?

Check it out
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/previe
s/1.2-rc1/compare.html
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99)

---
 * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] questions on FreeDOS

[Herminio Hernandez, Jr.]

I realized it was a listening issue. I ran netcat to listen on a port and I
was able to test that the port was open.

Thanks for the feedback!

On Wed, Feb 1, 2017 at 10:10 AM, Rugxulo  wrote:

> Hi,
>
> On Tue, Jan 31, 2017 at 9:14 PM,   wrote:
> >
> > 2. is there a way to set FreeDOS as a VNC, telnet, or even SSH server?
> > I would have a full screen session when playing some of the DOS games.
>
> First of all, I misread your question. But, just for clarity, (IIRC)
> you can make VBox full-screen using Host-F (N.B. Host is usually Right
> Ctrl).
>
> Secondly, although this isn't super helpful advice (and yet
> freedos.org does imply gaming), I don't think VirtualBox is ideal for
> games. It just lacks some compatibility that some games need. Maybe
> it'll work for some of your use cases, but normally it is suggested to
> use (non-FreeDOS) DOSBox emulator instead, which has much better sound
> and graphics support and can dynamically adjust cycles (among other
> things).
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 -- Whats Up?

[Jerome E. Shidel Jr.]

> On Nov 3, 2016, at 6:24 PM, Louis Santillan  wrote:
> 
> WOW!  Awesome work here.  Thanks for posting this!
> 

Thanks.

I see there might be a possible version regression with a couple base packages. 
I will have to look into those.

Jerome
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.2 -- Whats Up?

[Jerome E. Shidel Jr.]

Have you wondered exactly what has been updated in the new FreeDOS release 
since version 1.1?

Check it out 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/previews/1.2-rc1/compare.html
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Cannot boot FreeDOS on 8086-based IBM PS/2 -- any ideas?

[Jerome E. Shidel Jr.]

> On Oct 28, 2016, at 1:04 PM, Simon Atkinson  
> wrote:
> 
> Hi there 
> 
> I presume that FreeDOS, like other versions of DOS, will run on an 8086-based 
> system or have I missed something?
> 
> I have tried to boot FreeDOS on a IBM PS/2 Model 30 (8086 CPU and standard 
> 8-bit ISA and version with a 1.44MB floppy drive), but have had little luck.
> 
> The boot disks I created for MSDOS5.0 and OpenDOS 7.01 and DRDOS7.02 work 
> fine – dropping me into the DOS prompt. I can then use their respective 
> versions of FDISK to see to the installed 20MB hard disk etc. These boot 
> disks also work fine if the hard disk is removed allowing me to run the 
> respective version of DOS from the floppy.
> 
> However, FreeDOS doesn’t boot at all! I’m puzzled... I’ve tried simple boot 
> disks that I have created based on FreeDOS 1.1 and 1.2, but no luck. For 1.2, 
> for example, I just get a series of dots and the word “ERROR!” When I have 
> tried FreeDOS 1.1, with the hard disk in place, it boots to the point where 
> it list the hard disk’s CHS geometry and then just hangs
> 
> Any ideas?


I can’t say for FreeDOS 1.1 distribution files. 

However, some of the utilities required by the 1.2 Previews require a 386 or 
better to function. Also, CD-ROM and bootable USB really was not supported 
pre-386. So, all of the release images for FreeDOS 1.2 use the kernel built for 
386 or better processors. The kernel package that is included with 1.2 contains 
both the 386 and x86 kernels along with several docs and batch file utilities.

Jerome



--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 20, 2016, at 5:23 PM, Dimitris Zilaskos <dimitr...@gmail.com> wrote:
> 
> Hi,
> 
> On Wed, Jul 20, 2016 at 9:50 PM, Jerome E. Shidel Jr. <jer...@shidel.net 
> <mailto:jer...@shidel.net>> wrote:
>> On Jul 20, 2016, at 12:56 PM, Dimitris Zilaskos <dimitr...@gmail.com 
>> <mailto:dimitr...@gmail.com>> wrote:
>> […]
>> Dimitris
> 
> I have a few silly questions.
> 
> You have verified the drive has the correct jumpers set?
> 
> Correct, master / slave 

:-)

> 
> 
> You are not trying to use cable select mode?
> 
> Nope

:-)

>  
> 
> You are using the correct position on the IDE cable?
> 
> Yes 

:-)

> 
> You are plugged into the primary controller?
> 
> Yes

:-)

>  
> 
> Is the BIOS configuration for the drive being set manually or using "auto" 
> mode?
> 
> This is actually a good question. It is user mode which would qualify as 
> manually, but I can't remember if the values for CHS were actually entered 
> manually by copying them from the labels, or using the auto detect BIOS 
> feature. I do recall it look a lot of effort to figure this out, as any 
> mistake and the system would not detect the hdds or boot altogether. 
> 
> You mentioned “tertiary” at one point. How many drives? How many controllers? 
> 
> The sound blaster card has one IDE port that currently has 2 CD-ROM drives 
> connected in master/slave setup 
> 
> Is the drive partitioned as a single disk or multiple partitions?
> 
> single partition 
:-)
> 
> It is not inside an extended partition?
> 
> No
:-)
>  
> 
> If there are any other drives, are they partitioned and formatted for DOS?
> 
> Yes, the slave drive is an old windows98 system with a fat32  partition.
> 
> I can simplify the setup - remove all CDROM drives and the slave hard drive 
> and leave only one hdd and the floppy to see if there is any change.

It probably won’t help. But, It wouldn’t hurt to try. 

> 
> Cheers,
> 
> Dimitris

Mostly, I wanted to verify you weren’t using cable select. I’ve seen it work 
great and I’ve seen it cause weird issues. 
There are some strange jumper settings on some drives. Most just master/slave. 
But others that plus single or multiple, LBA or not…
Sometimes you just remove all the jumpers, sometimes you hunt around in you 
desk for an hour because you need just one more.
Oh, IDE was some much fun. Especially, when adding extra cards and raids. 

Anyhow, I figured I might as well play “20 questions” and rule out some of the 
simple but often overlooked items. 

Jerome


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 - Preview 22 - EDIT CPU load

[Jerome E. Shidel Jr.]

> On Jul 20, 2016, at 10:24 AM, Rugxulo  wrote:
> 
> Hi,
> 
> On Wed, Jul 20, 2016 at 6:01 AM, Eric Auer  wrote:
>> 
>>> I just downloaded the bootable FD 1.2pre22 CD and booted a VM in
>>> VirtualBox.  I see `FDAPM APMDOS` in autoexec.bat.  No IDLEHALT in
>>> FDCONFIG.SYS.  CPU also spikes to 100% when I run `edit autoexec.bat`.
>> 
>> I remember that this is a problem with certain EDIT versions. Of
>> course IDLEHALT is nice, but FDAPM APMDOS should be okay as well.
>> 
>> Here is what for example EDIT 0.7c did in DFLAT's dispatch_message:
>> ...
>> Please check the sources or ask Aitor Santamaria and Joe Cosentino.
>> Maybe your version is missing some patches...
> 
> According to DFP100S.ZIP's "source/dflatp/message.c":
> 
> BOOL dispatch_message(void)
> {
>WINDOW Mwnd, Kwnd;
>/*  collect mouse and keyboard events --- */
>collect_events();
> 
>/* only message.c can fill the event queue, but all components */
>/* can fill the message queue. Events come from user or clock. */
>if ( (EventQueueCtr == 0) && (MsgQueueCtr == 0) &&
>(handshaking == 0) ) {/* BORED - new 0.7c */
>union REGS r;
> #if 0/* int 2f is often quite crowded */
>r.x.ax = 0x1680;/* release multitasker timeslice */
>int86(0x2f, , );/* multiplexer call */
> #else
>r.h.ah = 0x84;/* "network" idle call */
>int86(0x2a, , );/* network interfaces */
> #endif
> ...
> }
> 
> But indeed, even with IDLEHALT, that doesn't seem to work with FD
> EDIT. Nor does TDE, strangely enough, which uses DJGPP's
> __dpmi_yield(). Even e3-16 is guilty (no surprise there, it's quite
> simplistic).
> 
> I also tried ancient Stevie 3.69a (TurboC?) and newer VILE 9.8
> (DJGPP), yet surprisingly both seemed to not hog the host cpu at all.
> Must be a vi thing!  :-P
> 
> P.S. IDLEHALT works quite well otherwise, esp. when just sitting at
> the console / shell doing nothing. That's why I mentioned it in the
> first place, it's better than nothing.

Yeah, EDIT runs at 100% CPU usage for me as well.

I had a user complaint that FDIMPLES “was great” but you could fry an egg on 
their CPU. 
Oops, sorry, Took about 3 seconds to fix. Just forgot to do something. 
Threw an assembly 0xF4 (HLT) in before keyboard check in its polling loop. 
Yay, CPU usage own to 6%.




--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 20, 2016, at 12:56 PM, Dimitris Zilaskos  wrote:
> […]
> Dimitris

I have a few silly questions.

You have verified the drive has the correct jumpers set?


You are not trying to use cable select mode?

You are using the correct position on the IDE cable?

You are plugged into the primary controller?

Is the BIOS configuration for the drive being set manually or using "auto" mode?

You mentioned “tertiary” at one point. How many drives? How many controllers? 

Is the drive partitioned as a single disk or multiple partitions?

It is not inside an extended partition?

If there are any other drives, are they partitioned and formatted for DOS?


Jerome--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 18, 2016, at 9:02 AM, Dimitris Zilaskos  > wrote:
> 
> Hi,
> 
> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this problem: 
> https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0 
> 
> 
> ​​I have observed that the gibberish stops given sufficient time: 
> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA 
> 
> 
> Let me know what else I can try - I will recheck the floppies for starters in 
> case they went bad and check the rest of your suggestions.
> 
> Best regards,
> 
> Dimitris
> 

You could just try removing HIMEMX.SYS from the FDCONFIG.SYS file.

Also, remove the DOS=HIGH, DOS=UMB, DOSDATA=UMB.

Change SHELLHIGH to SHELL.

After doing all of that, see what happens. 

FDI needs very little memory to run. It only loads stuff HIGH so the boot media
could be used to run other (not included) diagnostic programs and recovery 
tools.

Jerome--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos  > wrote:
> I have tried it please see the output attached. This is endlessly scrolling 
> after drives are detected. 
> 
> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr
>  
> 
Unfortunately, that isn’t very helpful.

When you boot the floppy, can you press F8 to walk through the startup?  What 
item in the configuration
causes it to crash?

Jerome--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

One more thing,

> On Jul 18, 2016, at 2:34 AM, Louis Santillan  wrote:
> [...]
> Install FD 1.2 beta.  `sys c:` at the end of your install.

I don’t think you need to do the ‘sys c:’ at the end of the install anymore.
It shouldn’t hurt anything if you do run it.

Now, on the other hand. If the installed system does not boot after 
installation, there is simple batch file included that will run FDI with
a special option. This will tell FDI that you have already installed
FreeDOS and it wouldn’t boot. FDI will then offer some advanced
mode options to FORCE new boot sector code. This will wipe out
any multi-boot boot loader (like GRUB) and install the FreeDOS
boot sector.

You can try this utility by booting one of the FDI install media images.
Then run MBRZAP.BAT from the command line.

Jerome
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Which freedos on 486

[Jerome E. Shidel Jr.]

> On Jul 18, 2016, at 2:34 AM, Louis Santillan  wrote:
> 
> On Sun, Jul 17, 2016 at 5:21 PM, Dimitris Zilaskos  
> wrote:
> 
> […]
> 
>> Is there a recommended strategy to get FreeDOS installed on such an ancient
>> system? Did some research and tried several bootdisks that float around,
>> nothing worked quite like FreeDOS 1.0.
> 
> If you're willing to test FDI 1.2, download the beta boot floppy [0],
> and the cdrom iso [1].  Make sure the boot floppy can recognize your
> two hard drives and your CD-ROM.  Add drivers and edit
> autoexec.bat/fdconfig.sys as necessary (especially wrt to ensuring
> CD-ROM access).  Install FD 1.2 beta.  `sys c:` at the end of your
> install.
> 
> [0] http://dnld.lod.bz/FDI-2016-07-17-0.pre.zip 
> [1] 
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/cdrom.iso
>  
> 

Louis is correct. Once you get the FDI 1.2 Preview floppy to boot and access 
your CD-ROM,
you should be able to run the installer. If the included driver (UDVD2) does 
not work with your
drive, you to hunt down an alternate driver or even vendor specific driver for 
your hardware.
There are a couple of other drivers in the old FreeDOS 1.1 Repository. These 
have been
removed from version 1.2 for various reasons. But, you could try UIDE [2], 
XCDROM [3] or
GCDROM [4]. 

If you have a functioning non-FreeDOS boot disk (like MS-DOS 5) that can access 
your
CD-ROM, you could try booting it and then sticking in the FDI floppy and CD. 
Then manually
run the SETUP.BAT. Assuming that works, you would have problems when you reboot 
the
installed system. 

If everything else fails, you could try the the spare disk install method. It 
is mentioned in the
FDI Readme [5]. More or less, you copy everything from one of the USB images to 
a spare
hard drive root directory using another computer. The put that drive in the 
computer where you
want to install FreeDOS and run the SETUP.BAT. The spare drive should NOT be 
the drive
where you want to install FreeDOS. Normally, FDI will not permit you to install 
from and to 
the same drive. Trying to override this behavior using FDI in advanced mode is 
NOT 
recommended and can cause very unpredictable results.

Just a note on the 1.2 Repository CD-ROM [1]. Building the CD can place a heavy 
load on 
the server for several minutes. So, when packages in the 1.2 repo are updated, 
building
of this image is postponed until the end of the day. This process is completely 
automated
and is self maintaining. When packages have changed, a new repo CD will be 
automatically
created and be posted at approximately 0300-0315 EST the next morning. 
Generally, this
image is not updated at release time. But, it takes care of itself within 24 
hours.

There are static CD [6], SLIM [7], USB [8]  and Latest Floppy [9] that are 
created at release time.
these are also available on ibiblio [10]. The packages on these images are not 
updated
once a Preview or Release is issued. 

All released versions use the same version of FDI. However, the booted system 
configuration 
can vary slightly. The biggest difference is the Floppy image. Unlike the 
others, it loads
disk caching software at startup to increase the performance when running FDI 
from a 
real floppy drive. FDI itself is unchanged from one format to another. 

So, for instance, you could pull the BOOT.IMG from RepoCD [1]. Write it to a 
real floppy disk.
Grab the SLIM USB [7] image and write it to a USB stick. Then boot the floppy 
and either
just let FDI run. Or, exit FDI. Switch to the USB stick. Remove the Floppy, 
Then run 
SETUP.BAT. The result should be the same. (Although, FDI does a couple things 
differently when you run it manually.)

[2] 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/uide.zip
 

[3] 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/xcdrom.zip
 

[4] 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/gcdrom.zip
 

[5] https://github.com/shidel/FDI/blob/master/README.md 
 or 
http://dnld.lod.bz/FDI-README.md 
[6] http://dnld.lod.bz/FDI-CD.iso  
[7] http://dnld.lod.bz/FDI-SLIM.zip  
[8] http://dnld.lod.bz/FDI-USB.zip  
[9] http://up.lod.bz/FDI/latest  
[10] 

[Freedos-user] FreeDOS 1.2 - Preview 22

[Jerome E. Shidel Jr.]

Preview 22 just released. Includes lots more packages.

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/previews/1.2-pre22/
 


or

http://up.lod.bz/FDI --
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.2 Networking and Internet.

[Jerome E. Shidel Jr.]

Hello all,

As you you may already know, we have been working on the FreeDOS 1.2 release. 
One thing I would like to see make it into the release is some networking. I 
don’t think it would be 
practical to have a universal setup for each and every machine and NIC at this 
time. But, it
may be possible to have the installer automatically do this for some of the 
known virtual machines.
For example, it may be feasible to setup and configure VMware, VirtualBOX and 
QEMU to do
networking. But, I don’t have the time to figure it all out. This is where all 
of you come in. 

If you can provide the detailed information for these platforms and Jim 
approves, I may then be 
possible to include it. 

Here are the main and mostly obvious requirements.

All files and drivers must have an acceptable license and can be 
redistributed. Public Domain, 
GPL, BSD or another open source or unrestricted license. No encumbered 
commercial drivers 
(such as NOVELL Netware, 3COM, NetGear, ….. ).

DHCP setup only.

Links to (or provide) any drivers and files that are required.
(It would be nice if they were in a FDNPKG compatible package)

Completely setup configuration files for the platform. (all INI, CFG 
files, etc)

List of any current 1.2 repo packages that may be needed (excluding 
BASE packages).

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/

Preferably, any files that are not in a package (like the config files) 
are placed under 
\NET\VMWARE, \NET\VBOX, \NET\QEMU or other appropriate directory for 
the platform.

Also, please do not provide a customized config.sys or autoexec.bat. It 
should be possible to
place all environment settings and load drivers from a 
\NET\STARTNET.BAT file. 

Thank you, Jerome

(Without your support, there is no way any type of pre-configured networking 
will make it into the next release.)



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Keyboard input absent

[JR]

Hi Ulrich
Apologies again, I see my previous response was to yourself and not the 
list.Thanks for all your suggestions.
To recap.
The OS is  XP.
The PC is a 10 year old HP notebook with a docking station.
I am using an external PS2 keyboard and mouse on a USB adaptor.
Running the P program kills keyboard input in the VDM. It also kills 
input from the notebook keyboard.
The P program runs under the Windows command prompt (cmd.exe)
P were made aware of the problem but will not be addressing it.

Some additional information.
My previous work around to this problem was to use a second PC on a 
network to run the P program.
This was a Windows 2K PC. The new version of P software does not run 
under W2K.
That's why it's now installed on my XP PC.
I have also tried running dosx.exe and ntvdm.exe found in 
\Windows\System32 directory.
Keyboard input is present in cmd.exe  and Windows apps after running the 
P program.

What I've learned so far.
Running the old P program on the W2K PC does not break the keyboard 
input in the VDM.
The old version also killed keyboard input on an XP PC.
I can't swap the PS2 keyboard and mouse as I'm using a USB adaptor. (2x 
PS2 to USB)
If I swap the PS2 plugs on the adaptor neither work. (Under Windows)
Deleting the keyboard drivers shown in the Device Manager does not 
change anything.
I don't think the TSR manager is relevant as the P program is run 
under cmd.exe

Any further thoughts are very welcome.

John




--
Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Keyboard input absent

[JR]

Hi there
My apologies if this mail has already been posted. I am new to the list. 
I posted it yesterday but I do not see it. So  here it is again.
My OS is XP SP3. After running a Windows command line application from 
"P Microcomputer Systems" to program Freescale MCU's there is no 
keyboard input in the VDM. FreeDOS launches normally but there is no 
keyboard input. If in Full Screen mode, Ctrl Esc works. Returns to the 
desktop and opens the Start menu. Perhaps a clue is that Alt Esc returns 
to Desktop (Start menu is not opened). Under normal operation when 
keyboard input is present in the VDM, the Alt Esc key sequence does not 
work. FreeDOS must be closed by right clicking the app icon on the 
bottom bar of the desktop to force it to be closed.
The only way to fix the problem is to reboot. Does any one know if I can 
patch memory or run a program fix this? Perhaps the vectors are being 
hi-jacked or the keyboard driver being replaced? P will not address 
the problem. Any help or ideas appreciated.
John

--
Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.2 Preview 21

[Jerome E. Shidel Jr.]

Hello All,

I have just released Preview 21.

This is only a minor preview update. Mostly these things:

installed configuration for FDNPKG now points to the 1.2 repository.
a couple of additional utilities by Eric Auer are included as EXTRAS on the big 
USB and CD image.
some release building improvements 

You can download it from either http://up.lod.bz/FDI  or 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/previews/1.2-pre21
 
.

Jerome--
Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Games - and DOS installation

[Jerome E. Shidel Jr.]

> On Jun 18, 2016, at 1:29 PM, Eric Auer  wrote:
> 
> 
> Hi guys,
> 
> (sorry about the long mail...)
> 
>> During the discussion of version 1.2, this was my interpretation of 
>> how this should be handled and what was implemented when the 
>> user installed FreeDOS in normal mode. Having a failed install (by 
>> not booting into FreeDOS) was unacceptable behavior. Therefore, 
>> the installer would normally backup and then over-write the boot...
> 
> Well, as mentioned several times in the 1.2 discussion, losing all
> your data is even more unacceptable, so there should be a choice ;-)

No data is lost unless the user intentional destroys it themselves. 
The boot sector and boot code is backed up prior to being over-written.
This occurs in either normal or advanced mode.

> 
> On dedicated harddisks or virtual computer images, which optionally
> could be auto-detected by the installer, it is of course nice to do
> automatic "rude" installs which makes sure that DOS boots afterwards.
> 
> But the user should have the choice between "rude" install, "no"
> install at all (simply use "live" DOS as booted from USB stick)
> and as 3rd choice "manual" install, where the user has to do the
> partitioning and formatting by hand before running the installer
> which limits itself to install DOS to any user-chosen directory,
> even asking whether SYS should be run and whether config/autoexec
> should be overwritten or just prepared under another name :-)

If the user has already prepared a drive C: prior to using the installer,
the installer will see this and will not auto-partition the hard drive. It will
also not even prompt to partition the drive. If the user has also formatted
the drive, the installer will skip this as well. 

Other things, like not installing the SYS files, not installing boot code,
not installing new autoexec & config files are all optional in advanced 
mode. 

Personally, I think anyone who is running the installer on a system
that is to be multi-boot or some other situation, should run the installer
in advanced mode to fully control its behavior.

> 
>> code during installation. This action can be overridden if advanced 
>> mode is used during the install. There were many pros and cons 
>> to this being the default action.
>> 
>> The installer will not destroy partitions...
> 
> As long as the installer makes it clear that you have a CHOICE,
> as long as that choice is not what happens by default when you
> just press Y or enter, this is already quite reasonable :-) As
> you see, people ARE scared that the install can delete data.
> 
>> * The installer checks if there is a drive C: visible to FreeDOS. 
> 
>> If does not find one, and that drive is blank it will use fdisk to 
>> automatically partition the drive in "smart" mode. Otherwise, if
>> there are partitions existing on the drive, or it cannot figure 
>> out what should be partitioned, or if it is in “dumb" mode. It
>> will launch fdisk and let the user deal with it.
> 
> How does it decide about the "blank" aspect?

It uses multiple tools and parses results from queries to fdisk.

If there are any partitions present, the drive will not be 
auto-partitioned. If there is a drive that fdisk lists as hard drive C:,
it will be used. 

> 
>> * Installer checks if drive C: can be read by FreeDOS. If not, 
>> it will format it.
> 
> It should NOT do that by default if you ask me. It should rather
> say something like "There is a C: but it does not work for DOS.
> If you just made the partition for DOS, you can press F now to
> let me format C: Otherwise, please leave the installer and take
> care to make C: accessible for DOS, in any way that seems good.”

As I said, I left out all question prompts the installer asks in the 
logic summary I posted. The installer does not just format a drive.
It asks first. 

It doesn’t even partition without asking. The partitioning behavior is
slightly different in advanced and normal modes.

When drive needs to be partitioned:

Normal mode:

Does all that detection stuff.

Asks if user wants to partition or quit?

If so, and can auto-partition, it does so. If it cannot auto-partition
it launches fdisk.

After partition. Asks to reboot or exit.

Advanced mode.

Does some detection stuff to determine bios drive.

Asks if user wants to partition or quit?

Launches fdisk set for the bios drive.

After partition. Asks to reboot or exit.

> 
> (the above example deliberately uses "F" instead of "Y" to make
> sure that people have to think before they just press "agree”)

Advanced mode.

> 
>> * The installer transfers the system files and overwrites the
>> boot code. 
> 
> That, too, might want to ask the user first…

Advanced mode.

> 
>> Advanced mode, provides these capabilities:
>> * never auto-partition 
>> * option of long-slow formatting.
>> * installing to drives other than C: (configured 

Re: [Freedos-user] Games - and DOS installation

[Jerome E. Shidel Jr.]

> On Jun 18, 2016, at 7:20 AM, Eric Auer  wrote:
> […]
> I think this was part of the FreeDOS 1.2 discussion before, but
> how about detection whether a harddisk is "totally" empty before
> showing the question how to install? I agree that for people who
> made a totally empty virtual PC image a minute before installing
> FreeDOS, it would be easiest to just let the installer throw one
> standard DOS partition on that "disk" without asking the user to
> make many decisions on partitioning and formatting. But for the
> users who do NOT have a dedicated harddisk for DOS, it is scary.
> 
> Cheers, Eric

During the discussion of version 1.2, this was my interpretation of 
how this should be handled and what was implemented when the 
user installed FreeDOS in normal mode. Having a failed install (by 
not booting into FreeDOS) was unacceptable behavior. Therefore, 
the installer would normally backup and then over-write the boot
code during installation. This action can be overridden if advanced 
mode is used during the install. There were many pros and cons 
to this being the default action.

The installer will not destroy partitions. Basically, this is what 
happens in basic normal mode (excluding question prompts
and lots of other stuff):

* Installer Boots.
* Installer tries to create a RAM drive for temporary data storage.
If that fails, the installer falls back to “dumb” mode.
* The installer checks if there is a drive C: visible to FreeDOS. 
If does not find one, and that drive is blank it will use fdisk to 
automatically partition the drive in "smart" mode. Otherwise, if
there are partitions existing on the drive, or it cannot figure 
out what should be partitioned, or if it is in “dumb" mode. It
will launch fdisk and let the user deal with it.
* If fdisk was run, reboot.
* Installer reloads.
* Installer performs all of the above checks again, this time
it finds a drive C:.
* Installer checks if drive C: can be read by FreeDOS. If not, 
it will format it.
* …….. Much later.
* The installer transfers the system files and overwrites the
boot code. 

Advanced mode, provides these capabilities:
* never auto-partition 
* option of long-slow formatting.
* installing to drives other than C: (configured as C: for booting)
* not transferring the system boot files
* not over-writting the boot code.
* lots of other stuff.

The FreeDOS 1.2 Preview releases contain several boot images.
ISO, Small USB and Big USB. There is lots of software for 
burning the ISO to a disc. Using a Mac or Linux machine, it
is also very easy to put either USB image on a flash drive.
This can be done by just using:

sudo dd if=FILENAME.IMG of=/dev/MEDIA

There are additional dd options. Some, that can be used to 
greatly speed up the process. But, that is all that is really needed.

Jerome
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FDI Preview 20

[Jerome E. Shidel Jr.]

Hello All, 

FDI Preview 20 has been released for testing.

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2-pre20/
 


or 

http://up.lod.bz/FDI 


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 Package LSM Data Verification

[Jerome E. Shidel Jr.]

> On May 19, 2016, at 3:55 PM, Louis Santillan <lpsan...@gmail.com> wrote:
> 
> On Wed, May 18, 2016 at 3:22 PM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> wrote:
> [SNIP]
>> 
>> Is DOSLFN going to be dropped? I don’t know. It is not up to me and my 
>> opinion is not even relevant. I have not been informed of any decision to do 
>> so. The problem is its licensing is unclear. There is no licensing 
>> information contained in its source files or with its binaries. It may be 
>> Public Domain. I have no idea.
>> 
>> Freely available source is not Open Source and is not Public Domain. All 
>> works are Copyright at the moment of their creation. Regardless if it is 
>> declared or not. However, it is nearly impossible to enforce a Copyright 
>> violation without said notice. But, would you like to see FreeDOS sued into 
>> non-existence do to a minor copyright violation?
>> 
>> Now in regards to my original quoted message. If DOSLFN is found to be 
>> unsuitable, I will not be hunting down an alternative to it.  Someone in 
>> either the freedos-user or devel group mentioned that there was another 
>> program that did lfn and it was very buggy. I have no idea what it is 
>> called. I have no idea if it is buggy. If you would like to find a suitable 
>> alternative, it can be considered for inclusion.
> 
> I finally found a(n obvious) term for DOSLFN's situation, License-Free
> Software [0].  This means source is unmarked with license and/or
> copyright info.  And if you believe DJB's judicial reasoning, placing
> the code on the net, demonstrating how to use the software "creates"
> an implied license with similar restrictions to Public Domain software
> 
> Food for thought.
> 
> [0] https://en.wikipedia.org/wiki/License-free_software 
> <https://en.wikipedia.org/wiki/License-free_software>

Sounds good to me.

Thanks

--
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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

Hello Eric and all,

First, I went through the couple old 1.1 packages that were not on the update 
repo. They were buried elsewhere on ibiblio.

So, at present these will be included on big USB but are not currently 
installed under ALL or BASE.

RIPCORD
DOSUTIL, also updated  to latest version.
SYSLINUX, 4.x, there is a 6.x version available if someone wants to build it, 
probably should add this to ALL.
FLASHROM
FDSHIELD, updated to latest version.
CALLVER, probably should add this to base.
SAMCFG

UPX had not gone away, it was it the DEVEL group. I just missed seeing it when 
compiling the list.

And, CURL is now back. It’s sources were located. I also updated it. Hopefully, 
it is not broken.

WATTCP is the only one remaining. 

I have spent many many many hours fixing broken and incorrect packages. At 
least for now and the foreseeable future, I think I am done fixing them. I will 
be more than happy to include the remainder once they are fixed. 

> On May 19, 2016, at 1:16 PM, Eric Auer  > wrote:
> 
> 
> Hi Jerome,
> 
>> Except for the following packages all other dropped and questionable
>> packages are listed at the beginning of this thread. This list of
> 
> Please cite the beginning-of-this-thread snippet, it is a long thread.
> 
>> packages shipped with 1.1 and are not presently in 1.2. None of these
>> packages are on the ibiblio repo for version 1.1 either.  I have not
>> put any work into trying to include these packages as of yet.
> 
> Do you mean they were part of the 1.1 distro but not of the 1.1 repo?

Yes, however some are elsewhere on ibiblio.

> 
>> DOSUTIL, No sources present in package. Might be buried on repos
> 
> What is the content of that package?
> 
>> RIPCORD, FreeDOS release related program, Compatibility not tested.
> 
> Indeed probably specific to the 1.1 distort.

For now, included. I will try it out prior to next release.

> 
>> SAMCFG, I don’t know if it is applicable anymore.
> 
> Sounds like a sample config, which could be useful to include.
> Of course if you find some settings which are no longer valid
> for updated drivers, it would be cool to update those, but I
> would say that the 1.1 sample config should still be valid :-)
> 
>> SYSLNX There has to be a newer version, not in repo for 1.1.
> 
> Syslinux? That sounds pretty important.

Probably, someone should really update it.

> 
>> WATTCP, No Source files present
> 
> http://www.freedos.org/software/?prog=wattcp 
>  says that would
> be the place to be. The wat2001b.zip indeed does have sources.
> 
>> CALLVER, FLASHR, SHIELD and UPX not in repo for 1.1
> 
> Maybe you mean FDSHIELD: www.freedos.org/software/?prog=fdshield 
> 
> This does include sources.
> 
> http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/ 
>  has
> a copy of CALLVER 2007-aug19.zip which includes sourcs.
> 
> I am not sure what FLASHR is, maybe a tool to update firmware?
> 
> For UPX, the version with UPX-UCL library should be used, because
> it has the more free/libre license compared to the UPX NRV default:
> http://www.freedos.org/software/?prog=upx-ucl 
>  (a very nice tool!)
> 
>> Almost all of the dropped packages in the top of this thread, never
>> shipped with FreeDOS. However, they are on the Repo for v1.1.
> 
> This probably means that they got added to the distro after 1.1, in
> the hope that they will be included in the FreeDOS 1.2 distro. The
> users were able to install through the repository in the meantime.
> 
>> FreeDOS 1.1 shipped with 80 packages total, 1.2 ships with 97 the
>> slim USB and 232 on the big USB.
> 
> That is really cool, thanks :-)
> 
> By the way, it is good to have full 8.3 file names for packages now,
> the "X" and "S" distinction in the repo makes it hard to find stuff
> which normally has 8 char names but has to squeeze in the "X" suffix.
> 
> Regards, Eric
> 
> 
> 
>> Well, this was the complete list of packages included with FreeDOS
>> 1.1, all 80 of them.
> 
> Base: Append Assign Attrib Cdrcach(e) Chkdsk Choice Command Comp
> Cpidos Ctmouse Cwsdpmi Debug Defrag Deltree Devload Diskc(o)py
> Display Dosfsck D(i)skcomp Edit Edlin Exe2bin Fasth(e)lp Fc Fdapm
> Fdisk Fdpkg Fdupdat(e) Find Format Fourdos (4dos) F(d)xms286
> Graphic(s) Help Himemx Infozip Install Jemmex Kernel Keyb Label
> Lbacach(e) Localiz(e) Mem Mirror Mode More Move Mtcp Nansi Nlsfunc
> Printq Print Recover Replace Ripcord Samcfg Share Shsucdx Sort
> Subst Tree Uide Undel(ete) Unf(or)m(a)t Usbdos Xcopy Xmgr Dosutil
> 
> Boot: Sysl(i)n(u)x
> 
> GUI: Fdshell (?)
> 
> Net: Wattcp Wget
> 
> Util: Bootfix Callver Doslfn  Flashr Fdshield Upx Vmsmnt
> 
>> And here is the list of packages on the Large USB Stick.
>> All, 232 of them.

This is a repost/updated not included and problem 

Re: [Freedos-user] FreeDOS 1.2 Package LSM Data Verification

[Jerome E. Shidel Jr.]

Eric, 

> On May 18, 2016, at 12:24 PM, Eric Auer  > wrote:
> 
> 
> I would like to agree with Tom: It is good that FreeDOS comes
> with a nice collection of drivers for modern hardware! Those
> times when a DOS driver was included when people bought their
> CD drive have long passed. Also, there are no reasons to limit
> our distro to those minimal features of a few MS DOS disks ;-)

I am more than happy to include any suitable open source drivers.

> 
>>> an operating system without CDROM and network drivers doesn't sound
>>> very useful to me, even if everything has the correct license. YMMV.
>> 
>> I think that the key is to perceive FreeDOS as a replacement to MSDOS, 
>> nothing else (that is, "BASE")...
> 
> It is good to have a BASE download (probably with "live CD" or
> "live USB stick" function, not requiring but allowing install
> to other disks) if you want a basic no-nonsense system. Still
> I would like to see drivers included even in such a download.
> 
>> But then, for actually useful (practical) stuff, one has to rely on a 
>> FreeDOS distribution, like Svarog386, or collect the required "non-free" 
>> bits by hand over the internet.
> 
> It also is good to have a FreeDOS distro which contains a pile
> of nice useful free software, if possible fully open source. I
> think IBIBLIO also requires open source for the file hosting.
> 
> I would NOT want the FreeDOS distro to be limited by extremely
> specific license taste. As far as I am concerned, GPL 2 and 3,
> MIT, Artistic license, BSD license, public domain etc. are all
> perfectly fine for inclusion of packages in our normal distro.
> 
>> Otherwise I agree it can get a bit frustrating for actual users,
>> and that's the reason I started Svarog386 in the first place.
> 
> Looking at your package listing, Svarog386 is quite nice, but we
> should not give up the hope of having a nice plain FreeDOS distro.
> 
> Jerome, could you make a list of packages which existed in either
> FreeDOS 1.0 or 1.1 but are not currently included in 1.2, along
> with the reason for exclusion? I think we should indeed be a bit
> more generous regarding inclusion of packages! Thanks :-)
> 
> Regards, Eric
> 

Except for the following packages all other dropped and questionable packages 
are listed at the beginning of this thread. This list of packages shipped with 
1.1 and are not presently in 1.2. None of these packages are on the ibiblio 
repo for version 1.1 either.  I have not put any work into trying to include 
these packages as of yet.

DOSUTIL, No sources present in package. Might be buried on repos somewhere.
RIPCORD, FreeDOS release related program, Compatibility not tested. 
SAMCFG, I don’t know if it is applicable anymore.
SYSLNX, There has to be a newer version, not in repo for 1.1.
WATTCP, No Source files present
CALLVER, FLASHR, SHIELD and UPX not in repo for 1.1

Almost all of the dropped packages in the top of this thread, never shipped 
with FreeDOS. However, they are on the Repo for v1.1.

FreeDOS 1.1 shipped with 80 packages total, 1.2 ships with 97 the slim USB and 
232 on the big USB.


Well, this was the complete list of packages included with FreeDOS 1.1, all 80 
of them.

BASE\APPENDX
BASE\ASSIGNX
BASE\ATTRIBX
BASE\CDRCACHX
BASE\CHKDSKX
BASE\CHOICEX
BASE\COMMANDX
BASE\COMPX
BASE\CPIDOSX
BASE\CTMOUSEX
BASE\CWSDPMIX
BASE\DEBUGX
BASE\DEFRAG
BASE\DELTREEX
BASE\DEVLOADX
BASE\DISKCPYX
BASE\DISPLAYX
BASE\DOSFSCKX
BASE\DSKCOMPX
BASE\EDITX
BASE\EDLINX
BASE\EXE2BINX
BASE\FASTHLPX
BASE\FCX
BASE\FDAPMX
BASE\FDISKX
BASE\FDPKGX
BASE\FDUPDATX
BASE\FINDX
BASE\FORMATX
BASE\FOURDOSX
BASE\FXMS286X
BASE\GRAPHICX
BASE\HELPX
BASE\HIMEMXX
BASE\INFOZIPX
BASE\INSTALLX
BASE\JEMMEXX
BASE\KERNELX
BASE\KEYBX
BASE\LABELX
BASE\LBACACHX
BASE\LOCALIZX
BASE\MEMX
BASE\MIRRORX
BASE\MODEX
BASE\MOREX
BASE\MOVEX
BASE\MTCPX
BASE\NANSI
BASE\NLSFUNCX
BASE\PRINTQX
BASE\PRINTX
BASE\RECOVERX
BASE\REPLACEX
BASE\RIPCORDX
BASE\SAMCFGX
BASE\SHAREX
BASE\SHSUCDXX
BASE\SORTX
BASE\SUBSTX
BASE\TREEX
BASE\UIDEX
BASE\UNDELX
BASE\UNFMTX
BASE\USBDOSX
BASE\XCOPYX
BASE\XMGRX
BOOT\SYSLNXX
GUI\FDSHELLX
NET\WATTCPX
NET\WGETX
BASE\DOSUTILX
UTIL\BOOTFIXX
UTIL\CALLVERX
UTIL\DOSLFNX
UTIL\FLASHRX
UTIL\FSHIELDX
UTIL\UPXX
UTIL\VMSMNTX

And here is the list of packages on the Large USB Stick. All, 232 of them.

; BASE Packages

archiver\unzip
archiver\zip
base\append
base\assign
base\attrib
base\chkdsk
base\choice
base\command
base\comp
base\cpidos
base\ctmouse
base\debug
base\defrag
base\deltree
base\devload
base\diskcomp
base\diskcopy
base\display
base\dosfsck
base\edit
base\edlin
base\exe2bin
base\fc
base\fdapm
base\fdisk
base\fdxms
base\fdxms286
base\find
base\format
base\help
base\himemx
base\jemm
base\kernel32
base\keyb
base\keyb_lay
base\label
base\lbacache
base\mem
base\mirror
base\mkeyb
base\mode
base\more
base\move
base\nansi
base\nlsfunc
base\print
base\recover
base\replace
base\share
base\shsucdx
base\sort
base\swsubst
base\tree
base\undelete

Re: [Freedos-user] FreeDOS 1.2 Package LSM Data Verification

[Jerome E . Shidel Jr .]

> On May 18, 2016, at 10:12 AM, Tom Ehlert  wrote:
> 
>>> Without DOSLFN, no support at all for long filenames?
> 
>> Correct. Although, I hear the was another very buggy one that was
>> around before DOSLFN. I don’t know the name.
> 
> THIS.IS.RIDICULOUS.
> 
> one of the worst manifestations of Stallmanitis ever.
> 
> bye
> 
> Tom.

Tom,

I understand you may have strong feelings regarding this subject. However, name 
calling, labels, slander, racism and other inflammatory and degrading remarks 
are unacceptable behavior. I have zero tolerance for such games. 

Now, my opinion regarding open source. Could not care less. I have written and 
released Public Domain, Open Source, Freeware, Trialware and Extremely 
Copy-protected software and have every intention of doing so in the future. The 
only type I have not done is Shareware and even that is not do to some moral 
objection. I just don’t think that model works as intended.

For the packages that are to be included with the next OS release, I have been 
given several directives. Among those are that the software package should be 
open source and its sources need to be included. Public domain software is less 
restrictive than open source. So as long as its source is present, it is fine 
that that type of software is included. Other software that places additional 
restrictions on use, do not fit the given requirements. Exceptions may be made. 
But, that decision is not up to me. I have a moral obligation to evaluate all 
of the packages and insure they meet the requirements I was given. 

Is DOSLFN going to be dropped? I don’t know. It is not up to me and my opinion 
is not even relevant. I have not been informed of any decision to do so. The 
problem is its licensing is unclear. There is no licensing information 
contained in its source files or with its binaries. It may be Public Domain. I 
have no idea. 

Freely available source is not Open Source and is not Public Domain. All works 
are Copyright at the moment of their creation. Regardless if it is declared or 
not. However, it is nearly impossible to enforce a Copyright violation without 
said notice. But, would you like to see FreeDOS sued into non-existence do to a 
minor copyright violation?

Now in regards to my original quoted message. If DOSLFN is found to be 
unsuitable, I will not be hunting down an alternative to it.  Someone in either 
the freedos-user or devel group mentioned that there was another program that 
did lfn and it was very buggy. I have no idea what it is called. I have no idea 
if it is buggy. If you would like to find a suitable alternative, it can be 
considered for inclusion.

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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

> On May 17, 2016, at 8:23 AM, Tom Ehlert  wrote:
> 
>>CRYNWR - Unknown License, Dropped.
> 
>>GCDROM - Listed as GPL, No Sources, Based on XCDROM, Removed.
> 
> GCDROM sources are available.
> 
> 
>>UIDE - Free for non-commercial, Removed.
>>UMBPCI - Listed as free, No sources, Dropped.
>>XCDROM - Removed.
> 
> 
> 
> an operating system without CDROM and network drivers doesn't sound
> very useful to me, even if everything has the correct license. YMMV.
> 
> Tom

It still contains UDVD2, which can function as a CD-ROM driver.

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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

> 
> I can't imagine anyone taking stuff from a FreeDOS 1.2 release and
> *wanting* to issue it as a commercial product.  Rex released 4DOS as
> open source because it was no longer selling.  The world had moved on
> from MSDOS and 16 bit, and so had he.
> __
> Dennis

It is not an impossibility. For example, the current version of the commercial 
product
SpinRite runs on a FreeDOS boot CD. Although,  I hear the next version will be
adding Mac Support and dropping all Operating System for direct hardware access.
So, not the entire world has moved on yet.

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

[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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

Hello,

> >Just as a general statement regarding “Dropped” packages. It doesn’t >mean 
> >they cannot be used or installed later. It also doesn’t mean they cannot be
> provided on ibiblio.
> 
> I am a bit confused by this, it seems to be an "end-around" solution; has 
> this been happening all along?

I don’t feel like it is. I am talking about them having been dropped or removed 
them from the Official  FreeDOS 1.2 release. Most of the dropped packages never 
even shipped with FreeDOS. They could be added later by the user. However, for 
those packages that met Jim’s requirements and for user convenience many of 
these uninstalled packages can be provided as EXTRAS on the big USB stick and 
CD-ROM versions. This would let the user have many desired add-on programs 
available without any extra fuss. But, there are requirements for all packages 
that are to be included on the Official install mediums. 

Also, think of it this way. MS-DOS never shipped with SoundBlaster or Adlib 
drivers. Besides the extra floppies that would have required. There would have 
licensing concerns. However, there was no problem with a user installing those 
drivers later.

> >PS: Why so many IBIBLIO files, how about Mateusz' updater repository?

They are from there 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/

> Perhaps this is the ideal solution, trim FreeDOS to a genuine FREE/Open 
> Source distro, and let end-users include the files they wish from alternate 
> sites?

This is one of reasons for all of the specific requirements packages must meet 
for their inclusion.

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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

Hello Eric and all,

4DOS:

I fixed the missing source issue. If Jim is fine with including a 
“Non-commercial use only” program it can stay. Otherwise,
it will either have to be installed later or could be provided on
unofficial FreeDOS releases.

GCDROM:

The GCDROM are incomplete they only contain the XCDROM source.
Also, it states that it is based on XCDROM. XCDROM has been removed for 
other reasons. So, GCDROM even if fixed. It’s fate is in question.

UIDE:

Mostly, I think your interpretation matches mine. However, when UIDE was used
FDINST would throw random errors. Why? IDK. It was suggested that command 
line switches could be used to help correct the issue. However, that would not
be remotely practical and might have required having a different install media
fork for every platform and virtual machine. Per a different suggestion, 
switched
to using UDVD2 and the problems vanished. UDVD2 is by the same author and
may eventually suffer the same fate as UIDE, XCDROM, RDISK and XMGR. 


--
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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

> On May 15, 2016, at 1:26 AM, Rugxulo  wrote:
> 
> I assume that your .ZIPs of CuteMouse
> (ctmouse.zip) and Jemm386 (jemm.zip) come from here:
> 
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/base/

Yep, nearly all others are from ibiblio as well. 

There are some, that I have updated and a few like CDRCACHE that are not on 
ibiblio.

Also, several on ibiblio that were missing sources and a few others that LSM 
data problems that I corrected as well.

> 
> If that's the case, then I will (weakly) "try" to fix them in the next
> few days, and then re-upload them
> so that FD 1.2 will have a slightly less burdensome status. (Which
> means trying to rebuild all their various (sub)binaries, which
> shouldn't be "too" hard.)

Sounds good to me. :-)

> Honestly, this kind of task belongs to the maintainers of those
> aforementioned packages, but
> since most so-called maintainers are too busy (or long since
> disappeared), it falls to such
> pathetic souls such as myself. (Sigh.) :-(

Agreed. When, I see the “can’t you fix” this package or that one. Or, the "but 
there is a newer version of this one on the website why aren’t you using it?” I 
shake my head and sigh. 

> I just hate to drop some things that are, in fact, useful and "mostly"
> free just because of some errant file or two. Jemm386 I never use much
> anymore (although it's still very useful, in select cases; but JLOAD
> never caught on, quite honestly). CuteMouse might be a much bigger
> loss (although I personally try to avoid the mouse, usually, which
> isn't easy in some programs).
> 
> Neither should have to be dropped, so I'm 99% sure that I can remove
> the closed-source parts successfully. I know this isn't a "real"
> problem, thus we keep procrastinating, but we do overall want to keep
> FreeDOS "free" (or as close as possible!).

Just as a general statement regarding “Dropped” packages. It doesn’t mean
they cannot be used or installed later. It also doesn’t mean they cannot be
provided on ibiblio. It only means, (if not fixed) they will not ship with the
official release of FreeDOS 1.2. 



--
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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

> On May 15, 2016, at 1:17 AM, dmccunney  wrote:
>> [..]
>> 4DOS - Listed as Free, No Sources. Kept for now, may get Dropped?
> 
> 4DOS sources, for the original 7.50 release, and the later 8.0 release
> by Luchezar Georgiev may be found here, along with 4DOS original
> author Rex Conn's open source license:
> http://www.4dos.info/sources.htm#1
> 
> 4DOS is my command processor of choice under DOS.

Thanks for the link. I have attached the sources to the my build copy of the 
4DOS package.

However, clause 3 for its license makes it NON-COMMERCIAL use only.

(3) The Software, or any portion of it, may not be used in any commercial
  product without written permission from Rex Conn 

We will have to see if Jim is OK with keeping it in FreeDOS 1.2.


--
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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

> On May 15, 2016, at 12:41 AM, Thomas Mueller  wrote:
> [..]
> I don't know if DIALOG proposed for FreeDOS is the same as any of those 
> dialogs.

I think it is the “DIALOG” package that shipped with FD1.1.

> 
> Without DOSLFN, no support at all for long filenames?

Correct. Although, I hear the was another very buggy one that was around before 
DOSLFN. I don’t know the name.

> 
> Without GCDROM and XCDROM, will there be any way to read CDs and DVDs, and 
> possibly burn a CD or DVD?

There is still UDVD2. It has been permitted to remain for now. However, in the 
long term, Jim has stated he would like to see it replaced with another 
solution.

> 
> CURL is open-source and much used in (quasi-)Unix OSes.

CURL is probably fine. But, it completely failed LSM verification. It is listed 
as being GPL. It’s license is clearly not. I’m not looking at it right now. 
But, if I recall correctly, i think it was either BSD or BSD-like. There were 
basic directives played out regarding what packages get included in FD1.2. I 
temporarily bent these restrictions for a couple highly demanded packages like 
4DOS. But, for most, I did not. That being said, CURL should be fixable if the 
license info is corrected and sources are included.

> PING and WHICH are a common part of open-source (quasi-)Unix systems.

I didn’t do any temporary rule bending on these. They are probably fixable. 
However, I think there is a PING included in MTCP as well.

> 
> Available source code does not necessarily mean buildable in FreeDOS; porting 
> to DOS typically requires much wrestling and is not always workable.  
> Remember DOSzilla?
> 
> I couldn't find NEWSNUZ.

It is on the ibiblio repository. 

> 
> Some of the packages, such as UIDE, UMBPCI and XMSDISK, are DOS-specific.
> 
> I'm not trying to track down any of the games you listed.  Aside from 
> TETRIS2K (related to Tetris?), I never heard of any of the others, or didn't 
> pay attention.
> 
> Tom


--
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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

Hello, 

> On May 14, 2016, at 9:45 PM, Rugxulo  wrote:

> In particular, some software is "GPLv2 only" while others are "GPLv2
> (or later)" or even "GPLv2 (only) or GPLv3 (only)”.

I did not go into that fine of detail. 

But, someone should do that someday.

> [It's a mess.]

Very much so. Some are technically multiple licenses and really should be 
listed as such. For example: Some, maybe CLAMAV (Maybe not, I did just go 
hundreds of packages) that contains sources that range from GPLv2, 
LGPL 2.1, BSD, MIT…..

> 
>> Anyhow, these are the problem packages and their probable destinies.
>> 
>> ARCHIVER:
>> 
>> ZOO - Includes sources, may be Public Domain. No License information.
>> Dropped.
> 
> I already pointed you to Debian. Or just use older 2.01 if that
> worried. Or just use BOOZ, at least it can decompress. But hey, it's
> fairly obscure at this point, so I doubt most people even want it or
> know what it is.
> 
>> BASE:
>> 
>> No issues.
> 
> Really? Did you double-check JEMM (JLOAD.EXE + *.JLM) and CuteMouse
> (COM2EXE.EXE)

I did not evaluate every single file in each package. What I did was, locate 
and 
determine the license the package says it is released under (NOT the LSM DATA). 
If not present, searched all other readme, help and text documents. Then primary
executable sources and program resource data files. Finally, if it could not be 
determined,
some quick web searching. 

Without going into details, my free time gets more and more limited as we move 
into 
summer. So, I am not going to evaluate or bring into compliance individual 
files or
packages. I can either drop non-compliant packages. Or, I can replace them with 
compliant versions. I’m not trying to be a jerk. I just don’t have the spare 
time to 
devote to that level of detail on those kind of issues.

> [..]

>> UIDE - Free for non-commercial, Removed.
> 
> Uh, no. AFAIK, none of his variations were ever "non-commercial only"
> (which would neither be "open source" [OSI] nor "Free" [FSF]).

You are correct. It is just freely distributable. I must have some moved into a 
different
package when I was looking at the UIDE licensing. Oh well, it happens. But, 
regardless
of its licensing it was slated for removal.

> "
>   XMGR, RDISK, and UIDE are offered at no cost, "as is", "use at your own
>   risk", and with NO warranties, not even the implied warranty of FITNESS
>   for any particular purpose nor of MERCHANTABILITY!
> "
> 
> However, AFAIK, Jim (still) seems to think it would be better
> (overall) if we removed these. I don't personally know of any concrete
> legal reason to do so, only some irrational rants and behavior from
> Jack himself.


--
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 Package LSM Data Verification

[Jerome E. Shidel Jr.]

Hello John and All,

> I note that DOSLFN installs by default in FreeDOS 1.1, so if it is not kept 
> then the FD 1.2 installer would have to accommodate.

At present, DOSLFN is not installed with BASE. However, It is installed under 
ALL. I was unable to determine it’s license. It may be BSD, GPL, LGPL or even 
Public Domain. It is up to Jim to determine if it will just “ship” as-is or 
needs to be pulled. If it gets Dropped, no accommodations are planned for 
Windows Long File Name support. Sorry, not up to me.

> That's a shame about the MPXPLAY unknown license.  It's my standard MP3 
> player.

Unfortunately, for the most part, I had to go through all of the packages 
myself and could only devote so much time to packages that had poorly 
documented license information. While hunting down licenses, some packages like 
TESTDISK will even receive an upgrade. Others exceeded their allowed time and 
not being part of BASE or ALL, were defaulted to “Dropped." However, I don’t 
think any of the “Dropped” packages ever “shipped” with a FreeDOS release. That 
being said, you could always install them later or add them to your own 
customized USB stick ( see https://github.com/shidel/FDI/wiki ).

If you wish, you (or anyone else) might even find some spare time track down 
missing sources and license information to any of the “Dropped” packages. The 
“Removed” packages have been pulled for other reasons and probably not be 
included this or future releases of FreeDOS. 

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

[Freedos-user] FreeDOS 1.2 Package LSM Data Verification

[Jerome E. Shidel Jr.]

Hello All, 

It took some doing. But, I have gone through all both the packages proposed for 
the FreeDOS 1.2 release. So, here are the changes that have been implemented. 
Some of these are listed even though it was decided beforehand that they were 
going to be pulled. One or two, have problems and aI am waiting on a decision 
from Jim to determine their fate. I have corrected nearly all packages with 
incorrect license types and versions. For example:

BASE\APPEND was just GNU GPL, but is GNU General Public License, Version 2
DEVEL\REGINA was listed as GPL, but is actually GNU Library General Public 
License, Version 2
DEVEL\NASM has moved from GPL  to Simplified (2-Clause) BSD License.
etc…

Anyhow, these are the problem packages and their probable destinies.

ARCHIVER:

ZOO - Includes sources, may be Public Domain. No License information. 
Dropped.

BASE:

No issues.

DEVEL:

PACIFICC - Free. No Sources. Dropped.
TPPATCH - Free. No Sources. Dropped.

GAMES:

CHICKEN2 - Listed as Emailware. DOC says "This means that if you like 
the game, please
please please send me an email or a postcard!” Include or Leave Dropped?

ELIZA - Listed as Public Domain. No License information. Leaving as 
Public Domain.

JUMPBUMP - Email author required. Dropped.

NYET - Listed as GPL, No Source, Dropped.

PAKUPAKU - Unknown License, Dropped.

PEDE - Unknown License, Dropped.

QUADNET - Freeware, no source, Dropped.

TETRIS2K - Listed as Free, Possibly Public Domain. No license 
information. Dropped.

XARGON - Two Licenses, One COMMERCIAL do not redistribute. AND Freeware 
License??? Dropped.

NET:

CRYNWR - Unknown License, Dropped.

CTORRENT - Listed as GPL, No License, No Sources. Dropped.

CURL - Listed as GPL, it is not. No Sources. Dropped.

NEWSNUZ - Listed as Public Domain. New parts are. Old parts say to 
reference missing file. Dropped.

PING - Listed as GPL, No Sources. Dropped.


SOUND:

ADT2 - Fair License? Dropped.

BLADEENC - LGPL, No Sources, Dropped.

DWJ - Freeware, No Sources, Dropped.

MPXPLAY - Unknown License, Dropped.

UTIL:

4DOS - Listed as Free, No Sources. Kept for now, may get Dropped?

BIEW - Listed as correctly as GPL, No Sources. Dropped.

DESI3 - Listed as Freeware, Unknown License, No Sources, Dropped.

DIALOG - Listed as GPL, No Sources, Dropped.

DOSIDLE - Free for non-commercial use, Dropped.

DOSLFN - Listed as GPL, No License Messages, Keep?

GCDROM - Listed as GPL, No Sources, Based on XCDROM, Removed.

LSCOLOR - Listed as Public Domain, No Sources, Dropped.

MD5SUM - Listed as GPL, is Public Domain, contains several different 
OSS licenses. Unchanged.

MEMTEST - Listed as Freeware, Unknown License, No Sources, Dropped.

SAVEPART - Listed as Free, No Sources. Dropped

SLOWDOS - Unknown License, No Sources, Dropped.
(Replacing with SLOWDOWN, Hopefully)

TINYAES - Listed as Free, Unknown License. Dropped.

UIDE - Free for non-commercial, Removed.

UMBPCI - Listed as free, No sources, Dropped.

WHICH - Listed as GPLv2, No Sources, Dropped.

XCDROM - Removed.

XMSDISK - Listed as Freeware, No Sources, Dropped.

Thats all folks. :-)

Thanks, 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 needs you

[Jerome E. Shidel Jr.]

> On May 12, 2016, at 6:19 PM, Rugxulo  wrote:

[..]

> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/pkgs/commands.zip

[..]

Thanks, 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 needs you

[Jerome E. Shidel Jr.]

So far, I have gone through all of the ARCHIVER and BASE packages and have 
corrected their LSM data.

In those groups, these packages have not been solved. 

Unknown license information and will probably be dropped from release,

ARCHIVER/ARJ
ARCHIVER/ZOO

Missing sources,

BASE/COMMAND

Yet to verify all packages on previously posted list in groups

DEVEL
EDIT
EMULATOR
GAMES
NET
SOUND
UTIL


Thanks, 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 needs you

[Jerome E. Shidel Jr.]

Updated list of packages that still need LSM data and License version 
verification.

; FreeDOS Installer Package List File

; BASE Packages

archiver\unzip
archiver\zip
base\assign
base\attrib
base\chkdsk
base\choice
base\command
base\comp
base\cpidos
base\ctmouse
base\debug
base\defrag
base\deltree
base\devload
base\diskcomp
base\diskcopy
base\display
base\dosfsck
base\edit
base\edlin
base\exe2bin
base\fc
base\fdapm
base\fdisk
base\fdxms
base\fdxms286
base\find
base\format
base\help
base\himemx
base\jemm
base\kernel
base\keyb
base\keyb_lay
base\label
base\lbacache
base\mem
base\mirror
base\mkeyb
base\mode
base\more
base\move
base\nansi
base\print
base\recover
base\replace
base\share
base\shsucdx
base\sort
base\swsubst
base\tree
base\undelete
base\unformat
base\welcome
base\xcopy
util\cwsdpmi
util\fdnpkg
util\graphics
util\shsufdrv
util\udvd2

; ALL Packages

archiver\bz2
archiver\gzip
archiver\lzip
archiver\lzma
archiver\lzop
archiver\tar
edit\msedit
net\mtcp
net\wget
util\4dos
util\biew
util\bmp2png
util\bootfix
util\cdrcache
util\cpied
util\daa2iso
util\dos32a
util\doslfn
util\foxcalc
util\gcdrom
util\gnubc
util\grep
util\less
util\localize
util\lscolor
util\md5sum
util\memtest
util\part
util\pg
util\srdisk
util\tee
util\touch
util\usbdos
util\which
util\xfdisk
util\zerofill

; EXTRA Packages

archiver\arj
archiver\cabext
archiver\lha
archiver\lpq1
archiver\p7zip
archiver\unrar
devel\bcc
devel\bwbasic
devel\cpp2ccmt
devel\djgpp
devel\djgpp_bn
devel\djgpp_bs
devel\djgpp_db
devel\djgpp_fq
devel\djgpp_fx
devel\djgpp_gc
devel\djgpp_gp
devel\djgpp_mk
devel\djgpp_ob
devel\djgpp_rh
devel\djgpp_tx
devel\euphoria
devel\fasm
devel\fbc
devel\fbc_help
devel\fpc
devel\insight
devel\jwasm
devel\nasm
devel\ow
devel\perl
devel\regina
devel\runtime
devel\tppatch
devel\upx
edit\blocek
edit\doshexed
edit\e3
edit\elvis
edit\fed
edit\mbedit
edit\pico
edit\tde
edit\uhex
emulator\atari800
emulator\chip8
emulator\fceu
emulator\meka
emulator\mines
emulator\nosefart
emulator\simcoupe
emulator\sneese
emulator\teo
emulator\vice
emulator\xf25
emulator\z26
emulator\zboy
games\boom
games\btitanic
games\eliza
games\empong
games\ewsnake
games\fmines
games\freedoom
games\frotz
games\gnuchess
games\hangman
games\happylnd
games\ivan
games\kiloblas
games\kraptor
games\lincrawl
games\liquiwar
games\magnetic
games\mirmagic
games\nethack
games\nge_nibb
games\nyet
games\psrinvad
games\qtetris
games\quadnet
games\snova
games\sudoku86
games\tetris2k
games\vertigo
games\vitetris
games\wing
games\ww1
games\xargon
games\zmiy
net\ctorrent
net\curl
net\dillo
net\ethtools
net\gopherus
net\htget
net\newsnuz
net\ntool
net\picosntp
net\picotcp
net\ping
net\rsync
net\vncview
sound\adplay
sound\bladeenc
sound\dosmid
sound\dwj
sound\gsplay
sound\lame
sound\mplayer
sound\mpxplay
sound\opencp
util\ansimat
util\b64
util\clamav
util\clamdb
util\desi3
util\dialog
util\dn2
util\doszip
util\fdshell
util\foxtype
util\gifsicle
util\hexcomp
util\hip
util\hiram
util\localcfg
util\lptdrv
util\ntfs
util\opengem
util\ozonegui
util\password
util\pbox
util\pcisleep
util\pngcrush
util\savepart
util\search
util\sqlite
util\terminal
util\testdisk
util\tinyaes
util\unrtf
util\utf8tocp
util\wde
util\xgrep

; Thats all folks.

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

> 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 Missing Packages and XDEL

[Jerome E. Shidel Jr.]

Hello Alain,

> I could not find your fix at 
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/ 
> ,
> where can I get the fixed version, just in case I need to release some future 
> fix…

I am not responsible for the packages provided by the Repo.

For now, until the next release that will include xDel, you can retrieve 
the updated version from my server at http://dnld.lod.bz/xdel.zip

> 
> My pack inculdes 3 locales, en, pt_br and es (I believe that by Aitor SM).
> Maybe some more come by ;-)
> 
> Alain
> 

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 Missing Packages and XDEL

[Jerome E. Shidel Jr.]

> Hello Alain,

> Here is the XDEL zip file: 
> https://www.dropbox.com/s/5xah8zlociu59yi/xdel206b.zip?dl=0
> 
> I updated the LSM but I am not 100% sure if the zip file is in 
> accordance with the rules, specially the HISTORY.TXT file.
> If needed just send me a word and I can fix it

For the most part, I think it all looked ok. 

I corrected the issues I found. Basically, the LSM needed to be in a 
APPINFO directory and the doc needed to be moved as well.
Finally, Jim doesn’t want it to just say “GPL.” So, I expanded
that to “GNU General Public License” in the LSM. 

I will include it in future builds and probably in the ALL package set.

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

[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

[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 needs you

[Jerome E. Shidel Jr.]

> What did we decide about XMGR?

XMGR along with UIDE and several other packages have been dropped from FreeDOS 
1.2.

This was not my decision. But, I completely agree with the reasoning behind 
their removal.

These are still available on the ibiblio repository. So, if you really need 
them in your version of FreeDOS 1.2. You can easily add them to your copy of 
one of the USB sticks. Then, running “fdimples /config” from the USB stick, you 
can even always have them install. 

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

[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

[Freedos-user] FreeDOS 1.2 Missing Packages and XDEL

[Jerome E. Shidel Jr.]

Hello Alain, 

I mentioned several days ago, that if there anything additional anyone wanted 
included to let me know.

But, it is still not to late.

However, XDEL is not on the FreeDOS Repo.

As long as I receive it. It is open source and includes the source. Is packaged 
up with the proper LSM data.

I can include it on future releases.

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

[Freedos-user] FreeDOS 1.2 needs you

[Jerome E. Shidel Jr.]

Hello All, 

FreeDOS 1.2 needs your help verifying package information. This is one of the 
main holdups for the
next OS release. Verifying this data is correct is essential. Especially the 
the licensing information.  
GPL, GPLv2, MIT, BSD …… Other information, such as website, authors and etc, 
should also be
 verified and updated.

So, please select some of these packages that you can verify the 
APPINFO\.LSM text file
data. The sooner this is done, the sooner we can have FreeDOS 1.2. :-)

Update this thread to prevent double work and directly email me the updated LSM 
file(s) (subject 
PKGNAME.LSM to prevent being filtered as spam) I have already removed a couple 
packages for 
which I know the information is correct.

Thank you in advance, Jerome

; FreeDOS Installer Package List File

; BASE Packages

archiver\unzip
archiver\zip
base\append
base\assign
base\attrib
base\chkdsk
base\choice
base\command
base\comp
base\cpidos
base\ctmouse
base\debug
base\defrag
base\deltree
base\devload
base\diskcomp
base\diskcopy
base\display
base\dosfsck
base\edit
base\edlin
base\exe2bin
base\fc
base\fdapm
base\fdisk
base\fdxms
base\fdxms286
base\find
base\format
base\help
base\himemx
base\jemm
base\kernel
base\keyb
base\keyb_lay
base\label
base\lbacache
base\mem
base\mirror
base\mkeyb
base\mode
base\more
base\move
base\nansi
base\nlsfunc
base\print
base\recover
base\replace
base\share
base\shsucdx
base\sort
base\swsubst
base\tree
base\undelete
base\unformat
base\welcome
base\xcopy
util\cwsdpmi
util\fdnpkg
util\graphics
util\shsufdrv
util\udvd2

; ALL Packages

archiver\bz2
archiver\gzip
archiver\lzip
archiver\lzma
archiver\lzop
archiver\tar
edit\msedit
net\mtcp
net\vmsmount
net\wget
util\4dos
util\biew
util\bmp2png
util\bootfix
util\cdrcache
util\cpied
util\daa2iso
util\dos32a
util\doslfn
util\foxcalc
util\gcdrom
util\gnubc
util\grep
util\less
util\localize
util\lscolor
util\md5sum
util\memtest
util\part
util\pg
util\srdisk
util\tee
util\touch
util\usbdos
util\which
util\xfdisk
util\zerofill

; EXTRA Packages

archiver\arj
archiver\cabext
archiver\lha
archiver\lpq1
archiver\p7zip
archiver\unrar
devel\bcc
devel\bwbasic
devel\cpp2ccmt
devel\djgpp
devel\djgpp_bn
devel\djgpp_bs
devel\djgpp_db
devel\djgpp_fq
devel\djgpp_fx
devel\djgpp_gc
devel\djgpp_gp
devel\djgpp_mk
devel\djgpp_ob
devel\djgpp_rh
devel\djgpp_tx
devel\euphoria
devel\fasm
devel\fbc
devel\fbc_help
devel\fpc
devel\insight
devel\jwasm
devel\nasm
devel\ow
devel\perl
devel\regina
devel\runtime
devel\tppatch
devel\upx
edit\blocek
edit\doshexed
edit\e3
edit\elvis
edit\fed
edit\mbedit
edit\pico
edit\tde
edit\uhex
emulator\atari800
emulator\chip8
emulator\fceu
emulator\meka
emulator\mines
emulator\nosefart
emulator\simcoupe
emulator\sneese
emulator\teo
emulator\vice
emulator\xf25
emulator\z26
emulator\zboy
games\boom
games\btitanic
games\eliza
games\empong
games\ewsnake
games\fmines
games\freedoom
games\frotz
games\gnuchess
games\hangman
games\happylnd
games\ivan
games\kiloblas
games\kraptor
games\lincrawl
games\liquiwar
games\magnetic
games\mirmagic
games\nethack
games\nge_nibb
games\nyet
games\psrinvad
games\qtetris
games\quadnet
games\snova
games\sudoku86
games\tetris2k
games\vertigo
games\vitetris
games\wing
games\ww1
games\xargon
games\zmiy
net\ctorrent
net\curl
net\dillo
net\ethtools
net\gopherus
net\htget
net\newsnuz
net\ntool
net\picosntp
net\picotcp
net\ping
net\rsync
net\vncview
sound\adplay
sound\bladeenc
sound\dosmid
sound\dwj
sound\gsplay
sound\lame
sound\mplayer
sound\mpxplay
sound\opencp
util\ansimat
util\b64
util\clamav
util\clamdb
util\desi3
util\dialog
util\dn2
util\doszip
util\fdshell
util\foxtype
util\gifsicle
util\hexcomp
util\hip
util\hiram
util\localcfg
util\lptdrv
util\ntfs
util\opengem
util\ozonegui
util\password
util\pbox
util\pcisleep
util\pngcrush
util\savepart
util\search
util\sqlite
util\terminal
util\testdisk
util\tinyaes
util\unrtf
util\utf8tocp
util\wde
util\xgrep
 
; Thats all folks.



--
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] Something to look forward to when Preview 17 is released.

[Jerome E. Shidel Jr.]

> On May 3, 2016, at 2:12 AM, Thomas Mueller  wrote:
> […]
> Now I wonder if FDI will run in DOSBox running under FreeBSD, NetBSD or 
> Linux.  

FDI since Preview 13 or 14 (I think), runs fine under DOSBox on a Mac.

1) Assume you have setup a C: drive for DOSBox.
2) Either:
a) Copy entire USB stick contents to a directory and mount that dir as 
drive D: in DOSBox
or
b) Just mount the USB image and mount it’s root as drive D: in DOSBox.
3) Switch to drive D:
4) run “setup”
5) answer FDI prompts

A Couple Notes: 

First, FDI does not do a complete FreeDOS install under DOSBox. It 
basically, installs 
all of the FreeDOS programs and creates a C:\AUTOEXEC.BAT for running the 
FreeCOM
shell on top of the DOSBox kernel. I felt this was better this way. It allows 
you to still interact
with the DOSBox filesystem from the HOST without doing anything special. You 
would probably
also want  to modify your Z:\AUTOEXEC.BAT to run the C:\AUTOEXEC.BAT at 
startup. I did not
have FDI do this automatically. 

> Or maybe boot from GRUB2 or grub4dos.

^O^

>  I would install to USB stick, probably 4 GB; would likely use factory 
> partitioning, would have to check cluster size so as not to be > 4 KB, might 
> have to reformat from NetBSD or FreeBSD.  Possibly install to 
> hard-disk/USB-stick image and then dd or rsync to USB stick?
> 
> It would be helpful if you could say how to boot FreeDOS using GRUB2, 
> grub4dos or Syslinux; then I might be able to run SYS to make a nonbootable 
> USB stick bootable.  Or would the boot be via Syslinux?

^O^

> But when I ran SYS on USB-stick installation of FreeDOS 1.1, the file system 
> was rendered nonreadable; I had to start over beginning with newfs_msdos from 
> FreeBSD.

What happens if you try it with the version of utilities in Preview 16?

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

[Freedos-user] Something to look forward to when Preview 17 is released.

[Jerome E. Shidel Jr.]

Well, FDI Preview 17 is not out yet. But, I though I would tell you about a new 
feature for the Power Users. The USB stick versions will contain a command line 
utility to recreate the entire FDI Build environment. So, all you FreeDOS 
hackers out there can build your own personal completely customized installer. 

From download to a built release, the whole process takes under 10 minutes. I 
put a Mac+VirtualBox demo video up on Youtube at https://youtu.be/rKAq7HEQ1oE 
 This feature is not available with the current 
public Preview 16 release. But, it will give you something cool to look forward 
to in Preview 17.

A text version is available on the FDI wiki at 
https://github.com/shidel/FDI/wiki 

The FDI Build environment creation utility and the mkFDI release build utility 
are both V8Power Tools enhanced batch files running under FreeDOS 1.2-pre. The 
actual build process is a very complex batch file and is kind cool to watch. If 
you just want to check out that, jump in a bit and just watch it from here mark 
https://youtu.be/rKAq7HEQ1oE?t=6m45s 

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

[Freedos-user] FDI Preview 16

[Jerome E. Shidel Jr.]

Hello all,

FreeDOS 1.2 - FDI Preview 16 is now available for download at 
http://up.lod.bz/FDI

It now includes a Boot Floppy, 32mb Slim USB, 512mb USB and 400mb+ Bootable CD. 

Booting the CD is not supported under VirtualBox. 
It requires booting the install floppy and just using the CD. 
Or, booting and using one of the USB images.

This is pretty much you final chance to provide input on what packages are
included with FreeDOS 1.2. The BASE and ALL package installation sets
have been mostly finalized. However, there may be a little flexibility remaining
in the EXTRA (included, but uninstalled) on big USB and CD images.

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] FDI Preview 15, Update 3

[Jerome E. Shidel Jr.]

Hello Mateusz and All,

> *** freezing ***
> After my C: drive being partitioned, the installer restarted and 
> formatted the drive. Then, it displayed a message "Gathering some 
> information to prepare for the installation."
> note 1: the message should end with 3 dots "installation...", since it's 
> something "in progress"
> note 2: my installation stopped there, since this screen never went 
> away. tested on VirtualBox with 8M of RAM and a 256M virtual drive. I 
> used all_cd.iso for the installation ("FreeDOS 1.2-pre15"), with the FDI 
> bootdisk downloaded from your website.

Freezing: I have Good news and Bad news.

First the Good news,

While running down this issue, I made a little streaming in FDI moving the
MEDIA detection routings out of STAGE700 (The prompting questions STAGE)
into STAGE600 (was unused as reserved). Makes it a little easier to follow
what is going on if reading through the batch sources.

Second, this led me to creating a CD iso version. So, I could run down the 
issue without saying hey Mateusz try this. now this. now this. now this…... 

Third, I was able to pinpoint exactly when the freeze occurred. It was
happening when checking for a files existence on the CD media. This 
led me to find a completely unrelated bug in vfdutil that would occur
if bad command line parameters were given to vfdutil. 

Also, this issue only occurred in VirtualBox when booting the CD. This
does not occur in VMware. It does not occur when using the USB versions
in either virtual machine. I did not test the CD version with QEMU. 

Finally, after spending a couple hours tracking down the exact problem, the 
issue
is not a bug in FDI or V8Power Tools. The problem occurs even when FDI is not 
run
and if no V8Power Tools are ever used.

Now the bad News,

I don’t know where the bug is located. It could be VirtualBox, FreeDOS kernel, 
FreeCOM shell, Himemx, UDVD2, SHSUCDX or possibly the boot disk configuration. 
(Note: removing LBACACHE had no effect on the bug.) 

This does not just effect FDI it effects other programs as well. For example,
the FreeDOS EDIT program. (Boot ALL_CD image, change to CD drive. Run edit. 
System Lockup)

A couple easy tests to replicate issue.

Create a VM in VirtualBox (with a Hard Drive, other settings like RAM 
are unimportant)

Boot the ALL_CD.iso. 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/all_cd.iso

Select Language in FDI, then exit to DOS.

Change to CD drive. (Should be D:)

Run any of the following:

edit(immediate freeze)

vfdutil /u D:\test   (in a stripped down config, it will 
run once without a lockup)

In summary, 

As best as I could determine, this bug occurs when reading the directories on 
the
CD ROM. Possibly a FindFirst/Next issue. Once i ruled out FDI and V8, I stopped
tracking down the issue.

Unless the non-FDI issue is resolved, the CD iso will not be able to install 
FreeDOS 
under VirtualBox. VirtualBox will only be able to use the USB images.

I also tested a completely stripped down startup config that only loaded 
HIMEMX, 
COMMAND, UDVD2, SHSUCDX and did not load FDI or any V8Power Tool. The 
problem still existed.

There may be a VirtualBox specific setting or switch needed for one of those 
programs that I don’t know. If not then it is a bug. 

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 16

[Jerome E. Shidel Jr.]

> On Apr 19, 2016, at 5:55 PM, Louis Santillan  wrote:
> 
> That would have been my argument.  The default imaging/image writing
> tools do not automagically expand the filesystem.  But, if you include
> a tool that could do off-line or on-line FAT expansion with freespace
> detection, that would be a killer feature.

Yes, that would be nice. But, time is scarce lately. :-)

Lets not forget. You could build the FDI install media from scratch to any size
you wish. 

I really need to put that in the github wiki and do a series of FDI hacking 
videos 
to cover all the basic tweaks and enhancements that can been done to FDI
with almost no effort. Things like adding custom packages to the media. 
Changing the default package selections. Post install system configurations.
Custom question prompts. Designer OS versions and Names. All kind of 
cool stuff that FDI is built to handle.

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 16

[Jerome E. Shidel Jr.]

Hello Jim,

Oops, I forgot to answer this part.

> For putting the image on a USB fob drive, wouldn't you use Live USB
> Creator or some similar tool anyway, so the 2GB thing doesn't matter?
> Live USB Creator allows you to set aside extra space on the target fob
> drive as writable space. 

I think most of us Mac and Linux users would just use dd. 

I’ve never tried that Live USB  Creator. Does it automatically expand 
the filesystem to fit the drive?

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

[Freedos-user] FreeDOS 1.2 - Preview 16

[Jerome E. Shidel Jr.]

Hello All,

At present there are two USB of FDI, 32MB and 512MB. 

Who would like the 512MB version expanded to 2GB in Preview 16?

This would not effect the download size or installed software.

However, it would require a 2GB USB drive instead of only 512MB.

The only benefit I see in doing this would be to allow the user 
to stick a whole lot of other stuff on their USB stick.

Any thoughts?

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] FDI Preview 15, Update 3

[Jerome E. Shidel Jr.]

Hello Jim and All,

Changed the English language “Select Language” text.

Changed all “wish to” to “want to”.

I removed all of the Periods for options.

I removed the Background fill character from the default theme.

(That all took about 2 minutes)

Waiting on reply from Jim to finalize default theme color scheme.

I could not locate the typo in:

"Yes - Partition drive %1"

Do you mean that it says “Partition drive D:?”  If so, that is not a typo
it is the true drive letter where FreeDOS will be installed. Usually, when
booting from a USB stick under DOS, the BIOS pushes the C: drive down 
a letter to D:.  On some systems, it does not. FDI does some detection
to determine wether C: or D: should be the target for the installation.

I understand this can be a little confusing to the user. I think it would be
a very bad idea to always just say C:. However, with just a little work,
I could have Normal mode just refer to it as “your hard drive” and other
vague terms.


> My suggestion is to leave it as-is, and add a note in the release notes for 
> folks who use VirtualBox. I think "not compatible with VirtualBox" means it 
> doesn't break/damage anything, it just doesn't work (well). If so, that 
> suggests it's okay to leave in.

Sounds good to me. It basically locks up immediately during the loading of 
JEMMX. Maybe later, if I get around to adding a VirtualBox detector to V8Power 
Tools. I will have it set a different default option for VirtualBox during 
installation.

> 
> 2) 4DOS is always shown as a boot option. At present, 4DOS is not installed 
> with BASE. It is only installed with ALL. Always Remove, Remove if not 
> installed, Always install, Ignore issue?
> 
> I saw that, and also noted that it only worked if you installed all packages. 
> But a quick reboot lets someone pick something else.
> 
> Option 1 is to leave it in, and add a note on the option like "(only if you 
> installed everything)". But that might be awkward.
> 
> Option 2 would be to remove the option, and assume only power users will 
> experiment with 4DOS. These users can edit their own CONFIG.SYS to specify 
> 4DOS.

I will just remove the 4DOS option from the CONFIG.SYS file. Easiest for me. :-)

Thanks again. 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

[Freedos-user] FDI Preview 15, Update 3

[Jerome E. Shidel Jr.]

Hello All,

Sorry that it took so long, but I have been swamped the last couple weeks. 

Anyhow, I updated vinfo in V8Power tools to detect QEMU. So, FDI should no 
longer get stuck by trying to create a RAMDRIVE or have issues under QEMU 
emulation.

Preview 15 Update 3 is now available at http://up.lod.bz/FDI

Thans for your patients, 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] 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

[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

[Jerome E. Shidel Jr.]

> On Apr 4, 2016, at 6:13 PM, Rugxulo <rugx...@gmail.com> wrote:
> 
> Hi,
> 
> On Mon, Apr 4, 2016 at 12:28 AM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> 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

[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

[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] FreeDos booting from a USB stick

[Jerome E. Shidel Jr.]

> On Mar 29, 2016, at 1:26 PM, Thomsen Thomsen  wrote:
> 
> Hello. I managed to create a bootable USB key running FreeDos using Rufus 
> (http://www.howtogeek.com/136987/how-to-create-a-bootable-dos-usb-drive/). It 
> works well and boots fine. I even managed to move files to the USB key. I 
> wanted to install some of the programs from http://www.freedos.org/software/. 
> In general I couldn't get this to work. Is there a way to get the "full 
> install" on a bootable USB key? I don't have a bunch of experience.

Hello, 

I recently made some additions to FDIMPLES and the FreeDOS Installer Preview 
USB stick images.

http://up.lod.bz/FDI

So, starting with FDIMPLES 0.9.1, you can easily update what packages get 
installed with
both BASE and ALL on the distributed USB stick images. You can make additions 
and 
removals to both package sets permanently to you USB stick. This would include 
packages
that are not even on the shipped install media.

Simply add you package to an appropriate subdirectory under \FDSETUP\PACKAGES 
like
GAMES, UTIL or even a new directory like MYSTUFF.

You should boot the install media and quit to DOS.

Run “fdimples /config”

You can then locate your package and set it’s state to none, B or A (not 
installed, 
BASE or BASE + ALL) by using the space/enter key. 

When finished making changes, select OK and the package lists for that USB stick
wil be updated.

If you wish, you can copy the packages LSM file to the \FDSETUP\PKGINFO as a 
.TXT
file. But, this is not required. However, it does allow FDIMPLES to display the 
package 
description information.

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

[Freedos-user] Minor update to FDI Preview 15

[Jerome E. Shidel Jr.]

Hello All, 

I just wanted to let you know I just pushed a minor update to FDI Preview 15.

I noticed that occasionally under DOSBox, the installer would hang at startup. 
The RAM drive program would get stuck sometimes. Since temporary storage
is not absolutely required at that point I just have it skip it under DOSBox.

It also includes an update to FDIMPLES 0.9.1. Mostly, the update adds a 
common-line switch /config that allows no-fuss editing of the BASE and ALL 
package lists on the install media. So, let’s say you never install DOSLFN, 
you can turn it off easily and permanently.

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] Boot FreeDOS (Black screen/blinking cursor)

[Jerome E. Shidel Jr.]

Hello Matt,

> I don't understand. I don't see AHCI.SYS or UIDE/UDVD in the FDI image.

Don is referring to line 18 in the autoexec.bat

DEVLOAD /H /Q %dosdir%\BIN\UDVD2.SYS /D:FDCD0001

> This particular disk has never never been GPT and the table is obliterated 
> anyway because I dd'd the FDI image to the disk itself, not a partition.
> 
> Any idea where I might be able to get those files without running an .exe. I 
> can't run an exe, at least not until I get FreeDOS installed.

Assuming the EXE is an executable archive, you could use the free DOSBox or 
Virtual Box on Linux to extract the exe.

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] Boot FreeDOS (Black screen/blinking cursor)

[Jerome E. Shidel Jr.]

Hello Matt,

> In the Boot tab in my BIOS, the menu for Xst Boot has CD, USB Floppy, USB CD, 
> etc, etc and UEFI at the bottom. Usually I have UEFI as first and only boot. 
> However, I've changed it to USB Floppy (I dunno why it thinks it's a floppy) 
> as first and only, no UEFI. I can't see any option to disable UEFI more than 
> that.

When you try to boot the image, if you only see a blank screen with blinking 
cursor, and you never see the “FreeDOS kernel 2041……..” messages, the kernel is 
either not compatible or is not being loaded. Unfortunately, I don’t know 
enough about your specific hardware. So, I cannot say if it is not compatible 
with FreeDOS. Or, what exact settings you would need to make to get it to run 
the OS. 

Perhaps, if you submit the information for your BIOS manufacturer and version, 
someone may know exactly what to change. Or, possibly may be familiar with 
getting FreeDOS to work in a similar situation. 

Sorry that I could not be of greater assistance.

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] Boot FreeDOS (Black screen/blinking cursor)

[Jerome E. Shidel Jr.]

Hello Matt,

> On Mar 30, 2016, at 6:15 AM, matthew berardi  wrote:
> 
> Hi Jerome,
> Thanks a lot for the response.
> I dd'd that image onto a hard drive. I could mount it and see DOSy looking 
> stuff. I tried to boot off it as USB and internal SATA and got the same black 
> screen with blinking cursor :(
> Both ways my BIOS detected it as an option for boot. I've pulled EVERYTHING 
> out of the computer, only 8GiBs RAM, no video card. Could it be some BIOS 
> setting I missed? Does it get cranky about USB keyboards? It doesn't feel 
> like there are enough variables for it not to work.


My best guess is that your BIOS is configured for UEFI+GPT boot media. Check 
your BIOS settings for an MBR boot option. 
Also, anything that says Legacy try to enable. Like maybe "Legacy USB keyboard 
support”

I don’t know when (or if) FreeDOS will support a UEFI+GPT only system.

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] FreeDos booting from a USB stick

[Jerome E. Shidel Jr.]

Hello,

> On Mar 29, 2016, at 1:26 PM, Thomsen Thomsen  wrote:
> 
> Hello. I managed to create a bootable USB key running FreeDos using Rufus 
> (http://www.howtogeek.com/136987/how-to-create-a-bootable-dos-usb-drive/). It 
> works well and boots fine. I even managed to move files to the USB key. I 
> wanted to install some of the programs from http://www.freedos.org/software/. 
> In general I couldn't get this to work. Is there a way to get the "full 
> install" on a bootable USB key? I don't have a bunch of experience.

FYI, I just updated FDI to Preview 15. http://up.lod.bz/FDI
It includes may more packages on the USB version. 

Switching into advanced mode during the installation provides an 
easy way to include these packages on a per/install basis.
You can switch into advanced mode by pressing CTRL+C at the
"Welcome To FreeDOS” screen or at any other time FDI is waiting
for you to pick an option.

The best method to add programs to a custom install stick is to
create a FDI build environment and update the package lists.

However, there is an easy way to add stuff to your own “ALL” install.

1) Place the new packages in the appropriate directory:

FDSETUP\PACKAGES\BASE
FDSETUP\PACKAGES\UTIL
….

2) Add the package to the proper list on the install media:

FDSETUP\SETUP\FDPLBASE.LST
FDSETUP\SETUP\FDPLALL.LST

3) your done. But, you may want its information to show
up in FDIMPLES. So you will need to place a copy of
the package LSM file in the FDSETUP\PKGINFO directory
as a TXT file. You could use 

FDIMPLES /LISTS to create the package lists. However, 
you will need to copy and rename them. FDIMPLES’ list
editing is designed to work with the raw source and FDI
build environments and will require a little extra work 
to use on a pre-built usb image.

Sometime in the hopefully near future, I want to create a couple
YouTube videos on using FDI to build custom releases and
FreeDOS based operating systems.

So, if you have a package for a utility called MYTHING.ZIP

add it to:

FDSETUP\PACKAGES\UTIL

Add util\mything to both or either:

FDSETUP\SETUP\FDPLBASE.LST
FDSETUP\SETUP\FDPLALL.LST

If you wish to create a custom package from scratch,
study one of the simple packages that ship with FDI.
You will need to mimic the directory structor in the 
zip archive. Also, you will need to create a custom
LSM (package information file) in the APPINFO\
directory. 

Hope this helps a little.

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] Preview 15, The Final Preview.

[Jerome E. Shidel Jr.]

Hello All,

Well I finally had a little bit of spare time and incorporated the enhancements 
I mentioned.

I foresee no further changes or enhancements. Technically, preview 15 should be 
called
Beta or RC 1. However, I just finished the modifications and hammered on the 
latest
version. So, I am just calling it Preview 15.

Basically, what has changed from 14 to 15.

Updated V8Power Tools.
Updated FDIMPLES.
Many additions to ALL package list.
Many additions to EXTRA software.
DOSBox installation support.

http://up.lod.bz/FDI 

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] DOSBox I/O issue follow-up

[Jerome E. Shidel Jr.]

The workaround is easy, you just read from STDIN as a file with DOS FN 0x3F.

The other is supposed to work and this is a little more code. But, who is 
complaining. :)
--
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=278785351=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOSBox I/O issue follow-up

[Jerome E. Shidel Jr.]

Sorry, minor correction on results.

> On Mar 22, 2016, at 9:06 PM, Jerome Shidel  wrote:
> 
> Hello Eric (and anyone else who is interested),
> 
> Here is a little proof-of-concept demonstration of the issue regarding I/O 
> redirection in DOSBox.
> 
> ; begin example code
> 
> ; NASM 2.11.08 for DOS
> ; Jerome Shidel, Public Domain.
> 
> use16
> 
> cpu 8086
> 
> org 0x100
> 
> StdPassThru:
> mov ah, 0x0b; DOS Check Standard Input Status
> int 0x21
> cmp al, 0x00; 0x00 = no character available, 0xff = present.
> je  NoInput
> mov ah, 0x08; DOS Get character from STDIN, no echo. AL = 
> Character
> int 0x21
> mov ah, 0x02; DOS Write DL character to STDOUT.
> mov dl, al
> int 0x21
> jmp StdPassThru
> 
> NoInput:
> mov ax, 0x4c00  ; DOS Terminate, no error code
> int 0x21
> 
> ; end example code
> 
> Compile with nasm PASSTHRU.ASM -fbin -o PASSTHRU.COM 
> 
> Run in default DOSBox:
> 
>   type passthru.asm | passthru.com 
>   Result garbage line of text.

Text goes immediately to STDOUT and does not go through PASSTHRU.COM 
.
(Sorry, I was running type passthru.com | passthru.com)

> 
> Run under FreeCOM shell inside DOSBox
> 
>   C:\FDOS\BIN\command.com 
>   type passthru.asm | passthru.com 
>   
>   result: .Text scrolls by, then infinite number of blank characters and 
> occasional 
>   control characters.
> 
> Run on real (or virtual machine of) FreeDOS, MS-DOS, PC-DOS….
> 
>   text of PASSTHRU.ASM is output and program terminates.

--
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=278785351=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.2 BETA, Coming soon--ish.

[Jerome E. Shidel Jr.]

Hello All,

This is mostly a status update regarding the FreeDOS 1.2 BETA release.

There have been no installer related issues reported with the current FDI 
Preview 14 and it
is technically ready for the BETA release. However, I intend on implementing a 
couple things
prior to that release. They will include:

A couple more features added to FDIMPLES for stand-alone mode usage.

An additional feature for detecting DOSBox in the V8Power Tools vinfo 
utility.

Due to either an issue that is probably in DOSBox or FreeCOM, I/O 
redirection
does not work to specification under DOSBox. This only effects the vstr 
part of 
the V8 Power Tools utilities. I intend on implementing a workaround in 
vstr to 
make FDI more DOSBox friendly.

Add a few lines in FDI to skip things like SYS transfer in DOSBox.

Maybe some more fine tuning of the BASE and ALL package lists.

I’ve been extremely busy over the last couple of weeks and have not had very 
much
free time to complete these items. I don’t see my schedule lightening up for 
quite a
while. But, I hope to squeeze a few minutes here and there to knock these items
out and have the BETA release ready soon--ish.


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=278785351=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FDI Preview 14 - Updated

[Jerome E. Shidel Jr.]

I decided that FDI should take care of a couple things. So, I pushed
a minor update.

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

[Freedos-user] FreeDOS Installer Preview 14 - The Final Chapter.

[Jerome E. Shidel Jr.]

Hello All,

The wholesome and awesome goodness of the FreeDOS Installer Preview 14 is now 
available. P14 contains many improvements over P13 including auto-partitioning 
(when obvious), fixed FDIMPLES bug, MBR updating and many many more 
enhancements.

http://up.lod.bz/FDI

I also ran an tested one of the USB stick images on a ancient Acer Netbook with 
a empty SSD drive. 

WARNING: If you don’t want your MBR updated, you will need to switch into 
advanced mode no later than the Welcome to FreeDOS message.

Except for any bug fixes, this is the final FDI Preview release until the 
FreeDOS 1.2 Beta. Mostly, that should only be
a fine-tuning of included packages.

Thanks again, Jerome


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

Re: [Freedos-user] FreeDOS 1.2+ Preview 12 - Now with Dimples

[Jerome E. Shidel Jr.]

> On Feb 23, 2016, at 3:05 PM, Eric Auer  wrote:
> 
> 
> Hi!
> 
>> Matuesz, I actually went and tested this.  MS-DOS 6.22 [0]
>> handles the MBR that same way as FDI [1] does. :/  Both leave a broken
>> MBR, one that cannot boot into the newly installed DOS.
> 
> Ouch. Note that MS DOS is from the time where nobody had any
> other operating system previously installed. FreeDOS has TWO
> new (and frequently happening!) situations to deal with:
> 
> - user has another OS and DOS must not kill the boot menu without asking
> 
> - user made a virtual computer for DOS, the disk contains nothing at all

- user has some old hardware they want to install and play with a newer DOS.

> 
> In the second case, it is good to automatically make a MBR from scratch.
> In the first case, it would be a disaster for those who want dual boot.

In the third case, neither solution works. MBR not blank and MBR needs 
overwritten.
User is angry to not have w working computer. Leaves and never comes back.

> 
>>> Naturally, an appropriately big warning must be presented before doing
>>> so, and if the user knows he has some tricky configuration (multi-boot),
>>> he should be able to select an option "leave my MBR alone please, I will
>>> take care of it myself".
>> 
>> YES!
> 
> +1
> 
> Cheers, Eric
> 

My understanding is that Jim wants a quick, easy, and friendly install process.
To throw this question at the user during a typical normal install, does not 
seem
to fit that request. 

In advanced mode starting in Preview 14, the user is provided with this 
question 
when they also have chosen to update the system boot files. A user who is 
doing multi-boot, probably would want to run it in advanced mode regardless
of wether the defaults in normal mode would suite their situation or not.

I think that it might be a viable compromise to warn the user at the time of 
download they need run in advanced mode for complex or multi-boot
installations. 

This would inform them that there may be an issue and also let them know
it even has advanced mode.

Jerome



--
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=272487151=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2+ Preview 12 - Now with Dimples

[Jerome E. Shidel Jr.]

Preview 14, Is going to zap the MBR by default in normal mode.

In advanced mode, this can be overridden. 

I may push Preview 14 out the door sometime today. Mostly, because I made a dumb
mistake in FDIMPLES with search and replace. Completely breaking the detailed
package selection in advanced mode without realizing it. :-(



--
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=272487151=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2+ Preview 12 - Now with Dimples

[Jerome E. Shidel Jr.]

> On Feb 23, 2016, at 8:54 AM, Corbin Davenport  
> wrote:
> 
> Is there a possibility FreeDOS could install the GRUB manager by default on 
> PCs with multiple partitions? Or even go a step further and try to detect an 
> existing GRUB installation, and adding it's own menu item to it?

I don’t think it would be very practical to do under DOS. Especially, when a 
preexisting grub may exist on a separate linux partition.

> 
> Corbin
> 
> On Tue, Feb 23, 2016 at 7:05 AM, Don Flowers  > wrote:
> OK - I have several PC's with varying modern installs (WIN7, WIN10, Xubuntu) 
> residing along with various versions of MS-DOS and FreeDOS (even a custom
> FAT16 version of FreeDOS). I have created several rescue disks and yet there 
> is
> always at least one install that either messes up my boot code (usually 
> fixable) or 
> deletes an entire partition even when hidden (thank you MS-DOS 6.2 and 
> Windows 10). 
> The point being it happens and the inew install should have the priority.
> If one has "precious" data then one better have a backup before installing.

This is how I am leaning now. 

Having a non-booting DOS install after a normal installation really is not an 
acceptable behavior. 

Therefore, I think in normal mode it should always just backup MBR to 
%DOSDIR%\ORIGINAL.BSS
and just zap it when it transfers the system files. 

> 
> On Tue, Feb 23, 2016 at 3:43 AM, Felix Miata  > wrote:
> Mateusz Viste composed on 2016-02-23 09:28 (UTC+0100):
> 
> > I'm going with Louis on this one. When installing FreeDOS, I'd expect
> > the installer to overwrite my MBR with clean boot code, so I don't have
> > any troubles booting FreeDOS post install. That's what MS-DOS did, and
> > that's what I expect from any OS in fact.
> 
> I expect more sophistication than such belligerence. Even WinXP checks MBR
> code compatibility, and leaves it undisturbed if OK.

Um, windows always trashed my boot loader on install in a multi-boot system.
It was always easiest to just install Windows, then install linux. That way I 
would
not have to fix it.

> 
> > Naturally, an appropriately big warning must be presented before doing
> > so, and if the user knows he has some tricky configuration (multi-boot),
> > he should be able to select an option "leave my MBR alone please, I will
> > take care of it myself".
> 
> This I find acceptable, and inconsistent with your previous paragraph. All
> the non-ancient Linux installers I'm familiar with allow the MBR to be kept
> undisturbed, even if it means the new Linux installation seems won't be 
> bootable.

I think this is in direct conflict with what Jim said he wanted.
Basically, only a few quick questions and you have finished installing.
However, if zapping the MBR is added. I will add a prompt in advanced mode
to not do it. Just like in advanced mode, you can change the install path, not
update config file, not transfer system files. etc.


--
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=272487151=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FDI Preview 13

[Jerome E. Shidel Jr.]

FDI Preview 13 is now available.

http://up.lod.bz/FDI 



--
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=272487151=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2+ Preview 12 - Now with Dimples

[Jerome E. Shidel Jr.]

There are a lot of major internal changes in 13. no sense testing 12.

Anyhow 13, floppy an 32mb slim usb images are up. it will be about an hour 
for the 512mb image. Internet is very slow where I am at right now.

http://up.lod.bz/FDI 


> On Feb 19, 2016, at 1:51 PM, Louis Santillan  wrote:
> 
> Hey all,
> 
> I plan to do another test run with the hardware I have.  1.2p12 or 13,
> which ever is available.
> 
> On Sat, Feb 13, 2016 at 3:46 PM, Jerome Shidel  wrote:
>> 
>>> On Feb 13, 2016, at 6:19 PM, Don Flowers  wrote:
>>> 
>>> I booted from the CD not USB , but my extreme test machine has 3 hard 
>>> drives wth various "C" drives among them. Even with XOSL hiding partitions, 
>>> I think the installer may not be prepared for setting drives beyond "D;" 
>>> "lastdrive=Z" notwithstanding.
>> 
>> If the installer is run in advanced mode, you can specify what drive you 
>> want it to install FreeDOS. Advanced mode can be entered 2 ways. Either by 
>> using "setup adv" from the command line or by pressing CTRL+C when it is 
>> waiting for user input. As long as dos can see a drive, it should be able to 
>> install to it. However, you would still need to know if you want it to go on 
>> E: F: X: or wherever. My only concern is SYS transfer of system files 
>> messing up your boot code.
>> 
>>> 
>>> Your rewrite should do the trick.
>> 
>> We will keep our fingers crossed. The installer works great. It's just 
>> getting the installers loader to setup an environment for it to run under 
>> that is compatible with all of the bizarre system configurations it may 
>> encounter. :-)
>> 
>> Hopefully have preview 13 out in a couple days (as free time permits).
>> 
>>> --
>>> 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=272487151=/4140
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> 
>> --
>> 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=272487151=/4140
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 
> --
> 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=272487151=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 

--
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=272487151=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2+ Preview 12 - Now with Dimples

[Jerome E. Shidel Jr.]

> On Feb 19, 2016, at 1:51 PM, Louis Santillan  wrote:
> 
> Hey all,
> 
> I plan to do another test run with the hardware I have.  1.2p12 or 13,
> which ever is available.

13 should be up in a few minutes or so.

> 
> On Sat, Feb 13, 2016 at 3:46 PM, Jerome Shidel  wrote:
>> 
>>> On Feb 13, 2016, at 6:19 PM, Don Flowers  wrote:
>>> 
>>> I booted from the CD not USB , but my extreme test machine has 3 hard 
>>> drives wth various "C" drives among them. Even with XOSL hiding partitions, 
>>> I think the installer may not be prepared for setting drives beyond "D;" 
>>> "lastdrive=Z" notwithstanding.
>> 
>> If the installer is run in advanced mode, you can specify what drive you 
>> want it to install FreeDOS. Advanced mode can be entered 2 ways. Either by 
>> using "setup adv" from the command line or by pressing CTRL+C when it is 
>> waiting for user input. As long as dos can see a drive, it should be able to 
>> install to it. However, you would still need to know if you want it to go on 
>> E: F: X: or wherever. My only concern is SYS transfer of system files 
>> messing up your boot code.
>> 
>>> 
>>> Your rewrite should do the trick.
>> 
>> We will keep our fingers crossed. The installer works great. It's just 
>> getting the installers loader to setup an environment for it to run under 
>> that is compatible with all of the bizarre system configurations it may 
>> encounter. :-)
>> 
>> Hopefully have preview 13 out in a couple days (as free time permits).
>> 
>>> --
>>> 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=272487151=/4140
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> 
>> --
>> 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=272487151=/4140
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 
> --
> 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=272487151=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 


--
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=272487151=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2+ Preview 12 - Now with Dimples

[Jerome E. Shidel Jr.]

> On Feb 12, 2016, at 10:26 PM, Eric Auer  wrote:
> 
> 
> Hi Don, to make a PESSIMISTIC GUESS about the following:
> 
>> Downloaded and burned to CD.
>> Lots of "Error writing to drive A: DOS area write protection violation
>> attempted" errors. Is there reason I am getting this?

It booted from CD? The USB image wasn’t really setup for that. 

> 
> Yes. Apparently version 1.2pre12 still tries to use pipelines, which
> in DOS always means using temp files, without setting the temp dir
> to a location on ramdisk or (if available) on your target harddisk?

Yes it did. 

Preview 11 would check for a pre-existing hard drive C: and if it was usable
would setup a temp directory. then it would use that to attempt to import
a couple things from the previous OS install. If it could not, it would
just wait until later when there was a hard drive it could use for temp
storage for the installation process. (This is why you had issues when
the USB stick booted as read only)

Preview 12: Just sets up a ram drive at startup, assumes all is well and moves 
on.
However, there was some old code that got left behind and is probably causing 
the 
write protect issue.

Preview 13: (coming soon) should resolve these issues.

> 
> This also means that all data sent through pipelines will be lost.
> 
> OPTIMISTICALLY, you MIGHT "simply" be suffering from a bug in how
> the DOSLFN driver interacts with the install process. It seems to
> cause A: access instead of access to the proper selected drive in
> certain situations, but you and Rugxulo know more about this than
> I, at this point ;-) You could try to skip loading that driver :-)
> 
> I am sure that Jerome & Rugxulo can give better, informed answers.

I have added a couple things to V8Power tools to remove the need for
piping in the startup section of FDI. 

I’m currently working on Preview 13. Basically, a complete rewrite of the
initialization an environment preparation for the installer. It is much more
robust and is completely drive letter agnostic. 


> 
> "Guessful" regards, Eric
> 
> PS: I suspected that LFN issue to be findfirst/findnext/findclose
> related, but it could also be something totally different, such as
> a bug in LFN support of command.com itself or in using LH w/o UMB.
> 
> 
> 
> --
> 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=272487151=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 


--
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=272487151=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.2+ Preview 12 - Now with Dimples

[Jerome E. Shidel Jr.]

Hello all,

Just released FDI Preview 12.

Some major non-UI underlying changes, for better performance and compatibility.
Too many improvements and far to many things to list. Hopefully, this will be 
the last 
preview before FreeDOS 1.2 beta. Next, I intend on looking through the package
lists and adding stuff to all and extras.

However, I mentioned dimples in the subject. I meant FDIMPLES. 
FreeDOS Installer - My Package List Editor Software. It is not 100% complete,
but it is fully integrated and works. Remember, you must be running the 
installer
in advanced mode for detailed package selections. You can enter advanced mode
by running “setup adv” or by pressing CTRL+C at any point the installer is 
waiting
on user input.

http://up.lod.bz/FDI 

Jerome--
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=272487151=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

> On Feb 2, 2016, at 12:17 PM, Eric Auer  wrote:
> 
> 
> Hi!
> 
>>> Wait, that is pretty serious! Only really important cache errors beep:
> 
> ...
> 
>> Hopefully, it is just from attempted writing of temp files to the locked USB 
>> stick.
> 
> Well that is still serious. Even if you do something as harmless as
> 
> copy STUFF SOMEWHERE | more
> 
> you would still end up 1. not seeing the output of "copy" and
> possibly even 2. block the "copy" process by stalling the pipe.
> 
> In short, please use a ramdisk for all your pipe and temp work :-)

Yeah, probably not going to do that. It adds to much complication 
to the installer startup. It would need to be very small and that
may risk package installation failure later on with fdinst. Also,
if a user did not boot the install media and just runs it from the 
command line, a pre-existing ramdisk may cause issues or be 
forcefully unloaded. It is also an additional driver to load. 
Compatible on all systems. etc.

There is an easy way around the issue. I will probably just have the 
installer test if C: is the USB stick prior to activating the TEMP 
directory. 

> 
> PS: More is a good example where pipes can be avoided, with help
> of my moresys driver ;-)

The batch file based FDI installer would not be very good without any 
pipes. It would have almost no flexibility at all. Would only have
hard coded package lists and would not be able to dynamically 
create customized system configuration files. 

> 
>> If the there is no beeping, when he boots the Floppy Install and
>> he only gets it when using the USB stick, It would probably be
>> due to the Read only USB stick. 
>> 
>> The floppy version, does not write to the floppy and at startup
>> checks to see if there is a writable drive C:. If so, it will try to 
>> configure a TEMP directory and see if it can import language
>> and DOSDIR settings...
> 
> It should probably not do that on C: but on the user-selected target
> drive, to avoid unwanted changes to C: ... In addition it should not
> use C: so early anyway: Maybe it needs to be formatted first.

At startup, it only uses C: if C: exists and is formatted. If those conditions
are met, It will check for system config files and import settings if they 
exist.

If C: is not formatted or does not exist. Then there would be nothing to 
import and no TEMP directory is setup at that time.

> 
>> If it cannot find C: or C: is not writable,
>> it will bypass the importing of settings.
> 
> Importing of settings?

Language settings, DOS Installation directory \FDOS \FREEDOS \OS
or whatever.

> 
>> the floppy will postpone setting up a TEMP directory ...
> 
> No need to postpone with a ramdisk ;-)
> 
>>  Sees C:
>> 
>>  Tries to configure the TEMP dir on C: (succeeds as 
>>  C:\FDSETUP\TEMP exists on image)
> 
> Hehe bad test ;-)

More or less, it is there on his system. It just isn’t writable. Not 
so much a bad test as more testing is required.

> 
>>  Attempts to import settings from C: (fails)
>> 
>>  Keeps C: as target drive and temp dir on C:
>> 
>>  Serious and repeated failures beyond this point. (fails, and 
>>  probable set /p system crash)
>> 
>> I have some ideas on how to resolve this issue. So, when
>> I get the time. I will take care of this compatibility issue.
> 
> Thanks! Cheers, Eric
> 
> 

Jerome

> 
> 
> --
> 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=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 


--
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=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

> On Feb 2, 2016, at 7:54 PM, Eric Auer  wrote:
> 
> 
> Hi!
> 
>>> Well that is still serious. Even if you do something as harmless as
>>> 
>>> copy STUFF SOMEWHERE | more
>>> 
>>> you would still end up 1. not seeing the output of "copy" and
>>> possibly even 2. block the "copy" process by stalling the pipe.
>>> 
>>> In short, please use a ramdisk for all your pipe and temp work :-)
>> 
>> Yeah, probably not going to do that. It adds to much complication 
>> to the installer startup. It would need to be very small and that
>> may risk package installation failure later on with fdinst.
> 
> That is exactly why I recommend using a ramdisk: Without ramdisk,
> everything sent through pipes goes to a digital black hole when
> the install disk is not writeable, risking plenty of side effects.
> 
> For piping stuff, a tiny ramdisk will be enough. If you assume that
> a computer which can boot from CD / DVD / USB has, say, at least 16
> MB RAM (yes youngsters, not 16 GB ;-)) then you could use 4 for the
> cache and 1 for the ramdisk and have 10 left for installer / unzip
> 32 bit activities still. So a bit of a ramdisk is totally harmless!

It really isn’t needed. 

> 
> By the way, how about creating a 600 MB RAMDISK (no joke) whenever
> the installer detects 1 GB or more RAM? That would allow users to
> do a full install to the ramdisk, effectively using your installer
> stick as a "LIVE CD" without install and without rebooting :-)

No reason, someone can not create an simple batch called something
like GOLIVE.BAT that could be included with the CD ISO. It could handle 
all of that post-boot. Also, with how the installer is designed. A drop in
could even be included to do it when the user exits the installer without
performing an install.

> 
>> if a user did not boot the install media and just runs it from
>> the command line, a pre-existing ramdisk may cause issues or be 
>> forcefully unloaded. It is also an additional driver to load.
> 
> Ramdisks are pretty compatible and I see no reason why loading more
> than one of them would cause any troubles. Also, my suggestion was
> to load a ramdisk in CONFIG & AUTOEXEC. Everybody who manually wants
> to start the installer from the command line of their existing DOS
> or Windows can be expected to know what they do, so I agree to not
> bother those by loading DRIVERS as side effect of installer start.
> 
> Maybe this is a good topic for review! As the moment, which steps
> do you take in CONFIG / AUTOEXEC and which steps, apart from the
> scripted invocation of (after optional fdisk and format) the DOS
> package manager and the creation of a target config and autoexec,
> are taken by the installer itself? Thanks for giving an overview!

The entire installer is modular, customizable and extensible. 
Other than at startup with language selection and initial target
verification, the installer performs no further actions until the
user makes the final “install now” selection. This with drop
in package lists, advanced mode, error handling screens and
all of the other steps it takes during execution. All logic is handled
inside the batch files that make up the installer. There is a rough
draft developer manual on the github source page that goes into
basic detail on what most of the different parts of the installer handle.

> 
>> There is an easy way around the issue. I will probably just have the 
>> installer test if C: is the USB stick prior to activating the TEMP 
>> directory. 
> 
> That will not work with PLOP, nor will it work with "booting from
> a harddisk image on CD or DVD", as those are all write-protected
> simulations of a C: harddisk as far as my intuition tells me that.

Actually, the installer already does this in automatic target drive
detection. That is how it knows to install to D: automatically. But, 
on some systems the USB drive is not C:, the installer automatically
targets C:. It shouldn’t be difficult to include some of this logic
into the initial (for settings import) TEMP directory setup.

> 
>> The batch file based FDI installer would not be very good without any 
>> pipes. It would have almost no flexibility at all. Would only have
>> hard coded package lists and would not be able to dynamically 
>> create customized system configuration files. 
> 
> You can do a lot with errorlevels and you can select packages AFTER
> selecting the target drive: By definition, as soon as the user has
> selected (and maybe formatted) a target drive, you can write it :-)

Absolutely, but this is some of what you would loos from the current 
installer. Modularity with simple drop in extendibility. Text file lists of
packages would be hard coded. Progress percentage could be 
done but all values would have to be calculated and hard coded for
every single package removal and install. No backup progress possible.
Import settings like DOSDIR and LANG from previous installation
would have to go. There are many things that would make the 

Re: [Freedos-user] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

Hi Don,

> On Feb 2, 2016, at 8:45 AM, Don Flowers <donr...@gmail.com> wrote:
> 
> USB installer is a different matter.
> First, please disable BELL on lbacache - it wreaks havoc on my wifes's 
> hearing aid. On 2nd boot I had to step through Config/autoexec.bat and ESC 
> out of LBACACHE.

I’ll see what I can do about the noise. Since it is probably not needed on the 
USB version, I may end up just removing LBACACHE from that version.

> Second on my Compaq Armada 1750 USB is only bootable by PLOP boot manager and 
> thus it a C: drive- this causes write protection on the USB (as it should) 
> with installer "confused" about how to handle the "ABORT, RETRY, IGNORE 
> error. Installation failed.

I know why this occurred. Basically, the installer see’s it is drive C: and 
startup trying to use it for it’s temporary files. When this occurs,
DOS starts throwing those error messages. The floppy version handles things a 
little bit differently.  This would not happen with the Floppy based version 
even if the floppy is write-protected and no hard drive existed. When, I get 
some more free time I will look into handling a write protected USB stick. 
Thanks for the heads-up.

> 
> On Tue, Feb 2, 2016 at 7:57 AM, Don Flowers <donr...@gmail.com 
> <mailto:donr...@gmail.com>> wrote:
> Very impressive "beta?"  installer.

Thank you. I called it Preview (alpha) version. Almost, beta.

> I tested it several ways;
> the test machine is a Compaq Armada 1750 Laptop,  PII MMX with 320MB
> ram a 60gb hard drive and a CDROM drive. 
> 1) Installed over existing FreeDOS 1.1.1
> 2) Installed with a blank formatted C: drive
> 3) Installed with a non-formatted drive.
> 
> The installer performed as expected with no hiccups whatever.

I’m glad to hear you had no issues with the Floppy based install. :-)

> Can't wait for the rest of the packages to be included!

This is something I'm are still trying to hash out with the FreeDOS
developers group. 

> 
> 
> On Mon, Feb 1, 2016 at 2:40 PM, Jerome E. Shidel Jr. <jer...@shidel.net 
> <mailto:jer...@shidel.net>> wrote:
> I just released the FreeDOS 1.2 Installer Preview 11. 
> 
> If you wish to participate in the general pre-beta testing
> of the hopefully soon to arrive FreeDOS 1.2 release, 
> you can find it’s floppy image and a link to the required 
> package repository CD image at:
> 
> http://up.load.bz/FDI/latest <http://up.load.bz/FDI/latest>
> 
> Also, there is a USB Stick Installer image available 
> that includes the packages. There is a link to it on the
> FDI Installer Prototype download page. Or, just use the 
> direct link  http://dnld.lod.bz/FDI-USB.zip <http://dnld.lod.bz/FDI-USB.zip>
> 
> What’s in Preview 11.
> 
>   Improved BOOT from any USB stick at any drive letter (A, B, C, D, E….)
> 
>   Improved Installation Target Detection. (C or D)
> 
>   Extra (not BASE or ALL), uninstalled packages on USB image. (about 50 
> extra)
> 
>   Welcome to FreeDOS message, converted to a installed package with NLS.
>   (removed language specific messages from autoexec.bat)
> 
>   V8Power Tools, converted to package like any other that gets installed 
> with ALL.
> 
>   Additional, BOOT menu item installed (DOS low - SAFE MODE)
> 
>   Moved CD driver from Installed FDCONFIG.SYS to AUTOEXEC.BAT
> 
>   Other minor improvements.
> 
> What is NOT in Preview 11. (Maybe 12, beta or not at all)
> 
>   Boot sector is not overwritten with boot code if it happens to be 
> missing.
>   ( If you boot sector needs replaced, see 
> https://sites.google.com/site/lpsantil/fdi12-msi-wind 
> <https://sites.google.com/site/lpsantil/fdi12-msi-wind> )
> 
>   Sufficient free space is not verified prior to installation.
> 
>   Language specific COMMAND.COM <http://command.com/> is installed. But, 
> it is not configured as default.
> 
>   Language specific FDCONFIG.SYS menu items.
> 
> Thanks, Jerome
> 
> 
> --
> 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=/4140 
> <http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net <mailto:Freedos-user@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/

[Freedos-user] Roll your own FreeDOS 1.2+

[Jerome E. Shidel Jr.]

Hello all, 

I have also created a youtube video that demonstrates how to 
create your own custom FreeDOS 1.2+ installation Floppy and
USB stick images with FDI. (The FreeDOS Installer — Preview 11) 

It demonstrates the complete process from scratch, includes what you need to 
download, how to configure the build environment inside VirtualBOX, changing the
included extra packages, customizing the OS version and all the way to having 
the both the Floppy and USB stick images.

https://youtu.be/9daLiLdG6SM 

You could also modify the to be installed AUTOEXEC.BAT and FDCONFIG.SYS files
that are located under \FDSETUP\SETUP in the FDI source as *.DEF files.

The \FDSETUP\AUTOEXEC.BAT and \FDSETUP\FDCONFIG.SYS contain the boot
configuration files for the installer images themselves. 

Enjoy,

Jerome

--
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=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

Hello again Don and Eric,

> On Feb 2, 2016, at 10:50 AM, Eric Auer  wrote:
> 
> 
> Hi Don et al,
> 
>> USB installer is a different matter.
>> First, please disable BELL on lbacache - it wreaks havoc on my wifes's
>> hearing aid.
> 
> Wait, that is pretty serious! Only really important cache errors beep:
> 
> - impossible CHS geometry or cylinder in CHS access
> - unsupported and rather exotic INT13 disk BIOS calls
> - disk write errors and disk read errors

Hopefully, it is just from attempted writing of temp files to the locked USB 
stick.

> - XMS driver errors (for example HIMEM A20 errors)
> - disk calls recursively doing other disk calls
> 
> Please let me know which errors happen on your system.
> 
>> Second on my Compaq Armada 1750 USB is only bootable by PLOP boot manager
>> and thus it a C: drive- this causes write protection on the USB (as it
>> should) with installer "confused" about how to handle the "ABORT, RETRY,
>> IGNORE error. Installation failed.
> 
> That might mean that PLOP itself is more or less a "bootable read
> only USB stick driver", which is quite unusual. Maybe the USB DOS
> installer tries to write to the stick! That would be unnecessary,
> if you ask me: It is much faster to write to a small ramdisk - the
> installer should only need small amounts of writing apart from the
> writes to the target disk. It should have minimal usage of pipelines
> because in DOS, those work with temp files: dir | more basically is
> "dir > tempfile" followed by "more < tempfile". Luckily, command.com
> respects the TEMP or TMP variable setting for selecting temp dirs :-)
> 
> If the beeps are due to write failure, then the installer will fail
> as well, because it probably relies on being able to put temp files
> in the stick. As said, it SHOULD not rely on that anyway, IMHO...
> 
> Regards, Eric

If the there is no beeping, when he boots the Floppy Install and
he only gets it when using the USB stick, It would probably be
due to the Read only USB stick. 

The floppy version, does not write to the floppy and at startup
checks to see if there is a writable drive C:. If so, it will try to 
configure a TEMP directory and see if it can import language
and DOSDIR settings. If it cannot find C: or C: is not writable,
it will bypass the importing of settings. It requires some temp
files to do the import. But if there is no drive C:, there are no 
settings. So, the floppy will postpone setting up a TEMP directory
until later in the install process when a writeable C: is present.
TEMP files are required  later on in the install process. This 
is no problem for the floppy install.

The USB version, mostly works the same, except there is what 
appears tp be a drive C: (on his system, some say the USB stick 
boots as D: or higher on their systems). What happens goes 
something like this:

Sees C:

Tries to configure the TEMP dir on C: (succeeds as 
C:\FDSETUP\TEMP exists on image)

Attempts to import settings from C: (fails)

Keeps C: as target drive and temp dir on C:

Serious and repeated failures beyond this point. (fails, and 
probable set /p system crash)

I have some ideas on how to resolve this issue. So, when
I get the time. I will take care of this compatibility issue.

Jerome.


> 
> 
> 
> --
> 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=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 


--
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=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

I just released the FreeDOS 1.2 Installer Preview 11. 

If you wish to participate in the general pre-beta testing
of the hopefully soon to arrive FreeDOS 1.2 release, 
you can find it’s floppy image and a link to the required 
package repository CD image at:

http://up.load.bz/FDI/latest 

Also, there is a USB Stick Installer image available 
that includes the packages. There is a link to it on the
FDI Installer Prototype download page. Or, just use the 
direct link  http://dnld.lod.bz/FDI-USB.zip 

What’s in Preview 11.

Improved BOOT from any USB stick at any drive letter (A, B, C, D, E….)

Improved Installation Target Detection. (C or D)

Extra (not BASE or ALL), uninstalled packages on USB image. (about 50 
extra)

Welcome to FreeDOS message, converted to a installed package with NLS.
(removed language specific messages from autoexec.bat)

V8Power Tools, converted to package like any other that gets installed 
with ALL.

Additional, BOOT menu item installed (DOS low - SAFE MODE)

Moved CD driver from Installed FDCONFIG.SYS to AUTOEXEC.BAT

Other minor improvements.

What is NOT in Preview 11. (Maybe 12, beta or not at all)

Boot sector is not overwritten with boot code if it happens to be 
missing.
( If you boot sector needs replaced, see 
https://sites.google.com/site/lpsantil/fdi12-msi-wind 
 )

Sufficient free space is not verified prior to installation.

Language specific COMMAND.COM  is installed. But, 
it is not configured as default.

Language specific FDCONFIG.SYS menu items.

Thanks, Jerome

--
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=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user